LiveActive security incident?Get immediate response
CVE Record

CVE-2017-12109: 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 MULRK 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-12109 is a high-severity flaw in libxls 1.4 XLS parsing. A malicious spreadsheet can corrupt memory and may run code when a vulnerable application opens or processes it. The risk is highest where untrusted XLS files are handled by analysts, email workflows, upload pipelines, or R/readxl-based processing.

Executive priority

Treat as high priority where XLS processing is exposed to external files or routine analyst handling. Prioritize inventory and upgrades, but do not claim emergency active exploitation without new evidence.

Technical view

The issue is an integer overflow in xls_preparseWorkSheet while handling a MULRK record. Talos reports that a crafted XLS file can trigger memory corruption leading to remote code execution. The CVSS vector requires user interaction, with no privileges needed and high confidentiality, integrity, and availability impact.

Likely exposure

Exposure depends on whether libxls 1.4, or tested dependent use through R readxl 1.0.0, exists in file-processing paths. The source bundle does not prove all downstream affected versions, so validate actual dependency linkage and XLS ingestion routes.

Exploitation context

Sources support malicious-file exploitation, not confirmed active exploitation. CVE KEV status is false in the bundle. The attacker needs a vulnerable system or user-driven workflow to open or parse a specially crafted XLS file.

Researcher notes

The bundle identifies libxls 1.4 and a tested readxl/R context, but does not provide a full affected-version matrix or patch details. Focus on dependency provenance, parser reachability, and whether untrusted XLS files cross the boundary.

Mitigation direction

  • Check libxls and downstream package vendor guidance for fixed versions or mitigations.
  • Upgrade libxls/readxl-dependent components where vendor-supported patched versions exist.
  • Block or quarantine untrusted legacy XLS files in high-risk workflows.
  • Run spreadsheet parsing in sandboxed or least-privileged processing environments.
  • Prefer safer conversion or inspection services before internal processing.

Validation and detection

  • Inventory systems and applications that parse XLS files with libxls.
  • Check R environments for readxl usage and transitive libxls exposure.
  • Review upload, email, and data-pipeline paths accepting legacy XLS files.
  • Confirm deployed library versions against vendor advisories and package metadata.
  • Verify mitigations with benign regression files, not weaponized samples.
Prepared
Confidence
medium
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-12109 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-12109Attack 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.