GHSA-f28g-86hc-823q json
Tokenizer vulnerable to client brute-force of token secrets
published 3y ago modified 2y ago also GO-2023-1914
- cvss
- —
- not scored
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- —
- no score, EPSS covers CVEs only
- public exploits
- 0
- none known
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.
Patch / fix
- go github.com/superfly/tokenizer 0.0.1
- github.com/superfly/tokenizer#8 pull request
- github.com/superfly/tokenizer#9 pull request
Is GHSA-f28g-86hc-823q in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerAffected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| go | github.com/superfly/tokenizer | <0.0.1 |
0.0.1 |
References
Sources
- GitHub Advisory GHSA-f28g-86hc-823q
- OSV GO-2023-1914
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.