{"answers":{"affected":"It affects 7 products.","exploited":"There is no known exploitation of CVE-2019-15911 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-15911 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-15911 is a critical vulnerability in n/a, published on 20 Dec 2019. 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-15911 and fix it if it is affected.\n\nWhat it is: CVE-2019-15911 is a critical vulnerability in n/a, published on 20 Dec 2019. 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-15911 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-15911/ (Markdown: https://insights.sbomify.com/CVE-2019-15911/index.md)","id":"CVE-2019-15911","markdown":"https://insights.sbomify.com/CVE-2019-15911/index.md","name":"CVE-2019-15911","record":{"aliases":["GHSA-w2ph-248f-gj8m"],"analysis":{"component_type":"iot_embedded","fix_type":"no_fix_stated","impacts":["data_read","denial_of_service","account_takeover","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"ZigBee smart home devices","requires_auth":"none","summary":"Insecure key transport in ZigBee devices allows attackers to steal data, cause denial of service, take over devices, and tamper with messages.","user_interaction":"not_required","vuln_class":"weak_cryptography"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"as-101_firmware","vendor":"asus"},{"product":"dl-101_firmware","vendor":"asus"},{"product":"hg100_firmware","vendor":"asus"},{"product":"ms-101_firmware","vendor":"asus"},{"product":"mw100_firmware","vendor":"asus"},{"product":"ts-101_firmware","vendor":"asus"},{"product":"ws-101_firmware","vendor":"asus"}],"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-319","name":"Cleartext Transmission of Sensitive Information"}],"description":"An issue was discovered on ASUS HG100, MW100, WS-101, TS-101, AS-101, MS-101, DL-101 devices using ZigBee PRO. Because of insecure key transport in ZigBee communication, attackers can obtain sensitive information, cause the multiple denial of service attacks, take over smart home devices, and tamper with messages.","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":"Weak cryptography in n/a","id":"CVE-2019-15911","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"weak_cryptography","year":"2019"},"n_packages":0,"n_references":1,"next":{"headline":"Denial of service in n/a","id":"CVE-2019-15912"},"packages":[],"prev":{"headline":"Denial of service in n/a","id":"CVE-2019-15910"},"products":["n/a"],"published":"2019-12-20","related":[{"cvss_score":7.5,"headline":"Denial of service in n/a","id":"CVE-2019-15910","kev_date_added":null,"published":"2019-12-20"},{"cvss_score":7.5,"headline":"Denial of service in n/a","id":"CVE-2019-15912","kev_date_added":null,"published":"2019-12-20"}],"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":"Insecure key transport in ZigBee devices allows attackers to steal data, cause denial of service, take over devices, and tamper with messages.","url":"https://insights.sbomify.com/CVE-2019-15911/"}