cve.bz

CVE-2018-18586 kyzer libmspack: Path traversal

5.3 mediumExploit referenceEPSS 3.3%

Medium (5.3) in kyzer libmspack. EPSS 3.3% estimated probability of exploitation activity in the next 30 days.

On this page
chmextract.c in the chmextract sample program, as distributed with libmspack before 0.8alpha, does not protect against absolute/relative pathnames in CHM files, leading to Directory Traversal. NOTE: the vendor disputes that this is a libmspack vulnerability, because chmextract.c was only intended as a source-code example, not a supported application

Severity

CVSS 3.0

5.3 medium
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
EPSS
3.3% (unchanged from 3.3% a week ago; 3.3% 30 days ago) estimated probability of exploitation activity in the next 30 days; 89th percentile. Scored 2026-11-21. A forecast for this CVE across the internet, not for your own systems.
CWE
CWE-22 Improper Limitation of a Pathname to a Restricted Directory (Path traversal)
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2018-18586 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2018-18586?via=ask-ai-copy and https://cve.bz/cve/CVE-2018-18586?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2018-18586 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
kyzer:libmspack0.3:alpha
kyzer:libmspack0.4:alpha
kyzer:libmspack0.5:alpha
kyzer:libmspack0.6:alpha
kyzer:libmspack0.7:alpha

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12, 13, 14libmspack0.8-1DEBIAN-CVE-2018-18586
SUSELinux Enterprise Micro 5.0, Linux Enterprise Micro 5.1, Linux Enterprise Module for Basesystem 15 SP3libmspack0.6-3.14.1SUSE-SU-2022:0069-1
SUSELinux Enterprise Real Time 15 SP2libmspack0.6-3.14.1SUSE-SU-2022:0069-2
SUSELinux Enterprise Server 12 SP5, Linux Enterprise Server for SAP Applications 12 SP5, Linux Enterprise Software Development Kit 12 SP5libmspack0.4-15.13.1SUSE-SU-2022:4287-1
openSUSELeap 15.3libmspack0.6-3.14.1openSUSE-SU-2022:0069-1
Alpinev3.6, v3.7, v3.8 and 16 morelibmspack0.8_alpha-r0ALPINE-CVE-2018-18586

From the distributions' data via OSV.dev: the Debian Security Tracker; SUSE security data, CC BY 4.0; the Alpine secdb, CC BY-SA 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · SUSE · openSUSE · Alpine.

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

This issue did not affect the versions of libmspack as shipped with Red Hat Enterprise Linux 7.

ProductPackageStateAdvisory
Red Hat Enterprise Linux 7libmspackNot affected
Red Hat Enterprise Linux 8libmspackNot affected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2018-18586.

Attack patterns (CAPEC)

  • CAPEC-64 Using Slashes and URL Encoding Combined to Bypass Validation Logic Likelihood: High · Severity: High
  • CAPEC-76 Manipulating Web Input to File System Calls Likelihood: High · Severity: Very High
  • CAPEC-78 Using Escaped Slashes in Alternate Encoding Likelihood: High · Severity: High
  • CAPEC-79 Using Slashes in Alternate Encoding Likelihood: High · Severity: High
  • CAPEC-126 Path Traversal Likelihood: High · Severity: Very High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON