{"answers":{"affected":"2 open source packages ship an affected version, including HaemmerElectronics.SeppPenner.WindowsHello. It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-11005 in the wild and no public exploit code.","fix":"Upgrade HaemmerElectronics.SeppPenner.WindowsHello to 1.0.4 or later.","what":"CVE-2020-11005 is a medium-severity vulnerability in SeppPenner WindowsHello, published on 14 Apr 2020. 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-2020-11005 and fix it if it is affected.\n\nWhat it is: CVE-2020-11005 is a medium-severity vulnerability in SeppPenner WindowsHello, published on 14 Apr 2020. 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-2020-11005 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- HaemmerElectronics.SeppPenner.WindowsHello (NuGet): affected all versions; fixed in 1.0.4\n- HaemmerElectronics.SeppPenner.WindowsHello (NuGet): affected all versions; fixed in 1.0.4\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-2020-11005/ (Markdown: https://insights.sbomify.com/CVE-2020-11005/index.md)","id":"CVE-2020-11005","markdown":"https://insights.sbomify.com/CVE-2020-11005/index.md","name":"CVE-2020-11005","record":{"aliases":["GHSA-wvpv-ffcv-r6cw"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"WindowsHello NuGet library","requires_auth":"none","summary":"Attackers can bypass Windows Hello authentication to decrypt sensitive data using an exposed internal method in the WindowsHello library.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"windowshello","vendor":"windowshello_project"}],"cvss":{"score":5.1,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-327","name":"Use of a Broken or Risky Cryptographic Algorithm"},{"id":"CWE-288","name":"Authentication Bypass Using an Alternate Path or Channel"}],"description":"The WindowsHello open source library (NuGet HaemmerElectronics.SeppPenner.WindowsHello), before version 1.0.4, has a vulnerability where encrypted data could potentially be decrypted without needing authentication. If the library is used to encrypt text and write the output to a txt file, another executable could be able to decrypt the text using the static method NCryptDecrypt from this same library without the need to use Windows Hello Authentication again. This has been patched in version 1.0.4.","ecosystems":["NuGet"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Internal NCryptDecrypt method could be used externally from WindowsHello library.","id":"CVE-2020-11005","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"NuGet","product":null,"products":[],"type":"security_feature_bypass","year":"2020"},"n_packages":2,"n_references":2,"next":{"headline":"Potential remote code execution in Shopizer","id":"CVE-2020-11006"},"packages":[{"ecosystem":"NuGet","fixed":["1.0.4"],"introduced":["0"],"last_affected":[],"package":"HaemmerElectronics.SeppPenner.WindowsHello","purl":null,"source":"GHSA-wvpv-ffcv-r6cw"},{"ecosystem":"NuGet","fixed":["1.0.4"],"introduced":["0"],"last_affected":[],"package":"HaemmerElectronics.SeppPenner.WindowsHello","purl":"pkg:nuget/HaemmerElectronics.SeppPenner.WindowsHello","source":"GHSA-wvpv-ffcv-r6cw"}],"prev":{"headline":"SQL Injection in Admidio","id":"CVE-2020-11004"},"products":["WindowsHello"],"published":"2020-04-14","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"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":["SeppPenner"]},"summary":"Attackers can bypass Windows Hello authentication to decrypt sensitive data using an exposed internal method in the WindowsHello library.","url":"https://insights.sbomify.com/CVE-2020-11005/"}