CVSS: 4.3EPSS: 0%CPEs: 1EXPL: 0CVE-2024-31894 – IBM App Connect Enterprise information disclosure
https://notcve.org/view.php?id=CVE-2024-31894
IBM App Connect Enterprise 12.0.1.0 through 12.0.12.1 could allow an authenticated user to obtain sensitive user information using an expired access token. IBM X-Force ID: 288175. IBM App Connect Enterprise 12.0.1.0 a 12.0.12.1 podría permitir que un usuario autenticado obtenga información confidencial del usuario utilizando un token de acceso caducado. ID de IBM X-Force: 288175. • https://exchange.xforce.ibmcloud.com/vulnerabilities/288175 https://www.ibm.com/support/pages/node/7154606 • CWE-324: Use of a Key Past its Expiration Date •
CVSS: 4.3EPSS: 0%CPEs: 1EXPL: 0CVE-2024-31895 – IBM App Connect Enterprise information disclosure
https://notcve.org/view.php?id=CVE-2024-31895
IBM App Connect Enterprise 12.0.1.0 through 12.0.12.1 could allow an authenticated user to obtain sensitive user information using an expired access token. IBM X-Force ID: 288176. IBM App Connect Enterprise 12.0.1.0 a 12.0.12.1 podría permitir que un usuario autenticado obtenga información confidencial del usuario utilizando un token de acceso caducado. ID de IBM X-Force: 288176. • https://exchange.xforce.ibmcloud.com/vulnerabilities/288176 https://www.ibm.com/support/pages/node/7154606 • CWE-324: Use of a Key Past its Expiration Date •
CVSS: 4.3EPSS: 0%CPEs: 1EXPL: 0CVE-2024-31893 – IBM App Connect Enterprise information disclosure
https://notcve.org/view.php?id=CVE-2024-31893
IBM App Connect Enterprise 12.0.1.0 through 12.0.12.1 could allow an authenticated user to obtain sensitive calendar information using an expired access token. IBM X-Force ID: 288174. IBM App Connect Enterprise 12.0.1.0 a 12.0.12.1 podría permitir que un usuario autenticado obtenga información confidencial del calendario utilizando un token de acceso caducado. ID de IBM X-Force: 288174.v • https://exchange.xforce.ibmcloud.com/vulnerabilities/288174 https://www.ibm.com/support/pages/node/7154606 • CWE-324: Use of a Key Past its Expiration Date •
CVSS: -EPSS: 0%CPEs: 9EXPL: 0CVE-2021-47477 – comedi: dt9812: fix DMA buffers on stack
https://notcve.org/view.php?id=CVE-2021-47477
In the Linux kernel, the following vulnerability has been resolved: comedi: dt9812: fix DMA buffers on stack USB transfer buffers are typically mapped for DMA and must not be allocated on the stack or transfers will fail. Allocate proper transfer buffers in the various command helpers and return an error on short transfers instead of acting on random stack data. Note that this also fixes a stack info leak on systems where DMA is not used as 32 bytes are always sent to the device regardless of how short the command is. • https://git.kernel.org/stable/c/63274cd7d38a3322d90b66a5bc976de1fb899051 https://git.kernel.org/stable/c/a6af69768d5cb4b2528946d53be5fa19ade37723 https://git.kernel.org/stable/c/365a346cda82f51d835c49136a00a9df8a78c7f2 https://git.kernel.org/stable/c/8a52bc480992c7c9da3ebfea456af731f50a4b97 https://git.kernel.org/stable/c/39ea61037ae78f14fa121228dd962ea3280eacf3 https://git.kernel.org/stable/c/3efb7af8ac437085b6c776e5b54830b149d86efe https://git.kernel.org/stable/c/786f5b03450454557ff858a8bead5d7c0cbf78d6 https://git.kernel.org/stable/c/3ac273d154d634e2034508a14db82a95d •
CVSS: -EPSS: 0%CPEs: 8EXPL: 0CVE-2021-47401 – ipack: ipoctal: fix stack information leak
https://notcve.org/view.php?id=CVE-2021-47401
In the Linux kernel, the following vulnerability has been resolved: ipack: ipoctal: fix stack information leak The tty driver name is used also after registering the driver and must specifically not be allocated on the stack to avoid leaking information to user space (or triggering an oops). Drivers should not try to encode topology information in the tty device name but this one snuck in through staging without anyone noticing and another driver has since copied this malpractice. Fixing the ABI is a separate issue, but this at least plugs the security hole. En el kernel de Linux, se ha resuelto la siguiente vulnerabilidad: ipack: ipoctal: corrige la fuga de información de la pila. El nombre del controlador tty también se usa después de registrar el controlador y específicamente no debe asignarse en la pila para evitar filtrar información al espacio del usuario (o activar un ups). Los controladores no deberían intentar codificar información de topología en el nombre del dispositivo tty, pero este se coló durante la preparación sin que nadie se diera cuenta y desde entonces otro controlador copió esta mala práctica. Arreglar la ABI es un tema aparte, pero esto al menos tapa el agujero de seguridad. • https://git.kernel.org/stable/c/ba4dc61fe8c545a5d6a68b63616776556b771f51 https://git.kernel.org/stable/c/acb96e782bad427ca4bb1bd94af660acd1462380 https://git.kernel.org/stable/c/741ea2670e021350e54f491106bdaa22dc50e6a0 https://git.kernel.org/stable/c/2725925982dc96a78069cd118ea3d66759bfdad7 https://git.kernel.org/stable/c/829f13d6079cf7a2465522f39acb43033e9b320d https://git.kernel.org/stable/c/8657158a3b68c85234e6da3d8eae33d6183588b7 https://git.kernel.org/stable/c/5f6a309a699675680df15d9b6d389114515b4426 https://git.kernel.org/stable/c/0a9c36a2e06a249acbed64e8e0b84637c •