# CVE-2017-13092: Weak cryptography in Standard

> Flawed encryption methods in the IEEE P1735 standard allow attackers to recover plaintext intellectual property without the key.

- **Severity:** High 7.8 (`CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Jul 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-2j47-qm67-hvhx

## What is CVE-2017-13092?

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.

### Official 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.

Weakness: CWE-310

## Which versions are affected by CVE-2017-13092?

It affects 1 product.


Products: - -.

## How do I fix CVE-2017-13092?

No fix has been published for CVE-2017-13092 yet. Limit exposure of the affected software until one is available.

## Is CVE-2017-13092 being exploited?

There is no known exploitation of CVE-2017-13092 in the wild and no public exploit code.

## Other vulnerabilities in IEEE Standard

- [CVE-2017-13091](https://insights.sbomify.com/CVE-2017-13091/): Weak cryptography in Standard (high 7.8)
- [CVE-2017-13093](https://insights.sbomify.com/CVE-2017-13093/): Weak cryptography in Standard (high 7.8)
- [CVE-2017-13094](https://insights.sbomify.com/CVE-2017-13094/): Weak cryptography in Standard (high 7.8)
- [CVE-2017-13095](https://insights.sbomify.com/CVE-2017-13095/): Weak cryptography in Standard (high 7.8)
- [CVE-2017-13096](https://insights.sbomify.com/CVE-2017-13096/): Weak cryptography in Standard (high 7.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-13092 and fix it if it is affected.

What 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.
Exploitation: There is no known exploitation of CVE-2017-13092 in the wild and no public exploit code.

Affected product: IEEE Standard. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2017-13092/ (Markdown: https://insights.sbomify.com/CVE-2017-13092/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2017-13092
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2017-13092
- OSV: https://osv.dev/vulnerability/CVE-2017-13092

---
From sbomify Insights: https://insights.sbomify.com/CVE-2017-13092/
Summaries are generated and may contain mistakes; the official description above is the record.