Insecure Default Configuration in tesseract.js

published 2019-06-05 7y ago modified 2021-08-04 5y ago

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

Versions of `tesseract.js` prior to 1.0.19 default to using a third-party proxy. Requests may be proxied through `crossorigin.me` which clearly states is not suitable for production use. This may lead to instability and privacy violations.

## Recommendation

Upgrade to version 1.0.19 or later.

Patch / fix

fixed in 1 links 2

npm tesseract.js 1.0.19

github.com/naptha/tesseract.js@679eba0 commit
github.com/naptha/tesseract.js#267 pull request

Is GHSA-83rx-c8cr-6j8q 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

CVSS scores

assigned by	version	score	vector
GitHub	3.1	5.9	CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N

Affected packages

ecosystem	package	affected	fixed in
npm	tesseract.js	<1.0.19	1.0.19

Classification

Weakness

CWE-829 Inclusion of Functionality from Untrusted Control Sphere

References

Sources

GitHub Advisory GHSA-83rx-c8cr-6j8q

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.