{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-14122 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-14122 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-14122 is a medium-severity vulnerability in MIUI, published on 21 Apr 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-2020-14122 and fix it if it is affected.\n\nWhat it is: CVE-2020-14122 is a medium-severity vulnerability in MIUI, published on 21 Apr 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-2020-14122 in the wild and no public exploit code.\n\nAffected product: MIUI. 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-2020-14122/ (Markdown: https://insights.sbomify.com/CVE-2020-14122/index.md)","id":"CVE-2020-14122","markdown":"https://insights.sbomify.com/CVE-2020-14122/index.md","name":"CVE-2020-14122","record":{"aliases":["GHSA-c8r8-gwg2-5wfh"],"analysis":{"component_type":"mobile_application","fix_type":"patch","impacts":["data_read","security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Xiaomi MIUI","requires_auth":"low_privilege","summary":"Attackers can leak user information and potentially forge identities on Xiaomi phones due to missing parameter verification in MIUI.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Xiaomi","cpe":[{"product":"miui","vendor":"mi"}],"cvss":{"score":5.5,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-345","name":"Insufficient Verification of Data Authenticity"}],"description":"Some Xiaomi phones have information leakage vulnerabilities, and some of them may be able to forge a specific identity due to the lack of parameter verification, resulting in user information leakage.","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":"Information disclosure in MIUI","id":"CVE-2020-14122","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2020"},"n_packages":0,"n_references":1,"next":{"headline":"Use after free in MIUI","id":"CVE-2020-14123"},"packages":[],"prev":{"headline":"Business logic in Mi App Store","id":"CVE-2020-14121"},"products":["MIUI"],"published":"2022-04-21","related":[{"cvss_score":8.8,"headline":"Missing authorization in MIUI","id":"CVE-2020-14120","kev_date_added":null,"published":"2022-04-21"},{"cvss_score":7.5,"headline":"Memory corruption in Redmi K40 ,Redmi Note10 Pro","id":"CVE-2020-14127","kev_date_added":null,"published":"2022-07-14"},{"cvss_score":7.5,"headline":"Memory corruption in Redmi Note 11 ,Redmi Note 9T","id":"CVE-2020-14125","kev_date_added":null,"published":"2022-06-08"},{"cvss_score":7.5,"headline":"Use after free in MIUI","id":"CVE-2020-14123","kev_date_added":null,"published":"2022-04-22"},{"cvss_score":5.5,"headline":"Information disclosure in Xiaomi 10","id":"CVE-2020-14105","kev_date_added":null,"published":"2021-04-20"},{"cvss_score":5.5,"headline":"Information disclosure in Xiaomi 10","id":"CVE-2020-14103","kev_date_added":null,"published":"2021-04-08"}],"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-08-04","vendors":["n/a"]},"summary":"Attackers can leak user information and potentially forge identities on Xiaomi phones due to missing parameter verification in MIUI.","url":"https://insights.sbomify.com/CVE-2020-14122/"}