CVE-2023-34449Public exploitNetwork attack vector

Contract-result corruption via missing result wrapper

Published Jun 14, 2023 · Updated Dec 30, 2024

Incorrect return-value decoding in Parity Technologies ink! 4.0.0 through 4.2.0 allows remote attackers to corrupt contract results. The delegate-call path decodes the SCALE-encoded MessageResult buffer directly as R, so the wrapper's status byte becomes result data and unsigned integers can be returned at 256 times the stored value. Exposure requires an ink! 4.x contract that uses CallBuilder::delegate or ink_env::invoke_contract_delegate; ordinary calls and contracts without delegate calls are unaffected.

CVSS severity5.3
Medium
EPSS probability0.97%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Incorrect return-value decoding in Parity Technologies ink! 4.0.0 through 4.2.0 allows remote attackers to corrupt contract results. The delegate-call path decodes the SCALE-encoded MessageResult buffer directly as R, so the wrapper's status byte becomes result data and unsigned integers can be returned at 256 times the stored value. Exposure requires an ink! 4.x contract that uses CallBuilder::delegate or ink_env::invoke_contract_delegate; ordinary calls and contracts without delegate calls are unaffected.

The record

CVE
CVE-2023-34449
Published
Jun 14, 2023
Updated
Dec 30, 2024
Vendor
Parity Technologies
Product
ink!
Classifications
CWE-253, CWE-754
Attack vector
network
Privileges
unauthenticated

Timeline

How it unfolded

  1. Jun 14, 2023CVE publishedPublication date reported by the CVE source.
  2. Dec 30, 2024Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=>= 4.0.0, < 4.2.1

What conditions does exploitation require?

Attack vectornetwork
Required privilegesunauthenticated

What is affected?

Parity Technologies · ink!version=>= 4.0.0, < 4.2.1

Published CVSS scores

5.3NVDCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
5.3GitHub, Inc.CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitPublished

Weakness, pattern, technique

CWE-253Incorrect Check of Function Return Value
CWE-754Improper Check for Unusual or Exceptional Conditions

Public exploit references

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo