LiveActive security incident?Get immediate response
CVE Record

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

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

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2018-25010 is a libwebp memory-safety flaw described as a heap-based buffer overflow in ApplyFilter() before version 1.0.1. Because libwebp is commonly embedded by other software, exposure depends on where that library is bundled. The provided sources do not include CVSS, active exploitation, or detailed impact evidence.

Executive priority

Treat this as a targeted dependency hygiene issue unless local exposure shows high-risk WebP processing. Prioritize internet-facing or automated image-processing systems first. Urgency is limited by missing severity and exploitation evidence, but memory-safety flaws in media libraries can become broadly relevant through embedded dependencies.

Technical view

The issue is reported in libwebp ApplyFilter() before 1.0.1. The bundle labels it as a heap-based buffer overflow but also lists CWE-125, creating a source inconsistency. References include an OSS-Fuzz issue and an upstream libwebp commit, but the supplied data does not describe exploitability, reachability conditions, or affected downstream products.

Likely exposure

Likely exposure is software or services that process WebP images using a vulnerable libwebp build. The source bundle does not name downstream products, package versions, or platforms. Validate both system packages and vendored copies because embedded libraries may not appear in top-level dependency lists.

Exploitation context

No provided source reports active exploitation, and the CVE is not marked in CISA KEV in the bundle. The OSS-Fuzz reference suggests testing discovered the issue, but the supplied evidence does not establish real-world attacks, public exploit availability, or practical exploit conditions.

Researcher notes

The record has incomplete severity data and a mismatch between the overflow description and CWE-125. It also states “before 1.0.1” while the affected entry lists “libwebp 1.0.1,” so validate against upstream commit and vendor advisories before making definitive version claims.

Mitigation direction

  • Inventory libwebp versions in system packages, containers, applications, and vendored dependencies.
  • Check upstream and distribution vendor guidance for the confirmed fixed libwebp release.
  • Update vulnerable libwebp builds once a vendor-supported fixed package is available.
  • Prioritize systems that automatically process untrusted or externally supplied WebP images.

Validation and detection

  • Confirm the exact libwebp version used at runtime, not only build-time dependency metadata.
  • Check application bundles and containers for statically included libwebp copies.
  • Review image-processing services for WebP handling exposed to untrusted users.
  • Verify remediation by retesting version inventory after updates or rebuilds.
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-25010 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.