CVE-2020-1623
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 · uneditedA local, authenticated user with shell can view sensitive configuration information via the ev.ops configuration file. This issue affects all versions of Junos OS Evolved prior to 19.2R1.
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 confidenceA local, authenticated user with shell access on Junos OS Evolved can read the ev.ops configuration file which contains sensitive configuration information. This is an information disclosure vulnerability affecting all versions prior to 19.2R1.
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< 19.2r1CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the Junos OS variantRun 'show version' or check the system banner to confirm whether the device is running Junos OS Evolved versus standard Junos OS. This vulnerability affects only the Evolved variant.Affected if The device is running Junos OS Evolved (not standard Junos OS)
-
Check the installed Junos OS Evolved versionRun 'show version' or 'cat /etc/version' to obtain the exact version number. Compare this version against the 19.2R1 baseline.Affected if The installed version is earlier than 19.2R1 (for example, 19.1.x, 18.4.x, or earlier)
-
Locate the ev.ops configuration fileCheck for the existence of the file at /etc/ev.ops or /junos/ev.ops on the filesystem. Use 'ls -la' to inspect the file and its permissions.Affected if The ev.ops file exists and is readable by non-privileged users
-
Verify file permissions on sensitive configurationRun 'ls -l /etc/ev.ops' or equivalent path to determine if the file has overly permissive read access for authenticated local users.Affected if The file is readable by authenticated local users with shell access (world-readable or group-readable by non-root users)
-
Confirm shell access availabilityDetermine whether local users have shell access to the device. Review /etc/passwd or user configurations to see which users can access the shell.Affected if Local authenticated users have shell access to the system
A user is affected if the device runs Junos OS Evolved with a version prior to 19.2R1 and the ev.ops configuration file is readable by authenticated local users with shell access.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor data19.2r1
Upgrade Junos OS Evolved to version 19.2R1 or later to remediate this vulnerability.
- Consultation4.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,728.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-1623 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2020-1623 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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