Em resumo
- CVE-2023-41048 é uma vulnerabilidade MÉDIO (CVSS 5.4) que afeta plone-namedfile, namedfile (plone).
- Chance de exploração nos próximos 30 dias (EPSS): 0.57%, maior que 47.0% das vulnerabilidades.
- Correção: atualize para 6.0.3, 6.1.3, 6.2.1, 5.6.1 ou posterior.
| Package | Affected versions | Patched versions |
|---|
| plone-namedfile PyPI | ≥ 6.0.0, < 6.0.3≥ 6.1.0, < 6.1.3≥ 6.2.0, < 6.2.1< 5.6.1
| 6.0.36.1.36.2.15.6.1
|
| namedfile | = 6.2.0≥ 6.0.0, < 6.0.3≥ 6.1.0, < 6.1.3< 5.6.1
| 6.0.36.1.35.6.1
|
Description
Impact
There is a stored cross site scripting vulnerability for SVG images. A security hotfix from 2021 already partially fixed this, by making sure SVG images are always downloaded instead of shown inline. But the same problem still exists for scales of SVG images.
Note that an image tag with an SVG image as source is not vulnerable, even when the SVG image contains malicious code. To exploit the vulnerability, an attacker would first need to upload an image, and then trick a user into following a specially crafted link.
All versions of plone.namedfile are impacted.
Patches
Patches will be released in various plone.namedfile releases:
- 5.6.1 (for Plone 5.2)
- 6.0.3 (for Plone 6.0.0-6.0.4)
- 6.1.3 (for Plone 6.0.5-6.0.6)
- 6.2.1 (for Plone 6.0.7)
Workarounds
There is no workaround.
NVD description
plone.namedfile allows users to handle `File` and `Image` fields targeting, but not depending on, Plone Dexterity content. Prior to versions 5.6.1, 6.0.3, 6.1.3, and 6.2.1, there is a stored cross site scripting vulnerability for SVG images. A security hotfix from 2021 already partially fixed this by making sure SVG images are always downloaded instead of shown inline. But the same problem still exists for scales of SVG images. Note that an image tag with an SVG image as source is not vulnerable, even when the SVG image contains malicious code. To exploit the vulnerability, an attacker would first need to upload an image, and then trick a user into following a specially crafted link. Patches are available in versions 5.6.1 (for Plone 5.2), 6.0.3 (for Plone 6.0.0-6.0.4), 6.1.3 (for Plone 6.0.5-6.0.6), and 6.2.1 (for Plone 6.0.7). There are no known workarounds.
Running one of these products? Scan your site to see whether it exposes a vulnerable version.
Scan my site free