CVE-2017-2923: An exploitable heap based buffer overflow vulnerability exists in the 'read_biff_next_record function' of Free

This month

HIGH 8.8WATCHLISTDOWNGRADEMITIGATE

CVE-2017-2923 is a high-severity flaw (CVSS 8.8) affecting freexl, debian linux. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

An exploitable heap based buffer overflow vulnerability exists in the 'read_biff_next_record function' of FreeXL 1.0.3. 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.

Why this priority

High severity
On your watchlist

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score	8.8 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	Required
EPSS exploit chance	3.2% (top 12%)
CISA exploited list	No
Weakness	CWE-787
Published	2018-04-24
Last modified	2026-06-17

Publisher (CNA): Talos · Vendor: debian · freexl project

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2018-04-24 19:29 UTCPublished CVE record published
2026-06-17 01:17 UTCUpdated Record last modified

freexl project freexl DOWNGRADE

Affected: 1.0.3

Fixed in: no fixed release known

Safe to downgrade to: a release before 1.0.3

1. Check installed version

apt-cache policy freexl || rpm -q freexl || freexl --version

2. No fixed release: DOWNGRADE to a release before 1.0.3 (Debian / Ubuntu)

apt-cache madison freexl sudo apt install freexl=<VERSION_BEFORE_1.0.3> sudo apt-mark hold freexl

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list freexl sudo dnf downgrade freexl-<VERSION_BEFORE_1.0.3> sudo dnf versionlock add freexl

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

debian debian linux MITIGATE

Affected: 8.0 · 9.0

Fixed in: no fixed release known

Safe to downgrade to: a release before 8.0

Check your OS release

cat /etc/os-release; uname -r

Debian / Ubuntu

sudo apt update && sudo apt full-upgrade

RHEL / Amazon Linux / Fedora

sudo dnf upgrade --refresh

Windows

Install the latest cumulative update from Windows Update

If no patch exists yet

OS downgrades are not safe. Apply the vendor mitigation from the advisory and restrict exposure.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2017-2923?

freexl: downgrade or apply the listed mitigation; debian linux: mitigate or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2017-2923 being exploited?

CVE-2017-2923 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2017-2923 affect?

CVE-2017-2923 affects freexl, debian linux. Severity is high (CVSS 8.8). An exploitable heap based buffer overflow vulnerability exists in the 'read_biff_next_record function' of FreeXL 1.0.3. A specially crafted XLS file can cause a memory corruption resulting in remote code execution. An attacker can send mali

How urgent is CVE-2017-2923?

Priority 58/100. High severity; On your watchlist

Software pages

Debian vulnerabilities

Related CVEs

CVE-2018-7439 HIGH 8.8 UPGRADE MITIGATE An issue was discovered in FreeXL before 1.0.5
CVE-2018-7438 HIGH 8.8 UPGRADE MITIGATE An issue was discovered in FreeXL before 1.0.5
CVE-2018-7437 HIGH 8.8 UPGRADE MITIGATE An issue was discovered in FreeXL before 1.0.5
CVE-2018-7436 HIGH 8.8 UPGRADE MITIGATE An issue was discovered in FreeXL before 1.0.5
CVE-2018-7435 HIGH 8.8 UPGRADE MITIGATE An issue was discovered in FreeXL before 1.0.5

References

← Back to latest CVEs