# CVE-2024-10327: Auth bypass in Okta Verify for iOS

> Attackers can bypass Okta Verify push authentication on iOS by exploiting ContextExtension flaws, allowing unauthorized access regardless of user selection.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 24 Oct 2024
- **Updated:** 25 Oct 2024
- **Also known as:** GHSA-55f2-f95r-q833

## What is CVE-2024-10327?

CVE-2024-10327 is a high-severity authentication bypass vulnerability in Okta Verify for iOS, published on 24 Oct 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

A vulnerability in Okta Verify for iOS versions 9.25.1 (beta) and 9.27.0 (including beta) allows push notification responses through the iOS ContextExtension feature allowing the authentication to proceed regardless of the user’s selection. When a user long-presses the notification banner and selects an option, both options allow the authentication to succeed. 
The ContextExtension feature is one of several push mechanisms available when using Okta Verify Push on iOS devices. The vulnerable flows include: 
* When a user is presented with a notification on a locked screen, the user presses on the notification directly and selects their reply without unlocking the device; 
* When a user is presented with a notification on the home screen and drags the notification down and selects their reply; 
* When an Apple Watch is used to reply directly to a notification. 

 A pre-condition for this vulnerability is that the user must have enrolled in Okta Verify while the Okta customer was using Okta Classic. This applies irrespective of whether the organization has since upgraded to Okta Identity Engine.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2024-10327?


## How do I fix CVE-2024-10327?

No fix has been published for CVE-2024-10327 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-10327 being exploited?

There is no known exploitation of CVE-2024-10327 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-10327 and fix it if it is affected.

What it is: CVE-2024-10327 is a high-severity authentication bypass vulnerability in Okta Verify for iOS, published on 24 Oct 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2024-10327 in the wild and no public exploit code.

Affected product: Okta Verify for iOS. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-10327/ (Markdown: https://insights.sbomify.com/CVE-2024-10327/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-10327
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-10327
- OSV: https://osv.dev/vulnerability/CVE-2024-10327

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-10327/
Summaries are generated and may contain mistakes; the official description above is the record.