CVE-2023-31100

Improper Access Control in SMI handler vulnerability in Phoenix SecureCore™ Technology™ 4 allows SPI flash modification. This issue affects SecureCore™ Technology™ 4: * from 4.3.0.0 before 4.3.0.203 * from 4.3.1.0 before 4.3.1.163 * from 4.4.0.0 before 4.4.0.217 * from 4.5.0.0 before 4.5.0.138

Published: 2023-11-15 Last update: 2025-09-25 Assigner: 22d9ba52-f336-4b0d-bf1f-0efbdcc3c1de Source: 22d9ba52-f336-4b0d-bf1f-0efbdcc3c1de
NVD Status：Analyzed，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2023-31100 is rated Low Risk (36.8/100): CVSS High severity, with low exploitation likelihood (EPSS 0.19%). Monitor for updates and reassess as exploit intelligence or EPSS changes.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2023-31100

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 0.04% 0.19% +0.14%
2 2026-04-09 0.06% 0.04% -0.01%
3 2025-12-16 — 0.06% —

Full EPSS history (8 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2023-31100

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
8.4 3.1 HIGH
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:N/I:H/A:H Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:C)
Breaking this can reach past the original component and bite other resources—bigger blast radius.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 2.0 5.8 22d9ba52-f336-4b0d-bf1f-0efbdcc3c1de
7.1 3.1 HIGH
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 1.8 5.2 [email protected]

Weakness enumeration for CVE-2023-31100

Affected software / configurations for CVE-2023-31100

Vendor Product Version Raw CPE
phoenixtech securecore_technology >= 4.3.0.0, < 4.3.0.203 cpe:2.3:o:phoenixtech:securecore_technology:*:*:*:*:*:*:*:*
phoenixtech securecore_technology >= 4.3.1.0, < 4.3.1.163 cpe:2.3:o:phoenixtech:securecore_technology:*:*:*:*:*:*:*:*
phoenixtech securecore_technology >= 4.4.0.0, < 4.4.0.217 cpe:2.3:o:phoenixtech:securecore_technology:*:*:*:*:*:*:*:*
phoenixtech securecore_technology >= 4.5.0.0, < 4.5.0.138 cpe:2.3:o:phoenixtech:securecore_technology:*:*:*:*:*:*:*:*

References for CVE-2023-31100

cvelogic Threat Intelligence