CVE-2021-4070 json
Off-by-one Error in v2fly/v2ray-core
published 2022-02-23 4 y ago modified 2026-06-17 4 mo ago also GHSA-4cxw-hq44-r344 , GO-2022-0550 , EUVD-2022-0809
- cvss
- 5.9
- version 3.0, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.9%
- EPSS 0.9% chance of exploitation in 30 days, percentile 58%
- public exploits
- 0
- none known
Summary
Off-by-one Error in GitHub repository v2fly/v2ray-core prior to 4.44.0.
Patch / fix
- go github.com/v2fly/v2ray-core/v4 4.44.0
- v2fly v2fly/v2ray-core 4.44.0
- golang-v2ray-core Debian 14, Debian 13, Debian 12 4.34.0-7
debian advisories DEBIAN-CVE-2021-4070
Exploit prediction
0.86% chance of exploitation in the next 30 days, higher than 58% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- huntr.dev https://huntr.dev/bounties/8da19456-4d89-41ef-9781-a41efd6a1877 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.0 | 5.9 | CVSS:3.0/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L |
| NVD | 3.1 | 9.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H |
| NVD | 2.0 | 6.4 | AV:N/AC:L/Au:N/C:P/I:N/A:P |
| GitHub | 3.1 | 9.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| go | github.com/v2fly/v2ray-core/v4 | <4.44.0 |
4.44.0 |
| go | github.com/v2fly/v2ray-core | all versions |
no fix listed |
Affected products
- v2fly v2fly/v2ray-core
Classification
- Weakness
-
- CWE-193 Off-by-one Error
References
-
github.com
/v2fly/v2ray-core/commit/c1af2bfd7aa59a4482aa7f6ec4b9208c1d350b5c
web, patch, third-party-advisory
-
huntr.dev
/bounties/8da19456-4d89-41ef-9781-a41efd6a1877
web, exploit, patch, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2021-4070
advisory
-
github.com
/v2fly/v2ray-core
package
-
github.com
/advisories/GHSA-4cxw-hq44-r344
advisory
Sources
- CVE List CVE-2021-4070
- GitHub Advisory GHSA-4cxw-hq44-r344
- NVD CVE-2021-4070
- OSV GO-2022-0550
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.