NFTBridge
60,000 USDC
View results
Submission Details
Severity: low
Invalid

explicitly check the validity of the parameters l2Address and l2Selector

Summary:

In State.sol The code doesn't explicitly check the validity of the parameters l2Address and l2Selector in the setStarklaneL2Address and setStarklaneL2Selector functions.

Vulnerability Details:

Potential Risks:

Invalid addresses or selectors could be set.

Impact:

Could lead to incorrect or failed messaging to Starknet L2.

Tools Used:

Manual

Recommendations:

Validate l2Address and l2Selector before setting.
Add require statements to ensure valid inputs.
Example:

require(l2Address > 0, "Invalid L2 address");
require(l2Selector > 0, "Invalid L2 selector");

Updates

Lead Judging Commences

n0kto Lead Judge 10 months ago
Submission Judgement Published
Invalidated
Reason: Non-acceptable severity
Assigned finding tags:

Informational / Gas

Please, do not suppose impacts, think about the real impact of the bug and check the CodeHawks documentation to confirm: https://docs.codehawks.com/hawks-auditors/how-to-determine-a-finding-validity A PoC always helps to understand the real impact possible.

Support

FAQs

Can't find an answer? Chat with us on Discord, Twitter or Linkedin.