CVE-2022-29516 Vulnerability Analysis & Exploit Details

CVE-2022-29516
Vulnerability Scoring

9.8
/10
Critical Risk

As a catastrophic security flaw, CVE-2022-29516 has severe implications, demanding immediate intervention.

Attack Complexity Details

  • Attack Complexity: Low
    Exploits can be performed without significant complexity or special conditions.
  • Attack Vector: Network
    Vulnerability is exploitable over a network without physical access.
  • Privileges Required: None
    No privileges are required for exploitation.
  • Scope: Unchanged
    Exploit remains within the originally vulnerable component.
  • User Interaction: None
    No user interaction is necessary for exploitation.

CVE-2022-29516 Details

Status: Modified

Last updated: 🕡 21 Nov 2024, 06:59 UTC
Originally published on: 🕒 18 May 2022, 15:15 UTC

Time between publication and last update: 917 days

CVSS Release: version 3

CVSS3 Source

nvd@nist.gov

CVSS3 Type

Primary

CVSS3 Vector

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

CVE-2022-29516 Vulnerability Summary

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), 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.

Assessing the Risk of CVE-2022-29516

Access Complexity Graph

The exploitability of CVE-2022-29516 depends on two key factors: attack complexity (the level of effort required to execute an exploit) and privileges required (the access level an attacker needs).

Exploitability Analysis for CVE-2022-29516

With low attack complexity and no required privileges, CVE-2022-29516 is an easy target for cybercriminals. Organizations should prioritize immediate mitigation measures to prevent unauthorized access and data breaches.

Understanding AC and PR

A lower complexity and fewer privilege requirements make exploitation easier. Security teams should evaluate these aspects to determine the urgency of mitigation strategies, such as patch management and access control policies.

Attack Complexity (AC) measures the difficulty in executing an exploit. A high AC means that specific conditions must be met, making an attack more challenging, while a low AC means the vulnerability can be exploited with minimal effort.

Privileges Required (PR) determine the level of system access necessary for an attack. Vulnerabilities requiring no privileges are more accessible to attackers, whereas high privilege requirements limit exploitation to authorized users with elevated access.

CVSS Score Breakdown Chart

Above is the CVSS Sub-score Breakdown for CVE-2022-29516, illustrating how Base, Impact, and Exploitability factors combine to form the overall severity rating. A higher sub-score typically indicates a more severe or easier-to-exploit vulnerability.

CIA Impact Analysis

Below is the Impact Analysis for CVE-2022-29516, showing how Confidentiality, Integrity, and Availability might be affected if the vulnerability is exploited. Higher values usually signal greater potential damage.

  • Confidentiality: High
    Exploiting CVE-2022-29516 can result in unauthorized access to sensitive data, severely compromising data privacy.
  • Integrity: High
    CVE-2022-29516 could allow unauthorized modifications to data, potentially affecting system reliability and trust.
  • Availability: High
    CVE-2022-29516 can disrupt system operations, potentially causing complete denial of service (DoS).

Exploit Prediction Scoring System (EPSS)

The EPSS score estimates the probability that this vulnerability will be exploited in the near future.

EPSS Score: 0.338% (probability of exploit)

EPSS Percentile: 71.55% (lower percentile = lower relative risk)
This vulnerability is less risky than approximately 28.450000000000003% of others.

CVE-2022-29516 References

External References

CWE Common Weakness Enumeration

CWE-78

CAPEC Common Attack Pattern Enumeration and Classification

  • Command Line Execution through SQL Injection CAPEC-108 An attacker uses standard SQL injection methods to inject data into the command line for execution. This could be done directly through misuse of directives such as MSSQL_xp_cmdshell or indirectly through injection of data into the database that would be interpreted as shell commands. Sometime later, an unscrupulous backend application (or could be part of the functionality of the same application) fetches the injected data stored in the database and uses this data as command line arguments without performing proper validation. The malicious data escapes that data plane by spawning new commands to be executed on the host.
  • Command Delimiters CAPEC-15 An attack of this type exploits a programs' vulnerabilities that allows an attacker's commands to be concatenated onto a legitimate command with the intent of targeting other resources such as the file system or database. The system that uses a filter or denylist input validation, as opposed to allowlist validation is vulnerable to an attacker who predicts delimiters (or combinations of delimiters) not present in the filter or denylist. As with other injection attacks, the attacker uses the command delimiter payload as an entry point to tunnel through the application and activate additional attacks through SQL queries, shell commands, network scanning, and so on.
  • Exploiting Multiple Input Interpretation Layers CAPEC-43 An attacker supplies the target software with input data that contains sequences of special characters designed to bypass input validation logic. This exploit relies on the target making multiples passes over the input data and processing a "layer" of special characters with each pass. In this manner, the attacker can disguise input that would otherwise be rejected as invalid by concealing it with layers of special/escape characters that are stripped off by subsequent processing steps. The goal is to first discover cases where the input validation layer executes before one or more parsing layers. That is, user input may go through the following logic in an application: <parser1> --> <input validator> --> <parser2>. In such cases, the attacker will need to provide input that will pass through the input validator, but after passing through parser2, will be converted into something that the input validator was supposed to stop.
  • Argument Injection CAPEC-6 An attacker changes the behavior or state of a targeted application through injecting data or command syntax through the targets use of non-validated and non-filtered arguments of exposed services or methods.
  • OS Command Injection CAPEC-88 In this type of an attack, an adversary injects operating system commands into existing application functions. An application that uses untrusted input to build command strings is vulnerable. An adversary can leverage OS command injection in an application to elevate privileges, execute arbitrary commands and compromise the underlying operating system.

Vulnerable Configurations

  • cpe:2.3:o:fujitsu:ipcom_ex2_nw_1100_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:fujitsu:ipcom_ex2_nw_1100_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:fujitsu:ipcom_ex2_nw_1100:-:*:*:*:*:*:*:*
    cpe:2.3:h:fujitsu:ipcom_ex2_nw_1100:-:*:*:*:*:*:*:*
  • cpe:2.3:o:fujitsu:ipcom_ex2_nw_3500_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:fujitsu:ipcom_ex2_nw_3500_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:fujitsu:ipcom_ex2_nw_3500:-:*:*:*:*:*:*:*
    cpe:2.3:h:fujitsu:ipcom_ex2_nw_3500:-:*:*:*:*:*:*:*
  • cpe:2.3:o:fujitsu:ipcom_ex2_nw_3200_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:fujitsu:ipcom_ex2_nw_3200_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:fujitsu:ipcom_ex2_nw_3200:-:*:*:*:*:*:*:*
    cpe:2.3:h:fujitsu:ipcom_ex2_nw_3200:-:*:*:*:*:*:*:*
  • cpe:2.3:o:fujitsu:ipcom_ex2_sc_1100_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:fujitsu:ipcom_ex2_sc_1100_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:fujitsu:ipcom_ex2_sc_1100:-:*:*:*:*:*:*:*
    cpe:2.3:h:fujitsu:ipcom_ex2_sc_1100:-:*:*:*:*:*:*:*
  • cpe:2.3:o:fujitsu:ipcom_ex2_sc_3500_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:fujitsu:ipcom_ex2_sc_3500_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:fujitsu:ipcom_ex2_sc_3500:-:*:*:*:*:*:*:*
    cpe:2.3:h:fujitsu:ipcom_ex2_sc_3500:-:*:*:*:*:*:*:*
  • cpe:2.3:o:fujitsu:ipcom_ex2_sc_3200_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:fujitsu:ipcom_ex2_sc_3200_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:fujitsu:ipcom_ex2_sc_3200:-:*:*:*:*:*:*:*
    cpe:2.3:h:fujitsu:ipcom_ex2_sc_3200:-:*:*:*:*:*:*:*
  • cpe:2.3:o:fujitsu:ipcom_ex2_lb_1100_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:fujitsu:ipcom_ex2_lb_1100_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:fujitsu:ipcom_ex2_lb_1100:-:*:*:*:*:*:*:*
    cpe:2.3:h:fujitsu:ipcom_ex2_lb_1100:-:*:*:*:*:*:*:*
  • cpe:2.3:o:fujitsu:ipcom_ex2_lb_3500_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:fujitsu:ipcom_ex2_lb_3500_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:fujitsu:ipcom_ex2_lb_3500:-:*:*:*:*:*:*:*
    cpe:2.3:h:fujitsu:ipcom_ex2_lb_3500:-:*:*:*:*:*:*:*
  • cpe:2.3:o:fujitsu:ipcom_ex2_lb_3200_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:fujitsu:ipcom_ex2_lb_3200_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:fujitsu:ipcom_ex2_lb_3200:-:*:*:*:*:*:*:*
    cpe:2.3:h:fujitsu:ipcom_ex2_lb_3200:-:*:*:*:*:*:*:*
  • cpe:2.3:o:fujitsu:ipcom_ex2_in_1100_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:fujitsu:ipcom_ex2_in_1100_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:fujitsu:ipcom_ex2_in_1100:-:*:*:*:*:*:*:*
    cpe:2.3:h:fujitsu:ipcom_ex2_in_1100:-:*:*:*:*:*:*:*
  • cpe:2.3:o:fujitsu:ipcom_ex2_in_3200_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:fujitsu:ipcom_ex2_in_3200_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:fujitsu:ipcom_ex2_in_3200:-:*:*:*:*:*:*:*
    cpe:2.3:h:fujitsu:ipcom_ex2_in_3200:-:*:*:*:*:*:*:*
  • cpe:2.3:o:fujitsu:ipcom_ex2_in_3500_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:fujitsu:ipcom_ex2_in_3500_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:fujitsu:ipcom_ex2_in_3500:-:*:*:*:*:*:*:*
    cpe:2.3:h:fujitsu:ipcom_ex2_in_3500:-:*:*:*:*:*:*:*
  • cpe:2.3:o:fujitsu:ipcom_ex2_dc_3500_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:fujitsu:ipcom_ex2_dc_3500_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:fujitsu:ipcom_ex2_dc_3500:-:*:*:*:*:*:*:*
    cpe:2.3:h:fujitsu:ipcom_ex2_dc_3500:-:*:*:*:*:*:*:*
  • cpe:2.3:o:fujitsu:ipcom_ex2_dc_3200_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:fujitsu:ipcom_ex2_dc_3200_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:fujitsu:ipcom_ex2_dc_3200:-:*:*:*:*:*:*:*
    cpe:2.3:h:fujitsu:ipcom_ex2_dc_3200:-:*:*:*:*:*:*:*
  • cpe:2.3:o:fujitsu:ipcom_ex_in_2300_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:fujitsu:ipcom_ex_in_2300_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:fujitsu:ipcom_ex_in_2300:-:*:*:*:*:*:*:*
    cpe:2.3:h:fujitsu:ipcom_ex_in_2300:-:*:*:*:*:*:*:*
  • cpe:2.3:o:fujitsu:ipcom_ex_in_2500_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:fujitsu:ipcom_ex_in_2500_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:fujitsu:ipcom_ex_in_2500:-:*:*:*:*:*:*:*
    cpe:2.3:h:fujitsu:ipcom_ex_in_2500:-:*:*:*:*:*:*:*
  • cpe:2.3:o:fujitsu:ipcom_ex_in_2700_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:fujitsu:ipcom_ex_in_2700_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:fujitsu:ipcom_ex_in_2700:-:*:*:*:*:*:*:*
    cpe:2.3:h:fujitsu:ipcom_ex_in_2700:-:*:*:*:*:*:*:*
  • cpe:2.3:o:fujitsu:ipcom_ex_lb_1100_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:fujitsu:ipcom_ex_lb_1100_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:fujitsu:ipcom_ex_lb_1100:-:*:*:*:*:*:*:*
    cpe:2.3:h:fujitsu:ipcom_ex_lb_1100:-:*:*:*:*:*:*:*
  • cpe:2.3:o:fujitsu:ipcom_ex_lb_1300_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:fujitsu:ipcom_ex_lb_1300_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:fujitsu:ipcom_ex_lb_1300:-:*:*:*:*:*:*:*
    cpe:2.3:h:fujitsu:ipcom_ex_lb_1300:-:*:*:*:*:*:*:*
  • cpe:2.3:o:fujitsu:ipcom_ex_lb_2300_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:fujitsu:ipcom_ex_lb_2300_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:fujitsu:ipcom_ex_lb_2300:-:*:*:*:*:*:*:*
    cpe:2.3:h:fujitsu:ipcom_ex_lb_2300:-:*:*:*:*:*:*:*
  • cpe:2.3:o:fujitsu:ipcom_ex_lb_2500_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:fujitsu:ipcom_ex_lb_2500_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:fujitsu:ipcom_ex_lb_2500:-:*:*:*:*:*:*:*
    cpe:2.3:h:fujitsu:ipcom_ex_lb_2500:-:*:*:*:*:*:*:*
  • cpe:2.3:o:fujitsu:ipcom_ex_lb_2700_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:fujitsu:ipcom_ex_lb_2700_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:fujitsu:ipcom_ex_lb_2700:-:*:*:*:*:*:*:*
    cpe:2.3:h:fujitsu:ipcom_ex_lb_2700:-:*:*:*:*:*:*:*
  • cpe:2.3:o:fujitsu:ipcom_ex_sc_1100_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:fujitsu:ipcom_ex_sc_1100_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:fujitsu:ipcom_ex_sc_1100:-:*:*:*:*:*:*:*
    cpe:2.3:h:fujitsu:ipcom_ex_sc_1100:-:*:*:*:*:*:*:*
  • cpe:2.3:o:fujitsu:ipcom_ex_sc_1300_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:fujitsu:ipcom_ex_sc_1300_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:fujitsu:ipcom_ex_sc_1300:-:*:*:*:*:*:*:*
    cpe:2.3:h:fujitsu:ipcom_ex_sc_1300:-:*:*:*:*:*:*:*
  • cpe:2.3:o:fujitsu:ipcom_ex_sc_2300_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:fujitsu:ipcom_ex_sc_2300_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:fujitsu:ipcom_ex_sc_2300:-:*:*:*:*:*:*:*
    cpe:2.3:h:fujitsu:ipcom_ex_sc_2300:-:*:*:*:*:*:*:*
  • cpe:2.3:o:fujitsu:ipcom_ex_sc_2500_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:fujitsu:ipcom_ex_sc_2500_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:fujitsu:ipcom_ex_sc_2500:-:*:*:*:*:*:*:*
    cpe:2.3:h:fujitsu:ipcom_ex_sc_2500:-:*:*:*:*:*:*:*
  • cpe:2.3:o:fujitsu:ipcom_ex_sc_2700_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:fujitsu:ipcom_ex_sc_2700_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:fujitsu:ipcom_ex_sc_2700:-:*:*:*:*:*:*:*
    cpe:2.3:h:fujitsu:ipcom_ex_sc_2700:-:*:*:*:*:*:*:*
  • cpe:2.3:o:fujitsu:ipcom_ex_nw_1100_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:fujitsu:ipcom_ex_nw_1100_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:fujitsu:ipcom_ex_nw_1100:-:*:*:*:*:*:*:*
    cpe:2.3:h:fujitsu:ipcom_ex_nw_1100:-:*:*:*:*:*:*:*
  • cpe:2.3:o:fujitsu:ipcom_ex_nw_1300_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:fujitsu:ipcom_ex_nw_1300_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:fujitsu:ipcom_ex_nw_1300:-:*:*:*:*:*:*:*
    cpe:2.3:h:fujitsu:ipcom_ex_nw_1300:-:*:*:*:*:*:*:*
  • cpe:2.3:o:fujitsu:ipcom_ex_nw_2300_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:fujitsu:ipcom_ex_nw_2300_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:fujitsu:ipcom_ex_nw_2300:-:*:*:*:*:*:*:*
    cpe:2.3:h:fujitsu:ipcom_ex_nw_2300:-:*:*:*:*:*:*:*
  • cpe:2.3:o:fujitsu:ipcom_ex_nw_2500_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:fujitsu:ipcom_ex_nw_2500_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:fujitsu:ipcom_ex_nw_2500:-:*:*:*:*:*:*:*
    cpe:2.3:h:fujitsu:ipcom_ex_nw_2500:-:*:*:*:*:*:*:*
  • cpe:2.3:o:fujitsu:ipcom_ex_nw_2700_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:fujitsu:ipcom_ex_nw_2700_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:fujitsu:ipcom_ex_nw_2700:-:*:*:*:*:*:*:*
    cpe:2.3:h:fujitsu:ipcom_ex_nw_2700:-:*:*:*:*:*:*:*
  • cpe:2.3:o:fujitsu:ipcom_ve2_ls_100_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:fujitsu:ipcom_ve2_ls_100_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:fujitsu:ipcom_ve2_ls_100:-:*:*:*:*:*:*:*
    cpe:2.3:h:fujitsu:ipcom_ve2_ls_100:-:*:*:*:*:*:*:*
  • cpe:2.3:o:fujitsu:ipcom_ve2_ls_200_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:fujitsu:ipcom_ve2_ls_200_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:fujitsu:ipcom_ve2_ls_200:-:*:*:*:*:*:*:*
    cpe:2.3:h:fujitsu:ipcom_ve2_ls_200:-:*:*:*:*:*:*:*
  • cpe:2.3:o:fujitsu:ipcom_ve2_ls_220_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:fujitsu:ipcom_ve2_ls_220_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:fujitsu:ipcom_ve2_ls_220:-:*:*:*:*:*:*:*
    cpe:2.3:h:fujitsu:ipcom_ve2_ls_220:-:*:*:*:*:*:*:*
  • cpe:2.3:o:fujitsu:ipcom_ve2_ls_plus_100_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:fujitsu:ipcom_ve2_ls_plus_100_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:fujitsu:ipcom_ve2_ls_plus_100:-:*:*:*:*:*:*:*
    cpe:2.3:h:fujitsu:ipcom_ve2_ls_plus_100:-:*:*:*:*:*:*:*
  • cpe:2.3:o:fujitsu:ipcom_ve2_ls_plus_200_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:fujitsu:ipcom_ve2_ls_plus_200_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:fujitsu:ipcom_ve2_ls_plus_200:-:*:*:*:*:*:*:*
    cpe:2.3:h:fujitsu:ipcom_ve2_ls_plus_200:-:*:*:*:*:*:*:*
  • cpe:2.3:o:fujitsu:ipcom_ve2_ls_plus_220_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:fujitsu:ipcom_ve2_ls_plus_220_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:fujitsu:ipcom_ve2_ls_plus_220:-:*:*:*:*:*:*:*
    cpe:2.3:h:fujitsu:ipcom_ve2_ls_plus_220:-:*:*:*:*:*:*:*
  • cpe:2.3:o:fujitsu:ipcom_ve2_ls_plus2_200_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:fujitsu:ipcom_ve2_ls_plus2_200_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:fujitsu:ipcom_ve2_ls_plus2_200:-:*:*:*:*:*:*:*
    cpe:2.3:h:fujitsu:ipcom_ve2_ls_plus2_200:-:*:*:*:*:*:*:*
  • cpe:2.3:o:fujitsu:ipcom_ve2_ls_plus2_220_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:fujitsu:ipcom_ve2_ls_plus2_220_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:fujitsu:ipcom_ve2_ls_plus2_220:-:*:*:*:*:*:*:*
    cpe:2.3:h:fujitsu:ipcom_ve2_ls_plus2_220:-:*:*:*:*:*:*:*
  • cpe:2.3:o:fujitsu:ipcom_ve2_sc_100_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:fujitsu:ipcom_ve2_sc_100_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:fujitsu:ipcom_ve2_sc_100:-:*:*:*:*:*:*:*
    cpe:2.3:h:fujitsu:ipcom_ve2_sc_100:-:*:*:*:*:*:*:*
  • cpe:2.3:o:fujitsu:ipcom_ve2_sc_200_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:fujitsu:ipcom_ve2_sc_200_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:fujitsu:ipcom_ve2_sc_200:-:*:*:*:*:*:*:*
    cpe:2.3:h:fujitsu:ipcom_ve2_sc_200:-:*:*:*:*:*:*:*
  • cpe:2.3:o:fujitsu:ipcom_ve2_sc_220_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:fujitsu:ipcom_ve2_sc_220_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:fujitsu:ipcom_ve2_sc_220:-:*:*:*:*:*:*:*
    cpe:2.3:h:fujitsu:ipcom_ve2_sc_220:-:*:*:*:*:*:*:*
  • cpe:2.3:o:fujitsu:ipcom_ve2_sc_plus_100_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:fujitsu:ipcom_ve2_sc_plus_100_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:fujitsu:ipcom_ve2_sc_plus_100:-:*:*:*:*:*:*:*
    cpe:2.3:h:fujitsu:ipcom_ve2_sc_plus_100:-:*:*:*:*:*:*:*
  • cpe:2.3:o:fujitsu:ipcom_ve2_sc_plus_200_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:fujitsu:ipcom_ve2_sc_plus_200_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:fujitsu:ipcom_ve2_sc_plus_200:-:*:*:*:*:*:*:*
    cpe:2.3:h:fujitsu:ipcom_ve2_sc_plus_200:-:*:*:*:*:*:*:*
  • cpe:2.3:o:fujitsu:ipcom_ve2_sc_plus_220_firmware:-:*:*:*:*:*:*:*
    cpe:2.3:o:fujitsu:ipcom_ve2_sc_plus_220_firmware:-:*:*:*:*:*:*:*
  • cpe:2.3:h:fujitsu:ipcom_ve2_sc_plus_220:-:*:*:*:*:*:*:*
    cpe:2.3:h:fujitsu:ipcom_ve2_sc_plus_220:-:*:*:*:*:*:*:*

Protect Your Infrastructure against CVE-2022-29516: Combat Critical CVE Threats

Stay updated with real-time CVE vulnerabilities and take action to secure your systems. Enhance your cybersecurity posture with the latest threat intelligence and mitigation techniques. Develop the skills necessary to defend against CVEs and secure critical infrastructures. Join the top cybersecurity professionals safeguarding today's infrastructures.

Other 5 Recently Published CVEs Vulnerabilities

  • CVE-2025-26205 – Lua 5.4.7, when the debug library is used, has a out-of-bounds read and segmentation violation in mainpositionTV in ltable.c. NOTE: this is dispute...
  • CVE-2025-26204 – Lua 5.4.7, when the debug library is used, has a out-of-bounds read and segmentation violation in equalkey in ltable.c. NOTE: this is disputed beca...
  • CVE-2025-2129 – A vulnerability was found in Mage AI 0.9.75. It has been classified as problematic. This affects an unknown part. The manipulation leads to insecur...
  • CVE-2025-2127 – A vulnerability was found in JoomlaUX JUX Real Estate 3.4.0 on Joomla. It has been classified as problematic. Affected is an unknown function of th...
  • CVE-2025-2126 – A vulnerability was found in JoomlaUX JUX Real Estate 3.4.0 on Joomla and classified as critical. This issue affects some unknown processing of the...