Bug 2135164

Summary: CVE-2022-21699 ipython: arbitrary code execution by cross user temporary files mismanagment [epel-7]
Product: [Fedora] Fedora EPEL Reporter: Maxwell G <maxwell>
Component: ipythonAssignee: Carl George 🤠 <carl>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: epel7CC: carl, dcantrell, epel-packagers-sig, extras-qa, lbalhar, maxwell, mhroncok, michel, mrehak, mrunge, orion, python-packagers-sig, python-sig, tomspur
Target Milestone: ---Keywords: Security, SecurityTracking
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: ipython-3.2.3-1.el7 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 2047815 Environment:
Last Closed: 2023-01-29 00:47:54 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On:    
Bug Blocks: 2047813    

Description Maxwell G 2022-10-16 22:27:42 UTC
+++ This bug was initially created as a clone of Bug #2047815 +++

This is an automatically created tracking bug!  It was created to ensure
that one or more security vulnerabilities are fixed in affected versions
of epel-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:

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 EPEL. 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.

--- Additional comment from Marian Rehak on 2022-01-28 09:44:41 CST ---

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)

# low, medium, high, urgent (required)

# testing, stable

# Bug numbers: 1234,9876

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

# 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 web interface to submit updates:


--- Additional comment from Maxwell G on 2022-10-16 17:26:12 CDT ---

I've submitted a PR to mitigate this in EPEL 8: https://src.fedoraproject.org/rpms/ipython/pull-request/45.

I'm creating a separate bug for EPEL 7 so that can be tracked separately. There is no upstream fix for the 3.x branch which is packaged there, so someone will need to backport the change or go through the EPEL incompatible updates policy. This is a high severity CVE that has gone unpatched in EPEL for 10 months, so it should be made a priority.

Comment 2 Fedora Update System 2023-01-19 17:45:14 UTC
FEDORA-EPEL-2023-afd7021128 has been submitted as an update to Fedora EPEL 7. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-afd7021128

Comment 3 Fedora Update System 2023-01-21 03:41:17 UTC
FEDORA-EPEL-2023-afd7021128 has been pushed to the Fedora EPEL 7 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2023-afd7021128

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

Comment 4 Fedora Update System 2023-01-29 00:47:54 UTC
FEDORA-EPEL-2023-afd7021128 has been pushed to the Fedora EPEL 7 stable repository.
If problem still persists, please make note of it in this bug report.