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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
33,296 | 4,821,300,337 | IssuesEvent | 2016-11-05 08:16:33 | Ivan-Sergeyev/slae_alg_comp | https://api.github.com/repos/Ivan-Sergeyev/slae_alg_comp | closed | tests for linear_algebra.h | test | implement more tests for [linear_algebra.h](linear_algebra.h) in [linear_algebra_test.h](linear_algebra_test.h)
the tests should cover everything -- all functions, all cases | 1.0 | tests for linear_algebra.h - implement more tests for [linear_algebra.h](linear_algebra.h) in [linear_algebra_test.h](linear_algebra_test.h)
the tests should cover everything -- all functions, all cases | non_priority | tests for linear algebra h implement more tests for linear algebra h in linear algebra test h the tests should cover everything all functions all cases | 0 |
274,422 | 30,022,118,104 | IssuesEvent | 2023-06-27 01:00:26 | KDWSS/checkov | https://api.github.com/repos/KDWSS/checkov | closed | golang.org/x/net-v0.0.0-20210415231046-e915ea6b2b7d: 7 vulnerabilities (highest severity is: 7.5) - autoclosed | Mend: dependency security vulnerability | <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>golang.org/x/net-v0.0.0-20210415231046-e915ea6b2b7d</b></p></summary>
<p></p>
<p>Library home page: <a href="https://proxy.golang.org/golang.org/x/net/@v/v0.0.0-20210415231046-e915ea6b2b7d.zip">https://proxy.golang.org/golang.org/x/net/@v/v0.0.0-20210415231046-e915ea6b2b7d.zip</a></p>
<p>
<p>Found in HEAD commit: <a href="https://github.com/KDWSS/checkov/commit/4d489b9f7c0daf4e81386f69e00c17d8627c5d9c">4d489b9f7c0daf4e81386f69e00c17d8627c5d9c</a></p></details>
## Vulnerabilities
| CVE | Severity | <img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS | Dependency | Type | Fixed in (golang.org/x/net-v0.0.0 version) | Remediation Available |
| ------------- | ------------- | ----- | ----- | ----- | ------------- | --- |
| [CVE-2022-27664](https://www.mend.io/vulnerability-database/CVE-2022-27664) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 7.5 | golang.org/x/net-v0.0.0-20210415231046-e915ea6b2b7d | Direct | golang.org/x/net - 0.0.0-20220906165146-f3363e06e74c, go1.18.6, go1.19.1 | ❌ |
| [CVE-2022-30633](https://www.mend.io/vulnerability-database/CVE-2022-30633) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 7.5 | golang.org/x/net-v0.0.0-20210415231046-e915ea6b2b7d | Direct | go1.17.12,go1.18.4 | ❌ |
| [CVE-2022-41721](https://www.mend.io/vulnerability-database/CVE-2022-41721) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 7.5 | golang.org/x/net-v0.0.0-20210415231046-e915ea6b2b7d | Direct | N/A | ❌ |
| [CVE-2021-33194](https://www.mend.io/vulnerability-database/CVE-2021-33194) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 7.5 | golang.org/x/net-v0.0.0-20210415231046-e915ea6b2b7d | Direct | golang.org/x/net - v0.0.0-20210520170846-37e1c6afe023 | ❌ |
| [CVE-2021-44716](https://www.mend.io/vulnerability-database/CVE-2021-44716) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 7.5 | golang.org/x/net-v0.0.0-20210415231046-e915ea6b2b7d | Direct | github.com/golang/net - 491a49abca63de5e07ef554052d180a1b5fe2d70 | ❌ |
| [CVE-2022-28131](https://www.mend.io/vulnerability-database/CVE-2022-28131) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 7.5 | golang.org/x/net-v0.0.0-20210415231046-e915ea6b2b7d | Direct | go1.17.12,go1.18.4 | ❌ |
| [CVE-2021-31525](https://www.mend.io/vulnerability-database/CVE-2021-31525) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> Medium | 5.9 | golang.org/x/net-v0.0.0-20210415231046-e915ea6b2b7d | Direct | golang - v1.15.12,v1.16.4,v1.17.0 | ❌ |
## Details
<details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> CVE-2022-27664</summary>
### Vulnerable Library - <b>golang.org/x/net-v0.0.0-20210415231046-e915ea6b2b7d</b></p>
<p></p>
<p>Library home page: <a href="https://proxy.golang.org/golang.org/x/net/@v/v0.0.0-20210415231046-e915ea6b2b7d.zip">https://proxy.golang.org/golang.org/x/net/@v/v0.0.0-20210415231046-e915ea6b2b7d.zip</a></p>
<p>
Dependency Hierarchy:
- :x: **golang.org/x/net-v0.0.0-20210415231046-e915ea6b2b7d** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/KDWSS/checkov/commit/4d489b9f7c0daf4e81386f69e00c17d8627c5d9c">4d489b9f7c0daf4e81386f69e00c17d8627c5d9c</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
In net/http in Go before 1.18.6 and 1.19.x before 1.19.1, attackers can cause a denial of service because an HTTP/2 connection can hang during closing if shutdown were preempted by a fatal error.
<p>Publish Date: 2022-09-06
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-27664>CVE-2022-27664</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>7.5</b>)
<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>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://pkg.go.dev/vuln/GO-2022-0969">https://pkg.go.dev/vuln/GO-2022-0969</a></p>
<p>Release Date: 2022-09-06</p>
<p>Fix Resolution: golang.org/x/net - 0.0.0-20220906165146-f3363e06e74c, go1.18.6, go1.19.1</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> CVE-2022-30633</summary>
### Vulnerable Library - <b>golang.org/x/net-v0.0.0-20210415231046-e915ea6b2b7d</b></p>
<p></p>
<p>Library home page: <a href="https://proxy.golang.org/golang.org/x/net/@v/v0.0.0-20210415231046-e915ea6b2b7d.zip">https://proxy.golang.org/golang.org/x/net/@v/v0.0.0-20210415231046-e915ea6b2b7d.zip</a></p>
<p>
Dependency Hierarchy:
- :x: **golang.org/x/net-v0.0.0-20210415231046-e915ea6b2b7d** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/KDWSS/checkov/commit/4d489b9f7c0daf4e81386f69e00c17d8627c5d9c">4d489b9f7c0daf4e81386f69e00c17d8627c5d9c</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
Uncontrolled recursion in Unmarshal in encoding/xml before Go 1.17.12 and Go 1.18.4 allows an attacker to cause a panic due to stack exhaustion via unmarshalling an XML document into a Go struct which has a nested field that uses the 'any' field tag.
<p>Publish Date: 2022-08-10
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-30633>CVE-2022-30633</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>7.5</b>)
<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>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://security-tracker.debian.org/tracker/CVE-2022-30633">https://security-tracker.debian.org/tracker/CVE-2022-30633</a></p>
<p>Release Date: 2022-05-13</p>
<p>Fix Resolution: go1.17.12,go1.18.4</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> CVE-2022-41721</summary>
### Vulnerable Library - <b>golang.org/x/net-v0.0.0-20210415231046-e915ea6b2b7d</b></p>
<p></p>
<p>Library home page: <a href="https://proxy.golang.org/golang.org/x/net/@v/v0.0.0-20210415231046-e915ea6b2b7d.zip">https://proxy.golang.org/golang.org/x/net/@v/v0.0.0-20210415231046-e915ea6b2b7d.zip</a></p>
<p>
Dependency Hierarchy:
- :x: **golang.org/x/net-v0.0.0-20210415231046-e915ea6b2b7d** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/KDWSS/checkov/commit/4d489b9f7c0daf4e81386f69e00c17d8627c5d9c">4d489b9f7c0daf4e81386f69e00c17d8627c5d9c</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
A request smuggling attack is possible when using MaxBytesHandler. When using MaxBytesHandler, the body of an HTTP request is not fully consumed. When the server attempts to read HTTP2 frames from the connection, it will instead be reading the body of the HTTP request, which could be attacker-manipulated to represent arbitrary HTTP2 requests.
<p>Publish Date: 2023-01-13
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-41721>CVE-2022-41721</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>7.5</b>)
<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>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> CVE-2021-33194</summary>
### Vulnerable Library - <b>golang.org/x/net-v0.0.0-20210415231046-e915ea6b2b7d</b></p>
<p></p>
<p>Library home page: <a href="https://proxy.golang.org/golang.org/x/net/@v/v0.0.0-20210415231046-e915ea6b2b7d.zip">https://proxy.golang.org/golang.org/x/net/@v/v0.0.0-20210415231046-e915ea6b2b7d.zip</a></p>
<p>
Dependency Hierarchy:
- :x: **golang.org/x/net-v0.0.0-20210415231046-e915ea6b2b7d** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/KDWSS/checkov/commit/4d489b9f7c0daf4e81386f69e00c17d8627c5d9c">4d489b9f7c0daf4e81386f69e00c17d8627c5d9c</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
golang.org/x/net before v0.0.0-20210520170846-37e1c6afe023 allows attackers to cause a denial of service (infinite loop) via crafted ParseFragment input.
<p>Publish Date: 2021-05-26
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2021-33194>CVE-2021-33194</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>7.5</b>)
<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>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-33194">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-33194</a></p>
<p>Release Date: 2021-05-26</p>
<p>Fix Resolution: golang.org/x/net - v0.0.0-20210520170846-37e1c6afe023</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> CVE-2021-44716</summary>
### Vulnerable Library - <b>golang.org/x/net-v0.0.0-20210415231046-e915ea6b2b7d</b></p>
<p></p>
<p>Library home page: <a href="https://proxy.golang.org/golang.org/x/net/@v/v0.0.0-20210415231046-e915ea6b2b7d.zip">https://proxy.golang.org/golang.org/x/net/@v/v0.0.0-20210415231046-e915ea6b2b7d.zip</a></p>
<p>
Dependency Hierarchy:
- :x: **golang.org/x/net-v0.0.0-20210415231046-e915ea6b2b7d** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/KDWSS/checkov/commit/4d489b9f7c0daf4e81386f69e00c17d8627c5d9c">4d489b9f7c0daf4e81386f69e00c17d8627c5d9c</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
net/http in Go before 1.16.12 and 1.17.x before 1.17.5 allows uncontrolled memory consumption in the header canonicalization cache via HTTP/2 requests.
<p>Publish Date: 2022-01-01
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2021-44716>CVE-2021-44716</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>7.5</b>)
<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>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/advisories/GHSA-vc3p-29h2-gpcp">https://github.com/advisories/GHSA-vc3p-29h2-gpcp</a></p>
<p>Release Date: 2022-01-01</p>
<p>Fix Resolution: github.com/golang/net - 491a49abca63de5e07ef554052d180a1b5fe2d70</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> CVE-2022-28131</summary>
### Vulnerable Library - <b>golang.org/x/net-v0.0.0-20210415231046-e915ea6b2b7d</b></p>
<p></p>
<p>Library home page: <a href="https://proxy.golang.org/golang.org/x/net/@v/v0.0.0-20210415231046-e915ea6b2b7d.zip">https://proxy.golang.org/golang.org/x/net/@v/v0.0.0-20210415231046-e915ea6b2b7d.zip</a></p>
<p>
Dependency Hierarchy:
- :x: **golang.org/x/net-v0.0.0-20210415231046-e915ea6b2b7d** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/KDWSS/checkov/commit/4d489b9f7c0daf4e81386f69e00c17d8627c5d9c">4d489b9f7c0daf4e81386f69e00c17d8627c5d9c</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
Uncontrolled recursion in Decoder.Skip in encoding/xml before Go 1.17.12 and Go 1.18.4 allows an attacker to cause a panic due to stack exhaustion via a deeply nested XML document.
<p>Publish Date: 2022-08-10
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-28131>CVE-2022-28131</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>7.5</b>)
<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>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://security-tracker.debian.org/tracker/CVE-2022-28131">https://security-tracker.debian.org/tracker/CVE-2022-28131</a></p>
<p>Release Date: 2022-03-29</p>
<p>Fix Resolution: go1.17.12,go1.18.4</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> CVE-2021-31525</summary>
### Vulnerable Library - <b>golang.org/x/net-v0.0.0-20210415231046-e915ea6b2b7d</b></p>
<p></p>
<p>Library home page: <a href="https://proxy.golang.org/golang.org/x/net/@v/v0.0.0-20210415231046-e915ea6b2b7d.zip">https://proxy.golang.org/golang.org/x/net/@v/v0.0.0-20210415231046-e915ea6b2b7d.zip</a></p>
<p>
Dependency Hierarchy:
- :x: **golang.org/x/net-v0.0.0-20210415231046-e915ea6b2b7d** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/KDWSS/checkov/commit/4d489b9f7c0daf4e81386f69e00c17d8627c5d9c">4d489b9f7c0daf4e81386f69e00c17d8627c5d9c</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
net/http in Go before 1.15.12 and 1.16.x before 1.16.4 allows remote attackers to cause a denial of service (panic) via a large header to ReadRequest or ReadResponse. Server, Transport, and Client can each be affected in some configurations.
<p>Publish Date: 2021-05-27
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2021-31525>CVE-2021-31525</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>5.9</b>)
<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>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://bugzilla.redhat.com/show_bug.cgi?id=1958341">https://bugzilla.redhat.com/show_bug.cgi?id=1958341</a></p>
<p>Release Date: 2021-05-27</p>
<p>Fix Resolution: golang - v1.15.12,v1.16.4,v1.17.0</p>
</p>
<p></p>
</details> | True | golang.org/x/net-v0.0.0-20210415231046-e915ea6b2b7d: 7 vulnerabilities (highest severity is: 7.5) - autoclosed - <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>golang.org/x/net-v0.0.0-20210415231046-e915ea6b2b7d</b></p></summary>
<p></p>
<p>Library home page: <a href="https://proxy.golang.org/golang.org/x/net/@v/v0.0.0-20210415231046-e915ea6b2b7d.zip">https://proxy.golang.org/golang.org/x/net/@v/v0.0.0-20210415231046-e915ea6b2b7d.zip</a></p>
<p>
<p>Found in HEAD commit: <a href="https://github.com/KDWSS/checkov/commit/4d489b9f7c0daf4e81386f69e00c17d8627c5d9c">4d489b9f7c0daf4e81386f69e00c17d8627c5d9c</a></p></details>
## Vulnerabilities
| CVE | Severity | <img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS | Dependency | Type | Fixed in (golang.org/x/net-v0.0.0 version) | Remediation Available |
| ------------- | ------------- | ----- | ----- | ----- | ------------- | --- |
| [CVE-2022-27664](https://www.mend.io/vulnerability-database/CVE-2022-27664) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 7.5 | golang.org/x/net-v0.0.0-20210415231046-e915ea6b2b7d | Direct | golang.org/x/net - 0.0.0-20220906165146-f3363e06e74c, go1.18.6, go1.19.1 | ❌ |
| [CVE-2022-30633](https://www.mend.io/vulnerability-database/CVE-2022-30633) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 7.5 | golang.org/x/net-v0.0.0-20210415231046-e915ea6b2b7d | Direct | go1.17.12,go1.18.4 | ❌ |
| [CVE-2022-41721](https://www.mend.io/vulnerability-database/CVE-2022-41721) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 7.5 | golang.org/x/net-v0.0.0-20210415231046-e915ea6b2b7d | Direct | N/A | ❌ |
| [CVE-2021-33194](https://www.mend.io/vulnerability-database/CVE-2021-33194) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 7.5 | golang.org/x/net-v0.0.0-20210415231046-e915ea6b2b7d | Direct | golang.org/x/net - v0.0.0-20210520170846-37e1c6afe023 | ❌ |
| [CVE-2021-44716](https://www.mend.io/vulnerability-database/CVE-2021-44716) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 7.5 | golang.org/x/net-v0.0.0-20210415231046-e915ea6b2b7d | Direct | github.com/golang/net - 491a49abca63de5e07ef554052d180a1b5fe2d70 | ❌ |
| [CVE-2022-28131](https://www.mend.io/vulnerability-database/CVE-2022-28131) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 7.5 | golang.org/x/net-v0.0.0-20210415231046-e915ea6b2b7d | Direct | go1.17.12,go1.18.4 | ❌ |
| [CVE-2021-31525](https://www.mend.io/vulnerability-database/CVE-2021-31525) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> Medium | 5.9 | golang.org/x/net-v0.0.0-20210415231046-e915ea6b2b7d | Direct | golang - v1.15.12,v1.16.4,v1.17.0 | ❌ |
## Details
<details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> CVE-2022-27664</summary>
### Vulnerable Library - <b>golang.org/x/net-v0.0.0-20210415231046-e915ea6b2b7d</b></p>
<p></p>
<p>Library home page: <a href="https://proxy.golang.org/golang.org/x/net/@v/v0.0.0-20210415231046-e915ea6b2b7d.zip">https://proxy.golang.org/golang.org/x/net/@v/v0.0.0-20210415231046-e915ea6b2b7d.zip</a></p>
<p>
Dependency Hierarchy:
- :x: **golang.org/x/net-v0.0.0-20210415231046-e915ea6b2b7d** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/KDWSS/checkov/commit/4d489b9f7c0daf4e81386f69e00c17d8627c5d9c">4d489b9f7c0daf4e81386f69e00c17d8627c5d9c</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
In net/http in Go before 1.18.6 and 1.19.x before 1.19.1, attackers can cause a denial of service because an HTTP/2 connection can hang during closing if shutdown were preempted by a fatal error.
<p>Publish Date: 2022-09-06
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-27664>CVE-2022-27664</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>7.5</b>)
<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>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://pkg.go.dev/vuln/GO-2022-0969">https://pkg.go.dev/vuln/GO-2022-0969</a></p>
<p>Release Date: 2022-09-06</p>
<p>Fix Resolution: golang.org/x/net - 0.0.0-20220906165146-f3363e06e74c, go1.18.6, go1.19.1</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> CVE-2022-30633</summary>
### Vulnerable Library - <b>golang.org/x/net-v0.0.0-20210415231046-e915ea6b2b7d</b></p>
<p></p>
<p>Library home page: <a href="https://proxy.golang.org/golang.org/x/net/@v/v0.0.0-20210415231046-e915ea6b2b7d.zip">https://proxy.golang.org/golang.org/x/net/@v/v0.0.0-20210415231046-e915ea6b2b7d.zip</a></p>
<p>
Dependency Hierarchy:
- :x: **golang.org/x/net-v0.0.0-20210415231046-e915ea6b2b7d** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/KDWSS/checkov/commit/4d489b9f7c0daf4e81386f69e00c17d8627c5d9c">4d489b9f7c0daf4e81386f69e00c17d8627c5d9c</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
Uncontrolled recursion in Unmarshal in encoding/xml before Go 1.17.12 and Go 1.18.4 allows an attacker to cause a panic due to stack exhaustion via unmarshalling an XML document into a Go struct which has a nested field that uses the 'any' field tag.
<p>Publish Date: 2022-08-10
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-30633>CVE-2022-30633</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>7.5</b>)
<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>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://security-tracker.debian.org/tracker/CVE-2022-30633">https://security-tracker.debian.org/tracker/CVE-2022-30633</a></p>
<p>Release Date: 2022-05-13</p>
<p>Fix Resolution: go1.17.12,go1.18.4</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> CVE-2022-41721</summary>
### Vulnerable Library - <b>golang.org/x/net-v0.0.0-20210415231046-e915ea6b2b7d</b></p>
<p></p>
<p>Library home page: <a href="https://proxy.golang.org/golang.org/x/net/@v/v0.0.0-20210415231046-e915ea6b2b7d.zip">https://proxy.golang.org/golang.org/x/net/@v/v0.0.0-20210415231046-e915ea6b2b7d.zip</a></p>
<p>
Dependency Hierarchy:
- :x: **golang.org/x/net-v0.0.0-20210415231046-e915ea6b2b7d** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/KDWSS/checkov/commit/4d489b9f7c0daf4e81386f69e00c17d8627c5d9c">4d489b9f7c0daf4e81386f69e00c17d8627c5d9c</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
A request smuggling attack is possible when using MaxBytesHandler. When using MaxBytesHandler, the body of an HTTP request is not fully consumed. When the server attempts to read HTTP2 frames from the connection, it will instead be reading the body of the HTTP request, which could be attacker-manipulated to represent arbitrary HTTP2 requests.
<p>Publish Date: 2023-01-13
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-41721>CVE-2022-41721</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>7.5</b>)
<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>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> CVE-2021-33194</summary>
### Vulnerable Library - <b>golang.org/x/net-v0.0.0-20210415231046-e915ea6b2b7d</b></p>
<p></p>
<p>Library home page: <a href="https://proxy.golang.org/golang.org/x/net/@v/v0.0.0-20210415231046-e915ea6b2b7d.zip">https://proxy.golang.org/golang.org/x/net/@v/v0.0.0-20210415231046-e915ea6b2b7d.zip</a></p>
<p>
Dependency Hierarchy:
- :x: **golang.org/x/net-v0.0.0-20210415231046-e915ea6b2b7d** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/KDWSS/checkov/commit/4d489b9f7c0daf4e81386f69e00c17d8627c5d9c">4d489b9f7c0daf4e81386f69e00c17d8627c5d9c</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
golang.org/x/net before v0.0.0-20210520170846-37e1c6afe023 allows attackers to cause a denial of service (infinite loop) via crafted ParseFragment input.
<p>Publish Date: 2021-05-26
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2021-33194>CVE-2021-33194</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>7.5</b>)
<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>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-33194">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-33194</a></p>
<p>Release Date: 2021-05-26</p>
<p>Fix Resolution: golang.org/x/net - v0.0.0-20210520170846-37e1c6afe023</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> CVE-2021-44716</summary>
### Vulnerable Library - <b>golang.org/x/net-v0.0.0-20210415231046-e915ea6b2b7d</b></p>
<p></p>
<p>Library home page: <a href="https://proxy.golang.org/golang.org/x/net/@v/v0.0.0-20210415231046-e915ea6b2b7d.zip">https://proxy.golang.org/golang.org/x/net/@v/v0.0.0-20210415231046-e915ea6b2b7d.zip</a></p>
<p>
Dependency Hierarchy:
- :x: **golang.org/x/net-v0.0.0-20210415231046-e915ea6b2b7d** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/KDWSS/checkov/commit/4d489b9f7c0daf4e81386f69e00c17d8627c5d9c">4d489b9f7c0daf4e81386f69e00c17d8627c5d9c</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
net/http in Go before 1.16.12 and 1.17.x before 1.17.5 allows uncontrolled memory consumption in the header canonicalization cache via HTTP/2 requests.
<p>Publish Date: 2022-01-01
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2021-44716>CVE-2021-44716</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>7.5</b>)
<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>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/advisories/GHSA-vc3p-29h2-gpcp">https://github.com/advisories/GHSA-vc3p-29h2-gpcp</a></p>
<p>Release Date: 2022-01-01</p>
<p>Fix Resolution: github.com/golang/net - 491a49abca63de5e07ef554052d180a1b5fe2d70</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> CVE-2022-28131</summary>
### Vulnerable Library - <b>golang.org/x/net-v0.0.0-20210415231046-e915ea6b2b7d</b></p>
<p></p>
<p>Library home page: <a href="https://proxy.golang.org/golang.org/x/net/@v/v0.0.0-20210415231046-e915ea6b2b7d.zip">https://proxy.golang.org/golang.org/x/net/@v/v0.0.0-20210415231046-e915ea6b2b7d.zip</a></p>
<p>
Dependency Hierarchy:
- :x: **golang.org/x/net-v0.0.0-20210415231046-e915ea6b2b7d** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/KDWSS/checkov/commit/4d489b9f7c0daf4e81386f69e00c17d8627c5d9c">4d489b9f7c0daf4e81386f69e00c17d8627c5d9c</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
Uncontrolled recursion in Decoder.Skip in encoding/xml before Go 1.17.12 and Go 1.18.4 allows an attacker to cause a panic due to stack exhaustion via a deeply nested XML document.
<p>Publish Date: 2022-08-10
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-28131>CVE-2022-28131</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>7.5</b>)
<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>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://security-tracker.debian.org/tracker/CVE-2022-28131">https://security-tracker.debian.org/tracker/CVE-2022-28131</a></p>
<p>Release Date: 2022-03-29</p>
<p>Fix Resolution: go1.17.12,go1.18.4</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> CVE-2021-31525</summary>
### Vulnerable Library - <b>golang.org/x/net-v0.0.0-20210415231046-e915ea6b2b7d</b></p>
<p></p>
<p>Library home page: <a href="https://proxy.golang.org/golang.org/x/net/@v/v0.0.0-20210415231046-e915ea6b2b7d.zip">https://proxy.golang.org/golang.org/x/net/@v/v0.0.0-20210415231046-e915ea6b2b7d.zip</a></p>
<p>
Dependency Hierarchy:
- :x: **golang.org/x/net-v0.0.0-20210415231046-e915ea6b2b7d** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/KDWSS/checkov/commit/4d489b9f7c0daf4e81386f69e00c17d8627c5d9c">4d489b9f7c0daf4e81386f69e00c17d8627c5d9c</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
net/http in Go before 1.15.12 and 1.16.x before 1.16.4 allows remote attackers to cause a denial of service (panic) via a large header to ReadRequest or ReadResponse. Server, Transport, and Client can each be affected in some configurations.
<p>Publish Date: 2021-05-27
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2021-31525>CVE-2021-31525</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>5.9</b>)
<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>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://bugzilla.redhat.com/show_bug.cgi?id=1958341">https://bugzilla.redhat.com/show_bug.cgi?id=1958341</a></p>
<p>Release Date: 2021-05-27</p>
<p>Fix Resolution: golang - v1.15.12,v1.16.4,v1.17.0</p>
</p>
<p></p>
</details> | non_priority | golang org x net vulnerabilities highest severity is autoclosed vulnerable library golang org x net library home page a href found in head commit a href vulnerabilities cve severity cvss dependency type fixed in golang org x net version remediation available high golang org x net direct golang org x net high golang org x net direct high golang org x net direct n a high golang org x net direct golang org x net high golang org x net direct github com golang net high golang org x net direct medium golang org x net direct golang details cve vulnerable library golang org x net library home page a href dependency hierarchy x golang org x net vulnerable library found in head commit a href found in base branch main vulnerability details in net http in go before and x before attackers can cause a denial of service because an http connection can hang during closing if shutdown were preempted by a fatal error 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 org x net cve vulnerable library golang org x net library home page a href dependency hierarchy x golang org x net vulnerable library found in head commit a href found in base branch main vulnerability details uncontrolled recursion in unmarshal in encoding xml before go and go allows an attacker to cause a panic due to stack exhaustion via unmarshalling an xml document into a go struct which has a nested field that uses the any field tag 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 cve vulnerable library golang org x net library home page a href dependency hierarchy x golang org x net vulnerable library found in head commit a href found in base branch main vulnerability details a request smuggling attack is possible when using maxbyteshandler when using maxbyteshandler the body of an http request is not fully consumed when the server attempts to read frames from the connection it will instead be reading the body of the http request which could be attacker manipulated to represent arbitrary requests 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 cve vulnerable library golang org x net library home page a href dependency hierarchy x golang org x net vulnerable library found in head commit a href found in base branch main vulnerability details golang org x net before allows attackers to cause a denial of service infinite loop via crafted parsefragment input 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 org x net cve vulnerable library golang org x net library home page a href dependency hierarchy x golang org x net vulnerable library found in head commit a href found in base branch main vulnerability details net http in go before and x before allows uncontrolled memory consumption in the header canonicalization cache via http requests 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 github com golang net cve vulnerable library golang org x net library home page a href dependency hierarchy x golang org x net vulnerable library found in head commit a href found in base branch main vulnerability details uncontrolled recursion in decoder skip in encoding xml before go and go allows an attacker to cause a panic due to stack exhaustion via a deeply nested xml document 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 cve vulnerable library golang org x net library home page a href dependency hierarchy x golang org x net vulnerable library found in head commit a href found in base branch main vulnerability details net http in go before and x before allows remote attackers to cause a denial of service panic via a large header to readrequest or readresponse server transport and client can each be affected in some configurations 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 golang | 0 |
17,137 | 23,651,371,174 | IssuesEvent | 2022-08-26 07:01:13 | dotnet/runtime | https://api.github.com/repos/dotnet/runtime | opened | HttpClient creates Quic threads even if HTTP/3 is not in use | tenet-compatibility area-System.Net.Quic | 1. Create simple console app with HTTP and run simple http1.1 request on Windows 11 or Server 22.
2. look at application threads.
Application crates 2x threads per core even if HTTP/3 and Quic are not in used. This was originally reported on legacy system with 54 cores. That will create 100+ threads ... for nothing.
We should figure out how to make `Quic.IsSupported` cheap and defer thread creation until needed.
This will impact legacy app that has no clue tor intention to use Quic or HTTP/3. | True | HttpClient creates Quic threads even if HTTP/3 is not in use - 1. Create simple console app with HTTP and run simple http1.1 request on Windows 11 or Server 22.
2. look at application threads.
Application crates 2x threads per core even if HTTP/3 and Quic are not in used. This was originally reported on legacy system with 54 cores. That will create 100+ threads ... for nothing.
We should figure out how to make `Quic.IsSupported` cheap and defer thread creation until needed.
This will impact legacy app that has no clue tor intention to use Quic or HTTP/3. | non_priority | httpclient creates quic threads even if http is not in use create simple console app with http and run simple request on windows or server look at application threads application crates threads per core even if http and quic are not in used this was originally reported on legacy system with cores that will create threads for nothing we should figure out how to make quic issupported cheap and defer thread creation until needed this will impact legacy app that has no clue tor intention to use quic or http | 0 |
69,130 | 22,198,686,020 | IssuesEvent | 2022-06-07 09:14:24 | vector-im/element-ios | https://api.github.com/repos/vector-im/element-ios | closed | Incorrect room names: "Someone and x others" or "Joe and Joe" | T-Defect A-SDK A-Room-List S-Minor O-Uncommon Z-WTF | ### Steps to reproduce
Unsure of steps to reproduce but there have been multiple reports of the room name being wiped out and becoming "Someone and x others". Creating this issue to keep track of reports.
One user has mentioned they've seen it on Element Desktop too, so potentially a synapse issue?
### Outcome
#### What did you expect?
The name shouldn't fallback to this unless it is actually removed from the room.
#### What happened instead?
"Someone and x others"
### Your phone model
_No response_
### Operating system version
_No response_
### Application version
1.6.8
### Homeserver
_No response_
### Will you send logs?
No | 1.0 | Incorrect room names: "Someone and x others" or "Joe and Joe" - ### Steps to reproduce
Unsure of steps to reproduce but there have been multiple reports of the room name being wiped out and becoming "Someone and x others". Creating this issue to keep track of reports.
One user has mentioned they've seen it on Element Desktop too, so potentially a synapse issue?
### Outcome
#### What did you expect?
The name shouldn't fallback to this unless it is actually removed from the room.
#### What happened instead?
"Someone and x others"
### Your phone model
_No response_
### Operating system version
_No response_
### Application version
1.6.8
### Homeserver
_No response_
### Will you send logs?
No | non_priority | incorrect room names someone and x others or joe and joe steps to reproduce unsure of steps to reproduce but there have been multiple reports of the room name being wiped out and becoming someone and x others creating this issue to keep track of reports one user has mentioned they ve seen it on element desktop too so potentially a synapse issue outcome what did you expect the name shouldn t fallback to this unless it is actually removed from the room what happened instead someone and x others your phone model no response operating system version no response application version homeserver no response will you send logs no | 0 |
112,401 | 24,264,356,221 | IssuesEvent | 2022-09-28 04:00:23 | dotnet/runtime | https://api.github.com/repos/dotnet/runtime | closed | Support value numbering of SIMD types in RyuJIT optimizer | enhancement tenet-performance area-CodeGen-coreclr optimization JitUntriaged | Per the comment, extend value numbering to support SIMD types in RyuJIT.
valuenum.cpp
```
#ifdef FEATURE_SIMD
// TODO-CQ: For now TYP_SIMD values are not handled by value numbering to be amenable for CSE'ing.
if (oper == GT_SIMD)
{
tree->gtVNPair.SetBoth(vnStore->VNForExpr(TYP_UNKNOWN));
return;
}
#endif
```
category:cq
theme:vector-codegen
skill-level:intermediate
cost:medium | 1.0 | Support value numbering of SIMD types in RyuJIT optimizer - Per the comment, extend value numbering to support SIMD types in RyuJIT.
valuenum.cpp
```
#ifdef FEATURE_SIMD
// TODO-CQ: For now TYP_SIMD values are not handled by value numbering to be amenable for CSE'ing.
if (oper == GT_SIMD)
{
tree->gtVNPair.SetBoth(vnStore->VNForExpr(TYP_UNKNOWN));
return;
}
#endif
```
category:cq
theme:vector-codegen
skill-level:intermediate
cost:medium | non_priority | support value numbering of simd types in ryujit optimizer per the comment extend value numbering to support simd types in ryujit valuenum cpp ifdef feature simd todo cq for now typ simd values are not handled by value numbering to be amenable for cse ing if oper gt simd tree gtvnpair setboth vnstore vnforexpr typ unknown return endif category cq theme vector codegen skill level intermediate cost medium | 0 |
437,484 | 30,600,976,314 | IssuesEvent | 2023-07-22 11:28:54 | ThosRTanner/inforss | https://api.github.com/repos/ThosRTanner/inforss | closed | Marking all headlines in group read only marks visible headlines read | Documentation User Interface | This is confusing if you (say) limit the headline display to 3 headlines. It'll only mark the 3 visible headlines read, and leave all the other ones alone.
this is reasonable in so far as you've probably not seen the other ones but really annoying when you have set up a new feed and have already read all the articles the feed presents.
Minimally this needs to be documented better.
Also maybe add an option to control the behavior.
| 1.0 | Marking all headlines in group read only marks visible headlines read - This is confusing if you (say) limit the headline display to 3 headlines. It'll only mark the 3 visible headlines read, and leave all the other ones alone.
this is reasonable in so far as you've probably not seen the other ones but really annoying when you have set up a new feed and have already read all the articles the feed presents.
Minimally this needs to be documented better.
Also maybe add an option to control the behavior.
| non_priority | marking all headlines in group read only marks visible headlines read this is confusing if you say limit the headline display to headlines it ll only mark the visible headlines read and leave all the other ones alone this is reasonable in so far as you ve probably not seen the other ones but really annoying when you have set up a new feed and have already read all the articles the feed presents minimally this needs to be documented better also maybe add an option to control the behavior | 0 |
429,687 | 30,085,585,308 | IssuesEvent | 2023-06-29 08:23:48 | Tencent/tdesign-miniprogram | https://api.github.com/repos/Tencent/tdesign-miniprogram | closed | [Checkbox] 文档描述错误 | documentation | ### tdesign-miniprogram 版本
1.1.10
### 重现链接
https://tdesign.tencent.com/miniprogram/components/checkbox?tab=api
### 重现步骤
CheckboxGroup Events 的参数描述与实际不符
实际并没有 context 参数
```ts
this._trigger('change', { value: newValue });
```
https://github.com/Tencent/tdesign-miniprogram/blob/b40609d3f0573067afc002e4058d3067f52aa4e7/src/checkbox-group/checkbox-group.ts#L113C7-L113C7
### 期望结果
_No response_
### 实际结果
_No response_
### 基础库版本
_No response_
### 补充说明
_No response_ | 1.0 | [Checkbox] 文档描述错误 - ### tdesign-miniprogram 版本
1.1.10
### 重现链接
https://tdesign.tencent.com/miniprogram/components/checkbox?tab=api
### 重现步骤
CheckboxGroup Events 的参数描述与实际不符
实际并没有 context 参数
```ts
this._trigger('change', { value: newValue });
```
https://github.com/Tencent/tdesign-miniprogram/blob/b40609d3f0573067afc002e4058d3067f52aa4e7/src/checkbox-group/checkbox-group.ts#L113C7-L113C7
### 期望结果
_No response_
### 实际结果
_No response_
### 基础库版本
_No response_
### 补充说明
_No response_ | non_priority | 文档描述错误 tdesign miniprogram 版本 重现链接 重现步骤 checkboxgroup events 的参数描述与实际不符 实际并没有 context 参数 ts this trigger change value newvalue 期望结果 no response 实际结果 no response 基础库版本 no response 补充说明 no response | 0 |
288,197 | 24,888,403,001 | IssuesEvent | 2022-10-28 09:45:30 | airbytehq/airbyte | https://api.github.com/repos/airbytehq/airbyte | closed | SAT [strict_mode]: `basic_read.expect_records` must be set | type/enhancement Acceptance Tests team/connector-ops | ## Tell us about the problem you're trying to solve
`basic_read.expect_record` is currently optionally used to declare a file with a list of records expected to receive on a `read` command. Making it mandatory for GA connectors is required to validate record schema and limit regression on `read`.
## Describe the solution you’d like
SAT must enforce the presence of the `expect_record` field in the `basic_read` test section for GA connectors.
I'd like these expect_records to be split by stream for maximum control and granularity in a future coverage computation.
**If a bypass_reason is filled SAT should log a warning.**
Example for a partially seeded sandbox account:
```yaml
strict_mode: strict
tests:
basic_read:
- config_path: "secrets/config.json"
configured_catalog_path: "integration_tests/configured_catalog.json"
expect_records:
streams:
- stream_name: stream_a
expected_records_path: "integration_tests/a_expected_records.txt"
extra_fields: no
exact_order: yes
extra_records: no
- stream_name: stream_b
bypass_reason: "We cannot seed stream b"
```
Example for a not seeded sandbox account:
```yaml
strict_mode: strict
tests:
basic_read:
- config_path: "secrets/config.json"
configured_catalog_path: "integration_tests/configured_catalog.json"
expect_records:
bypass_reason: "No stream can be seeded on our sandbox account"
```
**If a bypass_reason is filled SAT should log a warning.**
This will require changing the configuration structure of `expect_records` which is not currently stream-specific:
```yaml
basic_read:
- config_path: "secrets/config.json"
configured_catalog_path: "integration_tests/configured_catalog.json"
expect_records:
path: "integration_tests/expected_records.txt"
extra_fields: no
exact_order: yes
extra_records: no
```
| 1.0 | SAT [strict_mode]: `basic_read.expect_records` must be set - ## Tell us about the problem you're trying to solve
`basic_read.expect_record` is currently optionally used to declare a file with a list of records expected to receive on a `read` command. Making it mandatory for GA connectors is required to validate record schema and limit regression on `read`.
## Describe the solution you’d like
SAT must enforce the presence of the `expect_record` field in the `basic_read` test section for GA connectors.
I'd like these expect_records to be split by stream for maximum control and granularity in a future coverage computation.
**If a bypass_reason is filled SAT should log a warning.**
Example for a partially seeded sandbox account:
```yaml
strict_mode: strict
tests:
basic_read:
- config_path: "secrets/config.json"
configured_catalog_path: "integration_tests/configured_catalog.json"
expect_records:
streams:
- stream_name: stream_a
expected_records_path: "integration_tests/a_expected_records.txt"
extra_fields: no
exact_order: yes
extra_records: no
- stream_name: stream_b
bypass_reason: "We cannot seed stream b"
```
Example for a not seeded sandbox account:
```yaml
strict_mode: strict
tests:
basic_read:
- config_path: "secrets/config.json"
configured_catalog_path: "integration_tests/configured_catalog.json"
expect_records:
bypass_reason: "No stream can be seeded on our sandbox account"
```
**If a bypass_reason is filled SAT should log a warning.**
This will require changing the configuration structure of `expect_records` which is not currently stream-specific:
```yaml
basic_read:
- config_path: "secrets/config.json"
configured_catalog_path: "integration_tests/configured_catalog.json"
expect_records:
path: "integration_tests/expected_records.txt"
extra_fields: no
exact_order: yes
extra_records: no
```
| non_priority | sat basic read expect records must be set tell us about the problem you re trying to solve basic read expect record is currently optionally used to declare a file with a list of records expected to receive on a read command making it mandatory for ga connectors is required to validate record schema and limit regression on read describe the solution you’d like sat must enforce the presence of the expect record field in the basic read test section for ga connectors i d like these expect records to be split by stream for maximum control and granularity in a future coverage computation if a bypass reason is filled sat should log a warning example for a partially seeded sandbox account yaml strict mode strict tests basic read config path secrets config json configured catalog path integration tests configured catalog json expect records streams stream name stream a expected records path integration tests a expected records txt extra fields no exact order yes extra records no stream name stream b bypass reason we cannot seed stream b example for a not seeded sandbox account yaml strict mode strict tests basic read config path secrets config json configured catalog path integration tests configured catalog json expect records bypass reason no stream can be seeded on our sandbox account if a bypass reason is filled sat should log a warning this will require changing the configuration structure of expect records which is not currently stream specific yaml basic read config path secrets config json configured catalog path integration tests configured catalog json expect records path integration tests expected records txt extra fields no exact order yes extra records no | 0 |
3,782 | 3,249,867,958 | IssuesEvent | 2015-10-18 14:31:25 | felansu/QRBWS | https://api.github.com/repos/felansu/QRBWS | closed | Create domain class 'Locacao' | building | It's necessary create the domain class 'Locacao' (lend) for in/out control of books | 1.0 | Create domain class 'Locacao' - It's necessary create the domain class 'Locacao' (lend) for in/out control of books | non_priority | create domain class locacao it s necessary create the domain class locacao lend for in out control of books | 0 |
212,895 | 16,486,604,039 | IssuesEvent | 2021-05-24 18:58:35 | YMk-lab/daily-diabetes | https://api.github.com/repos/YMk-lab/daily-diabetes | closed | Monkey testing for patient cases table | monkey-testing | Provide dozen of cases to test patient cases table and test mat paginator | 1.0 | Monkey testing for patient cases table - Provide dozen of cases to test patient cases table and test mat paginator | non_priority | monkey testing for patient cases table provide dozen of cases to test patient cases table and test mat paginator | 0 |
345,007 | 24,839,886,087 | IssuesEvent | 2022-10-26 11:54:31 | Epitech-R-Type/R-Type | https://api.github.com/repos/Epitech-R-Type/R-Type | closed | Rework protocol.txt for added clarity | documentation | ### Purpose
- Add ASCII diagrams illustrating TCP and UDP client/server interaction
- Increase clarity in UDP command arguments | 1.0 | Rework protocol.txt for added clarity - ### Purpose
- Add ASCII diagrams illustrating TCP and UDP client/server interaction
- Increase clarity in UDP command arguments | non_priority | rework protocol txt for added clarity purpose add ascii diagrams illustrating tcp and udp client server interaction increase clarity in udp command arguments | 0 |
210,980 | 23,778,948,805 | IssuesEvent | 2022-09-02 01:06:13 | lkurzyniec/YellowNotes | https://api.github.com/repos/lkurzyniec/YellowNotes | closed | CVE-2017-0256 (Medium) detected in microsoft.codedom.providers.dotnetcompilerplatform.3.6.0.nupkg - autoclosed | security vulnerability | ## CVE-2017-0256 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>microsoft.codedom.providers.dotnetcompilerplatform.3.6.0.nupkg</b></p></summary>
<p>Replacement CodeDOM providers that use the new .NET Compiler Platform ("Roslyn") compiler as a service APIs.</p>
<p>Library home page: <a href="https://api.nuget.org/packages/microsoft.codedom.providers.dotnetcompilerplatform.3.6.0.nupkg">https://api.nuget.org/packages/microsoft.codedom.providers.dotnetcompilerplatform.3.6.0.nupkg</a></p>
<p>Path to dependency file: /YellowNotes.Api/YellowNotes.Api.csproj</p>
<p>Path to vulnerable library: /t/packages/microsoft.codedom.providers.dotnetcompilerplatform/3.6.0/microsoft.codedom.providers.dotnetcompilerplatform.3.6.0.nupkg</p>
<p>
Dependency Hierarchy:
- :x: **microsoft.codedom.providers.dotnetcompilerplatform.3.6.0.nupkg** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/lkurzyniec/YellowNotes/commit/b38cb84bda037cac69573fdd240885876dca2fda">b38cb84bda037cac69573fdd240885876dca2fda</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>
A spoofing vulnerability exists when the ASP.NET Core fails to properly sanitize web requests.
<p>Publish Date: 2017-05-12
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2017-0256>CVE-2017-0256</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.3</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: Low
- 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-2017-0256">https://nvd.nist.gov/vuln/detail/CVE-2017-0256</a></p>
<p>Release Date: 2017-05-12</p>
<p>Fix Resolution: Microsoft.AspNetCore.Mvc.ApiExplorer - 1.1.3,1.0.4;Microsoft.AspNetCore.Mvc.Abstractions - 1.1.3,1.0.4;Microsoft.AspNetCore.Mvc.Core - 1.0.4,1.1.3;Microsoft.AspNetCore.Mvc.Cors - 1.0.4,1.1.3;Microsoft.AspNetCore.Mvc.Localization - 1.1.3,1.0.4;System.Net.Http - 4.1.2,4.3.2;Microsoft.AspNetCore.Mvc.Razor - 1.1.3,1.0.4;System.Net.Http.WinHttpHandler - 4.0.2,4.3.0-preview1-24530-04;System.Net.Security - 4.3.0-preview1-24530-04,4.0.1;Microsoft.AspNetCore.Mvc.ViewFeatures - 1.1.3,1.0.4;Microsoft.AspNetCore.Mvc.TagHelpers - 1.0.4,1.1.3;System.Text.Encodings.Web - 4.3.0-preview1-24530-04,4.0.1;Microsoft.AspNetCore.Mvc.Razor.Host - 1.1.3,1.0.4;Microsoft.AspNetCore.Mvc.Formatters.Json - 1.0.4,1.1.3;Microsoft.AspNetCore.Mvc.WebApiCompatShim - 1.0.4,1.1.3;System.Net.WebSockets.Client - 4.3.0-preview1-24530-04,4.0.1;Microsoft.AspNetCore.Mvc.Formatters.Xml - 1.1.3,1.0.4;Microsoft.AspNetCore.Mvc.DataAnnotations - 1.0.4,1.1.3</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-2017-0256 (Medium) detected in microsoft.codedom.providers.dotnetcompilerplatform.3.6.0.nupkg - autoclosed - ## CVE-2017-0256 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>microsoft.codedom.providers.dotnetcompilerplatform.3.6.0.nupkg</b></p></summary>
<p>Replacement CodeDOM providers that use the new .NET Compiler Platform ("Roslyn") compiler as a service APIs.</p>
<p>Library home page: <a href="https://api.nuget.org/packages/microsoft.codedom.providers.dotnetcompilerplatform.3.6.0.nupkg">https://api.nuget.org/packages/microsoft.codedom.providers.dotnetcompilerplatform.3.6.0.nupkg</a></p>
<p>Path to dependency file: /YellowNotes.Api/YellowNotes.Api.csproj</p>
<p>Path to vulnerable library: /t/packages/microsoft.codedom.providers.dotnetcompilerplatform/3.6.0/microsoft.codedom.providers.dotnetcompilerplatform.3.6.0.nupkg</p>
<p>
Dependency Hierarchy:
- :x: **microsoft.codedom.providers.dotnetcompilerplatform.3.6.0.nupkg** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/lkurzyniec/YellowNotes/commit/b38cb84bda037cac69573fdd240885876dca2fda">b38cb84bda037cac69573fdd240885876dca2fda</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>
A spoofing vulnerability exists when the ASP.NET Core fails to properly sanitize web requests.
<p>Publish Date: 2017-05-12
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2017-0256>CVE-2017-0256</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.3</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: Low
- 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-2017-0256">https://nvd.nist.gov/vuln/detail/CVE-2017-0256</a></p>
<p>Release Date: 2017-05-12</p>
<p>Fix Resolution: Microsoft.AspNetCore.Mvc.ApiExplorer - 1.1.3,1.0.4;Microsoft.AspNetCore.Mvc.Abstractions - 1.1.3,1.0.4;Microsoft.AspNetCore.Mvc.Core - 1.0.4,1.1.3;Microsoft.AspNetCore.Mvc.Cors - 1.0.4,1.1.3;Microsoft.AspNetCore.Mvc.Localization - 1.1.3,1.0.4;System.Net.Http - 4.1.2,4.3.2;Microsoft.AspNetCore.Mvc.Razor - 1.1.3,1.0.4;System.Net.Http.WinHttpHandler - 4.0.2,4.3.0-preview1-24530-04;System.Net.Security - 4.3.0-preview1-24530-04,4.0.1;Microsoft.AspNetCore.Mvc.ViewFeatures - 1.1.3,1.0.4;Microsoft.AspNetCore.Mvc.TagHelpers - 1.0.4,1.1.3;System.Text.Encodings.Web - 4.3.0-preview1-24530-04,4.0.1;Microsoft.AspNetCore.Mvc.Razor.Host - 1.1.3,1.0.4;Microsoft.AspNetCore.Mvc.Formatters.Json - 1.0.4,1.1.3;Microsoft.AspNetCore.Mvc.WebApiCompatShim - 1.0.4,1.1.3;System.Net.WebSockets.Client - 4.3.0-preview1-24530-04,4.0.1;Microsoft.AspNetCore.Mvc.Formatters.Xml - 1.1.3,1.0.4;Microsoft.AspNetCore.Mvc.DataAnnotations - 1.0.4,1.1.3</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 microsoft codedom providers dotnetcompilerplatform nupkg autoclosed cve medium severity vulnerability vulnerable library microsoft codedom providers dotnetcompilerplatform nupkg replacement codedom providers that use the new net compiler platform roslyn compiler as a service apis library home page a href path to dependency file yellownotes api yellownotes api csproj path to vulnerable library t packages microsoft codedom providers dotnetcompilerplatform microsoft codedom providers dotnetcompilerplatform nupkg dependency hierarchy x microsoft codedom providers dotnetcompilerplatform nupkg vulnerable library found in head commit a href found in base branch master vulnerability details a spoofing vulnerability exists when the asp net core fails to properly sanitize web requests 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 low availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution microsoft aspnetcore mvc apiexplorer microsoft aspnetcore mvc abstractions microsoft aspnetcore mvc core microsoft aspnetcore mvc cors microsoft aspnetcore mvc localization system net http microsoft aspnetcore mvc razor system net http winhttphandler system net security microsoft aspnetcore mvc viewfeatures microsoft aspnetcore mvc taghelpers system text encodings web microsoft aspnetcore mvc razor host microsoft aspnetcore mvc formatters json microsoft aspnetcore mvc webapicompatshim system net websockets client microsoft aspnetcore mvc formatters xml microsoft aspnetcore mvc dataannotations step up your open source security game with mend | 0 |
334,389 | 29,833,884,047 | IssuesEvent | 2023-06-18 15:49:13 | litestar-org/litestar | https://api.github.com/repos/litestar-org/litestar | opened | Refactor: Reorganise test suite | help wanted refactor tests-issue | Our test suite has grown with the project, but as a result has become a bit disorganised in quite a few places. It should be efactored in a way that structures it in a more consistent and logical way. | 1.0 | Refactor: Reorganise test suite - Our test suite has grown with the project, but as a result has become a bit disorganised in quite a few places. It should be efactored in a way that structures it in a more consistent and logical way. | non_priority | refactor reorganise test suite our test suite has grown with the project but as a result has become a bit disorganised in quite a few places it should be efactored in a way that structures it in a more consistent and logical way | 0 |
97,482 | 8,657,327,775 | IssuesEvent | 2018-11-27 21:00:00 | webhintio/hint | https://api.github.com/repos/webhintio/hint | closed | [Tests] Pass correctly typed objects/methods into sinon spy/stub | difficulty:medium greenkeeper type:testing |
## The devDependency [@types/sinon](https://github.com/DefinitelyTyped/DefinitelyTyped) was updated from `5.0.5` to `5.0.6`.
🚨 [View failing branch](https://github.com/webhintio/hint/compare/master...webhintio:greenkeeper%2Fdefault%2F%40types%2Fsinon-5.0.6).
This version is **covered** by your **current version range** and after updating it in your project **the build failed**.
@types/sinon is a devDependency of this project. It **might not break your production code or affect downstream projects**, but probably breaks your build or test tools, which may **prevent deploying or publishing**.
<details>
<summary>Status Details</summary>
- ❌ **continuous-integration/travis-ci/push:** The Travis CI build failed ([Details](https://travis-ci.org/webhintio/hint/builds/456660726?utm_source=github_status&utm_medium=notification)).
</details>
---
<details>
<summary>FAQ and help</summary>
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those don’t help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).
</details>
---
Your [Greenkeeper](https://greenkeeper.io) Bot :palm_tree:
| 1.0 | [Tests] Pass correctly typed objects/methods into sinon spy/stub -
## The devDependency [@types/sinon](https://github.com/DefinitelyTyped/DefinitelyTyped) was updated from `5.0.5` to `5.0.6`.
🚨 [View failing branch](https://github.com/webhintio/hint/compare/master...webhintio:greenkeeper%2Fdefault%2F%40types%2Fsinon-5.0.6).
This version is **covered** by your **current version range** and after updating it in your project **the build failed**.
@types/sinon is a devDependency of this project. It **might not break your production code or affect downstream projects**, but probably breaks your build or test tools, which may **prevent deploying or publishing**.
<details>
<summary>Status Details</summary>
- ❌ **continuous-integration/travis-ci/push:** The Travis CI build failed ([Details](https://travis-ci.org/webhintio/hint/builds/456660726?utm_source=github_status&utm_medium=notification)).
</details>
---
<details>
<summary>FAQ and help</summary>
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those don’t help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).
</details>
---
Your [Greenkeeper](https://greenkeeper.io) Bot :palm_tree:
| non_priority | pass correctly typed objects methods into sinon spy stub the devdependency was updated from to 🚨 this version is covered by your current version range and after updating it in your project the build failed types sinon is a devdependency of this project it might not break your production code or affect downstream projects but probably breaks your build or test tools which may prevent deploying or publishing status details ❌ continuous integration travis ci push the travis ci build failed faq and help there is a collection of if those don’t help you can always your bot palm tree | 0 |
232,321 | 25,567,907,959 | IssuesEvent | 2022-11-30 15:32:18 | ilan-WS/cloudify-stage | https://api.github.com/repos/ilan-WS/cloudify-stage | opened | CVE-2022-38900 (High) detected in decode-uri-component-0.2.0.tgz | security vulnerability | ## CVE-2022-38900 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>decode-uri-component-0.2.0.tgz</b></p></summary>
<p>A better decodeURIComponent</p>
<p>Library home page: <a href="https://registry.npmjs.org/decode-uri-component/-/decode-uri-component-0.2.0.tgz">https://registry.npmjs.org/decode-uri-component/-/decode-uri-component-0.2.0.tgz</a></p>
<p>Path to dependency file: /backend/package.json</p>
<p>Path to vulnerable library: /backend/node_modules/decode-uri-component/package.json,/node_modules/decode-uri-component/package.json</p>
<p>
Dependency Hierarchy:
- css-3.0.0.tgz (Root Library)
- source-map-resolve-0.6.0.tgz
- :x: **decode-uri-component-0.2.0.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/ilan-WS/cloudify-stage/commit/50731d7b248d2728e4e5fda6648192e5a322f08c">50731d7b248d2728e4e5fda6648192e5a322f08c</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>
decode-uri-component 0.2.0 is vulnerable to Improper Input Validation resulting in DoS.
<p>Publish Date: 2022-11-28
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-38900>CVE-2022-38900</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>
| True | CVE-2022-38900 (High) detected in decode-uri-component-0.2.0.tgz - ## CVE-2022-38900 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>decode-uri-component-0.2.0.tgz</b></p></summary>
<p>A better decodeURIComponent</p>
<p>Library home page: <a href="https://registry.npmjs.org/decode-uri-component/-/decode-uri-component-0.2.0.tgz">https://registry.npmjs.org/decode-uri-component/-/decode-uri-component-0.2.0.tgz</a></p>
<p>Path to dependency file: /backend/package.json</p>
<p>Path to vulnerable library: /backend/node_modules/decode-uri-component/package.json,/node_modules/decode-uri-component/package.json</p>
<p>
Dependency Hierarchy:
- css-3.0.0.tgz (Root Library)
- source-map-resolve-0.6.0.tgz
- :x: **decode-uri-component-0.2.0.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/ilan-WS/cloudify-stage/commit/50731d7b248d2728e4e5fda6648192e5a322f08c">50731d7b248d2728e4e5fda6648192e5a322f08c</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>
decode-uri-component 0.2.0 is vulnerable to Improper Input Validation resulting in DoS.
<p>Publish Date: 2022-11-28
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-38900>CVE-2022-38900</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>
| non_priority | cve high detected in decode uri component tgz cve high severity vulnerability vulnerable library decode uri component tgz a better decodeuricomponent library home page a href path to dependency file backend package json path to vulnerable library backend node modules decode uri component package json node modules decode uri component package json dependency hierarchy css tgz root library source map resolve tgz x decode uri component tgz vulnerable library found in head commit a href found in base branch master vulnerability details decode uri component is vulnerable to improper input validation resulting in dos 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 | 0 |
97,879 | 12,265,232,504 | IssuesEvent | 2020-05-07 06:42:27 | JeschkeLab/DeerLab | https://api.github.com/repos/JeschkeLab/DeerLab | closed | statistics structure from bootan and sensitivan should be equal | design enhancement | Currently the ``bootan`` and `sensitivan` functions return a statistics structure `stats` which should contain the same fieldnames and information as both function should return the same type of confidence intervals, just with different origins. | 1.0 | statistics structure from bootan and sensitivan should be equal - Currently the ``bootan`` and `sensitivan` functions return a statistics structure `stats` which should contain the same fieldnames and information as both function should return the same type of confidence intervals, just with different origins. | non_priority | statistics structure from bootan and sensitivan should be equal currently the bootan and sensitivan functions return a statistics structure stats which should contain the same fieldnames and information as both function should return the same type of confidence intervals just with different origins | 0 |
13,314 | 10,199,209,957 | IssuesEvent | 2019-08-13 07:56:12 | RedisLabs/redislabs-docs | https://api.github.com/repos/RedisLabs/redislabs-docs | closed | Add clean line between code and note | bug infrastructure | **Current behavior** (A concise description of what you found)
When a code line is next to a note, there is no white space between the code grey box and the note grey box
**Expected behavior** (A concise description of what you expected to find)
There needs to be a separation between the code box and the note box to indicate that they are not connected.
**Screenshots** (If applicable, add screenshots of the problem)
https://docs.redislabs.com/latest/rs/getting-started/quick-setup/
**Additional context** (Add any other information)
This needs to be resolved in the Hugo style files | 1.0 | Add clean line between code and note - **Current behavior** (A concise description of what you found)
When a code line is next to a note, there is no white space between the code grey box and the note grey box
**Expected behavior** (A concise description of what you expected to find)
There needs to be a separation between the code box and the note box to indicate that they are not connected.
**Screenshots** (If applicable, add screenshots of the problem)
https://docs.redislabs.com/latest/rs/getting-started/quick-setup/
**Additional context** (Add any other information)
This needs to be resolved in the Hugo style files | non_priority | add clean line between code and note current behavior a concise description of what you found when a code line is next to a note there is no white space between the code grey box and the note grey box expected behavior a concise description of what you expected to find there needs to be a separation between the code box and the note box to indicate that they are not connected screenshots if applicable add screenshots of the problem additional context add any other information this needs to be resolved in the hugo style files | 0 |
204,949 | 23,293,362,122 | IssuesEvent | 2022-08-06 06:53:02 | billmcchesney1/singleton | https://api.github.com/repos/billmcchesney1/singleton | opened | CVE-2022-31197 (High) detected in postgresql-42.1.4.jar, postgresql-42.2.16.jar | security vulnerability | ## CVE-2022-31197 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>postgresql-42.1.4.jar</b>, <b>postgresql-42.2.16.jar</b></p></summary>
<p>
<details><summary><b>postgresql-42.1.4.jar</b></p></summary>
<p>Java JDBC 4.2 (JRE 8+) driver for PostgreSQL database</p>
<p>Library home page: <a href="https://github.com/pgjdbc/pgjdbc">https://github.com/pgjdbc/pgjdbc</a></p>
<p>Path to dependency file: /g11n-ws/modules/md-data-api-pgimpl/build.gradle</p>
<p>Path to vulnerable library: /canner/.gradle/caches/modules-2/files-2.1/org.postgresql/postgresql/42.1.4/1c7788d16b67d51f2f38ae99e474ece968bf715a/postgresql-42.1.4.jar</p>
<p>
Dependency Hierarchy:
- :x: **postgresql-42.1.4.jar** (Vulnerable Library)
</details>
<details><summary><b>postgresql-42.2.16.jar</b></p></summary>
<p>PostgreSQL JDBC Driver Postgresql</p>
<p>Library home page: <a href="https://jdbc.postgresql.org">https://jdbc.postgresql.org</a></p>
<p>Path to dependency file: /g11n-ws/modules/md-data-initdb/build.gradle</p>
<p>Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.postgresql/postgresql/42.2.16/a9ee12f737bd5dc7d046e4c065e391d38d6a3cfc/postgresql-42.2.16.jar</p>
<p>
Dependency Hierarchy:
- md-data-api-pgimpl-1.0 (Root Library)
- :x: **postgresql-42.2.16.jar** (Vulnerable Library)
</details>
<p>Found in HEAD commit: <a href="https://github.com/billmcchesney1/singleton/commit/2bb883ae0b199f3e432621e91d0f801cfc406a89">2bb883ae0b199f3e432621e91d0f801cfc406a89</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>
PostgreSQL JDBC Driver (PgJDBC for short) allows Java programs to connect to a PostgreSQL database using standard, database independent Java code. The PGJDBC implementation of the `java.sql.ResultRow.refreshRow()` method is not performing escaping of column names so a malicious column name that contains a statement terminator, e.g. `;`, could lead to SQL injection. This could lead to executing additional SQL commands as the application's JDBC user. User applications that do not invoke the `ResultSet.refreshRow()` method are not impacted. User application that do invoke that method are impacted if the underlying database that they are querying via their JDBC application may be under the control of an attacker. The attack requires the attacker to trick the user into executing SQL against a table name who's column names would contain the malicious SQL and subsequently invoke the `refreshRow()` method on the ResultSet. Note that the application's JDBC user and the schema owner need not be the same. A JDBC application that executes as a privileged user querying database schemas owned by potentially malicious less-privileged users would be vulnerable. In that situation it may be possible for the malicious user to craft a schema that causes the application to execute commands as the privileged user. Patched versions will be released as `42.2.26` and `42.4.1`. Users are advised to upgrade. There are no known workarounds for this issue.
<p>Publish Date: 2022-08-03
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-31197>CVE-2022-31197</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: Network
- Attack Complexity: High
- Privileges Required: Low
- User Interaction: Required
- 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://github.com/pgjdbc/pgjdbc/security/advisories/GHSA-r38f-c4h4-hqq2">https://github.com/pgjdbc/pgjdbc/security/advisories/GHSA-r38f-c4h4-hqq2</a></p>
<p>Release Date: 2022-08-03</p>
<p>Fix Resolution: 42.2.25.jre6</p>
</p>
</details>
<p></p>
***
<!-- REMEDIATE-OPEN-PR-START -->
- [ ] Check this box to open an automated fix PR
<!-- REMEDIATE-OPEN-PR-END -->
| True | CVE-2022-31197 (High) detected in postgresql-42.1.4.jar, postgresql-42.2.16.jar - ## CVE-2022-31197 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>postgresql-42.1.4.jar</b>, <b>postgresql-42.2.16.jar</b></p></summary>
<p>
<details><summary><b>postgresql-42.1.4.jar</b></p></summary>
<p>Java JDBC 4.2 (JRE 8+) driver for PostgreSQL database</p>
<p>Library home page: <a href="https://github.com/pgjdbc/pgjdbc">https://github.com/pgjdbc/pgjdbc</a></p>
<p>Path to dependency file: /g11n-ws/modules/md-data-api-pgimpl/build.gradle</p>
<p>Path to vulnerable library: /canner/.gradle/caches/modules-2/files-2.1/org.postgresql/postgresql/42.1.4/1c7788d16b67d51f2f38ae99e474ece968bf715a/postgresql-42.1.4.jar</p>
<p>
Dependency Hierarchy:
- :x: **postgresql-42.1.4.jar** (Vulnerable Library)
</details>
<details><summary><b>postgresql-42.2.16.jar</b></p></summary>
<p>PostgreSQL JDBC Driver Postgresql</p>
<p>Library home page: <a href="https://jdbc.postgresql.org">https://jdbc.postgresql.org</a></p>
<p>Path to dependency file: /g11n-ws/modules/md-data-initdb/build.gradle</p>
<p>Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.postgresql/postgresql/42.2.16/a9ee12f737bd5dc7d046e4c065e391d38d6a3cfc/postgresql-42.2.16.jar</p>
<p>
Dependency Hierarchy:
- md-data-api-pgimpl-1.0 (Root Library)
- :x: **postgresql-42.2.16.jar** (Vulnerable Library)
</details>
<p>Found in HEAD commit: <a href="https://github.com/billmcchesney1/singleton/commit/2bb883ae0b199f3e432621e91d0f801cfc406a89">2bb883ae0b199f3e432621e91d0f801cfc406a89</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>
PostgreSQL JDBC Driver (PgJDBC for short) allows Java programs to connect to a PostgreSQL database using standard, database independent Java code. The PGJDBC implementation of the `java.sql.ResultRow.refreshRow()` method is not performing escaping of column names so a malicious column name that contains a statement terminator, e.g. `;`, could lead to SQL injection. This could lead to executing additional SQL commands as the application's JDBC user. User applications that do not invoke the `ResultSet.refreshRow()` method are not impacted. User application that do invoke that method are impacted if the underlying database that they are querying via their JDBC application may be under the control of an attacker. The attack requires the attacker to trick the user into executing SQL against a table name who's column names would contain the malicious SQL and subsequently invoke the `refreshRow()` method on the ResultSet. Note that the application's JDBC user and the schema owner need not be the same. A JDBC application that executes as a privileged user querying database schemas owned by potentially malicious less-privileged users would be vulnerable. In that situation it may be possible for the malicious user to craft a schema that causes the application to execute commands as the privileged user. Patched versions will be released as `42.2.26` and `42.4.1`. Users are advised to upgrade. There are no known workarounds for this issue.
<p>Publish Date: 2022-08-03
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-31197>CVE-2022-31197</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: Network
- Attack Complexity: High
- Privileges Required: Low
- User Interaction: Required
- 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://github.com/pgjdbc/pgjdbc/security/advisories/GHSA-r38f-c4h4-hqq2">https://github.com/pgjdbc/pgjdbc/security/advisories/GHSA-r38f-c4h4-hqq2</a></p>
<p>Release Date: 2022-08-03</p>
<p>Fix Resolution: 42.2.25.jre6</p>
</p>
</details>
<p></p>
***
<!-- REMEDIATE-OPEN-PR-START -->
- [ ] Check this box to open an automated fix PR
<!-- REMEDIATE-OPEN-PR-END -->
| non_priority | cve high detected in postgresql jar postgresql jar cve high severity vulnerability vulnerable libraries postgresql jar postgresql jar postgresql jar java jdbc jre driver for postgresql database library home page a href path to dependency file ws modules md data api pgimpl build gradle path to vulnerable library canner gradle caches modules files org postgresql postgresql postgresql jar dependency hierarchy x postgresql jar vulnerable library postgresql jar postgresql jdbc driver postgresql library home page a href path to dependency file ws modules md data initdb build gradle path to vulnerable library home wss scanner gradle caches modules files org postgresql postgresql postgresql jar dependency hierarchy md data api pgimpl root library x postgresql jar vulnerable library found in head commit a href found in base branch master vulnerability details postgresql jdbc driver pgjdbc for short allows java programs to connect to a postgresql database using standard database independent java code the pgjdbc implementation of the java sql resultrow refreshrow method is not performing escaping of column names so a malicious column name that contains a statement terminator e g could lead to sql injection this could lead to executing additional sql commands as the application s jdbc user user applications that do not invoke the resultset refreshrow method are not impacted user application that do invoke that method are impacted if the underlying database that they are querying via their jdbc application may be under the control of an attacker the attack requires the attacker to trick the user into executing sql against a table name who s column names would contain the malicious sql and subsequently invoke the refreshrow method on the resultset note that the application s jdbc user and the schema owner need not be the same a jdbc application that executes as a privileged user querying database schemas owned by potentially malicious less privileged users would be vulnerable in that situation it may be possible for the malicious user to craft a schema that causes the application to execute commands as the privileged user patched versions will be released as and users are advised to upgrade there are no known workarounds for this issue publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity high privileges required low user interaction required 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 check this box to open an automated fix pr | 0 |
6,249 | 8,959,233,349 | IssuesEvent | 2019-01-27 20:45:41 | Simsys/LxpApi | https://api.github.com/repos/Simsys/LxpApi | closed | Should be usable in all Python 3 projects | Requirement Library | This means
- simple API
- as few external libraries as possible (exception: http://docs.python-requests.org)
- no special assumptions about the environment (e.g. loggign, GUI library, ...) | 1.0 | Should be usable in all Python 3 projects - This means
- simple API
- as few external libraries as possible (exception: http://docs.python-requests.org)
- no special assumptions about the environment (e.g. loggign, GUI library, ...) | non_priority | should be usable in all python projects this means simple api as few external libraries as possible exception no special assumptions about the environment e g loggign gui library | 0 |
118,382 | 25,298,244,570 | IssuesEvent | 2022-11-17 08:44:58 | Onelinerhub/onelinerhub | https://api.github.com/repos/Onelinerhub/onelinerhub | opened | Short solution needed: "Random forest" (python-scikit-learn) | help wanted good first issue code python-scikit-learn | Please help us write most modern and shortest code solution for this issue:
**Random forest** (technology: [python-scikit-learn](https://onelinerhub.com/python-scikit-learn))
### Fast way
Just write the code solution in the comments.
### Prefered way
1. Create [pull request](https://github.com/Onelinerhub/onelinerhub/blob/main/how-to-contribute.md) with a new code file inside [inbox folder](https://github.com/Onelinerhub/onelinerhub/tree/main/inbox).
2. Don't forget to [use comments](https://github.com/Onelinerhub/onelinerhub/blob/main/how-to-contribute.md#code-file-md-format) explain solution.
3. Link to this issue in comments of pull request. | 1.0 | Short solution needed: "Random forest" (python-scikit-learn) - Please help us write most modern and shortest code solution for this issue:
**Random forest** (technology: [python-scikit-learn](https://onelinerhub.com/python-scikit-learn))
### Fast way
Just write the code solution in the comments.
### Prefered way
1. Create [pull request](https://github.com/Onelinerhub/onelinerhub/blob/main/how-to-contribute.md) with a new code file inside [inbox folder](https://github.com/Onelinerhub/onelinerhub/tree/main/inbox).
2. Don't forget to [use comments](https://github.com/Onelinerhub/onelinerhub/blob/main/how-to-contribute.md#code-file-md-format) explain solution.
3. Link to this issue in comments of pull request. | non_priority | short solution needed random forest python scikit learn please help us write most modern and shortest code solution for this issue random forest technology fast way just write the code solution in the comments prefered way create with a new code file inside don t forget to explain solution link to this issue in comments of pull request | 0 |
267,983 | 28,565,357,252 | IssuesEvent | 2023-04-21 01:16:48 | Satheesh575555/frameworks_native_AOSP10_r33_CVE-2021-0332 | https://api.github.com/repos/Satheesh575555/frameworks_native_AOSP10_r33_CVE-2021-0332 | opened | CVE-2023-21094 (Medium) detected in multiple libraries | Mend: dependency security vulnerability | ## CVE-2023-21094 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>nativeandroid-10.0.0_r45</b>, <b>nativeandroid-10.0.0_r45</b>, <b>nativeandroid-10.0.0_r30</b></p></summary>
<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>
In sanitize of LayerState.cpp, there is a possible way to take over the screen display and swap the display content due to a missing permission check. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android-11 Android-12 Android-12L Android-13Android ID: A-248031255
<p>Publish Date: 2023-04-19
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2023-21094>CVE-2023-21094</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>
<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://android.googlesource.com/platform/frameworks/native/+/c710617ac6489a7f518c5138a78059a99f98e38d">https://android.googlesource.com/platform/frameworks/native/+/c710617ac6489a7f518c5138a78059a99f98e38d</a></p>
<p>Release Date: 2023-04-19</p>
<p>Fix Resolution: android-13.0.0_r38</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-2023-21094 (Medium) detected in multiple libraries - ## CVE-2023-21094 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>nativeandroid-10.0.0_r45</b>, <b>nativeandroid-10.0.0_r45</b>, <b>nativeandroid-10.0.0_r30</b></p></summary>
<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>
In sanitize of LayerState.cpp, there is a possible way to take over the screen display and swap the display content due to a missing permission check. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android-11 Android-12 Android-12L Android-13Android ID: A-248031255
<p>Publish Date: 2023-04-19
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2023-21094>CVE-2023-21094</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>
<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://android.googlesource.com/platform/frameworks/native/+/c710617ac6489a7f518c5138a78059a99f98e38d">https://android.googlesource.com/platform/frameworks/native/+/c710617ac6489a7f518c5138a78059a99f98e38d</a></p>
<p>Release Date: 2023-04-19</p>
<p>Fix Resolution: android-13.0.0_r38</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 multiple libraries cve medium severity vulnerability vulnerable libraries nativeandroid nativeandroid nativeandroid vulnerability details in sanitize of layerstate cpp there is a possible way to take over the screen display and swap the display content due to a missing permission check this could lead to local escalation of privilege with no additional execution privileges needed user interaction is not needed for exploitation product androidversions android android android android id a 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 suggested fix type upgrade version origin a href release date fix resolution android step up your open source security game with mend | 0 |
24,999 | 11,135,886,983 | IssuesEvent | 2019-12-20 15:22:15 | MicrosoftDocs/azure-docs | https://api.github.com/repos/MicrosoftDocs/azure-docs | closed | "Connections from inside Azure" should mention the option in Azure portal | Pri1 cxp doc-enhancement security/subsvc sql-database/svc triaged | It only noted "A firewall setting that has starting and ending IP addresses equal to 0.0.0.0 indicates that Azure connections are allowed," however it should mention this option is "Allow Azure services and resources to access this server" in Azure portal for firewall blade. Otherwise, people could miss the important note in that section.
---
#### Document Details
⚠ *Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.*
* ID: 79891897-a11e-6e20-9d41-e4fbbb84311e
* Version Independent ID: c8317b35-e80a-7f5d-51bf-7a26b2279595
* Content: [IP firewall rules - Azure SQL Database and SQL Data Warehouse](https://docs.microsoft.com/en-us/azure/sql-database/sql-database-firewall-configure#feedback)
* Content Source: [articles/sql-database/sql-database-firewall-configure.md](https://github.com/Microsoft/azure-docs/blob/master/articles/sql-database/sql-database-firewall-configure.md)
* Service: **sql-database**
* Sub-service: **security**
* GitHub Login: @VanMSFT
* Microsoft Alias: **vanto** | True | "Connections from inside Azure" should mention the option in Azure portal - It only noted "A firewall setting that has starting and ending IP addresses equal to 0.0.0.0 indicates that Azure connections are allowed," however it should mention this option is "Allow Azure services and resources to access this server" in Azure portal for firewall blade. Otherwise, people could miss the important note in that section.
---
#### Document Details
⚠ *Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.*
* ID: 79891897-a11e-6e20-9d41-e4fbbb84311e
* Version Independent ID: c8317b35-e80a-7f5d-51bf-7a26b2279595
* Content: [IP firewall rules - Azure SQL Database and SQL Data Warehouse](https://docs.microsoft.com/en-us/azure/sql-database/sql-database-firewall-configure#feedback)
* Content Source: [articles/sql-database/sql-database-firewall-configure.md](https://github.com/Microsoft/azure-docs/blob/master/articles/sql-database/sql-database-firewall-configure.md)
* Service: **sql-database**
* Sub-service: **security**
* GitHub Login: @VanMSFT
* Microsoft Alias: **vanto** | non_priority | connections from inside azure should mention the option in azure portal it only noted a firewall setting that has starting and ending ip addresses equal to indicates that azure connections are allowed however it should mention this option is allow azure services and resources to access this server in azure portal for firewall blade otherwise people could miss the important note in that section 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 sql database sub service security github login vanmsft microsoft alias vanto | 0 |
192,313 | 14,614,151,660 | IssuesEvent | 2020-12-22 09:26:24 | github-vet/rangeloop-pointer-findings | https://api.github.com/repos/github-vet/rangeloop-pointer-findings | closed | mrsplayground/OCI_TF_LAB1: oci/core_security_list_test.go; 16 LoC | fresh small test |
Found a possible issue in [mrsplayground/OCI_TF_LAB1](https://www.github.com/mrsplayground/OCI_TF_LAB1) at [oci/core_security_list_test.go](https://github.com/mrsplayground/OCI_TF_LAB1/blob/0754a23ebdf6429de9d286019594972a20306eda/oci/core_security_list_test.go#L587-L602)
Below is the message reported by the analyzer for this snippet of code. Beware that the analyzer only reports the first
issue it finds, so please do not limit your consideration to the contents of the below message.
> reference to vcnId is reassigned at line 588
[Click here to see the code in its original context.](https://github.com/mrsplayground/OCI_TF_LAB1/blob/0754a23ebdf6429de9d286019594972a20306eda/oci/core_security_list_test.go#L587-L602)
<details>
<summary>Click here to show the 16 line(s) of Go which triggered the analyzer.</summary>
```go
for _, vcnId := range vcnIds {
listSecurityListsRequest.VcnId = &vcnId
listSecurityListsRequest.LifecycleState = oci_core.SecurityListLifecycleStateAvailable
listSecurityListsResponse, err := virtualNetworkClient.ListSecurityLists(context.Background(), listSecurityListsRequest)
if err != nil {
return resourceIds, fmt.Errorf("Error getting SecurityList list for compartment id : %s , %s \n", compartmentId, err)
}
for _, securityList := range listSecurityListsResponse.Items {
id := *securityList.Id
resourceIds = append(resourceIds, id)
addResourceIdToSweeperResourceIdMap(compartmentId, "SecurityListId", id)
}
}
```
</details>
Leave a reaction on this issue to contribute to the project by classifying this instance as a **Bug** :-1:, **Mitigated** :+1:, or **Desirable Behavior** :rocket:
See the descriptions of the classifications [here](https://github.com/github-vet/rangeclosure-findings#how-can-i-help) for more information.
commit ID: 0754a23ebdf6429de9d286019594972a20306eda
| 1.0 | mrsplayground/OCI_TF_LAB1: oci/core_security_list_test.go; 16 LoC -
Found a possible issue in [mrsplayground/OCI_TF_LAB1](https://www.github.com/mrsplayground/OCI_TF_LAB1) at [oci/core_security_list_test.go](https://github.com/mrsplayground/OCI_TF_LAB1/blob/0754a23ebdf6429de9d286019594972a20306eda/oci/core_security_list_test.go#L587-L602)
Below is the message reported by the analyzer for this snippet of code. Beware that the analyzer only reports the first
issue it finds, so please do not limit your consideration to the contents of the below message.
> reference to vcnId is reassigned at line 588
[Click here to see the code in its original context.](https://github.com/mrsplayground/OCI_TF_LAB1/blob/0754a23ebdf6429de9d286019594972a20306eda/oci/core_security_list_test.go#L587-L602)
<details>
<summary>Click here to show the 16 line(s) of Go which triggered the analyzer.</summary>
```go
for _, vcnId := range vcnIds {
listSecurityListsRequest.VcnId = &vcnId
listSecurityListsRequest.LifecycleState = oci_core.SecurityListLifecycleStateAvailable
listSecurityListsResponse, err := virtualNetworkClient.ListSecurityLists(context.Background(), listSecurityListsRequest)
if err != nil {
return resourceIds, fmt.Errorf("Error getting SecurityList list for compartment id : %s , %s \n", compartmentId, err)
}
for _, securityList := range listSecurityListsResponse.Items {
id := *securityList.Id
resourceIds = append(resourceIds, id)
addResourceIdToSweeperResourceIdMap(compartmentId, "SecurityListId", id)
}
}
```
</details>
Leave a reaction on this issue to contribute to the project by classifying this instance as a **Bug** :-1:, **Mitigated** :+1:, or **Desirable Behavior** :rocket:
See the descriptions of the classifications [here](https://github.com/github-vet/rangeclosure-findings#how-can-i-help) for more information.
commit ID: 0754a23ebdf6429de9d286019594972a20306eda
| non_priority | mrsplayground oci tf oci core security list test go loc found a possible issue in at below is the message reported by the analyzer for this snippet of code beware that the analyzer only reports the first issue it finds so please do not limit your consideration to the contents of the below message reference to vcnid is reassigned at line click here to show the line s of go which triggered the analyzer go for vcnid range vcnids listsecuritylistsrequest vcnid vcnid listsecuritylistsrequest lifecyclestate oci core securitylistlifecyclestateavailable listsecuritylistsresponse err virtualnetworkclient listsecuritylists context background listsecuritylistsrequest if err nil return resourceids fmt errorf error getting securitylist list for compartment id s s n compartmentid err for securitylist range listsecuritylistsresponse items id securitylist id resourceids append resourceids id addresourceidtosweeperresourceidmap compartmentid securitylistid id leave a reaction on this issue to contribute to the project by classifying this instance as a bug mitigated or desirable behavior rocket see the descriptions of the classifications for more information commit id | 0 |
429,272 | 30,033,384,398 | IssuesEvent | 2023-06-27 11:07:05 | keep-starknet-strange/madara | https://api.github.com/repos/keep-starknet-strange/madara | opened | Full End-to-End Guide for Deploying on Sharingan Testnet | documentation enhancement good first issue | ---
**Describe the documentation you'd like**
A comprehensive, end-to-end guide for deploying on the Sharingan testnet. This guide should be broad and encompass various languages and SDKs, specifically starknet-rs, starknet-js, and starknet-py, among others. The objective of this guide is to provide developers with a clear understanding of how to deploy on the testnet using existing tooling and/or scripts in different languages.
**Preferred Format**
The guide should be easy to understand and should be formatted as follows:
1. **Introduction:** Brief about Sharingan testnet, its applications and its importance.
2. **Pre-requisites:** List of things/programs required before the process begins.
3. **Step-by-Step Instructions:** A step-by-step process on how to deploy on the testnet.
- Section for each language/SDK.
- Each step should have a brief explanation of what is happening.
- Code snippets for each step where applicable.
- Any images or diagrams that can be used to help illustrate the process.
4. **Troubleshooting:** Common errors and their solutions.
5. **Conclusion:** Final thoughts and a brief about what can be done after the deployment.
**Additional context or references**
Please include references or links to official resources that provide more detailed information about the Sharingan testnet and the specific SDKs (starknet-rs, starknet-js, starknet-py).
**Who can help?**
Anyone with experience deploying on the Sharingan testnet using one or more of the SDKs listed above is encouraged to contribute. If you are a developer with experience in one of these areas, please consider sharing your expertise to help create this guide.
Thank you!
| 1.0 | Full End-to-End Guide for Deploying on Sharingan Testnet - ---
**Describe the documentation you'd like**
A comprehensive, end-to-end guide for deploying on the Sharingan testnet. This guide should be broad and encompass various languages and SDKs, specifically starknet-rs, starknet-js, and starknet-py, among others. The objective of this guide is to provide developers with a clear understanding of how to deploy on the testnet using existing tooling and/or scripts in different languages.
**Preferred Format**
The guide should be easy to understand and should be formatted as follows:
1. **Introduction:** Brief about Sharingan testnet, its applications and its importance.
2. **Pre-requisites:** List of things/programs required before the process begins.
3. **Step-by-Step Instructions:** A step-by-step process on how to deploy on the testnet.
- Section for each language/SDK.
- Each step should have a brief explanation of what is happening.
- Code snippets for each step where applicable.
- Any images or diagrams that can be used to help illustrate the process.
4. **Troubleshooting:** Common errors and their solutions.
5. **Conclusion:** Final thoughts and a brief about what can be done after the deployment.
**Additional context or references**
Please include references or links to official resources that provide more detailed information about the Sharingan testnet and the specific SDKs (starknet-rs, starknet-js, starknet-py).
**Who can help?**
Anyone with experience deploying on the Sharingan testnet using one or more of the SDKs listed above is encouraged to contribute. If you are a developer with experience in one of these areas, please consider sharing your expertise to help create this guide.
Thank you!
| non_priority | full end to end guide for deploying on sharingan testnet describe the documentation you d like a comprehensive end to end guide for deploying on the sharingan testnet this guide should be broad and encompass various languages and sdks specifically starknet rs starknet js and starknet py among others the objective of this guide is to provide developers with a clear understanding of how to deploy on the testnet using existing tooling and or scripts in different languages preferred format the guide should be easy to understand and should be formatted as follows introduction brief about sharingan testnet its applications and its importance pre requisites list of things programs required before the process begins step by step instructions a step by step process on how to deploy on the testnet section for each language sdk each step should have a brief explanation of what is happening code snippets for each step where applicable any images or diagrams that can be used to help illustrate the process troubleshooting common errors and their solutions conclusion final thoughts and a brief about what can be done after the deployment additional context or references please include references or links to official resources that provide more detailed information about the sharingan testnet and the specific sdks starknet rs starknet js starknet py who can help anyone with experience deploying on the sharingan testnet using one or more of the sdks listed above is encouraged to contribute if you are a developer with experience in one of these areas please consider sharing your expertise to help create this guide thank you | 0 |
3,745 | 4,539,712,542 | IssuesEvent | 2016-09-09 12:12:32 | lysevi/dariadb | https://api.github.com/repos/lysevi/dariadb | opened | build refact | infrastructure | - [ ] optional build.
- [ ] - unit tests with optional depend. boost.unit_tests.
- [ ] - benchmarks.
- [ ] - network with optional depend. boost.asio.
- [ ] - engine can using as sub project witoh network. | 1.0 | build refact - - [ ] optional build.
- [ ] - unit tests with optional depend. boost.unit_tests.
- [ ] - benchmarks.
- [ ] - network with optional depend. boost.asio.
- [ ] - engine can using as sub project witoh network. | non_priority | build refact optional build unit tests with optional depend boost unit tests benchmarks network with optional depend boost asio engine can using as sub project witoh network | 0 |
11,234 | 13,219,491,461 | IssuesEvent | 2020-08-17 10:34:49 | AdguardTeam/AdguardForAndroid | https://api.github.com/repos/AdguardTeam/AdguardForAndroid | closed | com.akakce.akakce - broken app | Bug Compatibility | @adguard-bot commented on [Wed Dec 04 2019](https://github.com/AdguardTeam/AdguardFilters/issues/45407)
### Issue URL (Incorrect Blocking)
[https://play.google.com/store/apps/details?id=com.akakce.akakce](https://adguardteam.github.io/AnonymousRedirect/redirect.html?url=https%3A%2F%2Fplay.google.com%2Fstore%2Fapps%2Fdetails%3Fid%3Dcom.akakce.akakce)
### Comment
> First "HTTPS Filtering is disabled for this app"
> Second I disabled DNS filtering.
> First screenshots shows the welcome page of the app never loads with filtering enabled. after disabling filtering, then the page loads. Please fix it. Thanks
### Screenshots
<details>
<summary>Screenshot 1</summary>
</details>
<details>
<summary>Screenshot 2</summary>
</details>
### System configuration
Information | value
--- | ---
Platform: | And 8.0.0
AdGuard version: | 3.3 beta 2 (102)
Stealth mode options: | Strip URLs from tracking parameters, Self-destructing third-party cookies (0)
AdGuard mode: | VPN
Filtering quality: | High-quality
HTTPS filtering: | enabled
DNS requests blocking: | enabled
Filters: | <b>Ad Blocking:</b><br/> AdGuard Base, <br/>AdGuard Mobile Ads<br/><br/><b>Privacy:</b><br/> AdGuard Tracking Protection<br/><br/><b>Social Widgets:</b><br/> AdGuard Social Media<br/><br/><b>Annoyances:</b><br/> AdGuard Annoyances<br/><br/><b>Language-specific:</b><br/> AdGuard Turkish
| True | com.akakce.akakce - broken app - @adguard-bot commented on [Wed Dec 04 2019](https://github.com/AdguardTeam/AdguardFilters/issues/45407)
### Issue URL (Incorrect Blocking)
[https://play.google.com/store/apps/details?id=com.akakce.akakce](https://adguardteam.github.io/AnonymousRedirect/redirect.html?url=https%3A%2F%2Fplay.google.com%2Fstore%2Fapps%2Fdetails%3Fid%3Dcom.akakce.akakce)
### Comment
> First "HTTPS Filtering is disabled for this app"
> Second I disabled DNS filtering.
> First screenshots shows the welcome page of the app never loads with filtering enabled. after disabling filtering, then the page loads. Please fix it. Thanks
### Screenshots
<details>
<summary>Screenshot 1</summary>
</details>
<details>
<summary>Screenshot 2</summary>
</details>
### System configuration
Information | value
--- | ---
Platform: | And 8.0.0
AdGuard version: | 3.3 beta 2 (102)
Stealth mode options: | Strip URLs from tracking parameters, Self-destructing third-party cookies (0)
AdGuard mode: | VPN
Filtering quality: | High-quality
HTTPS filtering: | enabled
DNS requests blocking: | enabled
Filters: | <b>Ad Blocking:</b><br/> AdGuard Base, <br/>AdGuard Mobile Ads<br/><br/><b>Privacy:</b><br/> AdGuard Tracking Protection<br/><br/><b>Social Widgets:</b><br/> AdGuard Social Media<br/><br/><b>Annoyances:</b><br/> AdGuard Annoyances<br/><br/><b>Language-specific:</b><br/> AdGuard Turkish
| non_priority | com akakce akakce broken app adguard bot commented on issue url incorrect blocking comment first https filtering is disabled for this app second i disabled dns filtering first screenshots shows the welcome page of the app never loads with filtering enabled after disabling filtering then the page loads please fix it thanks screenshots screenshot screenshot system configuration information value platform and adguard version beta stealth mode options strip urls from tracking parameters self destructing third party cookies adguard mode vpn filtering quality high quality https filtering enabled dns requests blocking enabled filters ad blocking adguard base adguard mobile ads privacy adguard tracking protection social widgets adguard social media annoyances adguard annoyances language specific adguard turkish | 0 |
175,295 | 13,543,801,317 | IssuesEvent | 2020-09-16 19:33:36 | thefrontside/bigtest | https://api.github.com/repos/thefrontside/bigtest | closed | Better server console output | @bigtest/bundler @bigtest/server enhancement | I've come across a few inconveniences regarding the server console output while writing tests. I'm not entirely sure if they're related to the `server` itself or if it's the `bundler` or `orchestrator` but I'll list them here:
1. When there's an error from building the manifest, the errors are overwhelming to the user and it would be really nice if we could shave it down to the most essential errors. Not only is each of the individual errors long in content but they get spammed in the console. Here's a screenshot of what one of those errors looks like in the console:
2. And when those errors are addressed, the server console doesn't refresh itself to say "everything is good now". It just stays on the error so I'm constantly wondering if there are more errors.
3. It would be nice to see how many test suites bigtest is able to detect. Sometimes in order to run a test file in isolation, I will specify the file I want in `bigtest.json` but if there's a typo, running the test command will just linger without letting the user know that there are no tests detected. It could make users jump to the conclusion that Bigtest is stalling and takes a few moments before I consider the possibility that I made a typo.
4. Related to the second point, how can we refresh the server console whenever a test file is updated? I'll run the tests, make changes to a test, save the file, re-run the test. But if that's done too quickly before the server is done refreshing, it'll run the old test suite. I've been remembering the number of steps and assertions from the previous run to confirm that bigtest ran the most updated version of my test but in cases where there are no new steps/assertions, I don't have any way of confirming if bigtest ran the newest test suite or its previous iteration. This particular issue slows down my test-writing process.
- Again I'm not sure if this is viable but perhaps whenever the server detects a file has changed, it can update its status to "Updating..." and when finished updating it could provide a unique ID of some sort so that when I run tests in a separate terminal, it can display that ID to confirm that the test run is indeed after the refresh with the new files? 🤷 | 2.0 | Better server console output - I've come across a few inconveniences regarding the server console output while writing tests. I'm not entirely sure if they're related to the `server` itself or if it's the `bundler` or `orchestrator` but I'll list them here:
1. When there's an error from building the manifest, the errors are overwhelming to the user and it would be really nice if we could shave it down to the most essential errors. Not only is each of the individual errors long in content but they get spammed in the console. Here's a screenshot of what one of those errors looks like in the console:
2. And when those errors are addressed, the server console doesn't refresh itself to say "everything is good now". It just stays on the error so I'm constantly wondering if there are more errors.
3. It would be nice to see how many test suites bigtest is able to detect. Sometimes in order to run a test file in isolation, I will specify the file I want in `bigtest.json` but if there's a typo, running the test command will just linger without letting the user know that there are no tests detected. It could make users jump to the conclusion that Bigtest is stalling and takes a few moments before I consider the possibility that I made a typo.
4. Related to the second point, how can we refresh the server console whenever a test file is updated? I'll run the tests, make changes to a test, save the file, re-run the test. But if that's done too quickly before the server is done refreshing, it'll run the old test suite. I've been remembering the number of steps and assertions from the previous run to confirm that bigtest ran the most updated version of my test but in cases where there are no new steps/assertions, I don't have any way of confirming if bigtest ran the newest test suite or its previous iteration. This particular issue slows down my test-writing process.
- Again I'm not sure if this is viable but perhaps whenever the server detects a file has changed, it can update its status to "Updating..." and when finished updating it could provide a unique ID of some sort so that when I run tests in a separate terminal, it can display that ID to confirm that the test run is indeed after the refresh with the new files? 🤷 | non_priority | better server console output i ve come across a few inconveniences regarding the server console output while writing tests i m not entirely sure if they re related to the server itself or if it s the bundler or orchestrator but i ll list them here when there s an error from building the manifest the errors are overwhelming to the user and it would be really nice if we could shave it down to the most essential errors not only is each of the individual errors long in content but they get spammed in the console here s a screenshot of what one of those errors looks like in the console and when those errors are addressed the server console doesn t refresh itself to say everything is good now it just stays on the error so i m constantly wondering if there are more errors it would be nice to see how many test suites bigtest is able to detect sometimes in order to run a test file in isolation i will specify the file i want in bigtest json but if there s a typo running the test command will just linger without letting the user know that there are no tests detected it could make users jump to the conclusion that bigtest is stalling and takes a few moments before i consider the possibility that i made a typo related to the second point how can we refresh the server console whenever a test file is updated i ll run the tests make changes to a test save the file re run the test but if that s done too quickly before the server is done refreshing it ll run the old test suite i ve been remembering the number of steps and assertions from the previous run to confirm that bigtest ran the most updated version of my test but in cases where there are no new steps assertions i don t have any way of confirming if bigtest ran the newest test suite or its previous iteration this particular issue slows down my test writing process again i m not sure if this is viable but perhaps whenever the server detects a file has changed it can update its status to updating and when finished updating it could provide a unique id of some sort so that when i run tests in a separate terminal it can display that id to confirm that the test run is indeed after the refresh with the new files 🤷 | 0 |
89,018 | 8,183,649,000 | IssuesEvent | 2018-08-29 09:40:48 | humera987/HumTestData | https://api.github.com/repos/humera987/HumTestData | opened | testing_test : ApiV1OrgsGetInvalidDatatypePagesize | testing_test | Project : testing_test
Job : UAT
Env : UAT
Region : FXLabs/US_WEST_1
Result : fail
Status Code : 401
Headers : {WWW-Authenticate=[Basic realm="Realm", Basic realm="Realm"], X-Content-Type-Options=[nosniff], X-XSS-Protection=[1; mode=block], Cache-Control=[no-cache, no-store, max-age=0, must-revalidate], Pragma=[no-cache], Expires=[0], X-Frame-Options=[DENY], Content-Length=[0], Date=[Wed, 29 Aug 2018 09:40:46 GMT]}
Endpoint : http://13.56.210.25/api/v1/orgs?pageSize=cImV0L
Request :
Response :
null
Logs :
Assertion [@StatusCode != 404] passed, not expecting [404] and found [401]Assertion [@StatusCode != 401] failed, not expecting [401] but found [401]
--- FX Bot --- | 2.0 | testing_test : ApiV1OrgsGetInvalidDatatypePagesize - Project : testing_test
Job : UAT
Env : UAT
Region : FXLabs/US_WEST_1
Result : fail
Status Code : 401
Headers : {WWW-Authenticate=[Basic realm="Realm", Basic realm="Realm"], X-Content-Type-Options=[nosniff], X-XSS-Protection=[1; mode=block], Cache-Control=[no-cache, no-store, max-age=0, must-revalidate], Pragma=[no-cache], Expires=[0], X-Frame-Options=[DENY], Content-Length=[0], Date=[Wed, 29 Aug 2018 09:40:46 GMT]}
Endpoint : http://13.56.210.25/api/v1/orgs?pageSize=cImV0L
Request :
Response :
null
Logs :
Assertion [@StatusCode != 404] passed, not expecting [404] and found [401]Assertion [@StatusCode != 401] failed, not expecting [401] but found [401]
--- FX Bot --- | non_priority | testing test project testing test job uat env uat region fxlabs us west result fail status code headers www authenticate x content type options x xss protection cache control pragma expires x frame options content length date endpoint request response null logs assertion passed not expecting and found assertion failed not expecting but found fx bot | 0 |
109,928 | 16,938,166,669 | IssuesEvent | 2021-06-27 01:07:36 | hashier/test-bazel-go | https://api.github.com/repos/hashier/test-bazel-go | opened | CVE-2021-28169 (Medium) detected in jetty-server-9.0.7.v20131107.jar | security vulnerability | ## CVE-2021-28169 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>jetty-server-9.0.7.v20131107.jar</b></p></summary>
<p>The core jetty server artifact.</p>
<p>Library home page: <a href="http://www.eclipse.org/jetty">http://www.eclipse.org/jetty</a></p>
<p>Path to dependency file: /tmp/ws-scm/test-bolt/build.gradle</p>
<p>Path to vulnerable library: /root/.gradle/caches/modules-2/files-2.1/org.eclipse.jetty/jetty-server/9.0.7.v20131107/682ae23f9e4a5e397d96f215b62641755d2a59b7/jetty-server-9.0.7.v20131107.jar,/root/.gradle/caches/modules-2/files-2.1/org.eclipse.jetty/jetty-server/9.0.7.v20131107/682ae23f9e4a5e397d96f215b62641755d2a59b7/jetty-server-9.0.7.v20131107.jar</p>
<p>
Dependency Hierarchy:
- dropwizard-core-0.7.1.jar (Root Library)
- dropwizard-metrics-0.7.1.jar
- dropwizard-lifecycle-0.7.1.jar
- :x: **jetty-server-9.0.7.v20131107.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>
For Eclipse Jetty versions <= 9.4.40, <= 10.0.2, <= 11.0.2, it is possible for requests to the ConcatServlet with a doubly encoded path to access protected resources within the WEB-INF directory. For example a request to `/concat?/%2557EB-INF/web.xml` can retrieve the web.xml file. This can reveal sensitive information regarding the implementation of a web application.
<p>Publish Date: 2021-06-09
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-28169>CVE-2021-28169</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.3</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: Low
- 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/eclipse/jetty.project/security/advisories/GHSA-gwcr-j4wh-j3cq">https://github.com/eclipse/jetty.project/security/advisories/GHSA-gwcr-j4wh-j3cq</a></p>
<p>Release Date: 2021-06-09</p>
<p>Fix Resolution: org.eclipse.jetty:jetty-runner:9.4.41.v20210516, 10.0.3, 11.0.3, org.eclipse.jetty:jetty-http:9.4.41.v20210516, 10.0.3, 11.0.3,org.eclipse.jetty:jetty-servlets:9.4.41.v20210516, 10.0.3, 11.0.3, org.eclipse.jetty:jetty-server:9.4.41.v20210516, 10.0.3, 11.0.3</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-2021-28169 (Medium) detected in jetty-server-9.0.7.v20131107.jar - ## CVE-2021-28169 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>jetty-server-9.0.7.v20131107.jar</b></p></summary>
<p>The core jetty server artifact.</p>
<p>Library home page: <a href="http://www.eclipse.org/jetty">http://www.eclipse.org/jetty</a></p>
<p>Path to dependency file: /tmp/ws-scm/test-bolt/build.gradle</p>
<p>Path to vulnerable library: /root/.gradle/caches/modules-2/files-2.1/org.eclipse.jetty/jetty-server/9.0.7.v20131107/682ae23f9e4a5e397d96f215b62641755d2a59b7/jetty-server-9.0.7.v20131107.jar,/root/.gradle/caches/modules-2/files-2.1/org.eclipse.jetty/jetty-server/9.0.7.v20131107/682ae23f9e4a5e397d96f215b62641755d2a59b7/jetty-server-9.0.7.v20131107.jar</p>
<p>
Dependency Hierarchy:
- dropwizard-core-0.7.1.jar (Root Library)
- dropwizard-metrics-0.7.1.jar
- dropwizard-lifecycle-0.7.1.jar
- :x: **jetty-server-9.0.7.v20131107.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>
For Eclipse Jetty versions <= 9.4.40, <= 10.0.2, <= 11.0.2, it is possible for requests to the ConcatServlet with a doubly encoded path to access protected resources within the WEB-INF directory. For example a request to `/concat?/%2557EB-INF/web.xml` can retrieve the web.xml file. This can reveal sensitive information regarding the implementation of a web application.
<p>Publish Date: 2021-06-09
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-28169>CVE-2021-28169</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.3</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: Low
- 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/eclipse/jetty.project/security/advisories/GHSA-gwcr-j4wh-j3cq">https://github.com/eclipse/jetty.project/security/advisories/GHSA-gwcr-j4wh-j3cq</a></p>
<p>Release Date: 2021-06-09</p>
<p>Fix Resolution: org.eclipse.jetty:jetty-runner:9.4.41.v20210516, 10.0.3, 11.0.3, org.eclipse.jetty:jetty-http:9.4.41.v20210516, 10.0.3, 11.0.3,org.eclipse.jetty:jetty-servlets:9.4.41.v20210516, 10.0.3, 11.0.3, org.eclipse.jetty:jetty-server:9.4.41.v20210516, 10.0.3, 11.0.3</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 jetty server jar cve medium severity vulnerability vulnerable library jetty server jar the core jetty server artifact library home page a href path to dependency file tmp ws scm test bolt build gradle path to vulnerable library root gradle caches modules files org eclipse jetty jetty server jetty server jar root gradle caches modules files org eclipse jetty jetty server jetty server jar dependency hierarchy dropwizard core jar root library dropwizard metrics jar dropwizard lifecycle jar x jetty server jar vulnerable library vulnerability details for eclipse jetty versions it is possible for requests to the concatservlet with a doubly encoded path to access protected resources within the web inf directory for example a request to concat inf web xml can retrieve the web xml file this can reveal sensitive information regarding the implementation of a web application 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 low 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 org eclipse jetty jetty runner org eclipse jetty jetty http org eclipse jetty jetty servlets org eclipse jetty jetty server step up your open source security game with whitesource | 0 |
230,962 | 17,658,354,791 | IssuesEvent | 2021-08-21 02:11:40 | drakearch/kaggle-courses | https://api.github.com/repos/drakearch/kaggle-courses | closed | Microchallenges | documentation Learning | Ultra-short challenges to build and test your skill
- [x] Blackjack Microchallenge
- [x] Airline Price Optimization Micro-Challenge | 1.0 | Microchallenges - Ultra-short challenges to build and test your skill
- [x] Blackjack Microchallenge
- [x] Airline Price Optimization Micro-Challenge | non_priority | microchallenges ultra short challenges to build and test your skill blackjack microchallenge airline price optimization micro challenge | 0 |
46,878 | 24,764,377,481 | IssuesEvent | 2022-10-22 10:12:40 | Dudrie/Tutor-Management-System | https://api.github.com/repos/Dudrie/Tutor-Management-System | closed | Change DB to SQL | 🗄 server 📚 collection 📦 dependencies 🚀 performance | ## 🏁 Goal
Change the database used to a SQL database.
## ✔ ToDos
- [x] ~~Decide which SQL database to use (mysql vs postgres vs mariadb).~~
~~Postgres~~, MySQL
- [x] Add [Mikro-ORM](https://mikro-orm.io/docs/installation/) and the corresponding SQL dependency.
- [x] Add pre/post hooks
- [x] Add encryption to sensitive data
- [x] Add the `@mirko-orm/nestjs` package ([instructions here](https://mikro-orm.io/docs/usage-with-nestjs)) and properly initialized the `MikroOrmModule`.
- [x] Add entities for the database entities needed (those will replace the former mongoose documents).
- [x] ~~Introduce proper repositories.~~ Using injected repositories makes things more complicated, because the Mikro-ORM NestJS package can not autoload entities from a directory and make those entities' repositories injectable...
- [x] Adjust services to use the entities & repositories instead of the documents.
- [x] Adjust session to use the SQL database.
- [x] Rewrite tests to use an ~~in-memory~~ SQL database.
In theory only the initialization and clean up of the tests should be affected (can those be simplified through some helpers additionally?).
- [x] Remove mongoose documents & all MongoDB related dependencies.
- [x] Adjust GitHub actions ~~if neccessary~~
- [x] Adjust action for unit tests.
- [x] The docker-test workflow should need adjustments but those should be the same adjustments needed for the docker-compose file in the documentation.
- [x] Adjust documentation, especially the installation page.
- [ ] `findAll()` methods in all (?) services should not use `populate: true`
This makes retrieving the entities from the DB really slow. Instead they should only populate the fields actually necessary for the part calling the `findAll()` method.
- [x] Re-add fixes from main since 2.3.5: [Compare changes](https://github.com/Dudrie/Tutor-Management-System/compare/issue-957-Change_DB_to_SQL...main)
- [ ] Test deployment version.
## 💡 Reason
The reason behind this is that the usage of a non-SQL database (like MongoDB) proofed to be not optimal for the use case at hand.
Especially later during a term the time it takes to read a student with all it's gradings from the DB increases significantly due to the way students & gradings are structured.
The structuring of the gradings (ie put them into the students) can not be changed due to the fact that multiple students can have the same grading.
SQL databases should provide a more consistent and faster solution for this task due to the ability to perform joins over multiple tables.
| True | Change DB to SQL - ## 🏁 Goal
Change the database used to a SQL database.
## ✔ ToDos
- [x] ~~Decide which SQL database to use (mysql vs postgres vs mariadb).~~
~~Postgres~~, MySQL
- [x] Add [Mikro-ORM](https://mikro-orm.io/docs/installation/) and the corresponding SQL dependency.
- [x] Add pre/post hooks
- [x] Add encryption to sensitive data
- [x] Add the `@mirko-orm/nestjs` package ([instructions here](https://mikro-orm.io/docs/usage-with-nestjs)) and properly initialized the `MikroOrmModule`.
- [x] Add entities for the database entities needed (those will replace the former mongoose documents).
- [x] ~~Introduce proper repositories.~~ Using injected repositories makes things more complicated, because the Mikro-ORM NestJS package can not autoload entities from a directory and make those entities' repositories injectable...
- [x] Adjust services to use the entities & repositories instead of the documents.
- [x] Adjust session to use the SQL database.
- [x] Rewrite tests to use an ~~in-memory~~ SQL database.
In theory only the initialization and clean up of the tests should be affected (can those be simplified through some helpers additionally?).
- [x] Remove mongoose documents & all MongoDB related dependencies.
- [x] Adjust GitHub actions ~~if neccessary~~
- [x] Adjust action for unit tests.
- [x] The docker-test workflow should need adjustments but those should be the same adjustments needed for the docker-compose file in the documentation.
- [x] Adjust documentation, especially the installation page.
- [ ] `findAll()` methods in all (?) services should not use `populate: true`
This makes retrieving the entities from the DB really slow. Instead they should only populate the fields actually necessary for the part calling the `findAll()` method.
- [x] Re-add fixes from main since 2.3.5: [Compare changes](https://github.com/Dudrie/Tutor-Management-System/compare/issue-957-Change_DB_to_SQL...main)
- [ ] Test deployment version.
## 💡 Reason
The reason behind this is that the usage of a non-SQL database (like MongoDB) proofed to be not optimal for the use case at hand.
Especially later during a term the time it takes to read a student with all it's gradings from the DB increases significantly due to the way students & gradings are structured.
The structuring of the gradings (ie put them into the students) can not be changed due to the fact that multiple students can have the same grading.
SQL databases should provide a more consistent and faster solution for this task due to the ability to perform joins over multiple tables.
| non_priority | change db to sql 🏁 goal change the database used to a sql database ✔ todos decide which sql database to use mysql vs postgres vs mariadb postgres mysql add and the corresponding sql dependency add pre post hooks add encryption to sensitive data add the mirko orm nestjs package and properly initialized the mikroormmodule add entities for the database entities needed those will replace the former mongoose documents introduce proper repositories using injected repositories makes things more complicated because the mikro orm nestjs package can not autoload entities from a directory and make those entities repositories injectable adjust services to use the entities repositories instead of the documents adjust session to use the sql database rewrite tests to use an in memory sql database in theory only the initialization and clean up of the tests should be affected can those be simplified through some helpers additionally remove mongoose documents all mongodb related dependencies adjust github actions if neccessary adjust action for unit tests the docker test workflow should need adjustments but those should be the same adjustments needed for the docker compose file in the documentation adjust documentation especially the installation page findall methods in all services should not use populate true this makes retrieving the entities from the db really slow instead they should only populate the fields actually necessary for the part calling the findall method re add fixes from main since test deployment version 💡 reason the reason behind this is that the usage of a non sql database like mongodb proofed to be not optimal for the use case at hand especially later during a term the time it takes to read a student with all it s gradings from the db increases significantly due to the way students gradings are structured the structuring of the gradings ie put them into the students can not be changed due to the fact that multiple students can have the same grading sql databases should provide a more consistent and faster solution for this task due to the ability to perform joins over multiple tables | 0 |
63,244 | 17,483,406,296 | IssuesEvent | 2021-08-09 07:43:46 | hazelcast/hazelcast | https://api.github.com/repos/hazelcast/hazelcast | closed | Serializer[com.hazelcast.internal.serialization.impl.defaultserializers.JavaDefaultSerializers$JavaSerializer@13352000] has been already registered for type: class hzcmd.model.person.PersonExternalizable java.lang.IllegalStateException | Type: Defect Team: Client Team: Core Source: Internal Module: Serialization |
Failed http://jenkins.hazelcast.com/view/kill/job/kill-sql/73/console
```
15:40:02 /home/ec2-user/workspace/kill-sql/4.2-SNAPSHOT/2021_03_15-15_35_08/sql/bit-map Failed
15:40:02 fail HzClient3HZ put-mapBak1Obj hzcmd.map.PutRandomStylePerson threadId=0 com.hazelcast.nio.serialization.HazelcastSerializationException: Failed to serialize 'hzcmd.model.person.PersonExternalizable' [0m
15:40:03 http://3.87.100.12/~/home/ec2-user/workspace/kill-sql/4.2-SNAPSHOT/2021_03_15-15_35_08/sql/bit-map
```
but very next run passed
Padded http://jenkins.hazelcast.com/view/kill/job/kill-sql/74/console
```
16:31:22 /home/ec2-user/workspace/kill-sql/4.2-SNAPSHOT/2021_03_15-16_26_18/sql/bit-map Passed
16:31:22 http://3.87.100.12/~/home/ec2-user/workspace/kill-sql/4.2-SNAPSHOT/2021_03_15-16_26_18/sql/bit-map
```
java.lang.IllegalStateException: Serializer[com.hazelcast.internal.serialization.impl.defaultserializers.JavaDefaultSerializers$JavaSerializer@13352000] has been already registered for type: class ......
could there be some kind of race condition hear ?
```
com.hazelcast.nio.serialization.HazelcastSerializationException: Failed to serialize 'hzcmd.model.person.PersonExternalizable'
at com.hazelcast.internal.serialization.impl.SerializationUtil.handleSerializeException(SerializationUtil.java:115)
at com.hazelcast.internal.serialization.impl.AbstractSerializationService.toBytes(AbstractSerializationService.java:178)
at com.hazelcast.internal.serialization.impl.AbstractSerializationService.toBytes(AbstractSerializationService.java:154)
at com.hazelcast.internal.serialization.impl.AbstractSerializationService.toData(AbstractSerializationService.java:139)
at com.hazelcast.internal.serialization.impl.AbstractSerializationService.toData(AbstractSerializationService.java:127)
at com.hazelcast.client.impl.spi.ClientProxy.toData(ClientProxy.java:76)
at com.hazelcast.client.impl.proxy.ClientMapProxy.putInternal(ClientMapProxy.java:525)
at com.hazelcast.client.impl.proxy.ClientMapProxy.put(ClientMapProxy.java:266)
at hzcmd.map.PutRandomStylePerson.timeStep(PutRandomStylePerson.java:12)
at remote.bench.marker.RollMarker.flatOut(RollMarker.java:72)
at remote.bench.marker.RollMarker.bench(RollMarker.java:59)
at remote.bench.BenchThread.call(BenchThread.java:41)
at remote.bench.BenchThread.call(BenchThread.java:14)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
at java.base/java.lang.Thread.run(Thread.java:829)
Caused by: java.lang.IllegalStateException: Serializer[com.hazelcast.internal.serialization.impl.defaultserializers.JavaDefaultSerializers$JavaSerializer@13352000] has been already registered for type: class hzcmd.model.person.PersonExternalizable
at com.hazelcast.internal.serialization.impl.AbstractSerializationService.safeRegister(AbstractSerializationService.java:441)
at com.hazelcast.internal.serialization.impl.AbstractSerializationService.lookupJavaSerializer(AbstractSerializationService.java:581)
at com.hazelcast.internal.serialization.impl.AbstractSerializationService.serializerFor(AbstractSerializationService.java:508)
at com.hazelcast.internal.serialization.impl.AbstractSerializationService.toBytes(AbstractSerializationService.java:167)
... 17 more
``` | 1.0 | Serializer[com.hazelcast.internal.serialization.impl.defaultserializers.JavaDefaultSerializers$JavaSerializer@13352000] has been already registered for type: class hzcmd.model.person.PersonExternalizable java.lang.IllegalStateException -
Failed http://jenkins.hazelcast.com/view/kill/job/kill-sql/73/console
```
15:40:02 /home/ec2-user/workspace/kill-sql/4.2-SNAPSHOT/2021_03_15-15_35_08/sql/bit-map Failed
15:40:02 fail HzClient3HZ put-mapBak1Obj hzcmd.map.PutRandomStylePerson threadId=0 com.hazelcast.nio.serialization.HazelcastSerializationException: Failed to serialize 'hzcmd.model.person.PersonExternalizable' [0m
15:40:03 http://3.87.100.12/~/home/ec2-user/workspace/kill-sql/4.2-SNAPSHOT/2021_03_15-15_35_08/sql/bit-map
```
but very next run passed
Padded http://jenkins.hazelcast.com/view/kill/job/kill-sql/74/console
```
16:31:22 /home/ec2-user/workspace/kill-sql/4.2-SNAPSHOT/2021_03_15-16_26_18/sql/bit-map Passed
16:31:22 http://3.87.100.12/~/home/ec2-user/workspace/kill-sql/4.2-SNAPSHOT/2021_03_15-16_26_18/sql/bit-map
```
java.lang.IllegalStateException: Serializer[com.hazelcast.internal.serialization.impl.defaultserializers.JavaDefaultSerializers$JavaSerializer@13352000] has been already registered for type: class ......
could there be some kind of race condition hear ?
```
com.hazelcast.nio.serialization.HazelcastSerializationException: Failed to serialize 'hzcmd.model.person.PersonExternalizable'
at com.hazelcast.internal.serialization.impl.SerializationUtil.handleSerializeException(SerializationUtil.java:115)
at com.hazelcast.internal.serialization.impl.AbstractSerializationService.toBytes(AbstractSerializationService.java:178)
at com.hazelcast.internal.serialization.impl.AbstractSerializationService.toBytes(AbstractSerializationService.java:154)
at com.hazelcast.internal.serialization.impl.AbstractSerializationService.toData(AbstractSerializationService.java:139)
at com.hazelcast.internal.serialization.impl.AbstractSerializationService.toData(AbstractSerializationService.java:127)
at com.hazelcast.client.impl.spi.ClientProxy.toData(ClientProxy.java:76)
at com.hazelcast.client.impl.proxy.ClientMapProxy.putInternal(ClientMapProxy.java:525)
at com.hazelcast.client.impl.proxy.ClientMapProxy.put(ClientMapProxy.java:266)
at hzcmd.map.PutRandomStylePerson.timeStep(PutRandomStylePerson.java:12)
at remote.bench.marker.RollMarker.flatOut(RollMarker.java:72)
at remote.bench.marker.RollMarker.bench(RollMarker.java:59)
at remote.bench.BenchThread.call(BenchThread.java:41)
at remote.bench.BenchThread.call(BenchThread.java:14)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
at java.base/java.lang.Thread.run(Thread.java:829)
Caused by: java.lang.IllegalStateException: Serializer[com.hazelcast.internal.serialization.impl.defaultserializers.JavaDefaultSerializers$JavaSerializer@13352000] has been already registered for type: class hzcmd.model.person.PersonExternalizable
at com.hazelcast.internal.serialization.impl.AbstractSerializationService.safeRegister(AbstractSerializationService.java:441)
at com.hazelcast.internal.serialization.impl.AbstractSerializationService.lookupJavaSerializer(AbstractSerializationService.java:581)
at com.hazelcast.internal.serialization.impl.AbstractSerializationService.serializerFor(AbstractSerializationService.java:508)
at com.hazelcast.internal.serialization.impl.AbstractSerializationService.toBytes(AbstractSerializationService.java:167)
... 17 more
``` | non_priority | serializer has been already registered for type class hzcmd model person personexternalizable java lang illegalstateexception failed home user workspace kill sql snapshot sql bit map failed fail put hzcmd map putrandomstyleperson threadid com hazelcast nio serialization hazelcastserializationexception failed to serialize hzcmd model person personexternalizable but very next run passed padded home user workspace kill sql snapshot sql bit map passed java lang illegalstateexception serializer has been already registered for type class could there be some kind of race condition hear com hazelcast nio serialization hazelcastserializationexception failed to serialize hzcmd model person personexternalizable at com hazelcast internal serialization impl serializationutil handleserializeexception serializationutil java at com hazelcast internal serialization impl abstractserializationservice tobytes abstractserializationservice java at com hazelcast internal serialization impl abstractserializationservice tobytes abstractserializationservice java at com hazelcast internal serialization impl abstractserializationservice todata abstractserializationservice java at com hazelcast internal serialization impl abstractserializationservice todata abstractserializationservice java at com hazelcast client impl spi clientproxy todata clientproxy java at com hazelcast client impl proxy clientmapproxy putinternal clientmapproxy java at com hazelcast client impl proxy clientmapproxy put clientmapproxy java at hzcmd map putrandomstyleperson timestep putrandomstyleperson java at remote bench marker rollmarker flatout rollmarker java at remote bench marker rollmarker bench rollmarker java at remote bench benchthread call benchthread java at remote bench benchthread call benchthread java at java base java util concurrent futuretask run futuretask java at java base java util concurrent executors runnableadapter call executors java at java base java util concurrent futuretask run futuretask java at java base java util concurrent threadpoolexecutor runworker threadpoolexecutor java at java base java util concurrent threadpoolexecutor worker run threadpoolexecutor java at java base java lang thread run thread java caused by java lang illegalstateexception serializer has been already registered for type class hzcmd model person personexternalizable at com hazelcast internal serialization impl abstractserializationservice saferegister abstractserializationservice java at com hazelcast internal serialization impl abstractserializationservice lookupjavaserializer abstractserializationservice java at com hazelcast internal serialization impl abstractserializationservice serializerfor abstractserializationservice java at com hazelcast internal serialization impl abstractserializationservice tobytes abstractserializationservice java more | 0 |
119,583 | 15,576,891,245 | IssuesEvent | 2021-03-17 12:55:25 | owncloud/client | https://api.github.com/repos/owncloud/client | closed | Forbidden web page when using invalid URL in setup dialog | Design & UX PR available bug | ### Steps
1. Setup Apache2 with ownCloud under http://localhost/owncloud
1. Setup desktop client and enter "http://localhost" (note that it's the wrong path)
1. Click "next"
### Expected
User-friendly error message
### Actual
Popup appears with 403 error page inside. I can close it to go back.
### Versions
openSUSE Tumbleweed
plasma5-workspace-5.11.2-1.2.x86_64
owncloud-client-2.4.0~alpha1-8649.1.x86_64
| 1.0 | Forbidden web page when using invalid URL in setup dialog - ### Steps
1. Setup Apache2 with ownCloud under http://localhost/owncloud
1. Setup desktop client and enter "http://localhost" (note that it's the wrong path)
1. Click "next"
### Expected
User-friendly error message
### Actual
Popup appears with 403 error page inside. I can close it to go back.
### Versions
openSUSE Tumbleweed
plasma5-workspace-5.11.2-1.2.x86_64
owncloud-client-2.4.0~alpha1-8649.1.x86_64
| non_priority | forbidden web page when using invalid url in setup dialog steps setup with owncloud under setup desktop client and enter note that it s the wrong path click next expected user friendly error message actual popup appears with error page inside i can close it to go back versions opensuse tumbleweed workspace owncloud client | 0 |
89,849 | 25,912,154,386 | IssuesEvent | 2022-12-15 14:44:52 | matplotlib/matplotlib | https://api.github.com/repos/matplotlib/matplotlib | closed | [MNT]: Write a bot to post doc build issues | Maintenance Documentation: build | ### Summary
When doc builds fail, most of the time it's due to ReST formatting or referencing issues.
Most issues have a form similar to
> /home/circleci/project/doc/api/next_api_changes/behavior/22135-JSS3.rst:3: WARNING: py:obj reference target not found: Figure._localaxes
My standard way to find out the error is:
- Open CircleCI
- Download the build log
- Search for "WARNING"
This is cumbersome and not very discoverable for new contributors.
### Proposed fix
It would be great to have a bot post these warnings if CicleCI fails. I assume that would cover 95% of doc build failures and point contributors (new and experienced) to the problem so that they can solve it faster.
| 1.0 | [MNT]: Write a bot to post doc build issues - ### Summary
When doc builds fail, most of the time it's due to ReST formatting or referencing issues.
Most issues have a form similar to
> /home/circleci/project/doc/api/next_api_changes/behavior/22135-JSS3.rst:3: WARNING: py:obj reference target not found: Figure._localaxes
My standard way to find out the error is:
- Open CircleCI
- Download the build log
- Search for "WARNING"
This is cumbersome and not very discoverable for new contributors.
### Proposed fix
It would be great to have a bot post these warnings if CicleCI fails. I assume that would cover 95% of doc build failures and point contributors (new and experienced) to the problem so that they can solve it faster.
| non_priority | write a bot to post doc build issues summary when doc builds fail most of the time it s due to rest formatting or referencing issues most issues have a form similar to home circleci project doc api next api changes behavior rst warning py obj reference target not found figure localaxes my standard way to find out the error is open circleci download the build log search for warning this is cumbersome and not very discoverable for new contributors proposed fix it would be great to have a bot post these warnings if cicleci fails i assume that would cover of doc build failures and point contributors new and experienced to the problem so that they can solve it faster | 0 |
39,994 | 6,793,827,520 | IssuesEvent | 2017-11-01 09:28:17 | yeoman/yo | https://api.github.com/repos/yeoman/yo | closed | Document the ability to run local generators | actionnable documentation easy | ## Type of issue
### Documentation improvement
The ability to run local generators with `yo ./path/to/some/generator` should be documented in:
+ the README
+ the CLIs help output
----
This popped up via #545 | 1.0 | Document the ability to run local generators - ## Type of issue
### Documentation improvement
The ability to run local generators with `yo ./path/to/some/generator` should be documented in:
+ the README
+ the CLIs help output
----
This popped up via #545 | non_priority | document the ability to run local generators type of issue documentation improvement the ability to run local generators with yo path to some generator should be documented in the readme the clis help output this popped up via | 0 |
91,345 | 18,442,284,745 | IssuesEvent | 2021-10-14 19:40:23 | lightbend/akkaserverless-java-sdk | https://api.github.com/repos/lightbend/akkaserverless-java-sdk | closed | Wrong / confusing resolution of service to entities in Scala codegen | bug codegen scala-sdk | Given the example from the TCK (slightly cleaned up):
```proto
package akkaserverless.tck.model.eventsourcedentity;
option java_package = "com.akkaserverless.tck.model.eventsourcedentity";
option java_multiple_files = true;
import "akkaserverless/annotations.proto";
import "google/api/annotations.proto";
import "akkaserverless/tck/model/eventsourcedentity/event_sourced_entity_api.proto";
option (akkaserverless.file).event_sourced_entity = {
name: "EventSourcedTckModelEntity"
entity_type: "event-sourced-tck-model"
state: "Persisted"
events: ["Persisted"]
};
service EventSourcedTckModel {
option (akkaserverless.service) = {
type : SERVICE_TYPE_ENTITY
component: "EventSourcedTckModelEntity"
};
rpc Process(Request) returns (Response) {
option (google.api.http) = {
post: "/tck/model/eventsourced/{id}"
body: "*"
};
}
}
```
leads to this error message:
```
java.lang.IllegalArgumentException: Service [com.akkaserverless.tck.model.eventsourcedentity.event_sourced_tck_model.EventSourcedTckModel] refers to entity [akkaserverless.tck.model.eventsourcedentity.EventSourcedTckModelEntity], but no entity configuration is found for that component name. Entities: [com.akkaserverless.tck.model.eventsourcedentity.event_sourced_configured.EventSourcedConfiguredEntity, com.akkaserverless.tck.model.eventsourcedentity.event_sourced_two.EventSourcedTwoEntity, akkaserverless.tck.model.valueentity.ValueEntityTckModelEntity, com.akkaserverless.tck.model.eventsourcedentity.event_sourced_tck_model.EventSourcedTckModelEntity, akkaserverless.tck.model.valueentity.ValueEntityTwoEntity, akkaserverless.tck.model.valueentity.ValueEntityConfiguredEntity]
```
Note the slight discrepancy between package names (proto package vs `java_package`) but also the different handling between value and event-sourced entities. | 1.0 | Wrong / confusing resolution of service to entities in Scala codegen - Given the example from the TCK (slightly cleaned up):
```proto
package akkaserverless.tck.model.eventsourcedentity;
option java_package = "com.akkaserverless.tck.model.eventsourcedentity";
option java_multiple_files = true;
import "akkaserverless/annotations.proto";
import "google/api/annotations.proto";
import "akkaserverless/tck/model/eventsourcedentity/event_sourced_entity_api.proto";
option (akkaserverless.file).event_sourced_entity = {
name: "EventSourcedTckModelEntity"
entity_type: "event-sourced-tck-model"
state: "Persisted"
events: ["Persisted"]
};
service EventSourcedTckModel {
option (akkaserverless.service) = {
type : SERVICE_TYPE_ENTITY
component: "EventSourcedTckModelEntity"
};
rpc Process(Request) returns (Response) {
option (google.api.http) = {
post: "/tck/model/eventsourced/{id}"
body: "*"
};
}
}
```
leads to this error message:
```
java.lang.IllegalArgumentException: Service [com.akkaserverless.tck.model.eventsourcedentity.event_sourced_tck_model.EventSourcedTckModel] refers to entity [akkaserverless.tck.model.eventsourcedentity.EventSourcedTckModelEntity], but no entity configuration is found for that component name. Entities: [com.akkaserverless.tck.model.eventsourcedentity.event_sourced_configured.EventSourcedConfiguredEntity, com.akkaserverless.tck.model.eventsourcedentity.event_sourced_two.EventSourcedTwoEntity, akkaserverless.tck.model.valueentity.ValueEntityTckModelEntity, com.akkaserverless.tck.model.eventsourcedentity.event_sourced_tck_model.EventSourcedTckModelEntity, akkaserverless.tck.model.valueentity.ValueEntityTwoEntity, akkaserverless.tck.model.valueentity.ValueEntityConfiguredEntity]
```
Note the slight discrepancy between package names (proto package vs `java_package`) but also the different handling between value and event-sourced entities. | non_priority | wrong confusing resolution of service to entities in scala codegen given the example from the tck slightly cleaned up proto package akkaserverless tck model eventsourcedentity option java package com akkaserverless tck model eventsourcedentity option java multiple files true import akkaserverless annotations proto import google api annotations proto import akkaserverless tck model eventsourcedentity event sourced entity api proto option akkaserverless file event sourced entity name eventsourcedtckmodelentity entity type event sourced tck model state persisted events service eventsourcedtckmodel option akkaserverless service type service type entity component eventsourcedtckmodelentity rpc process request returns response option google api http post tck model eventsourced id body leads to this error message java lang illegalargumentexception service refers to entity but no entity configuration is found for that component name entities note the slight discrepancy between package names proto package vs java package but also the different handling between value and event sourced entities | 0 |
52,991 | 6,669,004,048 | IssuesEvent | 2017-10-03 17:46:50 | pandas-dev/pandas | https://api.github.com/repos/pandas-dev/pandas | opened | API? Adding a | API Design Dtypes Numeric | Possible API breakage for dask in https://github.com/pandas-dev/pandas/pull/16821
```python
import dask.dataframe as dd
import pandas as pd
from dask.dataframe.utils import assert_eq
s = dd.core.Scalar({('s', 0): 10}, 's', 'i8')
pdf = pd.DataFrame({'a': [1, 2, 3, 4, 5, 6, 7],
'b': [7, 6, 5, 4, 3, 2, 1]})
result = (pdf + s).dtypes # This now casts to object, used to retain int64
expected = pdf.dtypes
assert_eq(result, expected)
```
I'm looking into #16821 to see if this was unintentional, and can be avoided. | 1.0 | API? Adding a - Possible API breakage for dask in https://github.com/pandas-dev/pandas/pull/16821
```python
import dask.dataframe as dd
import pandas as pd
from dask.dataframe.utils import assert_eq
s = dd.core.Scalar({('s', 0): 10}, 's', 'i8')
pdf = pd.DataFrame({'a': [1, 2, 3, 4, 5, 6, 7],
'b': [7, 6, 5, 4, 3, 2, 1]})
result = (pdf + s).dtypes # This now casts to object, used to retain int64
expected = pdf.dtypes
assert_eq(result, expected)
```
I'm looking into #16821 to see if this was unintentional, and can be avoided. | non_priority | api adding a possible api breakage for dask in python import dask dataframe as dd import pandas as pd from dask dataframe utils import assert eq s dd core scalar s s pdf pd dataframe a b result pdf s dtypes this now casts to object used to retain expected pdf dtypes assert eq result expected i m looking into to see if this was unintentional and can be avoided | 0 |
293,790 | 25,322,301,496 | IssuesEvent | 2022-11-18 05:41:15 | Taewoongjung/Doseoro_Java | https://api.github.com/repos/Taewoongjung/Doseoro_Java | closed | GetAllInformationOfTheBookByBookIdDtoResult 테스트 추가 | ✅ Test | # Issue:✨FEATURE
GetAllInformationOfTheBookByBookIdDtoResult 테스트 추가
## Description
## To-do
- [x] 팝니다 책 조회 테스트 추가
- [x] 무료나눔 책 조회 테스트 추가
| 1.0 | GetAllInformationOfTheBookByBookIdDtoResult 테스트 추가 - # Issue:✨FEATURE
GetAllInformationOfTheBookByBookIdDtoResult 테스트 추가
## Description
## To-do
- [x] 팝니다 책 조회 테스트 추가
- [x] 무료나눔 책 조회 테스트 추가
| non_priority | getallinformationofthebookbybookiddtoresult 테스트 추가 issue ✨feature getallinformationofthebookbybookiddtoresult 테스트 추가 description to do 팝니다 책 조회 테스트 추가 무료나눔 책 조회 테스트 추가 | 0 |
142,620 | 13,035,822,603 | IssuesEvent | 2020-07-28 11:05:37 | SuffolkLITLab/docassemble-NoticeOfLimitedAppearances | https://api.github.com/repos/SuffolkLITLab/docassemble-NoticeOfLimitedAppearances | closed | Remove Cover Page | documentation | We need to remove the cover page and the ''submit to court'' option from the interview as the Attorney will download and deliver this form themselves. | 1.0 | Remove Cover Page - We need to remove the cover page and the ''submit to court'' option from the interview as the Attorney will download and deliver this form themselves. | non_priority | remove cover page we need to remove the cover page and the submit to court option from the interview as the attorney will download and deliver this form themselves | 0 |
61,297 | 8,507,732,382 | IssuesEvent | 2018-10-30 19:54:47 | cyberark/conjur | https://api.github.com/repos/cyberark/conjur | closed | Front page link to AUTHENTICATORS.md broken | kind/bug kind/documentation triage/not-reproducible | Same for ROTATORS.md. Looks the files were moved into docs folder and the links weren't updated. | 1.0 | Front page link to AUTHENTICATORS.md broken - Same for ROTATORS.md. Looks the files were moved into docs folder and the links weren't updated. | non_priority | front page link to authenticators md broken same for rotators md looks the files were moved into docs folder and the links weren t updated | 0 |
246,851 | 20,920,937,314 | IssuesEvent | 2022-03-24 17:19:45 | srid/emanote | https://api.github.com/repos/srid/emanote | closed | Console errors on non-Emanote notebook: `attempt to encode a 404 route: index.html/favicon.svg` | bug case-for-tests | <img width="670" alt="image" src="https://user-images.githubusercontent.com/3998/159970065-565db199-0626-421b-9402-368970209891.png">
| 1.0 | Console errors on non-Emanote notebook: `attempt to encode a 404 route: index.html/favicon.svg` - <img width="670" alt="image" src="https://user-images.githubusercontent.com/3998/159970065-565db199-0626-421b-9402-368970209891.png">
| non_priority | console errors on non emanote notebook attempt to encode a route index html favicon svg img width alt image src | 0 |
101,538 | 21,708,273,046 | IssuesEvent | 2022-05-10 11:42:24 | EddieHubCommunity/LinkFree | https://api.github.com/repos/EddieHubCommunity/LinkFree | closed | Add icons to icons.md | help wanted 💻 aspect: code good first issue 🔢 points: 1 📄 aspect: text | ### Description
Add programming language icons to icons.md, I have used a couple of icons in my PR, someone suggested adding an issue so it can be added to the documentation
### Screenshots
_No response_
### Additional information
_No response_ | 1.0 | Add icons to icons.md - ### Description
Add programming language icons to icons.md, I have used a couple of icons in my PR, someone suggested adding an issue so it can be added to the documentation
### Screenshots
_No response_
### Additional information
_No response_ | non_priority | add icons to icons md description add programming language icons to icons md i have used a couple of icons in my pr someone suggested adding an issue so it can be added to the documentation screenshots no response additional information no response | 0 |
336,330 | 30,188,617,001 | IssuesEvent | 2023-07-04 13:47:57 | cockroachdb/cockroach | https://api.github.com/repos/cockroachdb/cockroach | closed | pkg/sql/sqlstats/persistedsqlstats/persistedsqlstats_test: TestSQLStatsPersistedLimitReached failed | C-test-failure O-robot branch-release-23.1 T-cluster-observability | pkg/sql/sqlstats/persistedsqlstats/persistedsqlstats_test.TestSQLStatsPersistedLimitReached [failed](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Ci_TestsAwsLinuxArm64_UnitTests/10743045?buildTab=log) with [artifacts](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Ci_TestsAwsLinuxArm64_UnitTests/10743045?buildTab=artifacts#/) on release-23.1 @ [845bcfb583bb92fc09a66e3edd2154469981a1de](https://github.com/cockroachdb/cockroach/commits/845bcfb583bb92fc09a66e3edd2154469981a1de):
```
=== RUN TestSQLStatsPersistedLimitReached
test_log_scope.go:161: test logs captured to: /artifacts/tmp/_tmp/c5ba30668f7c1d418e84ab9d90b4c4de/logTestSQLStatsPersistedLimitReached4270577646
test_log_scope.go:79: use -show-logs to present logs inline
flush_test.go:517:
Error Trace: pkg/sql/sqlstats/persistedsqlstats/persistedsqlstats_test_test/pkg/sql/sqlstats/persistedsqlstats/flush_test.go:517
Error: "16" is not less than or equal to "15"
Test: TestSQLStatsPersistedLimitReached
panic.go:522: -- test log scope end --
test logs left over in: /artifacts/tmp/_tmp/c5ba30668f7c1d418e84ab9d90b4c4de/logTestSQLStatsPersistedLimitReached4270577646
--- FAIL: TestSQLStatsPersistedLimitReached (1.79s)
```
<details><summary>Help</summary>
<p>
See also: [How To Investigate a Go Test Failure \(internal\)](https://cockroachlabs.atlassian.net/l/c/HgfXfJgM)
</p>
</details>
/cc @cockroachdb/cluster-observability
<sub>
[This test on roachdash](https://roachdash.crdb.dev/?filter=status:open%20t:.*TestSQLStatsPersistedLimitReached.*&sort=title+created&display=lastcommented+project) | [Improve this report!](https://github.com/cockroachdb/cockroach/tree/master/pkg/cmd/internal/issues)
</sub>
Jira issue: CRDB-29256 | 1.0 | pkg/sql/sqlstats/persistedsqlstats/persistedsqlstats_test: TestSQLStatsPersistedLimitReached failed - pkg/sql/sqlstats/persistedsqlstats/persistedsqlstats_test.TestSQLStatsPersistedLimitReached [failed](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Ci_TestsAwsLinuxArm64_UnitTests/10743045?buildTab=log) with [artifacts](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Ci_TestsAwsLinuxArm64_UnitTests/10743045?buildTab=artifacts#/) on release-23.1 @ [845bcfb583bb92fc09a66e3edd2154469981a1de](https://github.com/cockroachdb/cockroach/commits/845bcfb583bb92fc09a66e3edd2154469981a1de):
```
=== RUN TestSQLStatsPersistedLimitReached
test_log_scope.go:161: test logs captured to: /artifacts/tmp/_tmp/c5ba30668f7c1d418e84ab9d90b4c4de/logTestSQLStatsPersistedLimitReached4270577646
test_log_scope.go:79: use -show-logs to present logs inline
flush_test.go:517:
Error Trace: pkg/sql/sqlstats/persistedsqlstats/persistedsqlstats_test_test/pkg/sql/sqlstats/persistedsqlstats/flush_test.go:517
Error: "16" is not less than or equal to "15"
Test: TestSQLStatsPersistedLimitReached
panic.go:522: -- test log scope end --
test logs left over in: /artifacts/tmp/_tmp/c5ba30668f7c1d418e84ab9d90b4c4de/logTestSQLStatsPersistedLimitReached4270577646
--- FAIL: TestSQLStatsPersistedLimitReached (1.79s)
```
<details><summary>Help</summary>
<p>
See also: [How To Investigate a Go Test Failure \(internal\)](https://cockroachlabs.atlassian.net/l/c/HgfXfJgM)
</p>
</details>
/cc @cockroachdb/cluster-observability
<sub>
[This test on roachdash](https://roachdash.crdb.dev/?filter=status:open%20t:.*TestSQLStatsPersistedLimitReached.*&sort=title+created&display=lastcommented+project) | [Improve this report!](https://github.com/cockroachdb/cockroach/tree/master/pkg/cmd/internal/issues)
</sub>
Jira issue: CRDB-29256 | non_priority | pkg sql sqlstats persistedsqlstats persistedsqlstats test testsqlstatspersistedlimitreached failed pkg sql sqlstats persistedsqlstats persistedsqlstats test testsqlstatspersistedlimitreached with on release run testsqlstatspersistedlimitreached test log scope go test logs captured to artifacts tmp tmp test log scope go use show logs to present logs inline flush test go error trace pkg sql sqlstats persistedsqlstats persistedsqlstats test test pkg sql sqlstats persistedsqlstats flush test go error is not less than or equal to test testsqlstatspersistedlimitreached panic go test log scope end test logs left over in artifacts tmp tmp fail testsqlstatspersistedlimitreached help see also cc cockroachdb cluster observability jira issue crdb | 0 |
56,620 | 11,614,705,388 | IssuesEvent | 2020-02-26 13:03:47 | Bachelor-Thesis-Project-Gruppun/StaticAnalyser | https://api.github.com/repos/Bachelor-Thesis-Project-Gruppun/StaticAnalyser | closed | Investigate data-flow and control-flow | NotCode Report | Investigate the following static analysis methods to determine if they are suitable for our project:
- [ ] Investigate
- [ ] Investigate data-flow | 1.0 | Investigate data-flow and control-flow - Investigate the following static analysis methods to determine if they are suitable for our project:
- [ ] Investigate
- [ ] Investigate data-flow | non_priority | investigate data flow and control flow investigate the following static analysis methods to determine if they are suitable for our project investigate investigate data flow | 0 |
14,644 | 17,871,309,278 | IssuesEvent | 2021-09-06 15:56:25 | safing/portmaster | https://api.github.com/repos/safing/portmaster | closed | Support for sysVinit maybe? | docs pending suggestion in/compatibility backlog | **Pre-Submit Checklist**:
- Check applicable sources for existing issues:
- [Linux Compatibility](https://docs.safing.io/portmaster/install/linux#compatibility)
- [VPN Compatibility](https://docs.safing.io/portmaster/install/status/vpn-compatibility)
- [Github Issues](https://github.com/safing/portmaster/issues?q=is%3Aissue+label%3Ain%2Fcompatibility)
System information:
System: Kernel: 5.8.16-antix.1-amd64-smp x86_64 bits: 64 compiler: gcc v: 8.3.0
parameters: BOOT_IMAGE=/boot/vmlinuz-5.8.16-antix.1-amd64-smp root=UUID=<filter> ro
quiet splash init=/lib/systemd/systemd
Desktop: KDE Plasma 5.14.5 tk: Qt 5.11.3 info: latte-dock wm: kwin_x11 vt: 7 dm: SDDM
Distro: MX-19.4_x64 patito feo March 31 2021 base: Debian GNU/Linux 10 (buster)
Machine: Type: Desktop Mobo: MSI model: H61M-P32/W8 (MS-7788) v: 4.0 serial: <filter> UEFI: American Megatrends v: 10.11
date: 10/18/2013
Network: Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Micro-Star MSI driver: r8169 v: kernel
port: e000 bus-ID: 02:00.0 chip-ID: 10ec:8168 class-ID: 0200
IF: eth0 state: up speed: 100 Mbps duplex: full mac: <filter>
Info: Processes: 252 Uptime: 33m wakeups: 0 Memory: 7.48 GiB used: 2.4 GiB (32.1%) Init: systemd v: 241 runlevel: 5
default: 5 tool: systemctl Compilers: gcc: 8.3.0 alt: 8 Shell: quick-system-in default: Bash v: 5.0.3
running-in: quick-system-in inxi: 3.3.06
**What worked?**
UI and notifier works since its started by kde.
**What did not work?**
Core does not start since it relies on systemd.
I switched to systemd in kernel and for some reason core still doesn't start.
Manually starting core works "sudo /var/lib/portmaster/portmaster-start core" works, but I guess it starts late down the line instead of earlier. I'm not really sure, how to write a sysvinit script for on startup.
Is providing support for sysVinit maybe possible?
| True | Support for sysVinit maybe? - **Pre-Submit Checklist**:
- Check applicable sources for existing issues:
- [Linux Compatibility](https://docs.safing.io/portmaster/install/linux#compatibility)
- [VPN Compatibility](https://docs.safing.io/portmaster/install/status/vpn-compatibility)
- [Github Issues](https://github.com/safing/portmaster/issues?q=is%3Aissue+label%3Ain%2Fcompatibility)
System information:
System: Kernel: 5.8.16-antix.1-amd64-smp x86_64 bits: 64 compiler: gcc v: 8.3.0
parameters: BOOT_IMAGE=/boot/vmlinuz-5.8.16-antix.1-amd64-smp root=UUID=<filter> ro
quiet splash init=/lib/systemd/systemd
Desktop: KDE Plasma 5.14.5 tk: Qt 5.11.3 info: latte-dock wm: kwin_x11 vt: 7 dm: SDDM
Distro: MX-19.4_x64 patito feo March 31 2021 base: Debian GNU/Linux 10 (buster)
Machine: Type: Desktop Mobo: MSI model: H61M-P32/W8 (MS-7788) v: 4.0 serial: <filter> UEFI: American Megatrends v: 10.11
date: 10/18/2013
Network: Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Micro-Star MSI driver: r8169 v: kernel
port: e000 bus-ID: 02:00.0 chip-ID: 10ec:8168 class-ID: 0200
IF: eth0 state: up speed: 100 Mbps duplex: full mac: <filter>
Info: Processes: 252 Uptime: 33m wakeups: 0 Memory: 7.48 GiB used: 2.4 GiB (32.1%) Init: systemd v: 241 runlevel: 5
default: 5 tool: systemctl Compilers: gcc: 8.3.0 alt: 8 Shell: quick-system-in default: Bash v: 5.0.3
running-in: quick-system-in inxi: 3.3.06
**What worked?**
UI and notifier works since its started by kde.
**What did not work?**
Core does not start since it relies on systemd.
I switched to systemd in kernel and for some reason core still doesn't start.
Manually starting core works "sudo /var/lib/portmaster/portmaster-start core" works, but I guess it starts late down the line instead of earlier. I'm not really sure, how to write a sysvinit script for on startup.
Is providing support for sysVinit maybe possible?
| non_priority | support for sysvinit maybe pre submit checklist check applicable sources for existing issues system information system kernel antix smp bits compiler gcc v parameters boot image boot vmlinuz antix smp root uuid ro quiet splash init lib systemd systemd desktop kde plasma tk qt info latte dock wm kwin vt dm sddm distro mx patito feo march base debian gnu linux buster machine type desktop mobo msi model ms v serial uefi american megatrends v date network device realtek pci express gigabit ethernet vendor micro star msi driver v kernel port bus id chip id class id if state up speed mbps duplex full mac info processes uptime wakeups memory gib used gib init systemd v runlevel default tool systemctl compilers gcc alt shell quick system in default bash v running in quick system in inxi what worked ui and notifier works since its started by kde what did not work core does not start since it relies on systemd i switched to systemd in kernel and for some reason core still doesn t start manually starting core works sudo var lib portmaster portmaster start core works but i guess it starts late down the line instead of earlier i m not really sure how to write a sysvinit script for on startup is providing support for sysvinit maybe possible | 0 |
30,627 | 5,829,305,280 | IssuesEvent | 2017-05-08 14:18:12 | idaholab/moose | https://api.github.com/repos/idaholab/moose | opened | Create custom livereload Watcher object to auto load new markdown | C: Documentation | ### Description of the enhancement or error report
Currently, the live view of the docs will not re-load when a new markdown file is created. This can be solve but it will require a custom livereload.Watcher object that if the number of markdown files change then rebuild the entire page and re-add all the pages to the individual page builder.
### Rationale for the enhancement or information for reproducing the error
Having this would make writing docs easier.
### Identified impact
(i.e. Internal object changes, limited interface changes, public API change, or a list of specific applications impacted)
None | 1.0 | Create custom livereload Watcher object to auto load new markdown - ### Description of the enhancement or error report
Currently, the live view of the docs will not re-load when a new markdown file is created. This can be solve but it will require a custom livereload.Watcher object that if the number of markdown files change then rebuild the entire page and re-add all the pages to the individual page builder.
### Rationale for the enhancement or information for reproducing the error
Having this would make writing docs easier.
### Identified impact
(i.e. Internal object changes, limited interface changes, public API change, or a list of specific applications impacted)
None | non_priority | create custom livereload watcher object to auto load new markdown description of the enhancement or error report currently the live view of the docs will not re load when a new markdown file is created this can be solve but it will require a custom livereload watcher object that if the number of markdown files change then rebuild the entire page and re add all the pages to the individual page builder rationale for the enhancement or information for reproducing the error having this would make writing docs easier identified impact i e internal object changes limited interface changes public api change or a list of specific applications impacted none | 0 |
185,190 | 15,013,527,715 | IssuesEvent | 2021-02-01 04:39:54 | CATcher-org/CATcher | https://api.github.com/repos/CATcher-org/CATcher | opened | User notes: Update to account for web app | aspect-Documentation | - [ ] Provide URL of web app, and state that it is the default
- [ ] Add table of contents | 1.0 | User notes: Update to account for web app - - [ ] Provide URL of web app, and state that it is the default
- [ ] Add table of contents | non_priority | user notes update to account for web app provide url of web app and state that it is the default add table of contents | 0 |
56,297 | 31,851,054,585 | IssuesEvent | 2023-09-15 01:44:17 | keras-team/keras | https://api.github.com/repos/keras-team/keras | closed | Wrong calculation of output value in GRU | type:bug/performance stat:awaiting response from contributor stale | In file /keras/layers/recurrent.py, at commit 07bb88c, the output of the GRU layer is wrongly calculated. In fact, in line 1921 we can read:
`h = z * h_tm1 + (1 - z) * hh`
which is incorrect, since the candidate hidden state `hh` multiplies with z and not with (1-z). I guess the reason it works is because, in the end, the algorithm adjusted the weights `Wz` and `Uz` that produces z so take this into account, but I feat that the accuracy might not be achieving its full potential because of this. From the GRU original paper [https://arxiv.org/abs/1412.3555](url), on page 4, we confirm that `z` actually multiplies with `hh`, and not the other way around:
<img width="426" alt="2021-05-16 21_31_03-1412 3555 pdf" src="https://user-images.githubusercontent.com/9438498/118410103-15a9e880-b68e-11eb-865c-2c5e85ef6167.png">
Thanks in advance!
| True | Wrong calculation of output value in GRU - In file /keras/layers/recurrent.py, at commit 07bb88c, the output of the GRU layer is wrongly calculated. In fact, in line 1921 we can read:
`h = z * h_tm1 + (1 - z) * hh`
which is incorrect, since the candidate hidden state `hh` multiplies with z and not with (1-z). I guess the reason it works is because, in the end, the algorithm adjusted the weights `Wz` and `Uz` that produces z so take this into account, but I feat that the accuracy might not be achieving its full potential because of this. From the GRU original paper [https://arxiv.org/abs/1412.3555](url), on page 4, we confirm that `z` actually multiplies with `hh`, and not the other way around:
<img width="426" alt="2021-05-16 21_31_03-1412 3555 pdf" src="https://user-images.githubusercontent.com/9438498/118410103-15a9e880-b68e-11eb-865c-2c5e85ef6167.png">
Thanks in advance!
| non_priority | wrong calculation of output value in gru in file keras layers recurrent py at commit the output of the gru layer is wrongly calculated in fact in line we can read h z h z hh which is incorrect since the candidate hidden state hh multiplies with z and not with z i guess the reason it works is because in the end the algorithm adjusted the weights wz and uz that produces z so take this into account but i feat that the accuracy might not be achieving its full potential because of this from the gru original paper url on page we confirm that z actually multiplies with hh and not the other way around img width alt pdf src thanks in advance | 0 |
32,372 | 15,359,688,793 | IssuesEvent | 2021-03-01 16:07:01 | microsoft/fluentui | https://api.github.com/repos/microsoft/fluentui | opened | Research performance tests used by other frameworks | Area: Performance Type: Epic | This is one of those Schroedinger's issue which might either come to a close really quickly, or unwrap into a rather lengthy, time-consuming research with many avenues. The TL;DR of this issue is to track and gather intel on performance tests used by other frameworks. As I will be working on analysing other frameworks and how it's done over there, I will periodically update this issue, so feel free to check back here for progress updates. Finally, whenever possible, I will try to port as many perf cases over to our own `perf-test` app as possible.
---
### tl;dr
- [ ] investigate performance scenarios used by other frameworks
- [ ] Material
- [ ] ...
- [ ] add additional performance scenarios to `perf-test` app
- [ ] ...
- [ ] draw some conclusions/compare against others to see how we fare at this moment | True | Research performance tests used by other frameworks - This is one of those Schroedinger's issue which might either come to a close really quickly, or unwrap into a rather lengthy, time-consuming research with many avenues. The TL;DR of this issue is to track and gather intel on performance tests used by other frameworks. As I will be working on analysing other frameworks and how it's done over there, I will periodically update this issue, so feel free to check back here for progress updates. Finally, whenever possible, I will try to port as many perf cases over to our own `perf-test` app as possible.
---
### tl;dr
- [ ] investigate performance scenarios used by other frameworks
- [ ] Material
- [ ] ...
- [ ] add additional performance scenarios to `perf-test` app
- [ ] ...
- [ ] draw some conclusions/compare against others to see how we fare at this moment | non_priority | research performance tests used by other frameworks this is one of those schroedinger s issue which might either come to a close really quickly or unwrap into a rather lengthy time consuming research with many avenues the tl dr of this issue is to track and gather intel on performance tests used by other frameworks as i will be working on analysing other frameworks and how it s done over there i will periodically update this issue so feel free to check back here for progress updates finally whenever possible i will try to port as many perf cases over to our own perf test app as possible tl dr investigate performance scenarios used by other frameworks material add additional performance scenarios to perf test app draw some conclusions compare against others to see how we fare at this moment | 0 |
213,337 | 23,985,116,822 | IssuesEvent | 2022-09-13 18:20:38 | ghc-dev/3330349_1972 | https://api.github.com/repos/ghc-dev/3330349_1972 | opened | urllib3-1.19-py2.py3-none-any.whl: 4 vulnerabilities (highest severity is: 9.8) | security vulnerability | <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>urllib3-1.19-py2.py3-none-any.whl</b></p></summary>
<p>HTTP library with thread-safe connection pooling, file post, and more.</p>
<p>Library home page: <a href="https://files.pythonhosted.org/packages/34/02/f043d2c9e2360dd6f6f1f7e44c71733ede2478e8b084de43375b316105c5/urllib3-1.19-py2.py3-none-any.whl">https://files.pythonhosted.org/packages/34/02/f043d2c9e2360dd6f6f1f7e44c71733ede2478e8b084de43375b316105c5/urllib3-1.19-py2.py3-none-any.whl</a></p>
<p>Path to dependency file: /requirements.txt</p>
<p>Path to vulnerable library: /requirements.txt</p>
<p>
<p>Found in HEAD commit: <a href="https://github.com/ghc-dev/3330349_1972/commit/4c764f3edae2577d324ae6595a4f42bb7bb7b231">4c764f3edae2577d324ae6595a4f42bb7bb7b231</a></p></details>
## Vulnerabilities
| CVE | Severity | <img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS | Dependency | Type | Fixed in | Remediation Available |
| ------------- | ------------- | ----- | ----- | ----- | --- | --- |
| [CVE-2018-20060](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-20060) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 9.8 | urllib3-1.19-py2.py3-none-any.whl | Direct | 1.23 | ✅ |
| [CVE-2019-11324](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-11324) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | urllib3-1.19-py2.py3-none-any.whl | Direct | 1.24.2 | ✅ |
| [CVE-2020-26137](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-26137) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 6.5 | urllib3-1.19-py2.py3-none-any.whl | Direct | 1.25.9 | ✅ |
| [CVE-2019-9740](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-9740) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 6.1 | urllib3-1.19-py2.py3-none-any.whl | Direct | 1.24.3 | ✅ |
## Details
<details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2018-20060</summary>
### Vulnerable Library - <b>urllib3-1.19-py2.py3-none-any.whl</b></p>
<p>HTTP library with thread-safe connection pooling, file post, and more.</p>
<p>Library home page: <a href="https://files.pythonhosted.org/packages/34/02/f043d2c9e2360dd6f6f1f7e44c71733ede2478e8b084de43375b316105c5/urllib3-1.19-py2.py3-none-any.whl">https://files.pythonhosted.org/packages/34/02/f043d2c9e2360dd6f6f1f7e44c71733ede2478e8b084de43375b316105c5/urllib3-1.19-py2.py3-none-any.whl</a></p>
<p>Path to dependency file: /requirements.txt</p>
<p>Path to vulnerable library: /requirements.txt</p>
<p>
Dependency Hierarchy:
- :x: **urllib3-1.19-py2.py3-none-any.whl** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/ghc-dev/3330349_1972/commit/4c764f3edae2577d324ae6595a4f42bb7bb7b231">4c764f3edae2577d324ae6595a4f42bb7bb7b231</a></p>
<p>Found in base branch: <b>second_feature_branch</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
urllib3 before version 1.23 does not remove the Authorization HTTP header when following a cross-origin redirect (i.e., a redirect that differs in host, port, or scheme). This can allow for credentials in the Authorization header to be exposed to unintended hosts or transmitted in cleartext.
<p>Publish Date: 2018-12-11
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-20060>CVE-2018-20060</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>9.8</b>)
<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>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-20060">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-20060</a></p>
<p>Release Date: 2018-12-11</p>
<p>Fix Resolution: 1.23</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation is available for this issue
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2019-11324</summary>
### Vulnerable Library - <b>urllib3-1.19-py2.py3-none-any.whl</b></p>
<p>HTTP library with thread-safe connection pooling, file post, and more.</p>
<p>Library home page: <a href="https://files.pythonhosted.org/packages/34/02/f043d2c9e2360dd6f6f1f7e44c71733ede2478e8b084de43375b316105c5/urllib3-1.19-py2.py3-none-any.whl">https://files.pythonhosted.org/packages/34/02/f043d2c9e2360dd6f6f1f7e44c71733ede2478e8b084de43375b316105c5/urllib3-1.19-py2.py3-none-any.whl</a></p>
<p>Path to dependency file: /requirements.txt</p>
<p>Path to vulnerable library: /requirements.txt</p>
<p>
Dependency Hierarchy:
- :x: **urllib3-1.19-py2.py3-none-any.whl** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/ghc-dev/3330349_1972/commit/4c764f3edae2577d324ae6595a4f42bb7bb7b231">4c764f3edae2577d324ae6595a4f42bb7bb7b231</a></p>
<p>Found in base branch: <b>second_feature_branch</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
The urllib3 library before 1.24.2 for Python mishandles certain cases where the desired set of CA certificates is different from the OS store of CA certificates, which results in SSL connections succeeding in situations where a verification failure is the correct outcome. This is related to use of the ssl_context, ca_certs, or ca_certs_dir argument.
<p>Publish Date: 2019-04-18
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-11324>CVE-2019-11324</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>7.5</b>)
<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: 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>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-11324">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-11324</a></p>
<p>Release Date: 2019-04-18</p>
<p>Fix Resolution: 1.24.2</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation is available for this issue
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2020-26137</summary>
### Vulnerable Library - <b>urllib3-1.19-py2.py3-none-any.whl</b></p>
<p>HTTP library with thread-safe connection pooling, file post, and more.</p>
<p>Library home page: <a href="https://files.pythonhosted.org/packages/34/02/f043d2c9e2360dd6f6f1f7e44c71733ede2478e8b084de43375b316105c5/urllib3-1.19-py2.py3-none-any.whl">https://files.pythonhosted.org/packages/34/02/f043d2c9e2360dd6f6f1f7e44c71733ede2478e8b084de43375b316105c5/urllib3-1.19-py2.py3-none-any.whl</a></p>
<p>Path to dependency file: /requirements.txt</p>
<p>Path to vulnerable library: /requirements.txt</p>
<p>
Dependency Hierarchy:
- :x: **urllib3-1.19-py2.py3-none-any.whl** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/ghc-dev/3330349_1972/commit/4c764f3edae2577d324ae6595a4f42bb7bb7b231">4c764f3edae2577d324ae6595a4f42bb7bb7b231</a></p>
<p>Found in base branch: <b>second_feature_branch</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
urllib3 before 1.25.9 allows CRLF injection if the attacker controls the HTTP request method, as demonstrated by inserting CR and LF control characters in the first argument of putrequest(). NOTE: this is similar to CVE-2020-26116.
<p>Publish Date: 2020-09-30
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-26137>CVE-2020-26137</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>6.5</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: Low
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-26137">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-26137</a></p>
<p>Release Date: 2020-09-30</p>
<p>Fix Resolution: 1.25.9</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation is available for this issue
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2019-9740</summary>
### Vulnerable Library - <b>urllib3-1.19-py2.py3-none-any.whl</b></p>
<p>HTTP library with thread-safe connection pooling, file post, and more.</p>
<p>Library home page: <a href="https://files.pythonhosted.org/packages/34/02/f043d2c9e2360dd6f6f1f7e44c71733ede2478e8b084de43375b316105c5/urllib3-1.19-py2.py3-none-any.whl">https://files.pythonhosted.org/packages/34/02/f043d2c9e2360dd6f6f1f7e44c71733ede2478e8b084de43375b316105c5/urllib3-1.19-py2.py3-none-any.whl</a></p>
<p>Path to dependency file: /requirements.txt</p>
<p>Path to vulnerable library: /requirements.txt</p>
<p>
Dependency Hierarchy:
- :x: **urllib3-1.19-py2.py3-none-any.whl** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/ghc-dev/3330349_1972/commit/4c764f3edae2577d324ae6595a4f42bb7bb7b231">4c764f3edae2577d324ae6595a4f42bb7bb7b231</a></p>
<p>Found in base branch: <b>second_feature_branch</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
An issue was discovered in urllib2 in Python 2.x through 2.7.16 and urllib in Python 3.x through 3.7.3. CRLF injection is possible if the attacker controls a url parameter, as demonstrated by the first argument to urllib.request.urlopen with \r\n (specifically in the query string after a ? character) followed by an HTTP header or a Redis command. This is fixed in: v2.7.17, v2.7.17rc1, v2.7.18, v2.7.18rc1; v3.5.10, v3.5.10rc1, v3.5.8, v3.5.8rc1, v3.5.8rc2, v3.5.9; v3.6.10, v3.6.10rc1, v3.6.11, v3.6.11rc1, v3.6.12, v3.6.9, v3.6.9rc1; v3.7.4, v3.7.4rc1, v3.7.4rc2, v3.7.5, v3.7.5rc1, v3.7.6, v3.7.6rc1, v3.7.7, v3.7.7rc1, v3.7.8, v3.7.8rc1, v3.7.9.
<p>Publish Date: 2019-03-13
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-9740>CVE-2019-9740</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>6.1</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: Low
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-9740">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-9740</a></p>
<p>Release Date: 2019-03-13</p>
<p>Fix Resolution: 1.24.3</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation is available for this issue
</details>
***
<p>:rescue_worker_helmet: Automatic Remediation is available for this issue.</p> | True | urllib3-1.19-py2.py3-none-any.whl: 4 vulnerabilities (highest severity is: 9.8) - <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>urllib3-1.19-py2.py3-none-any.whl</b></p></summary>
<p>HTTP library with thread-safe connection pooling, file post, and more.</p>
<p>Library home page: <a href="https://files.pythonhosted.org/packages/34/02/f043d2c9e2360dd6f6f1f7e44c71733ede2478e8b084de43375b316105c5/urllib3-1.19-py2.py3-none-any.whl">https://files.pythonhosted.org/packages/34/02/f043d2c9e2360dd6f6f1f7e44c71733ede2478e8b084de43375b316105c5/urllib3-1.19-py2.py3-none-any.whl</a></p>
<p>Path to dependency file: /requirements.txt</p>
<p>Path to vulnerable library: /requirements.txt</p>
<p>
<p>Found in HEAD commit: <a href="https://github.com/ghc-dev/3330349_1972/commit/4c764f3edae2577d324ae6595a4f42bb7bb7b231">4c764f3edae2577d324ae6595a4f42bb7bb7b231</a></p></details>
## Vulnerabilities
| CVE | Severity | <img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS | Dependency | Type | Fixed in | Remediation Available |
| ------------- | ------------- | ----- | ----- | ----- | --- | --- |
| [CVE-2018-20060](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-20060) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 9.8 | urllib3-1.19-py2.py3-none-any.whl | Direct | 1.23 | ✅ |
| [CVE-2019-11324](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-11324) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | urllib3-1.19-py2.py3-none-any.whl | Direct | 1.24.2 | ✅ |
| [CVE-2020-26137](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-26137) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 6.5 | urllib3-1.19-py2.py3-none-any.whl | Direct | 1.25.9 | ✅ |
| [CVE-2019-9740](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-9740) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 6.1 | urllib3-1.19-py2.py3-none-any.whl | Direct | 1.24.3 | ✅ |
## Details
<details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2018-20060</summary>
### Vulnerable Library - <b>urllib3-1.19-py2.py3-none-any.whl</b></p>
<p>HTTP library with thread-safe connection pooling, file post, and more.</p>
<p>Library home page: <a href="https://files.pythonhosted.org/packages/34/02/f043d2c9e2360dd6f6f1f7e44c71733ede2478e8b084de43375b316105c5/urllib3-1.19-py2.py3-none-any.whl">https://files.pythonhosted.org/packages/34/02/f043d2c9e2360dd6f6f1f7e44c71733ede2478e8b084de43375b316105c5/urllib3-1.19-py2.py3-none-any.whl</a></p>
<p>Path to dependency file: /requirements.txt</p>
<p>Path to vulnerable library: /requirements.txt</p>
<p>
Dependency Hierarchy:
- :x: **urllib3-1.19-py2.py3-none-any.whl** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/ghc-dev/3330349_1972/commit/4c764f3edae2577d324ae6595a4f42bb7bb7b231">4c764f3edae2577d324ae6595a4f42bb7bb7b231</a></p>
<p>Found in base branch: <b>second_feature_branch</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
urllib3 before version 1.23 does not remove the Authorization HTTP header when following a cross-origin redirect (i.e., a redirect that differs in host, port, or scheme). This can allow for credentials in the Authorization header to be exposed to unintended hosts or transmitted in cleartext.
<p>Publish Date: 2018-12-11
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-20060>CVE-2018-20060</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>9.8</b>)
<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>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-20060">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-20060</a></p>
<p>Release Date: 2018-12-11</p>
<p>Fix Resolution: 1.23</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation is available for this issue
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2019-11324</summary>
### Vulnerable Library - <b>urllib3-1.19-py2.py3-none-any.whl</b></p>
<p>HTTP library with thread-safe connection pooling, file post, and more.</p>
<p>Library home page: <a href="https://files.pythonhosted.org/packages/34/02/f043d2c9e2360dd6f6f1f7e44c71733ede2478e8b084de43375b316105c5/urllib3-1.19-py2.py3-none-any.whl">https://files.pythonhosted.org/packages/34/02/f043d2c9e2360dd6f6f1f7e44c71733ede2478e8b084de43375b316105c5/urllib3-1.19-py2.py3-none-any.whl</a></p>
<p>Path to dependency file: /requirements.txt</p>
<p>Path to vulnerable library: /requirements.txt</p>
<p>
Dependency Hierarchy:
- :x: **urllib3-1.19-py2.py3-none-any.whl** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/ghc-dev/3330349_1972/commit/4c764f3edae2577d324ae6595a4f42bb7bb7b231">4c764f3edae2577d324ae6595a4f42bb7bb7b231</a></p>
<p>Found in base branch: <b>second_feature_branch</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
The urllib3 library before 1.24.2 for Python mishandles certain cases where the desired set of CA certificates is different from the OS store of CA certificates, which results in SSL connections succeeding in situations where a verification failure is the correct outcome. This is related to use of the ssl_context, ca_certs, or ca_certs_dir argument.
<p>Publish Date: 2019-04-18
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-11324>CVE-2019-11324</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>7.5</b>)
<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: 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>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-11324">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-11324</a></p>
<p>Release Date: 2019-04-18</p>
<p>Fix Resolution: 1.24.2</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation is available for this issue
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2020-26137</summary>
### Vulnerable Library - <b>urllib3-1.19-py2.py3-none-any.whl</b></p>
<p>HTTP library with thread-safe connection pooling, file post, and more.</p>
<p>Library home page: <a href="https://files.pythonhosted.org/packages/34/02/f043d2c9e2360dd6f6f1f7e44c71733ede2478e8b084de43375b316105c5/urllib3-1.19-py2.py3-none-any.whl">https://files.pythonhosted.org/packages/34/02/f043d2c9e2360dd6f6f1f7e44c71733ede2478e8b084de43375b316105c5/urllib3-1.19-py2.py3-none-any.whl</a></p>
<p>Path to dependency file: /requirements.txt</p>
<p>Path to vulnerable library: /requirements.txt</p>
<p>
Dependency Hierarchy:
- :x: **urllib3-1.19-py2.py3-none-any.whl** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/ghc-dev/3330349_1972/commit/4c764f3edae2577d324ae6595a4f42bb7bb7b231">4c764f3edae2577d324ae6595a4f42bb7bb7b231</a></p>
<p>Found in base branch: <b>second_feature_branch</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
urllib3 before 1.25.9 allows CRLF injection if the attacker controls the HTTP request method, as demonstrated by inserting CR and LF control characters in the first argument of putrequest(). NOTE: this is similar to CVE-2020-26116.
<p>Publish Date: 2020-09-30
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-26137>CVE-2020-26137</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>6.5</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: Low
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-26137">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-26137</a></p>
<p>Release Date: 2020-09-30</p>
<p>Fix Resolution: 1.25.9</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation is available for this issue
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2019-9740</summary>
### Vulnerable Library - <b>urllib3-1.19-py2.py3-none-any.whl</b></p>
<p>HTTP library with thread-safe connection pooling, file post, and more.</p>
<p>Library home page: <a href="https://files.pythonhosted.org/packages/34/02/f043d2c9e2360dd6f6f1f7e44c71733ede2478e8b084de43375b316105c5/urllib3-1.19-py2.py3-none-any.whl">https://files.pythonhosted.org/packages/34/02/f043d2c9e2360dd6f6f1f7e44c71733ede2478e8b084de43375b316105c5/urllib3-1.19-py2.py3-none-any.whl</a></p>
<p>Path to dependency file: /requirements.txt</p>
<p>Path to vulnerable library: /requirements.txt</p>
<p>
Dependency Hierarchy:
- :x: **urllib3-1.19-py2.py3-none-any.whl** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/ghc-dev/3330349_1972/commit/4c764f3edae2577d324ae6595a4f42bb7bb7b231">4c764f3edae2577d324ae6595a4f42bb7bb7b231</a></p>
<p>Found in base branch: <b>second_feature_branch</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
An issue was discovered in urllib2 in Python 2.x through 2.7.16 and urllib in Python 3.x through 3.7.3. CRLF injection is possible if the attacker controls a url parameter, as demonstrated by the first argument to urllib.request.urlopen with \r\n (specifically in the query string after a ? character) followed by an HTTP header or a Redis command. This is fixed in: v2.7.17, v2.7.17rc1, v2.7.18, v2.7.18rc1; v3.5.10, v3.5.10rc1, v3.5.8, v3.5.8rc1, v3.5.8rc2, v3.5.9; v3.6.10, v3.6.10rc1, v3.6.11, v3.6.11rc1, v3.6.12, v3.6.9, v3.6.9rc1; v3.7.4, v3.7.4rc1, v3.7.4rc2, v3.7.5, v3.7.5rc1, v3.7.6, v3.7.6rc1, v3.7.7, v3.7.7rc1, v3.7.8, v3.7.8rc1, v3.7.9.
<p>Publish Date: 2019-03-13
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-9740>CVE-2019-9740</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>6.1</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: Low
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-9740">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-9740</a></p>
<p>Release Date: 2019-03-13</p>
<p>Fix Resolution: 1.24.3</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation is available for this issue
</details>
***
<p>:rescue_worker_helmet: Automatic Remediation is available for this issue.</p> | non_priority | none any whl vulnerabilities highest severity is vulnerable library none any whl http library with thread safe connection pooling file post and more library home page a href path to dependency file requirements txt path to vulnerable library requirements txt found in head commit a href vulnerabilities cve severity cvss dependency type fixed in remediation available high none any whl direct high none any whl direct medium none any whl direct medium none any whl direct details cve vulnerable library none any whl http library with thread safe connection pooling file post and more library home page a href path to dependency file requirements txt path to vulnerable library requirements txt dependency hierarchy x none any whl vulnerable library found in head commit a href found in base branch second feature branch vulnerability details before version does not remove the authorization http header when following a cross origin redirect i e a redirect that differs in host port or scheme this can allow for credentials in the authorization header to be exposed to unintended hosts or transmitted in cleartext 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 rescue worker helmet automatic remediation is available for this issue cve vulnerable library none any whl http library with thread safe connection pooling file post and more library home page a href path to dependency file requirements txt path to vulnerable library requirements txt dependency hierarchy x none any whl vulnerable library found in head commit a href found in base branch second feature branch vulnerability details the library before for python mishandles certain cases where the desired set of ca certificates is different from the os store of ca certificates which results in ssl connections succeeding in situations where a verification failure is the correct outcome this is related to use of the ssl context ca certs or ca certs dir argument 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 high availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution rescue worker helmet automatic remediation is available for this issue cve vulnerable library none any whl http library with thread safe connection pooling file post and more library home page a href path to dependency file requirements txt path to vulnerable library requirements txt dependency hierarchy x none any whl vulnerable library found in head commit a href found in base branch second feature branch vulnerability details before allows crlf injection if the attacker controls the http request method as demonstrated by inserting cr and lf control characters in the first argument of putrequest note this is similar to cve 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 low integrity impact low availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution rescue worker helmet automatic remediation is available for this issue cve vulnerable library none any whl http library with thread safe connection pooling file post and more library home page a href path to dependency file requirements txt path to vulnerable library requirements txt dependency hierarchy x none any whl vulnerable library found in head commit a href found in base branch second feature branch vulnerability details an issue was discovered in in python x through and urllib in python x through crlf injection is possible if the attacker controls a url parameter as demonstrated by the first argument to urllib request urlopen with r n specifically in the query string after a character followed by an http header or a redis command this is fixed in publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction required scope changed impact metrics confidentiality impact low integrity impact low availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution rescue worker helmet automatic remediation is available for this issue rescue worker helmet automatic remediation is available for this issue | 0 |
40,500 | 5,299,836,166 | IssuesEvent | 2017-02-10 01:44:50 | backdrop/backdrop-issues | https://api.github.com/repos/backdrop/backdrop-issues | closed | 1.6.0 regression: Layouts: Header block: Site info checkboxes not saved after hitting the "Update block" button. | pr - reviewed & tested by the community status - has pull request type - bug report | From my testing, this only happens with this specific block and only for these specific settings within it (logo, name, slogan). The rest of the block settings seem to be saved fine. Seems to be caused by the move of these settings inside a fieldset in https://github.com/backdrop/backdrop/pull/1723
PS: this effects only the ability to show/hide the logo/name/slogan. There respective settings under `admin/config/system/site-information` are saved properly and also properly rendered in the header section.
---
~PR by @klonos: https://github.com/backdrop/backdrop/pull/1756~
Replaced with PR by @jenlampton at https://github.com/backdrop/backdrop/pull/1778 (Edit Dinornis) | 1.0 | 1.6.0 regression: Layouts: Header block: Site info checkboxes not saved after hitting the "Update block" button. - From my testing, this only happens with this specific block and only for these specific settings within it (logo, name, slogan). The rest of the block settings seem to be saved fine. Seems to be caused by the move of these settings inside a fieldset in https://github.com/backdrop/backdrop/pull/1723
PS: this effects only the ability to show/hide the logo/name/slogan. There respective settings under `admin/config/system/site-information` are saved properly and also properly rendered in the header section.
---
~PR by @klonos: https://github.com/backdrop/backdrop/pull/1756~
Replaced with PR by @jenlampton at https://github.com/backdrop/backdrop/pull/1778 (Edit Dinornis) | non_priority | regression layouts header block site info checkboxes not saved after hitting the update block button from my testing this only happens with this specific block and only for these specific settings within it logo name slogan the rest of the block settings seem to be saved fine seems to be caused by the move of these settings inside a fieldset in ps this effects only the ability to show hide the logo name slogan there respective settings under admin config system site information are saved properly and also properly rendered in the header section pr by klonos replaced with pr by jenlampton at edit dinornis | 0 |
12,511 | 7,922,784,683 | IssuesEvent | 2018-07-05 12:05:26 | gama-platform/gama | https://api.github.com/repos/gama-platform/gama | closed | New project pop up window too small | > Bug Affects Usability OS Windows Version 1.8 RC | ### Steps to reproduce
1. In GAMA, File / New ... / Gama Project
3.
### Expected behavior
Tell us what should happen (include all relevant expectations)
### Actual behavior
The popup window is too small to let appear the field to enter the new of the project.
We had to increase the size to use it properly.
### System and version
GAMA 1.8 RC, seems to be Windows 10 only
| True | New project pop up window too small - ### Steps to reproduce
1. In GAMA, File / New ... / Gama Project
3.
### Expected behavior
Tell us what should happen (include all relevant expectations)
### Actual behavior
The popup window is too small to let appear the field to enter the new of the project.
We had to increase the size to use it properly.
### System and version
GAMA 1.8 RC, seems to be Windows 10 only
| non_priority | new project pop up window too small steps to reproduce in gama file new gama project expected behavior tell us what should happen include all relevant expectations actual behavior the popup window is too small to let appear the field to enter the new of the project we had to increase the size to use it properly system and version gama rc seems to be windows only | 0 |
8,131 | 3,141,557,910 | IssuesEvent | 2015-09-12 18:13:18 | yyoon/Journaley | https://api.github.com/repos/yyoon/Journaley | closed | Journaley Website | Documentation | I'm currently investigating making a simple website for Journaley. Will likely be using a simple wordpess site for now.
The website would contain likely contain 2 to 3 pages:
1. Home Page >> Acts as the page explaining *what* Journaley is and tries to justify why you might want to write a journal.
2. About >> Explain who is behind Journaley and a paragraph justifying Journaley's existence. And finally provide ways to contact.
2. Dev Blog >> A way to communicate with users with progress and release notes etc. | 1.0 | Journaley Website - I'm currently investigating making a simple website for Journaley. Will likely be using a simple wordpess site for now.
The website would contain likely contain 2 to 3 pages:
1. Home Page >> Acts as the page explaining *what* Journaley is and tries to justify why you might want to write a journal.
2. About >> Explain who is behind Journaley and a paragraph justifying Journaley's existence. And finally provide ways to contact.
2. Dev Blog >> A way to communicate with users with progress and release notes etc. | non_priority | journaley website i m currently investigating making a simple website for journaley will likely be using a simple wordpess site for now the website would contain likely contain to pages home page acts as the page explaining what journaley is and tries to justify why you might want to write a journal about explain who is behind journaley and a paragraph justifying journaley s existence and finally provide ways to contact dev blog a way to communicate with users with progress and release notes etc | 0 |
199,221 | 22,690,855,164 | IssuesEvent | 2022-07-04 20:02:50 | TIBCOSoftware/PDToolRelease | https://api.github.com/repos/TIBCOSoftware/PDToolRelease | closed | CVE-2015-7940 (Medium) detected in bcprov-jdk15-1.32.jar - autoclosed | security vulnerability | ## CVE-2015-7940 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>bcprov-jdk15-1.32.jar</b></p></summary>
<p>The Bouncy Castle Crypto package is a Java implementation of cryptographic algorithms. This jar contains JCE provider and lightweight API for the Bouncy Castle Cryptography APIs for JDK 1.5.</p>
<p>Library home page: <a href="http://www.bouncycastle.org/java.html">http://www.bouncycastle.org/java.html</a></p>
<p>Path to vulnerable library: PDToolRelease/8.0.0/Release-8.0.0-2020-10-20/PDTool-8.0.0-2020-10-20.r1/PDTool8.0.0_installer/installer_source/PDTool/lib/tdv/bcprov-jdk15-1.32.jar</p>
<p>
Dependency Hierarchy:
- :x: **bcprov-jdk15-1.32.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://api.github.com/repos/TIBCOSoftware/PDToolRelease/commits/a7158f33cf806b5b24145bf3187826fa12f060d2">a7158f33cf806b5b24145bf3187826fa12f060d2</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 Bouncy Castle Java library before 1.51 does not validate a point is withing the elliptic curve, which makes it easier for remote attackers to obtain private keys via a series of crafted elliptic curve Diffie Hellman (ECDH) key exchanges, aka an "invalid curve attack."
<p>Publish Date: 2015-11-09
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2015-7940>CVE-2015-7940</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 2 Score Details (<b>5.0</b>)</summary>
<p>
Base Score Metrics not available</p>
</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-2015-7940">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-7940</a></p>
<p>Release Date: 2015-11-09</p>
<p>Fix Resolution: org.bouncycastle:bcprov-ext-jdk15on:1.51,org.bouncycastle:bcprov-jdk14:1.51,org.bouncycastle:bcprov-jdk15on:1.51</p>
</p>
</details>
<p></p>
***
<!-- REMEDIATE-OPEN-PR-START -->
- [ ] Check this box to open an automated fix PR
<!-- REMEDIATE-OPEN-PR-END -->
<!-- <REMEDIATE>{"isOpenPROnVulnerability":false,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"Java","groupId":"org.bouncycastle","packageName":"bcprov-jdk15","packageVersion":"1.32","packageFilePaths":[],"isTransitiveDependency":false,"dependencyTree":"org.bouncycastle:bcprov-jdk15:1.32","isMinimumFixVersionAvailable":true,"minimumFixVersion":"org.bouncycastle:bcprov-ext-jdk15on:1.51,org.bouncycastle:bcprov-jdk14:1.51,org.bouncycastle:bcprov-jdk15on:1.51"}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2015-7940","vulnerabilityDetails":"The Bouncy Castle Java library before 1.51 does not validate a point is withing the elliptic curve, which makes it easier for remote attackers to obtain private keys via a series of crafted elliptic curve Diffie Hellman (ECDH) key exchanges, aka an \"invalid curve attack.\"","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2015-7940","cvss2Severity":"medium","cvss2Score":"5.0","extraData":{}}</REMEDIATE> --> | True | CVE-2015-7940 (Medium) detected in bcprov-jdk15-1.32.jar - autoclosed - ## CVE-2015-7940 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>bcprov-jdk15-1.32.jar</b></p></summary>
<p>The Bouncy Castle Crypto package is a Java implementation of cryptographic algorithms. This jar contains JCE provider and lightweight API for the Bouncy Castle Cryptography APIs for JDK 1.5.</p>
<p>Library home page: <a href="http://www.bouncycastle.org/java.html">http://www.bouncycastle.org/java.html</a></p>
<p>Path to vulnerable library: PDToolRelease/8.0.0/Release-8.0.0-2020-10-20/PDTool-8.0.0-2020-10-20.r1/PDTool8.0.0_installer/installer_source/PDTool/lib/tdv/bcprov-jdk15-1.32.jar</p>
<p>
Dependency Hierarchy:
- :x: **bcprov-jdk15-1.32.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://api.github.com/repos/TIBCOSoftware/PDToolRelease/commits/a7158f33cf806b5b24145bf3187826fa12f060d2">a7158f33cf806b5b24145bf3187826fa12f060d2</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 Bouncy Castle Java library before 1.51 does not validate a point is withing the elliptic curve, which makes it easier for remote attackers to obtain private keys via a series of crafted elliptic curve Diffie Hellman (ECDH) key exchanges, aka an "invalid curve attack."
<p>Publish Date: 2015-11-09
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2015-7940>CVE-2015-7940</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 2 Score Details (<b>5.0</b>)</summary>
<p>
Base Score Metrics not available</p>
</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-2015-7940">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-7940</a></p>
<p>Release Date: 2015-11-09</p>
<p>Fix Resolution: org.bouncycastle:bcprov-ext-jdk15on:1.51,org.bouncycastle:bcprov-jdk14:1.51,org.bouncycastle:bcprov-jdk15on:1.51</p>
</p>
</details>
<p></p>
***
<!-- REMEDIATE-OPEN-PR-START -->
- [ ] Check this box to open an automated fix PR
<!-- REMEDIATE-OPEN-PR-END -->
<!-- <REMEDIATE>{"isOpenPROnVulnerability":false,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"Java","groupId":"org.bouncycastle","packageName":"bcprov-jdk15","packageVersion":"1.32","packageFilePaths":[],"isTransitiveDependency":false,"dependencyTree":"org.bouncycastle:bcprov-jdk15:1.32","isMinimumFixVersionAvailable":true,"minimumFixVersion":"org.bouncycastle:bcprov-ext-jdk15on:1.51,org.bouncycastle:bcprov-jdk14:1.51,org.bouncycastle:bcprov-jdk15on:1.51"}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2015-7940","vulnerabilityDetails":"The Bouncy Castle Java library before 1.51 does not validate a point is withing the elliptic curve, which makes it easier for remote attackers to obtain private keys via a series of crafted elliptic curve Diffie Hellman (ECDH) key exchanges, aka an \"invalid curve attack.\"","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2015-7940","cvss2Severity":"medium","cvss2Score":"5.0","extraData":{}}</REMEDIATE> --> | non_priority | cve medium detected in bcprov jar autoclosed cve medium severity vulnerability vulnerable library bcprov jar the bouncy castle crypto package is a java implementation of cryptographic algorithms this jar contains jce provider and lightweight api for the bouncy castle cryptography apis for jdk library home page a href path to vulnerable library pdtoolrelease release pdtool installer installer source pdtool lib tdv bcprov jar dependency hierarchy x bcprov jar vulnerable library found in head commit a href found in base branch master vulnerability details the bouncy castle java library before does not validate a point is withing the elliptic curve which makes it easier for remote attackers to obtain private keys via a series of crafted elliptic curve diffie hellman ecdh key exchanges aka an invalid curve attack publish date url a href cvss score details base score metrics not available suggested fix type upgrade version origin a href release date fix resolution org bouncycastle bcprov ext org bouncycastle bcprov org bouncycastle bcprov check this box to open an automated fix pr isopenpronvulnerability false ispackagebased true isdefaultbranch true packages istransitivedependency false dependencytree org bouncycastle bcprov isminimumfixversionavailable true minimumfixversion org bouncycastle bcprov ext org bouncycastle bcprov org bouncycastle bcprov basebranches vulnerabilityidentifier cve vulnerabilitydetails the bouncy castle java library before does not validate a point is withing the elliptic curve which makes it easier for remote attackers to obtain private keys via a series of crafted elliptic curve diffie hellman ecdh key exchanges aka an invalid curve attack vulnerabilityurl | 0 |
347,441 | 24,888,388,792 | IssuesEvent | 2022-10-28 09:44:51 | matthewphua/ped | https://api.github.com/repos/matthewphua/ped | opened | Separate workflows in help center guide | type.DocumentationBug severity.Low | Difficult to know what lines belong with what. Perhaps separate into sections.
<!--session: 1666946644498-e73631f5-45d0-458d-9dec-63b1d83b63ca-->
<!--Version: Web v3.4.4--> | 1.0 | Separate workflows in help center guide - Difficult to know what lines belong with what. Perhaps separate into sections.
<!--session: 1666946644498-e73631f5-45d0-458d-9dec-63b1d83b63ca-->
<!--Version: Web v3.4.4--> | non_priority | separate workflows in help center guide difficult to know what lines belong with what perhaps separate into sections | 0 |
29,219 | 13,065,794,305 | IssuesEvent | 2020-07-30 20:26:34 | cityofaustin/atd-data-tech | https://api.github.com/repos/cityofaustin/atd-data-tech | closed | Feature request: Add Comments feature | Need: 3-Could Have Service: Apps Type: Feature Workgroup: DTS | ## Sandbox Environment
- Member Directory
- Member Directory details
### User Story
- I'm a member/admin and would like to add comments to my profile in about my dues/membership stuff
## Functionally
- [x] Create new object table `comments`
- [x] Create field `Created Date`
- [x] Create field `Created By` - adding a connection to `Accounts`, rename to `Created By`
- [x] Create field `Modified Date`
- [x] Create field `Modified By` - adding a connection to `Accounts`, rename to `Modified By`
- [x] Create field `Comment`
- [Reference](https://builder.knack.com/atd/parking#pages/scene_28)
#### Forms
- New Comment
- Edit Comment
#### Table
- Comment table | Editable (edit button available) - Admin user role only
- Comment table | Non- Editable (Read only)
# Attachments feature
- If you get done with this earlier
| 1.0 | Feature request: Add Comments feature - ## Sandbox Environment
- Member Directory
- Member Directory details
### User Story
- I'm a member/admin and would like to add comments to my profile in about my dues/membership stuff
## Functionally
- [x] Create new object table `comments`
- [x] Create field `Created Date`
- [x] Create field `Created By` - adding a connection to `Accounts`, rename to `Created By`
- [x] Create field `Modified Date`
- [x] Create field `Modified By` - adding a connection to `Accounts`, rename to `Modified By`
- [x] Create field `Comment`
- [Reference](https://builder.knack.com/atd/parking#pages/scene_28)
#### Forms
- New Comment
- Edit Comment
#### Table
- Comment table | Editable (edit button available) - Admin user role only
- Comment table | Non- Editable (Read only)
# Attachments feature
- If you get done with this earlier
| non_priority | feature request add comments feature sandbox environment member directory member directory details user story i m a member admin and would like to add comments to my profile in about my dues membership stuff functionally create new object table comments create field created date create field created by adding a connection to accounts rename to created by create field modified date create field modified by adding a connection to accounts rename to modified by create field comment forms new comment edit comment table comment table editable edit button available admin user role only comment table non editable read only attachments feature if you get done with this earlier | 0 |
46,330 | 5,796,004,567 | IssuesEvent | 2017-05-02 18:25:47 | elastic/elasticsearch | https://api.github.com/repos/elastic/elasticsearch | closed | index sorting yaml test fails against multiple nodes | jenkins test | Link to the failure: https://elasticsearch-ci.elastic.co/job/elastic+elasticsearch+master+multijob-intake/1160 .
Despite setting the index to be sorted on the `rank` field, it seems like the results are not properly sorted.
```
> Throwable #1: java.lang.AssertionError: Failure at [indices.sort/10_basic:72]: hits.hits.0._id didn't match expected value:
> hits.hits.0._id: expected [2] but was [3]
> at __randomizedtesting.SeedInfo.seed([E5B9D8E6C696CADE:6DEDE73C686AA726]:0)
> at org.elasticsearch.test.rest.yaml.ESClientYamlSuiteTestCase.executeSection(ESClientYamlSuiteTestCase.java:346)
> at org.elasticsearch.test.rest.yaml.ESClientYamlSuiteTestCase.test(ESClientYamlSuiteTestCase.java:326)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: java.lang.AssertionError: hits.hits.0._id didn't match expected value:
> hits.hits.0._id: expected [2] but was [3]
> at org.elasticsearch.test.rest.yaml.section.MatchAssertion.doAssert(MatchAssertion.java:87)
> at org.elasticsearch.test.rest.yaml.section.Assertion.execute(Assertion.java:76)
> at org.elasticsearch.test.rest.yaml.ESClientYamlSuiteTestCase.executeSection(ESClientYamlSuiteTestCase.java:342)
> ... 37 more
``` | 1.0 | index sorting yaml test fails against multiple nodes - Link to the failure: https://elasticsearch-ci.elastic.co/job/elastic+elasticsearch+master+multijob-intake/1160 .
Despite setting the index to be sorted on the `rank` field, it seems like the results are not properly sorted.
```
> Throwable #1: java.lang.AssertionError: Failure at [indices.sort/10_basic:72]: hits.hits.0._id didn't match expected value:
> hits.hits.0._id: expected [2] but was [3]
> at __randomizedtesting.SeedInfo.seed([E5B9D8E6C696CADE:6DEDE73C686AA726]:0)
> at org.elasticsearch.test.rest.yaml.ESClientYamlSuiteTestCase.executeSection(ESClientYamlSuiteTestCase.java:346)
> at org.elasticsearch.test.rest.yaml.ESClientYamlSuiteTestCase.test(ESClientYamlSuiteTestCase.java:326)
> at java.lang.Thread.run(Thread.java:748)
> Caused by: java.lang.AssertionError: hits.hits.0._id didn't match expected value:
> hits.hits.0._id: expected [2] but was [3]
> at org.elasticsearch.test.rest.yaml.section.MatchAssertion.doAssert(MatchAssertion.java:87)
> at org.elasticsearch.test.rest.yaml.section.Assertion.execute(Assertion.java:76)
> at org.elasticsearch.test.rest.yaml.ESClientYamlSuiteTestCase.executeSection(ESClientYamlSuiteTestCase.java:342)
> ... 37 more
``` | non_priority | index sorting yaml test fails against multiple nodes link to the failure despite setting the index to be sorted on the rank field it seems like the results are not properly sorted throwable java lang assertionerror failure at hits hits id didn t match expected value hits hits id expected but was at randomizedtesting seedinfo seed at org elasticsearch test rest yaml esclientyamlsuitetestcase executesection esclientyamlsuitetestcase java at org elasticsearch test rest yaml esclientyamlsuitetestcase test esclientyamlsuitetestcase java at java lang thread run thread java caused by java lang assertionerror hits hits id didn t match expected value hits hits id expected but was at org elasticsearch test rest yaml section matchassertion doassert matchassertion java at org elasticsearch test rest yaml section assertion execute assertion java at org elasticsearch test rest yaml esclientyamlsuitetestcase executesection esclientyamlsuitetestcase java more | 0 |
85,562 | 24,625,185,866 | IssuesEvent | 2022-10-16 12:30:46 | dotnet/efcore | https://api.github.com/repos/dotnet/efcore | closed | Problem with Owned Entity: exception raised when using it and no exception without it | type-bug closed-out-of-scope customer-reported punted-for-2.2 punted-for-3.0 punted-for-3.1 area-model-building | I'm trying to emulate SQL Server's FileTable. I decided to move several attributes into separate class, so the obvious solution is Owned Entities.
There are two variants of table for test:
1. When all properties are in the "table" class.
2. When several properties are moved into separate (owned) class (FileAttributes).
The `USE_OWNED` directive lets switch between these two modes.
### Code:
```C#
#define USE_OWNED
using Microsoft.SqlServer.Types;
// FileTable emulation
[Table("Drawing", Schema = "ft")]
class Drawing
{
[Required]
[Timestamp]
[Column("stream_id")]
public Guid StreamId { get; set; }
[Column("file_stream")]
public byte[] FileStream { get; set; }
[Column("name")]
public string Name { get; set; }
[Key]
[Column("path_locator")]
public SqlHierarchyId PathLocator { get; set; }
[Column("parent_path_locator")]
public SqlHierarchyId? ParentPathLocator { get; set; }
#if USE_OWNED
public FileAttributes Attributes { get; set; }
#else
[Column("file_type")]
public string FileType { get; set; }
[Column("cached_file_size")]
public long? CachedFileSize { get; set; }
[Column("creation_time")]
public DateTimeOffset CreationTime { get; set; }
[Column("last_write_time")]
public DateTimeOffset LastWriteTime { get; set; }
[Column("last_access_time")]
public DateTimeOffset? LastAccessTime { get; set; }
[Column("is_directory")]
public bool IsDirectory { get; set; }
[Column("is_offline")]
public bool IsOffline { get; set; }
[Column("is_hidden")]
public bool IsHidden { get; set; }
[Column("is_readonly")]
public bool IsReadOnly { get; set; }
[Column("is_archive")]
public bool IsArchive { get; set; }
[Column("is_system")]
public bool IsSystem { get; set; }
[Column("is_temporary")]
public bool IsTemporary { get; set; }
#endif
}
// Owned Entity
[Owned]
class FileAttributes
{
[Column("file_type")]
public string FileType { get; set; }
[Column("cached_file_size")]
public long? CachedFileSize { get; set; }
[Column("creation_time")]
public DateTimeOffset CreationTime { get; set; }
[Column("last_write_time")]
public DateTimeOffset LastWriteTime { get; set; }
[Column("last_access_time")]
public DateTimeOffset? LastAccessTime { get; set; }
[Column("is_directory")]
public bool IsDirectory { get; set; }
[Column("is_offline")]
public bool IsOffline { get; set; }
[Column("is_hidden")]
public bool IsHidden { get; set; }
[Column("is_readonly")]
public bool IsReadOnly { get; set; }
[Column("is_archive")]
public bool IsArchive { get; set; }
[Column("is_system")]
public bool IsSystem { get; set; }
[Column("is_temporary")]
public bool IsTemporary { get; set; }
}
```
### Test code:
```C#
private void OnRun(object sender, RoutedEventArgs e)
{
using (var db = new FileStreamContext())
{
var file = db.Drawings.First();
if (file != null)
{
#if USE_OWNED
MessageBox.Show($"Is dir: {file.Attributes.IsDirectory.ToString()}");
#else
MessageBox.Show($"Is dir: {file.IsDirectory.ToString()}");
#endif
}
}
}
```
### Results:
1. When all properties are in one class, _everything is OK, and table is queried successfully_.
2. When using Owned Entity (FileAttributes), I get the following error:
> **System.ArgumentException**: Expression of type 'System.Data.SqlTypes.SqlBoolean' cannot be used for return type 'System.Boolean'
### Stack trace:
> at Microsoft.EntityFrameworkCore.Metadata.Internal.ClrAccessorFactory\`1.Create(PropertyInfo propertyInfo, IPropertyBase propertyBase)
> at Microsoft.EntityFrameworkCore.Metadata.Internal.ClrAccessorFactory\`1.Create(IPropertyBase property)
> at Microsoft.EntityFrameworkCore.Internal.NonCapturingLazyInitializer.EnsureInitialized[TParam,TValue](TValue& target, TParam param, Func\`2 valueFactory)
> at Microsoft.EntityFrameworkCore.Query.ExpressionVisitors.Internal.MemberAccessBindingExpressionVisitor.<>c__DisplayClass14_0.<VisitMethodCall>b__0(IProperty property, IQuerySource _)
> at Microsoft.EntityFrameworkCore.Query.EntityQueryModelVisitor.<>c__DisplayClass92_0\`1.<BindMethodCallExpression>b__0(IReadOnlyList\`1 ps, IQuerySource qs)
> at Microsoft.EntityFrameworkCore.Query.EntityQueryModelVisitor.BindPropertyExpressionCore[TResult](Expression propertyExpression, IQuerySource querySource, Func\`3 propertyBinder)
> at Microsoft.EntityFrameworkCore.Query.ExpressionVisitors.Internal.MemberAccessBindingExpressionVisitor.VisitMethodCall(MethodCallExpression methodCallExpression)
> at Microsoft.EntityFrameworkCore.Query.EntityQueryModelVisitor.ReplaceClauseReferences(Expression expression, IQuerySource querySource, Boolean inProjection)
> at Microsoft.EntityFrameworkCore.Query.EntityQueryModelVisitor.VisitGroupJoinClause(GroupJoinClause groupJoinClause, QueryModel queryModel, Int32 index)
> at Microsoft.EntityFrameworkCore.Query.RelationalQueryModelVisitor.VisitGroupJoinClause(GroupJoinClause groupJoinClause, QueryModel queryModel, Int32 index)
> at Remotion.Linq.QueryModelVisitorBase.VisitBodyClauses(ObservableCollection\`1 bodyClauses, QueryModel queryModel)
> at Remotion.Linq.QueryModelVisitorBase.VisitQueryModel(QueryModel queryModel)
> at Microsoft.EntityFrameworkCore.Query.EntityQueryModelVisitor.VisitQueryModel(QueryModel queryModel)
> at Microsoft.EntityFrameworkCore.Query.RelationalQueryModelVisitor.VisitQueryModel(QueryModel queryModel)
> at Microsoft.EntityFrameworkCore.Query.EntityQueryModelVisitor.CreateQueryExecutor[TResult](QueryModel queryModel)
> at Microsoft.EntityFrameworkCore.Query.Internal.QueryCompiler.CompileQueryCore[TResult](Expression query, IQueryModelGenerator queryModelGenerator, IDatabase database, IDiagnosticsLogger\`1 logger, Type contextType)
> at Microsoft.EntityFrameworkCore.Query.Internal.QueryCompiler.<>c__DisplayClass13_0\`1.<Execute>b__0()
> at Microsoft.EntityFrameworkCore.Query.Internal.CompiledQueryCache.GetOrAddQueryCore[TFunc](Object cacheKey, Func\`1 compiler)
> at Microsoft.EntityFrameworkCore.Query.Internal.QueryCompiler.Execute[TResult](Expression query)
> at FileStreamApp.Root.OnRun(Object sender, RoutedEventArgs e) in D:\Projects\FileStreamProject\FileStreamApp\Root.xaml.cs:line 39
> at System.Windows.EventRoute.InvokeHandlersImpl(Object source, RoutedEventArgs args, Boolean reRaised)
> at System.Windows.UIElement.RaiseEventImpl(DependencyObject sender, RoutedEventArgs args)
> at System.Windows.Controls.Primitives.ButtonBase.OnClick()
> at System.Windows.Controls.Button.OnClick()
> at System.Windows.Controls.Primitives.ButtonBase.OnMouseLeftButtonUp(MouseButtonEventArgs e)
> at System.Windows.RoutedEventArgs.InvokeHandler(Delegate handler, Object target)
> at System.Windows.RoutedEventHandlerInfo.InvokeHandler(Object target, RoutedEventArgs routedEventArgs)
> at System.Windows.EventRoute.InvokeHandlersImpl(Object source, RoutedEventArgs args, Boolean reRaised)
> at System.Windows.UIElement.ReRaiseEventAs(DependencyObject sender, RoutedEventArgs args, RoutedEvent newEvent)
> at System.Windows.UIElement.OnMouseUpThunk(Object sender, MouseButtonEventArgs e)
> at System.Windows.RoutedEventArgs.InvokeHandler(Delegate handler, Object target)
> at System.Windows.RoutedEventHandlerInfo.InvokeHandler(Object target, RoutedEventArgs routedEventArgs)
> at System.Windows.EventRoute.InvokeHandlersImpl(Object source, RoutedEventArgs args, Boolean reRaised)
> at System.Windows.UIElement.RaiseEventImpl(DependencyObject sender, RoutedEventArgs args)
> at System.Windows.UIElement.RaiseTrustedEvent(RoutedEventArgs args)
> at System.Windows.Input.InputManager.ProcessStagingArea()
> at System.Windows.Input.InputManager.ProcessInput(InputEventArgs input)
> at System.Windows.Input.InputProviderSite.ReportInput(InputReport inputReport)
> at System.Windows.Interop.HwndMouseInputProvider.ReportInput(IntPtr hwnd, InputMode mode, Int32 timestamp, RawMouseActions actions, Int32 x, Int32 y, Int32 wheel)
> at System.Windows.Interop.HwndMouseInputProvider.FilterMessage(IntPtr hwnd, WindowMessage msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
> at System.Windows.Interop.HwndSource.InputFilterMessage(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
> at MS.Win32.HwndWrapper.WndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
> at MS.Win32.HwndSubclass.DispatcherCallbackOperation(Object o)
> at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
> at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)
> at System.Windows.Threading.Dispatcher.LegacyInvokeImpl(DispatcherPriority priority, TimeSpan timeout, Delegate method, Object args, Int32 numArgs)
> at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam)
> at MS.Win32.UnsafeNativeMethods.DispatchMessage(MSG& msg)
> at System.Windows.Threading.Dispatcher.PushFrameImpl(DispatcherFrame frame)
> at System.Windows.Application.RunDispatcher(Object ignore)
> at System.Windows.Application.RunInternal(Window window)
> at FileStreamApp.App.Main()
### Further technical details
EF Core version: **2.1.0**
Database Provider: **Microsoft.EntityFrameworkCore.SqlServer**
Operating system: **Windows 10 x64 Home Edition 1803 build 17134.81**
IDE: **Visual Studio 2017 15.8.0 Preview 2.0**
| 1.0 | Problem with Owned Entity: exception raised when using it and no exception without it - I'm trying to emulate SQL Server's FileTable. I decided to move several attributes into separate class, so the obvious solution is Owned Entities.
There are two variants of table for test:
1. When all properties are in the "table" class.
2. When several properties are moved into separate (owned) class (FileAttributes).
The `USE_OWNED` directive lets switch between these two modes.
### Code:
```C#
#define USE_OWNED
using Microsoft.SqlServer.Types;
// FileTable emulation
[Table("Drawing", Schema = "ft")]
class Drawing
{
[Required]
[Timestamp]
[Column("stream_id")]
public Guid StreamId { get; set; }
[Column("file_stream")]
public byte[] FileStream { get; set; }
[Column("name")]
public string Name { get; set; }
[Key]
[Column("path_locator")]
public SqlHierarchyId PathLocator { get; set; }
[Column("parent_path_locator")]
public SqlHierarchyId? ParentPathLocator { get; set; }
#if USE_OWNED
public FileAttributes Attributes { get; set; }
#else
[Column("file_type")]
public string FileType { get; set; }
[Column("cached_file_size")]
public long? CachedFileSize { get; set; }
[Column("creation_time")]
public DateTimeOffset CreationTime { get; set; }
[Column("last_write_time")]
public DateTimeOffset LastWriteTime { get; set; }
[Column("last_access_time")]
public DateTimeOffset? LastAccessTime { get; set; }
[Column("is_directory")]
public bool IsDirectory { get; set; }
[Column("is_offline")]
public bool IsOffline { get; set; }
[Column("is_hidden")]
public bool IsHidden { get; set; }
[Column("is_readonly")]
public bool IsReadOnly { get; set; }
[Column("is_archive")]
public bool IsArchive { get; set; }
[Column("is_system")]
public bool IsSystem { get; set; }
[Column("is_temporary")]
public bool IsTemporary { get; set; }
#endif
}
// Owned Entity
[Owned]
class FileAttributes
{
[Column("file_type")]
public string FileType { get; set; }
[Column("cached_file_size")]
public long? CachedFileSize { get; set; }
[Column("creation_time")]
public DateTimeOffset CreationTime { get; set; }
[Column("last_write_time")]
public DateTimeOffset LastWriteTime { get; set; }
[Column("last_access_time")]
public DateTimeOffset? LastAccessTime { get; set; }
[Column("is_directory")]
public bool IsDirectory { get; set; }
[Column("is_offline")]
public bool IsOffline { get; set; }
[Column("is_hidden")]
public bool IsHidden { get; set; }
[Column("is_readonly")]
public bool IsReadOnly { get; set; }
[Column("is_archive")]
public bool IsArchive { get; set; }
[Column("is_system")]
public bool IsSystem { get; set; }
[Column("is_temporary")]
public bool IsTemporary { get; set; }
}
```
### Test code:
```C#
private void OnRun(object sender, RoutedEventArgs e)
{
using (var db = new FileStreamContext())
{
var file = db.Drawings.First();
if (file != null)
{
#if USE_OWNED
MessageBox.Show($"Is dir: {file.Attributes.IsDirectory.ToString()}");
#else
MessageBox.Show($"Is dir: {file.IsDirectory.ToString()}");
#endif
}
}
}
```
### Results:
1. When all properties are in one class, _everything is OK, and table is queried successfully_.
2. When using Owned Entity (FileAttributes), I get the following error:
> **System.ArgumentException**: Expression of type 'System.Data.SqlTypes.SqlBoolean' cannot be used for return type 'System.Boolean'
### Stack trace:
> at Microsoft.EntityFrameworkCore.Metadata.Internal.ClrAccessorFactory\`1.Create(PropertyInfo propertyInfo, IPropertyBase propertyBase)
> at Microsoft.EntityFrameworkCore.Metadata.Internal.ClrAccessorFactory\`1.Create(IPropertyBase property)
> at Microsoft.EntityFrameworkCore.Internal.NonCapturingLazyInitializer.EnsureInitialized[TParam,TValue](TValue& target, TParam param, Func\`2 valueFactory)
> at Microsoft.EntityFrameworkCore.Query.ExpressionVisitors.Internal.MemberAccessBindingExpressionVisitor.<>c__DisplayClass14_0.<VisitMethodCall>b__0(IProperty property, IQuerySource _)
> at Microsoft.EntityFrameworkCore.Query.EntityQueryModelVisitor.<>c__DisplayClass92_0\`1.<BindMethodCallExpression>b__0(IReadOnlyList\`1 ps, IQuerySource qs)
> at Microsoft.EntityFrameworkCore.Query.EntityQueryModelVisitor.BindPropertyExpressionCore[TResult](Expression propertyExpression, IQuerySource querySource, Func\`3 propertyBinder)
> at Microsoft.EntityFrameworkCore.Query.ExpressionVisitors.Internal.MemberAccessBindingExpressionVisitor.VisitMethodCall(MethodCallExpression methodCallExpression)
> at Microsoft.EntityFrameworkCore.Query.EntityQueryModelVisitor.ReplaceClauseReferences(Expression expression, IQuerySource querySource, Boolean inProjection)
> at Microsoft.EntityFrameworkCore.Query.EntityQueryModelVisitor.VisitGroupJoinClause(GroupJoinClause groupJoinClause, QueryModel queryModel, Int32 index)
> at Microsoft.EntityFrameworkCore.Query.RelationalQueryModelVisitor.VisitGroupJoinClause(GroupJoinClause groupJoinClause, QueryModel queryModel, Int32 index)
> at Remotion.Linq.QueryModelVisitorBase.VisitBodyClauses(ObservableCollection\`1 bodyClauses, QueryModel queryModel)
> at Remotion.Linq.QueryModelVisitorBase.VisitQueryModel(QueryModel queryModel)
> at Microsoft.EntityFrameworkCore.Query.EntityQueryModelVisitor.VisitQueryModel(QueryModel queryModel)
> at Microsoft.EntityFrameworkCore.Query.RelationalQueryModelVisitor.VisitQueryModel(QueryModel queryModel)
> at Microsoft.EntityFrameworkCore.Query.EntityQueryModelVisitor.CreateQueryExecutor[TResult](QueryModel queryModel)
> at Microsoft.EntityFrameworkCore.Query.Internal.QueryCompiler.CompileQueryCore[TResult](Expression query, IQueryModelGenerator queryModelGenerator, IDatabase database, IDiagnosticsLogger\`1 logger, Type contextType)
> at Microsoft.EntityFrameworkCore.Query.Internal.QueryCompiler.<>c__DisplayClass13_0\`1.<Execute>b__0()
> at Microsoft.EntityFrameworkCore.Query.Internal.CompiledQueryCache.GetOrAddQueryCore[TFunc](Object cacheKey, Func\`1 compiler)
> at Microsoft.EntityFrameworkCore.Query.Internal.QueryCompiler.Execute[TResult](Expression query)
> at FileStreamApp.Root.OnRun(Object sender, RoutedEventArgs e) in D:\Projects\FileStreamProject\FileStreamApp\Root.xaml.cs:line 39
> at System.Windows.EventRoute.InvokeHandlersImpl(Object source, RoutedEventArgs args, Boolean reRaised)
> at System.Windows.UIElement.RaiseEventImpl(DependencyObject sender, RoutedEventArgs args)
> at System.Windows.Controls.Primitives.ButtonBase.OnClick()
> at System.Windows.Controls.Button.OnClick()
> at System.Windows.Controls.Primitives.ButtonBase.OnMouseLeftButtonUp(MouseButtonEventArgs e)
> at System.Windows.RoutedEventArgs.InvokeHandler(Delegate handler, Object target)
> at System.Windows.RoutedEventHandlerInfo.InvokeHandler(Object target, RoutedEventArgs routedEventArgs)
> at System.Windows.EventRoute.InvokeHandlersImpl(Object source, RoutedEventArgs args, Boolean reRaised)
> at System.Windows.UIElement.ReRaiseEventAs(DependencyObject sender, RoutedEventArgs args, RoutedEvent newEvent)
> at System.Windows.UIElement.OnMouseUpThunk(Object sender, MouseButtonEventArgs e)
> at System.Windows.RoutedEventArgs.InvokeHandler(Delegate handler, Object target)
> at System.Windows.RoutedEventHandlerInfo.InvokeHandler(Object target, RoutedEventArgs routedEventArgs)
> at System.Windows.EventRoute.InvokeHandlersImpl(Object source, RoutedEventArgs args, Boolean reRaised)
> at System.Windows.UIElement.RaiseEventImpl(DependencyObject sender, RoutedEventArgs args)
> at System.Windows.UIElement.RaiseTrustedEvent(RoutedEventArgs args)
> at System.Windows.Input.InputManager.ProcessStagingArea()
> at System.Windows.Input.InputManager.ProcessInput(InputEventArgs input)
> at System.Windows.Input.InputProviderSite.ReportInput(InputReport inputReport)
> at System.Windows.Interop.HwndMouseInputProvider.ReportInput(IntPtr hwnd, InputMode mode, Int32 timestamp, RawMouseActions actions, Int32 x, Int32 y, Int32 wheel)
> at System.Windows.Interop.HwndMouseInputProvider.FilterMessage(IntPtr hwnd, WindowMessage msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
> at System.Windows.Interop.HwndSource.InputFilterMessage(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
> at MS.Win32.HwndWrapper.WndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
> at MS.Win32.HwndSubclass.DispatcherCallbackOperation(Object o)
> at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
> at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)
> at System.Windows.Threading.Dispatcher.LegacyInvokeImpl(DispatcherPriority priority, TimeSpan timeout, Delegate method, Object args, Int32 numArgs)
> at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam)
> at MS.Win32.UnsafeNativeMethods.DispatchMessage(MSG& msg)
> at System.Windows.Threading.Dispatcher.PushFrameImpl(DispatcherFrame frame)
> at System.Windows.Application.RunDispatcher(Object ignore)
> at System.Windows.Application.RunInternal(Window window)
> at FileStreamApp.App.Main()
### Further technical details
EF Core version: **2.1.0**
Database Provider: **Microsoft.EntityFrameworkCore.SqlServer**
Operating system: **Windows 10 x64 Home Edition 1803 build 17134.81**
IDE: **Visual Studio 2017 15.8.0 Preview 2.0**
| non_priority | problem with owned entity exception raised when using it and no exception without it i m trying to emulate sql server s filetable i decided to move several attributes into separate class so the obvious solution is owned entities there are two variants of table for test when all properties are in the table class when several properties are moved into separate owned class fileattributes the use owned directive lets switch between these two modes code c define use owned using microsoft sqlserver types filetable emulation class drawing public guid streamid get set public byte filestream get set public string name get set public sqlhierarchyid pathlocator get set public sqlhierarchyid parentpathlocator get set if use owned public fileattributes attributes get set else public string filetype get set public long cachedfilesize get set public datetimeoffset creationtime get set public datetimeoffset lastwritetime get set public datetimeoffset lastaccesstime get set public bool isdirectory get set public bool isoffline get set public bool ishidden get set public bool isreadonly get set public bool isarchive get set public bool issystem get set public bool istemporary get set endif owned entity class fileattributes public string filetype get set public long cachedfilesize get set public datetimeoffset creationtime get set public datetimeoffset lastwritetime get set public datetimeoffset lastaccesstime get set public bool isdirectory get set public bool isoffline get set public bool ishidden get set public bool isreadonly get set public bool isarchive get set public bool issystem get set public bool istemporary get set test code c private void onrun object sender routedeventargs e using var db new filestreamcontext var file db drawings first if file null if use owned messagebox show is dir file attributes isdirectory tostring else messagebox show is dir file isdirectory tostring endif results when all properties are in one class everything is ok and table is queried successfully when using owned entity fileattributes i get the following error system argumentexception expression of type system data sqltypes sqlboolean cannot be used for return type system boolean stack trace at microsoft entityframeworkcore metadata internal clraccessorfactory create propertyinfo propertyinfo ipropertybase propertybase at microsoft entityframeworkcore metadata internal clraccessorfactory create ipropertybase property at microsoft entityframeworkcore internal noncapturinglazyinitializer ensureinitialized tvalue target tparam param func valuefactory at microsoft entityframeworkcore query expressionvisitors internal memberaccessbindingexpressionvisitor c b iproperty property iquerysource at microsoft entityframeworkcore query entityquerymodelvisitor c b ireadonlylist ps iquerysource qs at microsoft entityframeworkcore query entityquerymodelvisitor bindpropertyexpressioncore expression propertyexpression iquerysource querysource func propertybinder at microsoft entityframeworkcore query expressionvisitors internal memberaccessbindingexpressionvisitor visitmethodcall methodcallexpression methodcallexpression at microsoft entityframeworkcore query entityquerymodelvisitor replaceclausereferences expression expression iquerysource querysource boolean inprojection at microsoft entityframeworkcore query entityquerymodelvisitor visitgroupjoinclause groupjoinclause groupjoinclause querymodel querymodel index at microsoft entityframeworkcore query relationalquerymodelvisitor visitgroupjoinclause groupjoinclause groupjoinclause querymodel querymodel index at remotion linq querymodelvisitorbase visitbodyclauses observablecollection bodyclauses querymodel querymodel at remotion linq querymodelvisitorbase visitquerymodel querymodel querymodel at microsoft entityframeworkcore query entityquerymodelvisitor visitquerymodel querymodel querymodel at microsoft entityframeworkcore query relationalquerymodelvisitor visitquerymodel querymodel querymodel at microsoft entityframeworkcore query entityquerymodelvisitor createqueryexecutor querymodel querymodel at microsoft entityframeworkcore query internal querycompiler compilequerycore expression query iquerymodelgenerator querymodelgenerator idatabase database idiagnosticslogger logger type contexttype at microsoft entityframeworkcore query internal querycompiler c b at microsoft entityframeworkcore query internal compiledquerycache getoraddquerycore object cachekey func compiler at microsoft entityframeworkcore query internal querycompiler execute expression query at filestreamapp root onrun object sender routedeventargs e in d projects filestreamproject filestreamapp root xaml cs line at system windows eventroute invokehandlersimpl object source routedeventargs args boolean reraised at system windows uielement raiseeventimpl dependencyobject sender routedeventargs args at system windows controls primitives buttonbase onclick at system windows controls button onclick at system windows controls primitives buttonbase onmouseleftbuttonup mousebuttoneventargs e at system windows routedeventargs invokehandler delegate handler object target at system windows routedeventhandlerinfo invokehandler object target routedeventargs routedeventargs at system windows eventroute invokehandlersimpl object source routedeventargs args boolean reraised at system windows uielement reraiseeventas dependencyobject sender routedeventargs args routedevent newevent at system windows uielement onmouseupthunk object sender mousebuttoneventargs e at system windows routedeventargs invokehandler delegate handler object target at system windows routedeventhandlerinfo invokehandler object target routedeventargs routedeventargs at system windows eventroute invokehandlersimpl object source routedeventargs args boolean reraised at system windows uielement raiseeventimpl dependencyobject sender routedeventargs args at system windows uielement raisetrustedevent routedeventargs args at system windows input inputmanager processstagingarea at system windows input inputmanager processinput inputeventargs input at system windows input inputprovidersite reportinput inputreport inputreport at system windows interop hwndmouseinputprovider reportinput intptr hwnd inputmode mode timestamp rawmouseactions actions x y wheel at system windows interop hwndmouseinputprovider filtermessage intptr hwnd windowmessage msg intptr wparam intptr lparam boolean handled at system windows interop hwndsource inputfiltermessage intptr hwnd msg intptr wparam intptr lparam boolean handled at ms hwndwrapper wndproc intptr hwnd msg intptr wparam intptr lparam boolean handled at ms hwndsubclass dispatchercallbackoperation object o at system windows threading exceptionwrapper internalrealcall delegate callback object args numargs at system windows threading exceptionwrapper trycatchwhen object source delegate callback object args numargs delegate catchhandler at system windows threading dispatcher legacyinvokeimpl dispatcherpriority priority timespan timeout delegate method object args numargs at ms hwndsubclass subclasswndproc intptr hwnd msg intptr wparam intptr lparam at ms unsafenativemethods dispatchmessage msg msg at system windows threading dispatcher pushframeimpl dispatcherframe frame at system windows application rundispatcher object ignore at system windows application runinternal window window at filestreamapp app main further technical details ef core version database provider microsoft entityframeworkcore sqlserver operating system windows home edition build ide visual studio preview | 0 |
239,271 | 26,220,628,893 | IssuesEvent | 2023-01-04 14:35:12 | elastic/kibana | https://api.github.com/repos/elastic/kibana | closed | [Security Solution] PoC of the rule upgrade workflow | Team:Detections and Resp Team: SecuritySolution Team:Detection Rules Feature:Prebuilt Detection Rules 8.7 candidate v8.7.0 | **Epic:** https://github.com/elastic/security-team/issues/1974 (internal)
## Summary
To implement the rule upgrade UI (see [designs](https://www.figma.com/file/gLHm8LpTtSkAUQHrkG3RHU/%5B8.1%5D-%5BEpic%5D-Rule-Immutability%2FCustomization?node-id=948%3A189020)), we will first need to do some software design work for the rule upgrade workflow:
- Design a data model of prebuilt rule assets
- Design a domain model that will be used on the frontend to build the rule upgrade UI
- Design API endpoints for the rule upgrade workflow
- Design an algorithm that returns a diff between several rule versions
A PoC should be built to prove the design.
## Diff algorithm
For every prebuilt rule, this algorithm will return a diff between several versions of the same rule:
- The current local rule revision (R2 on the diagram below)
- The rule version the current had been forked from (V2)
- The latest remote rule version we’re upgrading to(V4)
<img src="https://user-images.githubusercontent.com/1938181/181506981-928634ba-9e2c-403e-beec-e34be3f2aece.png" />
The algorithm should:
1. Return changes between R2 and V2
2. Return changes between V2 and V4
3. Return conflicts: fields modified in both R2 and V4. Or that information should be easily derived from the above.
4. Ignore insignificant changes, like changes in the order of rule tags
| True | [Security Solution] PoC of the rule upgrade workflow - **Epic:** https://github.com/elastic/security-team/issues/1974 (internal)
## Summary
To implement the rule upgrade UI (see [designs](https://www.figma.com/file/gLHm8LpTtSkAUQHrkG3RHU/%5B8.1%5D-%5BEpic%5D-Rule-Immutability%2FCustomization?node-id=948%3A189020)), we will first need to do some software design work for the rule upgrade workflow:
- Design a data model of prebuilt rule assets
- Design a domain model that will be used on the frontend to build the rule upgrade UI
- Design API endpoints for the rule upgrade workflow
- Design an algorithm that returns a diff between several rule versions
A PoC should be built to prove the design.
## Diff algorithm
For every prebuilt rule, this algorithm will return a diff between several versions of the same rule:
- The current local rule revision (R2 on the diagram below)
- The rule version the current had been forked from (V2)
- The latest remote rule version we’re upgrading to(V4)
<img src="https://user-images.githubusercontent.com/1938181/181506981-928634ba-9e2c-403e-beec-e34be3f2aece.png" />
The algorithm should:
1. Return changes between R2 and V2
2. Return changes between V2 and V4
3. Return conflicts: fields modified in both R2 and V4. Or that information should be easily derived from the above.
4. Ignore insignificant changes, like changes in the order of rule tags
| non_priority | poc of the rule upgrade workflow epic internal summary to implement the rule upgrade ui see we will first need to do some software design work for the rule upgrade workflow design a data model of prebuilt rule assets design a domain model that will be used on the frontend to build the rule upgrade ui design api endpoints for the rule upgrade workflow design an algorithm that returns a diff between several rule versions a poc should be built to prove the design diff algorithm for every prebuilt rule this algorithm will return a diff between several versions of the same rule the current local rule revision on the diagram below the rule version the current had been forked from the latest remote rule version we’re upgrading to the algorithm should return changes between and return changes between and return conflicts fields modified in both and or that information should be easily derived from the above ignore insignificant changes like changes in the order of rule tags | 0 |
60,180 | 12,060,531,035 | IssuesEvent | 2020-04-15 21:24:10 | SergioAlmeidaCiprianoJr/Android_Ajuda_Gestantes | https://api.github.com/repos/SergioAlmeidaCiprianoJr/Android_Ajuda_Gestantes | closed | Iniciar aplicação | code | ## Descrição
Criar projeto com android studio.
## Critérios de aceitação
- [ ] Iniciar projeto
- [ ] Nome do projeto: AjudaGestante
- [ ] Deletar "Hello World" | 1.0 | Iniciar aplicação - ## Descrição
Criar projeto com android studio.
## Critérios de aceitação
- [ ] Iniciar projeto
- [ ] Nome do projeto: AjudaGestante
- [ ] Deletar "Hello World" | non_priority | iniciar aplicação descrição criar projeto com android studio critérios de aceitação iniciar projeto nome do projeto ajudagestante deletar hello world | 0 |
63,261 | 14,656,688,982 | IssuesEvent | 2020-12-28 13:59:05 | fu1771695yongxie/pug | https://api.github.com/repos/fu1771695yongxie/pug | opened | CVE-2018-3728 (High) detected in hoek-2.16.3.tgz | security vulnerability | ## CVE-2018-3728 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>hoek-2.16.3.tgz</b></p></summary>
<p>General purpose node utilities</p>
<p>Library home page: <a href="https://registry.npmjs.org/hoek/-/hoek-2.16.3.tgz">https://registry.npmjs.org/hoek/-/hoek-2.16.3.tgz</a></p>
<p>Path to dependency file: pug/packages/pug/package.json</p>
<p>Path to vulnerable library: pug/packages/pug/node_modules/hoek/package.json,pug/packages/pug-filters/node_modules/hoek/package.json</p>
<p>
Dependency Hierarchy:
- jstransformer-less-2.3.0.tgz (Root Library)
- less-2.7.3.tgz
- request-2.81.0.tgz
- hawk-3.1.3.tgz
- :x: **hoek-2.16.3.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/fu1771695yongxie/pug/commit/f3d9ae4a0af35ee594b3929483af62083e9f8b10">f3d9ae4a0af35ee594b3929483af62083e9f8b10</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>
hoek node module before 4.2.0 and 5.0.x before 5.0.3 suffers from a Modification of Assumed-Immutable Data (MAID) vulnerability via 'merge' and 'applyToDefaults' 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-03-30
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-3728>CVE-2018-3728</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>8.8</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: 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://nvd.nist.gov/vuln/detail/CVE-2018-3728">https://nvd.nist.gov/vuln/detail/CVE-2018-3728</a></p>
<p>Release Date: 2018-03-30</p>
<p>Fix Resolution: 4.2.1,5.0.3</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-2018-3728 (High) detected in hoek-2.16.3.tgz - ## CVE-2018-3728 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>hoek-2.16.3.tgz</b></p></summary>
<p>General purpose node utilities</p>
<p>Library home page: <a href="https://registry.npmjs.org/hoek/-/hoek-2.16.3.tgz">https://registry.npmjs.org/hoek/-/hoek-2.16.3.tgz</a></p>
<p>Path to dependency file: pug/packages/pug/package.json</p>
<p>Path to vulnerable library: pug/packages/pug/node_modules/hoek/package.json,pug/packages/pug-filters/node_modules/hoek/package.json</p>
<p>
Dependency Hierarchy:
- jstransformer-less-2.3.0.tgz (Root Library)
- less-2.7.3.tgz
- request-2.81.0.tgz
- hawk-3.1.3.tgz
- :x: **hoek-2.16.3.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/fu1771695yongxie/pug/commit/f3d9ae4a0af35ee594b3929483af62083e9f8b10">f3d9ae4a0af35ee594b3929483af62083e9f8b10</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>
hoek node module before 4.2.0 and 5.0.x before 5.0.3 suffers from a Modification of Assumed-Immutable Data (MAID) vulnerability via 'merge' and 'applyToDefaults' 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-03-30
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-3728>CVE-2018-3728</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>8.8</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: 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://nvd.nist.gov/vuln/detail/CVE-2018-3728">https://nvd.nist.gov/vuln/detail/CVE-2018-3728</a></p>
<p>Release Date: 2018-03-30</p>
<p>Fix Resolution: 4.2.1,5.0.3</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 hoek tgz cve high severity vulnerability vulnerable library hoek tgz general purpose node utilities library home page a href path to dependency file pug packages pug package json path to vulnerable library pug packages pug node modules hoek package json pug packages pug filters node modules hoek package json dependency hierarchy jstransformer less tgz root library less tgz request tgz hawk tgz x hoek tgz vulnerable library found in head commit a href found in base branch master vulnerability details hoek node module before and x before suffers from a modification of assumed immutable data maid vulnerability via merge and applytodefaults 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 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 step up your open source security game with whitesource | 0 |
324,444 | 23,999,478,105 | IssuesEvent | 2022-09-14 10:12:39 | OpenEnergyPlatform/oem2orm | https://api.github.com/repos/OpenEnergyPlatform/oem2orm | closed | Metadata to ORM feature | documentation | I requested a feature to convert the _oemetadata_ JSON to ORM.
This makes the publication of data easy.
My collegue @henhuy developed this package _md2orm_ and @jh-RLI pushed it to this repo.
Planned toolchain for **Data Upload:**
1. Create **metadata** from data
2. Create ORM from metadata using `MD2ORM`
3. Create [ERM](https://en.wikipedia.org/wiki/Entity%E2%80%93relationship_model) usind `ERAlchemy`
4. Upload data to **OEP** using `oedialect`
5. Upload **metadata** and add **tags**
| 1.0 | Metadata to ORM feature - I requested a feature to convert the _oemetadata_ JSON to ORM.
This makes the publication of data easy.
My collegue @henhuy developed this package _md2orm_ and @jh-RLI pushed it to this repo.
Planned toolchain for **Data Upload:**
1. Create **metadata** from data
2. Create ORM from metadata using `MD2ORM`
3. Create [ERM](https://en.wikipedia.org/wiki/Entity%E2%80%93relationship_model) usind `ERAlchemy`
4. Upload data to **OEP** using `oedialect`
5. Upload **metadata** and add **tags**
| non_priority | metadata to orm feature i requested a feature to convert the oemetadata json to orm this makes the publication of data easy my collegue henhuy developed this package and jh rli pushed it to this repo planned toolchain for data upload create metadata from data create orm from metadata using create usind eralchemy upload data to oep using oedialect upload metadata and add tags | 0 |
33,469 | 7,719,695,903 | IssuesEvent | 2018-05-23 20:17:55 | Microsoft/vscode-python | https://api.github.com/repos/Microsoft/vscode-python | closed | Ensure reattaching to remote debugging session works (experimental debugger) | feature-debugging needs upstream fix type-code health upstream-ptvsd | In old debugger, re-attaching fails (attach second time after detaching)
Ensure we don't have the same issue with the new debugger.
Upstream PTVSD issue | 1.0 | Ensure reattaching to remote debugging session works (experimental debugger) - In old debugger, re-attaching fails (attach second time after detaching)
Ensure we don't have the same issue with the new debugger.
Upstream PTVSD issue | non_priority | ensure reattaching to remote debugging session works experimental debugger in old debugger re attaching fails attach second time after detaching ensure we don t have the same issue with the new debugger upstream ptvsd issue | 0 |
30,455 | 13,247,934,364 | IssuesEvent | 2020-08-19 18:05:13 | terraform-providers/terraform-provider-aws | https://api.github.com/repos/terraform-providers/terraform-provider-aws | closed | r/aws_spot_instance_request: Tag-on-create | enhancement service/ec2 | <!--- Please keep this note for the community --->
### Community Note
* Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue to help the community and maintainers prioritize this request
* Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
* If you are interested in working on this issue or have submitted a pull request, please leave a comment
<!--- Thank you for keeping this note for the community --->
### Description
<!--- Please leave a helpful description of the feature request here. --->
> EC2 Spot now enables customers to tag their Spot Instances Requests on creation.
### New or Affected Resource(s)
<!--- Please list the new or affected resources and data sources. --->
* [`aws_spot_instance_request`](https://www.terraform.io/docs/providers/aws/r/spot_instance_request.html)
### References
<!---
Information about referencing Github Issues: https://help.github.com/articles/basic-writing-and-formatting-syntax/#referencing-issues-and-pull-requests
Are there any other GitHub issues (open or closed) or pull requests that should be linked here? Vendor blog posts or documentation? For example:
* https://aws.amazon.com/about-aws/whats-new/2018/04/introducing-amazon-ec2-fleet/
--->
[Announcement](https://aws.amazon.com/about-aws/whats-new/2020/07/amazon-ec2-now-supports-tagging-ec2-spot-instance-requests/).
Requires [AWS SDK v1.33.4](https://github.com/aws/aws-sdk-go/releases/tag/v1.33.4):
* #14000
| 1.0 | r/aws_spot_instance_request: Tag-on-create - <!--- Please keep this note for the community --->
### Community Note
* Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue to help the community and maintainers prioritize this request
* Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
* If you are interested in working on this issue or have submitted a pull request, please leave a comment
<!--- Thank you for keeping this note for the community --->
### Description
<!--- Please leave a helpful description of the feature request here. --->
> EC2 Spot now enables customers to tag their Spot Instances Requests on creation.
### New or Affected Resource(s)
<!--- Please list the new or affected resources and data sources. --->
* [`aws_spot_instance_request`](https://www.terraform.io/docs/providers/aws/r/spot_instance_request.html)
### References
<!---
Information about referencing Github Issues: https://help.github.com/articles/basic-writing-and-formatting-syntax/#referencing-issues-and-pull-requests
Are there any other GitHub issues (open or closed) or pull requests that should be linked here? Vendor blog posts or documentation? For example:
* https://aws.amazon.com/about-aws/whats-new/2018/04/introducing-amazon-ec2-fleet/
--->
[Announcement](https://aws.amazon.com/about-aws/whats-new/2020/07/amazon-ec2-now-supports-tagging-ec2-spot-instance-requests/).
Requires [AWS SDK v1.33.4](https://github.com/aws/aws-sdk-go/releases/tag/v1.33.4):
* #14000
| non_priority | r aws spot instance request tag on create community note please vote on this issue by adding a 👍 to the original issue to help the community and maintainers prioritize this request please do not leave or other comments that do not add relevant new information or questions they generate extra noise for issue followers and do not help prioritize the request if you are interested in working on this issue or have submitted a pull request please leave a comment description spot now enables customers to tag their spot instances requests on creation new or affected resource s references information about referencing github issues are there any other github issues open or closed or pull requests that should be linked here vendor blog posts or documentation for example requires | 0 |
126,943 | 17,145,783,257 | IssuesEvent | 2021-07-13 14:28:07 | Zubiik/HangarFest | https://api.github.com/repos/Zubiik/HangarFest | opened | Typographie | Design | Trouver les 2 typo de hangar festival pour pouvoir les utiliser dans le site
Demander a la personne qui à designer hangar festival | 1.0 | Typographie - Trouver les 2 typo de hangar festival pour pouvoir les utiliser dans le site
Demander a la personne qui à designer hangar festival | non_priority | typographie trouver les typo de hangar festival pour pouvoir les utiliser dans le site demander a la personne qui à designer hangar festival | 0 |
208,095 | 16,103,651,200 | IssuesEvent | 2021-04-27 12:37:35 | ministryofjustice/modernisation-platform | https://api.github.com/repos/ministryofjustice/modernisation-platform | closed | Define a networking strategy: VPCs/DNS/CIDR ranges | core networking documentation mvp | We should define a networking strategy for VPCs, DNS, and CIDR ranges to ensure we can automate, monitor and configure application VPCs centrally. | 1.0 | Define a networking strategy: VPCs/DNS/CIDR ranges - We should define a networking strategy for VPCs, DNS, and CIDR ranges to ensure we can automate, monitor and configure application VPCs centrally. | non_priority | define a networking strategy vpcs dns cidr ranges we should define a networking strategy for vpcs dns and cidr ranges to ensure we can automate monitor and configure application vpcs centrally | 0 |
336,206 | 24,489,401,694 | IssuesEvent | 2022-10-09 21:35:40 | VSangarya/AMATSA | https://api.github.com/repos/VSangarya/AMATSA | closed | Generate code documentation | documentation help wanted | Generate docs for code using some tool. https://docs.python.org/3/library/pydoc.html is a good source to read about. | 1.0 | Generate code documentation - Generate docs for code using some tool. https://docs.python.org/3/library/pydoc.html is a good source to read about. | non_priority | generate code documentation generate docs for code using some tool is a good source to read about | 0 |
260,615 | 27,784,667,603 | IssuesEvent | 2023-03-17 01:27:01 | andythinkpower/vuex | https://api.github.com/repos/andythinkpower/vuex | opened | CVE-2023-28155 (Medium) detected in request-2.88.2.tgz | Mend: dependency security vulnerability | ## CVE-2023-28155 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>request-2.88.2.tgz</b></p></summary>
<p>Simplified HTTP request client.</p>
<p>Library home page: <a href="https://registry.npmjs.org/request/-/request-2.88.2.tgz">https://registry.npmjs.org/request/-/request-2.88.2.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/request/package.json</p>
<p>
Dependency Hierarchy:
- chromedriver-2.46.0.tgz (Root Library)
- :x: **request-2.88.2.tgz** (Vulnerable Library)
<p>Found in base branch: <b>dev</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>
** UNSUPPORTED WHEN ASSIGNED ** The Request package through 2.88.1 for Node.js allows a bypass of SSRF mitigations via an attacker-controller server that does a cross-protocol redirect (HTTP to HTTPS, or HTTPS to HTTP). NOTE: This vulnerability only affects products that are no longer supported by the maintainer.
<p>Publish Date: 2023-03-16
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2023-28155>CVE-2023-28155</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-28155 (Medium) detected in request-2.88.2.tgz - ## CVE-2023-28155 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>request-2.88.2.tgz</b></p></summary>
<p>Simplified HTTP request client.</p>
<p>Library home page: <a href="https://registry.npmjs.org/request/-/request-2.88.2.tgz">https://registry.npmjs.org/request/-/request-2.88.2.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/request/package.json</p>
<p>
Dependency Hierarchy:
- chromedriver-2.46.0.tgz (Root Library)
- :x: **request-2.88.2.tgz** (Vulnerable Library)
<p>Found in base branch: <b>dev</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>
** UNSUPPORTED WHEN ASSIGNED ** The Request package through 2.88.1 for Node.js allows a bypass of SSRF mitigations via an attacker-controller server that does a cross-protocol redirect (HTTP to HTTPS, or HTTPS to HTTP). NOTE: This vulnerability only affects products that are no longer supported by the maintainer.
<p>Publish Date: 2023-03-16
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2023-28155>CVE-2023-28155</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 request tgz cve medium severity vulnerability vulnerable library request tgz simplified http request client library home page a href path to dependency file package json path to vulnerable library node modules request package json dependency hierarchy chromedriver tgz root library x request tgz vulnerable library found in base branch dev vulnerability details unsupported when assigned the request package through for node js allows a bypass of ssrf mitigations via an attacker controller server that does a cross protocol redirect http to https or https to http note this vulnerability only affects products that are no longer supported by the maintainer 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 |
963 | 2,668,319,918 | IssuesEvent | 2015-03-23 07:32:36 | tarantool/tarantool | https://api.github.com/repos/tarantool/tarantool | opened | Fails build on FreeBSD | broken build | ```
[ 53%] Building CXX object src/box/CMakeFiles/box.dir/memtx_engine.cc.o
In file included from /home/vg/Develop/Tarantool/tarantool/src/box/memtx_engine.cc:44:
/home/vg/Develop/Tarantool/tarantool/src/box/recovery.h:75:19: error: field has incomplete
type 'struct sockaddr'
struct sockaddr addr;
^
/usr/include/netinet/in.h:574:8: note: forward declaration of 'sockaddr'
struct sockaddr;
^
/home/vg/Develop/Tarantool/tarantool/src/box/memtx_engine.cc:445:6: error: use of
undeclared identifier 'WIFSIGNALED'
if (WIFSIGNALED(rc))
^
/home/vg/Develop/Tarantool/tarantool/src/box/memtx_engine.cc:448:8: error: use of
undeclared identifier 'WEXITSTATUS'
rc = WEXITSTATUS(rc);
^
3 errors generated.
src/box/CMakeFiles/box.dir/build.make:505: recipe for target 'src/box/CMakeFiles/box.dir/memtx_engine.cc.o' failed
gmake[2]: *** [src/box/CMakeFiles/box.dir/memtx_engine.cc.o] Error 1
CMakeFiles/Makefile2:1039: recipe for target 'src/box/CMakeFiles/box.dir/all' failed
gmake[1]: *** [src/box/CMakeFiles/box.dir/all] Error 2
Makefile:137: recipe for target 'all' failed
gmake: *** [all] Error 2
```
```
[ 43%] Building CXX object src/box/CMakeFiles/box.dir/memtx_engine.cc.o
In file included from /home/vg/Develop/Tarantool/tarantool/src/box/memtx_engine.cc:45:
/home/vg/Develop/Tarantool/tarantool/src/box/recovery.h:75:19: error: field has incomplete
type 'struct sockaddr'
struct sockaddr addr;
^
/usr/include/netinet/in.h:574:8: note: forward declaration of 'sockaddr'
struct sockaddr;
^
1 error generated.
src/box/CMakeFiles/box.dir/build.make:505: recipe for target 'src/box/CMakeFiles/box.dir/memtx_engine.cc.o' failed
gmake[2]: *** [src/box/CMakeFiles/box.dir/memtx_engine.cc.o] Error 1
CMakeFiles/Makefile2:1004: recipe for target 'src/box/CMakeFiles/box.dir/all' failed
gmake[1]: *** [src/box/CMakeFiles/box.dir/all] Error 2
Makefile:137: recipe for target 'all' failed
gmake: *** [all] Error 2
``` | 1.0 | Fails build on FreeBSD - ```
[ 53%] Building CXX object src/box/CMakeFiles/box.dir/memtx_engine.cc.o
In file included from /home/vg/Develop/Tarantool/tarantool/src/box/memtx_engine.cc:44:
/home/vg/Develop/Tarantool/tarantool/src/box/recovery.h:75:19: error: field has incomplete
type 'struct sockaddr'
struct sockaddr addr;
^
/usr/include/netinet/in.h:574:8: note: forward declaration of 'sockaddr'
struct sockaddr;
^
/home/vg/Develop/Tarantool/tarantool/src/box/memtx_engine.cc:445:6: error: use of
undeclared identifier 'WIFSIGNALED'
if (WIFSIGNALED(rc))
^
/home/vg/Develop/Tarantool/tarantool/src/box/memtx_engine.cc:448:8: error: use of
undeclared identifier 'WEXITSTATUS'
rc = WEXITSTATUS(rc);
^
3 errors generated.
src/box/CMakeFiles/box.dir/build.make:505: recipe for target 'src/box/CMakeFiles/box.dir/memtx_engine.cc.o' failed
gmake[2]: *** [src/box/CMakeFiles/box.dir/memtx_engine.cc.o] Error 1
CMakeFiles/Makefile2:1039: recipe for target 'src/box/CMakeFiles/box.dir/all' failed
gmake[1]: *** [src/box/CMakeFiles/box.dir/all] Error 2
Makefile:137: recipe for target 'all' failed
gmake: *** [all] Error 2
```
```
[ 43%] Building CXX object src/box/CMakeFiles/box.dir/memtx_engine.cc.o
In file included from /home/vg/Develop/Tarantool/tarantool/src/box/memtx_engine.cc:45:
/home/vg/Develop/Tarantool/tarantool/src/box/recovery.h:75:19: error: field has incomplete
type 'struct sockaddr'
struct sockaddr addr;
^
/usr/include/netinet/in.h:574:8: note: forward declaration of 'sockaddr'
struct sockaddr;
^
1 error generated.
src/box/CMakeFiles/box.dir/build.make:505: recipe for target 'src/box/CMakeFiles/box.dir/memtx_engine.cc.o' failed
gmake[2]: *** [src/box/CMakeFiles/box.dir/memtx_engine.cc.o] Error 1
CMakeFiles/Makefile2:1004: recipe for target 'src/box/CMakeFiles/box.dir/all' failed
gmake[1]: *** [src/box/CMakeFiles/box.dir/all] Error 2
Makefile:137: recipe for target 'all' failed
gmake: *** [all] Error 2
``` | non_priority | fails build on freebsd building cxx object src box cmakefiles box dir memtx engine cc o in file included from home vg develop tarantool tarantool src box memtx engine cc home vg develop tarantool tarantool src box recovery h error field has incomplete type struct sockaddr struct sockaddr addr usr include netinet in h note forward declaration of sockaddr struct sockaddr home vg develop tarantool tarantool src box memtx engine cc error use of undeclared identifier wifsignaled if wifsignaled rc home vg develop tarantool tarantool src box memtx engine cc error use of undeclared identifier wexitstatus rc wexitstatus rc errors generated src box cmakefiles box dir build make recipe for target src box cmakefiles box dir memtx engine cc o failed gmake error cmakefiles recipe for target src box cmakefiles box dir all failed gmake error makefile recipe for target all failed gmake error building cxx object src box cmakefiles box dir memtx engine cc o in file included from home vg develop tarantool tarantool src box memtx engine cc home vg develop tarantool tarantool src box recovery h error field has incomplete type struct sockaddr struct sockaddr addr usr include netinet in h note forward declaration of sockaddr struct sockaddr error generated src box cmakefiles box dir build make recipe for target src box cmakefiles box dir memtx engine cc o failed gmake error cmakefiles recipe for target src box cmakefiles box dir all failed gmake error makefile recipe for target all failed gmake error | 0 |
2,196 | 7,753,473,117 | IssuesEvent | 2018-05-31 00:52:26 | tgstation/tgstation | https://api.github.com/repos/tgstation/tgstation | closed | Health scanners displaying cat people as human. | Bug Consistency Issue Maintainability/Hinders improvements | Issue reported from Round ID: 82075 (/tg/Station Bagil [ENGLISH] [US-EAST] [100% FREE LAG]
Small issue after being informed that cat people where not human I checked with a health scanner to see it showed up as human.
| True | Health scanners displaying cat people as human. - Issue reported from Round ID: 82075 (/tg/Station Bagil [ENGLISH] [US-EAST] [100% FREE LAG]
Small issue after being informed that cat people where not human I checked with a health scanner to see it showed up as human.
| non_priority | health scanners displaying cat people as human issue reported from round id tg station bagil small issue after being informed that cat people where not human i checked with a health scanner to see it showed up as human | 0 |
426,194 | 29,512,358,064 | IssuesEvent | 2023-06-04 04:12:54 | DS-Homebrew/DLDI | https://api.github.com/repos/DS-Homebrew/DLDI | closed | Investigate differences between DSTT and DEMON carts | bug documentation help wanted | It is widely known that DEMON carts (timebomb carts, r4i-sdhc.com, etc) are based on the DSTT. DSTT's DLDI has worked on it and has been used this way for years.
Current open-source `ttio` driver does not work on these carts. It should be noted that this driver was written based on the DSONE SDHC behaviour, which is yet another ancestor of the DSTT carts.
Some things have been noted with some hex editing of prebuilt DSONE SDHC DLDI on hand:
- DSTT perfectly implements all commands DSONE SDHC uses; the driver initializes and runs fine if you nop the SDHC checks and use an SDHC card
- This behaviour was reproduced on several other DSTT offshoots
- this exact same process does not work on a DEMON based cart; it locks up somewhere during read or write
This behaves identically to the current `ttio` driver.
Notes:
- DSTT DLDI and the previously open source `scdssdhc*` all write commands directly to REG_CARD_COMMAND, and only values that need replacing, while the new card library writes an entire u64, replacing what was previously there.
- Trying to emulate that behaviour locally doesn't work either. | 1.0 | Investigate differences between DSTT and DEMON carts - It is widely known that DEMON carts (timebomb carts, r4i-sdhc.com, etc) are based on the DSTT. DSTT's DLDI has worked on it and has been used this way for years.
Current open-source `ttio` driver does not work on these carts. It should be noted that this driver was written based on the DSONE SDHC behaviour, which is yet another ancestor of the DSTT carts.
Some things have been noted with some hex editing of prebuilt DSONE SDHC DLDI on hand:
- DSTT perfectly implements all commands DSONE SDHC uses; the driver initializes and runs fine if you nop the SDHC checks and use an SDHC card
- This behaviour was reproduced on several other DSTT offshoots
- this exact same process does not work on a DEMON based cart; it locks up somewhere during read or write
This behaves identically to the current `ttio` driver.
Notes:
- DSTT DLDI and the previously open source `scdssdhc*` all write commands directly to REG_CARD_COMMAND, and only values that need replacing, while the new card library writes an entire u64, replacing what was previously there.
- Trying to emulate that behaviour locally doesn't work either. | non_priority | investigate differences between dstt and demon carts it is widely known that demon carts timebomb carts sdhc com etc are based on the dstt dstt s dldi has worked on it and has been used this way for years current open source ttio driver does not work on these carts it should be noted that this driver was written based on the dsone sdhc behaviour which is yet another ancestor of the dstt carts some things have been noted with some hex editing of prebuilt dsone sdhc dldi on hand dstt perfectly implements all commands dsone sdhc uses the driver initializes and runs fine if you nop the sdhc checks and use an sdhc card this behaviour was reproduced on several other dstt offshoots this exact same process does not work on a demon based cart it locks up somewhere during read or write this behaves identically to the current ttio driver notes dstt dldi and the previously open source scdssdhc all write commands directly to reg card command and only values that need replacing while the new card library writes an entire replacing what was previously there trying to emulate that behaviour locally doesn t work either | 0 |
103,138 | 16,601,997,813 | IssuesEvent | 2021-06-01 20:53:48 | samq-ghdemo/SEARCH-NCJIS-nibrs | https://api.github.com/repos/samq-ghdemo/SEARCH-NCJIS-nibrs | opened | CVE-2020-5421 (Medium) detected in multiple libraries | security vulnerability | ## CVE-2020-5421 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>spring-web-5.1.7.RELEASE.jar</b>, <b>spring-web-4.3.11.RELEASE.jar</b>, <b>spring-web-5.0.9.RELEASE.jar</b></p></summary>
<p>
<details><summary><b>spring-web-5.1.7.RELEASE.jar</b></p></summary>
<p>Spring Web</p>
<p>Library home page: <a href="https://github.com/spring-projects/spring-framework">https://github.com/spring-projects/spring-framework</a></p>
<p>Path to dependency file: SEARCH-NCJIS-nibrs/tools/nibrs-summary-report-common/pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/org/springframework/spring-web/5.1.7.RELEASE/spring-web-5.1.7.RELEASE.jar</p>
<p>
Dependency Hierarchy:
- spring-boot-starter-web-2.1.5.RELEASE.jar (Root Library)
- :x: **spring-web-5.1.7.RELEASE.jar** (Vulnerable Library)
</details>
<details><summary><b>spring-web-4.3.11.RELEASE.jar</b></p></summary>
<p>Spring Web</p>
<p>Library home page: <a href="https://github.com/spring-projects/spring-framework">https://github.com/spring-projects/spring-framework</a></p>
<p>Path to dependency file: SEARCH-NCJIS-nibrs/tools/nibrs-fbi-service/pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/org/springframework/spring-web/4.3.11.RELEASE/spring-web-4.3.11.RELEASE.jar,SEARCH-NCJIS-nibrs/tools/nibrs-fbi-service/target/nibrs-fbi-service-1.0.0/WEB-INF/lib/spring-web-4.3.11.RELEASE.jar</p>
<p>
Dependency Hierarchy:
- :x: **spring-web-4.3.11.RELEASE.jar** (Vulnerable Library)
</details>
<details><summary><b>spring-web-5.0.9.RELEASE.jar</b></p></summary>
<p>Spring Web</p>
<p>Library home page: <a href="https://github.com/spring-projects/spring-framework">https://github.com/spring-projects/spring-framework</a></p>
<p>Path to dependency file: SEARCH-NCJIS-nibrs/web/nibrs-web/pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/org/springframework/spring-web/5.0.9.RELEASE/spring-web-5.0.9.RELEASE.jar,/home/wss-scanner/.m2/repository/org/springframework/spring-web/5.0.9.RELEASE/spring-web-5.0.9.RELEASE.jar,/home/wss-scanner/.m2/repository/org/springframework/spring-web/5.0.9.RELEASE/spring-web-5.0.9.RELEASE.jar,/home/wss-scanner/.m2/repository/org/springframework/spring-web/5.0.9.RELEASE/spring-web-5.0.9.RELEASE.jar,/home/wss-scanner/.m2/repository/org/springframework/spring-web/5.0.9.RELEASE/spring-web-5.0.9.RELEASE.jar,SEARCH-NCJIS-nibrs/web/nibrs-web/target/nibrs-web/WEB-INF/lib/spring-web-5.0.9.RELEASE.jar</p>
<p>
Dependency Hierarchy:
- :x: **spring-web-5.0.9.RELEASE.jar** (Vulnerable Library)
</details>
<p>Found in HEAD commit: <a href="https://github.com/samq-ghdemo/SEARCH-NCJIS-nibrs/commit/2643373aa9a184ff4ea81e98caf4009bf2ee8e91">2643373aa9a184ff4ea81e98caf4009bf2ee8e91</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>
In Spring Framework versions 5.2.0 - 5.2.8, 5.1.0 - 5.1.17, 5.0.0 - 5.0.18, 4.3.0 - 4.3.28, and older unsupported versions, the protections against RFD attacks from CVE-2015-5211 may be bypassed depending on the browser used through the use of a jsessionid path parameter.
<p>Publish Date: 2020-09-19
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-5421>CVE-2020-5421</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: High
- Privileges Required: Low
- User Interaction: Required
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: Low
- 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://tanzu.vmware.com/security/cve-2020-5421">https://tanzu.vmware.com/security/cve-2020-5421</a></p>
<p>Release Date: 2020-09-19</p>
<p>Fix Resolution: org.springframework:spring-web:4.3.29,5.0.19,5.1.18,5.2.9</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":false,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"Java","groupId":"org.springframework","packageName":"spring-web","packageVersion":"5.1.7.RELEASE","packageFilePaths":["/tools/nibrs-summary-report-common/pom.xml"],"isTransitiveDependency":true,"dependencyTree":"org.springframework.boot:spring-boot-starter-web:2.1.5.RELEASE;org.springframework:spring-web:5.1.7.RELEASE","isMinimumFixVersionAvailable":true,"minimumFixVersion":"org.springframework:spring-web:4.3.29,5.0.19,5.1.18,5.2.9"},{"packageType":"Java","groupId":"org.springframework","packageName":"spring-web","packageVersion":"4.3.11.RELEASE","packageFilePaths":["/tools/nibrs-fbi-service/pom.xml"],"isTransitiveDependency":false,"dependencyTree":"org.springframework:spring-web:4.3.11.RELEASE","isMinimumFixVersionAvailable":true,"minimumFixVersion":"org.springframework:spring-web:4.3.29,5.0.19,5.1.18,5.2.9"},{"packageType":"Java","groupId":"org.springframework","packageName":"spring-web","packageVersion":"5.0.9.RELEASE","packageFilePaths":["/web/nibrs-web/pom.xml","/tools/nibrs-staging-data-common/pom.xml","/tools/nibrs-route/pom.xml","/tools/nibrs-staging-data/pom.xml","/tools/nibrs-summary-report/pom.xml"],"isTransitiveDependency":false,"dependencyTree":"org.springframework:spring-web:5.0.9.RELEASE","isMinimumFixVersionAvailable":true,"minimumFixVersion":"org.springframework:spring-web:4.3.29,5.0.19,5.1.18,5.2.9"}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2020-5421","vulnerabilityDetails":"In Spring Framework versions 5.2.0 - 5.2.8, 5.1.0 - 5.1.17, 5.0.0 - 5.0.18, 4.3.0 - 4.3.28, and older unsupported versions, the protections against RFD attacks from CVE-2015-5211 may be bypassed depending on the browser used through the use of a jsessionid path parameter.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-5421","cvss3Severity":"medium","cvss3Score":"6.5","cvss3Metrics":{"A":"None","AC":"High","PR":"Low","S":"Changed","C":"Low","UI":"Required","AV":"Network","I":"High"},"extraData":{}}</REMEDIATE> --> | True | CVE-2020-5421 (Medium) detected in multiple libraries - ## CVE-2020-5421 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>spring-web-5.1.7.RELEASE.jar</b>, <b>spring-web-4.3.11.RELEASE.jar</b>, <b>spring-web-5.0.9.RELEASE.jar</b></p></summary>
<p>
<details><summary><b>spring-web-5.1.7.RELEASE.jar</b></p></summary>
<p>Spring Web</p>
<p>Library home page: <a href="https://github.com/spring-projects/spring-framework">https://github.com/spring-projects/spring-framework</a></p>
<p>Path to dependency file: SEARCH-NCJIS-nibrs/tools/nibrs-summary-report-common/pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/org/springframework/spring-web/5.1.7.RELEASE/spring-web-5.1.7.RELEASE.jar</p>
<p>
Dependency Hierarchy:
- spring-boot-starter-web-2.1.5.RELEASE.jar (Root Library)
- :x: **spring-web-5.1.7.RELEASE.jar** (Vulnerable Library)
</details>
<details><summary><b>spring-web-4.3.11.RELEASE.jar</b></p></summary>
<p>Spring Web</p>
<p>Library home page: <a href="https://github.com/spring-projects/spring-framework">https://github.com/spring-projects/spring-framework</a></p>
<p>Path to dependency file: SEARCH-NCJIS-nibrs/tools/nibrs-fbi-service/pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/org/springframework/spring-web/4.3.11.RELEASE/spring-web-4.3.11.RELEASE.jar,SEARCH-NCJIS-nibrs/tools/nibrs-fbi-service/target/nibrs-fbi-service-1.0.0/WEB-INF/lib/spring-web-4.3.11.RELEASE.jar</p>
<p>
Dependency Hierarchy:
- :x: **spring-web-4.3.11.RELEASE.jar** (Vulnerable Library)
</details>
<details><summary><b>spring-web-5.0.9.RELEASE.jar</b></p></summary>
<p>Spring Web</p>
<p>Library home page: <a href="https://github.com/spring-projects/spring-framework">https://github.com/spring-projects/spring-framework</a></p>
<p>Path to dependency file: SEARCH-NCJIS-nibrs/web/nibrs-web/pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/org/springframework/spring-web/5.0.9.RELEASE/spring-web-5.0.9.RELEASE.jar,/home/wss-scanner/.m2/repository/org/springframework/spring-web/5.0.9.RELEASE/spring-web-5.0.9.RELEASE.jar,/home/wss-scanner/.m2/repository/org/springframework/spring-web/5.0.9.RELEASE/spring-web-5.0.9.RELEASE.jar,/home/wss-scanner/.m2/repository/org/springframework/spring-web/5.0.9.RELEASE/spring-web-5.0.9.RELEASE.jar,/home/wss-scanner/.m2/repository/org/springframework/spring-web/5.0.9.RELEASE/spring-web-5.0.9.RELEASE.jar,SEARCH-NCJIS-nibrs/web/nibrs-web/target/nibrs-web/WEB-INF/lib/spring-web-5.0.9.RELEASE.jar</p>
<p>
Dependency Hierarchy:
- :x: **spring-web-5.0.9.RELEASE.jar** (Vulnerable Library)
</details>
<p>Found in HEAD commit: <a href="https://github.com/samq-ghdemo/SEARCH-NCJIS-nibrs/commit/2643373aa9a184ff4ea81e98caf4009bf2ee8e91">2643373aa9a184ff4ea81e98caf4009bf2ee8e91</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>
In Spring Framework versions 5.2.0 - 5.2.8, 5.1.0 - 5.1.17, 5.0.0 - 5.0.18, 4.3.0 - 4.3.28, and older unsupported versions, the protections against RFD attacks from CVE-2015-5211 may be bypassed depending on the browser used through the use of a jsessionid path parameter.
<p>Publish Date: 2020-09-19
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-5421>CVE-2020-5421</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: High
- Privileges Required: Low
- User Interaction: Required
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: Low
- 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://tanzu.vmware.com/security/cve-2020-5421">https://tanzu.vmware.com/security/cve-2020-5421</a></p>
<p>Release Date: 2020-09-19</p>
<p>Fix Resolution: org.springframework:spring-web:4.3.29,5.0.19,5.1.18,5.2.9</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":false,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"Java","groupId":"org.springframework","packageName":"spring-web","packageVersion":"5.1.7.RELEASE","packageFilePaths":["/tools/nibrs-summary-report-common/pom.xml"],"isTransitiveDependency":true,"dependencyTree":"org.springframework.boot:spring-boot-starter-web:2.1.5.RELEASE;org.springframework:spring-web:5.1.7.RELEASE","isMinimumFixVersionAvailable":true,"minimumFixVersion":"org.springframework:spring-web:4.3.29,5.0.19,5.1.18,5.2.9"},{"packageType":"Java","groupId":"org.springframework","packageName":"spring-web","packageVersion":"4.3.11.RELEASE","packageFilePaths":["/tools/nibrs-fbi-service/pom.xml"],"isTransitiveDependency":false,"dependencyTree":"org.springframework:spring-web:4.3.11.RELEASE","isMinimumFixVersionAvailable":true,"minimumFixVersion":"org.springframework:spring-web:4.3.29,5.0.19,5.1.18,5.2.9"},{"packageType":"Java","groupId":"org.springframework","packageName":"spring-web","packageVersion":"5.0.9.RELEASE","packageFilePaths":["/web/nibrs-web/pom.xml","/tools/nibrs-staging-data-common/pom.xml","/tools/nibrs-route/pom.xml","/tools/nibrs-staging-data/pom.xml","/tools/nibrs-summary-report/pom.xml"],"isTransitiveDependency":false,"dependencyTree":"org.springframework:spring-web:5.0.9.RELEASE","isMinimumFixVersionAvailable":true,"minimumFixVersion":"org.springframework:spring-web:4.3.29,5.0.19,5.1.18,5.2.9"}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2020-5421","vulnerabilityDetails":"In Spring Framework versions 5.2.0 - 5.2.8, 5.1.0 - 5.1.17, 5.0.0 - 5.0.18, 4.3.0 - 4.3.28, and older unsupported versions, the protections against RFD attacks from CVE-2015-5211 may be bypassed depending on the browser used through the use of a jsessionid path parameter.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-5421","cvss3Severity":"medium","cvss3Score":"6.5","cvss3Metrics":{"A":"None","AC":"High","PR":"Low","S":"Changed","C":"Low","UI":"Required","AV":"Network","I":"High"},"extraData":{}}</REMEDIATE> --> | non_priority | cve medium detected in multiple libraries cve medium severity vulnerability vulnerable libraries spring web release jar spring web release jar spring web release jar spring web release jar spring web library home page a href path to dependency file search ncjis nibrs tools nibrs summary report common pom xml path to vulnerable library home wss scanner repository org springframework spring web release spring web release jar dependency hierarchy spring boot starter web release jar root library x spring web release jar vulnerable library spring web release jar spring web library home page a href path to dependency file search ncjis nibrs tools nibrs fbi service pom xml path to vulnerable library home wss scanner repository org springframework spring web release spring web release jar search ncjis nibrs tools nibrs fbi service target nibrs fbi service web inf lib spring web release jar dependency hierarchy x spring web release jar vulnerable library spring web release jar spring web library home page a href path to dependency file search ncjis nibrs web nibrs web pom xml path to vulnerable library home wss scanner repository org springframework spring web release spring web release jar home wss scanner repository org springframework spring web release spring web release jar home wss scanner repository org springframework spring web release spring web release jar home wss scanner repository org springframework spring web release spring web release jar home wss scanner repository org springframework spring web release spring web release jar search ncjis nibrs web nibrs web target nibrs web web inf lib spring web release jar dependency hierarchy x spring web release jar vulnerable library found in head commit a href found in base branch master vulnerability details in spring framework versions and older unsupported versions the protections against rfd attacks from cve may be bypassed depending on the browser used through the use of a jsessionid path parameter publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity high privileges required low user interaction required scope changed impact metrics confidentiality impact low 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 org springframework spring web isopenpronvulnerability false ispackagebased true isdefaultbranch true packages istransitivedependency true dependencytree org springframework boot spring boot starter web release org springframework spring web release isminimumfixversionavailable true minimumfixversion org springframework spring web packagetype java groupid org springframework packagename spring web packageversion release packagefilepaths istransitivedependency false dependencytree org springframework spring web release isminimumfixversionavailable true minimumfixversion org springframework spring web packagetype java groupid org springframework packagename spring web packageversion release packagefilepaths istransitivedependency false dependencytree org springframework spring web release isminimumfixversionavailable true minimumfixversion org springframework spring web basebranches vulnerabilityidentifier cve vulnerabilitydetails in spring framework versions and older unsupported versions the protections against rfd attacks from cve may be bypassed depending on the browser used through the use of a jsessionid path parameter vulnerabilityurl | 0 |
197,769 | 15,689,796,034 | IssuesEvent | 2021-03-25 16:02:21 | retaildevcrews/ngsa | https://api.github.com/repos/retaildevcrews/ngsa | closed | Document PnP deploy feature crew onboarding resources | Documentation | ## Description
What:
- Document links to resources that the team has found so far around aks-secure-baseline for onboarding
Why:
- Improve onboarding experience
- Capture links from different locations in one, easy to find location.
When:
- On-going
Where:
- Discussions- https://github.com/retaildevcrews/ngsa/discussions/categories/pnp-deploy
## Tasks
- [ ] Document aks-secure-baseline links for onboarding
## Acceptance Criteria
- Enables new dev to quickly upskill on tech
- Enable new dev to quickly onboard to project
## Constraints
- N/A
## References:
- References
| 1.0 | Document PnP deploy feature crew onboarding resources - ## Description
What:
- Document links to resources that the team has found so far around aks-secure-baseline for onboarding
Why:
- Improve onboarding experience
- Capture links from different locations in one, easy to find location.
When:
- On-going
Where:
- Discussions- https://github.com/retaildevcrews/ngsa/discussions/categories/pnp-deploy
## Tasks
- [ ] Document aks-secure-baseline links for onboarding
## Acceptance Criteria
- Enables new dev to quickly upskill on tech
- Enable new dev to quickly onboard to project
## Constraints
- N/A
## References:
- References
| non_priority | document pnp deploy feature crew onboarding resources description what document links to resources that the team has found so far around aks secure baseline for onboarding why improve onboarding experience capture links from different locations in one easy to find location when on going where discussions tasks document aks secure baseline links for onboarding acceptance criteria enables new dev to quickly upskill on tech enable new dev to quickly onboard to project constraints n a references references | 0 |
328 | 5,908,767,887 | IssuesEvent | 2017-05-19 21:21:29 | jemalloc/jemalloc | https://api.github.com/repos/jemalloc/jemalloc | closed | Refactor away rtree locking | bug portability | The single-bit rtree element locking makes applications vulnerable to priority inversion deadlock. Fix this by associating a mutex with each ```extent_t```, and validating that the correct extent was locked (the ```extent_t``` could have been recycled between us reading the pointer from the rtree and acquiring the mutex). There are some important details to making this work correctly:
- Validating that the correct extent was locked can either be achieved by validating ```e_addr``` (and ```e_size``` when locking an adjacent extent that is lower in memory), or by re-reading the rtree element to make sure it has not changed.
- Extent structures must either never be deallocated (true of the current implementation, which caches discarded extent structures), or there must be a mechanism for assuring that no threads are accessing the extent structure anymore prior to it being deallocated.
- In order to portably support forking, we need to be able to iterate over all mutexes, ideally in a reasonable amount of time. This suggests that we use a fixed pool of mutexes (the size of which is a function of the number of CPUs), and create a stable mapping from (hashed) extent pointers to mutexes. With such a mapping, we don't need to store mutex pointers within ```extent_t```.
- Rather than using ```extent->e_addr``` to determine extent locking order, we must use a stable mutex ordering. Furthermore, it is possible for adjacent extents to use the same mutex, in which case care must be taken to only lock once.
| True | Refactor away rtree locking - The single-bit rtree element locking makes applications vulnerable to priority inversion deadlock. Fix this by associating a mutex with each ```extent_t```, and validating that the correct extent was locked (the ```extent_t``` could have been recycled between us reading the pointer from the rtree and acquiring the mutex). There are some important details to making this work correctly:
- Validating that the correct extent was locked can either be achieved by validating ```e_addr``` (and ```e_size``` when locking an adjacent extent that is lower in memory), or by re-reading the rtree element to make sure it has not changed.
- Extent structures must either never be deallocated (true of the current implementation, which caches discarded extent structures), or there must be a mechanism for assuring that no threads are accessing the extent structure anymore prior to it being deallocated.
- In order to portably support forking, we need to be able to iterate over all mutexes, ideally in a reasonable amount of time. This suggests that we use a fixed pool of mutexes (the size of which is a function of the number of CPUs), and create a stable mapping from (hashed) extent pointers to mutexes. With such a mapping, we don't need to store mutex pointers within ```extent_t```.
- Rather than using ```extent->e_addr``` to determine extent locking order, we must use a stable mutex ordering. Furthermore, it is possible for adjacent extents to use the same mutex, in which case care must be taken to only lock once.
| non_priority | refactor away rtree locking the single bit rtree element locking makes applications vulnerable to priority inversion deadlock fix this by associating a mutex with each extent t and validating that the correct extent was locked the extent t could have been recycled between us reading the pointer from the rtree and acquiring the mutex there are some important details to making this work correctly validating that the correct extent was locked can either be achieved by validating e addr and e size when locking an adjacent extent that is lower in memory or by re reading the rtree element to make sure it has not changed extent structures must either never be deallocated true of the current implementation which caches discarded extent structures or there must be a mechanism for assuring that no threads are accessing the extent structure anymore prior to it being deallocated in order to portably support forking we need to be able to iterate over all mutexes ideally in a reasonable amount of time this suggests that we use a fixed pool of mutexes the size of which is a function of the number of cpus and create a stable mapping from hashed extent pointers to mutexes with such a mapping we don t need to store mutex pointers within extent t rather than using extent e addr to determine extent locking order we must use a stable mutex ordering furthermore it is possible for adjacent extents to use the same mutex in which case care must be taken to only lock once | 0 |
70,054 | 13,401,414,092 | IssuesEvent | 2020-09-03 17:16:33 | dotnet/aspnetcore | https://api.github.com/repos/dotnet/aspnetcore | closed | LSP fails to initialize in VSCode after O# upgrade | area-razor.tooling feature-razor.vscode | On the very latest O# version (0.18.0-beta0082) we get an exception in VSCode when trying to Initialize the Language Server
```
[Error - 10:49:01 AM] OmniSharp.Extensions.JsonRpc.InputHandler: Failed to handle request initialize 0 - System.NullReferenceException: Object reference not set to an instance of an object.
at OmniSharp.Extensions.LanguageServer.Server.LanguageServerHelpers.DynamicallyRegisterHandlers(IClientLanguageServer client, Task initializeComplete, Registration[] registrations)
at System.Reactive.PlatformServices.ExceptionServicesImpl.Rethrow(Exception exception) in /_/Rx.NET/Source/src/System.Reactive/Internal/ExceptionServicesImpl.cs:line 16
at System.Reactive.ExceptionHelpers.Throw(Exception exception) in /_/Rx.NET/Source/src/System.Reactive/Internal/ExceptionServices.cs:line 14
at System.Reactive.Stubs.<>c.<.cctor>b__2_1(Exception ex) in /_/Rx.NET/Source/src/System.Reactive/Internal/Stubs.cs:line 16
at System.Reactive.AnonymousSafeObserver`1.OnError(Exception error) in /_/Rx.NET/Source/src/System.Reactive/AnonymousSafeObserver.cs:line 62
at System.Reactive.Sink`1.ForwardOnError(Exception error) in /_/Rx.NET/Source/src/System.Reactive/Internal/Sink.cs:line 60
at System.Reactive.Linq.ObservableImpl.Throw`1._.<>c.<Run>b__2_0(_ this) in /_/Rx.NET/Source/src/System.Reactive/Linq/Observable/Throw.cs:line 37
at System.Reactive.Concurrency.Scheduler.<>c__75`1.<ScheduleAction>b__75_0(IScheduler _, ValueTuple`2 tuple) in /_/Rx.NET/Source/src/System.Reactive/Concurrency/Scheduler.Simple.cs:line 65
at System.Reactive.Concurrency.ImmediateScheduler.Schedule[TState](TState state, Func`3 action) in /_/Rx.NET/Source/src/System.Reactive/Concurrency/ImmediateScheduler.cs:line 41
at System.Reactive.Concurrency.Scheduler.ScheduleAction[TState](IScheduler scheduler, TState state, Action`1 action) in /_/Rx.NET/Source/src/System.Reactive/Concurrency/Scheduler.Simple.cs:line 61
at System.Reactive.Linq.ObservableImpl.Throw`1._.Run(IScheduler scheduler) in /_/Rx.NET/Source/src/System.Reactive/Linq/Observable/Throw.cs:line 37
at System.Reactive.Linq.ObservableImpl.Throw`1.Run(_ sink) in /_/Rx.NET/Source/src/System.Reactive/Linq/Observable/Throw.cs:line 23
at System.Reactive.Producer`2.SubscribeRaw(IObserver`1 observer, Boolean enableSafeguard) in /_/Rx.NET/Source/src/System.Reactive/Internal/Producer.cs:line 125
at System.Reactive.Producer`2.Subscribe(IObserver`1 observer) in /_/Rx.NET/Source/src/System.Reactive/Internal/Producer.cs:line 97
at System.ObservableExtensions.Subscribe[T](IObservable`1 source) in /_/Rx.NET/Source/src/System.Reactive/Observable.Extensions.cs:line 37
at OmniSharp.Extensions.LanguageServer.Server.LanguageServerHelpers.RegisterHandlers(Task initializeComplete, IClientLanguageServer client, IServerWorkDoneManager serverWorkDoneManager, ISupportedCapabilities supportedCapabilities, IEnumerable`1 collection)
at OmniSharp.Extensions.LanguageServer.Server.LanguageServer.MediatR.IRequestHandler<OmniSharp.Extensions.LanguageServer.Protocol.Models.InternalInitializeParams,OmniSharp.Extensions.LanguageServer.Protocol.Models.InitializeResult>.Handle(InternalInitializeParams request, CancellationToken token)
at OmniSharp.Extensions.LanguageServer.Server.Pipelines.SemanticTokensDeltaPipeline`2.Handle(TRequest request, CancellationToken cancellationToken, RequestHandlerDelegate`1 next)
at OmniSharp.Extensions.LanguageServer.Server.Pipelines.ResolveCommandPipeline`2.Handle(TRequest request, CancellationToken cancellationToken, RequestHandlerDelegate`1 next)
at MediatR.Pipeline.RequestPreProcessorBehavior`2.Handle(TRequest request, CancellationToken cancellationToken, RequestHandlerDelegate`1 next)
at MediatR.Pipeline.RequestPostProcessorBehavior`2.Handle(TRequest request, CancellationToken cancellationToken, RequestHandlerDelegate`1 next)
at MediatR.Pipeline.RequestExceptionProcessorBehavior`2.Handle(TRequest request, CancellationToken cancellationToken, RequestHandlerDelegate`1 next)
at MediatR.Pipeline.RequestExceptionProcessorBehavior`2.Handle(TRequest request, CancellationToken cancellationToken, RequestHandlerDelegate`1 next)
at MediatR.Pipeline.RequestExceptionActionProcessorBehavior`2.Handle(TRequest request, CancellationToken cancellationToken, RequestHandlerDelegate`1 next)
at MediatR.Pipeline.RequestExceptionActionProcessorBehavior`2.Handle(TRequest request, CancellationToken cancellationToken, RequestHandlerDelegate`1 next)
at OmniSharp.Extensions.JsonRpc.RequestRouterBase`1.<RouteRequest>g__InnerRoute|5_0(IServiceScopeFactory serviceScopeFactory, Request request, TDescriptor descriptor, Object params, CancellationToken token, ILogger logger)
at OmniSharp.Extensions.JsonRpc.RequestRouterBase`1.RouteRequest(IRequestDescriptor`1 descriptors, Request request, CancellationToken token)
at OmniSharp.Extensions.JsonRpc.InputHandler.<>c__DisplayClass38_0.<<RouteRequest>b__5>d.MoveNext() | Method='initialize' RequestId='0'
```
I talked to @david-driscoll offline and he thinks he knows a fix, so from our end this might just mean taking a new O# beta. | 1.0 | LSP fails to initialize in VSCode after O# upgrade - On the very latest O# version (0.18.0-beta0082) we get an exception in VSCode when trying to Initialize the Language Server
```
[Error - 10:49:01 AM] OmniSharp.Extensions.JsonRpc.InputHandler: Failed to handle request initialize 0 - System.NullReferenceException: Object reference not set to an instance of an object.
at OmniSharp.Extensions.LanguageServer.Server.LanguageServerHelpers.DynamicallyRegisterHandlers(IClientLanguageServer client, Task initializeComplete, Registration[] registrations)
at System.Reactive.PlatformServices.ExceptionServicesImpl.Rethrow(Exception exception) in /_/Rx.NET/Source/src/System.Reactive/Internal/ExceptionServicesImpl.cs:line 16
at System.Reactive.ExceptionHelpers.Throw(Exception exception) in /_/Rx.NET/Source/src/System.Reactive/Internal/ExceptionServices.cs:line 14
at System.Reactive.Stubs.<>c.<.cctor>b__2_1(Exception ex) in /_/Rx.NET/Source/src/System.Reactive/Internal/Stubs.cs:line 16
at System.Reactive.AnonymousSafeObserver`1.OnError(Exception error) in /_/Rx.NET/Source/src/System.Reactive/AnonymousSafeObserver.cs:line 62
at System.Reactive.Sink`1.ForwardOnError(Exception error) in /_/Rx.NET/Source/src/System.Reactive/Internal/Sink.cs:line 60
at System.Reactive.Linq.ObservableImpl.Throw`1._.<>c.<Run>b__2_0(_ this) in /_/Rx.NET/Source/src/System.Reactive/Linq/Observable/Throw.cs:line 37
at System.Reactive.Concurrency.Scheduler.<>c__75`1.<ScheduleAction>b__75_0(IScheduler _, ValueTuple`2 tuple) in /_/Rx.NET/Source/src/System.Reactive/Concurrency/Scheduler.Simple.cs:line 65
at System.Reactive.Concurrency.ImmediateScheduler.Schedule[TState](TState state, Func`3 action) in /_/Rx.NET/Source/src/System.Reactive/Concurrency/ImmediateScheduler.cs:line 41
at System.Reactive.Concurrency.Scheduler.ScheduleAction[TState](IScheduler scheduler, TState state, Action`1 action) in /_/Rx.NET/Source/src/System.Reactive/Concurrency/Scheduler.Simple.cs:line 61
at System.Reactive.Linq.ObservableImpl.Throw`1._.Run(IScheduler scheduler) in /_/Rx.NET/Source/src/System.Reactive/Linq/Observable/Throw.cs:line 37
at System.Reactive.Linq.ObservableImpl.Throw`1.Run(_ sink) in /_/Rx.NET/Source/src/System.Reactive/Linq/Observable/Throw.cs:line 23
at System.Reactive.Producer`2.SubscribeRaw(IObserver`1 observer, Boolean enableSafeguard) in /_/Rx.NET/Source/src/System.Reactive/Internal/Producer.cs:line 125
at System.Reactive.Producer`2.Subscribe(IObserver`1 observer) in /_/Rx.NET/Source/src/System.Reactive/Internal/Producer.cs:line 97
at System.ObservableExtensions.Subscribe[T](IObservable`1 source) in /_/Rx.NET/Source/src/System.Reactive/Observable.Extensions.cs:line 37
at OmniSharp.Extensions.LanguageServer.Server.LanguageServerHelpers.RegisterHandlers(Task initializeComplete, IClientLanguageServer client, IServerWorkDoneManager serverWorkDoneManager, ISupportedCapabilities supportedCapabilities, IEnumerable`1 collection)
at OmniSharp.Extensions.LanguageServer.Server.LanguageServer.MediatR.IRequestHandler<OmniSharp.Extensions.LanguageServer.Protocol.Models.InternalInitializeParams,OmniSharp.Extensions.LanguageServer.Protocol.Models.InitializeResult>.Handle(InternalInitializeParams request, CancellationToken token)
at OmniSharp.Extensions.LanguageServer.Server.Pipelines.SemanticTokensDeltaPipeline`2.Handle(TRequest request, CancellationToken cancellationToken, RequestHandlerDelegate`1 next)
at OmniSharp.Extensions.LanguageServer.Server.Pipelines.ResolveCommandPipeline`2.Handle(TRequest request, CancellationToken cancellationToken, RequestHandlerDelegate`1 next)
at MediatR.Pipeline.RequestPreProcessorBehavior`2.Handle(TRequest request, CancellationToken cancellationToken, RequestHandlerDelegate`1 next)
at MediatR.Pipeline.RequestPostProcessorBehavior`2.Handle(TRequest request, CancellationToken cancellationToken, RequestHandlerDelegate`1 next)
at MediatR.Pipeline.RequestExceptionProcessorBehavior`2.Handle(TRequest request, CancellationToken cancellationToken, RequestHandlerDelegate`1 next)
at MediatR.Pipeline.RequestExceptionProcessorBehavior`2.Handle(TRequest request, CancellationToken cancellationToken, RequestHandlerDelegate`1 next)
at MediatR.Pipeline.RequestExceptionActionProcessorBehavior`2.Handle(TRequest request, CancellationToken cancellationToken, RequestHandlerDelegate`1 next)
at MediatR.Pipeline.RequestExceptionActionProcessorBehavior`2.Handle(TRequest request, CancellationToken cancellationToken, RequestHandlerDelegate`1 next)
at OmniSharp.Extensions.JsonRpc.RequestRouterBase`1.<RouteRequest>g__InnerRoute|5_0(IServiceScopeFactory serviceScopeFactory, Request request, TDescriptor descriptor, Object params, CancellationToken token, ILogger logger)
at OmniSharp.Extensions.JsonRpc.RequestRouterBase`1.RouteRequest(IRequestDescriptor`1 descriptors, Request request, CancellationToken token)
at OmniSharp.Extensions.JsonRpc.InputHandler.<>c__DisplayClass38_0.<<RouteRequest>b__5>d.MoveNext() | Method='initialize' RequestId='0'
```
I talked to @david-driscoll offline and he thinks he knows a fix, so from our end this might just mean taking a new O# beta. | non_priority | lsp fails to initialize in vscode after o upgrade on the very latest o version we get an exception in vscode when trying to initialize the language server omnisharp extensions jsonrpc inputhandler failed to handle request initialize system nullreferenceexception object reference not set to an instance of an object at omnisharp extensions languageserver server languageserverhelpers dynamicallyregisterhandlers iclientlanguageserver client task initializecomplete registration registrations at system reactive platformservices exceptionservicesimpl rethrow exception exception in rx net source src system reactive internal exceptionservicesimpl cs line at system reactive exceptionhelpers throw exception exception in rx net source src system reactive internal exceptionservices cs line at system reactive stubs c b exception ex in rx net source src system reactive internal stubs cs line at system reactive anonymoussafeobserver onerror exception error in rx net source src system reactive anonymoussafeobserver cs line at system reactive sink forwardonerror exception error in rx net source src system reactive internal sink cs line at system reactive linq observableimpl throw c b this in rx net source src system reactive linq observable throw cs line at system reactive concurrency scheduler c b ischeduler valuetuple tuple in rx net source src system reactive concurrency scheduler simple cs line at system reactive concurrency immediatescheduler schedule tstate state func action in rx net source src system reactive concurrency immediatescheduler cs line at system reactive concurrency scheduler scheduleaction ischeduler scheduler tstate state action action in rx net source src system reactive concurrency scheduler simple cs line at system reactive linq observableimpl throw run ischeduler scheduler in rx net source src system reactive linq observable throw cs line at system reactive linq observableimpl throw run sink in rx net source src system reactive linq observable throw cs line at system reactive producer subscriberaw iobserver observer boolean enablesafeguard in rx net source src system reactive internal producer cs line at system reactive producer subscribe iobserver observer in rx net source src system reactive internal producer cs line at system observableextensions subscribe iobservable source in rx net source src system reactive observable extensions cs line at omnisharp extensions languageserver server languageserverhelpers registerhandlers task initializecomplete iclientlanguageserver client iserverworkdonemanager serverworkdonemanager isupportedcapabilities supportedcapabilities ienumerable collection at omnisharp extensions languageserver server languageserver mediatr irequesthandler handle internalinitializeparams request cancellationtoken token at omnisharp extensions languageserver server pipelines semantictokensdeltapipeline handle trequest request cancellationtoken cancellationtoken requesthandlerdelegate next at omnisharp extensions languageserver server pipelines resolvecommandpipeline handle trequest request cancellationtoken cancellationtoken requesthandlerdelegate next at mediatr pipeline requestpreprocessorbehavior handle trequest request cancellationtoken cancellationtoken requesthandlerdelegate next at mediatr pipeline requestpostprocessorbehavior handle trequest request cancellationtoken cancellationtoken requesthandlerdelegate next at mediatr pipeline requestexceptionprocessorbehavior handle trequest request cancellationtoken cancellationtoken requesthandlerdelegate next at mediatr pipeline requestexceptionprocessorbehavior handle trequest request cancellationtoken cancellationtoken requesthandlerdelegate next at mediatr pipeline requestexceptionactionprocessorbehavior handle trequest request cancellationtoken cancellationtoken requesthandlerdelegate next at mediatr pipeline requestexceptionactionprocessorbehavior handle trequest request cancellationtoken cancellationtoken requesthandlerdelegate next at omnisharp extensions jsonrpc requestrouterbase g innerroute iservicescopefactory servicescopefactory request request tdescriptor descriptor object params cancellationtoken token ilogger logger at omnisharp extensions jsonrpc requestrouterbase routerequest irequestdescriptor descriptors request request cancellationtoken token at omnisharp extensions jsonrpc inputhandler c b d movenext method initialize requestid i talked to david driscoll offline and he thinks he knows a fix so from our end this might just mean taking a new o beta | 0 |
75,116 | 20,670,424,383 | IssuesEvent | 2022-03-10 01:08:07 | dotnet/efcore | https://api.github.com/repos/dotnet/efcore | opened | ToTable(b => {}) should map the entity type to the default table | type-bug area-model-building | Currently, if `ToView` or a similar call is performed the entity type will end up not mapped to any table. | 1.0 | ToTable(b => {}) should map the entity type to the default table - Currently, if `ToView` or a similar call is performed the entity type will end up not mapped to any table. | non_priority | totable b should map the entity type to the default table currently if toview or a similar call is performed the entity type will end up not mapped to any table | 0 |
78,333 | 14,985,374,554 | IssuesEvent | 2021-01-28 19:52:48 | pschanely/CrossHair | https://api.github.com/repos/pschanely/CrossHair | opened | Consider migrating to pytest | code health | Pytest seems like it might be better for us then unittest:
* it works better with mypy (because mypy understands real asserts)
* It's easier to selectively run tests (CrossHair has a lot of not-fast tests)
| 1.0 | Consider migrating to pytest - Pytest seems like it might be better for us then unittest:
* it works better with mypy (because mypy understands real asserts)
* It's easier to selectively run tests (CrossHair has a lot of not-fast tests)
| non_priority | consider migrating to pytest pytest seems like it might be better for us then unittest it works better with mypy because mypy understands real asserts it s easier to selectively run tests crosshair has a lot of not fast tests | 0 |
187,221 | 22,039,905,161 | IssuesEvent | 2022-05-29 07:19:21 | ronakjain2012/node-boilerplate | https://api.github.com/repos/ronakjain2012/node-boilerplate | closed | CVE-2020-7788 (High) detected in ini-1.3.5.tgz | security vulnerability | ## CVE-2020-7788 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>ini-1.3.5.tgz</b></p></summary>
<p>An ini encoder/decoder for node</p>
<p>Library home page: <a href="https://registry.npmjs.org/ini/-/ini-1.3.5.tgz">https://registry.npmjs.org/ini/-/ini-1.3.5.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/ini/package.json</p>
<p>
Dependency Hierarchy:
- npm-check-updates-4.1.2.tgz (Root Library)
- libnpmconfig-1.2.1.tgz
- :x: **ini-1.3.5.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/ronakjain2012/node-boilerplate/commit/29cfc6ccf7871c02275ffdcdd0b5a41ed0369aab">29cfc6ccf7871c02275ffdcdd0b5a41ed0369aab</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>
This affects the package ini before 1.3.6. If an attacker submits a malicious INI file to an application that parses it with ini.parse, they will pollute the prototype on the application. This can be exploited further depending on the context.
<p>Publish Date: 2020-12-11
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-7788>CVE-2020-7788</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.3</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: Low
- Integrity Impact: Low
- Availability Impact: Low
</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-2020-7788">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-7788</a></p>
<p>Release Date: 2020-12-11</p>
<p>Fix Resolution (ini): 1.3.6</p>
<p>Direct dependency fix Resolution (npm-check-updates): 5.0.0-alpha.1</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-2020-7788 (High) detected in ini-1.3.5.tgz - ## CVE-2020-7788 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>ini-1.3.5.tgz</b></p></summary>
<p>An ini encoder/decoder for node</p>
<p>Library home page: <a href="https://registry.npmjs.org/ini/-/ini-1.3.5.tgz">https://registry.npmjs.org/ini/-/ini-1.3.5.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/ini/package.json</p>
<p>
Dependency Hierarchy:
- npm-check-updates-4.1.2.tgz (Root Library)
- libnpmconfig-1.2.1.tgz
- :x: **ini-1.3.5.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/ronakjain2012/node-boilerplate/commit/29cfc6ccf7871c02275ffdcdd0b5a41ed0369aab">29cfc6ccf7871c02275ffdcdd0b5a41ed0369aab</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>
This affects the package ini before 1.3.6. If an attacker submits a malicious INI file to an application that parses it with ini.parse, they will pollute the prototype on the application. This can be exploited further depending on the context.
<p>Publish Date: 2020-12-11
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-7788>CVE-2020-7788</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.3</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: Low
- Integrity Impact: Low
- Availability Impact: Low
</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-2020-7788">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-7788</a></p>
<p>Release Date: 2020-12-11</p>
<p>Fix Resolution (ini): 1.3.6</p>
<p>Direct dependency fix Resolution (npm-check-updates): 5.0.0-alpha.1</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 ini tgz cve high severity vulnerability vulnerable library ini tgz an ini encoder decoder for node library home page a href path to dependency file package json path to vulnerable library node modules ini package json dependency hierarchy npm check updates tgz root library libnpmconfig tgz x ini tgz vulnerable library found in head commit a href found in base branch master vulnerability details this affects the package ini before if an attacker submits a malicious ini file to an application that parses it with ini parse they will pollute the prototype on the application this can be exploited further depending on the context 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 low integrity impact low availability impact low for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution ini direct dependency fix resolution npm check updates alpha step up your open source security game with whitesource | 0 |
264,089 | 19,987,147,314 | IssuesEvent | 2022-01-30 20:44:53 | UnBArqDsw2021-2/2021.2_G2_lava-jato | https://api.github.com/repos/UnBArqDsw2021-2/2021.2_G2_lava-jato | opened | Moscow | documentation Sprint 1 Priorização | ### Descrição:
Montar uma tabela com os requisitos priorizados, todos integrantes deverão priorizar os requisitos da forma que acham mais lógica, no final terá uma tabela final para o projeto.
### Tarefas:
- [ ] Tabela individual de todos os membros, devidamente priorizadas.
- [ ] Tabela geral do projeto com os requisitos priorizados.
### Critério de aceitação:
Todos os integrantes devem participar, para conseguirmos discutir e ter insumos para definir as prioridades do projeto. | 1.0 | Moscow - ### Descrição:
Montar uma tabela com os requisitos priorizados, todos integrantes deverão priorizar os requisitos da forma que acham mais lógica, no final terá uma tabela final para o projeto.
### Tarefas:
- [ ] Tabela individual de todos os membros, devidamente priorizadas.
- [ ] Tabela geral do projeto com os requisitos priorizados.
### Critério de aceitação:
Todos os integrantes devem participar, para conseguirmos discutir e ter insumos para definir as prioridades do projeto. | non_priority | moscow descrição montar uma tabela com os requisitos priorizados todos integrantes deverão priorizar os requisitos da forma que acham mais lógica no final terá uma tabela final para o projeto tarefas tabela individual de todos os membros devidamente priorizadas tabela geral do projeto com os requisitos priorizados critério de aceitação todos os integrantes devem participar para conseguirmos discutir e ter insumos para definir as prioridades do projeto | 0 |
125,822 | 10,354,548,942 | IssuesEvent | 2019-09-05 13:57:47 | trustbloc/fabric-peer-ext | https://api.github.com/repos/trustbloc/fabric-peer-ext | closed | Ledger Config Service BDD test | test | Add a BDD test for the local configuration service which includes retrieval by key and notifications of configuration updates/deletes.
Part of epic #207 | 1.0 | Ledger Config Service BDD test - Add a BDD test for the local configuration service which includes retrieval by key and notifications of configuration updates/deletes.
Part of epic #207 | non_priority | ledger config service bdd test add a bdd test for the local configuration service which includes retrieval by key and notifications of configuration updates deletes part of epic | 0 |
12,193 | 7,805,736,449 | IssuesEvent | 2018-06-11 11:56:19 | woocommerce/woocommerce | https://api.github.com/repos/woocommerce/woocommerce | closed | Woocommerce Importer meta:[fields] postmeta is inserted on each run | enhancement help wanted performance | **Describe the bug**
When I import products with the WooCommerce importer the fields marked as meta: in the export are removed and inserted in the postmeta table on each run.
This is visible due to the increasing meta_id numbers in the postmeta table. It seems like the old value is removed and the new value is inserted.
Due to this my meta_id numbers are shooting up on each import as I have thousands of products to updated regulary.
**To Reproduce**
1. Create CSV file with meta:[fields] columns
2. Import the CSV
3. Check the meta_id numbers of the meta:[fields]
4. Import the CSV (update products)
5. Check the meta_id numbers of the meta:[fields]
6. They should be highers
**Screenshots**
After one run:
**Expected behavior**
The expected behaviour should be that the postmeta values get updated. Or even better(?), values should get skipped if no change.
**Isolating the problem (mark completed items with an [x]):**
- [ no ] I have deactivated other plugins and confirmed this bug occurs when only WooCommerce plugin is active.
- [ yes ] This bug happens with a default WordPress theme active, or [Storefront](https://woocommerce.com/storefront/).
- [ yes ] I can reproduce this bug consistently using the steps above.
**WordPress Environment**
Will post this if necessarry
| True | Woocommerce Importer meta:[fields] postmeta is inserted on each run - **Describe the bug**
When I import products with the WooCommerce importer the fields marked as meta: in the export are removed and inserted in the postmeta table on each run.
This is visible due to the increasing meta_id numbers in the postmeta table. It seems like the old value is removed and the new value is inserted.
Due to this my meta_id numbers are shooting up on each import as I have thousands of products to updated regulary.
**To Reproduce**
1. Create CSV file with meta:[fields] columns
2. Import the CSV
3. Check the meta_id numbers of the meta:[fields]
4. Import the CSV (update products)
5. Check the meta_id numbers of the meta:[fields]
6. They should be highers
**Screenshots**
After one run:
**Expected behavior**
The expected behaviour should be that the postmeta values get updated. Or even better(?), values should get skipped if no change.
**Isolating the problem (mark completed items with an [x]):**
- [ no ] I have deactivated other plugins and confirmed this bug occurs when only WooCommerce plugin is active.
- [ yes ] This bug happens with a default WordPress theme active, or [Storefront](https://woocommerce.com/storefront/).
- [ yes ] I can reproduce this bug consistently using the steps above.
**WordPress Environment**
Will post this if necessarry
| non_priority | woocommerce importer meta postmeta is inserted on each run describe the bug when i import products with the woocommerce importer the fields marked as meta in the export are removed and inserted in the postmeta table on each run this is visible due to the increasing meta id numbers in the postmeta table it seems like the old value is removed and the new value is inserted due to this my meta id numbers are shooting up on each import as i have thousands of products to updated regulary to reproduce create csv file with meta columns import the csv check the meta id numbers of the meta import the csv update products check the meta id numbers of the meta they should be highers screenshots after one run expected behavior the expected behaviour should be that the postmeta values get updated or even better values should get skipped if no change isolating the problem mark completed items with an i have deactivated other plugins and confirmed this bug occurs when only woocommerce plugin is active this bug happens with a default wordpress theme active or i can reproduce this bug consistently using the steps above wordpress environment will post this if necessarry | 0 |
195,408 | 22,337,174,472 | IssuesEvent | 2022-06-14 19:43:41 | icgc-argo/platform-ui | https://api.github.com/repos/icgc-argo/platform-ui | closed | Investigate GraphQL & Apollo solutions | security dependencies | On Platform-UI all of our Apollo and GraphQL dependencies are deprecated.
1. What's the best way to use these technologies in Next 12/React 17 in our app?
2. What packages should we use?
3. Can we migrate to them before upgrading to Next 11/React 17, during, or after? What's the order of operations here?
4. What impact does this have on platform-UI? Does it impact other projects?
5. What's the level of effort?
---
Results:
1. Our current approach is OK, no major refactoring needed.
2. Migrate to apollo/client 3. https://github.com/icgc-argo/platform-ui/issues/2301 GraphQL may require more investigation after the Apollo ticket.
3. We have to update Apollo/GraphQL before Next/React.
4. No significant impact, beyond updating these packages and some minor API changes.
5. 5 story points. Would be 3 but GQL is a question mark.
GraphQL details:
- graphql-import & graphql-tools can be removed.
- 2 `babel-*-graphql` libraries have API changes with Apollo 3.
- graphql library itself: 2 versions behind.
- Will re-evaluate when Apollo is updated. | True | Investigate GraphQL & Apollo solutions - On Platform-UI all of our Apollo and GraphQL dependencies are deprecated.
1. What's the best way to use these technologies in Next 12/React 17 in our app?
2. What packages should we use?
3. Can we migrate to them before upgrading to Next 11/React 17, during, or after? What's the order of operations here?
4. What impact does this have on platform-UI? Does it impact other projects?
5. What's the level of effort?
---
Results:
1. Our current approach is OK, no major refactoring needed.
2. Migrate to apollo/client 3. https://github.com/icgc-argo/platform-ui/issues/2301 GraphQL may require more investigation after the Apollo ticket.
3. We have to update Apollo/GraphQL before Next/React.
4. No significant impact, beyond updating these packages and some minor API changes.
5. 5 story points. Would be 3 but GQL is a question mark.
GraphQL details:
- graphql-import & graphql-tools can be removed.
- 2 `babel-*-graphql` libraries have API changes with Apollo 3.
- graphql library itself: 2 versions behind.
- Will re-evaluate when Apollo is updated. | non_priority | investigate graphql apollo solutions on platform ui all of our apollo and graphql dependencies are deprecated what s the best way to use these technologies in next react in our app what packages should we use can we migrate to them before upgrading to next react during or after what s the order of operations here what impact does this have on platform ui does it impact other projects what s the level of effort results our current approach is ok no major refactoring needed migrate to apollo client graphql may require more investigation after the apollo ticket we have to update apollo graphql before next react no significant impact beyond updating these packages and some minor api changes story points would be but gql is a question mark graphql details graphql import graphql tools can be removed babel graphql libraries have api changes with apollo graphql library itself versions behind will re evaluate when apollo is updated | 0 |
239,379 | 18,271,708,833 | IssuesEvent | 2021-10-04 14:25:51 | embedded-office/canopen-stack | https://api.github.com/repos/embedded-office/canopen-stack | closed | Function description missing on API page "Object Entry" | documentation | **Describe the bug**
Missing description for function `COObjTypeUserSDOAbort()` in Functions table on API page [Object Entry](https://canopen-stack.org/docs/api/object/)
| 1.0 | Function description missing on API page "Object Entry" - **Describe the bug**
Missing description for function `COObjTypeUserSDOAbort()` in Functions table on API page [Object Entry](https://canopen-stack.org/docs/api/object/)
| non_priority | function description missing on api page object entry describe the bug missing description for function coobjtypeusersdoabort in functions table on api page | 0 |
111,079 | 17,009,704,465 | IssuesEvent | 2021-07-02 01:09:30 | tamirdahan/keycloak | https://api.github.com/repos/tamirdahan/keycloak | opened | CVE-2020-27216 (High) detected in jetty-webapp-9.2.4.v20141103.jar | security vulnerability | ## CVE-2020-27216 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>jetty-webapp-9.2.4.v20141103.jar</b></p></summary>
<p>Jetty web application support</p>
<p>Library home page: <a href="http://www.eclipse.org/jetty">http://www.eclipse.org/jetty</a></p>
<p>Path to dependency file: keycloak/adapters/oidc/spring-boot/pom.xml</p>
<p>Path to vulnerable library: canner/.m2/repository/org/eclipse/jetty/jetty-webapp/9.2.4.v20141103/jetty-webapp-9.2.4.v20141103.jar,canner/.m2/repository/org/eclipse/jetty/jetty-webapp/9.2.4.v20141103/jetty-webapp-9.2.4.v20141103.jar,canner/.m2/repository/org/eclipse/jetty/jetty-webapp/9.2.4.v20141103/jetty-webapp-9.2.4.v20141103.jar</p>
<p>
Dependency Hierarchy:
- :x: **jetty-webapp-9.2.4.v20141103.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/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
In Eclipse Jetty versions 1.0 thru 9.4.32.v20200930, 10.0.0.alpha1 thru 10.0.0.beta2, and 11.0.0.alpha1 thru 11.0.0.beta2O, on Unix like systems, the system's temporary directory is shared between all users on that system. A collocated user can observe the process of creating a temporary sub directory in the shared temporary directory and race to complete the creation of the temporary subdirectory. If the attacker wins the race then they will have read and write permission to the subdirectory used to unpack web applications, including their WEB-INF/lib jar files and JSP files. If any code is ever executed out of this temporary directory, this can lead to a local privilege escalation vulnerability.
<p>Publish Date: 2020-10-23
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-27216>CVE-2020-27216</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.0</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: High
- Privileges Required: Low
- 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://bugs.eclipse.org/bugs/show_bug.cgi?id=567921">https://bugs.eclipse.org/bugs/show_bug.cgi?id=567921</a></p>
<p>Release Date: 2020-10-20</p>
<p>Fix Resolution: org.eclipse.jetty:jetty-runner:9.4.33,10.0.0.beta3,11.0.0.beta3;org.eclipse.jetty:jetty-webapp:9.4.33,10.0.0.beta3,11.0.0.beta3</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":false,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"Java","groupId":"org.eclipse.jetty","packageName":"jetty-webapp","packageVersion":"9.2.4.v20141103","packageFilePaths":["/adapters/oidc/spring-boot/pom.xml","/adapters/oidc/spring-boot-adapter-core/pom.xml","/adapters/oidc/spring-boot2/pom.xml"],"isTransitiveDependency":false,"dependencyTree":"org.eclipse.jetty:jetty-webapp:9.2.4.v20141103","isMinimumFixVersionAvailable":true,"minimumFixVersion":"org.eclipse.jetty:jetty-runner:9.4.33,10.0.0.beta3,11.0.0.beta3;org.eclipse.jetty:jetty-webapp:9.4.33,10.0.0.beta3,11.0.0.beta3"}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2020-27216","vulnerabilityDetails":"In Eclipse Jetty versions 1.0 thru 9.4.32.v20200930, 10.0.0.alpha1 thru 10.0.0.beta2, and 11.0.0.alpha1 thru 11.0.0.beta2O, on Unix like systems, the system\u0027s temporary directory is shared between all users on that system. A collocated user can observe the process of creating a temporary sub directory in the shared temporary directory and race to complete the creation of the temporary subdirectory. If the attacker wins the race then they will have read and write permission to the subdirectory used to unpack web applications, including their WEB-INF/lib jar files and JSP files. If any code is ever executed out of this temporary directory, this can lead to a local privilege escalation vulnerability.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-27216","cvss3Severity":"high","cvss3Score":"7.0","cvss3Metrics":{"A":"High","AC":"High","PR":"Low","S":"Unchanged","C":"High","UI":"None","AV":"Local","I":"High"},"extraData":{}}</REMEDIATE> --> | True | CVE-2020-27216 (High) detected in jetty-webapp-9.2.4.v20141103.jar - ## CVE-2020-27216 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>jetty-webapp-9.2.4.v20141103.jar</b></p></summary>
<p>Jetty web application support</p>
<p>Library home page: <a href="http://www.eclipse.org/jetty">http://www.eclipse.org/jetty</a></p>
<p>Path to dependency file: keycloak/adapters/oidc/spring-boot/pom.xml</p>
<p>Path to vulnerable library: canner/.m2/repository/org/eclipse/jetty/jetty-webapp/9.2.4.v20141103/jetty-webapp-9.2.4.v20141103.jar,canner/.m2/repository/org/eclipse/jetty/jetty-webapp/9.2.4.v20141103/jetty-webapp-9.2.4.v20141103.jar,canner/.m2/repository/org/eclipse/jetty/jetty-webapp/9.2.4.v20141103/jetty-webapp-9.2.4.v20141103.jar</p>
<p>
Dependency Hierarchy:
- :x: **jetty-webapp-9.2.4.v20141103.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/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
In Eclipse Jetty versions 1.0 thru 9.4.32.v20200930, 10.0.0.alpha1 thru 10.0.0.beta2, and 11.0.0.alpha1 thru 11.0.0.beta2O, on Unix like systems, the system's temporary directory is shared between all users on that system. A collocated user can observe the process of creating a temporary sub directory in the shared temporary directory and race to complete the creation of the temporary subdirectory. If the attacker wins the race then they will have read and write permission to the subdirectory used to unpack web applications, including their WEB-INF/lib jar files and JSP files. If any code is ever executed out of this temporary directory, this can lead to a local privilege escalation vulnerability.
<p>Publish Date: 2020-10-23
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-27216>CVE-2020-27216</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.0</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: High
- Privileges Required: Low
- 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://bugs.eclipse.org/bugs/show_bug.cgi?id=567921">https://bugs.eclipse.org/bugs/show_bug.cgi?id=567921</a></p>
<p>Release Date: 2020-10-20</p>
<p>Fix Resolution: org.eclipse.jetty:jetty-runner:9.4.33,10.0.0.beta3,11.0.0.beta3;org.eclipse.jetty:jetty-webapp:9.4.33,10.0.0.beta3,11.0.0.beta3</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":false,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"Java","groupId":"org.eclipse.jetty","packageName":"jetty-webapp","packageVersion":"9.2.4.v20141103","packageFilePaths":["/adapters/oidc/spring-boot/pom.xml","/adapters/oidc/spring-boot-adapter-core/pom.xml","/adapters/oidc/spring-boot2/pom.xml"],"isTransitiveDependency":false,"dependencyTree":"org.eclipse.jetty:jetty-webapp:9.2.4.v20141103","isMinimumFixVersionAvailable":true,"minimumFixVersion":"org.eclipse.jetty:jetty-runner:9.4.33,10.0.0.beta3,11.0.0.beta3;org.eclipse.jetty:jetty-webapp:9.4.33,10.0.0.beta3,11.0.0.beta3"}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2020-27216","vulnerabilityDetails":"In Eclipse Jetty versions 1.0 thru 9.4.32.v20200930, 10.0.0.alpha1 thru 10.0.0.beta2, and 11.0.0.alpha1 thru 11.0.0.beta2O, on Unix like systems, the system\u0027s temporary directory is shared between all users on that system. A collocated user can observe the process of creating a temporary sub directory in the shared temporary directory and race to complete the creation of the temporary subdirectory. If the attacker wins the race then they will have read and write permission to the subdirectory used to unpack web applications, including their WEB-INF/lib jar files and JSP files. If any code is ever executed out of this temporary directory, this can lead to a local privilege escalation vulnerability.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-27216","cvss3Severity":"high","cvss3Score":"7.0","cvss3Metrics":{"A":"High","AC":"High","PR":"Low","S":"Unchanged","C":"High","UI":"None","AV":"Local","I":"High"},"extraData":{}}</REMEDIATE> --> | non_priority | cve high detected in jetty webapp jar cve high severity vulnerability vulnerable library jetty webapp jar jetty web application support library home page a href path to dependency file keycloak adapters oidc spring boot pom xml path to vulnerable library canner repository org eclipse jetty jetty webapp jetty webapp jar canner repository org eclipse jetty jetty webapp jetty webapp jar canner repository org eclipse jetty jetty webapp jetty webapp jar dependency hierarchy x jetty webapp jar vulnerable library found in base branch master vulnerability details in eclipse jetty versions thru thru and thru on unix like systems the system s temporary directory is shared between all users on that system a collocated user can observe the process of creating a temporary sub directory in the shared temporary directory and race to complete the creation of the temporary subdirectory if the attacker wins the race then they will have read and write permission to the subdirectory used to unpack web applications including their web inf lib jar files and jsp files if any code is ever executed out of this temporary directory this can lead to a local privilege escalation vulnerability publish date url a href cvss score details base score metrics exploitability metrics attack vector local attack complexity high privileges required low 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 org eclipse jetty jetty runner org eclipse jetty jetty webapp isopenpronvulnerability false ispackagebased true isdefaultbranch true packages istransitivedependency false dependencytree org eclipse jetty jetty webapp isminimumfixversionavailable true minimumfixversion org eclipse jetty jetty runner org eclipse jetty jetty webapp basebranches vulnerabilityidentifier cve vulnerabilitydetails in eclipse jetty versions thru thru and thru on unix like systems the system temporary directory is shared between all users on that system a collocated user can observe the process of creating a temporary sub directory in the shared temporary directory and race to complete the creation of the temporary subdirectory if the attacker wins the race then they will have read and write permission to the subdirectory used to unpack web applications including their web inf lib jar files and jsp files if any code is ever executed out of this temporary directory this can lead to a local privilege escalation vulnerability vulnerabilityurl | 0 |
10,619 | 3,411,124,224 | IssuesEvent | 2015-12-04 23:48:12 | boostorg/hana | https://api.github.com/repos/boostorg/hana | closed | Poor documentation formatting on Android 5.1 Chrome | documentation | The reference documentation has some odd properties when viewed on my Nexus 5 (Android 5.1.1 Chrome). When entering the "Methods" section of any concept's documentation page the font size gets much bigger and the text no longer wraps to the browser witdth. You can see a similar effect on the emulated Nexus 7 here:
http://mobt.me/BwmI
except there the font is getting smaller rather than larger (which looks less odd). I presume that the two font sizes are being chosen differently - one by pixel size and one by physical size.
I guess this is probably a Doxygen bug, not hana's fault, but I felt I ought to mention it (perhaps you could pass along the bug report to the Doxygen folks as appropriate). | 1.0 | Poor documentation formatting on Android 5.1 Chrome - The reference documentation has some odd properties when viewed on my Nexus 5 (Android 5.1.1 Chrome). When entering the "Methods" section of any concept's documentation page the font size gets much bigger and the text no longer wraps to the browser witdth. You can see a similar effect on the emulated Nexus 7 here:
http://mobt.me/BwmI
except there the font is getting smaller rather than larger (which looks less odd). I presume that the two font sizes are being chosen differently - one by pixel size and one by physical size.
I guess this is probably a Doxygen bug, not hana's fault, but I felt I ought to mention it (perhaps you could pass along the bug report to the Doxygen folks as appropriate). | non_priority | poor documentation formatting on android chrome the reference documentation has some odd properties when viewed on my nexus android chrome when entering the methods section of any concept s documentation page the font size gets much bigger and the text no longer wraps to the browser witdth you can see a similar effect on the emulated nexus here except there the font is getting smaller rather than larger which looks less odd i presume that the two font sizes are being chosen differently one by pixel size and one by physical size i guess this is probably a doxygen bug not hana s fault but i felt i ought to mention it perhaps you could pass along the bug report to the doxygen folks as appropriate | 0 |
186,167 | 14,394,659,319 | IssuesEvent | 2020-12-03 01:49:18 | github-vet/rangeclosure-findings | https://api.github.com/repos/github-vet/rangeclosure-findings | closed | GlobalCyberAlliance/GCAMcScrapy: vendor/golang.org/x/net/dns/dnsmessage/message_test.go; 14 LoC | fresh small test vendored |
Found a possible issue in [GlobalCyberAlliance/GCAMcScrapy](https://www.github.com/GlobalCyberAlliance/GCAMcScrapy) at [vendor/golang.org/x/net/dns/dnsmessage/message_test.go](https://github.com/GlobalCyberAlliance/GCAMcScrapy/blob/fd920b8153208cb8d0d56d5e8d018a65e9824c0b/vendor/golang.org/x/net/dns/dnsmessage/message_test.go#L236-L249)
Below is the message reported by the analyzer for this snippet of code. Beware that the analyzer only reports the first
issue it finds, so please do not limit your consideration to the contents of the below message.
> function call which takes a reference to want at line 247 may start a goroutine
[Click here to see the code in its original context.](https://github.com/GlobalCyberAlliance/GCAMcScrapy/blob/fd920b8153208cb8d0d56d5e8d018a65e9824c0b/vendor/golang.org/x/net/dns/dnsmessage/message_test.go#L236-L249)
<details>
<summary>Click here to show the 14 line(s) of Go which triggered the analyzer.</summary>
```go
for i, want := range wants {
b, err := want.Pack()
if err != nil {
t.Fatalf("%d: packing failed: %v", i, err)
}
var got Message
err = got.Unpack(b)
if err != nil {
t.Fatalf("%d: unpacking failed: %v", i, err)
}
if !reflect.DeepEqual(got, want) {
t.Errorf("%d: got = %+v, want = %+v", i, &got, &want)
}
}
```
</details>
Leave a reaction on this issue to contribute to the project by classifying this instance as a **Bug** :-1:, **Mitigated** :+1:, or **Desirable Behavior** :rocket:
See the descriptions of the classifications [here](https://github.com/github-vet/rangeclosure-findings#how-can-i-help) for more information.
commit ID: fd920b8153208cb8d0d56d5e8d018a65e9824c0b
| 1.0 | GlobalCyberAlliance/GCAMcScrapy: vendor/golang.org/x/net/dns/dnsmessage/message_test.go; 14 LoC -
Found a possible issue in [GlobalCyberAlliance/GCAMcScrapy](https://www.github.com/GlobalCyberAlliance/GCAMcScrapy) at [vendor/golang.org/x/net/dns/dnsmessage/message_test.go](https://github.com/GlobalCyberAlliance/GCAMcScrapy/blob/fd920b8153208cb8d0d56d5e8d018a65e9824c0b/vendor/golang.org/x/net/dns/dnsmessage/message_test.go#L236-L249)
Below is the message reported by the analyzer for this snippet of code. Beware that the analyzer only reports the first
issue it finds, so please do not limit your consideration to the contents of the below message.
> function call which takes a reference to want at line 247 may start a goroutine
[Click here to see the code in its original context.](https://github.com/GlobalCyberAlliance/GCAMcScrapy/blob/fd920b8153208cb8d0d56d5e8d018a65e9824c0b/vendor/golang.org/x/net/dns/dnsmessage/message_test.go#L236-L249)
<details>
<summary>Click here to show the 14 line(s) of Go which triggered the analyzer.</summary>
```go
for i, want := range wants {
b, err := want.Pack()
if err != nil {
t.Fatalf("%d: packing failed: %v", i, err)
}
var got Message
err = got.Unpack(b)
if err != nil {
t.Fatalf("%d: unpacking failed: %v", i, err)
}
if !reflect.DeepEqual(got, want) {
t.Errorf("%d: got = %+v, want = %+v", i, &got, &want)
}
}
```
</details>
Leave a reaction on this issue to contribute to the project by classifying this instance as a **Bug** :-1:, **Mitigated** :+1:, or **Desirable Behavior** :rocket:
See the descriptions of the classifications [here](https://github.com/github-vet/rangeclosure-findings#how-can-i-help) for more information.
commit ID: fd920b8153208cb8d0d56d5e8d018a65e9824c0b
| non_priority | globalcyberalliance gcamcscrapy vendor golang org x net dns dnsmessage message test go loc found a possible issue in at below is the message reported by the analyzer for this snippet of code beware that the analyzer only reports the first issue it finds so please do not limit your consideration to the contents of the below message function call which takes a reference to want at line may start a goroutine click here to show the line s of go which triggered the analyzer go for i want range wants b err want pack if err nil t fatalf d packing failed v i err var got message err got unpack b if err nil t fatalf d unpacking failed v i err if reflect deepequal got want t errorf d got v want v i got want leave a reaction on this issue to contribute to the project by classifying this instance as a bug mitigated or desirable behavior rocket see the descriptions of the classifications for more information commit id | 0 |
269,728 | 28,960,259,537 | IssuesEvent | 2023-05-10 01:27:34 | praneethpanasala/linux | https://api.github.com/repos/praneethpanasala/linux | reopened | CVE-2023-0179 (High) detected in linuxlinux-4.19.6 | Mend: dependency security vulnerability | ## CVE-2023-0179 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>linuxlinux-4.19.6</b></p></summary>
<p>
<p>Apache Software Foundation (ASF)</p>
<p>Library home page: <a href=https://mirrors.edge.kernel.org/pub/linux/kernel/v4.x/?wsslib=linux>https://mirrors.edge.kernel.org/pub/linux/kernel/v4.x/?wsslib=linux</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>/net/netfilter/nft_payload.c</b>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/net/netfilter/nft_payload.c</b>
</p>
</details>
<p></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 buffer overflow vulnerability was found in the Netfilter subsystem in the Linux Kernel. This issue could allow the leakage of both stack and heap addresses, and potentially allow Local Privilege Escalation to the root user via arbitrary code execution.
<p>Publish Date: 2023-03-27
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2023-0179>CVE-2023-0179</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.8</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: 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://www.linuxkernelcves.com/cves/CVE-2023-0179">https://www.linuxkernelcves.com/cves/CVE-2023-0179</a></p>
<p>Release Date: 2023-01-11</p>
<p>Fix Resolution: v5.10.164,v5.15.89,v6.1.7</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-2023-0179 (High) detected in linuxlinux-4.19.6 - ## CVE-2023-0179 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>linuxlinux-4.19.6</b></p></summary>
<p>
<p>Apache Software Foundation (ASF)</p>
<p>Library home page: <a href=https://mirrors.edge.kernel.org/pub/linux/kernel/v4.x/?wsslib=linux>https://mirrors.edge.kernel.org/pub/linux/kernel/v4.x/?wsslib=linux</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>/net/netfilter/nft_payload.c</b>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/net/netfilter/nft_payload.c</b>
</p>
</details>
<p></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 buffer overflow vulnerability was found in the Netfilter subsystem in the Linux Kernel. This issue could allow the leakage of both stack and heap addresses, and potentially allow Local Privilege Escalation to the root user via arbitrary code execution.
<p>Publish Date: 2023-03-27
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2023-0179>CVE-2023-0179</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.8</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: 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://www.linuxkernelcves.com/cves/CVE-2023-0179">https://www.linuxkernelcves.com/cves/CVE-2023-0179</a></p>
<p>Release Date: 2023-01-11</p>
<p>Fix Resolution: v5.10.164,v5.15.89,v6.1.7</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 linuxlinux cve high severity vulnerability vulnerable library linuxlinux apache software foundation asf library home page a href found in head commit a href found in base branch master vulnerable source files net netfilter nft payload c net netfilter nft payload c vulnerability details a buffer overflow vulnerability was found in the netfilter subsystem in the linux kernel this issue could allow the leakage of both stack and heap addresses and potentially allow local privilege escalation to the root user via arbitrary code execution 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 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 step up your open source security game with mend | 0 |
72,786 | 13,919,616,677 | IssuesEvent | 2020-10-21 09:19:04 | spotify/backstage | https://api.github.com/repos/spotify/backstage | opened | Merge already existing mkdocs.yaml config with techdocs-core config instead of override | docs-like-code enhancement | Currently, the techdocs-core plugin overrides the config and set the new config instead of taking the already existing configuration (in mkdocs.yml) and merge the two ones together.
This means if, for example I want to add toc_depth as configuration to my table of contents, I could add this to my mkdocs.yml file but it will be overridden by the configs set in the techdocs-core plugin.
## Feature Suggestion
Merge the already existing config in the mkdocs.yml file with the config set in the techdocs-core plugin.
| 1.0 | Merge already existing mkdocs.yaml config with techdocs-core config instead of override - Currently, the techdocs-core plugin overrides the config and set the new config instead of taking the already existing configuration (in mkdocs.yml) and merge the two ones together.
This means if, for example I want to add toc_depth as configuration to my table of contents, I could add this to my mkdocs.yml file but it will be overridden by the configs set in the techdocs-core plugin.
## Feature Suggestion
Merge the already existing config in the mkdocs.yml file with the config set in the techdocs-core plugin.
| non_priority | merge already existing mkdocs yaml config with techdocs core config instead of override currently the techdocs core plugin overrides the config and set the new config instead of taking the already existing configuration in mkdocs yml and merge the two ones together this means if for example i want to add toc depth as configuration to my table of contents i could add this to my mkdocs yml file but it will be overridden by the configs set in the techdocs core plugin feature suggestion merge the already existing config in the mkdocs yml file with the config set in the techdocs core plugin | 0 |
158,320 | 20,024,178,949 | IssuesEvent | 2022-02-01 19:23:09 | gms-ws-sandbox/Java-Demo | https://api.github.com/repos/gms-ws-sandbox/Java-Demo | opened | CVE-2021-41184 (Medium) detected in jquery-ui-1.8.19.min.js, jquery-ui-1.11.4.min.js | security vulnerability | ## CVE-2021-41184 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>jquery-ui-1.8.19.min.js</b>, <b>jquery-ui-1.11.4.min.js</b></p></summary>
<p>
<details><summary><b>jquery-ui-1.8.19.min.js</b></p></summary>
<p>A curated set of user interface interactions, effects, widgets, and themes built on top of the jQuery JavaScript Library.</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/jqueryui/1.8.19/jquery-ui.min.js">https://cdnjs.cloudflare.com/ajax/libs/jqueryui/1.8.19/jquery-ui.min.js</a></p>
<p>Path to dependency file: /src/main/webapp/index.jsp</p>
<p>Path to vulnerable library: /Java-Demo/src/main/webapp/js/jqueryUI.js,/Java-Demo/src/main/webapp/js/jqueryUI.js</p>
<p>
Dependency Hierarchy:
- :x: **jquery-ui-1.8.19.min.js** (Vulnerable Library)
</details>
<details><summary><b>jquery-ui-1.11.4.min.js</b></p></summary>
<p>A curated set of user interface interactions, effects, widgets, and themes built on top of the jQuery JavaScript Library.</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/jqueryui/1.11.4/jquery-ui.min.js">https://cdnjs.cloudflare.com/ajax/libs/jqueryui/1.11.4/jquery-ui.min.js</a></p>
<p>Path to vulnerable library: /Java-Demo/src/main/webapp/js/jquery-ui.min.js</p>
<p>
Dependency Hierarchy:
- :x: **jquery-ui-1.11.4.min.js** (Vulnerable Library)
</details>
<p>Found in base branch: <b>dev</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>
jQuery-UI is the official jQuery user interface library. Prior to version 1.13.0, accepting the value of the `of` option of the `.position()` util from untrusted sources may execute untrusted code. The issue is fixed in jQuery UI 1.13.0. Any string value passed to the `of` option is now treated as a CSS selector. A workaround is to not accept the value of the `of` option from untrusted sources.
<p>Publish Date: 2021-10-26
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-41184>CVE-2021-41184</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.1</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: Low
- 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://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-41184">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-41184</a></p>
<p>Release Date: 2021-10-26</p>
<p>Fix Resolution: jquery-ui - 1.13.0</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"JavaScript","packageName":"jqueryui","packageVersion":"1.8.19","packageFilePaths":["/src/main/webapp/index.jsp"],"isTransitiveDependency":false,"dependencyTree":"jqueryui:1.8.19","isMinimumFixVersionAvailable":true,"minimumFixVersion":"jquery-ui - 1.13.0","isBinary":false},{"packageType":"JavaScript","packageName":"jqueryui","packageVersion":"1.11.4","packageFilePaths":[null],"isTransitiveDependency":false,"dependencyTree":"jqueryui:1.11.4","isMinimumFixVersionAvailable":true,"minimumFixVersion":"jquery-ui - 1.13.0","isBinary":false}],"baseBranches":["dev"],"vulnerabilityIdentifier":"CVE-2021-41184","vulnerabilityDetails":"jQuery-UI is the official jQuery user interface library. Prior to version 1.13.0, accepting the value of the `of` option of the `.position()` util from untrusted sources may execute untrusted code. The issue is fixed in jQuery UI 1.13.0. Any string value passed to the `of` option is now treated as a CSS selector. A workaround is to not accept the value of the `of` option from untrusted sources.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-41184","cvss3Severity":"medium","cvss3Score":"6.1","cvss3Metrics":{"A":"None","AC":"Low","PR":"None","S":"Changed","C":"Low","UI":"Required","AV":"Network","I":"Low"},"extraData":{}}</REMEDIATE> --> | True | CVE-2021-41184 (Medium) detected in jquery-ui-1.8.19.min.js, jquery-ui-1.11.4.min.js - ## CVE-2021-41184 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>jquery-ui-1.8.19.min.js</b>, <b>jquery-ui-1.11.4.min.js</b></p></summary>
<p>
<details><summary><b>jquery-ui-1.8.19.min.js</b></p></summary>
<p>A curated set of user interface interactions, effects, widgets, and themes built on top of the jQuery JavaScript Library.</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/jqueryui/1.8.19/jquery-ui.min.js">https://cdnjs.cloudflare.com/ajax/libs/jqueryui/1.8.19/jquery-ui.min.js</a></p>
<p>Path to dependency file: /src/main/webapp/index.jsp</p>
<p>Path to vulnerable library: /Java-Demo/src/main/webapp/js/jqueryUI.js,/Java-Demo/src/main/webapp/js/jqueryUI.js</p>
<p>
Dependency Hierarchy:
- :x: **jquery-ui-1.8.19.min.js** (Vulnerable Library)
</details>
<details><summary><b>jquery-ui-1.11.4.min.js</b></p></summary>
<p>A curated set of user interface interactions, effects, widgets, and themes built on top of the jQuery JavaScript Library.</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/jqueryui/1.11.4/jquery-ui.min.js">https://cdnjs.cloudflare.com/ajax/libs/jqueryui/1.11.4/jquery-ui.min.js</a></p>
<p>Path to vulnerable library: /Java-Demo/src/main/webapp/js/jquery-ui.min.js</p>
<p>
Dependency Hierarchy:
- :x: **jquery-ui-1.11.4.min.js** (Vulnerable Library)
</details>
<p>Found in base branch: <b>dev</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>
jQuery-UI is the official jQuery user interface library. Prior to version 1.13.0, accepting the value of the `of` option of the `.position()` util from untrusted sources may execute untrusted code. The issue is fixed in jQuery UI 1.13.0. Any string value passed to the `of` option is now treated as a CSS selector. A workaround is to not accept the value of the `of` option from untrusted sources.
<p>Publish Date: 2021-10-26
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-41184>CVE-2021-41184</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.1</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: Low
- 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://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-41184">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-41184</a></p>
<p>Release Date: 2021-10-26</p>
<p>Fix Resolution: jquery-ui - 1.13.0</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"JavaScript","packageName":"jqueryui","packageVersion":"1.8.19","packageFilePaths":["/src/main/webapp/index.jsp"],"isTransitiveDependency":false,"dependencyTree":"jqueryui:1.8.19","isMinimumFixVersionAvailable":true,"minimumFixVersion":"jquery-ui - 1.13.0","isBinary":false},{"packageType":"JavaScript","packageName":"jqueryui","packageVersion":"1.11.4","packageFilePaths":[null],"isTransitiveDependency":false,"dependencyTree":"jqueryui:1.11.4","isMinimumFixVersionAvailable":true,"minimumFixVersion":"jquery-ui - 1.13.0","isBinary":false}],"baseBranches":["dev"],"vulnerabilityIdentifier":"CVE-2021-41184","vulnerabilityDetails":"jQuery-UI is the official jQuery user interface library. Prior to version 1.13.0, accepting the value of the `of` option of the `.position()` util from untrusted sources may execute untrusted code. The issue is fixed in jQuery UI 1.13.0. Any string value passed to the `of` option is now treated as a CSS selector. A workaround is to not accept the value of the `of` option from untrusted sources.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-41184","cvss3Severity":"medium","cvss3Score":"6.1","cvss3Metrics":{"A":"None","AC":"Low","PR":"None","S":"Changed","C":"Low","UI":"Required","AV":"Network","I":"Low"},"extraData":{}}</REMEDIATE> --> | non_priority | cve medium detected in jquery ui min js jquery ui min js cve medium severity vulnerability vulnerable libraries jquery ui min js jquery ui min js jquery ui min js a curated set of user interface interactions effects widgets and themes built on top of the jquery javascript library library home page a href path to dependency file src main webapp index jsp path to vulnerable library java demo src main webapp js jqueryui js java demo src main webapp js jqueryui js dependency hierarchy x jquery ui min js vulnerable library jquery ui min js a curated set of user interface interactions effects widgets and themes built on top of the jquery javascript library library home page a href path to vulnerable library java demo src main webapp js jquery ui min js dependency hierarchy x jquery ui min js vulnerable library found in base branch dev vulnerability details jquery ui is the official jquery user interface library prior to version accepting the value of the of option of the position util from untrusted sources may execute untrusted code the issue is fixed in jquery ui any string value passed to the of option is now treated as a css selector a workaround is to not accept the value of the of option from untrusted sources publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction required scope changed impact metrics confidentiality impact low integrity impact low availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution jquery ui isopenpronvulnerability true ispackagebased true isdefaultbranch true packages istransitivedependency false dependencytree jqueryui isminimumfixversionavailable true minimumfixversion jquery ui isbinary false packagetype javascript packagename jqueryui packageversion packagefilepaths istransitivedependency false dependencytree jqueryui isminimumfixversionavailable true minimumfixversion jquery ui isbinary false basebranches vulnerabilityidentifier cve vulnerabilitydetails jquery ui is the official jquery user interface library prior to version accepting the value of the of option of the position util from untrusted sources may execute untrusted code the issue is fixed in jquery ui any string value passed to the of option is now treated as a css selector a workaround is to not accept the value of the of option from untrusted sources vulnerabilityurl | 0 |
176,160 | 13,629,545,372 | IssuesEvent | 2020-09-24 15:15:12 | celo-org/celo-monorepo | https://api.github.com/repos/celo-org/celo-monorepo | closed | [FLAKEY TEST] end-to-end-mobile-test-ios -> mobile -> New Account -> CELO -> Go to CELO screen and through education flow | FLAKEY end-to-end-mobile-test-ios end-to-end-mobile-test-ios mobile | Discovered at commit 4a3b0db23679146204b76e4e98ff3b703296ab49
Attempt No. 1:
Error: Test Failed: View “<RCTView: 0x7f96f5ffae60>” is not hittable at point “{"x":60,"y":24}”; Another view “<RCTView: 0x7f96f5e8a710>” is hittable at window point “{"x":207,"y":814}”
View Hierarchy:
<UIWindow: 0x7f96f5d17ff0; frame = (0 0; 414 896); autoresize = W+H; gestureRecognizers = <NSArray: 0x600002210f30>; layer = <UIWindowLayer: 0x600002c6d240>>
| <UITransitionView: 0x7f96f5f72540; frame = (0 0; 414 896); autoresize = W+H; layer = <CALayer: 0x600002c7afa0>>
| | <UIDropShadowView: 0x7f96f5f733a0; frame = (0 0; 414 896); clipsToBounds = YES; autoresize = W+H; layer = <CALayer: 0x600002c7bd60>>
| | | <RCTRootView: 0x7f96f5f7d1b0; frame = (0 0; 414 896); autoresize = W+H; layer = <CALayer: 0x600002c58880>>
| | | | <RCTRootContentView: 0x7f96f5f779f0; reactTag: 1; frame = (0 0; 414 896); gestureRecognizers = <NSArray: 0x600002216220>; layer = <CALayer: 0x600002c58920>>
| | | | | <RCTView: 0x7f96f5f69e90; reactTag: 7; frame = (0 0; 414 896); layer = <CALayer: 0x600002c29000>>
| | | | | | <RCTView: 0x7f96f5c35e40; reactTag: 5; frame = (0 0; 414 896); layer = <CALayer: 0x600002cd21a0>>
| | | | | | | <RNCSafeAreaProvider: 0x7f96f5c72d70; reactTag: 3; frame = (0 0; 414 896); layer = <CALayer: 0x600002cd2080>>
| | | | | | | | <RCTView: 0x7f96f5d34d50; reactTag: 55; frame = (0 0; 414 896); layer = <CALayer: 0x600002ce5700>>
| | | | | | | | | <RCTView: 0x7f96f5d34810; reactTag: 49; frame = (0 0; 414 896); layer = <CALayer: 0x600002ce5840>>
| | | | | | | | | | <RCTView: 0x7f96f5d342e0; reactTag: 47; frame = (0 0; 414 896); layer = <CALayer: 0x600002ce58c0>>
| | | | | | | | | | | <RCTView: 0x7f96f5d34040; reactTag: 45; frame = (0 0; 414 896); layer = <CALayer: 0x600002ce5880>>
| | | | | | | | | | | | <RCTView: 0x7f96f5d314f0; reactTag: 15; frame = (0 0; 414 0); layer = <CALayer: 0x600002cd6e40>>
| | | | | | | | | | | | <RCTView: 0x7f96f5d329f0; reactTag: 43; frame = (0 0; 414 896); layer = <CALayer: 0x600002ce53c0>>
| | | | | | | | | | | | | <RCTView: 0x7f96f5c876d0; reactTag: 19; frame = (0 0; 414 896); layer = <CALayer: 0x600002cd3c60>>
| | | | | | | | | | | | | | <RCTView: 0x7f96f5cd2b80; reactTag: 2539; frame = (0 0; 414 896); alpha = 0.3; userInteractionEnabled = NO; layer = <CALayer: 0x600002a1a8e0>>
| | | | | | | | | | | | | <RCTView: 0x7f96f5d33da0; reactTag: 39; frame = (0 0; 414 896); layer = <CALayer: 0x600002ce56a0>>
| | | | | | | | | | | | | | <RCTView: 0x7f96f5d33b00; reactTag: 37; frame = (0 0; 414 896); clipsToBounds = YES; gestureRecognizers = <NSArray: 0x6000022f3480>; layer = <CALayer: 0x600002ce5300>>
| | | | | | | | | | | | | | | <RCTView: 0x7f96f5d33860; reactTag: 35; frame = (0 0; 414 896); clipsToBounds = YES; layer = <CALayer: 0x600002ce59e0>>
| | | | | | | | | | | | | | | | <RCTView: 0x7f96f5d335c0; reactTag: 33; frame = (0 0; 414 896); layer = <CALayer: 0x600002ce59a0>>
| | | | | | | | | | | | | | | | | <RCTView: 0x7f96f5d32ed0; reactTag: 27; frame = (0 0; 414 896); layer = <CALayer: 0x600002ce5980>>
| | | | | | | | | | | | | | | | | | <RCTView: 0x7f96f5d3c2f0; reactTag: 209; frame = (0 0; 414 896); layer = <CALayer: 0x600002ce4940>>
| | | | | | | | | | | | | | | | | | | <RCTView: 0x7f96f5e602f0; reactTag: 159; frame = (0 0; 414 896); layer = <CALayer: 0x600002cd5280>>
| | | | | | | | | | | | | | | | | | | | <RCTView: 0x7f96f5ea4b00; reactTag: 1847; frame = (0 0; 414 896); layer = <CALayer: 0x600002c8a880>>
| | | | | | | | | | | | | | | | | | | | | <RCTView: 0x7f96f5d35b50; reactTag: 1365; frame = (0 0; 414 0); layer = <CALayer: 0x600002c9d800>>
| | | | | | | | | | | | | | | | | | | | | <RCTView: 0x7f96f5ea4860; reactTag: 1845; frame = (0 0; 414 896); layer = <CALayer: 0x600002c8ad80>>
| | | | | | | | | | | | | | | | | | | | | | <RCTView: 0x7f96f5fddb80; reactTag: 1843; frame = (0 0; 414 896); layer = <CALayer: 0x600002ca3700>>
| | | | | | | | | | | | | | | | | | | | | | | <RCTView: 0x7f96f5fdd8e0; reactTag: 1839; frame = (0 0; 414 896); gestureRecognizers = <NSArray: 0x6000023e6580>; layer = <CALayer: 0x600002ca2e60>>
| | | | | | | | | | | | | | | | | | | | | | | | <RCTView: 0x7f96f5d109d0; reactTag: 1367; frame = (0 0; 3 896); userInteractionEnabled = NO; layer = <CALayer: 0x600002c9ec60>>
| | | | | | | | | | | | | | | | | | | | | | | | <RCTView: 0x7f96f5fdd640; reactTag: 1837; frame = (0 0; 414 896); clipsToBounds = YES; layer = <CALayer: 0x600002ca2ec0>>
| | | | | | | | | | | | | | | | | | | | | | | | | <RCTView: 0x7f96f5fdd3a0; reactTag: 1835; frame = (0 0; 414 896); layer = <CALayer: 0x600002ca3220>>
| | | | | | | | | | | | | | | | | | | | | | | | | | <RCTView: 0x7f96f5fdd100; reactTag: 1833; frame = (0 0; 414 896); layer = <CALayer: 0x600002ca1160>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTView: 0x7f96f5fdce60; reactTag: 1829; frame = (0 0; 414 896); layer = <CALayer: 0x600002ca1380>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTView: 0x7f96f5fdcbc0; reactTag: 1827; frame = (0 0; 414 896); clipsToBounds = YES; gestureRecognizers = <NSArray: 0x6000023e6430>; layer = <CALayer: 0x600002ca11e0>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTView: 0x7f96f5ecc840; reactTag: 1577; frame = (0 0; 414 896); layer = <CALayer: 0x600002ceaf80>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTView: 0x7f96f5fd0600; reactTag: 1573; frame = (0 0; 414 896); layer = <CALayer: 0x600002ca1360>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RNSScreenContainerView: 0x7f96f5f8b900; frame = (0 0; 414 896); layer = <CALayer: 0x600002ca1060>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <UIView: 0x7f96f5f999c0; frame = (0 0; 414 896); autoresize = W+H; layer = <CALayer: 0x600002ca1340>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RNSScreenView: 0x7f96f5ccb3f0; reactTag: 3313; frame = (0 0; 414 896); layer = <CALayer: 0x600002a44b80>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RNCSafeAreaView: 0x7f96f5ff7dd0; reactTag: 3309; frame = (0 0; 414 896); layer = <CALayer: 0x600002a56980>; RNCSafeAreaInsets = {44, 0, 34, 0}; appliedRNCSafeAreaInsets = {44, 0, 34, 0}>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTView: 0x7f96f8710bd0; reactTag: 3193; frame = (0 44; 414 56); layer = <CALayer: 0x600002a56d80>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTView: 0x7f96f5fb3170; reactTag: 3189; frame = (16 12; 32 32); layer = <CALayer: 0x600002a57400>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RNSVGSvgView: 0x7f96f5fb6d20; frame = (0 0; 32 32); layer = <CALayer: 0x600002a546a0>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RNSVGGroup: 0x7f96f7925600; frame = (6 8.5; 20 14.5); opaque = NO; userInteractionEnabled = NO; layer = <CALayer: 0x600002a56c20>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RNSVGLine: 0x7f96f7922400; frame = (6 8.5; 20 2.5); opaque = NO; userInteractionEnabled = NO; layer = <CALayer: 0x600002a544e0>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RNSVGLine: 0x7f96f78a1200; frame = (6 14.5; 20 2.5); opaque = NO; userInteractionEnabled = NO; layer = <CALayer: 0x600002a574c0>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RNSVGLine: 0x7f96f78be000; frame = (6 20.5; 20 2.5); opaque = NO; userInteractionEnabled = NO; layer = <CALayer: 0x600002a543c0>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTView: 0x7f96f5ff7b30; reactTag: 3307; frame = (0 100; 414 762); layer = <CALayer: 0x600002a545c0>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTView: 0x7f96f5ffabc0; reactTag: 3293; frame = (0 0; 414 690); layer = <CALayer: 0x600002a579a0>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTScrollView: 0x7f96f5f956d0; reactTag: 3277; frame = (0 0; 414 690); clipsToBounds = YES; layer = <CALayer: 0x600002a57d40>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTCustomScrollView: 0x7f96f78bee00; baseClass = UIScrollView; frame = (0 0; 414 690); clipsToBounds = YES; autoresize = W+H; gestureRecognizers = <NSArray: 0x6000023e6100>; layer = <CALayer: 0x600002a57500>; contentOffset: {0, 0}; contentSize: {1656, 690}; adjustedContentInset: {0, 0, 0, 0}>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTScrollContentView: 0x7f96f5fd9300; reactTag: 3275; frame = (0 0; 1656 690); layer = <CALayer: 0x600002a56480>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTView: 0x7f96f8706ec0; reactTag: 3213; frame = (0 0; 414 690); layer = <CALayer: 0x600002a56500>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTView: 0x7f96f873b2b0; reactTag: 3209; frame = (0 0; 414 666); layer = <CALayer: 0x600002a54c80>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTView: 0x7f96f5fda300; reactTag: 3207; frame = (24 0; 366 666); layer = <CALayer: 0x600002a55d40>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTImageView: 0x7f96f5f6ef30; reactTag: 3195; frame = (63 187; 240 180); clipsToBounds = YES; layer = <CALayer: 0x600002a55d00>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTUIImageViewAnimated: 0x7f96f5fc8750; baseClass = UIImageView; frame = (0 0; 240 180); opaque = NO; autoresize = W+H; userInteractionEnabled = NO; layer = <CALayer: 0x600002a55880>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTTextView: 0x7f96f5fed130; reactTag: 3199; text: What is CELO? frame = (0 390.5; 366 28.5); text = 'What is CELO?'; opaque = NO; layer = <CALayer: 0x600002a565e0>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTTextView: 0x7f96f5fd8d20; reactTag: 3205; text: CELO helps keep the Celo Network running and the Celo Dollar stable. frame = (0 419; 366 60.5); text = 'CELO helps keep the Celo ...'; opaque = NO; layer = <CALayer: 0x600002a566c0>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTView: 0x7f96f8742650; reactTag: 3233; frame = (414 0; 414 690); layer = <CALayer: 0x600002a55b40>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTView: 0x7f96f8742f40; reactTag: 3229; frame = (0 0; 414 666); layer = <CALayer: 0x600002a54440>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTView: 0x7f96f8732b70; reactTag: 3227; frame = (24 0; 366 666); layer = <CALayer: 0x600002a54540>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTImageView: 0x7f96f5fc3d20; reactTag: 3215; frame = (63 176; 240 180); clipsToBounds = YES; layer = <CALayer: 0x600002a55a00>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTUIImageViewAnimated: 0x7f96f87474d0; baseClass = UIImageView; frame = (0 0; 240 180); opaque = NO; autoresize = W+H; userInteractionEnabled = NO; layer = <CALayer: 0x600002a56d00>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTTextView: 0x7f96f5fc4980; reactTag: 3219; text: CELO’s price changes frame = (0 379.5; 366 28.5); text = 'CELO’s price changes'; opaque = NO; layer = <CALayer: 0x600002a56940>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTTextView: 0x7f96f5f950e0; reactTag: 3225; text: Unlike Celo Dollars, the value of CELO changes. If more people use Celo Dollar, the value of CELO increases. frame = (0 408; 366 82.5); text = 'Unlike Celo Dollars, the ...'; opaque = NO; layer = <CALayer: 0x600002a573e0>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTView: 0x7f96f5f93330; reactTag: 3253; frame = (828 0; 414 690); layer = <CALayer: 0x600002a57a20>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTView: 0x7f96f5f94cc0; reactTag: 3249; frame = (0 0; 414 666); layer = <CALayer: 0x600002a56cc0>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTView: 0x7f96f8736200; reactTag: 3247; frame = (24 0; 366 666); layer = <CALayer: 0x600002a56b40>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTImageView: 0x7f96f5ed8cd0; reactTag: 3235; frame = (63 176; 240 180); clipsToBounds = YES; layer = <CALayer: 0x600002a42c80>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTUIImageViewAnimated: 0x7f96f90005e0; baseClass = UIImageView; frame = (0 0; 240 180); opaque = NO; autoresize = W+H; userInteractionEnabled = NO; layer = <CALayer: 0x600002a43ec0>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTTextView: 0x7f96f5e11570; reactTag: 3239; text: Shape the Celo Network frame = (0 379.5; 366 28.5); text = 'Shape the Celo Network'; opaque = NO; layer = <CALayer: 0x600002a407e0>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTTextView: 0x7f96f5fdba80; reactTag: 3245; text: By holding CELO, you have the ability to vote for changes and features you’d like to see on the Celo Network. frame = (0 408; 366 82.5); text = 'By holding CELO, you have...'; opaque = NO; layer = <CALayer: 0x600002a57c60>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTView: 0x7f96f8713910; reactTag: 3273; frame = (1242 0; 414 690); layer = <CALayer: 0x600002a55620>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTView: 0x7f96f5f6f400; reactTag: 3269; frame = (0 0; 414 666); layer = <CALayer: 0x600002a564e0>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTView: 0x7f96f873c4c0; reactTag: 3267; frame = (24 0; 366 666); layer = <CALayer: 0x600002a56740>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTImageView: 0x7f96f5fbd2a0; reactTag: 3255; frame = (63 176; 240 180); clipsToBounds = YES; layer = <CALayer: 0x600002a57420>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTUIImageViewAnimated: 0x7f96f5fdf8e0; baseClass = UIImageView; frame = (0 0; 240 180); opaque = NO; autoresize = W+H; userInteractionEnabled = NO; layer = <CALayer: 0x600002a54600>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTTextView: 0x7f96f5f98e80; reactTag: 3259; text: Please buy and sell responsibly frame = (0 379.5; 366 28.5); text = 'Please buy and sell respo...'; opaque = NO; layer = <CALayer: 0x600002a55220>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTTextView: 0x7f96f5fbab40; reactTag: 3265; text: Celo Wallet allows you to buy and sell CELO. CELO presents a risk of financial loss, please exercise caution. frame = (0 408; 366 82.5); text = 'Celo Wallet allows you to...'; opaque = NO; layer = <CALayer: 0x600002a56fe0>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTView: 0x7f96f5ffa920; reactTag: 3289; frame = (0 654; 414 11); userInteractionEnabled = NO; layer = <CALayer: 0x600002a55780>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTView: 0x7f96f5fec370; reactTag: 3279; frame = (188 3; 5 5); layer = <CALayer: 0x600002a549e0>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTView: 0x7f96f5f95a90; reactTag: 3283; frame = (199 3; 5 5); layer = <CALayer: 0x600002a560c0>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTView: 0x7f96f5fe1270; reactTag: 3285; frame = (210 3; 5 5); layer = <CALayer: 0x600002a54ae0>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTView: 0x7f96f5fe1510; reactTag: 3287; frame = (221 3; 5 5); layer = <CALayer: 0x600002a55f80>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTView: 0x7f96f5ff7890; reactTag: 3305; frame = (147 690; 120 48); layer = <CALayer: 0x600002a55920>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTView: 0x7f96f5ff75f0; reactTag: 3303; frame = (0 0; 120 48); clipsToBounds = YES; layer = <CALayer: 0x600002a550a0>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTView: 0x7f96f5ffae60; reactTag: 3299; frame = (0 0; 120 48); layer = <CALayer: 0x600002a56220>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTTextView: 0x7f96f5fe17b0; reactTag: 3297; text: Next frame = (41.5 12.5; 37 23); text = 'Next'; opaque = NO; layer = <CALayer: 0x600002a54e40>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTView: 0x7f96f5e8a710; reactTag: 1575; frame = (0 0; 414 896); alpha = 0.0107927; gestureRecognizers = <NSArray: 0x6000023e62e0>; layer = <CALayer: 0x600002ceb3e0>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTView: 0x7f96f5fdc920; reactTag: 1825; frame = (-263.129 0; 280 896); transform = [1, 0, 0, 1, 16.870845794677734, 0]; layer = <CALayer: 0x600002ca11a0>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTScrollView: 0x7f96f5fdbef0; reactTag: 1823; frame = (0 0; 280 896); clipsToBounds = YES; layer = <CALayer: 0x600002ca0fe0>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTCustomScrollView: 0x7f96f78ffa00; baseClass = UIScrollView; frame = (0 0; 280 896); clipsToBounds = YES; autoresize = W+H; gestureRecognizers = <NSArray: 0x6000022f1e30>; layer = <CALayer: 0x600002ca1000>; contentOffset: {0, 0}; contentSize: {280, 788}; adjustedContentInset: {0, 0, 0, 0}>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTScrollContentView: 0x7f96f5fdbc50; reactTag: 1819; frame = (0 0; 280 788); layer = <CALayer: 0x600002ca1020>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTView: 0x7f96f5fee670; reactTag: 1629; frame = (16 64; 248 214); layer = <CALayer: 0x600002ca1120>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTView: 0x7f96f5e893d0; reactTag: 1585; frame = (0 0; 64 64); layer = <CALayer: 0x600002cebe80>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTView: 0x7f96f5e98ad0; reactTag: 1583; frame = (0 0; 64 64); layer = <CALayer: 0x600002cebdc0>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTImageView: 0x7f96f5ef0740; reactTag: 1579; frame = (0 0; 64 64); clipsToBounds = YES; layer = <CALayer: 0x600002ceb560>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTUIImageViewAnimated: 0x7f96f5e16b90; baseClass = UIImageView; frame = (0 0; 64 64); opaque = NO; autoresize = W+H; userInteractionEnabled = NO; layer = <CALayer: 0x600002ceaaa0>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTTextView: 0x7f96f5ee8d20; reactTag: 1589; text: Test Name frame = (0 72; 83 24.5); text = 'Test Name'; opaque = NO; layer = <CALayer: 0x600002cebf40>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTView: 0x7f96f5ec3590; reactTag: 1603; frame = (0 96; 150 18); layer = <CALayer: 0x600002c49f60>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTTextView: 0x7f96f5eb4d60; reactTag: 1595; text: 🇺🇸 frame = (0 0; 19.5 18.5); text = '🇺🇸'; opaque = NO; layer = <CALayer: 0x600002cee6a0>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTTextView: 0x7f96f5eb3eb0; reactTag: 1599; text: +1 (205) 200-0000 frame = (23 0; 127.5 18.5); text = '+1 (205) 200-0000'; opaque = NO; layer = <CALayer: 0x600002cee4a0>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTView: 0x7f96f5e84710; reactTag: 1605; frame = (0 134; 248 1); layer = <CALayer: 0x600002c4e260>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTTextView: 0x7f96f5fd08a0; reactTag: 1615; text: $0.00 frame = (0 147; 45.5 22.5); text = '$0.00'; opaque = NO; layer = <CALayer: 0x600002ca0be0>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTTextView: 0x7f96f5fd7f40; reactTag: 1625; text: 0.00 Celo Dollars frame = (0 171; 113.5 18.5); text = '0.00 Celo Dollars'; opaque = NO; layer = <CALayer: 0x600002ca02e0>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTView: 0x7f96f5fee3d0; reactTag: 1627; frame = (0 201; 248 1); layer = <CALayer: 0x600002ca1100>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTView: 0x7f96f5fef490; reactTag: 1655; frame = (10 282; 260 48); clipsToBounds = YES; layer = <CALayer: 0x600002ca12e0>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTView: 0x7f96f5fef1f0; reactTag: 1653; frame = (0 0; 260 48); layer = <CALayer: 0x600002ca1220>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTView: 0x7f96f5feef50; reactTag: 1649; frame = (0 0; 260 48); layer = <CALayer: 0x600002ca1ea0>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RNSVGSvgView: 0x7f96f5fd9de0; frame = (8 8; 32 32); layer = <CALayer: 0x600002ca2640>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RNSVGGroup: 0x7f96f78d2600; frame = (5.669 3.91485; 20.1332 24.2601); opaque = NO; userInteractionEnabled = NO; layer = <CALayer: 0x600002ca1c60>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RNSVGPath: 0x7f96f7922a00; frame = (11.9456 3.91485; 13.8565 17.1184); opaque = NO; userInteractionEnabled = NO; layer = <CALayer: 0x600002ca1180>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RNSVGPath: 0x7f96f7921800; frame = (5.669 11.072; 13.854 17.103); opaque = NO; userInteractionEnabled = NO; layer = <CALayer: 0x600002ca25e0>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTView: 0x7f96f5feea50; reactTag: 1647; frame = (72 13; 25 22); layer = <CALayer: 0x600002ca13a0>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTTextView: 0x7f96f5fb7150; reactTag: 1645; text: Home frame = (-20 0; 45.5 22.5); text = 'Home'; opaque = NO; layer = <CALayer: 0x600002ca1e20>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTView: 0x7f96f5ff0620; reactTag: 1679; frame = (10 338; 260 48); clipsToBounds = YES; layer = <CALayer: 0x600002ca24c0>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTView: 0x7f96f5ff0380; reactTag: 1677; frame = (0 0; 260 48); layer = <CALayer: 0x600002ca2a80>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTView: 0x7f96f5ff00e0; reactTag: 1675; frame = (0 0; 260 48); layer = <CALayer: 0x600002ca2d80>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RNSVGSvgView: 0x7f96f5fef730; frame = (8 8; 32 32); layer = <CALayer: 0x600002ca2460>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RNSVGGroup: 0x7f96f78f5c00; frame = (1.86524 7.58215; 28.0414 19.3484); opaque = NO; userInteractionEnabled = NO; layer = <CALayer: 0x600002ca0c80>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RNSVGPath: 0x7f96f78f8400; frame = (20.3577 7.58215; 9.54894 11.7979); opaque = NO; userInteractionEnabled = NO; layer = <CALayer: 0x600002ca1300>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RNSVGPath: 0x7f96f78a1800; frame = (1.86524 8.8743; 20.2735 18.0562); opaque = NO; userInteractionEnabled = NO; layer = <CALayer: 0x600002ca12a0>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTView: 0x7f96f5fefc60; reactTag: 1673; frame = (72 13; 22 22); layer = <CALayer: 0x600002ca34e0>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTTextView: 0x7f96f5fd7b50; reactTag: 1669; text: CELO frame = (-20 0; 42.5 22.5); text = 'CELO'; opaque = NO; layer = <CALayer: 0x600002ca2480>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTView: 0x7f96f5ff5700; reactTag: 1707; frame = (10 394; 260 48); clipsToBounds = YES; layer = <CALayer: 0x600002ca30e0>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTView: 0x7f96f5ff5460; reactTag: 1705; frame = (0 0; 260 48); layer = <CALayer: 0x600002ca33e0>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTView: 0x7f96f5ff51c0; reactTag: 1703; frame = (0 0; 260 48); layer = <CALayer: 0x600002ca3380>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RNSVGSvgView: 0x7f96f5ff4660; frame = (8 8; 32 32); layer = <CALayer: 0x600002ca26c0>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RNSVGGroup: 0x7f96f78f7e00; frame = (5 5; 26 24); opaque = NO; userInteractionEnabled = NO; layer = <CALayer: 0x600002ca24e0>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RNSVGPath: 0x7f96f78f6a00; frame = (5 5; 13.943 24); opaque = NO; userInteractionEnabled = NO; layer = <CALayer: 0x600002ca37e0>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RNSVGPath: 0x7f96f78f6200; frame = (14 14.5; 12 5); opaque = NO; userInteractionEnabled = NO; layer = <CALayer: 0x600002ca3660>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RNSVGCircle: 0x7f96f78f7000; frame = (24 12; 7 7); opaque = NO; userInteractionEnabled = NO; layer = <CALayer: 0x600002ca2d00>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTView: 0x7f96f5ff4d40; reactTag: 1699; frame = (72 13; 75 22); layer = <CALayer: 0x600002ca38a0>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTTextView: 0x7f96f5ff4910; reactTag: 1697; text: Account Key frame = (-20 0; 95.5 22.5); text = 'Account Key'; opaque = NO; layer = <CALayer: 0x600002ca1740>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTView: 0x7f96f5ff3ba0; reactTag: 1729; frame = (10 450; 260 48); clipsToBounds = YES; layer = <CALayer: 0x600002ca2c20>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTView: 0x7f96f5ff3900; reactTag: 1727; frame = (0 0; 260 48); layer = <CALayer: 0x600002ca3360>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTView: 0x7f96f5ff3660; reactTag: 1725; frame = (0 0; 260 48); layer = <CALayer: 0x600002ca32e0>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RNSVGSvgView: 0x7f96f5ff59a0; frame = (8 8; 32 32); layer = <CALayer: 0x600002ca17a0>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RNSVGGroup: 0x7f96f78f7600; frame = (4.90237 7.90237; 23.1953 15.1953); opaque = NO; userInteractionEnabled = NO; layer = <CALayer: 0x600002ca1f00>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RNSVGPath: 0x7f96f78fb400; frame = (4.90237 7.90237; 23.1953 15.1953); opaque = NO; userInteractionEnabled = NO; layer = <CALayer: 0x600002ca1a00>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTView: 0x7f96f5ff33c0; reactTag: 1723; frame = (72 13; 120.5 22); layer = <CALayer: 0x600002ca2b60>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTTextView: 0x7f96f5ff4ac0; reactTag: 1719; text: Add and Withdraw frame = (-20 0; 141 22.5); text = 'Add and Withdraw'; opaque = NO; layer = <CALayer: 0x600002ca2f40>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTView: 0x7f96f5fed2e0; reactTag: 1759; frame = (10 506; 260 48); clipsToBounds = YES; layer = <CALayer: 0x600002ca2500>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTView: 0x7f96f5fafca0; reactTag: 1757; frame = (0 0; 260 48); layer = <CALayer: 0x600002ca38c0>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTView: 0x7f96f5fafa00; reactTag: 1755; frame = (0 0; 260 48); layer = <CALayer: 0x600002ca04a0>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RNSVGSvgView: 0x7f96f5ff5c50; frame = (8 8; 32 32); layer = <CALayer: 0x600002ca3600>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RNSVGGroup: 0x7f96f78d2c00; frame = (5 4; 22 24); opaque = NO; userInteractionEnabled = NO; layer = <CALayer: 0x600002ca2ac0>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RNSVGPath: 0x7f96f78fba00; frame = (5 7.5; 13 5); opaque = NO; userInteractionEnabled = NO; layer = <CALayer: 0x600002ca27c0>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RNSVGPath: 0x7f96f78fac00; frame = (14 19.5; 12 6); opaque = NO; userInteractionEnabled = NO; layer = <CALayer: 0x600002ca2dc0>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RNSVGCircle: 0x7f96f78fc000; frame = (16 4; 11 11); opaque = NO; userInteractionEnabled = NO; layer = <CALayer: 0x600002ca2bc0>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RNSVGCircle: 0x7f96f78fce00; frame = (5 17; 11 11); opaque = NO; userInteractionEnabled = NO; layer = <CALayer: 0x600002ca3540>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTView: 0x7f96f5ff2260; reactTag: 1753; frame = (72 13; 42.5 22); layer = <CALayer: 0x600002ca06c0>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTTextView: 0x7f96f5ff4250; reactTag: 1749; text: Settings frame = (-20 0; 63 22.5); text = 'Settings'; opaque = NO; layer = <CALayer: 0x600002ca3a20>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTView: 0x7f96f5fe1f90; reactTag: 1787; frame = (10 562; 260 48); clipsToBounds = YES; layer = <CALayer: 0x600002ca32a0>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTView: 0x7f96f5fe1cf0; reactTag: 1785; frame = (0 0; 260 48); layer = <CALayer: 0x600002ca2420>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTView: 0x7f96f5feddf0; reactTag: 1783; frame = (0 0; 260 48); layer = <CALayer: 0x600002ca2200>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RNSVGSvgView: 0x7f96f5fed580; frame = (8 8; 32 32); layer = <CALayer: 0x600002ca0c00>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RNSVGGroup: 0x7f96f78fda00; frame = (4 4; 24 24); opaque = NO; userInteractionEnabled = NO; layer = <CALayer: 0x600002ca3f80>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RNSVGCircle: 0x7f96f78ff400; frame = (4 4; 24 24); opaque = NO; userInteractionEnabled = NO; layer = <CALayer: 0x600002ca3c60>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RNSVGPath: 0x7f96f78fc600; frame = (12.008 9; 7.901 10.5489); opaque = NO; userInteractionEnabled = NO; layer = <CALayer: 0x600002ca0700>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RNSVGCircle: 0x7f96f78fd400; frame = (14.637 21.001; 2.196 2.196); opaque = NO; userInteractionEnabled = NO; layer = <CALayer: 0x600002ca3d20>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTView: 0x7f96f5fed970; reactTag: 1779; frame = (72 13; 15 22); layer = <CALayer: 0x600002ca2340>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTTextView: 0x7f96f5ff2500; reactTag: 1777; text: Help frame = (-20 0; 35.5 22.5); text = 'Help'; opaque = NO; layer = <CALayer: 0x600002ca2700>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTView: 0x7f96f5fdb7e0; reactTag: 1817; frame = (16 646; 248 110); layer = <CALayer: 0x600002ca1140>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTTextView: 0x7f96f5fedc10; reactTag: 1793; text: Account No. frame = (0 0; 248 16.5); text = 'Account No.'; opaque = NO; layer = <CALayer: 0x600002ca3fc0>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTView: 0x7f96f5fdb3d0; reactTag: 1809; frame = (0 24; 248 36); layer = <CALayer: 0x600002ca1260>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTView: 0x7f96f5fdb130; reactTag: 1807; frame = (4 0; 215 36); layer = <CALayer: 0x600002ca2260>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTView: 0x7f96f5fdacc0; reactTag: 1805; frame = (0 0; 215 36); layer = <CALayer: 0x600002ca2280>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTTextView: 0x7f96f5fe2510; reactTag: 1797; text: 0x 7420 9d66 eb75 348b d33e frame = (0 0; 215 18.5); text = '0x 7420 9d66 eb75 348b d3...'; opaque = NO; layer = <CALayer: 0x600002ca3ca0>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTTextView: 0x7f96f5fdab10; reactTag: 1803; text: 6728 3f78 3161 129c 9a1b frame = (0 18; 215 18.5); text = '6728 3f78 3161 129c 9a1b'; opaque = NO; layer = <CALayer: 0x600002ca22e0>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTTextView: 0x7f96f5fdaf60; reactTag: 1815; text: Version 1.0.1 frame = (0 92; 248 18.5); text = 'Version 1.0.1'; opaque = NO; layer = <CALayer: 0x600002ca0b60>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <_UIScrollViewScrollIndicator: 0x7f96f5cd0120; frame = (274 155; 3 704); alpha = 0; autoresize = LM; layer = <CALayer: 0x600002caea80>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <UIView: 0x7f96f5cd02b0; frame = (0 0; 3 704); layer = <CALayer: 0x600002cacc60>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <_UIScrollViewScrollIndicator: 0x7f96f5ccf710; frame = (3 856; 274 3); alpha = 0; autoresize = TM; layer = <CALayer: 0x600002cae9e0>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <UIView: 0x7f96f5ccfcc0; frame = (0 0; 274 3); layer = <CALayer: 0x600002caf700>>
| | | | | | | | | | | | | | | | | | | <RCTView: 0x7f96f5d3c050; reactTag: 207; frame = (0 0; 414 0); layer = <CALayer: 0x600002ce4900>>
| | | | | | | | | | | | | | | | | <RCTView: 0x7f96f5d33320; reactTag: 29; frame = (0 0; 414 0); layer = <CALayer: 0x600002ce59c0>>
| | | | | | | | | <RCTView: 0x7f96f5d34ab0; reactTag: 53; frame = (0 0; 414 0); layer = <CALayer: 0x600002ce5660>>
at process._tickCallback (internal/process/next_tick.js:68:7)
Attempt No. 2:
Test Passed!
| 2.0 | [FLAKEY TEST] end-to-end-mobile-test-ios -> mobile -> New Account -> CELO -> Go to CELO screen and through education flow - Discovered at commit 4a3b0db23679146204b76e4e98ff3b703296ab49
Attempt No. 1:
Error: Test Failed: View “<RCTView: 0x7f96f5ffae60>” is not hittable at point “{"x":60,"y":24}”; Another view “<RCTView: 0x7f96f5e8a710>” is hittable at window point “{"x":207,"y":814}”
View Hierarchy:
<UIWindow: 0x7f96f5d17ff0; frame = (0 0; 414 896); autoresize = W+H; gestureRecognizers = <NSArray: 0x600002210f30>; layer = <UIWindowLayer: 0x600002c6d240>>
| <UITransitionView: 0x7f96f5f72540; frame = (0 0; 414 896); autoresize = W+H; layer = <CALayer: 0x600002c7afa0>>
| | <UIDropShadowView: 0x7f96f5f733a0; frame = (0 0; 414 896); clipsToBounds = YES; autoresize = W+H; layer = <CALayer: 0x600002c7bd60>>
| | | <RCTRootView: 0x7f96f5f7d1b0; frame = (0 0; 414 896); autoresize = W+H; layer = <CALayer: 0x600002c58880>>
| | | | <RCTRootContentView: 0x7f96f5f779f0; reactTag: 1; frame = (0 0; 414 896); gestureRecognizers = <NSArray: 0x600002216220>; layer = <CALayer: 0x600002c58920>>
| | | | | <RCTView: 0x7f96f5f69e90; reactTag: 7; frame = (0 0; 414 896); layer = <CALayer: 0x600002c29000>>
| | | | | | <RCTView: 0x7f96f5c35e40; reactTag: 5; frame = (0 0; 414 896); layer = <CALayer: 0x600002cd21a0>>
| | | | | | | <RNCSafeAreaProvider: 0x7f96f5c72d70; reactTag: 3; frame = (0 0; 414 896); layer = <CALayer: 0x600002cd2080>>
| | | | | | | | <RCTView: 0x7f96f5d34d50; reactTag: 55; frame = (0 0; 414 896); layer = <CALayer: 0x600002ce5700>>
| | | | | | | | | <RCTView: 0x7f96f5d34810; reactTag: 49; frame = (0 0; 414 896); layer = <CALayer: 0x600002ce5840>>
| | | | | | | | | | <RCTView: 0x7f96f5d342e0; reactTag: 47; frame = (0 0; 414 896); layer = <CALayer: 0x600002ce58c0>>
| | | | | | | | | | | <RCTView: 0x7f96f5d34040; reactTag: 45; frame = (0 0; 414 896); layer = <CALayer: 0x600002ce5880>>
| | | | | | | | | | | | <RCTView: 0x7f96f5d314f0; reactTag: 15; frame = (0 0; 414 0); layer = <CALayer: 0x600002cd6e40>>
| | | | | | | | | | | | <RCTView: 0x7f96f5d329f0; reactTag: 43; frame = (0 0; 414 896); layer = <CALayer: 0x600002ce53c0>>
| | | | | | | | | | | | | <RCTView: 0x7f96f5c876d0; reactTag: 19; frame = (0 0; 414 896); layer = <CALayer: 0x600002cd3c60>>
| | | | | | | | | | | | | | <RCTView: 0x7f96f5cd2b80; reactTag: 2539; frame = (0 0; 414 896); alpha = 0.3; userInteractionEnabled = NO; layer = <CALayer: 0x600002a1a8e0>>
| | | | | | | | | | | | | <RCTView: 0x7f96f5d33da0; reactTag: 39; frame = (0 0; 414 896); layer = <CALayer: 0x600002ce56a0>>
| | | | | | | | | | | | | | <RCTView: 0x7f96f5d33b00; reactTag: 37; frame = (0 0; 414 896); clipsToBounds = YES; gestureRecognizers = <NSArray: 0x6000022f3480>; layer = <CALayer: 0x600002ce5300>>
| | | | | | | | | | | | | | | <RCTView: 0x7f96f5d33860; reactTag: 35; frame = (0 0; 414 896); clipsToBounds = YES; layer = <CALayer: 0x600002ce59e0>>
| | | | | | | | | | | | | | | | <RCTView: 0x7f96f5d335c0; reactTag: 33; frame = (0 0; 414 896); layer = <CALayer: 0x600002ce59a0>>
| | | | | | | | | | | | | | | | | <RCTView: 0x7f96f5d32ed0; reactTag: 27; frame = (0 0; 414 896); layer = <CALayer: 0x600002ce5980>>
| | | | | | | | | | | | | | | | | | <RCTView: 0x7f96f5d3c2f0; reactTag: 209; frame = (0 0; 414 896); layer = <CALayer: 0x600002ce4940>>
| | | | | | | | | | | | | | | | | | | <RCTView: 0x7f96f5e602f0; reactTag: 159; frame = (0 0; 414 896); layer = <CALayer: 0x600002cd5280>>
| | | | | | | | | | | | | | | | | | | | <RCTView: 0x7f96f5ea4b00; reactTag: 1847; frame = (0 0; 414 896); layer = <CALayer: 0x600002c8a880>>
| | | | | | | | | | | | | | | | | | | | | <RCTView: 0x7f96f5d35b50; reactTag: 1365; frame = (0 0; 414 0); layer = <CALayer: 0x600002c9d800>>
| | | | | | | | | | | | | | | | | | | | | <RCTView: 0x7f96f5ea4860; reactTag: 1845; frame = (0 0; 414 896); layer = <CALayer: 0x600002c8ad80>>
| | | | | | | | | | | | | | | | | | | | | | <RCTView: 0x7f96f5fddb80; reactTag: 1843; frame = (0 0; 414 896); layer = <CALayer: 0x600002ca3700>>
| | | | | | | | | | | | | | | | | | | | | | | <RCTView: 0x7f96f5fdd8e0; reactTag: 1839; frame = (0 0; 414 896); gestureRecognizers = <NSArray: 0x6000023e6580>; layer = <CALayer: 0x600002ca2e60>>
| | | | | | | | | | | | | | | | | | | | | | | | <RCTView: 0x7f96f5d109d0; reactTag: 1367; frame = (0 0; 3 896); userInteractionEnabled = NO; layer = <CALayer: 0x600002c9ec60>>
| | | | | | | | | | | | | | | | | | | | | | | | <RCTView: 0x7f96f5fdd640; reactTag: 1837; frame = (0 0; 414 896); clipsToBounds = YES; layer = <CALayer: 0x600002ca2ec0>>
| | | | | | | | | | | | | | | | | | | | | | | | | <RCTView: 0x7f96f5fdd3a0; reactTag: 1835; frame = (0 0; 414 896); layer = <CALayer: 0x600002ca3220>>
| | | | | | | | | | | | | | | | | | | | | | | | | | <RCTView: 0x7f96f5fdd100; reactTag: 1833; frame = (0 0; 414 896); layer = <CALayer: 0x600002ca1160>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTView: 0x7f96f5fdce60; reactTag: 1829; frame = (0 0; 414 896); layer = <CALayer: 0x600002ca1380>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTView: 0x7f96f5fdcbc0; reactTag: 1827; frame = (0 0; 414 896); clipsToBounds = YES; gestureRecognizers = <NSArray: 0x6000023e6430>; layer = <CALayer: 0x600002ca11e0>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTView: 0x7f96f5ecc840; reactTag: 1577; frame = (0 0; 414 896); layer = <CALayer: 0x600002ceaf80>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTView: 0x7f96f5fd0600; reactTag: 1573; frame = (0 0; 414 896); layer = <CALayer: 0x600002ca1360>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RNSScreenContainerView: 0x7f96f5f8b900; frame = (0 0; 414 896); layer = <CALayer: 0x600002ca1060>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <UIView: 0x7f96f5f999c0; frame = (0 0; 414 896); autoresize = W+H; layer = <CALayer: 0x600002ca1340>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RNSScreenView: 0x7f96f5ccb3f0; reactTag: 3313; frame = (0 0; 414 896); layer = <CALayer: 0x600002a44b80>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RNCSafeAreaView: 0x7f96f5ff7dd0; reactTag: 3309; frame = (0 0; 414 896); layer = <CALayer: 0x600002a56980>; RNCSafeAreaInsets = {44, 0, 34, 0}; appliedRNCSafeAreaInsets = {44, 0, 34, 0}>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTView: 0x7f96f8710bd0; reactTag: 3193; frame = (0 44; 414 56); layer = <CALayer: 0x600002a56d80>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTView: 0x7f96f5fb3170; reactTag: 3189; frame = (16 12; 32 32); layer = <CALayer: 0x600002a57400>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RNSVGSvgView: 0x7f96f5fb6d20; frame = (0 0; 32 32); layer = <CALayer: 0x600002a546a0>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RNSVGGroup: 0x7f96f7925600; frame = (6 8.5; 20 14.5); opaque = NO; userInteractionEnabled = NO; layer = <CALayer: 0x600002a56c20>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RNSVGLine: 0x7f96f7922400; frame = (6 8.5; 20 2.5); opaque = NO; userInteractionEnabled = NO; layer = <CALayer: 0x600002a544e0>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RNSVGLine: 0x7f96f78a1200; frame = (6 14.5; 20 2.5); opaque = NO; userInteractionEnabled = NO; layer = <CALayer: 0x600002a574c0>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RNSVGLine: 0x7f96f78be000; frame = (6 20.5; 20 2.5); opaque = NO; userInteractionEnabled = NO; layer = <CALayer: 0x600002a543c0>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTView: 0x7f96f5ff7b30; reactTag: 3307; frame = (0 100; 414 762); layer = <CALayer: 0x600002a545c0>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTView: 0x7f96f5ffabc0; reactTag: 3293; frame = (0 0; 414 690); layer = <CALayer: 0x600002a579a0>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTScrollView: 0x7f96f5f956d0; reactTag: 3277; frame = (0 0; 414 690); clipsToBounds = YES; layer = <CALayer: 0x600002a57d40>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTCustomScrollView: 0x7f96f78bee00; baseClass = UIScrollView; frame = (0 0; 414 690); clipsToBounds = YES; autoresize = W+H; gestureRecognizers = <NSArray: 0x6000023e6100>; layer = <CALayer: 0x600002a57500>; contentOffset: {0, 0}; contentSize: {1656, 690}; adjustedContentInset: {0, 0, 0, 0}>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTScrollContentView: 0x7f96f5fd9300; reactTag: 3275; frame = (0 0; 1656 690); layer = <CALayer: 0x600002a56480>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTView: 0x7f96f8706ec0; reactTag: 3213; frame = (0 0; 414 690); layer = <CALayer: 0x600002a56500>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTView: 0x7f96f873b2b0; reactTag: 3209; frame = (0 0; 414 666); layer = <CALayer: 0x600002a54c80>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTView: 0x7f96f5fda300; reactTag: 3207; frame = (24 0; 366 666); layer = <CALayer: 0x600002a55d40>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTImageView: 0x7f96f5f6ef30; reactTag: 3195; frame = (63 187; 240 180); clipsToBounds = YES; layer = <CALayer: 0x600002a55d00>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTUIImageViewAnimated: 0x7f96f5fc8750; baseClass = UIImageView; frame = (0 0; 240 180); opaque = NO; autoresize = W+H; userInteractionEnabled = NO; layer = <CALayer: 0x600002a55880>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTTextView: 0x7f96f5fed130; reactTag: 3199; text: What is CELO? frame = (0 390.5; 366 28.5); text = 'What is CELO?'; opaque = NO; layer = <CALayer: 0x600002a565e0>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTTextView: 0x7f96f5fd8d20; reactTag: 3205; text: CELO helps keep the Celo Network running and the Celo Dollar stable. frame = (0 419; 366 60.5); text = 'CELO helps keep the Celo ...'; opaque = NO; layer = <CALayer: 0x600002a566c0>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTView: 0x7f96f8742650; reactTag: 3233; frame = (414 0; 414 690); layer = <CALayer: 0x600002a55b40>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTView: 0x7f96f8742f40; reactTag: 3229; frame = (0 0; 414 666); layer = <CALayer: 0x600002a54440>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTView: 0x7f96f8732b70; reactTag: 3227; frame = (24 0; 366 666); layer = <CALayer: 0x600002a54540>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTImageView: 0x7f96f5fc3d20; reactTag: 3215; frame = (63 176; 240 180); clipsToBounds = YES; layer = <CALayer: 0x600002a55a00>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTUIImageViewAnimated: 0x7f96f87474d0; baseClass = UIImageView; frame = (0 0; 240 180); opaque = NO; autoresize = W+H; userInteractionEnabled = NO; layer = <CALayer: 0x600002a56d00>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTTextView: 0x7f96f5fc4980; reactTag: 3219; text: CELO’s price changes frame = (0 379.5; 366 28.5); text = 'CELO’s price changes'; opaque = NO; layer = <CALayer: 0x600002a56940>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTTextView: 0x7f96f5f950e0; reactTag: 3225; text: Unlike Celo Dollars, the value of CELO changes. If more people use Celo Dollar, the value of CELO increases. frame = (0 408; 366 82.5); text = 'Unlike Celo Dollars, the ...'; opaque = NO; layer = <CALayer: 0x600002a573e0>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTView: 0x7f96f5f93330; reactTag: 3253; frame = (828 0; 414 690); layer = <CALayer: 0x600002a57a20>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTView: 0x7f96f5f94cc0; reactTag: 3249; frame = (0 0; 414 666); layer = <CALayer: 0x600002a56cc0>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTView: 0x7f96f8736200; reactTag: 3247; frame = (24 0; 366 666); layer = <CALayer: 0x600002a56b40>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTImageView: 0x7f96f5ed8cd0; reactTag: 3235; frame = (63 176; 240 180); clipsToBounds = YES; layer = <CALayer: 0x600002a42c80>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTUIImageViewAnimated: 0x7f96f90005e0; baseClass = UIImageView; frame = (0 0; 240 180); opaque = NO; autoresize = W+H; userInteractionEnabled = NO; layer = <CALayer: 0x600002a43ec0>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTTextView: 0x7f96f5e11570; reactTag: 3239; text: Shape the Celo Network frame = (0 379.5; 366 28.5); text = 'Shape the Celo Network'; opaque = NO; layer = <CALayer: 0x600002a407e0>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTTextView: 0x7f96f5fdba80; reactTag: 3245; text: By holding CELO, you have the ability to vote for changes and features you’d like to see on the Celo Network. frame = (0 408; 366 82.5); text = 'By holding CELO, you have...'; opaque = NO; layer = <CALayer: 0x600002a57c60>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTView: 0x7f96f8713910; reactTag: 3273; frame = (1242 0; 414 690); layer = <CALayer: 0x600002a55620>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTView: 0x7f96f5f6f400; reactTag: 3269; frame = (0 0; 414 666); layer = <CALayer: 0x600002a564e0>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTView: 0x7f96f873c4c0; reactTag: 3267; frame = (24 0; 366 666); layer = <CALayer: 0x600002a56740>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTImageView: 0x7f96f5fbd2a0; reactTag: 3255; frame = (63 176; 240 180); clipsToBounds = YES; layer = <CALayer: 0x600002a57420>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTUIImageViewAnimated: 0x7f96f5fdf8e0; baseClass = UIImageView; frame = (0 0; 240 180); opaque = NO; autoresize = W+H; userInteractionEnabled = NO; layer = <CALayer: 0x600002a54600>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTTextView: 0x7f96f5f98e80; reactTag: 3259; text: Please buy and sell responsibly frame = (0 379.5; 366 28.5); text = 'Please buy and sell respo...'; opaque = NO; layer = <CALayer: 0x600002a55220>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTTextView: 0x7f96f5fbab40; reactTag: 3265; text: Celo Wallet allows you to buy and sell CELO. CELO presents a risk of financial loss, please exercise caution. frame = (0 408; 366 82.5); text = 'Celo Wallet allows you to...'; opaque = NO; layer = <CALayer: 0x600002a56fe0>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTView: 0x7f96f5ffa920; reactTag: 3289; frame = (0 654; 414 11); userInteractionEnabled = NO; layer = <CALayer: 0x600002a55780>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTView: 0x7f96f5fec370; reactTag: 3279; frame = (188 3; 5 5); layer = <CALayer: 0x600002a549e0>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTView: 0x7f96f5f95a90; reactTag: 3283; frame = (199 3; 5 5); layer = <CALayer: 0x600002a560c0>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTView: 0x7f96f5fe1270; reactTag: 3285; frame = (210 3; 5 5); layer = <CALayer: 0x600002a54ae0>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTView: 0x7f96f5fe1510; reactTag: 3287; frame = (221 3; 5 5); layer = <CALayer: 0x600002a55f80>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTView: 0x7f96f5ff7890; reactTag: 3305; frame = (147 690; 120 48); layer = <CALayer: 0x600002a55920>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTView: 0x7f96f5ff75f0; reactTag: 3303; frame = (0 0; 120 48); clipsToBounds = YES; layer = <CALayer: 0x600002a550a0>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTView: 0x7f96f5ffae60; reactTag: 3299; frame = (0 0; 120 48); layer = <CALayer: 0x600002a56220>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTTextView: 0x7f96f5fe17b0; reactTag: 3297; text: Next frame = (41.5 12.5; 37 23); text = 'Next'; opaque = NO; layer = <CALayer: 0x600002a54e40>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTView: 0x7f96f5e8a710; reactTag: 1575; frame = (0 0; 414 896); alpha = 0.0107927; gestureRecognizers = <NSArray: 0x6000023e62e0>; layer = <CALayer: 0x600002ceb3e0>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTView: 0x7f96f5fdc920; reactTag: 1825; frame = (-263.129 0; 280 896); transform = [1, 0, 0, 1, 16.870845794677734, 0]; layer = <CALayer: 0x600002ca11a0>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTScrollView: 0x7f96f5fdbef0; reactTag: 1823; frame = (0 0; 280 896); clipsToBounds = YES; layer = <CALayer: 0x600002ca0fe0>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTCustomScrollView: 0x7f96f78ffa00; baseClass = UIScrollView; frame = (0 0; 280 896); clipsToBounds = YES; autoresize = W+H; gestureRecognizers = <NSArray: 0x6000022f1e30>; layer = <CALayer: 0x600002ca1000>; contentOffset: {0, 0}; contentSize: {280, 788}; adjustedContentInset: {0, 0, 0, 0}>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTScrollContentView: 0x7f96f5fdbc50; reactTag: 1819; frame = (0 0; 280 788); layer = <CALayer: 0x600002ca1020>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTView: 0x7f96f5fee670; reactTag: 1629; frame = (16 64; 248 214); layer = <CALayer: 0x600002ca1120>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTView: 0x7f96f5e893d0; reactTag: 1585; frame = (0 0; 64 64); layer = <CALayer: 0x600002cebe80>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTView: 0x7f96f5e98ad0; reactTag: 1583; frame = (0 0; 64 64); layer = <CALayer: 0x600002cebdc0>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTImageView: 0x7f96f5ef0740; reactTag: 1579; frame = (0 0; 64 64); clipsToBounds = YES; layer = <CALayer: 0x600002ceb560>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTUIImageViewAnimated: 0x7f96f5e16b90; baseClass = UIImageView; frame = (0 0; 64 64); opaque = NO; autoresize = W+H; userInteractionEnabled = NO; layer = <CALayer: 0x600002ceaaa0>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTTextView: 0x7f96f5ee8d20; reactTag: 1589; text: Test Name frame = (0 72; 83 24.5); text = 'Test Name'; opaque = NO; layer = <CALayer: 0x600002cebf40>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTView: 0x7f96f5ec3590; reactTag: 1603; frame = (0 96; 150 18); layer = <CALayer: 0x600002c49f60>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTTextView: 0x7f96f5eb4d60; reactTag: 1595; text: 🇺🇸 frame = (0 0; 19.5 18.5); text = '🇺🇸'; opaque = NO; layer = <CALayer: 0x600002cee6a0>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTTextView: 0x7f96f5eb3eb0; reactTag: 1599; text: +1 (205) 200-0000 frame = (23 0; 127.5 18.5); text = '+1 (205) 200-0000'; opaque = NO; layer = <CALayer: 0x600002cee4a0>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTView: 0x7f96f5e84710; reactTag: 1605; frame = (0 134; 248 1); layer = <CALayer: 0x600002c4e260>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTTextView: 0x7f96f5fd08a0; reactTag: 1615; text: $0.00 frame = (0 147; 45.5 22.5); text = '$0.00'; opaque = NO; layer = <CALayer: 0x600002ca0be0>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTTextView: 0x7f96f5fd7f40; reactTag: 1625; text: 0.00 Celo Dollars frame = (0 171; 113.5 18.5); text = '0.00 Celo Dollars'; opaque = NO; layer = <CALayer: 0x600002ca02e0>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTView: 0x7f96f5fee3d0; reactTag: 1627; frame = (0 201; 248 1); layer = <CALayer: 0x600002ca1100>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTView: 0x7f96f5fef490; reactTag: 1655; frame = (10 282; 260 48); clipsToBounds = YES; layer = <CALayer: 0x600002ca12e0>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTView: 0x7f96f5fef1f0; reactTag: 1653; frame = (0 0; 260 48); layer = <CALayer: 0x600002ca1220>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTView: 0x7f96f5feef50; reactTag: 1649; frame = (0 0; 260 48); layer = <CALayer: 0x600002ca1ea0>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RNSVGSvgView: 0x7f96f5fd9de0; frame = (8 8; 32 32); layer = <CALayer: 0x600002ca2640>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RNSVGGroup: 0x7f96f78d2600; frame = (5.669 3.91485; 20.1332 24.2601); opaque = NO; userInteractionEnabled = NO; layer = <CALayer: 0x600002ca1c60>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RNSVGPath: 0x7f96f7922a00; frame = (11.9456 3.91485; 13.8565 17.1184); opaque = NO; userInteractionEnabled = NO; layer = <CALayer: 0x600002ca1180>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RNSVGPath: 0x7f96f7921800; frame = (5.669 11.072; 13.854 17.103); opaque = NO; userInteractionEnabled = NO; layer = <CALayer: 0x600002ca25e0>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTView: 0x7f96f5feea50; reactTag: 1647; frame = (72 13; 25 22); layer = <CALayer: 0x600002ca13a0>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTTextView: 0x7f96f5fb7150; reactTag: 1645; text: Home frame = (-20 0; 45.5 22.5); text = 'Home'; opaque = NO; layer = <CALayer: 0x600002ca1e20>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTView: 0x7f96f5ff0620; reactTag: 1679; frame = (10 338; 260 48); clipsToBounds = YES; layer = <CALayer: 0x600002ca24c0>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTView: 0x7f96f5ff0380; reactTag: 1677; frame = (0 0; 260 48); layer = <CALayer: 0x600002ca2a80>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTView: 0x7f96f5ff00e0; reactTag: 1675; frame = (0 0; 260 48); layer = <CALayer: 0x600002ca2d80>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RNSVGSvgView: 0x7f96f5fef730; frame = (8 8; 32 32); layer = <CALayer: 0x600002ca2460>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RNSVGGroup: 0x7f96f78f5c00; frame = (1.86524 7.58215; 28.0414 19.3484); opaque = NO; userInteractionEnabled = NO; layer = <CALayer: 0x600002ca0c80>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RNSVGPath: 0x7f96f78f8400; frame = (20.3577 7.58215; 9.54894 11.7979); opaque = NO; userInteractionEnabled = NO; layer = <CALayer: 0x600002ca1300>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RNSVGPath: 0x7f96f78a1800; frame = (1.86524 8.8743; 20.2735 18.0562); opaque = NO; userInteractionEnabled = NO; layer = <CALayer: 0x600002ca12a0>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTView: 0x7f96f5fefc60; reactTag: 1673; frame = (72 13; 22 22); layer = <CALayer: 0x600002ca34e0>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTTextView: 0x7f96f5fd7b50; reactTag: 1669; text: CELO frame = (-20 0; 42.5 22.5); text = 'CELO'; opaque = NO; layer = <CALayer: 0x600002ca2480>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTView: 0x7f96f5ff5700; reactTag: 1707; frame = (10 394; 260 48); clipsToBounds = YES; layer = <CALayer: 0x600002ca30e0>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTView: 0x7f96f5ff5460; reactTag: 1705; frame = (0 0; 260 48); layer = <CALayer: 0x600002ca33e0>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTView: 0x7f96f5ff51c0; reactTag: 1703; frame = (0 0; 260 48); layer = <CALayer: 0x600002ca3380>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RNSVGSvgView: 0x7f96f5ff4660; frame = (8 8; 32 32); layer = <CALayer: 0x600002ca26c0>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RNSVGGroup: 0x7f96f78f7e00; frame = (5 5; 26 24); opaque = NO; userInteractionEnabled = NO; layer = <CALayer: 0x600002ca24e0>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RNSVGPath: 0x7f96f78f6a00; frame = (5 5; 13.943 24); opaque = NO; userInteractionEnabled = NO; layer = <CALayer: 0x600002ca37e0>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RNSVGPath: 0x7f96f78f6200; frame = (14 14.5; 12 5); opaque = NO; userInteractionEnabled = NO; layer = <CALayer: 0x600002ca3660>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RNSVGCircle: 0x7f96f78f7000; frame = (24 12; 7 7); opaque = NO; userInteractionEnabled = NO; layer = <CALayer: 0x600002ca2d00>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTView: 0x7f96f5ff4d40; reactTag: 1699; frame = (72 13; 75 22); layer = <CALayer: 0x600002ca38a0>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTTextView: 0x7f96f5ff4910; reactTag: 1697; text: Account Key frame = (-20 0; 95.5 22.5); text = 'Account Key'; opaque = NO; layer = <CALayer: 0x600002ca1740>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTView: 0x7f96f5ff3ba0; reactTag: 1729; frame = (10 450; 260 48); clipsToBounds = YES; layer = <CALayer: 0x600002ca2c20>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTView: 0x7f96f5ff3900; reactTag: 1727; frame = (0 0; 260 48); layer = <CALayer: 0x600002ca3360>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTView: 0x7f96f5ff3660; reactTag: 1725; frame = (0 0; 260 48); layer = <CALayer: 0x600002ca32e0>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RNSVGSvgView: 0x7f96f5ff59a0; frame = (8 8; 32 32); layer = <CALayer: 0x600002ca17a0>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RNSVGGroup: 0x7f96f78f7600; frame = (4.90237 7.90237; 23.1953 15.1953); opaque = NO; userInteractionEnabled = NO; layer = <CALayer: 0x600002ca1f00>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RNSVGPath: 0x7f96f78fb400; frame = (4.90237 7.90237; 23.1953 15.1953); opaque = NO; userInteractionEnabled = NO; layer = <CALayer: 0x600002ca1a00>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTView: 0x7f96f5ff33c0; reactTag: 1723; frame = (72 13; 120.5 22); layer = <CALayer: 0x600002ca2b60>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTTextView: 0x7f96f5ff4ac0; reactTag: 1719; text: Add and Withdraw frame = (-20 0; 141 22.5); text = 'Add and Withdraw'; opaque = NO; layer = <CALayer: 0x600002ca2f40>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTView: 0x7f96f5fed2e0; reactTag: 1759; frame = (10 506; 260 48); clipsToBounds = YES; layer = <CALayer: 0x600002ca2500>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTView: 0x7f96f5fafca0; reactTag: 1757; frame = (0 0; 260 48); layer = <CALayer: 0x600002ca38c0>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTView: 0x7f96f5fafa00; reactTag: 1755; frame = (0 0; 260 48); layer = <CALayer: 0x600002ca04a0>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RNSVGSvgView: 0x7f96f5ff5c50; frame = (8 8; 32 32); layer = <CALayer: 0x600002ca3600>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RNSVGGroup: 0x7f96f78d2c00; frame = (5 4; 22 24); opaque = NO; userInteractionEnabled = NO; layer = <CALayer: 0x600002ca2ac0>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RNSVGPath: 0x7f96f78fba00; frame = (5 7.5; 13 5); opaque = NO; userInteractionEnabled = NO; layer = <CALayer: 0x600002ca27c0>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RNSVGPath: 0x7f96f78fac00; frame = (14 19.5; 12 6); opaque = NO; userInteractionEnabled = NO; layer = <CALayer: 0x600002ca2dc0>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RNSVGCircle: 0x7f96f78fc000; frame = (16 4; 11 11); opaque = NO; userInteractionEnabled = NO; layer = <CALayer: 0x600002ca2bc0>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RNSVGCircle: 0x7f96f78fce00; frame = (5 17; 11 11); opaque = NO; userInteractionEnabled = NO; layer = <CALayer: 0x600002ca3540>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTView: 0x7f96f5ff2260; reactTag: 1753; frame = (72 13; 42.5 22); layer = <CALayer: 0x600002ca06c0>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTTextView: 0x7f96f5ff4250; reactTag: 1749; text: Settings frame = (-20 0; 63 22.5); text = 'Settings'; opaque = NO; layer = <CALayer: 0x600002ca3a20>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTView: 0x7f96f5fe1f90; reactTag: 1787; frame = (10 562; 260 48); clipsToBounds = YES; layer = <CALayer: 0x600002ca32a0>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTView: 0x7f96f5fe1cf0; reactTag: 1785; frame = (0 0; 260 48); layer = <CALayer: 0x600002ca2420>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTView: 0x7f96f5feddf0; reactTag: 1783; frame = (0 0; 260 48); layer = <CALayer: 0x600002ca2200>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RNSVGSvgView: 0x7f96f5fed580; frame = (8 8; 32 32); layer = <CALayer: 0x600002ca0c00>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RNSVGGroup: 0x7f96f78fda00; frame = (4 4; 24 24); opaque = NO; userInteractionEnabled = NO; layer = <CALayer: 0x600002ca3f80>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RNSVGCircle: 0x7f96f78ff400; frame = (4 4; 24 24); opaque = NO; userInteractionEnabled = NO; layer = <CALayer: 0x600002ca3c60>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RNSVGPath: 0x7f96f78fc600; frame = (12.008 9; 7.901 10.5489); opaque = NO; userInteractionEnabled = NO; layer = <CALayer: 0x600002ca0700>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RNSVGCircle: 0x7f96f78fd400; frame = (14.637 21.001; 2.196 2.196); opaque = NO; userInteractionEnabled = NO; layer = <CALayer: 0x600002ca3d20>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTView: 0x7f96f5fed970; reactTag: 1779; frame = (72 13; 15 22); layer = <CALayer: 0x600002ca2340>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTTextView: 0x7f96f5ff2500; reactTag: 1777; text: Help frame = (-20 0; 35.5 22.5); text = 'Help'; opaque = NO; layer = <CALayer: 0x600002ca2700>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTView: 0x7f96f5fdb7e0; reactTag: 1817; frame = (16 646; 248 110); layer = <CALayer: 0x600002ca1140>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTTextView: 0x7f96f5fedc10; reactTag: 1793; text: Account No. frame = (0 0; 248 16.5); text = 'Account No.'; opaque = NO; layer = <CALayer: 0x600002ca3fc0>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTView: 0x7f96f5fdb3d0; reactTag: 1809; frame = (0 24; 248 36); layer = <CALayer: 0x600002ca1260>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTView: 0x7f96f5fdb130; reactTag: 1807; frame = (4 0; 215 36); layer = <CALayer: 0x600002ca2260>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTView: 0x7f96f5fdacc0; reactTag: 1805; frame = (0 0; 215 36); layer = <CALayer: 0x600002ca2280>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTTextView: 0x7f96f5fe2510; reactTag: 1797; text: 0x 7420 9d66 eb75 348b d33e frame = (0 0; 215 18.5); text = '0x 7420 9d66 eb75 348b d3...'; opaque = NO; layer = <CALayer: 0x600002ca3ca0>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTTextView: 0x7f96f5fdab10; reactTag: 1803; text: 6728 3f78 3161 129c 9a1b frame = (0 18; 215 18.5); text = '6728 3f78 3161 129c 9a1b'; opaque = NO; layer = <CALayer: 0x600002ca22e0>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <RCTTextView: 0x7f96f5fdaf60; reactTag: 1815; text: Version 1.0.1 frame = (0 92; 248 18.5); text = 'Version 1.0.1'; opaque = NO; layer = <CALayer: 0x600002ca0b60>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <_UIScrollViewScrollIndicator: 0x7f96f5cd0120; frame = (274 155; 3 704); alpha = 0; autoresize = LM; layer = <CALayer: 0x600002caea80>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <UIView: 0x7f96f5cd02b0; frame = (0 0; 3 704); layer = <CALayer: 0x600002cacc60>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <_UIScrollViewScrollIndicator: 0x7f96f5ccf710; frame = (3 856; 274 3); alpha = 0; autoresize = TM; layer = <CALayer: 0x600002cae9e0>>
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | <UIView: 0x7f96f5ccfcc0; frame = (0 0; 274 3); layer = <CALayer: 0x600002caf700>>
| | | | | | | | | | | | | | | | | | | <RCTView: 0x7f96f5d3c050; reactTag: 207; frame = (0 0; 414 0); layer = <CALayer: 0x600002ce4900>>
| | | | | | | | | | | | | | | | | <RCTView: 0x7f96f5d33320; reactTag: 29; frame = (0 0; 414 0); layer = <CALayer: 0x600002ce59c0>>
| | | | | | | | | <RCTView: 0x7f96f5d34ab0; reactTag: 53; frame = (0 0; 414 0); layer = <CALayer: 0x600002ce5660>>
at process._tickCallback (internal/process/next_tick.js:68:7)
Attempt No. 2:
Test Passed!
| non_priority | end to end mobile test ios mobile new account celo go to celo screen and through education flow discovered at commit attempt no error test failed view “ ” is not hittable at point “ x y ” another view “ ” is hittable at window point “ x y ” view hierarchy layer layer layer layer layer rncsafeareainsets appliedrncsafeareainsets layer contentoffset contentsize adjustedcontentinset layer layer contentoffset contentsize adjustedcontentinset at process tickcallback internal process next tick js attempt no test passed | 0 |
8,973 | 12,480,226,906 | IssuesEvent | 2020-05-29 19:51:46 | goharbor/harbor | https://api.github.com/repos/goharbor/harbor | closed | Add column / info about used storage | backlog community kind/requirement | Add column/info about the used storage for a project and/or an image.
Can be useful to see the big consumers.
Thanks | 1.0 | Add column / info about used storage - Add column/info about the used storage for a project and/or an image.
Can be useful to see the big consumers.
Thanks | non_priority | add column info about used storage add column info about the used storage for a project and or an image can be useful to see the big consumers thanks | 0 |
20,548 | 6,047,733,360 | IssuesEvent | 2017-06-12 15:01:47 | phageParser/phageParser | https://api.github.com/repos/phageParser/phageParser | closed | Script to analyze BLAST output from host genome | code good first bug | This is marked as a **good first bug** because, although it sounds complicated, it's computationally not as bad as it sounds - I think. There might be some tricky sections, but if a newcomer is attempting this, I'm available for questions anytime! Just comment in this issue.
### Motivation
Research has suggested that there may be cases when CRISPR systems are used for something besides immunity to foreign DNA - perhaps they could be regulating the host genome, or they might simply be inactive. A clue that one of these things might be happening is if there are spacers that come from their own host genome. To this end, we need functions to (A) BLAST spacers against the host genome and (B) analyze the BLAST output. The first function is described in issue #60 and the second function is described here.
---
### The function
**Input:**
- XML file produced by the BLAST function in issue #60 (example [here](https://github.com/goyalsid/phageParser/blob/master/data/NC_000853.xml)).
- File containing the start and end positions of CRISPR loci in the sequence, which can be found [here](https://github.com/goyalsid/phageParser/blob/master/data/CRISPR_locus_positions.csv). The format of each row in this file is `Accession, CRISPR_ID, start, end`.
- Optional expect value cutoff, default should be 1.
**The function should do the following:**
- Use [BioPython's built-in BLAST parser](http://biopython.org/DIST/docs/tutorial/Tutorial.html#sec:parsing-blast) to parse the XML file produced by BLAST (example in Input section). This is also done in [filterByExpect_all_v2.py](https://github.com/goyalsid/phageParser/blob/master/filterByExpect_all_v2.py), although I've noticed a few mistakes just now so be careful!
- This is the tricky part: differentiate between a match with itself (i.e. the source spacer array) and a match somewhere else in the genome. I think the easiest way might be to run [extract_CRISPRdb.py](https://github.com/goyalsid/phageParser/blob/master/extract_CRISPRdb.py) once at the beginning of the analysis, and then use the start and stop locations of the CRISPR loci as boundaries to exclude from. If there is more than one CRISPR locus in a genome, matches to any of the loci should be considered "CRISPR" matches. This will have to be slightly modified if people are contributing genomes not from CRISPRdb - but this could be solved by first running [CRISPRfinder](http://crispr.u-psud.fr/Server/) on submitted genomes. If a match is suspected to be from the original CRISPR array, the output should mark it as being "CRISPR". If it is suspected to be from a different region of the genome, the output should mark it as being "non-CRISPR".
**Output:**
- A csv file called `accession_self-spacers.csv` (where "accession" is the NCBI accession number, i.e. NC_000853) with the following column headings:
- Query
- Score
- Expect
- QueryStart
- QueryEnd
- SubjectStart
- SubjectEnd
- Source
The "Source" column contains the "CRISPR" or "non-CRISPR" flag. All other column headings are fields in the object that results from the BLAST-parser module.
| 1.0 | Script to analyze BLAST output from host genome - This is marked as a **good first bug** because, although it sounds complicated, it's computationally not as bad as it sounds - I think. There might be some tricky sections, but if a newcomer is attempting this, I'm available for questions anytime! Just comment in this issue.
### Motivation
Research has suggested that there may be cases when CRISPR systems are used for something besides immunity to foreign DNA - perhaps they could be regulating the host genome, or they might simply be inactive. A clue that one of these things might be happening is if there are spacers that come from their own host genome. To this end, we need functions to (A) BLAST spacers against the host genome and (B) analyze the BLAST output. The first function is described in issue #60 and the second function is described here.
---
### The function
**Input:**
- XML file produced by the BLAST function in issue #60 (example [here](https://github.com/goyalsid/phageParser/blob/master/data/NC_000853.xml)).
- File containing the start and end positions of CRISPR loci in the sequence, which can be found [here](https://github.com/goyalsid/phageParser/blob/master/data/CRISPR_locus_positions.csv). The format of each row in this file is `Accession, CRISPR_ID, start, end`.
- Optional expect value cutoff, default should be 1.
**The function should do the following:**
- Use [BioPython's built-in BLAST parser](http://biopython.org/DIST/docs/tutorial/Tutorial.html#sec:parsing-blast) to parse the XML file produced by BLAST (example in Input section). This is also done in [filterByExpect_all_v2.py](https://github.com/goyalsid/phageParser/blob/master/filterByExpect_all_v2.py), although I've noticed a few mistakes just now so be careful!
- This is the tricky part: differentiate between a match with itself (i.e. the source spacer array) and a match somewhere else in the genome. I think the easiest way might be to run [extract_CRISPRdb.py](https://github.com/goyalsid/phageParser/blob/master/extract_CRISPRdb.py) once at the beginning of the analysis, and then use the start and stop locations of the CRISPR loci as boundaries to exclude from. If there is more than one CRISPR locus in a genome, matches to any of the loci should be considered "CRISPR" matches. This will have to be slightly modified if people are contributing genomes not from CRISPRdb - but this could be solved by first running [CRISPRfinder](http://crispr.u-psud.fr/Server/) on submitted genomes. If a match is suspected to be from the original CRISPR array, the output should mark it as being "CRISPR". If it is suspected to be from a different region of the genome, the output should mark it as being "non-CRISPR".
**Output:**
- A csv file called `accession_self-spacers.csv` (where "accession" is the NCBI accession number, i.e. NC_000853) with the following column headings:
- Query
- Score
- Expect
- QueryStart
- QueryEnd
- SubjectStart
- SubjectEnd
- Source
The "Source" column contains the "CRISPR" or "non-CRISPR" flag. All other column headings are fields in the object that results from the BLAST-parser module.
| non_priority | script to analyze blast output from host genome this is marked as a good first bug because although it sounds complicated it s computationally not as bad as it sounds i think there might be some tricky sections but if a newcomer is attempting this i m available for questions anytime just comment in this issue motivation research has suggested that there may be cases when crispr systems are used for something besides immunity to foreign dna perhaps they could be regulating the host genome or they might simply be inactive a clue that one of these things might be happening is if there are spacers that come from their own host genome to this end we need functions to a blast spacers against the host genome and b analyze the blast output the first function is described in issue and the second function is described here the function input xml file produced by the blast function in issue example file containing the start and end positions of crispr loci in the sequence which can be found the format of each row in this file is accession crispr id start end optional expect value cutoff default should be the function should do the following use to parse the xml file produced by blast example in input section this is also done in although i ve noticed a few mistakes just now so be careful this is the tricky part differentiate between a match with itself i e the source spacer array and a match somewhere else in the genome i think the easiest way might be to run once at the beginning of the analysis and then use the start and stop locations of the crispr loci as boundaries to exclude from if there is more than one crispr locus in a genome matches to any of the loci should be considered crispr matches this will have to be slightly modified if people are contributing genomes not from crisprdb but this could be solved by first running on submitted genomes if a match is suspected to be from the original crispr array the output should mark it as being crispr if it is suspected to be from a different region of the genome the output should mark it as being non crispr output a csv file called accession self spacers csv where accession is the ncbi accession number i e nc with the following column headings query score expect querystart queryend subjectstart subjectend source the source column contains the crispr or non crispr flag all other column headings are fields in the object that results from the blast parser module | 0 |
262,475 | 27,951,258,591 | IssuesEvent | 2023-03-24 09:03:00 | Satheesh575555/linux-4.1.15_CVE-2022-45934 | https://api.github.com/repos/Satheesh575555/linux-4.1.15_CVE-2022-45934 | opened | CVE-2022-3643 (High) detected in linuxlinux-4.6 | Mend: dependency security vulnerability | ## CVE-2022-3643 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>linuxlinux-4.6</b></p></summary>
<p>
<p>The Linux Kernel</p>
<p>Library home page: <a href=https://mirrors.edge.kernel.org/pub/linux/kernel/v4.x/?wsslib=linux>https://mirrors.edge.kernel.org/pub/linux/kernel/v4.x/?wsslib=linux</a></p>
<p>Found in HEAD commit: <a href="https://github.com/Satheesh575555/linux-4.1.15_CVE-2022-45934/commit/7c0b143b43394df131d83e9aecb3c5518edc127a">7c0b143b43394df131d83e9aecb3c5518edc127a</a></p>
<p>Found in base branch: <b>main</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 (1)</summary>
<p></p>
<p>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/drivers/net/xen-netback/netback.c</b>
</p>
</details>
<p></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>
Guests can trigger NIC interface reset/abort/crash via netback It is possible for a guest to trigger a NIC interface reset/abort/crash in a Linux based network backend by sending certain kinds of packets. It appears to be an (unwritten?) assumption in the rest of the Linux network stack that packet protocol headers are all contained within the linear section of the SKB and some NICs behave badly if this is not the case. This has been reported to occur with Cisco (enic) and Broadcom NetXtrem II BCM5780 (bnx2x) though it may be an issue with other NICs/drivers as well. In case the frontend is sending requests with split headers, netback will forward those violating above mentioned assumption to the networking core, resulting in said misbehavior.
<p>Publish Date: 2022-12-07
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-3643>CVE-2022-3643</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>10.0</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Changed
- 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://www.linuxkernelcves.com/cves/CVE-2022-3643">https://www.linuxkernelcves.com/cves/CVE-2022-3643</a></p>
<p>Release Date: 2022-12-07</p>
<p>Fix Resolution: v4.9.336,v4.14.302,v4.19.269,v5.4.227,v5.10.159,v5.15.83,v6.0.13,v6.1</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-3643 (High) detected in linuxlinux-4.6 - ## CVE-2022-3643 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>linuxlinux-4.6</b></p></summary>
<p>
<p>The Linux Kernel</p>
<p>Library home page: <a href=https://mirrors.edge.kernel.org/pub/linux/kernel/v4.x/?wsslib=linux>https://mirrors.edge.kernel.org/pub/linux/kernel/v4.x/?wsslib=linux</a></p>
<p>Found in HEAD commit: <a href="https://github.com/Satheesh575555/linux-4.1.15_CVE-2022-45934/commit/7c0b143b43394df131d83e9aecb3c5518edc127a">7c0b143b43394df131d83e9aecb3c5518edc127a</a></p>
<p>Found in base branch: <b>main</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 (1)</summary>
<p></p>
<p>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/drivers/net/xen-netback/netback.c</b>
</p>
</details>
<p></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>
Guests can trigger NIC interface reset/abort/crash via netback It is possible for a guest to trigger a NIC interface reset/abort/crash in a Linux based network backend by sending certain kinds of packets. It appears to be an (unwritten?) assumption in the rest of the Linux network stack that packet protocol headers are all contained within the linear section of the SKB and some NICs behave badly if this is not the case. This has been reported to occur with Cisco (enic) and Broadcom NetXtrem II BCM5780 (bnx2x) though it may be an issue with other NICs/drivers as well. In case the frontend is sending requests with split headers, netback will forward those violating above mentioned assumption to the networking core, resulting in said misbehavior.
<p>Publish Date: 2022-12-07
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-3643>CVE-2022-3643</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>10.0</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Changed
- 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://www.linuxkernelcves.com/cves/CVE-2022-3643">https://www.linuxkernelcves.com/cves/CVE-2022-3643</a></p>
<p>Release Date: 2022-12-07</p>
<p>Fix Resolution: v4.9.336,v4.14.302,v4.19.269,v5.4.227,v5.10.159,v5.15.83,v6.0.13,v6.1</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 linuxlinux cve high severity vulnerability vulnerable library linuxlinux the linux kernel library home page a href found in head commit a href found in base branch main vulnerable source files drivers net xen netback netback c vulnerability details guests can trigger nic interface reset abort crash via netback it is possible for a guest to trigger a nic interface reset abort crash in a linux based network backend by sending certain kinds of packets it appears to be an unwritten assumption in the rest of the linux network stack that packet protocol headers are all contained within the linear section of the skb and some nics behave badly if this is not the case this has been reported to occur with cisco enic and broadcom netxtrem ii though it may be an issue with other nics drivers as well in case the frontend is sending requests with split headers netback will forward those violating above mentioned assumption to the networking core resulting in said misbehavior 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 changed 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 step up your open source security game with mend | 0 |
337,708 | 30,258,431,918 | IssuesEvent | 2023-07-07 06:03:13 | ITISFoundation/osparc-ops-environments | https://api.github.com/repos/ITISFoundation/osparc-ops-environments | closed | Add e2e-ops test: Docker engine version is identical for all nodes | p:mid-prio FAST e2e & test | Actionable item:
In the e2e-ops tests, run `docker node ls` and check the docker engine version. There should always be the same version across all nodes. Alert if there is a version mismatch. | 1.0 | Add e2e-ops test: Docker engine version is identical for all nodes - Actionable item:
In the e2e-ops tests, run `docker node ls` and check the docker engine version. There should always be the same version across all nodes. Alert if there is a version mismatch. | non_priority | add ops test docker engine version is identical for all nodes actionable item in the ops tests run docker node ls and check the docker engine version there should always be the same version across all nodes alert if there is a version mismatch | 0 |
320,136 | 27,420,279,357 | IssuesEvent | 2023-03-01 16:16:05 | unifyai/ivy | https://api.github.com/repos/unifyai/ivy | opened | Fix container.test_container_assert_contains | Sub Task Failing Test | | | |
|---|---|
|tensorflow|<a href="https://github.com/unifyai/ivy/actions/" rel="noopener noreferrer" target="_blank"><img src=https://img.shields.io/badge/-success-success></a>
|torch|<a href="null" rel="noopener noreferrer" target="_blank"><img src=https://img.shields.io/badge/-failure-red></a>
|numpy|<a href="https://github.com/unifyai/ivy/actions/runs/4133150123/jobs/7142729843" rel="noopener noreferrer" target="_blank"><img src=https://img.shields.io/badge/-success-success></a>
|jax|<a href="https://github.com/unifyai/ivy/actions/runs/4133150123/jobs/7142742966" rel="noopener noreferrer" target="_blank"><img src=https://img.shields.io/badge/-success-success></a>
| 1.0 | Fix container.test_container_assert_contains - | | |
|---|---|
|tensorflow|<a href="https://github.com/unifyai/ivy/actions/" rel="noopener noreferrer" target="_blank"><img src=https://img.shields.io/badge/-success-success></a>
|torch|<a href="null" rel="noopener noreferrer" target="_blank"><img src=https://img.shields.io/badge/-failure-red></a>
|numpy|<a href="https://github.com/unifyai/ivy/actions/runs/4133150123/jobs/7142729843" rel="noopener noreferrer" target="_blank"><img src=https://img.shields.io/badge/-success-success></a>
|jax|<a href="https://github.com/unifyai/ivy/actions/runs/4133150123/jobs/7142742966" rel="noopener noreferrer" target="_blank"><img src=https://img.shields.io/badge/-success-success></a>
| non_priority | fix container test container assert contains tensorflow img src torch img src numpy img src jax img src | 0 |
284,907 | 30,963,155,160 | IssuesEvent | 2023-08-08 06:27:02 | Vonage/vonage-dotnet-sdk | https://api.github.com/repos/Vonage/vonage-dotnet-sdk | closed | vonage.server.7.0.4-beta.nupkg: 1 vulnerabilities (highest severity is: 7.5) | wontfix Mend: dependency security vulnerability | <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>vonage.server.7.0.4-beta.nupkg</b></p></summary>
<p></p>
<p>Path to vulnerable library: /home/wss-scanner/.nuget/packages/microsoft.aspnetcore.server.kestrel.transport.sockets/2.2.0/microsoft.aspnetcore.server.kestrel.transport.sockets.2.2.0.nupkg</p>
<p>
<p>Found in HEAD commit: <a href="https://github.com/Vonage/vonage-dotnet-sdk/commit/6de5370f013bbdf6a5489e89446d154d12da705c">6de5370f013bbdf6a5489e89446d154d12da705c</a></p></details>
## Vulnerabilities
| CVE | Severity | <img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS | Dependency | Type | Fixed in (vonage.server.7.0.4-beta.nupkg version) | Remediation Available |
| ------------- | ------------- | ----- | ----- | ----- | ------------- | --- |
| [CVE-2019-0548](https://www.mend.io/vulnerability-database/CVE-2019-0548) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 7.5 | detected in multiple dependencies | Transitive | N/A* | ❌ |
<p>*For some transitive vulnerabilities, there is no version of direct dependency with a fix. Check the "Details" section below to see if there is a version of transitive dependency where vulnerability is fixed.</p>
## Details
<details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> CVE-2019-0548</summary>
### Vulnerable Libraries - <b>microsoft.aspnetcore.server.iisintegration.2.2.0.nupkg</b>, <b>microsoft.aspnetcore.2.2.0.nupkg</b>, <b>microsoft.aspnetcore.server.kestrel.transport.sockets.2.2.0.nupkg</b></p>
<p>
### <b>microsoft.aspnetcore.server.iisintegration.2.2.0.nupkg</b></p>
<p>ASP.NET Core components for working with the IIS AspNetCoreModule.
This package was built from the ...</p>
<p>Library home page: <a href="https://api.nuget.org/packages/microsoft.aspnetcore.server.iisintegration.2.2.0.nupkg">https://api.nuget.org/packages/microsoft.aspnetcore.server.iisintegration.2.2.0.nupkg</a></p>
<p>Path to dependency file: /Vonage.Common.Test/Vonage.Common.Test.csproj</p>
<p>Path to vulnerable library: /home/wss-scanner/.nuget/packages/microsoft.aspnetcore.server.iisintegration/2.2.0/microsoft.aspnetcore.server.iisintegration.2.2.0.nupkg</p>
<p>
Dependency Hierarchy:
- vonage.server.7.0.4-beta.nupkg (Root Library)
- Vonage.Common.Test-1.0.0
- wiremock.net.1.5.31.nupkg
- microsoft.aspnetcore.2.2.0.nupkg
- :x: **microsoft.aspnetcore.server.iisintegration.2.2.0.nupkg** (Vulnerable Library)
### <b>microsoft.aspnetcore.2.2.0.nupkg</b></p>
<p>Microsoft.AspNetCore</p>
<p>Library home page: <a href="https://api.nuget.org/packages/microsoft.aspnetcore.2.2.0.nupkg">https://api.nuget.org/packages/microsoft.aspnetcore.2.2.0.nupkg</a></p>
<p>Path to dependency file: /Vonage.Common.Test/Vonage.Common.Test.csproj</p>
<p>Path to vulnerable library: /home/wss-scanner/.nuget/packages/microsoft.aspnetcore/2.2.0/microsoft.aspnetcore.2.2.0.nupkg</p>
<p>
Dependency Hierarchy:
- vonage.server.7.0.4-beta.nupkg (Root Library)
- Vonage.Common.Test-1.0.0
- wiremock.net.1.5.31.nupkg
- :x: **microsoft.aspnetcore.2.2.0.nupkg** (Vulnerable Library)
### <b>microsoft.aspnetcore.server.kestrel.transport.sockets.2.2.0.nupkg</b></p>
<p>Managed socket transport for the ASP.NET Core Kestrel cross-platform web server.</p>
<p>Library home page: <a href="https://api.nuget.org/packages/microsoft.aspnetcore.server.kestrel.transport.sockets.2.2.0.nupkg">https://api.nuget.org/packages/microsoft.aspnetcore.server.kestrel.transport.sockets.2.2.0.nupkg</a></p>
<p>Path to dependency file: /Vonage.Common.Test/Vonage.Common.Test.csproj</p>
<p>Path to vulnerable library: /home/wss-scanner/.nuget/packages/microsoft.aspnetcore.server.kestrel.transport.sockets/2.2.0/microsoft.aspnetcore.server.kestrel.transport.sockets.2.2.0.nupkg</p>
<p>
Dependency Hierarchy:
- vonage.server.7.0.4-beta.nupkg (Root Library)
- Vonage.Common.Test-1.0.0
- wiremock.net.1.5.31.nupkg
- microsoft.aspnetcore.2.2.0.nupkg
- microsoft.aspnetcore.server.kestrel.2.2.0.nupkg
- :x: **microsoft.aspnetcore.server.kestrel.transport.sockets.2.2.0.nupkg** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/Vonage/vonage-dotnet-sdk/commit/6de5370f013bbdf6a5489e89446d154d12da705c">6de5370f013bbdf6a5489e89446d154d12da705c</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
A denial of service vulnerability exists when ASP.NET Core improperly handles web requests, aka "ASP.NET Core Denial of Service Vulnerability." This affects ASP.NET Core 2.2, ASP.NET Core 2.1. This CVE ID is unique from CVE-2019-0564.
<p>Publish Date: 2019-01-08
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2019-0548>CVE-2019-0548</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>7.5</b>)
<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>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Release Date: 2019-01-08</p>
<p>Fix Resolution: Microsoft.AspNetCore.Server.Kestrel.Transport.Sockets - 2.2.1; Microsoft.AspNetCore.Server.IIS - 2.2.1; Microsoft.AspNetCore.Server.IISIntegration - 2.2.1;Microsoft.AspNetCore.Server.Kestrel.Core - 2.1.7</p>
</p>
<p></p>
</details> | True | vonage.server.7.0.4-beta.nupkg: 1 vulnerabilities (highest severity is: 7.5) - <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>vonage.server.7.0.4-beta.nupkg</b></p></summary>
<p></p>
<p>Path to vulnerable library: /home/wss-scanner/.nuget/packages/microsoft.aspnetcore.server.kestrel.transport.sockets/2.2.0/microsoft.aspnetcore.server.kestrel.transport.sockets.2.2.0.nupkg</p>
<p>
<p>Found in HEAD commit: <a href="https://github.com/Vonage/vonage-dotnet-sdk/commit/6de5370f013bbdf6a5489e89446d154d12da705c">6de5370f013bbdf6a5489e89446d154d12da705c</a></p></details>
## Vulnerabilities
| CVE | Severity | <img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS | Dependency | Type | Fixed in (vonage.server.7.0.4-beta.nupkg version) | Remediation Available |
| ------------- | ------------- | ----- | ----- | ----- | ------------- | --- |
| [CVE-2019-0548](https://www.mend.io/vulnerability-database/CVE-2019-0548) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 7.5 | detected in multiple dependencies | Transitive | N/A* | ❌ |
<p>*For some transitive vulnerabilities, there is no version of direct dependency with a fix. Check the "Details" section below to see if there is a version of transitive dependency where vulnerability is fixed.</p>
## Details
<details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> CVE-2019-0548</summary>
### Vulnerable Libraries - <b>microsoft.aspnetcore.server.iisintegration.2.2.0.nupkg</b>, <b>microsoft.aspnetcore.2.2.0.nupkg</b>, <b>microsoft.aspnetcore.server.kestrel.transport.sockets.2.2.0.nupkg</b></p>
<p>
### <b>microsoft.aspnetcore.server.iisintegration.2.2.0.nupkg</b></p>
<p>ASP.NET Core components for working with the IIS AspNetCoreModule.
This package was built from the ...</p>
<p>Library home page: <a href="https://api.nuget.org/packages/microsoft.aspnetcore.server.iisintegration.2.2.0.nupkg">https://api.nuget.org/packages/microsoft.aspnetcore.server.iisintegration.2.2.0.nupkg</a></p>
<p>Path to dependency file: /Vonage.Common.Test/Vonage.Common.Test.csproj</p>
<p>Path to vulnerable library: /home/wss-scanner/.nuget/packages/microsoft.aspnetcore.server.iisintegration/2.2.0/microsoft.aspnetcore.server.iisintegration.2.2.0.nupkg</p>
<p>
Dependency Hierarchy:
- vonage.server.7.0.4-beta.nupkg (Root Library)
- Vonage.Common.Test-1.0.0
- wiremock.net.1.5.31.nupkg
- microsoft.aspnetcore.2.2.0.nupkg
- :x: **microsoft.aspnetcore.server.iisintegration.2.2.0.nupkg** (Vulnerable Library)
### <b>microsoft.aspnetcore.2.2.0.nupkg</b></p>
<p>Microsoft.AspNetCore</p>
<p>Library home page: <a href="https://api.nuget.org/packages/microsoft.aspnetcore.2.2.0.nupkg">https://api.nuget.org/packages/microsoft.aspnetcore.2.2.0.nupkg</a></p>
<p>Path to dependency file: /Vonage.Common.Test/Vonage.Common.Test.csproj</p>
<p>Path to vulnerable library: /home/wss-scanner/.nuget/packages/microsoft.aspnetcore/2.2.0/microsoft.aspnetcore.2.2.0.nupkg</p>
<p>
Dependency Hierarchy:
- vonage.server.7.0.4-beta.nupkg (Root Library)
- Vonage.Common.Test-1.0.0
- wiremock.net.1.5.31.nupkg
- :x: **microsoft.aspnetcore.2.2.0.nupkg** (Vulnerable Library)
### <b>microsoft.aspnetcore.server.kestrel.transport.sockets.2.2.0.nupkg</b></p>
<p>Managed socket transport for the ASP.NET Core Kestrel cross-platform web server.</p>
<p>Library home page: <a href="https://api.nuget.org/packages/microsoft.aspnetcore.server.kestrel.transport.sockets.2.2.0.nupkg">https://api.nuget.org/packages/microsoft.aspnetcore.server.kestrel.transport.sockets.2.2.0.nupkg</a></p>
<p>Path to dependency file: /Vonage.Common.Test/Vonage.Common.Test.csproj</p>
<p>Path to vulnerable library: /home/wss-scanner/.nuget/packages/microsoft.aspnetcore.server.kestrel.transport.sockets/2.2.0/microsoft.aspnetcore.server.kestrel.transport.sockets.2.2.0.nupkg</p>
<p>
Dependency Hierarchy:
- vonage.server.7.0.4-beta.nupkg (Root Library)
- Vonage.Common.Test-1.0.0
- wiremock.net.1.5.31.nupkg
- microsoft.aspnetcore.2.2.0.nupkg
- microsoft.aspnetcore.server.kestrel.2.2.0.nupkg
- :x: **microsoft.aspnetcore.server.kestrel.transport.sockets.2.2.0.nupkg** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/Vonage/vonage-dotnet-sdk/commit/6de5370f013bbdf6a5489e89446d154d12da705c">6de5370f013bbdf6a5489e89446d154d12da705c</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
A denial of service vulnerability exists when ASP.NET Core improperly handles web requests, aka "ASP.NET Core Denial of Service Vulnerability." This affects ASP.NET Core 2.2, ASP.NET Core 2.1. This CVE ID is unique from CVE-2019-0564.
<p>Publish Date: 2019-01-08
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2019-0548>CVE-2019-0548</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>7.5</b>)
<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>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Release Date: 2019-01-08</p>
<p>Fix Resolution: Microsoft.AspNetCore.Server.Kestrel.Transport.Sockets - 2.2.1; Microsoft.AspNetCore.Server.IIS - 2.2.1; Microsoft.AspNetCore.Server.IISIntegration - 2.2.1;Microsoft.AspNetCore.Server.Kestrel.Core - 2.1.7</p>
</p>
<p></p>
</details> | non_priority | vonage server beta nupkg vulnerabilities highest severity is vulnerable library vonage server beta nupkg path to vulnerable library home wss scanner nuget packages microsoft aspnetcore server kestrel transport sockets microsoft aspnetcore server kestrel transport sockets nupkg found in head commit a href vulnerabilities cve severity cvss dependency type fixed in vonage server beta nupkg version remediation available high detected in multiple dependencies transitive n a for some transitive vulnerabilities there is no version of direct dependency with a fix check the details section below to see if there is a version of transitive dependency where vulnerability is fixed details cve vulnerable libraries microsoft aspnetcore server iisintegration nupkg microsoft aspnetcore nupkg microsoft aspnetcore server kestrel transport sockets nupkg microsoft aspnetcore server iisintegration nupkg asp net core components for working with the iis aspnetcoremodule this package was built from the library home page a href path to dependency file vonage common test vonage common test csproj path to vulnerable library home wss scanner nuget packages microsoft aspnetcore server iisintegration microsoft aspnetcore server iisintegration nupkg dependency hierarchy vonage server beta nupkg root library vonage common test wiremock net nupkg microsoft aspnetcore nupkg x microsoft aspnetcore server iisintegration nupkg vulnerable library microsoft aspnetcore nupkg microsoft aspnetcore library home page a href path to dependency file vonage common test vonage common test csproj path to vulnerable library home wss scanner nuget packages microsoft aspnetcore microsoft aspnetcore nupkg dependency hierarchy vonage server beta nupkg root library vonage common test wiremock net nupkg x microsoft aspnetcore nupkg vulnerable library microsoft aspnetcore server kestrel transport sockets nupkg managed socket transport for the asp net core kestrel cross platform web server library home page a href path to dependency file vonage common test vonage common test csproj path to vulnerable library home wss scanner nuget packages microsoft aspnetcore server kestrel transport sockets microsoft aspnetcore server kestrel transport sockets nupkg dependency hierarchy vonage server beta nupkg root library vonage common test wiremock net nupkg microsoft aspnetcore nupkg microsoft aspnetcore server kestrel nupkg x microsoft aspnetcore server kestrel transport sockets nupkg vulnerable library found in head commit a href found in base branch main vulnerability details a denial of service vulnerability exists when asp net core improperly handles web requests aka asp net core denial of service vulnerability this affects asp net core asp net core this cve id is unique from cve 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 microsoft aspnetcore server kestrel transport sockets microsoft aspnetcore server iis microsoft aspnetcore server iisintegration microsoft aspnetcore server kestrel core | 0 |
108,472 | 16,777,917,365 | IssuesEvent | 2021-06-15 01:18:57 | swagger-api/swagger-core | https://api.github.com/repos/swagger-api/swagger-core | opened | CVE-2021-28169 (Medium) detected in multiple libraries | security vulnerability | ## CVE-2021-28169 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>jetty-server-9.4.39.v20210325.jar</b>, <b>jetty-servlets-9.4.39.v20210325.jar</b>, <b>jetty-http-9.4.39.v20210325.jar</b></p></summary>
<p>
<details><summary><b>jetty-server-9.4.39.v20210325.jar</b></p></summary>
<p>The core jetty server artifact.</p>
<p>Library home page: <a href="https://eclipse.org/jetty">https://eclipse.org/jetty</a></p>
<p>Path to dependency file: swagger-core/modules/swagger-gradle-plugin/build.gradle</p>
<p>Path to vulnerable library: swagger-core/modules/swagger-maven-plugin/target/lib/jetty-server-9.4.39.v20210325.jar,canner/.m2/repository/org/eclipse/jetty/jetty-server/9.4.39.v20210325/jetty-server-9.4.39.v20210325.jar,/home/wss-scanner/.m2/repository/org/eclipse/jetty/jetty-server/9.4.39.v20210325/jetty-server-9.4.39.v20210325.jar</p>
<p>
Dependency Hierarchy:
- :x: **jetty-server-9.4.39.v20210325.jar** (Vulnerable Library)
</details>
<details><summary><b>jetty-servlets-9.4.39.v20210325.jar</b></p></summary>
<p>Utility Servlets from Jetty</p>
<p>Library home page: <a href="https://eclipse.org/jetty">https://eclipse.org/jetty</a></p>
<p>Path to dependency file: swagger-core/modules/swagger-gradle-plugin/build.gradle</p>
<p>Path to vulnerable library: swagger-core/modules/swagger-maven-plugin/target/lib/jetty-servlets-9.4.39.v20210325.jar,canner/.m2/repository/org/eclipse/jetty/jetty-servlets/9.4.39.v20210325/jetty-servlets-9.4.39.v20210325.jar</p>
<p>
Dependency Hierarchy:
- :x: **jetty-servlets-9.4.39.v20210325.jar** (Vulnerable Library)
</details>
<details><summary><b>jetty-http-9.4.39.v20210325.jar</b></p></summary>
<p></p>
<p>Library home page: <a href="https://eclipse.org/jetty">https://eclipse.org/jetty</a></p>
<p>Path to dependency file: swagger-core/modules/swagger-gradle-plugin/build.gradle</p>
<p>Path to vulnerable library: swagger-core/modules/swagger-maven-plugin/target/lib/jetty-http-9.4.39.v20210325.jar,/home/wss-scanner/.m2/repository/org/eclipse/jetty/jetty-http/9.4.39.v20210325/jetty-http-9.4.39.v20210325.jar</p>
<p>
Dependency Hierarchy:
- jetty-server-9.4.39.v20210325.jar (Root Library)
- :x: **jetty-http-9.4.39.v20210325.jar** (Vulnerable Library)
</details>
<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>
For Eclipse Jetty versions <= 9.4.40, <= 10.0.2, <= 11.0.2, it is possible for requests to the ConcatServlet with a doubly encoded path to access protected resources within the WEB-INF directory. For example a request to `/concat?/%2557EB-INF/web.xml` can retrieve the web.xml file. This can reveal sensitive information regarding the implementation of a web application.
<p>Publish Date: 2021-06-09
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-28169>CVE-2021-28169</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.3</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: Low
- 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/eclipse/jetty.project/security/advisories/GHSA-gwcr-j4wh-j3cq">https://github.com/eclipse/jetty.project/security/advisories/GHSA-gwcr-j4wh-j3cq</a></p>
<p>Release Date: 2021-06-09</p>
<p>Fix Resolution: org.eclipse.jetty:jetty-runner:9.4.41.v20210516, 10.0.3, 11.0.3, org.eclipse.jetty:jetty-http:9.4.41.v20210516, 10.0.3, 11.0.3,org.eclipse.jetty:jetty-servlets:9.4.41.v20210516, 10.0.3, 11.0.3, org.eclipse.jetty:jetty-server:9.4.41.v20210516, 10.0.3, 11.0.3</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":false,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"Java","groupId":"org.eclipse.jetty","packageName":"jetty-server","packageVersion":"9.4.39.v20210325","packageFilePaths":["/modules/swagger-gradle-plugin/build.gradle"],"isTransitiveDependency":false,"dependencyTree":"org.eclipse.jetty:jetty-server:9.4.39.v20210325","isMinimumFixVersionAvailable":true,"minimumFixVersion":"org.eclipse.jetty:jetty-runner:9.4.41.v20210516, 10.0.3, 11.0.3, org.eclipse.jetty:jetty-http:9.4.41.v20210516, 10.0.3, 11.0.3,org.eclipse.jetty:jetty-servlets:9.4.41.v20210516, 10.0.3, 11.0.3, org.eclipse.jetty:jetty-server:9.4.41.v20210516, 10.0.3, 11.0.3"},{"packageType":"Java","groupId":"org.eclipse.jetty","packageName":"jetty-servlets","packageVersion":"9.4.39.v20210325","packageFilePaths":["/modules/swagger-gradle-plugin/build.gradle"],"isTransitiveDependency":false,"dependencyTree":"org.eclipse.jetty:jetty-servlets:9.4.39.v20210325","isMinimumFixVersionAvailable":true,"minimumFixVersion":"org.eclipse.jetty:jetty-runner:9.4.41.v20210516, 10.0.3, 11.0.3, org.eclipse.jetty:jetty-http:9.4.41.v20210516, 10.0.3, 11.0.3,org.eclipse.jetty:jetty-servlets:9.4.41.v20210516, 10.0.3, 11.0.3, org.eclipse.jetty:jetty-server:9.4.41.v20210516, 10.0.3, 11.0.3"},{"packageType":"Java","groupId":"org.eclipse.jetty","packageName":"jetty-http","packageVersion":"9.4.39.v20210325","packageFilePaths":["/modules/swagger-gradle-plugin/build.gradle"],"isTransitiveDependency":true,"dependencyTree":"org.eclipse.jetty:jetty-server:9.4.39.v20210325;org.eclipse.jetty:jetty-http:9.4.39.v20210325","isMinimumFixVersionAvailable":true,"minimumFixVersion":"org.eclipse.jetty:jetty-runner:9.4.41.v20210516, 10.0.3, 11.0.3, org.eclipse.jetty:jetty-http:9.4.41.v20210516, 10.0.3, 11.0.3,org.eclipse.jetty:jetty-servlets:9.4.41.v20210516, 10.0.3, 11.0.3, org.eclipse.jetty:jetty-server:9.4.41.v20210516, 10.0.3, 11.0.3"}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2021-28169","vulnerabilityDetails":"For Eclipse Jetty versions \u003c\u003d 9.4.40, \u003c\u003d 10.0.2, \u003c\u003d 11.0.2, it is possible for requests to the ConcatServlet with a doubly encoded path to access protected resources within the WEB-INF directory. For example a request to `/concat?/%2557EB-INF/web.xml` can retrieve the web.xml file. This can reveal sensitive information regarding the implementation of a web application.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-28169","cvss3Severity":"medium","cvss3Score":"5.3","cvss3Metrics":{"A":"None","AC":"Low","PR":"None","S":"Unchanged","C":"Low","UI":"None","AV":"Network","I":"None"},"extraData":{}}</REMEDIATE> --> | True | CVE-2021-28169 (Medium) detected in multiple libraries - ## CVE-2021-28169 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>jetty-server-9.4.39.v20210325.jar</b>, <b>jetty-servlets-9.4.39.v20210325.jar</b>, <b>jetty-http-9.4.39.v20210325.jar</b></p></summary>
<p>
<details><summary><b>jetty-server-9.4.39.v20210325.jar</b></p></summary>
<p>The core jetty server artifact.</p>
<p>Library home page: <a href="https://eclipse.org/jetty">https://eclipse.org/jetty</a></p>
<p>Path to dependency file: swagger-core/modules/swagger-gradle-plugin/build.gradle</p>
<p>Path to vulnerable library: swagger-core/modules/swagger-maven-plugin/target/lib/jetty-server-9.4.39.v20210325.jar,canner/.m2/repository/org/eclipse/jetty/jetty-server/9.4.39.v20210325/jetty-server-9.4.39.v20210325.jar,/home/wss-scanner/.m2/repository/org/eclipse/jetty/jetty-server/9.4.39.v20210325/jetty-server-9.4.39.v20210325.jar</p>
<p>
Dependency Hierarchy:
- :x: **jetty-server-9.4.39.v20210325.jar** (Vulnerable Library)
</details>
<details><summary><b>jetty-servlets-9.4.39.v20210325.jar</b></p></summary>
<p>Utility Servlets from Jetty</p>
<p>Library home page: <a href="https://eclipse.org/jetty">https://eclipse.org/jetty</a></p>
<p>Path to dependency file: swagger-core/modules/swagger-gradle-plugin/build.gradle</p>
<p>Path to vulnerable library: swagger-core/modules/swagger-maven-plugin/target/lib/jetty-servlets-9.4.39.v20210325.jar,canner/.m2/repository/org/eclipse/jetty/jetty-servlets/9.4.39.v20210325/jetty-servlets-9.4.39.v20210325.jar</p>
<p>
Dependency Hierarchy:
- :x: **jetty-servlets-9.4.39.v20210325.jar** (Vulnerable Library)
</details>
<details><summary><b>jetty-http-9.4.39.v20210325.jar</b></p></summary>
<p></p>
<p>Library home page: <a href="https://eclipse.org/jetty">https://eclipse.org/jetty</a></p>
<p>Path to dependency file: swagger-core/modules/swagger-gradle-plugin/build.gradle</p>
<p>Path to vulnerable library: swagger-core/modules/swagger-maven-plugin/target/lib/jetty-http-9.4.39.v20210325.jar,/home/wss-scanner/.m2/repository/org/eclipse/jetty/jetty-http/9.4.39.v20210325/jetty-http-9.4.39.v20210325.jar</p>
<p>
Dependency Hierarchy:
- jetty-server-9.4.39.v20210325.jar (Root Library)
- :x: **jetty-http-9.4.39.v20210325.jar** (Vulnerable Library)
</details>
<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>
For Eclipse Jetty versions <= 9.4.40, <= 10.0.2, <= 11.0.2, it is possible for requests to the ConcatServlet with a doubly encoded path to access protected resources within the WEB-INF directory. For example a request to `/concat?/%2557EB-INF/web.xml` can retrieve the web.xml file. This can reveal sensitive information regarding the implementation of a web application.
<p>Publish Date: 2021-06-09
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-28169>CVE-2021-28169</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.3</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: Low
- 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/eclipse/jetty.project/security/advisories/GHSA-gwcr-j4wh-j3cq">https://github.com/eclipse/jetty.project/security/advisories/GHSA-gwcr-j4wh-j3cq</a></p>
<p>Release Date: 2021-06-09</p>
<p>Fix Resolution: org.eclipse.jetty:jetty-runner:9.4.41.v20210516, 10.0.3, 11.0.3, org.eclipse.jetty:jetty-http:9.4.41.v20210516, 10.0.3, 11.0.3,org.eclipse.jetty:jetty-servlets:9.4.41.v20210516, 10.0.3, 11.0.3, org.eclipse.jetty:jetty-server:9.4.41.v20210516, 10.0.3, 11.0.3</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":false,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"Java","groupId":"org.eclipse.jetty","packageName":"jetty-server","packageVersion":"9.4.39.v20210325","packageFilePaths":["/modules/swagger-gradle-plugin/build.gradle"],"isTransitiveDependency":false,"dependencyTree":"org.eclipse.jetty:jetty-server:9.4.39.v20210325","isMinimumFixVersionAvailable":true,"minimumFixVersion":"org.eclipse.jetty:jetty-runner:9.4.41.v20210516, 10.0.3, 11.0.3, org.eclipse.jetty:jetty-http:9.4.41.v20210516, 10.0.3, 11.0.3,org.eclipse.jetty:jetty-servlets:9.4.41.v20210516, 10.0.3, 11.0.3, org.eclipse.jetty:jetty-server:9.4.41.v20210516, 10.0.3, 11.0.3"},{"packageType":"Java","groupId":"org.eclipse.jetty","packageName":"jetty-servlets","packageVersion":"9.4.39.v20210325","packageFilePaths":["/modules/swagger-gradle-plugin/build.gradle"],"isTransitiveDependency":false,"dependencyTree":"org.eclipse.jetty:jetty-servlets:9.4.39.v20210325","isMinimumFixVersionAvailable":true,"minimumFixVersion":"org.eclipse.jetty:jetty-runner:9.4.41.v20210516, 10.0.3, 11.0.3, org.eclipse.jetty:jetty-http:9.4.41.v20210516, 10.0.3, 11.0.3,org.eclipse.jetty:jetty-servlets:9.4.41.v20210516, 10.0.3, 11.0.3, org.eclipse.jetty:jetty-server:9.4.41.v20210516, 10.0.3, 11.0.3"},{"packageType":"Java","groupId":"org.eclipse.jetty","packageName":"jetty-http","packageVersion":"9.4.39.v20210325","packageFilePaths":["/modules/swagger-gradle-plugin/build.gradle"],"isTransitiveDependency":true,"dependencyTree":"org.eclipse.jetty:jetty-server:9.4.39.v20210325;org.eclipse.jetty:jetty-http:9.4.39.v20210325","isMinimumFixVersionAvailable":true,"minimumFixVersion":"org.eclipse.jetty:jetty-runner:9.4.41.v20210516, 10.0.3, 11.0.3, org.eclipse.jetty:jetty-http:9.4.41.v20210516, 10.0.3, 11.0.3,org.eclipse.jetty:jetty-servlets:9.4.41.v20210516, 10.0.3, 11.0.3, org.eclipse.jetty:jetty-server:9.4.41.v20210516, 10.0.3, 11.0.3"}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2021-28169","vulnerabilityDetails":"For Eclipse Jetty versions \u003c\u003d 9.4.40, \u003c\u003d 10.0.2, \u003c\u003d 11.0.2, it is possible for requests to the ConcatServlet with a doubly encoded path to access protected resources within the WEB-INF directory. For example a request to `/concat?/%2557EB-INF/web.xml` can retrieve the web.xml file. This can reveal sensitive information regarding the implementation of a web application.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-28169","cvss3Severity":"medium","cvss3Score":"5.3","cvss3Metrics":{"A":"None","AC":"Low","PR":"None","S":"Unchanged","C":"Low","UI":"None","AV":"Network","I":"None"},"extraData":{}}</REMEDIATE> --> | non_priority | cve medium detected in multiple libraries cve medium severity vulnerability vulnerable libraries jetty server jar jetty servlets jar jetty http jar jetty server jar the core jetty server artifact library home page a href path to dependency file swagger core modules swagger gradle plugin build gradle path to vulnerable library swagger core modules swagger maven plugin target lib jetty server jar canner repository org eclipse jetty jetty server jetty server jar home wss scanner repository org eclipse jetty jetty server jetty server jar dependency hierarchy x jetty server jar vulnerable library jetty servlets jar utility servlets from jetty library home page a href path to dependency file swagger core modules swagger gradle plugin build gradle path to vulnerable library swagger core modules swagger maven plugin target lib jetty servlets jar canner repository org eclipse jetty jetty servlets jetty servlets jar dependency hierarchy x jetty servlets jar vulnerable library jetty http jar library home page a href path to dependency file swagger core modules swagger gradle plugin build gradle path to vulnerable library swagger core modules swagger maven plugin target lib jetty http jar home wss scanner repository org eclipse jetty jetty http jetty http jar dependency hierarchy jetty server jar root library x jetty http jar vulnerable library found in base branch master vulnerability details for eclipse jetty versions it is possible for requests to the concatservlet with a doubly encoded path to access protected resources within the web inf directory for example a request to concat inf web xml can retrieve the web xml file this can reveal sensitive information regarding the implementation of a web application 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 low 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 org eclipse jetty jetty runner org eclipse jetty jetty http org eclipse jetty jetty servlets org eclipse jetty jetty server isopenpronvulnerability false ispackagebased true isdefaultbranch true packages istransitivedependency false dependencytree org eclipse jetty jetty server isminimumfixversionavailable true minimumfixversion org eclipse jetty jetty runner org eclipse jetty jetty http org eclipse jetty jetty servlets org eclipse jetty jetty server packagetype java groupid org eclipse jetty packagename jetty servlets packageversion packagefilepaths istransitivedependency false dependencytree org eclipse jetty jetty servlets isminimumfixversionavailable true minimumfixversion org eclipse jetty jetty runner org eclipse jetty jetty http org eclipse jetty jetty servlets org eclipse jetty jetty server packagetype java groupid org eclipse jetty packagename jetty http packageversion packagefilepaths istransitivedependency true dependencytree org eclipse jetty jetty server org eclipse jetty jetty http isminimumfixversionavailable true minimumfixversion org eclipse jetty jetty runner org eclipse jetty jetty http org eclipse jetty jetty servlets org eclipse jetty jetty server basebranches vulnerabilityidentifier cve vulnerabilitydetails for eclipse jetty versions it is possible for requests to the concatservlet with a doubly encoded path to access protected resources within the web inf directory for example a request to concat inf web xml can retrieve the web xml file this can reveal sensitive information regarding the implementation of a web application vulnerabilityurl | 0 |
29,655 | 24,140,874,658 | IssuesEvent | 2022-09-21 14:45:02 | WordPress/performance | https://api.github.com/repos/WordPress/performance | closed | Readme changelog command is broken | [Type] Bug Infrastructure Needs Triage | ## Bug Description
When running `npm run readme -- -m "1.5.0"` earlier to prepare the 1.5.0 release, I received an error causing the changelog to not be generated:
```
TypeError: Octokit is not a constructor
at getChangelog (.../performance/bin/plugin/commands/changelog.js:268:18)
at updateReadme (.../performance/bin/plugin/commands/readme.js:158:28)
at processTicksAndRejections (internal/process/task_queues.js:95:5)
at async exports.handler (.../performance/bin/plugin/commands/readme.js:54:2)
at async Command.<anonymous> (.../performance/bin/plugin/cli.js:18:4)
```
Please test running it on your side as well. If this is a consistent error, something broke (possibly during the recent dependency update in #511) and we need to fix it.
| 1.0 | Readme changelog command is broken - ## Bug Description
When running `npm run readme -- -m "1.5.0"` earlier to prepare the 1.5.0 release, I received an error causing the changelog to not be generated:
```
TypeError: Octokit is not a constructor
at getChangelog (.../performance/bin/plugin/commands/changelog.js:268:18)
at updateReadme (.../performance/bin/plugin/commands/readme.js:158:28)
at processTicksAndRejections (internal/process/task_queues.js:95:5)
at async exports.handler (.../performance/bin/plugin/commands/readme.js:54:2)
at async Command.<anonymous> (.../performance/bin/plugin/cli.js:18:4)
```
Please test running it on your side as well. If this is a consistent error, something broke (possibly during the recent dependency update in #511) and we need to fix it.
| non_priority | readme changelog command is broken bug description when running npm run readme m earlier to prepare the release i received an error causing the changelog to not be generated typeerror octokit is not a constructor at getchangelog performance bin plugin commands changelog js at updatereadme performance bin plugin commands readme js at processticksandrejections internal process task queues js at async exports handler performance bin plugin commands readme js at async command performance bin plugin cli js please test running it on your side as well if this is a consistent error something broke possibly during the recent dependency update in and we need to fix it | 0 |
335,056 | 30,008,612,102 | IssuesEvent | 2023-06-26 13:58:30 | eclipse-openj9/openj9 | https://api.github.com/repos/eclipse-openj9/openj9 | opened | testJCMMXBeanRemote crash vmState=0x00020002 | comp:gc test failure segfault | https://openj9-jenkins.osuosl.org/job/Test_openjdk20_j9_extended.functional_x86-64_windows_Nightly_testList_0/85
testJCMMXBeanRemote_1 `-Xjit -Xgcpolicy:optthruput -Xnocompressedrefs`
https://openj9-artifactory.osuosl.org/artifactory/ci-openj9/Test/Test_openjdk20_j9_extended.functional_x86-64_windows_Nightly_testList_0/85/functional_test_output.tar.gz
```
10:48:54 Type=Segmentation error vmState=0x00020002
10:48:54 Windows_ExceptionCode=c0000005 J9Generic_Signal=00000004 ExceptionAddress=00007FFDD196BEBB ContextFlags=0010005f
10:48:54 Handler1=00007FFDD23AAFF0 Handler2=00007FFDDD0EABA0 InaccessibleReadAddress=0000000000000000
10:48:54 RDI=00007FFDD1B3B730 RSI=00007FFDD1B3B6E8 RAX=00000233FDD6F530 RBX=00007FF3D30E5C68
10:48:54 RCX=00000233FDD574E0 RDX=0000000099669966 R8=00000233FD478230 R9=000002339D4C3B58
10:48:54 R10=0000000000002000 R11=00000233FCE06438 R12=00007FFDD1A170D0 R13=000002339D4C3918
10:48:54 R14=00000233FD478250 R15=0000000000000000
10:48:54 RIP=00007FFDD196BEBB RSP=00000034B4F7F440 RBP=00000034B4F7F540 EFLAGS=0000000000010246
10:48:54 FS=0053 ES=002B DS=002B
10:48:54 XMM0 0000000000000000 (f: 0.000000, d: 0.000000e+00)
10:48:54 XMM1 0000000000000000 (f: 0.000000, d: 0.000000e+00)
10:48:54 XMM2 0000000000000000 (f: 0.000000, d: 0.000000e+00)
10:48:54 XMM3 0000000000000000 (f: 0.000000, d: 0.000000e+00)
10:48:54 XMM4 0000000000000000 (f: 0.000000, d: 0.000000e+00)
10:48:54 XMM5 0000000000000000 (f: 0.000000, d: 0.000000e+00)
10:48:54 XMM6 0000000000000000 (f: 0.000000, d: 0.000000e+00)
10:48:54 XMM7 0000000000000000 (f: 0.000000, d: 0.000000e+00)
10:48:54 XMM8 0000000000000000 (f: 0.000000, d: 0.000000e+00)
10:48:54 XMM9 0000000000000000 (f: 0.000000, d: 0.000000e+00)
10:48:54 XMM10 0000000000000000 (f: 0.000000, d: 0.000000e+00)
10:48:54 XMM11 0000000000000000 (f: 0.000000, d: 0.000000e+00)
10:48:54 XMM12 0000000000000000 (f: 0.000000, d: 0.000000e+00)
10:48:54 XMM13 0000000000000000 (f: 0.000000, d: 0.000000e+00)
10:48:54 XMM14 0000000000000000 (f: 0.000000, d: 0.000000e+00)
10:48:54 XMM15 0000000000000000 (f: 0.000000, d: 0.000000e+00)
10:48:54 Module=F:\Users\jenkins\workspace\Test_openjdk20_j9_extended.functional_x86-64_windows_Nightly_testList_0\openjdkbinary\j2sdk-image\bin\default\j9gc_full29.dll
10:48:54 Module_base_address=00007FFDD1810000 Offset_in_DLL=000000000015bebb
10:48:54 Target=2_90_20230624_89 (Windows Server 2019 10.0 build 17763)
10:48:54 CPU=amd64 (8 logical CPUs) (0x3ffb9c000 RAM)
10:48:54 ----------- Stack Backtrace -----------
10:48:54 J9VMDllMain+0x15aeab (0x00007FFDD196BEBB [j9gc_full29+0x15bebb])
10:48:54 J9VMDllMain+0x15a355 (0x00007FFDD196B365 [j9gc_full29+0x15b365])
10:48:54 J9VMDllMain+0x1cf266 (0x00007FFDD19E0276 [j9gc_full29+0x1d0276])
10:48:54 J9VMDllMain+0x14ed2d (0x00007FFDD195FD3D [j9gc_full29+0x14fd3d])
10:48:54 J9VMDllMain+0x14fec1 (0x00007FFDD1960ED1 [j9gc_full29+0x150ed1])
10:48:54 j9port_isCompatible+0x1a1bb (0x00007FFDDD0ECD9B [j9prt29+0x1cd9b])
10:48:54 J9VMDllMain+0x15001b (0x00007FFDD196102B [j9gc_full29+0x15102b])
10:48:54 omrthread_get_category+0xa42 (0x00007FFDDD254242 [j9thr29+0x4242])
10:48:54 _o_exp+0x5a (0x00007FFDE6A7268A [ucrtbase+0x2268a])
10:48:54 BaseThreadInitThunk+0x14 (0x00007FFDEA687AC4 [KERNEL32+0x17ac4])
10:48:54 RtlUserThreadStart+0x21 (0x00007FFDEAA1A351 [ntdll+0x5a351])
```
There are other issues with vmState=0x00020002, this may be a dup. | 1.0 | testJCMMXBeanRemote crash vmState=0x00020002 - https://openj9-jenkins.osuosl.org/job/Test_openjdk20_j9_extended.functional_x86-64_windows_Nightly_testList_0/85
testJCMMXBeanRemote_1 `-Xjit -Xgcpolicy:optthruput -Xnocompressedrefs`
https://openj9-artifactory.osuosl.org/artifactory/ci-openj9/Test/Test_openjdk20_j9_extended.functional_x86-64_windows_Nightly_testList_0/85/functional_test_output.tar.gz
```
10:48:54 Type=Segmentation error vmState=0x00020002
10:48:54 Windows_ExceptionCode=c0000005 J9Generic_Signal=00000004 ExceptionAddress=00007FFDD196BEBB ContextFlags=0010005f
10:48:54 Handler1=00007FFDD23AAFF0 Handler2=00007FFDDD0EABA0 InaccessibleReadAddress=0000000000000000
10:48:54 RDI=00007FFDD1B3B730 RSI=00007FFDD1B3B6E8 RAX=00000233FDD6F530 RBX=00007FF3D30E5C68
10:48:54 RCX=00000233FDD574E0 RDX=0000000099669966 R8=00000233FD478230 R9=000002339D4C3B58
10:48:54 R10=0000000000002000 R11=00000233FCE06438 R12=00007FFDD1A170D0 R13=000002339D4C3918
10:48:54 R14=00000233FD478250 R15=0000000000000000
10:48:54 RIP=00007FFDD196BEBB RSP=00000034B4F7F440 RBP=00000034B4F7F540 EFLAGS=0000000000010246
10:48:54 FS=0053 ES=002B DS=002B
10:48:54 XMM0 0000000000000000 (f: 0.000000, d: 0.000000e+00)
10:48:54 XMM1 0000000000000000 (f: 0.000000, d: 0.000000e+00)
10:48:54 XMM2 0000000000000000 (f: 0.000000, d: 0.000000e+00)
10:48:54 XMM3 0000000000000000 (f: 0.000000, d: 0.000000e+00)
10:48:54 XMM4 0000000000000000 (f: 0.000000, d: 0.000000e+00)
10:48:54 XMM5 0000000000000000 (f: 0.000000, d: 0.000000e+00)
10:48:54 XMM6 0000000000000000 (f: 0.000000, d: 0.000000e+00)
10:48:54 XMM7 0000000000000000 (f: 0.000000, d: 0.000000e+00)
10:48:54 XMM8 0000000000000000 (f: 0.000000, d: 0.000000e+00)
10:48:54 XMM9 0000000000000000 (f: 0.000000, d: 0.000000e+00)
10:48:54 XMM10 0000000000000000 (f: 0.000000, d: 0.000000e+00)
10:48:54 XMM11 0000000000000000 (f: 0.000000, d: 0.000000e+00)
10:48:54 XMM12 0000000000000000 (f: 0.000000, d: 0.000000e+00)
10:48:54 XMM13 0000000000000000 (f: 0.000000, d: 0.000000e+00)
10:48:54 XMM14 0000000000000000 (f: 0.000000, d: 0.000000e+00)
10:48:54 XMM15 0000000000000000 (f: 0.000000, d: 0.000000e+00)
10:48:54 Module=F:\Users\jenkins\workspace\Test_openjdk20_j9_extended.functional_x86-64_windows_Nightly_testList_0\openjdkbinary\j2sdk-image\bin\default\j9gc_full29.dll
10:48:54 Module_base_address=00007FFDD1810000 Offset_in_DLL=000000000015bebb
10:48:54 Target=2_90_20230624_89 (Windows Server 2019 10.0 build 17763)
10:48:54 CPU=amd64 (8 logical CPUs) (0x3ffb9c000 RAM)
10:48:54 ----------- Stack Backtrace -----------
10:48:54 J9VMDllMain+0x15aeab (0x00007FFDD196BEBB [j9gc_full29+0x15bebb])
10:48:54 J9VMDllMain+0x15a355 (0x00007FFDD196B365 [j9gc_full29+0x15b365])
10:48:54 J9VMDllMain+0x1cf266 (0x00007FFDD19E0276 [j9gc_full29+0x1d0276])
10:48:54 J9VMDllMain+0x14ed2d (0x00007FFDD195FD3D [j9gc_full29+0x14fd3d])
10:48:54 J9VMDllMain+0x14fec1 (0x00007FFDD1960ED1 [j9gc_full29+0x150ed1])
10:48:54 j9port_isCompatible+0x1a1bb (0x00007FFDDD0ECD9B [j9prt29+0x1cd9b])
10:48:54 J9VMDllMain+0x15001b (0x00007FFDD196102B [j9gc_full29+0x15102b])
10:48:54 omrthread_get_category+0xa42 (0x00007FFDDD254242 [j9thr29+0x4242])
10:48:54 _o_exp+0x5a (0x00007FFDE6A7268A [ucrtbase+0x2268a])
10:48:54 BaseThreadInitThunk+0x14 (0x00007FFDEA687AC4 [KERNEL32+0x17ac4])
10:48:54 RtlUserThreadStart+0x21 (0x00007FFDEAA1A351 [ntdll+0x5a351])
```
There are other issues with vmState=0x00020002, this may be a dup. | non_priority | testjcmmxbeanremote crash vmstate testjcmmxbeanremote xjit xgcpolicy optthruput xnocompressedrefs type segmentation error vmstate windows exceptioncode signal exceptionaddress contextflags inaccessiblereadaddress rdi rsi rax rbx rcx rdx rip rsp rbp eflags fs es ds f d f d f d f d f d f d f d f d f d f d f d f d f d f d f d f d module f users jenkins workspace test extended functional windows nightly testlist openjdkbinary image bin default dll module base address offset in dll target windows server build cpu logical cpus ram stack backtrace iscompatible omrthread get category o exp basethreadinitthunk rtluserthreadstart there are other issues with vmstate this may be a dup | 0 |
24,849 | 24,385,363,439 | IssuesEvent | 2022-10-04 11:17:22 | ebi-webcomponents/nightingale | https://api.github.com/repos/ebi-webcomponents/nightingale | closed | Improve protvista-navigation usability | protvista-navigation usability Stalled | **Describe the usability issue**
In user testing, it has been found that users do not notice the fact that `protvista-navigation` is an interactive element. They also miss the fact they can use the left and right edges of the grey area to specify the zoom start and end.
**Describe the solution that has been discussed by the team**
1. Add "handles" to the left and right edges. Could be 2x half circles, other examples below
2. hover effect: add a hover effect to the grey area and the handles (see 1. above). Note: it would be good to define a hover effect globally for Nightingale components (e.g. opacity 90%)
**How does the solution address the problem?**
Visual markers and behaviour make it easier for the user to discover the functionality. | True | Improve protvista-navigation usability - **Describe the usability issue**
In user testing, it has been found that users do not notice the fact that `protvista-navigation` is an interactive element. They also miss the fact they can use the left and right edges of the grey area to specify the zoom start and end.
**Describe the solution that has been discussed by the team**
1. Add "handles" to the left and right edges. Could be 2x half circles, other examples below
2. hover effect: add a hover effect to the grey area and the handles (see 1. above). Note: it would be good to define a hover effect globally for Nightingale components (e.g. opacity 90%)
**How does the solution address the problem?**
Visual markers and behaviour make it easier for the user to discover the functionality. | non_priority | improve protvista navigation usability describe the usability issue in user testing it has been found that users do not notice the fact that protvista navigation is an interactive element they also miss the fact they can use the left and right edges of the grey area to specify the zoom start and end describe the solution that has been discussed by the team add handles to the left and right edges could be half circles other examples below hover effect add a hover effect to the grey area and the handles see above note it would be good to define a hover effect globally for nightingale components e g opacity how does the solution address the problem visual markers and behaviour make it easier for the user to discover the functionality | 0 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.