dbcve.org
Apu0200 FirmwareOperating system · Sick

CVE-2023-43697

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 →
74/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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
Modification of Assumed-Immutable Data (MAID) in RDT400 in SICK APU allows an unprivileged remote attacker to make the site unable to load necessary strings via changing file paths using HTTP requests.

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

The RDT400 component in SICK APU devices has a MAID vulnerability where an unprivileged remote attacker can manipulate file paths through HTTP requests, causing the site to fail loading necessary string resources. This represents a path traversal or manipulation issue that compromises data integrity assumptions.

MitigationImplement strict input validation on file path parameters in HTTP requests and ensure critical string resource files are treated as immutable with proper access controls at the filesystem level.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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 SICK APU device model
    Access the device web interface or check device documentation/labels to confirm the model is Apu0200
    Affected if Device model is Apu0200 and firmware version is below 4.0.0.6
  2. Check firmware version
    Log into the device admin panel or use SICK diagnostic tools to retrieve the installed firmware version number
    Affected if Firmware version is less than 4.0.0.6
  3. Verify RDT400 component is active
    Check the device web interface or configuration for the RDT400 component status - look for RDT400 references in the HTTP service or device diagnostics
    Affected if RDT400 component is running and accessible via HTTP
  4. Confirm HTTP interface exposure
    Attempt to access the device HTTP service on common ports (80/443) or check network configuration for exposed web services
    Affected if HTTP interface is externally accessible or on the local network without segmentation
  5. Test for path traversal response
    Send a crafted HTTP request with path traversal sequences (e.g., ../../) to endpoints that accept file path parameters - observe if the device returns unexpected errors or fails to load string resources
    Affected if HTTP requests with path traversal characters cause resource loading failures or unusual error responses

Device is affected if it is a SICK Apu0200 with firmware below 4.0.0.6, has the RDT400 component enabled, and exposes an HTTP interface that exhibits path traversal behavior.

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

Implement strict input validation on file path parameters in HTTP requests and ensure critical string resource files are treated as immutable with proper access controls at the filesystem level.

Recommended fix Moderate confidence

Firmware version 4.0.0.6 or later

  1. Access the SICK APU device management interface or use the official SICK firmware update process
  2. Locate the firmware update section for the Apu0200 or RDT400 device
  3. Upload and install firmware version 4.0.0.6 or later
  4. Verify the firmware installation was successful
  5. Restart the device if required to complete the update

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

Fix this in Apu0200 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

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 locally
dbcve dependency scanner

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