CVE-2024-37368
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 user authentication vulnerability exists in the Rockwell Automation FactoryTalk® View SE. The vulnerability allows a user from a remote system with FTView to send a packet to the customer’s server to view an HMI project. Due to the lack of proper authentication, this action is allowed without proper authentication verification.
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 View SE fails to properly authenticate remote users attempting to view HMI projects. An attacker from a remote system with FTView can send specially crafted packets to the server to access HMI project data without any valid credentials, due to missing authentication verification in the project viewing functionality.
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>= 11.0, < 14.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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/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 if FactoryTalk View SE is installedCheck the system for FactoryTalk View SE installation. In Windows environments, review installed programs via Control Panel > Programs and Features, or query the Windows Registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for entries containing 'FactoryTalk View' or 'FTView'.Affected if FactoryTalk View SE is present on the system
-
Determine the installed FactoryTalk View SE versionLocate the version information for the installed FactoryTalk View SE software. Typically found in the program's properties within the Windows installation directory (commonly in C:\Program Files\Rockwell Software\FactoryTalk View\ or via the Windows Registry uninstall entries). Compare the installed version against the affected range: version 11.0 or higher but below version 14.0.Affected if The installed version falls within >= 11.0 and < 14.0
-
Verify if HMI project viewing functionality is enabledExamine the FactoryTalk View SE server configuration and project settings. Review the project configuration files and server settings to determine if remote project viewing or HMI data access features are enabled. Look for configuration settings related to remote access, project publishing, or data server accessibility.Affected if Remote project viewing or HMI data serving features are enabled on the FTView SE server
-
Assess network accessibility of the FTView serverEvaluate the network exposure of the system running FactoryTalk View SE. Determine if the server is directly accessible from untrusted networks or if proper network segmentation, firewalls, or VPN controls are in place to restrict unauthorized remote access to the FTView service ports.Affected if The FTView SE server is reachable from untrusted or external network segments without adequate access controls
A system is affected if it runs FactoryTalk View SE versions 11.0 through 13.x with remote project viewing enabled and accessible from untrusted networks, allowing unauthenticated remote access to HMI project data.
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 · scoped14.0
Implement proper authentication verification for all HMI project viewing requests, ensuring remote users must provide valid credentials before accessing project data. Consider network segmentation to limit exposure of the FTView server to untrusted networks.
FactoryTalk View 14.0 or later
- Back up all FactoryTalk View SE projects, HMI applications, and server configurations before proceeding with the upgrade
- Download FactoryTalk View version 14.0 or later from the official Rockwell Automation download portal or support website
- Review Rockwell Automation's installation and upgrade documentation for FactoryTalk View 14.0
- Install FactoryTalk View 14.0 on the affected server(s) following the documented upgrade procedure
- After installation, verify that the FactoryTalk View SE services start correctly
- Test that remote unauthenticated access to HMI projects is now properly blocked (the vulnerability should be remediated)
- Restore the backed-up projects and configurations to the upgraded system
Generated from the published advisory — verify against the referenced sources before acting.
- 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-37368 — 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-37368 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