CVE-2017-1000024
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 · uneditedShotwell version 0.24.4 or earlier and 0.25.3 or earlier is vulnerable to an information disclosure in the web publishing plugins resulting in potential password and oauth token plaintext transmission
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 confidenceShotwell versions 0.24.4 and earlier, and 0.25.3 and earlier contain an information disclosure vulnerability in the web publishing plugins. The vulnerability results in passwords and OAuth tokens being transmitted in plaintext, potentially exposing authentication credentials to network eavesdropping.
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>= 0.24.0, <= 0.24.4>= 0.25.0, <= 0.25.3CVSS 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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/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.
-
Identify installed Shotwell versionRun 'shotwell --version' from command line, or check the application's 'About' section in the Help menu. On Linux systems, you can also check via package manager: 'dpkg -l | grep shotwell' or 'rpm -qa | grep shotwell'.Affected if The version is 0.24.0 through 0.24.4, or 0.25.0 through 0.25.3
-
Determine if web publishing plugins are configuredOpen Shotwell, go to Edit > Preferences > Publishing > and review the list of enabled publishing plugins (Facebook, Flickr, Picasa, YouTube, etc.). Alternatively, check for published albums or configured export destinations.Affected if Any web publishing plugin is enabled or has been configured at least once
-
Check for stored authentication credentialsExamine Shotwell's configuration directory (typically ~/.local/share/shotwell/ or ~/.config/shotwell/) for files containing OAuth tokens or saved passwords related to publishing services.Affected if Credential files exist for any web service integration
-
Inspect network configuration for publishing servicesReview any proxy settings or network configuration that might route Shotwell traffic through untrusted networks. Check if HTTPS is enforced in any relevant configuration files.Affected if Connections to publishing services could traverse untrusted networks (public WiFi, etc.)
You are affected if you run Shotwell version 0.24.0-0.24.4 or 0.25.0-0.25.3 AND have web publishing plugins enabled or have configured accounts for services like Facebook, Flickr, or Picasa.
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 Shotwell to a version beyond 0.25.3 (or the latest stable release). If upgrading is not immediately possible, avoid using web publishing plugins or ensure all network connections occur over trusted networks or VPNs.
- 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-2017-1000024 — 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-1000024 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