About product updates
The pages in this section list product updates from 2023 and earlier for Veracode products and services. For the latest updates, see Updates.
Updates that apply to specific Veracode regions show a region icon.
The pages in this section list product updates from 2023 and earlier for Veracode products and services. For the latest updates, see Updates.
Updates that apply to specific Veracode regions show a region icon.
This page lists CI/CD integration updates from 2023 and earlier. For current updates, see CI/CD.
Updates that apply to specific Veracode regions show a region icon.
This update includes the following improvements:
This update includes the following changes:
Unstable if the scan succeeds but fails the security policy.This version includes the following updates:
STOPPED_VERIFYING_PARTIAL_RESULTS and STOPPED_PARTIAL_RESULTS_AVAILABLE.This version includes the following changes:
-ppassword parameter for a proxy password.Veracode TeamCity Plugin version 2.7.0 adds configuration options for deleting incomplete scans.
Veracode Jenkins Plugin version 22.6.18.0 adds configuration options for deleting incomplete scans.
This video shows you how to:
The new Veracode for Artifactory version 1.3.0 allows you to perform security scanning of your application artifacts from within Artifactory. This release includes these features:
This page lists IDE integration updates from 2023 and earlier. For current updates, see IDEs.
Updates that apply to specific Veracode regions show a region icon.
This update includes the following improvements:
This update includes the following improvements:
This update includes minor performance improvements.
This update includes minor performance improvements.
This updates includes minor performance improvements.
This update fixes a minor performance issue.
This update includes the following improvements:
This update includes the following improvements:
Veracode SCA Scan for JetBrains version 0.6.1 adds support for IntelliJ IDEA version 2023.2.
Veracode SCA Scan for JetBrains version 0.6.0 is a new extension that integrates Software Composition Analysis (SCA) into the IntelliJ IDEA and PyCharm IDEs. Developers can scan their code to detect security risks in open-source libraries, library dependencies, and licenses. The detailed scan results help developers learn about vulnerabilities, prioritize security fixes, and remediate security issues from within their IDE.
This update includes the following improvements:
USER_HOME directory no longer result in an error.This update includes the following improvements:
veracode-project-user.json.This update improves error handling.
See Veracode Greenlight for VS Code.
This update adds security improvements.
This update includes the following improvements:
This update adds support for Eclipse IDE version 2023-03.
This update includes the following improvements:
Veracode Greenlight v1.8.7 adds support for IntelliJ v2022.2.3.
Veracode SCA Scan for VS Code version 0.6.0 includes the following updates:
Veracode Greenlight for IntelliJ version 1.8.6 supports a recent change to the Greenlight API. To continue using this plugin, you must upgrade to this version by February 13, 2023.
Veracode Greenlight for Eclipse version 2.9.7 includes these changes:
Veracode has made a change to the Greenlight API that will impact the following plugins.
New versions of these plugins will be available on February 2, 2023 and February 3, 2023, respectively. To continue using these plugins, you must upgrade to the new versions by February 13, 2023.
Veracode SCA Scan for VS Code version 0.5.0 is a new extension that integrates Software Composition Analysis (SCA) into VS Code. Developers can scan their code to detect security risks in open-source libraries, library dependencies, and licenses. The detailed scan results help developers learn about vulnerabilities, prioritize security fixes, and remediate security issues from within their IDE. Version 0.5.1 only removes an obsolete README.
Veracode for VS Code version 1.6.0 includes the following updates:
Veracode Static for Visual Studio version 1.7.0 fixes an issue where the extension could not authenticate with Veracode from a European Region instance.
Veracode Greenlight for IntelliJ version 1.8.5 adds support for IntelliJ IDEA 2022.2.3.
Veracode Static for Visual Studio 2019 and 2022 version 1.6.0 includes these changes:
Greenlight for Eclipse version 2.9.6 includes minor security and documentation updates.
Veracode Static for Visual Studio (New) version 1.5.0 includes these changes:
Veracode Static for Visual Studio version 1.4.0 is a new extension for adding Static Analysis to Visual Studio 2019 and 2022. The new extension for Visual Studio 2019 provides major improvements compared to our current legacy extension for version 2019, which Veracode continues to support.
The extensions include these features:
An extension for each Visual Studio version is available from the Visual Studio Marketplace.
Veracode Greenlight for Visual Studio version 1.3.184.96 is a new extension for adding Greenlight scanning to the newer versions of Visual Studio 2019 and 2022. An extension for each Visual Studio version is available from the Visual Studio Marketplace.
This video shows you how to:
This video shows you how to:
Veracode Static for Eclipse version 3.4.0 replaces the Veracode Eclipse Plugin. This version adds support for Eclipse 2019-09. It also adds support for Java Runtime Environment (JRE) 11 and 13.
You can no longer use basic authentication. Basic authentication consists of only a username and password. You must now use Veracode API ID and key authentication. Any custom integration scripts must also include HMAC signing.
Veracode Static for IntelliJ version 3.0.0 replaces the Veracode IntelliJ Plugin. This version supports IntelliJ IDEA Ultimate and Community 2017.x to 2019.3. It also adds support for Java Runtime Environment (JRE) 11 and 13.
You can no longer use basic authentication. Basic authentication consists of only a username and password. You must now use Veracode API ID and key authentication. Any custom integration scripts must also include HMAC signing.
Veracode Static for Visual Studio version 4.0.0.1 replaces the Veracode for Visual Studio Extension. This version supports Visual Studio 2015, 2017, and 2019. In Visual Studio 2015 and 2017, the name of the top-level Veracode menu is now Veracode Static. In Visual Studio 2019, the Veracode Static menu appears under the Extensions menu.
You are required to configure an API credentials file, which you use to provide your Veracode API ID and key credentials to Veracode Static for Visual Studio.
This page lists SCM and ticketing integration updates from 2023 and earlier. For current updates, see SCM and ticketing.
Updates that apply to specific Veracode regions show a region icon.
This update includes the following improvements:
This update adds historical diagnostics data to the Monitoring and Troubleshooting page.
Veracode has released the Veracode Workflow App that allows you to scan your GitHub repositories with Static Analysis, Software Composition Analysis (SCA), and Container Security. The app uses template workflows in a centralized location that you can apply to all repositories across your organization.
The functionality of the app includes:
You can download the app from the GitHub marketplace. For more information, view the Veracode documentation.
This update includes the following changes:
This update adds support for Jira Server version 9.11.2.
This update includes the following changes:
This update includes the following improvements:
This update includes the following improvements:
This update includes the following improvements:
This update fixes an issue where IssueCreatorImpl errors on the Monitoring and Troubleshooting page caused unexpected failures.
This update includes the following improvements:
This update includes the following changes:
scanpollinginterval.This update includes the following changes:
This update includes the following changes:
lifecyclestage parameter as an optional argument in the Upload and Scan task. This parameter is not supported in YAML.The integration now imports findings from scanned applications with COTS (commercial off-the-shelf) enabled.
This version includes the following changes:
This version addresses the low severity information disclosure issue detailed in CVE-2023-25722. For more information, go to the Veracode Community.
This update adds support for both of the following YAML property values:
ConnectionDetailsSelection='Endpoint'ConnectionDetailsSelection='Service Connection'This update includes the following changes:
ConnectionDetailsSelection='Endpoint' to ConnectionDetailsSelection='Service Connection'. When you upgrade to this new extension, you must update your YAML with the new value name.Fail build if Upload and scan build steps fails option is cleared, but the application name contains special characters.Veracode Integration for Jira version 4.0.1 adds support for Jira Server 9. This integration no longer supports Jira Server 8.6.0 and earlier.
ConnectionDetailsSelection='Endpoint' YAML PropertyIn February 2023, Veracode will release a new Azure DevOps Extension that uses the YAML property value ConnectionDetailsSelection='Service Connection' rather than the current value ConnectionDetailsSelection='Endpoint'. When upgrading to this new extension, you must update your YAML with the new value name.
Veracode Azure DevOps Extension version 3.17.0 includes the following improvements:
Veracode Integration for Jira Cloud version 4.7.0 now successfully loads the Findings Import page when importing large Jira projects.
Veracode Integration for Jira Server version 3.38.0 includes the following improvements:
Veracode Azure DevOps Extension version 3.16.0 fixes the link on the Veracode Scan Summary tab. The link now opens the scan results in the Veracode Platform instead of the Application page.
Veracode Integration for Jira version 3.37.0 fixes an issue where the plugin ignores all remaining applications after attempting to import findings from an application with COTS enabled.
Veracode Azure DevOps Extension version 3.15.0 adds options for deleting incomplete scans in your pipeline. When configuring the extension, you can add -deleteincompletescan as an optional argument or add -deleteIncompleteScan as a YAML property.
Veracode Integration for Jira Cloud version 4.6.0 adds a new filter that only imports findings with new scan data, policy changes, or changes to applied mitigations since the last import.
Veracode Azure DevOps Extension version 3.14.0 includes the following improvements to the Flaw Importer Task.
Veracode Integration for Jira version 3.36.0 fixes an issue where the integration did not create tickets of imported flaws if it could not retrieve the Detailed XML Report. The integration now attempts to retrieve the Detailed XML Report during the next import cycle.
Veracode Azure DevOps Extension version 3.13.0 updates the Flaw Importer task to support importing Software Composition Analysis (SCA) vulnerabilities as work items.
Veracode Integration for Jira Server version 3.35.0 adds a new filter that only imports findings with new scan data, policy changes, or changes to applied mitigations since the last import.
Veracode Azure DevOps Extension version 3.10.0 includes these changes:
Veracode Azure DevOps Extension version 3.5.0 includes these changes:
optargs property to proxySettings. This new name more accurately identifies the valid values for this property. Ensure you update your pipelines with this new property name.Veracode Azure DevOps Extension version 3.4.0 includes these updates:
The Veracode Integration for Jira Cloud version 3.5.0 includes these improvements:
The Veracode Integration for Jira Cloud version 3.3.0 adds these new options for importing findings from Veracode to Jira Cloud:
The Veracode Integration for Jira version 3.23.0 adds these new options for importing findings from Veracode to Jira Server or Jira Data Center:
The Veracode Integration for Jira version 3.22.0 includes these updates:
The Veracode Integration for Jira Cloud version 3.2.0 includes these updates:
This page lists Veracode Analytics updates from 2023 and earlier. For current updates, see Veracode Analytics.
Updates that apply to specific Veracode regions show a region icon.
The new Second Party Component and Fixable (Yes / No) fields in the Veracode Analytics Findings explore are now available.
The new Second Party Component and Fixable (Yes / No) fields in the Veracode Analytics Findings explore are now available in the European Region.
Veracode has upgraded Analytics to use version 22.20 of the Looker platform. All existing dashboards now reflect the new Looker experience.
This upgrade introduces a known issue that prevents you from scrolling in the Timeline visualization. Additionally, you may experience an issue that automatically enables the Row Totals column in some pivot tables, which can cause rows to be double counted in stacked visualizations. To fix this issue, edit the dashboard and visualization, clear the Row Totals option, and save your changes.
The default number of applications displayed in the What is my policy compliance over time? section of the Security Program Overview dashboard in Veracode Analytics has decreased from 100 to 25.
To view additional applications, customize the visualization and adjust the Application Rank by Published Date Descending filter.
Data from Veracode Software Composition Analysis (SCA) agent-based scans and upload scans is now available in Veracode Analytics for the European Region. The predefined Veracode dashboards, including the SCA Findings dashboard, now contain SCA scan data. You can also use the Findings, SCA Agent-Based Scans, and SCA Agent-Based Scan Issues data explores for custom reporting.
Veracode Analytics now provides details about Software Composition Analysis (SCA) findings. If you have an SCA subscription, you can view SCA vulnerabilities displayed in the Findings Status & History dashboard and the Resolution and Mitigation Details dashboard.
Veracode Analytics does not currently display findings from agent-based scans.
This page lists CLI updates from 2023 and earlier. For current updates, see Veracode CLI.
Updates that apply to specific Veracode regions show a region icon.
You can now install the Veracode CLI on Windows with Chocolatey.
The veracode fix command is a new generative AI feature of the Veracode CLI. It uses the results from a Veracode Pipeline Scan to generate suggested code fixes that you can apply to flaws in your application source code. This feature is currently only available in the Commercial Region. To get started, see the quickstart.
Veracode Container Security is available. Container Security is a feature of the Veracode CLI that does the following:
For more information about Veracode Container Security, contact your Veracode account representative.
This page lists DAST updates from 2023 and earlier. For current updates, see Veracode DAST.
Updates that apply to specific Veracode regions show a region icon.
You can now configure web application scans and API scans to use time-based one-time password (TOTP) seeds for URLs that require multi-factor authentication (MFA). You can also configure TOTP with the REST API.
Veracode now offers a free 14-day trial of DAST in the Veracode Platform. To sign up, on the Sign in page, select Sign Up to create your account. If you are a Veracode customer and want to try DAST, contact your sales associate.
DAST is a new Dynamic Application Security Testing (DAST) product that provides rapid and resilient DAST scanning of web applications and REST APIs, a user-friendly interface, and seamless CI/CD pipeline integration. To get started, see the quickstart.
You can now configure web application scans and API scans to use one or more custom cookies for authentication.
Added executable scripts that update the JAVA_HOME path for the endpoint.
You can now use the Dynamic Analysis REST API to set URL scan settings for all analyses and scans in an organization.
Veracode Dynamic Analysis adds a new feature that enables you to manually resume a scheduled analysis from a paused state. This feature is only available upon request. To add this feature to your account, contact Veracode Technical Support.
Veracode has renamed and changed the descriptions for the following URL scan status messages for Dynamic Analysis. The new names more accurately describe the issues that caused these status messages to appear in the Veracode Platform.
Killed - Partial Results Available is now Lockout - Partial Results Available.Killed - Verifying Partial Results is now Lockout - Verifying Partial Results.Internal Scanning Management (ISM) is now available for Veracode Dynamic Analysis of web applications and API specifications in the European region.
Veracode API Scanning adds a new option for using JavaScript to modify an HTTP request, at runtime, when authenticating with a remote host.
When configuring an analysis of a web application, you can now set a threshold for ignoring similar web pages during the analysis.
The Veracode scan engine now creates a verification screenshot if it is unable to log in to a target application after 50 attempts. The screenshot image shows when and where in the scanning process the failed login attempts occurred. You can use this information for troubleshooting.
You can now view detailed information about all past occurrences of both a dynamic analysis and its scans.
Veracode Dynamic Analysis is now available in the European region. If you have a Veracode Dynamic Analysis subscription, you can now perform dynamic analysis security testing and API testing on public-facing web applications and APIs.
When scheduling a Dynamic Analysis, you can now set it to pause and resume scanning at specific days and times. Veracode disabled this option on October 7, 2021.
Dynamic Analysis now provides status messages that indicate when Veracode is verifying partial results and when partial results are available for review. Partial results can occur when a scan stops prematurely due to:
Veracode Dynamic Analysis now supports concurrent browsers for running multiple Dynamic Analysis scans at the same time. When configuring a web application scan, you can specify up to 12 concurrent browsers.
Veracode API Scanning includes these changes:
Veracode Dynamic Analysis can now detect Log4j vulnerability CWE-115 when scanning web applications or API specifications.
The Dynamic Analysis scan engine includes these updates:
For more information, see the endpoint release history
Veracode has improved the scan engine coverage with:
Veracode has released several improvements to the Dynamic Analysis workflow to enhance these user experiences:
keyUp, keyDown, keyPress, assertTextPresent, waitForElementVisibile, and clickAt.veracode.com.out of memory protection.Auto-Publish is now enabled in Veracode Dynamic Analysis to automatically publish some findings, providing quicker results for specific types of vulnerabilities.
Veracode Dynamic Analysis has updated the status definition that displays when any URL scans fail verification for either a connection or authentication issue.
This page lists Veracode eLearning updates from 2023 and earlier. For current updates, see Veracode eLearning.
Updates that apply to specific Veracode regions show a region icon.
Veracode has made these improvements to eLearning:
This page lists Fix updates from 2023 and earlier. For current updates, see Veracode Fix.
Updates that apply to specific Veracode regions show a region icon.
Veracode Fix now provides suggested fixes for JavaScript and TypeScript.
Veracode Fix is now fully supported in the European region.
This page lists Veracode Platform updates from 2023 and earlier. For current updates, see Veracode Platform. For Veracode Analytics updates from 2023 and earlier, see Veracode Analytics - 2023 and earlier.
Updates that apply to specific Veracode regions show a region icon.
Veracode now offers a free 14-day trial of DAST Essentials in the Veracode Platform. To sign up, on the Sign in page, select Sign Up to create your account. If you are a Veracode customer and want to try DAST Essentials, contact your sales associate.
You can now send requests to the Identity REST API from within the Java API wrapper.
You can now provide a proxy host, port, and its credentials in an environment variable. The environment variable name must be https_proxy.
This update includes the following changes:
STOPPED_VERIFYING_PARTIAL_RESULTS and STOPPED_PARTIAL_RESULTS_AVAILABLE.scanpollinginterval are now consistent with any imposed time delays during polling.-includenewmodules parameter.This version includes the following changes:
https_proxy.You can now use the Identity REST API to manage Veracode API credentials for API service accounts, also called API users.
Veracode Java API Wrapper version 23.1.10.5 adds logic to identify and remove unicode application names from the XML response.
Veracode Mobile Application Packager is now End of Life (EOL) and is no longer supported by Veracode Technical Support. To compile and package tvOS or iOS applications that you developed in the Xcode IDE, see the packaging requirements.
Veracode Mobile Application Packager is now deprecated and will be obsolete on February 1, 2023.
Veracode C# API wrapper version 22.10.8.6 includes these updates:
~ ^ ' { }-debug parameter now logs timestamped messages that identify connectivity issues, error conditions, and the status of various composite actions.Veracode Java API Wrapper version 22.10.10.4 now cancels any scans that exceed the upload limit.
The following features are now available in the European Region.
In Veracode Java API Wrapper version 22.9.10.3 the documentation available in the wrapper installation file now describes the Credentials class.
Veracode C# API wrapper version 22.8.8.5 includes these updates:
-debug parameter.uploadandscan.The Auto-Update CWE Top 25 security standard that you use in Veracode policies now reflects the 2022 CWE Top 25 list.
New single sign-on (SSO) and Just-In-Time (JIT) provisioning capabilities in the Veracode Platform improve reliability and supportability and extend the roles that JIT provisioning supports. Before using this feature, you must update your SSO settings in your identity provider.
To begin the process of enabling these capabilities, contact Veracode Support.
Veracode has deprecated the Admin XML APIs for user and team management. End-of-support for these APIs is scheduled for June 30, 2023. Veracode recommends that you begin updating your automations to use the Identity REST APIs. Also, enabling the Single Sign-on and Just-in-Time Provisioning feature automatically disables the Admin XML APIs for user management. Before enabling this feature, ensure all of your automations are using the Identity APIs.
Issues Vulnerability Count now includes only issues where the Issue Type is a Vulnerability Issue. In the past, this measure included the count of Vulnerability, License, and Library issues. The calculation of Issues Vulnerability Count is still based on the filters you select.
-deleteincompletescan Parameter with Backward CompatibilityJava API Wrapper version 22.5.10.1 updates the -deleteincompletescan parameter to be backward compatible with Java API wrapper versions earlier than 22.5.10.0, which released on May 4, 2022. After upgrading the wrapper, the parameter value automatically changes from boolean to an integer:
true, the value changes to 1.false, the value changes to 0.Veracode has added sandbox information to the Unsubmitted Static Scans data export to make it easier to find the incomplete static scans for an application.
Veracode will no longer support Microsoft Internet Explorer 11 after June 30, 2022. This change follows the Microsoft updates to its support model for Internet Explorer. Veracode recommends that you switch to a supported browser to avoid issues.
The Veracode Docs are updated to confirm that Microsoft Edge is a supported browser.
-deleteincompletescan ParameterJava API Wrapper version 22.5.10.0 includes changes to the -deleteincompletescan parameter for deleting incomplete scans when running the uploadandscan action. This parameter now accepts an integer value, rather than boolean, for deleting an incomplete scan based on the scan status.
These changes are not backward compatible with the -deleteincompletescan parameter available in earlier versions of the Java API Wrapper. If you currently use this parameter, after upgrading the wrapper you must change the value from boolean to one of the accepted integer values.
You can now raise a support case and schedule a consultation from the Veracode Platform in the European Region.
Applications and policies for the European Region now run on the current versions in the Veracode Platform.
You can now view the date and time of the most recent event that triggered a policy evaluation for an application in a new field in the Applications REST API and the Applications list in the Veracode Platform. You can use this field to search for applications that have had new scans or approved mitigations since the listed date.
maxretrycount parameter to now retry requests that fail due to certain error conditions. Previously, this parameter polled for failed build status and only applied to the uploadandscan action.Veracode Java API Wrapper version v21.2.7.5 includes these changes:
deleteincompletescan parameter for automatically deleting scans that did not complete due to one or more errors.You can now include evaluation timeframes in Veracode application security policies to define when findings can impact policy compliance. In your policies, you can:
Veracode no longer supports these legacy versions of Safari and Android because of their use of weak ciphers (TLS 1.2):
Safari 6 on iOS 6.0.1
Safari 7 on iOS 7.1
Safari 8 on iOS 8.4
Safari 7 on OS X 10.9
Safari 8 on OS X 10.10
Android 5.0.0
Android 6.0
You cannot access analysiscenter.veracode.com using these browsers.
This video shows you how to:
debug parameter in your command to show this diagnostic information in the output.Veracode now provides these REST APIs:
You can now perform these tasks with the Veracode Findings REST API:
Veracode now provides these products as container images on Docker Hub:
Veracode has updated policy rules that include the OWASP Mobile security standard to reflect additional research. OWASP Mobile policy rules now include these CWEs: CWE-77, 78, 80, 252, 287, 319, 345, 404, 415, 416, 601, 614, 676, 693, 757.
Applications that contain these flaws may fail OWASP Mobile policy rules as a result of this update. Veracode will apply the update upon rescan of the application.
Rolling sandbox histories let you limit sandbox data by restricting the number of retained scans for each sandbox to 15. After more than 15 scans, the Veracode Platform deletes the oldest scan, though the data remains available through Veracode Analytics. If enabled, this feature replaces the previous data limitation method of expiring old sandboxes.
To request access to rolling sandbox histories, contact Veracode Technical Support.
deleteuser.do, deleteteam.do, deleteapp.do, and removefiles.do XML API calls now return an HTTP 200 response and a change summary, instead of a list of the items remaining after the deletion.Veracode now provides reporting based on CWE version 4.1 definitions, which changes the names and descriptions of a few existing CWE categories. The complete list of changes in CWE version 4.1 is available from the MITRE website. This new version does not impact the CWE mappings for the OWASP, CWE Top 25, or CERT security standards.
MITRE is updating their CWE list on a more frequent basis, but Veracode remains committed to staying up-to-date with each new version. As MITRE updates their CWE database, you might notice periodic changes in Veracode reports, such as differences between parent-child relationships or mappings.
deletesandbox.do and deletebuild.do XML API Callsdeletebuild.do and deletesandbox.do XML API calls, these calls now return an HTTP 200 response and a summary of the deleted items, instead of a list of items remaining after deletion. These calls also use new schema files.-credprofile parameter to specify the profile to use for Veracode authentication. The existing -vid and -vkey parameters, for specifying your API credentials at the command line, are now optional.-credprofile parameter to specify the profile to use for Veracode authentication. The existing -vid and -vkey parameters, for specifying your API credentials at the command line, are now optional.Veracode has updated the values for industries in application profiles to more accurately reflect the market. Because applications include industry values to help inform the Veracode State of Software Security report, this change affects the createapp.do and updateapp.do XML API calls.
If you have a script coded with an expected value for the industry field, please update your script to reflect the updated values or use the default value already provided.
Veracode eLearning has released a new set of secure coding foundation courses:
These courses cover application security practices and associated vulnerabilities.
Veracode has improved these eLearning windows:
Updated Applications List View
Veracode has made these improvements to developer sandboxes:
Veracode eLearning has released a new set of secure coding courses for JavaScript:
These courses cover application security practices and associated vulnerabilities, including the OWASP Top Ten, and secure coding techniques in JavaScript, including using the AngularJS and ReachJS frameworks.
Veracode has implemented these changes to improve the performance of sandbox scans:
This page lists SAST updates from 2023 and earlier. For current updates, see Veracode SAST.
Updates that apply to specific Veracode regions show a region icon.
The new COBOL scanner for Veracode Static Analysis includes advanced pattern recognition and static analysis techniques, allowing for more accurate and efficient detection of security vulnerabilities in COBOL code.
The improved detection may result in the identification of additional vulnerabilities and potential threats. The updates may also impact flaw matching for your applications. If you need help resolving these changes, contact Veracode Technical Support.
All COBOL scans now use the upgraded scanner.
More details are available in the Veracode Community.
jsonify cleanser support for flaw class CWE-80 (Improper Neutralization of Script-Related HTML Tags in a Web Page (Basic XSS))Veracode has deprecated support of .NET cleansers for the following functions for flaw classes CWE-93, CWE-113, and CWE-117:
These cleansing functions are insufficient for addressing their targeted flaw classes and better alternatives are available.
For more details on why Veracode deprecated support for these functions and how to protect your applications against CRLF injection attacks, see the Veracode Community.
In last month’s release, Veracode added improved support for CWE-798 (Use of Hard-coded Credentials) detection. However, a bug in the pattern matching caused a significant number of false positives for some users. Veracode has resolved this issue and the improvement should result in significantly fewer CWE-798 false positives.
produces annotation attributeVeracode has added support for Quarkus, a Kubernetes-native Java stack tailored for OpenJDK HotSpot and GraalVM.
Veracode has improved static analysis by adding support for these new versions of supported technologies:
Improvements to the detection methods Veracode uses to identify CWE-259 (Use of Hard-coded Password), and CWE-798 (Use of Hard-coded Credentials) vulnerabilities should reduce the number of false positives during static analysis. Improved CWE-259 coverage for Python language submissions.
Veracode has added support for Micronaut 3.8.x, which is a JVM-based framework you use to build lightweight, modular applications.
Veracode has improved static analysis by enhancing support for Android 12.
Veracode has improved static analysis by adding support for these new versions of supported technologies:
Improvements to the detection methods utilized to identify CWE-259 and CWE-798 vulnerabilities should reduce the number of false positives found during static analysis.
Veracode has added an additional CWE-693 (Protection Mechanism Failure) check for Android applications to ensure that the Play Integrity API is used appropriately.
Veracode improved static analysis by adding support for these new versions of supported technologies:
The improved coverage increases the number of potential CWE-89 flaws that Veracode discovers in Java and JavaScript/TypeScript applications, which might affect your scan results.
Veracode has added CWE-451 (Tapjacking) coverage for Android applications.
Pipeline Scan adds a new --include parameter. You use this parameter to specify the top-level modules to include during scanning. The scan results now show both the modules that Veracode identified during prescan and the modules included in the scan.
This update is available with Veracode CLI version 23.4.3-0 and Veracode Docker image version 23.4.3.
Veracode improved static analysis by adding support for these new versions of supported technologies:
Static analysis of Python applications inaccurately reports certain CWE-918 (Server-Side Request Forgery (SSRF)) flaws as CWE-201 (Insertion of Sensitive Information Into Sent Data) flaws. This update recategorizes these incorrectly reported flaws as CWE-918. This update might impact existing flaw matching and you might need to apply new mitigations to these flaws.
After you apply this update, any Python applications that contain CWE-201 flaws and have any of the following policy requirements might fail your security policy:
Security Standard rule for Auto-Update CWE Top 25
Findings by Severity rule for Medium or higher
Minimum Scan Score rule
Veracode improved static analysis by adding support for these new versions of supported technologies:
Veracode has improved static analysis for WebMethodAttribute use in ASP.NET Classic (non MVC and/or MVC Core) WebForms and WebServices. This will affect the flaws found and associated policy results for customers by reducing the number of FPs found.
Veracode improved static analysis by adding support for these new versions of supported technologies:
Veracode no longer reports parser errors in standalone copybook files that COBOL files do not include. These files are not relevant for security scanning unless COBOL files reference them.
Veracode improved static analysis by adding support for these new versions of supported technologies:
Veracode has improved static analysis by adding support for:
Veracode has released a new version of our new iOS packaging tool:
Veracode improved static analysis by adding support for these new versions of supported technologies:
Veracode improved static analysis by adding support for these new languages and frameworks:
Veracode has improved static analysis by adding a new iOS packaging tool to support Xcode 14 without the Enable_Bitcode setting:
Veracode improved static analysis by adding support for these languages and frameworks:
Veracode improved static analysis by adding support for these languages and frameworks:
You can use the new Veracode Packaging Cheat Sheet to generate language-specific packaging guidance for Static Analysis.
Veracode improved static analysis by adding support for these languages and frameworks:
Veracode has improved static analysis by adding:
Veracode has improved static analysis by adding:
Veracode has improved static analysis by adding:
Veracode has improved static analysis by adding:
Veracode has improved static analysis by adding:
Veracode has improved static analysis by adding:
Veracode has improved static analysis by adding support for these new versions:
Veracode has improved static analysis by adding:
Veracode has improved static analysis by adding support for these new versions:
Veracode has improved accuracy of hard-coded Passwords. You can expect:
Veracode has improved modeling for TypeScript support. You can expect:
Veracode has improved static analysis by adding support for:
Veracode has improved static analysis by adding:
The Veracode European Region is now available for new customers. This region, which initially supports Veracode Static Analysis and Veracode Software Composition Analysis, provides European data residency for Veracode customers.
Veracode has improved static analysis by adding:
Veracode has made several improvements to static analysis, including:
Veracode has improved static analysis by adding support for these new technologies:
On April 1 2021, Veracode will no longer support versions of pipeline-scan.jar that you have downloaded before September 2020. These versions are 20.9.1 and earlier. To identify the version of the pipeline-scan.jar that you are using, you can run it with the --version option at the command line.
To transition to a supported version of the JAR file, replace the version that you are using with the latest one, which you can download here: https://downloads.veracode.com/securityscan/pipeline-scan-LATEST.zip Veracode also provides Pipeline Scan as a Docker image on ##### Docker Hub](https://hub.docker.com/r/veracode/pipeline-scan).
Updating to the latest version of pipeline-scan.jar ensures that you are working with the latest version of the Veracode software, which includes many new features and bug fixes.
Veracode has improved static analysis by adding support for these new versions of supported technologies:
Veracode has improved static analysis by adding initial support for these versions of supported technologies:
Veracode has improved static analysis by adding support for these new technologies:
Veracode provides these improvements for supported technologies:
Veracode has improved warning messages to identify applications that do not meet Veracode packaging requirements.
Veracode has also improved the accuracy of warning messages for several languages and file types by providing more descriptive error resolution recommendations.
Veracode has improved static analysis of Java web applications packaged as WAR and EAR files. Veracode provides more consistent results between subsequent scans and more accurately recognizes first-party components in the applications.
You may notice a one-time change to scan results as a result of this improvement.
Veracode has improved static analysis by adding support for these new versions of supported technologies:
Veracode has improved its warning messages to notify you when the JavaScript and TypeScript files you submit have parsing errors. Parsing errors can affect the quality of the prescan results.
Veracode has also improved the accuracy of warning messages for several other languages and file types.
Veracode has improved static analysis of these supported technologies:
New Pipeline Scan Reporting Options:
Veracode has improved pipeline scans to include these enhancements:
Veracode has added support for new versions of these technologies:
Veracode has improved static analysis of AWS SDK for JavaScript.
Veracode has improved static analysis of .NET and JVM-based applications. Veracode reduced the number of prescan warning messages that it sends for components that are common third-party libraries.
Veracode has added static analysis support for these technologies:
As a result of updated security research, Veracode has added several CRLF cleansing functions to the list of supported cleansing functions. Veracode also removed these CRLF functions:
com.google.gwt.safehtml.shared.SafeHtmlUtils.htmlEscapecom.google.gwt.safehtml.shared.SafeHtmlUtils.htmlEscapeAllowEntitiescom.google.gwt.safehtml.shared.SafeHtmlUtils.fromStringorg.springframework.web.util.HtmlUtils.htmlEscapeorg.springframework.web.util.HtmlUtils.htmlEscapeDecimalorg.springframework.web.util.HtmlUtils.htmlEscapeHexorg.apache.axis.components.encoding.XMLEncoder.encodecom.liferay.portal.kernel.util.HtmlUtil.escapeAttributecom.liferay.portal.kernel.util.HtmlUtil.escapecom.liferay.portal.kernel.util.HtmlUtil.escapeHREFcom.liferay.portal.kernel.util.HtmlUtil.escapeXPathVeracode has improved the user experience of static analysis by providing:
Veracode Static Analysis using pipeline scanning includes these enhancements:
--gl_issue_generation--gl_vulnerability_generationVeracode has added static analysis support for these technologies:
Veracode has improved static analysis of these technologies:
This video shows you how to:
Veracode has added static analysis support for these technologies:
Veracode has improved static analysis of these technologies:
Veracode Static Analysis using pipeline scanning includes these enhancements:
--app_id--development_stageVeracode now supports static analysis of these libraries for Apex:
Veracode now supports static analysis of these technologies:
Veracode has updated policy rules that included entries for CWE 100 and CWE 391 to include the new CWEs.
After you run the next scan of affected applications, the Veracode Platform reports and analytics reflect the new CWE values. Data for previous scans still include the historical values.
Veracode static analysis using pipeline scanning now includes these features:
Veracode has improved static analysis of these technologies:
Veracode has changed reporting of CWE 404 flaws to be more specific about where they occur, which may result in additional findings. Veracode has also changed the severity of CWE 404 to Informational.
Veracode has improved static analysis of these supported technologies:
Veracode has improved static analysis by adding support for these new versions of supported technologies:
Veracode has improved static analysis of these supported technologies:
This page lists SCA updates from 2023 and earlier. For current updates, see Veracode SCA.
Updates that apply to specific Veracode regions show a region icon.
The SCA agent can now scan target directories that contain spaces when SRCCLR_NO_GIT is set to 1.
Veracode has added data from the Cybersecurity & Infrastructure Security Agency's Known Exploited Vulnerabilities (KEV) catalog to the SCA Agent Issues APIs and the Findings API. See Understanding SCA exploitability information for more details.
Veracode has released the SCA App-Linking REST API. You can use this API to link a project for SCA agent-based scans to an application profile. The linked application profile receives all libraries, licenses, and discovered vulnerabilities from that project, along with all results from SCA Upload scans. To link a project, use the linkAppProject endpoint. To unlink a project, use the unlinkAppProject endpoint.
Veracode has fixed an issue that prevented the SCA agent from cleaning up local scan directories and added enhancements to the agent that will be used in the future for scanning Java projects.
Veracode has added enhancements to the SCA agent that will be used in the future for scanning Java projects.
Veracode has added several enhancements and fixes to the SCA agent.
Veracode has added enhancements to the SCA agent that will be used in the future for scanning Java projects.
Veracode has released the SCA Annotations REST API. This API includes the getSCAannotations endpoint to retrieve comments and mitigations applied to findings from SCA upload scans and the createSCAannotations endpoint to annotate SCA upload findings, including adding comments and proposing, accepting, and rejecting mitigations.
The SCA Annotations API specification is available on SwaggerHub.
This API is not part of the Annotations API, which works with findings from Static Analysis and Dynamic Analysis.
Veracode has added data from the Exploit Prediction Scoring System (EPSS) to the Findings REST API. See Understanding SCA exploitability information for more details.
Veracode has fixed an issue that caused a null pointer exception when performing an agent-based scan on some projects.
Veracode has fixed an issue impacting the calculation of Fix By dates in sandbox scans. Previously, SCA used the scan date or the scan promotion date as the date that a component was first found, causing the Fix By date to be pushed out continuously. This fix is not retroactive and only impacts scans completed after Sept 27, 2023.
The new Unified Policy feature allows you to assign policies to workspaces used for SCA agent-based scans. Like the existing agent rules, you can use policies to create issues and break your build based on certain criteria. See more details about applying rules to a policy, assigning policies to agent-based workspaces, and setting default policies.
Veracode will migrate customers from agent rules to Unified Policy in batches and will retire agent rules before April 1, 2024.
Because the National Vulnerability Database stopped supporting CVSS v2 in July 2022 and most users have moved to v3, the Library and Vulnerability pages of SCA's agent-based scan user interface now display CVSS v3 scores, instead of v2. You must clear the cache in your web browser to see these changes.
To also display CVSS v3 on the workspace Issue pages and the project Issue tab, you must update your agent rules to use CVSS v3.
Veracode has improved the performance of the SCA agent by optimizing how it handles dependencies with very complicated and intertwined dependency graphs.
Veracode has added data from the Exploit Prediction Scoring System (EPSS) to the SCA Agent REST APIs. See Understanding SCA Exploitability Information for more details.
Veracode has added the following enhancements to SCA scanning for .NET applications:
deps.json and project.asset.json files.--quick scans on NuGet projects.Veracode has released the getApplicationProjects API to allow users to retrieve a list of SCA agent projects that are linked to a specific application. Users who have rights to call the getApplications API may also call the getApplicationProjects API.
Veracode has expanded the list of roles that are allowed to call the CycloneDX Software Bill of Materials (SBOM) API and the SPDX SBOM API. See the SBOM API instructions for application profiles and agent-based projects for details.
The Vulnerabilities section of the Summary Report that appears in your CLI after an SCA agent-based scan now displays CVSS v3 severities, instead of v2.
The Issues section still displays CVSS v2 severities by default, but you can edit the severity in your agent-based scanning rules to reflect v3. If you have not modified your rules to use CVSS v3, Veracode recommends setting up organization-level rules to avoid having to edit rules on every workspace individually.
Veracode has added support for NPM lockfile format version 3. See Run an Agent-Based Scan for NPM or JavaScript and TypeScript Packaging for details.
Veracode has fixed an issue causing SCA agent-based scans of Yarn projects to erroneously fail.
Veracode has upgraded the Java Runtime Environment (JRE) for the SCA agent from version 11 to 17.
Veracode has added GNU Privacy Guard (GPG) signature files to all SCA agent downloads to verify you are downloading a valid version.
Veracode has resolved an issue impacting the scope parameter for SCA agent-based scans of NPM projects.
Veracode has added the following enhancements to the SCA agent:
You can now specify a date for Veracode to stop ignoring issues from SCA agent-based scans.
Veracode has added the following enhancements to SCA scanning for Go projects:
Veracode SCA has improved agent-based scan support for projects that contain Java 17 features.
Veracode Software Composition Analysis (SCA) upload scans now support displaying updated severity ratings that more closely match the National Vulnerability Database (NVD) severity ratings. To enable this feature for your account, contact Veracode Technical Support.
You can now choose to accept the risk of specific vulnerabilities and licenses as part of your mitigation process for Veracode SCA upload scans. This mitigation type is already available for Veracode Static Analysis and Dynamic Analysis.
Veracode SCA agent-based scans now include a region flag that you can use to configure accounts in the European or United States Federal region.
Veracode has upgraded the Java Runtime Environment (JRE) that is bundled with the Software Composition Analysis (SCA) agent.
Veracode Software Composition Analysis (SCA) agent-based scans now more effectively locate local Python 3 installations.
You can now use the Veracode SCA Agent REST API to create a software bill of materials (SBOM) in SPDX JSON format from the results of your Veracode SCA upload scans.
Veracode Software Composition Analysis (SCA) now supports scanning Android projects. This support includes AAR files for agent-based scans and APK and AAB files for upload scans.
Veracode Software Composition Analysis (SCA) now supports aliases in Go projects. This support includes agent-based and upload scans.
Veracode SCA agent-based scanning now supports vulnerable method analysis for Java 17.
You can now set the source code management (SCM) URI as your project name using the --uri-as-name option in your Veracode SCA agent-based scans.
You can now use the Veracode SCA Agent REST API to create a software bill of materials (SBOM) from the results of your Veracode SCA agent-based scans that you have linked to an application profile. The API generates an SBOM in CycloneDX JSON format.
You can now use the Veracode SCA Agent REST API to create a software bill of materials (SBOM) from the results of your Veracode SCA agent-based scans. The API generates an SBOM in CycloneDX JSON format.
You can now generate a software bill of materials (SBOM) for Veracode SCA upload scans that have been promoted from sandbox to policy scans. The Veracode SCA Agent REST API includes promoted sandbox scan results when it returns a CycloneDX SBOM for an application.
Veracode has removed the Number of Known Vulnerabilities by Severity column from the Applications table on the Upload and Scan page in the Veracode Platform. This update significantly reduces load times for the page. You can still view the number of known vulnerabilities by severity for each application in the application profile.
You can now use the Veracode SCA Agent REST API to create a software bill of materials (SBOM) from the results of your Veracode SCA upload scans. The API generates an SBOM in CycloneDX JSON format.
Veracode Software Composition Analysis (SCA) now provides the CVSS version 3 score in the JSON CLI output of your agent-based scan results. To use this feature, you must upgrade your Veracode SCA agent to version 3.7.77 or later.
The Veracode European region is now available for new customers. This region, which initially supports Veracode Static Analysis and Veracode Software Composition Analysis, provides European data residency for Veracode customers.
You can now set your Veracode Software Composition Analysis projects to automatically update their default branch to be the most recently scanned branch or tag. This enhancement enables the use of tags as default branches and reduces the number of issues that display in the Veracode Platform, by default.
Existing projects without a default branch selected in their project settings now use the Use Last Scanned option as the default branch.
The Veracode Vulnerability Database is updated to resolve a discrepancy in severity rating compared to the National Vulnerability Database (NVD) for approximately 200 of over 20,000 total vulnerabilities. Veracode has already contacted all organizations that have applications that fail policy as a result of this update.
If your Veracode account manager has not contacted you, you do not need to take any action.
This video shows you how to: