dbcve.org
Dr. SafetyApplication · Trendmicro

CVE-2018-18334

HIGH · 7.5 CVSS v3.0 Published 2019-02-05
Fix available
A fix is available. Upgrade to 3.0.1478 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
A vulnerability in the Private Browser of Trend Micro Dr. Safety for Android (Consumer) versions below 3.0.1478 could allow an remote attacker to bypass the Same Origin Policy (SOP) and obtain sensitive information via crafted JavaScript code 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 · high confidence

A Same Origin Policy (SOP) bypass vulnerability exists in the Private Browser component of Trend Micro Dr. Safety for Android versions prior to 3.0.1478. The flaw allows a remote attacker to inject crafted JavaScript that can circumvent browser security restrictions, potentially accessing sensitive data such as cookies, session tokens, or other origin-isolated information from other web contexts.

MitigationUpgrade Trend Micro Dr. Safety for Android to version 3.0.1478 or later through the Google Play Store or enterprise mobile deployment channel.

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
Dr. SafetyApplication
Affected:< 3.0.1478

CVSS 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
High
Integrity
None
Availability
None

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Trend Micro Dr. Safety is installed
    On the Android device, go to Settings > Apps > Apps list and search for 'Dr. Safety' or 'Trend Micro', or check the app drawer for the Dr. Safety icon
    Affected if The app is present on the device
  2. Identify the installed version
    In Settings > Apps > Dr. Safety, scroll to the 'App info' or 'Version' field to see the current version number (for example, 3.0.1456 or 3.0.1478)
    Affected if Version shown is less than 3.0.1478 (such as 3.0.1400, 3.0.1456, etc.)
  3. Determine if Private Browser is in use
    Open the Dr. Safety app and look for the 'Private Browser' or 'Secure Browser' feature within the app interface; this may be accessible via a toolbar icon or menu option
    Affected if The Private Browser feature is accessible or has been used on the device

The environment is affected if Trend Micro Dr. Safety for Android is installed with a version lower than 3.0.1478 and the Private Browser component is available or has been used.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to 3.0.1478 or later
Fixed in 3.0.1478
Interim mitigation

Upgrade Trend Micro Dr. Safety for Android to version 3.0.1478 or later through the Google Play Store or enterprise mobile deployment channel.

Fix this in Dr. Safety Scoped from the published advisory
  • Consultation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
3.0 hours of engineering $750
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-18334 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2018-18334 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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