search

kasunkv / owasp-zap-vsts-task

Visual Studio Team Services build/release task for running OWASP ZAP automated security tests
MIT License
30 stars 11 forks source link

HTML rapports "Cannot read property 'riskcode' of undefined" #25

Open bilalAchahbar opened 5 years ago

bilalAchahbar commented 5 years ago

I know this issue is been asked a couple of times, but I tried to output a HTML rapport a couple of weeks ago (after the last time this issue is being asked) and it worked perfectly with a HTML rapport. But now it gives the same error as the persons asked before Error: Task Failed. Error: "Cannot read property 'riskcode' of undefined"; Markdown is fine but HTML is not working anymore

kasunkv commented 5 years ago

Did you get different alert types in the second time you scanned your site? or the report is exactly the same with the issues reported previously?

bilalAchahbar commented 5 years ago

I do not get your question. The first time ( a couple of weeks ago) HTML option is working perfectly The second time right now : i got this error and I don't get any error.

Markdown doesn't give any errors and gives a normal repport

kasunkv commented 5 years ago

Could you check the HTML report you got when it worked and check the count for each type of security issues. and then take the markdown report (since HTML report is not working) and count each type of security issues reported and see if the count is different.

bilalAchahbar commented 5 years ago

With the Html report i got 1 medium and 4 low risks With the markdown report i got 1 low risk

kasunkv commented 5 years ago

Also can you confirm that, in the markdown file that you got only 1 risk, the riskcode value is not available?

bilalAchahbar commented 5 years ago

I can confirm that in the markdown i got only 1 risk. What do you mean by the riskcode value ?

andydkelly-ig commented 5 years ago

I too am receiving the same error when trying to produce the HTML or XML report via the VSTS extension.

HuguesJ commented 5 years ago

I got the same issue with TFS on Prem and the latest version of the extension. Any way to work around the issue?

jithuvgeorge commented 5 years ago

@kasunkv, I too got the same issue. I am getting this error whenever there are 0 alerts after the scan. I think its something related to report generation.