Skip to content
Fencer Intel
medium 6.0

CVE-2014-2354 json

Cogent DataHub Use of Password Hash With Insufficient Computational Effort

published 2014-05-30 12 y ago modified 2026-06-17 4 mo ago also EUVD-2014-2391

cvss
6.0
version 2.0, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.7%
EPSS 0.7% chance of exploitation in 30 days, percentile 52%
public exploits
0
none known

Summary

Cogent DataHub before 7.3.5 does not use a salt during password hashing, which makes it easier for context-dependent attackers to obtain cleartext passwords via a brute-force attack.

Patch / fix

  • Cogent DataHub 7.3.5

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

cisa ICSA-14-149-02 updated cvss 6.0

Cogent DataHub Vulnerabilities

  • Cogent Real-Time Systems DataHub <7.3.5
    affected: mitigation

From CISA ICS and IT advisories (CSAF, https://github.com/cisagov/CSAF), a U.S. Government work; changed: reduced to products, statuses and remediations. CISA notification · csaf

Exploit prediction

0.69% chance of exploitation in the next 30 days, higher than 52% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 2.0 6.0 AV:L/AC:H/Au:S/C:C/I:C/A:C
NVD 2.0 5.0 AV:N/AC:L/Au:N/C:P/I:N/A:N

Affected products

  • Cogent DataHub

Classification

Weakness
  • CWE-916 Use of Password Hash With Insufficient Computational Effort
  • CWE-255 Credentials Management Errors

References

Sources

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.