Vulnerabilidades explotables hoy
16,755en la vista actual
Score único combinando CVSS, membresía KEV y EPSS. Cada CVE con su ficha propia — timeline desde publicación hasta explotación activa.
En catálogo KEV1,758
Nuevos KEV · 24H0
Exploit Today ≥ 701,691
Distribución · última ventana
- Crítico5,635
- Alto21,782
- Medio20,206
- Bajo2,118
Filtros
Ventana
Severidad
Filtros
CVECVSSEPSSKEVRExplotTítuloVis.
CVE-2024-54608——
——0Rejected reason: This candidate was in a CNA pool that was not assigned to any issues.6hCVE-2024-54607——
——0Rejected reason: This candidate was in a CNA pool that was not assigned to any issues.6hCVE-2024-54606——
——0Rejected reason: This candidate was in a CNA pool that was not assigned to any issues.6hCVE-2024-54605——
——0Rejected reason: This candidate was in a CNA pool that was not assigned to any issues.6hCVE-2024-54604——
——0Rejected reason: This candidate was in a CNA pool that was not assigned to any issues.6hCVE-2024-54603——
——0Rejected reason: This candidate was in a CNA pool that was not assigned to any issues.6hCVE-2024-54602——
——0Rejected reason: This candidate was in a CNA pool that was not assigned to any issues.6hCVE-2024-54601——
——0Rejected reason: This candidate was in a CNA pool that was not assigned to any issues.6hCVE-2024-54600——
——0Rejected reason: This candidate was in a CNA pool that was not assigned to any issues.6hCVE-2024-54599——
——0Rejected reason: This candidate was in a CNA pool that was not assigned to any issues.6hCVE-2024-54598——
——0Rejected reason: This candidate was in a CNA pool that was not assigned to any issues.6hCVE-2024-54597——
——0Rejected reason: This candidate was in a CNA pool that was not assigned to any issues.6hCVE-2024-54596——
——0Rejected reason: This candidate was in a CNA pool that was not assigned to any issues.6hCVE-2024-54595——
——0Rejected reason: This candidate was in a CNA pool that was not assigned to any issues.6hCVE-2024-54594——
——0Rejected reason: This candidate was in a CNA pool that was not assigned to any issues.6hCVE-2024-54593——
——0Rejected reason: This candidate was in a CNA pool that was not assigned to any issues.6hCVE-2024-54592——
——0Rejected reason: This candidate was in a CNA pool that was not assigned to any issues.6hCVE-2024-54591——
——0Rejected reason: This candidate was in a CNA pool that was not assigned to any issues.6hCVE-2024-54590——
——0Rejected reason: This candidate was in a CNA pool that was not assigned to any issues.6hCVE-2024-54589——
——0Rejected reason: This candidate was in a CNA pool that was not assigned to any issues.6hCVE-2024-54588——
——0Rejected reason: This candidate was in a CNA pool that was not assigned to any issues.6hCVE-2024-54587——
——0Rejected reason: This candidate was in a CNA pool that was not assigned to any issues.6hCVE-2024-54586——
——0Rejected reason: This candidate was in a CNA pool that was not assigned to any issues.6hCVE-2024-54585——
——0Rejected reason: This candidate was in a CNA pool that was not assigned to any issues.6hCVE-2024-54584——
——0Rejected reason: This candidate was in a CNA pool that was not assigned to any issues.6hCVE-2024-54583——
——0Rejected reason: This candidate was in a CNA pool that was not assigned to any issues.6hCVE-2024-54582——
——0Rejected reason: This candidate was in a CNA pool that was not assigned to any issues.6hCVE-2023-42999——
——0Rejected reason: This candidate was in a CNA pool that was not assigned to any issues.8dCVE-2023-42998——
——0Rejected reason: This candidate was in a CNA pool that was not assigned to any issues.8dCVE-2023-42997——
——0Rejected reason: This candidate was in a CNA pool that was not assigned to any issues.8dCVE-2023-42996——
——0Rejected reason: This candidate was in a CNA pool that was not assigned to any issues.8dCVE-2023-42995——
——0Rejected reason: This candidate was in a CNA pool that was not assigned to any issues.8dCVE-2023-42994——
——0Rejected reason: This candidate was in a CNA pool that was not assigned to any issues.8dCVE-2023-42993——
——0Rejected reason: This candidate was in a CNA pool that was not assigned to any issues.8dCVE-2023-42992——
——0Rejected reason: This candidate was in a CNA pool that was not assigned to any issues.8dCVE-2023-42991——
——0Rejected reason: This candidate was in a CNA pool that was not assigned to any issues.8dCVE-2023-42990——
——0Rejected reason: This candidate was in a CNA pool that was not assigned to any issues.8dCVE-2026-767888.8 ALT16.1%
——5The OSDP Control Panel reply parser cp_decode_response() in subsys/mgmt/osdp/src/osdp_cp.c decodes replies from a Peripheral Device into a stack-allocated struct osdp_event. For the REPLY_KEYPPAD and REPLY_RAW reply types, the payload length is taken from the received frame and the only validation performed is that the declared length is self-consistent with the number of payload bytes present in the frame. Because the attacker controls both the length field and the frame length, that check imposes no bound, and the subsequent memcpy() writes into the fixed 64-byte data arrays of struct osdp_event_keypress / struct osdp_event_cardread (OSDP_EVENT_MAX_DATALEN). The sibling REPLY_FMT handler in the same switch already carried the missing > OSDP_EVENT_MAX_DATALEN bound.
The defect is reached from cp_process_reply(), which reads bytes from the OSDP RS-485 channel and passes them through osdp_phy_check_packet() and osdp_phy_decode_packet() before dispatching on the reply ID. Triggering it requires CONFIG_OSDP with CONFIG_OSDP_MODE_CP and an application event callback registered (the normal Control Panel integration), plus a frame carrying a correct SOM, a valid CRC-16, and a matching 2-bit sequence number — all of which are computable or observable by anyone on the bus. No check ties the reply ID to the outstanding command, so an oversized REPLY_KEYPPAD or REPLY_RAW is accepted as the answer to a routine CMD_POLL. A malicious or compromised card reader, or anyone with access to the RS-485 wiring, can supply such a frame; CONFIG_OSDP_SC_ENABLED only helps while a secure channel is active, and a single unauthenticated frame carrying a bad MAC causes sc_deactivate(), after which plaintext replies are again accepted.
With the default CONFIG_OSDP_UART_BUFFER_LENGTH of 256, roughly 180 bytes of fully attacker-chosen data can be written past the end of the stack-allocated event object, over saved registers and the return address on typical Cortex-M and RISC-V frame layouts (Zephyr does not enable stack canaries by default). The impact ranges from a hard crash of the access-control panel to potential control-flow hijack in the context of the OSDP receive thread. The fix adds an OSDP_EVENT_MAX_DATALEN bound to both handlers, capping each memcpy() at the size of its destination.7dCVE-2026-767875.9 MED29.8%
——9The UpdateHub firmware-over-the-air client parses the CoAP probe response with Zephyr's JSON library in z_impl_updatehub_probe() (subsys/mgmt/updatehub/updatehub.c). The decoder treats every descriptor field as optional — json_obj_parse() returns a bitmask of the fields it actually decoded and never fails on a missing one — so a response that omits the "sha256sum" string leaves the corresponding const char * in the zero-initialised struct resp_probe_any_boards / struct resp_probe_some_boards at NULL. Both metadata branches then computed sha256size = strlen(...objects.sha256sum) + 1 before any validation, dereferencing that NULL pointer; the SHA256_HEX_DIGEST_SIZE test that follows operates on a value the bad read has already produced and cannot prevent it.
The metadata is supplied entirely by the network peer: probe_cb() accepts the datagram, runs coap_packet_parse() and copies the payload with no token matching and no cryptographic check. With CONFIG_UPDATEHUB_DTLS unset — the default — start_coap_client() uses plain CoAP over UDP on port 5683 with no peer authentication and resolves the server via unauthenticated DNS, so an on-path attacker, a DNS spoofer, or an off-path attacker who wins the race with a forged source address can deliver the malformed metadata. A probe response as simple as "objects":[[{}],[{}]] suffices, and no user interaction is required because updatehub_autohandler() polls on CONFIG_UPDATEHUB_POLL_INTERVAL. When CONFIG_UPDATEHUB_DTLS=y the trigger narrows to a malicious or compromised update server.
The primitive is a read at address zero, not a write, so the impact is availability only. On targets where the low address range is unmapped or protected — MMU-based architectures, builds with CONFIG_NULL_POINTER_EXCEPTION_DETECTION_DWT/_MPU/_PMP, TrustZone non-secure images, and SoCs such as nRF54L whose 0x0–0x400 window is unmapped — the load faults and Zephyr's default fatal handler halts the system, giving a remotely re-triggerable denial of service on every poll. On classic Cortex-M targets where the vector table is readable at address zero the walk usually terminates immediately and the request is rejected by the length check, so the outcome is configuration- and SoC-dependent. There is no memory write, and the copied bytes are only compared against the locally computed image hash, so there is no information-disclosure channel.
The fix adds an explicit sha256sum == NULL test that returns UPDATEHUB_METADATA_ERROR ahead of the strlen() in both metadata branches. Debug builds (CONFIG_UPDATEHUB_LOG_LEVEL=4) still format the same pointers with %s in a LOG_DBG() loop that runs before the new checks, so that variant remains in debug configurations only.7dCVE-2026-1123956.5 MED30.3%
——9Pillow is a Python imaging library. From 8.2.0 until 13.0.0, Pillow's tiled-TIFF decoder can read past the tile buffer while copying four-byte pixels. In _decodeTile, libtiff can return a tile allocation smaller than the required row stride multiplied by the tile length, and Pillow's stride-and-copy loop walks beyond that allocation. An attacker can supply a crafted tiled TIFF to an application that loads it. This can expose adjacent heap data in pixels or crash the process. This issue is fixed in version 13.0.0.1d