What is the severity of CVE-2013-6687?

CVE-2013-6687 is classified as a medium-severity vulnerability due to its potential impact on administrative credentials.

How do I fix CVE-2013-6687?

To fix CVE-2013-6687, update to the latest version of Cisco Webex Meetings Server that addresses this issue.

Who is affected by CVE-2013-6687?

Any organization using Cisco Webex Meetings Server is at risk of CVE-2013-6687 if they do not have the proper security measures in place.

What type of attack vector does CVE-2013-6687 represent?

CVE-2013-6687 represents an information disclosure vulnerability, allowing remote authenticated users to view administrative passwords.

Are there any workarounds for CVE-2013-6687 until a patch is applied?

There are no recommended workarounds for CVE-2013-6687; applying the available patch is the best course of action.

Vulnerability/
CVE-2013-6687

medium

CWE

255

16/1/2014

6/8/2024

CVE-2013-6687

First published: Thu Jan 16 2014(Updated: )

The web portal in the Enterprise License Manager component in Cisco WebEx Meetings Server allows remote authenticated users to discover the cleartext administrative password by reading HTML source code, aka Bug ID CSCul33876.

Credit: ykramarz@cisco.com

Affected Software	Affected Version	How to fix
Cisco Webex Meetings Server Software

Never miss a vulnerability like this again

Reference Links

http://tools.cisco.com/security/center/content/CiscoSecurityNotice/CVE-2013-6687

Frequently Asked Questions

What is the severity of CVE-2013-6687?
CVE-2013-6687 is classified as a medium-severity vulnerability due to its potential impact on administrative credentials.
How do I fix CVE-2013-6687?
To fix CVE-2013-6687, update to the latest version of Cisco Webex Meetings Server that addresses this issue.
Who is affected by CVE-2013-6687?
Any organization using Cisco Webex Meetings Server is at risk of CVE-2013-6687 if they do not have the proper security measures in place.
What type of attack vector does CVE-2013-6687 represent?
CVE-2013-6687 represents an information disclosure vulnerability, allowing remote authenticated users to view administrative passwords.
Are there any workarounds for CVE-2013-6687 until a patch is applied?
There are no recommended workarounds for CVE-2013-6687; applying the available patch is the best course of action.

agent/type
agent/softwarecombine
collector/mitre-cve
source/MITRE
agent/weakness
agent/last-modified-date
agent/severity
agent/references
agent/author
agent/description
agent/first-publish-date
agent/event
agent/source
agent/tags
collector/nvd-index
agent/software-canonical-lookup-request
vendor/cisco
canonical/cisco webex meetings server software

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-2013-6687?
CVE-2013-6687 is classified as a medium-severity vulnerability due to its potential impact on administrative credentials.
How do I fix CVE-2013-6687?
To fix CVE-2013-6687, update to the latest version of Cisco Webex Meetings Server that addresses this issue.
Who is affected by CVE-2013-6687?
Any organization using Cisco Webex Meetings Server is at risk of CVE-2013-6687 if they do not have the proper security measures in place.
What type of attack vector does CVE-2013-6687 represent?
CVE-2013-6687 represents an information disclosure vulnerability, allowing remote authenticated users to view administrative passwords.
Are there any workarounds for CVE-2013-6687 until a patch is applied?
There are no recommended workarounds for CVE-2013-6687; applying the available patch is the best course of action.