LiveActive security incident?Get immediate response
CVE Record

CVE-2017-13097: The P1735 IEEE standard describes flawed methods for encrypting electronic-design intellectual property (IP), including modification of Rights Block to remove or relax license requirement

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 modification of Rights Block to remove or relax license requirement. 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

CVE-2017-13097 concerns weaknesses in the IEEE P1735 approach for protecting electronic-design intellectual property. In affected implementations, encrypted design IP may not reliably protect ownership or licensing rules, and severe cases may expose the underlying plaintext design. The business risk is IP theft, unauthorized use, and weakened licensing controls. Exposure is most likely in semiconductor, EDA, FPGA, ASIC, or IP-vendor workflows that rely on IEEE P1735-encrypted design IP. Risk depends on the specific implementation, toolchain, and how encrypted IP is exchanged or trusted. Prioritize review if the organization creates, licenses, shares, or consumes valuable electronic-design IP. The key concern is loss of confidentiality and license control, not ordinary server compromise. Treat urgency as high where P1735-protected IP underpins revenue or strategic designs. Mitigation focus: Inventory where IEEE P1735-encrypted IP is used or accepted.; Check EDA tool and IP vendor guidance for CVE-2017-13097 or VU#739007.; Do not treat P1735 encryption alone as sufficient IP protection..

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-13097 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.