# GHSA-hrjv-pf36-jpmr: Post-Quantum Key Encapsulation Mechanism SIKE broken

> Attackers can recover secret keys from SIKE/SIDH implementations, compromising encrypted data confidentiality.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 30 Jul 2022
- **Also known as:** RUSTSEC-2022-0045

## What is GHSA-hrjv-pf36-jpmr?

GHSA-hrjv-pf36-jpmr is a vulnerability in oqs, published on 30 Jul 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Wouter Castryck and Thomas Decru presented an efficient key recovery attack on the SIDH protocol.
As a result, the secret key of SIKEp751 can be recovered in a matter of hours.
The SIKE and SIDH schemes will be removed from oqs 0.7.2.

The affected schemes are the `oqs::kem::Algorithm::Sike*` and `oqs::kem::Algorithm::Sidh*` enum variants.

[An efficient key recovery attack on SIDH (preliminary version)](https://eprint.iacr.org/2022/975)

## Which versions are affected by GHSA-hrjv-pf36-jpmr?

3 open source packages ship an affected version, including oqs.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `oqs` | crates.io | All versions | 0.7.2 |
| `oqs` | crates.io | All versions | 0.7.2 |
| `oqs` | crates.io | From 0.0.0-0 | 0.7.2 |

## How do I fix GHSA-hrjv-pf36-jpmr?

Upgrade oqs to 0.7.2 or later.

## Is GHSA-hrjv-pf36-jpmr being exploited?

There is no known exploitation of GHSA-hrjv-pf36-jpmr in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-hrjv-pf36-jpmr and fix it if it is affected.

What it is: GHSA-hrjv-pf36-jpmr is a vulnerability in oqs, published on 30 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 GHSA-hrjv-pf36-jpmr in the wild and no public exploit code.

Affected packages and fixed versions:
- oqs (crates.io): affected all versions; fixed in 0.7.2
- oqs (crates.io): affected all versions; fixed in 0.7.2
- oqs (crates.io): affected from 0.0.0-0; fixed in 0.7.2

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/GHSA-hrjv-pf36-jpmr/ (Markdown: https://insights.sbomify.com/GHSA-hrjv-pf36-jpmr/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-hrjv-pf36-jpmr

---
From sbomify Insights: https://insights.sbomify.com/GHSA-hrjv-pf36-jpmr/
Summaries are generated and may contain mistakes; the official description above is the record.