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

CVE-2024-41977

HIGH · 8.0 CVSS v3.1 Published 2024-08-13
Fix available
A fix is available. Upgrade to 8.1 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable

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 do not properly enforce isolation between user sessions in their web server component. This could allow an authenticated remote attacker to escalate their privileges on the devices.

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

The affected RUGGEDCOM and SCALANCE devices have a session isolation vulnerability in their web server component. An authenticated remote attacker can exploit improper session management to escalate privileges, likely through session hijacking or fixation to access another user's authenticated session.

MitigationUpdate all affected devices to firmware version V8.1 or later to obtain the vendor patch.

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
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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. Identify the device model
    Access the device web interface, console, or management interface and locate the product name/model information. This is typically visible on the login page, dashboard, or in system information pages.
    Affected if The device model is one of: Ruggedcom Rm1224 Lte 4g (EU or NAM), Scalance M804pb, Scalance M826 2 Shdsl Router, Scalance M874-2, Scalance M874-3, Scalance M876-3, or Scalance M876-4.
  2. Check the installed firmware version
    Locate the firmware version in the device web interface (usually in the footer, about page, or system status) or via console command such as 'show version' or 'get firmware version'. Compare your version number against the affected range.
    Affected if The firmware version is below 8.1 (for example, 7.x or earlier).
  3. Verify the web server component is enabled
    Confirm that the device web interface is accessible and accepting HTTP/HTTPS connections. Check device network settings or services configuration to verify the web server service is running.
    Affected if The web-based management interface is enabled and accessible on the device.
  4. Check for active user sessions
    If available in the web interface, examine the session management or user active sessions panel to observe how sessions are handled and whether multiple users can have simultaneous active sessions.
    Affected if Multiple authenticated sessions can exist simultaneously and session IDs are not regenerated between logins.

The device is affected if it is one of the listed models, runs firmware version below 8.1, and has the web server interface enabled, allowing potential session hijacking or fixation attacks.

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

Update all affected devices to firmware version V8.1 or later to obtain the vendor patch.

Recommended fix High confidence

V8.1 (or latest available version beyond V8.1)

  1. 1. Identify the exact model number of the affected Ruggedcom or Scalance device from the affected products list
  2. 2. Navigate to Siemens Industry Online Support (support.industry.siemens.com) or cert-portal.siemens.com
  3. 3. Locate the firmware V8.1 or later version for your specific device model
  4. 4. Download the firmware file following Siemens' standard download procedures
  5. 5. Review the firmware release notes and upgrade instructions specific to your device
  6. 6. Apply the firmware upgrade following the device-specific procedure (typically via web UI, FTP, or management interface)
  7. 7. After upgrade, verify the device is operational and web interface is accessible
  8. 8. Confirm the firmware version displays as V8.1 or later
Caveat Standard firmware upgrade considerations apply - review release notes for any configuration or feature changes before upgrading production devices

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
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-41977 — 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-41977 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