Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 2073312
| Summary: | CVE-2022-1271 gzip: arbitrary-file-write vulnerability [fedora-all] | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Vipul Nair <vinair> |
| Component: | gzip | Assignee: | Jakub Martisko <jamartis> |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 35 | CC: | awilliam, jamartis, kdudka, kparal, michel, pstodulk, rjones |
| Target Milestone: | --- | Keywords: | Security, SecurityTracking |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | AcceptedFreezeException | ||
| Fixed In Version: | Doc Type: | No Doc Update | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2022-05-02 12:06:04 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 1953786, 2073310 | ||
|
Description
Vipul Nair
2022-04-08 08:05:54 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=2073310,2073312 # 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 Looks like this is built for Rawhide, any chance F36, F35, and F34 can be upgraded too? https://bodhi.fedoraproject.org/updates/?packages=gzip Updates for f34-f36, unlike in rawhide where an update to gzip 1.12 has been made, the updates below are gzip 1.10/1.11 with the related patches. Testing would be thus appreciated. f34: https://bodhi.fedoraproject.org/updates/FEDORA-2022-6b512ae9e5 f35: https://bodhi.fedoraproject.org/updates/FEDORA-2022-6746dde2a0 f36: https://bodhi.fedoraproject.org/updates/FEDORA-2022-eeb6c686c7 Do we have a separate bug for xz? Anyway for xz (not gzip): Rawhide: https://koji.fedoraproject.org/koji/taskinfo?taskID=85814448 F36: https://bodhi.fedoraproject.org/updates/FEDORA-2022-07cd35f6b8 F35: https://bodhi.fedoraproject.org/updates/FEDORA-2022-c69e286f8d F34: https://bodhi.fedoraproject.org/updates/FEDORA-2022-ec66ee6b59 Requesting an F36 freeze exception for a CVE fix. The update is in comment 3. Not sure if the update from comment 4 is related as well. +4 in https://pagure.io/fedora-qa/blocker-review/issue/777 , marking accepted FE. @kparal Hi, I am a bit confused right now, the bodhi update seems to have enough karma and is currently in testing -> stable. Is there anything else I am supposed to do now (regarding the gzip/f36)? https://bodhi.fedoraproject.org/updates/FEDORA-2022-eeb6c686c7 No, there's nothing you need to do. It wasn't pushed yet because we had a Final RC that had not been rejected; by policy, the builds that go in the final frozen repos should be exactly the same set of builds used to build the RC we ship as Final, so they're consistent. So as long as an RC is "live" we cannot push anything stable that wasn't in that RC. As of this morning, though, that RC is not going to be shipped, so we can push freeze exceptions like this stable, and they will be included in the next RC. I'll do a stable push request shortly. Aha! Thank you for the info. Oh, there was one other thing to do - mark the update as fixing this bug. The blockerbugs app requires that, or else it won't show the update in the auto-generated push request. I can do it, though. FEDORA-2022-eeb6c686c7 has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-eeb6c686c7 FEDORA-2022-eeb6c686c7 has been pushed to the Fedora 36 stable repository. If problem still persists, please make note of it in this bug report. I believe this can now be closed. I filed bug 2080938 for xz case. |