You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit c829ea8
Browse filesBrowse the repository at this point in the historyBrowse files
SAST to DAST sink correlation: read code sinks, mark them reachable or context
The gray box reader already pulled routes from the mapped code. It now also
reads dangerous patterns, tagged by type: a query built by string joining, a
shell or eval call, an unsafe deserialize, a template rendered from a string, a
write into the page, a file opened from user input. Each sink carries the
routes its file declares.
After the scan, each sink is marked reachable when the scan reached one of
those routes, or context when it did not. A reachable sink is a lead a dynamic
test can prove; one that is not reachable is a thing to review by hand, not a
dynamic bug, which is the right way to treat code the outside cannot touch.
The PDF report gains a Code and the scan section: the reached sinks as leads,
and an Areas to review list for the rest, not counted toward the grade. All
deterministic, no AI. Stored in a new code_sinks column, added on boot.
<pclass="faint">{{ "Dangerous patterns read from the mapped code, split by whether the scan reached the route they sit behind. Reachable means a dynamic test can get to that code, so it is a lead worth proving. The rest is context: a thing to look at by hand, not a dynamic finding." | sentence_spaced }}</p>
<h3>5.2 Areas to review (not reached by the scan)</h3>
283
+
<pclass="faint">{{ "Not confirmed, and not counted toward the grade. These are leads for a code review, not proven bugs, because the scan could not reach them from the outside." | sentence_spaced }}</p>
0 commit comments