CVE-2024-12533

Improper Check for Unusual or Exceptional Conditions vulnerability in Phoenix SecureCore Technology 4 allows Input Data Manipulation.This issue affects SecureCore Technology 4: from 4.0.1.0 before 4.0.1.1018, from 4.1.0.1 before 4.1.0.573, from 4.2.0.1 before 4.2.0.338, from 4.2.1.1 before 4.2.1.300, from 4.3.0.1 before 4.3.0.244, from 4.3.1.1 before 4.3.1.187, from 4.4.0.1 before 4.4.0.299, from 4.5.0.1 before 4.5.0.231, from 4.5.1.1 before 4.5.1.103, from 4.5.5.1 before 4.5.5.36, from 4.6.0.1 before 4.6.0.67.

Published: 2025-05-13 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-2024-12533 is rated Low Risk (21.4/100): CVSS Low severity, with low exploitation likelihood (EPSS 0.08%). 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-2024-12533

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-03-09 0.01% 0.08% +0.07%
2 2025-05-14 — 0.01% —

Full EPSS history (2 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2024-12533

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
3.3 3.1 LOW
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L 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:N)
Data isn’t meaningfully altered or forged.
Availability (A:L)
Might cause slowdowns, glitches, or partial disruption—not a full brick.
 1.8 1.4 22d9ba52-f336-4b0d-bf1f-0efbdcc3c1de

Weakness enumeration for CVE-2024-12533

Affected software / configurations for CVE-2024-12533

Vendor Product Version Raw CPE
phoenixtech securecore_technology >= 4.0.1.0, < 4.0.1.1018 cpe:2.3:o:phoenixtech:securecore_technology:*:*:*:*:*:*:*:*
phoenixtech securecore_technology >= 4.1.0.1, < 4.1.0.573 cpe:2.3:o:phoenixtech:securecore_technology:*:*:*:*:*:*:*:*
phoenixtech securecore_technology >= 4.2.0.1, < 4.2.0.338 cpe:2.3:o:phoenixtech:securecore_technology:*:*:*:*:*:*:*:*
phoenixtech securecore_technology >= 4.2.1.1, < 4.2.1.300 cpe:2.3:o:phoenixtech:securecore_technology:*:*:*:*:*:*:*:*
phoenixtech securecore_technology >= 4.3.0.1, < 4.3.0.244 cpe:2.3:o:phoenixtech:securecore_technology:*:*:*:*:*:*:*:*
phoenixtech securecore_technology >= 4.3.1.1, < 4.3.1.187 cpe:2.3:o:phoenixtech:securecore_technology:*:*:*:*:*:*:*:*
phoenixtech securecore_technology >= 4.4.0.1, < 4.4.0.299 cpe:2.3:o:phoenixtech:securecore_technology:*:*:*:*:*:*:*:*
phoenixtech securecore_technology >= 4.5.0.1, < 4.5.0.231 cpe:2.3:o:phoenixtech:securecore_technology:*:*:*:*:*:*:*:*
phoenixtech securecore_technology >= 4.5.1.1, <= 4.5.1.103 cpe:2.3:o:phoenixtech:securecore_technology:*:*:*:*:*:*:*:*
phoenixtech securecore_technology >= 4.5.5.1, < 4.5.5.36 cpe:2.3:o:phoenixtech:securecore_technology:*:*:*:*:*:*:*:*
phoenixtech securecore_technology >= 4.6.0.1, < 4.6.0.67 cpe:2.3:o:phoenixtech:securecore_technology:*:*:*:*:*:*:*:*

References for CVE-2024-12533

cvelogic Threat Intelligence