CVE-2022-21721 Vulnerability Analysis & Exploit Details

CVE-2022-21721
Vulnerability Scoring

5.9
/10
Significant Risk

Security assessments indicate that CVE-2022-21721 presents a notable risk, potentially requiring prompt mitigation.

Attack Complexity Details

  • Attack Complexity: High
    Exploits require significant effort and 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-21721 Details

Status: Modified

Last updated: 🕡 21 Nov 2024, 06:45 UTC
Originally published on: 🕙 28 Jan 2022, 22:15 UTC

Time between publication and last update: 1027 days

CVSS Release: version 3

CVSS3 Source

security-advisories@github.com

CVSS3 Type

Secondary

CVSS3 Vector

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

CVE-2022-21721 Vulnerability Summary

CVE-2022-21721: Next.js is a React framework. Starting with version 12.0.0 and prior to version 12.0.9, vulnerable code could allow a bad actor to trigger a denial of service attack for anyone using i18n functionality. In order to be affected by this CVE, one must use next start or a custom server and the built-in i18n support. Deployments on Vercel, along with similar environments where invalid requests are filtered before reaching Next.js, are not affected. A patch has been released, `next@12.0.9`, that mitigates this issue. As a workaround, one may ensure `/${locale}/_next/` is blocked from reaching the Next.js instance until it becomes feasible to upgrade.

Assessing the Risk of CVE-2022-21721

Access Complexity Graph

The exploitability of CVE-2022-21721 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-21721

CVE-2022-21721 presents a challenge to exploit due to its high attack complexity, but the absence of privilege requirements still makes it a viable target for skilled attackers. A thorough security review is advised.

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-21721, 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-21721, showing how Confidentiality, Integrity, and Availability might be affected if the vulnerability is exploited. Higher values usually signal greater potential damage.

  • Confidentiality: None
    CVE-2022-21721 has no significant impact on data confidentiality.
  • Integrity: None
    CVE-2022-21721 poses no threat to data integrity.
  • Availability: High
    CVE-2022-21721 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.171% (probability of exploit)

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

CVE-2022-21721 References

External References

CWE Common Weakness Enumeration

NVD-CWE-noinfo

Vulnerable Configurations

  • cpe:2.3:a:vercel:next.js:12.0.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:vercel:next.js:12.0.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:vercel:next.js:12.0.1:-:*:*:*:node.js:*:*
    cpe:2.3:a:vercel:next.js:12.0.1:-:*:*:*:node.js:*:*
  • cpe:2.3:a:vercel:next.js:12.0.1:canary0:*:*:*:node.js:*:*
    cpe:2.3:a:vercel:next.js:12.0.1:canary0:*:*:*:node.js:*:*
  • cpe:2.3:a:vercel:next.js:12.0.1:canary1:*:*:*:node.js:*:*
    cpe:2.3:a:vercel:next.js:12.0.1:canary1:*:*:*:node.js:*:*
  • cpe:2.3:a:vercel:next.js:12.0.1:canary2:*:*:*:node.js:*:*
    cpe:2.3:a:vercel:next.js:12.0.1:canary2:*:*:*:node.js:*:*
  • cpe:2.3:a:vercel:next.js:12.0.1:canary3:*:*:*:node.js:*:*
    cpe:2.3:a:vercel:next.js:12.0.1:canary3:*:*:*:node.js:*:*
  • cpe:2.3:a:vercel:next.js:12.0.1:canary4:*:*:*:node.js:*:*
    cpe:2.3:a:vercel:next.js:12.0.1:canary4:*:*:*:node.js:*:*
  • cpe:2.3:a:vercel:next.js:12.0.1:canary5:*:*:*:node.js:*:*
    cpe:2.3:a:vercel:next.js:12.0.1:canary5:*:*:*:node.js:*:*
  • cpe:2.3:a:vercel:next.js:12.0.2:-:*:*:*:node.js:*:*
    cpe:2.3:a:vercel:next.js:12.0.2:-:*:*:*:node.js:*:*
  • cpe:2.3:a:vercel:next.js:12.0.2:canary0:*:*:*:node.js:*:*
    cpe:2.3:a:vercel:next.js:12.0.2:canary0:*:*:*:node.js:*:*
  • cpe:2.3:a:vercel:next.js:12.0.2:canary1:*:*:*:node.js:*:*
    cpe:2.3:a:vercel:next.js:12.0.2:canary1:*:*:*:node.js:*:*
  • cpe:2.3:a:vercel:next.js:12.0.2:canary10:*:*:*:node.js:*:*
    cpe:2.3:a:vercel:next.js:12.0.2:canary10:*:*:*:node.js:*:*
  • cpe:2.3:a:vercel:next.js:12.0.2:canary11:*:*:*:node.js:*:*
    cpe:2.3:a:vercel:next.js:12.0.2:canary11:*:*:*:node.js:*:*
  • cpe:2.3:a:vercel:next.js:12.0.2:canary12:*:*:*:node.js:*:*
    cpe:2.3:a:vercel:next.js:12.0.2:canary12:*:*:*:node.js:*:*
  • cpe:2.3:a:vercel:next.js:12.0.2:canary13:*:*:*:node.js:*:*
    cpe:2.3:a:vercel:next.js:12.0.2:canary13:*:*:*:node.js:*:*
  • cpe:2.3:a:vercel:next.js:12.0.2:canary14:*:*:*:node.js:*:*
    cpe:2.3:a:vercel:next.js:12.0.2:canary14:*:*:*:node.js:*:*
  • cpe:2.3:a:vercel:next.js:12.0.2:canary2:*:*:*:node.js:*:*
    cpe:2.3:a:vercel:next.js:12.0.2:canary2:*:*:*:node.js:*:*
  • cpe:2.3:a:vercel:next.js:12.0.2:canary3:*:*:*:node.js:*:*
    cpe:2.3:a:vercel:next.js:12.0.2:canary3:*:*:*:node.js:*:*
  • cpe:2.3:a:vercel:next.js:12.0.2:canary4:*:*:*:node.js:*:*
    cpe:2.3:a:vercel:next.js:12.0.2:canary4:*:*:*:node.js:*:*
  • cpe:2.3:a:vercel:next.js:12.0.2:canary5:*:*:*:node.js:*:*
    cpe:2.3:a:vercel:next.js:12.0.2:canary5:*:*:*:node.js:*:*
  • cpe:2.3:a:vercel:next.js:12.0.2:canary6:*:*:*:node.js:*:*
    cpe:2.3:a:vercel:next.js:12.0.2:canary6:*:*:*:node.js:*:*
  • cpe:2.3:a:vercel:next.js:12.0.2:canary7:*:*:*:node.js:*:*
    cpe:2.3:a:vercel:next.js:12.0.2:canary7:*:*:*:node.js:*:*
  • cpe:2.3:a:vercel:next.js:12.0.2:canary8:*:*:*:node.js:*:*
    cpe:2.3:a:vercel:next.js:12.0.2:canary8:*:*:*:node.js:*:*
  • cpe:2.3:a:vercel:next.js:12.0.2:canary9:*:*:*:node.js:*:*
    cpe:2.3:a:vercel:next.js:12.0.2:canary9:*:*:*:node.js:*:*
  • cpe:2.3:a:vercel:next.js:12.0.3:-:*:*:*:node.js:*:*
    cpe:2.3:a:vercel:next.js:12.0.3:-:*:*:*:node.js:*:*
  • cpe:2.3:a:vercel:next.js:12.0.3:canary0:*:*:*:node.js:*:*
    cpe:2.3:a:vercel:next.js:12.0.3:canary0:*:*:*:node.js:*:*
  • cpe:2.3:a:vercel:next.js:12.0.3:canary1:*:*:*:node.js:*:*
    cpe:2.3:a:vercel:next.js:12.0.3:canary1:*:*:*:node.js:*:*
  • cpe:2.3:a:vercel:next.js:12.0.3:canary10:*:*:*:node.js:*:*
    cpe:2.3:a:vercel:next.js:12.0.3:canary10:*:*:*:node.js:*:*
  • cpe:2.3:a:vercel:next.js:12.0.3:canary2:*:*:*:node.js:*:*
    cpe:2.3:a:vercel:next.js:12.0.3:canary2:*:*:*:node.js:*:*
  • cpe:2.3:a:vercel:next.js:12.0.3:canary3:*:*:*:node.js:*:*
    cpe:2.3:a:vercel:next.js:12.0.3:canary3:*:*:*:node.js:*:*
  • cpe:2.3:a:vercel:next.js:12.0.3:canary4:*:*:*:node.js:*:*
    cpe:2.3:a:vercel:next.js:12.0.3:canary4:*:*:*:node.js:*:*
  • cpe:2.3:a:vercel:next.js:12.0.3:canary5:*:*:*:node.js:*:*
    cpe:2.3:a:vercel:next.js:12.0.3:canary5:*:*:*:node.js:*:*
  • cpe:2.3:a:vercel:next.js:12.0.3:canary6:*:*:*:node.js:*:*
    cpe:2.3:a:vercel:next.js:12.0.3:canary6:*:*:*:node.js:*:*
  • cpe:2.3:a:vercel:next.js:12.0.3:canary7:*:*:*:node.js:*:*
    cpe:2.3:a:vercel:next.js:12.0.3:canary7:*:*:*:node.js:*:*
  • cpe:2.3:a:vercel:next.js:12.0.3:canary8:*:*:*:node.js:*:*
    cpe:2.3:a:vercel:next.js:12.0.3:canary8:*:*:*:node.js:*:*
  • cpe:2.3:a:vercel:next.js:12.0.3:canary9:*:*:*:node.js:*:*
    cpe:2.3:a:vercel:next.js:12.0.3:canary9:*:*:*:node.js:*:*
  • cpe:2.3:a:vercel:next.js:12.0.4:-:*:*:*:node.js:*:*
    cpe:2.3:a:vercel:next.js:12.0.4:-:*:*:*:node.js:*:*
  • cpe:2.3:a:vercel:next.js:12.0.4:canary0:*:*:*:node.js:*:*
    cpe:2.3:a:vercel:next.js:12.0.4:canary0:*:*:*:node.js:*:*
  • cpe:2.3:a:vercel:next.js:12.0.4:canary1:*:*:*:node.js:*:*
    cpe:2.3:a:vercel:next.js:12.0.4:canary1:*:*:*:node.js:*:*
  • cpe:2.3:a:vercel:next.js:12.0.4:canary10:*:*:*:node.js:*:*
    cpe:2.3:a:vercel:next.js:12.0.4:canary10:*:*:*:node.js:*:*
  • cpe:2.3:a:vercel:next.js:12.0.4:canary11:*:*:*:node.js:*:*
    cpe:2.3:a:vercel:next.js:12.0.4:canary11:*:*:*:node.js:*:*
  • cpe:2.3:a:vercel:next.js:12.0.4:canary12:*:*:*:node.js:*:*
    cpe:2.3:a:vercel:next.js:12.0.4:canary12:*:*:*:node.js:*:*
  • cpe:2.3:a:vercel:next.js:12.0.4:canary13:*:*:*:node.js:*:*
    cpe:2.3:a:vercel:next.js:12.0.4:canary13:*:*:*:node.js:*:*
  • cpe:2.3:a:vercel:next.js:12.0.4:canary14:*:*:*:node.js:*:*
    cpe:2.3:a:vercel:next.js:12.0.4:canary14:*:*:*:node.js:*:*
  • cpe:2.3:a:vercel:next.js:12.0.4:canary15:*:*:*:node.js:*:*
    cpe:2.3:a:vercel:next.js:12.0.4:canary15:*:*:*:node.js:*:*
  • cpe:2.3:a:vercel:next.js:12.0.4:canary2:*:*:*:node.js:*:*
    cpe:2.3:a:vercel:next.js:12.0.4:canary2:*:*:*:node.js:*:*
  • cpe:2.3:a:vercel:next.js:12.0.4:canary3:*:*:*:node.js:*:*
    cpe:2.3:a:vercel:next.js:12.0.4:canary3:*:*:*:node.js:*:*
  • cpe:2.3:a:vercel:next.js:12.0.4:canary4:*:*:*:node.js:*:*
    cpe:2.3:a:vercel:next.js:12.0.4:canary4:*:*:*:node.js:*:*
  • cpe:2.3:a:vercel:next.js:12.0.4:canary5:*:*:*:node.js:*:*
    cpe:2.3:a:vercel:next.js:12.0.4:canary5:*:*:*:node.js:*:*
  • cpe:2.3:a:vercel:next.js:12.0.4:canary6:*:*:*:node.js:*:*
    cpe:2.3:a:vercel:next.js:12.0.4:canary6:*:*:*:node.js:*:*
  • cpe:2.3:a:vercel:next.js:12.0.4:canary7:*:*:*:node.js:*:*
    cpe:2.3:a:vercel:next.js:12.0.4:canary7:*:*:*:node.js:*:*
  • cpe:2.3:a:vercel:next.js:12.0.4:canary8:*:*:*:node.js:*:*
    cpe:2.3:a:vercel:next.js:12.0.4:canary8:*:*:*:node.js:*:*
  • cpe:2.3:a:vercel:next.js:12.0.4:canary9:*:*:*:node.js:*:*
    cpe:2.3:a:vercel:next.js:12.0.4:canary9:*:*:*:node.js:*:*
  • cpe:2.3:a:vercel:next.js:12.0.5:-:*:*:*:node.js:*:*
    cpe:2.3:a:vercel:next.js:12.0.5:-:*:*:*:node.js:*:*
  • cpe:2.3:a:vercel:next.js:12.0.5:canary0:*:*:*:node.js:*:*
    cpe:2.3:a:vercel:next.js:12.0.5:canary0:*:*:*:node.js:*:*
  • cpe:2.3:a:vercel:next.js:12.0.5:canary1:*:*:*:node.js:*:*
    cpe:2.3:a:vercel:next.js:12.0.5:canary1:*:*:*:node.js:*:*
  • cpe:2.3:a:vercel:next.js:12.0.5:canary10:*:*:*:node.js:*:*
    cpe:2.3:a:vercel:next.js:12.0.5:canary10:*:*:*:node.js:*:*
  • cpe:2.3:a:vercel:next.js:12.0.5:canary11:*:*:*:node.js:*:*
    cpe:2.3:a:vercel:next.js:12.0.5:canary11:*:*:*:node.js:*:*
  • cpe:2.3:a:vercel:next.js:12.0.5:canary12:*:*:*:node.js:*:*
    cpe:2.3:a:vercel:next.js:12.0.5:canary12:*:*:*:node.js:*:*
  • cpe:2.3:a:vercel:next.js:12.0.5:canary13:*:*:*:node.js:*:*
    cpe:2.3:a:vercel:next.js:12.0.5:canary13:*:*:*:node.js:*:*
  • cpe:2.3:a:vercel:next.js:12.0.5:canary14:*:*:*:node.js:*:*
    cpe:2.3:a:vercel:next.js:12.0.5:canary14:*:*:*:node.js:*:*
  • cpe:2.3:a:vercel:next.js:12.0.5:canary15:*:*:*:node.js:*:*
    cpe:2.3:a:vercel:next.js:12.0.5:canary15:*:*:*:node.js:*:*
  • cpe:2.3:a:vercel:next.js:12.0.5:canary16:*:*:*:node.js:*:*
    cpe:2.3:a:vercel:next.js:12.0.5:canary16:*:*:*:node.js:*:*
  • cpe:2.3:a:vercel:next.js:12.0.5:canary17:*:*:*:node.js:*:*
    cpe:2.3:a:vercel:next.js:12.0.5:canary17:*:*:*:node.js:*:*
  • cpe:2.3:a:vercel:next.js:12.0.5:canary18:*:*:*:node.js:*:*
    cpe:2.3:a:vercel:next.js:12.0.5:canary18:*:*:*:node.js:*:*
  • cpe:2.3:a:vercel:next.js:12.0.5:canary19:*:*:*:node.js:*:*
    cpe:2.3:a:vercel:next.js:12.0.5:canary19:*:*:*:node.js:*:*
  • cpe:2.3:a:vercel:next.js:12.0.5:canary2:*:*:*:node.js:*:*
    cpe:2.3:a:vercel:next.js:12.0.5:canary2:*:*:*:node.js:*:*
  • cpe:2.3:a:vercel:next.js:12.0.5:canary3:*:*:*:node.js:*:*
    cpe:2.3:a:vercel:next.js:12.0.5:canary3:*:*:*:node.js:*:*
  • cpe:2.3:a:vercel:next.js:12.0.5:canary4:*:*:*:node.js:*:*
    cpe:2.3:a:vercel:next.js:12.0.5:canary4:*:*:*:node.js:*:*
  • cpe:2.3:a:vercel:next.js:12.0.5:canary5:*:*:*:node.js:*:*
    cpe:2.3:a:vercel:next.js:12.0.5:canary5:*:*:*:node.js:*:*
  • cpe:2.3:a:vercel:next.js:12.0.5:canary6:*:*:*:node.js:*:*
    cpe:2.3:a:vercel:next.js:12.0.5:canary6:*:*:*:node.js:*:*
  • cpe:2.3:a:vercel:next.js:12.0.5:canary7:*:*:*:node.js:*:*
    cpe:2.3:a:vercel:next.js:12.0.5:canary7:*:*:*:node.js:*:*
  • cpe:2.3:a:vercel:next.js:12.0.5:canary8:*:*:*:node.js:*:*
    cpe:2.3:a:vercel:next.js:12.0.5:canary8:*:*:*:node.js:*:*
  • cpe:2.3:a:vercel:next.js:12.0.5:canary9:*:*:*:node.js:*:*
    cpe:2.3:a:vercel:next.js:12.0.5:canary9:*:*:*:node.js:*:*
  • cpe:2.3:a:vercel:next.js:12.0.6:-:*:*:*:node.js:*:*
    cpe:2.3:a:vercel:next.js:12.0.6:-:*:*:*:node.js:*:*
  • cpe:2.3:a:vercel:next.js:12.0.6:canary0:*:*:*:node.js:*:*
    cpe:2.3:a:vercel:next.js:12.0.6:canary0:*:*:*:node.js:*:*
  • cpe:2.3:a:vercel:next.js:12.0.7:-:*:*:*:node.js:*:*
    cpe:2.3:a:vercel:next.js:12.0.7:-:*:*:*:node.js:*:*
  • cpe:2.3:a:vercel:next.js:12.0.7:canary0:*:*:*:node.js:*:*
    cpe:2.3:a:vercel:next.js:12.0.7:canary0:*:*:*:node.js:*:*
  • cpe:2.3:a:vercel:next.js:12.0.8:-:*:*:*:node.js:*:*
    cpe:2.3:a:vercel:next.js:12.0.8:-:*:*:*:node.js:*:*
  • cpe:2.3:a:vercel:next.js:12.0.8:canary0:*:*:*:node.js:*:*
    cpe:2.3:a:vercel:next.js:12.0.8:canary0:*:*:*:node.js:*:*
  • cpe:2.3:a:vercel:next.js:12.0.8:canary1:*:*:*:node.js:*:*
    cpe:2.3:a:vercel:next.js:12.0.8:canary1:*:*:*:node.js:*:*
  • cpe:2.3:a:vercel:next.js:12.0.8:canary10:*:*:*:node.js:*:*
    cpe:2.3:a:vercel:next.js:12.0.8:canary10:*:*:*:node.js:*:*
  • cpe:2.3:a:vercel:next.js:12.0.8:canary11:*:*:*:node.js:*:*
    cpe:2.3:a:vercel:next.js:12.0.8:canary11:*:*:*:node.js:*:*
  • cpe:2.3:a:vercel:next.js:12.0.8:canary12:*:*:*:node.js:*:*
    cpe:2.3:a:vercel:next.js:12.0.8:canary12:*:*:*:node.js:*:*
  • cpe:2.3:a:vercel:next.js:12.0.8:canary13:*:*:*:node.js:*:*
    cpe:2.3:a:vercel:next.js:12.0.8:canary13:*:*:*:node.js:*:*
  • cpe:2.3:a:vercel:next.js:12.0.8:canary14:*:*:*:node.js:*:*
    cpe:2.3:a:vercel:next.js:12.0.8:canary14:*:*:*:node.js:*:*
  • cpe:2.3:a:vercel:next.js:12.0.8:canary15:*:*:*:node.js:*:*
    cpe:2.3:a:vercel:next.js:12.0.8:canary15:*:*:*:node.js:*:*
  • cpe:2.3:a:vercel:next.js:12.0.8:canary16:*:*:*:node.js:*:*
    cpe:2.3:a:vercel:next.js:12.0.8:canary16:*:*:*:node.js:*:*
  • cpe:2.3:a:vercel:next.js:12.0.8:canary17:*:*:*:node.js:*:*
    cpe:2.3:a:vercel:next.js:12.0.8:canary17:*:*:*:node.js:*:*
  • cpe:2.3:a:vercel:next.js:12.0.8:canary18:*:*:*:node.js:*:*
    cpe:2.3:a:vercel:next.js:12.0.8:canary18:*:*:*:node.js:*:*
  • cpe:2.3:a:vercel:next.js:12.0.8:canary19:*:*:*:node.js:*:*
    cpe:2.3:a:vercel:next.js:12.0.8:canary19:*:*:*:node.js:*:*
  • cpe:2.3:a:vercel:next.js:12.0.8:canary2:*:*:*:node.js:*:*
    cpe:2.3:a:vercel:next.js:12.0.8:canary2:*:*:*:node.js:*:*
  • cpe:2.3:a:vercel:next.js:12.0.8:canary20:*:*:*:node.js:*:*
    cpe:2.3:a:vercel:next.js:12.0.8:canary20:*:*:*:node.js:*:*
  • cpe:2.3:a:vercel:next.js:12.0.8:canary21:*:*:*:node.js:*:*
    cpe:2.3:a:vercel:next.js:12.0.8:canary21:*:*:*:node.js:*:*
  • cpe:2.3:a:vercel:next.js:12.0.8:canary22:*:*:*:node.js:*:*
    cpe:2.3:a:vercel:next.js:12.0.8:canary22:*:*:*:node.js:*:*
  • cpe:2.3:a:vercel:next.js:12.0.8:canary3:*:*:*:node.js:*:*
    cpe:2.3:a:vercel:next.js:12.0.8:canary3:*:*:*:node.js:*:*
  • cpe:2.3:a:vercel:next.js:12.0.8:canary4:*:*:*:node.js:*:*
    cpe:2.3:a:vercel:next.js:12.0.8:canary4:*:*:*:node.js:*:*
  • cpe:2.3:a:vercel:next.js:12.0.8:canary5:*:*:*:node.js:*:*
    cpe:2.3:a:vercel:next.js:12.0.8:canary5:*:*:*:node.js:*:*
  • cpe:2.3:a:vercel:next.js:12.0.8:canary6:*:*:*:node.js:*:*
    cpe:2.3:a:vercel:next.js:12.0.8:canary6:*:*:*:node.js:*:*
  • cpe:2.3:a:vercel:next.js:12.0.8:canary7:*:*:*:node.js:*:*
    cpe:2.3:a:vercel:next.js:12.0.8:canary7:*:*:*:node.js:*:*
  • cpe:2.3:a:vercel:next.js:12.0.8:canary8:*:*:*:node.js:*:*
    cpe:2.3:a:vercel:next.js:12.0.8:canary8:*:*:*:node.js:*:*
  • cpe:2.3:a:vercel:next.js:12.0.8:canary9:*:*:*:node.js:*:*
    cpe:2.3:a:vercel:next.js:12.0.8:canary9:*:*:*:node.js:*:*

Protect Your Infrastructure against CVE-2022-21721: 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-2024-43107 – Improper Certificate Validation (CWE-295) in the Gallagher Milestone Integration Plugin (MIP) permits unauthenticated messages (e.g. alarm events) ...
  • CVE-2024-41724 – Improper Certificate Validation (CWE-295) in the Gallagher Command Centre SALTO integration allowed an attacker to spoof the SALTO server. Thi...
  • CVE-2025-2133 – A vulnerability classified as problematic was found in ftcms 2.1. Affected by this vulnerability is an unknown functionality of the file /admin/ind...
  • CVE-2025-2132 – A vulnerability classified as critical has been found in ftcms 2.1. Affected is an unknown function of the file /admin/index.php/web/ajax_all_lists...
  • CVE-2025-2131 – A vulnerability was found in dayrui XunRuiCMS up to 4.6.3. It has been rated as problematic. This issue affects some unknown processing of the comp...