An out-of-bounds read in dns_validate_dns_response in dns.c was discovered in HAProxy through 1.8.14.
An out-of-bounds read in dns_validate_dns_response in dns.c was discovered in HAProxy through 1.8.14. Due to a missing check when validating DNS responses, remote attackers might be able read the 16 bytes corresponding to an AAAA record from the non-initialized part of the buffer, possibly accessing anything that was left on the stack, or even past the end of the 8193-byte buffer, depending on the value of accepted_payload_size.
- Published
- Dec 12, 2018
- Updated
- Jun 16, 2026
- EPSS
- 4.2% · 91th percentile
- CWE
- CWE-125
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
31
Monitor
Low priority for now.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 4.2%
Affected systems
| Vendor | Product | CPE |
|---|---|---|
| haproxy | haproxy | cpe:2.3:a:haproxy:haproxy |
| canonical | ubuntu linux | cpe:2.3:o:canonical:ubuntu_linux |
| redhat | openshift container platform | cpe:2.3:a:redhat:openshift_container_platform |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- canonical ubuntu linux16.04
- canonical ubuntu linux18.04
- canonical ubuntu linux18.10
- haproxy haproxyup to 1.8.14 inclusive
- redhat openshift container platform3.11
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.15-1 | 1.8.15-1 |
| Debian:9 | haproxy | before 1.7.5-2+deb9u1 | 1.7.5-2+deb9u1 |
| Red Hat:openshift:3.11::el7 | atomic-enterprise-service-catalog | before 1:3.11.82-1.git.1673.133961e.el7 | 1:3.11.82-1.git.1673.133961e.el7 |
| Red Hat:openshift:3.11::el7 | atomic-enterprise-service-catalog-svcat | before 1:3.11.82-1.git.1673.133961e.el7 | 1:3.11.82-1.git.1673.133961e.el7 |
| Red Hat:openshift:3.11::el7 | atomic-openshift | before 0:3.11.82-1.git.0.08bc31b.el7 | 0:3.11.82-1.git.0.08bc31b.el7 |
| Red Hat:openshift:3.11::el7 | atomic-openshift-clients | before 0:3.11.82-1.git.0.08bc31b.el7 | 0:3.11.82-1.git.0.08bc31b.el7 |
| Red Hat:openshift:3.11::el7 | atomic-openshift-clients-redistributable | before 0:3.11.82-1.git.0.08bc31b.el7 | 0:3.11.82-1.git.0.08bc31b.el7 |
| Red Hat:openshift:3.11::el7 | atomic-openshift-cluster-autoscaler | before 0:3.11.82-1.git.0.efb6af0.el7 | 0:3.11.82-1.git.0.efb6af0.el7 |
| Red Hat:openshift:3.11::el7 | atomic-openshift-descheduler | before 0:3.11.82-1.git.300.89765c9.el7 | 0:3.11.82-1.git.300.89765c9.el7 |
| Red Hat:openshift:3.11::el7 | atomic-openshift-docker-excluder | before 0:3.11.82-1.git.0.08bc31b.el7 | 0:3.11.82-1.git.0.08bc31b.el7 |
| Red Hat:openshift:3.11::el7 | atomic-openshift-dockerregistry | before 0:3.11.82-1.git.452.0ce6383.el7 | 0:3.11.82-1.git.452.0ce6383.el7 |
| Red Hat:openshift:3.11::el7 | atomic-openshift-excluder | before 0:3.11.82-1.git.0.08bc31b.el7 | 0:3.11.82-1.git.0.08bc31b.el7 |
| Red Hat:openshift:3.11::el7 | atomic-openshift-hyperkube | before 0:3.11.82-1.git.0.08bc31b.el7 | 0:3.11.82-1.git.0.08bc31b.el7 |
| Red Hat:openshift:3.11::el7 | atomic-openshift-hypershift | before 0:3.11.82-1.git.0.08bc31b.el7 | 0:3.11.82-1.git.0.08bc31b.el7 |
| Red Hat:openshift:3.11::el7 | atomic-openshift-master | before 0:3.11.82-1.git.0.08bc31b.el7 | 0:3.11.82-1.git.0.08bc31b.el7 |
| Red Hat:openshift:3.11::el7 | atomic-openshift-metrics-server | before 0:3.11.82-1.git.52.2fdca3f.el7 | 0:3.11.82-1.git.52.2fdca3f.el7 |
| Red Hat:openshift:3.11::el7 | atomic-openshift-node | before 0:3.11.82-1.git.0.08bc31b.el7 | 0:3.11.82-1.git.0.08bc31b.el7 |
| Red Hat:openshift:3.11::el7 | atomic-openshift-node-problem-detector | before 0:3.11.82-1.git.254.a448936.el7 | 0:3.11.82-1.git.254.a448936.el7 |
| Red Hat:openshift:3.11::el7 | atomic-openshift-pod | before 0:3.11.82-1.git.0.08bc31b.el7 | 0:3.11.82-1.git.0.08bc31b.el7 |
| Red Hat:openshift:3.11::el7 | atomic-openshift-sdn-ovs | before 0:3.11.82-1.git.0.08bc31b.el7 | 0:3.11.82-1.git.0.08bc31b.el7 |
| Red Hat:openshift:3.11::el7 | atomic-openshift-service-idler | before 0:3.11.82-1.git.14.e353758.el7 | 0:3.11.82-1.git.14.e353758.el7 |
| Red Hat:openshift:3.11::el7 | atomic-openshift-template-service-broker | before 0:3.11.82-1.git.0.08bc31b.el7 | 0:3.11.82-1.git.0.08bc31b.el7 |
| Red Hat:openshift:3.11::el7 | atomic-openshift-tests | before 0:3.11.82-1.git.0.08bc31b.el7 | 0:3.11.82-1.git.0.08bc31b.el7 |
| Red Hat:openshift:3.11::el7 | atomic-openshift-web-console | before 0:3.11.82-1.git.355.5e8b1d9.el7 | 0:3.11.82-1.git.355.5e8b1d9.el7 |
+23
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 bytes53Plan
- 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 prot51Plan
- 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, a47Plan
- CVE-2016-5360HAproxy 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 memor43Plan
- CVE-2019-19330The HTTP/2 implementation in HAProxy before 2.0.10 mishandles headers, as demonstrated by carriage return (CR, ASCII 0xd), line feed (LF, AS40Plan
- CVE-2023-25725HAProxy before 2.7.3 may allow a bypass of access control because HTTP/1 headers are inadvertently lost in some situations, aka "request smu38Monitor
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.15-1 · Debian:12 | Package registry (OSV) |
| red hat:atomic-enterprise-service-catalog | 1:3.11.82-1.git.1673.133961e.el7 · Red Hat:openshift:3.11::el7 | Package registry (OSV) |
| red hat:atomic-enterprise-service-catalog-svcat | 1:3.11.82-1.git.1673.133961e.el7 · Red Hat:openshift:3.11::el7 | Package registry (OSV) |
| red hat:atomic-openshift | 0:3.11.82-1.git.0.08bc31b.el7 · Red Hat:openshift:3.11::el7 | Package registry (OSV) |
| red hat:atomic-openshift-clients | 0:3.11.82-1.git.0.08bc31b.el7 · Red Hat:openshift:3.11::el7 | Package registry (OSV) |
| red hat:atomic-openshift-clients-redistributable | 0:3.11.82-1.git.0.08bc31b.el7 · Red Hat:openshift:3.11::el7 | Package registry (OSV) |
| red hat:atomic-openshift-cluster-autoscaler | 0:3.11.82-1.git.0.efb6af0.el7 · Red Hat:openshift:3.11::el7 | Package registry (OSV) |
| red hat:atomic-openshift-descheduler | 0:3.11.82-1.git.300.89765c9.el7 · Red Hat:openshift:3.11::el7 | Package registry (OSV) |
| red hat:atomic-openshift-docker-excluder | 0:3.11.82-1.git.0.08bc31b.el7 · Red Hat:openshift:3.11::el7 | Package registry (OSV) |
| red hat:atomic-openshift-dockerregistry | 0:3.11.82-1.git.452.0ce6383.el7 · Red Hat:openshift:3.11::el7 | Package registry (OSV) |
| red hat:atomic-openshift-excluder | 0:3.11.82-1.git.0.08bc31b.el7 · Red Hat:openshift:3.11::el7 | Package registry (OSV) |
| red hat:atomic-openshift-hyperkube | 0:3.11.82-1.git.0.08bc31b.el7 · Red Hat:openshift:3.11::el7 | Package registry (OSV) |
| red hat:atomic-openshift-hypershift | 0:3.11.82-1.git.0.08bc31b.el7 · Red Hat:openshift:3.11::el7 | Package registry (OSV) |
| suse:haproxy | 1.8.15~git0.6b6a350a-3.6.2 · SUSE:Linux Enterprise High Availability Extension 15 | 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).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
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
- high · data can be read
- Integrity
- none
- Availability
- none
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
CWE-125 · Out-of-bounds ReadCVSS vector
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
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)
ATT&CK techniques
—
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for helpChange log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
- git.haproxy.org/?p=haproxy.git%3Ba=commit%3Bh=efbbdf72992cd20458259962346044cafd9331c0
- www.securityfocus.com/bid/106223
- access.redhat.com/errata/RHBA-2019:0326
- access.redhat.com/errata/RHBA-2019:0327
- access.redhat.com/errata/RHSA-2019:1436
- lists.debian.org/debian-lts-announce/2022/05/msg00045.html
- usn.ubuntu.com/3858-1/
Vendor advisories and official records. Exploit/PoC links are deliberately left out.