GHSA-mw25-f5r2-hpc6 CVE-2021-34797
Insertion of Sensitive Information into Log File in Apache Geode
- Severity
- High
- The publisher's own rating, not a CVSS score
- Exploit chance (EPSS)
- 2.60%
- Chance of exploitation in the next 30 days. Higher than 85.33% of scored vulnerabilities.
- Known exploited
- No
- Not in CISA's catalog
- Weakness
- CWE-532 Insertion of Sensitive Information into Log File
- Fix
1.12.5- Upgrade org.apache.geode:geode-core to this version or later
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 versions
Maven
| Package | Vulnerable | Fixed in |
|---|---|---|
| org.apache.geode:geode-core | < 1.12.5 |
1.12.5 |
| org.apache.geode:geode-core | >= 1.13.0, < 1.13.5 |
1.13.5 |
How to fix
Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.
org.apache.geode:geode-core Maven → 1.12.5
- maven
<dependency><groupId>org.apache.geode</groupId><artifactId>geode-core</artifactId><version>1.12.5</version></dependency>- gradle
implementation("org.apache.geode:geode-core:1.12.5")
Weakness
CWE-532: Insertion of Sensitive Information into Log File
The product writes sensitive information to a log file.
How to prevent it
- Architecture and Design, Implementation: Consider seriously the sensitivity of the information written into log files. Do not write secrets into the log files.
- Distribution: Remove debug log files before deploying the application into production.
- Operation: Protect log files against unauthorized read/write.
- Implementation: Adjust configurations appropriately when software is transitioned from a debug state to production.
References
Advisories
Packages
Other links
Timeline
- Published
- Last updated by the source
- Latest EPSS score
Related advisories
| Advisory | Severity | Why it's related |
|---|---|---|
| GHSA-373r-9mg8-3jc4 Apache Geode vulnerable to Cross-Site Scripting | Medium | Also affects org.apache.geode:geode-core |
| GHSA-qf8g-vpwp-6579 Apache Geode versions deserialization of untrusted datawhen using JMX over RMI on Java 11 | High | Also affects org.apache.geode:geode-core |
| GHSA-q4q3-r45f-7gwg Apache Geode vulnerable to Deserialization of Untrusted Data | Critical | Also affects org.apache.geode:geode-core |
| GHSA-72x9-48mc-phh6 Apache Geode versions prior to 1.15.0 are vulnerable to a deserialization of untrusted data | Medium | Also affects org.apache.geode:geode-core |
| GHSA-2gw6-73wc-x88f Apache Geode information disclosure vulnerability | High | Also affects org.apache.geode:geode-core |
| GHSA-37m3-qp37-x3c6 Apache Geode gfsh query vulnerability | Medium | Also affects org.apache.geode:geode-core |
| GHSA-h22r-h77w-2g5f Apache Geode gfsh authorization vulnerability | High | Also affects org.apache.geode:geode-core |
| GHSA-q7cp-r6cj-hpf5 Apache Geode OQL bind parameter vulnerability | Medium | Also affects org.apache.geode:geode-core |
MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.
Check your repos with MergeHarbor