Bug 2222680 (CVE-2023-29449) - CVE-2023-29449 zabbix: JavaScript can cause uncontrolled CPU, memory, and disk I/O utilization
Summary: CVE-2023-29449 zabbix: JavaScript can cause uncontrolled CPU, memory, and dis...
Keywords:
Status: CLOSED UPSTREAM
Alias: CVE-2023-29449
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Nobody
QA Contact:
URL:
Whiteboard:
Depends On: 2222681 2222682
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-07-13 12:50 UTC by Mauro Matteo Cascella
Modified: 2023-07-16 20:53 UTC (History)
1 user (show)

Fixed In Version: zabbix 5.0.32rc1, zabbix 6.0.14rc1, zabbix 6.2.8rc1, zabbix 6.4.0rc1, zabbix 7.0.0alpha1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-07-13 17:41:23 UTC
Embargoed:


Attachments (Terms of Use)

Description Mauro Matteo Cascella 2023-07-13 12:50:03 UTC
JavaScript preprocessing, webhooks and global scripts can cause uncontrolled CPU, memory, and disk I/O utilization. Preprocessing/webhook/global script configuration and testing are only available to Administrative roles (Admin and Superadmin). Administrative privileges should be typically granted to users who need to perform tasks that require more control over the system. The security risk is limited because not all users have this level of access.

Reference:
https://support.zabbix.com/browse/ZBX-22589

Comment 1 Mauro Matteo Cascella 2023-07-13 12:50:19 UTC
Created zabbix tracking bugs for this issue:

Affects: epel-all [bug 2222681]
Affects: fedora-all [bug 2222682]

Comment 2 Product Security DevOps Team 2023-07-13 17:41:22 UTC
This CVE Bugzilla entry is for community support informational purposes only as it does not affect a package in a commercially supported Red Hat product. Refer to the dependent bugs for status of those individual community products.

Comment 3 Orion Poplawski 2023-07-16 20:53:28 UTC
Fix Version/s:
5.0.32rc1, 6.0.14rc1


Note You need to log in before you can comment on or make changes to this bug.