Skip to content

brainproxy 0.6.1

Choose a tag to compare

@github-actions github-actions released this 08 Nov 16:37
· 322 commits to main since this release

brainproxy 0.6.1

Fixes for 0.6.0, plus a scope check on the Host header, a record of who changed what, and every scan request written down before it goes out.

Update if you use 0.6.0 reports: 0.6.0 printed the decoded password of an HTTP Basic Authorization header in every report that included the finding about it. 0.6.1 masks it. Regenerate any report made with 0.6.0 that you have shared or kept.

Schema change (v17 → v19): a project opened with 0.6.1 can't be opened by 0.6.0 again. Keep a copy if you need to go back.

Changed: check these before updating scripts or CI

  • SARIF fingerprints are brainproxy/v3 (#103). Path parameters such as ;jsessionid= no longer make a new finding per session. The first upload after updating may show existing alerts as closed and reopened.
  • Issues have hosts (#103): an issue merged across hosts lists them all; host stays for the first.
  • Risk can go down (#103): a rescan that sees a finding at a lower risk lowers it, and the timeline records the change.
  • The Host header is checked against scope (#83). A request whose Host, :authority or absolute URL names a host outside scope is refused, wherever it comes from: send, fuzz, scans, logins, macros, proxy rules. Header values with a line break or NUL are refused for everyone.
    • Host header tests are still possible: pass --host-header-test (send, fuzz, scan active, auth login/status, macro run, rules add/enable), and the request goes out with a warning.
    • A proxy rule added by an agent without the flag that would put a foreign host on a request gets a 502 instead.
    • With an IP address or range in scope, any name that resolves to it is in scope. See Scope in the manual.
  • More is refused through MCP (#102): --force on report, ca export, ca init and findings repro; report-profile save over an existing layout; report-profile remove is not a tool.
  • Every scan request is recorded before it is sent (#85): crawls, active scans, authz, fuzz --store all and callbacks. A stopped or crashed run keeps what it sent. Active scans now keep every attack request by default, so projects grow faster.
    • To keep only the attack requests that back a finding, turn on scan prune on (or Keep only attack requests that back a finding in the app's New scan), or pass scan active --prune for one scan. Pruning runs when the scan ends or is stopped, and never deletes the requests the scan started from or anything a finding, note or tag points to. Through MCP, pruning can't be turned on: an agent's scan always keeps everything.

New

  • --mask on report and findings repro (#101): masks extra values you name (at least 6 characters). Not with --no-redact.
  • Provenance (#84): who changed an auth profile, session rule or macro (edited_by), who started a job, fuzz run, authz run, WebSocket or callback payload, and a log of setting changes. proxy status says when a running proxy is older than the project's rules.
  • Delete a project from the app (#104).

Fixed

  • Redaction (#101): overlapping secrets no longer leave a tail; the unsigned half of a signed cookie is masked; titles, company, scope, filters and host lists are scrubbed too; masking happens before a body is cut.
  • The script signer's memory limit now also works on macOS and Windows (#65).
  • Nuclei checks run about twice as fast (#87).
  • ZAP data synced with upstream (#64).
  • The app stops the proxy it started when you close a project, also without auto-start (#68).
  • Scan depth times in the wizard are rough ranges now: quick 5 to 10 minutes, standard around an hour, thorough several hours depending on the site's size (#69).
  • Findings bookkeeping (#100): marking a finding with the state it already has no longer records a change, and a retest that finds it still present no longer counts twice in the passive scan.

Thanks to @L1ghtn1ng for #103 and #104.