How to fix: Angular bypassSecurityTrust* with user input
Calling bypassSecurityTrustHtml(userInput) or bypassSecurityTrustScript(userInput) tells Angular the value is safe, completely defeating its built-in DomSanitizer.
Why it matters
Attacker-controlled HTML or URL is rendered as-is, enabling stored XSS or javascript: navigation.
The `code-xss-angular-bypass-dynamic` check verifies that the server does not expose the `xss-angular-bypass-dynamic` weakness in the code category. The detection runs against the response headers, body, or auxiliary probes (DNS, TLS, async fetch) as appropriate.
How to fix it
- 1Sanitize the value with DomSanitizer.sanitize(SecurityContext.HTML, ...) before trusting it.
- 2Avoid passing user input directly into bypassSecurityTrust* APIs.
- 3Render Angular templates with interpolation; reserve bypass for known-static strings.
Code examples
Use SecurityContext.HTML sanitization for dynamic binding
import { DomSanitizer, SecurityContext } from "@angular/platform-browser";
@Component({ template: `<div [innerHTML]="safeHtml"></div>` })
export class SafeHtmlComponent {
safeHtml: string;
constructor(private sanitizer: DomSanitizer) {
this.safeHtml = this.sanitizer.sanitize(
SecurityContext.HTML,
dynamicHtmlInput
) ?? "";
}
}References
Detected automatically by VulnRadar. The check id is code-xss-angular-bypass-dynamic, 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 Angular bypassSecurityTrust* with user input?
- VulnRadar rates this high 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 code-xss-angular-bypass-dynamic, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does Angular bypassSecurityTrust* with user input map to?
- It maps to CWE-79. In the OWASP Top 10 it falls under A03:2021.
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.