CVE-2014-2360
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedOleumTech WIO DH2 Wireless Gateway and Sensor Wireless I/O Modules allow remote attackers to execute arbitrary code via packets that report a high battery voltage.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceThe OleumTech WIO DH2 Wireless Gateway and Sensor Wireless I/O Modules contain a vulnerability where specially crafted network packets reporting an abnormally high battery voltage trigger a memory corruption issue that can be exploited for remote code execution. This affects the wireless communication stack used in industrial sensor networks.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE dataall versionsall versionsCVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/Au:N/C:P/I:P/A:P
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify OleumTech device on the networkReview network inventory or physically inspect devices for OleumTech WIO DH2 Wireless Gateway or Sensor Wireless I/O Module labels, or check DHCP/asset lists for OleumTech device MAC addresses or hostnamesAffected if Device is an OleumTech WIO DH2 Wireless Gateway or Sensor Wireless I/O Module
-
Confirm wireless communication stack is activeCheck device network configuration or monitoring port 5050/tcp (wireless protocol port used by OleumTech devices) for active listeners using 'netstat -an' or similar network diagnostic toolsAffected if The device wireless communication interface is enabled and listening for sensor data
-
Inspect network traffic for anomalous battery voltage packetsCapture network traffic (PCAP) on the device segment and filter for application-layer data containing battery voltage field values significantly exceeding expected ranges (typically above 4.0V for standard sensor batteries); use display filters such as 'data contains' with hex patterns for battery voltage telemetryAffected if Network captures show battery voltage telemetry packets with values outside normal operational ranges (e.g., values above 4.5V or abnormally high)
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataApply vendor patches when available; in the interim, networksegment the affected devices behind firewalls with strict ACLs, and monitor for anomalous battery voltage telemetry packets in network traffic.
- Consultation6.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,760.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-2360 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2014-2360 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data