# CVE-2020-6948: HashBrown CMS RCE

> Remote attackers can execute arbitrary commands on HashBrown CMS servers by exploiting improper handling of Git deployment parameters.

- **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:** Yes
- **Published:** 13 Jan 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-4gjv-5jjp-rcgh

## What is CVE-2020-6948?

CVE-2020-6948 is a critical command injection vulnerability in n/a, published on 13 Jan 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A remote code execution issue was discovered in HashBrown CMS through 1.3.3. Server/Entity/Deployer/GitDeployer.js has a Service.AppService.exec call that mishandles the URL, repository, username, and password.

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

## Which versions are affected by CVE-2020-6948?

2 open source packages ship an affected version, including hashbrown-cms. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `hashbrown-cms` | npm | All versions | 1.3.4 |
| `hashbrown-cms` | npm | All versions | 1.3.4 |

Products: Hashbrowncms Hashbrown Cms.

## How do I fix CVE-2020-6948?

Upgrade hashbrown-cms to 1.3.4 or later.

## Is CVE-2020-6948 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-6949](https://insights.sbomify.com/CVE-2020-6949/): Privilege escalation in n/a (high 8.8)
- [CVE-2020-5840](https://insights.sbomify.com/CVE-2020-5840/): HashBrown CMS Directory Traversal (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-6948 and fix it if it is affected.

What it is: CVE-2020-6948 is a critical command injection vulnerability in n/a, published on 13 Jan 2020. 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-2020-6948 in the wild and no public exploit code.

Affected packages and fixed versions:
- hashbrown-cms (npm): affected all versions; fixed in 1.3.4
- hashbrown-cms (npm): affected all versions; fixed in 1.3.4

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

## Sources

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

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