Enviar #520180: Open Source libgsf <=1.14.53 Uninitalized Heap Read (gsf_base64_encode_simple)información

TítuloOpen Source libgsf <=1.14.53 Uninitalized Heap Read (gsf_base64_encode_simple)
DescripciónThe vulnerability arises because the null terminator is written based on an unsynchronized size argument, allowing uninitialized heap data to be included in the base64 encoded output. guint8 * gsf_base64_encode_simple (guint8 const *data, size_t len) { guint8 *out; int state = 0; guint save = 0; gboolean break_lines = TRUE; /* This differs from g_base64_encode */ size_t outlen = len * 4 / 3 + 5; // Compute the estimated output buffer size. if (break_lines) outlen += outlen / 72 + 1; // Account for line breaks in Base64 output. out = g_new (guint8, outlen); // Allocate the buffer on the heap. outlen = gsf_base64_encode_close (data, len, break_lines, out, &state, &save); // Here, `out[outlen] = '\0';` assumes that `outlen` is a valid index within `out`, // but `outlen` is calculated based on the actual bytes written, which might be // *less than* the originally allocated buffer size. If `gsf_base64_encode_close` // did not write as much data as expected (e.g., due to input size), `outlen` // might point beyond the valid written range, leaving uninitialized bytes in `out`. out[outlen] = '\0'; return out; }
Usuario ninpwn (UID 82253)
Sumisión2025-03-13 21:17 (hace 1 Año)
Moderación2025-03-24 13:46 (11 days later)
EstadoAceptado
Entrada de VulDB300740 [GNOME libgsf hasta 1.14.53 gsf_base64_encode_simple size divulgación de información]
Puntos17

Want to know what is going to be exploited?

We predict KEV entries!