CVE-2018-16135
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 Opera Mini application 47.1.2249.129326 for Android allows remote attackers to spoof the Location Permission dialog via a crafted web site.
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 Opera Mini Android browser (version 47.1.2249.129326) contains a UI spoofing vulnerability in its Location Permission dialog. Attackers can host a crafted webpage that displays a deceptive location permission prompt, potentially tricking users into granting location access to malicious sites. This is a dialog-spoofing flaw allowing permission request manipulation.
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= 47.1.2249.129326CVSS 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
- Required
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/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.
-
Verify Opera Mini is installed on the Android deviceCheck the device's installed applications list for 'Opera Mini' or 'Opera Mini - fast web browser'. On Android, this can be done via Settings > Apps or by using an MDM/EMM solution's app inventory feature.Affected if Opera Mini browser is present on the device
-
Determine the installed Opera Mini versionOpen Opera Mini, tap the browser menu (usually three dots or 'O' icon), go to Settings > About Opera Mini, and record the version number shown. Alternatively, check via Play Store app listing or MDM software inventory.Affected if The version number equals exactly 47.1.2249.129326
-
Verify the location permission dialog functionality existsIn Opera Mini, visit any website that requests location access (or use a test page that requests geolocation). Observe whether a Location Permission dialog appears prompting the user to Allow or Deny location access.Affected if The browser displays a location permission prompt when a website requests geolocation, indicating the vulnerable dialog feature is present and active
-
Confirm the browser has location permission capability enabledCheck if Opera Mini has been granted location permission at the system level: go to Android Settings > Apps > Opera Mini > Permissions, and verify whether the Location permission is listed (even if not yet granted to any site).Affected if The Location permission option exists in the browser's permissions, meaning the UI component targeted by the spoofing flaw is present
A user is affected if their Opera Mini Android browser is version 47.1.2249.129326 and the location permission dialog feature is present and accessible on the device.
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 dataSince this is a client-side vulnerability requiring a vendor patch, organizations should ensure Opera Mini is updated to a patched version once available, and consider inventorying affected Android devices running this browser version.
- Consultation2.0 h
- Implementation1.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,456.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-16135 — 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-2018-16135 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