# CVE-2008-1898: Memory corruption in n/a

> Remote attackers can execute arbitrary code or crash the browser via a malicious ActiveX control in Microsoft Office applications.

- **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 Apr 2008
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-q85g-qvvf-hm5m

## What is CVE-2008-1898?

CVE-2008-1898 is a critical memory corruption vulnerability in Microsoft Office, published on 21 Apr 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

A certain ActiveX control in WkImgSrv.dll 7.03.0616.0, as distributed in Microsoft Works 7 and Microsoft Office 2003 and 2007, allows remote attackers to execute arbitrary code or cause a denial of service (browser crash) via an invalid WksPictureInterface property value, which triggers an improper function call.

Weakness: CWE-20 (Improper Input Validation)

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

It affects 2 products.


Products: Microsoft Office, Microsoft Works.

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

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

## Is CVE-2008-1898 being exploited?

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

Public exploit code:

- Microsoft Works 7 - 'WkImgSrv.dll' ActiveX Denial of Service (PoC) (exploitdb)
- Microsoft Works 7 - 'WkImgSrv.dll' ActiveX Remote Buffer Overflow (exploitdb)
- Microsoft Works 7 WkImgSrv.dll WKsPictureInterface() ActiveX Code Execution (metasploit)
- Microsoft Works 7 - 'WkImgSrv.dll' WKsPictureInterface() ActiveX (Metasploit) (exploitdb)

## Other vulnerabilities in Microsoft Office

- [CVE-2018-0798](https://insights.sbomify.com/CVE-2018-0798/): Microsoft Office Memory Corruption (high 8.8, exploited in the wild)
- [CVE-2015-1770](https://insights.sbomify.com/CVE-2015-1770/): Microsoft Office Uninitialized Memory Use (high 8.8, exploited in the wild)
- [CVE-2006-2492](https://insights.sbomify.com/CVE-2006-2492/): Microsoft Word Malformed Object Pointer (high 8.8, exploited in the wild)
- [CVE-2018-0802](https://insights.sbomify.com/CVE-2018-0802/): Microsoft Office Memory Corruption (high 7.8, exploited in the wild)
- [CVE-2017-11882](https://insights.sbomify.com/CVE-2017-11882/): Microsoft Office Memory Corruption (high 7.8, exploited in the wild)

## Fix prompt for AI coding agents

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

What it is: CVE-2008-1898 is a critical memory corruption vulnerability in Microsoft Office, published on 21 Apr 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2008-1898 exists.

Affected product: Microsoft Office. 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-1898/ (Markdown: https://insights.sbomify.com/CVE-2008-1898/index.md)
```

## Sources

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

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