Advisory Published
Updated

REDHAT-BUG-1949638

First published: Wed Apr 14 2021(Updated: )

In Gradle from version 5.1 and before version 7.0 there is a vulnerability which can lead to information disclosure and/or dependency poisoning. Repository content filtering is a security control Gradle introduced to help users specify what repositories are used to resolve specific dependencies. This feature was introduced in the wake of the "A Confusing Dependency" blog post. In some cases, Gradle may ignore content filters and search all repositories for dependencies. This only occurs when repository content filtering is used from within a `pluginManagement` block in a settings file. This may change how dependencies are resolved for Gradle plugins and build scripts. For builds that are vulnerable, there are two risks: 1) Information disclosure: Gradle could make dependency requests to repositories outside your organization and leak internal package identifiers. 2) Dependency poisoning/Dependency confusion: Gradle could download a malicious binary from a repository outside your organization due to name squatting. For a full example and more details refer to the referenced GitHub Security Advisory. The problem has been patched and released with Gradle 7.0. Users relying on this feature should upgrade their build as soon as possible. As a workaround, users may use a company repository which has the right rules for fetching packages from public repositories, or use project level repository content filtering, inside `buildscript.repositories`. This option is available since Gradle 5.1 when the feature was introduced. Reference: <a href="https://github.com/gradle/gradle/security/advisories/GHSA-jvmj-rh6q-x395">https://github.com/gradle/gradle/security/advisories/GHSA-jvmj-rh6q-x395</a>

Affected SoftwareAffected VersionHow to fix
Gradle>=5.1<7.0

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Frequently Asked Questions

  • What is the severity of REDHAT-BUG-1949638?

    The severity of REDHAT-BUG-1949638 is classified as high due to the potential for information disclosure and dependency poisoning.

  • What software is affected by REDHAT-BUG-1949638?

    REDHAT-BUG-1949638 affects Gradle versions from 5.1 to 7.0.

  • How do I fix REDHAT-BUG-1949638?

    To fix REDHAT-BUG-1949638, upgrade Gradle to version 7.0 or later.

  • What vulnerabilities are associated with REDHAT-BUG-1949638?

    REDHAT-BUG-1949638 is associated with vulnerabilities related to information disclosure and dependency poisoning.

  • Is there a workaround for REDHAT-BUG-1949638?

    Currently, no official workaround is suggested for REDHAT-BUG-1949638 other than upgrading Gradle.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2025 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203