LiveActive security incident?Get immediate response
CVE Record

CVE-2018-10887: A flaw was found in libgit2 before version 0.27.3.

A flaw was found in libgit2 before version 0.27.3. It has been discovered that an unexpected sign extension in git_delta_apply function in delta.c file may lead to an integer overflow which in turn leads to an out of bound read, allowing to read before the base object. An attacker may use this flaw to leak memory addresses or cause a Denial of Service.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2018-10887 affects libgit2 before 0.27.3. A crafted Git object could trigger incorrect integer handling, causing an out-of-bounds read. The stated impacts are possible memory address leakage or denial of service. There is no source-provided evidence of active exploitation.

Executive priority

Treat this as a moderate maintenance and resilience issue. It is not documented as actively exploited, but affected systems can expose memory details or become unavailable when processing malicious repository data. Prioritize shared developer infrastructure and internet-facing services using libgit2.

Technical view

The flaw is an unexpected sign extension in git_delta_apply in delta.c, leading to integer overflow and an out-of-bounds read before the base object. Sources identify CWE-194 and fixed upstream release 0.27.3, with Debian LTS security updates also published.

Likely exposure

Exposure is most likely where applications, developer tooling, CI systems, or services use libgit2 before 0.27.3, especially when processing repository data from untrusted or semi-trusted sources. Static or bundled libgit2 copies need separate verification.

Exploitation context

The provided sources say an attacker may use the flaw to leak memory addresses or cause denial of service. KEV status is false, and the bundle does not cite public active exploitation, exploit availability, or confirmed real-world abuse.

Researcher notes

Evidence is strongest for affected version, root cause, and impact class. The source bundle lacks CVSS, exploit maturity, and detailed environmental prerequisites. Validate exposure by tracing libgit2 use in package dependencies and embedded application builds rather than relying only on OS package inventory.

Mitigation direction

  • Upgrade libgit2 to version 0.27.3 or later.
  • Apply distribution security updates where libgit2 is packaged by the OS.
  • Identify applications that bundle or statically link libgit2.
  • Check vendor guidance for products embedding libgit2.
  • Prioritize systems processing untrusted Git repository data.

Validation and detection

  • Inventory installed and bundled libgit2 versions.
  • Confirm runtime libraries report version 0.27.3 or later.
  • Review SBOMs for statically linked libgit2 copies.
  • Verify OS package advisories have been applied.
  • Regression test Git repository handling after updates.
Prepared
Confidence
medium
Sources
8

Public sources used

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-194: 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-10887 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
7Source 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
libgit2libgit2before version 0.27.3Listed
Weakness

CWE details

CWE-194

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

CWE-194 · source CWE mapping

Unexpected Sign Extension

Unexpected Sign Extension represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

Open CWE intelligenceSame-CWE CVEs