forked from codice/ddf
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathdependency-check-maven-config.xml
185 lines (178 loc) · 7.27 KB
/
dependency-check-maven-config.xml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
<?xml version="1.0" encoding="UTF-8"?>
<suppressions xmlns="https://www.owasp.org/index.php/OWASP_Dependency_Check_Suppression">
<!-- 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
</notes>
<cve>CVE-2017-5644</cve>
</suppress>
<suppress>
<notes>
CVE-2004-0009 is an issue with Apache not-yet-commons-ssl. This jar has been stripped
from the distribution, the suppression is to prevent OWASP from complaining.
apache-karaf-4.1.2.tar.gz: apache-karaf-4.1.2.tar:
org.apache.servicemix.bundles.not-yet-commons-ssl-0.3.11_1.jar
</notes>
<cve>CVE-2004-0009</cve>
</suppress>
<suppress>
<notes>
this CVE is generating a lot of false positives it should only include
jackson-dataformat-xml jar but it is catching all jackson dependencies unfortunately I
can't fix it so if we start depending on a vulnerable version of jackson-dataformat-xml
this will still suppress it.
</notes>
<cve>CVE-2016-3720</cve>
</suppress>
<suppress>
<notes>
CVE-2008-0660 is a stack based buffer overflow vulnerability related to ActiveX and
several image uploaders. This is unrelated to presto-parser, so marking as a false
positive.
</notes>
<cve>CVE-2008-0660</cve>
</suppress>
<suppress>
<notes>
CVE-2016-1000031: Applies to commons-fileupload-1.2.1, suppressing because the
vulnerable class DiskFileItem is not used in the project
</notes>
<cve>CVE-2016-1000031</cve>
</suppress>
<suppress>
<notes>
False positive. This cve is not related to pax-url-aether.
pax-url-aether-2.4.7.jar
</notes>
<cve>CVE-2016-0749</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.0+ which is not affected by this issue.
</notes>
<cve>CVE-2012-6612</cve>
</suppress>
<suppress>
<notes>
file name: commons-beanutils-1.8.3.jar
shiro-core has a dependency on this but it doesn’t expose commons-beanutils to user
input so it wouldn't pose a risk like the struts library that is called out in the CVE
</notes>
<sha1>686EF3410BCF4AB8CE7FD0B899E832AABA5FACF7</sha1>
<cve>CVE-2014-0114</cve>
</suppress>
<suppress>
<notes>
false positive CVE is unrelated. owasp is confusing the platform-filter-delegate with
the DeleGate library
file name: platform-filter-delegate-*.jar
</notes>
<cve>CVE-2005-0861</cve>
</suppress>
<suppress>
<notes>
file name: ffmpeg-3.1.1_1-bin.zip: ffmpeg.exe
Reported CVE's are vulnerabilities in earlier versions of FFmpeg
</notes>
<sha1>6EECC43A0883EF7C2A8E4BAF3AD45E24D8119ECC</sha1>
<cpe>cpe:/a:ffmpeg:ffmpeg:-</cpe>
</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.
file name: proxy-camel-servlet-2.11.0-SNAPSHOT.jar
</notes>
<filePath regex="true">.*proxy-camel-servlet.*.jar</filePath>
<cve>CVE-2015-5344</cve>
<cve>CVE-2014-0002</cve>
<cve>CVE-2014-0003</cve>
<cve>CVE-2017-3159</cve>
</suppress>
<!-- tika -->
<suppress>
<notes>
This is an issue with the jmatio library included in the tika-parser 1.13. The problem
doesn't exist in 1.14/1.15 so this is a false positive.
tika-bundle-1.15.0_1.jar: vorbis-java-tika-0.8.jar: CVE-2016-6809
</notes>
<cve>CVE-2016-6809</cve>
</suppress>
<suppress>
<notes>
False positive. The cve is for jcore which is not used by tika-bundle or
apache-mime4j-core
tika-bundle-1.14.0_1.jar: apache-mime4j-core-0.7.2.jar: CVE-2012-4232
</notes>
<cve>CVE-2012-4232</cve>
</suppress>
<suppress>
<notes>
From security-core-api SecurityLogger. This is not an issue as we are not receiving
logging messages via TCP or UDP socket. This can be fixed by upgrading to version 2.8.2.
The version upgrade requires an update to karaf 4.1.1
log4j-api-2.4.1.jar (cpe:/a:apache:log4j:2.4.1,
org.apache.logging.log4j:log4j-api:2.4.1)
</notes>
<cve>CVE-2017-5645</cve>
</suppress>
<!-- 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-->
<suppress>
<notes>
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
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
</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-6420</cve>
<cve>CVE-2016-0766</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>
</suppress>
<suppress>
<notes>
This CVE is incorrectly attributing a CXF vulnerability to Camel camel-cxf-2.19.0.jar.
The CVE is 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.
</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-2016-2108</cve>
<cve>CVE-2016-2109</cve>
</suppress>
</suppressions>