firefox vulnerabilities (openEuler)
1,191 vulnerabilities.
firefoxopenEulerData was not properly sanitized when decoding a QUIC ACK frame; this could have led to...7.5 HighfirefoxopenEulerIf an attacker could find a way to trigger a particular code path in `SafeRefPtr`, it could have...8.1 HighfirefoxopenEulerA missing delay on when pointer lock was used could have allowed a malicious page to trick a user...5.5 MediumfirefoxopenEulerUsing a markup injection an attacker could have stolen nonce values. This could have been used to...6.1 MediumfirefoxopenEulerThe permission prompt input delay could have expired while the window is not in focus, which made...6.1 MediumfirefoxopenEuler`AppendEncodedAttributeValue(), ExtraSpaceNeededForAttrEncoding()` and `AppendEncodedCharacters()...8.4 HighfirefoxopenEulerReturn registers were overwritten which could have allowed an attacker to execute arbitrary code....8.1 HighfirefoxopenEulerPassing invalid data could have led to invalid wasm values being created, such as arbitrary...3.7 LowfirefoxopenEulerMemory safety bugs present in Firefox 122. Some of these bugs showed evidence of memory...8.1 HighfirefoxopenEulerThe incorrect object was checked for NULL in the built-in profiler, potentially leading to...6.5 MediumfirefoxopenEulerWhen opening a website using the `firefox://` protocol handler, SameSite cookies were not...8.3 HighfirefoxopenEulerThe `fetch()` API and navigation incorrectly shared the same cache, as the cache key did not...9.8 CriticalfirefoxopenEulerMemory safety bugs present in Firefox 122, Firefox ESR 115.7, and Thunderbird 115.7. Some of...8.1 HighfirefoxopenEulerSet-Cookie response headers were being incorrectly honored in multipart HTTP responses. If an...6.1 MediumfirefoxopenEulerA malicious website could have used a combination of exiting fullscreen mode and ...6.1 MediumfirefoxopenEulerIf a website set a large custom cursor, portions of the cursor could have overlapped with the...6.1 MediumfirefoxopenEulerA website could have obscured the fullscreen notification by using a dropdown select input...4.3 MediumfirefoxopenEulerThrough a series of API calls and redirects, an attacker-controlled alert dialog could have been...6.5 MediumfirefoxopenEulerSome WASM source files could have caused a crash when loaded in devtools. This vulnerability...6.5 MediumfirefoxopenEulerA compromised content process could have updated the document URI. This could have allowed an...4.3 MediumfirefoxopenEulerThe WebAudio `OscillatorNode` object was susceptible to a stack buffer overflow. This could have...8.8 HighfirefoxopenEulerIn some circumstances, JIT compiled code could have dereferenced a wild pointer value. This could...7.5 HighfirefoxopenEulerAn unchecked return value in TLS handshake code could have caused a potentially exploitable crash...7.5 HighfirefoxopenEulerMemory safety bugs present in Firefox 121, Firefox ESR 115.6, and Thunderbird 115.6. Some of...8.8 HighfirefoxopenEulerIn specific HSTS configurations an attacker could have bypassed HSTS on a subdomain. This...6.5 MediumfirefoxopenEulerA malicious devtools extension could have been used to escalate privileges. This vulnerability...8.8 HighfirefoxopenEulerA phishing site could have repurposed an `about:` dialog to show phishing content with an...4.3 MediumfirefoxopenEulerWhen a parent page loaded a child in an iframe with `unsafe-inline`, the parent Content Security...6.5 MediumfirefoxopenEulerIt was possible for certain browser prompts and dialogs to be activated or dismissed...4.3 MediumfirefoxopenEulerAn out of bounds write in ANGLE could have allowed an attacker to corrupt memory leading to a...6.5 MediumfirefoxopenEulerheap buffer overflow in libaom9.0 CriticalfirefoxopenEulerSQLite SQLite3 make alltest sqlite3session.c sessionReadRecord heap-based overflow5.5 MediumfirefoxopenEulerMemory safety bugs present in Firefox 120. Some of these bugs showed evidence of memory...8.8 HighfirefoxopenEulerBrowser tab titles were being leaked by GNOME to system logs. This could potentially expose the...6.5 MediumfirefoxopenEulerUnder certain conditions, Firefox did not display a warning when a user attempted to navigate to...4.3 MediumfirefoxopenEulerA `` element could have been manipulated to paint content outside of a sandboxed iframe. This...6.5 MediumfirefoxopenEulerThe timing of a button click causing a popup to disappear was approximately the same length as...6.1 MediumfirefoxopenEulerTypedArrays can be fallible and lacked proper exception handling. This could lead to abuse in...8.8 HighfirefoxopenEuler`EncryptingOutputStream` was susceptible to exposing uninitialized data. This issue could only...6.5 MediumfirefoxopenEulerMultiple NSS NIST curves were susceptible to a side-channel attack known as "Minerva". This...4.3 MediumfirefoxopenEulerMemory safety bugs present in Firefox 120, Firefox ESR 115.5, and Thunderbird 115.5. Some of...8.8 HighfirefoxopenEulerThe `ShutdownObserver()` was susceptible to potentially undefined behavior due to its reliance on...8.8 HighfirefoxopenEulerA use-after-free was identified in the `nsDNSService::Init`. This issue appears to manifest...8.8 HighfirefoxopenEulerThe `nsWindow::PickerOpen(void)` method was susceptible to a heap buffer overflow when running in...8.8 HighfirefoxopenEulerThe `VideoBridge` allowed any content process to use textures produced by remote decoders. This...6.5 MediumfirefoxopenEulerA use-after-free condition affected TLS socket creation when under memory pressure. This...8.8 HighfirefoxopenEulerFirefox was susceptible to a heap buffer overflow in `nsTextFragment` due to insufficient OOM...8.8 HighfirefoxopenEulerWhen resolving a symlink, a race may occur where the buffer passed to `readlink` may actually be...5.3 MediumfirefoxopenEulerThe WebGL `DrawElementsInstanced` method was susceptible to a heap buffer overflow when used on...8.8 HighfirefoxopenEulerMemory safety bugs present in Firefox 119. Some of these bugs showed evidence of memory...8.8 High- Show moreLoading…