dbcve.org
OfbizApplication · Apache

CVE-2024-25065

CRITICAL · 9.1 CVSS v3.1 Published 2024-02-29
Fix available
A fix is available. Upgrade to 18.12.12 or later.
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
Possible path traversal in Apache OFBiz allowing authentication bypass. Users are recommended to upgrade to version 18.12.12, that fixes the issue.

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

A path traversal vulnerability exists in Apache OFBiz that allows attackers to bypass authentication mechanisms. This critical flaw (CVSS 9.1) could enable unauthorized access to the system by manipulating file paths in HTTP requests.

MitigationUpgrade Apache OFBiz to version 18.12.12 or later to remediate the path traversal vulnerability and restore proper authentication controls.

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
OfbizApplication
Affected:< 18.12.12

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 installed Apache OFBiz version
    Locate the OFBiz version file or check startup logs. The version is typically documented in a build file, version properties file, or displayed in the server startup output.
    Affected if The installed version is below 18.12.12 (for example, 18.12.11, 18.12.10, or earlier releases)
  2. Confirm OFBiz web application is deployed
    Verify that the OFBiz web application is running and accessible. This typically involves checking if the OFBiz web container (usually on port 8443 for HTTPS or 8080 for HTTP) is listening and responding.
    Affected if OFBiz web services are exposed and the version is below 18.12.12
  3. Review HTTP request handling configuration
    Examine the OFBiz web configuration files and controller mappings that handle incoming HTTP requests. Look for file-serving or resource-inclusion mechanisms that process user-supplied paths.
    Affected if The web framework processes file paths from HTTP requests and the version is below 18.12.12

You are affected if your deployed Apache OFBiz version is any release prior to 18.12.12 and the OFBiz web interface is accessible.

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 18.12.12 or later
Fixed in 18.12.12
Interim mitigation

Upgrade Apache OFBiz to version 18.12.12 or later to remediate the path traversal vulnerability and restore proper authentication controls.

Recommended fix High confidence

18.12.12

  1. 1. Back up the existing Apache OFBiz installation including all configuration files, databases, and custom code.
  2. 2. Download Apache OFBiz version 18.12.12 from the official Apache OFBiz download page (ofbiz.apache.org).
  3. 3. Stop the currently running OFBiz service.
  4. 4. Replace the existing OFBiz installation files with the new 18.12.12 version files, preserving custom configurations and data directories.
  5. 5. Review and update any custom configuration files to ensure compatibility with the new version.
  6. 6. Start the OFBiz service and verify the application is running correctly.
  7. 7. Test that the path traversal vulnerability is no longer exploitable and that authentication is working as expected.
Caveat Review release notes for 18.12.12 for any configuration or API changes that may affect custom components

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

Fix this in Ofbiz 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 the upgrade done

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