Skip to content

Conversation

@Napalys
Copy link
Contributor

@Napalys Napalys commented Sep 17, 2025

No description provided.

@Napalys Napalys marked this pull request as ready for review September 17, 2025 09:41
@Napalys Napalys requested a review from a team as a code owner September 17, 2025 09:41
Copilot AI review requested due to automatic review settings September 17, 2025 09:41
Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

This PR improves GraphQL data flow analysis by adding support for tracking taint flow from GraphQL query sources and variables to resolver function parameters in the CodeQL JavaScript library.

  • Adds taint flow modeling for the graphql library to track data from query sources to resolver parameters
  • Includes test case demonstrating code injection vulnerability through GraphQL resolver
  • Updates expected test results to reflect the new taint flow tracking

Reviewed Changes

Copilot reviewed 5 out of 5 changed files in this pull request and generated 1 comment.

File Description
graph-ql.js Test case showing GraphQL code injection vulnerability with eval in resolver
graph-ql.model.yml Taint flow model for graphql library tracking source to resolver parameters
*.expected Updated test expectations reflecting new taint flow detection
2025-09-17-graphql-enhance.md Release notes documenting the GraphQL analysis improvement

@@ -0,0 +1,36 @@
const express = require('express');
Copy link

Copilot AI Sep 17, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[nitpick] The filename 'graph-ql.js' uses a hyphen, but GraphQL is typically written as one word. Consider renaming to 'graphql.js' for consistency with the library name.

Copilot uses AI. Check for mistakes.
@Napalys Napalys requested a review from asgerf September 17, 2025 10:38
@Napalys Napalys merged commit 4f8166a into github:main Sep 17, 2025
14 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants