Security readout for executives and security teams
Plain-English summary
This issue affects OnionShare through 1.3.1 only when debug mode is enabled. It uses a predictable log file path in /tmp, which may let a local user overwrite files or read sensitive debug information. The available sources do not show remote exposure or active exploitation.
Executive priority
Treat this as a targeted hygiene issue, not an emergency. Prioritize if OnionShare is used on shared systems or with debug mode enabled. Otherwise, confirm configuration and fold remediation into normal patching.
Technical view
The vulnerable debug_mode function in web/web.py logs to /tmp/onionshare_server.log when --debug is enabled. The fixed pathname creates a local file-handling risk, potentially enabling local users to overwrite files or obtain sensitive information. CVSS, CWE, and precise package fix details are not provided in the source bundle.
Likely exposure
Exposure is most likely on systems running OnionShare through 1.3.1 with --debug enabled, especially shared or multi-user hosts. Systems not using debug mode appear outside the described trigger condition.
Exploitation context
The source bundle does not cite active exploitation, and KEV is false. The issue requires local user access and a debug-enabled OnionShare process. Evidence is incomplete on exploit maturity, affected distributions, and fixed versions.
Researcher notes
The useful pivot is configuration: --debug is the stated precondition. The public bundle lacks CVSS, CWE mapping, and fix confirmation. Avoid assuming remote impact or exploitation without additional vendor or distribution evidence.
Mitigation direction
- Disable --debug unless it is strictly needed for troubleshooting.
- Avoid running affected OnionShare versions on shared multi-user systems.
- Check vendor or Debian guidance for fixed package versions.
- Upgrade OnionShare if a vendor-supported fixed release is available.
- Restrict local shell access on systems that must run debug mode.
Validation and detection
- Inventory systems for OnionShare through 1.3.1.
- Check service files, scripts, and running processes for --debug usage.
- Review permissions and ownership around /tmp/onionshare_server.log.
- Confirm whether any local untrusted users can access affected hosts.
- Track vendor or Debian advisories for remediation details.
Public sources used
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.
CVE-2018-19960 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://bugs.debian.org/915859CVE 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.