Vulnerability Assessment & Network Security Forums
If through a vulnerability assessment, a network security issue is detected for the vulnerability below, applying the appropriate security patches in a timely matter is very important. If you have detected that your system has already been compromised, following CERT's Network Security recovery document will assist with recommended steps for system recovery.
Vulnerability Assessment Details
cURL: Off-by-one errors in URL handling
Detailed Explanation for this Vulnerability Assessment
The remote host is affected by the vulnerability described in GLSA-200512-09
(cURL: Off-by-one errors in URL handling)
Stefan Esser from the Hardened-PHP Project has reported a
vulnerability in cURL that permits for a local buffer overflow when cURL
attempts to parse specially crafted URLs. The URL can be specially
crafted in one of two ways: the URL could be malformed in a way that
prevents a terminating null byte from being added to either a hostname
or path buffer
or the URL could contain a "?" separator in the
hostname portion, which causes a "/" to be prepended to the resulting
A possible hacker capable of getting cURL to parse a maliciously crafted
URL could cause a denial of service or execute arbitrary code with the
rights of the user making the call to cURL. A possible hacker could also
escape open_basedir or safe_mode pseudo-restrictions when exploiting
this problem from within a PHP program when PHP is compiled with
There is no known workaround at this time.
All cURL users should upgrade to the latest version:
# emerge --sync
# emerge --ask --oneshot --verbose ">=net-misc/curl-7.15.1"
Network Security Threat Level: Low
Networks Security ID:
Vulnerability Assessment Copyright: (C) 2005 Michel Arboi
|SanDisk SD8SB8U-512G-1122 512GB x400 SATA 2.5 SSD Solid State Drive - SKU#930678
|SK Hynix HFS128G3AMNB 2200A AD 128GB 1.8" mSATA Solid State Drive
|ORICO 5Gbps USB 3.0 PC MAC Hard Drive Disk Enclosure Case For 2.5 inch HHD SSD
|Transcend 128 GB External Solid State Drive - USB 3.0
No Discussions have been posted on this vulnerability.