CVE-2018-12385: Input Validation
A potentially exploitable crash in TransportSecurityInfo used for SSL can be triggered by data stored in the local cache in the user profile directory. This issue is only exploitable in combination with another vulnerability allowing an attacker to write data into the local cache or from locally installed malware. This issue also triggers a non-exploitable startup crash for users switching between the Nightly and Release versions of Firefox if the same profile is used.
External Reference:
https://www.mozilla.org/en-US/security/advisories/mfsa2018-23/#CVE-2018-12385
Other sources
A potentially exploitable crash in TransportSecurityInfo used for SSL can be triggered by data stored in the local cache in the user profile directory. This issue is only exploitable in combination with another vulnerability allowing an attacker to write data into the local cache or from locally installed malware. This issue also triggers a non-exploitable startup crash for users switching between the Nightly and Release versions of Firefox if the same profile is used.
— Mozilla
Affected Software
Event History
Parent advisories
This vulnerability appears in the following advisories.
Peer vulnerabilities
Found alongside the following vulnerabilities.
Frequently Asked Questions
What is the severity of CVE-2018-12385?
CVE-2018-12385 has been classified as having moderate severity due to the potential for crash exploitation under specific conditions.
How do I fix CVE-2018-12385?
To address CVE-2018-12385, users should update to the latest version of affected software such as Thunderbird, Firefox, or their respective ESR versions.
What versions are affected by CVE-2018-12385?
CVE-2018-12385 impacts Mozilla Thunderbird and Firefox up to version 60.2.1, as well as Firefox ESR versions up to 60.2.1.
Can CVE-2018-12385 be exploited remotely?
CVE-2018-12385 is not directly exploitable remotely and typically requires an attacker to leverage another vulnerability to write data into local cache.
Is there a public exploit available for CVE-2018-12385?
As of now, there are no known public exploits specifically targeting CVE-2018-12385.