OSV-2021-812 Uncaught exception in com.esotericsoftware.kryo.serializers.FieldSerializer.read
Not scored
Published
Check this codebase for OSV-2021-812 and fix it if it is affected.
What it is: OSV-2021-812 is a denial of service vulnerability in kryo, published on 29 May 2021.
Exploitation: There is no known exploitation of OSV-2021-812 in the wild and no public exploit code.
Affected packages and fixed versions:
- kryo (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-2021-812/ (Markdown: https://insights.sbomify.com/OSV-2021-812/index.md)
An uncaught exception in Kryo's FieldSerializer can cause a denial of service when processing malformed serialized data.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Not stated
- Victim action needed
- Not needed
- Fix
- None listed
What is OSV-2021-812?
OSV-2021-812 is a denial of service vulnerability in kryo, published on 29 May 2021.
Official description
OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=34733
Crash type: Uncaught exception
Crash state:
com.esotericsoftware.kryo.serializers.FieldSerializer.read
com.esotericsoftware.kryo.Kryo.readObject
DeserializeStringFuzzer.fuzzerTestOneInput
Which versions are affected by OSV-2021-812?
1 open source package ship an affected version, including kryo.
| Package | Affected | Fixed in |
|---|---|---|
kryo OSS-Fuzz | All versions | None |
How do I fix OSV-2021-812?
No fix has been published for OSV-2021-812 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-2021-812 being exploited?
There is no known exploitation of OSV-2021-812 in the wild and no public exploit code.