Home
Reapsaw automation solution was build to run scans and provide developers consolidated report with friendly recommendations on fixes.
- Vulnerabilities reported to build pipeline, ReportPortal and Jira,
- Easy to integrate within build pipeline;
- BugBar functionality.
- Installed Docker v18.09+
- You need to build and package the project for test it as for deploy
- Checkmarx or Snyk API token
Instructions about how to setup Checkmarx and Snyk can be found on the right hand menu.
Pull the code of the project for scanning from the CSV:
$ git clone <git_repo_url>For the demo purposes we will use one of the OWASP repositories:
$ git clone https://github.com/OWASP/NodeGoat
$ cd NodeGoat
$ npm install # exit code 0Make sure you're got no errors after the build step command.
This will let you run Reapsaw on your local machine.
Ensure you have Checkmarx or Snyk token in place.
- Clone
Reapsaw:
$ git clone https://github.com/dowjones/reapsawNow, look in your project folder and see that there is a newly created sast folder with Reapsaw source code.
- Build image:
$ cd reapsaw
$ docker build -t sast:latest .
....
---> b995eb5d7d1a
Successfully built b995eb5d7d1a
Successfully tagged sast:latestHere -t sast:latest is the name and tag of image.
The resulting image will be tagged as sast:latest:
- Run container:
$ docker run --name sast --rm \
-v <path_to_folder_with_source_code>:/code \
-e TASKS=<tasks> \
-e CX_PROJECT=<project_name> \
-e CX_URL=<cx_url> \
-e CX_USER=<cx_user> \
-e CX_PASSWORD=<cx_user_pwd> \
-e SNYK_TOKEN=<snyk_token> \
sast:latestThere are a few different run options:
-e TASKS # Available option: "cx","snyk","cx,snyk"
-e TASKS='cx' # e.g You want Checkmarx scan to happen:
-e CX_PROJECT # Project name in Checkmarx
-e CX_URL # Checkmarx (e.g. https://checkmarx.com)
-e CX_USER # username
-e CX_PASSWORD # password
-e SNYK_TOKEN # Snyk API tokenIf you want to Checkmarx and Snyk to happen together:
$ docker run --name sast --rm \
-v /Users/demo/NodeGoat:/code \
-e TASKS="cx,snyk" \
-e CX_PROJECT="demo_sast" \
-e CX_URL="https://mycheckmarx.com" \
-e CX_USER="my_user_id" \
-e CX_PASSWORD="my_user_pwd" \
-e SNYK_TOKEN="my-snyk-api-token" \
sast:latestReapsaw will start scanning source code and creates reports in reports/ folder.
Container will be automatically deleted when run finished.
Reports are available on your host machine in reports folder:
$ cat <path_to_folder_with_source_code>/reports/json_report.jsonIf you want only Snyk to happen
$ docker run --name sast --rm \
-e TASKS="snyk" \
-v <path_to_folder_with_source_code>:/code \
-e SNYK_TOKEN=<SNYK_TOKEN> \
sast:latest- JSON report
[
{
"Issue Name": <string>, # Vulnerability name e.g "SQL Injection"
"Issue Tool": <string>, # Tool name e.g "Checkmarx"
"Issue Priority": <string>, # "Major" by default
"Issue Severity": <string>, # According to BugBar configuration
"Description": <string>, # Used for Jira, e.g The software does not sufficiently validate ...
"Recommendations": <string>, # Recommendation from tool or BugBar e.g Upgrade `marked` to version 0.6.2 or higher
"Instances": <string>, # Location of finding/module e.g "File routes/login.js"
"Jira Name": <string>, # Title of the corresponding ticket created in Jira. Get's from BugBar
"Links": <string>, # Link to the "Checkmarx Viewer"
"Snippet": <string>, # Code snippet if applicable: "var url_params = url.parse(req.url, true).query;"
"top_level_module": <string>, # Name of the top level module to update e.g "marked" ,
....
}
]Example
[
{
"Issue Name": "Cross-site Scripting (XSS).app/routes/contributions.js",
"Issue Tool": "Checkmarx",
"Steps To Reproduce": "",
"Issue Priority": "Major",
"Issue Severity": "High",
"Issue Confidence": "Certain",
"CWE": "[CWE-79|https://cwe.mitre.org/data/definitions/79]",
"CVE": "",
"Overview": "",
"Recommendations": "# Validate all input, regardless of source. Validation should be based on a whitelist: accept only data fitting a specified structure, rather than reject bad patterns. Check for:\n#* Data type\n#* Size\n#* Range\n#* Format\n#* Expected values\n# Fully encode all dynamic data before embedding it in output.\n# Encoding should be context-sensitive. For example:\n#* HTML encoding for HTML content\n#* HTML Attribute encoding for data output to attribute values\n#* JavaScript encoding for server-generated JavaScript.\n# Consider using either the ESAPI encoding library, or the built-in platform functions. For earlier versions of ASP.NET, consider using the AntiXSS library.\n# In the Content-Type HTTP response header, explicitly define character encoding (charset) for the entire page.\n# Set the httpOnly flag on the session cookie, to prevent XSS exploits from stealing the cookie.\n\n",
"References": "Line 34 in file [app/routes/contributions.js|https://checkmarx.com/CxWebClient/ViewerMain.aspx?scanid=1041725&projectid=3133&pathid=6]",
"Paths": "",
"URLs": "",
"error_string": "Cross-site Scripting (XSS) 79\napp/routes/contributions.js",
"Description": " The software does not sufficiently validate, filter, escape, and/or encode user-controllable input before it is placed in output that is used as a web page that is served to other users.\n GROUP: JavaScript_Server_Side_Vulnerabilities\n CATEGORY: A7-Cross-Site Scripting (XSS)\n *Code*:\n ``` var userId = req.session.userId; ```",
"Instances": "File app/routes/contributions.js",
"Attachments": [],
"Tags": [
{
"TestType": "sast"
},
{
"Provider": "Reapsaw"
},
{
"Tool": "Checkmarx"
}
],
"Jira Name": "Cross-site Scripting (XSS)",
"Repo": "",
"Links": "https://checkmarx.com/CxWebClient/ViewerMain.aspx?scanid=1041725&projectid=3133&pathid=6",
"Snippet": "var userId = req.session.userId;",
"Jira Description": "h3.*Instances:*\nFile app/routes/contributions.js\nh3.*Recommendations:*\n\n# Validate all input, regardless of source. Validation should be based on a whitelist: accept only data fitting a specified structure, rather than reject bad patterns. Check for:\n#* Data type\n#* Size\n#* Range\n#* Format\n#* Expected values\n# Fully encode all dynamic data before embedding it in output.\n# Encoding should be context-sensitive. For example:\n#* HTML encoding for HTML content\n#* HTML Attribute encoding for data output to attribute values\n#* JavaScript encoding for server-generated JavaScript.\n# Consider using either the ESAPI encoding library, or the built-in platform functions. For earlier versions of ASP.NET, consider using the AntiXSS library.\n# In the Content-Type HTTP response header, explicitly define character encoding (charset) for the entire page.\n# Set the httpOnly flag on the session cookie, to prevent XSS exploits from stealing the cookie.\n\n\nh3.*Overview:*\n{panel:title=Cross-site Scripting (XSS)}*Description*: \nThe software does not sufficiently validate, filter, escape, and/or encode user-controllable input before it is placed in output that is used as a web page that is served to other users.\n GROUP: JavaScript_Server_Side_Vulnerabilities\n CATEGORY: A7-Cross-Site Scripting (XSS)\n *Code*:\n ``` var userId = req.session.userId; ```\n\n*References*: \nLine 10 in file [app/routes/contributions.js|https://checkmarx.com/CxWebClient/ViewerMain.aspx?scanid=1041725&projectid=3133&pathid=5]\n\n{panel}\n{panel:title=Cross-site Scripting (XSS)}*Description*: \nThe software does not sufficiently validate, filter, escape, and/or encode user-controllable input before it is placed in output that is used as a web page that is served to other users.\n GROUP: JavaScript_Server_Side_Vulnerabilities\n CATEGORY: A7-Cross-Site Scripting (XSS)\n *Code*:\n ``` var userId = req.session.userId; ```\n\n*References*: \nLine 34 in file [app/routes/contributions.js|https://checkmarx.com/CxWebClient/ViewerMain.aspx?scanid=1041725&projectid=3133&pathid=6]\n\n{panel}\n"
},
{
"Issue Name": "Regular Expression Denial of Service (ReDoS).marked",
"Issue Tool": "Snyk",
"Steps To Reproduce": "",
"Issue Priority": "Major",
"Issue Severity": "High",
"Issue Confidence": "Certain",
"CWE": "CWE-185",
"CVE": "",
"Overview": "",
"Recommendations": "Upgrade `marked` to version 0.6.2 or higher",
"References": "\r\n- [GitHub PR](https://github.com/markedjs/marked/pull/1083)\r\n- [GitHub Commit](https://github.com/markedjs/marked/pull/1083)",
"Paths": "owasp-nodejs-goat>[email protected]",
"URLs": "",
"error_string": "marked",
"Description": "*Vulnerable Package:* marked\n*Current Version:* 0.3.9\n*Vulnerable Version(s):* <0.3.18\n \n *Remediation:*\r\nUpgrade marked to version 0.3.17 or higher\r\n\r\n\n Overview\r\n[`marked`](https://www.npmjs.com/package/marked) is a markdown parser built for speed\r\n\r\nAffected versions of this package are vulnerable to Regular Expression Denial of Service (ReDoS) attacks. This can cause an impact of about 10 seconds matching time for data 150 characters long.\r\n\r\n\n ",
"Instances": "marked",
"Attachments": [],
"Tags": [
{
"TestType": "sast"
},
{
"Provider": "Reapsaw"
},
{
"Tool": "Snyk"
}
],
"Jira Name": "Vulnerable Software",
"Repo": "",
"top_level_module": "marked",
"upgrades": [
false,
"[email protected]"
],
"language": "js",
"RP Defect Type": "Product Bug"
}
]JUNIT report
<testsuites disabled="0" errors="10" failures="0" tests="10" time="0.0">
<testsuite disabled="0" errors="10" failures="0" name="SAST Scan" skipped="0" tests="10" time="0">
<testcase classname="Certain" name="Cross-site Scripting (XSS).app/routes/contributions.js">
<error message="Cross-site Scripting (XSS) 79 app/routes/contributions.js h3.*Instances:* File app/routes/contributions.js h3.*Recommendations:* # Validate all input, regardless of source. Validation should be based on a whitelist: accept only data fitting a specified structure, rather than reject bad patterns. Check for: #* Data type #* Size #* Range #* Format #* Expected values # Fully encode all dynamic data before embedding it in output. # Encoding should be context-sensitive. For example: #* HTML encoding for HTML content #* HTML Attribute encoding for data output to attribute values #* JavaScript encoding for server-generated JavaScript. # Consider using either the ESAPI encoding library, or the built-in platform functions. For earlier versions of ASP.NET, consider using the AntiXSS library. # In the Content-Type HTTP response header, explicitly define character encoding (charset) for the entire page. # Set the httpOnly flag on the session cookie, to prevent XSS exploits from stealing the cookie. h3.*Overview:* {panel:title=Cross-site Scripting (XSS)}*Description*: The software does not sufficiently validate, filter, escape, and/or encode user-controllable input before it is placed in output that is used as a web page that is served to other users. GROUP: JavaScript_Server_Side_Vulnerabilities CATEGORY: A7-Cross-Site Scripting (XSS) *Code*: ``` var userId = req.session.userId; ``` *References*: Line 10 in file [app/routes/contributions.js|https://checkmarx.com/CxWebClient/ViewerMain.aspx?scanid=1041725&projectid=3133&pathid=5] {panel} {panel:title=Cross-site Scripting (XSS)}*Description*: The software does not sufficiently validate, filter, escape, and/or encode user-controllable input before it is placed in output that is used as a web page that is served to other users. GROUP: JavaScript_Server_Side_Vulnerabilities CATEGORY: A7-Cross-Site Scripting (XSS) *Code*: ``` var userId = req.session.userId; ``` *References*: Line 34 in file [app/routes/contributions.js|https://checkmarx.com/CxWebClient/ViewerMain.aspx?scanid=1041725&projectid=3133&pathid=6] {panel} "
type="High"/>
</testcase>
<testcase classname="Certain" name="Vulnerable Software Version.marked">
<error message="marked h3.*Instances:* marked h3.*Recommendations:* Upgrade `marked` to version 0.6.2 or higher h3.*Overview:* {panel:title=Regular Expression Denial of Service (ReDoS)}*Description*: *Vulnerable Package:* marked *Current Version:* 0.3.9 *Vulnerable Version(s):* <0.3.18 *Remediation:* Upgrade marked to version 0.3.17 or higher Overview [`marked`](https://www.npmjs.com/package/marked) is a markdown parser built for speed Affected versions of this package are vulnerable to Regular Expression Denial of Service (ReDoS) attacks. This can cause an impact of about 10 seconds matching time for data 150 characters long. *References*: - [GitHub PR](https://github.com/markedjs/marked/pull/1083) - [GitHub Commit](https://github.com/markedjs/marked/pull/1083) *Paths*: owasp-nodejs-goat>[email protected] {panel} {panel:title=Regular Expression Denial of Service (ReDoS)}*Description*: *Vulnerable Package:* marked *Current Version:* 0.3.9 *Vulnerable Version(s):* <0.4.0 *Remediation:* Upgrade `marked` to version 0.4.0 or higher. Overview [marked](https://marked.js.org/) is a low-level compiler for parsing markdown without caching or blocking for long periods of time. Affected versions of this package are vulnerable to Regular Expression Denial of Service (ReDoS). A Denial of Service condition could be triggered through exploitation of the `heading` regex. *References*: - [GitHub Commit](https://github.com/markedjs/marked/commit/09afabf69c6d0c919c03443f47bdfe476566105d) - [GitHub PR](https://github.com/markedjs/marked/pull/1224) *Paths*: owasp-nodejs-goat>[email protected] {panel} {panel:title=Regular Expression Denial of Service (ReDoS)}*Description*: *Vulnerable Package:* marked *Current Version:* 0.3.9 *Vulnerable Version(s):* >=0.1.3 <0.6.2 *Remediation:* Upgrade `marked` to version 0.6.2 or higher. Overview [marked](https://marked.js.org/) is a low-level compiler for parsing markdown without caching or blocking for long periods of time. Affected versions of this package are vulnerable to Regular Expression Denial of Service (ReDoS). The `inline.text regex` may take quadratic time to scan for potential email addresses starting at every point. *References*: - [GitHub Commit](https://github.com/markedjs/marked/pull/1460/commits/be27472a8169dda7875330939f8115ab677cdc07) - [GitHub Commit Introducing the Vuln](https://github.com/markedjs/marked/commit/00f1f7a23916ef27186d0904635aa3509af63d47) - [GitHub PR](https://github.com/markedjs/marked/pull/1460) *Paths*: owasp-nodejs-goat>[email protected] {panel} "
type="High"/>
</testcase>
</testsuite>
</testsuites>- Reapsaw container in run state with set tokens.
- You can run container using next command:
$ docker run -tdi --entrypoint=cat --name sast \
-v <path_to_folder_with_source_code>:/code \
-v <path_to_folder_with_source_code>/reports:/code/reports \
-e CX_PROJECT="demo_sast" \
-e CX_URL="cx_url" \
-e CX_USER="user_cx" \
-e CX_PASSWORD="cx_pwd" \
-e SNYK_TOKEN="snyk_token" \
sast:latestwhere
-e CX_PROJECT # Project name in Checkmarx
-e CX_URL # Checkmarx (e.g. https://checkmarx.com)
-e CX_USER # username
-e CX_PASSWORD # password
-e SNYK_TOKEN # Snyk API token- Run multiple tools:
$ docker exec -t sast scan- to run only Checkmarx:
$ docker exec -t -e TASKS=cx sast scan- Generating JSON reports:
$ docker exec -it sast generate_reports -r falseThere are a few optional arguments:
-r REPORTPORTAL, --reportportal REPORTPORTAL # If false will not sent to Report Portal
-o OUTPUT, --output OUTPUT # output file
--json_output JSON_OUTPUT # Path to the JSON output file (by default reports folder)
--cm_input CM_INPUT # Path to the Checkmarx XML report file
--sn_input SN_INPUT # Path to the Snyk JSON report fileto print report run next:
$ cat reports/json_report.json- Convert Report into HTML:
$ docker exec -it sast junit2html /code/reports/junit_report.xml /code/reports/report.html- HTML report in Browser:
$ open <path_to_folder_with_source_code>/reports/report.html
- Push reports to ReportPortal :
If want to send results in Report Portal you should add next environment variables :
-e REPORT_PORTAL_URL # Report Portal (e.g. http://reportportal.io)
-e RP_TOKEN # You can get UUID user profile page in the Report Portal.
-e RP_PROJECT # Project name in Report PortalFind Report Portal configuration by the link:
$ docker exec -it \
-e RP_PROJECT="demo_data" \
-e REPORT_PORTAL_URL="https://reportportal.io" \
-e RP_TOKEN="API-TOKEN" \
sast generate_reports- Push vulnerabilities to JIRA
Make sure you're have a connection to Jira.
- Set env variables with JIRA parameters:
-e JIRA_HOST # URL to JIRA
-e JIRA_USR # user name
-e JIRA_PWD # user password$ docker exec -it \
-e JIRA_HOST='https://jira.example.net' \
-e JIRA_PWD='password' \
-e JIRA_USR='username' \
sast push_to_jira --jira_project TEST --jira_assignee testuserThere are different options :
--jira_project # Required
--jira_assignee # Required
--report_file # Optional
--defect_type # Optional
JIRA Ticket Example
