LiveActive security incident?Get immediate response
CVE Record

CVE-2017-12108: An exploitable integer overflow vulnerability exists in the xls_preparseWorkSheet function of libxls 1.4 wh...

An exploitable integer overflow vulnerability exists in the xls_preparseWorkSheet function of libxls 1.4 when handling a MULBLANK record. 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-12108 is a high-severity file-parsing flaw in libxls 1.4. A malicious XLS spreadsheet can corrupt memory when opened or processed, creating potential remote code execution risk. Business exposure depends on where libxls or the tested R readxl package path processes untrusted spreadsheets.

Executive priority

Prioritize this as high where spreadsheet intake is part of business operations. It combines common file delivery with possible code execution, but urgency should be driven by confirmed vulnerable deployments and untrusted XLS exposure, not by known active exploitation.

Technical view

The vulnerability is an integer overflow in libxls 1.4 xls_preparseWorkSheet handling of a MULBLANK record. Talos reports a crafted XLS can trigger memory corruption and remote code execution. CVSS 3.0 is 8.8 with user interaction required and high confidentiality, integrity, and availability impact.

Likely exposure

Most likely exposed systems are workstations, services, or data pipelines that use libxls 1.4, including the tested readxl package 1.0.0 path for R, to open or parse XLS files from email, uploads, partners, or other untrusted sources.

Exploitation context

The source bundle does not show CISA KEV listing or active exploitation. Exploitation requires a malicious XLS file to be opened or processed by vulnerable code. Treat internet-facing upload workflows and email-driven spreadsheet handling as higher risk because they increase attacker delivery opportunities.

Researcher notes

Evidence supports libxls 1.4 and the tested readxl package 1.0.0 path. The bundle does not provide CWE mapping, active exploitation evidence, or a named fixed version. Validate dependency embedding carefully because libxls may be included indirectly.

Mitigation direction

  • Inventory libxls and readxl usage across applications, analytics systems, and file-processing workflows.
  • Check libxls and readxl vendor guidance for fixed versions or official mitigations.
  • Avoid processing untrusted XLS files with vulnerable components until remediated.
  • Isolate spreadsheet parsing from sensitive systems where immediate replacement is not possible.
  • Prioritize patching systems that parse emailed, uploaded, or partner-supplied spreadsheets.

Validation and detection

  • Confirm whether libxls 1.4 is present directly or through bundled dependencies.
  • Identify workflows that parse XLS files from untrusted or semi-trusted sources.
  • Review dependency manifests and runtime images for readxl package 1.0.0 where applicable.
  • Check logs for crashes or memory-corruption symptoms during XLS parsing.
  • Verify remediation by confirming vulnerable library versions are no longer deployed.
Prepared
Confidence
high
Sources
3

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-12108 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
2Source 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-12108Attack 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.4 readxl package 1.0.0 for R (tested using Microsoft R 4.3.1)Listed
Weakness

CWE details

No CWE listed

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