Bug 2331625 - CVE-2024-46657 mupdf: segmentation fault via tools/pdfextract.c [epel-9]
Summary: CVE-2024-46657 mupdf: segmentation fault via tools/pdfextract.c [epel-9]
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: mupdf
Version: epel9
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
Assignee: Michael J Gruber
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: {"flaws": ["2041ba29-c303-4780-96cc-c...
Depends On:
Blocks: CVE-2024-46657
TreeView+ depends on / blocked
 
Reported: 2024-12-11 01:29 UTC by Robb Gatica
Modified: 2025-01-03 02:00 UTC (History)
2 users (show)

Fixed In Version: mupdf-1.21.1-6.el9
Clone Of:
Environment:
Last Closed: 2025-01-03 02:00:36 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Robb Gatica 2024-12-11 01:29:29 UTC
More information about this security flaw is available in the following bug:

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

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 2024-12-26 17:33:05 UTC
FEDORA-EPEL-2024-94a20f339a (mupdf-1.21.1-6.el9) has been submitted as an update to Fedora EPEL 9.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-94a20f339a

Comment 2 Fedora Update System 2024-12-27 01:31:38 UTC
FEDORA-EPEL-2024-94a20f339a has been pushed to the Fedora EPEL 9 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-94a20f339a

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

Comment 3 Fedora Update System 2025-01-03 02:00:36 UTC
FEDORA-EPEL-2024-94a20f339a (mupdf-1.21.1-6.el9) has been pushed to the Fedora EPEL 9 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.