LiveActive security incident?Get immediate response
CVE Record

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

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.

HighCVSS 8.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2023-51939 is a high-severity issue reported in Relic relic-toolkit 0.6.0, in the cp_bbs_sig signing function. The public record says a remote attacker may obtain sensitive information and escalate privileges, but affected-product metadata and remediation details are sparse.

Executive priority

Prioritize investigation if cryptographic services, identity systems, or signing workflows depend on Relic 0.6.0. If Relic is not present or BBS signatures are unused, urgency is lower but should still be documented.

Technical view

The CVE describes an issue in relic/src/cp/relic_cp_bbs.c, function cp_bbs_sig, associated with CWE-74. CVSS 3.1 is 8.8 with network attack vector, low complexity, no privileges, user interaction required, and high confidentiality, integrity, and availability impact.

Likely exposure

Exposure is likely limited to systems that compile or embed Relic relic-toolkit 0.6.0 and use the affected BBS signature functionality. The CVE record does not provide CPEs, downstream package names, or deployment-specific indicators.

Exploitation context

The source bundle includes public GitHub research references and a Relic issue, but KEV is false and no cited source confirms active exploitation. Treat this as a credible public vulnerability, not evidence of ongoing mass exploitation.

Researcher notes

The public record is thin: affected vendor/product fields are n/a despite the description naming Relic relic-toolkit 0.6.0. No patch, fixed version, or active exploitation evidence is provided in the supplied bundle.

Mitigation direction

  • Inventory software using Relic relic-toolkit 0.6.0.
  • Check the Relic issue and vendor guidance for patches or recommended changes.
  • Prioritize systems exposing BBS signature operations to untrusted users or workflows.
  • Reduce untrusted access to affected signing paths until remediation is confirmed.
  • Review sensitive key material handling if exposure is suspected.

Validation and detection

  • Confirm whether Relic relic-toolkit 0.6.0 is present in builds or dependencies.
  • Determine whether cp_bbs_sig or BBS signature functionality is used.
  • Map whether remote or untrusted input can reach the affected function.
  • Review vendor issue status before declaring remediation complete.
  • Document uncertainty where product metadata or fixed versions are unavailable.
Prepared
Confidence
medium
Sources
5

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-74: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2023-51939 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
8.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
4Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
8.8CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H2.85.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

8.8High
CVSS 3.1 vector shape for CVE-2023-51939Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-74 · source CWE mapping

Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection')

Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.