OSV-2022-616 Timeout in JsonFuzzer
Not scored
Published
Check this codebase for OSV-2022-616 and fix it if it is affected.
What it is: OSV-2022-616 is a denial of service vulnerability in fastjson2, published on 24 Jul 2022.
Exploitation: There is no known exploitation of OSV-2022-616 in the wild and no public exploit code.
Affected packages and fixed versions:
- fastjson2 (OSS-Fuzz): affected all versions; no fix listed
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/OSV-2022-616/ (Markdown: https://insights.sbomify.com/OSV-2022-616/index.md)
A timeout vulnerability in the JSON fuzzer can cause denial of service by hanging the application during parsing.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Not stated
- Victim action needed
- Not needed
- Fix
- None listed
What is OSV-2022-616?
OSV-2022-616 is a denial of service vulnerability in fastjson2, published on 24 Jul 2022.
Official description
OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=49401
Crash type: Timeout
Crash state:
JsonFuzzer
Which versions are affected by OSV-2022-616?
1 open source package ship an affected version, including fastjson2.
| Package | Affected | Fixed in |
|---|---|---|
fastjson2 OSS-Fuzz | All versions | None |
How do I fix OSV-2022-616?
No fix has been published for OSV-2022-616 yet. Limit exposure of the affected software until one is available.
Upgrade, then put limits on request size, rate and nesting depth so one client cannot exhaust the service. More about Denial of service.
Is OSV-2022-616 being exploited?
There is no known exploitation of OSV-2022-616 in the wild and no public exploit code.