You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The following input strings causes dora to run an infinite loop, eventually consume all memory and the go process gets killed by the OS (Tested in Ubuntu 20.04).
Input strings:
{a
{'a'}
[a[
Post crash dmesg error message (in Ubuntu 20.04 ) :
Out of memory: Killed process 174471 (test) total-vm:16253192kB, anon-rss:15326772kB, file-rss:0kB, shmem-rss:0kB, UID:1001 pgtables:30120kB oom_score_adj:0
A bug which causes the go program to have a runtime panic because of slice bounds out of range due to a bug in lexer.go. This bug can be triggered by certain strings that contain 0. For the testcase [[0000// program crashed with the following error :
Bug Type #1
Description
The following input strings causes dora to run an infinite loop, eventually consume all memory and the go process gets killed by the OS (Tested in Ubuntu 20.04).
Input strings:
{a
{'a'}
[a[
Post crash dmesg error message (in Ubuntu 20.04 ) :
Proof of Concept
PoC #1
PoC #2
PoC #3
To Run
Impact
This can cause the Running Process to consume all available memory on the machine, and eventually get killed by OS (tested in ubuntu 20.04).
Bug Type #2
Description
A bug which causes the go program to have a
runtime panic
because ofslice bounds out of range
due to a bug inlexer.go
. This bug can be triggered by certain strings that contain0
. For the testcase[[0000//
program crashed with the following error :PoC
To Run
Impact
The running Go process crashes
The bugs were found while fuzzing the target using go-fuzz.
The text was updated successfully, but these errors were encountered: