Security readout for executives and security teams
Plain-English summary
CVE-2017-0913 lets a logged-in Ubiquiti UCRM user with System Customization edit rights read arbitrary files from the local file system. The default Docker deployment limits the host impact, but sensitive files inside the container could still be exposed.
Executive priority
Treat this as a targeted insider-or-account-compromise risk, not an unauthenticated emergency. Prioritize upgrade and privileged access review for any legacy UCRM deployment still in the affected version range.
Technical view
UCRM versions 2.3.0 through 2.7.7 contain an authenticated arbitrary local file read issue. Successful exploitation requires valid credentials and Edit access to System Customization. The CVE notes default local file system isolation inside a Docker container, which may constrain reachable files.
Likely exposure
Exposure is limited to organizations running Ubiquiti UCRM 2.3.0 to 2.7.7, especially where privileged customization access is broadly assigned or admin accounts are shared.
Exploitation context
The provided sources do not show CISA KEV listing or active exploitation. The required authenticated, privileged access lowers internet-scale risk, but compromise or misuse of an authorized account could expose configuration or application data.
Researcher notes
The source bundle lacks CVSS, CWE, and detailed patch notes. Analysis should remain bounded to authenticated arbitrary file read in UCRM 2.3.0-2.7.7 with Docker isolation noted as a default environmental constraint.
Mitigation direction
- Upgrade affected UCRM instances using Ubiquiti release guidance.
- Remove unnecessary System Customization edit permissions from user accounts.
- Review privileged account sharing and enforce unique credentials.
- Check vendor guidance for any version-specific remediation notes.
Validation and detection
- Inventory UCRM versions and identify any 2.3.0 through 2.7.7 deployments.
- Review users with Edit access to System Customization.
- Confirm UCRM runs inside the expected Docker isolation boundary.
- Inspect logs for unusual customization activity or file access attempts.
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.
Container behavior lookup
The affected technology mentions containers, so container-specific ATT&CK technique review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2017-0913 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
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
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 and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://hackerone.com/reports/301406CVE reference · x_refsource_MISC
- https://community.ubnt.com/t5/UCRM/New-UCRM-upgrades-available-2-8-2-and-2-9-0-beta3/td-p/2211814CVE reference · x_refsource_MISC
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.