{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-34772 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-34772 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-34772 is a medium-severity authentication bypass vulnerability in Tabit, published on 22 Aug 2022. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-34772 and fix it if it is affected.\n\nWhat it is: CVE-2022-34772 is a medium-severity authentication bypass vulnerability in Tabit, published on 22 Aug 2022. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2022-34772 in the wild and no public exploit code.\n\nAffected product: Tabit. 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-2022-34772/ (Markdown: https://insights.sbomify.com/CVE-2022-34772/index.md)","id":"CVE-2022-34772","markdown":"https://insights.sbomify.com/CVE-2022-34772/index.md","name":"CVE-2022-34772","record":{"aliases":["GHSA-c38h-5gmx-rf6h"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["account_takeover"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Tabit authentication system","requires_auth":"high_privilege","summary":"Attackers can bypass authentication by repeatedly resending 4-digit OTPs due to missing rate limiting, leading to account takeover.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"INCD","cpe":[{"product":"tabit","vendor":"tabit"}],"cvss":{"score":4.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:A/AC:L/PR:H/UI:N/S:U/C:L/I:L/A:L","version":"3.1"},"cwes":[{"id":"CWE-521","name":"Weak Password Requirements"}],"description":"Tabit - password enumeration. Description: Tabit - password enumeration. The passwords for the Tabit system is a 4 digit OTP. One can resend OTP and try logging in indefinitely. Once again, this is an example of OWASP: API4 - Rate limiting.","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":"Tabit - password enumeration","id":"CVE-2022-34772","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2022"},"n_packages":0,"n_references":1,"next":{"headline":"Tabit - HTTP Method manipulation","id":"CVE-2022-34773"},"packages":[],"prev":{"headline":"Tabit - arbitrary SMS send on Tabits behalf","id":"CVE-2022-34771"},"products":["Tabit"],"published":"2022-08-22","related":[{"cvss_score":6.3,"headline":"Tabit - Arbitrary account modification","id":"CVE-2022-34774","kev_date_added":null,"published":"2022-08-22"},{"cvss_score":6.3,"headline":"Tabit - Excessive data exposure","id":"CVE-2022-34775","kev_date_added":null,"published":"2022-08-22"},{"cvss_score":5.5,"headline":"Tabit - arbitrary SMS send on Tabits behalf","id":"CVE-2022-34771","kev_date_added":null,"published":"2022-08-22"},{"cvss_score":5.5,"headline":"Tabit - giftcard stealth","id":"CVE-2022-34776","kev_date_added":null,"published":"2022-08-22"},{"cvss_score":4.9,"headline":"Tabit - HTTP Method manipulation","id":"CVE-2022-34773","kev_date_added":null,"published":"2022-08-22"},{"cvss_score":4.6,"headline":"Tabit - sensitive information disclosure","id":"CVE-2022-34770","kev_date_added":null,"published":"2022-08-22"}],"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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-09-17","vendors":["Tabit"]},"summary":"Attackers can bypass authentication by repeatedly resending 4-digit OTPs due to missing rate limiting, leading to account takeover.","url":"https://insights.sbomify.com/CVE-2022-34772/"}