LiveActive security incident?Get immediate response
CVE Record

CVE-2019-13603: An issue was discovered in the HID Global DigitalPersona (formerly Crossmatch) U.are.U 4500 Fingerprint Rea...

An issue was discovered in the HID Global DigitalPersona (formerly Crossmatch) U.are.U 4500 Fingerprint Reader Windows Biometric Framework driver 5.0.0.5. It has a statically coded initialization vector to encrypt a user's fingerprint image, resulting in weak encryption of that. This, in combination with retrieving an encrypted fingerprint image and encryption key (through another vulnerability), allows an attacker to obtain a user's fingerprint image.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This CVE concerns weak protection of fingerprint images in a specific HID Global DigitalPersona U.are.U 4500 Windows biometric driver. A hard-coded encryption value can help expose a user’s fingerprint image if an attacker also obtains the encrypted image and key through another vulnerability. Biometric compromise is serious because fingerprints cannot be rotated like passwords.

Executive priority

Prioritize inventory and vendor confirmation. This is not presented as broadly internet-exploitable, but it affects sensitive biometric data and may create long-term identity risk if combined with the companion retrieval weakness.

Technical view

The reported issue affects HID Global DigitalPersona U.are.U 4500 Fingerprint Reader Windows Biometric Framework driver 5.0.0.5. The driver uses a static initialization vector when encrypting fingerprint images, weakening confidentiality. The CVE states image recovery requires combination with another vulnerability that retrieves both the encrypted fingerprint image and encryption key.

Likely exposure

Exposure appears limited to Windows systems using the named U.are.U 4500 reader driver version 5.0.0.5. Risk is higher where attackers can access local biometric data paths or pair this flaw with the separate retrieval vulnerability referenced by the CVE description.

Exploitation context

The source bundle does not show CISA KEV listing or confirmed active exploitation. Public references exist, but the provided CVE text frames exploitation as dependent on another vulnerability that supplies the encrypted image and key.

Researcher notes

The CVE record lacks CVSS, CWE, patch details, and precise companion-vulnerability identifiers in the provided bundle. Avoid treating this as standalone fingerprint theft unless evidence shows the encrypted image and key can also be retrieved in the target environment.

Mitigation direction

  • Inventory Windows hosts using HID DigitalPersona U.are.U 4500 driver 5.0.0.5.
  • Check HID or DigitalPersona guidance for fixed driver versions or replacement recommendations.
  • Restrict administrative and local access to systems using affected biometric readers.
  • Consider disabling affected biometric authentication where vendor guidance is unavailable.
  • Treat exposed fingerprint images as sensitive biometric data in incident response.

Validation and detection

  • Confirm the exact fingerprint reader model and Windows Biometric Framework driver version.
  • Identify whether affected hosts store or process fingerprint images locally.
  • Assess whether the separate image-and-key retrieval vulnerability is also present.
  • Review endpoint access controls around biometric software and driver components.
  • Document affected users because biometric data cannot be practically rotated.
Prepared
Confidence
medium
Sources
5

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2019-13603 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
4Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.