GHSA-6gvq-jcmp-8959 ALTCHA Proof-of-Work Vulnerable to Challenge Splicing and Replay

• npm altcha-lib: < 1.4.1 → fixed in 1.4.1 • Packagist altcha-org/altcha: < 1.3.1 → fixed in 1.3.1 • Go github.com/altcha-org/altcha-lib-go: < 1.0.0 → fixed in 1.0.0 • Maven org.altcha:altcha: < 1.3.0 → fixed in 1.3.0 • RubyGems altcha: < 1.0.0 → fixed in 1.0.0 • PyPI altcha: < 1.0.0 → fixed in 1.0.0 • Hex altcha: < 1.0.0 → fixed in 1.0.0

Impact A cryptographic semantic binding flaw in ALTCHA libraries allows challenge payload splicing, which may enable replay attacks. The HMAC signature does not unambiguously bind challenge parameters to the nonce, allowing an attacker to reinterpret a valid proof-of-work submission with a modified expiration value. This may allow previously solved challenges to be reused beyond their intended lifetime, depending on server-side replay handling and deployment assumptions. The vulnerability primarily impacts abuse-prevention mechanisms such as rate limiting and bot mitigation. It does not directly affect data confidentiality or integrity. Patches This issue has been addressed by enforcing explicit semantic separation between challenge parameters and the nonce during HMAC computation. Users are advised to upgrade to patched versions. Workarounds As a mitigation, implementations may append a delimiter to the end of the `salt` value prior to HMAC computation (for example, `?expires=&`). This prevents ambiguity between parameters and the nonce and is backward-compatible with existing implementations, as the delimiter is treated as a standard URL parameter separator.