The security of the devices we use while living in a time when all of our information has been transferred to the digital world has become very important, however, although companies make efforts in this regard, malicious people continue to struggle against companies with the same determination. By identifying a vulnerability found in companies’ software, these people can perhaps capture the information of millions of people. We’ve seen a few examples of this incident recently on the Android side, and these issues have been fixed, but a new vulnerability has been discovered today.
It covers all Android users:
The vulnerability detected today is much more critical than the vulnerabilities detected recently, as this vulnerability has the potential to affect all users using the Android operating system, rather than affecting a particular audience. Moreover, it does not matter which version of Android users have. The new vulnerability detected allows hackers who take advantage of this vulnerability to access a user’s bank accounts, camera, photos, messages, and login information. Moreover, the hacker, who takes advantage of the vulnerability, can get all this information undetected. Another critical vulnerability found last year was called StrandHogg 2.0, a continuation of StrandHogg. The vulnerability is more dangerous than last year, according to Norwegian security company Promon. Hackers are able to attack more widely with this vulnerability. The StrandHogg 2.0 vulnerability leaves no trace behind hackers. The vulnerability uses a process called ‘reflection.’ In this way, the counterfeit of the application they actually try to use is confronted with the users. Users fill their information in this application because they cannot understand this. You may have been worried when you heard about the vulnerability, but according to the statement from Google, the vulnerability does not affect you for now. According to Google, nobody affected by this vulnerability has been detected so far. The company also said that they have released a patch for this error.
