CVE-2024-3218 json
Shibang Communications IP Network Intercom Broadcasting System busyscreenshotpush.php path traversal
published 2024-04-02 2 y ago modified 2026-06-17 4 mo ago also EUVD-2024-31810
- cvss
- 5.4
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.7%
- EPSS 0.7% chance of exploitation in 30 days, percentile 51%
- public exploits
- 0
- none known
Summary
A vulnerability classified as critical has been found in Shibang Communications IP Network Intercom Broadcasting System 1.0. This affects an unknown part of the file /php/busyscreenshotpush.php. The manipulation of the argument jsondata[callee]/jsondata[imagename] leads to path traversal: '../filedir'. It is possible to initiate the attack remotely. The exploit has been disclosed to the public and may be used. The identifier VDB-259065 was assigned to this vulnerability.
CISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- partial
- Assessed
- 2 y ago
Exploit prediction
0.65% chance of exploitation in the next 30 days, higher than 51% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- github.com https://github.com/garboa/cve_3/blob/main/file_put_content.md referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 5.4 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L |
| CNA | 3.0 | 5.4 | CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L |
| CNA | 2.0 | 5.5 | AV:N/AC:L/Au:S/C:N/I:P/A:P |
Affected products
- Shibang Communications IP Network Intercom Broadcasting System
- shibangcommunications ip_network_intercom_broadcasting_system
Classification
- Weakness
-
- CWE-24 Path Traversal: '../filedir'
References
-
github.com
/garboa/cve_3/blob/main/file_put_content.md
exploit
-
vuldb.com
/?id.259065
vdb-entry, technical-description
-
vuldb.com
/?ctiid.259065
signature, permissions-required
-
vuldb.com
/?submit.308510
third-party-advisory
Sources
- CVE List CVE-2024-3218
- NVD CVE-2024-3218
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.