Security readout for executives and security teams
Plain-English summary
CVE-2017-20199 affects old Buttercup browser extension versions up to 0.14.2. It is an improper access control issue in vault handling that could expose limited sensitive information. The rated severity is low because exploitation is difficult and requires user interaction, but affected software is unsupported and should not remain in use.
Executive priority
Handle through normal vulnerability management, not emergency response. Prioritize removal or upgrade because password-manager extensions handle sensitive data and the affected builds are unsupported, but current evidence supports low severity and no confirmed active exploitation.
Technical view
The issue is mapped to CWE-266 and CWE-284 and has CVSS 3.1 score 3.1. The vector indicates network reachability, high attack complexity, no privileges, required user interaction, unchanged scope, and low confidentiality impact only. Sources state upgrading to version 1.0.1 addresses the issue via pull request 89.
Likely exposure
Exposure is most likely limited to users or managed endpoints still running Buttercup buttercup-browser-extension versions 0.14.0, 0.14.1, or 0.14.2. The source states affected products are no longer supported by the maintainer, increasing operational risk despite low technical severity.
Exploitation context
The source bundle says a public exploit exists and could be used, but CISA KEV status is false and no active exploitation evidence is provided. Exploitation is described as remote but difficult, with high complexity and required user interaction.
Researcher notes
Evidence identifies the component as Vault Handler but does not describe the vulnerable code path in detail. Treat the GitHub issue, pull request 89, and v1.0.1 release as primary remediation context. Do not assume broader Buttercup products are affected without vendor evidence.
Mitigation direction
- Inventory browsers for Buttercup browser extension versions up to 0.14.2.
- Upgrade to Buttercup browser extension 1.0.1 where still applicable.
- Remove unsupported Buttercup extension builds from managed endpoints.
- Check vendor guidance before applying any nonstandard workaround.
- If exposure is suspected, follow credential review and rotation procedures.
Validation and detection
- Confirm installed Buttercup browser extension versions on managed browsers.
- Verify no endpoint is running versions 0.14.0 through 0.14.2.
- Document whether version 1.0.1 or removal resolved exposure.
- Review extension allowlists and endpoint software inventory for unsupported builds.
Public sources used
- CVE Program
- CVE List V5
- VDB-319969 | Buttercup buttercup-browser-extension Vault access control
- VDB-319969 | CTI Indicators (IOB, IOC, TTP)
- Submit #628170 | Buttercup Password Manager Buttercup Browser Extension <=v0.14.2 Improper Access Control
- Buttercup browser extension issue 92
- Buttercup issue 92 comment 358449755
- Buttercup issue 92 comment 372991430
- Buttercup browser extension pull request 89
- Buttercup browser extension v1.0.1 release
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-266: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCWE-284: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2017-20199 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Low
- CVSS
- 3.1 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:N/A:N/E:P/RL:O/RC:C
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:N/A:N/E:P/RL:O/RC:C1.61.4Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
3.1LowVector: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:N/A:N/E:P/RL:O/RC:C
Source materials
- CVE List V5 sourceCVE List V5
- VDB-319969 | Buttercup buttercup-browser-extension Vault access controlCVE reference · vdb-entry, technical-description
- VDB-319969 | CTI Indicators (IOB, IOC, TTP)CVE reference · signature, permissions-required
- Submit #628170 | Buttercup Password Manager Buttercup Browser Extension <=v0.14.2 Improper Access Control – Sensitive Data Exposure (CWE-284 / CWECVE reference · third-party-advisory
- https://github.com/buttercup/buttercup-browser-extension/issues/92CVE reference · issue-tracking, exploit
- https://github.com/buttercup/buttercup-browser-extension/pull/89CVE reference · issue-tracking, patch
- https://github.com/buttercup/buttercup-browser-extension/releases/tag/v1.0.1CVE reference · patch
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Incorrect Privilege Assignment
Incorrect Privilege Assignment represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Improper Access Control
Improper Access Control represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
