Skip to content

brainproxy 0.5.1

Choose a tag to compare

@github-actions github-actions released this 05 Nov 13:30
· 377 commits to main since this release

brainproxy 0.5.1

This release fixes recorded logins that never counted as logged in. It adds HQL injection scanning and makes the time-based SQL injection payloads actually wait. An agent working through MCP can no longer change what the proxy records, or where your traffic goes, without it showing.

No schema change: 0.5.0 still opens projects saved by this version.

Fixed

  • Recorded logins judged as failed. A recorded login used "the page has a password field" to tell when you were logged out. A logged-in page with a change-password form matched that, so every login, though it worked, was reported as failed ("logged-out pattern matched after login") and retried.
    • Recording now picks a sign that is on the login page and on none of the pages after it: any password field, the login form's own field by name, or the form that posts to the login.
    • The logged-in page can now be the check page even with a password field on it.
    • Profiles recorded before this release keep their old pattern: record the login again, or change the profile's "Logged out" pattern in Settings.
  • sqli-time payloads now wait 5 seconds. 31 of them sent the placeholder __TIME__ as it was, so they could never slow a response. The list's header line, which was also being sent as a payload, is gone (41 payloads).
  • GitHub's download limit. When GitHub's hourly limit for API requests without login is used up, checks update and scan data update now say so and when it resets, instead of a bare "HTTP 403". A full 40-character commit id given as --ref needs no API request.

New

  • HQL injection rule (100003). It finds input built into Hibernate HQL or JPQL queries (EclipseLink, OpenJPA).
    • A random dotted path that only the ORM's query parser reports as unknown confirms it, with high confidence, and the finding names the entity.
    • Otherwise it looks for a new query parser error (medium confidence).
    • 3, 6 or 9 requests per parameter, by strength.
    • The SQL injection rule (40018) no longer reports Hibernate's "unexpected token" parser error as "SQL Injection - Hypersonic SQL".
  • Traffic outside the recording scope still leaves a row (#91, @L1ghtn1ng). Plain HTTP gets a row with its request line; an HTTPS tunnel gets a CONNECT row, written when it opens, so a proxy that is killed still leaves it.
  • Changes to what the proxy records, and to where traffic goes, are logged with who made them. That covers the recording scope, the TLS pass-through list, upstream proxies, host overrides and client certificates (scope show, proxy status, Target › Scope).
    • Narrowing recording: an agent doing it through MCP shows a "Recording narrowed by an agent" warning.
    • Changing routing: an agent doing it shows a "Routing changed by an agent" warning.
    • Clearing a warning: it stays until a person changes that setting or keeps it as it is. Keeping a routing change is the new connection review, which an agent can't run.
    • Keeping the log: an agent's changes stay in the log however many follow; a flood of them is capped at 5,000 and counted.
  • Proxy restarts that are killed partway no longer leave the proxy off (#89, @L1ghtn1ng). If the restart dies partway through, a small background process puts the old proxy back, and proxy status says so. The app keeps track of the proxy it brought back.
  • --sni is checked before connecting (#90, @L1ghtn1ng), and recorded with each request. A refused name leaves no row claiming it was sent.

Changed: opt-ins for requests that can change data

  • A request now needs its method and MUTATION separately. A GraphQL mutation sent as POST to authz run needs --include-methods POST,MUTATION, where MUTATION alone used to be enough. A DELETE that names a persisted query needs DELETE and MUTATION. The app passes both after asking you. Scripts that pass only MUTATION to authz run will now be refused.
  • More GraphQL operations count as mutations, since they can't be shown to be read-only:
    • persisted queries (a hash instead of the query) and Relay doc_id;
    • multipart uploads and form-encoded queries;
    • bodies that can't be decoded;
    • application/graphql+json bodies.
  • authz run --url needs the same opt-in as a request named from history.
  • import api now treats a GraphQL mutation in a Postman collection's body as one.

Other

  • brainproxy capabilities lists 145 commands (new: connection review).
  • Dependencies: tauri-plugin-dialog 2.8.4, @types/node 26.6.6.

Thanks to @L1ghtn1ng for #89, #90 and #91.