CVE-2018-10184: An issue was discovered in HAProxy before 1.8.8.
Noroxi assessment
Priority: Monitor (action score 32/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 8.1% (FIRST EPSS); higher than 94.9% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: haproxy (Debian:12) 1.8.8-1; haproxy (Red Hat:openshift:3.9::el7) 0:1.8.8-1.el7; haproxy-debuginfo (Red Hat:openshift:3.9::el7) 0:1.8.8-1.el7.
Low priority for now. Upgrade to haproxy (Debian:12) 1.8.8-1; haproxy (Red Hat:openshift:3.9::el7) 0:1.8.8-1.el7; haproxy-debuginfo (Red Hat:openshift:3.9::el7) 0:1.8.8-1.el7 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
An issue was discovered in HAProxy before 1.8.8. The incoming H2 frame length was checked against the max_frame_size setting instead of being checked against the bufsize. The max_frame_size only applies to outgoing traffic and not to incoming, so if a large enough frame size is advertised in the SETTINGS frame, a wrapped frame will be defragmented into a temporary allocated buffer where the second fragment may overflow the heap by up to 16 kB. It is very unlikely that this can be exploited for code execution given that buffers are very short lived and their addresses not realistically predictable in production, but the likelihood of an immediate crash is absolutely certain.
- Published
- May 9, 2018
- Updated
- Jun 16, 2026
- EPSS
- 8.1% · 94th percentile
- CWE
- CWE-119
Report tools
Action score
32
Low priority for now.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 2 / 30 · 8.1%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| haproxy | haproxy | cpe:2.3:a:haproxy:haproxy |
| redhat | enterprise linux | cpe:2.3:o:redhat:enterprise_linux |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- haproxy haproxybefore 1.8.8
- redhat enterprise linux7.0
- redhat enterprise linux7.3
- redhat enterprise linux7.4
- redhat enterprise linux7.5
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | haproxy | before 1.8.8-1 | 1.8.8-1 |
| Red Hat:openshift:3.9::el7 | haproxy | before 0:1.8.8-1.el7 | 0:1.8.8-1.el7 |
| Red Hat:openshift:3.9::el7 | haproxy-debuginfo | before 0:1.8.8-1.el7 | 0:1.8.8-1.el7 |
| Red Hat:openshift:3.9::el7 | haproxy18 | before 0:1.8.8-1.el7 | 0:1.8.8-1.el7 |
| Red Hat:rhel_software_collections:3::el7 | rh-haproxy18-haproxy | before 0:1.8.4-2.el7 | 0:1.8.4-2.el7 |
| Red Hat:rhel_software_collections:3::el7 | rh-haproxy18-haproxy-debuginfo | before 0:1.8.4-2.el7 | 0:1.8.4-2.el7 |
| Red Hat:rhel_software_collections:3::el7 | rh-haproxy18-haproxy-syspaths | before 0:1.8.4-2.el7 | 0:1.8.4-2.el7 |
Same product
haproxy: all recordsOther highest-scoring records for the same primary product.
- CVE-2020-11100In hpack_dht_insert in hpack-tbl.c in the HPACK decoder in HAProxy 1.8 through 2.x before 2.1.4, a remote attacker can write arbitrary…53Plan
- CVE-2019-14241HAProxy through 2.0.2 allows attackers to cause a denial of service (ha_panic) via vectors related to htx_manage_client_side_cookies in…51Plan
- CVE-2021-40346An integer overflow exists in HAProxy 2.0 through 2.5 in htx_add_header that can be exploited to perform an HTTP request smuggling attack…48Plan
Published before and after this one in the same product
- ← EarlierCVE-2016-5360Jun 30, 2016 · HAproxy 1.6.x before 1.6.6, when a deny comes from a reqdeny rule, allows remote attackers to cause a denial of service (uninitialized…43Plan
- ← EarlierCVE-2016-2102Aug 22, 2017 · HAProxy statistics in openstack-tripleo-image-elements are non-authenticated over the network.22Monitor
- Later →CVE-2018-11469May 25, 2018 · Incorrect caching of responses to requests including an Authorization header in HAProxy 1.8.0 through 1.8.9 (if cache enabled) allows…24Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| debian:haproxy | 1.8.8-1 · Debian:12 | Package registry (OSV) |
| red hat:haproxy | 0:1.8.8-1.el7 · Red Hat:openshift:3.9::el7 | Package registry (OSV) |
| red hat:haproxy-debuginfo | 0:1.8.8-1.el7 · Red Hat:openshift:3.9::el7 | Package registry (OSV) |
| red hat:haproxy18 | 0:1.8.8-1.el7 · Red Hat:openshift:3.9::el7 | Package registry (OSV) |
| red hat:rh-haproxy18-haproxy | 0:1.8.4-2.el7 · Red Hat:rhel_software_collections:3::el7 | Package registry (OSV) |
| red hat:rh-haproxy18-haproxy-debuginfo | 0:1.8.4-2.el7 · Red Hat:rhel_software_collections:3::el7 | Package registry (OSV) |
| red hat:rh-haproxy18-haproxy-syspaths | 0:1.8.4-2.el7 · Red Hat:rhel_software_collections:3::el7 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Not on record for this CVE: patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-119 · Improper Restriction of Operations within the Bounds of a Memory BufferCVSS vector
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Buffer Overflow via Environment VariablesCAPEC-10likelihood: High · High
- Overflow BuffersCAPEC-100likelihood: High · Very High
- Buffer ManipulationCAPEC-123likelihood: High · Very High
- Client-side Injection-induced Buffer OverflowCAPEC-14likelihood: Medium · High
- Filter Failure through Buffer OverflowCAPEC-24likelihood: High · High
- MIME ConversionCAPEC-42likelihood: High · High
- Overflow Binary Resource FileCAPEC-44likelihood: High · Very High
- Buffer Overflow via Symbolic LinksCAPEC-45likelihood: High · High
ATT&CK techniques
—
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (2 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.