CVE-2024-37367
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 v12. 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. 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 v12 contains an authentication bypass vulnerability where remote users can send packets to the server to view HMI projects without proper authentication verification. This allows unauthenticated attackers to potentially access sensitive operational information about the industrial control system.
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>= 12.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.
-
Verify FactoryTalk View SE versionCheck the installed version via Windows Registry at HKLM\SOFTWARE\Rockwell Software\FactoryTalk View SE\Version or by right-clicking the application in Windows Programs and selecting PropertiesAffected if The installed version is 12.0 or higher but lower than 14.0
-
Confirm HMI project server is runningOpen Windows Services and verify the 'FactoryTalk View SE Server' service status, or check via Task Manager for related processes like 'FTViewSE.exe' or 'HMIProjectServer.exe'Affected if The FactoryTalk View SE Server service is running and accepting remote connections
-
Check network accessibility of the serverUse 'netstat -an | findstr LISTENING' to identify listening ports (typically TCP 80, 443, or custom ports for FactoryTalk SE) and verify if the server IP is exposed to untrusted networksAffected if The FactoryTalk View SE server ports are listening on interfaces accessible from untrusted networks (not limited to localhost or internal management VLAN)
-
Inspect HMI project access loggingReview FactoryTalk View SE log files in the application logs directory (typically under C:\Program Files\Rockwell Software\FactoryTalk View\SE\Logs\) for unauthenticated or unexpected project access entriesAffected if Log entries show project access from IP addresses that do not correspond to authenticated user sessions or expected clients
A user is affected if FactoryTalk View SE version 12.0 through 13.x is installed with the server component exposed to network access and unauthenticated project requests are possible or logged.
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
Apply the vendor patch from Rockwell Automation when available. In the interim, implement network segmentation to restrict unauthorized access to the FTView SE server and monitor for anomalous HMI project access attempts.
FactoryTalk View 14.0
- Upgrade FactoryTalk View SE to version 14.0 or later to remediate the authentication bypass vulnerability
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation2.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,160.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-37367 — 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-37367 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