CVE-2023-31408
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 · uneditedCleartext Storage of Sensitive Information in SICK FTMg AIR FLOW SENSOR with Partnumbers 1100214, 1100215, 1100216, 1120114, 1120116, 1122524, 1122526 allows a remote attacker to potentially steal user credentials that are stored in the user’s browsers local storage via cross-site-scripting attacks.
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 confidenceUser credentials are stored in cleartext in browser local storage on the affected SICK FTMg AIR FLOW SENSOR devices. When an attacker can inject malicious scripts (XSS) into the web interface, they can access and exfiltrate these stored 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< 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 modelAccess the device web interface or check the physical device labeling to confirm the model is one of: Ftmg Esd20axx, Esd25axx, Esn40sxx, Esn50sxx, Esr50sxx, Esr40sxx, or Esd15axxAffected if Device model matches one of the listed affected models
-
Check firmware versionLog into the device web interface and navigate to the system information or firmware version page. Compare the installed firmware version against version 2.0Affected if Firmware version is below 2.0 (e.g., 1.x)
-
Verify web interface is accessibleConfirm the device web management interface is reachable over HTTP/HTTPS on the networkAffected if Web interface is exposed and accessible to network attackers
-
Inspect browser local storage for credentialsIf you have access to the device web interface, open the browser developer tools (F12), go to Application tab, select Local Storage, and examine if user credentials or session tokens are stored in cleartextAffected if Cleartext credentials or sensitive tokens are present in local storage
-
Check for XSS vulnerability in web interfaceReview the web application for reflected or stored XSS vulnerabilities by testing input fields with malicious script payloads, or examine the application source code if accessibleAffected if XSS vulnerability exists that could allow theft of local storage contents
Device is affected if it is one of the listed SICK FTMg models running firmware below version 2.0 and the web interface stores credentials in browser local storage
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.
From vendor data2.0
Implement input validation and output encoding to prevent XSS attacks, add Content Security Policy headers, and avoid storing sensitive credentials in local storage—use secure session tokens or HTTP-only cookies instead.
- Consultation3.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 $4,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-31408 — 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-31408 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