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
Love the npl tool, I think it's super creative and really easy to use.
Brief Summary
While I was using the tool I had my fuzzer running in the background and came across a local/remote crash (DoS condition) as a result of slightly malformed input. Running the tool as a daemon/service (via inetd or some other means) would cause it to crash for all users accessing npl. The issue comes from invoking the SET_CAR function on an Atom when the input is malformed.
Reproduction
I've attached the input for reproduction purposes. After running npl against the input you can see following the GDB trace:
./npl -s ./input_file
Below is the hex dump of the input file:
A similar process could be repeated for GET_CAR files.zip
The text was updated successfully, but these errors were encountered:
Hi!
Love the npl tool, I think it's super creative and really easy to use.
Brief Summary
While I was using the tool I had my fuzzer running in the background and came across a local/remote crash (DoS condition) as a result of slightly malformed input. Running the tool as a daemon/service (via inetd or some other means) would cause it to crash for all users accessing npl. The issue comes from invoking the SET_CAR function on an Atom when the input is malformed.
Reproduction
I've attached the input for reproduction purposes. After running npl against the input you can see following the GDB trace:
Below is the hex dump of the input file:
A similar process could be repeated for GET_CAR
files.zip
The text was updated successfully, but these errors were encountered: