Register | Log in

python-ldap

Choose email to subscribe with

general

source: python-ldap (main)
version: 3.4.4-2
maintainer: Debian Python Team (DMD)
uploaders: Willem van den Akker [DMD] – Michael Fladischer [DMD]
arch: all any
std-ver: 4.7.2
VCS: Git (Browse, QA)

versions [more versions can be listed by madison] [old versions available from snapshot.debian.org]

[pool directory]

o-o-stable: 3.2.0-4
oldstable: 3.4.3-2
stable: 3.4.4-1
testing: 3.4.4-1
unstable: 3.4.4-2

versioned links

3.2.0-4: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
3.4.3-2: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
3.4.4-1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
3.4.4-2: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]

binaries

python-ldap-doc
python3-ldap (1 bugs: 0, 1, 0, 0)
python3-pyldap

action needed

2 security issues in trixie high

There are 2 open security issues in trixie.

2 important issues:

CVE-2025-61911: python-ldap is a lightweight directory access protocol (LDAP) client API for Python. In versions prior to 3.4.5, the sanitization method `ldap.filter.escape_filter_chars` can be tricked to skip escaping of special characters when a crafted `list` or `dict` is supplied as the `assertion_value` parameter, and the non-default `escape_mode=1` is configured. The method `ldap.filter.escape_filter_chars` supports 3 different escaping modes. `escape_mode=0` (default) and `escape_mode=2` happen to raise exceptions when a `list` or `dict` object is supplied as the `assertion_value` parameter. However, `escape_mode=1` computes without performing adequate logic to ensure a fully escaped return value. If an application relies on the vulnerable method in the `python-ldap` library to escape untrusted user input, an attacker might be able to abuse the vulnerability to launch ldap injection attacks which could potentially disclose or manipulate ldap data meant to be inaccessible to them. Version 3.4.5 fixes the issue by adding a type check at the start of the `ldap.filter.escape_filter_chars` method to raise an exception when the supplied `assertion_value` parameter is not of type `str`.
CVE-2025-61912: python-ldap is a lightweight directory access protocol (LDAP) client API for Python. In versions prior to 3.4.5, ldap.dn.escape_dn_chars() escapes \x00 incorrectly by emitting a backslash followed by a literal NUL byte instead of the RFC-4514 hex form \00. Any application that uses this helper to construct DNs from untrusted input can be made to consistently fail before a request is sent to the LDAP server (e.g., AD), resulting in a client-side denial of service. Version 3.4.5 contains a patch for the issue.

Created: 2025-10-11 Last update: 2025-10-12 16:32

2 security issues in sid high

There are 2 open security issues in sid.

2 important issues:

CVE-2025-61911: python-ldap is a lightweight directory access protocol (LDAP) client API for Python. In versions prior to 3.4.5, the sanitization method `ldap.filter.escape_filter_chars` can be tricked to skip escaping of special characters when a crafted `list` or `dict` is supplied as the `assertion_value` parameter, and the non-default `escape_mode=1` is configured. The method `ldap.filter.escape_filter_chars` supports 3 different escaping modes. `escape_mode=0` (default) and `escape_mode=2` happen to raise exceptions when a `list` or `dict` object is supplied as the `assertion_value` parameter. However, `escape_mode=1` computes without performing adequate logic to ensure a fully escaped return value. If an application relies on the vulnerable method in the `python-ldap` library to escape untrusted user input, an attacker might be able to abuse the vulnerability to launch ldap injection attacks which could potentially disclose or manipulate ldap data meant to be inaccessible to them. Version 3.4.5 fixes the issue by adding a type check at the start of the `ldap.filter.escape_filter_chars` method to raise an exception when the supplied `assertion_value` parameter is not of type `str`.
CVE-2025-61912: python-ldap is a lightweight directory access protocol (LDAP) client API for Python. In versions prior to 3.4.5, ldap.dn.escape_dn_chars() escapes \x00 incorrectly by emitting a backslash followed by a literal NUL byte instead of the RFC-4514 hex form \00. Any application that uses this helper to construct DNs from untrusted input can be made to consistently fail before a request is sent to the LDAP server (e.g., AD), resulting in a client-side denial of service. Version 3.4.5 contains a patch for the issue.

Created: 2025-10-11 Last update: 2025-10-12 16:32

2 security issues in forky high

There are 2 open security issues in forky.

2 important issues:

CVE-2025-61911: python-ldap is a lightweight directory access protocol (LDAP) client API for Python. In versions prior to 3.4.5, the sanitization method `ldap.filter.escape_filter_chars` can be tricked to skip escaping of special characters when a crafted `list` or `dict` is supplied as the `assertion_value` parameter, and the non-default `escape_mode=1` is configured. The method `ldap.filter.escape_filter_chars` supports 3 different escaping modes. `escape_mode=0` (default) and `escape_mode=2` happen to raise exceptions when a `list` or `dict` object is supplied as the `assertion_value` parameter. However, `escape_mode=1` computes without performing adequate logic to ensure a fully escaped return value. If an application relies on the vulnerable method in the `python-ldap` library to escape untrusted user input, an attacker might be able to abuse the vulnerability to launch ldap injection attacks which could potentially disclose or manipulate ldap data meant to be inaccessible to them. Version 3.4.5 fixes the issue by adding a type check at the start of the `ldap.filter.escape_filter_chars` method to raise an exception when the supplied `assertion_value` parameter is not of type `str`.
CVE-2025-61912: python-ldap is a lightweight directory access protocol (LDAP) client API for Python. In versions prior to 3.4.5, ldap.dn.escape_dn_chars() escapes \x00 incorrectly by emitting a backslash followed by a literal NUL byte instead of the RFC-4514 hex form \00. Any application that uses this helper to construct DNs from untrusted input can be made to consistently fail before a request is sent to the LDAP server (e.g., AD), resulting in a client-side denial of service. Version 3.4.5 contains a patch for the issue.

Created: 2025-10-11 Last update: 2025-10-12 16:32

3 security issues in bullseye high

There are 3 open security issues in bullseye.

2 important issues:

CVE-2025-61911: python-ldap is a lightweight directory access protocol (LDAP) client API for Python. In versions prior to 3.4.5, the sanitization method `ldap.filter.escape_filter_chars` can be tricked to skip escaping of special characters when a crafted `list` or `dict` is supplied as the `assertion_value` parameter, and the non-default `escape_mode=1` is configured. The method `ldap.filter.escape_filter_chars` supports 3 different escaping modes. `escape_mode=0` (default) and `escape_mode=2` happen to raise exceptions when a `list` or `dict` object is supplied as the `assertion_value` parameter. However, `escape_mode=1` computes without performing adequate logic to ensure a fully escaped return value. If an application relies on the vulnerable method in the `python-ldap` library to escape untrusted user input, an attacker might be able to abuse the vulnerability to launch ldap injection attacks which could potentially disclose or manipulate ldap data meant to be inaccessible to them. Version 3.4.5 fixes the issue by adding a type check at the start of the `ldap.filter.escape_filter_chars` method to raise an exception when the supplied `assertion_value` parameter is not of type `str`.
CVE-2025-61912: python-ldap is a lightweight directory access protocol (LDAP) client API for Python. In versions prior to 3.4.5, ldap.dn.escape_dn_chars() escapes \x00 incorrectly by emitting a backslash followed by a literal NUL byte instead of the RFC-4514 hex form \00. Any application that uses this helper to construct DNs from untrusted input can be made to consistently fail before a request is sent to the LDAP server (e.g., AD), resulting in a client-side denial of service. Version 3.4.5 contains a patch for the issue.

1 issue postponed or untriaged:

CVE-2021-46823: (needs triaging) python-ldap before 3.4.0 is vulnerable to a denial of service when ldap.schema is used for untrusted schema definitions, because of a regular expression denial of service (ReDoS) flaw in the LDAP schema parser. By sending crafted regex input, a remote authenticated attacker could exploit this vulnerability to cause a denial of service condition.

Created: 2025-10-11 Last update: 2025-10-12 16:32

2 security issues in bookworm high

There are 2 open security issues in bookworm.

2 important issues:

CVE-2025-61911: python-ldap is a lightweight directory access protocol (LDAP) client API for Python. In versions prior to 3.4.5, the sanitization method `ldap.filter.escape_filter_chars` can be tricked to skip escaping of special characters when a crafted `list` or `dict` is supplied as the `assertion_value` parameter, and the non-default `escape_mode=1` is configured. The method `ldap.filter.escape_filter_chars` supports 3 different escaping modes. `escape_mode=0` (default) and `escape_mode=2` happen to raise exceptions when a `list` or `dict` object is supplied as the `assertion_value` parameter. However, `escape_mode=1` computes without performing adequate logic to ensure a fully escaped return value. If an application relies on the vulnerable method in the `python-ldap` library to escape untrusted user input, an attacker might be able to abuse the vulnerability to launch ldap injection attacks which could potentially disclose or manipulate ldap data meant to be inaccessible to them. Version 3.4.5 fixes the issue by adding a type check at the start of the `ldap.filter.escape_filter_chars` method to raise an exception when the supplied `assertion_value` parameter is not of type `str`.
CVE-2025-61912: python-ldap is a lightweight directory access protocol (LDAP) client API for Python. In versions prior to 3.4.5, ldap.dn.escape_dn_chars() escapes \x00 incorrectly by emitting a backslash followed by a literal NUL byte instead of the RFC-4514 hex form \00. Any application that uses this helper to construct DNs from untrusted input can be made to consistently fail before a request is sent to the LDAP server (e.g., AD), resulting in a client-side denial of service. Version 3.4.5 contains a patch for the issue.

Created: 2025-10-11 Last update: 2025-10-12 16:32

A new upstream version is available: 3.4.5 high

A new upstream version 3.4.5 is available, you should consider packaging it.

Created: 2025-10-12 Last update: 2025-10-12 16:31

lintian reports 1 warning normal

Lintian reports 1 warning about this package. You should make the package lintian clean getting rid of them.

Created: 2025-10-12 Last update: 2025-10-12 21:33

debian/patches: 2 patches to forward upstream low

Among the 2 debian patches available in version 3.4.4-2 of the package, we noticed the following issues:

2 patches where the metadata indicates that the patch has not yet been forwarded upstream. You should either forward the patch upstream or update the metadata to document its real status.

Created: 2023-02-26 Last update: 2025-10-12 18:34

testing migrations

excuses:
- Migration status for python-ldap (3.4.4-1 to 3.4.4-2): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- ∙ ∙ Too young, only 1 of 2 days old
- Additional info:
- ∙ ∙ Piuparts tested OK - https://piuparts.debian.org/sid/source/p/python-ldap.html
- ∙ ∙ autopkgtest for python-ldap/3.4.4-2: amd64: Pass, arm64: Pass, i386: Pass, ppc64el: Pass, riscv64: Pass, s390x: Pass
- ∙ ∙ Waiting for reproducibility test results on amd64 - info ♻
- ∙ ∙ Waiting for reproducibility test results on arm64 - info ♻
- ∙ ∙ Required age reduced by 3 days because of autopkgtest
- Not considered

news

[2025-10-12] Accepted python-ldap 3.4.4-2 (source) into unstable (Alexandre Detiste)
[2023-12-10] python-ldap 3.4.4-1 MIGRATED to testing (Debian testing watch)
[2023-12-03] Accepted python-ldap 3.4.4-1 (source) into unstable (Michael Fladischer)
[2022-10-19] python-ldap 3.4.3-2 MIGRATED to testing (Debian testing watch)
[2022-10-16] Accepted python-ldap 3.4.3-2 (source) into unstable (Jelmer Vernooĳ) (signed by: Jelmer Vernooij)
[2022-10-05] python-ldap 3.4.3-1 MIGRATED to testing (Debian testing watch)
[2022-09-27] Accepted python-ldap 3.4.3-1 (source) into unstable (Michael Fladischer)
[2022-09-06] python-ldap 3.4.2-3 MIGRATED to testing (Debian testing watch)
[2022-09-04] Accepted python-ldap 3.4.2-3 (source) into unstable (Emanuele Rocca)
[2022-08-09] Accepted python-ldap 3.4.2-2 (source all arm64) into unstable, unstable (Debian FTP Masters) (signed by: Michael Fladischer)
[2022-08-08] python-ldap 3.4.2-1 MIGRATED to testing (Debian testing watch)
[2022-07-31] Accepted python-ldap 3.4.2-1 (source) into unstable (Michael Fladischer)
[2022-07-09] python-ldap 3.4.0-2 MIGRATED to testing (Debian testing watch)
[2022-07-06] Accepted python-ldap 3.4.0-2 (source) into unstable (Michael Fladischer)
[2022-06-18] Accepted python-ldap 3.4.0-1 (source) into unstable (Sandro Tosi)
[2022-01-15] Accepted python-ldap 3.4.0-1~exp1 (source) into experimental (Michael Fladischer)
[2021-03-11] Accepted python-ldap 3.3.1-1 (source amd64) into experimental (Loic Dachary (OuoU)) (signed by: Loic Dachary)
[2020-01-10] python-ldap 3.2.0-4 MIGRATED to testing (Debian testing watch)
[2020-01-04] Accepted python-ldap 3.2.0-4 (source) into unstable (Sandro Tosi)
[2019-10-31] python-ldap 3.2.0-3 MIGRATED to testing (Debian testing watch)
[2019-10-25] Accepted python-ldap 3.2.0-3 (source) into unstable (Sandro Tosi)
[2019-09-01] python-ldap 3.2.0-2 MIGRATED to testing (Debian testing watch)
[2019-08-27] Accepted python-ldap 3.2.0-2 (source) into unstable (Ondřej Nový)
[2019-08-26] Accepted python-ldap 3.2.0-1 (source) into unstable (Ondřej Nový)
[2018-08-19] python-ldap 3.1.0-2 MIGRATED to testing (Debian testing watch)
[2018-08-14] Accepted python-ldap 3.1.0-2 (source amd64) into unstable (Pierre-Elliott Bécue) (signed by: Jonas Meurer)
[2018-06-07] python-ldap 3.1.0-1 MIGRATED to testing (Debian testing watch)
[2018-06-01] Accepted python-ldap 3.1.0-1 (source) into unstable (Willem van den Akker) (signed by: Adam Borowski)
[2018-04-06] python-ldap 3.0.0-1 MIGRATED to testing (Debian testing watch)
[2018-03-27] Accepted python-ldap 3.0.0-1 (source) into unstable (Willem van den Akker) (signed by: Adam Borowski)

1
2

bugs [bug history graph]

all: 5
RC: 0
I&N: 4
M&W: 1
F&P: 0
patch: 0

links

homepage
lintian (0, 1)
buildd: logs, reproducibility, cross
popcon
browse source code
edit tags
other distros
security tracker
screenshots
debian patches
debci

ubuntu

[Information about Ubuntu for Debian Developers]

version: 3.4.4-1build3
1 bug (1 patch)

Debian Package Tracker — Copyright 2013-2025 The Distro Tracker Developers

Report problems to the tracker.debian.org pseudo-package in the Debian BTS.

Documentation — Bugs — Git Repository — Contributing