# CVE-2005-3718: Misconfiguration in n/a

> Remote attackers can execute arbitrary shell commands via unauthenticated rlogin or exploit SNMP due to inability to disable these services on the device.

- **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:** 21 Nov 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-pmmj-9c47-7652

## What is CVE-2005-3718?

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

### Official description

UTStarcom F1000 VOIP WIFI Phone s2.0 running VxWorks 5.5.1 with kernel WIND 2.6 does not allow users to disable access to (1) SNMP or (2) the rlogin port TCP 513, which allows remote attackers to exploit other vulnerabilities such as CVE-2005-3716, or execute arbitrary shell commands via rlogin, which does not require authentication.

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

It affects 1 product.


Products: Utstarcom F1000 Voip Wifi Phone.

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

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

## Is CVE-2005-3718 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2005-3717](https://insights.sbomify.com/CVE-2005-3717/): Hardcoded credentials in n/a (high 7.5)

## Fix prompt for AI coding agents

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

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

## Sources

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

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