CVE-2025-41665
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 · uneditedAn low privileged remote attacker can enforce the watchdog of the affected devices to reboot the PLC due to incorrect default permissions of a config file.
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 confidenceA config file on affected PLC devices has incorrect default permissions, allowing a low-privileged remote attacker to modify it and trigger the device's watchdog timer to force a reboot, resulting in denial of service.
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
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify PLC device model and firmware versionLocate the device's model number and firmware version through the device's web interface, console, or documentation. Compare against any vendor advisories for affected versions.Affected if The device is a PLC from a vendor affected by this vulnerability and runs a firmware version within the affected range.
-
Locate watchdog timer configuration fileAccess the device's file system via SSH, FTP, or vendor-specific management interface. Search for configuration files related to watchdog timer settings, typically named with terms like 'watchdog', 'watchdog.conf', or 'config.xml' in system or etc directories.Affected if A watchdog timer configuration file exists on the device and is accessible.
-
Check file permissions on the config fileUse the 'ls -la' command (or equivalent file attribute check via vendor interface) on the identified configuration file to view permission bits. Look for owner, group, and world read/write/execute permissions.Affected if The file permissions allow write access by users other than the administrator or root account (e.g., permissions include 'w' for group or world).
-
Verify low-privilege access to modify the fileAttempt to modify the configuration file using a low-privileged account or check if the file is owned by a privileged user but still writable by others due to misconfigured permissions.Affected if A low-privilege user or remote attacker can successfully modify the watchdog configuration file.
-
Confirm watchdog timer can be triggered for DoSIf file permissions allow modification, verify that changing the watchdog timer configuration to force an immediate or very short timeout would trigger a device reboot.Affected if The watchdog timer is software-configurable through the accessible config file, and triggering it causes device restart.
The device is affected if the watchdog timer configuration file has overly permissive file permissions that allow modification by low-privileged users, enabling a denial of service via forced reboot.
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 dataCorrect the default file permissions on the affected config file to restrict unauthorized modification, and consider firmware updates if available from the vendor.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-41665 — 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-41665 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