Security readout for executives and security teams
Plain-English summary
AnyDesk for Windows versions before 3.6.1 had a DLL injection vulnerability. In business terms, an outdated remote-access tool could be abused in ways the public sources do not fully detail. Because AnyDesk provides remote control capability, even sparse vulnerability data should trigger inventory and upgrade checks.
Executive priority
Treat this as an asset hygiene and remote-access risk item. Prioritize finding and upgrading old AnyDesk for Windows installations, especially on sensitive workstations and servers.
Technical view
The CVE describes DLL injection in AnyDesk before 3.6.1 on Windows. The public record does not provide CVSS, CWE, affected CPEs, prerequisites, or impact detail. The version boundary indicates Windows installations below 3.6.1 are the known exposure set.
Likely exposure
Exposure is limited by the supplied sources to Windows systems running AnyDesk versions earlier than 3.6.1. No affected non-Windows products are identified in the source bundle.
Exploitation context
The source bundle does not cite active exploitation, and the CVE is not listed as KEV. Available sources do not document exploit maturity, attacker requirements, or observed abuse.
Researcher notes
The public record is unusually sparse. It supports the product, platform, vulnerability class, and fixed version boundary, but not root cause, attack path, privilege context, or impact severity.
Mitigation direction
- Inventory AnyDesk installations on Windows endpoints.
- Upgrade any AnyDesk for Windows installation older than 3.6.1.
- Prefer a currently supported AnyDesk release where operationally possible.
- Remove AnyDesk where there is no business need.
- Check current AnyDesk guidance for any additional vendor recommendations.
Validation and detection
- Confirm installed AnyDesk versions on Windows assets.
- Flag any version earlier than 3.6.1 for remediation.
- Verify remediated systems report version 3.6.1 or later.
- Check remote-access software inventories for unmanaged AnyDesk installs.
- Review vendor changelog and CVE record for scope changes.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CVE-2017-14397 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://download.anydesk.com/changelog.txtCVE reference · x_refsource_CONFIRM
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.