DLL Hijacking in Yandex Browser for Desktop
CVE-2024-6473 is a DLL hijacking vulnerability in Yandex Browser for Desktop before version 24.7.1.380. The product uses an untrusted search path when loading DLLs, allowing a malicious library to be loaded instead of the intended legitimate one. The provided content specifically states that the issue was exploited by replacing a legitimate DLL such as Wldp.dll, and separately references related tradecraft involving replacement of winsta.dll in a DLL hijacking chain. In practical terms, if an attacker can place a crafted DLL in a location searched before the trusted system path, execution of the browser or a related launched component can cause the attacker-controlled DLL to be loaded and executed in the context of the affected process.
Are you exposed to this one?
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
Impact, mitigation & remediation
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Mitigation
If you can’t patch tonight, do this now.
Remediation
Patch, then assume compromise.
Exploits
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository is a proof-of-concept (PoC) exploit for CVE-2024-6473, a DLL hijacking vulnerability in Yandex Browser for Desktop (before version 24.7.1.380). The exploit consists of a Visual Studio C++ project that builds a DLL. When this DLL is placed in the Yandex Browser application directory (%LOCALAPPDATA%\Yandex\YandexBrowser\Application) and the browser is started, the browser loads the DLL due to an untrusted search path. The DLL's entry point (DllMain) executes a payload that spawns a command prompt (cmd.exe) and then terminates the process, demonstrating arbitrary code execution. The repository includes build files, a module definition file exporting several functions as stubs, and a README with detailed usage instructions and references. The attack vector is local, requiring the attacker to place the DLL on the victim's machine. No network endpoints are involved, but the exploit is fingerprintable by the required file paths and the use of cmd.exe.
Affected products & vendors
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
Recent activity
3 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A Yandex Browser DLL hijacking vulnerability referenced as previously exploited in targeted attacks (rail freight industry).
A DLL hijacking vulnerability in Yandex Browser that was exploited as a zero-day to download and execute malware.
A DLL hijacking vulnerability in Yandex Browser abused by replacing a legitimate DLL (Wldp.dll) to execute a malicious payload.
The version that knows your environment.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.