<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://cve.radiocsirt.org</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Fri, 02 Oct 2026 13:59:37 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-44305 — Lemur: LDAP TLS certificate verification globally disabled enables credential interception</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2026-44305</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Netflix lemur&lt;/p&gt;
&lt;p&gt;Lemur manages TLS certificate creation. Prior to 1.9.0, when LDAP TLS is enabled (LDAP_USE_TLS = True), Lemur&amp;#39;s LDAP authentication module unconditionally disables TLS certificate verification at the global ldap module level. This allows a man-in-the-middle attacker positioned between Lemur and the LDAP server to intercept all authentication credentials. This vulnerability is fixed in 1.9.0.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Netflix lemur&lt;/p&gt;
&lt;p&gt;Lemur manages TLS certificate creation. Prior to 1.9.0, when LDAP TLS is enabled (LDAP_USE_TLS = True), Lemur&amp;#39;s LDAP authentication module unconditionally disables TLS certificate verification at the global ldap module level. This allows a man-in-the-middle attacker positioned between Lemur and the LDAP server to intercept all authentication credentials. This vulnerability is fixed in 1.9.0.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2026-44305</guid>
    </item>
    <item>
      <title>GHSA-vr7c-r5gj-j3w5 — Lemur: LDAP Authentication Globally Disables TLS Certificate Verification When LDAP_USE_TLS Is Enabled</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-vr7c-r5gj-j3w5</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: lemur&lt;/p&gt;
&lt;p&gt;## Description&lt;/p&gt;
&lt;p&gt;### Overview&lt;/p&gt;
&lt;p&gt;When LDAP TLS is enabled (`LDAP_USE_TLS = True`), Lemur&amp;#39;s LDAP authentication module unconditionally disables TLS certificate verification at the **global** `ldap` module level. This allows a man-in-the-middle attacker positioned between Lemur and the LDAP server to intercept all authentication credentials.&lt;/p&gt;
&lt;p&gt;### Vulnerable Code&lt;/p&gt;
&lt;p&gt;**Location:** `lemur/auth/ldap.py`, `_bind()` method, line ~172&lt;/p&gt;
&lt;p&gt;```python
if self.ldap_use_tls:
    ldap.set_option(ldap.OPT_X_TLS_REQUIRE_CERT, ldap.OPT_X_TLS_NEVER)
```&lt;/p&gt;
&lt;p&gt;Key issues:&lt;/p&gt;
&lt;p&gt;1. `ldap.set_option()` is a **global** call (as opposed to `self.ldap_client.set_option()`), meaning it disables TLS verification for the entire Python process, not just this connection
2. `OPT_X_TLS_NEVER` means no certificate validation is performed whatsoever — self-signed, expired, wrong hostname, and revoked certificates are all silently accepted
3. There is no configuration option to override this behavior — TLS verification is always disabled when TLS is enabled&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;A network-positioned attacker (man-in-the-middle) between Lemur and the LDAP server can:&lt;/p&gt;
&lt;p&gt;- **Intercept all LDAP credentials** (usernames and plaintext passwords) for every user who authenticates
- **Modify LDAP responses** to inject arbitrary group memberships, granting admin access
- **Compromise the entire PKI infrastructure** managed by Lemur, since authentication controls access to certificates and private keys&lt;/p&gt;
&lt;p&gt;This is particularly severe because Lemur is…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: lemur&lt;/p&gt;
&lt;p&gt;## Description&lt;/p&gt;
&lt;p&gt;### Overview&lt;/p&gt;
&lt;p&gt;When LDAP TLS is enabled (`LDAP_USE_TLS = True`), Lemur&amp;#39;s LDAP authentication module unconditionally disables TLS certificate verification at the **global** `ldap` module level. This allows a man-in-the-middle attacker positioned between Lemur and the LDAP server to intercept all authentication credentials.&lt;/p&gt;
&lt;p&gt;### Vulnerable Code&lt;/p&gt;
&lt;p&gt;**Location:** `lemur/auth/ldap.py`, `_bind()` method, line ~172&lt;/p&gt;
&lt;p&gt;```python
if self.ldap_use_tls:
    ldap.set_option(ldap.OPT_X_TLS_REQUIRE_CERT, ldap.OPT_X_TLS_NEVER)
```&lt;/p&gt;
&lt;p&gt;Key issues:&lt;/p&gt;
&lt;p&gt;1. `ldap.set_option()` is a **global** call (as opposed to `self.ldap_client.set_option()`), meaning it disables TLS verification for the entire Python process, not just this connection
2. `OPT_X_TLS_NEVER` means no certificate validation is performed whatsoever — self-signed, expired, wrong hostname, and revoked certificates are all silently accepted
3. There is no configuration option to override this behavior — TLS verification is always disabled when TLS is enabled&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;A network-positioned attacker (man-in-the-middle) between Lemur and the LDAP server can:&lt;/p&gt;
&lt;p&gt;- **Intercept all LDAP credentials** (usernames and plaintext passwords) for every user who authenticates
- **Modify LDAP responses** to inject arbitrary group memberships, granting admin access
- **Compromise the entire PKI infrastructure** managed by Lemur, since authentication controls access to certificates and private keys&lt;/p&gt;
&lt;p&gt;This is particularly severe because Lemur is…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-vr7c-r5gj-j3w5</guid>
    </item>
  </channel>
</rss>
