Vulnerabilities

Tenda G3 v3.0 v15.11.0.20 was discovered to contain a command injection vulnerability via the formSetDebugCfg function.

Insecure creation of temporary files allows local users on systems with non-default configurations to cause denial of service or set the encryption key for a filesystem

Directory Traversal vulnerability in DotNetZip v.1.16.0 and before allows a remote attacker to execute arbitrary code via the src/Zip.Shared/ZipEntry.Extract.cs component NOTE: This vulnerability only affects products that are no longer supported by the maintainer.

A vulnerability was found in Moodle. Additional checks are required to ensure users with permission to view badge recipients can only access lists of those they are intended to have access to.

A Improper Neutralization of Input During Web Page Generation (&amp;#39;Cross-site Scripting&amp;#39;) vulnerability in openSUSE Tumbleweed MirrorCache allows the execution of arbitrary JS via reflected XSS in the  REGEX and P parameters.<br /> This issue affects MirrorCache before 1.083.

grub2 allowed attackers with access to the grub shell to access files on the encrypted disks.

An information disclosure vulnerability exists in the backup configuration process where the SAS token is not masked in the configuration response. This oversight results in sensitive information leakage within the yb_backup log files, exposing the SAS token in plaintext. The leakage occurs during the backup procedure, leading to potential unauthorized access to resources associated with the SAS token. This issue affects YugabyteDB Anywhere: from 2.20.0.0 before 2.20.7.0, from 2.23.0.0 before 2.23.1.0, from 2024.1.0.0 before 2024.1.3.0.

Using remote content in OpenPGP encrypted messages can lead to the disclosure of plaintext. This vulnerability affects Thunderbird

A vulnerability in the PROFINET stack implementation of the IndraDrive (all versions) of Bosch Rexroth allows an attacker to cause a denial of service, rendering the device unresponsive by sending arbitrary UDP messages.

A vulnerability has been identified in the way that Rancher stores vSphere&amp;#39;s CPI (Cloud Provider Interface) and CSI (Container Storage Interface) credentials used to deploy clusters through the vSphere cloud provider. This issue leads to the vSphere CPI and CSI passwords being stored in a plaintext object inside Rancher. This vulnerability is only applicable to users that deploy clusters in vSphere environments.

A authentication bypass using an alternate path or channel in Fortinet FortiClientWindows version 7.4.0, versions 7.2.4 through 7.2.0, versions 7.0.12 through 7.0.0, and 6.4.10 through 6.4.0 allows low privilege attacker to execute arbitrary code with high privilege via spoofed named pipe messages.

Issue summary: Calling the OpenSSL API function SSL_free_buffers may cause<br /> memory to be accessed that was previously freed in some situations<br /> <br /> Impact summary: A use after free can have a range of potential consequences such<br /> as the corruption of valid data, crashes or execution of arbitrary code.<br /> However, only applications that directly call the SSL_free_buffers function are<br /> affected by this issue. Applications that do not call this function are not<br /> vulnerable. Our investigations indicate that this function is rarely used by<br /> applications.<br /> <br /> The SSL_free_buffers function is used to free the internal OpenSSL buffer used<br /> when processing an incoming record from the network. The call is only expected<br /> to succeed if the buffer is not currently in use. However, two scenarios have<br /> been identified where the buffer is freed even when still in use.<br /> <br /> The first scenario occurs where a record header has been received from the<br /> network and processed by OpenSSL, but the full record body has not yet arrived.<br /> In this case calling SSL_free_buffers will succeed even though a record has only<br /> been partially processed and the buffer is still in use.<br /> <br /> The second scenario occurs where a full record containing application data has<br /> been received and processed by OpenSSL but the application has only read part of<br /> this data. Again a call to SSL_free_buffers will succeed even though the buffer<br /> is still in use.<br /> <br /> While these scenarios could occur accidentally during normal operation a<br /> malicious attacker could attempt to engineer a stituation where this occurs.<br /> We are not aware of this issue being actively exploited.<br /> <br /> The FIPS modules in 3.3, 3.2, 3.1 and 3.0 are not affected by this issue.