Breaking News: Hijacked Releases of Microsoft’s Official agent-framework Steals Azure and CI Credentials
Read the Report
Learn How MCP Is Bypassing a Decade of Cloud Security Best Practices
Read the Report
Are you exposed? Connect a repo in minutes.
Scan your repos free

CVE-2016-10152

hesiod: Use of hard-coded unsafe configuration if configuration file cannot be opened

Overview

Published
28 Mar 2017
Modified
13 May 2026
Critical CVE
0 Registry packages
2 OS packages
4 Linux distributions
Yes Fix available

Description

The read_config_file function in lib/hesiod.c in Hesiod 3.2.1 falls back to the ".athena.mit.edu" default domain when opening the configuration file fails, which allows remote attackers to gain root privileges by poisoning the DNS cache.

Source: OX vulnerability database

Severity

9.8 · CRITICAL

CVSS 3.0 base score, scored by NVD.

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Weakness: CWE-264

Affected packages · 0

No registry package. This ID affects operating system packages only.

Operating systems · 9 fixes

Red Hat 1 release · 1 package

wont fix 1
hesiod
Red Hat fixes for CVE-2016-10152
ReleasePackageFixed in
7 hesiod +1 wont fix

debian 5 releases · 1 package

fixed 4 affected 1
hesiod
debian fixes for CVE-2016-10152
ReleasePackageFixed in
11 hesiod 3.2.1-3.1
12 hesiod 3.2.1-3.1
13 hesiod 3.2.1-3.1
14 hesiod 3.2.1-3.1
9 hesiod affected

echo 1 release · 1 package

fixed 1
hesiod
echo fixes for CVE-2016-10152
ReleasePackageFixed in
hesiod 3.2.1-3.1

ubuntu 2 releases · 1 package

fixed 2
hesiod
ubuntu fixes for CVE-2016-10152
ReleasePackageFixed in
18.04 hesiod 3.2.1-3.1~build0.18.04.1
18.04-ESM hesiod 3.2.1-3.1~build0.18.04.1

References

OX Radar and Response Center

Find threats in your stack.

OX Radar can check high-priority threats, like critical package CVEs, against your context.

Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.