CVE-2014-6270: Buffer Overflow
Last updated 24 July 2024
Other sources
Off-by-one error in the snmpHandleUdp function in snmpcore.cc in Squid 2.x and 3.x, when an SNMP port is configured, allows remote attackers to cause a denial of service (crash) or possibly execute arbitrary code via a crafted UDP SNMP request, which triggers a heap-based buffer overflow.
— Launchpad
Sebastian Krahmer discovered an off-by-one error, leading to a heap-based buffer overflow flaw, in the way Squid handled UDP SNMP requests. An unauthenticated, remote attacker could possibly use this flaw to crash Squid or, potentially, execute arbitrary code.
As noted in Sebastian's original report, an SNMP port must be configured. The default configuration of Squid for Red Hat Enterprise Linux 6 and 7 does not include an snmpport declaration (http://wiki.squid-cache.org/Features/Snmp).
Patch:
http://bugzillafiles.novell.org/attachment.cgi?id=605545
References:
https://bugzilla.novell.com/showbug.cgi?id=895773 http://seclists.org/oss-sec/2014/q3/542
— Red Hat
Affected Software
Remediation
Patch Available
Event History
Frequently Asked Questions
What is the severity of CVE-2014-6270?
CVE-2014-6270 has been classified as a medium risk vulnerability due to its potential to cause denial of service or arbitrary code execution.
How do I fix CVE-2014-6270?
To mitigate CVE-2014-6270, it is recommended to upgrade to a patched version of Squid, specifically versions 4.13-10+deb11u3, 5.7-2+deb12u2, or 6.12-1.
What types of systems are affected by CVE-2014-6270?
CVE-2014-6270 affects multiple versions of the Squid Web Proxy Cache, particularly versions from 2.x to 3.x.
What exploitation vector does CVE-2014-6270 utilize?
CVE-2014-6270 can be exploited by sending a crafted UDP SNMP request to the configured SNMP port of affected Squid instances.
What are the potential impacts of CVE-2014-6270?
The impacts of CVE-2014-6270 include a crash of the Squid service and possible arbitrary code execution.