Skip to content

minor: suppress some CVEs #19384

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.

Sign up for GitHub

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

Merged
cecemei merged 1 commit into from
Apr 28, 2026
+20 −0
Merged

minor: suppress some CVEs #19384

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
20 changes: 20 additions & 0 deletions owasp-dependency-check-suppressions.xml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -146,6 +146,7 @@
<cve>CVE-2024-9823</cve> <!-- This is in hadoop's shadded jetty. no version of hadoop has updated to fixed version. It is a jetty server vuln, which should not be exploitable in hadoop client code -->
<cve>CVE-2025-27821</cve> <!-- native hdfs vulnerability -->
<cve>CVE-2025-5115</cve> <!-- netty issue in shaded hadoop -->
<cve>CVE-2026-5795</cve> <!-- This affects Jetty JASPIAuthenticator (jetty-security module). The application only includes shaded jetty-io, which does not contain the vulnerable classes. -->
</suppress>

<!-- those are false positives, no other tools report any of those CVEs in the hadoop package -->
Expand Down Expand Up @@ -594,6 +595,16 @@
<cve>CVE-2023-26464</cve>
</suppress>

<suppress>
<notes><![CDATA[
file name: log4j-*-2.25.3.jar (all log4j artifacts)
Copy link
Copy Markdown
Contributor

@capistrant capistrant Apr 28, 2026

Choose a reason for hiding this comment

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

why not just do the patch version bump for the log4j dependency instead?

Copy link
Copy Markdown
Contributor Author

@cecemei cecemei Apr 28, 2026

Choose a reason for hiding this comment

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

flexible either way, but i'm just thinking that since we've decided we're not affected then we should not need to change the version or roll out security patch for released versions

]]></notes>
<packageUrl regex="true">^pkg:maven/org\.apache\.logging\.log4j/log4j-.*@.*$</packageUrl>
<cve>CVE-2026-34478</cve>
<cve>CVE-2026-34480</cve>
<cve>CVE-2026-34481</cve>
</suppress>

<suppress>
<!--
- TODO: The lastest version of ambari-metrics-common is 2.7.0.0.0, released in July 2018.
Expand Down Expand Up @@ -760,4 +771,13 @@
<packageUrl regex="true">^pkg:maven/io\.grpc/grpc-.*@.*$</packageUrl>
<cve>CVE-2026-33186</cve> <!-- Only applicable to gRPC Go (google.golang.org/grpc < 1.79.3), not gRPC Java - https://nvd.nist.gov/vuln/detail/CVE-2026-33186 -->
</suppress>

<suppress>
<notes><![CDATA[
file name: pac4j-*-5.7.3.jar (all pac4j artifacts)
]]></notes>
<packageUrl regex="true">^pkg:maven/org\.pac4j/pac4j-.*@5\.7\.3$</packageUrl>
<cve>CVE-2026-40458</cve> <!-- CSRF vulnerability - not applicable as Druid explicitly disables CSRF checks by using authorizer="none" in Pac4jFilter for API/web service usage -->
<cve>CVE-2026-40459</cve> <!-- LDAP injection vulnerability - not applicable as Druid uses OIDC authentication (pac4j-oidc), not LDAP authentication -->
</suppress>
</suppressions>
Loading