CVSS: 5.3EPSS: 0%CPEs: 5EXPL: 0CVE-2022-39161 – IBM WebSphere Application Server information disclosure
https://notcve.org/view.php?id=CVE-2022-39161
IBM WebSphere Application Server 7.0, 8.0, 8.5, 9.0, and IBM WebSphere Application Server Liberty, when configured to communicate with the Web Server Plug-ins for IBM WebSphere Application Server, could allow an authenticated user to conduct spoofing attacks. A man-in-the-middle attacker could exploit this vulnerability using a certificate issued by a trusted authority to obtain sensitive information. IBM X-Force ID: 235069. • https://exchange.xforce.ibmcloud.com/vulnerabilities/235069 https://www.ibm.com/support/pages/node/6987779 • CWE-295: Improper Certificate Validation •
CVSS: 9.3EPSS: 0%CPEs: 21EXPL: 0CVE-2022-30995
https://notcve.org/view.php?id=CVE-2022-30995
Sensitive information disclosure due to improper authentication. • https://security-advisory.acronis.com/advisories/SEC-3855 • CWE-287: Improper Authentication •
CVSS: 9.3EPSS: 0%CPEs: 21EXPL: 1CVE-2022-3405
https://notcve.org/view.php?id=CVE-2022-3405
Code execution and sensitive information disclosure due to excessive privileges assigned to Acronis Agent. • https://herolab.usd.de/security-advisories/usd-2022-0008 https://security-advisory.acronis.com/advisories/SEC-4092 • CWE-269: Improper Privilege Management •
CVSS: 7.3EPSS: 0%CPEs: 204EXPL: 0CVE-2022-33273 – Buffer over-read in Trusted Execution Environment
https://notcve.org/view.php?id=CVE-2022-33273
Information disclosure due to buffer over-read in Trusted Execution Environment while QRKS report generation. • https://www.qualcomm.com/company/product-security/bulletins/may-2023-bulletin • CWE-125: Out-of-bounds Read CWE-126: Buffer Over-read •
CVSS: 8.4EPSS: 0%CPEs: 334EXPL: 0CVE-2023-21666 – Improper Release of Memory Before Removing Last Reference (`Memory Leak`) in Graphics
https://notcve.org/view.php?id=CVE-2023-21666
Memory Corruption in Graphics while accessing a buffer allocated through the graphics pool. On Qualcomm Adreno/KGSL builds where CONFIG_QCOM_KGSL_USE_SHMEM is not set (or on older KGSL versions without CONFIG_QCOM_KGSL_USE_SHMEM), KGSL allocates GPU-shared memory from its own page pool. Pages from this pool are inserted into VMAs that don't have any weird flags like VM_PFNMAP set, which means userspace can grab extra references to these pages through get_user_pages() (for example, using vmsplice()). But when GPU-shared memory is freed, KGSL puts the freed pages into its own page pool without checking the page refcount. This means that pages that are still accessible from userspace can be reallocated as GPU memory by another process. • http://packetstormsecurity.com/files/172664/Qualcomm-Adreno-KGSL-Data-Leakage.html https://www.qualcomm.com/company/product-security/bulletins/may-2023-bulletin • CWE-401: Missing Release of Memory after Effective Lifetime •