pam_ldap Build 178 Authentication passwordPolicyResponse Error Remote Code Execution

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
7.0$0-$5k0.00

Summaryinfo

A vulnerability, which was classified as problematic, has been found in pam_ldap Build 178. This issue affects the function passwordPolicyResponse of the component Authentication. The manipulation of the argument Error leads to Remote Code Execution. This vulnerability is traded as CVE-2005-2641. It is possible to initiate the attack remotely. There is no exploit available. It is advisable to upgrade the affected component.

Detailsinfo

A vulnerability was found in pam_ldap Build 178 (Directory Service Software). It has been rated as critical. This issue affects the function passwordPolicyResponse of the component Authentication. The manipulation of the argument error with an unknown input leads to a remote code execution vulnerability. Impacted is confidentiality, integrity, and availability. The summary by CVE is:

Unknown vulnerability in pam_ldap before 180 does not properly handle a new password policy control, which could allow attackers to gain privileges. NOTE: CVE-2005-2497 had also been assigned to this issue, but CVE-2005-2641 is the correct candidate.

The bug was discovered 08/24/2005. The weakness was shared 08/24/2005 by Luke Howard (Website). The advisory is shared at secunia.com. The identification of this vulnerability is CVE-2005-2641 since 08/21/2005. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Technical details are known, but no exploit is available.

The vulnerability scanner Nessus provides a plugin with the ID 21413 (FreeBSD : pam_ldap -- authentication bypass vulnerability (38c76fcf-1744-11da-978e-0001020eed82)), which helps to determine the existence of the flaw in a target environment. It is assigned to the family FreeBSD Local Security Checks and running in the context l. The commercial vulnerability scanner Qualys is able to test this issue with plugin 117825 (CentOS Security Update for OpenLDAP (CESA-2005:767)).

Upgrading to version 180 eliminates this vulnerability. Applying a patch is able to eliminate this problem. The bugfix is ready for download at padl.com. The best possible mitigation is suggested to be upgrading to the latest version. A possible mitigation has been published 3 days after the disclosure of the vulnerability.

The vulnerability is also documented in the databases at X-Force (21982), Tenable (21413), SecurityFocus (BID 14649†), OSVDB (18963†) and Secunia (SA16518†). The entries VDB-1580 and VDB-1581 are related to this item. If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

Name

Version

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 7.3
VulDB Meta Temp Score: 7.0

VulDB Base Score: 7.3
VulDB Temp Score: 7.0
VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

NVD Base Score: 🔍

Exploitinginfo

Class: Remote Code Execution
CWE: Unknown
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Yes

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 21413
Nessus Name: FreeBSD : pam_ldap -- authentication bypass vulnerability (38c76fcf-1744-11da-978e-0001020eed82)
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍
Nessus Port: 🔍

OpenVAS ID: 55166
OpenVAS Name: Debian Security Advisory DSA 785-1 (libpam-ldap)
OpenVAS File: 🔍
OpenVAS Family: 🔍

Qualys ID: 🔍
Qualys Name: 🔍

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

Reaction Time: 🔍
Exposure Time: 🔍

Upgrade: pam_ldap 180
Patch: padl.com

Timelineinfo

08/21/2005 🔍
08/23/2005 +2 days 🔍
08/24/2005 +1 days 🔍
08/24/2005 +0 days 🔍
08/24/2005 +0 days 🔍
08/24/2005 +0 days 🔍
08/25/2005 +0 days 🔍
08/26/2005 +1 days 🔍
08/27/2005 +1 days 🔍
09/05/2005 +9 days 🔍
05/13/2006 +250 days 🔍
01/19/2025 +6826 days 🔍

Sourcesinfo

Advisory: secunia.com⛔
Researcher: Luke Howard
Status: Confirmed
Confirmation: 🔍

CVE: CVE-2005-2641 (🔍)
GCVE (CVE): GCVE-0-2005-2641
GCVE (VulDB): GCVE-100-1709

OVAL: 🔍

CERT: 🔍
X-Force: 21982
SecurityFocus: 14649 - PADL Software PAM_LDAP Authentication Bypass Vulnerability
Secunia: 16518 - pam_ldap Client Authentication Security Bypass, Less Critical
OSVDB: 18963 - pam_ldap Client passwordPolicyResponse BindResponse Authentication Bypass
SecurityTracker: 1014788
Vulnerability Center: 9061 - PADL pam_ldap Module <180 Authentication Bypass, Medium

See also: 🔍

Entryinfo

Created: 08/26/2005 11:05
Updated: 01/19/2025 06:14
Changes: 08/26/2005 11:05 (99), 07/04/2019 09:53 (2), 01/19/2025 06:14 (17)
Complete: 🔍
Cache ID: 216:8DD:103

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

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Are you interested in using VulDB?

Download the whitepaper to learn more about our service!