CVE-2017-1000025
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 · uneditedGNOME Web (Epiphany) 3.23 before 3.23.5, 3.22 before 3.22.6, 3.20 before 3.20.7, 3.18 before 3.18.11, and prior versions, is vulnerable to a password manager sweep attack resulting in the remote exfiltration of stored passwords for a selected set of websites.
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 confidenceGNOME Web (Epiphany) browser contains a vulnerability in its built-in password manager that allows malicious webpages to perform a 'sweep attack' - querying the password manager via JavaScript and exfiltrating stored credentials for targeted websites. The attack does not require user interaction beyond visiting a crafted webpage.
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= 3.18.0= 3.18.1= 3.18.2= 3.18.3= 3.18.4= 3.18.5= 3.18.6= 3.18.7= 3.18.8= 3.18.9= 3.18.10= 3.20.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
- 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 Epiphany versionRun 'epiphany --version' or check the package manager (e.g., 'dpkg -l epiphany-browser' or 'rpm -qi epiphany')Affected if The version matches 3.18.0-3.18.10, 3.18.11, 3.20.0, 3.22.6, 3.23.5, or 3.20.7 - only versions prior to 3.18.11, 3.20.7, 3.22.6, or 3.23.5 are affected (the versions listed are the vulnerable ones)
-
Verify password manager is in useCheck if Epiphany has any saved passwords by accessing the password manager UI (Preferences > Privacy > Passwords) or inspecting ~/.local/share/epiphany/ directory for password filesAffected if The password manager contains stored credentials and the browser version is vulnerable
-
Confirm JavaScript is enabledIn Epiphany, go to Preferences > Privacy and verify JavaScript is enabled, or inspect about:config for javascript.enabledAffected if JavaScript is enabled in the browser settings - this is required for the sweep attack to execute
You are affected if you are running Epiphany versions 3.18.0 through 3.18.10 or 3.20.0, use the built-in password manager with saved credentials, and have JavaScript enabled in the browser.
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 GNOME Web (Epiphany) to version 3.23.5, 3.22.6, 3.20.7, or 3.18.11 or later to receive the security patch.
- Consultation1.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,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-1000025 — 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-1000025 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