dbcve.org
Armorstart St 284ee FirmwareOperating system · Rockwellautomation

CVE-2023-29025

MEDIUM · 5.9 CVSS v3.1 Published 2023-05-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
63/100
Remediation priority · Elevated
Remotely reachable

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 · unedited
A 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 confidence

A stored cross-site scripting (XSS) vulnerability exists in the Rockwell Automation ArmorStart ST web interface. An authenticated attacker with admin privileges and network access can inject malicious scripts into web pages, allowing execution in other users' browsers to view sensitive data, modify the interface, or cause availability disruptions.

MitigationApply vendor-provided patches when available. Until then, limit network access to the web interface to trusted administrators only and implement additional network segmentation. Implement output encoding and input validation on all user-controllable fields in the interim.

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
Armorstart St 284ee FirmwareOperating system
Affected:all versions
Armorstart St 281e FirmwareOperating system
Affected:all versions

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify ArmorStart ST device in your network
    Locate Rockwell Automation ArmorStart ST industrial controllers on the network using device discovery or inventory tools. Check network scans for devices matching this product line.
    Affected if ArmorStart ST model 284ee or 281e is present on the network
  2. Confirm the specific model number
    Access the device directly or check asset inventory to verify whether the model is specifically 284ee or 281e. These models have the web interface feature.
    Affected if Model number is 284ee or 281e firmware
  3. Verify web interface is enabled
    Attempt to access the device web interface via HTTP/HTTPS on the expected management port (typically port 80/443 or vendor-assigned ports). Check if the web service responds.
    Affected if Web interface is accessible and responds to HTTP/HTTPS requests
  4. Confirm admin-level access exists
    Verify you have administrative credentials for the ArmorStart ST web interface. The vulnerability requires an authenticated attacker with admin privileges.
    Affected if Admin credentials exist or can be obtained for the device web interface
  5. Inspect web interface for stored scripts
    Log into the web interface with admin privileges and examine all input fields (device name, configuration fields, banner messages, or any user-controllable parameters). Look for unexpected script tags or encoded JavaScript that could indicate prior exploitation.
    Affected if Any user-controllable fields in the web interface accept and store script content without sanitization

You are affected if you have an ArmorStart ST 284ee or 281e device with the web interface enabled and accessible using admin credentials, as all versions of these models contain the stored XSS vulnerability.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor-provided patches when available. Until then, limit network access to the web interface to trusted administrators only and implement additional network segmentation. Implement output encoding and input validation on all user-controllable fields in the interim.

Fix this in Armorstart St 284ee Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,960.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-29025 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-29025 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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