Skip to content
Fencer Intel
high 7.1

CVE-2013-0683 json

The DataSim and DataPid demonstration clients in Cogent Real-Time Systems Cogent DataHub before 7.3.0, OPC DataHub before 6.4.22, Cascade D…

published 13y ago modified 4mo ago also EUVD-2013-0694

cvss
7.1
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.0%
EPSS 1.0% chance of exploitation in 30 days, percentile 62%
public exploits
0
none known

Summary

The DataSim and DataPid demonstration clients in Cogent Real-Time Systems Cogent DataHub before 7.3.0, OPC DataHub before 6.4.22, Cascade DataHub before 6.4.22 on Windows, and DataHub QuickTrend before 7.3.0 allow remote servers to cause a denial of service (incorrect pointer access and client crash) via malformed data in a formatted text command.

Is CVE-2013-0683 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

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

cisa ICSA-13-095-01 updated cvss 7.1

Cogent Real-Time Systems Vulnerabilities

  • Cogent Real-Time Systems Cascade DataHub for Windows <=6.4.21 Cogent Real-Time Systems Cogent DataHub <=7.2.2 Cogent Real-Time Systems DataHub QuickTrend <=7.2.2 Cogent Real-Time Systems DataSim and DataPid demonstration clients for Cogent DataHub V7.2.2 Cogent Real-Time Systems DataSim and DataPid demonstration clients for OPC DataHub and Cascade DataHub V6.4.21 Cogent Real-Time Systems OPC DataHub <=6.4.21
    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.99% chance of exploitation in the next 30 days, higher than 62% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 2.0 7.1 AV:N/AC:M/Au:N/C:N/I:N/A:C

Classification

Weakness

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.