{"vulnerability": "CVE-2025-24032", "sightings": [{"uuid": "fa80c450-93a8-4b47-a231-04ba9357a117", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-24032", "type": "seen", "source": "https://bsky.app/profile/cve.skyfleet.blue/post/3lhtx7ofiha2a", "content": "", "creation_timestamp": "2025-02-10T20:10:09.219782Z"}, {"uuid": "3da5040c-6c3f-44d0-b815-839060ea494e", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-24032", "type": "seen", "source": "https://bsky.app/profile/dinosn.bsky.social/post/3lhxbja7oi225", "content": "", "creation_timestamp": "2025-02-12T03:52:25.593144Z"}, {"uuid": "448afd09-6f46-4bf8-9bf5-da54db21b638", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-24032", "type": "seen", "source": "https://infosec.exchange/users/cve/statuses/113980382711327196", "content": "", "creation_timestamp": "2025-02-10T15:50:17.597951Z"}, {"uuid": "e4df6b59-5bc9-4967-ba35-62c0a58a35a1", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-24032", "type": "seen", "source": "https://bsky.app/profile/cve-notifications.bsky.social/post/3lhtk6j6lx42c", "content": "", "creation_timestamp": "2025-02-10T16:16:47.682320Z"}, {"uuid": "5ad737e9-63c3-4aec-95e1-7687590a358a", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-24032", "type": "seen", "source": "https://infosec.exchange/users/cR0w/statuses/113980543498444388", "content": "", "creation_timestamp": "2025-02-10T16:31:11.275779Z"}, {"uuid": "7a38d18e-4b74-4b17-8db4-52ee4faf9abb", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-24032", "type": "published-proof-of-concept", "source": "Telegram/OeH9zkywoY5RVyH3R_smk_5t4405jKnk6ZNWTlGk6rqPQWQ", "content": "", "creation_timestamp": "2025-02-10T17:30:24.000000Z"}, {"uuid": "a80f0b26-2d7a-4191-87ac-70689a574df9", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-24032", "type": "seen", "source": "https://bsky.app/profile/tmjintel.bsky.social/post/3lhy5yqd6p527", "content": "", "creation_timestamp": "2025-02-12T12:22:08.391375Z"}, {"uuid": "6080ce9e-0372-4159-ade0-7dca544c02c0", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-24032", "type": "seen", "source": "https://bsky.app/profile/bolhasec.com/post/3llywykafub2u", "content": "", "creation_timestamp": "2025-04-04T17:30:12.659542Z"}, {"uuid": "998bd1fa-c833-444c-af4b-e95612631fec", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-24032", "type": "seen", "source": "https://t.me/cvedetector/17563", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-24032 - Linux-PAM PAM-PKCS#11 Public Key Certificate Token Hijacking\", \n  \"Content\": \"CVE ID : CVE-2025-24032 \nPublished : Feb. 10, 2025, 4:15 p.m. | 1\u00a0hour, 27\u00a0minutes ago \nDescription : 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;`. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"10 Feb 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-02-10T18:45:34.000000Z"}, {"uuid": "d898a57e-4f69-4b01-b930-be22847e6b21", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2025-24032", "type": "seen", "source": "Telegram/A7-5UCNKfEn7GNuXcYpaEmNvFzHdVaxAw6ttggaZRamuS6Le", "content": "", "creation_timestamp": "2025-02-18T21:11:31.000000Z"}]}