Missing authorization in Jenkins RQM Plugin
Key facts
- Attack vector
- Network
- Privileges required
- Low
- User interaction
- None
- Attack complexity
- Low
- Impact type
- Security bypass
- Confidentiality · integrity · availability
- High · None · None
- Fix status
- No fix listed
Attack profile from CVSS 3.1 · NVD. Fix status from CNA and GitHub. Impact type from CWE-862.
Summary
A missing check in Jenkins RQM Plugin 2.8 and earlier allows attackers with Overall/Read permission to enumerate credentials IDs of credentials stored in Jenkins.
Why it matters now
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| Jenkins | Jenkins RQM Plugin | up to 2.8 | — | No fix listed | CNA |
| — | net.praqma:rqm-plugin (Maven) | up to 2.8 | — | No fix listed | GHSA-2348-ccqj-8p27 |
- Jenkins RQM Plugin VendorJenkins Affected up to 2.8 Fixed in — No fix listed CNA
- net.praqma:rqm-plugin (Maven) Vendor— Affected up to 2.8 Fixed in — No fix listed GHSA-2348-ccqj-8p27
Remediation
No fixed version listed by the sources yet.
Fixed in the same release
Records fixed by the same vendor advisory or release, as the CNA lists them.
- Release ·
Jenkins RQM Plugin unspecified
2 records Highest priority Priority LOW 2 LOW
Other records, highest priority first
- TI-2022-15616 Insufficiently protected credentials in Jenkins RQM PluginPriority LOW 30
Timeline
- 2026-10-02 Threatist record created from CVE-2022-34810
- 2026-10-03 Alias added: GHSA-2348-ccqj-8p27
References
More Jenkins Rqm vulnerabilities
- TI-2022-19751 Jenkins RQM Plugin 2.8 and earlier does not configure its XML parser to prevent XML external entity (XXE) attacks. CVSS 3.1CRITICAL 9.8
- TI-2022-15616 Insufficiently protected credentials in Jenkins RQM Plugin CVSS 3.1MEDIUM 6.5
Sources
- CVE-2022-34810 · CVE Program
- CVE-2022-34810 · NVD
- FIRST EPSS
- GHSA-2348-ccqj-8p27 · GitHub Advisory Database · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences