Addressed Issues in Prisma SD-WAN
Focus
Focus
Prisma SD-WAN

Addressed Issues in Prisma SD-WAN

Table of Contents

Addressed Issues in Prisma SD-WAN

Learn about the Addressed Issues in Prisma SD-WAN.
The following table lists the addressed issues in Prisma SD-WAN.
Issue IDDescription
CGSDW-38675Fixed an issue where the GET /snmpagents API returned the SNMP community string in cleartext. SNMP configuration fields now enforce a strict character validation policy to prevent command injection. The fields accept only alphanumeric characters and select symbols (!, @, #, %, ^, *, -, _, +, =, :, ., ,, ?, /, ~). Existing configurations with restricted characters continue to function, but the system enforces the new validation rules when you modify these settings.
CGSDW-38379Fixed an issue where the GET API response returned the default Element user password for newly claimed devices in cleartext. The API now masks this default password. You must change the default Element user password before you use the device.
CGSDW-29863Resolved an issue where filtering by incidents was not updating the list of sites for Monitor>Branch Sites in the Map view.
CGSDW-29475Resolved an issue where the app acceleration policy rule creation was not working.
CGSDW-29332Resolved an issue where the TSG ID for a migrated tenant was giving an error.
CGSDW-29118Resolved an issue where the supported_base_software_version in PUT payload for Appdefs was resulting in an error.
CGSDW-28726The hardware ID is now available during machine recovery in case the device ID is not available.
CGSDW-28571Resolved an issue where BGP peer status was not displayed for devices with software version lower than 6.2.
CGSDW-28431Device deallocation is now successful for a device which is in an assigned state and disconnected.
CGSDW-28392Resolved an issue wherein the default rule set was being prepended with the text SDWAN that was causing the Simple Default Rule Stack to be treated as Advanced.
CGSDW-25961Resolved an issue where multiple device software versions having the same SHA hash resulted in incorrect software version representation on the web interface.