dbcve.org
OfbizApplication · Apache

CVE-2024-47208

CRITICAL · 9.8 CVSS v3.1 Published 2024-11-18
Fix available
A fix is available. Upgrade to 18.12.17 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
Server-Side Request Forgery (SSRF), Improper Control of Generation of Code ('Code Injection') vulnerability in Apache OFBiz. This issue affects Apache OFBiz: before 18.12.17. Users are recommended to upgrade to version 18.12.17, 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 · moderate confidence

This vulnerability combines Server-Side Request Forgery (SSRF) and Code Injection in Apache OFBiz. SSRF allows attackers to make the server perform arbitrary requests to internal or external resources, potentially accessing sensitive internal services. Code Injection enables improper control of code generation, potentially allowing execution of arbitrary code on the affected system.

MitigationUpgrade Apache OFBiz to version 18.12.17 or later to resolve both the SSRF and code injection vulnerabilities.

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

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
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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 Apache OFBiz installation
    Locate the OFBiz installation directory and look for the build.gradle or gradle.properties file that typically contains the version definition, or check the WAR file manifest.
    Affected if Apache OFBiz is found to be installed on the system
  2. Determine the installed OFBiz version
    Open the build.gradle or gradle.properties file in the OFBiz root directory and read the version number, or check the manifest file within the OFBiz WAR files.
    Affected if The version is lower than 18.12.17 (e.g., 18.12.16, 18.12.15, earlier releases)
  3. Check if the web interface is exposed
    Identify whether the OFBiz web applications (such as the admin portal, webtools, or order management) are accessible over HTTP/HTTPS by reviewing server configuration files (such as server.xml for Tomcat or the OFBiz container configuration).
    Affected if The OFBiz web interface is externally accessible and the version is below 18.12.17
  4. Verify vulnerable endpoints are reachable
    Check the available web service endpoints and controllers (particularly those handling external requests or code execution) by examining the OFBiz controller.xml files in the webapp directories, and determine if unauthenticated or low-privilege access to these endpoints is possible.
    Affected if Endpoints that handle external requests or dynamic code generation are exposed and the OFBiz version is below 18.12.17

You are affected if Apache OFBiz is installed with a version lower than 18.12.17 and the vulnerable web endpoints or services are 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.17 or later
Fixed in 18.12.17
Interim mitigation

Upgrade Apache OFBiz to version 18.12.17 or later to resolve both the SSRF and code injection vulnerabilities.

Recommended fix High confidence

18.12.17

  1. Download Apache OFBiz version 18.12.17 or later from the official Apache OFBiz website (ofbiz.apache.org)
  2. Review the upgrade documentation provided with the release
  3. Back up your existing OFBiz data and configuration
  4. Deploy version 18.12.17 following the standard upgrade procedure
  5. Verify the application starts successfully and all services are operational

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
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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