Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/owasp-dep-scan/blint
BLint is a Binary Linter to check the security properties, and capabilities in your executables. Since v2, blint is also an SBOM generator for binaries.
https://github.com/owasp-dep-scan/blint
binary cyclonedx depscan fuzzing malware sbom supply-chain-analytics supply-chain-security
Last synced: 3 months ago
JSON representation
BLint is a Binary Linter to check the security properties, and capabilities in your executables. Since v2, blint is also an SBOM generator for binaries.
- Host: GitHub
- URL: https://github.com/owasp-dep-scan/blint
- Owner: owasp-dep-scan
- License: mit
- Created: 2023-01-21T15:42:23.000Z (almost 2 years ago)
- Default Branch: main
- Last Pushed: 2024-07-31T21:16:54.000Z (3 months ago)
- Last Synced: 2024-08-02T00:38:16.916Z (3 months ago)
- Topics: binary, cyclonedx, depscan, fuzzing, malware, sbom, supply-chain-analytics, supply-chain-security
- Language: Python
- Homepage:
- Size: 1.56 MB
- Stars: 320
- Watchers: 7
- Forks: 32
- Open Issues: 36
-
Metadata Files:
- Readme: README.md
- Funding: .github/FUNDING.yml
- License: LICENSE
Awesome Lists containing this project
- awesome-software-supply-chain-security - AppThreat/blint: BLint is a Binary Linter to check the security properties, and capabilities in your executables. It is powered by lief.
README
# BLint
BLint is a Binary Linter that checks the security properties and capabilities of your executables. It is powered by [lief](https://github.com/lief-project/LIEF). Since version 2, blint can also generate Software Bill-of-Materials (SBOM) for supported binaries.
[](https://asciinema.org/a/438138)
Supported binary formats:
- Android (apk, aab)
- ELF (GNU, musl)
- PE (exe, dll)
- Mach-O (x64, arm64)
You can run blint on Linux, Windows, and Mac against any of these binary formats.
## Motivation
Nowadays, vendors distribute statically linked binaries produced by Golang, Rust, or Dotnet tooling. Users are used to running antivirus and anti-malware scans while using these binaries in their local devices. Blint augments these scans by listing the technical capabilities of a binary. For example, whether the binary could use network connections or can perform file system operations and so on.
The binary is first parsed using the lief framework to identify the various properties, such as functions and the presence of symtab and dynamic symbols. Thanks to YAML-based annotation data, this information can be matched against capabilities and presented visually using a rich table.
NOTE: The presence of capabilities doesn't imply that the binary always performs the operations. Use the output of this tool to get an idea about a binary. Also, this tool is not suitable for reviewing malware and other heavily obfuscated binaries for obvious reasons.
## Use cases
- Quickly identify malicious binaries by looking at their capabilities (Ability to manipulate networks or drivers or kernels etc)
- Add blint to CI/CD to inspect the final binaries to ensure code signing or authenticode is applied correctly
- Identify interesting functions and symbols for fuzzing
## Installation
- Install python 3.10, 3.11, or 3.12
```bash
pip install blint
```
### Single binary releases
You can download single binary builds from the [blint-bin releases](https://github.com/OWASP-dep-scan/blint/releases). These executables should work without requiring python to be installed. The macOS .pkg file is signed with a valid developer account.
## Usage
```shell
usage: blint [-h] [-i SRC_DIR_IMAGE [SRC_DIR_IMAGE ...]] [-o REPORTS_DIR] [--no-error] [--no-banner]
[--no-reviews] [--suggest-fuzzable]
{sbom} ...
Binary linter and SBOM generator.
options:
-h, --help show this help message and exit
-i SRC_DIR_IMAGE [SRC_DIR_IMAGE ...], --src SRC_DIR_IMAGE [SRC_DIR_IMAGE ...]
Source directories, container images or binary files. Defaults to current directory.
-o REPORTS_DIR, --reports REPORTS_DIR
Reports directory. Defaults to reports.
--no-error Continue on error to prevent build from breaking.
--no-banner Do not display banner.
--no-reviews Do not perform method reviews.
--suggest-fuzzable Suggest functions and symbols for fuzzing based on a dictionary.
sub-commands:
Additional sub-commands
{sbom}
sbom Command to generate SBOM for supported binaries.
```
### SBOM sub-command
```shell
usage: blint sbom [-h] [-i SRC_DIR_IMAGE [SRC_DIR_IMAGE ...]] [-o SBOM_OUTPUT] [--deep]
options:
-h, --help show this help message and exit
-i SRC_DIR_IMAGE [SRC_DIR_IMAGE ...], --src SRC_DIR_IMAGE [SRC_DIR_IMAGE ...]
Source directories, container images or binary files. Defaults to current directory.
-o SBOM_OUTPUT, --output-file SBOM_OUTPUT
SBOM output file. Defaults to bom.json in current directory.
--deep Enable deep mode to collect more used symbols and modules aggressively. Slow
operation.
--stdout Print the SBOM to stdout instead of a file.
```
To test any binary, including default commands
```bash
blint -i /bin/netstat -o /tmp/blint
```
Use -i to check any other binary. For eg: to check ngrok
```bash
blint -i ~/ngrok -o /tmp/blint
```
Pass `--suggest-fuzzable` to get suggestions for fuzzing. A dictionary containing "common verbs" is used to identify these functions.
```bash
blint -i ~/ngrok -o /tmp/blint --suggest-fuzzable
```
To generate SBOM in [CycloneDX format](https://cyclonedx.org/) for supported binaries, use the sbom sub-command.
```shell
blint sbom -i /path/to/apk -o bom.json
```
```shell
blint sbom -i /directory/with/apk/aab -o bom.json
```
To parse all files, including `.dex` files, pass `--deep` argument.
```shell
blint sbom -i /path/to/apk -o bom.json --deep
```
The following binaries are supported:
- Android (apk/aab)
- Dotnet executable binaries
- Go binaries
- Rust binaries
```shell
blint sbom -i /path/to/go-binaries -o bom.json --deep
```
For all other binaries, the symbols will be collected and represented as properties with `internal` prefixes for the parent component. Child components and dependencies would be missing.
PowerShell example
## Reports
Blint produces the following json artifacts in the reports directory:
- blint-output.html - HTML output from the console logs
- exename-metadata.json - Raw metadata about the parsed binary. Includes symbols, functions, and signature information
- findings.json - Contains information from the security properties audit. Useful for CI/CD integrations
- reviews.json - Contains information from the capability reviews. Useful for further analysis
- fuzzables.json - Contains a suggested list of methods for fuzzing
sbom command generates CycloneDX json.
## References
- [lief examples](https://github.com/lief-project/LIEF/tree/master/examples)
- [checksec](https://github.com/Wenzel/checksec.py)
## Discord support
The developers can be reached via the [Discord](https://discord.gg/DCNxzaeUpd) channel.
## Sponsorship wishlist
If you love blint, you should consider [donating](https://owasp.org/donate?reponame=www-project-dep-scan&title=OWASP+dep-scan) to our project. In addition, consider donating to the below projects, which make blint possible.
- [LIEF](https://github.com/sponsors/lief-project/)