# CVE-1999-0472: Hardcoded credentials in n/a

> Attackers can access SNMP data because the default community string remains active despite administrator attempts to disable it.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Sep 1999
- **Updated:** 9 Oct 2026
- **Also known as:** GHSA-3866-98fq-wg7f

## What is CVE-1999-0472?

CVE-1999-0472 is a medium-severity vulnerability in n/a, published on 29 Sep 1999. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The SNMP default community name "public" is not properly removed in NetApps C630 Netcache, even if the administrator tries to disable it.

## Which versions are affected by CVE-1999-0472?

It affects 2 products.


Products: Network Appliance Netcache, Snmp Snmp.

## How do I fix CVE-1999-0472?

No fix has been published for CVE-1999-0472 yet. Limit exposure of the affected software until one is available.

## Is CVE-1999-0472 being exploited?

There is no known exploitation of CVE-1999-0472 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2001-1087](https://insights.sbomify.com/CVE-2001-1087/): Misconfiguration in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-1999-0472 and fix it if it is affected.

What it is: CVE-1999-0472 is a medium-severity vulnerability in n/a, published on 29 Sep 1999. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-1999-0472 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-1999-0472/ (Markdown: https://insights.sbomify.com/CVE-1999-0472/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-1999-0472
- NVD: https://nvd.nist.gov/vuln/detail/CVE-1999-0472
- OSV: https://osv.dev/vulnerability/CVE-1999-0472

---
From sbomify Insights: https://insights.sbomify.com/CVE-1999-0472/
Summaries are generated and may contain mistakes; the official description above is the record.