# CVE-2011-2732: Improper Control of Generation of Code in Spring Security

> Remote attackers can inject HTTP headers and split responses via the logout redirect parameter in Spring Security.

- **Severity:** Medium 4.3 (`AV:N/AC:M/Au:N/C:N/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 5 Dec 2012
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-5xm9-rf63-wj7h

## What is CVE-2011-2732?

CVE-2011-2732 is a medium-severity vulnerability in n/a, published on 5 Dec 2012. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-94 (Improper Control of Generation of Code)

## Which versions are affected by CVE-2011-2732?

4 open source packages ship an affected version, including org.springframework.security:spring-security-core. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.springframework.security:spring-security-core` | Maven | All versions | 2.0.7 |
| `org.springframework.security:spring-security-core` | Maven | All versions | 2.0.7 |
| `org.springframework.security:spring-security-core` | Maven | From 3.0.0 | 3.0.6 |
| `org.springframework.security:spring-security-core` | Maven | From 3.0.0 | 3.0.6 |

Products: Vmware Springsource Spring Security.

## How do I fix CVE-2011-2732?

Upgrade org.springframework.security:spring-security-core to a fixed version for your release line: 2.0.7 or 3.0.6.

## Is CVE-2011-2732 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2011-2732 exists.

Public exploit code:

- Spring Security - HTTP Header Injection (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2011-2731](https://insights.sbomify.com/CVE-2011-2731/): Concurrent Execution using Shared Resource with Improper Synchronization in Spring Security (medium 5.1)
- [CVE-2012-5055](https://insights.sbomify.com/CVE-2012-5055/): Exposure of Sensitive Information to an Unauthorized Actor in Spring Security (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2011-2732 and fix it if it is affected.

What it is: CVE-2011-2732 is a medium-severity vulnerability in n/a, published on 5 Dec 2012. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2011-2732 exists.

Affected packages and fixed versions:
- org.springframework.security:spring-security-core (Maven): affected all versions; fixed in 2.0.7
- org.springframework.security:spring-security-core (Maven): affected all versions; fixed in 2.0.7
- org.springframework.security:spring-security-core (Maven): affected from 3.0.0; fixed in 3.0.6
- org.springframework.security:spring-security-core (Maven): affected from 3.0.0; fixed in 3.0.6

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2011-2732/ (Markdown: https://insights.sbomify.com/CVE-2011-2732/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2011-2732
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2011-2732
- OSV: https://osv.dev/vulnerability/CVE-2011-2732

---
From sbomify Insights: https://insights.sbomify.com/CVE-2011-2732/
Summaries are generated and may contain mistakes; the official description above is the record.