CVE-2024-43882: Software Security Vulnerability Vulnerability

HIGH
Advisory Identifier: GHSA-gpj2-qxrh-r55r
Share
CVSS 7.0
CWE-367
Published
Advisory Summary

CVE-2024-43882 is a HIGH (CVSS 7.0) security vulnerability vulnerability (CWE-367: Time-of-check Time-of-use (TOCTOU) Race Condition) affecting Software libraries in the Maven ecosystem. The weakness occurs when the product checks the state of a resource before using that resource, but the resource's state can change between the check and the use in a way that invalidates the results of the check.. Remediation is available in the latest vendor maintenance releases.

CVE-2024-43882 at a Glance

CVE Identifier CVE-2024-43882
GHSA Identifier GHSA-gpj2-qxrh-r55r
Severity HIGH
CVSS v3.1 Base Score 7.0
CWE Classification CWE-367: Time-of-check Time-of-use (TOCTOU) Race Condition
Affected Product Software
Package Ecosystem Maven
Published Date
Last Updated

Security Impact

CVSS: 7.0

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

Attack Vector Local (AV:L)
Attack Complexity High (AC:H)
Privileges Required Low (PR:L)
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-2024-43882

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-2024-43882, 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-367: Time-of-check Time-of-use (TOCTOU) Race Condition, where the product checks the state of a resource before using that resource, but the resource's state can change between the check and the use in a way that invalidates the results of the check. 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: exec: Fix ToCToU between perm check and set-uid/gid usage When opening a file for exec via do_filp_open(), permission checking is done against the file's metadata at that moment, and on success, a file pointer is passed back. Much later in the execve() code path, the file metadata (specifically mode, uid, and gid) is used to determine if/how to set the uid and gid. However, those values may have changed since the permissions check, meaning the execution may gain unintended privileges. For example, if a file could change permissions from executable and not set-id: ---------x 1 root root 16048 Aug 7 13:16 target to set-id and non-executable: ---S------ 1 root root 16048 Aug 7 13:16 target it is possible to gain root privileges when execution should have been disallowed. While this race condition is rare in real-world scenarios, it has been observed (and proven exploitable) when package managers are updating the setuid bits of installed programs. Such files start with being world-executable but then are adjusted to be group-exec with a set-uid bit. For example, "chmod o-x,u+s target" makes "target" executable only by uid "root" and gid "cdrom", while also becoming setuid-root: -rwxr-xr-x 1 root cdrom 16048 Aug 7 13:16 target becomes: -rwsr-xr-- 1 root cdrom 16048 Aug 7 13:16 target But racing the chmod means users without group "cdrom" membership can get the permission to execute "target" just before the chmod, and when the chmod finishes, the exec reaches brpm_fill_uid(), and performs the setuid to root, violating the expressed authorization of "only cdrom group members can setuid to root". Re-check that we still have execute permissions in case the metadata has changed. It would be better to keep a copy from the perm-check time, but until we can do that refactoring, the least-bad option is to do a full inode_permission() call (under inode lock). It is understood that this is safe against dead-locks, but hardly optimal.

References

NVD — CVE-2024-43882 NVD
https://nvd.nist.gov/vuln/detail/CVE-2024-43882
cert-portal.siemens.com/productcert/html/ss... WEB
https://cert-portal.siemens.com/productcert/html/ssa-265688.html
cert-portal.siemens.com/productcert/html/ss... WEB
https://cert-portal.siemens.com/productcert/html/ssa-355557.html
cert-portal.siemens.com/productcert/html/ss... WEB
https://cert-portal.siemens.com/productcert/html/ssa-613116.html
git.kernel.org/stable/c/15469d46ba... WEB
https://git.kernel.org/stable/c/15469d46ba34559bfe7e3de6659115778c624759
git.kernel.org/stable/c/368f6985d4... WEB
https://git.kernel.org/stable/c/368f6985d46657b8b466a421dddcacd4051f7ada
git.kernel.org/stable/c/90dfbba89a... WEB
https://git.kernel.org/stable/c/90dfbba89ad4f0d9c9744ecbb1adac4aa2ff4f3e
git.kernel.org/stable/c/9b424c5d41... WEB
https://git.kernel.org/stable/c/9b424c5d4130d56312e2a3be17efb0928fec4d64
git.kernel.org/stable/c/d2a2a4714d... WEB
https://git.kernel.org/stable/c/d2a2a4714d80d09b0f8eb6438ab4224690b7121e
git.kernel.org/stable/c/d5c3c7e262... WEB
https://git.kernel.org/stable/c/d5c3c7e26275a2d83b894d30f7582a42853a958f
git.kernel.org/stable/c/f50733b45d... WEB
https://git.kernel.org/stable/c/f50733b45d865f91db90919f8311e2127ce5a0cb
git.kernel.org/stable/c/f6cfc6bcfd... WEB
https://git.kernel.org/stable/c/f6cfc6bcfd5e1cf76115b6450516ea4c99897ae1
lists.debian.org/debian-lts-announce... WEB
https://lists.debian.org/debian-lts-announce/2024/10/msg00003.html
lists.debian.org/debian-lts-announce... WEB
https://lists.debian.org/debian-lts-announce/2025/01/msg00001.html

Frequently Asked Questions

What is CVE-2024-43882?
CVE-2024-43882 is a security vulnerability in Software classified as a security vulnerability vulnerability under CWE-367: Time-of-check Time-of-use (TOCTOU) Race Condition.
Which Software versions are affected?
Affected versions include releases prior to current release patches.
What version fixes CVE-2024-43882?
Upgrading to current release patches (or the latest patched release for your respective branch) resolves the vulnerability.
What is the CVSS score of CVE-2024-43882?
CVE-2024-43882 has a CVSS v3.1 base score of 7.0 (HIGH) with vector string CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H.
What CWE is associated with CVE-2024-43882?
CVE-2024-43882 is classified under CWE-367: Time-of-check Time-of-use (TOCTOU) Race Condition (The product checks the state of a resource before using that resource, but the resource's state can change between the check and the use in a way that invalidates the results of the check.).
How can I check Maven dependencies for CVE-2024-43882?
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-gpj2-qxrh-r55r",
  "modified" : "2026-05-12T12:32:05Z",
  "published" : "2024-08-21T03:31:53Z",
  "aliases" : [ "CVE-2024-43882" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nexec: Fix ToCToU between perm check and set-uid/gid usage\n\nWhen opening a file for exec via do_filp_open(), permission checking is\ndone against the file's metadata at that moment, and on success, a file\npointer is passed back. Much later in the execve() code path, the file\nmetadata (specifically mode, uid, and gid) is used to determine if/how\nto set the uid and gid. However, those values may have changed since the\npermissions check, meaning the execution may gain unintended privileges.\n\nFor example, if a file could change permissions from executable and not\nset-id:\n\n---------x 1 root root 16048 Aug  7 13:16 target\n\nto set-id and non-executable:\n\n---S------ 1 root root 16048 Aug  7 13:16 target\n\nit is possible to gain root privileges when execution should have been\ndisallowed.\n\nWhile this race condition is rare in real-world scenarios, it has been\nobserved (and proven exploitable) when package managers are updating\nthe setuid bits of installed programs. Such files start with being\nworld-executable but then are adjusted to be group-exec with a set-uid\nbit. For example, \"chmod o-x,u+s target\" makes \"target\" executable only\nby uid \"root\" and gid \"cdrom\", while also becoming setuid-root:\n\n-rwxr-xr-x 1 root cdrom 16048 Aug  7 13:16 target\n\nbecomes:\n\n-rwsr-xr-- 1 root cdrom 16048 Aug  7 13:16 target\n\nBut racing the chmod means users without group \"cdrom\" membership can\nget the permission to execute \"target\" just before the chmod, and when\nthe chmod finishes, the exec reaches brpm_fill_uid(), and performs the\nsetuid to root, violating the expressed authorization of \"only cdrom\ngroup members can setuid to root\".\n\nRe-check that we still have execute permissions in case the metadata\nhas changed. It would be better to keep a copy from the perm-check time,\nbut until we can do that refactoring, the least-bad option is to do a\nfull inode_permission() call (under inode lock). It is understood that\nthis is safe against dead-locks, but hardly optimal.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H"
  } ],
  "affected" : [ ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2024-43882"
  }, {
    "type" : "WEB",
    "url" : "https://cert-portal.siemens.com/productcert/html/ssa-265688.html"
  }, {
    "type" : "WEB",
    "url" : "https://cert-portal.siemens.com/productcert/html/ssa-355557.html"
  }, {
    "type" : "WEB",
    "url" : "https://cert-portal.siemens.com/productcert/html/ssa-613116.html"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/15469d46ba34559bfe7e3de6659115778c624759"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/368f6985d46657b8b466a421dddcacd4051f7ada"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/90dfbba89ad4f0d9c9744ecbb1adac4aa2ff4f3e"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/9b424c5d4130d56312e2a3be17efb0928fec4d64"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/d2a2a4714d80d09b0f8eb6438ab4224690b7121e"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/d5c3c7e26275a2d83b894d30f7582a42853a958f"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/f50733b45d865f91db90919f8311e2127ce5a0cb"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/f6cfc6bcfd5e1cf76115b6450516ea4c99897ae1"
  }, {
    "type" : "WEB",
    "url" : "https://lists.debian.org/debian-lts-announce/2024/10/msg00003.html"
  }, {
    "type" : "WEB",
    "url" : "https://lists.debian.org/debian-lts-announce/2025/01/msg00001.html"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-367" ],
    "severity" : "HIGH",
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2024-08-21T01:15:12Z"
  }
}