Skip to content

Previous versions of ldapmavis-mt mishandle zero-length user passwords for LDAP user authentication.

High
MarcJHuber published GHSA-3wm8-6774-6grx Mar 2, 2025

Package

ldapmavis-mt

Affected versions

pre 20250302

Patched versions

post 20250302

Description

Previous versions of ldapmavis-mt mishandle zero-length user passwords for LDAP user authentication.

While some recent LDAP server implementations simply deny these requests, older servers may consider them as anonymous binds. If your setup uses ldapmavis-mt and your LDAP server permits anonymous binds with a DN set you might be at risk.

This issue affects ldapmavis-mt only. The script LDAP backends are safe.

There are several ways to remedy this issue:

Recommended: Upgrade to the current GIT, it comes with fixed code

Workaround A: Add a minimalistic script to reject zero-length passwords:

    mavis module = external-mt {
            script in {
                    if (defined $PASSWORD && $PASSWORD =~ /^$/) { set $RESULT = "NAK" return }
                    if (defined $PASSWDNEW && $PASSWDNEW =~ /^$/) { set $RESULT = "NAK" return }
            }
            # ...
            exec = /usr/local/sbin/ldapmavis-mt
    }

Workaround B: Switch to one of the script-based backends (mavis_tacplus-ng_ldap.pl/mavis_tacplus_ldap.pl/mavis_tacplus_ldap.py)

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

CVE ID

No known CVE

Weaknesses

No CWEs

Credits