LiveActive security incident?Get immediate response
CVE Record

CVE-2018-25012: A heap-based buffer overflow was found in libwebp in versions before 1.0.1 in GetLE24().

A heap-based buffer overflow was found in libwebp in versions before 1.0.1 in GetLE24().

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2018-25012 is a libwebp memory-safety flaw in image parsing. The public record says versions before 1.0.1 have a heap-based buffer overflow in GetLE24(). Business urgency depends on where libwebp is embedded in browsers, apps, or services that process WebP images.

Executive priority

Track and remediate as a dependency hygiene issue with elevated attention for internet-facing image processing. Do not treat it as confirmed exploited based on the supplied evidence. Patch through normal vendor channels, prioritizing systems that parse untrusted media.

Technical view

The CVE describes a heap-based buffer overflow in libwebp before 1.0.1, specifically in GetLE24(). The source bundle lists CWE-125 and references an upstream libwebp commit plus an OSS-Fuzz issue. No CVSS score, detailed impact, or vendor-specific package mapping is provided.

Likely exposure

Exposure is most likely where vulnerable libwebp builds are used to decode untrusted WebP images. This may include applications, services, or packaged dependencies, but the supplied sources only name libwebp and do not enumerate downstream products.

Exploitation context

The source bundle does not show CISA KEV listing, active exploitation, public exploitation, or exploit maturity. Treat exploit status as unconfirmed. The issue came through OSS-Fuzz references, suggesting parser fuzzing found the defect, but operational exploitability is not established here.

Researcher notes

The available evidence is sparse: no CVSS vector, no complete affected product list, and conflicting metadata around version wording. Base validation on actual libwebp versions and vendor backport notes, not only upstream version numbers.

Mitigation direction

  • Inventory direct and bundled libwebp usage across servers, desktops, containers, and applications.
  • Upgrade libwebp to 1.0.1 or later where vendor guidance confirms the fix.
  • Apply distribution or application vendor updates for packages embedding libwebp.
  • Prioritize systems that process untrusted WebP images from users or the internet.
  • Monitor vendor advisories for downstream product-specific fixes and backports.

Validation and detection

  • Check installed libwebp package versions and embedded library copies.
  • Confirm whether runtime binaries link against vulnerable libwebp builds.
  • Review SBOMs and container images for libwebp versions before 1.0.1.
  • Verify patched packages include the referenced upstream libwebp fix or vendor backport.
  • Confirm image-processing workflows reject or isolate untrusted inputs where patching is delayed.
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-125: 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-2018-25012 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
4Source links

CVSS and timeline data

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

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/alibwebplibwebp 1.0.1Listed
Weakness

CWE details

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

CWE-125 · source CWE mapping

Out-of-bounds Read

Out-of-bounds Read represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.