Memory allocation with excessive size value vulnerability in Apache Directory LDAP API. A...
zetlyn/cve-ghsa vulnerability ghsa GHSA-h24g-pjpf-8f2m cve CVE-2026-102731 known 2026-10-02
https://github.com/advisories/GHSA-h24g-pjpf-8f2m
Properties
| cwe | CWE-789receipt
What the source handed over{
"comments": 0,
"credits": [],
"cve_id": "CVE-2026-102731",
"cvss": {
"score": null,
"vector_string": null
},
"cvss_severities": {
"cvss_v3": {
"score": 0.0,
"vector_string": null
},
"cvss_v4": {
"score": 0.0,
"vector_string": null
}
},
"cwes": [
{
"cwe_id": "CWE-789",
"name": "Memory Allocation with Excessive Size Value"
}
],
"description": "Memory allocation with excessive size value vulnerability in Apache Directory LDAP API.\n\n\n\nA malicious peer (or a MITM) can send a small BER-encoded response causing a large memory allocation before any data is received. This can lead to an OutOfMemoryError and denial of service.\n\n\n\nThe client JVM OOMs (OutOfMemoryError bypasses the DecoderException handlers) or pins the large allocation per connection while the attacker stalls.\n\n\n\nA handful of connections exhausts any heap. The same bytes from an unauthenticated pre-bind client hit any embedding server that did not set MAX_PDU_SIZE_ATTR.\n\n\n\nThis issue affects Apache Directory LDAP API: from 1.2.0 before 1.2.9.\n\n\n\nUsers are recommended to upgrade to version 1.2.9, which fixes the issue.",
"ghsa_id": "GHSA-h24g-pjpf-8f2m",
"github_reviewed_at": null,
"html_url": "https://github.com/advisories/GHSA-h24g-pjpf-8f2m",
"identifiers": [
{
"type": "GHSA",
"value": "GHSA-h24g-pjpf-8f2m"
},
{
"type": "CVE",
"value": "CVE-2026-102731"
}
],
"nvd_published_at": "2026-10-02T10:17:04Z",
"published_at": "2026-10-02T12:31:09Z",
"references": [
"https://nvd.nist.gov/vuln/detail/CVE-2026-102731",
"https://lists.apache.org/thread.html/b8kg8881pc0v8lp59w0fcfrs69wjbqvd",
"https://github.com/advisories/GHSA-h24g-pjpf-8f2m"
],
"repository_advisory_url": null,
"severity": "unknown",
"source_code_location": "",
"summary": "Memory allocation with excessive size value vulnerability in Apache Directory LDAP API.\n\n\n\nA...",
"type": "unreviewed",
"updated_at": "2026-10-02T12:31:18Z",
"url": "https://api.github.com/advisories/GHSA-h24g-pjpf-8f2m",
"vulnerabilities": [],
"withdrawn_at": null
} |
|---|---|
| severity | unknownreceipt
What the source handed over{
"comments": 0,
"credits": [],
"cve_id": "CVE-2026-102731",
"cvss": {
"score": null,
"vector_string": null
},
"cvss_severities": {
"cvss_v3": {
"score": 0.0,
"vector_string": null
},
"cvss_v4": {
"score": 0.0,
"vector_string": null
}
},
"cwes": [
{
"cwe_id": "CWE-789",
"name": "Memory Allocation with Excessive Size Value"
}
],
"description": "Memory allocation with excessive size value vulnerability in Apache Directory LDAP API.\n\n\n\nA malicious peer (or a MITM) can send a small BER-encoded response causing a large memory allocation before any data is received. This can lead to an OutOfMemoryError and denial of service.\n\n\n\nThe client JVM OOMs (OutOfMemoryError bypasses the DecoderException handlers) or pins the large allocation per connection while the attacker stalls.\n\n\n\nA handful of connections exhausts any heap. The same bytes from an unauthenticated pre-bind client hit any embedding server that did not set MAX_PDU_SIZE_ATTR.\n\n\n\nThis issue affects Apache Directory LDAP API: from 1.2.0 before 1.2.9.\n\n\n\nUsers are recommended to upgrade to version 1.2.9, which fixes the issue.",
"ghsa_id": "GHSA-h24g-pjpf-8f2m",
"github_reviewed_at": null,
"html_url": "https://github.com/advisories/GHSA-h24g-pjpf-8f2m",
"identifiers": [
{
"type": "GHSA",
"value": "GHSA-h24g-pjpf-8f2m"
},
{
"type": "CVE",
"value": "CVE-2026-102731"
}
],
"nvd_published_at": "2026-10-02T10:17:04Z",
"published_at": "2026-10-02T12:31:09Z",
"references": [
"https://nvd.nist.gov/vuln/detail/CVE-2026-102731",
"https://lists.apache.org/thread.html/b8kg8881pc0v8lp59w0fcfrs69wjbqvd",
"https://github.com/advisories/GHSA-h24g-pjpf-8f2m"
],
"repository_advisory_url": null,
"severity": "unknown",
"source_code_location": "",
"summary": "Memory allocation with excessive size value vulnerability in Apache Directory LDAP API.\n\n\n\nA...",
"type": "unreviewed",
"updated_at": "2026-10-02T12:31:18Z",
"url": "https://api.github.com/advisories/GHSA-h24g-pjpf-8f2m",
"vulnerabilities": [],
"withdrawn_at": null
} |
Text
Memory allocation with excessive size value vulnerability in Apache Directory LDAP API.
A...
Memory allocation with excessive size value vulnerability in Apache Directory LDAP API.
A malicious peer (or a MITM) can send a small BER-encoded response causing a large memory allocation before any data is received. This can lead to an OutOfMemoryError and denial of service.
The client JVM OOMs (OutOfMemoryError bypasses the DecoderException handlers) or pins the large allocation per connection while the attacker stalls.
A handful of connections exhausts any heap. The same bytes from an unauthenticated pre-bind client hit any embedding server that did not set MAX_PDU_SIZE_ATTR.
This issue affects Apache Directory LDAP API: from 1.2.0 before 1.2.9.
Users are recommended to upgrade to version 1.2.9, which fixes the issue.