CVE-2017-17553
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe Dolphin Browser for Android 12.0.2 suffers from an insecure parsing implementation of the Intent URI scheme. This vulnerability could allow attackers to abuse this implementation through a malicious Intent URI, in order to invoke private Activities within the Dolphin Browser.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe Dolphin Browser for Android 12.0.2 contains an insecure Intent URI scheme parser that fails to properly validate incoming Intent URIs. This allows a malicious URI to trigger invocation of private (internal) activities within the browser application, potentially leading to unauthorized actions or information disclosure.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 12.0.2CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify if Dolphin Browser is installedRun 'pm list packages | grep dolphin' or check app settings to confirm Dolphin Browser presenceAffected if Dolphin Browser (Changyou Dolphin) is installed on the device
-
Check the installed Dolphin Browser versionUse 'dumpsys package com.dolphin.browser' or check app info in Settings > Apps > Dolphin Browser to get the version numberAffected if Version displayed is exactly 12.0.2
-
Determine if the app has exported activity componentsRun 'dumpsys package com.dolphin.browser' and examine the 'android:exported' attributes for activity components in the outputAffected if The app exports activity components that can be invoked via Intent URIs from external apps
-
Check if Intent URI scheme handling is enabledInspect the browser's intent-filter configurations in the app manifest via 'aapt dump badging' or decompile the APK to examine intent-filter definitions for URI schemesAffected if The app declares intent-filters accepting external Intent URIs without proper validation filters
-
Verify private activities are reachable via Intent URIAttempt to construct and test a malicious Intent URI targeting internal activities (e.g., intent://[activity]#Intent;end) from a third-party app or ADBAffected if The Intent URI successfully triggers a private or internal activity that should not be externally accessible
You are affected if Dolphin Browser version 12.0.2 is installed AND the browser exposes exported activities that can be invoked via Intent URIs from external applications.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement strict allowlist-based validation for Intent URIs and ensure private activities are not reachable via external Intent URIs. The browser should validate the target component before dispatching any Intent.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-17553 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2017-17553 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data