{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-43660 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2023-43660 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-43660 is a medium-severity authentication bypass vulnerability in warp-tech warpgate, published on 27 Sep 2023. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-43660 and fix it if it is affected.\n\nWhat it is: CVE-2023-43660 is a medium-severity authentication bypass vulnerability in warp-tech warpgate, published on 27 Sep 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2023-43660 in the wild and no public exploit code.\n\nAffected product: warp-tech warpgate. 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-2023-43660/ (Markdown: https://insights.sbomify.com/CVE-2023-43660/index.md)","id":"CVE-2023-43660","markdown":"https://insights.sbomify.com/CVE-2023-43660/index.md","name":"CVE-2023-43660","record":{"aliases":["GHSA-3cjp-w4cp-m9c8"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"SSH bastion host","requires_auth":"none","summary":"Attackers can bypass SSH key authentication in Warpgate by sending unsigned key offers, requiring specific user configuration and knowledge of public keys.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"warpgate","vendor":"warpgate_project"}],"cvss":{"score":4.8,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-347","name":"Improper Verification of Cryptographic Signature"},{"id":"CWE-287","name":"Improper Authentication"}],"description":"Warpgate is a smart SSH, HTTPS and MySQL bastion host for Linux that doesn't need special client apps. The SSH key verification for a user can be bypassed by sending an SSH key offer without a signature. This allows bypassing authentication under following conditions: 1. The attacker knows the username and a valid target name 2. The attacked knows the user's public key and 3. Only SSH public key authentication is required for the user account. This issue has been addressed in version 0.8.1. Users are advised to upgrade. There are no known workarounds for this vulnerability.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"SSH key password bypassed in warpgate","id":"CVE-2023-43660","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2023"},"n_packages":0,"n_references":2,"next":{"headline":"Cachet vulnerable to Authenticated Remote Code Execution","id":"CVE-2023-43661"},"packages":[],"prev":{"headline":"Cross-site Scripting via email preview when CSP disabled in Discourse","id":"CVE-2023-43659"},"products":["warpgate"],"published":"2023-09-27","related":[{"cvss_score":7.1,"headline":"User authorization bug leading to privilege escalation in warpgate","id":"CVE-2023-48712","kev_date_added":null,"published":"2023-11-24"},{"cvss_score":6.4,"headline":"User login confusion with SSO in warpgate","id":"CVE-2023-37268","kev_date_added":null,"published":"2023-07-14"},{"cvss_score":5.8,"headline":"Warpgate: SSO CSRF -- State Token Not Validated on Return","id":"CVE-2026-44347","kev_date_added":null,"published":"2026-05-12"}],"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":"2024-09-20","vendors":["warp-tech"]},"summary":"Attackers can bypass SSH key authentication in Warpgate by sending unsigned key offers, requiring specific user configuration and knowledge of public keys.","url":"https://insights.sbomify.com/CVE-2023-43660/"}