1,441 results · Feed
-
Unscored —
Firefox used to cache the last filename used for printing a file. When generating a filename for printing, Firefox usua…
-
Unscored —
When styling and rendering an oversized `<select>` element, Firefox did not apply correct clipping which allowed an att…
-
Unscored —
Mozilla developers reported memory safety bugs present in Firefox 88. Some of these bugs showed evidence of memory corr…
-
Unscored —
Mozilla developers reported memory safety bugs present in Firefox 88 and Firefox ESR 78.11. Some of these bugs showed e…
-
Unscored —
Out of bounds write in ANGLE in Google Chrome prior to 91.0.4472.101 allowed a remote attacker to potentially perform o…
-
Unscored —
A texture upload of a Pixel Buffer Object could have confused the WebGL code to skip binding the buffer used to unpack …
-
Unscored —
Using techniques that built on the slipstream research, a malicious webpage could have scanned both an internal network…
-
Unscored —
By causing a transition on a parent node by removing a CSS rule, an invalid property for a marker could have been appli…
-
Unscored —
A malicious extension could have opened a popup window lacking an address bar. The title of the popup lacking an addres…
-
Unscored —
If an attacker is able to alter specific about:config values (for example malware running on the user's computer), the …
-
Unscored —
A malicious extension with the 'search' permission could have installed a new search engine whose favicon referenced a …
-
Unscored —
Mozilla developers and community members reported memory safety bugs present in Firefox 86 and Firefox ESR 78.8. Some o…
-
Unscored —
Mozilla developers reported memory safety bugs present in Firefox 86. Some of these bugs showed evidence of memory corr…
-
Unscored —
Mozilla developers reported memory safety bugs present in Firefox 84 and Firefox ESR 78.6. Some of these bugs showed ev…
-
Unscored —
Mozilla developers reported memory safety bugs present in Firefox 84. Some of these bugs showed evidence of memory corr…
-
Unscored —
Mozilla developers reported memory safety bugs present in Firefox 85. Some of these bugs showed evidence of memory corr…
-
Unscored —
Mozilla developers reported memory safety bugs present in Firefox 85 and Firefox ESR 78.7. Some of these bugs showed ev…
-
Unscored —
When sharing geolocation during an active WebRTC share, Firefox could have reset the webRTC sharing state in the user i…
-
Unscored —
If a user clicked into a specifically crafted PDF, the PDF reader could be confused into leaking cross-origin informati…
-
Unscored —
Using the new logical assignment operators in a JavaScript switch statement could have caused a type confusion, leading…
-
Unscored —
The browser could have been confused into transferring a pointer lock state into another tab, which could have lead to …
-
Unscored —
An ambiguous file picker design could have confused users who intended to select and upload a single file into uploadin…
-
Unscored —
The browser could have been confused into transferring a screen sharing state into another tab, which would leak uninte…
-
Unscored —
Performing garbage collection on re-declared JavaScript variables resulted in a user-after-poison, and a potentially ex…
-
Unscored —
Further techniques that built on the slipstream research combined with a malicious webpage could have exposed both an i…
-
Unscored —
Incorrect use of the '<RowCountChanged>' method could have led to a user-after-poison and a potentially exploitable cra…
-
Unscored —
If Content Security Policy blocked frame navigation, the full destination of a redirect served in the frame was reporte…
-
Unscored —
As specified in the W3C Content Security Policy draft, when creating a violation report, "User agents need to ensure th…
-
Unscored —
Context-specific code was included in a shared jump table; resulting in assertions being triggered in multithreaded was…
-
Unscored —
When processing a redirect with a conflicting Referrer-Policy, Firefox would have adopted the redirect's Referrer-Polic…
-
Unscored —
One phishing tactic on the web is to provide a link with HTTP Auth. For example 'https://www.phishingtarget.com@evil.co…
-
Unscored —
When trying to load a cross-origin resource in an audio/video context a decoding error may have resulted, and the conte…
-
Unscored —
The DOMParser API did not properly process '<noscript>' elements for escaping. This could be used as an mXSS vector to …
-
Unscored —
The developer page about:memory has a Measure function for exploring what object types the browser has allocated and th…
-
Unscored —
Use after free in WebRTC in Google Chrome prior to 88.0.4324.96 allowed a remote attacker to potentially exploit heap c…
-
Unscored —
Uninitialized Use in V8 in Google Chrome prior to 87.0.4280.88 allowed a remote attacker to obtain potentially sensitiv…
-
Unscored —CVE-2020-16012 Public exploit
Side-channel information leakage in graphics in Google Chrome prior to 87.0.4280.66 allowed a remote attacker to leak c…
-
Unscored —
Certain blit values provided by the user were not properly constrained leading to a heap buffer overflow on some video …
-
Unscored —
The lifecycle of IPC Actors allows managed actors to outlive their manager actors; and the former must ensure that they…
-
Unscored —
Certain input to the CSS Sanitizer confused it, resulting in incorrect components being removed. This could have been u…