CVE-2023-52925: Software Security Vulnerability Vulnerability

MODERATE
Advisory Identifier: GHSA-cgvr-gqfv-x5mj
Share
CVSS 6.2
Published
Advisory Summary

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

CVE-2023-52925 at a Glance

CVE Identifier CVE-2023-52925
GHSA Identifier GHSA-cgvr-gqfv-x5mj
Severity MODERATE
CVSS v3.1 Base Score 6.2
CWE Classification General Security Weakness
Affected Product Software
Package Ecosystem Maven
Published Date
Last Updated

Security Impact

CVSS: 6.2

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

Attack Vector Local (AV:L)
Attack Complexity Low (AC:L)
Privileges Required None (PR:N)
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-2023-52925

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-2023-52925, 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: netfilter: nf_tables: don't fail inserts if duplicate has expired nftables selftests fail: run-tests.sh testcases/sets/0044interval_overlap_0 Expected: 0-2 . 0-3, got: W: [FAILED] ./testcases/sets/0044interval_overlap_0: got 1 Insertion must ignore duplicate but expired entries. Moreover, there is a strange asymmetry in nft_pipapo_activate: It refetches the current element, whereas the other ->activate callbacks (bitmap, hash, rhash, rbtree) use elem->priv. Same for .remove: other set implementations take elem->priv, nft_pipapo_remove fetches elem->priv, then does a relookup, remove this. I suspect this was the reason for the change that prompted the removal of the expired check in pipapo_get() in the first place, but skipping exired elements there makes no sense to me, this helper is used for normal get requests, insertions (duplicate check) and deactivate callback. In first two cases expired elements must be skipped. For ->deactivate(), this gets called for DELSETELEM, so it seems to me that expired elements should be skipped as well, i.e. delete request should fail with -ENOENT error.

References

NVD — CVE-2023-52925 NVD
https://nvd.nist.gov/vuln/detail/CVE-2023-52925
git.kernel.org/stable/c/156369a702... WEB
https://git.kernel.org/stable/c/156369a702c33ad5434a19c3a689bfb836d4e0b8
git.kernel.org/stable/c/59ee68c437... WEB
https://git.kernel.org/stable/c/59ee68c437c562170265194a99698c805a686bb3
git.kernel.org/stable/c/7845914f45... WEB
https://git.kernel.org/stable/c/7845914f45f066497ac75b30c50dbc735e84e884
git.kernel.org/stable/c/891ca5dfe3... WEB
https://git.kernel.org/stable/c/891ca5dfe3b718b441fc786014a7ba8f517da188
git.kernel.org/stable/c/af78b0489e... WEB
https://git.kernel.org/stable/c/af78b0489e8898a8c9449ffc0fdd2e181916f0d4

Frequently Asked Questions

What is CVE-2023-52925?
CVE-2023-52925 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-2023-52925?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What is the CVSS score of CVE-2023-52925?
CVE-2023-52925 has a CVSS v3.1 base score of 6.2 (MODERATE) with vector string CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H.
What CWE is associated with CVE-2023-52925?
CVE-2023-52925 is classified under General Security Weakness.
How can I check Maven dependencies for CVE-2023-52925?
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-cgvr-gqfv-x5mj",
  "modified" : "2025-02-06T18:31:05Z",
  "published" : "2025-02-05T12:33:06Z",
  "aliases" : [ "CVE-2023-52925" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nnetfilter: nf_tables: don't fail inserts if duplicate has expired\n\nnftables selftests fail:\nrun-tests.sh testcases/sets/0044interval_overlap_0\nExpected: 0-2 . 0-3, got:\nW: [FAILED]     ./testcases/sets/0044interval_overlap_0: got 1\n\nInsertion must ignore duplicate but expired entries.\n\nMoreover, there is a strange asymmetry in nft_pipapo_activate:\n\nIt refetches the current element, whereas the other ->activate callbacks\n(bitmap, hash, rhash, rbtree) use elem->priv.\nSame for .remove: other set implementations take elem->priv,\nnft_pipapo_remove fetches elem->priv, then does a relookup,\nremove this.\n\nI suspect this was the reason for the change that prompted the\nremoval of the expired check in pipapo_get() in the first place,\nbut skipping exired elements there makes no sense to me, this helper\nis used for normal get requests, insertions (duplicate check)\nand deactivate callback.\n\nIn first two cases expired elements must be skipped.\n\nFor ->deactivate(), this gets called for DELSETELEM, so it\nseems to me that expired elements should be skipped as well, i.e.\ndelete request should fail with -ENOENT error.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H"
  } ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2023-52925"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/156369a702c33ad5434a19c3a689bfb836d4e0b8"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/59ee68c437c562170265194a99698c805a686bb3"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/7845914f45f066497ac75b30c50dbc735e84e884"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/891ca5dfe3b718b441fc786014a7ba8f517da188"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/af78b0489e8898a8c9449ffc0fdd2e181916f0d4"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : "MODERATE",
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2025-02-05T10:15:21Z"
  }
}