# CVE-2011-4141: Privilege escalation in n/a

> Local attackers can escalate privileges by placing a malicious DLL in the current working directory when using RSA SecurID Software Token.

- **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:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 17 Dec 2011
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-mm88-gfr5-7vjp

## What is CVE-2011-4141?

CVE-2011-4141 is a critical vulnerability in n/a, published on 17 Dec 2011. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Untrusted search path vulnerability in EMC RSA SecurID Software Token 4.1 before 4.1.1 allows local users to gain privileges via a Trojan horse DLL in the current working directory, as demonstrated by a directory that contains a Software Token file.

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

It affects 1 product.


Products: Rsa Securid.

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

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

## Is CVE-2011-4141 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2001-1461](https://insights.sbomify.com/CVE-2001-1461/): Path traversal in n/a (high 7.5)
- [CVE-2001-1462](https://insights.sbomify.com/CVE-2001-1462/): Information disclosure in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2011-4141 is a critical vulnerability in n/a, published on 17 Dec 2011. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2011-4141 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-4141/ (Markdown: https://insights.sbomify.com/CVE-2011-4141/index.md)
```

## Sources

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

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