{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-44425 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2021-44425 yet. Limit exposure of the affected software until one is available.","what":"CVE-2021-44425 is a medium-severity missing authorization vulnerability in n/a, published on 12 Sep 2022. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2021-44425 and fix it if it is affected.\n\nWhat it is: CVE-2021-44425 is a medium-severity missing authorization vulnerability in n/a, published on 12 Sep 2022. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2021-44425 in the wild and no public exploit code.\n\nAffected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2021-44425/ (Markdown: https://insights.sbomify.com/CVE-2021-44425/index.md)","id":"CVE-2021-44425","markdown":"https://insights.sbomify.com/CVE-2021-44425/index.md","name":"CVE-2021-44425","record":{"aliases":["GHSA-rgr5-hjh7-p6gp"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["security_bypass","data_read"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"AnyDesk remote desktop","requires_auth":"none","summary":"Attackers on the local network can access the AnyDesk tunneling protocol stack and remote destinations due to an unnecessarily open port when tunneling is enabled.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"anydesk","vendor":"anydesk"}],"cvss":{"score":6.5,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[],"description":"An issue was discovered in AnyDesk before 6.2.6 and 6.3.x before 6.3.3. An unnecessarily open listening port on a machine in the LAN of an attacker, opened by the Anydesk Windows client when using the tunneling feature, allows the attacker unauthorized access to the local machine's AnyDesk tunneling protocol stack (and also to any remote destination machine software that is listening to the AnyDesk tunneled port).","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Missing authorization in n/a","id":"CVE-2021-44425","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2021"},"n_packages":0,"n_references":2,"next":{"headline":"File upload in n/a","id":"CVE-2021-44426"},"packages":[],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2021-44423"},"products":["n/a"],"published":"2022-09-12","related":[{"cvss_score":9.8,"headline":"Integer overflow in n/a","id":"CVE-2025-27918","kev_date_added":null,"published":"2025-11-06"},{"cvss_score":9.8,"headline":"Other in n/a","id":"CVE-2020-13160","kev_date_added":null,"published":"2020-06-09"},{"cvss_score":9.8,"headline":"AnyDesk before 3.6.1 on Windows has a DLL injection vulnerability.","id":"CVE-2017-14397","kev_date_added":null,"published":"2017-09-12"},{"cvss_score":8.8,"headline":"File upload in n/a","id":"CVE-2021-44426","kev_date_added":null,"published":"2022-09-12"},{"cvss_score":8.5,"headline":"AnyDesk 2.5.0 Unquoted Service Path Elevation of Privilege","id":"CVE-2016-20094","kev_date_added":null,"published":"2026-06-19"},{"cvss_score":8.5,"headline":"AnyDesk 5.4.0 - Unquoted Service Path","id":"CVE-2019-25261","kev_date_added":null,"published":"2026-02-03"},{"cvss_score":8.2,"headline":"Missing authorization in n/a","id":"CVE-2025-27919","kev_date_added":null,"published":"2025-11-06"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["n/a"]},"summary":"Attackers on the local network can access the AnyDesk tunneling protocol stack and remote destinations due to an unnecessarily open port when tunneling is enabled.","url":"https://insights.sbomify.com/CVE-2021-44425/"}