zaproxy / zaproxy-website

The source of ZAP website
https://www.zaproxy.org
MIT License
64 stars 107 forks source link

ZAP Scan Baseline Report #441

Closed github-actions[bot] closed 2 years ago

github-actions[bot] commented 3 years ago

View the following link to download the report. RunnerID:862420546

github-actions[bot] commented 3 years ago

View the following link to download the report. RunnerID:984757042

kingthorin commented 3 years ago

Something needs to be tweaked to not post empty results?

github-actions[bot] commented 3 years ago

View the following link to download the report. RunnerID:1196398412

github-actions[bot] commented 2 years ago

View the following link to download the report. RunnerID:1410452254

github-actions[bot] commented 2 years ago

View the following link to download the report. RunnerID:1609472728

Anthonymcqueen21 commented 2 years ago

Does Cacheable HTTPS response count as a valid informational vulnerability ?

kingthorin commented 2 years ago

No all the information the site serves is public.

Anthonymcqueen21 commented 2 years ago

Okay thank you what informational bugs do you accept ?

kingthorin commented 2 years ago

For the BugBounty I can't think of any. The BugCrowd program is more for high impact stuff. For ZAP itself we only payout for RCEs, though we've accepted some other lower impact things like protocol usage, lack or password masking, etc. For the site we've accepted some reports like link/domain squatting. Hope that helps.

Keep in mind what ZAP is and that it's an Open Source project with very limited funds and a small team.

Anthonymcqueen21 commented 2 years ago

Thank you well i recently sent a informational that was accepted no payout that is totally fine the fact i got accepted and not denied i was grateful.

Anthonymcqueen21 commented 2 years ago

Remote Code Executions the holy grail of bugs well time to figure it out thank you.

Anthonymcqueen21 commented 2 years ago

One last question, if found do you accept Path Traversal bugs ?

kingthorin commented 2 years ago

I guess we'd be concerned if the traversal was outside of the web root. (Well actually GitHub probably would.)

Ex: No we aren't concerned that: www.zaproxy.org/blog/../ works. However, if you can get access to /etc/passwd or something that we don't intend to have web accessible then yes obviously that's an issue.

Anthonymcqueen21 commented 2 years ago

Okay thank you just wanted to ask RCE only got it.

thc202 commented 2 years ago

It's preferable to use the mailing lists (Get in Touch) for these type of queries.

Anthonymcqueen21 commented 2 years ago

Besides RCE are there any other critical or high bugs that you might be interested in or it just depends on the impact ?

kingthorin commented 2 years ago

It really depends on impact. RCE is currently the only thing we consistently payout for. As mentioned earlier there are things we accepted but didn't payout for, it just depends on the issue. As @thc202 mentioned if there's more to this discussion it should be moved to the User Group :wink:

kingthorin commented 2 years ago

https://github.com/zaproxy/zaproxy-website/issues/874