Find and Fix a CodeQL Security Finding on GitHub | Lesson 36

Find and Fix a CodeQL Security Finding on GitHub. In this lesson: Trace request input to the actual CodeQL finding Reproduce and repair the query behavior with unchanged tests Verify the same alert is fixed after comparable corrected-head analysis Lesson 36 of the Digital Tech-IQ Git and GitHub course. Follow the full course in order, or use this lesson to practice this specific skill. Full course:    • Git & GitHub Complete Course | From First ...   Chapters 00:00 Follow the input all the way to the query 00:33 Open settings for the code scanning practice lab 00:58 Open Advanced Security from the repository settings 01:28 Open the CodeQL setup choices 01:54 Inspect the detected Python default configuration 02:25 Configuration starts the work; analysis supplies the evidence 03:02 Confirm CodeQL is configured after the backend setup completes 03:31 Open the repository security overview for the finding 03:56 Open the actual code scanning alert list 04:22 Read the SQL injection alert on the recorded source 04:50 Inspect the data path from request input to the SQL query 05:22 A finding connects a source to a sensitive operation 05:58 Inspect the exact code scanning lab baseline 06:23 Confirm the isolated Python environment 06:52 Read the request input and interpolated query 07:21 Read the ordinary and security regression checks 07:49 Ordinary tests can miss the boundary 08:24 Reproduce the security regression against the flagged code 08:53 Bind values instead of building SQL from them 09:30 Apply the supplied parameterized query correction 09:59 Review the exact SQL parameter binding change 10:26 Run the same four checks against the correction 10:53 A local pass and a hosted fix are separate checks 11:28 Confirm only the intended source file changed 11:53 Stage only the reviewed query correction 12:20 Commit the independently tested query fix 12:48 Push the tested correction for hosted analysis 13:11 Read the correction commit for the next scan 13:36 Return to security after the tested correction 14:04 Check the open alert count after hosted reanalysis 14:28 Open the closed code scanning alerts 14:53 Closed does not always mean repaired 15:30 Verify the same SQL injection finding is fixed 15:59 Return from the resolved finding to code scanning 16:25 Inspect CodeQL tool status after the repair 16:56 Your code-scanning repair challenge Practice in your own learning repository. Pause, try the steps, and check the result before continuing. Narration is AI-generated. Captions use estimated timing. #GitHub #Git #LearnGitHub