Acunetix 360 On-Premises

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
• Removed 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

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

• 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 AcuSensor 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
• 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 Acunetix 360 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 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
• 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