크롬 최신버전 정보 - Chrome 63.0.3239.84(공식빌드) 업데이트 배포 본문

Smart Working

크롬 최신버전 정보 - Chrome 63.0.3239.84(공식빌드) 업데이트 배포

삶의 행복을 공유하는 하나모자란천사

구글은 Chrome Releases를 통해서 현지 시간 기준(Wednesday, December 6, 2017), 국내 기준 오늘 Chrome 63.0.3239.84 공식빌드 업데이트를 배포했다. 이번 업데이트는 보안과 관련하여 37건의 버그가 수정 되었으며, 매우 중요한 업데이트 1건을 포함하고, 높은 위험 수준의 버그 패치도 6건이 포함되어 있다. 상세한 내용은 Chrome Releases를 통해서 확인 가능하다. 이번 업데이트의 경우도 신규 설치는 구글 크롬 웹사이트에서 설치하면 최신 공식빌드가 설치가 되고, 기존 사용자의 경우 '설정 > 도움말 > 크롬정보'를 통해서 설치할 수 있다.



아래는 기존 크롬 사용 중 크롬 업데이트를 진행하는 과정이다.



설정에서 크롬정보를 클릭하면 최신 공식빌드 적용 유무를 검색하고, 업데이트 필요 시 자동으로 업데이트를 적용하고 업데이트 적용을 위해 크롬을 다시 시작하라고 한다.



크롬을 다시 시작하면 아래와 같이 최신 공식빌드(Chrome 버전 63.3239.84)가 적용된 것을 확인할 수 있다.



이번 공식빌드 배포와 관련된 상세한 정보는 아래 크롬 블로그인 Chrome Releases를 통해서 확인할 수 있다.



Stable Channel Update for Desktop

Wednesday, December 6, 2017

The Chrome team is delighted to announce the promotion of Chrome 63 to the stable channel for Windows, Mac and Linux. This will roll out over the coming days/weeks.

 Chrome 63.0.3239.84 contains a number of fixes and improvements -- a list of changes is available in the log. Watch out for upcoming Chrome and Chromium blog posts about new features and big efforts delivered in 63.

 Security Fixes and Rewards

Note: Access to bug details and links may be kept restricted until a majority of users are updated with a fix. We will also retain restrictions if the bug exists in a third party library that other projects similarly depend on, but haven’t yet fixed.

 This update includes 37 security fixes. Below, we highlight fixes that were contributed by external researchers. Please see the Chrome Security Page for more information.

 [$10500][778505] Critical CVE-2017-15407: Out of bounds write in QUIC. Reported by Ned Williamson on 2017-10-26

[$6337][762374] High CVE-2017-15408: Heap buffer overflow in PDFium. Reported by Ke Liu of Tencent's Xuanwu LAB on 2017-09-06

[$5000][763972] High CVE-2017-15409: Out of bounds write in Skia. Reported by Anonymous on 2017-09-11

[$5000][765921] High CVE-2017-15410: Use after free in PDFium. Reported by Luật Nguyễn (@l4wio) of KeenLab, Tencent on 2017-09-16

[$5000][770148] High CVE-2017-15411: Use after free in PDFium. Reported by Luật Nguyễn (@l4wio) of KeenLab, Tencent on 2017-09-29

[$3500][727039] High CVE-2017-15412: Use after free in libXML. Reported by Nick Wellnhofer on 2017-05-27

[$500][766666] High CVE-2017-15413: Type confusion in WebAssembly. Reported by Gaurav Dewan(@007gauravdewan) of Adobe Systems India Pvt. Ltd. on 2017-09-19

[$3337][765512] Medium CVE-2017-15415: Pointer information disclosure in IPC call. Reported by Viktor Brange of Microsoft Offensive Security Research Team on 2017-09-15

[$2500][779314] Medium CVE-2017-15416: Out of bounds read in Blink. Reported by Ned Williamson on 2017-10-28

[$2000][699028] Medium CVE-2017-15417: Cross origin information disclosure in Skia . Reported by Max May on 2017-03-07

[$1000][765858] Medium CVE-2017-15418: Use of uninitialized value in Skia. Reported by Kushal Arvind Shah of Fortinet's FortiGuard Labs on 2017-09-15

[$1000][780312] Medium CVE-2017-15419: Cross origin leak of redirect URL in Blink. Reported by Jun Kokatsu (@shhnjk) on 2017-10-31

[$500][777419] Medium CVE-2017-15420: URL spoofing in Omnibox. Reported by WenXu Wu of Tencent's Xuanwu Lab on 2017-10-23

[$TBD][774382] Medium CVE-2017-15422: Integer overflow in ICU. Reported by Yuan Deng of Ant-financial Light-Year Security Lab on 2017-10-13

[$500][778101] Low CVE-2017-15423: Issue with SPAKE implementation in BoringSSL. Reported by Greg Hudson on 2017-10-25

[$N/A][756226] Low CVE-2017-15424: URL Spoof in Omnibox. Reported by Khalil Zhani on 2017-08-16

[$N/A][756456] Low CVE-2017-15425: URL Spoof in Omnibox. Reported by xisigr of Tencent's Xuanwu Lab on 2017-08-17

[$N/A][756735] Low CVE-2017-15426: URL Spoof in Omnibox. Reported by WenXu Wu of Tencent's Xuanwu Lab on 2017-08-18

[$N/A][768910] Low CVE-2017-15427: Insufficient blocking of JavaScript in Omnibox. Reported by Junaid Farhan (fb.me/junaid.farhan.54) on 2017-09-26

 We would also like to thank all security researchers that worked with us during the development cycle to prevent security bugs from ever reaching the stable channel.

As usual, our ongoing internal security work was responsible for a wide range of fixes:

[792099] Various fixes from internal audits, fuzzing and other initiatives

Many of our security bugs are detected using AddressSanitizer, MemorySanitizer, UndefinedBehaviorSanitizer, Control Flow Integrity, libFuzzer, or AFL.

 Interested in switching release channels? Find out how.  If you find a new issue, please let us know by filing a bug. The community help forum is also a great place to reach out for help or learn about common issues.

 Krishna Govind

Google Chrome

 Share on Google+  Share on Twitter  Share on Facebook




위에서 언급이 되었지만 이번 공식빌드에는 심각한 위험 1건을 포함하여, 높은 위험의 버그 패치 6건을 포함하고 있음으로 사용 중인 크롬의 버전을 확인 후 최신 버전 업데이트를 적용하기를 권고한다.


Comments 0
댓글쓰기 폼

애드센스 (Adsense)

애드센스 (Adsense)

텐핑 (10PING)

애드센스 (Adsense)

애드센스 (Adsense)

Total
258,296
Today
112
Yesterday
1,028