How severe is GHSA-mw25-f5r2-hpc6?

No CVSS score has been assigned to GHSA-mw25-f5r2-hpc6 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-mw25-f5r2-hpc6?

GHSA-mw25-f5r2-hpc6 affects the following packages: org.apache.geode:geode-core (Maven), org.apache.geode:geode-core (Maven). Ecosystems affected: Maven.

How do I fix GHSA-mw25-f5r2-hpc6?

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

How do I detect GHSA-mw25-f5r2-hpc6 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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-mw25-f5r2-hpc6 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-mw25-f5r2-hpc6 actively exploited in the wild?

No public exploit code has been indexed for GHSA-mw25-f5r2-hpc6 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-mw25-f5r2-hpc6?

GHSA-mw25-f5r2-hpc6 has an EPSS (Exploit Prediction Scoring System) score of 2.5%, placing it in the 84th 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.

What type of vulnerability is GHSA-mw25-f5r2-hpc6?

GHSA-mw25-f5r2-hpc6 is classified as CWE-532 (CWE-532). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-mw25-f5r2-hpc6 published, and has it been updated?

GHSA-mw25-f5r2-hpc6 was published on January 6, 2022 and was last updated on December 4, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

Insertion of Sensitive Information into Log File in Apache…

EPSS Exploitation Probability

via FIRST.org ↗

2.5%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs84th percentile — riskier than 84% of all scored CVEsHighest risk

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

Real-World Exposure

2 pkgs affected

☕org.apache.geode:geode-core☕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

Apache Geode versions up to 1.12.4 and 1.13.4 are vulnerable to a log file redaction of sensitive information flaw when using values that begin with characters other than letters or numbers for passwords and security properties with the prefix "sysprop-", "javax.net.ssl", or "security-". This issue is fixed by overhauling the log file redaction in Apache Geode versions 1.12.5, 1.13.5, and 1.14.0.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.apache.geode:geode-core`	all versions	1.12.5`org.apache.geode:geode-core:1.12.5`
☕Maven	`org.apache.geode:geode-core`	≥ 1.13.0&&< 1.13.5	1.13.5`org.apache.geode:geode-core:1.13.5`

Affected Products

1 product · 2 configurations

Application

geodeapache

≥ 1.13.0 && ≤ 1.13.4

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.apache.geode:geode-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.apache.geode:geode-core to 1.12.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-mw25-f5r2-hpc6 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

Apache Geode versions up to 1.12.4 and 1.13.4 are vulnerable to a log file redaction of sensitive information flaw when using values that begin with characters other than letters or numbers for passwords and security properties with the prefix "sysprop-", "javax.net.ssl", or "security-". This issue is fixed by overhauling the log file redaction in Apache Geode versions 1.12.5, 1.13.5, and 1.14.0.

O3 Security · Impact-Aware SCA

Is GHSA-mw25-f5r2-hpc6 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works

Insertion of Sensitive Information into Log File in Apache GeodeGHSA-mw25-f5r2-hpc6