{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-18978 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-18978 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-18978 is a high-severity vulnerability in n/a, published on 6 May 2019. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2018-18978 and fix it if it is affected.\n\nWhat it is: CVE-2018-18978 is a high-severity vulnerability in n/a, published on 6 May 2019. 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-2018-18978 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-2018-18978/ (Markdown: https://insights.sbomify.com/CVE-2018-18978/index.md)","id":"CVE-2018-18978","markdown":"https://insights.sbomify.com/CVE-2018-18978/index.md","name":"CVE-2018-18978","record":{"aliases":["GHSA-hgh5-r35v-w387"],"analysis":{"component_type":"mobile_application","fix_type":"patch","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Android medical app","requires_auth":"none","summary":"Attackers can extract a static encryption key to decrypt and modify patient medical data exchanged with the backend server.","user_interaction":"not_required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"contour_diabetes","vendor":"ascensia"}],"cvss":{"score":7.4,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N","version":"3.0"},"cwes":[{"id":"CWE-798","name":"Use of Hard-coded Credentials"}],"description":"An issue was discovered in the Ascensia Contour NEXT ONE application for Android before 2019-01-15. It has a statically coded encryption key. Extraction of the encryption key is necessary for deciphering communications between this application and the backend server. This, in combination with retrieving any user's encrypted data from the Ascensia cloud through another vulnerability, allows an attacker to obtain and modify any patient's medical information.","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":"Hardcoded credentials in n/a","id":"CVE-2018-18978","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"hardcoded_credentials","year":"2018"},"n_packages":0,"n_references":1,"next":{"headline":"Hardcoded credentials in n/a","id":"CVE-2018-18979"},"packages":[],"prev":{"headline":"Information disclosure in n/a","id":"CVE-2018-18977"},"products":["n/a"],"published":"2019-05-06","related":[{"cvss_score":7.5,"headline":"Weak cryptography in n/a","id":"CVE-2018-18975","kev_date_added":null,"published":"2019-05-06"},{"cvss_score":7.5,"headline":"Information disclosure in n/a","id":"CVE-2018-18977","kev_date_added":null,"published":"2019-05-06"},{"cvss_score":7.4,"headline":"Hardcoded credentials in n/a","id":"CVE-2018-18979","kev_date_added":null,"published":"2019-05-06"},{"cvss_score":5.3,"headline":"Missing authorization in n/a","id":"CVE-2018-18976","kev_date_added":null,"published":"2019-05-06"}],"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":["n/a"]},"summary":"Attackers can extract a static encryption key to decrypt and modify patient medical data exchanged with the backend server.","url":"https://insights.sbomify.com/CVE-2018-18978/"}