{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-19495 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-19495 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-19495 is a critical vulnerability in n/a, published on 8 Jan 2020. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2019-19495 and fix it if it is affected.\n\nWhat it is: CVE-2019-19495 is a critical vulnerability in n/a, published on 8 Jan 2020. 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-2019-19495 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-19495/ (Markdown: https://insights.sbomify.com/CVE-2019-19495/index.md)","id":"CVE-2019-19495","markdown":"https://insights.sbomify.com/CVE-2019-19495/index.md","name":"CVE-2019-19495","record":{"aliases":["GHSA-h625-6744-fm5g"],"analysis":{"component_type":"network_device","fix_type":"no_fix_stated","impacts":["code_execution","privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"Cable modem","requires_auth":"none","summary":"Remote attackers can use DNS rebinding to configure the modem and expose its root shell, leading to full device compromise.","user_interaction":"not_required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"tc7230_steb_firmware","vendor":"technicolor"}],"cvss":{"score":9.8,"severity":"critical","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-20","name":"Improper Input Validation"}],"description":"The web interface on the Technicolor TC7230 STEB 01.25 is vulnerable to DNS rebinding, which allows a remote attacker to configure the cable modem via JavaScript in a victim's browser. The attacker can then configure the cable modem to port forward the modem's internal TELNET server, allowing external access to a root shell.","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":"Other in n/a","id":"CVE-2019-19495","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"other","year":"2019"},"n_packages":0,"n_references":3,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2019-19496"},"packages":[],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2019-19494"},"products":["n/a"],"published":"2020-01-08","related":[],"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":"Remote attackers can use DNS rebinding to configure the modem and expose its root shell, leading to full device compromise.","url":"https://insights.sbomify.com/CVE-2019-19495/"}