# GHSA-GFWJ-45PC-W6R5: ALTCHA: Nil-map panic (pre-verification DoS) in v1 parseServerSignature on malformed VerificationData

- Database: GitHub
- Severity: medium (stated by ghsa, no CVSS score)
- Published: 2026-11-20
- Modified: 2026-11-20

## Tracked as

- [CVE-2026-103033](https://cve.now/CVE-2026-103033.md): ALTCHA Lib Go denial of service via nil-map panic in signature parsing

## Affected versions

- github.com/altcha-org/altcha-lib-go/v2 (Go): from 2.0.0, fixed in 2.1.0

## Description

### 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

```go
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.

## References

- https://github.com/altcha-org/altcha-lib-go/security/advisories/GHSA-gfwj-45pc-w6r5
- https://nvd.nist.gov/vuln/detail/CVE-2026-103033
- https://github.com/altcha-org/altcha-lib-go/commit/2c4fc27a7b2d5b89f7175676445efcacc564c27c
- https://github.com/altcha-org/altcha-lib-go
- https://github.com/altcha-org/altcha-lib-go/releases/tag/v2.1.0

Page: https://cve.now/GHSA-GFWJ-45PC-W6R5
