CVE-2018-17061
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 · uneditedBullGuard Safe Browsing before 18.1.355.9 allows XSS on Google, Bing, and Yahoo! pages via domains indexed in search results.
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 confidenceCross-site scripting (XSS) vulnerability in BullGuard Safe Browsing browser extension before version 18.1.355.9 allows injection of malicious scripts through search result domains displayed on Google, Bing, and Yahoo search engine results pages.
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< 18.1.355.9CVSS 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
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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 BullGuard Safe Browsing extension is installedOpen your browser's extension management page (Chrome: chrome://extensions, Firefox: about:addons, Edge: edge://extensions) and look for 'BullGuard Safe Browsing' in the installed extensions listAffected if The extension is not present in the browser - if not installed, the vulnerability does not apply
-
Locate the installed version numberIn the browser extension management page, find the BullGuard Safe Browsing extension and locate the version number displayed next to it (typically shown in the extension details or info section)Affected if Unable to determine version - cannot assess vulnerability status without version information
-
Compare installed version to affected rangeTake the installed version number and compare it to the vulnerable version range: any version lower than 18.1.355.9 is affected (for example: 18.1.355.8, 18.1.354.0, etc.)Affected if Installed version is less than 18.1.355.9 - the environment is running a vulnerable version
-
Confirm extension is enabledIn the browser extension management page, verify that the BullGuard Safe Browsing extension is turned ON or enabled (not disabled or paused)Affected if Extension is disabled - the vulnerability cannot be exploited while the extension is disabled
A user is affected if BullGuard Safe Browsing extension version lower than 18.1.355.9 is installed and enabled in the browser, allowing malicious search result domains to inject scripts.
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 data18.1.355.9
Upgrade BullGuard Safe Browsing to version 18.1.355.9 or later to patch the XSS vulnerability in the Safe Browsing extension.
- Consultation1.0 h
- Implementation1.0 h
- Testing2.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,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-17061 — 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-17061 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