Search threats, CVEs… ⌘K
Vendor advisories

Microsoft Security Response Center

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

Current Checked 4 hours ago Checked every 6 hours
All vendor sources Official source

15,806 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-32763
HighCVSS 7.5

An issue was discovered in Qt before 5.15.15 6.x before 6.2.9 and 6.3.x through 6.5.x before 6.5.1. When a SVG file with an image inside it is rendered a QTextLayout buffer overflow can be triggered.

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 productscm1 qt5-qtbase 5.12.11-7 on CBL Mariner 1.0, cbl2 qt5-qtbase 5.12.11-8 on CBL Mariner 2.0
Fixed versions5.12.11-7, 5.12.11-8
Vendor guidance

CBL-Mariner Releases

CVE-2023-32763
Read the vendor advisory Watch this product
Microsoft Security Response CenterCVE-2023-32700
HighCVSS 7.8

LuaTeX before 1.17.0 allows execution of arbitrary shell commands when compiling a TeX file obtained from an untrusted source. This occurs because luatex-core.lua lets the original io.popen be accessed. This also affects TeX Live before 2023 r66984 and MiKTeX before 23.5.

Mariner

Affected productsazl4 texlive-base 11:20230311-95.azl4.2 on Azure Linux 4.0
Fixed versions11:11:20230311-95.azl4.2
Vendor guidance

Release Notes

CVE-2023-32700
Read the vendor advisory Watch this product
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