# CVE-2019-12812: Command injection in MyBuilder

> Attackers can execute arbitrary commands via crafted configuration files in MyBuilder viewer, leading to code execution.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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:** Not needed
- **Fix available:** No
- **Published:** 7 Oct 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-jq63-3p3v-m99f

## What is CVE-2019-12812?

CVE-2019-12812 is a critical command injection vulnerability in ACTIVESOFT MyBuilder, published on 7 Oct 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

MyBuilder viewer before 6.2.2019.814 allow an attacker to execute arbitrary command via specifically crafted configuration file. This can be leveraged for code execution.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

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

It affects 1 product.


Products: Activesoft Mybuilder.

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

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

## Is CVE-2019-12812 being exploited?

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

## Other vulnerabilities in ACTIVESOFT MyBuilder

- [CVE-2019-12811](https://insights.sbomify.com/CVE-2019-12811/): Command injection in MyBuilder (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-12812 is a critical command injection vulnerability in ACTIVESOFT MyBuilder, published on 7 Oct 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-12812 in the wild and no public exploit code.

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

## Sources

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

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