- Joined
- Jun 28, 2017
- Messages
- 6,805
- Reaction score
- 648
South Africa’s biggest forum. Discuss, discover, and connect with thousands of members.
The article doesn't say when backdoor had been discovered, by whom and how long it took it to patch.
The longer time indicate MS intent to replace it with a different backdoor.
The method how Microsoft fix these 'bugs' is not acceptable. The (so called) "virus definition file" is actually an active executable code running in NT System Authority. It is very unsafe, as every new "virus definition file" can activate new backdoors. Starting from v.1709 MS 'telemetry' spying and crypto-currency engine is being integrated with Defender, so now you may have better understanding a real purpose of the "virus definition file".
What?
The article doesn't say when backdoor had been discovered, by whom and how long it took it to patch.
The longer time indicate MS intent to replace it with a different backdoor.
The method how Microsoft fix these 'bugs' is not acceptable. The (so called) "virus definition file" is actually an active executable code running in NT System Authority. It is very unsafe, as every new "virus definition file" can activate new backdoors. Starting from v.1709 MS 'telemetry' spying and crypto-currency engine is being integrated with Defender, so now you may have better understanding a real purpose of the "virus definition file".
The article doesn't say when backdoor had been discovered, by whom and how long it took it to patch.
The longer time indicate MS intent to replace it with a different backdoor.
The method how Microsoft fix these 'bugs' is not acceptable. The (so called) "virus definition file" is actually an active executable code running in NT System Authority. It is very unsafe, as every new "virus definition file" can activate new backdoors. Starting from v.1709 MS 'telemetry' spying and crypto-currency engine is being integrated with Defender, so now you may have better understanding a real purpose of the "virus definition file".
Exactly as said.What?
The longer time indicate MS intent to replace it with a different backdoor.
The (so called) "virus definition file" is actually an active executable code running in NT System Authority. It is very unsafe, as every new "virus definition file" can activate new backdoors.
How do you know it for sure?Since the staff writer didn't get this info, here you go:
It's called CVE-2018-0986.
How do you know it for sure?
How do I know what?
The statement you made in a quoted part.How do I know what?
Exactly as said.
The statement you made in a quoted part.
Yesterday, April 3, Microsoft released an emergency security update via Windows Update that fixes CVE-2018-0986, a vulnerability in the Microsoft Malware Protection Engine (MMPE).
MMPE (mpengine.dll) is the malware scanning, detection, and cleaning component of several Microsoft antivirus and antispyware programs, such as Windows Defender, Microsoft Security Essentials, Microsoft Endpoint Protection, Windows Intune Endpoint Protection, and Microsoft Forefront Endpoint Protection.
Vulnerability rated "critical"
A Google security researcher discovered a flaw in the MMPE component that allows attackers to execute malicious code on a Windows machine. Because the MMPE component runs with system privileges, the bug, if exploited, can grant attackers complete control over a victim's system.
Microsoft rated the vulnerability as "critical," its highest severity level. "To exploit this vulnerability, a specially crafted file must be scanned by an affected version of the Microsoft Malware Protection Engine," the company said in an advisory.
Nope. Not in the article.Cause it says so!?
May I propose that we implement a system that bans sajunky from any threads that have the word Microsoft or Windows in it?
The statement you made in a quoted part.