Skip to content
Noroxi
CVE-2016-7069· NVD / CVE Program· CNA redhat

An issue has been found in dnsdist before 1.2.0 in the way EDNS0 OPT records are handled when parsing responses from a backend.

An issue has been found in dnsdist before 1.2.0 in the way EDNS0 OPT records are handled when parsing responses from a backend. When dnsdist is configured to add EDNS Client Subnet to a query, the response may contain an EDNS0 OPT record that has to be removed before forwarding the response to the initial client. On a 32-bit system, the pointer arithmetic used when parsing the received response to remove that record might trigger an undefined behavior leading to a crash.

HighCVSS 7.5 · v3.0—No exploit Fix available
Published
Sep 11, 2018
Updated
Jun 16, 2026
EPSS
4.6% · 91th percentile
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

31

Monitor

Low priority for now.

CVSS
30 / 40 · 7.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
1 / 30 · 4.6%

CNA vs NVD score

NVD
7.5
CNA · redhat
5.9
1.6 point gap

CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Affected systems

VendorProduct
powerdnsdnsdist

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • powerdns dnsdistup to 1.2.0 inclusive

Versions reported by the vendor

Affected version ranges reported by the assigning authority (redhat). Independent of NVD's CPE analysis and usually ahead of it.

  • Open-Xchange dnsdist

    • 1.2.0affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12dnsdistbefore 1.2.0-11.2.0-1
openSUSE:Tumbleweeddnsdistbefore 1.8.0~rc1-1.11.8.0~rc1-1.1
SUSE:Linux Enterprise Module for Basesystem 15 SP4dnsdistbefore 1.8.0-150400.9.3.11.8.0-150400.9.3.1
SUSE:Linux Enterprise Module for Basesystem 15 SP4dnsdistbefore 1.8.0-150400.9.3.11.8.0-150400.9.3.1
SUSE:Linux Enterprise Module for Basesystem 15 SP4luajitbefore 2.1.0~beta3+git.1624618403.e9577376-150400.4.2.12.1.0~beta3+git.1624618403.e9577376-150400.4.2.1
SUSE:Linux Enterprise Module for Basesystem 15 SP4luajitbefore 2.1.0~beta3+git.1624618403.e9577376-150400.4.2.12.1.0~beta3+git.1624618403.e9577376-150400.4.2.1
SUSE:Linux Enterprise Server 15 SP1-LTSSdnsdistbefore 1.8.0-150100.3.5.11.8.0-150100.3.5.1

Other highest-scoring records for the same primary product.

  • CVE-2026-33598Out-of-bounds read in cache inspection via Lua
    37Monitor
  • CVE-2017-7557dnsdist version 1.1.0 is vulnerable to a flaw in authentication mechanism for REST API potentially allowing CSRF attack.
    35Monitor
  • CVE-2026-33602Off-by-one access when processing crafted UDP responses
    32Monitor
  • CVE-2026-33599Out-of-bounds read in service discovery
    32Monitor
  • CVE-2026-24028Out-of-bounds read when parsing DNS packets via Lua
    32Monitor
  • CVE-2025-30194Denial of service via crafted DoH exchange
    31Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
debian:dnsdist1.2.0-1 · Debian:12Package registry (OSV)
opensuse:dnsdist1.8.0-150400.9.3.1 · openSUSE:Leap 15.4Package registry (OSV)
opensuse:luajit2.1.0~beta3+git.1624618403.e9577376-150400.4.2.1 · openSUSE:Leap 15.4Package registry (OSV)
suse:dnsdist1.8.0-150400.9.3.1 · SUSE:Linux Enterprise Module for Basesystem 15 SP4Package registry (OSV)
suse:luajit2.1.0~beta3+git.1624618403.e9577376-150400.4.2.1 · SUSE:Linux Enterprise Module for Basesystem 15 SP4Package 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.

EPSS, last 120 days

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.

Finders, 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
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

CVSS vector

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

nvd-primary

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 help

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records