Skip to content
Fencer Intel
medium 6.1

CVE-2015-5700 json

mktexlsr revision 22855 through revision 36625 as packaged in texlive allows local users to write to arbitrary files via a symlink attack.

published 2017-08-25 9 y ago modified 2026-06-17 4 mo ago also EUVD-2015-5647

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

Summary

mktexlsr revision 22855 through revision 36625 as packaged in texlive allows local users to write to arbitrary files via a symlink attack.

Patch / fix

  • texlive-bin Debian 14, Debian 13, Debian 12 2014.20140926.35254-5

debian advisories DEBIAN-CVE-2015-5700

  • texlive-bin Ubuntu 14.04 LTS 2013.20130729.30972-2ubuntu0.1

ubuntu advisories UBUNTU-CVE-2015-5700

Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

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-5700 updated cvss 2.1

texlive: insecure use of /tmp in mktexlsr

  • Red Hat Enterprise Linux 7 texlive, texlive-ae, texlive-cm, texlive-ec, texlive-fp, texlive-lm, +304 more
    affected: no fix planned “Will not fix”
  • Red Hat Enterprise Linux 6 mendexk, texlive, kpathsea, texlive-afm, texlive-dvips, texlive-latex, +5 more
    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

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

CVSS scores

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

Classification

Weakness
  • CWE-59 Improper Link Resolution Before File Access

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.