Menu

Star on GitHub · 3.2k

CVE-2002-0345

7.5 · HIGH

Symantec Ghost 7.0 stores usernames and passwords in plaintext in the NGServer\params registry key, which could allow an attacker to gain privileges.

Published Jun 25, 2002symantecEPSS 1.64%

Overview

CVE-2002-0345 is a high-severity vulnerability affecting symantec norton_ghost. It was published on June 25, 2002 and has a CVSS 2.0 base score of 7.5 (HIGH).

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

Technical description

Symantec Ghost 7.0 stores usernames and passwords in plaintext in the NGServer\params registry key, which could allow an attacker to gain privileges.

Remediation

Check the references section for vendor advisories and patches from symantec. Update norton_ghost 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-0345?

CVE-2002-0345 is a high-severity vulnerability affecting symantec norton_ghost. It was published on June 25, 2002 and has a CVSS 2.0 base score of 7.5 (HIGH).

How severe is CVE-2002-0345?

This vulnerability has a CVSS 2.0 base score of 7.5, 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-0345?

Check the references section for vendor advisories and patches from symantec. Update norton_ghost 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-0345?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2002-0345 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