Bug 2356866 - CVE-2024-42325 zabbix: Excessive information returned by user.get [epel-9]
Summary: CVE-2024-42325 zabbix: Excessive information returned by user.get [epel-9]
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: zabbix
Version: epel9
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: ---
Assignee: Gwyn Ciesla
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: {"flaws": ["e2ea520f-fc6b-4367-95a2-9...
Depends On:
Blocks: CVE-2024-42325
TreeView+ depends on / blocked
 
Reported: 2025-04-02 09:11 UTC by Michal Findra
Modified: 2025-04-17 19:43 UTC (History)
4 users (show)

Fixed In Version: zabbix-6.0.39-1.el9
Clone Of:
Environment:
Last Closed: 2025-04-17 19:43:15 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Michal Findra 2025-04-02 09:11:07 UTC
More information about this security flaw is available in the following bug:

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

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-04-09 15:36:17 UTC
FEDORA-EPEL-2025-c997801cc7 (zabbix-6.0.39-1.el9) has been submitted as an update to Fedora EPEL 9.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-c997801cc7

Comment 2 Fedora Update System 2025-04-10 00:22:28 UTC
FEDORA-EPEL-2025-c997801cc7 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-2025-c997801cc7

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

Comment 3 Fedora Update System 2025-04-17 19:43:15 UTC
FEDORA-EPEL-2025-c997801cc7 (zabbix-6.0.39-1.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.