Security readout for executives and security teams
Plain-English summary
CVE-2025-48571 is an Android 17 issue where a logic error could let a remote attacker intercept SMS messages. It does not require attacker privileges, but exploitation requires user interaction. Business impact is confidentiality loss for SMS-based communications, including one-time codes or sensitive messages.
Executive priority
Treat as a moderate mobile confidentiality risk. Prioritize environments where Android 17 devices receive sensitive SMS messages or SMS-based authentication codes, but do not escalate as actively exploited based on current supplied evidence.
Technical view
The CVE cites multiple functions in btm_sec.cc and classifies the weakness as CWE-693. The stated impact is remote information disclosure with low attack complexity, no privileges required, required user interaction, and low confidentiality impact. The provided data names Android 17 as affected.
Likely exposure
Exposure appears limited to Android 17 devices, based on the supplied affected-product data. Organizations should confirm deployed Android versions and OEM security bulletin coverage before assuming exposure or non-exposure.
Exploitation context
The bundle does not show CISA KEV listing or any cited evidence of active exploitation. The CVSS vector indicates network reachability, low complexity, no privileges, and required user interaction.
Researcher notes
Evidence is sparse beyond the CVE description, CVSS vector, CWE-693, Android 17 affected data, and Android bulletin reference. Do not infer exploitability details, exact user interaction, or fixed build identifiers without vendor bulletin confirmation.
Mitigation direction
- Review Google Android 17 bulletin and OEM advisories for corrected builds.
- Inventory Android 17 devices in managed and BYOD environments.
- Patch affected devices when vendor-supported updates are available.
- Reduce reliance on SMS for sensitive authentication where practical.
- Monitor vendor guidance for clarifications on affected builds.
Validation and detection
- Confirm whether any managed devices run Android 17.
- Check OEM patch level against the Android 17 security bulletin.
- Verify mobile device management reports for update compliance.
- Review authentication flows that still depend on SMS codes.
- Watch for vendor or CVE updates changing scope or severity.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-693: 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 lookupCVE-2025-48571 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 4.3 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N
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.
SSVC decision data
CVSS vector scores
1 official scoreWe 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.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N2.81.4CISA-ADPVulnerability scoring details
Base CVSS 3.1 score
4.3MediumVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://source.android.com/docs/security/bulletin/android-17CVE reference, google_android
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Protection Mechanism Failure
Protection Mechanism Failure represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.