# OSV-2020-407: Heap-double-free in opt_cleanup

> A heap double-free vulnerability in libpcap's opt_cleanup function can lead to denial of service or potential code execution.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Not stated
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Jul 2020

## What is OSV-2020-407?

OSV-2020-407 is an use after free vulnerability in libpcap, published on 1 Jul 2020. 

### Official description

OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=15178

```
Crash type: Heap-double-free
Crash state:
opt_cleanup
bpf_optimize
pcap_compile
```

## Which versions are affected by OSV-2020-407?

1 open source package ship an affected version, including libpcap.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `libpcap` | OSS-Fuzz | All versions | None |

## How do I fix OSV-2020-407?

No fix has been published for OSV-2020-407 yet. Limit exposure of the affected software until one is available.

## Is OSV-2020-407 being exploited?

There is no known exploitation of OSV-2020-407 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for OSV-2020-407 and fix it if it is affected.

What it is: OSV-2020-407 is an use after free vulnerability in libpcap, published on 1 Jul 2020. 
Exploitation: There is no known exploitation of OSV-2020-407 in the wild and no public exploit code.

Affected packages and fixed versions:
- libpcap (OSS-Fuzz): affected all versions; no fix listed

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/OSV-2020-407/ (Markdown: https://insights.sbomify.com/OSV-2020-407/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/OSV-2020-407

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