4.3 Medium
CVSS2
Attack Vector
NETWORK
Attack 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
0.003 Low
EPSS
Percentile
71.0%
IBM TRIRIGA Application Platform could allow a remote attacker to view image files uploaded by other users through the use of a specially crafted URL.
Vulnerability Details
CVEID:****CVE-2014-8895
CVSS Base Score: 4.30
CVSS Temporal Score: See <https://exchange.xforce.ibmcloud.com/vulnerabilities/99014> for the current score
CVSS Environmental Score*: Undefined
CVSS Vector: (AV:N/AC:M/Au:N/C:P/I:N/A:N)
Affected Products and Versions
The following Application Platform versions are affected.
ยท IBM TRIRIGA Application Platform 3.4.1 and earlier versions
ยท IBM TRIRIGA Application Platform 3.3.2.2 and earlier versions
ยท IBM TRIRIGA Application Platform 3.2.1 and earlier versions
Remediation/Fixes
The recommended solution is to apply the fix for each named product as soon as practical. Please see below for information on the fixes available.
This vulnerability is resolved in the IBM TRIRIGA Application Platform fix packs 3.4.1.1, and 3.3.2.3. Due to the threat posed by a successful attack, IBM strongly recommends an upgrade to TRIRIGA Application Platform version 3.4.1.1 or 3.3.2.3. Anyone running IBM TRIRIGA Application Platform prior to 3.3.0 should contact customer support. Instructions on how to download and install the platform fix pack can be found here: IBM Fix Central Instructions on how to download and install IBM TRIRIGA Application Platform 3.4.1 can be found here:
<http://www-01.ibm.com/support/docview.wss?uid=swg24038161>
Workarounds and Mitigations
Until you apply the fixes, it may be possible to reduce the risk of successful attack by restricting network protocols required by an attack. For attacks that require certain privileges or access to certain packages, removing the privileges or the ability to access the packages from unprivileged users may help reduce the risk of successful attack. Both approaches may break application functionality, so IBM strongly recommends that customers test changes on non-production systems. Neither approach should be considered a long-term solution as neither corrects the underlying problem.
**