Sandipan Roy

A flaw exists in the `AwsAlbKeyResolver` of SmallRye JWT, used for verifying JSON Web Tokens signed by AWS Application Load Balancers. When the `AWS ALB` key provider is active, the resolver builds the key-fetch URL by concatenating the `kid` header value from an incoming JWT without sanitizing path traversal characters or query-string separators. This allows an unauthenticated remote attacker to trigger GET requests to arbitrary paths on the same origin as the configured key endpoint, potentially exposing non-public endpoints or internal data before the JWT signature is verified. This is a Server-Side Request Forgery (SSRF), where the server is tricked into making requests to its own internal resources.

Insufficient validation of client-controlled JMX service URLs in the JSR-160 proxy functionality allows a bypass of the existing denylist. The proxy accepts a `target.url` value from a POST request and passes it to `JMXServiceURL` and `JMXConnectorFactory` to establish a remote JMX connection. Because the denylist only rejects URLs matching `service:jmx:rmi:///jndi/ldap:.*`, attackers can use alternative forms such as `ldaps://` schemes or LDAP URLs with a non-empty JMX host component. This can force the Jolokia agent JVM to perform a JNDI (Java Naming and Directory Interface) lookup against an attacker-controlled LDAP endpoint, potentially leading to server-side request forgery (SSRF), leakage of JMX credentials, or remote code execution.

A flaw in the sos clean utility within the sos package allows a local attacker to create or overwrite arbitrary files. The issue stems from a path traversal flaw during the extraction of tar archives, where symlink and hardlink targets are not properly validated. This allows an attacker to write files to any location on the system using the privileges of the sos clean process, which typically executes as root.

An issue exists in the tarball processing of rpmbuild. When operating in tarball mode (such as -ts, -ta, or -tb), the `getTarSpec()` function in tools/rpmbuild.cc passes a member name from a crafted source archive to `rpmExpand()` within a %{basename:...} macro expression. This allows an attacker to inject RPM macros, including Lua expressions, leading to arbitrary code execution with the privileges of the user running the process.

An out-of-bounds buffer operation exists in the xfrm-ESP and RxRPC subsystems. Unsafe in-place cryptographic processing of shared socket buffer fragments allows a low-privileged local attacker to corrupt page-cache contents of readable files, including sensitive system files, and gain root privileges. The xfrm-ESP variant requires the creation of a network namespace or an unprivileged user, while the RxRPC variant requires the `rxrpc` module to be available on the target system. The issue occurs because IPv4/IPv6 datagram append paths failed to set the `SKBFL SHARED FRAG` flag when splicing pages into UDP skbs, causing ESP input to decrypt data in place over fragments not privately owned by the skb.

A flaw in the oFono interface for working with mobile connectivity is related to a buffer overflow in the `decode deliver()` function during SMS decoding. This issue can be exploited by a remote attacker to access confidential data, compromise its integrity, and cause a denial of service. The attack scenario is assumed to be accessible from a compromised modem, a malicious base station, or via SMS. A bound check for the `memcpy` length in `decode submit()` was forgotten in `decode deliver()`, leading to the stack overflow bug.

A vulnerability was found related to the response times to malformed ciphertexts in RSA-PSK ClientKeyExchange, which differ from response times of ciphertexts with correct PKCS#1 v1.5 padding. This issue is associated with information disclosure through inconsistency. Exploitation of the vulnerability may allow a remote attacker to access confidential data.

A flaw was found in 3Scale Admin Portal. If a user logs out from the personal tokens page and then presses the back button in the browser, the tokens page is rendered from the browser cache, potentially allowing an attacker to disclose protected information.

A security issue occurs as the Hot Rod client and Netty do not enable hostname validation when using TLS, possibly resulting in a man-in-the-middle (MITM) attack. This issue can allow a remote attacker to execute a man-in-the-middle attack.

A vulnerability was found in the implementation of the TLS protocol in the Quarkus Java framework. This issue is related to the insufficient reliability of encryption when using the quarkus.http.ssl.protocols configuration. The vulnerability occurs because the TLS protocol configured with quarkus.http.ssl.protocols is not enforced, allowing a client to force the selection of a weaker supported TLS protocol. This could potentially allow a remote attacker to gain unauthorized access to protected information.

A security flaw in OpenSC causes a buffer overrun vulnerability in `pkcs15` `cardos have verifyrc package`. An attacker can supply a smart card package with malformed ASN1 context. The `cardos have verifyrc package` function scans the ASN1 buffer for 2 tags, where the remaining length is wrongly calculated due to a moved starting pointer. This leads to a possible heap-based buffer out of bounds read. In cases where ASAN is enabled while compiling, this causes a crash. Further information leak or more damage is possible.

The issue is related to a null pointer dereference in the `ber memalloc x()` function. This can be exploited by a remote attacker to cause a denial of service. The estimated number of potentially affected devices worldwide is not available. There is no information about real-world incidents where this issue was exploited. The technical details about exploitation include a null pointer dereference in the `ber memalloc x()` function.

A flaw was found in ofono, an Open Source Telephony on Linux, where a stack overflow bug is triggered within the `decode status report()` function during SMS decoding. The attack scenario is assumed to be accessible from a compromised modem, a malicious base station, or just SMS. There is a bound check for the `memcpy` length in `decode submit()`, but it was forgotten in `decode status report()`. This vulnerability may allow a remote attacker to access confidential data, disrupt its integrity, and cause a denial of service.

A flaw was found in ofono, an Open Source Telephony on Linux, where a stack overflow bug is triggered within the `decode deliver report()` function during SMS decoding. This issue is related to the parsing of SMS PDUs and can be exploited remotely without requiring authentication. The attack scenario is assumed to be accessible from a compromised modem, a malicious base station, or via SMS. A bound check for the `memcpy` length was forgotten in `decode deliver report()`, unlike in `decode submit()`.

A flaw in oFono, an Open Source Telephony on Linux, is related to a stack overflow bug triggered within the `decode submit report()` function during SMS decoding in PDU format. This issue may allow a remote attacker to execute arbitrary code. The attack scenario is assumed to be accessible from a compromised modem, a malicious base station, or just SMS. There is a bound check for the `memcpy` length in `decode submit()`, but it was forgotten in `decode submit report()`.

A flaw was found in ofono, an Open Source Telephony on Linux, where a stack overflow bug is triggered within the `sms decode address field()` function during the SMS PDU decoding. This issue can be exploited remotely, potentially allowing an attacker to execute arbitrary code. The attack scenario is assumed to be accessible from a compromised modem, a malicious base station, or just SMS.

A security flaw in the libtiff library causes a heap buffer overflow in the `extractContigSamples32bits()` function, located in tiffcrop.c. This issue can be exploited by an attacker using specially crafted data, potentially leading to a denial of service.

The undertow client does not check the server identity presented by the server certificate in https connections, which is a compulsory step that should be performed by default in https and http/2. This issue affects the TLS client protocol.

The issue is related to the Quarkus Form Authentication session cookie Path attribute being set to `/`, which may lead to a cross-site attack and potentially result in Information Disclosure. This can be prevented by using the Quarkus CSRF Prevention feature. The vulnerability is also associated with a lack of protection for the web page structure, which could allow a remote attacker to conduct a cross-site scripting (XSS) attack.

A flaw was found in codeplex-codehaus, allowing a directory traversal attack to access files and directories stored outside the intended folder. By manipulating files with `../` sequences and their variations or by using absolute file paths, it may be possible to access arbitrary files and directories stored on the file system, including application source code, configuration, and other critical system files.