pkcs11
Activity
- Latest release
- 6y ago
- Total releases
- 8
- Cadence
- ~2 months
- Last 12 months
- 0
Details
- License
- Apache-2.0
- First release
- Nov 09, 2017
| Version | Released | |
|---|---|---|
0.5.0
unknown
1 CVE
RUSTSEC-2022-0034
Jul 22, 2022
Safety issues in `pkcs11` ImpactThe interface of Other problems that have been identified by the community include use-after-free (mheese/rust-pkcs11#53) and unsound uses of WorkaroundsUsers of the crate need to be extremely careful in all the calls made to avoid segmentation faults and undefined behaviour due to use of stale pointers. Whenever a pointer is derived from a value and passed to the library, that value's lifetime must be guaranteed to outlast all calls that rely on the pointer. For example, users should avoid creating or converting values within a separate scope (say, in a dedicated function), deriving a pointer, then extracting the pointer from that scope leaving the value to get dropped before passing the pointer to ReferencesReferences Updated Jul 25, 2022 · Source: OSV.dev |
0.5.0
unknown
Dependencies (6)
|
|
0.4.2
unknown
1 CVE
RUSTSEC-2022-0034
Jul 22, 2022
Safety issues in `pkcs11` ImpactThe interface of Other problems that have been identified by the community include use-after-free (mheese/rust-pkcs11#53) and unsound uses of WorkaroundsUsers of the crate need to be extremely careful in all the calls made to avoid segmentation faults and undefined behaviour due to use of stale pointers. Whenever a pointer is derived from a value and passed to the library, that value's lifetime must be guaranteed to outlast all calls that rely on the pointer. For example, users should avoid creating or converting values within a separate scope (say, in a dedicated function), deriving a pointer, then extracting the pointer from that scope leaving the value to get dropped before passing the pointer to ReferencesReferences Updated Jul 25, 2022 · Source: OSV.dev |
0.4.2
unknown
Dependencies (6)
|
|
0.4.1
unknown
1 CVE
RUSTSEC-2022-0034
Jul 22, 2022
Safety issues in `pkcs11` ImpactThe interface of Other problems that have been identified by the community include use-after-free (mheese/rust-pkcs11#53) and unsound uses of WorkaroundsUsers of the crate need to be extremely careful in all the calls made to avoid segmentation faults and undefined behaviour due to use of stale pointers. Whenever a pointer is derived from a value and passed to the library, that value's lifetime must be guaranteed to outlast all calls that rely on the pointer. For example, users should avoid creating or converting values within a separate scope (say, in a dedicated function), deriving a pointer, then extracting the pointer from that scope leaving the value to get dropped before passing the pointer to ReferencesReferences Updated Jul 25, 2022 · Source: OSV.dev |
0.4.1
unknown
Dependencies (6)
|
|
0.4.0
unknown
1 CVE
RUSTSEC-2022-0034
Jul 22, 2022
Safety issues in `pkcs11` ImpactThe interface of Other problems that have been identified by the community include use-after-free (mheese/rust-pkcs11#53) and unsound uses of WorkaroundsUsers of the crate need to be extremely careful in all the calls made to avoid segmentation faults and undefined behaviour due to use of stale pointers. Whenever a pointer is derived from a value and passed to the library, that value's lifetime must be guaranteed to outlast all calls that rely on the pointer. For example, users should avoid creating or converting values within a separate scope (say, in a dedicated function), deriving a pointer, then extracting the pointer from that scope leaving the value to get dropped before passing the pointer to ReferencesReferences Updated Jul 25, 2022 · Source: OSV.dev |
0.4.0
unknown
Dependencies (4)
|
|
0.3.1
unknown
1 CVE
RUSTSEC-2022-0034
Jul 22, 2022
Safety issues in `pkcs11` ImpactThe interface of Other problems that have been identified by the community include use-after-free (mheese/rust-pkcs11#53) and unsound uses of WorkaroundsUsers of the crate need to be extremely careful in all the calls made to avoid segmentation faults and undefined behaviour due to use of stale pointers. Whenever a pointer is derived from a value and passed to the library, that value's lifetime must be guaranteed to outlast all calls that rely on the pointer. For example, users should avoid creating or converting values within a separate scope (say, in a dedicated function), deriving a pointer, then extracting the pointer from that scope leaving the value to get dropped before passing the pointer to ReferencesReferences Updated Jul 25, 2022 · Source: OSV.dev |
0.3.1
unknown
Dependencies (4)
|
|
0.3.0
unknown
1 CVE
RUSTSEC-2022-0034
Jul 22, 2022
Safety issues in `pkcs11` ImpactThe interface of Other problems that have been identified by the community include use-after-free (mheese/rust-pkcs11#53) and unsound uses of WorkaroundsUsers of the crate need to be extremely careful in all the calls made to avoid segmentation faults and undefined behaviour due to use of stale pointers. Whenever a pointer is derived from a value and passed to the library, that value's lifetime must be guaranteed to outlast all calls that rely on the pointer. For example, users should avoid creating or converting values within a separate scope (say, in a dedicated function), deriving a pointer, then extracting the pointer from that scope leaving the value to get dropped before passing the pointer to ReferencesReferences Updated Jul 25, 2022 · Source: OSV.dev |
0.3.0
unknown
Dependencies (4)
|
|
0.2.0
unknown
1 CVE
RUSTSEC-2022-0034
Jul 22, 2022
Safety issues in `pkcs11` ImpactThe interface of Other problems that have been identified by the community include use-after-free (mheese/rust-pkcs11#53) and unsound uses of WorkaroundsUsers of the crate need to be extremely careful in all the calls made to avoid segmentation faults and undefined behaviour due to use of stale pointers. Whenever a pointer is derived from a value and passed to the library, that value's lifetime must be guaranteed to outlast all calls that rely on the pointer. For example, users should avoid creating or converting values within a separate scope (say, in a dedicated function), deriving a pointer, then extracting the pointer from that scope leaving the value to get dropped before passing the pointer to ReferencesReferences Updated Jul 25, 2022 · Source: OSV.dev |
0.2.0
unknown
Dependencies (3)
|
|
0.1.0
unknown
1 CVE
RUSTSEC-2022-0034
Jul 22, 2022
Safety issues in `pkcs11` ImpactThe interface of Other problems that have been identified by the community include use-after-free (mheese/rust-pkcs11#53) and unsound uses of WorkaroundsUsers of the crate need to be extremely careful in all the calls made to avoid segmentation faults and undefined behaviour due to use of stale pointers. Whenever a pointer is derived from a value and passed to the library, that value's lifetime must be guaranteed to outlast all calls that rely on the pointer. For example, users should avoid creating or converting values within a separate scope (say, in a dedicated function), deriving a pointer, then extracting the pointer from that scope leaving the value to get dropped before passing the pointer to ReferencesReferences Updated Jul 25, 2022 · Source: OSV.dev |
0.1.0
unknown
Dependencies (1)
|