{"answers":{"affected":"1 open source package ship an affected version, including kryo.","exploited":"There is no known exploitation of OSV-2021-812 in the wild and no public exploit code.","fix":"No fix has been published for OSV-2021-812 yet. Limit exposure of the affected software until one is available.","what":"OSV-2021-812 is a denial of service vulnerability in kryo, published on 29 May 2021."},"fix_prompt":"Check this codebase for OSV-2021-812 and fix it if it is affected.\n\nWhat it is: OSV-2021-812 is a denial of service vulnerability in kryo, published on 29 May 2021. \nExploitation: There is no known exploitation of OSV-2021-812 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- kryo (OSS-Fuzz): affected all versions; no fix listed\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/OSV-2021-812/ (Markdown: https://insights.sbomify.com/OSV-2021-812/index.md)","id":"OSV-2021-812","markdown":"https://insights.sbomify.com/OSV-2021-812/index.md","name":"OSV-2021-812","record":{"aliases":[],"analysis":{"component_type":"library","fix_type":"no_fix_stated","impacts":["denial_of_service"],"network_reachable":"unknown","non_default_config":false,"product_category":"Java serialization library","requires_auth":"none","summary":"An uncaught exception in Kryo's FieldSerializer can cause a denial of service when processing malformed serialized data.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=34733\n\n```\nCrash type: Uncaught exception\nCrash state:\ncom.esotericsoftware.kryo.serializers.FieldSerializer.read\ncom.esotericsoftware.kryo.Kryo.readObject\nDeserializeStringFuzzer.fuzzerTestOneInput\n```","ecosystems":["OSS-Fuzz"],"exploits":{"exploitdb":null,"first_seen":null,"github_poc":null,"max_poc_stars":null,"metasploit":null,"nuclei":null,"refs":[],"tier":null},"has_fix":false,"headline":"Uncaught exception in com.esotericsoftware.kryo.serializers.FieldSerializer.read","id":"OSV-2021-812","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"OSS-Fuzz","product":null,"products":[],"type":"denial_of_service","year":"2021"},"n_packages":1,"n_references":null,"packages":[{"ecosystem":"OSS-Fuzz","fixed":[],"introduced":[],"last_affected":[],"package":"kryo","purl":"pkg:generic/kryo","source":"OSV-2021-812"}],"products":null,"published":"2021-05-29","related":[],"sources":[{"class":"attribution","licence":"CC BY 4.0","name":"OSS-Fuzz","prefix":"OSV"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":null,"updated":null,"vendors":null},"summary":"An uncaught exception in Kryo's FieldSerializer can cause a denial of service when processing malformed serialized data.","url":"https://insights.sbomify.com/OSV-2021-812/"}