CVE-2022-28381 in the critical feed json
Mediaserver.exe in ALLMediaServer 1.6 has a stack-based buffer overflow that allows remote attackers to execute arbitrary code via a long s…
published 4y ago modified 4mo ago also EUVD-2022-32826
- cvss
- 9.8
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 70.4%
- EPSS 70.4% chance of exploitation in 30 days, percentile 99.3%
- public exploits
- 1
- Metasploit
Summary
Mediaserver.exe in ALLMediaServer 1.6 has a stack-based buffer overflow that allows remote attackers to execute arbitrary code via a long string to TCP port 888, a related issue to CVE-2017-17932.
Is CVE-2022-28381 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
- First public exploit (Metasploit exploit/windows/misc/cve_2022_28381_allmediaserver_bof)
- Published
Exploit prediction
70.41% chance of exploitation in the next 30 days, higher than 99.3% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- Metasploit exploit/windows/misc/cve_2022_28381_allmediaserver_bof ALLMediaServer 1.6 SEH Buffer Overflow metasploit exploit, good rank, 2022-04-01
- github.com https://github.com/Matrix07ksa/ALLMediaServer-1.6-Buffer-Overflow referenced PoC, tagged "exploit" by a source, unverified
- packetstormsecurity.com http://packetstormsecurity.com/files/166573/ALLMediaServer-1.6-Buffer-Overflow.html referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| 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 |
Classification
- Weakness
-
- CWE-787 Out-of-bounds Write
References
-
github.com
/Matrix07ksa/ALLMediaServer-1.6-Buffer-Overflow
exploit, third-party-advisory
-
packetstormsecurity.com
/files/166573/ALLMediaServer-1.6-Buffer-Overflow.html
exploit, third-party-advisory, vdb-entry
Sources
- CVE List CVE-2022-28381
- NVD CVE-2022-28381
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.