{"answers":{"affected":"It affects 3 products.","exploited":"There is no known exploitation of CVE-2020-13131 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2020-13131 is a medium-severity vulnerability in n/a, published on 9 Jul 2020. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2020-13131 and fix it if it is affected.\n\nWhat it is: CVE-2020-13131 is a medium-severity vulnerability in n/a, published on 9 Jul 2020. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2020-13131 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-2020-13131/ (Markdown: https://insights.sbomify.com/CVE-2020-13131/index.md)","id":"CVE-2020-13131","markdown":"https://insights.sbomify.com/CVE-2020-13131/index.md","name":"CVE-2020-13131","record":{"aliases":["DEBIAN-CVE-2020-13131","GHSA-rx8c-cr48-p2ff","UBUNTU-CVE-2020-13131"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Yubico libykpiv library","requires_auth":"none","summary":"A malicious PIV token can trigger a memory leak in libykpiv, exposing sensitive data like PINs and keys to the host application.","user_interaction":"required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"libykpiv","vendor":"yubico"},{"product":"piv_tool_manager","vendor":"yubico"},{"product":"yubikey_smart_card_minidriver","vendor":"yubico"}],"cvss":{"score":4.3,"severity":"medium","source":"cna","vector":"CVSS:3.0/AC:L/AV:P/A:N/C:H/I:N/PR:N/S:U/UI:R","version":"3.0"},"cwes":[{"id":"CWE-125","name":"Out-of-bounds Read"}],"description":"An issue was discovered in Yubico libykpiv before 2.1.0. lib/util.c in this library (which is included in yubico-piv-tool) does not properly check embedded length fields during device communication. A malicious PIV token can misreport the returned length fields during RSA key generation. This will cause stack memory to be copied into heap allocated memory that gets returned to the caller. The leaked memory could include PINs, passwords, key material, and other sensitive information depending on the integration. During further processing by the caller, this information could leak across trust boundaries. Note that RSA key generation is triggered by the host and cannot directly be triggered by the token.","ecosystems":[],"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":"Information disclosure in n/a","id":"CVE-2020-13131","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2020"},"n_packages":0,"n_references":2,"next":{"headline":"Use after free in n/a","id":"CVE-2020-13132"},"packages":[],"prev":{"headline":"Information disclosure in n/a","id":"CVE-2020-13129"},"products":["n/a"],"published":"2020-07-09","related":[{"cvss_score":4.3,"headline":"Use after free in n/a","id":"CVE-2020-13132","kev_date_added":null,"published":"2020-07-09"}],"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 malicious PIV token can trigger a memory leak in libykpiv, exposing sensitive data like PINs and keys to the host application.","url":"https://insights.sbomify.com/CVE-2020-13131/"}