01 Record
CVE-2018-0023
Junos Snapshot Administrator (JSNAPy) world writeable default configuration file permission
MediumPUBLISHEDCNA: juniper
CNA base score5.5 CVSS v3.xCVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
02 Description
Junos Snapshot Administrator (JSNAPy) world writeable default configuration file permission
03 Exploitation and scoring
- Exploitation
- Not assessed. CISA has not published an exploitation assessment for this record, and it is not in the KEV catalog. That is an absence of assessment, not a finding of no risk.
- SSVC decision
- Not assessed by CISA
- EPSS probability
- 0.29% probability of exploitation activity in the next 30 days.
- EPSS percentile
- Equal to or higher than the score of 21.6% of scored records. A rank, not a probability.
- NVD base score
- 5.5 (CVSS v3.x), scored by the NVD independently of the CNA.
- NVD CVSS vector
- CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
- NVD analysis status
- Modified. NVD last modified this record on 2026-06-17.
- Red Hat severity
- No Red Hat rating. Red Hat rates the CVEs that affect its products.
Exploit-prediction scores from FIRST. Independent scoring and analysis status from the NVD. Vendor severity from Red Hat. Exploitation assessment and catalog membership from CISA.
04 Metadata
- Published
- 2018-04-11 19:00Z8 YR AGO
- Last updated
- 2024-09-16 16:13Z2 YR AGO
- Reserved
- 2017-11-16
- Assigning CNA
- juniper
- Record state
- PUBLISHED
- Severity
- Medium (CVSS 5.5)
- CNA CVSS vector
- CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
- Weaknesses
- CWE-276Incorrect Default PermissionsBase
- Data version
- 5.1
- Document digest
- e3c1f142f294afd8146a88cfe6bfe7a1320b04db861d28e7f58210ef0a2e83cc
05 Affected products
VendorProductVersionsPlatforms
06 References
- kb.juniper.nethttps://kb.juniper.net/JSA10856
- www.securityfocus.com103745http://www.securityfocus.com/bid/103745
07 Remediation
This issue is resolved in 1.3.0 and subsequent releases. Fixed JSNAPy releases can be downloaded from https://github.com/Juniper/jsnapy/releases.
Upgrading to the fixed release is not sufficient to resolve the issue, modifying file permission after upgrade as described in the workaround section is required. This issue is fixed for fresh/new installation.