Is Asan ID token signing safe?
Asan ID token signing is low risk.
Asan ID token signing relays smart card certificate and signing operations to any web page via an unguarded postMessage channel.
The extension injects a script into every page and listens for postMessage events using only a forgeable data-field check (event.data.src === 'azedit_page.js') rather than an origin check. Any page script can send a crafted message to trigger CERT (read the user's X.509 certificate) or SIGN (produce a digital signature over attacker-supplied data) operations via the native host az.asanimza.azedit. The native host response is then posted back to the page, exposing smart card credentials and signing capability to any site the user visits.
Part of this rating comes from analysis signals we haven't published as detailed findings yet.
What Asan ID token signing can do
Permissions this extension asks for, as declared in version 0.0.1. Asking for a permission is not a finding on its own - it is what the extension can do if it chooses to.
Talk to a program installed on your computer, outside the browser's sandbox
nativeMessaging
Where Asan ID token signing sends data
- az.asanimza.azedit
Found in its code · only this extension
Chrome Web Store listing
- Versions
- 0.0.1 seen since March 4, 2026
- Store rating
- 3.8 from 4 ratings
- Last updated
- October 1, 2015
- Size
- 62.84 KiB
