Acunetix 360 On-Premises

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 version 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 Acunetix 360 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: 0650A87C4C8ED1B56A588420FABB4001E526743867F478B037652F04EF595B0C

Methods to Verify the Hash Value:

PowerShell (Windows):

Get-FileHash -Path "25.3.0.zip" -Algorithm SHA256

Command Prompt (Windows):

certutil -hashfile "25.3.0.zip" SHA256

Linux or macOS:

sha256sum "25.3.0.zip"

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 Acunetix 360 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: D48F8DE13932C5AC975DF835251CC7652A99D48F70A6D7EEEEFED96BAA4B48FC

Methods to Verify the Hash Value:

PowerShell (Windows):

Get-FileHash -Path "25.1.0.zip" -Algorithm SHA256

Command Prompt (Windows):

certutil -hashfile "25.1.0.zip" SHA256

Linux 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.

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 a new filter in the 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

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 Acunetix 360 On-Premises Upgrade: .NET 6 to .NET 8

Impact

With the 24.12.0 release, Acunetix 360 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 Acunetix 360 to maintain compatibility and support.

Solution (Customer Action Required)

Customers must verify the Linux version on which they are running Acunetix 360 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 Acunetix 360 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: 9957D4DA135F6DA98D61ABAA947C49D88E72A6C753740094F206AAD74A4C3042

Methods to Verify the Hash Value:

PowerShell (Windows):

Get-FileHash -Path "24.12.0.zip" -Algorithm SHA256

Command Prompt (Windows):

certutil -hashfile "24.12.0.zip" SHA256

Linux 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

• 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

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
• Resolved an issue that was causing an error when modifying the Settings
• 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