LiveActive security incident?Get immediate response
CVE Record

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

Out-of-bounds write in libimagecodec.quram.so prior to SMR Apr-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

This is a Samsung mobile image-processing vulnerability that can let an attacker run code after a victim interacts with malicious content. It affects Samsung Mobile Devices before the April 2025 security release. CISA lists it as known exploited, so this is not just theoretical risk.

Executive priority

Treat this as urgent for Samsung fleets because known exploitation is documented and the impact is full device compromise. Patch availability and deployment coverage should be verified quickly, especially for high-value users.

Technical view

CVE-2025-21042 is a CWE-787 out-of-bounds write in Samsung's libimagecodec.quram.so. The CVSS 3.1 score is 8.8 with network attack vector, low complexity, no privileges required, and user interaction required. Successful exploitation can impact confidentiality, integrity, and availability.

Likely exposure

Likely exposure is Samsung Mobile Devices on Android 13, 14, or 15 that have not received SMR Apr-2025 Release 1. Exact exposure depends on device model, carrier, region, and patch level.

Exploitation context

Active exploitation is supported by the CISA KEV listing. Unit 42 reporting associates the issue with Landfall commercial-grade Android spyware. The provided sources do not include safe validation indicators beyond patch and version checks.

Researcher notes

The bundle identifies the vulnerable component, weakness class, CVSS vector, affected platform family, Samsung patch reference, KEV status, and Unit 42 spyware context. It does not provide exploit mechanics, detection logic, or complete model-level affected-device details.

Mitigation direction

  • Apply Samsung SMR Apr-2025 Release 1 or later where available.
  • Prioritize executive, security, legal, and high-risk user devices.
  • Check Samsung guidance for device-specific patch availability.
  • Restrict risky message and file handling until devices are patched.
  • Monitor CISA KEV and Samsung advisories for updates.

Validation and detection

  • Inventory Samsung Mobile Devices running Android 13, 14, or 15.
  • Verify each device security patch level against SMR Apr-2025 Release 1.
  • Confirm whether vulnerable devices are used by high-risk personnel.
  • Review MDM compliance reports for missing April 2025 Samsung updates.
  • Track remediation exceptions by model, carrier, and business owner.
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-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-21042 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
4Source 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-21042Attack 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 Apr-2025 Release in Android 13, 14, 15affected
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.