CVE-2000-0300: Weak Encryption

Published Apr 6, 2000
·
Updated

The default encryption method of PcAnywhere 9.x uses weak encryption, which allows remote attackers to sniff and decrypt PcAnywhere or NT domain accounts.

Affected Software

1 affected component
Symantec pcAnywhere=9.0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Remove

    Remove Symantec pcAnywhere from your environment.

    Uninstall pcAnywhere if remote access functionality is not required to eliminate exposure to the weak-default-encryption vulnerability.

  2. Configuration

    Change pcAnywhere's default encryption method in the product configuration to disable the weak default algorithm and enable a stronger encryption option if available.

    Symantec pcAnywhere encryption method (default) = disable default weak encryption / use a stronger encryption method
  3. Compensating control

    Restrict network exposure of pcAnywhere services using firewall rules, access control lists, or require access via a trusted VPN to prevent remote attackers from sniffing traffic.

  4. Operational

    Rotate PcAnywhere and any affected NT domain account credentials that may have been exposed or decrypted before applying configuration changes or removal.

Event History

Apr 6, 2000
CVE Published
04:00 AM
Data Sourced
via NVD·04:00 AM
RemedyDescriptionSeverityAffected Software
Apr 26, 2000
CVE Published
via MITRE·08:00 AM
Data Sourced
via MITRE·08:00 AM
Description

Frequently Asked Questions

1

What is the severity of CVE-2000-0300?

The severity of CVE-2000-0300 is considered high due to the use of weak encryption methods.

2

How do I fix CVE-2000-0300?

To fix CVE-2000-0300, upgrade to a newer version of PcAnywhere that uses stronger encryption methods.

3

What versions of PcAnywhere are affected by CVE-2000-0300?

CVE-2000-0300 specifically affects Symantec PcAnywhere version 9.0.

4

What types of attacks can exploit CVE-2000-0300?

CVE-2000-0300 can be exploited by remote attackers to sniff and decrypt account credentials.

5

Is there a workaround for CVE-2000-0300?

A temporary workaround for CVE-2000-0300 is to avoid using the default encryption method and switch to more secure options if available.

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.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203