What is the severity of CVE-2002-1117?

The severity of CVE-2002-1117 is considered high due to its potential to expose sensitive information.

How do I fix CVE-2002-1117?

To fix CVE-2002-1117, change the 'RestrictAnonymous' registry key for Microsoft Exchange 2000 to 1.

Which versions of Veritas Backup Exec are affected by CVE-2002-1117?

CVE-2002-1117 affects all versions of Veritas Backup Exec up to and including 8.5.

What risks are associated with CVE-2002-1117?

The risks associated with CVE-2002-1117 include unauthorized access to the SAM database and shared resources.

Is there a patch available for CVE-2002-1117?

There is no specific patch for CVE-2002-1117, but configuration changes can mitigate the vulnerability.

Vulnerability/
CVE-2002-1117

medium

CWE

NVD-CWE-Other

4/10/2002

1/9/2004

8/8/2024

CVE-2002-1117

First published: Fri Oct 04 2002(Updated: )

Veritas Backup Exec 8.5 and earlier requires that the "RestrictAnonymous" registry key for Microsoft Exchange 2000 must be set to 0, which enables anonymous listing of the SAM database and shares.

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
Symantec Veritas Backup Exec	<=8.5

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2002-1117?
The severity of CVE-2002-1117 is considered high due to its potential to expose sensitive information.
How do I fix CVE-2002-1117?
To fix CVE-2002-1117, change the 'RestrictAnonymous' registry key for Microsoft Exchange 2000 to 1.
Which versions of Veritas Backup Exec are affected by CVE-2002-1117?
CVE-2002-1117 affects all versions of Veritas Backup Exec up to and including 8.5.
What risks are associated with CVE-2002-1117?
The risks associated with CVE-2002-1117 include unauthorized access to the SAM database and shared resources.
Is there a patch available for CVE-2002-1117?
There is no specific patch for CVE-2002-1117, but configuration changes can mitigate the vulnerability.

collector/nvd-historical
collector/nvd-index
agent/references
agent/type
agent/first-publish-date
agent/softwarecombine
collector/mitre-cve
source/MITRE
agent/weakness
agent/severity
agent/author
agent/last-modified-date
agent/description
agent/tags
agent/event
agent/source
vendor/symantec veritas
canonical/symantec veritas backup exec
version/symantec veritas backup exec/8.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-2002-1117?
The severity of CVE-2002-1117 is considered high due to its potential to expose sensitive information.
How do I fix CVE-2002-1117?
To fix CVE-2002-1117, change the 'RestrictAnonymous' registry key for Microsoft Exchange 2000 to 1.
Which versions of Veritas Backup Exec are affected by CVE-2002-1117?
CVE-2002-1117 affects all versions of Veritas Backup Exec up to and including 8.5.
What risks are associated with CVE-2002-1117?
The risks associated with CVE-2002-1117 include unauthorized access to the SAM database and shared resources.
Is there a patch available for CVE-2002-1117?
There is no specific patch for CVE-2002-1117, but configuration changes can mitigate the vulnerability.