# CVE-2022-34632: Weak cryptography in n/a

> Insufficient cryptography in Rocket-Chip allows attackers to bypass security mechanisms, affecting hardware designers and users of this open-source SoC generator.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Jul 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-hg7j-9h3g-36x3

## What is CVE-2022-34632?

CVE-2022-34632 is a critical vulnerability in n/a, published on 18 Jul 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Rocket-Chip commit 4f8114374d8824dfdec03f576a8cd68bebce4e56 was discovered to contain insufficient cryptography via the component /rocket/RocketCore.scala.

Weakness: CWE-327 (Use of a Broken or Risky Cryptographic Algorithm)

## Which versions are affected by CVE-2022-34632?

It affects 1 product.


Products: Linuxfoundation Rocket Chip Generator.

## How do I fix CVE-2022-34632?

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

## Is CVE-2022-34632 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-34632 and fix it if it is affected.

What it is: CVE-2022-34632 is a critical vulnerability in n/a, published on 18 Jul 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-34632 in the wild and no public exploit code.

Affected product: n/a. 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-2022-34632/ (Markdown: https://insights.sbomify.com/CVE-2022-34632/index.md)
```

## Sources

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

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