First published: Tue Sep 17 2024(Updated: )
### Impact When using the AWS S3 or GCS storage provider for TechDocs it is possible to access content in the entire storage bucket. This can leak contents of the bucket that are not intended to be accessible, as well as bypass permission checks in Backstage. ### Patches This has been fixed in the 1.10.13 release of the `@backstage/plugin-techdocs-backend` package. ### References If you have any questions or comments about this advisory: Open an issue in the [Backstage repository](https://github.com/backstage/backstage) Visit our Discord, linked to in [Backstage README](https://github.com/backstage/backstage)
Credit: security-advisories@github.com security-advisories@github.com
Affected Software | Affected Version | How to fix |
---|---|---|
npm/@backstage/plugin-techdocs-backend | <1.10.13 | 1.10.13 |
Backstage | <1.10.13 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2024-45816 has been classified as a high-severity vulnerability due to the potential for unauthorized access to sensitive content in cloud storage buckets.
To fix CVE-2024-45816, upgrade the version of @backstage/plugin-techdocs-backend to 1.10.13 or later.
CVE-2024-45816 affects versions of the Backstage framework prior to 1.10.13, specifically those using AWS S3 or Google Cloud Storage providers.
The risks of CVE-2024-45816 include leaking unintended content from storage buckets and bypassing permission checks within Backstage.
There is no documented workaround for CVE-2024-45816; upgrading to the patched version is recommended to mitigate the vulnerability.