# CVE-2012-6349: Memory corruption in n/a

> Remote attackers can execute arbitrary code via a crafted .mdb file in IBM Notes due to a buffer overflow in the KeyView IDOL parser.

- **Severity:** Critical 9.3 (`AV:N/AC:M/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 18 Jul 2013
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-4h9v-gg55-hx7g

## What is CVE-2012-6349?

CVE-2012-6349 is a critical memory corruption vulnerability in Ibm Lotus Notes, published on 18 Jul 2013. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Buffer overflow in the .mdb parser in Autonomy KeyView IDOL, as used in IBM Notes 8.5.x before 8.5.3 FP4, allows remote attackers to execute arbitrary code via a crafted file, aka SPR KLYH92XL3W.

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

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

It affects 2 products.


Products: Autonomy Keyview Idol, Ibm Lotus Notes.

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

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

## Is CVE-2012-6349 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2012-6349 is a critical memory corruption vulnerability in Ibm Lotus Notes, published on 18 Jul 2013. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2012-6349 in the wild and no public exploit code.

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

## Sources

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

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