Skip to content

TEZ-4422 : [CVE-2021-43138] Upgrade async from 2.3.0 to 2.6.4 - #217

Merged
abstractdog merged 1 commit into
apache:masterfrom
amanraj2520:TEZ-4422_AsyncUpgrade
Jun 15, 2022
Merged

TEZ-4422 : [CVE-2021-43138] Upgrade async from 2.3.0 to 2.6.4#217
abstractdog merged 1 commit into
apache:masterfrom
amanraj2520:TEZ-4422_AsyncUpgrade

Conversation

@amanraj2520

@amanraj2520amanraj2520 commented Jun 7, 2022

Copy link
Copy Markdown
Contributor

Upgrade async from 2.3.0 to 2.6.4 to fix the vulnerability. Also an upgrade of yarn version to 1.6.0 and frontend maven plugin to 1.8.0 was done along with this change. Link to JIRA : https://issues.apache.org/jira/browse/TEZ-4422

Link to parent JIRA : https://issues.apache.org/jira/browse/TEZ-4419

RFC documentation : https://github.com/yarnpkg/rfcs/blob/master/implemented/0000-selective-versions-resolutions.md

…the vulnerability. Also an upgrade of yarn version to 1.6.0 and frontend maven plugin to 1.8.0 was done.
@amanraj2520

Copy link
Copy Markdown
ContributorAuthor

@abstractdog Can you please review this PR. As suggested by you, I am raising individual PR's for the TEZ-4419 parent issue.

@tez-yetus

Copy link
Copy Markdown

💔 -1 overall

VoteSubsystemRuntimeComment
+0 🆗reexec13m 49sDocker mode activated.
_ Prechecks _
+1 💚dupname0m 0sNo case conflicting files found.
+1 💚@author0m 0sThe patch does not contain any @author tags.
-1 ❌test4tests0m 0sThe patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.
_ master Compile Tests _
+0 🆗mvndep6m 49sMaven dependency ordering for branch
+1 💚mvninstall11m 8smaster passed
+1 💚compile3m 44smaster passed with JDK Private Build-11.0.15+10-Ubuntu-0ubuntu0.20.04.1
+1 💚compile3m 21smaster passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07
+1 💚javadoc2m 52smaster passed with JDK Private Build-11.0.15+10-Ubuntu-0ubuntu0.20.04.1
+1 💚javadoc2m 13smaster passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07
_ Patch Compile Tests _
+0 🆗mvndep0m 17sMaven dependency ordering for patch
+1 💚mvninstall6m 33sthe patch passed
+1 💚compile3m 34sthe patch passed with JDK Private Build-11.0.15+10-Ubuntu-0ubuntu0.20.04.1
+1 💚javac3m 34sthe patch passed
+1 💚compile3m 19sthe patch passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07
+1 💚javac3m 19sthe patch passed
+1 💚whitespace0m 0sThe patch has no whitespace issues.
+1 💚xml0m 3sThe patch has no ill-formed XML file.
+1 💚javadoc2m 38sthe patch passed with JDK Private Build-11.0.15+10-Ubuntu-0ubuntu0.20.04.1
+1 💚javadoc2m 11sthe patch passed with JDK Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07
_ Other Tests _
+1 💚unit2m 17stez-ui in the patch passed.
+1 💚unit70m 6sroot in the patch passed.
+1 💚asflicense1m 9sThe patch does not generate ASF License warnings.
137m 18s
SubsystemReport/Notes
DockerClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/tez-multibranch/job/PR-217/1/artifact/out/Dockerfile
GITHUB PR#217
Optional Testsdupname asflicense javac javadoc unit xml compile
unameLinux 95e936e1f84c 4.15.0-169-generic #177-Ubuntu SMP Thu Feb 3 10:50:38 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
Build toolmaven
Personalitypersonality/tez.sh
git revisionmaster / e5a5578
Default JavaPrivate Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07
Multi-JDK versions/usr/lib/jvm/java-11-openjdk-amd64:Private Build-11.0.15+10-Ubuntu-0ubuntu0.20.04.1 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_312-8u312-b07-0ubuntu1~20.04-b07
Test Resultshttps://ci-hadoop.apache.org/job/tez-multibranch/job/PR-217/1/testReport/
Max. process+thread count1484 (vs. ulimit of 5500)
modulesC: tez-ui . U: .
Console outputhttps://ci-hadoop.apache.org/job/tez-multibranch/job/PR-217/1/console
versionsgit=2.25.1 maven=3.6.3
Powered byApache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.

Comment threadpom.xml
<protoc.path>${env.PROTOC_PATH}</protoc.path>
<scm.url>scm:git:https://gitbox.apache.org/repos/asf/tez.git</scm.url>
<frontend-maven-plugin.version>1.4</frontend-maven-plugin.version>
<frontend-maven-plugin.version>1.8.0</frontend-maven-plugin.version>

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

is this related to async upgrade?

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

please confirm this one

Copy link
Copy Markdown
ContributorAuthor

Choose a reason for hiding this comment

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

@abstractdog I confirm this change

Comment threadtez-ui/pom.xml
<configuration>
<nodeVersion>${nodeVersion}</nodeVersion>
<yarnVersion>v0.21.3</yarnVersion>
<yarnVersion>v1.6.0</yarnVersion>

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

is this related to async upgrade?

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

please confirm this one

Copy link
Copy Markdown
ContributorAuthor

Choose a reason for hiding this comment

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

@abstractdog I confirm this change

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

I mean, this looks like a major version change of yarn, can you please let me know how is this related to the CVE patch (or is it necessary)?
I prefer doing version changes in separate patches if they're not closely related

Copy link
Copy Markdown
ContributorAuthor

Choose a reason for hiding this comment

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

@abstractdog The yarnVersion was changed since the selective dependency feature is only supported in yarn 1.0 and above. And yarnVersion of 1.6.0 is compatible with frontend maven plugin 1.8.0. That's why I did this change.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

cool, thanks for clarifying @amanraj2520 !

lodash@^4.14.0:
version "4.17.4"
resolved "https://registry.yarnpkg.com/lodash/-/lodash-4.17.4.tgz#78203a4d1c328ae1d86dca6460e369b57f4055ae"
lodash@^4.17.14:

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

is this related to async upgrade?

Copy link
Copy Markdown
ContributorAuthor

Choose a reason for hiding this comment

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

@abstractdog Yes these are related to async upgrade. The yark.lock file is automatically updated based on package.json.

@abstractdog

Copy link
Copy Markdown
Contributor

left minor comments
I'm fine with upgrading single dependencies separately until Ember3 upgrade is not finished (it looks like a huge PR) if they don't clash with each other

@amanraj2520

Copy link
Copy Markdown
ContributorAuthor

@abstractdog@guptanikhil007 Should we first merge the Ember3 upgrade or push these vulnerability fixes first?

@abstractdog

Copy link
Copy Markdown
Contributor

I don't think it's a problem to merge these version bumps first, and then do Ember3 update later when @jteagles has the bandwidth for it, please let me know @jteagles if have any objections with this

@amanraj2520

Copy link
Copy Markdown
ContributorAuthor

Yes I think we are good with these changes from our side. I have run tests locally as well with this PR. According to me we can go ahead with this merge @abstractdog

@abstractdog
abstractdog self-requested a review June 13, 2022 09:37

@abstractdogabstractdog left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

+1 LGTM

I'm merging in 12 hours if there are no further comments

@amanraj2520

Copy link
Copy Markdown
ContributorAuthor

@abstractdog Can we please merge this PR. I will raise PR's for remaining vulnerabilities as well after this.

@amanraj2520

Copy link
Copy Markdown
ContributorAuthor

@abstractdog Just a gentle reminder, can you please merge this PR

@abstractdog
abstractdog merged commit 3da8438 into apache:masterJun 15, 2022
@abstractdog

Copy link
Copy Markdown
Contributor

merged, sorry for the delay!

Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants

@amanraj2520@tez-yetus@abstractdog@guptanikhil007