# CVE-2012-4820: Privilege escalation in n/a

> Remote attackers can escalate privileges by bypassing the Java security manager via insecure reflection usage in IBM JRE.

- **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:** Not needed
- **Fix available:** Yes
- **Published:** 11 Jan 2013
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-jfrg-75v5-493f

## What is CVE-2012-4820?

CVE-2012-4820 is a critical vulnerability in Ibm Lotus Domino, published on 11 Jan 2013. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Unspecified vulnerability in the JRE component in IBM Java 7 SR2 and earlier, Java 6.0.1 SR3 and earlier, Java 6 SR11 and earlier, Java 5 SR14 and earlier, and Java 142 SR13 FP13 and earlier; as used in IBM Rational Host On-Demand, Rational Change, Tivoli Monitoring, Smart Analytics System 5600, Tivoli Remote Control 5.1.2, WebSphere Real Time, Lotus Notes & Domino, Tivoli Storage Productivity Center, and Service Deliver Manager; and other products from other vendors such as Red Hat, when running under a security manager, allows remote attackers to gain privileges by modifying or removing the security manager via vectors related to "insecure use of the java.lang.reflect.Method invoke() method."

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

It affects 16 products.


Products: Ibm Java, Ibm Lotus Domino, Ibm Lotus Notes, Ibm Lotus Notes Sametime, Ibm Lotus Notes Traveler, Ibm Rational Change, Ibm Rational Host On-Demand, Ibm Service Delivery Manager, Ibm Smart Analytics System 5600, Ibm Smart Analytics System 5600 Software, Ibm Tivoli Monitoring, Ibm Tivoli Remote Control, Ibm Websphere Real Time, Tivoli Storage Productivity Center 5.0, Tivoli Storage Productivity Center 5.1, Tivoli Storage Productivity Center 5.1.1.

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

Upgrade to a fixed version.

## Is CVE-2012-4820 being exploited?

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

## Other vulnerabilities in Ibm Lotus Domino

- [CVE-2013-0485](https://insights.sbomify.com/CVE-2013-0485/): Other in n/a (critical 10.0)
- [CVE-2015-0192](https://insights.sbomify.com/CVE-2015-0192/): Privilege escalation in n/a (critical 9.8)
- [CVE-2013-5456](https://insights.sbomify.com/CVE-2013-5456/): Deserialization in n/a (critical 9.3)
- [CVE-2013-5457](https://insights.sbomify.com/CVE-2013-5457/): Code injection in n/a (critical 9.3)
- [CVE-2013-5458](https://insights.sbomify.com/CVE-2013-5458/): Code injection in n/a (critical 9.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2012-4820 is a critical vulnerability in Ibm Lotus Domino, published on 11 Jan 2013. 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-4820 in the wild and no public exploit code.

Affected product: Ibm Lotus Domino. 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-4820/ (Markdown: https://insights.sbomify.com/CVE-2012-4820/index.md)
```

## Sources

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

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