Lucene search
K
Catalog
Vendors
Products
Timeline
Vulnerabilities
Sources
Documentation
Blog
Glossary
FAQ
Brand assets
Assessment
Agents dashboard
Agent Scanning
API Scanning
Assessment API
Alerts
Email notifications
Webhook notifications
Alerts API
SBOM package analysis
API Reference
Support
Settings
Sign in

Call to safeApprove without checking previous allowance in burnFees could result in locked funds

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

Call to safeApprove without checking previous allowance in burnFees could result in locked funds. Deprecated function can lead to unintended reverts and potential locking of funds. Possible mitigation steps include replacing safeApprove with safeIncreaseAllowance or using internal _approve function for additional allowance check

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

Book a live demo
19 Jun 2022 00:00Current
6.8Medium risk
Vulners AI Score6.8
safeapprovelocked fundsdeprecated functionmitigation stepsallowance check
6