CVE-2022-32153: Software Security Vulnerability Vulnerability

HIGH
Advisory Identifier: GHSA-3vq3-mvhh-hjcp
Share
CVSS 8.1
CWE-295
Published
Advisory Summary

CVE-2022-32153 is a HIGH (CVSS 8.1) security vulnerability vulnerability (CWE-295: Improper Certificate Validation) affecting Software libraries in the Maven ecosystem. The weakness occurs when the product does not validate, or incorrectly validates, a certificate.. Remediation is available in the latest vendor maintenance releases.

CVE-2022-32153 at a Glance

CVE Identifier CVE-2022-32153
GHSA Identifier GHSA-3vq3-mvhh-hjcp
Severity HIGH
CVSS v3.1 Base Score 8.1
CWE Classification CWE-295: Improper Certificate Validation
Affected Product Software
Package Ecosystem Maven
Published Date
Last Updated

Security Impact

CVSS: 8.1

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

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

How to Fix CVE-2022-32153

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-32153, 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-295: Improper Certificate Validation, where the product does not validate, or incorrectly validates, a certificate. 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

Splunk Enterprise peers in Splunk Enterprise versions before 9.0 and Splunk Cloud Platform versions before 8.2.2203 did not validate the TLS certificates during Splunk-to-Splunk communications by default. Splunk peer communications configured properly with valid certificates were not vulnerable. However, an attacker with administrator credentials could add a peer without a valid certificate and connections from misconfigured nodes without valid certificates did not fail by default. For Splunk Enterprise, update to Splunk Enterprise version 9.0 and Configure TLS host name validation for Splunk-to-Splunk communications (https://docs.splunk.com/Documentation/Splunk/9.0.0/Security/EnableTLSCertHostnameValidation) to enable the remediation.

References

NVD — CVE-2022-32153 NVD
https://nvd.nist.gov/vuln/detail/CVE-2022-32153
Software Security Information SECURITY
https://docs.splunk.com/Documentation/Splunk/9.0.0/Security/EnableTLSCertHostnameValidation
Software Security Information SECURITY
https://docs.splunk.com/Documentation/Splunk/9.0.0/Security/Updates
research.splunk.com/application/splunk_... WEB
https://research.splunk.com/application/splunk_digital_certificates_infrastructure_version
research.splunk.com/application/splunk_... WEB
https://research.splunk.com/application/splunk_digital_certificates_lack_of_encryption
research.splunk.com/application/splunk_... WEB
https://research.splunk.com/application/splunk_protocol_impersonation_weak_encryption_selfsigned
research.splunk.com/network/splunk_iden... WEB
https://research.splunk.com/network/splunk_identified_ssl_tls_certificates
Software Security Information SECURITY
https://www.splunk.com/en_us/product-security/announcements/svd-2022-0603.html

Frequently Asked Questions

What is CVE-2022-32153?
CVE-2022-32153 is a security vulnerability in Software classified as a security vulnerability vulnerability under CWE-295: Improper Certificate Validation.
Which Software versions are affected?
Affected versions include releases prior to current release patches.
What version fixes CVE-2022-32153?
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-32153?
CVE-2022-32153 has a CVSS v3.1 base score of 8.1 (HIGH) with vector string CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H.
What CWE is associated with CVE-2022-32153?
CVE-2022-32153 is classified under CWE-295: Improper Certificate Validation (The product does not validate, or incorrectly validates, a certificate.).
How can I check Maven dependencies for CVE-2022-32153?
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-3vq3-mvhh-hjcp",
  "modified" : "2022-06-25T00:01:03Z",
  "published" : "2022-06-16T00:00:22Z",
  "aliases" : [ "CVE-2022-32153" ],
  "details" : "Splunk Enterprise peers in Splunk Enterprise versions before 9.0 and Splunk Cloud Platform versions before 8.2.2203 did not validate the TLS certificates during Splunk-to-Splunk communications by default. Splunk peer communications configured properly with valid certificates were not vulnerable. However, an attacker with administrator credentials could add a peer without a valid certificate and connections from misconfigured nodes without valid certificates did not fail by default. For Splunk Enterprise, update to Splunk Enterprise version 9.0 and Configure TLS host name validation for Splunk-to-Splunk communications (https://docs.splunk.com/Documentation/Splunk/9.0.0/Security/EnableTLSCertHostnameValidation) to enable the remediation.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H"
  } ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2022-32153"
  }, {
    "type" : "WEB",
    "url" : "https://docs.splunk.com/Documentation/Splunk/9.0.0/Security/EnableTLSCertHostnameValidation"
  }, {
    "type" : "WEB",
    "url" : "https://docs.splunk.com/Documentation/Splunk/9.0.0/Security/Updates"
  }, {
    "type" : "WEB",
    "url" : "https://research.splunk.com/application/splunk_digital_certificates_infrastructure_version"
  }, {
    "type" : "WEB",
    "url" : "https://research.splunk.com/application/splunk_digital_certificates_lack_of_encryption"
  }, {
    "type" : "WEB",
    "url" : "https://research.splunk.com/application/splunk_protocol_impersonation_weak_encryption_selfsigned"
  }, {
    "type" : "WEB",
    "url" : "https://research.splunk.com/network/splunk_identified_ssl_tls_certificates"
  }, {
    "type" : "WEB",
    "url" : "https://www.splunk.com/en_us/product-security/announcements/svd-2022-0603.html"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-295" ],
    "severity" : "HIGH",
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2022-06-15T17:15:00Z"
  }
}