org.apache.geode:geode-core vulnerabilities
Apache Geode provides a database-like consistency model, reliable transaction processing and a shared-nothing architecture to maintain very low latency performance with high concurrency processing
- Registry
- Maven
- Latest
- 2.0.4
- License
- The Apache Software License, Version 2.0
17 known advisories
The latest version, 2.0.4, is not affected by any of them. Projects on older versions may be.
mvn versions:use-dep-version -Dincludes=org.apache.geode:geode-core -DdepVersion=2.0.4 -DforceVersion=trueIs your project on an affected org.apache.geode:geode-core?
Look after several Java apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Security advisories for org.apache.geode:geode-core
Apache Geode vulnerable to Cross-Site Scripting
- Affected
- <1.15.1
- Fixed in
- 1.15.1
Apache Geode vulnerable to Deserialization of Untrusted Data
- Affected
- <1.12.16 · >=1.13.0 <1.13.5 · >=1.14.0 <1.14.1
- Fixed in
- 1.12.16, 1.13.5, 1.14.1
Apache Geode versions deserialization of untrusted datawhen using JMX over RMI on Java 11
- Affected
- <1.15.0
- Fixed in
- 1.15.0
Apache Geode versions prior to 1.15.0 are vulnerable to a deserialization of untrusted data
- Affected
- <1.15.0
- Fixed in
- 1.15.0
Apache Geode information disclosure vulnerability
- Affected
- >=1.1.0 <1.1.1
- Fixed in
- 1.1.1
Apache Geode gfsh query vulnerability
- Affected
- >=1.0.0 <1.2.1
- Fixed in
- 1.2.1
Apache Geode gfsh authorization vulnerability
- Affected
- >=1.0.0 <1.3.0
- Fixed in
- 1.3.0
Apache Geode OQL bind parameter vulnerability
- Affected
- >=1.0.0 <1.3.0
- Fixed in
- 1.3.0
Apache Geode configuration request authorization vulnerability
- Affected
- >=1.0.0 <1.4.0
- Fixed in
- 1.4.0
Apache Geode unsafe deserialization in TcpServer
- Affected
- >=1.0.0 <1.4.0
- Fixed in
- 1.4.0
Apache Geode unsafe deserialization of application objects
- Affected
- >=1.0.0 <1.4.0
- Fixed in
- 1.4.0
Apache Geode OQL method invocation vulnerability
- Affected
- >=1.0.0 <1.3.0
- Fixed in
- 1.3.0
Apache Geode vulnerable to Exposure of Sensitive Information
- Affected
- >=1.0.0 <1.2.1
- Fixed in
- 1.2.1
Apache Geode vulnerable to Incorrect Authorization
- Affected
- >=1.0.0 <1.5.0
- Fixed in
- 1.5.0
Apache Geode SSL endpoint verification vulnerability
- Affected
- <1.10.0
- Fixed in
- 1.10.0
Insertion of Sensitive Information into Log File in Apache Geode
- Affected
- <1.12.5 · >=1.13.0 <1.13.5
- Fixed in
- 1.12.5, 1.13.5
Argument Injection in Apache Geode server
- Affected
- <1.9.0
- Fixed in
- 1.9.0
Is your org.apache.geode:geode-core version vulnerable?
- org.apache.geode:geode-core 2.0No known advisories in 2.0.4
- org.apache.geode:geode-core 1.15No known advisories in 1.15.6
- org.apache.geode:geode-core 1.143 advisories in 1.14.4
- org.apache.geode:geode-core 1.133 advisories in 1.13.8
- org.apache.geode:geode-core 1.124 advisories in 1.12.9
- org.apache.geode:geode-core 1.115 advisories in 1.11.0
- org.apache.geode:geode-core 1.105 advisories in 1.10.0
Which of your client projects still run an old org.apache.geode:geode-core?
NPMscan reads the pom.xml, build.gradle and gradle.lockfile in every GitHub repo you pick and checks each installed version against these advisories, including the packages your packages pull in. Each finding comes with the command that fixes it.
Other Maven packages
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily. Package details from the Maven registry.