CVE-2020-14059: An issue was discovered in Squid 5.x before 5.0.3.
Noroxi assessment
Priority: Monitor (action score 27/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 4.4% (FIRST EPSS); higher than 91.3% of all records.
- Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: squid (openSUSE:Leap 15.1) 4.12-lp151.2.21.1; squid (openSUSE:Leap 15.2) 4.12-lp152.2.3.1; squid (SUSE:HPE Helion OpenStack 8) 3.5.21-26.26.1.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to squid (openSUSE:Leap 15.1) 4.12-lp151.2.21.1; squid (openSUSE:Leap 15.2) 4.12-lp152.2.3.1; squid (SUSE:HPE Helion OpenStack 8) 3.5.21-26.26.1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Jun 30, 2020
- Updated
- Jun 16, 2026
- EPSS
- 4.4% · 91th percentile
- CWE
- CWE-662
Report tools
Action score
27
Monitor
Low priority for now.
- CVSS
- 26 / 40 · 6.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 4.4%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| squid-cache | squid | cpe:2.3:a:squid-cache:squid |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- squid-cache squid5.0 and later · before 5.0.3
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| openSUSE:Leap 15.1 | squid | before 4.12-lp151.2.21.1 | 4.12-lp151.2.21.1 |
| openSUSE:Leap 15.2 | squid | before 4.12-lp152.2.3.1 | 4.12-lp152.2.3.1 |
| SUSE:HPE Helion OpenStack 8 | squid | before 3.5.21-26.26.1 | 3.5.21-26.26.1 |
| SUSE:Linux Enterprise Module for Server Applications 15 SP1 | squid | before 4.12-5.20.1 | 4.12-5.20.1 |
| SUSE:Linux Enterprise Point of Sale 11 SP3 | squid3 | before 3.1.23-8.16.37.12.1 | 3.1.23-8.16.37.12.1 |
| SUSE:Linux Enterprise Server 12 SP5 | squid | before 4.12-4.12.1 | 4.12-4.12.1 |
Same product
squid-cache: all recordsOther highest-scoring records for the same primary product.
- CVE-2024-25617Denial of Service in HTTP Header parser in squid proxy56Plan
- CVE-2023-49285Denial of Service in HTTP Message Processing in Squid56Plan
- CVE-2021-31806An issue was discovered in Squid before 4.15 and 5.x before 5.0.6.55Plan
Published before and after this one in the same product
- ← EarlierCVE-2020-15049Jun 30, 2020 · An issue was discovered in http/ContentLengthInterpreter.cc in Squid before 4.12 and 5.x before 5.0.3.37Monitor
- ← EarlierCVE-2020-14058Jun 30, 2020 · An issue was discovered in Squid before 4.12 and 5.x before 5.0.3.31Monitor
- Later →CVE-2020-24606Aug 24, 2020 · Squid before 4.13 and 5.x before 5.0.4 allows a trusted peer to perform Denial of Service by consuming all available CPU cycles during handl31Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| opensuse:squid | 4.12-lp151.2.21.1 · openSUSE:Leap 15.1 | Package registry (OSV) |
| suse:squid | 4.12-5.20.1 · SUSE:Linux Enterprise Module for Server Applications 15 SP1 | Package registry (OSV) |
| suse:squid3 | 3.1.23-8.16.37.12.1 · SUSE:Linux Enterprise Point of Sale 11 SP3 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-20-473 · Jun 26, 2020(Squid Sunucu Güvenlik Güncellemesi)
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-662 · Improper SynchronizationCVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (2 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.