{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-5212 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-5212 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-5212 is a medium-severity missing authorization vulnerability in P20, published on 29 Nov 2019. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2019-5212 and fix it if it is affected.\n\nWhat it is: CVE-2019-5212 is a medium-severity missing authorization vulnerability in P20, published on 29 Nov 2019. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2019-5212 in the wild and no public exploit code.\n\nAffected product: P20. 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-2019-5212/ (Markdown: https://insights.sbomify.com/CVE-2019-5212/index.md)","id":"CVE-2019-5212","markdown":"https://insights.sbomify.com/CVE-2019-5212/index.md","name":"CVE-2019-5212","record":{"aliases":["GHSA-5mr2-62qq-29fg"],"analysis":{"component_type":"mobile_application","fix_type":"patch","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Huawei Share app","requires_auth":"none","summary":"An attacker can trick a user into installing a malicious app to exploit improper access control in Huawei Share, leading to information disclosure.","user_interaction":"required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"huawei","cpe":[{"product":"p20_firmware","vendor":"huawei"}],"cvss":{"score":5.5,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-732","name":"Incorrect Permission Assignment for Critical Resource"}],"description":"There is an improper access control vulnerability in Huawei Share. The software does not properly restrict access to certain file from certain application. An attacker tricks the user into installing a malicious application then establishing a connect to the attacker through Huawei Share, successful exploit could cause information disclosure.","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":"Missing authorization in P20","id":"CVE-2019-5212","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2019"},"n_packages":0,"n_references":1,"next":{"headline":"Auth bypass in Honor play","id":"CVE-2019-5213"},"packages":[],"prev":{"headline":"Other in P20","id":"CVE-2019-5211"},"products":["P20"],"published":"2019-11-29","related":[{"cvss_score":5.9,"headline":"Memory corruption in Huawei P20","id":"CVE-2018-7987","kev_date_added":null,"published":"2018-12-04"},{"cvss_score":5.7,"headline":"Other in P20","id":"CVE-2019-5211","kev_date_added":null,"published":"2019-11-29"},{"cvss_score":4.6,"headline":"Security feature bypass in P20","id":"CVE-2019-5283","kev_date_added":null,"published":"2019-06-04"},{"cvss_score":4.6,"headline":"Security feature bypass in P20","id":"CVE-2019-5306","kev_date_added":null,"published":"2019-06-04"},{"cvss_score":2.4,"headline":"Auth bypass in P20","id":"CVE-2020-9073","kev_date_added":null,"published":"2020-05-15"}],"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":"An attacker can trick a user into installing a malicious app to exploit improper access control in Huawei Share, leading to information disclosure.","url":"https://insights.sbomify.com/CVE-2019-5212/"}