CVE-2023-43700
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 · uneditedMissing Authorization in RDT400 in SICK APU allows an unprivileged remote attacker to modify data via HTTP requests that no not require authentication.
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 confidenceMissing authorization in the RDT400 component of SICK APU allows unauthenticated remote attackers to modify device data via HTTP requests. The vulnerability stems from missing authentication checks on certain HTTP endpoints, enabling any remote user to alter configuration or operational data without credentials.
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
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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 APU device modelAccess the device web interface or check device labeling/documentation to confirm the exact model number is Apu0200Affected if The device is a SICK Apu0200 unit
-
Check the installed firmware versionLog into the device web interface and navigate to the firmware/version information page, or use the device's CLI or management interface to query the firmware versionAffected if The firmware version is below 4.0.0.6 (for example, 4.0.0.5 or earlier)
-
Verify HTTP management interface accessibilityAttempt to access the device's HTTP web interface from a remote host using a browser or HTTP client without providing any credentialsAffected if The HTTP interface loads and presents device pages or endpoints without requiring authentication
-
Test for unauthenticated configuration modificationSend an HTTP POST request to common configuration endpoints (such as those for network settings, device parameters, or RDT400-related functions) without including any authentication tokens or credentialsAffected if The device accepts and processes the configuration changes without rejecting the request due to missing authentication
If the device is a SICK Apu0200 with firmware version lower than 4.0.0.6 and its HTTP interface is accessible without authentication, the environment is affected by this vulnerability.
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
Apply vendor-provided firmware/patch for RDT400 to enforce proper authentication on HTTP endpoints. Implement network segmentation to restrict access to the SICK APU device to trusted hosts only as a compensating control.
Firmware version 4.0.0.6 or later for SICK APU (Apu0200)
- Obtain the official firmware update package (version 4.0.0.6 or later) from SICK's support portal at sick.com
- Access the SICK APU device management interface via the web browser
- Navigate to the firmware update or system maintenance section
- Upload and apply the firmware version 4.0.0.6
- Verify the firmware update was applied successfully by checking the device status
- Confirm the HTTP endpoints now require proper authentication
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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 $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-43700 — 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-43700 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