CVE-2022-33879 | Incomplete fix and new regex DoS in StandardsExtractingContentHandler

The initial fixes in CVE-2022-30126 and CVE-2022-30973 for regexes in the StandardsExtractingContentHandler were insufficient, and we found a separate, new regex DoS in a different regex in the StandardsExtractingContentHandler. These are now fixed in 1.28.4 and 2.4.1.

Published: 2022-06-27 Last update: 2026-06-17 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2022-33879 is rated Low Risk (39.6/100): CVSS Low severity, with medium exploitation likelihood (EPSS 1.52%). EPSS rose +1.50% over the last day, indicating growing attacker interest. Monitor for updates and reassess as exploit intelligence or EPSS changes.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2022-33879

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 0.03% 1.52% +1.50%
2 2025-11-21 1.17% 0.03% -1.14%
3 2025-11-18 — 1.17% —

Full EPSS history (7 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2022-33879

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
3.3 3.1 LOW
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:L Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:L)
Might cause slowdowns, glitches, or partial disruption—not a full brick.
 1.8 1.4 [email protected]
2.6 2.0 LOW
AV:N/AC:H/Au:N/C:N/I:N/A:P Click to expand
Access vector (AV:N)
Can be exploited remotely over network reachability.
Access complexity (AC:H)
Exploitation requires uncommon or highly specific conditions.
Authentication (AU:N)
No authentication is required.
Confidentiality impact (C:N)
No confidentiality impact.
Integrity impact (I:N)
No integrity impact.
Availability impact (A:P)
Partial availability impact.
 4.9 2.9 [email protected]

Weakness enumeration for CVE-2022-33879

GitHub Security Advisory for CVE-2022-33879

GHSA-6q8v-2hvm-fx37 · Severity: low · Ecosystem: maven — Apache Tika contains incomplete fix for regex DoS

OS Trackers for CVE-2022-33879

vendor priority summary link
debian not yet assigned CVE-2022-33879 not yet assigned priority: Debian including 1 source packages (tika), 2 status rows across 2 suites (bullseye, sid): open 2. https://security-tracker.debian.org/tracker/CVE-2022-33879
suse medium — https://www.suse.com/security/cve/CVE-2022-33879/
ubuntu medium CVE-2022-33879 medium priority: Ubuntu including 1 source packages (tika), 14 status rows across 14 suites (bionic, focal, impish, jammy, kinetic, lunar, mantic, noble, oracular, plucky, questing, trusty, upstream, xenial): ignored 6, needs-triage 4, released 3, DNE 1. https://ubuntu.com/security/CVE-2022-33879

Affected software / configurations for CVE-2022-33879

Vendor Product Version Raw CPE
apache tika < 1.28.4 cpe:2.3:a:apache:tika:*:*:*:*:*:*:*:*
apache tika >= 2.0.0, < 2.4.1 cpe:2.3:a:apache:tika:*:*:*:*:*:*:*:*

References for CVE-2022-33879

cvelogic Threat Intelligence