LiveActive security incident?Get immediate response
CVE Record

CVE-2016-15006: enigmaX Scrambling Table main.c getSeed prng seed

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.

LowCVSS 3.7Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysislow

Security readout for executives and security teams

Plain-English summary

enigmaX versions 2.0 through 2.2 use a predictable pseudo-random seed in the Scrambling Table Handler. This can weaken confidentiality for affected scrambling behavior, but the published rating is low, with high attack complexity and no integrity or availability impact. Version 2.3 addresses it.

Executive priority

Treat this as a low-priority remediation unless enigmaX protects sensitive information or is internet-exposed. It should still be upgraded during normal patch cycles because the fix is available and the weakness affects randomness quality.

Technical view

CVE-2016-15006 is CWE-337 in main.c getSeed for enigmaX up to 2.2. Manipulation can produce a predictable PRNG seed. CVSS 3.1 is 3.7: AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N. The referenced fix is commit 922bf90c and release 2.3.

Likely exposure

Exposure appears limited to deployments using enigmaX 2.0, 2.1, or 2.2, especially if the affected component can be reached remotely. The bundle provides no CPEs or broader platform mapping.

Exploitation context

The source bundle says the attack may be remote, but complexity is high and exploitation is difficult. It does not cite public exploitation or KEV listing, so active exploitation should not be assumed.

Researcher notes

The evidence identifies the vulnerable function and weakness class but does not provide detailed exploit mechanics, CPEs, or real-world deployment data. Avoid assuming impact beyond low confidentiality loss unless local application context shows the scrambling output protects sensitive data.

Mitigation direction

  • Upgrade enigmaX 2.0, 2.1, or 2.2 to version 2.3.
  • Confirm the deployed code includes commit 922bf90ca14a681629ba0b807a997a81d70225b5.
  • Check vendor project guidance for any additional operational recommendations.
  • Prioritize exposed internet-facing uses before internal-only or retired deployments.

Validation and detection

  • Inventory systems or packages using enigmaX and record deployed versions.
  • Confirm whether the Scrambling Table Handler is reachable from untrusted networks.
  • Verify version 2.3 or the referenced patch commit is deployed.
  • Review application use of affected scrambling behavior for confidentiality sensitivity.
Prepared
Confidence
high
Sources
6

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-337: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2016-15006 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Low
CVSS
3.7 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
5Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
3.7CVSS 3.1LowCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N2.21.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

3.7Low
CVSS 3.1 vector shape for CVE-2016-15006Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/aenigmaX2.0, 2.1, 2.2Listed
Weakness

CWE details

CWE-337

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-337 · source CWE mapping

Predictable Seed in Pseudo-Random Number Generator (PRNG)

Predictable Seed in Pseudo-Random Number Generator (PRNG) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

Open CWE intelligenceSame-CWE CVEs