# CVE-2004-1970: Auth bypass in n/a

> Remote attackers can gain administrative access to Samsung SmartEther switches by exploiting a flaw in the login error handling process.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 10 May 2005
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-crm6-w28g-73jf

## What is CVE-2004-1970?

CVE-2004-1970 is a high-severity authentication bypass vulnerability in n/a, published on 10 May 2005. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Samsung SmartEther SS6215S switch, and possibly other Samsung switches, allows remote attackers and local users to gain administrative access by providing the admin username followed by a password that is the maximum allowed length, then pressing the enter key after the resulting error message.

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

It affects 1 product.


Products: Securecomputing Smartether Ss6215s Switch.

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

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

## Is CVE-2004-1970 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2004-1970 is a high-severity authentication bypass vulnerability in n/a, published on 10 May 2005. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2004-1970 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-1970/ (Markdown: https://insights.sbomify.com/CVE-2004-1970/index.md)
```

## Sources

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

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