Menu

Star on GitHub · 3.2k

CVE-2002-0626

10.0 · HIGH

Polycom ViewStation before 7.2.4 has a default null password for the administrator account, which allows arbitrary users to conduct unauthorized activities.

Published Jan 7, 2003polycomEPSS 1.80%

Overview

CVE-2002-0626 is a high-severity vulnerability affecting polycom viewstation_128. It was published on January 7, 2003 and has a CVSS 2.0 base score of 10.0 (HIGH).

This vulnerability has a CVSS 2.0 base score of 10.0, rated HIGH. It can be exploited remotely over the network. No authentication or special privileges are required for exploitation.

Technical description

Polycom ViewStation before 7.2.4 has a default null password for the administrator account, which allows arbitrary users to conduct unauthorized activities.

Remediation

Check the references section for vendor advisories and patches from polycom. Update viewstation_128 to the latest patched version. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Affected products

VendorProductVersionsStatus

Frequently asked questions

What is CVE-2002-0626?

CVE-2002-0626 is a high-severity vulnerability affecting polycom viewstation_128. It was published on January 7, 2003 and has a CVSS 2.0 base score of 10.0 (HIGH).

How severe is CVE-2002-0626?

This vulnerability has a CVSS 2.0 base score of 10.0, rated HIGH. It can be exploited remotely over the network. No authentication or special privileges are required for exploitation.

How do I fix or remediate CVE-2002-0626?

Check the references section for vendor advisories and patches from polycom. Update viewstation_128 to the latest patched version. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2002-0626?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2002-0626 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related HIGH CVEs from 2002

View all