# CVE-2008-0072: Other in n/a

> Remote attackers can execute arbitrary code via a crafted encrypted message in the Evolution email client, requiring user interaction to view the message.

- **Severity:** Medium 6.8 (`AV:N/AC:M/Au:N/C:P/I:P/A:P`)
- **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:** Yes
- **Published:** 6 Mar 2008
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2008-0072, DSA-1512-1, GHSA-j468-6fhg-5w3c, RHSA-2008:0177, RHSA-2008:0178

## What is CVE-2008-0072?

CVE-2008-0072 is a medium-severity vulnerability in n/a, published on 6 Mar 2008. 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

Format string vulnerability in the emf_multipart_encrypted function in mail/em-format.c in Evolution 2.12.3 and earlier allows remote attackers to execute arbitrary code via a crafted encrypted message, as demonstrated using the Version field.

Weakness: CWE-134 (Use of Externally-Controlled Format String)

## Which versions are affected by CVE-2008-0072?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `evolution` | Red Hat:enterprise_linux:4::as | All versions | 0:2.0.2-35.0.4.el4_6.1 |
| `evolution-debuginfo` | Red Hat:enterprise_linux:4::as | All versions | 0:2.0.2-35.0.4.el4_6.1 |
| `evolution-devel` | Red Hat:enterprise_linux:4::as | All versions | 0:2.0.2-35.0.4.el4_6.1 |
| `evolution28` | Red Hat:enterprise_linux:4::as | All versions | 0:2.8.0-53.el4_6.2 |
| `evolution28-debuginfo` | Red Hat:enterprise_linux:4::as | All versions | 0:2.8.0-53.el4_6.2 |
| `evolution28-devel` | Red Hat:enterprise_linux:4::as | All versions | 0:2.8.0-53.el4_6.2 |
| `evolution` | Red Hat:enterprise_linux:4::desktop | All versions | 0:2.0.2-35.0.4.el4_6.1 |
| `evolution-debuginfo` | Red Hat:enterprise_linux:4::desktop | All versions | 0:2.0.2-35.0.4.el4_6.1 |
| `evolution-devel` | Red Hat:enterprise_linux:4::desktop | All versions | 0:2.0.2-35.0.4.el4_6.1 |
| `evolution28` | Red Hat:enterprise_linux:4::desktop | All versions | 0:2.8.0-53.el4_6.2 |
| `evolution28-debuginfo` | Red Hat:enterprise_linux:4::desktop | All versions | 0:2.8.0-53.el4_6.2 |
| `evolution28-devel` | Red Hat:enterprise_linux:4::desktop | All versions | 0:2.8.0-53.el4_6.2 |
| `evolution` | Red Hat:enterprise_linux:4::es | All versions | 0:2.0.2-35.0.4.el4_6.1 |
| `evolution-debuginfo` | Red Hat:enterprise_linux:4::es | All versions | 0:2.0.2-35.0.4.el4_6.1 |
| `evolution-devel` | Red Hat:enterprise_linux:4::es | All versions | 0:2.0.2-35.0.4.el4_6.1 |
| `evolution28` | Red Hat:enterprise_linux:4::es | All versions | 0:2.8.0-53.el4_6.2 |
| `evolution28-debuginfo` | Red Hat:enterprise_linux:4::es | All versions | 0:2.8.0-53.el4_6.2 |
| `evolution28-devel` | Red Hat:enterprise_linux:4::es | All versions | 0:2.8.0-53.el4_6.2 |
| `evolution` | Red Hat:enterprise_linux:4::ws | All versions | 0:2.0.2-35.0.4.el4_6.1 |
| `evolution-debuginfo` | Red Hat:enterprise_linux:4::ws | All versions | 0:2.0.2-35.0.4.el4_6.1 |
| `evolution-devel` | Red Hat:enterprise_linux:4::ws | All versions | 0:2.0.2-35.0.4.el4_6.1 |
| `evolution28` | Red Hat:enterprise_linux:4::ws | All versions | 0:2.8.0-53.el4_6.2 |
| `evolution28-debuginfo` | Red Hat:enterprise_linux:4::ws | All versions | 0:2.8.0-53.el4_6.2 |
| `evolution28-devel` | Red Hat:enterprise_linux:4::ws | All versions | 0:2.8.0-53.el4_6.2 |
| `evolution` | Red Hat:enterprise_linux:5::client | All versions | 0:2.8.0-40.el5_1.1 |
| `evolution-debuginfo` | Red Hat:enterprise_linux:5::client | All versions | 0:2.8.0-40.el5_1.1 |
| `evolution` | Red Hat:enterprise_linux:5::client_workstation | All versions | 0:2.8.0-40.el5_1.1 |
| `evolution-debuginfo` | Red Hat:enterprise_linux:5::client_workstation | All versions | 0:2.8.0-40.el5_1.1 |
| `evolution-devel` | Red Hat:enterprise_linux:5::client_workstation | All versions | 0:2.8.0-40.el5_1.1 |
| `evolution` | Red Hat:rhel_eus:4.5::as | All versions | 0:2.0.2-35.0.4.el4_5.1 |
| `evolution-debuginfo` | Red Hat:rhel_eus:4.5::as | All versions | 0:2.0.2-35.0.4.el4_5.1 |
| `evolution-devel` | Red Hat:rhel_eus:4.5::as | All versions | 0:2.0.2-35.0.4.el4_5.1 |
| `evolution` | Red Hat:rhel_eus:4.5::es | All versions | 0:2.0.2-35.0.4.el4_5.1 |
| `evolution-debuginfo` | Red Hat:rhel_eus:4.5::es | All versions | 0:2.0.2-35.0.4.el4_5.1 |
| `evolution-devel` | Red Hat:rhel_eus:4.5::es | All versions | 0:2.0.2-35.0.4.el4_5.1 |
| `evolution` | Red Hat:rhel_productivity:5 | All versions | 0:2.8.0-40.el5_1.1 |
| `evolution-debuginfo` | Red Hat:rhel_productivity:5 | All versions | 0:2.8.0-40.el5_1.1 |
| `evolution-devel` | Red Hat:rhel_productivity:5 | All versions | 0:2.8.0-40.el5_1.1 |

Products: Gnome Evolution.

## How do I fix CVE-2008-0072?

Upgrade to a fixed version.

## Is CVE-2008-0072 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-12422](https://insights.sbomify.com/CVE-2018-12422/): Memory corruption in n/a (critical 9.8)
- [CVE-2008-1109](https://insights.sbomify.com/CVE-2008-1109/): Memory corruption in n/a (critical 9.3)
- [CVE-2009-3721](https://insights.sbomify.com/CVE-2009-3721/): Path traversal in ytnef (high 7.8)
- [CVE-2008-1108](https://insights.sbomify.com/CVE-2008-1108/): Memory corruption in n/a (high 7.6)
- [CVE-2013-4166](https://insights.sbomify.com/CVE-2013-4166/): Information disclosure in Evolution (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2008-0072 and fix it if it is affected.

What it is: CVE-2008-0072 is a medium-severity vulnerability in n/a, published on 6 Mar 2008. 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-2008-0072 in the wild and no public exploit code.

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

## Sources

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

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