# CVE-2012-2276: Null dereference in n/a

> Remote attackers can crash the EMC Documentum IRM Server daemon by sending malformed input data, causing a denial of service.

- **Severity:** High 7.8 (`AV:N/AC:L/Au:N/C:N/I:N/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 May 2012
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-3pjm-j8pf-453f

## What is CVE-2012-2276?

CVE-2012-2276 is a high-severity vulnerability in n/a, published on 14 May 2012. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The IRM Server in EMC Documentum Information Rights Management 4.x before 4.7.0100 and 5.x before 5.0.1030 allows remote attackers to cause a denial of service (NULL pointer dereference and daemon crash) via input data that (1) lacks FIPS fields or (2) has an invalid version number.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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

It affects 1 product.


Products: Emc Documentum Information Rights Management.

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

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

## Is CVE-2012-2276 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2012-2276 exists.

Public exploit code:

- EMC IRM License Server 4.6.1.1995 - Denial of Service (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2012-2277](https://insights.sbomify.com/CVE-2012-2277/): Denial of service in n/a (high 7.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2012-2276 is a high-severity vulnerability in n/a, published on 14 May 2012. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2012-2276 exists.

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

## Sources

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

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