Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

R4R: fix potential reentrancy attack in relayMessage #109

Merged
merged 2 commits into from
Mar 1, 2024

Conversation

HaoyangLiu
Copy link
Contributor

Copy link

Encountered a total of 1 failing tests, 533 tests succeeded

Copy link

openzeppelin-code bot commented Feb 27, 2024

WIP: fix potential reentrancy attack in relayMessage

Generated at commit: 38e73183396bbf2201c4a092fb92a4a4bddbe68c

🚨 Report Summary

Severity Level Results
Contracts Critical
High
Medium
Low
Note
Total
3
3
0
18
45
69
Dependencies Critical
High
Medium
Low
Note
Total
0
0
0
0
0
0

For more details view the full report in OpenZeppelin Code Inspector

@HaoyangLiu HaoyangLiu changed the base branch from release/v0.5.0 to audits March 1, 2024 09:13
@HaoyangLiu HaoyangLiu changed the title WIP: fix potential reentrancy attack in relayMessage R4R: fix potential reentrancy attack in relayMessage Mar 1, 2024
@Tri-stone Tri-stone merged commit d5f48b8 into audits Mar 1, 2024
0 of 3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants