Vulnerabilities

Helm is a tool that streamlines installing and managing Kubernetes applications.`getHostByName` is a Helm template function introduced in Helm v3. The function is able to accept a hostname and return an IP address for that hostname. To get the IP address the function performs a DNS lookup. The DNS lookup happens when used with `helm install|upgrade|template` or when the Helm SDK is used to render a chart. Information passed into the chart can be disclosed to the DNS servers used to lookup the IP address. For example, a malicious chart could inject `getHostByName` into a chart in order to disclose values to a malicious DNS server. The issue has been fixed in Helm 3.11.1. Prior to using a chart with Helm verify the `getHostByName` function is not being used in a template to disclose any information you do not want passed to DNS servers.

Nextcloud office/richdocuments is an office suit for the nextcloud server platform. In affected versions the Collabora integration can be tricked to provide access to any file without proper permission validation. As a result any user with access to Collabora can obtain the content of other users files. It is recommended that the Nextcloud Office App (Collabora Integration) is updated to 7.0.2 (Nextcloud 25), 6.3.2 (Nextcloud 24), 5.0.10 (Nextcloud 23), 4.2.9 (Nextcloud 21-22), or 3.8.7 (Nextcloud 15-20). There are no known workarounds for this issue.

When GELI reads a key file from standard input, it does not reuse the key file to initialize multiple providers at once resulting in the second and subsequent devices silently using a NULL key as the user key file. If a user only uses a key file without a user passphrase, the master key is encrypted with an empty key file allowing trivial recovery of the master key.<br />

Tinacms is a Git-backed headless content management system with support for visual editing. Sites being built with @tinacms/cli &gt;= 1.0.0 &amp;&amp;

opentelemetry-go-contrib is a collection of extensions for OpenTelemetry-Go. The v0.38.0 release of `go.opentelemetry.io/contrib/instrumentation/net/http/otelhttp` uses the `httpconv.ServerRequest` function to annotate metric measurements for the `http.server.request_content_length`, `http.server.response_content_length`, and `http.server.duration` instruments. The `ServerRequest` function sets the `http.target` attribute value to be the whole request URI (including the query string)[^1]. The metric instruments do not "forget" previous measurement attributes when `cumulative` temporality is used, this means the cardinality of the measurements allocated is directly correlated with the unique URIs handled. If the query string is constantly random, this will result in a constant increase in memory allocation that can be used in a denial-of-service attack. This issue has been addressed in version 0.39.0. Users are advised to upgrade. There are no known workarounds for this issue.

The public API function BIO_new_NDEF is a helper function used for streaming<br /> ASN.1 data via a BIO. It is primarily used internally to OpenSSL to support the<br /> SMIME, CMS and PKCS7 streaming capabilities, but may also be called directly by<br /> end user applications.<br /> <br /> The function receives a BIO from the caller, prepends a new BIO_f_asn1 filter<br /> BIO onto the front of it to form a BIO chain, and then returns the new head of<br /> the BIO chain to the caller. Under certain conditions, for example if a CMS<br /> recipient public key is invalid, the new filter BIO is freed and the function<br /> returns a NULL result indicating a failure. However, in this case, the BIO chain<br /> is not properly cleaned up and the BIO passed by the caller still retains<br /> internal pointers to the previously freed filter BIO. If the caller then goes on<br /> to call BIO_pop() on the BIO then a use-after-free will occur. This will most<br /> likely result in a crash.<br /> <br /> <br /> <br /> This scenario occurs directly in the internal function B64_write_ASN1() which<br /> may cause BIO_new_NDEF() to be called and will subsequently call BIO_pop() on<br /> the BIO. This internal function is in turn called by the public API functions<br /> PEM_write_bio_ASN1_stream, PEM_write_bio_CMS_stream, PEM_write_bio_PKCS7_stream,<br /> SMIME_write_ASN1, SMIME_write_CMS and SMIME_write_PKCS7.<br /> <br /> Other public API functions that may be impacted by this include<br /> i2d_ASN1_bio_stream, BIO_new_CMS, BIO_new_PKCS7, i2d_CMS_bio_stream and<br /> i2d_PKCS7_bio_stream.<br /> <br /> The OpenSSL cms and smime command line applications are similarly affected.

An invalid pointer dereference on read can be triggered when an<br /> application tries to load malformed PKCS7 data with the<br /> d2i_PKCS7(), d2i_PKCS7_bio() or d2i_PKCS7_fp() functions.<br /> <br /> The result of the dereference is an application crash which could<br /> lead to a denial of service attack. The TLS implementation in OpenSSL<br /> does not call this function however third party applications might<br /> call these functions on untrusted data.

An invalid pointer dereference on read can be triggered when an<br /> application tries to check a malformed DSA public key by the<br /> EVP_PKEY_public_check() function. This will most likely lead<br /> to an application crash. This function can be called on public<br /> keys supplied from untrusted sources which could allow an attacker<br /> to cause a denial of service attack.<br /> <br /> The TLS implementation in OpenSSL does not call this function<br /> but applications might call the function if there are additional<br /> security requirements imposed by standards such as FIPS 140-3.

There is a type confusion vulnerability relating to X.400 address processing<br /> inside an X.509 GeneralName. X.400 addresses were parsed as an ASN1_STRING but<br /> the public structure definition for GENERAL_NAME incorrectly specified the type<br /> of the x400Address field as ASN1_TYPE. This field is subsequently interpreted by<br /> the OpenSSL function GENERAL_NAME_cmp as an ASN1_TYPE rather than an<br /> ASN1_STRING.<br /> <br /> When CRL checking is enabled (i.e. the application sets the<br /> X509_V_FLAG_CRL_CHECK flag), this vulnerability may allow an attacker to pass<br /> arbitrary pointers to a memcmp call, enabling them to read memory contents or<br /> enact a denial of service. In most cases, the attack requires the attacker to<br /> provide both the certificate chain and CRL, neither of which need to have a<br /> valid signature. If the attacker only controls one of these inputs, the other<br /> input must already contain an X.400 address as a CRL distribution point, which<br /> is uncommon. As such, this vulnerability is most likely to only affect<br /> applications which have implemented their own functionality for retrieving CRLs<br /> over a network.

A NULL pointer can be dereferenced when signatures are being<br /> verified on PKCS7 signed or signedAndEnveloped data. In case the hash<br /> algorithm used for the signature is known to the OpenSSL library but<br /> the implementation of the hash algorithm is not available the digest<br /> initialization will fail. There is a missing check for the return<br /> value from the initialization function which later leads to invalid<br /> usage of the digest API most likely leading to a crash.<br /> <br /> The unavailability of an algorithm can be caused by using FIPS<br /> enabled configuration of providers or more commonly by not loading<br /> the legacy provider.<br /> <br /> PKCS7 data is processed by the SMIME library calls and also by the<br /> time stamp (TS) library calls. The TLS implementation in OpenSSL does<br /> not call these functions however third party applications would be<br /> affected if they call these functions to verify signatures on untrusted<br /> data.

IBM API Connect 10.0.0.0 through 10.0.5.0, 10.0.1.0 through 10.0.1.7, and 2018.4.1.0 through 2018.4.1.20 is vulnerable to External Service Interaction attack, caused by improper validation of user-supplied input. A remote attacker could exploit this vulnerability to induce the application to perform server-side DNS lookups or HTTP requests to arbitrary domain names. By submitting suitable payloads, an attacker can cause the application server to attack other systems that it can interact with. IBM X-Force ID: 230264.

A timing based side channel exists in the OpenSSL RSA Decryption implementation<br /> which could be sufficient to recover a plaintext across a network in a<br /> Bleichenbacher style attack. To achieve a successful decryption an attacker<br /> would have to be able to send a very large number of trial messages for<br /> decryption. The vulnerability affects all RSA padding modes: PKCS#1 v1.5,<br /> RSA-OEAP and RSASVE.<br /> <br /> For example, in a TLS connection, RSA is commonly used by a client to send an<br /> encrypted pre-master secret to the server. An attacker that had observed a<br /> genuine connection between a client and a server could use this flaw to send<br /> trial messages to the server and record the time taken to process them. After a<br /> sufficiently large number of messages the attacker could recover the pre-master<br /> secret used for the original connection and thus be able to decrypt the<br /> application data sent over that connection.