shah keval

Security Analyst #Instrumentation #Fuzzing
Interested in #IAST & #SAST

[shah keval @iHttpOnly]

By that logic, listening with a stethoscope is better than an X-ray.

[s1r1us @S1r1u5_]

😐 what does that even mean?

[shah keval @iHttpOnly]

@win3zz @Cuberks Best wishes bipin...

[shah keval @iHttpOnly]

CISA has published advisory on which i have done research. My first research on ICS security and 3rd CVE.
Found security issue in inductive automation ignition using #Instrumentation(#IAST , #SAST) (one of the key target in pwn2own ICS)

[ICS-CERT @ICSCERT]

🛑 @CISAgov issued public advisory ICSA-22-207-01 Inductive #Automation Ignition to the ICS webpage: https://t.co/RhucydCz4k #cyber #cybersecurity #infosec #ICS

[/r/netsec @_r_netsec]

From fuzzing to remote code execution in Samsung Android https://t.co/xxwt3oPAGo

[44CON @44CON]

Fuzzing npm/nodejs WebAssembly parsing library with jsfuzz https://t.co/d7936ZGLpx #fuzzing #javascript

[Patrick Ventuzelo @Pat_Ventuzelo]

🎉 New #fuzzing blogpost :)

Quick blogpost about how I found a OOM/DoS bug in a famous @npmjs/@nodejs package using coverage-guided #javascript fuzzer.

➡️ Fuzzer: Jsfuzz by @fuzzitdev
➡️ Target: wasm-parser
➡️ Bug: DoS/OOM

https://t.co/KUrXcUVI64

#WeAssembly #js #wasm #NodeJS

[GitHub Security Lab @GHSecurityLab]

Check out @Nosoynadiemas ' tips on Fuzzing, to overcome known challenges and maximize results: https://t.co/g5iGRj3qp6

[MicrosVuln @microsvuln]

Fuzzing software: common challenges and potential solutions (Part 1) https://t.co/PB7oMetgKl #fuzzing #exploitation

[Patrick Ventuzelo @Pat_Ventuzelo]

🎉 First #wasm security blogpost of 2020 🎉

Some people ask me, so here is how to start fuzzing #WebAssembly APIs of #browser JavaScript engines like Chrome/V8.

In this blogpost, I'm using:
✅ Dharma/Domato
✅ Chrome/v8 ASan pre-built
✅ Honggfuzz ;)

https://t.co/vnKMnbiFGD

[shah keval @iHttpOnly]

#2020goals Start working on previous 3 year's goal.🤔🤷🏻‍♂️😆

[Jiliac @Jilyac]

We made a website which shows a genealogy of fuzzers: https://t.co/16WVvzkKAE
Basically, this is a fork from the one we have in the survey, but which we can keep up-to-date and where anyone can contribute at: https://t.co/eTh8pbRFjV

[The Hacker's Choice (@[email protected]) @hackerschoice]

afl++ 2.59c was released: https://t.co/3KX6MINcv1 - new: radamsa, qbdi fuzzing, python3, llvm10, more *BSD and Android support and many more things :) #fuzzing #fuzzer #afl

[Programming Wisdom @CodeWisdom]

"Documentation is a love letter that you write to your future self." - Damian Conway

[MicrosVuln @microsvuln]

Guided Fuzzing with Driller

https://t.co/5MWFc189Dt

#CGC #Driller #Shellphish #AFL #symbolic_AFL_fuzzing #shellphuzz

[Dmitry Vyukov @dvyukov]

Nice to see fuzzing tutorials. Esp from companies like @gitlab. Esp about continuous setup with automatic issue filing:
https://t.co/DifL7B3U5n
Such continuous fuzzing integrated into dev process is the next big shift in testing, currently in early adopter phase.

[Programming Wisdom @CodeWisdom]

"Debuggers don't remove bugs. They only show them in slow motion." - Unknown

[Unicorn Engine @unicorn_engine]

A nice paper on using Unicorn+AFL to fuzz arbitrary parsers in OS kernel, without requiring kernel source code.

https://t.co/s0LivoLMl6

Tool: https://t.co/y6f5zZihlY

[Programming Wisdom @CodeWisdom]

"If at first you don’t succeed, call it version 1.0." ― Unknown