# CVE-2005-0102: Integer overflow in n/a

> Local users or malicious POP3 servers can execute arbitrary code via an integer overflow in the Evolution email client's lock helper.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 29 Jan 2005
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2005-0102, DSA-673-1, GHSA-ghp8-rg92-746w, RHSA-2005:238

## What is CVE-2005-0102?

CVE-2005-0102 is a critical vulnerability in Debian Debian Linux, published on 29 Jan 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Integer overflow in camel-lock-helper in Evolution 2.0.2 and earlier allows local users or remote malicious POP3 servers to execute arbitrary code via a length value of -1, which leads to a zero byte memory allocation and a buffer overflow.

Weakness: CWE-190 (Integer Overflow or Wraparound)

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

It affects 2 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `evolution` | Red Hat:enterprise_linux:3::as | All versions | 0:1.4.5-14 |
| `evolution-debuginfo` | Red Hat:enterprise_linux:3::as | All versions | 0:1.4.5-14 |
| `evolution-devel` | Red Hat:enterprise_linux:3::as | All versions | 0:1.4.5-14 |
| `evolution` | Red Hat:enterprise_linux:3::desktop | All versions | 0:1.4.5-14 |
| `evolution-debuginfo` | Red Hat:enterprise_linux:3::desktop | All versions | 0:1.4.5-14 |
| `evolution-devel` | Red Hat:enterprise_linux:3::desktop | All versions | 0:1.4.5-14 |
| `evolution` | Red Hat:enterprise_linux:3::es | All versions | 0:1.4.5-14 |
| `evolution-debuginfo` | Red Hat:enterprise_linux:3::es | All versions | 0:1.4.5-14 |
| `evolution-devel` | Red Hat:enterprise_linux:3::es | All versions | 0:1.4.5-14 |
| `evolution` | Red Hat:enterprise_linux:3::ws | All versions | 0:1.4.5-14 |
| `evolution-debuginfo` | Red Hat:enterprise_linux:3::ws | All versions | 0:1.4.5-14 |
| `evolution-devel` | Red Hat:enterprise_linux:3::ws | All versions | 0:1.4.5-14 |

Products: Debian Debian Linux, Gnome Evolution.

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

Apply the vendor's patch.

## Is CVE-2005-0102 being exploited?

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

## Other vulnerabilities in Debian Debian Linux

- [CVE-2015-3306](https://insights.sbomify.com/CVE-2015-3306/): ProFTPD Improper Access Control (critical 10.0, exploited in the wild)
- [CVE-2025-49113](https://insights.sbomify.com/CVE-2025-49113/): RoundCube Webmail Deserialization of Untrusted Data (critical 9.9, exploited in the wild)
- [CVE-2026-24061](https://insights.sbomify.com/CVE-2026-24061/): GNU InetUtils Argument Injection (critical 9.8, exploited in the wild)
- [CVE-2025-39682](https://insights.sbomify.com/CVE-2025-39682/): Linux Kernel Improper Check for Unusual or Exceptional Conditions (critical 9.8, exploited in the wild)
- [CVE-2024-9680](https://insights.sbomify.com/CVE-2024-9680/): Mozilla Firefox Use-After-Free (critical 9.8, exploited in the wild)

## Fix prompt for AI coding agents

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

What it is: CVE-2005-0102 is a critical vulnerability in Debian Debian Linux, published on 29 Jan 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2005-0102 in the wild and no public exploit code.

Affected product: Debian Debian Linux. 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-0102/ (Markdown: https://insights.sbomify.com/CVE-2005-0102/index.md)
```

## Sources

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

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