dbcve.org
Yandex BrowserApplication · Yandex

CVE-2020-27969

HIGH · 7.3 CVSS v3.1 Published 2021-09-13
Fix available
A fix is available. Upgrade to 20.8.4 or later.
See remediation →
82/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
Yandex Browser for Android 20.8.4 allows remote attackers to perform SOP bypass and addresss bar spoofing

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

This vulnerability in Yandex Browser for Android 20.8.4 allows a Same-Origin Policy (SOP) bypass, enabling a malicious webpage to access resources from different origins that should be restricted. Additionally, it permits address bar spoofing, where the browser displays a fraudulent URL in the address bar while actually rendering different content, facilitating phishing attacks.

MitigationUpdate Yandex Browser for Android to a patched version beyond 20.8.4. Until patched, users should avoid clicking untrusted links and consider using an alternative browser.

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
Yandex BrowserApplication
Affected:< 20.8.4= 20.8.4

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
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L

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 Yandex Browser for Android is installed
    Open Android Settings > Apps & notifications > See all apps, or check the app drawer for Yandex Browser
    Affected if Yandex Browser for Android is present on the device
  2. Check installed Yandex Browser version
    Open Yandex Browser, tap the three-dot menu > Settings > scroll to About (or About Browser) to view the version number
    Affected if Version shown is < 20.8.4 or equals 20.8.4 exactly
  3. Confirm vulnerability applicability
    Since SOP bypass and address bar spoofing are code-level flaws, no specific browser setting enables them - they exist in the affected versions by default
    Affected if The browser is actively used to browse untrusted web content

A user is affected if Yandex Browser for Android version 20.8.4 or any version below 20.8.4 is installed and 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 20.8.4 or later
Fixed in 20.8.4
Interim mitigation

Update Yandex Browser for Android to a patched version beyond 20.8.4. Until patched, users should avoid clicking untrusted links and consider using an alternative browser.

Fix this in Yandex Browser Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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