dbcve.org
TikaApplication · Apache

CVE-2022-25169

MEDIUM · 5.5 CVSS v3.1 Published 2022-05-16
Fix available
A fix is available. Upgrade to 1.28.2 / 2.4.0 or later.
See remediation →
58/100
Remediation priority · Elevated
No privileges

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
The BPG parser in versions of Apache Tika before 1.28.2 and 2.4.0 may allocate an unreasonable amount of memory on carefully crafted files.

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 Tika's BPG (Better Portable Graphics) parser versions before 1.28.2 and 2.4.0 is vulnerable to resource exhaustion. Specially crafted BPG image files can cause the parser to allocate an unreasonable amount of memory, leading to denial of service conditions.

MitigationUpgrade Apache Tika to version 1.28.2, 2.4.0, or later. If immediate patching is not feasible, consider disabling the BPG parser or implementing memory allocation limits at the application level.

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
TikaApplication
Affected:< 1.28.2>= 2.0.0, < 2.4.0
Primavera UnifierApplication
Affected:>= 17.7, <= 17.12= 18.8= 19.12= 20.12= 21.12

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
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/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 Tika version
    Locate the tika-core or tika-server JAR file and check its version from the filename, MANIFEST.MF, or run: java -jar tika-core-{version}.jar --version
    Affected if The installed version is less than 1.28.2, OR greater than or equal to 2.0.0 but less than 2.4.0
  2. Verify BPG parser is available
    Confirm the BPG parser module (tika-parser-bpg) is present in the classpath or lib directory, or check if BPG content type detection is active
    Affected if The BPG parser is loaded and able to process BPG files in the environment
  3. Check Oracle Primavera Unifier version (if applicable)
    If Oracle Primavera Unifier is in use, identify its version through the Oracle Enterprise Manager, WebLogic admin console, or product documentation
    Affected if The installed version matches: 17.7 through 17.12, 18.8, 19.12, 20.12, or 21.12, AND the application processes BPG image uploads

A user is affected if their Apache Tika version falls within the vulnerable ranges AND the BPG parser is enabled, or if they run a vulnerable Oracle Primavera Unifier version that processes BPG images.

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 1.28.2 / 2.4.0 or later
Fixed in 1.28.22.4.0
Interim mitigation

Upgrade Apache Tika to version 1.28.2, 2.4.0, or later. If immediate patching is not feasible, consider disabling the BPG parser or implementing memory allocation limits at the application level.

Recommended fix High confidence

Apache Tika 1.28.2 or 2.4.0 (depending on major version); Oracle Primavera Unifier patches via Oracle Critical Patch Updates

  1. For Apache Tika: Upgrade to version 1.28.2 if using the 1.x line, or upgrade to version 2.4.0 if using the 2.x line
  2. For Primavera Unifier: Apply the relevant Oracle Critical Patch Update that addresses this vulnerability for your specific version (17.7-17.12, 18.8, 19.12, or 20.12)
  3. After upgrading, verify the BPG parser handles large files within reasonable memory constraints
  4. Consider implementing memory limits for parser operations as an additional defense-in-depth measure
Caveat Likely minimal - this is a memory allocation fix with no known breaking API changes

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

Fix this in Tika Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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