Bug 1921381 (CVE-2020-36223) - CVE-2020-36223 openldap: Out-of-bounds read in Values Return Filter
Summary: CVE-2020-36223 openldap: Out-of-bounds read in Values Return Filter
Keywords:
Status: CLOSED WONTFIX
Alias: CVE-2020-36223
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 1921382
Blocks: 1921410
TreeView+ depends on / blocked
 
Reported: 2021-01-27 23:09 UTC by Pedro Sampaio
Modified: 2021-09-23 08:06 UTC (History)
7 users (show)

Fixed In Version: openldap 2.4.57
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-03-02 13:01:59 UTC
Embargoed:

Attachments (Terms of Use)

Description Pedro Sampaio 2021-01-27 23:09:28 UTC 
A flaw was discovered in OpenLDAP before 2.4.57 leading to a slapd crash in the Values Return Filter control handling, resulting in denial of service (double free and out-of-bounds read).

https://bugs.openldap.org/show_bug.cgi?id=9408
https://git.openldap.org/openldap/openldap/-/commit/21981053a1195ae1555e23df4d9ac68d34ede9dd
https://git.openldap.org/openldap/openldap/-/tags/OPENLDAP_REL_ENG_2_4_57
Comment 1 Pedro Sampaio 2021-01-27 23:10:08 UTC 
Created openldap tracking bugs for this issue:

Affects: fedora-all [bug 1921382]
Comment 3 Todd Cullum 2021-02-02 23:15:14 UTC 
Statement:

This flaw does not affect openldap as shipped with Red Hat Enterprise Linux 8 because the slapd server is not shipped. While Red Hat Enterprise Linux 7 does ship the slapd server, this flaw is out of support scope for Red Hat Enterprise Linux 7 and earlier. For more information on support scope, see https://access.redhat.com/support/policy/updates/errata/ .
Comment 4 Product Security DevOps Team 2021-03-02 13:01:59 UTC 
This bug is now closed. Further updates for individual products will be reflected on the CVE page(s):

https://access.redhat.com/security/cve/cve-2020-36223
Note You need to log in before you can comment on or make changes to this bug.