{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-7961 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-7961 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-7961 is a medium-severity vulnerability in Huawei Technologies Co., Ltd. Emily-AL00A, published on 27 Nov 2018. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2018-7961 and fix it if it is affected.\n\nWhat it is: CVE-2018-7961 is a medium-severity vulnerability in Huawei Technologies Co., Ltd. Emily-AL00A, published on 27 Nov 2018. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2018-7961 in the wild and no public exploit code.\n\nAffected product: Huawei Technologies Co., Ltd. Emily-AL00A. 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-2018-7961/ (Markdown: https://insights.sbomify.com/CVE-2018-7961/index.md)","id":"CVE-2018-7961","markdown":"https://insights.sbomify.com/CVE-2018-7961/index.md","name":"CVE-2018-7961","record":{"aliases":["GHSA-hxq2-xf4p-6vfm"],"analysis":{"component_type":"mobile_application","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Huawei smartphone","requires_auth":"none","summary":"An attacker can leak sensitive information by tricking a user into accessing a malicious site or app due to incorrect SMS verification code processing.","user_interaction":"required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"huawei","cpe":[{"product":"emily-al00a_firmware","vendor":"huawei"}],"cvss":{"score":6.5,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N","version":"3.0"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"There is a smart SMS verification code vulnerability in some Huawei smart phones. An attacker should trick a user to access malicious Website or malicious App and register. Due to incorrect processing of the smart SMS verification code, successful exploitation can cause sensitive information leak.","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 Emily-AL00A","id":"CVE-2018-7961","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2018"},"n_packages":0,"n_references":1,"next":{"headline":"DO NOT USE THIS CANDIDATE NUMBER.","id":"CVE-2018-7963"},"packages":[],"prev":{"headline":"Information disclosure in eSpace 7950","id":"CVE-2018-7960"},"products":["Emily-AL00A"],"published":"2018-11-27","related":[{"cvss_score":7.8,"headline":"Use after free in Emily-AL00A, Emily-TL00B, Emily-L09C, Emily-L29C","id":"CVE-2019-5282","kev_date_added":null,"published":"2019-11-13"},{"cvss_score":6.8,"headline":"Auth bypass in Emily-AL00A","id":"CVE-2018-7925","kev_date_added":null,"published":"2018-11-13"},{"cvss_score":6.8,"headline":"Security feature bypass in Emily-AL00A","id":"CVE-2018-7944","kev_date_added":null,"published":"2018-07-05"},{"cvss_score":3.9,"headline":"Auth bypass in Emily-AL00A","id":"CVE-2018-7947","kev_date_added":null,"published":"2018-07-31"}],"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-05","vendors":["Huawei Technologies Co., Ltd."]},"summary":"An attacker can leak sensitive information by tricking a user into accessing a malicious site or app due to incorrect SMS verification code processing.","url":"https://insights.sbomify.com/CVE-2018-7961/"}