What is the severity of CVE-2016-2972?

CVE-2016-2972 is classified as a moderate severity vulnerability due to the potential exposure of user credentials.

How do I fix CVE-2016-2972?

To fix CVE-2016-2972, users should ensure they are using the latest version of the IBM Sametime Meeting Server and configure their browsers to clear local cache regularly.

What systems are affected by CVE-2016-2972?

CVE-2016-2972 affects IBM Sametime Meeting Server versions 8.5.2 and 9.0, including its subsequent updates.

What type of impact does CVE-2016-2972 have on users?

CVE-2016-2972 can lead to unauthorized access to user credentials stored in the browser cache by local users.

Is there a workaround for CVE-2016-2972?

A temporary workaround for CVE-2016-2972 is to manually log out of sessions and clear the browser cache after use.

Vulnerability/
CVE-2016-2972

high

7.8

CWE

255

29/8/2017

16/9/2024

CVE-2016-2972

First published: Tue Aug 29 2017(Updated: )

IBM Sametime Meeting Server 8.5.2 and 9.0 could store credentials of the Sametime Meetings user in the local cache of their browser which could be accessed by a local user. IBM X-Force ID: 113855.

Credit: psirt@us.ibm.com

Affected Software	Affected Version	How to fix
HCL Sametime	=8.5.2.0
HCL Sametime	=8.5.2.1
HCL Sametime	=9.0.0.0
HCL Sametime	=9.0.0.1
HCL Sametime	=9.0.1

Remedy

http://www.ibm.com/support/docview.wss?uid=swg22006439

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2016-2972?
CVE-2016-2972 is classified as a moderate severity vulnerability due to the potential exposure of user credentials.
How do I fix CVE-2016-2972?
To fix CVE-2016-2972, users should ensure they are using the latest version of the IBM Sametime Meeting Server and configure their browsers to clear local cache regularly.
What systems are affected by CVE-2016-2972?
CVE-2016-2972 affects IBM Sametime Meeting Server versions 8.5.2 and 9.0, including its subsequent updates.
What type of impact does CVE-2016-2972 have on users?
CVE-2016-2972 can lead to unauthorized access to user credentials stored in the browser cache by local users.
Is there a workaround for CVE-2016-2972?
A temporary workaround for CVE-2016-2972 is to manually log out of sessions and clear the browser cache after use.

agent/references
agent/type
agent/softwarecombine
agent/weakness
agent/remedy
agent/severity
agent/author
agent/description
collector/mitre-cve
source/MITRE
agent/last-modified-date
agent/first-publish-date
agent/event
agent/source
agent/tags
collector/nvd-index
agent/software-canonical-lookup-request
vendor/ibm
canonical/hcl sametime
version/hcl sametime/8.5.2.0
version/hcl sametime/8.5.2.1
version/hcl sametime/9.0.0.0
version/hcl sametime/9.0.0.1
version/hcl sametime/9.0.1

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co

By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.