CVE-2013-6429: Cross-Site Request Forgery in Spring Framework

CVE-2013-6429 · Severity: info · Published 2022-05-13

Cross-Site Request Forgery in Spring Framework

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

Quick answers

Is CVE-2013-6429 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2013-6429 being exploited in the wild.
How severe is CVE-2013-6429?
Informational severity, published 13 May 2022.
Which products and versions are affected?
org.springframework:spring-web (Maven) ECOSYSTEM:introduced=0,fixed=3.2.5.RELEASE.
Is there a fix for CVE-2013-6429?
Yes. org.springframework:spring-web (Maven): upgrade to 3.2.5.RELEASE or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2013-6429?
Check whether you run org.springframework:spring-web (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-web (Maven): upgrade to 3.2.5.RELEASE or later
    # set org.springframework:spring-web to 3.2.5.RELEASE in your pom.xml or build.gradle

Affected products

  • org.springframework:spring-web (Maven) ECOSYSTEM:introduced=0,fixed=3.2.5.RELEASE

Identifiers

  • CVE-2013-6429
  • GHSA-g6hf-f9cq-q7w7

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