Quick answers
- Is This vulnerability exploited in the wild?
- No. Junglewise Threat Intelligence has no report of This vulnerability being exploited in the wild.
- How severe is This vulnerability?
- Informational severity, published 4 June 2019.
- Which products and versions are affected?
- opencv (npm) SEMVER:introduced=0,fixed=6.1.0.
- Is there a fix for This vulnerability?
- Yes. opencv (npm): upgrade to 6.1.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is This vulnerability attacked?
- It is attacked with local access.
- Am I affected?
- Check whether you run opencv (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
- opencv (npm): upgrade to 6.1.0 or later
npm install opencv@6.1.0
Technical details
The vulnerability is a command injection flaw (CWE-77) in the utils/find-opencv.js script that fails to properly validate user input before passing it to shell execution. An attacker can inject arbitrary shell commands through unvalidated parameters during the npm package installation or build process. The attack requires local access or the ability to influence the build environment (e.g., via a compromised dependency or malicious environment variables). The fix was applied in version 6.1.0 by removing untrusted input from exec calls.
Affected products
- <UNKNOWN> opencv before 6.1.0
Timeline
- 2019-06-04: disclosed
- 2019-06-04: patched: Fixed in version 6.1.0