search

pumasecurity / puma-scan

Puma Scan is a software security Visual Studio extension that provides real time, continuous source code analysis as development teams write code. Vulnerabilities are immediately displayed in the development environment as spell check and compiler warnings, preventing security bugs from entering your applications.
https://www.pumascan.com
Mozilla Public License 2.0
443 stars 82 forks source link

Version 1.0.7 does not prompt any warnings #48

Closed YeeSuannn closed 5 years ago

YeeSuannn commented 5 years ago

Hi,

I'm using Puma Scan Version 1.0.7 in VS 2015 mainly. It does not prompt any warnings in my error list panel. However, it prompted errors in VS 2017 when i'm using version 2.0.0.1. It does not tally with VS 2015. Is it Cos' version 1.0.7 is depreciating?? If so, is there no fixes for it?

Thanks.

ejohn20 commented 5 years ago

Version 1.0.7 should work for VS2015. Did you enable full solution analysis? If so, can you provide more details on what diagnostic is not showing up?

YeeSuannn commented 5 years ago

Yes, i did enabled the full solution analysis. Example of diagnostic that does not work such as "Unvalidated redirect location is passed to the Response.Redirect method" and "Unvalidated file paths are passed to a file open API, which can allow unauthorized file system operations (e.g. read, write, delete) to be performed on unintended server files."

ejohn20 commented 5 years ago

Please provide code snippets of the warnings that are not showing. These rules are supposed in the 1.0.7 version.

YeeSuannn commented 5 years ago

image

The previous comment are the warnings that are not appearing in VS 2015, while it appeared only in VS 2017 for my program.

Do take note once again. For VS 2015, i'm using 1.0.7 while in VS 2017, i'm using 2.0.0.1.

ejohn20 commented 5 years ago

@YeeSuan95 In Visual Studio 2015 are you seeing the spell check warnings on the actual line of code in the document?

YeeSuannn commented 5 years ago

@ejohn20 Nope

ejohn20 commented 5 years ago

Closing this issue. VS2015 is not supported with newer versions of the extension. We recommend upgrading to VS2017.