dbcve.org
Ruggedcom Rm1224 Lte\(4g\) Eu FirmwareOperating system · Siemens

CVE-2024-41978

MEDIUM · 6.5 CVSS v3.1 Published 2024-08-13
Fix available
A fix is available. Upgrade to 8.1 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A vulnerability has been identified in RUGGEDCOM RM1224 LTE(4G) EU (6GK6108-4AM00-2BA2) (All versions < V8.1), RUGGEDCOM RM1224 LTE(4G) NAM (6GK6108-4AM00-2DA2) (All versions < V8.1), SCALANCE M804PB (6GK5804-0AP00-2AA2) (All versions < V8.1), SCALANCE M812-1 ADSL-Router family (All versions < V8.1), SCALANCE M816-1 ADSL-Router family (All versions < V8.1), SCALANCE M826-2 SHDSL-Router (6GK5826-2AB00-2AB2) (All versions < V8.1), SCALANCE M874-2 (6GK5874-2AA00-2AA2) (All versions < V8.1), SCALANCE M874-3 (6GK5874-3AA00-2AA2) (All versions < V8.1), SCALANCE M874-3 3G-Router (CN) (6GK5874-3AA00-2FA2) (All versions < V8.1), SCALANCE M876-3 (6GK5876-3AA02-2BA2) (All versions < V8.1), SCALANCE M876-3 (ROK) (6GK5876-3AA02-2EA2) (All versions < V8.1), SCALANCE M876-4 (6GK5876-4AA10-2BA2) (All versions < V8.1), SCALANCE M876-4 (EU) (6GK5876-4AA00-2BA2) (All versions < V8.1), SCALANCE M876-4 (NAM) (6GK5876-4AA00-2DA2) (All versions < V8.1), SCALANCE MUM853-1 (A1) (6GK5853-2EA10-2AA1) (All versions < V8.1), SCALANCE MUM853-1 (B1) (6GK5853-2EA10-2BA1) (All versions < V8.1), SCALANCE MUM853-1 (EU) (6GK5853-2EA00-2DA1) (All versions < V8.1), SCALANCE MUM856-1 (A1) (6GK5856-2EA10-3AA1) (All versions < V8.1), SCALANCE MUM856-1 (B1) (6GK5856-2EA10-3BA1) (All versions < V8.1), SCALANCE MUM856-1 (CN) (6GK5856-2EA00-3FA1) (All versions < V8.1), SCALANCE MUM856-1 (EU) (6GK5856-2EA00-3DA1) (All versions < V8.1), SCALANCE MUM856-1 (RoW) (6GK5856-2EA00-3AA1) (All versions < V8.1), SCALANCE S615 EEC LAN-Router (6GK5615-0AA01-2AA2) (All versions < V8.1), SCALANCE S615 LAN-Router (6GK5615-0AA00-2AA2) (All versions < V8.1). Affected devices insert sensitive information about the generation of 2FA tokens into log files. This could allow an authenticated remote attacker to forge 2FA tokens of other users.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Multiple Siemens RUGGEDCOM and SCALANCE router models (all versions prior to V8.1) contain a vulnerability where sensitive information used in 2FA token generation is written to device log files. An authenticated remote attacker with access to these logs can extract the secret material needed to forge 2FA tokens for other users, bypassing two-factor authentication.

MitigationUpgrade all affected devices to firmware V8.1 or later. Additionally, secure access to device logs and monitor for unauthorized access to prevent log theft prior to patching.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Ruggedcom Rm1224 Lte\(4g\) Eu FirmwareOperating system
Affected:< 8.1
Ruggedcom Rm1224 Lte\(4g\) Nam FirmwareOperating system
Affected:< 8.1
Scalance M804pb FirmwareOperating system
Affected:< 8.1
Scalance M826 2 Shdsl Router FirmwareOperating system
Affected:< 8.1
Scalance M874 2 FirmwareOperating system
Affected:< 8.1
Scalance M874 3 FirmwareOperating system
Affected:< 8.1
Scalance M876 3 FirmwareOperating system
Affected:< 8.1
Scalance M876 4 FirmwareOperating system
Affected:< 8.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Determine the device firmware version
    Access the device web interface or CLI and navigate to System > Firmware or use the 'show version' command to retrieve the currently installed firmware version.
    Affected if The installed version is below V8.1 (for example, V7.x or earlier).
  2. Confirm 2FA is enabled on the device
    Log into the device management interface and check the user authentication settings to see if two-factor authentication is configured and active.
    Affected if 2FA is enabled and in use, as the vulnerability only exposes 2FA secret material.
  3. Examine device log files for 2FA secrets
    Access the device logging section or retrieve log files via syslog/FTP and search for patterns related to 2FA token generation, such as TOTP secrets, seed values, or authentication tokens in plain text.
    Affected if Log files contain any plaintext 2FA-related secrets, seeds, or token generation material.
  4. Review log access records for suspicious activity
    Check system logs and access logs for any unusual or unauthorized retrieval of log files that may indicate an attacker has obtained the sensitive log data.
    Affected if Logs show evidence of unauthorized log access or export by an authenticated attacker.

The device is affected if it runs firmware version prior to V8.1 and has 2FA enabled, with 2FA secret material present in accessible log files.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 8.1 or later
Fixed in 8.1
Interim mitigation

Upgrade all affected devices to firmware V8.1 or later. Additionally, secure access to device logs and monitor for unauthorized access to prevent log theft prior to patching.

Recommended fix High confidence

V8.1

  1. 1. Obtain the V8.1 firmware for your specific device model from Siemens (cert-portal.siemens.com or official Siemens support channels)
  2. 2. Back up the current device configuration before performing the upgrade
  3. 3. Upload the V8.1 firmware to the affected Ruggedcom or Scalance device following the manufacturer's firmware upgrade procedure
  4. 4. Verify the firmware upgrade completed successfully
  5. 5. Confirm the device is running V8.1 and validate that sensitive 2FA token information is no longer being written to log files

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Ruggedcom Rm1224 Lte\(4g\) Eu Firmware Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,980
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,968.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-41978 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-41978 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data