CVE-2022-41777 json
nadesiko3 allows remote attacker to inject invalid value to decodeURIComponent of nako3edit
published 2022-12-05 3 y ago modified 2026-06-17 4 mo ago also GHSA-x2jx-w3wm-9p3p , EUVD-2022-7765
- cvss
- 7.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.6%
- EPSS 1.6% chance of exploitation in 30 days, percentile 76%
- public exploits
- 0
- none known
Summary
Improper check or handling of exceptional conditions vulnerability in Nako3edit, editor component of nadesiko3 (PC Version) v3.3.74 and earlier allows a remote attacker to inject an invalid value to decodeURIComponent of nako3edit, which may lead the server to crash.
Patch / fix
- npm nadesiko3 3.3.75
CISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
- Assessed
- 18 mo ago
Exploit prediction
1.60% chance of exploitation in the next 30 days, higher than 76% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
| NVD | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
| CNA | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
| GitHub | 3.0 | 5.3 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| npm | nadesiko3 | <3.3.75 |
3.3.75 |
Affected products
- kujirahand Nako3edit, editor component of nadesiko3 (PC Version)
Classification
References
-
github.com
/kujirahand/nadesiko3/issues/1325
web, issue-tracking, patch, third-party-advisory
-
github.com
/kujirahand/nadesiko3/issues/1347
web, issue-tracking, third-party-advisory
-
jvn.jp
/en/jp/JVN56968681/index.html
web, third-party-advisory, vdb-entry
-
nvd.nist.gov
/vuln/detail/CVE-2022-41777
advisory
-
github.com
/kujirahand/nadesiko3
package
-
github.com
/kujirahand/nadesiko3/releases/tag/3.3.75
web
Sources
- CVE List CVE-2022-41777
- GitHub Advisory GHSA-x2jx-w3wm-9p3p
- NVD CVE-2022-41777
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.