CVE-2017-10888
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 · uneditedBOOK WALKER for Windows Ver.1.2.9 and earlier, BOOK WALKER for Mac Ver.1.2.5 and earlier allow an attacker to access local files via unspecified vectors.
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 · moderate confidenceThis is a Local File Inclusion (LFI) or Path Traversal vulnerability in BOOK WALKER desktop applications for Windows (versions 1.2.9 and earlier) and Mac (versions 1.2.5 and earlier). The vulnerability allows attackers to access local files on the host system through unspecified vectors, likely due to insufficient input validation or path sanitization in the application's file handling routines.
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.2.9<= 1.2.5CVSS 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
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:L/AC:L/PR:N/UI:R/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.
-
Check if BOOK WALKER is installed on WindowsOpen Control Panel > Programs and Features, or search for 'BookWalker' in the Start menu. Alternatively, check for the executable at typical installation paths such as C:\Program Files\BookWalker\ or C:\Program Files (x86)\BookWalker\.Affected if BOOK WALKER application is present on the system
-
Check if BOOK WALKER is installed on macOSOpen Finder > Applications and look for 'BookWalker' app, or search using Spotlight (Cmd+Space) for 'BookWalker'.Affected if BOOK WALKER application is present in the Applications folder
-
Determine the installed version on WindowsRight-click the BookWalker executable or shortcut, select Properties, and check the Details tab for the version number. Alternatively, open the application and look for an About or Version section in the Help menu.Affected if The reported version is 1.2.9 or earlier
-
Determine the installed version on macOSRight-click the BookWalker.app in Applications, select Get Info (or press Cmd+I), and check the Version field under the General section. Alternatively, open the application and look for an About option in the BookWalker menu.Affected if The reported version is 1.2.5 or earlier
-
Compare your version against the affected rangesFor Windows: versions 1.2.9 and earlier are affected; the fix is in version 1.2.10 and later. For Mac: versions 1.2.5 and earlier are affected; the fix is in version 1.2.6 and later.Affected if Your installed version falls within the affected range for your platform
You are affected if BOOK WALKER is installed and the version number is 1.2.9 or earlier on Windows, or 1.2.5 or earlier on macOS.
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 dataUpgrade BOOK WALKER to version 1.2.10 or later (Windows) and version 1.2.6 or later (Mac) to obtain the vendor patch addressing this file access vulnerability.
- Consultation2.0 h
- Implementation2.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-10888 — 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-2017-10888 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