OSV-2020-2017 Heap-buffer-overflow in flb_msgpack_to_json
Not scored
Published
Check this codebase for OSV-2020-2017 and fix it if it is affected.
What it is: OSV-2020-2017 is a memory corruption vulnerability in fluent-bit, published on 12 Oct 2020.
Exploitation: There is no known exploitation of OSV-2020-2017 in the wild and no public exploit code.
Affected packages and fixed versions:
- fluent-bit (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-2020-2017/ (Markdown: https://insights.sbomify.com/OSV-2020-2017/index.md)
A heap-buffer-overflow in Fluent Bit's msgpack-to-JSON conversion allows attackers to cause crashes or potentially execute code via crafted input.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Not stated
- Victim action needed
- Not needed
- Fix
- None listed
What is OSV-2020-2017?
OSV-2020-2017 is a memory corruption vulnerability in fluent-bit, published on 12 Oct 2020.
Official description
OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=26248
Crash type: Heap-buffer-overflow WRITE 1
Crash state:
flb_msgpack_to_json
flb_msgpack_raw_to_json_sds
msgpack_parse_fuzzer.c
Which versions are affected by OSV-2020-2017?
1 open source package ship an affected version, including fluent-bit.
| Package | Affected | Fixed in |
|---|---|---|
fluent-bit OSS-Fuzz | All versions | None |
How do I fix OSV-2020-2017?
No fix has been published for OSV-2020-2017 yet. Limit exposure of the affected software until one is available.
Upgrade to the fixed version. Memory-safe languages, compiler hardening and fuzzing prevent most new cases. More about Memory corruption.
Is OSV-2020-2017 being exploited?
There is no known exploitation of OSV-2020-2017 in the wild and no public exploit code.