Skip to content
Fencer Intel
critical 9.8

CVE-2017-16042 json

Growl before 1.10.0 vulnerable to Command Injection

published 8y ago modified 4mo ago also GHSA-qh2h-chj9-jffq , EUVD-2018-0199

cvss
9.8
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
4.6%
EPSS 4.6% chance of exploitation in 30 days, percentile 91%
public exploits
0
none known

Summary

Growl adds growl notification support to nodejs. Growl before 1.10.2 does not properly sanitize input before passing it to exec, allowing for arbitrary command execution.

Patch / fix

  • npm growl 1.10.0
  • growl_project growl 1.10.2
  • node-growl Debian 14, Debian 13, Debian 12 1.10.5-1

debian advisories DEBIAN-CVE-2017-16042

Is CVE-2017-16042 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2017-16042 updated cvss 8.1

nodejs-growl: Does not properly sanitize input before passing it to exec

  • Red Hat Mobile Application Platform 4 nodejs-growl Red Hat Virtualization 4 ovirt-engine-dashboard, ovirt-engine-ui-extensions
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

4.58% chance of exploitation in the next 30 days, higher than 91% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.0 9.8 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD 2.0 7.5 AV:N/AC:L/Au:N/C:P/I:P/A:P
GitHub 3.0 9.8 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
npm growl
<1.10.0
1.10.0

Affected products

  • HackerOne growl node module

Classification

Weakness
  • CWE-94 Improper Control of Generation of Code
  • CWE-78 Improper Neutralization of Special Elements used in an OS Command

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.