LiveActive security incident?Get immediate response
CVE Record

CVE-2017-13092: The P1735 IEEE standard describes flawed methods for encrypting electronic-design intellectual property (IP), including improperly specified HDL syntax allows use of an EDA tool as a decryption oracle

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysis

Security readout for executives and security teams

IEEE P1735 was intended to protect electronic design intellectual property, but the cited vulnerability describes flaws that can let protected HDL IP be recovered without the key. The business risk is loss of confidential chip or design IP where P1735-encrypted packages and affected EDA tools are used. Exposure is likely limited to organizations that create, receive, license, or evaluate encrypted electronic-design IP using IEEE P1735 workflows or compatible EDA tools. The bundle identifies IEEE P1735 as affected, but does not enumerate specific vendor implementations or versions. Prioritize assessment if semiconductor, FPGA, ASIC, or EDA-dependent work is material to the business. The main impact is intellectual property loss, not service disruption. Urgency depends on whether P1735-protected design IP is used or shared externally. Mitigation focus: Inventory P1735-encrypted IP and EDA tools in design workflows.; Check EDA vendor guidance linked from CERT VU#739007 before assuming a fix.; Apply vendor-recommended updates or workflow changes where available..

Prepared

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-310: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2017-13092 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
IEEEStandardP1735Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-310 · source CWE mapping

Cryptographic Issues

Cryptographic Issues represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.