{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-10606 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2017-10606 yet. Limit exposure of the affected software until one is available.","what":"CVE-2017-10606 is a medium-severity vulnerability in Juniper Networks Junos OS, published on 13 Oct 2017. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2017-10606 and fix it if it is affected.\n\nWhat it is: CVE-2017-10606 is a medium-severity vulnerability in Juniper Networks Junos OS, published on 13 Oct 2017. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2017-10606 in the wild and no public exploit code.\n\nAffected product: Juniper Networks Junos OS. 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-2017-10606/ (Markdown: https://insights.sbomify.com/CVE-2017-10606/index.md)","id":"CVE-2017-10606","markdown":"https://insights.sbomify.com/CVE-2017-10606/index.md","name":"CVE-2017-10606","record":{"aliases":["GHSA-h472-275m-5q88"],"analysis":{"component_type":"network_device","fix_type":"patch","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"SRX300 TPM firmware","requires_auth":"high_privilege","summary":"Weak cryptographic key generation in SRX300 TPM firmware allows attackers to decrypt sensitive configuration data.","user_interaction":"not_required","vuln_class":"weak_cryptography"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"juniper","cpe":[{"product":"trusted_platform_module_firmware","vendor":"juniper"}],"cvss":{"score":4.4,"severity":"medium","source":"cna","vector":"CVSS:3.0/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N","version":"3.0"},"cwes":[],"description":"Version 4.40 of the TPM (Trusted Platform Module) firmware on Juniper Networks SRX300 Series has a weakness in generating cryptographic keys that may allow an attacker to decrypt sensitive information in SRX300 Series products. The TPM is used in the SRX300 Series to encrypt sensitive configuration data. While other products also ship with a TPM, no other products or platforms are affected by this vulnerability. Customers can confirm the version of TPM firmware via the 'show security tpm status' command. This issue was discovered by an external security researcher. No other Juniper Networks products or platforms are affected by this issue.","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":"SRX Series: Cryptographic weakness in SRX300 Series TPM Firmware","id":"CVE-2017-10606","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"weak_cryptography","year":"2017"},"n_packages":0,"n_references":1,"next":{"headline":"Junos: rpd core due to receipt of specially crafted BGP packet","id":"CVE-2017-10607"},"packages":[],"prev":{"headline":"Junos: SRX Series denial of service vulnerability in flowd due to crafted DHCP packet","id":"CVE-2017-10605"},"products":["Junos OS"],"published":"2017-10-13","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":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-09-17","vendors":["Juniper Networks"]},"summary":"Weak cryptographic key generation in SRX300 TPM firmware allows attackers to decrypt sensitive configuration data.","url":"https://insights.sbomify.com/CVE-2017-10606/"}