CVE-1999-0472
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe SNMP default community name "public" is not properly removed in NetApps C630 Netcache, even if the administrator tries to disable it.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe NetApps C630 Netcache device ships with the default SNMP community name 'public' enabled, and this default community string cannot be properly disabled even when the administrator attempts to remove it. This leaves the device vulnerable to unauthorized SNMP queries that can reveal system information, network configuration, and other sensitive details.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE dataall versionsall versionsCVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- None
- Availability
- None
AV:N/AC:L/Au:N/C:P/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify the device modelDetermine if the target system is a Network Appliance Netcache C630 or similar NetApp Netcache device. Check the device management interface, firmware banner, or system information for the model identification.Affected if The device is a Network Appliance Netcache C630 or other NetApp Netcache hardware.
-
Verify SNMP service statusCheck if SNMP is enabled on the device. On NetApp Netcache devices, this is typically configured under the SNMP or system management settings in the web interface or via CLI command 'snmp status' or 'snmp show'.Affected if SNMP service is running or enabled on the Netcache device.
-
Test default community string accessibilitySend an SNMP query using the community string 'public' to the device on UDP port 161. Use a tool like snmpwalk (e.g., snmpwalk -v2c -c public <device_ip> system) or snmpget to probe the device.Affected if The SNMP query with community string 'public' successfully returns system information, network configuration, or other OID data.
-
Confirm community string removal failsAttempt to remove or disable the 'public' community string through the device management interface or CLI. Check if the community string persists or becomes re-enabled after removal attempts.Affected if The 'public' community string cannot be permanently disabled or removed, or reappears after being deleted.
If the device is a NetApp Netcache with SNMP enabled and the default community string 'public' responds to queries and persists despite removal attempts, the environment is affected by CVE-1999-0472.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataRestrict SNMP access at the network perimeter using ACLs or firewall rules to block external UDP port 161 traffic, or upgrade to a firmware version that properly supports disabling the default community string.
- Consultation2.0 h
- Implementation2.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-1999-0472 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-1999-0472 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data