CVE-2018-5737
published 2019-01-16CVE-2018-5737: A problem with the implementation of the new serve-stale feature in BIND 9.12 can lead to an assertion failure in rbtdb.c, even when stale-answer-enable is…
PriorityP343high7.5CVSS 3.0
AVNACLPRNUINSUCNINAH
EPSS
10.44%
95.4th percentile
A problem with the implementation of the new serve-stale feature in BIND 9.12 can lead to an assertion failure in rbtdb.c, even when stale-answer-enable is off. Additionally, problematic interaction between the serve-stale feature and NSEC aggressive negative caching can in some cases cause undesirable behavior from named, such as a recursion loop or excessive logging. Deliberate exploitation of this condition could cause operational problems depending on the particular manifestation -- either degradation or denial of service. Affects BIND 9.12.0 and 9.12.1.
Affected
21 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | bind9 | — | — |
| isc | bind | — | — |
| isc | bind | — | — |
| isc | bind | >= 0 < 9.12.1_p2-r0 | 9.12.1_p2-r0 |
| isc | bind | >= 0 < 9.12.1_p2-r0 | 9.12.1_p2-r0 |
| isc | bind | >= 0 < 9.12.1_p2-r0 | 9.12.1_p2-r0 |
| isc | bind | >= 0 < 9.12.1_p2-r0 | 9.12.1_p2-r0 |
| isc | bind | >= 0 < 9.12.1_p2-r0 | 9.12.1_p2-r0 |
| isc | bind | >= 0 < 9.12.1_p2-r0 | 9.12.1_p2-r0 |
| isc | bind | >= 0 < 9.12.1_p2-r0 | 9.12.1_p2-r0 |
| isc | bind | >= 0 < 9.12.1_p2-r0 | 9.12.1_p2-r0 |
| isc | bind | >= 0 < 9.12.1_p2-r0 | 9.12.1_p2-r0 |
| isc | bind | >= 0 < 9.12.1_p2-r0 | 9.12.1_p2-r0 |
| isc | bind | >= 0 < 9.12.1_p2-r0 | 9.12.1_p2-r0 |
| isc | bind | >= 0 < 9.12.1_p2-r0 | 9.12.1_p2-r0 |
| isc | bind | >= 0 < 9.12.1_p2-r0 | 9.12.1_p2-r0 |
| isc | bind | >= 0 < 9.12.1_p2-r0 | 9.12.1_p2-r0 |
| isc | bind | >= 0 < 9.12.1_p2-r0 | 9.12.1_p2-r0 |
| isc | bind | >= 0 < 9.12.1_p2-r0 | 9.12.1_p2-r0 |
| isc | bind_9 | — | — |
| msrc | cm1_nodejs_14.17.2-1_on_cbl_mariner_1.0 | — | — |
CVSS provenance
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_msrc7.5HIGH
vendor_redhat7.5HIGH
vendor_debian5.9LOW
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.
Microsoft
In Node.js including 6.x before 6.17.0 8.x before 8.15.1 10.x before 10.15.2 and 11.x before 11.10.1 an attacker can cause a Denial of Service (DoS) by establishing an HTTP or HTTPS connection in keep
vendor_msrc·2019-03-12·CVSS 7.5
CVE-2019-5737 [HIGH] CWE-770 In Node.js including 6.x before 6.17.0 8.x before 8.15.1 10.x before 10.15.2 and 11.x before 11.10.1 an attacker can cause a Denial of Service (DoS) by establishing an HTTP or HTTPS connection in keep
In Node.js including 6.x before 6.17.0 8.x before 8.15.1 10.x before 10.15.2 and 11.x before 11.10.1 an attacker can cause a Denial of Service (DoS) by establishing an HTTP or HTTPS connection in keep-alive mode and by sending headers very slowly. This keeps the connection and associated resources alive for a long period of time. Potential attacks are mitigated by the use of a load balancer or other proxy layer. This vulnerability is an extension of CVE-2018-12121 addressed in November and impacts all active Node.js release lines including 6.x before 6.17.0 8.x before 8.15.1 10.x before 10.15.2 and 11.x before 11.10.1.
FAQ: Is Azure Linux the only Microsoft product that includes this open-source library and is therefore potentially affected by this vulnerability?
One of the main benefits
Red Hat
nodejs: Insufficient Slowloris fix causing DoS via server.headersTimeout bypass
vendor_redhat·2019-02-28·CVSS 7.5
CVE-2019-5737 [HIGH] CWE-400 nodejs: Insufficient Slowloris fix causing DoS via server.headersTimeout bypass
nodejs: Insufficient Slowloris fix causing DoS via server.headersTimeout bypass
In Node.js including 6.x before 6.17.0, 8.x before 8.15.1, 10.x before 10.15.2, and 11.x before 11.10.1, an attacker can cause a Denial of Service (DoS) by establishing an HTTP or HTTPS connection in keep-alive mode and by sending headers very slowly. This keeps the connection and associated resources alive for a long period of time. Potential attacks are mitigated by the use of a load balancer or other proxy layer. This vulnerability is an extension of CVE-2018-12121, addressed in November and impacts all active Node.js release lines including 6.x before 6.17.0, 8.x before 8.15.1, 10.x before 10.15.2, and 11.x before 11.10.1.
It was found that the original fix for Slowloris, CVE-2018-12122, was insufficient.
Red Hat
bind: Interaction between NSEC aggresive negative caching and the serve-stale feature can cause a denial of service
vendor_redhat·2018-05-18·CVSS 5.9
CVE-2018-5737 [MEDIUM] CWE-400 bind: Interaction between NSEC aggresive negative caching and the serve-stale feature can cause a denial of service
bind: Interaction between NSEC aggresive negative caching and the serve-stale feature can cause a denial of service
A problem with the implementation of the new serve-stale feature in BIND 9.12 can lead to an assertion failure in rbtdb.c, even when stale-answer-enable is off. Additionally, problematic interaction between the serve-stale feature and NSEC aggressive negative caching can in some cases cause undesirable behavior from named, such as a recursion loop or excessive logging. Deliberate exploitation of this condition could cause operational problems depending on the particular manifestation -- either degradation or denial of service. Affects BIND 9.12.0 and 9.12.1.
A flaw was found in the "serve-stale" feature as implemented in bind. Problematic interaction between serve-stale fea
Debian
CVE-2018-5737: bind9 - A problem with the implementation of the new serve-stale feature in BIND 9.12 ca...
vendor_debian·2018·CVSS 5.9
CVE-2018-5737 [MEDIUM] CVE-2018-5737: bind9 - A problem with the implementation of the new serve-stale feature in BIND 9.12 ca...
A problem with the implementation of the new serve-stale feature in BIND 9.12 can lead to an assertion failure in rbtdb.c, even when stale-answer-enable is off. Additionally, problematic interaction between the serve-stale feature and NSEC aggressive negative caching can in some cases cause undesirable behavior from named, such as a recursion loop or excessive logging. Deliberate exploitation of this condition could cause operational problems depending on the particular manifestation -- either degradation or denial of service. Affects BIND 9.12.0 and 9.12.1.
Scope: local
bookworm: resolved
bullseye: resolved
forky: resolved
sid: resolved
trixie: resolved
GHSA
GHSA-9cxr-pmg7-9w5v: A problem with the implementation of the new serve-stale feature in BIND 9
ghsa_unreviewed·2022-05-13
CVE-2018-5737 [HIGH] CWE-617 GHSA-9cxr-pmg7-9w5v: A problem with the implementation of the new serve-stale feature in BIND 9
A problem with the implementation of the new serve-stale feature in BIND 9.12 can lead to an assertion failure in rbtdb.c, even when stale-answer-enable is off. Additionally, problematic interaction between the serve-stale feature and NSEC aggressive negative caching can in some cases cause undesirable behavior from named, such as a recursion loop or excessive logging. Deliberate exploitation of this condition could cause operational problems depending on the particular manifestation -- either degradation or denial of service. Affects BIND 9.12.0 and 9.12.1.
OSV
CVE-2018-5737: A problem with the implementation of the new serve-stale feature in BIND 9
osv·2019-01-16·CVSS 7.5
CVE-2018-5737 [HIGH] CVE-2018-5737: A problem with the implementation of the new serve-stale feature in BIND 9
A problem with the implementation of the new serve-stale feature in BIND 9.12 can lead to an assertion failure in rbtdb.c, even when stale-answer-enable is off. Additionally, problematic interaction between the serve-stale feature and NSEC aggressive negative caching can in some cases cause undesirable behavior from named, such as a recursion loop or excessive logging. Deliberate exploitation of this condition could cause operational problems depending on the particular manifestation -- either degradation or denial of service. Affects BIND 9.12.0 and 9.12.1.
No detection rules found.
No public exploits indexed.
http://www.securityfocus.com/bid/104236http://www.securitytracker.com/id/1040942https://kb.isc.org/docs/aa-01606https://security.netapp.com/advisory/ntap-20180926-0004/http://www.securityfocus.com/bid/104236http://www.securitytracker.com/id/1040942https://kb.isc.org/docs/aa-01606https://security.netapp.com/advisory/ntap-20180926-0004/
2019-01-16
Published