Security readout for executives and security teams
Plain-English summary
This flaw affects older AnyDesk Windows clients when the tunneling feature is used. The client could expose a listening port too broadly on the local network, letting a nearby attacker reach AnyDesk tunneling components and potentially software on the remote tunneled destination.
Executive priority
Prioritize remediation where AnyDesk is used for administration, support, or access into sensitive environments. The business risk is unauthorized lateral access from the same LAN, not confirmed mass exploitation.
Technical view
CVE-2021-44425 concerns AnyDesk before 6.2.6 and 6.3.x before 6.3.3. When Windows tunneling is enabled, an unnecessarily open LAN listening port can allow unauthorized access to the local AnyDesk tunneling protocol stack and the software listening behind the tunneled remote port.
Likely exposure
Exposure is most likely on Windows endpoints running affected AnyDesk versions that use the tunneling feature while connected to networks containing untrusted or compromised LAN peers.
Exploitation context
The provided sources do not show CISA KEV listing or active exploitation. The attack condition described is local-network proximity plus use of AnyDesk tunneling, so broad internet-wide exposure is not established by the bundle.
Researcher notes
The bundle lacks CVSS, CWE, and detailed patch notes. Analysis should stay tied to the published affected ranges and the Argus-described tunneling exposure. Do not assume other AnyDesk platforms or non-tunneling workflows are affected without vendor evidence.
Mitigation direction
- Upgrade AnyDesk Windows clients to 6.2.6, 6.3.3, or later fixed versions.
- Disable AnyDesk tunneling where it is not operationally required.
- Restrict local network access to systems running AnyDesk tunneling.
- Review vendor guidance for current supported versions and hardening advice.
- Segment administrative workstations from untrusted LAN users and guest networks.
Validation and detection
- Inventory Windows endpoints with AnyDesk installed and record client versions.
- Identify endpoints where the AnyDesk tunneling feature is enabled or used.
- Confirm affected versions are upgraded beyond the vulnerable ranges.
- Check host firewall policy limits unexpected LAN access to AnyDesk-related listeners.
- Review remote tunneled services for unintended exposure through AnyDesk tunneling.
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-2021-44425 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://anydesk.com/en/downloads/windowsCVE reference · x_refsource_MISC
- https://argus-sec.com/discovering-tunneling-service-security-flaws-in-anydesk-remote-application/CVE reference · x_refsource_MISC
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.