ID CVE-2014-0132
Summary The SASL authentication functionality in 389 Directory Server before 1.2.11.26 allows remote authenticated users to connect as an arbitrary user and gain privileges via the authzid parameter in a SASL/GSSAPI bind.
References
Vulnerable Configurations
  • Fedora Project 389 Directory Server 1.2.11.25
    cpe:2.3:a:fedoraproject:389_directory_server:1.2.11.25
  • Fedora Project 389 Directory Server 1.2.11.23
    cpe:2.3:a:fedoraproject:389_directory_server:1.2.11.23
  • Fedora Project 389 Directory Server 1.2.11.22
    cpe:2.3:a:fedoraproject:389_directory_server:1.2.11.22
  • Fedora Project 389 Directory Server 1.2.11.21
    cpe:2.3:a:fedoraproject:389_directory_server:1.2.11.21
  • Fedora Project 389 Directory Server 1.2.11.20
    cpe:2.3:a:fedoraproject:389_directory_server:1.2.11.20
  • Fedora Project 389 Directory Server 1.2.11.1
    cpe:2.3:a:fedoraproject:389_directory_server:1.2.11.1
  • Fedora Project 389 Directory Server 1.2.11.10
    cpe:2.3:a:fedoraproject:389_directory_server:1.2.11.10
  • Fedora Project 389 Directory Server 1.2.11.11
    cpe:2.3:a:fedoraproject:389_directory_server:1.2.11.11
  • Fedora Project 389 Directory Server 1.2.11.12
    cpe:2.3:a:fedoraproject:389_directory_server:1.2.11.12
  • Fedora Project 389 Directory Server 1.2.11.13
    cpe:2.3:a:fedoraproject:389_directory_server:1.2.11.13
  • Fedora Project 389 Directory Server 1.2.11.14
    cpe:2.3:a:fedoraproject:389_directory_server:1.2.11.14
  • Fedora Project 389 Directory Server 1.2.11.15
    cpe:2.3:a:fedoraproject:389_directory_server:1.2.11.15
  • Fedora Project 389 Directory Server 1.2.11.17
    cpe:2.3:a:fedoraproject:389_directory_server:1.2.11.17
  • Fedora Project 389 Directory Server 1.2.11.19
    cpe:2.3:a:fedoraproject:389_directory_server:1.2.11.19
  • Fedora Project 389 Directory Server 1.2.11.5
    cpe:2.3:a:fedoraproject:389_directory_server:1.2.11.5
  • Fedora Project 389 Directory Server 1.2.11.6
    cpe:2.3:a:fedoraproject:389_directory_server:1.2.11.6
  • Fedora Project 389 Directory Server 1.2.11.8
    cpe:2.3:a:fedoraproject:389_directory_server:1.2.11.8
  • Fedora Project 389 Directory Server 1.2.11.9
    cpe:2.3:a:fedoraproject:389_directory_server:1.2.11.9
CVSS
Base: 6.5 (as of 19-03-2014 - 10:12)
Impact:
Exploitability:
CWE CWE-287
CAPEC
  • Authentication Abuse
    An attacker obtains unauthorized access to an application, service or device either through knowledge of the inherent weaknesses of an authentication mechanism, or by exploiting a flaw in the authentication scheme's implementation. In such an attack an authentication mechanism is functioning but a carefully controlled sequence of events causes the mechanism to grant access to the attacker. This attack may exploit assumptions made by the target's authentication procedures, such as assumptions regarding trust relationships or assumptions regarding the generation of secret values. This attack differs from Authentication Bypass attacks in that Authentication Abuse allows the attacker to be certified as a valid user through illegitimate means, while Authentication Bypass allows the user to access protected material without ever being certified as an authenticated user. This attack does not rely on prior sessions established by successfully authenticating users, as relied upon for the "Exploitation of Session Variables, Resource IDs and other Trusted Credentials" attack patterns.
  • Exploiting Trust in Client (aka Make the Client Invisible)
    An attack of this type exploits a programs' vulnerabilities in client/server communication channel authentication and data integrity. It leverages the implicit trust a server places in the client, or more importantly, that which the server believes is the client. An attacker executes this type of attack by placing themselves in the communication channel between client and server such that communication directly to the server is possible where the server believes it is communicating only with a valid client. There are numerous variations of this type of attack.
  • Utilizing REST's Trust in the System Resource to Register Man in the Middle
    This attack utilizes a REST(REpresentational State Transfer)-style applications' trust in the system resources and environment to place man in the middle once SSL is terminated. Rest applications premise is that they leverage existing infrastructure to deliver web services functionality. An example of this is a Rest application that uses HTTP Get methods and receives a HTTP response with an XML document. These Rest style web services are deployed on existing infrastructure such as Apache and IIS web servers with no SOAP stack required. Unfortunately from a security standpoint, there frequently is no interoperable identity security mechanism deployed, so Rest developers often fall back to SSL to deliver security. In large data centers, SSL is typically terminated at the edge of the network - at the firewall, load balancer, or router. Once the SSL is terminated the HTTP request is in the clear (unless developers have hashed or encrypted the values, but this is rare). The attacker can utilize a sniffer such as Wireshark to snapshot the credentials, such as username and password that are passed in the clear once SSL is terminated. Once the attacker gathers these credentials, they can submit requests to the web service provider just as authorized user do. There is not typically an authentication on the client side, beyond what is passed in the request itself so once this is compromised, then this is generally sufficient to compromise the service's authentication scheme.
  • Man in the Middle Attack
    This type of attack targets the communication between two components (typically client and server). The attacker places himself in the communication channel between the two components. Whenever one component attempts to communicate with the other (data flow, authentication challenges, etc.), the data first goes to the attacker, who has the opportunity to observe or alter it, and it is then passed on to the other component as if it was never intercepted. This interposition is transparent leaving the two compromised components unaware of the potential corruption or leakage of their communications. The potential for Man-in-the-Middle attacks yields an implicit lack of trust in communication or identify between two components.
Access
VectorComplexityAuthentication
NETWORK LOW SINGLE_INSTANCE
Impact
ConfidentialityIntegrityAvailability
PARTIAL PARTIAL PARTIAL
nessus via4
  • NASL family Scientific Linux Local Security Checks
    NASL id SL_20140313_389_DS_BASE_ON_SL6_X.NASL
    description It was discovered that the 389 Directory Server did not properly handle certain SASL-based authentication mechanisms. A user able to authenticate to the directory using these SASL mechanisms could connect as any other directory user, including the administrative Directory Manager account. This could allow them to modify configuration values, as well as read and write any data the directory holds. (CVE-2014-0132) After installing this update, the 389 server service will be restarted automatically.
    last seen 2019-02-21
    modified 2018-12-28
    plugin id 73013
    published 2014-03-14
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=73013
    title Scientific Linux Security Update : 389-ds-base on SL6.x i386/x86_64
  • NASL family Fedora Local Security Checks
    NASL id FEDORA_2014-3936.NASL
    description An important security bug was fixed. Note that Tenable Network Security has extracted the preceding description block directly from the Fedora security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.
    last seen 2019-02-21
    modified 2015-10-19
    plugin id 73048
    published 2014-03-17
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=73048
    title Fedora 19 : 389-ds-base-1.3.1.22-1.fc19 (2014-3936)
  • NASL family CentOS Local Security Checks
    NASL id CENTOS_RHSA-2014-0292.NASL
    description Updated 389-ds-base packages that fix one security issue are now available for Red Hat Enterprise Linux 6. The Red Hat Security Response Team has rated this update as having Important security impact. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available from the CVE link in the References section. The 389 Directory Server is an LDAPv3 compliant server. The base packages include the Lightweight Directory Access Protocol (LDAP) server and command-line utilities for server administration. It was discovered that the 389 Directory Server did not properly handle certain SASL-based authentication mechanisms. A user able to authenticate to the directory using these SASL mechanisms could connect as any other directory user, including the administrative Directory Manager account. This could allow them to modify configuration values, as well as read and write any data the directory holds. (CVE-2014-0132) All 389-ds-base users are advised to upgrade to these updated packages, which contain a backported patch to correct this issue. After installing this update, the 389 server service will be restarted automatically.
    last seen 2019-02-21
    modified 2018-11-10
    plugin id 72987
    published 2014-03-14
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=72987
    title CentOS 6 : 389-ds-base (CESA-2014:0292)
  • NASL family Oracle Linux Local Security Checks
    NASL id ORACLELINUX_ELSA-2014-0292.NASL
    description From Red Hat Security Advisory 2014:0292 : Updated 389-ds-base packages that fix one security issue are now available for Red Hat Enterprise Linux 6. The Red Hat Security Response Team has rated this update as having Important security impact. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available from the CVE link in the References section. The 389 Directory Server is an LDAPv3 compliant server. The base packages include the Lightweight Directory Access Protocol (LDAP) server and command-line utilities for server administration. It was discovered that the 389 Directory Server did not properly handle certain SASL-based authentication mechanisms. A user able to authenticate to the directory using these SASL mechanisms could connect as any other directory user, including the administrative Directory Manager account. This could allow them to modify configuration values, as well as read and write any data the directory holds. (CVE-2014-0132) All 389-ds-base users are advised to upgrade to these updated packages, which contain a backported patch to correct this issue. After installing this update, the 389 server service will be restarted automatically.
    last seen 2019-02-21
    modified 2015-12-01
    plugin id 73008
    published 2014-03-14
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=73008
    title Oracle Linux 6 : 389-ds-base (ELSA-2014-0292)
  • NASL family Amazon Linux Local Security Checks
    NASL id ALA_ALAS-2014-311.NASL
    description It was discovered that the 389 Directory Server did not properly handle certain SASL-based authentication mechanisms. A user able to authenticate to the directory using these SASL mechanisms could connect as any other directory user, including the administrative Directory Manager account. This could allow them to modify configuration values, as well as read and write any data the directory holds.
    last seen 2019-02-21
    modified 2018-04-18
    plugin id 73230
    published 2014-03-28
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=73230
    title Amazon Linux AMI : 389-ds-base (ALAS-2014-311)
  • NASL family Red Hat Local Security Checks
    NASL id REDHAT-RHSA-2014-0292.NASL
    description Updated 389-ds-base packages that fix one security issue are now available for Red Hat Enterprise Linux 6. The Red Hat Security Response Team has rated this update as having Important security impact. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available from the CVE link in the References section. The 389 Directory Server is an LDAPv3 compliant server. The base packages include the Lightweight Directory Access Protocol (LDAP) server and command-line utilities for server administration. It was discovered that the 389 Directory Server did not properly handle certain SASL-based authentication mechanisms. A user able to authenticate to the directory using these SASL mechanisms could connect as any other directory user, including the administrative Directory Manager account. This could allow them to modify configuration values, as well as read and write any data the directory holds. (CVE-2014-0132) All 389-ds-base users are advised to upgrade to these updated packages, which contain a backported patch to correct this issue. After installing this update, the 389 server service will be restarted automatically.
    last seen 2019-02-21
    modified 2018-11-10
    plugin id 73010
    published 2014-03-14
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=73010
    title RHEL 6 : 389-ds-base (RHSA-2014:0292)
  • NASL family Fedora Local Security Checks
    NASL id FEDORA_2014-3904.NASL
    description An important security bug was fixed. Note that Tenable Network Security has extracted the preceding description block directly from the Fedora security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.
    last seen 2019-02-21
    modified 2015-10-19
    plugin id 73047
    published 2014-03-17
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=73047
    title Fedora 20 : 389-ds-base-1.3.2.16-1.fc20 (2014-3904)
redhat via4
advisories
bugzilla
id 1074845
title CVE-2014-0132 389-ds: flaw in parsing authzid can lead to privilege escalation
oval
AND
  • OR
    • comment Red Hat Enterprise Linux 6 Client is installed
      oval oval:com.redhat.rhsa:tst:20100842001
    • comment Red Hat Enterprise Linux 6 Server is installed
      oval oval:com.redhat.rhsa:tst:20100842002
    • comment Red Hat Enterprise Linux 6 Workstation is installed
      oval oval:com.redhat.rhsa:tst:20100842003
    • comment Red Hat Enterprise Linux 6 ComputeNode is installed
      oval oval:com.redhat.rhsa:tst:20100842004
  • OR
    • AND
      • comment 389-ds-base is earlier than 0:1.2.11.15-32.el6_5
        oval oval:com.redhat.rhsa:tst:20140292005
      • comment 389-ds-base is signed with Red Hat redhatrelease2 key
        oval oval:com.redhat.rhsa:tst:20120813006
    • AND
      • comment 389-ds-base-devel is earlier than 0:1.2.11.15-32.el6_5
        oval oval:com.redhat.rhsa:tst:20140292009
      • comment 389-ds-base-devel is signed with Red Hat redhatrelease2 key
        oval oval:com.redhat.rhsa:tst:20120813008
    • AND
      • comment 389-ds-base-libs is earlier than 0:1.2.11.15-32.el6_5
        oval oval:com.redhat.rhsa:tst:20140292007
      • comment 389-ds-base-libs is signed with Red Hat redhatrelease2 key
        oval oval:com.redhat.rhsa:tst:20120813010
rhsa
id RHSA-2014:0292
released 2014-03-13
severity Important
title RHSA-2014:0292: 389-ds-base security update (Important)
rpms
  • 389-ds-base-0:1.2.11.15-32.el6_5
  • 389-ds-base-devel-0:1.2.11.15-32.el6_5
  • 389-ds-base-libs-0:1.2.11.15-32.el6_5
refmap via4
confirm
secunia
  • 57412
  • 57427
Last major update 19-03-2014 - 10:12
Published 18-03-2014 - 13:02
Back to Top