gitlab gitlab-org/security-products/dast v2.0.3

latest releases: v4.0.31, v4.0.30, v4.0.29...
2 years ago
Changes
  • Users can configure the browser-based scans to wait for a navigation to complete with DAST_BROWSER_NAVIGATION_TIMEOUT (!486)
  • Users can configure the browser-based scans to wait for an action to complete with DAST_BROWSER_ACTION_TIMEOUT (!486)
  • Users can configure the browser-based scans to wait for the DOM to be stable with DAST_BROWSER_STABILITY_TIMEOUT (!486)
  • Users can configure the browser-based scans to wait for the DOM to be stable after a navigation with DAST_BROWSER_NAVIGATION_STABILITY_TIMEOUT (!486)
  • Users can configure the browser-based scans to wait for the DOM to be stable after a browser action executes with DAST_BROWSER_ACTION_STABILITY_TIMEOUT (!486)
  • Users can configure the browser-based scans to restrict how long to spend searching for elements for analysis with DAST_BROWSER_SEARCH_ELEMENT_TIMEOUT (!486)
  • Users can configure the browser-based scans to restrict how long to spend extracting for elements for analysis with DAST_BROWSER_EXTRACT_ELEMENT_TIMEOUT (!486)
  • Users can configure the browser-based scans to wait for an element to be considered ready for analysis with DAST_BROWSER_ELEMENT_TIMEOUT (!486)
  • Upgrade Browserker to version 0.0.36 (!486)
    • Return an internal error to user in the event a scan gets stuck for more than 15 minutes browserker!264
    • Allow user to configure how long to wait for a navigation to complete with --navigationtimeout browserker!264
    • Allow user to configure how long to wait for searching elements with --searchelementtimeout browserker!264
    • Allow user to configure how long to wait for extracting elements with --extractelementtimeout browserker!264
    • Allow user to configure how long to wait after executing a browser action with --actiontimeout browserker!264
    • Allow user to configure how long to wait for elements to be considered ready for analysis with --elementreadytimeout browserker!264
    • Allow user to configure how long to wait for the DOM to be stable with --stabilitytimeout browserker!264
    • Allow user to configure how long to wait after a navigation with --waitafternavigation browserker!264
    • Allow user to configure how long to wait after an action with --waitafteraction browserker!264
    • Add vulnerabilities[].evidence.request.url to the secure report browserker!260
  • Upgrade Browserker to version 0.0.37 (!487)
    • Selectors use an ID, name or css selector by default when the selector type is not set browserker!271

Don't miss a new dast release

NewReleases is sending notifications on new releases.