Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Maven

GHSA-wxcp-f2c8-x6xv

MEDIUM

GHSA-wxcp-f2c8-x6xv is a medium-severity (CVSS 5.9) CWE-203 vulnerability in org.apache.tomcat:tomcat. O3 Security confirms whether GHSA-wxcp-f2c8-x6xv is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Observable Discrepancy in Apache Tomcat

Also known asCVE-2016-0762
Published
May 13, 2022
Updated
Mar 11, 2024
Affected
5 pkgs
Patched
5 / 5
Exploits
None indexed

Blast Radius

5 pkgs affected
org.apache.tomcat:tomcatorg.apache.tomcat:tomcatorg.apache.tomcat:tomcatorg.apache.tomcat:tomcatorg.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

The Realm implementations in Apache Tomcat versions 9.0.0.M1 to 9.0.0.M9, 8.5.0 to 8.5.4, 8.0.0.RC1 to 8.0.36, 7.0.0 to 7.0.70 and 6.0.0 to 6.0.45 did not process the supplied password if the supplied user name did not exist. This made a timing attack possible to determine valid user names. Note that the default configuration includes the LockOutRealm which makes exploitation of this vulnerability harder.

Affected Packages

5 total 5 fixed
EcosystemPackageVulnerable rangeFix
Mavenorg.apache.tomcat:tomcat9.0.0M1&&< 9.0.0.M109.0.0.M10
Mavenorg.apache.tomcat:tomcat8.5.0&&< 8.5.58.5.5
Mavenorg.apache.tomcat:tomcat8.0.0.RC1&&< 8.0.378.0.37
Mavenorg.apache.tomcat:tomcat7.0.0&&< 7.0.727.0.72
Mavenorg.apache.tomcat:tomcat6.0.0&&< 6.0.466.0.46

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.tomcat:tomcat. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Fix

    Update org.apache.tomcat:tomcat to 9.0.0.M10 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-wxcp-f2c8-x6xv is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 pinpoints whether GHSA-wxcp-f2c8-x6xv is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-wxcp-f2c8-x6xv. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

The Realm implementations in Apache Tomcat versions 9.0.0.M1 to 9.0.0.M9, 8.5.0 to 8.5.4, 8.0.0.RC1 to 8.0.36, 7.0.0 to 7.0.70 and 6.0.0 to 6.0.45 did not process the supplied password if the supplied user name did not exist. This made a timing attack possible to determine valid user names. Note that the default configuration includes the LockOutRealm which makes exploitation of this vulnerability harder.
O3 Security · Impact-Aware SCA

Is GHSA-wxcp-f2c8-x6xv in your dependencies?

O3 detects GHSA-wxcp-f2c8-x6xv across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.