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

Stack overflow when using python console #2083

Closed
yrp604 opened this issue Nov 1, 2020 · 3 comments
Closed

Stack overflow when using python console #2083

yrp604 opened this issue Nov 1, 2020 · 3 comments
Assignees
Labels
Impact: Low Issue is a papercut or has a good, supported workaround State: Invalid Issue had issues and is not valid Type: Bug Issue is a non-crashing bug with repro steps

Comments

@yrp604
Copy link
Contributor

yrp604 commented Nov 1, 2020

Windows 10 2.2.2508-dev Personal

Issue does not immediately repro with the same steps.

From the console I did the following:

>>> ii = current_function.lifted_il
>>> ii = ii[0]
>>> ii
>>> ii.operands
>>> ii.operands[1]
>>> ii.operands[2] # crash here
(3b1c.a68): Security check failure or stack buffer overrun - code c0000409 (!!! second chance !!!)
Subcode: 0x7 FAST_FAIL_FATAL_APP_EXIT 
ucrtbase!abort+0x4e:
00007ffc`f2fa287e cd29            int     29h
0:000> kn
 # Child-SP          RetAddr               Call Site
00 000000af`4936c100 00007ffc`eabc699a     ucrtbase!abort+0x4e
01 000000af`4936c130 00007ffc`a32bf4b0     VCRUNTIME140!_purecall+0x1a [D:\a01\_work\2\s\src\vctools\crt\vcruntime\src\misc\purevirt.cpp @ 29] 
02 000000af`4936c160 00007ffc`a330f302     Qt5Core!QAbstractEventDispatcher::filterNativeEvent+0x70
03 000000af`4936c1b0 00007ffc`b7ab76f9     Qt5Core!QEventDispatcherWin32::processEvents+0x552
04 000000af`4936f2e0 00007ffc`a32c097c     qwindows!qt_plugin_query_metadata+0x1f49
05 000000af`4936f310 00007ffc`a32c37f4     Qt5Core!QEventLoop::exec+0x1bc
06 000000af`4936f370 00007ff7`84f2846a     Qt5Core!QCoreApplication::exec+0x154
07 000000af`4936f3d0 00007ff7`84fa5b97     binaryninja+0x2846a
08 000000af`4936fb10 00007ff7`84fa4f7a     binaryninja+0xa5b97
09 000000af`4936fba0 00007ffc`f5077034     binaryninja+0xa4f7a
0a 000000af`4936fbe0 00007ffc`f547cec1     KERNEL32!BaseThreadInitThunk+0x14
0b 000000af`4936fc10 00000000`00000000     ntdll!RtlUserThreadStart+0x21
0:000> r
rax=0000000000000001 rbx=0000000000000001 rcx=0000000000000007
rdx=000000000000000f rsi=0000021cb60db5f0 rdi=0000000000000001
rip=00007ffcf2fa287e rsp=000000af4936c100 rbp=0000021cb6096840
 r8=0000000000000001  r9=000000af4936c0a8 r10=0000000000000012
r11=0000000000000246 r12=000000af4936c238 r13=0000000000000000
r14=0000000000000000 r15=000000af4936c1e8
iopl=0         nv up ei pl nz na pe nc
cs=0033  ss=002b  ds=002b  es=002b  fs=0053  gs=002b             efl=00000200
ucrtbase!abort+0x4e:
00007ffc`f2fa287e cd29            int     29h

binja-crash

binary is ntdll for arm64, linked in this comment and the current function was RtlAllocateHeap. Only possible other factor was I had been (ab)using the snippets plugin earlier in the python session.

@plafosse plafosse added State: Unreproducible Issue could not be reproduced by a developer Type: Bug Issue is a non-crashing bug with repro steps Impact: Low Issue is a papercut or has a good, supported workaround and removed State: Unreproducible Issue could not be reproduced by a developer labels Nov 4, 2020
@yrp604
Copy link
Contributor Author

yrp604 commented Nov 6, 2020

Looking at the stack trace again, this is almost definitely Vector35/snippets#7

@psifertex psifertex self-assigned this May 12, 2021
@psifertex
Copy link
Member

Upstream closed so closing this.

@psifertex psifertex added the State: Invalid Issue had issues and is not valid label May 28, 2021
@psifertex
Copy link
Member

FYI, marking as "invalid" only to help our sorting with 2.4 release bugs, the root bug on snippets is obviously valid. Still haven't been able to get a good debug trace on it yet as an update.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Impact: Low Issue is a papercut or has a good, supported workaround State: Invalid Issue had issues and is not valid Type: Bug Issue is a non-crashing bug with repro steps
Projects
None yet
Development

No branches or pull requests

3 participants