Появился повод проверить своих поставщиков- есть ли у них поставки в Китай, если да велика вероятность в их оборудовании бэкдоров специально для Китая.
Да и вообще радуют пассажи, бэкдор? Все делают- это!
Но вообще это желтое издание и мы ему не верим! Да?
Lenovo: Companies working in China may have to install local backdoors
#lenovo #backdoor #china
https://www.theinquirer.net/inquirer/news/3062910/lenovo-companies-working-in-china-may-have-to-install-local-backdoors
Да и вообще радуют пассажи, бэкдор? Все делают- это!
Но вообще это желтое издание и мы ему не верим! Да?
Lenovo: Companies working in China may have to install local backdoors
#lenovo #backdoor #china
https://www.theinquirer.net/inquirer/news/3062910/lenovo-companies-working-in-china-may-have-to-install-local-backdoors
http://www.theinquirer.net
Lenovo: Companies working in China may have to install local backdoors
But emphasises that this doesn't apply to the rest of the world
Forwarded from Vulnerability Management and more
Vulnerability Life Cycle and Vulnerability Disclosures
Vulnerability Life Cycle diagram shows possible states of the #vulnerability. In a previous post I suggested to treat vulnerabilities as bugs. Every known #vulnerability, as same as every #bug, was implemented by some software developer at some moment of time and was fixed at some moment of time later. What happens between this two events?
Right after the #vulnerability was implemented in the code by some developer ( creation ) nobody knows about it. Well, of course, if it was done unintentionally. By the way, making backdoors look like an ordinary vulnerabilities it’s a smart way to do such things. 😉 But let’s say it #WAS done unintentionally.
Time passed and some researcher found ( discovery ) this #vulnerability and described it somehow. What’s next? It depends on who was that researcher.
#vulnerability #Stuxnet #PoC #malware #exploit #EternalBlue #bughunter #backdoor #0day #VulnerabilityManagement #VulnerabilityDatabase #Concept
Read more: https://avleonov.com/2019/01/30/vulnerability-life-cycle-and-vulnerability-disclosures/
Vulnerability Life Cycle diagram shows possible states of the #vulnerability. In a previous post I suggested to treat vulnerabilities as bugs. Every known #vulnerability, as same as every #bug, was implemented by some software developer at some moment of time and was fixed at some moment of time later. What happens between this two events?
Right after the #vulnerability was implemented in the code by some developer ( creation ) nobody knows about it. Well, of course, if it was done unintentionally. By the way, making backdoors look like an ordinary vulnerabilities it’s a smart way to do such things. 😉 But let’s say it #WAS done unintentionally.
Time passed and some researcher found ( discovery ) this #vulnerability and described it somehow. What’s next? It depends on who was that researcher.
#vulnerability #Stuxnet #PoC #malware #exploit #EternalBlue #bughunter #backdoor #0day #VulnerabilityManagement #VulnerabilityDatabase #Concept
Read more: https://avleonov.com/2019/01/30/vulnerability-life-cycle-and-vulnerability-disclosures/