CVE-2022-3158
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 VantagePoint versions 8.0, 8.10, 8.20, 8.30, 8.31 are vulnerable to an input validation vulnerability. The FactoryTalk VantagePoint SQL Server lacks input validation when users enter SQL statements to retrieve information from the back-end database. If successfully exploited, this could allow a user with basic user privileges to perform remote code execution on the server.
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 confidenceSQL injection vulnerability in FactoryTalk VantagePoint allows authenticated users with basic privileges to execute arbitrary SQL statements on the back-end SQL Server database. The lack of input validation on user-supplied SQL queries can be chained to achieve remote code execution on the host server.
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= 8.0= 8.10= 8.20= 8.30= 8.31CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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 VantagePoint is installedCheck the Windows Programs and Features list (appwiz.cpl) or look for the installation directory typically under C:\Program Files\Rockwell Software\FactoryTalk VantagePointAffected if FactoryTalk VantagePoint appears in installed programs
-
Identify the installed versionOpen the Windows Registry and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Rockwell Software\FactoryTalk VantagePoint\ or check the version info of the main application executable in the installation folderAffected if The version matches 8.0, 8.10, 8.20, 8.30, or 8.31 exactly
-
Verify the web interface is accessibleCheck if the FactoryTalk VantagePoint web server (IIS or internal web service) is running and reachable on the network by accessing the web portal URLAffected if The web interface is exposed to network access beyond trusted administrators
-
Review application logs for suspicious SQL patternsExamine FactoryTalk VantagePoint logs in the installation logs folder for SQL keywords (SELECT, UNION, INSERT, DROP, xp_) in query parameters or unexpected query patternsAffected if Logs contain SQL injection attempts or anomalous SQL queries from authenticated sessions
-
Check for unexpected user accounts with basic privilegesReview the FactoryTalk VantagePoint user management console to list accounts with basic-level permissions, especially any newly created or unrecognized accountsAffected if There are untrusted or unknown basic-privilege user accounts
If FactoryTalk VantagePoint versions 8.0 through 8.31 are installed and the web interface is network-accessible to untrusted users, the environment is likely affected by this SQL injection vulnerability.
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 · scopedApply vendor patch when available; until then, restrict network access to FactoryTalk VantagePoint to trusted users only and monitor for suspicious SQL query patterns in logs.
Contact Rockwell Automation for the fixed release (versions after 8.31)
- Contact Rockwell Automation technical support to obtain the security update for this vulnerability
- Request the specific patch or updated version that addresses CVE-2022-3158
- Apply the update following Rockwell Automation's standard patch management procedures for FactoryTalk VantagePoint
- Verify the patch was applied successfully and test that SQL injection is no longer possible
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation16.0 h
- Testing12.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 $11,136.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-3158 — 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-2022-3158 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