# CVE-2010-3133: Path traversal in n/a

> Local attackers can execute arbitrary code via DLL hijacking when Wireshark loads a malicious library from the current directory.

- **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:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 26 Aug 2010
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-4vf6-2fhm-2c5g

## What is CVE-2010-3133?

CVE-2010-3133 is a critical path traversal vulnerability in Wireshark Wireshark, published on 26 Aug 2010. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Untrusted search path vulnerability in Wireshark 0.8.4 through 1.0.15 and 1.2.0 through 1.2.10 allows local users, and possibly remote attackers, to execute arbitrary code and conduct DLL hijacking attacks via a Trojan horse airpcap.dll, and possibly other DLLs, that is located in the same folder as a file that automatically launches Wireshark.

## Which versions are affected by CVE-2010-3133?

It affects 1 product.


Products: Wireshark Wireshark.

## How do I fix CVE-2010-3133?

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

## Is CVE-2010-3133 being exploited?

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

Public exploit code:

- Wireshark 1.2.10 - 'airpcap.dll' DLL Hijacking (exploitdb)

## Other vulnerabilities in Wireshark Wireshark

- [CVE-2011-0444](https://insights.sbomify.com/CVE-2011-0444/): Memory corruption in n/a (critical 10.0)
- [CVE-2010-2994](https://insights.sbomify.com/CVE-2010-2994/): Memory corruption in n/a (critical 10.0)
- [CVE-2010-2995](https://insights.sbomify.com/CVE-2010-2995/): Memory corruption in n/a (critical 10.0)
- [CVE-2009-1266](https://insights.sbomify.com/CVE-2009-1266/): Other in n/a (critical 10.0)
- [CVE-2009-1210](https://insights.sbomify.com/CVE-2009-1210/): Memory corruption in n/a (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2010-3133 and fix it if it is affected.

What it is: CVE-2010-3133 is a critical path traversal vulnerability in Wireshark Wireshark, published on 26 Aug 2010. It can only be exploited from the same machine or local network, 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-2010-3133 exists.

Affected product: Wireshark Wireshark. 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-2010-3133/ (Markdown: https://insights.sbomify.com/CVE-2010-3133/index.md)
```

## Sources

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

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