# CVE-2004-1474: Hardcoded credentials in n/a

> Remote attackers can modify firewall configuration using default SNMP credentials, requiring firmware upgrades to mitigate.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:P/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:** 13 Feb 2005
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-fgq9-ggr2-vg42

## What is CVE-2004-1474?

CVE-2004-1474 is a medium-severity vulnerability in n/a, published on 13 Feb 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Symantec Enterprise Firewall/VPN Appliances 100, 200, and 200R running firmware before 1.63 and Gateway Security 320, 360, and 360R running firmware before 622 uses a default read/write SNMP community string, which allows remote attackers to alter the firewall's configuration file.

## Which versions are affected by CVE-2004-1474?

It affects 12 products.


Products: Symantec Firewall Vpn Appliance 100, Symantec Firewall Vpn Appliance 200, Symantec Firewall Vpn Appliance 200r, Symantec Gateway Security 320, Symantec Gateway Security 360, Symantec Gateway Security 360r, Symantec Nexland Isb Soho Firewall Appliance, Symantec Nexland Pro100 Firewall Appliance, Symantec Nexland Pro400 Firewall Appliance, Symantec Nexland Pro800 Firewall Appliance, Symantec Nexland Pro800turbo Firewall Appliance, Symantec Nexland Wavebase Firewall Appliance.

## How do I fix CVE-2004-1474?

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

## Is CVE-2004-1474 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2004-0190](https://insights.sbomify.com/CVE-2004-0190/): Information disclosure in n/a (high 7.5)
- [CVE-2002-1937](https://insights.sbomify.com/CVE-2002-1937/): Hardcoded credentials in n/a (medium 5.0)
- [CVE-2004-1472](https://insights.sbomify.com/CVE-2004-1472/): Denial of service in n/a (medium 5.0)
- [CVE-2004-1473](https://insights.sbomify.com/CVE-2004-1473/): Information disclosure in n/a (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2004-1474 and fix it if it is affected.

What it is: CVE-2004-1474 is a medium-severity vulnerability in n/a, published on 13 Feb 2005. 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-2004-1474 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-2004-1474/ (Markdown: https://insights.sbomify.com/CVE-2004-1474/index.md)
```

## Sources

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

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