# What is CVE-2017-13090?

> CVE-2017-13090 is a high-severity flaw (CVSS 8.8) in Wget from Gnu, published on 27 October 2017. It is not on the list of flaws known to be exploited today. The latest forecast puts its chance of use in the next 30 days at 37%. If you run an affected version, plan in the vendor’s fix.

Canonical page: https://www.precursorintelligence.com/what-is/cve-2017-13090

## At a glance

- **Verdict:** Fix this soon. Not confirmed as exploited yet, but serious or likely enough that it should not wait for a quiet month.
- **Precursor Intelligence risk score:** 43 out of 100 (Medium); action: Plan remediation. Kept up to date as the evidence changes.
- **Severity:** High (CVSS 8.8 out of 10)
- **Known to be exploited:** No, not on the list of flaws known to be exploited today
- **Chance of use in the next 30 days:** 37% (latest exploit-likelihood forecast)
- **Published:** 27 October 2017
- **Record last updated:** 20 April 2025
- **Main product:** Wget from Gnu
- **Affected products:** 2

## What is CVE-2017-13090? In plain terms

It can be attacked from anywhere on the internet without logging in, but a person has to take an action first. If it works, the attacker can read data, change data and take it offline.

### The official description

The retr.c:fd_read_body() function is called when processing OK responses. When the response is sent chunked in wget before 1.19.2, the chunk parser uses strtol() to read each chunk's length, but doesn't check that the chunk length is a non-negative number. The code then tries to read the chunk in pieces of 8192 bytes by using the MIN() macro, but ends up passing the negative chunk length to retr.c:fd_read(). As fd_read() takes an int argument, the high 32 bits of the chunk length are discarded, leaving fd_read() with a completely attacker controlled length argument. The attacker can corrupt malloc metadata after the allocated buffer.

### What kind of flaw is it?

- CWE-119: Improper Restriction of Operations within the Bounds of a Memory Buffer
- CWE-122: Heap-based Buffer Overflow

### How an attack on it works

- Where an attacker can be: Anywhere on the internet
- How hard it is to pull off: Easy: no special conditions
- Login needed first: No login needed
- Does someone have to click: Yes, a person has to take an action
- What an attacker gets: Can read data, change data and take it offline

Severity vector: `CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`

## Is CVE-2017-13090 being exploited? Not that we know of

It is not on the list of flaws known to be exploited today. The latest forecast puts the chance of it being used in the next 30 days at 37%. That can change at any time, which is why we keep watching.

Exploit likelihood over the last 7 days: 37%, 37%, 37%, 37%, 37%, 37%, 37%.

### Timeline

- 27 October 2017: Published
- 20 April 2025: Record last updated
- 16 June 2026: Exploit likelihood jumped

### How Precursor Intelligence ranks it

CVE-2017-13090 scores **43 out of 100 (Medium)**, with the action "Plan remediation".

Every published flaw gets a risk score from 0 to 100, kept up to date as the evidence changes. Four things go into the score, from the one that counts most to the ones that count less:

- Evidence it is being exploited: biggest factor
- How severe it is: strong factor
- How widely exposed it is: smaller factor
- Threat activity around it: smaller factor

85 and above is Critical. Anything confirmed as exploited is always marked for an emergency patch, whatever its score. When this flaw matches software you track, it lands in your list with its score and the reasons behind it.

## Who is affected by CVE-2017-13090?

The published record lists 2 products.

- [Wget](https://www.precursorintelligence.com/product/gnu/wget) by [Gnu](https://www.precursorintelligence.com/vendors/gnu) (Application): up to 1.19.1
- [Debian Linux](https://www.precursorintelligence.com/product/debian/debian_linux) by [Debian](https://www.precursorintelligence.com/vendors/debian) (Operating system): 8.0, 9.0

## How do I fix CVE-2017-13090?

1. **Check whether you run it.** Compare your versions with the affected products above. Not sure what you run? Precursor Intelligence can work it out from your public website, or you can pick it from a list.
2. **Apply the vendor’s fix.** Install the update named in the vendor’s advisory. We’ve put the advisories and patch notes first in the list.
3. **If you can’t patch today.** Follow any mitigation the vendor publishes, and limit who can reach the affected system from the internet until the update is in.
4. **Keep an eye on it.** Track the product and we tell you as soon as we spot this flaw on the list of exploited flaws, or a jump in its exploit likelihood.

### References

- [git.savannah.gnu.org](http://git.savannah.gnu.org/cgit/wget.git/commit/?id=ba6b44f6745b14dce414761a8e4b35d31b176bba) (Issue tracking, Patch, Third-party advisory)
- [viestintavirasto.fi](https://www.viestintavirasto.fi/en/cybersecurity/vulnerabilities/2017/haavoittuvuus-2017-037.html) (Issue tracking, Patch, Third-party advisory)
- [debian.org](http://www.debian.org/security/2017/dsa-4008) (Issue tracking, Third-party advisory)
- [securityfocus.com](http://www.securityfocus.com/bid/101590) (Issue tracking, Third-party advisory, Vulnerability database)
- [securitytracker.com](http://www.securitytracker.com/id/1039661) (Issue tracking, Third-party advisory, Vulnerability database)
- [access.redhat.com](https://access.redhat.com/errata/RHSA-2017:3075)
- [security.gentoo.org](https://security.gentoo.org/glsa/201711-06) (Issue tracking, Third-party advisory)
- [synology.com](https://www.synology.com/support/security/Synology_SA_17_62_Wget)

## Questions

### What is CVE-2017-13090?

CVE-2017-13090 is a high-severity flaw in Wget from Gnu, published on 27 October 2017. It can be attacked from anywhere on the internet without logging in, but a person has to take an action first. If it works, the attacker can read data, change data and take it offline.

### How serious is CVE-2017-13090?

It scores 8.8 out of 10 on the CVSS severity scale, which is high. Our risk score for CVE-2017-13090 is 43 out of 100, which is Medium. Its action is "Plan remediation". Not confirmed as exploited yet, but serious or likely enough that it should not wait for a quiet month.

### Is CVE-2017-13090 being exploited?

It is not on the list of flaws known to be exploited today. The latest forecast puts the chance of it being used in the next 30 days at 37%. That can change at any time, which is why we keep watching.

### Which versions does CVE-2017-13090 affect?

For Wget from Gnu: up to 1.19.1. The record lists 2 products in all, each with its versions, under "Who is affected" on this page.

### How do I fix CVE-2017-13090?

Install the update the vendor names in its advisory, linked first under "How do I fix" on this page. If you can't patch today, follow the vendor's mitigation and limit who can reach the affected system from the internet.

## Does CVE-2017-13090 affect you?

Precursor Intelligence keeps checking for you:

- **Tell us what you run.** Pick your software from a list, or let us work it out from your website.
- **We match it to every flaw.** Over 400,000 published flaws, checked against your list.
- **Ranked by real-world risk.** Every flaw gets a 0 to 100 risk score, kept up to date, led by evidence criminals are using it.
- **Told as soon as we know.** An alert by email, in the app or by webhook to your own tools.

Start free (no card, nothing to install): https://www.precursorintelligence.com/register
Book a demo: https://www.precursorintelligence.com/contact