dbcve.org
Junos Os EvolvedOperating system · Juniper

CVE-2023-44195

MEDIUM · 5.3 CVSS v3.1 Published 2023-10-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable 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 Improper Restriction of Communication Channel to Intended Endpoints vulnerability in the NetworkStack agent daemon (nsagentd) of Juniper Networks Junos OS Evolved allows an unauthenticated network based attacker to cause limited impact to the availability of the system. If specific packets reach the Routing-Engine (RE) these will be processed normally even if firewall filters are in place which should have prevented this. This can lead to a limited, increased consumption of resources resulting in a Denial-of-Service (DoS), and unauthorized access. CVE-2023-44196 is a prerequisite for this issue. This issue affects Juniper Networks Junos OS Evolved: * 21.3-EVO versions prior to 21.3R3-S5-EVO; * 21.4-EVO versions prior to 21.4R3-S4-EVO; * 22.1-EVO version 22.1R1-EVO and later; * 22.2-EVO version 22.2R1-EVO and later; * 22.3-EVO versions prior to 22.3R2-S2-EVO, 22.3R3-S1-EVO; * 22.4-EVO versions prior to 22.4R3-EVO. This issue doesn't not affected Junos OS Evolved versions prior to 21.3R1-EVO.

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

Improper restriction of communication channel in the NetworkStack agent daemon (nsagentd) allows specific packets to bypass firewall filters and reach the Routing-Engine (RE) even when blocking rules are configured. This enables unauthenticated network-based attackers to cause limited resource consumption (DoS) and potential unauthorized access. The issue requires CVE-2023-44196 as a prerequisite.

MitigationApply the vendor-supplied patches for the affected Junos OS Evolved versions. Review and enforce firewall filter policies on the Routing-Engine to restrict unnecessary network communication to nsagentd.

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

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

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

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 the Junos OS Evolved version
    Run 'show version' or 'cat /etc/version' to determine the installed Junos OS Evolved version
    Affected if The version matches 21.4, 22.1, 22.2, 22.3, 22.4, 23.1, or 23.2 from the affected versions list
  2. Verify nsagentd daemon is running
    Run 'systemctl status nsagentd' or check process list for nsagentd
    Affected if The NetworkStack agent daemon (nsagentd) is active on the system
  3. Confirm CVE-2023-44196 prerequisite exists
    Check if the prerequisite vulnerability CVE-2023-44196 is also present on the system
    Affected if CVE-2023-44196 is present, as it is required for CVE-2023-44195 to be exploitable
  4. Check firewall filter configuration
    Run 'show firewall' or review filter policies configured on the Routing-Engine
    Affected if Firewall filter rules are configured to block network traffic to nsagentd but may be bypassed

The system is affected if it runs Junos OS Evolved version 21.4, 22.1, 22.2, 22.3, 22.4, 23.1, or 23.2 with the nsagentd daemon running and the prerequisite CVE-2023-44196 present.

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

Apply the vendor-supplied patches for the affected Junos OS Evolved versions. Review and enforce firewall filter policies on the Routing-Engine to restrict unnecessary network communication to nsagentd.

Recommended fix High confidence

22.4R3-EVO (or the latest available fixed version for your branch: 21.3R3-S5-EVO, 21.4R3-S4-EVO, 22.3R3-S1-EVO)

  1. 1. Identify the current Junos OS Evolved version running on the device using 'show version' command
  2. 2. Determine the appropriate fixed version based on your current branch: 21.3-EVO → 21.3R3-S5-EVO, 21.4-EVO → 21.4R3-S4-EVO, 22.3-EVO → 22.3R3-S1-EVO (preferred) or 22.3R2-S2-EVO, 22.4-EVO → 22.4R3-EVO
  3. 3. Download the appropriate fixed Junos OS Evolved software from the Juniper Networks support portal
  4. 4. Back up the current device configuration using 'request system configuration backup'
  5. 5. Install the software upgrade following Juniper's standard upgrade procedure: 'request system software add <package-name> reboot'
  6. 6. After reboot, verify the new version is running with 'show version'
  7. 7. Verify the fix is applied by confirming nsagentd behavior and that firewall filters are properly enforced
Caveat Standard Junos OS upgrade risks apply - ensure configuration compatibility and plan for potential downtime

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

Fix this in Junos Os Evolved 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-2023-44195 — 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-44195 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