Information Exposure Affecting jenkins-2-plugins package, versions *


Severity

Recommended
medium

Based on Red Hat Enterprise Linux security rating.

Threat Intelligence

EPSS
0.31% (70th 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-5251380
  • published26 Jul 2021
  • disclosed23 Apr 2021

Introduced: 23 Apr 2021

CVE-2021-26291  (opens in a new tab)
CWE-200  (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.

Apache Maven will follow repositories that are defined in a dependency’s Project Object Model (pom) which may be surprising to some users, resulting in potential risk if a malicious actor takes over that repository or is able to insert themselves into a position to pretend to be that repository. Maven is changing the default behavior in 3.8.1+ to no longer follow http (non-SSL) repository references by default. More details available in the referenced urls. If you are currently using a repository manager to govern the repositories used by your builds, you are unaffected by the risks present in the legacy behavior, and are unaffected by this vulnerability and change to default behavior. See this link for more information about repository management: https://maven.apache.org/repository-management.html

References

CVSS Scores

version 3.1