dbcve.org
Path TraversalWeakness · CWE-22

CVE-2025-14617

MEDIUM · 5.3 CVSS v3.1 Published 2025-12-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
55/100
Remediation priority · Elevated
Zero-click

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 · unedited
A vulnerability has been found in Jehovahs Witnesses JW Library App up to 15.5.1 on Android. Affected is an unknown function of the component org.jw.jwlibrary.mobile.activity.SiloContainer. Such manipulation leads to path traversal. Local access is required to approach this attack. The exploit has been disclosed to the public and may be used.

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 confidence

A path traversal vulnerability exists in the JW Library Android app (versions up to 15.5.1) within the SiloContainer component (org.jw.jwlibrary.mobile.activity.SiloContainer). Local attackers can manipulate file path parameters to access files outside the intended directory boundaries.

MitigationApply vendor-supplied patch/update once released for version 15.5.1 or later; until then, limit local device access and avoid storing sensitive data in accessible filesystem locations.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS 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
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify if JW Library is installed
    Run 'adb shell pm list packages | grep jw' or check app list in Settings > Apps for 'JW Library'
    Affected if The package org.jw.jwlibrary.mobile is present on the device
  2. Check installed JW Library version
    Run 'adb shell dumpsys package org.jw.jwlibrary.mobile' and look for versionName under 'Package' section, or view in Play Store/app info
    Affected if versionName is 15.5.1 or lower (any version up to and including 15.5.1)
  3. Verify SiloContainer activity is exported
    Run 'adb shell dumpsys package org.jw.jwlibrary.mobile' and examine the <activity> declarations for org.jw.jwlibrary.mobile.activity.SiloContainer; look for android:exported="true"
    Affected if The SiloContainer activity has android:exported set to true or is implicitly exported (allows other apps or local processes to trigger it)
  4. Check app permissions
    Run 'adb shell dumpsys package org.jw.jwlibrary.mobile' and review permissions under 'granted=true' - particularly storage or file access permissions
    Affected if The app holds storage or file system permissions that could be exploited via the path traversal

User is affected if JW Library version is 15.5.1 or lower AND the SiloContainer activity is exported to other apps, allowing local attackers to manipulate file path parameters beyond intended directories.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor-supplied patch/update once released for version 15.5.1 or later; until then, limit local device access and avoid storing sensitive data in accessible filesystem locations.

Have this fixed Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
27.0 hours of engineering $4,800
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,680.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-14617 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-14617 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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