Add CISA known exploited vulnerabilities info to cisa.gov namespace about gsd-tools

[kurtseifried]

Took a quick look at the data, seems each entry is simply:
{ "cveID": "CVE-2021-27104", "vendorProject": "Accellion", "product": "FTA", "vulnerabilityName": "Accellion FTA OS Command Injection Vulnerability", "dateAdded": "2021-11-03", "shortDescription": "Accellion FTA 9_12_370 and earlier is affected by OS command execution via a crafted POST request to various admin endpoints.", "requiredAction": "Apply updates per vendor instructions.", "dueDate": "2021-11-17" },

I think the simplest/most obvious way to put the data in the files would be to keep it in its original format, and simply stick it into the cisa.gov namespace, e.g.:

{ "namespaces": { "cisa.gov": { "title": "CISA Catalog of Known Exploited Vulnerabilities", "catalogVersion": "2022.02.11", "dateReleased": "2022-02-11T10:44:14.1414Z", "count": 368, "vulnerabilities": [ { "cveID": "CVE-2021-27104", "vendorProject": "Accellion", "product": "FTA", "vulnerabilityName": "Accellion FTA OS Command Injection Vulnerability", "dateAdded": "2021-11-03", "shortDescription": "Accellion FTA 9_12_370 and earlier is affected by OS command execution via a crafted POST request to various admin endpoints.", "requiredAction": "Apply updates per vendor instructions.", "dueDate": "2021-11-17" } ] } } }

and obviously match up the CVE in CISA with our CVE alias field so they go in the correct files.

[oswalpalash]

Thanks @kurtseifried !
I'll write up a python script under securitylist/src/securitylist/ and the corresponding tests and propose a PR soon!
Some questions before I start writing -

• I'm guessing we'd want this script to be executed independently and just add the json blob under a cisa.gov namespace and update if it doesn't match? (similar pattern as securitylist/src/securitylist/CVE.py#L28 )
• How often do these scripts trigger and are they triggered with github actions? Can I look at how that is defined to write proper entrypoints/params to the script.

[westonsteimel]

I think @joshbressers can help answer questions about how this currently executes.

[kurtseifried]

I think for now the best way to do this is to simply have it generate a PR, I'm looking at my email and CISA has updated the known exploited vulnerability catalog: Jan 10, 17, 24, 28, 31, Feb 4, 7, 11 so about 1-2 times a week (https://public.govdelivery.com/accounts/USDHSCISA/subscriber/new?preferences=true#tab1 to join the list) so a manual script kickoff->PR is manageable and the easiest way to track changes/etc. The gsd-bot is "special" and actually, we want to move away from it and towards an "everyone/everything is a PR" model long term.

[oswalpalash]

I could use PR reviews on :

1. #19
2. https://github.com/cloudsecurityalliance/gsd-database/pull/2250/files

[oswalpalash]

Can be closed now.

[joshbuker]

@oswalpalash added this a while ago, closing.

Thanks Palash!