OpenSSL vulnerabilities were disclosed on June 11, 2015 and December 3, 2015 by the OpenSSL Project. OpenSSL, used by the IBM Spectrum Protect (formerly Tivoli Storage Manager) Client and IBM Spectrum Protect for Virtual Environments (formerly Tivoli Storage Manager for Virtual Environments): Data Protection from VMware, has addressed the applicable CVEs.
CVE(s): CVE-2015-1791, CVE-2015-3193, CVE-2015-3194, CVE-2015-3195, CVE-2015-3196, CVE-2015-1794
Affected product(s) and affected version(s):
These security exposures affect network connections between IBM Spectrum Protect (formerly Tivoli Storage Manager) and VMware services. This exposure affects:
- IBM Spectrum Protect (formerly Tivoli Storage Manager) Client levels:
– 7.1.0.0 through 7.1.6.4
– 6.4 all levels
– 6.3 all levels (6.3 is EOS)Note that the 8.1 client is not affected because the affected component in 8.1 has been moved to Data Protection for VMware.
- IBM Spectrum Protect for Virtual Environments (formerly Tivoli Storage Manager for Virtual Environments): Data Protection for VMware levels:
– 8.1.0.0 through 8.1.0.1
– 7.1.0.0 through 7.1.6.4
– 6.4 all levels
– 6.3 all levels (6.3 is EOS)Note that for 8.1, the affected component was moved from the Client to DP for VMware.
Refer to the following reference URLs for remediation and additional vulnerability details:
Source Bulletin: http://ift.tt/2rorO6p
X-Force Database: http://ift.tt/2knxB8v
X-Force Database: http://ift.tt/1rd28Gc
X-Force Database: http://ift.tt/1KB3Vh1
X-Force Database: http://ift.tt/1QmYT4z
X-Force Database: http://ift.tt/1KB3SSD
X-Force Database: http://ift.tt/1rd26hzThe post IBM Security Bulletin: Multiple Vulnerabilities in OpenSSL affect IBM Spectrum Protect (formerly Tivoli Storage Manager) Client and IBM Spectrum Protect (formerly Tivoli Storage Manager) for Virtual Environments: Data Protection for VMware appeared first on IBM PSIRT Blog.
- IBM Spectrum Protect for Virtual Environments (formerly Tivoli Storage Manager for Virtual Environments): Data Protection for VMware levels:
from IBM Product Security Incident Response Team http://ift.tt/2smlXvT
No comments:
Post a Comment
Note: Only a member of this blog may post a comment.