Skip to content
OpenAdvisories
Unscored USN-3260-1 36 CVEs

firefox vulnerabilities

Published Apr 21, 2017 · Updated Oct 27, 2026

Summary

Multiple security issues were discovered in Firefox. If a user were
tricked in to opening a specially crafted website, an attacker could
potentially exploit these to read uninitialized memory, obtain sensitive
information, spoof the addressbar contents or other UI elements, escape
the sandbox to read local files, conduct cross-site scripting (XSS)
attacks, cause a denial of service via application crash, or execute
arbitrary code. (CVE-2017-5429, CVE-2017-5430, CVE-2017-5432,
CVE-2017-5433, CVE-2017-5434, CVE-2017-5435, CVE-2017-5436, CVE-2017-5437,
CVE-2017-5438, CVE-2017-5439, CVE-2017-5440, CVE-2017-5441, CVE-2017-5442,
CVE-2017-5443, CVE-2017-5444, CVE-2017-5445, CVE-2017-5446, CVE-2017-5447,
CVE-2017-5448, CVE-2017-5449, CVE-2017-5451, CVE-2017-5453, CVE-2017-5454,
CVE-2017-5455, CVE-2017-5456, CVE-2017-5458, CVE-2017-5459, CVE-2017-5460,
CVE-2017-5461, CVE-2017-5464, CVE-2017-5465, CVE-2017-5466, CVE-2017-5467,
CVE-2017-5468, CVE-2017-5469)

A flaw was discovered in the DRBG number generation in NSS. If an
attacker were able to perform a machine-in-the-middle attack, this flaw
could potentially be exploited to view sensitive information.
(CVE-2017-5462)

Fixed packages 2

ReleasePackageFixed in
Ubuntu · 14.04 LTS 14.04:LTS firefox 53.0+build6-0ubuntu0.14.04.1
Ubuntu · 16.04 LTS 16.04:LTS firefox 53.0+build6-0ubuntu0.16.04.1

Vulnerabilities 36

References

  • report
    https://ubuntu.com/security/CVE-2017-5429
  • report
    https://ubuntu.com/security/CVE-2017-5430
  • report
    https://ubuntu.com/security/CVE-2017-5432
  • report
    https://ubuntu.com/security/CVE-2017-5433
  • report
    https://ubuntu.com/security/CVE-2017-5434
  • report
    https://ubuntu.com/security/CVE-2017-5435
  • report
    https://ubuntu.com/security/CVE-2017-5436
  • report
    https://ubuntu.com/security/CVE-2017-5437
  • report
    https://ubuntu.com/security/CVE-2017-5438
  • report
    https://ubuntu.com/security/CVE-2017-5439
  • report
    https://ubuntu.com/security/CVE-2017-5440
  • report
    https://ubuntu.com/security/CVE-2017-5441
  • report
    https://ubuntu.com/security/CVE-2017-5442
  • report
    https://ubuntu.com/security/CVE-2017-5443
  • report
    https://ubuntu.com/security/CVE-2017-5444
  • report
    https://ubuntu.com/security/CVE-2017-5445
  • report
    https://ubuntu.com/security/CVE-2017-5446
  • report
    https://ubuntu.com/security/CVE-2017-5447
  • report
    https://ubuntu.com/security/CVE-2017-5448
  • report
    https://ubuntu.com/security/CVE-2017-5449
  • report
    https://ubuntu.com/security/CVE-2017-5451
  • report
    https://ubuntu.com/security/CVE-2017-5453
  • report
    https://ubuntu.com/security/CVE-2017-5454
  • report
    https://ubuntu.com/security/CVE-2017-5455
  • report
    https://ubuntu.com/security/CVE-2017-5456
  • report
    https://ubuntu.com/security/CVE-2017-5458
  • report
    https://ubuntu.com/security/CVE-2017-5459
  • report
    https://ubuntu.com/security/CVE-2017-5460
  • report
    https://ubuntu.com/security/CVE-2017-5461
  • report
    https://ubuntu.com/security/CVE-2017-5462
  • report
    https://ubuntu.com/security/CVE-2017-5464
  • report
    https://ubuntu.com/security/CVE-2017-5465
  • report
    https://ubuntu.com/security/CVE-2017-5466
  • report
    https://ubuntu.com/security/CVE-2017-5467
  • report
    https://ubuntu.com/security/CVE-2017-5468
  • report
    https://ubuntu.com/security/CVE-2017-5469