# CVE-2007-4901: Code injection in n/a

> Remote attackers can execute arbitrary code or read local files via malicious HTML in instant messages due to improper IE control constraints.

- **Severity:** Medium 5.8 (`AV:N/AC:M/Au:N/C:P/I:P/A:N`)
- **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:** 14 Sep 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-464x-prm7-r3m9

## What is CVE-2007-4901?

CVE-2007-4901 is a medium-severity code injection vulnerability in n/a, published on 14 Sep 2007. 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

The embedded Internet Explorer server control in AOL Instant Messenger (AIM) 6.1.41.2 and 6.2.32.1, AIM Pro, and AIM Lite does not properly constrain the use of mshtml.dll's web script and HTML functionality for incoming instant messages, which allows remote attackers to place HTML into unexpected contexts or execute arbitrary code, as demonstrated by writing arbitrary HTML to a notification window, and writing contents of arbitrary local image files to this window via IMG SRC.

## Which versions are affected by CVE-2007-4901?

It affects 3 products.


Products: Aol Aim Lite, Aol Aim Pro, Aol Instant Messenger.

## How do I fix CVE-2007-4901?

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

## Is CVE-2007-4901 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2007-4901 and fix it if it is affected.

What it is: CVE-2007-4901 is a medium-severity code injection vulnerability in n/a, published on 14 Sep 2007. 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-2007-4901 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-2007-4901/ (Markdown: https://insights.sbomify.com/CVE-2007-4901/index.md)
```

## Sources

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

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