How severe is CVE-2019-16543?

No CVSS score has been assigned to CVE-2019-16543 yet. Review the advisory details and affected package list to assess your exposure.

How do I fix CVE-2019-16543?

Update com.inflectra.spiratest.plugins:inflectra-spira-integration to 3.2.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2019-16543 is resolved across your whole dependency graph.

How do I detect CVE-2019-16543 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.inflectra.spiratest.plugins:inflectra-spira-integration, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2019-16543 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is CVE-2019-16543 actively exploited in the wild?

No public exploit code has been indexed for CVE-2019-16543 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2019-16543?

CVE-2019-16543 has an EPSS (Exploit Prediction Scoring System) score of 0.3%, placing it in the 25th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2019-16543?

CVE-2019-16543 is classified as CWE-522 (CWE-522). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2019-16543 published, and has it been updated?

CVE-2019-16543 was published on May 24, 2022 and was last updated on November 28, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕ Maven

Not in CISA KEV

CVE-2019-16543 — inflectra-spira-integrati…

CVE-2019-16543 is a CWE-522 vulnerability in com.inflectra.spiratest.plugins:inflectra-spira-integration. A fix is available for com.inflectra.spiratest.plugins:inflectra-spira-integration — see the affected versions and patch details below.

Plaintext Storage in Jenkins Spira Importer Plugin

Published

May 24, 2022

Updated

Nov 28, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 5, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

0.3%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs25th percentile — riskier than 25% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

☕com.inflectra.spiratest.plugins:inflectra-spira-integration

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

Jenkins 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.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`com.inflectra.spiratest.plugins:inflectra-spira-integration`	all versions	3.2.3`com.inflectra.spiratest.plugins:inflectra-spira-integration:3.2.3`

Affected Products

1 product · 1 configurations

Application

spira importerjenkins

≤ 3.2.2

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.inflectra.spiratest.plugins:inflectra-spira-integration, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update com.inflectra.spiratest.plugins:inflectra-spira-integration to 3.2.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2019-16543 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2019-16543 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works