dbcve.org
AuroraApplication · Apache

CVE-2024-27905

CRITICAL · 9.1 CVSS v3.1 Published 2024-02-27
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
** UNSUPPORTED WHEN ASSIGNED ** Exposure of Sensitive Information to an Unauthorized Actor vulnerability in Apache Aurora. An endpoint exposing internals to unauthenticated users can be used as a "padding oracle" allowing an anonymous attacker to construct a valid authentication cookie. Potentially this could be combined with vulnerabilities in other components to achieve remote code execution. As this project is retired, we do not plan to release a version that fixes this issue. Users are recommended to find an alternative or restrict access to the instance to trusted users. NOTE: This vulnerability only affects products that are no longer supported by the maintainer.

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

Apache Aurora contains a padding oracle vulnerability where an unauthenticated endpoint exposes internal information, allowing attackers to decrypt or construct valid authentication cookies. This can enable full authentication bypass and potentially lead to remote code execution when chained with other vulnerabilities.

MitigationSince the project is retired with no fix planned, organizations should either migrate to an alternative solution or implement strict network-level access controls to limit exposure to trusted users only.

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
AuroraApplication
Affected:>= 0.5.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
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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 if Apache Aurora is installed
    Search for Aurora installation directories, process lists, or service configurations (e.g., ps aux | grep -i aurora, find /opt -name '*aurora*', check systemd services)
    Affected if Apache Aurora is found running in the environment
  2. Determine installed Aurora version
    Check the version file in the Aurora installation directory or run 'aurora version' if available; compare against the affected range >= 0.5.0
    Affected if The installed version is 0.5.0 or higher
  3. Verify network exposure of unauthenticated endpoints
    Review firewall rules, network ACLs, or proxy configurations to determine if Aurora management ports (typically 8081, 8082) are reachable from untrusted network segments or the public internet
    Affected if Aurora management interfaces are accessible from untrusted networks without authentication controls
  4. Confirm unauthenticated endpoint behavior
    Attempt a request to the root or /health endpoint of the Aurora service from an unauthorized network location to verify it responds without authentication
    Affected if The service responds to unauthenticated requests, indicating the padding oracle endpoint is exposed

A user is affected if Apache Aurora version 0.5.0 or higher is running and its unauthenticated endpoints are accessible from untrusted network locations.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Since the project is retired with no fix planned, organizations should either migrate to an alternative solution or implement strict network-level access controls to limit exposure to trusted users only.

Recommended fix High confidence
  1. Restrict network access to the Apache Aurora instance to trusted users only, such as by using firewall rules or network segmentation
  2. If the Aurora instance is exposed to the internet, block external access entirely or place it behind a VPN with strong authentication
  3. If possible, disable or remove the vulnerable endpoint that exposes internals to unauthenticated users
  4. Review and limit cookie/credential handling to prevent padding oracle attacks
  5. Monitor access logs for suspicious authentication patterns

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

Fix this in Aurora Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,690
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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