Vendor advisories

Microsoft Security Response Center

Browse 15,805 advisories from this official source. Search by product, CVE, severity, or advisory ID.

Current Checked 15 minutes ago Checked every 6 hours

15,805 advisories

Each date says whether the vendor published or updated the bulletin. A vendor bulletin describes products that may be affected. It does not prove that the vulnerable product or version is installed in your environment.

RSS for these results
Microsoft Security Response CenterCVE-2023-3978
MediumCVSS 6.1

Improper rendering of text nodes in golang.org/x/net/html

Is Azure Linux the only Microsoft product that includes this open-source library and is therefore potentially affected by this vulnerability? One of the main benefits to our customers who choose to use the Azure Linux distro is the commitment to keep it up to date with the mos...

Affected productscbl2 packer 1.8.7-2 on CBL Mariner 2.0, azl3 application-gateway-kubernetes-ingress 1.7.2-3 on Azure Linux 3.0, azl3 containerized-data-importer 1.57.0-14 on Azure Linux 3.0, azl3 kubevirt 0.59.0-14 on Azure Linux 3.0
Fixed versions1.10.1-1, 1.7.7-1, 1.57.0-12, 1.2.0-1
Vendor guidance

CBL-Mariner Releases

Microsoft Security Response CenterCVE-2023-39533
HighCVSS 7.5

libp2p nodes vulnerable to attack using large RSA keys

Is Azure Linux the only Microsoft product that includes this open-source library and is therefore potentially affected by this vulnerability? One of the main benefits to our customers who choose to use the Azure Linux distro is the commitment to keep it up to date with the mos...

Affected productscbl2 golang 1.17.13-2 on CBL Mariner 2.0, cbl2 golang 1.18.8-7 on CBL Mariner 2.0, cbl2 golang 1.21.6-1 on CBL Mariner 2.0, cbl2 msft-golang 1.19.12-1 on CBL Mariner 2.0
Fixed versions1.21.6-1, 1.19.12-1
Vendor guidance

CBL-Mariner Releases

Before you act

Start with the vendor's bulletin.

We normalize the fields that vendors publish so you can search and compare advisories in one place. We do not replace the original bulletin or turn a product-name match into proof that a system is vulnerable.

Confirm the installed product and version, read the linked vendor guidance, and test the recommended update or mitigation through your normal change process.

How we check our sources