KB5017392: Windows Server 2022 Security Update (September 2022)
Discription
The remote Windows host is missing security update 5017392. It is, therefore, affected by multiple vulnerabilities
– HTTP V3 Denial of Service Vulnerability (CVE-2022-35838)
– Windows Credential Roaming Service Elevation of Privilege Vulnerability (CVE-2022-30170)
– Windows Secure Channel Denial of Service Vulnerability (CVE-2022-30196, CVE-2022-35833)
Note that Nessus has not tested for these issues but has instead relied only on the application’s self-reported version number.Read More
References
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-34729https://support.microsoft.com/en-us/help/5017392http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-30170http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-34725http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-35838http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-35840http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-34726http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-35832http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-35831http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-34724http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-34730http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-35836http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-37969http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-33679http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-34732http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-35841http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-37955http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-34727http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-30200http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-34731http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-35830http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-35833http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-34719http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-34733http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-38006http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-34720http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-35834http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-35837http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-37958http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-34728http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-34722http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-37956http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-34734http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-37954http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-37959http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-35803http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-34721http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-30196http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-35835https://support.microsoft.com/help/5017392http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-33647http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-34718http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-38005Back to Main