LiveActive security incident?Get immediate response
CVE Record

CVE-2019-13565: An issue was discovered in OpenLDAP 2.x before 2.4.48.

An issue was discovered in OpenLDAP 2.x before 2.4.48. When using SASL authentication and session encryption, and relying on the SASL security layers in slapd access controls, it is possible to obtain access that would otherwise be denied via a simple bind for any identity covered in those ACLs. After the first SASL bind is completed, the sasl_ssf value is retained for all new non-SASL connections. Depending on the ACL configuration, this can affect different types of operations (searches, modifications, etc.). In other words, a successful authorization step completed by one user affects the authorization requirement for a different user.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysis

Security readout for executives and security teams

OpenLDAP deployments before 2.4.48 can make an access-control decision using security state left behind by a prior SASL-authenticated connection. In affected configurations, a later simple-bind connection may get directory access that ACLs should have denied. Business risk is unauthorized directory reads or changes where LDAP controls sensitive identity data. Exposure is limited to OpenLDAP 2.x before 2.4.48 where SASL authentication, session encryption, and ACLs depending on SASL security layers are used. Directory services embedded in vendor products may also be affected if they ship vulnerable OpenLDAP builds. Prioritize remediation where LDAP protects employee, customer, or service-account identity data. The issue is not flagged as actively exploited in the provided sources, but affected configurations can undermine directory authorization controls. Mitigation focus: Upgrade OpenLDAP to 2.4.48 or vendor-patched packages.; Apply relevant distro or vendor advisories for Ubuntu, Debian, SUSE, Apple, Oracle, or F5.; Review ACLs that depend on SASL security strength or session encryption state..

Prepared

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2019-13565 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
14Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.