CVE-2024-12168
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 · uneditedYandex Telemost for Desktop before 2.7.0 has a DLL Hijacking Vulnerability because an untrusted search path is used.
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 confidenceYandex Telemost for Desktop versions before 2.7.0 contain a DLL hijacking vulnerability due to the application using an untrusted search path to load dynamic link libraries. An attacker with write access to a directory in the DLL search path could place a malicious DLL that the application would load, potentially achieving arbitrary code execution with the privileges of the running user.
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= 2.7.0CVSS 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
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/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 Yandex Telemost for Desktop installationSearch for the application in standard installation directories such as C:\Program Files\Yandex\Yandex Telemost or C:\Users\[Username]\AppData\Local\Programs\yandex-telemost. Also check the Start Menu and Desktop for shortcuts.Affected if The application is found installed on the system.
-
Determine installed versionRight-click the executable (e.g., telemost.exe) and select Properties, then go to the Details tab to view the Product Version. Alternatively, open PowerShell and run: Get-ItemProperty 'C:\Program Files\Yandex\Yandex Telemost\telemost.exe' | Select-Object VersionInfoAffected if The version is lower than 2.7.0 (e.g., 2.6.x, 2.5.x, etc.).
-
Check execution location vulnerabilityNote the directory from which the application is launched. Check if the working directory is in a writable location such as a shared network drive, download folder, or public directory. Run: (Get-Process -Name telemost -ErrorAction SilentlyContinue).Path to find the running process path.Affected if The application is launched from a directory where untrusted users have write permissions, or from a network share, download folder, or temp directory.
-
Inspect DLL search pathRun the application and use Process Monitor (from Sysinternals) to capture DLL load events, filtering by the telemost.exe process name. Look for DLLs loaded from directories outside the application installation folder.Affected if The application loads DLLs from directories in the PATH environment variable, current working directory, or other user-writable locations.
You are affected if Yandex Telemost for Desktop is installed at a version lower than 2.7.0 AND the application is launched from or loads DLLs via a directory where an attacker could place a malicious DLL.
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 · scopedUpdate Yandex Telemost for Desktop to version 2.7.0 or later. As a workaround, ensure the application is run from directories with strict access controls and avoid launching the application from untrusted or shared locations.
Yandex Telemost for Desktop version 2.7.0 or later
- Upgrade Yandex Telemost for Desktop to version 2.7.0 or later, as this version contains the fix for the DLL hijacking vulnerability (CVE-2024-12168).
- Verify the upgrade was successful by checking the application version in the software's 'About' or settings menu.
- Ensure the upgraded application launches and functions normally after the update.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.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 $2,880.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-12168 — 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-2024-12168 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