Show filters
871 Total Results
Displaying 131-140 of 871
Sort by:
Attacker Value
Unknown

CVE-2014-125098

Disclosure Date: April 10, 2023 (last updated February 24, 2025)
A vulnerability was found in Dart http_server up to 0.9.5 and classified as problematic. Affected by this issue is the function VirtualDirectory of the file lib/src/virtual_directory.dart of the component Directory Listing Handler. The manipulation of the argument request.uri.path leads to cross site scripting. The attack may be launched remotely. Upgrading to version 0.9.6 is able to address this issue. The name of the patch is 27c1cbd8125bb0369e675eb72e48218496e48ffb. It is recommended to upgrade the affected component. The identifier of this vulnerability is VDB-225356.
Attacker Value
Unknown

CVE-2022-48367

Disclosure Date: March 12, 2023 (last updated February 24, 2025)
An issue was discovered in eZ Publish Ibexa Kernel before 7.5.28. Access control based on object state is mishandled.
Attacker Value
Unknown

CVE-2023-26281

Disclosure Date: March 01, 2023 (last updated February 24, 2025)
IBM HTTP Server 8.5 used by IBM WebSphere Application Server could allow a remote user to cause a denial of service using a specially crafted URL. IBM X-Force ID: 248296.
Attacker Value
Unknown

CVE-2023-27371

Disclosure Date: February 28, 2023 (last updated February 24, 2025)
GNU libmicrohttpd before 0.9.76 allows remote DoS (Denial of Service) due to improper parsing of a multipart/form-data boundary in the postprocessor.c MHD_create_post_processor() method. This allows an attacker to remotely send a malicious HTTP POST packet that includes one or more '\0' bytes in a multipart/form-data boundary field, which - assuming a specific heap layout - will result in an out-of-bounds read and a crash in the find_boundary() function.
Attacker Value
Unknown

CVE-2022-41723

Disclosure Date: February 28, 2023 (last updated February 24, 2025)
A maliciously crafted HTTP/2 stream could cause excessive CPU consumption in the HPACK decoder, sufficient to cause a denial of service from a small number of small requests.
Attacker Value
Unknown

CVE-2022-25906

Disclosure Date: February 01, 2023 (last updated February 24, 2025)
All versions of the package is-http2 are vulnerable to Command Injection due to missing input sanitization or other checks, and sandboxes being employed to the isH2 function.
Attacker Value
Unknown

CVE-2022-25881

Disclosure Date: January 31, 2023 (last updated February 24, 2025)
This affects versions of the package http-cache-semantics before 4.1.1. The issue can be exploited via malicious request header values sent to a server, when that server reads the cache policy from the request using this library.
Attacker Value
Unknown

CVE-2023-24623

Disclosure Date: January 30, 2023 (last updated February 24, 2025)
Paranoidhttp before 0.3.0 allows SSRF because [::] is equivalent to the 127.0.0.1 address, but does not match the filter for private addresses.
Attacker Value
Unknown

CVE-2023-0040

Disclosure Date: January 18, 2023 (last updated February 24, 2025)
Versions of Async HTTP Client prior to 1.13.2 are vulnerable to a form of targeted request manipulation called CRLF injection. This vulnerability was the result of insufficient validation of HTTP header field values before sending them to the network. Users are vulnerable if they pass untrusted data into HTTP header field values without prior sanitisation. Common use-cases here might be to place usernames from a database into HTTP header fields. This vulnerability allows attackers to inject new HTTP header fields, or entirely new requests, into the data stream. This can cause requests to be understood very differently by the remote server than was intended. In general, this is unlikely to result in data disclosure, but it can result in a number of logical errors and other misbehaviours.
Attacker Value
Unknown

CVE-2022-37436

Disclosure Date: January 17, 2023 (last updated February 24, 2025)
Prior to Apache HTTP Server 2.4.55, a malicious backend can cause the response headers to be truncated early, resulting in some headers being incorporated into the response body. If the later headers have any security purpose, they will not be interpreted by the client.