secp256k1
Rust wrapper library for Pieter Wuille's `libsecp256k1`. Implements ECDSA and BIP 340 signatures for the SECG elliptic curve group secp256k1 and related utilities.
Activity
- Latest release
- 2w ago
- Total releases
- 100
- Cadence
- ~20 days
- Last 12 months
- 5
Reach
- Downloads
- 75.3M
Details
- License
- CC0-1.0
- First release
- May 04, 2015
| Version | Released | |
|---|---|---|
0.33.1
patch
|
0.33.1
patch
Dependencies (11)
+ 3 more
Changelog
Compare changes
|
|
0.33.0
minor
|
0.33.0
minor
Dependencies (11)
+ 3 more
Changelog
Compare changes
|
|
0.32.0-beta.2
unknown
|
0.32.0-beta.2
unknown
Dependencies (11)
+ 3 more
Changelog
Compare changes
|
|
0.32.0-beta.1
unknown
|
0.32.0-beta.1
unknown
Dependencies (11)
+ 3 more
Changelog
Compare changes
|
|
0.32.0-beta.0
unknown
|
0.32.0-beta.0
unknown
Dependencies (11)
+ 3 more
Changelog
Compare changes
|
|
0.31.1
unknown
|
0.31.1
unknown
Dependencies (11)
+ 3 more
Changelog
Compare changes
|
|
0.31.0
unknown
|
0.31.0
unknown
Dependencies (11)
+ 3 more
Changelog
Compare changes
|
|
0.30.0
unknown
|
0.30.0
unknown
Dependencies (11)
+ 3 more
Changelog
Compare changes
|
|
0.29.1
unknown
|
0.29.1
unknown
Dependencies (10)
+ 2 more
Changelog
Compare changes
|
|
0.29.0
unknown
|
0.29.0
unknown
Dependencies (10)
+ 2 more
Changelog
Compare changes
|
|
0.28.2
unknown
|
0.28.2
unknown
Dependencies (10)
+ 2 more
Changelog
Compare changes
|
|
0.28.1
unknown
|
0.28.1
unknown
Dependencies (10)
+ 2 more
Changelog
Compare changes
|
|
0.28.0
unknown
yanked
|
0.28.0
unknown
yanked
Dependencies (10)
+ 2 more
Changelog
Compare changes
|
|
0.27.0
unknown
|
0.27.0
unknown
Dependencies (10)
+ 2 more
Changelog
Compare changes
|
|
0.26.0
unknown
|
0.26.0
unknown
Dependencies (10)
+ 2 more
Changelog
Compare changes
|
|
0.24.3
unknown
|
0.24.3
unknown
Dependencies (12)
+ 4 more
Changelog
Compare changes
|
|
0.25.0
unknown
|
0.25.0
unknown
Dependencies (10)
+ 2 more
Changelog
Compare changes
|
|
0.24.2
unknown
|
0.24.2
unknown
Dependencies (12)
+ 4 more
Changelog
Compare changes
|
|
0.23.5
unknown
|
0.23.5
unknown
Dependencies (12)
+ 4 more
Changelog
Compare changes
|
|
0.22.2
unknown
|
0.22.2
unknown
Dependencies (9)
+ 1 more
Changelog
Compare changes
|
|
0.24.1
unknown
yanked
1 CVE
GHSA-969w-q74q-9j8v
RUSTSEC-2022-0070
Dec 08, 2022
Unsound API in `secp256k1` allows use-after-free and invalid deallocation from safe code
Medium
Because of incorrect bounds on method The method takes a place for storing the context as a mutable reference and returns context containing that reference. Because the code internally uses You are unaffected if you either
The patched version uses correct bounds which means it is API-breaking. This effectively means adopting the policy of Rust lang itself allowing API-breaking changes to fix soundness bugs. Note however that valid straigthforward usage of the code will continue to compile. Only unsound code or code that propagates the bound in custom generics will fail to compile. If the code is sound fixing the bounds should be sufficient to make the code compile. See the GitHub issue for example "exploit" code and further discussion. Fixed in
0.22.2
0.23.5
0.24.2
References Updated Nov 08, 2023 · Source: OSV.dev |
0.24.1
unknown
yanked
Dependencies (12)
+ 4 more
Changelog
Compare changes
|
|
0.24.0
unknown
1 CVE
GHSA-969w-q74q-9j8v
RUSTSEC-2022-0070
Dec 08, 2022
Unsound API in `secp256k1` allows use-after-free and invalid deallocation from safe code
Medium
Because of incorrect bounds on method The method takes a place for storing the context as a mutable reference and returns context containing that reference. Because the code internally uses You are unaffected if you either
The patched version uses correct bounds which means it is API-breaking. This effectively means adopting the policy of Rust lang itself allowing API-breaking changes to fix soundness bugs. Note however that valid straigthforward usage of the code will continue to compile. Only unsound code or code that propagates the bound in custom generics will fail to compile. If the code is sound fixing the bounds should be sufficient to make the code compile. See the GitHub issue for example "exploit" code and further discussion. Fixed in
0.22.2
0.23.5
0.24.2
References Updated Nov 08, 2023 · Source: OSV.dev |
0.24.0
unknown
Dependencies (12)
+ 4 more
Changelog
Compare changes
|
|
0.23.4
unknown
yanked
1 CVE
GHSA-969w-q74q-9j8v
RUSTSEC-2022-0070
Dec 08, 2022
Unsound API in `secp256k1` allows use-after-free and invalid deallocation from safe code
Medium
Because of incorrect bounds on method The method takes a place for storing the context as a mutable reference and returns context containing that reference. Because the code internally uses You are unaffected if you either
The patched version uses correct bounds which means it is API-breaking. This effectively means adopting the policy of Rust lang itself allowing API-breaking changes to fix soundness bugs. Note however that valid straigthforward usage of the code will continue to compile. Only unsound code or code that propagates the bound in custom generics will fail to compile. If the code is sound fixing the bounds should be sufficient to make the code compile. See the GitHub issue for example "exploit" code and further discussion. Fixed in
0.22.2
0.23.5
0.24.2
References Updated Nov 08, 2023 · Source: OSV.dev |
0.23.4
unknown
yanked
Dependencies (12)
+ 4 more
Changelog
Compare changes
|
|
0.23.3
unknown
1 CVE
GHSA-969w-q74q-9j8v
RUSTSEC-2022-0070
Dec 08, 2022
Unsound API in `secp256k1` allows use-after-free and invalid deallocation from safe code
Medium
Because of incorrect bounds on method The method takes a place for storing the context as a mutable reference and returns context containing that reference. Because the code internally uses You are unaffected if you either
The patched version uses correct bounds which means it is API-breaking. This effectively means adopting the policy of Rust lang itself allowing API-breaking changes to fix soundness bugs. Note however that valid straigthforward usage of the code will continue to compile. Only unsound code or code that propagates the bound in custom generics will fail to compile. If the code is sound fixing the bounds should be sufficient to make the code compile. See the GitHub issue for example "exploit" code and further discussion. Fixed in
0.22.2
0.23.5
0.24.2
References Updated Nov 08, 2023 · Source: OSV.dev |
0.23.3
unknown
Dependencies (12)
+ 4 more
Changelog
Compare changes
|
|
0.23.2
unknown
1 CVE
GHSA-969w-q74q-9j8v
RUSTSEC-2022-0070
Dec 08, 2022
Unsound API in `secp256k1` allows use-after-free and invalid deallocation from safe code
Medium
Because of incorrect bounds on method The method takes a place for storing the context as a mutable reference and returns context containing that reference. Because the code internally uses You are unaffected if you either
The patched version uses correct bounds which means it is API-breaking. This effectively means adopting the policy of Rust lang itself allowing API-breaking changes to fix soundness bugs. Note however that valid straigthforward usage of the code will continue to compile. Only unsound code or code that propagates the bound in custom generics will fail to compile. If the code is sound fixing the bounds should be sufficient to make the code compile. See the GitHub issue for example "exploit" code and further discussion. Fixed in
0.22.2
0.23.5
0.24.2
References Updated Nov 08, 2023 · Source: OSV.dev |
0.23.2
unknown
Dependencies (12)
+ 4 more
Changelog
Compare changes
|
|
0.23.1
unknown
1 CVE
GHSA-969w-q74q-9j8v
RUSTSEC-2022-0070
Dec 08, 2022
Unsound API in `secp256k1` allows use-after-free and invalid deallocation from safe code
Medium
Because of incorrect bounds on method The method takes a place for storing the context as a mutable reference and returns context containing that reference. Because the code internally uses You are unaffected if you either
The patched version uses correct bounds which means it is API-breaking. This effectively means adopting the policy of Rust lang itself allowing API-breaking changes to fix soundness bugs. Note however that valid straigthforward usage of the code will continue to compile. Only unsound code or code that propagates the bound in custom generics will fail to compile. If the code is sound fixing the bounds should be sufficient to make the code compile. See the GitHub issue for example "exploit" code and further discussion. Fixed in
0.22.2
0.23.5
0.24.2
References Updated Nov 08, 2023 · Source: OSV.dev |
0.23.1
unknown
Dependencies (12)
+ 4 more
Changelog
Compare changes
|
|
0.23.0
unknown
1 CVE
GHSA-969w-q74q-9j8v
RUSTSEC-2022-0070
Dec 08, 2022
Unsound API in `secp256k1` allows use-after-free and invalid deallocation from safe code
Medium
Because of incorrect bounds on method The method takes a place for storing the context as a mutable reference and returns context containing that reference. Because the code internally uses You are unaffected if you either
The patched version uses correct bounds which means it is API-breaking. This effectively means adopting the policy of Rust lang itself allowing API-breaking changes to fix soundness bugs. Note however that valid straigthforward usage of the code will continue to compile. Only unsound code or code that propagates the bound in custom generics will fail to compile. If the code is sound fixing the bounds should be sufficient to make the code compile. See the GitHub issue for example "exploit" code and further discussion. Fixed in
0.22.2
0.23.5
0.24.2
References Updated Nov 08, 2023 · Source: OSV.dev |
0.23.0
unknown
Dependencies (12)
+ 4 more
Changelog
Compare changes
|
|
0.22.1
unknown
yanked
1 CVE
GHSA-969w-q74q-9j8v
RUSTSEC-2022-0070
Dec 08, 2022
Unsound API in `secp256k1` allows use-after-free and invalid deallocation from safe code
Medium
Because of incorrect bounds on method The method takes a place for storing the context as a mutable reference and returns context containing that reference. Because the code internally uses You are unaffected if you either
The patched version uses correct bounds which means it is API-breaking. This effectively means adopting the policy of Rust lang itself allowing API-breaking changes to fix soundness bugs. Note however that valid straigthforward usage of the code will continue to compile. Only unsound code or code that propagates the bound in custom generics will fail to compile. If the code is sound fixing the bounds should be sufficient to make the code compile. See the GitHub issue for example "exploit" code and further discussion. Fixed in
0.22.2
0.23.5
0.24.2
References Updated Nov 08, 2023 · Source: OSV.dev |
0.22.1
unknown
yanked
Dependencies (9)
+ 1 more
Changelog
Compare changes
|
|
0.22.0
unknown
1 CVE
GHSA-969w-q74q-9j8v
RUSTSEC-2022-0070
Dec 08, 2022
Unsound API in `secp256k1` allows use-after-free and invalid deallocation from safe code
Medium
Because of incorrect bounds on method The method takes a place for storing the context as a mutable reference and returns context containing that reference. Because the code internally uses You are unaffected if you either
The patched version uses correct bounds which means it is API-breaking. This effectively means adopting the policy of Rust lang itself allowing API-breaking changes to fix soundness bugs. Note however that valid straigthforward usage of the code will continue to compile. Only unsound code or code that propagates the bound in custom generics will fail to compile. If the code is sound fixing the bounds should be sufficient to make the code compile. See the GitHub issue for example "exploit" code and further discussion. Fixed in
0.22.2
0.23.5
0.24.2
References Updated Nov 08, 2023 · Source: OSV.dev |
0.22.0
unknown
Dependencies (9)
+ 1 more
Changelog
Compare changes
|
|
0.21.3
unknown
1 CVE
GHSA-969w-q74q-9j8v
RUSTSEC-2022-0070
Dec 08, 2022
Unsound API in `secp256k1` allows use-after-free and invalid deallocation from safe code
Medium
Because of incorrect bounds on method The method takes a place for storing the context as a mutable reference and returns context containing that reference. Because the code internally uses You are unaffected if you either
The patched version uses correct bounds which means it is API-breaking. This effectively means adopting the policy of Rust lang itself allowing API-breaking changes to fix soundness bugs. Note however that valid straigthforward usage of the code will continue to compile. Only unsound code or code that propagates the bound in custom generics will fail to compile. If the code is sound fixing the bounds should be sufficient to make the code compile. See the GitHub issue for example "exploit" code and further discussion. Fixed in
0.22.2
0.23.5
0.24.2
References Updated Nov 08, 2023 · Source: OSV.dev |
0.21.3
unknown
Dependencies (9)
+ 1 more
Changelog
Compare changes
|
|
0.21.2
unknown
1 CVE
GHSA-969w-q74q-9j8v
RUSTSEC-2022-0070
Dec 08, 2022
Unsound API in `secp256k1` allows use-after-free and invalid deallocation from safe code
Medium
Because of incorrect bounds on method The method takes a place for storing the context as a mutable reference and returns context containing that reference. Because the code internally uses You are unaffected if you either
The patched version uses correct bounds which means it is API-breaking. This effectively means adopting the policy of Rust lang itself allowing API-breaking changes to fix soundness bugs. Note however that valid straigthforward usage of the code will continue to compile. Only unsound code or code that propagates the bound in custom generics will fail to compile. If the code is sound fixing the bounds should be sufficient to make the code compile. See the GitHub issue for example "exploit" code and further discussion. Fixed in
0.22.2
0.23.5
0.24.2
References Updated Nov 08, 2023 · Source: OSV.dev |
0.21.2
unknown
Dependencies (9)
+ 1 more
Changelog
Compare changes
|
|
0.21.1
unknown
1 CVE
GHSA-969w-q74q-9j8v
RUSTSEC-2022-0070
Dec 08, 2022
Unsound API in `secp256k1` allows use-after-free and invalid deallocation from safe code
Medium
Because of incorrect bounds on method The method takes a place for storing the context as a mutable reference and returns context containing that reference. Because the code internally uses You are unaffected if you either
The patched version uses correct bounds which means it is API-breaking. This effectively means adopting the policy of Rust lang itself allowing API-breaking changes to fix soundness bugs. Note however that valid straigthforward usage of the code will continue to compile. Only unsound code or code that propagates the bound in custom generics will fail to compile. If the code is sound fixing the bounds should be sufficient to make the code compile. See the GitHub issue for example "exploit" code and further discussion. Fixed in
0.22.2
0.23.5
0.24.2
References Updated Nov 08, 2023 · Source: OSV.dev |
0.21.1
unknown
Dependencies (9)
+ 1 more
Changelog
Compare changes
|
|
0.21.0
unknown
yanked
1 CVE
GHSA-969w-q74q-9j8v
RUSTSEC-2022-0070
Dec 08, 2022
Unsound API in `secp256k1` allows use-after-free and invalid deallocation from safe code
Medium
Because of incorrect bounds on method The method takes a place for storing the context as a mutable reference and returns context containing that reference. Because the code internally uses You are unaffected if you either
The patched version uses correct bounds which means it is API-breaking. This effectively means adopting the policy of Rust lang itself allowing API-breaking changes to fix soundness bugs. Note however that valid straigthforward usage of the code will continue to compile. Only unsound code or code that propagates the bound in custom generics will fail to compile. If the code is sound fixing the bounds should be sufficient to make the code compile. See the GitHub issue for example "exploit" code and further discussion. Fixed in
0.22.2
0.23.5
0.24.2
References Updated Nov 08, 2023 · Source: OSV.dev |
0.21.0
unknown
yanked
Dependencies (9)
+ 1 more
Changelog
Compare changes
|
|
0.20.3
unknown
1 CVE
GHSA-969w-q74q-9j8v
RUSTSEC-2022-0070
Dec 08, 2022
Unsound API in `secp256k1` allows use-after-free and invalid deallocation from safe code
Medium
Because of incorrect bounds on method The method takes a place for storing the context as a mutable reference and returns context containing that reference. Because the code internally uses You are unaffected if you either
The patched version uses correct bounds which means it is API-breaking. This effectively means adopting the policy of Rust lang itself allowing API-breaking changes to fix soundness bugs. Note however that valid straigthforward usage of the code will continue to compile. Only unsound code or code that propagates the bound in custom generics will fail to compile. If the code is sound fixing the bounds should be sufficient to make the code compile. See the GitHub issue for example "exploit" code and further discussion. Fixed in
0.22.2
0.23.5
0.24.2
References Updated Nov 08, 2023 · Source: OSV.dev |
0.20.3
unknown
Dependencies (9)
+ 1 more
Changelog
Compare changes
|
|
0.20.2
unknown
1 CVE
GHSA-969w-q74q-9j8v
RUSTSEC-2022-0070
Dec 08, 2022
Unsound API in `secp256k1` allows use-after-free and invalid deallocation from safe code
Medium
Because of incorrect bounds on method The method takes a place for storing the context as a mutable reference and returns context containing that reference. Because the code internally uses You are unaffected if you either
The patched version uses correct bounds which means it is API-breaking. This effectively means adopting the policy of Rust lang itself allowing API-breaking changes to fix soundness bugs. Note however that valid straigthforward usage of the code will continue to compile. Only unsound code or code that propagates the bound in custom generics will fail to compile. If the code is sound fixing the bounds should be sufficient to make the code compile. See the GitHub issue for example "exploit" code and further discussion. Fixed in
0.22.2
0.23.5
0.24.2
References Updated Nov 08, 2023 · Source: OSV.dev |
0.20.2
unknown
Dependencies (9)
+ 1 more
Changelog
Compare changes
|
|
0.20.1
unknown
1 CVE
GHSA-969w-q74q-9j8v
RUSTSEC-2022-0070
Dec 08, 2022
Unsound API in `secp256k1` allows use-after-free and invalid deallocation from safe code
Medium
Because of incorrect bounds on method The method takes a place for storing the context as a mutable reference and returns context containing that reference. Because the code internally uses You are unaffected if you either
The patched version uses correct bounds which means it is API-breaking. This effectively means adopting the policy of Rust lang itself allowing API-breaking changes to fix soundness bugs. Note however that valid straigthforward usage of the code will continue to compile. Only unsound code or code that propagates the bound in custom generics will fail to compile. If the code is sound fixing the bounds should be sufficient to make the code compile. See the GitHub issue for example "exploit" code and further discussion. Fixed in
0.22.2
0.23.5
0.24.2
References Updated Nov 08, 2023 · Source: OSV.dev |
0.20.1
unknown
Dependencies (9)
+ 1 more
Changelog
Compare changes
|
|
0.20.0
unknown
1 CVE
GHSA-969w-q74q-9j8v
RUSTSEC-2022-0070
Dec 08, 2022
Unsound API in `secp256k1` allows use-after-free and invalid deallocation from safe code
Medium
Because of incorrect bounds on method The method takes a place for storing the context as a mutable reference and returns context containing that reference. Because the code internally uses You are unaffected if you either
The patched version uses correct bounds which means it is API-breaking. This effectively means adopting the policy of Rust lang itself allowing API-breaking changes to fix soundness bugs. Note however that valid straigthforward usage of the code will continue to compile. Only unsound code or code that propagates the bound in custom generics will fail to compile. If the code is sound fixing the bounds should be sufficient to make the code compile. See the GitHub issue for example "exploit" code and further discussion. Fixed in
0.22.2
0.23.5
0.24.2
References Updated Nov 08, 2023 · Source: OSV.dev |
0.20.0
unknown
Dependencies (9)
+ 1 more
Changelog
Compare changes
|
|
0.19.0
unknown
1 CVE
GHSA-969w-q74q-9j8v
RUSTSEC-2022-0070
Dec 08, 2022
Unsound API in `secp256k1` allows use-after-free and invalid deallocation from safe code
Medium
Because of incorrect bounds on method The method takes a place for storing the context as a mutable reference and returns context containing that reference. Because the code internally uses You are unaffected if you either
The patched version uses correct bounds which means it is API-breaking. This effectively means adopting the policy of Rust lang itself allowing API-breaking changes to fix soundness bugs. Note however that valid straigthforward usage of the code will continue to compile. Only unsound code or code that propagates the bound in custom generics will fail to compile. If the code is sound fixing the bounds should be sufficient to make the code compile. See the GitHub issue for example "exploit" code and further discussion. Fixed in
0.22.2
0.23.5
0.24.2
References Updated Nov 08, 2023 · Source: OSV.dev |
0.19.0
unknown
Dependencies (9)
+ 1 more
Changelog
Compare changes
|
|
0.18.0
unknown
1 CVE
GHSA-969w-q74q-9j8v
RUSTSEC-2022-0070
Dec 08, 2022
Unsound API in `secp256k1` allows use-after-free and invalid deallocation from safe code
Medium
Because of incorrect bounds on method The method takes a place for storing the context as a mutable reference and returns context containing that reference. Because the code internally uses You are unaffected if you either
The patched version uses correct bounds which means it is API-breaking. This effectively means adopting the policy of Rust lang itself allowing API-breaking changes to fix soundness bugs. Note however that valid straigthforward usage of the code will continue to compile. Only unsound code or code that propagates the bound in custom generics will fail to compile. If the code is sound fixing the bounds should be sufficient to make the code compile. See the GitHub issue for example "exploit" code and further discussion. Fixed in
0.22.2
0.23.5
0.24.2
References Updated Nov 08, 2023 · Source: OSV.dev |
0.18.0
unknown
Dependencies (9)
+ 1 more
Changelog
Compare changes
|
|
0.17.2
unknown
1 CVE
GHSA-969w-q74q-9j8v
RUSTSEC-2022-0070
Dec 08, 2022
Unsound API in `secp256k1` allows use-after-free and invalid deallocation from safe code
Medium
Because of incorrect bounds on method The method takes a place for storing the context as a mutable reference and returns context containing that reference. Because the code internally uses You are unaffected if you either
The patched version uses correct bounds which means it is API-breaking. This effectively means adopting the policy of Rust lang itself allowing API-breaking changes to fix soundness bugs. Note however that valid straigthforward usage of the code will continue to compile. Only unsound code or code that propagates the bound in custom generics will fail to compile. If the code is sound fixing the bounds should be sufficient to make the code compile. See the GitHub issue for example "exploit" code and further discussion. Fixed in
0.22.2
0.23.5
0.24.2
References Updated Nov 08, 2023 · Source: OSV.dev | ||
0.17.1
unknown
1 CVE
GHSA-969w-q74q-9j8v
RUSTSEC-2022-0070
Dec 08, 2022
Unsound API in `secp256k1` allows use-after-free and invalid deallocation from safe code
Medium
Because of incorrect bounds on method The method takes a place for storing the context as a mutable reference and returns context containing that reference. Because the code internally uses You are unaffected if you either
The patched version uses correct bounds which means it is API-breaking. This effectively means adopting the policy of Rust lang itself allowing API-breaking changes to fix soundness bugs. Note however that valid straigthforward usage of the code will continue to compile. Only unsound code or code that propagates the bound in custom generics will fail to compile. If the code is sound fixing the bounds should be sufficient to make the code compile. See the GitHub issue for example "exploit" code and further discussion. Fixed in
0.22.2
0.23.5
0.24.2
References Updated Nov 08, 2023 · Source: OSV.dev | ||
0.17.0
unknown
1 CVE
GHSA-969w-q74q-9j8v
RUSTSEC-2022-0070
Dec 08, 2022
Unsound API in `secp256k1` allows use-after-free and invalid deallocation from safe code
Medium
Because of incorrect bounds on method The method takes a place for storing the context as a mutable reference and returns context containing that reference. Because the code internally uses You are unaffected if you either
The patched version uses correct bounds which means it is API-breaking. This effectively means adopting the policy of Rust lang itself allowing API-breaking changes to fix soundness bugs. Note however that valid straigthforward usage of the code will continue to compile. Only unsound code or code that propagates the bound in custom generics will fail to compile. If the code is sound fixing the bounds should be sufficient to make the code compile. See the GitHub issue for example "exploit" code and further discussion. Fixed in
0.22.2
0.23.5
0.24.2
References Updated Nov 08, 2023 · Source: OSV.dev | ||
0.16.0
unknown
1 CVE
GHSA-969w-q74q-9j8v
RUSTSEC-2022-0070
Dec 08, 2022
Unsound API in `secp256k1` allows use-after-free and invalid deallocation from safe code
Medium
Because of incorrect bounds on method The method takes a place for storing the context as a mutable reference and returns context containing that reference. Because the code internally uses You are unaffected if you either
The patched version uses correct bounds which means it is API-breaking. This effectively means adopting the policy of Rust lang itself allowing API-breaking changes to fix soundness bugs. Note however that valid straigthforward usage of the code will continue to compile. Only unsound code or code that propagates the bound in custom generics will fail to compile. If the code is sound fixing the bounds should be sufficient to make the code compile. See the GitHub issue for example "exploit" code and further discussion. Fixed in
0.22.2
0.23.5
0.24.2
References Updated Nov 08, 2023 · Source: OSV.dev | ||
0.15.5
unknown
1 CVE
GHSA-969w-q74q-9j8v
RUSTSEC-2022-0070
Dec 08, 2022
Unsound API in `secp256k1` allows use-after-free and invalid deallocation from safe code
Medium
Because of incorrect bounds on method The method takes a place for storing the context as a mutable reference and returns context containing that reference. Because the code internally uses You are unaffected if you either
The patched version uses correct bounds which means it is API-breaking. This effectively means adopting the policy of Rust lang itself allowing API-breaking changes to fix soundness bugs. Note however that valid straigthforward usage of the code will continue to compile. Only unsound code or code that propagates the bound in custom generics will fail to compile. If the code is sound fixing the bounds should be sufficient to make the code compile. See the GitHub issue for example "exploit" code and further discussion. Fixed in
0.22.2
0.23.5
0.24.2
References Updated Nov 08, 2023 · Source: OSV.dev | ||
0.15.4
unknown
yanked
1 CVE
GHSA-969w-q74q-9j8v
RUSTSEC-2022-0070
Dec 08, 2022
Unsound API in `secp256k1` allows use-after-free and invalid deallocation from safe code
Medium
Because of incorrect bounds on method The method takes a place for storing the context as a mutable reference and returns context containing that reference. Because the code internally uses You are unaffected if you either
The patched version uses correct bounds which means it is API-breaking. This effectively means adopting the policy of Rust lang itself allowing API-breaking changes to fix soundness bugs. Note however that valid straigthforward usage of the code will continue to compile. Only unsound code or code that propagates the bound in custom generics will fail to compile. If the code is sound fixing the bounds should be sufficient to make the code compile. See the GitHub issue for example "exploit" code and further discussion. Fixed in
0.22.2
0.23.5
0.24.2
References Updated Nov 08, 2023 · Source: OSV.dev | ||
0.15.3
unknown
1 CVE
GHSA-969w-q74q-9j8v
RUSTSEC-2022-0070
Dec 08, 2022
Unsound API in `secp256k1` allows use-after-free and invalid deallocation from safe code
Medium
Because of incorrect bounds on method The method takes a place for storing the context as a mutable reference and returns context containing that reference. Because the code internally uses You are unaffected if you either
The patched version uses correct bounds which means it is API-breaking. This effectively means adopting the policy of Rust lang itself allowing API-breaking changes to fix soundness bugs. Note however that valid straigthforward usage of the code will continue to compile. Only unsound code or code that propagates the bound in custom generics will fail to compile. If the code is sound fixing the bounds should be sufficient to make the code compile. See the GitHub issue for example "exploit" code and further discussion. Fixed in
0.22.2
0.23.5
0.24.2
References Updated Nov 08, 2023 · Source: OSV.dev | ||
0.15.2
unknown
1 CVE
GHSA-969w-q74q-9j8v
RUSTSEC-2022-0070
Dec 08, 2022
Unsound API in `secp256k1` allows use-after-free and invalid deallocation from safe code
Medium
Because of incorrect bounds on method The method takes a place for storing the context as a mutable reference and returns context containing that reference. Because the code internally uses You are unaffected if you either
The patched version uses correct bounds which means it is API-breaking. This effectively means adopting the policy of Rust lang itself allowing API-breaking changes to fix soundness bugs. Note however that valid straigthforward usage of the code will continue to compile. Only unsound code or code that propagates the bound in custom generics will fail to compile. If the code is sound fixing the bounds should be sufficient to make the code compile. See the GitHub issue for example "exploit" code and further discussion. Fixed in
0.22.2
0.23.5
0.24.2
References Updated Nov 08, 2023 · Source: OSV.dev | ||
0.15.1
unknown
1 CVE
GHSA-969w-q74q-9j8v
RUSTSEC-2022-0070
Dec 08, 2022
Unsound API in `secp256k1` allows use-after-free and invalid deallocation from safe code
Medium
Because of incorrect bounds on method The method takes a place for storing the context as a mutable reference and returns context containing that reference. Because the code internally uses You are unaffected if you either
The patched version uses correct bounds which means it is API-breaking. This effectively means adopting the policy of Rust lang itself allowing API-breaking changes to fix soundness bugs. Note however that valid straigthforward usage of the code will continue to compile. Only unsound code or code that propagates the bound in custom generics will fail to compile. If the code is sound fixing the bounds should be sufficient to make the code compile. See the GitHub issue for example "exploit" code and further discussion. Fixed in
0.22.2
0.23.5
0.24.2
References Updated Nov 08, 2023 · Source: OSV.dev | ||
0.15.0
unknown
1 CVE
GHSA-969w-q74q-9j8v
RUSTSEC-2022-0070
Dec 08, 2022
Unsound API in `secp256k1` allows use-after-free and invalid deallocation from safe code
Medium
Because of incorrect bounds on method The method takes a place for storing the context as a mutable reference and returns context containing that reference. Because the code internally uses You are unaffected if you either
The patched version uses correct bounds which means it is API-breaking. This effectively means adopting the policy of Rust lang itself allowing API-breaking changes to fix soundness bugs. Note however that valid straigthforward usage of the code will continue to compile. Only unsound code or code that propagates the bound in custom generics will fail to compile. If the code is sound fixing the bounds should be sufficient to make the code compile. See the GitHub issue for example "exploit" code and further discussion. Fixed in
0.22.2
0.23.5
0.24.2
References Updated Nov 08, 2023 · Source: OSV.dev | ||
0.14.1
unknown
1 CVE
GHSA-969w-q74q-9j8v
RUSTSEC-2022-0070
Dec 08, 2022
Unsound API in `secp256k1` allows use-after-free and invalid deallocation from safe code
Medium
Because of incorrect bounds on method The method takes a place for storing the context as a mutable reference and returns context containing that reference. Because the code internally uses You are unaffected if you either
The patched version uses correct bounds which means it is API-breaking. This effectively means adopting the policy of Rust lang itself allowing API-breaking changes to fix soundness bugs. Note however that valid straigthforward usage of the code will continue to compile. Only unsound code or code that propagates the bound in custom generics will fail to compile. If the code is sound fixing the bounds should be sufficient to make the code compile. See the GitHub issue for example "exploit" code and further discussion. Fixed in
0.22.2
0.23.5
0.24.2
References Updated Nov 08, 2023 · Source: OSV.dev |