{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-15312 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-15312 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-15312 is a high-severity server-side request forgery vulnerability in n/a, published on 1 Jul 2020. 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-2019-15312 and fix it if it is affected.\n\nWhat it is: CVE-2019-15312 is a high-severity server-side request forgery vulnerability in n/a, published on 1 Jul 2020. 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-2019-15312 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-2019-15312/ (Markdown: https://insights.sbomify.com/CVE-2019-15312/index.md)","id":"CVE-2019-15312","markdown":"https://insights.sbomify.com/CVE-2019-15312/index.md","name":"CVE-2019-15312","record":{"aliases":["GHSA-fpfh-736w-3wqw"],"analysis":{"component_type":"iot_embedded","fix_type":"no_fix_stated","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Zolo Halo smart speaker","requires_auth":"none","summary":"Attackers can compromise Zolo Halo devices via DNS rebinding combined with command injection in HTTP API endpoints.","user_interaction":"required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"linkplay","vendor":"linkplay"}],"cvss":{"score":8.8,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[],"description":"An issue was discovered on Zolo Halo devices via the Linkplay firmware. There is a Zolo Halo DNS rebinding attack. The device was found to be vulnerable to DNS rebinding. Combined with one of the many /httpapi.asp endpoint command-execution security issues, the DNS rebinding attack could allow an attacker to compromise the victim device from the Internet.","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":"Server-side request forgery in n/a","id":"CVE-2019-15312","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"ssrf","year":"2019"},"n_packages":0,"n_references":3,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2019-15313"},"packages":[],"prev":{"headline":"Command injection in n/a","id":"CVE-2019-15311"},"products":["n/a"],"published":"2020-07-01","related":[{"cvss_score":9.8,"headline":"Command injection in n/a","id":"CVE-2019-15310","kev_date_added":null,"published":"2020-07-01"},{"cvss_score":9.8,"headline":"Command injection in n/a","id":"CVE-2019-15311","kev_date_added":null,"published":"2020-07-01"}],"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":"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 compromise Zolo Halo devices via DNS rebinding combined with command injection in HTTP API endpoints.","url":"https://insights.sbomify.com/CVE-2019-15312/"}