Swiftnio vulnerabilitiesRanked by how likely they are to be used.
Swiftnio is made by Apple. We track 10 published vulnerabilities listed under that exact name, across 78 versions. None of them is on the list of flaws known to be exploited today. Apple lists newer releases under their own names, such as Swiftnio Http/2, so check those pages too.
We keep watching the known-exploited list.
Is Swiftnio listed under other names? Yes.
Apple also lists Swiftnio under more specific names, such as Swiftnio Http/2 and Swiftnio SSL. Flaws listed only under those names are counted on their own pages, not here. If you run one of these, open its page for its own exploited flaws.
Which Swiftnio vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Swiftnio's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Swiftnio flaws are most likely to be used?
Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.
- 87%CVE-2019-9515High
Some HTTP/2 implementations are vulnerable to a settings flood, potentially leading to a denial of service.
- 83%CVE-2019-9512High
Some HTTP/2 implementations are vulnerable to ping floods, potentially leading to a denial of service.
- 83%CVE-2019-9514High
Some HTTP/2 implementations are vulnerable to a reset flood, potentially leading to a denial of service.
- 82%CVE-2019-9513High
Some HTTP/2 implementations are vulnerable to resource loops, potentially leading to a denial of service.
- 60%CVE-2019-9511High
Some HTTP/2 implementations are vulnerable to window size manipulation and stream prioritization manipulation, potentially leading to a denial of service.
- 28%CVE-2019-9517High
Some HTTP/2 implementations are vulnerable to unconstrained interal data buffering, potentially leading to a denial of service.
- 25%CVE-2019-9518High
Some HTTP/2 implementations are vulnerable to a flood of empty frames, potentially leading to a denial of service.
- 1.0%CVE-2018-4281Critical
In SwiftNIO before 1.8.0, a buffer overflow was addressed with improved size validation.
- 0.7%CVE-2022-3215High
NIOHTTP1 and projects using it for generating HTTP responses can be subject to a HTTP Response Injection attack.
Running Swiftnio? 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 a settings flood, potentially leading to a denial of service. The attacker sends a stream of SETTINGS frames to the peer. Since the RFC requires that the peer reply with one acknowledgement per SETTINGS frame, an empty SETTINGS frame is almost equivalent in behavior to a ping. Depending on how efficiently this data is queued, this can consume excess CPU, memory, or both.
- 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.
We track 10 published vulnerabilities listed under the name Swiftnio, across 78 versions.
None of Swiftnio's vulnerabilities is on the list of flaws known to be exploited today.
Apple also lists Swiftnio under more specific names, such as Swiftnio Http/2 and Swiftnio SSL. Flaws listed only under those names are counted on their own pages, not here. Open the release you run to see its own list.
Create a Precursor Intelligence account and track Swiftnio. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.