# CVE-2012-1803: Hardcoded credentials in n/a

> Remote attackers can gain administrative access to RuggedCom devices by calculating the factory account password from the MAC address.

- **Severity:** High 8.5 (`AV:N/AC:M/Au:S/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Apr 2012
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-qgxr-qjc2-5hqj

## What is CVE-2012-1803?

CVE-2012-1803 is a high-severity vulnerability in n/a, published on 28 Apr 2012. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

RuggedCom Rugged Operating System (ROS) 3.10.x and earlier has a factory account with a password derived from the MAC Address field in the banner, which makes it easier for remote attackers to obtain access by performing a calculation on this address value, and then establishing a (1) TELNET, (2) remote shell (aka rsh), or (3) serial-console session.

Weakness: CWE-310

## Which versions are affected by CVE-2012-1803?

It affects 1 product.


Products: Siemens Ruggedcom Rugged Operating System.

## How do I fix CVE-2012-1803?

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

## Is CVE-2012-1803 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2012-1803 exists.

Public exploit code:

- RuggedCom Devices - Backdoor Access (exploitdb)
- Critical vulnerability in Siemens RuggedCom ROS devices allowing attackers to derive a hidden factory account password from the device MAC address and gain unauthorized administrative access via TELNET, rsh, or serial interfaces. Affects ROS 3.10.x and earlier. (github_poc): https://github.com/x3roxismygood/CVE-2012-1803
- RuggedCom Telnet Password Generator (metasploit)

## Other vulnerabilities in n/a

- [CVE-2012-2441](https://insights.sbomify.com/CVE-2012-2441/): Hardcoded credentials in n/a (high 8.5)
- [CVE-2013-6925](https://insights.sbomify.com/CVE-2013-6925/): Other in n/a (high 8.3)
- [CVE-2013-6926](https://insights.sbomify.com/CVE-2013-6926/): Privilege escalation in n/a (high 8.0)
- [CVE-2014-1966](https://insights.sbomify.com/CVE-2014-1966/): Denial of service in n/a (high 7.8)
- [CVE-2014-2590](https://insights.sbomify.com/CVE-2014-2590/): Denial of service in n/a (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2012-1803 and fix it if it is affected.

What it is: CVE-2012-1803 is a high-severity vulnerability in n/a, published on 28 Apr 2012. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2012-1803 exists.

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-2012-1803/ (Markdown: https://insights.sbomify.com/CVE-2012-1803/index.md)
```

## Sources

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

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