dbcve.org
St Ipm 6350 FirmwareOperating system · Redlioncontrols

CVE-2023-42770

CRITICAL · 9.8 CVSS v3.1 Published 2023-11-21
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available

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
Red Lion SixTRAK and VersaTRAK Series RTUs with authenticated users enabled (UDR-A) any Sixnet UDR message will meet an authentication challenge over UDP/IP. When the same message is received over TCP/IP the RTU will simply accept the message with no authentication challenge.

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

A detailed technical summary for this CVE is being prepared.

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
St Ipm 6350 FirmwareOperating system
Affected:= 4.9.114
St Ipm 8460 FirmwareOperating system
Affected:= 6.0.202
Vt Mipm 135 D FirmwareOperating system
Affected:= 4.9.114
Vt Mipm 245 D FirmwareOperating system
Affected:= 4.9.114
Vt Ipm2m 213 D FirmwareOperating system
Affected:= 4.9.114
Vt Ipm2m 113 D FirmwareOperating system
Affected:= 4.9.114

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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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 · scoped
Patch available Apply the vendor patch
Vendor patch https →
Recommended fix Moderate confidence

Latest firmware version available from Red Lion support portal (vendor to confirm specific version containing RLCSIM-2023-05 patch)

  1. 1. Identify the exact model number and current firmware version of the Red Lion SixTRAK or VersaTRAK RTU device
  2. 2. Navigate to the Red Lion support portal at https://support.redlion.net/
  3. 3. Locate the firmware download section for your specific device model (St Ipm 6350, St Ipm 8460, Vt Mipm 135 D, Vt Mipm 245 D, Vt Ipm2m 213 D, or Vt Ipm2m 113 D)
  4. 4. Download the latest available firmware version from the vendor's official support page
  5. 5. Review the firmware release notes to confirm the version includes the CVE-2023-42770 fix (RLCSIM-2023-05)
  6. 6. Back up the current device configuration
  7. 7. Apply the firmware update following the vendor's documented upgrade procedure
  8. 8. After upgrade, verify that TCP/IP messages now require authentication similar to UDP/IP messages
Caveat Review release notes for any breaking changes between current version (4.9.114 or 6.0.202) and the target upgrade version

Generated from the published advisory — verify against the referenced sources before acting.

We can apply and verify the patch for your build — typical engagement from $2,300. Get the patch applied

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-42770 — 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-42770 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