What is the severity of CVE-2001-0549?

CVE-2001-0549 is considered a moderate severity vulnerability due to the potential for local users to obtain sensitive proxy passwords.

How do I fix CVE-2001-0549?

To fix CVE-2001-0549, it is recommended to upgrade to a version of Symantec LiveUpdate that does not store proxy passwords in cleartext.

Who is affected by CVE-2001-0549?

CVE-2001-0549 affects users of Symantec LiveUpdate version 1.5.

What does CVE-2001-0549 expose to local users?

CVE-2001-0549 exposes proxy passwords stored in cleartext in a registry key to local users.

Is there a workaround for CVE-2001-0549?

A temporary workaround for CVE-2001-0549 includes restricting access to the registry keys where the proxy passwords are stored.

Vulnerability/
CVE-2001-0549

medium

4.6

CWE

NVD-CWE-Other

14/8/2001

9/3/2002

8/8/2024

CVE-2001-0549

First published: Tue Aug 14 2001(Updated: )

Symantec LiveUpdate 1.5 stores proxy passwords in cleartext in a registry key, which could allow local users to obtain the passwords.

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
Symantec LiveUpdate	=1.5

Remedy

http://www.kb.cert.org/vuls/id/814187

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2001-0549?
CVE-2001-0549 is considered a moderate severity vulnerability due to the potential for local users to obtain sensitive proxy passwords.
How do I fix CVE-2001-0549?
To fix CVE-2001-0549, it is recommended to upgrade to a version of Symantec LiveUpdate that does not store proxy passwords in cleartext.
Who is affected by CVE-2001-0549?
CVE-2001-0549 affects users of Symantec LiveUpdate version 1.5.
What does CVE-2001-0549 expose to local users?
CVE-2001-0549 exposes proxy passwords stored in cleartext in a registry key to local users.
Is there a workaround for CVE-2001-0549?
A temporary workaround for CVE-2001-0549 includes restricting access to the registry keys where the proxy passwords are stored.

collector/nvd-historical
collector/nvd-index
agent/type
agent/softwarecombine
agent/first-publish-date
collector/mitre-cve
source/MITRE
agent/author
agent/remedy
agent/references
agent/weakness
agent/last-modified-date
agent/severity
agent/tags
agent/description
agent/event
agent/source
vendor/symantec
canonical/symantec liveupdate
version/symantec liveupdate/1.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-2001-0549?
CVE-2001-0549 is considered a moderate severity vulnerability due to the potential for local users to obtain sensitive proxy passwords.
How do I fix CVE-2001-0549?
To fix CVE-2001-0549, it is recommended to upgrade to a version of Symantec LiveUpdate that does not store proxy passwords in cleartext.
Who is affected by CVE-2001-0549?
CVE-2001-0549 affects users of Symantec LiveUpdate version 1.5.
What does CVE-2001-0549 expose to local users?
CVE-2001-0549 exposes proxy passwords stored in cleartext in a registry key to local users.
Is there a workaround for CVE-2001-0549?
A temporary workaround for CVE-2001-0549 includes restricting access to the registry keys where the proxy passwords are stored.