Incident sheet · /security
- System
- Security & Risk
- Filed
- Read
- 4 min · 719 words
- Severity
- Routine
CERT-In Flags emBridge Flaw in eMudhra Signing Tool After CA Collapse
CERT-In's November 13 advisory covers a low-severity emBridge file-disclosure bug, patched November 11 — weeks after eMudhra revoked eight weakly-generated CA certificates.

Event log
- CERT-In advisory dated November 13 flags a low-severity emBridge flaw; eMudhra says it was fixed November 11.
- Affected: emBridge 5.9.1.x–5.9.3.x (Windows), 3.2.4.x–3.2.6.x (macOS), 3.2.0.x–3.3.0.x (Ubuntu/Red Hat).
- On October 17 a researcher derived private keys for eight eMudhra intermediate CA certificates in under a second; revoked October 18.
- eMudhra will exit the global SSL/TLS business and appointed KPMG as independent reviewer on October 30.
- The emBridge bug affects the domestic signing stack the government had said was unaffected.
India's CERT-In published an advisory on November 13 against eMudhra's emBridge desktop software, four weeks after the same vendor's certificate authority collapsed. The flaw is low severity. The timing is not. emBridge sits inside the domestic digital signature stack that the government had said was untouched by October's incident. It was not untouched.
Security researcher Karan Saini reported the bug. An attacker on the same local network could view file, folder, and drive names on a machine running a vulnerable version. CERT-In's note states plainly what the flaw does not allow:
- Reading file contents.
- Modifying or deleting files.
- Executing code.
- Obtaining cryptographic keys or token PINs.
eMudhra says it resolved the issue on November 11 — two days before the advisory went public. The company also claims its firewall and local-only request handling block direct access from other machines. That claim addresses one attack path. It does not address the browser path described below.
How does the attack actually work?
emBridge is middleware. Browsers cannot talk directly to USB tokens holding digital signature certificates, so emBridge bridges them. CERT-In found that some file-browsing functions did not verify whether requests came from authorised sources. On Windows, those functions run with the highest system privileges.
That combination — unauthenticated requests plus elevated privileges — let a malicious webpage query emBridge and map the machine's file structure. eMudhra insists several conditions must align at once:
- A vulnerable emBridge version.
- A malicious webpage hosted on the same local network.
- The user opening that page.
- A browser without Local Network Access restrictions.
Four preconditions is a narrow window. But a motivated attacker inside a corporate network controls the first two and can engineer the third. Only the fourth depends on browser defaults the enterprise does not manage.
Which versions are vulnerable, and what fixes exist?
The remediation table is specific, and the fix is blunt: eMudhra removed all file-browsing functions from emBridge entirely, so the software can no longer list files and folders at all.
| Platform | Vulnerable | Upgrade to |
|---|---|---|
| Windows | 5.9.1.x to 5.9.3.x | 5.9.4.x or later |
| macOS | 3.2.4.x to 3.2.6.x | 3.2.7.x or later |
| Ubuntu / Red Hat Linux | 3.2.0.x to 3.3.0.x | 3.3.1.x or later |
IT teams should inventory deployments now and force the upgrade. The patch shipped November 11, so there is no supply excuse for delay.
Is the severity rating itself in dispute?
Yes. Saini described the bug as trivial, noting that eMudhra's own advisory downplays its significance — a rare case of researcher and vendor agreeing the bug is small, while the vendor compresses it further. An eMudhra spokesperson told Inc42 that each digital signature certificate requires a token PIN before use, and that CERT-In confirmed no cryptographic keys or PINs were exposed.
That defense is accurate as far as it goes. Metadata — file names, folder structures, drive names — still reveals what a department works on, and on which machines. Low severity does not mean zero value to an attacker doing reconnaissance.
What does this mean after October's certificate incident?
The backdrop is worse than the bug. On October 17, a researcher found that private keys for eight of eMudhra's intermediate certificate authority certificates were generated so poorly they could be derived from publicly available data in under a second. eMudhra revoked all eight on October 18. Browser vendors then blocked them and distrusted the associated root.
The company traced the weak keys to a script error during an April 2025 key-generation ceremony. The fallout continues on multiple fronts:
- eMudhra said it will exit the global SSL/TLS certificate business.
- Its shares fell sharply over two days.
- The Ministry of Electronics and Information Technology set up a special team to examine the incident.
- On October 30, eMudhra appointed KPMG as independent reviewer of the incident and its security controls.
Inc42 reports the emBridge flaw touches the domestic signing stack — the part the government had previously stated was unaffected. That statement now needs revision. For enterprises, the lesson is procedural: verify vendor assurances against advisories, patch emBridge to the fixed versions, and wait for KPMG's findings before trusting the rest of the stack.
via medianama.com (Source)
More from Daniel Okafor
Show full bio
Staff writer covering technology and product news in enterprise information technology and the leaders who run at CIO Monitor.
203 articles
The newsroom digest
One email a day with the stories that matter. No noise.
Cross-references
- eMudhra Revokes 8 More CAs; Microsoft to Remove 10 Roots
- eMudhra exits global TLS certificate market after signing-key compromise
- Eight eMudhra CA Keys Cracked: Chrome and Firefox Block Intermediates
- eMudhra Revokes 8 More CA Certificates, Raising Affected Total to 16
- Hackers Burned $740,000 in Stolen AI Compute; Railway Ate the Bill