Vulnerabilities

Nix is a package manager for Linux and other Unix systems. Starting in version 1.11 and prior to versions 2.18.8 and 2.24.8, `` did not verify TLS certificates on HTTPS connections. This could lead to connection details such as full URLs or credentials leaking in case of a man-in-the-middle (MITM) attack. `` is also known as the builtin derivation builder `builtin:fetchurl`. It's not to be confused with the evaluation-time function `builtins.fetchurl`, which was not affected by this issue. A user may be affected by the risk of leaking credentials if they have a `netrc` file for authentication, or rely on derivations with `impureEnvVars` set to use credentials from the environment. In addition, the commonplace trust-on-first-use (TOFU) technique of updating dependencies by specifying an invalid hash and obtaining it from a remote store was also vulnerable to a MITM injecting arbitrary store objects. This also applied to the impure derivations experimental feature. Note that this may also happen when using Nixpkgs fetchers to obtain new hashes when not using the fake hash method, although that mechanism is not implemented in Nix itself but rather in Nixpkgs using a fixed-output derivation. The behavior was introduced in version 1.11 to make it consistent with the Nixpkgs `pkgs.fetchurl` and to make `` work in the derivation builder sandbox, which back then did not have access to the CA bundles by default. Nowadays, CA bundles are bind-mounted on Linux. This issue has been fixed in Nix 2.18.8 and 2.24.8. As a workaround, implement (authenticated) fetching with `pkgs.fetchurl` from Nixpkgs, using `impureEnvVars` and `curlOpts` as needed.

In the goTenna Pro App, the encryption keys are stored along with a <br /> static IV on the End User Device (EUD). This allows for complete <br /> decryption of keys stored on the EUD if physically compromised. This <br /> allows an attacker to decrypt all encrypted broadcast communications <br /> based on encryption keys stored on the EUD. This requires access to and <br /> control of the EUD, so it is recommended to use strong access control <br /> measures and layered encryption on the EUD for more secure operation.

The goTenna Pro App does not encrypt callsigns in messages. It is <br /> recommended to not use sensitive information in callsigns when using <br /> this and previous versions of the app and update your app to the current<br /> app version which uses AES-256 encryption for callsigns in encrypted <br /> operation.

The goTenna Pro App does not authenticate public keys which allows an <br /> unauthenticated attacker to manipulate messages. It is advised to update<br /> your app to the current release for enhanced encryption protocols.

The goTenna Pro App does not use SecureRandom when generating passwords <br /> for sharing cryptographic keys. The random function in use makes it <br /> easier for attackers to brute force this password if the broadcasted <br /> encryption key is captured over RF. This only applies to the optional <br /> broadcast of an encryption key, so it is advised to share the key with <br /> local QR code for higher security operations.

In the goTenna Pro App there is a vulnerability that makes it possible <br /> to inject any custom message with any GID and Callsign using a software <br /> defined radio in existing goTenna mesh networks. This vulnerability can <br /> be exploited if the device is being used in an unencrypted environment <br /> or if the cryptography has already been compromised. It is advised to <br /> share encryption keys via QR scanning for higher security operations and<br /> update your app to the current release for enhanced encryption <br /> protocols.

The goTenna Pro App encryption key name is always sent unencrypted when <br /> the key is shared over RF through a broadcast message. It is advised to <br /> share the encryption key via local QR for higher security operations.

The goTenna Pro App does not inject extra characters into broadcasted <br /> frames to obfuscate the length of messages. This makes it possible to <br /> tell the length of the payload regardless of the encryption used.

The goTenna Pro App uses AES CTR type encryption for short, encrypted <br /> messages without any additional integrity checking mechanisms. This <br /> leaves messages malleable to an attacker that can access the message. It<br /> is recommended to continue to use encryption in the app and update to <br /> the current release for more secure operations.

The goTenna Pro ATAK Plugin does not encrypt callsigns in messages. It <br /> is advised to not use sensitive information in callsigns when using this<br /> and previous versions of the plugin. Update to current plugin version <br /> which uses AES-256 encryption for callsigns in encrypted operation

Projectworld Online Voting System Version 1.0 is vulnerable to Cross Site Request Forgery (CSRF) via voter.php. This vulnerability allows an attacker to craft a malicious link that, when clicked by an authenticated user, automatically submits a vote for a specified party without the user&amp;#39;s consent or knowledge. The attack leverages the user&amp;#39;s active session to perform the unauthorized action, compromising the integrity of the voting process.

LayUI is a native minimalist modular Web UI component library. Versions prior to 2.9.17 have a DOM Clobbering vulnerability that can lead to Cross-site Scripting (XSS) on web pages where attacker-controlled HTML elements (e.g., `img` tags with unsanitized `name` attributes) are present. Version 2.9.17 fixes this issue.