GHSA-GFWJ-45PC-W6R5
ALTCHA: Nil-map panic (pre-verification DoS) in v1 parseServerSignature on malformed VerificationData
Ciclo de vida de la vulnerabilidad
| Fecha | Fase | Evento | Detalle |
|---|---|---|---|
| Divulgación | Publicada | GHSA-GFWJ-45PC-W6R5 divulgada | |
| Divulgación | Modificada | Última actualización del registro | |
| Monitoreo | Detectada | Ingresó al índice | |
| Monitoreo | Verificada | Última verificación contra las fuentes |
Summary
`parseServerSignature` in the v1 module only initializes `ServerSignatureVerificationData.Extra` inside the `if err == nil` branch after `url.ParseQuery(parsedPayload.VerificationData)`. Go's `url.ParseQuery` returns the successfully-parsed pairs together with a non-nil error when the query string contains a malformed percent-escape. A subsequent loop unconditionally writes unknown keys into `Extra`, regardless of `err`, causing a nil-map write panic (assignment to entry in nil map) whenever an attacker supplies a `VerificationData` string with a bad %-escape (e.g. `x=1&%zz=2`).
This is reachable pre-authentication: `parseServerSignature` is called by the exported `VerifyServerSignature` / `VerifyServerSignatureSafe` before any HMAC/signature check, and `VerificationData` is attacker-controlled data forwarded by the client as part of the ALTCHA server-signature payload.
Impact
Any application calling `VerifyServerSignature` or `VerifyServerSignatureSafe` on unauthenticated input can be made to panic by submitting a crafted payload. Under standard net/http, the per-request goroutine panic is recovered and the request aborts (a log-flood / per-request DoS); it escalates to a full process crash if verification runs in an application-spawned goroutine or a non-recovering framework.
Proof Of Concept
payload, _ := json.Marshal(ServerSignaturePayload{
Algorithm: SHA256,
VerificationData: "x=1&%zz=2",
Signature: "irrelevant",
Verified: true,
})
encoded := base64.StdEncoding.EncodeToString(payload)
VerifyServerSignature(encoded, "some-secret") // panics: assignment to entry in nil map
Patch
`Extra` is now initialized unconditionally before the `url.ParseQuery` error check, so it's always safe to write into regardless of parse errors.
Workarounds
Recover from panics around calls to `VerifyServerSignature`/`VerifyServerSignatureSafe`, or reject/sanitize `VerificationData` before calling them, until upgrading.
Patch
Patch commit: 2c4fc27
Credit
Reported by Arpit Jain (@arpitjain099) via private disclosure.
Incluye detalles técnicos publicados por el investigador. Úselos solo para validar y corregir sus propios sistemas.
Rangos afectados
Estado del parche por paquete
| Paquete / producto | Estado | Corregida en | Desde divulgación | Última versión |
|---|---|---|---|---|
Gogithub.com/altcha-org/altcha-lib-go/v2 |
Corregida | 2.1.0 | — | — |
2.1.0Arsenal público
Sin exploits, módulos ni PoC públicos conocidos a la fecha de verificación.
https://nvd.nist.gov/vuln/detail/CVE-2026-103033https://github.com/altcha-org/altcha-lib-go/security/advisories/GHSA-gfwj-45pc-w6r5https://github.com/altcha-org/altcha-lib-go/commit/2c4fc27a7b2d5b89f7175676445efcacc564c27chttps://github.com/altcha-org/altcha-lib-gohttps://github.com/altcha-org/altcha-lib-go/releases/tag/v2.1.0Las referencias externas se muestran para copiar: cve.llama.ec no lo redirige a otros sitios.
