# CVE-2015-1031: Use after free in n/a

> Remote attackers can exploit use-after-free flaws in Privoxy to potentially execute code or cause denial of service.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 10 Feb 2015
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2015-1031, DSA-3133-1, GHSA-p49r-xm5f-3r8x

## What is CVE-2015-1031?

CVE-2015-1031 is a high-severity use after free vulnerability in n/a, published on 10 Feb 2015. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Multiple use-after-free vulnerabilities in Privoxy before 3.0.22 allow remote attackers to have unspecified impact via vectors related to (1) the unmap function in list.c or (2) "two additional unconfirmed use-after-free complaints made by Coverity scan." NOTE: some of these details are obtained from third party information.

## Which versions are affected by CVE-2015-1031?

It affects 1 product.


Products: Privoxy Privoxy.

## How do I fix CVE-2015-1031?

Upgrade to a fixed version.

## Is CVE-2015-1031 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2019-3699](https://insights.sbomify.com/CVE-2019-3699/): Local privilege escalation from user privoxy to root (high 7.7)
- [CVE-2021-44540](https://insights.sbomify.com/CVE-2021-44540/): Denial of service in Privoxy (high 7.5)
- [CVE-2021-44541](https://insights.sbomify.com/CVE-2021-44541/): Denial of service in Privoxy (high 7.5)
- [CVE-2021-44542](https://insights.sbomify.com/CVE-2021-44542/): Denial of service in Privoxy (high 7.5)
- [CVE-2021-20209](https://insights.sbomify.com/CVE-2021-20209/): Denial of service in privoxy (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2015-1031 and fix it if it is affected.

What it is: CVE-2015-1031 is a high-severity use after free vulnerability in n/a, published on 10 Feb 2015. 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-2015-1031 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-2015-1031/ (Markdown: https://insights.sbomify.com/CVE-2015-1031/index.md)
```

## Sources

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

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