Slip10Like derivation method instantiated with certain curves may allow attacker to find derivation path which results into very long derivation (possible DoS)

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

not scored

EPSS

No dated EPSS signal available.

As published by the source; long descriptions are shortened.

Impact <!-- What kind of vulnerability is it? Who is impacted? -- Impacted are the only ones who use hdwallet::Slip10Like or slip10 derivation method instantiated with curves other than secp256k1 and secp256r1. hdwallet crate used to provide Slip10Like derivation method, which is also provided in slip-10 crate as a default derivation method. It's based on slip10 method that searches for a valid child key in an infinite loop until it's found. Theoretically, this could be exploited by an attacker by finding a derivation path that would force someone to execute a lot of iterations of this loop to find a valid child key. This attack, however, requires the probability of getting an invalid scalar from random 32 bytes to be high. Slip10 is protected from this attack as it's only defined on secp256k1 and secp256r1 curves, for which such probability is very low: - For secp256k1, probability is $< 2^{-127}$. This means that a loop with 2 or more iterations is vanishingly impossible. - For…

Published by the source

18 Dec 2024, 15:51 UTC

Last modified by the source

18 Dec 2024, 15:51 UTC

Source last checked

26 Oct 2026, 15:38 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-2ff4-xfpr-m32r

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: GHSA-2ff4-xfpr-m32r

Advisory: `Slip10Like` derivation method instantiated with certain curves may allow attacker to find derivation path which results into very long derivation (possible DoS)
IDs: GHSA-2ff4-xfpr-m32r
Record: https://patchnext.com/advisories/ghsa-2ff4-xfpr-m32r (revision 1, source checked 26 Oct 2026, 15:38 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Unrated
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Partial vendor fix; fixed versions by package: hd-wallet 0.6.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- crates.io hd-wallet: affected < 0.6.0; fixed in 0.6.0
- crates.io slip-10: affected <= 0.4.1

## Suggested inspection (read-only)
- crates.io hd-wallet: check the installed version with your package manager.
- crates.io slip-10: check the installed version with your package manager.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on hd-wallet, slip-10.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-2ff4-xfpr-m32r (GitHub-reviewed advisory GHSA-2ff4-xfpr-m32r lists affected ranges: crates.io hd-wallet >=0 =0 <=0.4.1)

Commands are suggestions: review each one before running it.