CVE-2018-18330
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 · uneditedAn Address Bar Spoofing vulnerability in Trend Micro Dr. Safety for Android (Consumer) versions 3.0.1324 and below could allow an attacker to potentially trick a victim into visiting a malicious URL using address bar spoofing on the Private Browser of the app on vulnerable installations.
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 · moderate confidenceAn address bar spoofing vulnerability exists in the Private Browser component of Trend Micro Dr. Safety for Android versions 3.0.1324 and below. The vulnerability allows the browser's address bar to display a different URL than the one actually being loaded, enabling attackers to disguise malicious sites as legitimate ones and trick users into visiting harmful URLs.
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<= 3.0.1324CVSS 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.0/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.
-
Locate Trend Micro Dr. Safety app on the Android deviceOpen the device Settings > Apps > Apps list and search for 'Dr. Safety' or 'Trend Micro'. Alternatively, check the device home screen and app drawer for the Dr. Safety icon.Affected if The app is installed on the device
-
Determine the installed version of Trend Micro Dr. SafetyOpen the Dr. Safety app, then go to Settings > About (or tap the profile icon > About) to view the version number. Alternatively, go to Settings > Apps > Dr. Safety and view the version information displayed under the app name.Affected if The displayed version number is 3.0.1324 or lower (for example, 3.0.1324, 3.0.1300, 2.5.x, etc.)
-
Verify if the Private Browser feature has been usedOpen the Dr. Safety app and look for a Private Browser mode or tab, often indicated by a mask or incognito icon. Check the app's browsing history or recent tabs to see if Private Browser sessions have been opened.Affected if The Private Browser feature has been used to navigate to web pages; this is the vulnerable component where the address bar spoofing occurs
-
Confirm the version falls within the affected rangeCompare the version found in step 2 against the affected range: any version less than or equal to 3.0.1324 is vulnerable.Affected if The installed version is 3.0.1324 or any lower version number, and the Private Browser has been used to visit web pages
A user is affected if Trend Micro Dr. Safety for Android is installed with version 3.0.1324 or lower and the Private Browser feature has been used to browse the web, as the address bar can display a different URL than the actual page being loaded.
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 dataUpgrade Trend Micro Dr. Safety for Android to a version higher than 3.0.1324. Until the update is applied, avoid using the Private Browser feature to mitigate the risk of address bar spoofing attacks.
- Consultation4.0 h
- Implementation16.0 h
- Testing8.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 $8,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-18330 — 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-18330 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