VYPR

rpm package

suse/libsoup&distro=SUSE Manager Server 4.3

pkg:rpm/suse/libsoup&distro=SUSE%20Manager%20Server%204.3

Vulnerabilities (20)

  • CVE-2025-4969MedMay 21, 2025
    affected < 3.0.4-150400.3.10.1fixed 3.0.4-150400.3.10.1

    A vulnerability was found in the libsoup package. This flaw stems from its failure to correctly verify the termination of multipart HTTP messages. This can allow a remote attacker to send a specially crafted multipart HTTP body, causing the libsoup-consuming server to read beyond

  • CVE-2025-4948HigMay 19, 2025
    affected < 3.0.4-150400.3.10.1fixed 3.0.4-150400.3.10.1

    A flaw was found in the soup_multipart_new_from_message() function of the libsoup HTTP library, which is commonly used by GNOME and other applications to handle web communications. The issue occurs when the library processes specially crafted multipart messages. Due to improper v

  • CVE-2025-4476MedMay 16, 2025
    affected < 3.0.4-150400.3.10.1fixed 3.0.4-150400.3.10.1

    A denial-of-service vulnerability has been identified in the libsoup HTTP client library. This flaw can be triggered when a libsoup client receives a 401 (Unauthorized) HTTP response containing a specifically crafted domain parameter within the WWW-Authenticate header. Processing

  • CVE-2025-46421MedApr 24, 2025
    affected < 3.0.4-150400.3.7.1fixed 3.0.4-150400.3.7.1

    A flaw was found in libsoup. When libsoup clients encounter an HTTP redirect, they mistakenly send the HTTP Authorization header to the new host that the redirection points to. This allows the new host to impersonate the user to the original host that issued the redirect.

  • CVE-2025-46420MedApr 24, 2025
    affected < 3.0.4-150400.3.7.1fixed 3.0.4-150400.3.7.1

    A flaw was found in libsoup. It is vulnerable to memory leaks in the soup_header_parse_quality_list() function when parsing a quality list that contains elements with all zeroes.

  • CVE-2025-32914HigApr 14, 2025
    affected < 3.0.4-150400.3.7.1fixed 3.0.4-150400.3.7.1

    A flaw was found in libsoup, where the soup_multipart_new_from_message() function is vulnerable to an out-of-bounds read. This flaw allows a malicious HTTP client to induce the libsoup server to read out of bounds.

  • CVE-2025-32912MedApr 14, 2025
    affected < 3.0.4-150400.3.7.1fixed 3.0.4-150400.3.7.1

    A flaw was found in libsoup, where SoupAuthDigest is vulnerable to a NULL pointer dereference. The HTTP server may cause the libsoup client to crash.

  • CVE-2025-32910MedApr 14, 2025
    affected < 3.0.4-150400.3.7.1fixed 3.0.4-150400.3.7.1

    A flaw was found in libsoup, where soup_auth_digest_authenticate() is vulnerable to a NULL pointer dereference. This issue may cause the libsoup client to crash.

  • CVE-2025-32909MedApr 14, 2025
    affected < 3.0.4-150400.3.7.1fixed 3.0.4-150400.3.7.1

    A flaw was found in libsoup. SoupContentSniffer may be vulnerable to a NULL pointer dereference in the sniff_mp4 function. The HTTP server may cause the libsoup client to crash.

  • CVE-2025-32913HigApr 14, 2025
    affected < 3.0.4-150400.3.7.1fixed 3.0.4-150400.3.7.1

    A flaw was found in libsoup, where the soup_message_headers_get_content_disposition() function is vulnerable to a NULL pointer dereference. This flaw allows a malicious HTTP peer to crash a libsoup client or server that uses this function.

  • CVE-2025-32907MedApr 14, 2025
    affected < 3.0.4-150400.3.7.1fixed 3.0.4-150400.3.7.1

    A flaw was found in libsoup. The implementation of HTTP range requests is vulnerable to a resource consumption attack. This flaw allows a malicious client to request the same range many times in a single HTTP request, causing the server to use large amounts of memory. This does n

  • CVE-2025-32906HigApr 14, 2025
    affected < 3.0.4-150400.3.7.1fixed 3.0.4-150400.3.7.1

    A flaw was found in libsoup, where the soup_headers_parse_request() function may be vulnerable to an out-of-bound read. This flaw allows a malicious user to use a specially crafted HTTP request to crash the HTTP server.

  • CVE-2025-32053MedApr 3, 2025
    affected < 3.0.4-150400.3.7.1fixed 3.0.4-150400.3.7.1

    A flaw was found in libsoup. A vulnerability in sniff_feed_or_html() and skip_insignificant_space() functions may lead to a heap buffer over-read.

  • CVE-2025-32052MedApr 3, 2025
    affected < 3.0.4-150400.3.7.1fixed 3.0.4-150400.3.7.1

    A flaw was found in libsoup. A vulnerability in the sniff_unknown() function may lead to heap buffer over-read.

  • CVE-2025-32051MedApr 3, 2025
    affected < 3.0.4-150400.3.7.1fixed 3.0.4-150400.3.7.1

    A flaw was found in libsoup. The libsoup soup_uri_decode_data_uri() function may crash when processing malformed data URI. This flaw allows an attacker to cause a denial of service (DoS).

  • CVE-2025-32050MedApr 3, 2025
    affected < 3.0.4-150400.3.7.1fixed 3.0.4-150400.3.7.1

    A flaw was found in libsoup. The libsoup append_param_quoted() function may contain an overflow bug resulting in a buffer under-read.

  • CVE-2025-2784Apr 3, 2025
    affected < 3.0.4-150400.3.7.1fixed 3.0.4-150400.3.7.1

    A flaw was found in libsoup. The package is vulnerable to a heap buffer over-read when sniffing content via the skip_insight_whitespace() function. Libsoup clients may read one byte out-of-bounds in response to a crafted HTTP response by an HTTP server.

  • CVE-2024-52532Nov 11, 2024
    affected < 3.0.4-150400.3.3.1fixed 3.0.4-150400.3.3.1

    GNOME libsoup before 3.6.1 has an infinite loop, and memory consumption. during the reading of certain patterns of WebSocket data from clients.

  • CVE-2024-52531Nov 11, 2024
    affected < 3.0.4-150400.3.3.1fixed 3.0.4-150400.3.3.1

    GNOME libsoup before 3.6.1 allows a buffer overflow in applications that perform conversion to UTF-8 in soup_header_parse_param_list_strict. There is a plausible way to reach this remotely via soup_message_headers_get_content_type (e.g., an application may want to retrieve the co

  • CVE-2024-52530Nov 11, 2024
    affected < 3.0.4-150400.3.3.1fixed 3.0.4-150400.3.3.1

    GNOME libsoup before 3.6.0 allows HTTP request smuggling in some configurations because '\0' characters at the end of header names are ignored, i.e., a "Transfer-Encoding\0: chunked" header is treated the same as a "Transfer-Encoding: chunked" header.