ID CVE-2013-2219
Summary The Red Hat Directory Server before 8.2.11-13 and 389 Directory Server do not properly restrict access to entity attributes, which allows remote authenticated users to obtain sensitive information via a search query for the attribute.
References
Vulnerable Configurations
  • cpe:2.3:a:fedoraproject:389_directory_server
    cpe:2.3:a:fedoraproject:389_directory_server
  • Red Hat Directory Server 7.1
    cpe:2.3:a:redhat:directory_server:7.1
  • Red Hat Directory Server 8.0
    cpe:2.3:a:redhat:directory_server:8.0
  • Red Hat Directory Server 8.1
    cpe:2.3:a:redhat:directory_server:8.1
  • Red Hat Directory Server 8.2
    cpe:2.3:a:redhat:directory_server:8.2
CVSS
Base: 4.0 (as of 31-07-2013 - 17:03)
Impact:
Exploitability:
CWE CWE-264
CAPEC
  • Accessing, Modifying or Executing Executable Files
    An attack of this type exploits a system's configuration that allows an attacker to either directly access an executable file, for example through shell access; or in a possible worst case allows an attacker to upload a file and then execute it. Web servers, ftp servers, and message oriented middleware systems which have many integration points are particularly vulnerable, because both the programmers and the administrators must be in synch regarding the interfaces and the correct privileges for each interface.
  • Leverage Executable Code in Non-Executable Files
    An attack of this type exploits a system's trust in configuration and resource files, when the executable loads the resource (such as an image file or configuration file) the attacker has modified the file to either execute malicious code directly or manipulate the target process (e.g. application server) to execute based on the malicious configuration parameters. Since systems are increasingly interrelated mashing up resources from local and remote sources the possibility of this attack occurring is high. The attack can be directed at a client system, such as causing buffer overrun through loading seemingly benign image files, as in Microsoft Security Bulletin MS04-028 where specially crafted JPEG files could cause a buffer overrun once loaded into the browser. Another example targets clients reading pdf files. In this case the attacker simply appends javascript to the end of a legitimate url for a pdf (http://www.gnucitizen.org/blog/danger-danger-danger/) http://path/to/pdf/file.pdf#whatever_name_you_want=javascript:your_code_here The client assumes that they are reading a pdf, but the attacker has modified the resource and loaded executable javascript into the client's browser process. The attack can also target server processes. The attacker edits the resource or configuration file, for example a web.xml file used to configure security permissions for a J2EE app server, adding role name "public" grants all users with the public role the ability to use the administration functionality. The server trusts its configuration file to be correct, but when they are manipulated, the attacker gains full control.
  • Blue Boxing
    This type of attack against older telephone switches and trunks has been around for decades. A tone is sent by an adversary to impersonate a supervisor signal which has the effect of rerouting or usurping command of the line. While the US infrastructure proper may not contain widespread vulnerabilities to this type of attack, many companies are connected globally through call centers and business process outsourcing. These international systems may be operated in countries which have not upgraded Telco infrastructure and so are vulnerable to Blue boxing. Blue boxing is a result of failure on the part of the system to enforce strong authorization for administrative functions. While the infrastructure is different than standard current applications like web applications, there are historical lessons to be learned to upgrade the access control for administrative functions.
  • Restful Privilege Elevation
    Rest uses standard HTTP (Get, Put, Delete) style permissions methods, but these are not necessarily correlated generally with back end programs. Strict interpretation of HTTP get methods means that these HTTP Get services should not be used to delete information on the server, but there is no access control mechanism to back up this logic. This means that unless the services are properly ACL'd and the application's service implementation are following these guidelines then an HTTP request can easily execute a delete or update on the server side. The attacker identifies a HTTP Get URL such as http://victimsite/updateOrder, which calls out to a program to update orders on a database or other resource. The URL is not idempotent so the request can be submitted multiple times by the attacker, additionally, the attacker may be able to exploit the URL published as a Get method that actually performs updates (instead of merely retrieving data). This may result in malicious or inadvertent altering of data on the server.
  • Target Programs with Elevated Privileges
    This attack targets programs running with elevated privileges. The attacker would try to leverage a bug in the running program and get arbitrary code to execute with elevated privileges. For instance an attacker would look for programs that write to the system directories or registry keys (such as HKLM, which stores a number of critical Windows environment variables). These programs are typically running with elevated privileges and have usually not been designed with security in mind. Such programs are excellent exploit targets because they yield lots of power when they break. The malicious user try to execute its code at the same level as a privileged system call.
  • Manipulating Input to File System Calls
    An attacker manipulates inputs to the target software which the target software passes to file system calls in the OS. The goal is to gain access to, and perhaps modify, areas of the file system that the target software did not intend to be accessible.
Access
VectorComplexityAuthentication
NETWORK LOW SINGLE_INSTANCE
Impact
ConfidentialityIntegrityAvailability
PARTIAL NONE NONE
nessus via4
  • NASL family Red Hat Local Security Checks
    NASL id REDHAT-RHSA-2013-1119.NASL
    description Updated 389-ds-base packages that fix one security issue and three bugs are now available for Red Hat Enterprise Linux 6. The Red Hat Security Response Team has rated this update as having moderate 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 honor defined attribute access controls when evaluating search filter expressions. A remote attacker (with permission to query the Directory Server) could use this flaw to determine the values of restricted attributes via a series of search queries with filter conditions that used restricted attributes. (CVE-2013-2219) This issue was discovered by Ludwig Krispenz of Red Hat. This update also fixes the following bugs : * Previously, the disk monitoring feature did not function properly. If logging functionality was set to critical and logging was disabled, rotated logs would be deleted. If the attribute 'nsslapd-errorlog-level' was explicitly set to any value, even zero, the disk monitoring feature would not stop the Directory Server when it was supposed to. This update corrects the disk monitoring feature settings, and it no longer malfunctions in the described scenarios. (BZ#972930) * Previously, setting the 'nsslapd-disk-monitoring-threshold' attribute via ldapmodify to a large value worked as expected; however, a bug in ldapsearch caused such values for the option to be displayed as negative values. This update corrects the bug in ldapsearch and correct values are now displayed. (BZ#984970) * If logging functionality was not set to critical, then the mount point for the logs directory was incorrectly skipped during the disk space check. (BZ#987850) All 389-ds-base users are advised to upgrade to these updated packages, which contain backported patches to correct these issues. After installing this update, the 389 server service will be restarted automatically.
    last seen 2019-02-21
    modified 2018-11-10
    plugin id 69160
    published 2013-07-31
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=69160
    title RHEL 6 : 389-ds-base (RHSA-2013:1119)
  • NASL family Amazon Linux Local Security Checks
    NASL id ALA_ALAS-2013-223.NASL
    description ns-slapd in 389 Directory Server before 1.3.0.8 allows remote attackers to cause a denial of service (server crash) via a crafted Distinguished Name (DN) in a MOD operation request. 389 Directory Server does not properly restrict access to entity attributes, which allows remote authenticated users to obtain sensitive information via a search query for the attribute.
    last seen 2019-02-21
    modified 2018-04-18
    plugin id 70227
    published 2013-10-01
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=70227
    title Amazon Linux AMI : 389-ds-base (ALAS-2013-223)
  • NASL family Fedora Local Security Checks
    NASL id FEDORA_2013-15540.NASL
    description In this version, a security bug -- modifying an entry specified by an invalid DN crashed the server and a Windows Sync bug were fixed; logconv and setup-ds.pl scripts were enhanced. 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 69537
    published 2013-09-02
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=69537
    title Fedora 19 : 389-ds-base-1.3.1.7-1.fc19 (2013-15540)
  • NASL family Red Hat Local Security Checks
    NASL id REDHAT-RHSA-2013-1116.NASL
    description Updated redhat-ds-base packages that fix one security issue and several bugs are now available for Red Hat Directory Server 8.2. The Red Hat Security Response Team has rated this update as having moderate 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. Red Hat 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 Red Hat Directory Server did not honor defined attribute access controls when evaluating search filter expressions. A remote attacker (with permission to query the Directory Server) could use this flaw to determine the values of restricted attributes via a series of search queries with filter conditions that used restricted attributes. (CVE-2013-2219) This issue was discovered by Ludwig Krispenz of Red Hat. This update also fixes the following bugs : * Prior to this update, the replication of the schema failed because of the attribute 'unhashed#user#password,' which had an invalid name. When this problem happened, the error logs recorded the message 'Schema replication update failed: Invalid syntax.' This update allows this attribute's name and the replication of the schema. (BZ#970934) * Prior to this update, under high load of incoming connections and due to a race condition, a connection which was not yet fully initialized could start being polled. This would lead to a crash. This update ensures that the connection is fully initialized before being in the polling set. (BZ#954051) * Prior to this update, if some requested attributes were skipped during a search (for example, because of an ACI), the returned attribute names and values could be shifted. This update removes attributes that are not authorized from the requested attributes set, so that the returned attributes/values are not shifted. (BZ#922773) * Prior to this update, when an attribute was configured to be encrypted, online import failed to store it in an encrypted way. This update allows encryption, on the consumer side, during an online import. (BZ#893178) * Prior to this update, updating the redhat-ds-base package resulted in the '/etc/dirsrv/slapd-[instance]/certmap.conf' file being overwritten with the default template. With this update, upgrading the redhat-ds-base package no longer causes '/etc/dirsrv/slapd-[instance]/certmap.conf' to be overwritten if the file already exists, preventing users from losing their custom changes. (BZ#919154) All users of Red Hat Directory Server 8.2 are advised to upgrade to these updated packages, which fix these issues.
    last seen 2019-02-21
    modified 2018-11-10
    plugin id 78966
    published 2014-11-08
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=78966
    title RHEL 5 : redhat-ds-base (RHSA-2013:1116)
  • NASL family CentOS Local Security Checks
    NASL id CENTOS_RHSA-2013-1119.NASL
    description Updated 389-ds-base packages that fix one security issue and three bugs are now available for Red Hat Enterprise Linux 6. The Red Hat Security Response Team has rated this update as having moderate 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 honor defined attribute access controls when evaluating search filter expressions. A remote attacker (with permission to query the Directory Server) could use this flaw to determine the values of restricted attributes via a series of search queries with filter conditions that used restricted attributes. (CVE-2013-2219) This issue was discovered by Ludwig Krispenz of Red Hat. This update also fixes the following bugs : * Previously, the disk monitoring feature did not function properly. If logging functionality was set to critical and logging was disabled, rotated logs would be deleted. If the attribute 'nsslapd-errorlog-level' was explicitly set to any value, even zero, the disk monitoring feature would not stop the Directory Server when it was supposed to. This update corrects the disk monitoring feature settings, and it no longer malfunctions in the described scenarios. (BZ#972930) * Previously, setting the 'nsslapd-disk-monitoring-threshold' attribute via ldapmodify to a large value worked as expected; however, a bug in ldapsearch caused such values for the option to be displayed as negative values. This update corrects the bug in ldapsearch and correct values are now displayed. (BZ#984970) * If logging functionality was not set to critical, then the mount point for the logs directory was incorrectly skipped during the disk space check. (BZ#987850) All 389-ds-base users are advised to upgrade to these updated packages, which contain backported patches to correct these issues. After installing this update, the 389 server service will be restarted automatically.
    last seen 2019-02-21
    modified 2018-11-10
    plugin id 69142
    published 2013-07-31
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=69142
    title CentOS 6 : 389-ds-base (CESA-2013:1119)
  • NASL family Oracle Linux Local Security Checks
    NASL id ORACLELINUX_ELSA-2013-1119.NASL
    description From Red Hat Security Advisory 2013:1119 : Updated 389-ds-base packages that fix one security issue and three bugs are now available for Red Hat Enterprise Linux 6. The Red Hat Security Response Team has rated this update as having moderate 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 honor defined attribute access controls when evaluating search filter expressions. A remote attacker (with permission to query the Directory Server) could use this flaw to determine the values of restricted attributes via a series of search queries with filter conditions that used restricted attributes. (CVE-2013-2219) This issue was discovered by Ludwig Krispenz of Red Hat. This update also fixes the following bugs : * Previously, the disk monitoring feature did not function properly. If logging functionality was set to critical and logging was disabled, rotated logs would be deleted. If the attribute 'nsslapd-errorlog-level' was explicitly set to any value, even zero, the disk monitoring feature would not stop the Directory Server when it was supposed to. This update corrects the disk monitoring feature settings, and it no longer malfunctions in the described scenarios. (BZ#972930) * Previously, setting the 'nsslapd-disk-monitoring-threshold' attribute via ldapmodify to a large value worked as expected; however, a bug in ldapsearch caused such values for the option to be displayed as negative values. This update corrects the bug in ldapsearch and correct values are now displayed. (BZ#984970) * If logging functionality was not set to critical, then the mount point for the logs directory was incorrectly skipped during the disk space check. (BZ#987850) All 389-ds-base users are advised to upgrade to these updated packages, which contain backported patches to correct these issues. After installing this update, the 389 server service will be restarted automatically.
    last seen 2019-02-21
    modified 2018-07-18
    plugin id 69158
    published 2013-07-31
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=69158
    title Oracle Linux 6 : 389-ds-base (ELSA-2013-1119)
  • NASL family Scientific Linux Local Security Checks
    NASL id SL_20130730_389_DS_BASE_ON_SL6_X.NASL
    description It was discovered that the 389 Directory Server did not honor defined attribute access controls when evaluating search filter expressions. A remote attacker (with permission to query the Directory Server) could use this flaw to determine the values of restricted attributes via a series of search queries with filter conditions that used restricted attributes. (CVE-2013-2219) This update also fixes the following bugs : - Previously, the disk monitoring feature did not function properly. If logging functionality was set to critical and logging was disabled, rotated logs would be deleted. If the attribute 'nsslapd-errorlog-level' was explicitly set to any value, even zero, the disk monitoring feature would not stop the Directory Server when it was supposed to. This update corrects the disk monitoring feature settings, and it no longer malfunctions in the described scenarios. - Previously, setting the 'nsslapd-disk-monitoring-threshold' attribute via ldapmodify to a large value worked as expected; however, a bug in ldapsearch caused such values for the option to be displayed as negative values. This update corrects the bug in ldapsearch and correct values are now displayed. - If logging functionality was not set to critical, then the mount point for the logs directory was incorrectly skipped during the disk space check. After installing this update, the 389 server service will be restarted automatically.
    last seen 2019-02-21
    modified 2018-12-31
    plugin id 69163
    published 2013-07-31
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=69163
    title Scientific Linux Security Update : 389-ds-base on SL6.x i386/x86_64
redhat via4
advisories
  • bugzilla
    id 987850
    title Disk Monitoring not checking filesystem with logs
    oval
    AND
    • OR
      • comment Red Hat Enterprise Linux 6 Client is installed
        oval oval:com.redhat.rhba:tst:20111656001
      • comment Red Hat Enterprise Linux 6 Server is installed
        oval oval:com.redhat.rhba:tst:20111656002
      • comment Red Hat Enterprise Linux 6 Workstation is installed
        oval oval:com.redhat.rhba:tst:20111656003
      • comment Red Hat Enterprise Linux 6 ComputeNode is installed
        oval oval:com.redhat.rhba:tst:20111656004
    • OR
      • AND
        • comment 389-ds-base is earlier than 0:1.2.11.15-20.el6_4
          oval oval:com.redhat.rhsa:tst:20131119005
        • comment 389-ds-base is signed with Red Hat redhatrelease2 key
          oval oval:com.redhat.rhba:tst:20151554010
      • AND
        • comment 389-ds-base-devel is earlier than 0:1.2.11.15-20.el6_4
          oval oval:com.redhat.rhsa:tst:20131119007
        • comment 389-ds-base-devel is signed with Red Hat redhatrelease2 key
          oval oval:com.redhat.rhba:tst:20151554006
      • AND
        • comment 389-ds-base-libs is earlier than 0:1.2.11.15-20.el6_4
          oval oval:com.redhat.rhsa:tst:20131119009
        • comment 389-ds-base-libs is signed with Red Hat redhatrelease2 key
          oval oval:com.redhat.rhba:tst:20151554008
    rhsa
    id RHSA-2013:1119
    released 2013-07-30
    severity Moderate
    title RHSA-2013:1119: 389-ds-base security and bug fix update (Moderate)
  • rhsa
    id RHSA-2013:1116
rpms
  • 389-ds-base-0:1.2.11.15-20.el6_4
  • 389-ds-base-devel-0:1.2.11.15-20.el6_4
  • 389-ds-base-libs-0:1.2.11.15-20.el6_4
refmap via4
confirm https://bugzilla.redhat.com/show_bug.cgi?id=979508
Last major update 31-07-2013 - 00:00
Published 31-07-2013 - 09:20
Last modified 17-11-2017 - 21:29
Back to Top