{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2024-57174 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-57174 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-57174 is a high-severity vulnerability in n/a, published on 5 Mar 2025. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-57174 and fix it if it is affected.\n\nWhat it is: CVE-2024-57174 is a high-severity vulnerability in n/a, published on 5 Mar 2025. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2024-57174 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-2024-57174/ (Markdown: https://insights.sbomify.com/CVE-2024-57174/index.md)","id":"CVE-2024-57174","markdown":"https://insights.sbomify.com/CVE-2024-57174/index.md","name":"CVE-2024-57174","record":{"aliases":["GHSA-mfqx-wfm8-g2h8"],"analysis":{"component_type":"network_device","fix_type":"configuration_change","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"ASEE-1443 firmware","requires_auth":"low_privilege","summary":"Attackers can register an unclaimed default DNS suffix to intercept traffic and access sensitive information on Alphion ASEE-1443 devices.","user_interaction":"not_required","vuln_class":"misconfiguration"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[],"cvss":{"score":8.1,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[],"description":"A misconfiguration in Alphion ASEE-1443 Firmware v0.4.H.00.02.15 defines a previously unregistered domain name as the default DNS suffix. This allows attackers to register the unclaimed domain and point its wildcard DNS entry to an attacker-controlled IP address, making it possible to access sensitive 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":"Misconfiguration in n/a","id":"CVE-2024-57174","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"misconfiguration","year":"2024"},"n_packages":0,"n_references":2,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2024-57175"},"packages":[],"prev":{"headline":"Path traversal in n/a","id":"CVE-2024-57170"},"products":["n/a"],"published":"2025-03-05","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-03-06","vendors":["n/a"]},"summary":"Attackers can register an unclaimed default DNS suffix to intercept traffic and access sensitive information on Alphion ASEE-1443 devices.","url":"https://insights.sbomify.com/CVE-2024-57174/"}