A critical bug in Mozilla's Network Security Services (NSS) cryptographic library, tracked as CVE-2021-43527 and nicknamed BigSig, was discovered by Google's Project Zero researcher Tavis Ormandy. The flaw is triggered during digital signature verification and can lead to remote code execution.
Firefox escapes this particular attack vector, but NSS is embedded in far more than browsers.
Why BigSig is different
Most software vendors lean on third-party open source crypto such as OpenSSL, or on encryption libraries shipped with operating systems—Microsoft's Secure Channel (Schannel) or Apple's Secure Transport. Mozilla maintains its own cryptographic library, NSS. That independence has benefits, but also means bugs in NSS do not get fixed by anyone else's patch cycle.
The flaw sits in the code path that verifies digital signatures for incoming content: emails, PDFs, web pages. It fires precisely when the application is trying to confirm whether a sender is genuine.
How the overflow happens
NSS allocates memory for the public key involved in signature verification. The allocation is sized to accommodate the largest key NSS expects—including RSA keys up to 4096 bits, which are standard in production environments. The buggy code assumed nothing larger would ever arrive and skipped a length check.
Send a signature with an RSA key exceeding 4096 bits, and the data overflows into adjacent memory. Normally this causes a crash. But a carefully shaped overflow can redirect execution into attacker-controlled code, turning denial of service into remote code execution.
Who should care
| User Type | Risk Level | Action |
|---|---|---|
| Thunderbird users | High | Patch immediately when available |
| LibreOffice/Evolution/Evince users | High | Monitor vendor advisories |
| Firefox users | None | No action needed |
| Linux admins | Medium | Check for system-wide NSS updates |
| Enterprise IT | Medium | Inventory NSS dependencies across the org |
Our analysis
This bug exposes a familiar trap: code that assumes "this will never happen" and skips validation. RSA keys above 4096 bits are vanishingly rare—larger keys are slower to generate and offer no meaningful security gain against current cracking methods—but the code's job is to handle unexpected input gracefully, not to assume it won't arrive.
For most teams, the practical question is not whether their favourite app uses NSS, but whether their vendor or IT department will ship the fix before the bug is weaponised. Vendors who use NSS through a framework or runtime will pick up the fix on their own schedule, and that schedule varies. Larger projects such as Mozilla and LibreOffice will likely patch promptly. Smaller downstream projects are the usual laggards.
Worth treating this as a supply chain lesson: crypto libraries deserve the same dependency scrutiny as any other open source component.
What to watch next
Patch anything that ships NSS as soon as fixed builds are available. Watch Mozilla's security advisories, your Linux distro's security feed, and LibreOffice for updates. Assume unsigned or unexpectedly large signed documents are red flags until patches land.
Key takeaways
- BigSig is a buffer overflow in NSS signature verification that can escalate to remote code execution.
- Firefox is unaffected; Thunderbird, LibreOffice, Evolution and Evince are explicitly listed as vulnerable.
- Apps that bundle NSS outside the Mozilla family may also be exposed.
- Treat CVE-2021-43527 as a priority inventory task across every tool that processes signed content.
- Map crypto dependencies now, so the next advisory does not require a scramble.
Frequently asked questions
What is CVE-2021-43527?
A critical buffer overflow in Mozilla's NSS cryptographic library, nicknamed BigSig, that triggers when verifying an oversized digital signature and can lead to remote code execution.
Is Firefox affected by BigSig?
No. The bug cannot be triggered through Firefox, though many other applications that use NSS are affected.
Which apps are confirmed as vulnerable?
Mozilla explicitly names Thunderbird, LibreOffice, Evolution and Evince. Other apps that bundle NSS may also be vulnerable.
How does the overflow become remote code execution?
The oversized signature corrupts adjacent memory, which usually causes a crash. An attacker who controls the overflow's contents can redirect execution into their own code.
What should teams do right now?
Inventory every tool that handles signed documents or email, watch vendor advisories for patched builds, and schedule updates as soon as fixes are available.