dbcve.org
Ipcom Ve2 Ls 100 FirmwareOperating system · Fujitsu

CVE-2024-39921

HIGH · 7.5 CVSS v3.1 Published 2024-09-04
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A timing side-channel vulnerability exists in the cryptographic implementation of IPCOM EX2 and VE2 Series routers. The observable timing discrepancy allows an attacker to potentially decrypt some encrypted communications by analyzing timing differences in cryptographic operations, likely during authentication or key derivation processes.

MitigationApply vendor-supplied firmware updates to all affected IPCOM EX2 and VE2 devices; until patched, avoid transmitting sensitive data over affected devices or use additional encryption layers (e.g., VPN).

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Ipcom Ve2 Ls 100 FirmwareOperating system
Affected:>= v01l04nf0001, <= v01l06nf0112
Ipcom Ve2 Ls 200 FirmwareOperating system
Affected:>= v01l04nf0001, <= v01l06nf0112
Ipcom Ve2 Ls 220 FirmwareOperating system
Affected:>= v01l04nf0001, <= v01l06nf0112
Ipcom Ve2 Ls Plus 100 FirmwareOperating system
Affected:>= v01l04nf0001, <= v01l06nf0112
Ipcom Ve2 Ls Plus 200 FirmwareOperating system
Affected:>= v01l04nf0001, <= v01l06nf0112
Ipcom Ve2 Ls Plus 220 FirmwareOperating system
Affected:>= v01l04nf0001, <= v01l06nf0112
Ipcom Ve2 Ls Plus2 200 FirmwareOperating system
Affected:>= v01l04nf0001, <= v01l06nf0112
Ipcom Ve2 Ls Plus2 220 FirmwareOperating system
Affected:>= v01l04nf0001, <= v01l06nf0112

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify device model
    Access the router admin interface or CLI and retrieve the exact model name (e.g., Ipcom Ve2 Ls 100, Ipcom Ve2 Ls Plus 200, etc.)
    Affected if The model is NOT one of: VE2 LS 100, VE2 LS 200, VE2 LS 220, VE2 LS Plus 100, VE2 LS Plus 200, VE2 LS Plus 220, VE2 LS Plus2 200, or VE2 LS Plus2 220
  2. Retrieve firmware version
    Access the router admin interface or CLI and locate the firmware version information (typically under System Status, Firmware Info, or similar menu)
    Affected if Unable to retrieve firmware version information from the device
  3. Compare firmware version against affected range
    Compare the installed firmware version string to the affected range: v01l04nf0001 through v01l06nf0112 inclusive
    Affected if The installed version falls within >= v01l04nf0001 AND <= v01l06nf0112 (the device is vulnerable)
  4. Verify timing-sensitive crypto operations are in use
    The vulnerability affects timing differences in cryptographic operations during authentication or key derivation - confirm the device handles authenticated VPN connections, remote access, or other crypto-dependent services
    Affected if The device processes any authenticated or encrypted network traffic (this condition is true for most deployments)

A user is affected if they own a Fujitsu Ipcom VE2 series router (any of the 8 listed models) AND the installed firmware version is between v01l04nf0001 and v01l06nf0112 inclusive, AND the device handles encrypted or authenticated communications.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor-supplied firmware updates to all affected IPCOM EX2 and VE2 devices; until patched, avoid transmitting sensitive data over affected devices or use additional encryption layers (e.g., VPN).

Recommended fix Moderate confidence

V01L06NF0401 or later (any version beyond V01L06NF0112)

  1. 1. Identify the current firmware version of the IPCOM VE2 device by accessing the administrative web interface or checking system information.
  2. 2. Navigate to the firmware update section in the device management interface.
  3. 3. Download the latest firmware version from the official Fujitsu support website (www.fujitsu.com).
  4. 4. Before upgrading, backup the current device configuration to ensure settings can be restored if needed.
  5. 5. Initiate the firmware upgrade process, ensuring stable power supply throughout the update.
  6. 6. After upgrade completes, verify the new firmware version displays as V01L06NF0401 or later.
  7. 7. Confirm that the vulnerability is resolved by checking the firmware release notes for CVE-2024-39921 addressing.
  8. 8. Restore the backed-up configuration if necessary and test normal device operation.
Caveat Review release notes for any configuration changes or feature modifications between your current version and the target version

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Ipcom Ve2 Ls 100 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-39921 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-39921 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data