p PatchFirst

PatchFirst · Vulnérabilités récentes

Vulnérabilités de python-ldap

Vulnérabilité publiée pour python-ldap au cours des 30 derniers jours : 0. Dans le catalogue KEV : 0.

Filtrer les vulnérabilités
Effacer les filtres

Vulnérabilités : 3

  1. CVE-2025-61912

    Moyenne · CVSS 5.5EPSS 0,46%Correctif disponible

    python-ldap Vulnerable to Improper Encoding or Escaping of Output and Improper Null Termination

    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.

    • Mettez à jour vers 3.4.4-1+deb13u1
    Publication Mise à jour
  2. CVE-2025-61911

    Moyenne · CVSS 5.5EPSS 0,32%Correctif disponible

    python-ldap has sanitization bypass in ldap.filter.escape_filter_chars

    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 adequat

    • Mettez à jour vers 3.4.4-1+deb13u1
    Publication Mise à jour
  3. CVE-2021-46823

    Moyenne · CVSS 6.5EPSS 1,94%Correctif disponible

    CVE-2021-46823

    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.

    • Mettez à jour vers 3.4.0-1
    Publication Mise à jour

Vérifiez votre serveur

Comparez votre pile et les versions installées aux bases de vulnérabilités actuelles.

Vérifiez votre serveur →