NVD / CVE Program· CNA apache

CVE-2022-29885: EncryptInterceptor does not provide complete protection on insecure networks

Noroxi assessment

Priority: Plan (action score 52/100)

Public proof-of-concept code exists (Exploit-DB, GitHub); there is no record of exploitation in the wild.
Probability of exploitation in the next 30 days: 73.4% (FIRST EPSS); higher than 99.4% of all records.
Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
According to CISA the attack is automatable: targets can be found by mass scanning.
Fixed version: tomcat9 (Debian:10) 9.0.31-1~deb10u7; tomcat9 (Debian:11) 9.0.43-2~deb11u4; tomcat9 (Debian:12) 9.0.63-1.

Add it to your regular patch cycle. Upgrade to tomcat9 (Debian:10) 9.0.31-1~deb10u7; tomcat9 (Debian:11) 9.0.43-2~deb11u4; tomcat9 (Debian:12) 9.0.63-1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

The documentation of Apache Tomcat 10.1.0-M1 to 10.1.0-M14, 10.0.0-M1 to 10.0.20, 9.0.13 to 9.0.62 and 8.5.38 to 8.5.78 for the EncryptInterceptor incorrectly stated it enabled Tomcat clustering to run over an untrusted network. This was not correct. While the EncryptInterceptor does provide confidentiality and integrity protection, it does not protect against all risks associated with running over any untrusted network, particularly DoS risks.

HighCVSS 7.5 · v3.1—Proof of concept Fix available

Published: May 12, 2022
Updated: Oct 8, 2026
EPSS: 73.4% · 99th percentile
CWE: CWE-400

Report tools

JSON

Action score

Plan

Add it to your regular patch cycle.

CVSS: 30 / 40 · 7.5 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 22 / 30 · 73.4%

CISA SSVC decision

Exploitation: none
Automatable: yes
Technical impact: partial

Vulnrichment: CISA's decision-tree inputs.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
Proof of concept exists, no weaponized module
A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
apache	tomcat	cpe:2.3:a:apache:tomcat
debian	debian linux	cpe:2.3:o:debian:debian_linux
oracle	hospitality cruise shipboard property management system	cpe:2.3:a:oracle:hospitality_cruise_shipboard_property_management_system

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

apache tomcat8.5.38 and later · up to 8.5.78 inclusive
apache tomcat9.0.13 and later · up to 9.0.62 inclusive
apache tomcat10.0.0 and later · up to 10.0.20 inclusive
apache tomcat10.1.0
debian debian linux10.0
debian debian linux11.0
oracle hospitality cruise shipboard property management system20.2.1

Versions reported by the vendor

Affected version ranges reported by the assigning authority (apache). Independent of NVD's CPE analysis and usually ahead of it.

Apache Software Foundation Apache Tomcat
- Apache Tomcat 10.1 10.1.0-M1 to 10.1.0-M14, Apache Tomcat 10 10.0.0-M1 to 10.0.20, Apache Tomcat 9 9.0.13 to 9.0.62, Apache Tomcat 8.5 8.5.38 to 8.5.78affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

Ecosystem	Package	Affected range	Fix
Debian:10	tomcat9	before 9.0.31-1~deb10u7	9.0.31-1~deb10u7
Debian:11	tomcat9	before 9.0.43-2~deb11u4	9.0.43-2~deb11u4
Debian:12	tomcat9	before 9.0.63-1	9.0.63-1
Maven	org.apache.tomcat:tomcat	from 10.0.0-M1 · before 10.0.21	10.0.21
Maven	org.apache.tomcat:tomcat	from 10.1.0-M1 · before 10.1.0-M15	10.1.0-M15
Maven	org.apache.tomcat:tomcat	from 8.5.38 · before 8.5.79	8.5.79
Maven	org.apache.tomcat:tomcat	from 9.0.13 · before 9.0.63	9.0.63

Same product

apache: all records

Other highest-scoring records for the same primary product.

CVE-2025-24813Apache Tomcat: Potential RCE and/or information disclosure and/or information corruption with partial PUTKEV
99Now
CVE-2016-8735Remote code execution is possible with Apache Tomcat before 6.0.48, 7.x before 7.0.73, 8.x before 8.0.39, 8.5.x before 8.5.7, and 9.x beforeKEV
96Now
CVE-2017-12617When running Apache Tomcat versions 9.0.0.M1 to 9.0.0, 8.5.0 to 8.5.22, 8.0.0.RC1 to 8.0.46 and 7.0.0 to 7.0.81 with HTTP PUTs enabled (e.g.KEV
92Now

Published before and after this one in the same product

← EarlierCVE-2021-42340Oct 14, 2021 · DoS via memory leak with WebSocket connections
34Monitor
← EarlierCVE-2022-23181Jan 27, 2022 · Local privilege escalation with FileStore
28Monitor
Later →CVE-2022-25762May 13, 2022 · Response mix-up with WebSocket concurrent send and close
37Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / package	Fixed version	Source
debian:tomcat9	9.0.63-1 · Debian:12	Package registry (OSV)
Maven:org.apache.tomcat:tomcat	10.0.21	Package registry (OSV)
Maven:org.apache.tomcat:tomcat	10.1.0-M15	Package registry (OSV)
Maven:org.apache.tomcat:tomcat	8.5.79	Package registry (OSV)
Maven:org.apache.tomcat:tomcat	9.0.63	Package registry (OSV)

Exploit status

Proof of concept available

A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.

Evidence

Exploit-DB entry ×1
Proof-of-concept repository on GitHub ×2

Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.

Public exploit evidence
Source	Kind	Date
Exploit-DB entry	dos	2023-04-05
Proof-of-concept repository on GitHub	stars:5	2022-06-30
Proof-of-concept repository on GitHub	stars:4	2022-07-01

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

PublishedMay 12, 2022
First PoCJun 30, 2022+49 d
TodayNov 6, 2026+1639 d

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

This issue was reported to the Apache Tomcat Security team by 4ra1n.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

Anyone who can reach it over the internet can trigger it.
No account or password is required.
No user action is required.
No special conditions are required; it is repeatable.

If successful

Confidentiality: none
Integrity: none
Availability: high · the service can be disrupted

Attack vector: Network
Attack complexity: Low
Privileges required: None
User interaction: None
Scope: Unchanged
Confidentiality impact: None
Integrity impact: None
Availability impact: High

Weakness class (CWE)

CWE-400 · Uncontrolled Resource Consumption

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

nvd-primary

Root cause

Code that parses nested structures sets no depth or size limit. A small input can turn into a disproportionate processing load.

The bug in code

The whole CWE-400 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

1function expand(node) {
2  return node.children.map(expand);
3}

Fixed

1const MAX_DEPTH = 32;
2function expand(node, depth = 0) {
3  if (depth > MAX_DEPTH) throw new Error("too deep");
4  return node.children.map((c) => expand(c, depth + 1));
5}