Vulnerabilities

code-projects Mobile Shop Management System 1.0 is vulnerable to File Upload in /ExAddProduct.php.

Issue summary: When using the low-level OCB API directly with AES-NI orother hardware-accelerated code paths, inputs whose length is not a multipleof 16 bytes can leave the final partial block unencrypted and unauthenticated.Impact summary: The trailing 1-15 bytes of a message may be exposed incleartext on encryption and are not covered by the authentication tag,allowing an attacker to read or tamper with those bytes without detection.The low-level OCB encrypt and decrypt routines in the hardware-acceleratedstream path process full 16-byte blocks but do not advance the input/outputpointers. The subsequent tail-handling code then operates on the originalbase pointers, effectively reprocessing the beginning of the buffer whileleaving the actual trailing bytes unprocessed. The authentication checksumalso excludes the true tail bytes.However, typical OpenSSL consumers using EVP are not affected because thehigher-level EVP and provider OCB implementations split inputs so that fullblocks and trailing partial blocks are processed in separate calls, avoidingthe problematic code path. Additionally, TLS does not use OCB ciphersuites.The vulnerability only affects applications that call the low-levelCRYPTO_ocb128_encrypt() or CRYPTO_ocb128_decrypt() functions directly withnon-block-aligned lengths in a single call on hardware-accelerated builds.For these reasons the issue was assessed as Low severity.The FIPS modules in 3.6, 3.5, 3.4, 3.3, 3.2, 3.1 and 3.0 are not affectedby this issue, as OCB mode is not a FIPS-approved algorithm.OpenSSL 3.6, 3.5, 3.4, 3.3, 3.0 and 1.1.1 are vulnerable to this issue.OpenSSL 1.0.2 is not affected by this issue.

xrdp is an open source RDP server. xrdp before v0.10.5 contains an unauthenticated stack-based buffer overflow vulnerability. The issue stems from improper bounds checking when processing user domain information during the connection sequence. If exploited, the vulnerability could allow remote attackers to execute arbitrary code on the target system. The vulnerability allows an attacker to overwrite the stack buffer and the return address, which could theoretically be used to redirect the execution flow. The impact of this vulnerability is lessened if a compiler flag has been used to build the xrdp executable with stack canary protection. If this is the case, a second vulnerability would need to be used to leak the stack canary value. Upgrade to version 0.10.5 to receive a patch. Additionally, do not rely on stack canary protection on production systems.

A denial-of-service vulnerability exists in the NetX IPv6 component functionality of Eclipse ThreadX NetX Duo. A specially crafted network packet of "Packet Too Big" with more than 15 different source address can lead to denial of service. An attacker can send a malicious packet to trigger this vulnerability.

Issue summary: A TLS 1.3 connection using certificate compression can be<br /> forced to allocate a large buffer before decompression without checking<br /> against the configured certificate size limit.<br /> <br /> Impact summary: An attacker can cause per-connection memory allocations of<br /> up to approximately 22 MiB and extra CPU work, potentially leading to<br /> service degradation or resource exhaustion (Denial of Service).<br /> <br /> In affected configurations, the peer-supplied uncompressed certificate<br /> length from a CompressedCertificate message is used to grow a heap buffer<br /> prior to decompression. This length is not bounded by the max_cert_list<br /> setting, which otherwise constrains certificate message sizes. An attacker<br /> can exploit this to cause large per-connection allocations followed by<br /> handshake failure. No memory corruption or information disclosure occurs.<br /> <br /> This issue only affects builds where TLS 1.3 certificate compression is<br /> compiled in (i.e., not OPENSSL_NO_COMP_ALG) and at least one compression<br /> algorithm (brotli, zlib, or zstd) is available, and where the compression<br /> extension is negotiated. Both clients receiving a server CompressedCertificate<br /> and servers in mutual TLS scenarios receiving a client CompressedCertificate<br /> are affected. Servers that do not request client certificates are not<br /> vulnerable to client-initiated attacks.<br /> <br /> Users can mitigate this issue by setting SSL_OP_NO_RX_CERTIFICATE_COMPRESSION<br /> to disable receiving compressed certificates.<br /> <br /> The FIPS modules in 3.6, 3.5, 3.4 and 3.3 are not affected by this issue,<br /> as the TLS implementation is outside the OpenSSL FIPS module boundary.<br /> <br /> OpenSSL 3.6, 3.5, 3.4 and 3.3 are vulnerable to this issue.<br /> <br /> OpenSSL 3.0, 1.1.1 and 1.0.2 are not affected by this issue.

Issue summary: Writing large, newline-free data into a BIO chain using the<br /> line-buffering filter where the next BIO performs short writes can trigger<br /> a heap-based out-of-bounds write.<br /> <br /> Impact summary: This out-of-bounds write can cause memory corruption which<br /> typically results in a crash, leading to Denial of Service for an application.<br /> <br /> The line-buffering BIO filter (BIO_f_linebuffer) is not used by default in<br /> TLS/SSL data paths. In OpenSSL command-line applications, it is typically<br /> only pushed onto stdout/stderr on VMS systems. Third-party applications that<br /> explicitly use this filter with a BIO chain that can short-write and that<br /> write large, newline-free data influenced by an attacker would be affected.<br /> However, the circumstances where this could happen are unlikely to be under<br /> attacker control, and BIO_f_linebuffer is unlikely to be handling non-curated<br /> data controlled by an attacker. For that reason the issue was assessed as<br /> Low severity.<br /> <br /> The FIPS modules in 3.6, 3.5, 3.4, 3.3 and 3.0 are not affected by this issue,<br /> as the BIO implementation is outside the OpenSSL FIPS module boundary.<br /> <br /> OpenSSL 3.6, 3.5, 3.4, 3.3, 3.0, 1.1.1 and 1.0.2 are vulnerable to this issue.

Issue summary: Parsing CMS AuthEnvelopedData message with maliciously<br /> crafted AEAD parameters can trigger a stack buffer overflow.<br /> <br /> Impact summary: A stack buffer overflow may lead to a crash, causing Denial<br /> of Service, or potentially remote code execution.<br /> <br /> When parsing CMS AuthEnvelopedData structures that use AEAD ciphers such as<br /> AES-GCM, the IV (Initialization Vector) encoded in the ASN.1 parameters is<br /> copied into a fixed-size stack buffer without verifying that its length fits<br /> the destination. An attacker can supply a crafted CMS message with an<br /> oversized IV, causing a stack-based out-of-bounds write before any<br /> authentication or tag verification occurs.<br /> <br /> Applications and services that parse untrusted CMS or PKCS#7 content using<br /> AEAD ciphers (e.g., S/MIME AuthEnvelopedData with AES-GCM) are vulnerable.<br /> Because the overflow occurs prior to authentication, no valid key material<br /> is required to trigger it. While exploitability to remote code execution<br /> depends on platform and toolchain mitigations, the stack-based write<br /> primitive represents a severe risk.<br /> <br /> The FIPS modules in 3.6, 3.5, 3.4, 3.3 and 3.0 are not affected by this<br /> issue, as the CMS implementation is outside the OpenSSL FIPS module<br /> boundary.<br /> <br /> OpenSSL 3.6, 3.5, 3.4, 3.3 and 3.0 are vulnerable to this issue.<br /> <br /> OpenSSL 1.1.1 and 1.0.2 are not affected by this issue.

Issue summary: PBMAC1 parameters in PKCS#12 files are missing validation<br /> which can trigger a stack-based buffer overflow, invalid pointer or NULL<br /> pointer dereference during MAC verification.<br /> <br /> Impact summary: The stack buffer overflow or NULL pointer dereference may<br /> cause a crash leading to Denial of Service for an application that parses<br /> untrusted PKCS#12 files. The buffer overflow may also potentially enable<br /> code execution depending on platform mitigations.<br /> <br /> When verifying a PKCS#12 file that uses PBMAC1 for the MAC, the PBKDF2<br /> salt and keylength parameters from the file are used without validation.<br /> If the value of keylength exceeds the size of the fixed stack buffer used<br /> for the derived key (64 bytes), the key derivation will overflow the buffer.<br /> The overflow length is attacker-controlled. Also, if the salt parameter is<br /> not an OCTET STRING type this can lead to invalid or NULL pointer<br /> dereference.<br /> <br /> Exploiting this issue requires a user or application to process<br /> a maliciously crafted PKCS#12 file. It is uncommon to accept untrusted<br /> PKCS#12 files in applications as they are usually used to store private<br /> keys which are trusted by definition. For this reason the issue was assessed<br /> as Moderate severity.<br /> <br /> The FIPS modules in 3.6, 3.5 and 3.4 are not affected by this issue, as<br /> PKCS#12 processing is outside the OpenSSL FIPS module boundary.<br /> <br /> OpenSSL 3.6, 3.5 and 3.4 are vulnerable to this issue.<br /> <br /> OpenSSL 3.3, 3.0, 1.1.1 and 1.0.2 are not affected by this issue as they do<br /> not support PBMAC1 in PKCS#12.

Issue summary: If an application using the SSL_CIPHER_find() function in<br /> a QUIC protocol client or server receives an unknown cipher suite from<br /> the peer, a NULL dereference occurs.<br /> <br /> Impact summary: A NULL pointer dereference leads to abnormal termination of<br /> the running process causing Denial of Service.<br /> <br /> Some applications call SSL_CIPHER_find() from the client_hello_cb callback<br /> on the cipher ID received from the peer. If this is done with an SSL object<br /> implementing the QUIC protocol, NULL pointer dereference will happen if<br /> the examined cipher ID is unknown or unsupported.<br /> <br /> As it is not very common to call this function in applications using the QUIC <br /> protocol and the worst outcome is Denial of Service, the issue was assessed<br /> as Low severity.<br /> <br /> The vulnerable code was introduced in the 3.2 version with the addition<br /> of the QUIC protocol support.<br /> <br /> The FIPS modules in 3.6, 3.5, 3.4 and 3.3 are not affected by this issue,<br /> as the QUIC implementation is outside the OpenSSL FIPS module boundary.<br /> <br /> OpenSSL 3.6, 3.5, 3.4 and 3.3 are vulnerable to this issue.<br /> <br /> OpenSSL 3.0, 1.1.1 and 1.0.2 are not affected by this issue.

Issue summary: The &amp;#39;openssl dgst&amp;#39; command-line tool silently truncates input<br /> data to 16MB when using one-shot signing algorithms and reports success instead<br /> of an error.<br /> <br /> Impact summary: A user signing or verifying files larger than 16MB with<br /> one-shot algorithms (such as Ed25519, Ed448, or ML-DSA) may believe the entire<br /> file is authenticated while trailing data beyond 16MB remains unauthenticated.<br /> <br /> When the &amp;#39;openssl dgst&amp;#39; command is used with algorithms that only support<br /> one-shot signing (Ed25519, Ed448, ML-DSA-44, ML-DSA-65, ML-DSA-87), the input<br /> is buffered with a 16MB limit. If the input exceeds this limit, the tool<br /> silently truncates to the first 16MB and continues without signaling an error,<br /> contrary to what the documentation states. This creates an integrity gap where<br /> trailing bytes can be modified without detection if both signing and<br /> verification are performed using the same affected codepath.<br /> <br /> The issue affects only the command-line tool behavior. Verifiers that process<br /> the full message using library APIs will reject the signature, so the risk<br /> primarily affects workflows that both sign and verify with the affected<br /> &amp;#39;openssl dgst&amp;#39; command. Streaming digest algorithms for &amp;#39;openssl dgst&amp;#39; and<br /> library users are unaffected.<br /> <br /> The FIPS modules in 3.5 and 3.6 are not affected by this issue, as the<br /> command-line tools are outside the OpenSSL FIPS module boundary.<br /> <br /> OpenSSL 3.5 and 3.6 are vulnerable to this issue.<br /> <br /> OpenSSL 3.4, 3.3, 3.0, 1.1.1 and 1.0.2 are not affected by this issue.

Buffer Overflow vulnerability in libpng 1.6.43-1.6.46 allows a local attacker to cause a denial of service via the pngimage with AddressSanitizer (ASan), the program leaks memory in various locations, eventually leading to high memory usage and causing the program to become unresponsive

Buffer Overflow vulnerability in libpng 1.6.43-1.6.46 allows a local attacker to cause a denial of service via png_create_read_struct() function.