CVE-2023-23446
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 · uneditedImproper Access Control in SICK FTMg AIR FLOW SENSOR with Partnumbers 1100214, 1100215, 1100216, 1120114, 1120116, 1122524, 1122526 allows an unprivileged remote attacker to download files by using a therefore unpriviledged account 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 confidenceImproper access control in SICK FTMg AIR FLOW sensors allows remote unprivileged attackers to download arbitrary files via the REST interface by leveraging unprivileged accounts, bypassing intended authorization boundaries.
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
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify device model and firmware versionAccess the device's web interface or REST API and retrieve the model identifier and firmware version from the system information or status endpoint. For CLI access, use the appropriate command to display firmware version (e.g., 'show version' or similar).Affected if The device model matches any of the affected variants (Esd20axx, Esd25axx, Esn40sxx, Esn50sxx, Esr50sxx, Esr40sxx, Esd15axx) AND the firmware version is below 2.0.
-
Verify REST interface is network accessibleCheck if the device's REST API port (commonly 80/tcp or 443/tcp for HTTPS) is reachable from untrusted networks. Use network scanning tools (nmap) or review firewall rules and network segmentation configurations.Affected if The REST interface is exposed to networks that untrusted or unauthorized users can access.
-
Review configured user accounts and privilege levelsAccess the device's user management interface or use the REST API to enumerate accounts. Identify accounts that are NOT in administrative or privileged roles.Affected if There are one or more non-administrative or unprivileged user accounts configured on the device.
-
Test arbitrary file download with unprivileged accountUsing a non-administrative account, attempt to access file paths outside the intended scope via the REST API (e.g., trying to retrieve system configuration files, log files, or other sensitive files not meant for that user level). Compare the HTTP response codes and returned content against expected access restrictions.Affected if An unprivileged account can successfully retrieve files that should be restricted to administrative or higher privilege levels.
-
Confirm REST API authorization boundaries are enforcedExecute REST API requests that should require elevated privileges (such as accessing system files, configuration backups, or diagnostic data) using a standard unprivileged account. Verify whether the device correctly denies these requests.Affected if The device allows unprivileged accounts to perform operations that should be restricted to privileged users, indicating broken authorization.
The environment is affected if a SICK FTMg sensor model (Esd20axx, Esd25axx, Esn40sxx, Esn50sxx, Esr50sxx, Esr40sxx, or Esd15axx) is running firmware version below 2.0, has unprivileged user accounts, and the REST interface is network-accessible with improper authorization enforcement.
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
Restrict network exposure of the device's REST interface, implement proper role-based access controls ensuring unprivileged accounts cannot access sensitive files, and apply vendor security updates if available.
Firmware version 2.0 or later for the respective FTMg model (1100214, 1100215, 1100216, 1120114, 1120116, 1122524, 1122526)
- Identify the specific FTMg sensor model (Esd20axx, Esd25axx, Esn40sxx, Esn50sxx, Esr50sxx, Esr40sxx, or Esd15axx) currently deployed
- Check the current firmware version of the affected sensor via the SICK management interface or documentation
- Download the firmware version 2.0 or later from the official SICK support website (sick.com) for your specific part number
- Follow SICK's official firmware update procedure documented in the sensor's operation manual
- After upgrading, verify that unprivileged accounts can no longer download files via the REST interface
- Confirm the firmware version has been successfully updated to 2.0 or higher
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-23446 — 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-23446 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