{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-23168 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-23168 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-23168 is a medium-severity vulnerability in Versa Director, published on 18 Jun 2025. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-23168 and fix it if it is affected.\n\nWhat it is: CVE-2025-23168 is a medium-severity vulnerability in Versa Director, published on 18 Jun 2025. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-23168 in the wild and no public exploit code.\n\nAffected product: Versa Director. 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-2025-23168/ (Markdown: https://insights.sbomify.com/CVE-2025-23168/index.md)","id":"CVE-2025-23168","markdown":"https://insights.sbomify.com/CVE-2025-23168/index.md","name":"CVE-2025-23168","record":{"aliases":["GHSA-p4f9-mqjc-2hrf"],"analysis":{"component_type":"network_device","fix_type":"upgrade","impacts":["account_takeover","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"SD-WAN orchestration platform","requires_auth":"low_privilege","summary":"Attackers can bypass 2FA by redirecting OTPs or reusing codes, leading to account takeover in Versa Director SD-WAN platforms.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"hackerone","cpe":[{"product":"versa_director","vendor":"versa-networks"}],"cvss":{"score":6.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L","version":"3.1"},"cwes":[{"id":"CWE-290","name":"Authentication Bypass by Spoofing"}],"description":"The Versa Director SD-WAN orchestration platform implements Two-Factor Authentication (2FA) using One-Time Passcodes (OTP) delivered via email or SMS. Versa Director accepts untrusted user input when dispatching 2FA codes, allowing an attacker who knows a valid username and password to redirect the OTP delivery (SMS/email) to their own device. OTP/TOTP codes are not invalidated after use, enabling reuse by an attacker who has previously intercepted or obtained a valid code. In addition, the 2FA system does not adequately restrict the number or frequency of login attempts. The OTP values are generated from a relatively small keyspace, making brute-force attacks more feasible. \r\n\r\nExploitation Status: \r\n\r\nVersa Networks is not aware of any reported instance where this vulnerability was exploited. Proof of concept for this vulnerability has been disclosed by third party security researchers.  \r\n\r\nWorkarounds or Mitigation: \r\n\r\nVersa recommends that Director be upgraded to one of the remediated software versions.","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":"Security feature bypass in Director","id":"CVE-2025-23168","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2025"},"n_packages":0,"n_references":5,"next":{"headline":"Cross-site scripting in Director","id":"CVE-2025-23169"},"packages":[],"prev":{"headline":"Other in node","id":"CVE-2025-23167"},"products":["Director"],"published":"2025-06-18","related":[{"cvss_score":6.6,"headline":"Versa Director Dangerous File Type Upload","id":"CVE-2024-39717","kev_date_added":"2024-08-23","published":"2024-08-22"},{"cvss_score":10,"headline":"Hardcoded credentials in Director","id":"CVE-2024-42450","kev_date_added":null,"published":"2024-11-19"},{"cvss_score":9.8,"headline":"Hardcoded credentials in Director","id":"CVE-2025-24288","kev_date_added":null,"published":"2025-06-18"},{"cvss_score":9.8,"headline":"Command injection in Versa Director","id":"CVE-2019-25029","kev_date_added":null,"published":"2021-05-26"},{"cvss_score":7.5,"headline":"Information disclosure in Director","id":"CVE-2025-23173","kev_date_added":null,"published":"2025-06-18"},{"cvss_score":7.2,"headline":"File upload in Director","id":"CVE-2025-23171","kev_date_added":null,"published":"2025-06-18"},{"cvss_score":7.2,"headline":"Server-side request forgery in Director","id":"CVE-2025-23172","kev_date_added":null,"published":"2025-06-18"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"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":"partial"},"state":"PUBLISHED","updated":"2025-06-23","vendors":["Versa"]},"summary":"Attackers can bypass 2FA by redirecting OTPs or reusing codes, leading to account takeover in Versa Director SD-WAN platforms.","url":"https://insights.sbomify.com/CVE-2025-23168/"}