CVE-2019-1000001
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 · uneditedTeamPass version 2.1.27 and earlier contains a Storing Passwords in a Recoverable Format vulnerability in Shared password vaults that can result in all shared passwords are recoverable server side. This attack appears to be exploitable via any vulnerability that can bypass authentication or role assignment and can lead to shared password leakage.
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 confidenceTeamPass versions 2.1.27 and earlier store shared passwords in a recoverable (likely plaintext or weakly encrypted) format within the shared password vaults. When combined with any vulnerability that bypasses authentication or role assignment checks, an attacker can access and recover all shared passwords stored on the server.
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<= 2.1.27.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
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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 TeamPass versionLocate the version file or configuration entry in the TeamPass installation directory or database. Common locations include a version.php file, a config file, or a version field in the database settings table.Affected if The installed version is 2.1.27.0 or any earlier version (e.g., 2.1.26, 2.1.25, etc.)
-
Confirm presence of shared passwordsQuery the database or inspect the shared password vault feature to determine if any shared passwords are stored in the system. In TeamPass, shared passwords are typically stored in a dedicated table (often named something like 'shared_secrets' or 'shared_passwords').Affected if The system contains any shared passwords in the shared vault feature.
The environment is affected if running TeamPass version 2.1.27.0 or earlier AND the system contains shared passwords in the vault, as these credentials are stored in a recoverable weak format.
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.
dbcve · scopedUpgrade TeamPass to a version beyond 2.1.27 that implements proper password encryption. Additionally, identify and remediate the authentication/role bypass vector that enables access to the recoverable passwords, and consider rotating exposed shared credentials as a precautionary measure.
Teampass 2.1.27.1 or later stable release
- 1. Backup your Teampass database and files before making any changes
- 2. Identify your current Teampass version in the admin interface or source code
- 3. Download the latest stable Teampass release from the official GitHub repository (github.com/nilsteampassnet/TeamPass)
- 4. Review the release notes for version 2.1.27.1 or later to confirm security fixes are included
- 5. Upgrade Teampass to version 2.1.27.1 or latest stable release
- 6. Verify the upgrade was successful and test password retrieval functionality
- 7. Ensure proper encryption keys are configured and functioning
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation24.0 h
- Testing12.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $14,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-1000001 — 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-2019-1000001 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