Libmseed
Monthly
Heap out-of-bounds read in EarthScope libmseed through 3.5.4 occurs when an application passes a truncated 40-to-47-byte miniSEED 2 record that still satisfies the MS2_ISVALIDHEADER check to msr3_parse() or ms3_detect(); the parser then reads the blockette-offset field beyond the end of the allocated buffer, over-reading up to 8 bytes and potentially crashing the process. Publicly available exploit code exists (a detailed write-up and the upstream fix are both linked from the CVE references), but CISA KEV does not list this issue, so there is no confirmation of active exploitation. Impact is limited to a denial of service (process crash) with no confidentiality or integrity effect; exploitation is local and requires passive user interaction, since a victim application or automated ingest pipeline must actually feed the malformed record to the parser - no authentication is required.
Heap out-of-bounds read in EarthScope libmseed through 3.5.4 occurs when an application passes a truncated 40-to-47-byte miniSEED 2 record that still satisfies the MS2_ISVALIDHEADER check to msr3_parse() or ms3_detect(); the parser then reads the blockette-offset field beyond the end of the allocated buffer, over-reading up to 8 bytes and potentially crashing the process. Publicly available exploit code exists (a detailed write-up and the upstream fix are both linked from the CVE references), but CISA KEV does not list this issue, so there is no confirmation of active exploitation. Impact is limited to a denial of service (process crash) with no confidentiality or integrity effect; exploitation is local and requires passive user interaction, since a victim application or automated ingest pipeline must actually feed the malformed record to the parser - no authentication is required.