Open
Conversation
Codecov Report❌ Patch coverage is Additional details and impacted files@@ Coverage Diff @@
## dev #2007 +/- ##
=======================================
- Coverage 92% 92% -0%
=======================================
Files 416 438 +22
Lines 34690 36026 +1336
=======================================
+ Hits 31644 32810 +1166
- Misses 3046 3216 +170 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
5cb7f10 to
1a36dae
Compare
…ements BBOT server improvements
…ements BBOT server improvements
…ements Pydantic updates
Memory Optimizations
Fix Parrot distro test failures caused by stale mirror
…reduce Reduce padding oracle false positives in lightfuzz crypto module
…-interactsh-fix Add lightfuzz SSRF submodule, fix interactsh issues
…is-a-real-boy-now Make user_agent_suffix a proper config value
…ization-fp-fix Fix lightfuzz deserialization Error Resolution false positives
…-fix Attribute verified URL stats to discovering module instead of httpx
…-pending (Hopefully) Improving Task Cleanup
Update lightfuzz docs for 3.0
Move legba module out of deadly folder
…ction Filter duplicate JWT detection in badsecrets
…tions Improve azure functions
…actions/dev/github-actions-674967a53d Bump actions/upload-artifact from 6 to 7 in the github-actions group
Fix double-request bug in pgp module
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
BBOT 3.0 "
blazed_elijah" contains changes needed to store BBOT data in a persistent database. The idea is to release it alongside BBOT server, a tiny CLI-only database. This will be paired with a series of blog posts showing how BBOT server can be used on the command line to script out bug bounty hunting, threat intel, and ASM (i.e. running scheduled scans, exporting to CSV, diffing results over time, etc.).Together, BBOT 3.0 and BBOT server will give us a solid foundation to build a bunch of other useful tooling, like asset inventory. Sometime in the future, it may also be useful to frontend.
Breaking changes
1.
.dataand.data_jsonevent fieldsThe main breaking change in BBOT 3.0 is that the name of the
.datafield is different based on whether it's astrordict..data: string.data_json: dictionaryThe
siem_friendlyoption has been removed, since BBOT data is now SIEM-friendly by default.2. Changes to vulnerabilities
The
VULNERABILITYevent type has been removed in favor ofFINDING, which now has several improvements:namefield which holds a generic description common to all findings of the same type. This makes it easier to collapse and categorize them.confidencefieldseverityfieldFeatures
Potential changes