Skip to content

Apache Tika vulnerable to uncontrolled memory consumption

Moderate severity GitHub Reviewed Published May 17, 2022 to the GitHub Advisory Database • Updated Jan 31, 2023

Package

maven org.apache.tika:tika (Maven)

Affected versions

< 1.28.2
>= 2.0.0, < 2.4.0

Patched versions

1.28.2
2.4.0

Description

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.

References

Published by the National Vulnerability Database May 16, 2022
Published to the GitHub Advisory Database May 17, 2022
Reviewed May 25, 2022
Last updated Jan 31, 2023

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Local
Attack complexity
Low
Privileges required
None
User interaction
Required
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H

EPSS score

0.051%
(21st percentile)

Weaknesses

CVE ID

CVE-2022-25169

GHSA ID

GHSA-7qcq-xp2f-56f6

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.