Skip to content
Fencer Intel
medium 4.3

CVE-2014-2379 json

Sensys Networks Traffic Sensor Missing Encryption of Sensitive Data

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

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

Summary

Sensys Networks VSN240-F and VSN240-T sensors VDS before 2.10.1 and TrafficDOT before 2.10.3 do not use encryption, which allows remote attackers to interfere with traffic control by replaying transmissions on a wireless network.

Patch / fix

  • 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 cvss 4.3

Sensys Networks Traffic Sensor Vulnerabilities (Update A)

  • Sensys Networks TrafficDOT <2.10.3 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.28% chance of exploitation in the next 30 days, higher than 21% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

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

Affected products

  • Sensys Networks VSN240-F
  • Sensys Networks VSN240-T

Classification

Weakness
  • CWE-311 Missing Encryption of Sensitive Data
  • CWE-310 Cryptographic Issues

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.