Vulnerabilities in pkg:npm/Rambox

PACKAGE
Advisory Identifier: GHSA-2gc6-2h2g-ph48
Share
Advisory Summary

CVE-2019-17625 is a CRITICAL (CVSS 9.0) remote code execution vulnerability (CWE-78: Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')) affecting Rambox libraries in the npm ecosystem. The issue involves rambox rce vulnerability. Remediation is available in the latest vendor maintenance releases.

1 Known Advisory Record(s)
Package Vulnerability Intelligence

pkg:npm/Rambox

1 Known Advisory Record(s)

Vulnerability advisories affecting package pkg:npm/Rambox. Select an advisory below to view technical details or fixes.

Advisory ID CVE / NVD Severity Summary
GHSA-2gc6-2h2g-ph48 CVE-2019-17625 CRITICAL Rambox RCE Vulnerability

CVE-2019-17625 at a Glance

CVE Identifier CVE-2019-17625
GHSA Identifier GHSA-2gc6-2h2g-ph48
Severity CRITICAL
CVSS v3.1 Base Score 9.0
CWE Classification CWE-78: Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')
Affected Product Rambox
Package Ecosystem npm
Published Date
Last Updated

Security Impact

CVSS: 9.0

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:H).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required Low (PR:L)
User Interaction Required (UI:R)
Scope Changed (S:C)
Confidentiality High (C:H)
Integrity High (I:H)
Availability High (A:H)

How to Fix CVE-2019-17625

To remediate this vulnerability, upgrade all affected Rambox dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

Rambox fixed: Latest secure release 
npm install Rambox@Latest secure release
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release: 

npm ls Rambox

How to Check if You Are Affected

To determine whether your Node.js application is affected by CVE-2019-17625, inspect your project dependencies using npm:

npm ls Rambox

Analyze the terminal output to locate any version of Rambox in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than the patched release), your application is affected.

Note: The npm ls Rambox command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-78: Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection'), where the product constructs all or part of an os command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended os command when it is sent to a downstream component. In Rambox, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

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.

CVE-2019-17625 Affected Rambox Versions

1 component(s)
Product / Package Ecosystem Affected Versions Fixed Version
Rambox
npm/Rambox
npm
≤ 0.6.9

References

NVD — CVE-2019-17625 NVD
https://nvd.nist.gov/vuln/detail/CVE-2019-17625
Rambox Source Repository REPOSITORY
https://github.com/Ekultek/CVE-2019-17625
Rambox Source Repository REPOSITORY
https://github.com/ramboxapp/community-edition
web.archive.org/web/20211209122051/... WEB
https://web.archive.org/web/20211209122051/https://github.com/ramboxapp/community-edition/issues/2418

Frequently Asked Questions

What is CVE-2019-17625?
CVE-2019-17625 is a security vulnerability in Rambox involving Rambox RCE Vulnerability under CWE-78: Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection').
Which Rambox versions are affected?
Affected versions include releases prior to current release patches across affected packages: Rambox.
What version fixes CVE-2019-17625?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
Is Rambox affected?
Yes, Rambox is affected in releases prior to Latest secure release. Upgrade your dependency to Latest secure release or later.
What is the CVSS score of CVE-2019-17625?
CVE-2019-17625 has a CVSS v3.1 base score of 9.0 (CRITICAL) with vector string CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:H.
What CWE is associated with CVE-2019-17625?
CVE-2019-17625 is classified under CWE-78: Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection') (The product constructs all or part of an OS command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended OS command when it is sent to a downstream component.).
How can I check npm dependencies for CVE-2019-17625?
Run the dependency tree command: 'npm ls Rambox'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-2gc6-2h2g-ph48",
  "modified" : "2023-07-18T20:31:10Z",
  "published" : "2022-05-24T16:58:57Z",
  "aliases" : [ "CVE-2019-17625" ],
  "summary" : "Rambox RCE Vulnerability",
  "details" : "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.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:H"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "npm",
      "name" : "Rambox"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "last_affected" : "0.6.9"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2019-17625"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/Ekultek/CVE-2019-17625"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/ramboxapp/community-edition"
  }, {
    "type" : "WEB",
    "url" : "https://web.archive.org/web/20211209122051/https://github.com/ramboxapp/community-edition/issues/2418"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-78", "CWE-79" ],
    "severity" : "CRITICAL",
    "github_reviewed" : true,
    "github_reviewed_at" : "2023-07-18T20:31:10Z",
    "nvd_published_at" : "2019-10-16T12:15:00Z"
  }
}