| Summary: | CVE Resource information not available in SRTool | ||
|---|---|---|---|
| Product: | [Yocto Project Subprojects] Security Response Tool | Reporter: | Karin Julenius <karin.julenius> |
| Component: | General | Assignee: | David Reyna <david.reyna> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Medium | ||
| Version: | unspecified | ||
| Target Milestone: | 2.7 M2 | ||
| Hardware: | x86 | ||
| OS: | x86_64 | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | No (bug/feature does not impact docs) | |
|
Description
Karin Julenius
2019-01-04 15:27:23 UTC
Hi Karin, It is true that the CVE is indeed purposely patterned after the NIST page. And it is also true that the "resource" and "type" fields are currently empty. * When I did my first implementation, the JSON files from NIST did not include the "Resource", "Type", and "Source" fields. I did not worry about it at the time because the content visible at the NIST site seemed completely redundant with the actual hyperlink. * I just now looked again at NIST, and I see that they have since changed the interface. The "Resource" field now seems to be 'tag' like entries, and the "Type" and "Source" fields are removed. I will review the latest JSON format, and include the "resource" field if it present. Thanks, David And yes, it has been added to the NIST JSON schema:
"references":
"reference_data": [
"url": "http://www.securityfocus.com/bid/103092", "name": "103092", "tags": [], "refsource": "BID"},
"url": "http://www.securitytracker.com/id/1040180", "name": "1040180", "tags": ["Third Party Advisory", "VDB Entry"], "refsource": "SECTRACK"},
"url": "https://kb.juniper.net/JSA10828", "name": "https://kb.juniper.net/JSA10828", "tags": ["Mitigation", "Patch", "Vendor Advisory"], "refsource": "CONFIRM"}
]}
Fix pushed: commit e61223da184829d911c6247640abb81d08c7ab59 Hi! Thank you for a quick fix! However, some resource links look like they have been parsed incorrectly, for instance first row in: http://linux-srtool:8010/srtgui/cve/CVE-2015-8504 Sorry, for the internal link. I meant to paste this one: https://nvd.nist.gov/vuln/detail/CVE-2015-8504 New fix pushed: commit 89a07b2546cfed66ed833c0960ddfc2bc69be9fc Changing the internal field separator from ';' to a tab key avoids parsing problems with CVE references like: http://git.qemu-project.org/?p=qemu.git;a=commitdiff;h=4c65fed8b... - David commit 98b5bc41ed75b57de4376757a575458e72bf44c3 commit 89a07b2546cfed66ed833c0960ddfc2bc69be9fc commit e61223da184829d911c6247640abb81d08c7ab59 |