GHSA-9WFH-R7PQ-3FR9
Peer certificates were accepted for purposes they don't allow
Ciclo de vida de la vulnerabilidad
| Fecha | Fase | Evento | Detalle |
|---|---|---|---|
| Divulgación | Publicada | GHSA-9WFH-R7PQ-3FR9 divulgada | |
| Monitoreo | Detectada | Ingresó al índice | |
| Monitoreo | Verificada | Última verificación contra las fuentes |
When it checked a peer's certificate, erlang_quic validated the chain and the host name but not what the certificate may be used for. A certificate issued by a trusted CA for another purpose, such as code signing, was accepted to authenticate a QUIC server or client. So was one whose Key Usage doesn't allow signatures.
A server's certificate must allow TLS server authentication, and a client's certificate TLS client authentication, when it carries an Extended Key Usage extension (RFC 5280 Section 4.2.1.12). Its Key Usage, when present, must allow digital signatures (RFC 9846 Section 4.5.1.2).
3.0.0 checks both, on the client for the server's certificate and on the server for a client certificate.
- A certificate you list yourself in `cacerts` (a pinned or self-signed one) is still trusted as you configured it.
- A certificate used in both directions, as an Erlang distribution node uses its own, needs both purposes or no Extended Key Usage.
Rangos afectados
Estado del parche por paquete
| Paquete / producto | Estado | Corregida en | Desde divulgación | Última versión |
|---|---|---|---|---|
Hexquic |
Sin parche | — | — | — |
Arsenal público
Sin exploits, módulos ni PoC públicos conocidos a la fecha de verificación.
https://github.com/benoitc/erlang_quic/security/advisories/GHSA-9wfh-r7pq-3fr9Las referencias externas se muestran para copiar: cve.llama.ec no lo redirige a otros sitios.
