Skip to content
Noroxi
CVE-2013-1944· NVD / CVE Program· CNA redhat

The tailMatch function in cookie.c in cURL and libcurl before 7.30.0 does not properly match the path domain when sending cookies, which all

The tailMatch function in cookie.c in cURL and libcurl before 7.30.0 does not properly match the path domain when sending cookies, which allows remote attackers to steal cookies via a matching suffix in the domain of a URL.

MediumCVSS 5.0 · v2.0—No exploit Fix available
Published
Apr 29, 2013
Updated
Jun 16, 2026
EPSS
4.3% · 91th percentile
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

21

Monitor

Low priority for now.

CVSS
20 / 40 · 5.0 / 10
CISA KEV
0 / 30 · Not listed
EPSS
1 / 30 · 4.3%

Affected systems

VendorProduct
haxxcurl
haxxlibcurl
canonicalubuntu linux

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • canonical ubuntu linux10.04
  • canonical ubuntu linux11.10
  • canonical ubuntu linux12.04
  • canonical ubuntu linux12.10
  • canonical ubuntu linux8.04
  • haxx curlup to 7.29.0 inclusive
  • haxx curl6.0
  • haxx curl6.1
  • haxx curl6.2
  • haxx curl6.3
  • haxx curl6.3.1
  • haxx curl6.4
  • haxx curl6.5
  • haxx curl6.5.1
  • haxx curl6.5.2
  • haxx curl7.1
  • haxx curl7.1.1
  • haxx curl7.10
  • haxx curl7.10.1
  • haxx curl7.10.2

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12curlbefore 7.29.0-2.17.29.0-2.1
Debian:6.0curlbefore 7.21.0-2.1+squeeze37.21.0-2.1+squeeze3
openSUSE:Tumbleweedcurlbefore 7.51.0-1.17.51.0-1.1
Red Hat:enterprise_linux:5::servercurlbefore 0:7.15.5-16.el5_90:7.15.5-16.el5_9
Red Hat:enterprise_linux:5::servercurl-debuginfobefore 0:7.15.5-16.el5_90:7.15.5-16.el5_9
Red Hat:enterprise_linux:5::servercurl-develbefore 0:7.15.5-16.el5_90:7.15.5-16.el5_9
Red Hat:enterprise_linux:6::clientcurlbefore 0:7.19.7-36.el6_40:7.19.7-36.el6_4
Red Hat:enterprise_linux:6::clientcurl-debuginfobefore 0:7.19.7-36.el6_40:7.19.7-36.el6_4
Red Hat:enterprise_linux:6::clientlibcurlbefore 0:7.19.7-36.el6_40:7.19.7-36.el6_4
Red Hat:enterprise_linux:6::clientlibcurl-develbefore 0:7.19.7-36.el6_40:7.19.7-36.el6_4

Same product

haxx: all records

Other highest-scoring records for the same primary product.

  • CVE-2021-22901curl 7.75.0 through 7.76.1 suffers from a use-after-free vulnerability resulting in already freed memory being used when a TLS 1.3 session t
    50Plan
  • CVE-2023-38039When curl retrieves an HTTP response, it stores the incoming headers so that they can be accessed later via the libcurl headers API.
    47Plan
  • CVE-2024-2398HTTP/2 push headers memory-leak
    45Plan
  • CVE-2019-5482Heap buffer overflow in the TFTP protocol handler in cURL 7.19.4 to 7.65.3.
    44Plan
  • CVE-2017-8817The FTP wildcard function in curl and libcurl before 7.57.0 allows remote attackers to cause a denial of service (out-of-bounds read and app
    42Plan
  • CVE-2017-8816The NTLM authentication feature in curl and libcurl before 7.57.0 on 32-bit platforms allows attackers to cause a denial of service (integer
    42Plan

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
debian:curl7.29.0-2.1 · Debian:12Package registry (OSV)
opensuse:curl7.51.0-1.1 · openSUSE:TumbleweedPackage registry (OSV)
red hat:curl0:7.15.5-16.el5_9 · Red Hat:enterprise_linux:5::serverPackage registry (OSV)
red hat:curl-debuginfo0:7.15.5-16.el5_9 · Red Hat:enterprise_linux:5::serverPackage registry (OSV)
red hat:curl-devel0:7.15.5-16.el5_9 · Red Hat:enterprise_linux:5::serverPackage registry (OSV)
red hat:libcurl0:7.19.7-36.el6_4 · Red Hat:enterprise_linux:6::clientPackage registry (OSV)
red hat:libcurl-devel0:7.19.7-36.el6_4 · Red Hat:enterprise_linux:6::clientPackage registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days-1% in 7 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • No special conditions are required; it is repeatable.

If successful

Confidentiality
P · data can be read
Integrity
none
Availability
none
Attack complexity
Low
Confidentiality impact
P
Integrity impact
None
Availability impact
None

CVSS vector

AV:N/AC:L/Au:N/C:P/I:N/A:N

nvd-primary

Root cause

The extension requests broader permissions than its function needs and sends the data it collects out for purposes beyond its stated function.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

json
{  "permissions": ["tabs", "<all_urls>"],  "background": { "service_worker": "analytics.js" }}

Fixed

json
{  "permissions": ["activeTab"],  "host_permissions": ["https://yildiz.example/*"]}

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records