ID CVE-2019-4256
Summary IBM API Connect 5.0.0.0 through 5.0.8.6 uses weaker than expected cryptographic algorithms that could allow an attacker to decrypt highly sensitive information. IBM X-Force ID: 159944.
References
Vulnerable Configurations
  • cpe:2.3:a:ibm:api_connect:5.0.0.0:*:*:*:*:*:*:*
    cpe:2.3:a:ibm:api_connect:5.0.0.0:*:*:*:*:*:*:*
  • cpe:2.3:a:ibm:api_connect:5.0.0.1:*:*:*:*:*:*:*
    cpe:2.3:a:ibm:api_connect:5.0.0.1:*:*:*:*:*:*:*
  • cpe:2.3:a:ibm:api_connect:5.0.1.0:*:*:*:*:*:*:*
    cpe:2.3:a:ibm:api_connect:5.0.1.0:*:*:*:*:*:*:*
  • cpe:2.3:a:ibm:api_connect:5.0.2.0:*:*:*:*:*:*:*
    cpe:2.3:a:ibm:api_connect:5.0.2.0:*:*:*:*:*:*:*
  • cpe:2.3:a:ibm:api_connect:5.0.3.0:*:*:*:*:*:*:*
    cpe:2.3:a:ibm:api_connect:5.0.3.0:*:*:*:*:*:*:*
  • cpe:2.3:a:ibm:api_connect:5.0.4.0:*:*:*:*:*:*:*
    cpe:2.3:a:ibm:api_connect:5.0.4.0:*:*:*:*:*:*:*
  • cpe:2.3:a:ibm:api_connect:5.0.5.0:*:*:*:*:*:*:*
    cpe:2.3:a:ibm:api_connect:5.0.5.0:*:*:*:*:*:*:*
  • cpe:2.3:a:ibm:api_connect:5.0.6.0:*:*:*:*:*:*:*
    cpe:2.3:a:ibm:api_connect:5.0.6.0:*:*:*:*:*:*:*
  • cpe:2.3:a:ibm:api_connect:5.0.6.1:*:*:*:*:*:*:*
    cpe:2.3:a:ibm:api_connect:5.0.6.1:*:*:*:*:*:*:*
  • cpe:2.3:a:ibm:api_connect:5.0.6.2:*:*:*:*:*:*:*
    cpe:2.3:a:ibm:api_connect:5.0.6.2:*:*:*:*:*:*:*
  • cpe:2.3:a:ibm:api_connect:5.0.6.3:*:*:*:*:*:*:*
    cpe:2.3:a:ibm:api_connect:5.0.6.3:*:*:*:*:*:*:*
  • cpe:2.3:a:ibm:api_connect:5.0.6.4:*:*:*:*:*:*:*
    cpe:2.3:a:ibm:api_connect:5.0.6.4:*:*:*:*:*:*:*
  • cpe:2.3:a:ibm:api_connect:5.0.6.5:*:*:*:*:*:*:*
    cpe:2.3:a:ibm:api_connect:5.0.6.5:*:*:*:*:*:*:*
  • cpe:2.3:a:ibm:api_connect:5.0.6.6:*:*:*:*:*:*:*
    cpe:2.3:a:ibm:api_connect:5.0.6.6:*:*:*:*:*:*:*
  • cpe:2.3:a:ibm:api_connect:5.0.7.0:*:*:*:*:*:*:*
    cpe:2.3:a:ibm:api_connect:5.0.7.0:*:*:*:*:*:*:*
  • cpe:2.3:a:ibm:api_connect:5.0.7.1:*:*:*:*:*:*:*
    cpe:2.3:a:ibm:api_connect:5.0.7.1:*:*:*:*:*:*:*
  • cpe:2.3:a:ibm:api_connect:5.0.7.2:*:*:*:*:*:*:*
    cpe:2.3:a:ibm:api_connect:5.0.7.2:*:*:*:*:*:*:*
  • cpe:2.3:a:ibm:api_connect:5.0.8.0:*:*:*:*:*:*:*
    cpe:2.3:a:ibm:api_connect:5.0.8.0:*:*:*:*:*:*:*
  • cpe:2.3:a:ibm:api_connect:5.0.8.1:*:*:*:*:*:*:*
    cpe:2.3:a:ibm:api_connect:5.0.8.1:*:*:*:*:*:*:*
  • cpe:2.3:a:ibm:api_connect:5.0.8.2:*:*:*:*:*:*:*
    cpe:2.3:a:ibm:api_connect:5.0.8.2:*:*:*:*:*:*:*
  • cpe:2.3:a:ibm:api_connect:5.0.8.3:*:*:*:*:*:*:*
    cpe:2.3:a:ibm:api_connect:5.0.8.3:*:*:*:*:*:*:*
  • cpe:2.3:a:ibm:api_connect:5.0.8.4:*:*:*:*:*:*:*
    cpe:2.3:a:ibm:api_connect:5.0.8.4:*:*:*:*:*:*:*
  • cpe:2.3:a:ibm:api_connect:5.0.8.5:*:*:*:*:*:*:*
    cpe:2.3:a:ibm:api_connect:5.0.8.5:*:*:*:*:*:*:*
  • cpe:2.3:a:ibm:api_connect:5.0.8.6:*:*:*:*:*:*:*
    cpe:2.3:a:ibm:api_connect:5.0.8.6:*:*:*:*:*:*:*
CVSS
Base: 5.0 (as of 03-02-2023 - 20:11)
Impact:
Exploitability:
CWE CWE-326
CAPEC
  • Brute Force
    In this attack, some asset (information, functionality, identity, etc.) is protected by a finite secret value. The attacker attempts to gain access to this asset by using trial-and-error to exhaustively explore all the possible secret values in the hope of finding the secret (or a value that is functionally equivalent) that will unlock the asset. Examples of secrets can include, but are not limited to, passwords, encryption keys, database lookup keys, and initial values to one-way functions. The key factor in this attack is the attackers' ability to explore the possible secret space rapidly. This, in turn, is a function of the size of the secret space and the computational power the attacker is able to bring to bear on the problem. If the attacker has modest resources and the secret space is large, the challenge facing the attacker is intractable. While the defender cannot control the resources available to an attacker, they can control the size of the secret space. Creating a large secret space involves selecting one's secret from as large a field of equally likely alternative secrets as possible and ensuring that an attacker is unable to reduce the size of this field using available clues or cryptanalysis. Doing this is more difficult than it sounds since elimination of patterns (which, in turn, would provide an attacker clues that would help them reduce the space of potential secrets) is difficult to do using deterministic machines, such as computers. Assuming a finite secret space, a brute force attack will eventually succeed. The defender must rely on making sure that the time and resources necessary to do so will exceed the value of the information. For example, a secret space that will likely take hundreds of years to explore is likely safe from raw-brute force attacks.
  • Protocol Analysis
    An adversary engages in activities to decipher and/or decode protocol information for a network or application communication protocol used for transmitting information between interconnected nodes or systems on a packet-switched data network. While this type of analysis involves the analysis of a networking protocol inherently, it does not require the presence of an actual or physical network. Although certain techniques for protocol analysis benefit from manipulating live 'on-the-wire' interactions between communicating components, static or dynamic analysis techniques applied to executables as well as to device drivers, such as network interface drivers, can also be used to reveal the function and characteristics of a communication protocol implementation. Depending upon the methods used the process may involve observing, interacting, and modifying actual communications occurring between hosts. The goal of protocol analysis is to derive the data transmission syntax, as well as to extract the meaningful content, including packet or content delimiters used by the protocol. This type of analysis is often performed on closed-specification protocols, or proprietary protocols, but is also useful for analyzing publicly available specifications to determine how particular implementations deviate from published specifications.
  • Encryption Brute Forcing
    An attacker, armed with the cipher text and the encryption algorithm used, performs an exhaustive (brute force) search on the key space to determine the key that decrypts the cipher text to obtain the plaintext.
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
refmap via4
bid 108530
confirm https://www.ibm.com/support/docview.wss?uid=ibm10882968
xf ibm-api-cve20194256-info-disc (159944)
Last major update 03-02-2023 - 20:11
Published 29-05-2019 - 15:29
Last modified 03-02-2023 - 20:11
Back to Top