AI That Hunts Logic Bugs Before Attackers Do - Taylor Luttrell-Williams, Sonar
Loading slides…
Read the talk
AI That Hunts Logic Bugs Before Attackers Do
Taylor Luttrell introduces SonarQube Hunter Agent through a Python application whose findings include self-assigned admin access and an MFA bypass. The walkthrough connects repository-wide reasoning, specialist agents, validation, issue triage, and scheduled remediation.
From a talk by Taylor Luttrell-Williams
At a glance
Ideas worth remembering
Logic vulnerabilities can arise from relationships between otherwise working components: the demo's admin check trusts a role field that users can write themselves.
Hunter Agent maps the repository, feeds three specialist investigations, and applies adversarial validation and noise gates before surfacing findings in SonarQube.
The demonstrated Python scan took about an hour and returned 46 open findings, including self-assigned admin access and protected-route access without completing MFA.
Accepting a valid issue excludes it from quality-gate impact; confirming it lets it affect the gate. Detection and release blocking are separate decisions.
Scans support schedules and branch selection. Automatic, scheduled remediation is announced through SonarQube Remediation Agent, without a demonstrated fix in this recording.
When valid code violates the business rules
Code can work as written and still violate the application's security expectations. That is the gap Taylor Luttrell, who creates developer content at Sonar, introduces with SonarQube Hunter Agent. Traditional pattern-based static application security testing, or SAST, looks for recognizable problems in code. A logic vulnerability instead requires understanding whether the behavior makes sense under the application's business rules.
The distinction turns on intent: an operation may be technically valid while allowing a user to do something the application should forbid. Luttrell frames the urgency around faster, higher-volume agent-generated changes and attackers with stronger models. Periodic penetration tests—described here as occurring twice a year or quarterly in many companies—leave intervals in which those changes can introduce new vulnerabilities. Hunter Agent is presented as a way to investigate that class of problem more frequently.
Suggest correction
This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.
One repository map feeds three specialist investigations
Hunter Agent begins by mapping the repository globally. That map then supplies three specialist agents, one for each supported vulnerability class. Their task is to examine relationships among components and infer the security expectations those relationships should enforce. The shared map matters because a locally reasonable check can become unsafe when another part of the application controls the data it trusts.
A suspected issue must then survive adversarial validation. Noise gates also filter weak findings and behavior that appears intentional. The playbooks handle this orchestration and return issues with severity, impact, and a location where a developer can address the problem. Those issues appear alongside existing SAST findings in SonarQube, preserving the assignment and inspection workflow.
The slide illustrates how an investigation can span the repository. It marks leads in files including SessionManager.java, InvoiceController.java, and AccountRepository.java.
Shared context, separate specialist investigations
Read the diagram as text
- Repository. Source input to the investigation playbooks.
- Global repository map. Captures components and their relationships.
- Broken access control. specialists — Investigates authorization and privilege problems.
- Business logic. specialists — Investigates workflow and repeatable-action abuse.
- Authentication and sessions. specialists — Investigates login, session, and authentication gaps.
- Adversarial validation and noise gates. Checks candidate findings and filters weak or intentional behavior.
- SonarQube issues. Severity, impact, source location, and developer assignment.
- Repository → Global repository map: Maps globally.
- Global repository map → Broken access control: Supplies context.
- Global repository map → Business logic: Supplies context.
- Global repository map → Authentication and sessions: Supplies context.
- Broken access control → Adversarial validation and noise gates: Submits candidate findings.
- Business logic → Adversarial validation and noise gates: Submits candidate findings.
- Authentication and sessions → Adversarial validation and noise gates: Submits candidate findings.
- Adversarial validation and noise gates → SonarQube issues: Surfaces retained findings.
Suggest correction
This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.
Frontier reasoning joins the existing security layers
The talk announces Sonar joining the OpenAI Daybreak Cyber Partner Program, described as bringing governed access to advanced cybersecurity models into products such as Hunter Agent. The intended role is deeper reasoning inside the repository-wide playbooks: investigate leads, validate them before surfacing them, and produce findings that are precise, repeatable, and auditable.
Sonar recommends combining Hunter Agent with SAST and software composition analysis, or SCA, in the same platform. The existing scanners remain one layer; Hunter Agent adds investigation of contextual and logic-level failures. The recording supplies no comparative evaluation or precision and recall measurements, so its promises of comprehensive coverage and repeatable zero-day discovery remain product claims rather than demonstrated guarantees.
Suggest correction
This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.
An hour-long Python scan returns 46 open findings
The demonstration moves into a simple Python application in SonarQube Cloud. Under Hunter Agent, Scan Now estimates the number of units required for a deep, whole-codebase reasoning pass. The product also supports the self-hosted SonarQube Server. Scan duration depends on project size and complexity and can exceed an hour; this application's scan took about an hour, so the walkthrough uses an already completed run.
The scan first securely clones the repository to give the AI engine access to its source. Architecture analysis maps potential attack surfaces and builds a threat model. Contextual scans then investigate vulnerabilities, and findings from the specialist agents are aggregated and deduplicated into a unified list. Validated vulnerabilities are exported into SonarQube's issue list.
What does that run produce for a developer to inspect? Scan Results shows 46 open issues across broken access control, business logic, and authentication and session vulnerabilities. This is the output count for the demonstrated application, rather than a general detection-rate measure. The category breakdown separates different security expectations that the specialists investigate.
- Broken access control: The listed examples include insecure direct object references, or IDOR; missing or incorrect authorization checks; privilege escalation; sensitive data exposure; and cross-site request forgery. The central question is whether a user can reach data or actions they should not control.
- Business logic: Examples include skipping required workflow steps, abusing repeatable actions, and missing rate limits. Here the problem concerns allowed operations being performed in an unsafe order or quantity.
- Authentication and sessions: Examples include broken authentication, session fixation, non-expiring sessions, weak password recovery, missing multi-factor authentication, and brute-force gaps.
Opening the access-control category leads to the familiar SonarQube issues list. A high-severity finding carries both a Hunter Agent tag and its vulnerability-class tag. The integration lets developers inspect these results alongside other findings without moving into a separate dashboard.
Suggest correction
This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.
A user-writable role defeats the admin check
The first detailed finding exposes the opening distinction between valid code and flawed intent: any signed-in user can pass the admin access check because they can write their own role field. The authorization decision relies on a value that the person being authorized can change. That relationship makes the check ineffective even if reading the role and checking it both work as implemented.
Where does the user's ability to change their role connect to the admin decision? The issue view points to a source location and explains why the behavior is vulnerable, then provides guidance on fixing it. The important relationship to inspect is the write permission on the role field and the later trust placed in that field. The recording does not specify the patch; the supported correction is to prevent users from granting themselves the privilege the check is meant to enforce.
The issue also has an activity history and can be assigned to a developer. Findings begin in an open state, after which triage determines both the team's judgment and the quality-gate consequence:
- Accept: Treat the finding as valid while excluding it from quality-gate impact, so it does not prevent shipment on that basis.
- Confirm: Treat the finding as valid and let it affect the quality gate.
- False positive: Reject the finding as incorrect.
Accepting an issue therefore records a different decision from confirming it, even though both recognize a real vulnerability.
Suggest correction
This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.
A password reaches routes that should require MFA
Returning to the scan reveals five business-logic findings before the walkthrough opens an authentication and session finding. This second high-severity issue asks a different question: what can a user reach after supplying only an account password? The reported answer is every protected route, including admin functions, without completing multi-factor authentication. The issue view again provides the source location, explanation, and fix guidance.
The failure is the missing requirement between password authentication and access to protected routes. If those routes admit the user before MFA is complete, the additional factor does not constrain access to them. The security expectation must hold where protected functionality becomes reachable; having an MFA step elsewhere in the application is insufficient.
Suggest correction
This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.
Schedule the investigation, then assign remediation
How can the same investigation run as the repository changes? Hunter Agent supports scheduled scans as well as on-demand runs, with daily, weekly, or monthly frequency and a selectable branch. The demonstrated scan used the main branch, but recurring scans can target another branch. These settings turn the deep analysis into a recurring task rather than a one-time inspection.
The closing announcement extends the workflow from finding issues and suggesting fixes to assigning them to SonarQube Remediation Agent. Luttrell announces automatic remediation as becoming available that week and says remediation can also run on a schedule. The ending does not demonstrate a generated patch or its verification, so it establishes the announced handoff rather than the correctness of an automatic fix.
That handoff completes the product's proposed path: investigate logic-level vulnerabilities, put findings into the existing issue workflow, and assign work to developers or the remediation agent. The closing invitation keeps the talk's hunting metaphor: “hunt for issues before you yourself are hunted.”
Suggest correction
This note stays in this page until you copy or download it. Nothing is submitted; reloading clears the draft.
Resources
Related talks
- SonarQube + OpenAI: Agentic Development — Killian Carlsen-Phelan, Sonar
Related topic: SonarQube and OpenAI in agentic development.
- How to Build Quality Gates into Agentic Coding Workflows — Nnenna Ndukwe, Qodo AI
Related topic: building quality gates into agentic coding workflows.
Full transcript
Loading transcript…