Spira ImporterApplication · Jenkins
CVE-2019-16543
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 Spira Importer Plugin 3.2.2 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 Spira Importer Plugin version 3.2.2 and earlier stores credentials in plaintext within its global configuration file on the Jenkins master filesystem. Users who have file system 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
Spira ImporterApplication
<= 3.2.2CVSS 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
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/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 if Spira Importer Plugin is installedNavigate to Jenkins > Manage Jenkins > Manage Plugins > Installed tab and search for 'Spira Importer' in the list of installed plugins, or use the Jenkins CLI: java -jar jenkins-cli.jar list-pluginsAffected if The Spira Importer plugin appears in the installed plugins list
-
Check the installed plugin versionIn Jenkins > Manage Jenkins > Manage Plugins > Installed, locate the Spira Importer plugin and note the version number displayed in the 'Version' columnAffected if The version is 3.2.2 or lower (any version up to and including 3.2.2)
-
Locate the plugin configuration fileOn the Jenkins master filesystem, navigate to $JENKINS_HOME and search for configuration files related to Spira, typically named 'org.jenkinsci.plugins.spira_importer.xml' or similar under the $JENKINS_HOME directoryAffected if A configuration file exists in the Jenkins home directory with 'spira' in the filename
-
Inspect configuration file for plaintext credentialsOpen the Spira Importer configuration file using a text editor or cat command, and look for credential fields (such as username, password, API key, or URL) - check if these values appear in plaintext rather than being encrypted or maskedAffected if Credentials (usernames, passwords, API keys, or similar secrets) appear as readable plaintext strings within the XML or config file
A user is affected if the Spira Importer Plugin version is 3.2.2 or lower AND the configuration file contains unencrypted plaintext credentials.
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 Spira Importer Plugin to a version newer than 3.2.2 that encrypts stored credentials, and rotate any credentials that may have been exposed through this vulnerability.
Fix this in Spira Importer
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.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,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-16543 — 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-16543 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