CVE-2022-34803

Jenkins OpsGenie Plugin 1.9 and earlier stores API keys unencrypted in its global configuration file and in job config.xml files on the Jenkins controller where they can be viewed by users with Extended Read permission (config.xml), or access to the Jenkins controller file system.

Jenkins OpsGenie Plugin 1.9 and earlier stores API keys unencrypted in its global configuration file and in job config.xml files on the Jenkins controller where they can be viewed by users with Extended Read permission (config.xml), or access to the Jenkins controller file system.

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.

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.

Jenkins OpsGenie Plugin versiones 1.9 y anteriores, almacena las claves API sin encriptar en su archivo de configuración global y en los archivos config.xml de los trabajos en el controlador Jenkins, donde pueden ser visualizados por usuarios con permiso de Lectura Extendida (config.xml), o con acceso al sistema de archivos del controlador Jenkins