LiveActive security incident?Get immediate response
CVE Record

CVE-2025-25370: An issue in realme GT 2 (RMX3311) running Android 14 with realme UI 5.0 allows a physically proximate attac...

An issue in realme GT 2 (RMX3311) running Android 14 with realme UI 5.0 allows a physically proximate attacker to obtain sensitive information via the show app only setting function.

MediumCVSS 4.6Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2025-25370 is an information disclosure issue reported on realme GT 2 RMX3311 running Android 14 with realme UI 5.0. A nearby attacker with physical access could obtain sensitive information through the “show app only” setting function. It is not described as remotely exploitable.

Executive priority

Treat as a moderate mobile-device privacy risk, not an enterprise-wide remote compromise. Prioritize validation where realme GT 2 devices are used in regulated, shared, executive, or field environments.

Technical view

The CVE is classified as CWE-200 with CVSS 3.1 score 4.6: AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N. The record names physical proximity as required and indicates confidentiality impact only. Official affected CPE/product metadata is not populated.

Likely exposure

Exposure appears limited to realme GT 2 RMX3311 devices on Android 14 with realme UI 5.0. Fleet impact cannot be confirmed from CPE data because the CVE record lists affected vendor/product/version as n/a.

Exploitation context

The source bundle does not show CISA KEV listing or cited evidence of active exploitation. The attack scenario requires physical proximity, which lowers broad internet risk but matters for lost, shared, inspected, or poorly controlled devices.

Researcher notes

The public record is sparse: one device model/configuration is described, but structured affected-product data is missing. No patch, workaround, exploit maturity, or vendor advisory is included in the supplied sources.

Mitigation direction

  • Check realme or device-management guidance for fixed builds or mitigations.
  • Prioritize updates for affected realme GT 2 devices when vendor guidance is available.
  • Restrict physical access to managed devices and enforce strong lock-screen controls.
  • Review mobile device policy for shared or kiosk-like device use.

Validation and detection

  • Inventory realme GT 2 RMX3311 devices and record Android/UI versions.
  • Confirm whether Android 14 with realme UI 5.0 is present.
  • Check vendor bulletins or build notes for CVE-2025-25370 references.
  • Assess sensitive-data exposure only in an authorized lab device.
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 · medium confidence lookup

CWE-200: Information exposure and cloud metadata lookup

Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. 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-2025-25370 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
4.6 (3.1)
Known Exploited
No
Published

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

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
3Timeline events
1ADP providers
2Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

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
4.6CVSS 3.1MediumCVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N0.93.6CISA-ADP

Vulnerability scoring details

Base CVSS 3.1 score

4.6Medium
CVSS 3.1 vector shape for CVE-2025-25370Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

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

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
cvssV3_1other:ssvc
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

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

CWE-200 · source CWE mapping

Exposure of Sensitive Information to an Unauthorized Actor

Exposure of Sensitive Information to an Unauthorized Actor represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.