{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-5035 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-5035 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-5035 is a critical vulnerability in Nest Labs, published on 20 Aug 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-5035 and fix it if it is affected.\n\nWhat it is: CVE-2019-5035 is a critical vulnerability in Nest Labs, published on 20 Aug 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-5035 in the wild and no public exploit code.\n\nAffected product: Nest Labs. 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-5035/ (Markdown: https://insights.sbomify.com/CVE-2019-5035/index.md)","id":"CVE-2019-5035","markdown":"https://insights.sbomify.com/CVE-2019-5035/index.md","name":"CVE-2019-5035","record":{"aliases":["GHSA-r4rh-rgr8-5wjr"],"analysis":{"component_type":"iot_embedded","fix_type":"no_fix_stated","impacts":["data_read","privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"Nest Cam IQ Indoor","requires_auth":"none","summary":"Attackers can brute force pairing codes via crafted packets to gain unauthorized access and potentially full control of the device.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"talos","cpe":[{"product":"nest_cam_iq_indoor_firmware","vendor":"google"}],"cvss":{"score":9,"severity":"critical","source":"cna","vector":"CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-327","name":"Use of a Broken or Risky Cryptographic Algorithm"},{"id":"CWE-307","name":"Improper Restriction of Excessive Authentication Attempts"}],"description":"An exploitable information disclosure vulnerability exists in the Weave PASE pairing functionality of the Nest Cam IQ Indoor, version 4620002. A set of specially crafted weave packets can brute force a pairing code, resulting in greater Weave access and potentially full device control. An attacker can send specially crafted packets to trigger this vulnerability.","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":"Information disclosure in Nest Labs","id":"CVE-2019-5035","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2019"},"n_packages":0,"n_references":1,"next":{"headline":"Denial of service in Nest Labs","id":"CVE-2019-5036"},"packages":[],"prev":{"headline":"Information disclosure in Nest Labs","id":"CVE-2019-5034"},"products":["Nest Labs"],"published":"2019-08-20","related":[{"cvss_score":8.2,"headline":"Integer overflow in Nest Labs","id":"CVE-2019-5040","kev_date_added":null,"published":"2019-08-20"},{"cvss_score":7.5,"headline":"Denial of service in Nest Labs","id":"CVE-2019-5036","kev_date_added":null,"published":"2019-08-20"},{"cvss_score":7.5,"headline":"Integer overflow in Nest Labs","id":"CVE-2019-5037","kev_date_added":null,"published":"2019-08-20"},{"cvss_score":5.3,"headline":"Denial of service in Nest Labs","id":"CVE-2019-5043","kev_date_added":null,"published":"2019-10-31"},{"cvss_score":5.3,"headline":"Information disclosure in Nest Labs","id":"CVE-2019-5034","kev_date_added":null,"published":"2019-08-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-04","vendors":["n/a"]},"summary":"Attackers can brute force pairing codes via crafted packets to gain unauthorized access and potentially full control of the device.","url":"https://insights.sbomify.com/CVE-2019-5035/"}