What is CVE-2019-9517?A high-severity flaw in Swiftnio, explained.
CVE-2019-9517 is a high-severity flaw (CVSS 7.5) in Swiftnio from Apple, published on 13 August 2019. 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 28%. If you run an affected version, plan in the vendor’s fix.
Published 13 August 2019. Record last updated 14 January 2025. We keep this page's data up to date.
What is CVE-2019-9517? In plain terms.
It can be attacked from anywhere on the internet without logging in, and nobody has to click anything. If it works, the attacker can take it offline.
Some HTTP/2 implementations are vulnerable to unconstrained interal data buffering, potentially leading to a denial of service. The attacker opens the HTTP/2 window so the peer can send without constraint; however, they leave the TCP window closed so the peer cannot actually write (many of) the bytes on the wire. The attacker then sends a stream of requests for a large response object. Depending on how the servers queue the responses, this can consume excess memory, CPU, or both.
What kind of flaw is it?
- CWE-400Uncontrolled Resource Consumption
- CWE-770Allocation of Resources Without Limits or Throttling
How an attack on it works
Read straight from its severity rating, translated out of the shorthand.
- Where an attacker can beAnywhere on the internet
- How hard it is to pull offEasy: no special conditions
- Login needed firstNo login needed
- Does someone have to clickNo, nobody has to do anything
- What an attacker getsCan take it offline
Severity vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Is CVE-2019-9517 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 28%. That can change at any time, which is why we keep watching.
Timeline
- Published
- Record last updated
- Exploit likelihood jumped
- Exploit likelihood fell
CVE-2019-9517 scores 49. Action: Plan remediation.
We keep the score of every published flaw up to date as the evidence changes. Four things go into the score, and evidence that criminals are actually using it counts most. In order:
- Evidence it is being exploitedBiggest factor
- How severe it isStrong factor
- How widely exposed it isSmaller factor
- Threat activity around itSmaller factor
85 and above is Critical. Anything confirmed as exploited is always marked for an emergency patch, whatever its score.
When CVE-2019-9517 matches software you track, it lands in your list with its score and the reasons behind it.
See your own ranked list →Who is affected by CVE-2019-9517? 25 products.
The published record lists 25 products from 12 vendors. Versions are shown as published: "8.9.0 to before 8.16.1" means from 8.9.0 up to, but not including, 8.16.1. If you run one of these, check your version, then go to the fix below.
- Application
Swiftnio
by Apple
Affected versions1.0.0 to 1.4.0 - Application
Node.js
by Nodejs
Affected versions8.0.0 to 8.8.18.9.0 to before 8.16.110.0.0 to 10.12.010.13.0 to before 10.16.312.0.0 to before 12.8.1 - Application
Communications Element Manager
by Oracle
Affected versions8.0.08.1.08.1.18.2.0 - Application
Traffic Server
by Apache
Affected versions6.0.0 to 6.2.37.0.0 to 7.1.68.0.0 to 8.0.3 - Application
Web Gateway
by Mcafee
Affected versions7.7.2.0 to before 7.7.2.247.8.2.0 to before 7.8.2.138.1.0 to before 8.2.0 - Operating system
Debian Linux
by Debian
Affected versions9.010.0 - Operating system
Fedora
Affected versions2930 - Application
Jboss Enterprise Application Platform
by Red Hat
Affected versions7.2.07.3.0 - Operating system
Leap
by Opensuse
Affected versions15.015.1
How do I fix CVE-2019-9517? Four steps.
- Check whether you run itCompare 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.
- Apply the vendor’s fixInstall the update named in the vendor’s advisory. We’ve put the advisory first in the list.
- If you can’t patch todayFollow any mitigation the vendor publishes, and limit who can reach the affected system from the internet until the update is in.
- Keep an eye on itTrack 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
47 links- Cpuoct2019 5072832 (opens in a new tab)oracle.com
- Msg00004 (opens in a new tab)opensuse.org · 2019
- Msg00031 (opens in a new tab)opensuse.org · 2019
- Msg00032 (opens in a new tab)opensuse.org · 2019
- oss-security mailing list post, 15 Aug 2019 (opens in a new tab)openwall.com · 2019
- RHSA 2019:2893 (opens in a new tab)redhat.com
Does CVE-2019-9517 affect you? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 new flaw affects software Acme tracks
Some HTTP/2 implementations are vulnerable to unconstrained interal data buffering, potentially leading to a denial of service. The attacker opens the HTTP/2...
- Matched to
- Swiftnio on Acme's software list
- What to do
- Plan in the vendor’s update
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
CVE-2019-9517 is a high-severity flaw in Swiftnio from Apple, published on 13 August 2019. It can be attacked from anywhere on the internet without logging in, and nobody has to click anything. If it works, the attacker can take it offline.
It scores 7.5 out of 10 on the CVSS severity scale, which is high. Our risk score for CVE-2019-9517 is 49 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.
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 28%. That can change at any time, which is why we keep watching.
For Swiftnio from Apple: 1.0.0 to 1.4.0. The record lists 25 products in all, each with its versions, under "Who is affected" on this page.
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.