LiveActive security incident?Get immediate response
CVE Record

CVE-2014-7210: pdns specific as packaged in Debian in version before 3.3.1-1 creates a too privileged MySQL user.

pdns specific as packaged in Debian in version before 3.3.1-1 creates a too privileged MySQL user. It was discovered that the maintainer scripts of pdns-backend-mysql grant too wide database permissions for the pdns user. Other backends are not affected.

CriticalCVSS 9.8Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

Debian’s PowerDNS MySQL backend packaging created a database user with overly broad MySQL privileges. An attacker who can act through that account could affect confidentiality, integrity, or availability of the PowerDNS database. The issue is specific to Debian’s pdns-backend-mysql packaging before version 3.3.1-1; other backends are stated as unaffected.

Executive priority

Prioritize remediation where Debian PowerDNS uses MySQL for production DNS. DNS database compromise can disrupt service or alter records. The vulnerability is old and no active exploitation is cited, but the impact rating justifies prompt validation and cleanup.

Technical view

CVE-2014-7210 is a CWE-276 permissions flaw in Debian maintainer scripts for pdns-backend-mysql. The scripts granted the pdns MySQL user wider database permissions than intended. The supplied CVSS 3.1 score is 9.8, but the source bundle does not provide exploit mechanics or proof of active exploitation.

Likely exposure

Exposure is likely limited to Debian hosts using the pdns-backend-mysql package before 3.3.1-1. Non-MySQL PowerDNS backends are stated as unaffected. Exact vulnerable Debian releases and upgrade package names should be confirmed against Debian guidance.

Exploitation context

No CISA KEV listing or cited source in the bundle indicates active exploitation. The risk comes from excessive database privileges assigned by packaging scripts, which could magnify impact if the pdns database account is reached or abused.

Researcher notes

The affected metadata in the bundle is sparse and includes an unusual version value of "0" with defaultStatus "unaffected." Treat scanner matches carefully and validate against Debian package history, pdns-backend-mysql installation status, and the referenced Debian commit/advisory.

Mitigation direction

  • Upgrade affected Debian pdns-backend-mysql packages to vendor-fixed versions.
  • Confirm Debian guidance for the exact supported release and package version.
  • Review the pdns MySQL account privileges for least-privilege alignment.
  • Restrict database access to trusted PowerDNS hosts only.
  • Assess whether any non-MySQL backends are incorrectly flagged by tooling.

Validation and detection

  • Inventory Debian systems running pdns-backend-mysql.
  • Check installed pdns package versions against 3.3.1-1 and Debian advisories.
  • Inspect MySQL grants for the pdns database user.
  • Verify PowerDNS continues resolving after privilege corrections or package updates.
  • Document any exceptions where vendor guidance is unavailable.
Prepared
Confidence
medium
Sources
4

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-276: 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
description · low confidence lookup

Database behavior lookup

The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2014-7210 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
Critical
CVSS
9.8 (3.1)
Known Exploited
No
Published

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

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
3Source 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
9.8CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

9.8Critical
CVSS 3.1 vector shape for CVE-2014-7210Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

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

Products and packages named in the record

VendorProductVersion / packageStatus
Debianpdns0unaffected
Weakness

CWE details

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

CWE-276 · source CWE mapping

Incorrect Default Permissions

Incorrect Default Permissions represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.