CVE-2022-29516
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 · uneditedThe web console of FUJITSU Network IPCOM series (IPCOM EX2 IN(3200, 3500), IPCOM EX2 LB(1100, 3200, 3500), IPCOM EX2 SC(1100, 3200, 3500), IPCOM EX2 NW(1100, 3200, 3500), IPCOM EX2 DC, IPCOM EX2 DC, IPCOM EX IN(2300, 2500, 2700), IPCOM EX LB(1100, 1300, 2300, 2500, 2700), IPCOM EX SC(1100, 1300, 2300, 2500, 2700), and IPCOM EX NW(1100, 1300, 2300, 2500, 2700)) allows a remote attacker to execute an arbitrary OS command via unspecified vectors.
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 confidenceCommand injection vulnerability in the web console of Fujitsu IPCOM network appliances allowing remote attackers to execute arbitrary OS commands. This is a critical flaw that enables complete device compromise without authentication.
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< v01l05_nf0501< v01l05_nf0501< v01l05_nf0501< v01l05_nf0501< v01l05_nf0501< v01l05_nf0501< v01l05_nf0501< v01l05_nf0501CVSS 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
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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 checksWork through these to decide whether this CVE applies to you.
-
Identify the Fujitsu IPCOM device modelAccess the device web console or check the device label/serial number to confirm the exact model (e.g., Ipcom Ex2 Nw 1100, Sc 3500, Lb 3200)Affected if The device is a Fujitsu Ipcom Ex2 series model (Nw, Sc, or Lb variants)
-
Check the installed firmware versionLog into the device web interface or CLI and locate the firmware version information, typically found in System, Status, or About sectionsAffected if The firmware version is earlier than v01l05_nf0501 (for example, v01l04 or earlier)
-
Verify the web console is enabled and accessibleConfirm that the HTTP/HTTPS web management interface is enabled and reachable on the device networkAffected if The web console is exposed on the network (this is required for the command injection to be exploitable)
-
Confirm the device falls within affected version rangeCross-reference the identified model and firmware version against the affected product list provided in the CVEAffected if The device is a listed model (Nw 1100, Nw 3500, Nw 3200, Sc 1100, Sc 3500, Sc 3200, Lb 1100, Lb 3500) with firmware version less than v01l05_nf0501
You are affected if you have a Fujitsu Ipcom Ex2 series device (Nw, Sc, or Lb model) running firmware version earlier than v01l05_nf0501 with the web console enabled and accessible on your network.
Generated from the published advisory. Verify against your own configuration.
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 · scopedRestrict network access to management interfaces immediately. Contact Fujitsu for available firmware patches and apply them to all affected devices. If no patch available, consider network segmentation or device replacement.
v01l05_nf0501
- Identify the exact IPCOM EX2 model (NW, SC, or LB series) and current firmware version via the web console or administrative interface
- Navigate to Fujitsu support website (www.fujitsu.com) or the vendor's firmware download page
- Download firmware version v01l05_nf0501 or later for your specific model
- Backup the current device configuration through the web console
- Access the firmware upgrade section in the device administration interface
- Upload and apply the v01l05_nf0501 firmware file
- Verify the upgrade was successful by checking the new firmware version in the web console
- Restore the configuration if needed and verify normal operation
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $10,240.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-29516 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-29516 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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