Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update dependency com.puppycrawl.tools:checkstyle to v8.29 [SECURITY] - autoclosed #397

Conversation

ghost
Copy link

@ghost ghost commented Jun 28, 2020

This PR contains the following updates:

Package Update Change
com.puppycrawl.tools:checkstyle (source) minor 8.0 -> 8.29

GitHub Vulnerability Alerts

CVE-2019-9658

Checkstyle prior to 8.18 loads external DTDs by default, which can potentially lead to denial of service attacks or the leaking of confidential information.

CVE-2019-10782

Due to an incomplete fix for CVE-2019-9658, checkstyle was still vulnerable to XML External Entity (XXE) Processing.

Impact

User: Build Maintainers

This vulnerability probably doesn't impact Maven/Gradle users as, in most cases, these builds are processing files that are trusted, or pre-vetted by a pull request reviewer before being run on internal CI infrastructure.

User: Static Analysis as a Service

If you operate a site/service that parses "untrusted" Checkstyle XML configuration files, you are vulnerable to this and should patch.

Note from the discoverer of the original CVE-2019-9658:

While looking at a few companies that run Checkstyle/PMD/ect... as a service I notice that it's a common pattern to run the static code analysis tool inside of a Docker container with the following flags:

--net=none \
--privileged=false \
--cap-drop=ALL

Running the analysis in Docker has the advantage that there should be no sensitive local file information that XXE can exfiltrate from the container. Additionally, these flags prevent vulnerabilities in static analysis tools like Checkstyle from being used to exfiltrate data via XXE or to perform SSRF.
- Jonathan Leitschuh

Patches

Has the problem been patched? What versions should users upgrade to?

Patched, will be released with version 8.29 at 26 Jan 2020.

Workarounds

Is there a way for users to fix or remediate the vulnerability without upgrading?

No workaround are available

References

For more information

If you have any questions or comments about this advisory:


Renovate configuration

馃搮 Schedule: "" in timezone America/Argentina/Buenos_Aires.

馃殾 Automerge: Disabled by config. Please merge this manually once you are satisfied.

鈾伙笍 Rebasing: Whenever PR becomes conflicted, or if you modify the PR title to begin with "rebase!".

馃敃 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

@ghost ghost force-pushed the renovate-maven-com.puppycrawl.tools-checkstyle-vulnerability branch from d65cd2b to b855c79 Compare July 1, 2020 19:58
@ghost ghost force-pushed the renovate-maven-com.puppycrawl.tools-checkstyle-vulnerability branch from b855c79 to 31069d8 Compare November 4, 2020 13:47
@ghost ghost force-pushed the renovate-maven-com.puppycrawl.tools-checkstyle-vulnerability branch from 31069d8 to 914cc53 Compare December 3, 2020 20:56
@ghost ghost changed the title Update dependency com.puppycrawl.tools:checkstyle to v8.29 [SECURITY] Update dependency com.puppycrawl.tools:checkstyle to v8.29 [SECURITY] - autoclosed Dec 17, 2020
@ghost ghost closed this Dec 17, 2020
@ghost ghost deleted the renovate-maven-com.puppycrawl.tools-checkstyle-vulnerability branch December 17, 2020 17:16
This pull request was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant