CVE-2023-23449
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 · uneditedObservable Response Discrepancy in SICK FTMg AIR FLOW SENSOR with Partnumbers 1100214, 1100215, 1100216, 1120114, 1120116, 1122524, 1122526 allows a remote attacker to gain information about valid usernames by analyzing challenge responses from the server 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 sensors with specified partnumbers have an observable response discrepancy vulnerability in their REST interface authentication. A remote attacker can send authentication requests and analyze differences in server challenge responses to determine which usernames are valid on the system, enabling username enumeration.
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
- 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 device modelLocate the physical device or check network inventory for SICK FTMg AIR FLOW sensors. Confirm the part number matches one of these: Esd20axx, Esd25axx, Esn40sxx, Esn50sxx, Esr50sxx, Esr40sxx, Esd15axx.Affected if The device is a SICK FTMg sensor with any of these part numbers.
-
Check the installed firmware versionAccess the device's web interface or use SNMP/CLI to retrieve the firmware version. Compare it against the affected version range of < 2.0.Affected if The firmware version is below 2.0.
-
Verify REST interface accessibilityAttempt to access the device's REST API endpoint (typically on port 443 or 80) from a remote location. Check network access controls and firewall rules surrounding the device.Affected if The REST interface is reachable from an untrusted network.
-
Test for username enumeration response differencesSend authentication requests to the REST interface with valid and invalid usernames. Compare HTTP response codes, response times, or error messages for differences. Use two test cases: one with a known-valid username and one with a random invalid username.Affected if The responses differ between valid and invalid usernames, revealing which usernames exist on the system.
You are affected if you have a SICK FTMg sensor with any of the listed part numbers running firmware version below 2.0, and the REST interface is accessible and exhibits different authentication responses based on username validity.
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
The vendor must issue a firmware update that normalizes authentication responses to not reveal username validity. Pending a fix, network-segment the device's management interface and restrict REST access to trusted networks to reduce exposure.
Firmware version 2.0 or later for the respective FTMg model
- 1. Identify the specific FTMg AIR FLOW SENSOR model (Esd20axx, Esd25axx, Esn40sxx, Esn50sxx, Esr50sxx, Esr40sxx, or Esd15axx) in use
- 2. Obtain the firmware upgrade file from the official SICK support portal at sick.com
- 3. Follow SICK's standard firmware update procedure for the FTMg device, typically involving the device's web interface or SICK software tools
- 4. After upgrade, verify the firmware version is 2.0 or later
- 5. Test the REST interface to confirm proper authentication behavior (both valid and invalid usernames should produce consistent response timing/format)
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.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 $4,880.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-23449 — 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-23449 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