{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2022-22215 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-22215 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-22215 is a medium-severity denial of service vulnerability in Juniper Junos, published on 20 Jul 2022. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-22215 and fix it if it is affected.\n\nWhat it is: CVE-2022-22215 is a medium-severity denial of service vulnerability in Juniper Junos, published on 20 Jul 2022. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2022-22215 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-22215/ (Markdown: https://insights.sbomify.com/CVE-2022-22215/index.md)","id":"CVE-2022-22215","markdown":"https://insights.sbomify.com/CVE-2022-22215/index.md","name":"CVE-2022-22215","record":{"aliases":["GHSA-g948-gw7m-3495"],"analysis":{"component_type":"network_device","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Juniper Junos OS","requires_auth":"low_privilege","summary":"A local attacker can cause inode exhaustion and denial of service by repeatedly terminating gRPC connections without cleaning up environment files.","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:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-772","name":"Missing Release of Resource after Effective Lifetime"}],"description":"A Missing Release of File Descriptor or Handle after Effective Lifetime vulnerability in plugable authentication module (PAM) of Juniper Networks Junos OS and Junos OS Evolved allows a locally authenticated attacker with low privileges to cause a Denial of Service (DoS). It is possible that after the termination of a gRPC connection the respective/var/run/\u003cpid\u003e.env file is not getting deleted which if occurring repeatedly can cause inode exhaustion. Inode exhaustion can present itself in two different ways: 1. The following log message can be observed: host kernel: pid \u003cpid\u003e (\u003cprocess\u003e), uid \u003cuid\u003e inumber \u003cnumber\u003e on /.mount/var: out of inodes which by itself is a clear indication. 2. The following log message can be observed: host \u003cprocess\u003e[\u003cpid\u003e]: ... : No space left on device which is not deterministic and just a representation of a write error which could have several reasons. So the following check needs to be done: user@host\u003e show system storage no-forwarding Filesystem Size Used Avail Capacity Mounted on /dev/ada1p1 475M 300M 137M 69% /.mount/var which indicates that the write error is not actually due to a lack of disk space. If either 1. or 2. has been confirmed, then the output of: user@host\u003e file list /var/run/*.env | count need to be checked and if it indicates a high (\u003e10000) number of files the system has been affected by this issue. This issue affects: Juniper Networks Junos OS All versions prior to 19.1R3-S8; 19.2 versions prior to 19.2R3-S6; 19.3 versions prior to 19.3R3-S5; 19.4 versions prior to 19.4R2-S6, 19.4R3-S7; 20.1 version 20.1R1 and later versions; 20.2 versions prior to 20.2R3-S5; 20.3 versions prior to 20.3R3-S4; 20.4 versions prior to 20.4R3; 21.1 versions prior to 21.1R3; 21.2 versions prior to 21.2R2. Juniper Networks Junos OS Evolved All versions prior to 20.4R3-EVO; 21.1 versions prior to 21.1R3-S1-EVO; 21.2 versions prior to 21.2R1-S1-EVO, 21.2R2-EVO.","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":"Denial of service in Junos OS","id":"CVE-2022-22215","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: PTX Series and QFX10000 Series: 'Etherleak' memory disclosure in Ethernet padding data","id":"CVE-2022-22216"},"packages":[],"prev":{"headline":"Junos OS and Junos OS Evolved: In an MPLS scenario upon receipt of a specific IPv6 packet an FPC will crash","id":"CVE-2022-22214"},"products":["Junos OS","Junos OS Evolved"],"published":"2022-07-20","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":"A local attacker can cause inode exhaustion and denial of service by repeatedly terminating gRPC connections without cleaning up environment files.","url":"https://insights.sbomify.com/CVE-2022-22215/"}