CVE-1999-0472
First published: Wed Apr 07 1999(Updated: )
The SNMP default community name "public" is not properly removed in NetApps C630 Netcache, even if the administrator tries to disable it.
Credit: cve@mitre.org cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Snmp Snmp | ||
| Network Appliance NetCache | ||
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Frequently Asked Questions
What is the severity of CVE-1999-0472?
CVE-1999-0472 is considered a moderate severity vulnerability due to the potential for unauthorized access.
How do I fix CVE-1999-0472?
To fix CVE-1999-0472, ensure that the default SNMP community name 'public' is removed and not just disabled.
What systems are affected by CVE-1999-0472?
CVE-1999-0472 affects Network Appliance NetCache systems and SNMP implementations.
Can CVE-1999-0472 lead to data breaches?
Yes, CVE-1999-0472 can lead to data breaches if the default community string is exploited.
Is CVE-1999-0472 still relevant today?
Yes, CVE-1999-0472 remains relevant as legacy systems with default configurations can still be found in use.
- collector/nvd-historical
- collector/nvd-index
- agent/type
- agent/first-publish-date
- collector/mitre-cve
- source/MITRE
- agent/severity
- agent/weakness
- agent/references
- agent/description
- collector/nvd-api
- source/NVD
- agent/software-canonical-lookup
- agent/last-modified-date
- agent/author
- agent/softwarecombine
- agent/event
- agent/tags
- agent/source
- vendor/snmp
- canonical/snmp snmp
- vendor/network appliance
- canonical/network appliance netcache