{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-7298 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-7298 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-7298 is a high-severity vulnerability in n/a, published on 22 Feb 2018. 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-7298 and fix it if it is affected.\n\nWhat it is: CVE-2018-7298 is a high-severity vulnerability in n/a, published on 22 Feb 2018. 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-7298 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-7298/ (Markdown: https://insights.sbomify.com/CVE-2018-7298/index.md)","id":"CVE-2018-7298","markdown":"https://insights.sbomify.com/CVE-2018-7298/index.md","name":"CVE-2018-7298","record":{"aliases":["GHSA-xv6q-9vrg-6p5g"],"analysis":{"component_type":"iot_embedded","fix_type":"no_fix_stated","impacts":["code_execution","privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"HomeMatic CCU2","requires_auth":"none","summary":"Attackers can inject malicious firmware via unencrypted HTTP updates, leading to full system compromise of HomeMatic CCU2 devices.","user_interaction":"not_required","vuln_class":"supply_chain"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"homematic_central_control_unit_ccu2_firmware","vendor":"eq-3"}],"cvss":{"score":8.1,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-319","name":"Cleartext Transmission of Sensitive Information"}],"description":"In /usr/local/etc/config/addons/mh/loopupd.sh on eQ-3 AG HomeMatic CCU2 2.29.22 devices, software update packages are downloaded via the HTTP protocol, which does not provide any cryptographic protection of the downloaded contents. An attacker with a privileged network position (which could be obtained via DNS spoofing of www.meine-homematic.de or other approaches) can exploit this issue in order to provide arbitrary malicious firmware updates to the CCU2. This can result in a full system compromise.","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":"Supply chain in n/a","id":"CVE-2018-7298","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"supply_chain","year":"2018"},"n_packages":0,"n_references":1,"next":{"headline":"File upload in n/a","id":"CVE-2018-7299"},"packages":[],"prev":{"headline":"Command injection in n/a","id":"CVE-2018-7297"},"products":["n/a"],"published":"2018-02-22","related":[{"cvss_score":9.8,"headline":"Command injection in n/a","id":"CVE-2018-7297","kev_date_added":null,"published":"2018-02-22"},{"cvss_score":9.8,"headline":"Missing authorization in n/a","id":"CVE-2018-7301","kev_date_added":null,"published":"2018-02-22"},{"cvss_score":8,"headline":"File upload in n/a","id":"CVE-2018-7299","kev_date_added":null,"published":"2018-02-22"},{"cvss_score":5.3,"headline":"Path traversal in n/a","id":"CVE-2018-7296","kev_date_added":null,"published":"2018-02-22"}],"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 inject malicious firmware via unencrypted HTTP updates, leading to full system compromise of HomeMatic CCU2 devices.","url":"https://insights.sbomify.com/CVE-2018-7298/"}