{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2024-10327 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-10327 yet. Limit exposure of the affected software until one is available.","what":"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."},"fix_prompt":"Check this codebase for CVE-2024-10327 and fix it if it is affected.\n\nWhat 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.\nExploitation: There is no known exploitation of CVE-2024-10327 in the wild and no public exploit code.\n\nAffected product: Okta Verify for iOS. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2024-10327/ (Markdown: https://insights.sbomify.com/CVE-2024-10327/index.md)","id":"CVE-2024-10327","markdown":"https://insights.sbomify.com/CVE-2024-10327/index.md","name":"CVE-2024-10327","record":{"aliases":["GHSA-55f2-f95r-q833"],"analysis":{"component_type":"mobile_application","fix_type":"patch","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"Okta Verify iOS app","requires_auth":"none","summary":"Attackers can bypass Okta Verify push authentication on iOS by exploiting ContextExtension flaws, allowing unauthorized access regardless of user selection.","user_interaction":"required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Okta","cpe":[],"cvss":{"score":8.1,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-287","name":"Improper Authentication"}],"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. \nThe ContextExtension feature is one of several push mechanisms available when using Okta Verify Push on iOS devices. The vulnerable flows include: \n* 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; \n* When a user is presented with a notification on the home screen and drags the notification down and selects their reply; \n* When an Apple Watch is used to reply directly to a notification. \n\n 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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Auth bypass in Okta Verify for iOS","id":"CVE-2024-10327","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2024"},"n_packages":0,"n_references":2,"next":{"headline":"Ultimate Bootstrap Elements for Elementor \u003c= 1.4.6 - Authenticated (Contributor+) Sensitive Information Exposure","id":"CVE-2024-10329"},"packages":[],"prev":{"headline":"RomethemeKit For Elementor \u003c= 1.5.3 - Missing Authorization in save_options and reset_widgets","id":"CVE-2024-10326"},"products":["Okta Verify for iOS"],"published":"2024-10-24","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2024-10-25","vendors":["Okta"]},"summary":"Attackers can bypass Okta Verify push authentication on iOS by exploiting ContextExtension flaws, allowing unauthorized access regardless of user selection.","url":"https://insights.sbomify.com/CVE-2024-10327/"}