Open ASKAC0810 opened 2 months ago
Confirmed that 1dd2685dcc735496d7adde87ac60b9434ed4a04c is tagged as 1.30.1:
$ git ls-remote https://github.com/mirror/busybox | fgrep 1dd2685dcc735496d7adde87ac60b9434ed4a04c
1dd2685dcc735496d7adde87ac60b9434ed4a04c refs/heads/1_30_stable
1dd2685dcc735496d7adde87ac60b9434ed4a04c refs/tags/1_30_1
Confirmed that querying for 1dd2685dcc735496d7adde87ac60b9434ed4a04c only returns CVE-2023-39810 and not CVE-2021-42384:
$ curl -d \
'{"commit": "1dd2685dcc735496d7adde87ac60b9434ed4a04c"}' \
"https://api.osv.dev/v1/query"
{"vulns":[{"id":"CVE-2023-39810","details":"An issue in the CPIO command of Busybox v1.33.2 allows attackers to execute a directory traversal.","modified":"2024-05-14T12:59:18.428091Z","published":"2023-08-28T19:15:07Z","references":[{"type":"ARTICLE","url":"https://www.pentagrid.ch/en/blog/busybox-cpio-directory-traversal-vulnerability/"},{"type":"WEB","url":"http://busybox.com"}],"affected":[{"ranges":[{"type":"GIT","repo":"https://github.com/mirror/busybox","events":[{"introduced":"0"},{"last_affected":"1dd2685dcc735496d7adde87ac60b9434ed4a04c"},{"last_affected":"db726ae0c61ffec6b58e19749e0c63aaaf4f6989"}]}],"versions":["0_29alpha2","0_32","0_33","0_34","0_36","0_39","0_40","0_41","0_42","0_43","0_43pre1","0_45","0_46","0_47","0_48","0_49","0_50","0_51","0_52","0_60_0","0_60_1","0_60_2","0_60_3","0_60_4","0_60_5","1_00","1_00_pre1","1_00_pre10","1_00_pre2","1_00_pre3","1_00_pre4","1_00_pre5","1_00_pre6","1_00_pre7","1_00_pre8","1_00_pre9","1_00_rc1","1_00_rc2","1_00_rc3","1_10_0","1_12_0","1_14_0","1_15_0","1_16_0","1_17_0","1_18_0","1_19_0","1_1_0","1_1_1","1_20_0","1_21_0","1_22_0","1_23_0","1_24_0","1_25_0","1_26_0","1_27_0","1_28_0","1_29_0","1_2_0","1_30_0","1_30_1","1_31_0","1_32_0","1_33_0","1_33_1","1_33_2","1_4_0","1_8_0","1_9_0"],"database_specific":{"source":"https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2023-39810.json"}}],"schema_version":"1.6.0","severity":[{"type":"CVSS_V3","score":"CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H"}]}]}
My current conclusion is that this is an issue in the version enumeration/repository analysis code and not the CVE conversion itself.
The CVE ID CVE-2021-42384
Describe the data quality issue observed When I searched this CVE ID from osv.dev, I got different result with NVD when echo system is GIT. Result of osv.dev
The affected version shows as below image![image](https://github.com/google/osv.dev/assets/164469490/9020c856-0cc7-4c71-88d2-8c5c6d3fab2f)
Result of NVD
The affected version shows as below image![image](https://github.com/google/osv.dev/assets/164469490/ff968dd3-949f-46df-aea6-57d982ed59dc)
The "From" (1_18_0) and and "Up to" (1_33_1) version are both the same between osv.dev and NVD.
However, osv.dev does not link this CVE to all tag version .
For example, I use the busybox v1.30.1, the tag ID is 1_30_1 , and the GIT commit hash is as following 1dd2685dcc735496d7adde87ac60b9434ed4a04c
As you can see, CVE-2021-42384 can not be found on osv.dev and osv-scanner tool with this version.
Suggested changes to record Link CVE to all tag version between from and Up .
Hope my description is clear :) Thank you very much.