dbcve.org
OfbizApplication · Apache

CVE-2024-36104

CRITICAL · 9.1 CVSS v3.1 Published 2024-06-04
Fix available
A fix is available. Upgrade to 18.12.14 or later.
See remediation →
100/100
Remediation priority · Urgent
High EPSS 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
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in Apache OFBiz. This issue affects Apache OFBiz: before 18.12.14. Users are recommended to upgrade to version 18.12.14, which 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 · high confidence

Path traversal vulnerability in Apache OFBiz allows attackers to access files outside the intended restricted directory using '..' sequences in file paths. The CVSS 9.1 indicates severe impact, potentially enabling unauthorized file reads or code execution.

MitigationUpgrade Apache OFBiz to version 18.12.14 or later to resolve the path traversal vulnerability.

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

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. Locate Apache OFBiz installation and determine version
    Check for OFBiz directories (commonly in /opt/ofbiz, /home/*/ofbiz, or the application server's webapps directory). Look for a VERSION.txt file or check the build.gradle/gradle.properties for the 'ofbiz.version' property.
    Affected if The installed version is found to be below 18.12.14 (e.g., 18.12.13, 18.12.12, older releases)
  2. Verify OFBiz web application is accessible
    Attempt to access the OFBiz control panel or web interface via HTTP/HTTPS (default ports 8443 for secure, 8080 for standard). The path traversal would be exploited through web requests.
    Affected if The web interface is exposed and responds to requests
  3. Confirm version against CVE range
    Review the identified version number from step 1 and compare it to the affected range: any version less than 18.12.14.
    Affected if The installed version is 18.12.13 or any earlier release (18.12.x series before .14, or 17.x and older)
  4. Check for recent OFBiz process or service
    Run 'ps aux | grep ofbiz' or check running Java processes to see if OFBiz is actively running as a service.
    Affected if OFBiz is running and the version cannot be confirmed as 18.12.14 or later

If Apache OFBiz is installed and the version is below 18.12.14 with the web interface accessible, the environment is affected by this path traversal vulnerability.

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.14 or later
Fixed in 18.12.14
Interim mitigation

Upgrade Apache OFBiz to version 18.12.14 or later to resolve the path traversal vulnerability.

Recommended fix High confidence

18.12.14

  1. 1. Back up your current Apache OFBiz installation and database before proceeding with the upgrade
  2. 2. Download Apache OFBiz version 18.12.14 from the official Apache OFBiz distribution repository (ofbiz.apache.org)
  3. 3. Stop the running OFBiz service
  4. 4. Replace the existing OFBiz installation files with the new version 18.12.14 files
  5. 5. Restore any custom configurations, scripts, or custom code from your backup to the new installation
  6. 6. Review and apply any necessary migration steps documented in the release notes for version 18.12.14
  7. 7. Start the OFBiz service
  8. 8. Verify the upgrade was successful by checking that OFBiz starts without errors and the path traversal vulnerability is resolved

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