모질라 재단에서 브라우저인 파이어폭스에 대한 보안 업데이트가 보안 업데이트가 진행이 되었습니다. 해당 보안 업데이트는 기본적으로 파이어폭스에 대한 보안 업데이트를 포함을 하고 있으며 그리고 윈도우 11버전 22H2 장치에서 브라우저를 실행하는 일부 사용자의 성능을 개선을 진행합니다.
보안 업데이트 내용은 다음과 같습니다.
CVE-2022-45403: Service Workers might have learned size of cross-origin media files
Description:Service Workers should not be able to infer information about opaque cross-origin responses; but timing information for cross-origin media combined with Range requests might have allowed them to determine the presence or length of a media file.
CVE-2022-45404:Fullscreen notification bypass
Description:Through a series of popup and window.print() calls, an attacker can cause a window to go fullscreen without the user seeing the notification prompt, resulting in potential user confusion or spoofing attacks.
CVE-2022-45405: Use-after-free in InputStream implementation
Description:Freeing arbitrary nsIInputStream's on a different thread than creation could have led to a use-after-free and potentially exploitable crash.
CVE-2022-45406: Use-after-free of a JavaScript Realm
Description:If an out-of-memory condition occurred when creating a JavaScript global, a JavaScript realm may be deleted while references to it lived on in a BaseShape. This could lead to a use-after-free causing a potentially exploitable crash.
CVE-2022-45407: Loading fonts on workers was not thread-safe
Description:If an attacker loaded a font using FontFace() on a background worker, a use-after-free could have occurred, leading to a potentially exploitable crash.
CVE-2022-45408: Fullscreen notification bypass via windowName
Description:Through a series of popups that reuse windowName, an attacker can cause a window to go fullscreen without the user seeing the notification prompt, resulting in potential user confusion or spoofing attacks.
CVE-2022-45409: Use-after-free in Garbage Collection
Description:The garbage collector could have been aborted in several states and zones and GCRuntime::finishCollection may not have been called, leading to a use-after-free and potentially exploitable crash
CVE-2022-45410: ServiceWorker-intercepted requests bypassed SameSite cookie policy
Description:When a ServiceWorker intercepted a request with FetchEvent, the origin of the request was lost after the ServiceWorker took ownership of it. This had the effect of negating SameSite cookie protections. This was addressed in the spec and then in browsers.
CVE-2022-45411: Cross-Site Tracing was possible via non-standard override headers
Description:Cross-Site Tracing occurs when a server will echo a request back via the Trace method, allowing an XSS attack to access to authorization headers and cookies inaccessible to JavaScript (such as cookies protected by HTTPOnly). To mitigate this attack, browsers placed limits on fetch() and XMLHttpRequest; however some webservers have implemented non-standard headers such as X-Http-Method-Override that override the HTTP method, and made this attack possible again. Firefox has applied the same mitigations to the use of this and similar headers.
CVE-2022-45412: Symlinks may resolve to partially uninitialized buffers
Description:When resolving a symlink such as file(:)///proc/self/fd/1, an error message may be produced where the symlink was resolved to a string containing unitialized memory in the buffer.
This bug only affects Firefox on Unix-based operated systems (Android, Linux, MacOS). Windows is unaffected.5413: SameSite=Strict cookies could have been sent cross-site via intent URLs
Description:Using the S.browser_fallback_url parameter parameter, an attacker could redirect a user to a URL and cause SameSite=Strict cookies to be sent.
This issue only affects Firefox for Android. Other operating systems are not affected.
CVE-2022-40674: Use-after-free vulnerability in expat
Description:A flaw in XML parsing could have led to a use-after-free causing a potentially exploitable crash.
In official releases of Firefox this vulnerability is mitigated by wasm sandboxing; versions managed by Linux distributions may have other settings.
CVE-2022-45415: Downloaded file may have been saved with malicious extension
Description:When downloading an HTML file, if the title of the page was formatted as a filename with a malicious extension, Firefox may have saved the file with that extension, leading to possible system compromise if the downloaded file was later ran.
CVE-2022-45416: Keystroke Side-Channel Leakage
Description:Keyboard events reference strings like "KeyA" that were at fixed, known, and widely-spread addresses. Cache-based timing attacks such as Prime+Probe could have possibly figured out which keys were being pressed.
CVE-2022-45417: Service Workers in Private Browsing Mode may have been written to disk
Description:Service Workers did not detect Private Browsing Mode correctly in all cases, which could have led to Service Workers being written to disk for websites visited in Private Browsing Mode. This would not have persisted them in a state where they would run again, but it would have leaked Private Browsing Mode details to disk.
CVE-2022-45418: Custom mouse cursor could have been drawn over browser UI
Description:If a custom mouse cursor is specified in CSS, under certain circumstances the cursor could have been drawn over the browser UI, resulting in potential user confusion or spoofing attacks.
CVE-2022-45419: Deleting a security exception did not take effect immediately
Description:If the user added a security exception for an invalid TLS certificate, opened an ongoing TLS connection with a server that used that certificate, and then deleted the exception, Firefox would have kept the connection alive, making it seem like the certificate was still trusted.
CVE-2022-45420: Iframe contents could be rendered outside the iframe
Description:Using tables inside of an iframe, an attacker could have caused iframe contents to be rendered outside the boundaries of the iframe, resulting in potential user confusion or spoofing attacks.
CVE-2022-45421: Memory safety bugs fixed in Firefox 107 and Firefox ESR 102.5
Description:Mozilla developers Andrew McCreight and Gabriele Svelto reported memory safety bugs present in Firefox 106 and Firefox ESR 102.4. Some of these bugs showed evidence of memory corruption and we presume that with enough effort some of these could have been exploited to run arbitrary code.
파이어폭스 사용자 분들 그리고 토르 브라우저 사용자 분들은 업데이트를 진행을 하시길 바랍니다.
Firefox 108 Stable은 2022년의 마지막 주요 브라우저 릴리스가 될 것임 버그 및 문제를 해결하기 위해 몇 가지 포인트 릴리스도 배포될 수 있음
모질라 는 브라우저에서 총 19개의 서로 다른 보안 문제를 수정 취약점의 가장 높은 심각도는 높음 등급들임
'소프트웨어 팁 > 보안 및 분석' 카테고리의 다른 글
외교 안보 국방분야 교수,북한 민간 전문가 노리는 Kimsuky(김수키) 워드 악성코드-법제처 국가법령정보센터.doc(2022.11.20) (0) | 2022.11.22 |
---|---|
윈도우 10 바탕 화면 및 작업 표시줄 문제 확인 및 해결 방법 (0) | 2022.11.21 |
윈도우 10 KB5020030 미리 보기 업데이트 (0) | 2022.11.18 |
윈도우 Windows DirectAccess 연결 문제 해결 (0) | 2022.11.17 |
윈도우 10 버전 21H1 2022년 12월 지원 종료 (0) | 2022.11.15 |
입사지원서 또는 이력서로 유포 되고 있는 LockBit 랜섬웨어-심시아.docx(2022.10.28) (7) | 2022.11.14 |
윈도우 10 KB5019959 및 KB5019966 보안 업데이트 (0) | 2022.11.10 |
네이버 고객센터 피싱 메일 분석-e9lhv32 iamfvk9 gov kr (2) | 2022.11.10 |