Apache Directory Ldap Api
Monthly
Stack-based buffer overflow in Apache LDAP API 1.2.0 through 1.2.8 allows unauthenticated remote attackers to crash server-side LDAP filter decoders by sending deeply nested search filters before the bind step, producing a denial-of-service condition. No public exploit code or CISA KEV listing was identified at time of analysis and no EPSS score was provided; the independently assessed CVSS vector is AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H, so the primary risk is remote availability loss rather than code execution.
Denial of service in Apache Directory LDAP API versions 1.2.0 through 1.2.8 allows a malicious LDAP peer or man-in-the-middle to crash a client JVM by causing a huge heap allocation before any response payload is delivered. A tiny crafted BER-encoded message declares an oversized length value, and the client's decoder allocates accordingly, producing an OutOfMemoryError that bypasses the decoder's exception handling and pins memory per stalled connection; a handful of such connections can exhaust the heap of any embedding application that failed to set MAX_PDU_SIZE_ATTR. The flaw is remotely triggerable by an unauthenticated peer (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H, 7.5) and requires the victim to connect to, or be intercepted by, an attacker-influenced LDAP server; EPSS is low at 0.19% (8th percentile), there is no CISA KEV listing, and no public exploit code has been identified at time of analysis.
Stack-based buffer overflow in Apache LDAP API 1.2.0 through 1.2.8 allows unauthenticated remote attackers to crash server-side LDAP filter decoders by sending deeply nested search filters before the bind step, producing a denial-of-service condition. No public exploit code or CISA KEV listing was identified at time of analysis and no EPSS score was provided; the independently assessed CVSS vector is AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H, so the primary risk is remote availability loss rather than code execution.
Denial of service in Apache Directory LDAP API versions 1.2.0 through 1.2.8 allows a malicious LDAP peer or man-in-the-middle to crash a client JVM by causing a huge heap allocation before any response payload is delivered. A tiny crafted BER-encoded message declares an oversized length value, and the client's decoder allocates accordingly, producing an OutOfMemoryError that bypasses the decoder's exception handling and pins memory per stalled connection; a handful of such connections can exhaust the heap of any embedding application that failed to set MAX_PDU_SIZE_ATTR. The flaw is remotely triggerable by an unauthenticated peer (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H, 7.5) and requires the victim to connect to, or be intercepted by, an attacker-influenced LDAP server; EPSS is low at 0.19% (8th percentile), there is no CISA KEV listing, and no public exploit code has been identified at time of analysis.