LiveActive security incident?Get immediate response
CVE Record

CVE-2017-2896: An exploitable out-of-bounds write vulnerability exists in the xls_mergedCells function of libxls 1.4.

An exploitable out-of-bounds write vulnerability exists in the xls_mergedCells function of libxls 1.4. . A specially crafted XLS file can cause a memory corruption resulting in remote code execution. An attacker can send malicious XLS file to trigger this vulnerability.

HighCVSS 8.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2017-2896 is a memory-corruption flaw in libxls 1.4. A malicious XLS spreadsheet can crash or potentially take control of a system that processes it. Business risk is highest where XLS files are accepted from customers, partners, email, or automated ingestion workflows.

Executive priority

Treat this as high priority where XLS files cross trust boundaries. It is older, but legacy libraries commonly persist in import and conversion services. Prioritize internet-facing or automated file-processing systems first.

Technical view

The issue is an out-of-bounds write in libxls 1.4, specifically the xls_mergedCells function. The published CVSS 3.0 score is 8.8 with network attack vector, low complexity, no privileges required, and user interaction required. Successful exploitation may lead to remote code execution.

Likely exposure

Exposure is likely limited to systems or applications that use libxls 1.4 to parse XLS files. Risk increases when parsing happens on untrusted uploads, email attachments, imports, or document conversion pipelines.

Exploitation context

The sources describe a crafted XLS file triggering memory corruption and possible remote code execution. The bundle does not show CISA KEV listing or other cited evidence of active exploitation, so active exploitation should not be assumed.

Researcher notes

Evidence is strong for affected component, function, impact, and CVSS severity. The bundle does not provide exploit-in-the-wild confirmation, exact fixed upstream version, or detailed product embedding data. Avoid assuming downstream exposure without inventory evidence.

Mitigation direction

  • Identify and upgrade any libxls 1.4 installations using vendor guidance.
  • Apply relevant distribution security updates from Debian, Gentoo, or your package vendor.
  • Restrict untrusted XLS parsing until patched or isolated.
  • Run file parsing workloads with least privilege and process isolation.
  • Monitor vendor advisories for exact fixed package versions.

Validation and detection

  • Inventory applications and services that parse XLS files.
  • Check package manifests, SBOMs, and containers for libxls 1.4.
  • Confirm patched packages against Debian, Gentoo, or upstream advisories.
  • Review upload and ingestion paths that accept XLS files.
  • Verify parsing services run with constrained privileges.
Prepared
Confidence
high
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.

description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2017-2896 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
High
CVSS
8.8 (3.0)
Known Exploited
No
Published

Vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

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.

1CVSS vectors
0Timeline events
0ADP providers
4Source links

CVSS vector scores

1 official score

We 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.

ScoreVersionSeverityVectorExploitImpactSource
8.8CVSS 3.0HighCVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H2.85.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.0 score

8.8High
CVSS 3.0 vector shape for CVE-2017-2896Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
libxlslibxls1.4Listed
Weakness

CWE details

No CWE listed

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