[OASIS Issue Tracker] (CSAF-20) Analysis of CVE Automation and JSON format

From
OASIS Issues Tracker <>
Date
2017-02-22T12:25:19+00:00
ID
Thread
[OASIS Issue Tracker] (CSAF-20) Analysis of CVE Automation and JSON format
[ https://issues.oasis-open.org/browse/CSAF-20?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=65302#comment-65302 ] 

Stefan Hagen commented on CSAF-20:
----------------------------------

In the current draft model of the CVEProject at github and as retrieved today (2017-02-22) the only component afine elements are inside the JSONPath: 

  $.CVE_affects.CVE_vendor.CVE_vendor_data[*].CVE_product

How is a component perspective expected to be different from the data in above objects?

Is this more a C2 perspective?

> Analysis of CVE Automation and JSON format
> ------------------------------------------
>
>                 Key: CSAF-20
>                 URL: https://issues.oasis-open.org/browse/CSAF-20
>             Project: OASIS Common Security Advisory Framework (CSAF) TC
>          Issue Type: Bug
>            Reporter: Omar Santos
>
> Perform analysis of the CVE json format being worked in the CVE Automation Working Group:
> https://github.com/CVEProject/automation-working-group



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)