dbcve.org
AnydeskApplication

CVE-2018-13102

HIGH · 7.8 CVSS v3.0 Published 2018-07-03
Fix available
A fix is available. Upgrade to 4.1.3 or later.
See remediation →
81/100
Remediation priority · High
No privileges

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
AnyDesk before "12.06.2018 - 4.1.3" on Windows 7 SP1 has a DLL preloading vulnerability.

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 confidence

AnyDesk versions prior to 4.1.3 on Windows 7 SP1 contain a DLL preloading (DLL hijacking) vulnerability where the application uses a relative path to load dynamic link libraries, potentially allowing an attacker to place a malicious DLL in a location where it will be loaded by the application.

MitigationUpdate AnyDesk to version 4.1.3 or later, or ensure that only trusted DLLs exist in directories from which AnyDesk loads libraries.

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
AnydeskApplication
Affected:< 4.1.3

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
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/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 checks

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

  1. Check if AnyDesk is installed
    Look for AnyDesk installation directory at C:\Program Files\AnyDesk\AnyDesk.exe or search for the executable using File Explorer, or check the Windows Registry under HKLM\Software\Microsoft\Windows\CurrentVersion\Uninstall for an AnyDesk entry.
    Affected if AnyDesk executable or registry entry is found on the system.
  2. Determine the installed AnyDesk version
    Right-click on AnyDesk.exe, select Properties, and view the Version tab. Alternatively, open Command Prompt and run: wmic product where "name like '%AnyDesk%'" get version
    Affected if A version number is returned by these methods.
  3. Compare version against the vulnerable range
    Compare the detected version number to 4.1.3. Any version lower than 4.1.3 (such as 4.1.2, 4.0.0, 3.x.x, etc.) is affected.
    Affected if The installed version is lower than 4.1.3 (for example, 4.1.2, 4.0.1, 3.7.0).
  4. Confirm the operating system context
    Run 'winver' from the Start menu or Command Prompt to check the Windows version. The vulnerability disclosure specifically references Windows 7 SP1.
    Affected if The system is running Windows 7 SP1 and AnyDesk version is below 4.1.3.

If AnyDesk is installed with a version lower than 4.1.3 on Windows 7 SP1, the system is affected by this DLL preloading vulnerability.

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

Update AnyDesk to version 4.1.3 or later, or ensure that only trusted DLLs exist in directories from which AnyDesk loads libraries.

Fix this in Anydesk Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
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,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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