# CVE-2011-1935: Information disclosure in n/a

> Attackers can evade detection by sending crafted packets that are truncated during capture, bypassing security monitoring tools.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 20 Oct 2017
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2011-1935, GHSA-9x67-6959-6grf

## What is CVE-2011-1935?

CVE-2011-1935 is a critical vulnerability in n/a, published on 20 Oct 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

pcap-linux.c in libpcap 1.1.1 before commit ea9432fabdf4b33cbc76d9437200e028f1c47c93 when snaplen is set may truncate packets, which might allow remote attackers to send arbitrary data while avoiding detection via crafted packets.

## Which versions are affected by CVE-2011-1935?

It affects 1 product.


Products: Tcpdump Libpcap.

## How do I fix CVE-2011-1935?

Apply the vendor's patch.

## Is CVE-2011-1935 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2019-15163](https://insights.sbomify.com/CVE-2019-15163/): Null dereference in n/a (high 7.5)
- [CVE-2019-15161](https://insights.sbomify.com/CVE-2019-15161/): Integer overflow in n/a (medium 5.3)
- [CVE-2019-15162](https://insights.sbomify.com/CVE-2019-15162/): Information disclosure in n/a (medium 5.3)
- [CVE-2019-15164](https://insights.sbomify.com/CVE-2019-15164/): Server-side request forgery in n/a (medium 5.3)
- [CVE-2023-7256](https://insights.sbomify.com/CVE-2023-7256/): Double-free in libpcap before 1.10.5 with remote packet capture support. (medium 4.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2011-1935 and fix it if it is affected.

What it is: CVE-2011-1935 is a critical vulnerability in n/a, published on 20 Oct 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2011-1935 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-2011-1935/ (Markdown: https://insights.sbomify.com/CVE-2011-1935/index.md)
```

## Sources

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

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