CVE-2024-21917
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 exists in Rockwell Automation FactoryTalk® Service Platform that allows a malicious user to obtain the service token and use it for authentication on another FTSP directory. This is due to the lack of digital signing between the FTSP service token and directory. If exploited, a malicious user could potentially retrieve user information and modify settings without any authentication.
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 confidenceA critical authentication bypass exists in Rockwell Automation FactoryTalk Service Platform where service tokens lack digital signature validation. Attackers can obtain tokens from one FTSP directory and reuse them to authenticate to other FTSP directories, allowing unauthenticated access to retrieve user information and modify system settings.
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<= 6.31.00CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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 installed FactoryTalk Service Platform versionUse the Windows Programs and Features control panel, or check the program's About/Properties dialog, or run the FactoryTalk Administration Console to view the installed FTSP version numberAffected if The installed version is 6.31.00 or lower (any version up to and including 6.31.00)
-
Determine if multiple FTSP directories existOpen FactoryTalk Administration Console and check if more than one FTSP directory (domain) is configured in the FactoryTalk Network Directory settingsAffected if Multiple FTSP directories are configured and accessible on the network
-
Verify token signature validation is enabledInspect FactoryTalk Service Platform security configuration settings in the FactoryTalk Administration Console under Security or Directory services settings for any option related to token validation or signature verificationAffected if Token signature validation is disabled or there is no option to enforce it
-
Review FTSP directory access logsCheck FactoryTalk logs or Windows Event Viewer for authentication events where tokens from one directory are used to access a different directoryAffected if Logs show cross-directory token authentication attempts or successful authentications from unexpected directory sources
-
Check network exposure of FTSP servicesReview network firewall rules and listening services to determine if FactoryTalk Service Platform ports are exposed beyond the internal network segmentAffected if FTSP services are accessible from network segments outside the trusted environment
A user is affected if FactoryTalk Service Platform version 6.31.00 or lower is installed, especially when multiple FTSP directories exist and token signature validation is not enforced.
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 dataApply vendor-provided patches for FactoryTalk Service Platform immediately; implement network segmentation to isolate FTSP components and monitor for unauthorized token usage across directories.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,352.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-21917 — 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-21917 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