CVE-2022-29631 json
Server-Side Request Forgery in Jodd HTTP
published 4y ago modified 4mo ago also GHSA-pp3c-cf6j-m3ff , EUVD-2022-6117
- cvss
- 7.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.0%
- EPSS 1.0% chance of exploitation in 30 days, percentile 63%
- public exploits
- 0
- none known
Summary
Jodd HTTP v6.0.9 was discovered to contain multiple CLRF injection vulnerabilities via the components jodd.http.HttpRequest#set and `jodd.http.HttpRequest#send. These vulnerabilities allow attackers to execute Server-Side Request Forgery (SSRF) via a crafted TCP payload.
Patch / fix
Is CVE-2022-29631 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
1.00% chance of exploitation in the next 30 days, higher than 63% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- github.com https://github.com/oblac/jodd/issues/787 referenced PoC, tagged "exploit" by a source, unverified
- github.com https://github.com/oblac/jodd-http/issues/9 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N |
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:N/I:P/A:N |
| GitHub | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| maven | org.jodd:jodd-http | >=5.0.0, <6.2.1 |
6.2.1 |
Classification
References
-
github.com
/oblac/jodd-http/commit/e50f573c8f6a39212ade68c6eb1256b2889fa8a6
web
-
github.com
/oblac/jodd/issues/787
web, exploit, issue-tracking, third-party-advisory
-
github.com
/oblac/jodd-http/issues/9
web, exploit, issue-tracking, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2022-29631
advisory
-
github.com
/oblac/jodd-http
package
Sources
- CVE List CVE-2022-29631
- GitHub Advisory GHSA-pp3c-cf6j-m3ff
- NVD CVE-2022-29631
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.