How severe is GHSA-w395-hpq9-7xwr?

GHSA-w395-hpq9-7xwr has a CVSS score of 9.8/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by GHSA-w395-hpq9-7xwr?

GHSA-w395-hpq9-7xwr affects the following packages: org.apache.geode:geode-core (Maven). Ecosystems affected: Maven.

How do I fix GHSA-w395-hpq9-7xwr?

Update org.apache.geode:geode-core to 1.4.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-w395-hpq9-7xwr is resolved across your whole dependency graph.

How do I detect GHSA-w395-hpq9-7xwr in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.geode:geode-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.

How do I mitigate GHSA-w395-hpq9-7xwr 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-w395-hpq9-7xwr?

O3 pinpoints whether GHSA-w395-hpq9-7xwr 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-w395-hpq9-7xwr actively exploited in the wild?

No public exploit code has been indexed for GHSA-w395-hpq9-7xwr 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 type of vulnerability is GHSA-w395-hpq9-7xwr?

GHSA-w395-hpq9-7xwr 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-w395-hpq9-7xwr published, and has it been updated?

GHSA-w395-hpq9-7xwr was published on May 14, 2022 and was last updated on November 8, 2023. 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-w395-hpq9-7xwr

CRITICAL

GHSA-w395-hpq9-7xwr is a critical-severity (CVSS 9.8) Deserialization of Untrusted Data vulnerability in org.apache.geode:geode-core. O3 Security confirms whether GHSA-w395-hpq9-7xwr is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Apache Geode unsafe deserialization in TcpServer

Also known asCVE-2017-15692

Published

May 14, 2022

Updated

Nov 8, 2023

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Blast Radius

1 pkg affected

☕org.apache.geode:geode-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 Geode before v1.4.0, the TcpServer within the Geode locator opens a network port that deserializes data. If an unprivileged user gains access to the Geode locator, they may be able to cause remote code execution if certain classes are present on the classpath.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.apache.geode:geode-core`	≥ 1.0.0&&< 1.4.0	1.4.0

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.geode:geode-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.geode:geode-core to 1.4.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-w395-hpq9-7xwr 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-w395-hpq9-7xwr 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-w395-hpq9-7xwr. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is GHSA-w395-hpq9-7xwr in your dependencies?

O3 detects GHSA-w395-hpq9-7xwr 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