# CVE-2019-17625: Rambox RCE Vulnerability

> Stored XSS in Rambox service name field allows attackers to execute arbitrary OS commands via crafted payloads.

- **Severity:** Critical 9.0 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 16 Oct 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-2gc6-2h2g-ph48

## What is CVE-2019-17625?

CVE-2019-17625 is a critical cross-site scripting vulnerability in n/a, published on 16 Oct 2019. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

There is a stored XSS in Rambox 0.6.9 that can lead to code execution. The XSS is in the name field while adding/editing a service. The problem occurs due to incorrect sanitization of the name field when being processed and stored. This allows a user to craft a payload for Node.js and Electron, such as an exec of OS commands within the onerror attribute of an IMG element.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation), CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

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

2 open source packages ship an affected version, including Rambox. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `Rambox` | npm | All versions to 0.6.9 | None |
| `Rambox` | npm | All versions to 0.6.9 | None |

Products: Rambox Rambox.

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

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

## Is CVE-2019-17625 being exploited?

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

Public exploit code:

- Working exploit code for CVE-2019-17625 (github_poc): https://github.com/Ekultek/CVE-2019-17625

## Fix prompt for AI coding agents

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

What it is: CVE-2019-17625 is a critical cross-site scripting vulnerability in n/a, published on 16 Oct 2019. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2019-17625 in the wild and no public exploit code.

Affected packages and fixed versions:
- Rambox (npm): affected all versions up to 0.6.9; no fix listed
- Rambox (npm): affected all versions up to 0.6.9; no fix listed

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

## Sources

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

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