Bug 1610645 (CVE-2018-10919) - CVE-2018-10919 samba: Confidential attribute disclosure via substring search
Summary: CVE-2018-10919 samba: Confidential attribute disclosure via substring search
Keywords:
Status: CLOSED NOTABUG
Alias: CVE-2018-10919
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: 1612808 1617911 1617914 1618620 1618621
Blocks: 1610646
TreeView+ depends on / blocked
 
Reported: 2018-08-01 05:34 UTC by Sam Fowler
Modified: 2022-03-13 15:19 UTC (History)
29 users (show)

Fixed In Version: samba 4.6.16, samba 4.7.9, samba 4.8.4
Doc Type: If docs needed, set a value
Doc Text:
The Samba Active Directory LDAP server was vulnerable to an information disclosure flaw because of missing access control checks. An authenticated attacker could use this flaw to extract confidential attribute values using LDAP search expressions.
Clone Of:
Environment:
Last Closed: 2019-07-12 13:05:52 UTC
Embargoed:

Attachments (Terms of Use)

Description Sam Fowler 2018-08-01 05:34:54 UTC 
When using custom LDAP attributes, Samba seems to recognize the searchFlags confidential flag on custom attributes and hides them from all non-admin users. However, the values of the attributes can still be guessed efficiently by brute forcing them one character after another in a wildcard search query.
Comment 2 Sam Fowler 2018-08-16 03:41:43 UTC 
External Reference:

https://www.samba.org/samba/security/CVE-2018-10919.html
Comment 3 Sam Fowler 2018-08-16 07:13:27 UTC 
Created samba tracking bugs for this issue:

Affects: fedora-all [bug 1617911]
Comment 5 Huzaifa S. Sidhpurwala 2018-08-17 05:49:06 UTC 
Acknowledgments:

Name: Phillip Kuhrt (the Samba project)
Comment 8 Product Security DevOps Team 2019-07-12 13:05:52 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-2018-10919
Note You need to log in before you can comment on or make changes to this bug.