dbcve.org
BackstageApplication · Linuxfoundation

CVE-2024-45815

MEDIUM · 6.5 CVSS v3.1 Published 2024-09-17
Fix available
A fix is available. Upgrade to 1.26.0 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. A malicious actor with authenticated access to a Backstage instance with the catalog backend plugin installed is able to interrupt the service using a specially crafted query to the catalog API. This has been fixed in the `1.26.0` release of the `@backstage/plugin-catalog-backend`. 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

This is a denial-of-service vulnerability in the Backstage catalog-backend plugin. An authenticated user with access to the catalog API can send specially crafted queries that cause the service to become unavailable. The vulnerability was addressed in version 1.26.0 of @backstage/plugin-catalog-backend.

MitigationUpgrade @backstage/plugin-catalog-backend to version 1.26.0 or later. No workarounds are available.

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.26.0

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
None
Integrity
None
Availability
High

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

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. Verify catalog-backend plugin is installed
    Check your project's package.json or package-lock.json for @backstage/plugin-catalog-backend in dependencies. Run: npm list @backstage/plugin-catalog-backend or grep -r '@backstage/plugin-catalog-backend' package.json
    Affected if The plugin appears in your dependencies
  2. Determine installed version of the plugin
    Run npm list @backstage/plugin-catalog-backend to see the exact version number, or inspect node_modules/@backstage/plugin-catalog-backend/package.json for the version field
    Affected if The installed version is lower than 1.26.0 (e.g., 1.25.0, 1.24.0, etc.)
  3. Confirm catalog API is enabled
    Check your Backstage app config (app-config.yaml) for catalog plugin configuration. Look for catalog settings in the plugins section or any router configuration exposing the catalog-backend endpoints
    Affected if The catalog API endpoints are exposed and accessible to authenticated users
  4. Check for unauthenticated access to catalog
    Review your backend authentication configuration to determine whether the catalog API requires authentication. Inspect your backend router setup for the catalog-backend plugin
    Affected if Authenticated users can access the catalog API (this is the condition required for exploitation)

You are affected if @backstage/plugin-catalog-backend is installed with a version below 1.26.0 AND your catalog API is accessible to authenticated users, as the DoS requires a user with catalog API access to send malicious queries.

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.26.0 or later
Fixed in 1.26.0
Interim mitigation

Upgrade @backstage/plugin-catalog-backend to version 1.26.0 or later. No workarounds are available.

Recommended fix High confidence

@backstage/[email protected]

  1. Locate the `@backstage/plugin-catalog-backend` dependency in your project's `package.json` file
  2. Update the version of `@backstage/plugin-catalog-backend` to `1.26.0` or later
  3. Run `yarn install` or `npm install` to update the dependency
  4. Verify the package is installed at version 1.26.0 or higher using `yarn list @backstage/plugin-catalog-backend` or `npm list @backstage/plugin-catalog-backend`
  5. Restart the Backstage backend service to load the patched version
  6. Test that the catalog API continues to function normally

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-45815 — 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-45815 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