Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Maven

CVE-2024-22871

HIGH

CVE-2024-22871 is a high-severity (CVSS 7.5) Deserialization of Untrusted Data vulnerability in org.clojure:clojure. O3 Security confirms whether CVE-2024-22871 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Reading specially crafted serializable objects from an untrusted source may cause an infinite loop and denial of service

Also known asGHSA-vr64-r9qj-h27f
Published
Feb 29, 2024
Updated
Jul 15, 2026
Affected
2 pkgs
Patched
2 / 2
Exploits
None indexed

Blast Radius

2 pkgs affected
org.clojure:clojureorg.clojure:clojure

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

An issue in Clojure versions 1.20 to 1.12.0-alpha5 allows an attacker to cause a denial of service (DoS) via the clojure.core$partial$fn__5920 function.

Affected Packages

2 total 2 fixed
EcosystemPackageVulnerable rangeFix
Mavenorg.clojure:clojure1.7.0&&< 1.11.21.11.2
Mavenorg.clojure:clojure1.12.0-alpha1&&< 1.12.0-alpha91.12.0-alpha9

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.clojure:clojure. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Fix

    Update org.clojure:clojure to 1.11.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-22871 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 pinpoints whether CVE-2024-22871 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to CVE-2024-22871. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

An issue in Clojure versions 1.20 to 1.12.0-alpha5 allows an attacker to cause a denial of service (DoS) via the clojure.core$partial$fn__5920 function.
O3 Security · Impact-Aware SCA

Is CVE-2024-22871 in your dependencies?

O3 detects CVE-2024-22871 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.