CVE-2018-15160: The libesedb_catalog_definition_read function in libesedb_catalog_definition.c in libesedb through 2018-04-01

Q: How do I fix CVE-2018-15160?

libesedb: upgrade to newer than 2018-04-01. Exact commands for each OS are on this page.

Q: Is CVE-2018-15160 being exploited?

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

Q: What does CVE-2018-15160 affect?

CVE-2018-15160 affects libesedb. Severity is medium (CVSS 6.5). The libesedb_catalog_definition_read function in libesedb_catalog_definition.c in libesedb through 2018-04-01 allows remote attackers to cause a heap-based buffer over-read via a crafted esedb file. NOTE: the vendor has disputed this as des

Q: How urgent is CVE-2018-15160?

Priority 46/100. Public exploit reference

This month

MEDIUM 6.5UPGRADE

CVE-2018-15160 is a medium-severity flaw (CVSS 6.5) affecting libesedb. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

The libesedb_catalog_definition_read function in libesedb_catalog_definition.c in libesedb through 2018-04-01 allows remote attackers to cause a heap-based buffer over-read via a crafted esedb file. NOTE: the vendor has disputed this as described in the GitHub issue comments

Why this priority

Public exploit reference

A fixed release or distro patch exists.

Risk facts

CVSS score	6.5 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	Required
EPSS exploit chance	1.5% (top 27%)
CISA exploited list	No
Weakness	CWE-125
Published	2018-09-01
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: libesedb project

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

Am I affected?

Timeline

2018-09-01 03:29 UTCPublished CVE record published
2026-06-17 01:42 UTCUpdated Record last modified

libesedb project libesedb UPGRADE

Affected: <= 2018-04-01

Fixed in: newer than 2018-04-01

Safe to downgrade to: no unaffected older release

1. Check installed version

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

2. UPGRADE to newer than 2018-04-01 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade libesedb

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade libesedb

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

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-2018-15160?

libesedb: upgrade to newer than 2018-04-01. Exact commands for each OS are on this page.

Is CVE-2018-15160 being exploited?

CVE-2018-15160 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-2018-15160 affect?

CVE-2018-15160 affects libesedb. Severity is medium (CVSS 6.5). The libesedb_catalog_definition_read function in libesedb_catalog_definition.c in libesedb through 2018-04-01 allows remote attackers to cause a heap-based buffer over-read via a crafted esedb file. NOTE: the vendor has disputed this as des

How urgent is CVE-2018-15160?

Priority 46/100. Public exploit reference

Software pages

GitHub vulnerabilities

Related CVEs

CVE-2018-15161 MEDIUM 6.5 UPGRADE The libesedb_key_append_data function in libesedb_key.c in libesedb through 2018-04-01 allows remote attackers
CVE-2018-15159 MEDIUM 6.5 UPGRADE The libesedb_page_read_tags function in libesedb_page.c in libesedb through 2018-04-01 allows remote attackers
CVE-2018-15158 MEDIUM 6.5 UPGRADE The libesedb_page_read_values function in libesedb_page.c in libesedb through 2018-04-01 allows remote attacke

References

← Back to latest CVEs