CVE-2018-1000024: The Squid Software Foundation Squid HTTP Caching Proxy version 3.0 to 3.5.27, 4.0 to 4.0.22 contains a Incorrect Pointer Handling…
Noroxi assessment
Priority: Monitor (action score 32/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: 7.9% (FIRST EPSS); higher than 94.8% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: n/a n/a 4.0.23.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to n/a n/a 4.0.23 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
The Squid Software Foundation Squid HTTP Caching Proxy version 3.0 to 3.5.27, 4.0 to 4.0.22 contains a Incorrect Pointer Handling vulnerability in ESI Response Processing that can result in Denial of Service for all clients using the proxy.. This attack appear to be exploitable via Remote server delivers an HTTP response payload containing valid but unusual ESI syntax.. This vulnerability appears to have been fixed in 4.0.23 and later.
- Published
- Feb 9, 2018
- Updated
- Jun 16, 2026
- EPSS
- 7.9% · 94th percentile
- CWE
- —
Report tools
Action score
32
Low priority for now.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 2 / 30 · 7.9%
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.
Is your version affected? Check itNoroxi 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 |
| debian | debian linux | cpe:2.3:o:debian:debian_linux |
| canonical | ubuntu linux | cpe:2.3:o:canonical:ubuntu_linux |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- canonical ubuntu linux14.04
- canonical ubuntu linux16.04
- canonical ubuntu linux17.10
- debian debian linux7.0
- debian debian linux8.0
- debian debian linux9.0
- squid-cache squid3.0 and later · up to 3.5.27 inclusive
- squid-cache squid4.0 and later · up to 4.0.22 inclusive
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Alpine:v3.10 | squid | from 3.0 · before 3.5.27-r2 | 3.5.27-r2 |
| Alpine:v3.4 | squid | from 3.0 · before 3.5.27-r0 | 3.5.27-r0 |
| Debian:12 | squid | before 4.1-1 | 4.1-1 |
| Debian:7 | squid3 | before 3.1.20-2.2+deb7u8 | 3.1.20-2.2+deb7u8 |
| Debian:8 | squid3 | before 3.4.8-6+deb8u5 | 3.4.8-6+deb8u5 |
| Debian:9 | squid3 | before 3.5.23-5+deb9u1 | 3.5.23-5+deb9u1 |
| openSUSE:Tumbleweed | squid | before 4.16-1.5 | 4.16-1.5 |
| Red Hat:enterprise_linux:7::server | squid | before 7:3.5.20-15.el7 | 7:3.5.20-15.el7 |
| Red Hat:enterprise_linux:7::server | squid-debuginfo | before 7:3.5.20-15.el7 | 7:3.5.20-15.el7 |
| Red Hat:enterprise_linux:7::server | squid-migration-script | before 7:3.5.20-15.el7 | 7:3.5.20-15.el7 |
| Red Hat:enterprise_linux:7::server | squid-sysvinit | before 7:3.5.20-15.el7 | 7:3.5.20-15.el7 |
| SUSE:Linux Enterprise Server 11 SP4 | squid3 | before 3.1.23-8.16.37.3.1 | 3.1.23-8.16.37.3.1 |
| SUSE:Linux Enterprise Server for Raspberry Pi 12 SP2 | squid | before 3.5.21-26.6.1 | 3.5.21-26.6.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 proxy57Plan
- 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-2016-4556May 10, 2016 · Double free vulnerability in Esi.cc in Squid 3.x before 3.5.18 and 4.x before 4.0.10 allows remote servers to cause a denial of service…37Monitor
- ← EarlierCVE-2016-10003Jan 27, 2017 · Incorrect HTTP Request header comparison in Squid HTTP Proxy 3.5.0.1 through 3.5.22, and 4.0.1 through 4.0.16 results in Collapsed…31Monitor
- Later →CVE-2018-1000027Feb 9, 2018 · The Squid Software Foundation Squid HTTP Caching Proxy version prior to version 4.0.23 contains a NULL Pointer Dereference vulnerability in…34Monitor
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 |
|---|---|---|
| n/a n/a | 4.0.23 · description | Vendor (CNA) |
| alpine:squid | 3.5.27-r2 · Alpine:v3.10 | Package registry (OSV) |
| debian:squid | 4.1-1 · Debian:12 | Package registry (OSV) |
| debian:squid3 | 3.1.20-2.2+deb7u8 · Debian:7 | Package registry (OSV) |
| opensuse:squid | 4.16-1.5 · openSUSE:Tumbleweed | Package registry (OSV) |
| red hat:squid | 7:3.5.20-15.el7 · Red Hat:enterprise_linux:7::server | Package registry (OSV) |
| red hat:squid-debuginfo | 7:3.5.20-15.el7 · Red Hat:enterprise_linux:7::server | Package registry (OSV) |
| red hat:squid-migration-script | 7:3.5.20-15.el7 · Red Hat:enterprise_linux:7::server | Package registry (OSV) |
| red hat:squid-sysvinit | 7:3.5.20-15.el7 · Red Hat:enterprise_linux:7::server | Package registry (OSV) |
| suse:squid | 3.5.21-26.6.1 · SUSE:Linux Enterprise Server for Raspberry Pi 12 SP2 | Package registry (OSV) |
| suse:squid3 | 3.1.23-8.16.37.3.1 · SUSE:Linux Enterprise Server 11 SP4 | 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.
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-20-189 · Apr 1, 2020(Red Hat Enterprise Linux 7 Güvenlik Güncellemesi)
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.0/AV:N/AC:L/PR:N/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.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.