This may lead to the disclosure of sensitive information, a denial of service, or the installation of malicious software. An issue existed in WebKit where a maliciously crafted web site could lead to cross-site scripting. This issue was addressed by filtering cross-site requests. An issue existed in the handling of certain malformed web site cookies. This issue was addressed by rejecting invalid cookies. An issue existed in the handling of an HTTP header named “X-FRAME-OPTIONS”. This issue was addressed by not parsing the header anymore. An uninitialized memory issue in WebKit allowed remote attackers to execute arbitrary code via a crafted web site, as demonstrated by 1C1Q. This issue was addressed by fixing an uninitialized memory issue. A memory corruption issue existed in WebKit. An attacker could force the user to download a malicious extension. This issue was fixed by ensuring extensions are signed. An issue existed in WebKit where data communicated over HTTP was not properly validated. This issue was addressed by validating data over HTTP. An issue existed in WebKit where data communicated over a custom protocol was not properly validated. This issue was addressed by validating data over a custom protocol. An issue existed in WebKit where data communicated over WebSockets was not properly validated. This issue was addressed by validating data over WebSockets. An issue existed in WebKit where data communicated over localStorage was not properly validated
Security Improvements to iFrame Handling
A security improvement was made in WebKit where the handling of iFrames from a content-loading web site was improved. This issue was addressed by not treating iFrames from content-loading web sites differently than other frames.
Vulnerability overview
The following CVEs have been assigned to this vulnerability:
CVE-2022-32821: An issue existed in WebKit where a maliciously crafted web site could lead to cross-site scripting. This issue was addressed by filtering cross-site requests.
CVE-2022-32822: An issue existed in the handling of certain malformed web site cookies. This issue was addressed by rejecting invalid cookies.
CVE-2022-32823: An issue existed in the handling of an HTTP header named “X-FRAME-OPTIONS”. This issue was addressed by not parsing the header anymore.
CVE-2022-32824: A memory corruption issue existed in WebKit. An attacker could force the user to download a malicious extension. This issue was fixed by ensuring extensions are signed.
CVE-2022-32825: An issue existed in WebKit where data communicated over HTTP was not properly validated. This issue was addressed by validating data over HTTP
Timeline
Published on: 09/23/2022 19:15:00 UTC
Last modified on: 09/27/2022 17:55:00 UTC