Skip to content

Vyper has incorrect re-entrancy lock when key is empty string

Moderate severity GitHub Reviewed Published Sep 15, 2023 in vyperlang/vyper • Updated Nov 22, 2024

Package

pip vyper (pip)

Affected versions

>= 0.2.9, < 0.3.10

Patched versions

0.3.10

Description

Impact

Locks of the type @nonreentrant("") or @nonreentrant('') do not produce reentrancy checks at runtime.

@nonreentrant("") # unprotected
@external
def bar():
    pass

@nonreentrant("lock") # protected
@external
def foo():
    pass

Patches

Patched in #3605

Workarounds

The lock name should be a non-empty string.

References

Are there any links users can visit to find out more?

References

@charles-cooper charles-cooper published to vyperlang/vyper Sep 15, 2023
Published to the GitHub Advisory Database Sep 18, 2023
Reviewed Sep 18, 2023
Published by the National Vulnerability Database Sep 18, 2023
Last updated Nov 22, 2024

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

EPSS score

0.088%
(39th percentile)

Weaknesses

CVE ID

CVE-2023-42441

GHSA ID

GHSA-3hg2-r75x-g69m

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.