Bug 1181169 - texlive: insecure use of /tmp in mktexlsr [fedora-all]
Summary: texlive: insecure use of /tmp in mktexlsr [fedora-all]
Alias: None
Product: Fedora
Classification: Fedora
Component: texlive
Version: 21
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Ngo Than
QA Contact: Fedora Extras Quality Assurance
Depends On:
Blocks: CVE-2015-5700, CVE-2015-5701
TreeView+ depends on / blocked
Reported: 2015-01-12 14:12 UTC by Vasyl Kaigorodov
Modified: 2015-05-12 20:38 UTC (History)
3 users (show)

Fixed In Version: texlive-2014-7.1.20140525_r34255.fc21
Doc Type: Release Note
Doc Text:
Clone Of:
Last Closed: 2015-05-10 23:38:01 UTC

Attachments (Terms of Use)

Description Vasyl Kaigorodov 2015-01-12 14:12:57 UTC
This is an automatically created tracking bug!  It was created to ensure
that one or more security vulnerabilities are fixed in affected versions
of Fedora.

For comments that are specific to the vulnerability please use bugs filed
against the "Security Response" product referenced in the "Blocks" field.

For more information see:

When submitting as an update, use the fedpkg template provided in the next
comment(s).  This will include the bug IDs of this tracking bug as well as
the relevant top-level CVE bugs.

Please also mention the CVE IDs being fixed in the RPM changelog and the
fedpkg commit message.

NOTE: this issue affects multiple supported versions of Fedora. While only
one tracking bug has been filed, please correct all affected versions at
the same time.  If you need to fix the versions independent of each other,
you may clone this bug as appropriate.

[bug automatically created by: add-tracking-bugs]

Comment 1 Vasyl Kaigorodov 2015-01-12 14:13:01 UTC
Use the following template to for the 'fedpkg update' request to submit an
update for this issue as it contains the top-level parent bug(s) as well as
this tracking bug.  This will ensure that all associated bugs get updated
when new packages are pushed to stable.


# bugfix, security, enhancement, newpackage (required)

# testing, stable

# Bug numbers: 1234,9876

# Description of your update
notes=Security fix for 

# Enable request automation based on the stable/unstable karma thresholds

# Automatically close bugs when this marked as stable

# Suggest that users restart after update


Additionally, you may opt to use the bodhi update submission link instead:


Comment 2 Ngo Than 2015-04-23 13:28:18 UTC
Vasyl, do we have CVE for this?

Comment 3 Vasyl Kaigorodov 2015-04-23 15:20:40 UTC
(In reply to Ngo Than from comment #2)
> Vasyl, do we have CVE for this?

No, we don't yet have a CVE ID for that.
I have requested one on oss-security mailing list (Subject: CVE Request: texlive: insecure use of /tmp in mktexlsr) and will update the 1181167 bug metadata as soon as it will be assigned.

Comment 4 Ngo Than 2015-04-29 16:09:21 UTC
it's fixed in rawhide, f22. i'm building it for f21 nd will push it  to bohdi today

Comment 5 Fedora Update System 2015-04-30 15:33:48 UTC
texlive-2014-7.1.20140525_r34255.fc21 has been submitted as an update for Fedora 21.

Comment 6 Fedora Update System 2015-05-01 16:39:11 UTC
Package texlive-2014-7.1.20140525_r34255.fc21:
* should fix your issue,
* was pushed to the Fedora 21 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing texlive-2014-7.1.20140525_r34255.fc21'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).

Comment 7 Fedora Update System 2015-05-04 11:47:45 UTC
texlive-2014-8.20140525_r34255.fc22 has been submitted as an update for Fedora 22.

Comment 8 Fedora Update System 2015-05-10 23:38:01 UTC
texlive-2014-8.20140525_r34255.fc22 has been pushed to the Fedora 22 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 9 Fedora Update System 2015-05-12 20:38:00 UTC
texlive-2014-7.1.20140525_r34255.fc21 has been pushed to the Fedora 21 stable repository.  If problems still persist, please make note of it in this bug report.

Note You need to log in before you can comment on or make changes to this bug.