Security readout for executives and security teams
OleumTech WIO systems using BreeZ may expose the site security key without authentication. Someone close to the equipment, with direct hardware access or manual-setup mode, could obtain that key and impersonate wireless communications. This is high impact for industrial sites because spoofed I/O communications can affect confidentiality, integrity, and availability. Exposure is most likely in industrial or field deployments using OleumTech WIO DH2 gateways or Sensor Wireless I/O Modules with BreeZ. Risk is concentrated where unauthorized people can approach equipment, access setup workflows, or interact with hardware. Treat this as high priority where OleumTech WIO equipment supports production, safety, or remote operations. The main business risk is trusted wireless I/O traffic being spoofed after key exposure, especially at sites with weak physical security. Mitigation focus: Review CISA ICSA-14-202-01A and OleumTech support for vendor-approved guidance.; Inventory WIO DH2 gateways and Sensor Wireless I/O Modules using BreeZ.; Restrict physical access to gateways, sensors, enclosures, and setup interfaces..
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-320: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2014-2361 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.2 (2.0)
- Known Exploited
- No
- Published
Vector: AV:L/AC:L/Au:N/C:C/I:C/A:C
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
AV:L/AC:L/Au:N/C:C/I:C/A:C3.910Primary CVE scoreVulnerability scoring details
Base CVSS 2.0 score
7.2HighVector: AV:L/AC:L/Au:N/C:C/I:C/A:C
Source materials
- CVE List V5 sourceCVE List V5
- https://www.cisa.gov/news-events/ics-advisories/icsa-14-202-01aCVE reference
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Key Management Errors
Key Management Errors represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.