Lucene search
+L

No reentrancy guards on functions using .call

🗓️ 14 Jan 2022 00:00:00Reported by Code4renaType 
code423n4
 code423n4
🔗 github.com👁 6 Views

No reentrancy guards on functions using .call # Handle jayjonah8 # Vulnerability details ## Impact In BridgeMinter.sol the migrateToNewMinter() and withdrawETHToL1Migrator() both use the .call function without adding reentrancy guard modifiers to the functions. This is important when using .call as functions can be reentered before execution is complete manipulating state and stealing funds. Even if this function is only callable by the L1Migrator it still should have reentrancy guards in place as a protection

Data

Build on a solid foundation with Vulners data

We provide the essential building blocks for cybersecurity solutions with comprehensive, structured, and constantly updated vulnerability and exploits data

Api

Power your application with Vulners API

The Vulners REST API offers reliable, high-performance access to vulnerability intelligence, with 99.9% SLA uptime and CDN-backed data delivery for seamless global access

App

Assess and manage vulnerabilities with Vulners tools

Built on top of Vulners' database and SDK, end-user solutions give security professionals and developers lightweight and powerful tools for vulnerability remediation

30 Jan 2022 00:00Current
7.2High risk
Vulners AI Score7.2
6