Zabbix up to 6.0.40/7.0.17/7.2.11/7.4.1 LDAP Bind password insufficiently protected credentials

Summaryinfo

A vulnerability was found in Zabbix up to 6.0.40/7.0.17/7.2.11/7.4.1. It has been rated as problematic. The affected element is an unknown function of the component LDAP Handler. This manipulation of the argument Bind password causes insufficiently protected credentials. This vulnerability appears as CVE-2025-27231. The attack may be initiated remotely. There is no available exploit.

Detailsinfo

A vulnerability has been found in Zabbix up to 6.0.40/7.0.17/7.2.11/7.4.1 and classified as problematic. Affected by this vulnerability is an unknown function of the component LDAP Handler. The manipulation of the argument Bind password with an unknown input leads to a insufficiently protected credentials vulnerability. The CWE definition for the vulnerability is CWE-522. The product transmits or stores authentication credentials, but it uses an insecure method that is susceptible to unauthorized interception and/or retrieval. As an impact it is known to affect confidentiality. The summary by CVE is:

The LDAP 'Bind password' value cannot be read after saving, but a Super Admin account can leak it by changing LDAP 'Host' to a rogue LDAP server. To mitigate this, the 'Bind password' value is now reset on 'Host' change.

The advisory is shared at support.zabbix.com. This vulnerability is known as CVE-2025-27231 since 02/20/2025. The exploitation appears to be easy. The attack can be launched remotely. Additional levels of successful authentication are necessary for exploitation. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1552 for this issue.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

The vulnerability is also documented in the vulnerability database at CERT Bund (WID-SEC-2025-2207). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Affected

• Zabbix Zabbix

Productinfo

Type

• Network Management Software

Name

• Zabbix

Version

• 6.0.0
• 6.0.1
• 6.0.2
• 6.0.3
• 6.0.4
• 6.0.5
• 6.0.6
• 6.0.7
• 6.0.8
• 6.0.9
• 6.0.10
• 6.0.11
• 6.0.12
• 6.0.13
• 6.0.14
• 6.0.15
• 6.0.16
• 6.0.17
• 6.0.18
• 6.0.19
• 6.0.20
• 6.0.21
• 6.0.22
• 6.0.23
• 6.0.24
• 6.0.25
• 6.0.26
• 6.0.27
• 6.0.28
• 6.0.29
• 6.0.30
• 6.0.31
• 6.0.32
• 6.0.33
• 6.0.34
• 6.0.35
• 6.0.36
• 6.0.37
• 6.0.38
• 6.0.39
• 6.0.40
• 7.0.0
• 7.0.1
• 7.0.2
• 7.0.3
• 7.0.4
• 7.0.5
• 7.0.6
• 7.0.7
• 7.0.8
• 7.0.9
• 7.0.10
• 7.0.11
• 7.0.12
• 7.0.13
• 7.0.14
• 7.0.15
• 7.0.16
• 7.0.17
• 7.2.0
• 7.2.1
• 7.2.2
• 7.2.3
• 7.2.4
• 7.2.5
• 7.2.6
• 7.2.7
• 7.2.8
• 7.2.9
• 7.2.10
• 7.2.11
• 7.4.0
• 7.4.1

License

• open-source

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion