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

CVE-2021-35516 in dependency org.apache.commons:commons-compress #4308

Closed
redcatbear opened this issue Jul 28, 2021 · 8 comments
Closed

CVE-2021-35516 in dependency org.apache.commons:commons-compress #4308

redcatbear opened this issue Jul 28, 2021 · 8 comments

Comments

@redcatbear
Copy link

Situation

Testcontainers depends on org.apache.commons:commons-compress version 1.20, which has a reported vulnerability CVE-2021-35516. Specially crafted archives can be used to allocate large amounts of memory, resulting in DoS.

Solution

Please update dependency:

<dependency>
  <groupId>org.apache.commons</groupId>
  <artifactId>commons-compress</artifactId>
  <version>1.21</version>
</dependency>
@kiview
Copy link
Member

kiview commented Jul 28, 2021

Thanks for bringing this to our attention @redcatbear.

Please note that this is not an attack vector for normal Testcontainer usage scenarios and is unlikely to have exploitable consequences.

@redcatbear
Copy link
Author

Thanks for recognizing the issue. I agree that the use case for an exploit is not the typical testcontainer scenario. Still it is a good idea to keep ones software as clean as possible and the fix in this case is luckily trivial.

@moritzluedtke
Copy link

moritzluedtke commented Sep 29, 2021

Just as an addition:
CVE-2021-35517, CVE-2021-35515 and CVE-2021-36090 are also reported on commons-compress-1.20.jar when running the OWASP check and using Testcontainers 1.16.0.

@kiview Do you have an estimate on when the dependency bump will be released?

@moritzluedtke
Copy link

moritzluedtke commented Nov 1, 2021

This issue is now over 3 month old. Any update on when this will be addressed? @kiview

@moritzluedtke
Copy link

This seems to be fixed (at least in 1.16.2). It would have been nice to include this issue in the release notes.

@rnorth
Copy link
Member

rnorth commented Nov 1, 2021

@moritzluedtke sorry, looks like we missed this in the release notes. Will add now.

@rnorth rnorth added this to the 1.16.1 milestone Nov 1, 2021
@moritzluedtke
Copy link

@rnorth Thank you!

@eddumelendez
Copy link
Member

Closing due to it was fixed last year.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants