How severe is CVE-2010-1157?

No CVSS score has been assigned to CVE-2010-1157 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2010-1157?

CVE-2010-1157 affects the following packages: org.apache.tomcat:tomcat (Maven), org.apache.tomcat:tomcat (Maven). Ecosystems affected: Maven.

How do I fix CVE-2010-1157?

Update org.apache.tomcat:tomcat to 5.5.30 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2010-1157 is resolved across your whole dependency graph.

How do I detect CVE-2010-1157 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.tomcat:tomcat, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2010-1157 if there is no patch (or I can't update yet)?

Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

Is CVE-2010-1157 actively exploited in the wild?

Yes. There are 1 known exploit references for CVE-2010-1157, including 1 documented proof-of-concept exploit on Exploit-DB. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2010-1157?

CVE-2010-1157 has an EPSS (Exploit Prediction Scoring System) score of 52.5%, placing it in the 99th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

What type of vulnerability is CVE-2010-1157?

CVE-2010-1157 is classified as Information Exposure (CWE-200). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2010-1157 published, and has it been updated?

CVE-2010-1157 was published on May 2, 2022 and was last updated on November 8, 2023. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕ Maven

Not in CISA KEV

CVE-2010-1157 — tomcat

CVE-2010-1157 is a Information Exposure vulnerability in org.apache.tomcat:tomcat. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for org.apache.tomcat:tomcat — see the affected versions and patch details below.

Exposure of Sensitive Information to an Unauthorized Actor in Apache Tomcat

Published

May 2, 2022

Updated

Nov 8, 2023

Affected

2 pkgs

Patched

2 / 2

Exploits

1 known

Exploitation data as of Nov 6, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

52.5%probability of exploitation in next 30 days

High Risk0.00%

Lower risk than most CVEs99th percentile — riskier than 99% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

2 pkgs affected

☕org.apache.tomcat:tomcat☕org.apache.tomcat:tomcat

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

Apache Tomcat 5.5.0 through 5.5.29 and 6.0.0 through 6.0.26 might allow remote attackers to discover the server's hostname or IP address by sending a request for a resource that requires (1) BASIC or (2) DIGEST authentication, and then reading the realm field in the WWW-Authenticate header in the reply.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.apache.tomcat:tomcat`	≥ 5.5.0&&< 5.5.30	5.5.30`org.apache.tomcat:tomcat:5.5.30`
☕Maven	`org.apache.tomcat:tomcat`	≥ 6.0.0&&< 6.0.28	6.0.28`org.apache.tomcat:tomcat:6.0.28`

Affected Products

1 product · 53 configurations

Application

tomcatapache

53 versions

5.5.05.5.15.5.25.5.35.5.45.5.55.5.65.5.75.5.85.5.95.5.105.5.11

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

EDB-12343remotemultiple✓ Verified

Apache Tomcat 5.5.0 < 5.5.29 / 6.0.0 < 6.0.26 - Information Disclosure

by Deniz Cevik · Apr 22, 2010

Exploit-DB Source

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.tomcat:tomcat, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.apache.tomcat:tomcat to 5.5.30 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2010-1157 is resolved across your whole dependency graph.
Workarounds
Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatLow

The risks associated with fixing this flaw are greater than the low severity security risk. We therefore have no plans to fix this flaw. The information leak can be avoided by adjusting the configuration to always specify a realm-name.

Product	Fixed in	Advisory
JBEAP 4.2.0 for RHEL 5	`jbossweb-0:2.0.0-6.CP14.0jpp.ep1.1.el5`	RHSA-2010:0584
Red Hat JBoss Enterprise Web Server 1 for RHEL 5	`ant-0:1.7.1-13.jdk6.ep5.el5`	RHSA-2011:0897
Red Hat JBoss Web Server 1.0	see advisory	RHSA-2011:0896

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2010-1157 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works