CVE-2022-49180: Software Security Vulnerability Vulnerability

MODERATE
Advisory Identifier: GHSA-pqwr-48cq-xrw8
Share
CVSS 5.5
Published
Advisory Summary

CVE-2022-49180 is a MODERATE (CVSS 5.5) security vulnerability vulnerability (General Security Weakness) affecting Software libraries in the Maven ecosystem. Remediation is available in the latest vendor maintenance releases.

CVE-2022-49180 at a Glance

CVE Identifier CVE-2022-49180
GHSA Identifier GHSA-pqwr-48cq-xrw8
Severity MODERATE
CVSS v3.1 Base Score 5.5
CWE Classification General Security Weakness
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-49180

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-49180, 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 General Security Weakness. 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: LSM: general protection fault in legacy_parse_param The usual LSM hook "bail on fail" scheme doesn't work for cases where a security module may return an error code indicating that it does not recognize an input. In this particular case Smack sees a mount option that it recognizes, and returns 0. A call to a BPF hook follows, which returns -ENOPARAM, which confuses the caller because Smack has processed its data. The SELinux hook incorrectly returns 1 on success. There was a time when this was correct, however the current expectation is that it return 0 on success. This is repaired.

References

NVD — CVE-2022-49180 NVD
https://nvd.nist.gov/vuln/detail/CVE-2022-49180
git.kernel.org/stable/c/00fc07fa0b... WEB
https://git.kernel.org/stable/c/00fc07fa0b4a004711b6e1a944f0d2e46f7093b7
git.kernel.org/stable/c/2784604c8c... WEB
https://git.kernel.org/stable/c/2784604c8c6fc523248f8f80a421c313a9d790b7
git.kernel.org/stable/c/cadae7c5e4... WEB
https://git.kernel.org/stable/c/cadae7c5e477aaafcba819b8e4a3d1c1a1503b62
git.kernel.org/stable/c/ddcdda888e... WEB
https://git.kernel.org/stable/c/ddcdda888e14ca451b3ee83d11b65b2a9c8e783b
git.kernel.org/stable/c/ecff30575b... WEB
https://git.kernel.org/stable/c/ecff30575b5ad0eda149aadad247b7f75411fd47
git.kernel.org/stable/c/f3f93a1aaa... WEB
https://git.kernel.org/stable/c/f3f93a1aaafc3032e0a9655fb43deccfb3e953a3

Frequently Asked Questions

What is CVE-2022-49180?
CVE-2022-49180 is a security vulnerability in Software classified as a security vulnerability vulnerability under General Security Weakness.
Which Software versions are affected?
Affected versions include releases prior to current release patches.
What version fixes CVE-2022-49180?
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-49180?
CVE-2022-49180 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-49180?
CVE-2022-49180 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2022-49180?
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
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-pqwr-48cq-xrw8",
  "modified" : "2025-10-22T18:30:30Z",
  "published" : "2025-10-22T18:30:30Z",
  "aliases" : [ "CVE-2022-49180" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nLSM: general protection fault in legacy_parse_param\n\nThe usual LSM hook \"bail on fail\" scheme doesn't work for cases where\na security module may return an error code indicating that it does not\nrecognize an input.  In this particular case Smack sees a mount option\nthat it recognizes, and returns 0. A call to a BPF hook follows, which\nreturns -ENOPARAM, which confuses the caller because Smack has processed\nits data.\n\nThe SELinux hook incorrectly returns 1 on success. There was a time\nwhen this was correct, however the current expectation is that it\nreturn 0 on success. This is repaired.",
  "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-49180"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/00fc07fa0b4a004711b6e1a944f0d2e46f7093b7"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/2784604c8c6fc523248f8f80a421c313a9d790b7"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/cadae7c5e477aaafcba819b8e4a3d1c1a1503b62"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/ddcdda888e14ca451b3ee83d11b65b2a9c8e783b"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/ecff30575b5ad0eda149aadad247b7f75411fd47"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/f3f93a1aaafc3032e0a9655fb43deccfb3e953a3"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : "MODERATE",
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2025-02-26T07:00:55Z"
  }
}