# CVE-2006-1649: Path traversal in n/a

> Local attackers can bypass write permissions to create files in restricted directories via the quarantine restore feature in ESET NOD32.

- **Severity:** High 7.2 (`AV:L/AC:L/Au:N/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:** 6 Apr 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-5xp3-87g8-2vfv

## What is CVE-2006-1649?

CVE-2006-1649 is a high-severity path traversal vulnerability in n/a, published on 6 Apr 2006. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The "restore to" selection in the "quarantine a file" capability of ESET NOD32 before 2.51.26 allows a restore to any directory that permits read access by the invoking user, which allows local users to create new files despite write-access directory permissions.

## Which versions are affected by CVE-2006-1649?

It affects 1 product.


Products: Eset Software Nod32 Antivirus.

## How do I fix CVE-2006-1649?

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

## Is CVE-2006-1649 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2007-2852](https://insights.sbomify.com/CVE-2007-2852/): Memory corruption in n/a (critical 9.3)
- [CVE-2006-6676](https://insights.sbomify.com/CVE-2006-6676/): Integer overflow in n/a (critical 9.3)
- [CVE-2005-2903](https://insights.sbomify.com/CVE-2005-2903/): Memory corruption in n/a (high 7.5)
- [CVE-2006-0951](https://insights.sbomify.com/CVE-2006-0951/): Privilege escalation in n/a (high 7.2)
- [CVE-2003-0062](https://insights.sbomify.com/CVE-2003-0062/): Memory corruption in n/a (high 7.2)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2006-1649 and fix it if it is affected.

What it is: CVE-2006-1649 is a high-severity path traversal vulnerability in n/a, published on 6 Apr 2006. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2006-1649 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-2006-1649/ (Markdown: https://insights.sbomify.com/CVE-2006-1649/index.md)
```

## Sources

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

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