CVE-2016-15006 json
enigmaX Scrambling Table main.c getSeed prng seed
published 2023-01-02 3 y ago modified 2026-06-17 4 mo ago also EUVD-2016-2079
- cvss
- 3.7
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.8%
- EPSS 0.8% chance of exploitation in 30 days, percentile 57%
- public exploits
- 0
- none known
Summary
A vulnerability, which was classified as problematic, has been found in enigmaX up to 2.2. This issue affects the function getSeed of the file main.c of the component Scrambling Table Handler. The manipulation leads to predictable seed in pseudo-random number generator (prng). The attack may be initiated remotely. The complexity of an attack is rather high. The exploitation is known to be difficult. Upgrading to version 2.3 is able to address this issue. The identifier of the patch is 922bf90ca14a681629ba0b807a997a81d70225b5. It is recommended to upgrade the affected component. The identifier VDB-217181 was assigned to this vulnerability.
Patch / fix
- enigmax_project enigmax 2.3
Exploit prediction
0.82% chance of exploitation in the next 30 days, higher than 57% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 3.7 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N |
| CNA | 3.0 | 3.7 | CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N |
| CNA | 2.0 | 2.6 | AV:N/AC:H/Au:N/C:P/I:N/A:N |
| NVD | 3.1 | 5.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N |
Affected products
- n/a enigmaX
Classification
- Weakness
-
- CWE-337 Predictable Seed in Pseudo-Random Number Generator (PRNG)
References
-
github.com
/pfmonville/enigmaX/commit/922bf90ca14a681629ba0b807a997a81d70225b5
patch, third-party-advisory
-
github.com
/pfmonville/enigmaX/releases/tag/2.3
patch, release-notes, third-party-advisory
-
vuldb.com
/?id.217181
vdb-entry, technical-description, third-party-advisory
-
vuldb.com
/?ctiid.217181
signature, permissions-required, third-party-advisory
Sources
- CVE List CVE-2016-15006
- NVD CVE-2016-15006
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.