Support on SonicWall Products, Services and Solutions
Browse Knowledgebase by Category
SonicWall UTM running the affected SonicOS version fails PCI vulnerability scan due to a "X.50
03/26/2020 
10 
8629
DESCRIPTION:
SonicWall UTM running the affected SonicOS version fails PCI vulnerability scan due to a "X.509 Certificate MD5 Signature Collision Vulnerability".
RESOLUTION:
Problem Definition:
SonicWall UTM running the affected SonicOS version fails PCI vulnerability scan due to a "X.509 Certificate MD5 Signature Collision Vulnerability".
Resolution or Workaround:
The default SonicOS management certificate on firmware versions of the affected branches use an MD5 hash algorithm. This SSL certificate which is signed with the less secure MD5 hash will be carried over with regular firmware upgrades and therefore SonicOS versions which include the fix might still be using it and fail the PCI vulnerability scan.
SonicWall recommends booting a publicly released SonicOS version higher than the affected versions after exporting the preferences and booting it with factory default settings before importing the preferences. Alternatively the management certificate’s common name can be changed to e.g. the Primary LAN interface’s IP address in the Web Management Settings area of the System > Administration section. (Note: the IP address shown in the screen shots is an example).
In case the existing IP address already is the correct Primary LAN interface IP address, temporarily change it to another address, hit the Accept button and change it back to the unit’s current Primary LAN interface IP address before hitting the Accept button again.
With the described changes the PCI Vulnerability Scan should pass the "X.509 Certificate MD5 Signature Collision Vulnerability” check.
Other notes:
In cases where a private or commercial certificate for the SSL management connections was loaded on the device, then to avoid this issue you would have to load a certificate that has not been signed with an MD5 hash.
Also if the scan is detecting a public server that has been configured then either the public server needs to update its SSL certificate or SSL Control needs to be enabled with the ‘Detect MD5 Digest’ checkbox checked.
This vulnerability is fixed on all SonicWall UTM models running the latest firmware.
