IPCOM EX2 Series: Observable Discrepancy
CVE-2024-39921 is a high-severity observable discrepancy vulnerability in IPCOM EX2 Series from Fsas Technologies, with a CVSS 3.1 base score of 7.5 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. Affected IPCOM EX2 Series versions: V01L02NF0001 to V01L06NF0401; V01L20NF0001 to V01L20NF0401; V02L20NF0001 to V02L21NF0301. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 0.43% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Check which version of IPCOM EX2 Series you run against the affected versions below, and install the vendor's latest release.
- Read the advisory on fujitsu.com for workarounds and exact fixed builds.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Fsas Technologies | IPCOM EX2 Series | V01L02NF0001 to V01L06NF0401; V01L20NF0001 to V01L20NF0401; V02L20NF0001 to V02L21NF0301 | Not stated |
| Fsas Technologies | IPCOM VE2 Series | V01L04NF0001 to V01L06NF0112 | Not stated |
| Fujitsu | Ipcom Ve2 Ls 100 Firmware | v01l04nf0001 through v01l06nf0112 | Not stated |
| Fujitsu | Ipcom Ve2 Ls 200 Firmware | v01l04nf0001 through v01l06nf0112 | Not stated |
| Fujitsu | Ipcom Ve2 Ls 220 Firmware | v01l04nf0001 through v01l06nf0112 | Not stated |
| Fujitsu | Ipcom Ve2 Ls Plus 100 Firmware | v01l04nf0001 through v01l06nf0112 | Not stated |
| Fujitsu | Ipcom Ve2 Ls Plus 200 Firmware | v01l04nf0001 through v01l06nf0112 | Not stated |
| Fujitsu | Ipcom Ve2 Ls Plus 220 Firmware | v01l04nf0001 through v01l06nf0112 | Not stated |
| Fujitsu | Ipcom Ve2 Ls Plus2 200 Firmware | v01l04nf0001 through v01l06nf0112 | Not stated |
| Fujitsu | Ipcom Ve2 Ls Plus2 220 Firmware | v01l04nf0001 through v01l06nf0112 | Not stated |
| Fujitsu | Ipcom Ve2 Sc Plus 100 Firmware | v01l04nf0001 through v01l06nf0112 | Not stated |
| Fujitsu | Ipcom Ve2 Sc Plus 200 Firmware | v01l04nf0001 through v01l06nf0112 | Not stated |
| Fujitsu | Ipcom Ve2 Sc Plus 220 Firmware | v01l04nf0001 through v01l06nf0112 | Not stated |
| Fujitsu | Ipcom Ex2 In 3200 Firmware | v01l02nf0001 through v01l06nf0401; v01l20nf0001 through v01l20nf0401; v02l20nf0001 through v02l21nf0301 | Not stated |
| Fujitsu | Ipcom Ex2 In 3500 Firmware | v01l02nf0001 through v01l06nf0401; v01l20nf0001 through v01l20nf0401; v02l20nf0001 through v02l21nf0301 | Not stated |
| Fujitsu | Ipcom Ex2 Lb 3200 Firmware | v01l02nf0001 through v01l06nf0401; v01l20nf0001 through v01l20nf0401; v02l20nf0001 through v02l21nf0301 | Not stated |
| Fujitsu | Ipcom Ex2 Lb 3500 Firmware | v01l02nf0001 through v01l06nf0401; v01l20nf0001 through v01l20nf0401; v02l20nf0001 through v02l21nf0301 | Not stated |
| Fujitsu | Ipcom Ex2 Sc 3200 Firmware | v01l02nf0001 through v01l06nf0401; v01l20nf0001 through v01l20nf0401; v02l20nf0001 through v02l21nf0301 | Not stated |
| Fujitsu | Ipcom Ex2 Sc 3500 Firmware | v01l02nf0001 through v01l06nf0401; v01l20nf0001 through v01l20nf0401; v02l20nf0001 through v02l21nf0301 | Not stated |
| Fujitsu | Ipcom Ex2 Dc 3200 Firmware | v01l02nf0001 through v01l06nf0401; v01l20nf0001 through v01l20nf0401; v02l20nf0001 through v02l21nf0301 | Not stated |
| Fujitsu | Ipcom Ex2 Dc 3500 Firmware | v01l02nf0001 through v01l06nf0401; v01l20nf0001 through v01l20nf0401; v02l20nf0001 through v02l21nf0301 | Not stated |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- NoneNothing can be modified.
- Availability
- NoneAvailability is not affected.
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 7.5 | High | NVD |
| CVSS 3.1 | 7.5 | High | CISA (ADP) |
Official description
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.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Observable Discrepancy
The product behaves differently or sends different responses under different circumstances in a way that is observable to an unauthorized actor.
How developers prevent this class of flaw
- Compartmentalize the system to have safe areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area. Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: partial).
- Record last changed materially (score, affected products, status or references).
References
Advisories
Patches and release notes
- jvn.jp/en/jp/JVN29238389/Mitigation, Third Party Advisory
Recent Observable Discrepancy vulnerabilities
- 5.3 Medium severity
Twilio Authy Information Disclosure Exploited
- 7.5 High severity
- 7.5 High severity
- 7.5 High severity
- 8.2 High severity
- 7.5 High severity
Spotted an error? Tell us.