CVE-2019-12847
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 · uneditedIn JetBrains Hub versions earlier than 2018.4.11298, the audit events for SMTPSettings show a cleartext password to the admin user. It is only relevant in cases where a password has not changed since 2017, and if the audit log still contains events from before that period.
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 confidenceIn JetBrains Hub versions prior to 2018.4.11298, the audit logging feature for SMTP settings stores and displays server passwords in plaintext. Administrators with access to audit logs can view these cleartext credentials for any SMTP configurations that have passwords unchanged since 2017 and where audit events from that period still exist.
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< 2018.4.11298CVSS 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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:H/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 the installed JetBrains Hub versionAccess the Hub administration interface and navigate to the About section, or check the product version through the Hub configuration files or startup logsAffected if The version is less than 2018.4.11298 (e.g., 2018.3.x, 2018.2.x, or earlier)
-
Locate historical audit logsAccess the Hub audit log viewer in the administration panel, typically found under Administration > Audit Logs or similar pathAffected if Audit logs exist from the 2017 time period and contain SMTP configuration events
-
Examine SMTP configuration audit eventsWithin the audit logs, search for events related to SMTP settings (e.g., 'SMTP password changed' or 'SMTP configuration updated') from 2017Affected if SMTP password change events from 2017 are visible and the password field shows plaintext characters rather than masked or hashed values
-
Check current SMTP password ageReview the current SMTP configuration in Hub settings and determine when the password was last changed, or compare against any password change historyAffected if The SMTP password has remained unchanged since 2017 and historical audit events from that period are still retained in the system
A user is affected if their Hub version is below 2018.4.11298 AND they have historical audit logs containing SMTP password change events from 2017, with passwords still unchanged since that time.
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 data2018.4.11298
Upgrade JetBrains Hub to version 2018.4.11298 or later to remediate the plaintext password disclosure. Additionally, rotate any SMTP passwords that may have been exposed in historical audit logs as a precautionary measure.
- Consultation1.0 h
- Implementation2.0 h
- Testing1.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,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-12847 — 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-12847 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