CVE-2014-2379: Sensys Networks Traffic Sensor Missing Encryption of Sensitive Data
Noroxi assessment
Priority: Monitor (action score 21/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.28% (FIRST EPSS).
- According to the record, no fixed version is available yet.
Low priority for now. Update when a fix is released; follow the vendor's advisory.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Sep 5, 2014
- Updated
- Jun 16, 2026
- EPSS
- 0.2% · 21th percentile
- CWE
- CWE-311
Report tools
Action score
21
Low priority for now.
- CVSS
- 21 / 40 · 5.4 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CNA vs NVD score
- NVD
- 5.4
- CNA · icscert
- 4.3
- 1.1 point gap
AV:A/AC:H/Au:N/C:P/I:P/A:P
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- No fixed version yet
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| sensysnetworks | trafficdot | cpe:2.3:a:sensysnetworks:trafficdot |
| sensysnetworks | vsn240-f | cpe:2.3:h:sensysnetworks:vsn240-f |
| sensysnetworks | vsn240-t | cpe:2.3:h:sensysnetworks:vsn240-t |
| sensysnetworks | vds | cpe:2.3:a:sensysnetworks:vds |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (icscert). Independent of NVD's CPE analysis and usually ahead of it.
Sensys Networks VSN240-F
- before VDS 2.10.1affected
- before VDS 1.8.8affected
- before TrafficDOT 2.10.3affected
Sensys Networks VSN240-T
- before VDS 2.10.1affected
- before VDS 1.8.8affected
- before TrafficDOT 2.10.3affected
Affected versions · NVD (11)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- sensysnetworks trafficdotup to 2.10.2 inclusive
- sensysnetworks trafficdot2.10.0
- sensysnetworks trafficdot2.10.1
- sensysnetworks trafficdot2.8.3
- sensysnetworks vdsup to 2.10.0 inclusive
- sensysnetworks vds1.8.5
- sensysnetworks vds1.8.7
- sensysnetworks vds2.6.3
- sensysnetworks vds2.6.4
- sensysnetworks vsn240-fall versions
- sensysnetworks vsn240-tall versions
Same product
sensysnetworks: all recordsOther highest-scoring records for the same primary product.
- CVE-2014-2378Sensys Networks Traffic Sensor Download of Code Without Integrity Check30Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
- Cesar CerrudoIOActivefinder
Not on record for this CVE: EPSS history · patch commit or PR link · variant or chain candidate · public bounty program.
Technical details
Attack conditions
If successful
- Confidentiality
- P · data can be read
- Integrity
- P · data or configuration can be modified
- Availability
- P · the service can be disrupted
- Attack complexity
- M
- Confidentiality impact
- P
- Integrity impact
- P
- Availability impact
- P
Weakness class (CWE)
CWE-311 · Missing Encryption of Sensitive DataCVSS vector
AV:A/AC:M/Au:N/C:P/I:P/A:P
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Sniffing AttacksCAPEC-157Medium
- Sniffing Network TrafficCAPEC-158Medium
- Lifting Sensitive Data Embedded in CacheCAPEC-204Medium
- Accessing/Intercepting/Modifying HTTP CookiesCAPEC-31likelihood: High · High
- Retrieve Embedded Sensitive DataCAPEC-37likelihood: High · Very High
- Harvesting Information via API Event MonitoringCAPEC-383Low
- Application API Message Manipulation via Man-in-the-MiddleCAPEC-384Low
- Transaction or Event Tampering via Application API ManipulationCAPEC-385Medium
Change log (0)
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Show all references (3 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.