CVE-2022-46670
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 was made aware of a vulnerability by a security researcher from Georgia Institute of Technology that the MicroLogix 1100 and 1400 controllers contain a vulnerability that may give an attacker the ability to accomplish remote code execution. The vulnerability is an unauthenticated stored cross-site scripting vulnerability in the embedded webserver. The payload is transferred to the controller over SNMP and is rendered on the homepage of the embedded website.
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 · high confidenceUnauthenticated stored cross-site scripting vulnerability in the embedded webserver of Rockwell MicroLogix 1100 and 1400 controllers. Malicious JavaScript payloads are transferred to the controller via SNMP and persist on the web interface homepage, executing in browsers of users who access the controller's web 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 dataall versionsall versions<= 21.007<= 21.007<= 7.000CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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 device model and firmware versionAccess the controller's web interface or use SNMP queries (snmpget or snmpwalk) to retrieve the sysDescr and firmware version OIDs. For web access, check the controller's status or about page. For SNMP, query OID 1.3.6.1.2.1.1.1.0 (sysDescr) and 1.3.6.1.4.1.1991.1.1.1.1.1.0 (firmware revision).Affected if The device is a MicroLogix 1400 with firmware version <= 21.007 (B/C revision) or <= 7.000 (A revision), or any version of MicroLogix 1100, and the firmware is not patched to a version beyond the affected ranges.
-
Confirm embedded web server is enabledAccess the controller's IP address via HTTP/HTTPS in a web browser. If a login page or controller status page loads, the web server is active. Alternatively, check if TCP ports 80 or 443 are listening on the controller's IP address using a port scanner (nmap -p 80,443 <controller_ip>).Affected if The web interface is accessible, meaning the embedded web server is enabled and the XSS payload could be stored and served to browsers.
-
Verify SNMP service accessibilityUse an SNMP client to test if SNMP is responding on UDP port 161. Run 'snmpwalk -v2c -c public <controller_ip>' to enumerate SNMP data. Check if SNMP community strings are accepted.Affected if SNMP is accessible on the network, indicating the attack vector (SNMP injection) is possible and a malicious payload could be sent to the controller.
-
Inspect web interface for suspicious script contentView the controller's homepage source code (right-click > View Page Source) or use browser developer tools to examine the HTML for any unexpected <script> tags, event handlers (onclick, onerror, onload), or iframe/embed elements containing JavaScript. Also check the controller status or welcome messages.Affected if The page contains unrecognized JavaScript code, Base64-encoded strings, or script tags that were not configured by legitimate administrators, indicating a stored XSS payload is present.
-
Check SNMP configuration for unexpected OID valuesUse snmpget or snmpwalk to query string-type OIDs on the controller, particularly the sysContact (1.3.6.1.2.1.1.4.0) or sysLocation (1.3.6.1.2.1.1.6.0) OIDs. Examine returned values for HTML-encoded or obfuscated content.Affected if The SNMP values contain HTML tags, script elements, or unusual strings that could represent a malicious payload awaiting execution on the web interface.
If the device is a MicroLogix 1100 or 1400 with an affected firmware version, has its web server enabled, and has accessible SNMP, then the controller is potentially vulnerable to stored XSS execution when users access the web interface.
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 dataRestrict network access to the controller's web server and SNMP services using network segmentation; filter SNMP traffic at the perimeter. Apply vendor firmware updates when available and consider deploying a web application firewall for industrial protocols.
- Consultation6.0 h
- Implementation10.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 $7,104.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-46670 — 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-46670 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