CVE-2022-22160
MEDIUMDescription
An Unchecked Error Condition vulnerability in the subscriber management daemon (smgd) of Juniper Networks Junos OS allows an unauthenticated adjacent attacker to cause a crash of and thereby a Denial of Service (DoS). In a subscriber management / broadband edge environment if a single session group configuration contains dual-stack and a pp0 interface, smgd will crash and restart every time a PPPoE client sends a specific message. This issue affects Juniper Networks Junos OS on MX Series: 16.1 version 16.1R1 and later versions prior to 18.4R3-S10; 19.1 versions prior to 19.1R2-S3, 19.1R3-S7; 19.2 versions prior to 19.2R1-S8, 19.2R3-S4; 19.3 versions prior to 19.3R3-S4; 19.4 versions prior to 19.4R3-S5; 20.1 versions prior to 20.1R3-S3; 20.2 versions prior to 20.2R3-S3; 20.3 versions prior to 20.3R3-S2; 20.4 versions prior to 20.4R3; 21.1 versions prior to 21.1R3; 21.2 versions prior to 21.2R2. This issue does not affect Juniper Networks Junos OS versions prior to 16.1R1.
How to fix
No published remediation has been found for this vulnerability's affected products yet.
Mitigation guidance may be in the linked vendor advisories in the References section below.
TridentStack Control tracks known vulnerabilities across your Windows, macOS, and Linux fleet and shows the fix as soon as one is published. See how it works
CVSS v3 Vector
Exploitability
Impact
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Exploit Intelligence
Low risk: more likely to be exploited than 29% of all known CVEs.
References
Related Vulnerabilities
Other CWE-391 vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2024-52316 | Critical | 9.8 | 6.3% | - | Fix |
| CVE-2017-12179 | Critical | 9.8 | 4.4% | - | Fix |
| CVE-2017-12177 | Critical | 9.8 | 4.4% | - | Fix |
| CVE-2017-12186 | Critical | 9.8 | 4.3% | - | Fix |
| CVE-2017-12183 | Critical | 9.8 | 4.2% | - | Fix |
| CVE-2017-12182 | Critical | 9.8 | 4.2% | - | Fix |
Common questions
How do I fix CVE-2022-22160?
No published fix for CVE-2022-22160 has been found yet. Check the linked vendor advisories for guidance as it becomes available.
Is CVE-2022-22160 being actively exploited?
Not that we know of. CVE-2022-22160 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.36% is the estimated probability that it will be exploited in the next 30 days. That is higher than 29% of all scored CVEs.
How severe is CVE-2022-22160?
CVE-2022-22160 has a CVSS v3 base score of 6.5, rated medium. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
Embed a live status badge for CVE-2022-22160
Markdown
[](https://tridentstack.com/cve/CVE-2022-22160)HTML
<a href="https://tridentstack.com/cve/CVE-2022-22160"><img src="https://tridentstack.com/cve/badge/CVE-2022-22160.svg" alt="CVE-2022-22160"></a>Find and fix vulnerabilities across your fleet
TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2024-11-21.