LiveActive security incident?Get immediate response
CVE Record

CVE-2025-21043: Out-of-bounds write in libimagecodec.quram.so prior to SMR Sep-2025 Release 1 allows remote attackers to ex...

Out-of-bounds write in libimagecodec.quram.so prior to SMR Sep-2025 Release 1 allows remote attackers to execute arbitrary code.

HighCVSS 8.8Known exploitedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

Samsung mobile devices had a serious image-processing flaw that could let a remote attacker run code if a user interacted with malicious content. CISA lists it as known exploited, so this is not theoretical. The clearest business action is to confirm Samsung Android devices are on the September 2025 security maintenance release or later.

Executive priority

Treat this as urgent mobile fleet patching. Known exploitation raises business risk, but available sources do not show wormable behavior or exploitation without user interaction. Focus on fast update coverage and exception tracking.

Technical view

CVE-2025-21043 is a CWE-787 out-of-bounds write in Samsung's libimagecodec.quram.so before SMR Sep-2025 Release 1. CVSS 3.1 is 8.8 with network attack vector, low complexity, no privileges, and user interaction required. Impact is confidentiality, integrity, and availability compromise through arbitrary code execution.

Likely exposure

Samsung Mobile Devices running Android 13, 14, 15, or 16 before SMR Sep-2025 Release 1 are in scope. The provided sources do not list exact models, regions, carriers, or app-level exposure conditions.

Exploitation context

Active exploitation is supported by CISA KEV listing for CVE-2025-21043. The public bundle does not provide exploit details, indicators, attacker targeting, or delivery method beyond remote attack and required user interaction.

Researcher notes

The important gap is specificity: sources identify the vulnerable library and release boundary, but not exact models, file formats, delivery channel, IOCs, or exploit chain. Avoid assuming unsupported device lists or compensating controls beyond vendor guidance.

Mitigation direction

  • Apply Samsung SMR Sep-2025 Release 1 or later to affected devices.
  • Prioritize managed Samsung Android 13 through 16 devices.
  • Use MDM compliance rules to block outdated patch levels.
  • Check Samsung guidance for model-specific availability and constraints.
  • Review CISA KEV handling requirements for regulated environments.

Validation and detection

  • Inventory Samsung mobile devices and Android versions.
  • Verify each device security patch level against SMR Sep-2025 Release 1 or later.
  • Confirm MDM reports match device-side patch status.
  • Track exceptions where carrier or model updates are unavailable.
  • Monitor vendor and CISA pages for updated guidance.
Prepared
Confidence
high
Sources
4

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-2025-21043 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
8.8 (3.1)
Known Exploited
Yes
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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
3Source links

CISA KEV status

Status
Known exploited
Source
CISA / ADP
Date added
Not provided

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

Vulnerability scoring details

Base CVSS 3.1 score

8.8High
CVSS 3.1 vector shape for CVE-2025-21043Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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 Sep-2025 Release in Android 13, 14, 15, 16affected
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.