You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
<h2className="heading-top">Reporting a vulnerability</h2><br/>
27
+
<p>We are very grateful to the security researchers and users that report security vulnerabilities. We investigate each report thoroughly.</p>
28
+
<p>To make a report, send an email to the private <ahref="mailto:security-vulns-reports@layer5.io">security-vulns-reports@layer5.io</a> mailing list with the vulnerability details. For normal product bugs unrelated to latent security vulnerabilities, please head to the appropriate repository and submit a <ahref="https://github.com/layer5io/layer5/issues/new/choose">new issue</a> .</p>
46
29
<p>Note that the Layer5 community spans six GitHub organizations:</p>
47
-
48
30
<ulclassName="project-org-list">
49
31
<li>
50
32
<ahref="https://github.com/layer5io">
51
-
<imgsrc={layer5icon}alt="layer5 icon"/>
33
+
<img
34
+
src={layer5icon}
35
+
alt="layer5 icon"
36
+
/>
52
37
Layer5
53
-
</a>{" "}
54
-
- established projects like GetNighthawk, community with
55
-
MeshMates, a catch-all org.
38
+
</a>
39
+
- established projects like GetNighthawk, community with MeshMates, a catch-all org.
<li>You need help applying security related updates.</li>
154
123
<li>Your issue is not security related.</li>
155
124
</ul>
156
-
<p>
157
-
Instead, join the community{" "}
158
-
<ahref="https://slack.layer5.io/">Slack</a> and ask questions.
159
-
</p>
125
+
<p>Instead, join the community <ahref="https://slack.layer5.io/">Slack</a> and ask questions.</p>
160
126
161
127
<h3>Evaluation</h3>
162
-
<p>
163
-
The Layer5 team acknowledges and analyzes each vulnerability
164
-
report within 10 working days.
165
-
</p>
128
+
<p>The Layer5 team acknowledges and analyzes each vulnerability report within 10 working days.</p>
166
129
167
-
<p>
168
-
Any vulnerability information you share with the Layer5 team stays
169
-
within the respective Layer5 project. We don’t disseminate the
170
-
information to other projects. We only share the information as
171
-
needed to fix the issue.
172
-
</p>
130
+
<p>Any vulnerability information you share with the Layer5 team stays within the respective Layer5 project. We don’t disseminate the information to other projects. We only share the information as needed to fix the issue.</p>
173
131
174
-
<p>
175
-
We keep the reporter updated as the status of the security issue
176
-
is addressed.
177
-
</p>
132
+
<p>We keep the reporter updated as the status of the security issue is addressed.</p>
178
133
179
134
<h3>Fixing the issue</h3>
180
-
<p>
181
-
Once a security vulnerability has been fully characterized, a fix
182
-
is developed by the Layer5 team. The development and testing for
183
-
the fix happens in a private GitHub repository in order to prevent
184
-
premature disclosure of the vulnerability.
185
-
</p>
135
+
<p>Once a security vulnerability has been fully characterized, a fix is developed by the Layer5 team. The development and testing for the fix happens in a private GitHub repository in order to prevent premature disclosure of the vulnerability.</p>
186
136
187
137
<h3>Early disclosures</h3>
188
-
<p>
189
-
The Layer5 project maintains a mailing list for private early
190
-
disclosure of security vulnerabilities. The list is used to
191
-
provide actionable information to close Layer5 partners. The list
192
-
is not intended for individuals to find out about security issues.
193
-
</p>
138
+
<p>The Layer5 project maintains a mailing list for private early disclosure of security vulnerabilities. The list is used to provide actionable information to close Layer5 partners. The list is not intended for individuals to find out about security issues.</p>
194
139
195
140
<h3>Public disclosures</h3>
196
-
<p>
197
-
On the day chosen for public disclosure, a sequence of activities
198
-
takes place as quickly as possible:
199
-
</p>
141
+
<p>On the day chosen for public disclosure, a sequence of activities takes place as quickly as possible:</p>
200
142
<ul>
201
-
<li>
202
-
Changes are merged from the private GitHub repository holding
203
-
the fix into the appropriate set of public branches.
204
-
</li>
205
-
<li>
206
-
Layer5 team ensures all necessary binaries are promptly built
207
-
and published.
208
-
</li>
209
-
<li>
210
-
Once the binaries are available, an announcement is sent out on
211
-
the following channels:
143
+
<li>Changes are merged from the private GitHub repository holding the fix into the appropriate set of public branches.</li>
144
+
<li>Layer5 team ensures all necessary binaries are promptly built and published.</li>
145
+
<li>Once the binaries are available, an announcement is sent out on the following channels:
<li>The <ahref="https://layer5io.slack.com/archives/CSF3PSZT9">#announcements</a> channel on community <ahref="https://slack.layer5.io/">Slack</a></li>
229
150
</ul>
230
151
</li>
231
152
</ul>
232
-
<p>
233
-
As much as possible this announcement will be actionable, and
234
-
include any mitigating steps customers can take prior to upgrading
235
-
to a fixed version.
236
-
</p>
153
+
<p>As much as possible this announcement will be actionable, and include any mitigating steps customers can take prior to upgrading to a fixed version.</p>
237
154
238
155
<h2>List of Announced Vulnerabilities:</h2>
239
156
240
157
<divclassName="table-container">
241
158
<table>
242
159
<thead>
243
160
<tr>
244
-
<th>
245
-
<b>DATE ANNOUNCED</b>
246
-
</th>
247
-
<th>
248
-
<b>CVE ID</b>
249
-
</th>
250
-
<th>
251
-
<b>DESCRIPTION</b>
252
-
</th>
253
-
<th>
254
-
<b>AFFECTED COMPONENT</b>
255
-
</th>
256
-
<th>
257
-
<b>VULNERABLE VERSION</b>
258
-
</th>
259
-
<th>
260
-
<b>PATCHED VERSION</b>
261
-
</th>
262
-
<th>
263
-
<b>FIX DETAILS</b>
264
-
</th>
265
-
<th>
266
-
<b>LINKS</b>
267
-
</th>
161
+
<th><b>DATE ANNOUNCED</b></th>
162
+
<th><b>CVE ID</b></th>
163
+
<th><b>DESCRIPTION</b></th>
164
+
<th><b>AFFECTED COMPONENT</b></th>
165
+
<th><b>VULNERABLE VERSION</b></th>
166
+
<th><b>PATCHED VERSION</b></th>
167
+
<th><b>FIX DETAILS</b></th>
168
+
<th><b>LINKS</b></th>
268
169
</tr>
269
170
</thead>
270
171
<tbody>
271
172
<tr>
272
173
<td>2021-04-28</td>
273
174
<td>CVE-2021-31856</td>
274
-
<td>
275
-
A SQL Injection vulnerability in the REST API in Layer5
276
-
Meshery 0.5.2 allows an attacker to execute arbitrary SQL
277
-
commands via the /experimental/patternfiles endpoint
278
-
(order parameter in GetMesheryPatterns in
279
-
models/meshery_pattern_persister.go).
280
-
</td>
175
+
<td>A SQL Injection vulnerability in the REST API in Layer5 Meshery 0.5.2 allows an attacker to execute arbitrary SQL commands via the /experimental/patternfiles endpoint (order parameter in GetMesheryPatterns in models/meshery_pattern_persister.go).</td>
0 commit comments