CVE-2023-31408: Cleartext Storage of Sensitive Information in SICK FTMg AIR FLOW SENSOR with
Partnumbers 1100214, 1100215,...
Cleartext 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.
Security readout for executives and security teams
Plain-English summary
This issue concerns certain SICK FTMg air flow sensors storing sensitive user credentials in browser local storage in cleartext. If an attacker can trigger cross-site scripting against a user’s browser, those stored credentials could potentially be stolen. The supplied sources rate it medium severity, and do not show CISA KEV listing or active exploitation.
Executive priority
Treat this as a targeted operational-technology credential exposure issue, not an internet-wide emergency based on the supplied evidence. Prioritize inventory, access restriction, and vendor guidance review where affected SICK sensors support production operations.
Technical view
CVE-2023-31408 is CWE-312 in listed SICK FTMg air flow sensor models and part numbers. The source bundle says all firmware versions are affected. The stated attack path is remote credential theft from browser local storage via cross-site scripting. CVSS 3.1 is 5.3 with network access, low complexity, no privileges, and no user interaction in the vector.
Likely exposure
Exposure is most likely where affected SICK FTMg sensor web interfaces are administered from browsers that retain credentials in local storage, especially if those interfaces are reachable from broader operational or corporate networks.
Exploitation context
The supplied bundle does not identify public exploitation or KEV status. It describes a potential credential-theft outcome through cross-site scripting against credentials stored in browser local storage. Evidence is incomplete on exploit availability, affected deployment prevalence, and vendor-fixed firmware availability.
Researcher notes
Key gaps are whether SICK provides a fixed firmware or only compensating controls, and whether the referenced cross-site-scripting condition is a separate CVE or attack precondition. Do not infer active exploitation from the provided data.
Mitigation direction
Check SICK PSIRT and advisory SCA-2023-0004 for official remediation guidance.
Inventory listed FTMg part numbers and assume all firmware versions are affected.
Restrict network access to sensor management interfaces to trusted administrative paths.
Avoid retaining sensor credentials in browsers where operationally feasible.
Clear browser local storage after administering affected devices.
Monitor vendor guidance for firmware or configuration updates.
Validation and detection
Confirm whether listed SICK FTMg models or part numbers exist in asset inventory.
Verify whether administrative browsers store sensor credentials in local storage.
Review network paths to affected sensor management interfaces.
Check whether current firmware or vendor guidance changes affected status.
Look for unusual administrative access to affected sensor interfaces.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-312: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
ScoreVersionSeverityVectorExploitImpactSource
5.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L3.91.4SICK AG