¶íÂÞ˹¡°Ö÷Ȩ»¥ÁªÍø¡±Ë¾·¨ÉúЧ£¬£¬£¬£¬£¬£¬¿ÉÓëÈ«Çò»¥ÁªÍø¶Ï¿ª£»£»£»£»£»£»£»Ê׸ö´ó¹æÄ£ÀûÓÃBlueKeep·ì϶µÄÍøÂç¹¥»÷»î¶¯
°ä²¼¹¦·ò 2019-11-04
°²È«×¨¼ÒKevin BeaumontÔÚÖÜÁù·¢ÏÖÊ׸öÀûÓÃBlueKeep·ì϶µÄ´ó¹æÄ£ºÚ¿Í¹¥»÷»î¶¯£¬£¬£¬£¬£¬£¬ÆäʱËûµÄ¶à¸öEternalPot RDPÃÛ¹ÞϵͳºöÈ»±ÀÀ£²¢³ÁÆô¡£¡£¡£¡£¡£¸Ã¹¥»÷Ö¼ÔÚ´«²¼ÃÅÂÞ±ÒÍÚ¿óľÂí¡£¡£¡£¡£¡£°²È«×êÑÐÈËÔ±Marcus Hutchins·ÖÎöÆäcrash dumpÎļþºóÈ·ÈÏÁËÕâÒ»·¢ÏÖ£¬£¬£¬£¬£¬£¬µ«°µÊ¾¸Ã¶ñÒâ´úÂëÉв»¾ß±¸×ÔÎÒ´«²¼Ö°ÄÜ¡£¡£¡£¡£¡£¹¥»÷ÕßËÆºõÊÇÏÈ´ÓInternetÉÏɨÃèÒ×Êܹ¥»÷µÄϵͳ£¬£¬£¬£¬£¬£¬¶øºóÔÙ¹¥»÷ËüÃÇ¡£¡£¡£¡£¡£Ä¿Ç°Éв»Ã÷ÏÔÕâ´Î¹¥»÷ÒѾϰȾÁ˼¸¶àϵͳ¡£¡£¡£¡£¡£
ÔÎÄÁ´½Ó£º
https://thehackernews.com/2019/11/bluekeep-rdp-vulnerability.html2¡¢×êÑÐÈËÔ±Åû¶rConfigÖеÄÁ½¸ö佨²¹RCE·ì϶
°²È«×êÑÐÈËÔ±ÔÚrConfig¹¤¾ßÖз¢ÏÖÁ½¸ö佨¸´µÄ¹Ø¼üRCE·ì϶£¬£¬£¬£¬£¬£¬²¢Åû¶ÁËÓйØPoC¡£¡£¡£¡£¡£rConfigÊÇÓÃPHP±àдµÄ¿ªÔ´ÍøÂçÉ豸ÅäÖù¤¾ß£¬£¬£¬£¬£¬£¬Æ¾¾Ý¸ÃÏîÖ÷ÕÅÍøÕ¾£¬£¬£¬£¬£¬£¬rConfig±»ÓÃÓÚÖÎÀí³¬¹ý330Íò¸öÍøÂçÉ豸¡£¡£¡£¡£¡£ÕâÁ½¸ö·ì϶Ô̺¬ajaxServerSettingsChk.phpÖÐδ¾Éí·ÝÑéÖ¤µÄRCE£¨CVE-2019-16662£©ºÍsearch.crud.phpÖо¹ýÉí·ÝÑéÖ¤µÄRCE£¨CVE-2019-16663£©¡£¡£¡£¡£¡£¹¥»÷Õß¿Éͨ¹ýGET²ÎÊý½Ó¼ûÎļþ²¢ÔÚÖ¸±ê·þÎñÆ÷ÉÏÖ´ÐжñÒâºÅÁî¡£¡£¡£¡£¡£ËùÓа汾µÄrConfig¶¼ÊÜÓ°Ï죬£¬£¬£¬£¬£¬Ô̺¬×îа汾3.9.2¡£¡£¡£¡£¡£rConfigÏîÄ¿ÊØ»¤ÕßÉÐδ¶Ô·ì϶½øÐлØÓ¦£¬£¬£¬£¬£¬£¬Òò¶øµ±Ç°Ã»ÓпÉÓõĽ¨¸´²¹¶¡¡£¡£¡£¡£¡£
ÔÎÄÁ´½Ó£º
https://thehackernews.com/2019/11/rConfig-network-vulnerability.html3¡¢Å¦Ô¼²¼Â³¿ËÁÖÒ½ÔºÔâ¶ñÒâÈí¼þ¹¥»÷ÇÒÊý¾ÝÎÞ·¨¸´Ô
ŦԼ²¼Â³¿ËÁÖÒ½ÔºÖÐÐİ䲼Êý¾Ýй¶֪ͨ³Æ£¬£¬£¬£¬£¬£¬¸ÃÒ½ÔºÔÚ7ÔÂÏÂÑ®·¢ÏÖ·þÎñÆ÷ÉÏ´æÔÚijЩÒì³£»£»£»£»£»£»£»î¶¯£¬£¬£¬£¬£¬£¬¾¹ýµ÷²é¸ÃҽԺȷ¶¨Ä³Ð©¼ÓÃÜÀà¶ñÒâÈí¼þ·ÛËéÁËҽԺϵͳµÄÔËÐÓ×£¡£¡£¡£¡£Ã»ÓÐÖ¤¾ÝÅúעδ¾ÊÚȨµÄµÚÈýÕßÏÖʵ½Ó¼û»ò»ñÈ¡ÁËÊý¾Ý£¬£¬£¬£¬£¬£¬µ«Ä³Ð©»¼ÕßÊý¾ÝÎÞ·¨¸´Ô£¬£¬£¬£¬£¬£¬Ô̺¬»¼ÕßµÄÐÕÃûºÍÐÄÔà¡¢ÑÀ³ÝͼÏñ¡£¡£¡£¡£¡£¸ÃÒ½ÔºÉÐδ·¢ÏÖÈκÎÏÖʵ»òÊÔͼ½Ó¼û¡¢ÀÄÓÃÒ½ÁÆÐÅÏ¢/Ó×ÎÒÐÅÏ¢µÄÇé¿ö¡£¡£¡£¡£¡£
ÔÎÄÁ´½Ó£º
https://finance.yahoo.com/news/brooklyn-hospital-center-notice-data-230000523.html4¡¢Î¬¶û¾©ÈºµºWAPA³ÉΪClick2GovÊý¾Ýй¶µÄ×îÐÂÊܺ¦Õß
ÔÎÄÁ´½Ó£º
https://stcroixsource.com/2019/10/31/wapa-advises-customers-to-continue-monitoring-credit-card-accounts-for-fraudulent-charges/
5¡¢µÂ¿ËÈøË¹ÖÝÐÂÊý¾Ýй¶֪ͨ·¨°¸½«ÓÚ2020ÄêÆð³¢ÊÔ
µÂ¿ËÈøË¹ÖݵÄÐÂÊý¾Ýй¶֪ͨ·¨°¸½«ÓÚ2020Äê1ÔÂ1ÈÕÆðʵÐÓ×£¡£¡£¡£¡£¸Ã·¨°¸½¨¸ÄÁË¡¶µÂ¿ËÈøË¹ÖÝÉí·Ý͵ÇÔ·¨Âɺͱ£»£»£»£»£»£»£»¤·¨¡·£¬£¬£¬£¬£¬£¬ÒªÇóÆóÒµÔÚÈ·¶¨²úÉúÊý¾ÝÎ¥¹æºóÔÚ60ÌìÄÚ֪ͨµÂ¿ËÈøË¹ÖݾÓÃñ¡£¡£¡£¡£¡£´Ë±í£¬£¬£¬£¬£¬£¬ÈôÊÇÎ¥¹æÊÂÎñÓ°ÏìÁ˳¬¹ý250ÃûµÂ¿ËÈøË¹ÖݾÓÃñ£¬£¬£¬£¬£¬£¬ÆóÒµ±ØÐëÔÚͳһ¹¦·ò£¨60Ì죩ÄÚÏòÖÝ˾·¨²¿³¤ÌṩÊÂÎñ֪ͨ£¬£¬£¬£¬£¬£¬¸Ã֪ͨӦ¸ÃÔ̺¬¾ßÌåÊÂÎñÃèÊö/ʹÓõÄÃô¸ÐÐÅÏ¢¡¢ÊÜÓ°ÏìµÄÈËÊý¡¢ÒѲÉÈ¡¼°½«Òª²ÉÈ¡µÄ´ëÊ©ÒÔ¼°ÊÇ·ñÒÑ֪ͨ·¨Âɲ¿ÃŵÈÐÅÏ¢¡£¡£¡£¡£¡£
ÔÎÄÁ´½Ó£º
https://www.natlawreview.com/article/texas-updates-data-breach-notification-requirements
6¡¢¶íÂÞ˹¡°Ö÷Ȩ»¥ÁªÍø¡±Ë¾·¨ÉúЧ£¬£¬£¬£¬£¬£¬¿ÉÓëÈ«Çò»¥ÁªÍø¶Ï¿ª
¶íÂÞ˹¡°Ö÷Ȩ»¥ÁªÍø¡±Ë¾·¨ÔÚÉÏÖÜÎåÉúЧ£¬£¬£¬£¬£¬£¬Õ⽫ʹ¶íÂÞ˹µ±¾Ö¿ÉÄܽ«¸Ã¹úÓëÈ«Çò»¥ÁªÍø¶Ï¿ªÏνӡ£¡£¡£¡£¡£ÕâÏî˾·¨ÓÉÆÕ¾©×ÜͳÔÚ5Ô·ÝÇ©Ê𣬣¬£¬£¬£¬£¬ÒªÇóISP×°Öõ±¾ÖÌṩµÄ¼¼ÊõÉ豸ÒÔ½øÐÐÁ÷Á¿²é³£¬£¬£¬£¬£¬£¬Õâ¿ÉÄÜΪ´ó¹æÄ£¼à¶½´ò¿ªÁË´óÃÅ¡£¡£¡£¡£¡£Æ¾¾Ý¶íÂÞ˹µ±¾ÖµÄ˵·¨£¬£¬£¬£¬£¬£¬¸Ã˾·¨Ö¼ÔÚÈ·±£¼´±ã¶Ï¿ªÓëÈ«Çò»¥ÁªÍøµÄÏνÓÒ²Äܹ»½Ó¼û¶íÂÞ˹վµã£¬£¬£¬£¬£¬£¬ÒÔÓ¦¶ÔÓÉÍøÂç¹¥»÷»ò°²È«ÊÂÎñµ¼ÖµÄÖжϡ£¡£¡£¡£¡£¸Ã˾·¨½«Ê¹¶íÂÞ˹µ±¾Ö¿ÉÄÜÉó²éÔÚÏßÄÚÈݲ¢¼à¶½ÍøÃñ¡£¡£¡£¡£¡£
ÔÎÄÁ´½Ó£º
https://securityaffairs.co/wordpress/93315/laws-and-regulations/russia-controversial-law-russia.html


¾©¹«Íø°²±¸11010802024551ºÅ