CVE-2022-22215

Junos OS and Junos OS Evolved: /var/run/<pid>.env files are potentially not deleted during termination of a gRPC connection causing inode exhaustion

MEDIUM
5.5
CVSS Score
Published: July 20, 2022 at 02:15 PM UTC
Updated: June 17, 2026 at 04:28 AM UTC
3 products affected across 2 vendorsJunosJunos OS EvolvedJunos OS Evolved

Using Junos OS by Juniper Networks?

Get instant alerts when new vulnerabilities affect Junos OS - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM5.5
Exploit prediction
EPSS 0.6%

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/<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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Affected range stops below 20.4, so it looks safe — our inference, not a vendor statement
Affected range stops below 19.1, so it looks safe — our inference, not a vendor statement
Affected range stops below 19.1R3-S8, so it looks safe — our inference, not a vendor statement
Affected range stops below 19.2R3-S6, so it looks safe — our inference, not a vendor statement
Affected range stops below 19.3R3-S5, so it looks safe — our inference, not a vendor statement
Affected range stops below 19.4R2-S6, 19.4R3-S7, so it looks safe — our inference, not a vendor statement
Affected range stops below 20.1*, so it looks safe — our inference, not a vendor statement
Affected range stops below 20.2R3-S5, so it looks safe — our inference, not a vendor statement
Affected range stops below 20.3R3-S4, so it looks safe — our inference, not a vendor statement
Affected range stops below 20.4R3, so it looks safe — our inference, not a vendor statement
Affected range stops below 21.1R3, so it looks safe — our inference, not a vendor statement
Affected range stops below 21.2R2, so it looks safe — our inference, not a vendor statement
v < 20.4R3-EVO21.1 ≤ v < 21.1R3-S1-EVO21.2 ≤ v < 21.2R1-S1-EVO, 21.2R2-EVO21.121.2
Affected range stops below 20.4R3-EVO, so it looks safe — our inference, not a vendor statement
Affected range stops below 21.1R3-S1-EVO, so it looks safe — our inference, not a vendor statement
Affected range stops below 21.2R1-S1-EVO, 21.2R2-EVO, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

Patch and advisory references

References (1)

x_refsource_CONFIRMExploitVendor Advisory
https://kb.juniper.net/JSA69719

CVSS

Attack Vector
LOCAL
Complexity
LOW
Privileges
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
NONE
Availability
HIGH
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-772

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card