Sensys Networks Traffic Sensor Download of Code Without Integrity Check

published 2014-09-05 12 y ago modified 2026-06-17 4 mo ago also EUVD-2014-2415

cvss: 6.5; version 2.0, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.9%; EPSS 0.9% chance of exploitation in 30 days, percentile 59%
public exploits: 0; none known

Sensys Networks VSN240-F and VSN240-T sensors VDS before 2.10.1 and TrafficDOT before 2.10.3 do not verify the integrity of downloaded updates, which allows remote attackers to execute arbitrary code via a Trojan horse update.

Patch / fix

fixed in 2

Sensys Networks VSN240-F TrafficDOT 2.10.3, VDS 1.8.8, VDS 2.10.1
Sensys Networks VSN240-T TrafficDOT 2.10.3, VDS 1.8.8, VDS 2.10.1

Vendor advisories

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

cisa ICSA-14-247-01A updated 2025-06-06 cvss 6.5

Sensys Networks Traffic Sensor Vulnerabilities (Update A)

Sensys Networks TrafficDOT <2.10.2 Sensys Networks VDS <2.10.1, <1.8.8
affected: mitigation “Sensys Networks has produced updated product versions VDS 2.10.1 and TrafficDOT 2.10.3 to remediate vulnerabilities identified in their VSN240-F and VSN240-T traffic sensors”

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.90% chance of exploitation in the next 30 days, higher than 59% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by	version	score	vector
CNA	2.0	6.5	AV:A/AC:H/Au:N/C:C/I:C/A:P
NVD	2.0	7.6	AV:A/AC:M/Au:N/C:C/I:C/A:P

Affected products

Sensys Networks VSN240-F
Sensys Networks VSN240-T

Classification

Weakness

CWE-494 Download of Code Without Integrity Check
CWE-94 Improper Control of Generation of Code

References

Sources

CVE List CVE-2014-2378
NVD CVE-2014-2378

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.

Summary