Release Notes
Invicti Enterprise On-Premises
RSS FEED
Improvements
- Updated .NET 8 runtime to fix a security issue (CVE-2025-55315)
Notes for Verifying the Hash Value for Package Integrity in Invicti Enterprise On-Premises
The hash value for the "25.9.1.zip" file is provided below. You can verify the integrity of the file by checking its hash value using one of the outlined methods:
Release Package Hash Value: 8A7AB79A55F3EDA9CB0ED822CE73D42B0655806191B40F7BD7B44657B1490F7F
Methods to Verify the Hash Value:
PowerShell (Windows):
Get-FileHash -Path "25.9.1.zip" -Algorithm SHA256
Command Prompt (Windows):
certutil -hashfile "25.9.1.zip" SHA256
Linux or macOS:
sha256sum "25.9.1.zip"
New features
- LDAP Integration: Permanently enabled LDAP integration for on-premise WebApp installations by removing its associated feature flag. LDAP functionality is now available by default
- Added Post-Request Script feature (Read more)
- Added API GET method to retrieve scheduled scans by ID
Improvements
- Updated plugin dependencies to address known security vulnerabilities and improve overall stability; upgraded Jenkins compatibility to version 2.474
- Increased the timeout duration for IAST responses to prevent premature failures
- When user roles changes details are now available on Activity Logs
- Jenkins Plugin: Corrected misleading UI validation for the “Report Type” parameter within the “Netsparker Enterprise Scan” build step. The field no longer incorrectly appears as required, clarifying its optional nature
- Added validation to ensure base scan file existence before initiating Incremental or Retest scans, preventing potential scan failures due to missing dependencies
- Improved design of Authentication Verifier Service page
- Added support for configuring the temp file via appsettings.json or an environment variable
- Updated workflows to improve reliability and security while maintaining alignment with GitHub’s best practices
- Updated the Jenkins plugin script generation to use the latest GitHub Actions versions and ubuntu-latest runner for improved compatibility and security
- Addressed multiple versions of GitHub Actions available in the marketplace
- Improved incremental scanning
- Implemented an enhancement to capture the token information present in the response during the OAuth2 Implicit Flow
- Added new REST API endpoint (agents/listverifiers) to retrieve AV agents data
- Implemented an enhancement to enable more effective cookie management when HTTP/2 is enabled
- Updated Microsoft.OpenApi to version 2.0 preview to support OpenAPI 3.1.0 for improved API scanning
- Agent and Verifier download names now come in certain format
- Minor security patch for the Authentication Verifier service
- Improved suspend mechanism in JIRA integration
Resolved issues
- An improvement has been made to allow multiple secrets to be used simultaneously within a single custom header
- File Uploads: Expanded the allowed MIME types for ZIP file uploads to include application/zip and application/x-zip. This resolves issues where ZIP files uploaded from certain operating systems (e.g., Mac/Linux) were not recognized due to variations in reported MIME types
- Resolved an issue where duplicate X-Content-Type-Options headers triggered false missing header reports
- Resolved discrepancy between API (listByWebsite) and UI (Recent Scans) results
- Fixed an issue with verifying the existence of links in the link pool
- Resolved an issue where SSL certificate chain errors blocked UI or auto-update of Internal Verifier Agents on Linux
- Implemented logic to create the UserDocumentsDirectoryPath when it doesn't already exist
- Added support for defining headers and HTTP method during CSV import
- Resolved an issue where multiple versions of Next.js were not properly displayed in the Technologies dashboard and Scan Reports
- Added a note for values requiring wrap-around quotes in API
Notes for Verifying the Hash Value for Package Integrity in Invicti Enterprise On-Premises
The hash value for the "25.7.0.zip" file is provided below. You can verify the integrity of the file by checking its hash value using one of the outlined methods:
Release Package Hash Value: 2329F1F9F3E23D25AB8CAD4194F4CFBE0C98EBF411D9658A773D285A1931EAE4
Methods to Verify the Hash Value:
PowerShell (Windows):
Get-FileHash -Path "25.7.0.zip" -Algorithm SHA256Command Prompt (Windows):
certutil -hashfile "25.7.0.zip" SHA256Linux or macOS:
sha256sum "25.7.0.zip"
New features
- Implemented webapp for secure storage and retrieval of passwords for Pre-Request scripts
- Added an integration for NTA with NGINX (Read more)
Improvements
- Implemented default limit setting to 1000 without flag for all fields except Second Level Domains
- Implemented custom field Parent option in integration with Azure Boards
- Implemented agent for secure storage and retrieval of passwords for Pre-Request scripts
Resolved issues
- Resolved an issue on the Technologies Dashboard
- The 'Tags' filter in All Issues now works correctly when using the 'Not Contains' condition
- Resolved issue where no results appeared when filtering the target list on the Target Group page. This was linked to the 'View Target List' permission
- Resolved communication issues in the TestBasicAuthCredentials process and improved HTTP connection handling
- Resolved an issue where not all attributes were exported correctly from the Issues page
- Fixed an issue with Bad Request Response on Scan Summary
- Fixed naming issues of WordPress plugin Contact Form 7
- Fixed the issue of LoginRequiredUrl and Pre-Request script requests causing bottlenecks in HTTP requests
- Fixed an issue that unnecessarily included the code parameter in OAuth2 authorization requests
- The scanning engine now correctly processes merged request headers received from browser
- Resolved an issue where scans using cloud agents would occasionally fail after extended runtimes with an "agent unavailable" error
Notes for Verifying the Hash Value for Package Integrity in Invicti Enterprise On-Premises
The hash value for the "25.5.0.zip" file is provided below. You can verify the integrity of the file by checking its hash value using one of the methods outlined above:
Release Package Hash Value: F89BE5A51ACC8F1AC6AAE11A620B95B208FE26C9F128FCA297A65E45796E7C61
Methods to Verify the Hash Value:
PowerShell (Windows):
Get-FileHash -Path "25.5.0.zip" -Algorithm SHA256Command Prompt (Windows):
certutil -hashfile "25.5.0.zip" SHA256Linux or macOS:
sha256sum "25.5.0.zip"
New features
- Added an option to prevent reopening Issue Tracker issues when a vulnerability is marked as False Positive and later revived (Read more).
- Added the ability to reset the issue state to its default
Improvements
- Requests with empty or default values are not sent to DeepInfo
- Introduced a new setting under the Account General settings, within the Data Privacy and Security section, to modify the X-AMZ-Expires parameter while downloading the scan data
- Enhanced the "Configure New Agent" page to include additional details for auth verifier agents (Read more)
- Updated remediation details for outdated AngularJS versions
- [BREAKING CHANGE]: Updated the Docker agent's compression method and file extension; ensure any automation or scripts referencing the old format are updated accordingly.
- Enhanced the locally hosted web app in isolated networks to prevent unnecessary rerouting through Google reCAPTCHA
Resolved issues
- Fixed an issue where the Issue note field could not be updated
- Fixed inefficient algorithmic complexity in DotNet IAST Sensor
- Resolved the issue where an invalid character response occurred when attempting to add a user
- Resolved the "Invalid Target URI" error that occurred when editing the Target URI to end with multiple slashes (///) on the new scan page
- Resolved the issue where the scan profile was not updating with the support account
- Fixed restrictions for JIRA integration
- Fixed an issue where pressing "Enter" instead of clicking the "Check" button during password verification triggered a full scan instead of the intended login verification
- Updated Chromium and Node.js versions, resolving Chromium-related issues, including the unexpected increase in Chromium count
- Exclude URL rules now function correctly even when the excluded URL is the target
- Fixed an issue with retrieving OAuth2 token data from JSON responses
- Fixed an exception caused by an invalid Target URI in scheduled scans
- Fixed an issue where proxy credentials were not encrypted when launching InvictiProxy
- Fixed inconsistent styling in the report policy, ensuring uniform formatting in the vulnerability profile sections
Notes for Verifying the Hash Value for Package Integrity in Invicti Enterprise On-Premises
The hash value for the "25.4.0.zip" file is provided below. You can verify the integrity of the file by checking its hash value using one of the methods outlined above:
Release Package Hash Value: 0DA0E72DE19A6ABE85BCF9B5E659C5776F8FE11700F06D3214B1993C6334A0E5
Methods to Verify the Hash Value:
PowerShell (Windows):
Get-FileHash -Path "25.4.0.zip" -Algorithm SHA256Command Prompt (Windows):
certutil -hashfile "25.4.0.zip" SHA256Linux or macOS:
sha256sum "25.4.0.zip"
New features
- Added support for encrypting proxy credentials settings in the agent appsettings.json file
Improvements
- Improved technology version detection from URI
- Scheduled group scans will be initiated in chunks when exceeding 500 websites
- The SelfDisable command is no longer sent to the Agent when its state is updated to Disabled.
- Fixed the issue to enable compatibility with the latest version of GitHub Actions
- Scheduled scans now remove the URL path after ‘#’ when using the default Scan Profile
- Added a loading state for the Export CSV button to prevent multiple clicks
- Improved multiple technology reporting on the same location.
- Improved signatures for Axios and PrototypeJs detection.
- Upgraded 3rd party script libraries
- Updated OpenSSL from version 3.3.1 to 3.3.2
- Added AttackUsage to DOM XSS Patterns
- Updated the Splunk Python SDK for the Splunk Plugin to ensure compliance with the latest Splunk Vetting Policy
- Improved value filling in GraphQL queries
Resolved issues
- Fixed an issue where the agent was duplicated on premises when using a cloud provider
- Fixed an issue where "Test Scripts" under Form Authentication in a scan profile failed to load responses
- The Validate Imported Links API endpoint no longer requires a Target URL when a file is uploaded
- Fixed an issue where changing the website associated with a profile disrupted the settings, configurations, and scan tasks
- Fixed an issue where past scans would not load in Invicti Standard 25.1
- Fixed sorting issues in the dashboard to use numerical order instead of alphabetical
- Fixed an issue where an insecure deserialization vulnerability in Invicti scan files could allow the execution of arbitrary code upon scan import
- Fixed an issue where 'LaunchInstance' errors caused GUIDs to be stored instead of AWS-generated instance IDs in the database
- Fixed an issue that caused the Mend vulnerabilities to be reported with incorrect severity
- Fixed the issue which was causing exports from Invicti Standard to Invicti Enterprise On-Premises to fail
- Resolved an issue where LDAP synchronization would fail if a group member was missing an email address; the member is now skipped in such cases
- The issue preventing the use of the Chromium Extension in Scanner and Verifier Agent has been resolved
Notes for Verifying the Hash Value for Package Integrity in Invicti Enterprise On-Premises
The hash value for the "25.3.0.zip" file is provided below. You can verify the integrity of the file by checking its hash value using one of the methods outlined above:
Release Package Hash Value: E51A9053B751AA6247D684AC89F2F382E0029D506ECC2C0C71BB0C6BC3F81DD2
Methods to Verify the Hash Value:
PowerShell (Windows):
Get-FileHash -Path "25.3.0.zip" -Algorithm SHA256Command Prompt (Windows):
certutil -hashfile "25.3.0.zip" SHA256Linux or macOS:
sha256sum "25.3.0.zip"
New Features
- Added single-tab crawling for websites that do not allow multiple-tab browsing
- Upgraded the Shortcut integration API endpoint to v3
Improvements
- Added Customizations folder to the Agent Output folder
- Removed Feature flag and implementation for ‘INV-5855-HashiCorp-Vault-TLS-certificate-authentication-support-enabled’ flag
- Improved the performance of searching by profileName on the Scan-Index page
Resolved issues
- Updated APIHub npm package to the latest version
- Resolved scan authentication issues for multiple pages
- Resolved issues related to screenshots and login processes
- Fixed Dashboard Widget Active Issue is empty when selecting a specific target
- Fixed the problem of reverting vulnerability in issue update endpoint to default
- Fixed removes preferred agent group in update-scheduled API endpoint
- Fixed an auto-update issue for Verifier Agent
- Added control for URLs that should not be included in the scope
- Upgraded the Shortcut (Clubhouse) integration
- Resolved an issue caused by the Chromium version update by updating Chromium dependencies for the Linux operating system. Refer to the updated scripts to install the required dependencies for Headless Chrome. (Read more)
Notes for Verifying the Hash Value for Package Integrity in Invicti Enterprise On-Premises
The hash value for the "25.2.0.zip" file is provided below. You can verify the integrity of the file by checking its hash value using one of the methods outlined above:
Release Package Hash Value: DB85D47E9796F0366B0AC8F3AA8F61FA7200C248B2D05DB6EED76BCA28C8D9F1
Methods to Verify the Hash Value:
PowerShell (Windows):
Get-FileHash -Path "25.2.0.zip" -Algorithm SHA256Command Prompt (Windows):
certutil -hashfile "25.2.0.zip" SHA256Linux or macOS:
sha256sum "25.2.0.zip"
You can use any of the above methods to verify the hash value and ensure the integrity of the "25.2.0.zip" file.
New Features
- Clicking on the scheduled scan icon in the scan summary screen now redirects you to the Recent Scans page with a filtered view, improving navigation and access to relevant scan details
- Implemented an integration that automatically retrieves the latest Container security results from Mend when a DAST scan is initiated
Improvements
- Added a feature flag for enabling unlimited scan duration in On-Premise deployments
- Fixed an issue on the 2FA page where the code text field was not automatically focused upon page load
- Introduces a configurable retention period for HTTP log files, allowing Root users to specify the number of days before log
- Implemented a restriction to prevent the modification of the Vulnerability Signature Type
- Enhanced the UI to highlight the menu when API Hub specifications are linked to a scan profile, making it easier for users to identify associated profiles
- Updated Chromium from version 121 to version 131 for enhanced performance and compatibility
- Enhanced detection accuracy for Weak Ciphers Enabled by analyzing false positives
- Administrators can now assign Agent Groups to Teams for greater control over agents and the teams that can use them. Learn more.
Resolved issues
- Corrected OTP configuration attachment to personas, ensuring separate secrets and preventing shared changes
- Resolved issue where the internal agent service stopped after being disabled in the UI. The service now remains active even when the agent is disabled from the web application
- Resolved an issue where statistics were not displaying correctly after v24.11.0 update.
- Updated the SharedAssemblyInfo file to reflect the correct copyright details
- Fixed an issue where a disabled scan was inadvertently running, leading to an outage
- Fixed a bug where users were unable to update the website name longer than 40 characters
- Fixed an issue where the Invicti REST API did not return errors when importing an invalid definition file
- Resolved the “Internal Server Error” encountered on the Invicti scans/report API endpoint after enabling the “Prevent any sensitive information showing within the product” setting
- Fixed an issue where the issue state was inadvertently removed when a user, without permission to update the state, added a note to the issue
- Fixed an issue where the "Notification Settings" hyperlink in notification emails was redirecting incorrectly
- Resolved the issue where the Agent Verifier was encountering errors when using certificates in a Linux environment
- Fixed an issue where duplicate tickets were being created in ServiceNow due to integration error
- Fixed an issue where the severity trend chart was not rendering correctly on the individual website dashboard
- Node.js v6 has reached its End of Life (EOL), and support for this version has been removed from Azure Pipelines
- Resolved a coverage issue where the login page reappeared during scans
Notes for Verifying the Hash Value for Package Integrity in Invicti Enterprise On-Premises
The hash value for the "25.1.0.zip" file is provided below. You can verify the integrity of the file by checking its hash value using one of the methods outlined above:
Release Package Hash Value: D4ADFE2A0CBA752C87234DB3F3608D6F7DC9365CA2005684087A328991CB2F0D
Methods to Verify the Hash Value:
PowerShell (Windows):
Get-FileHash -Path "25.1.0.zip" -Algorithm SHA256Command Prompt (Windows):
certutil -hashfile "25.1.0.zip" SHA256Linux or macOS:
sha256sum "25.1.0.zip"
You can use any of the above methods to verify the hash value and ensure the integrity of the "25.1.0.zip" file.
Fixes
- Fixed Sqlite exception in verifier
Notes for Verifying the Hash Value for Package Integrity in Invicti Enterprise On-Premises
The hash value for the "24.12.1.zip" file is provided below. You can verify the integrity of the file by checking its hash value using one of the methods outlined above:
Hash Value: 186C51B2F5D7B6D5C1DC5B863773B49C6C5FD3F7798F52A60E325EEBB2204633
Methods to Verify the Hash Value:
PowerShell (Windows):
Get-FileHash -Path "24.12.1.zip" -Algorithm SHA256Command Prompt (Windows):
certutil -hashfile "24.12.1.zip" SHA256Linux or macOS:
sha256sum "24.12.1.zip"
You can use any of the above methods to verify the hash value and ensure the integrity of the "24.12.1.zip" file.
New Features
- API Discovery now supports working with RAML specs from Mulesoft Anypoint Exchange
- API Discovery now supports retrieving Open API/Swagger specs from Kong Konnect → Learn more
- Verifying the Hash Value for Package Integrity in Acunetix 360 On-Premises - see notes below
New Security Checks
- Added detection for multiple JavaScript libraries
- Added detection for Masa CMS (CVE-2022-47002 and CVE-2021-42183)
- Added a check for applications performing certificate name validation to prevent reading invalid memory addresses (CVE-2024-6119)
- Added detection of Google Tag Manager as a technology in the Vulnerability Database (VDB)
Improvements
- Changed the Mend integration to utilize an activation key so that the setup process is simpler
- Updated the AuthVerificationService from .NET 6.0 to .NET 8.0
- Enhanced security to prevent customer login information from being written in clear text
- OpenSSL configuration (openssl.cnf) updated for Docker compatibility
- Added new filter in Recent Scans page for Agent Mode in order to distinguish between Internal and Cloud agents
- Revised field descriptions in the Swagger model documentation to accurately reflect the use of the RequiredIf attribute
- Improved analysis and remediation capabilities for [Possible] Server-Side Template Injection vulnerabilities
- Fixed an issue with the implementation of AWS Lambda integration for HTML to PDF conversion in WebApp
- Updated field descriptions in the Swagger model documentation to reflect the use of the RequiredIf attribute
Fixes
- Vulnerability profiles that are set as hidden will now still be reported in the scan reports of scans completed prior to the vulnerability being hidden
- Fixed a bug in the editing of scan profiles with custom report policies
- Resolved an issue in the exporting of team member data with all attributes selected
- Resolved an issue with missing vulnerability profiles in custom report policies
- Fixed an issue with missing links in imported files that were sent from the API Inventory to the agent
- Fixed an issue where target names longer than 40 characters were not being truncated as expected on the Create New Target page
- Fixed an issue where the "Download HTTP Request Logs" button triggered an error while a scan was in progress
- Fixed an issue where user names containing the character "ä" could not be added
- Fixed an issue with the scan data retention period for raw scan files that was not working as expected
- Fixed missing scan completed notifications with report attachments
- Fixed an issue where adding more than one name to a Notification's Excluded Recipients would remove the other users from all other notifications
- Fixed an issue where the verifier agent could not read or apply custom proxy settings from the appsettings.json file
- Fixed an issue where uploading a .proto file caused a "No links found in the file" error
- Fixed missing request/response details for some out-of-band vulnerabilities
- Resolved a breaking change in .NET 8's System.Net.Security.UseManagedNtlm by upgrading from Ubuntu 22.04 to Ubuntu 24.04, where the issue was addressed. The Agent was updated to .NET 8.
- Fixed an issue where Retest-type scans did not identify the same vulnerabilities detected during full scans
- Fixed high CPU usage in some agents caused by Chromium
- Scans attempting to run with Agent Group without any agents will result correctly in failure instead of queue
- Fixed an issue that was preventing users from accessing a Scan Policy
- Fixed an issue where the Misconfigured Access-Control-Allow-Origin Header vulnerability was not detected
- Improved detection of the [Possible] Password Transmitted over Query String vulnerability.
- Fixed an issue with URL and port validation for the IAST Bridge on WebApp OnPrem
- Fixed a minor typo in the Slack integration documentation
Notes for IE Upgrade: .NET 6 to .NET 8
Impact
With the 24.12.0 release, Invicti Enterprise upgraded from .NET 6 to .NET 8. This upgrade may affect customers using agents on certain Linux distributions due to changes in operating system dependencies.
As a result, agents might not function correctly on unsupported versions of Linux after the upgrade.
Why Is This Happening?
Microsoft has deprecated .NET 6, and upgrading to .NET 8 is mandatory for Invicti Enterprise to maintain compatibility and support.
Solution (Customer Action Required)
Customers must verify the Linux version on which they are running Invicti Agents:
- If using Ubuntu 24.04 or higher: No action is required.
- If using RHEL 8 or higher: No action is required.
- If using an older version (Ubuntu <24.04 or RHEL <8):
- Option 1: Upgrade to Ubuntu 24.04 or RHEL 8 (or higher).
- Option 2: Disable auto-upgrade until the system is updated to a supported version.
Note
We will automatically disable auto-upgrade for affected agents. Customers should not re-enable auto-upgrade until they have upgraded to a supported version of Linux.
Notes for Verifying the Hash Value for Package Integrity in Invicti Enterprise On-Premises
The hash value for the "24.12.0.zip" file is provided below. You can verify the integrity of the file by checking its hash value using one of the methods outlined above:
Hash Value: 96320BC9F49A4851BD307ED23DE6FA6C256F967CBF1A416096382E97D4B3E8FA
Methods to Verify the Hash Value:
PowerShell (Windows):
Get-FileHash -Path "24.12.0.zip" -Algorithm SHA256Command Prompt (Windows):
certutil -hashfile "24.12.0.zip" SHA256Linux or macOS:
sha256sum "24.12.0.zip"
You can use any of the above methods to verify the hash value and ensure the integrity of the "24.12.0.zip" file.
New Features
- Integration with Mend SAST: display Mend SAST results alongside DAST results in Invicti Enterprise so you can prioritize all your application security testing fixes in one list → Learn more
- API Security: Added integration with Azure API Management to fetch Swagger2 and OpenAPI3 specification files → Learn more
- API Security now supports working with RAML specs from MuleSoft Anypoint Exchange
New Security Checks
- Updated detection for ActiveMQ - Remote Code Execution (CVE-2023-46604) and TorchServe Management API SSRF (CVE-2023-43654)
- Added detection for multiple JavaScript libraries
- Added detection for Masa CMS (CVE-2022-47002 and CVE-2021-42183)
Improvements
- Database optimizations
- Reporting improvements for the “Unknown Option Used In Referrer-Policy” vulnerability
- Improved the behavior of the 'Recent Scans' button group on the global dashboard when using the mobile view
Fixes
- Fixed a timeout bug in zero-configuration API discovery
- Fixed some wording inconsistencies and other minor improvements to the user interface
- Removal of sitemap data when a scan is canceled, failed, or aborted
- Resolved an issue in the General Settings page configuration
- Resolved an issue with user sessions not timing out in compliance with the specified configuration
- Fixed a false positive issue with Boolean Based MongoDB Injection detection
- Out-of-date version for Boolean Based MongoDB Injection is now reported correctly
- Vulnerability profiles that are set as hidden will now still be reported in the scan reports of scans completed prior to the vulnerability being hidden
- Fixed a bug in the editing of scan profiles with custom report policies
- Resolved an issue in the exporting of team member data with all attributes selected
- Resolved an issue with missing vulnerability profiles in custom report policies
New Features
- Administrators can now assign Agent Groups to Teams for greater control over agents and the teams that can use them. Contact our Support team to activate this feature
New Security Checks
- Adjusted the severity of SSLv3 and TLS 1.0 vulnerabilities to reflect their security risks
- Added support for CSP frame-ancestors
- Added detection for CVE-2024-6297, affecting several WordPress plugins
- Added XWiki version disclosure vulnerability and attack patterns
Improvements
- Pre-request script now works in DOM as well
- The Azure Extension now retries connections, preventing pipeline failures
- Anonymous sharing of diagnostics and user data with our analytics partner, Pendo, is now opt-out only
Fixes
- Remediated a high vulnerability issue on the Agent Dotnet dependency package
- Fixed an issue that was preventing the selection of configuration items during ServiceNow integration setup
- Fixed an issue with updating targets using the target group ID
- Fixed an issue where the Auth Verifier heartbeat was showing an hour behind due to daylight saving time adjustments
- Fixed an error that was occurring when editing Report Policies
- Fixed an issue with a REST API endpoint returning alternating severity data for TLS 1.0 vulnerabilities
- Resolved an issue with a pre-request script that was affecting crawling functionality
- Fixed the issue where tagging in the Discovery service would create a single-character tag when converted to a target
- Fixed an issue where the encryption process remained pending and incomplete after starting encryption key generation
- Fixed a bug in the API where '/api/1.0/issues/allissues' always returned NULL in the History field
- The option to suspend all future scans is now available to all customers in Scans Control Settings
- Fixed the false negative issue related to Polyfill.io
- Fixed an issue related to creating a custom script for a web application using the OIDC method with a login pop-up
- Fixed the issue where the scan summary page did not time out according to the settings
- Resolved an issue where the AV agent failed to install during the installation process
- Resolved an issue where modifying the settings triggered an error
- Resolved an issue that was blocking the loading of issue details
New Security Checks
- Added detection for Jenkins Secret as a Sensitive Data Exposure
Improvements
- API Discovery: changes to the setup configuration for the Invicti Network Traffic Analyzer
Fixes
- Fixed an error that was occurring when editing Report Policies
- Fixed the WMI spiking issue that was causing CPU 100% problems
- API Discovery: in certain cases, discovered APIs from Apigee were not properly shown
- Fixed the issue where the ServiceNow Integration fields were not loading while editing the integration
- Fixed the issue where clicking the clone button in the Jira integration incorrectly redirected to the create new integration page
- Fixed Chromium related issues in the agent
- Corrected the description of the "api/1.0/scans/test-scan-profile-credentials" endpoint
- Fixed the error when selecting a custom time period in the Dashboard Date Range
- Fixed the issue where temp folders could not be deleted and Chromium instances remained open when Puppeteer encountered an error
- Fixed the display issue on the Scan Summary page
- Fixed the false positive on detection of "Stack Trace Disclosure (Java)"
- Fixed a scan authentication issue and reduced latency
- Fixed the issue that was preventing the download of detailed PCI reports
- Fixed an issue related to the Moment.js regex
- Updated the OpenSSL configuration on the Cloud AMI
- Fixed the disk space issue in the Invicti Common folder
- Fixed the automatic syncing of issues with Jira integrations
- Fixed the issue where scans were failing due to a TLS connection not being established
- Fixed the OIDC authentication issue
- Fixed the issue where the REST API endpoint returned HTTP 400 instead of HTTP 200 when sending custom values
- Fixed the issue preventing proper login to the target URL
This release is currently only available on request.
New Features
- Invicti API Security: multi-layered API discovery to enable comprehensive identification of known and undocumented APIs → Learn more
New Security Checks
- Added a check for Authentication bypass in Fortra’s GoAnywhere MFT (CVE-2024-0204)
- Added a check for Open SSH server RCE (CVE-2024-6387)
- Added a check for cached pages that contain sensitive data (CWE-525)
- Incorporated the reporting of sensitive information disclosures from Okta
Improvements
- Added custom header support for SSRF registration
- Added a toggle to the Recent Scans widget on the Targets Dashboard to switch between displaying the target name and target URL
- Added the option to select the Agent mode when importing targets
- Added an option to filter by Agent Name on the Recent Scans screen
- Added more links from the global dashboard widgets to the corresponding sections in the UI
- Scheduled scans that repeatedly fail with the same result can now be automatically disabled
- Unlinked API specs from the scan profile automatically unlink on the API Inventory page as well
- Added the ability to navigate from the API operation vulnerability count in the API Inventory to a filtered list of vulnerabilities on the Issues page
- Reverted the fix for a problem in the JWT Engine that was intended to resolve a false positive issue
Fixes
- Fixed an issue related to Agent Selection and Preferred Agent Group settings
- Fixed an error occurring with valid requests to schedule a scan via the profile endpoint
- Fixed an issue where scan reports attached to emails could not be opened
- Fixed an issue where changing vulnerability details in the Report Policy deleted some information from the vulnerability
- Fixed an issue where scan summary reports were not accessible in the UI
- Fixed an issue where users were unable to remove URLs from Website Groups
- Fixed an issue where users were unable to create both HTTP and HTTPS for the same endpoint
- Fixed an issue where clients with limited access and custom roles were seeing all notifications for all users and websites in a target website’s dashboard
- Fixed an issue related to BLR links
- Fixed an issue where the scan was not displaying all the URLs in the sitemap
- Fixed an SSL Untrusted Root Certificate issue for scans conducted with the OpenShift agent
- Fixed an issue that was causing intermittent errors in PCI reports
- Fixed the ‘Bad Request’ error that was occurring in the vulnerability details of scan reports
- Fixed an issue where the character ‘ñ’ was causing errors when updating or adding new users
- Fixed the issue that was preventing the deletion of unused scan policies
- Fixed the issue where additional website vulnerabilities were being stored as target vulnerabilities
- Fixed the missing tooltips for source errors on the API Discovery Sources page
- Fixed the issue where the linked target URL was clickable even when the API specification was hidden
New Features
- Share Usage Analytics: New option to share anonymous diagnostics and usage data with Invicti and our analytics partner, Pendo
- LDAP Service: New settings enable administrators to manage LDAP server configurations (available for select customers)
- Added custom headers for communication between Agents and Invicti Hawk
- Added a warning message when creating scan targets for websites that do not have a hostname mapped to an IP address
New Security Checks
- Added detection for supply chain attacks through Polyfill JS
- Added detection for GeoServer SQLi (CVE-2023-25157)
- Added checks for various WordPress plugins
Improvements
- Renamed the ‘Websites and APIs’ menu to ‘Targets’
- Improved Credit Card Disclosure Security Check
- Set the severity of ‘Possible XSS’ vulnerabilities to ‘Informational’
- Improved various Sensitive Data Exposure security checks
- Improved detection of the Short SSL Key Length vulnerability
- Added capability to check for Sensitive Data in XML responses
Fixes
- Added OpenShift certificate permission to resolve an SSL/TLS untrusted root certificate vulnerability issue with Docker/Kubernetes agents
- Fixed a timeout issue on the global dashboard
- Fixed missing Request Body content in vulnerability details
- Fixed an issue with the selection of agent groups
- Fixed an issue with the order in which internal agent scans are initiated
- Fixed an issue with the ‘Ignore Certificate Errors’ Agent setting for SSL Validation
- Fixed a download problem with PCI reports
- Fixed an issue with the SSO login that was causing incorrect redirects
- Removed references to 3.2 in the PCI DSS Compliance scan summary
- Fixed an issue with the Azure Boards integration reopening old vulnerabilities that do not link to active issues in Invicti Enterprise
- Fixed a timeout issue that was occurring on a pre-request script
- Fixed a problem in the JWT Engine to resolve a false positive issue
- Updated vulnerable OpenSSL libraries to secure versions
- Fixed a bug in the Checkout Logout Detection so that it now chooses the same verification agent as the verification process
- Fixed an issue related to the OTA app scan
- Fixed HTTP 413 responses resulting from nonce cookies stacking
New Features
- Added functionality for scanning gRPC API Web Services → Learn more
New Security Checks
- Added detection of Fortinet vulnerabilities (CVE-2020-12812, CVE-2019-5591, CVE-2018-13379)
- Added a new attack pattern for missing Open Redirection
Improvements
- Added a "Stop The Scan When Build is Aborted" option to the Jenkins integration
- Added an option to trigger only specified lists of events
- Added a 100MB limit to the maximum total file size for imported link files
- Added an option to the GitHub Actions CI/CD integration to fail a build if a vulnerability with a specific severity is found during the scan
- Added a Y-axis to the Severity Trend graph in the dashboard
- Updated all the IAST Sensors: .NET Framework and .NET Core 6.2.0, Java 16.0.0, Node.js 2.1.3, PHP 8.0.1
- Adjusted the behavior of the website matching option in the Discovery Settings to remove 2nd level domain matching in order to improve the relevance of discovery results
- Added a new option to the Discovery Match Settings (enabled by default) to only show discovery results that have an IP address. This change is intended to prevent the consumption of licenses on targets that cannot be scanned due to the lack of an actual IP address.
- Updated to the latest Chromium version to improve security and performance → Learn more
- Updated the summary information of the PCI compliance report
- Added the OpenShift Docker Agent to the public repository
Fixes
- Fixed a bug in the user timeout session setting
- Resolved an issue with the frequency of out-of-date technology email notifications
- Removed email notifications for out-of-date technologies in failed scans
- Fixed an issue that was causing scans to be stuck in an async archiving state
- Fixed a bug in the automatic sign-out functionality when the session timeout period has expired
- Fixed an issue in the detection of the 'Improper XML parsing leads to Billion Laughs Attack' vulnerability
- Fixed a bug in the Service Now Integration
- Fixed the issue that was causing activity logs to display incorrect owners of failed scans
- Fixed an issue with user-agent selection in scan policies that was causing disabled security check vulnerabilities to appear in the dashboards and scan reports
- Fixed an issue that was causing the agent to not send a heartbeat and become unavailable while archiving and uploading scan results
- Fixed the issue that was preventing updates made in Azure Boards from reflecting in Invicti Enterprise
- Fixed vulnerabilities with the Invicti Scan Agent Docker image
- Fixed the disk space utilization issue that was causing the InvictiCommon folder size to increase significantly during scans
- Resolved an issue with the Business Logic Recorder
- Improved the crawling capability to allow for automatic crawling of XHR requests
- Fixed the missing technology details on the scan summary and scan report pages
- Fixed an AWS4Signer authentication issue
- Fixed the screenshot error on Linux Agents
- Updated the advanced installer files to fix an issue with scanners and verifiers disappearing during the update process
- Fixed an error that was preventing PDF reports from opening
- Updated the installation wizard
New features
- Predictive Risk Scoring – prioritize your web asset discovery results according to their potential risk before you scan them. Learn more in our Introduction to Predictive Risk Scoring and guide to Utilizing Predictive Risk Scoring
- Enabled Korean language support
- A new API Token encryption method for Agents/Verifier Agents
- Added a pre-request script to generate AWS Signature tokens to perform authentication
- CVSS 4.0 scores are now available via API
- Added the ability to include/exclude main-level domains in the Discovery settings
New security checks
- Added detection method for Angular
- Added a new security check for Oracle EBS RCE
- Added a new security check for TLS/SSL certificate key size too small issue
- Improved WP Config detection over backup files
- Added a new security check for authentication bypass and command injection in Ivanti ICS and Ivanti Policy Secure (CVE-2023-46805 and CVE-2024-21887)
- Added detection for exposed WordPress configuration files
- Added a new security check that reports two vulnerabilities: TorchServe Management API Publicly Exposed and TorchServe Management API SSRF (CVE-2023-43654)
- Command Injection in VMware Aria Operations for Networks can now be detected
- Added a new signature for Stack Trace Disclosures (ASP.Net)
- Added a new security check for Client-Side Prototype Pollution
Improvements
- Improved AWS Secret Key ID detection security checks
- Improved Google Cloud API Key detection security checks
- Updated remediation information for Angular JS-related vulnerabilities
- Improved Boolean-Based MongoDB Injection detection method
- Updated all IAST sensors to support Java 17 and 21
- Added highlighting and verification of response status codes to the BREACH engine
- Updated the notes section of the [Possible] Cross-Site Scripting issue detail to cover MIME sniffing
- Increased the default severity level of Version Disclosure (Varnish) from 'Information' to 'Low'
- Improved WordPress Config detection over backup files
- The Agent type (Arm or Intel) information is now displayed on the Scan Summary page
- Permissions on the General Settings screen are now grouped by category rather than listed without being categorized
- Added an option to enable or disable the JavaScript Parser, facilitating JavaScript parameter discovery within the JavaScript code
- The Jenkins plugin now routes requests through the proxy
- The Team Administrator role checkbox is now in a separate Limiting Permissions Role section of the UI
Fixes
- Adjusted the settings for SSL certificate errors to resolve a scan failure 'target link timeout error'
- Fixed a bug in the automatic sign out functionality when the session timeout period has expired
- Resolved an issue with downloading HTTP request logs
- Fixed a validation error when validating Shark settings
- Fixed an issue with duplicate custom user agents that was preventing scanning
- Fixed an issue where authentication would fail when started with an Authentication profile
- Fixed an issue that caused proxy usage for Chromium even when no proxy was selected from the scan policy settings
- Fixed a scan authentication issue and a crawling issue with Cloud Agents
- Fixed the HTTP 401 forbidden response form authentication error
- Fixed an issue with the detection method for wp-admin vulnerabilities
- Fixed an error that was occurring when generating knowledge base reports
- Updated the extraction algorithm for downloaded scan files from Invicti Enterprise
- Fixed a scan issue that was producing 413 error responses
- Fixed a bug in the API Access settings
- Resolved an issue with custom severity levels that were reverting to their previous level
- Fixed a bug in the API update command for scan profiles
- Removed limits on AWS Discovery port filters
- Technologies identified during failed scans are no longer displayed
- Fixed a bug in the scan retention period settings that was causing inaccurate information in the Recent Scans list
- The Last Login Date is now aligned between the UI and the API
- Fixed an issue with the detection method for wp-admin vulnerabilities
- Fixed the issue where scan profiles could not be created through automation tools, Postman, or through the Invicti API Documentation page
- Fixed the issue with scans that were stuck in ‘Delayed’ or ‘Archiving’ status
- Fixed an issue that was occurring with the Jira Integration when the Jira URL was set as Localhost
- Fixed a scan authentication issue and a crawling issue with Cloud Agents
- Fixed an issue that was occurring when websites were added with both http and https protocols
- The scan report pdf file name now includes the time and date when it is delivered via the scan completed notification
- Fixed the 504 error that was appearing when running the Scans_NewWithProfile endpoint
- Fixed a bug that was preventing retest scans from launching
- Fixed an issue with the scan data import from Invicti Enterprise to Invicti Standard
- Fixed the HTTP 401 forbidden response form authentication error
- Fixed a scan issue that was producing 413 error responses
- Resolved a cookie use on subdomains issue that was causing a scan authentication and crawling issue
- Fixed an issue that was causing a memory issue in JavaScript Parser
- Fixed an issue with the custom script editor that was stopping it from loading the form authentication fields
- Disabled BREACH attack from the default security checks policy
- Fixed the issue where users were unable to load the Scan Report
- Fixed the issue where internal scans were not failing if their Agents were terminated
- Fixed the Azure Boards integration, which was reported to have been suspended by itself
- Fixed query optimization on the main Scans page, resulting in improved response time and query quality
- The page number in the Custom Script Editor is now correctly displayed
- When the personal access token has expired, the Azure Boards Integration is now disabled
- Fixed concurrency exceptions occurring for the scan and website tables due to excessive update requests sent within a short timeframe
- Fixed the inability to export a scan from Invicti Standard to Invicti Enterprise
- The issues counter on the Dashboard now displays the correct number of issues
- Fixed an issue when Team Administrator and Account Owner roles are assigned to the same user
New features
- Added the option to remove Request/Response details from the detailed template to avoid the character limit error when sending vulnerabilities
- Added the option to enable enhanced logging of failed logins
- Added functionality to the UI for users to obtain logs from failed scans (previously only system administrators were able to do that)
- ServiceNow Application Vulnerability Response integration is now available in the ServiceNow store
New security checks
- Added a check for dotCMS (CVE-2022-26352)
- Added a check for the Ultimate Member WordPress plugin (CVE-2023-3460)
- Added a new mXSS pattern
- Added new signatures to detect JWKs
- Implemented a detection and reporting mechanism for the Backup Migration WordPress plugin (CVE-2023-6553)
- Added detection for TinyMCE
- Added detection for ActiveMQ RCE to the OOB RCE Attack Pattern (CVE-2023-46604)
Improvements
- Improved the recommendations for the Weak Ciphers Enabled vulnerability
- Improved detection of swagger.json vulnerabilities
- Updated the "Insecure Transportation Security Protocol Supported (TLS 1.0)" vulnerability to High Severity
- Implemented support for scanning sites with location permission pop-ups
- Implemented support for FreshService API V2
- Revised the labeling of the active vulnerabilities information on the Scan Summary page to provide greater clarity
- Removed obsolete X-Frame-Options Header security checks
- Improved ServiceNow Vulnerability Response integration
Fixes
- Fixed a bug in the cloning report policies functionality
- Fixed an error that was occurring with the API endpoint: list-scheduled
- Fixed a bug with the Jira integration
- Fixed a bug with custom scheduled scans that were not updating the Next Execution Time field correctly
- Fixed an issue with the HashiCorp Vault integration token validation path
- Fixed the missing 'Known Issues' tab from scan summary issue details
- Fixed an issue with the severity trend chart on the Dashboard
- Fixed a problem with importing WDSL files
- Fixed a bug in the Request/Response tab of Version Disclosure vulnerabilities
- Corrected an issue in the technical reports where vulnerabilities identified in Korean are now reported in English
- Changed the ID parameter from 'optional' to 'required' within the Scan Policy Update API
- Removed the target URL from the scope control list
- Resolved a bug in the filtering of vulnerabilities on the Issues page
- Fixed a bug in the marking of issues as a false positive
- Resolved an issue where the agent would become unavailable after receiving a 401 error
- Fixed the issue with uploading a Swagger file into a scan profile
- Fixed the system to halt subsequent tests if a scan is aborted from Jenkins
- Upgraded Microsoft.Owin package to version number 4.2.2
New features
- Added notifications about agent disk full issues for easier navigation and to prevent scan errors
- Added an option to the Jenkins integration that stops the scan when the Jenkins build is aborted
New security checks
- RCE for Backup Migration WP plugin (CVE-2023-6553)
Improvements
- Improved reporting of DOM XSS vulnerabilities
Fixes
- Fixed an issue with removing the client certificate via API
- Fixed an inconsistency for PCI results between the Invicti UI and the PCI DSS detailed report
- Fixed a bug that was causing scan session files to fail when loading
- Fixed inconsistencies with the 'average time to fix' table on the dashboard
- Fixed an issue with the import of scan data from Invicti Enterprise to Invicti Standard
- Fixed an issue with the form verifier not using the new scan policy until the scan profile is saved
- Added a custom detailed scan report
- Fixed a bug in the importing of links
- Fixed an error that was occurring when setting an issue as Accepted Risk
- Resolved issues with importing API documentation from a link
- Resolved issues with the Authentication Verifier and Agent.db file corrupting after update
- Fixed a bug in the Jenkins plugin that was causing the 'Stop The Scan When Build Fails' option to not work correctly
New features
- Added CVSS 4.0 categorization of vulnerabilities
- Added support for PCI DSS 4.0
New security checks
Improvements
- Added descriptions to the agent warning messages on the Scan Summary page
- Updated messaging around the functionality of the Team Administrator role
- Improved the request body rating algorithm
- Improved the Postman collection parsing algorithm
- Improved the vulnerability calculator for Boolean MongoDB
- Resolved an issue with adding a client certificate to set up a scan
Fixes
- Fixed a bug that was preventing customers from adding back previously deleted targets
- Increased character length for the Jira and Snow integration URL validation regex to ensure it accommodates Top-Level Domains (TLDs)
- Paused scheduled scans that were resuming automatically will now remain paused until manually resumed
- Removed the previous limit on the number of supported second-level domains in the Discovery feature
- Fixed an error that was occurring when updating an issue from Fixed (confirmed) to Accepted Risk status
- Fixed discrepancies in the numbers displayed on the Dashboard
- Fixed an issue with the agent auto-updater
- Added a missing control for SSO users while editing members
- Fixed a bug in the communication between Invicti and ServiceNow
- Fixed a bug that was preventing administrators from creating new notifications or editing built-in notifications
- Fixed an issue that was causing verifiers to not use scan policy proxy settings
- Fixed an auth verifier client certificate authentication path error
- Fixed the Invicti crawler that wasn't getting JS endpoints correctly
- Resolved issues with importing API documentation from a link
- Fixed a bug in the Jenkins plugin that was causing the 'Stop The Scan When Build Fails' option to not work correctly
- Fixed insecure Windows service permissions that were vulnerable to privilege escalation attacks
New features
- Added the ability to pull a PCI Report from the CloneSystem itself by using API endpoints
- Added the option for customers to define a namespace for their HashiCorp integration
- Enhanced reporting capabilities with more attributes available in .csv exports and the option to do a .csv export in more places in the UI
- Added an option under New Scan Policy > Ignored Parameters to allow customers to set 'Cookie' as a type of ignored parameter
- Added a setting for administrators to enable internal agents to get VDB updates from the WebApp to avoid routing and proxy issues
- Added the option for administrators to hide sensitive data (passwords, tokens, session IDs, etc.) from the UI
- Added functionality to the Dashboard so that you can drill down to view more information when clicking on the Severities and Securities Overview section
- Added an option under General > Settings to require a password for edit access to custom scripts
- Added an option under General > Settings to set a session timeout limit for all users
- We now support AWS IAM Roles as an authentication method
New security checks
- Added new checks for the WordPress Login with Phone Number Plugin: CVE-2023-23492
- Added new checks for the WordPress JupiterX Core Plugin: CVE-2023-38389, CVE-2023-38388
Improvements
- Added support for custom authentication tokens without token type
- Improved LFI attack patterns for better accuracy
- Fixed some vulnerabilities in the Docker image
- Stricter sensitive data rules
- Improved bot detection bypass scenarios
- Added a warning message when selecting or assigning the Team Administrator role
Fixes
- Fixed a sensitive data issue when uploading a pre-request script
- Fixed a bug that was preventing scheduling group scans using API
- Fixed custom header values in scan profiles so that they are masked
- Docker Cloud Stack check has been updated to reduce noise
- SSL/TLS classification updated from CWE-311 to CWE-319
- Fixed a bug in scheduling group scans with API
- Removed 401 to 500 status code conversion for internal agent requests
- Changed the IP range limitation for excluded IPs in Discovery Settings to fix the Invalid IP address error
- Fixed an issue with scheduled scans not following the scan time window
- Fixed the problem with scan failed logs not appearing in activity logs
- Fixed the broken verify login and logout function in scan profiles
- Updated the vulnerability severity ranking so that issues are correctly sent to integrated issue tracking systems
- Changed the Active Issue count on the dashboard so that it is consistent with the number when you click on it
- Fixed an issue with accessing a scan profile
- Fixed an issue related to having multiple integrations with the same project but with different issue types
- Fixed an issue in the 'Basic, Digest, NTLM/Kerberos, Negotiate Authentication' settings for scans
- Fixed the Jira Server integration issue that was causing only some Jira users to display when configuring Jira Field Mappings
- Fixed a bug that was causing URL rewrite rules to not be included in the Export Knowledge Base report
- Fixed a problem with the internal agent not sending a heartbeat to the web app when in archiving state
- Fixed an issue with Jira-related integration information being removed from the issue history when a previous scan is deleted
- Fixed an internal agent issue that was causing an exception when registering a vulnerability
- Fixed an issue that was causing the Knowledgebase, Crawled URLs, and Scanned URLs to fail when there is no content
- Fixed the missing mapping for Proxy Bypass On Local that was not saving when a scan policy was saved
- Fixed a bug that was duplicating roles when a Team Administrator modified another Team Administrator direct role assignment
- Fixed a bug that was preventing the import of WSDL files to Invicti Enterprise
- Fixed version information reported in Web App Fingerprint Vulnerabilities
New features
- Added a new Team Administrator role that gives you the flexibility to designate an administrator for oversight across specific web applications, and assign certain roles and website groups to specific Teams or Team Members
- Added an option under General > Settings to set a session timeout limit for all users
- Added new options to the dashboard for selecting date ranges, including creating custom time periods
- Added a notification to the scan results page to show the VDB update version and Invicti Hawk connectivity status for the agent used in the scan
- Added a sensitive data (password, session cookie, token, etc.) encoder
New security checks
- Added JQuery placeholder detection methods
- Added a new security check for the Missing X-Content-Type-Options vulnerability
Improvements
- Improved the JS Delivery CDN disclosure check to increase stability
- Improved the remediation part for the Weak Ciphers Enabled vulnerability
- Reduced the certainty value to 90 for the Robot Attack Detected vulnerability
- Improved the detection method for CSP
- Improved the detection method for the Dockerignore File Detected vulnerability
- Improved the detection method for the Docker Cloud Stack File Detected vulnerability
Fixes
- Fixed an issue with imported links in the API
- Fixed a bug in the scan URL rewrite rules
- Fixed a bug that was preventing retest scans from starting correctly when the vulnerability states were changed from 'Reviewed' to 'Fixed (Unconfirmed)'
- Fixed a bug with disabling the scheduled scans list
- Fixed an issue with viewing the Account Edit page
- Added the missing CVE to the issue details for the "Out-of-date Version (jQuery Validation)" vulnerability
- Fixed some bugs that were affecting BLR
- Encrypted proxy password details when used in the Agent
- Fixed a custom proxy bypass list issue
- Fixed a unique analyzer bug for the WSDL importer
- Improved our XSS capabilities
- Fixed an NTLM login issue
- Fixed an issue that was causing the license file to become empty after upgrading the product
- Fixed several bugs that were impacting some agent proxy settings, synchronization of the vulnerabilities database, and saving scan policies when the proxy bypass feature is used
- Other miscellaneous bug fixes
New features
- Added the option to set a Custom HTTP Authorization Header under Scan policy > HTTP > Request
- Adjusted agent download parameters to allow installation of internal scanner agents using the Docker client via the Invicti registry service
- Changed the compression tool and default compression format for log files from 7zip to Tar
- Added functionality to enable entering of multiple IP addresses and IP ranges into the IP Address Restrictions setting. Previously, only single-entry IP addresses were permitted.
- Added TLS certificate authentication as an option when integrating with HashiCorp Vault. Previously, we only supported token authentications.
New security checks
- Added new patterns to detect XSS
Improvements
- Improved notification delivery with integration services
- [Closed Beta] Protected visibility of passwords within custom scripts
- Improved detection and reporting of File Inclusion vulnerabilities
- Improved detection and reporting of Sensitive Data Exposure vulnerabilities
- Improved detection and reporting of Dockerfiles
- Disabled caching from the boolean-based MongoDB security engine to avoid possible false positives
- Improved the content-type exemption for non-HTML content types in the CSP engine
- Improved the typehead.js check to increase stability
- Removed the X-XSS-Protection header check because it is deprecated by modern browsers
- Added functionalities to prevent bot detection and fixed an issue that was causing cookie loss after authentication
- Improved the remediation part for the JetBrains .idea detected vulnerability
- Added information to the UI about the functionality of the 'Edit My Team's Role' permission
- Added bypass list functionality for scan policies
Fixes
- Fixed a bug in the date filter that was causing incorrect information to display on the dashboard
- Fixed the external SOAP web service import problem
- Fixed a problem that was causing default values to be filled incorrectly, resulting in false negatives
- Fixed Vulnerabilities visible from the UI but not via API in certain failed scan situations
- Fixed inconsistent scan states in rare deleted scan scenarios
- Fixed missing Next Execution Time for certain scheduled scans
- Fixed an issue that prevented saving scheduled scans in some scenarios
- Fixed inconsistencies in the Resource Finder with certain hidden files and backup files
- Improved updating of groups in Azure Provisioning scenarios
- Fixed a problem with converting scan data while the CloudProvider Settings page is open
- Fixed a database update exception when a large number of scans are launched simultaneously
- Fixed the incorrect reporting of outdated technology versions
- Fixed a bug that was preventing reports from being saved
- Fixed a bug that can cause too much browser user data to be left in the temp folder
- Fixed a bug that was stopping the certificate authentication process from working correctly for Authverifiers
- Fixed a boolean-based MongoDB Injection that was causing false positives in scan reports
- Fixed the incorrect display of vulnerabilities when importing scan results from Invicti Standard to Invicti Enterprise
- Fixed a bug that was preventing the editing of internal website URLs
- Fixed a character validity issue so that user names with Danish characters can now be edited in the UI
- Fixed a bug that was allowing access to the UI via the back button after the user had signed out
- Fixed the Discovery Main Domains Filter Expression that was not working properly for some domains
- Fixed an issue that was causing tags to be duplicated when a website was imported using a CSV file
- Fixed the update agent command that was not working correctly
- Fixed the internal Linux v23.7 AV agent that wasn’t sending header configurations
- Encrypted the proxy password used in the scan policy file
- Fixed a scan coverage issue
- Fixed a custom script issue so that now passwords written to the logs are encrypted
- Fixed an issue where vulnerabilities could not be generated as CloudFlare WAF rules via API
Important note
- Customers currently using version 23.7.0 on Windows running internal agents will need to perform additional steps in order for this update to run successfully in their environment. Affected customers have been contacted directly with more information.
New features
- [Closed beta] Added the Team Administrator default role
- Changed compression tool from 7zip to Tar
- Added Diana.jl support for GraphQL Library Detection
- Added Hot Chocolate support for GraphQL Library Detection
- Added Zero Day Vulnerability for MOVEit Software
Improvements
- Improved the scan deletion process
- Improved the authentication agent to carry out any stepped authentication, such as first Form Authentication then OAuth2
- Added filter for discovered websites via AWS connection
- Enabled regex case sensitivity for attack payloads
- Updated Boolean NoSQL / SQL Injection attack payloads
- Expanded scenarios for Discovery Service with AWS Connections
- Improved performance when updating vulnerability lookups
- Improved performance of database indexes
- Improved added API endpoints for Custom Scripts
- Improved performance for Issues Report API endpoint
- Improved detection of IT Hit WebDav Server .Net versions
- Improved Internal Path Disclosure detection
- Improved Remediation Advice for Autocomplete Enabled vulnerability
- Improved detection logic for LFI vulnerability
- Improved identification and version disclosure for PopperJS, CanvasJS, and Next.js
- Improved WAF Detection for F5 BIG IP
Fixes
- Fixed PCI Report generation error when selecting a specific group
- Fixed the issue that prevents users from saving the scan profile when the Is Regex checkbox next to the Excluded Path field is selected on the URL Rewrite page
- Fixed the timezone problem on the Knowledge Base Reports
- Fixed issue with scans stopping with the Find & Follow New Links option enabled
- Fixed issue with agent compression of chromium and node files
- Fixed null value exception with REST API
- Fixed InvalidCastException with REST API
- Fixed ArgumentNullException with Custom Security Checks
- Fixed Access Denied error when attempting to delete scan files which were already previously deleted
- Fixed cannot login to web app after changing database password
- Fixed unclear results with PCI reports with edge date ranges
- Fixed BLR cannot fill address fields
- Fixed licensing issue when adding a previously-deleted website
- Fixed adding some MongoDB vulnerabilities to Knowledge Base report
- Fixed importing Swagger/OpenAPI links
- Fixed Discovery Service issue with AWS Connection throttling
- Fixed authentication failure with MFA recovery codes
- Fixed license file corruption issue during version upgrade
- Fixed scans unauthenticated after successful authentication verification
- Fixed Linux agent update issue
- Fixed the data type detection when importing Swagger schemas