CVE-2023-5101
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 · uneditedFiles or Directories Accessible to External Parties in RDT400 in SICK APU allows an unprivileged remote attacker to download various files from the server via 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 confidenceThe SICK APU RDT400 device has an information disclosure vulnerability where an unprivileged remote attacker can download arbitrary files from the server through HTTP requests without authentication. This exposes sensitive system files, configuration data, and potentially credentials to unauthenticated users.
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< 4.0.0.6CVSS 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
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the SICK device modelLocate the device label, web interface header, or system information page showing the model number. Confirm it is either 'SICK APU RDT400' or 'Sick Apu0200'.Affected if The device model is SICK APU RDT400 or Apu0200.
-
Check the firmware versionAccess the device web interface and navigate to the firmware or system information section. Record the installed firmware version number.Affected if The firmware version is lower than 4.0.0.6 (for example, 4.0.0.5, 3.x.x, etc.).
-
Verify HTTP web interface accessibilityAttempt to access the device over HTTP (port 80) or HTTPS from a remote location. Confirm the web interface responds without requiring login credentials.Affected if The web interface is reachable and does not prompt for authentication.
-
Test unauthenticated file download capabilitySend an HTTP GET request to a known file path on the device (for example, /download?file=../../etc/passwd or similar file retrieval endpoint). Observe if the server returns file contents without authentication.Affected if Arbitrary files can be retrieved via HTTP without providing valid credentials.
A user is affected if they have a SICK APU RDT400 or Apu0200 device running firmware version lower than 4.0.0.6 with the web interface accessible without authentication.
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.
dbcve · scoped4.0.0.6
Restrict network access to the RDT400 web interface, implement proper authentication and authorization controls, and apply vendor-supplied patches or firmware updates to remediate the file download vulnerability.
Apu0200 Firmware 4.0.0.6 or later
- Identify the current firmware version of the SICK APU (Apu0200) device by accessing the device management interface or checking system information
- Navigate to the official SICK support website (sick.com) and locate the firmware download section for the Apu0200 product
- Download the firmware version 4.0.0.6 or a later stable release that addresses the vulnerability
- Follow the vendor's documented firmware upgrade procedure, typically involving uploading the firmware file through the device's web interface or using the SICK deployment tool
- After upgrading, verify the firmware version has been successfully applied and confirm the vulnerability is resolved
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-5101 — 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-5101 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