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. 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.

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.

How does O3 Security protect against GHSA-j3ch-vjph-8q6v?

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

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 66th 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

GHSA-j3ch-vjph-8q6v

CRITICAL

GHSA-j3ch-vjph-8q6v is a critical-severity (CVSS 9.8) vulnerability in org.alluxio:alluxio-core-common. O3 Security confirms whether GHSA-j3ch-vjph-8q6v is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Command injection in Alluxio

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 Aug 23, 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 CVEs66th percentile — riskier than 66% of all scored CVEsHighest risk

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.

How urgent is this, really

GHSA-j3ch-vjph-8q6v plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.

Where this sits among everything scored

Of 0 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.

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

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. 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.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.
How O3 protects you
O3 pinpoints whether GHSA-j3ch-vjph-8q6v 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-j3ch-vjph-8q6v. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

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?

O3 detects GHSA-j3ch-vjph-8q6v 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 dependencies How O3 SCA works