CVE-2018-20615

An out-of-bounds read issue was discovered in the HTTP/2 protocol decoder in HAProxy 1.8.x and 1.9.x through 1.9.0 which can result in a crash. The processing of the PRIORITY flag in a HEADERS frame requires 5 extra bytes, and while these bytes are skipped, the total frame length was not re-checked to make sure they were present in the frame.

Published: 2019-03-21 Last update: 2026-06-16 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2018-20615 is rated High Risk (65.9/100): CVSS High severity, with high exploitation likelihood (EPSS 4.46%, 90th percentile). EPSS ranks this CVE among the most likely to be exploited in the near term. EPSS rose +4.32% over the last day, indicating growing attacker interest. High exploitation likelihood—assess exposure and prioritize 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-2018-20615

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.14% 4.46% +4.32%
2 2026-05-29 0.17% 0.14% -0.02%
3 2026-05-26 — 0.17% —

Full EPSS history (26 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2018-20615

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.5 3.0 HIGH
CVSS:3.0/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]
5.0 2.0 MEDIUM
AV:N/AC:L/Au:N/C:N/I:N/A:P Click to expand
Access vector (AV:N)
Can be exploited remotely over network reachability.
Access complexity (AC:L)
Exploitation conditions are straightforward and predictable.
Authentication (AU:N)
No authentication is required.
Confidentiality impact (C:N)
No confidentiality impact.
Integrity impact (I:N)
No integrity impact.
Availability impact (A:P)
Partial availability impact.
 10.0 2.9 [email protected]

Weakness enumeration for CVE-2018-20615

OS Trackers for CVE-2018-20615

vendor priority summary link
debian not yet assigned CVE-2018-20615 not yet assigned priority: Debian including 1 source packages (haproxy), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5. https://security-tracker.debian.org/tracker/CVE-2018-20615
redhat high — https://access.redhat.com/security/cve/CVE-2018-20615
suse high CVE-2018-20615 severity important: SUSE including 9 source package names (haproxy, haproxy-1.8.17~git0.e89d25b2-3.9.1, …), 20 product×package rows across 20 product lines (HPE Helion OpenStack 8, SUSE Linux Enterprise High Availability Extension 12, … (20 product lines)): Known Not Affected 12, Fixed 8. https://www.suse.com/security/cve/CVE-2018-20615/
ubuntu medium CVE-2018-20615 medium priority: Ubuntu including 1 source packages (haproxy), 5 status rows across 5 suites (bionic, cosmic, trusty, upstream, xenial): released 3, DNE 1, not-affected 1. https://ubuntu.com/security/CVE-2018-20615

Affected software / configurations for CVE-2018-20615

Vendor Product Version Raw CPE
haproxy haproxy >= 1.8.0, <= 1.8.19 cpe:2.3:a:haproxy:haproxy:*:*:*:*:*:*:*:*
haproxy haproxy 1.9.0 cpe:2.3:a:haproxy:haproxy:1.9.0:-:*:*:*:*:*:*
haproxy haproxy 1.9.0 cpe:2.3:a:haproxy:haproxy:1.9.0:dev0:*:*:*:*:*:*
haproxy haproxy 1.9.0 cpe:2.3:a:haproxy:haproxy:1.9.0:dev1:*:*:*:*:*:*
haproxy haproxy 1.9.0 cpe:2.3:a:haproxy:haproxy:1.9.0:dev10:*:*:*:*:*:*
haproxy haproxy 1.9.0 cpe:2.3:a:haproxy:haproxy:1.9.0:dev11:*:*:*:*:*:*
haproxy haproxy 1.9.0 cpe:2.3:a:haproxy:haproxy:1.9.0:dev2:*:*:*:*:*:*
haproxy haproxy 1.9.0 cpe:2.3:a:haproxy:haproxy:1.9.0:dev3:*:*:*:*:*:*
haproxy haproxy 1.9.0 cpe:2.3:a:haproxy:haproxy:1.9.0:dev4:*:*:*:*:*:*
haproxy haproxy 1.9.0 cpe:2.3:a:haproxy:haproxy:1.9.0:dev5:*:*:*:*:*:*
haproxy haproxy 1.9.0 cpe:2.3:a:haproxy:haproxy:1.9.0:dev6:*:*:*:*:*:*
haproxy haproxy 1.9.0 cpe:2.3:a:haproxy:haproxy:1.9.0:dev7:*:*:*:*:*:*
haproxy haproxy 1.9.0 cpe:2.3:a:haproxy:haproxy:1.9.0:dev8:*:*:*:*:*:*
haproxy haproxy 1.9.0 cpe:2.3:a:haproxy:haproxy:1.9.0:dev9:*:*:*:*:*:*
opensuse leap 15.0 cpe:2.3:o:opensuse:leap:15.0:*:*:*:*:*:*:*
canonical ubuntu_linux 16.04 cpe:2.3:o:canonical:ubuntu_linux:16.04:*:*:*:lts:*:*:*
canonical ubuntu_linux 18.04 cpe:2.3:o:canonical:ubuntu_linux:18.04:*:*:*:lts:*:*:*
canonical ubuntu_linux 18.10 cpe:2.3:o:canonical:ubuntu_linux:18.10:*:*:*:*:*:*:*
redhat openshift_container_platform 3.11 cpe:2.3:a:redhat:openshift_container_platform:3.11:*:*:*:*:*:*:*
redhat enterprise_linux 7.0 cpe:2.3:o:redhat:enterprise_linux:7.0:*:*:*:*:*:*:*
redhat enterprise_linux 7.4 cpe:2.3:o:redhat:enterprise_linux:7.4:*:*:*:*:*:*:*
redhat enterprise_linux 7.5 cpe:2.3:o:redhat:enterprise_linux:7.5:*:*:*:*:*:*:*
redhat enterprise_linux 7.6 cpe:2.3:o:redhat:enterprise_linux:7.6:*:*:*:*:*:*:*

References for CVE-2018-20615

cvelogic Threat Intelligence