Cyber Resilience

CVE-2023-42441

Vyperlang Vyper 0.2.9 – 0.3.10

Public PoC
Published
18 September 2023
Modified
21 November 2024
Patch / advisory
View advisory
CVSS Score v3.1 5.3
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
EPSS Score 0.0042 35th percentile
Risk Priority 44 floored blend · peak EPSS

Summary

CVE-2023-42441 is a medium-severity Deadlock (CWE-833) vulnerability in Vyperlang Vyper. Its CVSS base score is 5.3 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Endpoint Denial of Service (T1499); ranked at the 35th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

EU & UK References

Vulnerability Data

Vyper is a Pythonic Smart Contract Language for the Ethereum Virtual Machine (EVM). Starting in version 0.2.9 and prior to version 0.3.10, locks of the type `@nonreentrant("")` or `@nonreentrant('')` do not produce reentrancy checks at runtime. This issue is fixed…

more

in version 0.3.10. As a workaround, ensure the lock name is a non-empty string.

CWE(s)
CWE-833CWE-667

Related Threats

MITRE ATT&CK Enterprise Techniques

T1499 Endpoint Denial of Service Impact
Adversaries may perform Endpoint Denial of Service (DoS) attacks to degrade or block the availability of services to users.
attack.mitre.org →
T1499.004 Application or System Exploitation Impact
Adversaries may exploit software vulnerabilities that can cause an application or system to crash and deny availability to users.
attack.mitre.org →
T1068 Exploitation for Privilege Escalation Privilege Escalation
Adversaries may exploit software vulnerabilities in an attempt to elevate privileges.
attack.mitre.org →
T1548 Abuse Elevation Control Mechanism Privilege Escalation
Adversaries may circumvent mechanisms designed to control privilege elevation to gain higher-level permissions.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2024-32648Same product: Vyperlang Vyper
CVE-2025-27104Same product: Vyperlang Vyper
CVE-2024-24567Same product: Vyperlang Vyper
CVE-2023-30837Same product: Vyperlang Vyper
CVE-2023-39363Same product: Vyperlang Vyper
CVE-2023-32058Same product: Vyperlang Vyper
CVE-2024-32645Same product: Vyperlang Vyper
CVE-2025-26622Same product: Vyperlang Vyper
CVE-2023-42460Same product: Vyperlang Vyper
CVE-2024-32646Same product: Vyperlang Vyper

Affected Assets

vyperlang
vyper
0.2.9 — 0.3.10

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V15.4.3

Likely Mitigating Controls AI

Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.

PL-6 Security-related Activity Planning
addresses: CWE-833

Advance scheduling and deconfliction of security tasks lowers the chance that overlapping operations will produce deadlock conditions on shared resources.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly include code reviews, static analysis, and concurrency standards that prevent improper locking.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing in development can detect deadlock conditions through stress and concurrency testing.

A.8.25 Secure development life cycle partial match
prevents

Secure development lifecycle requires deadlock analysis and avoidance techniques during design and coding.

A.8.26 Application security requirements partial match
prevents

Application security requirements can mandate proper lock acquisition/release patterns.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure system architecture principles include concurrency controls and resource-locking discipline that prevent deadlock.

A.8.28 Secure coding partial match
prevents

Secure coding standards mandate safe lock ordering, timeouts, and deadlock detection patterns.

A.8.32 Change management partial match
prevents

Change management may catch locking issues introduced by modifications but does not prevent the weakness itself.

References