CVE-2019-1020009
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 · uneditedFleet before 2.1.2 allows exposure of SMTP credentials.
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 confidenceFleet before version 2.1.2 contains a vulnerability where SMTP credentials used for email functionality are exposed, likely through logs, error messages, or an API response. An attacker with access to these outputs could obtain valid SMTP credentials.
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.0.2, <= 2.1.1CVSS 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 Fleet versionRun 'fleet --version' or check the Fleet server metadata to determine the exact version numberAffected if Version is >= 2.0.2 and <= 2.1.1
-
Determine if SMTP is configuredReview Fleet configuration files or settings for SMTP/email integration settings. Check for SMTP host, port, username, and password configuration parametersAffected if SMTP functionality is enabled and credentials are stored in the Fleet configuration
-
Review Fleet logs for credential exposureExamine Fleet server logs, especially error messages, startup logs, and any debugging output for occurrences of SMTP username or password stringsAffected if Logs contain SMTP credentials in plain text or with minimal obfuscation
-
Check API responses for credential leakageInspect API responses from Fleet endpoints, particularly error responses or configuration-related endpoints, for exposed SMTP credentialsAffected if API responses return SMTP credentials in any field
-
Examine configuration storage locationsReview database entries, environment variables, or configuration files where SMTP settings are stored for any inadvertent credential exposureAffected if Stored SMTP credentials are accessible beyond the intended secure storage
A user is affected if running Fleet version 2.0.2 through 2.1.1 with SMTP functionality configured, and SMTP credentials appear in any logs, error messages, or API outputs.
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 Fleet to version 2.1.2 or later to remediate the credential exposure. Additionally, rotate any SMTP credentials that may have been exposed prior to the upgrade.
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-1020009 — 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-1020009 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