CVE-2024-36464 | Media Types: Office365, SMTP passwords are unencrypted and visible in plaintext when exported

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.

Published: 2024-11-27 Last update: 2025-11-03 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2024-36464 is rated Low Risk (18.1/100): CVSS Low severity, with low exploitation likelihood (EPSS 0.07%). Low composite risk—no urgent action required; patch on your normal maintenance cycle and revisit priority if CVSS or EPSS increases.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2024-36464

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-04-18 0.04% 0.07% +0.03%
2 2026-01-27 0.06% 0.04% -0.01%
3 2026-01-24 — 0.06% —

Full EPSS history (8 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2024-36464

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
2.7 3.1 LOW
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:H)
They need powerful rights—admin, root, or similar—before this pays off.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:L)
Some sensitive info could get out, but not a total data dump.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:N)
Service keeps running; no real outage angle.
 1.2 1.4 [email protected]

Weakness enumeration for CVE-2024-36464

OS Trackers for CVE-2024-36464

vendor priority summary link
debian not yet assigned CVE-2024-36464 not yet assigned priority: Debian including 1 source packages (zabbix), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 4, open 1. https://security-tracker.debian.org/tracker/CVE-2024-36464
suse medium CVE-2024-36464 severity moderate: SUSE including 2 source package names (zabbix, zabbix-agent), 7 product×package rows across 5 product lines (SUSE Linux Enterprise Server 12 SP4-LTSS, SUSE Linux Enterprise Server 12 SP5-LTSS, … (5 product lines)): Known Not Affected 7. https://www.suse.com/security/cve/CVE-2024-36464/
ubuntu medium CVE-2024-36464 medium priority: Ubuntu including 1 source packages (zabbix), 10 status rows across 10 suites (bionic, focal, jammy, noble, oracular, plucky, questing, trusty, upstream, xenial): needs-triage 7, ignored 2, DNE 1. https://ubuntu.com/security/CVE-2024-36464

Affected software / configurations for CVE-2024-36464

Vendor Product Version Raw CPE
zabbix zabbix >= 6.0.0, < 6.0.30 cpe:2.3:a:zabbix:zabbix:*:*:*:*:*:*:*:*
zabbix zabbix >= 6.4.0, < 6.4.15 cpe:2.3:a:zabbix:zabbix:*:*:*:*:*:*:*:*

References for CVE-2024-36464

cvelogic Threat Intelligence