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.

Sign up for GitHub

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

Jump to bottom

opStack is not zero-initialized which leads to the memory disclosure #38

Open
rivit98 opened this issue Aug 19, 2024 · 0 comments
Open

opStack is not zero-initialized which leads to the memory disclosure #38

rivit98 opened this issue Aug 19, 2024 · 0 comments

Comments

@rivit98
Copy link

rivit98 commented Aug 19, 2024

Hello, during my research on this project, I noticed that opStack variable is not zero-initialized (https://github.com/jnz/q3vm/blob/master/src/vm/vm.c#L873). This can lead to the memory disclosure issue. Ideally, opStack should be zeroed on function entry.

Please see PoC and more details here:
https://github.com/TeamAustria/writeups/blob/main/2024-justctf/q3vm.md
https://enzo.run/posts/justctf2024/
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@rivit98