ALTCHA Proof-of-Work Vulnerable to Challenge Splicing and Replay
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| altcha-org | altcha-lib | affected |
|
No data.
No data.
| Vendor | Product | Versions |
|---|---|---|
| Altcha | Altcha | — |
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-6gvq-jcmp-8959 | ALTCHA Proof-of-Work Vulnerable to Challenge Splicing and Replay |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.463% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Altcha
Altcha altcha |
|
| Vendors & Products |
Altcha
Altcha altcha |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | ALTCHA is privacy-first software for captcha and bot protection. 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. 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, which include version 1.0.0 of the altcha Golang package, version 1.0.0 of the altcha Rubygem, version 1.0.0 of the altcha pip package, version 1.0.0 of the altcha Erlang package, version 1.4.1 of the altcha-lib npm package, version 1.3.1 of the altcha-org/altcha Composer package, and version 1.3.0 of the org.altcha:altcha Maven package. As a mitigation, implementations may append a delimiter to the end of the `salt` value prior to HMAC computation (for example, `<salt>?expires=<time>&`). 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. | |
| Title | ALTCHA Proof-of-Work Vulnerable to Challenge Splicing and Replay | |
| Weaknesses | CWE-115 CWE-347 |
|
| References |
|
|
| Metrics |
cvssV3_1
|