high
8.8
CWE
119
Advisory Published
Updated

CVE-2016-1953: Buffer Overflow

First published: Sun Mar 13 2016(Updated: )

Multiple unspecified vulnerabilities in the browser engine in Mozilla Firefox before 45.0 allow remote attackers to cause a denial of service (memory corruption and application crash) or possibly execute arbitrary code via vectors related to js/src/jit/arm/Assembler-arm.cpp, and unknown other vectors.

Credit: security@mozilla.org security@mozilla.org

Affected SoftwareAffected VersionHow to fix
Firefox<=44.0.2
Firefox=38.0
Firefox=38.0.1
Firefox=38.0.5
Firefox=38.1.0
Firefox=38.1.1
Firefox=38.2.0
Firefox=38.2.1
Firefox=38.3.0
Firefox=38.4.0
Firefox=38.5.0
Firefox=38.5.1
Firefox=38.6.0
Firefox=38.6.1
Thunderbird<=38.6.0
SUSE Package Hub for SUSE Linux Enterprise=12
SUSE Linux=42.1
SUSE Linux=13.1
SUSE Linux=13.2
Firefox ESR=38.0
Firefox ESR=38.0.1
Firefox ESR=38.0.5
Firefox ESR=38.1.0
Firefox ESR=38.1.1
Firefox ESR=38.2.0
Firefox ESR=38.2.1
Firefox ESR=38.3.0
Firefox ESR=38.4.0
Firefox ESR=38.5.0
Firefox ESR=38.5.1
Firefox ESR=38.6.0
Firefox ESR=38.6.1

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Read MoreStart Free Trial

Reference Links

Frequently Asked Questions

  • What is the severity of CVE-2016-1953?

    CVE-2016-1953 has been classified as a high-severity vulnerability due to its potential to cause denial of service and possible remote code execution.

  • How do I fix CVE-2016-1953?

    To fix CVE-2016-1953, update Mozilla Firefox to version 45.0 or later.

  • Which versions of Firefox are affected by CVE-2016-1953?

    CVE-2016-1953 affects Firefox versions up to and including 44.0.2 and Firefox ESR versions up to and including 38.6.1.

  • Can CVE-2016-1953 cause data loss?

    While CVE-2016-1953 primarily causes application crashes, arbitrary code execution could potentially lead to data loss under certain circumstances.

  • Is there any workaround for CVE-2016-1953?

    There are no known workarounds for CVE-2016-1953, and the only reliable solution is to upgrade to a secure version.

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2025 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203