GHSA-FG6G-24V3-5276

Vulnerability from github – Published: 2025-07-08 12:31 – Updated: 2025-07-08 12:31
VLAI
Details

A vulnerability has been identified in RUGGEDCOM RMC8388 V5.X (All versions < V5.10.0), RUGGEDCOM RMC8388NC V5.X (All versions < V5.10.0), RUGGEDCOM RS416NCv2 V5.X (All versions < V5.10.0), RUGGEDCOM RS416PNCv2 V5.X (All versions < V5.10.0), RUGGEDCOM RS416Pv2 V5.X (All versions < V5.10.0), RUGGEDCOM RS416v2 V5.X (All versions < V5.10.0), RUGGEDCOM RS900 (32M) V5.X (All versions < V5.10.0), RUGGEDCOM RS900G (32M) V5.X (All versions < V5.10.0), RUGGEDCOM RS900GNC(32M) V5.X (All versions < V5.10.0), RUGGEDCOM RS900NC(32M) V5.X (All versions < V5.10.0), RUGGEDCOM RSG2100 (32M) V5.X (All versions < V5.10.0), RUGGEDCOM RSG2100NC(32M) V5.X (All versions < V5.10.0), RUGGEDCOM RSG2100P (32M) V5.X (All versions < V5.10.0), RUGGEDCOM RSG2100PNC (32M) V5.X (All versions < V5.10.0), RUGGEDCOM RSG2288 V5.X (All versions < V5.10.0), RUGGEDCOM RSG2288NC V5.X (All versions < V5.10.0), RUGGEDCOM RSG2300 V5.X (All versions < V5.10.0), RUGGEDCOM RSG2300NC V5.X (All versions < V5.10.0), RUGGEDCOM RSG2300P V5.X (All versions < V5.10.0), RUGGEDCOM RSG2300PNC V5.X (All versions < V5.10.0), RUGGEDCOM RSG2488 V5.X (All versions < V5.10.0), RUGGEDCOM RSG2488NC V5.X (All versions < V5.10.0), RUGGEDCOM RSG907R (All versions < V5.10.0), RUGGEDCOM RSG908C (All versions < V5.10.0), RUGGEDCOM RSG909R (All versions < V5.10.0), RUGGEDCOM RSG910C (All versions < V5.10.0), RUGGEDCOM RSG920P V5.X (All versions < V5.10.0), RUGGEDCOM RSG920PNC V5.X (All versions < V5.10.0), RUGGEDCOM RSL910 (All versions < V5.10.0), RUGGEDCOM RSL910NC (All versions < V5.10.0), RUGGEDCOM RST2228 (All versions < V5.10.0), RUGGEDCOM RST2228P (All versions < V5.10.0), RUGGEDCOM RST916C (All versions < V5.10.0), RUGGEDCOM RST916P (All versions < V5.10.0). The affected products do not properly enforce interface access restrictions when changing from management to non-management interface configurations until a system reboot occurs, despite configuration being saved. This could allow an attacker with network access and credentials to gain access to device through non-management and maintain SSH access to the device until reboot.

Show details on source website

{
  "affected": [],
  "aliases": [
    "CVE-2025-41224"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-693"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2025-07-08T11:15:31Z",
    "severity": "HIGH"
  },
  "details": "A vulnerability has been identified in RUGGEDCOM RMC8388 V5.X (All versions \u003c V5.10.0), RUGGEDCOM RMC8388NC V5.X (All versions \u003c V5.10.0), RUGGEDCOM RS416NCv2 V5.X (All versions \u003c V5.10.0), RUGGEDCOM RS416PNCv2 V5.X (All versions \u003c V5.10.0), RUGGEDCOM RS416Pv2 V5.X (All versions \u003c V5.10.0), RUGGEDCOM RS416v2 V5.X (All versions \u003c V5.10.0), RUGGEDCOM RS900 (32M) V5.X (All versions \u003c V5.10.0), RUGGEDCOM RS900G (32M) V5.X (All versions \u003c V5.10.0), RUGGEDCOM RS900GNC(32M) V5.X (All versions \u003c V5.10.0), RUGGEDCOM RS900NC(32M) V5.X (All versions \u003c V5.10.0), RUGGEDCOM RSG2100 (32M) V5.X (All versions \u003c V5.10.0), RUGGEDCOM RSG2100NC(32M) V5.X (All versions \u003c V5.10.0), RUGGEDCOM RSG2100P (32M) V5.X (All versions \u003c V5.10.0), RUGGEDCOM RSG2100PNC (32M) V5.X (All versions \u003c V5.10.0), RUGGEDCOM RSG2288 V5.X (All versions \u003c V5.10.0), RUGGEDCOM RSG2288NC V5.X (All versions \u003c V5.10.0), RUGGEDCOM RSG2300 V5.X (All versions \u003c V5.10.0), RUGGEDCOM RSG2300NC V5.X (All versions \u003c V5.10.0), RUGGEDCOM RSG2300P V5.X (All versions \u003c V5.10.0), RUGGEDCOM RSG2300PNC V5.X (All versions \u003c V5.10.0), RUGGEDCOM RSG2488 V5.X (All versions \u003c V5.10.0), RUGGEDCOM RSG2488NC V5.X (All versions \u003c V5.10.0), RUGGEDCOM RSG907R (All versions \u003c V5.10.0), RUGGEDCOM RSG908C (All versions \u003c V5.10.0), RUGGEDCOM RSG909R (All versions \u003c V5.10.0), RUGGEDCOM RSG910C (All versions \u003c V5.10.0), RUGGEDCOM RSG920P V5.X (All versions \u003c V5.10.0), RUGGEDCOM RSG920PNC V5.X (All versions \u003c V5.10.0), RUGGEDCOM RSL910 (All versions \u003c V5.10.0), RUGGEDCOM RSL910NC (All versions \u003c V5.10.0), RUGGEDCOM RST2228 (All versions \u003c V5.10.0), RUGGEDCOM RST2228P (All versions \u003c V5.10.0), RUGGEDCOM RST916C (All versions \u003c V5.10.0), RUGGEDCOM RST916P (All versions \u003c V5.10.0). The affected products do not properly enforce interface access restrictions when changing from management to non-management interface configurations until a system reboot occurs, despite configuration being saved. This could allow an attacker with network access and credentials to gain access to device through non-management and maintain SSH access to the device until reboot.",
  "id": "GHSA-fg6g-24v3-5276",
  "modified": "2025-07-08T12:31:03Z",
  "published": "2025-07-08T12:31:03Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2025-41224"
    },
    {
      "type": "WEB",
      "url": "https://cert-portal.siemens.com/productcert/html/ssa-083019.html"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
      "type": "CVSS_V3"
    },
    {
      "score": "CVSS:4.0/AV:A/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/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",
      "type": "CVSS_V4"
    }
  ]
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline

Sightings and recorded dates, grouped by day · UTC

JSON
How durations are calculated

Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.

Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.

Events included in the timeline

Loading timeline…


    Loading…

    Loading…

    Loading…

    Related by attack behaviour

    Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.