CVE-2011-3501 json
Integer overflow in Cogent DataHub 7.1.1.63 and earlier allows remote attackers to cause a denial of service (crash) via a negative or larg…
published 2011-09-16 15 y ago modified 2026-06-16 4 mo ago also EUVD-2011-3464
- cvss
- 5.0
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.9%
- EPSS 2.9% chance of exploitation in 30 days, percentile 87%
- public exploits
- 1
- Exploit-DB
Summary
Integer overflow in Cogent DataHub 7.1.1.63 and earlier allows remote attackers to cause a denial of service (crash) via a negative or large Content-Length value.
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
cisa ICSA-11-280-01 updated cvss 5.0
Cogent DataHub Vulnerabilities
-
Cogent Real-Time Systems Cascade DataHub 6_6.4.20. Cogent Real-Time Systems Cogent DataHub 7_until_7.1.2 Cogent Real-Time Systems OPC DataHub <6.4.20affected: 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
Timeline
- First public exploit (EDB-17839)
- Published
Exploit prediction
2.94% chance of exploitation in the next 30 days, higher than 87% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-17839 Cogent DataHub 7.1.1.63 - Integer Overflow dos, 2011-09-14
- aluigi.altervista.org http://aluigi.altervista.org/adv/cogent_3-adv.txt referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:N/I:N/A:P |
Classification
- Weakness
-
- CWE-189 Numeric Errors
References
-
aluigi.altervista.org
/adv/cogent_3-adv.txt
exploit
-
us-cert.gov
/control_systems/pdf/ICS-ALERT-11-256-03.pdf
us-government-resource
Sources
- CVE List CVE-2011-3501
- NVD CVE-2011-3501
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.