CVE-2018-0023
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 · uneditedJSNAPy is an open source python version of Junos Snapshot Administrator developed by Juniper available through github. The default configuration and sample files of JSNAPy automation tool versions prior to 1.3.0 are created world writable. This insecure file and directory permission allows unprivileged local users to alter the files under this directory including inserting operations not intended by the package maintainer, system administrator, or other users. This issue only affects users who downloaded and installed JSNAPy from github.
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 confidenceJSNAPy versions prior to 1.3.0 create default configuration and sample files with world-writable (777) permissions. This allows any local unprivileged user to read, modify, or delete files in these directories, potentially injecting arbitrary operations into the automation tool's execution flow.
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< 1.3.0CVSS 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
- None
- Integrity
- High
- Availability
- None
CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/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.
-
Determine installed JSNAPy versionRun 'jsnapy --version' or check the version file in the JSNAPy installation directory (typically in site-packages or /opt/jsnapy)Affected if Version is lower than 1.3.0
-
Locate JSNAPy config directoryFind the default configuration directory - typically ~/.jsnapy/ or /etc/jsnapy/ where JSNAPy stores its config filesAffected if This directory exists and was created by JSNAPy prior to version 1.3.0
-
Check config directory permissionsRun 'ls -ld ~/.jsnapy/' or the identified config directory path to view permissionsAffected if Directory shows rwxrwxrwx (777) permissions indicating world-writable access
-
Check config file permissionsRun 'ls -la ~/.jsnapy/' to list all files in the config directory and review their permission bitsAffected if Any .yml, .yaml, or sample files show rw-rw-rw- (666) or similar world-writable permissions
-
Check sample templates directory permissionsLocate and inspect the templates/samples directory (commonly in /opt/jsnapy/samples or within the installation) for world-writable permissionsAffected if Sample files or templates have world-writable permissions
A user is affected if JSNAPy version is below 1.3.0 AND the config/sample directories or files within them have world-writable (777/666) permission bits set, allowing unprivileged local 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 data1.3.0
Restrict file permissions on JSNAPy config/sample directories (chmod 755 for dirs, 644 for files) to remove world-writable access, or upgrade to JSNAPy 1.3.0+ which contains the corrected default permissions.
- Consultation1.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-0023 — 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-2018-0023 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