dbcve.org
JunosOperating system · Juniper

CVE-2023-44176

MEDIUM · 5.5 CVSS v3.1 Published 2023-10-13
Fix available
A fix is available. Upgrade to 20.4 or later.
See remediation →
57/100
Remediation priority · Elevated
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
A Stack-based Buffer Overflow vulnerability in the CLI command of Juniper Networks Junos OS allows a low privileged attacker to execute a specific CLI commands leading to Denial of Service. Repeated actions by the attacker will create a sustained Denial of Service (DoS) condition. This issue affects Juniper Networks: Junos OS: * All versions prior to 20.4R3-S8; * 21.2 versions prior to 21.2R3-S6; * 21.3 versions prior to 21.3R3-S5; * 22.1 versions prior to 22.1R3-S3; * 22.3 versions prior to 22.3R3; * 22.4 versions prior to 22.4R3.

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 · moderate confidence

A stack-based buffer overflow vulnerability exists in the Juniper Junos OS CLI that allows a low-privileged attacker to execute specific CLI commands causing denial of service. Repeated exploitation leads to sustained DoS conditions.

MitigationApply the vendor-supplied patches by upgrading Junos OS to the fixed versions (20.4R3-S8, 21.2R3-S6, 21.3R3-S5, 22.1R3-S3, 22.3R3, or 22.4R3 and later).

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:< 20.4= 20.4= 21.2= 21.3= 21.4= 22.1= 22.2= 22.3= 22.4
Junos Os EvolvedOperating system
Affected:< 20.4= 20.4= 21.2= 21.3= 21.4= 22.1= 22.2= 22.3= 22.4

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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/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 OS version
    Run 'show version' or 'show version detail' command in the CLI to obtain the exact installed version and build number
    Affected if The displayed version matches any of the affected versions: < 20.4, 20.4, 21.2, 21.3, 21.4, 22.1, 22.2, 22.3, or 22.4 (or their Rsuffix variants like 20.4R1, 22.4R1, etc.)
  2. Confirm Junos OS Evolved variant
    Check if the device runs Junos OS Evolved by examining the 'show version' output for 'Evolved' or checking the OS variant in the system details
    Affected if The device runs Junos OS Evolved and the version matches the affected list for Evolved (same version numbers as standard Junos)
  3. Verify CLI access exists
    Review user accounts and authentication logs to determine if low-privileged users have CLI login capability
    Affected if Low-privileged non-administrative users can access the CLI, as the vulnerability is exploitable by such users through specific CLI commands

The environment is affected if the Junos OS/Junos OS Evolved version matches any of the listed affected versions (20.4, 21.2, 21.3, 21.4, 22.1, 22.2, 22.3, 22.4 or versions prior to 20.4) and low-privileged CLI access is available.

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
Upgrade available Upgrade to 20.4 or later
Fixed in 20.4
Interim mitigation

Apply the vendor-supplied patches by upgrading Junos OS to the fixed versions (20.4R3-S8, 21.2R3-S6, 21.3R3-S5, 22.1R3-S3, 22.3R3, or 22.4R3 and later).

Recommended fix High confidence

20.4R3-S8, 21.2R3-S6, 21.3R3-S5, 22.1R3-S3, 22.3R3, or 22.4R3 (depending on current branch)

  1. 1. Identify the currently installed Junos OS version using 'show version' command
  2. 2. Determine the appropriate upgrade path based on current version branch (20.4, 21.2, 21.3, 22.1, 22.3, or 22.4)
  3. 3. Download the appropriate fixed release from Juniper Networks support portal: for 20.4 branch use 20.4R3-S8 or later, for 21.2 branch use 21.2R3-S6 or later, for 21.3 branch use 21.3R3-S5 or later, for 22.1 branch use 22.1R3-S3 or later, for 22.3 branch use 22.3R3 or later, for 22.4 branch use 22.4R3 or later
  4. 4. Plan maintenance window as upgrade requires system reboot
  5. 5. Back up current configuration using 'request system configuration backup'
  6. 6. Upload the upgrade package to the device using 'request system software add' command
  7. 7. Reboot the device to complete installation using 'request system reboot'
  8. 8. Verify successful upgrade with 'show version' confirming running the patched version
Caveat Standard Junos upgrade may cause temporary service interruption; ensure configuration compatibility and plan for downtime

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

Fix this in Junos Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,480
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-44176 — 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-2023-44176 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