MozillaFirefox-branding-SLE (SUSE:Manager Retail Branch Server 4.1) — known CVEs & security advisories

Known CVE vulnerabilities and GitHub Security Advisories affecting the SUSE:Manager Retail Branch Server 4.1 package MozillaFirefox-branding-SLE, with affected version ranges, CVSS severity, EPSS exploit prediction, and CISA KEV status.

CVEs (34)

• CVE-2022-34485 — CVSS 9.8 (critical): Mozilla developers Bryce Seager van Dyk and the Mozilla Fuzzing Team reported potential vulnerabilities present in Firefox 101. Some of…
• CVE-2022-34470 — CVSS 9.8 (critical): Session history navigations may have led to a use-after-free and potentially exploitable crash. This vulnerability affects Firefox < 102…
• CVE-2022-34476 — CVSS 9.8 (critical): ASN.1 parsing of an indefinite SEQUENCE inside an indefinite GROUP could have resulted in the parser accepting malformed ASN.1. This…
• CVE-2022-40962 — CVSS 8.8 (high): Mozilla developers Nika Layzell, Timothy Nikkel, Sebastian Hengst, Andreas Pehrson, and the Mozilla Fuzzing Team reported memory safety…
• CVE-2022-2505 — CVSS 8.8 (high): Mozilla developers and the Mozilla Fuzzing Team reported memory safety bugs present in Firefox 102. Some of these bugs showed evidence of…
• CVE-2022-34468 — CVSS 8.8 (high): An iframe that was not permitted to run scripts could do so if the user clicked on a <code>javascript:</code> link. This vulnerability…
• CVE-2022-34480 — CVSS 8.8 (high): Within the <code>lg_init()</code> function, if several allocations succeed but then one fails, an uninitialized pointer would have been…
• CVE-2022-34481 — CVSS 8.8 (high): In the <code>nsTArray_Impl::ReplaceElementsAt()</code> function, an integer overflow could have occurred when the number of elements to…
• CVE-2022-34482 — CVSS 8.8 (high): An attacker who could have convinced a user to drag and drop an image to a filesystem could have manipulated the resulting filename to…
• CVE-2022-34483 — CVSS 8.8 (high): An attacker who could have convinced a user to drag and drop an image to a filesystem could have manipulated the resulting filename to…
• CVE-2022-34484 — CVSS 8.8 (high): The Mozilla Fuzzing Team reported potential vulnerabilities present in Thunderbird 91.10. Some of these bugs showed evidence of memory…
• CVE-2022-38473 — CVSS 8.8 (high): A cross-origin iframe referencing an XSLT document would inherit the parent domain's permissions (such as microphone or camera access)…
• CVE-2022-38477 — CVSS 8.8 (high): Mozilla developer Nika Layzell and the Mozilla Fuzzing Team reported memory safety bugs present in Firefox 103 and Firefox ESR 102.1. Some…
• CVE-2022-38478 — CVSS 8.8 (high): Members the Mozilla Fuzzing Team reported memory safety bugs present in Firefox 103, Firefox ESR 102.1, and Firefox ESR 91.12. Some of…
• CVE-2022-2200 — CVSS 8.8 (high): If an object prototype was corrupted by an attacker, they would have been able to set undesired attributes on a JavaScript object, leading…
• CVE-2022-34469 — CVSS 8.1 (high): When a TLS Certificate error occurs on a domain protected by the HSTS header, the browser should not allow the user to bypass the…
• CVE-2022-34477 — CVSS 7.5 (high): The MediaError message property should be consistent to avoid leaking information about cross-origin resources; however for a same-site…
• CVE-2022-36319 — CVSS 7.5 (high): When combining CSS properties for overflow and transform, the mouse cursor could interact with different coordinates than displayed. This…
• CVE-2022-38476 — CVSS 7.5 (high): A data race could occur in the <code>PK11_ChangePW</code> function, potentially leading to a use-after-free vulnerability. In Firefox, this…
• CVE-2022-40958 — CVSS 6.5 (medium): By injecting a cookie with certain special characters, an attacker on a shared subdomain which is not a secure context could set and thus…
• CVE-2022-40960 — CVSS 6.5 (medium): Concurrent use of the URL parser with non-UTF-8 data was not thread-safe. This could lead to a use-after-free causing a potentially…
• CVE-2022-40957 — CVSS 6.5 (medium): Inconsistent data in instruction and data cache when creating wasm code could lead to a potentially exploitable crash.<br>*This bug only…
• CVE-2022-38472 — CVSS 6.5 (medium): An attacker could have abused XSLT error handling to associate attacker-controlled content with another origin which was displayed in the…
• CVE-2022-40959 — CVSS 6.5 (medium): During iframe navigation, certain pages did not have their FeaturePolicy fully initialized leading to a bypass that leaked device…
• CVE-2022-34471 — CVSS 6.5 (medium): When downloading an update for an addon, the downloaded addon update's version was not verified to match the version selected from the…
• CVE-2022-34478 — CVSS 6.5 (medium): The <code>ms-msdt</code>, <code>search</code>, and <code>search-ms</code> protocols deliver content to Microsoft applications, bypassing…
• CVE-2022-34479 — CVSS 6.5 (medium): A malicious website that could create a popup could have resized the popup to overlay the address bar with its own content, resulting in…
• CVE-2022-40956 — CVSS 6.1 (medium): When injecting an HTML base element, some requests would ignore the CSP's base-uri settings and accept the injected element's base instead…
• CVE-2022-34475 — CVSS 6.1 (medium): SVG <code>&lt;use&gt;</code> tags that referenced a same-origin document could have resulted in script execution if attacker input was…
• CVE-2022-34474 — CVSS 6.1 (medium): Even when an iframe was sandboxed with <code>allow-top-navigation-by-user-activation</code>, if it received a redirect header to an…
• CVE-2022-34473 — CVSS 6.1 (medium): The HTML Sanitizer should have sanitized the <code>href</code> attribute of SVG <code>&lt;use&gt;</code> tags; however it incorrectly did…
• CVE-2022-36314 — CVSS 5.5 (medium): When opening a Windows shortcut from the local filesystem, an attacker could supply a remote path that would lead to unexpected network…
• CVE-2022-36318 — CVSS 5.3 (medium): When visiting directory listings for `chrome://` URLs as source text, some parameters were reflected. This vulnerability affects Firefox…
• CVE-2022-34472 — CVSS 4.3 (medium): If there was a PAC URL set and the server that hosts the PAC was not reachable, OCSP requests would have been blocked, resulting in…