Data quality issue with several MAL advisories

[sobregosodd]

Examples:

• ngx-toastr: GH advisory affected versions>= 19.0.1, <= 19.0.2 vs OSV.dev affected all versions
• @ctrl/tinycolor: GH advisory affected versions >= 4.1.1, <= 4.1.2 vs OSV.dev affected all versions
• @ctrl/deluge: GH advisory affected versions >= 7.2.1, <= 7.2.2 vs OSV.dev affected all versions

Describe the data quality issue observed
There is a discrepancy with the data ingested from GH advisories, apparently at least this commit is wrongly assigning "introduced": "0" (all versions are vulnerable) to packages where specific versions where subject to compromise.

Suggested changes to record
Fix the items, and assign the proper version / ranges

Additional context
I'm unaware if the situation is only related to this commit or if is there any others MAL records having the same problem.

[github-actions]

✨ Thank you for your interest in OSV.dev's data quality! ✨

Please review our FAQ entry on how to most efficiently have this addressed.

[michaelkedar]

Hi, thanks for the report.
I believe this issue should be raised upstream in the malicious packages repository.