Affected devices store the CLI user passwords encrypted in flash memory.
Noroxi assessment
Priority: Monitor (action score 20/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.26% (FIRST EPSS).
- Physical access to the device is required. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- According to the record, no fixed version is available yet.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Update when a fix is released; follow the vendor's advisory.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
Affected devices store the CLI user passwords encrypted in flash memory. Attackers with physical access to the device could retrieve the file and decrypt the CLI user passwords.
- Published
- Dec 13, 2022
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 17th percentile
- CWE
- CWE-257
Report tools
Action score
20
Monitor
Low priority for now.
- CVSS
- 20 / 40 · 5.2 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · siemens
- 5.7
- NVD has not scored this yet; the score shown is the CNA’s.
CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- No fixed version yet
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| siemens | ruggedcom rm1224 lte\(4g\) eu firmware | cpe:2.3:o:siemens:ruggedcom_rm1224_lte\(4g\)_eu_firmware |
| siemens | ruggedcom rm1224 lte\(4g\) eu | cpe:2.3:h:siemens:ruggedcom_rm1224_lte\(4g\)_eu |
| siemens | ruggedcom rm1224 lte\(4g\) nam firmware | cpe:2.3:o:siemens:ruggedcom_rm1224_lte\(4g\)_nam_firmware |
| siemens | ruggedcom rm1224 lte\(4g\) nam | cpe:2.3:h:siemens:ruggedcom_rm1224_lte\(4g\)_nam |
| siemens | scalance m804pb firmware | cpe:2.3:o:siemens:scalance_m804pb_firmware |
| siemens | scalance m804pb | cpe:2.3:h:siemens:scalance_m804pb |
| siemens | scalance m812-1 adsl-router firmware | cpe:2.3:o:siemens:scalance_m812-1_adsl-router_firmware |
| siemens | scalance m812-1 adsl-router | cpe:2.3:h:siemens:scalance_m812-1_adsl-router |
| siemens | scalance m816-1 adsl-router firmware | cpe:2.3:o:siemens:scalance_m816-1_adsl-router_firmware |
| siemens | scalance m816-1 adsl-router | cpe:2.3:h:siemens:scalance_m816-1_adsl-router |
| siemens | scalance m826-2 shdsl-router firmware | cpe:2.3:o:siemens:scalance_m826-2_shdsl-router_firmware |
| siemens | scalance m826-2 shdsl-router | cpe:2.3:h:siemens:scalance_m826-2_shdsl-router |
and 188 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- siemens ruggedcom rm1224 lte(4g) eu firmwareall versions
- siemens ruggedcom rm1224 lte(4g) nam firmwareall versions
- siemens scalance m804pb firmwareall versions
- siemens scalance m812-1 adsl-router firmwareall versions
- siemens scalance m816-1 adsl-router firmwareall versions
- siemens scalance m826-2 shdsl-router firmwareall versions
- siemens scalance m874-2 firmwareall versions
- siemens scalance m874-3 firmwareall versions
- siemens scalance m876-3 firmwareall versions
- siemens scalance m876-4 firmwareall versions
- siemens scalance mum853-1 firmwareall versions
- siemens scalance mum856-1 firmwareall versions
- siemens scalance s615 eec firmwareall versions
- siemens scalance s615 firmwareall versions
- siemens scalance sc622-2c firmwarebefore 2.3
- siemens scalance sc626-2c firmwarebefore 2.3
- siemens scalance sc632-2c firmwarebefore 2.3
- siemens scalance sc636-2c firmwarebefore 2.3
- siemens scalance sc642-2c firmwarebefore 2.3
- siemens scalance sc646-2c firmwarebefore 2.3
Versions reported by the vendor
Affected version ranges reported by the assigning authority (siemens). Independent of NVD's CPE analysis and usually ahead of it.
Siemens RUGGEDCOM RM1224 LTE(4G) EU
- before V7.2affected
Siemens RUGGEDCOM RM1224 LTE(4G) NAM
- before V7.2affected
Siemens SCALANCE M804PB
- before V7.2affected
Siemens SCALANCE M812-1 ADSL-Router
- before V7.2affected
- before V7.2affected
Siemens SCALANCE M816-1 ADSL-Router
- before V7.2affected
- before V7.2affected
Siemens SCALANCE M826-2 SHDSL-Router
- before V7.2affected
Siemens SCALANCE M874-2
- before V7.2affected
Siemens SCALANCE M874-3
- before V7.2affected
Siemens SCALANCE M876-3
- before V7.2affected
Siemens SCALANCE M876-3 (ROK)
- before V7.2affected
Siemens SCALANCE M876-4
- before V7.2affected
Siemens SCALANCE M876-4 (EU)
- before V7.2affected
Same product
siemens: all recordsOther highest-scoring records for the same primary product.
- CVE-2024-50572A vulnerability has been identified in RUGGEDCOM RM1224 LTE(4G) EU (6GK6108-4AM00-2BA2) (All versions < V8.2), RUGGEDCOM RM1224 LTE(4G) NAM 34Monitor
- CVE-2024-50557A vulnerability has been identified in RUGGEDCOM RM1224 LTE(4G) EU (6GK6108-4AM00-2BA2) (All versions < V8.2), RUGGEDCOM RM1224 LTE(4G) NAM 34Monitor
- CVE-2024-41976A vulnerability has been identified in RUGGEDCOM RM1224 LTE(4G) EU (6GK6108-4AM00-2BA2) (All versions < V8.1), RUGGEDCOM RM1224 LTE(4G) NAM 34Monitor
- CVE-2024-41977A vulnerability has been identified in RUGGEDCOM RM1224 LTE(4G) EU (6GK6108-4AM00-2BA2) (All versions < V8.1), RUGGEDCOM RM1224 LTE(4G) NAM 29Monitor
- CVE-2024-41978A vulnerability has been identified in RUGGEDCOM RM1224 LTE(4G) EU (6GK6108-4AM00-2BA2) (All versions < V8.1), RUGGEDCOM RM1224 LTE(4G) NAM 28Monitor
- CVE-2022-46140Affected devices use a weak encryption scheme to encrypt the debug zip file.28Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-22-0750 · Dec 20, 2022(Siemens Scalance Endüstriyel Ürünler Güvenlik Zafiyeti)
Technical details
Attack conditions
- Physical access to the device is required.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- Integrity
- Availability
- Attack vector
- Physical
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- X
Weakness class (CWE)
CWE-257 · Storing Passwords in a Recoverable FormatCVSS vector
CVSS:4.0/AV:P/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/VA:L/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
Change log
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Show all references (1 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.