Is CVE-2019-10061 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2019-10061 being exploited in the wild.

How severe is CVE-2019-10061?

Low severity, with a CVSS score of 3, published 12 October 2021.

Which products and versions are affected?

opencv (npm) SEMVER:introduced=0,fixed=6.1.0.

Is there a fix for CVE-2019-10061?

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 CVE-2019-10061 attacked?

It is attacked over the network.

Am I affected by CVE-2019-10061?

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.

CVE-2019-10061: node-opencv OS command injection in find-opencv

CVE-2019-10061 · Severity: low · CVSS 3 · Published 2021-10-12

node-opencv is a popular Node.js library that provides bindings to OpenCV, a computer vision library used for image and video processing tasks. A command injection vulnerability in the find-opencv utility allows attackers to execute arbitrary system commands without authentication, potentially compromising the entire system running applications that depend on this library.

Vendors: npm.

Quick answers

Is CVE-2019-10061 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2019-10061 being exploited in the wild.
How severe is CVE-2019-10061?: Low severity, with a CVSS score of 3, published 12 October 2021.
Which products and versions are affected?: opencv (npm) SEMVER:introduced=0,fixed=6.1.0.
Is there a fix for CVE-2019-10061?: 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 CVE-2019-10061 attacked?: It is attacked over the network.
Am I affected by CVE-2019-10061?: 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 an OS command injection flaw (CWE-78) in utils/find-opencv.js that fails to validate or sanitize user input before passing it to shell execution. The vulnerable code constructs shell commands with untrusted input, allowing attackers to inject arbitrary commands. The attack vector is network-accessible if the library processes untrusted input from external sources. No authentication or user interaction is required. An attacker can execute arbitrary commands with the privileges of the process running the application. The vulnerability was fixed in version 6.1.0 by removing untrusted input from the exec call.

Affected products

opencv prior to 6.1.0

Identifiers

CVE-2019-10061
GHSA-mc7w-4cjf-c973

Timeline

2021-10-12: disclosed
2021-10-07: patched: Fixed in version 6.1.0

References

https://github.com/peterbraden/node-opencv/commit/81a4b8620188e89f7e4fc985f3c89b58d4bcc86b

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.