Bug 2154891 - CVE-2021-33640 libtar: fixes for CVE-2021-33645 and CVE-2021-33646 introduced new use-after-free bugs in libtar [fedora-all]
Summary: CVE-2021-33640 libtar: fixes for CVE-2021-33645 and CVE-2021-33646 introduced...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: libtar
Version: 37
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
Assignee: Kamil Dudka
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: CVE-2021-33640
TreeView+ depends on / blocked
 
Reported: 2022-12-19 14:30 UTC by Zack Miele
Modified: 2022-12-28 01:39 UTC (History)
3 users (show)

Fixed In Version: libtar-1.2.20-26.fc38 libtar-1.2.20-26.fc37 libtar-1.2.20-26.fc36
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-12-28 01:34:40 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Zack Miele 2022-12-19 14:30:14 UTC
More information about this security flaw is available in the following bug:

http://bugzilla.redhat.com/show_bug.cgi?id=2143012

Disclaimer: Community trackers are created by Red Hat Product Security team on a best effort basis. Package maintainers are required to ascertain if the flaw indeed affects their package, before starting the update process.

Comment 1 Zack Miele 2022-12-19 14:30:16 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=2143012,2154891

# 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 3 Fedora Update System 2022-12-19 16:01:24 UTC
FEDORA-2022-88772d0a2d has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2022-88772d0a2d

Comment 4 Fedora Update System 2022-12-19 16:01:36 UTC
FEDORA-2022-ccc68b06cc has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-ccc68b06cc

Comment 5 Fedora Update System 2022-12-20 01:28:57 UTC
FEDORA-2022-88772d0a2d has been pushed to the Fedora 37 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2022-88772d0a2d`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-88772d0a2d

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

Comment 6 Fedora Update System 2022-12-20 01:45:05 UTC
FEDORA-2022-ccc68b06cc has been pushed to the Fedora 36 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2022-ccc68b06cc`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-ccc68b06cc

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

Comment 7 Fedora Update System 2022-12-28 01:34:40 UTC
FEDORA-2022-88772d0a2d has been pushed to the Fedora 37 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 8 Fedora Update System 2022-12-28 01:39:54 UTC
FEDORA-2022-ccc68b06cc has been pushed to the Fedora 36 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.