Security Weakness Resulting in Potential Local Privilege Escalation When HA (High Availability) is Active

A weakness in the SMA100 Series exists when High Availability (HA) pair is active, potentially permitting an operation at a privilege's level that is higher than the minimum level required. If a malicious actor obtains a 'nobody' user shell on an impacted SMA100 device, this can potentially lead to commands being executed with root-level privilege. This is a SMA100 series security weakness, not a vulnerability that can be exploited remotely. 
CVE: N/A
Last updated: Sept. 23, 2021, 9:20 p.m.

The Alternative Way of Recovering Data from a Burnt SSD

Hello everybody!

Sometimes, when the proven solutions can’t be applied to your problem, you need to change the approach and experiment a little. Let’s discuss the alternative method of data recovery from a burnt SSD.

Several years ago our company switched our way of working with SSDs from the PC-3000 Flash to PC-3000 SSD. Why did we do it?

The reason was that recovering data with the chip-off method from SSDs was difficult and time-consuming. It took around 1 week to detect the correct order of the memory chips, fix the ECC errors, eliminate all the controller preparations and, finally, build the image.

It was a real pain even back then, but nowadays it is even more complicated to recover data from SSDs using the chip-off method due to the full encryption of the data inside the NAND memory chip or encryption with the AES-128 key.

These issues can be easily solved and bypassed via the PC-3000 SSD Software for the PC-3000 Express/UDMA/Portable III tools. We add more and more SSDs an..

The Alternative Way of Recovering Data from a Burnt SSD

Hello everybody!

Sometimes, when the proven solutions can’t be applied to your problem, you need to change the approach and experiment a little. Let’s discuss the alternative method of data recovery from a burnt SSD.

Several years ago our company switched our way of working with SSDs from the PC-3000 Flash to PC-3000 SSD. Why did we do it?

The reason was that recovering data with the chip-off method from SSDs was difficult and time-consuming. It took around 1 week to detect the correct order of the memory chips, fix the ECC errors, eliminate all the controller preparations and, finally, build the image.

It was a real pain even back then, but nowadays it is even more complicated to recover data from SSDs using the chip-off method due to the full encryption of the data inside the NAND memory chip or encryption with the AES-128 key.

These issues can be easily solved and bypassed via the PC-3000 SSD Software for the PC-3000 Express/UDMA/Portable III tools. We add more and more SSDs an..