LiveActive security incident?Get immediate response
CVE Record

CVE-2023-30645: Heap out of bound write vulnerability in IpcRxIncomingCBMsg of RILD prior to SMR Jul-2023 Release 1 allows...

Heap out of bound write vulnerability in IpcRxIncomingCBMsg of RILD prior to SMR Jul-2023 Release 1 allows attackers to execute arbitrary code.

HighCVSS 7.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

This Samsung mobile vulnerability could let a local, low-privileged attacker execute code through the RILD cellular component. The published severity is high because successful exploitation could affect confidentiality, integrity, and availability. Organizations with managed Samsung fleets should verify devices received the July 2023 Samsung Mobile Security Release or later.

Executive priority

Treat this as a high-priority mobile fleet hygiene issue, not a confirmed emergency. The impact is serious, but the provided evidence does not show active exploitation. Require patch compliance and exceptions reporting for Samsung devices.

Technical view

CVE-2023-30645 is a heap out-of-bounds write in IpcRxIncomingCBMsg of Samsung RILD. The CVSS 3.1 vector is local, low complexity, low privileges, no user interaction, with high CIA impact. The issue is described as affecting Samsung Mobile Devices prior to SMR Jul-2023 Release 1.

Likely exposure

Exposure is most likely on Samsung mobile devices that have not been updated to SMR Jul-2023 Release 1 or later. The source bundle does not provide specific model lists, carrier variants, or Android versions, so asset validation should focus on Samsung patch level.

Exploitation context

The source bundle does not show CISA KEV listing or cite active exploitation. CVSS indicates exploitation requires local access and low privileges, with no user interaction. Public sources in the bundle do not provide exploit details, proof of concept status, or observed campaign evidence.

Researcher notes

Key gaps are the absence of affected model granularity, exploit telemetry, and detailed patch notes. The vulnerability maps to CWE-787 and involves RILD message handling. Validation should avoid exploit reproduction and rely on patch-level and vendor-advisory confirmation.

Mitigation direction

  • Update Samsung devices to SMR Jul-2023 Release 1 or later.
  • Use MDM compliance rules to require current Samsung security patch levels.
  • Prioritize devices used by executives, administrators, and high-risk mobile workers.
  • Check Samsung guidance for model-specific availability and carrier rollout status.

Validation and detection

  • Inventory Samsung mobile devices and record security patch level.
  • Confirm each device has SMR Jul-2023 Release 1 or later installed.
  • Identify unsupported or carrier-delayed devices that cannot receive the update.
  • Review MDM reports for noncompliant or stale Samsung patch levels.
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-30645 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.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:L/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
7.8CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

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

Vector: CVSS:3.1/AV:L/AC:L/PR:L/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.