CVE-2020-7912
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 YouTrack before 2019.2.59309, SMTP/Jabber settings could be accessed using backups.
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 confidenceJetBrains YouTrack before version 2019.2.59309 contains an information disclosure vulnerability where backup files expose SMTP and Jabber configuration settings, potentially including authentication credentials used for these services.
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>= 2019.2.0, < 2019.2.59309CVSS 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
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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 YouTrack versionAccess the YouTrack administration console or check the version file in the YouTrack installation directory. In a standard installation, this can often be found in the about page of the admin interface or by reviewing the version.txt file in the installation root.Affected if The installed version is 2019.2.0 or later but earlier than 2019.2.59309
-
Verify backup creation was performedReview the YouTrack administration panel for backup history or check the configured backup storage location for any existing backup files.Affected if One or more backup files exist in a location accessible to the system
-
Inspect backup file contents for exposed credentialsExamine a recent backup file (typically a zip archive) and locate the configuration files within it, specifically looking for SMTP and Jabber/XMPP settings in the exported configuration.Affected if The backup archive contains configuration files with SMTP or Jabber settings that include authentication credentials in plain text or easily decodable format
-
Check backup file access controlsReview file system permissions on the backup storage directory to determine if unauthorized users or processes could read the backup files.Affected if Backup files are stored in a directory with overly permissive access controls or in a location accessible via web server
A user is affected if their YouTrack version falls within 2019.2.0 to 2019.2.59309 AND they have created backups that may contain exposed SMTP or Jabber credentials in accessible configuration files.
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 data2019.2.59309
Upgrade YouTrack to version 2019.2.59309 or later. Additionally, restrict access to backup files and ensure they are stored in secure, access-controlled locations.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-7912 — 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-2020-7912 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