Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 1493998 - (CVE-2017-14623) CVE-2017-14623 gopkg.in-ldap.v2: Authentication bypass via empty password
CVE-2017-14623 gopkg.in-ldap.v2: Authentication bypass via empty password
Status: NEW
Product: Security Response
Classification: Other
Component: vulnerability (Show other bugs)
unspecified
All Linux
medium Severity medium
: ---
: ---
Assigned To: Red Hat Product Security
impact=moderate,public=20170824,repor...
: Security
Depends On: 1566145
Blocks: 1493999
  Show dependency treegraph
 
Reported: 2017-09-21 05:54 EDT by Andrej Nemec
Modified: 2018-06-29 18:28 EDT (History)
9 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Andrej Nemec 2017-09-21 05:54:11 EDT
In the ldap.v2 (aka go-ldap) package through 2.5.0 for Go, an attacker may be able to login with an empty password. This issue affects an application using this package if these conditions are met: (1) it relies only on the return error of the Bind function call to determine whether a user is authorized (i.e., a nil return value is interpreted as successful authorization) and (2) it is used with an LDAP server allowing unauthenticated bind.

Upstream patch:

https://github.com/go-ldap/ldap/commit/95ede1266b237bf8e9aa5dce0b3250e51bfefe66

Upstream issue:

https://github.com/go-ldap/ldap/pull/126
Comment 3 Andrej Nemec 2018-05-14 08:11:35 EDT
Statement:

This issue affects the versions of the go in-ldap package as shipped with Red Hat OpenShift Enterprise. However OpenShift explicitly checks for blank passwords in order to prevent anonymous LDAP binds, as such the OpenShift product itself is not directly affected by this vulnerability. Red Hat Product Security has rated this issue as having security impact of Moderate. A future update may address this issue. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/.

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