CVE-2009-0037: The redirect implementation in curl and libcurl 5.11 through 7.19.3, when CURLOPT_FOLLOWLOCATION is enabled, accepts arbitrary Location…
Noroxi assessment
Priority: Monitor (action score 30/100)
- Public proof-of-concept code exists (Exploit-DB); there is no record of exploitation in the wild.
- Probability of exploitation in the next 30 days: 9% (FIRST EPSS); higher than 95.3% of all records.
- Fixed version: curl (Debian:12) 7.18.2-8.1; curl (Debian:4.0) 7.15.5-1etch2; curl (Debian:5.0) 7.18.2-8lenny2.
Low priority for now. Upgrade to curl (Debian:12) 7.18.2-8.1; curl (Debian:4.0) 7.15.5-1etch2; curl (Debian:5.0) 7.18.2-8lenny2 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
The redirect implementation in curl and libcurl 5.11 through 7.19.3, when CURLOPT_FOLLOWLOCATION is enabled, accepts arbitrary Location values, which might allow remote HTTP servers to (1) trigger arbitrary requests to intranet servers, (2) read or overwrite arbitrary files via a redirect to a file: URL, or (3) execute arbitrary commands via a redirect to an scp: URL.
- Published
- Mar 4, 2009
- Updated
- Jun 16, 2026
- EPSS
- 9.0% · 95th percentile
- CWE
- CWE-352
Report tools
Action score
30
Low priority for now.
- CVSS
- 27 / 40 · 6.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 3 / 30 · 9.0%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- Proof of concept exists, no weaponized module
- 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.
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- curl curl5.11
- curl curl6.0
- curl curl6.1beta
- curl curl6.2
- curl curl6.3
- curl curl6.3.1
- curl curl6.4
- curl curl6.5
+12 more rows
- curl curl6.5.1
- curl curl6.5.2
- curl curl7.1
- curl curl7.1.1
- curl curl7.10
- curl curl7.10.1
- curl curl7.10.2
- curl curl7.10.3
- curl curl7.10.4
- curl curl7.10.5
- curl curl7.10.6
- curl curl7.10.7
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.18.2-8.1 | 7.18.2-8.1 |
| Debian:4.0 | curl | before 7.15.5-1etch2 | 7.15.5-1etch2 |
| Debian:5.0 | curl | before 7.18.2-8lenny2 | 7.18.2-8lenny2 |
| openSUSE:Tumbleweed | curl | before 7.51.0-1.1 | 7.51.0-1.1 |
| Red Hat:enterprise_linux:2.1::as | curl | before 0:7.8-3.rhel2 | 0:7.8-3.rhel2 |
| Red Hat:enterprise_linux:2.1::as | curl-devel | before 0:7.8-3.rhel2 | 0:7.8-3.rhel2 |
| Red Hat:enterprise_linux:3::as | curl | before 0:7.10.6-9.rhel3 | 0:7.10.6-9.rhel3 |
| Red Hat:enterprise_linux:3::as | curl-debuginfo | before 0:7.10.6-9.rhel3 | 0:7.10.6-9.rhel3 |
| Red Hat:enterprise_linux:3::as | curl-devel | before 0:7.10.6-9.rhel3 | 0:7.10.6-9.rhel3 |
| Red Hat:enterprise_linux:4::as | curl | before 0:7.12.1-11.1.el4_7.1 | 0:7.12.1-11.1.el4_7.1 |
| Red Hat:enterprise_linux:4::as | curl-debuginfo | before 0:7.12.1-11.1.el4_7.1 | 0:7.12.1-11.1.el4_7.1 |
| Red Hat:enterprise_linux:4::as | curl-devel | before 0:7.12.1-11.1.el4_7.1 | 0:7.12.1-11.1.el4_7.1 |
| Red Hat:enterprise_linux:5::client_workstation | curl | before 0:7.15.5-2.1.el5_3.4 | 0:7.15.5-2.1.el5_3.4 |
| Red Hat:enterprise_linux:5::client_workstation | curl-debuginfo | before 0:7.15.5-2.1.el5_3.4 | 0:7.15.5-2.1.el5_3.4 |
| Red Hat:enterprise_linux:5::client_workstation | curl-devel | before 0:7.15.5-2.1.el5_3.4 | 0:7.15.5-2.1.el5_3.4 |
Same product
curl: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-94265Authorization: Negotiate sent to foreign origin36Monitor
- CVE-2026-92388FTP wildcard write callback mixup36Monitor
- CVE-2026-87866wolfSSL public-key pinning bypass36Monitor
Published before and after this one in the same product
- ← EarlierCVE-2005-3185Oct 13, 2005 · Stack-based buffer overflow in the ntlm_output function in http-ntlm.c for (1) wget 1.10, (2) curl 7.13.2, and (3) libcurl 7.13.2, and…32Monitor
- Later →CVE-2010-3842Oct 27, 2010 · Absolute path traversal vulnerability in curl 7.20.0 through 7.21.1, when the --remote-header-name or -J option is used, allows remote…24Monitor
- Later →CVE-2012-0036Apr 13, 2012 · curl and libcurl 7.2x before 7.24.0 do not properly consider special characters during extraction of a pathname from a URL, which allows…35Monitor
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.18.2-8.1 · Debian:12 | Package registry (OSV) |
| opensuse:curl | 7.51.0-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| red hat:curl | 0:7.8-3.rhel2 · Red Hat:enterprise_linux:2.1::as | Package registry (OSV) |
| red hat:curl-debuginfo | 0:7.10.6-9.rhel3 · Red Hat:enterprise_linux:3::as | Package registry (OSV) |
| red hat:curl-devel | 0:7.8-3.rhel2 · Red Hat:enterprise_linux:2.1::as | Package registry (OSV) |
Exploit status
Proof of concept available
A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.
Evidence
- Exploit-DB entry ×1
Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.
| Source | Kind | Date |
|---|---|---|
| Exploit-DB entry | remote | 2009-03-03 |
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.
- First PoC-2 d
- Published
- TodayNov 16, 2026+6466 d
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
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: patch commit or PR link · 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-352 · Cross-Site Request Forgery (CSRF)CVSS vector
AV:N/AC:M/Au:N/C:P/I:P/A:P
nvd-primary
Root cause
State-changing requests rely on the session cookie the browser sends automatically; nothing verifies that the request came from the user’s own page.
The bug in code
The whole CWE-352 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
app.use(session({ cookie: { httpOnly: true } }));
app.post("/account/address", updateAddress);Fixed
app.use(session({ cookie: { httpOnly: true, sameSite: "lax" } }));
app.post("/account/address", csrfProtection, updateAddress);Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
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/lxr/source/CHANGES
- lists.apple.com/archives/security-announce/2010//Mar/msg00001.html
- lists.opensuse.org/opensuse-security-announce/2009-03/msg00001.html
- lists.vmware.com/pipermail/security-announce/2009/000060.html
- secunia.com/advisories/34138
- secunia.com/advisories/34202
- secunia.com/advisories/34237
- secunia.com/advisories/34251
- secunia.com/advisories/34255
- secunia.com/advisories/34259
- secunia.com/advisories/34399
- secunia.com/advisories/35766
- security.gentoo.org/glsa/glsa-200903-21.xml
- slackware.com/security/viewer.php?l=slackware-security&y=2009&m=slackware-security.476602
- support.apple.com/kb/HT4077
- wiki.rpath.com/wiki/Advisories:rPSA-2009-0042
- www.debian.org/security/2009/dsa-1738
- www.redhat.com/support/errata/RHSA-2009-0341.html
- www.securityfocus.com/archive/1/501757/100/0/threaded
Vendor advisories and official records. Exploit/PoC links are deliberately left out.