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

> Attackers can execute arbitrary Groovy code on victim machines by tricking users into opening malicious project files in ReadyAPI or SoapUI.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/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:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 5 Feb 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-mvpr-q6w5-8529

## What is CVE-2019-12180?

CVE-2019-12180 is a high-severity code injection vulnerability in n/a, published on 5 Feb 2020. 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

An issue was discovered in SmartBear ReadyAPI through 2.8.2 and 3.0.0 and SoapUI through 5.5. When opening a project, the Groovy "Load Script" is automatically executed. This allows an attacker to execute arbitrary Groovy Language code (Java scripting language) on the victim machine by inducing it to open a malicious Project. The same issue is present in the "Save Script" function, which is executed automatically when saving a project.

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

It affects 2 products.


Products: Smartbear Readyapi, Smartbear Soapui.

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

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

## Is CVE-2019-12180 being exploited?

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

Public exploit code:

- Advisory & PoC (github_poc): https://github.com/0x-nope/CVE-2019-12180

## Other vulnerabilities in n/a

- [CVE-2020-12835](https://insights.sbomify.com/CVE-2020-12835/): Deserialization in n/a (critical 9.8)
- [CVE-2018-20580](https://insights.sbomify.com/CVE-2018-20580/): Code injection in n/a (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-12180 is a high-severity code injection vulnerability in n/a, published on 5 Feb 2020. 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: There is no known exploitation of CVE-2019-12180 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-12180/ (Markdown: https://insights.sbomify.com/CVE-2019-12180/index.md)
```

## Sources

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

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