NVD / CVE Program· CNA jpcert

CVE-2022-29516: The web console of FUJITSU Network IPCOM series (IPCOM EX2 IN(3200, 3500), IPCOM EX2 LB(1100, 3200, 3500), IPCOM EX2 SC(1100, 3200, 3500), I

Noroxi assessment

Priority: Plan (action score 40/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 2.1% (FIRST EPSS); higher than 82.4% of all records.
Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
According to the record, no fixed version is available yet.

Add it to your regular patch cycle. Update when a fix is released; follow the vendor's advisory.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

The 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.

CriticalCVSS 9.8 · v3.1—No exploit No fix recorded

Published: May 18, 2022
Updated: Jun 17, 2026
EPSS: 2.1% · 82th percentile
CWE: CWE-78

Report tools

JSON

Action score

Plan

Add it to your regular patch cycle.

CVSS: 39 / 40 · 9.8 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 1 / 30 · 2.1%

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
No fixed version yet

If any of these changes, we'll tell you in the daily email digest.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
fujitsu	ipcom ex2 nw 1100 firmware	cpe:2.3:o:fujitsu:ipcom_ex2_nw_1100_firmware
fujitsu	ipcom ex2 nw 1100	cpe:2.3:h:fujitsu:ipcom_ex2_nw_1100
fujitsu	ipcom ex2 nw 3500 firmware	cpe:2.3:o:fujitsu:ipcom_ex2_nw_3500_firmware
fujitsu	ipcom ex2 nw 3500	cpe:2.3:h:fujitsu:ipcom_ex2_nw_3500
fujitsu	ipcom ex2 nw 3200 firmware	cpe:2.3:o:fujitsu:ipcom_ex2_nw_3200_firmware
fujitsu	ipcom ex2 nw 3200	cpe:2.3:h:fujitsu:ipcom_ex2_nw_3200
fujitsu	ipcom ex2 sc 1100 firmware	cpe:2.3:o:fujitsu:ipcom_ex2_sc_1100_firmware
fujitsu	ipcom ex2 sc 1100	cpe:2.3:h:fujitsu:ipcom_ex2_sc_1100
fujitsu	ipcom ex2 sc 3500 firmware	cpe:2.3:o:fujitsu:ipcom_ex2_sc_3500_firmware
fujitsu	ipcom ex2 sc 3500	cpe:2.3:h:fujitsu:ipcom_ex2_sc_3500
fujitsu	ipcom ex2 sc 3200 firmware	cpe:2.3:o:fujitsu:ipcom_ex2_sc_3200_firmware
fujitsu	ipcom ex2 sc 3200	cpe:2.3:h:fujitsu:ipcom_ex2_sc_3200

and 80 more

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

fujitsu ipcom ex in 2300 firmwarebefore e20l33_nf1101
fujitsu ipcom ex in 2500 firmwarebefore e20l33_nf1101
fujitsu ipcom ex in 2700 firmwarebefore e20l33_nf1101
fujitsu ipcom ex lb 1100 firmwarebefore e20l33_nf1101
fujitsu ipcom ex lb 1300 firmwarebefore e20l33_nf1101
fujitsu ipcom ex lb 2300 firmwarebefore e20l33_nf1101
fujitsu ipcom ex lb 2500 firmwarebefore e20l33_nf1101
fujitsu ipcom ex lb 2700 firmwarebefore e20l33_nf1101
fujitsu ipcom ex nw 1100 firmwarebefore e20l33_nf1101
fujitsu ipcom ex nw 1300 firmwarebefore e20l33_nf1101
fujitsu ipcom ex nw 2300 firmwarebefore e20l33_nf1101
fujitsu ipcom ex nw 2500 firmwarebefore e20l33_nf1101
fujitsu ipcom ex nw 2700 firmwarebefore e20l33_nf1101
fujitsu ipcom ex sc 1100 firmwarebefore e20l33_nf1101
fujitsu ipcom ex sc 1300 firmwarebefore e20l33_nf1101
fujitsu ipcom ex sc 2300 firmwarebefore e20l33_nf1101
fujitsu ipcom ex sc 2500 firmwarebefore e20l33_nf1101
fujitsu ipcom ex sc 2700 firmwarebefore e20l33_nf1101
fujitsu ipcom ex2 dc 3200 firmwarebefore v02l21_nf0201
fujitsu ipcom ex2 dc 3500 firmwarebefore v02l21_nf0201

Versions reported by the vendor

Affected version ranges reported by the assigning authority (jpcert). Independent of NVD's CPE analysis and usually ahead of it.

FUJITSU LIMITED IPCOM EX2 series, IPCOM EX series, IPCOM VE2 series, and IPCOM VA2/VE1 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, 1affected

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

No fix version is recorded for this entry. Check the references for vendor advisories.

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

Anyone who can reach it over the internet can trigger it.
No account or password is required.
No user action is required.
No special conditions are required; it is repeatable.

If successful

Confidentiality: high · data can be read
Integrity: high · data or configuration can be modified
Availability: high · the service can be disrupted

Attack vector: Network
Attack complexity: Low
Privileges required: None
User interaction: None
Scope: Unchanged
Confidentiality impact: High
Integrity impact: High
Availability impact: High

Weakness class (CWE)

CWE-78 · Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')

CVSS vector

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

nvd-primary

Root cause

User input is inserted as text into a shell command. The shell may interpret special characters in the input as part of the command.

The bug in code

The whole CWE-78 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

1const host = req.body.host;
2exec("ping -c 1 " + host, onResult);

Fixed

1const host = req.body.host;
2if (!/^[a-z0-9.-]{1,253}$/i.test(host)) return res.sendStatus(400);
3execFile("ping", ["-c", "1", host], onResult);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Attack patterns (CAPEC)

ATT&CK techniques

—

Change log

No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.

References

jvn.jp/en/jp/JVN96561229/index.html

Show all references (1 more)

www.fujitsu.com/jp/products/network/support/2022/ipcom-01/

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records