dependency-check-maven-config.xml

<?xml version="1.0" encoding="UTF-8"?>
<suppressions xmlns="https://jeremylong.github.io/DependencyCheck/dependency-suppression.1.1.xsd">

    <suppress>
        <notes>
            vorbis-java-tika-0.8.jar from tika-bundle-1.18.0_5.jar
            tika-parsers uses vorbis 0.8. That version is not upgraded in the latest tika-parsers version.
        </notes>
        <cve>CVE-2016-6809</cve>
        <cve>CVE-2018-1335</cve>
    </suppress>

    <!-- Remove this suppression CVE-2017-5644 once DDF-3064 has been resolved-->
    <suppress>
        <notes>
            This is not an issue since the vulnerability is in reading untrusted documents and
            platform-metrics-reporting only creates them. The issue is resolved in version 3.16 but
            will require code refactoring.
            poi-3.12.jar (cpe:/a:apache:poi:3.12, org.apache.poi:poi:3.12) : CVE-2017-5644
            ooxml-schemas-1.3.jar and ooxml-security-1.1.jar
        </notes>
        <cve>CVE-2017-5644</cve>
    </suppress>
    <suppress>
        <notes>
            FasterXML jackson-databind through 2.8.10 and 2.9.x through 2.9.3 allows unauthenticated
            remote code execution because of an incomplete fix for the CVE-2017-7525 deserialization
            flaw. This is exploitable by sending maliciously crafted JSON input to the
            readValue method of the ObjectMapper, bypassing a blacklist that is ineffective
            if the Spring libraries are available in the classpath.
            We have upgraded to 2.9.4 which fixes the issue but version 2.6.3 is still being used by
            org.apache.cxf:cxf-rt-rs-security-sso-saml -> ehcache-2.10.4 -> jackson-databind-2.6.3.
            solr-assembly.zip -> jackson-core-asl-1.9.13.jar
            This suppression can be removed when DDF-3593 has been completed.
        </notes>
        <cve>CVE-2016-3720</cve>
        <cve>CVE-2017-7525</cve>
        <cve>CVE-2017-15095</cve>
        <cve>CVE-2017-17485</cve>
        <cve>CVE-2018-7489</cve>

        <cve>CVE-2018-11307</cve>
        <cve>CVE-2018-14719</cve>
        <cve>CVE-2018-14718</cve>
        <cve>CVE-2018-14721</cve>
        <cve>CVE-2018-14720</cve>
        <cve>CVE-2018-19362</cve>
        <cve>CVE-2018-19361</cve>
        <cve>CVE-2018-19360</cve>
    </suppress>
    <suppress>
        <notes>
            file name: solr-*.jar
            OWASP is getting confused by our version number being on a jar with solr in the name we
            are on solr 6.6+ which is not affected by this issue.
        </notes>
        <cve>CVE-2012-6612</cve>
    </suppress>

    <!-- proxy-camel-servlet false positives - these are all because the proxy-camel-servlet is getting confused with the camel-servlet-->
    <suppress>
        <notes>
            This is an issue with Camel version before 2.16.1 OWASP appears to have confused the
            internal proxy-camel-servlet version with the overall Camel version - marking as false
            positive.
            ddf distribution -> org.apache.karaf.decanter.appender.camel-1.3.0.jar
        </notes>
        <cve>CVE-2014-0002</cve>
        <cve>CVE-2014-0003</cve>
        <cve>CVE-2015-5344</cve>
        <cve>CVE-2017-3159</cve>
        <cve>CVE-2017-12633</cve>
        <cve>CVE-2017-12634</cve>
        <cve>CVE-2016-8749</cve>
    </suppress>
    <suppress>
        <notes>
            This is an issue with Camel version before 2.16.1 OWASP appears to have confused the
            internal proxy-camel-servlet version with the overall Camel version - marking as false
            positive.
            org.apache.karaf.decanter.appender.camel-1.3.0.jar
            org.apache.karaf.decanter.collector.camel-tracer-1.3.0.jar
            org.apache.karaf.decanter.sla.camel-1.3.0.jar
        </notes>
        <cve>CVE-2014-0002</cve>
        <cve>CVE-2014-0003</cve>
        <cve>CVE-2015-5344</cve>
    </suppress>
    <suppress>
        <notes>
            <!-- these are the geowebcache vulnerabilities it is not installed by default and it is only
            experimental these security issues would need to be resolved before geowebcache can be
            installed in a production environment-->
            gwc-web-1.5.0.war: com.noelios.restlet-1.0.8.jar
            gwc-web-1.5.0.war: commons-beanutils-1.7.0.jar
            gwc-web-1.5.0.war: commons-collections-3.1.jar
            gwc-web-1.5.0.war: postgresql-8.4-701.jdbc3.jar
            gwc-web-1.9.1.war: commons-fileupload-1.2.1.jar, suppressing because the vulnerable class DiskFileItem is not used in the project
            gwc-web-1.9.1.war: gwc-sqlite-1.9.1.jar
            geowebcache-server-standalone-0.7.0.war: gwc-sqlite-1.9.1.jar
            geowebcache-server-standalone-0.7.0.war: sqlite-jdbc-3.8.6.jar
            geowebcache-server-standalone-0.7.0.war: commons-fileupload-1.2.1.jar
            solr-dependencies -> commons-configuration -> commons-beanutils
            org.codice:lux -> solr-core -> org.restlet-2.1.1.jar
        </notes>
        <cve>CVE-2016-3092</cve>
        <cve>CVE-2014-0050</cve>
        <cve>CVE-2013-4271</cve>
        <cve>CVE-2013-4221</cve>
        <cve>CVE-2014-0114</cve>
        <cve>CVE-2015-5895</cve>
        <cve>CVE-2015-3717</cve>
        <cve>CVE-2015-3416</cve>
        <cve>CVE-2015-3415</cve>
        <cve>CVE-2015-3414</cve>
        <cve>CVE-2017-10989</cve>
        <cve>CVE-2016-7048</cve>
        <cve>CVE-2019-8457</cve>
        <cve>CVE-2016-1000031</cve>
    </suppress>
    <suppress>
        <notes>
            These CVEs are incorrectly attributing a CXF vulnerability to Camel
            camel-cxf-2.19.0.jar.
            The CVEs are in CXF versions in this case the camel version is incorrectly being used
        </notes>
        <cve>CVE-2016-8739</cve>
    </suppress>
    <suppress>
        <notes>
            These CVEs are all related to asciidoc and jruby vulnerabilities which are only used
            when the documentation is building.
            asciidoctorj-1.5.6.jar: jruby_cache_backend.jar
            jruby-complete-9.0.4.0.jar: jopenssl.jar
            jruby-complete-9.0.4.0.jar: readline.jar
            jruby-complete-9.0.4.0.jar: cparse-jruby.jar
            jruby-complete-9.0.4.0.jar/META-INF/maven/com.boundary/high-scale-lib/pom.xml
        </notes>
        <cve>CVE-1999-0428</cve>
        <cve>CVE-2009-3245</cve>
        <cve>CVE-2010-0742</cve>
        <cve>CVE-2010-4252</cve>
        <cve>CVE-2011-4838</cve>
        <cve>CVE-2012-2110</cve>
        <cve>CVE-2014-3567</cve>
        <cve>CVE-2014-8176</cve>
        <cve>CVE-2015-0292</cve>
        <cve>CVE-2015-8768</cve>
        <cve>CVE-2016-2108</cve>
        <cve>CVE-2016-2109</cve>
    </suppress>
    <suppress>
        <notes>
            This CVE is related to hash collisions at the Java level. This is mitigated by newer
            versions of Java (8+).
            See http://openjdk.java.net/jeps/180 for more information.
            xercesImpl-2.11.0.jar
        </notes>
        <cve>CVE-2012-0881</cve>
    </suppress>
    <suppress>
        <notes>
            These CVEs apply to the Hawtio console which is not exposed in this system.
            artemis-core-client-2.1.0.jar and activemq-client-5.14.5.jar
        </notes>
        <cve>CVE-2015-5184</cve>
        <cve>CVE-2015-5183</cve>
    </suppress>
    <suppress>
        <notes>
            These CVEs apply to org.apache.geronimo:geronimo which is not a dependency of any of
            these artifacts.

            geronimo-activation_1.1_spec-1.1.jar
            geronimo-javamail_1.4_spec-1.7.1.jar
            geronimo-jms_1.1_spec-1.1.1.jar
            geronimo-jms_2.0_spec-1.0-alpha-2.jar
            geronimo-servlet_3.0_spec-1.0.jar
            geronimo-stax-api_1.0_spec-1.0.1.jar
            apache-karaf-4.1.2.tar.gz: apache-karaf-4.1.2.tar:
            org.apache.servicemix.specs.saaj-api-1.3-2.9.0.jar/META-INF/maven/org.apache.geronimo.specs/geronimo-saaj_1.3_spec/pom.xml
            apache-karaf-4.1.2.tar.gz: apache-karaf-4.1.2.tar:
            org.apache.servicemix.specs.jaxws-api-2.2-2.9.0.jar/META-INF/maven/org.apache.geronimo.specs/geronimo-jaxws_2.2_spec/pom.xml
            geronimo-javamail_1.4_mail-1.8.4.jar: transitive dependency of wss4j-ws-security-dom
        </notes>
        <cve>CVE-2011-5034</cve>
    </suppress>
    <suppress>
        <notes>
            This CVE applies to Apache-SSL 1.3.28+1.52 and earlier. It does not apply to the
            artifact that OWASP is reporting.
            apache-karaf-4.2.2.tar.gz: apache-karaf-4.2.2.tar:
            org.apache.servicemix.bundles.not-yet-commons-ssl-0.3.11_1.jar
        </notes>
        <cve>CVE-2004-0009</cve>
    </suppress>
    <suppress>
        <notes>
            Applies to an LDAP class that we do not use in the system.
            - groovy-all-2.4.7.jar is only used in tests.
            - rest-assured 2.9.0 uses groovy-2.4.4.jar and groovy-xml-2.4.4.jar
        </notes>
        <cve>CVE-2016-6814</cve>
    </suppress>
    <suppress>
        <notes>
            This CVE has been addressed by upgrading commons-beanutils to version 1.9.3. OWASP will
            continue to report the vulnerability since OWASP sees the DDF version instead of the
            actual version.
            security-pdp-authzrealm-2.11.4-SNAPSHOT.jar (cpe:/a:apache:commons_beanutils:2.11.4,
            cpe:/a:apache:commons_collections:2.11.4,
            ddf.security.pdp:security-pdp-authzrealm:2.11.4-SNAPSHOT)
            security-sts-attributequeryclaimshandler-2.17.0-SNAPSHOT.jar
        </notes>
        <cve>CVE-2017-15708</cve>
        <cve>CVE-2015-6420</cve>
    </suppress>
    <suppress>
        <notes>
            False positive. This CVE is for a Perl library
            Algorithmic complexity vulnerability in Address.pm in the Email-Address module 1.908 and earlier for Perl allows
            remote attackers to cause a denial of service (CPU consumption) via a crafted string containing a list of e-mail
            addresses in conjunction with parenthesis characters that can be associated with nested comments.
            NOTE: the default configuration in 1.908 mitigates this vulnerability but misparses certain realistic comments.
            platform-email-impl -> simple-java-mail-4.1.3.jar/META-INF/maven/com.github.bbottema/emailaddress-rfc2822/pom.xml
            simple-java-mail could be upgraded.
        </notes>
        <cve>CVE-2015-7686</cve>
    </suppress>
    <suppress>
        <notes>
            restito-0.8.2.jar: is still used in thirdparty/restito in DDF
        </notes>
        <cve>CVE-2015-1820</cve>
    </suppress>
    <suppress>
        <notes>This CVE is related to a PHP script. There are no PHP scripts in the DDF.</notes>
        <cve>CVE-2006-6460</cve>
    </suppress>
    <suppress>
        <notes>
            These CVEs are not an issue since the software is not exposing STOMP over WebSocket
            endpoints.
            security-sts-ldapclaimshandler -> spring-ldap-core -> spring-tx-4.3.4.RELEASE.jar
        </notes>
        <cve>CVE-2018-1270</cve>
        <cve>CVE-2018-1275</cve>
    </suppress>

    <suppress>
        <notes>
            These CVEs affect Jetty 9.3.x up to 9.3.23 and 9.4.x up to 9.4.10. DDF is using a
            version of jetty that does not fall within those ranges.
            However, org.apache.cxf:cxf-rt-ws-security:jar:3.2.6 uses ehcache:jar:2.10.5 which has a vulnerable jetty
            ehcache-2.10.5.jar/rest-management-private-classpath/META-INF/maven/org.eclipse.jetty/jetty-http/pom.xml
        </notes>
        <cve>CVE-2017-7658</cve>
        <cve>CVE-2017-7657</cve>
    </suppress>
    <suppress>
        <notes>
            Nearly all of these are not an issue because either we are not using those features
            entirely or (and in addition to the fact) that solr is now running as an external
            process and completely locked down, so no one could access solr to take advantage of
            these vulnerabilities. All communication is controlled by DDF.

            kernel -> solr-assembly.zip -> velocity-tools-2.0.jar
        </notes>
        <cve>CVE-2016-3081</cve>
        <cve>CVE-2013-4316</cve>
        <cve>CVE-2016-4436</cve>
        <cve>CVE-2013-2115</cve>
        <cve>CVE-2012-0391</cve>
        <cve>CVE-2016-3082</cve>
        <cve>CVE-2013-2135</cve>
        <cve>CVE-2014-0112</cve>
        <cve>CVE-2012-0838</cve>
        <cve>CVE-2013-1965</cve>
        <cve>CVE-2013-1966</cve>
        <cve>CVE-2014-0113</cve>
        <cve>CVE-2013-2134</cve>
        <cve>CVE-2013-2251</cve>
        <cve>CVE-2016-0785</cve>
        <cve>CVE-2016-4461</cve>
    </suppress>
    <suppress>
        <notes>
            Apache httpd vulnerabilities inaccurately associated with artemis-server-osgi-2.4.0.jar
            and cxf-rt-transports-http-netty-server-3.2.5.jar in the DDF distribution.
            artemis-server-osgi-2.6.2.jar
            cxf-rt-transports-http-netty-server-3.2.6.jar
        </notes>
        <cve>CVE-1999-0236</cve>
        <cve>CVE-1999-1237</cve>
        <cve>CVE-1999-1412</cve>
        <cve>CVE-2007-0086</cve>
        <cve>CVE-2007-4723</cve>
        <cve>CVE-2009-1955</cve>
        <cve>CVE-2009-3095</cve>
        <cve>CVE-2007-6423</cve>
        <cve>CVE-2010-0425</cve>
        <cve>CVE-2009-1890</cve>
        <cve>CVE-2009-1891</cve>
    </suppress>
    <suppress>
        <notes>
            A CVE against slf4j for the class "EventData", which is not used in DDF or pax-logging.
        </notes>
        <cve>CVE-2018-8088</cve>
    </suppress>
    <suppress>
        <notes>
            A CVE against tomcat-embed-jasper, which is brought in transitively from pax-web-jsp.
            The CVE applies to the Windows command-line, which has no impact on DDF as it is used.
        </notes>
        <cve>CVE-2019-0232</cve>
    </suppress>
    <suppress>
        <notes>
            This vulnerability is related to the use of Apache Hadoop YARN. YARN is a resource
            management application for Hadoop. DDF only include Hadoop JAR files to support Solr
            dependencies. DDF does not make use of YARN.

            solr-dependencies -> hadoop-auth-2.7.4.jar (latest versions available)
            org.codice:lux -> solr-core -> hadoop-auth-2.2.0.jar
        </notes>
        <cve>CVE-2018-8029</cve>
        <cve>CVE-2018-11766</cve>
        <cve>CVE-2016-6811</cve>
        <cve>CVE-2017-3162</cve>
    </suppress>

</suppressions>