Unnamed: 0 int64 0 832k | id float64 2.49B 32.1B | type stringclasses 1 value | created_at stringlengths 19 19 | repo stringlengths 5 112 | repo_url stringlengths 34 141 | action stringclasses 3 values | title stringlengths 1 844 | labels stringlengths 4 721 | body stringlengths 1 261k | index stringclasses 12 values | text_combine stringlengths 96 261k | label stringclasses 2 values | text stringlengths 96 248k | binary_label int64 0 1 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
24,104 | 12,217,147,943 | IssuesEvent | 2020-05-01 16:35:03 | numba/numba | https://api.github.com/repos/numba/numba | closed | for loop is not getting faster in some cases | performance question | I have write a function to calculate move OLS beta for time series
calculate it by a sliding window
```
@jit(nopython=True)
def regBeta(y,x,n,d):
'''
y OLS with x and get the beta
y,x: vector
d: past d dates
'''
rowNum_ = n-d+1
y_ = np.lib.stride_tricks.as_strided(y,shape=(rowNum_,d),strides=(y.strides[0],y.strides[0]))
x_ = np.lib.stride_tricks.as_strided(x,shape=(rowNum_,d),strides=(x.strides[0],x.strides[0]))
#beta = np.zeros(rowNum_,dtype=np.float32)
# for i in range(rowNum_):
# x_i = x_[i]
# y_i = y_[i]
# #beta[i] = np.linalg.solve(np.dot(x_i.T,x_i),np.dot(x_i.T,y_i))
#x1_.sum(1).reshape(n-d+1,1)/d
x_mean = x_.sum(1).reshape(rowNum_,1) / d
y_mean = y_.sum(1).reshape(rowNum_,1) / d
x_1 = x_ - x_mean
y_1 = y_ - y_mean
x_2 = x_1 * x_1
xy_1 = x_1 * y_1
x_2_s = x_2.sum(1)
xy_1_s = xy_1.sum(1)
beta = xy_1_s / x_2_s
return beta
@jit(nopython=True)
def regBeta_mat(m1,m2,d):
'''
m1 OLS with m2 in past d dates and get the beta
m1,m2: matrix (m1:y,m2:x)
return: beta of OLS
'''
size1,size2 = m1.size,m2.size
if size1 == 1 or size2 == 1:
return np.full(fill_value=np.nan,shape=(1,1),dtype=np.float32)
rowNum1 = m1.shape[0]
rowNum2 = m2.shape[0]
colNum = m1.shape[1]
if d < 20:
return np.full(fill_value=np.nan,shape=(rowNum1,colNum),dtype=np.float32)
if rowNum1 < rowNum2:
rowNum = rowNum1
m2 = m2[-rowNum:]
else:
rowNum = rowNum2
m1 = m1[-rowNum:]
if rowNum <= d + 20:
return np.full(fill_value=np.nan,shape=(rowNum,colNum),dtype=np.float32)
retMat = np.zeros((rowNum-d+1,colNum),dtype=np.float32)
for i in np.arange(colNum):
retMat[:,i] = regBeta(m1[:,i],m2[:,i],rowNum,d)
return retMat
```
```
m1 = np.random.randn(750,4000).astype(np.float32)
m2 = np.random.randn(750,4000).astype(np.float32)
%timeit regBeta_mat(m1,m2,20)
469 ms ± 1.3 ms per loop (mean ± std. dev. of 7 runs, 1 loop each)
%timeit regBeta_mat.py_func(m1,m2,20)
477 ms ± 1.04 ms per loop (mean ± std. dev. of 7 runs, 1 loop each)
```
I created two random matrix (750,4000) . And I do the OLS column by column. So it will do 4000 times OLS , and for loop by 4000 times.
And I think numba will accelerate the for loop significantly, but the result is very close .
Maybe I miss something or forget something in numba, is there any method to accelerate the for loop significantly? Thank you . | True | for loop is not getting faster in some cases - I have write a function to calculate move OLS beta for time series
calculate it by a sliding window
```
@jit(nopython=True)
def regBeta(y,x,n,d):
'''
y OLS with x and get the beta
y,x: vector
d: past d dates
'''
rowNum_ = n-d+1
y_ = np.lib.stride_tricks.as_strided(y,shape=(rowNum_,d),strides=(y.strides[0],y.strides[0]))
x_ = np.lib.stride_tricks.as_strided(x,shape=(rowNum_,d),strides=(x.strides[0],x.strides[0]))
#beta = np.zeros(rowNum_,dtype=np.float32)
# for i in range(rowNum_):
# x_i = x_[i]
# y_i = y_[i]
# #beta[i] = np.linalg.solve(np.dot(x_i.T,x_i),np.dot(x_i.T,y_i))
#x1_.sum(1).reshape(n-d+1,1)/d
x_mean = x_.sum(1).reshape(rowNum_,1) / d
y_mean = y_.sum(1).reshape(rowNum_,1) / d
x_1 = x_ - x_mean
y_1 = y_ - y_mean
x_2 = x_1 * x_1
xy_1 = x_1 * y_1
x_2_s = x_2.sum(1)
xy_1_s = xy_1.sum(1)
beta = xy_1_s / x_2_s
return beta
@jit(nopython=True)
def regBeta_mat(m1,m2,d):
'''
m1 OLS with m2 in past d dates and get the beta
m1,m2: matrix (m1:y,m2:x)
return: beta of OLS
'''
size1,size2 = m1.size,m2.size
if size1 == 1 or size2 == 1:
return np.full(fill_value=np.nan,shape=(1,1),dtype=np.float32)
rowNum1 = m1.shape[0]
rowNum2 = m2.shape[0]
colNum = m1.shape[1]
if d < 20:
return np.full(fill_value=np.nan,shape=(rowNum1,colNum),dtype=np.float32)
if rowNum1 < rowNum2:
rowNum = rowNum1
m2 = m2[-rowNum:]
else:
rowNum = rowNum2
m1 = m1[-rowNum:]
if rowNum <= d + 20:
return np.full(fill_value=np.nan,shape=(rowNum,colNum),dtype=np.float32)
retMat = np.zeros((rowNum-d+1,colNum),dtype=np.float32)
for i in np.arange(colNum):
retMat[:,i] = regBeta(m1[:,i],m2[:,i],rowNum,d)
return retMat
```
```
m1 = np.random.randn(750,4000).astype(np.float32)
m2 = np.random.randn(750,4000).astype(np.float32)
%timeit regBeta_mat(m1,m2,20)
469 ms ± 1.3 ms per loop (mean ± std. dev. of 7 runs, 1 loop each)
%timeit regBeta_mat.py_func(m1,m2,20)
477 ms ± 1.04 ms per loop (mean ± std. dev. of 7 runs, 1 loop each)
```
I created two random matrix (750,4000) . And I do the OLS column by column. So it will do 4000 times OLS , and for loop by 4000 times.
And I think numba will accelerate the for loop significantly, but the result is very close .
Maybe I miss something or forget something in numba, is there any method to accelerate the for loop significantly? Thank you . | non_priority | for loop is not getting faster in some cases i have write a function to calculate move ols beta for time series calculate it by a sliding window jit nopython true def regbeta y x n d y ols with x and get the beta y x vector d past d dates rownum n d y np lib stride tricks as strided y shape rownum d strides y strides y strides x np lib stride tricks as strided x shape rownum d strides x strides x strides beta np zeros rownum dtype np for i in range rownum x i x y i y beta np linalg solve np dot x i t x i np dot x i t y i sum reshape n d d x mean x sum reshape rownum d y mean y sum reshape rownum d x x x mean y y y mean x x x xy x y x s x sum xy s xy sum beta xy s x s return beta jit nopython true def regbeta mat d ols with in past d dates and get the beta matrix y x return beta of ols size size if or return np full fill value np nan shape dtype np shape shape colnum shape if d return np full fill value np nan shape colnum dtype np if rownum else rownum if rownum d return np full fill value np nan shape rownum colnum dtype np retmat np zeros rownum d colnum dtype np for i in np arange colnum retmat regbeta rownum d return retmat np random randn astype np np random randn astype np timeit regbeta mat ms ± ms per loop mean ± std dev of runs loop each timeit regbeta mat py func ms ± ms per loop mean ± std dev of runs loop each i created two random matrix and i do the ols column by column so it will do times ols and for loop by times and i think numba will accelerate the for loop significantly but the result is very close maybe i miss something or forget something in numba is there any method to accelerate the for loop significantly thank you | 0 |
445,602 | 31,241,474,485 | IssuesEvent | 2023-08-20 22:56:15 | brett-buskirk/guide-to-deployment | https://api.github.com/repos/brett-buskirk/guide-to-deployment | closed | Make wiki for the repo | documentation | Now that the repo has been made public, I can enable the Wiki settings to create a guide to its useage. | 1.0 | Make wiki for the repo - Now that the repo has been made public, I can enable the Wiki settings to create a guide to its useage. | non_priority | make wiki for the repo now that the repo has been made public i can enable the wiki settings to create a guide to its useage | 0 |
46,104 | 7,237,433,762 | IssuesEvent | 2018-02-13 11:00:10 | godotengine/godot | https://api.github.com/repos/godotengine/godot | closed | JSON.parse returns JSONParseResult with valid json | bug documentation | **Godot version: 3.0**
<!-- Specify commit hash if non-official. -->
**Windows 8**
**Issue description:**
JSON.parse returns a JSONParseResult object in trivial cases (which are valid JSON), including the documentation example (found here : http://docs.godotengine.org/en/latest/classes/class_jsonparseresult.html#class-jsonparseresult)
I expected to get an array, as in the documentation example.
**Steps to reproduce:**
New project.
Add new node.
Add built-in script to this node
In _ready(), copy-paste the example code from the documentation : http://docs.godotengine.org/en/latest/classes/class_jsonparseresult.html#class-jsonparseresult
Execute. Log outputs "unexpected result"
**Minimal reproduction project:**
[testgodotjsonbug.zip](https://github.com/godotengine/godot/files/1692886/testgodotjsonbug.zip)
| 1.0 | JSON.parse returns JSONParseResult with valid json - **Godot version: 3.0**
<!-- Specify commit hash if non-official. -->
**Windows 8**
**Issue description:**
JSON.parse returns a JSONParseResult object in trivial cases (which are valid JSON), including the documentation example (found here : http://docs.godotengine.org/en/latest/classes/class_jsonparseresult.html#class-jsonparseresult)
I expected to get an array, as in the documentation example.
**Steps to reproduce:**
New project.
Add new node.
Add built-in script to this node
In _ready(), copy-paste the example code from the documentation : http://docs.godotengine.org/en/latest/classes/class_jsonparseresult.html#class-jsonparseresult
Execute. Log outputs "unexpected result"
**Minimal reproduction project:**
[testgodotjsonbug.zip](https://github.com/godotengine/godot/files/1692886/testgodotjsonbug.zip)
| non_priority | json parse returns jsonparseresult with valid json godot version windows issue description json parse returns a jsonparseresult object in trivial cases which are valid json including the documentation example found here i expected to get an array as in the documentation example steps to reproduce new project add new node add built in script to this node in ready copy paste the example code from the documentation execute log outputs unexpected result minimal reproduction project | 0 |
48,376 | 5,955,657,843 | IssuesEvent | 2017-05-28 08:58:54 | hapijs/wreck | https://api.github.com/repos/hapijs/wreck | closed | Fix tests for node 7.10.0 | test | @geek @cjihrig Not sure why this is needed but the tests fail when run with latest node. | 1.0 | Fix tests for node 7.10.0 - @geek @cjihrig Not sure why this is needed but the tests fail when run with latest node. | non_priority | fix tests for node geek cjihrig not sure why this is needed but the tests fail when run with latest node | 0 |
40,055 | 20,405,879,624 | IssuesEvent | 2022-02-23 05:19:55 | google/mediapipe | https://api.github.com/repos/google/mediapipe | closed | Algorithms Specification | MediaPipe stat:awaiting response type:performance type:others stalled | Hello,
Is there any **algorithm specification**, requirement or evaluation guideline for mediapipe, specially the Facemesh, Holistic, Face Geometry and Object Detection solutions.
1) I want to know the strength and weakness of these solutions?
2) Is there any constraint or environmental circumstances/conditions that these solution can works better or worst there?
Thank you | True | Algorithms Specification - Hello,
Is there any **algorithm specification**, requirement or evaluation guideline for mediapipe, specially the Facemesh, Holistic, Face Geometry and Object Detection solutions.
1) I want to know the strength and weakness of these solutions?
2) Is there any constraint or environmental circumstances/conditions that these solution can works better or worst there?
Thank you | non_priority | algorithms specification hello is there any algorithm specification requirement or evaluation guideline for mediapipe specially the facemesh holistic face geometry and object detection solutions i want to know the strength and weakness of these solutions is there any constraint or environmental circumstances conditions that these solution can works better or worst there thank you | 0 |
13,843 | 9,087,724,411 | IssuesEvent | 2019-02-18 14:27:52 | mF2C/mF2C | https://api.github.com/repos/mF2C/mF2C | closed | documentation update for agent getting certificate on installation | SECURITY | when an agent joins the network, it needs to get a certificate from the CA as part of the installation process. This must be described in the installation manual. | True | documentation update for agent getting certificate on installation - when an agent joins the network, it needs to get a certificate from the CA as part of the installation process. This must be described in the installation manual. | non_priority | documentation update for agent getting certificate on installation when an agent joins the network it needs to get a certificate from the ca as part of the installation process this must be described in the installation manual | 0 |
72,556 | 24,180,879,517 | IssuesEvent | 2022-09-23 08:46:58 | primefaces/primefaces | https://api.github.com/repos/primefaces/primefaces | opened | Carousel: Has no paginator link limit | :lady_beetle: defect :bangbang: needs-triage | ### Describe the bug
Since PrimeFaces 11.0.0 the carousel component is missing the of the attribute "pageLinks" which was used to limit the displayed page links in the paginator area. So now there is a page link for every item in the carousel. For example, if you have 20 items in it, it will show 20 page links and so on. We need at least an option to disable the display of the page links to prevent an overflow of those.
### Reproducer
```
<div class="card">
<p:carousel circular="true">
<f:facet name="header">
<h5>Tabs</h5>
</f:facet>
<p:tab>
<p class="m-0 p-3">A</p>
</p:tab>
<p:tab>
<p class="m-0 p-3">A</p>
</p:tab>
<p:tab>
<p class="m-0 p-3">A</p>
</p:tab>
<p:tab>
<p class="m-0 p-3">A</p>
</p:tab>
<p:tab>
<p class="m-0 p-3">A</p>
</p:tab> <p:tab>
<p class="m-0 p-3">A</p>
</p:tab> <p:tab>
<p class="m-0 p-3">A</p>
</p:tab> <p:tab>
<p class="m-0 p-3">A</p>
</p:tab>
</p:carousel>
</div>
```
### Expected behavior
_No response_
### PrimeFaces edition
_No response_
### PrimeFaces version
11.0.0
### Theme
Diamond
### JSF implementation
MyFaces
### JSF version
2.3
### Java version
Java 8
### Browser(s)
_No response_ | 1.0 | Carousel: Has no paginator link limit - ### Describe the bug
Since PrimeFaces 11.0.0 the carousel component is missing the of the attribute "pageLinks" which was used to limit the displayed page links in the paginator area. So now there is a page link for every item in the carousel. For example, if you have 20 items in it, it will show 20 page links and so on. We need at least an option to disable the display of the page links to prevent an overflow of those.
### Reproducer
```
<div class="card">
<p:carousel circular="true">
<f:facet name="header">
<h5>Tabs</h5>
</f:facet>
<p:tab>
<p class="m-0 p-3">A</p>
</p:tab>
<p:tab>
<p class="m-0 p-3">A</p>
</p:tab>
<p:tab>
<p class="m-0 p-3">A</p>
</p:tab>
<p:tab>
<p class="m-0 p-3">A</p>
</p:tab>
<p:tab>
<p class="m-0 p-3">A</p>
</p:tab> <p:tab>
<p class="m-0 p-3">A</p>
</p:tab> <p:tab>
<p class="m-0 p-3">A</p>
</p:tab> <p:tab>
<p class="m-0 p-3">A</p>
</p:tab>
</p:carousel>
</div>
```
### Expected behavior
_No response_
### PrimeFaces edition
_No response_
### PrimeFaces version
11.0.0
### Theme
Diamond
### JSF implementation
MyFaces
### JSF version
2.3
### Java version
Java 8
### Browser(s)
_No response_ | non_priority | carousel has no paginator link limit describe the bug since primefaces the carousel component is missing the of the attribute pagelinks which was used to limit the displayed page links in the paginator area so now there is a page link for every item in the carousel for example if you have items in it it will show page links and so on we need at least an option to disable the display of the page links to prevent an overflow of those reproducer tabs a a a a a a a a expected behavior no response primefaces edition no response primefaces version theme diamond jsf implementation myfaces jsf version java version java browser s no response | 0 |
91,083 | 26,271,095,471 | IssuesEvent | 2023-01-06 17:03:53 | lennartkoopmann/nzyme | https://api.github.com/repos/lennartkoopmann/nzyme | closed | Do not overwrite /etc/default/nzyme during installation | bug build/release | Check if the file exists and do not overwrite it if it does. Currently, we are overwriting all changes to it, rendering it useless. | 1.0 | Do not overwrite /etc/default/nzyme during installation - Check if the file exists and do not overwrite it if it does. Currently, we are overwriting all changes to it, rendering it useless. | non_priority | do not overwrite etc default nzyme during installation check if the file exists and do not overwrite it if it does currently we are overwriting all changes to it rendering it useless | 0 |
233,641 | 17,873,625,285 | IssuesEvent | 2021-09-06 20:58:07 | cf-301-group-2021/entertainment-tracker | https://api.github.com/repos/cf-301-group-2021/entertainment-tracker | closed | Create Domain Model, add to README.md | documentation | Draw out the entities for your project and how they are related to each other. Determine the relationships between the functions/methods and entities of your app.
Include in your domain model the names and data types of your entities and their properties.
Do some research on domain modeling and create your own diagram that represents your app. Here are some helpful resources as a starting point:
- [Brief introduction to Domain Modeling](https://medium.com/@olegchursin/a-brief-introduction-to-domain-modeling-862a30b38353)
- [Domain Modeling](https://www.scaledagileframework.com/domain-modeling/)
- [Domain driven architecture diagram](https://medium.com/nick-tune-tech-strategy-blog/domain-driven-architecture-diagrams-139a75acb578)
Include this domain model in the README.md file located in your project’s GitHub repo. | 1.0 | Create Domain Model, add to README.md - Draw out the entities for your project and how they are related to each other. Determine the relationships between the functions/methods and entities of your app.
Include in your domain model the names and data types of your entities and their properties.
Do some research on domain modeling and create your own diagram that represents your app. Here are some helpful resources as a starting point:
- [Brief introduction to Domain Modeling](https://medium.com/@olegchursin/a-brief-introduction-to-domain-modeling-862a30b38353)
- [Domain Modeling](https://www.scaledagileframework.com/domain-modeling/)
- [Domain driven architecture diagram](https://medium.com/nick-tune-tech-strategy-blog/domain-driven-architecture-diagrams-139a75acb578)
Include this domain model in the README.md file located in your project’s GitHub repo. | non_priority | create domain model add to readme md draw out the entities for your project and how they are related to each other determine the relationships between the functions methods and entities of your app include in your domain model the names and data types of your entities and their properties do some research on domain modeling and create your own diagram that represents your app here are some helpful resources as a starting point include this domain model in the readme md file located in your project’s github repo | 0 |
107,285 | 11,525,182,441 | IssuesEvent | 2020-02-15 06:19:21 | flutter/flutter | https://api.github.com/repos/flutter/flutter | reopened | AndroidX is not supported in FlutterFragmentActivity, FlutterActivity And FlutterFragment | a: existing-apps d: website - content documentation tool ▣ platform-android | FlutterFragmentActivity, FlutterActivity, FlutterFragment is not supprot AndroidX, and They use support libaries!!! | 1.0 | AndroidX is not supported in FlutterFragmentActivity, FlutterActivity And FlutterFragment - FlutterFragmentActivity, FlutterActivity, FlutterFragment is not supprot AndroidX, and They use support libaries!!! | non_priority | androidx is not supported in flutterfragmentactivity flutteractivity and flutterfragment flutterfragmentactivity flutteractivity flutterfragment is not supprot androidx and they use support libaries | 0 |
269,676 | 28,960,245,996 | IssuesEvent | 2023-05-10 01:26:27 | praneethpanasala/linux | https://api.github.com/repos/praneethpanasala/linux | reopened | CVE-2020-16120 (Medium) detected in linuxv4.19 | Mend: dependency security vulnerability | ## CVE-2020-16120 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>linuxv4.19</b></p></summary>
<p>
<p>Linux kernel source tree</p>
<p>Library home page: <a href=https://github.com/torvalds/linux.git>https://github.com/torvalds/linux.git</a></p>
<p>Found in HEAD commit: <a href="https://api.github.com/repos/praneethpanasala/linux/commits/d80c4f847c91020292cb280132b15e2ea147f1a3">d80c4f847c91020292cb280132b15e2ea147f1a3</a></p>
<p>Found in base branch: <b>master</b></p></p>
</details>
</p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Source Files (2)</summary>
<p></p>
<p>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/fs/overlayfs/readdir.c</b>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/fs/overlayfs/readdir.c</b>
</p>
</details>
<p></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> Vulnerability Details</summary>
<p>
Overlayfs did not properly perform permission checking when copying up files in an overlayfs and could be exploited from within a user namespace, if, for example, unprivileged user namespaces were allowed. It was possible to have a file not readable by an unprivileged user to be copied to a mountpoint controlled by the user, like a removable device. This was introduced in kernel version 4.19 by commit d1d04ef ("ovl: stack file ops"). This was fixed in kernel version 5.8 by commits 56230d9 ("ovl: verify permissions in ovl_path_open()"), 48bd024 ("ovl: switch to mounter creds in readdir") and 05acefb ("ovl: check permission to open real file"). Additionally, commits 130fdbc ("ovl: pass correct flags for opening real directory") and 292f902 ("ovl: call secutiry hook in ovl_real_ioctl()") in kernel 5.8 might also be desired or necessary. These additional commits introduced a regression in overlay mounts within user namespaces which prevented access to files with ownership outside of the user namespace. This regression was mitigated by subsequent commit b6650da ("ovl: do not fail because of O_NOATIMEi") in kernel 5.11.
<p>Publish Date: 2021-02-10
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2020-16120>CVE-2020-16120</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>4.4</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: High
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: None
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://www.linuxkernelcves.com/cves/CVE-2020-16120">https://www.linuxkernelcves.com/cves/CVE-2020-16120</a></p>
<p>Release Date: 2021-02-10</p>
<p>Fix Resolution: v5.8-rc1</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | CVE-2020-16120 (Medium) detected in linuxv4.19 - ## CVE-2020-16120 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>linuxv4.19</b></p></summary>
<p>
<p>Linux kernel source tree</p>
<p>Library home page: <a href=https://github.com/torvalds/linux.git>https://github.com/torvalds/linux.git</a></p>
<p>Found in HEAD commit: <a href="https://api.github.com/repos/praneethpanasala/linux/commits/d80c4f847c91020292cb280132b15e2ea147f1a3">d80c4f847c91020292cb280132b15e2ea147f1a3</a></p>
<p>Found in base branch: <b>master</b></p></p>
</details>
</p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Source Files (2)</summary>
<p></p>
<p>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/fs/overlayfs/readdir.c</b>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/fs/overlayfs/readdir.c</b>
</p>
</details>
<p></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> Vulnerability Details</summary>
<p>
Overlayfs did not properly perform permission checking when copying up files in an overlayfs and could be exploited from within a user namespace, if, for example, unprivileged user namespaces were allowed. It was possible to have a file not readable by an unprivileged user to be copied to a mountpoint controlled by the user, like a removable device. This was introduced in kernel version 4.19 by commit d1d04ef ("ovl: stack file ops"). This was fixed in kernel version 5.8 by commits 56230d9 ("ovl: verify permissions in ovl_path_open()"), 48bd024 ("ovl: switch to mounter creds in readdir") and 05acefb ("ovl: check permission to open real file"). Additionally, commits 130fdbc ("ovl: pass correct flags for opening real directory") and 292f902 ("ovl: call secutiry hook in ovl_real_ioctl()") in kernel 5.8 might also be desired or necessary. These additional commits introduced a regression in overlay mounts within user namespaces which prevented access to files with ownership outside of the user namespace. This regression was mitigated by subsequent commit b6650da ("ovl: do not fail because of O_NOATIMEi") in kernel 5.11.
<p>Publish Date: 2021-02-10
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2020-16120>CVE-2020-16120</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>4.4</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: High
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: None
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://www.linuxkernelcves.com/cves/CVE-2020-16120">https://www.linuxkernelcves.com/cves/CVE-2020-16120</a></p>
<p>Release Date: 2021-02-10</p>
<p>Fix Resolution: v5.8-rc1</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_priority | cve medium detected in cve medium severity vulnerability vulnerable library linux kernel source tree library home page a href found in head commit a href found in base branch master vulnerable source files fs overlayfs readdir c fs overlayfs readdir c vulnerability details overlayfs did not properly perform permission checking when copying up files in an overlayfs and could be exploited from within a user namespace if for example unprivileged user namespaces were allowed it was possible to have a file not readable by an unprivileged user to be copied to a mountpoint controlled by the user like a removable device this was introduced in kernel version by commit ovl stack file ops this was fixed in kernel version by commits ovl verify permissions in ovl path open ovl switch to mounter creds in readdir and ovl check permission to open real file additionally commits ovl pass correct flags for opening real directory and ovl call secutiry hook in ovl real ioctl in kernel might also be desired or necessary these additional commits introduced a regression in overlay mounts within user namespaces which prevented access to files with ownership outside of the user namespace this regression was mitigated by subsequent commit ovl do not fail because of o noatimei in kernel publish date url a href cvss score details base score metrics exploitability metrics attack vector local attack complexity low privileges required high user interaction none scope unchanged impact metrics confidentiality impact high integrity impact none availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution step up your open source security game with mend | 0 |
278,743 | 24,172,548,836 | IssuesEvent | 2022-09-22 20:41:22 | Mamr96insatbug/test | https://api.github.com/repos/Mamr96insatbug/test | opened | Error playing | Forwarded-to-Test | # :clipboard: Bug Details
>Error playing
key | value
--|--
Reported At | 2022-09-22 20:41:04 UTC
Categories | Report a bug, Usability Issue
Tags | Forwarded-to-Test
App Version | 2.0.8 (6)
Session Duration | 208279
Device | arm64, iOS 16.0
Display | 390x844 (@3x)
Location | Cairo, Egypt (en)
## :point_right: [View Full Bug Report on Instabug](https://dashboard.instabug.com/applications/test123/beta/bugs/482?utm_source=github&utm_medium=integrations) :point_left:
___
# :chart_with_downwards_trend: Session Profiler
Here is what the app was doing right before the bug was reported:
Key | Value
--|--
CPU Load | 1%
Used Memory | 100.0% - 0.04/0.04 GB
Used Storage | 39.7% - 90.66/228.27 GB
Connectivity | no_connection - NA
Battery | 100% - unplugged
Orientation | portrait
Find all the changes that happened in the parameters mentioned above during the last 60 seconds before the bug was reported here: :point_right: **[View Full Session Profiler](https://dashboard.instabug.com/applications/test123/beta/bugs/482?show-session-profiler=true&utm_source=github&utm_medium=integrations)** :point_left:
___
# :mag_right: Logs
### User Steps
Here are the last 10 steps done by the user right before the bug was reported:
```
20:39:58 Top View: SwiftRadio.NowPlayingViewController
20:39:57 Tap in UIStackView in SwiftRadio.StationsViewController
20:39:56 Top View: SwiftRadio.StationsViewController
20:39:55 Tap in _UIButtonBarButton in SwiftRadio.NowPlayingViewController
20:39:54 Top View: SwiftRadio.NowPlayingViewController
20:39:54 Tap in UIStackView in SwiftRadio.StationsViewController
10:49:08 Tap in UITableView in SwiftRadio.StationsViewController
10:49:05 Top View: SwiftRadio.StationsViewController
10:49:04 Application: DidBecomeActive
10:49:04 Application: SceneDidActivate
```
Find all the user steps done by the user throughout the session here: :point_right: **[View All User Steps](https://dashboard.instabug.com/applications/test123/beta/bugs/482?show-logs=user_steps&utm_source=github&utm_medium=integrations)** :point_left:
___
# :camera: Images
[](https://d38gnqwzxziyyy.cloudfront.net/attachments/bugs/18914425/b3d01fe8d391f20ef8c8c9fd5c37c689_original/27307959/2022092210410222010394.jpg?Expires=4819552881&Signature=rlHi1oncVITc-VXwsg1mkxpt7C~XFoFpJpCVNSjJg6vXkZdi-Pl9WBd8fDb9WvJ66waeZmM~wurchMArdUGnidHmw5WJ1CSxWsqBlC-Qvgu9sBvJpV0akWhdIH97IJ~BXYbWpbuy76mesm5wNIiDg03Ryt4Fb215jA1g9Z7n6SvFQmZnDvbTrVav7Aez8EOnm-5DeZIT~XBsXA0k6VvJ7gzvX-NrVpBcZuFjqa9GmBKv6Jv55yDxF82cj29xKPVAeb6AtfIWwOTzaIpMKY6y-HIrGIn9FUB~azfvPo~Q0yfqMcEWmNTHOz~sCWrYdNXi-h5R5hx6d47aSSz7p7eaww__&Key-Pair-Id=APKAIXAG65U6UUX7JAQQ)
___
# :warning: Looking for More Details?
1. **Network Log**: we are unable to capture your network requests automatically. If you are using AFNetworking or Alamofire, [**check the details mentioned here**](https://docs.instabug.com/docs/ios-logging?utm_source=github&utm_medium=integrations#section-requests-not-appearing-in-logs).
2. **User Events**: start capturing custom User Events to send them along with each report. [**Find all the details in the docs**](https://docs.instabug.com/docs/ios-logging?utm_source=github&utm_medium=integrations).
3. **Instabug Log**: start adding Instabug logs to see them right inside each report you receive. [**Find all the details in the docs**](https://docs.instabug.com/docs/ios-logging?utm_source=github&utm_medium=integrations).
4. **Console Log**: when enabled you will see them right inside each report you receive. [**Find all the details in the docs**](https://docs.instabug.com/docs/ios-logging?utm_source=github&utm_medium=integrations). | 1.0 | Error playing - # :clipboard: Bug Details
>Error playing
key | value
--|--
Reported At | 2022-09-22 20:41:04 UTC
Categories | Report a bug, Usability Issue
Tags | Forwarded-to-Test
App Version | 2.0.8 (6)
Session Duration | 208279
Device | arm64, iOS 16.0
Display | 390x844 (@3x)
Location | Cairo, Egypt (en)
## :point_right: [View Full Bug Report on Instabug](https://dashboard.instabug.com/applications/test123/beta/bugs/482?utm_source=github&utm_medium=integrations) :point_left:
___
# :chart_with_downwards_trend: Session Profiler
Here is what the app was doing right before the bug was reported:
Key | Value
--|--
CPU Load | 1%
Used Memory | 100.0% - 0.04/0.04 GB
Used Storage | 39.7% - 90.66/228.27 GB
Connectivity | no_connection - NA
Battery | 100% - unplugged
Orientation | portrait
Find all the changes that happened in the parameters mentioned above during the last 60 seconds before the bug was reported here: :point_right: **[View Full Session Profiler](https://dashboard.instabug.com/applications/test123/beta/bugs/482?show-session-profiler=true&utm_source=github&utm_medium=integrations)** :point_left:
___
# :mag_right: Logs
### User Steps
Here are the last 10 steps done by the user right before the bug was reported:
```
20:39:58 Top View: SwiftRadio.NowPlayingViewController
20:39:57 Tap in UIStackView in SwiftRadio.StationsViewController
20:39:56 Top View: SwiftRadio.StationsViewController
20:39:55 Tap in _UIButtonBarButton in SwiftRadio.NowPlayingViewController
20:39:54 Top View: SwiftRadio.NowPlayingViewController
20:39:54 Tap in UIStackView in SwiftRadio.StationsViewController
10:49:08 Tap in UITableView in SwiftRadio.StationsViewController
10:49:05 Top View: SwiftRadio.StationsViewController
10:49:04 Application: DidBecomeActive
10:49:04 Application: SceneDidActivate
```
Find all the user steps done by the user throughout the session here: :point_right: **[View All User Steps](https://dashboard.instabug.com/applications/test123/beta/bugs/482?show-logs=user_steps&utm_source=github&utm_medium=integrations)** :point_left:
___
# :camera: Images
[](https://d38gnqwzxziyyy.cloudfront.net/attachments/bugs/18914425/b3d01fe8d391f20ef8c8c9fd5c37c689_original/27307959/2022092210410222010394.jpg?Expires=4819552881&Signature=rlHi1oncVITc-VXwsg1mkxpt7C~XFoFpJpCVNSjJg6vXkZdi-Pl9WBd8fDb9WvJ66waeZmM~wurchMArdUGnidHmw5WJ1CSxWsqBlC-Qvgu9sBvJpV0akWhdIH97IJ~BXYbWpbuy76mesm5wNIiDg03Ryt4Fb215jA1g9Z7n6SvFQmZnDvbTrVav7Aez8EOnm-5DeZIT~XBsXA0k6VvJ7gzvX-NrVpBcZuFjqa9GmBKv6Jv55yDxF82cj29xKPVAeb6AtfIWwOTzaIpMKY6y-HIrGIn9FUB~azfvPo~Q0yfqMcEWmNTHOz~sCWrYdNXi-h5R5hx6d47aSSz7p7eaww__&Key-Pair-Id=APKAIXAG65U6UUX7JAQQ)
___
# :warning: Looking for More Details?
1. **Network Log**: we are unable to capture your network requests automatically. If you are using AFNetworking or Alamofire, [**check the details mentioned here**](https://docs.instabug.com/docs/ios-logging?utm_source=github&utm_medium=integrations#section-requests-not-appearing-in-logs).
2. **User Events**: start capturing custom User Events to send them along with each report. [**Find all the details in the docs**](https://docs.instabug.com/docs/ios-logging?utm_source=github&utm_medium=integrations).
3. **Instabug Log**: start adding Instabug logs to see them right inside each report you receive. [**Find all the details in the docs**](https://docs.instabug.com/docs/ios-logging?utm_source=github&utm_medium=integrations).
4. **Console Log**: when enabled you will see them right inside each report you receive. [**Find all the details in the docs**](https://docs.instabug.com/docs/ios-logging?utm_source=github&utm_medium=integrations). | non_priority | error playing clipboard bug details error playing key value reported at utc categories report a bug usability issue tags forwarded to test app version session duration device ios display location cairo egypt en point right point left chart with downwards trend session profiler here is what the app was doing right before the bug was reported key value cpu load used memory gb used storage gb connectivity no connection na battery unplugged orientation portrait find all the changes that happened in the parameters mentioned above during the last seconds before the bug was reported here point right point left mag right logs user steps here are the last steps done by the user right before the bug was reported top view swiftradio nowplayingviewcontroller tap in uistackview in swiftradio stationsviewcontroller top view swiftradio stationsviewcontroller tap in uibuttonbarbutton in swiftradio nowplayingviewcontroller top view swiftradio nowplayingviewcontroller tap in uistackview in swiftradio stationsviewcontroller tap in uitableview in swiftradio stationsviewcontroller top view swiftradio stationsviewcontroller application didbecomeactive application scenedidactivate find all the user steps done by the user throughout the session here point right point left camera images warning looking for more details network log we are unable to capture your network requests automatically if you are using afnetworking or alamofire user events start capturing custom user events to send them along with each report instabug log start adding instabug logs to see them right inside each report you receive console log when enabled you will see them right inside each report you receive | 0 |
136,212 | 30,499,191,993 | IssuesEvent | 2023-07-18 12:57:16 | anoma/namada | https://api.github.com/repos/anoma/namada | closed | Remove native VP `ADDR` associated type | ledger refactor / code quality | The `ADDR` associated type in native VPs never gets used for anything useful. #1718 and #1693 introduce internal addresses containing data. Since there is no reasonable default to instantiate this data with, we should remove the `ADDR` type altogether from the native VP interface. | 1.0 | Remove native VP `ADDR` associated type - The `ADDR` associated type in native VPs never gets used for anything useful. #1718 and #1693 introduce internal addresses containing data. Since there is no reasonable default to instantiate this data with, we should remove the `ADDR` type altogether from the native VP interface. | non_priority | remove native vp addr associated type the addr associated type in native vps never gets used for anything useful and introduce internal addresses containing data since there is no reasonable default to instantiate this data with we should remove the addr type altogether from the native vp interface | 0 |
105,984 | 13,236,718,623 | IssuesEvent | 2020-08-18 20:18:43 | phetsims/natural-selection | https://api.github.com/repos/phetsims/natural-selection | opened | recessive mutations should not be favored by environmental factors | design:general | This came up in the context of https://github.com/phetsims/natural-selection/issues/183, revising the Food model.
Recessive mutants are currently excluded from application of environmental factors. This can lead to incorrect conclusions, and odd behavior if recessive mutants are the sole remaining bunnies.
@amanda-phet and I discussed on Zoom, and decided that this behavior is incorrect. Recessive mutants can be favored during mating, to make them appear in the phenotype more quickly. But they should not be favored during selection.
I will change this. If we discover that it causes other problem, we can revisit, and it's relatively easy to revert. | 1.0 | recessive mutations should not be favored by environmental factors - This came up in the context of https://github.com/phetsims/natural-selection/issues/183, revising the Food model.
Recessive mutants are currently excluded from application of environmental factors. This can lead to incorrect conclusions, and odd behavior if recessive mutants are the sole remaining bunnies.
@amanda-phet and I discussed on Zoom, and decided that this behavior is incorrect. Recessive mutants can be favored during mating, to make them appear in the phenotype more quickly. But they should not be favored during selection.
I will change this. If we discover that it causes other problem, we can revisit, and it's relatively easy to revert. | non_priority | recessive mutations should not be favored by environmental factors this came up in the context of revising the food model recessive mutants are currently excluded from application of environmental factors this can lead to incorrect conclusions and odd behavior if recessive mutants are the sole remaining bunnies amanda phet and i discussed on zoom and decided that this behavior is incorrect recessive mutants can be favored during mating to make them appear in the phenotype more quickly but they should not be favored during selection i will change this if we discover that it causes other problem we can revisit and it s relatively easy to revert | 0 |
3,960 | 15,033,217,454 | IssuesEvent | 2021-02-02 11:11:38 | gchq/Gaffer | https://api.github.com/repos/gchq/Gaffer | closed | Add action to rerun the last release | automation enhancement | If the Maven deploy command fails because of a network issue, it would be handy to have a way of re-running it. Simply re-running the Release workflow won't work because It also does things like create a tag (which can't be created twice). Therefore there should be a workflow that can be triggered by a member of the team to re-run the latest release. | 1.0 | Add action to rerun the last release - If the Maven deploy command fails because of a network issue, it would be handy to have a way of re-running it. Simply re-running the Release workflow won't work because It also does things like create a tag (which can't be created twice). Therefore there should be a workflow that can be triggered by a member of the team to re-run the latest release. | non_priority | add action to rerun the last release if the maven deploy command fails because of a network issue it would be handy to have a way of re running it simply re running the release workflow won t work because it also does things like create a tag which can t be created twice therefore there should be a workflow that can be triggered by a member of the team to re run the latest release | 0 |
268,630 | 23,385,306,935 | IssuesEvent | 2022-08-11 13:18:33 | OpenOlitor/OpenOlitor | https://api.github.com/repos/OpenOlitor/OpenOlitor | closed | Filters are not working as expected | bug ready:test | There are 3 filters available in the customer detail view, collaboration detail view and creation of a new invoice view. Those filters are supposed to send a request to the back-end with the string to be found. At the moment, the back-end is always sending back the whole list of customer and/or persons and filtered on the front-end.
The expected behavior is to return from the backend the list of customers and persons already filtered. Once this workflow is corrected the frontend should display the list that is returned. | 1.0 | Filters are not working as expected - There are 3 filters available in the customer detail view, collaboration detail view and creation of a new invoice view. Those filters are supposed to send a request to the back-end with the string to be found. At the moment, the back-end is always sending back the whole list of customer and/or persons and filtered on the front-end.
The expected behavior is to return from the backend the list of customers and persons already filtered. Once this workflow is corrected the frontend should display the list that is returned. | non_priority | filters are not working as expected there are filters available in the customer detail view collaboration detail view and creation of a new invoice view those filters are supposed to send a request to the back end with the string to be found at the moment the back end is always sending back the whole list of customer and or persons and filtered on the front end the expected behavior is to return from the backend the list of customers and persons already filtered once this workflow is corrected the frontend should display the list that is returned | 0 |
14,588 | 9,358,674,613 | IssuesEvent | 2019-04-02 03:28:14 | sesong11/NodeStartUpKit | https://api.github.com/repos/sesong11/NodeStartUpKit | opened | WS-2017-0236 Medium Severity Vulnerability detected by WhiteSource | security vulnerability | ## WS-2017-0236 - Medium Severity Vulnerability
<details><summary><img src='https://www.whitesourcesoftware.com/wp-content/uploads/2018/10/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>growl-1.9.2.tgz</b></p></summary>
<p>Growl unobtrusive notifications</p>
<p>path: /tmp/git/NodeStartUpKit/node_modules/growl/package.json</p>
<p>
<p>Library home page: <a href=http://registry.npmjs.org/growl/-/growl-1.9.2.tgz>http://registry.npmjs.org/growl/-/growl-1.9.2.tgz</a></p>
Dependency Hierarchy:
- mocha-3.1.2.tgz (Root Library)
- :x: **growl-1.9.2.tgz** (Vulnerable Library)
</p>
</details>
<p></p>
<details><summary><img src='https://www.whitesourcesoftware.com/wp-content/uploads/2018/10/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
Affected versions of the package are vulnerable to Arbitrary Code Injection.
<p>Publish Date: 2017-05-01
<p>URL: <a href=https://github.com/tj/node-growl/commit/d9f6ea2fb215ab9c5bce3e9ee88b1f0803aaf71e>WS-2017-0236</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://www.whitesourcesoftware.com/wp-content/uploads/2018/10/cvss3.png' width=19 height=20> CVSS 2 Score Details (<b>5.6</b>)</summary>
<p>
Base Score Metrics not available</p>
</p>
</details>
<p></p>
<details><summary><img src='https://www.whitesourcesoftware.com/wp-content/uploads/2018/10/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Change files</p>
<p>Origin: <a href="https://github.com/tj/node-growl/commit/d9f6ea2fb215ab9c5bce3e9ee88b1f0803aaf71e">https://github.com/tj/node-growl/commit/d9f6ea2fb215ab9c5bce3e9ee88b1f0803aaf71e</a></p>
<p>Release Date: 2016-09-05</p>
<p>Fix Resolution: Replace or update the following files: package.json, growl.js</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | WS-2017-0236 Medium Severity Vulnerability detected by WhiteSource - ## WS-2017-0236 - Medium Severity Vulnerability
<details><summary><img src='https://www.whitesourcesoftware.com/wp-content/uploads/2018/10/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>growl-1.9.2.tgz</b></p></summary>
<p>Growl unobtrusive notifications</p>
<p>path: /tmp/git/NodeStartUpKit/node_modules/growl/package.json</p>
<p>
<p>Library home page: <a href=http://registry.npmjs.org/growl/-/growl-1.9.2.tgz>http://registry.npmjs.org/growl/-/growl-1.9.2.tgz</a></p>
Dependency Hierarchy:
- mocha-3.1.2.tgz (Root Library)
- :x: **growl-1.9.2.tgz** (Vulnerable Library)
</p>
</details>
<p></p>
<details><summary><img src='https://www.whitesourcesoftware.com/wp-content/uploads/2018/10/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
Affected versions of the package are vulnerable to Arbitrary Code Injection.
<p>Publish Date: 2017-05-01
<p>URL: <a href=https://github.com/tj/node-growl/commit/d9f6ea2fb215ab9c5bce3e9ee88b1f0803aaf71e>WS-2017-0236</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://www.whitesourcesoftware.com/wp-content/uploads/2018/10/cvss3.png' width=19 height=20> CVSS 2 Score Details (<b>5.6</b>)</summary>
<p>
Base Score Metrics not available</p>
</p>
</details>
<p></p>
<details><summary><img src='https://www.whitesourcesoftware.com/wp-content/uploads/2018/10/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Change files</p>
<p>Origin: <a href="https://github.com/tj/node-growl/commit/d9f6ea2fb215ab9c5bce3e9ee88b1f0803aaf71e">https://github.com/tj/node-growl/commit/d9f6ea2fb215ab9c5bce3e9ee88b1f0803aaf71e</a></p>
<p>Release Date: 2016-09-05</p>
<p>Fix Resolution: Replace or update the following files: package.json, growl.js</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_priority | ws medium severity vulnerability detected by whitesource ws medium severity vulnerability vulnerable library growl tgz growl unobtrusive notifications path tmp git nodestartupkit node modules growl package json library home page a href dependency hierarchy mocha tgz root library x growl tgz vulnerable library vulnerability details affected versions of the package are vulnerable to arbitrary code injection publish date url a href cvss score details base score metrics not available suggested fix type change files origin a href release date fix resolution replace or update the following files package json growl js step up your open source security game with whitesource | 0 |
171,298 | 14,286,759,883 | IssuesEvent | 2020-11-23 15:32:14 | grafana/tempo | https://api.github.com/repos/grafana/tempo | opened | Document s3 permissions | documentation | **Is your feature request related to a problem? Please describe.**
We currently support s3, but don't have a list of the required permissions. | 1.0 | Document s3 permissions - **Is your feature request related to a problem? Please describe.**
We currently support s3, but don't have a list of the required permissions. | non_priority | document permissions is your feature request related to a problem please describe we currently support but don t have a list of the required permissions | 0 |
392,910 | 26,964,615,815 | IssuesEvent | 2023-02-08 21:09:00 | denoland/deno_lint | https://api.github.com/repos/denoland/deno_lint | closed | [Docs] No highlighting in `ignoring-rules`. | bug documentation | It seems that in the `ignoring-rules` page, there is no highlighting for the code present. Maybe use [`deno-gfm`](https://github.com/denoland/deno-gfm/)? | 1.0 | [Docs] No highlighting in `ignoring-rules`. - It seems that in the `ignoring-rules` page, there is no highlighting for the code present. Maybe use [`deno-gfm`](https://github.com/denoland/deno-gfm/)? | non_priority | no highlighting in ignoring rules it seems that in the ignoring rules page there is no highlighting for the code present maybe use | 0 |
129,339 | 27,446,354,852 | IssuesEvent | 2023-03-02 14:32:24 | dotnet/runtime | https://api.github.com/repos/dotnet/runtime | closed | [wasm] System.Memory.Tests broken if SIMD is enabled | arch-wasm area-Codegen-Interpreter-mono in-pr | Right now SIMD is disabled for HOST_BROWSER because the jiterp doesn't support it. If you turn it on it seems to break System.Memory.Tests, see this log:
https://helixre107v0xdcypoyl9e7f.blob.core.windows.net/dotnet-runtime-refs-pull-82773-merge-d904e60cf8534bb888/normal-System.Memory.Tests/1/console.55efc30d.log?helixlogtype=result
```
... etc ...
fail: [FAIL] System.Buffers.Binary.Tests.ReverseEndiannessUnitTests.ReverseEndianness_Span_AllElementsReversed<Int16>(original: [-1426, 31290, -14834, -477, 28732, ...])
info: Assert.Equal() Failure
info: ↓ (pos 0)
info: Expected: [28410, 14970, 3782, 9214, 15472, ...]
info: Actual: [-1282, 31354, -14642, -257, 28796, ...]
info: ↑ (pos 0)
info: at System.Buffers.Binary.Tests.ReverseEndiannessUnitTests.ReverseEndianness_Span_AllElementsReversed[Int16](Int16[] original)
info: at System.Reflection.MethodInvoker.InterpretedInvoke(Object obj, IntPtr* args)
info: at System.Reflection.MethodInvoker.Invoke(Object obj, IntPtr* args, BindingFlags invokeAttr)
info: Finished: System.Memory.Tests.dll
info:
info: === TEST EXECUTION SUMMARY ===
info: Total: 48920, Errors: 0, Failed: 56, Skipped: 0, Time: 117.80777s
```
This reproduces both with jiterp SIMD enabled (from my PR) and with jiterp SIMD disabled, and reproduces both when the jiterp uses v128 opcodes and when it doesn't. | 1.0 | [wasm] System.Memory.Tests broken if SIMD is enabled - Right now SIMD is disabled for HOST_BROWSER because the jiterp doesn't support it. If you turn it on it seems to break System.Memory.Tests, see this log:
https://helixre107v0xdcypoyl9e7f.blob.core.windows.net/dotnet-runtime-refs-pull-82773-merge-d904e60cf8534bb888/normal-System.Memory.Tests/1/console.55efc30d.log?helixlogtype=result
```
... etc ...
fail: [FAIL] System.Buffers.Binary.Tests.ReverseEndiannessUnitTests.ReverseEndianness_Span_AllElementsReversed<Int16>(original: [-1426, 31290, -14834, -477, 28732, ...])
info: Assert.Equal() Failure
info: ↓ (pos 0)
info: Expected: [28410, 14970, 3782, 9214, 15472, ...]
info: Actual: [-1282, 31354, -14642, -257, 28796, ...]
info: ↑ (pos 0)
info: at System.Buffers.Binary.Tests.ReverseEndiannessUnitTests.ReverseEndianness_Span_AllElementsReversed[Int16](Int16[] original)
info: at System.Reflection.MethodInvoker.InterpretedInvoke(Object obj, IntPtr* args)
info: at System.Reflection.MethodInvoker.Invoke(Object obj, IntPtr* args, BindingFlags invokeAttr)
info: Finished: System.Memory.Tests.dll
info:
info: === TEST EXECUTION SUMMARY ===
info: Total: 48920, Errors: 0, Failed: 56, Skipped: 0, Time: 117.80777s
```
This reproduces both with jiterp SIMD enabled (from my PR) and with jiterp SIMD disabled, and reproduces both when the jiterp uses v128 opcodes and when it doesn't. | non_priority | system memory tests broken if simd is enabled right now simd is disabled for host browser because the jiterp doesn t support it if you turn it on it seems to break system memory tests see this log etc fail system buffers binary tests reverseendiannessunittests reverseendianness span allelementsreversed original info assert equal failure info ↓ pos info expected info actual info ↑ pos info at system buffers binary tests reverseendiannessunittests reverseendianness span allelementsreversed original info at system reflection methodinvoker interpretedinvoke object obj intptr args info at system reflection methodinvoker invoke object obj intptr args bindingflags invokeattr info finished system memory tests dll info info test execution summary info total errors failed skipped time this reproduces both with jiterp simd enabled from my pr and with jiterp simd disabled and reproduces both when the jiterp uses opcodes and when it doesn t | 0 |
42,035 | 6,962,094,656 | IssuesEvent | 2017-12-08 12:15:29 | IATI/IATI-Extra-Documentation | https://api.github.com/repos/IATI/IATI-Extra-Documentation | opened | Add `document-link` element to `result` element | 2.03 Documentation enhancement | Add `document-link` to `result`:
- [ ] Add example to `activity-standard-example.xml`
- [ ] Create/amend `.rst` file for element
- [ ] Provide usage example
- [ ] Add to changelog
- [ ] Update 2.03 changelog in IATI-Guidance | 1.0 | Add `document-link` element to `result` element - Add `document-link` to `result`:
- [ ] Add example to `activity-standard-example.xml`
- [ ] Create/amend `.rst` file for element
- [ ] Provide usage example
- [ ] Add to changelog
- [ ] Update 2.03 changelog in IATI-Guidance | non_priority | add document link element to result element add document link to result add example to activity standard example xml create amend rst file for element provide usage example add to changelog update changelog in iati guidance | 0 |
290,071 | 21,801,980,390 | IssuesEvent | 2022-05-16 06:40:12 | haskell/cabal | https://api.github.com/repos/haskell/cabal | closed | document "cabal install --lib" | documentation cabal-install: cmd/install | Hi.
The "--lib" flag to "cabal install" is not mentioned at https://www.haskell.org/cabal/users-guide/installing-packages.html#building-and-installing-a-user-package , and is missing from https://www.haskell.org/cabal/users-guide/genindex.html .
This creates confusion: 1. what does the flag do? 2. are we even looking in the right place for documentation? - e.g., sandboxing, documented there, is no longer a thing since we have environment files now?
(e.g., https://github.com/tidalcycles/Tidal/issues/572#issuecomment-559941709 ) | 1.0 | document "cabal install --lib" - Hi.
The "--lib" flag to "cabal install" is not mentioned at https://www.haskell.org/cabal/users-guide/installing-packages.html#building-and-installing-a-user-package , and is missing from https://www.haskell.org/cabal/users-guide/genindex.html .
This creates confusion: 1. what does the flag do? 2. are we even looking in the right place for documentation? - e.g., sandboxing, documented there, is no longer a thing since we have environment files now?
(e.g., https://github.com/tidalcycles/Tidal/issues/572#issuecomment-559941709 ) | non_priority | document cabal install lib hi the lib flag to cabal install is not mentioned at and is missing from this creates confusion what does the flag do are we even looking in the right place for documentation e g sandboxing documented there is no longer a thing since we have environment files now e g | 0 |
90,753 | 10,696,056,769 | IssuesEvent | 2019-10-23 14:06:30 | EMAD-2019-Accenture/App | https://api.github.com/repos/EMAD-2019-Accenture/App | closed | Conversione nomi | documentation | - [x] Prodotti -> Articoli
- [x] Offerta -> Promozione
- [x] Cliente -> Acquirente
- [x] Tipologia -> Categoria
| 1.0 | Conversione nomi - - [x] Prodotti -> Articoli
- [x] Offerta -> Promozione
- [x] Cliente -> Acquirente
- [x] Tipologia -> Categoria
| non_priority | conversione nomi prodotti articoli offerta promozione cliente acquirente tipologia categoria | 0 |
217,209 | 16,848,836,150 | IssuesEvent | 2021-06-20 04:12:49 | hakehuang/infoflow | https://api.github.com/repos/hakehuang/infoflow | opened |
tests-ci :kernel.memory_protection.userspace.domain_add_thread_drop_to_user : zephyr-v2.6.0-286-g46029914a7ac: lpcxpresso55s28: test Timeout
| area: Tests |
**Describe the bug**
kernel.memory_protection.userspace.domain_add_thread_drop_to_user test is Timeout on zephyr-v2.6.0-286-g46029914a7ac on lpcxpresso55s28
see logs for details
**To Reproduce**
1.
```
scripts/twister --device-testing --device-serial /dev/ttyACM0 -p lpcxpresso55s28 --testcase-root tests --sub-test kernel.memory_protection
```
2. See error
**Expected behavior**
test pass
**Impact**
**Logs and console output**
```
*** Booting Zephyr OS build zephyr-v2.6.0-286-g46029914a7ac ***
Running test suite userspace
===================================================================
START - test_is_usermode
PASS - test_is_usermode in 0.1 seconds
===================================================================
START - test_write_control
PASS - test_write_control in 0.1 seconds
===================================================================
START - test_disable_mmu_mpu
ASSERTION FAIL [esf != ((void *)0)] @ WEST_TOPDIR/zephyr/arch/arm/core/aarch32/cortex_m/fault.c:993
ESF could not be retrieved successfully. Shall never occur.
ASSERTION FAIL [esf != ((void *)0)] @ WEST_TOPDIR/zephyr/arch/arm/core/aarch32/cortex_m/fault.c:993
ESF could not be retrieved successfully. Shall never occur.
```
**Environment (please complete the following information):**
- OS: (e.g. Linux )
- Toolchain (e.g Zephyr SDK)
- Commit SHA or Version used: zephyr-v2.6.0-286-g46029914a7ac
| 1.0 |
tests-ci :kernel.memory_protection.userspace.domain_add_thread_drop_to_user : zephyr-v2.6.0-286-g46029914a7ac: lpcxpresso55s28: test Timeout
-
**Describe the bug**
kernel.memory_protection.userspace.domain_add_thread_drop_to_user test is Timeout on zephyr-v2.6.0-286-g46029914a7ac on lpcxpresso55s28
see logs for details
**To Reproduce**
1.
```
scripts/twister --device-testing --device-serial /dev/ttyACM0 -p lpcxpresso55s28 --testcase-root tests --sub-test kernel.memory_protection
```
2. See error
**Expected behavior**
test pass
**Impact**
**Logs and console output**
```
*** Booting Zephyr OS build zephyr-v2.6.0-286-g46029914a7ac ***
Running test suite userspace
===================================================================
START - test_is_usermode
PASS - test_is_usermode in 0.1 seconds
===================================================================
START - test_write_control
PASS - test_write_control in 0.1 seconds
===================================================================
START - test_disable_mmu_mpu
ASSERTION FAIL [esf != ((void *)0)] @ WEST_TOPDIR/zephyr/arch/arm/core/aarch32/cortex_m/fault.c:993
ESF could not be retrieved successfully. Shall never occur.
ASSERTION FAIL [esf != ((void *)0)] @ WEST_TOPDIR/zephyr/arch/arm/core/aarch32/cortex_m/fault.c:993
ESF could not be retrieved successfully. Shall never occur.
```
**Environment (please complete the following information):**
- OS: (e.g. Linux )
- Toolchain (e.g Zephyr SDK)
- Commit SHA or Version used: zephyr-v2.6.0-286-g46029914a7ac
| non_priority | tests ci kernel memory protection userspace domain add thread drop to user zephyr test timeout describe the bug kernel memory protection userspace domain add thread drop to user test is timeout on zephyr on see logs for details to reproduce scripts twister device testing device serial dev p testcase root tests sub test kernel memory protection see error expected behavior test pass impact logs and console output booting zephyr os build zephyr running test suite userspace start test is usermode pass test is usermode in seconds start test write control pass test write control in seconds start test disable mmu mpu assertion fail west topdir zephyr arch arm core cortex m fault c esf could not be retrieved successfully shall never occur assertion fail west topdir zephyr arch arm core cortex m fault c esf could not be retrieved successfully shall never occur environment please complete the following information os e g linux toolchain e g zephyr sdk commit sha or version used zephyr | 0 |
27,661 | 22,107,188,770 | IssuesEvent | 2022-06-01 17:56:19 | hackforla/HomeUniteUs | https://api.github.com/repos/hackforla/HomeUniteUs | closed | Create resources for Amazon Cognito HUU tenant | Role: Back End Feature: Infrastructure points: 2 | ### Overview
Create user/identity pools, configure external OIDC providers and ensure connectivity
### Action Items
- [ ] Create User Pool for authentication
- [ ] Create Identity Pool for authorization
- [ ] Connect to Cognito from client (HUU source or example)
### Resources/Instructions
https://docs.aws.amazon.com/cognito/latest/developerguide/getting-started-with-cognito-user-pools.html
https://docs.aws.amazon.com/cognito/latest/developerguide/getting-started-with-identity-pools.html
https://aws.amazon.com/premiumsupport/knowledge-center/cognito-user-pools-identity-pools/
| 1.0 | Create resources for Amazon Cognito HUU tenant - ### Overview
Create user/identity pools, configure external OIDC providers and ensure connectivity
### Action Items
- [ ] Create User Pool for authentication
- [ ] Create Identity Pool for authorization
- [ ] Connect to Cognito from client (HUU source or example)
### Resources/Instructions
https://docs.aws.amazon.com/cognito/latest/developerguide/getting-started-with-cognito-user-pools.html
https://docs.aws.amazon.com/cognito/latest/developerguide/getting-started-with-identity-pools.html
https://aws.amazon.com/premiumsupport/knowledge-center/cognito-user-pools-identity-pools/
| non_priority | create resources for amazon cognito huu tenant overview create user identity pools configure external oidc providers and ensure connectivity action items create user pool for authentication create identity pool for authorization connect to cognito from client huu source or example resources instructions | 0 |
313,725 | 23,489,423,659 | IssuesEvent | 2022-08-17 17:09:57 | bcgov/PSA-DJ-program | https://api.github.com/repos/bcgov/PSA-DJ-program | opened | SL REVIEW: Front end form in Digital Journeys | Documentation UX SL Review | This epic will cover all the tickets/issues related to creating the front-end of the form in Formsflow | 1.0 | SL REVIEW: Front end form in Digital Journeys - This epic will cover all the tickets/issues related to creating the front-end of the form in Formsflow | non_priority | sl review front end form in digital journeys this epic will cover all the tickets issues related to creating the front end of the form in formsflow | 0 |
134,727 | 30,121,813,460 | IssuesEvent | 2023-06-30 15:45:55 | roanlinde/nodegoat | https://api.github.com/repos/roanlinde/nodegoat | opened | CVE: 2020-7598 found in minimist - Version: 1.2.5,0.0.10,0.0.8 [JS] | Severity: High Veracode Dependency Scanning | Veracode Software Composition Analysis
===============================
Attribute | Details
| --- | --- |
Library | minimist
Description | parse argument options
Language | JS
Vulnerability | Prototype Pollution
Vulnerability description | minimist is vulnerable to prototype pollution. The library allows an attacker to modify properties of Object.prototype using a `constructor` or `__proto__` payload.
CVE | 2020-7598
CVSS score | 6.8
Vulnerability present in version/s | 0.0.0-0.2.0
Found library version/s | 1.2.5,0.0.10,0.0.8
Vulnerability fixed in version | 0.2.1
Library latest version | 1.2.8
Fix |
Links:
- https://sca.analysiscenter.veracode.com/vulnerability-database/libraries/617?version=1.2.5
- https://sca.analysiscenter.veracode.com/vulnerability-database/vulnerabilities/22678
- Patch: | 1.0 | CVE: 2020-7598 found in minimist - Version: 1.2.5,0.0.10,0.0.8 [JS] - Veracode Software Composition Analysis
===============================
Attribute | Details
| --- | --- |
Library | minimist
Description | parse argument options
Language | JS
Vulnerability | Prototype Pollution
Vulnerability description | minimist is vulnerable to prototype pollution. The library allows an attacker to modify properties of Object.prototype using a `constructor` or `__proto__` payload.
CVE | 2020-7598
CVSS score | 6.8
Vulnerability present in version/s | 0.0.0-0.2.0
Found library version/s | 1.2.5,0.0.10,0.0.8
Vulnerability fixed in version | 0.2.1
Library latest version | 1.2.8
Fix |
Links:
- https://sca.analysiscenter.veracode.com/vulnerability-database/libraries/617?version=1.2.5
- https://sca.analysiscenter.veracode.com/vulnerability-database/vulnerabilities/22678
- Patch: | non_priority | cve found in minimist version veracode software composition analysis attribute details library minimist description parse argument options language js vulnerability prototype pollution vulnerability description minimist is vulnerable to prototype pollution the library allows an attacker to modify properties of object prototype using a constructor or proto payload cve cvss score vulnerability present in version s found library version s vulnerability fixed in version library latest version fix links patch | 0 |
399,571 | 27,245,442,392 | IssuesEvent | 2023-02-22 01:21:22 | devcontainers-contrib/templates | https://api.github.com/repos/devcontainers-contrib/templates | closed | Add proper description & tags | documentation enhancement | I don't think this repo has a description as of yet. It would probably be a good idea to add one.
It should probably be the same as the tagline thing in the readme (at least, that's my @jcbhmr convention). That description is currently:
> 📂 Pre-made .devcontainer folders for starting your next project
☝ I think this one is the weakest of the bunch shown below. I might change the readme around and add a better header image with a new tagline.
Here are some other ideas:
- 💻 80% of the configuration you'll ever need
- 🥧 Ready-made `devcontainer.json` files for popular projects
- 🚀 Devcontainer configurations to get you off the ground
- 📋 Template `devcontainer.json` files for popular projects
- 🚀 @<!---->devcontainers configurations to get you started
I think that an emoji is a good idea, but that's again the @jcbhmr convention peeking through. Some other popular orgs/people do it too, though: https://github.com/wow-actions https://github.com/sindresorhus
I don't have the power to actually edit the description/URL/tags of this repo. That falls on you @danielbraun89 🤷♂️
Speaking of tags, while you're at it, here's some ideas for tags:
- https://github.com/topics/devcontainer
- https://github.com/topics/devcontainer-template
- https://github.com/topics/getting-started | 1.0 | Add proper description & tags - I don't think this repo has a description as of yet. It would probably be a good idea to add one.
It should probably be the same as the tagline thing in the readme (at least, that's my @jcbhmr convention). That description is currently:
> 📂 Pre-made .devcontainer folders for starting your next project
☝ I think this one is the weakest of the bunch shown below. I might change the readme around and add a better header image with a new tagline.
Here are some other ideas:
- 💻 80% of the configuration you'll ever need
- 🥧 Ready-made `devcontainer.json` files for popular projects
- 🚀 Devcontainer configurations to get you off the ground
- 📋 Template `devcontainer.json` files for popular projects
- 🚀 @<!---->devcontainers configurations to get you started
I think that an emoji is a good idea, but that's again the @jcbhmr convention peeking through. Some other popular orgs/people do it too, though: https://github.com/wow-actions https://github.com/sindresorhus
I don't have the power to actually edit the description/URL/tags of this repo. That falls on you @danielbraun89 🤷♂️
Speaking of tags, while you're at it, here's some ideas for tags:
- https://github.com/topics/devcontainer
- https://github.com/topics/devcontainer-template
- https://github.com/topics/getting-started | non_priority | add proper description tags i don t think this repo has a description as of yet it would probably be a good idea to add one it should probably be the same as the tagline thing in the readme at least that s my jcbhmr convention that description is currently 📂 pre made devcontainer folders for starting your next project ☝ i think this one is the weakest of the bunch shown below i might change the readme around and add a better header image with a new tagline here are some other ideas 💻 of the configuration you ll ever need 🥧 ready made devcontainer json files for popular projects 🚀 devcontainer configurations to get you off the ground 📋 template devcontainer json files for popular projects 🚀 devcontainers configurations to get you started i think that an emoji is a good idea but that s again the jcbhmr convention peeking through some other popular orgs people do it too though i don t have the power to actually edit the description url tags of this repo that falls on you 🤷♂️ speaking of tags while you re at it here s some ideas for tags | 0 |
221,765 | 24,657,126,885 | IssuesEvent | 2022-10-18 01:21:18 | mcaj-git/nextcloud-dev | https://api.github.com/repos/mcaj-git/nextcloud-dev | opened | CVE-2022-37603 (High) detected in loader-utils-2.0.0.tgz | security vulnerability | ## CVE-2022-37603 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>loader-utils-2.0.0.tgz</b></p></summary>
<p>utils for webpack loaders</p>
<p>Library home page: <a href="https://registry.npmjs.org/loader-utils/-/loader-utils-2.0.0.tgz">https://registry.npmjs.org/loader-utils/-/loader-utils-2.0.0.tgz</a></p>
<p>
Dependency Hierarchy:
- eslint-loader-4.0.2.tgz (Root Library)
- :x: **loader-utils-2.0.0.tgz** (Vulnerable Library)
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
A Regular expression denial of service (ReDoS) flaw was found in Function interpolateName in interpolateName.js in webpack loader-utils 2.0.0 via the url variable in interpolateName.js.
<p>Publish Date: 2022-10-14
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-37603>CVE-2022-37603</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Release Date: 2022-10-14</p>
<p>Fix Resolution: loader-utils - 3.0.0</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | CVE-2022-37603 (High) detected in loader-utils-2.0.0.tgz - ## CVE-2022-37603 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>loader-utils-2.0.0.tgz</b></p></summary>
<p>utils for webpack loaders</p>
<p>Library home page: <a href="https://registry.npmjs.org/loader-utils/-/loader-utils-2.0.0.tgz">https://registry.npmjs.org/loader-utils/-/loader-utils-2.0.0.tgz</a></p>
<p>
Dependency Hierarchy:
- eslint-loader-4.0.2.tgz (Root Library)
- :x: **loader-utils-2.0.0.tgz** (Vulnerable Library)
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
A Regular expression denial of service (ReDoS) flaw was found in Function interpolateName in interpolateName.js in webpack loader-utils 2.0.0 via the url variable in interpolateName.js.
<p>Publish Date: 2022-10-14
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-37603>CVE-2022-37603</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Release Date: 2022-10-14</p>
<p>Fix Resolution: loader-utils - 3.0.0</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_priority | cve high detected in loader utils tgz cve high severity vulnerability vulnerable library loader utils tgz utils for webpack loaders library home page a href dependency hierarchy eslint loader tgz root library x loader utils tgz vulnerable library found in base branch master vulnerability details a regular expression denial of service redos flaw was found in function interpolatename in interpolatename js in webpack loader utils via the url variable in interpolatename js publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact none integrity impact none availability impact high for more information on scores click a href suggested fix type upgrade version release date fix resolution loader utils step up your open source security game with mend | 0 |
32,081 | 15,211,655,105 | IssuesEvent | 2021-02-17 09:22:47 | hzi-braunschweig/SORMAS-Project | https://api.github.com/repos/hzi-braunschweig/SORMAS-Project | closed | Add setting to disable audit log of properties [1] | SSD backend change performance | <!--
If you've never submitted an issue to the SORMAS repository before or this is your first time using this template, please read the Contributing guidelines (accessible in the right sidebar) for an explanation about the information we'd like you to provide.
-->
### Situation Description
Currently SORMAS comes with two audit/history systems. Once is the audit log, that logs all changes to an external database, including who changes it. The other are the postgres history tables that automatically create a history entry whenever a table row is modified. Ideally we would use only the later one, but this is currently not possible, because it misses information on who changed the data.
Still it looks like we are running into performance problems on big systems, so it would be good to have a setting in the properties file to disable the audit log.
### Feature Description
- [x] Add a setting to the properties file to disable the attribute logging of the audit log (we have the history tables for this anyway), but be enabled be default.
- [x] Change Auditor.getValueContainerOf to not inspect the attributes when disabled
- [x] The information on whether the property audit log is enabled or disabled needs to be cached! | True | Add setting to disable audit log of properties [1] - <!--
If you've never submitted an issue to the SORMAS repository before or this is your first time using this template, please read the Contributing guidelines (accessible in the right sidebar) for an explanation about the information we'd like you to provide.
-->
### Situation Description
Currently SORMAS comes with two audit/history systems. Once is the audit log, that logs all changes to an external database, including who changes it. The other are the postgres history tables that automatically create a history entry whenever a table row is modified. Ideally we would use only the later one, but this is currently not possible, because it misses information on who changed the data.
Still it looks like we are running into performance problems on big systems, so it would be good to have a setting in the properties file to disable the audit log.
### Feature Description
- [x] Add a setting to the properties file to disable the attribute logging of the audit log (we have the history tables for this anyway), but be enabled be default.
- [x] Change Auditor.getValueContainerOf to not inspect the attributes when disabled
- [x] The information on whether the property audit log is enabled or disabled needs to be cached! | non_priority | add setting to disable audit log of properties if you ve never submitted an issue to the sormas repository before or this is your first time using this template please read the contributing guidelines accessible in the right sidebar for an explanation about the information we d like you to provide situation description currently sormas comes with two audit history systems once is the audit log that logs all changes to an external database including who changes it the other are the postgres history tables that automatically create a history entry whenever a table row is modified ideally we would use only the later one but this is currently not possible because it misses information on who changed the data still it looks like we are running into performance problems on big systems so it would be good to have a setting in the properties file to disable the audit log feature description add a setting to the properties file to disable the attribute logging of the audit log we have the history tables for this anyway but be enabled be default change auditor getvaluecontainerof to not inspect the attributes when disabled the information on whether the property audit log is enabled or disabled needs to be cached | 0 |
60,436 | 7,342,746,441 | IssuesEvent | 2018-03-07 09:04:03 | WordPress/gutenberg | https://api.github.com/repos/WordPress/gutenberg | closed | "Responsive buttons" should have tooltips and use consistent CSS techniques | Accessibility Needs Design Feedback | There are a few buttons that change depending on the viewport width. Let's call them "responsive buttons" for the sake of clarity.
<img width="584" alt="screen shot 2018-03-02 at 17 23 49" src="https://user-images.githubusercontent.com/1682452/36910177-48f624b8-1e40-11e8-87d4-c8243d776587.png">
<img width="522" alt="screen shot 2018-03-02 at 17 23 04" src="https://user-images.githubusercontent.com/1682452/36910175-48d9c48a-1e40-11e8-8edd-4fd9c3e01779.png">
In the desktop view, these buttons don't have tooltips. That's perfectly OK because there's already some visible text. However, in the responsive view the responsive buttons text gets hidden (using different CSS techniques) and they still have no tooltips.
Worth reminding any UI control whose meaning is communicated by only an icon should at least have a tooltip. Even on small screens.
Additionally, the "Upload" button text (see screenshot below) gets hidden setting `font-size: 0;`. I'd recommend to change this since there's no guarantee that assistive technologies and other software will consider such text "visible", they could completely ignore it.
The "Save Draft" button sets a smaller width to hide the text, it doesn't use `font-size: 0;`. For consistency, I'd suggest to improve consistency and use a unique pattern.
/cc @jasmussen | 1.0 | "Responsive buttons" should have tooltips and use consistent CSS techniques - There are a few buttons that change depending on the viewport width. Let's call them "responsive buttons" for the sake of clarity.
<img width="584" alt="screen shot 2018-03-02 at 17 23 49" src="https://user-images.githubusercontent.com/1682452/36910177-48f624b8-1e40-11e8-87d4-c8243d776587.png">
<img width="522" alt="screen shot 2018-03-02 at 17 23 04" src="https://user-images.githubusercontent.com/1682452/36910175-48d9c48a-1e40-11e8-8edd-4fd9c3e01779.png">
In the desktop view, these buttons don't have tooltips. That's perfectly OK because there's already some visible text. However, in the responsive view the responsive buttons text gets hidden (using different CSS techniques) and they still have no tooltips.
Worth reminding any UI control whose meaning is communicated by only an icon should at least have a tooltip. Even on small screens.
Additionally, the "Upload" button text (see screenshot below) gets hidden setting `font-size: 0;`. I'd recommend to change this since there's no guarantee that assistive technologies and other software will consider such text "visible", they could completely ignore it.
The "Save Draft" button sets a smaller width to hide the text, it doesn't use `font-size: 0;`. For consistency, I'd suggest to improve consistency and use a unique pattern.
/cc @jasmussen | non_priority | responsive buttons should have tooltips and use consistent css techniques there are a few buttons that change depending on the viewport width let s call them responsive buttons for the sake of clarity img width alt screen shot at src img width alt screen shot at src in the desktop view these buttons don t have tooltips that s perfectly ok because there s already some visible text however in the responsive view the responsive buttons text gets hidden using different css techniques and they still have no tooltips worth reminding any ui control whose meaning is communicated by only an icon should at least have a tooltip even on small screens additionally the upload button text see screenshot below gets hidden setting font size i d recommend to change this since there s no guarantee that assistive technologies and other software will consider such text visible they could completely ignore it the save draft button sets a smaller width to hide the text it doesn t use font size for consistency i d suggest to improve consistency and use a unique pattern cc jasmussen | 0 |
20,126 | 3,794,042,339 | IssuesEvent | 2016-03-22 15:45:07 | elastic/elasticsearch | https://api.github.com/repos/elastic/elasticsearch | closed | QuorumGatewayIT fails on master | test | The failure reproduces (e.g. with seed BD57BE5B57A9875A:5339034DFF2C888F). Stumbled upon it while running tests to get #16963 back up-to-date. Seems like we are missing the document that we index after the full cluster restart, when a single node is up. Seems quite bad at first glance.
```
java.lang.AssertionError: Count is 2 but 3 was expected. Total shards: 5 Successful shards: 5 & 0 shard failures:
at __randomizedtesting.SeedInfo.seed([BD57BE5B57A9875A:5339034DFF2C888F]:0)
at org.junit.Assert.fail(Assert.java:88)
at org.elasticsearch.test.hamcrest.ElasticsearchAssertions.assertHitCount(ElasticsearchAssertions.java:248)
at org.elasticsearch.gateway.QuorumGatewayIT.testQuorumRecovery(QuorumGatewayIT.java:103)
``` | 1.0 | QuorumGatewayIT fails on master - The failure reproduces (e.g. with seed BD57BE5B57A9875A:5339034DFF2C888F). Stumbled upon it while running tests to get #16963 back up-to-date. Seems like we are missing the document that we index after the full cluster restart, when a single node is up. Seems quite bad at first glance.
```
java.lang.AssertionError: Count is 2 but 3 was expected. Total shards: 5 Successful shards: 5 & 0 shard failures:
at __randomizedtesting.SeedInfo.seed([BD57BE5B57A9875A:5339034DFF2C888F]:0)
at org.junit.Assert.fail(Assert.java:88)
at org.elasticsearch.test.hamcrest.ElasticsearchAssertions.assertHitCount(ElasticsearchAssertions.java:248)
at org.elasticsearch.gateway.QuorumGatewayIT.testQuorumRecovery(QuorumGatewayIT.java:103)
``` | non_priority | quorumgatewayit fails on master the failure reproduces e g with seed stumbled upon it while running tests to get back up to date seems like we are missing the document that we index after the full cluster restart when a single node is up seems quite bad at first glance java lang assertionerror count is but was expected total shards successful shards shard failures at randomizedtesting seedinfo seed at org junit assert fail assert java at org elasticsearch test hamcrest elasticsearchassertions asserthitcount elasticsearchassertions java at org elasticsearch gateway quorumgatewayit testquorumrecovery quorumgatewayit java | 0 |
69,752 | 17,839,092,789 | IssuesEvent | 2021-09-03 07:40:37 | inmanta/inmanta-core | https://api.github.com/repos/inmanta/inmanta-core | opened | web-console clean_up_packages fails | build master task | The following indicates an error in `/clean_up_packages.js` that gets triggered during the cleanup phase of the [nightly builds](https://jenkins.inmanta.com/job/releases/job/npm/job/web-console-release/job/master/539/console):
```
$ node clean_up_packages
internal/modules/cjs/loader.js:1102
throw new ERR_REQUIRE_ESM(filename, parentPath, packageJsonPath);
^
Error [ERR_REQUIRE_ESM]: Must use import to load ES Module: /home/jenkins/workspace/s_npm_web-console-release_master/web-console/node_modules/node-fetch/src/index.js
require() of ES modules is not supported.
require() of /home/jenkins/workspace/s_npm_web-console-release_master/web-console/node_modules/node-fetch/src/index.js from /home/jenkins/workspace/s_npm_web-console-release_master/web-console/clean_up_packages.js is an ES module file as it is a .js file whose nearest parent package.json contains "type": "module" which defines all .js files in that package scope as ES modules.
Instead rename index.js to end in .cjs, change the requiring code to use import(), or remove "type": "module" from /home/jenkins/workspace/s_npm_web-console-release_master/web-console/node_modules/node-fetch/package.json.
at Object.Module._extensions..js (internal/modules/cjs/loader.js:1102:13)
at Module.load (internal/modules/cjs/loader.js:950:32)
at Function.Module._load (internal/modules/cjs/loader.js:790:14)
at Module.require (internal/modules/cjs/loader.js:974:19)
at require (internal/modules/cjs/helpers.js:92:18)
at Object.<anonymous> (/home/jenkins/workspace/s_npm_web-console-release_master/web-console/clean_up_packages.js:1:16)
at Module._compile (internal/modules/cjs/loader.js:1085:14)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:1114:10)
at Module.load (internal/modules/cjs/loader.js:950:32)
at Function.Module._load (internal/modules/cjs/loader.js:790:14) {
code: 'ERR_REQUIRE_ESM'
}
``` | 1.0 | web-console clean_up_packages fails - The following indicates an error in `/clean_up_packages.js` that gets triggered during the cleanup phase of the [nightly builds](https://jenkins.inmanta.com/job/releases/job/npm/job/web-console-release/job/master/539/console):
```
$ node clean_up_packages
internal/modules/cjs/loader.js:1102
throw new ERR_REQUIRE_ESM(filename, parentPath, packageJsonPath);
^
Error [ERR_REQUIRE_ESM]: Must use import to load ES Module: /home/jenkins/workspace/s_npm_web-console-release_master/web-console/node_modules/node-fetch/src/index.js
require() of ES modules is not supported.
require() of /home/jenkins/workspace/s_npm_web-console-release_master/web-console/node_modules/node-fetch/src/index.js from /home/jenkins/workspace/s_npm_web-console-release_master/web-console/clean_up_packages.js is an ES module file as it is a .js file whose nearest parent package.json contains "type": "module" which defines all .js files in that package scope as ES modules.
Instead rename index.js to end in .cjs, change the requiring code to use import(), or remove "type": "module" from /home/jenkins/workspace/s_npm_web-console-release_master/web-console/node_modules/node-fetch/package.json.
at Object.Module._extensions..js (internal/modules/cjs/loader.js:1102:13)
at Module.load (internal/modules/cjs/loader.js:950:32)
at Function.Module._load (internal/modules/cjs/loader.js:790:14)
at Module.require (internal/modules/cjs/loader.js:974:19)
at require (internal/modules/cjs/helpers.js:92:18)
at Object.<anonymous> (/home/jenkins/workspace/s_npm_web-console-release_master/web-console/clean_up_packages.js:1:16)
at Module._compile (internal/modules/cjs/loader.js:1085:14)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:1114:10)
at Module.load (internal/modules/cjs/loader.js:950:32)
at Function.Module._load (internal/modules/cjs/loader.js:790:14) {
code: 'ERR_REQUIRE_ESM'
}
``` | non_priority | web console clean up packages fails the following indicates an error in clean up packages js that gets triggered during the cleanup phase of the node clean up packages internal modules cjs loader js throw new err require esm filename parentpath packagejsonpath error must use import to load es module home jenkins workspace s npm web console release master web console node modules node fetch src index js require of es modules is not supported require of home jenkins workspace s npm web console release master web console node modules node fetch src index js from home jenkins workspace s npm web console release master web console clean up packages js is an es module file as it is a js file whose nearest parent package json contains type module which defines all js files in that package scope as es modules instead rename index js to end in cjs change the requiring code to use import or remove type module from home jenkins workspace s npm web console release master web console node modules node fetch package json at object module extensions js internal modules cjs loader js at module load internal modules cjs loader js at function module load internal modules cjs loader js at module require internal modules cjs loader js at require internal modules cjs helpers js at object home jenkins workspace s npm web console release master web console clean up packages js at module compile internal modules cjs loader js at object module extensions js internal modules cjs loader js at module load internal modules cjs loader js at function module load internal modules cjs loader js code err require esm | 0 |
62,373 | 14,656,488,769 | IssuesEvent | 2020-12-28 13:32:19 | fu1771695yongxie/front-end-interview-handbook | https://api.github.com/repos/fu1771695yongxie/front-end-interview-handbook | opened | CVE-2020-28275 (High) detected in cache-base-1.0.1.tgz | security vulnerability | ## CVE-2020-28275 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>cache-base-1.0.1.tgz</b></p></summary>
<p>Basic object cache with `get`, `set`, `del`, and `has` methods for node.js/javascript projects.</p>
<p>Library home page: <a href="https://registry.npmjs.org/cache-base/-/cache-base-1.0.1.tgz">https://registry.npmjs.org/cache-base/-/cache-base-1.0.1.tgz</a></p>
<p>Path to dependency file: front-end-interview-handbook/website/package.json</p>
<p>Path to vulnerable library: front-end-interview-handbook/website/node_modules/cache-base/package.json</p>
<p>
Dependency Hierarchy:
- core-2.0.0-alpha.70.tgz (Root Library)
- webpack-4.44.2.tgz
- micromatch-3.1.10.tgz
- snapdragon-0.8.2.tgz
- base-0.11.2.tgz
- :x: **cache-base-1.0.1.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/fu1771695yongxie/front-end-interview-handbook/commit/346d84adc6db12b6ea2ac724c8525293b8f9d439">346d84adc6db12b6ea2ac724c8525293b8f9d439</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
Prototype pollution vulnerability in 'cache-base' versions 0.7.0 through 4.0.0 allows attacker to cause a denial of service and may lead to remote code execution.
<p>Publish Date: 2020-11-07
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-28275>CVE-2020-28275</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | CVE-2020-28275 (High) detected in cache-base-1.0.1.tgz - ## CVE-2020-28275 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>cache-base-1.0.1.tgz</b></p></summary>
<p>Basic object cache with `get`, `set`, `del`, and `has` methods for node.js/javascript projects.</p>
<p>Library home page: <a href="https://registry.npmjs.org/cache-base/-/cache-base-1.0.1.tgz">https://registry.npmjs.org/cache-base/-/cache-base-1.0.1.tgz</a></p>
<p>Path to dependency file: front-end-interview-handbook/website/package.json</p>
<p>Path to vulnerable library: front-end-interview-handbook/website/node_modules/cache-base/package.json</p>
<p>
Dependency Hierarchy:
- core-2.0.0-alpha.70.tgz (Root Library)
- webpack-4.44.2.tgz
- micromatch-3.1.10.tgz
- snapdragon-0.8.2.tgz
- base-0.11.2.tgz
- :x: **cache-base-1.0.1.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/fu1771695yongxie/front-end-interview-handbook/commit/346d84adc6db12b6ea2ac724c8525293b8f9d439">346d84adc6db12b6ea2ac724c8525293b8f9d439</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
Prototype pollution vulnerability in 'cache-base' versions 0.7.0 through 4.0.0 allows attacker to cause a denial of service and may lead to remote code execution.
<p>Publish Date: 2020-11-07
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-28275>CVE-2020-28275</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_priority | cve high detected in cache base tgz cve high severity vulnerability vulnerable library cache base tgz basic object cache with get set del and has methods for node js javascript projects library home page a href path to dependency file front end interview handbook website package json path to vulnerable library front end interview handbook website node modules cache base package json dependency hierarchy core alpha tgz root library webpack tgz micromatch tgz snapdragon tgz base tgz x cache base tgz vulnerable library found in head commit a href found in base branch master vulnerability details prototype pollution vulnerability in cache base versions through allows attacker to cause a denial of service and may lead to remote code execution publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact none integrity impact none availability impact high for more information on scores click a href step up your open source security game with whitesource | 0 |
36,831 | 9,912,332,345 | IssuesEvent | 2019-06-28 08:45:09 | jOOQ/jOOQ | https://api.github.com/repos/jOOQ/jOOQ | opened | Change `@Support` annotation retention to source | C: Build C: Functionality E: All Editions P: Medium T: Enhancement T: Incompatible change | Currently, our `@Support` annotation has retention `RUNTIME` because we need it for our integration testing. The only other known use cases for this annotation are:
- The `jOOQ-checker` module, which uses annotation processing and/or compiler plugins to introspect this annotation (`SOURCE` retention should be sufficient)
- Javadoc (retention is irrelevant)
There are no known use cases by users for this annotations. Of course such use cases cannot be entirely ruled out, which is why we have to be careful about implementing this improvement.
`jooq.jar` file sizes:
- `Retention.RUNTIME`: 2 845 243 bytes
- `Retention.SOURCE`: 2 777 208 bytes
That's 68kb just for this annotation that hardly anyone uses. On some devices, this may make a difference. | 1.0 | Change `@Support` annotation retention to source - Currently, our `@Support` annotation has retention `RUNTIME` because we need it for our integration testing. The only other known use cases for this annotation are:
- The `jOOQ-checker` module, which uses annotation processing and/or compiler plugins to introspect this annotation (`SOURCE` retention should be sufficient)
- Javadoc (retention is irrelevant)
There are no known use cases by users for this annotations. Of course such use cases cannot be entirely ruled out, which is why we have to be careful about implementing this improvement.
`jooq.jar` file sizes:
- `Retention.RUNTIME`: 2 845 243 bytes
- `Retention.SOURCE`: 2 777 208 bytes
That's 68kb just for this annotation that hardly anyone uses. On some devices, this may make a difference. | non_priority | change support annotation retention to source currently our support annotation has retention runtime because we need it for our integration testing the only other known use cases for this annotation are the jooq checker module which uses annotation processing and or compiler plugins to introspect this annotation source retention should be sufficient javadoc retention is irrelevant there are no known use cases by users for this annotations of course such use cases cannot be entirely ruled out which is why we have to be careful about implementing this improvement jooq jar file sizes retention runtime bytes retention source bytes that s just for this annotation that hardly anyone uses on some devices this may make a difference | 0 |
121,903 | 12,136,898,428 | IssuesEvent | 2020-04-23 15:00:02 | strimzi/strimzi-kafka-operator | https://api.github.com/repos/strimzi/strimzi-kafka-operator | opened | [Doc] Consequences and migration path for enabling KafkaConnectors CRDs is missing | documentation | **Suggestion / Problem**
After enabling `KafkaConnectors` CRD through the annotation as described on the documentation
we lost all the configuration from the existing connectors configured through the REST API
Our expectation was that both could live together
**Documentation Link**
- https://strimzi.io/docs/master/#kafkaconnector_resources
- https://strimzi.io/docs/master/#con-creating-managing-connectors-str
- https://strimzi.io/docs/master/#proc-enabling-kafkaconnectors-deployment-configuration-kafka-connect
| 1.0 | [Doc] Consequences and migration path for enabling KafkaConnectors CRDs is missing - **Suggestion / Problem**
After enabling `KafkaConnectors` CRD through the annotation as described on the documentation
we lost all the configuration from the existing connectors configured through the REST API
Our expectation was that both could live together
**Documentation Link**
- https://strimzi.io/docs/master/#kafkaconnector_resources
- https://strimzi.io/docs/master/#con-creating-managing-connectors-str
- https://strimzi.io/docs/master/#proc-enabling-kafkaconnectors-deployment-configuration-kafka-connect
| non_priority | consequences and migration path for enabling kafkaconnectors crds is missing suggestion problem after enabling kafkaconnectors crd through the annotation as described on the documentation we lost all the configuration from the existing connectors configured through the rest api our expectation was that both could live together documentation link | 0 |
56,205 | 11,540,821,116 | IssuesEvent | 2020-02-18 01:38:18 | nmrih/source-game | https://api.github.com/repos/nmrih/source-game | closed | Zombie hands beat the air | Status: Reviewed Type: Code | Version: 1.0.9.5
What happens: zombies are suddenly stops and begin to beat the air with their hands for no reason.
When does it happen: sometimes.
Screenshots:
| 1.0 | Zombie hands beat the air - Version: 1.0.9.5
What happens: zombies are suddenly stops and begin to beat the air with their hands for no reason.
When does it happen: sometimes.
Screenshots:
| non_priority | zombie hands beat the air version what happens zombies are suddenly stops and begin to beat the air with their hands for no reason when does it happen sometimes screenshots | 0 |
108,670 | 11,597,919,966 | IssuesEvent | 2020-02-24 21:53:58 | tobiasanker/libKitsunemimiCommon | https://api.github.com/repos/tobiasanker/libKitsunemimiCommon | closed | add benchmark-tests | documentation feature / enhancement | similar to the unit-tests, some simple benchmark-tests should be added for performance-analytic | 1.0 | add benchmark-tests - similar to the unit-tests, some simple benchmark-tests should be added for performance-analytic | non_priority | add benchmark tests similar to the unit tests some simple benchmark tests should be added for performance analytic | 0 |
433,641 | 30,342,424,697 | IssuesEvent | 2023-07-11 13:31:59 | falcosecurity/falco-website | https://api.github.com/repos/falcosecurity/falco-website | closed | Create Audit Dashboards with Grafana Loki: Gather Audit Logs by using FluentBit | help wanted kind/content area/documentation lifecycle/rotten | <!-- Please only use this template for submitting content requests -->
/area documentation
**What would you like to be added**:
From the Slack conversation we had with @developer-guy and @leogr, dropping here, so we don't forget!
We thought that we can write a new blog post and demonstrate some threat/audit dashboards on the [Grafana Loki](https://grafana.com/oss/loki/). Here is a 30000-foot view of the rough architecture:
```
Kuberenetes Audit Logs -> FluentBit -> Falco (k8s-audit) -> Grafana Loki (Dashboards)
```
**Why is this needed**:
This post will be kind of the next part of [Detect Malicious Behaviour on Kubernetes API Server through gathering Audit Logs by using FluentBit - Part 2](https://falco.org/blog/detect-malicious-behaviour-on-kubernetes-api-server-through-gathering-audit-logs-by-using-fluentbit-part-2/) post.
| 1.0 | Create Audit Dashboards with Grafana Loki: Gather Audit Logs by using FluentBit - <!-- Please only use this template for submitting content requests -->
/area documentation
**What would you like to be added**:
From the Slack conversation we had with @developer-guy and @leogr, dropping here, so we don't forget!
We thought that we can write a new blog post and demonstrate some threat/audit dashboards on the [Grafana Loki](https://grafana.com/oss/loki/). Here is a 30000-foot view of the rough architecture:
```
Kuberenetes Audit Logs -> FluentBit -> Falco (k8s-audit) -> Grafana Loki (Dashboards)
```
**Why is this needed**:
This post will be kind of the next part of [Detect Malicious Behaviour on Kubernetes API Server through gathering Audit Logs by using FluentBit - Part 2](https://falco.org/blog/detect-malicious-behaviour-on-kubernetes-api-server-through-gathering-audit-logs-by-using-fluentbit-part-2/) post.
| non_priority | create audit dashboards with grafana loki gather audit logs by using fluentbit area documentation what would you like to be added from the slack conversation we had with developer guy and leogr dropping here so we don t forget we thought that we can write a new blog post and demonstrate some threat audit dashboards on the here is a foot view of the rough architecture kuberenetes audit logs fluentbit falco audit grafana loki dashboards why is this needed this post will be kind of the next part of post | 0 |
164,943 | 13,963,194,345 | IssuesEvent | 2020-10-25 13:08:25 | linrunner/TLP | https://api.github.com/repos/linrunner/TLP | closed | Default governor for intel_pstate driver changed in kernel 5.7 | defaults documentation change fix committed | The TLP config file, as well as the corresponding bit in the docs (https://github.com/linrunner/tlp-doc/blob/988e228b3e385a622ac0f0cb255b8d41ce2b6f93/settings/processor.rst) both claim that `powersave` is the default kernel governor when the `intel_pstate` driver is used:
https://github.com/linrunner/TLP/blob/bd068be60fe286e60b009a22e9cfaf4a43c9ed06/tlp.conf#L62-L74
However, as of Linux 5.7, this is no longer the case: https://www.phoronix.com/scan.php?page=news_item&px=Linux-5.7-Schedutil-P-State
The default governor now seems to be `schedutil`, with `intel_pstate` running in passive mode (https://www.kernel.org/doc/html/v5.8/admin-guide/pm/intel_pstate.html#passive-mode -- note that these docs are also outdated, apparently), as is the case on my fresh Arch install:
```
[micha@micha-laptop-hp1 ~]$ cat /sys/devices/system/cpu/intel_pstate/status
passive
[micha@micha-laptop-hp1 ~]$ cat /sys/devices/system/cpu/cpu*/cpufreq/scaling_governor
schedutil
schedutil
schedutil
schedutil
```
Note that the available governors also seem to have changed, with `powersave` getting ditched. Here is my `tlp-stat -p` output:
```
--- TLP 1.3.1 --------------------------------------------
+++ Processor
CPU model = Intel(R) Pentium(R) Silver N5000 CPU @ 1.10GHz
/sys/devices/system/cpu/cpu0/cpufreq/scaling_driver = intel_cpufreq
/sys/devices/system/cpu/cpu0/cpufreq/scaling_governor = schedutil
/sys/devices/system/cpu/cpu0/cpufreq/scaling_available_governors = performance schedutil
/sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq = 800000 [kHz]
/sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq = 2700000 [kHz]
[... repeated 4 times for 4 cores ...]
/sys/devices/system/cpu/intel_pstate/min_perf_pct = 29 [%]
/sys/devices/system/cpu/intel_pstate/max_perf_pct = 100 [%]
/sys/devices/system/cpu/intel_pstate/no_turbo = 0
/sys/devices/system/cpu/intel_pstate/turbo_pct = 81 [%]
/sys/devices/system/cpu/intel_pstate/num_pstates = 20
Intel EPB: unsupported CPU.
/sys/module/workqueue/parameters/power_efficient = Y
/proc/sys/kernel/nmi_watchdog = 0
```
I haven't been able to make sure these are all stock kernel changes, and not something introduced by Arch maintainers, but I believe that to be the case, as I doubt they would have played with these settings. I have not been able to find up-to-date documentation about this, as both the kernel documentation and Arch wiki appear to be outdated.
This is, of course, purely a documentation issue -- TLP doesn't change the governor by default; but it may cause confusion for users: "here it says `powersave` is the default and what I should be using, but `schedutil` is instead enabled on my system for some reason," or something like that.
I'm not making this a pull request because I'm not 100% on how it should be worded, whether there should be a note about it being changed in 5.7, etc. | 1.0 | Default governor for intel_pstate driver changed in kernel 5.7 - The TLP config file, as well as the corresponding bit in the docs (https://github.com/linrunner/tlp-doc/blob/988e228b3e385a622ac0f0cb255b8d41ce2b6f93/settings/processor.rst) both claim that `powersave` is the default kernel governor when the `intel_pstate` driver is used:
https://github.com/linrunner/TLP/blob/bd068be60fe286e60b009a22e9cfaf4a43c9ed06/tlp.conf#L62-L74
However, as of Linux 5.7, this is no longer the case: https://www.phoronix.com/scan.php?page=news_item&px=Linux-5.7-Schedutil-P-State
The default governor now seems to be `schedutil`, with `intel_pstate` running in passive mode (https://www.kernel.org/doc/html/v5.8/admin-guide/pm/intel_pstate.html#passive-mode -- note that these docs are also outdated, apparently), as is the case on my fresh Arch install:
```
[micha@micha-laptop-hp1 ~]$ cat /sys/devices/system/cpu/intel_pstate/status
passive
[micha@micha-laptop-hp1 ~]$ cat /sys/devices/system/cpu/cpu*/cpufreq/scaling_governor
schedutil
schedutil
schedutil
schedutil
```
Note that the available governors also seem to have changed, with `powersave` getting ditched. Here is my `tlp-stat -p` output:
```
--- TLP 1.3.1 --------------------------------------------
+++ Processor
CPU model = Intel(R) Pentium(R) Silver N5000 CPU @ 1.10GHz
/sys/devices/system/cpu/cpu0/cpufreq/scaling_driver = intel_cpufreq
/sys/devices/system/cpu/cpu0/cpufreq/scaling_governor = schedutil
/sys/devices/system/cpu/cpu0/cpufreq/scaling_available_governors = performance schedutil
/sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq = 800000 [kHz]
/sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq = 2700000 [kHz]
[... repeated 4 times for 4 cores ...]
/sys/devices/system/cpu/intel_pstate/min_perf_pct = 29 [%]
/sys/devices/system/cpu/intel_pstate/max_perf_pct = 100 [%]
/sys/devices/system/cpu/intel_pstate/no_turbo = 0
/sys/devices/system/cpu/intel_pstate/turbo_pct = 81 [%]
/sys/devices/system/cpu/intel_pstate/num_pstates = 20
Intel EPB: unsupported CPU.
/sys/module/workqueue/parameters/power_efficient = Y
/proc/sys/kernel/nmi_watchdog = 0
```
I haven't been able to make sure these are all stock kernel changes, and not something introduced by Arch maintainers, but I believe that to be the case, as I doubt they would have played with these settings. I have not been able to find up-to-date documentation about this, as both the kernel documentation and Arch wiki appear to be outdated.
This is, of course, purely a documentation issue -- TLP doesn't change the governor by default; but it may cause confusion for users: "here it says `powersave` is the default and what I should be using, but `schedutil` is instead enabled on my system for some reason," or something like that.
I'm not making this a pull request because I'm not 100% on how it should be worded, whether there should be a note about it being changed in 5.7, etc. | non_priority | default governor for intel pstate driver changed in kernel the tlp config file as well as the corresponding bit in the docs both claim that powersave is the default kernel governor when the intel pstate driver is used however as of linux this is no longer the case the default governor now seems to be schedutil with intel pstate running in passive mode note that these docs are also outdated apparently as is the case on my fresh arch install cat sys devices system cpu intel pstate status passive cat sys devices system cpu cpu cpufreq scaling governor schedutil schedutil schedutil schedutil note that the available governors also seem to have changed with powersave getting ditched here is my tlp stat p output tlp processor cpu model intel r pentium r silver cpu sys devices system cpu cpufreq scaling driver intel cpufreq sys devices system cpu cpufreq scaling governor schedutil sys devices system cpu cpufreq scaling available governors performance schedutil sys devices system cpu cpufreq scaling min freq sys devices system cpu cpufreq scaling max freq sys devices system cpu intel pstate min perf pct sys devices system cpu intel pstate max perf pct sys devices system cpu intel pstate no turbo sys devices system cpu intel pstate turbo pct sys devices system cpu intel pstate num pstates intel epb unsupported cpu sys module workqueue parameters power efficient y proc sys kernel nmi watchdog i haven t been able to make sure these are all stock kernel changes and not something introduced by arch maintainers but i believe that to be the case as i doubt they would have played with these settings i have not been able to find up to date documentation about this as both the kernel documentation and arch wiki appear to be outdated this is of course purely a documentation issue tlp doesn t change the governor by default but it may cause confusion for users here it says powersave is the default and what i should be using but schedutil is instead enabled on my system for some reason or something like that i m not making this a pull request because i m not on how it should be worded whether there should be a note about it being changed in etc | 0 |
15,302 | 19,529,318,548 | IssuesEvent | 2021-12-30 13:54:47 | qouteall/ImmersivePortalsMod | https://api.github.com/repos/qouteall/ImmersivePortalsMod | closed | Direct Incompatibility with Seasons for Fabric 1.17 | Mod Compatibility | 
Basically the story goes you load in just these two mods (Seasons for Fabric and Immersive Portals), go to a creative world, put down a portal and then /set time 672000t and the game will suddenly only be able to render about 2 chunks at a time and keep a stable framerate. Not sure who's end this is on but I figured I'd at least make you aware that modpack authors are having to make a tough choice. Love the work so much and thank you for doing it. | True | Direct Incompatibility with Seasons for Fabric 1.17 - 
Basically the story goes you load in just these two mods (Seasons for Fabric and Immersive Portals), go to a creative world, put down a portal and then /set time 672000t and the game will suddenly only be able to render about 2 chunks at a time and keep a stable framerate. Not sure who's end this is on but I figured I'd at least make you aware that modpack authors are having to make a tough choice. Love the work so much and thank you for doing it. | non_priority | direct incompatibility with seasons for fabric basically the story goes you load in just these two mods seasons for fabric and immersive portals go to a creative world put down a portal and then set time and the game will suddenly only be able to render about chunks at a time and keep a stable framerate not sure who s end this is on but i figured i d at least make you aware that modpack authors are having to make a tough choice love the work so much and thank you for doing it | 0 |
87,787 | 8,121,888,200 | IssuesEvent | 2018-08-16 09:39:57 | red/red | https://api.github.com/repos/red/red | closed | VID: system colors override in a panel | GUI status.built status.tested type.bug | An issue very similar to https://github.com/red/red/issues/3247
### Expected behavior
It **almost** works (except for some miscalculation of the width)
`view [text font-size 20 "now u see me now u dont"]`
### Actual behavior
now - in a panel!
`view [panel [text font-size 20 "now u see me now u dont"]]`
let's override the background:
`view [panel [text blue font-size 20 "now u see me now u dont"]]`
### Red and platform version
stable & nightly both
```
-----------RED & PLATFORM VERSION-----------
RED: [ branch: "master" tag: #v0.6.3 ahead: 750 date: 12-Jun-2018/15:07:14 commit: #e62b63d51cdc5d5f6033eb3fa366fd94be0b2deb ]
PLATFORM: [ name: "Windows 7 Service Pack 1" OS: 'Windows arch: 'x86-64 version: 6.1.1 build: 7601 ]
--------------------------------------------
``` | 1.0 | VID: system colors override in a panel - An issue very similar to https://github.com/red/red/issues/3247
### Expected behavior
It **almost** works (except for some miscalculation of the width)
`view [text font-size 20 "now u see me now u dont"]`
### Actual behavior
now - in a panel!
`view [panel [text font-size 20 "now u see me now u dont"]]`
let's override the background:
`view [panel [text blue font-size 20 "now u see me now u dont"]]`
### Red and platform version
stable & nightly both
```
-----------RED & PLATFORM VERSION-----------
RED: [ branch: "master" tag: #v0.6.3 ahead: 750 date: 12-Jun-2018/15:07:14 commit: #e62b63d51cdc5d5f6033eb3fa366fd94be0b2deb ]
PLATFORM: [ name: "Windows 7 Service Pack 1" OS: 'Windows arch: 'x86-64 version: 6.1.1 build: 7601 ]
--------------------------------------------
``` | non_priority | vid system colors override in a panel an issue very similar to expected behavior it almost works except for some miscalculation of the width view actual behavior now in a panel view let s override the background view red and platform version stable nightly both red platform version red platform | 0 |
116,576 | 11,936,031,994 | IssuesEvent | 2020-04-02 09:36:50 | dsii-2020-unirsm/archive | https://api.github.com/repos/dsii-2020-unirsm/archive | closed | Aggiungi preview output | documentation good first issue | https://github.com/dsii-2020-unirsm/archive/tree/master/GiuliaBollini/p5.js%20esercizi/Esercitazione_Noise
Ciao @GiuliaBollini puoi aggiungere una preview/immagine nel file README dell'output (per ogni esercizio che farai)? | 1.0 | Aggiungi preview output - https://github.com/dsii-2020-unirsm/archive/tree/master/GiuliaBollini/p5.js%20esercizi/Esercitazione_Noise
Ciao @GiuliaBollini puoi aggiungere una preview/immagine nel file README dell'output (per ogni esercizio che farai)? | non_priority | aggiungi preview output ciao giuliabollini puoi aggiungere una preview immagine nel file readme dell output per ogni esercizio che farai | 0 |
57,916 | 14,227,329,527 | IssuesEvent | 2020-11-18 01:01:47 | Mohib-hub/jwala | https://api.github.com/repos/Mohib-hub/jwala | opened | CVE-2020-26217 (Medium) detected in xstream-1.4.7.jar | security vulnerability | ## CVE-2020-26217 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>xstream-1.4.7.jar</b></p></summary>
<p>XStream is a serialization library from Java objects to XML and back.</p>
<p>Path to vulnerable library: jwala/jwala-services/src/test/resources/get-resource-mime-type-test-files/war/WEB-INF/lib/xstream-1.4.7.jar</p>
<p>
Dependency Hierarchy:
- :x: **xstream-1.4.7.jar** (Vulnerable Library)
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
XStream before version 1.4.14 is vulnerable to Remote Code Execution.The vulnerability may allow a remote attacker to run arbitrary shell commands only by manipulating the processed input stream. Only users who rely on blocklists are affected. Anyone using XStream's Security Framework allowlist is not affected. The linked advisory provides code workarounds for users who cannot upgrade. The issue is fixed in version 1.4.14.
<p>Publish Date: 2020-11-16
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-26217>CVE-2020-26217</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>6.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: High
- Privileges Required: Low
- User Interaction: Required
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: None
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/x-stream/xstream/security/advisories/GHSA-mw36-7c6c-q4q2">https://github.com/x-stream/xstream/security/advisories/GHSA-mw36-7c6c-q4q2</a></p>
<p>Release Date: 2020-11-16</p>
<p>Fix Resolution: com.thoughtworks.xstream:xstream:1.4.14</p>
</p>
</details>
<p></p>
***
:rescue_worker_helmet: Automatic Remediation is available for this issue
<!-- <REMEDIATE>{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"Java","groupId":"com.thoughtworks.xstream","packageName":"xstream","packageVersion":"1.4.7","isTransitiveDependency":false,"dependencyTree":"com.thoughtworks.xstream:xstream:1.4.7","isMinimumFixVersionAvailable":true,"minimumFixVersion":"com.thoughtworks.xstream:xstream:1.4.14"}],"vulnerabilityIdentifier":"CVE-2020-26217","vulnerabilityDetails":"XStream before version 1.4.14 is vulnerable to Remote Code Execution.The vulnerability may allow a remote attacker to run arbitrary shell commands only by manipulating the processed input stream. Only users who rely on blocklists are affected. Anyone using XStream\u0027s Security Framework allowlist is not affected. The linked advisory provides code workarounds for users who cannot upgrade. The issue is fixed in version 1.4.14.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-26217","cvss3Severity":"medium","cvss3Score":"6.5","cvss3Metrics":{"A":"None","AC":"High","PR":"Low","S":"Unchanged","C":"High","UI":"Required","AV":"Local","I":"None"},"extraData":{}}</REMEDIATE> --> | True | CVE-2020-26217 (Medium) detected in xstream-1.4.7.jar - ## CVE-2020-26217 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>xstream-1.4.7.jar</b></p></summary>
<p>XStream is a serialization library from Java objects to XML and back.</p>
<p>Path to vulnerable library: jwala/jwala-services/src/test/resources/get-resource-mime-type-test-files/war/WEB-INF/lib/xstream-1.4.7.jar</p>
<p>
Dependency Hierarchy:
- :x: **xstream-1.4.7.jar** (Vulnerable Library)
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
XStream before version 1.4.14 is vulnerable to Remote Code Execution.The vulnerability may allow a remote attacker to run arbitrary shell commands only by manipulating the processed input stream. Only users who rely on blocklists are affected. Anyone using XStream's Security Framework allowlist is not affected. The linked advisory provides code workarounds for users who cannot upgrade. The issue is fixed in version 1.4.14.
<p>Publish Date: 2020-11-16
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-26217>CVE-2020-26217</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>6.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: High
- Privileges Required: Low
- User Interaction: Required
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: None
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/x-stream/xstream/security/advisories/GHSA-mw36-7c6c-q4q2">https://github.com/x-stream/xstream/security/advisories/GHSA-mw36-7c6c-q4q2</a></p>
<p>Release Date: 2020-11-16</p>
<p>Fix Resolution: com.thoughtworks.xstream:xstream:1.4.14</p>
</p>
</details>
<p></p>
***
:rescue_worker_helmet: Automatic Remediation is available for this issue
<!-- <REMEDIATE>{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"Java","groupId":"com.thoughtworks.xstream","packageName":"xstream","packageVersion":"1.4.7","isTransitiveDependency":false,"dependencyTree":"com.thoughtworks.xstream:xstream:1.4.7","isMinimumFixVersionAvailable":true,"minimumFixVersion":"com.thoughtworks.xstream:xstream:1.4.14"}],"vulnerabilityIdentifier":"CVE-2020-26217","vulnerabilityDetails":"XStream before version 1.4.14 is vulnerable to Remote Code Execution.The vulnerability may allow a remote attacker to run arbitrary shell commands only by manipulating the processed input stream. Only users who rely on blocklists are affected. Anyone using XStream\u0027s Security Framework allowlist is not affected. The linked advisory provides code workarounds for users who cannot upgrade. The issue is fixed in version 1.4.14.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-26217","cvss3Severity":"medium","cvss3Score":"6.5","cvss3Metrics":{"A":"None","AC":"High","PR":"Low","S":"Unchanged","C":"High","UI":"Required","AV":"Local","I":"None"},"extraData":{}}</REMEDIATE> --> | non_priority | cve medium detected in xstream jar cve medium severity vulnerability vulnerable library xstream jar xstream is a serialization library from java objects to xml and back path to vulnerable library jwala jwala services src test resources get resource mime type test files war web inf lib xstream jar dependency hierarchy x xstream jar vulnerable library vulnerability details xstream before version is vulnerable to remote code execution the vulnerability may allow a remote attacker to run arbitrary shell commands only by manipulating the processed input stream only users who rely on blocklists are affected anyone using xstream s security framework allowlist is not affected the linked advisory provides code workarounds for users who cannot upgrade the issue is fixed in version publish date url a href cvss score details base score metrics exploitability metrics attack vector local attack complexity high privileges required low user interaction required scope unchanged impact metrics confidentiality impact high integrity impact none availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution com thoughtworks xstream xstream rescue worker helmet automatic remediation is available for this issue isopenpronvulnerability true ispackagebased true isdefaultbranch true packages vulnerabilityidentifier cve vulnerabilitydetails xstream before version is vulnerable to remote code execution the vulnerability may allow a remote attacker to run arbitrary shell commands only by manipulating the processed input stream only users who rely on blocklists are affected anyone using xstream security framework allowlist is not affected the linked advisory provides code workarounds for users who cannot upgrade the issue is fixed in version vulnerabilityurl | 0 |
392,113 | 26,925,098,333 | IssuesEvent | 2023-02-07 13:15:42 | Azure/Enterprise-Scale | https://api.github.com/repos/Azure/Enterprise-Scale | closed | Deploy to Azure Button Inconsistencies | documentation engineering | <p>On this page: https://github.com/Azure/Enterprise-Scale#deploying-enterprise-scale-architecture-in-your-own-environment </p>
<p>On the page, Trey Research Deploy to Azure button links to the following json:
https://portal.azure.com/#blade/Microsoft<em>Azure</em>CreateUIDef/CustomDeploymentBlade/uri/https%3A%2f%2fraw.githubusercontent.com%2fAzure%2fEnterprise-Scale%2fmain%2fdocs%2freference%2ftreyresearch%2farmTemplates%2fes-lite.json/createUIDefinitionUri/https%3A%2f%2fraw.githubusercontent.com%2fAzure%2fEnterprise-Scale%2fmain%2fdocs%2freference%2ftreyresearch%2farmTemplates%2fportal-es-lite.json </p>
<p>However, when you click on Detailed Description for Trey Research, the Deploy to Azure button links to the following json:
https://portal.azure.com/#blade/Microsoft<em>Azure</em>CreateUIDef/CustomDeploymentBlade/uri/https%3A%2f%2fraw.githubusercontent.com%2fAzure%2fEnterprise-Scale%2fmain%2feslzArm%2feslzArm.json/uiFormDefinitionUri/https%3A%2f%2fraw.githubusercontent.com%2fAzure%2fEnterprise-Scale%2fmain%2feslzArm%2feslz-portal.json </p>
<p>Contoso, AdventureWorks, and WingTip all point to the same json for the Deploy to Azure button in both the table and each of their Detailed Descriptions. But I think this may be intentional for these 3 to all share the same json. </p> | 1.0 | Deploy to Azure Button Inconsistencies - <p>On this page: https://github.com/Azure/Enterprise-Scale#deploying-enterprise-scale-architecture-in-your-own-environment </p>
<p>On the page, Trey Research Deploy to Azure button links to the following json:
https://portal.azure.com/#blade/Microsoft<em>Azure</em>CreateUIDef/CustomDeploymentBlade/uri/https%3A%2f%2fraw.githubusercontent.com%2fAzure%2fEnterprise-Scale%2fmain%2fdocs%2freference%2ftreyresearch%2farmTemplates%2fes-lite.json/createUIDefinitionUri/https%3A%2f%2fraw.githubusercontent.com%2fAzure%2fEnterprise-Scale%2fmain%2fdocs%2freference%2ftreyresearch%2farmTemplates%2fportal-es-lite.json </p>
<p>However, when you click on Detailed Description for Trey Research, the Deploy to Azure button links to the following json:
https://portal.azure.com/#blade/Microsoft<em>Azure</em>CreateUIDef/CustomDeploymentBlade/uri/https%3A%2f%2fraw.githubusercontent.com%2fAzure%2fEnterprise-Scale%2fmain%2feslzArm%2feslzArm.json/uiFormDefinitionUri/https%3A%2f%2fraw.githubusercontent.com%2fAzure%2fEnterprise-Scale%2fmain%2feslzArm%2feslz-portal.json </p>
<p>Contoso, AdventureWorks, and WingTip all point to the same json for the Deploy to Azure button in both the table and each of their Detailed Descriptions. But I think this may be intentional for these 3 to all share the same json. </p> | non_priority | deploy to azure button inconsistencies on this page on the page trey research deploy to azure button links to the following json however when you click on detailed description for trey research the deploy to azure button links to the following json contoso adventureworks and wingtip all point to the same json for the deploy to azure button in both the table and each of their detailed descriptions but i think this may be intentional for these to all share the same json | 0 |
105,233 | 9,039,914,167 | IssuesEvent | 2019-02-10 11:49:00 | RPi-Distro/python-gpiozero | https://api.github.com/repos/RPi-Distro/python-gpiozero | opened | Ensure every class's repr is tested | tests | It's possible for all tests to be passing but a device's repr fail, as I just found with `TonalBuzzer`.
I added a call to `repr(tb)` at the top of the first test for `TonalBuzzer` and since calling it raised an exception.
I know some tests actually inspect the contents of repr. Do we think this is necessary for all classes? Maybe. I think there should be at least a "test" that repr doesn't fall over.
@waveform80 @lurch thoughts? | 1.0 | Ensure every class's repr is tested - It's possible for all tests to be passing but a device's repr fail, as I just found with `TonalBuzzer`.
I added a call to `repr(tb)` at the top of the first test for `TonalBuzzer` and since calling it raised an exception.
I know some tests actually inspect the contents of repr. Do we think this is necessary for all classes? Maybe. I think there should be at least a "test" that repr doesn't fall over.
@waveform80 @lurch thoughts? | non_priority | ensure every class s repr is tested it s possible for all tests to be passing but a device s repr fail as i just found with tonalbuzzer i added a call to repr tb at the top of the first test for tonalbuzzer and since calling it raised an exception i know some tests actually inspect the contents of repr do we think this is necessary for all classes maybe i think there should be at least a test that repr doesn t fall over lurch thoughts | 0 |
3,510 | 4,364,718,348 | IssuesEvent | 2016-08-03 08:06:53 | oppia/oppia | https://api.github.com/repos/oppia/oppia | closed | Convert continuous computations to cron jobs, where appropriate. | loc: backend team: mapreduce infrastructure TODO: tech (breakdown) type: feature (minor) | We have some computations that run continuously but don't really need to, either because the data being computed doesn't get updated very often, or because having up-to-date data is not particularly necessary. This leads to unnecessary work, and increased frontend usage + costs.
The aim of this issue is therefore to turn the following these jobs into weekly crons:
- [x] SearchRanker
- [x] ExplorationRecommendationsAggregator
| 1.0 | Convert continuous computations to cron jobs, where appropriate. - We have some computations that run continuously but don't really need to, either because the data being computed doesn't get updated very often, or because having up-to-date data is not particularly necessary. This leads to unnecessary work, and increased frontend usage + costs.
The aim of this issue is therefore to turn the following these jobs into weekly crons:
- [x] SearchRanker
- [x] ExplorationRecommendationsAggregator
| non_priority | convert continuous computations to cron jobs where appropriate we have some computations that run continuously but don t really need to either because the data being computed doesn t get updated very often or because having up to date data is not particularly necessary this leads to unnecessary work and increased frontend usage costs the aim of this issue is therefore to turn the following these jobs into weekly crons searchranker explorationrecommendationsaggregator | 0 |
181,261 | 14,858,489,068 | IssuesEvent | 2021-01-18 16:52:58 | buckleyb98/Basic-JavaScript | https://api.github.com/repos/buckleyb98/Basic-JavaScript | opened | JS Comments | documentation | Comments are lines of code that JavaScript will intentionally ignore. Comments are a great way to leave notes to yourself and to other people who will later need to figure out what that code does.
// This is an in-line comment.
/* **This is a**
**multi-line comment** */ | 1.0 | JS Comments - Comments are lines of code that JavaScript will intentionally ignore. Comments are a great way to leave notes to yourself and to other people who will later need to figure out what that code does.
// This is an in-line comment.
/* **This is a**
**multi-line comment** */ | non_priority | js comments comments are lines of code that javascript will intentionally ignore comments are a great way to leave notes to yourself and to other people who will later need to figure out what that code does this is an in line comment this is a multi line comment | 0 |
9,089 | 8,515,984,262 | IssuesEvent | 2018-11-01 00:01:52 | MicrosoftDocs/azure-docs | https://api.github.com/repos/MicrosoftDocs/azure-docs | closed | Does not show how to upload voodoo to storage blob. | assigned-to-author doc-enhancement media-services/svc triaged | Does not show how to upload voodoo to storage blob.
I don't see how the input asset is populated
---
#### Document Details
⚠ *Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.*
* ID: 2bba6896-48dd-503f-1a49-98b79fa59fbb
* Version Independent ID: 670e2111-5369-0d52-66a6-cbf2e928f02a
* Content: [Upload, encode, and stream using Azure Media Services](https://docs.microsoft.com/en-us/azure/media-services/latest/stream-files-tutorial-with-rest)
* Content Source: [articles/media-services/latest/stream-files-tutorial-with-rest.md](https://github.com/Microsoft/azure-docs/blob/master/articles/media-services/latest/stream-files-tutorial-with-rest.md)
* Service: **media-services**
* GitHub Login: @Juliako
* Microsoft Alias: **juliako** | 1.0 | Does not show how to upload voodoo to storage blob. - Does not show how to upload voodoo to storage blob.
I don't see how the input asset is populated
---
#### Document Details
⚠ *Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.*
* ID: 2bba6896-48dd-503f-1a49-98b79fa59fbb
* Version Independent ID: 670e2111-5369-0d52-66a6-cbf2e928f02a
* Content: [Upload, encode, and stream using Azure Media Services](https://docs.microsoft.com/en-us/azure/media-services/latest/stream-files-tutorial-with-rest)
* Content Source: [articles/media-services/latest/stream-files-tutorial-with-rest.md](https://github.com/Microsoft/azure-docs/blob/master/articles/media-services/latest/stream-files-tutorial-with-rest.md)
* Service: **media-services**
* GitHub Login: @Juliako
* Microsoft Alias: **juliako** | non_priority | does not show how to upload voodoo to storage blob does not show how to upload voodoo to storage blob i don t see how the input asset is populated document details ⚠ do not edit this section it is required for docs microsoft com ➟ github issue linking id version independent id content content source service media services github login juliako microsoft alias juliako | 0 |
115,605 | 24,787,014,368 | IssuesEvent | 2022-10-24 10:39:06 | sast-automation-dev/easybuggy-43 | https://api.github.com/repos/sast-automation-dev/easybuggy-43 | opened | Code Security Report: 54 high severity findings, 108 total findings | code security findings | # Code Security Report
**Latest Scan:** 2022-10-24 10:38am
**Total Findings:** 108
**Tested Project Files:** 102
**Detected Programming Languages:** 1
<!-- SAST-MANUAL-SCAN-START -->
- [ ] Check this box to manually trigger a scan
<!-- SAST-MANUAL-SCAN-END -->
## Language: Java
| Severity | CWE | Vulnerability Type | Count |
|-|-|-|-|
|<img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High|[CWE-89](https://cwe.mitre.org/data/definitions/89.html)|SQL Injection|3|
|<img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High|[CWE-94](https://cwe.mitre.org/data/definitions/94.html)|Code Injection|1|
|<img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High|[CWE-22](https://cwe.mitre.org/data/definitions/22.html)|Path/Directory Traversal|9|
|<img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High|[CWE-73](https://cwe.mitre.org/data/definitions/73.html)|File Manipulation|8|
|<img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High|[CWE-79](https://cwe.mitre.org/data/definitions/79.html)|Cross-Site Scripting|32|
|<img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High|[CWE-918](https://cwe.mitre.org/data/definitions/918.html)|Server Side Request Forgery|1|
|<img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium|[CWE-338](https://cwe.mitre.org/data/definitions/338.html)|Weak Pseudo-Random|2|
|<img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium|[CWE-244](https://cwe.mitre.org/data/definitions/244.html)|Heap Inspection|5|
|<img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium|[CWE-501](https://cwe.mitre.org/data/definitions/501.html)|Trust Boundary Violation|5|
|<img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium|[CWE-209](https://cwe.mitre.org/data/definitions/209.html)|Error Messages Information Exposure|15|
|<img src='https://whitesource-resources.whitesourcesoftware.com/low_vul.png' width=19 height=20> Low|[CWE-601](https://cwe.mitre.org/data/definitions/601.html)|Unvalidated/Open Redirect|17|
|<img src='https://whitesource-resources.whitesourcesoftware.com/low_vul.png' width=19 height=20> Low|[CWE-117](https://cwe.mitre.org/data/definitions/117.html)|Log Forging|4|
|<img src='https://whitesource-resources.whitesourcesoftware.com/low_vul.png' width=19 height=20> Low|[CWE-113](https://cwe.mitre.org/data/definitions/113.html)|HTTP Header Injection|1|
|<img src='https://whitesource-resources.whitesourcesoftware.com/low_vul.png' width=19 height=20> Low|[CWE-20](https://cwe.mitre.org/data/definitions/20.html)|Session Poisoning|5|
### Details
> The below list presents the 20 most relevant findings that need your attention. To view information on the remaining findings, navigate to the [Mend SAST Application](https://dev.whitesourcesoftware.com/sast/#/scans/b535c649-9649-4dfe-8649-aee4d69e71d8/details).
<details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20>SQL Injection (CWE-89) : 3</summary>
#### Findings
<details>
<summary>vulnerabilities/SQLInjectionServlet.java:69</summary>
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/vulnerabilities/SQLInjectionServlet.java#L64-L69
<details>
<summary> Trace </summary>
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/vulnerabilities/SQLInjectionServlet.java#L28
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/vulnerabilities/SQLInjectionServlet.java#L45
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/vulnerabilities/SQLInjectionServlet.java#L60
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/vulnerabilities/SQLInjectionServlet.java#L69
</details>
</details>
<details>
<summary>vulnerabilities/SQLInjectionServlet.java:69</summary>
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/vulnerabilities/SQLInjectionServlet.java#L64-L69
<details>
<summary> Trace </summary>
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/vulnerabilities/SQLInjectionServlet.java#L28
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/vulnerabilities/SQLInjectionServlet.java#L45
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/vulnerabilities/SQLInjectionServlet.java#L60
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/vulnerabilities/SQLInjectionServlet.java#L69
</details>
</details>
<details>
<summary>vulnerabilities/SQLInjectionServlet.java:69</summary>
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/vulnerabilities/SQLInjectionServlet.java#L64-L69
<details>
<summary> Trace </summary>
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/vulnerabilities/SQLInjectionServlet.java#L28
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/vulnerabilities/SQLInjectionServlet.java#L39
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/vulnerabilities/SQLInjectionServlet.java#L45
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/vulnerabilities/SQLInjectionServlet.java#L60
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/vulnerabilities/SQLInjectionServlet.java#L69
</details>
</details>
</details>
<details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20>Code Injection (CWE-94) : 1</summary>
#### Findings
<details>
<summary>vulnerabilities/CodeInjectionServlet.java:65</summary>
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/vulnerabilities/CodeInjectionServlet.java#L60-L65
<details>
<summary> Trace </summary>
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/vulnerabilities/CodeInjectionServlet.java#L25
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/vulnerabilities/CodeInjectionServlet.java#L44
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/vulnerabilities/CodeInjectionServlet.java#L45
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/vulnerabilities/CodeInjectionServlet.java#L46
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/vulnerabilities/CodeInjectionServlet.java#L47
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/vulnerabilities/CodeInjectionServlet.java#L61
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/vulnerabilities/CodeInjectionServlet.java#L65
</details>
</details>
</details>
<details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20>Path/Directory Traversal (CWE-22) : 9</summary>
#### Findings
<details>
<summary>vulnerabilities/MailHeaderInjectionServlet.java:133</summary>
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/vulnerabilities/MailHeaderInjectionServlet.java#L128-L133
<details>
<summary> Trace </summary>
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/vulnerabilities/MailHeaderInjectionServlet.java#L125
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/core/utils/MultiPartFileUtils.java#L57
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/core/utils/MultiPartFileUtils.java#L59
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/vulnerabilities/MailHeaderInjectionServlet.java#L127
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/vulnerabilities/MailHeaderInjectionServlet.java#L133
</details>
</details>
<details>
<summary>vulnerabilities/NullByteInjectionServlet.java:46</summary>
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/vulnerabilities/NullByteInjectionServlet.java#L41-L46
<details>
<summary> Trace </summary>
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/vulnerabilities/NullByteInjectionServlet.java#L35
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/vulnerabilities/NullByteInjectionServlet.java#L40
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/vulnerabilities/NullByteInjectionServlet.java#L46
</details>
</details>
<details>
<summary>vulnerabilities/UnrestrictedSizeUploadServlet.java:84</summary>
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/vulnerabilities/UnrestrictedSizeUploadServlet.java#L79-L84
<details>
<summary> Trace </summary>
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/vulnerabilities/UnrestrictedSizeUploadServlet.java#L70
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/core/utils/MultiPartFileUtils.java#L57
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/core/utils/MultiPartFileUtils.java#L59
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/vulnerabilities/UnrestrictedSizeUploadServlet.java#L71
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/vulnerabilities/UnrestrictedSizeUploadServlet.java#L84
</details>
</details>
<details>
<summary>vulnerabilities/UnrestrictedExtensionUploadServlet.java:84</summary>
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/vulnerabilities/UnrestrictedExtensionUploadServlet.java#L79-L84
<details>
<summary> Trace </summary>
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/vulnerabilities/UnrestrictedExtensionUploadServlet.java#L69
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/core/utils/MultiPartFileUtils.java#L57
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/core/utils/MultiPartFileUtils.java#L59
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/vulnerabilities/UnrestrictedExtensionUploadServlet.java#L76
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/vulnerabilities/UnrestrictedExtensionUploadServlet.java#L84
</details>
</details>
<details>
<summary>vulnerabilities/UnrestrictedExtensionUploadServlet.java:110</summary>
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/vulnerabilities/UnrestrictedExtensionUploadServlet.java#L105-L110
<details>
<summary> Trace </summary>
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/vulnerabilities/UnrestrictedExtensionUploadServlet.java#L69
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/core/utils/MultiPartFileUtils.java#L57
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/core/utils/MultiPartFileUtils.java#L59
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/vulnerabilities/UnrestrictedExtensionUploadServlet.java#L76
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/vulnerabilities/UnrestrictedExtensionUploadServlet.java#L84
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/vulnerabilities/UnrestrictedExtensionUploadServlet.java#L106
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/vulnerabilities/UnrestrictedExtensionUploadServlet.java#L110
</details>
</details>
<details>
<summary>vulnerabilities/UnrestrictedExtensionUploadServlet.java:135</summary>
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/vulnerabilities/UnrestrictedExtensionUploadServlet.java#L130-L135
<details>
<summary> Trace </summary>
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/vulnerabilities/UnrestrictedExtensionUploadServlet.java#L69
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/core/utils/MultiPartFileUtils.java#L57
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/core/utils/MultiPartFileUtils.java#L59
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/vulnerabilities/UnrestrictedExtensionUploadServlet.java#L76
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/vulnerabilities/UnrestrictedExtensionUploadServlet.java#L84
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/vulnerabilities/UnrestrictedExtensionUploadServlet.java#L106
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/vulnerabilities/UnrestrictedExtensionUploadServlet.java#L135
</details>
</details>
<details>
<summary>vulnerabilities/UnrestrictedSizeUploadServlet.java:127</summary>
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/vulnerabilities/UnrestrictedSizeUploadServlet.java#L122-L127
<details>
<summary> Trace </summary>
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/vulnerabilities/UnrestrictedSizeUploadServlet.java#L70
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/core/utils/MultiPartFileUtils.java#L57
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/core/utils/MultiPartFileUtils.java#L59
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/vulnerabilities/UnrestrictedSizeUploadServlet.java#L71
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/vulnerabilities/UnrestrictedSizeUploadServlet.java#L84
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/vulnerabilities/UnrestrictedSizeUploadServlet.java#L111
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/vulnerabilities/UnrestrictedSizeUploadServlet.java#L127
</details>
</details>
<details>
<summary>vulnerabilities/XEEandXXEServlet.java:196</summary>
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/vulnerabilities/XEEandXXEServlet.java#L191-L196
<details>
<summary> Trace </summary>
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/vulnerabilities/XEEandXXEServlet.java#L141
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/core/utils/MultiPartFileUtils.java#L57
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/core/utils/MultiPartFileUtils.java#L59
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/vulnerabilities/XEEandXXEServlet.java#L148
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/vulnerabilities/XEEandXXEServlet.java#L161
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/vulnerabilities/XEEandXXEServlet.java#L192
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/vulnerabilities/XEEandXXEServlet.java#L196
</details>
</details>
<details>
<summary>vulnerabilities/UnrestrictedSizeUploadServlet.java:114</summary>
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/vulnerabilities/UnrestrictedSizeUploadServlet.java#L109-L114
<details>
<summary> Trace </summary>
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/vulnerabilities/UnrestrictedSizeUploadServlet.java#L70
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/core/utils/MultiPartFileUtils.java#L57
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/core/utils/MultiPartFileUtils.java#L59
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/vulnerabilities/UnrestrictedSizeUploadServlet.java#L71
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/vulnerabilities/UnrestrictedSizeUploadServlet.java#L84
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/vulnerabilities/UnrestrictedSizeUploadServlet.java#L111
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/vulnerabilities/UnrestrictedSizeUploadServlet.java#L114
</details>
</details>
</details>
<details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20>File Manipulation (CWE-73) : 7</summary>
#### Findings
<details>
<summary>vulnerabilities/MailHeaderInjectionServlet.java:142</summary>
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/vulnerabilities/MailHeaderInjectionServlet.java#L137-L142
<details>
<summary> Trace </summary>
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/vulnerabilities/MailHeaderInjectionServlet.java#L141
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/vulnerabilities/MailHeaderInjectionServlet.java#L142
</details>
</details>
<details>
<summary>utils/MultiPartFileUtils.java:38</summary>
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/core/utils/MultiPartFileUtils.java#L33-L38
<details>
<summary> Trace </summary>
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/core/utils/MultiPartFileUtils.java#L37
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/core/utils/MultiPartFileUtils.java#L38
</details>
</details>
<details>
<summary>utils/MultiPartFileUtils.java:38</summary>
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/core/utils/MultiPartFileUtils.java#L33-L38
<details>
<summary> Trace </summary>
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/core/utils/MultiPartFileUtils.java#L37
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/core/utils/MultiPartFileUtils.java#L38
</details>
</details>
<details>
<summary>utils/MultiPartFileUtils.java:38</summary>
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/core/utils/MultiPartFileUtils.java#L33-L38
<details>
<summary> Trace </summary>
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/core/utils/MultiPartFileUtils.java#L37
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/core/utils/MultiPartFileUtils.java#L38
</details>
</details>
<details>
<summary>utils/MultiPartFileUtils.java:38</summary>
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/core/utils/MultiPartFileUtils.java#L33-L38
<details>
<summary> Trace </summary>
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/core/utils/MultiPartFileUtils.java#L37
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/core/utils/MultiPartFileUtils.java#L38
</details>
</details>
<details>
<summary>utils/MultiPartFileUtils.java:33</summary>
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/core/utils/MultiPartFileUtils.java#L28-L33
<details>
<summary> Trace </summary>
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/vulnerabilities/XEEandXXEServlet.java#L141
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/core/utils/MultiPartFileUtils.java#L57
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/core/utils/MultiPartFileUtils.java#L59
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/vulnerabilities/XEEandXXEServlet.java#L148
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/vulnerabilities/XEEandXXEServlet.java#L157
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/core/utils/MultiPartFileUtils.java#L28
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/core/utils/MultiPartFileUtils.java#L33
</details>
</details>
<details>
<summary>utils/MultiPartFileUtils.java:33</summary>
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/core/utils/MultiPartFileUtils.java#L28-L33
<details>
<summary> Trace </summary>
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/vulnerabilities/UnrestrictedSizeUploadServlet.java#L70
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/core/utils/MultiPartFileUtils.java#L57
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/core/utils/MultiPartFileUtils.java#L59
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/vulnerabilities/UnrestrictedSizeUploadServlet.java#L71
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/vulnerabilities/UnrestrictedSizeUploadServlet.java#L80
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/core/utils/MultiPartFileUtils.java#L28
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/core/utils/MultiPartFileUtils.java#L33
</details>
</details>
</details>
| 1.0 | Code Security Report: 54 high severity findings, 108 total findings - # Code Security Report
**Latest Scan:** 2022-10-24 10:38am
**Total Findings:** 108
**Tested Project Files:** 102
**Detected Programming Languages:** 1
<!-- SAST-MANUAL-SCAN-START -->
- [ ] Check this box to manually trigger a scan
<!-- SAST-MANUAL-SCAN-END -->
## Language: Java
| Severity | CWE | Vulnerability Type | Count |
|-|-|-|-|
|<img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High|[CWE-89](https://cwe.mitre.org/data/definitions/89.html)|SQL Injection|3|
|<img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High|[CWE-94](https://cwe.mitre.org/data/definitions/94.html)|Code Injection|1|
|<img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High|[CWE-22](https://cwe.mitre.org/data/definitions/22.html)|Path/Directory Traversal|9|
|<img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High|[CWE-73](https://cwe.mitre.org/data/definitions/73.html)|File Manipulation|8|
|<img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High|[CWE-79](https://cwe.mitre.org/data/definitions/79.html)|Cross-Site Scripting|32|
|<img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High|[CWE-918](https://cwe.mitre.org/data/definitions/918.html)|Server Side Request Forgery|1|
|<img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium|[CWE-338](https://cwe.mitre.org/data/definitions/338.html)|Weak Pseudo-Random|2|
|<img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium|[CWE-244](https://cwe.mitre.org/data/definitions/244.html)|Heap Inspection|5|
|<img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium|[CWE-501](https://cwe.mitre.org/data/definitions/501.html)|Trust Boundary Violation|5|
|<img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium|[CWE-209](https://cwe.mitre.org/data/definitions/209.html)|Error Messages Information Exposure|15|
|<img src='https://whitesource-resources.whitesourcesoftware.com/low_vul.png' width=19 height=20> Low|[CWE-601](https://cwe.mitre.org/data/definitions/601.html)|Unvalidated/Open Redirect|17|
|<img src='https://whitesource-resources.whitesourcesoftware.com/low_vul.png' width=19 height=20> Low|[CWE-117](https://cwe.mitre.org/data/definitions/117.html)|Log Forging|4|
|<img src='https://whitesource-resources.whitesourcesoftware.com/low_vul.png' width=19 height=20> Low|[CWE-113](https://cwe.mitre.org/data/definitions/113.html)|HTTP Header Injection|1|
|<img src='https://whitesource-resources.whitesourcesoftware.com/low_vul.png' width=19 height=20> Low|[CWE-20](https://cwe.mitre.org/data/definitions/20.html)|Session Poisoning|5|
### Details
> The below list presents the 20 most relevant findings that need your attention. To view information on the remaining findings, navigate to the [Mend SAST Application](https://dev.whitesourcesoftware.com/sast/#/scans/b535c649-9649-4dfe-8649-aee4d69e71d8/details).
<details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20>SQL Injection (CWE-89) : 3</summary>
#### Findings
<details>
<summary>vulnerabilities/SQLInjectionServlet.java:69</summary>
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/vulnerabilities/SQLInjectionServlet.java#L64-L69
<details>
<summary> Trace </summary>
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/vulnerabilities/SQLInjectionServlet.java#L28
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/vulnerabilities/SQLInjectionServlet.java#L45
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/vulnerabilities/SQLInjectionServlet.java#L60
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/vulnerabilities/SQLInjectionServlet.java#L69
</details>
</details>
<details>
<summary>vulnerabilities/SQLInjectionServlet.java:69</summary>
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/vulnerabilities/SQLInjectionServlet.java#L64-L69
<details>
<summary> Trace </summary>
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/vulnerabilities/SQLInjectionServlet.java#L28
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/vulnerabilities/SQLInjectionServlet.java#L45
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/vulnerabilities/SQLInjectionServlet.java#L60
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/vulnerabilities/SQLInjectionServlet.java#L69
</details>
</details>
<details>
<summary>vulnerabilities/SQLInjectionServlet.java:69</summary>
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/vulnerabilities/SQLInjectionServlet.java#L64-L69
<details>
<summary> Trace </summary>
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/vulnerabilities/SQLInjectionServlet.java#L28
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/vulnerabilities/SQLInjectionServlet.java#L39
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/vulnerabilities/SQLInjectionServlet.java#L45
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/vulnerabilities/SQLInjectionServlet.java#L60
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/vulnerabilities/SQLInjectionServlet.java#L69
</details>
</details>
</details>
<details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20>Code Injection (CWE-94) : 1</summary>
#### Findings
<details>
<summary>vulnerabilities/CodeInjectionServlet.java:65</summary>
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/vulnerabilities/CodeInjectionServlet.java#L60-L65
<details>
<summary> Trace </summary>
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/vulnerabilities/CodeInjectionServlet.java#L25
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/vulnerabilities/CodeInjectionServlet.java#L44
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/vulnerabilities/CodeInjectionServlet.java#L45
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/vulnerabilities/CodeInjectionServlet.java#L46
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/vulnerabilities/CodeInjectionServlet.java#L47
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/vulnerabilities/CodeInjectionServlet.java#L61
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/vulnerabilities/CodeInjectionServlet.java#L65
</details>
</details>
</details>
<details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20>Path/Directory Traversal (CWE-22) : 9</summary>
#### Findings
<details>
<summary>vulnerabilities/MailHeaderInjectionServlet.java:133</summary>
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/vulnerabilities/MailHeaderInjectionServlet.java#L128-L133
<details>
<summary> Trace </summary>
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/vulnerabilities/MailHeaderInjectionServlet.java#L125
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/core/utils/MultiPartFileUtils.java#L57
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/core/utils/MultiPartFileUtils.java#L59
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/vulnerabilities/MailHeaderInjectionServlet.java#L127
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/vulnerabilities/MailHeaderInjectionServlet.java#L133
</details>
</details>
<details>
<summary>vulnerabilities/NullByteInjectionServlet.java:46</summary>
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/vulnerabilities/NullByteInjectionServlet.java#L41-L46
<details>
<summary> Trace </summary>
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/vulnerabilities/NullByteInjectionServlet.java#L35
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/vulnerabilities/NullByteInjectionServlet.java#L40
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/vulnerabilities/NullByteInjectionServlet.java#L46
</details>
</details>
<details>
<summary>vulnerabilities/UnrestrictedSizeUploadServlet.java:84</summary>
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/vulnerabilities/UnrestrictedSizeUploadServlet.java#L79-L84
<details>
<summary> Trace </summary>
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/vulnerabilities/UnrestrictedSizeUploadServlet.java#L70
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/core/utils/MultiPartFileUtils.java#L57
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/core/utils/MultiPartFileUtils.java#L59
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/vulnerabilities/UnrestrictedSizeUploadServlet.java#L71
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/vulnerabilities/UnrestrictedSizeUploadServlet.java#L84
</details>
</details>
<details>
<summary>vulnerabilities/UnrestrictedExtensionUploadServlet.java:84</summary>
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/vulnerabilities/UnrestrictedExtensionUploadServlet.java#L79-L84
<details>
<summary> Trace </summary>
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/vulnerabilities/UnrestrictedExtensionUploadServlet.java#L69
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/core/utils/MultiPartFileUtils.java#L57
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/core/utils/MultiPartFileUtils.java#L59
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/vulnerabilities/UnrestrictedExtensionUploadServlet.java#L76
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/vulnerabilities/UnrestrictedExtensionUploadServlet.java#L84
</details>
</details>
<details>
<summary>vulnerabilities/UnrestrictedExtensionUploadServlet.java:110</summary>
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/vulnerabilities/UnrestrictedExtensionUploadServlet.java#L105-L110
<details>
<summary> Trace </summary>
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/vulnerabilities/UnrestrictedExtensionUploadServlet.java#L69
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/core/utils/MultiPartFileUtils.java#L57
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/core/utils/MultiPartFileUtils.java#L59
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/vulnerabilities/UnrestrictedExtensionUploadServlet.java#L76
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/vulnerabilities/UnrestrictedExtensionUploadServlet.java#L84
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/vulnerabilities/UnrestrictedExtensionUploadServlet.java#L106
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/vulnerabilities/UnrestrictedExtensionUploadServlet.java#L110
</details>
</details>
<details>
<summary>vulnerabilities/UnrestrictedExtensionUploadServlet.java:135</summary>
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/vulnerabilities/UnrestrictedExtensionUploadServlet.java#L130-L135
<details>
<summary> Trace </summary>
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/vulnerabilities/UnrestrictedExtensionUploadServlet.java#L69
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/core/utils/MultiPartFileUtils.java#L57
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/core/utils/MultiPartFileUtils.java#L59
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/vulnerabilities/UnrestrictedExtensionUploadServlet.java#L76
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/vulnerabilities/UnrestrictedExtensionUploadServlet.java#L84
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/vulnerabilities/UnrestrictedExtensionUploadServlet.java#L106
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/vulnerabilities/UnrestrictedExtensionUploadServlet.java#L135
</details>
</details>
<details>
<summary>vulnerabilities/UnrestrictedSizeUploadServlet.java:127</summary>
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/vulnerabilities/UnrestrictedSizeUploadServlet.java#L122-L127
<details>
<summary> Trace </summary>
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/vulnerabilities/UnrestrictedSizeUploadServlet.java#L70
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/core/utils/MultiPartFileUtils.java#L57
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/core/utils/MultiPartFileUtils.java#L59
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/vulnerabilities/UnrestrictedSizeUploadServlet.java#L71
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/vulnerabilities/UnrestrictedSizeUploadServlet.java#L84
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/vulnerabilities/UnrestrictedSizeUploadServlet.java#L111
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/vulnerabilities/UnrestrictedSizeUploadServlet.java#L127
</details>
</details>
<details>
<summary>vulnerabilities/XEEandXXEServlet.java:196</summary>
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/vulnerabilities/XEEandXXEServlet.java#L191-L196
<details>
<summary> Trace </summary>
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/vulnerabilities/XEEandXXEServlet.java#L141
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/core/utils/MultiPartFileUtils.java#L57
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/core/utils/MultiPartFileUtils.java#L59
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/vulnerabilities/XEEandXXEServlet.java#L148
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/vulnerabilities/XEEandXXEServlet.java#L161
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/vulnerabilities/XEEandXXEServlet.java#L192
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/vulnerabilities/XEEandXXEServlet.java#L196
</details>
</details>
<details>
<summary>vulnerabilities/UnrestrictedSizeUploadServlet.java:114</summary>
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/vulnerabilities/UnrestrictedSizeUploadServlet.java#L109-L114
<details>
<summary> Trace </summary>
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/vulnerabilities/UnrestrictedSizeUploadServlet.java#L70
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/core/utils/MultiPartFileUtils.java#L57
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/core/utils/MultiPartFileUtils.java#L59
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/vulnerabilities/UnrestrictedSizeUploadServlet.java#L71
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/vulnerabilities/UnrestrictedSizeUploadServlet.java#L84
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/vulnerabilities/UnrestrictedSizeUploadServlet.java#L111
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/vulnerabilities/UnrestrictedSizeUploadServlet.java#L114
</details>
</details>
</details>
<details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20>File Manipulation (CWE-73) : 7</summary>
#### Findings
<details>
<summary>vulnerabilities/MailHeaderInjectionServlet.java:142</summary>
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/vulnerabilities/MailHeaderInjectionServlet.java#L137-L142
<details>
<summary> Trace </summary>
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/vulnerabilities/MailHeaderInjectionServlet.java#L141
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/vulnerabilities/MailHeaderInjectionServlet.java#L142
</details>
</details>
<details>
<summary>utils/MultiPartFileUtils.java:38</summary>
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/core/utils/MultiPartFileUtils.java#L33-L38
<details>
<summary> Trace </summary>
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/core/utils/MultiPartFileUtils.java#L37
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/core/utils/MultiPartFileUtils.java#L38
</details>
</details>
<details>
<summary>utils/MultiPartFileUtils.java:38</summary>
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/core/utils/MultiPartFileUtils.java#L33-L38
<details>
<summary> Trace </summary>
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/core/utils/MultiPartFileUtils.java#L37
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/core/utils/MultiPartFileUtils.java#L38
</details>
</details>
<details>
<summary>utils/MultiPartFileUtils.java:38</summary>
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/core/utils/MultiPartFileUtils.java#L33-L38
<details>
<summary> Trace </summary>
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/core/utils/MultiPartFileUtils.java#L37
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/core/utils/MultiPartFileUtils.java#L38
</details>
</details>
<details>
<summary>utils/MultiPartFileUtils.java:38</summary>
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/core/utils/MultiPartFileUtils.java#L33-L38
<details>
<summary> Trace </summary>
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/core/utils/MultiPartFileUtils.java#L37
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/core/utils/MultiPartFileUtils.java#L38
</details>
</details>
<details>
<summary>utils/MultiPartFileUtils.java:33</summary>
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/core/utils/MultiPartFileUtils.java#L28-L33
<details>
<summary> Trace </summary>
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/vulnerabilities/XEEandXXEServlet.java#L141
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/core/utils/MultiPartFileUtils.java#L57
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/core/utils/MultiPartFileUtils.java#L59
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/vulnerabilities/XEEandXXEServlet.java#L148
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/vulnerabilities/XEEandXXEServlet.java#L157
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/core/utils/MultiPartFileUtils.java#L28
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/core/utils/MultiPartFileUtils.java#L33
</details>
</details>
<details>
<summary>utils/MultiPartFileUtils.java:33</summary>
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/core/utils/MultiPartFileUtils.java#L28-L33
<details>
<summary> Trace </summary>
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/vulnerabilities/UnrestrictedSizeUploadServlet.java#L70
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/core/utils/MultiPartFileUtils.java#L57
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/core/utils/MultiPartFileUtils.java#L59
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/vulnerabilities/UnrestrictedSizeUploadServlet.java#L71
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/vulnerabilities/UnrestrictedSizeUploadServlet.java#L80
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/core/utils/MultiPartFileUtils.java#L28
https://github.com/sast-automation-dev/easybuggy-43/blob/64f051ba6413be82b57966efe14f592b4eaf0e2d/easybuggy-43/src/main/java/org/t246osslab/easybuggy/core/utils/MultiPartFileUtils.java#L33
</details>
</details>
</details>
| non_priority | code security report high severity findings total findings code security report latest scan total findings tested project files detected programming languages check this box to manually trigger a scan language java severity cwe vulnerability type count high injection high injection high traversal high manipulation high scripting high side request forgery medium pseudo random medium inspection medium boundary violation medium messages information exposure low redirect low forging low header injection low poisoning details the below list presents the most relevant findings that need your attention to view information on the remaining findings navigate to the sql injection cwe findings vulnerabilities sqlinjectionservlet java trace vulnerabilities sqlinjectionservlet java trace vulnerabilities sqlinjectionservlet java trace code injection cwe findings vulnerabilities codeinjectionservlet java trace path directory traversal cwe findings vulnerabilities mailheaderinjectionservlet java trace vulnerabilities nullbyteinjectionservlet java trace vulnerabilities unrestrictedsizeuploadservlet java trace vulnerabilities unrestrictedextensionuploadservlet java trace vulnerabilities unrestrictedextensionuploadservlet java trace vulnerabilities unrestrictedextensionuploadservlet java trace vulnerabilities unrestrictedsizeuploadservlet java trace vulnerabilities xeeandxxeservlet java trace vulnerabilities unrestrictedsizeuploadservlet java trace file manipulation cwe findings vulnerabilities mailheaderinjectionservlet java trace utils multipartfileutils java trace utils multipartfileutils java trace utils multipartfileutils java trace utils multipartfileutils java trace utils multipartfileutils java trace utils multipartfileutils java trace | 0 |
68,127 | 13,081,929,696 | IssuesEvent | 2020-08-01 12:47:59 | LambdaHack/LambdaHack | https://api.github.com/repos/LambdaHack/LambdaHack | closed | In F1 scenario screen, show game over message in gray if not yet seen | UI code smell easy good first issue help wanted self-contained | The check would be similar to the current check in case of victory messages (which should not be shown at all, if not seen in game, to avoid spoilers). | 1.0 | In F1 scenario screen, show game over message in gray if not yet seen - The check would be similar to the current check in case of victory messages (which should not be shown at all, if not seen in game, to avoid spoilers). | non_priority | in scenario screen show game over message in gray if not yet seen the check would be similar to the current check in case of victory messages which should not be shown at all if not seen in game to avoid spoilers | 0 |
258,816 | 22,349,933,702 | IssuesEvent | 2022-06-15 11:07:07 | lowRISC/opentitan | https://api.github.com/repos/lowRISC/opentitan | opened | csrng - fuse enable sw app read test | Type:Task IP:csrng Component:ChipLevelTest | # Verify the fuse input to CSRNG.
- Initialize the OTP with this fuse bit set to 1.
- Issue an instantiate command to request entropy.
- Verify that SW can read the internal states.
- Reset the chip and repeat the steps above, but this time, with OTP fuse bit set to 0.
- Verify that the SW reads back all zeros when reading the internal states. | 1.0 | csrng - fuse enable sw app read test - # Verify the fuse input to CSRNG.
- Initialize the OTP with this fuse bit set to 1.
- Issue an instantiate command to request entropy.
- Verify that SW can read the internal states.
- Reset the chip and repeat the steps above, but this time, with OTP fuse bit set to 0.
- Verify that the SW reads back all zeros when reading the internal states. | non_priority | csrng fuse enable sw app read test verify the fuse input to csrng initialize the otp with this fuse bit set to issue an instantiate command to request entropy verify that sw can read the internal states reset the chip and repeat the steps above but this time with otp fuse bit set to verify that the sw reads back all zeros when reading the internal states | 0 |
360,258 | 25,282,759,818 | IssuesEvent | 2022-11-16 16:54:00 | mandiant/VM-Packages | https://api.github.com/repos/mandiant/VM-Packages | closed | Document "Install from ZIP" and "Install Raw GitHub repo" | :page_facing_up: documentation :gem: enhancement | Document different between VM-Install-From-Zip and VM-Install-Raw-GitHub-Repo (also in the ISSUE template, or link to the added documentation). | 1.0 | Document "Install from ZIP" and "Install Raw GitHub repo" - Document different between VM-Install-From-Zip and VM-Install-Raw-GitHub-Repo (also in the ISSUE template, or link to the added documentation). | non_priority | document install from zip and install raw github repo document different between vm install from zip and vm install raw github repo also in the issue template or link to the added documentation | 0 |
63,397 | 17,620,311,124 | IssuesEvent | 2021-08-18 14:36:32 | jOOQ/jOOQ | https://api.github.com/repos/jOOQ/jOOQ | closed | Empty select() should not project asterisk if unknown table is used with leftSemiJoin() or leftAntiJoin() | T: Defect C: Functionality P: Medium R: Fixed E: All Editions | ### Expected behavior
When using a `leftSemiJoin` with an *unknown* table (and I guess - but did not verify - when using anti-joins as well) jOOQ throws away the column information that is used to map the result set into records. This leads to an ambiguous/invalid mapping since `into` falls back to trying to maching column and field names.
This is to be expected to happen for all join types that change the projection, since there is no way for jOOQ to know the columns. But semi- and anti-joins do not change the projection, therefore I believe this to be a bug.
```
YRecord wrong = ctx
.select()
.from(X)
.join(Y)
.on(Y.ID.eq(X.ID))
.leftSemiJoin(DSL.table(DSL.name("OTHER")))
.on(DSL.field(DSL.name("OTHER", "ID"), Long.class).eq(Y.VALUE))
.fetchOne()
.into(Y);
```
In this case the `.into(Y)` uses columns from `X` if they have the same name as columns in `Y`. (See MCVE)
```
YRecord right = ctx
.select()
.from(X)
.join(Y)
.on(Y.ID.eq(X.ID))
.where(DSL.exists(DSL.select(DSL.one()).from(DSL.table(DSL.name("OTHER"))).where(DSL.field(DSL.name("OTHER", "ID"), Long.class).eq(Y.VALUE))))
.fetchOne()
.into(Y);
```
This query works, because jOOQ keeps the information about which column is which.
### Steps to reproduce the problem
You can find an MCVE here: https://github.com/kaini/jOOQ-mcve-1
### Versions
- jOOQ: 3.15.1 Enterprise
- Java: 16
- Database (include vendor): Oracle 19c (also observed with DB2 LUW 11.5)
- OS: Linux
- JDBC Driver (include name if inofficial driver): `com.oracle.database.jdbc:ojdbc11:21.1.0.0` (also observed with `com.ibm.db2:jcc:11.5.5.0`)
| 1.0 | Empty select() should not project asterisk if unknown table is used with leftSemiJoin() or leftAntiJoin() - ### Expected behavior
When using a `leftSemiJoin` with an *unknown* table (and I guess - but did not verify - when using anti-joins as well) jOOQ throws away the column information that is used to map the result set into records. This leads to an ambiguous/invalid mapping since `into` falls back to trying to maching column and field names.
This is to be expected to happen for all join types that change the projection, since there is no way for jOOQ to know the columns. But semi- and anti-joins do not change the projection, therefore I believe this to be a bug.
```
YRecord wrong = ctx
.select()
.from(X)
.join(Y)
.on(Y.ID.eq(X.ID))
.leftSemiJoin(DSL.table(DSL.name("OTHER")))
.on(DSL.field(DSL.name("OTHER", "ID"), Long.class).eq(Y.VALUE))
.fetchOne()
.into(Y);
```
In this case the `.into(Y)` uses columns from `X` if they have the same name as columns in `Y`. (See MCVE)
```
YRecord right = ctx
.select()
.from(X)
.join(Y)
.on(Y.ID.eq(X.ID))
.where(DSL.exists(DSL.select(DSL.one()).from(DSL.table(DSL.name("OTHER"))).where(DSL.field(DSL.name("OTHER", "ID"), Long.class).eq(Y.VALUE))))
.fetchOne()
.into(Y);
```
This query works, because jOOQ keeps the information about which column is which.
### Steps to reproduce the problem
You can find an MCVE here: https://github.com/kaini/jOOQ-mcve-1
### Versions
- jOOQ: 3.15.1 Enterprise
- Java: 16
- Database (include vendor): Oracle 19c (also observed with DB2 LUW 11.5)
- OS: Linux
- JDBC Driver (include name if inofficial driver): `com.oracle.database.jdbc:ojdbc11:21.1.0.0` (also observed with `com.ibm.db2:jcc:11.5.5.0`)
| non_priority | empty select should not project asterisk if unknown table is used with leftsemijoin or leftantijoin expected behavior when using a leftsemijoin with an unknown table and i guess but did not verify when using anti joins as well jooq throws away the column information that is used to map the result set into records this leads to an ambiguous invalid mapping since into falls back to trying to maching column and field names this is to be expected to happen for all join types that change the projection since there is no way for jooq to know the columns but semi and anti joins do not change the projection therefore i believe this to be a bug yrecord wrong ctx select from x join y on y id eq x id leftsemijoin dsl table dsl name other on dsl field dsl name other id long class eq y value fetchone into y in this case the into y uses columns from x if they have the same name as columns in y see mcve yrecord right ctx select from x join y on y id eq x id where dsl exists dsl select dsl one from dsl table dsl name other where dsl field dsl name other id long class eq y value fetchone into y this query works because jooq keeps the information about which column is which steps to reproduce the problem you can find an mcve here versions jooq enterprise java database include vendor oracle also observed with luw os linux jdbc driver include name if inofficial driver com oracle database jdbc also observed with com ibm jcc | 0 |
12,067 | 4,351,126,988 | IssuesEvent | 2016-07-31 17:37:12 | drbenvincent/delay-discounting-analysis | https://api.github.com/repos/drbenvincent/delay-discounting-analysis | opened | create a CODA class | code clean up enhancement | Create a `CODA` class, which does much that same as this R package https://cran.r-project.org/web/packages/coda/coda.pdf
It will replace `mcmcContainer` (which had subclasses `STANmcmc` and `JAGSmcmc`)
- It has alternate constructors to build the object out of either a) samples and stats from matjags, or b) a StanFit object from MatlabStan
- It will provide get methods for both samples and mcmc chain statistics
- It will also have various plot methods | 1.0 | create a CODA class - Create a `CODA` class, which does much that same as this R package https://cran.r-project.org/web/packages/coda/coda.pdf
It will replace `mcmcContainer` (which had subclasses `STANmcmc` and `JAGSmcmc`)
- It has alternate constructors to build the object out of either a) samples and stats from matjags, or b) a StanFit object from MatlabStan
- It will provide get methods for both samples and mcmc chain statistics
- It will also have various plot methods | non_priority | create a coda class create a coda class which does much that same as this r package it will replace mcmccontainer which had subclasses stanmcmc and jagsmcmc it has alternate constructors to build the object out of either a samples and stats from matjags or b a stanfit object from matlabstan it will provide get methods for both samples and mcmc chain statistics it will also have various plot methods | 0 |
106,180 | 9,116,548,992 | IssuesEvent | 2019-02-22 09:19:52 | apeinot/incubator-nemo | https://api.github.com/repos/apeinot/incubator-nemo | opened | Run tests and save as log after the refactoring | Test-Log | The test output has to be saved in a log file after all refactoring changes are made. | 1.0 | Run tests and save as log after the refactoring - The test output has to be saved in a log file after all refactoring changes are made. | non_priority | run tests and save as log after the refactoring the test output has to be saved in a log file after all refactoring changes are made | 0 |
41,724 | 21,917,804,821 | IssuesEvent | 2022-05-22 04:52:03 | tailscale/tailscale | https://api.github.com/repos/tailscale/tailscale | closed | hello.ts.net is missing from my tailnet | L1 Very few P1 Nuisance T3 Performance/Debugging bug | ### What is the issue?
Noticed as part of #1233, but I'm splitting it out to it's own bug.
https://login.tailscale.com/admin/machines shows `hello`:
| MACHINE | IP | OS | LAST SEEN | |
| ------- | -- | -- | --------- | --- |
| hello (?) | 100.101.102.103 | Linux | Connected | ... |
| services@tailscale.com | | 1.18.2 | |
| [External] [No expiry] |
but I can not access it. It is not in the output of `tailscale status` of any of the nodes in my tailnet, nor is it in the kernel routing table for tailscale (`ip route ls table 52). If I try adding it manually and using `tailscale ping`, `ping` and `socat` to connect, then I see:
```
ping(100.101.102.103): no matching peer
Accept: ICMPv4{100.93.62.55:0 > 100.101.102.103:0} 84 ok out
Accept: ICMPv4{100.93.62.55:0 > 100.101.102.103:0} 84 ok out
Accept: ICMPv4{100.93.62.55:0 > 100.101.102.103:0} 84 ok out
Accept: TCP{100.93.62.55:60416 > 100.101.102.103:80} 60 ok out
open-conn-track: timeout opening (TCP 100.93.62.55:60416 => 100.101.102.103:80); no associated peer node
```
I have tried removing it, and re-adding it via https://login.tailscale.com/admin/invite/hello.ts.net, but that doesn't seem to change anything.
### Steps to reproduce
_No response_
### Are there any recent changes that introduced the issue?
_No response_
### OS
Linux
### OS version
Debian testing (bookworm), Raspberry Pi with Debian 11 (bullseye)
### Tailscale version
1.24.2
### Bug report
BUG-54838b594ceee0c96e93a9af1141b6ad0d8ac169018ee32176f2c9533b5be982-20220513174315Z-f1d276883ef9df8f | True | hello.ts.net is missing from my tailnet - ### What is the issue?
Noticed as part of #1233, but I'm splitting it out to it's own bug.
https://login.tailscale.com/admin/machines shows `hello`:
| MACHINE | IP | OS | LAST SEEN | |
| ------- | -- | -- | --------- | --- |
| hello (?) | 100.101.102.103 | Linux | Connected | ... |
| services@tailscale.com | | 1.18.2 | |
| [External] [No expiry] |
but I can not access it. It is not in the output of `tailscale status` of any of the nodes in my tailnet, nor is it in the kernel routing table for tailscale (`ip route ls table 52). If I try adding it manually and using `tailscale ping`, `ping` and `socat` to connect, then I see:
```
ping(100.101.102.103): no matching peer
Accept: ICMPv4{100.93.62.55:0 > 100.101.102.103:0} 84 ok out
Accept: ICMPv4{100.93.62.55:0 > 100.101.102.103:0} 84 ok out
Accept: ICMPv4{100.93.62.55:0 > 100.101.102.103:0} 84 ok out
Accept: TCP{100.93.62.55:60416 > 100.101.102.103:80} 60 ok out
open-conn-track: timeout opening (TCP 100.93.62.55:60416 => 100.101.102.103:80); no associated peer node
```
I have tried removing it, and re-adding it via https://login.tailscale.com/admin/invite/hello.ts.net, but that doesn't seem to change anything.
### Steps to reproduce
_No response_
### Are there any recent changes that introduced the issue?
_No response_
### OS
Linux
### OS version
Debian testing (bookworm), Raspberry Pi with Debian 11 (bullseye)
### Tailscale version
1.24.2
### Bug report
BUG-54838b594ceee0c96e93a9af1141b6ad0d8ac169018ee32176f2c9533b5be982-20220513174315Z-f1d276883ef9df8f | non_priority | hello ts net is missing from my tailnet what is the issue noticed as part of but i m splitting it out to it s own bug shows hello machine ip os last seen hello linux connected services tailscale com but i can not access it it is not in the output of tailscale status of any of the nodes in my tailnet nor is it in the kernel routing table for tailscale ip route ls table if i try adding it manually and using tailscale ping ping and socat to connect then i see ping no matching peer accept ok out accept ok out accept ok out accept tcp ok out open conn track timeout opening tcp no associated peer node i have tried removing it and re adding it via but that doesn t seem to change anything steps to reproduce no response are there any recent changes that introduced the issue no response os linux os version debian testing bookworm raspberry pi with debian bullseye tailscale version bug report bug | 0 |
359,543 | 25,243,661,001 | IssuesEvent | 2022-11-15 09:31:12 | rrousselGit/riverpod | https://api.github.com/repos/rrousselGit/riverpod | closed | Missing when `mounted` is to be used in case of `async` + provider rebuild | documentation needs triage | **Describe what scenario you think is uncovered by the existing examples/articles**
Documentation is missing examples/description/usecase when `mounted` is to be used in case of `async` + provider rebuild.
**Describe why existing examples/articles do not cover this case**
The entire riverpod.dev page is missing any example with `mounted` case.
**Additional context**
A StateNotifier might rebuild when watching other provider, e.g.:
```
final providerThatMayRebuild = StateProvider.family<SomeStateController, AsyncValue<SomeState>, int>((ref, id) {
final selectedFilter = ref.watch(filterProvider);
final repo = ref.watch(repositoryProvider);
return SomeStateController(
id: id,
filter: selectedFilter,
repository: repo,
);
});
class SomeStateController extends StateNotifier<AsyncValue<SomeState>> {
final int id;
final int filter;
final MyRepo repository;
SomeStateController(this.id, this.filter, this.repository)
: super(const AsyncLoading()) {
init();
}
Future<void> init() async {
state = const AsyncLoading();
final either = await repository.getSomething(id, filter);
either.fold(
(l) => state = const AsyncError('some error', StackTrace.empty),
(r) {
if (mounted) {
state = AsyncData(r); // without "if(mounted)" it was throwing Bad state exception here
}
},
);
}
}
```
As you can see, `providerThatMayRebuild` rebuild every time when `selectedFilter` changes.
If there is pending `await repository.getSomething(id, filter)` operation, and new `SomeStateController` instance is created, then the previous one is disposed, and `state = AsyncData(r)` will throw `Bad state` exception.
I've found in StackOverflow, that a solution for that is to check `if(mounted)` however Riverpod documentation is missing how to handle cases when StateNotifier is disposed while there's an async operation in progress.
**Alternatively** documentation is silent whether rebuild of `StateNotifier` is a good/bad practice at all, or how to do it to avoid `Bad state` exception | 1.0 | Missing when `mounted` is to be used in case of `async` + provider rebuild - **Describe what scenario you think is uncovered by the existing examples/articles**
Documentation is missing examples/description/usecase when `mounted` is to be used in case of `async` + provider rebuild.
**Describe why existing examples/articles do not cover this case**
The entire riverpod.dev page is missing any example with `mounted` case.
**Additional context**
A StateNotifier might rebuild when watching other provider, e.g.:
```
final providerThatMayRebuild = StateProvider.family<SomeStateController, AsyncValue<SomeState>, int>((ref, id) {
final selectedFilter = ref.watch(filterProvider);
final repo = ref.watch(repositoryProvider);
return SomeStateController(
id: id,
filter: selectedFilter,
repository: repo,
);
});
class SomeStateController extends StateNotifier<AsyncValue<SomeState>> {
final int id;
final int filter;
final MyRepo repository;
SomeStateController(this.id, this.filter, this.repository)
: super(const AsyncLoading()) {
init();
}
Future<void> init() async {
state = const AsyncLoading();
final either = await repository.getSomething(id, filter);
either.fold(
(l) => state = const AsyncError('some error', StackTrace.empty),
(r) {
if (mounted) {
state = AsyncData(r); // without "if(mounted)" it was throwing Bad state exception here
}
},
);
}
}
```
As you can see, `providerThatMayRebuild` rebuild every time when `selectedFilter` changes.
If there is pending `await repository.getSomething(id, filter)` operation, and new `SomeStateController` instance is created, then the previous one is disposed, and `state = AsyncData(r)` will throw `Bad state` exception.
I've found in StackOverflow, that a solution for that is to check `if(mounted)` however Riverpod documentation is missing how to handle cases when StateNotifier is disposed while there's an async operation in progress.
**Alternatively** documentation is silent whether rebuild of `StateNotifier` is a good/bad practice at all, or how to do it to avoid `Bad state` exception | non_priority | missing when mounted is to be used in case of async provider rebuild describe what scenario you think is uncovered by the existing examples articles documentation is missing examples description usecase when mounted is to be used in case of async provider rebuild describe why existing examples articles do not cover this case the entire riverpod dev page is missing any example with mounted case additional context a statenotifier might rebuild when watching other provider e g final providerthatmayrebuild stateprovider family int ref id final selectedfilter ref watch filterprovider final repo ref watch repositoryprovider return somestatecontroller id id filter selectedfilter repository repo class somestatecontroller extends statenotifier final int id final int filter final myrepo repository somestatecontroller this id this filter this repository super const asyncloading init future init async state const asyncloading final either await repository getsomething id filter either fold l state const asyncerror some error stacktrace empty r if mounted state asyncdata r without if mounted it was throwing bad state exception here as you can see providerthatmayrebuild rebuild every time when selectedfilter changes if there is pending await repository getsomething id filter operation and new somestatecontroller instance is created then the previous one is disposed and state asyncdata r will throw bad state exception i ve found in stackoverflow that a solution for that is to check if mounted however riverpod documentation is missing how to handle cases when statenotifier is disposed while there s an async operation in progress alternatively documentation is silent whether rebuild of statenotifier is a good bad practice at all or how to do it to avoid bad state exception | 0 |
244,630 | 26,441,523,786 | IssuesEvent | 2023-01-16 01:03:26 | phunware/maas-mapping-android-sdk | https://api.github.com/repos/phunware/maas-mapping-android-sdk | opened | CVE-2023-22899 (Medium) detected in zip4j-2.10.0.jar | security vulnerability | ## CVE-2023-22899 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>zip4j-2.10.0.jar</b></p></summary>
<p>Zip4j - A Java library for zip files and streams</p>
<p>Library home page: <a href="https://github.com/srikanth-lingala/zip4j">https://github.com/srikanth-lingala/zip4j</a></p>
<p>Path to dependency file: /Samples/kotlin/build.gradle</p>
<p>Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/net.lingala.zip4j/zip4j/2.10.0/c84585dda68de8f133a80e049fecacb64e48352a/zip4j-2.10.0.jar</p>
<p>
Dependency Hierarchy:
- mapping-core-4.3.0.pom (Root Library)
- :x: **zip4j-2.10.0.jar** (Vulnerable Library)
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
Zip4j through 2.11.2, as used in Threema and other products, does not always check the MAC when decrypting a ZIP archive.
<p>Publish Date: 2023-01-10
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2023-22899>CVE-2023-22899</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | CVE-2023-22899 (Medium) detected in zip4j-2.10.0.jar - ## CVE-2023-22899 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>zip4j-2.10.0.jar</b></p></summary>
<p>Zip4j - A Java library for zip files and streams</p>
<p>Library home page: <a href="https://github.com/srikanth-lingala/zip4j">https://github.com/srikanth-lingala/zip4j</a></p>
<p>Path to dependency file: /Samples/kotlin/build.gradle</p>
<p>Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/net.lingala.zip4j/zip4j/2.10.0/c84585dda68de8f133a80e049fecacb64e48352a/zip4j-2.10.0.jar</p>
<p>
Dependency Hierarchy:
- mapping-core-4.3.0.pom (Root Library)
- :x: **zip4j-2.10.0.jar** (Vulnerable Library)
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
Zip4j through 2.11.2, as used in Threema and other products, does not always check the MAC when decrypting a ZIP archive.
<p>Publish Date: 2023-01-10
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2023-22899>CVE-2023-22899</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_priority | cve medium detected in jar cve medium severity vulnerability vulnerable library jar a java library for zip files and streams library home page a href path to dependency file samples kotlin build gradle path to vulnerable library home wss scanner gradle caches modules files net lingala jar dependency hierarchy mapping core pom root library x jar vulnerable library found in base branch master vulnerability details through as used in threema and other products does not always check the mac when decrypting a zip archive publish date url a href cvss score details base score metrics exploitability metrics attack vector local attack complexity low privileges required none user interaction required scope unchanged impact metrics confidentiality impact none integrity impact none availability impact high for more information on scores click a href step up your open source security game with mend | 0 |
170,716 | 13,200,047,328 | IssuesEvent | 2020-08-14 07:25:18 | owncloud/core | https://api.github.com/repos/owncloud/core | opened | Reporting of unexpected failures when running just a single feature | QA-team dev:acceptance-tests | If a developer runs just a single feature, e.g. putting
```
make test-acceptance-api BEHAT_FEATURE=tests/acceptance/features/apiComments/editComments.feature
```
and `EXPECTED_FAILURES_FILE` is defined,
then `tests/acceptance/run.sh` does understand to check just the expected failures for the `apiComments` suite - that is a good start.
But it will also report about expected failures in other feature files like `apiComments/createComments.feature`
Make it smarter so that when running just a single feature, it only processes expected failure for the feature.
| 1.0 | Reporting of unexpected failures when running just a single feature - If a developer runs just a single feature, e.g. putting
```
make test-acceptance-api BEHAT_FEATURE=tests/acceptance/features/apiComments/editComments.feature
```
and `EXPECTED_FAILURES_FILE` is defined,
then `tests/acceptance/run.sh` does understand to check just the expected failures for the `apiComments` suite - that is a good start.
But it will also report about expected failures in other feature files like `apiComments/createComments.feature`
Make it smarter so that when running just a single feature, it only processes expected failure for the feature.
| non_priority | reporting of unexpected failures when running just a single feature if a developer runs just a single feature e g putting make test acceptance api behat feature tests acceptance features apicomments editcomments feature and expected failures file is defined then tests acceptance run sh does understand to check just the expected failures for the apicomments suite that is a good start but it will also report about expected failures in other feature files like apicomments createcomments feature make it smarter so that when running just a single feature it only processes expected failure for the feature | 0 |
49,884 | 10,429,253,231 | IssuesEvent | 2019-09-17 02:00:31 | iamwwc/blogsuepost | https://api.github.com/repos/iamwwc/blogsuepost | opened | 罗马数字求和-leetcode13 | Leetcode | 题目来源
https://leetcode.com/problems/roman-to-integer/
### 题目描述
给定一个字符串 s，计算得出 s 对应的值。
```
Input: "MCMXCIV"
Output: 1994
Explanation: M = 1000, CM = 900, XC = 90 and IV = 4.
```
### 题目分析
罗马数字计算最关键的是
1. 通常数字大小从左到右依次递减。
2. 如果 s[i] < s[i + 1]，说明这两个数字可以组合在一起，且值为 s[i + 1] - s[i]。
3. 如果 s[i] >= s[i + 1]，则值为 s[i]
### 实现
````java
class Solution {
public int romanToInt(String s) {
char[] arrs = s.toCharArray();
int result = 0;
HashMap<Character,Integer> map = new HashMap<>();
map.put('I',1);
map.put('V',5);
map.put('X',10);
map.put('L',50);
map.put('C',100);
map.put('D',500);
map.put('M',1000);
for(int i = 0 ; i < arrs.length; i ++) {
int current = map.get(arrs[i]);
// 这里需要处理数组索引溢出
// '1'表明溢出，我们用 0 代替
int next = map.getOrDefault(i < arrs.length - 1 ? arrs[i + 1] : '1',0);
if (next > current) {
result += next - current;
i += 1;
continue;
}
result += current;
}
return result;
}
}
``` | 1.0 | 罗马数字求和-leetcode13 - 题目来源
https://leetcode.com/problems/roman-to-integer/
### 题目描述
给定一个字符串 s，计算得出 s 对应的值。
```
Input: "MCMXCIV"
Output: 1994
Explanation: M = 1000, CM = 900, XC = 90 and IV = 4.
```
### 题目分析
罗马数字计算最关键的是
1. 通常数字大小从左到右依次递减。
2. 如果 s[i] < s[i + 1]，说明这两个数字可以组合在一起，且值为 s[i + 1] - s[i]。
3. 如果 s[i] >= s[i + 1]，则值为 s[i]
### 实现
````java
class Solution {
public int romanToInt(String s) {
char[] arrs = s.toCharArray();
int result = 0;
HashMap<Character,Integer> map = new HashMap<>();
map.put('I',1);
map.put('V',5);
map.put('X',10);
map.put('L',50);
map.put('C',100);
map.put('D',500);
map.put('M',1000);
for(int i = 0 ; i < arrs.length; i ++) {
int current = map.get(arrs[i]);
// 这里需要处理数组索引溢出
// '1'表明溢出，我们用 0 代替
int next = map.getOrDefault(i < arrs.length - 1 ? arrs[i + 1] : '1',0);
if (next > current) {
result += next - current;
i += 1;
continue;
}
result += current;
}
return result;
}
}
``` | non_priority | 罗马数字求和 题目来源 题目描述 给定一个字符串 s，计算得出 s 对应的值。 input mcmxciv output explanation m cm xc and iv 题目分析 罗马数字计算最关键的是 通常数字大小从左到右依次递减。 如果 s s ，说明这两个数字可以组合在一起，且值为 s s 。 如果 s s ，则值为 s 实现 java class solution public int romantoint string s char arrs s tochararray int result hashmap map new hashmap map put i map put v map put x map put l map put c map put d map put m for int i i arrs length i int current map get arrs 这里需要处理数组索引溢出 表明溢出，我们用 代替 int next map getordefault i arrs length arrs if next current result next current i continue result current return result | 0 |
82,359 | 10,245,208,682 | IssuesEvent | 2019-08-20 12:21:17 | navikt/Designsystemet | https://api.github.com/repos/navikt/Designsystemet | closed | Prinsipper for interne flater | design.nav.no | Publisere prinsipper for interne flater, kontakt Linda eller Elin innhold. | 1.0 | Prinsipper for interne flater - Publisere prinsipper for interne flater, kontakt Linda eller Elin innhold. | non_priority | prinsipper for interne flater publisere prinsipper for interne flater kontakt linda eller elin innhold | 0 |
4,324 | 16,082,979,383 | IssuesEvent | 2021-04-26 07:52:26 | rancher-sandbox/cOS-toolkit | https://api.github.com/repos/rancher-sandbox/cOS-toolkit | opened | Move away from Dockerhub in CI to prevent rate limit failures | automation | Too often the CI fails due to rate limit issues from Dockerhub.
We should move to a different registry without such problems. | 1.0 | Move away from Dockerhub in CI to prevent rate limit failures - Too often the CI fails due to rate limit issues from Dockerhub.
We should move to a different registry without such problems. | non_priority | move away from dockerhub in ci to prevent rate limit failures too often the ci fails due to rate limit issues from dockerhub we should move to a different registry without such problems | 0 |
60,677 | 6,712,599,774 | IssuesEvent | 2017-10-13 09:58:21 | vaadin/vaadin-tabs | https://api.github.com/repos/vaadin/vaadin-tabs | closed | focus-ring isn't set on tab after right-click on it and left-click outside | bug in review UX tests finding | 
Steps to reproduce:
- right-click on a tab
- left-click outside
- try to navigate with arrow keys, `focus-ring` won't be applied on a tab from the step 1 | 1.0 | focus-ring isn't set on tab after right-click on it and left-click outside - 
Steps to reproduce:
- right-click on a tab
- left-click outside
- try to navigate with arrow keys, `focus-ring` won't be applied on a tab from the step 1 | non_priority | focus ring isn t set on tab after right click on it and left click outside steps to reproduce right click on a tab left click outside try to navigate with arrow keys focus ring won t be applied on a tab from the step | 0 |
71,787 | 23,802,877,554 | IssuesEvent | 2022-09-03 15:24:05 | vector-im/element-web | https://api.github.com/repos/vector-im/element-web | opened | Desktop App icon no longer shows notification count on macOS | T-Defect | ### Steps to reproduce
Open Desktop on an account with unread notifs. Hit cmd-tab; observe that the app icon has no badge count. I'm pretty sure we used to have this, just as iMessage does (and used https://www.electronjs.org/docs/api/app#appsetbadgecountcount-linux-macos to set it)
<img width="277" alt="Screenshot 2022-09-03 at 16 22 33" src="https://user-images.githubusercontent.com/1294269/188277363-8c63083b-dd24-47d1-ae49-c60c1662d83f.png">
### Outcome
#### What did you expect?
Badge count
#### What happened instead?
No badge count
### Operating system
macOS
### Application version
nightly
### How did you install the app?
nightly
### Homeserver
matrix.org
### Will you send logs?
No | 1.0 | Desktop App icon no longer shows notification count on macOS - ### Steps to reproduce
Open Desktop on an account with unread notifs. Hit cmd-tab; observe that the app icon has no badge count. I'm pretty sure we used to have this, just as iMessage does (and used https://www.electronjs.org/docs/api/app#appsetbadgecountcount-linux-macos to set it)
<img width="277" alt="Screenshot 2022-09-03 at 16 22 33" src="https://user-images.githubusercontent.com/1294269/188277363-8c63083b-dd24-47d1-ae49-c60c1662d83f.png">
### Outcome
#### What did you expect?
Badge count
#### What happened instead?
No badge count
### Operating system
macOS
### Application version
nightly
### How did you install the app?
nightly
### Homeserver
matrix.org
### Will you send logs?
No | non_priority | desktop app icon no longer shows notification count on macos steps to reproduce open desktop on an account with unread notifs hit cmd tab observe that the app icon has no badge count i m pretty sure we used to have this just as imessage does and used to set it img width alt screenshot at src outcome what did you expect badge count what happened instead no badge count operating system macos application version nightly how did you install the app nightly homeserver matrix org will you send logs no | 0 |
70,661 | 15,097,259,616 | IssuesEvent | 2021-02-07 18:03:07 | rsoreq/jquery-ui | https://api.github.com/repos/rsoreq/jquery-ui | opened | CVE-2018-3721 (Medium) detected in lodash-3.10.1.tgz | security vulnerability | ## CVE-2018-3721 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>lodash-3.10.1.tgz</b></p></summary>
<p>The modern build of lodash modular utilities.</p>
<p>Library home page: <a href="https://registry.npmjs.org/lodash/-/lodash-3.10.1.tgz">https://registry.npmjs.org/lodash/-/lodash-3.10.1.tgz</a></p>
<p>Path to dependency file: jquery-ui/package.json</p>
<p>Path to vulnerable library: jquery-ui/node_modules/xmlbuilder/node_modules/lodash/package.json,jquery-ui/node_modules/babel-core/node_modules/lodash/package.json,jquery-ui/node_modules/grunt-jscs/node_modules/lodash/package.json,jquery-ui/node_modules/jsdoctypeparser/node_modules/lodash/package.json,jquery-ui/node_modules/babel-plugin-proto-to-assign/node_modules/lodash/package.json</p>
<p>
Dependency Hierarchy:
- grunt-jscs-2.1.0.tgz (Root Library)
- :x: **lodash-3.10.1.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/rsoreq/jquery-ui/commit/aea8374eb85e7dfb6eb6be79e0b0c6b96369785a">aea8374eb85e7dfb6eb6be79e0b0c6b96369785a</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
lodash node module before 4.17.5 suffers from a Modification of Assumed-Immutable Data (MAID) vulnerability via defaultsDeep, merge, and mergeWith functions, which allows a malicious user to modify the prototype of "Object" via __proto__, causing the addition or modification of an existing property that will exist on all objects.
<p>Publish Date: 2018-06-07
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-3721>CVE-2018-3721</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>6.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: High
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://nvd.nist.gov/vuln/detail/CVE-2018-3721">https://nvd.nist.gov/vuln/detail/CVE-2018-3721</a></p>
<p>Release Date: 2018-06-07</p>
<p>Fix Resolution: 4.17.5</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":false,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"lodash","packageVersion":"3.10.1","packageFilePaths":["/package.json"],"isTransitiveDependency":true,"dependencyTree":"grunt-jscs:2.1.0;lodash:3.10.1","isMinimumFixVersionAvailable":true,"minimumFixVersion":"4.17.5"}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2018-3721","vulnerabilityDetails":"lodash node module before 4.17.5 suffers from a Modification of Assumed-Immutable Data (MAID) vulnerability via defaultsDeep, merge, and mergeWith functions, which allows a malicious user to modify the prototype of \"Object\" via __proto__, causing the addition or modification of an existing property that will exist on all objects.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-3721","cvss3Severity":"medium","cvss3Score":"6.5","cvss3Metrics":{"A":"None","AC":"Low","PR":"Low","S":"Unchanged","C":"None","UI":"None","AV":"Network","I":"High"},"extraData":{}}</REMEDIATE> --> | True | CVE-2018-3721 (Medium) detected in lodash-3.10.1.tgz - ## CVE-2018-3721 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>lodash-3.10.1.tgz</b></p></summary>
<p>The modern build of lodash modular utilities.</p>
<p>Library home page: <a href="https://registry.npmjs.org/lodash/-/lodash-3.10.1.tgz">https://registry.npmjs.org/lodash/-/lodash-3.10.1.tgz</a></p>
<p>Path to dependency file: jquery-ui/package.json</p>
<p>Path to vulnerable library: jquery-ui/node_modules/xmlbuilder/node_modules/lodash/package.json,jquery-ui/node_modules/babel-core/node_modules/lodash/package.json,jquery-ui/node_modules/grunt-jscs/node_modules/lodash/package.json,jquery-ui/node_modules/jsdoctypeparser/node_modules/lodash/package.json,jquery-ui/node_modules/babel-plugin-proto-to-assign/node_modules/lodash/package.json</p>
<p>
Dependency Hierarchy:
- grunt-jscs-2.1.0.tgz (Root Library)
- :x: **lodash-3.10.1.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/rsoreq/jquery-ui/commit/aea8374eb85e7dfb6eb6be79e0b0c6b96369785a">aea8374eb85e7dfb6eb6be79e0b0c6b96369785a</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
lodash node module before 4.17.5 suffers from a Modification of Assumed-Immutable Data (MAID) vulnerability via defaultsDeep, merge, and mergeWith functions, which allows a malicious user to modify the prototype of "Object" via __proto__, causing the addition or modification of an existing property that will exist on all objects.
<p>Publish Date: 2018-06-07
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-3721>CVE-2018-3721</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>6.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: High
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://nvd.nist.gov/vuln/detail/CVE-2018-3721">https://nvd.nist.gov/vuln/detail/CVE-2018-3721</a></p>
<p>Release Date: 2018-06-07</p>
<p>Fix Resolution: 4.17.5</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":false,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"lodash","packageVersion":"3.10.1","packageFilePaths":["/package.json"],"isTransitiveDependency":true,"dependencyTree":"grunt-jscs:2.1.0;lodash:3.10.1","isMinimumFixVersionAvailable":true,"minimumFixVersion":"4.17.5"}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2018-3721","vulnerabilityDetails":"lodash node module before 4.17.5 suffers from a Modification of Assumed-Immutable Data (MAID) vulnerability via defaultsDeep, merge, and mergeWith functions, which allows a malicious user to modify the prototype of \"Object\" via __proto__, causing the addition or modification of an existing property that will exist on all objects.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-3721","cvss3Severity":"medium","cvss3Score":"6.5","cvss3Metrics":{"A":"None","AC":"Low","PR":"Low","S":"Unchanged","C":"None","UI":"None","AV":"Network","I":"High"},"extraData":{}}</REMEDIATE> --> | non_priority | cve medium detected in lodash tgz cve medium severity vulnerability vulnerable library lodash tgz the modern build of lodash modular utilities library home page a href path to dependency file jquery ui package json path to vulnerable library jquery ui node modules xmlbuilder node modules lodash package json jquery ui node modules babel core node modules lodash package json jquery ui node modules grunt jscs node modules lodash package json jquery ui node modules jsdoctypeparser node modules lodash package json jquery ui node modules babel plugin proto to assign node modules lodash package json dependency hierarchy grunt jscs tgz root library x lodash tgz vulnerable library found in head commit a href found in base branch master vulnerability details lodash node module before suffers from a modification of assumed immutable data maid vulnerability via defaultsdeep merge and mergewith functions which allows a malicious user to modify the prototype of object via proto causing the addition or modification of an existing property that will exist on all objects publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required low user interaction none scope unchanged impact metrics confidentiality impact none integrity impact high availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution isopenpronvulnerability false ispackagebased true isdefaultbranch true packages istransitivedependency true dependencytree grunt jscs lodash isminimumfixversionavailable true minimumfixversion basebranches vulnerabilityidentifier cve vulnerabilitydetails lodash node module before suffers from a modification of assumed immutable data maid vulnerability via defaultsdeep merge and mergewith functions which allows a malicious user to modify the prototype of object via proto causing the addition or modification of an existing property that will exist on all objects vulnerabilityurl | 0 |
74,684 | 25,258,045,868 | IssuesEvent | 2022-11-15 19:57:20 | department-of-veterans-affairs/va.gov-cms | https://api.github.com/repos/department-of-veterans-affairs/va.gov-cms | closed | Linky issues | Defect Needs refining ⭐️ Sitewide CMS | ## Describe the defect
When testing PHP 8.1, it does not seem as though Linky is working as it should. Adding new links within nodes is not creating new Managed links and when I view the links within the Source view I see the true end destination, rather than a Linky reference.
## To Reproduce
Steps to reproduce the behavior:
1. Go to [Managed Links](https://vacms-10870-upgrade-to-php81-rh7pjindaxvyxvr35alvilr3mqpgaoko.ci.cms.va.gov/admin/content/linky)
2. In the **Title** field, search for a a term that probably does not already have an existing reference, perhaps "Shenanigans". Confirm that Linky does not already have a reference for your term.
3. Go to any node and create a new link with your term (i.e. Shenanigans) as the link text
4. Go back to Managed links and search for your term again
5. Confirm Linky still does not have a reference for this term
Second behavior:
1. Go to the node with the new link you just created above, view the source code of the rich text editor.
2. Confirm that the link is displayed as the end destination instead of the Linky reference
## AC / Expected behavior
- [ ] Investigate/Resolve errors
## Screenshots
### CMS Team
Please check the team(s) that will do this work.
- [ ] `Program`
- [ ] `Platform CMS Team`
- [ ] `Sitewide Crew`
- [x] `⭐️ Sitewide CMS`
- [ ] `⭐️ Public Websites`
- [ ] `⭐️ Facilities`
- [ ] `⭐️ User support`
| 1.0 | Linky issues - ## Describe the defect
When testing PHP 8.1, it does not seem as though Linky is working as it should. Adding new links within nodes is not creating new Managed links and when I view the links within the Source view I see the true end destination, rather than a Linky reference.
## To Reproduce
Steps to reproduce the behavior:
1. Go to [Managed Links](https://vacms-10870-upgrade-to-php81-rh7pjindaxvyxvr35alvilr3mqpgaoko.ci.cms.va.gov/admin/content/linky)
2. In the **Title** field, search for a a term that probably does not already have an existing reference, perhaps "Shenanigans". Confirm that Linky does not already have a reference for your term.
3. Go to any node and create a new link with your term (i.e. Shenanigans) as the link text
4. Go back to Managed links and search for your term again
5. Confirm Linky still does not have a reference for this term
Second behavior:
1. Go to the node with the new link you just created above, view the source code of the rich text editor.
2. Confirm that the link is displayed as the end destination instead of the Linky reference
## AC / Expected behavior
- [ ] Investigate/Resolve errors
## Screenshots
### CMS Team
Please check the team(s) that will do this work.
- [ ] `Program`
- [ ] `Platform CMS Team`
- [ ] `Sitewide Crew`
- [x] `⭐️ Sitewide CMS`
- [ ] `⭐️ Public Websites`
- [ ] `⭐️ Facilities`
- [ ] `⭐️ User support`
| non_priority | linky issues describe the defect when testing php it does not seem as though linky is working as it should adding new links within nodes is not creating new managed links and when i view the links within the source view i see the true end destination rather than a linky reference to reproduce steps to reproduce the behavior go to in the title field search for a a term that probably does not already have an existing reference perhaps shenanigans confirm that linky does not already have a reference for your term go to any node and create a new link with your term i e shenanigans as the link text go back to managed links and search for your term again confirm linky still does not have a reference for this term second behavior go to the node with the new link you just created above view the source code of the rich text editor confirm that the link is displayed as the end destination instead of the linky reference ac expected behavior investigate resolve errors screenshots cms team please check the team s that will do this work program platform cms team sitewide crew ⭐️ sitewide cms ⭐️ public websites ⭐️ facilities ⭐️ user support | 0 |
77,981 | 22,062,382,786 | IssuesEvent | 2022-05-30 19:57:38 | NixOS/nixpkgs | https://api.github.com/repos/NixOS/nixpkgs | closed | symbola fails to unpack | 0.kind: build failure | I'm not sure if the remote file or [fetchzip changed](https://github.com/NixOS/nixpkgs/pull/173430), but something seems to have broken recently...
### Steps To Reproduce
Steps to reproduce the behavior:
1. build *symbola*
### Build log
```
builder for '/nix/store/10cny769wbnnavab5hh11qllgq0bvk3y-symbola-13.00.drv' failed with exit code 1; last 8 log lines:
trying https://dn-works.com/wp-content/uploads/2020/UFAS-Fonts/Symbola.zip
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 3581k 100 3581k 0 0 691k 0 0:00:05 0:00:05 --:--:-- 812k
unpacking source archive /build/Symbola.zip
error: zip file must contain a single file or directory.
hint: Pass stripRoot=false; to fetchzip to assume flat list of files.
```
### Additional context
This also seems to be out of date since there's a version 14, but it's [uploaded as a pdf attachment rather than a zip???](https://dn-works.com/wp-content/uploads/2021/UFAS121921/Symbola.pdf)
### Notify maintainers
cc @marsam
### Metadata
22aa8e5c7a19a9e74af9f223b0e033341629d92d | 1.0 | symbola fails to unpack - I'm not sure if the remote file or [fetchzip changed](https://github.com/NixOS/nixpkgs/pull/173430), but something seems to have broken recently...
### Steps To Reproduce
Steps to reproduce the behavior:
1. build *symbola*
### Build log
```
builder for '/nix/store/10cny769wbnnavab5hh11qllgq0bvk3y-symbola-13.00.drv' failed with exit code 1; last 8 log lines:
trying https://dn-works.com/wp-content/uploads/2020/UFAS-Fonts/Symbola.zip
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 3581k 100 3581k 0 0 691k 0 0:00:05 0:00:05 --:--:-- 812k
unpacking source archive /build/Symbola.zip
error: zip file must contain a single file or directory.
hint: Pass stripRoot=false; to fetchzip to assume flat list of files.
```
### Additional context
This also seems to be out of date since there's a version 14, but it's [uploaded as a pdf attachment rather than a zip???](https://dn-works.com/wp-content/uploads/2021/UFAS121921/Symbola.pdf)
### Notify maintainers
cc @marsam
### Metadata
22aa8e5c7a19a9e74af9f223b0e033341629d92d | non_priority | symbola fails to unpack i m not sure if the remote file or but something seems to have broken recently steps to reproduce steps to reproduce the behavior build symbola build log builder for nix store symbola drv failed with exit code last log lines trying total received xferd average speed time time time current dload upload total spent left speed unpacking source archive build symbola zip error zip file must contain a single file or directory hint pass striproot false to fetchzip to assume flat list of files additional context this also seems to be out of date since there s a version but it s notify maintainers cc marsam metadata | 0 |
432,876 | 30,297,558,424 | IssuesEvent | 2023-07-10 01:12:39 | RE-M4/PV-Final-2023 | https://api.github.com/repos/RE-M4/PV-Final-2023 | closed | Agregar documentación a los archivos de la capa "service" de testimonio | documentation | -Se debe agregar documentación a todos los métodos de la lógica de negocio, además de eliminar líneas de código innecesarias de haberlas. | 1.0 | Agregar documentación a los archivos de la capa "service" de testimonio - -Se debe agregar documentación a todos los métodos de la lógica de negocio, además de eliminar líneas de código innecesarias de haberlas. | non_priority | agregar documentación a los archivos de la capa service de testimonio se debe agregar documentación a todos los métodos de la lógica de negocio además de eliminar líneas de código innecesarias de haberlas | 0 |
26,053 | 11,257,763,864 | IssuesEvent | 2020-01-13 01:00:56 | LevyForchh/Argus | https://api.github.com/repos/LevyForchh/Argus | opened | WS-2016-7071 (High) detected in hadoop-common-2.7.4.jar | security vulnerability | ## WS-2016-7071 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>hadoop-common-2.7.4.jar</b></p></summary>
<p>Apache Hadoop Common</p>
<p>Path to dependency file: /Argus/ArgusWebServices/pom.xml</p>
<p>Path to vulnerable library: /root/.m2/repository/org/apache/hadoop/hadoop-common/2.7.4/hadoop-common-2.7.4.jar,/root/.m2/repository/org/apache/hadoop/hadoop-common/2.7.4/hadoop-common-2.7.4.jar,/root/.m2/repository/org/apache/hadoop/hadoop-common/2.7.4/hadoop-common-2.7.4.jar</p>
<p>
Dependency Hierarchy:
- hbase-client-1.4.2.jar (Root Library)
- :x: **hadoop-common-2.7.4.jar** (Vulnerable Library)
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
Apache Hadoop versions 2.7.2 to 2.7.7 are vulnerable to Cross-Site Request Forgery that targets HTTP requests to “NameNode” and “DataNode”.
<p>Publish Date: 2020-01-08
<p>URL: <a href=https://github.com/apache/hadoop/commit/5d1889a66d91608d34ca9411fb6e9161e637e9d3>WS-2016-7071</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.1</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: N/A
- Attack Complexity: N/A
- Privileges Required: N/A
- User Interaction: N/A
- Scope: N/A
- Impact Metrics:
- Confidentiality Impact: N/A
- Integrity Impact: N/A
- Availability Impact: N/A
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/apache/hadoop/commit/5d1889a66d91608d34ca9411fb6e9161e637e9d3">https://github.com/apache/hadoop/commit/5d1889a66d91608d34ca9411fb6e9161e637e9d3</a></p>
<p>Release Date: 2020-01-08</p>
<p>Fix Resolution: 2.8.0,3.0.0-alpha1</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":false,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"Java","groupId":"org.apache.hadoop","packageName":"hadoop-common","packageVersion":"2.7.4","isTransitiveDependency":true,"dependencyTree":"org.apache.hbase:hbase-client:1.4.2;org.apache.hadoop:hadoop-common:2.7.4","isMinimumFixVersionAvailable":true,"minimumFixVersion":"2.8.0,3.0.0-alpha1"}],"vulnerabilityIdentifier":"WS-2016-7071","vulnerabilityDetails":"Apache Hadoop versions 2.7.2 to 2.7.7 are vulnerable to Cross-Site Request Forgery that targets HTTP requests to “NameNode” and “DataNode”.","vulnerabilityUrl":"https://github.com/apache/hadoop/commit/5d1889a66d91608d34ca9411fb6e9161e637e9d3","cvss3Severity":"high","cvss3Score":"7.1","cvss3Metrics":{"A":"N/A","AC":"N/A","PR":"N/A","S":"N/A","C":"N/A","UI":"N/A","AV":"N/A","I":"N/A"},"extraData":{}}</REMEDIATE> --> | True | WS-2016-7071 (High) detected in hadoop-common-2.7.4.jar - ## WS-2016-7071 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>hadoop-common-2.7.4.jar</b></p></summary>
<p>Apache Hadoop Common</p>
<p>Path to dependency file: /Argus/ArgusWebServices/pom.xml</p>
<p>Path to vulnerable library: /root/.m2/repository/org/apache/hadoop/hadoop-common/2.7.4/hadoop-common-2.7.4.jar,/root/.m2/repository/org/apache/hadoop/hadoop-common/2.7.4/hadoop-common-2.7.4.jar,/root/.m2/repository/org/apache/hadoop/hadoop-common/2.7.4/hadoop-common-2.7.4.jar</p>
<p>
Dependency Hierarchy:
- hbase-client-1.4.2.jar (Root Library)
- :x: **hadoop-common-2.7.4.jar** (Vulnerable Library)
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
Apache Hadoop versions 2.7.2 to 2.7.7 are vulnerable to Cross-Site Request Forgery that targets HTTP requests to “NameNode” and “DataNode”.
<p>Publish Date: 2020-01-08
<p>URL: <a href=https://github.com/apache/hadoop/commit/5d1889a66d91608d34ca9411fb6e9161e637e9d3>WS-2016-7071</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.1</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: N/A
- Attack Complexity: N/A
- Privileges Required: N/A
- User Interaction: N/A
- Scope: N/A
- Impact Metrics:
- Confidentiality Impact: N/A
- Integrity Impact: N/A
- Availability Impact: N/A
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/apache/hadoop/commit/5d1889a66d91608d34ca9411fb6e9161e637e9d3">https://github.com/apache/hadoop/commit/5d1889a66d91608d34ca9411fb6e9161e637e9d3</a></p>
<p>Release Date: 2020-01-08</p>
<p>Fix Resolution: 2.8.0,3.0.0-alpha1</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":false,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"Java","groupId":"org.apache.hadoop","packageName":"hadoop-common","packageVersion":"2.7.4","isTransitiveDependency":true,"dependencyTree":"org.apache.hbase:hbase-client:1.4.2;org.apache.hadoop:hadoop-common:2.7.4","isMinimumFixVersionAvailable":true,"minimumFixVersion":"2.8.0,3.0.0-alpha1"}],"vulnerabilityIdentifier":"WS-2016-7071","vulnerabilityDetails":"Apache Hadoop versions 2.7.2 to 2.7.7 are vulnerable to Cross-Site Request Forgery that targets HTTP requests to “NameNode” and “DataNode”.","vulnerabilityUrl":"https://github.com/apache/hadoop/commit/5d1889a66d91608d34ca9411fb6e9161e637e9d3","cvss3Severity":"high","cvss3Score":"7.1","cvss3Metrics":{"A":"N/A","AC":"N/A","PR":"N/A","S":"N/A","C":"N/A","UI":"N/A","AV":"N/A","I":"N/A"},"extraData":{}}</REMEDIATE> --> | non_priority | ws high detected in hadoop common jar ws high severity vulnerability vulnerable library hadoop common jar apache hadoop common path to dependency file argus arguswebservices pom xml path to vulnerable library root repository org apache hadoop hadoop common hadoop common jar root repository org apache hadoop hadoop common hadoop common jar root repository org apache hadoop hadoop common hadoop common jar dependency hierarchy hbase client jar root library x hadoop common jar vulnerable library vulnerability details apache hadoop versions to are vulnerable to cross site request forgery that targets http requests to “namenode” and “datanode” publish date url a href cvss score details base score metrics exploitability metrics attack vector n a attack complexity n a privileges required n a user interaction n a scope n a impact metrics confidentiality impact n a integrity impact n a availability impact n a for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution isopenpronvulnerability false ispackagebased true isdefaultbranch true packages vulnerabilityidentifier ws vulnerabilitydetails apache hadoop versions to are vulnerable to cross site request forgery that targets http requests to “namenode” and “datanode” vulnerabilityurl | 0 |
135,133 | 10,963,147,058 | IssuesEvent | 2019-11-27 18:57:21 | rancher/rancher | https://api.github.com/repos/rancher/rancher | closed | Cannot add node labels to imported k3s or rke nodes | [zube]: To Test kind/bug team/ca | Rancher v2.3.2
Rancher v2.2.x (pre-existing issue)
**What kind of request is this (question/bug/enhancement/feature request):**
Bug
**Steps to reproduce (least amount of steps as possible):**
- Import a k3s cluster (in my case v0.10.1 k3s) into Rancher using the UI
- Edit node and add a label
**Result:**
Label is never added.
**Expected Result:**
Label should be added to the node(s).
**Other details that may be helpful:**
Seems to have worked in an older v2.3 release | 1.0 | Cannot add node labels to imported k3s or rke nodes - Rancher v2.3.2
Rancher v2.2.x (pre-existing issue)
**What kind of request is this (question/bug/enhancement/feature request):**
Bug
**Steps to reproduce (least amount of steps as possible):**
- Import a k3s cluster (in my case v0.10.1 k3s) into Rancher using the UI
- Edit node and add a label
**Result:**
Label is never added.
**Expected Result:**
Label should be added to the node(s).
**Other details that may be helpful:**
Seems to have worked in an older v2.3 release | non_priority | cannot add node labels to imported or rke nodes rancher rancher x pre existing issue what kind of request is this question bug enhancement feature request bug steps to reproduce least amount of steps as possible import a cluster in my case into rancher using the ui edit node and add a label result label is never added expected result label should be added to the node s other details that may be helpful seems to have worked in an older release | 0 |
15,061 | 18,908,453,294 | IssuesEvent | 2021-11-16 11:36:45 | ValhelsiaTeam/Valhelsia-Structures | https://api.github.com/repos/ValhelsiaTeam/Valhelsia-Structures | closed | [1.17.1 - 0.1.0] Conflict with something (compatibility issue with Optifine) | Duplicate Type: Mod Compatibility | My game crashes every time I tried to play it and I narrowed down that this mod or its core is either conflicting with a mod I have or that it is broken on mine.
Version : 1.17.1
Crash Log : https://pastebin.com/Bk0KLAjE | True | [1.17.1 - 0.1.0] Conflict with something (compatibility issue with Optifine) - My game crashes every time I tried to play it and I narrowed down that this mod or its core is either conflicting with a mod I have or that it is broken on mine.
Version : 1.17.1
Crash Log : https://pastebin.com/Bk0KLAjE | non_priority | conflict with something compatibility issue with optifine my game crashes every time i tried to play it and i narrowed down that this mod or its core is either conflicting with a mod i have or that it is broken on mine version crash log | 0 |
72,509 | 31,768,921,973 | IssuesEvent | 2023-09-12 10:28:50 | gauravrs18/issue_onboarding | https://api.github.com/repos/gauravrs18/issue_onboarding | closed | dev-angular-integration-account-services-new-connection-component-activate-component
-consumer-details-component
-application-component
-payment-component | CX-account-services | dev-angular-integration-account-services-new-connection-component-activate-component
-consumer-details-component
-application-component
-payment-component | 1.0 | dev-angular-integration-account-services-new-connection-component-activate-component
-consumer-details-component
-application-component
-payment-component - dev-angular-integration-account-services-new-connection-component-activate-component
-consumer-details-component
-application-component
-payment-component | non_priority | dev angular integration account services new connection component activate component consumer details component application component payment component dev angular integration account services new connection component activate component consumer details component application component payment component | 0 |
124,739 | 26,525,512,294 | IssuesEvent | 2023-01-19 08:23:07 | numbbo/coco | https://api.github.com/repos/numbbo/coco | closed | [Bug report] Postprocessing incompatible with python 3.10 | bug Code-Postprocessing | **Describe the bug**
It seems that the COCO postprocessing is not compatible (yet) with python 3.10 (and most likely with python 3.11 as well):
```
Post-processing (1)
loading data...
C:\Users\[...localpath...]\PythonSoftwareFoundation.Python.3.10_qbz5n2kfra8p0\LocalCache\local-packages\Python310\site-packages\cocopp\pproc.py:1075: UserWarning: instance numbers not among the ones specified in 2009, 2010, 2012, 2013, and 2015-2018
warnings.warn(' instance numbers not among the ones specified in 2009, 2010, 2012, 2013, and 2015-2018')
Will generate output data in folder ppdata\random_search_of_cocoex.solvers_2D_on_bbob-003
this might take several minutes.
Scaling figures...
Loading best algorithm data from refalgs/best2009-bbob.tar.gz ...
Data consistent according to consistency_check() in pproc.DataSet
using: c:\users\[...localpath...]\pythonsoftwarefoundation.python.3.10_qbz5n2kfra8p0\localcache\local-packages\python310\site-packages\cocopp\refalgs/best2009-bbob.tar.gz
done (Tue Jan 10 20:41:53 2023).
Traceback (most recent call last):
File "C:\Users\[...localpath...]\code-experiments\build\python\example_experiment2.py", line 197, in <module>
cocopp.main(observer.result_folder) # re-run folders look like "...-001" etc
File "C:\Users\[...localpath...]\PythonSoftwareFoundation.Python.3.10_qbz5n2kfra8p0\LocalCache\local-packages\Python310\site-packages\cocopp\rungeneric.py", line 408, in main
dsld = rungeneric1.main(alg, outputdir, genopts + ["-o", outputdir, alg])
File "C:\Users\[...localpath...]\PythonSoftwareFoundation.Python.3.10_qbz5n2kfra8p0\LocalCache\local-packages\Python310\site-packages\cocopp\rungeneric1.py", line 154, in main
ppfigdim.main(dsList, values_of_interest, algoutputdir)
File "C:\Users\[...localpath...]\PythonSoftwareFoundation.Python.3.10_qbz5n2kfra8p0\LocalCache\local-packages\Python310\site-packages\cocopp\ppfigdim.py", line 595, in main
ppfig.save_figure(filename, dsList[0].algId)
File "C:\Users\[...localpath...]\PythonSoftwareFoundation.Python.3.10_qbz5n2kfra8p0\LocalCache\local-packages\Python310\site-packages\cocopp\ppfig.py", line 97, in save_figure
plt.savefig(filename + '.' + format,
File "C:\Users\[...localpath...]\PythonSoftwareFoundation.Python.3.10_qbz5n2kfra8p0\LocalCache\local-packages\Python310\site-packages\matplotlib\pyplot.py", line 954, in savefig
res = fig.savefig(*args, **kwargs)
File "C:\Users\[...localpath...]\PythonSoftwareFoundation.Python.3.10_qbz5n2kfra8p0\LocalCache\local-packages\Python310\site-packages\matplotlib\figure.py", line 3274, in savefig
self.canvas.print_figure(fname, **kwargs)
File "C:\Users\[...localpath...]\PythonSoftwareFoundation.Python.3.10_qbz5n2kfra8p0\LocalCache\local-packages\Python310\site-packages\matplotlib\backend_bases.py", line 2285, in print_figure
with cbook._setattr_cm(self, manager=None), \
File "C:\Program Files\WindowsApps\PythonSoftwareFoundation.Python.3.10_3.10.2544.0_x64__qbz5n2kfra8p0\lib\contextlib.py", line 135, in __enter__
return next(self.gen)
File "C:\Users\[...localpath...]\PythonSoftwareFoundation.Python.3.10_qbz5n2kfra8p0\LocalCache\local-packages\Python310\site-packages\matplotlib\backend_bases.py", line 2188, in _switch_canvas_and_return_print_method
canvas_class = get_registered_canvas_class(fmt)
File "C:\Users\[...localpath...]\PythonSoftwareFoundation.Python.3.10_qbz5n2kfra8p0\LocalCache\local-packages\Python310\site-packages\matplotlib\backend_bases.py", line 146, in get_registered_canvas_class
backend_class = importlib.import_module(backend_class).FigureCanvas
File "C:\Program Files\WindowsApps\PythonSoftwareFoundation.Python.3.10_3.10.2544.0_x64__qbz5n2kfra8p0\lib\importlib\__init__.py", line 126, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
File "<frozen importlib._bootstrap>", line 1050, in _gcd_import
File "<frozen importlib._bootstrap>", line 1027, in _find_and_load
File "<frozen importlib._bootstrap>", line 1006, in _find_and_load_unlocked
File "<frozen importlib._bootstrap>", line 688, in _load_unlocked
File "<frozen importlib._bootstrap_external>", line 883, in exec_module
File "<frozen importlib._bootstrap>", line 241, in _call_with_frames_removed
File "C:\Users\[...localpath...]\PythonSoftwareFoundation.Python.3.10_qbz5n2kfra8p0\LocalCache\local-packages\Python310\site-packages\matplotlib\backends\backend_pdf.py", line 43, in <module>
from . import _backend_pdf_ps
File "C:\Users\[...localpath...]\PythonSoftwareFoundation.Python.3.10_qbz5n2kfra8p0\LocalCache\local-packages\Python310\site-packages\matplotlib\backends\_backend_pdf_ps.py", line 8, in <module>
from fontTools import subset
File "C:\Users\[...localpath...]\PythonSoftwareFoundation.Python.3.10_qbz5n2kfra8p0\LocalCache\local-packages\Python310\site-packages\fontTools\subset\__init__.py", line 17, in <module>
from fontTools.varLib import varStore # for subset_varidxes
File "C:\Users\[...localpath...]\PythonSoftwareFoundation.Python.3.10_qbz5n2kfra8p0\LocalCache\local-packages\Python310\site-packages\fontTools\varLib\__init__.py", line 35, in <module>
from fontTools.varLib.iup import iup_delta_optimize
File "C:\Users\[...localpath...]\PythonSoftwareFoundation.Python.3.10_qbz5n2kfra8p0\LocalCache\local-packages\Python310\site-packages\fontTools\varLib\iup.py", line 17, in <module>
if cython.compiled:
AttributeError: module 'cython' has no attribute 'compiled'
```
Many thanks to Zeidan Braik for reporting this issue. | 1.0 | [Bug report] Postprocessing incompatible with python 3.10 - **Describe the bug**
It seems that the COCO postprocessing is not compatible (yet) with python 3.10 (and most likely with python 3.11 as well):
```
Post-processing (1)
loading data...
C:\Users\[...localpath...]\PythonSoftwareFoundation.Python.3.10_qbz5n2kfra8p0\LocalCache\local-packages\Python310\site-packages\cocopp\pproc.py:1075: UserWarning: instance numbers not among the ones specified in 2009, 2010, 2012, 2013, and 2015-2018
warnings.warn(' instance numbers not among the ones specified in 2009, 2010, 2012, 2013, and 2015-2018')
Will generate output data in folder ppdata\random_search_of_cocoex.solvers_2D_on_bbob-003
this might take several minutes.
Scaling figures...
Loading best algorithm data from refalgs/best2009-bbob.tar.gz ...
Data consistent according to consistency_check() in pproc.DataSet
using: c:\users\[...localpath...]\pythonsoftwarefoundation.python.3.10_qbz5n2kfra8p0\localcache\local-packages\python310\site-packages\cocopp\refalgs/best2009-bbob.tar.gz
done (Tue Jan 10 20:41:53 2023).
Traceback (most recent call last):
File "C:\Users\[...localpath...]\code-experiments\build\python\example_experiment2.py", line 197, in <module>
cocopp.main(observer.result_folder) # re-run folders look like "...-001" etc
File "C:\Users\[...localpath...]\PythonSoftwareFoundation.Python.3.10_qbz5n2kfra8p0\LocalCache\local-packages\Python310\site-packages\cocopp\rungeneric.py", line 408, in main
dsld = rungeneric1.main(alg, outputdir, genopts + ["-o", outputdir, alg])
File "C:\Users\[...localpath...]\PythonSoftwareFoundation.Python.3.10_qbz5n2kfra8p0\LocalCache\local-packages\Python310\site-packages\cocopp\rungeneric1.py", line 154, in main
ppfigdim.main(dsList, values_of_interest, algoutputdir)
File "C:\Users\[...localpath...]\PythonSoftwareFoundation.Python.3.10_qbz5n2kfra8p0\LocalCache\local-packages\Python310\site-packages\cocopp\ppfigdim.py", line 595, in main
ppfig.save_figure(filename, dsList[0].algId)
File "C:\Users\[...localpath...]\PythonSoftwareFoundation.Python.3.10_qbz5n2kfra8p0\LocalCache\local-packages\Python310\site-packages\cocopp\ppfig.py", line 97, in save_figure
plt.savefig(filename + '.' + format,
File "C:\Users\[...localpath...]\PythonSoftwareFoundation.Python.3.10_qbz5n2kfra8p0\LocalCache\local-packages\Python310\site-packages\matplotlib\pyplot.py", line 954, in savefig
res = fig.savefig(*args, **kwargs)
File "C:\Users\[...localpath...]\PythonSoftwareFoundation.Python.3.10_qbz5n2kfra8p0\LocalCache\local-packages\Python310\site-packages\matplotlib\figure.py", line 3274, in savefig
self.canvas.print_figure(fname, **kwargs)
File "C:\Users\[...localpath...]\PythonSoftwareFoundation.Python.3.10_qbz5n2kfra8p0\LocalCache\local-packages\Python310\site-packages\matplotlib\backend_bases.py", line 2285, in print_figure
with cbook._setattr_cm(self, manager=None), \
File "C:\Program Files\WindowsApps\PythonSoftwareFoundation.Python.3.10_3.10.2544.0_x64__qbz5n2kfra8p0\lib\contextlib.py", line 135, in __enter__
return next(self.gen)
File "C:\Users\[...localpath...]\PythonSoftwareFoundation.Python.3.10_qbz5n2kfra8p0\LocalCache\local-packages\Python310\site-packages\matplotlib\backend_bases.py", line 2188, in _switch_canvas_and_return_print_method
canvas_class = get_registered_canvas_class(fmt)
File "C:\Users\[...localpath...]\PythonSoftwareFoundation.Python.3.10_qbz5n2kfra8p0\LocalCache\local-packages\Python310\site-packages\matplotlib\backend_bases.py", line 146, in get_registered_canvas_class
backend_class = importlib.import_module(backend_class).FigureCanvas
File "C:\Program Files\WindowsApps\PythonSoftwareFoundation.Python.3.10_3.10.2544.0_x64__qbz5n2kfra8p0\lib\importlib\__init__.py", line 126, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
File "<frozen importlib._bootstrap>", line 1050, in _gcd_import
File "<frozen importlib._bootstrap>", line 1027, in _find_and_load
File "<frozen importlib._bootstrap>", line 1006, in _find_and_load_unlocked
File "<frozen importlib._bootstrap>", line 688, in _load_unlocked
File "<frozen importlib._bootstrap_external>", line 883, in exec_module
File "<frozen importlib._bootstrap>", line 241, in _call_with_frames_removed
File "C:\Users\[...localpath...]\PythonSoftwareFoundation.Python.3.10_qbz5n2kfra8p0\LocalCache\local-packages\Python310\site-packages\matplotlib\backends\backend_pdf.py", line 43, in <module>
from . import _backend_pdf_ps
File "C:\Users\[...localpath...]\PythonSoftwareFoundation.Python.3.10_qbz5n2kfra8p0\LocalCache\local-packages\Python310\site-packages\matplotlib\backends\_backend_pdf_ps.py", line 8, in <module>
from fontTools import subset
File "C:\Users\[...localpath...]\PythonSoftwareFoundation.Python.3.10_qbz5n2kfra8p0\LocalCache\local-packages\Python310\site-packages\fontTools\subset\__init__.py", line 17, in <module>
from fontTools.varLib import varStore # for subset_varidxes
File "C:\Users\[...localpath...]\PythonSoftwareFoundation.Python.3.10_qbz5n2kfra8p0\LocalCache\local-packages\Python310\site-packages\fontTools\varLib\__init__.py", line 35, in <module>
from fontTools.varLib.iup import iup_delta_optimize
File "C:\Users\[...localpath...]\PythonSoftwareFoundation.Python.3.10_qbz5n2kfra8p0\LocalCache\local-packages\Python310\site-packages\fontTools\varLib\iup.py", line 17, in <module>
if cython.compiled:
AttributeError: module 'cython' has no attribute 'compiled'
```
Many thanks to Zeidan Braik for reporting this issue. | non_priority | postprocessing incompatible with python describe the bug it seems that the coco postprocessing is not compatible yet with python and most likely with python as well post processing loading data c users pythonsoftwarefoundation python localcache local packages site packages cocopp pproc py userwarning instance numbers not among the ones specified in and warnings warn instance numbers not among the ones specified in and will generate output data in folder ppdata random search of cocoex solvers on bbob this might take several minutes scaling figures loading best algorithm data from refalgs bbob tar gz data consistent according to consistency check in pproc dataset using c users pythonsoftwarefoundation python localcache local packages site packages cocopp refalgs bbob tar gz done tue jan traceback most recent call last file c users code experiments build python example py line in cocopp main observer result folder re run folders look like etc file c users pythonsoftwarefoundation python localcache local packages site packages cocopp rungeneric py line in main dsld main alg outputdir genopts file c users pythonsoftwarefoundation python localcache local packages site packages cocopp py line in main ppfigdim main dslist values of interest algoutputdir file c users pythonsoftwarefoundation python localcache local packages site packages cocopp ppfigdim py line in main ppfig save figure filename dslist algid file c users pythonsoftwarefoundation python localcache local packages site packages cocopp ppfig py line in save figure plt savefig filename format file c users pythonsoftwarefoundation python localcache local packages site packages matplotlib pyplot py line in savefig res fig savefig args kwargs file c users pythonsoftwarefoundation python localcache local packages site packages matplotlib figure py line in savefig self canvas print figure fname kwargs file c users pythonsoftwarefoundation python localcache local packages site packages matplotlib backend bases py line in print figure with cbook setattr cm self manager none file c program files windowsapps pythonsoftwarefoundation python lib contextlib py line in enter return next self gen file c users pythonsoftwarefoundation python localcache local packages site packages matplotlib backend bases py line in switch canvas and return print method canvas class get registered canvas class fmt file c users pythonsoftwarefoundation python localcache local packages site packages matplotlib backend bases py line in get registered canvas class backend class importlib import module backend class figurecanvas file c program files windowsapps pythonsoftwarefoundation python lib importlib init py line in import module return bootstrap gcd import name package level file line in gcd import file line in find and load file line in find and load unlocked file line in load unlocked file line in exec module file line in call with frames removed file c users pythonsoftwarefoundation python localcache local packages site packages matplotlib backends backend pdf py line in from import backend pdf ps file c users pythonsoftwarefoundation python localcache local packages site packages matplotlib backends backend pdf ps py line in from fonttools import subset file c users pythonsoftwarefoundation python localcache local packages site packages fonttools subset init py line in from fonttools varlib import varstore for subset varidxes file c users pythonsoftwarefoundation python localcache local packages site packages fonttools varlib init py line in from fonttools varlib iup import iup delta optimize file c users pythonsoftwarefoundation python localcache local packages site packages fonttools varlib iup py line in if cython compiled attributeerror module cython has no attribute compiled many thanks to zeidan braik for reporting this issue | 0 |
23,840 | 4,048,850,173 | IssuesEvent | 2016-05-23 12:04:14 | IDgis/CRS2 | https://api.github.com/repos/IDgis/CRS2 | closed | kaart schaal | fout Gis-viewer wacht op input tester | de schaal van de kaart klopt niet helemaal. bij schaal 1:6000 op A3 is het schaalbalkje 9.2 cm lang op papier. | 1.0 | kaart schaal - de schaal van de kaart klopt niet helemaal. bij schaal 1:6000 op A3 is het schaalbalkje 9.2 cm lang op papier. | non_priority | kaart schaal de schaal van de kaart klopt niet helemaal bij schaal op is het schaalbalkje cm lang op papier | 0 |
288,589 | 24,917,763,447 | IssuesEvent | 2022-10-30 16:00:11 | dromara/hertzbeat | https://api.github.com/repos/dromara/hertzbeat | closed | [Task] <Unit Test Case> manager/controller/SummaryControllerTest.java | status: volunteer wanted unit test case | ### Description
Help us impl Unit Test For [manager/controller/SummaryControllerTest.java](https://github.com/dromara/hertzbeat/blob/master/manager/src/test/java/com/usthe/manager/controller/SummaryControllerTest.java)
You can learn and refer to the previous test cases impl.
1. controller example unit case: https://github.com/dromara/hertzbeat/blob/master/manager/src/test/java/com/usthe/manager/controller/AccountControllerTest.java
2. service example unit case: https://github.com/dromara/hertzbeat/blob/master/manager/src/test/java/com/usthe/manager/service/TagServiceTest.java
3. jpa sql dao example unit case: https://github.com/dromara/hertzbeat/blob/master/manager/src/test/java/com/usthe/manager/dao/MonitorDaoTest.java
### Task List
- [ ] Impl Unit Test For [manager/controller/SummaryControllerTest.java](https://github.com/dromara/hertzbeat/blob/master/manager/src/test/java/com/usthe/manager/controller/SummaryControllerTest.java) | 1.0 | [Task] <Unit Test Case> manager/controller/SummaryControllerTest.java - ### Description
Help us impl Unit Test For [manager/controller/SummaryControllerTest.java](https://github.com/dromara/hertzbeat/blob/master/manager/src/test/java/com/usthe/manager/controller/SummaryControllerTest.java)
You can learn and refer to the previous test cases impl.
1. controller example unit case: https://github.com/dromara/hertzbeat/blob/master/manager/src/test/java/com/usthe/manager/controller/AccountControllerTest.java
2. service example unit case: https://github.com/dromara/hertzbeat/blob/master/manager/src/test/java/com/usthe/manager/service/TagServiceTest.java
3. jpa sql dao example unit case: https://github.com/dromara/hertzbeat/blob/master/manager/src/test/java/com/usthe/manager/dao/MonitorDaoTest.java
### Task List
- [ ] Impl Unit Test For [manager/controller/SummaryControllerTest.java](https://github.com/dromara/hertzbeat/blob/master/manager/src/test/java/com/usthe/manager/controller/SummaryControllerTest.java) | non_priority | manager controller summarycontrollertest java description help us impl unit test for you can learn and refer to the previous test cases impl controller example unit case service example unit case jpa sql dao example unit case task list impl unit test for | 0 |
21,934 | 18,105,486,910 | IssuesEvent | 2021-09-22 18:43:30 | ray-project/ray | https://api.github.com/repos/ray-project/ray | opened | [Feature][workflow] Namespace for workflow | enhancement workflow-usability workflow | ### Search before asking
- [X] I had searched in the [issues](https://github.com/ray-project/ray/issues) and found no similar feature requirement.
### Description
In ray, we have already had a namespace concept which should be useful for workflow as well.
Recommend API should be:
```
workflow.init(namespace=name_space)
Actor.get_or_create(namespace=name_space)
```
### Use case
_No response_
### Related issues
_No response_
### Are you willing to submit a PR?
- [ ] Yes I am willing to submit a PR! | True | [Feature][workflow] Namespace for workflow - ### Search before asking
- [X] I had searched in the [issues](https://github.com/ray-project/ray/issues) and found no similar feature requirement.
### Description
In ray, we have already had a namespace concept which should be useful for workflow as well.
Recommend API should be:
```
workflow.init(namespace=name_space)
Actor.get_or_create(namespace=name_space)
```
### Use case
_No response_
### Related issues
_No response_
### Are you willing to submit a PR?
- [ ] Yes I am willing to submit a PR! | non_priority | namespace for workflow search before asking i had searched in the and found no similar feature requirement description in ray we have already had a namespace concept which should be useful for workflow as well recommend api should be workflow init namespace name space actor get or create namespace name space use case no response related issues no response are you willing to submit a pr yes i am willing to submit a pr | 0 |
23,078 | 7,276,178,183 | IssuesEvent | 2018-02-21 15:41:27 | neomutt/neomutt | https://api.github.com/repos/neomutt/neomutt | closed | Functional and unit tests for CI | needs:decision status:in-progress topic:automatization topic:build-process topic:lua-scripting topic:stability topic:testing type:enhancement | following #222 and all the others discussion about testing. It took me some time, but I finally found out a decent way to implement functional and unit testing for (neo)mutt.
## functional tests
Those are tests being done using the mutt runtime, calling commands using mutt's eventloop. To achieve that, the Lua API is a good way to go #298.
So I've done exactly that: https://gist.github.com/35be5c581aaabf6f1c453cbc2a6e6147
A few tests that are ran by calling:
```
build/mutt -F tests/functional/test_runner.muttrc --batch
```
Those tests will *not* be included in the Lua PR #298.
## unit tests
those ones are a bit trickier. The idea is to to access each header of mutt and test the API exposed through the compiled objects. I've achieved this by using [Luajit]+[FFI], and compiling mutt as a big shared library. To complete the testing toolchain (and load all the headers and symbols), I've stolen a bunch of lua files from neovim/neovim 😀 like [helpers.lua].
And then I wrote a test case for the lists (babysteps!): https://gist.github.com/b12b948616341d8dffd825ae9a5efcea
[FFI]:https://en.wikipedia.org/wiki/Foreign_function_interface
[Luajit]:http://luajit.org
[helpers.lua]:https://github.com/neovim/neovim/blob/master/test/unit/helpers.lua | 1.0 | Functional and unit tests for CI - following #222 and all the others discussion about testing. It took me some time, but I finally found out a decent way to implement functional and unit testing for (neo)mutt.
## functional tests
Those are tests being done using the mutt runtime, calling commands using mutt's eventloop. To achieve that, the Lua API is a good way to go #298.
So I've done exactly that: https://gist.github.com/35be5c581aaabf6f1c453cbc2a6e6147
A few tests that are ran by calling:
```
build/mutt -F tests/functional/test_runner.muttrc --batch
```
Those tests will *not* be included in the Lua PR #298.
## unit tests
those ones are a bit trickier. The idea is to to access each header of mutt and test the API exposed through the compiled objects. I've achieved this by using [Luajit]+[FFI], and compiling mutt as a big shared library. To complete the testing toolchain (and load all the headers and symbols), I've stolen a bunch of lua files from neovim/neovim 😀 like [helpers.lua].
And then I wrote a test case for the lists (babysteps!): https://gist.github.com/b12b948616341d8dffd825ae9a5efcea
[FFI]:https://en.wikipedia.org/wiki/Foreign_function_interface
[Luajit]:http://luajit.org
[helpers.lua]:https://github.com/neovim/neovim/blob/master/test/unit/helpers.lua | non_priority | functional and unit tests for ci following and all the others discussion about testing it took me some time but i finally found out a decent way to implement functional and unit testing for neo mutt functional tests those are tests being done using the mutt runtime calling commands using mutt s eventloop to achieve that the lua api is a good way to go so i ve done exactly that a few tests that are ran by calling build mutt f tests functional test runner muttrc batch those tests will not be included in the lua pr unit tests those ones are a bit trickier the idea is to to access each header of mutt and test the api exposed through the compiled objects i ve achieved this by using and compiling mutt as a big shared library to complete the testing toolchain and load all the headers and symbols i ve stolen a bunch of lua files from neovim neovim 😀 like and then i wrote a test case for the lists babysteps | 0 |
161,576 | 20,154,148,079 | IssuesEvent | 2022-02-09 15:03:21 | kapseliboi/mimic | https://api.github.com/repos/kapseliboi/mimic | opened | CVE-2017-16129 (Medium) detected in superagent-3.5.2.tgz | security vulnerability | ## CVE-2017-16129 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>superagent-3.5.2.tgz</b></p></summary>
<p>elegant & feature rich browser / node HTTP with a fluent API</p>
<p>Library home page: <a href="https://registry.npmjs.org/superagent/-/superagent-3.5.2.tgz">https://registry.npmjs.org/superagent/-/superagent-3.5.2.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/superagent/package.json</p>
<p>
Dependency Hierarchy:
- :x: **superagent-3.5.2.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/kapseliboi/mimic/commit/6d4fe404335bf56c57080e4ab1425b65bbe3ac2f">6d4fe404335bf56c57080e4ab1425b65bbe3ac2f</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
The HTTP client module superagent is vulnerable to ZIP bomb attacks. In a ZIP bomb attack, the HTTP server replies with a compressed response that becomes several magnitudes larger once uncompressed. If a client does not take special care when processing such responses, it may result in excessive CPU and/or memory consumption. An attacker might exploit such a weakness for a DoS attack. To exploit this the attacker must control the location (URL) that superagent makes a request to.
<p>Publish Date: 2018-06-07
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2017-16129>CVE-2017-16129</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.9</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://www.npmjs.com/advisories/479/versions">https://www.npmjs.com/advisories/479/versions</a></p>
<p>Release Date: 2018-06-07</p>
<p>Fix Resolution: 3.7.0</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | CVE-2017-16129 (Medium) detected in superagent-3.5.2.tgz - ## CVE-2017-16129 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>superagent-3.5.2.tgz</b></p></summary>
<p>elegant & feature rich browser / node HTTP with a fluent API</p>
<p>Library home page: <a href="https://registry.npmjs.org/superagent/-/superagent-3.5.2.tgz">https://registry.npmjs.org/superagent/-/superagent-3.5.2.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/superagent/package.json</p>
<p>
Dependency Hierarchy:
- :x: **superagent-3.5.2.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/kapseliboi/mimic/commit/6d4fe404335bf56c57080e4ab1425b65bbe3ac2f">6d4fe404335bf56c57080e4ab1425b65bbe3ac2f</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
The HTTP client module superagent is vulnerable to ZIP bomb attacks. In a ZIP bomb attack, the HTTP server replies with a compressed response that becomes several magnitudes larger once uncompressed. If a client does not take special care when processing such responses, it may result in excessive CPU and/or memory consumption. An attacker might exploit such a weakness for a DoS attack. To exploit this the attacker must control the location (URL) that superagent makes a request to.
<p>Publish Date: 2018-06-07
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2017-16129>CVE-2017-16129</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.9</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://www.npmjs.com/advisories/479/versions">https://www.npmjs.com/advisories/479/versions</a></p>
<p>Release Date: 2018-06-07</p>
<p>Fix Resolution: 3.7.0</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_priority | cve medium detected in superagent tgz cve medium severity vulnerability vulnerable library superagent tgz elegant feature rich browser node http with a fluent api library home page a href path to dependency file package json path to vulnerable library node modules superagent package json dependency hierarchy x superagent tgz vulnerable library found in head commit a href found in base branch master vulnerability details the http client module superagent is vulnerable to zip bomb attacks in a zip bomb attack the http server replies with a compressed response that becomes several magnitudes larger once uncompressed if a client does not take special care when processing such responses it may result in excessive cpu and or memory consumption an attacker might exploit such a weakness for a dos attack to exploit this the attacker must control the location url that superagent makes a request to publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity high privileges required none user interaction none scope unchanged impact metrics confidentiality impact none integrity impact none availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution step up your open source security game with whitesource | 0 |
344,050 | 30,710,257,027 | IssuesEvent | 2023-07-27 09:16:49 | wazuh/wazuh | https://api.github.com/repos/wazuh/wazuh | opened | Release 4.5.0 - Alpha 1 - Integration tests | type/test level/task | # Description
| Wazuh QA: Branch | Wazuh QA: Commit | Wazuh: Tag | Wazuh: Commit |
|:--:|:--:|:--:|:--:|
| `v4.5.0-alpha1`| https://github.com/wazuh/wazuh-qa/commit/ede149c9ab767d23d3d4f9ca461186dc660e45a6 | `v4.5.0-alpha1` |https://github.com/wazuh/wazuh/commit/39df1e74bfd035fea8948191ae195fc17eb7e2f3 |
We are going to check that the integration tests of the `4.5` branch of `wazuh-qa` work correctly using the [v4.5.0-alpha1](https://github.com/wazuh/wazuh/tree/v4.5.0-alpha1) version of `wazuh`.
The tests will be performed in Jenkins using `centOS` as the manager OS. As for the agents, `Linux`, `Windows` , `Solaris`, `macOS` will be used as required.
## Tests Integration - Status
#### Main RC issue
- https://github.com/wazuh/wazuh/issues/18058
#### References
|Color|Status |
|:--:|:--|
|🟢|All tests passed successfully|
|🟡|All tests passed but there are some warnings|
|🔴|Some tests have failures or errors|
|🔵|Test execution in progress|
|:black_circle:|To Do|
|🟠|Jenkins provision fails|
|:purple_circle:| All skipped |
## Test Integration - Results
<table>
<thead>
<tr>
<th style="width: 175px;">Name</th>
<th style="width: 499px;" colspan="6">Jenkins</th>
</tr>
</thead>
<tbody>
<tr>
<td style="width: 175px;">OS</td>
<td style="width: 208px;" colspan="2">Linux</td>
<td style="width: 79px;">Windows</td>
<td style="width: 97px;">Solaris</td>
<td style="width: 97px;" colspan="2">macOS</td>
</tr>
<tr>
<td style="width: 175px;">Target</td>
<td style="width: 103px;">Manager</td>
<td style="width: 99px;">Agent</td>
<td style="width: 79px;">Agent</td>
<td style="width: 97px;">Agent</td>
<td style="width: 97px;" colspan="2">Agent</td>
</tr>
<tr>
<td style="width: 175px;"><strong>active_response</strong></td>
<td style="width: 103px;">🔵</td>
<td style="width: 99px;">🔵</td>
<td style="width: 79px;">🔵</td>
<td style="text-align: center; width: 97px;">NA</td>
<td style="text-align: center; width: 97px;" colspan="2">NA</td>
</tr>
<tr>
<td style="width: 175px;"><strong>agentd</strong></td>
<td style="width: 103px;">NA</td>
<td style="width: 99px;">🔵</td>
<td style="width: 79px;">🔵</td>
<td style="text-align: center; width: 97px;">NA</td>
<td style="text-align: center; width: 97px;" colspan="2">NA</td>
</tr>
<tr>
<td style="width: 175px;"><strong>analysisd</strong></td>
<td style="width: 103px;">🔵 </td>
<td style="width: 99px;">NA</td>
<td style="width: 79px;">NA</td>
<td style="text-align: center; width: 97px;">NA</td>
<td style="text-align: center; width: 97px;" colspan="2">NA</td>
</tr>
<tr>
<td style="width: 175px;"><strong>api</strong></td>
<td style="width: 103px;">🔵</td>
<td style="width: 99px;">NA</td>
<td style="width: 79px;">NA</td>
<td style="text-align: center; width: 97px;">NA</td>
<td style="text-align: center; width: 97px;" colspan="2">NA</td>
</tr>
<tr>
<td style="width: 175px;"><strong>authd</strong></td>
<td style="width: 103px;">🔵</td>
<td style="width: 99px;"> NA</td>
<td style="width: 79px;">NA</td>
<td style="text-align: center; width: 97px;">NA</td>
<td style="text-align: center; width: 97px;" colspan="2">NA</td>
</tr>
<tr>
<td style="width: 175px;"><strong>enrollment<br/></strong></td>
<td style="width: 103px;">NA</td>
<td style="width: 99px;">🔵</td>
<td style="width: 79px;">🔵</td>
<td style="text-align: center; width: 97px;">NA</td>
<td style="text-align: center; width: 97px;" colspan="2">NA</td>
</tr>
<tr>
<td style="width: 175px;"><strong>fim</strong></td>
<td style="width: 103px;">🔵</td>
<td style="width: 99px;">🔵</td>
<td style="width: 79px;">🔵</td>
<td style="width: 97px;">🔵</td>
<td style="width: 97px;" colspan="2">🔵</td>
</tr>
<tr>
<td style="width: 175px;"><strong>gcloud<br/></strong></td>
<td style="width: 103px;">🔵</td>
<td style="width: 99px;">NA</td>
<td style="width: 79px;">NA</td>
<td style="text-align: center; width: 97px;">NA</td>
<td style="text-align: center; width: 97px;" colspan="2">NA</td>
</tr>
<tr>
<td style="width: 175px;"><strong>github<br /></strong></td>
<td style="width: 103px;">🔵</td>
<td style="width: 99px;">🔵</td>
<td style="width: 79px;">NA</td>
<td style="text-align: center; width: 97px;">NA</td>
<td style="text-align: center; width: 97px;" colspan="2">NA</td>
</tr>
<tr>
<td style="width: 175px;"><strong>logcollector</strong></td>
<td style="width: 103px;">🔵</td>
<td style="width: 99px;">🔵</td>
<td style="width: 79px;">🔵</td>
<td style="width: 97px;">🔵</td>
<td style="width: 97px;" colspan="2">🔵</td>
</tr>
<tr>
<td style="width: 175px;"><strong>logtest<br/></strong></td>
<td style="width: 103px;">🔵</td>
<td style="width: 99px;">NA</td>
<td style="width: 79px;">NA</td>
<td style="text-align: center; width: 97px;">NA</td>
<td style="text-align: center; width: 97px;" colspan="2">NA</td>
</tr>
<tr>
<td style="width: 175px;"><strong>office365<br /></strong></td>
<td style="width: 103px;">🔵</td>
<td style="width: 99px;">🔵</td>
<td style="width: 79px;">NA</td>
<td style="text-align: center; width: 97px;">NA</td>
<td style="text-align: center; width: 97px;" colspan="2">NA</td>
</tr>
<tr>
<td style="width: 175px;"><strong>remoted</strong></td>
<td style="width: 103px;">🔵</td>
<td style="width: 99px;">NA</td>
<td style="width: 79px;">NA</td>
<td style="text-align: center; width: 97px;">NA</td>
<td style="text-align: center; width: 97px;" colspan="2">NA</td>
</tr>
<tr>
<td style="width: 175px;"><strong>rids</strong></td>
<td style="width: 103px;">🔵</td>
<td style="width: 99px;">NA</td>
<td style="width: 79px;">NA</td>
<td style="text-align: center; width: 97px;">NA</td>
<td style="text-align: center; width: 97px;" colspan="2">NA</td>
</tr>
<tr>
<td style="width: 175px;"><strong>rootcheck</strong></td>
<td style="width: 103px;">🔵</td>
<td style="width: 99px;">NA</td>
<td style="width: 79px;">NA</td>
<td style="text-align: center; width: 97px;">NA</td>
<td style="text-align: center; width: 97px;" colspan="2">NA</td>
</tr>
<tr>
<td style="width: 175px;"><strong>vulnerability_detector</strong></td>
<td style="width: 103px;">🔵</td>
<td style="width: 99px;">NA</td>
<td style="width: 79px;">NA</td>
<td style="text-align: center; width: 97px;">NA</td>
<td style="text-align: center; width: 97px;" colspan="2">NA</td>
</tr>
<tr>
<td style="width: 175px;"><strong>wazuh_db</strong></td>
<td style="width: 103px;">🔵</td>
<td style="width: 99px;">NA</td>
<td style="width: 79px;">NA</td>
<td style="text-align: center; width: 97px;">NA</td>
<td style="text-align: center; width: 97px;" colspan="2">NA</td>
</tr>
<tr>
<td style="width: 175px;"><strong>syscollector</strong></td>
<td style="width: 103px;">🔵</td>
<td style="width: 99px;">🔵</td>
<td style="width: 79px;">🔵</td>
<td style="text-align: center; width: 97px;">NA</td>
<td style="text-align: center; width: 97px;" colspan="2">🔵</td>
</tr>
</tbody>
</table>
## Evidence
**IT Launcher build**: https://ci.wazuh.info/job/Test_integration_launcher/178/
## Conclusion
WIP
## Auditors validation
The definition of done for this one is the validation of the conclusions and the test results from all auditors.
All checks from below must be accepted in order to close this issue.
- [ ] @davidjiglesias
- [ ] @jnasselle | 1.0 | Release 4.5.0 - Alpha 1 - Integration tests - # Description
| Wazuh QA: Branch | Wazuh QA: Commit | Wazuh: Tag | Wazuh: Commit |
|:--:|:--:|:--:|:--:|
| `v4.5.0-alpha1`| https://github.com/wazuh/wazuh-qa/commit/ede149c9ab767d23d3d4f9ca461186dc660e45a6 | `v4.5.0-alpha1` |https://github.com/wazuh/wazuh/commit/39df1e74bfd035fea8948191ae195fc17eb7e2f3 |
We are going to check that the integration tests of the `4.5` branch of `wazuh-qa` work correctly using the [v4.5.0-alpha1](https://github.com/wazuh/wazuh/tree/v4.5.0-alpha1) version of `wazuh`.
The tests will be performed in Jenkins using `centOS` as the manager OS. As for the agents, `Linux`, `Windows` , `Solaris`, `macOS` will be used as required.
## Tests Integration - Status
#### Main RC issue
- https://github.com/wazuh/wazuh/issues/18058
#### References
|Color|Status |
|:--:|:--|
|🟢|All tests passed successfully|
|🟡|All tests passed but there are some warnings|
|🔴|Some tests have failures or errors|
|🔵|Test execution in progress|
|:black_circle:|To Do|
|🟠|Jenkins provision fails|
|:purple_circle:| All skipped |
## Test Integration - Results
<table>
<thead>
<tr>
<th style="width: 175px;">Name</th>
<th style="width: 499px;" colspan="6">Jenkins</th>
</tr>
</thead>
<tbody>
<tr>
<td style="width: 175px;">OS</td>
<td style="width: 208px;" colspan="2">Linux</td>
<td style="width: 79px;">Windows</td>
<td style="width: 97px;">Solaris</td>
<td style="width: 97px;" colspan="2">macOS</td>
</tr>
<tr>
<td style="width: 175px;">Target</td>
<td style="width: 103px;">Manager</td>
<td style="width: 99px;">Agent</td>
<td style="width: 79px;">Agent</td>
<td style="width: 97px;">Agent</td>
<td style="width: 97px;" colspan="2">Agent</td>
</tr>
<tr>
<td style="width: 175px;"><strong>active_response</strong></td>
<td style="width: 103px;">🔵</td>
<td style="width: 99px;">🔵</td>
<td style="width: 79px;">🔵</td>
<td style="text-align: center; width: 97px;">NA</td>
<td style="text-align: center; width: 97px;" colspan="2">NA</td>
</tr>
<tr>
<td style="width: 175px;"><strong>agentd</strong></td>
<td style="width: 103px;">NA</td>
<td style="width: 99px;">🔵</td>
<td style="width: 79px;">🔵</td>
<td style="text-align: center; width: 97px;">NA</td>
<td style="text-align: center; width: 97px;" colspan="2">NA</td>
</tr>
<tr>
<td style="width: 175px;"><strong>analysisd</strong></td>
<td style="width: 103px;">🔵 </td>
<td style="width: 99px;">NA</td>
<td style="width: 79px;">NA</td>
<td style="text-align: center; width: 97px;">NA</td>
<td style="text-align: center; width: 97px;" colspan="2">NA</td>
</tr>
<tr>
<td style="width: 175px;"><strong>api</strong></td>
<td style="width: 103px;">🔵</td>
<td style="width: 99px;">NA</td>
<td style="width: 79px;">NA</td>
<td style="text-align: center; width: 97px;">NA</td>
<td style="text-align: center; width: 97px;" colspan="2">NA</td>
</tr>
<tr>
<td style="width: 175px;"><strong>authd</strong></td>
<td style="width: 103px;">🔵</td>
<td style="width: 99px;"> NA</td>
<td style="width: 79px;">NA</td>
<td style="text-align: center; width: 97px;">NA</td>
<td style="text-align: center; width: 97px;" colspan="2">NA</td>
</tr>
<tr>
<td style="width: 175px;"><strong>enrollment<br/></strong></td>
<td style="width: 103px;">NA</td>
<td style="width: 99px;">🔵</td>
<td style="width: 79px;">🔵</td>
<td style="text-align: center; width: 97px;">NA</td>
<td style="text-align: center; width: 97px;" colspan="2">NA</td>
</tr>
<tr>
<td style="width: 175px;"><strong>fim</strong></td>
<td style="width: 103px;">🔵</td>
<td style="width: 99px;">🔵</td>
<td style="width: 79px;">🔵</td>
<td style="width: 97px;">🔵</td>
<td style="width: 97px;" colspan="2">🔵</td>
</tr>
<tr>
<td style="width: 175px;"><strong>gcloud<br/></strong></td>
<td style="width: 103px;">🔵</td>
<td style="width: 99px;">NA</td>
<td style="width: 79px;">NA</td>
<td style="text-align: center; width: 97px;">NA</td>
<td style="text-align: center; width: 97px;" colspan="2">NA</td>
</tr>
<tr>
<td style="width: 175px;"><strong>github<br /></strong></td>
<td style="width: 103px;">🔵</td>
<td style="width: 99px;">🔵</td>
<td style="width: 79px;">NA</td>
<td style="text-align: center; width: 97px;">NA</td>
<td style="text-align: center; width: 97px;" colspan="2">NA</td>
</tr>
<tr>
<td style="width: 175px;"><strong>logcollector</strong></td>
<td style="width: 103px;">🔵</td>
<td style="width: 99px;">🔵</td>
<td style="width: 79px;">🔵</td>
<td style="width: 97px;">🔵</td>
<td style="width: 97px;" colspan="2">🔵</td>
</tr>
<tr>
<td style="width: 175px;"><strong>logtest<br/></strong></td>
<td style="width: 103px;">🔵</td>
<td style="width: 99px;">NA</td>
<td style="width: 79px;">NA</td>
<td style="text-align: center; width: 97px;">NA</td>
<td style="text-align: center; width: 97px;" colspan="2">NA</td>
</tr>
<tr>
<td style="width: 175px;"><strong>office365<br /></strong></td>
<td style="width: 103px;">🔵</td>
<td style="width: 99px;">🔵</td>
<td style="width: 79px;">NA</td>
<td style="text-align: center; width: 97px;">NA</td>
<td style="text-align: center; width: 97px;" colspan="2">NA</td>
</tr>
<tr>
<td style="width: 175px;"><strong>remoted</strong></td>
<td style="width: 103px;">🔵</td>
<td style="width: 99px;">NA</td>
<td style="width: 79px;">NA</td>
<td style="text-align: center; width: 97px;">NA</td>
<td style="text-align: center; width: 97px;" colspan="2">NA</td>
</tr>
<tr>
<td style="width: 175px;"><strong>rids</strong></td>
<td style="width: 103px;">🔵</td>
<td style="width: 99px;">NA</td>
<td style="width: 79px;">NA</td>
<td style="text-align: center; width: 97px;">NA</td>
<td style="text-align: center; width: 97px;" colspan="2">NA</td>
</tr>
<tr>
<td style="width: 175px;"><strong>rootcheck</strong></td>
<td style="width: 103px;">🔵</td>
<td style="width: 99px;">NA</td>
<td style="width: 79px;">NA</td>
<td style="text-align: center; width: 97px;">NA</td>
<td style="text-align: center; width: 97px;" colspan="2">NA</td>
</tr>
<tr>
<td style="width: 175px;"><strong>vulnerability_detector</strong></td>
<td style="width: 103px;">🔵</td>
<td style="width: 99px;">NA</td>
<td style="width: 79px;">NA</td>
<td style="text-align: center; width: 97px;">NA</td>
<td style="text-align: center; width: 97px;" colspan="2">NA</td>
</tr>
<tr>
<td style="width: 175px;"><strong>wazuh_db</strong></td>
<td style="width: 103px;">🔵</td>
<td style="width: 99px;">NA</td>
<td style="width: 79px;">NA</td>
<td style="text-align: center; width: 97px;">NA</td>
<td style="text-align: center; width: 97px;" colspan="2">NA</td>
</tr>
<tr>
<td style="width: 175px;"><strong>syscollector</strong></td>
<td style="width: 103px;">🔵</td>
<td style="width: 99px;">🔵</td>
<td style="width: 79px;">🔵</td>
<td style="text-align: center; width: 97px;">NA</td>
<td style="text-align: center; width: 97px;" colspan="2">🔵</td>
</tr>
</tbody>
</table>
## Evidence
**IT Launcher build**: https://ci.wazuh.info/job/Test_integration_launcher/178/
## Conclusion
WIP
## Auditors validation
The definition of done for this one is the validation of the conclusions and the test results from all auditors.
All checks from below must be accepted in order to close this issue.
- [ ] @davidjiglesias
- [ ] @jnasselle | non_priority | release alpha integration tests description wazuh qa branch wazuh qa commit wazuh tag wazuh commit we are going to check that the integration tests of the branch of wazuh qa work correctly using the version of wazuh the tests will be performed in jenkins using centos as the manager os as for the agents linux windows solaris macos will be used as required tests integration status main rc issue references color status 🟢 all tests passed successfully 🟡 all tests passed but there are some warnings 🔴 some tests have failures or errors 🔵 test execution in progress black circle to do 🟠 jenkins provision fails purple circle all skipped test integration results name jenkins os linux windows solaris macos target manager agent agent agent agent active response 🔵 🔵 🔵 na na agentd na 🔵 🔵 na na analysisd 🔵 na na na na api 🔵 na na na na authd 🔵 nbsp na na na na enrollment na 🔵 🔵 na na fim 🔵 🔵 🔵 🔵 🔵 gcloud 🔵 na na na na github 🔵 🔵 na na na logcollector 🔵 🔵 🔵 🔵 🔵 logtest 🔵 na na na na 🔵 🔵 na na na remoted 🔵 na na na na rids 🔵 na na na na rootcheck 🔵 na na na na vulnerability detector 🔵 na na na na wazuh db 🔵 na na na na syscollector 🔵 🔵 🔵 na 🔵 evidence it launcher build conclusion wip auditors validation the definition of done for this one is the validation of the conclusions and the test results from all auditors all checks from below must be accepted in order to close this issue davidjiglesias jnasselle | 0 |
396,009 | 27,096,181,635 | IssuesEvent | 2023-02-15 03:10:21 | statelesscode/nerd_dice | https://api.github.com/repos/statelesscode/nerd_dice | closed | Create a CONTRIBUTING.md file | documentation | Create a CONTRIBUTING.md file. See the [nerd_dice_dot_com](https://github.com/statelesscode/nerd_dice_dot_com/blob/main/CONTRIBUTING.md) version as an example. | 1.0 | Create a CONTRIBUTING.md file - Create a CONTRIBUTING.md file. See the [nerd_dice_dot_com](https://github.com/statelesscode/nerd_dice_dot_com/blob/main/CONTRIBUTING.md) version as an example. | non_priority | create a contributing md file create a contributing md file see the version as an example | 0 |
48,630 | 25,720,215,417 | IssuesEvent | 2022-12-07 13:12:15 | decentraland/unity-renderer | https://api.github.com/repos/decentraland/unity-renderer | closed | Scene unable to start in preview | bug need validation major stream-performance | Lastraum has reported that his scene has suddenly stop working with this crash
The scene is in this link https://files.slack.com/files-pri/T9EJMTT7Z-F02KW2LCVRP/download/archive.zip
It seems to be related to a glb
 | True | Scene unable to start in preview - Lastraum has reported that his scene has suddenly stop working with this crash
The scene is in this link https://files.slack.com/files-pri/T9EJMTT7Z-F02KW2LCVRP/download/archive.zip
It seems to be related to a glb
 | non_priority | scene unable to start in preview lastraum has reported that his scene has suddenly stop working with this crash the scene is in this link it seems to be related to a glb | 0 |
86,106 | 10,719,826,039 | IssuesEvent | 2019-10-26 13:17:17 | ekzyis/physicsbot | https://api.github.com/repos/ekzyis/physicsbot | opened | Wrong file extension | bug design | I always add ".pdf" to a file attachment at the end if it is not already included but this breaks opening of files since they may not even be PDFs.
The best way would be to know how the server would name it when downloading in browser.
This should be included in the Header "Content-Disposition"
See https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Content-Disposition | 1.0 | Wrong file extension - I always add ".pdf" to a file attachment at the end if it is not already included but this breaks opening of files since they may not even be PDFs.
The best way would be to know how the server would name it when downloading in browser.
This should be included in the Header "Content-Disposition"
See https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Content-Disposition | non_priority | wrong file extension i always add pdf to a file attachment at the end if it is not already included but this breaks opening of files since they may not even be pdfs the best way would be to know how the server would name it when downloading in browser this should be included in the header content disposition see | 0 |
201,475 | 22,972,490,937 | IssuesEvent | 2022-07-20 05:25:52 | smb-h/nn-lab | https://api.github.com/repos/smb-h/nn-lab | closed | CVE-2022-29202 (Medium) detected in tensorflow-2.6.3-cp37-cp37m-manylinux2010_x86_64.whl - autoclosed | security vulnerability | ## CVE-2022-29202 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>tensorflow-2.6.3-cp37-cp37m-manylinux2010_x86_64.whl</b></p></summary>
<p>TensorFlow is an open source machine learning framework for everyone.</p>
<p>Library home page: <a href="https://files.pythonhosted.org/packages/73/a3/142f73d0e076f5582fd8da29c68af0413bf529933eed09f86a8857fab0d6/tensorflow-2.6.3-cp37-cp37m-manylinux2010_x86_64.whl">https://files.pythonhosted.org/packages/73/a3/142f73d0e076f5582fd8da29c68af0413bf529933eed09f86a8857fab0d6/tensorflow-2.6.3-cp37-cp37m-manylinux2010_x86_64.whl</a></p>
<p>Path to dependency file: /requirements.txt</p>
<p>Path to vulnerable library: /requirements.txt</p>
<p>
Dependency Hierarchy:
- :x: **tensorflow-2.6.3-cp37-cp37m-manylinux2010_x86_64.whl** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/smb-h/nn-lab/commit/977293e8b3e6b1a0183210a2c32c01f32c53dd6c">977293e8b3e6b1a0183210a2c32c01f32c53dd6c</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
TensorFlow is an open source platform for machine learning. Prior to versions 2.9.0, 2.8.1, 2.7.2, and 2.6.4, the implementation of `tf.ragged.constant` does not fully validate the input arguments. This results in a denial of service by consuming all available memory. Versions 2.9.0, 2.8.1, 2.7.2, and 2.6.4 contain a patch for this issue.
<p>Publish Date: 2022-05-20
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-29202>CVE-2022-29202</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-29202">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-29202</a></p>
<p>Release Date: 2022-05-20</p>
<p>Fix Resolution: tensorflow - 2.6.4,2.7.2,2.8.1,2.9.0;tensorflow-cpu - 2.6.4,2.7.2,2.8.1,2.9.0;tensorflow-gpu - 2.6.4,2.7.2,2.8.1,2.9.0</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | CVE-2022-29202 (Medium) detected in tensorflow-2.6.3-cp37-cp37m-manylinux2010_x86_64.whl - autoclosed - ## CVE-2022-29202 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>tensorflow-2.6.3-cp37-cp37m-manylinux2010_x86_64.whl</b></p></summary>
<p>TensorFlow is an open source machine learning framework for everyone.</p>
<p>Library home page: <a href="https://files.pythonhosted.org/packages/73/a3/142f73d0e076f5582fd8da29c68af0413bf529933eed09f86a8857fab0d6/tensorflow-2.6.3-cp37-cp37m-manylinux2010_x86_64.whl">https://files.pythonhosted.org/packages/73/a3/142f73d0e076f5582fd8da29c68af0413bf529933eed09f86a8857fab0d6/tensorflow-2.6.3-cp37-cp37m-manylinux2010_x86_64.whl</a></p>
<p>Path to dependency file: /requirements.txt</p>
<p>Path to vulnerable library: /requirements.txt</p>
<p>
Dependency Hierarchy:
- :x: **tensorflow-2.6.3-cp37-cp37m-manylinux2010_x86_64.whl** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/smb-h/nn-lab/commit/977293e8b3e6b1a0183210a2c32c01f32c53dd6c">977293e8b3e6b1a0183210a2c32c01f32c53dd6c</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
TensorFlow is an open source platform for machine learning. Prior to versions 2.9.0, 2.8.1, 2.7.2, and 2.6.4, the implementation of `tf.ragged.constant` does not fully validate the input arguments. This results in a denial of service by consuming all available memory. Versions 2.9.0, 2.8.1, 2.7.2, and 2.6.4 contain a patch for this issue.
<p>Publish Date: 2022-05-20
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-29202>CVE-2022-29202</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-29202">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-29202</a></p>
<p>Release Date: 2022-05-20</p>
<p>Fix Resolution: tensorflow - 2.6.4,2.7.2,2.8.1,2.9.0;tensorflow-cpu - 2.6.4,2.7.2,2.8.1,2.9.0;tensorflow-gpu - 2.6.4,2.7.2,2.8.1,2.9.0</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_priority | cve medium detected in tensorflow whl autoclosed cve medium severity vulnerability vulnerable library tensorflow whl tensorflow is an open source machine learning framework for everyone library home page a href path to dependency file requirements txt path to vulnerable library requirements txt dependency hierarchy x tensorflow whl vulnerable library found in head commit a href found in base branch main vulnerability details tensorflow is an open source platform for machine learning prior to versions and the implementation of tf ragged constant does not fully validate the input arguments this results in a denial of service by consuming all available memory versions and contain a patch for this issue publish date url a href cvss score details base score metrics exploitability metrics attack vector local attack complexity low privileges required low user interaction none scope unchanged impact metrics confidentiality impact none integrity impact none availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution tensorflow tensorflow cpu tensorflow gpu step up your open source security game with mend | 0 |
79,301 | 22,699,494,771 | IssuesEvent | 2022-07-05 09:22:01 | scipy/scipy | https://api.github.com/repos/scipy/scipy | closed | Running 1.5.2 on Apple M1 / ARM64 | Build issues query | When running an AWS SAM Lambda locally on my Mac M1, I receive the following error:
`Unable to import module '...': /var/task/scipy/linalg/_fblas.cpython-37m-x86_64-linux-gnu.so: ELF load command address/offset not properly aligned`
Our workaround [on intel] is to pin `scipy==1.5.2` (see https://github.com/scipy/scipy/issues/12975#issuecomment-1065013153).
But a binary for that version is not available anywhere as far as I can see. So
(a) Do you know where I can find such a binary?
(b) Failing that, does anyone have robust steps to build from source under ARM?
(c) Is there another workaround?
Many thanks in particular to @rgommers for your assistance here! :)
| 1.0 | Running 1.5.2 on Apple M1 / ARM64 - When running an AWS SAM Lambda locally on my Mac M1, I receive the following error:
`Unable to import module '...': /var/task/scipy/linalg/_fblas.cpython-37m-x86_64-linux-gnu.so: ELF load command address/offset not properly aligned`
Our workaround [on intel] is to pin `scipy==1.5.2` (see https://github.com/scipy/scipy/issues/12975#issuecomment-1065013153).
But a binary for that version is not available anywhere as far as I can see. So
(a) Do you know where I can find such a binary?
(b) Failing that, does anyone have robust steps to build from source under ARM?
(c) Is there another workaround?
Many thanks in particular to @rgommers for your assistance here! :)
| non_priority | running on apple when running an aws sam lambda locally on my mac i receive the following error unable to import module var task scipy linalg fblas cpython linux gnu so elf load command address offset not properly aligned our workaround is to pin scipy see but a binary for that version is not available anywhere as far as i can see so a do you know where i can find such a binary b failing that does anyone have robust steps to build from source under arm c is there another workaround many thanks in particular to rgommers for your assistance here | 0 |
16,532 | 9,438,197,229 | IssuesEvent | 2019-04-13 21:17:24 | bocadilloproject/bocadillo | https://api.github.com/repos/bocadilloproject/bocadillo | closed | Go all-async | breaking community docs enhancement performance | **Is your feature request related to a problem? Please describe.**
<!-- A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] -->
Supporting both sync and async syntax introduced a lot of complexity to the framework code.
The main benefit we get out of that is lower barrier to entry — people not familiar with async can just jump right in and write `def my_view()`.
But Bocadillo is an async framework after all — if they're looking for a synchronous framework, they can just use a WSGI framework like Flask. Plus I think it'd be nice to spread the async love by *teaching* stuff to people.
**Describe the solution you'd like**
<!-- A clear and concise description of what you want to happen. -->
a. Remove support for synchronous syntax in:
- Views
- Error handlers
- Hooks
b. Keep synchronous syntax where it makes sense (e.g. `templates.render_string()`).
c. Be *very* explicit that using Bocadillo requires to use the `async` syntax, but:
- No prerequisite necessary — take users by the hand by showing them the basic syntax.
- Show async equivalent of some common synchronous code (e.g. function definition, function calls, loops, context managers).
- Let them know they do *not* need to know anything about `asyncio` or how async works under the hood — it's just about *syntax*.
- Explain what async enables and how the benefits can be potentially ruined (e.g. running long blocking operations, e.g. querying a database with a synchronous library).
- Explain common patterns, e.g.:
- Dealing with CPU-bound operations (threadpool execution)
- Wrapping a sync function in an async one
- Give useful resources to learn more about async if they want to.
**Describe alternatives you've considered**
<!-- A clear and concise description of any alternative solutions or features you've considered. -->
**Implementation ideas**
<!-- If you already have ideas on how to implement this feature, please list them here. -->
- Remove async support from listed components.
- Update the docs with the above modifications.
**Additional context**
<!-- Add any other context or screenshots about the feature request here. -->
Part of the spring cleanup: #236 | True | Go all-async - **Is your feature request related to a problem? Please describe.**
<!-- A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] -->
Supporting both sync and async syntax introduced a lot of complexity to the framework code.
The main benefit we get out of that is lower barrier to entry — people not familiar with async can just jump right in and write `def my_view()`.
But Bocadillo is an async framework after all — if they're looking for a synchronous framework, they can just use a WSGI framework like Flask. Plus I think it'd be nice to spread the async love by *teaching* stuff to people.
**Describe the solution you'd like**
<!-- A clear and concise description of what you want to happen. -->
a. Remove support for synchronous syntax in:
- Views
- Error handlers
- Hooks
b. Keep synchronous syntax where it makes sense (e.g. `templates.render_string()`).
c. Be *very* explicit that using Bocadillo requires to use the `async` syntax, but:
- No prerequisite necessary — take users by the hand by showing them the basic syntax.
- Show async equivalent of some common synchronous code (e.g. function definition, function calls, loops, context managers).
- Let them know they do *not* need to know anything about `asyncio` or how async works under the hood — it's just about *syntax*.
- Explain what async enables and how the benefits can be potentially ruined (e.g. running long blocking operations, e.g. querying a database with a synchronous library).
- Explain common patterns, e.g.:
- Dealing with CPU-bound operations (threadpool execution)
- Wrapping a sync function in an async one
- Give useful resources to learn more about async if they want to.
**Describe alternatives you've considered**
<!-- A clear and concise description of any alternative solutions or features you've considered. -->
**Implementation ideas**
<!-- If you already have ideas on how to implement this feature, please list them here. -->
- Remove async support from listed components.
- Update the docs with the above modifications.
**Additional context**
<!-- Add any other context or screenshots about the feature request here. -->
Part of the spring cleanup: #236 | non_priority | go all async is your feature request related to a problem please describe supporting both sync and async syntax introduced a lot of complexity to the framework code the main benefit we get out of that is lower barrier to entry — people not familiar with async can just jump right in and write def my view but bocadillo is an async framework after all — if they re looking for a synchronous framework they can just use a wsgi framework like flask plus i think it d be nice to spread the async love by teaching stuff to people describe the solution you d like a remove support for synchronous syntax in views error handlers hooks b keep synchronous syntax where it makes sense e g templates render string c be very explicit that using bocadillo requires to use the async syntax but no prerequisite necessary — take users by the hand by showing them the basic syntax show async equivalent of some common synchronous code e g function definition function calls loops context managers let them know they do not need to know anything about asyncio or how async works under the hood — it s just about syntax explain what async enables and how the benefits can be potentially ruined e g running long blocking operations e g querying a database with a synchronous library explain common patterns e g dealing with cpu bound operations threadpool execution wrapping a sync function in an async one give useful resources to learn more about async if they want to describe alternatives you ve considered implementation ideas remove async support from listed components update the docs with the above modifications additional context part of the spring cleanup | 0 |
97,434 | 28,290,616,585 | IssuesEvent | 2023-04-09 06:26:23 | ClickHouse/ClickHouse | https://api.github.com/repos/ClickHouse/ClickHouse | closed | build : ld.lld: error: unable to find library -lgcc_eh | build st-need-info | > Make sure that `git diff` result is empty and you've just pulled fresh master. Try cleaning up cmake cache. Just in case, official build instructions are published here: https://clickhouse.com/docs/en/development/build/
**Operating system**
ld.lld: error: unable to find library -lgcc_eh
> OS kind or distribution, specific version/release, non-standard kernel if any. If you are trying to build inside virtual machine, please mention it too.
OS：Linux open 5.15.0-58-generic #64-Ubuntu SMP Thu Jan 5 11:43:13 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
Ubuntu22.04
flind gcc_eh :
roott@linux:/root/gcc-11.3.0/build$ sudo find /usr/lib -name "libgcc*"
/usr/lib/gcc/x86_64-linux-gnu/11/libgcc_s.so
/usr/lib/gcc/x86_64-linux-gnu/11/libgcc_eh.a
/usr/lib/gcc/x86_64-linux-gnu/11/libgcc.a
/usr/lib/x86_64-linux-gnu/libgccpp.so.1
/usr/lib/x86_64-linux-gnu/libgcc_eh.a
/usr/lib/x86_64-linux-gnu/libgccpp.so.1.4.1
/usr/lib/x86_64-linux-gnu/libgcc_s.so.1
/usr/lib/libgcc_eh.a
**Cmake version**
3.24.2
-DCMAKE_CXX_COMPILER_LAUNCHER=ccache
-DCMAKE_BUILD_TYPE=Debug
-GNinja
-DENABLE_CLICKHOUSE_ALL=OFF
-DENABLE_CLICKHOUSE_SERVER=ON
-DENABLE_CLICKHOUSE_CLIENT=ON
-DENABLE_LIBRARIES=OFF
-DENABLE_UTILS=OFF
-DENABLE_TESTS=ON
-DUSE_ROCKSDB=ON
-DENABLE_ROCKSDB=ON
-DENABLE_JEMALLOC=ON
**Ninja version**
1.10.1
**Compiler name and version**
master -> remotes/origin/23.1
**Full cmake and/or ninja output**
/software/ide/clion/clion-2022.3.2/bin/cmake/linux/x64/bin/cmake --build /opensource/cpp-source/ClickHouse/build --target all -j 10
[0/2] Re-checking globbed directories...
[1/4007] Linking CXX executable contrib/llvm-project/llvm/bin/llvm-tblgen
FAILED: contrib/llvm-project/llvm/bin/llvm-tblgen
: && /usr/bin/clang++ --target=x86_64-linux-gnu --sysroot=/opensource/cpp-source/ClickHouse/cmake/linux/../../contrib/sysroot/linux-x86_64/x86_64-linux-gnu/libc --gcc-toolchain=/opensource/cpp-source/ClickHouse/cmake/linux/../../contrib/sysroot/linux-x86_64 -std=c++20 -fdiagnostics-color=always -Xclang -fuse-ctor-homing -fsized-deallocation -gdwarf-aranges -pipe -mssse3 -msse4.1 -msse4.2 -mpclmul -mpopcnt -fasynchronous-unwind-tables -falign-functions=32 -mbranches-within-32B-boundaries -fdiagnostics-absolute-paths -fstrict-vtable-pointers -fexperimental-new-pass-manager -w -fvisibility-inlines-hidden -Werror=date-time -Werror=unguarded-availability-new -Wall -Wextra -Wno-unused-parameter -Wwrite-strings -Wcast-qual -Wmissing-field-initializers -pedantic -Wno-long-long -Wc++98-compat-extra-semi -Wimplicit-fallthrough -Wcovered-switch-default -Wno-class-memaccess -Wno-noexcept-type -Wnon-virtual-dtor -Wdelete-non-virtual-dtor -Wsuggest-override -Wstring-conversion -Wmisleading-indentation -fdiagnostics-color -g -O0 -g -gdwarf-4 -D_LIBCPP_DEBUG=0 --gcc-toolchain=/opensource/cpp-source/ClickHouse/cmake/linux/../../contrib/sysroot/linux-x86_64 --ld-path=/opensource/cpp-source/ClickHouse/build/ld.lld -rdynamic -Wl,--gdb-index -Wl,--build-id=sha1 -no-pie -Wl,-no-pie -fno-pie -Xlinker --no-undefined contrib/llvm-project/llvm/utils/TableGen/CMakeFiles/llvm-tblgen.dir/AsmMatcherEmitter.cpp.o contrib/llvm-project/llvm/utils/TableGen/CMakeFiles/llvm-tblgen.dir/AsmWriterEmitter.cpp.o contrib/llvm-project/llvm/utils/TableGen/CMakeFiles/llvm-tblgen.dir/AsmWriterInst.cpp.o contrib/llvm-project/llvm/utils/TableGen/CMakeFiles/llvm-tblgen.dir/Attributes.cpp.o contrib/llvm-project/llvm/utils/TableGen/CMakeFiles/llvm-tblgen.dir/CallingConvEmitter.cpp.o contrib/llvm-project/llvm/utils/TableGen/CMakeFiles/llvm-tblgen.dir/CodeEmitterGen.cpp.o contrib/llvm-project/llvm/utils/TableGen/CMakeFiles/llvm-tblgen.dir/CodeGenDAGPatterns.cpp.o contrib/llvm-project/llvm/utils/TableGen/CMakeFiles/llvm-tblgen.dir/CodeGenHwModes.cpp.o contrib/llvm-project/llvm/utils/TableGen/CMakeFiles/llvm-tblgen.dir/CodeGenInstruction.cpp.o contrib/llvm-project/llvm/utils/TableGen/CMakeFiles/llvm-tblgen.dir/CodeGenMapTable.cpp.o contrib/llvm-project/llvm/utils/TableGen/CMakeFiles/llvm-tblgen.dir/CodeGenRegisters.cpp.o contrib/llvm-project/llvm/utils/TableGen/CMakeFiles/llvm-tblgen.dir/CodeGenSchedule.cpp.o contrib/llvm-project/llvm/utils/TableGen/CMakeFiles/llvm-tblgen.dir/CodeGenTarget.cpp.o contrib/llvm-project/llvm/utils/TableGen/CMakeFiles/llvm-tblgen.dir/DAGISelEmitter.cpp.o contrib/llvm-project/llvm/utils/TableGen/CMakeFiles/llvm-tblgen.dir/DAGISelMatcherEmitter.cpp.o contrib/llvm-project/llvm/utils/TableGen/CMakeFiles/llvm-tblgen.dir/DAGISelMatcherGen.cpp.o contrib/llvm-project/llvm/utils/TableGen/CMakeFiles/llvm-tblgen.dir/DAGISelMatcherOpt.cpp.o contrib/llvm-project/llvm/utils/TableGen/CMakeFiles/llvm-tblgen.dir/DAGISelMatcher.cpp.o contrib/llvm-project/llvm/utils/TableGen/CMakeFiles/llvm-tblgen.dir/DecoderEmitter.cpp.o contrib/llvm-project/llvm/utils/TableGen/CMakeFiles/llvm-tblgen.dir/DFAEmitter.cpp.o contrib/llvm-project/llvm/utils/TableGen/CMakeFiles/llvm-tblgen.dir/DFAPacketizerEmitter.cpp.o contrib/llvm-project/llvm/utils/TableGen/CMakeFiles/llvm-tblgen.dir/DirectiveEmitter.cpp.o contrib/llvm-project/llvm/utils/TableGen/CMakeFiles/llvm-tblgen.dir/DisassemblerEmitter.cpp.o contrib/llvm-project/llvm/utils/TableGen/CMakeFiles/llvm-tblgen.dir/DXILEmitter.cpp.o contrib/llvm-project/llvm/utils/TableGen/CMakeFiles/llvm-tblgen.dir/ExegesisEmitter.cpp.o contrib/llvm-project/llvm/utils/TableGen/CMakeFiles/llvm-tblgen.dir/FastISelEmitter.cpp.o contrib/llvm-project/llvm/utils/TableGen/CMakeFiles/llvm-tblgen.dir/GICombinerEmitter.cpp.o contrib/llvm-project/llvm/utils/TableGen/CMakeFiles/llvm-tblgen.dir/GlobalISelEmitter.cpp.o contrib/llvm-project/llvm/utils/TableGen/CMakeFiles/llvm-tblgen.dir/InfoByHwMode.cpp.o contrib/llvm-project/llvm/utils/TableGen/CMakeFiles/llvm-tblgen.dir/InstrInfoEmitter.cpp.o contrib/llvm-project/llvm/utils/TableGen/CMakeFiles/llvm-tblgen.dir/InstrDocsEmitter.cpp.o contrib/llvm-project/llvm/utils/TableGen/CMakeFiles/llvm-tblgen.dir/IntrinsicEmitter.cpp.o contrib/llvm-project/llvm/utils/TableGen/CMakeFiles/llvm-tblgen.dir/OptEmitter.cpp.o contrib/llvm-project/llvm/utils/TableGen/CMakeFiles/llvm-tblgen.dir/OptParserEmitter.cpp.o contrib/llvm-project/llvm/utils/TableGen/CMakeFiles/llvm-tblgen.dir/OptRSTEmitter.cpp.o contrib/llvm-project/llvm/utils/TableGen/CMakeFiles/llvm-tblgen.dir/PredicateExpander.cpp.o contrib/llvm-project/llvm/utils/TableGen/CMakeFiles/llvm-tblgen.dir/PseudoLoweringEmitter.cpp.o contrib/llvm-project/llvm/utils/TableGen/CMakeFiles/llvm-tblgen.dir/CompressInstEmitter.cpp.o contrib/llvm-project/llvm/utils/TableGen/CMakeFiles/llvm-tblgen.dir/RegisterBankEmitter.cpp.o contrib/llvm-project/llvm/utils/TableGen/CMakeFiles/llvm-tblgen.dir/RegisterInfoEmitter.cpp.o contrib/llvm-project/llvm/utils/TableGen/CMakeFiles/llvm-tblgen.dir/SDNodeProperties.cpp.o contrib/llvm-project/llvm/utils/TableGen/CMakeFiles/llvm-tblgen.dir/SearchableTableEmitter.cpp.o contrib/llvm-project/llvm/utils/TableGen/CMakeFiles/llvm-tblgen.dir/SubtargetEmitter.cpp.o contrib/llvm-project/llvm/utils/TableGen/CMakeFiles/llvm-tblgen.dir/SubtargetFeatureInfo.cpp.o contrib/llvm-project/llvm/utils/TableGen/CMakeFiles/llvm-tblgen.dir/TableGen.cpp.o contrib/llvm-project/llvm/utils/TableGen/CMakeFiles/llvm-tblgen.dir/Types.cpp.o contrib/llvm-project/llvm/utils/TableGen/CMakeFiles/llvm-tblgen.dir/VarLenCodeEmitterGen.cpp.o contrib/llvm-project/llvm/utils/TableGen/CMakeFiles/llvm-tblgen.dir/X86DisassemblerTables.cpp.o contrib/llvm-project/llvm/utils/TableGen/CMakeFiles/llvm-tblgen.dir/X86EVEX2VEXTablesEmitter.cpp.o contrib/llvm-project/llvm/utils/TableGen/CMakeFiles/llvm-tblgen.dir/X86FoldTablesEmitter.cpp.o contrib/llvm-project/llvm/utils/TableGen/CMakeFiles/llvm-tblgen.dir/X86MnemonicTables.cpp.o contrib/llvm-project/llvm/utils/TableGen/CMakeFiles/llvm-tblgen.dir/X86ModRMFilters.cpp.o contrib/llvm-project/llvm/utils/TableGen/CMakeFiles/llvm-tblgen.dir/X86RecognizableInstr.cpp.o contrib/llvm-project/llvm/utils/TableGen/CMakeFiles/llvm-tblgen.dir/WebAssemblyDisassemblerEmitter.cpp.o contrib/llvm-project/llvm/utils/TableGen/CMakeFiles/llvm-tblgen.dir/CTagsEmitter.cpp.o -o contrib/llvm-project/llvm/bin/llvm-tblgen contrib/llvm-project/llvm/lib/libLLVMSupportd.a contrib/llvm-project/llvm/lib/libLLVMTableGend.a contrib/llvm-project/llvm/lib/libLLVMTableGenGlobalISeld.a contrib/llvm-project/llvm/lib/libLLVMTableGend.a contrib/llvm-project/llvm/lib/libLLVMSupportd.a contrib/llvm-project/llvm/lib/libLLVMDemangled.a base/glibc-compatibility/libglibc-compatibilityd.a base/glibc-compatibility/memcpy/libmemcpyd.a base/glibc-compatibility/libglibc-compatibilityd.a base/glibc-compatibility/memcpy/libmemcpyd.a -Wl,--start-group contrib/libcxx-cmake/libcxxd.a contrib/libcxxabi-cmake/libcxxabid.a -lgcc_eh -Wl,--end-group -nodefaultlibs /usr/lib/llvm-14/lib/clang/14.0.0/lib/linux/libclang_rt.builtins-x86_64.a -lc -lm -lrt -lpthread -ldl && :
ld.lld: error: unable to find library -lgcc_eh
clang: error: linker command failed with exit code 1 (use -v to see invocation)
[10/4007] Building CXX object contrib/llvm-project/llvm/lib/MC/CMakeFiles/LLVMMC.dir/MCELFStreamer.cpp.o
ninja: build stopped: subcommand failed.
| 1.0 | build : ld.lld: error: unable to find library -lgcc_eh - > Make sure that `git diff` result is empty and you've just pulled fresh master. Try cleaning up cmake cache. Just in case, official build instructions are published here: https://clickhouse.com/docs/en/development/build/
**Operating system**
ld.lld: error: unable to find library -lgcc_eh
> OS kind or distribution, specific version/release, non-standard kernel if any. If you are trying to build inside virtual machine, please mention it too.
OS：Linux open 5.15.0-58-generic #64-Ubuntu SMP Thu Jan 5 11:43:13 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
Ubuntu22.04
flind gcc_eh :
roott@linux:/root/gcc-11.3.0/build$ sudo find /usr/lib -name "libgcc*"
/usr/lib/gcc/x86_64-linux-gnu/11/libgcc_s.so
/usr/lib/gcc/x86_64-linux-gnu/11/libgcc_eh.a
/usr/lib/gcc/x86_64-linux-gnu/11/libgcc.a
/usr/lib/x86_64-linux-gnu/libgccpp.so.1
/usr/lib/x86_64-linux-gnu/libgcc_eh.a
/usr/lib/x86_64-linux-gnu/libgccpp.so.1.4.1
/usr/lib/x86_64-linux-gnu/libgcc_s.so.1
/usr/lib/libgcc_eh.a
**Cmake version**
3.24.2
-DCMAKE_CXX_COMPILER_LAUNCHER=ccache
-DCMAKE_BUILD_TYPE=Debug
-GNinja
-DENABLE_CLICKHOUSE_ALL=OFF
-DENABLE_CLICKHOUSE_SERVER=ON
-DENABLE_CLICKHOUSE_CLIENT=ON
-DENABLE_LIBRARIES=OFF
-DENABLE_UTILS=OFF
-DENABLE_TESTS=ON
-DUSE_ROCKSDB=ON
-DENABLE_ROCKSDB=ON
-DENABLE_JEMALLOC=ON
**Ninja version**
1.10.1
**Compiler name and version**
master -> remotes/origin/23.1
**Full cmake and/or ninja output**
/software/ide/clion/clion-2022.3.2/bin/cmake/linux/x64/bin/cmake --build /opensource/cpp-source/ClickHouse/build --target all -j 10
[0/2] Re-checking globbed directories...
[1/4007] Linking CXX executable contrib/llvm-project/llvm/bin/llvm-tblgen
FAILED: contrib/llvm-project/llvm/bin/llvm-tblgen
: && /usr/bin/clang++ --target=x86_64-linux-gnu --sysroot=/opensource/cpp-source/ClickHouse/cmake/linux/../../contrib/sysroot/linux-x86_64/x86_64-linux-gnu/libc --gcc-toolchain=/opensource/cpp-source/ClickHouse/cmake/linux/../../contrib/sysroot/linux-x86_64 -std=c++20 -fdiagnostics-color=always -Xclang -fuse-ctor-homing -fsized-deallocation -gdwarf-aranges -pipe -mssse3 -msse4.1 -msse4.2 -mpclmul -mpopcnt -fasynchronous-unwind-tables -falign-functions=32 -mbranches-within-32B-boundaries -fdiagnostics-absolute-paths -fstrict-vtable-pointers -fexperimental-new-pass-manager -w -fvisibility-inlines-hidden -Werror=date-time -Werror=unguarded-availability-new -Wall -Wextra -Wno-unused-parameter -Wwrite-strings -Wcast-qual -Wmissing-field-initializers -pedantic -Wno-long-long -Wc++98-compat-extra-semi -Wimplicit-fallthrough -Wcovered-switch-default -Wno-class-memaccess -Wno-noexcept-type -Wnon-virtual-dtor -Wdelete-non-virtual-dtor -Wsuggest-override -Wstring-conversion -Wmisleading-indentation -fdiagnostics-color -g -O0 -g -gdwarf-4 -D_LIBCPP_DEBUG=0 --gcc-toolchain=/opensource/cpp-source/ClickHouse/cmake/linux/../../contrib/sysroot/linux-x86_64 --ld-path=/opensource/cpp-source/ClickHouse/build/ld.lld -rdynamic -Wl,--gdb-index -Wl,--build-id=sha1 -no-pie -Wl,-no-pie -fno-pie -Xlinker --no-undefined contrib/llvm-project/llvm/utils/TableGen/CMakeFiles/llvm-tblgen.dir/AsmMatcherEmitter.cpp.o contrib/llvm-project/llvm/utils/TableGen/CMakeFiles/llvm-tblgen.dir/AsmWriterEmitter.cpp.o contrib/llvm-project/llvm/utils/TableGen/CMakeFiles/llvm-tblgen.dir/AsmWriterInst.cpp.o contrib/llvm-project/llvm/utils/TableGen/CMakeFiles/llvm-tblgen.dir/Attributes.cpp.o contrib/llvm-project/llvm/utils/TableGen/CMakeFiles/llvm-tblgen.dir/CallingConvEmitter.cpp.o contrib/llvm-project/llvm/utils/TableGen/CMakeFiles/llvm-tblgen.dir/CodeEmitterGen.cpp.o contrib/llvm-project/llvm/utils/TableGen/CMakeFiles/llvm-tblgen.dir/CodeGenDAGPatterns.cpp.o contrib/llvm-project/llvm/utils/TableGen/CMakeFiles/llvm-tblgen.dir/CodeGenHwModes.cpp.o contrib/llvm-project/llvm/utils/TableGen/CMakeFiles/llvm-tblgen.dir/CodeGenInstruction.cpp.o contrib/llvm-project/llvm/utils/TableGen/CMakeFiles/llvm-tblgen.dir/CodeGenMapTable.cpp.o contrib/llvm-project/llvm/utils/TableGen/CMakeFiles/llvm-tblgen.dir/CodeGenRegisters.cpp.o contrib/llvm-project/llvm/utils/TableGen/CMakeFiles/llvm-tblgen.dir/CodeGenSchedule.cpp.o contrib/llvm-project/llvm/utils/TableGen/CMakeFiles/llvm-tblgen.dir/CodeGenTarget.cpp.o contrib/llvm-project/llvm/utils/TableGen/CMakeFiles/llvm-tblgen.dir/DAGISelEmitter.cpp.o contrib/llvm-project/llvm/utils/TableGen/CMakeFiles/llvm-tblgen.dir/DAGISelMatcherEmitter.cpp.o contrib/llvm-project/llvm/utils/TableGen/CMakeFiles/llvm-tblgen.dir/DAGISelMatcherGen.cpp.o contrib/llvm-project/llvm/utils/TableGen/CMakeFiles/llvm-tblgen.dir/DAGISelMatcherOpt.cpp.o contrib/llvm-project/llvm/utils/TableGen/CMakeFiles/llvm-tblgen.dir/DAGISelMatcher.cpp.o contrib/llvm-project/llvm/utils/TableGen/CMakeFiles/llvm-tblgen.dir/DecoderEmitter.cpp.o contrib/llvm-project/llvm/utils/TableGen/CMakeFiles/llvm-tblgen.dir/DFAEmitter.cpp.o contrib/llvm-project/llvm/utils/TableGen/CMakeFiles/llvm-tblgen.dir/DFAPacketizerEmitter.cpp.o contrib/llvm-project/llvm/utils/TableGen/CMakeFiles/llvm-tblgen.dir/DirectiveEmitter.cpp.o contrib/llvm-project/llvm/utils/TableGen/CMakeFiles/llvm-tblgen.dir/DisassemblerEmitter.cpp.o contrib/llvm-project/llvm/utils/TableGen/CMakeFiles/llvm-tblgen.dir/DXILEmitter.cpp.o contrib/llvm-project/llvm/utils/TableGen/CMakeFiles/llvm-tblgen.dir/ExegesisEmitter.cpp.o contrib/llvm-project/llvm/utils/TableGen/CMakeFiles/llvm-tblgen.dir/FastISelEmitter.cpp.o contrib/llvm-project/llvm/utils/TableGen/CMakeFiles/llvm-tblgen.dir/GICombinerEmitter.cpp.o contrib/llvm-project/llvm/utils/TableGen/CMakeFiles/llvm-tblgen.dir/GlobalISelEmitter.cpp.o contrib/llvm-project/llvm/utils/TableGen/CMakeFiles/llvm-tblgen.dir/InfoByHwMode.cpp.o contrib/llvm-project/llvm/utils/TableGen/CMakeFiles/llvm-tblgen.dir/InstrInfoEmitter.cpp.o contrib/llvm-project/llvm/utils/TableGen/CMakeFiles/llvm-tblgen.dir/InstrDocsEmitter.cpp.o contrib/llvm-project/llvm/utils/TableGen/CMakeFiles/llvm-tblgen.dir/IntrinsicEmitter.cpp.o contrib/llvm-project/llvm/utils/TableGen/CMakeFiles/llvm-tblgen.dir/OptEmitter.cpp.o contrib/llvm-project/llvm/utils/TableGen/CMakeFiles/llvm-tblgen.dir/OptParserEmitter.cpp.o contrib/llvm-project/llvm/utils/TableGen/CMakeFiles/llvm-tblgen.dir/OptRSTEmitter.cpp.o contrib/llvm-project/llvm/utils/TableGen/CMakeFiles/llvm-tblgen.dir/PredicateExpander.cpp.o contrib/llvm-project/llvm/utils/TableGen/CMakeFiles/llvm-tblgen.dir/PseudoLoweringEmitter.cpp.o contrib/llvm-project/llvm/utils/TableGen/CMakeFiles/llvm-tblgen.dir/CompressInstEmitter.cpp.o contrib/llvm-project/llvm/utils/TableGen/CMakeFiles/llvm-tblgen.dir/RegisterBankEmitter.cpp.o contrib/llvm-project/llvm/utils/TableGen/CMakeFiles/llvm-tblgen.dir/RegisterInfoEmitter.cpp.o contrib/llvm-project/llvm/utils/TableGen/CMakeFiles/llvm-tblgen.dir/SDNodeProperties.cpp.o contrib/llvm-project/llvm/utils/TableGen/CMakeFiles/llvm-tblgen.dir/SearchableTableEmitter.cpp.o contrib/llvm-project/llvm/utils/TableGen/CMakeFiles/llvm-tblgen.dir/SubtargetEmitter.cpp.o contrib/llvm-project/llvm/utils/TableGen/CMakeFiles/llvm-tblgen.dir/SubtargetFeatureInfo.cpp.o contrib/llvm-project/llvm/utils/TableGen/CMakeFiles/llvm-tblgen.dir/TableGen.cpp.o contrib/llvm-project/llvm/utils/TableGen/CMakeFiles/llvm-tblgen.dir/Types.cpp.o contrib/llvm-project/llvm/utils/TableGen/CMakeFiles/llvm-tblgen.dir/VarLenCodeEmitterGen.cpp.o contrib/llvm-project/llvm/utils/TableGen/CMakeFiles/llvm-tblgen.dir/X86DisassemblerTables.cpp.o contrib/llvm-project/llvm/utils/TableGen/CMakeFiles/llvm-tblgen.dir/X86EVEX2VEXTablesEmitter.cpp.o contrib/llvm-project/llvm/utils/TableGen/CMakeFiles/llvm-tblgen.dir/X86FoldTablesEmitter.cpp.o contrib/llvm-project/llvm/utils/TableGen/CMakeFiles/llvm-tblgen.dir/X86MnemonicTables.cpp.o contrib/llvm-project/llvm/utils/TableGen/CMakeFiles/llvm-tblgen.dir/X86ModRMFilters.cpp.o contrib/llvm-project/llvm/utils/TableGen/CMakeFiles/llvm-tblgen.dir/X86RecognizableInstr.cpp.o contrib/llvm-project/llvm/utils/TableGen/CMakeFiles/llvm-tblgen.dir/WebAssemblyDisassemblerEmitter.cpp.o contrib/llvm-project/llvm/utils/TableGen/CMakeFiles/llvm-tblgen.dir/CTagsEmitter.cpp.o -o contrib/llvm-project/llvm/bin/llvm-tblgen contrib/llvm-project/llvm/lib/libLLVMSupportd.a contrib/llvm-project/llvm/lib/libLLVMTableGend.a contrib/llvm-project/llvm/lib/libLLVMTableGenGlobalISeld.a contrib/llvm-project/llvm/lib/libLLVMTableGend.a contrib/llvm-project/llvm/lib/libLLVMSupportd.a contrib/llvm-project/llvm/lib/libLLVMDemangled.a base/glibc-compatibility/libglibc-compatibilityd.a base/glibc-compatibility/memcpy/libmemcpyd.a base/glibc-compatibility/libglibc-compatibilityd.a base/glibc-compatibility/memcpy/libmemcpyd.a -Wl,--start-group contrib/libcxx-cmake/libcxxd.a contrib/libcxxabi-cmake/libcxxabid.a -lgcc_eh -Wl,--end-group -nodefaultlibs /usr/lib/llvm-14/lib/clang/14.0.0/lib/linux/libclang_rt.builtins-x86_64.a -lc -lm -lrt -lpthread -ldl && :
ld.lld: error: unable to find library -lgcc_eh
clang: error: linker command failed with exit code 1 (use -v to see invocation)
[10/4007] Building CXX object contrib/llvm-project/llvm/lib/MC/CMakeFiles/LLVMMC.dir/MCELFStreamer.cpp.o
ninja: build stopped: subcommand failed.
| non_priority | build ld lld error unable to find library lgcc eh make sure that git diff result is empty and you ve just pulled fresh master try cleaning up cmake cache just in case official build instructions are published here operating system ld lld error unable to find library lgcc eh os kind or distribution specific version release non standard kernel if any if you are trying to build inside virtual machine please mention it too os：linux open generic ubuntu smp thu jan utc gnu linux flind gcc eh roott linux root gcc build sudo find usr lib name libgcc usr lib gcc linux gnu libgcc s so usr lib gcc linux gnu libgcc eh a usr lib gcc linux gnu libgcc a usr lib linux gnu libgccpp so usr lib linux gnu libgcc eh a usr lib linux gnu libgccpp so usr lib linux gnu libgcc s so usr lib libgcc eh a cmake version dcmake cxx compiler launcher ccache dcmake build type debug gninja denable clickhouse all off denable clickhouse server on denable clickhouse client on denable libraries off denable utils off denable tests on duse rocksdb on denable rocksdb on denable jemalloc on ninja version compiler name and version master remotes origin full cmake and or ninja output software ide clion clion bin cmake linux bin cmake build opensource cpp source clickhouse build target all j re checking globbed directories linking cxx executable contrib llvm project llvm bin llvm tblgen failed contrib llvm project llvm bin llvm tblgen usr bin clang target linux gnu sysroot opensource cpp source clickhouse cmake linux contrib sysroot linux linux gnu libc gcc toolchain opensource cpp source clickhouse cmake linux contrib sysroot linux std c fdiagnostics color always xclang fuse ctor homing fsized deallocation gdwarf aranges pipe mpclmul mpopcnt fasynchronous unwind tables falign functions mbranches within boundaries fdiagnostics absolute paths fstrict vtable pointers fexperimental new pass manager w fvisibility inlines hidden werror date time werror unguarded availability new wall wextra wno unused parameter wwrite strings wcast qual wmissing field initializers pedantic wno long long wc compat extra semi wimplicit fallthrough wcovered switch default wno class memaccess wno noexcept type wnon virtual dtor wdelete non virtual dtor wsuggest override wstring conversion wmisleading indentation fdiagnostics color g g gdwarf d libcpp debug gcc toolchain opensource cpp source clickhouse cmake linux contrib sysroot linux ld path opensource cpp source clickhouse build ld lld rdynamic wl gdb index wl build id no pie wl no pie fno pie xlinker no undefined contrib llvm project llvm utils tablegen cmakefiles llvm tblgen dir asmmatcheremitter cpp o contrib llvm project llvm utils tablegen cmakefiles llvm tblgen dir asmwriteremitter cpp o contrib llvm project llvm utils tablegen cmakefiles llvm tblgen dir asmwriterinst cpp o contrib llvm project llvm utils tablegen cmakefiles llvm tblgen dir attributes cpp o contrib llvm project llvm utils tablegen cmakefiles llvm tblgen dir callingconvemitter cpp o contrib llvm project llvm utils tablegen cmakefiles llvm tblgen dir codeemittergen cpp o contrib llvm project llvm utils tablegen cmakefiles llvm tblgen dir codegendagpatterns cpp o contrib llvm project llvm utils tablegen cmakefiles llvm tblgen dir codegenhwmodes cpp o contrib llvm project llvm utils tablegen cmakefiles llvm tblgen dir codegeninstruction cpp o contrib llvm project llvm utils tablegen cmakefiles llvm tblgen dir codegenmaptable cpp o contrib llvm project llvm utils tablegen cmakefiles llvm tblgen dir codegenregisters cpp o contrib llvm project llvm utils tablegen cmakefiles llvm tblgen dir codegenschedule cpp o contrib llvm project llvm utils tablegen cmakefiles llvm tblgen dir codegentarget cpp o contrib llvm project llvm utils tablegen cmakefiles llvm tblgen dir dagiselemitter cpp o contrib llvm project llvm utils tablegen cmakefiles llvm tblgen dir dagiselmatcheremitter cpp o contrib llvm project llvm utils tablegen cmakefiles llvm tblgen dir dagiselmatchergen cpp o contrib llvm project llvm utils tablegen cmakefiles llvm tblgen dir dagiselmatcheropt cpp o contrib llvm project llvm utils tablegen cmakefiles llvm tblgen dir dagiselmatcher cpp o contrib llvm project llvm utils tablegen cmakefiles llvm tblgen dir decoderemitter cpp o contrib llvm project llvm utils tablegen cmakefiles llvm tblgen dir dfaemitter cpp o contrib llvm project llvm utils tablegen cmakefiles llvm tblgen dir dfapacketizeremitter cpp o contrib llvm project llvm utils tablegen cmakefiles llvm tblgen dir directiveemitter cpp o contrib llvm project llvm utils tablegen cmakefiles llvm tblgen dir disassembleremitter cpp o contrib llvm project llvm utils tablegen cmakefiles llvm tblgen dir dxilemitter cpp o contrib llvm project llvm utils tablegen cmakefiles llvm tblgen dir exegesisemitter cpp o contrib llvm project llvm utils tablegen cmakefiles llvm tblgen dir fastiselemitter cpp o contrib llvm project llvm utils tablegen cmakefiles llvm tblgen dir gicombineremitter cpp o contrib llvm project llvm utils tablegen cmakefiles llvm tblgen dir globaliselemitter cpp o contrib llvm project llvm utils tablegen cmakefiles llvm tblgen dir infobyhwmode cpp o contrib llvm project llvm utils tablegen cmakefiles llvm tblgen dir instrinfoemitter cpp o contrib llvm project llvm utils tablegen cmakefiles llvm tblgen dir instrdocsemitter cpp o contrib llvm project llvm utils tablegen cmakefiles llvm tblgen dir intrinsicemitter cpp o contrib llvm project llvm utils tablegen cmakefiles llvm tblgen dir optemitter cpp o contrib llvm project llvm utils tablegen cmakefiles llvm tblgen dir optparseremitter cpp o contrib llvm project llvm utils tablegen cmakefiles llvm tblgen dir optrstemitter cpp o contrib llvm project llvm utils tablegen cmakefiles llvm tblgen dir predicateexpander cpp o contrib llvm project llvm utils tablegen cmakefiles llvm tblgen dir pseudoloweringemitter cpp o contrib llvm project llvm utils tablegen cmakefiles llvm tblgen dir compressinstemitter cpp o contrib llvm project llvm utils tablegen cmakefiles llvm tblgen dir registerbankemitter cpp o contrib llvm project llvm utils tablegen cmakefiles llvm tblgen dir registerinfoemitter cpp o contrib llvm project llvm utils tablegen cmakefiles llvm tblgen dir sdnodeproperties cpp o contrib llvm project llvm utils tablegen cmakefiles llvm tblgen dir searchabletableemitter cpp o contrib llvm project llvm utils tablegen cmakefiles llvm tblgen dir subtargetemitter cpp o contrib llvm project llvm utils tablegen cmakefiles llvm tblgen dir subtargetfeatureinfo cpp o contrib llvm project llvm utils tablegen cmakefiles llvm tblgen dir tablegen cpp o contrib llvm project llvm utils tablegen cmakefiles llvm tblgen dir types cpp o contrib llvm project llvm utils tablegen cmakefiles llvm tblgen dir varlencodeemittergen cpp o contrib llvm project llvm utils tablegen cmakefiles llvm tblgen dir cpp o contrib llvm project llvm utils tablegen cmakefiles llvm tblgen dir cpp o contrib llvm project llvm utils tablegen cmakefiles llvm tblgen dir cpp o contrib llvm project llvm utils tablegen cmakefiles llvm tblgen dir cpp o contrib llvm project llvm utils tablegen cmakefiles llvm tblgen dir cpp o contrib llvm project llvm utils tablegen cmakefiles llvm tblgen dir cpp o contrib llvm project llvm utils tablegen cmakefiles llvm tblgen dir webassemblydisassembleremitter cpp o contrib llvm project llvm utils tablegen cmakefiles llvm tblgen dir ctagsemitter cpp o o contrib llvm project llvm bin llvm tblgen contrib llvm project llvm lib libllvmsupportd a contrib llvm project llvm lib libllvmtablegend a contrib llvm project llvm lib libllvmtablegenglobaliseld a contrib llvm project llvm lib libllvmtablegend a contrib llvm project llvm lib libllvmsupportd a contrib llvm project llvm lib libllvmdemangled a base glibc compatibility libglibc compatibilityd a base glibc compatibility memcpy libmemcpyd a base glibc compatibility libglibc compatibilityd a base glibc compatibility memcpy libmemcpyd a wl start group contrib libcxx cmake libcxxd a contrib libcxxabi cmake libcxxabid a lgcc eh wl end group nodefaultlibs usr lib llvm lib clang lib linux libclang rt builtins a lc lm lrt lpthread ldl ld lld error unable to find library lgcc eh clang error linker command failed with exit code use v to see invocation building cxx object contrib llvm project llvm lib mc cmakefiles llvmmc dir mcelfstreamer cpp o ninja build stopped subcommand failed | 0 |
43,998 | 13,046,219,626 | IssuesEvent | 2020-07-29 08:38:22 | orhanarifoglu/bitti | https://api.github.com/repos/orhanarifoglu/bitti | opened | CVE-2019-13116 (High) detected in commons-collections-3.2.jar | security vulnerability | ## CVE-2019-13116 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>commons-collections-3.2.jar</b></p></summary>
<p>Types that extend and augment the Java Collections Framework.</p>
<p>Library home page: <a href="http://jakarta.apache.org/commons/collections/">http://jakarta.apache.org/commons/collections/</a></p>
<p>Path to vulnerable library: _depth_0/bitti/build/distributions/gradleproject2/gradleproject2/lib/commons-collections-3.2.jar,canner/.gradle/caches/modules-2/files-2.1/commons-collections/commons-collections/3.2/f951934aa5ae5a88d7e6dfaa6d32307d834a88be/commons-collections-3.2.jar</p>
<p>
Dependency Hierarchy:
- :x: **commons-collections-3.2.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/orhanarifoglu/bitti/commit/b9de9df64013494e4cad4e932f22f2c53e6e45c0">b9de9df64013494e4cad4e932f22f2c53e6e45c0</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
The MuleSoft Mule Community Edition runtime engine before 3.8 allows remote attackers to execute arbitrary code because of Java Deserialization, related to Apache Commons Collections
<p>Publish Date: 2019-10-16
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-13116>CVE-2019-13116</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>9.8</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-13116">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-13116</a></p>
<p>Release Date: 2019-10-16</p>
<p>Fix Resolution: commons-collections:commons-collections:3.2.2</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | CVE-2019-13116 (High) detected in commons-collections-3.2.jar - ## CVE-2019-13116 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>commons-collections-3.2.jar</b></p></summary>
<p>Types that extend and augment the Java Collections Framework.</p>
<p>Library home page: <a href="http://jakarta.apache.org/commons/collections/">http://jakarta.apache.org/commons/collections/</a></p>
<p>Path to vulnerable library: _depth_0/bitti/build/distributions/gradleproject2/gradleproject2/lib/commons-collections-3.2.jar,canner/.gradle/caches/modules-2/files-2.1/commons-collections/commons-collections/3.2/f951934aa5ae5a88d7e6dfaa6d32307d834a88be/commons-collections-3.2.jar</p>
<p>
Dependency Hierarchy:
- :x: **commons-collections-3.2.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/orhanarifoglu/bitti/commit/b9de9df64013494e4cad4e932f22f2c53e6e45c0">b9de9df64013494e4cad4e932f22f2c53e6e45c0</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
The MuleSoft Mule Community Edition runtime engine before 3.8 allows remote attackers to execute arbitrary code because of Java Deserialization, related to Apache Commons Collections
<p>Publish Date: 2019-10-16
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-13116>CVE-2019-13116</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>9.8</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-13116">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-13116</a></p>
<p>Release Date: 2019-10-16</p>
<p>Fix Resolution: commons-collections:commons-collections:3.2.2</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_priority | cve high detected in commons collections jar cve high severity vulnerability vulnerable library commons collections jar types that extend and augment the java collections framework library home page a href path to vulnerable library depth bitti build distributions lib commons collections jar canner gradle caches modules files commons collections commons collections commons collections jar dependency hierarchy x commons collections jar vulnerable library found in head commit a href vulnerability details the mulesoft mule community edition runtime engine before allows remote attackers to execute arbitrary code because of java deserialization related to apache commons collections publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact high integrity impact high availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution commons collections commons collections step up your open source security game with whitesource | 0 |
71,845 | 30,921,674,390 | IssuesEvent | 2023-08-06 01:18:11 | Zahlungsmittel/Zahlungsmittel | https://api.github.com/repos/Zahlungsmittel/Zahlungsmittel | opened | [CLOSED] 💥 [DevOps] Update Cypress | devops test service: e2e end-to-end imported | <a href="https://github.com/mahula"><img src="https://avatars.githubusercontent.com/u/3883288?v=4" align="left" width="96" height="96" hspace="10"></img></a> **Issue by [mahula](https://github.com/mahula)**
_Tuesday Jun 13, 2023 at 13:04 GMT_
_Originally opened as https://github.com/gradido/gradido/issues/3055_
----
## 💥 DevOps ticket
Update cypress relevant topics and packages.
- The experimentalSessionAndOrigin configuration option was removed in Cypress version 12
You can safely remove this option from your config.
Kann entfernt werden (siehe https://docs.cypress.io/guides/references/migration-guide)
- Packages updaten
- "@badeball/cypress-cucumber-preprocessor": "^12.0.0",
- "@cypress/browserify-preprocessor": "^3.0.2",
- "cypress": "^12.7.0",
- "eslint-plugin-cypress": "^2.12.1"
-
### Todo
- [x] remove experimentalSessionAndOrigin configuration option ([it is a general availabitiy since Cypress version 12](https://docs.cypress.io/guides/references/migration-guide))
- [x] update packages `cypress`, `@badeball/cypress-cucumber-preprocessor`, `@cypress/browserify-preprocessor`, `eslint-plugin-cypress`
| 1.0 | [CLOSED] 💥 [DevOps] Update Cypress - <a href="https://github.com/mahula"><img src="https://avatars.githubusercontent.com/u/3883288?v=4" align="left" width="96" height="96" hspace="10"></img></a> **Issue by [mahula](https://github.com/mahula)**
_Tuesday Jun 13, 2023 at 13:04 GMT_
_Originally opened as https://github.com/gradido/gradido/issues/3055_
----
## 💥 DevOps ticket
Update cypress relevant topics and packages.
- The experimentalSessionAndOrigin configuration option was removed in Cypress version 12
You can safely remove this option from your config.
Kann entfernt werden (siehe https://docs.cypress.io/guides/references/migration-guide)
- Packages updaten
- "@badeball/cypress-cucumber-preprocessor": "^12.0.0",
- "@cypress/browserify-preprocessor": "^3.0.2",
- "cypress": "^12.7.0",
- "eslint-plugin-cypress": "^2.12.1"
-
### Todo
- [x] remove experimentalSessionAndOrigin configuration option ([it is a general availabitiy since Cypress version 12](https://docs.cypress.io/guides/references/migration-guide))
- [x] update packages `cypress`, `@badeball/cypress-cucumber-preprocessor`, `@cypress/browserify-preprocessor`, `eslint-plugin-cypress`
| non_priority | 💥 update cypress issue by tuesday jun at gmt originally opened as 💥 devops ticket update cypress relevant topics and packages the experimentalsessionandorigin configuration option was removed in cypress version you can safely remove this option from your config kann entfernt werden siehe packages updaten badeball cypress cucumber preprocessor cypress browserify preprocessor cypress eslint plugin cypress todo remove experimentalsessionandorigin configuration option update packages cypress badeball cypress cucumber preprocessor cypress browserify preprocessor eslint plugin cypress | 0 |
8,790 | 8,407,142,586 | IssuesEvent | 2018-10-11 20:02:21 | blockchain-signaling-system/bloss-dashboard | https://api.github.com/repos/blockchain-signaling-system/bloss-dashboard | opened | Service Status Component | enhancement service-status-component | ## Intro
This component directly interacts with the `service-status-feature` offered by `bloss-node` and retrieves its information from there.
### TODO
**The `Service Status` Component should**
- [ ] ... **display the statuses of the services running** on the respective controller (i.e.`geth.service`, `bloss.service`, `ipfs.service` and the connection / status to the local `influxdb`)
- [ ] ... keep it simple and **only display two different statuses**: **INACTIVE (DEAD)** or **ACTIVE (RUNNING)**
- [ ] ... **manage state of the statuses with Vuex**, which means implementation of meaningful mutations / actions and state variables.
### Nice-to-have
- [ ] ... enable **control** **(start/stop/restart)** over the statuses of the services running on the respective controller (i.e.`geth.service`, `bloss.service`, `ipfs.service` and `influxdb.service`)
- [ ] ... display a "loading" status, however this can become very tricky and hacky due to the relayed nature of the information retrieval via `bloss-node`
| 1.0 | Service Status Component - ## Intro
This component directly interacts with the `service-status-feature` offered by `bloss-node` and retrieves its information from there.
### TODO
**The `Service Status` Component should**
- [ ] ... **display the statuses of the services running** on the respective controller (i.e.`geth.service`, `bloss.service`, `ipfs.service` and the connection / status to the local `influxdb`)
- [ ] ... keep it simple and **only display two different statuses**: **INACTIVE (DEAD)** or **ACTIVE (RUNNING)**
- [ ] ... **manage state of the statuses with Vuex**, which means implementation of meaningful mutations / actions and state variables.
### Nice-to-have
- [ ] ... enable **control** **(start/stop/restart)** over the statuses of the services running on the respective controller (i.e.`geth.service`, `bloss.service`, `ipfs.service` and `influxdb.service`)
- [ ] ... display a "loading" status, however this can become very tricky and hacky due to the relayed nature of the information retrieval via `bloss-node`
| non_priority | service status component intro this component directly interacts with the service status feature offered by bloss node and retrieves its information from there todo the service status component should display the statuses of the services running on the respective controller i e geth service bloss service ipfs service and the connection status to the local influxdb keep it simple and only display two different statuses inactive dead or active running manage state of the statuses with vuex which means implementation of meaningful mutations actions and state variables nice to have enable control start stop restart over the statuses of the services running on the respective controller i e geth service bloss service ipfs service and influxdb service display a loading status however this can become very tricky and hacky due to the relayed nature of the information retrieval via bloss node | 0 |
21,202 | 3,874,217,213 | IssuesEvent | 2016-04-11 19:43:40 | realm/realm-js | https://api.github.com/repos/realm/realm-js | closed | Test object with optional properties can be created without optional properties missing | S:P2 Backlog T:Test | Don't see a test for this. | 1.0 | Test object with optional properties can be created without optional properties missing - Don't see a test for this. | non_priority | test object with optional properties can be created without optional properties missing don t see a test for this | 0 |
68,304 | 8,248,032,833 | IssuesEvent | 2018-09-11 17:12:56 | atom/github | https://api.github.com/repos/atom/github | opened | Multi-File Diff | design | We're accumulating several place where we have a need to present a diff that spans multiple files in a single view, a la the ["files changed" tab on a GitHub pull request](https://github.com/atom/github/pull/1685/files):
* The CommitPaneItem proposed in #1655
* The "Files Changed" tab within the IssueishPaneItem tabs proposed by #1656, which @annthurium has started putting together in #1684
We can't really start building this until the FilePatchItem is revamped in #1512, but let's start talking about what the design for a multi-file diff view should look like, so we can hit the ground running once it lands 🐎 .
Essentially what we need to design is a re-usable React component that:
* Shows the list of files contained in a multi-file diff.
* Shows the combined diff, with some kind of prominent divider between each file's portions of the diff.
* Makes it easy to jump quickly to a specific file you care about, or back to the file list to get to another file.
* Makes it apparent which file a part of a long diff belongs to, so you don't lose track of what file you're looking at if its diff is larger than you can fit in the pane at once.
/cc @annthurium, @kuychaco, and @simurai for input on what this should look like and how it should behave :smile: | 1.0 | Multi-File Diff - We're accumulating several place where we have a need to present a diff that spans multiple files in a single view, a la the ["files changed" tab on a GitHub pull request](https://github.com/atom/github/pull/1685/files):
* The CommitPaneItem proposed in #1655
* The "Files Changed" tab within the IssueishPaneItem tabs proposed by #1656, which @annthurium has started putting together in #1684
We can't really start building this until the FilePatchItem is revamped in #1512, but let's start talking about what the design for a multi-file diff view should look like, so we can hit the ground running once it lands 🐎 .
Essentially what we need to design is a re-usable React component that:
* Shows the list of files contained in a multi-file diff.
* Shows the combined diff, with some kind of prominent divider between each file's portions of the diff.
* Makes it easy to jump quickly to a specific file you care about, or back to the file list to get to another file.
* Makes it apparent which file a part of a long diff belongs to, so you don't lose track of what file you're looking at if its diff is larger than you can fit in the pane at once.
/cc @annthurium, @kuychaco, and @simurai for input on what this should look like and how it should behave :smile: | non_priority | multi file diff we re accumulating several place where we have a need to present a diff that spans multiple files in a single view a la the the commitpaneitem proposed in the files changed tab within the issueishpaneitem tabs proposed by which annthurium has started putting together in we can t really start building this until the filepatchitem is revamped in but let s start talking about what the design for a multi file diff view should look like so we can hit the ground running once it lands 🐎 essentially what we need to design is a re usable react component that shows the list of files contained in a multi file diff shows the combined diff with some kind of prominent divider between each file s portions of the diff makes it easy to jump quickly to a specific file you care about or back to the file list to get to another file makes it apparent which file a part of a long diff belongs to so you don t lose track of what file you re looking at if its diff is larger than you can fit in the pane at once cc annthurium kuychaco and simurai for input on what this should look like and how it should behave smile | 0 |
9,723 | 7,795,427,146 | IssuesEvent | 2018-06-08 08:04:34 | whatwg/html | https://api.github.com/repos/whatwg/html | opened | Should "familiar with" use same origin or same origin-domain? | interop security/privacy topic: navigation | https://bugzilla.mozilla.org/show_bug.cgi?id=1459671 was filed against Firefox because it uses a same origin check. Per investigation from @bzbarsky it appears that other browsers use same origin-domain. This means that you can target a cross-origin `<iframe>`'s name if you are same origin-domain with it.
It seems better if this concept does not depend on `document.domain`.
@whatwg/security interested in fixing this in your respective implementations?
Either way, we should probably also add a test for this as I don't think it's covered. | True | Should "familiar with" use same origin or same origin-domain? - https://bugzilla.mozilla.org/show_bug.cgi?id=1459671 was filed against Firefox because it uses a same origin check. Per investigation from @bzbarsky it appears that other browsers use same origin-domain. This means that you can target a cross-origin `<iframe>`'s name if you are same origin-domain with it.
It seems better if this concept does not depend on `document.domain`.
@whatwg/security interested in fixing this in your respective implementations?
Either way, we should probably also add a test for this as I don't think it's covered. | non_priority | should familiar with use same origin or same origin domain was filed against firefox because it uses a same origin check per investigation from bzbarsky it appears that other browsers use same origin domain this means that you can target a cross origin s name if you are same origin domain with it it seems better if this concept does not depend on document domain whatwg security interested in fixing this in your respective implementations either way we should probably also add a test for this as i don t think it s covered | 0 |
13,203 | 5,312,348,980 | IssuesEvent | 2017-02-13 08:44:17 | archlinuxcn/repo | https://api.github.com/repos/archlinuxcn/repo | closed | Require rebuild all kernels with gcc6.3 | rebuild | Archlinux have upgraded gcc to 6.3. But all the kernels in this mirror was built by gcc 6.2. It caused some dkms such as nivdia cannot be built correctly. So please rebuild it. | 1.0 | Require rebuild all kernels with gcc6.3 - Archlinux have upgraded gcc to 6.3. But all the kernels in this mirror was built by gcc 6.2. It caused some dkms such as nivdia cannot be built correctly. So please rebuild it. | non_priority | require rebuild all kernels with archlinux have upgraded gcc to but all the kernels in this mirror was built by gcc it caused some dkms such as nivdia cannot be built correctly so please rebuild it | 0 |
125,956 | 17,861,744,392 | IssuesEvent | 2021-09-06 02:19:32 | Galaxy-Software-Service/WebGoat | https://api.github.com/repos/Galaxy-Software-Service/WebGoat | opened | CVE-2018-10237 (Medium) detected in guava-18.0.jar | security vulnerability | ## CVE-2018-10237 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>guava-18.0.jar</b></p></summary>
<p>Guava is a suite of core and expanded libraries that include
utility classes, google's collections, io classes, and much
much more.
Guava has only one code dependency - javax.annotation,
per the JSR-305 spec.</p>
<p>Library home page: <a href="http://code.google.com/p/guava-libraries">http://code.google.com/p/guava-libraries</a></p>
<p>Path to dependency file: WebGoat/webgoat-integration-tests/pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/com/google/guava/guava/18.0/guava-18.0.jar,m2/repository/com/google/guava/guava/18.0/guava-18.0.jar</p>
<p>
Dependency Hierarchy:
- :x: **guava-18.0.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/Galaxy-Software-Service/WebGoat/commit/12040d57fd51ffa0b6407f8b4e9cc04e47656d2d">12040d57fd51ffa0b6407f8b4e9cc04e47656d2d</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
Unbounded memory allocation in Google Guava 11.0 through 24.x before 24.1.1 allows remote attackers to conduct denial of service attacks against servers that depend on this library and deserialize attacker-provided data, because the AtomicDoubleArray class (when serialized with Java serialization) and the CompoundOrdering class (when serialized with GWT serialization) perform eager allocation without appropriate checks on what a client has sent and whether the data size is reasonable.
<p>Publish Date: 2018-04-26
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-10237>CVE-2018-10237</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.9</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://nvd.nist.gov/vuln/detail/CVE-2018-10237">https://nvd.nist.gov/vuln/detail/CVE-2018-10237</a></p>
<p>Release Date: 2018-04-26</p>
<p>Fix Resolution: 24.1.1-jre, 24.1.1-android</p>
</p>
</details>
<p></p>
***
:rescue_worker_helmet: Automatic Remediation is available for this issue
<!-- <REMEDIATE>{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"Java","groupId":"com.google.guava","packageName":"guava","packageVersion":"18.0","packageFilePaths":["/webgoat-integration-tests/pom.xml","/webwolf/pom.xml"],"isTransitiveDependency":false,"dependencyTree":"com.google.guava:guava:18.0","isMinimumFixVersionAvailable":true,"minimumFixVersion":"24.1.1-jre, 24.1.1-android"}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2018-10237","vulnerabilityDetails":"Unbounded memory allocation in Google Guava 11.0 through 24.x before 24.1.1 allows remote attackers to conduct denial of service attacks against servers that depend on this library and deserialize attacker-provided data, because the AtomicDoubleArray class (when serialized with Java serialization) and the CompoundOrdering class (when serialized with GWT serialization) perform eager allocation without appropriate checks on what a client has sent and whether the data size is reasonable.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-10237","cvss3Severity":"medium","cvss3Score":"5.9","cvss3Metrics":{"A":"High","AC":"High","PR":"None","S":"Unchanged","C":"None","UI":"None","AV":"Network","I":"None"},"extraData":{}}</REMEDIATE> --> | True | CVE-2018-10237 (Medium) detected in guava-18.0.jar - ## CVE-2018-10237 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>guava-18.0.jar</b></p></summary>
<p>Guava is a suite of core and expanded libraries that include
utility classes, google's collections, io classes, and much
much more.
Guava has only one code dependency - javax.annotation,
per the JSR-305 spec.</p>
<p>Library home page: <a href="http://code.google.com/p/guava-libraries">http://code.google.com/p/guava-libraries</a></p>
<p>Path to dependency file: WebGoat/webgoat-integration-tests/pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/com/google/guava/guava/18.0/guava-18.0.jar,m2/repository/com/google/guava/guava/18.0/guava-18.0.jar</p>
<p>
Dependency Hierarchy:
- :x: **guava-18.0.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/Galaxy-Software-Service/WebGoat/commit/12040d57fd51ffa0b6407f8b4e9cc04e47656d2d">12040d57fd51ffa0b6407f8b4e9cc04e47656d2d</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
Unbounded memory allocation in Google Guava 11.0 through 24.x before 24.1.1 allows remote attackers to conduct denial of service attacks against servers that depend on this library and deserialize attacker-provided data, because the AtomicDoubleArray class (when serialized with Java serialization) and the CompoundOrdering class (when serialized with GWT serialization) perform eager allocation without appropriate checks on what a client has sent and whether the data size is reasonable.
<p>Publish Date: 2018-04-26
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-10237>CVE-2018-10237</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.9</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://nvd.nist.gov/vuln/detail/CVE-2018-10237">https://nvd.nist.gov/vuln/detail/CVE-2018-10237</a></p>
<p>Release Date: 2018-04-26</p>
<p>Fix Resolution: 24.1.1-jre, 24.1.1-android</p>
</p>
</details>
<p></p>
***
:rescue_worker_helmet: Automatic Remediation is available for this issue
<!-- <REMEDIATE>{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"Java","groupId":"com.google.guava","packageName":"guava","packageVersion":"18.0","packageFilePaths":["/webgoat-integration-tests/pom.xml","/webwolf/pom.xml"],"isTransitiveDependency":false,"dependencyTree":"com.google.guava:guava:18.0","isMinimumFixVersionAvailable":true,"minimumFixVersion":"24.1.1-jre, 24.1.1-android"}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2018-10237","vulnerabilityDetails":"Unbounded memory allocation in Google Guava 11.0 through 24.x before 24.1.1 allows remote attackers to conduct denial of service attacks against servers that depend on this library and deserialize attacker-provided data, because the AtomicDoubleArray class (when serialized with Java serialization) and the CompoundOrdering class (when serialized with GWT serialization) perform eager allocation without appropriate checks on what a client has sent and whether the data size is reasonable.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-10237","cvss3Severity":"medium","cvss3Score":"5.9","cvss3Metrics":{"A":"High","AC":"High","PR":"None","S":"Unchanged","C":"None","UI":"None","AV":"Network","I":"None"},"extraData":{}}</REMEDIATE> --> | non_priority | cve medium detected in guava jar cve medium severity vulnerability vulnerable library guava jar guava is a suite of core and expanded libraries that include utility classes google s collections io classes and much much more guava has only one code dependency javax annotation per the jsr spec library home page a href path to dependency file webgoat webgoat integration tests pom xml path to vulnerable library home wss scanner repository com google guava guava guava jar repository com google guava guava guava jar dependency hierarchy x guava jar vulnerable library found in head commit a href found in base branch master vulnerability details unbounded memory allocation in google guava through x before allows remote attackers to conduct denial of service attacks against servers that depend on this library and deserialize attacker provided data because the atomicdoublearray class when serialized with java serialization and the compoundordering class when serialized with gwt serialization perform eager allocation without appropriate checks on what a client has sent and whether the data size is reasonable publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity high privileges required none user interaction none scope unchanged impact metrics confidentiality impact none integrity impact none availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution jre android rescue worker helmet automatic remediation is available for this issue isopenpronvulnerability true ispackagebased true isdefaultbranch true packages istransitivedependency false dependencytree com google guava guava isminimumfixversionavailable true minimumfixversion jre android basebranches vulnerabilityidentifier cve vulnerabilitydetails unbounded memory allocation in google guava through x before allows remote attackers to conduct denial of service attacks against servers that depend on this library and deserialize attacker provided data because the atomicdoublearray class when serialized with java serialization and the compoundordering class when serialized with gwt serialization perform eager allocation without appropriate checks on what a client has sent and whether the data size is reasonable vulnerabilityurl | 0 |
282,828 | 24,498,965,623 | IssuesEvent | 2022-10-10 11:09:39 | apache/shardingsphere | https://api.github.com/repos/apache/shardingsphere | opened | [DistSQL] Add SQL parser test case for `AddShardingHintTableValueStatement` | in: test feature: DistSQL hacktoberfest |
### Background
`ADD SHARDING HINT DATABASE_VALUE xx = yy` is a syntax in [DistSQL RAL](https://shardingsphere.apache.org/document/current/en/user-manual/shardingsphere-proxy/distsql/syntax/ral/), when `ShardingSphereSQLParserEngine` receives this SQL text, it parses it as `AddShardingHintTableValueStatement`. Now we need to add a test case for this parsing process to assert that the parsing is correct.
### Aim
Add SQL parser test case for `AddShardingHintTableValueStatement`.
- Affected files:
- SQLParserTestCases (**modify**)
- test/parser/src/main/resources/case/ral/updatable.xml (**modify**)
- test/parser/src/main/resources/sql/supported/ral/updatable.xml (**modify**)
- test/parser/src/main/java/org/apache/shardingsphere/test/sql/parser/parameterized/jaxb/cases/domain/statement/distsql/ral/updatable/AddShardingHintTableValueStatementTestCase.java (**create**)
- test/parser/src/main/java/org/apache/shardingsphere/test/sql/parser/parameterized/asserts/statement/distsql/ral/impl/updatable/AddShardingHintTableValueStatementAssert.java (**create**)
- UpdatableRALStatementAssert (**modify**)
- After all, execute `DistSQLParserParameterizedTest#assertDistSQL()` for validation
### Basic Qualifications
- Java
- Maven
### Example FYI
- ImportDatabaseConfigurationStatement
- ImportDatabaseConfigurationStatementTestCase
- ImportDatabaseConfigurationStatementAssert
- SQLParserTestCases
- search for "import-database-config" | 1.0 | [DistSQL] Add SQL parser test case for `AddShardingHintTableValueStatement` -
### Background
`ADD SHARDING HINT DATABASE_VALUE xx = yy` is a syntax in [DistSQL RAL](https://shardingsphere.apache.org/document/current/en/user-manual/shardingsphere-proxy/distsql/syntax/ral/), when `ShardingSphereSQLParserEngine` receives this SQL text, it parses it as `AddShardingHintTableValueStatement`. Now we need to add a test case for this parsing process to assert that the parsing is correct.
### Aim
Add SQL parser test case for `AddShardingHintTableValueStatement`.
- Affected files:
- SQLParserTestCases (**modify**)
- test/parser/src/main/resources/case/ral/updatable.xml (**modify**)
- test/parser/src/main/resources/sql/supported/ral/updatable.xml (**modify**)
- test/parser/src/main/java/org/apache/shardingsphere/test/sql/parser/parameterized/jaxb/cases/domain/statement/distsql/ral/updatable/AddShardingHintTableValueStatementTestCase.java (**create**)
- test/parser/src/main/java/org/apache/shardingsphere/test/sql/parser/parameterized/asserts/statement/distsql/ral/impl/updatable/AddShardingHintTableValueStatementAssert.java (**create**)
- UpdatableRALStatementAssert (**modify**)
- After all, execute `DistSQLParserParameterizedTest#assertDistSQL()` for validation
### Basic Qualifications
- Java
- Maven
### Example FYI
- ImportDatabaseConfigurationStatement
- ImportDatabaseConfigurationStatementTestCase
- ImportDatabaseConfigurationStatementAssert
- SQLParserTestCases
- search for "import-database-config" | non_priority | add sql parser test case for addshardinghinttablevaluestatement background add sharding hint database value xx yy is a syntax in when shardingspheresqlparserengine receives this sql text it parses it as addshardinghinttablevaluestatement now we need to add a test case for this parsing process to assert that the parsing is correct aim add sql parser test case for addshardinghinttablevaluestatement affected files sqlparsertestcases modify test parser src main resources case ral updatable xml modify test parser src main resources sql supported ral updatable xml modify test parser src main java org apache shardingsphere test sql parser parameterized jaxb cases domain statement distsql ral updatable addshardinghinttablevaluestatementtestcase java create test parser src main java org apache shardingsphere test sql parser parameterized asserts statement distsql ral impl updatable addshardinghinttablevaluestatementassert java create updatableralstatementassert modify after all execute distsqlparserparameterizedtest assertdistsql for validation basic qualifications java maven example fyi importdatabaseconfigurationstatement importdatabaseconfigurationstatementtestcase importdatabaseconfigurationstatementassert sqlparsertestcases search for import database config | 0 |
12,431 | 7,878,063,074 | IssuesEvent | 2018-06-26 09:07:30 | symfony/symfony | https://api.github.com/repos/symfony/symfony | closed | Symfony 3.3 unsusable with windows ubuntu bash | Bug Performance Status: Needs Review | | Q | A
| ---------------- | -----
| Bug report? | yes
| Feature request? | no
| BC Break report? | no
| RFC? | no
| Symfony version | 3.3.2
Hello,
Since I can use the bash ubuntu on windows, I have been using it instead of a vm. Few months ago I started a tiny sf project, sf 3.2, no problem at all (same for 3.1), everything worked fine.
But today, I created a new symfony 3.3 project, and it was unsuable, the page took 30 sec to load (after I put app_dev.php). I even re-installed my bash, clean install, still the same (but no problem with symfony 3.2). I tried on my vm, it was all good, so the problem is only on the ubuntu bash for windows :( | True | Symfony 3.3 unsusable with windows ubuntu bash - | Q | A
| ---------------- | -----
| Bug report? | yes
| Feature request? | no
| BC Break report? | no
| RFC? | no
| Symfony version | 3.3.2
Hello,
Since I can use the bash ubuntu on windows, I have been using it instead of a vm. Few months ago I started a tiny sf project, sf 3.2, no problem at all (same for 3.1), everything worked fine.
But today, I created a new symfony 3.3 project, and it was unsuable, the page took 30 sec to load (after I put app_dev.php). I even re-installed my bash, clean install, still the same (but no problem with symfony 3.2). I tried on my vm, it was all good, so the problem is only on the ubuntu bash for windows :( | non_priority | symfony unsusable with windows ubuntu bash q a bug report yes feature request no bc break report no rfc no symfony version hello since i can use the bash ubuntu on windows i have been using it instead of a vm few months ago i started a tiny sf project sf no problem at all same for everything worked fine but today i created a new symfony project and it was unsuable the page took sec to load after i put app dev php i even re installed my bash clean install still the same but no problem with symfony i tried on my vm it was all good so the problem is only on the ubuntu bash for windows | 0 |
62,641 | 12,228,946,314 | IssuesEvent | 2020-05-03 21:40:34 | unisonweb/unison | https://api.github.com/repos/unisonweb/unison | closed | Should be possible to view any hash, even if it's not in the current branch | codebase-manager | Might let us figure out stuff like #400 and is just generally useful.
Idea for implementation - could just `mappend` all the `PrettyPrintEnv` for all branches, then print it using that combined environment.
There's probably a more efficient implementation with a better codebase repo format than the one we have now. | 1.0 | Should be possible to view any hash, even if it's not in the current branch - Might let us figure out stuff like #400 and is just generally useful.
Idea for implementation - could just `mappend` all the `PrettyPrintEnv` for all branches, then print it using that combined environment.
There's probably a more efficient implementation with a better codebase repo format than the one we have now. | non_priority | should be possible to view any hash even if it s not in the current branch might let us figure out stuff like and is just generally useful idea for implementation could just mappend all the prettyprintenv for all branches then print it using that combined environment there s probably a more efficient implementation with a better codebase repo format than the one we have now | 0 |
31,516 | 5,956,886,990 | IssuesEvent | 2017-05-28 20:58:12 | nwjs-community/nw-builder | https://api.github.com/repos/nwjs-community/nw-builder | closed | Add a README to every directory | documentation help-wanted | So it's easier for people to contribute. It doesn't have to contain too much but a minimum of one line giving a summary of the directory | 1.0 | Add a README to every directory - So it's easier for people to contribute. It doesn't have to contain too much but a minimum of one line giving a summary of the directory | non_priority | add a readme to every directory so it s easier for people to contribute it doesn t have to contain too much but a minimum of one line giving a summary of the directory | 0 |
247,158 | 26,688,700,404 | IssuesEvent | 2023-01-27 01:16:53 | turkdevops/grafana | https://api.github.com/repos/turkdevops/grafana | closed | CVE-2021-33196 (High) detected in github.com/klauspost/Compress-v1.4.1 - autoclosed | security vulnerability | ## CVE-2021-33196 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>github.com/klauspost/Compress-v1.4.1</b></p></summary>
<p>Optimized Go Compression Packages</p>
<p>Library home page: <a href="https://proxy.golang.org/github.com/klauspost/compress/@v/v1.4.1.zip">https://proxy.golang.org/github.com/klauspost/compress/@v/v1.4.1.zip</a></p>
<p>
Dependency Hierarchy:
- github.com/go-macaron/gzip-v0.0.0-20160222043647-cad1c6580a07 (Root Library)
- :x: **github.com/klauspost/Compress-v1.4.1** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/turkdevops/grafana/commit/a1c271764655c7e3ff81126d5929b8dda6170bf4">a1c271764655c7e3ff81126d5929b8dda6170bf4</a></p>
<p>Found in base branch: <b>datasource-meta</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
In archive/zip in Go before 1.15.13 and 1.16.x before 1.16.5, a crafted file count (in an archive's header) can cause a NewReader or OpenReader panic.
<p>Publish Date: 2021-08-02
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2021-33196>CVE-2021-33196</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://nvd.nist.gov/vuln/detail/CVE-2021-33196">https://nvd.nist.gov/vuln/detail/CVE-2021-33196</a></p>
<p>Release Date: 2021-08-02</p>
<p>Fix Resolution: golang-1.7 - 1.7.4-2+deb9u4;golang-1.8 - 1.8.1-1+deb9u4;golang-1.15 - 1.15.9-4</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | CVE-2021-33196 (High) detected in github.com/klauspost/Compress-v1.4.1 - autoclosed - ## CVE-2021-33196 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>github.com/klauspost/Compress-v1.4.1</b></p></summary>
<p>Optimized Go Compression Packages</p>
<p>Library home page: <a href="https://proxy.golang.org/github.com/klauspost/compress/@v/v1.4.1.zip">https://proxy.golang.org/github.com/klauspost/compress/@v/v1.4.1.zip</a></p>
<p>
Dependency Hierarchy:
- github.com/go-macaron/gzip-v0.0.0-20160222043647-cad1c6580a07 (Root Library)
- :x: **github.com/klauspost/Compress-v1.4.1** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/turkdevops/grafana/commit/a1c271764655c7e3ff81126d5929b8dda6170bf4">a1c271764655c7e3ff81126d5929b8dda6170bf4</a></p>
<p>Found in base branch: <b>datasource-meta</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
In archive/zip in Go before 1.15.13 and 1.16.x before 1.16.5, a crafted file count (in an archive's header) can cause a NewReader or OpenReader panic.
<p>Publish Date: 2021-08-02
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2021-33196>CVE-2021-33196</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://nvd.nist.gov/vuln/detail/CVE-2021-33196">https://nvd.nist.gov/vuln/detail/CVE-2021-33196</a></p>
<p>Release Date: 2021-08-02</p>
<p>Fix Resolution: golang-1.7 - 1.7.4-2+deb9u4;golang-1.8 - 1.8.1-1+deb9u4;golang-1.15 - 1.15.9-4</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_priority | cve high detected in github com klauspost compress autoclosed cve high severity vulnerability vulnerable library github com klauspost compress optimized go compression packages library home page a href dependency hierarchy github com go macaron gzip root library x github com klauspost compress vulnerable library found in head commit a href found in base branch datasource meta vulnerability details in archive zip in go before and x before a crafted file count in an archive s header can cause a newreader or openreader panic publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact none integrity impact none availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution golang golang golang step up your open source security game with mend | 0 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.