{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-13092 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2017-13092 yet. Limit exposure of the affected software until one is available.","what":"CVE-2017-13092 is a high-severity vulnerability in IEEE Standard, published on 13 Jul 2018. 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-13092 and fix it if it is affected.\n\nWhat it is: CVE-2017-13092 is a high-severity vulnerability in IEEE Standard, published on 13 Jul 2018. 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-13092 in the wild and no public exploit code.\n\nAffected product: IEEE Standard. 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-13092/ (Markdown: https://insights.sbomify.com/CVE-2017-13092/index.md)","id":"CVE-2017-13092","markdown":"https://insights.sbomify.com/CVE-2017-13092/index.md","name":"CVE-2017-13092","record":{"aliases":["GHSA-2j47-qm67-hvhx"],"analysis":{"component_type":"other","fix_type":"no_fix_stated","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"IEEE P1735 standard","requires_auth":"low_privilege","summary":"Flawed encryption methods in the IEEE P1735 standard allow attackers to recover plaintext intellectual property without the key.","user_interaction":"not_required","vuln_class":"weak_cryptography"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"certcc","cpe":[{"product":"-","vendor":"-"}],"cvss":{"score":7.8,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-310","name":null}],"description":"The P1735 IEEE standard describes flawed methods for encrypting electronic-design intellectual property (IP), as well as the management of access rights for such IP, including improperly specified HDL syntax allows use of an EDA tool as a decryption oracle. The methods are flawed and, in the most egregious cases, enable attack vectors that allow recovery of the entire underlying plaintext IP. Implementations of IEEE P1735 may be weak to cryptographic attacks that allow an attacker to obtain plaintext intellectual property without the key, among other impacts.","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 Standard","id":"CVE-2017-13092","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"weak_cryptography","year":"2017"},"n_packages":0,"n_references":2,"next":{"headline":"Weak cryptography in Standard","id":"CVE-2017-13093"},"packages":[],"prev":{"headline":"Weak cryptography in Standard","id":"CVE-2017-13091"},"products":["Standard"],"published":"2018-07-13","related":[{"cvss_score":7.8,"headline":"Weak cryptography in Standard","id":"CVE-2017-13091","kev_date_added":null,"published":"2018-07-13"},{"cvss_score":7.8,"headline":"Weak cryptography in Standard","id":"CVE-2017-13093","kev_date_added":null,"published":"2018-07-13"},{"cvss_score":7.8,"headline":"Weak cryptography in Standard","id":"CVE-2017-13094","kev_date_added":null,"published":"2018-07-13"},{"cvss_score":7.8,"headline":"Weak cryptography in Standard","id":"CVE-2017-13095","kev_date_added":null,"published":"2018-07-13"},{"cvss_score":7.8,"headline":"Weak cryptography in Standard","id":"CVE-2017-13096","kev_date_added":null,"published":"2018-07-13"},{"cvss_score":7.8,"headline":"Weak cryptography in Standard","id":"CVE-2017-13097","kev_date_added":null,"published":"2018-07-13"}],"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":["IEEE"]},"summary":"Flawed encryption methods in the IEEE P1735 standard allow attackers to recover plaintext intellectual property without the key.","url":"https://insights.sbomify.com/CVE-2017-13092/"}