VulertSecurity VulertSecurity

Vulnerability Database · Maven · org.apache.geode:geode-core · Version

org.apache.geode:geode-core 1.2.0

1.2.0 is affected by 16 vulnerabilities.

The vulnerabilities that cover this exact version are listed below with the fixed version to move to. The upgrade Vulert recommends: 2.0.3.

Critical 2 High 8 Medium 6 Low 0 Unrated 0

All org.apache.geode:geode-core versions & vulnerabilities → Source repository Search the database for this package →
Released 12 Jul 2017 Licence Apache-2.0 Also known from other sources 16 Newer releases 52 Database updated 23/Oct/2026

Release and licence data published by Maven Central. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Vulnerabilities affecting this version

org.apache.geode:geode-core 1.2.0 vulnerabilities

16 vulnerabilities cover org.apache.geode:geode-core 1.2.0. Scroll the table for all of them, or open the full list in the database.

Vulnerability Severity Fixed version Disclosed
CVE-2022-37021: Apache Geode Deserialization of Untrusted Data 9.8 critical 1.12.16 01 Sep 2022
CVE-2017-15692: Apache Geode unsafe deserialization in TcpServer 9.8 critical 1.4.0 14 May 2022
CVE-2022-37022: Apache Geode - Deserialization of Untrusted Data in JMX over RMI on Java 11 8.8 high 1.15.0 01 Sep 2022
CVE-2017-15695: Apache Geode Incorrect Authorization 8.8 high 1.5.0 13 May 2022
CVE-2017-15696: Apache Geode configuration request authorization vulnerability 7.5 high 1.4.0 14 May 2022
CVE-2017-15693: Apache Geode unsafe deserialization of application objects 7.5 high 1.4.0 14 May 2022
CVE-2017-9795: Apache Geode OQL method invocation vulnerability in org.apache.geode:geode-core 7.5 high 1.3.0 14 May 2022
CVE-2019-10091: Improper Certificate Validation in Apache Geode 7.4 high 1.10.0 10 Feb 2022
CVE-2017-12622: Apache Geode gfsh authorization vulnerability 7.1 high 1.3.0 14 May 2022
CVE-2022-37023: Apache Geode - Deserialization of Untrusted Data 6.5 medium 1.15.0 01 Sep 2022
CVE-2017-9797: Apache Geode Exposure of Sensitive Information 6.5 medium 1.2.1 13 May 2022
CVE-2017-15694: Argument Injection in Apache Geode server 6.5 medium 1.9.0 26 Jun 2019
CVE-2022-34870: Apache Geode Cross-Site Scripting Vulnerability 5.4 medium 1.15.1 25 Oct 2022
CVE-2017-9796: Apache Geode OQL bind parameter vulnerability in org.apache.geode:geode-core 5.3 medium 1.3.0 14 May 2022
CVE-2017-9794: Apache Geode gfsh query vulnerability 4.3 medium 1.2.1 17 May 2022
CVE-2021-34797: Insertion of Sensitive Information into Log File in Apache Geode N/A high 1.12.5 06 Jan 2022

Looking for another version, or everything Vulert holds for org.apache.geode:geode-core?

All versions → Full vulnerability list →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About org.apache.geode:geode-core 1.2.0

Is org.apache.geode:geode-core 1.2.0 vulnerable?

Yes. 16 vulnerabilities in the Vulert database cover org.apache.geode:geode-core 1.2.0: 2 critical, 8 high, 6 medium and 0 low. The upgrade Vulert recommends is 2.0.3, and each entry above names the fixed version to move to.

Which version of org.apache.geode:geode-core should I use instead of 1.2.0?

2.0.3 is the version Vulert recommends for this release line. The version table on the package page lists every release with the vulnerabilities recorded against it.

Is 1.2.0 the latest release of org.apache.geode:geode-core?

No. 1.2.0 was published 12 Jul 2017, and newer releases exist. Newer is not automatically safer — the version table on the package page shows what each release carries.

How do I monitor org.apache.geode:geode-core for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the org.apache.geode:geode-core version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.