Approved changes feed: RSS · Atom
cpe:2.3:a:parity:ink\!:*:*:*:*:*:rust:*:*
part: a version: * update: *
| Vendor | Parity (d4191ed2-5da2-54f0-a37b-57baccf1aafa) |
|---|---|
| Product | Ink! (e025c9c6-8f84-5e6a-8818-da9d068e19c8) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | rust |
| Target hardware | * |
| Other | * |
| Notes | Imported from gcve-enriched-dumps CVE data |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2023-34449 |
vulnerable | 2026-06-08 06:06:25.630939 |
ink! vulnerable to incorrect decoding of storage value when using `DelegateCall`
MEDIUM (5.3)
ink! is an embedded domain specific language to write smart contracts in Rust for blockchains built on the Substrate framework. Starting in version 4.0.0 and prior to version 4.2.1, the return value when using delegate call mechanics, either through `CallBuilder::delegate` or `ink_env::invoke_contract_delegate`, is decoded incorrectly. This bug was related to the mechanics around decoding a call's return buffer, which was changed as part of pull request 1450. Since this feature was only released in ink! 4.0.0, no previous versions are affected. Users who have an ink! 4.x series contract should upgrade to 4.2.1 to receive a patch.
Published: 2023-06-14T20:10:54.842Z
Updated: 2024-12-30T14:57:52.199Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.