LiveActive security incident?Get immediate response
CVE Record

CVE-2023-35699: Cleartext Storage on Disk in the SICK ICR890-4 could allow an unauthenticated attacker with local access to...

Cleartext Storage on Disk in the SICK ICR890-4 could allow an unauthenticated attacker with local access to the device to disclose sensitive information by accessing a SD card.

MediumCVSS 5.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2023-35699 means sensitive data may be stored unencrypted on the SD card of SICK ICR890-4 devices. The main business risk is information exposure if someone can physically access the device or removable storage. This is not described as a remote internet attack.

Executive priority

Treat this as a moderate physical-access confidentiality risk. Prioritize sites where devices are publicly reachable, shared with contractors, or deployed in less controlled operational environments. It is less urgent than remotely exploitable vulnerabilities but still relevant for sensitive industrial data protection.

Technical view

The issue is CWE-313 cleartext storage on disk in SICK ICR890-4. CVSS 3.1 is 5.3 with physical attack vector, low complexity, no privileges, no user interaction, changed scope, and high confidentiality impact. The source bundle does not identify integrity or availability impact.

Likely exposure

Exposure is most likely where SICK ICR890-4 devices are deployed in locations where unauthorized people can access the device or SD card. The bundle lists the product as affected but provides limited version detail beyond version 0/default affected status.

Exploitation context

The source bundle supports local physical access as the required attack condition. It does not support active exploitation, public exploit use, or remote exploitation. CISA KEV status is false in the provided data.

Researcher notes

Evidence is limited to the CVE record and SICK advisory references. The bundle does not name a patch, firmware version, or detailed remediation. Avoid assuming broader SICK product exposure. Validation should focus on product presence, physical media access, and vendor advisory follow-up.

Mitigation direction

  • Inventory SICK ICR890-4 deployments and confirm whether SD cards are physically accessible.
  • Review SICK PSIRT advisory SCA-2023-0006 for vendor remediation or compensating controls.
  • Restrict physical access to affected devices and removable storage media.
  • Handle removed SD cards as sensitive media until vendor guidance confirms exposure risk.
  • Update internal asset and risk records with the vendor advisory status.

Validation and detection

  • Confirm whether any SICK ICR890-4 devices are present in production or field environments.
  • Check device locations for unauthorized physical access paths to SD cards.
  • Review vendor advisory applicability against deployed device versions and configurations.
  • Assess what sensitive data could be present on removable storage.
  • Document non-exposure if no affected product is deployed.
Prepared
Confidence
high
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.

cwe · low confidence lookup

CWE-313: 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.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2023-35699 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
Medium
CVSS
5.3 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:C/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
0Timeline events
0ADP providers
4Source links

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
5.3CVSS 3.1MediumCVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N0.94Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.3Medium
CVSS 3.1 vector shape for CVE-2023-35699Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:C/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

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
SICK AGICR890-40affected
Weakness

CWE details

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

CWE-313 · source CWE mapping

Cleartext Storage in a File or on Disk

Cleartext Storage in a File or on Disk represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.