BlackTree Security · Infrastructure · Automation · AI

Sign2Shell Turns Document-Signing Extensions Into Windows Code Execution

Software installed to sign documents can also provide a route out of the browser. Researchers at Am I Being Pwned report remote code execution in five widely installed Brazilian signing extensions, representing about ten million installations across browser stores. Their 17 November Sign2Shell disclosure identifies Lacuna Web PKI, Softplan Web Signer, Certisign WebSigner, Certisign CertiPlugin and BRy Assinatura Digital. The reported attacks target Windows systems with the corresponding native host installed.

The privileged component is outside the browser

Chrome’s native-messaging documentation describes how an extension exchanges messages with a separately installed application. That application is registered through a host manifest, including the extension origins allowed to contact it. The browser launches the native process and communicates through standard input and output.

This arrangement makes hardware and operating-system integrations possible. It also places an important validation boundary in the native application. Permission for an extension to contact a host does not establish that every website-originated request reaching that extension is trustworthy.

The researchers’ published repository documents six attack chains across the five products, including separate chains against Lacuna Web PKI 2.17.0 and the partial-patch 2.17.5. Their common mechanism is an attacker-influenced module path reaching a Windows library-loading operation. The intended signing or certificate operation can fail after the loaded module has already run. Renaming a library with a harmless-looking extension does not change that behaviour.

Four fixes and one mitigation

The researchers report these first fixed extension versions:

  • Lacuna Web PKI: 2.18.0.
  • Certisign WebSigner: 2.18.0.
  • Softplan Web Signer: 2.18.3.
  • BRy Assinatura Digital: 2.2.8.
  • Certisign CertiPlugin: no complete fix reported; version 1.15.1 narrows the allowed websites.

The article explicitly distinguishes CertiPlugin’s mitigation from a corrected library-loading operation. It also says Lacuna 2.17.5 remained vulnerable after an initial partial patch. The repository’s broad statement that the issues are patched should therefore not be read as proof that CertiPlugin’s underlying defect is fixed.

Check the installed pair, then investigate exposure

Inventory both the extension and its native companion. Record product, publisher, extension identifier, installed version and the Windows application it uses. Compare that evidence with the supplier’s current instructions and the disclosure’s version boundaries. Confirm the update has actually reached managed browser profiles, rather than relying only on an update policy being enabled.

For CertiPlugin, seek a vendor-supported complete fix or an approved alternative. A narrower website list reduces reachability but should remain visible as a mitigation in the exception record. Remove signing software that a device no longer needs, and assess operational consequences before disabling a component used for essential signing work.

The demonstrated result is code running with the logged-in user’s permissions. The researchers did not investigate real-world exploitation, so installation counts are neither victim counts nor evidence of a mass compromise. If a device was exposed, review relevant browser downloads, unexpected activity beneath the signing host and endpoint telemetry. Preserve suspicious evidence and assess accessible credentials and signing material through the incident-response process.

A version check closes only the update question. The wider design lesson is to authenticate the website request and validate the exact native operation before granting access to operating-system capabilities.

Leave a Reply

Your email address will not be published. Required fields are marked *