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

(HAL-25) SEQUENCE NUMBER MISMATCH IN TRANSACTION PROCESSING #594

Closed
SA124 opened this issue Sep 12, 2024 · 2 comments
Closed

(HAL-25) SEQUENCE NUMBER MISMATCH IN TRANSACTION PROCESSING #594

SA124 opened this issue Sep 12, 2024 · 2 comments
Assignees
Labels
Source: Audit Issues discovered by audit.

Comments

@SA124
Copy link

SA124 commented Sep 12, 2024

(HAL-25) SEQUENCE NUMBER MISMATCH IN TRANSACTION PROCESSING
Auditor: Halborn
Severity: Informational

Description
In the opt-executor transaction processing implementation in tick_transaction_pipe, there is a discrepancy between the sequence number used for transaction validation and the one used for adding the transaction to the mempool.

Screenshot 2024-09-12 at 12 31 10 PM

This mismatch bypasses an essential verification ensuring that user cannot use sequences that they already used. Fortunately, the execution VM performs the same verification upstream, but that could have an impact on future upgrades.

Score
AO:A/AC:L/AX:L/R:N/S:U/C:N/A:N/I:N/D:N/Y:N (0.0)
Screenshot 2024-09-12 at 12 31 43 PM

Recommendation
It is recommended to use the sequence number from the database instead of the one from the transaction.

@andygolay andygolay added the Source: Audit Issues discovered by audit. label Sep 13, 2024
@mzabaluev
Copy link
Collaborator

Duplicate of #415

@mzabaluev mzabaluev marked this as a duplicate of #415 Sep 17, 2024
@mzabaluev mzabaluev closed this as not planned Won't fix, can't repro, duplicate, stale Sep 17, 2024
@l-monninger
Copy link
Collaborator

This has been dealt with or modified in several forms. The latest change to sequence number validation to prevent GAS DOS was included in #722.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Source: Audit Issues discovered by audit.
Projects
None yet
Development

No branches or pull requests

5 participants