dbcve.org
3scale Api ManagementApplication · Redhat

CVE-2024-10295

HIGH · 7.5 CVSS v3.1 Published 2024-10-24
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
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
A flaw was found in Gateway. Sending a non-base64 'basic' auth with special characters can cause APICast to incorrectly authenticate a request. A malformed basic authentication header containing special characters bypasses authentication and allows unauthorized access to the backend. This issue can occur due to a failure in the base64 decoding process, which causes APICast to skip the rest of the authentication checks and proceed with routing the request upstream.

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

APICast (API Gateway) contains an authentication bypass vulnerability where malformed basic authentication headers containing special characters that fail base64 decoding cause the gateway to skip all authentication checks and route the request upstream anyway. This allows unauthorized access to backend services.

MitigationApply vendor patches for APICast when available. As a temporary workaround, implement additional authentication/authorization layers (e.g., API keys, OAuth) or network-level access controls to validate requests before they reach the gateway.

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
3scale Api ManagementApplication
Affected:= 2.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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/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 APICast installation
    Check if Red Hat 3scale API Management or APICast gateway is deployed in your environment by searching for apicast or 3scale services, pods, or packages.
    Affected if APICast or 3scale is not present in the environment, the system is not affected.
  2. Verify installed version
    Determine the installed version of 3scale API Management or APICast. Compare it against the affected version 2.0. Use package managers, container image tags, or API management admin consoles to retrieve version information.
    Affected if The installed version is exactly 2.0, the environment falls within the affected range.
  3. Confirm basic authentication is enabled
    Inspect APICast configuration files or API gateway settings to determine whether basic authentication is configured as an authentication method. Look for auth mechanisms set to basic, http, or similar authentication type in the gateway configuration.
    Affected if Basic authentication is not enabled or configured, the specific bypass condition cannot be triggered.
  4. Check authentication processing configuration
    Review the API gateway configuration for settings related to authentication header processing, particularly how the gateway handles basic auth headers that fail base64 decoding. Look for directives controlling authentication validation behavior.
    Affected if The gateway is configured to skip authentication on malformed headers, the vulnerability is present.
  5. Review authentication logs for bypass attempts
    Examine API gateway logs for requests with malformed basic authentication headers containing special characters. Look for patterns where authentication appears to be bypassed or where base64 decoding failures are logged.
    Affected if Logs show requests processed without authentication validation despite malformed auth headers, the vulnerability may be exploitable.

The environment is affected if 3scale API Management version 2.0 is installed with basic authentication enabled and the gateway processes malformed basic auth headers without proper validation.

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

Apply vendor patches for APICast when available. As a temporary workaround, implement additional authentication/authorization layers (e.g., API keys, OAuth) or network-level access controls to validate requests before they reach the gateway.

Fix this in 3scale Api Management Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA6.0 h
34.0 hours of engineering $5,940
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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