CVE-2022-0848 in the critical feed json
OS Command Injection in part-db/part-db
published 4y ago modified 4mo ago also EUVD-2022-15891
- cvss
- 10.0
- version 3.0, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 35.4%
- EPSS 35.4% chance of exploitation in 30 days, percentile 98%
- public exploits
- 1
- Exploit-DB
Summary
OS Command Injection in GitHub repository part-db/part-db prior to 0.5.11.
Patch / fix
- part-db part-db/part-db 0.5.11
Is CVE-2022-0848 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerTimeline
- Published
- First public exploit (EDB-50800)
Exploit prediction
35.44% chance of exploitation in the next 30 days, higher than 98% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-50800 part-db 0.5.11 - Remote Code Execution (RCE) webapps, 2022-03-07
- huntr.dev https://huntr.dev/bounties/3e91685f-cfb9-4ee4-abaf-9b712a8fd5a6 referenced PoC, tagged "exploit" by a source, unverified
- packetstormsecurity.com http://packetstormsecurity.com/files/166217/part-db-0.5.11-Remote-Code-Execution.html referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.0 | 10.0 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H |
| NVD | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 10.0 | AV:N/AC:L/Au:N/C:C/I:C/A:C |
Affected products
- part-db part-db/part-db
Classification
- Weakness
-
- CWE-78 Improper Neutralization of Special Elements used in an OS Command
References
-
github.com
/part-db/part-db/commit/9cd4eee393028aa4cab70fcbac284b0028c0bc95
patch, third-party-advisory
-
huntr.dev
/bounties/3e91685f-cfb9-4ee4-abaf-9b712a8fd5a6
exploit, patch, third-party-advisory
-
packetstormsecurity.com
/files/166217/part-db-0.5.11-Remote-Code-Execution.html
exploit, third-party-advisory, vdb-entry
Sources
- CVE List CVE-2022-0848
- NVD CVE-2022-0848
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.