ghsa-9j54-8gmh-m2jr
Vulnerability from github
Published
2024-07-11 00:32
Modified
2024-07-11 00:32
Details

A Heap-based Buffer Overflow vulnerability in the telemetry sensor process (sensord) of Juniper Networks Junos OS on MX240, MX480, MX960 platforms using MPC10E causes a steady increase in memory utilization, ultimately leading to a Denial of Service (DoS).

When the device is subscribed to a specific subscription on Junos Telemetry Interface, a slow memory leak occurs and eventually all resources are consumed and the device becomes unresponsive. A manual reboot of the Line Card will be required to restore the device to its normal functioning. 

This issue is only seen when telemetry subscription is active.

The Heap memory utilization can be monitored using the following command:   > show system processes extensive

The following command can be used to monitor the memory utilization of the specific sensor   > show system info | match sensord PID NAME MEMORY PEAK MEMORY %CPU THREAD-COUNT CORE-AFFINITY UPTIME

1986 sensord 877.57MB 877.57MB 2 4 0,2-15 7-21:41:32

This issue affects Junos OS: 

  • from 21.2R3-S5 before 21.2R3-S7, 
  • from 21.4R3-S4 before 21.4R3-S6, 
  • from 22.2R3 before 22.2R3-S4, 
  • from 22.3R2 before 22.3R3-S2, 
  • from 22.4R1 before 22.4R3, 
  • from 23.2R1 before 23.2R2.
Show details on source website


{
  "affected": [],
  "aliases": [
    "CVE-2024-39518"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-122"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2024-07-10T23:15:11Z",
    "severity": "HIGH"
  },
  "details": "A Heap-based Buffer Overflow vulnerability in the telemetry sensor process (sensord) of Juniper Networks Junos OS on MX240, MX480, MX960 platforms using MPC10E causes a steady increase in memory utilization, ultimately leading to a Denial of Service (DoS).\n\nWhen the device is subscribed to a specific subscription on Junos Telemetry Interface, a slow memory leak occurs and eventually all resources are consumed and the device becomes unresponsive. A manual reboot of the Line Card will be required to restore the device to its normal functioning.\u00a0\n\nThis issue is only seen when telemetry subscription is active.\n\nThe Heap memory utilization can be monitored using the following command:\n\u00a0 \u003e show system processes extensive\n\nThe following command can be used to monitor the memory utilization of the specific sensor\n\u00a0 \u003e show system info | match sensord\n   PID   NAME                 MEMORY     PEAK MEMORY    %CPU   THREAD-COUNT CORE-AFFINITY   UPTIME\n\n   1986  sensord            877.57MB   877.57MB         2       4           0,2-15          7-21:41:32\n\n\nThis issue affects Junos OS:\u00a0\n\n\n\n  *  from 21.2R3-S5 before 21.2R3-S7,\u00a0\n  *  from 21.4R3-S4 before 21.4R3-S6,\u00a0\n  *  from 22.2R3 before 22.2R3-S4,\u00a0\n  *  from 22.3R2 before 22.3R3-S2,\u00a0\n  *  from 22.4R1 before 22.4R3,\u00a0\n  *  from 23.2R1 before 23.2R2.",
  "id": "GHSA-9j54-8gmh-m2jr",
  "modified": "2024-07-11T00:32:50Z",
  "published": "2024-07-11T00:32:50Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-39518"
    },
    {
      "type": "WEB",
      "url": "https://supportportal.juniper.net/JSA82982"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
      "type": "CVSS_V3"
    },
    {
      "score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:L/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X",
      "type": "CVSS_V4"
    }
  ]
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading...

Loading...

Loading...

Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
  • Confirmed: The vulnerability is confirmed from an analyst perspective.
  • Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
  • Patched: This vulnerability was successfully patched by the user reporting the sighting.
  • Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
  • Not confirmed: The user expresses doubt about the veracity of the vulnerability.
  • Not patched: This vulnerability was not successfully patched by the user reporting the sighting.