IBM Security Bulletin: vCenter password disclosure via application tracing in IBM Spectrum Protect (formerly Tivoli Storage Manager) Client and IBM Spectrum Protect (formerly Tivoli Storage Manager) for Virtual Environments: Data Protection for VMware

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 may display the obfuscated VMware vCenter userID and password during VM related operations in the application trace output when application tracing is enabled with the GENERAL trace flag. This problem only manifests when the IBM Spectrum Protect (Tivoli Storage Manager) Client is used as the IBM Spectrum Protect (Tivoli Storage Manager) for Virtual Environments: Data Protection for VMware data mover.

CVE(s): CVE-2017-1378

Affected product(s) and affected version(s):

This security exposure affects:

• IBM Spectrum Protect (formerly Tivoli Storage Manager) Client levels:
  – 7.1.0.0 through 7.1.6.6
  – 6.4 and below all levels (6.4 and below are 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.2
    – 7.1.0.0 through 7.1.6.5
    – 6.4 and below all levels (6.4 and below are 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/2y8dUH6
    X-Force Database: http://ift.tt/2y3C5sr

    The post IBM Security Bulletin: vCenter password disclosure via application tracing in 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.

from IBM Product Security Incident Response Team http://ift.tt/2i7PXvH