CVE-1999-0517: Infoleak
An SNMP community name is the default (e.g. public), null, or missing.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Configuration
Configure the SNMP agent to use a non-default, non-empty community name (do not leave it null or missing and do not use the default 'public'). Ensure the configured community string is applied for the relevant SNMP service on the affected hosts.
SNMP on HPE HP-UX and SunOS community name = non-default, non-empty (not 'public')
Event History
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.