LiveActive security incident?Get immediate response
CVE Record

CVE-2016-7074: An issue has been found in PowerDNS before 3.4.11 and 4.0.2, and PowerDNS recursor before 4.0.4, allowing a...

An issue has been found in PowerDNS before 3.4.11 and 4.0.2, and PowerDNS recursor before 4.0.4, allowing an attacker in position of man-in-the-middle to alter the content of an AXFR because of insufficient validation of TSIG signatures. A missing check that the TSIG record is the last one, leading to the possibility of parsing records that are not covered by the TSIG signature.

MediumCVSS 5.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2016-7074 affects older PowerDNS components. A man-in-the-middle attacker could alter DNS zone transfer content because TSIG signature validation did not ensure the signed record was last. Business impact is integrity risk to DNS data, not direct system takeover.

Executive priority

Treat as a targeted DNS integrity issue. Prioritize internet-facing or cross-network DNS transfer environments, but this is not described as wormable or actively exploited in the supplied sources.

Technical view

PowerDNS before 3.4.11 and 4.0.2, and PowerDNS Recursor before 4.0.4, insufficiently validated TSIG-signed AXFR responses. Records after the TSIG could be parsed even though not covered by the signature, allowing tampering by an attacker positioned on the transfer path.

Likely exposure

Exposure is most relevant where affected PowerDNS versions handle AXFR zone transfers protected by TSIG, especially across networks where a man-in-the-middle position is plausible.

Exploitation context

The supplied sources describe a network attacker in man-in-the-middle position. No KEV listing or provided source indicates active exploitation in the wild.

Researcher notes

The core flaw is missing validation that TSIG is the final AXFR record. Scope appears limited to integrity of transferred zone content under man-in-the-middle conditions. Evidence does not show confidentiality or availability impact.

Mitigation direction

  • Upgrade PowerDNS Authoritative to 3.4.11, 4.0.2, or a later supported release.
  • Upgrade PowerDNS Recursor to 4.0.4 or a later supported release.
  • Apply relevant Debian or vendor package updates where PowerDNS is OS-managed.
  • Prioritize servers performing AXFR transfers over less trusted network paths.
  • Check PowerDNS and distribution advisories for environment-specific guidance if upgrade is delayed.

Validation and detection

  • Inventory PowerDNS authoritative and recursor installations and record installed versions.
  • Compare versions with the fixed releases named in the advisories.
  • Identify DNS zones using AXFR with TSIG and their transfer paths.
  • Confirm vendor package changelogs include the CVE fix or equivalent backport.
  • Review secondary DNS data for unexpected records after remediation.
Prepared
Confidence
high
Sources
5

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-20: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2016-7074 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
5.3 (3.0)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
4Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
5.3CVSS 3.0MediumCVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N3.91.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.0 score

5.3Medium
CVSS 3.0 vector shape for CVE-2016-7074Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Open-Xchangepdns3.4.11, 4.0.2, 4.0.4Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-20 · source CWE mapping

Improper Input Validation

Improper Input Validation represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.