Back to Resources

Professional Edition 1.1.2 (July 2021)

Professional Edition 1.1.2 Release Notes

Puma Scan’s 1.1.2 release is an update for the Puma Scan End User, Server, and Azure DevOps Editions.

System Requirements

  • End User Edition for Visual Studio Code requires Visual Studio Code for Windows, macOS, or Linux.

  • End User Edition for Visual Studio requires Visual Studio 2019 v16.0 or higher.

  • End User Edition for Visual Studio 2017 requires Visual Studio 2017 v15.9 or higher.

  • Server Edition requires a Windows Server with the following:

    • .NET Framework v4.7.2

    • The Build Tools for Visual Studio 2017 and 2019 are both supported. Ensure you have at least 1 of the following installed:

      • Build Tools 2017 version 15.8 or higher

      • Build Tools 2019 version 16.4 or higher

  • Azure DevOps Edition requires a hosted Azure Build Pipeline using the vs2017-win2016 or windows-2019 build agent.

Framework Enhancements

  • Bug fix: In Puma Scan rule, SEC0019 - Insecure Deserialization, certain uses of System.Runtime.Serialization.Json.DataContractJsonSerializer raise the following exception:
    'System.ArgumentOutOfRangeException' with message 'Specified argument was out of the range of valid values.
  • Bug fix: In Puma Scan rule, SEC0039 - Vulnerable Package Reference, project dependencies omitting a Version attribute will cause all project dependencies to be ignored for a given project.

Server and Azure DevOps Editions

  • Enhancement: The project and settings switches now support asterisk style glob pattern to be used when providing the path the solution, project or settings file.
    c:\> PumaScan -p c:\git\puma-prey\**\*.sln
      -s c:\git\puma-prey\**\.pumafile
      -f html,json
      -o c:\git\puma-prey\puma-scan-results

Azure DevOps Editions

  • Enhancement: Activating an Azure DevOps license no longer requires the PumaLicense pipeline variable to be updated after an activation or after a license renewal. Manual activation and updating of the pipeline variable is only required if Puma License servers are unreachable and the PumaLicense value has gone stale.

Server Edition

  • Bug fix: Command line exit code incorrectly reporting an error code of 1 when running Puma Scan with the version switch.

End User Edition for Visual Studio

  • Enhancement: New informational messages displayed on the Reports dialog (Extensions-> PumaScan-> Reports) when Visual Studio settings or project configurations are preventing Puma Scan from reporting all results.