CVE-2023-52699: Software Security Vulnerability Vulnerability

MODERATE
Advisory Identifier: GHSA-29pq-gr25-8674
Share
CVSS 5.3
CWE-667
Published
Advisory Summary

CVE-2023-52699 is a MODERATE (CVSS 5.3) security vulnerability vulnerability (CWE-667: Improper Locking) affecting Software libraries in the Maven ecosystem. The weakness occurs when the product does not properly acquire or release a lock on a resource, leading to unexpected resource state changes and behaviors.. Remediation is available in the latest vendor maintenance releases.

CVE-2023-52699 at a Glance

CVE Identifier CVE-2023-52699
GHSA Identifier GHSA-29pq-gr25-8674
Severity MODERATE
CVSS v3.1 Base Score 5.3
CWE Classification CWE-667: Improper Locking
Affected Product Software
Package Ecosystem Maven
Published Date
Last Updated

Security Impact

CVSS: 5.3

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

Attack Vector Network (AV:N)
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 Low (A:L)

How to Fix CVE-2023-52699

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-52699, 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-667: Improper Locking, where the product does not properly acquire or release a lock on a resource, leading to unexpected resource state changes and behaviors. 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: sysv: don't call sb_bread() with pointers_lock held syzbot is reporting sleep in atomic context in SysV filesystem [1], for sb_bread() is called with rw_spinlock held. A "write_lock(&pointers_lock) => read_lock(&pointers_lock) deadlock" bug and a "sb_bread() with write_lock(&pointers_lock)" bug were introduced by "Replace BKL for chain locking with sysvfs-private rwlock" in Linux 2.5.12. Then, "[PATCH] err1-40: sysvfs locking fix" in Linux 2.6.8 fixed the former bug by moving pointers_lock lock to the callers, but instead introduced a "sb_bread() with read_lock(&pointers_lock)" bug (which made this problem easier to hit). Al Viro suggested that why not to do like get_branch()/get_block()/ find_shared() in Minix filesystem does. And doing like that is almost a revert of "[PATCH] err1-40: sysvfs locking fix" except that get_branch() from with find_shared() is called without write_lock(&pointers_lock).

References

NVD — CVE-2023-52699 NVD
https://nvd.nist.gov/vuln/detail/CVE-2023-52699
cert-portal.siemens.com/productcert/html/ss... WEB
https://cert-portal.siemens.com/productcert/html/ssa-398330.html
git.kernel.org/stable/c/13b33feb2e... WEB
https://git.kernel.org/stable/c/13b33feb2ebddc2b1aa607f553566b18a4af1d76
git.kernel.org/stable/c/1b4fe801b5... WEB
https://git.kernel.org/stable/c/1b4fe801b5bedec2b622ddb18e5c9bf26c63d79f
git.kernel.org/stable/c/53cb1e52c9... WEB
https://git.kernel.org/stable/c/53cb1e52c9db618c08335984d1ca80db220ccf09
git.kernel.org/stable/c/674c1c4229... WEB
https://git.kernel.org/stable/c/674c1c4229e743070e09db63a23442950ff000d1
git.kernel.org/stable/c/89e8524135... WEB
https://git.kernel.org/stable/c/89e8524135a3902e7563a5a59b7b5ec1bf4904ac
git.kernel.org/stable/c/a692242237... WEB
https://git.kernel.org/stable/c/a69224223746ab96d43e5db9d22d136827b7e2d3
git.kernel.org/stable/c/f123dc8638... WEB
https://git.kernel.org/stable/c/f123dc86388cb669c3d6322702dc441abc35c31e
git.kernel.org/stable/c/fd203d2c67... WEB
https://git.kernel.org/stable/c/fd203d2c671bdee9ab77090ff394d3b71b627927
lists.debian.org/debian-lts-announce... WEB
https://lists.debian.org/debian-lts-announce/2024/06/msg00017.html
lists.debian.org/debian-lts-announce... WEB
https://lists.debian.org/debian-lts-announce/2024/06/msg00020.html

Frequently Asked Questions

What is CVE-2023-52699?
CVE-2023-52699 is a security vulnerability in Software classified as a security vulnerability vulnerability under CWE-667: Improper Locking.
Which Software versions are affected?
Affected versions include releases prior to current release patches.
What version fixes CVE-2023-52699?
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-52699?
CVE-2023-52699 has a CVSS v3.1 base score of 5.3 (MODERATE) with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L.
What CWE is associated with CVE-2023-52699?
CVE-2023-52699 is classified under CWE-667: Improper Locking (The product does not properly acquire or release a lock on a resource, leading to unexpected resource state changes and behaviors.).
How can I check Maven dependencies for CVE-2023-52699?
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-29pq-gr25-8674",
  "modified" : "2026-10-15T03:33:35Z",
  "published" : "2024-05-19T12:30:38Z",
  "aliases" : [ "CVE-2023-52699" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nsysv: don't call sb_bread() with pointers_lock held\n\nsyzbot is reporting sleep in atomic context in SysV filesystem [1], for\nsb_bread() is called with rw_spinlock held.\n\nA \"write_lock(&pointers_lock) => read_lock(&pointers_lock) deadlock\" bug\nand a \"sb_bread() with write_lock(&pointers_lock)\" bug were introduced by\n\"Replace BKL for chain locking with sysvfs-private rwlock\" in Linux 2.5.12.\n\nThen, \"[PATCH] err1-40: sysvfs locking fix\" in Linux 2.6.8 fixed the\nformer bug by moving pointers_lock lock to the callers, but instead\nintroduced a \"sb_bread() with read_lock(&pointers_lock)\" bug (which made\nthis problem easier to hit).\n\nAl Viro suggested that why not to do like get_branch()/get_block()/\nfind_shared() in Minix filesystem does. And doing like that is almost a\nrevert of \"[PATCH] err1-40: sysvfs locking fix\" except that get_branch()\n from with find_shared() is called without write_lock(&pointers_lock).",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L"
  } ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2023-52699"
  }, {
    "type" : "WEB",
    "url" : "https://cert-portal.siemens.com/productcert/html/ssa-398330.html"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/13b33feb2ebddc2b1aa607f553566b18a4af1d76"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/1b4fe801b5bedec2b622ddb18e5c9bf26c63d79f"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/53cb1e52c9db618c08335984d1ca80db220ccf09"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/674c1c4229e743070e09db63a23442950ff000d1"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/89e8524135a3902e7563a5a59b7b5ec1bf4904ac"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/a69224223746ab96d43e5db9d22d136827b7e2d3"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/f123dc86388cb669c3d6322702dc441abc35c31e"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/fd203d2c671bdee9ab77090ff394d3b71b627927"
  }, {
    "type" : "WEB",
    "url" : "https://lists.debian.org/debian-lts-announce/2024/06/msg00017.html"
  }, {
    "type" : "WEB",
    "url" : "https://lists.debian.org/debian-lts-announce/2024/06/msg00020.html"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-667" ],
    "severity" : "MODERATE",
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2024-05-19T11:15:47Z"
  }
}