CVE-2017-14853: The Orpak SiteOmat OrCU component is vulnerable to code injection, for all versions prior to 2017-09-25, du...
The Orpak SiteOmat OrCU component is vulnerable to code injection, for all versions prior to 2017-09-25, due to a search query that uses a direct shell command. By tampering with the request, an attacker is able to run shell commands and receive valid output from the device.
Security readout for executives and security teams
CVE-2017-14853 affects Orpak SiteOmat OrCU versions before 2017-09-25. A malformed request can make the device run shell commands and return output. For executives, the concern is unauthorized control of an operational component, with high integrity impact and some confidentiality and availability risk. Exposure is most likely where Orpak SiteOmat OrCU components running versions before 2017-09-25 are reachable over a network. The supplied CVE data does not identify CPEs or a full product matrix, so asset confirmation is required. Treat this as a high-priority operational technology exposure. Prioritize sites where OrCU components are network-accessible, especially if version status is unknown or remediation cannot be confirmed. Mitigation focus: Inventory Orpak SiteOmat OrCU deployments and identify versions or build dates.; Move affected OrCU components to vendor-confirmed fixed versions dated 2017-09-25 or later.; If patch status is unclear, request current remediation guidance from Orpak..
Prepared
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
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 · medium confidence lookup
CWE-94: Code execution behavior lookup
Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. 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.
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.
1CVSS vectors
3Timeline events
2ADP providers
3Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: yesTechnical Impact: total
CVSS vector scores
1 official score
We 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.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-94 · source CWE mapping
Improper Control of Generation of Code ('Code Injection')
Improper Control of Generation of Code ('Code Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.