{"answers":{"affected":"It affects 3 products.","exploited":"There is no known exploitation of CVE-2018-14780 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2018-14780 is a medium-severity memory corruption vulnerability in n/a, published on 15 Aug 2018. 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-2018-14780 and fix it if it is affected.\n\nWhat it is: CVE-2018-14780 is a medium-severity memory corruption vulnerability in n/a, published on 15 Aug 2018. 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-2018-14780 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-2018-14780/ (Markdown: https://insights.sbomify.com/CVE-2018-14780/index.md)","id":"CVE-2018-14780","markdown":"https://insights.sbomify.com/CVE-2018-14780/index.md","name":"CVE-2018-14780","record":{"aliases":["DEBIAN-CVE-2018-14780","GHSA-xwgg-25ph-4c8p","UBUNTU-CVE-2018-14780"],"analysis":{"component_type":"library","fix_type":"patch","impacts":["data_read","denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Yubico PIV driver","requires_auth":"none","summary":"An out-of-bounds read in the Yubico PIV smartcard driver allows attackers to read memory or cause a crash via crafted APDU data.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"piv_manager","vendor":"yubico"},{"product":"piv_tool","vendor":"yubico"},{"product":"smart_card_minidriver","vendor":"yubico"}],"cvss":{"score":4.6,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.0"},"cwes":[{"id":"CWE-125","name":"Out-of-bounds Read"}],"description":"An out-of-bounds read issue was discovered in the Yubico-Piv 1.5.0 smartcard driver. The file lib/ykpiv.c contains the following code in the function `_ykpiv_fetch_object()`: {% highlight c %} if(sw == SW_SUCCESS) { size_t outlen; int offs = _ykpiv_get_length(data + 1, \u0026outlen); if(offs == 0) { return YKPIV_SIZE_ERROR; } memmove(data, data + 1 + offs, outlen); *len = outlen; return YKPIV_OK; } else { return YKPIV_GENERIC_ERROR; } {% endhighlight %} -- in the end, a `memmove()` occurs with a length retrieved from APDU data. This length is not checked for whether it is outside of the APDU data retrieved. Therefore the `memmove()` could copy bytes behind the allocated data buffer into this buffer.","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":"Memory corruption in n/a","id":"CVE-2018-14780","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2018"},"n_packages":0,"n_references":4,"next":{"headline":"Medtronic MiniMed MMT-500/MMT-503 Remote Controllers Authentication Bypass by Capture-replay","id":"CVE-2018-14781"},"packages":[],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2018-14779"},"products":["n/a"],"published":"2018-08-15","related":[{"cvss_score":6.8,"headline":"Memory corruption in n/a","id":"CVE-2018-14779","kev_date_added":null,"published":"2018-08-15"}],"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-05","vendors":["n/a"]},"summary":"An out-of-bounds read in the Yubico PIV smartcard driver allows attackers to read memory or cause a crash via crafted APDU data.","url":"https://insights.sbomify.com/CVE-2018-14780/"}