Homepage
About Snyk

Improper Access Control Affecting openldap package, versions <0:2.4.44-25.amzn2.0.5

0.0
high

Snyk CVSS

    Attack Complexity High
    Confidentiality High
    Integrity High

    Threat Intelligence

    EPSS 0.16% (52nd percentile)
Expand this section
NVD
7.5 high
Expand this section
SUSE
6.5 medium
Expand this section
Red Hat
7.4 high

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk ID SNYK-AMZN2-OPENLDAP-5496575
  • published 4 May 2023
  • disclosed 26 Jul 2019
Report a new vulnerability Found a mistake?

Introduced: 26 Jul 2019

CVE-2019-13565 Open this link in a new tab
CWE-284 Open this link in a new tab

How to fix?

Upgrade Amazon-Linux:2 openldap to version 0:2.4.44-25.amzn2.0.5 or higher.
This issue was patched in ALAS2-2023-2033.

NVD Description

Note: Versions mentioned in the description apply only to the upstream openldap package and not the openldap package as distributed by Amazon-Linux. See How to fix? for Amazon-Linux:2 relevant fixed versions and status.

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.

References