CVE-2018-10184

Source
https://nvd.nist.gov/vuln/detail/CVE-2018-10184
Import Source
https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2018-10184.json
JSON Data
https://api.osv.dev/v1/vulns/CVE-2018-10184
Related
Published
2018-05-09T07:29:00Z
Modified
2024-11-21T03:40:58Z
Severity
  • 7.5 (High) CVSS_V3 - CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H CVSS Calculator
Summary
[none]
Details

An issue was discovered in HAProxy before 1.8.8. The incoming H2 frame length was checked against the maxframesize setting instead of being checked against the bufsize. The maxframesize 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.

References

Affected packages

Debian:11 / haproxy

Package

Name
haproxy
Purl
pkg:deb/debian/haproxy?arch=source

Affected ranges

Type
ECOSYSTEM
Events
Introduced
0Unknown introduced version / All previous versions are affected
Fixed
1.8.8-1

Ecosystem specific

{
    "urgency": "not yet assigned"
}

Debian:12 / haproxy

Package

Name
haproxy
Purl
pkg:deb/debian/haproxy?arch=source

Affected ranges

Type
ECOSYSTEM
Events
Introduced
0Unknown introduced version / All previous versions are affected
Fixed
1.8.8-1

Ecosystem specific

{
    "urgency": "not yet assigned"
}

Debian:13 / haproxy

Package

Name
haproxy
Purl
pkg:deb/debian/haproxy?arch=source

Affected ranges

Type
ECOSYSTEM
Events
Introduced
0Unknown introduced version / All previous versions are affected
Fixed
1.8.8-1

Ecosystem specific

{
    "urgency": "not yet assigned"
}