CVE-2015-10067 json
oznetmaster SSharpSmartThreadPool SmartThreadPool.cs race condition
published 2023-01-18 3 y ago modified 2026-06-17 4 mo ago also EUVD-2015-1080
- cvss
- 4.6
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.6%
- EPSS 0.6% chance of exploitation in 30 days, percentile 47%
- public exploits
- 0
- none known
Summary
A vulnerability was found in oznetmaster SSharpSmartThreadPool. It has been classified as problematic. This affects an unknown part of the file SSharpSmartThreadPool/SmartThreadPool.cs. The manipulation leads to race condition within a thread. The complexity of an attack is rather high. The exploitability is told to be difficult. The patch is named 0e58073c831093aad75e077962e9fb55cad0dc5f. It is recommended to apply a patch to fix this issue. The associated identifier of this vulnerability is VDB-218463.
Patch / fix
- ssharpsmartthreadpool_project ssharpsmartthreadpool 2015-03-13
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 19 mo ago
Exploit prediction
0.56% chance of exploitation in the next 30 days, higher than 47% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 4.6 | CVSS:3.1/AV:A/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:L |
| CNA | 3.0 | 4.6 | CVSS:3.0/AV:A/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:L |
| CNA | 2.0 | 4.0 | AV:A/AC:H/Au:S/C:P/I:P/A:P |
| NVD | 3.1 | 8.1 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H |
Affected products
- oznetmaster SSharpSmartThreadPool
Classification
References
-
github.com
/oznetmaster/SSharpSmartThreadPool/commit/0e58073c831093aad75e077962e9fb55cad0dc5f
patch, third-party-advisory
-
vuldb.com
/?id.218463
vdb-entry, technical-description, permissions-required, third-party-advisory
-
vuldb.com
/?ctiid.218463
signature, permissions-required, third-party-advisory
Sources
- CVE List CVE-2015-10067
- NVD CVE-2015-10067
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.