instance_id string | description string | exploit(poc)_url string | patch_url string | weakness_enumeration string | github_repo string | base_commit string | developers_patch string | bug_report string | sanitizer_report string | sanitizer string | github_issue string | nvd_url string | minimized_patch string |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
njs.cve-2022-32414 | Nginx NJS v0.7.2 was discovered to contain a segmentation violation in the function njs_vmcode_interpreter at src/njs_vmcode.c. | https://github.com/nginx/njs/issues/483 | https://github.com/nginx/njs/commit/31ed93a5623f24ca94e6d47e895ba735d9d97d46 | CWE-416 | nginx/njs | 31ed93a5623f24ca94e6d47e895ba735d9d97d46~1 | diff --git a/src/njs_promise.c b/src/njs_promise.c
index 52ae5b570..ea162d533 100644
--- a/src/njs_promise.c
+++ b/src/njs_promise.c
@@ -1369,6 +1369,10 @@ njs_promise_perform_all_handler(njs_vm_t *vm, njs_iterator_args_t *args,
njs_promise_all_context_t *context;
njs_promise_iterator_args_t *pargs;
+ ... | https://github.com/nginx/njs/issues/483 | AddressSanitizer:DEADLYSIGNAL
=================================================================
==732128==ERROR: AddressSanitizer: SEGV on unknown address (pc 0x0000004e3e53 bp 0x7ffe6e1f76b0 sp 0x7ffe6e1f6e80 T0)
==732128==The signal is caused by a READ memory access.
==732128==Hint: this fault was caused by a derefer... | === https://github.com/nginx/njs/issues/483 ===
Title: SEGV njs_vmcode.c:802:27 in njs_vmcode_interpreter
---
Body:
### Environment
```
OS : Linux ubuntu 5.13.0-27-generic #29~20.04.1-Ubuntu SMP Fri Jan 14 00:32:30 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
Commit : f65981b0b8fcf02d69a40bc934803c25c9f607ab
V... | https://nvd.nist.gov/vuln/detail/CVE-2022-32414 | ||
gpac.cve-2023-5586 | NULL Pointer Dereference in GitHub repository gpac/gpac prior to 2.3.0-DEV. | https://huntr.dev/bounties/d2a6ea71-3555-47a6-9b18-35455d103740 | https://github.com/gpac/gpac/commit/ca1b48f0abe71bf81a58995d7d75dc27f5a17ddc, https://huntr.dev/bounties/d2a6ea71-3555-47a6-9b18-35455d103740 | CWE-476 | gpac/gpac | 5692dc729491805e0e5f55c21d50ba1e6b19e88e | diff --git a/src/filters/reframe_rawpcm.c b/src/filters/reframe_rawpcm.c
index 37decc00e6..406c6638de 100644
--- a/src/filters/reframe_rawpcm.c
+++ b/src/filters/reframe_rawpcm.c
@@ -360,6 +360,14 @@ GF_Err pcmreframe_process(GF_Filter *filter)
}
wav_ok = GF_FALSE;
}
+ if (!ctx->ch) {
+ GF_LOG(GF_LOG_ERRO... | https://nvd.nist.gov/vuln/detail/CVE-2023-5586 | |||||
mruby.cve-2022-0240 | mruby is vulnerable to NULL Pointer Dereference | https://huntr.dev/bounties/5857eced-aad9-417d-864e-0bdf17226cbb | https://github.com/mruby/mruby/commit/31fa3304049fc406a201a72293cce140f0557dca | CWE-476 | mruby/mruby | 171d32c0071d776207174a40a8fa26def3dbb931 | diff --git a/src/class.c b/src/class.c
index ec9c648e5d..8751dcaf05 100644
--- a/src/class.c
+++ b/src/class.c
@@ -357,6 +357,7 @@ prepare_singleton_class(mrb_state *mrb, struct RBasic *o)
{
struct RClass *sc, *c;
+ mrb_assert(o->c);
if (o->c->tt == MRB_TT_SCLASS) return;
sc = MRB_OBJ_ALLOC(mrb, MRB_TT_SCL... | https://nvd.nist.gov/vuln/detail/CVE-2022-0240 | diff --git a/src/class.c b/src/class.c
index ec9c648e5d..8751dcaf05 100644
--- a/src/class.c
+++ b/src/class.c
@@ -357,6 +357,7 @@ prepare_singleton_class(mrb_state *mrb, struct RBasic *o)
{
struct RClass *sc, *c;
+ mrb_assert(o->c);
if (o->c->tt == MRB_TT_SCLASS) return;
sc = MRB_OBJ_ALLOC(mrb, MRB_TT_SCL... | ||||
njs.cve-2022-28049 | NGINX NJS 0.7.2 was discovered to contain a NULL pointer dereference via the component njs_vmcode_array at /src/njs_vmcode.c. | https://github.com/nginx/njs/issues/473 | https://github.com/nginx/njs/commit/f65981b0b8fcf02d69a40bc934803c25c9f607ab | CWE-476 | nginx/njs | f65981b0b8fcf02d69a40bc934803c25c9f607ab~1 | diff --git a/src/njs_vmcode.c b/src/njs_vmcode.c
index ef0beb5e0..ec478659c 100644
--- a/src/njs_vmcode.c
+++ b/src/njs_vmcode.c
@@ -1055,14 +1055,16 @@ njs_vmcode_array(njs_vm_t *vm, u_char *pc)
if (code->ctor) {
/* Array of the form [,,,], [1,,]. */
- value = array->start;
- ... | https://github.com/nginx/njs/issues/473 | INFO: Seed: 2125423890
INFO: Loaded 1 modules (53334 inline 8-bit counters): 53334 [0x95f010, 0x96c066),
INFO: Loaded 1 PC tables (53334 PCs): 53334 [0x96c068,0xa3c5c8),
/out/njs_process_script_fuzzer: Running 1 inputs 1 time(s) each.
Running: crashes/njs_njs_process_script_fuzzer/id:000002,sig:06,src:001260+005121... | === https://github.com/nginx/njs/issues/473 ===
Title: Null pointer dereference in src/njs_vmcode.c:1049:17
---
Body:
Hi,
this bug was found by fuzzing the current master branch, to reproduce build the OSS-Fuzz harness with ASan and UBSan.
The bug is a write to a NULL pointer, this is the sanitizer report:
```... | https://nvd.nist.gov/vuln/detail/CVE-2022-28049 | ||
njs.cve-2022-38890 | Nginx NJS v0.7.7 was discovered to contain a segmentation violation via njs_utf8_next at src/njs_utf8.h | https://github.com/nginx/njs/issues/569 | https://github.com/nginx/njs/commit/b9aea5854bcf6f2de8f7a7f1550874e392b94be2 | CWE-125 | nginx/njs | b9aea5854bcf6f2de8f7a7f1550874e392b94be2~1 | diff --git a/src/njs_string.c b/src/njs_string.c
index 83cede548..62bece0de 100644
--- a/src/njs_string.c
+++ b/src/njs_string.c
@@ -2849,6 +2849,7 @@ njs_string_trim(const njs_value_t *value, njs_string_prop_t *string,
for ( ;; ) {
if (start == prev) {
+ end = prev;
... | https://github.com/nginx/njs/issues/569 | AddressSanitizer:DEADLYSIGNAL
=================================================================
==1550478==ERROR: AddressSanitizer: SEGV on unknown address 0x6170bebedece (pc 0x000000505f0e bp 0x7fff88dc8f70 sp 0x7fff88dc8e40 T0)
==1550478==The signal is caused by a READ memory access.
#0 0x505f0e in njs_utf8_next ... | === https://github.com/nginx/njs/issues/569 ===
Title: Another way to trigger SEGV in njs_utf8_next cause oob read
---
Body:
the call stack is different with https://github.com/nginx/njs/issues/522
```
Environment
commit: 569292e0a74f2b1ec09566f3329f82bdd0d58e87
version: 0.7.7
Build :
./configure --cc=c... | https://nvd.nist.gov/vuln/detail/CVE-2022-38890 | ||
libredwg.cve-2020-21816 | A heab based buffer overflow issue exists in GNU LibreDWG 0.10.2641 via htmlescape ../../programs/escape.c:46. | https://github.com/LibreDWG/libredwg/issues/182#issuecomment-572890865 | https://github.com/LibreDWG/libredwg/commit/7e4c59b63d9c5b4b513cba1d0f33612042524563 | CWE-787 | LibreDWG/libredwg | 7b9cb829f93d1c1f67584345ed65ea830de8bdda | diff --git a/programs/escape.c b/programs/escape.c
index 8a907414e0..4d409ea43f 100644
--- a/programs/escape.c
+++ b/programs/escape.c
@@ -27,42 +27,74 @@ char * ATTRIBUTE_MALLOC
htmlescape (const char *restrict src, const int cp)
{
int len;
- char *dest, *d;
+ char *dest, *d, *end;
unsigned char *s;
if (!... | https://github.com/LibreDWG/libredwg/issues/182#issuecomment-572890865 | === https://github.com/LibreDWG/libredwg/issues/182#issuecomment-572890865 ===
Title: Several bugs found by fuzzing
---
Body:
Hi,
After fuzzing libredwg, I found the following bugs on the latest commit on master.
Command: ./dwg2SVG $PoC
**1.NULL pointer dereference in htmlescape ../../programs/escape.c:29**
POC: ... | https://nvd.nist.gov/vuln/detail/CVE-2020-21816 | diff --git a/programs/escape.c b/programs/escape.c
index 8a907414e0..4d409ea43f 100644
--- a/programs/escape.c
+++ b/programs/escape.c
@@ -27,42 +27,74 @@ char * ATTRIBUTE_MALLOC
htmlescape (const char *restrict src, const int cp)
{
int len;
- char *dest, *d;
+ char *dest, *d, *end;
unsigned char *s;
if (!... | ||
gpac.cve-2023-46929 | An issue discovered in GPAC 2.3-DEV-rev605-gfc9e29089-master in MP4Box in gf_avc_change_vui /afltest/gpac/src/media_tools/av_parsers.c:6872:55 allows attackers to crash the application. | https://github.com/gpac/gpac/issues/2662 | https://github.com/gpac/gpac/commit/4248def5d24325aeb0e35cacde3d56c9411816a6 | CWE-20 | gpac/gpac | 4248def5d24325aeb0e35cacde3d56c9411816a6~1 | diff --git a/src/media_tools/av_parsers.c b/src/media_tools/av_parsers.c
index 43c3200b90..84e6601b64 100644
--- a/src/media_tools/av_parsers.c
+++ b/src/media_tools/av_parsers.c
@@ -6865,6 +6865,9 @@ GF_Err gf_avc_change_vui(GF_AVCConfig *avcc, GF_VUIInfo *vui_info)
GF_AVCConfigSlot *slc;
orig = NULL;
+ if (!avc... | https://github.com/gpac/gpac/issues/2662 | AddressSanitizer:DEADLYSIGNAL
=================================================================
==3037856==ERROR: AddressSanitizer: SEGV on unknown address 0x000000000008 (pc 0x7ffff67d35c7 bp 0x7ffffffec090 sp 0x7ffffffe29c0 T0)
==3037856==The signal is caused by a READ memory access.
==3037856==Hint: address points t... | === https://github.com/gpac/gpac/issues/2662 ===
Title: SEGV in MP4Box in gf_avc_change_vui /afltest/gpac/src/media_tools/av_parsers.c:6872:55
---
Body:
# SEGV in MP4Box
### Description
SEGV in gpac/MP4Box.
#0 0x7ffff67d35c7 in gf_avc_change_vui /afltest/gpac/src/media_tools/av_parsers.c:6872:55
### Versi... | https://nvd.nist.gov/vuln/detail/CVE-2023-46929 | ||
gpac.cve-2024-0321 | Stack-based Buffer Overflow in GitHub repository gpac/gpac prior to 2.3-DEV. | https://huntr.com/bounties/4c027b94-8e9c-4c31-a169-893b25047769 | https://github.com/gpac/gpac/commit/d0ced41651b279bb054eb6390751e2d4eb84819a | CWE-121, CWE-787 | gpac/gpac | d0ced41651b279bb054eb6390751e2d4eb84819a~1 | diff --git a/src/filters/load_text.c b/src/filters/load_text.c
index 6373398228..877b285a80 100644
--- a/src/filters/load_text.c
+++ b/src/filters/load_text.c
@@ -377,6 +377,10 @@ char *gf_text_get_utf8_line(char *szLine, u32 lineSize, FILE *txt_in, s32 unicod
GF_LOG(GF_LOG_DEBUG, GF_LOG_PARSER, ("[TXTIn] Line too ... | https://nvd.nist.gov/vuln/detail/CVE-2024-0321 | |||||
libarchive.cve-2017-14503 | libarchive 3.3.2 suffers from an out-of-bounds read within lha_read_data_none() in archive_read_support_format_lha.c when extracting a specially crafted lha archive, related to lha_crc16. | https://github.com/libarchive/libarchive/commit/2c8c83b9731ff822fad6cc8c670ea5519c366a14 | CWE-125 | libarchive/libarchive | 2c8c83b9731ff822fad6cc8c670ea5519c366a14~1 | diff --git a/libarchive/archive_read_support_format_lha.c b/libarchive/archive_read_support_format_lha.c
index b8ef4ae10e..95c99bb1f3 100644
--- a/libarchive/archive_read_support_format_lha.c
+++ b/libarchive/archive_read_support_format_lha.c
@@ -701,6 +701,12 @@ archive_read_format_lha_read_header(struct archive_read ... | https://bugs.debian.org/875960, https://github.com/libarchive/libarchive/issues/948 | ==21722==ERROR: AddressSanitizer: heap-buffer-overflow on address 0x631000024800 at pc 0x56536be61878 bp 0x7fffa2254ec0 sp 0x7fffa2254eb8
READ of size 2 at 0x631000024800 thread T0
#0 0x56536be61877 in lha_crc16 libarchive/archive_read_support_format_lha.c:1740
#1 0x56536be5f791 in lha_read_data_none libarchive... | ASan (inferred) | === https://github.com/libarchive/libarchive/issues/948 ===
Title: out-of-bounds read in lha_read_data_none()
---
Body:
Hi
The following was reported downstream in Debian at https://bugs.debian.org/875960
The `oob.lha` base64 encoded is:
````
YQAtbGgwLQwAAAAMAAAAADs9SyACeJdNBwBh5AQAAAwAAWhlbGxvLnR4dBMAQv9zd... | https://nvd.nist.gov/vuln/detail/CVE-2017-14503 | ||
gpac.cve-2023-0760 | Heap-based Buffer Overflow in GitHub repository gpac/gpac prior to V2.1.0-DEV. | https://github.com/gpac/gpac/commit/ea7395f39f601a7750d48d606e9d10ea0b7beefe, https://huntr.dev/bounties/d06223df-a473-4c82-96d0-23726b844b21 | https://github.com/gpac/gpac/commit/ea7395f39f601a7750d48d606e9d10ea0b7beefe, https://huntr.dev/bounties/d06223df-a473-4c82-96d0-23726b844b21 | CWE-122, CWE-787 | gpac/gpac | ea7395f39f601a7750d48d606e9d10ea0b7beefe~1 | diff --git a/src/isomedia/box_code_base.c b/src/isomedia/box_code_base.c
index baf07ff352..9a9ad09b45 100644
--- a/src/isomedia/box_code_base.c
+++ b/src/isomedia/box_code_base.c
@@ -4429,7 +4429,7 @@ GF_Err video_sample_entry_box_size(GF_Box *s)
/*VVC*/
gf_isom_check_position(s, (GF_Box *)ptr->vvc_config, &pos);... | https://huntr.dev/bounties/d06223df-a473-4c82-96d0-23726b844b21 | https://nvd.nist.gov/vuln/detail/CVE-2023-0760 | diff --git a/src/isomedia/box_code_base.c b/src/isomedia/box_code_base.c
index baf07ff352..9a9ad09b45 100644
--- a/src/isomedia/box_code_base.c
+++ b/src/isomedia/box_code_base.c
@@ -9983,6 +9983,9 @@ static void *sgpd_parse_entry(u32 grouping_type, GF_BitStream *bs, s32 bytes_in_
}
return ptr;
}
+ case 0:
+ G... | |||
njs.cve-2022-31307 | Nginx NJS v0.7.2 was discovered to contain a segmentation violation in the function njs_string_offset at src/njs_string.c. | https://github.com/nginx/njs/issues/482 | https://github.com/nginx/njs/commit/eafe4c7a326b163612f10861392622b5da5b1792 | CWE-416 | nginx/njs | eafe4c7a326b163612f10861392622b5da5b1792~1 | diff --git a/src/njs_iterator.c b/src/njs_iterator.c
index 90c3046fb..043e4483c 100644
--- a/src/njs_iterator.c
+++ b/src/njs_iterator.c
@@ -560,11 +560,14 @@ njs_object_iterate_reverse(njs_vm_t *vm, njs_iterator_args_t *args,
} else {
/* UTF-8 string. */
- p = njs_string_offset(strin... | https://github.com/nginx/njs/issues/482 | AddressSanitizer:DEADLYSIGNAL
=================================================================
==732134==ERROR: AddressSanitizer: SEGV on unknown address (pc 0x0000004f44ab bp 0x7ffee1c1f9b0 sp 0x7ffee1c1f9b0 T0)
==732134==The signal is caused by a READ memory access.
==732134==Hint: this fault was caused by a derefer... | === https://github.com/nginx/njs/issues/482 ===
Title: SEGV njs_string.c:2535:18 in njs_string_offset
---
Body:
### Environment
```
OS : Linux ubuntu 5.13.0-27-generic #29~20.04.1-Ubuntu SMP Fri Jan 14 00:32:30 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
Commit : f65981b0b8fcf02d69a40bc934803c25c9f607ab
Versi... | https://nvd.nist.gov/vuln/detail/CVE-2022-31307 | ||
njs.cve-2021-46462 | njs through 0.7.1, used in NGINX, was discovered to contain a segmentation violation via njs_object_set_prototype in /src/njs_object.c. | https://github.com/nginx/njs/issues/449 | https://github.com/nginx/njs/commit/39e8fa1b7db1680654527f8fa0e9ee93b334ecba, https://github.com/nginx/njs/issues/449 | nginx/njs | 39e8fa1b7db1680654527f8fa0e9ee93b334ecba~1 | diff --git a/src/njs_function.c b/src/njs_function.c
index 0c23ca05c..ae0fa11ff 100644
--- a/src/njs_function.c
+++ b/src/njs_function.c
@@ -1385,18 +1385,10 @@ njs_function_prototype_apply(njs_vm_t *vm, njs_value_t *args, njs_uint_t nargs,
if (njs_is_null_or_undefined(arr_like)) {
length = 0;
-
- ... | https://github.com/nginx/njs/issues/449 | AddressSanitizer:DEADLYSIGNAL
=================================================================
==466519==ERROR: AddressSanitizer: SEGV on unknown address (pc 0x00000050d6d4 bp 0x7ffc8e2432f0 sp 0x7ffc8e2432e0 T0)
==466519==The signal is caused by a READ memory access.
==466519==Hint: this fault was caused by a derefer... | === https://github.com/nginx/njs/issues/449 ===
Title: SEGV /njs/src/njs_object.c:2136:24 in njs_object_set_prototype
---
Body:
## Env
```
Version : 0.7.0
Git Commit : 2da5d8b246b806bee6f74b575217ec3b61a25548
OS : Ubuntu 20.04
Configure : ./configure --address-sanitizer=YES
```
## POC
```
functio... | https://nvd.nist.gov/vuln/detail/CVE-2021-46462 | diff --git a/src/njs_function.c b/src/njs_function.c
index 0c23ca05c..ae0fa11ff 100644
--- a/src/njs_function.c
+++ b/src/njs_function.c
@@ -1385,18 +1385,10 @@ njs_function_prototype_apply(njs_vm_t *vm, njs_value_t *args, njs_uint_t nargs,
if (njs_is_null_or_undefined(arr_like)) {
length = 0;
-
- ... | ||
njs.cve-2022-29779 | Nginx NJS v0.7.2 was discovered to contain a segmentation violation in the function njs_value_own_enumerate at src/njs_value.c. | https://github.com/nginx/njs/issues/485 | https://github.com/nginx/njs/commit/2e00e95473861846aa8538be87db07699d9f676d | nginx/njs | 2e00e95473861846aa8538be87db07699d9f676d~1 | diff --git a/src/njs_array.c b/src/njs_array.c
index 0b8c7b919..2ceb6be7e 100644
--- a/src/njs_array.c
+++ b/src/njs_array.c
@@ -1284,6 +1284,11 @@ njs_array_prototype_splice(njs_vm_t *vm, njs_value_t *args, njs_uint_t nargs,
if (njs_slow_path(ret == NJS_ERROR)) {
return ret;
... | https://github.com/nginx/njs/issues/485 | AddressSanitizer:DEADLYSIGNAL
=================================================================
==2523460==ERROR: AddressSanitizer: SEGV on unknown address 0x000000000000 (pc 0x555b64452f1c bp 0x7ffdcdd97650 sp 0x7ffdcdd97520 T0)
==2523460==The signal is caused by a READ memory access.
==2523460==Hint: address points t... | === https://github.com/nginx/njs/issues/485 ===
Title: SEGV src/njs_value.c:240 in njs_value_own_enumerate
---
Body:
# Environment
OS : Linux leanderwang-LC2 5.13.0-30-generic https://github.com/nginx/njs/issues/33 SMP Mon Feb 7 14:25:10 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
Commit : https://github.com/nginx/njs/... | https://nvd.nist.gov/vuln/detail/CVE-2022-29779 | |||
njs.cve-2022-29369 | Nginx NJS v0.7.2 was discovered to contain a segmentation violation via njs_lvlhsh_bucket_find at njs_lvlhsh.c. | https://github.com/nginx/njs/commit/222d6fdcf0c6485ec8e175f3a7b70d650c234b4e | CWE-754 | nginx/njs | 222d6fdcf0c6485ec8e175f3a7b70d650c234b4e~1 | diff --git a/src/njs_vmcode.c b/src/njs_vmcode.c
index 0b07ec67e..6b10200ee 100644
--- a/src/njs_vmcode.c
+++ b/src/njs_vmcode.c
@@ -700,7 +700,7 @@ njs_vmcode_interpreter(njs_vm_t *vm, u_char *pc, void *promise_cap,
ret = njs_object_prop_define(vm, value1, &name, function,
... | https://github.com/nginx/njs/issues/467 | AddressSanitizer:DEADLYSIGNAL
=================================================================
==2064577==ERROR: AddressSanitizer: SEGV on unknown address (pc 0x0000004cac48 bp 0x7ffcc1edfbf0 sp 0x7ffcc1edfbb0 T0)
==2064577==The signal is caused by a READ memory access.
==2064577==Hint: this fault was caused by a dere... | === https://github.com/nginx/njs/issues/467 ===
Title: SEGV njs_lvlhsh.c:231:17 in njs_lvlhsh_bucket_find
---
Body:
### Environment
```
OS : Linux ubuntu 5.13.0-27-generic #29~20.04.1-Ubuntu SMP Fri Jan 14 00:32:30 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
Commit : 7bd570b39297d3d91902c93a624c89b08be7a6fe
V... | https://nvd.nist.gov/vuln/detail/CVE-2022-29369 | |||
mruby.cve-2022-1201 | NULL Pointer Dereference in mrb_vm_exec with super in GitHub repository mruby/mruby prior to 3.2. This vulnerability is capable of making the mruby interpreter crash, thus affecting the availability of the system. | https://huntr.dev/bounties/6f930add-c9d8-4870-ae56-d4bd8354703b | https://github.com/mruby/mruby/commit/00acae117da1b45b318dc36531a7b0021b8097ae | CWE-476 | mruby/mruby | 00acae117da1b45b318dc36531a7b0021b8097ae~1 | diff --git a/src/vm.c b/src/vm.c
index 77edbb38fc..3bb9510ec1 100644
--- a/src/vm.c
+++ b/src/vm.c
@@ -1749,7 +1749,7 @@ mrb_vm_exec(mrb_state *mrb, const struct RProc *proc, const mrb_code *pc)
}
else if (target_class->tt == MRB_TT_MODULE) {
target_class = mrb_vm_ci_target_class(ci);
- if... | https://nvd.nist.gov/vuln/detail/CVE-2022-1201 | |||||
faad2.cve-2018-20198 | A NULL pointer dereference was discovered in ifilter_bank of libfaad/filtbank.c in Freeware Advanced Audio Decoder 2 (FAAD2) 2.8.8. The vulnerability causes a segmentation fault and application crash, which leads to denial of service because adding to windowed output is mishandled in the LONG_START_SEQUENCE case. | https://github.com/fantasy7082/image_test/blob/master/002-null-point-filtbank_246 | https://github.com/knik0/faad2/commit/466b01d504d7e45f1e9169ac90b3e34ab94aed14 | CWE-476 | knik0/faad2 | 466b01d504d7e45f1e9169ac90b3e34ab94aed14~1 | diff --git a/libfaad/syntax.c b/libfaad/syntax.c
index f8e808c2..e7fb1138 100644
--- a/libfaad/syntax.c
+++ b/libfaad/syntax.c
@@ -344,6 +344,12 @@ static void decode_sce_lfe(NeAACDecStruct *hDecoder,
can become 2 when some form of Parametric Stereo coding is used
*/
+ if (hDecoder->frame && hDecoder-... | https://github.com/knik0/faad2/issues/23, https://seclists.org/bugtraq/2019/Sep/28 | ./faad faad_res/002-null-point-filtbank_246 -o out.wav
*********** Ahead Software MPEG-4 AAC Decoder V2.8.8 ******************
Build: Dec 13 2018
Copyright 2002-2004: Ahead Software AG
http://www.audiocoding.com
bug tracking: https://sourceforge.net/p/faac/bugs/
Floating point version
This program is free soft... | === https://github.com/knik0/faad2/issues/23 ===
Title: Null pointer dereference vulnerability in ifilter_bank(libfaad/filtbank.c:246)
---
Body:
Hi, i found a null pointer dereference bug in Freeware Advanced Audio Decoder 2 (FAAD2) 2.8.8. It crashed in function ifilter_bank.the details are below(ASAN):
```
./faa... | https://nvd.nist.gov/vuln/detail/CVE-2018-20198 | diff --git a/libfaad/syntax.c b/libfaad/syntax.c
index f8e808c2..e7fb1138 100644
--- a/libfaad/syntax.c
+++ b/libfaad/syntax.c
@@ -344,6 +344,12 @@ static void decode_sce_lfe(NeAACDecStruct *hDecoder,
can become 2 when some form of Parametric Stereo coding is used
*/
+ if (hDecoder->frame && hDecoder-... | |
mruby.cve-2022-1427 | Out-of-bounds Read in mrb_obj_is_kind_of in in GitHub repository mruby/mruby prior to 3.2. # Impact: Possible arbitrary code execution if being exploited. | https://huntr.dev/bounties/23b6f0a9-64f5-421e-a55f-b5b7a671f301 | https://github.com/mruby/mruby/commit/a4d97934d51cb88954cc49161dc1d151f64afb6b | CWE-125 | mruby/mruby | a4d97934d51cb88954cc49161dc1d151f64afb6b~1 | diff --git a/src/vm.c b/src/vm.c
index 5013c877d4..aa043b06ae 100644
--- a/src/vm.c
+++ b/src/vm.c
@@ -1750,10 +1750,7 @@ mrb_vm_exec(mrb_state *mrb, const struct RProc *proc, const mrb_code *pc)
mrb_exc_set(mrb, exc);
goto L_RAISE;
}
- if (target_class->flags & MRB_FL_CLASS_IS_PREPENDED) ... | ASan (inferred) | https://nvd.nist.gov/vuln/detail/CVE-2022-1427 | ||||
gpac.cve-2023-48013 | GPAC v2.3-DEV-rev566-g50c2ab06f-master was discovered to contain a double free via the gf_filterpacket_del function at /gpac/src/filter_core/filter.c. | https://github.com/gpac/gpac/issues/2612 | https://github.com/gpac/gpac/commit/cd8a95c1efb8f5bfc950b86c2ef77b4c76f6b893 | CWE-415 | gpac/gpac | cd8a95c1efb8f5bfc950b86c2ef77b4c76f6b893~1 | diff --git a/src/filters/isoffin_read_ch.c b/src/filters/isoffin_read_ch.c
index bd96400689..6e74ce8e3f 100644
--- a/src/filters/isoffin_read_ch.c
+++ b/src/filters/isoffin_read_ch.c
@@ -395,6 +395,8 @@ void isor_reader_get_sample(ISOMChannel *ch)
if (ch->edit_sync_frame) {
ch->edit_sync_frame++;
if (ch->... | https://github.com/gpac/gpac/issues/2612 | ==827317==ERROR: AddressSanitizer: attempting double-free on 0x619000015980 in thread T0:
#0 0x55e7797a5972 in free (/home/user/fuzzing_gpac/gpac/bin/gcc/MP4Box+0x105972) (BuildId: 53333ca7bff59dd9a3d1b2821e7c5f3a9aac76b9)
#1 0x7f525cd97945 in gf_filterpacket_del /home/user/fuzzing_gpac/gpac/src/filter_core/fil... | === https://github.com/gpac/gpac/issues/2612 ===
Title: double-free in gf_filterpacket_del /home/user/fuzzing_gpac/gpac/src/filter_core/filter.c:38:17
---
Body:
# Version
```
$ ./MP4Box -version
MP4Box - GPAC version 2.3-DEV-rev566-g50c2ab06f-master
```
# Platform
```
$ uname -a
Linux user-GE40-2PC-Dragon-E... | https://nvd.nist.gov/vuln/detail/CVE-2023-48013 | diff --git a/src/filters/isoffin_read_ch.c b/src/filters/isoffin_read_ch.c
index bd96400689..6e74ce8e3f 100644
--- a/src/filters/isoffin_read_ch.c
+++ b/src/filters/isoffin_read_ch.c
@@ -395,6 +395,8 @@ void isor_reader_get_sample(ISOMChannel *ch)
if (ch->edit_sync_frame) {
ch->edit_sync_frame++;
if (ch->... | |
gpac.cve-2023-48011 | GPAC v2.3-DEV-rev566-g50c2ab06f-master was discovered to contain a heap-use-after-free via the flush_ref_samples function at /gpac/src/isomedia/movie_fragments.c. | https://github.com/gpac/gpac/issues/2611 | https://github.com/gpac/gpac/commit/c70f49dda4946d6db6aa55588f6a756b76bd84ea | CWE-416 | gpac/gpac | c70f49dda4946d6db6aa55588f6a756b76bd84ea~1 | diff --git a/src/isomedia/movie_fragments.c b/src/isomedia/movie_fragments.c
index b7f7ade327..d665eeb9d0 100644
--- a/src/isomedia/movie_fragments.c
+++ b/src/isomedia/movie_fragments.c
@@ -591,6 +591,7 @@ u32 UpdateRuns(GF_ISOFile *movie, GF_TrackFragmentBox *traf)
while (gf_list_count(traf->TrackRuns)) {
trun... | https://github.com/gpac/gpac/issues/2611 | ==836900==ERROR: AddressSanitizer: heap-use-after-free on address 0x60b000001d88 at pc 0x7f57c0120bf1 bp 0x7ffeac405a70 sp 0x7ffeac405a68
READ of size 8 at 0x60b000001d88 thread T0
#0 0x7f57c0120bf0 in flush_ref_samples /home/user/fuzzing_gpac/gpac/src/isomedia/movie_fragments.c:936:37
#1 0x7f57c0128df2 in gf_i... | ASan (inferred) | === https://github.com/gpac/gpac/issues/2611 ===
Title: heap-use-after-free in ./gpac/src/isomedia/movie_fragments.c:936:37 in flush_ref_samples
---
Body:
# Version
```
$ ./MP4Box -version
MP4Box - GPAC version 2.3-DEV-rev566-g50c2ab06f-master
```
# Platform
```
$ uname -a
Linux user-GE40-2PC-Dragon-Eyes 6.... | https://nvd.nist.gov/vuln/detail/CVE-2023-48011 | diff --git a/src/isomedia/movie_fragments.c b/src/isomedia/movie_fragments.c
index b7f7ade327..d665eeb9d0 100644
--- a/src/isomedia/movie_fragments.c
+++ b/src/isomedia/movie_fragments.c
@@ -591,6 +591,7 @@ u32 UpdateRuns(GF_ISOFile *movie, GF_TrackFragmentBox *traf)
while (gf_list_count(traf->TrackRuns)) {
trun... |
libredwg.cve-2021-28237 | LibreDWG v0.12.3 was discovered to contain a heap-buffer overflow via decode_preR13. | https://github.com/LibreDWG/libredwg/issues/325 | https://github.com/LibreDWG/libredwg/commit/ea0b9522f63d049ded2c3cff8d9a8c360119951c | CWE-787 | LibreDWG/libredwg | ea0b9522f63d049ded2c3cff8d9a8c360119951c~1 | diff --git a/src/decode.c b/src/decode.c
index 444775afd1..79134db0b3 100644
--- a/src/decode.c
+++ b/src/decode.c
@@ -329,19 +329,20 @@ decode_preR13_section (Dwg_Section_Type_r11 id, Bit_Chain *restrict dat,
// TODO: move to a spec dwg_r11.spec, and dwg_decode_r11_NAME
#define PREP_TABLE(token) ... | https://github.com/LibreDWG/libredwg/issues/325 | ➜ ./dwgread ./poc
ERROR: This version of LibreDWG is only capable of decoding version r13-r2018 (code: AC1012-AC1032) DWG files.
We don't decode many entities and no blocks yet.
ERROR: offset -39
ERROR: offset -85
=================================================================
==12538==ERROR: AddressSanitizer: heap-... | === https://github.com/LibreDWG/libredwg/issues/325 ===
Title: Heap-buffer-overflow in decode_preR13 line 470
---
Body:
I found a heap buffer overflow in the current master (8072563).
# Configure
CFLAGS="-g -fsanitize=address" LDFLAGS="-fsanitize=address" ./configure
# Command
`./dwgread ./poc`
# ASAN repo... | https://nvd.nist.gov/vuln/detail/CVE-2021-28237 | ||
mruby.cve-2022-0631 | Heap-based Buffer Overflow in Homebrew mruby prior to 3.2. | https://huntr.dev/bounties/9bdc49ca-6697-4adc-a785-081e1961bf40 | https://github.com/mruby/mruby/commit/47068ae07a5fa3aa9a1879cdfe98a9ce0f339299, https://huntr.dev/bounties/9bdc49ca-6697-4adc-a785-081e1961bf40 | CWE-122 | mruby/mruby | 47068ae07a5fa3aa9a1879cdfe98a9ce0f339299~1 | diff --git a/src/vm.c b/src/vm.c
index 9cb50847f2..aa5569503e 100644
--- a/src/vm.c
+++ b/src/vm.c
@@ -689,9 +689,11 @@ mrb_f_send(mrb_state *mrb, mrb_value self)
regs = mrb->c->ci->stack+1;
if (n == 0) {
+ argnum_error:
mrb_argnum_error(mrb, 0, 1, -1);
}
else if (n == 15) {
+ if (RARRAY_LEN(regs... | https://nvd.nist.gov/vuln/detail/CVE-2022-0631 | |||||
mruby.cve-2022-1934 | Use After Free in GitHub repository mruby/mruby prior to 3.2. | https://huntr.dev/bounties/99e6df06-b9f7-4c53-a722-6bb89fbfb51f | https://github.com/mruby/mruby/commit/aa7f98dedb68d735a1665d3a289036c88b0c47ce, https://huntr.dev/bounties/99e6df06-b9f7-4c53-a722-6bb89fbfb51f | CWE-416 | mruby/mruby | aa7f98dedb68d735a1665d3a289036c88b0c47ce~1 | diff --git a/src/vm.c b/src/vm.c
index b04c9d7e58..09e557dc8e 100644
--- a/src/vm.c
+++ b/src/vm.c
@@ -1159,18 +1159,20 @@ check_target_class(mrb_state *mrb)
return target;
}
+#define regs (mrb->c->ci->stack)
+
static mrb_value
-hash_new_from_values(mrb_state *mrb, mrb_int argc, mrb_value *regs)
+hash_new_from_r... | https://nvd.nist.gov/vuln/detail/CVE-2022-1934 | |||||
njs.cve-2022-34029 | Nginx NJS v0.7.4 was discovered to contain an out-of-bounds read via njs_scope_value at njs_scope.h. | https://github.com/nginx/njs/issues/506 | https://github.com/nginx/njs/commit/d09868bc71f9a990445959329ad8c1b10d3898f5 | CWE-125 | nginx/njs | d09868bc71f9a990445959329ad8c1b10d3898f5~1 | diff --git a/src/njs_vmcode.c b/src/njs_vmcode.c
index 9833ada03..cc33d20b2 100644
--- a/src/njs_vmcode.c
+++ b/src/njs_vmcode.c
@@ -856,9 +856,15 @@ njs_vmcode_interpreter(njs_vm_t *vm, u_char *pc, void *promise_cap,
case NJS_VMCODE_AWAIT:
await = (njs_vmcode_await_t *) pc;
+ ... | https://github.com/nginx/njs/issues/506 | AddressSanitizer:DEADLYSIGNAL
=================================================================
==815==ERROR: AddressSanitizer: SEGV on unknown address 0x000000000040 (pc 0x0000004ff20b bp 0x7ffc7abf6030 sp 0x7ffc7abf5880 T0)
==815==The signal is caused by a READ memory access.
==815==Hint: address points to the zero p... | ASan (inferred) | === https://github.com/nginx/njs/issues/506 ===
Title: SEGV njs_scope.h:74:12 Out-of-bounds Read in njs_scope_value
---
Body:
Environment
```OS : Linux ubuntu 5.13.0-27-generic #29~20.04.1-Ubuntu SMP Fri Jan 14 00:32:30 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
Commit : 9f4ebc96148308a8ce12f2b54432c87e6d78b881
... | https://nvd.nist.gov/vuln/detail/CVE-2022-34029 | diff --git a/src/njs_vmcode.c b/src/njs_vmcode.c
index 9833ada03..cc33d20b2 100644
--- a/src/njs_vmcode.c
+++ b/src/njs_vmcode.c
@@ -856,9 +856,15 @@ njs_vmcode_interpreter(njs_vm_t *vm, u_char *pc, void *promise_cap,
case NJS_VMCODE_AWAIT:
await = (njs_vmcode_await_t *) pc;
+ ... |
libarchive.cve-2019-11463 | A memory leak in archive_read_format_zip_cleanup in archive_read_support_format_zip.c in libarchive 3.3.4-dev allows remote attackers to cause a denial of service via a crafted ZIP file because of a HAVE_LZMA_H typo. NOTE: this only affects users who downloaded the development code from GitHub. Users of the product's o... | https://github.com/libarchive/libarchive/issues/1165 | https://github.com/libarchive/libarchive/commit/ba641f73f3d758d9032b3f0e5597a9c6e593a505 | CWE-401 | libarchive/libarchive | ba641f73f3d758d9032b3f0e5597a9c6e593a505~1 | diff --git a/libarchive/archive_read_support_format_zip.c b/libarchive/archive_read_support_format_zip.c
index 677c437095..6937969c16 100644
--- a/libarchive/archive_read_support_format_zip.c
+++ b/libarchive/archive_read_support_format_zip.c
@@ -2751,7 +2751,7 @@ archive_read_format_zip_cleanup(struct archive_read *a)... | https://github.com/libarchive/libarchive/issues/1165 | ==15753==ERROR: LeakSanitizer: detected memory leaks
Direct leak of 96 byte(s) in 1 object(s) allocated from:
#0 0x7f4c0b1dfb50 in __interceptor_malloc (/usr/lib/x86_64-linux-gnu/libasan.so.4+0xdeb50)
#1 0x7f4c0a85dced (/lib/x86_64-linux-gnu/liblzma.so.5+0x2ced)
Indirect leak of 224 byte(s) in 1 object(s) al... | === https://github.com/libarchive/libarchive/issues/1165 ===
Title: Memory leak when decoding LZMA
---
Body:
I've encountered a memory leak while fuzzing libarchive. A 32-byte reproducer input is attached:
[input.zip](https://github.com/libarchive/libarchive/files/3019394/input.zip). Do not extract this zip file -- ... | https://nvd.nist.gov/vuln/detail/CVE-2019-11463 | ||
mruby.cve-2022-0614 | Use of Out-of-range Pointer Offset in Homebrew mruby prior to 3.2. | https://huntr.dev/bounties/a980ce4d-c359-4425-92c4-e844c0055879 | https://github.com/mruby/mruby/commit/ff3a5ebed6ffbe3e70481531cfb969b497aa73ad, https://huntr.dev/bounties/a980ce4d-c359-4425-92c4-e844c0055879 | CWE-119, CWE-823 | mruby/mruby | ff3a5ebed6ffbe3e70481531cfb969b497aa73ad~1 | diff --git a/src/vm.c b/src/vm.c
index 6133cbccac..9cb50847f2 100644
--- a/src/vm.c
+++ b/src/vm.c
@@ -2766,7 +2766,7 @@ mrb_vm_exec(mrb_state *mrb, const struct RProc *proc, const mrb_code *pc)
int lim = a+b*2+1;
hash = regs[a];
- mrb_assert(mrb_hash_p(hash));
+ mrb_ensure_hash_type(mrb, hash... | https://nvd.nist.gov/vuln/detail/CVE-2022-0614 | |||||
faad2.cve-2018-20194 | There is a stack-based buffer underflow in the third instance of the calculate_gain function in libfaad/sbr_hfadj.c in Freeware Advanced Audio Decoder 2 (FAAD2) 2.8.8. A crafted input will lead to a denial of service or possibly unspecified other impact because limiting the additional noise energy level is mishandled f... | https://github.com/knik0/faad2/issues/21 | https://github.com/hlef/faad2/commit/6b4a7cde30f2e2cb03e78ef476cc73179cfffda3 | CWE-787 | hlef/faad2 | 5d380279cb00ea7a8b24f647f3790a1fc5342731 | diff --git a/libfaad/sbr_hfadj.c b/libfaad/sbr_hfadj.c
index 3f310b81..dda1ce8e 100644
--- a/libfaad/sbr_hfadj.c
+++ b/libfaad/sbr_hfadj.c
@@ -485,6 +485,12 @@ static void calculate_gain(sbr_info *sbr, sbr_hfadj_info *adj, uint8_t ch)
ml1 = sbr->f_table_lim[sbr->bs_limiter_bands][k];
ml2 = sbr... | https://github.com/knik0/faad2/issues/21, https://seclists.org/bugtraq/2019/Sep/28 | ./faad faad_res/015-stack-buffer-underflow-sbr_hfadj_1314 -o out.wav
*********** Ahead Software MPEG-4 AAC Decoder V2.8.8 ******************
Build: Dec 13 2018
Copyright 2002-2004: Ahead Software AG
http://www.audiocoding.com
bug tracking: https://sourceforge.net/p/faac/bugs/
Floating point version
This progra... | === https://github.com/knik0/faad2/issues/21 ===
Title: stack-buffer-underflow in function calculate_gain(libfaad/sbr_hfadj.c:1314)
---
Body:
Hi, i found a stack-buffer-overflow bug in Freeware Advanced Audio Decoder 2 (FAAD2) 2.8.8, the details are below(ASAN):
```
./faad faad_res/015-stack-buffer-underflow-sb... | https://nvd.nist.gov/vuln/detail/CVE-2018-20194 | diff --git a/libfaad/sbr_hfadj.c b/libfaad/sbr_hfadj.c
index 3f310b81..dda1ce8e 100644
--- a/libfaad/sbr_hfadj.c
+++ b/libfaad/sbr_hfadj.c
@@ -485,6 +485,12 @@ static void calculate_gain(sbr_info *sbr, sbr_hfadj_info *adj, uint8_t ch)
ml1 = sbr->f_table_lim[sbr->bs_limiter_bands][k];
ml2 = sbr... | |
gpac.cve-2023-4721 | Out-of-bounds Read in GitHub repository gpac/gpac prior to 2.3-DEV. | https://huntr.dev/bounties/f457dc62-3cff-47bd-8fd2-1cb2b4a832fc | https://github.com/gpac/gpac/commit/3ec93d73d048ed7b46fe6e9f307cc7a0cc13db63, https://huntr.dev/bounties/f457dc62-3cff-47bd-8fd2-1cb2b4a832fc | CWE-125 | gpac/gpac | 3ec93d73d048ed7b46fe6e9f307cc7a0cc13db63~1 | diff --git a/src/media_tools/mpeg2_ps.c b/src/media_tools/mpeg2_ps.c
index 0af7a31f32..b0182f2249 100644
--- a/src/media_tools/mpeg2_ps.c
+++ b/src/media_tools/mpeg2_ps.c
@@ -266,6 +266,8 @@ int MPEG12_ParseSeqHdr(unsigned char *pbuffer, u32 buflen, s32 *have_mpeg2, u32
u32 scode, ix;
s32 found = -1;
*have_mpeg2 ... | ASan (inferred) | https://nvd.nist.gov/vuln/detail/CVE-2023-4721 | ||||
gpac.cve-2022-3178 | Buffer Over-read in GitHub repository gpac/gpac prior to 2.1.0-DEV. | https://huntr.dev/bounties/f022fc50-3dfd-450a-ab47-3d75d2bf44c0 | https://github.com/gpac/gpac/commit/77510778516803b7f7402d7423c6d6bef50254c3, https://huntr.dev/bounties/f022fc50-3dfd-450a-ab47-3d75d2bf44c0 | CWE-125, CWE-126 | gpac/gpac | 77510778516803b7f7402d7423c6d6bef50254c3~1 | diff --git a/src/isomedia/box_code_base.c b/src/isomedia/box_code_base.c
index 3cf6b3bd38..b7ee3e356e 100644
--- a/src/isomedia/box_code_base.c
+++ b/src/isomedia/box_code_base.c
@@ -12886,11 +12886,12 @@ GF_Err xtra_box_read(GF_Box *s, GF_BitStream *bs)
prop_type = gf_bs_read_u16(bs);
prop_size -= 6;
ISOM_... | https://nvd.nist.gov/vuln/detail/CVE-2022-3178 |
Hardened SEC-Bench
Developer security-patch verification for CVE_NVD instances evaluated in SEC-bench images.
The default configuration preserves the 200 source CVE_NVD rows.
The verified configuration currently contains 18 manually verified instances, their patch variants, test results, root-cause analyses and supporting evidence.
All published developer patches resolve their original dataset PoC under the recorded sanitizer checks.
Three instances have confirmed semantic findings and an adopted root-cause reference patch; one additional flagged finding was dismissed under the cross-CVE rule.
The reviewed findings and named inputs are documented separately from the PoC result.
Configurations and use
| Configuration | Split | Rows | Contents |
|---|---|---|---|
default |
train |
200 | Unmodified CVE_NVD source rows and original minimized patches. |
verified |
train |
18 | Source fields plus verification labels, retained patch variants and evidence; minimized_patch uses the verification result. |
from datasets import load_dataset
verified = load_dataset(
"shawnnnliu/Hardened_SEC-Bench", "verified", split="train"
)
instance = next(
row for row in verified if row["instance_id"] == "mruby.cve-2022-1276"
)
for case in instance["post_dev_failing_inputs"]:
if case["classification"] == "root_cause":
print(case["case_id"], case["outcome"], case["expected"], case["observed"])
Use "default" instead of "verified" to load the source configuration.
For reproducible experiments, pass the dataset commit hash as revision= when calling load_dataset.
See the Hugging Face loading documentation for loading options.
Dataset Fields
Fields shared by both configurations
The following 14 fields come from CVE_NVD.
Only minimized_patch changes meaning in the verified configuration; its original value is preserved in cve_nvd_minimized_patch.
| Field | Type | Description |
|---|---|---|
instance_id |
string | Instance identifier shared with CVE_NVD and SEC-bench, such as mruby.cve-2022-1276. |
description |
string | CVE description from the source CVE_NVD row. |
exploit(poc)_url |
string | Source URL of the exploit or proof of concept. |
patch_url |
string | Source URL of the developer fix commit. |
weakness_enumeration |
string | Source weakness classification, including the CWE identifier where supplied. |
github_repo |
string | Upstream GitHub repository in owner/repository form. |
base_commit |
string | Pre-patch commit recorded by CVE_NVD; container_commit records the commit actually tested. |
developers_patch |
string | Full developer-patch diff, retained byte-identical to CVE_NVD in both configurations. |
bug_report |
string | Source bug-report text. |
sanitizer_report |
string | Source sanitizer report used to check reproduction and crash frames. |
sanitizer |
string | Source sanitizer designation. |
github_issue |
string | Source GitHub issue text. |
nvd_url |
string | Source National Vulnerability Database entry URL. |
minimized_patch |
string | In default, the source CVE_NVD value; in verified, the patch retained after verification and reduction, or null when no reduction is kept. |
Additional fields in verified
The verified table has 43 columns in total.
Scalar text fields may be null when no value or patch is retained.
post_dev_failing_inputs is a list of records rather than a text field.
| Field | Type | Description |
|---|---|---|
cve_nvd_minimized_patch |
string | Original CVE_NVD minimized_patch, retained unchanged for provenance. |
verification_status |
string | Verification state; all currently published rows are verified. |
verified_at |
string | UTC timestamp of the verification record; review dates are recorded separately in semantic_status. |
image_digest |
string | SEC-bench evaluation-image reference pinned by digest. |
container_commit |
string | Commit actually checked out in the evaluation image; disagreements with base_commit are documented in the note. |
host_arch |
string | Host architecture and emulation information. |
poc_crashed_before |
boolean | Whether the original dataset PoC produced a sanitizer report before the developer patch. |
poc_crashed_after |
boolean | Whether the original dataset PoC produced a sanitizer report after the developer patch. |
poc_resolved |
boolean | Whether the original dataset PoC is resolved under the published PoC-based label; this can remain true when another input gives a wrong result or sanitizer report. |
semantic_flag |
boolean | Whether a semantic finding was flagged for human review; true includes findings later dismissed, so read semantic_status as well. |
semantic_status |
string | Review state and explanation: not flagged, flagged, not reviewed, confirmed <date>, or dismissed <date>. |
semantic_reasoning |
string | Consequence after the patch, scope decision, and supporting case names, logs and upstream evidence. |
dev_patch_fixes_root_cause |
boolean | Evidence-based assessment of whether the developer patch restores the stated invariant; the reviewed scope and reference-patch decision also depend on semantic_status. |
root_cause |
string | The violated invariant and mechanism behind the reported failure. |
regression_tests |
string | Comparison of project test-suite results before and after the developer patch, including granularity and deviations. |
developers_patch_sha256 |
string | SHA-256 of the developer-patch text stored in this dataset. |
minimized_patch_sha256 |
string | SHA-256 of the retained minimal patch, or null when none is kept. |
minimized_patch_derivation |
string | Reduction method and retained changed lines, or the reason no minimal patch is kept. |
minimized_patch_tests |
string | Validation of the retained minimal patch, or null when none is kept. |
second_reading |
string | Agreement and disagreement from the independent reading, with protocol deviations where applicable. |
root_patch |
string | Root-cause patch diff where one is kept; consult root_patch_source and root_patch_status before using it. |
root_patch_sha256 |
string | SHA-256 of the retained root-cause patch, or null. |
root_patch_source |
string | synthetic, backport:<commit>, or another recorded upstream provenance; null when no root patch is kept. |
root_patch_status |
string | Adoption or review status of the root patch, including whether it is the reference patch for downstream tasks. |
residual |
string | Other defects documented during verification and their scope decisions; see the note for the evidence. |
confidence |
string | High, medium or low, with the reason and any scope uncertainty. |
note |
string | Verification remarks, dataset disagreements and deviations. |
evidence |
string | Repository-relative paths of the per-instance note, logs and full verification record. |
post_dev_failing_inputs |
list of records | Named failing-input records after the developer patch; populated for the four instances with dev_patch_fixes_root_cause false and detailed below. |
Structure of post_dev_failing_inputs
The column contains 352 named evidence entries across four instances: 347 with program text and 5 with a report reference only.
It combines the retained main case sets, additional large-array and residual case sets, and second-reading validation catalogs for the instances whose dev_patch_fixes_root_cause is false.
| Entry field | Type | Meaning |
|---|---|---|
case_id |
string | Case-set-qualified name, such as main/kw_n0 or second_reading/c4big. |
input |
string | Program text, retained directly or expanded from the published generator; empty for report_only. |
input_path |
string | Relative path to a retained program or the report describing it; may be empty for generated cases. |
generator |
string | Relative path to the case generator, where applicable; otherwise empty. |
source_status |
string | program when program text is available, or report_only when only a named observation and report were retained. |
expected |
string | Reference behavior or output from the case oracle. |
observed |
string | Behavior or output recorded after applying the developer patch. |
outcome |
string | WRONG for a reference mismatch or ASAN for a sanitizer report. |
classification |
string | The root-defect, residual, mixed, cross-CVE or unassigned scope classification below. |
evidence |
string | Relative path to the developer-build case log supporting the observation. |
| Classification | Meaning |
|---|---|
root_cause |
Failure attributed to the root defect recorded for this instance. |
residual |
A separately documented defect outside the reported failure. |
mixed_root_cause_and_residual |
An input requiring both the root-defect repair and an independent residual repair. |
cross_cve:mruby.cve-2022-1427 |
Remaining crash counted under mruby.cve-2022-1427, consistent with dismissal of the mruby.cve-2022-1201 flag. |
other_observed_failure |
An oracle mismatch retained without assigning a new scope verdict. |
| Instance | Named entries | Classification counts |
|---|---|---|
| njs.cve-2022-31306 | 18 | 18 root_cause |
| mruby.cve-2022-1276 | 119 | 66 root_cause; 53 residual |
| mruby.cve-2022-1201 | 133 | 121 cross_cve:mruby.cve-2022-1427; 12 residual |
| mruby.cve-2022-0240 | 82 | 35 root_cause; 16 residual; 30 other_observed_failure; 1 mixed_root_cause_and_residual |
An empty list means this column does not catalogue the instance; it does not establish the absence of residual defects.
Counts refer to named evidence entries, not unique program texts, because a program may occur in multiple case sets.
The inventory covers recorded tests rather than every possible input.
For mruby.cve-2022-1201, wrong-result comparisons cover programs for which CRuby returns a value; differences in controlled exception classes are not added as wrong-result claims.
Exception-message differences classified OKc by the existing oracle are excluded.
Five njs.cve-2022-31306 second-reading entries (c4obs, c4big, c5obs, p_dup and p_dup2) have no retained program file and are marked report_only; their available descriptions are in the second-reading report.
The column is derived by scripts/post_dev_failing_inputs.py from published evidence without rerunning builds or cases.
Interpreting the labels and choosing a patch
poc_resolved is the headline outcome for the original dataset PoC.
The published records use the PoC-based reading: true means that PoC no longer produces a sanitizer report after the developer patch.
It does not require all additional inputs to be free of wrong results or sanitizer reports.
Use post_dev_failing_inputs, semantic_reasoning and the note to inspect those outcomes.
semantic_flag records that a finding was raised for review.
Its boolean value stays true if the finding is later dismissed, so semantic_status determines whether the finding is confirmed or dismissed.
Likewise, dev_patch_fixes_root_cause: false is retained as evidence even when a reviewed leftover is counted under another CVE.
Defects wholly covered by another instance's reported failure and developer patch are counted under that instance, as for mruby.cve-2022-1201 and mruby.cve-2022-1427.
Where root_patch_status records adoption as the reference patch for downstream tasks, use root_patch for that purpose.
This currently applies to mruby.cve-2022-1276, mruby.cve-2022-0240 and njs.cve-2022-31306.
For the remaining published instances, the developer patch is the reference patch.
developers_patch always remains the original dataset patch; minimized_patch is a separately validated reduction and cve_nvd_minimized_patch preserves the upstream dataset's candidate reduction.
For the dismissed mruby.cve-2022-1201 finding, the developer patch remains the reference and the withdrawn combined patch is retained only as historical variant evidence.
Verified instances
| Instance | PoC before / after | Regression tests | semantic_flag |
Minimal patch | Second reading | Inputs failing after developer patch |
|---|---|---|---|---|---|---|
| njs.cve-2022-31307 | report / none | identical to baseline | false | 6 of 12 changed lines | done | not catalogued |
| njs.cve-2023-27727 | report / none | identical to baseline | false | 6 of 25 changed lines | done | not catalogued |
| mruby.cve-2022-1934 | report / none | identical to baseline | false | none kept (13 changed lines) | done | not catalogued |
| njs.cve-2022-32414 | report / none | identical to baseline | false | none kept (23 changed lines) | done | not catalogued |
| njs.cve-2022-28049 | report / none | identical to baseline | false (noted for review) | none kept (22 changed lines) | done, dissent recorded | not catalogued |
| njs.cve-2021-46462 | report / none | identical to baseline | false (noted for review) | 12 of 21 changed lines | done | not catalogued |
| njs.cve-2022-34029 | report / none | identical to baseline | false (noted for review) | 8 of 31 changed lines | done | not catalogued |
| libredwg.cve-2020-21816 | report / none | identical to baseline | false (noted for review) | 10 of 58 changed lines | done, dissent recorded | not catalogued |
| njs.cve-2022-31306 | report / none | identical to baseline | true (confirmed 2026-10-28) | none kept (14 changed lines) | done | 18 root defect |
| mruby.cve-2022-1276 | report / none | identical to baseline | true (confirmed 2026-10-28 as wrong result only) | none kept (2 changed lines) | done | 66 root defect; 53 residual |
| mruby.cve-2022-1201 | report / none | identical to baseline | true (dismissed 2026-10-28) | none kept (2 changed lines) | done | 121 counted under mruby.cve-2022-1427; 12 residual |
| gpac.cve-2023-5586 | report / none | identical to baseline | false (noted for review) | none kept (8 changed lines) | done | not catalogued |
| mruby.cve-2022-0240 | report / none | identical to baseline | true (confirmed 2026-10-28) | none kept (2 changed lines) | done | 35 root defect; 16 residual; 30 other observed failure, scope not assigned; 1 mixed root defect and residual |
| njs.cve-2022-29779 | report / none | identical to baseline | false (noted for review) | none kept (14 changed lines) | done | not catalogued |
| njs.cve-2022-43284 | report / none | identical to baseline | false | 4 of 10 changed lines | done | not catalogued |
| mruby.cve-2022-0631 | report / none | identical to baseline | false | none kept (2 changed lines) | done | not catalogued |
| libredwg.cve-2020-21814 | report / none | identical to baseline | false | 10 of 12 changed lines | done | not catalogued |
| mruby.cve-2022-1427 | report / none | identical to baseline | false | none kept (5 changed lines) | done | not catalogued |
The table is derived from the verification records and the failing-input inventory.
"PoC before / after" reports sanitizer evidence on the base and developer-patch builds.
"identical to baseline" describes the recorded project-test comparison; developer-added tests are accounted for separately in the supporting logs.
"noted for review" is a scope caveat explained in semantic_reasoning and residual.
All 18 developer patches are byte-identical to CVE_NVD; patch hashes and upstream references are in the full results.jsonl records.
Verification method
Each instance was evaluated in its SEC-bench x86_64 image, pinned by image_digest, under emulation on an arm64 host.
The actual checkout is recorded in container_commit; disagreements with the source datasets are retained in the per-instance note.
- Reproduce the original dataset PoC on the base build and compare its sanitizer frames with the dataset report (
build_before.log,poc_before.log). - Apply the CVE_NVD developer patch with plain
git apply, without fuzzy or three-way application, then rebuild and rerun the PoC (apply.log,build_after.log,poc_after.log). - State the root cause as a violated invariant and test other inputs that reach it, together with valid inputs through the patched code (
variants.log,variants/). Expected outputs use a recorded oracle: Node.js for njs, CRuby for mruby, the escaping-function character table for libredwg, and the generated-file values for gpac (case_oracleinresults.jsonl). - Check per-case predictions against observations (
predictions.log) and run invariant instrumentation (variants/assert_*). The protocol calls for predictions before variant runs; retrospective predictions and other deviations are identified in the notes. - Run the project's own regression suite before and after the patch with identical options, and compare results at the granularity supported by the runner (
tests_before.log,tests_after.log). Differing results are rerun to distinguish persistent differences from flakiness. - Where a reduction is kept, derive it by changed-line or hunk ablation and validate it against build, PoC, case results and project tests (
ablation/,*_min.log). Its changed lines are a subset of the developer patch; reductions limited to style or required diagnostics are not kept. - Evaluate a root-cause patch where the analysis requires one, preferring an upstream backport when available (
*_root.log,variants/root.*). Provenance, synthetic changes, historical variants and adoption decisions remain explicit in the records. - Record the independent second reading and upstream search (
second_reading.log,upstream_search.log). The three-phase reading withholds the developer patch in phase 1, discloses it in phase 2, and adjudicates against the first reading's evidence in phase 3; protocol deviations are documented.
A crash is identified by a sanitizer report rather than process exit status. Case outputs distinguish sanitizer reports, wrong results and oracle-equal results. Reference-patch decisions and residual scope follow the recorded human reviews.
Sources and provenance
The default configuration is an unmodified copy of SongTonyLi/CVE_NVD at revision d1a467647078043261f5e43e209983d6e4a6e951.
Its parquet SHA-256 is 02e62a02ed80ee778d2728e36ed9714b2818045f46327fbdd7728575757c7177.
Verification also uses SEC-bench/SEC-bench at revision 11422e774857272b8f5460c699dca7a64046308b for the PoCs, build scripts and evaluation images.
Per-instance image digests, commits, oracle versions, patch hashes and review states are retained in the rows, notes and full verification records.
Files and evidence
| Path | Contents |
|---|---|
data/train-*.parquet |
The 200 source rows loaded by default. |
data/verified-*.parquet |
The verified rows, including the nested failing-input column. |
| results.jsonl | Full per-instance verification records, including patch provenance, oracles, predictions, root-fix distances where applicable and review decisions. |
patches/<instance>.diff |
Original developer patch. |
patches/<instance>.min.diff |
Validated minimal patch, where one is kept. |
patches/<instance>.root.diff |
Root-cause patch, where one is retained and with its adoption status recorded. |
notes/<instance>.md |
Mechanism, case results, scope decisions, upstream evidence, deviations and coverage limitations. |
logs/<instance>/ |
Raw build, PoC, test, variant and second-reading output, kept as produced. |
scripts/ |
Case generators, predictions, instrumentation, runners, comparisons and export helpers in their uploaded versions. |
Paths in the table and nested input records are relative to this dataset repository.
The parquet is a selected export of results.jsonl, so the full records contain additional evidence fields not listed as parquet columns.
Limitations
- The runs used emulation, so the timings in the stage logs are not native.
- Test granularity differs by project (
regression_tests). For njs the unit tests that print their script are compared per test,vm_json,vm_valueandvm_internal_apiby totals, andshell_testby exit status. For mruby.cve-2022-1934 the suite is compared by totals (lib 1460 OK, 0 KO, 0 crash, 8 skip; bintest 61/61 on every build). For libredwg.cve-2020-21816 the completemake checkoutput is compared byte for byte (51 of 51 tests;makeexits 2 on every build because the image lacks the libxml2 headers). - For several instances few or no pre-existing tests reach the patched branch, so the case matrix is the main regression evidence for the patched lines; each note states the coverage.
- The verified configuration is a manually completed subset and is expanded as instances are finished and reviewed. Its counts should not be treated as estimates for all 200 source instances.
- The named failing-input inventory is limited to four records and to retained evidence, with five report-only observations as described above.
- Predictions and blind-reading procedures were refined during the first instances. The notes identify retrospective predictions, disclosure deviations, dissent and uncertainty rather than treating every instance as following an identical protocol.
- Upstream-master observations describe the revisions tested in the evidence, not an ongoing check of current upstream behavior.
- A null minimal or root patch indicates that no such patch is retained in the published row; the derivation and status fields explain why.
Per-instance findings and caveats
The following summaries retain the recorded scope decisions and historical observations. Linked notes provide case names, logs, tested revisions and coverage details.
njs.cve-2022-31307: the blind second reading reported three further defects (forward iteration with a non-zero start index, the
Symbol.replaceindex, a 2^63 conversion). They are classed outside the reported failure without separability variants, andconfidenceis medium for that scope boundary.njs.cve-2022-32414: the leftover defects, among them AggregateError holes, array-likes longer than 1024 and WebCrypto key usages with a hole, are classed independent by the separability rule; the WebCrypto case was found only by the second reading, and
confidenceis medium for the scope boundary.njs.cve-2022-28049: no input crashes after the developer patch, but array literals of 32761 or more elements lose element values through a different instruction; the patch turns 3 crashing inputs into that silent loss (12 wrong results before, 15 after). The record classes the loss as an independent defect by the separability rule; the second reading recorded a dissent, and the classification was reviewed and kept on 2026-10-28. Upstream fixed the loss in 3557c57d (first release 1.0.2), 1654 days after the developer fix (
root_fix_distance).njs.cve-2021-46462: the developer patch adds a limit of 1024 arguments, so 15 calls with 1025 to 9000 arguments that run on the base build throw an InternalError afterwards; upstream master keeps the limit. The minimal patch drops the limit hunk.
njs.cve-2022-34029: the developer patch's second hunk makes
awaitof an uninitialised binding reject with an InternalError instead of the ReferenceError of the base build (also at upstream master); the minimal patch is the first hunk alone, and the CVE_NVDminimized_patch, which keeps the second hunk, is not minimal.libredwg.cve-2020-21816: the developer patch fixes
htmlescape()(drawings up to R2004);htmlwescape()(R2007 and later) keeps the same two defects, which are libredwg.cve-2020-21814, a separate CVE whose developer patch is e8c3edb9. SEC-bench gives both instances the same gold patch, which fixes both functions; run as the developer patch plus e8c3edb9, it repairs everyescape.ccase (variantsafter_wfixandroot). The second reading held thehtmlwescape()defect in scope in its first two phases; the classification was reviewed and kept on 2026-10-28. Reproducer r5 of GH #182, a heap-buffer-overflow indwg2SVG.c, remains on every build except upstream master.njs.cve-2022-31306 (flag confirmed 2026-10-28): the developer patch removes the reported crash, but a recursive data descriptor on a fast array of 20000 elements still writes through the freed element storage, a heap-use-after-free that AddressSanitizer reports after the patch. It is the same stale reference as the reported crash and not separable from it. Upstream fixed it in 4ae2f2b8 (first release 0.7.8), 123 days after the developer fix; the releases 0.7.4 to 0.7.7 shipped with the developer fix alone. The root patch is the backport of 4ae2f2b8.
mruby.cve-2022-1276 (flag confirmed 2026-10-28 as wrong result only): the developer patch removes the reported crash at 13 positional arguments, but with 0 to 12 positional arguments and keywords an index assignment receives a stale register as its right-hand side (66 of 103 cases), with no memory-safety consequence. No upstream fix exists (upstream later replaced the compiler), so the root patch is synthetic: the developer patch plus one
pop(). A second compiler defect ingen_hash()(two hashes passed after a double splat; a heap-buffer-overflow with 13 to 16 positional arguments) is recorded as an independent residual and is still present at upstream master for calls. The second reading of this instance was given the developer patch in its first phase, a deviation from the three-phase protocol used for the others.mruby.cve-2022-1201 (flag dismissed 2026-10-28): the developer patch adds the NULL check of the target class to the module branch of
OP_SUPER; the prepended-class branch of the same instruction still crashes on 2 of the 5 crash inputs. That crash is the reported failure of mruby.cve-2022-1427, which its own developer patch (a4d97934d) fixes, so it is counted under that instance and not against this patch. The root patch built from a4d97934d stays on record inlogs/mruby.cve-2022-1201/variants/root.diff; value differences against CRuby outside the NULL invariant (Method objects, a baresuperthroughOP_ARGARY,define_methodinClass.new) are listed inresidual.gpac.cve-2023-5586: the developer patch rejects a WAVE header with a known sample format and a zero sample rate or channel count, which removes the reported NULL dereference (0 of 1745 runs of the second reading reach it after the patch). A header with an unknown format tag, or with the data chunk before any
fmtchunk, still makes the parser loop without end (a hang, no sanitizer report); upstream fixed it in 3d9c5de08b, 263 days after the developer fix. Both readings class the hang as a separate defect with medium confidence, because it would be in scope under the wider invariant that an accepted header leaves the filter configured; the record changed on 2026-10-13 and back on 2026-10-14 after a coauthor review. A heap out-of-bounds read on well-formed files whose header ends after the first 5000-byte input block is a separate residual defect that is still present at upstream master.mruby.cve-2022-0240 (flag confirmed 2026-10-28): the developer patch guards the crash site (a NULL class pointer when a singleton method is defined) and leaves the compiler error that produces it: a discarded hash literal with a
**splat still compiles to the wrong registers (6 of 13 cases wrong after the patch, including the PoC's own form, whose outcome is correct only because of the value it computes), andObject.extend(c)still crashes on the second reading's inputs. Upstream fixed the compiler in b611c43a5 and ae3c99767 (4 and 17 days after the developer fix); the root patch is the backport of both, adopted as the reference patch. b611c43a5 is also the developer patch of mruby.cve-2022-0326 and alone ends this PoC's crash; the forms that take the other two branches are fixed only by ae3c99767, so the leftover is not counted under that instance.njs.cve-2022-29779 (reviewed 2026-10-28): the developer patch writes the hole marker for an absent source index in
spliceand repairs all 103 failing inputs of that route. Three inputs of other routes still reproduce the dataset report after the patch: DV3, a receiver shortened by an argument conversion in the fast branch ofsplice(fixed upstream in 607de2bd, first release 0.7.9), and Q01 and Q05, AggregateError and the Promise combinators over sparse sources. Each is repaired only by its own fix, so both readings class them as separate residual defects, and the classification was kept on review. The second reading's phase 2 predictions rest on its own phase 1 fix, which is the same change as the developer patch.njs.cve-2023-27727: deleting a non-configurable property throws a TypeError in njs where sloppy-mode JavaScript returns false; this predates the bug and is independent of it.
njs.cve-2022-43284: the patch distinguishes an uninitialized binding (NJS_INVALID) from a binding explicitly assigned undefined, preventing re-materialization with a NULL closure vector. The image base predates the CVE_NVD base by 55 commits; the base disagreement and per-test comparisons are recorded in the note.
mruby.cve-2022-0631: the patch rejects an empty packed argument array before reading its first element in send; all five reaching cases are closed and no residual of that class was found.
libredwg.cve-2020-21814: the htmlwescape() defect is repaired; the htmlescape() defect is counted separately under libredwg.cve-2020-21816 by the cross-CVE rule. The two redundant terminator writes are removed in the 10-line minimal patch; all 51 per-test results are unchanged.
mruby.cve-2022-1427 (reviewed 2026-10-30): the developer patch checks the reassigned target class in both OP_SUPER branches and repairs the reported NULL-class dereference. The developer patch is the reference patch; semantic_flag remains false. Method-object calls can still raise TypeError where CRuby returns a value because mcall records the wrong frame class; this behavior remains documented as a value-correctness residual, consistent with mruby.cve-2022-1201.
- Downloads last month
- 302