LiveActive security incident?Get immediate response
CVE Record

CVE-2023-30651: Out of bounds read and write in callgetTspsysfs of sysinput HAL service prior to SMR Jul-2023 Release 1 all...

Out of bounds read and write in callgetTspsysfs of sysinput HAL service prior to SMR Jul-2023 Release 1 allows local attackers to execute arbitrary code.

MediumCVSS 6.7Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2023-30651 is a Samsung Mobile device flaw fixed in the July 2023 Security Maintenance Release. A local attacker with high privileges could abuse an out-of-bounds read/write issue in a system input HAL service to run arbitrary code. The business risk is mainly from unmanaged or outdated Samsung devices.

Executive priority

Treat this as a mobile endpoint hygiene issue, not an internet-facing emergency. Prioritize patch compliance for Samsung fleets, especially executive, privileged, BYOD, and field devices that may hold sensitive data.

Technical view

The vulnerability is CWE-787 in callgetTspsysfs within Samsung's sysinput HAL service before SMR Jul-2023 Release 1. CVSS 3.1 is 6.7: local attack, low complexity, high privileges, no user interaction, and high confidentiality, integrity, and availability impact.

Likely exposure

Exposure is likely limited to Samsung Mobile devices that had not received SMR Jul-2023 Release 1 or later. The source bundle does not name specific models, Android versions, or carrier build identifiers, so validation requires device-level patch verification.

Exploitation context

The provided sources do not show known active exploitation, and the CVE is not listed as KEV in the bundle. The attack requires local access with high privileges, which reduces broad remote risk but matters on rooted, compromised, or poorly managed devices.

Researcher notes

Public details are sparse. The bundle identifies the vulnerable component, impact, CVSS vector, CWE, and Samsung fixed release, but does not provide affected model lists, proof-of-concept status, patch diff, or technical root-cause detail.

Mitigation direction

  • Apply Samsung SMR Jul-2023 Release 1 or a later supported security update.
  • Confirm Samsung devices remain in a supported update channel.
  • Restrict privileged local access on managed mobile devices.
  • Check Samsung's advisory for device-specific update availability.
  • Retire or isolate devices that cannot receive the fixed release.

Validation and detection

  • Inventory Samsung Mobile devices across MDM and asset systems.
  • Verify each device security patch level against SMR Jul-2023 Release 1 or later.
  • Identify rooted, unmanaged, or noncompliant Samsung devices for priority review.
  • Check Samsung advisory notes for applicable device families and update status.
  • Document unsupported devices requiring replacement or compensating controls.
Prepared
Confidence
medium
Sources
3

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-787: 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
description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. 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-30651 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
6.7 (3.1)
Known Exploited
No
Published

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

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
2Source 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
6.7CVSS 3.1MediumCVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H0.85.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

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

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

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

Products and packages named in the record

VendorProductVersion / packageStatus
Samsung MobileSamsung Mobile DevicesSMR Jul-2023 Release 1affected
Weakness

CWE details

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

CWE-787 · source CWE mapping

Out-of-bounds Write

Out-of-bounds Write represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.