This doesn’t show in the CVE database, and another vendor is using this ID as well today. Can you verify the CVE number?
Hi @tsmithco, thanks for reaching out. I’m not sure, it looks like veeam have changed to CVE-2023-27532. Do you know if this was a copy-paste error or was a new CVE issued to mitigate this conflict?
I’ve just double checked HackerOne and CVE-2023-27530 is the one they assigned to us.
Thanks. I see that as well now. They initially published with the same, but apparently made the mistake and corrected it. Thanks for verifying!