{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-16058 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2019-16058 is a high-severity memory corruption vulnerability in Opensc Project Opensc, published on 6 Sep 2019. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2019-16058 and fix it if it is affected.\n\nWhat it is: CVE-2019-16058 is a high-severity memory corruption vulnerability in Opensc Project Opensc, published on 6 Sep 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2019-16058 in the wild and no public exploit code.\n\nAffected product: Opensc Project Opensc. 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-2019-16058/ (Markdown: https://insights.sbomify.com/CVE-2019-16058/index.md)","id":"CVE-2019-16058","markdown":"https://insights.sbomify.com/CVE-2019-16058/index.md","name":"CVE-2019-16058","record":{"aliases":["DEBIAN-CVE-2019-16058","GHSA-2pqr-cp8m-m5vw","UBUNTU-CVE-2019-16058","openSUSE-SU-2024:11143-1"],"analysis":{"component_type":"operating_system","fix_type":"patch","impacts":["code_execution","privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"OpenSC PAM module","requires_auth":"none","summary":"A buffer overflow in the pam_p11 component allows attackers to execute arbitrary code or escalate privileges via a crafted smart card signature.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"opensc","vendor":"opensc_project"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.0"},"cwes":[{"id":"CWE-119","name":"Improper Restriction of Operations within the Bounds of a Memory Buffer"}],"description":"An issue was discovered in the pam_p11 component 0.2.0 and 0.3.0 for OpenSC. If a smart card creates a signature with a length longer than 256 bytes, this triggers a buffer overflow. This may be the case for RSA keys with 4096 bits depending on the signature scheme.","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-2019-16058","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"opensc_project:opensc","products":["opensc_project:opensc"],"type":"memory_corruption","year":"2019"},"n_packages":0,"n_references":2,"next":{"headline":"Cross-site request forgery in n/a","id":"CVE-2019-16059"},"packages":[],"prev":{"headline":"D-Link DNS-320 Remote Code Execution","id":"CVE-2019-16057"},"products":["n/a"],"published":"2019-09-06","related":[{"cvss_score":7.5,"headline":"Memory corruption in n/a","id":"CVE-2021-34193","kev_date_added":null,"published":"2023-08-22"},{"cvss_score":7.5,"headline":"Denial of service in n/a","id":"CVE-2019-6502","kev_date_added":null,"published":"2019-01-22"},{"cvss_score":7.1,"headline":"Memory corruption in OpenSC","id":"CVE-2023-2977","kev_date_added":null,"published":"2023-06-01"},{"cvss_score":6.8,"headline":"Use after free in n/a","id":"CVE-2019-20792","kev_date_added":null,"published":"2020-04-29"},{"cvss_score":6.8,"headline":"Memory corruption in n/a","id":"CVE-2018-16391","kev_date_added":null,"published":"2018-09-03"},{"cvss_score":6.8,"headline":"Memory corruption in n/a","id":"CVE-2018-16392","kev_date_added":null,"published":"2018-09-03"}],"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":"A buffer overflow in the pam_p11 component allows attackers to execute arbitrary code or escalate privileges via a crafted smart card signature.","url":"https://insights.sbomify.com/CVE-2019-16058/"}