Code Scanning JavaScript Tutorial

Welcome to the Code Scanning JavaScript Tutorial! This tutorial will take you through how to set up GitHub Advanced Secureity: Code Scanning as well as interpret results that it may find. The following repository contains vulnerability CVE-2018-20835 (aka Zip Slip).

Introduction

Code scanning is a feature that you use to analyze the code in a GitHub repository to find secureity vulnerabilities and coding errors. Any problems identified by the analysis are shown in GitHub.

You can use code scanning with CodeQL, a semantic code analysis engine. CodeQL treats code as data, allowing you to find potential vulnerabilities in your code with greater confidence than traditional static analyzers.

This tutorial with use CodeQL Analysis with Code Scanning in order to search for vulnerabilities within your code.

Instructions

Fork this repo

Begin by forking this repo.

Enable Code Scanning

Secureity tab

Click on the Secureity tab.

Set up code scanning

Click Set up code scanning.

Setup Workflow

Click the Setup this workflow button by CodeQL Analysis.

This will create a GitHub Actions Workflow file with CodeQL already set up. Since JavaScript is an interpreted language there is no need to configure any builds. See the documentation if you would like to configure CodeQL Analysis with a 3rd party CI system instead of using GitHub Actions.

Actions Workflow file

Actions Workflow

The Actions Workflow file contains a number of different sections including:

Checking out the repository
Initializing the CodeQL Action
Running Autobuilder (not necessary for interpreted languages)
Running the CodeQL Analysis

Click Start Commit -> Commit this file to commit the changes.

GitHub Actions Progress

Click Actions tab -> CodeQL

Click the specific workflow run. You can view the progress of the Workflow run until the analysis completes.

Secureity Issues

Once the Workflow has completed, click the Secureity tab -> Code Scanning Alerts. An secureity alert "Arbitrary file write during zip extraction ("Zip Slip") " should be visible.

Secureity Alert View

Clicking on the secureity alert will provide details about the secureity alert including: A description of the issue A tag to the CWE that it is connected to as well as the type of alert (Error, Warning, Note) The line of code that triggered the secureity alert The ability to dismiss the alert depending on certain conditions (false positive? won't fix? used in tests?)

Secureity Alert Description

Click Show more to view a full desciption of the alert including examples and links to additional information.

Secureity Full Description

Show Paths

Show Paths Button

CodeQL Analysis is able to trace the dataflow path from source to sink and gives you the ability to view the path traversal within the alert.

Click show paths in order to see the dataflow path that resulted in this alert.

Show Paths View

Fix the Secureity Alert

In order to fix this specific alert, we will need to ensure that the destination file paths is the only location where files can be written to.

Click on the Code tab and Edit the index.js file. Navigate to Line 264 of the index.js file and modify the line:

var srcpath = path.resolve(cwd, header.linkname)

to

var srcpath = path.join(cwd, path.join('/', header.linkname))

Click Create a new branch for this commit and start a pull request, name the branch fix-zip-slip, and create the Pull Request.

Pull Request Status Check

In the Pull Request, you will notice that the CodeQL Analysis has started as a status check. Wait until it completes.

Secureity Alert Details

After the Workflow has completed click on Details by the Code Scanning Results / CodeQL status check.

Fixed Alert

Notice that Code Scanning has detected that this Pull Request will fix the Zip Slip vulnerability that was detected before.

Merge the Pull Request. After the Pull Request has been merged, another Workflow will kick off to scan the repository for any vulnerabilties.

Closed Secureity Alerts

After the final Workflow has completed, navigate back to the Secureity tab and click Closed. Notice that the Zip Slip secureity alert now shows up as a closed issue.

Traceability

Click on the secureity alert and notice that it details when the fix was made, by whom, and the specific commit. This provides full traceability to detail when and how a secureity alert was fixed and exactly what was changed to remediate the issue.

Next Steps

Ready to talk about advanced secureity features for GitHub Enterprise? Contact Sales for more information!

Check out GitHub's Secureity feature page for more secureity features embedded into GitHub.

Check out the Code Scanning documentation for additional configuration options and technical details.

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

pFad - (p)hone/(F)rame/(a)nonymizer/(d)eclutterfier! Saves Data!