Bug 2081935 (CVE-2022-29155) - CVE-2022-29155 openldap: OpenLDAP SQL injection
Summary: CVE-2022-29155 openldap: OpenLDAP SQL injection
Keywords:
Status: CLOSED WONTFIX
Alias: CVE-2022-29155
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: 2081936 2083625 2083626 2083627 2083628
Blocks: 2081937
TreeView+ depends on / blocked
 
Reported: 2022-05-05 03:41 UTC by Avinash Hanwate
Modified: 2022-06-06 14:49 UTC (History)
4 users (show)

Fixed In Version: openldap 2.5.12, openldap 2.6.2
Doc Type: If docs needed, set a value
Doc Text:
A vulnerability was found in the openldap-servers package. A SQL injection vulnerability exists in the experimental back-sql backend to slapd, via a SQL statement within an LDAP query. This issue occurs during an LDAP search operation when the search filter is processed due to a lack of proper escaping.
Clone Of:
Environment:
Last Closed: 2022-06-06 14:49:44 UTC


Attachments (Terms of Use)

Description Avinash Hanwate 2022-05-05 03:41:40 UTC
In OpenLDAP 2.x before 2.5.12 and 2.6.x before 2.6.2, a SQL injection vulnerability exists in the experimental back-sql backend to slapd, via a SQL statement within an LDAP query. This can occur during an LDAP search operation when the search filter is processed, due to a lack of proper escaping.

https://bugs.openldap.org/show_bug.cgi?id=9815

Comment 1 Avinash Hanwate 2022-05-05 03:42:02 UTC
Created openldap tracking bugs for this issue:

Affects: fedora-all [bug 2081936]

Comment 3 Simon Pichugin 2022-05-10 23:53:21 UTC
The issue happens in openldap-servers package, which is not shipped since RHEL 8. Hence, I'm closing the issues as WONTFIX.

Comment 4 Product Security DevOps Team 2022-06-06 14:49:42 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-2022-29155


Note You need to log in before you can comment on or make changes to this bug.