Security Resilience

CVE-2023-42441

Vyperlang Vyper 0.2.9 – 0.3.10

Public PoC
Published
18 September 2023
Modified
21 November 2024
Patch / 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.0051 42th percentile
Risk Priority 45 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

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 Junk Data (T1001.001); ranked at the 42th 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)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1001.001 Junk Data Command And Control
Adversaries may add junk data to protocols used for command and control to make detection more difficult.
T1003 OS Credential Dumping Credential Access
Adversaries may attempt to dump credentials to obtain account login and credential material, normally in the form of a hash or a clear text password.
T1003.005 Cached Domain Credentials Credential Access
Adversaries may attempt to access cached domain credentials used to allow authentication to occur in the event a domain controller is unavailable.
T1010 Application Window Discovery Discovery
Adversaries may attempt to get a listing of open application windows.
T1011 Exfiltration Over Other Network Medium Exfiltration
Adversaries may attempt to exfiltrate data over a different network medium than the command and control channel.
T1014 Rootkit Stealth
Adversaries may use rootkits to hide the presence of programs, files, network connections, services, drivers, and other system components.
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-2024-22419Same product: Vyperlang Vyper
CVE-2023-42443Same product: Vyperlang Vyper
CVE-2024-24561Same product: Vyperlang Vyper
CVE-2023-31146Same product: Vyperlang Vyper
CVE-2025-27105Same product: Vyperlang Vyper
CVE-2023-30837Same product: Vyperlang Vyper
CVE-2023-32058Same product: Vyperlang Vyper
CVE-2023-46247Same product: Vyperlang Vyper
CVE-2024-32481Same 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.

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 partial match
blocks

Secure SDLC practices can include concurrency analysis and lock discipline to avoid deadlock conditions.

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.

blocks

A.8.25 mandates a secure SDLC process with checkpoints, secure coding, testing and training; none of those steps stop an existing deadlock from being exploitable, they only aim to reduce the chance one is introduced

blocks

A.8.27 mandates establishing and applying secure engineering principles (defense-in-depth, least privilege, fail securely, security by design, etc.) and performing design reviews; deadlock is a runtime concurrency flaw in implementation or threading logic that these principles and reviews do not stop from being introduced or exploited.

prevents

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

finds

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

blocks

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

Hardening callouts derived

DISA STIG baselines are authored against specific weaknesses. Where this CVE cites a broad weakness class, the mapping is not asserted at that abstraction (owner ruling, 2026-09-25: grade only at Base and below), so no rule is shown here rather than a rule shown against the wrong grain.

  • No fine-grained STIG row for CWE-667, a class-level weakness, and none of its children carries one either.

References