Sensitive configuration disclosure via readable ev.ops file
Published Apr 8, 2020 · Updated Sep 16, 2024
Information disclosure in Juniper Networks Junos OS Evolved before 19.2R1 allows local users with shell access to read sensitive configuration data. The ev.ops configuration file records sensitive configuration information and leaves that content readable from the Linux shell. Exploitation requires an authenticated account permitted to enter the shell; the demonstrated consequence is configuration-data disclosure only.
Summary
What happened
Information disclosure in Juniper Networks Junos OS Evolved before 19.2R1 allows local users with shell access to read sensitive configuration data. The ev.ops configuration file records sensitive configuration information and leaves that content readable from the Linux shell. Exploitation requires an authenticated account permitted to enter the shell; the demonstrated consequence is configuration-data disclosure only.
The record
- CVE
- CVE-2020-1623
- Published
- Apr 8, 2020
- Updated
- Sep 16, 2024
- Vendor
- Juniper Networks
- Product
- Junos OS Evolved
- Classifications
- CWE-532, CAPEC-215, T1005
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 8, 2020CVE publishedPublication date reported by the CVE source.
- Sep 16, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=unspecified <19.2R1-EVO
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo