Search Results for "injection"

...Coraza runs the OWASP Core Rule Set (CRS) to protect your web applications from a wide range of attacks, including the OWASP Top Ten, with a minimum of false alerts. CRS protects from many common attack categories including: SQL Injection (SQLi), Cross Site Scripting (XSS), PHP & Java Code Injection, HTTPoxy, Shellshock, Scripting/Scanner/Bot Detection & Metadata & Error Leakages. Coraza is a library at its core, with many integrations to deploy on-premise Web Application Firewall instances.

How It Works [Android Device] │ │ OpenVPN TCP/UDP ▼ [SNI Tunnel Client] ← Wraps traffic in SSL + injects fake SNI │ │ Looks like: HTTPS → microsoft.com ✓ ▼ [ISP Firewall] ← Passes through — sees only valid HTTPS │ ▼ [VPS Server] ← Decrypts TLS, recovers OpenVPN traffic │ ▼ [OpenVPN Server] ← Receives native OpenVPN traffic │ ▼ Internet The core trick is SNI injection: the tunnel client inserts a trusted domain name (e.g. microsoft.com) into the TLS handshake. The ISP sees what appears to be a standard HTTPS connection and allows it through. The VPS server on the other end strips the SSL wrapper and forwards the real OpenVPN packets to the OpenVPN server.

How It Works [Android Device] │ │ WireGuard UDP ▼ [SNI Tunnel Client] ← Wraps UDP in TLS/ssl + injects fake SNI │ │ Looks like: HTTPS → microsoft.com ✓ ▼ [ISP Firewall] ← Passes through — sees only valid HTTPS │ ▼ [VPS Server] ← Decrypts TLS, recovers WireGuard UDP │ ▼ [Cloudflare Warp] ← Receives native WireGuard traffic │ ▼ Internet The core trick is SNI injection: the tunnel client inserts a trusted domain name (e.g. microsoft.com) into the TLS handshake. The ISP sees what appears to be a standard HTTPS connection and allows it through. The VPS server on the other end strips the TLS wrapper and forwards the real WireGuard packets to Cloudflare.

...Instead of leaving headers and policies to ad-hoc middleware, it sets Content Security Policy, X-Frame-Options, and other protections by default, and centralizes template escaping rules. Request handling emphasizes principled APIs for parsing and validating input, reducing the risk of injection and deserialization bugs. The framework’s routing and response layers are designed to be explicit and auditable, making it clearer when unsafe behaviors are being opted into. It also offers utilities for CSRF protection, secure cookies, and safe resource embedding that work well with Go’s standard library. By turning security posture into a first-class concern, go-safeweb helps teams achieve defense-in-depth without scattering security logic across a codebase.