TestlinkApplication · Jenkins
CVE-2019-10378
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 TestLink Plugin 3.16 and earlier stores 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 confidenceThe Jenkins TestLink Plugin versions 3.16 and earlier stores user credentials in plaintext within its global configuration file on the Jenkins master node. Users who have filesystem access to the Jenkins master can read these unencrypted credentials directly from the configuration file.
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
TestlinkApplication
<= 3.16CVSS 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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
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 TestLink Plugin installation statusNavigate to Jenkins > Manage Jenkins > Manage Plugins > Installed tab, or inspect the Jenkins plugin directory for the testlink plugin folder. Determine if the plugin is present.Affected if The TestLink Plugin is installed and its version is 3.16 or earlier.
-
Determine the installed TestLink Plugin versionIn Jenkins, go to Manage Jenkins > Manage Plugins > Installed and locate TestLink Plugin to view its version. Alternatively, check the plugin's manifest or version file in the plugin directory on the Jenkins master filesystem.Affected if The installed version is 3.16 or lower.
-
Locate the plugin's global configuration fileSearch the Jenkins home directory for configuration files related to TestLink Plugin, typically named with the plugin identifier. Check common locations such as the Jenkins home root or within the plugin's dedicated configuration directory.Affected if A configuration file for the TestLink Plugin exists on the Jenkins master.
-
Inspect credentials storage formatOpen the TestLink Plugin configuration file using a text editor or command-line tool and examine whether credentials appear in plaintext (unencrypted) rather than in an encrypted or masked format.Affected if Credentials are stored in plaintext within the configuration file.
A user is affected if the TestLink Plugin version is 3.16 or earlier and plaintext credentials are present in its global configuration file on the Jenkins master.
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 the TestLink Plugin to version 3.17 or later, which encrypts credentials. Additionally, rotate any credentials that may have been exposed through this vulnerability.
Fix this in Testlink
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.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 $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-10378 — 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-10378 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