What is the severity of CVE-1999-0517?

CVE-1999-0517 is classified as a high severity vulnerability due to potential unauthorized access.

How do I fix CVE-1999-0517?

To fix CVE-1999-0517, change the default SNMP community names from 'public' to a more secure value.

What systems are affected by CVE-1999-0517?

CVE-1999-0517 affects HPE HP-UX versions 10.00 and 11.00, as well as Sun SunOS version 5.0.

What are the risks of leaving CVE-1999-0517 unaddressed?

Leaving CVE-1999-0517 unaddressed can allow attackers to gain unauthorized access to sensitive network management information.

Is CVE-1999-0517 a known vulnerability?

Yes, CVE-1999-0517 is a well-known vulnerability that has been documented and recognized since its publication.

Vulnerability/
CVE-1999-0517

high

7.5

CWE

NVD-CWE-Other

1/1/1997

4/2/2000

20/11/2024

CVE-1999-0517

First published: Wed Jan 01 1997(Updated: )

An SNMP community name is the default (e.g. public), null, or missing.

Credit: cve@mitre.org cve@mitre.org

Affected Software	Affected Version	How to fix
HPE HP-UX	=11.00
HPE HP-UX	=10
Sun SunOS	=5.0

Never miss a vulnerability like this again

Reference Links

https://exchange.xforce.ibmcloud.com/vulnerabilities/CVE-1999-0517

Frequently Asked Questions

What is the severity of CVE-1999-0517?
CVE-1999-0517 is classified as a high severity vulnerability due to potential unauthorized access.
How do I fix CVE-1999-0517?
To fix CVE-1999-0517, change the default SNMP community names from 'public' to a more secure value.
What systems are affected by CVE-1999-0517?
CVE-1999-0517 affects HPE HP-UX versions 10.00 and 11.00, as well as Sun SunOS version 5.0.
What are the risks of leaving CVE-1999-0517 unaddressed?
Leaving CVE-1999-0517 unaddressed can allow attackers to gain unauthorized access to sensitive network management information.
Is CVE-1999-0517 a known vulnerability?
Yes, CVE-1999-0517 is a well-known vulnerability that has been documented and recognized since its publication.

agent/type
agent/first-publish-date
collector/mitre-cve
source/MITRE
agent/severity
agent/weakness
agent/references
agent/description
agent/last-modified-date
agent/author
agent/softwarecombine
agent/event
agent/source
agent/tags
collector/nvd-historical
agent/software-canonical-lookup-request
collector/nvd-index
collector/nvd-api
source/NVD
agent/software-canonical-lookup
vendor/hp
canonical/hpe hp-ux
version/hpe hp-ux/11.00
version/hpe hp-ux/10
vendor/sun
canonical/sun sunos
version/sun sunos/5.0

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-1999-0517?
CVE-1999-0517 is classified as a high severity vulnerability due to potential unauthorized access.
How do I fix CVE-1999-0517?
To fix CVE-1999-0517, change the default SNMP community names from 'public' to a more secure value.
What systems are affected by CVE-1999-0517?
CVE-1999-0517 affects HPE HP-UX versions 10.00 and 11.00, as well as Sun SunOS version 5.0.
What are the risks of leaving CVE-1999-0517 unaddressed?
Leaving CVE-1999-0517 unaddressed can allow attackers to gain unauthorized access to sensitive network management information.
Is CVE-1999-0517 a known vulnerability?
Yes, CVE-1999-0517 is a well-known vulnerability that has been documented and recognized since its publication.