CVE-2023-23445
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 gain unauthorized access to data fields 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 · high confidenceThe SICK FTMg AIR FLOW Sensor devices have improper access control on their REST interface, allowing unprivileged authenticated users to access sensitive data fields outside their intended permissions. This is a broken access control vulnerability where the REST API fails to properly enforce authorization checks before returning data to 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< 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 the exact FTMg device modelLocate the device label on the physical unit or check the device information page in the web interface to confirm the model number (e.g., Esd20axx, Esd25axx, Esn40sxx, Esn50sxx, Esr50sxx, Esr40sxx, Esd15axx)Affected if The model matches one of the affected variants: Esd20axx, Esd25axx, Esn40sxx, Esn50sxx, Esr50sxx, Esr40sxx, or Esd15axx
-
Determine the installed firmware versionAccess the device web interface and navigate to the firmware/version information section, or query the REST API endpoint that exposes device information (commonly /api/device/info or similar)Affected if The firmware version is below 2.0 (for example, 1.x.x or any version number less than 2.0)
-
Confirm the REST interface is accessibleAttempt to reach the device REST API by sending an HTTP request to the device IP (for example, GET http://<device-ip>/api/) and verify you receive a JSON or XML responseAffected if The REST API responds and is reachable on the network
-
Verify presence of multiple user accounts with different privilege levelsLog into the device administration interface or query the user management API endpoints to list configured users and their assigned roles or permission levelsAffected if More than one user account exists, or there are users with roles other than full administrator
-
Test for authorization bypassUsing a non-administrator (low-privilege) authenticated account, query REST API endpoints that should return sensitive data (such as system configuration, diagnostics, or calibration data) and observe whether the API returns information without enforcing role-based restrictionsAffected if A user with limited privileges can successfully retrieve sensitive data that should be restricted to administrator or higher-privilege roles
Your environment is affected if you have a SICK FTMg device model from the affected list running firmware version below 2.0, with the REST interface enabled and at least one non-administrator user account that can access restricted data.
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 proper role-based access control (RBAC) on REST API endpoints to verify user permissions before returning data, and apply vendor-supplied firmware updates that address the access control flaw.
Firmware version 2.0 or later for FTMg Esd20axx, Esd25axx, Esn40sxx, Esn50sxx, Esr50sxx, Esr40sxx, and Esd15axx
- Identify the specific FTMg model (Esd20axx, Esd25axx, Esn40sxx, Esn50sxx, Esr50sxx, Esr40sxx, or Esd15axx) currently deployed
- Locate the firmware update on SICK's official support portal (sick.com) for the specific model number
- Download firmware version 2.0 or later for the affected device
- Review SICK's firmware upgrade documentation for any prerequisite steps
- Upload and apply the firmware update through the device's management interface
- After upgrade, verify the REST interface now properly enforces access controls for unprivileged accounts
- Confirm the firmware version has been successfully updated to >= 2.0
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-23445 — 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-23445 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