Skip to content
Fencer Intel
low 2.7

CVE-2024-36464 json

Media Types: Office365, SMTP passwords are unencrypted and visible in plaintext when exported

published last yr. modified 4mo ago also EUVD-2024-36347

cvss
2.7
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.6%
EPSS 0.6% chance of exploitation in 30 days, percentile 46%
public exploits
0
none known

Summary

When exporting media types, the password is exported in the YAML in plain text. This appears to be a best practices type issue and may have no actual impact. The user would need to have permissions to access the media types and therefore would be expected to have access to these passwords.

Patch / fix

  • zabbix frontend 6.0.30rc1, 6.4.15rc1, 7.0.1rc1
  • zabbix zabbix 6.0.30rc1, 6.4.15rc1, 7.0.1rc1
  • zabbix zabbix_server 6.0.30rc1, 6.4.15rc1, 7.0.1rc1
  • zabbix Debian 14, Debian 13 1:7.0.9+dfsg-1

debian advisories DEBIAN-CVE-2024-36464

Is CVE-2024-36464 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
last yr.

Exploit prediction

0.56% chance of exploitation in the next 30 days, higher than 46% of all scored CVEs (FIRST EPSS, 2026-11-11).

CVSS scores

assigned by version score vector
CNA 3.1 2.7 CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:N

Affected products

  • Zabbix Zabbix

Classification

Weakness
  • CWE-256 Plaintext Storage of a Password

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.