InfoCode
How to fix: SubtleCrypto API Usage
Web Crypto API usage detected.
Why it matters
Ensure proper key management.
Web Crypto provides cryptographic operations.
How to fix it
- 1Use secure random generation and proper key storage.
Code examples
Web Crypto API: use secure algorithms
// Use AES-GCM (authenticated encryption), not AES-CBC without MAC
const key = await crypto.subtle.generateKey(
{ name: "AES-GCM", length: 256 },
false,
["encrypt", "decrypt"]
);
const iv = crypto.getRandomValues(new Uint8Array(12)); // unique per message
const encrypted = await crypto.subtle.encrypt(
{ name: "AES-GCM", iv },
key,
plaintext
);
// Prepend iv to ciphertext for storage/transmissionReferences
Detected automatically by VulnRadar. The check id is crypto-subtle-usage, stable across every scan so you can filter or diff on it.
More code checks
- CriticalForm Submits Data Over Insecure HTTP
- MediumPotential Prototype Pollution Sinks Detected
- HighPotential Command Injection Vectors
- HighJWT Decoded Without Signature Verification
- HighPotential Path Traversal Vulnerability
- HighInsecure Authentication Mechanisms Detected
- HighPotential Insecure Deserialization
- Mediumeval() Usage in Inline Scripts
Questions
- How severe is SubtleCrypto API Usage?
- VulnRadar rates this info severity in the code category. The severity is fixed per check, not scored per site, so the same finding is the same severity on every scan.
- Does VulnRadar check for this automatically?
- Yes. It runs as part of every scan under the check id crypto-subtle-usage, which stays the same between runs so you can filter, diff, or gate CI on it.
Missing a check?
The detection set is open. If you know a misconfiguration this does not catch, propose it: the issue template asks for the threat model, how to detect it, the false-positive risk, and a test fixture, which is the same thing a maintainer would have to work out anyway.