{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2024-45617 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2024-45617 is a low-severity vulnerability in Opensc Project Opensc, published on 3 Sep 2024. 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-2024-45617 and fix it if it is affected.\n\nWhat it is: CVE-2024-45617 is a low-severity vulnerability in Opensc Project Opensc, published on 3 Sep 2024. 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-2024-45617 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-2024-45617/ (Markdown: https://insights.sbomify.com/CVE-2024-45617/index.md)","id":"CVE-2024-45617","markdown":"https://insights.sbomify.com/CVE-2024-45617/index.md","name":"CVE-2024-45617","record":{"aliases":["AZL-48732","AZL-48823","BELL-CVE-2024-45617","DEBIAN-CVE-2024-45617","GHSA-cf2w-h975-2fpg","UBUNTU-CVE-2024-45617"],"analysis":{"component_type":"library","fix_type":"patch","impacts":["other"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"OpenSC smart card library","requires_auth":"none","summary":"Attackers can cause unexpected behavior via crafted smart card responses due to uninitialized variables in OpenSC.","user_interaction":"not_required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"redhat","cpe":[{"product":"opensc","vendor":"opensc_project"},{"product":"enterprise_linux","vendor":"redhat"}],"cvss":{"score":3.9,"severity":"low","source":"cna","vector":"CVSS:3.1/AV:P/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L","version":"3.1"},"cwes":[{"id":"CWE-908","name":"Use of Uninitialized Resource"},{"id":"CWE-457","name":"Use of Uninitialized Variable"}],"description":"A vulnerability was found in OpenSC, OpenSC tools, PKCS#11 module, minidriver, and CTK. An attacker could use a crafted USB Device or Smart Card, which would present the system with a specially crafted response to APDUs. \n\nInsufficient or missing checking of return values of functions leads to unexpected work with variables that have not been initialized.","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":"Libopensc: uninitialized values after incorrect or missing checking return values of functions in libopensc","id":"CVE-2024-45617","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"opensc_project:opensc","products":["opensc_project:opensc","redhat:enterprise_linux"],"type":"other","year":"2024"},"n_packages":0,"n_references":2,"next":{"headline":"Libopensc: uninitialized values after incorrect or missing checking return values of functions in pkcs15init","id":"CVE-2024-45618"},"packages":[],"prev":{"headline":"Libopensc: uninitialized values after incorrect check or usage of apdu response values in libopensc","id":"CVE-2024-45616"},"products":["Red Hat Enterprise Linux 10","Red Hat Enterprise Linux 7","Red Hat Enterprise Linux 8","Red Hat Enterprise Linux 9"],"published":"2024-09-03","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":"Memory corruption in n/a","id":"CVE-2019-16058","kev_date_added":null,"published":"2019-09-06"},{"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":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-06-30","vendors":["Red Hat"]},"summary":"Attackers can cause unexpected behavior via crafted smart card responses due to uninitialized variables in OpenSC.","url":"https://insights.sbomify.com/CVE-2024-45617/"}