Articles on rhythmrx9's Blog

Weekly Blog #9 - Stuff 1

rhythmrx9@gmail.com (rhythmrx9) — Sun, 18 Sep 2022 16:11:30 +0000

What did I do this week?

I worked on new issues related to OSV and database handling.

What is coming up next?

Next, I will be adding and integrating GitLab Advisory Database as a data source.

Did I get stuck anywhere?

No, I did not get stuck anywhere.

Weekly Blog #8 - Stuff 0

rhythmrx9@gmail.com (rhythmrx9) — Sun, 18 Sep 2022 16:06:48 +0000

What did I do this week?

I fixed some issues related to LGTM quality reports, that's all.

What is coming up next?

Next, I will be working on some new issues related to database and OSV.

Did I get stuck anywhere?

No, I did not get stuck anywhere.

Weekly Blog #7 - OSV : Finishing up.

rhythmrx9@gmail.com (rhythmrx9) — Sun, 18 Sep 2022 16:03:35 +0000

What did I do this week?

After addition of OSV, I added tests and documentation for it. An update in a CVE broke a test, which I updated. Now OSV is finally added and integrated as a data source.

What is coming up next?

Next, I will be looking at doing something other than working on a data source.

Did I get stuck anywhere?

No, I did not get stuck anywhere.

Weekly Blog #6 - Duplicates

rhythmrx9@gmail.com (rhythmrx9) — Sun, 18 Sep 2022 15:51:13 +0000

What did I do this week?

I implemented checking for duplicate CVEs, NVD is given priority, so any common CVEs from OSV are rejected.

What is coming up next?

Next, I will be adding tests and documentation for OSV.

Did I get stuck anywhere?

No, I did not get stuck anywhere.

Weekly Blog #5 - OSV : Vendor Problem

rhythmrx9@gmail.com (rhythmrx9) — Sun, 18 Sep 2022 15:38:28 +0000

What did I do this week?

I implemented a mechanism to get vendor data from NVD data source and use it to update vendors for CVEs from OSV. By updating vendors, there was a good increase in the amount of CVEs that could be detected now.

What is coming up next?

Next, I will be working on eliminating duplicate CVEs, as there are common CVEs procured from data sources.

Did I get stuck anywhere?

Yes, I came up with a number of solutions to update vendors for OSV but was stuck for quite a while before I thought of using NVD to get vendor data.

Weekly Blog #4 - OSV : Integration

rhythmrx9@gmail.com (rhythmrx9) — Sun, 18 Sep 2022 15:23:36 +0000

What did I do this week?

I implemented formatting CVE data from OSV and integrated the database to be used by code handling the database. The data from OSV does not include vendors so a solution to rectify that needs to be implemented.

What is coming up next?

Next, I will be adding a mechanism to update vendor data in CVEs from OSV, so that CVEs can be detected and reported.

Did I get stuck anywhere?

No, I did not get stuck anywhere.

Weekly Blog #3 - OSV

rhythmrx9@gmail.com (rhythmrx9) — Sat, 23 Jul 2022 06:32:12 +0000

What did I do this week?

I added the bare bones to implement the OSV data source. Fetching CVE data and parsing it is implemented, but the source itself is not integrated as of now.

Formatting of data, getting vendor data, and actual integration still remains to be implemented.

What is coming up next?

Next, I will be finishing up with formatting of data to a common format.

Did I get stuck anywhere?

No, I did not get stuck anywhere.

Weekly Blog #2 - New Structure

rhythmrx9@gmail.com (rhythmrx9) — Fri, 22 Jul 2022 13:21:31 +0000

What did I do this week?

I implemented a new structure for database handling, as the database handling and CVE data fetching functionalities are now separate.

Multiple data sources can now be added, I am going with a modular approach with them.

What is coming up next?

Next, I will be adding a new data source! I will be starting with OSV.

Did I get stuck anywhere?

I did not get stuck, as I did plan this ahead while refactoring.

Weekly Blog #1 - Refactoring

rhythmrx9@gmail.com (rhythmrx9) — Fri, 22 Jul 2022 09:46:37 +0000

Hello, I am Rhythm Jamwal, a student pursuing Computer Science and Engineering. I will be adding new data sources to CVE Binary Tool, hence increasing CVE coverage.

What did I do this week?

I went through the code responsible for database handling, which is also responsible for fetching CVE Data from NVD, looking to split both functionalities.

This refactor will help in implementing a new structure for database handling and fetching CVEs from multiple sources.

What is coming up next?

Next, I will be looking to implement the new structure for database handling that supports multiple data sources.

Did I get stuck anywhere?

I did not get stuck, the refactoring was lengthy but easy.