# CVE-2012-2281: Auth bypass in n/a

> Remote attackers can replay session tokens after logout to bypass authentication and take over user accounts in RSA Access Manager.

- **Severity:** Medium 6.8 (`AV:A/AC:H/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Jul 2012
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-7qf5-247v-pcc8

## What is CVE-2012-2281?

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

### Official description

EMC RSA Access Manager Server 6.x before 6.1 SP4 and RSA Access Manager Agent do not properly validate session tokens after a logout, which might allow remote attackers to conduct replay attacks via unspecified vectors.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2012-2281?

It affects 2 products.


Products: Rsa Access Manager Agent, Rsa Access Manager Server.

## How do I fix CVE-2012-2281?

No fix has been published for CVE-2012-2281 yet. Limit exposure of the affected software until one is available.

## Is CVE-2012-2281 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2010-3017](https://insights.sbomify.com/CVE-2010-3017/): Auth bypass in n/a (medium 5.7)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2012-2281 and fix it if it is affected.

What it is: CVE-2012-2281 is a medium-severity authentication bypass vulnerability in n/a, published on 5 Jul 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-2012-2281 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

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

## Sources

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

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