{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2022-22172 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-22172 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-22172 is a medium-severity denial of service vulnerability in Juniper Junos, published on 19 Jan 2022. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-22172 and fix it if it is affected.\n\nWhat it is: CVE-2022-22172 is a medium-severity denial of service vulnerability in Juniper Junos, published on 19 Jan 2022. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2022-22172 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-22172/ (Markdown: https://insights.sbomify.com/CVE-2022-22172/index.md)","id":"CVE-2022-22172","markdown":"https://insights.sbomify.com/CVE-2022-22172/index.md","name":"CVE-2022-22172","record":{"aliases":["GHSA-v6f8-xxj7-93g3"],"analysis":{"component_type":"network_device","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Juniper Junos OS","requires_auth":"none","summary":"An unauthenticated adjacent attacker can cause a memory leak in l2cpd via specific LLDP packets, leading to memory exhaustion and denial of service.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"juniper","cpe":[{"product":"junos","vendor":"juniper"},{"product":"junos_os_evolved","vendor":"juniper"}],"cvss":{"score":6.5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-401","name":"Missing Release of Memory after Effective Lifetime"}],"description":"A Missing Release of Memory after Effective Lifetime vulnerability in the Layer-2 control protocols daemon (l2cpd) of Juniper Networks Junos OS and Junos OS Evolved allows an unauthenticated adjacent attacker to cause a memory leak. Continued exploitation can lead to memory exhaustion and thereby a Denial of Service (DoS). This issue occurs when specific LLDP packets are received. The impact of the l2cpd cores is that if any of the stp protocols (rstp, mstp or vstp) is used then stp re-converges and traffic loss will occur during that time. Also if any services depend on LLDP state (like PoE or VoIP device recognition) then these will also be affected. The memory utilization of the L2CPd process can be monitored with the following command: user@host\u003e show system processes extensive | match l2cpd 1234 root 52 0 521M 43412K RUN 1 4:02 34.47% l2cpd This issue affects: Juniper Networks Junos OS 18.4 version 18.4R2-S4 and later versions prior to 18.4R2-S10. 19.2 versions prior to 19.2R1-S8, 19.2R3-S4; 19.3 versions prior to 19.3R3-S5; 19.4 versions prior to 19.4R3-S7; 20.1 versions prior to 20.1R3-S3; 20.2 versions prior to 20.2R3-S2; 20.3 versions prior to 20.3R3-S1; 20.4 versions prior to 20.4R3; 21.1 versions prior to 21.1R2-S2, 21.1R3; 21.2 versions prior to 21.2R2; Juniper Networks Junos OS Evolved All versions prior to 20.4R3-S2-EVO; 21.1 version 21.1R1-EVO and later versions; 21.2 versions prior to 21.2R2-EVO. This issue does not affect: Juniper Networks Junos OS 19.1 version 19.1R1 and later versions.","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 and Junos OS Evolved: An l2cpd memory leak can occur when specific LLDP packets are received leading to a DoS","id":"CVE-2022-22172","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"juniper:junos","products":["juniper:junos","juniper:junos_os_evolved"],"type":"denial_of_service","year":"2022"},"n_packages":0,"n_references":1,"next":{"headline":"Junos OS: CRL failing to download causes a memory leak and ultimately a DoS","id":"CVE-2022-22173"},"packages":[],"prev":{"headline":"Junos OS: Specific packets over VXLAN cause FPC reset","id":"CVE-2022-22171"},"products":["Junos OS","Junos OS Evolved"],"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-16","vendors":["Juniper Networks"]},"summary":"An unauthenticated adjacent attacker can cause a memory leak in l2cpd via specific LLDP packets, leading to memory exhaustion and denial of service.","url":"https://insights.sbomify.com/CVE-2022-22172/"}