What is the severity of CVE-2016-6446?

CVE-2016-6446 has a high severity rating due to its potential to allow unauthorized access to sensitive memory data.

How do I fix CVE-2016-6446?

To fix CVE-2016-6446, update your Cisco Meeting Server to a patched version that addresses this vulnerability.

Who is affected by CVE-2016-6446?

CVE-2016-6446 affects users of Cisco Meeting Server versions 1.8, 1.9, and 2.0.

What is the impact of CVE-2016-6446?

The impact of CVE-2016-6446 includes the possibility for an unauthenticated attacker to retrieve sensitive memory information.

Is there a workaround for CVE-2016-6446?

Currently, there are no effective workarounds for CVE-2016-6446; therefore, patching is essential.

Vulnerability/
CVE-2016-6446

high

7.5

CWE

200

27/10/2016

6/8/2024

CVE-2016-6446: Infoleak

First published: Thu Oct 27 2016(Updated: )

A vulnerability in Web Bridge for Cisco Meeting Server could allow an unauthenticated, remote attacker to retrieve memory from a connected server. More Information: CSCvb03308. Known Affected Releases: 1.8, 1.9, 2.0.

Credit: ykramarz@cisco.com

Affected Software	Affected Version	How to fix
Cisco Meeting Server	=1.8.15
Cisco Meeting Server	=1.8_base
Cisco Meeting Server	=1.9.0
Cisco Meeting Server	=1.9.2
Cisco Meeting Server	=2.0.0
Cisco Meeting Server	=2.0.1
Cisco Meeting Server	=2.0.3
Cisco Meeting Server	=2.0.4
Cisco Meeting Server	=2.0.5

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2016-6446?
CVE-2016-6446 has a high severity rating due to its potential to allow unauthorized access to sensitive memory data.
How do I fix CVE-2016-6446?
To fix CVE-2016-6446, update your Cisco Meeting Server to a patched version that addresses this vulnerability.
Who is affected by CVE-2016-6446?
CVE-2016-6446 affects users of Cisco Meeting Server versions 1.8, 1.9, and 2.0.
What is the impact of CVE-2016-6446?
The impact of CVE-2016-6446 includes the possibility for an unauthenticated attacker to retrieve sensitive memory information.
Is there a workaround for CVE-2016-6446?
Currently, there are no effective workarounds for CVE-2016-6446; therefore, patching is essential.

collector/nvd-index
agent/references
agent/type
agent/softwarecombine
collector/mitre-cve
source/MITRE
agent/author
agent/last-modified-date
agent/severity
agent/weakness
agent/event
agent/first-publish-date
agent/description
agent/trending
agent/tags
agent/source
vendor/cisco
canonical/cisco meeting server
version/cisco meeting server/1.8.15
version/cisco meeting server/1.8_base
version/cisco meeting server/1.9.0
version/cisco meeting server/1.9.2
version/cisco meeting server/2.0.0
version/cisco meeting server/2.0.1
version/cisco meeting server/2.0.3
version/cisco meeting server/2.0.4
version/cisco meeting server/2.0.5

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-2016-6446?
CVE-2016-6446 has a high severity rating due to its potential to allow unauthorized access to sensitive memory data.
How do I fix CVE-2016-6446?
To fix CVE-2016-6446, update your Cisco Meeting Server to a patched version that addresses this vulnerability.
Who is affected by CVE-2016-6446?
CVE-2016-6446 affects users of Cisco Meeting Server versions 1.8, 1.9, and 2.0.
What is the impact of CVE-2016-6446?
The impact of CVE-2016-6446 includes the possibility for an unauthenticated attacker to retrieve sensitive memory information.
Is there a workaround for CVE-2016-6446?
Currently, there are no effective workarounds for CVE-2016-6446; therefore, patching is essential.