cve.bz

CVE-2023-23940 openzeppelin contracts

5.3 mediumEPSS 0.2%Fix available

Medium (5.3) in openzeppelin contracts. EPSS 0.2% estimated probability of exploitation activity in the next 30 days. Fixed in openzeppelin-cairo-contracts 0.6.1.

On this page
OpenZeppelin Contracts for Cairo is a library for secure smart contract development written in Cairo for StarkNet, a decentralized ZK Rollup. `is_valid_eth_signature` is missing a call to `finalize_keccak` after calling `verify_eth_signature`. As a result, any contract using `is_valid_eth_signature` from the account library (such as the `EthAccount` preset) is vulnerable to a malicious sequencer. Specifically, the malicious sequencer would be able to bypass signature validation to impersonate an instance of these accounts. The issue has been patched in 0.6.1.

Severity

CVSS 3.1

5.3 medium
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N
EPSS
0.2% (unchanged from 0.2% a week ago; 0.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 14th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2025-03-10. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-347 Improper Verification of Cryptographic Signature
CWE-345 Insufficient Verification of Data Authenticity
OWASP Top 10
A04:2025 Cryptographic Failures, A08:2025 Software or Data Integrity Failures
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2023-23940 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2023-23940?via=ask-ai-copy and https://cve.bz/cve/CVE-2023-23940?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2023-23940 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
openzeppelin:contractsfrom 0.2.0 before 0.6.1

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-626q-v9j4-mcp4PyPIopenzeppelin-cairo-contracts>=0.2.0 <0.6.10.6.1
PYSEC-2023-39PyPIopenzeppelin-cairo-contracts>=0.2.0 <0.6.10.6.1

Attack patterns (CAPEC)

  • CAPEC-463 Padding Oracle Crypto Attack Severity: High
  • CAPEC-475 Signature Spoofing by Improper Validation Likelihood: Low · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-345 (12).

References

Check your stackJSON