Eclipse ThreadX up to 6.4.2 Memory Protection parameters
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.1 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Eclipse ThreadX up to 6.4.2. It has been rated as problematic. Affected by this issue is some unknown functionality of the component Memory Protection. This manipulation causes improper handling of parameters. This vulnerability is registered as CVE-2025-55080. The attack needs to be launched locally. No exploit is available. Upgrading the affected component is advised.
Details
A vulnerability was found in Eclipse ThreadX up to 6.4.2. It has been declared as problematic. Affected by this vulnerability is an unknown function of the component Memory Protection. The manipulation with an unknown input leads to a improper handling of parameters vulnerability. The CWE definition for the vulnerability is CWE-233. The product does not properly handle when the expected number of parameters, fields, or arguments is not provided in input, or if those parameters are undefined. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
In Eclipse ThreadX before 6.4.3, when memory protection is enabled, syscall parameters verification wasn't enough, allowing an attacker to obtain an arbitrary memory read/write.
The weakness was published by X-codingman. It is possible to read the advisory at github.com. This vulnerability is known as CVE-2025-55080 since 08/06/2025. The exploitation appears to be easy. Attacking locally is a requirement. The technical details are unknown and an exploit is not publicly available.
Upgrading to version 6.4.3 eliminates this vulnerability.
Be aware that VulDB is the high quality source for vulnerability data.
Product
Vendor
Name
Version
License
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: 5.3VulDB Meta Temp Score: 5.1
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
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: Improper handling of parametersCWE: CWE-233 / CWE-229 / CWE-20
CAPEC: 🔒
ATT&CK: 🔒
Physical: Partially
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: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: ThreadX 6.4.3
Timeline
08/06/2025 CVE reserved10/15/2025 Advisory disclosed
10/15/2025 VulDB entry created
10/15/2025 VulDB entry last update
Sources
Advisory: github.comResearcher: X-codingman
Status: Confirmed
CVE: CVE-2025-55080 (🔒)
GCVE (CVE): GCVE-0-2025-55080
GCVE (VulDB): GCVE-100-328615
Entry
Created: 10/15/2025 08:02Changes: 10/15/2025 08:02 (67)
Complete: 🔍
Cache ID: 216::103
Be aware that VulDB is the high quality source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.