Skip to content
OpenAdvisories

Archive

29 May 2020

Vulnerabilities first published on this day (UTC), newest first.

8 results · Clear filters · Feed

  • Low 3.7

    Out-of-bound read in FreeRDP

    In FreeRDP before 2.1.0, there is an out-of-bound read in irp functions (parallel_process_irp_create, serial_process_irp_create, drive_process_irp_write, printer_process_irp_write, rdpei_recv_pdu, serial_process_irp_write). This has been fixed in 2.1.0.

  • Low 3.1

    Out-of-bound read in FreeRDP

    In FreeRDP less than or equal to 2.0.0, there is an out-of-bound read in ntlm_read_NegotiateMessage. This has been fixed in 2.1.0.

  • Low 2.2

    Out-of-bounds Read in FreeRDP

    In FreeRDP less than or equal to 2.0.0, there is an out-of-bound data read from memory in clear_decompress_subcode_rlex, visualized on screen as color. This has been patched in 2.1.0.

  • Low 3.1

    Out-of-bounds Read in FreeRDP `ntlm_read_ntlm_v2_response`

    In FreeRDP less than or equal to 2.0.0, there is an out-of-bound read in ntlm_read_ntlm_v2_client_challenge that reads up to 28 bytes out-of-bound to an internal structure. This has been fixed in 2.1.0.

  • Low 2.2

    Out-of-bounds Read in FreeRDP

    In FreeRDP less than or equal to 2.0.0, there is an out-of-bounds read in rfx_process_message_tileset. Invalid data fed to RFX decoder results in garbage on screen (as colors). This has been patched in 2.1.0.

  • Low 3.1

    Out-of-bounds Read in FreeRDP

    In FreeRDP less than or equal to 2.0.0, there is an out-of-bound read in ntlm_read_AuthenticateMessage. This has been fixed in 2.1.0.

  • Low 2.6

    Out-of-bounds Read in FreeRDP

    In FreeRDP before 2.1.0, there is an out-of-bounds read in cliprdr_read_format_list. Clipboard format data read (by client or server) might read data out-of-bounds. This has been fixed in 2.1.0.

  • Low 2.2

    Improper Validation of Array Index in FreeRDP

    In FreeRDP less than or equal to 2.0.0, an outside controlled array index is used unchecked for data used as configuration for sound backend (alsa, oss, pulse, ...). The most likely outcome is a crash of the client instance followed by no or distorted sound o…