CVE-2017-5468: Critical severity Mozilla Firefox vulnerability
An issue with incorrect ownership model of "privateBrowsing" information exposed through developer tools. This can result in a non-exploitable crash when manually triggered during debugging. This vulnerability affects Firefox < 53.
Other sources
An issue with incorrect ownership model of privateBrowsing information exposed through developer tools. This can result in a non-exploitable crash when manually triggered during debugging.
Affected Software
Remediation
Patch Available
Event History
Peer vulnerabilities
Found alongside the following vulnerabilities.
- CVE-2017-5433
- CVE-2017-5435
- CVE-2017-5436
- CVE-2017-5461
- CVE-2017-5459
- CVE-2017-5466
- CVE-2017-5434
- CVE-2017-5432
- CVE-2017-5460
- CVE-2017-5438
- CVE-2017-5439
- CVE-2017-5440
- CVE-2017-5441
- CVE-2017-5442
- CVE-2017-5464
- CVE-2017-5443
- CVE-2017-5444
- CVE-2017-5446
- CVE-2017-5447
- CVE-2017-5465
- CVE-2017-5448
- CVE-2016-10196
- CVE-2017-5454
- CVE-2017-5455
- CVE-2017-5456
- CVE-2017-5469
- CVE-2017-5445
- CVE-2017-5449
- CVE-2017-5450
- CVE-2017-5451
- CVE-2017-5462
- CVE-2017-5463
- CVE-2017-5467
- CVE-2017-5452
- CVE-2017-5453
- CVE-2017-5458
- CVE-2017-5468
- CVE-2017-5430
- CVE-2017-5429
Frequently Asked Questions
What is the severity of CVE-2017-5468?
CVE-2017-5468 has been classified with a low severity due to its non-exploitable nature.
How do I fix CVE-2017-5468?
To fix CVE-2017-5468, upgrade your Firefox browser to version 53 or later.
Which versions of Firefox are affected by CVE-2017-5468?
CVE-2017-5468 affects all versions of Firefox prior to 53.
Can CVE-2017-5468 be exploited remotely?
CVE-2017-5468 cannot be exploited remotely as it results in a crash that requires manual triggering.
Is there a workaround for CVE-2017-5468?
There is no known workaround for CVE-2017-5468 other than updating to a fixed version.