CVSS 3.1
7.5 highCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:NHigh (7.5) in fujitsu. EPSS 0.4% estimated probability of exploitation activity in the next 30 days.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:NExplain CVE-2024-39921 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2024-39921?via=ask-ai-copy and https://cve.bz/cve/CVE-2024-39921?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2024-39921 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
From the NVD's CPE matches.
| Product | Affected |
|---|---|
| fujitsu:ipcom_ve2_ls_100_firmware | from v01l04nf0001 through v01l06nf0112 |
| fujitsu:ipcom_ve2_ls_200_firmware | from v01l04nf0001 through v01l06nf0112 |
| fujitsu:ipcom_ve2_ls_220_firmware | from v01l04nf0001 through v01l06nf0112 |
| fujitsu:ipcom_ve2_ls_plus_100_firmware | from v01l04nf0001 through v01l06nf0112 |
| fujitsu:ipcom_ve2_ls_plus_200_firmware | from v01l04nf0001 through v01l06nf0112 |
| fujitsu:ipcom_ve2_ls_plus_220_firmware | from v01l04nf0001 through v01l06nf0112 |
| fujitsu:ipcom_ve2_ls_plus2_200_firmware | from v01l04nf0001 through v01l06nf0112 |
| fujitsu:ipcom_ve2_ls_plus2_220_firmware | from v01l04nf0001 through v01l06nf0112 |
| fujitsu:ipcom_ve2_sc_plus_100_firmware | from v01l04nf0001 through v01l06nf0112 |
| fujitsu:ipcom_ve2_sc_plus_200_firmware | from v01l04nf0001 through v01l06nf0112 |
| fujitsu:ipcom_ve2_sc_plus_220_firmware | from v01l04nf0001 through v01l06nf0112 |
| fujitsu:ipcom_ex2_in_3200_firmware | from v01l02nf0001 through v01l06nf0401 |
| fujitsu:ipcom_ex2_in_3200_firmware | from v01l20nf0001 through v01l20nf0401 |
| fujitsu:ipcom_ex2_in_3200_firmware | from v02l20nf0001 through v02l21nf0301 |
| fujitsu:ipcom_ex2_in_3500_firmware | from v01l02nf0001 through v01l06nf0401 |
| fujitsu:ipcom_ex2_in_3500_firmware | from v01l20nf0001 through v01l20nf0401 |
| fujitsu:ipcom_ex2_in_3500_firmware | from v02l20nf0001 through v02l21nf0301 |
| fujitsu:ipcom_ex2_lb_3200_firmware | from v01l02nf0001 through v01l06nf0401 |
| fujitsu:ipcom_ex2_lb_3200_firmware | from v01l20nf0001 through v01l20nf0401 |
| fujitsu:ipcom_ex2_lb_3200_firmware | from v02l20nf0001 through v02l21nf0301 |
| fujitsu:ipcom_ex2_lb_3500_firmware | from v01l02nf0001 through v01l06nf0401 |
| fujitsu:ipcom_ex2_lb_3500_firmware | from v01l20nf0001 through v01l20nf0401 |
| fujitsu:ipcom_ex2_lb_3500_firmware | from v02l20nf0001 through v02l21nf0301 |
| fujitsu:ipcom_ex2_sc_3200_firmware | from v01l02nf0001 through v01l06nf0401 |
| fujitsu:ipcom_ex2_sc_3200_firmware | from v01l20nf0001 through v01l20nf0401 |
| fujitsu:ipcom_ex2_sc_3200_firmware | from v02l20nf0001 through v02l21nf0301 |
| fujitsu:ipcom_ex2_sc_3500_firmware | from v01l02nf0001 through v01l06nf0401 |
| fujitsu:ipcom_ex2_sc_3500_firmware | from v01l20nf0001 through v01l20nf0401 |
| fujitsu:ipcom_ex2_sc_3500_firmware | from v02l20nf0001 through v02l21nf0301 |
| fujitsu:ipcom_ex2_dc_3200_firmware | from v01l02nf0001 through v01l06nf0401 |
| fujitsu:ipcom_ex2_dc_3200_firmware | from v01l20nf0001 through v01l20nf0401 |
| fujitsu:ipcom_ex2_dc_3200_firmware | from v02l20nf0001 through v02l21nf0301 |
| fujitsu:ipcom_ex2_dc_3500_firmware | from v01l02nf0001 through v01l06nf0401 |
| fujitsu:ipcom_ex2_dc_3500_firmware | from v01l20nf0001 through v01l20nf0401 |
| fujitsu:ipcom_ex2_dc_3500_firmware | from v02l20nf0001 through v02l21nf0301 |
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.