CVE-2006-20001 | Apache HTTP Server: mod_dav out of bounds read, or write of zero byte

A carefully crafted If: request header can cause a memory read, or write of a single zero byte, in a pool (heap) memory location beyond the header value sent. This could cause the process to crash. This issue affects Apache HTTP Server 2.4.54 and earlier.

Published: 2023-01-17 Last update: 2026-06-16 Assigner: [email protected] Source: [email protected]

Conclusion & alert: CVE-2006-20001 is rated Moderate Risk (63.8/100): CVSS High severity, with medium exploitation likelihood (EPSS 3.55%). Core evidence: EPSS rose +3.08% over the last day, indicating growing attacker interest. Mandatory action: Review affected assets and schedule remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2006-20001

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 0.47% 3.55% +3.08%
2 2026-05-20 0.44% 0.47% +0.03%
3 2026-03-29 0.44%

Full EPSS history (54 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2006-20001

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.5 3.1 HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
3.9 3.6 [email protected]

Weakness enumeration for CVE-2006-20001

OS Trackers for CVE-2006-20001

vendor priority summary link
alpine CVE-2006-20001: 1 source package rows (apache2); 1 state rows across 1 repos (3.17-main); fixed 1, open 0. https://security.alpinelinux.org/vuln/CVE-2006-20001
debian not yet assigned CVE-2006-20001 not yet assigned priority: Debian including 1 source packages (apache2), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5. https://security-tracker.debian.org/tracker/CVE-2006-20001
gentoo low CVE-2006-20001: 1 GLSA(s) (202309-01), 1 atom(s) (www-servers/apache); latest impact low. https://bugs.gentoo.org/buglist.cgi?quicksearch=CVE-2006-20001
redhat medium https://access.redhat.com/security/cve/CVE-2006-20001
suse high CVE-2006-20001 severity important: SUSE including 317 source package names (2.8-13.5:apache2-utils-2.4.51-150400.6.6.1, 4.3.4.9.25.2:apache2-2.4.51-150400.6.6.1, …), 595 product×package rows across 89 product lines (Container bci/php-apache, Container suse/manager/4.3/proxy-httpd, … (89 product lines)): Fixed 364, Known Affected 231. https://www.suse.com/security/cve/CVE-2006-20001/
ubuntu medium CVE-2006-20001 medium priority: Ubuntu including 1 source packages (apache2), 13 status rows across 13 suites (bionic, focal, jammy, kinetic, lunar, mantic, noble, oracular, plucky, questing, trusty, upstream, xenial): released 12, needed 1. https://ubuntu.com/security/CVE-2006-20001

Affected software / configurations for CVE-2006-20001

Vendor Product Version Raw CPE
apache http_server < 2.4.55 cpe:2.3:a:apache:http_server:*:*:*:*:*:*:*:*

References for CVE-2006-20001

cvelogic Threat Intelligence