CVE-2022-28225
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 · uneditedLocal privilege vulnerability in Yandex Browser for Windows prior to 22.3.3.684 allows a local, low privileged, attacker to execute arbitary code with the SYSTEM privileges through manipulating symlinks to installation file during Yandex Browser update process.
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 confidenceLocal privilege escalation vulnerability in Yandex Browser for Windows prior to 22.3.3.684. During the update process, an attacker with low-privileged local access can manipulate symbolic links to redirect the installation mechanism, causing arbitrary code execution with SYSTEM privileges.
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< 22.3.3.684CVSS 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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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.
-
Identify installed Yandex Browser versionOpen Yandex Browser, navigate to Settings > About Browser, or check the application version through Windows Programs and Features. Alternatively, examine the executable file properties of the Yandex Browser installation.Affected if The displayed version is lower than 22.3.3.684
-
Verify if automatic updates are enabledCheck the Yandex Browser settings for update configuration. On Windows, this may also be controllable via registry or group policy settings related to browser update mechanisms.Affected if Automatic or manual update checks are enabled and the installed version is below 22.3.3.684, making the update process exploitable
-
Examine update-related directories for symbolic linksLocate the directories used by Yandex Browser for storing temporary update files or staging patches. Inspect these directories for any symbolic links that may redirect installation paths.Affected if Symbolic links exist in update directories that point to unexpected locations or were created by a low-privileged user
-
Review update process execution contextMonitor or inspect how the Yandex Browser update process runs on the system. Determine whether it executes with elevated (SYSTEM) privileges during the update operation.Affected if The update process runs with SYSTEM privileges and the installed version is vulnerable
You are affected if Yandex Browser version is below 22.3.3.684 and the update feature is enabled, allowing a low-privileged local attacker to exploit symlink manipulation during the update process for privilege escalation.
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.
dbcve · scoped22.3.3.684
Update Yandex Browser to version 22.3.3.684 or later. Until patched, monitor update processes for unauthorized symlink manipulation and restrict local user permissions where possible.
22.3.3.684 or later
- Open Yandex Browser
- Click on the menu icon (three dots) in the top-right corner
- Navigate to 'Settings'
- Scroll down and click 'About Yandex Browser'
- If an update is available, click 'Update Yandex Browser'
- Wait for the update to complete and restart the browser if prompted
- Alternatively, download the latest version from the official Yandex website (yandex.com) and run the installer to upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation1.0 h
- Testing1.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,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-28225 — 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-2022-28225 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