feat: Add CVE extraction utility and standardize YAML handling in vulntotal - #2242
Closed
ogubuikeAlex wants to merge 2 commits into
Closed
feat: Add CVE extraction utility and standardize YAML handling in vulntotal#2242ogubuikeAlex wants to merge 2 commits into
ogubuikeAlex wants to merge 2 commits into
Conversation
ogubuikeAlex
changed the title
Member
|
Is this AI-generated code? This PR contains completely unrelated changes, no tests and does not pass basic checks. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
As part of my GSoC 2026 proposal to process unstructured data sources for vulnerability discovery, I've started contributing to VulnerableCode to familiarize myself with the codebase and lay groundwork for the project.
I began with a small housekeeping fix which replaces the standard yaml library with saneyaml in the vulntotal CLI to align it with the rest of the codebase. The output stays identical, but the codebase is now more consistent.
Also, I added an utility function (extract_cve_ids) that pulls CVE identifiers out of raw unstructured text. It handles CVEs buried in URLs, mixed casing, duplicates, trailing punctuation, and returns a clean, sorted list. This is a small but necessary piece of the larger extraction pipeline I'm proposing, which will eventually parse not just CVE IDs but also package PURLs, version ranges, and fix commit hashes from mailing lists, changelogs, and git logs to feed into VulnerableCode's AdvisoryDataV2 ingestion flow.
(Related to RFC Issue #2241)