Command Injection in opencv

published 2019-06-04 7y ago modified 2020-08-31 6y ago

cvss: —; not scored
cisa kev: Not listed; not in CISA's catalog
epss: —; no score, EPSS covers CVEs only
public exploits: 0; none known

Versions of `opencv`prior to 6.1.0 are vulnerable to Command Injection. The utils/ script find-opencv.js does not validate user input allowing attackers to execute arbitrary commands.

## Recommendation

Upgrade to version 6.1.0.

Patch / fix

fixed in 1 links 1

npm opencv 6.1.0

github.com/peterbraden/node-opencv@81a4b86 commit

Is GHSA-f698-m2v9-5fh3 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

Affected packages

ecosystem	package	affected	fixed in
npm	opencv	<6.1.0	6.1.0

Classification

Weakness

CWE-77 Improper Neutralization of Special Elements used in a Command

References

Sources

GitHub Advisory GHSA-f698-m2v9-5fh3

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.