CVE-2024-11705: Null Pointer Dereference
First published: Tue Nov 26 2024(Updated: )
`NSC_DeriveKey` inadvertently assumed that the `phKey` parameter is always non-NULL. When it was passed as NULL, a segmentation fault (SEGV) occurred, leading to crashes. This behavior conflicted with the PKCS#11 v3.0 specification, which allows `phKey` to be NULL for certain mechanisms. This vulnerability affects Firefox < 133 and Thunderbird < 133.
Credit: security@mozilla.org security@mozilla.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| debian/firefox | 135.0-1 | |
| Thunderbird | <133 | 133 |
| Firefox | <133 | 133 |
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.
Reference Links
- https://bugzilla.mozilla.org/show_bug.cgi?id=1921768
- https://www.mozilla.org/en-US/security/advisories/mfsa2024-63/
- https://www.mozilla.org/en-US/security/advisories/mfsa2024-67/
- https://www.mozilla.org/security/advisories/mfsa2024-63/
- https://www.mozilla.org/security/advisories/mfsa2024-67/
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-11705
- https://nvd.nist.gov/vuln/detail/CVE-2024-11705
- https://launchpad.net/bugs/cve/CVE-2024-11705
- https://security-tracker.debian.org/tracker/CVE-2024-11705
- https://ubuntu.com/security/CVE-2024-11705
- https://www.mozilla.org/en-US/security/advisories/mfsa2024-63/#CVE-2024-11705
Peer vulnerabilities
(Found alongside the following vulnerabilities)
Frequently Asked Questions
What is the severity of CVE-2024-11705?
CVE-2024-11705 is classified as a security vulnerability that can lead to segmentation faults and application crashes.
How do I fix CVE-2024-11705?
To fix CVE-2024-11705, update Mozilla Thunderbird or Mozilla Firefox to version 134 or later.
What software is affected by CVE-2024-11705?
CVE-2024-11705 affects Mozilla Thunderbird versions prior to 134 and Mozilla Firefox versions prior to 134.
What kind of issue does CVE-2024-11705 cause?
CVE-2024-11705 causes segmentation faults when the phKey parameter is passed as NULL.
Does CVE-2024-11705 comply with PKCS#11 v3.0 specifications?
CVE-2024-11705 does not comply with PKCS#11 v3.0 specifications, which allow phKey to be NULL for certain mechanisms.
- agent/weakness
- agent/type
- agent/first-publish-date
- collector/nvd-api
- source/NVD
- agent/last-modified-date
- agent/severity
- collector/mitre-cve
- source/MITRE
- agent/references
- collector/usn-cve
- source/Ubuntu
- collector/nvd-cve
- agent/author
- agent/description
- agent/trending
- agent/source
- collector/security-tracker-debian
- source/Debian
- agent/event
- collector/mozilla-advisory
- source/Mozilla
- agent/software-canonical-lookup
- agent/software-canonical-lookup-request
- agent/softwarecombine
- agent/tags
- package-manager/debian
- vendor/mozilla
- canonical/thunderbird
- canonical/firefox