LiveActive security incident?Get immediate response
CVE Record

CVE-2018-9145: In the DataBuf class in include/exiv2/types.hpp in Exiv2 0.26, an issue exists in the constructor with an i...

In the DataBuf class in include/exiv2/types.hpp in Exiv2 0.26, an issue exists in the constructor with an initial buffer size. A large size value may lead to a SIGABRT during an attempt at memory allocation. NOTE: some third parties have been unable to reproduce the SIGABRT when using the 4-DataBuf-abort-1 PoC file.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2018-9145 is a crash risk in Exiv2 0.26 when handling a very large buffer size. In practical terms, software that uses Exiv2 to process untrusted image metadata could abort instead of completing normally. The public record notes reproducibility concerns, so business urgency depends on where Exiv2 is exposed.

Executive priority

Handle as a targeted availability risk, not a confirmed breach indicator. Prioritize remediation where image processing is internet-facing or business-critical, while noting the incomplete severity data and disputed reproducibility.

Technical view

The CVE describes an issue in the DataBuf constructor in include/exiv2/types.hpp in Exiv2 0.26. A large initial buffer size may trigger SIGABRT during memory allocation. The record does not provide CVSS, CWE, confirmed fixed versions, or a complete affected-product matrix.

Likely exposure

Exposure is most plausible where Exiv2 0.26 is installed directly or embedded in applications that parse image metadata from users, customers, uploads, email attachments, or automated media pipelines.

Exploitation context

The source bundle includes a public PoC repository reference, but the CVE notes some third parties could not reproduce the SIGABRT with the referenced PoC. CISA KEV is false, and the provided sources do not support active exploitation.

Researcher notes

Key gaps are missing CVSS, absent CWE mapping, unclear fixed-version detail in the CVE record, and disputed PoC reproducibility. Validation should focus on package provenance, exposed parsing paths, and vendor advisory correlation rather than assuming exploitability.

Mitigation direction

  • Inventory systems and applications using Exiv2, especially version 0.26.
  • Check Gentoo, Red Hat, SUSE, and upstream Exiv2 guidance for fixed package versions.
  • Prioritize exposed upload or media-processing services before internal-only tooling.
  • Limit untrusted image processing until vendor remediation is confirmed.
  • Monitor package advisories for distro-specific backports or patch status.

Validation and detection

  • Confirm installed Exiv2 versions across servers, containers, and desktop imaging tools.
  • Identify applications that link to or bundle Exiv2 for metadata parsing.
  • Review media upload paths for untrusted image processing exposure.
  • Check vulnerability scanner findings against distro package advisory status.
  • Treat exploitability as uncertain unless reproduced in an authorized test environment.
Prepared
Confidence
medium
Sources
6

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.

cve · low confidence lookup

CVE-2018-9145 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
Unknown
CVSS
Not scored
Known Exploited
No
Published
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.

0CVSS vectors
0Timeline events
0ADP providers
5Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

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