CVE-2019-19331
published 2019-12-16CVE-2019-19331: knot-resolver before version 4.3.0 is vulnerable to denial of service through high CPU utilization. DNS replies with very many resource records might be…
PriorityP335high7.5CVSS 3.1
AVNACLPRNUINSUCNINAH
EPSS
2.17%
80.0th percentile
knot-resolver before version 4.3.0 is vulnerable to denial of service through high CPU utilization. DNS replies with very many resource records might be processed very inefficiently, in extreme cases taking even several CPU seconds for each such uncached message. For example, a few thousand A records can be squashed into one DNS message (limit is 64kB).
Affected
9 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| cz.nic | knot-resolver | — | — |
| cz.nic | knot-resolver | >= 0 < 5.0.1-1 | 5.0.1-1 |
| cz.nic | knot-resolver | >= 0 < 5.0.1-1 | 5.0.1-1 |
| cz.nic | knot-resolver | >= 0 < 5.0.1-1 | 5.0.1-1 |
| cz.nic | knot-resolver | >= 0 < 5.0.1-1 | 5.0.1-1 |
| cz.nic | knot-resolver | >= 0 < 3.2.1-3ubuntu2.2 | 3.2.1-3ubuntu2.2 |
| debian | debian_linux | — | — |
| debian | knot-resolver | < knot-resolver 5.0.1-1 (bookworm) | knot-resolver 5.0.1-1 (bookworm) |
| nic | knot_resolver | < 4.3.0 | 4.3.0 |
CVSS provenance
nvdv3.17.5HIGHCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
nvdv3.07.5HIGHCVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
nvdv2.05.0MEDIUMAV:N/AC:L/Au:N/C:N/I:N/A:P
osv7.5HIGH
vendor_debian7.5HIGH
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
OSV
knot-resolver vulnerabilities
osv·2024-10-01·CVSS 7.5
CVE-2019-10190 [HIGH] knot-resolver vulnerabilities
knot-resolver vulnerabilities
Vladimír Čunát discovered that Knot Resolver incorrectly handled input
during DNSSEC validation. A remote attacker could possibly use this issue
to bypass certain validations. (CVE-2019-10190)
Vladimír Čunát discovered that Knot Resolver incorrectly handled input
during DNSSEC validation. A remote attacker could possibly use this issue
to downgrade DNSSEC-secure domains to a DNSSEC-insecure state, resulting
in a domain hijacking attack. (CVE-2019-10191)
Vladimír Čunát discovered that Knot Resolver incorrectly handled certain
DNS replies with many resource records. An attacker could possibly use
this issue to consume system resources, resulting in a denial of service.
(CVE-2019-19331)
Lior Shafir, Yehuda Afek, and Anat Bremler-Barr discovered that Knot
Reso
GHSA
GHSA-9f7v-8m4p-pv76: knot-resolver before version 4
ghsa_unreviewed·2022-05-24
CVE-2019-19331 [HIGH] CWE-404 GHSA-9f7v-8m4p-pv76: knot-resolver before version 4
knot-resolver before version 4.3.0 is vulnerable to denial of service through high CPU utilization. DNS replies with very many resource records might be processed very inefficiently, in extreme cases taking even several CPU seconds for each such uncached message. For example, a few thousand A records can be squashed into one DNS message (limit is 64kB).
OSV
CVE-2019-19331: knot-resolver before version 4
osv·2019-12-16·CVSS 7.5
CVE-2019-19331 [HIGH] CVE-2019-19331: knot-resolver before version 4
knot-resolver before version 4.3.0 is vulnerable to denial of service through high CPU utilization. DNS replies with very many resource records might be processed very inefficiently, in extreme cases taking even several CPU seconds for each such uncached message. For example, a few thousand A records can be squashed into one DNS message (limit is 64kB).
Debian
CVE-2019-19331: knot-resolver - knot-resolver before version 4.3.0 is vulnerable to denial of service through hi...
vendor_debian·2019·CVSS 7.5
CVE-2019-19331 [HIGH] CVE-2019-19331: knot-resolver - knot-resolver before version 4.3.0 is vulnerable to denial of service through hi...
knot-resolver before version 4.3.0 is vulnerable to denial of service through high CPU utilization. DNS replies with very many resource records might be processed very inefficiently, in extreme cases taking even several CPU seconds for each such uncached message. For example, a few thousand A records can be squashed into one DNS message (limit is 64kB).
Scope: local
bookworm: resolved (fixed in 5.0.1-1)
bullseye: resolved (fixed in 5.0.1-1)
forky: resolved (fixed in 5.0.1-1)
sid: resolved (fixed in 5.0.1-1)
trixie: resolved (fixed in 5.0.1-1)
No detection rules found.
No public exploits indexed.
Bugzilla
CVE-2019-19331 knot-resolver: DNS packets taking few seconds to process with full CPU utilization leads to DoS [epel-7]
bugzilla·2019-12-06·CVSS 7.5
CVE-2019-19331 [HIGH] CVE-2019-19331 knot-resolver: DNS packets taking few seconds to process with full CPU utilization leads to DoS [epel-7]
CVE-2019-19331 knot-resolver: DNS packets taking few seconds to process with full CPU utilization leads to DoS [epel-7]
This is an automatically created tracking bug! It was created to ensure
that one or more security vulnerabilities are fixed in affected versions
of epel-7.
For comments that are specific to the vulnerability please use bugs filed
against the "Security Response" product referenced in the "Blocks" field.
For more information see:
http://fedoraproject.org/wiki/Security/TrackingBugs
When submitting as an update, use the fedpkg template provided in the next
comment(s). This will include the bug IDs of this tracking bug as well as
the relevant top-level CVE bugs.
Please also mention the CVE IDs being fixed in the RPM changelog and the
fedpkg commit message.
Discussion:
U
Bugzilla
CVE-2019-19331 knot-resolver: DNS packets taking few seconds to process with full CPU utilization leads to DoS [fedora-all]
bugzilla·2019-12-06·CVSS 7.5
CVE-2019-19331 [HIGH] CVE-2019-19331 knot-resolver: DNS packets taking few seconds to process with full CPU utilization leads to DoS [fedora-all]
CVE-2019-19331 knot-resolver: DNS packets taking few seconds to process with full CPU utilization leads to DoS [fedora-all]
This is an automatically created tracking bug! It was created to ensure
that one or more security vulnerabilities are fixed in affected versions
of fedora-all.
For comments that are specific to the vulnerability please use bugs filed
against the "Security Response" product referenced in the "Blocks" field.
For more information see:
http://fedoraproject.org/wiki/Security/TrackingBugs
When submitting as an update, use the fedpkg template provided in the next
comment(s). This will include the bug IDs of this tracking bug as well as
the relevant top-level CVE bugs.
Please also mention the CVE IDs being fixed in the RPM changelog and the
fedpkg commit message.
NOTE:
Bugzilla
CVE-2019-19331 knot-resolver: DNS packets taking few seconds to process with full CPU utilization leads to DoS
bugzilla·2019-12-04·CVSS 7.5
CVE-2019-19331 [HIGH] CVE-2019-19331 knot-resolver: DNS packets taking few seconds to process with full CPU utilization leads to DoS
CVE-2019-19331 knot-resolver: DNS packets taking few seconds to process with full CPU utilization leads to DoS
DNS replies with very many resource records might be processed very inefficiently, in extreme cases taking even several CPU seconds for each such uncached message. For example, a few thousand A records can be squashed into one DNS message (limit is 64kB).
To execute an attack it is enough to:
+ own a rogue authoritative server or utilize an existing name with a huge RRset, and
+ trigger DNS query for that name from the resolver to be attacked
References:
https://gitlab.labs.nic.cz/knot/knot-resolver/tags/v4.3.0
Discussion:
From upstream:
Most of the issue can be mitigated by updating libknot dependency to >= 2.9.1. Otherwise a complete fix will be released in Knot Resolver
https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2019-19331https://lists.debian.org/debian-lts-announce/2024/04/msg00017.htmlhttps://www.knot-resolver.cz/2019-12-04-knot-resolver-4.3.0.htmlhttps://bugzilla.redhat.com/show_bug.cgi?id=CVE-2019-19331https://lists.debian.org/debian-lts-announce/2024/04/msg00017.htmlhttps://www.knot-resolver.cz/2019-12-04-knot-resolver-4.3.0.html
2019-12-16
Published