# CVE-2020-14059: Race condition in n/a

> A race condition in Squid's SMP cache memory management allows attackers to cause a denial of service via an ABA problem.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 30 Jun 2020
- **Updated:** 4 Aug 2024
- **Also known as:** SUSE-SU-2020:1769-1, SUSE-SU-2020:1770-1, openSUSE-SU-2020:0910-1, openSUSE-SU-2020:0914-1

## What is CVE-2020-14059?

CVE-2020-14059 is a medium-severity vulnerability in Squid-Cache Squid, published on 30 Jun 2020. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An issue was discovered in Squid 5.x before 5.0.3. Due to an Incorrect Synchronization, a Denial of Service can occur when processing objects in an SMP cache because of an Ipc::Mem::PageStack::pop ABA problem during access to the memory page/slot management list.

Weakness: CWE-662 (Improper Synchronization)

## Which versions are affected by CVE-2020-14059?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `squid` | SUSE:Linux Enterprise High Performance Computing 15-ESPOS | All versions | 4.12-5.20.1 |
| `squid` | SUSE:Linux Enterprise High Performance Computing 15-LTSS | All versions | 4.12-5.20.1 |
| `squid` | SUSE:Linux Enterprise Module for Server Applications 15 SP1 | All versions | 4.12-5.20.1 |
| `squid` | SUSE:Linux Enterprise Module for Server Applications 15 SP2 | All versions | 4.12-5.20.1 |
| `squid` | SUSE:Linux Enterprise Server 12 SP5 | All versions | 4.12-4.12.1 |
| `squid` | SUSE:Linux Enterprise Server 15-LTSS | All versions | 4.12-5.20.1 |
| `squid` | SUSE:Linux Enterprise Server for SAP Applications 12 SP5 | All versions | 4.12-4.12.1 |
| `squid` | SUSE:Linux Enterprise Server for SAP Applications 15 | All versions | 4.12-5.20.1 |
| `squid` | openSUSE:Leap 15.1 | All versions | 4.12-lp151.2.21.1 |
| `squid` | openSUSE:Leap 15.2 | All versions | 4.12-lp152.2.3.1 |

Products: Squid-Cache Squid.

## How do I fix CVE-2020-14059?

Upgrade to a fixed version.

## Is CVE-2020-14059 being exploited?

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

## Other vulnerabilities in Squid-Cache Squid

- [CVE-2025-62168](https://insights.sbomify.com/CVE-2025-62168/): Squid vulnerable to information disclosure via authentication credential leakage in error handling (critical 10.0)
- [CVE-2025-54574](https://insights.sbomify.com/CVE-2025-54574/): Squid's URN Handling can lead to Buffer Overflow (critical 9.3)
- [CVE-2026-33526](https://insights.sbomify.com/CVE-2026-33526/): Squid vulnerable to Denial of Service in ICP Request handling (critical 9.2)
- [CVE-2026-32748](https://insights.sbomify.com/CVE-2026-32748/): Squid has Denial of Service in ICP Response handling (high 8.7)
- [CVE-2023-50269](https://insights.sbomify.com/CVE-2023-50269/): SQUID-2023:10 Denial of Service in HTTP Request parsing (high 8.6)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-14059 and fix it if it is affected.

What it is: CVE-2020-14059 is a medium-severity vulnerability in Squid-Cache Squid, published on 30 Jun 2020. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-14059 in the wild and no public exploit code.

Affected product: Squid-Cache Squid. 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-2020-14059/ (Markdown: https://insights.sbomify.com/CVE-2020-14059/index.md)
```

## Sources

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

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