CVE-2020-25691 json
A flaw was found in darkhttpd.
published 2022-04-01 4 y ago modified 2026-06-17 4 mo ago also EUVD-2020-18352
- cvss
- 7.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.3%
- EPSS 1.3% chance of exploitation in 30 days, percentile 70%
- public exploits
- 0
- none known
Summary
A flaw was found in darkhttpd. Invalid error handling allows remote attackers to cause denial-of-service by accessing a file with a large modification date. The highest threat from this vulnerability is to system availability.
Patch / fix
- darkhttpd Alpine 3.24, Alpine 3.23, Alpine 3.22 +6 more 1.14-r0
alpine advisories ALPINE-CVE-2020-25691
Alpine secdb © Alpine Linux, from https://secdb.alpinelinux.org via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2020-25691 updated cvss 7.5
darkhttpd: sending an HTTP GET to a file with large modification date can cause a DoS
-
Red Hat All currently supported Red Hat productsnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
1.32% chance of exploitation in the next 30 days, higher than 70% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:N/I:N/A:P |
Affected products
- n/a darkhttpd
Classification
- Weakness
-
- CWE-755 Improper Handling of Exceptional Conditions
References
-
bugzilla.redhat.com
/show_bug.cgi?id=1893725
issue-tracking, third-party-advisory
Sources
- CVE List CVE-2020-25691
- NVD CVE-2020-25691
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.