9.8 High
CVSS3
Attack Vector
NETWORK
Attack Complexity
LOW
Privileges Required
NONE
User Interaction
NONE
Scope
UNCHANGED
Confidentiality Impact
HIGH
Integrity Impact
HIGH
Availability Impact
HIGH
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
10 High
CVSS2
Access Vector
NETWORK
Access Complexity
LOW
Authentication
NONE
Confidentiality Impact
COMPLETE
Integrity Impact
COMPLETE
Availability Impact
COMPLETE
AV:N/AC:L/Au:N/C:C/I:C/A:C
0.924 High
EPSS
Percentile
99.0%
Severity: Critical
Date : 2017-03-10
CVE-ID : CVE-2017-5398 CVE-2017-5399 CVE-2017-5400 CVE-2017-5401
CVE-2017-5402 CVE-2017-5403 CVE-2017-5404 CVE-2017-5405
CVE-2017-5406 CVE-2017-5407 CVE-2017-5408 CVE-2017-5410
CVE-2017-5412 CVE-2017-5413 CVE-2017-5414 CVE-2017-5415
CVE-2017-5416 CVE-2017-5417 CVE-2017-5418 CVE-2017-5419
CVE-2017-5420 CVE-2017-5421 CVE-2017-5422 CVE-2017-5426
CVE-2017-5427
Package : firefox
Type : multiple issues
Remote : Yes
Link : https://security.archlinux.org/AVG-194
The package firefox before version 52.0-1 is vulnerable to multiple
issues including arbitrary code execution, access restriction bypass,
denial of service, information disclosure and content spoofing.
Upgrade to 52.0-1.
The problems have been fixed upstream in version 52.0.
None.
Several memory safety bugs, some of them leading to memory corruption
issues have been found in Firefox < 52 and Thunderbird < 45.8.
Several memory safety bugs, some of them leading to memory corruption
issues have been found in Firefox < 52.
JIT-spray targeting asm.js combined with a heap spray allows for a
bypass of ASLR and DEP protections leading to potential memory
corruption attacks.
A crash triggerable by web content in which an ErrorResult references
unassigned memory due to a logic error.
A use-after-free can occur when events are fired for a FontFace object
after the object has been already been destroyed while working with
fonts.
When adding a range to an object in the DOM, it is possible to use
addRange to add the range to an incorrect root object. This triggers a
use-after-free, resulting in a potentially exploitable crash.
A use-after-free error can occur when manipulating ranges in selections
with one node inside a native anonymous tree and one node outside of
it. This results in a potentially exploitable crash.
Certain response codes in FTP connections can result in the use of
uninitialized values for ports in FTP operations.
A segmentation fault can occur in the Skia graphics library during some
canvas operations due to issues with mask/clip intersection and empty
masks.
Using SVG filters that don’t use the fixed point math implementation on
a target iframe, a malicious page can extract pixel values from a
targeted user. This can be used to extract history information and read
text values across domains. This violates same-origin policy and leads
to information disclosure.
Video files loaded video captions cross-origin without checking for the
presence of CORS headers permitting such cross-origin use, leading to
potential information disclosure for video captions.
Memory corruption resulting in a potentially exploitable crash during
garbage collection of JavaScript due errors in how incremental sweeping
is managed for memory cleanup.
A buffer overflow read during SVG filter color value operations,
resulting in data exposure.
A segmentation fault can occur during some bidirectional layout
operations.
The file picker dialog can choose and display the wrong local default
directory when instantiated. On some operating systems, this can lead
to information disclosure, such as the operating system or the local
account name.
An attack can use a blob URL and script to spoof an arbitrary address
bar URL prefaced by blob: as the protocol, leading to user confusion
and further spoofing attacks.
In certain circumstances a networking event listener can be prematurely
released. This appears to result in a null dereference in practice.
When dragging content from the primary browser pane to the address bar
on a malicious site, it is possible to change the address bar so that
the displayed location following navigation does not match the URL of
the newly loaded page. This allows for spoofing attacks.
An out of bounds read error occurs when parsing some HTTP digest
authorization responses, resulting in information leakage through the
reading of random memory containing matches to specifically set
patterns.
If a malicious site repeatedly triggers a modal authentication prompt,
eventually the browser UI will become non-responsive, requiring
shutdown through the operating system. This is a denial of service
(DOS) attack.
A javascript: url loaded by a malicious page can obfuscate its location
by blanking the URL displayed in the address bar, allowing for an
attacker to spoof an existing page without the malicious page’s address
being displayed correctly.
A malicious site could spoof the contents of the print preview window
if popup windows are enabled, resulting in user confusion of what site
is currently loaded.
If a malicious site uses the view-source: protocol in a series within a
single hyperlink, it can trigger a non-exploitable browser crash when
the hyperlink is selected. This was fixed by no longer making view-
source: linkable.
On Linux, if the secure computing mode BPF (seccomp-bpf) filter is
running when the Gecko Media Plugin sandbox is started, the sandbox
fails to be applied and items that would run within the sandbox are run
protected only by the running filter which is typically weak compared
to the sandbox.
A non-existent chrome.manifest file will attempt to be loaded during
startup from the primary installation directory. If a malicious user
with local access puts chrome.manifest and other referenced files in
this directory, they will be loaded and activated during startup. This
could result in malicious software being added without consent or
modification of referenced installed files.
A remote attacker can bypass access restrictions, spoof content, access
sensitive information, cause a denial of service or execute arbitrary
code on the affected host.
https://www.mozilla.org/en-US/security/advisories/mfsa2017-05/
https://www.mozilla.org/en-US/security/advisories/mfsa2017-07/#CVE-2017-5398
https://bugzilla.mozilla.org/buglist.cgi?bug_id=1332550%2C1332597%2C1338383%2C1321612%2C1322971%2C1333568%2C1333887%2C1335450%2C1325052%2C1324379%2C1336510
https://www.mozilla.org/en-US/security/advisories/mfsa2017-05/#CVE-2017-5399
https://bugzilla.mozilla.org/buglist.cgi?bug_id=1332569%2C1315248%2C1261335%2C1321038%2C1331771%2C1339566%2C1339591%2C1240893%2C1341905%2C1323241%2C1336467%2C1270288%2C1295299%2C1296024%2C1304201%2C1306142%2C1307557%2C1308036%2C1334246%2C1334290%2C1317085%2C1339116%2C1324000%2C1323150%2C1332501%2C1320894%2C1333752%2C1303713%2C1321566%2C1264053%2C1343513
https://www.mozilla.org/en-US/security/advisories/mfsa2017-07/#CVE-2017-5400
https://bugzilla.mozilla.org/show_bug.cgi?id=1334933
https://www.mozilla.org/en-US/security/advisories/mfsa2017-07/#CVE-2017-5401
https://bugzilla.mozilla.org/show_bug.cgi?id=1328861
https://www.mozilla.org/en-US/security/advisories/mfsa2017-07/#CVE-2017-5402
https://bugzilla.mozilla.org/show_bug.cgi?id=1334876
https://www.mozilla.org/en-US/security/advisories/mfsa2017-05/#CVE-2017-5403
https://bugzilla.mozilla.org/show_bug.cgi?id=1340186
https://www.mozilla.org/en-US/security/advisories/mfsa2017-07/#CVE-2017-5404
https://bugzilla.mozilla.org/show_bug.cgi?id=1340138
https://www.mozilla.org/en-US/security/advisories/mfsa2017-07/#CVE-2017-5405
https://bugzilla.mozilla.org/show_bug.cgi?id=1336699
https://www.mozilla.org/en-US/security/advisories/mfsa2017-05/#CVE-2017-5406
https://bugzilla.mozilla.org/show_bug.cgi?id=1306890
https://www.mozilla.org/en-US/security/advisories/mfsa2017-05/#CVE-2017-5407
https://bugzilla.mozilla.org/show_bug.cgi?id=1336622
https://www.mozilla.org/en-US/security/advisories/mfsa2017-07/#CVE-2017-5408
https://bugzilla.mozilla.org/show_bug.cgi?id=1313711
https://www.mozilla.org/en-US/security/advisories/mfsa2017-07/#CVE-2017-5410
https://bugzilla.mozilla.org/show_bug.cgi?id=1330687
https://www.mozilla.org/en-US/security/advisories/mfsa2017-05/#CVE-2017-5412
https://bugzilla.mozilla.org/show_bug.cgi?id=1328323
https://www.mozilla.org/en-US/security/advisories/mfsa2017-05/#CVE-2017-5413
https://bugzilla.mozilla.org/show_bug.cgi?id=1337504
https://www.mozilla.org/en-US/security/advisories/mfsa2017-05/#CVE-2017-5414
https://bugzilla.mozilla.org/show_bug.cgi?id=1319370
https://www.mozilla.org/en-US/security/advisories/mfsa2017-05/#CVE-2017-5415
https://bugzilla.mozilla.org/show_bug.cgi?id=1321719
https://www.mozilla.org/en-US/security/advisories/mfsa2017-05/#CVE-2017-5416
https://bugzilla.mozilla.org/show_bug.cgi?id=1328121
https://www.mozilla.org/en-US/security/advisories/mfsa2017-05/#CVE-2017-5417
https://bugzilla.mozilla.org/show_bug.cgi?id=791597
https://www.mozilla.org/en-US/security/advisories/mfsa2017-05/#CVE-2017-5418
https://bugzilla.mozilla.org/show_bug.cgi?id=1338876
https://www.mozilla.org/en-US/security/advisories/mfsa2017-05/#CVE-2017-5419
https://bugzilla.mozilla.org/show_bug.cgi?id=1312243
https://www.mozilla.org/en-US/security/advisories/mfsa2017-05/#CVE-2017-5420
https://bugzilla.mozilla.org/show_bug.cgi?id=1284395
https://www.mozilla.org/en-US/security/advisories/mfsa2017-05/#CVE-2017-5421
https://bugzilla.mozilla.org/show_bug.cgi?id=1301876
https://www.mozilla.org/en-US/security/advisories/mfsa2017-05/#CVE-2017-5422
https://bugzilla.mozilla.org/show_bug.cgi?id=1295002
https://www.mozilla.org/en-US/security/advisories/mfsa2017-05/#CVE-2017-5426
https://bugzilla.mozilla.org/show_bug.cgi?id=1257361
https://www.mozilla.org/en-US/security/advisories/mfsa2017-05/#CVE-2017-5427
https://bugzilla.mozilla.org/show_bug.cgi?id=1295542
https://security.archlinux.org/CVE-2017-5398
https://security.archlinux.org/CVE-2017-5399
https://security.archlinux.org/CVE-2017-5400
https://security.archlinux.org/CVE-2017-5401
https://security.archlinux.org/CVE-2017-5402
https://security.archlinux.org/CVE-2017-5403
https://security.archlinux.org/CVE-2017-5404
https://security.archlinux.org/CVE-2017-5405
https://security.archlinux.org/CVE-2017-5406
https://security.archlinux.org/CVE-2017-5407
https://security.archlinux.org/CVE-2017-5408
https://security.archlinux.org/CVE-2017-5410
https://security.archlinux.org/CVE-2017-5412
https://security.archlinux.org/CVE-2017-5413
https://security.archlinux.org/CVE-2017-5414
https://security.archlinux.org/CVE-2017-5415
https://security.archlinux.org/CVE-2017-5416
https://security.archlinux.org/CVE-2017-5417
https://security.archlinux.org/CVE-2017-5418
https://security.archlinux.org/CVE-2017-5419
https://security.archlinux.org/CVE-2017-5420
https://security.archlinux.org/CVE-2017-5421
https://security.archlinux.org/CVE-2017-5422
https://security.archlinux.org/CVE-2017-5426
https://security.archlinux.org/CVE-2017-5427
bugzilla.mozilla.org/buglist.cgi?bug_id=1332550%2C1332597%2C1338383%2C1321612%2C1322971%2C1333568%2C1333887%2C1335450%2C1325052%2C1324379%2C1336510
bugzilla.mozilla.org/buglist.cgi?bug_id=1332569%2C1315248%2C1261335%2C1321038%2C1331771%2C1339566%2C1339591%2C1240893%2C1341905%2C1323241%2C1336467%2C1270288%2C1295299%2C1296024%2C1304201%2C1306142%2C1307557%2C1308036%2C1334246%2C1334290%2C1317085%2C1339116%2C1324000%2C1323150%2C1332501%2C1320894%2C1333752%2C1303713%2C1321566%2C1264053%2C1343513
bugzilla.mozilla.org/show_bug.cgi?id=1257361
bugzilla.mozilla.org/show_bug.cgi?id=1284395
bugzilla.mozilla.org/show_bug.cgi?id=1295002
bugzilla.mozilla.org/show_bug.cgi?id=1295542
bugzilla.mozilla.org/show_bug.cgi?id=1301876
bugzilla.mozilla.org/show_bug.cgi?id=1306890
bugzilla.mozilla.org/show_bug.cgi?id=1312243
bugzilla.mozilla.org/show_bug.cgi?id=1313711
bugzilla.mozilla.org/show_bug.cgi?id=1319370
bugzilla.mozilla.org/show_bug.cgi?id=1321719
bugzilla.mozilla.org/show_bug.cgi?id=1328121
bugzilla.mozilla.org/show_bug.cgi?id=1328323
bugzilla.mozilla.org/show_bug.cgi?id=1328861
bugzilla.mozilla.org/show_bug.cgi?id=1330687
bugzilla.mozilla.org/show_bug.cgi?id=1334876
bugzilla.mozilla.org/show_bug.cgi?id=1334933
bugzilla.mozilla.org/show_bug.cgi?id=1336622
bugzilla.mozilla.org/show_bug.cgi?id=1336699
bugzilla.mozilla.org/show_bug.cgi?id=1337504
bugzilla.mozilla.org/show_bug.cgi?id=1338876
bugzilla.mozilla.org/show_bug.cgi?id=1340138
bugzilla.mozilla.org/show_bug.cgi?id=1340186
bugzilla.mozilla.org/show_bug.cgi?id=791597
security.archlinux.org/AVG-194
security.archlinux.org/CVE-2017-5398
security.archlinux.org/CVE-2017-5399
security.archlinux.org/CVE-2017-5400
security.archlinux.org/CVE-2017-5401
security.archlinux.org/CVE-2017-5402
security.archlinux.org/CVE-2017-5403
security.archlinux.org/CVE-2017-5404
security.archlinux.org/CVE-2017-5405
security.archlinux.org/CVE-2017-5406
security.archlinux.org/CVE-2017-5407
security.archlinux.org/CVE-2017-5408
security.archlinux.org/CVE-2017-5410
security.archlinux.org/CVE-2017-5412
security.archlinux.org/CVE-2017-5413
security.archlinux.org/CVE-2017-5414
security.archlinux.org/CVE-2017-5415
security.archlinux.org/CVE-2017-5416
security.archlinux.org/CVE-2017-5417
security.archlinux.org/CVE-2017-5418
security.archlinux.org/CVE-2017-5419
security.archlinux.org/CVE-2017-5420
security.archlinux.org/CVE-2017-5421
security.archlinux.org/CVE-2017-5422
security.archlinux.org/CVE-2017-5426
security.archlinux.org/CVE-2017-5427
www.mozilla.org/en-US/security/advisories/mfsa2017-05/
www.mozilla.org/en-US/security/advisories/mfsa2017-05/#CVE-2017-5399
www.mozilla.org/en-US/security/advisories/mfsa2017-05/#CVE-2017-5403
www.mozilla.org/en-US/security/advisories/mfsa2017-05/#CVE-2017-5406
www.mozilla.org/en-US/security/advisories/mfsa2017-05/#CVE-2017-5407
www.mozilla.org/en-US/security/advisories/mfsa2017-05/#CVE-2017-5412
www.mozilla.org/en-US/security/advisories/mfsa2017-05/#CVE-2017-5413
www.mozilla.org/en-US/security/advisories/mfsa2017-05/#CVE-2017-5414
www.mozilla.org/en-US/security/advisories/mfsa2017-05/#CVE-2017-5415
www.mozilla.org/en-US/security/advisories/mfsa2017-05/#CVE-2017-5416
www.mozilla.org/en-US/security/advisories/mfsa2017-05/#CVE-2017-5417
www.mozilla.org/en-US/security/advisories/mfsa2017-05/#CVE-2017-5418
www.mozilla.org/en-US/security/advisories/mfsa2017-05/#CVE-2017-5419
www.mozilla.org/en-US/security/advisories/mfsa2017-05/#CVE-2017-5420
www.mozilla.org/en-US/security/advisories/mfsa2017-05/#CVE-2017-5421
www.mozilla.org/en-US/security/advisories/mfsa2017-05/#CVE-2017-5422
www.mozilla.org/en-US/security/advisories/mfsa2017-05/#CVE-2017-5426
www.mozilla.org/en-US/security/advisories/mfsa2017-05/#CVE-2017-5427
www.mozilla.org/en-US/security/advisories/mfsa2017-07/#CVE-2017-5398
www.mozilla.org/en-US/security/advisories/mfsa2017-07/#CVE-2017-5400
www.mozilla.org/en-US/security/advisories/mfsa2017-07/#CVE-2017-5401
www.mozilla.org/en-US/security/advisories/mfsa2017-07/#CVE-2017-5402
www.mozilla.org/en-US/security/advisories/mfsa2017-07/#CVE-2017-5404
www.mozilla.org/en-US/security/advisories/mfsa2017-07/#CVE-2017-5405
www.mozilla.org/en-US/security/advisories/mfsa2017-07/#CVE-2017-5408
www.mozilla.org/en-US/security/advisories/mfsa2017-07/#CVE-2017-5410
9.8 High
CVSS3
Attack Vector
NETWORK
Attack Complexity
LOW
Privileges Required
NONE
User Interaction
NONE
Scope
UNCHANGED
Confidentiality Impact
HIGH
Integrity Impact
HIGH
Availability Impact
HIGH
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
10 High
CVSS2
Access Vector
NETWORK
Access Complexity
LOW
Authentication
NONE
Confidentiality Impact
COMPLETE
Integrity Impact
COMPLETE
Availability Impact
COMPLETE
AV:N/AC:L/Au:N/C:C/I:C/A:C
0.924 High
EPSS
Percentile
99.0%