CVE-2016-5673
First published: Thu Aug 25 2016(Updated: )
UltraVNC Repeater before 1300 does not restrict destination IP addresses or TCP ports, which allows remote attackers to obtain open-proxy functionality by using a :: substring in between the IP address and port number.
Credit: cret@cert.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| UltraVNC | <=1201 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2016-5673?
CVE-2016-5673 is classified as a medium severity vulnerability due to its potential for exposing systems to unauthorized proxy access.
How do I fix CVE-2016-5673?
To fix CVE-2016-5673, upgrade UltraVNC Repeater to version 1300 or later, which includes necessary restrictions on destination IP addresses and TCP ports.
What types of attacks can exploit CVE-2016-5673?
CVE-2016-5673 can be exploited by remote attackers to establish open-proxy functionality through malformed IP address and port configurations.
What are the potential impacts of CVE-2016-5673?
The potential impacts of CVE-2016-5673 include unauthorized access to internal networks and the ability to use the vulnerable machine as a proxy.
Which versions of UltraVNC are affected by CVE-2016-5673?
CVE-2016-5673 affects UltraVNC Repeater versions prior to 1300.
- agent/type
- agent/softwarecombine
- collector/mitre-cve
- source/MITRE
- agent/severity
- agent/weakness
- agent/references
- agent/last-modified-date
- agent/author
- agent/first-publish-date
- agent/description
- agent/event
- agent/source
- agent/tags
- collector/nvd-index
- agent/software-canonical-lookup-request
- vendor/ultravnc
- canonical/ultravnc
- version/ultravnc/1201