Vuldb Updates

A vulnerability described as problematic has been identified in Nautobot up to 1.6.21/2.2.3. This affects an unknown part of the file /admin/constance/config/. The manipulation of the argument BANNER_TOP/BANNER_BOTTOM/BANNER_LOGIN results in cross site scripting. This vulnerability is cataloged as CVE-2024-34707. The attack may be launched remotely. There is no exploit available. Upgrading the affected component is recommended.

A vulnerability has been found in Miniaudio 0.10.35 and classified as critical. The impacted element is the function ma_default_vfs_close__stdio in the library miniaudio.h. The manipulation leads to double free. This vulnerability is referenced as CVE-2021-34184. The attack needs to be initiated within the local network. No exploit is available.

A vulnerability was found in Miniaudio 0.10.35 and classified as problematic. This affects the function drwav_bytes_to_u32 in the library miniaudio.h. The manipulation results in out-of-bounds read. This vulnerability is identified as CVE-2021-34185. The attack can only be performed from the local network. There is not any exploit available.

A vulnerability labeled as problematic has been found in nocodb up to 0.95.x. Impacted is an unknown function. Executing manipulation can lead to improper input validation. The identification of this vulnerability is CVE-2023-5104. The attack needs to be done within the local network. There is no exploit available. The affected component should be upgraded.

A vulnerability, which was classified as critical, has been found in nocodb 0.91.7/0.92.0/0.96.0. The impacted element is an unknown function of the file SqliteClient.ts. This manipulation causes sql injection. This vulnerability is registered as CVE-2023-43794. Remote exploitation of the attack is possible. No exploit is available. It is advisable to upgrade the affected component.

A vulnerability was found in Discourse up to 3.2.0/3.3.0.beta1. It has been declared as problematic. Impacted is an unknown function of the component CSV Export. Such manipulation leads to resource consumption. This vulnerability is documented as CVE-2024-27100. The attack can be executed remotely. There is not any exploit available.

A vulnerability was found in Discourse up to 3.2.0. It has been rated as problematic. The affected element is an unknown function of the file /uploads. Performing manipulation results in resource consumption. This vulnerability is reported as CVE-2024-24827. The attack is possible to be carried out remotely. No exploit exists. Upgrading the affected component is advised.

A vulnerability categorized as problematic has been discovered in Discourse up to 3.2.0/3.3.0.beta1. The impacted element is an unknown function of the component Invite Route. Executing manipulation can lead to resource consumption. This vulnerability appears as CVE-2024-27085. The attack may be performed from a remote location. There is no available exploit.

A vulnerability labeled as problematic has been found in Discourse up to 3.2.0/3.3.0.beta1. This impacts an unknown function of the component Category Handler. The manipulation results in information disclosure. This vulnerability is known as CVE-2024-28242. It is possible to launch the attack remotely. No exploit is available.

A vulnerability was found in python-ecdsa up to 0.18.0. It has been rated as critical. The affected element is an unknown function. The manipulation leads to covert timing channel. This vulnerability is documented as CVE-2024-23342. The attack can be initiated remotely. There is not any exploit available.

A vulnerability marked as problematic has been reported in IOVisor BPF Compiler Collection on Linux. Affected by this issue is the function KBuildHelper::get_flags of the file src/cc/frontends/clang/kbuild_helper.cc of the component Kernel Header Handler. Performing manipulation results in insecure temporary file. This vulnerability was named CVE-2024-2314. The attack needs to be approached locally. There is no available exploit. To fix this issue, it is recommended to deploy a patch.

A vulnerability classified as critical was found in MediaTek MT6739, MT6761, MT6762, MT6765, MT6768, MT6769, MT6771, MT6779, MT6781, MT6785, MT6789, MT6833, MT6853, MT6855, MT6873, MT6875, MT6877, MT6879, MT6883, MT6885, MT6889, MT6891, MT6893, MT6895, MT6983, MT8321, MT8385, MT8765, MT8766, MT8768, MT8786, MT8788, MT8789, MT8791, MT8791T and MT8797. This issue affects some unknown processing of the component ril. The manipulation results in out-of-bounds write. This vulnerability is known as CVE-2023-20613. Attacking locally is a requirement. No exploit is available. A patch should be applied to remediate this issue.

A vulnerability, which was classified as critical, has been found in MediaTek MT6739, MT6761, MT6762, MT6765, MT6768, MT6769, MT6771, MT6779, MT6781, MT6785, MT6789, MT6833, MT6853, MT6853T, MT6855, MT6873, MT6875, MT6877, MT6879, MT6883, MT6885, MT6889, MT6891, MT6893, MT6895, MT6983, MT8321, MT8385, MT8765, MT8766, MT8768, MT8786, MT8788, MT8789, MT8791, MT8791T and MT8797. Impacted is an unknown function of the component ril. This manipulation causes out-of-bounds write. This vulnerability is handled as CVE-2023-20614. It is possible to launch the attack on the local host. There is not any exploit available. To fix this issue, it is recommended to deploy a patch.

A vulnerability, which was classified as critical, was found in MediaTek MT6739, MT6761, MT6762, MT6765, MT6768, MT6769, MT6771, MT6779, MT6781, MT6785, MT6789, MT6833, MT6853, MT6855, MT6873, MT6875, MT6877, MT6879, MT6883, MT6885, MT6889, MT6891, MT6893, MT6895, MT6983, MT8321, MT8385, MT8765, MT8766, MT8768, MT8786, MT8788, MT8789, MT8791, MT8791T and MT8797. The affected element is an unknown function of the component ril. Such manipulation leads to out-of-bounds write. This vulnerability is uniquely identified as CVE-2023-20615. Local access is required to approach this attack. No exploit exists. It is advisable to implement a patch to correct this issue.

A vulnerability has been found in MediaTek MT6580, MT6735, MT6737, MT6739, MT6753, MT6757, MT6757C, MT6757CD, MT6757CH, MT6761, MT6762, MT6763, MT6765, MT6768, MT6769, MT6771, MT6779, MT6781, MT6785, MT6833, MT6853, MT6853T, MT6873, MT6875, MT6877, MT6883, MT6885, MT6889, MT6891, MT6893, MT8168, MT8183, MT8321, MT8365, MT8385, MT8666, MT8675, MT8765, MT8766, MT8768, MT8786, MT8788, MT8791T and MT8797 and classified as problematic. The impacted element is an unknown function of the component ion. Performing manipulation results in out-of-bounds read. This vulnerability was named CVE-2023-20616. The attack needs to be approached locally. There is no available exploit. Applying a patch is the recommended action to fix this issue.

A vulnerability classified as problematic was found in Microsoft Visual Studio. This issue affects some unknown processing of the component Git. The manipulation results in injection. This vulnerability is reported as CVE-2025-48385. The attacker must have access to the local network to execute the attack. No exploit exists. It is best practice to apply a patch to resolve this issue.

A vulnerability, which was classified as problematic, has been found in Microsoft Visual Studio. Impacted is an unknown function of the component Git. This manipulation causes privilege escalation. This vulnerability appears as CVE-2025-48386. The attacker needs to be present on the local network. There is no available exploit. It is recommended to apply a patch to fix this issue.

A vulnerability has been found in j6t git-gui up to 2.50.0 and classified as critical. Affected by this vulnerability is an unknown functionality. This manipulation causes argument injection. This vulnerability is tracked as CVE-2025-46835. The attack is restricted to local execution. No exploit exists. The affected component should be upgraded.

A vulnerability classified as problematic was found in Microsoft Visual Studio. This impacts an unknown function of the component Git. Such manipulation leads to privilege escalation. This vulnerability is traded as CVE-2025-46835. Access to the local network is required for this attack to succeed. There is no exploit available. A patch should be applied to remediate this issue.

A vulnerability classified as problematic has been found in Microsoft Visual Studio. This vulnerability affects unknown code of the component Git. The manipulation leads to symlink following. This vulnerability is documented as CVE-2025-48384. The attack requires being on the local network. Additionally, an exploit exists. Applying a patch is the recommended action to fix this issue.