dbcve.org
OfbizApplication · Apache

CVE-2022-47501

HIGH · 7.5 CVSS v3.1 Published 2023-04-14
Fix available
A fix is available. Upgrade to 18.12.07 or later.
See remediation →
84/100
Remediation priority · High
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
Arbitrary file reading vulnerability in Apache Software Foundation Apache OFBiz when using the Solr plugin. This is a  pre-authentication attack. This issue affects Apache OFBiz: before 18.12.07.

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 OFBiz versions before 18.12.07 contain a pre-authentication arbitrary file reading vulnerability in the Solr plugin integration. Attackers can exploit this to read sensitive files on the host system without any authentication credentials, likely through path traversal in Solr-related request parameters.

MitigationUpgrade Apache OFBiz to version 18.12.07 or later. If immediate patching is not feasible, disable or restrict network access to the Solr plugin endpoints and implement network segmentation to limit exposure.

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

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
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 the installed Apache OFBiz version
    Locate the OFBiz installation directory and check the version. Typically found in a 'VERSION' or 'build.gradle' file, or by examining the WAR file metadata in the 'hot-deploy' or 'framework' directories.
    Affected if The installed version is any version prior to 18.12.07.
  2. Confirm the Solr plugin is in use
    Check if the Solr plugin is deployed by looking for the 'solr' component directory under the OFBiz 'framework' or 'applications' folder, or by searching for Solr-related configuration files such as 'solrconfig.xml' or 'schema.xml' in the installation.
    Affected if The Solr plugin directory and configuration files exist in the OFBiz installation.
  3. Verify network accessibility of Solr endpoints
    Review network firewall rules, reverse proxy configurations, or OFBiz security constraints to determine if the Solr service ports (typically 8983) or OFBiz endpoints handling Solr requests are exposed to untrusted networks.
    Affected if Solr-related endpoints are reachable from the internet or untrusted internal networks without authentication.
  4. Examine access logs for suspicious Solr requests
    Search OFBiz and Solr access logs for unusual request patterns, particularly those containing path traversal sequences such as '../' or file references outside the Solr data directory.
    Affected if Logs show unauthenticated requests to Solr endpoints with path traversal patterns or access to sensitive system files.

You are affected if your installed OFBiz version is before 18.12.07 AND the Solr plugin is enabled and exposed, regardless of whether exploitation indicators are yet visible in logs.

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.07 or later
Fixed in 18.12.07
Interim mitigation

Upgrade Apache OFBiz to version 18.12.07 or later. If immediate patching is not feasible, disable or restrict network access to the Solr plugin endpoints and implement network segmentation to limit exposure.

Recommended fix High confidence

18.12.07

  1. 1. Back up the entire existing OFBiz installation directory and database before proceeding
  2. 2. Download Apache OFBiz version 18.12.07 from the official Apache OFBiz releases page (https://ofbiz.apache.org/download.html)
  3. 3. Stop the currently running OFBiz services
  4. 4. Create a full backup of the database and all configuration files (including entity engine, service engine, and component configuration files)
  5. 5. Extract the new 18.12.07 release to a new directory
  6. 6. Copy or migrate essential configuration files from the old installation to the new one
  7. 7. Review and update any deprecated configuration settings if needed
  8. 8. Start the OFBiz services and verify the application is running correctly

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

Fix this in Ofbiz Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,580
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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