Keeper Security Keeper 16.10.2
Approved changes feed: RSS · Atom
cpe:2.3:a:keepersecurity:keeper:16.10.2:*:*:*:*:*:*:*
part: a version: 16.10.2 update: *
| Vendor | Keepersecurity (b948c3da-c5f5-5f3c-8a15-0ba2495c83e2) |
|---|---|
| Product | Keeper (2d3d07fe-e5ed-5c26-84c5-d913cec50fbc) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from NVD CPE 2.0 feed |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2023-36266 |
vulnerable | 2026-06-08 06:06:28.681604 |
Details available
An issue was discovered in Keeper Password Manager for Desktop version 16.10.2 (fixed in 17.2), and the KeeperFill Browser Extensions version 16.5.4 (fixed in 17.2), allows local attackers to gain sensitive information via plaintext password storage in memory after the user is already logged in, and may persist after logout. NOTE: the vendor disputes this for two reasons: the information is inherently available during a logged-in session when the attacker can read from arbitrary memory locations, and information only remains available after logout because of memory-management limitations of web browsers (not because the Keeper technology itself is retaining the information).
Published: 2023-07-12T00:00:00.000Z
Updated: 2025-06-09T14:44:19.940Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.