{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-12257 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-12257 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-12257 is a medium-severity vulnerability in n/a, published on 12 Jun 2018. 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-2018-12257 and fix it if it is affected.\n\nWhat it is: CVE-2018-12257 is a medium-severity vulnerability in n/a, published on 12 Jun 2018. 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-2018-12257 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-12257/ (Markdown: https://insights.sbomify.com/CVE-2018-12257/index.md)","id":"CVE-2018-12257","markdown":"https://insights.sbomify.com/CVE-2018-12257/index.md","name":"CVE-2018-12257","record":{"aliases":["GHSA-6222-ghhf-xmx8"],"analysis":{"component_type":"iot_embedded","fix_type":"no_fix_stated","impacts":["code_execution","privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Momentum Axel 720P","requires_auth":"high_privilege","summary":"Authenticated root users can bypass SSL validation to install malicious firmware via DNS hijacking, leading to remote code execution.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"momentum_axel_720p_firmware","vendor":"apollotechnologiesinc"}],"cvss":{"score":4.4,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:N","version":"3.0"},"cwes":[{"id":"CWE-295","name":"Improper Certificate Validation"}],"description":"An issue was discovered on Momentum Axel 720P 5.1.8 devices. There is Authenticated Custom Firmware Upgrade via DNS Hijacking. An authenticated root user with CLI access is able to remotely upgrade firmware to a custom image due to lack of SSL validation by changing the nameservers in /etc/resolv.conf to the attacker's server, and serving the expected HTTPS response containing new firmware for the device to download.","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":"Security feature bypass in n/a","id":"CVE-2018-12257","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2018"},"n_packages":0,"n_references":1,"next":{"headline":"Other in n/a","id":"CVE-2018-12258"},"packages":[],"prev":{"headline":"File upload in n/a","id":"CVE-2018-12256"},"products":["n/a"],"published":"2018-06-12","related":[{"cvss_score":6.8,"headline":"Other in n/a","id":"CVE-2018-12258","kev_date_added":null,"published":"2018-06-12"},{"cvss_score":6.8,"headline":"Auth bypass in n/a","id":"CVE-2018-12259","kev_date_added":null,"published":"2018-06-12"},{"cvss_score":6.7,"headline":"Hardcoded credentials in n/a","id":"CVE-2018-12260","kev_date_added":null,"published":"2018-06-12"},{"cvss_score":4.4,"headline":"Privilege escalation in n/a","id":"CVE-2018-12261","kev_date_added":null,"published":"2018-06-12"}],"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-09-17","vendors":["n/a"]},"summary":"Authenticated root users can bypass SSL validation to install malicious firmware via DNS hijacking, leading to remote code execution.","url":"https://insights.sbomify.com/CVE-2018-12257/"}