InfluxdbApplication · Eficode
CVE-2019-10329
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 · uneditedJenkins InfluxDB Plugin 1.21 and earlier stored credentials unencrypted in its global configuration file on the Jenkins master where they can be viewed by users with access to the master file system.
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 confidenceJenkins InfluxDB Plugin versions 1.21 and earlier stores credentials in plain text (unencrypted) within its global configuration file on the Jenkins master node. Users with access to the master file system can read these stored credentials, resulting in credential exposure.
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
InfluxdbApplication
<= 1.21CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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.
-
Locate the InfluxDB Plugin global configuration fileNavigate to the Jenkins master file system and find the InfluxDB plugin configuration. This is typically stored in the Jenkins home directory under userContent or within the plugin's own configuration directory.Affected if The configuration file exists and contains stored credentials.
-
Identify the installed InfluxDB Plugin versionCheck the Jenkins plugin management interface or inspect the plugin's .jpi or .hpi file metadata in the plugins directory to determine the exact version number.Affected if The installed version is 1.21 or earlier.
-
Examine stored credentials for encryptionOpen the global configuration file in a text editor or use a command to view its contents. Look for credential fields (such as passwords, API tokens, or usernames) and determine whether they appear as plain readable text or as encrypted/obfuscated strings.Affected if Credentials are stored in plain text (readable, unencrypted format) rather than being encrypted or masked.
-
Verify credential exposure riskReview file system permissions on the configuration file. Check if users other than the Jenkins administrator have read access to the file containing the credentials.Affected if The configuration file is readable by users with file system access, and credentials are stored in plain text within it.
You are affected if the InfluxDB Plugin version is 1.21 or earlier AND credentials are stored in plain text (unencrypted) within the global configuration file accessible on the Jenkins master node.
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 dataRe-credential all exposed credentials (as they may have been compromised), clear any unencrypted credentials from the configuration file, and upgrade to InfluxDB Plugin version 1.22 or later which encrypts stored credentials.
Fix this in Influxdb
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.0 h
- Testing2.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 $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-10329 — 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-10329 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