dbcve.org
Tss LibApplication · Iofinnet

CVE-2022-47930

MEDIUM · 6.8 CVSS v3.1 Published 2023-04-21
Fix available
A fix is available. Upgrade to 2.0.0 or later.
See remediation →
74/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
An issue was discovered in IO FinNet tss-lib before 2.0.0. The parameter ssid for defining a session id is not used through the MPC implementation, which makes replaying and spoofing of messages easier. In particular, the Schnorr proof of knowledge implemented in sch.go does not utilize a session id, context, or random nonce in the generation of the challenge. This could allow a malicious user or an eavesdropper to replay a valid proof sent in the past.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The tss-lib library's Schnorr proof implementation in sch.go fails to incorporate the session ID (ssid), context, or a random nonce into the challenge generation. This allows an attacker to capture and replay previously valid proofs, enabling message spoofing and replay attacks against the MPC protocol.

MitigationUpgrade tss-lib to version 2.0.0 or later where session binding is properly implemented in the Schnorr proof generation.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Tss LibApplication
Affected:< 2.0.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
High
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify tss-lib version
    Inspect your go.mod file or run 'go list -m all | grep tss-lib' to determine the installed version of the Iofinnet tss-lib library
    Affected if The version is any release prior to 2.0.0
  2. Locate Schnorr proof source
    Find the sch.go file in your tss-lib dependency - typically in the directory path containing 'tss' and 'schnorr' or similar
    Affected if The sch.go file exists in your codebase and is being used by your application
  3. Examine challenge generation in sch.go
    Open sch.go and inspect the function that generates the Schnorr challenge (often named something like 'Challenge' or 'NewProof'). Look for variables related to session ID (ssid), context, or nonce in the challenge computation
    Affected if The challenge generation function does not incorporate ssid, context, or a random nonce into its computation - the proof relies only on static values
  4. Check for replay vulnerability
    Determine whether your application accepts Schnorr proofs from tss-lib without storing or validating a unique session identifier or timestamp associated with each proof
    Affected if Your MPC protocol accepts proofs without binding them to a unique session identifier that would prevent replay of a previously captured valid proof
  5. Verify MPC protocol usage
    Identify if your system uses the tss-lib for multi-party computation operations that rely on Schnorr proofs for authentication or message signing
    Affected if Your system uses tss-lib for MPC operations where the Schnorr proof output is accepted from other parties without replay protection

Your environment is affected if you are using any version of Iofinnet tss-lib prior to 2.0.0 and your application relies on the Schnorr proof implementation in sch.go for authentication or message verification.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.0.0 or later
Fixed in 2.0.0
Interim mitigation

Upgrade tss-lib to version 2.0.0 or later where session binding is properly implemented in the Schnorr proof generation.

Recommended fix High confidence

2.0.0

  1. 1. Identify all projects and dependencies that use tss-lib version earlier than 2.0.0
  2. 2. Update the dependency version to 2.0.0 or later in your project's dependency management system (e.g., go.mod for Go projects)
  3. 3. Run dependency resolution to fetch the new version (e.g., 'go mod tidy' or 'go get')
  4. 4. Rebuild and test the application to ensure compatibility with the updated library
  5. 5. Verify the fix is applied by confirming the Schnorr proof implementation now uses session ID, context, or random nonce in challenge generation
Caveat Review the tss-lib 2.0.0 release notes for any API changes or breaking changes in MPC protocol implementations before upgrading production systems

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Tss Lib Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,820
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,512.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-47930 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-47930 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data