-
Notifications
You must be signed in to change notification settings - Fork 29
/
security_advisories.xml
357 lines (308 loc) · 11.2 KB
/
security_advisories.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
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
<!--
Copyright (C) Igor Sysoev
Copyright (C) Nginx, Inc.
-->
<!DOCTYPE article SYSTEM "../../dtd/article.dtd">
<article name="nginx security advisories"
link="/en/security_advisories.html"
lang="en"
rev="1">
<section>
<para>
All nginx security issues should be reported to
<link url="mailto:[email protected]">[email protected]</link>
or via one of the methods listed
<link url="https://github.com/nginx/nginx/blob/master/SECURITY.md">here</link>.
</para>
<para>
Patches are signed using one of the
<link doc="pgp_keys.xml">PGP public keys</link>.
</para>
<security>
<item name="Buffer overread in the ngx_http_mp4_module"
severity="low"
advisory="https://mailman.nginx.org/pipermail/nginx-announce/2024/UUOCLLONPR6244YQYU65PO5LB7JDYCWM.html"
cve="2024-7347"
good="1.27.1+, 1.26.2+"
vulnerable="1.5.13-1.27.0">
<patch name="patch.2024.mp4.txt" />
</item>
<item name="Buffer overwrite in HTTP/3"
severity="medium"
advisory="https://mailman.nginx.org/pipermail/nginx-announce/2024/GMY32CSHFH6VFTN76HJNX7WNEX4RLHF6.html"
cve="2024-32760"
good="1.27.0+, 1.26.1+"
vulnerable="1.25.0-1.25.5, 1.26.0">
</item>
<item name="Stack overflow and use-after-free in HTTP/3"
severity="medium"
advisory="https://mailman.nginx.org/pipermail/nginx-announce/2024/GMY32CSHFH6VFTN76HJNX7WNEX4RLHF6.html"
cve="2024-31079"
good="1.27.0+, 1.26.1+"
vulnerable="1.25.0-1.25.5, 1.26.0">
</item>
<item name="NULL pointer dereference in HTTP/3"
severity="medium"
advisory="https://mailman.nginx.org/pipermail/nginx-announce/2024/GMY32CSHFH6VFTN76HJNX7WNEX4RLHF6.html"
cve="2024-35200"
good="1.27.0+, 1.26.1+"
vulnerable="1.25.0-1.25.5, 1.26.0">
</item>
<item name="Memory disclosure in HTTP/3"
severity="medium"
advisory="https://mailman.nginx.org/pipermail/nginx-announce/2024/GMY32CSHFH6VFTN76HJNX7WNEX4RLHF6.html"
cve="2024-34161"
good="1.27.0+, 1.26.1+"
vulnerable="1.25.0-1.25.5, 1.26.0">
</item>
<item name="NULL pointer dereference in HTTP/3"
severity="major"
advisory="https://mailman.nginx.org/pipermail/nginx-announce/2024/NW6MNW34VZ6HDIHH5YFBIJYZJN7FGNAV.html"
cve="2024-24989"
good="1.25.4+"
vulnerable="1.25.3">
</item>
<item name="Use-after-free in HTTP/3"
severity="major"
advisory="https://mailman.nginx.org/pipermail/nginx-announce/2024/NW6MNW34VZ6HDIHH5YFBIJYZJN7FGNAV.html"
cve="2024-24990"
good="1.25.4+"
vulnerable="1.25.0-1.25.3">
</item>
<item name="Memory corruption in the ngx_http_mp4_module"
severity="medium"
advisory="https://mailman.nginx.org/pipermail/nginx-announce/2022/RBRRON6PYBJJM2XIAPQBFBVLR4Q6IHRA.html"
cve="2022-41741"
good="1.23.2+, 1.22.1+"
vulnerable="1.1.3-1.23.1, 1.0.7-1.0.15">
<patch name="patch.2022.mp4.txt" />
</item>
<item name="Memory disclosure in the ngx_http_mp4_module"
severity="medium"
advisory="https://mailman.nginx.org/pipermail/nginx-announce/2022/RBRRON6PYBJJM2XIAPQBFBVLR4Q6IHRA.html"
cve="2022-41742"
good="1.23.2+, 1.22.1+"
vulnerable="1.1.3-1.23.1, 1.0.7-1.0.15">
<patch name="patch.2022.mp4.txt" />
</item>
<item name="1-byte memory overwrite in resolver"
severity="medium"
advisory="https://mailman.nginx.org/pipermail/nginx-announce/2021/000300.html"
cve="2021-23017"
good="1.21.0+, 1.20.1+"
vulnerable="0.6.18-1.20.0">
<patch name="patch.2021.resolver.txt" />
</item>
<item name="Excessive CPU usage in HTTP/2 with small window updates"
severity="medium"
advisory="https://mailman.nginx.org/pipermail/nginx-announce/2019/000249.html"
cve="2019-9511"
good="1.17.3+, 1.16.1+"
vulnerable="1.9.5-1.17.2">
</item>
<item name="Excessive CPU usage in HTTP/2 with priority changes"
severity="low"
advisory="https://mailman.nginx.org/pipermail/nginx-announce/2019/000249.html"
cve="2019-9513"
good="1.17.3+, 1.16.1+"
vulnerable="1.9.5-1.17.2">
</item>
<item name="Excessive memory usage in HTTP/2 with zero length headers"
severity="low"
advisory="https://mailman.nginx.org/pipermail/nginx-announce/2019/000249.html"
cve="2019-9516"
good="1.17.3+, 1.16.1+"
vulnerable="1.9.5-1.17.2">
</item>
<item name="Excessive memory usage in HTTP/2"
severity="low"
advisory="https://mailman.nginx.org/pipermail/nginx-announce/2018/000220.html"
cve="2018-16843"
good="1.15.6+, 1.14.1+"
vulnerable="1.9.5-1.15.5">
</item>
<item name="Excessive CPU usage in HTTP/2"
severity="low"
advisory="https://mailman.nginx.org/pipermail/nginx-announce/2018/000220.html"
cve="2018-16844"
good="1.15.6+, 1.14.1+"
vulnerable="1.9.5-1.15.5">
</item>
<item name="Memory disclosure in the ngx_http_mp4_module"
severity="medium"
advisory="https://mailman.nginx.org/pipermail/nginx-announce/2018/000221.html"
cve="2018-16845"
good="1.15.6+, 1.14.1+"
vulnerable="1.1.3-1.15.5, 1.0.7-1.0.15">
<patch name="patch.2018.mp4.txt" />
</item>
<item name="Integer overflow in the range filter"
severity="medium"
advisory="https://mailman.nginx.org/pipermail/nginx-announce/2017/000200.html"
cve="2017-7529"
good="1.13.3+, 1.12.1+"
vulnerable="0.5.6-1.13.2">
<patch name="patch.2017.ranges.txt" />
</item>
<item name="NULL pointer dereference while writing client request body"
severity="medium"
advisory="https://mailman.nginx.org/pipermail/nginx-announce/2016/000179.html"
cve="2016-4450"
good="1.11.1+, 1.10.1+"
vulnerable="1.3.9-1.11.0">
<patch name="patch.2016.write.txt" versions="1.9.13-1.11.0" />
<patch name="patch.2016.write2.txt" versions="1.3.9-1.9.12" />
</item>
<item name="Invalid pointer dereference in resolver"
severity="medium"
advisory="https://mailman.nginx.org/pipermail/nginx-announce/2016/000169.html"
cve="2016-0742"
good="1.9.10+, 1.8.1+"
vulnerable="0.6.18-1.9.9" />
<item name="Use-after-free during CNAME response processing in resolver"
severity="medium"
advisory="https://mailman.nginx.org/pipermail/nginx-announce/2016/000169.html"
cve="2016-0746"
good="1.9.10+, 1.8.1+"
vulnerable="0.6.18-1.9.9" />
<item name="Insufficient limits of CNAME resolution in resolver"
severity="medium"
advisory="https://mailman.nginx.org/pipermail/nginx-announce/2016/000169.html"
cve="2016-0747"
good="1.9.10+, 1.8.1+"
vulnerable="0.6.18-1.9.9" />
<item name="SSL session reuse vulnerability"
severity="medium"
advisory="https://mailman.nginx.org/pipermail/nginx-announce/2014/000147.html"
cve="2014-3616"
good="1.7.5+, 1.6.2+"
vulnerable="0.5.6-1.7.4">
</item>
<item name="STARTTLS command injection"
severity="medium"
advisory="https://mailman.nginx.org/pipermail/nginx-announce/2014/000144.html"
cve="2014-3556"
good="1.7.4+, 1.6.1+"
vulnerable="1.5.6-1.7.3">
<patch name="patch.2014.starttls.txt" />
</item>
<item name="SPDY heap buffer overflow"
severity="major"
advisory="https://mailman.nginx.org/pipermail/nginx-announce/2014/000135.html"
cve="2014-0133"
good="1.5.12+, 1.4.7+"
vulnerable="1.3.15-1.5.11">
<patch name="patch.2014.spdy2.txt" />
</item>
<item name="SPDY memory corruption"
severity="major"
advisory="https://mailman.nginx.org/pipermail/nginx-announce/2014/000132.html"
cve="2014-0088"
good="1.5.11+"
vulnerable="1.5.10">
<patch name="patch.2014.spdy.txt" />
</item>
<item name="Request line parsing vulnerability"
severity="medium"
advisory="https://mailman.nginx.org/pipermail/nginx-announce/2013/000125.html"
cve="2013-4547"
good="1.5.7+, 1.4.4+"
vulnerable="0.8.41-1.5.6">
<patch name="patch.2013.space.txt" />
</item>
<item name="Memory disclosure with specially crafted HTTP backend responses"
severity="medium"
advisory="https://mailman.nginx.org/pipermail/nginx-announce/2013/000114.html"
cve="2013-2070"
good="1.5.0+, 1.4.1+, 1.2.9+"
vulnerable="1.1.4-1.2.8, 1.3.9-1.4.0">
<patch name="patch.2013.chunked.txt" versions="1.3.9-1.4.0" />
<patch name="patch.2013.proxy.txt" versions="1.1.4-1.2.8" />
</item>
<item name="Stack-based buffer overflow with specially crafted request"
severity="major"
advisory="https://mailman.nginx.org/pipermail/nginx-announce/2013/000112.html"
cve="2013-2028"
good="1.5.0+, 1.4.1+"
vulnerable="1.3.9-1.4.0">
<patch name="patch.2013.chunked.txt" />
</item>
<item name="Vulnerabilities with Windows directory aliases"
severity="medium"
advisory="https://mailman.nginx.org/pipermail/nginx-announce/2012/000086.html"
cve="2011-4963"
good="1.3.1+, 1.2.1+"
vulnerable="nginx/Windows 0.7.52-1.3.0" />
<item name="Buffer overflow in the ngx_http_mp4_module"
severity="major"
advisory="https://mailman.nginx.org/pipermail/nginx-announce/2012/000080.html"
cve="2012-2089"
good="1.1.19+, 1.0.15+"
vulnerable="1.1.3-1.1.18, 1.0.7-1.0.14">
<patch name="patch.2012.mp4.txt" />
</item>
<item name="Memory disclosure with specially crafted backend responses"
severity="major"
advisory="https://mailman.nginx.org/pipermail/nginx-announce/2012/000076.html"
cve="2012-1180"
good="1.1.17+, 1.0.14+"
vulnerable="0.1.0-1.1.16">
<patch name="patch.2012.memory.txt" />
</item>
<item name="Buffer overflow in resolver"
severity="medium"
cve="2011-4315"
good="1.1.8+, 1.0.10+"
vulnerable="0.6.18-1.1.7" />
<item name="Vulnerabilities with invalid UTF-8 sequence on Windows"
severity="major"
cve="2010-2266"
good="0.8.41+, 0.7.67+"
vulnerable="nginx/Windows 0.7.52-0.8.40" />
<item name="Vulnerabilities with Windows file default stream"
severity="major"
cve="2010-2263"
good="0.8.40+, 0.7.66+"
vulnerable="nginx/Windows 0.7.52-0.8.39" />
<item name="Vulnerabilities with Windows 8.3 filename pseudonyms"
severity="major"
core="CORE-2010-0121"
href="http://www.coresecurity.com/content/filename-pseudonyms-vulnerabilities"
good="0.8.33+, 0.7.65+"
vulnerable="nginx/Windows 0.7.52-0.8.32" />
<item name="An error log data are not sanitized"
severity="none"
cve="2009-4487"
good="none"
vulnerable="all" />
<item name="The renegotiation vulnerability in SSL protocol"
severity="major"
cert="120541"
cve="2009-3555"
good="0.8.23+, 0.7.64+"
vulnerable="0.1.0-0.8.22">
<patch name="patch.cve-2009-3555.txt" />
</item>
<item name="Directory traversal vulnerability"
severity="minor"
cve="2009-3898"
good="0.8.17+, 0.7.63+"
vulnerable="0.1.0-0.8.16" />
<item name="Buffer underflow vulnerability"
severity="major"
cert="180065"
cve="2009-2629"
good="0.8.15+, 0.7.62+, 0.6.39+, 0.5.38+"
vulnerable="0.1.0-0.8.14">
<patch name="patch.180065.txt" />
</item>
<item name="Null pointer dereference vulnerability"
severity="major"
cve="2009-3896"
good="0.8.14+, 0.7.62+, 0.6.39+, 0.5.38+"
vulnerable="0.1.0-0.8.13">
<patch name="patch.null.pointer.txt" />
</item>
</security>
</section>
</article>