CVE-2023-51939: An issue in the cp_bbs_sig function in relic/src/cp/relic_cp_bbs.c of Relic relic-toolkit 0.6.0 allows a remot

This month

HIGH 8.8DOWNGRADE

CVE-2023-51939 is a high-severity flaw (CVSS 8.8) affecting relic. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

An issue in the cp_bbs_sig function in relic/src/cp/relic_cp_bbs.c of Relic relic-toolkit 0.6.0 allows a remote attacker to obtain sensitive information and escalate privileges via the cp_bbs_sig function.

Why this priority

High severity
Public exploit reference

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score	8.8 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	Required
EPSS exploit chance	0.9% (top 40%)
CISA exploited list	No
Weakness	CWE-74
Published	2024-02-01
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: relic project

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2024-02-01 07:15 UTCPublished CVE record published
2026-06-17 06:41 UTCUpdated Record last modified

relic project relic DOWNGRADE

Affected: 0.6.0

Fixed in: no fixed release known

Safe to downgrade to: a release before 0.6.0

1. Check installed version

apt-cache policy relic || rpm -q relic || relic --version

2. No fixed release: DOWNGRADE to a release before 0.6.0 (Debian / Ubuntu)

apt-cache madison relic sudo apt install relic=<VERSION_BEFORE_0.6.0> sudo apt-mark hold relic

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list relic sudo dnf downgrade relic-<VERSION_BEFORE_0.6.0> sudo dnf versionlock add relic

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2023-51939?

relic: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2023-51939 being exploited?

CVE-2023-51939 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2023-51939 affect?

CVE-2023-51939 affects relic. Severity is high (CVSS 8.8). An issue in the cp_bbs_sig function in relic/src/cp/relic_cp_bbs.c of Relic relic-toolkit 0.6.0 allows a remote attacker to obtain sensitive information and escalate privileges via the cp_bbs_sig function.

How urgent is CVE-2023-51939?

Priority 51/100. High severity; Public exploit reference

Related CVEs

CVE-2023-36327 CRITICAL 9.8 UPGRADE Integer Overflow vulnerability in RELIC before commit 421f2e91cf2ba42473d4d54daf24e295679e290e, allows attacke
CVE-2023-36326 CRITICAL 9.8 UPGRADE Integer Overflow vulnerability in RELIC before commit 34580d840469361ba9b5f001361cad659687b9ab, allows attacke

References

← Back to latest CVEs