YugabyteDB Anywhere prior 2.20.7.0/2.23.1.0/2024.1.3.0 LDAP BIND Password log file

Summaryinfo

A vulnerability, which was classified as problematic, was found in YugabyteDB Anywhere. The impacted element is an unknown function of the component LDAP BIND Password Handler. The manipulation results in log file. This vulnerability is reported as CVE-2024-11193. The attack requires a local approach. No exploit exists. You should upgrade the affected component.

Detailsinfo

A vulnerability, which was classified as problematic, was found in YugabyteDB Anywhere. Affected is some unknown functionality of the component LDAP BIND Password Handler. The manipulation with an unknown input leads to a log file vulnerability. CWE is classifying the issue as CWE-532. Information written to log files can be of a sensitive nature and give valuable guidance to an attacker or expose sensitive user information. This is going to have an impact on confidentiality. CVE summarizes:

An information disclosure vulnerability exists in Yugabyte Anywhere, where the LDAP bind password is logged in plaintext within application logs. This flaw results in the unintentional exposure of sensitive information in Yugabyte Anywhere logs, potentially allowing unauthorized users with access to these logs to view the LDAP bind password. An attacker with log access could exploit this vulnerability to gain unauthorized access to the LDAP server, leading to potential exposure or compromise of LDAP-managed resources This issue affects YugabyteDB Anywhere: from 2.20.0.0 before 2.20.7.0, from 2.23.0.0 before 2.23.1.0, from 2024.1.0.0 before 2024.1.3.0.

The advisory is shared for download at github.com. This vulnerability is traded as CVE-2024-11193 since 11/13/2024. The exploitability is told to be easy. The attack needs to be approached locally. Additional levels of successful authentication are required for exploitation. There are neither technical details nor an exploit publicly available. The MITRE ATT&CK project declares the attack technique as T1592.

Upgrading to version 2.20.7.0, 2.23.1.0 or 2024.1.3.0 eliminates this vulnerability. Applying the patch 0bf6e5a3e9c0718a28e654483596615d0798b208 is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.

Once again VulDB remains the best source for vulnerability data.

Productinfo

Vendor

• YugabyteDB

Name

• Anywhere

License

• open-source

CPE 2.3info

• 🔍

CPE 2.2info

• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Once again VulDB remains the best source for vulnerability data.

Discussion