# CVE-2005-2424: Auth bypass in n/a

> Remote attackers can bypass authentication to access the Telnet port on Siemens SANTIS routers by sending specific packets to the web interface.

- **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:** 3 Aug 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-962g-hj9f-64vg

## What is CVE-2005-2424?

CVE-2005-2424 is a high-severity authentication bypass vulnerability in n/a, published on 3 Aug 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The management interface for Siemens SANTIS 50 running firmware 4.2.8.0, and possibly other products including Ericsson HN294dp and Dynalink RTA300W, allows remote attackers to access the Telnet port without authentication via certain packets to the web interface that cause the interface to freeze.

## Which versions are affected by CVE-2005-2424?

It affects 1 product.


Products: Siemens Santis 50.

## How do I fix CVE-2005-2424?

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

## Is CVE-2005-2424 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2005-2424 and fix it if it is affected.

What it is: CVE-2005-2424 is a high-severity authentication bypass vulnerability in n/a, published on 3 Aug 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-2005-2424 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-2005-2424/ (Markdown: https://insights.sbomify.com/CVE-2005-2424/index.md)
```

## Sources

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

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