# CVE-2019-6738: Command injection in SafePay

> Remote attackers can execute arbitrary code via malicious TIScript processing in Bitdefender SafePay, requiring user interaction to visit a malicious page or file.

- **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:** 3 Jun 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-m93f-6f68-7r3h

## What is CVE-2019-6738?

CVE-2019-6738 is a high-severity command injection vulnerability in Bitdefender SafePay, published on 3 Jun 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

This vulnerability allows remote attackers to execute arbitrary code on vulnerable installations of Bitdefender SafePay 23.0.10.34. User interaction is required to exploit this vulnerability in that the target must visit a malicious page or open a malicious file. The specific flaw exists within the processing of TIScript. When processing the launch method the application does not properly validate a user-supplied string before using it to execute a system call. An attacker can leverage this vulnerability execute code in the context of the current process. Was ZDI-CAN-7250.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command), CWE-356 (Missing User Interaction for Potentially Unsafe Action)

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

It affects 1 product.


Products: Bitdefender Safepay.

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

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

## Is CVE-2019-6738 being exploited?

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

## Other vulnerabilities in Bitdefender SafePay

- [CVE-2019-6736](https://insights.sbomify.com/CVE-2019-6736/): Command injection in SafePay (high 8.8)
- [CVE-2019-6737](https://insights.sbomify.com/CVE-2019-6737/): Path traversal in SafePay (high 8.8)
- [CVE-2020-15734](https://insights.sbomify.com/CVE-2020-15734/): Same-origin policy vulnerability in Bitdefender Safepay (medium 5.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-6738 is a high-severity command injection vulnerability in Bitdefender SafePay, published on 3 Jun 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-6738 in the wild and no public exploit code.

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

## Sources

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

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