LiveActive security incident?Get immediate response
CVE Record

CVE-2023-41069: This issue was addressed by improving Face ID anti-spoofing models.

This issue was addressed by improving Face ID anti-spoofing models. This issue is fixed in iOS 17 and iPadOS 17. A 3D model constructed to look like the enrolled user may authenticate via Face ID.

MediumCVSS 5.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

Apple fixed a Face ID anti-spoofing weakness in iOS 17 and iPadOS 17. A 3D model made to resemble the enrolled user may have been able to authenticate as that user. This is mainly a physical-access and targeted-risk issue, not a remote mass-exploitation scenario based on the provided sources.

Executive priority

Treat this as a moderate mobile-device hygiene priority. It is not described as remotely exploitable or actively exploited, but it can undermine biometric trust for targeted users. Prioritize executive, administrator, finance, and legal devices first.

Technical view

CVE-2023-41069 is classified as CWE-290, authentication bypass by spoofing. Apple states improved Face ID anti-spoofing models addressed the issue. CVSS 3.1 is 5.5 with local attack vector, low complexity, no privileges, user interaction required, no confidentiality impact, high integrity impact, and no availability impact.

Likely exposure

Potential exposure is Apple iOS and iPadOS devices using affected Face ID behavior before iOS 17 or iPadOS 17. The source bundle does not enumerate exact vulnerable versions, device models, or configuration prerequisites beyond Apple’s fixed versions.

Exploitation context

The provided sources do not claim active exploitation, and the CVE is not marked KEV. Practical abuse appears targeted because it requires a 3D model resembling the enrolled user and local interaction with the device authentication flow.

Researcher notes

Evidence is narrow: Apple describes the issue and fixed release, while CVE metadata provides CWE and CVSS. Exact vulnerable version boundaries, impacted device models, and real-world exploit observations are not provided in the source bundle.

Mitigation direction

  • Update eligible devices to iOS 17 or iPadOS 17 or later.
  • Use MDM to enforce minimum supported iOS and iPadOS versions.
  • Review exceptions for devices that cannot upgrade to iOS 17 or iPadOS 17.
  • Check Apple guidance for any model-specific update or support constraints.
  • Apply compensating physical-security controls for high-risk executive or privileged devices.

Validation and detection

  • Inventory iOS and iPadOS versions across managed devices.
  • Confirm iOS 17 or iPadOS 17 installation through MDM reporting.
  • Identify devices still below Apple’s fixed release level.
  • Verify high-risk users are not excluded from update enforcement.
  • Document unsupported or unmanaged devices for risk acceptance or replacement.
Prepared
Confidence
high
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-290: 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
cve · low confidence lookup

CVE-2023-41069 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
Medium
CVSS
5.5 (3.1)
Known Exploited
No
Published

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

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
0Timeline events
0ADP providers
3Source links

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
5.5CVSS 3.1MediumCVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N1.83.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.5Medium
CVSS 3.1 vector shape for CVE-2023-41069Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

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

Products and packages named in the record

VendorProductVersion / packageStatus
AppleiOS and iPadOSunspecifiedListed
Weakness

CWE details

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

CWE-290 · source CWE mapping

Authentication Bypass by Spoofing

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