CVE-2023-29028
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 cross site scripting vulnerability was discovered in Rockwell Automation's ArmorStart ST product that could potentially allow a malicious user with admin privileges and network access to view user data and modify the web interface. Additionally, a malicious user could potentially cause interruptions to the availability of the web page.
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 confidenceA cross-site scripting (XSS) vulnerability exists in the web interface of Rockwell Automation's ArmorStart ST industrial motor starter product. An authenticated attacker with admin privileges and network access can inject malicious scripts to view user data, modify the web interface, or disrupt web page availability.
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 versionsCVSS 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
- High
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:L
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 ArmorStart ST device in the environmentLocate and confirm the presence of Rockwell Automation ArmorStart ST model 284E or 281E industrial motor starters in your network or asset inventory. Check device nameplates, network scans, or management interfaces for these specific model numbers.Affected if The environment contains any ArmorStart ST 284E or 281E device regardless of firmware version.
-
Check the installed firmware versionAccess the device web interface or use the device's management software to view the firmware version. Navigate to the system information or firmware details section.Affected if Any firmware version is installed, as all versions of these models are affected by this vulnerability.
-
Verify the web interface is enabledConfirm that the built-in web interface/HTTP server is enabled on the ArmorStart ST device. This is typically found in the device network settings or web server configuration section.Affected if The web interface is accessible and enabled on the device.
-
Confirm admin user accounts existReview the user management or accounts configuration on the device to determine if any admin-level user accounts are configured or present.Affected if Admin-level user accounts exist on the device, as the attacker requires admin privileges to exploit this XSS vulnerability.
-
Assess network accessibility of the web interfaceDetermine if the device web interface is reachable from network segments outside of trusted operational technology networks. Check firewall rules, VLAN configurations, and access control lists.Affected if The web interface is accessible from network segments beyond trusted personnel and isolated OT networks.
You are affected if you have any ArmorStart ST 284E or 281E device with the web interface enabled, even a single admin account configured, and the web interface is network-accessible beyond isolated trusted networks.
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-provided firmware updates or patches. Until then, restrict network access to trusted personnel only and implement input validation and output encoding on any interim workarounds.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-29028 — 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-29028 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