| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 2.0 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in Silabs Simplicity SDK and classified as problematic. This affects an unknown function. Performing a manipulation results in entropy. This vulnerability is known as CVE-2025-14972. The attack may be carried out on the physical device. No exploit is available.
Details
A vulnerability classified as problematic has been found in Silabs Simplicity SDK (the affected version unknown). This affects an unknown part. The manipulation with an unknown input leads to a entropy vulnerability. CWE is classifying the issue as CWE-331. The product uses an algorithm or scheme that produces insufficient entropy, leaving patterns or clusters of values that are more likely to occur than others. This is going to have an impact on confidentiality. The summary by CVE is:
* Countermeasures for DPA within SYMCRYPTO engine on SixG301xxx devices are not sufficiently random and will eventually repeat. * KSU keys using SYMCRYPTO will be impacted by this vulnerability.
The advisory is shared at community.silabs.com. This vulnerability is uniquely identified as CVE-2025-14972 since 12/19/2025. The exploitability is told to be difficult. An attack has to be approached locally. No form of authentication is needed for exploitation. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1600.001 for this issue.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Vendor
Name
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3
VulDB Meta Base Score: 2.0VulDB Meta Temp Score: 2.0
VulDB Base Score: 2.0
VulDB Temp Score: 2.0
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: EntropyCWE: CWE-331 / CWE-330 / CWE-310
CAPEC: 🔒
ATT&CK: 🔒
Physical: Yes
Local: Yes
Remote: No
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
12/19/2025 CVE reserved05/15/2026 Advisory disclosed
05/15/2026 VulDB entry created
05/15/2026 VulDB entry last update
Sources
Advisory: community.silabs.comStatus: Confirmed
CVE: CVE-2025-14972 (🔒)
GCVE (CVE): GCVE-0-2025-14972
GCVE (VulDB): GCVE-100-364185
Entry
Created: 05/15/2026 18:10Changes: 05/15/2026 18:10 (63)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.