Security readout for executives and security teams
Plain-English summary
This is a low-severity Exiv2 flaw where opening a malicious image for metadata parsing can expose a small amount of stack memory. It requires the victim system or user to process the crafted file. The bug is fixed in Exiv2 v0.27.4.
Executive priority
Treat as routine patching unless Exiv2 processes untrusted images in business workflows. The likely impact is limited memory disclosure, not remote system takeover, but internet-facing image processing increases relevance.
Technical view
Exiv2 v0.27.3 and earlier can read uninitialized memory while parsing metadata from a crafted image. The CVSS vector requires local interaction and user involvement, with low confidentiality and integrity impact and no availability impact. The issue maps to CWE-908.
Likely exposure
Exposure is most likely where Exiv2 CLI or the Exiv2 library processes untrusted images, such as metadata inspection workflows, upload handling, or analyst workstations. Confirm actual exposure through local package and dependency inventory.
Exploitation context
The sources describe potential leakage of a few bytes of stack memory if a victim runs Exiv2 on a crafted image. CISA KEV status is false in the bundle, and no cited source states active exploitation.
Researcher notes
The public record identifies the affected range as versions before v0.27.4 and the trigger as crafted image metadata parsing. Evidence provided does not include active exploitation, broad impact details, or a named workaround beyond upgrading.
Mitigation direction
- Upgrade Exiv2 to v0.27.4 or later.
- Apply fixed distribution packages from your operating-system vendor.
- Avoid processing untrusted images with vulnerable Exiv2 builds.
- Check vendor advisories before relying on alternate mitigations.
Validation and detection
- Inventory installed Exiv2 versions and linked library dependencies.
- Find services or scripts that invoke Exiv2 on uploaded images.
- Confirm patched packages are deployed on image-processing hosts.
- Review vendor advisories for your distribution-specific fixed versions.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-908: 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 lookupCVE-2021-29623 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Low
- CVSS
- 3.6 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:N
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.
CVSS vector scores
1 official scoreWe 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.
CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:N12.5Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
3.6LowVector: CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/Exiv2/exiv2/security/advisories/GHSA-6253-qjwm-3q4vCVE reference
- https://github.com/Exiv2/exiv2/pull/1627CVE reference
- FEDORA-2021-d1d5a0bf0fCVE reference · vendor-advisory
- FEDORA-2021-8253c78bd7CVE reference · vendor-advisory
- FEDORA-2021-bdba47348cCVE reference · vendor-advisory
- FEDORA-2021-8917c5d9d2CVE reference · vendor-advisory
- GLSA-202312-06CVE reference · vendor-advisory
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Use of Uninitialized Resource
Use of Uninitialized Resource represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
