Junos OS: Incorrect Authorization
CVE-2022-22157 is a critical-severity incorrect authorization vulnerability in Junos OS from Juniper Networks, with a CVSS 3.1 base score of 9.3 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. The record lists versions 18.4R2-S9, 18.4R3-S9, 19.1R2-S3, 19.1R3-S6, 19.2R1-S7, 19.2R3-S3 as the first without the flaw, so updating Junos OS to one of those releases or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.68% chance of exploitation within 30 days, higher than 53% of scored CVEs.
Critical severity: a successful attack would have severe impact.
What to do
- Update Junos OS to 18.4R2-S9, 18.4R3-S9 or 19.1R2-S3, 19.1R3-S6 or 19.2R1-S7, 19.2R3-S3 or 19.3R2-S6, 19.3R3-S2, whichever matches your release line, or a later version.
- Read the advisory on kb.juniper.net for workarounds and exact fixed builds.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Juniper Networks | Junos OS | 18.4 up to, but not including, 18.4R2-S9, 18.4R3-S9; 19.1 up to, but not including, 19.1R2-S3, 19.1R3-S6; 19.2 up to, but not including, 19.2R1-S7, 19.2R3-S3; 19.3 up to, but not including, 19.3R2-S6, 19.3R3-S2; 19.4 up to, but not including, 19.4R2-S5, 19.4R3-S3; 20.1 up to, but not including, 20.1R2-S2, 20.1R3; 20.2 up to, but not including, 20.2R3-S1; 20.3 up to, but not including, 20.3R3; and 2 more ranges | 18.4R2-S9, 18.4R3-S9, 19.1R2-S3, 19.1R3-S6, 19.2R1-S7, 19.2R3-S3, 19.3R2-S6, 19.3R3-S2, 19.4R2-S5, 19.4R3-S3, 20.1R2-S2, 20.1R3 |
| Juniper Networks | Junos | 18.4; 19.1; 19.2; 19.3; 19.4; 20.1; 20.2; 20.3; and 3 more ranges | Not stated |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- ChangedThe attack can reach beyond the vulnerable component into other systems.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- LowLimited modification of data is possible.
- Availability
- NoneAvailability is not affected.
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:L/A:N. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 7.2 | High | CNA (juniper.net) |
| CVSS 3.1 | 9.3 | Critical | NVD |
| CVSS 2.0 | 5.8 | Medium | NVD |
Official description
A traffic classification vulnerability in Juniper Networks Junos OS on the SRX Series Services Gateways may allow an attacker to bypass Juniper Deep Packet Inspection (JDPI) rules and access unauthorized networks or resources, when 'no-syn-check' is enabled on the device. JDPI incorrectly classifies out-of-state asymmetric TCP flows as the dynamic-application INCONCLUSIVE instead of UNKNOWN, which is more permissive, causing the firewall to allow traffic to be forwarded that should have been denied. This issue only occurs when 'set security flow tcp-session no-syn-check' is configured on the device. This issue affects Juniper Networks Junos OS on SRX Series: 18.4 versions prior to 18.4R2-S9, 18.4R3-S9; 19.1 versions prior to 19.1R2-S3, 19.1R3-S6; 19.2 versions prior to 19.2R1-S7, 19.2R3-S3; 19.3 versions prior to 19.3R2-S6, 19.3R3-S2; 19.4 versions prior to 19.4R2-S5, 19.4R3-S3; 20.1 versions prior to 20.1R2-S2, 20.1R3; 20.2 versions prior to 20.2R3-S1; 20.3 versions prior to 20.3R3; 20.4 versions prior to 20.4R2-S1, 20.4R3; 21.1 versions prior to 21.1R1-S1, 21.1R2. This issue does not affect Juniper Networks Junos OS versions prior to 18.4R1.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Incorrect Authorization
The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check.
How developers prevent this class of flaw
- Divide the product into anonymous, normal, privileged, and administrative areas. Reduce the attack surface by carefully mapping roles with data and functionality. Use role-based access control (RBAC) to enforce the roles at the appropriate boundaries. Note that this approach may not protect against horizontal authorization, i.e., it will not protect a user from attacking others with the same role.
- Ensure that access control checks are performed related to the business logic. These checks may be different than the access control checks that are applied to more generic resources such as files, connections, processes, memory, and database records. For example, a database may restrict access for medical records to a specific database user, but each record might only be intended to be accessible to the patient and the patient's doctor.
- Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. For example, consider using authorization frameworks such as the JAAS Authorization Framework and the OWASP ESAPI Access Control feature.
Timeline
- CVE record published.
- Record last changed materially (score, affected products, status or references).
References
Advisories
Other vulnerabilities in Junos OS
- 7.5 High severity
- 9.8 Critical severity
- 9.8 Critical severity
- 8.8 High severity
- 8.8 High severity
- 7.5 High severity
Recent Incorrect Authorization vulnerabilities
- 8.8 High severity
- 9.8 Critical severity
- 7.5 High severity
- 6.5 Medium severity
- 7.8 High severity
Linux Kernel Privilege Escalation Exploited
- 9.8 Critical severity
Spotted an error? Tell us.