Ecosyste.ms: Awesome

An open API service indexing awesome lists of open source software.

Awesome Lists | Featured Topics | Projects

https://github.com/aress31/openapi-parser

Parse OpenAPI documents into Burp Suite for automating OpenAPI-based APIs security assessments (approved by PortSwigger for inclusion in their official BApp Store).
https://github.com/aress31/openapi-parser

burp-extensions burp-plugin burpsuite json openapi openapi-client openapi-specification openapi2 openapi3 parser pentesting restful-api swagger yaml

Last synced: 28 days ago
JSON representation

Parse OpenAPI documents into Burp Suite for automating OpenAPI-based APIs security assessments (approved by PortSwigger for inclusion in their official BApp Store).

Awesome Lists containing this project

README 

        
# openapi-parser



[![Java CI with Gradle](https://github.com/aress31/openapi-parser/actions/workflows/gradle-build.yml/badge.svg)](https://github.com/aress31/openapi-parser/actions/workflows/gradle-build.yml)

bapp store

lang

license

version



> [!UPDATE]

> This extension has been updated to use the latest [Burp Montoya Java API](https://portswigger.github.io/burp-extensions-montoya-api/javadoc/burp/api/montoya/package-summary.html). The extension has undergone a complete overhaul to improve both its `UI`/`UX` and performance. These changes ensure that the extension is modern and optimised for use.



## openapi-parser is a `Burp Suite` extension designed for `OpenAPI`-based `API` testing



> The `OpenAPI` Specification (`OAS`) defines a standard, programming language-agnostic interface description for `REST` `APIs`, which allows both humans and computers to discover and understand the capabilities of a service without requiring access to source code, additional documentation, or inspection of network traffic. When properly defined via `OpenAPI`, a consumer can understand and interact with the remote service with a minimal amount of implementation logic. Similar to what interface descriptions have done for lower-level programming, the `OpenAPI` Specification removes guesswork in calling a service.

>

> Use cases for machine-readable `API` definition documents include, but are not limited to: interactive documentation; code generation for documentation, clients, and servers; and automation of test cases. `OpenAPI` documents describe an `API`'s services and are represented in either `YAML` or `JSON` formats. These documents may either be produced and served statically or be generated dynamically from an application.

>

> \- [`OpenAPI` Initiative](https://github.com/OAI/`OpenAPI`-Specification)



Performing security assessment of `OpenAPI`-based `APIs` can be a tedious task due to `Burp Suite` (industry standard) lacking native `OpenAPI` parsing capabilities. A solution to this situation, is to use third-party tools (e.g. `SOAP-UI`) or to implement custom scripts (often on a per engagement basis) to handle the parsing of `OpenAPI` documents and integrate/chain the results to `Burp Suite` to use its first class scanning capabilities.



openapi-parser is an `OpenAPI` parser that aims to streamline this entire process by allowing security professionals to use `Burp Suite` as a standalone tool for security assessment of `OpenAPI`-based `APIs`.



## Features



- `OpenAPI` documents can be parsed either from a supplied file or URL. The extension can fetch `OpenAPI` documents directly from a URL using the `Send to Swagger Parser` feature under the `Target -> Site map` context menu.

- Parse `OpenAPI` documents, formerly known as the `Swagger specification`, fully compliant with `OpenAPI` 2.0/3.0 Specifications (`OAS`).

- Requests can be directly viewed/edited within the extension prior to sending them to other Burp tools.

- Requests can be sent to the `Comparer`, `Intruder`, `Organizer`, `Repeater`, `Scanner`, `Site map` and `Scope` Burp tools.

- Requests matching specific criterias (detailed in the 'Parameters' tab) can be intercepted to automatically match and replace the parsed parameters default values defined in the 'Parameters' tab. This feature allows for fine-tuning of the requests prior to sending them to other Burp tools (e.g., scanner). Edited requests can be viewed within the 'Modified Request (`OpenAPI` Parser)' tab of Burp's message editor.

- Row highlighting allowing pentesters to highlight "interesting" `API` calls and/or colour code them for reporting purposes.

- Includes an export to `CSV` feature, allowing users to easily export selected `API` requests in `CSV` format for further analysis or reporting.

- Supports both `JSON` and `YAML` formats.



## Requirements



### 1. System requirements



- Operating System: Compatible with `Linux`, `macOS`, and `Windows` operating systems.

- Java Development Kit (JDK): `Version 11` or later.

- Burp Suite Professional or Community Edition: `Version 2023.11.1.3` or later.



  > [!IMPORTANT]

  > Please note that using any version lower than `2023.3.2` may result in a [java.lang.NoSuchMethodError](https://forum.portswigger.net/thread/montoya-api-nosuchmethoderror-275048be). It is crucial to use the specified version or a more recent one to avoid this issue.



### 2. Build tool



- Gradle: `Version 8.5` or later (recommended). The [build.gradle](https://github.com/aress31/openapi-parser/blob/main/lib/build.gradle) file is provided in the project repository.



### 3. Environment variables



- Set up the `JAVA_HOME` environment variable to point to the `JDK` installation directory.



Please ensure that all system requirements, including a compatible version of `Burp Suite`, are met before building and running the project. Note that the project's external dependencies will be automatically managed and installed by `Gradle` during the build process. Adhering to the requirements will help avoid potential issues and reduce the need for opening new issues in the project repository.



## Installation



### 1. Compilation



1. Ensure you have [Gradle](https://gradle.org/) installed and configured.



2. Download the `openapi-parser` repository:



   ```bash

   git clone https://github.com/aress31/openapi-parser

   cd .\openapi-parser\

   ```



3. Build the standalone `jar`:



   ```bash

   ./gradlew fatJar

   ```



### 2. Loading the Extension Into `Burp Suite`



To install `openapi-parser` in `Burp Suite`, first go to the `Extensions` tab and click on the `Add` button. Then, select the `openapi-parser-all` jar file located in the `.\build\libs` folder to load the extension.



Alternatively, you can skip the [Compilation](#1-compilation) step entirely and download the extension directly from the [BApp Store](https://portswigger.net/bappstore/6bf7574b632847faaaa4eb5e42f1757c).



_Note: The version distributed on the [BApp Store](https://portswigger.net/bappstore/6bf7574b632847faaaa4eb5e42f1757c) might be lagging behind the version available on this repository._



## Roadmap



- [ ] Beautify the graphical user interface.

- [ ] Deep parsing of `OpenAPI` schemas to collect all nested parameters along with their example/type.

- [ ] Code simplification/refactoring.

  - [x] Use `MyHttpRequest` instead of `RequestWithMetadata`.

- [x] Enable cells editing to change `API` calls directly from the `GUI`.

- [ ] Fix the custom request editor tab to work properly with intercepted requests based on the match and replace rulesets.

- [x] Further optimise the source code.

- [ ] Implement support for authenticated testing (via user-supplied `API`-keys).

- [x] Improve the `Param` column by adding parameters type (e.g. `inquery`, `inbody`).

- [x] Improve the tables and context menus.

- [x] Increase the extension verbosity (via the bottom panel).



See [TODO](TODO.md) for additional outstanding tasks.



## Project Information



In July 2016, after posting a request for improvement on the [PortSwigger support forum](https://support.portswigger.net/customer/portal/questions/16358278-swagger-parser-and-wsdler-improvement), I decided to take the initiative and to implement a solution myself.



The extension is still in development, feedback, comments and contributions are therefore much appreciated.



## Sponsor 💖



If this extension has saved you time and hassle during a security assessment, consider showing some love by sponsoring a cup of coffee ☕ for the developer. It's the fuel that powers development, after all. Just hit that shiny `Sponsor` button at the top of the page or [click here](https://github.com/sponsors/aress31) to contribute and keep the caffeine flowing. 💸



## Reporting Issues



Did you find a bug? Well, don't just let it crawl around! Let's squash it together like a couple of bug whisperers! 🐛💪



Please report any issues on the [GitHub issues tracker](https://github.com/aress31/openapi-parser/issues). Together, we'll make this extension as reliable as a cockroach surviving a nuclear apocalypse! 🚀



## Contributing



Looking to make a splash with your mad coding skills? 💻



Awesome! Contributions are welcome and greatly appreciated. Please submit all PRs on the [GitHub pull requests tracker](https://github.com/aress31/openapi-parser/pulls). Together we can make this extension even more amazing! 🚀



## License



See [LICENSE](LICENSE).