Checkmarx / ast-github-action

Checkmarx application security testing (AST) GitHub action
https://github.com/marketplace/actions/checkmarx-ast-github-action
Apache License 2.0
16 stars 23 forks source link

[BUG] - 2.0.10 is not compatible with asynchronous scans #76

Closed ArnaudLacroix closed 2 years ago

ArnaudLacroix commented 2 years ago

Describe the bug

When using the async parameter, the AST action fails with a Failed listing results: response status code 404 error

Expected behavior

Up to version 2.0.9, the behavior was successful completion with a simple message: Scan executed in asynchronous mode or still running. Hence, no results generated.

Actual behavior

Action fails with the following error: Failed listing results: response status code 404

Steps to reproduce

just add --async in the additional_params

Additional comments

N/A

Logs

"/home/runner/work/_temp/_runner_file_commands":"/github/file_commands" -v "/home/runner/work/xxx/xxx":"/github/workspace" 817f70:483c7dc5525d4185a81dced741eef258 "https://eu.ast.checkmarx.net/" "xxx" "***" "***" "***" "xxx" "--tags 'prod:true' --scan-types sast,sca,kics --project-tags xxx --project-groups *** --sast-preset-name 'Checkmarx default' --report-format summaryJSON --async" "" 2022-09-21T10:14:52.0723027Z Creating directory 2022-09-21T10:14:53.7655326Z {"ID":"xxx","ProjectID":"xxx","ProjectName":"xxx","Status":"Running","CreatedAt":"2022-09-21T10:14:53.710366293Z","UpdatedAt":"2022-09-21T10:14:53.710366293Z","Branch":"main","Tags":{"prod":"true"},"SastIncremental":"Full","Timeout":"NONE","Initiator":"xxx","Origin":"Github ","Engines":["","sast","kics","sca"]} 2022-09-21T10:14:54.5028766Z Failed listing results: response status code 404 2022-09-21T10:14:54.5065263Z PR decoration not created. 2022-09-21T10:14:54.6283776Z Post job cleanup.

pedrompflopes commented 2 years ago

Hi @ArnaudLacroix Thanks for raising the issue. Can you please use the new version 2.0.11, we introduced a fix for it.

Thanks.

ArnaudLacroix commented 2 years ago

Thanks! I confirm this bug is fixed in 2.0.11