dbcve.org
Improper AuthorizationWeakness · CWE-285

CVE-2024-52528

CRITICAL · 9.3 CVSS v4.0 Published 2024-11-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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
Budget Control Gateway acts as an entry point for incoming requests and routes them to the appropriate microservices for Budget Control. Budget Control Gateway does not properly validate auth tokens, which allows attackers to bypass intended restrictions. This vulnerability is fixed in 1.5.2.

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 · moderate confidence

The Budget Control Gateway acts as an API entry point that routes requests to downstream microservices but fails to properly validate authentication tokens. This allows attackers to bypass intended access restrictions and reach protected resources without proper authorization.

MitigationUpgrade Budget Control Gateway to version 1.5.2 or later, which contains the proper auth token validation fix.

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

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
None
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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. Confirm Budget Control Gateway is installed
    Locate the Budget Control Gateway installation by checking for the gateway process, service, or installation directory on the system. Common locations include /opt/budget-control-gateway, /usr/local/budget-gateway, or as a systemd service named budget-control-gateway.
    Affected if The gateway software is present on the system
  2. Identify the installed version
    Query the installed version using the gateway's CLI (e.g., budget-gateway --version), check a VERSION file in the installation directory, or call the /health or /version API endpoint if the service is running.
    Affected if Unable to determine version or version is below 1.5.2
  3. Verify the API gateway is network accessible
    Test connectivity to the gateway's API ports (common defaults: 8080, 8443, or configured port) using curl or telnet from an external host or confirm the service is binding to a reachable network interface.
    Affected if The gateway API is exposed on a network and version is below 1.5.2
  4. Confirm authentication handling is in use
    Inspect the gateway configuration file (typically gateway.yaml, config.json, or similar in the installation directory) for auth-token-validation, token-validation, or authentication settings. Verify the gateway is configured to validate tokens for downstream requests.
    Affected if The gateway is configured to validate tokens and the installed version is below 1.5.2

You are affected if Budget Control Gateway version below 1.5.2 is installed, the API gateway is network-accessible, and token validation is enabled in the configuration.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Budget Control Gateway to version 1.5.2 or later, which contains the proper auth token validation fix.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-52528 — 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-52528 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