KLA12429 Multiple vulnerabilities in Google Chrome

Multiple vulnerabilities were found in Google Chrome. Malicious users can exploit these vulnerabilities to cause denial of service, execute arbitrary code. Below is a complete list of vulnerabilities: 1. Implementation vulnerability in Service Worker API can be exploited to cause denial of servic...

CVE-2022-21867

Windows Push Notifications Apps Elevation of Privilege Vulnerability...

CVE-2022-21867

Windows Push Notifications Apps Elevation of Privilege Vulnerability...

CVE-2022-21867

Windows Push Notifications Apps Elevation of Privilege Vulnerability...

Privilege escalation

Windows Push Notifications Apps Elevation of Privilege Vulnerability...

CVE-2022-21867

Technical details for CVE-2022-21867 are not publicly available in the provided documents. Monitor for updates.

CVE-2022-21867 Windows Push Notifications Apps Elevation of Privilege Vulnerability

...

CLSA-2022-1641903536 Fix of 8 CVEs

CVE-2021-3517.patch: validate UTF8 in xmlEncodeEntities - CVE-2021-3518.patch: fix user-after-free with 'xmllint --xinclude --dropdtd' - CVE-2021-3537.patch: propagate error in xmlParseElementChildrenContentDeclPriv - CVE-2021-3541.patch: parser fix for the billion laughs attack -...

Windows Push Notifications Apps Elevation of Privilege Vulnerability

...

Microsoft Windows Push Notifications 权限许可和访问控制问题漏洞

Microsoft Windows Push Notifications is a push notification service from Microsoft USA. It provides a reliable way to deliver new updates. Microsoft Windows Push Notifications is vulnerable to privilege permission and access control issues. The following products and editions are affected:Windows...

PT-2022-1502 · Microsoft · Windows Push Notifications Apps +1

Name of the Vulnerable Software and Affected Versions: Windows Push Notifications Apps affected versions not specified Description: The issue is related to insecure privilege management in the Windows Push Notifications Apps component of the Windows operating system. It allows an attacker to...

CLSA-2021-1640700669 Fixed 8 CVEs in libxml2

CVE-2021-3517.patch: validate UTF8 in xmlEncodeEntities - CVE-2021-3518.patch: fix user-after-free with 'xmllint --xinclude --dropdtd' - CVE-2021-3537.patch: propagate error in xmlParseElementChildrenContentDeclPriv - CVE-2021-3541.patch: parser fix for the billion laughs attack -...

Exploit for Integer Overflow or Wraparound in Apple Ipados

PoC exploit for CVE-2021-30860, a vulnerability in Apple's Xcode...

PT-2021-5580 · Anker · Anker Eufy Homebase 2

Name of the Vulnerable Software and Affected Versions: Anker Eufy Homebase 2 version 2.1.6.9h Description: The issue is caused by an out-of-bounds write vulnerability in the read udp push config file function of the home security binary. This vulnerability can be exploited by a remote attacker...

CVE-2021-20846

Cross-site request forgery CSRF vulnerability in Push Notifications for WordPress Lite versions prior to 6.0.1 allows a remote attacker to hijack the authentication of an administrator and conduct an arbitrary operation via a specially crafted web page...

Cross site request forgery (csrf)

Cross-site request forgery CSRF vulnerability in Push Notifications for WordPress Lite versions prior to 6.0.1 allows a remote attacker to hijack the authentication of an administrator and conduct an arbitrary operation via a specially crafted web page...

CVE-2021-20846

The CVE-2021-20846 entry concerns the WordPress plugin Push Notifications for WordPress (Lite) before version 6.0.1. The connected sources confirm a Cross-site Request Forgery (CSRF) vulnerability that can allow an authenticated administrator to be hijacked to perform arbitrary actions via a craf...

Clarify Content-Type handling

Impact In the OCI Distribution Specification version 1.0.0 and prior, the Content-Type header alone was used to determine the type of document during push and pull operations. Documents that contain both “manifests” and “layers” fields could be interpreted as either a manifest or an index in the...

GHSA-MC8V-MGRF-8F4M Clarify Content-Type handling

Impact In the OCI Distribution Specification version 1.0.0 and prior, the Content-Type header alone was used to determine the type of document during push and pull operations. Documents that contain both “manifests” and “layers” fields could be interpreted as either a manifest or an index in the...

Incorrect Content-type Handling

github.com/opencontainers/distribution-spec is handling content-type incorrectly. Type of the manifest during the push and pull operations was wrongly determined as it uses only Content-Type header, causing a client to interpret the resulting content differently...