• Log In
  • Skip to primary navigation
  • Skip to main content
  • Skip to primary sidebar
  • HomePage
  • About
  • Structure
  • Schedule
    • First Half of the Semester
      • Week 1: Overview of Course
      • Week 2: TCP/IP and Network Architecture
      • Week 3: Reconnaissance
      • Week 4: Vulnerability scanning
      • Week 5: System and User enumeration
      • Week 6: Sniffers
      • Week 7: NetCat, Hellcat
    • Second Half of the Semester
      • Week 8: Social Engineering, Encoding, and Encryption
      • Week 9: Malware
      • Week 10: Web application hacking, Intercepting Proxies, and URL Editing
      • Week 11: SQL injection
      • Week 12: Web Services
      • Week 13: Evasion Techniques
      • Week 14: Review of all topics and wrap up discussion
  • Assignments
    • Analysis Reports
    • Quizzes & Tests
  • Webex
  • Harvard Coursepack
  • Gradebook

ITACS 5211: Introduction to Ethical Hacking

Wade Mackay

Google discloses major Windows bug

November 1, 2016 by Brent Easley 2 Comments

http://www.theverge.com/2016/10/31/13481502/windows-vulnerability-sandbox-google-microsoft-disclosure

This is a good article for this week’s lesson.  The Google Threat analysis group disclosed a critical vulnerability in Windows in a public post on the company’s security blog.  The vulnerability allows hackers to escape from security sandboxes through a weakness in the win32k system.  Google went public ten days after reporting the bug to Microsoft, before a patch could be deployed.  Google has already sent out a fix to protect users that use Chrome and Windows is still vulnerable.

 

Filed Under: Week 10: Web Application Hacking Tagged With:

Reader Interactions

Comments

  1. Ahmed A. Alkaysi says

    November 2, 2016 at 10:38 am

    I don’t like how Google went public before Microsoft sent a patch out. This just increases the risk of hackers who might not have known about this to exploit it. Even if they went public, how is the general public going to use this new-found knowledge to defend themselves? I understand that Google has a 7 day policy for vendors to either send a patch or disclose ways to mitigate the issue, and I really like this idea. However, I don’t agree on their decision to disclose this issue if that criteria is not met.

    Log in to Reply
  2. Mauchel Barthelemy says

    November 5, 2016 at 9:05 am

    Apparently, Microsoft is not pleased with the way Google handled this situation. It’s a good thing to discover the vulnerability and share it, but Microsoft feels that it should have been allowed a little bit more time to work on a patch. Companies need to develop a better coordination approach when discovering vulnerabilities of this nature for the common good of cyber security.

    Log in to Reply

Leave a Reply Cancel reply

You must be logged in to post a comment.

Primary Sidebar

Weekly Discussions

  • Uncategorized (133)
  • Week 01: Overview (1)
  • Week 02: TCP/IP and Network Architecture (8)
  • Week 03: Reconnaisance (25)
  • Week 04: Vulnerability Scanning (19)
  • Week 05: System and User Enumeration (15)
  • Week 06: Sniffers (9)
  • Week 07: NetCat and HellCat (11)
  • Week 08: Social Engineering, Encoding and Encryption (12)
  • Week 09: Malware (14)
  • Week 10: Web Application Hacking (12)
  • Week 11: SQL Injection (11)
  • Week 12: Web Services (10)
  • Week 13: Evasion Techniques (7)
  • Week 14: Review of all topics (5)

Copyright © 2025 · Magazine Pro Theme on Genesis Framework · WordPress · Log in