{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-22180 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-22180 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-22180 is a high-severity denial of service vulnerability in Juniper Junos, published on 19 Jan 2022. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-22180 and fix it if it is affected.\n\nWhat it is: CVE-2022-22180 is a high-severity denial of service vulnerability in Juniper Junos, published on 19 Jan 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2022-22180 in the wild and no public exploit code.\n\nAffected product: Juniper Junos. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2022-22180/ (Markdown: https://insights.sbomify.com/CVE-2022-22180/index.md)","id":"CVE-2022-22180","markdown":"https://insights.sbomify.com/CVE-2022-22180/index.md","name":"CVE-2022-22180","record":{"aliases":["GHSA-3jvq-22jp-22pp"],"analysis":{"component_type":"network_device","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Juniper EX Series switch","requires_auth":"none","summary":"Attackers can cause a denial of service on Juniper EX Series switches by sending specific IPv6 packets that exhaust DMA memory.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"juniper","cpe":[{"product":"junos","vendor":"juniper"}],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-754","name":"Improper Check for Unusual or Exceptional Conditions"}],"description":"An Improper Check for Unusual or Exceptional Conditions vulnerability in the processing of specific IPv6 packets on certain EX Series devices may lead to exhaustion of DMA memory causing a Denial of Service (DoS). Over time, exploitation of this vulnerability may cause traffic to stop being forwarded, or a crash of the fxpc process. An indication of the issue occurring may be observed through the following log messages: Sep 13 17:14:59 hostname : %PFE-3: fpc0 (buf alloc) failed allocating packet buffer Sep 13 17:14:59 hostname : %PFE-7: fpc0 brcm_pkt_buf_alloc:393 (buf alloc) failed allocating packet buffer When Packet DMA heap utilization reaches 99%, the system will become unstable. Packet DMA heap utilization can be monitored using the command: user@junos# request pfe execute target fpc0 timeout 30 command \"show heap\" ID Base Total(b) Free(b) Used(b) % Name -- ---------- ----------- ----------- ----------- --- ----------- 0 213301a8 536870488 387228840 149641648 27 Kernel 1 91800000 8388608 3735120 4653488 55 DMA 2 92000000 75497472 74452192 1045280 1 PKT DMA DESC 3 d330000 335544320 257091400 78452920 23 Bcm_sdk 4 96800000 184549376 2408 184546968 99 Packet DMA \u003c\u003c\u003c\u003c 5 903fffe0 20971504 20971504 0 0 Blob This issue affects: Juniper Networks Junos OS 18.4 versions prior to 18.4R2-S10, 18.4R3-S10 on EX2300 Series, EX2300-MP Series, EX3400 Series; 19.1 versions prior to 19.1R3-S7 on EX2300 Series, EX2300-MP Series, EX3400 Series; 19.2 versions prior to 19.2R1-S8, 19.2R3-S4 on EX2300 Series, EX2300-MP Series, EX3400 Series; 19.3 versions prior to 19.3R3-S5 on EX2300 Series, EX2300-MP Series, EX3400 Series; 19.4 versions prior to 19.4R3-S7 on EX2300 Series, EX2300-MP Series, EX3400 Series; 20.1 versions prior to 20.1R3-S3 on EX2300 Series, EX2300-MP Series, EX3400 Series; 20.2 versions prior to 20.2R3-S3 on EX2300 Series, EX2300-MP Series, EX3400 Series; 20.3 versions prior to 20.3R3-S2 on EX2300 Series, EX2300-MP Series, EX3400 Series; 20.4 versions prior to 20.4R3-S1 on EX2300 Series, EX2300-MP Series, EX3400 Series; 21.1 versions prior to 21.1R2-S2, 21.1R3 on EX2300 Series, EX2300-MP Series, EX3400 Series; 21.2 versions prior to 21.2R1-S2, 21.2R2 on EX2300 Series, EX2300-MP Series, EX3400 Series; 21.3 versions prior to 21.3R1-S1, 21.3R2 on EX2300 Series, EX2300-MP Series, EX3400 Series.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Junos OS: EX2300 Series, EX2300-MP Series, EX3400 Series: A slow memory leak due to processing of specific IPv6 packets","id":"CVE-2022-22180","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"juniper:junos","products":["juniper:junos"],"type":"denial_of_service","year":"2022"},"n_packages":0,"n_references":1,"next":{"headline":"Junos OS: J-Web can be compromised through reflected XSS attacks","id":"CVE-2022-22181"},"packages":[],"prev":{"headline":"Junos OS: jdhcpd crashes upon receiving a specific DHCP packet","id":"CVE-2022-22179"},"products":["Junos OS"],"published":"2022-01-19","related":[{"cvss_score":9.8,"headline":"Juniper Junos OS EX Series and SRX Series PHP External Variable Modification","id":"CVE-2023-36845","kev_date_added":"2023-11-13","published":"2023-08-17"},{"cvss_score":8.8,"headline":"Juniper Junos OS Path Traversal","id":"CVE-2020-1631","kev_date_added":"2022-03-25","published":"2020-05-04"},{"cvss_score":6.7,"headline":"Juniper Junos OS Improper Isolation or Compartmentalization","id":"CVE-2025-21590","kev_date_added":"2025-03-13","published":"2025-03-12"},{"cvss_score":5.3,"headline":"Juniper Junos OS SRX Series Missing Authentication for Critical Function","id":"CVE-2023-36851","kev_date_added":"2023-11-13","published":"2023-09-26"},{"cvss_score":5.3,"headline":"Juniper Junos OS EX Series PHP External Variable Modification","id":"CVE-2023-36844","kev_date_added":"2023-11-13","published":"2023-08-17"},{"cvss_score":5.3,"headline":"Juniper Junos OS SRX Series Missing Authentication for Critical Function","id":"CVE-2023-36846","kev_date_added":"2023-11-13","published":"2023-08-17"},{"cvss_score":5.3,"headline":"Juniper Junos OS EX Series Missing Authentication for Critical Function","id":"CVE-2023-36847","kev_date_added":"2023-11-13","published":"2023-08-17"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-09-17","vendors":["Juniper Networks"]},"summary":"Attackers can cause a denial of service on Juniper EX Series switches by sending specific IPv6 packets that exhaust DMA memory.","url":"https://insights.sbomify.com/CVE-2022-22180/"}