Vulnerabilities > High
| DATE | CVE | VULNERABILITY TITLE | RISK |
|---|---|---|---|
| 2024-12-30 | CVE-2024-13048 | Out-of-bounds Write vulnerability in Ashlar Cobalt 1204.90 Ashlar-Vellum Cobalt XE File Parsing Out-Of-Bounds Write Remote Code Execution Vulnerability. | 7.8 |
| 2024-12-30 | CVE-2024-13049 | Type Confusion vulnerability in Ashlar Cobalt 1204.90 Ashlar-Vellum Cobalt XE File Parsing Type Confusion Remote Code Execution Vulnerability. | 7.8 |
| 2024-12-30 | CVE-2024-13050 | Out-of-bounds Write vulnerability in Ashlar Graphite 13.0.48 Ashlar-Vellum Graphite VC6 File Parsing Heap-based Buffer Overflow Remote Code Execution Vulnerability. | 7.8 |
| 2024-12-30 | CVE-2024-13051 | Out-of-bounds Write vulnerability in Ashlar Graphite 13.0.48 Ashlar-Vellum Graphite VC6 File Parsing Heap-based Buffer Overflow Remote Code Execution Vulnerability. | 7.8 |
| 2024-12-30 | CVE-2024-54181 | IBM WebSphere Automation 1.7.5 could allow a remote privileged user, who has authorized access to the swagger UI, to execute arbitrary code. | 7.2 |
| 2024-12-30 | CVE-2024-13036 | SQL Injection vulnerability in Fabianros Chat System 1.0 A vulnerability was found in code-projects Chat System 1.0 and classified as critical. | 7.5 |
| 2024-12-30 | CVE-2024-13034 | Cross-site Scripting vulnerability in Code-Projects Chat System 1.0 A vulnerability, which was classified as problematic, was found in code-projects Chat System 1.0. | 7.6 |
| 2024-12-29 | CVE-2024-56721 | Out-of-bounds Read vulnerability in Linux Kernel In the Linux kernel, the following vulnerability has been resolved: x86/CPU/AMD: Terminate the erratum_1386_microcode array The erratum_1386_microcode array requires an empty entry at the end. Otherwise x86_match_cpu_with_stepping() will continue iterate the array after it ended. Add an empty entry to erratum_1386_microcode to its end. | 7.1 |
| 2024-12-29 | CVE-2024-56740 | Out-of-bounds Write vulnerability in Linux Kernel 6.12 In the Linux kernel, the following vulnerability has been resolved: nfs/localio: must clear res.replen in nfs_local_read_done Otherwise memory corruption can occur due to NFSv3 LOCALIO reads leaving garbage in res.replen: - nfs3_read_done() copies that into server->read_hdrsize; from there nfs3_proc_read_setup() copies it to args.replen in new requests. - nfs3_xdr_enc_read3args() passes that to rpc_prepare_reply_pages() which includes it in hdrsize for xdr_init_pages, so that rq_rcv_buf contains a ridiculous len. - This is copied to rq_private_buf and xs_read_stream_request() eventually passes the kvec to sock_recvmsg() which receives incoming data into entirely the wrong place. This is easily reproduced with NFSv3 LOCALIO that is servicing reads when it is made to pivot back to using normal RPC. | 7.8 |
| 2024-12-28 | CVE-2024-56704 | Double Free vulnerability in Linux Kernel In the Linux kernel, the following vulnerability has been resolved: 9p/xen: fix release of IRQ Kernel logs indicate an IRQ was double-freed. Pass correct device ID during IRQ release. [Dominique: remove confusing variable reset to 0] | 7.8 |