Is org.apache.geode:geode-core 1.3 vulnerable?
Maven · 1 release from 1.3.0 to 1.3.0 · latest org.apache.geode:geode-core is 2.0.4 · checked 18 Nov 2026
Yes: 11 known advisories
Yes. org.apache.geode:geode-core 1.3.0, the last 1.3 release, is affected by 11 known security advisories (2 critical, 6 high, 3 medium), including CVE-2022-37021, CVE-2017-15692, CVE-2022-37022. Upgrade to 1.15.1 or later to fix all of them.
mvn versions:use-dep-version -Dincludes=org.apache.geode:geode-core -DdepVersion=1.15.1 -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
Advisories affecting org.apache.geode:geode-core 1.3.0
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 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 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
Which of your client projects are still on org.apache.geode:geode-core 1.3?
NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact org.apache.geode:geode-core version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.
Other org.apache.geode:geode-core versions
- org.apache.geode:geode-core 1.6
- org.apache.geode:geode-core 1.5
- org.apache.geode:geode-core 1.4
- org.apache.geode:geode-core 1.2
- org.apache.geode:geode-core 1.1
- org.apache.geode:geode-core 2.0
- org.apache.geode:geode-core 1.15
- org.apache.geode:geode-core 1.14
- org.apache.geode:geode-core 1.13
- org.apache.geode:geode-core 1.12
- org.apache.geode:geode-core 1.11
- org.apache.geode:geode-core 1.10
- All org.apache.geode:geode-core advisories
Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the Maven registry. Refreshed daily.