Vulnerabilities

Processing an incomplete post-handshake message for a QUIC connection can cause a panic.

QUIC connections do not set an upper bound on the amount of data buffered when reading post-handshake messages, allowing a malicious QUIC connection to cause unbounded memory growth. With fix, connections now consistently reject messages larger than 65KiB in size.

The go.mod toolchain directive, introduced in Go 1.21, can be leveraged to execute scripts and binaries relative to the root of the module when the "go" command was executed within the module. This applies to modules downloaded using the "go" command from the module proxy, as well as modules downloaded directly using VCS software.

The html/template package does not apply the proper rules for handling occurrences of "

The html/template package does not properly handle HTML-like "" comment tokens, nor hashbang "#!" comment tokens, in contexts. This may cause the template parser to improperly interpret the contents of contexts, causing actions to be improperly escaped. This may be leveraged to perform an XSS attack.

FieldPopupNewsletter Prestashop Module v1.0.0 was discovered to contain a reflected cross-site scripting (XSS) vulnerability via the callback parameter at ajax.php.

SolarView Compact

Hexo up to v7.0.0 (RC2) was discovered to contain an arbitrary file read vulnerability.

Injecting random data into the USB memory area on a General Motors (GM) Chevrolet Equinox 2021 Software. 2021.03.26 (build version) vehicle causes a Denial of Service (DoS) in the in-car infotainment system.

Issue summary: The POLY1305 MAC (message authentication code) implementation<br /> contains a bug that might corrupt the internal state of applications on the<br /> Windows 64 platform when running on newer X86_64 processors supporting the<br /> AVX512-IFMA instructions.<br /> <br /> Impact summary: If in an application that uses the OpenSSL library an attacker<br /> can influence whether the POLY1305 MAC algorithm is used, the application<br /> state might be corrupted with various application dependent consequences.<br /> <br /> The POLY1305 MAC (message authentication code) implementation in OpenSSL does<br /> not save the contents of non-volatile XMM registers on Windows 64 platform<br /> when calculating the MAC of data larger than 64 bytes. Before returning to<br /> the caller all the XMM registers are set to zero rather than restoring their<br /> previous content. The vulnerable code is used only on newer x86_64 processors<br /> supporting the AVX512-IFMA instructions.<br /> <br /> The consequences of this kind of internal application state corruption can<br /> be various - from no consequences, if the calling application does not<br /> depend on the contents of non-volatile XMM registers at all, to the worst<br /> consequences, where the attacker could get complete control of the application<br /> process. However given the contents of the registers are just zeroized so<br /> the attacker cannot put arbitrary values inside, the most likely consequence,<br /> if any, would be an incorrect result of some application dependent<br /> calculations or a crash leading to a denial of service.<br /> <br /> The POLY1305 MAC algorithm is most frequently used as part of the<br /> CHACHA20-POLY1305 AEAD (authenticated encryption with associated data)<br /> algorithm. The most common usage of this AEAD cipher is with TLS protocol<br /> versions 1.2 and 1.3 and a malicious client can influence whether this AEAD<br /> cipher is used by the server. This implies that server applications using<br /> OpenSSL can be potentially impacted. However we are currently not aware of<br /> any concrete application that would be affected by this issue therefore we<br /> consider this a Low severity security issue.<br /> <br /> As a workaround the AVX512-IFMA instructions support can be disabled at<br /> runtime by setting the environment variable OPENSSL_ia32cap:<br /> <br /> OPENSSL_ia32cap=:~0x200000<br /> <br /> The FIPS provider is not affected by this issue.

<br /> An incorrect permission check in Qualys Container Scanning Connector Plugin 1.6.2.6 and earlier allows attackers with global Item/Configure permission (while lacking Item/Configure permission on any particular job) to enumerate credentials IDs of credentials stored in Jenkins and to connect to an attacker-specified URL using attacker-specified credentials IDs, capturing credentials stored in Jenkins. <br /> <br />

Cloud foundry routing release versions prior to 0.278.0 are vulnerable to abuse of HTTP Hop-by-Hop Headers. An unauthenticated attacker can use this vulnerability for headers like B3 or X-B3-SpanID to affect the identification value recorded in the logs in foundations.<br />