CVE-2022-30772 json
Manipulation of the input address in PnpSmm function 0x52 could be used by malware to overwrite SMRAM or OS kernel memory.
published 3y ago modified 4mo ago also EUVD-2022-52596
- cvss
- 8.2
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 9%
- public exploits
- 0
- none known
Summary
Manipulation of the input address in PnpSmm function 0x52 could be used by malware to overwrite SMRAM or OS kernel memory. Function 0x52 of the PnpSmm driver is passed the address and size of data to write into the SMBIOS table, but manipulation of the address could be used by malware to overwrite SMRAM or OS kernel memory. This issue was discovered by Insyde engineering during a security review. This issue is fixed in: Kernel 5.0: 05.09.41 Kernel 5.1: 05.17.43 Kernel 5.2: 05.27.30 Kernel 5.3: 05.36.30 Kernel 5.4: 05.44.30 Kernel 5.5: 05.52.30 https://www.insyde.com/security-pledge/SA-2022065
Patch / fix
- insyde kernel 5.0.05.09.41, 5.1.05.17.43, 5.2.05.27.30, 5.3.05.36.30, 5.4.05.44.30, 5.5.05.52.30
Is CVE-2022-30772 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
cisa ICSA-23-257-04 updated cvss 7.2
Siemens RUGGEDCOM APE1808 Products
-
Siemens RUGGEDCOM APE1808 ADM (6GK6015-0AL20-0GL0) <BIOS_V1.0.212N Siemens RUGGEDCOM APE1808 ADM CC (6GK6015-0AL20-0GL1) <BIOS_V1.0.212N Siemens RUGGEDCOM APE1808 CKP (6GK6015-0AL20-0GK0) <BIOS_V1.0.212N Siemens RUGGEDCOM APE1808 CKP CC (6GK6015-0AL20-0GK1) <BIOS_V1.0.212N Siemens RUGGEDCOM APE1808 CLOUDCONNECT (6GK6015-0AL20-0GM0) <BIOS_V1.0.212N Siemens RUGGEDCOM APE1808 CLOUDCONNECT CC (6GK6015-0AL20-0GM1) <BIOS_V1.0.212Naffected: fixed in V1.0.212N support.industry.siemens.com
+16 more productsfewer
Siemens RUGGEDCOM APE1808 ELAN (6GK6015-0AL20-0GP0) <BIOS_V1.0.212N Siemens RUGGEDCOM APE1808 ELAN CC (6GK6015-0AL20-0GP1) <BIOS_V1.0.212N Siemens RUGGEDCOM APE1808 SAM-L (6GK6015-0AL20-0GN0) <BIOS_V1.0.212N Siemens RUGGEDCOM APE1808 SAM-L CC (6GK6015-0AL20-0GN1) <BIOS_V1.0.212N Siemens RUGGEDCOM APE1808CLA-P (6GK6015-0AL20-1AA0) <BIOS_V1.0.212N Siemens RUGGEDCOM APE1808CLA-P CC (6GK6015-0AL20-1AA1) <BIOS_V1.0.212N Siemens RUGGEDCOM APE1808CLA-S1 (6GK6015-0AL20-1AB0) <BIOS_V1.0.212N Siemens RUGGEDCOM APE1808CLA-S1 CC (6GK6015-0AL20-1AB1) <BIOS_V1.0.212N Siemens RUGGEDCOM APE1808CLA-S3 (6GK6015-0AL20-1AD0) <BIOS_V1.0.212N Siemens RUGGEDCOM APE1808CLA-S3 CC (6GK6015-0AL20-1AD1) <BIOS_V1.0.212N Siemens RUGGEDCOM APE1808CLA-S5 (6GK6015-0AL20-1AF0) <BIOS_V1.0.212N Siemens RUGGEDCOM APE1808CLA-S5 CC (6GK6015-0AL20-1AF1) <BIOS_V1.0.212N Siemens RUGGEDCOM APE1808LNX (6GK6015-0AL20-0GH0) <BIOS_V1.0.212N Siemens RUGGEDCOM APE1808LNX CC (6GK6015-0AL20-0GH1) <BIOS_V1.0.212N Siemens RUGGEDCOM APE1808W10 (6GK6015-0AL20-0GJ0) <BIOS_V1.0.212N Siemens RUGGEDCOM APE1808W10 CC (6GK6015-0AL20-0GJ1) <BIOS_V1.0.212N
Facts from CISA's republication of the vendor's own advisory (CSAF); the linked advisory is the authoritative source. CISA notification · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- last yr.
Exploit prediction
0.20% chance of exploitation in the next 30 days, higher than 9% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 8.2 | CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H |
| NVD | 3.1 | 8.2 | CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H |
| CNA | 3.1 | 8.2 | CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H |
Classification
- Weakness
-
- CWE-787 Out-of-bounds Write
References
-
insyde.com
/security-pledge
vendor-advisory
-
insyde.com
/security-pledge/SA-2022065
vendor-advisory
Sources
- CVE List CVE-2022-30772
- NVD CVE-2022-30772
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.