Skip to content
Fencer Intel
medium 6.8

CVE-2015-2754 json

FreeXL before 1.0.0i allows remote attackers to cause a denial of service (stack corruption) and possibly execute arbitrary code via a craf…

published 11y ago modified 4mo ago also EUVD-2015-2844

cvss
6.8
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
3.3%
EPSS 3.3% chance of exploitation in 30 days, percentile 88%
public exploits
0
none known

Summary

FreeXL before 1.0.0i allows remote attackers to cause a denial of service (stack corruption) and possibly execute arbitrary code via a crafted workbook, related to a "premature EOF."

Patch / fix

  • freexl Debian 14, Debian 13, Debian 12 1.0.0g-1+deb8u1

debian advisories DEBIAN-CVE-2015-2754

  • freexl Ubuntu 14.04 LTS 1.0.0g-1ubuntu0.14.04.1

ubuntu advisories UBUNTU-CVE-2015-2754

Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

  • freexl openSUSE Tumbleweed 1.0.2-2.3

opensuse advisories openSUSE-SU-2024:10539-1

Is CVE-2015-2754 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2015-2754 updated cvss 4.4

freexl: multiple flaws when parsing malformed input

  • Red Hat OpenShift Enterprise 2 freexl
    affected: no fix planned “Will not fix”

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

3.34% chance of exploitation in the next 30 days, higher than 88% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 2.0 6.8 AV:N/AC:M/Au:N/C:P/I:P/A:P

Classification

Weakness
  • CWE-20 Improper Input Validation

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.