CVE-2022-41248 json
Jenkins BigPanda Notifier Plugin Missing Password Field Masking
published 4y ago modified 4mo ago also GHSA-cpm5-cqr9-7p79 , EUVD-2022-6781
- cvss
- 5.3
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 34%
- public exploits
- 0
- none known
Summary
Jenkins BigPanda Notifier Plugin 1.4.0 and earlier does not mask the BigPanda API key on the global configuration form, increasing the potential for attackers to observe and capture it.
Is CVE-2022-41248 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- last yr.
Exploit prediction
0.40% chance of exploitation in the next 30 days, higher than 34% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 5.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N |
| NVD | 3.1 | 5.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N |
| CNA | 3.1 | 5.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N |
| GitHub | 3.1 | 3.3 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| maven | org.jenkins-ci.plugins:bigpanda-jenkins | <=1.4.0 |
no fix listed |
Affected products
- Jenkins project Jenkins BigPanda Notifier Plugin
Classification
References
-
jenkins.io
/security/advisory/2022-09-21/#SECURITY-2243
web, vendor-advisory
-
openwall.com
/lists/oss-security/2022/09/21/5
mailing-list, web, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2022-41248
advisory
-
github.com
/jenkinsci/bigpanda-plugin
package
Sources
- CVE List CVE-2022-41248
- GitHub Advisory GHSA-cpm5-cqr9-7p79
- NVD CVE-2022-41248
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.