# CVE-2020-36315: Weak cryptography in n/a

> Attackers can forge RSA signatures if a low public exponent is used, bypassing authentication checks in the RELIC library.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/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:** 7 Apr 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-cc5x-p8hp-xch9

## What is CVE-2020-36315?

CVE-2020-36315 is a medium-severity vulnerability in n/a, published on 7 Apr 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In RELIC before 2020-08-01, RSA PKCS#1 v1.5 signature forgery can occur because certain checks of the padding (and of the first two bytes) are inadequate. NOTE: this requires that a low public exponent (such as 3) is being used. The product, by default, does not generate RSA keys with such a low number.

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

## Which versions are affected by CVE-2020-36315?

It affects 1 product.


Products: Relic Project Relic.

## How do I fix CVE-2020-36315?

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

## Is CVE-2020-36315 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2023-36326](https://insights.sbomify.com/CVE-2023-36326/): Integer overflow in n/a (critical 9.8)
- [CVE-2023-36327](https://insights.sbomify.com/CVE-2023-36327/): Integer overflow in n/a (critical 9.8)
- [CVE-2023-51939](https://insights.sbomify.com/CVE-2023-51939/): Information disclosure in n/a (high 8.8)
- [CVE-2020-36316](https://insights.sbomify.com/CVE-2020-36316/): Memory corruption in n/a (medium 5.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-36315 and fix it if it is affected.

What it is: CVE-2020-36315 is a medium-severity vulnerability in n/a, published on 7 Apr 2021. 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-2020-36315 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-2020-36315/ (Markdown: https://insights.sbomify.com/CVE-2020-36315/index.md)
```

## Sources

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

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