GHSA-7f6p-phw2-8253: Github.com/taurusgroup/multi party sig Taurus Multi-party-sig Has OT-based ECDSA Vulnerability

HIGH
Published
Advisory Summary

GHSA-7f6p-phw2-8253 is a HIGH taurus multi-party-sig has ot-based ecdsa vulnerability (General Security Weakness) affecting Github.com/taurusgroup/multi party sig libraries in the Go ecosystem. The issue involves taurus multi-party-sig has ot-based ecdsa protocol implementation flaws. Remediation is available by upgrading affected packages to version 0.7.0-alpha-2025-01-28.

GHSA-7f6p-phw2-8253 at a Glance

CVE Identifier N/A
GHSA Identifier GHSA-7f6p-phw2-8253
Severity HIGH
CVSS v3.1 Base Score N/A
CWE Classification General Security Weakness
Affected Product Github.com/taurusgroup/multi party sig
Package Ecosystem Go
Published Date
Last Updated

How to Fix GHSA-7f6p-phw2-8253

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

github.com/taurusgroup/multi-party-sig fixed: 0.7.0-alpha-2025-01-28
Upgrade github.com/taurusgroup/multi-party-sig to 0.7.0-alpha-2025-01-28
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 github.com/taurusgroup/multi-party-sig

How to Check if You Are Affected

To determine whether your application is affected by GHSA-7f6p-phw2-8253, inspect your project dependencies for Github.com/taurusgroup/multi party sig:

inspect dependencies for github.com/taurusgroup/multi-party-sig

Analyze the terminal output to locate any version of Github.com/taurusgroup/multi party sig in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 0.7.0-alpha-2025-01-28), 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 General Security Weakness. In Github.com/taurusgroup/multi party sig, 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

Coinbase researchers reported 2 security issues in our implementation of the oblivious transfer (OT) based protocol [DKLS](https://eprint.iacr.org/2018/499.pdf): ### 1. Secret share recovery attack If the base OT setup of the protocol is reused for another execution of the OT extension, then a malicious participant can extract a bit of the secret of another participant. By repeating the execution they can eventually recover the whole secret. Therefore, unlike our comments suggested, you **must not reuse an OT setup** for multiple protocol executions. We're adding a warning in the code: https://github.com/taurushq-io/multi-party-sig/blob/9e4400fccee89be6195d0a12dd0ed052288d5040/internal/ot/extended.go#L114 ### 2. Invalid security proof due to incorrect operator The original 2018 version of the DKLS had a typo in the OT extension protocol when computing the check value in the OT extension: the paper noted a XOR whereas it should be a field multiplication. This erroneous behavior was implemented [in our code](https://github.com/taurushq-io/multi-party-sig/blob/4d84aafb57b437da1b933db9a265fb7ce4e7c138/internal/ot/extended.go#L188). The proof of security fails in this case. No concrete attack is known, however. The [2023 update](https://eprint.iacr.org/2018/499.pdf) of the DKLS paper reported that typo and updated the protocol definition. ~As of 20241124, patching is in progress (branch [otfix](https://github.com/taurushq-io/multi-party-sig/tree/otfix)), but not merged to the main branch yes as the tests fail to pass. We're troubleshooting the issue and will merge into the main branch when it's resolved.~ As of 20250128, a patched version is available in https://github.com/taurushq-io/multi-party-sig/releases/tag/v0.7.0-alpha-2025-01-28, thanks to https://github.com/taurushq-io/multi-party-sig/pull/119. ### Workarounds Do not reuse an OT setup in the event that an abort is detected, to eliminate the secret recovery attack. ### Credits Thanks to the Coinbase researchers Yi-Hsiu Chen and Samuel Ranellucci for discovering these issues and providing a comprehensive write-up. Thank you to Yehuda Lindell for coordinating the disclosure. Thanks to Jay Prakash for clarifying the risk of the base setup reuse. Thanks to @cronokirby for writing the corrected code.

GHSA-7f6p-phw2-8253 Affected Github.com/taurusgroup/multi party sig Versions

1 component(s)
Fixed Versions:
0.7.0-alpha-2025-01-28
Product / Package Ecosystem Affected Versions Fixed Version
github.com/taurusgroup/multi-party-sig
Go
< 0.7.0-alpha-2025-01-28
0.7.0-alpha-2025-01-28

References

Frequently Asked Questions

What is GHSA-7f6p-phw2-8253?
GHSA-7f6p-phw2-8253 is a security vulnerability in Github.com/taurusgroup/multi party sig involving Taurus multi-party-sig has OT-based ECDSA protocol implementation flaws under General Security Weakness.
Which Github.com/taurusgroup/multi party sig versions are affected?
Affected versions include releases prior to 0.7.0-alpha-2025-01-28 across affected packages: github.com/taurusgroup/multi-party-sig.
What version fixes GHSA-7f6p-phw2-8253?
Upgrading to 0.7.0-alpha-2025-01-28 (or the latest patched release for your respective branch) resolves the vulnerability.
Is github.com/taurusgroup/multi-party-sig affected?
Yes, github.com/taurusgroup/multi-party-sig is affected in releases prior to 0.7.0-alpha-2025-01-28. Upgrade your dependency to 0.7.0-alpha-2025-01-28 or later.
What CWE is associated with GHSA-7f6p-phw2-8253?
GHSA-7f6p-phw2-8253 is classified under General Security Weakness.
How can I check Go dependencies for GHSA-7f6p-phw2-8253?
Run the dependency tree command: 'inspect dependencies for github.com/taurusgroup/multi-party-sig'. 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-7f6p-phw2-8253",
  "modified" : "2025-01-28T18:06:15Z",
  "published" : "2024-11-25T15:11:11Z",
  "aliases" : [ ],
  "summary" : "Taurus multi-party-sig has OT-based ECDSA protocol implementation flaws",
  "details" : "Coinbase researchers reported 2 security issues in our implementation of the oblivious transfer (OT) based protocol [DKLS](https://eprint.iacr.org/2018/499.pdf):\n\n### 1. Secret share recovery attack\n\nIf the base OT setup of the protocol is reused for another execution of the OT extension, then a malicious participant can extract a bit of the secret of another participant. By repeating the execution they can eventually recover the whole secret.\n\nTherefore, unlike our comments suggested, you **must not reuse an OT setup** for multiple protocol executions. \n\nWe're adding a warning in the code:\n\nhttps://github.com/taurushq-io/multi-party-sig/blob/9e4400fccee89be6195d0a12dd0ed052288d5040/internal/ot/extended.go#L114\n\n### 2. Invalid security proof due to incorrect operator\n\nThe original 2018 version of the DKLS had a typo in the OT extension protocol when computing the check value in the OT extension: the paper noted a XOR whereas it should be a field multiplication. This erroneous behavior was implemented [in our code](https://github.com/taurushq-io/multi-party-sig/blob/4d84aafb57b437da1b933db9a265fb7ce4e7c138/internal/ot/extended.go#L188). \n\nThe proof of security fails in this case. No concrete attack is known, however.\n\nThe [2023 update](https://eprint.iacr.org/2018/499.pdf) of the DKLS paper reported that typo and updated the protocol definition.\n\n~As of 20241124, patching is in progress (branch [otfix](https://github.com/taurushq-io/multi-party-sig/tree/otfix)), but not merged to the main branch yes as the tests fail to pass. We're troubleshooting the issue and will merge into the main branch when it's resolved.~\n\nAs of 20250128, a patched version is available in https://github.com/taurushq-io/multi-party-sig/releases/tag/v0.7.0-alpha-2025-01-28, thanks to https://github.com/taurushq-io/multi-party-sig/pull/119.\n\n### Workarounds\n\nDo not reuse an OT setup in the event that an abort is detected, to eliminate the secret recovery attack.\n  \n\n### Credits\n\nThanks to the Coinbase researchers Yi-Hsiu Chen and Samuel Ranellucci for discovering these issues and providing a comprehensive write-up. Thank you to Yehuda Lindell for coordinating the disclosure.\nThanks to Jay Prakash for clarifying the risk of the base setup reuse.\nThanks to @cronokirby for writing the corrected code.\n\n\n",
  "severity" : [ ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/taurusgroup/multi-party-sig"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "0.7.0-alpha-2025-01-28"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "<= 0.6.0-alpha-2021-09-21"
    }
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/taurushq-io/multi-party-sig/security/advisories/GHSA-7f6p-phw2-8253"
  }, {
    "type" : "WEB",
    "url" : "https://eprint.iacr.org/2018/499.pdf"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/taurushq-io/multi-party-sig"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/taurushq-io/multi-party-sig/blob/4d84aafb57b437da1b933db9a265fb7ce4e7c138/internal/ot/extended.go#L188"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/taurushq-io/multi-party-sig/blob/9e4400fccee89be6195d0a12dd0ed052288d5040/internal/ot/extended.go#L114"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/taurushq-io/multi-party-sig/tree/otfix"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2024-11-25T15:11:11Z",
    "nvd_published_at" : null
  }
}