LiveActive security incident?Get immediate response
CVE Record

CVE-2021-34055: jhead 3.06 is vulnerable to Buffer Overflow via exif.c in function Put16u.

jhead 3.06 is vulnerable to Buffer Overflow via exif.c in function Put16u.

HighCVSS 7.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2021-34055 is a high-severity memory corruption flaw in jhead 3.06, a JPEG EXIF handling tool. A crafted image could trigger a buffer overflow when a user or workflow processes it. Business risk is highest where jhead handles untrusted uploads, email attachments, or image pipelines.

Executive priority

Treat as a high-priority patching item for servers, workstations, or pipelines that process untrusted images. Urgency is lower where jhead is absent or only used on trusted files, but inventory should be completed because affected product metadata is incomplete.

Technical view

The issue is reported as CWE-120 buffer overflow in exif.c Put16u. CVSS 3.1 is 7.8: local attack vector, low complexity, no privileges, user interaction required, and high confidentiality, integrity, and availability impact. Debian published DSA-5294 and DLA-3219-1 security updates.

Likely exposure

Exposure is likely limited to systems that install or package jhead and process attacker-controlled JPEG/EXIF files. The source bundle does not identify CPEs, downstream embedded uses, or a complete affected version range beyond jhead 3.06.

Exploitation context

The source bundle does not report active exploitation, and the CVE is not listed as KEV. The CVSS vector requires user interaction, meaning exploitation likely depends on a person or automated workflow opening or processing a malicious image.

Researcher notes

Public details in the bundle are sparse: the named vulnerable function is Put16u in exif.c, with CWE-120 classification and a GitHub issue reference. Do not assume remote network exploitation; the published CVSS vector is local with user interaction required.

Mitigation direction

  • Identify all systems and containers with jhead installed.
  • Prioritize update through Debian or the relevant package vendor.
  • Check Debian DSA-5294 and DLA-3219-1 for fixed package guidance.
  • Restrict jhead from processing untrusted images until patched.
  • Run image-processing jobs with least privilege and isolation.

Validation and detection

  • Inventory package versions and confirm whether jhead 3.06 is present.
  • Review image upload, email, and batch-processing workflows for jhead use.
  • Confirm patched packages from Debian or your distribution are installed.
  • Check logs for crashes during JPEG or EXIF processing.
  • Document any compensating isolation controls around image processing.
Prepared
Confidence
medium
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-120: 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-2021-34055 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
High
CVSS
7.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/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
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
7.8CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H1.85.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.8High
CVSS 3.1 vector shape for CVE-2021-34055Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/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
n/an/an/aListed
Weakness

CWE details

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

CWE-120 · source CWE mapping

Buffer Copy without Checking Size of Input ('Classic Buffer Overflow')

Buffer Copy without Checking Size of Input ('Classic Buffer Overflow') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.