CVSS 3.1
9.8 criticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HCritical (9.8) in fujitsu. EPSS 2.2% 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:H/A:HExplain CVE-2022-29516 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2022-29516?via=ask-ai-copy and https://cve.bz/cve/CVE-2022-29516?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-2022-29516 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_ex2_nw_1100_firmware | before v01l05_nf0501 |
| fujitsu:ipcom_ex2_nw_3500_firmware | before v01l05_nf0501 |
| fujitsu:ipcom_ex2_nw_3200_firmware | before v01l05_nf0501 |
| fujitsu:ipcom_ex2_sc_1100_firmware | before v01l05_nf0501 |
| fujitsu:ipcom_ex2_sc_3500_firmware | before v01l05_nf0501 |
| fujitsu:ipcom_ex2_sc_3200_firmware | before v01l05_nf0501 |
| fujitsu:ipcom_ex2_lb_1100_firmware | before v01l05_nf0501 |
| fujitsu:ipcom_ex2_lb_3500_firmware | before v01l05_nf0501 |
| fujitsu:ipcom_ex2_lb_3200_firmware | before v01l05_nf0501 |
| fujitsu:ipcom_ex2_in_1100_firmware | before v01l05_nf0501 |
| fujitsu:ipcom_ex2_in_3200_firmware | before v01l05_nf0501 |
| fujitsu:ipcom_ex2_in_3500_firmware | before v01l05_nf0501 |
| fujitsu:ipcom_ex2_dc_3500_firmware | before v02l21_nf0201 |
| fujitsu:ipcom_ex2_dc_3200_firmware | before v02l21_nf0201 |
| fujitsu:ipcom_ex_in_2300_firmware | before e20l33_nf1101 |
| fujitsu:ipcom_ex_in_2500_firmware | before e20l33_nf1101 |
| fujitsu:ipcom_ex_in_2700_firmware | before e20l33_nf1101 |
| fujitsu:ipcom_ex_lb_1100_firmware | before e20l33_nf1101 |
| fujitsu:ipcom_ex_lb_1300_firmware | before e20l33_nf1101 |
| fujitsu:ipcom_ex_lb_2300_firmware | before e20l33_nf1101 |
| fujitsu:ipcom_ex_lb_2500_firmware | before e20l33_nf1101 |
| fujitsu:ipcom_ex_lb_2700_firmware | before e20l33_nf1101 |
| fujitsu:ipcom_ex_sc_1100_firmware | before e20l33_nf1101 |
| fujitsu:ipcom_ex_sc_1300_firmware | before e20l33_nf1101 |
| fujitsu:ipcom_ex_sc_2300_firmware | before e20l33_nf1101 |
| fujitsu:ipcom_ex_sc_2500_firmware | before e20l33_nf1101 |
| fujitsu:ipcom_ex_sc_2700_firmware | before e20l33_nf1101 |
| fujitsu:ipcom_ex_nw_1100_firmware | before e20l33_nf1101 |
| fujitsu:ipcom_ex_nw_1300_firmware | before e20l33_nf1101 |
| fujitsu:ipcom_ex_nw_2300_firmware | before e20l33_nf1101 |
| fujitsu:ipcom_ex_nw_2500_firmware | before e20l33_nf1101 |
| fujitsu:ipcom_ex_nw_2700_firmware | before e20l33_nf1101 |
| fujitsu:ipcom_ve2_ls_100_firmware | before e20l33_nf1101 |
| fujitsu:ipcom_ve2_ls_200_firmware | before e20l33_nf1101 |
| fujitsu:ipcom_ve2_ls_220_firmware | before e20l33_nf1101 |
| fujitsu:ipcom_ve2_ls_plus_100_firmware | before e20l33_nf1101 |
| fujitsu:ipcom_ve2_ls_plus_200_firmware | before e20l33_nf1101 |
| fujitsu:ipcom_ve2_ls_plus_220_firmware | before e20l33_nf1101 |
| fujitsu:ipcom_ve2_ls_plus2_200_firmware | before e20l33_nf1101 |
| fujitsu:ipcom_ve2_ls_plus2_220_firmware | before e20l33_nf1101 |
| fujitsu:ipcom_ve2_sc_100_firmware | before e20l33_nf1101 |
| fujitsu:ipcom_ve2_sc_200_firmware | before e20l33_nf1101 |
| fujitsu:ipcom_ve2_sc_220_firmware | before e20l33_nf1101 |
| fujitsu:ipcom_ve2_sc_plus_100_firmware | before e20l33_nf1101 |
| fujitsu:ipcom_ve2_sc_plus_200_firmware | before e20l33_nf1101 |
| fujitsu:ipcom_ve2_sc_plus_220_firmware | before e20l33_nf1101 |
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.