GHSA-vp98-w2p3-mv35
HIGHGHSA-vp98-w2p3-mv35 is a high-severity (CVSS 7.5) Deserialization of Untrusted Data vulnerability in org.apache.logging.log4j:log4j-core. O3 Security confirms whether GHSA-vp98-w2p3-mv35 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Apache Log4j 1.x (EOL) allows Denial of Service (DoS)
Blast Radius
org.apache.logging.log4j:log4j-core☕log4j:log4jReal-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
** UNSUPPORTED WHEN ASSIGNED ** When using the Chainsaw or SocketAppender components with Log4j 1.x on JRE less than 1.7, an attacker that manages to cause a logging entry involving a specially-crafted (ie deeply nested) hashmap or hashtable (depending on which logging component is in use) to be processed could exhaust the available memory in the virtual machine and achieve Denial of Service when the object is deserialized. This issue affects Apache Log4j before 2. Affected users are recommended to update to Log4j 2.x. NOTE: This vulnerability only affects products that are no longer supported by the maintainer.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.apache.logging.log4j:log4j-core | ≥ 1.0.4&&< 2.0 | 2.0 |
| ☕Maven | log4j:log4j | ≥ 1.0.4&&< 2.0 | 2.0 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.logging.log4j:log4j-core. 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.
Fix
Update org.apache.logging.log4j:log4j-core to 2.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-vp98-w2p3-mv35 is resolved across your whole dependency graph.
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.
How O3 protects you
O3 pinpoints whether GHSA-vp98-w2p3-mv35 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-vp98-w2p3-mv35. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-vp98-w2p3-mv35 in your dependencies?
O3 detects GHSA-vp98-w2p3-mv35 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.