CVE-2018-10184: An issue was discovered in HAProxy before 1.8.8.
High CVSS 7.5
- CVE id
- CVE-2018-10184
- Published
- Last modified
Affected packages
| Package | Affected versions | Fixed in |
|---|---|---|
| HAProxy Runtimes and servers |
< 1.8.8 | 1.8.8 |
How to fix it
Upgrade HAProxy to 1.8.8 or later.
haproxy -v
- Install the patched HAProxy release of your branch (the haproxy image tag or your packages) and reload it.
A free AIssue account reads the runtime versions your repositories pin (version files, Dockerfiles, build files) and tells you when one is affected.
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
Am I affected?
Upload or paste your lockfile. We check every package version in it against OSV.dev, this advisory included, and email you the vulnerable ones with the version that fixes them. Free, and no account needed.
About this data
Source: National Vulnerability Database (NVD) (public domain). Severity comes from the advisory's own rating when it has one, else from its CVSS score.