ID CVE-2017-7551
Summary 389-ds-base version before 1.3.5.19 and 1.3.6.7 are vulnerable to password brute-force attacks during account lockout due to different return codes returned on password attempts.
References
Vulnerable Configurations
  • cpe:2.3:a:fedoraproject:389_directory_server:1.3.6.7:*:*:*:*:*:*:*
    cpe:2.3:a:fedoraproject:389_directory_server:1.3.6.7:*:*:*:*:*:*:*
  • cpe:2.3:a:fedoraproject:389_directory_server:1.3.5.19:*:*:*:*:*:*:*
    cpe:2.3:a:fedoraproject:389_directory_server:1.3.5.19:*:*:*:*:*:*:*
CVSS
Base: 5.0 (as of 12-02-2023 - 23:31)
Impact:
Exploitability:
CWE CWE-209
CAPEC
  • Blind SQL Injection
    Blind SQL Injection results from an insufficient mitigation for SQL Injection. Although suppressing database error messages are considered best practice, the suppression alone is not sufficient to prevent SQL Injection. Blind SQL Injection is a form of SQL Injection that overcomes the lack of error messages. Without the error messages that facilitate SQL Injection, the adversary constructs input strings that probe the target through simple Boolean SQL expressions. The adversary can determine if the syntax and structure of the injection was successful based on whether the query was executed or not. Applied iteratively, the adversary determines how and where the target is vulnerable to SQL Injection.
  • Padding Oracle Crypto Attack
    An adversary is able to efficiently decrypt data without knowing the decryption key if a target system leaks data on whether or not a padding error happened while decrypting the ciphertext. A target system that leaks this type of information becomes the padding oracle and an adversary is able to make use of that oracle to efficiently decrypt data without knowing the decryption key by issuing on average 128*b calls to the padding oracle (where b is the number of bytes in the ciphertext block). In addition to performing decryption, an adversary is also able to produce valid ciphertexts (i.e., perform encryption) by using the padding oracle, all without knowing the encryption key. Any cryptosystem can be vulnerable to padding oracle attacks if the encrypted messages are not authenticated to ensure their validity prior to decryption, and then the information about padding error is leaked to the adversary. This attack technique may be used, for instance, to break CAPTCHA systems or decrypt/modify state information stored in client side objects (e.g., hidden fields or cookies). This attack technique is a side-channel attack on the cryptosystem that uses a data leak from an improperly implemented decryption routine to completely subvert the cryptosystem. The one bit of information that tells the adversary whether a padding error during decryption has occurred, in whatever form it comes, is sufficient for the adversary to break the cryptosystem. That bit of information can come in a form of an explicit error message about a padding error, a returned blank page, or even the server taking longer to respond (a timing attack). This attack can be launched cross domain where an adversary is able to use cross-domain information leaks to get the bits of information from the padding oracle from a target system / service with which the victim is communicating. To do so an adversary sends a request containing ciphertext to the target system. Due to the browser's same origin policy, the adversary is not able to see the response directly, but can use cross-domain information leak techniques to still get the information needed (i.e., information on whether or not a padding error has occurred). For instance, this can be done using "img" tag plus the onerror()/onload() events. The adversary's JavaScript can make web browsers to load an image on the target site, and know if the image is loaded or not. This is 1-bit information needed for the padding oracle attack to work: if the image is loaded, then it is valid padding, otherwise it is not.
  • Query System for Information
    An adversary, aware of an application's location (and possibly authorized to use the application), probes an application's structure and evaluates its robustness by submitting requests and examining responses. Often, this is accomplished by sending variants of expected queries in the hope that these modified queries might return information beyond what the expected set of queries would provide.
  • Fuzzing for garnering J2EE/.NET-based stack traces, for application mapping
    An attacker sends random, malformed, or otherwise unexpected messages to a target application and observes any stack traces produced by error messages. Fuzzing techniques involve sending random or malformed messages to a target and monitoring the target's response. The attacker does not initially know how a target will respond to individual messages but by attempting a large number of message variants they may find a variant that trigger's desired behavior. In this attack, the purpose of the fuzzing is to cause the targeted application to return an error including a stack trace, although fuzzing a target can also sometimes cause the target to enter an unstable state, causing a crash. The stack trace enumerates the chain of methods that led up to the point where the error was encountered. This can not only reveal the names of the methods (some of which may have known weaknesses) but possibly also the location of class files and libraries as well as parameter values. In some cases, the stack trace might even disclose sensitive configuration or user information.
  • Fuzzing and observing application log data/errors for application mapping
    An attacker sends random, malformed, or otherwise unexpected messages to a target application and observes the application's log or error messages returned. Fuzzing techniques involve sending random or malformed messages to a target and monitoring the target's response. The attacker does not initially know how a target will respond to individual messages but by attempting a large number of message variants they may find a variant that trigger's desired behavior. In this attack, the purpose of the fuzzing is to observe the application's log and error messages, although fuzzing a target can also sometimes cause the target to enter an unstable state, causing a crash. By observing logs and error messages, the attacker can learn details about the configuration of the target application and might be able to cause the target to disclose sensitive information.
Access
VectorComplexityAuthentication
NETWORK LOW NONE
Impact
ConfidentialityIntegrityAvailability
PARTIAL NONE NONE
cvss-vector via4 AV:N/AC:L/Au:N/C:P/I:N/A:N
redhat via4
advisories
bugzilla
id 1483865
title Crash while binding to a server during replication online init [rhel-7.4.z]
oval
OR
  • comment Red Hat Enterprise Linux must be installed
    oval oval:com.redhat.rhba:tst:20070304026
  • AND
    • comment Red Hat Enterprise Linux 7 is installed
      oval oval:com.redhat.rhba:tst:20150364027
    • OR
      • AND
        • comment 389-ds-base is earlier than 0:1.3.6.1-19.el7_4
          oval oval:com.redhat.rhsa:tst:20172569001
        • comment 389-ds-base is signed with Red Hat redhatrelease2 key
          oval oval:com.redhat.rhba:tst:20151554002
      • AND
        • comment 389-ds-base-devel is earlier than 0:1.3.6.1-19.el7_4
          oval oval:com.redhat.rhsa:tst:20172569003
        • comment 389-ds-base-devel is signed with Red Hat redhatrelease2 key
          oval oval:com.redhat.rhba:tst:20151554004
      • AND
        • comment 389-ds-base-libs is earlier than 0:1.3.6.1-19.el7_4
          oval oval:com.redhat.rhsa:tst:20172569005
        • comment 389-ds-base-libs is signed with Red Hat redhatrelease2 key
          oval oval:com.redhat.rhba:tst:20151554006
      • AND
        • comment 389-ds-base-snmp is earlier than 0:1.3.6.1-19.el7_4
          oval oval:com.redhat.rhsa:tst:20172569007
        • comment 389-ds-base-snmp is signed with Red Hat redhatrelease2 key
          oval oval:com.redhat.rhsa:tst:20162594008
rhsa
id RHSA-2017:2569
released 2017-09-05
severity Moderate
title RHSA-2017:2569: 389-ds-base security and bug fix update (Moderate)
rpms
  • 389-ds-base-0:1.3.6.1-19.el7_4
  • 389-ds-base-debuginfo-0:1.3.6.1-19.el7_4
  • 389-ds-base-devel-0:1.3.6.1-19.el7_4
  • 389-ds-base-libs-0:1.3.6.1-19.el7_4
  • 389-ds-base-snmp-0:1.3.6.1-19.el7_4
refmap via4
confirm https://pagure.io/389-ds-base/issue/49336
Last major update 12-02-2023 - 23:31
Published 16-08-2017 - 18:29
Last modified 12-02-2023 - 23:31
Back to Top