Hacker Newsnew | past | comments | ask | show | jobs | submit | bugfinder's commentslogin

Hey HN! Co-founder here. Over the past year we’ve been developing a new fuzzer for web JSON APIs. Today, we're launching a free plan with up to 50 free scans per month so that solo devs and small teams, which don't often have a ton of budget, can test their APIs.

To give a bit of background, a fuzzer generates random inputs and sends them to the application being tested. The fuzzer monitors the application to detect crashes. Fuzzing has been super helpful at finding bugs and security vulnerabilities, especially in memory unsafe code. libfuzzer and syzkaller are two projects that are good examples of what fuzzing can do.

We've been applying some of those fuzzing concepts to web APIs. We start from a specification (OpenAPI, Swagger, Postman, or even a HAR file) as a loose grammar to generate an infinite stream of requests that we send to the API being tested. The fuzzer uses API responses to generate better requests, and to detect bugs and security vulnerabilities. This is a DAST, for those familiar with that terminology. Mayhem for API has been really good at finding internal server errors and API crashes. And we've been adding more and more security checks (SQL injection, command injection, auth bypass, SSRF, path traversal).

We’ve been developing the fuzzer from scratch using Rust. Our experience with Rust has been phenomenal, and we can't recommend it enough. Rust has enabled us to move quickly & fearlessly. It makes it a lot easier to build fault-tolerant systems compared to previous systems I've built in dynamic languages, thanks to the strong typing & explicit errors in return types. Happy to chat about using Rust if you have any questions!

Our product is still pretty early, and we're actively working on making it better. Our goal is to help automate some of the API non-functional and security testing as part of CI, since we know it's hard for testing to keep up with the speed of development. I would love to hear what HN thinks, and if this fuzzer could help you in any way!

As an aside since this is HN, if you're looking for an open-source alternative, check out RESTler from Microsoft and ZAP from OWASP, which are both awesome projects. We believe our fuzzing engine is better in terms of performance and being able to exercise more API endpoints automatically, but ours is not open source.


ForAllSecure | Senior or Staff Rust Backend Engineer | Remote (US/Canada)| Full Time

ForAllSecure helps companies fuzz their code to find security & reliability issues. Our claim to fame was winning the DARPA Cyber Grand Challenge back in 2016. We are launching a new product targeting web APIs.

You will join a small team passionate about API testing. We believe that there is a better way to develop and test web APIs, and that fuzzing is part of the solution. We are driven to deliver that and help out all the API developers out there.

We are building everything but the frontend in Rust: our custom fuzzer, our web service, our CLI. It's been a blast!

We have offices in Palo Alto, CA & Pittsburgh PA, and many remote folks across the US and Canada.

You can apply through the job posting at https://boards.greenhouse.io/forallsecure/jobs/5086295002 or DM me.


Mayhem changed quite a bit since the publication of the paper. It now reports all crashes, and therefore bugs are not necessarily security critical.


The paper has been published a while ago. We have been improving Mayhem quite a bit since then, and we recently ran it on debian binaries. It found many crashes, that are not necessarily exploits. 1.2K is the number of bug reports we are going to submit to the Debian bug tracker.


As a long time Debian user I would like to thank you for choosing Debian as a target platform. The maintainers might not appreciate the bugs in the short term but in the long term this is great for everyone involved. Was there any reason why you chose Debian? I imagine bts made things easier for bug wrangling/submission.


The response has been fairly positive in general, and it's great to see that some of the bugs have already been fixed!

All Mayhem developers are using Debian, and our cluster is running Debian as well. We've been using it happily for years. That's why we chose to analyze it first. I believe we will also have an impact on other distributions since bugs are getting fixed upstream.


Thanks for the great work!

Do you plan to release the tool one day? It will be a great asset to other operating systems developers as well.


Having received one of the bugs (that was not exploitable), I appreciated it in the short term. :P

I hope a free version of this can be built, it would be a nice additional QA step to run before release.


I see that it is for moreutils. I am having the hardest time using the interface for forallsecure.com. It seems that you can not search by package. When I browsed through the list I figured I would have come across moreutils around page 49/51 but I did not see it. I am tempted to download:

  http://forallsecure.com/programs/1  
  ...
  http://forallsecure.com/programs/22630
But that seems like a waste of everyone's resources. What was the bug?

For people unfamiliar with joeyh's contribution to Debian it is important to note that he is a legendary DD:

http://qa.debian.org/developer.php?login=joeyh%40debian.org


Our interface is severely lacking. The website is mostly for internal use at the moment. I'll try to add a program search tonight to make it more usable.

As a matter of fact, most programs are not linked to packages, and most packages are not present, including moreutils. You won't find it even by crawling.


No worries. I will choose helping Debian over interface improvements anyday:) Again, thanks for choosing Debian.


Actually, I have not received the one for moreutils yet.

However, we got 1 report for the Debian Installer, which I hope means only 1 problem was found.. which is nice, as the d-i code is mostly not written with this kind of robustness in mind.


I read the mailing list post as the authors willingly restricted the number of reported bugs to one to avoid spamming the BTS.


Since d-i is split into a ton of components, we know that all but 1 of them had 0 bugs found.


44 reports got delayed, including the one for moreutils. It should be in your mailbox now.


I see. Thanks for the response. Also, thanks for choosing Debian and not some other closed source software.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: