Bug 2356856 - CVE-2024-36469 zabbix6.0: User enumeration via timing attack in Zabbix web interface [epel-8]
Summary: CVE-2024-36469 zabbix6.0: User enumeration via timing attack in Zabbix web in...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: zabbix6.0
Version: epel8
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: ---
Assignee: Orion Poplawski
QA Contact:
URL:
Whiteboard: {"flaws": ["ca75e8a8-1758-4d35-87b5-0...
Depends On:
Blocks: CVE-2024-36469
TreeView+ depends on / blocked
 
Reported: 2025-04-02 09:04 UTC by Michal Findra
Modified: 2025-04-11 00:36 UTC (History)
1 user (show)

Fixed In Version: zabbix6.0-6.0.39-1.el8
Clone Of:
Environment:
Last Closed: 2025-04-11 00:36:01 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)

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

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

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-02 23:24:52 UTC 
FEDORA-EPEL-2025-77875be662 (zabbix6.0-6.0.39-1.el8) has been submitted as an update to Fedora EPEL 8.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-77875be662
Comment 2 Fedora Update System 2025-04-03 02:31:24 UTC 
FEDORA-EPEL-2025-77875be662 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-77875be662

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Comment 3 Fedora Update System 2025-04-11 00:36:01 UTC 
FEDORA-EPEL-2025-77875be662 (zabbix6.0-6.0.39-1.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.