client-certificate-auth Vulnerable to Open Redirect via Host Header Injection in HTTP-to-HTTPS redirect
Summary
Versions 0.2.1 and 0.3.0 of client-certificate-auth contain an open redirect vulnerability. The middleware unconditionally redirects HTTP requests to HTTPS using the unvalidated Host header, allowing an attacker to redirect users to arbitrary domains.
Vulnerable Code
// lib/clientCertificateAuth.js (versions 0.2.1, 0.3.0)
if (!req.secure && req.header('x-forwarded-proto') != 'https') {
return res.redirect('https://' + req.header('host') + req.url);
}
Attack Scenario
- Attacker crafts a link:
http://vulnerable-app.example.com/login - When victim clicks, attacker intercepts and injects header:
Host: attacker.com - Server responds:
302 Found → https://attacker.com/login - Victim is redirected to attacker-controlled site
Impact
- Phishing: Attackers can use trusted domain links to redirect victims to credential-harvesting pages
- OAuth/SSO Token Theft: In authentication flows, authorization codes or tokens may leak via redirect
- Referer Leakage: Sensitive URL parameters may be exposed to attacker domains via the Referer header
- Cache Poisoning: In deployments with shared caches, malicious redirects may be cached and served to other users
Exploitability
Exploitation requires that HTTP traffic reaches the Node.js application without TLS termination setting x-forwarded-proto: https. This condition is uncommon in production deployments behind modern reverse proxies or load balancers, which limits real-world exploitability.
Fix
The vulnerable redirect behavior has been completely removed in version 1.0.0.
npm install client-certificate-auth@^1.0.0
Workarounds
If upgrading is not immediately possible:
- Block HTTP traffic at the network/load balancer level
- Ensure your reverse proxy always sets
x-forwarded-proto: https - Add middleware before
clientCertificateAuthto validate theHostheader against an allowlist
References
Software afectado
Haz clic en una tecnología para ver todas sus vulnerabilidades.
| Plataforma | Paquete | Versiones vulnerables | Corregida en |
|---|---|---|---|
| Paquete de npm | client-certificate-auth | >= 0.2.1, < 1.0.0 | 1.0.0 |
Referencias
- https://github.com/tgies/client-certificate-auth/security/advisories/GHSA-m4w9-gch5-c2g4
- https://nvd.nist.gov/vuln/detail/CVE-2026-25651
- https://github.com/tgies/client-certificate-auth/commit/8fc995e953db483495be46862965e50fe9e1cc52
- https://github.com/tgies/client-certificate-auth
- https://github.com/tgies/client-certificate-auth/releases/tag/v1.0.0
- Vector CVSS
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N- Debilidad (CWE)
CWE-601- Plataforma
- npm
- Paquete
client-certificate-auth- Publicada
- 06.02.2026
- Actualizado
- 11.10.2026 10:22
Fuentes y licencias
OSV / GitHub Advisory Database - GHSA-m4w9-gch5-c2g4 - CC BY 4.0
Historial de vulnerabilidades: client-certificate-auth
Todas las vulnerabilidades publicadas de este paquete (Paquete de npm), de la más reciente a la más antigua. Muestra si es un fallo aislado o un paquete que hay que vigilar.
Esta es la única vulnerabilidad conocida de este paquete.
Identifica las vulnerabilidades de tu aplicación
Con la integración de DockRay y el inventario de software activado, DockRay compara las versiones notificadas de los componentes con las vulnerabilidades conocidas y avisa de las coincidencias confirmadas. La cobertura depende de la tecnología compatible y de los avisos disponibles.