En resumen
- CVE-2023-25571 es una vulnerabilidad MEDIO (CVSS 5.4) que afecta a backstage catalog-model (linuxfoundation), backstage core-components (linuxfoundation), backstage plugin-catalog-backend (linuxfoundation).
- Probabilidad de explotación en los próximos 30 días (EPSS): 0.45%, mayor que el 39.5% de las vulnerabilidades.
- Solución: actualizar a 1.2.0, 0.12.4, 1.7.2 o posterior.
Description
Impact
This vulnerability allows a malicious actor with access to add or modify content in an instance of the Backstage software catalog to inject script URLs in the entities stored in the catalog. If users of the catalog then click on said URLs, that can lead to an XSS attack.
Patches
This vulnerability has been patched in both the frontend and backend implementations. The default Link component from @backstage/core-components will now reject javascript: URLs, and there is a global override of window.open to do the same.
In addition the catalog model as well as the catalog backend now has additional validation built in that prevents javascript: URLs in known annotations.
Workarounds
The general practice of limiting access to modifying catalog content and requiring code reviews greatly helps mitigate this vulnerability.
For more information
If you have any questions or comments about this advisory:
NVD description
Backstage is an open platform for building developer portals. `@backstage/catalog-model` prior to version 1.2.0, `@backstage/core-components` prior to 0.12.4, and `@backstage/plugin-catalog-backend` prior to 1.7.2 are affected by a cross-site scripting vulnerability. This vulnerability allows a malicious actor with access to add or modify content in an instance of the Backstage software catalog to inject script URLs in the entities stored in the catalog. If users of the catalog then click on said URLs, that can lead to an XSS attack.
This vulnerability has been patched in both the frontend and backend implementations. The default `Link` component from `@backstage/core-components` version 1.2.0 and greater will now reject `javascript:` URLs, and there is a global override of `window.open` to do the same. In addition, the catalog model v0.12.4 and greater as well as the catalog backend v1.7.2 and greater now has additional validation built in that prevents `javascript:` URLs in known annotations. As a workaround, the general practice of limiting access to modifying catalog content and requiring code reviews greatly help mitigate this vulnerability.
Running one of these products? Scan your site to see whether it exposes a vulnerable version.
Scan my site free