Open-Source Security Intelligence

Know every vulnerability
before it knows you.

DevGuard continuously monitors your dependencies and alerts you when CVEs like this one affect your stack — with real-time threat intelligence built for developers.

Search

CURL-CVE-2014-3613

Published Sep 10, 2014·Last modified Apr 25, 2026
Affected Components(0)

No affected components available

Description

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 129.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.

Risk Scores
Base Score
0.0

Measures severity based on intrinsic characteristics of the vulnerability, independent of environment.

Threat Intelligence
0.0

No exploitation activity has been observed at this time. Continue routine monitoring.

EPSS
N/A

Probability that this vulnerability will be exploited in the wild within the next 30 days.

Exploit
Not available

We did not find any exploit available. Neither in GitHub repositories nor in the Exploit-Database.

Scan your project

Continuously monitor your dependencies and get alerted when vulnerabilities like this one affect your stack.

Checkout DevGuard