What is the severity of CVE-2014-6160?

CVE-2014-6160 is considered a medium severity vulnerability due to its potential for unauthorized access.

How do I fix CVE-2014-6160?

To mitigate CVE-2014-6160, upgrading IBM WebSphere Service Registry and Repository to version 8.5.0.1 or later is recommended.

What impact does CVE-2014-6160 have on users?

CVE-2014-6160 allows remote attackers to bypass access restrictions on unattended workstations, potentially exposing sensitive data.

Which versions of IBM WebSphere are affected by CVE-2014-6160?

IBM WebSphere Service Registry and Repository versions prior to 8.5.0.1 are affected by CVE-2014-6160.

Is there a known exploit for CVE-2014-6160?

While specific exploits for CVE-2014-6160 have not been widely reported, the vulnerability's nature makes it a potential target for attackers.

Vulnerability/
CVE-2014-6160

low

2.1

CWE

264

29/12/2014

6/8/2024

CVE-2014-6160

First published: Mon Dec 29 2014(Updated: )

IBM WebSphere Service Registry and Repository (WSRR) 8.5 before 8.5.0.1, when Chrome and WebSEAL are used, does not properly process ServiceRegistryDashboard logout actions, which allows remote attackers to bypass intended access restrictions by leveraging an unattended workstation.

Credit: psirt@us.ibm.com

Affected Software	Affected Version	How to fix
IBM WebSphere Service Registry and Repository	=8.5
Google Chrome
Ibm Webseal

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2014-6160?
CVE-2014-6160 is considered a medium severity vulnerability due to its potential for unauthorized access.
How do I fix CVE-2014-6160?
To mitigate CVE-2014-6160, upgrading IBM WebSphere Service Registry and Repository to version 8.5.0.1 or later is recommended.
What impact does CVE-2014-6160 have on users?
CVE-2014-6160 allows remote attackers to bypass access restrictions on unattended workstations, potentially exposing sensitive data.
Which versions of IBM WebSphere are affected by CVE-2014-6160?
IBM WebSphere Service Registry and Repository versions prior to 8.5.0.1 are affected by CVE-2014-6160.
Is there a known exploit for CVE-2014-6160?
While specific exploits for CVE-2014-6160 have not been widely reported, the vulnerability's nature makes it a potential target for attackers.

agent/softwarecombine
agent/type
collector/nvd-index
agent/software-canonical-lookup-request
agent/references
agent/author
agent/severity
agent/weakness
agent/description
collector/mitre-cve
source/MITRE
agent/last-modified-date
agent/tags
agent/first-publish-date
agent/event
agent/source
vendor/ibm
canonical/ibm websphere service registry and repository
version/ibm websphere service registry and repository/8.5
vendor/google
canonical/google chrome
canonical/ibm webseal

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.

Frequently Asked Questions

What is the severity of CVE-2014-6160?
CVE-2014-6160 is considered a medium severity vulnerability due to its potential for unauthorized access.
How do I fix CVE-2014-6160?
To mitigate CVE-2014-6160, upgrading IBM WebSphere Service Registry and Repository to version 8.5.0.1 or later is recommended.
What impact does CVE-2014-6160 have on users?
CVE-2014-6160 allows remote attackers to bypass access restrictions on unattended workstations, potentially exposing sensitive data.
Which versions of IBM WebSphere are affected by CVE-2014-6160?
IBM WebSphere Service Registry and Repository versions prior to 8.5.0.1 are affected by CVE-2014-6160.
Is there a known exploit for CVE-2014-6160?
While specific exploits for CVE-2014-6160 have not been widely reported, the vulnerability's nature makes it a potential target for attackers.