dbcve.org
SnowhazeApplication

CVE-2019-18949

HIGH · 7.5 CVSS v3.1 Published 2019-11-14
Fix available
A fix is available. Upgrade to 2.6.6 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
SnowHaze before 2.6.6 is sometimes too late to honor a per-site JavaScript blocking setting, which leads to unintended JavaScript execution via a chain of webpage redirections targeted to the user's browser configuration.

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 confidence

SnowHaze browser before version 2.6.6 has a race condition where per-site JavaScript blocking settings are applied too late during redirect chains, allowing JavaScript to execute before the blocking policy takes effect. Attackers can bypass user-configured JavaScript restrictions by chaining page redirections.

MitigationUpgrade SnowHaze to version 2.6.6 or later to receive the fix for the timing vulnerability in JavaScript blocking enforcement.

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
SnowhazeApplication
Affected:< 2.6.6

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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 checks

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

  1. Verify SnowHaze browser is installed
    Check if the SnowHaze browser app is present on the iOS device in the app library or home screen
    Affected if SnowHaze browser is installed on the device
  2. Find installed SnowHaze version
    Open the App Store, go to the SnowHaze app page, or check within the app settings to view the installed version number
    Affected if Unable to determine version or version display shows no number
  3. Compare version to affected range
    Compare your installed version against version 2.6.6 - any version lower than 2.6.6 is affected
    Affected if Installed version is any version prior to 2.6.6 (e.g., 2.6.5, 2.6.0, 2.5.x, etc.)
  4. Check if JavaScript blocking is enabled
    Within SnowHaze settings, locate the per-site JavaScript blocking or content blocking configuration to see if any sites have JavaScript restrictions applied
    Affected if JavaScript blocking settings are configured for any websites

User is affected if SnowHaze browser is installed with a version lower than 2.6.6 AND has JavaScript blocking restrictions configured for websites, as the race condition allows JS to bypass those restrictions during redirect chains.

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 2.6.6 or later
Fixed in 2.6.6
Interim mitigation

Upgrade SnowHaze to version 2.6.6 or later to receive the fix for the timing vulnerability in JavaScript blocking enforcement.

Fix this in Snowhaze Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
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,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-18949 — 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-2019-18949 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