CVE-2023-23447
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 · uneditedUncontrolled Resource Consumption in SICK FTMg AIR FLOW SENSOR with Partnumbers 1100214, 1100215, 1100216, 1120114, 1120116, 1122524, 1122526 allows an unprivileged remote attacker to influence the availability of the webserver by invocing several open file requests via the REST interface.
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 confidenceUnauthenticated remote attacker can cause denial of service by sending multiple file request calls to the REST interface, exhausting server resources and affecting webserver availability.
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< 2.0< 2.0< 2.0< 2.0< 2.0< 2.0< 2.0CVSS 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
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
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 device model and firmware versionAccess the device web interface or use the SICK configuration tool to view system information. Look for the exact model number (Esd20axx, Esd25axx, Esn40sxx, Esn50sxx, Esr50sxx, Esr40sxx, or Esd15axx) and the installed firmware version.Affected if The firmware version is below 2.0 (e.g., 1.x.x) AND the model is one of the affected Ftmg variants.
-
Confirm REST interface is accessibleAttempt to reach the device REST API endpoint (typically at /api/v1/ or similar path on the device IP). Verify the interface responds to HTTP requests without authentication.Affected if The REST interface is exposed and responds to unauthenticated requests.
-
Check for resource exhaustion indicatorsReview device logs or system monitoring for signs of DoS conditions: high CPU usage, memory exhaustion, slow response times, or connection timeouts when multiple file request calls are made.Affected if Device shows degraded performance or unresponsiveness under repeated REST file request calls.
-
Verify network exposureDetermine if the device REST interface is accessible from untrusted networks (e.g., directly from the internet or outside the local production network segment).Affected if The REST interface is reachable from networks where unauthenticated attackers could send requests.
You are affected if you have a Sick Ftmg device (Esd20axx, Esd25axx, Esn40sxx, Esn50sxx, Esr50sxx, Esr40sxx, or Esd15axx) running firmware version below 2.0 with the REST interface exposed to network locations where attackers could send repeated file request calls.
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 · scoped2.0
Implement network segmentation and rate limiting on the REST API; contact SICK for firmware updates addressing the uncontrolled resource consumption.
Firmware version 2.0 or later for the specific FTMg model (Esd20axx, Esd25axx, Esn40sxx, Esn50sxx, Esr50sxx, Esr40sxx, or Esd15axx)
- Identify the specific FTMg device model (Esd20axx, Esd25axx, Esn40sxx, Esn50sxx, Esr50sxx, Esr40sxx, or Esd15axx) requiring remediation
- Access the SICK product support portal at sick.com to obtain the firmware version 2.0 or later for your specific device model
- Review the firmware upgrade instructions provided by SICK for the FTMg series devices
- Backup current device configuration if supported by the firmware upgrade process
- Upload and install firmware version 2.0 or later via the device's web interface or management tool
- Verify the firmware installation was successful and the device is operational
- Confirm the REST interface vulnerability is remediated by testing normal file request handling
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-23447 — 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-23447 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