CVE-2022-49171: Software Security Vulnerability Vulnerability

MODERATE
Advisory Identifier: GHSA-qgfx-vv83-vj4g
CVSS 5.5
CWE-617
Published
Advisory Summary

CVE-2022-49171 is a MODERATE (CVSS 5.5) security vulnerability vulnerability (CWE-617: Reachable Assertion) affecting Software libraries in the Maven ecosystem. The weakness occurs when the product contains an assert() or similar statement that can be triggered by an attacker, which leads to an application exit or other behavior that is more severe than necessary.. Remediation is available in the latest vendor maintenance releases.

CVE-2022-49171 at a Glance

CVE Identifier CVE-2022-49171
GHSA Identifier GHSA-qgfx-vv83-vj4g
Severity MODERATE
CVSS v3.1 Base Score 5.5
CWE Classification CWE-617: Reachable Assertion
Affected Product Software
Package Ecosystem Maven
Published Date
Last Updated

Security Impact

CVSS: 5.5

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H).

Attack Vector Local (AV:L)
Attack Complexity Low (AC:L)
Privileges Required Low (PR:L)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality None (C:N)
Integrity None (I:N)
Availability High (A:H)

How to Fix CVE-2022-49171

To remediate this vulnerability, upgrade all affected Software dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

mvn dependency:tree

How to Check if You Are Affected

To determine whether your Java application is affected by CVE-2022-49171, inspect your build dependencies using the Maven Dependency Plugin:

mvn dependency:tree

Analyze the terminal output to locate any version of Software in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than the patched release), your application is affected.

Note: The mvn dependency:tree command inspects the resolved dependency graph declared in your project's POM files; it does not perform automated security scanning or inspect runtime dynamic classpaths. Always verify runtime container classpaths and shaded JARs.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-617: Reachable Assertion, where the product contains an assert() or similar statement that can be triggered by an attacker, which leads to an application exit or other behavior that is more severe than necessary. In Software, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

In the Linux kernel, the following vulnerability has been resolved: ext4: don't BUG if someone dirty pages without asking ext4 first [un]pin_user_pages_remote is dirtying pages without properly warning the file system in advance. A related race was noted by Jan Kara in 2018[1]; however, more recently instead of it being a very hard-to-hit race, it could be reliably triggered by process_vm_writev(2) which was discovered by Syzbot[2]. This is technically a bug in mm/gup.c, but arguably ext4 is fragile in that if some other kernel subsystem dirty pages without properly notifying the file system using page_mkwrite(), ext4 will BUG, while other file systems will not BUG (although data will still be lost). So instead of crashing with a BUG, issue a warning (since there may be potential data loss) and just mark the page as clean to avoid unprivileged denial of service attacks until the problem can be properly fixed. More discussion and background can be found in the thread starting at [2]. [1] https://lore.kernel.org/linux-mm/20180103100430.GE4911@quack2.suse.cz [2] https://lore.kernel.org/r/Yg0m6IjcNmfaSokM@google.com

References

Frequently Asked Questions

What is CVE-2022-49171?
CVE-2022-49171 is a security vulnerability in Software classified as a security vulnerability vulnerability under CWE-617: Reachable Assertion.
Which Software versions are affected?
Affected versions include releases prior to current release patches.
What version fixes CVE-2022-49171?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What is the CVSS score of CVE-2022-49171?
CVE-2022-49171 has a CVSS v3.1 base score of 5.5 (MODERATE) with vector string CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H.
What CWE is associated with CVE-2022-49171?
CVE-2022-49171 is classified under CWE-617: Reachable Assertion (The product contains an assert() or similar statement that can be triggered by an attacker, which leads to an application exit or other behavior that is more severe than necessary.).
How can I check Maven dependencies for CVE-2022-49171?
Run the dependency tree command: 'mvn dependency:tree'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-qgfx-vv83-vj4g",
  "modified" : "2025-09-23T15:31:08Z",
  "published" : "2025-09-23T15:31:08Z",
  "aliases" : [ "CVE-2022-49171" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\next4: don't BUG if someone dirty pages without asking ext4 first\n\n[un]pin_user_pages_remote is dirtying pages without properly warning\nthe file system in advance.  A related race was noted by Jan Kara in\n2018[1]; however, more recently instead of it being a very hard-to-hit\nrace, it could be reliably triggered by process_vm_writev(2) which was\ndiscovered by Syzbot[2].\n\nThis is technically a bug in mm/gup.c, but arguably ext4 is fragile in\nthat if some other kernel subsystem dirty pages without properly\nnotifying the file system using page_mkwrite(), ext4 will BUG, while\nother file systems will not BUG (although data will still be lost).\n\nSo instead of crashing with a BUG, issue a warning (since there may be\npotential data loss) and just mark the page as clean to avoid\nunprivileged denial of service attacks until the problem can be\nproperly fixed.  More discussion and background can be found in the\nthread starting at [2].\n\n[1] https://lore.kernel.org/linux-mm/20180103100430.GE4911@quack2.suse.cz\n[2] https://lore.kernel.org/r/Yg0m6IjcNmfaSokM@google.com",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H"
  } ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2022-49171"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/0d3a6926f7e8be3c897fa46216ce13b119a9f56a"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/330d0e44fc5a47c27df958ecdd4693a3cb1d8b81"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/343117559ef41e992e326f7a92da1a8f254dfa8c"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/5a016c053f426a73752c3b41b60b497b58694d48"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/5db60e76edf5680ff1f3a7221036fc44b308f146"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/677c9d30e8487bee6c8e3b034070319d98f6e203"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/a0856764dc1276ad2dc7891288c2e9246bf11a37"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/cc5095747edfb054ca2068d01af20be3fcc3634f"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/d666dfaa571465a19f014534a214c255ea33f301"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-617" ],
    "severity" : "MODERATE",
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2025-02-26T07:00:54Z"
  }
}