# CVE-2011-2731: Concurrent Execution using Shared Resource with Improper Synchronization in Spring Security

> A race condition in Spring Security allows attackers to gain privileges by exploiting shared authentication contexts in concurrent threads.

- **Severity:** Medium 5.1 (`AV:N/AC:H/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 5 Dec 2012
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-4644-hg35-55m9

## What is CVE-2011-2731?

CVE-2011-2731 is a medium-severity vulnerability in n/a, published on 5 Dec 2012. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Race condition in the RunAsManager mechanism in VMware SpringSource Spring Security before 2.0.7 and 3.0.x before 3.0.6 stores the Authentication object in the shared security context, which allows attackers to gain privileges via a crafted thread.

Weakness: CWE-362 (Concurrent Execution using Shared Resource with Improper Synchronization)

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

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-2731?

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-2731 being exploited?

There is no known exploitation of CVE-2011-2731 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2012-5055](https://insights.sbomify.com/CVE-2012-5055/): Exposure of Sensitive Information to an Unauthorized Actor in Spring Security (medium 5.0)
- [CVE-2011-2732](https://insights.sbomify.com/CVE-2011-2732/): Improper Control of Generation of Code in Spring Security (medium 4.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2011-2731 is a medium-severity vulnerability in n/a, published on 5 Dec 2012. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2011-2731 in the wild and no public exploit code.

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-2731/ (Markdown: https://insights.sbomify.com/CVE-2011-2731/index.md)
```

## Sources

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

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