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’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

MCHECKSTYLE-366 Upgrade checkstyle to a more recent version #13

Closed
wants to merge 1 commit into from

Conversation

eolivelli
Copy link
Contributor

MCHECKSTYLE-366 Upgrade checkstyle to a more recent version
and require Java 8 as Checkstyle 7+ requires Java 8

Fix several integration tests that didn't work with new versions of checkstyle

and require Java 8 as Checkstyle 7+ requires Java 8
@eolivelli
Copy link
Contributor Author

@rnveach I have addressed your comment, please take another look

@eolivelli
Copy link
Contributor Author

@rnveach
Copy link
Contributor

rnveach commented Apr 22, 2019

Looks good, thanks.

@@ -20,8 +20,6 @@ under the License.
<!DOCTYPE module PUBLIC "-//Puppy Crawl//DTD Check Configuration 1.2//EN" "http://www.puppycrawl.com/dtds/configuration_1_2.dtd">
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

it would be good if you can update all xmls to have new DOCTYPE that reference to secure website.
Example: https://github.com/checkstyle/checkstyle/blob/master/config/checkstyle_checks.xml#L2
There should be no Puppy Crawl, no http://.

it is part of security issue - checkstyle/checkstyle#6478 and checkstyle/checkstyle#6474

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is a test resource

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@eolivelli , please address my comment, to avoid security issues in plugin.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@romani this file is a test resource, it is an integration test.
It would be better to create a specific JIRA and track the work to do.
I will be very happy to fix the problem you are reporting or to help your provide a patch.
This PR has already been merged, we should start a new one

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@eolivelli The security issue is in the parser that is used to parse this file. It leaves any code that parses this file vulnerable to XXE via a MITM.
It doesn't matter that it's a "test resource", it still leaves the build vulnerable to this attack vector.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I will create the ticket.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Here is the new ticket to provide any patches for: https://issues.apache.org/jira/browse/MCHECKSTYLE-375

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Great. If anyone wants to pick it up....I can wait for it before cutting the 3.1.0 release.
I am currently waiting for another patch se the is no hurry.

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@eolivelli , please share link to patch that you are waiting

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@romani this one #5

@eolivelli
Copy link
Contributor Author

This pr has been merged, sorry, I did not close it

@eolivelli eolivelli closed this Apr 23, 2019
@asfgit asfgit deleted the MCHECKSTYLE-366 branch February 12, 2020 22:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
4 participants