dbcve.org
Junos Os EvolvedOperating system · Juniper

CVE-2023-44187

MEDIUM · 5.5 CVSS v3.1 Published 2023-10-11
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
An Exposure of Sensitive Information vulnerability in the 'file copy' command of Junos OS Evolved allows a local, authenticated attacker with shell access to view passwords supplied on the CLI command-line. These credentials can then be used to provide unauthorized access to the remote system. This issue affects Juniper Networks Junos OS Evolved: * All versions prior to 20.4R3-S7-EVO; * 21.1 versions 21.1R1-EVO and later; * 21.2 versions prior to 21.2R3-S5-EVO; * 21.3 versions prior to 21.3R3-S4-EVO; * 21.4 versions prior to 21.4R3-S4-EVO; * 22.1 versions prior to 22.1R3-S2-EVO; * 22.2 versions prior to 22.2R2-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

A local authenticated attacker with shell access to Junos OS Evolved can view passwords supplied on the CLI command-line when using the 'file copy' command. These exposed credentials can then be used to gain unauthorized access to remote systems.

MitigationUpgrade to a fixed Junos OS Evolved version: 20.4R3-S7-EVO, 21.1R3-EVO or later, 21.2R3-S5-EVO or later, 21.3R3-S4-EVO or later, 21.4R3-S4-EVO or later, 22.1R3-S2-EVO, or 22.2R2-EVO.

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:< 20.4= 20.4= 21.1= 21.2= 21.3= 21.4= 22.1= 22.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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

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

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. Confirm product is Junos OS Evolved
    Run 'show version' or check system identification to verify the installed product is Junos OS Evolved (not standard Junos OS)
    Affected if The product is Junos OS Evolved (this vulnerability only affects the Evolved variant)
  2. Check installed Junos OS Evolved version
    Run 'show version' or 'version' command to obtain the exact installed version number
    Affected if The installed version matches any of the affected versions: 20.4, 21.1, 21.2, 21.3, 21.4, 22.1, 22.2, or any version below 20.4
  3. Verify if file copy command was used with credentials
    Review command history, audit logs, or shell logs for usage of the 'file copy' command that included passwords or authentication credentials on the command line
    Affected if The 'file copy' command was executed with credentials passed as command-line arguments, as these would have been visible in the process list
  4. Check for credential exposure in process arguments
    Use process monitoring or inspect running process arguments (if accessible) to see if credentials were exposed for any file copy operations
    Affected if Credentials were passed to 'file copy' and are visible in process metadata or system logs

A system is affected if it is running Junos OS Evolved with a version matching the affected list and the 'file copy' command was used with credentials on the command line.

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

Upgrade to a fixed Junos OS Evolved version: 20.4R3-S7-EVO, 21.1R3-EVO or later, 21.2R3-S5-EVO or later, 21.3R3-S4-EVO or later, 21.4R3-S4-EVO or later, 22.1R3-S2-EVO, or 22.2R2-EVO.

Recommended fix High confidence

20.4R3-S7-EVO, 21.2R3-S5-EVO, 21.3R3-S4-EVO, 21.4R3-S4-EVO, 22.1R3-S2-EVO, or 22.2R2-EVO depending on current branch

  1. 1. Identify the current Junos OS Evolved version using 'show version' command
  2. 2. Based on current version, upgrade to the minimum fixed release: 20.4R3-S7-EVO for 20.4 and earlier; 21.2R3-S5-EVO for 21.1; 21.2R3-S5-EVO for 21.2; 21.3R3-S4-EVO for 21.3; 21.4R3-S4-EVO for 21.4; 22.1R3-S2-EVO for 22.1; 22.2R2-EVO for 22.2
  3. 3. Download the appropriate upgrade package from the Juniper support portal
  4. 4. Upload the package to the device using 'request system software add' command with the validate option first
  5. 5. Reboot the device after successful upgrade using 'request system reboot'
  6. 6. After reboot, verify the new version is installed using 'show version'
  7. 7. Test the 'file copy' command to confirm credentials are no longer exposed in process listings
Caveat Standard Junos OS Evolved upgrade precautions apply - validate in lab first, ensure configuration compatibility, and plan maintenance window

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

Fix this in Junos Os Evolved Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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