Security readout for executives and security teams
Plain-English summary
Dolphin Browser for Android 12.0.2 mishandles Android Intent URIs. A malicious link could make the browser open internal screens that were meant to stay private, increasing risk on devices where this old browser version is still installed.
Executive priority
Treat as a targeted mobile browser exposure, not a broad enterprise emergency. Prioritize if Android fleet controls allow Dolphin Browser or if users handle sensitive data on unmanaged mobile devices.
Technical view
The issue is an insecure Intent URI parsing implementation in Dolphin Browser for Android 12.0.2. The reported impact is invocation of private Activities within the Dolphin Browser app. The source bundle does not provide CVSS, CWE, affected CPEs, or vendor remediation details.
Likely exposure
Exposure is likely limited to Android devices running Dolphin Browser 12.0.2. The bundle's affected-product fields are n/a, so asset teams should verify installed app versions rather than assume broader Dolphin Browser impact.
Exploitation context
The source bundle does not cite active exploitation, and KEV status is false. A public VerSprite advisory is referenced, but the provided evidence does not establish exploitation in the wild or a confirmed patched version.
Researcher notes
Key gaps are missing CVSS, CWE, CPE, and fix data. The core behavior is private Activity invocation through malicious Intent URI handling. Do not generalize beyond Dolphin Browser for Android 12.0.2 without additional vendor evidence.
Mitigation direction
- Inventory Android devices for Dolphin Browser, especially version 12.0.2.
- Check vendor or app-store guidance for a fixed release before upgrading.
- Restrict or remove unsupported Dolphin Browser installations through MDM where business need is low.
- Use a supported browser for sensitive workflows until remediation is confirmed.
Validation and detection
- Confirm installed Dolphin Browser package versions on managed Android devices.
- Review MDM inventory for unmanaged or sideloaded browser installations.
- Check whether users can open Intent URI links in Dolphin Browser.
- Document any vendor-fixed version once confirmed from official guidance.
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.
CVE-2017-17553 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
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
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.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/VerSprite/research/blob/master/advisories/VS-2017-002.mdCVE reference · x_refsource_MISC
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.