Skip to content
Fencer Intel
high 8.8

CVE-2017-17513 json

TeX Live through 20170524 does not validate strings before launching the program specified by the BROWSER environment variable, which might…

published 2017-12-14 8 y ago modified 2026-06-17 4 mo ago also EUVD-2017-8674

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

Summary

TeX Live through 20170524 does not validate strings before launching the program specified by the BROWSER environment variable, which might allow remote attackers to conduct argument-injection attacks via a crafted URL, related to linked_scripts/context/stubs/unix/mtxrun, texmf-dist/scripts/context/stubs/mswin/mtxrun.lua, and texmf-dist/tex/luatex/lualibs/lualibs-os.lua.

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-2017-17513 updated cvss 5.3

texlive: Command injection in mswin/mtxrun.lua and lualibs/lualibs-os.lua

  • Red Hat Enterprise Linux 9 texlive, texlive-ae, texlive-cm, texlive-ec, texlive-fp, texlive-lm, +363 more
    affected: no fix available
  • Red Hat Enterprise Linux 6 mendexk, texlive, kpathsea, texlive-afm, texlive-dvips, texlive-latex, +5 more Red Hat Enterprise Linux 7 texlive, texlive-ae, texlive-cm, texlive-ec, texlive-fp, texlive-lm, +304 more Red Hat Enterprise Linux 8 texlive, texlive-ae, texlive-cm, texlive-ec, texlive-fp, texlive-lm, +311 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

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

CVSS scores

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

Classification

Weakness
  • CWE-74 Improper Neutralization of Special Elements in Output Used by a Downstream Component

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.