Skip to main content
CVE-2024-37408VulnerabilityPublished Updated

CVE-2024-37408: fprintd · n/a

Affects fprintdSource CVE Database V5

0

Not known to be exploited · CVSS 7.3 High.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score
7.3High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 19% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 8 Jun 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

What to do

Affected software

ProductAffectedFixed in
Debiandebian/fprintdpkg:deb/debian/fprintdOther threatsAffected
  • <=1.94.3
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate this vulnerability, organizations should immediately audit PAM configurations involving pam_fprintd.so, especially those using "auth sufficient" for sudo authentication. Restrict pam_fprintd.so usage to front-end applications that implement proper security attention mechanisms to ensure deliberate user authentication. Consider temporarily disabling fingerprint authentication for sudo or replacing it with more secure multi-factor authentication methods until a patch or official fix is released. Monitor local user activities and sudo logs for unusual authentication patterns or unexpected privilege escalations. Implement strict local access controls to limit potential attackers from gaining initial footholds. Stay informed about updates from the fprintd maintainers and promptly apply patches once available. Additionally, educate users about the risks of unintended authorizations when using biometric authentication. For critical systems, consider deploying host-based intrusion detection systems (HIDS) to detect anomalous sudo usage. Finally, review and harden overall PAM configurations to minimize exposure to similar authentication bypass issues.

Description

fprintd through 1.94.3 lacks a security attention mechanism, and thus unexpected actions might be authorized by "auth sufficient pam_fprintd.so" for Sudo. NOTE: the supplier disputes this because they believe issue resolution would involve modifying the PAM configuration to restrict pam_fprintd.so to front-ends that implement a proper attention mechanism, not modifying pam_fprintd.so or fprintd.

References

Community reviews

Loading reviews…