# GHSA-f28g-86hc-823q: Tokenizer vulnerable to client brute-force of token secrets

> Authorized clients can brute-force token secrets via the Proxy-Tokenizer header, potentially bypassing security controls.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 13 Jul 2023
- **Also known as:** GO-2023-1914

## What is GHSA-f28g-86hc-823q?

GHSA-f28g-86hc-823q is a vulnerability in github.com/superfly/tokenizer, published on 13 Jul 2023. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

### 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.

## Which versions are affected by GHSA-f28g-86hc-823q?

3 open source packages ship an affected version, including github.com/superfly/tokenizer.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/superfly/tokenizer` | Go | All versions | 0.0.1 |
| `github.com/superfly/tokenizer` | Go | All versions | 0.0.1 |
| `github.com/superfly/tokenizer` | Go | All versions | 0.0.1 |

## How do I fix GHSA-f28g-86hc-823q?

Upgrade github.com/superfly/tokenizer to 0.0.1 or later.

## Is GHSA-f28g-86hc-823q being exploited?

There is no known exploitation of GHSA-f28g-86hc-823q in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-f28g-86hc-823q and fix it if it is affected.

What it is: GHSA-f28g-86hc-823q is a vulnerability in github.com/superfly/tokenizer, published on 13 Jul 2023. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of GHSA-f28g-86hc-823q in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/superfly/tokenizer (Go): affected all versions; fixed in 0.0.1
- github.com/superfly/tokenizer (Go): affected all versions; fixed in 0.0.1
- github.com/superfly/tokenizer (Go): affected all versions; fixed in 0.0.1

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/GHSA-f28g-86hc-823q/ (Markdown: https://insights.sbomify.com/GHSA-f28g-86hc-823q/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-f28g-86hc-823q

---
From sbomify Insights: https://insights.sbomify.com/GHSA-f28g-86hc-823q/
Summaries are generated and may contain mistakes; the official description above is the record.