HP Color LaserJet CM3530MFP / CM3530FS MFP Printer Firmware Upgrade Utility 53_170_1B

IMPORTANT NOTE:

This firmware version installs code signing verification functionality. Firmware signed by HP guarantees the integrity and authenticity of the code; meaning that the firmware was produced by HP (authenticity) and that the firmware has not been altered in any way (integrity).

ATTENTION:

Once this firmware has been applied to your printer or multifunction device it CANNOT BE DOWNGRADED to a previous version of firmware.

BACKGROUND:

It is important to note that Code Signing Verification functionality has been provided with this version of firmware and will be provided with all future versions of firmware, therefore, the ability to downgrade to a previous version of firmware no longer exists.

Product Name(s):

HP Color LaserJet CM3530 MFP, HP Color LaserJet CM3530fs MFP

Model Number(s):

CC519A, CC520A

The HP Easy Firmware Upgrade utility provides the HP MFP firmware .rfu bundle and a user friendly method to transfer the .rfu file to the MFP all contained in a self-extracting executable for the Windows operating systems.

Enhancements

- Base Product:
Ability to change control panel message when the service request is raised.
Now you are able to set tray 2 as the default tray for copying and have the MFP pull from tray 2 regardless of what type is in the tray.

- Embedded Digital Sending:
No new updates.

- Analog Fax:
No new updates

- Embedded Jet Direct:
802.1x failure to negotiate disables networking
No SSL Proxy available to Auto-Send
Secure@Install support is now available
SNMPv3 privacy and authentication use keys rather than passphrases

Fixes or improvements

This firmware provides fixes or improvements for following issues:

- Base Product:
Chai based solutions appear to be unresponsive at times either when drawing a GUI window or when pressing a Chai button with HPAC 6.33 installed
DST offset value is getting added while setting the time to a time which falls in daylight time saving period.
In some cases you may not be able to cancel a copy job after starting to copy multiple jobs,
Ringdale - Changes to the Fax application system variables do not take effect until after a reboot.
Stored jobs may not be visible under created folders when authentication is set to LDAP
The phrase "To use AutoSend with E-mail, you must first configure your E-mail Server"' was not localized in Slovak and Russian languages.
You may see the control panel timed out (returned to the home screen) before their job list is displayed on the CM6040 when using HPAC 6.33.

- Embedded Digital Sending:
Email addresses (including Fax Notification) may not be consistently set from device security services.
For devices configured to use the HP US Government SmartCard authentication solution (DOD CAC), send to network folder jobs could fail due to the device improperly sending the network credentials for the digital send job.
Embedded send to FTP jobs may fail even though the FTP path verifies successfully from the device Embedded Web Server
In the Send to Email configuration, after setting 'Lock the BCC Email field', the BCC field is disabled but does not gray out until reboot.
Send to FTP will generate 0 bytes files in FTP destination when the device is in ACTIVE mode and with a firewall enabled on the FTP server.
The MFP may hang during email address lookups when the LDAP settings are configured to use verbose mode.

- Analog Fax:
Analog Fax and Embedded Send to Email jobs could intermittently lock up the MFP
Embedded RightFax Metadata File May be incompatible with DSS.

- Embedded Jet Direct:
A "Reflected XSS" is possible due to redirection to HTTPS
Certificate Signing Requests specify 1024 bit keys; should specify 2048 bit keys
Crash results when a duplicate IPv6 address is encountered
Crash results when navigating to Refresh Rate in Networking pages
Misbehavior when DHCP NAK received
SSL vulnerable to a Cipersuite downgrade attack
SSL vulnerable to a man-in-the-middle renegotiation attack

- Telnet crashes
The default key size for Certificate Signing Requests should be 2048 bits not, 1024