dbcve.org
BackstageApplication · Linuxfoundation

CVE-2024-45816

MEDIUM · 6.5 CVSS v3.1 Published 2024-09-17
Fix available
A fix is available. Upgrade to 1.10.13 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Backstage is an open framework for building developer portals. 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. This has been fixed in the 1.10.13 release of the `@backstage/plugin-techdocs-backend` package. All users are advised to upgrade. There are no known workarounds for this vulnerability.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Backstage's TechDocs module using AWS S3 or GCS storage providers fails to properly scope access to intended documents, allowing retrieval of any file in the storage bucket and bypassing Backstage's permission model.

MitigationUpgrade `@backstage/plugin-techdocs-backend` to version 1.10.13 or later to enforce proper content access restrictions.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
BackstageApplication
Affected:< 1.10.13

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the installed TechDocs backend version
    Check package.json or run npm list @backstage/plugin-techdocs-backend to determine the installed version of the TechDocs backend plugin
    Affected if The installed version is lower than 1.10.13
  2. Verify the Backstage version if using bundled packages
    Check the main Backstage package.json or the installed @backstage/version for the overall Backstage version
    Affected if The Backstage version is lower than 1.10.13
  3. Confirm TechDocs storage provider configuration
    Examine the TechDocs configuration file (app-config.yaml or app-config.local.yaml) for techdocs.builder and techdocs.storage type settings, specifically looking for awsS3 or googleStorage providers
    Affected if The storage provider is set to AWS S3 (awsS3) or Google Cloud Storage (googleStorage) and the version is below 1.10.13
  4. Inspect environment variables for storage configuration
    Review environment variables such as TECHDOCS_STORAGE_BUCKET, AWS_S3_BUCKET, or related GCS bucket configuration variables in the deployment environment
    Affected if Environment variables indicate S3 or GCS bucket storage is in use with a vulnerable version

A user is affected if they are running any Backstage version below 1.10.13 with TechDocs configured to use AWS S3 or Google Cloud Storage as the storage provider.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.10.13 or later
Fixed in 1.10.13
Interim mitigation

Upgrade `@backstage/plugin-techdocs-backend` to version 1.10.13 or later to enforce proper content access restrictions.

Recommended fix High confidence

@backstage/plugin-techdocs-backend version 1.10.13 or later

  1. Identify the `@backstage/plugin-techdocs-backend` package in your Backstage project dependencies
  2. Run `yarn upgrade @backstage/plugin-techdocs-backend@^1.10.13` or `npm install @backstage/plugin-techdocs-backend@^1.10.13` to upgrade to the fixed version
  3. Verify the upgrade was successful by checking the installed version with `yarn list @backstage/plugin-techdocs-backend` or `npm list @backstage/plugin-techdocs-backend`
  4. Test TechDocs functionality with your AWS S3 or GCS storage provider to confirm the path traversal vulnerability is remediated
Caveat Upgrading Backstage packages may introduce breaking changes; review the Backstage changelog and test thoroughly before deploying to production

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Backstage Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,752.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-45816 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-45816 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data