dbcve.org
OfbizApplication · Apache

CVE-2012-1622

CRITICAL · 9.8 CVSS v3.0 Published 2017-10-26
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
Apache OFBiz 10.04.x before 10.04.02 allows remote attackers to execute arbitrary code via unspecified vectors.

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

Apache OFBiz 10.04.x before 10.04.02 contains a critical remote code execution vulnerability allowing unauthenticated attackers to execute arbitrary code via unspecified vectors. This is a pre-authentication RCE affecting the enterprise ERP/CRM platform.

MitigationUpgrade Apache OFBiz to version 10.04.02 or later. If immediate patching is not possible, restrict network access to OFBiz services and implement additional authentication layers as a temporary compensating control.

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:= 10.04

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.0/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 OFBiz by checking for the 'ofbiz.jar' file, 'ofbiz' startup scripts in /opt, /usr/local, or application directories. Also check for web application archives (WAR files) containing 'ofbiz' in the filename in servlet containers.
    Affected if OFBiz software is found on the system
  2. Determine installed OFBiz version
    Check the version by examining the ofbiz.jar manifest file, the build.gradle or ivy.xml file in the OFBiz installation directory, or by accessing the OFBiz administration interface at /admin (if accessible). The version is typically displayed on the login page or in the about section.
    Affected if The installed version is 10.04.00 or 10.04.01 (any 10.04.x version before 10.04.02)
  3. Verify version against CVE affected range
    Compare the identified version number to the vulnerable range: 10.04.00 through 10.04.01 are affected. Versions 10.04.02 and later, or any version outside the 10.04.x branch, are NOT affected by this specific CVE.
    Affected if Version is exactly 10.04.00 or 10.04.01

The environment is affected if Apache OFBiz version 10.04.00 or 10.04.01 is installed, as this is a pre-authentication RCE requiring no special configuration to be exploitable.

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

Upgrade Apache OFBiz to version 10.04.02 or later. If immediate patching is not possible, restrict network access to OFBiz services and implement additional authentication layers as a temporary compensating control.

Recommended fix High confidence

Apache OFBiz 10.04.02 or later (recommended: latest stable release)

  1. 1. Backup your current OFBiz installation and database before proceeding with any upgrade.
  2. 2. Download Apache OFBiz version 10.04.02 or later from the official Apache OFBiz releases repository (https://ofbiz.apache.org/download.html).
  3. 3. Stop the currently running OFBiz service.
  4. 4. Migrate your configuration files, data, and custom components from the old installation to the new version.
  5. 5. Review and apply any necessary database schema updates for the new version.
  6. 6. Start the upgraded OFBiz service and verify functionality.
Caveat Review release notes for any breaking changes between 10.04.x and 10.04.02; test thoroughly in staging before production deployment

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

Fix this in Ofbiz Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,880
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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