Conversation

@gregkh What the story behind your sourceIdentifier in the CVE data being published

Most CNAs use an email address. The kernel is using a uuid

416baaa9-dc9f-4396-8d5f-8c081fb06d67

1
0
0
@joshbressers I thought that was the correct field for that based on something, I can't remember what. You mean `assignerOrgId`, right? I don't see a field marked `sourceIdentifier` in our json output. Or are you talking about a different field?
1
0
0

@gregkh

It's from NVD. I pull in the NVD data rather than the data from CVE, and for whatever reason they aren't including the ASSIGNER field, which is cve@kernel.org

For example
https://services.nvd.nist.gov/rest/json/cves/2.0?cveId=CVE-2024-26599

has

sourceIdentifier "416baaa9-dc9f-4396-8d5f-8c081fb06d67"

But in every other case I've noticed, the source Identifier is the same as ASSIGNER

1
0
0
@joshbressers No idea, ask NVD. The original json record we upload to cve.org does not have that field at all: https://cveawg.mitre.org/api/cve/CVE-2024-26599
1
0
0

@gregkh Indeed, apologies for the invalid bug report

1
0
0
@joshbressers Not a problem, glad someone is looking at the records! :)
0
0
0