CVE-2018-18509: A flaw during verification of certain S/MIME signatures causes emails to be shown in Thunderbird as having a valid digital signature, even…
Noroxi assessment
Priority: Monitor (action score 22/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 1.6% (FIRST EPSS); higher than 77.2% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: thunderbird (Debian:12) 1:60.5.1-1; thunderbird (Debian:8) 1:60.5.1-1~deb8u1; thunderbird (Debian:9) 1:60.5.1-1~deb9u1.
Low priority for now. Upgrade to thunderbird (Debian:12) 1:60.5.1-1; thunderbird (Debian:8) 1:60.5.1-1~deb8u1; thunderbird (Debian:9) 1:60.5.1-1~deb9u1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
A flaw during verification of certain S/MIME signatures causes emails to be shown in Thunderbird as having a valid digital signature, even if the shown message contents aren't covered by the signature. The flaw allows an attacker to reuse a valid S/MIME signature to craft an email message with arbitrary content. This vulnerability affects Thunderbird < 60.5.1.
- Published
- Apr 26, 2019
- Updated
- Jun 16, 2026
- EPSS
- 1.6% · 77th percentile
- CWE
- CWE-347
Report tools
Action score
22
Low priority for now.
- CVSS
- 21 / 40 · 5.3 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 1.6%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| mozilla | thunderbird | cpe:2.3:a:mozilla:thunderbird |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (mozilla). Independent of NVD's CPE analysis and usually ahead of it.
Mozilla Thunderbird
- unspecified and later · before 60.5.1affected
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- mozilla thunderbirdbefore 60.5.1
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | thunderbird | before 1:60.5.1-1 | 1:60.5.1-1 |
| Debian:8 | thunderbird | before 1:60.5.1-1~deb8u1 | 1:60.5.1-1~deb8u1 |
| Debian:9 | thunderbird | before 1:60.5.1-1~deb9u1 | 1:60.5.1-1~deb9u1 |
| openSUSE:Leap 15.0 | MozillaThunderbird | before 60.6.1-lp150.3.37.1 | 60.6.1-lp150.3.37.1 |
| Red Hat:enterprise_linux:6::client | thunderbird | before 0:60.6.1-1.el6_10 | 0:60.6.1-1.el6_10 |
| Red Hat:enterprise_linux:6::client | thunderbird-debuginfo | before 0:60.6.1-1.el6_10 | 0:60.6.1-1.el6_10 |
| Red Hat:enterprise_linux:7::client | thunderbird | before 0:60.6.1-1.el7_6 | 0:60.6.1-1.el7_6 |
| Red Hat:enterprise_linux:7::client | thunderbird-debuginfo | before 0:60.6.1-1.el7_6 | 0:60.6.1-1.el7_6 |
| Red Hat:enterprise_linux:8::appstream | thunderbird | before 0:60.6.1-1.el8 | 0:60.6.1-1.el8 |
| Red Hat:enterprise_linux:8::appstream | thunderbird-debuginfo | before 0:60.6.1-1.el8 | 0:60.6.1-1.el8 |
| Red Hat:enterprise_linux:8::appstream | thunderbird-debugsource | before 0:60.6.1-1.el8 | 0:60.6.1-1.el8 |
| SUSE:Linux Enterprise Workstation Extension 15 | MozillaThunderbird | before 60.5.1-3.24.1 | 60.5.1-3.24.1 |
| SUSE:Linux Enterprise Workstation Extension 15 | MozillaThunderbird | before 60.6.1-3.28.1 | 60.6.1-3.28.1 |
| SUSE:Package Hub 12 | MozillaThunderbird | before 60.5.1-79.1 | 60.5.1-79.1 |
Same product
mozilla: all recordsOther highest-scoring records for the same primary product.
- CVE-2019-11705A flaw in Thunderbird's implementation of iCal causes a stack buffer overflow in icalrecur_add_bydayrules when processing certain email…42Plan
- CVE-2019-11704A flaw in Thunderbird's implementation of iCal causes a heap buffer overflow in icalmemory_strdup_and_dequote when processing certain email…42Plan
- CVE-2019-11703A flaw in Thunderbird's implementation of iCal causes a heap buffer overflow in parser_get_next_char when processing certain email…42Plan
Published before and after this one in the same product
- ← EarlierCVE-2018-12373Oct 18, 2018 · dDecrypted S/MIME parts hidden with CSS or the plaintext HTML tag can leak plaintext when included in a HTML reply/forward.27Monitor
- ← EarlierCVE-2018-12374Oct 18, 2018 · Plaintext of decrypted emails can leak through by user submitting an embedded form by pressing enter key within a text input field.18Monitor
- Later →CVE-2018-18512Apr 26, 2019 · A use-after-free vulnerability can occur while playing a sound notification in Thunderbird.39Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| debian:thunderbird | 1:60.5.1-1 · Debian:12 | Package registry (OSV) |
| opensuse:MozillaThunderbird | 60.6.1-lp150.3.37.1 · openSUSE:Leap 15.0 | Package registry (OSV) |
| red hat:thunderbird | 0:60.6.1-1.el6_10 · Red Hat:enterprise_linux:6::client | Package registry (OSV) |
| red hat:thunderbird-debuginfo | 0:60.6.1-1.el6_10 · Red Hat:enterprise_linux:6::client | Package registry (OSV) |
| red hat:thunderbird-debugsource | 0:60.6.1-1.el8 · Red Hat:enterprise_linux:8::appstream | Package registry (OSV) |
| suse:MozillaThunderbird | 60.5.1-3.24.1 · SUSE:Linux Enterprise Workstation Extension 15 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- low · data or configuration can be modified
- Availability
- none
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- Low
- Availability impact
- None
Weakness class (CWE)
CWE-347 · Improper Verification of Cryptographic SignatureCVSS vector
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
nvd-primary
Root cause
The verifier takes the algorithm to verify with from the token’s own header. Untrusted data ends up deciding its own verification rule.
The bug in code
The whole CWE-347 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
const claims = jwt.verify(token, publicKey);Fixed
const claims = jwt.verify(token, publicKey, {
algorithms: ["RS256"],
issuer: "https://id.example.com",
audience: "portal",
});Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- github.com/RUB-NDS/Johnny-You-Are-Fired/blob/master/paper/johnny-fired.pdf
- bugzilla.mozilla.org/show_bug.cgi?id=1507218
- lists.opensuse.org/opensuse-security-announce/2019-04/msg00043.html
- seclists.org/fulldisclosure/2019/Apr/38
- www.openwall.com/lists/oss-security/2019/04/30/4
- access.redhat.com/errata/RHSA-2019:1144
- www.mozilla.org/security/advisories/mfsa2019-06/
Vendor advisories and official records. Exploit/PoC links are deliberately left out.