# CVE-2008-7022: Code injection in n/a

> Remote attackers can execute arbitrary programs via the LoadXmlEmail method in the Chilkat IMAP ActiveX control, requiring user interaction.

- **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:** 21 Aug 2009
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-p6r4-vm36-7vhj

## What is CVE-2008-7022?

CVE-2008-7022 is a critical code injection vulnerability in n/a, published on 21 Aug 2009. 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

Insecure method vulnerability in ChilkatMail_v7_9.dll in the Chilkat Software IMAP ActiveX control (ChilkatMail2.ChilkatMailMan2.1) allows remote attackers to execute arbitrary programs via the LoadXmlEmail method.

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

It affects 1 product.


Products: Chilkatsoft Chilkat Imap Activex Control.

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

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

## Is CVE-2008-7022 being exploited?

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

Public exploit code:

- Chilkat IMAP ActiveX 7.9 - File Execution / Denial of Service (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2008-7022 is a critical code injection vulnerability in n/a, published on 21 Aug 2009. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2008-7022 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-2008-7022/ (Markdown: https://insights.sbomify.com/CVE-2008-7022/index.md)
```

## Sources

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

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