Specter and Meltdown are still not fully resolved and a new vulnerability jumps, in this case only in AMD processors, specifically a serious security flaw in AMD Secure, which the company knows ... SINCE SEPTEMBER!

We are still at odds with Specter and Metldown, a serious vulnerability that mainly affects Intel processors, but also affects AMD and ARM processors and that has shaken the industry and that has also caused Intel to be seen under various demands. Well, there is no rest time, because now it is the AMD processors that are affected by a significant vulnerability and that is because the year is starting very uphill for the large processor manufacturers.

The vulnerability detected has to do with AMD Secure, a co-processor of the company's processors and which, luckily, is easily corrected, since with an update of the BIOS, UEFI or firmware, it is more than enough . Previously this co-processor, received the name of AMD Platform Security Processor or PSP. This is nothing more than a chip-on-chip security system and it looks a lot like the Intel Management Engine, which has been criticized on several occasions. The Intel and AMD systems are co-processors that are next to the cores, specifically this one from AMD together with the AMD64 x86, which has the mission of loading an independent operating system, which manages several operations related to security of the data that is processed.

Cfir Cohen has been the one who discovered the vulnerability and he is part of the security team of Google Cloud Security Team. This security expert says that he has detected the vulnerability in the Trusted Platform Module (TPM), which is within the AMD Secure. TPM's mission is to store critical system data, such as passwords, certificates and encryption keys, within a secure environment and outside the processor's own cores, something that makes it easily accessible.

This Google researcher reported the vulnerability to the company in SEPTEMBER, but the information has not been known until now. AMD told him in December that they had already created a patch and are finalizing its release. Time has passed and we are in January and the company has not launched it yet, so it has jumped to the public, to put pressure on the company. It seems that the two companies are sloppy and the safety of the users does not matter much to them, because they are not in a hurry to solve their shit. We have been eight days of the year and we are going to scandal, practically, every two days.