CVE-2022-35143 json
Raneto v0.17.0 employs weak password complexity requirements
published 2022-08-04 4 y ago modified 2026-06-17 4 mo ago also GHSA-7942-2fx8-qhpf , EUVD-2022-6502
- cvss
- 9.8
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.7%
- EPSS 1.7% chance of exploitation in 30 days, percentile 77%
- public exploits
- 0
- none known
Summary
Renato v0.17.0 employs weak password complexity requirements, allowing attackers to crack user passwords via brute-force attacks.
Patch / fix
- npm raneto 0.17.1
- raneto_project raneto 0.17.1
Exploit prediction
1.71% chance of exploitation in the next 30 days, higher than 77% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- gainsec.com https://gainsec.com/2022/08/04/cve-2022-35142-cve-2022-35143-cve-2022-35144/ referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| GitHub | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| npm | raneto | <0.17.1 |
0.17.1 |
Classification
- Weakness
-
- CWE-521 Weak Password Requirements
References
-
gainsec.com
/2022/08/04/cve-2022-35142-cve-2022-35143-cve-2022-35144/
exploit, patch, third-party-advisory
-
github.com
/ryanlelek/Raneto/pull/370
web
-
github.com
/ryanlelek/Raneto/commit/55e442c9bc67b845094e14ceb228e95c639595be
web
-
cwe.mitre.org
/data/definitions/521.html
web, third-party-advisory
-
raneto.com
/
product
-
github.com
/gilbitron/Raneto/releases
web, release-notes, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2022-35143
advisory
-
gainsec.com
/2022/08/04/cve-2022-35142-cve-2022-35143-cve-2022-35144
web
-
github.com
/ryanlelek/Raneto
package
-
github.com
/ryanlelek/Raneto/releases/tag/0.17.1
web
-
raneto.com
web
Sources
- CVE List CVE-2022-35143
- GitHub Advisory GHSA-7942-2fx8-qhpf
- NVD CVE-2022-35143
Fencer Vulns 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.