Tokenizer vulnerable to client brute-force of token secrets
Priority LOW 38Published · Updated
Key facts
- Attack vector
- —
- Privileges required
- —
- User interaction
- —
- Attack complexity
- —
- Impact type
- —
- Confidentiality · integrity · availability
- —
- Fix status
- Fixed
No CVSS vector from any source. Fix status from GitHub.
Summary
### Impact Authorized clients, having an `inject_processor` secret, could brute-force the secret token value by abusing the `fmt` parameter to the `Proxy-Tokenizer` header. ### Patches This was fixed in https://github.com/superfly/tokenizer/pull/8 and further mitigated in https://github.com/superfly/tokenizer/pull/9.
Why it matters now
Fix Fixed github.com/superfly/tokenizer (Go): 0.0.1
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| — | github.com/superfly/tokenizer (Go) | before 0.0.1 | 0.0.1 | Patch available | GHSA-f28g-86hc-823q |
- github.com/superfly/tokenizer (Go) Vendor— Affected before 0.0.1 Fixed in 0.0.1 Patch available GHSA-f28g-86hc-823q
Remediation
- Fix · GHSA-f28g-86hc-823q github.com/superfly/tokenizer (Go) Fixed in 0.0.1 Advisory →
Timeline
- 2026-10-03 Threatist record created from GHSA-f28g-86hc-823q
References
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences