OSV-2024-114
Segv on unknown address in lj_BC_RET1
No scoreFix available
OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=66384
Crash type: Segv on unknown address
Crash state:
lj_BC_RET1
lua_pcall
luaL_loadbuffer_fuzzer.cc
What each source reports
OSV No score
Segv on unknown address in lj_BC_RET1
OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=66384
Crash type: Segv on unknown address
Crash state:
lj_BC_RET1
lua_pcall
luaL_loadbuffer_fuzzer.cc
- Record
OSV-2024-114- Updated
- 2026-11-02
Affected packages
| Package | Affected | Fixed |
|---|---|---|
tarantoolOSS-Fuzz |
Commit ranges | Not evaluated |
Not evaluated means the source gave git commits or a range we can't read, so we can't tell which releases are affected. A fixed version beside it is the source’s own claim.
History
| Recorded | Changed | Sources |
|---|---|---|
| first indexed | OSV |
Dates are when Every CVE recorded each change. Upstream dates may differ.
In short
OSV-2024-114 is a vulnerability with no CVSS score yet in tarantool, published February 17, 2024. No source lists public exploit code. A source reports a fix.