CVE-2018-1000027
What it is
The Squid Software Foundation Squid HTTP Caching Proxy version prior to version 4.0.23 contains a NULL Pointer Dereference vulnerability in HTTP Response X-Forwarded-For header processing that can result in Denial of Service to all clients of the proxy. This attack appear to be exploitable via Remote HTTP server responding with an X-Forwarded-For header to certain types of HTTP request. This vulnerability appears to have been fixed in 4.0.23 and later.
At a glance
- Exploitability
- Can be exploited over the network without logging in. High risk of service disruption.
- Exploit odds
- 12.9% chance of exploitation in the next 30 days (EPSS). Higher than most.
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 12.9% in the next 30 days (EPSS).
- Severity: 7.5 HIGH (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 12.9% · EPSS, next 30 days
- Weakness
- CWE-476 · NULL pointer dereference
- Record status
- Modified
Affected
- squid-cache Squid < 4.0.23
- Debian Linux 7.0
- Debian Linux 8.0
- Debian Linux 9.0
- Canonical Ubuntu Linux 14.04
- Canonical Ubuntu Linux 16.04
- Canonical Ubuntu Linux 17.10
Attack profile CVSS 3.0 · 7.5
- Attack vector
- Network
- Complexity
- Low
- Privileges needed
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
Raw vector
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2018-1000027.md and follow it. Check whether this project is affected by CVE-2018-1000027. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- http://www.squid-cache.org/Advisories/SQUID-2018_2.txt
- http://www.squid-cache.org/Versions/v3/3.5/changesets/SQUID-2018_2.patch
- http://www.squid-cache.org/Versions/v4/changesets/SQUID-2018_2.patch
- https://github.com/squid-cache/squid/pull/129/files
- http://www.squid-cache.org/Advisories/SQUID-2018_2.txt
- http://www.squid-cache.org/Versions/v3/3.5/changesets/SQUID-2018_2.patch
- http://www.squid-cache.org/Versions/v4/changesets/SQUID-2018_2.patch
- https://github.com/squid-cache/squid/pull/129/files
References
- http://www.squid-cache.org/Advisories/SQUID-2018_2.txt
- http://www.squid-cache.org/Versions/v3/3.5/changesets/SQUID-2018_2.patch
- http://www.squid-cache.org/Versions/v4/changesets/SQUID-2018_2.patch
- https://github.com/squid-cache/squid/pull/129/files
- https://lists.debian.org/debian-lts-announce/2018/02/msg00001.html
- https://lists.debian.org/debian-lts-announce/2018/02/msg00002.html
- https://usn.ubuntu.com/3557-1/
- https://usn.ubuntu.com/4059-2/
- https://www.debian.org/security/2018/dsa-4122
- http://www.squid-cache.org/Advisories/SQUID-2018_2.txt
- http://www.squid-cache.org/Versions/v3/3.5/changesets/SQUID-2018_2.patch
- http://www.squid-cache.org/Versions/v4/changesets/SQUID-2018_2.patch
- https://github.com/squid-cache/squid/pull/129/files
- https://lists.debian.org/debian-lts-announce/2018/02/msg00001.html
- https://lists.debian.org/debian-lts-announce/2018/02/msg00002.html
- https://usn.ubuntu.com/3557-1/
- https://usn.ubuntu.com/4059-2/
- https://www.debian.org/security/2018/dsa-4122