Security readout for executives and security teams
Plain-English summary
pycode-browser before 1.0 used predictable temporary files. In practical terms, a local user could potentially interfere with files the tool creates, causing limited information disclosure or file integrity impact. This is not described as remotely exploitable and is not listed as actively exploited in CISA KEV.
Executive priority
Treat this as a low-priority hygiene fix unless the software is present on shared systems with untrusted local users. Address through normal patch and legacy software removal cycles.
Technical view
The issue is classified as CWE-377: insecure temporary file handling. The CVSS 3.1 vector indicates local access, low complexity, low privileges, and required user interaction, with low confidentiality and integrity impact and no availability impact. The source bundle identifies pycode-browser before 1.0 as affected.
Likely exposure
Exposure is likely limited to systems where pycode-browser earlier than 1.0 is installed and used locally. Relevant assets may include developer workstations, admin systems, or build environments, rather than internet-facing services.
Exploitation context
The provided sources do not report active exploitation, and the CVE is not marked KEV. Exploitation would require local conditions and user interaction according to the CVSS vector, which materially limits business urgency.
Researcher notes
The public bundle is sparse: it names the weakness class, version boundary, Debian bug reference, and CVSS vector, but provides no detailed exploit narrative or standalone mitigation advisory. Avoid assuming affected downstream packages beyond the cited pycode-browser scope.
Mitigation direction
- Inventory systems for pycode-browser installations and versions.
- Upgrade pycode-browser to version 1.0 or later where applicable.
- If upgrade status is unclear, follow Debian or vendor package guidance.
- Restrict local shell access on systems where older versions remain installed.
- Remove pycode-browser where it is not operationally required.
Validation and detection
- Confirm whether pycode-browser is installed on workstations, build hosts, or servers.
- Verify installed versions are 1.0 or later.
- Check package manager records for Debian bug 790365 remediation status.
- Review local user access on systems running older pycode-browser versions.
- Document any unsupported or retained legacy installations.
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.
CWE-377: 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-2015-0849 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
- Low
- CVSS
- 3.9 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:N
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.
CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:N1.32.5Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
3.9LowVector: CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://bugs.debian.org/790365CVE 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.
Insecure Temporary File
Insecure Temporary File represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.