{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-41380 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2021-41380 yet. Limit exposure of the affected software until one is available.","what":"CVE-2021-41380 is a medium-severity denial of service vulnerability in n/a, published on 17 Sep 2021. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2021-41380 and fix it if it is affected.\n\nWhat it is: CVE-2021-41380 is a medium-severity denial of service vulnerability in n/a, published on 17 Sep 2021. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2021-41380 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-41380/ (Markdown: https://insights.sbomify.com/CVE-2021-41380/index.md)","id":"CVE-2021-41380","markdown":"https://insights.sbomify.com/CVE-2021-41380/index.md","name":"CVE-2021-41380","record":{"aliases":["GHSA-789c-r6w2-66gw"],"analysis":{"component_type":"desktop_application","fix_type":"no_fix_stated","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"VNC client","requires_auth":"none","summary":"A remote VNC server can cause RealVNC Viewer to hang via crafted protocol data, requiring user interaction to connect to a malicious server.","user_interaction":"required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"vnc_viewer","vendor":"realvnc"}],"cvss":{"score":6.5,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-20","name":"Improper Input Validation"}],"description":"RealVNC Viewer 6.21.406 allows remote VNC servers to cause a denial of service (application crash) via crafted RFB protocol data. NOTE: It is asserted that this issue requires social engineering a user into connecting to a fake VNC Server. The VNC Viewer application they are using will then hang, until terminated, but no memory leak occurs - the resources are freed once the hung process is terminated and the resource usage is constant during the hang. Only the process that is connected to the fake Server is affected. This is an application bug, not a security issue","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":"Denial of service in n/a","id":"CVE-2021-41380","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2021"},"n_packages":0,"n_references":1,"next":{"headline":"Path traversal in n/a","id":"CVE-2021-41381"},"packages":[],"prev":{"headline":"Microsoft Windows Installer Privilege Escalation","id":"CVE-2021-41379"},"products":["n/a"],"published":"2021-09-17","related":[],"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":"CWE Terms of Use","name":"CWE (MITRE)"},{"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":"A remote VNC server can cause RealVNC Viewer to hang via crafted protocol data, requiring user interaction to connect to a malicious server.","url":"https://insights.sbomify.com/CVE-2021-41380/"}