CVE-2017-13094
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe 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 the encryption key and insertion of hardware trojans in any IP. 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceIEEE P1735 standard for encrypting electronic design IP contains cryptographic flaws that allow attackers to recover plaintext IP without the encryption key. The vulnerabilities enable modification of encryption keys and potential insertion of hardware trojans in IP cores.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE dataall versionsCVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify IEEE P1735 usage in the environmentSearch for documentation, configuration files, or tool settings that reference 'IEEE P1735' or 'P1735' encryption for IP protectionAffected if IEEE P1735 encryption is implemented or referenced in any EDA tool, IP package, or design flow
-
Locate encrypted IP core filesSearch project directories for encrypted IP files such as .dcp (design checkpoint), .xci (IP core), .ngc, or vendor-specific encrypted HDL files that may use P1735 encryptionAffected if Encrypted IP core files exist that were created using IEEE P1735 encryption methods
-
Review IP procurement recordsCheck IP vendor licenses, purchase orders, or design documentation for mentions of IP encryption standards applied to acquired coresAffected if Acquired IP cores were delivered with IEEE P1735-based encryption protection
-
Inspect EDA tool encryption settingsExamine EDA tool preferences, project settings, or IP packaging options for encryption algorithm selections - look for settings related to 'P1735', 'IEEE 1735', or 'IP encryption'Affected if EDA tools are configured to use IEEE P1735 for encrypting or protecting IP cores
-
Audit IP distribution workflowsReview internal processes for distributing design IP to third parties; identify if IEEE P1735 is the encryption method used when sharing protected IPAffected if IEEE P1735 is used as the encryption mechanism when sharing or distributing IP to external parties
If IEEE P1735 encryption is used anywhere in the design flow for protecting electronic design IP, the environment is affected since all versions of the standard contain the cryptographic flaws described in this CVE.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataReview and audit all implementations of IEEE P1735 encryption for IP protection; consider alternative encryption schemes or updated standards that address these cryptographic weaknesses.
- Consultation16.0 h
- Implementation40.0 h
- Testing24.0 h
- Review / QA12.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $25,856.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-13094 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2017-13094 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data