CVE-2024-39921

Observable timing discrepancy issue exists in IPCOM EX2 Series V01L02NF0001 to V01L06NF0401, V01L20NF0001 to V01L20NF0401, V02L20NF0001 to V02L21NF0301, and IPCOM VE2 Series V01L04NF0001 to V01L06NF0112. If this vulnerability is exploited, some of the encrypted communication may be decrypted by an attacker who can obtain the contents of the communication.

Published: 2024-09-03 Last update: 2026-06-17 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2024-39921 is rated Moderate Risk (51.2/100): CVSS High severity, with medium exploitation likelihood (EPSS 0.40%). Review affected assets and schedule remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2024-39921

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-01-24 0.30% 0.40% +0.11%
2 2025-10-28 0.39% 0.30% -0.09%
3 2025-10-13 — 0.39% —

Full EPSS history (9 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2024-39921

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.5 3.1 HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:N)
Service keeps running; no real outage angle.
 3.9 3.6 [email protected]
7.5 3.1 HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:N)
Service keeps running; no real outage angle.
 3.9 3.6 134c704f-9b21-4f2e-91b3-4a467353bcc0

Weakness enumeration for CVE-2024-39921

Affected software / configurations for CVE-2024-39921

Vendor Product Version Raw CPE
fujitsu ipcom_ve2_ls_100_firmware >= v01l04nf0001, <= v01l06nf0112 cpe:2.3:o:fujitsu:ipcom_ve2_ls_100_firmware:*:*:*:*:*:*:*:*
fujitsu ipcom_ve2_ls_200_firmware >= v01l04nf0001, <= v01l06nf0112 cpe:2.3:o:fujitsu:ipcom_ve2_ls_200_firmware:*:*:*:*:*:*:*:*
fujitsu ipcom_ve2_ls_220_firmware >= v01l04nf0001, <= v01l06nf0112 cpe:2.3:o:fujitsu:ipcom_ve2_ls_220_firmware:*:*:*:*:*:*:*:*
fujitsu ipcom_ve2_ls_plus_100_firmware >= v01l04nf0001, <= v01l06nf0112 cpe:2.3:o:fujitsu:ipcom_ve2_ls_plus_100_firmware:*:*:*:*:*:*:*:*
fujitsu ipcom_ve2_ls_plus_200_firmware >= v01l04nf0001, <= v01l06nf0112 cpe:2.3:o:fujitsu:ipcom_ve2_ls_plus_200_firmware:*:*:*:*:*:*:*:*
fujitsu ipcom_ve2_ls_plus_220_firmware >= v01l04nf0001, <= v01l06nf0112 cpe:2.3:o:fujitsu:ipcom_ve2_ls_plus_220_firmware:*:*:*:*:*:*:*:*
fujitsu ipcom_ve2_ls_plus2_200_firmware >= v01l04nf0001, <= v01l06nf0112 cpe:2.3:o:fujitsu:ipcom_ve2_ls_plus2_200_firmware:*:*:*:*:*:*:*:*
fujitsu ipcom_ve2_ls_plus2_220_firmware >= v01l04nf0001, <= v01l06nf0112 cpe:2.3:o:fujitsu:ipcom_ve2_ls_plus2_220_firmware:*:*:*:*:*:*:*:*
fujitsu ipcom_ve2_sc_plus_100_firmware >= v01l04nf0001, <= v01l06nf0112 cpe:2.3:o:fujitsu:ipcom_ve2_sc_plus_100_firmware:*:*:*:*:*:*:*:*
fujitsu ipcom_ve2_sc_plus_200_firmware >= v01l04nf0001, <= v01l06nf0112 cpe:2.3:o:fujitsu:ipcom_ve2_sc_plus_200_firmware:*:*:*:*:*:*:*:*
fujitsu ipcom_ve2_sc_plus_220_firmware >= v01l04nf0001, <= v01l06nf0112 cpe:2.3:o:fujitsu:ipcom_ve2_sc_plus_220_firmware:*:*:*:*:*:*:*:*
fujitsu ipcom_ex2_in_3200_firmware >= v01l02nf0001, <= v01l06nf0401 cpe:2.3:o:fujitsu:ipcom_ex2_in_3200_firmware:*:*:*:*:*:*:*:*
fujitsu ipcom_ex2_in_3200_firmware >= v01l20nf0001, <= v01l20nf0401 cpe:2.3:o:fujitsu:ipcom_ex2_in_3200_firmware:*:*:*:*:*:*:*:*
fujitsu ipcom_ex2_in_3200_firmware >= v02l20nf0001, <= v02l21nf0301 cpe:2.3:o:fujitsu:ipcom_ex2_in_3200_firmware:*:*:*:*:*:*:*:*
fujitsu ipcom_ex2_in_3500_firmware >= v01l02nf0001, <= v01l06nf0401 cpe:2.3:o:fujitsu:ipcom_ex2_in_3500_firmware:*:*:*:*:*:*:*:*
fujitsu ipcom_ex2_in_3500_firmware >= v01l20nf0001, <= v01l20nf0401 cpe:2.3:o:fujitsu:ipcom_ex2_in_3500_firmware:*:*:*:*:*:*:*:*
fujitsu ipcom_ex2_in_3500_firmware >= v02l20nf0001, <= v02l21nf0301 cpe:2.3:o:fujitsu:ipcom_ex2_in_3500_firmware:*:*:*:*:*:*:*:*
fujitsu ipcom_ex2_lb_3200_firmware >= v01l02nf0001, <= v01l06nf0401 cpe:2.3:o:fujitsu:ipcom_ex2_lb_3200_firmware:*:*:*:*:*:*:*:*
fujitsu ipcom_ex2_lb_3200_firmware >= v01l20nf0001, <= v01l20nf0401 cpe:2.3:o:fujitsu:ipcom_ex2_lb_3200_firmware:*:*:*:*:*:*:*:*
fujitsu ipcom_ex2_lb_3200_firmware >= v02l20nf0001, <= v02l21nf0301 cpe:2.3:o:fujitsu:ipcom_ex2_lb_3200_firmware:*:*:*:*:*:*:*:*
fujitsu ipcom_ex2_lb_3500_firmware >= v01l02nf0001, <= v01l06nf0401 cpe:2.3:o:fujitsu:ipcom_ex2_lb_3500_firmware:*:*:*:*:*:*:*:*
fujitsu ipcom_ex2_lb_3500_firmware >= v01l20nf0001, <= v01l20nf0401 cpe:2.3:o:fujitsu:ipcom_ex2_lb_3500_firmware:*:*:*:*:*:*:*:*
fujitsu ipcom_ex2_lb_3500_firmware >= v02l20nf0001, <= v02l21nf0301 cpe:2.3:o:fujitsu:ipcom_ex2_lb_3500_firmware:*:*:*:*:*:*:*:*
fujitsu ipcom_ex2_sc_3200_firmware >= v01l02nf0001, <= v01l06nf0401 cpe:2.3:o:fujitsu:ipcom_ex2_sc_3200_firmware:*:*:*:*:*:*:*:*
fujitsu ipcom_ex2_sc_3200_firmware >= v01l20nf0001, <= v01l20nf0401 cpe:2.3:o:fujitsu:ipcom_ex2_sc_3200_firmware:*:*:*:*:*:*:*:*
fujitsu ipcom_ex2_sc_3200_firmware >= v02l20nf0001, <= v02l21nf0301 cpe:2.3:o:fujitsu:ipcom_ex2_sc_3200_firmware:*:*:*:*:*:*:*:*
fujitsu ipcom_ex2_sc_3500_firmware >= v01l02nf0001, <= v01l06nf0401 cpe:2.3:o:fujitsu:ipcom_ex2_sc_3500_firmware:*:*:*:*:*:*:*:*
fujitsu ipcom_ex2_sc_3500_firmware >= v01l20nf0001, <= v01l20nf0401 cpe:2.3:o:fujitsu:ipcom_ex2_sc_3500_firmware:*:*:*:*:*:*:*:*
fujitsu ipcom_ex2_sc_3500_firmware >= v02l20nf0001, <= v02l21nf0301 cpe:2.3:o:fujitsu:ipcom_ex2_sc_3500_firmware:*:*:*:*:*:*:*:*
fujitsu ipcom_ex2_dc_3200_firmware >= v01l02nf0001, <= v01l06nf0401 cpe:2.3:o:fujitsu:ipcom_ex2_dc_3200_firmware:*:*:*:*:*:*:*:*
fujitsu ipcom_ex2_dc_3200_firmware >= v01l20nf0001, <= v01l20nf0401 cpe:2.3:o:fujitsu:ipcom_ex2_dc_3200_firmware:*:*:*:*:*:*:*:*
fujitsu ipcom_ex2_dc_3200_firmware >= v02l20nf0001, <= v02l21nf0301 cpe:2.3:o:fujitsu:ipcom_ex2_dc_3200_firmware:*:*:*:*:*:*:*:*
fujitsu ipcom_ex2_dc_3500_firmware >= v01l02nf0001, <= v01l06nf0401 cpe:2.3:o:fujitsu:ipcom_ex2_dc_3500_firmware:*:*:*:*:*:*:*:*
fujitsu ipcom_ex2_dc_3500_firmware >= v01l20nf0001, <= v01l20nf0401 cpe:2.3:o:fujitsu:ipcom_ex2_dc_3500_firmware:*:*:*:*:*:*:*:*
fujitsu ipcom_ex2_dc_3500_firmware >= v02l20nf0001, <= v02l21nf0301 cpe:2.3:o:fujitsu:ipcom_ex2_dc_3500_firmware:*:*:*:*:*:*:*:*

References for CVE-2024-39921

URL Tags
https://jvn.jp/en/jp/JVN29238389/ Mitigation Third Party Advisory
https://www.fujitsu.com/jp/products/network/support/2024/ipcom-04/ Mitigation Vendor Advisory
cvelogic Threat Intelligence