dbcve.org
Apu0200 FirmwareOperating system · Sick

CVE-2023-5100

MEDIUM · 6.5 CVSS v3.1 Published 2023-10-09
Fix available
A fix is available. Upgrade to 4.0.0.6 or later.
See remediation →
72/100
Remediation priority · Elevated
Remotely reachable No privileges

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
Cleartext Transmission of Sensitive Information in RDT400 in SICK APU allows an unprivileged remote attacker to retrieve potentially sensitive information via intercepting network traffic that is not encrypted.

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 confidence

The SICK APU RDT400 device transmits sensitive information in cleartext over the network without encryption, allowing any unprivileged remote attacker on the network path to intercept and read potentially sensitive data.

MitigationEnable TLS/SSL encryption for all network communications on the RDT400 device, or isolate the device on a protected network segment to prevent unauthorized traffic interception.

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
Apu0200 FirmwareOperating system
Affected:< 4.0.0.6

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/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 checks

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

  1. Identify SICK APU RDT400 or Apu0200 device on the network
    Scan network for devices displaying SICK APU0200 or RDT400 identifiers, or review network asset inventory for these model numbers
    Affected if The device is a SICK Apu0200 or RDT400 model
  2. Check the installed firmware version
    Access the device web interface or administrative console and locate the firmware version information, or query the device via its management protocol
    Affected if Firmware version is below 4.0.0.6
  3. Verify TLS/SSL encryption is enabled
    Navigate to network security settings on the device management interface and confirm whether encryption is configured for communications
    Affected if TLS/SSL encryption is disabled or set to off
  4. Capture network traffic to confirm cleartext transmission
    Use a network packet sniffer on the same network segment to capture outgoing traffic from the device and inspect for unencrypted sensitive data
    Affected if Sensitive data such as credentials or configuration details appears in cleartext in captured packets

Environment is affected if a SICK Apu0200 device with firmware below version 4.0.0.6 has TLS/SSL encryption disabled, resulting in cleartext transmission of sensitive data.

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.

dbcve · scoped
Upgrade available Upgrade to 4.0.0.6 or later
Fixed in 4.0.0.6
Interim mitigation

Enable TLS/SSL encryption for all network communications on the RDT400 device, or isolate the device on a protected network segment to prevent unauthorized traffic interception.

Recommended fix Moderate confidence

Apu0200 Firmware 4.0.0.6 or later

  1. 1. Identify the current firmware version of the SICK APU device (Apu0200) by accessing the device management interface or checking system documentation.
  2. 2. Navigate to the official SICK support website (sick.com) and locate the firmware download section for the Apu0200 product.
  3. 3. Download firmware version 4.0.0.6 or later from the SICK support portal.
  4. 4. Consult the device's firmware upgrade instructions, typically found in the product manual or SICK support documentation.
  5. 5. Apply the firmware update to the Apu0200 device following the vendor's recommended procedure, which typically involves uploading the firmware file through the device's web interface or management tool.
  6. 6. After updating, verify that the device is running firmware version 4.0.0.6 or higher.
  7. 7. Once updated, ensure that network communications to/from the device use encrypted protocols (such as HTTPS, SSH, or other encrypted channels) to maintain security.

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

Fix this in Apu0200 Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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