# CVE-2004-1976: Misconfiguration in n/a

> Remote attackers can gain unauthorized access to SMC Barricade routers because remote administration is enabled by default on port 1900.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 May 2005
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-7pjp-26r9-pjjc

## What is CVE-2004-1976?

CVE-2004-1976 is a high-severity vulnerability in n/a, published on 10 May 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

SMC Barricade broadband router 7008ABR and 7004VBR enable remote administration by default, which allows remote attackers to gain access by connecting to port 1900.

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

It affects 1 product.


Products: Smc Networks Smc7004vbr.

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

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

## Is CVE-2004-1976 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2004-1976 is a high-severity vulnerability in n/a, published on 10 May 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-1976 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-1976/ (Markdown: https://insights.sbomify.com/CVE-2004-1976/index.md)
```

## Sources

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

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