LiveActive security incident?Get immediate response
CVE Record

CVE-2023-7103: Authentication Bypass in ZKSoftware's UFace 5

Authentication Bypass by Primary Weakness vulnerability in ZKSoftware Biometric Security Solutions UFace 5 allows Authentication Bypass. This issue affects UFace 5: through 12022024.

CriticalCVSS 9.8Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

CVE-2023-7103 is a critical authentication bypass in ZKSoftware Biometric Security Solutions UFace 5. A remote attacker may be able to access the system without valid login. Because biometric access-control systems can affect physical security and sensitive identity data, exposed deployments should be treated as urgent until verified safe.

Executive priority

Treat as high-priority for any organization using UFace 5 in access-control or biometric workflows. Prioritize exposure reduction immediately, then confirm official remediation with the vendor or cited government advisory.

Technical view

The CVE record describes CWE-305 authentication bypass affecting UFace 5 through 12022024. CVSS 3.1 is 9.8: network reachable, low complexity, no privileges, no user interaction, with high confidentiality, integrity, and availability impact. Public details are limited, and the provided sources do not name a specific patched version.

Likely exposure

Highest concern is UFace 5 reachable from untrusted networks or used for facility access, attendance, or biometric identity workflows. Internal-only systems still matter because compromise could affect physical access decisions or stored personal data.

Exploitation context

The source bundle does not show CISA KEV listing or cited evidence of active exploitation. However, the CVSS vector indicates exploitation could be remote and unauthenticated if the vulnerable service is reachable.

Researcher notes

Public disclosure is sparse. The CVE states authentication bypass and a broad affected range, but does not provide technical root cause, exploit conditions, or patch details. One listed USOM URL is marked broken in the source bundle; the Turkish cybersecurity advisory remains cited.

Mitigation direction

  • Identify all ZKSoftware UFace 5 deployments and owners.
  • Check vendor and government advisories for patched firmware or official workarounds.
  • Remove internet exposure for UFace 5 management interfaces.
  • Restrict access to trusted administrative networks only.
  • Increase monitoring for unusual authentication, configuration, or access-control events.
  • Review physical access procedures for fallback controls until remediated.

Validation and detection

  • Confirm whether deployed devices are UFace 5.
  • Record firmware or software version and compare against vendor guidance.
  • Verify whether any UFace 5 interface is internet accessible.
  • Review logs for unexpected administrative access or configuration changes.
  • Confirm compensating network restrictions are enforced.
  • Track remediation status for each affected device.
Prepared
Confidence
medium
Sources
4

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.

cwe · low confidence lookup

CWE-305: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Credential and access behavior lookup

The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2023-7103 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
Critical
CVSS
9.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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.

1CVSS vectors
3Timeline events
2ADP providers
3Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
9.8CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9TR-CERT

Vulnerability scoring details

Base CVSS 3.1 score

9.8Critical
CVSS 3.1 vector shape for CVE-2023-7103Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CVECVE Program Container
CISA-ADPCISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
ZKSoftware Biometric Security SolutionsUFace 50unaffected
Weakness

CWE details

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

CWE-305 · source CWE mapping

Authentication Bypass by Primary Weakness

Authentication Bypass by Primary Weakness represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.