CVE-2024-41173
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 · uneditedThe IPC-Diagnostics package included in TwinCAT/BSD is vulnerable to a local authentication bypass by a low privileged attacker.
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 IPC-Diagnostics package in TwinCAT/BSD contains a local authentication bypass vulnerability allowing a low-privileged attacker to circumvent authentication controls. This local vector means the attacker already has some level of system access but can escalate by bypassing authentication in the diagnostic tooling.
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< 2.0.0.1< 14.1.2.0CVSS 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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm TwinCAT/BSD is installedIdentify if the system is running Beckhoff TwinCAT/BSD by checking the OS or installed Beckhoff software componentsAffected if The system does not have TwinCAT/BSD installed - this CVE only applies to TwinCAT/BSD systems
-
Check TwinCAT/BSD versionDetermine the installed TwinCAT/BSD version numberAffected if TwinCAT/BSD version is below 14.1.2.0
-
Confirm IPC-Diagnostics package presenceVerify if the IPC-Diagnostics package is installed on the TwinCAT/BSD systemAffected if IPC-Diagnostics package is not installed - the vulnerability only affects systems with this package
-
Check IPC-Diagnostics package versionDetermine the installed IPC-Diagnostics package versionAffected if IPC-Diagnostics package version is below 2.0.0.1
A system is affected if it runs TwinCAT/BSD below version 14.1.2.0 or has IPC-Diagnostics package below version 2.0.0.1, with the IPC-Diagnostics package installed and enabled.
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.
dbcve · scoped2.0.0.114.1.2.0
Apply available patches or updates to the IPC-Diagnostics package; if no patch exists, review and harden authentication mechanisms within the diagnostic package and restrict local user privileges accordingly.
Ipc Diagnostics Package: 2.0.0.1 or later; TwinCAT/BSD: 14.1.2.0 or later
- 1. Identify the current version of the IPC Diagnostics Package installed on the TwinCAT/BSD system
- 2. Identify the current TwinCAT/BSD version running on the system
- 3. For IPC Diagnostics Package: Upgrade to version 2.0.0.1 or later
- 4. For TwinCAT/BSD: Upgrade to version 14.1.2.0 or later
- 5. After upgrade, verify that the authentication mechanism is functioning correctly
- 6. Test that low-privileged users can no longer bypass authentication controls
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-41173 — 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-2024-41173 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