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

Maven · 2 releases from 1.1.0 to 1.1.1 · latest org.apache.geode:geode-core is 2.0.4 · checked 18 Nov 2026

Yes: 16 known advisories

Yes. org.apache.geode:geode-core 1.1.1, the last 1.1 release, is affected by 16 known security advisories (2 critical, 8 high, 6 medium), including CVE-2022-37021, CVE-2017-15692, CVE-2022-37022. 1 more affects earlier 1.1.x releases. Upgrade to 1.15.1 or later to fix all of them.

Upgrade with:mvn versions:use-dep-version -Dincludes=org.apache.geode:geode-core -DdepVersion=1.15.1 -DforceVersion=true

Is your project on an affected org.apache.geode:geode-core?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

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.1.1

  • MediumCVE-2022-34870GHSA-373r-9mg8-3jc425 Oct 2022

    Apache Geode vulnerable to Cross-Site Scripting

    Affected
    <1.15.1
    Fixed in
    1.15.1
  • CriticalCVE-2022-37021GHSA-q4q3-r45f-7gwg1 Sept 2022

    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
  • HighCVE-2022-37022GHSA-qf8g-vpwp-65791 Sept 2022

    Apache Geode versions deserialization of untrusted datawhen using JMX over RMI on Java 11

    Affected
    <1.15.0
    Fixed in
    1.15.0
  • MediumCVE-2022-37023GHSA-72x9-48mc-phh61 Sept 2022

    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
  • MediumCVE-2017-9794GHSA-37m3-qp37-x3c617 May 2022

    Apache Geode gfsh query vulnerability

    Affected
    >=1.0.0 <1.2.1
    Fixed in
    1.2.1
  • HighCVE-2017-12622GHSA-h22r-h77w-2g5f14 May 2022

    Apache Geode gfsh authorization vulnerability

    Affected
    >=1.0.0 <1.3.0
    Fixed in
    1.3.0
  • MediumCVE-2017-9796GHSA-q7cp-r6cj-hpf514 May 2022

    Apache Geode OQL bind parameter vulnerability

    Affected
    >=1.0.0 <1.3.0
    Fixed in
    1.3.0
  • HighCVE-2017-15696GHSA-g569-49wg-jx5f14 May 2022

    Apache Geode configuration request authorization vulnerability

    Affected
    >=1.0.0 <1.4.0
    Fixed in
    1.4.0
  • CriticalCVE-2017-15692GHSA-w395-hpq9-7xwr14 May 2022

    Apache Geode unsafe deserialization in TcpServer

    Affected
    >=1.0.0 <1.4.0
    Fixed in
    1.4.0
  • HighCVE-2017-15693GHSA-95m2-p98f-24r514 May 2022

    Apache Geode unsafe deserialization of application objects

    Affected
    >=1.0.0 <1.4.0
    Fixed in
    1.4.0
  • HighCVE-2017-9795GHSA-6m68-3w55-6mx414 May 2022

    Apache Geode OQL method invocation vulnerability

    Affected
    >=1.0.0 <1.3.0
    Fixed in
    1.3.0
  • MediumCVE-2017-9797GHSA-vh98-fqfc-4hj313 May 2022

    Apache Geode vulnerable to Exposure of Sensitive Information

    Affected
    >=1.0.0 <1.2.1
    Fixed in
    1.2.1
  • HighCVE-2017-15695GHSA-jmg4-x4vp-6c6x13 May 2022

    Apache Geode vulnerable to Incorrect Authorization

    Affected
    >=1.0.0 <1.5.0
    Fixed in
    1.5.0
  • HighCVE-2019-10091GHSA-wc4x-4gm2-74j810 Feb 2022

    Apache Geode SSL endpoint verification vulnerability

    Affected
    <1.10.0
    Fixed in
    1.10.0
  • HighCVE-2021-34797GHSA-mw25-f5r2-hpc66 Jan 2022

    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
  • MediumCVE-2017-15694GHSA-p426-qw2p-v95v26 Jun 2019

    Argument Injection in Apache Geode server

    Affected
    <1.9.0
    Fixed in
    1.9.0

Fixed within 1.1.x, affecting earlier releases

  • HighCVE-2017-5649GHSA-2gw6-73wc-x88f17 May 2022

    Apache Geode information disclosure vulnerability

    Affected
    >=1.1.0 <1.1.1
    Fixed in
    1.1.1

Every org.apache.geode:geode-core 1.1.x release

Affected: 1.1.0 to 1.1.1. Latest org.apache.geode:geode-core: 2.0.4.

VersionKnown advisories
org.apache.geode:geode-core 1.1.1CVE-2022-34870, CVE-2022-37021, CVE-2022-37022, CVE-2022-37023, CVE-2017-9794, CVE-2017-12622, CVE-2017-9796, CVE-2017-15696, CVE-2017-15692, CVE-2017-15693, CVE-2017-9795, CVE-2017-9797, CVE-2017-15695, CVE-2019-10091, CVE-2021-34797, CVE-2017-15694
org.apache.geode:geode-core 1.1.0CVE-2022-34870, CVE-2022-37021, CVE-2022-37022, CVE-2022-37023, CVE-2017-5649, CVE-2017-9794, CVE-2017-12622, CVE-2017-9796, CVE-2017-15696, CVE-2017-15692, CVE-2017-15693, CVE-2017-9795, CVE-2017-9797, CVE-2017-15695, CVE-2019-10091, CVE-2021-34797, CVE-2017-15694

Which of your client projects are still on org.apache.geode:geode-core 1.1?

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

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.