GHSA-rm66-9gh4-4gp8: Cggmp21 Cggmp21 Vulnerable To Ambiguous Challenge Vulnerability

LOW
CWE-327
Published
Advisory Summary

GHSA-rm66-9gh4-4gp8 is a LOW cggmp21 vulnerable to ambiguous challenge vulnerability (CWE-327: Use of a Broken or Risky Cryptographic Algorithm) affecting Cggmp21 libraries in the crates.io ecosystem. The issue involves cggmp21 vulnerable to ambiguous challenge derivation. Remediation is available by upgrading affected packages to version 0.4.0.

GHSA-rm66-9gh4-4gp8 at a Glance

CVE Identifier N/A
GHSA Identifier GHSA-rm66-9gh4-4gp8
Severity LOW
CVSS v3.1 Base Score N/A
CWE Classification CWE-327: Use of a Broken or Risky Cryptographic Algorithm
Affected Product Cggmp21
Package Ecosystem crates.io
Published Date
Last Updated

How to Fix GHSA-rm66-9gh4-4gp8

To remediate this vulnerability, upgrade all affected Cggmp21 dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

cggmp21 fixed: 0.4.0
Upgrade cggmp21 to 0.4.0
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for cggmp21

How to Check if You Are Affected

To determine whether your application is affected by GHSA-rm66-9gh4-4gp8, inspect your project dependencies for Cggmp21:

inspect dependencies for cggmp21

Analyze the terminal output to locate any version of Cggmp21 in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 0.4.0), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-327: Use of a Broken or Risky Cryptographic Algorithm, where the product uses a broken or risky cryptographic algorithm or protocol. In Cggmp21, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

Challenge derivation in non-interactive ZK proofs was ambiguous and that could lead to security vulnerability (however, it's unknown if it could be exploited).

GHSA-rm66-9gh4-4gp8 Affected Cggmp21 Versions

1 component(s)
Fixed Versions:
0.4.0
Product / Package Ecosystem Affected Versions Fixed Version
cggmp21
crates.io
< 0.4.0
0.4.0

References

Frequently Asked Questions

What is GHSA-rm66-9gh4-4gp8?
GHSA-rm66-9gh4-4gp8 is a security vulnerability in Cggmp21 involving cggmp21 vulnerable to ambiguous challenge derivation under CWE-327: Use of a Broken or Risky Cryptographic Algorithm.
Which Cggmp21 versions are affected?
Affected versions include releases prior to 0.4.0 across affected packages: cggmp21.
What version fixes GHSA-rm66-9gh4-4gp8?
Upgrading to 0.4.0 (or the latest patched release for your respective branch) resolves the vulnerability.
Is cggmp21 affected?
Yes, cggmp21 is affected in releases prior to 0.4.0. Upgrade your dependency to 0.4.0 or later.
What CWE is associated with GHSA-rm66-9gh4-4gp8?
GHSA-rm66-9gh4-4gp8 is classified under CWE-327: Use of a Broken or Risky Cryptographic Algorithm (The product uses a broken or risky cryptographic algorithm or protocol.).
How can I check crates.io dependencies for GHSA-rm66-9gh4-4gp8?
Run the dependency tree command: 'inspect dependencies for cggmp21'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-rm66-9gh4-4gp8",
  "modified" : "2024-11-12T20:54:58Z",
  "published" : "2024-11-12T20:54:58Z",
  "aliases" : [ ],
  "summary" : "cggmp21 vulnerable to ambiguous challenge derivation",
  "details" : "Challenge derivation in non-interactive ZK proofs was ambiguous and that could lead to security vulnerability (however, it's unknown if it could be exploited).\n",
  "severity" : [ {
    "type" : "CVSS_V4",
    "score" : "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:U"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "crates.io",
      "name" : "cggmp21"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "0.4.0"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/dfns/cggmp21/pull/103"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/LFDT-Lockness/cggmp21"
  }, {
    "type" : "WEB",
    "url" : "https://rustsec.org/advisories/RUSTSEC-2024-0393.html"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-327" ],
    "severity" : "LOW",
    "github_reviewed" : true,
    "github_reviewed_at" : "2024-11-12T20:54:58Z",
    "nvd_published_at" : null
  }
}