GNU Wget before 1.19.5 is prone to a cookie injection vulnerability in the resp_new function in http.c via a \r\n sequence in a continuation
Noroxi assessment
Priority: Monitor (action score 31/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: 16.4% (FIRST EPSS); higher than 96.9% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. A user must open a link or visit a page. No special conditions are required; it is repeatable.
- Fixed version: wget (Alpine:v3.10) 1.19.5-r0; wget (Alpine:v3.4) 1.18-r3; wget (Alpine:v3.5) 1.18-r4.
Low priority for now. Upgrade to wget (Alpine:v3.10) 1.19.5-r0; wget (Alpine:v3.4) 1.18-r3; wget (Alpine:v3.5) 1.18-r4 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
GNU Wget before 1.19.5 is prone to a cookie injection vulnerability in the resp_new function in http.c via a \r\n sequence in a continuation line.
- Published
- May 6, 2018
- Updated
- Jun 16, 2026
- EPSS
- 16.4% · 96th percentile
- CWE
- CWE-20
Report tools
Action score
31
Monitor
Low priority for now.
- CVSS
- 26 / 40 · 6.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 5 / 30 · 16.4%
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.
Running WordPress? Scan your site free with WP Lens
Noroxi 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 |
|---|---|---|
| gnu | wget | cpe:2.3:a:gnu:wget |
| canonical | ubuntu linux | cpe:2.3:o:canonical:ubuntu_linux |
| debian | debian linux | cpe:2.3:o:debian:debian_linux |
| redhat | enterprise linux desktop | cpe:2.3:o:redhat:enterprise_linux_desktop |
| redhat | enterprise linux server | cpe:2.3:o:redhat:enterprise_linux_server |
| redhat | enterprise linux workstation | cpe:2.3:o:redhat:enterprise_linux_workstation |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- canonical ubuntu linux12.04
- canonical ubuntu linux14.04
- canonical ubuntu linux16.04
- canonical ubuntu linux17.10
- canonical ubuntu linux18.04
- debian debian linux7.0
- debian debian linux8.0
- debian debian linux9.0
- gnu wgetbefore 1.19.5
- redhat enterprise linux desktop7.0
- redhat enterprise linux server7.0
- redhat enterprise linux workstation7.0
Versions reported by the vendor
Affected version ranges reported by the assigning authority (debian). Independent of NVD's CPE analysis and usually ahead of it.
n/a WGet
- WGetaffected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Alpine:v3.10 | wget | before 1.19.5-r0 | 1.19.5-r0 |
| Alpine:v3.4 | wget | before 1.18-r3 | 1.18-r3 |
| Alpine:v3.5 | wget | before 1.18-r4 | 1.18-r4 |
| Debian:12 | wget | before 1.19.5-1 | 1.19.5-1 |
| Debian:7 | wget | before 1.13.4-3+deb7u6 | 1.13.4-3+deb7u6 |
| Debian:8 | wget | before 1.16-1+deb8u5 | 1.16-1+deb8u5 |
| Debian:9 | wget | before 1.18-5+deb9u2 | 1.18-5+deb9u2 |
| openSUSE:Tumbleweed | wget | before 1.21.1-2.2 | 1.21.1-2.2 |
| Red Hat:enterprise_linux:7::client | wget | before 0:1.14-18.el7 | 0:1.14-18.el7 |
| Red Hat:enterprise_linux:7::client | wget-debuginfo | before 0:1.14-18.el7 | 0:1.14-18.el7 |
| SUSE:Linux Enterprise Desktop 12 SP3 | wget | before 1.14-21.7.1 | 1.14-21.7.1 |
| SUSE:Linux Enterprise Server 11 SP4 | wget | before 1.11.4-1.41.3.1 | 1.11.4-1.41.3.1 |
| SUSE:Linux Enterprise Server 11-SECURITY | wget-openssl1 | before 1.11.4-1.41.3.1 | 1.11.4-1.41.3.1 |
Same product
gnu: all recordsOther highest-scoring records for the same primary product.
- CVE-2017-13089GNU Wget: stack overflow in HTTP protocol handling59Plan
- CVE-2016-4971GNU wget before 1.18 allows remote servers to write to arbitrary files by redirecting a request from HTTP to a crafted FTP resource.49Plan
- CVE-2014-4877Absolute path traversal vulnerability in GNU Wget before 1.16, when recursion is enabled, allows remote FTP servers to write to arbitrary fi49Plan
- CVE-2017-13090GNU Wget: heap overflow in HTTP protocol handling46Plan
- CVE-2019-5953Buffer overflow in GNU Wget 1.20.1 and earlier allows remote attackers to cause a denial-of-service (DoS) or may execute an arbitrary code v41Plan
- CVE-2024-38428url.c in GNU Wget through 1.24.5 mishandles semicolons in the userinfo subcomponent of a URI, and thus there may be insecure behavior in whi36Monitor
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 |
|---|---|---|
| alpine:wget | 1.19.5-r0 · Alpine:v3.10 | Package registry (OSV) |
| debian:wget | 1.19.5-1 · Debian:12 | Package registry (OSV) |
| opensuse:wget | 1.21.1-2.2 · openSUSE:Tumbleweed | Package registry (OSV) |
| red hat:wget | 0:1.14-18.el7 · Red Hat:enterprise_linux:7::client | Package registry (OSV) |
| red hat:wget-debuginfo | 0:1.14-18.el7 · Red Hat:enterprise_linux:7::client | Package registry (OSV) |
| suse:wget | 1.11.4-1.41.3.1 · SUSE:Linux Enterprise Server 11 SP4 | Package registry (OSV) |
| suse:wget-openssl1 | 1.11.4-1.41.3.1 · SUSE:Linux Enterprise Server 11-SECURITY | 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 | local | 2018-05-06 |
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-1 d
- Published
- TodayOct 18, 2026+3086 d
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.
Credits
All researchersFinders, 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
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- A user must open a link or visit a page.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- high · data or configuration can be modified
- Availability
- none
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- High
- Availability impact
- None
Weakness class (CWE)
CWE-20 · Improper Input ValidationCVSS vector
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N
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.
Attack patterns (CAPEC)
- Buffer Overflow via Environment VariablesCAPEC-10likelihood: High · High
- Server Side Include (SSI) InjectionCAPEC-101likelihood: High · High
- Cross Zone ScriptingCAPEC-104likelihood: Medium · High
- Command Line Execution through SQL InjectionCAPEC-108likelihood: Low · Very High
- Object Relational Mapping InjectionCAPEC-109likelihood: Low · High
- SQL Injection through SOAP Parameter TamperingCAPEC-110likelihood: High · Very High
- Double EncodingCAPEC-120likelihood: Low · Medium
- Subverting Environment Variable ValuesCAPEC-13likelihood: High · Very High
ATT&CK techniques
- Obfuscated Files or InformationT1027
- Masquerading: Invalid Code SignatureT1036.001
- Steal Web Session CookieT1539
- Subvert Trust Controls: Code SigningT1553.002
- Impair Defenses:Impair Command History LoggingT1562.003
- Hijack Execution Flow:Dynamic Linker HijackingT1574.006
- Hijack Execution Flow:Path Interception by PATH Environment VariableT1574.007
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (10 more)Show less
- www.securitytracker.com/id/1040838
- access.redhat.com/errata/RHSA-2018:3052
- git.savannah.gnu.org/cgit/wget.git/commit/?id=1fc9c95ec144499e69dc8ec76dbe07799d7d82cd
- lists.debian.org/debian-lts-announce/2018/05/msg00006.html
- lists.gnu.org/archive/html/bug-wget/2018-05/msg00020.html
- savannah.gnu.org/bugs/?53763
- security.gentoo.org/glsa/201806-01
- usn.ubuntu.com/3643-1/
- usn.ubuntu.com/3643-2/
- www.debian.org/security/2018/dsa-4195
Vendor advisories and official records. Exploit/PoC links are deliberately left out.