# CVE-2019-1163: Windows File Signature Security Feature Bypass Vulnerability

> Attackers can inject malicious code into signed CAB files without invalidating signatures, bypassing Windows security checks to execute code.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N/E:P/RL:O/RC:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 14 Aug 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-c3q8-2rfg-gpqv

## What is CVE-2019-1163?

CVE-2019-1163 is a medium-severity vulnerability in Microsoft Windows 10, published on 14 Aug 2019. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

A security feature bypass exists when Windows incorrectly validates CAB file signatures. An attacker who successfully exploited this vulnerability could inject code into a CAB file without invalidating the file's signature.
To exploit the vulnerability, an attacker could modify a signed CAB file and inject malicious code. The attacker could then convince a target user to execute the file.
The update addresses the vulnerability by correcting how Windows validates file signatures.

Weakness: CWE-354 (Improper Validation of Integrity Check Value)

## Which versions are affected by CVE-2019-1163?

It affects 3 products.


Products: Microsoft Windows 10, Microsoft Windows Server 2016, Microsoft Windows Server 2019.

## How do I fix CVE-2019-1163?

No fix has been published for CVE-2019-1163 yet. Limit exposure of the affected software until one is available.

## Is CVE-2019-1163 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2019-1163 exists.

## Other vulnerabilities in Microsoft Windows 10

- [CVE-2015-2426](https://insights.sbomify.com/CVE-2015-2426/): Microsoft Windows Adobe Type Manager Library Remote Code Execution (high 8.8, exploited in the wild)
- [CVE-2015-1769](https://insights.sbomify.com/CVE-2015-1769/): Microsoft Windows Mount Manager Privilege Escalation (medium 6.6, exploited in the wild)
- [CVE-2020-1467](https://insights.sbomify.com/CVE-2020-1467/): Windows Hard Link Elevation of Privilege Vulnerability (critical 10.0)
- [CVE-2021-26424](https://insights.sbomify.com/CVE-2021-26424/): Windows TCP/IP Remote Code Execution Vulnerability (critical 9.9)
- [CVE-2021-28476](https://insights.sbomify.com/CVE-2021-28476/): Windows Hyper-V Remote Code Execution Vulnerability (critical 9.9)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-1163 and fix it if it is affected.

What it is: CVE-2019-1163 is a medium-severity vulnerability in Microsoft Windows 10, published on 14 Aug 2019. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2019-1163 exists.

Affected product: Microsoft Windows 10. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2019-1163/ (Markdown: https://insights.sbomify.com/CVE-2019-1163/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2019-1163
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2019-1163
- OSV: https://osv.dev/vulnerability/CVE-2019-1163

---
From sbomify Insights: https://insights.sbomify.com/CVE-2019-1163/
Summaries are generated and may contain mistakes; the official description above is the record.