Show filters
831 Total Results
Displaying 11-20 of 831
Sort by:
Attacker Value
Unknown

CVE-2024-45569

Disclosure Date: February 03, 2025 (last updated February 06, 2025)
Memory corruption while parsing the ML IE due to invalid frame content.
Attacker Value
Unknown

CVE-2024-38420

Disclosure Date: February 03, 2025 (last updated February 06, 2025)
Memory corruption while configuring a Hypervisor based input virtual device.
Attacker Value
Unknown

CVE-2024-38418

Disclosure Date: February 03, 2025 (last updated February 06, 2025)
Memory corruption while parsing the memory map info in IOCTL calls.
Attacker Value
Unknown

CVE-2024-38417

Disclosure Date: February 03, 2025 (last updated February 06, 2025)
Information disclosure while processing IO control commands.
Attacker Value
Unknown

CVE-2024-38416

Disclosure Date: February 03, 2025 (last updated February 06, 2025)
Information disclosure during audio playback.
Attacker Value
Unknown

CVE-2024-38414

Disclosure Date: February 03, 2025 (last updated February 06, 2025)
Information disclosure while processing information on firmware image during core initialization.
Attacker Value
Unknown

CVE-2025-23006

Disclosure Date: January 23, 2025 (last updated January 28, 2025)
Pre-authentication deserialization of untrusted data vulnerability has been identified in the SMA1000 Appliance Management Console (AMC) and Central Management Console (CMC), which in specific conditions could potentially enable a remote unauthenticated attacker to execute arbitrary OS commands.
Attacker Value
Unknown

CVE-2024-45559

Disclosure Date: January 06, 2025 (last updated January 14, 2025)
Transient DOS can occur when GVM sends a specific message type to the Vdev-FastRPC backend.
Attacker Value
Unknown

CVE-2024-45558

Disclosure Date: January 06, 2025 (last updated January 14, 2025)
Transient DOS can occur when the driver parses the per STA profile IE and tries to access the EXTN element ID without checking the IE length.
Attacker Value
Unknown

CVE-2024-45555

Disclosure Date: January 06, 2025 (last updated January 14, 2025)
Memory corruption can occur if an already verified IFS2 image is overwritten, bypassing boot verification. This allows unauthorized programs to be injected into security-sensitive images, enabling the booting of a tampered IFS2 system image.