{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-24189 exists.","fix":"No fix has been published for CVE-2022-24189 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-24189 is a medium-severity authentication bypass vulnerability in n/a, published on 28 Nov 2022. 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-24189 and fix it if it is affected.\n\nWhat it is: CVE-2022-24189 is a medium-severity authentication bypass vulnerability in n/a, published on 28 Nov 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-24189 exists.\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-24189/ (Markdown: https://insights.sbomify.com/CVE-2022-24189/index.md)","id":"CVE-2022-24189","markdown":"https://insights.sbomify.com/CVE-2022-24189/index.md","name":"CVE-2022-24189","record":{"aliases":["GHSA-x859-4wp8-g67f"],"analysis":{"component_type":"mobile_application","fix_type":"no_fix_stated","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Ourphoto App","requires_auth":"none","summary":"Attackers can bypass authorization by removing the user token header, allowing them to enumerate and access other users' information via API calls.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"ourphoto","vendor":"sz-fujia"}],"cvss":{"score":6.5,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-863","name":"Incorrect Authorization"}],"description":"The user_token authorization header on the Ourphoto App version 1.4.1 /apiv1/* end-points is not implemented properly. Removing the value causes all requests to succeed, bypassing authorization and session management. The impact of this vulnerability allows an attacker POST api calls with other users unique identifiers and enumerate information of all other end-users.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":null,"headline":"Auth bypass in n/a","id":"CVE-2022-24189","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":"Missing authorization in n/a","id":"CVE-2022-24190"},"packages":[],"prev":{"headline":"Information disclosure in n/a","id":"CVE-2022-24188"},"products":["n/a"],"published":"2022-11-28","related":[{"cvss_score":7.5,"headline":"Information disclosure in n/a","id":"CVE-2022-24187","kev_date_added":null,"published":"2022-11-28"},{"cvss_score":7.5,"headline":"Information disclosure in n/a","id":"CVE-2022-24188","kev_date_added":null,"published":"2022-11-28"},{"cvss_score":7.5,"headline":"Missing authorization in n/a","id":"CVE-2022-24190","kev_date_added":null,"published":"2022-11-28"}],"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":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-04-29","vendors":["n/a"]},"summary":"Attackers can bypass authorization by removing the user token header, allowing them to enumerate and access other users' information via API calls.","url":"https://insights.sbomify.com/CVE-2022-24189/"}