A security researcher alleges that Microsoft discreetly addressed a vulnerability in Azure Backup for AKS after rejecting his report and without issuing a CVE, while Microsoft contends that the behavior was anticipated and no product changes occurred.
For a cybersecurity professional, the key takeaway here is the importance of independently verifying vendor claims regarding vulnerability fixes, especially when no CVE is issued. This incident underscores the need for continuous monitoring and validation of vendor-provided security measures, as well as maintaining open communication channels with security researchers to ensure critical fixes are transparently acknowledged and documented.