dbcve.org
JunosOperating system · Juniper

CVE-2022-22160

MEDIUM · 6.5 CVSS v3.1 Published 2022-01-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
70/100
Remediation priority · Elevated
No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

An unchecked error condition in the subscriber management daemon (smgd) causes repeated crashes when a specific PPPoE message is received from a client in a dual-stack configuration with a pp0 interface. An unauthenticated adjacent attacker can trigger the vulnerability by sending a specially crafted PPPoE message, causing smgd to crash and restart repeatedly, resulting in sustained denial of service.

MitigationUpgrade Junos OS to a patched version (18.4R3-S10, 19.1R2-S3, 19.1R3-S7, 19.2R1-S8, 19.2R3-S4, 19.3R3-S4, 19.4R3-S5, 20.1R3-S3, 20.2R3-S3, 20.3R3-S2, 20.4R3, 21.1R3, or 21.2R2 or later). As a temporary workaround, consider isolating subscriber management segments or restricting adjacent network access to PPPoE services.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
JunosOperating system
Affected:= 16.1= 16.1x65= 16.1x70= 16.2= 17.1= 17.2= 17.2x75= 17.3= 17.4= 17.4r2= 18.1= 18.1x75

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Adjacent
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Junos version
    Run 'show version' or 'system show version' command to obtain the installed Junos OS version
    Affected if Version matches or falls within 16.1, 16.1x65, 16.1x70, 16.2, 17.1, 17.2, 17.2x75, 17.3, 17.4, 17.4r2, 18.1, or 18.1x75
  2. Verify PPPoE subscriber management is active
    Run 'show interfaces pp0' or check for pp0 interface configuration in the layout. Use 'show subscribers interface' to list active PPPoE subscribers
    Affected if pp0 interfaces exist and PPPoE subscriber management is enabled
  3. Confirm dual-stack configuration
    Run 'show system services subscriber-management' and check for both IPv4 and IPv6 addresses assigned. Use 'show subscribers summary' to verify dual-stack subscribers
    Affected if Dual-stack (both IPv4 and IPv6) is configured for PPPoE subscribers
  4. Inspect smgd crash logs
    Run 'show system processes mgd' to check smgd status, and review '/var/log/messages' or use 'show log messages' for smgd crash or restart entries
    Affected if Multiple smgd crashes or restarts are logged, especially around PPPoE activity
  5. Check for sustained restart pattern
    Use 'show system core-dumps' and review 'show system services subscriber-management statistics' for restart counters
    Affected if smgd shows repeated restarts or high restart count without clear administrative cause

User is affected if running a listed vulnerable Junos version AND PPPoE subscriber management with dual-stack on pp0 interfaces is enabled, with evidence of smgd crashes.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Junos OS to a patched version (18.4R3-S10, 19.1R2-S3, 19.1R3-S7, 19.2R1-S8, 19.2R3-S4, 19.3R3-S4, 19.4R3-S5, 20.1R3-S3, 20.2R3-S3, 20.3R3-S2, 20.4R3, 21.1R3, or 21.2R2 or later). As a temporary workaround, consider isolating subscriber management segments or restricting adjacent network access to PPPoE services.

Recommended fix High confidence

Upgrade to the fixed maintenance release for your version branch (e.g., 18.4R3-S10, 19.1R3-S7, 19.2R3-S4, 19.3R3-S4, 19.4R3-S5, 20.1R3-S3, 20.2R3-S3, 20.3R3-S2, 20.4R3, 21.1R3, 21.2R2, or any later release)

  1. Identify the exact Junos OS version currently running on the MX Series device using 'show version'
  2. Determine which version branch (16.1, 19.1, 19.2, 19.3, 19.4, 20.1, 20.2, 20.3, 20.4, 21.1, or 21.2) the current software matches
  3. For 16.1 branch: upgrade to 18.4R3-S10 or later
  4. For 19.1 branch: upgrade to 19.1R2-S3 or 19.1R3-S7 (whichever is later in the maintenance stream)
  5. For 19.2 branch: upgrade to 19.2R1-S8 or 19.2R3-S4 (whichever is later in the maintenance stream)
  6. For 19.3 branch: upgrade to 19.3R3-S4 or later
  7. For 19.4 branch: upgrade to 19.4R3-S5 or later
  8. For 20.1 branch: upgrade to 20.1R3-S3 or later
Caveat Standard Junos upgrade caveats apply: review release notes for any changes to features used in your configuration, and plan for potential brief service interruption during upgrade

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Junos Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-22160 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-22160 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data