libhesiod0 3.2.1-3.1~build0.18.04.1: libhesiod0 3.2.1-3.1~build0.18.04.1 for Ubuntu 18.04.6 LTS (bionic)

libhesiod0 3.2.1-3.1~build0.18.04.1, released March 28, 2017, fixes 2 CVEs in libhesiod0. None of them is reported as exploited. Patch Radar priority: Routine. The product is no longer supported.

RoutineUnsupported product

CVEs closed

None rated Critical

Exploited

None reported

Highest CVSS

n/a

No CVSS score published

Highest EPSS

0.0683

94th percentile

Priority of the 2 CVEs

Patch now 0
                                Urgent 0
                                High 0
                                Routine 2

Fixed package versions

Product	Release	Fixed in
libhesiod0	Ubuntu 18.04.6 LTS (bionic)	3.2.1-3.1~build0.18.04.1

CVEs this fix closes

Priority	CVE	Title	CVSS	EPSS	Exploitation
Routine	CVE-2016-10152	hesiod: The read_config_file function in lib/hesiod.c in Hesiod 3.2.1 falls back to the ".athena.mit.edu" default domain when...	n/a	0.0683	None reported
Routine	CVE-2016-10151	hesiod: The hesiod_init function in lib/hesiod.c in Hesiod 3.2.1 compares EUID with UID to determine whether to use configura...	n/a	0.0039	None reported

Also fixes CVE-2016-10152

hesiod 3.2.1-3.1~build0.18.04.1
hesiod on Ubuntu 18.04.6 LTS (bionic)

For tools and AI agents

This page as data: JSON · Markdown

Link to this page

If this page saved you time, a link to it in your ticket, advisory or write-up helps others find it.

HTML

<a href="https://patchblox.com/security/fix/linux/ubuntu-bionic-libhesiod0-3.2.1-3.1-build0.18.04.1">libhesiod0 3.2.1-3.1~build0.18.04.1 on Patchblox Patch Radar</a>

Reusing the data? How to credit Patch Radar.

Which servers are still behind?

Patchblox compares the installed package on every Linux machine against the fixed version for its release, including machines reported through Azure Update Manager.

Get a demo

Patch Radar data is free to use with attribution. Terms and how to credit it.

Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.