Skip to content
Fencer Intel
medium 5.5

CVE-2022-30973 json

Missing fix for CVE-2022-30126 in 1.28.2

published 4y ago modified 4mo ago also GHSA-qw3f-w4pf-jh5f , EUVD-2022-6138

cvss
5.5
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
2.0%
EPSS 2.0% chance of exploitation in 30 days, percentile 80%
public exploits
0
none known

Summary

We failed to apply the fix for CVE-2022-30126 to the 1.x branch in the 1.28.2 release. In Apache Tika, a regular expression in the StandardsText class, used by the StandardsExtractingContentHandler could lead to a denial of service caused by backtracking on a specially crafted file. This only affects users who are running the StandardsExtractingContentHandler, which is a non-standard handler. This is fixed in 1.28.3.

Patch / fix

  • maven org.apache.tika:tika-core 1.28.3
  • apache tika 1.28.3
  • tika Ubuntu Pro 20.04 LTS 1.22-1ubuntu0.1~esm1
  • tika Ubuntu Pro 22.04 LTS 1.22-2ubuntu0.22.04.1~esm1

ubuntu advisories UBUNTU-CVE-2022-30973

Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

  • tika-core Manager Server Module 4.1 1.26-150200.3.8.1
  • tika-core Manager Server Module 4.2 1.26-150300.4.3.1

suse advisories SUSE-SU-2022:3311-1SUSE-SU-2022:3310-1

Is CVE-2022-30973 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2022-30973 updated cvss 3.1

tika-core: incomplete fix for CVE-2022-30126

  • Red Hat BPM Suite 6 tika-core
    affected: no fix planned “Out of support scope”
  • Red Hat Fuse 7 tika-core Red Hat Integration Camel Quarkus 1 tika-core
    affected: no fix available “Fix deferred”
  • Red Hat JBoss BRMS 5 tika-core Red Hat JBoss BRMS 6 tika-core Red Hat JBoss Data Virtualization 6 tika-core Red Hat JBoss Fuse 6 tika-core Red Hat JBoss Fuse Service Works 6 tika-core
    affected: no fix planned “Out of support scope”
  • Red Hat RHINT Camel-K 1.8.1
    fixed: vendor fix RHSA-2022:7257
  • Red Hat build of Quarkus tika-core
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

1.98% chance of exploitation in the next 30 days, higher than 80% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.1 5.5 CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
NVD 2.0 2.6 AV:N/AC:H/Au:N/C:N/I:N/A:P
GitHub 3.1 5.5 CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H

Affected packages

ecosystem package affected fixed in
maven org.apache.tika:tika-core
>=1.17, <1.28.3
1.28.3

Affected products

  • Apache Software Foundation Apache Tika

Classification

Weakness
  • CWE-1333 Inefficient Regular Expression Complexity

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.