{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-24032 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2025-24032 is a critical authentication bypass vulnerability in OpenSC pam_pkcs11, published on 10 Feb 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-24032 and fix it if it is affected.\n\nWhat it is: CVE-2025-24032 is a critical authentication bypass vulnerability in OpenSC pam_pkcs11, published on 10 Feb 2025. 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-2025-24032 in the wild and no public exploit code.\n\nAffected product: OpenSC pam_pkcs11. 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-2025-24032/ (Markdown: https://insights.sbomify.com/CVE-2025-24032/index.md)","id":"CVE-2025-24032","markdown":"https://insights.sbomify.com/CVE-2025-24032/index.md","name":"CVE-2025-24032","record":{"aliases":["DEBIAN-CVE-2025-24032","DLA-4058-1","GHSA-8r8p-7mgp-vf56","UBUNTU-CVE-2025-24032"],"analysis":{"component_type":"operating_system","fix_type":"upgrade","impacts":["account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"Linux PAM module","requires_auth":"none","summary":"Attackers can bypass authentication in PAM-PKCS#11 by creating a token with the user's public certificate, allowing unauthorized login as the victim.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":9.2,"severity":"critical","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:L/SC:L/SI:L/SA:L","version":"4.0"},"cwes":[{"id":"CWE-287","name":"Improper Authentication"}],"description":"PAM-PKCS#11 is a Linux-PAM login module that allows a X.509 certificate based user login. Prior to version 0.6.13, if cert_policy is set to none (the default value), then pam_pkcs11 will only check if the user is capable of logging into the token. An attacker may create a different token with the user's public data (e.g. the user's certificate) and a PIN known to the attacker. If no signature with the private key is required, then the attacker may now login as user with that created token. The default to *not* check the private key's signature has been changed with commit commi6638576892b59a99389043c90a1e7dd4d783b921, so that all versions starting with pam_pkcs11-0.6.0 should be affected. As a workaround, in `pam_pkcs11.conf`, set at least `cert_policy = signature;`.","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":"PAM-PKCS#11 vulnerable to authentication bypass with default value for `cert_policy` (`none`)","id":"CVE-2025-24032","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2025"},"n_packages":0,"n_references":5,"next":{"headline":"@fastify/multipart vulnerable to unlimited consumption of resources","id":"CVE-2025-24033"},"packages":[],"prev":{"headline":"PAM-PKCS#11 vulnerable to segmentation fault on ctrl-c/ctrl-d when asked for PIN","id":"CVE-2025-24031"},"products":["pam_pkcs11"],"published":"2025-02-10","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-05-21","vendors":["OpenSC"]},"summary":"Attackers can bypass authentication in PAM-PKCS#11 by creating a token with the user's public certificate, allowing unauthorized login as the victim.","url":"https://insights.sbomify.com/CVE-2025-24032/"}