LiveActive security incident?Get immediate response
CVE Record

CVE-2023-30663: Improper input validation vulnerability in OemPersonalizationSetLock in libsec-ril prior to SMR Jul-2023 Re...

Improper input validation vulnerability in OemPersonalizationSetLock in libsec-ril prior to SMR Jul-2023 Release 1 allows local attackers to cause an Out-Of-Bounds write.

MediumCVSS 5.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This is a Samsung Mobile vulnerability where weak input checking in a radio-interface library could let a local, low-privileged attacker corrupt memory. Business impact is moderate because exploitation requires local access, but affected managed or BYOD Samsung devices should be brought to the July 2023 security release level.

Executive priority

Treat this as a routine but necessary mobile patching item. It is not presented as internet-exploitable or actively exploited in the provided sources, but outdated Samsung devices may carry avoidable local compromise risk.

Technical view

CVE-2023-30663 is CWE-20 improper input validation in OemPersonalizationSetLock within libsec-ril before Samsung SMR Jul-2023 Release 1. The reported consequence is an out-of-bounds write with limited confidentiality, integrity, and availability impact. CVSS 3.1 is 5.3 with local attack vector and low privileges required.

Likely exposure

Exposure is limited to Samsung Mobile Devices running software before SMR Jul-2023 Release 1. The source bundle does not identify specific device models, Android versions, carrier variants, or enterprise configurations, so validation should use actual device patch levels rather than assumptions.

Exploitation context

The CVSS vector indicates local access, low privileges, and no user interaction. The CVE is not listed as KEV in the provided bundle, and no cited source states active exploitation. Public evidence in the bundle does not establish exploit availability.

Researcher notes

The public data is sparse: it names libsec-ril, OemPersonalizationSetLock, improper input validation, and out-of-bounds write. It does not provide model coverage, trigger conditions, patch diff detail, or exploitation evidence. Avoid extrapolating beyond Samsung's July 2023 advisory and CVE metadata.

Mitigation direction

  • Deploy Samsung SMR Jul-2023 Release 1 or newer where available.
  • Check Samsung Mobile Security Updates for device-specific update availability.
  • Require managed Samsung devices to meet the July 2023 patch level.
  • Restrict access for devices that cannot receive the vendor update.
  • Monitor Samsung guidance for any revised affected-device information.

Validation and detection

  • Inventory Samsung Mobile Devices in managed and BYOD environments.
  • Record each device security patch level from MDM or device settings.
  • Confirm affected devices are at SMR Jul-2023 Release 1 or newer.
  • Identify unsupported or non-updatable Samsung devices for risk treatment.
  • Document exceptions and compensating controls for remaining exposure.
Prepared
Confidence
high
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-20: 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-30663 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:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L

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

Vulnerability scoring details

Base CVSS 3.1 score

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

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

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-20 · source CWE mapping

Improper Input Validation

Improper Input Validation represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.