CVE-2022-0508 json
Server-Side Request Forgery (SSRF) in chocobozzz/peertube
published 4y ago modified 4mo ago also GHSA-mv26-cx23-vrfg , EUVD-2022-1109
- cvss
- 6.5
- 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 59%
- public exploits
- 0
- none known
Summary
Server-Side Request Forgery (SSRF) in GitHub repository chocobozzz/peertube prior to f33e515991a32885622b217bf2ed1d1b0d9d6832
Patch / fix
- npm @peertube/embed-api 4.1.0-rc.1
- chocobozzz chocobozzz/peertube f33e515991a32885622b217bf2ed1d1b0d9d6832
Is CVE-2022-0508 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 FencerExploit prediction
0.89% chance of exploitation in the next 30 days, higher than 59% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- huntr.dev https://huntr.dev/bounties/c3724574-b6c9-430b-849b-40dd2b20f23c referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.0 | 6.5 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N |
| NVD | 3.1 | 5.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N |
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:P/I:N/A:N |
| GitHub | 3.0 | 6.5 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| npm | @peertube/embed-api | <4.1.0-rc.1 |
4.1.0-rc.1 |
Affected products
- chocobozzz chocobozzz/peertube
Classification
- Weakness
-
- CWE-918 Server-Side Request Forgery
References
-
github.com
/chocobozzz/peertube/commit/f33e515991a32885622b217bf2ed1d1b0d9d6832
web, patch, third-party-advisory
-
huntr.dev
/bounties/c3724574-b6c9-430b-849b-40dd2b20f23c
web, exploit, patch, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2022-0508
advisory
-
github.com
/chocobozzz/peertube
package
Sources
- CVE List CVE-2022-0508
- GitHub Advisory GHSA-mv26-cx23-vrfg
- NVD CVE-2022-0508
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.