CVE-2012-1803 is a hard-coded 'factory' account in RuggedCom ROS 3.10.x and earlier. The password is derived from the device's MAC address, which the login banner displays, so anyone who sees the banner can calculate it and log in over Telnet, rsh or the serial console. NVD scores it 8.5 under CVSS v2. ROS 3.10.1, 3.9.3, 3.8.5 and 3.7.9 remove the account.
Vulnerability summary
CVSS base score
8.5
High severity
EPSS score (FIRST)
48.9%
Probability of exploitation in the wild in the next 30 days
CISA KEV catalog
No
Not listed
Published
Vulnerability ID: CVE-2012-1803 · Source: NVD
Affected components
| Component | CPE | Version range |
|---|---|---|
| RuggedCom Rugged Operating System (ROS), now Siemens RUGGEDCOM ROS, on RuggedCom switches and serial device servers | cpe:2.3:o:siemens:ruggedcom_rugged_operating_system:*:*:*:*:*:*:*:* | 3.10.x and earlier; fixed in ROS 3.10.1, 3.9.3, 3.8.5 and 3.7.9, and in 3.11.0 and later (CERT/CC VU#889195, CISA ICSA-12-146-01A). NVD's CPE covers 3.2.0 up to and including 3.10.1 |
What does this mean for affected devices?
NVD describes the flaw this way: "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." NVD's Primary score is CVSS v2 8.5 (AV:N/AC:M/Au:S/C:C/I:C/A:C) with CWE-310 (cryptographic issues). The record was published on 2012-04-28, with CERT/CC as the assigner (NVD, CVE record).
How does the factory account work?
CERT/CC's note VU#889195 explains the mechanics. ROS, which runs on RuggedCom network devices, has a hard-coded user account named "factory" that cannot be disabled. Its password is based on the device's MAC address and can easily be reverse engineered, and the MAC address is printed in the banner before login. In ROS 3.3.x the HTTP(S) and SSH services do not use the factory account, but Telnet, rsh and the serial console do. ROS does not appear to log successful or failed logins with the factory account. According to CERT/CC, an attacker who knows the MAC address may be able to gain complete administrative control of the device. CISA classes the weakness CWE-261 (weak encoding for password) in its advisory.
CERT/CC lists both RuggedCom and Siemens as affected vendors, and NVD's CPE now files the product under Siemens. CVE-2012-1803 is not in the CISA KEV catalog as of 2026-11-21 (catalog version 2026.11.20, 1,790 entries). FIRST EPSS gives it 0.48882, the 98.9th percentile, in the 2026-11-20 dataset. That is high for an ICS flaw (CISA KEV, FIRST EPSS).
Which versions are affected and fixed?
| ROS version | Status |
|---|---|
| 3.10.x and earlier | affected |
| 3.10.1, 3.9.3, 3.8.5, 3.7.9 | fixed, factory account removed |
| 3.11.0 and later | fixed |
| older than 3.7 | RuggedCom recommended an upgrade and offered updates for older firmware case by case |
According to the CISA advisory, the fixed releases do more than remove the factory account. They also turn insecure communication services off by default, store user passwords more securely, warn about weak passwords and remove device information from the login banner. CISA adds a warning: because the factory account is gone, recovering a lost administrator password now needs physical access to the device (CISA ICSA-12-146-01A CSAF). NVD's CPE range runs up to and including 3.10.1, while CERT/CC and CISA say 3.10.1 is fixed. Follow the CERT/CC and CISA statements.
How do you fix or mitigate it?
Update ROS to 3.10.1, 3.9.3, 3.8.5 or 3.7.9 or later; any current RUGGEDCOM ROS release is far beyond these. For devices that cannot be updated, CERT/CC notes that ROS 3.3.x lets you disable rsh and set the number of allowed Telnet connections to 0. ROS 3.2.x cannot disable either service. In every case, block Telnet and rsh to the device and protect physical access to the serial console.
Later ROS releases have their own advisories, including the DHCP client overflow CVE-2021-31895 and the mirror-port flaw CVE-2023-24845. Our SCALANCE and RUGGEDCOM vulnerability guide covers the range, and the hard-coded credentials fix guide explains this class of flaw.
Evidence
- NVD (read 2026-11-21): status Modified; published 2012-04-28; NVD Primary CVSS v2 8.5 AV:N/AC:M/Au:S/C:C/I:C/A:C; no CVSS v3 metric; CWE-310; CPE cpe:2.3:o:siemens:ruggedcom_rugged_operating_system from 3.2.0 up to and including 3.10.1; references ICSA-12-146-01A, VU#889195, ICS-ALERT-12-116-01A. — NVD
- CERT/CC VU#889195 (read 2026-11-21): ROS contains a hard-coded user account named factory that cannot be disabled; its password is based on the MAC address shown in the pre-authentication banner; in ROS 3.3.x HTTP(S) and ssh do not use the factory account; factory logins do not appear to be logged; an attacker may gain complete administrative control; fixed in ROS 3.10.1, 3.9.3, 3.8.5, 3.7.9 and 3.11.0; ROS 3.3.x can disable rsh and set Telnet connections to 0, ROS 3.2.x cannot. — CERT/CC
- CISA CSAF ICSA-12-146-01A (RuggedCom Weak Cryptography for Password Vulnerability, version 2), read 2026-11-21: CVE-2012-1803, CWE-261, CVSS v2 8.5; ROS 3.10.1, 3.9.3, 3.8.5 and 3.7.9 available, 3.11.x to follow; fixed releases remove the factory account, disable insecure services by default, improve password storage, detect weak passwords and remove device information from the banner; lost administrator passwords then need physical access; versions older than 3.7 handled case by case; references Siemens SSA-826381. — CISA ICS advisory (CSAF)
- CVE record (checked 2026-11-21): state PUBLISHED, assigner CERT/CC, published 2012-04-28; no CNA CVSS metric or CWE. — CVE.org
- Not in the CISA KEV catalog, version 2026.11.20 (1,790 entries), checked 2026-11-21. — CISA KEV
- EPSS 0.48882, percentile 0.98907, dataset 2026-11-20, read 2026-11-21. — FIRST EPSS

Related advisories
Sources
Frequently asked questions
Which ROS versions remove the factory account?
ROS 3.10.1, 3.9.3, 3.8.5 and 3.7.9, and 3.11.0 and later, according to CERT/CC VU#889195 and CISA ICSA-12-146-01A. NVD's CPE range includes 3.10.1, but both CERT/CC and CISA state that 3.10.1 is no longer affected.
Which services can the factory account log in to?
Telnet, rsh and the serial console, per NVD and CERT/CC. In ROS 3.3.x the HTTP(S) and SSH services do not use the factory account. Successful and failed factory logins do not appear to be logged, so device logs will not show its use.
How do I protect a device that cannot be updated?
On ROS 3.3.x, disable rsh and set the number of allowed Telnet connections to 0, as CERT/CC describes. ROS 3.2.x cannot disable these services, so block Telnet and rsh to the device on the network and control physical access to the serial port.
What changes after the update?
The factory account is gone, insecure services are disabled by default and the banner no longer shows device details. Because there is no factory account, CISA warns that recovering a lost administrator password requires physical access to the device.
Questions about this page?