Quick answers
- Is CVE-2019-19609 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2019-19609 being exploited in the wild.
- How severe is CVE-2019-19609?
- Low severity, with a CVSS score of 3.1, published 4 September 2020.
- Which products and versions are affected?
- strapi (npm) SEMVER:introduced=0,fixed=3.0.0-beta.17.8.
- Is there a fix for CVE-2019-19609?
- Yes. strapi (npm): upgrade to 3.0.0-beta.17.8 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2019-19609 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2019-19609?
- Check whether you run strapi (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- strapi (npm): upgrade to 3.0.0-beta.17.8 or later
npm install strapi@3.0.0-beta.17.8
Technical details
The vulnerability is a command injection flaw (CWE-77) in the /admin/plugins/install/ route of Strapi. The application fails to properly sanitize plugin names passed to this endpoint, allowing an authenticated attacker with admin privileges to inject arbitrary shell commands. The vulnerability requires network access to the admin interface and valid admin credentials. Successful exploitation allows remote code execution with server privileges. The fix was implemented in version 3.0.0-beta.17.8 via input validation on plugin names.
Affected products
- Strapi Strapi before 3.0.0-beta.17.8
Identifiers
- CVE-2019-19609
- GHSA-9p2w-rmx4-9mw7
Timeline
- 2020-09-04: disclosed
- 2019-12-01: patched: Fix merged in PR #4636 on 2019-12-01; patched in version 3.0.0-beta.17.8