Skip to content

Jenkins OpsGenie Plugin vulnerable to Cleartext Transmission of Sensitive Information

Moderate severity GitHub Reviewed Published Jul 1, 2022 to the GitHub Advisory Database • Updated Oct 27, 2023

Package

maven org.jenkins-ci.plugins:opsgenie (Maven)

Affected versions

<= 1.9

Patched versions

None

Description

Jenkins OpsGenie Plugin 1.9 and earlier stores API keys unencrypted in its global configuration file com.opsgenie.integration.jenkins.OpsGenieNotifier.xml and in job config.xml files on the Jenkins controller as part of its configuration.

Additionally, they are transmitted in plain text as part of the respective configuration forms.

These API keys can be viewed by users with Item/Extended Read permission (job config.xml only) or access to the Jenkins controller file system (both).

As of publication of this advisory, there is no fix.

References

Published by the National Vulnerability Database Jun 30, 2022
Published to the GitHub Advisory Database Jul 1, 2022
Reviewed Jul 13, 2022
Last updated Oct 27, 2023

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

EPSS score

0.054%
(24th percentile)

Weaknesses

CVE ID

CVE-2022-34804

GHSA ID

GHSA-7r65-pjgv-h2h9

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.