Vulnerabilities

An issue was discovered in the rollback feature of Elastic Endpoint Security for Windows, which could allow unprivileged users to elevate their privileges to those of the LocalSystem account.

Argo CD is a declarative, GitOps continuous delivery tool for Kubernetes. All versions of Argo CD starting with v2.6.0-rc1 have an output sanitization bug which leaks repository access credentials in error messages. These error messages are visible to the user, and they are logged. The error message is visible when a user attempts to create or update an Application via the Argo CD API (and therefor the UI or CLI). The user must have `applications, create` or `applications, update` RBAC access to reach the code which may produce the error. The user is not guaranteed to be able to trigger the error message. They may attempt to spam the API with requests to trigger a rate limit error from the upstream repository. If the user has `repositories, update` access, they may edit an existing repository to introduce a URL typo or otherwise force an error message. But if they have that level of access, they are probably intended to have access to the credentials anyway. A patch for this vulnerability has been released in version 2.6.1. Users are advised to upgrade. There are no known workarounds for this vulnerability.

An Improper Access Control vulnerability allows an attacker to access the control panel of the B420 without requiring any sort of authorization or authentication due to the IP based authorization. If an authorized user has accessed a publicly available B420 product using valid credentials, an insider attacker can gain access to the same panel without requiring any sort of authorization. The B420 module was already obsolete at the time this vulnerability was found (The End of Life announcement was made in 2013).

formula is a math and string formula parser. In versions prior to 3.0.1 crafted user-provided strings to formula's parser might lead to polynomial execution time and a denial of service. Users should upgrade to 3.0.1+. There are no known workarounds for this vulnerability.

Discourse is an open source discussion platform. In affected versions a malicious user can cause a regular expression denial of service using a carefully crafted git URL. This issue is patched in the latest stable, beta and tests-passed versions of Discourse. Users are advised to upgrade. There are no known workarounds for this issue.

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 />

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.