Call/WhatsApp/Text: +44 20 3289 5183

Question: What disclosure strategy was used when BlueKeep became public knowledge?

01 Nov 2022,3:47 PM

 

Read up on the vulnerability dubbed 'BlueKeep' and answer the following:

1. What disclosure strategy was used when BlueKeep became public knowledge?

2. What is the BlueKeep CVE ID?

3. What is the BlueKeep CVSS Score?

4. Which STRIDE aspects apply to BlueKeep?

5. Are exploits currently available?

6. Have patched been released yet?

Read the article at https://arstechnica.com/information-technology/2017/09/massive-equifax-breach-caused-by-failure-to-patch-two-month-old-bug/

7. What is the CVE of this particular vulnerability?

8. Who discovered it?

9. What are the CVSS score of the vulnerability?

10. Has a patch been released? If so, when?

11. Has the vulnerability been exploited?

12. How easily available is the exploit?

13. What is the effect of successful exploitation?

 

Expert answer

 

Microsoft decided to issue a patch for the vulnerability without waiting for a coordinated disclosure from security researchers. This decision was made after the WannaCry ransomware attack, which used a leaked NSA exploit. Microsoft felt that it was better to patch the vulnerability and risk negative publicity than wait for someone else to discover and weaponize it.

 

What is the 'BlueKeep' vulnerability?

The BlueKeep security flaw is a critical Remote Desktop Services (RDS) vulnerability that was discovered in Microsoft’s Windows operating system. The flaw could allow an attacker to remotely execute code on a vulnerable system without authentication, potentially leading to the compromise of the entire system.

 

What is the significance of this vulnerability?

This vulnerability is significant because it allows attackers to remotely take control of a victim's computer without needing any credentials or user interaction. This makes it much easier for attackers to exploit, as they do not need to trick users into clicking on malicious links or opening attachments.

 

How did Microsoft respond to this vulnerability?

Microsoft released a patch for the vulnerability on May 14, 2019, just days after the discovery of the flaw. This was an unusual move for Microsoft, as they usually wait for a coordinated disclosure from security researchers before releasing a patch. However, they felt that the risk of someone else weaponizing the vulnerability was too high, and decided to release the patch early.

 

What are some potential consequences of not patching this vulnerability?

If this vulnerability is not patched, it could be exploited by attackers to remotely take control of unpatched systems. This could lead to widespread compromise, as has been seen in previous ransomware attacks such as WannaCry. Additionally, attackers could use this flaw to create a worm that spreads automatically to other vulnerable systems on the same network. This would allow them to quickly compromise a large number of systems with little effort.

 

What can users do to protect themselves from this vulnerability?

Users should install the patch from Microsoft as soon as possible to protect their systems from this vulnerability. Additionally, they should ensure that their antivirus software is up-to-date and running, as this can help to detect and block malicious attacks. Finally, users should exercise caution when opening email attachments or clicking on links, even if they appear to come from a trusted source.

Stuck Looking For A Model Original Answer To This Or Any Other
Question?


Related Questions

What Clients Say About Us

WhatsApp us