CVE-2014-2361
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, when BreeZ is used, do not require authentication for reading the site security key, which allows physically proximate attackers to spoof communication by obtaining this key after use of direct hardware access or manual-setup mode.
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 · high confidenceThe OleumTech WIO DH2 Wireless Gateway and Sensor Wireless I/O Modules with BreeZ software do not require authentication for reading the site security key. Physically proximate attackers with direct hardware access or in manual-setup mode can obtain this key and use it to spoof communications between devices.
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
- Local
- Complexity
- Low
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:L/AC:L/Au:N/C:C/I:C/A:C
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 device modelLocate and inspect the physical hardware device or check device inventory/documentation. Confirm the model is either OleumTech WIO DH2 Wireless Gateway or OleumTech Sensor Wireless I/O Module.Affected if The device is an OleumTech WIO DH2 Wireless Gateway or Sensor Wireless I/O Module - all versions of these products are affected.
-
Verify BreeZ software is in useAccess the device management interface or check device configuration documentation to confirm the BreeZ software platform is running on the identified OleumTech device.Affected if BreeZ software is confirmed to be running on the OleumTech device.
-
Check device operational modeAccess the device configuration settings through the management interface or CLI. Determine if the device is currently operating in manual-setup mode, which allows unauthenticated access to the site security key.Affected if The device is in manual-setup mode, which exposes the site security key without authentication.
-
Assess physical access exposureEvaluate the physical security controls around the OleumTech device. Determine if unauthorized individuals could gain direct hardware access to read the site security key from the device.Affected if Physical access to the device is not restricted or controlled, creating an attack surface for key extraction.
If you have an OleumTech WIO DH2 Wireless Gateway or Sensor Wireless I/O Module running BreeZ software, especially in manual-setup mode or with unrestricted physical access, you are affected by this vulnerability.
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 dataRestrict physical access to devices, implement authentication requirements for accessing the site security key in BreeZ, or upgrade to a firmware version that enforces authentication for key retrieval.
- Consultation6.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-2361 — 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-2361 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