LiveActive security incident?Get immediate response
CVE Record

CVE-2023-31412: The LMS5xx uses weak hash generation methods, resulting in the creation of insecure hashs.

The LMS5xx uses weak hash generation methods, resulting in the creation of insecure hashs. If an attacker manages to retrieve the hash, it could lead to collision attacks and the potential retrieval of the password.

HighCVSS 7.5Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

SICK LMS5xx devices reportedly use weak password-hash generation. If an attacker obtains a stored hash, the weakness could help recover the password, creating a serious confidentiality risk for exposed devices.

Executive priority

Prioritize this for environments where LMS5xx devices are network-accessible or support safety, operational, or sensitive sensing workflows. The issue is high severity, but active exploitation is not evidenced in the provided sources.

Technical view

CVE-2023-31412 affects SICK AG LMS5xx in all firmware versions listed in the CVE bundle. The issue is weak hash generation, rated CVSS 3.1 7.5 with network attack vector, no privileges, no user interaction, and high confidentiality impact.

Likely exposure

Organizations using SICK LMS5xx devices should assume affected exposure, especially where device management or data paths are reachable from untrusted networks. The bundle does not identify specific firmware exceptions.

Exploitation context

The source bundle does not show CISA KEV listing or cited evidence of active exploitation. Risk depends on whether attackers can retrieve hashes and then use the weak hashing to recover credentials.

Researcher notes

The key unknown is how hashes can be retrieved in real deployments. The CVE supports weak hashing and possible password recovery after hash access, but the bundle does not provide exploit status, CWE mapping, or confirmed patch details.

Mitigation direction

  • Check SICK PSIRT and advisory SCA-2023-0007 for current vendor guidance.
  • Treat all LMS5xx firmware versions as affected until verified otherwise.
  • Restrict LMS5xx network reachability to trusted management networks only.
  • Rotate related credentials if hash exposure is suspected or confirmed.
  • Monitor for unauthorized access attempts against LMS5xx management interfaces.

Validation and detection

  • Inventory SICK LMS5xx assets and record firmware versions.
  • Confirm whether any LMS5xx interfaces are reachable from untrusted networks.
  • Review SICK advisory SCA-2023-0007 for affected-status and remediation details.
  • Check logs for suspicious authentication or configuration access.
  • Document compensating controls where vendor remediation is unavailable or pending.
Prepared
Confidence
medium
Sources
5

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.

description · low confidence lookup

Credential and access behavior lookup

The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2023-31412 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

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.

1CVSS vectors
3Timeline events
2ADP providers
4Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: yesTechnical Impact: partial

CVSS vector scores

1 official score

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
7.5CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N3.93.6SICK AG

Vulnerability scoring details

Base CVSS 3.1 score

7.5High
CVSS 3.1 vector shape for CVE-2023-31412Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CVECVE Program Container
CISA-ADPCISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
SICK AGLMS5xxall firmware versionsaffected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.