Skip to content
Fencer Intel
medium 5.3

CVE-2015-5186 json

Audit before 2.4.4 in Linux does not sanitize escape characters in filenames.

published 2017-09-06 9 y ago modified 2026-06-17 4 mo ago also EUVD-2015-5187

cvss
5.3
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
3.1%
EPSS 3.1% chance of exploitation in 30 days, percentile 87%
public exploits
0
none known

Summary

Audit before 2.4.4 in Linux does not sanitize escape characters in filenames.

Patch / fix

  • audit Debian 14, Debian 13, Debian 12 1:2.4.4-1

debian advisories DEBIAN-CVE-2015-5186

  • audit SLES for SAP 12 SP3, SLES 12 SP3, SLED 12 SP3 +1 more 2.8.1-8.3.1
  • audit-secondary SLES for SAP 12 SP3, SLES 12 SP3, SLED 12 SP3 2.8.1-8.3.3
  • audit SLES for SAP 12 SP4, SLES 12 SP4, SLED 12 SP4 +1 more 2.8.1-10.3.2
  • audit-secondary SLES for SAP 12 SP4, SLES 12 SP4, SLED 12 SP4 2.8.1-10.3.2

suse advisories SUSE-SU-2019:1166-1SUSE-SU-2019:0563-1

  • audit openSUSE Tumbleweed 2.5-1.82

opensuse advisories openSUSE-SU-2024:10252-1

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-5186 updated cvss 4.3

Audit: log terminal emulator escape sequences handling

  • Red Hat Enterprise Linux 4 audit Red Hat Enterprise Linux 5 audit Red Hat Enterprise Linux 6 audit, audit-libs, audispd-plugins, audit-libs-python Red Hat Enterprise Linux 7 audit, audit-libs, audispd-plugins, audit-libs-python Red Hat Enterprise Virtualization 3 rhev-hypervisor
    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.10% chance of exploitation in the next 30 days, higher than 87% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.0 5.3 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
NVD 2.0 5.0 AV:N/AC:L/Au:N/C:N/I:P/A:N

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.