How severe is GHSA-fxph-q3j8-mv87?

GHSA-fxph-q3j8-mv87 has a CVSS score of 9.8/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by GHSA-fxph-q3j8-mv87?

GHSA-fxph-q3j8-mv87 affects the following packages: org.apache.logging.log4j:log4j (Maven), org.apache.logging.log4j:log4j-core (Maven). Ecosystems affected: Maven.

How do I fix GHSA-fxph-q3j8-mv87?

Update org.apache.logging.log4j:log4j to version 2.8.2 or later. Run your dependency manager's update command and verify no transitive dependencies pin the vulnerable version. Use O3 Security's SCA scanner to confirm the fix is applied across your entire dependency tree.

Is GHSA-fxph-q3j8-mv87 actively exploited in the wild?

Yes. There are 4 known exploit references for GHSA-fxph-q3j8-mv87, including 2 in-the-wild exploitations observed on GitHub and other sources. 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 GHSA-fxph-q3j8-mv87?

GHSA-fxph-q3j8-mv87 has an EPSS (Exploit Prediction Scoring System) score of 93.9%, placing it in the 100th 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 GHSA-fxph-q3j8-mv87?

GHSA-fxph-q3j8-mv87 is classified as Deserialization of Untrusted Data (CWE-502). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was GHSA-fxph-q3j8-mv87 published, and has it been updated?

GHSA-fxph-q3j8-mv87 was published on January 6, 2020 and was last updated on March 14, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕ Maven

GHSA-fxph-q3j8-mv87

CRITICAL

Deserialization of Untrusted Data in Log4j

Also known asCVE-2017-5645

Published

Jan 6, 2020

Updated

Mar 14, 2024

Affected

2 pkgs

Patched

2 / 2

Exploits

4 known

EPSS Exploitation Probability

via FIRST.org ↗

93.9%probability of exploitation in next 30 days

Very High Risk100th percentile-0.10%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

2 pkgs affected

☕org.apache.logging.log4j:log4j☕org.apache.logging.log4j:log4j-core

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

In Apache Log4j 2.x before 2.8.2, when using the TCP socket server or UDP socket server to receive serialized log events from another application, a specially crafted binary payload can be sent that, when deserialized, can execute arbitrary code.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.apache.logging.log4j:log4j`	≥ 2.0&&< 2.8.2	2.8.2
☕Maven	`org.apache.logging.log4j:log4j-core`	≥ 2.0&&< 2.8.2	2.8.2

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.

In Apache Log4j 2.x before 2.8.2, when using the TCP socket server or UD…

github.comGithubAug 2017

In Apache Log4j 2.x before 2.8.2, when using the TCP socket server or UD…

github.comGithubDec 2021

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is GHSA-fxph-q3j8-mv87 in your stack?

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

Scan my stack How O3 SCA works