# CVE-2019-6986: Command Injection in VIVO Vitro

> Remote attackers can cause denial of service in VIVO Vitro via SPARQL injection in the uri parameter, requiring immediate patching.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 28 Jan 2019
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-hgq9-q8g2-3jmg

## What is CVE-2019-6986?

CVE-2019-6986 is a high-severity denial of service vulnerability in n/a, published on 28 Jan 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

SPARQL Injection in VIVO Vitro v1.10.0 allows a remote attacker to execute arbitrary SPARQL via the uri parameter, leading to a regular expression denial of service (ReDoS), as demonstrated by crafted use of FILTER%20regex in a /individual?uri= request.

Weakness: CWE-77 (Improper Neutralization of Special Elements used in a Command), CWE-400 (Uncontrolled Resource Consumption)

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

2 open source packages ship an affected version, including org.vivoweb:vitro-project. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.vivoweb:vitro-project` | Maven | All versions | 1.11.0 |
| `org.vivoweb:vitro-project` | Maven | All versions | 1.11.0 |

Products: Duraspace Vitro.

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

Upgrade org.vivoweb:vitro-project to 1.11.0 or later.

## Is CVE-2019-6986 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2019-6986 is a high-severity denial of service vulnerability in n/a, published on 28 Jan 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-6986 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.vivoweb:vitro-project (Maven): affected all versions; fixed in 1.11.0
- org.vivoweb:vitro-project (Maven): affected all versions; fixed in 1.11.0

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-6986/ (Markdown: https://insights.sbomify.com/CVE-2019-6986/index.md)
```

## Sources

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

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