MegaRAC_SPx vulnerabilities
19 known vulnerabilities in MegaRAC_SPx from AMI. 19 are rated high or critical, and 1 has been exploited in real attacks. Each entry lists the affected versions and the release that fixes it, where the vendor has published one.
Latest first
- 9.8 Critical severity
AMI MegaRAC SPx Authentication Bypass by Spoofing Exploited
AMI’s SPx contains a vulnerability in the BMC where an Attacker may bypass authentication remotely through the Redfish Host Interface. A successful exploitation of this vulnerability may lead to a loss of confidentiality, integrity, and/or availability.
- 8.8 High severity
MegaRAC_SPx: Out-of-bounds Write
AMI’s SPx contains a vulnerability in the BMC where an Attacker may cause a stack-based buffer overflow via an adjacent network. A successful exploitation of this vulnerability may lead to a loss of confidentiality, integrity, and/or availability.
- 8.8 High severity
MegaRAC_SPx: Out-of-bounds Write
AMI’s SPx contains a vulnerability in the BMC where an Attacker may cause a heap memory corruption via an adjacent network. A successful exploitation of this vulnerability may lead to a loss of confidentiality, integrity, and/or availability.
- 8.8 High severity
MegaRAC_SPx: Out-of-bounds Write
AMI’s SPx contains a vulnerability in the BMC where an Attacker may cause a stack memory corruption via an adjacent network. A successful exploitation of this vulnerability may lead to a loss of confidentiality, integrity, and/or availability.
- 8.8 High severity
MegaRAC_SPx: Out-of-bounds Write
AMI’s SPx contains a vulnerability in the BMC where an Attacker may cause a heap memory corruption via an adjacent network. A successful exploitation of this vulnerability may lead to a loss of confidentiality, integrity, and/or availability.
- 8.8 High severity
MegaRAC_SPx: Out-of-bounds Write
AMI’s SPx contains a vulnerability in the BMC where an Attacker may cause a heap memory corruption via an adjacent network. A successful exploitation of this vulnerability may lead to a loss of confidentiality, integrity, and/or availability.
- 8.8 High severity
MegaRAC_SPx: Out-of-bounds Write
AMI’s SPx contains a vulnerability in the BMC where an Attacker may cause a stack-based buffer overflow via an adjacent network. A successful exploitation of this vulnerability may lead to a loss of confidentiality, integrity, and/or availability.
- 7.8 High severity
MegaRAC_SPx: Improper Restriction of Operations within the Bounds of a Memory Buffer
AMI’s SPx contains a vulnerability in the BMC where an Attacker may cause an untrusted pointer to dereference via a local network. A successful exploitation of this vulnerability may lead to a loss of confidentiality, integrity, and/or availability.
- 7.8 High severity
MegaRAC_SPx: Improper Restriction of Operations within the Bounds of a Memory Buffer
AMI’s SPx contains a vulnerability in the BMC where an Attacker may cause an untrusted pointer to dereference by a local network. A successful exploitation of this vulnerability may lead to a loss of confidentiality, integrity, and/or availability.
- 8.8 High severity
MegaRAC_SPx: Use of Hard-coded Credentials
AMI SPx contains a vulnerability in the BMC where a valid user may cause a use of hard-coded credentials. A successful exploit of this vulnerability may lead to a loss of confidentiality, integrity, and availability.
- 8.1 High severity
MegaRAC_SPx: Missing Cryptographic Step
AMI SPx contains a vulnerability in the BMC where a user may cause a missing cryptographic step by generating a hash-based message authentication code (HMAC). A successful exploit of this vulnerability may lead to the loss confidentiality, integrity, and authe
- 9.8 Critical severity
MegaRAC_SPx: Use of Hard-coded Credentials
AMI SPx contains a vulnerability in the BMC where an Attacker may cause a use of hard-coded cryptographic key by a hard-coded certificate. A successful exploit of this vulnerability may lead to a loss of confidentiality, integrity, and availability.
- 8.8 High severity
MegaRAC_SPx: Inadequate Encryption Strength
AMI SPx contains a vulnerability in the BMC where a user may cause an inadequate encryption strength by hash-based message authentication code (HMAC). A successful exploit of this vulnerability may lead to a loss of confidentiality, integrity, and availability
- 8.8 High severity
MegaRAC_SPx: Improper Neutralization of Special Elements used in an OS Command
AMI BMC contains a vulnerability in the SPX REST API, where an attacker with the required privileges can inject arbitrary shell commands, which may lead to code execution, denial of service, information disclosure, or data tampering.
- 9.1 Critical severity
MegaRAC_SPx: Improper Limitation of a Pathname to a Restricted Directory
AMI BMC contains a vulnerability in the IPMI handler, where an attacker can upload and download arbitrary files under certain circumstances, which may lead to denial of service, escalation of privileges, information disclosure, or data tampering.
- 8.8 High severity
MegaRAC_SPx: Buffer Copy without Checking Size of Input
AMI BMC contains a vulnerability in the IPMI handler, where an attacker with the required privileges can cause a buffer overflow, which may lead to code execution, denial of service, or escalation of privileges.
- 9.1 Critical severity
MegaRAC_SPx: Missing Authentication for Critical Functionality
AMI BMC contains a vulnerability in the IPMI handler, where an unauthenticated host is allowed to write to a host SPI flash, bypassing secure boot protections. An exploitation of this vulnerability may lead to a loss of integrity or denial of service.
- 8.8 High severity
MegaRAC_SPx: Improper Neutralization of Special Elements used in an OS Command
AMI BMC contains a vulnerability in the SPX REST API, where an attacker with the required privileges can inject arbitrary shell commands, which may lead to code execution, denial of service, information disclosure, or data tampering.
- 8.8 High severity
MegaRAC_SPx: Improper Restriction of Operations within the Bounds of a Memory Buffer
AMI BMC contains a vulnerability in the SPX REST API, where an attacker with the required privileges can read and write to arbitrary locations within the memory context of the IPMI server process, which may lead to code execution, denial of service, informatio