# CVE-2011-2740: Auth bypass in n/a

> Remote attackers can execute arbitrary code by exploiting improper session termination on unattended workstations using specific Firefox versions.

- **Severity:** Critical 9.3 (`AV:N/AC:M/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:** A user has to click or open something
- **Fix available:** No
- **Published:** 9 Nov 2011
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-vjwc-fmqh-vqcv

## What is CVE-2011-2740?

CVE-2011-2740 is a critical authentication bypass vulnerability in n/a, published on 9 Nov 2011. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

EMC RSA Key Manager (RKM) Appliance 2.7 SP1 before 2.7.1.6, when Firefox 4.x or 5.0 is used, does not properly terminate a user session upon a logout action, which makes it easier for remote attackers to execute arbitrary code by leveraging an unattended workstation.

Weakness: CWE-264

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

It affects 1 product.


Products: Emc Rsa Key Manager Appliance.

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

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

## Is CVE-2011-2740 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2011-2740 is a critical authentication bypass vulnerability in n/a, published on 9 Nov 2011. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2011-2740 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-2011-2740/ (Markdown: https://insights.sbomify.com/CVE-2011-2740/index.md)
```

## Sources

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

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