CVE-2022-31129 Vulnerability Analysis & Exploit Details

CVE-2022-31129
Vulnerability Scoring

7.5
/10
Very High Risk

Highly exploitable, CVE-2022-31129 poses a critical security risk that could lead to severe breaches.

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-31129 Details

Status: Modified

Last updated: 🕖 21 Nov 2024, 07:03 UTC
Originally published on: 🕕 06 Jul 2022, 18:15 UTC

Time between publication and last update: 868 days

CVSS Release: version 3

CVSS3 Source

security-advisories@github.com

CVSS3 Type

Secondary

CVSS3 Vector

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

CVE-2022-31129 Vulnerability Summary

CVE-2022-31129: moment is a JavaScript date library for parsing, validating, manipulating, and formatting dates. Affected versions of moment were found to use an inefficient parsing algorithm. Specifically using string-to-date parsing in moment (more specifically rfc2822 parsing, which is tried by default) has quadratic (N^2) complexity on specific inputs. Users may notice a noticeable slowdown is observed with inputs above 10k characters. Users who pass user-provided strings without sanity length checks to moment constructor are vulnerable to (Re)DoS attacks. The problem is patched in 2.29.4, the patch can be applied to all affected versions with minimal tweaking. Users are advised to upgrade. Users unable to upgrade should consider limiting date lengths accepted from user input.

Assessing the Risk of CVE-2022-31129

Access Complexity Graph

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

With low attack complexity and no required privileges, CVE-2022-31129 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-31129, 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-31129, 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-31129 has no significant impact on data confidentiality.
  • Integrity: None
    CVE-2022-31129 poses no threat to data integrity.
  • Availability: High
    CVE-2022-31129 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.502% (probability of exploit)

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

CVE-2022-31129 References

External References

CWE Common Weakness Enumeration

CWE-1333

CAPEC Common Attack Pattern Enumeration and Classification

  • Regular Expression Exponential Blowup CAPEC-492 An adversary may execute an attack on a program that uses a poor Regular Expression(Regex) implementation by choosing input that results in an extreme situation for the Regex. A typical extreme situation operates at exponential time compared to the input size. This is due to most implementations using a Nondeterministic Finite Automaton(NFA) state machine to be built by the Regex algorithm since NFA allows backtracking and thus more complex regular expressions.

Vulnerable Configurations

  • cpe:2.3:a:momentjs:moment:2.18.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:momentjs:moment:2.18.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:momentjs:moment:2.18.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:momentjs:moment:2.18.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:momentjs:moment:2.19.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:momentjs:moment:2.19.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:momentjs:moment:2.19.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:momentjs:moment:2.19.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:momentjs:moment:2.19.2:*:*:*:*:node.js:*:*
    cpe:2.3:a:momentjs:moment:2.19.2:*:*:*:*:node.js:*:*
  • cpe:2.3:a:momentjs:moment:2.19.3:*:*:*:*:node.js:*:*
    cpe:2.3:a:momentjs:moment:2.19.3:*:*:*:*:node.js:*:*
  • cpe:2.3:a:momentjs:moment:2.19.4:*:*:*:*:node.js:*:*
    cpe:2.3:a:momentjs:moment:2.19.4:*:*:*:*:node.js:*:*
  • cpe:2.3:a:momentjs:moment:2.20.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:momentjs:moment:2.20.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:momentjs:moment:2.20.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:momentjs:moment:2.20.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:momentjs:moment:2.21.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:momentjs:moment:2.21.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:momentjs:moment:2.22.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:momentjs:moment:2.22.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:momentjs:moment:2.22.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:momentjs:moment:2.22.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:momentjs:moment:2.22.2:*:*:*:*:node.js:*:*
    cpe:2.3:a:momentjs:moment:2.22.2:*:*:*:*:node.js:*:*
  • cpe:2.3:a:momentjs:moment:2.23.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:momentjs:moment:2.23.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:momentjs:moment:2.24.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:momentjs:moment:2.24.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:momentjs:moment:2.25.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:momentjs:moment:2.25.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:momentjs:moment:2.25.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:momentjs:moment:2.25.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:momentjs:moment:2.25.2:*:*:*:*:node.js:*:*
    cpe:2.3:a:momentjs:moment:2.25.2:*:*:*:*:node.js:*:*
  • cpe:2.3:a:momentjs:moment:2.25.3:*:*:*:*:node.js:*:*
    cpe:2.3:a:momentjs:moment:2.25.3:*:*:*:*:node.js:*:*
  • cpe:2.3:a:momentjs:moment:2.26.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:momentjs:moment:2.26.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:momentjs:moment:2.27.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:momentjs:moment:2.27.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:momentjs:moment:2.28.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:momentjs:moment:2.28.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:momentjs:moment:2.29.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:momentjs:moment:2.29.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:momentjs:moment:2.29.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:momentjs:moment:2.29.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:momentjs:moment:2.29.2:*:*:*:*:node.js:*:*
    cpe:2.3:a:momentjs:moment:2.29.2:*:*:*:*:node.js:*:*
  • cpe:2.3:a:momentjs:moment:2.29.2:*:*:*:*:nuget:*:*
    cpe:2.3:a:momentjs:moment:2.29.2:*:*:*:*:nuget:*:*
  • cpe:2.3:a:momentjs:moment:2.29.3:*:*:*:*:node.js:*:*
    cpe:2.3:a:momentjs:moment:2.29.3:*:*:*:*:node.js:*:*
  • cpe:2.3:o:fedoraproject:fedora:35:*:*:*:*:*:*:*
    cpe:2.3:o:fedoraproject:fedora:35:*:*:*:*:*:*:*
  • cpe:2.3:o:fedoraproject:fedora:36:*:*:*:*:*:*:*
    cpe:2.3:o:fedoraproject:fedora:36:*:*:*:*:*:*:*
  • cpe:2.3:o:fedoraproject:fedora:37:*:*:*:*:*:*:*
    cpe:2.3:o:fedoraproject:fedora:37:*:*:*:*:*:*:*
  • cpe:2.3:o:debian:debian_linux:10.0:*:*:*:*:*:*:*
    cpe:2.3:o:debian:debian_linux:10.0:*:*:*:*:*:*:*

Protect Your Infrastructure against CVE-2022-31129: 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-3103 – The CLEVER - HTML5 Radio Player With History - Shoutcast and Icecast - Elementor Widget Addon plugin for WordPress is vulnerable to arbitrary file ...
  • CVE-2025-3275 – The Themesflat Addons For Elementor plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the TF E Slider widget in all versions up...
  • CVE-2025-1457 – The Element Pack Addons for Elementor – Free Templates and Widgets for Your WordPress Websites plugin for WordPress is vulnerable to Stored Cross-S...
  • CVE-2025-1093 – The AIHub theme for WordPress is vulnerable to arbitrary file uploads due to missing file type validation in the generate_image function in all ver...
  • CVE-2025-3284 – The User Registration & Membership – Custom Registration Form, Login Form, and User Profile plugin for WordPress is vulnerable to Cross-Site Reques...