Show filters
813 Total Results
Displaying 21-30 of 813
Sort by:
Attacker Value
Unknown
CVE-2023-51323
Disclosure Date: February 20, 2025 (last updated February 23, 2025)
A lack of rate limiting in the 'Forgot Password' feature of PHPJabbers Shared Asset Booking System v1.0 allows attackers to send an excessive amount of email for a legitimate user, leading to a possible Denial of Service (DoS) via a large amount of generated e-mail messages.
0
Attacker Value
Unknown
CVE-2023-51321
Disclosure Date: February 20, 2025 (last updated February 23, 2025)
A lack of rate limiting in the 'Forgot Password' feature of PHPJabbers Night Club Booking Software v1.0 allows attackers to send an excessive amount of email for a legitimate user, leading to a possible Denial of Service (DoS) via a large amount of generated e-mail messages.
0
Attacker Value
Unknown
CVE-2024-41107
Disclosure Date: July 19, 2024 (last updated February 23, 2025)
The CloudStack SAML authentication (disabled by default) does not enforce signature check. In CloudStack environments where SAML authentication is enabled, an attacker that initiates CloudStack SAML single sign-on authentication can bypass SAML authentication by submitting a spoofed SAML response with no signature and known or guessed username and other user details of a SAML-enabled CloudStack user-account. In such environments, this can result in a complete compromise of the resources owned and/or accessible by a SAML enabled user-account.
Affected users are recommended to disable the SAML authentication plugin by setting the "saml2.enabled" global setting to "false", or upgrade to version 4.18.2.2, 4.19.1.0 or later, which addresses this issue.
0
Attacker Value
Unknown
CVE-2023-7169
Disclosure Date: February 08, 2024 (last updated February 26, 2025)
Authentication Bypass by Spoofing vulnerability in Snow Software Snow Inventory Agent on Windows allows Signature Spoof.This issue affects Snow Inventory Agent: through 6.14.5. Customers advised to upgrade to version 7.0
0
Attacker Value
Unknown
CVE-2023-47700
Disclosure Date: February 07, 2024 (last updated February 26, 2025)
IBM SAN Volume Controller, IBM Storwize, IBM FlashSystem and IBM Storage Virtualize 8.6 products could allow a remote attacker to spoof a trusted system that would not be correctly validated by the Storwize server. This could lead to a user connecting to a malicious host, believing that it was a trusted system and deceived into accepting spoofed data. IBM X-Force ID: 271016.
0
Attacker Value
Unknown
CVE-2023-43017
Disclosure Date: February 07, 2024 (last updated February 26, 2025)
IBM Security Verify Access 10.0.0.0 through 10.0.6.1 could allow a privileged user to install a configuration file that could allow remote access. IBM X-Force ID: 266155.
0
Attacker Value
Unknown
CVE-2023-32330
Disclosure Date: February 07, 2024 (last updated February 26, 2025)
IBM Security Verify Access 10.0.0.0 through 10.0.6.1 uses insecure calls that could allow an attacker on the network to take control of the server. IBM X-Force ID: 254977.
0
Attacker Value
Unknown
CVE-2024-22520
Disclosure Date: February 06, 2024 (last updated February 26, 2025)
An issue discovered in Dronetag Drone Scanner 1.5.2 allows attackers to impersonate other drones via transmission of crafted data packets.
0
Attacker Value
Unknown
CVE-2024-22519
Disclosure Date: February 06, 2024 (last updated February 26, 2025)
An issue discovered in OpenDroneID OSM 3.5.1 allows attackers to impersonate other drones via transmission of crafted data packets.
0
Attacker Value
Unknown
CVE-2024-25140
Disclosure Date: February 06, 2024 (last updated February 26, 2025)
A default installation of RustDesk 1.2.3 on Windows places a WDKTestCert certificate under Trusted Root Certification Authorities with Enhanced Key Usage of Code Signing (1.3.6.1.5.5.7.3.3), valid from 2023 until 2033. This is potentially unwanted, e.g., because there is no public documentation of security measures for the private key, and arbitrary software could be signed if the private key were to be compromised. NOTE: the vendor's position is "we do not have EV cert, so we use test cert as a workaround." Insertion into Trusted Root Certification Authorities was the originally intended behavior, and the UI ensured that the certificate installation step (checked by default) was visible to the user before proceeding with the product installation.
0