Skip to content
Fencer Intel
high 7.5

CVE-2015-1386 json

Directory traversal vulnerability in unshield 1.0-1.

published 9y ago modified 4mo ago also EUVD-2015-1523

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

Summary

Directory traversal vulnerability in unshield 1.0-1.

Patch / fix

  • unshield Debian 14, Debian 13, Debian 12 1.4-1

debian advisories DEBIAN-CVE-2015-1386

  • unshield openSUSE Tumbleweed 1.4.3-2.9

opensuse advisories openSUSE-SU-2024:11484-1

Is CVE-2015-1386 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-1386 updated cvss 2.1

unshield: directory traversal

  • Red Hat All currently supported Red Hat products
    not affected: vulnerable code not present

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

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

Exploits and checks

  • openwall.com http://www.openwall.com/lists/oss-security/2015/01/27/27 referenced PoC, tagged "exploit" by a source, unverified
  • bugzilla.redhat.com https://bugzilla.redhat.com/show_bug.cgi?id=1185717 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

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

Classification

Weakness
  • CWE-22 Improper Limitation of a Pathname to a Restricted Directory

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.