# CVE-2008-1625: Privilege escalation in n/a

> Local attackers can escalate privileges by sending crafted IOCTL requests to the avast! kernel driver due to improper input validation.

- **Severity:** Medium 6.8 (`AV:L/AC:L/Au:S/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Apr 2008
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-wr6q-9jvw-7c6w

## What is CVE-2008-1625?

CVE-2008-1625 is a medium-severity vulnerability in n/a, published on 2 Apr 2008. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

aavmker4.sys in avast! Home and Professional 4.7 for Windows does not properly validate input to IOCTL 0xb2d60030, which allows local users to gain privileges via certain IOCTL requests.

Weakness: CWE-264

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

It affects 2 products.


Products: Avast Avast Antivirus Home, Avast Avast Antivirus Professional.

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

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

## Is CVE-2008-1625 being exploited?

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

Public exploit code:

- Avast! 4.7 - 'aavmker4.sys' Local Privilege Escalation (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2010-0705](https://insights.sbomify.com/CVE-2010-0705/): Memory corruption in n/a (high 7.2)
- [CVE-2009-4049](https://insights.sbomify.com/CVE-2009-4049/): Memory corruption in n/a (high 7.2)
- [CVE-2009-3522](https://insights.sbomify.com/CVE-2009-3522/): Memory corruption in n/a (high 7.2)
- [CVE-2009-3524](https://insights.sbomify.com/CVE-2009-3524/): Unspecified vulnerability in ashWsFtr.dll in avast! (high 7.2)
- [CVE-2009-3523](https://insights.sbomify.com/CVE-2009-3523/): Memory corruption in n/a (medium 6.9)

## Fix prompt for AI coding agents

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

What it is: CVE-2008-1625 is a medium-severity vulnerability in n/a, published on 2 Apr 2008. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2008-1625 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-1625/ (Markdown: https://insights.sbomify.com/CVE-2008-1625/index.md)
```

## Sources

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

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