{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-34771 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-34771 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-34771 is a medium-severity 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-34771 and fix it if it is affected.\n\nWhat it is: CVE-2022-34771 is a medium-severity 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-34771 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-34771/ (Markdown: https://insights.sbomify.com/CVE-2022-34771/index.md)","id":"CVE-2022-34771","markdown":"https://insights.sbomify.com/CVE-2022-34771/index.md","name":"CVE-2022-34771","record":{"aliases":["GHSA-gxfw-27c3-xr84"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["data_modify","other"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Tabit SMS service","requires_auth":"low_privilege","summary":"Attackers can send arbitrary SMS messages to any registered user via the resend OTP API, potentially enabling phishing or spam campaigns.","user_interaction":"not_required","vuln_class":"business_logic"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"INCD","cpe":[{"product":"tabit","vendor":"tabit"}],"cvss":{"score":5.5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L","version":"3.1"},"cwes":[],"description":"Tabit - arbitrary SMS send on Tabits behalf. The resend OTP API of tabit allows an adversary to send messages on tabits behalf to anyone registered on the system - the API receives the parameters: phone number, and CustomMessage, We can use that API to craft malicious messages to any user of the system. In addition, the API probably has some kind of template injection potential. When entering {{OTP}} in the custom message field it is formatted into an OTP.","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 - arbitrary SMS send on Tabits behalf","id":"CVE-2022-34771","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"business_logic","year":"2022"},"n_packages":0,"n_references":1,"next":{"headline":"Tabit - password enumeration","id":"CVE-2022-34772"},"packages":[],"prev":{"headline":"Tabit - sensitive information disclosure","id":"CVE-2022-34770"},"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 - 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"},{"cvss_score":4.3,"headline":"Tabit - password enumeration","id":"CVE-2022-34772","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":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-09-16","vendors":["Tabit"]},"summary":"Attackers can send arbitrary SMS messages to any registered user via the resend OTP API, potentially enabling phishing or spam campaigns.","url":"https://insights.sbomify.com/CVE-2022-34771/"}