{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2012-1803 exists.","fix":"No fix has been published for CVE-2012-1803 yet. Limit exposure of the affected software until one is available.","what":"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."},"fix_prompt":"Check this codebase for CVE-2012-1803 and fix it if it is affected.\n\nWhat 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.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2012-1803 exists.\n\nAffected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2012-1803/ (Markdown: https://insights.sbomify.com/CVE-2012-1803/index.md)","id":"CVE-2012-1803","markdown":"https://insights.sbomify.com/CVE-2012-1803/index.md","name":"CVE-2012-1803","record":{"aliases":["GHSA-qgxr-qjc2-5hqj"],"analysis":{"component_type":"network_device","fix_type":"patch","impacts":["account_takeover","privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"Industrial network switch","requires_auth":"none","summary":"Remote attackers can gain administrative access to RuggedCom devices by calculating the factory account password from the MAC address.","user_interaction":"not_required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"certcc","cpe":[{"product":"ruggedcom_rugged_operating_system","vendor":"siemens"}],"cvss":{"score":8.5,"severity":"high","source":"nvd","vector":"AV:N/AC:M/Au:S/C:C/I:C/A:C","version":"2.0"},"cwes":[{"id":"CWE-310","name":null}],"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.","ecosystems":[],"exploits":{"exploitdb":1,"first_seen":"2012-04-24","github_poc":1,"max_poc_stars":0,"metasploit":1,"nuclei":0,"refs":[{"date":"2012-04-24","kind":"exploitdb","ref":"18779","stars":null,"title":"RuggedCom Devices - Backdoor Access"},{"date":"2026-05-25T17:37:08Z","kind":"github_poc","ref":"https://github.com/x3roxismygood/CVE-2012-1803","stars":0,"title":"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."},{"date":null,"kind":"metasploit","ref":"auxiliary/scanner/telnet/telnet_ruggedcom","stars":null,"title":"RuggedCom Telnet Password Generator"}],"tier":"weaponised"},"has_fix":null,"headline":"Hardcoded credentials in n/a","id":"CVE-2012-1803","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"hardcoded_credentials","year":"2012"},"n_packages":0,"n_references":12,"next":{"headline":"Memory corruption in n/a","id":"CVE-2012-1804"},"packages":[],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2012-1802"},"products":["n/a"],"published":"2012-04-28","related":[{"cvss_score":8.5,"headline":"Hardcoded credentials in n/a","id":"CVE-2012-2441","kev_date_added":null,"published":"2012-04-28"},{"cvss_score":8.3,"headline":"Other in n/a","id":"CVE-2013-6925","kev_date_added":null,"published":"2013-12-17"},{"cvss_score":8,"headline":"Privilege escalation in n/a","id":"CVE-2013-6926","kev_date_added":null,"published":"2013-12-17"},{"cvss_score":7.8,"headline":"Denial of service in n/a","id":"CVE-2014-1966","kev_date_added":null,"published":"2014-02-24"},{"cvss_score":5,"headline":"Denial of service in n/a","id":"CVE-2014-2590","kev_date_added":null,"published":"2014-03-28"},{"cvss_score":4.3,"headline":"Security feature bypass in n/a","id":"CVE-2015-6675","kev_date_added":null,"published":"2015-09-11"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"attribution","licence":"BSD-3-Clause","name":"Metasploit"},{"class":"attribution","licence":"GPL-2.0-or-later","name":"Exploit-DB"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-06","vendors":["n/a"]},"summary":"Remote attackers can gain administrative access to RuggedCom devices by calculating the factory account password from the MAC address.","url":"https://insights.sbomify.com/CVE-2012-1803/"}