CVE-2010-0734: content_encoding.c in libcurl 7.10.5 through 7.19.7, when zlib is enabled, does not properly restrict the amount of callback data sent to an…
Noroxi assessment
Priority: Monitor (action score 28/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 3.6% (FIRST EPSS); higher than 89.7% of all records.
- Fixed version: curl (Debian:12) 7.20.0-1; curl (Debian:5.0) 7.18.2-8lenny4; curl (Red Hat:enterprise_linux:3::as) 0:7.10.6-11.rhel3.
Low priority for now. Upgrade to curl (Debian:12) 7.20.0-1; curl (Debian:5.0) 7.18.2-8lenny4; curl (Red Hat:enterprise_linux:3::as) 0:7.10.6-11.rhel3 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
content_encoding.c in libcurl 7.10.5 through 7.19.7, when zlib is enabled, does not properly restrict the amount of callback data sent to an application that requests automatic decompression, which might allow remote attackers to cause a denial of service (application crash) or have unspecified other impact by sending crafted compressed data to an application that relies on the intended data-length limit.
- Published
- Mar 19, 2010
- Updated
- Jun 16, 2026
- EPSS
- 3.6% · 89th percentile
- CWE
- CWE-264
Report tools
Action score
28
Low priority for now.
- CVSS
- 27 / 40 · 6.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 3.6%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| curl | libcurl | cpe:2.3:a:curl:libcurl |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- curl libcurl7.10.5
- curl libcurl7.10.6
- curl libcurl7.10.7
- curl libcurl7.10.8
- curl libcurl7.11.0
- curl libcurl7.11.1
- curl libcurl7.11.2
- curl libcurl7.12
+12 more rows
- curl libcurl7.12.0
- curl libcurl7.12.1
- curl libcurl7.12.2
- curl libcurl7.12.3
- curl libcurl7.13
- curl libcurl7.13.1
- curl libcurl7.13.2
- curl libcurl7.14
- curl libcurl7.14.1
- curl libcurl7.15
- curl libcurl7.15.1
- curl libcurl7.15.2
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | curl | before 7.20.0-1 | 7.20.0-1 |
| Debian:5.0 | curl | before 7.18.2-8lenny4 | 7.18.2-8lenny4 |
| Red Hat:enterprise_linux:3::as | curl | before 0:7.10.6-11.rhel3 | 0:7.10.6-11.rhel3 |
| Red Hat:enterprise_linux:3::as | curl-debuginfo | before 0:7.10.6-11.rhel3 | 0:7.10.6-11.rhel3 |
| Red Hat:enterprise_linux:3::as | curl-devel | before 0:7.10.6-11.rhel3 | 0:7.10.6-11.rhel3 |
| Red Hat:enterprise_linux:4::as | curl | before 0:7.12.1-11.1.el4_8.3 | 0:7.12.1-11.1.el4_8.3 |
| Red Hat:enterprise_linux:4::as | curl-debuginfo | before 0:7.12.1-11.1.el4_8.3 | 0:7.12.1-11.1.el4_8.3 |
| Red Hat:enterprise_linux:4::as | curl-devel | before 0:7.12.1-11.1.el4_8.3 | 0:7.12.1-11.1.el4_8.3 |
| Red Hat:enterprise_linux:5::client_workstation | curl | before 0:7.15.5-9.el5 | 0:7.15.5-9.el5 |
| Red Hat:enterprise_linux:5::client_workstation | curl-debuginfo | before 0:7.15.5-9.el5 | 0:7.15.5-9.el5 |
| Red Hat:enterprise_linux:5::client_workstation | curl-devel | before 0:7.15.5-9.el5 | 0:7.15.5-9.el5 |
Same product
curl: all recordsOther highest-scoring records for the same primary product.
- CVE-2009-2417lib/ssluse.c in cURL and libcurl 7.4 through 7.19.5, when OpenSSL is used, does not properly handle a '\0' character in a domain name in…31Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| debian:curl | 7.20.0-1 · Debian:12 | Package registry (OSV) |
| red hat:curl | 0:7.15.5-9.el5 · Red Hat:enterprise_linux:5::client_workstation | Package registry (OSV) |
| red hat:curl-debuginfo | 0:7.15.5-9.el5 · Red Hat:enterprise_linux:5::client_workstation | Package registry (OSV) |
| red hat:curl-devel | 0:7.15.5-9.el5 · Red Hat:enterprise_linux:5::client_workstation | Package 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.
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Bug bounty scope
The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.
Not on record for this CVE: EPSS history · researcher credit · variant or chain candidate.
Technical details
Attack conditions
If successful
- Confidentiality
- P · data can be read
- Integrity
- P · data or configuration can be modified
- Availability
- P · the service can be disrupted
- Attack complexity
- M
- Confidentiality impact
- P
- Integrity impact
- P
- Availability impact
- P
Weakness class (CWE)
CWE-264 · Permissions, Privileges, and Access ControlsCVSS vector
AV:N/AC:M/Au:N/C:P/I:P/A:P
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (19 more)Show less
- curl.haxx.se/docs/security.html#20100209
- curl.haxx.se/libcurl-contentencoding.patch
- lists.apple.com/archives/security-announce/2010//Jun/msg00001.html
- lists.fedoraproject.org/pipermail/package-announce/2010-March/036744.html
- lists.fedoraproject.org/pipermail/package-announce/2010-March/037143.html
- secunia.com/advisories/38843
- secunia.com/advisories/38981
- secunia.com/advisories/39087
- secunia.com/advisories/39734
- secunia.com/advisories/40220
- secunia.com/advisories/45047
- secunia.com/advisories/48256
- security.gentoo.org/glsa/glsa-201203-02.xml
- support.apple.com/kb/HT4188
- support.avaya.com/css/P8/documents/100081819
- wiki.rpath.com/Advisories:rPSA-2010-0072
- www.debian.org/security/2010/dsa-2023
- www.mandriva.com/security/advisories?name=MDVSA-2010:062
- www.openwall.com/lists/oss-security/2010/02/09/5
Vendor advisories and official records. Exploit/PoC links are deliberately left out.