Bug 2044430 - CVE-2021-45720 389-ds-base: bundled lru: Use after free in lru crate [fedora-all]
Summary: CVE-2021-45720 389-ds-base: bundled lru: Use after free in lru crate [fedora-...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: 389-ds-base
Version: 35
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
Assignee: mreynolds
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: CVE-2021-45720
TreeView+ depends on / blocked
 
Reported: 2022-01-24 15:29 UTC by Pedro Sampaio
Modified: 2022-03-11 13:14 UTC (History)
9 users (show)

Fixed In Version: 389-ds-base-2.0.14-1.fc35
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-02-04 01:22:31 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Pedro Sampaio 2022-01-24 15:29:18 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-01-24 15:29:20 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=2044429,2044430

# 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 Fabio Valentini 2022-01-24 16:12:32 UTC
The "lru" crate is not packaged for Fedora.
However, a vulnerable version (0.6.6) is bundled in 389-ds-base.

Comment 3 mreynolds 2022-01-24 16:22:44 UTC
Tests how we can upgrade lru to a newer version:

lru v0.6.6 -> v0.7.2

Will work on new builds shortly...

Comment 4 mreynolds 2022-01-24 19:44:29 UTC
Fixed upstream via: https://github.com/389ds/389-ds-base/issues/5132

Comment 5 Fedora Update System 2022-01-24 19:52:00 UTC
FEDORA-2022-7f62add497 has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2022-7f62add497

Comment 6 Fedora Update System 2022-01-25 02:10:46 UTC
FEDORA-2022-7f62add497 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-7f62add497`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-7f62add497

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

Comment 7 Fedora Update System 2022-02-04 01:22:31 UTC
FEDORA-2022-5aee32fbab has been pushed to the Fedora 35 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.