Security readout for executives and security teams
Plain-English summary
This old CVE describes a NetApps C630 Netcache issue where the default SNMP community name "public" may remain usable even after an administrator tries to disable it. That can leave management information exposed on affected legacy devices.
Executive priority
Treat this as a legacy exposure review item, not a confirmed emergency. Prioritize it if affected devices are internet-reachable, manage sensitive networks, or cannot be patched or replaced.
Technical view
The vulnerability concerns improper removal of the SNMP default community string "public" on NetApps C630 Netcache. The source bundle provides no CVSS score, CWE, vendor patch details, or precise affected version range beyond the product named in the description.
Likely exposure
Exposure is most plausible in organizations still operating legacy NetApps C630 Netcache devices with SNMP enabled, especially if SNMP is reachable outside a tightly controlled management network.
Exploitation context
The bundle does not show CISA KEV listing or cited evidence of active exploitation. The risk is still operationally relevant because "public" is a widely known SNMP default community name.
Researcher notes
Evidence is sparse. The CVE description is specific about the default SNMP community persistence, but the bundle lacks CVSS, CWE, affected versions, patch status, and exploit confirmation.
Mitigation direction
- Identify any NetApps C630 Netcache assets still in service.
- Check vendor or archival guidance for supported fixes or replacement direction.
- Restrict SNMP access to trusted management hosts only.
- Disable SNMP where it is not operationally required.
- Remove or isolate unsupported legacy devices when controls cannot be verified.
Validation and detection
- Inventory network devices for NetApps C630 Netcache systems.
- Review SNMP configuration for any active "public" community use.
- Confirm SNMP is blocked from untrusted networks.
- Check monitoring logs for unexpected SNMP access attempts.
- Document whether a vendor-supported fix exists for each affected asset.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CVE-1999-0472 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://exchange.xforce.ibmcloud.com/vulnerabilities/CVE-1999-0472CVE reference · x_refsource_MISC
- https://www.broadcom.com/support/fibre-channel-networking/security-advisories/brocade-security-advisory-2017-240CVE reference
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.