dbcve.org
UimajApplication · Apache

CVE-2022-32287

HIGH · 7.5 CVSS v3.1 Published 2022-11-03
Fix available
A fix is available. Upgrade to after 3.3.0 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
A relative path traversal vulnerability in a FileUtil class used by the PEAR management component of Apache UIMA allows an attacker to create files outside the designated target directory using carefully crafted ZIP entry names. This issue affects Apache UIMA Apache UIMA version 3.3.0 and prior versions. Note that PEAR files should never be installed into an UIMA installation from untrusted sources because PEAR archives are executable plugins that will be able to perform any actions with the same privileges as the host Java Virtual Machine.

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

A relative path traversal vulnerability exists in the FileUtil class of Apache UIMA's PEAR management component. Attackers can craft malicious ZIP archives containing entry names with '../' sequences to write files outside the intended target directory during PEAR installation. The vulnerability stems from insufficient validation of file paths during ZIP extraction.

MitigationDo not install PEAR files from untrusted sources. Implement strict path validation in the FileUtil class to reject ZIP entries containing path traversal sequences and verify canonical paths remain within the target directory before file extraction.

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
UimajApplication
Affected:<= 3.3.0

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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 UIMA installation
    Search for Apache UIMA directories or JAR files (such as uimaj-*.jar) in the system
    Affected if Apache UIMA software is present on the host
  2. Check Uimaj version
    Examine the version information of the installed Apache Uimaj JAR or library files, typically found in the filename or manifest
    Affected if The installed version is 3.3.0 or lower (any version <= 3.3.0)
  3. Verify PEAR installation capability
    Determine whether the PEAR management component (used for installing .pear files) is accessible or can be invoked
    Affected if PEAR file installation functionality is available in the environment
  4. Inspect FileUtil path validation
    Examine the FileUtil class source or bytecode within the PEAR management component for handling of ZIP entry paths
    Affected if The FileUtil class does not validate or reject path traversal sequences like '../' in ZIP entries before extraction

A system is affected if it runs Apache Uimaj version 3.3.0 or lower with the PEAR management component enabled, allowing installation of PEAR files from potentially untrusted sources.

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 a release after 3.3.0
Interim mitigation

Do not install PEAR files from untrusted sources. Implement strict path validation in the FileUtil class to reject ZIP entries containing path traversal sequences and verify canonical paths remain within the target directory before file extraction.

Recommended fix Moderate confidence

Apache UIMA 3.3.1 or later

  1. 1. Identify all systems running Apache UIMA version 3.3.0 or prior.
  2. 2. Back up the UIMA installation and any PEAR files before making changes.
  3. 3. Download Apache UIMA version 3.3.1 or later from the official Apache UIMA distribution repository.
  4. 4. Stop any running UIMA services or applications that use the UIMA framework.
  5. 5. Replace the existing UIMA installation with the new version, preserving configuration files.
  6. 6. Verify the FileUtil class in the PEAR management component has been updated to prevent path traversal.
  7. 7. Restart UIMA services and validate the installation.
  8. 8. Re-scan any previously processed PEAR files to ensure no malicious path traversal artifacts exist.
Caveat Review release notes for any API or configuration changes between 3.3.0 and the target upgrade version before deploying to production

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

Fix this in Uimaj Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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