LiveActive security incident?Get immediate response
CVE Record

CVE-2017-2919: An exploitable stack based buffer overflow vulnerability exists in the xls_getfcell function of libxls 1.3.4.

An exploitable stack based buffer overflow vulnerability exists in the xls_getfcell function of libxls 1.3.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-2919 is a high-severity flaw in libxls 1.3.4. A malicious Excel XLS file can corrupt memory when parsed, potentially letting an attacker run code on the affected system. User interaction is required because a vulnerable workflow must open or process the file.

Executive priority

Treat this as a high-priority remediation item if your organization processes untrusted XLS files. Business risk is highest in document ingestion systems because successful exploitation could affect data confidentiality, integrity, and service availability.

Technical view

The vulnerability is a stack-based buffer overflow in libxls xls_getfcell. The published CVSS 3.0 score is 8.8, with network attack vector, low complexity, no privileges required, user interaction required, and high confidentiality, integrity, and availability impact.

Likely exposure

Exposure is most likely where applications, services, or batch jobs use libxls 1.3.4 to parse untrusted or externally supplied XLS files, including uploads, email attachments, or document-processing pipelines.

Exploitation context

The source bundle states a specially crafted XLS file can trigger memory corruption and remote code execution. It does not cite CISA KEV listing or other evidence of active exploitation, so active exploitation is not established here.

Researcher notes

The record identifies libxls 1.3.4 and xls_getfcell specifically. Evidence supports crafted-file-triggered memory corruption with possible RCE, but the bundle does not provide safe validation artifacts, patched version details, or confirmed in-the-wild exploitation.

Mitigation direction

  • Inventory systems and dependencies for libxls 1.3.4 usage.
  • Check libxls, Debian, and Gentoo guidance for fixed packages or supported upgrade paths.
  • Prioritize remediation for internet-facing or user-upload XLS parsing workflows.
  • Limit processing of untrusted XLS files until remediation is complete.
  • Run file parsing in isolated, least-privileged environments where feasible.

Validation and detection

  • Review SBOMs, package manifests, and runtime images for libxls 1.3.4.
  • Map all workflows that parse XLS files from external sources.
  • Confirm vendor advisory status against deployed operating system packages.
  • Verify upload, email, and batch-processing paths cannot reach vulnerable parsers.
  • Confirm remediation through package version review after updates.
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-2919 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-2919Attack 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.3.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.