Bug 1913745 - CVE-2021-20197 mingw-binutils: binutils: race window allows users to own arbitrary files [fedora-all]
Summary: CVE-2021-20197 mingw-binutils: binutils: race window allows users to own arbi...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: mingw-binutils
Version: 33
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
Assignee: Richard W.M. Jones
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: CVE-2021-20197
TreeView+ depends on / blocked
 
Reported: 2021-01-07 13:57 UTC by Marian Rehak
Modified: 2021-02-06 01:16 UTC (History)
9 users (show)

Fixed In Version: mingw-binutils-2.34-7.fc34 mingw-binutils-2.34-7.fc33
Clone Of:
Environment:
Last Closed: 2021-02-06 01:16:44 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Marian Rehak 2021-01-07 13:57:26 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-all.

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:
http://fedoraproject.org/wiki/Security/TrackingBugs

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.

Comment 1 Marian Rehak 2021-01-07 13:57:30 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)
type=security

# low, medium, high, urgent (required)
severity=medium

# testing, stable
request=testing

# Bug numbers: 1234,9876
bugs=1913743,1913745

# Description of your update
notes=Security fix for [PUT CVEs HERE]

# Enable request automation based on the stable/unstable karma thresholds
autokarma=True
stable_karma=3
unstable_karma=-3

# Automatically close bugs when this marked as stable
close_bugs=True

# Suggest that users restart after update
suggest_reboot=False

======

Additionally, you may opt to use the bodhi web interface to submit updates:

https://bodhi.fedoraproject.org/updates/new

Comment 2 Nick Clifton 2021-01-28 10:17:44 UTC
Given that this package is only used internally in order to help build other packages, and that the circumstances for making use of the vulnerability are so difficult to achieve, I am going to close this BZ.

Comment 3 Richard W.M. Jones 2021-01-28 18:44:32 UTC
Reopening and taking this bug since we want to have the fix in RHEL 9 too.

Comment 4 Fedora Update System 2021-01-28 19:40:50 UTC
FEDORA-2021-354441fcdd has been submitted as an update to Fedora 33. https://bodhi.fedoraproject.org/updates/FEDORA-2021-354441fcdd

Comment 5 Fedora Update System 2021-01-29 02:02:03 UTC
FEDORA-2021-354441fcdd has been pushed to the Fedora 33 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-354441fcdd`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-354441fcdd

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 6 Fedora Update System 2021-02-06 01:16:44 UTC
FEDORA-2021-354441fcdd has been pushed to the Fedora 33 stable repository.
If problem still persists, 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.