Bug 2317786 - CVE-2024-48949 yarnpkg: Missing Validation in Elliptic's EDDSA Signature Verification [epel-8]
Summary: CVE-2024-48949 yarnpkg: Missing Validation in Elliptic's EDDSA Signature Veri...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: yarnpkg
Version: epel8
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
Assignee: Zuzana Svetlikova
QA Contact:
URL:
Whiteboard: {"flaws": ["680bdd30-e62e-4b68-a0e4-6...
Depends On:
Blocks: CVE-2024-48949
TreeView+ depends on / blocked
 
Reported: 2024-10-10 10:29 UTC by Michal Findra
Modified: 2025-04-06 01:12 UTC (History)
4 users (show)

Fixed In Version: yarnpkg-1.22.22-7.el8
Clone Of:
Environment:
Last Closed: 2025-04-06 01:12:13 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)

Description Michal Findra 2024-10-10 10:29:54 UTC 
More information about this security flaw is available in the following bug:

https://bugzilla.redhat.com/show_bug.cgi?id=2317724

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 Fedora Update System 2025-03-28 22:04:03 UTC 
FEDORA-EPEL-2025-7f793012aa (yarnpkg-1.22.22-7.el8) has been submitted as an update to Fedora EPEL 8.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-7f793012aa
Comment 2 Fedora Update System 2025-03-29 02:31:22 UTC 
FEDORA-EPEL-2025-7f793012aa has been pushed to the Fedora EPEL 8 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-7f793012aa

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Comment 3 Fedora Update System 2025-04-06 01:12:13 UTC 
FEDORA-EPEL-2025-7f793012aa (yarnpkg-1.22.22-7.el8) has been pushed to the Fedora EPEL 8 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.