openapi-fuzzer
restler-fuzzer
| openapi-fuzzer | restler-fuzzer | |
|---|---|---|
| 4 | 15 | |
| 515 | 2,466 | |
| - | 1.1% | |
| 6.8 | 7.3 | |
| 3 months ago | 16 days ago | |
| Rust | Python | |
| GNU Affero General Public License v3.0 | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
openapi-fuzzer
-
Hey Rustaceans! Got a question? Ask here! (32/2022)!
Hi, I'm working on a fuzzer, that fuzzes APIs based on OpenAPI specification. I'd like to implement shrinking. It means that when an interesting input (for the API) is found, I'd like to create the smallest possible input that still causes the same behaviour of the API. I'd like to implement a payload generation via proptest, because it already has the shrinking ability. I'm having issues implementing the JSON object as a proptest strategy. Here is what I tried so far. I explained it in a detail in stackoverflow question but it did not reach many people. Thanks for your help!
-
Show HN: OpenAPI fuzzer – fuzzing APIs based on OpenAPI specification
Thanks for the report. However, without more information I'm not able to help you. What is your setup? How did you run it? could you please share the specification file? Also, let's probably move this discussion to GitHub issues: https://github.com/matusf/openapi-fuzzer/issues
restler-fuzzer
- Protegendo APIs da Esquerda para a Direita (e em td no meio do caminho) [Tradução +/- Comentada]
-
Machine Learning Helps Fuzzing Find Hardware Bugs
It is popular in domains where it’s effective but it’s not as useful when it’s hard to know if an output is correct. I know several tools which fuzz mobile app UIs to see if you can cause crashes or irrecoverable states with random inputs because those are easy to detect, but beyond that you start needing to have more traditional QA approaches to say whether the resulting state is correct.
One area which is very interesting is the use of OpenAPI schemas to help with APIs since you can use the schemas to guide generation and validation. It’s non-trivial to do with authentication but I found this project of interest:
https://github.com/microsoft/restler-fuzzer
- RESTler is a stateful REST API fuzzing tool
- RESTler: Stateful REST API fuzzing tool
- GitHub - microsoft/restler-fuzzer: RESTler is the first stateful REST API fuzzing tool for automatically testing cloud services
- RESTler API fuzzing is now on Github (finally ?
-
Show HN: OpenAPI fuzzer – fuzzing APIs based on OpenAPI specification
There's another one here by Microsoft - this is cool though! great to see more Rust tools.
https://github.com/microsoft/restler-fuzzer
- Web app Fuzzing
-
I need some help building an API from github
once you install git, just do git clone https://github.com/microsoft/restler-fuzzer
What are some alternatives?
cats - CATS is a REST API Fuzzer and negative testing tool for OpenAPI endpoints. CATS automatically generates, runs and reports tests with minimum configuration and no coding effort. Tests are self-healing and do not require maintenance.
fuzzcheck-rs - Modular, structure-aware, and feedback-driven fuzzing engine for Rust functions
bachelor-thesis
openapiv3 - Rust Open API v3 Structs and Enums for easy deserialization with serde
benchling-rs - benchling client, generated from the OpenAPI spec
MeiliSearch - A lightning-fast search API that fits effortlessly into your apps, websites, and workflow
openapi-yup-generator - CLI tool for generating yup definitions from openapi3.yaml
bananafzz - Banana Fuzzer ~ modulable, loop based, poc gen, code cov, platform agnostic, race oriented
tokio - A runtime for writing reliable asynchronous applications with Rust. Provides I/O, networking, scheduling, timers, ...