CVE-2023-46290
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 · uneditedDue to inadequate code logic, a previously unauthenticated threat actor could potentially obtain a local Windows OS user token through the FactoryTalk® Services Platform web service and then use the token to log in into FactoryTalk® Services Platform . This vulnerability can only be exploited if the authorized user did not previously log in into the FactoryTalk® Services Platform web service.
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 confidenceFactoryTalk® Services Platform web service contains flawed code logic that allows an unauthenticated attacker to steal a local Windows OS user token. The stolen token can then be used to authenticate to FactoryTalk® Services Platform as the legitimate user, but only when that user has not previously logged in to the web service.
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.80CVSS 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
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:N/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 FactoryTalk Services Platform installationLook for the FactoryTalk Services Platform service or installed application on the Windows system. Check Windows Services for 'FactoryTalk' or look in Program Files for Rockwell Automation folders.Affected if FactoryTalk Services Platform is present on the system
-
Identify installed versionCheck the installed version of FactoryTalk Services Platform through Windows Programs and Features, or right-click the executable in the installation directory and view Properties > Details for the version number.Affected if Installed version is lower than 2.80 (e.g., 2.70, 2.60, etc.)
-
Verify web service is runningCheck if the FactoryTalk Services Platform web service is running and listening on its configured port (typically ports 80/443 or custom web service ports). Use netstat or check Windows Services for the web service status.Affected if Web service is running and accessible on the network
-
Check user login history to web serviceReview FactoryTalk Services Platform logs or user authentication records to determine which local Windows users have previously authenticated to the web service.Affected if There exist local Windows OS users who have NOT yet logged into the FactoryTalk web service (these are the users whose tokens could be stolen and used)
You are affected if FactoryTalk Services Platform version is below 2.80, the web service is running, and there are local Windows users who have never authenticated to the web service (making them potential targets for token theft).
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.80
Apply the vendor patch from Rockwell Automation to remediate the inadequate authentication logic in FactoryTalk® Services Platform. Until patched, consider network segmentation and restricting access to the web service to trusted users only.
FactoryTalk Services Platform 2.80
- 1. Identify the current version of FactoryTalk Services Platform installed in your environment
- 2. Navigate to the Rockwell Automation Product Compatibility and Download Center (PCDC) at rockwellautomation.custhelp.com
- 3. Search for FactoryTalk Services Platform
- 4. Download version 2.80 or later
- 5. Review the installation instructions in the release notes or user manual
- 6. Back up current configuration data as recommended by Rockwell documentation
- 7. Execute the upgrade following standard Rockwell Automation upgrade procedures
- 8. Verify the installation completed successfully
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-46290 — 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-2023-46290 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