CVE-2024-50195: Software Security Vulnerability Vulnerability

MODERATE
Advisory Identifier: GHSA-v787-c3f2-p88r
Share
CVSS 5.5
CWE-754
Published
Advisory Summary

CVE-2024-50195 is a MODERATE (CVSS 5.5) security vulnerability vulnerability (CWE-754: Improper Check for Unusual or Exceptional Conditions) affecting Software libraries in the Maven ecosystem. The weakness occurs when the product does not check or incorrectly checks for unusual or exceptional conditions that are not expected to occur frequently during day to day operation of the product.. Remediation is available in the latest vendor maintenance releases.

CVE-2024-50195 at a Glance

CVE Identifier CVE-2024-50195
GHSA Identifier GHSA-v787-c3f2-p88r
Severity MODERATE
CVSS v3.1 Base Score 5.5
CWE Classification CWE-754: Improper Check for Unusual or Exceptional Conditions
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-2024-50195

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-50195, 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-754: Improper Check for Unusual or Exceptional Conditions, where the product does not check or incorrectly checks for unusual or exceptional conditions that are not expected to occur frequently during day to day operation of the product. 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: posix-clock: Fix missing timespec64 check in pc_clock_settime() As Andrew pointed out, it will make sense that the PTP core checked timespec64 struct's tv_sec and tv_nsec range before calling ptp->info->settime64(). As the man manual of clock_settime() said, if tp.tv_sec is negative or tp.tv_nsec is outside the range [0..999,999,999], it should return EINVAL, which include dynamic clocks which handles PTP clock, and the condition is consistent with timespec64_valid(). As Thomas suggested, timespec64_valid() only check the timespec is valid, but not ensure that the time is in a valid range, so check it ahead using timespec64_valid_strict() in pc_clock_settime() and return -EINVAL if not valid. There are some drivers that use tp->tv_sec and tp->tv_nsec directly to write registers without validity checks and assume that the higher layer has checked it, which is dangerous and will benefit from this, such as hclge_ptp_settime(), igb_ptp_settime_i210(), _rcar_gen4_ptp_settime(), and some drivers can remove the checks of itself.

References

NVD — CVE-2024-50195 NVD
https://nvd.nist.gov/vuln/detail/CVE-2024-50195
git.kernel.org/stable/c/1ff7247101... WEB
https://git.kernel.org/stable/c/1ff7247101af723731ea42ed565d54fb8f341264
git.kernel.org/stable/c/27abbde44b... WEB
https://git.kernel.org/stable/c/27abbde44b6e71ee3891de13e1a228aa7ce95bfe
git.kernel.org/stable/c/29f085345c... WEB
https://git.kernel.org/stable/c/29f085345cde24566efb751f39e5d367c381c584
git.kernel.org/stable/c/673a1c5a29... WEB
https://git.kernel.org/stable/c/673a1c5a2998acbd429d6286e6cad10f17f4f073
git.kernel.org/stable/c/a3f169e398... WEB
https://git.kernel.org/stable/c/a3f169e398215e71361774d13bf91a0101283ac2
git.kernel.org/stable/c/c8789fbe2b... WEB
https://git.kernel.org/stable/c/c8789fbe2bbf75845e45302cba6ffa44e1884d01
git.kernel.org/stable/c/d8794ac20a... WEB
https://git.kernel.org/stable/c/d8794ac20a299b647ba9958f6d657051fc51a540
git.kernel.org/stable/c/e0c966bd3e... WEB
https://git.kernel.org/stable/c/e0c966bd3e31911b57ef76cec4c5796ebd88e512
lists.debian.org/debian-lts-announce... WEB
https://lists.debian.org/debian-lts-announce/2025/01/msg00001.html
lists.debian.org/debian-lts-announce... WEB
https://lists.debian.org/debian-lts-announce/2025/03/msg00002.html

Frequently Asked Questions

What is CVE-2024-50195?
CVE-2024-50195 is a security vulnerability in Software classified as a security vulnerability vulnerability under CWE-754: Improper Check for Unusual or Exceptional Conditions.
Which Software versions are affected?
Affected versions include releases prior to current release patches.
What version fixes CVE-2024-50195?
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-50195?
CVE-2024-50195 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-2024-50195?
CVE-2024-50195 is classified under CWE-754: Improper Check for Unusual or Exceptional Conditions (The product does not check or incorrectly checks for unusual or exceptional conditions that are not expected to occur frequently during day to day operation of the product.).
How can I check Maven dependencies for CVE-2024-50195?
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-v787-c3f2-p88r",
  "modified" : "2025-11-04T00:31:57Z",
  "published" : "2024-11-08T06:30:49Z",
  "aliases" : [ "CVE-2024-50195" ],
  "details" : "In the Linux kernel, the following vulnerability has been resolved:\n\nposix-clock: Fix missing timespec64 check in pc_clock_settime()\n\nAs Andrew pointed out, it will make sense that the PTP core\nchecked timespec64 struct's tv_sec and tv_nsec range before calling\nptp->info->settime64().\n\nAs the man manual of clock_settime() said, if tp.tv_sec is negative or\ntp.tv_nsec is outside the range [0..999,999,999], it should return EINVAL,\nwhich include dynamic clocks which handles PTP clock, and the condition is\nconsistent with timespec64_valid(). As Thomas suggested, timespec64_valid()\nonly check the timespec is valid, but not ensure that the time is\nin a valid range, so check it ahead using timespec64_valid_strict()\nin pc_clock_settime() and return -EINVAL if not valid.\n\nThere are some drivers that use tp->tv_sec and tp->tv_nsec directly to\nwrite registers without validity checks and assume that the higher layer\nhas checked it, which is dangerous and will benefit from this, such as\nhclge_ptp_settime(), igb_ptp_settime_i210(), _rcar_gen4_ptp_settime(),\nand some drivers can remove the checks of itself.",
  "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-2024-50195"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/1ff7247101af723731ea42ed565d54fb8f341264"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/27abbde44b6e71ee3891de13e1a228aa7ce95bfe"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/29f085345cde24566efb751f39e5d367c381c584"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/673a1c5a2998acbd429d6286e6cad10f17f4f073"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/a3f169e398215e71361774d13bf91a0101283ac2"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/c8789fbe2bbf75845e45302cba6ffa44e1884d01"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/d8794ac20a299b647ba9958f6d657051fc51a540"
  }, {
    "type" : "WEB",
    "url" : "https://git.kernel.org/stable/c/e0c966bd3e31911b57ef76cec4c5796ebd88e512"
  }, {
    "type" : "WEB",
    "url" : "https://lists.debian.org/debian-lts-announce/2025/01/msg00001.html"
  }, {
    "type" : "WEB",
    "url" : "https://lists.debian.org/debian-lts-announce/2025/03/msg00002.html"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-754" ],
    "severity" : "MODERATE",
    "github_reviewed" : false,
    "github_reviewed_at" : null,
    "nvd_published_at" : "2024-11-08T06:15:16Z"
  }
}