CVE-2010-1622: Improper Control of Generation of Code ('Code Injection') in Spring Framework

CVE-2010-1622 · Severity: info · Published 2022-05-17

Improper Control of Generation of Code ('Code Injection') in Spring Framework

Technologies: org.springframework:spring (Maven). Vendors: Maven.

Quick answers

Is CVE-2010-1622 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2010-1622 being exploited in the wild.
How severe is CVE-2010-1622?
Informational severity, published 17 May 2022.
Which products and versions are affected?
org.springframework:spring (Maven) ECOSYSTEM:introduced=2.5.0,fixed=2.5.7.
Is there a fix for CVE-2010-1622?
Yes. org.springframework:spring (Maven): upgrade to 2.5.7 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2010-1622?
Check whether you run org.springframework:spring (Maven) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • org.springframework:spring (Maven): upgrade to 2.5.7 or later
    # set org.springframework:spring to 2.5.7 in your pom.xml or build.gradle

Affected products

  • org.springframework:spring (Maven) ECOSYSTEM:introduced=2.5.0,fixed=2.5.7

Identifiers

  • CVE-2010-1622
  • GHSA-vpr3-f594-mg5g

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.