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

cleanup already resolved CVEs #15447

Merged

Conversation

janjwerner-confluent
Copy link
Contributor

Description

Remove the crud from the dependency-check suppression file

This PR has:

  • been self-reviewed.
  • added documentation for new or modified features or behaviors.
  • a release note entry in the PR description.
  • added Javadocs for most classes and all non-trivial methods. Linked related entities via Javadoc links.
  • added or updated version, license, or notice information in licenses.yaml
  • added comments explaining the "why" and the intent of the code wherever would not be obvious for an unfamiliar reader.
  • added unit tests or modified existing tests to cover new code paths, ensuring the threshold for code coverage is met.
  • added integration tests.
  • been tested in a test Druid cluster.

@abhishekagarwal87
Copy link
Contributor

In this PR, we had removed the dependency check on contrib extensions. Can you run the check manually to ensure that you are not removing genuine suppressions for contrib extensions?

Copy link
Contributor

@abhishekagarwal87 abhishekagarwal87 left a comment

Choose a reason for hiding this comment

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

left some comments. thanks for cleaning this up.

<notes><![CDATA[
file name: hadoop-*-3.3.1.jar
]]></notes>
<cve>CVE-2015-7430</cve>
Copy link
Contributor

Choose a reason for hiding this comment

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

The justification is lost during refactoring

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Added a bit of context.

<cve>CVE-2023-31419</cve>
</suppress>

<suppress>
Copy link
Contributor

Choose a reason for hiding this comment

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

can you add justifications for the suppressions?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Added a bit of context.

@janjwerner-confluent
Copy link
Contributor Author

In this PR, we had removed the dependency check on contrib extensions. Can you run the check manually to ensure that you are not removing genuine suppressions for contrib extensions?

@abhishekagarwal87
Which PR do you refer to?

In this PR, we had removed the dependency check on contrib extensions. Can you run the check manually to ensure that you are not removing genuine suppressions for contrib extensions?

It seems I have removed suppressions for some of the contrib extensions, however as I started re-adding them, there is even more issues in them (re-enabled scans for all the contrib repos and oh my!)
How would you like to proceed given that those extensions are not scanned anyways?

@abhishekagarwal87
Copy link
Contributor

oops. I missed to post the link - #15026

@abhishekagarwal87
Copy link
Contributor

I was initially thinking that we keep the old suppressions anyway but it's probably better to get rid of those if we are not doing a scan anyway.

@janjwerner-confluent
Copy link
Contributor Author

I'm almost done adding suppressions for the remaining modules - there are plenty missing from pre-pruning. I have not added reasoning to those.
Just checked the other PR and the discussion - are there criteria of removing an extension from Druid contrib? there are some pieces of code that were not touched for ~ 5 years.

@abhishekagarwal87
Copy link
Contributor

To remove an extension that is not being maintained, you can start a thread on dev@druid.apache.org. If there is consensus, we can remove the extension.

<cve>CVE-2021-33813</cve>
</suppress>
<notes><![CDATA[
file name: hadoop-*-3.3.1.jar
Copy link
Contributor

Choose a reason for hiding this comment

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

I think they are because of hadoop-shaded-guava which has a version of 1.1.1

Copy link
Contributor Author

Choose a reason for hiding this comment

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

do we need additional justification for those?

owasp-dependency-check-suppressions.xml Outdated Show resolved Hide resolved
owasp-dependency-check-suppressions.xml Outdated Show resolved Hide resolved
@janjwerner-confluent
Copy link
Contributor Author

the last run seems to be mis-reporting for a spurious failure in the run, end result is OK

@abhishekagarwal87 abhishekagarwal87 merged commit a469c53 into apache:master Dec 5, 2023
89 checks passed
@LakshSingla LakshSingla removed this from the 28.0.1 milestone Dec 7, 2023
@LakshSingla LakshSingla added this to the 29.0.0 milestone Jan 29, 2024
Sign up for free to 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.

None yet

3 participants