| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.6 | $0-$5k | 0.00 |
Summary
A vulnerability was found in cURL and libcURL up to 7.31.1. It has been classified as critical. This impacts an unknown function of the component Domain Name Handler. Performing a manipulation results in cryptographic issue. This vulnerability is reported as CVE-2014-3613. No exploit exists. Upgrading the affected component is recommended.
Details
A vulnerability classified as critical has been found in cURL and libcURL up to 7.31.1 (Network Utility Software). This affects an unknown code block of the component Domain Name Handler. The manipulation with an unknown input leads to a cryptographic issue vulnerability. CWE is classifying the issue as CWE-310. This is going to have an impact on integrity.
The weakness was disclosed 09/10/2014 by Tim Ruehsen as libcurl cookie leak with IP address as domain as confirmed advisory (Website). It is possible to read the advisory at curl.haxx.se. This vulnerability is uniquely identified as CVE-2014-3613 since 05/14/2014. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. The technical details are unknown and an exploit is not publicly available. The attack technique deployed by this issue is T1600 according to MITRE ATT&CK. The advisory points out:
By not detecting and rejecting domain names for partial literal IP addresses properly when parsing received HTTP cookies, libcurl can be fooled to both sending cookies to wrong sites and into allowing arbitrary sites to set cookies for others. For this problem to trigger, the client application must use the numerical IP address in the URL to access the site and the site must send back cookies to the site using domain= and a partial IP address. Since libcurl wrongly approaches the IP address like it was a normal domain name, a site at IP address 192.168.0.1 can set cookies for anything ending with .168.0.1 thus fooling libcurl to send them also to for example 127.168.0.1. The flaw requires dots to be present in the IP address, which restricts the flaw to IPv4 literal addresses or IPv6 addresses using the somewhat unusual "dotted-quad" style: "::ffff:192.0.2.128" This is not believed to be done by typical sites as this is not supported by clients that adhere to the rules of the RFC 6265, and many sites are written to explicitly use their own specific named domain when sending cookies.
The vulnerability was handled as a non-public zero-day exploit for at least 26 days. During that time the estimated underground price was around $0-$5k. The vulnerability scanner Nessus provides a plugin with the ID 78093 (Fedora 19 : curl-7.29.0-23.fc19 (2014-10714)), which helps to determine the existence of the flaw in a target environment. It is assigned to the family Fedora Local Security Checks and running in the context l. The commercial vulnerability scanner Qualys is able to test this issue with plugin 43619 (Juniper Junos OS Multiple vulnerabilities in cURL versions (JSA10874)).
Upgrading to version 7.38.0 eliminates this vulnerability. The upgrade is hosted for download at curl.haxx.se. A possible mitigation has been published immediately after the disclosure of the vulnerability.
The vulnerability is also documented in the databases at X-Force (95925), Tenable (78093), SecurityFocus (BID 69748†) and Vulnerability Center (SBV-58214†). Further details are available at bugzilla.redhat.com. The entries VDB-8439, VDB-9262, VDB-10906 and VDB-11245 are pretty similar. Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Type
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 4.6
VulDB Base Score: 5.3
VulDB Temp Score: 4.6
VulDB Vector: 🔍
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Cryptographic issueCWE: CWE-310
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Unproven
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Nessus ID: 78093
Nessus Name: Fedora 19 : curl-7.29.0-23.fc19 (2014-10714)
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍
Nessus Port: 🔍
OpenVAS ID: 703022
OpenVAS Name: Debian Security Advisory DSA 3022-1 (curl - security update)
OpenVAS File: 🔍
OpenVAS Family: 🔍
Qualys ID: 🔍
Qualys Name: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍
Upgrade: cURL/libcURL 7.38.0
Timeline
05/14/2014 🔍08/15/2014 🔍
09/10/2014 🔍
09/10/2014 🔍
09/11/2014 🔍
09/12/2014 🔍
10/09/2014 🔍
11/18/2014 🔍
04/13/2016 🔍
04/14/2016 🔍
02/15/2022 🔍
Sources
Advisory: libcurl cookie leak with IP address as domainResearcher: Tim Ruehsen
Status: Confirmed
Confirmation: 🔍
CVE: CVE-2014-3613 (🔍)
GCVE (CVE): GCVE-0-2014-3613
GCVE (VulDB): GCVE-100-67527
OVAL: 🔍
X-Force: 95925 - cURL/libcURL IP address security bypass, Medium Risk
SecurityFocus: 69748 - cURL/libcURL CVE-2014-3613 Remote Security Bypass Vulnerability
Vulnerability Center: 58214 - cURL 7.1 through 7.37.1 Remote Bypass Restrictions due to Improper Detect and Reject Domain Names, Medium
Misc.: 🔍
See also: 🔍
Entry
Created: 09/12/2014 10:14Updated: 02/15/2022 22:51
Changes: 09/12/2014 10:14 (89), 02/04/2019 16:14 (1), 02/15/2022 22:51 (3)
Complete: 🔍
Cache ID: 216:8AB:103
No comments yet. Languages: en.
Please log in to comment.