CVE-2016-5360: 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 memory access and crash) or possibly have unspecified other...
High CVSS 7.5
- CVE id
- CVE-2016-5360
- Published
- Last modified
Affected packages
| Package | Affected versions | Fixed in |
|---|---|---|
| HAProxy Runtimes and servers |
1.6.0 1.6.1 1.6.2 1.6.3 1.6.4 1.6.5 |
not fixed yet |
How to fix it
No fix yet. No fixed HAProxy release is listed yet.
haproxy -v
- Check the advisory and its references below for a workaround or a configuration change that turns off the affected feature.
- Limit exposure: don't pass untrusted input to the affected code path, and keep it off public endpoints if you can.
- 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
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 memory access and crash) or possibly have unspecified other impact via unknown vectors.
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.