CVE-2023-46289
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 · uneditedRockwell Automation FactoryTalk View Site Edition insufficiently validates user input, which could potentially allow threat actors to send malicious data bringing the product offline. If exploited, the product would become unavailable and require a restart to recover resulting in a denial-of-service condition.
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 Site Edition contains an input validation vulnerability where user-supplied data is not properly sanitized before processing. An unauthenticated attacker can send specially crafted malicious data to the application, causing it to become unresponsive or crash, resulting in a denial-of-service condition that requires a manual restart to recover.
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, <= 13.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
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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.
-
Identify if FactoryTalk View Site Edition is installedCheck the system for FactoryTalk View SE installation using the Windows Programs and Features control panel, or look for FactoryTalk View SE directories in Program Files (typically C:\Program Files\Rockwell Software\FactoryTalk View or similar locations).Affected if FactoryTalk View Site Edition is present on the system.
-
Determine the installed version of FactoryTalk View SEOpen FactoryTalk View SE and navigate to the About section, or check the installation directory for version information files. Alternatively, check Windows Registry under HKLM\SOFTWARE\Rockwell Software\FactoryTalk View SE for the Version key.Affected if The installed version falls within the range >= 11.0 and <= 13.0.
-
Check if the FactoryTalk View SE service is running and network-enabledOpen Windows Services and locate the FactoryTalk View SE service (typically named FactoryTalk View SE or similar). Verify if it is running and bound to network interfaces. Use netstat -an to check if ports used by FactoryTalk View SE (commonly port 80/443 or custom ports) are listening.Affected if The service is running and accepting network connections.
-
Assess network exposure of the FactoryTalk View SE interfaceReview firewall rules and network configuration to determine if the FactoryTalk View SE web interface or service ports are accessible from untrusted networks. Check if the application is exposed directly to the internet or to less-trusted network segments.Affected if The interface is accessible from untrusted networks without proper network segmentation or access controls.
A user is affected if FactoryTalk View Site Edition versions 11.0 through 13.0 are installed and the application service is running and accessible over the network, allowing unauthenticated attackers to send malicious data and cause a denial-of-service condition.
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-supplied patches when available. In the interim, implement network segmentation to restrict access to the application, deploy intrusion detection systems to monitor for anomalous input patterns, and enforce strict access controls to limit exposure to untrusted networks.
- Consultation6.0 h
- Implementation12.0 h
- Testing10.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,504.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-46289 — 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-46289 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