Bug 2069369 - CVE-2022-24778 golang-github-containerd-imgcrypt: imgcrypt: Unauthorized access to encryted container image on a shared system due to missing check in CheckAuthorization() code path [fedora-all]
Summary: CVE-2022-24778 golang-github-containerd-imgcrypt: imgcrypt: Unauthorized acce...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: golang-github-containerd-imgcrypt
Version: 35
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
Assignee: Robert-André Mauchin 🐧
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: CVE-2022-24778
TreeView+ depends on / blocked
 
Reported: 2022-03-28 19:23 UTC by Pedro Sampaio
Modified: 2022-05-07 04:15 UTC (History)
2 users (show)

Fixed In Version: golang-github-containerd-imgcrypt-1.1.4-1.fc37 golang-github-containerd-imgcrypt-1.1.4-1.fc35 golang-github-containerd-imgcrypt-1.1.4-1.fc34 golang-github-containerd-imgcrypt-1.1.4-1.fc36
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-04-03 03:17:26 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Pedro Sampaio 2022-03-28 19:23:32 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 Pedro Sampaio 2022-03-28 19:23:35 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=high

# testing, stable
request=testing

# Bug numbers: 1234,9876
bugs=2069368,2069369

# 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 Fedora Update System 2022-04-03 03:14:57 UTC
FEDORA-2022-cfe50b5ebb has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2022-cfe50b5ebb

Comment 3 Fedora Update System 2022-04-03 03:17:26 UTC
FEDORA-2022-cfe50b5ebb has been pushed to the Fedora 37 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 4 Fedora Update System 2022-04-03 04:43:08 UTC
FEDORA-2022-d86c15bfb7 has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-d86c15bfb7

Comment 5 Fedora Update System 2022-04-03 04:43:08 UTC
FEDORA-2022-5f746c8e5b has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2022-5f746c8e5b

Comment 6 Fedora Update System 2022-04-03 04:43:09 UTC
FEDORA-2022-de0f8beeb0 has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2022-de0f8beeb0

Comment 7 Fedora Update System 2022-04-04 01:47:26 UTC
FEDORA-2022-de0f8beeb0 has been pushed to the Fedora 34 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-de0f8beeb0`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-de0f8beeb0

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

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

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

Comment 9 Fedora Update System 2022-04-04 02:09:56 UTC
FEDORA-2022-d86c15bfb7 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 --advisory=FEDORA-2022-d86c15bfb7`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-d86c15bfb7

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

Comment 10 Fedora Update System 2022-04-11 17:17:11 UTC
FEDORA-2022-5f746c8e5b has been pushed to the Fedora 35 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 11 Fedora Update System 2022-04-11 17:40:55 UTC
FEDORA-2022-de0f8beeb0 has been pushed to the Fedora 34 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 12 Fedora Update System 2022-05-07 04:15:37 UTC
FEDORA-2022-d86c15bfb7 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.