CVE-2025-24009
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 · uneditedA vulnerability has been identified in SIRIUS 3RK3 Modular Safety System (MSS) (All versions), SIRIUS Safety Relays 3SK2 (All versions). The affected devices do not require authentication to access critical resources. An attacker with network access could retrieve sensitive information from certain data records, including obfuscated safety passwords.
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 · moderate confidenceThe SIRIUS 3RK3 Modular Safety System and SIRIUS Safety Relays 3SK2 allow unauthenticated network access to critical resources, enabling remote attackers to retrieve sensitive data including obfuscated safety passwords from certain data records.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:H/PR:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify SIRIUS safety devices on the networkScan network inventory or use industrial asset discovery tools to locate Siemens SIRIUS 3RK3 Modular Safety Systems and SIRIUS Safety Relays 3SK2. Check device nameplates, management interfaces, or PLC/SCADA configurations for these model numbers.Affected if SIRIUS 3RK3 or 3SK2 devices are present on the network and reachable via IP
-
Determine network exposure of safety devicesReview firewall rules, VLAN assignments, and network segmentation policies to check whether these safety devices are accessible from untrusted networks or the internet.Affected if Devices are accessible from untrusted network segments without proper isolation
-
Check for unauthenticated access to data recordsIf you have access to the device management interface, attempt to retrieve data records or configuration files without providing credentials. Look for endpoints that return safety-related data such as passwords or configuration parameters without authentication prompts.Affected if Data records containing safety passwords or sensitive configuration data are accessible without authentication
-
Review network logs for unauthorized access attemptsInspect firewall, IDS/IPS, or network monitoring logs for unusual traffic patterns targeting port 80/443 or proprietary protocols on the safety device IP addresses, particularly requests that retrieve configuration or password data.Affected if Log analysis reveals unauthorized external access attempts to safety device interfaces or data retrieval requests
-
Compare installed firmware versionAccess the device web interface or management console and record the firmware version. Compare against any vendor-released patched versions for CVE-2025-24009 if documented in vendor security advisories.Affected if Firmware version matches or predates the vulnerable version range and the device is network-accessible
Environment is affected if SIRIUS 3RK3 or 3SK2 safety devices are network-accessible and allow unauthenticated retrieval of sensitive data records or safety passwords.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataImplement network segmentation to isolate affected safety devices from untrusted networks; consult vendor for firmware updates that enforce authentication; until patched, monitor for unauthorized access attempts to these industrial safety components.
- Consultation6.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-24009 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-24009 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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