jhead 1:3.00-8~ubuntu0.2+esm1: jhead 1:3.00-8~ubuntu0.2+esm1 for Ubuntu 18.04.6 LTS (bionic)

jhead 1:3.00-8~ubuntu0.2+esm1, released March 23, 2022, fixes 2 CVEs in jhead. None of them is reported as exploited. Patch Radar priority: High. The product is no longer supported.

HighUnsupported product

CVEs closed

None rated Critical

Exploited

None reported

Highest CVSS

7.8

Base score, 0 to 10

Highest EPSS

0.0107

65th percentile

Priority of the 2 CVEs

Patch now 0
                                Urgent 0
                                High 1
                                Routine 1

Fixed package versions

Product	Release	Fixed in
jhead	Ubuntu 18.04.6 LTS (bionic)	1:3.00-8~ubuntu0.2+esm1

CVEs this fix closes

Priority	CVE	Title	CVSS	EPSS	Exploitation
High	CVE-2021-28277	jhead: A Heap-based Buffer Overflow vulnerabilty exists in jhead 3.04 and 3.05 is affected by: Buffer Overflow via the Remov...	7.8	0.0087	None reported
Routine	CVE-2021-3496	jhead: A heap-based buffer overflow was found in jhead in version 3.06 in Get16u() in exif.c when processing a crafted file.	n/a	0.0107	None reported

Also fixes CVE-2021-28277

jhead 1:3.04-1ubuntu0.2+esm1
jhead on Ubuntu 20.04 LTS (focal)
DEBIAN-CVE-2021-28277
jhead on Debian 12.15 (bookworm), Debian 13.5 (trixie), Debian 14

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-jhead-1-3.00-8-ubuntu0.2-esm1">jhead 1:3.00-8~ubuntu0.2+esm1 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.