# CVE-2018-6328: Auth bypass in n/a

> Unauthenticated attackers can bypass authentication and inject arbitrary commands via the /api/hosts parameter in Unitrends Backup.

- **Severity:** Critical 9.8 (`CVSS:3.0/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:** 14 Mar 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-743r-2x7m-hrm4

## What is CVE-2018-6328?

CVE-2018-6328 is a critical authentication bypass vulnerability in n/a, published on 14 Mar 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

It was discovered that the Unitrends Backup (UB) before 10.1.0 user interface was exposed to an authentication bypass, which then could allow an unauthenticated user to inject arbitrary commands into its /api/hosts parameters using backquotes.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2018-6328?

It affects 1 product.


Products: Kaseya Unitrends Backup.

## How do I fix CVE-2018-6328?

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

## Is CVE-2018-6328 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2018-6328 exists.

Public exploit code:

- Unitrends UEB http api remote code execution (metasploit)
- Unitrends UEB 10.0 - Root Remote Code Execution (exploitdb)
- Unitrends UEB - HTTP API Remote Code Execution (Metasploit) (exploitdb)
- Unitrends UEB - HTTP API Remote Code Execution (Metasploit) (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2021-40386](https://insights.sbomify.com/CVE-2021-40386/): Code injection in n/a (critical 9.8)
- [CVE-2021-43033](https://insights.sbomify.com/CVE-2021-43033/): Command injection in n/a (critical 9.8)
- [CVE-2021-43035](https://insights.sbomify.com/CVE-2021-43035/): SQL injection in n/a (critical 9.8)
- [CVE-2021-43036](https://insights.sbomify.com/CVE-2021-43036/): Hardcoded credentials in n/a (critical 9.8)
- [CVE-2021-43042](https://insights.sbomify.com/CVE-2021-43042/): Memory corruption in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-6328 and fix it if it is affected.

What it is: CVE-2018-6328 is a critical authentication bypass vulnerability in n/a, published on 14 Mar 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2018-6328 exists.

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

## Sources

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

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