3.4 Low
CVSS3
Attack Vector
NETWORK
Attack Complexity
HIGH
Privileges Required
NONE
User Interaction
REQUIRED
Scope
CHANGED
Confidentiality Impact
LOW
Integrity Impact
NONE
Availability Impact
NONE
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:L/I:N/A:N
4.3 Medium
CVSS2
Access Vector
NETWORK
Access Complexity
MEDIUM
Authentication
NONE
Confidentiality Impact
PARTIAL
Integrity Impact
NONE
Availability Impact
NONE
AV:N/AC:M/Au:N/C:P/I:N/A:N
SSLv3 contains a vulnerability that has been referred to as the Padding Oracle On Downgraded Legacy Encryption (POODLE) attack. SSLv3 is enabled in Algo Credit Limits
CVE-ID: CVE-2014-3566
DESCRIPTION: Product could allow a remote attacker to obtain sensitive information, caused by a design error when using the SSLv3 protocol. A remote user with the ability to conduct a man-in-the-middle attack could exploit this vulnerability via a POODLE (Padding Oracle On Downgraded Legacy Encryption) attack to decrypt SSL sessions and access the plaintext of encrypted connections.
CVSS Base Score: 4.3
CVSS Temporal Score: See https://exchange.xforce.ibmcloud.com/vulnerabilities/97013 for the current score
CVSS Environmental Score*: Undefined
CVSS Vector: (AV:N/AC:M/Au:N/C:P/I:N/A:N)
Algo Credit Limits 4.7 and earlier
A fix has been created for version 4.5.0.05 and 4.7.0.03 of the named product. Download and install the fix as soon as practicable. Fix and installation instructions are provided at the URL listed below.
For versions prior to 4.7.0 IBM recommends upgrading to a fixed, supported version/release/platform of the product.
Patch Number | Download URL |
---|---|
ACLM 4.7.0.03 FP6 | ACL 4.7.0.03 FP6 Solaris Oracle |
ACL 4.7.0.03 FP6 Solaris DB2 | |
ACL 4.7.0.03 FP6 RedHat Oracle | |
ACL 4.7.0.03 FP6 AIX Oracle | |
ACL 4.7.0.03 FP6 Window GUI Oracle | |
ACL 4.7.0.03 FP6 Window GUI DB2 | |
ACLM-TFOLC 4.5.0.05 IF9 | ACL-TFOLC 4.5.0.05 IF9 |
IBM recommends that you review your entire environment to identify areas that enable the SSLv3 protocol and take appropriate mitigation and remediation actions. The most immediate mitigation action that can be taken is disabling SSLv3. You should verify disabling SSLv3 does not cause any compatibility issues.
To disable the SSLv3 protocol in the Tomcat shipped as part of Algo Credit Limits, edit $JLIB_CONFIG_DIR/apps/tomcat/cfg/conf/server.xml. Find the SSL connector and add the following two lines after the SSLEnabled=“true” line:
sslProtocol=“TLS”
sslEnabledProtocols=“TLSv1.2,TLSv1.1,TLSv1”
CPE | Name | Operator | Version |
---|---|---|---|
algo credit limits | eq | 4.7.0 |
3.4 Low
CVSS3
Attack Vector
NETWORK
Attack Complexity
HIGH
Privileges Required
NONE
User Interaction
REQUIRED
Scope
CHANGED
Confidentiality Impact
LOW
Integrity Impact
NONE
Availability Impact
NONE
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:L/I:N/A:N
4.3 Medium
CVSS2
Access Vector
NETWORK
Access Complexity
MEDIUM
Authentication
NONE
Confidentiality Impact
PARTIAL
Integrity Impact
NONE
Availability Impact
NONE
AV:N/AC:M/Au:N/C:P/I:N/A:N