You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I noticed that the CVEs referred are bit old despite the fact that i was able to discover the recent CVE-2022-3040 with Domato.
I didn't know that this Domato finding was CVE-2022-3040, but when i tired to submit the bug i found a similar crash reported and submitted for the same code few months ago and then it was labeled as CVE-2022-3040 ( i wish i was bit faster :) )
I think we can add this new CVE ref in the readme ?
I can share the Domato output that triggered this crash identified in CVE-2022-3040, this was generated using the default template !
The text was updated successfully, but these errors were encountered:
Thanks for letting me know this was findable by Domato.
The Domato CVE list in the README is unmaintained and contains just the bugs I found before Domato or some its featurese were released.
Perfect, thank you Ivan. I submitted a PR with small text update to refer to this CVE in the README and also attached the original output file in the PR comment if needed (for reproducibility)
I noticed that the CVEs referred are bit old despite the fact that i was able to discover the recent CVE-2022-3040 with Domato.
I didn't know that this Domato finding was CVE-2022-3040, but when i tired to submit the bug i found a similar crash reported and submitted for the same code few months ago and then it was labeled as CVE-2022-3040 ( i wish i was bit faster :) )
I think we can add this new CVE ref in the readme ?
I can share the Domato output that triggered this crash identified in CVE-2022-3040, this was generated using the default template !
The text was updated successfully, but these errors were encountered: