{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-47034 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-47034 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-47034 is a critical authentication bypass vulnerability in n/a, published on 13 Feb 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-2022-47034 and fix it if it is affected.\n\nWhat it is: CVE-2022-47034 is a critical authentication bypass vulnerability in n/a, published on 13 Feb 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-2022-47034 in the wild and no public exploit code.\n\nAffected product: n/a. 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-47034/ (Markdown: https://insights.sbomify.com/CVE-2022-47034/index.md)","id":"CVE-2022-47034","markdown":"https://insights.sbomify.com/CVE-2022-47034/index.md","name":"CVE-2022-47034","record":{"aliases":["GHSA-2ffj-9mcf-rmj4"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"PlaySMS web application","requires_auth":"none","summary":"Attackers can bypass authentication in PlaySMS via type juggling in the authentication function, gaining unauthorized access.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"playsms","vendor":"playsms"}],"cvss":{"score":9.8,"severity":"critical","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-697","name":"Incorrect Comparison"}],"description":"A type juggling vulnerability in the component /auth/fn.php of PlaySMS v1.4.5 and earlier allows attackers to bypass authentication.","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":"Auth bypass in n/a","id":"CVE-2022-47034","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2022"},"n_packages":0,"n_references":2,"next":{"headline":"Memory corruption in n/a","id":"CVE-2022-47035"},"packages":[],"prev":{"headline":"Privilege escalation in n/a","id":"CVE-2022-47029"},"products":["n/a"],"published":"2023-02-13","related":[{"cvss_score":9.8,"headline":"PlaySMS Server-Side Template Injection","id":"CVE-2020-8644","kev_date_added":"2021-11-03","published":"2020-02-05"},{"cvss_score":9.8,"headline":"Code injection in n/a","id":"CVE-2021-40373","kev_date_added":null,"published":"2021-09-10"},{"cvss_score":9.8,"headline":"File upload in n/a","id":"CVE-2017-9101","kev_date_added":null,"published":"2017-05-21"},{"cvss_score":8.8,"headline":"File upload in n/a","id":"CVE-2017-9080","kev_date_added":null,"published":"2017-05-19"},{"cvss_score":7.5,"headline":"Path traversal in n/a","id":"CVE-2008-5881","kev_date_added":null,"published":"2009-01-09"},{"cvss_score":7.5,"headline":"Code injection in n/a","id":"CVE-2009-0103","kev_date_added":null,"published":"2009-01-09"}],"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":"yes","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-03-21","vendors":["n/a"]},"summary":"Attackers can bypass authentication in PlaySMS via type juggling in the authentication function, gaining unauthorized access.","url":"https://insights.sbomify.com/CVE-2022-47034/"}