Improper Authorization Affecting jenkins-2-plugins package, versions *


Severity

Recommended
medium

Based on Red Hat Enterprise Linux security rating.

Threat Intelligence

EPSS
0.66% (80th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-RHEL7-JENKINS2PLUGINS-5273049
  • published26 Mar 2023
  • disclosed3 Jul 2020

Introduced: 3 Jul 2020

CVE-2020-7692  (opens in a new tab)
CWE-285  (opens in a new tab)
CWE-358  (opens in a new tab)

How to fix?

There is no fixed version for RHEL:7 jenkins-2-plugins.

NVD Description

Note: Versions mentioned in the description apply only to the upstream jenkins-2-plugins package and not the jenkins-2-plugins package as distributed by RHEL. See How to fix? for RHEL:7 relevant fixed versions and status.

PKCE support is not implemented in accordance with the RFC for OAuth 2.0 for Native Apps. Without the use of PKCE, the authorization code returned by an authorization server is not enough to guarantee that the client that issued the initial authorization request is the one that will be authorized. An attacker is able to obtain the authorization code using a malicious app on the client-side and use it to gain authorization to the protected resource. This affects the package com.google.oauth-client:google-oauth-client before 1.31.0.

CVSS Scores

version 3.1