How severe is GHSA-j3ch-vjph-8q6v?

GHSA-j3ch-vjph-8q6v has a CVSS score of 9.8/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by GHSA-j3ch-vjph-8q6v?

GHSA-j3ch-vjph-8q6v affects the following packages: org.alluxio:alluxio-core-common (Maven). Ecosystems affected: Maven.

How do I fix GHSA-j3ch-vjph-8q6v?

Update org.alluxio:alluxio-core-common to 2.7.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-j3ch-vjph-8q6v is resolved across your whole dependency graph.

How do I detect GHSA-j3ch-vjph-8q6v in my Maven dependencies?

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

How do I mitigate GHSA-j3ch-vjph-8q6v if there is no patch (or I can't update yet)?

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.

Is GHSA-j3ch-vjph-8q6v actively exploited in the wild?

No public exploit code has been indexed for GHSA-j3ch-vjph-8q6v yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-j3ch-vjph-8q6v?

GHSA-j3ch-vjph-8q6v has an EPSS (Exploit Prediction Scoring System) score of 1.2%, placing it in the 68th 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. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

When was GHSA-j3ch-vjph-8q6v published, and has it been updated?

GHSA-j3ch-vjph-8q6v was published on February 21, 2022 and was last updated on December 5, 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

Not in CISA KEV

CRITICAL severity

Command injection in AlluxioGHSA-j3ch-vjph-8q6v

CRITICAL

GHSA-j3ch-vjph-8q6v is a critical-severity (CVSS 9.8) vulnerability in org.alluxio:alluxio-core-common. A fix is available for org.alluxio:alluxio-core-common — see the affected versions and patch details below.

Also known asCVE-2022-23848

Published

Feb 21, 2022

Updated

Dec 5, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

1.2%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs68th percentile — riskier than 68% of all scored CVEsHighest risk

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

How urgent is this, really

GHSA-j3ch-vjph-8q6v by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 385,738 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

1 pkg affected

☕org.alluxio:alluxio-core-common

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 Alluxio before 2.7.3, the logserver does not validate the input stream. NOTE: this is not the same as the CVE-2021-44228 Log4j vulnerability.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.alluxio:alluxio-core-common`	all versions	2.7.3`org.alluxio:alluxio-core-common:2.7.3`

Affected Products

1 product · 1 configurations

Application

alluxioalluxio

< 2.7.3

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.alluxio:alluxio-core-common, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.alluxio:alluxio-core-common to 2.7.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-j3ch-vjph-8q6v 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.

Frequently Asked Questions

In Alluxio before 2.7.3, the logserver does not validate the input stream. NOTE: this is not the same as the CVE-2021-44228 Log4j vulnerability.

O3 Security · Impact-Aware SCA

Is GHSA-j3ch-vjph-8q6v in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works