# CVE-2005-2618: Memory corruption in n/a

> Remote attackers can execute arbitrary code via crafted files processed by the KeyView SDK, affecting applications like Lotus Notes.

- **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:** 15 Feb 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-g7qc-77mr-f9fj

## What is CVE-2005-2618?

CVE-2005-2618 is a critical memory corruption vulnerability in Ibm Lotus Notes, published on 15 Feb 2006. 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

Multiple stack-based buffer overflows in Autonomy (formerly Verity) KeyView SDK before 9.2.0, as used in Lotus Notes 6.5.4 and 7.0, allow remote attackers to execute arbitrary code via (1) a UUE file containing an encoded file with a long filename handled by uudrdr.dll, (2) a compressed ZIP file with a long filename handled by kvarcve.dll, (3) a TAR archive with a long filename that is extracted to a directory with a long path handled by the TAR reader (tarrdr.dll), (4) an email that contains a long HTTP, FTP, or // link handled by the HTML speed reader (htmsr.dll) or (5) an email containing a crafted long link handled by the HTML speed reader (htmsr.dll).

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

## Which versions are affected by CVE-2005-2618?

It affects 4 products.


Products: Autonomy Keyview Export Sdk, Autonomy Keyview Filter Sdk, Autonomy Keyview Viewer Sdk, Ibm Lotus Notes.

## How do I fix CVE-2005-2618?

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

## Is CVE-2005-2618 being exploited?

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

## Other vulnerabilities in Ibm Lotus Notes

- [CVE-2010-0126](https://insights.sbomify.com/CVE-2010-0126/): Memory corruption in n/a (critical 9.3)
- [CVE-2010-0131](https://insights.sbomify.com/CVE-2010-0131/): Memory corruption in n/a (critical 9.3)
- [CVE-2010-0133](https://insights.sbomify.com/CVE-2010-0133/): Memory corruption in n/a (critical 9.3)
- [CVE-2010-0134](https://insights.sbomify.com/CVE-2010-0134/): Integer overflow in n/a (critical 9.3)
- [CVE-2010-0135](https://insights.sbomify.com/CVE-2010-0135/): Memory corruption in n/a (critical 9.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2005-2618 and fix it if it is affected.

What it is: CVE-2005-2618 is a critical memory corruption vulnerability in Ibm Lotus Notes, published on 15 Feb 2006. 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-2005-2618 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-2005-2618/ (Markdown: https://insights.sbomify.com/CVE-2005-2618/index.md)
```

## Sources

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

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