# CVE-2019-14422: Code injection in n/a

> Attackers can execute arbitrary code via malicious Excel macros by exploiting the Tsvncmd URI handler's lack of macro security warnings during diff operations.

- **Severity:** High 8.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 15 Aug 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-4gp2-c6v2-cw7v

## What is CVE-2019-14422?

CVE-2019-14422 is a high-severity code injection vulnerability in n/a, published on 15 Aug 2019. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

An issue was discovered in in TortoiseSVN 1.12.1. The Tsvncmd: URI handler allows a customised diff operation on Excel workbooks, which could be used to open remote workbooks without protection from macro security settings to execute arbitrary code. A tsvncmd:command:diff?path:[file1]?path2:[file2] URI will execute a customised diff on [file1] and [file2] based on the file extension. For xls files, it will execute the script diff-xls.js using wscript, which will open the two files for analysis without any macro security warning. An attacker can exploit this by putting a macro virus in a network drive, and force the victim to open the workbooks and execute the macro inside.

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

It affects 1 product.


Products: Tortoisesvn Tortoisesvn.

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

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

## Is CVE-2019-14422 being exploited?

There is no known exploitation of CVE-2019-14422 in the wild and no public exploit code.

Public exploit code:

- TortoiseSVN 1.12.1 - Remote Code Execution (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-14422 is a high-severity code injection vulnerability in n/a, published on 15 Aug 2019. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2019-14422 in the wild and no public exploit code.

Affected product: n/a. 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-14422/ (Markdown: https://insights.sbomify.com/CVE-2019-14422/index.md)
```

## Sources

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

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