Skip to content
Fencer Intel
medium 4.3

CVE-2011-2732 json

Improper Control of Generation of Code in Spring Security

published 2012-12-05 13 y ago modified 2026-06-16 4 mo ago also GHSA-5xm9-rf63-wj7h , EUVD-2022-2679

cvss
4.3
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
4.6%
EPSS 4.6% chance of exploitation in 30 days, percentile 91%
public exploits
1
Exploit-DB

Summary

CRLF injection vulnerability in the logout functionality in VMware SpringSource Spring Security before 2.0.7 and 3.0.x before 3.0.6 allows remote attackers to inject arbitrary HTTP headers and conduct HTTP response splitting attacks via the spring-security-redirect parameter.

Patch / fix

  • maven org.springframework.security:spring-security-core 2.0.7, 3.0.6

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2011-2732 updated cvss 4.3

Security: Header injection flaw due improper use of 'spring-security-redirect' parameter

  • Red Hat JBoss BRMS 5 unspecified unspecified
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Timeline

  1. First public exploit (EDB-36130)
  2. Published

Exploit prediction

4.65% chance of exploitation in the next 30 days, higher than 91% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • EDB-36130 Spring Security - HTTP Header Injection remote, 2011-09-09

CVSS scores

assigned by version score vector
NVD 2.0 4.3 AV:N/AC:M/Au:N/C:N/I:P/A:N

Affected packages

ecosystem package affected fixed in
maven org.springframework.security:spring-security-core
<2.0.7
>=3.0.0, <3.0.6
2.0.7
3.0.6

Classification

Weakness
  • CWE-94 Improper Control of Generation of Code
Technology feeds

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.