Sr635
This hub aggregates every CVE we track for Sr635, a product in the hardware firmware space. Use it to gauge the current risk picture and drill into individual advisories.
21
CVEs tracked
0
Critical
8
High
0
In CISA KEV
Severity distribution
MEDIUM13HIGH8
Monthly trend
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
2024-072026-06
Latest CVEs
The 15 most recently published vulnerabilities affecting Sr635.
- CVE-2023-20523TOCTOU in the ASP may allow a physical attacker to write beyond the buffer bounds, potentially leading to a loss of integrity or denial of service. 5.7
- CVE-2023-20522Insufficient input validation in ASP may allow an attacker with a malicious BIOS to potentially cause a denial of service. 7.5
- CVE-2022-23814Failure to validate addresses provided by software to BIOS commands may result in a potential loss of integrity of guest memory in a confidential compute environment. 5.3
- CVE-2022-23813The software interfaces to ASP and SMU may not enforce the SNP memory security policy resulting in a potential loss of integrity of guest memory in a confidential compute environment. 5.3
- CVE-2021-46791Insufficient input validation during parsing of the System Management Mode (SMM) binary may allow a maliciously crafted SMM executable binary to corrupt Dynamic Root of Trust for Measurement (DRTM)...5.5
- CVE-2021-46768Insufficient input validation in SEV firmware may allow an attacker to perform out-of-bounds memory reads within the ASP boot loader, potentially leading to a denial of service. 5.5
- CVE-2021-46767Insufficient input validation in the ASP may allow an attacker with physical access, unauthorized write access to memory potentially leading to a loss of integrity or denial of service. 6.1
- CVE-2021-26409Insufficient bounds checking in SEV-ES may allow an attacker to corrupt Reverse Map table (RMP) memory, potentially resulting in a loss of SNP (Secure Nested Paging) memory integrity. 7.8
- CVE-2021-26407A randomly generated Initialization Vector (IV) may lead to a collision of IVs with the same key potentially resulting in information disclosure. 5.5
- CVE-2021-26404Improper input validation and bounds checking in SEV firmware may leak scratch buffer bytes leading to potential information disclosure. 5.5
- CVE-2021-26403Insufficient checks in SEV may lead to a malicious hypervisor disclosing the launch secret potentially resulting in compromise of VM confidentiality. 6.5
- CVE-2021-26402Insufficient bounds checking in ASP (AMD Secure Processor) firmware while handling BIOS mailbox commands, may allow an attacker to write partially-controlled data out-of-bounds to SMM or SEV-ES reg...7.1
- CVE-2021-26398Insufficient input validation in SYS_KEY_DERIVE system call in a compromised user application or ABL may allow an attacker to corrupt ASP (AMD Secure Processor) OS memory which may lead to potentia...7.8
- CVE-2021-26396Insufficient validation of address mapping to IO in ASP (AMD Secure Processor) may result in a loss of memory integrity in the SNP guest. 4.4
- CVE-2021-26355Insufficient fencing and checks in System Management Unit (SMU) may result in access to invalid message port registers that could result in a potential denial-of-service. 5.5
Product normalization is registry-driven with AI assist and human review. How it works