CVE-2017-11109
High · 7.8CVSS
7.8
EPSS
1.1%
Published
Jul 8, 2017
CISA due date
—
Cloudanix analysis
A flaw in a text editor could let someone crash the program or run unwanted code simply by getting a user to open a specially prepared file.
- Exploitation
- Requires User Interaction
- Attacker needs
- User Interaction
- Complexity
- Low
- Impact
- Denial Of Service
- Component
- Application
- Class
- Use After Free
- Remediation
- Upgrade
- Effort
- Medium
- Patch risk
- Low
What it actually does
Use-after-free condition triggered when processing a crafted source file, resulting in invalid memory access that can cause a crash or permit further memory corruption.
Why it matters to the business
Attackers could disrupt operations by crashing editor instances or, in limited cases, achieve code execution on systems that process untrusted scripts, increasing risk for environments relying on affected packages.
How an attack unfolds
An attacker creates a malicious source file that exploits the use-after-free when opened with the vulnerable editor; the file is delivered via email, download, or shared storage and opened by a user or automated process.
How to fix it
Upgrade hubble-ui, hubble-ui-backend (Chainguard and Wolfi variants) to version 0.13.0-r1 or later; avoid opening untrusted source files until patches are applied.
How to confirm the fix worked
Verify package versions match or exceed the listed fixed releases; attempt reproduction with known proof-of-concept files in a controlled environment to confirm absence of the crash condition.
Typical attack path
- Craft a source file containing structures that trigger the use-after-free on parse
- Deliver the file to the target environment
- Induce the victim to open the file using the affected editor
- Trigger invalid free and subsequent memory operations for denial of service or code execution
How to detect it
Review process execution logs for editor invocations on unexpected files; inspect system or application logs for segmentation faults or invalid free errors around the time of file access.
What your security team should do
- Apply the 0.13.0-r1 updates to all listed packages immediately
- Restrict opening of untrusted source files in affected editor instances
- Monitor for new exploit maturity indicators given the 2017 disclosure date
The record
Vim 8.0 allows attackers to cause a denial of service (invalid free) or possibly have unspecified other impact via a crafted source (aka -S) file. NOTE: there might be a limited number of scenarios in which this has security relevance.
Affected packages
| Ecosystem | Package | Introduced | Fixed |
|---|---|---|---|
| Debian:10 | vim | 0 | 2:8.0.0197-5 |
| Debian:11 | vim | 0 | 2:8.0.0197-5 |
| Debian:12 | vim | 0 | 2:8.0.0197-5 |
| Debian:13 | vim | 0 | 2:8.0.0197-5 |
| Debian:7 | vim | 0 | 2:7.3.547-7+deb7u4 |
| Debian:8 | vim | 0 | 2:7.4.488-7+deb8u4 |
| Ubuntu:14.04:LTS | vim | 0 | 2:7.4.052-1ubuntu3.1+esm1 |
| Ubuntu:16.04:LTS | vim | 0 | 2:7.4.1689-3ubuntu1.4 |
| Ubuntu:18.04:LTS | vim | 0 | 2:8.0.1144-1ubuntu1 |
| Ubuntu:18.04:LTS | vim | 0 | 2:8.0.1453-1ubuntu1.3 |
| Ubuntu:Pro:14.04:LTS | vim | 0 | 2:7.4.052-1ubuntu3.1+esm1 |
Related vulnerabilities
- CVE-2023-4781 Heap-based Buffer Overflow in GitHub repository vim/vim prior to 9.0.1873. Also affects vim
- CVE-2023-4752 Use After Free in GitHub repository vim/vim prior to 9.0.1858. Also affects vim
- CVE-2023-2610 Integer Overflow or Wraparound in GitHub repository vim/vim prior to 9.0.1532. Also affects vim
- CVE-2022-3324 Stack-based Buffer Overflow in GitHub repository vim/vim prior to 9.0.0598. Also affects vim
- CVE-2022-2598 Out-of-bounds Write to API in GitHub repository vim/vim prior to 9.0.0100. Also affects vim
- CVE-2022-1720 Buffer Over-read in function grab_file_name in GitHub repository vim/vim prior to… Also affects vim
- CVE-2022-2000 Out-of-bounds Write in GitHub repository vim/vim prior to 8.2. Also affects vim
- CVE-2022-1968 Use After Free in GitHub repository vim/vim prior to 8.2. Also affects vim