GHSA-gfwj-45pc-w6r5

Suggest an improvement
Source
https://github.com/advisories/GHSA-gfwj-45pc-w6r5
Import Source
https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2026/11/GHSA-gfwj-45pc-w6r5/GHSA-gfwj-45pc-w6r5.json
JSON Data
https://api.osv.dev/v1/vulns/GHSA-gfwj-45pc-w6r5
Aliases
Published
2026-11-20T00:21:19Z
Modified
2026-11-20T00:30:06Z
Severity
  • 5.3 (Medium) CVSS_V3 - CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L CVSS Calculator
Summary
ALTCHA: Nil-map panic (pre-verification DoS) in v1 parseServerSignature on malformed VerificationData
Details

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.

Database specific
{
    "cwe_ids": [
        "CWE-248",
        "CWE-476"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2026-11-20T00:21:19Z",
    "nvd_published_at": "2026-11-19T21:17:40Z",
    "severity": "MODERATE"
}
References

Affected packages

Go / github.com/altcha-org/altcha-lib-go/v2

Package

Name
github.com/altcha-org/altcha-lib-go/v2
View open source insights on deps.dev
Purl
pkg:golang/github.com/altcha-org/altcha-lib-go/v2

Affected ranges

Type
SEMVER
Events
Introduced
2.0.0
Fixed
2.1.0

Database specific

source
"https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2026/11/GHSA-gfwj-45pc-w6r5/GHSA-gfwj-45pc-w6r5.json"