{"containers":{"cna":{"affected":[{"product":"Junos OS","vendor":"Juniper Networks","versions":[{"lessThan":"19.1R3-S8","status":"affected","version":"unspecified","versionType":"custom"},{"lessThan":"19.2R3-S6","status":"affected","version":"19.2","versionType":"custom"},{"lessThan":"19.3R3-S5","status":"affected","version":"19.3","versionType":"custom"},{"lessThan":"19.4R2-S6, 19.4R3-S7","status":"affected","version":"19.4","versionType":"custom"},{"lessThan":"20.1*","status":"affected","version":"20.1R1","versionType":"custom"},{"lessThan":"20.2R3-S5","status":"affected","version":"20.2","versionType":"custom"},{"lessThan":"20.3R3-S4","status":"affected","version":"20.3","versionType":"custom"},{"lessThan":"20.4R3","status":"affected","version":"20.4","versionType":"custom"},{"lessThan":"21.1R3","status":"affected","version":"21.1","versionType":"custom"},{"lessThan":"21.2R2","status":"affected","version":"21.2","versionType":"custom"}]},{"product":"Junos OS Evolved","vendor":"Juniper Networks","versions":[{"lessThan":"20.4R3-EVO","status":"affected","version":"unspecified","versionType":"custom"},{"lessThan":"21.1R3-S1-EVO","status":"affected","version":"21.1","versionType":"custom"},{"lessThan":"21.2R1-S1-EVO, 21.2R2-EVO","status":"affected","version":"21.2","versionType":"custom"}]}],"configurations":[{"lang":"en","value":"To be affected by this issue the system needs to be configured for gRPC:\n\n  [ system services extension-service request-response grpc ]"}],"datePublic":"2022-07-13T00:00:00.000Z","descriptions":[{"lang":"en","value":"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/<pid>.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 <pid> (<process>), uid <uid> inumber <number> on /.mount/var: out of inodes which by itself is a clear indication. 2. The following log message can be observed: host <process>[<pid>]: ... : 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> 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> file list /var/run/*.env | count need to be checked and if it indicates a high (>10000) 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."}],"exploits":[{"lang":"en","value":"Juniper SIRT is not aware of any malicious exploitation of this vulnerability."}],"metrics":[{"cvssV3_1":{"attackComplexity":"LOW","attackVector":"NETWORK","availabilityImpact":"HIGH","baseScore":6.5,"baseSeverity":"MEDIUM","confidentialityImpact":"NONE","integrityImpact":"NONE","privilegesRequired":"LOW","scope":"UNCHANGED","userInteraction":"NONE","vectorString":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","version":"3.1"}}],"problemTypes":[{"descriptions":[{"description":"775","lang":"en","type":"text"}]},{"descriptions":[{"description":"Denial of Service (DoS)","lang":"en","type":"text"}]}],"providerMetadata":{"dateUpdated":"2022-07-20T14:15:37.000Z","orgId":"8cbe9d5a-a066-4c94-8978-4b15efeae968","shortName":"juniper"},"references":[{"tags":["x_refsource_CONFIRM"],"url":"https://kb.juniper.net/JSA69719"}],"solutions":[{"lang":"en","value":"The following software releases have been updated to resolve this specific issue: \nJunos OS: 19.1R3-S8, 19.2R3-S6, 19.3R3-S5, 19.4R2-S6, 19.4R3-S7, 20.2R3-S5, 20.3R3-S4, 20.4R3, 21.1R3, 21.2R2, 21.3R1, and all subsequent releases;\nJunos OS Evolved: 20.4R3-EVO, 21.1R3-S1-EVO, 21.2R1-S1-EVO, 21.2R2-EVO, 21.3R1-EVO, and all subsequent releases."}],"source":{"advisory":"JSA69719","defect":["1604157"],"discovery":"USER"},"title":"Junos OS and Junos OS Evolved: /var/run/<pid>.env files are potentially not deleted during termination of a gRPC connection causing inode exhaustion","workarounds":[{"lang":"en","value":"There are no viable workarounds for this issue.\nTo reduce the risk of exploitation use access lists or firewall filters to the device only from trusted, administrative networks or hosts."}],"x_generator":{"engine":"Vulnogram 0.0.9"},"x_legacyV4Record":{"CVE_data_meta":{"ASSIGNER":"sirt@juniper.net","DATE_PUBLIC":"2022-07-13T16:00:00.000Z","ID":"CVE-2022-22215","STATE":"PUBLIC","TITLE":"Junos OS and Junos OS Evolved: /var/run/<pid>.env files are potentially not deleted during termination of a gRPC connection causing inode exhaustion"},"affects":{"vendor":{"vendor_data":[{"product":{"product_data":[{"product_name":"Junos OS","version":{"version_data":[{"version_affected":"<","version_value":"19.1R3-S8"},{"version_affected":"<","version_name":"19.2","version_value":"19.2R3-S6"},{"version_affected":"<","version_name":"19.3","version_value":"19.3R3-S5"},{"version_affected":"<","version_name":"19.4","version_value":"19.4R2-S6, 19.4R3-S7"},{"version_affected":">=","version_name":"20.1","version_value":"20.1R1"},{"version_affected":"<","version_name":"20.2","version_value":"20.2R3-S5"},{"version_affected":"<","version_name":"20.3","version_value":"20.3R3-S4"},{"version_affected":"<","version_name":"20.4","version_value":"20.4R3"},{"version_affected":"<","version_name":"21.1","version_value":"21.1R3"},{"version_affected":"<","version_name":"21.2","version_value":"21.2R2"}]}},{"product_name":"Junos OS Evolved","version":{"version_data":[{"version_affected":"<","version_value":"20.4R3-EVO"},{"version_affected":"<","version_name":"21.1","version_value":"21.1R3-S1-EVO"},{"version_affected":"<","version_name":"21.2","version_value":"21.2R1-S1-EVO, 21.2R2-EVO"}]}}]},"vendor_name":"Juniper Networks"}]}},"configuration":[{"lang":"en","value":"To be affected by this issue the system needs to be configured for gRPC:\n\n  [ system services extension-service request-response grpc ]"}],"data_format":"MITRE","data_type":"CVE","data_version":"4.0","description":{"description_data":[{"lang":"eng","value":"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/<pid>.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 <pid> (<process>), uid <uid> inumber <number> on /.mount/var: out of inodes which by itself is a clear indication. 2. The following log message can be observed: host <process>[<pid>]: ... : 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> 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> file list /var/run/*.env | count need to be checked and if it indicates a high (>10000) 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."}]},"exploit":[{"lang":"en","value":"Juniper SIRT is not aware of any malicious exploitation of this vulnerability."}],"generator":{"engine":"Vulnogram 0.0.9"},"impact":{"cvss":{"attackComplexity":"LOW","attackVector":"NETWORK","availabilityImpact":"HIGH","baseScore":6.5,"baseSeverity":"MEDIUM","confidentialityImpact":"NONE","integrityImpact":"NONE","privilegesRequired":"LOW","scope":"UNCHANGED","userInteraction":"NONE","vectorString":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","version":"3.1"}},"problemtype":{"problemtype_data":[{"description":[{"lang":"eng","value":"775"}]},{"description":[{"lang":"eng","value":"Denial of Service (DoS)"}]}]},"references":{"reference_data":[{"name":"https://kb.juniper.net/JSA69719","refsource":"CONFIRM","url":"https://kb.juniper.net/JSA69719"}]},"solution":[{"lang":"en","value":"The following software releases have been updated to resolve this specific issue: \nJunos OS: 19.1R3-S8, 19.2R3-S6, 19.3R3-S5, 19.4R2-S6, 19.4R3-S7, 20.2R3-S5, 20.3R3-S4, 20.4R3, 21.1R3, 21.2R2, 21.3R1, and all subsequent releases;\nJunos OS Evolved: 20.4R3-EVO, 21.1R3-S1-EVO, 21.2R1-S1-EVO, 21.2R2-EVO, 21.3R1-EVO, and all subsequent releases."}],"source":{"advisory":"JSA69719","defect":["1604157"],"discovery":"USER"},"work_around":[{"lang":"en","value":"There are no viable workarounds for this issue.\nTo reduce the risk of exploitation use access lists or firewall filters to the device only from trusted, administrative networks or hosts."}]}},"adp":[{"providerMetadata":{"orgId":"af854a3a-2127-422b-91ae-364da2661108","shortName":"CVE","dateUpdated":"2024-08-03T03:07:49.902Z"},"title":"CVE Program Container","references":[{"tags":["x_refsource_CONFIRM","x_transferred"],"url":"https://kb.juniper.net/JSA69719"}]}]},"cveMetadata":{"assignerOrgId":"8cbe9d5a-a066-4c94-8978-4b15efeae968","assignerShortName":"juniper","cveId":"CVE-2022-22215","datePublished":"2022-07-20T14:15:37.769Z","dateReserved":"2021-12-21T00:00:00.000Z","dateUpdated":"2024-09-17T01:11:06.894Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.1"}