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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
17,246 | 4,152,245,789 | IssuesEvent | 2016-06-15 23:49:54 | ambisonictoolkit/atk-sc3 | https://api.github.com/repos/ambisonictoolkit/atk-sc3 | opened | FoaEncoderKernel: SuperStereo, broken link in documentation | documentation | The link at: http://doc.sccode.org/Classes/FoaEncoderKernel.html#footnote_1
Currently points to: http://en.wikipedia.org/wiki/Ambisonics#Super_stereo
Should point to: https://en.wikipedia.org/wiki/Ambisonic_UHJ_format#Super_stereo | 1.0 | FoaEncoderKernel: SuperStereo, broken link in documentation - The link at: http://doc.sccode.org/Classes/FoaEncoderKernel.html#footnote_1
Currently points to: http://en.wikipedia.org/wiki/Ambisonics#Super_stereo
Should point to: https://en.wikipedia.org/wiki/Ambisonic_UHJ_format#Super_stereo | non_priority | foaencoderkernel superstereo broken link in documentation the link at currently points to should point to | 0 |
135,481 | 12,685,168,241 | IssuesEvent | 2020-06-20 02:32:58 | StefanoDepetris/DrinkTeam | https://api.github.com/repos/StefanoDepetris/DrinkTeam | closed | Falta | documentation | 1- revisar tp1, requerimientos, matriz y casos de prueba
2- faltan diagramas de paquetes, de objetos
3-faltan pruebas unitarias automáticas y actualizar la matriz | 1.0 | Falta - 1- revisar tp1, requerimientos, matriz y casos de prueba
2- faltan diagramas de paquetes, de objetos
3-faltan pruebas unitarias automáticas y actualizar la matriz | non_priority | falta revisar requerimientos matriz y casos de prueba faltan diagramas de paquetes de objetos faltan pruebas unitarias automáticas y actualizar la matriz | 0 |
211,386 | 23,812,128,537 | IssuesEvent | 2022-09-04 22:46:03 | kube-tarian/sigrun | https://api.github.com/repos/kube-tarian/sigrun | closed | CVE-2022-24769 (Medium) detected in github.com/docker/docker-v20.10.7 | security vulnerability no-issue-activity | ## CVE-2022-24769 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>github.com/docker/docker-v20.10.7</b></p></summary>
<p>Moby Project - a collaborative project for the container ecosystem to assemble container-based systems</p>
<p>
Dependency Hierarchy:
- github.com/google/go-containerregistry-v0.6.0 (Root Library)
- github.com/docker/cli-v20.10.7
- :x: **github.com/docker/docker-v20.10.7** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/kube-tarian/sigrun/commit/df1f7d3f67826e841793324e4796be4fbd91c00f">df1f7d3f67826e841793324e4796be4fbd91c00f</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
Moby is an open-source project created by Docker to enable and accelerate software containerization. A bug was found in Moby (Docker Engine) prior to version 20.10.14 where containers were incorrectly started with non-empty inheritable Linux process capabilities, creating an atypical Linux environment and enabling programs with inheritable file capabilities to elevate those capabilities to the permitted set during `execve(2)`. Normally, when executable programs have specified permitted file capabilities, otherwise unprivileged users and processes can execute those programs and gain the specified file capabilities up to the bounding set. Due to this bug, containers which included executable programs with inheritable file capabilities allowed otherwise unprivileged users and processes to additionally gain these inheritable file capabilities up to the container's bounding set. Containers which use Linux users and groups to perform privilege separation inside the container are most directly impacted. This bug did not affect the container security sandbox as the inheritable set never contained more capabilities than were included in the container's bounding set. This bug has been fixed in Moby (Docker Engine) 20.10.14. Running containers should be stopped, deleted, and recreated for the inheritable capabilities to be reset. This fix changes Moby (Docker Engine) behavior such that containers are started with a more typical Linux environment. As a workaround, the entry point of a container can be modified to use a utility like `capsh(1)` to drop inheritable capabilities prior to the primary process starting.
<p>Publish Date: 2022-03-24
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-24769>CVE-2022-24769</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.9</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- 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-2022-24769">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-24769</a></p>
<p>Release Date: 2022-03-24</p>
<p>Fix Resolution: v20.10.14</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-24769 (Medium) detected in github.com/docker/docker-v20.10.7 - ## CVE-2022-24769 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>github.com/docker/docker-v20.10.7</b></p></summary>
<p>Moby Project - a collaborative project for the container ecosystem to assemble container-based systems</p>
<p>
Dependency Hierarchy:
- github.com/google/go-containerregistry-v0.6.0 (Root Library)
- github.com/docker/cli-v20.10.7
- :x: **github.com/docker/docker-v20.10.7** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/kube-tarian/sigrun/commit/df1f7d3f67826e841793324e4796be4fbd91c00f">df1f7d3f67826e841793324e4796be4fbd91c00f</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
Moby is an open-source project created by Docker to enable and accelerate software containerization. A bug was found in Moby (Docker Engine) prior to version 20.10.14 where containers were incorrectly started with non-empty inheritable Linux process capabilities, creating an atypical Linux environment and enabling programs with inheritable file capabilities to elevate those capabilities to the permitted set during `execve(2)`. Normally, when executable programs have specified permitted file capabilities, otherwise unprivileged users and processes can execute those programs and gain the specified file capabilities up to the bounding set. Due to this bug, containers which included executable programs with inheritable file capabilities allowed otherwise unprivileged users and processes to additionally gain these inheritable file capabilities up to the container's bounding set. Containers which use Linux users and groups to perform privilege separation inside the container are most directly impacted. This bug did not affect the container security sandbox as the inheritable set never contained more capabilities than were included in the container's bounding set. This bug has been fixed in Moby (Docker Engine) 20.10.14. Running containers should be stopped, deleted, and recreated for the inheritable capabilities to be reset. This fix changes Moby (Docker Engine) behavior such that containers are started with a more typical Linux environment. As a workaround, the entry point of a container can be modified to use a utility like `capsh(1)` to drop inheritable capabilities prior to the primary process starting.
<p>Publish Date: 2022-03-24
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-24769>CVE-2022-24769</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.9</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- 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-2022-24769">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-24769</a></p>
<p>Release Date: 2022-03-24</p>
<p>Fix Resolution: v20.10.14</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 github com docker docker cve medium severity vulnerability vulnerable library github com docker docker moby project a collaborative project for the container ecosystem to assemble container based systems dependency hierarchy github com google go containerregistry root library github com docker cli x github com docker docker vulnerable library found in head commit a href found in base branch main vulnerability details moby is an open source project created by docker to enable and accelerate software containerization a bug was found in moby docker engine prior to version where containers were incorrectly started with non empty inheritable linux process capabilities creating an atypical linux environment and enabling programs with inheritable file capabilities to elevate those capabilities to the permitted set during execve normally when executable programs have specified permitted file capabilities otherwise unprivileged users and processes can execute those programs and gain the specified file capabilities up to the bounding set due to this bug containers which included executable programs with inheritable file capabilities allowed otherwise unprivileged users and processes to additionally gain these inheritable file capabilities up to the container s bounding set containers which use linux users and groups to perform privilege separation inside the container are most directly impacted this bug did not affect the container security sandbox as the inheritable set never contained more capabilities than were included in the container s bounding set this bug has been fixed in moby docker engine running containers should be stopped deleted and recreated for the inheritable capabilities to be reset this fix changes moby docker engine behavior such that containers are started with a more typical linux environment as a workaround the entry point of a container can be modified to use a utility like capsh to drop inheritable capabilities prior to the primary process starting publish date url a href cvss score details base score metrics exploitability metrics attack vector local 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 step up your open source security game with mend | 0 |
59,953 | 24,939,736,257 | IssuesEvent | 2022-10-31 17:53:04 | Azure/azure-sdk-for-java | https://api.github.com/repos/Azure/azure-sdk-for-java | closed | [BUG] [AMQP] Websocket upgrade request's hostname must be the same as the HTTP connection host | Event Hubs Service Bus amqp | Today we use the Event Hubs (or Service Bus) FQDN as the "hostname" + "host header" for the HTTP GET upgrade request to switch the protocol to WebSocket on an existing HTTP connection.
Such an upgrade request works if the existing HTTP connection had established to the FQDN of the Event Hubs.
On the other hand, if the HTTP connection had established to the Custom Endpoint (front-ending Event Hubs or Service Bus), then an upgrade request using the FQDN of the Event Hubs as the "hostname" + "host-header" may fail. Instead, the "hostname" + "host-header" should be the custom endpoint host.
For example, the server addressed by the Custom Endpoint may validate the "host-header" resulting 404 responses for the Upgrade request when the client expects a 101 response. Interestingly, not all custom endpoint host does the "host-header" validation; that's why we didn't encounter this before. For example, using App Gateway as a custom endpoint with multi-site setup kick off this validation; with basic-site setup, this validation is off.
In a nutshell, the Websocket upgrade request's hostname must be the same as the HTTP connection host. | 1.0 | [BUG] [AMQP] Websocket upgrade request's hostname must be the same as the HTTP connection host - Today we use the Event Hubs (or Service Bus) FQDN as the "hostname" + "host header" for the HTTP GET upgrade request to switch the protocol to WebSocket on an existing HTTP connection.
Such an upgrade request works if the existing HTTP connection had established to the FQDN of the Event Hubs.
On the other hand, if the HTTP connection had established to the Custom Endpoint (front-ending Event Hubs or Service Bus), then an upgrade request using the FQDN of the Event Hubs as the "hostname" + "host-header" may fail. Instead, the "hostname" + "host-header" should be the custom endpoint host.
For example, the server addressed by the Custom Endpoint may validate the "host-header" resulting 404 responses for the Upgrade request when the client expects a 101 response. Interestingly, not all custom endpoint host does the "host-header" validation; that's why we didn't encounter this before. For example, using App Gateway as a custom endpoint with multi-site setup kick off this validation; with basic-site setup, this validation is off.
In a nutshell, the Websocket upgrade request's hostname must be the same as the HTTP connection host. | non_priority | websocket upgrade request s hostname must be the same as the http connection host today we use the event hubs or service bus fqdn as the hostname host header for the http get upgrade request to switch the protocol to websocket on an existing http connection such an upgrade request works if the existing http connection had established to the fqdn of the event hubs on the other hand if the http connection had established to the custom endpoint front ending event hubs or service bus then an upgrade request using the fqdn of the event hubs as the hostname host header may fail instead the hostname host header should be the custom endpoint host for example the server addressed by the custom endpoint may validate the host header resulting responses for the upgrade request when the client expects a response interestingly not all custom endpoint host does the host header validation that s why we didn t encounter this before for example using app gateway as a custom endpoint with multi site setup kick off this validation with basic site setup this validation is off in a nutshell the websocket upgrade request s hostname must be the same as the http connection host | 0 |
90,664 | 26,162,850,573 | IssuesEvent | 2022-12-31 21:21:30 | mfem/mfem | https://api.github.com/repos/mfem/mfem | closed | When mfem is linked with superlu-dist mfem installs an invalid MFEMConfig.cmake file | building linalg stale | It has the line:
```
set(MFEM_INCLUDE_DIRS "${PACKAGE_PREFIX_DIR}/include;/usr/local/include;/usr/local/include/superlu")
```
with the directory ```/usr/local/include/superlu``` that doesn't exist.
mfem-4.4
superlu-dist-8.1.0
clang-14
FreeBSD 13.1
| 1.0 | When mfem is linked with superlu-dist mfem installs an invalid MFEMConfig.cmake file - It has the line:
```
set(MFEM_INCLUDE_DIRS "${PACKAGE_PREFIX_DIR}/include;/usr/local/include;/usr/local/include/superlu")
```
with the directory ```/usr/local/include/superlu``` that doesn't exist.
mfem-4.4
superlu-dist-8.1.0
clang-14
FreeBSD 13.1
| non_priority | when mfem is linked with superlu dist mfem installs an invalid mfemconfig cmake file it has the line set mfem include dirs package prefix dir include usr local include usr local include superlu with the directory usr local include superlu that doesn t exist mfem superlu dist clang freebsd | 0 |
305,945 | 26,423,190,352 | IssuesEvent | 2023-01-13 23:09:06 | tarantool/vshard | https://api.github.com/repos/tarantool/vshard | closed | flaky tests: storage/storage and unit/util | qa flaky test | Something is going on with fibers:
<details>
<summary> storage/storage.test.lua</summary>
```
storage/storage.test.lua memtx [ fail ]
Test failed! Result content mismatch:
--- storage/storage.result Mon Dec 5 12:49:08 2022
+++ /home/runner/work/vshard/vshard/test/var/rejects/storage/storage.reject Mon Dec 5 12:53:05 2022
@@ -962,7 +962,7 @@
...
assert(not ok and err.message)
---
-- fiber is cancelled
+- error: assertion failed!
...
--
-- Bucket_are_all_rw() registry function.
```
</details>
<details>
<summary> unit/util.test.lua</summary>
```
unit/util.test.lua [ fail ]
Test failed! Result content mismatch:
--- unit/util.result Mon Dec 5 12:49:08 2022
+++ /home/runner/work/vshard/vshard/test/var/rejects/unit/util.reject Mon Dec 5 12:53:21 2022
@@ -266,15 +266,16 @@
...
assert(not ok)
---
-- true
+- error: assertion failed!
...
err.message
---
-- fiber is cancelled
+- error: '[string "return err.message "]:1: attempt to index global ''err'' (a nil
+ value)'
...
assert(type(err) == 'table')
---
-- true
+- error: assertion failed!
...
--
-- Exception-safe fiber cancel check.
```
</details>
Reproduced on CI Tarantool 2.7 and 2.8. Cannot reproduced it locally | 1.0 | flaky tests: storage/storage and unit/util - Something is going on with fibers:
<details>
<summary> storage/storage.test.lua</summary>
```
storage/storage.test.lua memtx [ fail ]
Test failed! Result content mismatch:
--- storage/storage.result Mon Dec 5 12:49:08 2022
+++ /home/runner/work/vshard/vshard/test/var/rejects/storage/storage.reject Mon Dec 5 12:53:05 2022
@@ -962,7 +962,7 @@
...
assert(not ok and err.message)
---
-- fiber is cancelled
+- error: assertion failed!
...
--
-- Bucket_are_all_rw() registry function.
```
</details>
<details>
<summary> unit/util.test.lua</summary>
```
unit/util.test.lua [ fail ]
Test failed! Result content mismatch:
--- unit/util.result Mon Dec 5 12:49:08 2022
+++ /home/runner/work/vshard/vshard/test/var/rejects/unit/util.reject Mon Dec 5 12:53:21 2022
@@ -266,15 +266,16 @@
...
assert(not ok)
---
-- true
+- error: assertion failed!
...
err.message
---
-- fiber is cancelled
+- error: '[string "return err.message "]:1: attempt to index global ''err'' (a nil
+ value)'
...
assert(type(err) == 'table')
---
-- true
+- error: assertion failed!
...
--
-- Exception-safe fiber cancel check.
```
</details>
Reproduced on CI Tarantool 2.7 and 2.8. Cannot reproduced it locally | non_priority | flaky tests storage storage and unit util something is going on with fibers storage storage test lua storage storage test lua memtx test failed result content mismatch storage storage result mon dec home runner work vshard vshard test var rejects storage storage reject mon dec assert not ok and err message fiber is cancelled error assertion failed bucket are all rw registry function unit util test lua unit util test lua test failed result content mismatch unit util result mon dec home runner work vshard vshard test var rejects unit util reject mon dec assert not ok true error assertion failed err message fiber is cancelled error attempt to index global err a nil value assert type err table true error assertion failed exception safe fiber cancel check reproduced on ci tarantool and cannot reproduced it locally | 0 |
54,708 | 11,287,434,112 | IssuesEvent | 2020-01-16 04:28:20 | happycube/ld-decode | https://api.github.com/repos/happycube/ld-decode | closed | Make ld-process-efm map against VBI | enhancement ld-decode-tools wontfix | On discs such as Domesday AIV the VBI contains a hint as to where data/audio is present (as an EFM track) on the disc. This could be used to help the tool determine if errors are due to corrupt data or simply missing EFM. | 1.0 | Make ld-process-efm map against VBI - On discs such as Domesday AIV the VBI contains a hint as to where data/audio is present (as an EFM track) on the disc. This could be used to help the tool determine if errors are due to corrupt data or simply missing EFM. | non_priority | make ld process efm map against vbi on discs such as domesday aiv the vbi contains a hint as to where data audio is present as an efm track on the disc this could be used to help the tool determine if errors are due to corrupt data or simply missing efm | 0 |
276,017 | 20,964,614,428 | IssuesEvent | 2022-03-28 04:40:02 | LukeShortCloud/winesapOS | https://api.github.com/repos/LukeShortCloud/winesapOS | closed | Update VERSION for stable release | documentation | The VERSION file should say "3.0.0". After that tagged release, we can move onto "3.1.0-dev". | 1.0 | Update VERSION for stable release - The VERSION file should say "3.0.0". After that tagged release, we can move onto "3.1.0-dev". | non_priority | update version for stable release the version file should say after that tagged release we can move onto dev | 0 |
36,381 | 12,405,027,226 | IssuesEvent | 2020-05-21 16:32:12 | wrbejar/Nova8JavaVulnerable | https://api.github.com/repos/wrbejar/Nova8JavaVulnerable | opened | CVE-2018-1000632 (High) detected in dom4j-1.6.1.jar | security vulnerability | ## CVE-2018-1000632 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>dom4j-1.6.1.jar</b></p></summary>
<p>dom4j: the flexible XML framework for Java</p>
<p>Library home page: <a href="http://dom4j.org">http://dom4j.org</a></p>
<p>Path to vulnerable library: /Nova8JavaVulnerable/target/JavaVulnerableLab/WEB-INF/lib/dom4j-1.6.1.jar,_depth_0/Nova8JavaVulnerable/target/JavaVulnerableLab/META-INF/maven/org.cysecurity/JavaVulnerableLab/target/JavaVulnerableLab/WEB-INF/lib/dom4j-1.6.1.jar,/root/.m2/repository/dom4j/dom4j/1.6.1/dom4j-1.6.1.jar,_depth_0/Nova8JavaVulnerable/target/JavaVulnerableLab/WEB-INF/lib/dom4j-1.6.1.jar,/root/.m2/repository/dom4j/dom4j/1.6.1/dom4j-1.6.1.jar</p>
<p>
Dependency Hierarchy:
- :x: **dom4j-1.6.1.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/wrbejar/Nova8JavaVulnerable/commit/1387452ca7bf6063988c143381dd8c9938b0ab3f">1387452ca7bf6063988c143381dd8c9938b0ab3f</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
dom4j version prior to version 2.1.1 contains a CWE-91: XML Injection vulnerability in Class: Element. Methods: addElement, addAttribute that can result in an attacker tampering with XML documents through XML injection. This attack appear to be exploitable via an attacker specifying attributes or elements in the XML document. This vulnerability appears to have been fixed in 2.1.1 or later.
<p>Publish Date: 2018-08-20
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-1000632>CVE-2018-1000632</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: 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://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-1000632">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-1000632</a></p>
<p>Release Date: 2018-08-20</p>
<p>Fix Resolution: org.dom4j:dom4j:2.0.3</p>
</p>
</details>
<p></p>
***
:rescue_worker_helmet: Automatic Remediation is available for this issue
<!-- <REMEDIATE>{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"Java","groupId":"dom4j","packageName":"dom4j","packageVersion":"1.6.1","isTransitiveDependency":false,"dependencyTree":"dom4j:dom4j:1.6.1","isMinimumFixVersionAvailable":true,"minimumFixVersion":"org.dom4j:dom4j:2.0.3"}],"vulnerabilityIdentifier":"CVE-2018-1000632","vulnerabilityDetails":"dom4j version prior to version 2.1.1 contains a CWE-91: XML Injection vulnerability in Class: Element. Methods: addElement, addAttribute that can result in an attacker tampering with XML documents through XML injection. This attack appear to be exploitable via an attacker specifying attributes or elements in the XML document. This vulnerability appears to have been fixed in 2.1.1 or later.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-1000632","cvss3Severity":"high","cvss3Score":"7.5","cvss3Metrics":{"A":"None","AC":"Low","PR":"None","S":"Unchanged","C":"None","UI":"None","AV":"Network","I":"High"},"extraData":{}}</REMEDIATE> --> | True | CVE-2018-1000632 (High) detected in dom4j-1.6.1.jar - ## CVE-2018-1000632 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>dom4j-1.6.1.jar</b></p></summary>
<p>dom4j: the flexible XML framework for Java</p>
<p>Library home page: <a href="http://dom4j.org">http://dom4j.org</a></p>
<p>Path to vulnerable library: /Nova8JavaVulnerable/target/JavaVulnerableLab/WEB-INF/lib/dom4j-1.6.1.jar,_depth_0/Nova8JavaVulnerable/target/JavaVulnerableLab/META-INF/maven/org.cysecurity/JavaVulnerableLab/target/JavaVulnerableLab/WEB-INF/lib/dom4j-1.6.1.jar,/root/.m2/repository/dom4j/dom4j/1.6.1/dom4j-1.6.1.jar,_depth_0/Nova8JavaVulnerable/target/JavaVulnerableLab/WEB-INF/lib/dom4j-1.6.1.jar,/root/.m2/repository/dom4j/dom4j/1.6.1/dom4j-1.6.1.jar</p>
<p>
Dependency Hierarchy:
- :x: **dom4j-1.6.1.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/wrbejar/Nova8JavaVulnerable/commit/1387452ca7bf6063988c143381dd8c9938b0ab3f">1387452ca7bf6063988c143381dd8c9938b0ab3f</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
dom4j version prior to version 2.1.1 contains a CWE-91: XML Injection vulnerability in Class: Element. Methods: addElement, addAttribute that can result in an attacker tampering with XML documents through XML injection. This attack appear to be exploitable via an attacker specifying attributes or elements in the XML document. This vulnerability appears to have been fixed in 2.1.1 or later.
<p>Publish Date: 2018-08-20
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-1000632>CVE-2018-1000632</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: 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://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-1000632">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-1000632</a></p>
<p>Release Date: 2018-08-20</p>
<p>Fix Resolution: org.dom4j:dom4j:2.0.3</p>
</p>
</details>
<p></p>
***
:rescue_worker_helmet: Automatic Remediation is available for this issue
<!-- <REMEDIATE>{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"Java","groupId":"dom4j","packageName":"dom4j","packageVersion":"1.6.1","isTransitiveDependency":false,"dependencyTree":"dom4j:dom4j:1.6.1","isMinimumFixVersionAvailable":true,"minimumFixVersion":"org.dom4j:dom4j:2.0.3"}],"vulnerabilityIdentifier":"CVE-2018-1000632","vulnerabilityDetails":"dom4j version prior to version 2.1.1 contains a CWE-91: XML Injection vulnerability in Class: Element. Methods: addElement, addAttribute that can result in an attacker tampering with XML documents through XML injection. This attack appear to be exploitable via an attacker specifying attributes or elements in the XML document. This vulnerability appears to have been fixed in 2.1.1 or later.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-1000632","cvss3Severity":"high","cvss3Score":"7.5","cvss3Metrics":{"A":"None","AC":"Low","PR":"None","S":"Unchanged","C":"None","UI":"None","AV":"Network","I":"High"},"extraData":{}}</REMEDIATE> --> | non_priority | cve high detected in jar cve high severity vulnerability vulnerable library jar the flexible xml framework for java library home page a href path to vulnerable library target javavulnerablelab web inf lib jar depth target javavulnerablelab meta inf maven org cysecurity javavulnerablelab target javavulnerablelab web inf lib jar root repository jar depth target javavulnerablelab web inf lib jar root repository jar dependency hierarchy x jar vulnerable library found in head commit a href vulnerability details version prior to version contains a cwe xml injection vulnerability in class element methods addelement addattribute that can result in an attacker tampering with xml documents through xml injection this attack appear to be exploitable via an attacker specifying attributes or elements in the xml document this vulnerability appears to have been fixed in or later 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 org rescue worker helmet automatic remediation is available for this issue isopenpronvulnerability true ispackagebased true isdefaultbranch true packages vulnerabilityidentifier cve vulnerabilitydetails version prior to version contains a cwe xml injection vulnerability in class element methods addelement addattribute that can result in an attacker tampering with xml documents through xml injection this attack appear to be exploitable via an attacker specifying attributes or elements in the xml document this vulnerability appears to have been fixed in or later vulnerabilityurl | 0 |
189,691 | 14,518,019,831 | IssuesEvent | 2020-12-13 21:55:52 | verilator/verilator | https://api.github.com/repos/verilator/verilator | closed | -faligned-new does not work under Travis with clang | area: tests effort: days resolution: abandoned | ---
Author Name: **Todd Strader** (@toddstrader)
Original Redmine Issue: 1478 from https://www.veripool.org
---
It was discovered in # that the -faligned-new flag causes errors when compiling Verilated code under Travis CI using clang. This should have been detected and dealt with via a test for this behavior in configure, but configure did not observe the same behavior.
For the time being, a band-aid has been applied to configure.ac turn off this flag when compiling with clang under Travis:
```
AS_IF([test "x$TRAVIS_COMPILER" != xclang], [_MY_CXX_CHECK_OPT(CFG_CXXFLAGS_NO_UNUSED,-faligned-new)])
```
This resolves the Travis breakage but allows for the same issue to crop up on similar systems. Ultimately, we should understand why configure doesn't catch this behavior with Travis + clang so that the configure test can be improved and the band-aid can be removed.
| 1.0 | -faligned-new does not work under Travis with clang - ---
Author Name: **Todd Strader** (@toddstrader)
Original Redmine Issue: 1478 from https://www.veripool.org
---
It was discovered in # that the -faligned-new flag causes errors when compiling Verilated code under Travis CI using clang. This should have been detected and dealt with via a test for this behavior in configure, but configure did not observe the same behavior.
For the time being, a band-aid has been applied to configure.ac turn off this flag when compiling with clang under Travis:
```
AS_IF([test "x$TRAVIS_COMPILER" != xclang], [_MY_CXX_CHECK_OPT(CFG_CXXFLAGS_NO_UNUSED,-faligned-new)])
```
This resolves the Travis breakage but allows for the same issue to crop up on similar systems. Ultimately, we should understand why configure doesn't catch this behavior with Travis + clang so that the configure test can be improved and the band-aid can be removed.
| non_priority | faligned new does not work under travis with clang author name todd strader toddstrader original redmine issue from it was discovered in that the faligned new flag causes errors when compiling verilated code under travis ci using clang this should have been detected and dealt with via a test for this behavior in configure but configure did not observe the same behavior for the time being a band aid has been applied to configure ac turn off this flag when compiling with clang under travis as if this resolves the travis breakage but allows for the same issue to crop up on similar systems ultimately we should understand why configure doesn t catch this behavior with travis clang so that the configure test can be improved and the band aid can be removed | 0 |
135,294 | 19,552,457,021 | IssuesEvent | 2022-01-03 00:54:48 | redis/redis | https://api.github.com/repos/redis/redis | closed | Redis Cluster PubSub - Scalability Issues | state:needs-design class:feature | Edit: [full mailing list discussion](https://groups.google.com/forum/#!topic/redis-db/B0_fvfDWLGM)
Hi all,
I also posted this on the mailing list, but as I think it is a bug, I'll add it here, too.
according to [1] and [2] PubSub works by broadcasting every publish to every other Redis Cluster node. This limits the PubSub throughput to the [bisection bandwidth](https://en.wikipedia.org/wiki/Bisection_bandwidth) of the underlying network infrastructure divided by the number of nodes times message size. So if a typical message has 1KB, the cluster has 10 nodes and bandwidth is 1 GBit/s, throughput is already limited to 12.5K RPS. If we increase the message size to 5 KB and the number of nodes to 50, we only get 500 RPS - much less than a single Redis instance could service (>100K RPS), while putting maximum pressure on the network. PubSub thus scales linearly wrt. to the cluster size, but in the the negative direction!
This leads me to my question: why not just redirect clients to the node responsible for the PubSub channel's hash slot owner, similar to normal data operations? Cluster nodes would thus only have to publish and notify locally, similar to keyspace notifications [3], and PubSub would be perfectly scalable. Sure, this would break PSUBSCRIBE for the cluster, but PSUBSCRIBE could be limited to only allow patterns containing a {hash-tag}, meaning that the subscription only pertains to channels containing that hash tag + matching the pattern (i.e. one specific node). As PSUBSCRIBE is semantically a multi-key operation, this would make perfect sense and be consistent with the rest of Redis Cluster.
In summary, I think the assumption that clients may publish and subscribe to any node is a dangerous guarantee that kills scalability. What do you think - could the above be the way to handle PubSub in Redis Cluster? Are there currently any workarounds to have PubSub scale in a Redis Cluster deployment?
[1] https://github.com/antirez/redis/issues/1927
[2] http://redis.io/topics/cluster-spec
[3] https://github.com/antirez/redis/issues/2541
P.S. Redis Cluster is a great project and highly value all the effort that goes into it!
| 1.0 | Redis Cluster PubSub - Scalability Issues - Edit: [full mailing list discussion](https://groups.google.com/forum/#!topic/redis-db/B0_fvfDWLGM)
Hi all,
I also posted this on the mailing list, but as I think it is a bug, I'll add it here, too.
according to [1] and [2] PubSub works by broadcasting every publish to every other Redis Cluster node. This limits the PubSub throughput to the [bisection bandwidth](https://en.wikipedia.org/wiki/Bisection_bandwidth) of the underlying network infrastructure divided by the number of nodes times message size. So if a typical message has 1KB, the cluster has 10 nodes and bandwidth is 1 GBit/s, throughput is already limited to 12.5K RPS. If we increase the message size to 5 KB and the number of nodes to 50, we only get 500 RPS - much less than a single Redis instance could service (>100K RPS), while putting maximum pressure on the network. PubSub thus scales linearly wrt. to the cluster size, but in the the negative direction!
This leads me to my question: why not just redirect clients to the node responsible for the PubSub channel's hash slot owner, similar to normal data operations? Cluster nodes would thus only have to publish and notify locally, similar to keyspace notifications [3], and PubSub would be perfectly scalable. Sure, this would break PSUBSCRIBE for the cluster, but PSUBSCRIBE could be limited to only allow patterns containing a {hash-tag}, meaning that the subscription only pertains to channels containing that hash tag + matching the pattern (i.e. one specific node). As PSUBSCRIBE is semantically a multi-key operation, this would make perfect sense and be consistent with the rest of Redis Cluster.
In summary, I think the assumption that clients may publish and subscribe to any node is a dangerous guarantee that kills scalability. What do you think - could the above be the way to handle PubSub in Redis Cluster? Are there currently any workarounds to have PubSub scale in a Redis Cluster deployment?
[1] https://github.com/antirez/redis/issues/1927
[2] http://redis.io/topics/cluster-spec
[3] https://github.com/antirez/redis/issues/2541
P.S. Redis Cluster is a great project and highly value all the effort that goes into it!
| non_priority | redis cluster pubsub scalability issues edit hi all i also posted this on the mailing list but as i think it is a bug i ll add it here too according to and pubsub works by broadcasting every publish to every other redis cluster node this limits the pubsub throughput to the of the underlying network infrastructure divided by the number of nodes times message size so if a typical message has the cluster has nodes and bandwidth is gbit s throughput is already limited to rps if we increase the message size to kb and the number of nodes to we only get rps much less than a single redis instance could service rps while putting maximum pressure on the network pubsub thus scales linearly wrt to the cluster size but in the the negative direction this leads me to my question why not just redirect clients to the node responsible for the pubsub channel s hash slot owner similar to normal data operations cluster nodes would thus only have to publish and notify locally similar to keyspace notifications and pubsub would be perfectly scalable sure this would break psubscribe for the cluster but psubscribe could be limited to only allow patterns containing a hash tag meaning that the subscription only pertains to channels containing that hash tag matching the pattern i e one specific node as psubscribe is semantically a multi key operation this would make perfect sense and be consistent with the rest of redis cluster in summary i think the assumption that clients may publish and subscribe to any node is a dangerous guarantee that kills scalability what do you think could the above be the way to handle pubsub in redis cluster are there currently any workarounds to have pubsub scale in a redis cluster deployment p s redis cluster is a great project and highly value all the effort that goes into it | 0 |
399,764 | 27,254,719,035 | IssuesEvent | 2023-02-22 10:38:33 | hiubunho/blog | https://api.github.com/repos/hiubunho/blog | opened | This is my first blog. | documentation | This is my first blog.
This is my first blog.
This is my first blog.
This is my first blog.
| 1.0 | This is my first blog. - This is my first blog.
This is my first blog.
This is my first blog.
This is my first blog.
| non_priority | this is my first blog this is my first blog this is my first blog this is my first blog this is my first blog | 0 |
265,529 | 23,175,046,109 | IssuesEvent | 2022-07-31 09:40:46 | cockroachdb/cockroach | https://api.github.com/repos/cockroachdb/cockroach | opened | pkg/sql/sqlitelogictest/tests/local/local_test: TestSqlLiteLogic_testindexorderby_nosort1000slt_good_1_test failed | C-test-failure O-robot branch-master | pkg/sql/sqlitelogictest/tests/local/local_test.TestSqlLiteLogic_testindexorderby_nosort1000slt_good_1_test [failed](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Nightlies_SQLiteLogicTestsBazel/5921538?buildTab=log) with [artifacts](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Nightlies_SQLiteLogicTestsBazel/5921538?buildTab=artifacts#/) on master @ [0352fbee5e6933e8bca28aae4b136bcd495ab227](https://github.com/cockroachdb/cockroach/commits/0352fbee5e6933e8bca28aae4b136bcd495ab227):
```
[09:36:52] --- progress: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3411/execroot/com_github_cockroachdb_cockroach/bazel-out/k8-dbg/bin/pkg/sql/sqlitelogictest/tests/local/local_test_/local_test.runfiles/com_github_cockroachdb_cockroach/external/com_github_cockroachdb_sqllogictest/test/index/orderby_nosort/1000/slt_good_1.test: 5230 statements
[09:36:55] --- progress: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3411/execroot/com_github_cockroachdb_cockroach/bazel-out/k8-dbg/bin/pkg/sql/sqlitelogictest/tests/local/local_test_/local_test.runfiles/com_github_cockroachdb_cockroach/external/com_github_cockroachdb_sqllogictest/test/index/orderby_nosort/1000/slt_good_1.test: 5231 statements
[09:36:58] --- progress: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3411/execroot/com_github_cockroachdb_cockroach/bazel-out/k8-dbg/bin/pkg/sql/sqlitelogictest/tests/local/local_test_/local_test.runfiles/com_github_cockroachdb_cockroach/external/com_github_cockroachdb_sqllogictest/test/index/orderby_nosort/1000/slt_good_1.test: 5232 statements
[09:37:01] --- progress: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3411/execroot/com_github_cockroachdb_cockroach/bazel-out/k8-dbg/bin/pkg/sql/sqlitelogictest/tests/local/local_test_/local_test.runfiles/com_github_cockroachdb_cockroach/external/com_github_cockroachdb_sqllogictest/test/index/orderby_nosort/1000/slt_good_1.test: 5233 statements
[09:37:05] --- progress: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3411/execroot/com_github_cockroachdb_cockroach/bazel-out/k8-dbg/bin/pkg/sql/sqlitelogictest/tests/local/local_test_/local_test.runfiles/com_github_cockroachdb_cockroach/external/com_github_cockroachdb_sqllogictest/test/index/orderby_nosort/1000/slt_good_1.test: 5234 statements
[09:37:09] --- progress: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3411/execroot/com_github_cockroachdb_cockroach/bazel-out/k8-dbg/bin/pkg/sql/sqlitelogictest/tests/local/local_test_/local_test.runfiles/com_github_cockroachdb_cockroach/external/com_github_cockroachdb_sqllogictest/test/index/orderby_nosort/1000/slt_good_1.test: 5235 statements
[09:37:13] --- progress: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3411/execroot/com_github_cockroachdb_cockroach/bazel-out/k8-dbg/bin/pkg/sql/sqlitelogictest/tests/local/local_test_/local_test.runfiles/com_github_cockroachdb_cockroach/external/com_github_cockroachdb_sqllogictest/test/index/orderby_nosort/1000/slt_good_1.test: 5236 statements
[09:37:18] --- progress: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3411/execroot/com_github_cockroachdb_cockroach/bazel-out/k8-dbg/bin/pkg/sql/sqlitelogictest/tests/local/local_test_/local_test.runfiles/com_github_cockroachdb_cockroach/external/com_github_cockroachdb_sqllogictest/test/index/orderby_nosort/1000/slt_good_1.test: 5237 statements
[09:37:22] --- progress: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3411/execroot/com_github_cockroachdb_cockroach/bazel-out/k8-dbg/bin/pkg/sql/sqlitelogictest/tests/local/local_test_/local_test.runfiles/com_github_cockroachdb_cockroach/external/com_github_cockroachdb_sqllogictest/test/index/orderby_nosort/1000/slt_good_1.test: 5238 statements
[09:37:26] --- progress: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3411/execroot/com_github_cockroachdb_cockroach/bazel-out/k8-dbg/bin/pkg/sql/sqlitelogictest/tests/local/local_test_/local_test.runfiles/com_github_cockroachdb_cockroach/external/com_github_cockroachdb_sqllogictest/test/index/orderby_nosort/1000/slt_good_1.test: 5239 statements
[09:37:30] --- progress: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3411/execroot/com_github_cockroachdb_cockroach/bazel-out/k8-dbg/bin/pkg/sql/sqlitelogictest/tests/local/local_test_/local_test.runfiles/com_github_cockroachdb_cockroach/external/com_github_cockroachdb_sqllogictest/test/index/orderby_nosort/1000/slt_good_1.test: 5242 statements
[09:37:34] --- progress: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3411/execroot/com_github_cockroachdb_cockroach/bazel-out/k8-dbg/bin/pkg/sql/sqlitelogictest/tests/local/local_test_/local_test.runfiles/com_github_cockroachdb_cockroach/external/com_github_cockroachdb_sqllogictest/test/index/orderby_nosort/1000/slt_good_1.test: 5245 statements
[09:37:38] --- progress: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3411/execroot/com_github_cockroachdb_cockroach/bazel-out/k8-dbg/bin/pkg/sql/sqlitelogictest/tests/local/local_test_/local_test.runfiles/com_github_cockroachdb_cockroach/external/com_github_cockroachdb_sqllogictest/test/index/orderby_nosort/1000/slt_good_1.test: 5246 statements
[09:37:43] --- progress: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3411/execroot/com_github_cockroachdb_cockroach/bazel-out/k8-dbg/bin/pkg/sql/sqlitelogictest/tests/local/local_test_/local_test.runfiles/com_github_cockroachdb_cockroach/external/com_github_cockroachdb_sqllogictest/test/index/orderby_nosort/1000/slt_good_1.test: 5247 statements
[09:37:47] --- progress: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3411/execroot/com_github_cockroachdb_cockroach/bazel-out/k8-dbg/bin/pkg/sql/sqlitelogictest/tests/local/local_test_/local_test.runfiles/com_github_cockroachdb_cockroach/external/com_github_cockroachdb_sqllogictest/test/index/orderby_nosort/1000/slt_good_1.test: 5248 statements
[09:37:51] --- progress: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3411/execroot/com_github_cockroachdb_cockroach/bazel-out/k8-dbg/bin/pkg/sql/sqlitelogictest/tests/local/local_test_/local_test.runfiles/com_github_cockroachdb_cockroach/external/com_github_cockroachdb_sqllogictest/test/index/orderby_nosort/1000/slt_good_1.test: 5249 statements
[09:37:55] --- progress: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3411/execroot/com_github_cockroachdb_cockroach/bazel-out/k8-dbg/bin/pkg/sql/sqlitelogictest/tests/local/local_test_/local_test.runfiles/com_github_cockroachdb_cockroach/external/com_github_cockroachdb_sqllogictest/test/index/orderby_nosort/1000/slt_good_1.test: 5252 statements
[09:37:59] --- progress: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3411/execroot/com_github_cockroachdb_cockroach/bazel-out/k8-dbg/bin/pkg/sql/sqlitelogictest/tests/local/local_test_/local_test.runfiles/com_github_cockroachdb_cockroach/external/com_github_cockroachdb_sqllogictest/test/index/orderby_nosort/1000/slt_good_1.test: 5254 statements
[09:38:04] --- progress: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3411/execroot/com_github_cockroachdb_cockroach/bazel-out/k8-dbg/bin/pkg/sql/sqlitelogictest/tests/local/local_test_/local_test.runfiles/com_github_cockroachdb_cockroach/external/com_github_cockroachdb_sqllogictest/test/index/orderby_nosort/1000/slt_good_1.test: 5255 statements
[09:38:08] --- progress: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3411/execroot/com_github_cockroachdb_cockroach/bazel-out/k8-dbg/bin/pkg/sql/sqlitelogictest/tests/local/local_test_/local_test.runfiles/com_github_cockroachdb_cockroach/external/com_github_cockroachdb_sqllogictest/test/index/orderby_nosort/1000/slt_good_1.test: 5256 statements
[09:38:12] --- progress: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3411/execroot/com_github_cockroachdb_cockroach/bazel-out/k8-dbg/bin/pkg/sql/sqlitelogictest/tests/local/local_test_/local_test.runfiles/com_github_cockroachdb_cockroach/external/com_github_cockroachdb_sqllogictest/test/index/orderby_nosort/1000/slt_good_1.test: 5257 statements
[09:38:16] --- progress: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3411/execroot/com_github_cockroachdb_cockroach/bazel-out/k8-dbg/bin/pkg/sql/sqlitelogictest/tests/local/local_test_/local_test.runfiles/com_github_cockroachdb_cockroach/external/com_github_cockroachdb_sqllogictest/test/index/orderby_nosort/1000/slt_good_1.test: 5258 statements
[09:38:20] --- progress: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3411/execroot/com_github_cockroachdb_cockroach/bazel-out/k8-dbg/bin/pkg/sql/sqlitelogictest/tests/local/local_test_/local_test.runfiles/com_github_cockroachdb_cockroach/external/com_github_cockroachdb_sqllogictest/test/index/orderby_nosort/1000/slt_good_1.test: 5260 statements
[09:38:24] --- progress: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3411/execroot/com_github_cockroachdb_cockroach/bazel-out/k8-dbg/bin/pkg/sql/sqlitelogictest/tests/local/local_test_/local_test.runfiles/com_github_cockroachdb_cockroach/external/com_github_cockroachdb_sqllogictest/test/index/orderby_nosort/1000/slt_good_1.test: 5261 statements
[09:38:29] --- progress: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3411/execroot/com_github_cockroachdb_cockroach/bazel-out/k8-dbg/bin/pkg/sql/sqlitelogictest/tests/local/local_test_/local_test.runfiles/com_github_cockroachdb_cockroach/external/com_github_cockroachdb_sqllogictest/test/index/orderby_nosort/1000/slt_good_1.test: 5262 statements
[09:38:33] --- progress: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3411/execroot/com_github_cockroachdb_cockroach/bazel-out/k8-dbg/bin/pkg/sql/sqlitelogictest/tests/local/local_test_/local_test.runfiles/com_github_cockroachdb_cockroach/external/com_github_cockroachdb_sqllogictest/test/index/orderby_nosort/1000/slt_good_1.test: 5263 statements
[09:38:37] --- progress: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3411/execroot/com_github_cockroachdb_cockroach/bazel-out/k8-dbg/bin/pkg/sql/sqlitelogictest/tests/local/local_test_/local_test.runfiles/com_github_cockroachdb_cockroach/external/com_github_cockroachdb_sqllogictest/test/index/orderby_nosort/1000/slt_good_1.test: 5264 statements
[09:38:41] --- progress: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3411/execroot/com_github_cockroachdb_cockroach/bazel-out/k8-dbg/bin/pkg/sql/sqlitelogictest/tests/local/local_test_/local_test.runfiles/com_github_cockroachdb_cockroach/external/com_github_cockroachdb_sqllogictest/test/index/orderby_nosort/1000/slt_good_1.test: 5265 statements
[09:38:45] --- progress: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3411/execroot/com_github_cockroachdb_cockroach/bazel-out/k8-dbg/bin/pkg/sql/sqlitelogictest/tests/local/local_test_/local_test.runfiles/com_github_cockroachdb_cockroach/external/com_github_cockroachdb_sqllogictest/test/index/orderby_nosort/1000/slt_good_1.test: 5267 statements
[09:38:50] --- progress: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3411/execroot/com_github_cockroachdb_cockroach/bazel-out/k8-dbg/bin/pkg/sql/sqlitelogictest/tests/local/local_test_/local_test.runfiles/com_github_cockroachdb_cockroach/external/com_github_cockroachdb_sqllogictest/test/index/orderby_nosort/1000/slt_good_1.test: 5268 statements
[09:38:54] --- progress: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3411/execroot/com_github_cockroachdb_cockroach/bazel-out/k8-dbg/bin/pkg/sql/sqlitelogictest/tests/local/local_test_/local_test.runfiles/com_github_cockroachdb_cockroach/external/com_github_cockroachdb_sqllogictest/test/index/orderby_nosort/1000/slt_good_1.test: 5269 statements
[09:38:58] --- progress: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3411/execroot/com_github_cockroachdb_cockroach/bazel-out/k8-dbg/bin/pkg/sql/sqlitelogictest/tests/local/local_test_/local_test.runfiles/com_github_cockroachdb_cockroach/external/com_github_cockroachdb_sqllogictest/test/index/orderby_nosort/1000/slt_good_1.test: 5271 statements
[09:39:02] --- progress: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3411/execroot/com_github_cockroachdb_cockroach/bazel-out/k8-dbg/bin/pkg/sql/sqlitelogictest/tests/local/local_test_/local_test.runfiles/com_github_cockroachdb_cockroach/external/com_github_cockroachdb_sqllogictest/test/index/orderby_nosort/1000/slt_good_1.test: 5272 statements
[09:39:06] --- progress: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3411/execroot/com_github_cockroachdb_cockroach/bazel-out/k8-dbg/bin/pkg/sql/sqlitelogictest/tests/local/local_test_/local_test.runfiles/com_github_cockroachdb_cockroach/external/com_github_cockroachdb_sqllogictest/test/index/orderby_nosort/1000/slt_good_1.test: 5274 statements
[09:39:10] --- progress: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3411/execroot/com_github_cockroachdb_cockroach/bazel-out/k8-dbg/bin/pkg/sql/sqlitelogictest/tests/local/local_test_/local_test.runfiles/com_github_cockroachdb_cockroach/external/com_github_cockroachdb_sqllogictest/test/index/orderby_nosort/1000/slt_good_1.test: 5275 statements
[09:39:15] --- progress: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3411/execroot/com_github_cockroachdb_cockroach/bazel-out/k8-dbg/bin/pkg/sql/sqlitelogictest/tests/local/local_test_/local_test.runfiles/com_github_cockroachdb_cockroach/external/com_github_cockroachdb_sqllogictest/test/index/orderby_nosort/1000/slt_good_1.test: 5276 statements
[09:39:19] --- progress: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3411/execroot/com_github_cockroachdb_cockroach/bazel-out/k8-dbg/bin/pkg/sql/sqlitelogictest/tests/local/local_test_/local_test.runfiles/com_github_cockroachdb_cockroach/external/com_github_cockroachdb_sqllogictest/test/index/orderby_nosort/1000/slt_good_1.test: 5277 statements
[09:39:23] --- progress: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3411/execroot/com_github_cockroachdb_cockroach/bazel-out/k8-dbg/bin/pkg/sql/sqlitelogictest/tests/local/local_test_/local_test.runfiles/com_github_cockroachdb_cockroach/external/com_github_cockroachdb_sqllogictest/test/index/orderby_nosort/1000/slt_good_1.test: 5278 statements
[09:39:27] --- progress: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3411/execroot/com_github_cockroachdb_cockroach/bazel-out/k8-dbg/bin/pkg/sql/sqlitelogictest/tests/local/local_test_/local_test.runfiles/com_github_cockroachdb_cockroach/external/com_github_cockroachdb_sqllogictest/test/index/orderby_nosort/1000/slt_good_1.test: 5280 statements
[09:39:31] --- progress: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3411/execroot/com_github_cockroachdb_cockroach/bazel-out/k8-dbg/bin/pkg/sql/sqlitelogictest/tests/local/local_test_/local_test.runfiles/com_github_cockroachdb_cockroach/external/com_github_cockroachdb_sqllogictest/test/index/orderby_nosort/1000/slt_good_1.test: 5281 statements
[09:39:35] --- progress: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3411/execroot/com_github_cockroachdb_cockroach/bazel-out/k8-dbg/bin/pkg/sql/sqlitelogictest/tests/local/local_test_/local_test.runfiles/com_github_cockroachdb_cockroach/external/com_github_cockroachdb_sqllogictest/test/index/orderby_nosort/1000/slt_good_1.test: 5282 statements
[09:39:40] --- progress: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3411/execroot/com_github_cockroachdb_cockroach/bazel-out/k8-dbg/bin/pkg/sql/sqlitelogictest/tests/local/local_test_/local_test.runfiles/com_github_cockroachdb_cockroach/external/com_github_cockroachdb_sqllogictest/test/index/orderby_nosort/1000/slt_good_1.test: 5283 statements
logic.go:2542:
pq: streamer budget: memory budget exceeded: 19263 bytes requested, 28672 currently allocated, 37632 bytes in budget
[09:39:40] --- done: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3411/execroot/com_github_cockroachdb_cockroach/bazel-out/k8-dbg/bin/pkg/sql/sqlitelogictest/tests/local/local_test_/local_test.runfiles/com_github_cockroachdb_cockroach/external/com_github_cockroachdb_sqllogictest/test/index/orderby_nosort/1000/slt_good_1.test with config local: 5297 tests, 1 failures
logic.go:3570:
/home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3411/execroot/com_github_cockroachdb_cockroach/bazel-out/k8-dbg/bin/pkg/sql/sqlitelogictest/tests/local/local_test_/local_test.runfiles/com_github_cockroachdb_cockroach/external/com_github_cockroachdb_sqllogictest/test/index/orderby_nosort/1000/slt_good_1.test:23651: error while processing
logic.go:3570: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3411/execroot/com_github_cockroachdb_cockroach/bazel-out/k8-dbg/bin/pkg/sql/sqlitelogictest/tests/local/local_test_/local_test.runfiles/com_github_cockroachdb_cockroach/external/com_github_cockroachdb_sqllogictest/test/index/orderby_nosort/1000/slt_good_1.test:23651: too many errors encountered, skipping the rest of the input
panic.go:500: -- test log scope end --
--- FAIL: TestSqlLiteLogic_testindexorderby_nosort1000slt_good_1_test (2536.35s)
```
<details><summary>Help</summary>
<p>
See also: [How To Investigate a Go Test Failure \(internal\)](https://cockroachlabs.atlassian.net/l/c/HgfXfJgM)
</p>
</details>
<sub>
[This test on roachdash](https://roachdash.crdb.dev/?filter=status:open%20t:.*TestSqlLiteLogic_testindexorderby_nosort1000slt_good_1_test.*&sort=title+created&display=lastcommented+project) | [Improve this report!](https://github.com/cockroachdb/cockroach/tree/master/pkg/cmd/internal/issues)
</sub>
| 1.0 | pkg/sql/sqlitelogictest/tests/local/local_test: TestSqlLiteLogic_testindexorderby_nosort1000slt_good_1_test failed - pkg/sql/sqlitelogictest/tests/local/local_test.TestSqlLiteLogic_testindexorderby_nosort1000slt_good_1_test [failed](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Nightlies_SQLiteLogicTestsBazel/5921538?buildTab=log) with [artifacts](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Nightlies_SQLiteLogicTestsBazel/5921538?buildTab=artifacts#/) on master @ [0352fbee5e6933e8bca28aae4b136bcd495ab227](https://github.com/cockroachdb/cockroach/commits/0352fbee5e6933e8bca28aae4b136bcd495ab227):
```
[09:36:52] --- progress: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3411/execroot/com_github_cockroachdb_cockroach/bazel-out/k8-dbg/bin/pkg/sql/sqlitelogictest/tests/local/local_test_/local_test.runfiles/com_github_cockroachdb_cockroach/external/com_github_cockroachdb_sqllogictest/test/index/orderby_nosort/1000/slt_good_1.test: 5230 statements
[09:36:55] --- progress: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3411/execroot/com_github_cockroachdb_cockroach/bazel-out/k8-dbg/bin/pkg/sql/sqlitelogictest/tests/local/local_test_/local_test.runfiles/com_github_cockroachdb_cockroach/external/com_github_cockroachdb_sqllogictest/test/index/orderby_nosort/1000/slt_good_1.test: 5231 statements
[09:36:58] --- progress: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3411/execroot/com_github_cockroachdb_cockroach/bazel-out/k8-dbg/bin/pkg/sql/sqlitelogictest/tests/local/local_test_/local_test.runfiles/com_github_cockroachdb_cockroach/external/com_github_cockroachdb_sqllogictest/test/index/orderby_nosort/1000/slt_good_1.test: 5232 statements
[09:37:01] --- progress: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3411/execroot/com_github_cockroachdb_cockroach/bazel-out/k8-dbg/bin/pkg/sql/sqlitelogictest/tests/local/local_test_/local_test.runfiles/com_github_cockroachdb_cockroach/external/com_github_cockroachdb_sqllogictest/test/index/orderby_nosort/1000/slt_good_1.test: 5233 statements
[09:37:05] --- progress: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3411/execroot/com_github_cockroachdb_cockroach/bazel-out/k8-dbg/bin/pkg/sql/sqlitelogictest/tests/local/local_test_/local_test.runfiles/com_github_cockroachdb_cockroach/external/com_github_cockroachdb_sqllogictest/test/index/orderby_nosort/1000/slt_good_1.test: 5234 statements
[09:37:09] --- progress: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3411/execroot/com_github_cockroachdb_cockroach/bazel-out/k8-dbg/bin/pkg/sql/sqlitelogictest/tests/local/local_test_/local_test.runfiles/com_github_cockroachdb_cockroach/external/com_github_cockroachdb_sqllogictest/test/index/orderby_nosort/1000/slt_good_1.test: 5235 statements
[09:37:13] --- progress: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3411/execroot/com_github_cockroachdb_cockroach/bazel-out/k8-dbg/bin/pkg/sql/sqlitelogictest/tests/local/local_test_/local_test.runfiles/com_github_cockroachdb_cockroach/external/com_github_cockroachdb_sqllogictest/test/index/orderby_nosort/1000/slt_good_1.test: 5236 statements
[09:37:18] --- progress: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3411/execroot/com_github_cockroachdb_cockroach/bazel-out/k8-dbg/bin/pkg/sql/sqlitelogictest/tests/local/local_test_/local_test.runfiles/com_github_cockroachdb_cockroach/external/com_github_cockroachdb_sqllogictest/test/index/orderby_nosort/1000/slt_good_1.test: 5237 statements
[09:37:22] --- progress: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3411/execroot/com_github_cockroachdb_cockroach/bazel-out/k8-dbg/bin/pkg/sql/sqlitelogictest/tests/local/local_test_/local_test.runfiles/com_github_cockroachdb_cockroach/external/com_github_cockroachdb_sqllogictest/test/index/orderby_nosort/1000/slt_good_1.test: 5238 statements
[09:37:26] --- progress: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3411/execroot/com_github_cockroachdb_cockroach/bazel-out/k8-dbg/bin/pkg/sql/sqlitelogictest/tests/local/local_test_/local_test.runfiles/com_github_cockroachdb_cockroach/external/com_github_cockroachdb_sqllogictest/test/index/orderby_nosort/1000/slt_good_1.test: 5239 statements
[09:37:30] --- progress: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3411/execroot/com_github_cockroachdb_cockroach/bazel-out/k8-dbg/bin/pkg/sql/sqlitelogictest/tests/local/local_test_/local_test.runfiles/com_github_cockroachdb_cockroach/external/com_github_cockroachdb_sqllogictest/test/index/orderby_nosort/1000/slt_good_1.test: 5242 statements
[09:37:34] --- progress: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3411/execroot/com_github_cockroachdb_cockroach/bazel-out/k8-dbg/bin/pkg/sql/sqlitelogictest/tests/local/local_test_/local_test.runfiles/com_github_cockroachdb_cockroach/external/com_github_cockroachdb_sqllogictest/test/index/orderby_nosort/1000/slt_good_1.test: 5245 statements
[09:37:38] --- progress: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3411/execroot/com_github_cockroachdb_cockroach/bazel-out/k8-dbg/bin/pkg/sql/sqlitelogictest/tests/local/local_test_/local_test.runfiles/com_github_cockroachdb_cockroach/external/com_github_cockroachdb_sqllogictest/test/index/orderby_nosort/1000/slt_good_1.test: 5246 statements
[09:37:43] --- progress: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3411/execroot/com_github_cockroachdb_cockroach/bazel-out/k8-dbg/bin/pkg/sql/sqlitelogictest/tests/local/local_test_/local_test.runfiles/com_github_cockroachdb_cockroach/external/com_github_cockroachdb_sqllogictest/test/index/orderby_nosort/1000/slt_good_1.test: 5247 statements
[09:37:47] --- progress: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3411/execroot/com_github_cockroachdb_cockroach/bazel-out/k8-dbg/bin/pkg/sql/sqlitelogictest/tests/local/local_test_/local_test.runfiles/com_github_cockroachdb_cockroach/external/com_github_cockroachdb_sqllogictest/test/index/orderby_nosort/1000/slt_good_1.test: 5248 statements
[09:37:51] --- progress: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3411/execroot/com_github_cockroachdb_cockroach/bazel-out/k8-dbg/bin/pkg/sql/sqlitelogictest/tests/local/local_test_/local_test.runfiles/com_github_cockroachdb_cockroach/external/com_github_cockroachdb_sqllogictest/test/index/orderby_nosort/1000/slt_good_1.test: 5249 statements
[09:37:55] --- progress: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3411/execroot/com_github_cockroachdb_cockroach/bazel-out/k8-dbg/bin/pkg/sql/sqlitelogictest/tests/local/local_test_/local_test.runfiles/com_github_cockroachdb_cockroach/external/com_github_cockroachdb_sqllogictest/test/index/orderby_nosort/1000/slt_good_1.test: 5252 statements
[09:37:59] --- progress: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3411/execroot/com_github_cockroachdb_cockroach/bazel-out/k8-dbg/bin/pkg/sql/sqlitelogictest/tests/local/local_test_/local_test.runfiles/com_github_cockroachdb_cockroach/external/com_github_cockroachdb_sqllogictest/test/index/orderby_nosort/1000/slt_good_1.test: 5254 statements
[09:38:04] --- progress: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3411/execroot/com_github_cockroachdb_cockroach/bazel-out/k8-dbg/bin/pkg/sql/sqlitelogictest/tests/local/local_test_/local_test.runfiles/com_github_cockroachdb_cockroach/external/com_github_cockroachdb_sqllogictest/test/index/orderby_nosort/1000/slt_good_1.test: 5255 statements
[09:38:08] --- progress: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3411/execroot/com_github_cockroachdb_cockroach/bazel-out/k8-dbg/bin/pkg/sql/sqlitelogictest/tests/local/local_test_/local_test.runfiles/com_github_cockroachdb_cockroach/external/com_github_cockroachdb_sqllogictest/test/index/orderby_nosort/1000/slt_good_1.test: 5256 statements
[09:38:12] --- progress: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3411/execroot/com_github_cockroachdb_cockroach/bazel-out/k8-dbg/bin/pkg/sql/sqlitelogictest/tests/local/local_test_/local_test.runfiles/com_github_cockroachdb_cockroach/external/com_github_cockroachdb_sqllogictest/test/index/orderby_nosort/1000/slt_good_1.test: 5257 statements
[09:38:16] --- progress: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3411/execroot/com_github_cockroachdb_cockroach/bazel-out/k8-dbg/bin/pkg/sql/sqlitelogictest/tests/local/local_test_/local_test.runfiles/com_github_cockroachdb_cockroach/external/com_github_cockroachdb_sqllogictest/test/index/orderby_nosort/1000/slt_good_1.test: 5258 statements
[09:38:20] --- progress: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3411/execroot/com_github_cockroachdb_cockroach/bazel-out/k8-dbg/bin/pkg/sql/sqlitelogictest/tests/local/local_test_/local_test.runfiles/com_github_cockroachdb_cockroach/external/com_github_cockroachdb_sqllogictest/test/index/orderby_nosort/1000/slt_good_1.test: 5260 statements
[09:38:24] --- progress: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3411/execroot/com_github_cockroachdb_cockroach/bazel-out/k8-dbg/bin/pkg/sql/sqlitelogictest/tests/local/local_test_/local_test.runfiles/com_github_cockroachdb_cockroach/external/com_github_cockroachdb_sqllogictest/test/index/orderby_nosort/1000/slt_good_1.test: 5261 statements
[09:38:29] --- progress: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3411/execroot/com_github_cockroachdb_cockroach/bazel-out/k8-dbg/bin/pkg/sql/sqlitelogictest/tests/local/local_test_/local_test.runfiles/com_github_cockroachdb_cockroach/external/com_github_cockroachdb_sqllogictest/test/index/orderby_nosort/1000/slt_good_1.test: 5262 statements
[09:38:33] --- progress: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3411/execroot/com_github_cockroachdb_cockroach/bazel-out/k8-dbg/bin/pkg/sql/sqlitelogictest/tests/local/local_test_/local_test.runfiles/com_github_cockroachdb_cockroach/external/com_github_cockroachdb_sqllogictest/test/index/orderby_nosort/1000/slt_good_1.test: 5263 statements
[09:38:37] --- progress: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3411/execroot/com_github_cockroachdb_cockroach/bazel-out/k8-dbg/bin/pkg/sql/sqlitelogictest/tests/local/local_test_/local_test.runfiles/com_github_cockroachdb_cockroach/external/com_github_cockroachdb_sqllogictest/test/index/orderby_nosort/1000/slt_good_1.test: 5264 statements
[09:38:41] --- progress: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3411/execroot/com_github_cockroachdb_cockroach/bazel-out/k8-dbg/bin/pkg/sql/sqlitelogictest/tests/local/local_test_/local_test.runfiles/com_github_cockroachdb_cockroach/external/com_github_cockroachdb_sqllogictest/test/index/orderby_nosort/1000/slt_good_1.test: 5265 statements
[09:38:45] --- progress: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3411/execroot/com_github_cockroachdb_cockroach/bazel-out/k8-dbg/bin/pkg/sql/sqlitelogictest/tests/local/local_test_/local_test.runfiles/com_github_cockroachdb_cockroach/external/com_github_cockroachdb_sqllogictest/test/index/orderby_nosort/1000/slt_good_1.test: 5267 statements
[09:38:50] --- progress: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3411/execroot/com_github_cockroachdb_cockroach/bazel-out/k8-dbg/bin/pkg/sql/sqlitelogictest/tests/local/local_test_/local_test.runfiles/com_github_cockroachdb_cockroach/external/com_github_cockroachdb_sqllogictest/test/index/orderby_nosort/1000/slt_good_1.test: 5268 statements
[09:38:54] --- progress: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3411/execroot/com_github_cockroachdb_cockroach/bazel-out/k8-dbg/bin/pkg/sql/sqlitelogictest/tests/local/local_test_/local_test.runfiles/com_github_cockroachdb_cockroach/external/com_github_cockroachdb_sqllogictest/test/index/orderby_nosort/1000/slt_good_1.test: 5269 statements
[09:38:58] --- progress: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3411/execroot/com_github_cockroachdb_cockroach/bazel-out/k8-dbg/bin/pkg/sql/sqlitelogictest/tests/local/local_test_/local_test.runfiles/com_github_cockroachdb_cockroach/external/com_github_cockroachdb_sqllogictest/test/index/orderby_nosort/1000/slt_good_1.test: 5271 statements
[09:39:02] --- progress: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3411/execroot/com_github_cockroachdb_cockroach/bazel-out/k8-dbg/bin/pkg/sql/sqlitelogictest/tests/local/local_test_/local_test.runfiles/com_github_cockroachdb_cockroach/external/com_github_cockroachdb_sqllogictest/test/index/orderby_nosort/1000/slt_good_1.test: 5272 statements
[09:39:06] --- progress: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3411/execroot/com_github_cockroachdb_cockroach/bazel-out/k8-dbg/bin/pkg/sql/sqlitelogictest/tests/local/local_test_/local_test.runfiles/com_github_cockroachdb_cockroach/external/com_github_cockroachdb_sqllogictest/test/index/orderby_nosort/1000/slt_good_1.test: 5274 statements
[09:39:10] --- progress: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3411/execroot/com_github_cockroachdb_cockroach/bazel-out/k8-dbg/bin/pkg/sql/sqlitelogictest/tests/local/local_test_/local_test.runfiles/com_github_cockroachdb_cockroach/external/com_github_cockroachdb_sqllogictest/test/index/orderby_nosort/1000/slt_good_1.test: 5275 statements
[09:39:15] --- progress: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3411/execroot/com_github_cockroachdb_cockroach/bazel-out/k8-dbg/bin/pkg/sql/sqlitelogictest/tests/local/local_test_/local_test.runfiles/com_github_cockroachdb_cockroach/external/com_github_cockroachdb_sqllogictest/test/index/orderby_nosort/1000/slt_good_1.test: 5276 statements
[09:39:19] --- progress: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3411/execroot/com_github_cockroachdb_cockroach/bazel-out/k8-dbg/bin/pkg/sql/sqlitelogictest/tests/local/local_test_/local_test.runfiles/com_github_cockroachdb_cockroach/external/com_github_cockroachdb_sqllogictest/test/index/orderby_nosort/1000/slt_good_1.test: 5277 statements
[09:39:23] --- progress: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3411/execroot/com_github_cockroachdb_cockroach/bazel-out/k8-dbg/bin/pkg/sql/sqlitelogictest/tests/local/local_test_/local_test.runfiles/com_github_cockroachdb_cockroach/external/com_github_cockroachdb_sqllogictest/test/index/orderby_nosort/1000/slt_good_1.test: 5278 statements
[09:39:27] --- progress: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3411/execroot/com_github_cockroachdb_cockroach/bazel-out/k8-dbg/bin/pkg/sql/sqlitelogictest/tests/local/local_test_/local_test.runfiles/com_github_cockroachdb_cockroach/external/com_github_cockroachdb_sqllogictest/test/index/orderby_nosort/1000/slt_good_1.test: 5280 statements
[09:39:31] --- progress: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3411/execroot/com_github_cockroachdb_cockroach/bazel-out/k8-dbg/bin/pkg/sql/sqlitelogictest/tests/local/local_test_/local_test.runfiles/com_github_cockroachdb_cockroach/external/com_github_cockroachdb_sqllogictest/test/index/orderby_nosort/1000/slt_good_1.test: 5281 statements
[09:39:35] --- progress: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3411/execroot/com_github_cockroachdb_cockroach/bazel-out/k8-dbg/bin/pkg/sql/sqlitelogictest/tests/local/local_test_/local_test.runfiles/com_github_cockroachdb_cockroach/external/com_github_cockroachdb_sqllogictest/test/index/orderby_nosort/1000/slt_good_1.test: 5282 statements
[09:39:40] --- progress: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3411/execroot/com_github_cockroachdb_cockroach/bazel-out/k8-dbg/bin/pkg/sql/sqlitelogictest/tests/local/local_test_/local_test.runfiles/com_github_cockroachdb_cockroach/external/com_github_cockroachdb_sqllogictest/test/index/orderby_nosort/1000/slt_good_1.test: 5283 statements
logic.go:2542:
pq: streamer budget: memory budget exceeded: 19263 bytes requested, 28672 currently allocated, 37632 bytes in budget
[09:39:40] --- done: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3411/execroot/com_github_cockroachdb_cockroach/bazel-out/k8-dbg/bin/pkg/sql/sqlitelogictest/tests/local/local_test_/local_test.runfiles/com_github_cockroachdb_cockroach/external/com_github_cockroachdb_sqllogictest/test/index/orderby_nosort/1000/slt_good_1.test with config local: 5297 tests, 1 failures
logic.go:3570:
/home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3411/execroot/com_github_cockroachdb_cockroach/bazel-out/k8-dbg/bin/pkg/sql/sqlitelogictest/tests/local/local_test_/local_test.runfiles/com_github_cockroachdb_cockroach/external/com_github_cockroachdb_sqllogictest/test/index/orderby_nosort/1000/slt_good_1.test:23651: error while processing
logic.go:3570: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/3411/execroot/com_github_cockroachdb_cockroach/bazel-out/k8-dbg/bin/pkg/sql/sqlitelogictest/tests/local/local_test_/local_test.runfiles/com_github_cockroachdb_cockroach/external/com_github_cockroachdb_sqllogictest/test/index/orderby_nosort/1000/slt_good_1.test:23651: too many errors encountered, skipping the rest of the input
panic.go:500: -- test log scope end --
--- FAIL: TestSqlLiteLogic_testindexorderby_nosort1000slt_good_1_test (2536.35s)
```
<details><summary>Help</summary>
<p>
See also: [How To Investigate a Go Test Failure \(internal\)](https://cockroachlabs.atlassian.net/l/c/HgfXfJgM)
</p>
</details>
<sub>
[This test on roachdash](https://roachdash.crdb.dev/?filter=status:open%20t:.*TestSqlLiteLogic_testindexorderby_nosort1000slt_good_1_test.*&sort=title+created&display=lastcommented+project) | [Improve this report!](https://github.com/cockroachdb/cockroach/tree/master/pkg/cmd/internal/issues)
</sub>
| non_priority | pkg sql sqlitelogictest tests local local test testsqllitelogic testindexorderby good test failed pkg sql sqlitelogictest tests local local test testsqllitelogic testindexorderby good test with on master progress home roach cache bazel bazel roach sandbox processwrapper sandbox execroot com github cockroachdb cockroach bazel out dbg bin pkg sql sqlitelogictest tests local local test local test runfiles com github cockroachdb cockroach external com github cockroachdb sqllogictest test index orderby nosort slt good test statements progress home roach cache bazel bazel roach sandbox processwrapper sandbox execroot com github cockroachdb cockroach bazel out dbg bin pkg sql sqlitelogictest tests local local test local test runfiles com github cockroachdb cockroach external com github cockroachdb sqllogictest test index orderby nosort slt good test statements progress home roach cache bazel bazel roach sandbox processwrapper sandbox execroot com github cockroachdb cockroach bazel out dbg bin pkg sql sqlitelogictest tests local local test local test runfiles com github cockroachdb cockroach external com github cockroachdb sqllogictest test index orderby nosort slt good test statements progress home roach cache bazel bazel roach sandbox processwrapper sandbox execroot com github cockroachdb cockroach bazel out dbg bin pkg sql sqlitelogictest tests local local test local test runfiles com github cockroachdb cockroach external com github cockroachdb sqllogictest test index orderby nosort slt good test statements progress home roach cache bazel bazel roach sandbox processwrapper sandbox execroot com github cockroachdb cockroach bazel out dbg bin pkg sql sqlitelogictest tests local local test local test runfiles com github cockroachdb cockroach external com github cockroachdb sqllogictest test index orderby nosort slt good test statements progress home roach cache bazel bazel roach sandbox processwrapper sandbox execroot com github cockroachdb cockroach bazel out dbg bin pkg sql sqlitelogictest tests local local test local test runfiles com github cockroachdb cockroach external com github cockroachdb sqllogictest test index orderby nosort slt good test statements progress home roach cache bazel bazel roach sandbox processwrapper sandbox execroot com github cockroachdb cockroach bazel out dbg bin pkg sql sqlitelogictest tests local local test local test runfiles com github cockroachdb cockroach external com github cockroachdb sqllogictest test index orderby nosort slt good test statements progress home roach cache bazel bazel roach sandbox processwrapper sandbox execroot com github cockroachdb cockroach bazel out dbg bin pkg sql sqlitelogictest tests local local test local test runfiles com github cockroachdb cockroach external com github cockroachdb sqllogictest test index orderby nosort slt good test statements progress home roach cache bazel bazel roach sandbox processwrapper sandbox execroot com github cockroachdb cockroach bazel out dbg bin pkg sql sqlitelogictest tests local local test local test runfiles com github cockroachdb cockroach external com github cockroachdb sqllogictest test index orderby nosort slt good test statements progress home roach cache bazel bazel roach sandbox processwrapper sandbox execroot com github cockroachdb cockroach bazel out dbg bin pkg sql sqlitelogictest tests local local test local test runfiles com github cockroachdb cockroach external com github cockroachdb sqllogictest test index orderby nosort slt good test statements progress home roach cache bazel bazel roach sandbox processwrapper sandbox execroot com github cockroachdb cockroach bazel out dbg bin pkg sql sqlitelogictest tests local local test local test runfiles com github cockroachdb cockroach external com github cockroachdb sqllogictest test index orderby nosort slt good test statements progress home roach cache bazel bazel roach sandbox processwrapper sandbox execroot com github cockroachdb cockroach bazel out dbg bin pkg sql sqlitelogictest tests local local test local test runfiles com github cockroachdb cockroach external com github cockroachdb sqllogictest test index orderby nosort slt good test statements progress home roach cache bazel bazel roach sandbox processwrapper sandbox execroot com github cockroachdb cockroach bazel out dbg bin pkg sql sqlitelogictest tests local local test local test runfiles com github cockroachdb cockroach external com github cockroachdb sqllogictest test index orderby nosort slt good test statements progress home roach cache bazel bazel roach sandbox processwrapper sandbox execroot com github cockroachdb cockroach bazel out dbg bin pkg sql sqlitelogictest tests local local test local test runfiles com github cockroachdb cockroach external com github cockroachdb sqllogictest test index orderby nosort slt good test statements progress home roach cache bazel bazel roach sandbox processwrapper sandbox execroot com github cockroachdb cockroach bazel out dbg bin pkg sql sqlitelogictest tests local local test local test runfiles com github cockroachdb cockroach external com github cockroachdb sqllogictest test index orderby nosort slt good test statements progress home roach cache bazel bazel roach sandbox processwrapper sandbox execroot com github cockroachdb cockroach bazel out dbg bin pkg sql sqlitelogictest tests local local test local test runfiles com github cockroachdb cockroach external com github cockroachdb sqllogictest test index orderby nosort slt good test statements progress home roach cache bazel bazel roach sandbox processwrapper sandbox execroot com github cockroachdb cockroach bazel out dbg bin pkg sql sqlitelogictest tests local local test local test runfiles com github cockroachdb cockroach external com github cockroachdb sqllogictest test index orderby nosort slt good test statements progress home roach cache bazel bazel roach sandbox processwrapper sandbox execroot com github cockroachdb cockroach bazel out dbg bin pkg sql sqlitelogictest tests local local test local test runfiles com github cockroachdb cockroach external com github cockroachdb sqllogictest test index orderby nosort slt good test statements progress home roach cache bazel bazel roach sandbox processwrapper sandbox execroot com github cockroachdb cockroach bazel out dbg bin pkg sql sqlitelogictest tests local local test local test runfiles com github cockroachdb cockroach external com github cockroachdb sqllogictest test index orderby nosort slt good test statements progress home roach cache bazel bazel roach sandbox processwrapper sandbox execroot com github cockroachdb cockroach bazel out dbg bin pkg sql sqlitelogictest tests local local test local test runfiles com github cockroachdb cockroach external com github cockroachdb sqllogictest test index orderby nosort slt good test statements progress home roach cache bazel bazel roach sandbox processwrapper sandbox execroot com github cockroachdb cockroach bazel out dbg bin pkg sql sqlitelogictest tests local local test local test runfiles com github cockroachdb cockroach external com github cockroachdb sqllogictest test index orderby nosort slt good test statements progress home roach cache bazel bazel roach sandbox processwrapper sandbox execroot com github cockroachdb cockroach bazel out dbg bin pkg sql sqlitelogictest tests local local test local test runfiles com github cockroachdb cockroach external com github cockroachdb sqllogictest test index orderby nosort slt good test statements progress home roach cache bazel bazel roach sandbox processwrapper sandbox execroot com github cockroachdb cockroach bazel out dbg bin pkg sql sqlitelogictest tests local local test local test runfiles com github cockroachdb cockroach external com github cockroachdb sqllogictest test index orderby nosort slt good test statements progress home roach cache bazel bazel roach sandbox processwrapper sandbox execroot com github cockroachdb cockroach bazel out dbg bin pkg sql sqlitelogictest tests local local test local test runfiles com github cockroachdb cockroach external com github cockroachdb sqllogictest test index orderby nosort slt good test statements progress home roach cache bazel bazel roach sandbox processwrapper sandbox execroot com github cockroachdb cockroach bazel out dbg bin pkg sql sqlitelogictest tests local local test local test runfiles com github cockroachdb cockroach external com github cockroachdb sqllogictest test index orderby nosort slt good test statements progress home roach cache bazel bazel roach sandbox processwrapper sandbox execroot com github cockroachdb cockroach bazel out dbg bin pkg sql sqlitelogictest tests local local test local test runfiles com github cockroachdb cockroach external com github cockroachdb sqllogictest test index orderby nosort slt good test statements progress home roach cache bazel bazel roach sandbox processwrapper sandbox execroot com github cockroachdb cockroach bazel out dbg bin pkg sql sqlitelogictest tests local local test local test runfiles com github cockroachdb cockroach external com github cockroachdb sqllogictest test index orderby nosort slt good test statements progress home roach cache bazel bazel roach sandbox processwrapper sandbox execroot com github cockroachdb cockroach bazel out dbg bin pkg sql sqlitelogictest tests local local test local test runfiles com github cockroachdb cockroach external com github cockroachdb sqllogictest test index orderby nosort slt good test statements progress home roach cache bazel bazel roach sandbox processwrapper sandbox execroot com github cockroachdb cockroach bazel out dbg bin pkg sql sqlitelogictest tests local local test local test runfiles com github cockroachdb cockroach external com github cockroachdb sqllogictest test index orderby nosort slt good test statements progress home roach cache bazel bazel roach sandbox processwrapper sandbox execroot com github cockroachdb cockroach bazel out dbg bin pkg sql sqlitelogictest tests local local test local test runfiles com github cockroachdb cockroach external com github cockroachdb sqllogictest test index orderby nosort slt good test statements progress home roach cache bazel bazel roach sandbox processwrapper sandbox execroot com github cockroachdb cockroach bazel out dbg bin pkg sql sqlitelogictest tests local local test local test runfiles com github cockroachdb cockroach external com github cockroachdb sqllogictest test index orderby nosort slt good test statements progress home roach cache bazel bazel roach sandbox processwrapper sandbox execroot com github cockroachdb cockroach bazel out dbg bin pkg sql sqlitelogictest tests local local test local test runfiles com github cockroachdb cockroach external com github cockroachdb sqllogictest test index orderby nosort slt good test statements progress home roach cache bazel bazel roach sandbox processwrapper sandbox execroot com github cockroachdb cockroach bazel out dbg bin pkg sql sqlitelogictest tests local local test local test runfiles com github cockroachdb cockroach external com github cockroachdb sqllogictest test index orderby nosort slt good test statements progress home roach cache bazel bazel roach sandbox processwrapper sandbox execroot com github cockroachdb cockroach bazel out dbg bin pkg sql sqlitelogictest tests local local test local test runfiles com github cockroachdb cockroach external com github cockroachdb sqllogictest test index orderby nosort slt good test statements progress home roach cache bazel bazel roach sandbox processwrapper sandbox execroot com github cockroachdb cockroach bazel out dbg bin pkg sql sqlitelogictest tests local local test local test runfiles com github cockroachdb cockroach external com github cockroachdb sqllogictest test index orderby nosort slt good test statements progress home roach cache bazel bazel roach sandbox processwrapper sandbox execroot com github cockroachdb cockroach bazel out dbg bin pkg sql sqlitelogictest tests local local test local test runfiles com github cockroachdb cockroach external com github cockroachdb sqllogictest test index orderby nosort slt good test statements progress home roach cache bazel bazel roach sandbox processwrapper sandbox execroot com github cockroachdb cockroach bazel out dbg bin pkg sql sqlitelogictest tests local local test local test runfiles com github cockroachdb cockroach external com github cockroachdb sqllogictest test index orderby nosort slt good test statements progress home roach cache bazel bazel roach sandbox processwrapper sandbox execroot com github cockroachdb cockroach bazel out dbg bin pkg sql sqlitelogictest tests local local test local test runfiles com github cockroachdb cockroach external com github cockroachdb sqllogictest test index orderby nosort slt good test statements progress home roach cache bazel bazel roach sandbox processwrapper sandbox execroot com github cockroachdb cockroach bazel out dbg bin pkg sql sqlitelogictest tests local local test local test runfiles com github cockroachdb cockroach external com github cockroachdb sqllogictest test index orderby nosort slt good test statements progress home roach cache bazel bazel roach sandbox processwrapper sandbox execroot com github cockroachdb cockroach bazel out dbg bin pkg sql sqlitelogictest tests local local test local test runfiles com github cockroachdb cockroach external com github cockroachdb sqllogictest test index orderby nosort slt good test statements progress home roach cache bazel bazel roach sandbox processwrapper sandbox execroot com github cockroachdb cockroach bazel out dbg bin pkg sql sqlitelogictest tests local local test local test runfiles com github cockroachdb cockroach external com github cockroachdb sqllogictest test index orderby nosort slt good test statements progress home roach cache bazel bazel roach sandbox processwrapper sandbox execroot com github cockroachdb cockroach bazel out dbg bin pkg sql sqlitelogictest tests local local test local test runfiles com github cockroachdb cockroach external com github cockroachdb sqllogictest test index orderby nosort slt good test statements logic go pq streamer budget memory budget exceeded bytes requested currently allocated bytes in budget done home roach cache bazel bazel roach sandbox processwrapper sandbox execroot com github cockroachdb cockroach bazel out dbg bin pkg sql sqlitelogictest tests local local test local test runfiles com github cockroachdb cockroach external com github cockroachdb sqllogictest test index orderby nosort slt good test with config local tests failures logic go home roach cache bazel bazel roach sandbox processwrapper sandbox execroot com github cockroachdb cockroach bazel out dbg bin pkg sql sqlitelogictest tests local local test local test runfiles com github cockroachdb cockroach external com github cockroachdb sqllogictest test index orderby nosort slt good test error while processing logic go home roach cache bazel bazel roach sandbox processwrapper sandbox execroot com github cockroachdb cockroach bazel out dbg bin pkg sql sqlitelogictest tests local local test local test runfiles com github cockroachdb cockroach external com github cockroachdb sqllogictest test index orderby nosort slt good test too many errors encountered skipping the rest of the input panic go test log scope end fail testsqllitelogic testindexorderby good test help see also | 0 |
121,071 | 25,921,734,077 | IssuesEvent | 2022-12-15 22:45:46 | ni/nimi-python | https://api.github.com/repos/ni/nimi-python | closed | Codegen only the attribute classes that are used | enhancement wontfix codegen | ### Description of issue
Currently, the generator generates all the Attribute classes in `_attributes.py.mako` for all drivers even if some of them are not used.
We should make the generator smarter so that only the Attribute classes that are used get generated.
Kindly refer to https://github.com/ni/nimi-python/pull/1738#discussion_r904141387 for more details. | 1.0 | Codegen only the attribute classes that are used - ### Description of issue
Currently, the generator generates all the Attribute classes in `_attributes.py.mako` for all drivers even if some of them are not used.
We should make the generator smarter so that only the Attribute classes that are used get generated.
Kindly refer to https://github.com/ni/nimi-python/pull/1738#discussion_r904141387 for more details. | non_priority | codegen only the attribute classes that are used description of issue currently the generator generates all the attribute classes in attributes py mako for all drivers even if some of them are not used we should make the generator smarter so that only the attribute classes that are used get generated kindly refer to for more details | 0 |
110,570 | 23,957,815,994 | IssuesEvent | 2022-09-12 16:18:09 | appsmithorg/appsmith | https://api.github.com/repos/appsmithorg/appsmith | closed | [Bug]: pagination fields are too smal | Bug Needs Triaging BE Coders Pod GraphQL Plugin Integrations Pod | ### Is there an existing issue for this?
- [X] I have searched the existing issues
### Description
1. go here: http://3.111.33.176/applications
2. open app in edit mode
3. go to page GitHub
4. open query GetSixIssues
5. go to the pagination tab
Under cursor based pagination, these fields on the right are too small - the input is showing trucated
![Uploading Screenshot 2022-09-05 at 17.24.41.png…]()
### Steps To Reproduce
-
### Public Sample App
_No response_
### Version
cloud | 1.0 | [Bug]: pagination fields are too smal - ### Is there an existing issue for this?
- [X] I have searched the existing issues
### Description
1. go here: http://3.111.33.176/applications
2. open app in edit mode
3. go to page GitHub
4. open query GetSixIssues
5. go to the pagination tab
Under cursor based pagination, these fields on the right are too small - the input is showing trucated
![Uploading Screenshot 2022-09-05 at 17.24.41.png…]()
### Steps To Reproduce
-
### Public Sample App
_No response_
### Version
cloud | non_priority | pagination fields are too smal is there an existing issue for this i have searched the existing issues description go here open app in edit mode go to page github open query getsixissues go to the pagination tab under cursor based pagination these fields on the right are too small the input is showing trucated steps to reproduce public sample app no response version cloud | 0 |
31,115 | 14,861,292,533 | IssuesEvent | 2021-01-18 22:28:26 | dotnet/project-system | https://api.github.com/repos/dotnet/project-system | closed | Delay initializing BuildUpToDateCheck and PackageRestoreProgressTracker for inactive project configurations | Bug Bash Performance-Scenario-Solution-Open Tenet-Performance Triage-Approved | Current, inactive project configurations can be loaded in various conditions, either because the mismatching solution configurations, or when an extension or the developer access configured level properties (like appDesigner). AutoLoadComponents, especially dynamic loaded components are triggered in those configurations, which initializes dataflows, especially DT build dataflow, which is not essential until the configuration is activated. If we can delay initialize some of the auto load components until the configuration is activated/implicitly activated, it will reduce some of those initialization/overhead. BuildUpToDateCheck and PackageRestoreProgressTracker are two of those components inside ML project system, which can be delayed to establish dataflow subscription, until the configuration is activated.
| True | Delay initializing BuildUpToDateCheck and PackageRestoreProgressTracker for inactive project configurations - Current, inactive project configurations can be loaded in various conditions, either because the mismatching solution configurations, or when an extension or the developer access configured level properties (like appDesigner). AutoLoadComponents, especially dynamic loaded components are triggered in those configurations, which initializes dataflows, especially DT build dataflow, which is not essential until the configuration is activated. If we can delay initialize some of the auto load components until the configuration is activated/implicitly activated, it will reduce some of those initialization/overhead. BuildUpToDateCheck and PackageRestoreProgressTracker are two of those components inside ML project system, which can be delayed to establish dataflow subscription, until the configuration is activated.
| non_priority | delay initializing builduptodatecheck and packagerestoreprogresstracker for inactive project configurations current inactive project configurations can be loaded in various conditions either because the mismatching solution configurations or when an extension or the developer access configured level properties like appdesigner autoloadcomponents especially dynamic loaded components are triggered in those configurations which initializes dataflows especially dt build dataflow which is not essential until the configuration is activated if we can delay initialize some of the auto load components until the configuration is activated implicitly activated it will reduce some of those initialization overhead builduptodatecheck and packagerestoreprogresstracker are two of those components inside ml project system which can be delayed to establish dataflow subscription until the configuration is activated | 0 |
225,387 | 24,828,517,025 | IssuesEvent | 2022-10-25 23:39:36 | samq-ghdemo/SEARCH-NCJIS-nibrs | https://api.github.com/repos/samq-ghdemo/SEARCH-NCJIS-nibrs | reopened | CVE-2022-40153 (High) detected in woodstox-core-5.0.3.jar | security vulnerability | ## CVE-2022-40153 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>woodstox-core-5.0.3.jar</b></p></summary>
<p>Woodstox is a high-performance XML processor that
implements Stax (JSR-173), SAX2 and Stax2 APIs</p>
<p>Library home page: <a href="https://github.com/FasterXML/woodstox">https://github.com/FasterXML/woodstox</a></p>
<p>Path to dependency file: /web/nibrs-web/pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/com/fasterxml/woodstox/woodstox-core/5.0.3/woodstox-core-5.0.3.jar,/web/nibrs-web/target/nibrs-web/WEB-INF/lib/woodstox-core-5.0.3.jar,/home/wss-scanner/.m2/repository/com/fasterxml/woodstox/woodstox-core/5.0.3/woodstox-core-5.0.3.jar,/home/wss-scanner/.m2/repository/com/fasterxml/woodstox/woodstox-core/5.0.3/woodstox-core-5.0.3.jar</p>
<p>
Dependency Hierarchy:
- :x: **woodstox-core-5.0.3.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>
Those using Xstream to seralize XML data may be vulnerable to Denial of Service attacks (DOS). If the parser is running on user supplied input, an attacker may supply content that causes the parser to crash by stackoverflow. This effect may support a denial of service attack.
<p>Publish Date: 2022-09-16
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-40153>CVE-2022-40153</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Release Date: 2022-09-16</p>
<p>Fix Resolution: woodstox-core-5.4.0,woodstox-core-6.4.0</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-40153 (High) detected in woodstox-core-5.0.3.jar - ## CVE-2022-40153 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>woodstox-core-5.0.3.jar</b></p></summary>
<p>Woodstox is a high-performance XML processor that
implements Stax (JSR-173), SAX2 and Stax2 APIs</p>
<p>Library home page: <a href="https://github.com/FasterXML/woodstox">https://github.com/FasterXML/woodstox</a></p>
<p>Path to dependency file: /web/nibrs-web/pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/com/fasterxml/woodstox/woodstox-core/5.0.3/woodstox-core-5.0.3.jar,/web/nibrs-web/target/nibrs-web/WEB-INF/lib/woodstox-core-5.0.3.jar,/home/wss-scanner/.m2/repository/com/fasterxml/woodstox/woodstox-core/5.0.3/woodstox-core-5.0.3.jar,/home/wss-scanner/.m2/repository/com/fasterxml/woodstox/woodstox-core/5.0.3/woodstox-core-5.0.3.jar</p>
<p>
Dependency Hierarchy:
- :x: **woodstox-core-5.0.3.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>
Those using Xstream to seralize XML data may be vulnerable to Denial of Service attacks (DOS). If the parser is running on user supplied input, an attacker may supply content that causes the parser to crash by stackoverflow. This effect may support a denial of service attack.
<p>Publish Date: 2022-09-16
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-40153>CVE-2022-40153</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Release Date: 2022-09-16</p>
<p>Fix Resolution: woodstox-core-5.4.0,woodstox-core-6.4.0</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 woodstox core jar cve high severity vulnerability vulnerable library woodstox core jar woodstox is a high performance xml processor that implements stax jsr and apis library home page a href path to dependency file web nibrs web pom xml path to vulnerable library home wss scanner repository com fasterxml woodstox woodstox core woodstox core jar web nibrs web target nibrs web web inf lib woodstox core jar home wss scanner repository com fasterxml woodstox woodstox core woodstox core jar home wss scanner repository com fasterxml woodstox woodstox core woodstox core jar dependency hierarchy x woodstox core jar vulnerable library found in base branch master vulnerability details those using xstream to seralize xml data may be vulnerable to denial of service attacks dos if the parser is running on user supplied input an attacker may supply content that causes the parser to crash by stackoverflow this effect may support a denial of service attack 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 woodstox core woodstox core check this box to open an automated fix pr | 0 |
18,658 | 4,290,620,314 | IssuesEvent | 2016-07-18 10:30:51 | Microsoft/visualfsharp | https://api.github.com/repos/Microsoft/visualfsharp | closed | DocBug at MSDN: not all keywords reserved for future use are listed | Documentation | At [Keywords](https://msdn.microsoft.com/en-us/library/dd233249.aspx) MSDN page there is a section about tokens that are reserved as keywords for future expansion of the F# language.
The table do not contain some of the keywords defined in both language specifications [F# 3.0](http://fsharp.org/specs/language-spec/3.0/FSharpSpec-3.0-final.pdf) and [F# 3.1](http://fsharp.org/specs/language-spec/3.1/FSharpSpec-3.1-working.docx)
* fori
* measure
* params
* recursive
There are some entries in the table not reserved in the language specification:
* event
* external
Those also do not produce "The identifier '%s' is reserved for future use by F#" warning.
| 1.0 | DocBug at MSDN: not all keywords reserved for future use are listed - At [Keywords](https://msdn.microsoft.com/en-us/library/dd233249.aspx) MSDN page there is a section about tokens that are reserved as keywords for future expansion of the F# language.
The table do not contain some of the keywords defined in both language specifications [F# 3.0](http://fsharp.org/specs/language-spec/3.0/FSharpSpec-3.0-final.pdf) and [F# 3.1](http://fsharp.org/specs/language-spec/3.1/FSharpSpec-3.1-working.docx)
* fori
* measure
* params
* recursive
There are some entries in the table not reserved in the language specification:
* event
* external
Those also do not produce "The identifier '%s' is reserved for future use by F#" warning.
| non_priority | docbug at msdn not all keywords reserved for future use are listed at msdn page there is a section about tokens that are reserved as keywords for future expansion of the f language the table do not contain some of the keywords defined in both language specifications and fori measure params recursive there are some entries in the table not reserved in the language specification event external those also do not produce the identifier s is reserved for future use by f warning | 0 |
12,137 | 19,028,904,242 | IssuesEvent | 2021-11-24 08:32:49 | listen1/listen1_chrome_extension | https://api.github.com/repos/listen1/listen1_chrome_extension | closed | feat: myplaylist crud support | requirement | myplaylist
- [x] create
- [x] read
- [x] update
- [x] delete
- [ ] reorder -> wait for drag drop pr
favorite playlist
- [x] create
- [x] read
- [x] update
- [x] delete
- [ ] reorder-> wait for drag drop pr
tracks in playlist
- [x] create
- [x] read
- [x] update
- [x] delete
- [ ] reorder-> wait for drag drop pr | 1.0 | feat: myplaylist crud support - myplaylist
- [x] create
- [x] read
- [x] update
- [x] delete
- [ ] reorder -> wait for drag drop pr
favorite playlist
- [x] create
- [x] read
- [x] update
- [x] delete
- [ ] reorder-> wait for drag drop pr
tracks in playlist
- [x] create
- [x] read
- [x] update
- [x] delete
- [ ] reorder-> wait for drag drop pr | non_priority | feat myplaylist crud support myplaylist create read update delete reorder wait for drag drop pr favorite playlist create read update delete reorder wait for drag drop pr tracks in playlist create read update delete reorder wait for drag drop pr | 0 |
4,043 | 2,713,874,864 | IssuesEvent | 2015-04-09 21:53:14 | cgeo/cgeo | https://api.github.com/repos/cgeo/cgeo | closed | Log type field to small when logging a GK | Frontend Design GK low | I attended an opencaching event today and presented the upcoming GK feature.
While the feature is considered as really great from the audience some of them suggested to have a better logging view.
Due to the fact, that there is a new field for the time in the first row, the log type field became rather small, so that only a few letters are visisble.
The proposal was to somehow rearrange the view to give more room for the log type.
I currently do not have any great idea how this could look like.
Maybe we can move the date and time to a separate row below the log type? | 1.0 | Log type field to small when logging a GK - I attended an opencaching event today and presented the upcoming GK feature.
While the feature is considered as really great from the audience some of them suggested to have a better logging view.
Due to the fact, that there is a new field for the time in the first row, the log type field became rather small, so that only a few letters are visisble.
The proposal was to somehow rearrange the view to give more room for the log type.
I currently do not have any great idea how this could look like.
Maybe we can move the date and time to a separate row below the log type? | non_priority | log type field to small when logging a gk i attended an opencaching event today and presented the upcoming gk feature while the feature is considered as really great from the audience some of them suggested to have a better logging view due to the fact that there is a new field for the time in the first row the log type field became rather small so that only a few letters are visisble the proposal was to somehow rearrange the view to give more room for the log type i currently do not have any great idea how this could look like maybe we can move the date and time to a separate row below the log type | 0 |
146,867 | 23,135,081,787 | IssuesEvent | 2022-07-28 13:44:22 | carbon-design-system/carbon-platform | https://api.github.com/repos/carbon-design-system/carbon-platform | closed | MdxSanitizer - Contents Not Found + Scripts tags UI/UX | type: enhancement 💡 role: design 🎨 | **Summary**
1 - If the application fails to retrieve the contents of a given github mdx page, what should happen in the UI? (this is a full page error).
- this can just be a page not found
Example: supplied github route doesn't exist, requested resource is not allowed (authentication error...)
2 - If a remote mdx contains a script tag, we cannot allow that script for security concerns reasons, what should the feedback to the user be?
Options:
- Remove script tag
- Replace with inline notification error, what should that say?
- Full page error
- some other UX?
Example:
```mdx
# Hi
<div>Hello</div>
<script>alert(Date.now());</script>
```
Replace this with an inline notification :
(Replace import with script)
<img width="1020" alt="image" src="https://user-images.githubusercontent.com/40550942/179086629-4905f9d6-7b3b-4415-8dbc-9a8e0ce225ab.png">
<img width="1055" alt="image" src="https://user-images.githubusercontent.com/40550942/179087080-bd6290b3-e32c-4348-8b8b-711a285587f3.png">
**Job stories**
What value will this deliver?
1. When my remote mdx content has some type of error or defect, I want the app to handle it gracefully, so I can have the best user experience.
**Acceptance criteria**
What requirements must be met to complete this request?
1. Design specs for detailed cases
| 1.0 | MdxSanitizer - Contents Not Found + Scripts tags UI/UX - **Summary**
1 - If the application fails to retrieve the contents of a given github mdx page, what should happen in the UI? (this is a full page error).
- this can just be a page not found
Example: supplied github route doesn't exist, requested resource is not allowed (authentication error...)
2 - If a remote mdx contains a script tag, we cannot allow that script for security concerns reasons, what should the feedback to the user be?
Options:
- Remove script tag
- Replace with inline notification error, what should that say?
- Full page error
- some other UX?
Example:
```mdx
# Hi
<div>Hello</div>
<script>alert(Date.now());</script>
```
Replace this with an inline notification :
(Replace import with script)
<img width="1020" alt="image" src="https://user-images.githubusercontent.com/40550942/179086629-4905f9d6-7b3b-4415-8dbc-9a8e0ce225ab.png">
<img width="1055" alt="image" src="https://user-images.githubusercontent.com/40550942/179087080-bd6290b3-e32c-4348-8b8b-711a285587f3.png">
**Job stories**
What value will this deliver?
1. When my remote mdx content has some type of error or defect, I want the app to handle it gracefully, so I can have the best user experience.
**Acceptance criteria**
What requirements must be met to complete this request?
1. Design specs for detailed cases
| non_priority | mdxsanitizer contents not found scripts tags ui ux summary if the application fails to retrieve the contents of a given github mdx page what should happen in the ui this is a full page error this can just be a page not found example supplied github route doesn t exist requested resource is not allowed authentication error if a remote mdx contains a script tag we cannot allow that script for security concerns reasons what should the feedback to the user be options remove script tag replace with inline notification error what should that say full page error some other ux example mdx hi hello alert date now replace this with an inline notification replace import with script img width alt image src img width alt image src job stories what value will this deliver when my remote mdx content has some type of error or defect i want the app to handle it gracefully so i can have the best user experience acceptance criteria what requirements must be met to complete this request design specs for detailed cases | 0 |
20,287 | 4,534,841,881 | IssuesEvent | 2016-09-08 15:37:50 | matplotlib/matplotlib | https://api.github.com/repos/matplotlib/matplotlib | closed | It is getting increasingly difficult to build the matplotlib documentation | Difficulty: Easy Documentation | I've had to build the matplotlib documentation several times in the past couple of months, and everytime, it is getting increasingly difficult to build the documentation.
The number of packages required has drastically increased in the past year or so, including packages where the installation instruction is pretty much missing (http://matplotlib.org/basemap/users/installing.html)
Having had to set up a new computer recently, I am running in many problems that I believe many core devs are not aware.
This unfortunately increases the level required for new contributors to do documentation changes. I would consider removing a bunch of dependencies…
Note that the doc/README.txt only mentions that sphinx is required, and the documentation then crashes after 5 minutes of build.
Here is an uncomplete list of packages required to build the documentation: numpydoc, basemap, colorspacious, mock, ipython (!!!!) | 1.0 | It is getting increasingly difficult to build the matplotlib documentation - I've had to build the matplotlib documentation several times in the past couple of months, and everytime, it is getting increasingly difficult to build the documentation.
The number of packages required has drastically increased in the past year or so, including packages where the installation instruction is pretty much missing (http://matplotlib.org/basemap/users/installing.html)
Having had to set up a new computer recently, I am running in many problems that I believe many core devs are not aware.
This unfortunately increases the level required for new contributors to do documentation changes. I would consider removing a bunch of dependencies…
Note that the doc/README.txt only mentions that sphinx is required, and the documentation then crashes after 5 minutes of build.
Here is an uncomplete list of packages required to build the documentation: numpydoc, basemap, colorspacious, mock, ipython (!!!!) | non_priority | it is getting increasingly difficult to build the matplotlib documentation i ve had to build the matplotlib documentation several times in the past couple of months and everytime it is getting increasingly difficult to build the documentation the number of packages required has drastically increased in the past year or so including packages where the installation instruction is pretty much missing having had to set up a new computer recently i am running in many problems that i believe many core devs are not aware this unfortunately increases the level required for new contributors to do documentation changes i would consider removing a bunch of dependencies… note that the doc readme txt only mentions that sphinx is required and the documentation then crashes after minutes of build here is an uncomplete list of packages required to build the documentation numpydoc basemap colorspacious mock ipython | 0 |
26,073 | 26,375,560,150 | IssuesEvent | 2023-01-12 01:55:42 | MAAP-Project/ZenHub | https://api.github.com/repos/MAAP-Project/ZenHub | opened | Jobs UI: table-view needs some sort of affordance to indicate that you click a row to show the Details Panel | Usability | some affordances we could try:
- mouseover color
- mouseover icon shows up
| True | Jobs UI: table-view needs some sort of affordance to indicate that you click a row to show the Details Panel - some affordances we could try:
- mouseover color
- mouseover icon shows up
| non_priority | jobs ui table view needs some sort of affordance to indicate that you click a row to show the details panel some affordances we could try mouseover color mouseover icon shows up | 0 |
52,123 | 6,219,911,963 | IssuesEvent | 2017-07-09 17:55:43 | publiclab/plotsbot | https://api.github.com/repos/publiclab/plotsbot | closed | Integrate Coveralls | enhancement help wanted testing | Coveralls integration is something very platform / CI / testing library specific. Figure out a way to make it work. | 1.0 | Integrate Coveralls - Coveralls integration is something very platform / CI / testing library specific. Figure out a way to make it work. | non_priority | integrate coveralls coveralls integration is something very platform ci testing library specific figure out a way to make it work | 0 |
101,354 | 16,504,109,199 | IssuesEvent | 2021-05-25 17:06:16 | sharethrough/mikro-orm | https://api.github.com/repos/sharethrough/mikro-orm | opened | CVE-2021-23386 (High) detected in dns-packet-1.3.1.tgz | security vulnerability | ## CVE-2021-23386 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>dns-packet-1.3.1.tgz</b></p></summary>
<p>An abstract-encoding compliant module for encoding / decoding DNS packets</p>
<p>Library home page: <a href="https://registry.npmjs.org/dns-packet/-/dns-packet-1.3.1.tgz">https://registry.npmjs.org/dns-packet/-/dns-packet-1.3.1.tgz</a></p>
<p>Path to dependency file: mikro-orm/docs/package.json</p>
<p>Path to vulnerable library: mikro-orm/docs/node_modules/dns-packet</p>
<p>
Dependency Hierarchy:
- core-2.0.0-beta.0.tgz (Root Library)
- webpack-dev-server-3.11.2.tgz
- bonjour-3.5.0.tgz
- multicast-dns-6.2.3.tgz
- :x: **dns-packet-1.3.1.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/sharethrough/mikro-orm/commit/efde88fb861a10bc5c38b3a93138e8ea2b29e972">efde88fb861a10bc5c38b3a93138e8ea2b29e972</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 dns-packet before 5.2.2. It creates buffers with allocUnsafe and does not always fill them before forming network packets. This can expose internal application memory over unencrypted network when querying crafted invalid domain names.
<p>Publish Date: 2021-05-20
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-23386>CVE-2021-23386</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.7</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: Low
- User Interaction: None
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: High
- 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-2021-23386">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-23386</a></p>
<p>Release Date: 2021-05-20</p>
<p>Fix Resolution: dns-packet - 5.2.2</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":false,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"dns-packet","packageVersion":"1.3.1","packageFilePaths":["/docs/package.json"],"isTransitiveDependency":true,"dependencyTree":"@docusaurus/core:2.0.0-beta.0;webpack-dev-server:3.11.2;bonjour:3.5.0;multicast-dns:6.2.3;dns-packet:1.3.1","isMinimumFixVersionAvailable":true,"minimumFixVersion":"dns-packet - 5.2.2"}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2021-23386","vulnerabilityDetails":"This affects the package dns-packet before 5.2.2. It creates buffers with allocUnsafe and does not always fill them before forming network packets. This can expose internal application memory over unencrypted network when querying crafted invalid domain names.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-23386","cvss3Severity":"high","cvss3Score":"7.7","cvss3Metrics":{"A":"Low","AC":"High","PR":"Low","S":"Changed","C":"High","UI":"None","AV":"Network","I":"Low"},"extraData":{}}</REMEDIATE> --> | True | CVE-2021-23386 (High) detected in dns-packet-1.3.1.tgz - ## CVE-2021-23386 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>dns-packet-1.3.1.tgz</b></p></summary>
<p>An abstract-encoding compliant module for encoding / decoding DNS packets</p>
<p>Library home page: <a href="https://registry.npmjs.org/dns-packet/-/dns-packet-1.3.1.tgz">https://registry.npmjs.org/dns-packet/-/dns-packet-1.3.1.tgz</a></p>
<p>Path to dependency file: mikro-orm/docs/package.json</p>
<p>Path to vulnerable library: mikro-orm/docs/node_modules/dns-packet</p>
<p>
Dependency Hierarchy:
- core-2.0.0-beta.0.tgz (Root Library)
- webpack-dev-server-3.11.2.tgz
- bonjour-3.5.0.tgz
- multicast-dns-6.2.3.tgz
- :x: **dns-packet-1.3.1.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/sharethrough/mikro-orm/commit/efde88fb861a10bc5c38b3a93138e8ea2b29e972">efde88fb861a10bc5c38b3a93138e8ea2b29e972</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 dns-packet before 5.2.2. It creates buffers with allocUnsafe and does not always fill them before forming network packets. This can expose internal application memory over unencrypted network when querying crafted invalid domain names.
<p>Publish Date: 2021-05-20
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-23386>CVE-2021-23386</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.7</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: Low
- User Interaction: None
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: High
- 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-2021-23386">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-23386</a></p>
<p>Release Date: 2021-05-20</p>
<p>Fix Resolution: dns-packet - 5.2.2</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":false,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"dns-packet","packageVersion":"1.3.1","packageFilePaths":["/docs/package.json"],"isTransitiveDependency":true,"dependencyTree":"@docusaurus/core:2.0.0-beta.0;webpack-dev-server:3.11.2;bonjour:3.5.0;multicast-dns:6.2.3;dns-packet:1.3.1","isMinimumFixVersionAvailable":true,"minimumFixVersion":"dns-packet - 5.2.2"}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2021-23386","vulnerabilityDetails":"This affects the package dns-packet before 5.2.2. It creates buffers with allocUnsafe and does not always fill them before forming network packets. This can expose internal application memory over unencrypted network when querying crafted invalid domain names.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-23386","cvss3Severity":"high","cvss3Score":"7.7","cvss3Metrics":{"A":"Low","AC":"High","PR":"Low","S":"Changed","C":"High","UI":"None","AV":"Network","I":"Low"},"extraData":{}}</REMEDIATE> --> | non_priority | cve high detected in dns packet tgz cve high severity vulnerability vulnerable library dns packet tgz an abstract encoding compliant module for encoding decoding dns packets library home page a href path to dependency file mikro orm docs package json path to vulnerable library mikro orm docs node modules dns packet dependency hierarchy core beta tgz root library webpack dev server tgz bonjour tgz multicast dns tgz x dns packet tgz vulnerable library found in head commit a href found in base branch master vulnerability details this affects the package dns packet before it creates buffers with allocunsafe and does not always fill them before forming network packets this can expose internal application memory over unencrypted network when querying crafted invalid domain names publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity high privileges required low user interaction none scope changed impact metrics confidentiality impact high 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 dns packet isopenpronvulnerability false ispackagebased true isdefaultbranch true packages istransitivedependency true dependencytree docusaurus core beta webpack dev server bonjour multicast dns dns packet isminimumfixversionavailable true minimumfixversion dns packet basebranches vulnerabilityidentifier cve vulnerabilitydetails this affects the package dns packet before it creates buffers with allocunsafe and does not always fill them before forming network packets this can expose internal application memory over unencrypted network when querying crafted invalid domain names vulnerabilityurl | 0 |
15,557 | 8,957,393,647 | IssuesEvent | 2019-01-27 03:02:03 | simerplaha/SwayDB | https://api.github.com/repos/simerplaha/SwayDB | closed | Performance improvement for forward & backward iterators when there are too many dead updates within the current Level's iteration | Performance | Iterators can be slower if there are too many dead updates between two keys.
Put checkpoint can be added or something similar to help iterators skip dead updates entirely jump to the next valid key instantly.
A test case would be: Suppose there are 100,000 keys. Keys 1 & 100,000 are valid keys and updates were submitted for keys 2 to 99,999 that do not exist. This effects iterator performance when reading from key 1 to 100,000. | True | Performance improvement for forward & backward iterators when there are too many dead updates within the current Level's iteration - Iterators can be slower if there are too many dead updates between two keys.
Put checkpoint can be added or something similar to help iterators skip dead updates entirely jump to the next valid key instantly.
A test case would be: Suppose there are 100,000 keys. Keys 1 & 100,000 are valid keys and updates were submitted for keys 2 to 99,999 that do not exist. This effects iterator performance when reading from key 1 to 100,000. | non_priority | performance improvement for forward backward iterators when there are too many dead updates within the current level s iteration iterators can be slower if there are too many dead updates between two keys put checkpoint can be added or something similar to help iterators skip dead updates entirely jump to the next valid key instantly a test case would be suppose there are keys keys are valid keys and updates were submitted for keys to that do not exist this effects iterator performance when reading from key to | 0 |
292,620 | 25,226,616,498 | IssuesEvent | 2022-11-14 16:24:32 | hasura/graphql-engine | https://api.github.com/repos/hasura/graphql-engine | closed | server/tests: port pytests to hspec integration test suite | c/tests 🧪 | Relates to https://github.com/hasura/graphql-engine/issues/7760
This is a placeholder for now, for related tests as we think of them. But we might use this to coordinate work to gradually port pytests to hspecs, now that the [POC integration test suite](https://github.com/hasura/graphql-engine/issues/7760) is done. In rough priority order:
- [x] https://github.com/hasura/graphql-engine/issues/8433#issue-1214623537
- [x] [server/tests: organise hspec integration tests to mirror product architecture](https://github.com/hasura/graphql-engine-mono/issues/4757)
- [x] https://github.com/hasura/graphql-engine/issues/8172
- [ ] #8891
- [ ] [BigQuery schema, queries](https://github.com/hasura/graphql-engine-mono/issues/4758)
- [ ] Citus schema, queries, mutations, subscriptions
- [ ] SQL Server schema, queries, mutations, subscriptions
- [ ] remove duplicate Postgres pytests (the goal is _not_ to port over all Postgres pytests, only those testing common backend features)
- [ ] [run hspec tests on ARM](https://github.com/hasura/graphql-engine-mono/issues/3511)
- [ ] [support multitenant tests](https://github.com/hasura/graphql-engine-mono/issues/3680)
- [ ] parallelise test execution (or check it)
- [ ] DB healthcheck
- [ ] [server/bigquery: investigate bigquery API performance improvements](https://github.com/hasura/graphql-engine-mono/issues/3683) | 1.0 | server/tests: port pytests to hspec integration test suite - Relates to https://github.com/hasura/graphql-engine/issues/7760
This is a placeholder for now, for related tests as we think of them. But we might use this to coordinate work to gradually port pytests to hspecs, now that the [POC integration test suite](https://github.com/hasura/graphql-engine/issues/7760) is done. In rough priority order:
- [x] https://github.com/hasura/graphql-engine/issues/8433#issue-1214623537
- [x] [server/tests: organise hspec integration tests to mirror product architecture](https://github.com/hasura/graphql-engine-mono/issues/4757)
- [x] https://github.com/hasura/graphql-engine/issues/8172
- [ ] #8891
- [ ] [BigQuery schema, queries](https://github.com/hasura/graphql-engine-mono/issues/4758)
- [ ] Citus schema, queries, mutations, subscriptions
- [ ] SQL Server schema, queries, mutations, subscriptions
- [ ] remove duplicate Postgres pytests (the goal is _not_ to port over all Postgres pytests, only those testing common backend features)
- [ ] [run hspec tests on ARM](https://github.com/hasura/graphql-engine-mono/issues/3511)
- [ ] [support multitenant tests](https://github.com/hasura/graphql-engine-mono/issues/3680)
- [ ] parallelise test execution (or check it)
- [ ] DB healthcheck
- [ ] [server/bigquery: investigate bigquery API performance improvements](https://github.com/hasura/graphql-engine-mono/issues/3683) | non_priority | server tests port pytests to hspec integration test suite relates to this is a placeholder for now for related tests as we think of them but we might use this to coordinate work to gradually port pytests to hspecs now that the is done in rough priority order citus schema queries mutations subscriptions sql server schema queries mutations subscriptions remove duplicate postgres pytests the goal is not to port over all postgres pytests only those testing common backend features parallelise test execution or check it db healthcheck | 0 |
2,982 | 2,787,845,266 | IssuesEvent | 2015-05-08 09:24:54 | HGustavs/LenaSYS | https://api.github.com/repos/HGustavs/LenaSYS | closed | Additional fix for #1300 | bug CodeViewer | The regex was not written correctly so lines like "<br> text" lead to some unexpected behavior. | 1.0 | Additional fix for #1300 - The regex was not written correctly so lines like "<br> text" lead to some unexpected behavior. | non_priority | additional fix for the regex was not written correctly so lines like text lead to some unexpected behavior | 0 |
124,069 | 16,569,286,138 | IssuesEvent | 2021-05-30 03:58:27 | RafaGomezGlez/WebVisualization | https://api.github.com/repos/RafaGomezGlez/WebVisualization | opened | Sorting Algorithms Visualisation Page | Design | Upgrade UX Design.
- [ ] Adobe XD Design
- [ ] HTML/CSS Implementation | 1.0 | Sorting Algorithms Visualisation Page - Upgrade UX Design.
- [ ] Adobe XD Design
- [ ] HTML/CSS Implementation | non_priority | sorting algorithms visualisation page upgrade ux design adobe xd design html css implementation | 0 |
8,132 | 2,963,948,080 | IssuesEvent | 2015-07-10 14:05:18 | PropelVentures/GenericPlatform | https://api.github.com/repos/PropelVentures/GenericPlatform | closed | Lists - Box Format | Fix Applied - Test Not Working to Spec | - Need Initial Box format to display fields like genericveryold
- with the Image field very prominent.
- It is OK if the Box style function has a requirement that the first field in the field list, is the image field.
| 1.0 | Lists - Box Format - - Need Initial Box format to display fields like genericveryold
- with the Image field very prominent.
- It is OK if the Box style function has a requirement that the first field in the field list, is the image field.
| non_priority | lists box format need initial box format to display fields like genericveryold with the image field very prominent it is ok if the box style function has a requirement that the first field in the field list is the image field | 0 |
258,659 | 27,570,704,163 | IssuesEvent | 2023-03-08 09:03:50 | ghc-dev/8060538_2339 | https://api.github.com/repos/ghc-dev/8060538_2339 | closed | guava-28.1-jre.jar: 1 vulnerabilities (highest severity is: 3.3) - autoclosed | Mend: dependency security vulnerability | <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>guava-28.1-jre.jar</b></p></summary>
<p>Guava is a suite of core and expanded libraries that include
utility classes, google's collections, io classes, and much
much more.</p>
<p>Library home page: <a href="https://github.com/google/guava">https://github.com/google/guava</a></p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/com/google/guava/guava/28.1-jre/guava-28.1-jre.jar</p>
<p>
<p>Found in HEAD commit: <a href="https://github.com/ghc-dev/8060538_2339/commit/38b50fba3ac6f33c817f3c7a50a222ce6f91c4bc">38b50fba3ac6f33c817f3c7a50a222ce6f91c4bc</a></p></details>
## Vulnerabilities
| CVE | Severity | <img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS | Dependency | Type | Fixed in (guava version) | Remediation Available |
| ------------- | ------------- | ----- | ----- | ----- | ------------- | --- |
| [CVE-2020-8908](https://www.mend.io/vulnerability-database/CVE-2020-8908) | <img src='https://whitesource-resources.whitesourcesoftware.com/low_vul.png' width=19 height=20> Low | 3.3 | guava-28.1-jre.jar | Direct | 30.0-android | ✅ |
## Details
<details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/low_vul.png' width=19 height=20> CVE-2020-8908</summary>
### Vulnerable Library - <b>guava-28.1-jre.jar</b></p>
<p>Guava is a suite of core and expanded libraries that include
utility classes, google's collections, io classes, and much
much more.</p>
<p>Library home page: <a href="https://github.com/google/guava">https://github.com/google/guava</a></p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/com/google/guava/guava/28.1-jre/guava-28.1-jre.jar</p>
<p>
Dependency Hierarchy:
- :x: **guava-28.1-jre.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/ghc-dev/8060538_2339/commit/38b50fba3ac6f33c817f3c7a50a222ce6f91c4bc">38b50fba3ac6f33c817f3c7a50a222ce6f91c4bc</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
A temp directory creation vulnerability exists in all versions of Guava, allowing an attacker with access to the machine to potentially access data in a temporary directory created by the Guava API com.google.common.io.Files.createTempDir(). By default, on unix-like systems, the created directory is world-readable (readable by an attacker with access to the system). The method in question has been marked @Deprecated in versions 30.0 and later and should not be used. For Android developers, we recommend choosing a temporary directory API provided by Android, such as context.getCacheDir(). For other Java developers, we recommend migrating to the Java 7 API java.nio.file.Files.createTempDirectory() which explicitly configures permissions of 700, or configuring the Java runtime's java.io.tmpdir system property to point to a location whose permissions are appropriately configured.
<p>Publish Date: 2020-12-10
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2020-8908>CVE-2020-8908</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>3.3</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: Low
- 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>
<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-8908">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-8908</a></p>
<p>Release Date: 2020-12-10</p>
<p>Fix Resolution: 30.0-android</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 | guava-28.1-jre.jar: 1 vulnerabilities (highest severity is: 3.3) - autoclosed - <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>guava-28.1-jre.jar</b></p></summary>
<p>Guava is a suite of core and expanded libraries that include
utility classes, google's collections, io classes, and much
much more.</p>
<p>Library home page: <a href="https://github.com/google/guava">https://github.com/google/guava</a></p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/com/google/guava/guava/28.1-jre/guava-28.1-jre.jar</p>
<p>
<p>Found in HEAD commit: <a href="https://github.com/ghc-dev/8060538_2339/commit/38b50fba3ac6f33c817f3c7a50a222ce6f91c4bc">38b50fba3ac6f33c817f3c7a50a222ce6f91c4bc</a></p></details>
## Vulnerabilities
| CVE | Severity | <img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS | Dependency | Type | Fixed in (guava version) | Remediation Available |
| ------------- | ------------- | ----- | ----- | ----- | ------------- | --- |
| [CVE-2020-8908](https://www.mend.io/vulnerability-database/CVE-2020-8908) | <img src='https://whitesource-resources.whitesourcesoftware.com/low_vul.png' width=19 height=20> Low | 3.3 | guava-28.1-jre.jar | Direct | 30.0-android | ✅ |
## Details
<details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/low_vul.png' width=19 height=20> CVE-2020-8908</summary>
### Vulnerable Library - <b>guava-28.1-jre.jar</b></p>
<p>Guava is a suite of core and expanded libraries that include
utility classes, google's collections, io classes, and much
much more.</p>
<p>Library home page: <a href="https://github.com/google/guava">https://github.com/google/guava</a></p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/com/google/guava/guava/28.1-jre/guava-28.1-jre.jar</p>
<p>
Dependency Hierarchy:
- :x: **guava-28.1-jre.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/ghc-dev/8060538_2339/commit/38b50fba3ac6f33c817f3c7a50a222ce6f91c4bc">38b50fba3ac6f33c817f3c7a50a222ce6f91c4bc</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
A temp directory creation vulnerability exists in all versions of Guava, allowing an attacker with access to the machine to potentially access data in a temporary directory created by the Guava API com.google.common.io.Files.createTempDir(). By default, on unix-like systems, the created directory is world-readable (readable by an attacker with access to the system). The method in question has been marked @Deprecated in versions 30.0 and later and should not be used. For Android developers, we recommend choosing a temporary directory API provided by Android, such as context.getCacheDir(). For other Java developers, we recommend migrating to the Java 7 API java.nio.file.Files.createTempDirectory() which explicitly configures permissions of 700, or configuring the Java runtime's java.io.tmpdir system property to point to a location whose permissions are appropriately configured.
<p>Publish Date: 2020-12-10
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2020-8908>CVE-2020-8908</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>3.3</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: Low
- 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>
<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-8908">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-8908</a></p>
<p>Release Date: 2020-12-10</p>
<p>Fix Resolution: 30.0-android</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 | guava jre jar vulnerabilities highest severity is autoclosed vulnerable library guava jre jar guava is a suite of core and expanded libraries that include utility classes google s collections io classes and much much more library home page a href path to dependency file pom xml path to vulnerable library home wss scanner repository com google guava guava jre guava jre jar found in head commit a href vulnerabilities cve severity cvss dependency type fixed in guava version remediation available low guava jre jar direct android details cve vulnerable library guava jre jar guava is a suite of core and expanded libraries that include utility classes google s collections io classes and much much more library home page a href path to dependency file pom xml path to vulnerable library home wss scanner repository com google guava guava jre guava jre jar dependency hierarchy x guava jre jar vulnerable library found in head commit a href found in base branch main vulnerability details a temp directory creation vulnerability exists in all versions of guava allowing an attacker with access to the machine to potentially access data in a temporary directory created by the guava api com google common io files createtempdir by default on unix like systems the created directory is world readable readable by an attacker with access to the system the method in question has been marked deprecated in versions and later and should not be used for android developers we recommend choosing a temporary directory api provided by android such as context getcachedir for other java developers we recommend migrating to the java api java nio file files createtempdirectory which explicitly configures permissions of or configuring the java runtime s java io tmpdir system property to point to a location whose permissions are appropriately configured 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 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 android rescue worker helmet automatic remediation is available for this issue rescue worker helmet automatic remediation is available for this issue | 0 |
45,312 | 11,628,565,910 | IssuesEvent | 2020-02-27 18:35:27 | csf-dev/CSF.ORM | https://api.github.com/repos/csf-dev/CSF.ORM | opened | NuGet packages for NHibernate should not permit incorrect versions | build/deployment enhancement | Currently, the package dependency between the ORM NHibernate packages and the NHibernate library specify only a minimum version. They should also specify a maximum. | 1.0 | NuGet packages for NHibernate should not permit incorrect versions - Currently, the package dependency between the ORM NHibernate packages and the NHibernate library specify only a minimum version. They should also specify a maximum. | non_priority | nuget packages for nhibernate should not permit incorrect versions currently the package dependency between the orm nhibernate packages and the nhibernate library specify only a minimum version they should also specify a maximum | 0 |
236,225 | 19,522,996,959 | IssuesEvent | 2021-12-29 22:56:30 | jubishop/smalldemocracy | https://api.github.com/repos/jubishop/smalldemocracy | closed | Rack testing changes | testing 0pri | Let's create an expect slim.render(template).with_params(params)
Let's always expect either the slim template or exact error reply, along with http status. Also test all links take us where we want.
Then capybara apparition tests for actual views. | 1.0 | Rack testing changes - Let's create an expect slim.render(template).with_params(params)
Let's always expect either the slim template or exact error reply, along with http status. Also test all links take us where we want.
Then capybara apparition tests for actual views. | non_priority | rack testing changes let s create an expect slim render template with params params let s always expect either the slim template or exact error reply along with http status also test all links take us where we want then capybara apparition tests for actual views | 0 |
113,038 | 11,785,977,668 | IssuesEvent | 2020-03-17 11:20:35 | SE701ProjectGroup4/Flatmate-Management-System | https://api.github.com/repos/SE701ProjectGroup4/Flatmate-Management-System | closed | Document justification for custom labels | approved documentation | **Describe the change**
As per the assignment brief, a justification for our choice of our custom issue labels should be documented in the team wiki.
**Why is this happening**
Though our choice of labels are relatively mainstream, a quick justification of why we chose this subset of labels ensures the entire team has a shared understanding of the decision.
| 1.0 | Document justification for custom labels - **Describe the change**
As per the assignment brief, a justification for our choice of our custom issue labels should be documented in the team wiki.
**Why is this happening**
Though our choice of labels are relatively mainstream, a quick justification of why we chose this subset of labels ensures the entire team has a shared understanding of the decision.
| non_priority | document justification for custom labels describe the change as per the assignment brief a justification for our choice of our custom issue labels should be documented in the team wiki why is this happening though our choice of labels are relatively mainstream a quick justification of why we chose this subset of labels ensures the entire team has a shared understanding of the decision | 0 |
100,039 | 16,481,179,740 | IssuesEvent | 2021-05-24 11:53:03 | AlexRogalskiy/github-action-issue-commenter | https://api.github.com/repos/AlexRogalskiy/github-action-issue-commenter | opened | CVE-2021-23343 (High) detected in path-parse-1.0.6.tgz | security vulnerability | ## CVE-2021-23343 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>path-parse-1.0.6.tgz</b></p></summary>
<p>Node.js path.parse() ponyfill</p>
<p>Library home page: <a href="https://registry.npmjs.org/path-parse/-/path-parse-1.0.6.tgz">https://registry.npmjs.org/path-parse/-/path-parse-1.0.6.tgz</a></p>
<p>Path to dependency file: github-action-issue-commenter/package.json</p>
<p>Path to vulnerable library: github-action-issue-commenter/node_modules/path-parse/package.json</p>
<p>
Dependency Hierarchy:
- eslint-import-resolver-typescript-2.4.0.tgz (Root Library)
- resolve-1.20.0.tgz
- :x: **path-parse-1.0.6.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/AlexRogalskiy/github-action-issue-commenter/commit/ffad54a6758fa01d530393d50aea5e6f298a4a37">ffad54a6758fa01d530393d50aea5e6f298a4a37</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>
All versions of package path-parse are vulnerable to Regular Expression Denial of Service (ReDoS) via splitDeviceRe, splitTailRe, and splitPathRe regular expressions. ReDoS exhibits polynomial worst-case time complexity.
<p>Publish Date: 2021-05-04
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-23343>CVE-2021-23343</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | CVE-2021-23343 (High) detected in path-parse-1.0.6.tgz - ## CVE-2021-23343 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>path-parse-1.0.6.tgz</b></p></summary>
<p>Node.js path.parse() ponyfill</p>
<p>Library home page: <a href="https://registry.npmjs.org/path-parse/-/path-parse-1.0.6.tgz">https://registry.npmjs.org/path-parse/-/path-parse-1.0.6.tgz</a></p>
<p>Path to dependency file: github-action-issue-commenter/package.json</p>
<p>Path to vulnerable library: github-action-issue-commenter/node_modules/path-parse/package.json</p>
<p>
Dependency Hierarchy:
- eslint-import-resolver-typescript-2.4.0.tgz (Root Library)
- resolve-1.20.0.tgz
- :x: **path-parse-1.0.6.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/AlexRogalskiy/github-action-issue-commenter/commit/ffad54a6758fa01d530393d50aea5e6f298a4a37">ffad54a6758fa01d530393d50aea5e6f298a4a37</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>
All versions of package path-parse are vulnerable to Regular Expression Denial of Service (ReDoS) via splitDeviceRe, splitTailRe, and splitPathRe regular expressions. ReDoS exhibits polynomial worst-case time complexity.
<p>Publish Date: 2021-05-04
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-23343>CVE-2021-23343</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_priority | cve high detected in path parse tgz cve high severity vulnerability vulnerable library path parse tgz node js path parse ponyfill library home page a href path to dependency file github action issue commenter package json path to vulnerable library github action issue commenter node modules path parse package json dependency hierarchy eslint import resolver typescript tgz root library resolve tgz x path parse tgz vulnerable library found in head commit a href found in base branch master vulnerability details all versions of package path parse are vulnerable to regular expression denial of service redos via splitdevicere splittailre and splitpathre regular expressions redos exhibits polynomial worst case time complexity publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact none integrity impact none availability impact high for more information on scores click a href step up your open source security game with whitesource | 0 |
97,334 | 12,227,967,350 | IssuesEvent | 2020-05-03 17:23:51 | readthedocs/sphinx_rtd_theme | https://api.github.com/repos/readthedocs/sphinx_rtd_theme | opened | Use unique identifier to avoid caching | Accepted Needed: design decision | I enabled the RTD PR builder for this project, however CSS and JS get cached at the CDN now, making PR review of built documentation not very helpful -- these assets will get cached and any updates to CSS/JS on the PR won't show.
We can avoid this by using a query string to avoid the caching and would have a few things to decide on:
* What string to use? We surface `{{ commit }}` for most builds, we could conditionally add that on the end of js/css requests: `{% if commit %}?{{ commit }}{% endif %}`. Is there a better string?
* Is there a more generalized solution to this? Sphinx extension that does this for us?
* Do we want this on just development/PR builds? On the base theme `layout.html` and all projects that use our theme? Perhaps start by making this a configuration variable and work towards making it the default?
My vote is to use `commit`, and use a configuration variable to enable the addition to URLs. | 1.0 | Use unique identifier to avoid caching - I enabled the RTD PR builder for this project, however CSS and JS get cached at the CDN now, making PR review of built documentation not very helpful -- these assets will get cached and any updates to CSS/JS on the PR won't show.
We can avoid this by using a query string to avoid the caching and would have a few things to decide on:
* What string to use? We surface `{{ commit }}` for most builds, we could conditionally add that on the end of js/css requests: `{% if commit %}?{{ commit }}{% endif %}`. Is there a better string?
* Is there a more generalized solution to this? Sphinx extension that does this for us?
* Do we want this on just development/PR builds? On the base theme `layout.html` and all projects that use our theme? Perhaps start by making this a configuration variable and work towards making it the default?
My vote is to use `commit`, and use a configuration variable to enable the addition to URLs. | non_priority | use unique identifier to avoid caching i enabled the rtd pr builder for this project however css and js get cached at the cdn now making pr review of built documentation not very helpful these assets will get cached and any updates to css js on the pr won t show we can avoid this by using a query string to avoid the caching and would have a few things to decide on what string to use we surface commit for most builds we could conditionally add that on the end of js css requests if commit commit endif is there a better string is there a more generalized solution to this sphinx extension that does this for us do we want this on just development pr builds on the base theme layout html and all projects that use our theme perhaps start by making this a configuration variable and work towards making it the default my vote is to use commit and use a configuration variable to enable the addition to urls | 0 |
2,849 | 2,718,320,415 | IssuesEvent | 2015-04-12 06:01:02 | fritzy/SleekXMPP | https://api.github.com/repos/fritzy/SleekXMPP | opened | Create CHANGELOG file and backfill history | Documentation | from the mailing list:
On Sunday, April 12, 2015 at 1:38:19 AM UTC-4, Alexander Artemenko wrote:
By the way, you could restore some historical data for a changelog from here: http://allmychanges.com/p/python/sleekxmpp/ | 1.0 | Create CHANGELOG file and backfill history - from the mailing list:
On Sunday, April 12, 2015 at 1:38:19 AM UTC-4, Alexander Artemenko wrote:
By the way, you could restore some historical data for a changelog from here: http://allmychanges.com/p/python/sleekxmpp/ | non_priority | create changelog file and backfill history from the mailing list on sunday april at am utc alexander artemenko wrote by the way you could restore some historical data for a changelog from here | 0 |
32,389 | 4,769,150,250 | IssuesEvent | 2016-10-26 11:34:24 | linkedpipes/etl | https://api.github.com/repos/linkedpipes/etl | closed | Import of pipeline with template fails | bug test | I tried to import this <a href="http://fit1.opendata.cz:8090/resources/pipelines/created-1475676896625">pipeline</a> into my localhost instance and I got a "missing template" error. | 1.0 | Import of pipeline with template fails - I tried to import this <a href="http://fit1.opendata.cz:8090/resources/pipelines/created-1475676896625">pipeline</a> into my localhost instance and I got a "missing template" error. | non_priority | import of pipeline with template fails i tried to import this a href into my localhost instance and i got a missing template error | 0 |
144,410 | 19,286,226,719 | IssuesEvent | 2021-12-11 02:05:07 | Alanwang2015/XBot | https://api.github.com/repos/Alanwang2015/XBot | opened | CVE-2020-36187 (High) detected in jackson-databind-2.9.10.jar | security vulnerability | ## CVE-2020-36187 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>jackson-databind-2.9.10.jar</b></p></summary>
<p>General data-binding functionality for Jackson: works on core streaming API</p>
<p>Library home page: <a href="http://github.com/FasterXML/jackson">http://github.com/FasterXML/jackson</a></p>
<p>Path to dependency file: XBot/pom.xml</p>
<p>Path to vulnerable library: canner/.m2/repository/com/fasterxml/jackson/core/jackson-databind/2.9.10/jackson-databind-2.9.10.jar</p>
<p>
Dependency Hierarchy:
- :x: **jackson-databind-2.9.10.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>
FasterXML jackson-databind 2.x before 2.9.10.8 mishandles the interaction between serialization gadgets and typing, related to org.apache.tomcat.dbcp.dbcp.datasources.SharedPoolDataSource.
<p>Publish Date: 2021-01-06
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-36187>CVE-2020-36187</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.1</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: 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/FasterXML/jackson-databind/issues/2997">https://github.com/FasterXML/jackson-databind/issues/2997</a></p>
<p>Release Date: 2021-01-06</p>
<p>Fix Resolution: com.fasterxml.jackson.core:jackson-databind:2.9.10.8</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-36187 (High) detected in jackson-databind-2.9.10.jar - ## CVE-2020-36187 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>jackson-databind-2.9.10.jar</b></p></summary>
<p>General data-binding functionality for Jackson: works on core streaming API</p>
<p>Library home page: <a href="http://github.com/FasterXML/jackson">http://github.com/FasterXML/jackson</a></p>
<p>Path to dependency file: XBot/pom.xml</p>
<p>Path to vulnerable library: canner/.m2/repository/com/fasterxml/jackson/core/jackson-databind/2.9.10/jackson-databind-2.9.10.jar</p>
<p>
Dependency Hierarchy:
- :x: **jackson-databind-2.9.10.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>
FasterXML jackson-databind 2.x before 2.9.10.8 mishandles the interaction between serialization gadgets and typing, related to org.apache.tomcat.dbcp.dbcp.datasources.SharedPoolDataSource.
<p>Publish Date: 2021-01-06
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-36187>CVE-2020-36187</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.1</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: 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/FasterXML/jackson-databind/issues/2997">https://github.com/FasterXML/jackson-databind/issues/2997</a></p>
<p>Release Date: 2021-01-06</p>
<p>Fix Resolution: com.fasterxml.jackson.core:jackson-databind:2.9.10.8</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 jackson databind jar cve high severity vulnerability vulnerable library jackson databind jar general data binding functionality for jackson works on core streaming api library home page a href path to dependency file xbot pom xml path to vulnerable library canner repository com fasterxml jackson core jackson databind jackson databind jar dependency hierarchy x jackson databind jar vulnerable library found in base branch master vulnerability details fasterxml jackson databind x before mishandles the interaction between serialization gadgets and typing related to org apache tomcat dbcp dbcp datasources sharedpooldatasource 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 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 com fasterxml jackson core jackson databind step up your open source security game with whitesource | 0 |
257,931 | 27,563,834,151 | IssuesEvent | 2023-03-08 01:09:50 | jtimberlake/pacbot | https://api.github.com/repos/jtimberlake/pacbot | opened | CVE-2019-11358 (Medium) detected in jquery-1.10.1.min.js, jquery-1.11.1.jar | security vulnerability | ## CVE-2019-11358 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>jquery-1.10.1.min.js</b>, <b>jquery-1.11.1.jar</b></p></summary>
<p>
<details><summary><b>jquery-1.10.1.min.js</b></p></summary>
<p>JavaScript library for DOM operations</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/jquery/1.10.1/jquery.min.js">https://cdnjs.cloudflare.com/ajax/libs/jquery/1.10.1/jquery.min.js</a></p>
<p>Path to dependency file: /webapp/node_modules/offline-js/docs/welcome/index.html</p>
<p>Path to vulnerable library: /webapp/node_modules/offline-js/docs/welcome/index.html</p>
<p>
Dependency Hierarchy:
- :x: **jquery-1.10.1.min.js** (Vulnerable Library)
</details>
<details><summary><b>jquery-1.11.1.jar</b></p></summary>
<p>WebJar for jQuery</p>
<p>Library home page: <a href="http://webjars.org">http://webjars.org</a></p>
<p>Path to dependency file: /api/pacman-api-auth/pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/org/webjars/jquery/1.11.1/jquery-1.11.1.jar</p>
<p>
Dependency Hierarchy:
- bootstrap-3.3.2.jar (Root Library)
- :x: **jquery-1.11.1.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>
jQuery before 3.4.0, as used in Drupal, Backdrop CMS, and other products, mishandles jQuery.extend(true, {}, ...) because of Object.prototype pollution. If an unsanitized source object contained an enumerable __proto__ property, it could extend the native Object.prototype.
<p>Publish Date: 2019-04-20
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2019-11358>CVE-2019-11358</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-2019-11358">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-11358</a></p>
<p>Release Date: 2019-04-20</p>
<p>Fix Resolution (org.webjars:jquery): 3.4.0</p>
<p>Direct dependency fix Resolution (org.webjars:bootstrap): 4.4.1-1</p>
</p>
</details>
<p></p>
***
<!-- REMEDIATE-OPEN-PR-START -->
- [ ] Check this box to open an automated fix PR
<!-- REMEDIATE-OPEN-PR-END -->
| True | CVE-2019-11358 (Medium) detected in jquery-1.10.1.min.js, jquery-1.11.1.jar - ## CVE-2019-11358 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>jquery-1.10.1.min.js</b>, <b>jquery-1.11.1.jar</b></p></summary>
<p>
<details><summary><b>jquery-1.10.1.min.js</b></p></summary>
<p>JavaScript library for DOM operations</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/jquery/1.10.1/jquery.min.js">https://cdnjs.cloudflare.com/ajax/libs/jquery/1.10.1/jquery.min.js</a></p>
<p>Path to dependency file: /webapp/node_modules/offline-js/docs/welcome/index.html</p>
<p>Path to vulnerable library: /webapp/node_modules/offline-js/docs/welcome/index.html</p>
<p>
Dependency Hierarchy:
- :x: **jquery-1.10.1.min.js** (Vulnerable Library)
</details>
<details><summary><b>jquery-1.11.1.jar</b></p></summary>
<p>WebJar for jQuery</p>
<p>Library home page: <a href="http://webjars.org">http://webjars.org</a></p>
<p>Path to dependency file: /api/pacman-api-auth/pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/org/webjars/jquery/1.11.1/jquery-1.11.1.jar</p>
<p>
Dependency Hierarchy:
- bootstrap-3.3.2.jar (Root Library)
- :x: **jquery-1.11.1.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>
jQuery before 3.4.0, as used in Drupal, Backdrop CMS, and other products, mishandles jQuery.extend(true, {}, ...) because of Object.prototype pollution. If an unsanitized source object contained an enumerable __proto__ property, it could extend the native Object.prototype.
<p>Publish Date: 2019-04-20
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2019-11358>CVE-2019-11358</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-2019-11358">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-11358</a></p>
<p>Release Date: 2019-04-20</p>
<p>Fix Resolution (org.webjars:jquery): 3.4.0</p>
<p>Direct dependency fix Resolution (org.webjars:bootstrap): 4.4.1-1</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 medium detected in jquery min js jquery jar cve medium severity vulnerability vulnerable libraries jquery min js jquery jar jquery min js javascript library for dom operations library home page a href path to dependency file webapp node modules offline js docs welcome index html path to vulnerable library webapp node modules offline js docs welcome index html dependency hierarchy x jquery min js vulnerable library jquery jar webjar for jquery library home page a href path to dependency file api pacman api auth pom xml path to vulnerable library home wss scanner repository org webjars jquery jquery jar dependency hierarchy bootstrap jar root library x jquery jar vulnerable library found in base branch master vulnerability details jquery before as used in drupal backdrop cms and other products mishandles jquery extend true because of object prototype pollution if an unsanitized source object contained an enumerable proto property it could extend the native object prototype 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 org webjars jquery direct dependency fix resolution org webjars bootstrap check this box to open an automated fix pr | 0 |
372,695 | 26,014,702,184 | IssuesEvent | 2022-12-21 07:13:08 | Dapp-Learning-DAO/Dapp-Learning | https://api.github.com/repos/Dapp-Learning-DAO/Dapp-Learning | closed | Re-order the tasks' sequence of the basic part | documentation | Title:
Re-order the tasks' sequence of the basic part.
Description:
The tasks are randomly added by contributors, while the current list is not suitable for fresh guys. We need to pay some effort to re-order those tasks to make sure these courses can be helpful to learners. | 1.0 | Re-order the tasks' sequence of the basic part - Title:
Re-order the tasks' sequence of the basic part.
Description:
The tasks are randomly added by contributors, while the current list is not suitable for fresh guys. We need to pay some effort to re-order those tasks to make sure these courses can be helpful to learners. | non_priority | re order the tasks sequence of the basic part title re order the tasks sequence of the basic part description the tasks are randomly added by contributors while the current list is not suitable for fresh guys we need to pay some effort to re order those tasks to make sure these courses can be helpful to learners | 0 |
109,281 | 11,631,649,970 | IssuesEvent | 2020-02-28 02:07:08 | StewartThomson/Gotify-Ext | https://api.github.com/repos/StewartThomson/Gotify-Ext | opened | Add development guide | documentation | In the readme, I need to put what's necessary to dev this... might set up a docker-compose to make it easier. | 1.0 | Add development guide - In the readme, I need to put what's necessary to dev this... might set up a docker-compose to make it easier. | non_priority | add development guide in the readme i need to put what s necessary to dev this might set up a docker compose to make it easier | 0 |
140,922 | 21,302,148,683 | IssuesEvent | 2022-04-15 05:41:56 | cardano-indonesia/community-web-portal-in-bahasa | https://api.github.com/repos/cardano-indonesia/community-web-portal-in-bahasa | closed | Web Design | design web development | Web Design - @Rollies77
- [x] Prepare web design for review on 15/3 @Rollies77
- [x] Logo - 3 alternative @Rollies77
- [x] 2nd revision web design on 30 March @Rollies77
- [x] final revision web design by 6 April @Rollies77 | 1.0 | Web Design - Web Design - @Rollies77
- [x] Prepare web design for review on 15/3 @Rollies77
- [x] Logo - 3 alternative @Rollies77
- [x] 2nd revision web design on 30 March @Rollies77
- [x] final revision web design by 6 April @Rollies77 | non_priority | web design web design prepare web design for review on logo alternative revision web design on march final revision web design by april | 0 |
67,774 | 17,067,807,849 | IssuesEvent | 2021-07-07 09:30:31 | dotnet/runtime | https://api.github.com/repos/dotnet/runtime | closed | Remove MONO_CORLIB_VERSION | area-Build-mono in pr | This is no longer as useful with .NET 6, since we are much less likely to end up in a scenario where the runtime and corelib are out of sync. We haven't been good about bumping it with icall changes and it hasn't been a problem, so it should be safe to just remove.
cc: @akoeplinger @lambdageek | 1.0 | Remove MONO_CORLIB_VERSION - This is no longer as useful with .NET 6, since we are much less likely to end up in a scenario where the runtime and corelib are out of sync. We haven't been good about bumping it with icall changes and it hasn't been a problem, so it should be safe to just remove.
cc: @akoeplinger @lambdageek | non_priority | remove mono corlib version this is no longer as useful with net since we are much less likely to end up in a scenario where the runtime and corelib are out of sync we haven t been good about bumping it with icall changes and it hasn t been a problem so it should be safe to just remove cc akoeplinger lambdageek | 0 |
19,048 | 3,414,190,189 | IssuesEvent | 2015-12-07 03:54:29 | marekr/kicad-issue-test | https://api.github.com/repos/marekr/kicad-issue-test | opened | Delete wire/delete node not intuitive | eeschema eeschema-redesign Triaged Wishlist | The whole delete wire/delete node operation isn't really clear. The most
useful thing to do for a DEL keypress is to delete till the end or a junction
not the WHOLE wire (and not even always the whole, it depends on how it was
drawn to begin with). Example:
A 1 B 2 C 3 D
---*---*---*--- (wire with junction)
Pressing DEL on the A segment should delete only A, not the whole ABCD, or ABC,
or AB. Also the junction cleanup could be improved, often some 'corner' junction
remain or even some 'floating' ones. | 1.0 | Delete wire/delete node not intuitive - The whole delete wire/delete node operation isn't really clear. The most
useful thing to do for a DEL keypress is to delete till the end or a junction
not the WHOLE wire (and not even always the whole, it depends on how it was
drawn to begin with). Example:
A 1 B 2 C 3 D
---*---*---*--- (wire with junction)
Pressing DEL on the A segment should delete only A, not the whole ABCD, or ABC,
or AB. Also the junction cleanup could be improved, often some 'corner' junction
remain or even some 'floating' ones. | non_priority | delete wire delete node not intuitive the whole delete wire delete node operation isn t really clear the most useful thing to do for a del keypress is to delete till the end or a junction not the whole wire and not even always the whole it depends on how it was drawn to begin with example a b c d wire with junction pressing del on the a segment should delete only a not the whole abcd or abc or ab also the junction cleanup could be improved often some corner junction remain or even some floating ones | 0 |
33,054 | 7,647,098,420 | IssuesEvent | 2018-05-09 01:52:30 | EOSIO/eos | https://api.github.com/repos/EOSIO/eos | closed | Fix access control for context-aware vs context-free APIs | HARDFORK bug code review | Changes needed:
- `softfloat_api` and `compiler_builtins` are currently not available to context-free actions when they should be.
- The exposed methods of `apply_context` are currently available to context-free actions when they should not be.
- `check_auth` should be moved from `context_free_transaction_api` (which is available to context-free actions) to `permission_api` (which is only available to context-aware actions).
- Determine whether `now()` should be available to context-free actions. If not, then:
* `now()` should be moved out of the `system_api` (which is available to both context-free and context-aware actions) to an API that is only available to context-aware actions.
* We should figure out if `action_api::publication_time()` needs to be dealt with in a similar way. It wouldn't be a problem for a deferred transaction, but it may be for an immediately-executing input transaction.
- Determine whether `context_free_transaction_api::get_action` needs to be split into multiple functions: one that only gets actions in the original transaction and is available to both context-free and context-aware actions; and another one that can get all the actions in the current implicit transaction (including ones dispatched during execution of previously executed actions). Related to issues #2356 and #2386.
ATC:
- Unittests test all the api categories for access via context free actions. | 1.0 | Fix access control for context-aware vs context-free APIs - Changes needed:
- `softfloat_api` and `compiler_builtins` are currently not available to context-free actions when they should be.
- The exposed methods of `apply_context` are currently available to context-free actions when they should not be.
- `check_auth` should be moved from `context_free_transaction_api` (which is available to context-free actions) to `permission_api` (which is only available to context-aware actions).
- Determine whether `now()` should be available to context-free actions. If not, then:
* `now()` should be moved out of the `system_api` (which is available to both context-free and context-aware actions) to an API that is only available to context-aware actions.
* We should figure out if `action_api::publication_time()` needs to be dealt with in a similar way. It wouldn't be a problem for a deferred transaction, but it may be for an immediately-executing input transaction.
- Determine whether `context_free_transaction_api::get_action` needs to be split into multiple functions: one that only gets actions in the original transaction and is available to both context-free and context-aware actions; and another one that can get all the actions in the current implicit transaction (including ones dispatched during execution of previously executed actions). Related to issues #2356 and #2386.
ATC:
- Unittests test all the api categories for access via context free actions. | non_priority | fix access control for context aware vs context free apis changes needed softfloat api and compiler builtins are currently not available to context free actions when they should be the exposed methods of apply context are currently available to context free actions when they should not be check auth should be moved from context free transaction api which is available to context free actions to permission api which is only available to context aware actions determine whether now should be available to context free actions if not then now should be moved out of the system api which is available to both context free and context aware actions to an api that is only available to context aware actions we should figure out if action api publication time needs to be dealt with in a similar way it wouldn t be a problem for a deferred transaction but it may be for an immediately executing input transaction determine whether context free transaction api get action needs to be split into multiple functions one that only gets actions in the original transaction and is available to both context free and context aware actions and another one that can get all the actions in the current implicit transaction including ones dispatched during execution of previously executed actions related to issues and atc unittests test all the api categories for access via context free actions | 0 |
60,270 | 25,069,922,849 | IssuesEvent | 2022-11-07 11:16:48 | ministryofjustice/modernisation-platform | https://api.github.com/repos/ministryofjustice/modernisation-platform | closed | Instance Scheduler can't start some EC2s | bug sustainability self-service | When invoking the Instance Scheduler lambda manually through the AWS web console in core-shared-services account.
The `sprinkler-db-mgmt-server` is stopped through the lambda, but cannot be started. The lambda logs are not reporting any error because the message to start the instance is successful. However, the EC2 reports the following errors after some time:
```
State transition reason: Server.InternalError
State transition message: Client.InternalError: Client error on launch
```
This behaviour only seems to apply to `sprinkler-db-mgmt-server` whereas a temporal instance I created did not have the same issue.
The following PR unfortunately did not resolve the issue and might have to be reverted:
[Add "kms:CreateGrant" to instance scheduler role to try fixing the issue](https://github.com/ministryofjustice/modernisation-platform/pull/2536) | 1.0 | Instance Scheduler can't start some EC2s - When invoking the Instance Scheduler lambda manually through the AWS web console in core-shared-services account.
The `sprinkler-db-mgmt-server` is stopped through the lambda, but cannot be started. The lambda logs are not reporting any error because the message to start the instance is successful. However, the EC2 reports the following errors after some time:
```
State transition reason: Server.InternalError
State transition message: Client.InternalError: Client error on launch
```
This behaviour only seems to apply to `sprinkler-db-mgmt-server` whereas a temporal instance I created did not have the same issue.
The following PR unfortunately did not resolve the issue and might have to be reverted:
[Add "kms:CreateGrant" to instance scheduler role to try fixing the issue](https://github.com/ministryofjustice/modernisation-platform/pull/2536) | non_priority | instance scheduler can t start some when invoking the instance scheduler lambda manually through the aws web console in core shared services account the sprinkler db mgmt server is stopped through the lambda but cannot be started the lambda logs are not reporting any error because the message to start the instance is successful however the reports the following errors after some time state transition reason server internalerror state transition message client internalerror client error on launch this behaviour only seems to apply to sprinkler db mgmt server whereas a temporal instance i created did not have the same issue the following pr unfortunately did not resolve the issue and might have to be reverted | 0 |
161,368 | 12,541,934,597 | IssuesEvent | 2020-06-05 13:14:35 | SAP/spartacus | https://api.github.com/repos/SAP/spartacus | closed | Regression testing for 2.0 release | MUST release-testing team/gladiators | **Test against 1905**
Can use:
- https://dev-com-3.accdemo.b2c.ydev.hybris.com:4200/electronics-spa/en/USD/
-https://dev-com-10.accdemo.b2c.ydev.hybris.com:4200/electronics-spa/en/USD/
- [x] **Run all the E2E tests** on the nightly branch on jenkins (Marcin) - covered in https://github.com/SAP/spartacus/issues/7799
Note: Make sure that ALL the tests are being run (about 90 tests, including the flaky tests).
OR run them from your computer, pointing to dev17 server.
**Manually test the features that are failing:**
- [x] to come from release masters - Marcin - covered in https://github.com/SAP/spartacus/issues/7799
**Do a smoke test of these features manually**, since there's no E2E tests for them yet or they are flaky:
~~Cancel/Return~~ - Jimmy (Imported impex, but cancel/returns not enabled on 1905)
- [x] Smartedit (Wei lead, but get someone else to do it) - Kate
- [x] Qualtrics - Brian
- [x] Coupons - GC
- [x] Broken tabbing order (related to e2e accessibility? kacper fixing?) - Kate
- [x] Accessibility (checkout with keyboard nav on all 3 browsers) - Kate
- [x] Checkout as a persistent user
**Do a smoke test (happy path) on these browsers:**
- [x] safari - Kate: https://github.com/SAP/spartacus/issues/7817
- [x] firefox - Kate
- [ ] Edge Windows - Farzin
- ... more! mobile phones, tablet, etc. (GC -> Ipad Pro)
**Test against 2005**
- http://dev-com-2.accdemo.b2c.ydev.hybris.com:4200/electronics-spa/en/USD/
- https://dev-com-8.accdemo.b2c.ydev.hybris.com:4200/electronics-spa/en/USD/
- [x] Run the e2e tests pointing to dev7 server as backend (there's already a jenkins job for it) - Brian
- [x] Retest manually failing tests (make list of differences of failures between 1905 and 2005) - Brian
Redo manual set (cancel/return etc.) against 2005 as well
- [x] Cancel/Return - Jimmy
- [x] Smartedit (Wei lead, but get someone else to do it) - Kate
- [x] Qualtrics - Brian
- [x] Coupons (GC)
- [x] Broken tabbing order (related to e2e accessibility? kacper fixing?) - Kate
- [x] Accessibility (checkout with keyboard nav on all 3 browsers) - Kate
- [x] Checkout as a persistent user - Kate
Don't do for 2005: smoketest browsers
The 2005 goal is to see if we see any differences at all... in the future
**Manually test the features that are failing against 2005 backend:**
- [x] regression/cart.e2e-spec.ts #7841 - Kate: couldn't test apparel. and couldn't test out of stock product because backoffice isn't working for 2005. Can't go to products in backoffice, we get an error "cannot execute search".
- [x] smoke/checkout-flow.e2e-spec.ts #7842 - Kate
- [x] smoke/currency.e2e-spec.ts #7846 - Kate
- [x] smoke/language.e2e-spec.ts #7848 - Kate
- [x] smoke/product-search.e2e-spec.ts #7849 - Kate | 1.0 | Regression testing for 2.0 release - **Test against 1905**
Can use:
- https://dev-com-3.accdemo.b2c.ydev.hybris.com:4200/electronics-spa/en/USD/
-https://dev-com-10.accdemo.b2c.ydev.hybris.com:4200/electronics-spa/en/USD/
- [x] **Run all the E2E tests** on the nightly branch on jenkins (Marcin) - covered in https://github.com/SAP/spartacus/issues/7799
Note: Make sure that ALL the tests are being run (about 90 tests, including the flaky tests).
OR run them from your computer, pointing to dev17 server.
**Manually test the features that are failing:**
- [x] to come from release masters - Marcin - covered in https://github.com/SAP/spartacus/issues/7799
**Do a smoke test of these features manually**, since there's no E2E tests for them yet or they are flaky:
~~Cancel/Return~~ - Jimmy (Imported impex, but cancel/returns not enabled on 1905)
- [x] Smartedit (Wei lead, but get someone else to do it) - Kate
- [x] Qualtrics - Brian
- [x] Coupons - GC
- [x] Broken tabbing order (related to e2e accessibility? kacper fixing?) - Kate
- [x] Accessibility (checkout with keyboard nav on all 3 browsers) - Kate
- [x] Checkout as a persistent user
**Do a smoke test (happy path) on these browsers:**
- [x] safari - Kate: https://github.com/SAP/spartacus/issues/7817
- [x] firefox - Kate
- [ ] Edge Windows - Farzin
- ... more! mobile phones, tablet, etc. (GC -> Ipad Pro)
**Test against 2005**
- http://dev-com-2.accdemo.b2c.ydev.hybris.com:4200/electronics-spa/en/USD/
- https://dev-com-8.accdemo.b2c.ydev.hybris.com:4200/electronics-spa/en/USD/
- [x] Run the e2e tests pointing to dev7 server as backend (there's already a jenkins job for it) - Brian
- [x] Retest manually failing tests (make list of differences of failures between 1905 and 2005) - Brian
Redo manual set (cancel/return etc.) against 2005 as well
- [x] Cancel/Return - Jimmy
- [x] Smartedit (Wei lead, but get someone else to do it) - Kate
- [x] Qualtrics - Brian
- [x] Coupons (GC)
- [x] Broken tabbing order (related to e2e accessibility? kacper fixing?) - Kate
- [x] Accessibility (checkout with keyboard nav on all 3 browsers) - Kate
- [x] Checkout as a persistent user - Kate
Don't do for 2005: smoketest browsers
The 2005 goal is to see if we see any differences at all... in the future
**Manually test the features that are failing against 2005 backend:**
- [x] regression/cart.e2e-spec.ts #7841 - Kate: couldn't test apparel. and couldn't test out of stock product because backoffice isn't working for 2005. Can't go to products in backoffice, we get an error "cannot execute search".
- [x] smoke/checkout-flow.e2e-spec.ts #7842 - Kate
- [x] smoke/currency.e2e-spec.ts #7846 - Kate
- [x] smoke/language.e2e-spec.ts #7848 - Kate
- [x] smoke/product-search.e2e-spec.ts #7849 - Kate | non_priority | regression testing for release test against can use run all the tests on the nightly branch on jenkins marcin covered in note make sure that all the tests are being run about tests including the flaky tests or run them from your computer pointing to server manually test the features that are failing to come from release masters marcin covered in do a smoke test of these features manually since there s no tests for them yet or they are flaky cancel return jimmy imported impex but cancel returns not enabled on smartedit wei lead but get someone else to do it kate qualtrics brian coupons gc broken tabbing order related to accessibility kacper fixing kate accessibility checkout with keyboard nav on all browsers kate checkout as a persistent user do a smoke test happy path on these browsers safari kate firefox kate edge windows farzin more mobile phones tablet etc gc ipad pro test against run the tests pointing to server as backend there s already a jenkins job for it brian retest manually failing tests make list of differences of failures between and brian redo manual set cancel return etc against as well cancel return jimmy smartedit wei lead but get someone else to do it kate qualtrics brian coupons gc broken tabbing order related to accessibility kacper fixing kate accessibility checkout with keyboard nav on all browsers kate checkout as a persistent user kate don t do for smoketest browsers the goal is to see if we see any differences at all in the future manually test the features that are failing against backend regression cart spec ts kate couldn t test apparel and couldn t test out of stock product because backoffice isn t working for can t go to products in backoffice we get an error cannot execute search smoke checkout flow spec ts kate smoke currency spec ts kate smoke language spec ts kate smoke product search spec ts kate | 0 |
280,940 | 21,315,285,712 | IssuesEvent | 2022-04-16 06:53:58 | punnyhuimin/pe | https://api.github.com/repos/punnyhuimin/pe | opened | Unclear annotated image of resulting contact in list | type.DocumentationBug severity.Low | 
The annotation of the image takes some time for the user to decipher and does not necessarily provide the best information on what the user should be expected to see.
Usage of arrows or boxes to point out the exact place where the annotation is referring to would be best so that the users can easily decipher the annotation. Additionally, a more striking color (e.g. purple or red) can stand out better instead of using black, which may mislead users to think this is part of what they should see in the application.
<!--session: 1650089275146-ebf8047c-ce41-4646-b3cf-7b9c56b8d494-->
<!--Version: Web v3.4.2--> | 1.0 | Unclear annotated image of resulting contact in list - 
The annotation of the image takes some time for the user to decipher and does not necessarily provide the best information on what the user should be expected to see.
Usage of arrows or boxes to point out the exact place where the annotation is referring to would be best so that the users can easily decipher the annotation. Additionally, a more striking color (e.g. purple or red) can stand out better instead of using black, which may mislead users to think this is part of what they should see in the application.
<!--session: 1650089275146-ebf8047c-ce41-4646-b3cf-7b9c56b8d494-->
<!--Version: Web v3.4.2--> | non_priority | unclear annotated image of resulting contact in list the annotation of the image takes some time for the user to decipher and does not necessarily provide the best information on what the user should be expected to see usage of arrows or boxes to point out the exact place where the annotation is referring to would be best so that the users can easily decipher the annotation additionally a more striking color e g purple or red can stand out better instead of using black which may mislead users to think this is part of what they should see in the application | 0 |
89,246 | 8,198,552,451 | IssuesEvent | 2018-08-31 16:48:25 | ValveSoftware/steam-for-linux | https://api.github.com/repos/ValveSoftware/steam-for-linux | closed | Dota 2 blog and Store pages don't load. | Need Retest Steam client reviewed | The bug was originally reported on the Dota 2 issue tracker at [bug #1735](https://github.com/ValveSoftware/Dota-2/issues/1735)
Downgrading Steam to stable from the Beta branch fixes the issue.
| 1.0 | Dota 2 blog and Store pages don't load. - The bug was originally reported on the Dota 2 issue tracker at [bug #1735](https://github.com/ValveSoftware/Dota-2/issues/1735)
Downgrading Steam to stable from the Beta branch fixes the issue.
| non_priority | dota blog and store pages don t load the bug was originally reported on the dota issue tracker at downgrading steam to stable from the beta branch fixes the issue | 0 |
4,079 | 10,555,664,904 | IssuesEvent | 2019-10-03 22:35:21 | fga-eps-mds/2019.2-Gymnasteg-Wiki | https://api.github.com/repos/fga-eps-mds/2019.2-Gymnasteg-Wiki | closed | Elaborar Documento de Arquitetura | Architecture MDS documentation | ## Descrição
Documentar funcionamento da arquitetura do sistema parra melhor compreensão do time.
## Terafas
- [ ] Introdução
- [ ] Representação da Arquitetura
- [ ] Metas e Restrições da Arquitetura
- [ ] Visão de Casos de Uso
- [ ] Visão Lógica
- [ ] Visão de Dados
**Um template para o a realização desse documento pode ser encontrado [aqui](https://github.com/DroidFoundry/DroidMetronome/wiki/TEMPLATE-Documento-de-Arquitetura-de-Software)** | 1.0 | Elaborar Documento de Arquitetura - ## Descrição
Documentar funcionamento da arquitetura do sistema parra melhor compreensão do time.
## Terafas
- [ ] Introdução
- [ ] Representação da Arquitetura
- [ ] Metas e Restrições da Arquitetura
- [ ] Visão de Casos de Uso
- [ ] Visão Lógica
- [ ] Visão de Dados
**Um template para o a realização desse documento pode ser encontrado [aqui](https://github.com/DroidFoundry/DroidMetronome/wiki/TEMPLATE-Documento-de-Arquitetura-de-Software)** | non_priority | elaborar documento de arquitetura descrição documentar funcionamento da arquitetura do sistema parra melhor compreensão do time terafas introdução representação da arquitetura metas e restrições da arquitetura visão de casos de uso visão lógica visão de dados um template para o a realização desse documento pode ser encontrado | 0 |
113,296 | 17,117,949,469 | IssuesEvent | 2021-07-11 18:52:42 | turkdevops/design-language-website | https://api.github.com/repos/turkdevops/design-language-website | opened | CVE-2021-23337 (High) detected in lodash-4.17.20.tgz, lodash-4.17.19.tgz | security vulnerability | ## CVE-2021-23337 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>lodash-4.17.20.tgz</b>, <b>lodash-4.17.19.tgz</b></p></summary>
<p>
<details><summary><b>lodash-4.17.20.tgz</b></p></summary>
<p>Lodash modular utilities.</p>
<p>Library home page: <a href="https://registry.npmjs.org/lodash/-/lodash-4.17.20.tgz">https://registry.npmjs.org/lodash/-/lodash-4.17.20.tgz</a></p>
<p>Path to dependency file: design-language-website/package.json</p>
<p>Path to vulnerable library: design-language-website/node_modules/lodash</p>
<p>
Dependency Hierarchy:
- core-7.13.15.tgz (Root Library)
- types-7.13.14.tgz
- :x: **lodash-4.17.20.tgz** (Vulnerable Library)
</details>
<details><summary><b>lodash-4.17.19.tgz</b></p></summary>
<p>Lodash modular utilities.</p>
<p>Library home page: <a href="https://registry.npmjs.org/lodash/-/lodash-4.17.19.tgz">https://registry.npmjs.org/lodash/-/lodash-4.17.19.tgz</a></p>
<p>Path to dependency file: design-language-website/package.json</p>
<p>Path to vulnerable library: design-language-website/node_modules/lodash</p>
<p>
Dependency Hierarchy:
- babel-eslint-10.1.0.tgz (Root Library)
- types-7.10.4.tgz
- :x: **lodash-4.17.19.tgz** (Vulnerable Library)
</details>
<p>Found in HEAD commit: <a href="https://github.com/turkdevops/design-language-website/commit/187b6c70cc572cc46890f19fe80fcaddc53857c4">187b6c70cc572cc46890f19fe80fcaddc53857c4</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>
Lodash versions prior to 4.17.21 are vulnerable to Command Injection via the template function.
<p>Publish Date: 2021-02-15
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-23337>CVE-2021-23337</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.2</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: High
- 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://github.com/lodash/lodash/commit/3469357cff396a26c363f8c1b5a91dde28ba4b1c">https://github.com/lodash/lodash/commit/3469357cff396a26c363f8c1b5a91dde28ba4b1c</a></p>
<p>Release Date: 2021-02-15</p>
<p>Fix Resolution: lodash - 4.17.21</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-23337 (High) detected in lodash-4.17.20.tgz, lodash-4.17.19.tgz - ## CVE-2021-23337 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>lodash-4.17.20.tgz</b>, <b>lodash-4.17.19.tgz</b></p></summary>
<p>
<details><summary><b>lodash-4.17.20.tgz</b></p></summary>
<p>Lodash modular utilities.</p>
<p>Library home page: <a href="https://registry.npmjs.org/lodash/-/lodash-4.17.20.tgz">https://registry.npmjs.org/lodash/-/lodash-4.17.20.tgz</a></p>
<p>Path to dependency file: design-language-website/package.json</p>
<p>Path to vulnerable library: design-language-website/node_modules/lodash</p>
<p>
Dependency Hierarchy:
- core-7.13.15.tgz (Root Library)
- types-7.13.14.tgz
- :x: **lodash-4.17.20.tgz** (Vulnerable Library)
</details>
<details><summary><b>lodash-4.17.19.tgz</b></p></summary>
<p>Lodash modular utilities.</p>
<p>Library home page: <a href="https://registry.npmjs.org/lodash/-/lodash-4.17.19.tgz">https://registry.npmjs.org/lodash/-/lodash-4.17.19.tgz</a></p>
<p>Path to dependency file: design-language-website/package.json</p>
<p>Path to vulnerable library: design-language-website/node_modules/lodash</p>
<p>
Dependency Hierarchy:
- babel-eslint-10.1.0.tgz (Root Library)
- types-7.10.4.tgz
- :x: **lodash-4.17.19.tgz** (Vulnerable Library)
</details>
<p>Found in HEAD commit: <a href="https://github.com/turkdevops/design-language-website/commit/187b6c70cc572cc46890f19fe80fcaddc53857c4">187b6c70cc572cc46890f19fe80fcaddc53857c4</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>
Lodash versions prior to 4.17.21 are vulnerable to Command Injection via the template function.
<p>Publish Date: 2021-02-15
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-23337>CVE-2021-23337</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.2</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: High
- 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://github.com/lodash/lodash/commit/3469357cff396a26c363f8c1b5a91dde28ba4b1c">https://github.com/lodash/lodash/commit/3469357cff396a26c363f8c1b5a91dde28ba4b1c</a></p>
<p>Release Date: 2021-02-15</p>
<p>Fix Resolution: lodash - 4.17.21</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 lodash tgz lodash tgz cve high severity vulnerability vulnerable libraries lodash tgz lodash tgz lodash tgz lodash modular utilities library home page a href path to dependency file design language website package json path to vulnerable library design language website node modules lodash dependency hierarchy core tgz root library types tgz x lodash tgz vulnerable library lodash tgz lodash modular utilities library home page a href path to dependency file design language website package json path to vulnerable library design language website node modules lodash dependency hierarchy babel eslint tgz root library types tgz x lodash tgz vulnerable library found in head commit a href found in base branch master vulnerability details lodash versions prior to are vulnerable to command injection via the template function publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required high 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 lodash step up your open source security game with whitesource | 0 |
205,627 | 15,650,902,325 | IssuesEvent | 2021-03-23 09:33:42 | pravega/pravega | https://api.github.com/repos/pravega/pravega | opened | Sporadic failure in WatermarkingTest.watermarkTest | area/integration tag/flakeyTest | **Describe the bug**
Found a sporadic failure in test `WatermarkingTest.watermarkTest`: https://github.com/pravega/pravega/runs/2173677972
```
io.pravega.test.integration.WatermarkingTest > watermarkTest FAILED
java.lang.AssertionError
at org.junit.Assert.fail(Assert.java:86)
at org.junit.Assert.assertTrue(Assert.java:41)
at org.junit.Assert.assertNotNull(Assert.java:712)
at org.junit.Assert.assertNotNull(Assert.java:722)
at io.pravega.test.integration.WatermarkingTest.watermarkTest(WatermarkingTest.java:189)
```
I don't know if this is related to a recent change to speed up this test: #5836.
**To Reproduce**
The issue occurs sporadically in Git Actions when executing `./gradlew build`
**Expected behavior**
Test should pass consistently.
**Screenshots**
n/a
**Additional context**
n/a | 1.0 | Sporadic failure in WatermarkingTest.watermarkTest - **Describe the bug**
Found a sporadic failure in test `WatermarkingTest.watermarkTest`: https://github.com/pravega/pravega/runs/2173677972
```
io.pravega.test.integration.WatermarkingTest > watermarkTest FAILED
java.lang.AssertionError
at org.junit.Assert.fail(Assert.java:86)
at org.junit.Assert.assertTrue(Assert.java:41)
at org.junit.Assert.assertNotNull(Assert.java:712)
at org.junit.Assert.assertNotNull(Assert.java:722)
at io.pravega.test.integration.WatermarkingTest.watermarkTest(WatermarkingTest.java:189)
```
I don't know if this is related to a recent change to speed up this test: #5836.
**To Reproduce**
The issue occurs sporadically in Git Actions when executing `./gradlew build`
**Expected behavior**
Test should pass consistently.
**Screenshots**
n/a
**Additional context**
n/a | non_priority | sporadic failure in watermarkingtest watermarktest describe the bug found a sporadic failure in test watermarkingtest watermarktest io pravega test integration watermarkingtest watermarktest failed java lang assertionerror at org junit assert fail assert java at org junit assert asserttrue assert java at org junit assert assertnotnull assert java at org junit assert assertnotnull assert java at io pravega test integration watermarkingtest watermarktest watermarkingtest java i don t know if this is related to a recent change to speed up this test to reproduce the issue occurs sporadically in git actions when executing gradlew build expected behavior test should pass consistently screenshots n a additional context n a | 0 |
32,031 | 6,026,055,332 | IssuesEvent | 2017-06-08 10:14:14 | restic/restic | https://api.github.com/repos/restic/restic | closed | Cannot find docs for b2 backend | documentation question | I came to restic because of the amazing feature set and the support for b2, but I'm having trouble finding the docs for b2 - I found s3 under the latest documentation at https://restic.readthedocs.io/en/latest/tutorials.html | 1.0 | Cannot find docs for b2 backend - I came to restic because of the amazing feature set and the support for b2, but I'm having trouble finding the docs for b2 - I found s3 under the latest documentation at https://restic.readthedocs.io/en/latest/tutorials.html | non_priority | cannot find docs for backend i came to restic because of the amazing feature set and the support for but i m having trouble finding the docs for i found under the latest documentation at | 0 |
18,046 | 3,372,065,640 | IssuesEvent | 2015-11-23 21:49:59 | aspnet/Hosting | https://api.github.com/repos/aspnet/Hosting | closed | dnx command line weblistener/kestrel | needs design | _From @grahamehorner on September 16, 2015 10:47_
I'm not sure if I'm missing something or if it's possible to even do this; but how would you pass command line parameters to the startup method of a web application? does dnx pass the command line parameters to weblistner/kestrel which then get forwarded to the startup? or are they encapsulated in an object that is accessible like IHostingEnvironment, IApplicationEnvironment or IRuntimeEnvironment?
_Copied from original issue: aspnet/Home#928_ | 1.0 | dnx command line weblistener/kestrel - _From @grahamehorner on September 16, 2015 10:47_
I'm not sure if I'm missing something or if it's possible to even do this; but how would you pass command line parameters to the startup method of a web application? does dnx pass the command line parameters to weblistner/kestrel which then get forwarded to the startup? or are they encapsulated in an object that is accessible like IHostingEnvironment, IApplicationEnvironment or IRuntimeEnvironment?
_Copied from original issue: aspnet/Home#928_ | non_priority | dnx command line weblistener kestrel from grahamehorner on september i m not sure if i m missing something or if it s possible to even do this but how would you pass command line parameters to the startup method of a web application does dnx pass the command line parameters to weblistner kestrel which then get forwarded to the startup or are they encapsulated in an object that is accessible like ihostingenvironment iapplicationenvironment or iruntimeenvironment copied from original issue aspnet home | 0 |
89,439 | 11,222,933,719 | IssuesEvent | 2020-01-07 21:22:48 | ember-learn/ember-website | https://api.github.com/repos/ember-learn/ember-website | closed | [redesign] Fix relative link code for header and footer | Website Redesign RFC bug help wanted | We have an implementation of custom `@links` code that is supposed to work with ember-href to make sure that any internal links on the website are treated as `<LinkTo />`
This is particularly annoying when developing the new website because any time you click on an internal link you are brought to the production website https://emberjs.com | 1.0 | [redesign] Fix relative link code for header and footer - We have an implementation of custom `@links` code that is supposed to work with ember-href to make sure that any internal links on the website are treated as `<LinkTo />`
This is particularly annoying when developing the new website because any time you click on an internal link you are brought to the production website https://emberjs.com | non_priority | fix relative link code for header and footer we have an implementation of custom links code that is supposed to work with ember href to make sure that any internal links on the website are treated as this is particularly annoying when developing the new website because any time you click on an internal link you are brought to the production website | 0 |
983 | 3,268,677,975 | IssuesEvent | 2015-10-23 12:55:33 | mesosphere/marathon | https://api.github.com/repos/mesosphere/marathon | closed | Using docker w/ application groups | docs service | About this page:
https://mesosphere.github.io/marathon/docs/application-groups.html
Does this work with docker containers? @swartzrock would like to have a group of 2 docker containers which are scheduled at the same time. Can you do this now? Please add docs that show in detail how to do this!
https://mesosphere.atlassian.net/browse/MARATHON-318 | 1.0 | Using docker w/ application groups - About this page:
https://mesosphere.github.io/marathon/docs/application-groups.html
Does this work with docker containers? @swartzrock would like to have a group of 2 docker containers which are scheduled at the same time. Can you do this now? Please add docs that show in detail how to do this!
https://mesosphere.atlassian.net/browse/MARATHON-318 | non_priority | using docker w application groups about this page does this work with docker containers swartzrock would like to have a group of docker containers which are scheduled at the same time can you do this now please add docs that show in detail how to do this | 0 |
346,193 | 30,872,548,265 | IssuesEvent | 2023-08-03 12:22:29 | containers/podman-desktop | https://api.github.com/repos/containers/podman-desktop | opened | Implement Troubleshooting page object model representation | kind/enhancement ✨ area/tests 🚦 | ### Is your enhancement related to a problem? Please describe
We would make use of troubleshooting page in e2e tests - for various purposes - testing it and as a way to make tests more robust.
### Describe the solution you'd like
Simple e2e tests for troubleshooting page, and its representation in page object model. Also add various function so we know that image/containers/and other stores are fully loaded.
### Describe alternatives you've considered
_No response_
### Additional context
_No response_ | 1.0 | Implement Troubleshooting page object model representation - ### Is your enhancement related to a problem? Please describe
We would make use of troubleshooting page in e2e tests - for various purposes - testing it and as a way to make tests more robust.
### Describe the solution you'd like
Simple e2e tests for troubleshooting page, and its representation in page object model. Also add various function so we know that image/containers/and other stores are fully loaded.
### Describe alternatives you've considered
_No response_
### Additional context
_No response_ | non_priority | implement troubleshooting page object model representation is your enhancement related to a problem please describe we would make use of troubleshooting page in tests for various purposes testing it and as a way to make tests more robust describe the solution you d like simple tests for troubleshooting page and its representation in page object model also add various function so we know that image containers and other stores are fully loaded describe alternatives you ve considered no response additional context no response | 0 |
216,929 | 16,824,144,112 | IssuesEvent | 2021-06-17 16:15:46 | Realm667/WolfenDoom | https://api.github.com/repos/Realm667/WolfenDoom | closed | C1M3 unwanted nasty scrolling floors/ceilings plus | mapping playtesting | C1M3 ...
a) Floors and ceilings of sectors 1023, 1029, 1030 and 1037 have unwanted scroll. And the first four sectors scroll the sidedef textures, not the flat. Somehow linked to the 3D floor and the tag ?
b) While at it, the ceiling of sector 1703 should have a brightness of 128.
c) Texture on lines 6845 and 13667 should be the same. Can be clearly noticed when using the elevator at sectors 1330/1314.
| 1.0 | C1M3 unwanted nasty scrolling floors/ceilings plus - C1M3 ...
a) Floors and ceilings of sectors 1023, 1029, 1030 and 1037 have unwanted scroll. And the first four sectors scroll the sidedef textures, not the flat. Somehow linked to the 3D floor and the tag ?
b) While at it, the ceiling of sector 1703 should have a brightness of 128.
c) Texture on lines 6845 and 13667 should be the same. Can be clearly noticed when using the elevator at sectors 1330/1314.
| non_priority | unwanted nasty scrolling floors ceilings plus a floors and ceilings of sectors and have unwanted scroll and the first four sectors scroll the sidedef textures not the flat somehow linked to the floor and the tag b while at it the ceiling of sector should have a brightness of c texture on lines and should be the same can be clearly noticed when using the elevator at sectors | 0 |
52,886 | 13,772,603,173 | IssuesEvent | 2020-10-08 01:02:30 | RG4421/wp-calypso | https://api.github.com/repos/RG4421/wp-calypso | opened | CVE-2020-15174 (High) detected in electron-8.3.0.tgz | security vulnerability | ## CVE-2020-15174 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>electron-8.3.0.tgz</b></p></summary>
<p>Build cross platform desktop apps with JavaScript, HTML, and CSS</p>
<p>Library home page: <a href="https://registry.npmjs.org/electron/-/electron-8.3.0.tgz">https://registry.npmjs.org/electron/-/electron-8.3.0.tgz</a></p>
<p>Path to dependency file: wp-calypso/desktop/yarn.lock</p>
<p>Path to vulnerable library: wp-calypso/desktop/yarn.lock</p>
<p>
Dependency Hierarchy:
- :x: **electron-8.3.0.tgz** (Vulnerable Library)
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
In Electron before versions 11.0.0-beta.1, 10.0.1, 9.3.0 or 8.5.1 the `will-navigate` event that apps use to prevent navigations to unexpected destinations as per our security recommendations can be bypassed when a sub-frame performs a top-frame navigation across sites. The issue is patched in versions 11.0.0-beta.1, 10.0.1, 9.3.0 or 8.5.1 As a workaround sandbox all your iframes using the sandbox attribute. This will prevent them creating top-frame navigations and is good practice anyway.
<p>Publish Date: 2020-07-21
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-15174>CVE-2020-15174</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: High
- Privileges Required: None
- User Interaction: None
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: High
- 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://github.com/electron/electron/security/advisories/GHSA-2q4g-w47c-4674">https://github.com/electron/electron/security/advisories/GHSA-2q4g-w47c-4674</a></p>
<p>Release Date: 2020-07-21</p>
<p>Fix Resolution: v8.5.1, v9.3.0, v10.0.1, v11.0.0-beta.1</p>
</p>
</details>
<p></p>
***
:rescue_worker_helmet: Automatic Remediation is available for this issue
<!-- <REMEDIATE>{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"electron","packageVersion":"8.3.0","isTransitiveDependency":false,"dependencyTree":"electron:8.3.0","isMinimumFixVersionAvailable":true,"minimumFixVersion":"v8.5.1, v9.3.0, v10.0.1, v11.0.0-beta.1"}],"vulnerabilityIdentifier":"CVE-2020-15174","vulnerabilityDetails":"In Electron before versions 11.0.0-beta.1, 10.0.1, 9.3.0 or 8.5.1 the `will-navigate` event that apps use to prevent navigations to unexpected destinations as per our security recommendations can be bypassed when a sub-frame performs a top-frame navigation across sites. The issue is patched in versions 11.0.0-beta.1, 10.0.1, 9.3.0 or 8.5.1 As a workaround sandbox all your iframes using the sandbox attribute. This will prevent them creating top-frame navigations and is good practice anyway.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-15174","cvss3Severity":"high","cvss3Score":"7.5","cvss3Metrics":{"A":"Low","AC":"High","PR":"None","S":"Changed","C":"None","UI":"None","AV":"Network","I":"High"},"extraData":{}}</REMEDIATE> --> | True | CVE-2020-15174 (High) detected in electron-8.3.0.tgz - ## CVE-2020-15174 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>electron-8.3.0.tgz</b></p></summary>
<p>Build cross platform desktop apps with JavaScript, HTML, and CSS</p>
<p>Library home page: <a href="https://registry.npmjs.org/electron/-/electron-8.3.0.tgz">https://registry.npmjs.org/electron/-/electron-8.3.0.tgz</a></p>
<p>Path to dependency file: wp-calypso/desktop/yarn.lock</p>
<p>Path to vulnerable library: wp-calypso/desktop/yarn.lock</p>
<p>
Dependency Hierarchy:
- :x: **electron-8.3.0.tgz** (Vulnerable Library)
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
In Electron before versions 11.0.0-beta.1, 10.0.1, 9.3.0 or 8.5.1 the `will-navigate` event that apps use to prevent navigations to unexpected destinations as per our security recommendations can be bypassed when a sub-frame performs a top-frame navigation across sites. The issue is patched in versions 11.0.0-beta.1, 10.0.1, 9.3.0 or 8.5.1 As a workaround sandbox all your iframes using the sandbox attribute. This will prevent them creating top-frame navigations and is good practice anyway.
<p>Publish Date: 2020-07-21
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-15174>CVE-2020-15174</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: High
- Privileges Required: None
- User Interaction: None
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: High
- 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://github.com/electron/electron/security/advisories/GHSA-2q4g-w47c-4674">https://github.com/electron/electron/security/advisories/GHSA-2q4g-w47c-4674</a></p>
<p>Release Date: 2020-07-21</p>
<p>Fix Resolution: v8.5.1, v9.3.0, v10.0.1, v11.0.0-beta.1</p>
</p>
</details>
<p></p>
***
:rescue_worker_helmet: Automatic Remediation is available for this issue
<!-- <REMEDIATE>{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"electron","packageVersion":"8.3.0","isTransitiveDependency":false,"dependencyTree":"electron:8.3.0","isMinimumFixVersionAvailable":true,"minimumFixVersion":"v8.5.1, v9.3.0, v10.0.1, v11.0.0-beta.1"}],"vulnerabilityIdentifier":"CVE-2020-15174","vulnerabilityDetails":"In Electron before versions 11.0.0-beta.1, 10.0.1, 9.3.0 or 8.5.1 the `will-navigate` event that apps use to prevent navigations to unexpected destinations as per our security recommendations can be bypassed when a sub-frame performs a top-frame navigation across sites. The issue is patched in versions 11.0.0-beta.1, 10.0.1, 9.3.0 or 8.5.1 As a workaround sandbox all your iframes using the sandbox attribute. This will prevent them creating top-frame navigations and is good practice anyway.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-15174","cvss3Severity":"high","cvss3Score":"7.5","cvss3Metrics":{"A":"Low","AC":"High","PR":"None","S":"Changed","C":"None","UI":"None","AV":"Network","I":"High"},"extraData":{}}</REMEDIATE> --> | non_priority | cve high detected in electron tgz cve high severity vulnerability vulnerable library electron tgz build cross platform desktop apps with javascript html and css library home page a href path to dependency file wp calypso desktop yarn lock path to vulnerable library wp calypso desktop yarn lock dependency hierarchy x electron tgz vulnerable library found in base branch master vulnerability details in electron before versions beta or the will navigate event that apps use to prevent navigations to unexpected destinations as per our security recommendations can be bypassed when a sub frame performs a top frame navigation across sites the issue is patched in versions beta or as a workaround sandbox all your iframes using the sandbox attribute this will prevent them creating top frame navigations and is good practice anyway 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 changed impact metrics confidentiality impact none integrity impact high availability impact low for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution beta rescue worker helmet automatic remediation is available for this issue isopenpronvulnerability true ispackagebased true isdefaultbranch true packages vulnerabilityidentifier cve vulnerabilitydetails in electron before versions beta or the will navigate event that apps use to prevent navigations to unexpected destinations as per our security recommendations can be bypassed when a sub frame performs a top frame navigation across sites the issue is patched in versions beta or as a workaround sandbox all your iframes using the sandbox attribute this will prevent them creating top frame navigations and is good practice anyway vulnerabilityurl | 0 |
302,850 | 26,167,937,009 | IssuesEvent | 2023-01-01 14:31:35 | appium/appium | https://api.github.com/repos/appium/appium | closed | Popup blocker still occurs even when setting 'safariAllowPopups' capability | Bug XCUITest P1 | ## The problem
When running a simple script that is supposed to open a new window in safari browser, I can't get through the popup blocker. The capabilities that are supposed to disable to popup blocker seem to not work for me.
## Environment
* Appium version that exhibits the issue: 1.6.3
* Desktop OS/version used to run Appium: iOS 10.0
* Mobile platform/version under test: iPhone 6 simulator
* Real device or emulator/simulator: simulator
* Here is a link to the sauceLabs session https://saucelabs.com/beta/tests/459caa2ffb0941558c2429e8b7a057da/commands#5
## Code To Reproduce Issue
```
var webdriver = require('selenium-webdriver'),
By = webdriver.By,
username = 'u',
accessKey = 'k',
driver;
var caps = {
"browserName": "Safari",
"appiumVersion": "1.6.3",
"deviceName": "iPhone 6 Simulator",
"deviceOrientation": "portrait",
"platformVersion": "10.0",
"platformName": "iOS",
"safariAllowPopups": true,
"safariOpenLinksInBackground": true,
"autoAcceptAlerts": true,
"unexpectedAlertBehaviour": "accept"
}
caps['username'] = username;
caps['accessKey'] = accessKey;
driver = new webdriver.Builder().
withCapabilities(caps).
usingServer("http://" + username + ":" + accessKey +
"@ondemand.saucelabs.com:80/wd/hub").
build();
var url = "http://the-internet.herokuapp.com/redirector"
driver.get(url);
driver.findElement(By.css("[target='_blank']")).click();
driver.quit();
``` | 1.0 | Popup blocker still occurs even when setting 'safariAllowPopups' capability - ## The problem
When running a simple script that is supposed to open a new window in safari browser, I can't get through the popup blocker. The capabilities that are supposed to disable to popup blocker seem to not work for me.
## Environment
* Appium version that exhibits the issue: 1.6.3
* Desktop OS/version used to run Appium: iOS 10.0
* Mobile platform/version under test: iPhone 6 simulator
* Real device or emulator/simulator: simulator
* Here is a link to the sauceLabs session https://saucelabs.com/beta/tests/459caa2ffb0941558c2429e8b7a057da/commands#5
## Code To Reproduce Issue
```
var webdriver = require('selenium-webdriver'),
By = webdriver.By,
username = 'u',
accessKey = 'k',
driver;
var caps = {
"browserName": "Safari",
"appiumVersion": "1.6.3",
"deviceName": "iPhone 6 Simulator",
"deviceOrientation": "portrait",
"platformVersion": "10.0",
"platformName": "iOS",
"safariAllowPopups": true,
"safariOpenLinksInBackground": true,
"autoAcceptAlerts": true,
"unexpectedAlertBehaviour": "accept"
}
caps['username'] = username;
caps['accessKey'] = accessKey;
driver = new webdriver.Builder().
withCapabilities(caps).
usingServer("http://" + username + ":" + accessKey +
"@ondemand.saucelabs.com:80/wd/hub").
build();
var url = "http://the-internet.herokuapp.com/redirector"
driver.get(url);
driver.findElement(By.css("[target='_blank']")).click();
driver.quit();
``` | non_priority | popup blocker still occurs even when setting safariallowpopups capability the problem when running a simple script that is supposed to open a new window in safari browser i can t get through the popup blocker the capabilities that are supposed to disable to popup blocker seem to not work for me environment appium version that exhibits the issue desktop os version used to run appium ios mobile platform version under test iphone simulator real device or emulator simulator simulator here is a link to the saucelabs session code to reproduce issue var webdriver require selenium webdriver by webdriver by username u accesskey k driver var caps browsername safari appiumversion devicename iphone simulator deviceorientation portrait platformversion platformname ios safariallowpopups true safariopenlinksinbackground true autoacceptalerts true unexpectedalertbehaviour accept caps username caps accesskey driver new webdriver builder withcapabilities caps usingserver username accesskey ondemand saucelabs com wd hub build var url driver get url driver findelement by css click driver quit | 0 |
31,531 | 8,708,131,429 | IssuesEvent | 2018-12-06 10:01:46 | open-contracting/infrastructure | https://api.github.com/repos/open-contracting/infrastructure | closed | Build process | build process | I've updated and simplified the default build process for OCDS documentation. However, when trying to write a PR for this repo, I'm confused that requirements.in uses an unpinned version of Sphinx, and a version of recommonmark that is incompatible with the rest of our tooling. Is requirements.in in use, and if not can it be deleted?
The repository also omits Babel configuration files, which are required to support the translation of codelists and schema. I assume this omission isn't deliberate?
If my assumptions are correct, I'm happy to proceed with a PR. | 1.0 | Build process - I've updated and simplified the default build process for OCDS documentation. However, when trying to write a PR for this repo, I'm confused that requirements.in uses an unpinned version of Sphinx, and a version of recommonmark that is incompatible with the rest of our tooling. Is requirements.in in use, and if not can it be deleted?
The repository also omits Babel configuration files, which are required to support the translation of codelists and schema. I assume this omission isn't deliberate?
If my assumptions are correct, I'm happy to proceed with a PR. | non_priority | build process i ve updated and simplified the default build process for ocds documentation however when trying to write a pr for this repo i m confused that requirements in uses an unpinned version of sphinx and a version of recommonmark that is incompatible with the rest of our tooling is requirements in in use and if not can it be deleted the repository also omits babel configuration files which are required to support the translation of codelists and schema i assume this omission isn t deliberate if my assumptions are correct i m happy to proceed with a pr | 0 |
63,660 | 7,736,365,727 | IssuesEvent | 2018-05-28 01:40:15 | PHPfox-Official/phpfox-v4-issues | https://api.github.com/repos/PHPfox-Official/phpfox-v4-issues | closed | Expand Cron To Detect Last Run | Working as Designed | # Important!
Please follow this template!
----------------------------------------
## What happened?
...
The cron area of settings currently only detects the file path. It does not show when the last cron was run. It also doesn't give you the complete cron command, which it should based on detected Linux environmental variables.
## Steps to reproduce:
1. Go to Admin CP
2. Go to Settings > Cron
3. This is where the magic happens.
## What is expected?
...
Cron provide last run time. Also full in page documentation to be provided instead of a link to the help article for on site access.
## Browsers and Devices tested
(Example: Chrome on iPhone X, Safari on Macbook, Miscrosoft Edge on Windown 10, Firefox on Ubuntu 16.04, ...)
N/A server issue - Chrome Firefox tested windows 10
## Server information
(Example: CentOS 7, php 7.1 apache)
Centos 7 Linux php7.2 Apache2
...
## phpFox version
(Example: phpFox 4.6.0)
v4.6.2B3
...
## Screenshots
...
| 1.0 | Expand Cron To Detect Last Run - # Important!
Please follow this template!
----------------------------------------
## What happened?
...
The cron area of settings currently only detects the file path. It does not show when the last cron was run. It also doesn't give you the complete cron command, which it should based on detected Linux environmental variables.
## Steps to reproduce:
1. Go to Admin CP
2. Go to Settings > Cron
3. This is where the magic happens.
## What is expected?
...
Cron provide last run time. Also full in page documentation to be provided instead of a link to the help article for on site access.
## Browsers and Devices tested
(Example: Chrome on iPhone X, Safari on Macbook, Miscrosoft Edge on Windown 10, Firefox on Ubuntu 16.04, ...)
N/A server issue - Chrome Firefox tested windows 10
## Server information
(Example: CentOS 7, php 7.1 apache)
Centos 7 Linux php7.2 Apache2
...
## phpFox version
(Example: phpFox 4.6.0)
v4.6.2B3
...
## Screenshots
...
| non_priority | expand cron to detect last run important please follow this template what happened the cron area of settings currently only detects the file path it does not show when the last cron was run it also doesn t give you the complete cron command which it should based on detected linux environmental variables steps to reproduce go to admin cp go to settings cron this is where the magic happens what is expected cron provide last run time also full in page documentation to be provided instead of a link to the help article for on site access browsers and devices tested example chrome on iphone x safari on macbook miscrosoft edge on windown firefox on ubuntu n a server issue chrome firefox tested windows server information example centos php apache centos linux phpfox version example phpfox screenshots | 0 |
89,141 | 15,823,758,781 | IssuesEvent | 2021-04-06 01:34:47 | bsbtd/Teste | https://api.github.com/repos/bsbtd/Teste | opened | CVE-2021-26707 (Medium) detected in merge-deep-3.0.2.tgz | security vulnerability | ## CVE-2021-26707 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>merge-deep-3.0.2.tgz</b></p></summary>
<p>Recursively merge values in a javascript object.</p>
<p>Library home page: <a href="https://registry.npmjs.org/merge-deep/-/merge-deep-3.0.2.tgz">https://registry.npmjs.org/merge-deep/-/merge-deep-3.0.2.tgz</a></p>
<p>Path to dependency file: Teste/pro-table/package.json</p>
<p>Path to vulnerable library: Teste/pro-table/node_modules/merge-deep/package.json</p>
<p>
Dependency Hierarchy:
- babel-preset-umi-3.1.2.tgz (Root Library)
- webpack-4.3.3.tgz
- plugin-svgo-4.3.1.tgz
- :x: **merge-deep-3.0.2.tgz** (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>
A flaw was found in merge-deep before 3.0.3. A prototype pollution issue of Object.prototype via a constructor payload may lead to denial of service and other consequences.
<p>Publish Date: 2021-02-05
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-26707>CVE-2021-26707</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://bugzilla.redhat.com/show_bug.cgi?id=1922259">https://bugzilla.redhat.com/show_bug.cgi?id=1922259</a></p>
<p>Release Date: 2021-02-05</p>
<p>Fix Resolution: 3.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-26707 (Medium) detected in merge-deep-3.0.2.tgz - ## CVE-2021-26707 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>merge-deep-3.0.2.tgz</b></p></summary>
<p>Recursively merge values in a javascript object.</p>
<p>Library home page: <a href="https://registry.npmjs.org/merge-deep/-/merge-deep-3.0.2.tgz">https://registry.npmjs.org/merge-deep/-/merge-deep-3.0.2.tgz</a></p>
<p>Path to dependency file: Teste/pro-table/package.json</p>
<p>Path to vulnerable library: Teste/pro-table/node_modules/merge-deep/package.json</p>
<p>
Dependency Hierarchy:
- babel-preset-umi-3.1.2.tgz (Root Library)
- webpack-4.3.3.tgz
- plugin-svgo-4.3.1.tgz
- :x: **merge-deep-3.0.2.tgz** (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>
A flaw was found in merge-deep before 3.0.3. A prototype pollution issue of Object.prototype via a constructor payload may lead to denial of service and other consequences.
<p>Publish Date: 2021-02-05
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-26707>CVE-2021-26707</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://bugzilla.redhat.com/show_bug.cgi?id=1922259">https://bugzilla.redhat.com/show_bug.cgi?id=1922259</a></p>
<p>Release Date: 2021-02-05</p>
<p>Fix Resolution: 3.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 merge deep tgz cve medium severity vulnerability vulnerable library merge deep tgz recursively merge values in a javascript object library home page a href path to dependency file teste pro table package json path to vulnerable library teste pro table node modules merge deep package json dependency hierarchy babel preset umi tgz root library webpack tgz plugin svgo tgz x merge deep tgz vulnerable library vulnerability details a flaw was found in merge deep before a prototype pollution issue of object prototype via a constructor payload may lead to denial of service and other consequences 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 step up your open source security game with whitesource | 0 |
66,182 | 7,968,756,197 | IssuesEvent | 2018-07-16 05:49:43 | maxmagee/chick-fil-a | https://api.github.com/repos/maxmagee/chick-fil-a | opened | Implement Generalized Help Screen | design enhancement | Each of the icons on the Get Help screen open a page that has an image at the top along with article titles and paragraphs for each article.
Instead of implementing 6 different pages, we should generalize this out to a screen component that can accept an image and article objects.
In addition to this, I need to research how to render expandable views (think accordion-like) when the article title is pressed.
- [ ] Design screen in Sketch
- [ ] Research how to do expandable views
- [ ] Implement generalized screen | 1.0 | Implement Generalized Help Screen - Each of the icons on the Get Help screen open a page that has an image at the top along with article titles and paragraphs for each article.
Instead of implementing 6 different pages, we should generalize this out to a screen component that can accept an image and article objects.
In addition to this, I need to research how to render expandable views (think accordion-like) when the article title is pressed.
- [ ] Design screen in Sketch
- [ ] Research how to do expandable views
- [ ] Implement generalized screen | non_priority | implement generalized help screen each of the icons on the get help screen open a page that has an image at the top along with article titles and paragraphs for each article instead of implementing different pages we should generalize this out to a screen component that can accept an image and article objects in addition to this i need to research how to render expandable views think accordion like when the article title is pressed design screen in sketch research how to do expandable views implement generalized screen | 0 |
343,680 | 24,777,512,513 | IssuesEvent | 2022-10-23 22:36:00 | Easy1089/Proyecto-Fullstack-ISPC-G1 | https://api.github.com/repos/Easy1089/Proyecto-Fullstack-ISPC-G1 | closed | #TK08 Creacion de wiki para registro de daily, retro, etc. relacionado con el proyecto. | documentation | Creacion de wiki del proyecto:
Clone this wiki locally:
https://github.com/Easy1089/Proyecto-Fullstack-ISPC-G1.wiki.git | 1.0 | #TK08 Creacion de wiki para registro de daily, retro, etc. relacionado con el proyecto. - Creacion de wiki del proyecto:
Clone this wiki locally:
https://github.com/Easy1089/Proyecto-Fullstack-ISPC-G1.wiki.git | non_priority | creacion de wiki para registro de daily retro etc relacionado con el proyecto creacion de wiki del proyecto clone this wiki locally | 0 |
28,684 | 7,017,169,779 | IssuesEvent | 2017-12-21 08:32:15 | jOOQ/jOOQ | https://api.github.com/repos/jOOQ/jOOQ | opened | Add a way to specify what object type a <forcedType/> should match | C: Code Generation P: Medium T: Enhancement | Currently, `<forcedType/>` configurations simply match everything that matches their `<expression/>` and `<types/>` patterns. This can be a bit annoying when several objects have similar names, e.g. when matching:
```xml
<expression>.*?\.ID</expression>
```
This will match all `ID` columns, attributes, parameters, sequences, etc. Even when qualifying the expression, it could be ambiguous in the case of table valued functions, which can have both an `ID` parameter and an `ID` return column. In that case, it would be great to be able to specify:
```xml
<expression>.*?\.ID</expression>
<objectType>PARAMETER</objectType>
```
| 1.0 | Add a way to specify what object type a <forcedType/> should match - Currently, `<forcedType/>` configurations simply match everything that matches their `<expression/>` and `<types/>` patterns. This can be a bit annoying when several objects have similar names, e.g. when matching:
```xml
<expression>.*?\.ID</expression>
```
This will match all `ID` columns, attributes, parameters, sequences, etc. Even when qualifying the expression, it could be ambiguous in the case of table valued functions, which can have both an `ID` parameter and an `ID` return column. In that case, it would be great to be able to specify:
```xml
<expression>.*?\.ID</expression>
<objectType>PARAMETER</objectType>
```
| non_priority | add a way to specify what object type a should match currently configurations simply match everything that matches their and patterns this can be a bit annoying when several objects have similar names e g when matching xml id this will match all id columns attributes parameters sequences etc even when qualifying the expression it could be ambiguous in the case of table valued functions which can have both an id parameter and an id return column in that case it would be great to be able to specify xml id parameter | 0 |
941 | 2,666,406,014 | IssuesEvent | 2015-03-21 14:56:23 | jmxtrans/jmxtrans2 | https://api.github.com/repos/jmxtrans/jmxtrans2 | closed | Time- related tests failure | build | 2 tests are failing for me: logLineContainsAllRequiredInformation and logLineContainsException:
java.lang.AssertionError:
Expecting:
"1969.12.31 16:16:40.000 - DEBUG - testLogger - testMessage
"
to match pattern:
".*1970\.01\.01 ..:16:40\.000.*"
at org.jmxtrans.core.log.PrintWriterLoggerTest.logLineContainsAllRequiredInformation(PrintWriterLoggerTest.java:122)
Seems it is related to me being in UTC+7 timezone. | 1.0 | Time- related tests failure - 2 tests are failing for me: logLineContainsAllRequiredInformation and logLineContainsException:
java.lang.AssertionError:
Expecting:
"1969.12.31 16:16:40.000 - DEBUG - testLogger - testMessage
"
to match pattern:
".*1970\.01\.01 ..:16:40\.000.*"
at org.jmxtrans.core.log.PrintWriterLoggerTest.logLineContainsAllRequiredInformation(PrintWriterLoggerTest.java:122)
Seems it is related to me being in UTC+7 timezone. | non_priority | time related tests failure tests are failing for me loglinecontainsallrequiredinformation and loglinecontainsexception java lang assertionerror expecting debug testlogger testmessage to match pattern at org jmxtrans core log printwriterloggertest loglinecontainsallrequiredinformation printwriterloggertest java seems it is related to me being in utc timezone | 0 |
162,297 | 20,178,650,461 | IssuesEvent | 2022-02-10 16:26:18 | vital-ws/empty | https://api.github.com/repos/vital-ws/empty | opened | WS-2022-0071 (Medium) detected in tensorflow-2.5.2-cp37-cp37m-manylinux2010_x86_64.whl | security vulnerability | ## WS-2022-0071 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>tensorflow-2.5.2-cp37-cp37m-manylinux2010_x86_64.whl</b></p></summary>
<p>TensorFlow is an open source machine learning framework for everyone.</p>
<p>Library home page: <a href="https://files.pythonhosted.org/packages/5f/4d/b675803c25feca2e1a896c2c38380db4d9477d8ce4bd58ea103837793527/tensorflow-2.5.2-cp37-cp37m-manylinux2010_x86_64.whl">https://files.pythonhosted.org/packages/5f/4d/b675803c25feca2e1a896c2c38380db4d9477d8ce4bd58ea103837793527/tensorflow-2.5.2-cp37-cp37m-manylinux2010_x86_64.whl</a></p>
<p>Path to dependency file: /requirements.txt</p>
<p>Path to vulnerable library: /requirements.txt</p>
<p>
Dependency Hierarchy:
- :x: **tensorflow-2.5.2-cp37-cp37m-manylinux2010_x86_64.whl** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/vital-ws/empty/commit/a22b0de94d5c4e9c141f2b7c59bdf4ec92aee8b5">a22b0de94d5c4e9c141f2b7c59bdf4ec92aee8b5</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
Integer Overflow or Wraparound in TensorFlow
<p>Publish Date: 2022-02-10
<p>URL: <a href=https://github.com/tensorflow/tensorflow/commit/be7b286d40bc68cb0b56f702186cc4837d508058>WS-2022-0071</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://github.com/advisories/GHSA-wcv5-vrvr-3rx2">https://github.com/advisories/GHSA-wcv5-vrvr-3rx2</a></p>
<p>Release Date: 2022-02-10</p>
<p>Fix Resolution: tensorflow - 2.5.3,2.6.3,2.7.1,2.8.0;tensorflow-cpu - 2.5.3,2.6.3,2.7.1,2.8.0;tensorflow-gpu - 2.5.3,2.6.3,2.7.1,2.8.0</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":false,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"Python","packageName":"tensorflow","packageVersion":"2.5.2","packageFilePaths":["/requirements.txt"],"isTransitiveDependency":false,"dependencyTree":"tensorflow:2.5.2","isMinimumFixVersionAvailable":true,"minimumFixVersion":"tensorflow - 2.5.3,2.6.3,2.7.1,2.8.0;tensorflow-cpu - 2.5.3,2.6.3,2.7.1,2.8.0;tensorflow-gpu - 2.5.3,2.6.3,2.7.1,2.8.0","isBinary":false}],"baseBranches":["main"],"vulnerabilityIdentifier":"WS-2022-0071","vulnerabilityDetails":"Integer Overflow or Wraparound in TensorFlow","vulnerabilityUrl":"https://github.com/tensorflow/tensorflow/commit/be7b286d40bc68cb0b56f702186cc4837d508058","cvss3Severity":"medium","cvss3Score":"5.5","cvss3Metrics":{"A":"High","AC":"Low","PR":"None","S":"Unchanged","C":"None","UI":"Required","AV":"Local","I":"None"},"extraData":{}}</REMEDIATE> --> | True | WS-2022-0071 (Medium) detected in tensorflow-2.5.2-cp37-cp37m-manylinux2010_x86_64.whl - ## WS-2022-0071 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>tensorflow-2.5.2-cp37-cp37m-manylinux2010_x86_64.whl</b></p></summary>
<p>TensorFlow is an open source machine learning framework for everyone.</p>
<p>Library home page: <a href="https://files.pythonhosted.org/packages/5f/4d/b675803c25feca2e1a896c2c38380db4d9477d8ce4bd58ea103837793527/tensorflow-2.5.2-cp37-cp37m-manylinux2010_x86_64.whl">https://files.pythonhosted.org/packages/5f/4d/b675803c25feca2e1a896c2c38380db4d9477d8ce4bd58ea103837793527/tensorflow-2.5.2-cp37-cp37m-manylinux2010_x86_64.whl</a></p>
<p>Path to dependency file: /requirements.txt</p>
<p>Path to vulnerable library: /requirements.txt</p>
<p>
Dependency Hierarchy:
- :x: **tensorflow-2.5.2-cp37-cp37m-manylinux2010_x86_64.whl** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/vital-ws/empty/commit/a22b0de94d5c4e9c141f2b7c59bdf4ec92aee8b5">a22b0de94d5c4e9c141f2b7c59bdf4ec92aee8b5</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
Integer Overflow or Wraparound in TensorFlow
<p>Publish Date: 2022-02-10
<p>URL: <a href=https://github.com/tensorflow/tensorflow/commit/be7b286d40bc68cb0b56f702186cc4837d508058>WS-2022-0071</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://github.com/advisories/GHSA-wcv5-vrvr-3rx2">https://github.com/advisories/GHSA-wcv5-vrvr-3rx2</a></p>
<p>Release Date: 2022-02-10</p>
<p>Fix Resolution: tensorflow - 2.5.3,2.6.3,2.7.1,2.8.0;tensorflow-cpu - 2.5.3,2.6.3,2.7.1,2.8.0;tensorflow-gpu - 2.5.3,2.6.3,2.7.1,2.8.0</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":false,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"Python","packageName":"tensorflow","packageVersion":"2.5.2","packageFilePaths":["/requirements.txt"],"isTransitiveDependency":false,"dependencyTree":"tensorflow:2.5.2","isMinimumFixVersionAvailable":true,"minimumFixVersion":"tensorflow - 2.5.3,2.6.3,2.7.1,2.8.0;tensorflow-cpu - 2.5.3,2.6.3,2.7.1,2.8.0;tensorflow-gpu - 2.5.3,2.6.3,2.7.1,2.8.0","isBinary":false}],"baseBranches":["main"],"vulnerabilityIdentifier":"WS-2022-0071","vulnerabilityDetails":"Integer Overflow or Wraparound in TensorFlow","vulnerabilityUrl":"https://github.com/tensorflow/tensorflow/commit/be7b286d40bc68cb0b56f702186cc4837d508058","cvss3Severity":"medium","cvss3Score":"5.5","cvss3Metrics":{"A":"High","AC":"Low","PR":"None","S":"Unchanged","C":"None","UI":"Required","AV":"Local","I":"None"},"extraData":{}}</REMEDIATE> --> | non_priority | ws medium detected in tensorflow whl ws medium severity vulnerability vulnerable library tensorflow whl tensorflow is an open source machine learning framework for everyone library home page a href path to dependency file requirements txt path to vulnerable library requirements txt dependency hierarchy x tensorflow whl vulnerable library found in head commit a href found in base branch main vulnerability details integer overflow or wraparound in tensorflow 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 tensorflow tensorflow cpu tensorflow gpu isopenpronvulnerability false ispackagebased true isdefaultbranch true packages istransitivedependency false dependencytree tensorflow isminimumfixversionavailable true minimumfixversion tensorflow tensorflow cpu tensorflow gpu isbinary false basebranches vulnerabilityidentifier ws vulnerabilitydetails integer overflow or wraparound in tensorflow vulnerabilityurl | 0 |
197,462 | 14,925,825,869 | IssuesEvent | 2021-01-24 08:33:05 | apache/apisix-dashboard | https://api.github.com/repos/apache/apisix-dashboard | closed | after editing a Service, the upstream info will be lost. | bug frontend testcase | # Bug report
## Describe the bug
## How to Reproduce
1. Go to Service List;
2. Find a Service and click on Edit;
3. Update Upstream configuration;
4. Submit;
5. Edit again but without upstream configuration.
## System information
- Version: master branch | 1.0 | after editing a Service, the upstream info will be lost. - # Bug report
## Describe the bug
## How to Reproduce
1. Go to Service List;
2. Find a Service and click on Edit;
3. Update Upstream configuration;
4. Submit;
5. Edit again but without upstream configuration.
## System information
- Version: master branch | non_priority | after editing a service the upstream info will be lost bug report describe the bug how to reproduce go to service list find a service and click on edit update upstream configuration submit edit again but without upstream configuration system information version master branch | 0 |
210,494 | 23,754,801,910 | IssuesEvent | 2022-09-01 01:17:31 | turkdevops/sourcegraph | https://api.github.com/repos/turkdevops/sourcegraph | closed | CVE-2020-8116 (High) detected in dot-prop-4.2.0.tgz - autoclosed | security vulnerability | ## CVE-2020-8116 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>dot-prop-4.2.0.tgz</b></p></summary>
<p>Get, set, or delete a property from a nested object using a dot path</p>
<p>Library home page: <a href="https://registry.npmjs.org/dot-prop/-/dot-prop-4.2.0.tgz">https://registry.npmjs.org/dot-prop/-/dot-prop-4.2.0.tgz</a></p>
<p>
Dependency Hierarchy:
- open-color-1.7.0.tgz (Root Library)
- npm-6.13.4.tgz
- update-notifier-2.5.0.tgz
- configstore-3.1.2.tgz
- :x: **dot-prop-4.2.0.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/turkdevops/sourcegraph/commit/5a4a7def9ddff6354e22069c494feb0f30196e36">5a4a7def9ddff6354e22069c494feb0f30196e36</a></p>
<p>Found in base branch: <b>dev/seed-tool</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
Prototype pollution vulnerability in dot-prop npm package versions before 4.2.1 and versions 5.x before 5.1.1 allows an attacker to add arbitrary properties to JavaScript language constructs such as objects.
<p>Publish Date: 2020-02-04
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-8116>CVE-2020-8116</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-8116">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-8116</a></p>
<p>Release Date: 2020-02-04</p>
<p>Fix Resolution (dot-prop): 4.2.1</p>
<p>Direct dependency fix Resolution (open-color): 1.8.0</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | CVE-2020-8116 (High) detected in dot-prop-4.2.0.tgz - autoclosed - ## CVE-2020-8116 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>dot-prop-4.2.0.tgz</b></p></summary>
<p>Get, set, or delete a property from a nested object using a dot path</p>
<p>Library home page: <a href="https://registry.npmjs.org/dot-prop/-/dot-prop-4.2.0.tgz">https://registry.npmjs.org/dot-prop/-/dot-prop-4.2.0.tgz</a></p>
<p>
Dependency Hierarchy:
- open-color-1.7.0.tgz (Root Library)
- npm-6.13.4.tgz
- update-notifier-2.5.0.tgz
- configstore-3.1.2.tgz
- :x: **dot-prop-4.2.0.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/turkdevops/sourcegraph/commit/5a4a7def9ddff6354e22069c494feb0f30196e36">5a4a7def9ddff6354e22069c494feb0f30196e36</a></p>
<p>Found in base branch: <b>dev/seed-tool</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
Prototype pollution vulnerability in dot-prop npm package versions before 4.2.1 and versions 5.x before 5.1.1 allows an attacker to add arbitrary properties to JavaScript language constructs such as objects.
<p>Publish Date: 2020-02-04
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-8116>CVE-2020-8116</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-8116">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-8116</a></p>
<p>Release Date: 2020-02-04</p>
<p>Fix Resolution (dot-prop): 4.2.1</p>
<p>Direct dependency fix Resolution (open-color): 1.8.0</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_priority | cve high detected in dot prop tgz autoclosed cve high severity vulnerability vulnerable library dot prop tgz get set or delete a property from a nested object using a dot path library home page a href dependency hierarchy open color tgz root library npm tgz update notifier tgz configstore tgz x dot prop tgz vulnerable library found in head commit a href found in base branch dev seed tool vulnerability details prototype pollution vulnerability in dot prop npm package versions before and versions x before allows an attacker to add arbitrary properties to javascript language constructs such as objects 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 dot prop direct dependency fix resolution open color step up your open source security game with mend | 0 |
55,104 | 13,964,072,254 | IssuesEvent | 2020-10-25 16:39:49 | PrideInLondon/pride-london-new-app | https://api.github.com/repos/PrideInLondon/pride-london-new-app | closed | Dependabot couldn't find the branch master | Security | Dependabot was set up to create pull requests against the branch `master`, but couldn't find it.
If the branch has been permanently deleted you can update Dependabot's target branch in the `.dependabot/config.yml` file in this repo.
[View the update logs](https://app.dependabot.com/accounts/PrideInLondon/update-logs/52144517). | True | Dependabot couldn't find the branch master - Dependabot was set up to create pull requests against the branch `master`, but couldn't find it.
If the branch has been permanently deleted you can update Dependabot's target branch in the `.dependabot/config.yml` file in this repo.
[View the update logs](https://app.dependabot.com/accounts/PrideInLondon/update-logs/52144517). | non_priority | dependabot couldn t find the branch master dependabot was set up to create pull requests against the branch master but couldn t find it if the branch has been permanently deleted you can update dependabot s target branch in the dependabot config yml file in this repo | 0 |
286,005 | 24,712,858,510 | IssuesEvent | 2022-10-20 03:17:11 | microsoft/playwright | https://api.github.com/repos/microsoft/playwright | closed | [Feature]: Allow `describe` to be called in files other than test | P3-collecting-feedback feature-test-runner | ### Feature request
Currently, for our framework using Protractor, Jasmine, and Typescript, I have an override for the jasmine describe function with my own custom function. This allows me to do something like this in the test file:
```
login.loginDescribe(
My highest level describe description ',
[BackendService.REALAPI, BackendService.MOCKAPI], // this test will now run twice, once hitting a static deployed environment and again against a localhost for the mock end point.
Local, // can also pass "Saucelabs" then it will automatically take in sauce labs configs and run the test in the sauce labs platform
[InvitedAs.OWNER], // this and the remaining two other arguments allow us to read the username and password from a secrets file for login credentials.
personA,
TenantA,
() => {..............
```
I tried to do something similar with Playwright but got this error:
"Error: describe() can only be called in a test file"
The error makes sense too since I am calling `test.describe` in a ts class file that has the `loginDescribe` method and not a test file.
The request is for the test.describe to be allowed to be called in other files as well.
Is this possible? | 1.0 | [Feature]: Allow `describe` to be called in files other than test - ### Feature request
Currently, for our framework using Protractor, Jasmine, and Typescript, I have an override for the jasmine describe function with my own custom function. This allows me to do something like this in the test file:
```
login.loginDescribe(
My highest level describe description ',
[BackendService.REALAPI, BackendService.MOCKAPI], // this test will now run twice, once hitting a static deployed environment and again against a localhost for the mock end point.
Local, // can also pass "Saucelabs" then it will automatically take in sauce labs configs and run the test in the sauce labs platform
[InvitedAs.OWNER], // this and the remaining two other arguments allow us to read the username and password from a secrets file for login credentials.
personA,
TenantA,
() => {..............
```
I tried to do something similar with Playwright but got this error:
"Error: describe() can only be called in a test file"
The error makes sense too since I am calling `test.describe` in a ts class file that has the `loginDescribe` method and not a test file.
The request is for the test.describe to be allowed to be called in other files as well.
Is this possible? | non_priority | allow describe to be called in files other than test feature request currently for our framework using protractor jasmine and typescript i have an override for the jasmine describe function with my own custom function this allows me to do something like this in the test file login logindescribe my highest level describe description this test will now run twice once hitting a static deployed environment and again against a localhost for the mock end point local can also pass saucelabs then it will automatically take in sauce labs configs and run the test in the sauce labs platform this and the remaining two other arguments allow us to read the username and password from a secrets file for login credentials persona tenanta i tried to do something similar with playwright but got this error error describe can only be called in a test file the error makes sense too since i am calling test describe in a ts class file that has the logindescribe method and not a test file the request is for the test describe to be allowed to be called in other files as well is this possible | 0 |
159,626 | 20,085,865,145 | IssuesEvent | 2022-02-05 01:03:25 | doc-ai/tensorflow-ios-framework | https://api.github.com/repos/doc-ai/tensorflow-ios-framework | opened | CVE-2021-29585 (High) detected in tensorflowv2.0.2 | security vulnerability | ## CVE-2021-29585 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>tensorflowv2.0.2</b></p></summary>
<p>
<p>An Open Source Machine Learning Framework for Everyone</p>
<p>Library home page: <a href=https://github.com/tensorflow/tensorflow.git>https://github.com/tensorflow/tensorflow.git</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 (0)</summary>
<p></p>
<p>
</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>
TensorFlow is an end-to-end open source platform for machine learning. The TFLite computation for size of output after padding, `ComputeOutSize`(https://github.com/tensorflow/tensorflow/blob/0c9692ae7b1671c983569e5d3de5565843d500cf/tensorflow/lite/kernels/padding.h#L43-L55), does not check that the `stride` argument is not 0 before doing the division. Users can craft special models such that `ComputeOutSize` is called with `stride` set to 0. The fix will be included in TensorFlow 2.5.0. We will also cherrypick this commit on TensorFlow 2.4.2, TensorFlow 2.3.3, TensorFlow 2.2.3 and TensorFlow 2.1.4, as these are also affected and still in supported range.
<p>Publish Date: 2021-05-14
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-29585>CVE-2021-29585</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://github.com/tensorflow/tensorflow/security/advisories/GHSA-mv78-g7wq-mhp4">https://github.com/tensorflow/tensorflow/security/advisories/GHSA-mv78-g7wq-mhp4</a></p>
<p>Release Date: 2021-05-14</p>
<p>Fix Resolution: org.tensorflow:tensorflow-lite:2.5.0</p>
</p>
</details>
<p></p>
| True | CVE-2021-29585 (High) detected in tensorflowv2.0.2 - ## CVE-2021-29585 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>tensorflowv2.0.2</b></p></summary>
<p>
<p>An Open Source Machine Learning Framework for Everyone</p>
<p>Library home page: <a href=https://github.com/tensorflow/tensorflow.git>https://github.com/tensorflow/tensorflow.git</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 (0)</summary>
<p></p>
<p>
</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>
TensorFlow is an end-to-end open source platform for machine learning. The TFLite computation for size of output after padding, `ComputeOutSize`(https://github.com/tensorflow/tensorflow/blob/0c9692ae7b1671c983569e5d3de5565843d500cf/tensorflow/lite/kernels/padding.h#L43-L55), does not check that the `stride` argument is not 0 before doing the division. Users can craft special models such that `ComputeOutSize` is called with `stride` set to 0. The fix will be included in TensorFlow 2.5.0. We will also cherrypick this commit on TensorFlow 2.4.2, TensorFlow 2.3.3, TensorFlow 2.2.3 and TensorFlow 2.1.4, as these are also affected and still in supported range.
<p>Publish Date: 2021-05-14
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-29585>CVE-2021-29585</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://github.com/tensorflow/tensorflow/security/advisories/GHSA-mv78-g7wq-mhp4">https://github.com/tensorflow/tensorflow/security/advisories/GHSA-mv78-g7wq-mhp4</a></p>
<p>Release Date: 2021-05-14</p>
<p>Fix Resolution: org.tensorflow:tensorflow-lite:2.5.0</p>
</p>
</details>
<p></p>
| non_priority | cve high detected in cve high severity vulnerability vulnerable library an open source machine learning framework for everyone library home page a href found in base branch master vulnerable source files vulnerability details tensorflow is an end to end open source platform for machine learning the tflite computation for size of output after padding computeoutsize does not check that the stride argument is not before doing the division users can craft special models such that computeoutsize is called with stride set to the fix will be included in tensorflow we will also cherrypick this commit on tensorflow tensorflow tensorflow and tensorflow as these are also affected and still in supported range 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 org tensorflow tensorflow lite | 0 |
82,400 | 15,646,555,667 | IssuesEvent | 2021-03-23 01:11:58 | jgeraigery/redux | https://api.github.com/repos/jgeraigery/redux | closed | WS-2019-0063 (High) detected in js-yaml-3.4.5.tgz - autoclosed | security vulnerability | ## WS-2019-0063 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>js-yaml-3.4.5.tgz</b></p></summary>
<p>YAML 1.2 parser and serializer</p>
<p>Library home page: <a href="https://registry.npmjs.org/js-yaml/-/js-yaml-3.4.5.tgz">https://registry.npmjs.org/js-yaml/-/js-yaml-3.4.5.tgz</a></p>
<p>Path to dependency file: redux/package.json</p>
<p>Path to vulnerable library: redux/node_modules/js-yaml/package.json</p>
<p>
Dependency Hierarchy:
- eslint-1.10.3.tgz (Root Library)
- :x: **js-yaml-3.4.5.tgz** (Vulnerable Library)
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
Js-yaml prior to 3.13.1 are vulnerable to Code Injection. The load() function may execute arbitrary code injected through a malicious YAML file.
<p>Publish Date: 2019-04-05
<p>URL: <a href=https://github.com/nodeca/js-yaml/pull/480>WS-2019-0063</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>8.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://www.npmjs.com/advisories/813">https://www.npmjs.com/advisories/813</a></p>
<p>Release Date: 2019-04-05</p>
<p>Fix Resolution: js-yaml - 3.13.1</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"js-yaml","packageVersion":"3.4.5","isTransitiveDependency":true,"dependencyTree":"eslint:1.10.3;js-yaml:3.4.5","isMinimumFixVersionAvailable":true,"minimumFixVersion":"js-yaml - 3.13.1"}],"vulnerabilityIdentifier":"WS-2019-0063","vulnerabilityDetails":"Js-yaml prior to 3.13.1 are vulnerable to Code Injection. The load() function may execute arbitrary code injected through a malicious YAML file.","vulnerabilityUrl":"https://github.com/nodeca/js-yaml/pull/480","cvss2Severity":"high","cvss2Score":"8.0","extraData":{}}</REMEDIATE> --> | True | WS-2019-0063 (High) detected in js-yaml-3.4.5.tgz - autoclosed - ## WS-2019-0063 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>js-yaml-3.4.5.tgz</b></p></summary>
<p>YAML 1.2 parser and serializer</p>
<p>Library home page: <a href="https://registry.npmjs.org/js-yaml/-/js-yaml-3.4.5.tgz">https://registry.npmjs.org/js-yaml/-/js-yaml-3.4.5.tgz</a></p>
<p>Path to dependency file: redux/package.json</p>
<p>Path to vulnerable library: redux/node_modules/js-yaml/package.json</p>
<p>
Dependency Hierarchy:
- eslint-1.10.3.tgz (Root Library)
- :x: **js-yaml-3.4.5.tgz** (Vulnerable Library)
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
Js-yaml prior to 3.13.1 are vulnerable to Code Injection. The load() function may execute arbitrary code injected through a malicious YAML file.
<p>Publish Date: 2019-04-05
<p>URL: <a href=https://github.com/nodeca/js-yaml/pull/480>WS-2019-0063</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>8.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://www.npmjs.com/advisories/813">https://www.npmjs.com/advisories/813</a></p>
<p>Release Date: 2019-04-05</p>
<p>Fix Resolution: js-yaml - 3.13.1</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"js-yaml","packageVersion":"3.4.5","isTransitiveDependency":true,"dependencyTree":"eslint:1.10.3;js-yaml:3.4.5","isMinimumFixVersionAvailable":true,"minimumFixVersion":"js-yaml - 3.13.1"}],"vulnerabilityIdentifier":"WS-2019-0063","vulnerabilityDetails":"Js-yaml prior to 3.13.1 are vulnerable to Code Injection. The load() function may execute arbitrary code injected through a malicious YAML file.","vulnerabilityUrl":"https://github.com/nodeca/js-yaml/pull/480","cvss2Severity":"high","cvss2Score":"8.0","extraData":{}}</REMEDIATE> --> | non_priority | ws high detected in js yaml tgz autoclosed ws high severity vulnerability vulnerable library js yaml tgz yaml parser and serializer library home page a href path to dependency file redux package json path to vulnerable library redux node modules js yaml package json dependency hierarchy eslint tgz root library x js yaml tgz vulnerable library vulnerability details js yaml prior to are vulnerable to code injection the load function may execute arbitrary code injected through a malicious yaml file 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 js yaml isopenpronvulnerability true ispackagebased true isdefaultbranch true packages vulnerabilityidentifier ws vulnerabilitydetails js yaml prior to are vulnerable to code injection the load function may execute arbitrary code injected through a malicious yaml file vulnerabilityurl | 0 |
250,730 | 21,331,832,474 | IssuesEvent | 2022-04-18 09:25:14 | fkk-cz/noire_vehicles | https://api.github.com/repos/fkk-cz/noire_vehicles | closed | 92 Q4 Tipping Problem | performance issue requires testing | The recent 92 Alfa Romeo Q4 put in has a tipping problem if it takes turns at certain speeds without brakes. That’s the only thing happening, everything else seems fine besides little things here and there that’s tolerable. | 1.0 | 92 Q4 Tipping Problem - The recent 92 Alfa Romeo Q4 put in has a tipping problem if it takes turns at certain speeds without brakes. That’s the only thing happening, everything else seems fine besides little things here and there that’s tolerable. | non_priority | tipping problem the recent alfa romeo put in has a tipping problem if it takes turns at certain speeds without brakes that’s the only thing happening everything else seems fine besides little things here and there that’s tolerable | 0 |
242,908 | 26,277,868,431 | IssuesEvent | 2023-01-07 01:22:15 | lnuon/EmpirEqual | https://api.github.com/repos/lnuon/EmpirEqual | opened | CVE-2021-23382 (High) detected in postcss-6.0.22.tgz | security vulnerability | ## CVE-2021-23382 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>postcss-6.0.22.tgz</b></p></summary>
<p>Tool for transforming styles with JS plugins</p>
<p>Library home page: <a href="https://registry.npmjs.org/postcss/-/postcss-6.0.22.tgz">https://registry.npmjs.org/postcss/-/postcss-6.0.22.tgz</a></p>
<p>Path to dependency file: /EmpirEqual/src/frontend/package.json</p>
<p>Path to vulnerable library: /src/frontend/node_modules/react-scripts/node_modules/postcss/package.json,/src/frontend/node_modules/react-scripts/node_modules/postcss/package.json</p>
<p>
Dependency Hierarchy:
- react-scripts-1.1.4.tgz (Root Library)
- autoprefixer-7.1.6.tgz
- :x: **postcss-6.0.22.tgz** (Vulnerable Library)
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
The package postcss before 8.2.13 are vulnerable to Regular Expression Denial of Service (ReDoS) via getAnnotationURL() and loadAnnotation() in lib/previous-map.js. The vulnerable regexes are caused mainly by the sub-pattern \/\*\s* sourceMappingURL=(.*).
<p>Publish Date: 2021-04-26
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2021-23382>CVE-2021-23382</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-23382">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-23382</a></p>
<p>Release Date: 2021-04-26</p>
<p>Fix Resolution (postcss): 7.0.36</p>
<p>Direct dependency fix Resolution (react-scripts): 3.0.0</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | CVE-2021-23382 (High) detected in postcss-6.0.22.tgz - ## CVE-2021-23382 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>postcss-6.0.22.tgz</b></p></summary>
<p>Tool for transforming styles with JS plugins</p>
<p>Library home page: <a href="https://registry.npmjs.org/postcss/-/postcss-6.0.22.tgz">https://registry.npmjs.org/postcss/-/postcss-6.0.22.tgz</a></p>
<p>Path to dependency file: /EmpirEqual/src/frontend/package.json</p>
<p>Path to vulnerable library: /src/frontend/node_modules/react-scripts/node_modules/postcss/package.json,/src/frontend/node_modules/react-scripts/node_modules/postcss/package.json</p>
<p>
Dependency Hierarchy:
- react-scripts-1.1.4.tgz (Root Library)
- autoprefixer-7.1.6.tgz
- :x: **postcss-6.0.22.tgz** (Vulnerable Library)
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
The package postcss before 8.2.13 are vulnerable to Regular Expression Denial of Service (ReDoS) via getAnnotationURL() and loadAnnotation() in lib/previous-map.js. The vulnerable regexes are caused mainly by the sub-pattern \/\*\s* sourceMappingURL=(.*).
<p>Publish Date: 2021-04-26
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2021-23382>CVE-2021-23382</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-23382">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-23382</a></p>
<p>Release Date: 2021-04-26</p>
<p>Fix Resolution (postcss): 7.0.36</p>
<p>Direct dependency fix Resolution (react-scripts): 3.0.0</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_priority | cve high detected in postcss tgz cve high severity vulnerability vulnerable library postcss tgz tool for transforming styles with js plugins library home page a href path to dependency file empirequal src frontend package json path to vulnerable library src frontend node modules react scripts node modules postcss package json src frontend node modules react scripts node modules postcss package json dependency hierarchy react scripts tgz root library autoprefixer tgz x postcss tgz vulnerable library vulnerability details the package postcss before are vulnerable to regular expression denial of service redos via getannotationurl and loadannotation in lib previous map js the vulnerable regexes are caused mainly by the sub pattern s sourcemappingurl 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 postcss direct dependency fix resolution react scripts step up your open source security game with mend | 0 |
271,322 | 20,628,410,745 | IssuesEvent | 2022-03-08 02:23:10 | fga-eps-mds/2021.2-INDICAA | https://api.github.com/repos/fga-eps-mds/2021.2-INDICAA | closed | Vídeo de apresentação do grupo 03. | documentation Grupo 3 | # Tarefas
- [x] Definir roteiro.
- [x] Gravação do vídeo (E edição, caso necessário).
- [x] Postagem do vídeo para que outras pessoas consigam ver (Postar no YouTube, Drive, etc...).
- [x] Postagem de um comentário com o link do vídeo na [issue criada pela professora](https://github.com/fga-eps-mds/Qualifying-Software-Engineers-Undergraduates-in-DevOps/issues/33).
# Critérios de aceitação
- [x] O vídeo deve possuir boa qualidade de som e imagem.
- [x] O vídeo deve seguir o template proposto na [issue criada pela professora](https://github.com/fga-eps-mds/Qualifying-Software-Engineers-Undergraduates-in-DevOps/issues/33).
- [x] Todos os tópicos definidos devem ter sido abordados.
- [x] O projeto deve ter sido explicado sucintamente no vídeo.
- [x] O vídeo deve ter sido postado em plataforma pública.
- [x] O link para o vídeo deve ter sido disponibilizado na [issue criada pela professora](https://github.com/fga-eps-mds/Qualifying-Software-Engineers-Undergraduates-in-DevOps/issues/33).
| 1.0 | Vídeo de apresentação do grupo 03. - # Tarefas
- [x] Definir roteiro.
- [x] Gravação do vídeo (E edição, caso necessário).
- [x] Postagem do vídeo para que outras pessoas consigam ver (Postar no YouTube, Drive, etc...).
- [x] Postagem de um comentário com o link do vídeo na [issue criada pela professora](https://github.com/fga-eps-mds/Qualifying-Software-Engineers-Undergraduates-in-DevOps/issues/33).
# Critérios de aceitação
- [x] O vídeo deve possuir boa qualidade de som e imagem.
- [x] O vídeo deve seguir o template proposto na [issue criada pela professora](https://github.com/fga-eps-mds/Qualifying-Software-Engineers-Undergraduates-in-DevOps/issues/33).
- [x] Todos os tópicos definidos devem ter sido abordados.
- [x] O projeto deve ter sido explicado sucintamente no vídeo.
- [x] O vídeo deve ter sido postado em plataforma pública.
- [x] O link para o vídeo deve ter sido disponibilizado na [issue criada pela professora](https://github.com/fga-eps-mds/Qualifying-Software-Engineers-Undergraduates-in-DevOps/issues/33).
| non_priority | vídeo de apresentação do grupo tarefas definir roteiro gravação do vídeo e edição caso necessário postagem do vídeo para que outras pessoas consigam ver postar no youtube drive etc postagem de um comentário com o link do vídeo na critérios de aceitação o vídeo deve possuir boa qualidade de som e imagem o vídeo deve seguir o template proposto na todos os tópicos definidos devem ter sido abordados o projeto deve ter sido explicado sucintamente no vídeo o vídeo deve ter sido postado em plataforma pública o link para o vídeo deve ter sido disponibilizado na | 0 |
33,821 | 16,135,123,869 | IssuesEvent | 2021-04-29 10:46:50 | KratosMultiphysics/Kratos | https://api.github.com/repos/KratosMultiphysics/Kratos | closed | [Core][External library][Discussion] Replace python depence for mathematical expressions | Discussion Enhancement External library Performance Python | **Description**
Currently, in order to parse the mathematical functions we consider the pybind11 python callback, see: https://github.com/KratosMultiphysics/Kratos/blob/master/kratos/utilities/python_function_callback_utility.h
Looking for another project a way to parse a mathematical function without requiring this dependence (and also improving performance, as the performance of the function evaluation is python performance) I found this MIT library: [exprtk](https://www.partow.net/programming/exprtk/index.html)
I would like to discuss if it could be interesting to replace this python callback for this library.
| True | [Core][External library][Discussion] Replace python depence for mathematical expressions - **Description**
Currently, in order to parse the mathematical functions we consider the pybind11 python callback, see: https://github.com/KratosMultiphysics/Kratos/blob/master/kratos/utilities/python_function_callback_utility.h
Looking for another project a way to parse a mathematical function without requiring this dependence (and also improving performance, as the performance of the function evaluation is python performance) I found this MIT library: [exprtk](https://www.partow.net/programming/exprtk/index.html)
I would like to discuss if it could be interesting to replace this python callback for this library.
| non_priority | replace python depence for mathematical expressions description currently in order to parse the mathematical functions we consider the python callback see looking for another project a way to parse a mathematical function without requiring this dependence and also improving performance as the performance of the function evaluation is python performance i found this mit library i would like to discuss if it could be interesting to replace this python callback for this library | 0 |
80,031 | 7,737,094,355 | IssuesEvent | 2018-05-28 06:52:30 | celery/celery | https://api.github.com/repos/celery/celery | closed | Tasks with expires fail with AttributeError("'str' object has no attribute 'isoformat'",) | Issue Type: Bug Status: Has Testcase ✔ | ## Checklist
- [x] I have included the output of ``celery -A proj report`` in the issue.
(if you are not able to do this, then at least specify the Celery
version affected).
```
software -> celery:4.0.2 (latentcall) kombu:4.0.2 py:3.6.1
billiard:3.5.0.2 py-amqp:2.1.4
platform -> system:Darwin arch:64bit imp:CPython
loader -> celery.loaders.default.Loader
settings -> transport:amqp results:disabled
```
## Steps to reproduce
1. Create a task that retries via raise `self.retry()`
1. Call the task with `send_task` and set `expires`
## Expected behavior
The task should retry until the expires time is hit or the max_retries value is hit
## Actual behavior
```
Traceback (most recent call last):
File "/usr/lib/python3.6/site-packages/celery/app/task.py", line 684, in retry
S.apply_async()
File "/usr/lib/python3.6/site-packages/celery/canvas.py", line 221, in apply_async
return _apply(args, kwargs, **options)
File "/usr/lib/python3.6/site-packages/celery/app/task.py", line 535, in apply_async
**options
File "/usr/lib/python3.6/site-packages/celery/app/base.py", line 729, in send_task
root_id, parent_id, shadow, chain,
File "/usr/lib/python3.6/site-packages/celery/app/amqp.py", line 334, in as_task_v2
expires = expires and expires.isoformat()
AttributeError: 'str' object has no attribute 'isoformat'
``` | 1.0 | Tasks with expires fail with AttributeError("'str' object has no attribute 'isoformat'",) - ## Checklist
- [x] I have included the output of ``celery -A proj report`` in the issue.
(if you are not able to do this, then at least specify the Celery
version affected).
```
software -> celery:4.0.2 (latentcall) kombu:4.0.2 py:3.6.1
billiard:3.5.0.2 py-amqp:2.1.4
platform -> system:Darwin arch:64bit imp:CPython
loader -> celery.loaders.default.Loader
settings -> transport:amqp results:disabled
```
## Steps to reproduce
1. Create a task that retries via raise `self.retry()`
1. Call the task with `send_task` and set `expires`
## Expected behavior
The task should retry until the expires time is hit or the max_retries value is hit
## Actual behavior
```
Traceback (most recent call last):
File "/usr/lib/python3.6/site-packages/celery/app/task.py", line 684, in retry
S.apply_async()
File "/usr/lib/python3.6/site-packages/celery/canvas.py", line 221, in apply_async
return _apply(args, kwargs, **options)
File "/usr/lib/python3.6/site-packages/celery/app/task.py", line 535, in apply_async
**options
File "/usr/lib/python3.6/site-packages/celery/app/base.py", line 729, in send_task
root_id, parent_id, shadow, chain,
File "/usr/lib/python3.6/site-packages/celery/app/amqp.py", line 334, in as_task_v2
expires = expires and expires.isoformat()
AttributeError: 'str' object has no attribute 'isoformat'
``` | non_priority | tasks with expires fail with attributeerror str object has no attribute isoformat checklist i have included the output of celery a proj report in the issue if you are not able to do this then at least specify the celery version affected software celery latentcall kombu py billiard py amqp platform system darwin arch imp cpython loader celery loaders default loader settings transport amqp results disabled steps to reproduce create a task that retries via raise self retry call the task with send task and set expires expected behavior the task should retry until the expires time is hit or the max retries value is hit actual behavior traceback most recent call last file usr lib site packages celery app task py line in retry s apply async file usr lib site packages celery canvas py line in apply async return apply args kwargs options file usr lib site packages celery app task py line in apply async options file usr lib site packages celery app base py line in send task root id parent id shadow chain file usr lib site packages celery app amqp py line in as task expires expires and expires isoformat attributeerror str object has no attribute isoformat | 0 |
295,822 | 25,507,483,757 | IssuesEvent | 2022-11-28 10:32:16 | Sexy-Sisters/TOJ-server-v2 | https://api.github.com/repos/Sexy-Sisters/TOJ-server-v2 | closed | TDD for User Domain | ✅ TEST ⚙️SET | ## 📑 describe
> 유저 도메인에 관한 TDD
## ✅ Things to do
- [x] test setting
- [x] sign-up test
- [x] sign-in test
- [x] update user information test
- [x] find the current user profile
- [x] find the user profile
## 🙋🏿What I want to say
> nothing
| 1.0 | TDD for User Domain - ## 📑 describe
> 유저 도메인에 관한 TDD
## ✅ Things to do
- [x] test setting
- [x] sign-up test
- [x] sign-in test
- [x] update user information test
- [x] find the current user profile
- [x] find the user profile
## 🙋🏿What I want to say
> nothing
| non_priority | tdd for user domain 📑 describe 유저 도메인에 관한 tdd ✅ things to do test setting sign up test sign in test update user information test find the current user profile find the user profile 🙋🏿what i want to say nothing | 0 |
1,876 | 11,014,648,693 | IssuesEvent | 2019-12-04 23:18:06 | dfernandezm/moneycol | https://api.github.com/repos/dfernandezm/moneycol | closed | Terraform automation | automation myiac | - [ ] Setup buckets in GCP object storage for terraform state through myiac (gcloud client?)
- [ ] Backup terraform state file in GCP cloud storage
- [ ] Myiac: Deploy the backend skeleton with GraphQL endpoint/status endpoint (it must have been Dockerized first) | 1.0 | Terraform automation - - [ ] Setup buckets in GCP object storage for terraform state through myiac (gcloud client?)
- [ ] Backup terraform state file in GCP cloud storage
- [ ] Myiac: Deploy the backend skeleton with GraphQL endpoint/status endpoint (it must have been Dockerized first) | non_priority | terraform automation setup buckets in gcp object storage for terraform state through myiac gcloud client backup terraform state file in gcp cloud storage myiac deploy the backend skeleton with graphql endpoint status endpoint it must have been dockerized first | 0 |
52,557 | 6,260,920,353 | IssuesEvent | 2017-07-14 22:02:32 | geoffhumphrey/brewcompetitiononlineentry | https://api.github.com/repos/geoffhumphrey/brewcompetitiononlineentry | closed | 2.1.9: Setup Breaks on Input of Admin User Info | bug confirmed in latest master commit v2.1.10 | White screen with the following message appears when going through setup:
`
You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'brewerStaff ) ...
`
A fix is available in the latest commit and [here](https://github.com/geoffhumphrey/brewcompetitiononlineentry/commit/0c96d50f9b726acae24e8b2b529e96ac20d53b3c).
Basically a comma is missing on line 281 in the /includes/process/process_brewer.inc.php file. DOH!
| 1.0 | 2.1.9: Setup Breaks on Input of Admin User Info - White screen with the following message appears when going through setup:
`
You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'brewerStaff ) ...
`
A fix is available in the latest commit and [here](https://github.com/geoffhumphrey/brewcompetitiononlineentry/commit/0c96d50f9b726acae24e8b2b529e96ac20d53b3c).
Basically a comma is missing on line 281 in the /includes/process/process_brewer.inc.php file. DOH!
| non_priority | setup breaks on input of admin user info white screen with the following message appears when going through setup you have an error in your sql syntax check the manual that corresponds to your mysql server version for the right syntax to use near brewerstaff a fix is available in the latest commit and basically a comma is missing on line in the includes process process brewer inc php file doh | 0 |
10,424 | 3,109,769,772 | IssuesEvent | 2015-09-02 00:09:32 | OpenMS/OpenMS | https://api.github.com/repos/OpenMS/OpenMS | opened | failed tests with boost 1.58 | (Unit) Tests contrib | I get a couple of failed tests when compiling against boost 1.58
```
99% tests passed, 5 tests failed out of 1735
Total Test time (real) = 194.53 sec
The following tests FAILED:
326 - SvmTheoreticalSpectrumGenerator_test (Failed)
328 - SvmTheoreticalSpectrumGeneratorSet_test (Failed)
490 - IonizationSimulation_test (Failed)
491 - MSSim_test (Failed)
494 - RawTandemMSSignalSimulation_test (Failed)
Errors while running CTest
```
This may have something to do with the random number generator in boost, but I am not sure about this
```
326: checking void simulate(RichPeakSpectrum &spectrum, const AASequence &peptide, boost::random::mt19937_64&rng, Size precursor_charge) ... SVM model file loaded: testModel_11__1_class.svm
326: SVM model file loaded: testModel_11__1_reg.svm
326:
326: + line 103: TEST_EQUAL(exp.size(),1): got 1, expected 1
326: - line 106: TEST_EQUAL(spec.size(),exp[0].size()): got 8, expected 7
326: + line 111: TEST_REAL_SIMILAR(spec[i].getPosition()[0],(exp[0][i]).getPosition()[0]): got 147.112804913371, expected 147.112804913371
326: + line 112: TEST_REAL_SIMILAR(spec[i].getIntensity(),(exp[0][i]).getIntensity()): got 0.235752, expected 0.235752
326: + line 111: TEST_REAL_SIMILAR(spec[i].getPosition()[0],(exp[0][i]).getPosition()[0]): got 204.134269009071, expected 204.134269009071
326: + line 112: TEST_REAL_SIMILAR(spec[i].getIntensity(),(exp[0][i]).getIntensity()): got 0.466184, expected 0.466184
326: - line 111: TEST_REAL_SIMILAR(spec[i].getPosition()[0],(exp[0][i]).getPosition()[0]): got 216.134269009071, expected 303.202683296171 (absolute: 87.0684142871 [1e-05], relative: 1.40284409634016 [1.00001], message: "ratio of numbers is large"
326: - line 112: TEST_REAL_SIMILAR(spec[i].getIntensity(),(exp[0][i]).getIntensity()): got 0.490215, expected 0.734385 (absolute: 0.24417 [1e-05], relative: 1.49809 [1.00001], message: "ratio of numbers is large"
326: - line 111: TEST_REAL_SIMILAR(spec[i].getPosition()[0],(exp[0][i]).getPosition()[0]): got 303.202683296171, expected 333.184490732371 (absolute: 29.9818074362 [1e-05], relative: 1.09888371405643 [1.00001], message: "ratio of numbers is large"
326: - line 112: TEST_REAL_SIMILAR(spec[i].getIntensity(),(exp[0][i]).getIntensity()): got 0.734385, expected 0.957302 (absolute: 0.222917 [1e-05], relative: 1.30354 [1.00001], message: "ratio of numbers is large"
326: - line 111: TEST_REAL_SIMILAR(spec[i].getPosition()[0],(exp[0][i]).getPosition()[0]): got 333.184490732371, expected 431.261261551371 (absolute: 98.076770819 [1e-05], relative: 1.29436175316389 [1.00001], message: "ratio of numbers is large"
326: - line 112: TEST_REAL_SIMILAR(spec[i].getIntensity(),(exp[0][i]).getIntensity()): got 0.0317678, expected 0.707035 (absolute: 0.675267 [1e-05], relative: 22.2564 [1.00001], message: "ratio of numbers is large"
326: - line 111: TEST_REAL_SIMILAR(spec[i].getPosition()[0],(exp[0][i]).getPosition()[0]): got 431.261261551371, expected 518.293290710871 (absolute: 87.0320291595 [1e-05], relative: 1.20180813098404 [1.00001], message: "ratio of numbers is large"
326: - line 112: TEST_REAL_SIMILAR(spec[i].getIntensity(),(exp[0][i]).getIntensity()): got 0.707035, expected 0.584489 (absolute: 0.122546 [1e-05], relative: 1.20966 [1.00001], message: "ratio of numbers is large"
326: - line 111: TEST_REAL_SIMILAR(spec[i].getPosition()[0],(exp[0][i]).getPosition()[0]): got 518.293290710871, expected 665.361704997971 (absolute: 147.0684142871 [1e-05], relative: 1.28375519599219 [1.00001], message: "ratio of numbers is large"
326: - line 112: TEST_REAL_SIMILAR(spec[i].getIntensity(),(exp[0][i]).getIntensity()): got 0.584489, expected 0.631471 (absolute: 0.0469818 [1e-05], relative: 1.08038 [1.00001], message: "ratio of numbers is large"
326: : failed
326:
```
all works fine when compiling against boost 1.52 | 1.0 | failed tests with boost 1.58 - I get a couple of failed tests when compiling against boost 1.58
```
99% tests passed, 5 tests failed out of 1735
Total Test time (real) = 194.53 sec
The following tests FAILED:
326 - SvmTheoreticalSpectrumGenerator_test (Failed)
328 - SvmTheoreticalSpectrumGeneratorSet_test (Failed)
490 - IonizationSimulation_test (Failed)
491 - MSSim_test (Failed)
494 - RawTandemMSSignalSimulation_test (Failed)
Errors while running CTest
```
This may have something to do with the random number generator in boost, but I am not sure about this
```
326: checking void simulate(RichPeakSpectrum &spectrum, const AASequence &peptide, boost::random::mt19937_64&rng, Size precursor_charge) ... SVM model file loaded: testModel_11__1_class.svm
326: SVM model file loaded: testModel_11__1_reg.svm
326:
326: + line 103: TEST_EQUAL(exp.size(),1): got 1, expected 1
326: - line 106: TEST_EQUAL(spec.size(),exp[0].size()): got 8, expected 7
326: + line 111: TEST_REAL_SIMILAR(spec[i].getPosition()[0],(exp[0][i]).getPosition()[0]): got 147.112804913371, expected 147.112804913371
326: + line 112: TEST_REAL_SIMILAR(spec[i].getIntensity(),(exp[0][i]).getIntensity()): got 0.235752, expected 0.235752
326: + line 111: TEST_REAL_SIMILAR(spec[i].getPosition()[0],(exp[0][i]).getPosition()[0]): got 204.134269009071, expected 204.134269009071
326: + line 112: TEST_REAL_SIMILAR(spec[i].getIntensity(),(exp[0][i]).getIntensity()): got 0.466184, expected 0.466184
326: - line 111: TEST_REAL_SIMILAR(spec[i].getPosition()[0],(exp[0][i]).getPosition()[0]): got 216.134269009071, expected 303.202683296171 (absolute: 87.0684142871 [1e-05], relative: 1.40284409634016 [1.00001], message: "ratio of numbers is large"
326: - line 112: TEST_REAL_SIMILAR(spec[i].getIntensity(),(exp[0][i]).getIntensity()): got 0.490215, expected 0.734385 (absolute: 0.24417 [1e-05], relative: 1.49809 [1.00001], message: "ratio of numbers is large"
326: - line 111: TEST_REAL_SIMILAR(spec[i].getPosition()[0],(exp[0][i]).getPosition()[0]): got 303.202683296171, expected 333.184490732371 (absolute: 29.9818074362 [1e-05], relative: 1.09888371405643 [1.00001], message: "ratio of numbers is large"
326: - line 112: TEST_REAL_SIMILAR(spec[i].getIntensity(),(exp[0][i]).getIntensity()): got 0.734385, expected 0.957302 (absolute: 0.222917 [1e-05], relative: 1.30354 [1.00001], message: "ratio of numbers is large"
326: - line 111: TEST_REAL_SIMILAR(spec[i].getPosition()[0],(exp[0][i]).getPosition()[0]): got 333.184490732371, expected 431.261261551371 (absolute: 98.076770819 [1e-05], relative: 1.29436175316389 [1.00001], message: "ratio of numbers is large"
326: - line 112: TEST_REAL_SIMILAR(spec[i].getIntensity(),(exp[0][i]).getIntensity()): got 0.0317678, expected 0.707035 (absolute: 0.675267 [1e-05], relative: 22.2564 [1.00001], message: "ratio of numbers is large"
326: - line 111: TEST_REAL_SIMILAR(spec[i].getPosition()[0],(exp[0][i]).getPosition()[0]): got 431.261261551371, expected 518.293290710871 (absolute: 87.0320291595 [1e-05], relative: 1.20180813098404 [1.00001], message: "ratio of numbers is large"
326: - line 112: TEST_REAL_SIMILAR(spec[i].getIntensity(),(exp[0][i]).getIntensity()): got 0.707035, expected 0.584489 (absolute: 0.122546 [1e-05], relative: 1.20966 [1.00001], message: "ratio of numbers is large"
326: - line 111: TEST_REAL_SIMILAR(spec[i].getPosition()[0],(exp[0][i]).getPosition()[0]): got 518.293290710871, expected 665.361704997971 (absolute: 147.0684142871 [1e-05], relative: 1.28375519599219 [1.00001], message: "ratio of numbers is large"
326: - line 112: TEST_REAL_SIMILAR(spec[i].getIntensity(),(exp[0][i]).getIntensity()): got 0.584489, expected 0.631471 (absolute: 0.0469818 [1e-05], relative: 1.08038 [1.00001], message: "ratio of numbers is large"
326: : failed
326:
```
all works fine when compiling against boost 1.52 | non_priority | failed tests with boost i get a couple of failed tests when compiling against boost tests passed tests failed out of total test time real sec the following tests failed svmtheoreticalspectrumgenerator test failed svmtheoreticalspectrumgeneratorset test failed ionizationsimulation test failed mssim test failed rawtandemmssignalsimulation test failed errors while running ctest this may have something to do with the random number generator in boost but i am not sure about this checking void simulate richpeakspectrum spectrum const aasequence peptide boost random rng size precursor charge svm model file loaded testmodel class svm svm model file loaded testmodel reg svm line test equal exp size got expected line test equal spec size exp size got expected line test real similar spec getposition exp getposition got expected line test real similar spec getintensity exp getintensity got expected line test real similar spec getposition exp getposition got expected line test real similar spec getintensity exp getintensity got expected line test real similar spec getposition exp getposition got expected absolute relative message ratio of numbers is large line test real similar spec getintensity exp getintensity got expected absolute relative message ratio of numbers is large line test real similar spec getposition exp getposition got expected absolute relative message ratio of numbers is large line test real similar spec getintensity exp getintensity got expected absolute relative message ratio of numbers is large line test real similar spec getposition exp getposition got expected absolute relative message ratio of numbers is large line test real similar spec getintensity exp getintensity got expected absolute relative message ratio of numbers is large line test real similar spec getposition exp getposition got expected absolute relative message ratio of numbers is large line test real similar spec getintensity exp getintensity got expected absolute relative message ratio of numbers is large line test real similar spec getposition exp getposition got expected absolute relative message ratio of numbers is large line test real similar spec getintensity exp getintensity got expected absolute relative message ratio of numbers is large failed all works fine when compiling against boost | 0 |
131,763 | 18,249,411,320 | IssuesEvent | 2021-10-02 00:58:37 | ghc-dev/Larry-Mcmahon | https://api.github.com/repos/ghc-dev/Larry-Mcmahon | closed | CVE-2015-8315 (High) detected in ms-0.7.0.tgz - autoclosed | security vulnerability | ## CVE-2015-8315 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>ms-0.7.0.tgz</b></p></summary>
<p>Tiny ms conversion utility</p>
<p>Library home page: <a href="https://registry.npmjs.org/ms/-/ms-0.7.0.tgz">https://registry.npmjs.org/ms/-/ms-0.7.0.tgz</a></p>
<p>Path to dependency file: Larry-Mcmahon/package.json</p>
<p>Path to vulnerable library: Larry-Mcmahon/node_modules/ms/package.json</p>
<p>
Dependency Hierarchy:
- send-0.11.1.tgz (Root Library)
- :x: **ms-0.7.0.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/ghc-dev/Larry-Mcmahon/commit/7c12062c8785c9911d7d2c69ba23b628b7521acb">7c12062c8785c9911d7d2c69ba23b628b7521acb</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>
The ms package before 0.7.1 for Node.js allows attackers to cause a denial of service (CPU consumption) via a long version string, aka a "regular expression denial of service (ReDoS)."
<p>Publish Date: 2017-01-23
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2015-8315>CVE-2015-8315</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://nvd.nist.gov/vuln/detail/CVE-2015-8315">https://nvd.nist.gov/vuln/detail/CVE-2015-8315</a></p>
<p>Release Date: 2017-01-23</p>
<p>Fix Resolution: 0.7.1</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"ms","packageVersion":"0.7.0","packageFilePaths":["/package.json"],"isTransitiveDependency":true,"dependencyTree":"send:0.11.1;ms:0.7.0","isMinimumFixVersionAvailable":true,"minimumFixVersion":"0.7.1"}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2015-8315","vulnerabilityDetails":"The ms package before 0.7.1 for Node.js allows attackers to cause a denial of service (CPU consumption) via a long version string, aka a \"regular expression denial of service (ReDoS).\"","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2015-8315","cvss3Severity":"high","cvss3Score":"7.5","cvss3Metrics":{"A":"High","AC":"Low","PR":"None","S":"Unchanged","C":"None","UI":"None","AV":"Network","I":"None"},"extraData":{}}</REMEDIATE> --> | True | CVE-2015-8315 (High) detected in ms-0.7.0.tgz - autoclosed - ## CVE-2015-8315 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>ms-0.7.0.tgz</b></p></summary>
<p>Tiny ms conversion utility</p>
<p>Library home page: <a href="https://registry.npmjs.org/ms/-/ms-0.7.0.tgz">https://registry.npmjs.org/ms/-/ms-0.7.0.tgz</a></p>
<p>Path to dependency file: Larry-Mcmahon/package.json</p>
<p>Path to vulnerable library: Larry-Mcmahon/node_modules/ms/package.json</p>
<p>
Dependency Hierarchy:
- send-0.11.1.tgz (Root Library)
- :x: **ms-0.7.0.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/ghc-dev/Larry-Mcmahon/commit/7c12062c8785c9911d7d2c69ba23b628b7521acb">7c12062c8785c9911d7d2c69ba23b628b7521acb</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>
The ms package before 0.7.1 for Node.js allows attackers to cause a denial of service (CPU consumption) via a long version string, aka a "regular expression denial of service (ReDoS)."
<p>Publish Date: 2017-01-23
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2015-8315>CVE-2015-8315</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://nvd.nist.gov/vuln/detail/CVE-2015-8315">https://nvd.nist.gov/vuln/detail/CVE-2015-8315</a></p>
<p>Release Date: 2017-01-23</p>
<p>Fix Resolution: 0.7.1</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"ms","packageVersion":"0.7.0","packageFilePaths":["/package.json"],"isTransitiveDependency":true,"dependencyTree":"send:0.11.1;ms:0.7.0","isMinimumFixVersionAvailable":true,"minimumFixVersion":"0.7.1"}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2015-8315","vulnerabilityDetails":"The ms package before 0.7.1 for Node.js allows attackers to cause a denial of service (CPU consumption) via a long version string, aka a \"regular expression denial of service (ReDoS).\"","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2015-8315","cvss3Severity":"high","cvss3Score":"7.5","cvss3Metrics":{"A":"High","AC":"Low","PR":"None","S":"Unchanged","C":"None","UI":"None","AV":"Network","I":"None"},"extraData":{}}</REMEDIATE> --> | non_priority | cve high detected in ms tgz autoclosed cve high severity vulnerability vulnerable library ms tgz tiny ms conversion utility library home page a href path to dependency file larry mcmahon package json path to vulnerable library larry mcmahon node modules ms package json dependency hierarchy send tgz root library x ms tgz vulnerable library found in head commit a href found in base branch master vulnerability details the ms package before for node js allows attackers to cause a denial of service cpu consumption via a long version string aka a regular expression denial of service redos 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 isopenpronvulnerability true ispackagebased true isdefaultbranch true packages istransitivedependency true dependencytree send ms isminimumfixversionavailable true minimumfixversion basebranches vulnerabilityidentifier cve vulnerabilitydetails the ms package before for node js allows attackers to cause a denial of service cpu consumption via a long version string aka a regular expression denial of service redos vulnerabilityurl | 0 |
116,268 | 14,939,871,164 | IssuesEvent | 2021-01-25 17:29:59 | DavidHieselmayr/Gaias-resurrection | https://api.github.com/repos/DavidHieselmayr/Gaias-resurrection | closed | Planung Wasserinsel | design planung sprint2 | - [x] Inselaufbau
- [x] Boss Gegner #31
- [x] Fähigkeiten
- [x] Arenaumgebung
- [x] Kampfmechaniken
- [x] Kampfablauf
- [x] Lebewesen
- [ ] Design @JohnLimHTL | 1.0 | Planung Wasserinsel - - [x] Inselaufbau
- [x] Boss Gegner #31
- [x] Fähigkeiten
- [x] Arenaumgebung
- [x] Kampfmechaniken
- [x] Kampfablauf
- [x] Lebewesen
- [ ] Design @JohnLimHTL | non_priority | planung wasserinsel inselaufbau boss gegner fähigkeiten arenaumgebung kampfmechaniken kampfablauf lebewesen design johnlimhtl | 0 |
94,423 | 15,962,373,081 | IssuesEvent | 2021-04-16 01:10:28 | xinYG/bootstrap-timepicker | https://api.github.com/repos/xinYG/bootstrap-timepicker | reopened | CVE-2018-16487 (Medium) detected in lodash-4.17.4.js | security vulnerability | ## CVE-2018-16487 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>lodash-4.17.4.js</b></p></summary>
<p>A utility library delivering consistency, customization, performance, & extras.</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/lodash.js/4.17.4/lodash.js">https://cdnjs.cloudflare.com/ajax/libs/lodash.js/4.17.4/lodash.js</a></p>
<p>Path to vulnerable library: bootstrap-timepicker/node_modules/bower/lib/node_modules/lodash/lodash.js</p>
<p>
Dependency Hierarchy:
- :x: **lodash-4.17.4.js** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/xinYG/bootstrap-timepicker/commit/c92f0918f68b35842a2bf5ae212e5d75e70546e5">c92f0918f68b35842a2bf5ae212e5d75e70546e5</a></p>
<p>Found in base branch: <b>gh-pages</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 prototype pollution vulnerability was found in lodash <4.17.11 where the functions merge, mergeWith, and defaultsDeep can be tricked into adding or modifying properties of Object.prototype.
<p>Publish Date: 2019-02-01
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-16487>CVE-2018-16487</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.6</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: 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://bugzilla.redhat.com/show_bug.cgi?id=CVE-2018-16487">https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2018-16487</a></p>
<p>Release Date: 2019-02-01</p>
<p>Fix Resolution: 4.17.11</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":false,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"JavaScript","packageName":"lodash.js","packageVersion":"4.17.4","isTransitiveDependency":false,"dependencyTree":"lodash.js:4.17.4","isMinimumFixVersionAvailable":true,"minimumFixVersion":"4.17.11"}],"vulnerabilityIdentifier":"CVE-2018-16487","vulnerabilityDetails":"A prototype pollution vulnerability was found in lodash \u003c4.17.11 where the functions merge, mergeWith, and defaultsDeep can be tricked into adding or modifying properties of Object.prototype.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-16487","cvss3Severity":"medium","cvss3Score":"5.6","cvss3Metrics":{"A":"Low","AC":"High","PR":"None","S":"Unchanged","C":"Low","UI":"None","AV":"Network","I":"Low"},"extraData":{}}</REMEDIATE> --> | True | CVE-2018-16487 (Medium) detected in lodash-4.17.4.js - ## CVE-2018-16487 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>lodash-4.17.4.js</b></p></summary>
<p>A utility library delivering consistency, customization, performance, & extras.</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/lodash.js/4.17.4/lodash.js">https://cdnjs.cloudflare.com/ajax/libs/lodash.js/4.17.4/lodash.js</a></p>
<p>Path to vulnerable library: bootstrap-timepicker/node_modules/bower/lib/node_modules/lodash/lodash.js</p>
<p>
Dependency Hierarchy:
- :x: **lodash-4.17.4.js** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/xinYG/bootstrap-timepicker/commit/c92f0918f68b35842a2bf5ae212e5d75e70546e5">c92f0918f68b35842a2bf5ae212e5d75e70546e5</a></p>
<p>Found in base branch: <b>gh-pages</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 prototype pollution vulnerability was found in lodash <4.17.11 where the functions merge, mergeWith, and defaultsDeep can be tricked into adding or modifying properties of Object.prototype.
<p>Publish Date: 2019-02-01
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-16487>CVE-2018-16487</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.6</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: 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://bugzilla.redhat.com/show_bug.cgi?id=CVE-2018-16487">https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2018-16487</a></p>
<p>Release Date: 2019-02-01</p>
<p>Fix Resolution: 4.17.11</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":false,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"JavaScript","packageName":"lodash.js","packageVersion":"4.17.4","isTransitiveDependency":false,"dependencyTree":"lodash.js:4.17.4","isMinimumFixVersionAvailable":true,"minimumFixVersion":"4.17.11"}],"vulnerabilityIdentifier":"CVE-2018-16487","vulnerabilityDetails":"A prototype pollution vulnerability was found in lodash \u003c4.17.11 where the functions merge, mergeWith, and defaultsDeep can be tricked into adding or modifying properties of Object.prototype.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-16487","cvss3Severity":"medium","cvss3Score":"5.6","cvss3Metrics":{"A":"Low","AC":"High","PR":"None","S":"Unchanged","C":"Low","UI":"None","AV":"Network","I":"Low"},"extraData":{}}</REMEDIATE> --> | non_priority | cve medium detected in lodash js cve medium severity vulnerability vulnerable library lodash js a utility library delivering consistency customization performance extras library home page a href path to vulnerable library bootstrap timepicker node modules bower lib node modules lodash lodash js dependency hierarchy x lodash js vulnerable library found in head commit a href found in base branch gh pages vulnerability details a prototype pollution vulnerability was found in lodash where the functions merge mergewith and defaultsdeep can be tricked into adding or modifying properties of object prototype 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 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 isopenpronvulnerability false ispackagebased true isdefaultbranch true packages vulnerabilityidentifier cve vulnerabilitydetails a prototype pollution vulnerability was found in lodash where the functions merge mergewith and defaultsdeep can be tricked into adding or modifying properties of object prototype vulnerabilityurl | 0 |
116,032 | 11,893,943,996 | IssuesEvent | 2020-03-29 13:49:57 | Onther-Tech/docs.tokamak.network | https://api.github.com/repos/Onther-Tech/docs.tokamak.network | opened | 다국어지원 관련 오류 | documentation invalid | 
- 한국어를 눌러도 우측 상단의 "English"가 "한국어"로 바뀌지 않음. 한국어 모드에서는 우측 상단이 "한국어"로 바뀌어야 함.
- 한국어로 전환된 상태에서 "Getting Started"는 "빠르게 시작하기"로 수정 필요
- 한국어로 전환된 상태에서 "기초","고급","Getting Started"를 누르면 영문 페이지로 이동함 --> 국문 페이지로 이동하도록 수정 필요 | 1.0 | 다국어지원 관련 오류 - 
- 한국어를 눌러도 우측 상단의 "English"가 "한국어"로 바뀌지 않음. 한국어 모드에서는 우측 상단이 "한국어"로 바뀌어야 함.
- 한국어로 전환된 상태에서 "Getting Started"는 "빠르게 시작하기"로 수정 필요
- 한국어로 전환된 상태에서 "기초","고급","Getting Started"를 누르면 영문 페이지로 이동함 --> 국문 페이지로 이동하도록 수정 필요 | non_priority | 다국어지원 관련 오류 한국어를 눌러도 우측 상단의 english 가 한국어 로 바뀌지 않음 한국어 모드에서는 우측 상단이 한국어 로 바뀌어야 함 한국어로 전환된 상태에서 getting started 는 빠르게 시작하기 로 수정 필요 한국어로 전환된 상태에서 기초 고급 getting started 를 누르면 영문 페이지로 이동함 국문 페이지로 이동하도록 수정 필요 | 0 |
26,034 | 4,552,662,511 | IssuesEvent | 2016-09-13 00:04:31 | bridgedotnet/Bridge | https://api.github.com/repos/bridgedotnet/Bridge | opened | Add ICollection<T>.CopyTo() | defect | [MSDN ICollection<T>.CopyTo Method (T[], Int32)](https://msdn.microsoft.com/en-us/library/0efx51xw(v=vs.110).aspx)
> Copies the elements of the ICollection<T> to an Array, starting at a particular Array index.
```cs
void CopyTo(
T[] array,
int arrayIndex
)
```
Related #1548, #1810
https://github.com/bridgedotnet/Bridge/issues/1025#issuecomment-246532630
| 1.0 | Add ICollection<T>.CopyTo() - [MSDN ICollection<T>.CopyTo Method (T[], Int32)](https://msdn.microsoft.com/en-us/library/0efx51xw(v=vs.110).aspx)
> Copies the elements of the ICollection<T> to an Array, starting at a particular Array index.
```cs
void CopyTo(
T[] array,
int arrayIndex
)
```
Related #1548, #1810
https://github.com/bridgedotnet/Bridge/issues/1025#issuecomment-246532630
| non_priority | add icollection copyto copies the elements of the icollection to an array starting at a particular array index cs void copyto t array int arrayindex related | 0 |
38,637 | 12,561,338,184 | IssuesEvent | 2020-06-08 01:10:23 | kenferrara/atlasdb | https://api.github.com/repos/kenferrara/atlasdb | opened | CVE-2020-13692 (Medium) detected in postgresql-42.2.1.jar | security vulnerability | ## CVE-2020-13692 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>postgresql-42.2.1.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: /tmp/ws-scm/atlasdb/atlasdb-console-distribution/build.gradle</p>
<p>Path to vulnerable library: le/caches/modules-2/files-2.1/org.postgresql/postgresql/42.2.1/b7f61848ac43ae9fa6e38935bfd75628b7fc9086/postgresql-42.2.1.jar,le/caches/modules-2/files-2.1/org.postgresql/postgresql/42.2.1/b7f61848ac43ae9fa6e38935bfd75628b7fc9086/postgresql-42.2.1.jar</p>
<p>
Dependency Hierarchy:
- :x: **postgresql-42.2.1.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>
PostgreSQL JDBC Driver (aka PgJDBC) before 42.2.13 allows XXE.
<p>Publish Date: 2020-06-04
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-13692>CVE-2020-13692</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.0</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: N/A
- Attack Complexity: N/A
- Privileges Required: N/A
- User Interaction: N/A
- Scope: N/A
- Impact Metrics:
- Confidentiality Impact: N/A
- Integrity Impact: N/A
- Availability Impact: N/A
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://jdbc.postgresql.org/documentation/changelog.html#version_42.2.13">https://jdbc.postgresql.org/documentation/changelog.html#version_42.2.13</a></p>
<p>Release Date: 2020-06-04</p>
<p>Fix Resolution: org.postgresql:postgresql:42.2.13</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.postgresql","packageName":"postgresql","packageVersion":"42.2.1","isTransitiveDependency":false,"dependencyTree":"org.postgresql:postgresql:42.2.1","isMinimumFixVersionAvailable":true,"minimumFixVersion":"org.postgresql:postgresql:42.2.13"}],"vulnerabilityIdentifier":"CVE-2020-13692","vulnerabilityDetails":"PostgreSQL JDBC Driver (aka PgJDBC) before 42.2.13 allows XXE.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-13692","cvss3Severity":"medium","cvss3Score":"5.0","cvss3Metrics":{"A":"N/A","AC":"N/A","PR":"N/A","S":"N/A","C":"N/A","UI":"N/A","AV":"N/A","I":"N/A"},"extraData":{}}</REMEDIATE> --> | True | CVE-2020-13692 (Medium) detected in postgresql-42.2.1.jar - ## CVE-2020-13692 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>postgresql-42.2.1.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: /tmp/ws-scm/atlasdb/atlasdb-console-distribution/build.gradle</p>
<p>Path to vulnerable library: le/caches/modules-2/files-2.1/org.postgresql/postgresql/42.2.1/b7f61848ac43ae9fa6e38935bfd75628b7fc9086/postgresql-42.2.1.jar,le/caches/modules-2/files-2.1/org.postgresql/postgresql/42.2.1/b7f61848ac43ae9fa6e38935bfd75628b7fc9086/postgresql-42.2.1.jar</p>
<p>
Dependency Hierarchy:
- :x: **postgresql-42.2.1.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>
PostgreSQL JDBC Driver (aka PgJDBC) before 42.2.13 allows XXE.
<p>Publish Date: 2020-06-04
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-13692>CVE-2020-13692</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.0</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: N/A
- Attack Complexity: N/A
- Privileges Required: N/A
- User Interaction: N/A
- Scope: N/A
- Impact Metrics:
- Confidentiality Impact: N/A
- Integrity Impact: N/A
- Availability Impact: N/A
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://jdbc.postgresql.org/documentation/changelog.html#version_42.2.13">https://jdbc.postgresql.org/documentation/changelog.html#version_42.2.13</a></p>
<p>Release Date: 2020-06-04</p>
<p>Fix Resolution: org.postgresql:postgresql:42.2.13</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.postgresql","packageName":"postgresql","packageVersion":"42.2.1","isTransitiveDependency":false,"dependencyTree":"org.postgresql:postgresql:42.2.1","isMinimumFixVersionAvailable":true,"minimumFixVersion":"org.postgresql:postgresql:42.2.13"}],"vulnerabilityIdentifier":"CVE-2020-13692","vulnerabilityDetails":"PostgreSQL JDBC Driver (aka PgJDBC) before 42.2.13 allows XXE.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-13692","cvss3Severity":"medium","cvss3Score":"5.0","cvss3Metrics":{"A":"N/A","AC":"N/A","PR":"N/A","S":"N/A","C":"N/A","UI":"N/A","AV":"N/A","I":"N/A"},"extraData":{}}</REMEDIATE> --> | non_priority | cve medium detected in postgresql jar cve medium severity vulnerability vulnerable library postgresql jar java jdbc jre driver for postgresql database library home page a href path to dependency file tmp ws scm atlasdb atlasdb console distribution build gradle path to vulnerable library le caches modules files org postgresql postgresql postgresql jar le caches modules files org postgresql postgresql postgresql jar dependency hierarchy x postgresql jar vulnerable library vulnerability details postgresql jdbc driver aka pgjdbc before allows xxe publish date url a href cvss score details base score metrics exploitability metrics attack vector n a attack complexity n a privileges required n a user interaction n a scope n a impact metrics confidentiality impact n a integrity impact n a availability impact n a for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution org postgresql postgresql check this box to open an automated fix pr isopenpronvulnerability false ispackagebased true isdefaultbranch true packages vulnerabilityidentifier cve vulnerabilitydetails postgresql jdbc driver aka pgjdbc before allows xxe vulnerabilityurl | 0 |
167,649 | 26,529,120,686 | IssuesEvent | 2023-01-19 11:03:39 | hsmusic/hsmusic-wiki | https://api.github.com/repos/hsmusic/hsmusic-wiki | opened | Group timeline when clicking an album release date | type: needs design scope: client-side JS type: new feature | Horizontal with little thumbnails, button to select which group, etc.
This is just a crazy client-side feature suggestion, not for current release! Lots of infrastructure (re-exposing album data & client-side content generation in the first place), shared with other client-side features, required first!
| 1.0 | Group timeline when clicking an album release date - Horizontal with little thumbnails, button to select which group, etc.
This is just a crazy client-side feature suggestion, not for current release! Lots of infrastructure (re-exposing album data & client-side content generation in the first place), shared with other client-side features, required first!
| non_priority | group timeline when clicking an album release date horizontal with little thumbnails button to select which group etc this is just a crazy client side feature suggestion not for current release lots of infrastructure re exposing album data client side content generation in the first place shared with other client side features required first | 0 |
170,112 | 20,842,026,202 | IssuesEvent | 2022-03-21 02:06:53 | turkdevops/kiwiirc | https://api.github.com/repos/turkdevops/kiwiirc | opened | CVE-2022-24771 (High) detected in node-forge-0.9.0.tgz | security vulnerability | ## CVE-2022-24771 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>node-forge-0.9.0.tgz</b></p></summary>
<p>JavaScript implementations of network transports, cryptography, ciphers, PKI, message digests, and various utilities.</p>
<p>Library home page: <a href="https://registry.npmjs.org/node-forge/-/node-forge-0.9.0.tgz">https://registry.npmjs.org/node-forge/-/node-forge-0.9.0.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/node-forge/package.json</p>
<p>
Dependency Hierarchy:
- cli-service-4.3.1.tgz (Root Library)
- webpack-dev-server-3.10.3.tgz
- selfsigned-1.10.7.tgz
- :x: **node-forge-0.9.0.tgz** (Vulnerable Library)
<p>Found in base branch: <b>captcha-on-demand</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>
Forge (also called `node-forge`) is a native implementation of Transport Layer Security in JavaScript. Prior to version 1.3.0, RSA PKCS#1 v1.5 signature verification code is lenient in checking the digest algorithm structure. This can allow a crafted structure that steals padding bytes and uses unchecked portion of the PKCS#1 encoded message to forge a signature when a low public exponent is being used. The issue has been addressed in `node-forge` version 1.3.0. There are currently no known workarounds.
<p>Publish Date: 2022-03-18
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-24771>CVE-2022-24771</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: 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://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-24771">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-24771</a></p>
<p>Release Date: 2022-03-18</p>
<p>Fix Resolution: node-forge - 1.3.0</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | CVE-2022-24771 (High) detected in node-forge-0.9.0.tgz - ## CVE-2022-24771 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>node-forge-0.9.0.tgz</b></p></summary>
<p>JavaScript implementations of network transports, cryptography, ciphers, PKI, message digests, and various utilities.</p>
<p>Library home page: <a href="https://registry.npmjs.org/node-forge/-/node-forge-0.9.0.tgz">https://registry.npmjs.org/node-forge/-/node-forge-0.9.0.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/node-forge/package.json</p>
<p>
Dependency Hierarchy:
- cli-service-4.3.1.tgz (Root Library)
- webpack-dev-server-3.10.3.tgz
- selfsigned-1.10.7.tgz
- :x: **node-forge-0.9.0.tgz** (Vulnerable Library)
<p>Found in base branch: <b>captcha-on-demand</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>
Forge (also called `node-forge`) is a native implementation of Transport Layer Security in JavaScript. Prior to version 1.3.0, RSA PKCS#1 v1.5 signature verification code is lenient in checking the digest algorithm structure. This can allow a crafted structure that steals padding bytes and uses unchecked portion of the PKCS#1 encoded message to forge a signature when a low public exponent is being used. The issue has been addressed in `node-forge` version 1.3.0. There are currently no known workarounds.
<p>Publish Date: 2022-03-18
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-24771>CVE-2022-24771</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: 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://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-24771">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-24771</a></p>
<p>Release Date: 2022-03-18</p>
<p>Fix Resolution: node-forge - 1.3.0</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_priority | cve high detected in node forge tgz cve high severity vulnerability vulnerable library node forge tgz javascript implementations of network transports cryptography ciphers pki message digests and various utilities library home page a href path to dependency file package json path to vulnerable library node modules node forge package json dependency hierarchy cli service tgz root library webpack dev server tgz selfsigned tgz x node forge tgz vulnerable library found in base branch captcha on demand vulnerability details forge also called node forge is a native implementation of transport layer security in javascript prior to version rsa pkcs signature verification code is lenient in checking the digest algorithm structure this can allow a crafted structure that steals padding bytes and uses unchecked portion of the pkcs encoded message to forge a signature when a low public exponent is being used the issue has been addressed in node forge version there are currently no known workarounds 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 node forge step up your open source security game with whitesource | 0 |
102,426 | 16,566,211,272 | IssuesEvent | 2021-05-29 13:14:42 | AlexRogalskiy/github-action-random-quote | https://api.github.com/repos/AlexRogalskiy/github-action-random-quote | opened | CVE-2020-11023 (Medium) detected in jquery-1.8.1.min.js | security vulnerability | ## CVE-2020-11023 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>jquery-1.8.1.min.js</b></p></summary>
<p>JavaScript library for DOM operations</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/jquery/1.8.1/jquery.min.js">https://cdnjs.cloudflare.com/ajax/libs/jquery/1.8.1/jquery.min.js</a></p>
<p>Path to dependency file: github-action-random-quote/node_modules/redeyed/examples/browser/index.html</p>
<p>Path to vulnerable library: github-action-random-quote/node_modules/redeyed/examples/browser/index.html</p>
<p>
Dependency Hierarchy:
- :x: **jquery-1.8.1.min.js** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/AlexRogalskiy/github-action-random-quote/commit/99c135aa691d6abe5673bace94251bc0966b49e0">99c135aa691d6abe5673bace94251bc0966b49e0</a></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 jQuery versions greater than or equal to 1.0.3 and before 3.5.0, passing HTML containing <option> elements from untrusted sources - even after sanitizing it - to one of jQuery's DOM manipulation methods (i.e. .html(), .append(), and others) may execute untrusted code. This problem is patched in jQuery 3.5.0.
<p>Publish Date: 2020-04-29
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-11023>CVE-2020-11023</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-2020-11023">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-11023</a></p>
<p>Release Date: 2020-04-29</p>
<p>Fix Resolution: jquery - 3.5.0</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | CVE-2020-11023 (Medium) detected in jquery-1.8.1.min.js - ## CVE-2020-11023 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>jquery-1.8.1.min.js</b></p></summary>
<p>JavaScript library for DOM operations</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/jquery/1.8.1/jquery.min.js">https://cdnjs.cloudflare.com/ajax/libs/jquery/1.8.1/jquery.min.js</a></p>
<p>Path to dependency file: github-action-random-quote/node_modules/redeyed/examples/browser/index.html</p>
<p>Path to vulnerable library: github-action-random-quote/node_modules/redeyed/examples/browser/index.html</p>
<p>
Dependency Hierarchy:
- :x: **jquery-1.8.1.min.js** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/AlexRogalskiy/github-action-random-quote/commit/99c135aa691d6abe5673bace94251bc0966b49e0">99c135aa691d6abe5673bace94251bc0966b49e0</a></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 jQuery versions greater than or equal to 1.0.3 and before 3.5.0, passing HTML containing <option> elements from untrusted sources - even after sanitizing it - to one of jQuery's DOM manipulation methods (i.e. .html(), .append(), and others) may execute untrusted code. This problem is patched in jQuery 3.5.0.
<p>Publish Date: 2020-04-29
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-11023>CVE-2020-11023</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-2020-11023">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-11023</a></p>
<p>Release Date: 2020-04-29</p>
<p>Fix Resolution: jquery - 3.5.0</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_priority | cve medium detected in jquery min js cve medium severity vulnerability vulnerable library jquery min js javascript library for dom operations library home page a href path to dependency file github action random quote node modules redeyed examples browser index html path to vulnerable library github action random quote node modules redeyed examples browser index html dependency hierarchy x jquery min js vulnerable library found in head commit a href vulnerability details in jquery versions greater than or equal to and before passing html containing elements from untrusted sources even after sanitizing it to one of jquery s dom manipulation methods i e html append and others may execute untrusted code this problem is patched in jquery 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 step up your open source security game with whitesource | 0 |
89,906 | 18,048,114,502 | IssuesEvent | 2021-09-19 08:48:47 | edudata-plus/tools | https://api.github.com/repos/edudata-plus/tools | closed | 人物リスト対応: 第10+11桁 | code2broader | 社会科・歴史における人物リストは以下のように、第10桁目と11桁目の連番になるので、それらに対応すること：
```
8220265230000000 [ウ アの(ｱ)から(ｺ)までについては，例えば，次に掲げる人物を取り上げ，人物の働きを通して学習できるよう指導すること。]
-> 8220265230100000 [卑弥呼《ひみこ》]
-> 8220265230200000 [聖徳太子《しょうとくたいし》]
...
-> 8220265231000000 [紫式部《むらさきしきぶ》]
```
| 1.0 | 人物リスト対応: 第10+11桁 - 社会科・歴史における人物リストは以下のように、第10桁目と11桁目の連番になるので、それらに対応すること：
```
8220265230000000 [ウ アの(ｱ)から(ｺ)までについては，例えば，次に掲げる人物を取り上げ，人物の働きを通して学習できるよう指導すること。]
-> 8220265230100000 [卑弥呼《ひみこ》]
-> 8220265230200000 [聖徳太子《しょうとくたいし》]
...
-> 8220265231000000 [紫式部《むらさきしきぶ》]
```
| non_priority | 人物リスト対応 社会科・歴史における人物リストは以下のように、 、それらに対応すること： | 0 |
63,685 | 14,656,761,998 | IssuesEvent | 2020-12-28 14:08:29 | fu1771695yongxie/Boostnote | https://api.github.com/repos/fu1771695yongxie/Boostnote | opened | CVE-2020-28275 (High) detected in cache-base-1.0.1.tgz | security vulnerability | ## CVE-2020-28275 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>cache-base-1.0.1.tgz</b></p></summary>
<p>Basic object cache with `get`, `set`, `del`, and `has` methods for node.js/javascript projects.</p>
<p>Library home page: <a href="https://registry.npmjs.org/cache-base/-/cache-base-1.0.1.tgz">https://registry.npmjs.org/cache-base/-/cache-base-1.0.1.tgz</a></p>
<p>Path to dependency file: Boostnote/package.json</p>
<p>Path to vulnerable library: Boostnote/node_modules/cache-base/package.json</p>
<p>
Dependency Hierarchy:
- ava-0.25.0.tgz (Root Library)
- chokidar-1.7.0.tgz
- readdirp-2.2.1.tgz
- micromatch-3.1.10.tgz
- snapdragon-0.8.2.tgz
- base-0.11.2.tgz
- :x: **cache-base-1.0.1.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/fu1771695yongxie/Boostnote/commit/11e9dea15d65583ed8c71129e7f8b2449bca784a">11e9dea15d65583ed8c71129e7f8b2449bca784a</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
Prototype pollution vulnerability in 'cache-base' versions 0.7.0 through 4.0.0 allows attacker to cause a denial of service and may lead to remote code execution.
<p>Publish Date: 2020-11-07
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-28275>CVE-2020-28275</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | CVE-2020-28275 (High) detected in cache-base-1.0.1.tgz - ## CVE-2020-28275 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>cache-base-1.0.1.tgz</b></p></summary>
<p>Basic object cache with `get`, `set`, `del`, and `has` methods for node.js/javascript projects.</p>
<p>Library home page: <a href="https://registry.npmjs.org/cache-base/-/cache-base-1.0.1.tgz">https://registry.npmjs.org/cache-base/-/cache-base-1.0.1.tgz</a></p>
<p>Path to dependency file: Boostnote/package.json</p>
<p>Path to vulnerable library: Boostnote/node_modules/cache-base/package.json</p>
<p>
Dependency Hierarchy:
- ava-0.25.0.tgz (Root Library)
- chokidar-1.7.0.tgz
- readdirp-2.2.1.tgz
- micromatch-3.1.10.tgz
- snapdragon-0.8.2.tgz
- base-0.11.2.tgz
- :x: **cache-base-1.0.1.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/fu1771695yongxie/Boostnote/commit/11e9dea15d65583ed8c71129e7f8b2449bca784a">11e9dea15d65583ed8c71129e7f8b2449bca784a</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
Prototype pollution vulnerability in 'cache-base' versions 0.7.0 through 4.0.0 allows attacker to cause a denial of service and may lead to remote code execution.
<p>Publish Date: 2020-11-07
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-28275>CVE-2020-28275</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_priority | cve high detected in cache base tgz cve high severity vulnerability vulnerable library cache base tgz basic object cache with get set del and has methods for node js javascript projects library home page a href path to dependency file boostnote package json path to vulnerable library boostnote node modules cache base package json dependency hierarchy ava tgz root library chokidar tgz readdirp tgz micromatch tgz snapdragon tgz base tgz x cache base tgz vulnerable library found in head commit a href found in base branch master vulnerability details prototype pollution vulnerability in cache base versions through allows attacker to cause a denial of service and may lead to remote code execution publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact none integrity impact none availability impact high for more information on scores click a href step up your open source security game with whitesource | 0 |
8,922 | 6,689,643,621 | IssuesEvent | 2017-10-09 04:01:25 | openebs/openebs | https://api.github.com/repos/openebs/openebs | opened | Create YSCB benchmark k8s jobs to test Cassandra DB on OpenEBS | application area/ci area/performance | <!-- This form is for bug reports and feature requests ONLY! -->
<!-- Thanks for filing an issue! Before hitting the button, please answer these questions.-->
## Is this a BUG REPORT or FEATURE REQUEST?
FEATURE REQUEST
<!--
If this is a BUG REPORT, please:
- Fill in as much of the template below as you can. If you leave out information, we can't help you as well.
If this is a FEATURE REQUEST, please:
- Describe *in detail* the feature/behavior/change you'd like to see.
In both cases, be ready for followup questions, and please respond in a timely
manner. If we can't reproduce a bug or think a feature already exists, we
might close your issue. If we're wrong, PLEASE feel free to reopen it and
explain why.
-->
**What happened**:
YCSB is a popular benchmark tool for NoSQL. It have ready adapters for different NoSQL DB like Cassandra, Mongo, Redis and others.
The K8s YAML files to deploy a cassandra statefulset can be found here : https://github.com/openebs/openebs/tree/master/k8s/demo/cassandra
Benchmarking cassandra on OpenEBS using popular a BM tool like YCSB will help us identify bottlenecks and optimize OpenEBS for better application performance.
**What you expected to happen**:
Create the YSCB test container with requisite adapters for cassandra and also the K8s job YAMLs to run the benchmark tests & capture metrics.
<!--
**Environment**:
- kubectl get nodes
- kubectl get pods --all-namespaces
- kubectl get services
- kubectl get sc
- kubectl get pv
- kubectl get pvc
- OS (e.g. from /etc/os-release):
- Kernel (e.g. `uname -a`):
- Install tools:
- Others:
-->
| True | Create YSCB benchmark k8s jobs to test Cassandra DB on OpenEBS - <!-- This form is for bug reports and feature requests ONLY! -->
<!-- Thanks for filing an issue! Before hitting the button, please answer these questions.-->
## Is this a BUG REPORT or FEATURE REQUEST?
FEATURE REQUEST
<!--
If this is a BUG REPORT, please:
- Fill in as much of the template below as you can. If you leave out information, we can't help you as well.
If this is a FEATURE REQUEST, please:
- Describe *in detail* the feature/behavior/change you'd like to see.
In both cases, be ready for followup questions, and please respond in a timely
manner. If we can't reproduce a bug or think a feature already exists, we
might close your issue. If we're wrong, PLEASE feel free to reopen it and
explain why.
-->
**What happened**:
YCSB is a popular benchmark tool for NoSQL. It have ready adapters for different NoSQL DB like Cassandra, Mongo, Redis and others.
The K8s YAML files to deploy a cassandra statefulset can be found here : https://github.com/openebs/openebs/tree/master/k8s/demo/cassandra
Benchmarking cassandra on OpenEBS using popular a BM tool like YCSB will help us identify bottlenecks and optimize OpenEBS for better application performance.
**What you expected to happen**:
Create the YSCB test container with requisite adapters for cassandra and also the K8s job YAMLs to run the benchmark tests & capture metrics.
<!--
**Environment**:
- kubectl get nodes
- kubectl get pods --all-namespaces
- kubectl get services
- kubectl get sc
- kubectl get pv
- kubectl get pvc
- OS (e.g. from /etc/os-release):
- Kernel (e.g. `uname -a`):
- Install tools:
- Others:
-->
| non_priority | create yscb benchmark jobs to test cassandra db on openebs is this a bug report or feature request feature request if this is a bug report please fill in as much of the template below as you can if you leave out information we can t help you as well if this is a feature request please describe in detail the feature behavior change you d like to see in both cases be ready for followup questions and please respond in a timely manner if we can t reproduce a bug or think a feature already exists we might close your issue if we re wrong please feel free to reopen it and explain why what happened ycsb is a popular benchmark tool for nosql it have ready adapters for different nosql db like cassandra mongo redis and others the yaml files to deploy a cassandra statefulset can be found here benchmarking cassandra on openebs using popular a bm tool like ycsb will help us identify bottlenecks and optimize openebs for better application performance what you expected to happen create the yscb test container with requisite adapters for cassandra and also the job yamls to run the benchmark tests capture metrics environment kubectl get nodes kubectl get pods all namespaces kubectl get services kubectl get sc kubectl get pv kubectl get pvc os e g from etc os release kernel e g uname a install tools others | 0 |
139,550 | 12,867,608,453 | IssuesEvent | 2020-07-10 07:15:32 | EOSIO/eosio.cdt | https://api.github.com/repos/EOSIO/eosio.cdt | closed | [docs] as of eosio 2.0-rc1 deferred transaction are deprecated | documentation | As of eosio 2.0-rc1 deferred transaction are deprecated, the current documentation is saying they are considered to be deprecated. Change it to be explicit about it.
https://developers.eos.io/manuals/eosio.cdt/latest/best-practices/deferred_transactions/#gatsby-focus-wrapper | 1.0 | [docs] as of eosio 2.0-rc1 deferred transaction are deprecated - As of eosio 2.0-rc1 deferred transaction are deprecated, the current documentation is saying they are considered to be deprecated. Change it to be explicit about it.
https://developers.eos.io/manuals/eosio.cdt/latest/best-practices/deferred_transactions/#gatsby-focus-wrapper | non_priority | as of eosio deferred transaction are deprecated as of eosio deferred transaction are deprecated the current documentation is saying they are considered to be deprecated change it to be explicit about it | 0 |
4,488 | 11,219,704,111 | IssuesEvent | 2020-01-07 14:26:08 | mitmedialab/MediaCloud-Web-Tools | https://api.github.com/repos/mitmedialab/MediaCloud-Web-Tools | closed | validate release_history json before commit | architecture enhancement | We should set up a hook to do this automatically, so it doesn't keep biting us! Lets try husky:
https://jakebinstein.com/blog/validating-json-against-a-schema-on-commit/
| 1.0 | validate release_history json before commit - We should set up a hook to do this automatically, so it doesn't keep biting us! Lets try husky:
https://jakebinstein.com/blog/validating-json-against-a-schema-on-commit/
| non_priority | validate release history json before commit we should set up a hook to do this automatically so it doesn t keep biting us lets try husky | 0 |
156,580 | 12,323,291,772 | IssuesEvent | 2020-05-13 11:55:04 | cwerner/ldndc2nc | https://api.github.com/repos/cwerner/ldndc2nc | opened | rewrite read_ldndc_txt | testing | read_ldndc_txt is a big mess right now and well worth a rewrite (with proper testing) | 1.0 | rewrite read_ldndc_txt - read_ldndc_txt is a big mess right now and well worth a rewrite (with proper testing) | non_priority | rewrite read ldndc txt read ldndc txt is a big mess right now and well worth a rewrite with proper testing | 0 |
178,320 | 21,509,361,148 | IssuesEvent | 2022-04-28 01:32:42 | bsbtd/Teste | https://api.github.com/repos/bsbtd/Teste | closed | CVE-2016-1000031 (High) detected in commons-fileupload-1.2.jar - autoclosed | security vulnerability | ## CVE-2016-1000031 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>commons-fileupload-1.2.jar</b></p></summary>
<p>The FileUpload component provides a simple yet flexible means of adding support for multipart
file upload functionality to servlets and web applications.</p>
<p>Library home page: <a href="http://jakarta.apache.org/commons/fileupload/">http://jakarta.apache.org/commons/fileupload/</a></p>
<p>Path to vulnerable library: /upload-1.2.jar</p>
<p>
Dependency Hierarchy:
- :x: **commons-fileupload-1.2.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/bsbtd/Teste/commit/64dde89c50c07496423c4d4a865f2e16b92399ad">64dde89c50c07496423c4d4a865f2e16b92399ad</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
Apache Commons FileUpload before 1.3.3 DiskFileItem File Manipulation Remote Code Execution
<p>Publish Date: 2016-10-25
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2016-1000031>CVE-2016-1000031</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>9.8</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-1000031">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-1000031</a></p>
<p>Release Date: 2016-10-25</p>
<p>Fix Resolution: 1.3.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-2016-1000031 (High) detected in commons-fileupload-1.2.jar - autoclosed - ## CVE-2016-1000031 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>commons-fileupload-1.2.jar</b></p></summary>
<p>The FileUpload component provides a simple yet flexible means of adding support for multipart
file upload functionality to servlets and web applications.</p>
<p>Library home page: <a href="http://jakarta.apache.org/commons/fileupload/">http://jakarta.apache.org/commons/fileupload/</a></p>
<p>Path to vulnerable library: /upload-1.2.jar</p>
<p>
Dependency Hierarchy:
- :x: **commons-fileupload-1.2.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/bsbtd/Teste/commit/64dde89c50c07496423c4d4a865f2e16b92399ad">64dde89c50c07496423c4d4a865f2e16b92399ad</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
Apache Commons FileUpload before 1.3.3 DiskFileItem File Manipulation Remote Code Execution
<p>Publish Date: 2016-10-25
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2016-1000031>CVE-2016-1000031</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>9.8</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-1000031">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-1000031</a></p>
<p>Release Date: 2016-10-25</p>
<p>Fix Resolution: 1.3.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 commons fileupload jar autoclosed cve high severity vulnerability vulnerable library commons fileupload jar the fileupload component provides a simple yet flexible means of adding support for multipart file upload functionality to servlets and web applications library home page a href path to vulnerable library upload jar dependency hierarchy x commons fileupload jar vulnerable library found in head commit a href vulnerability details apache commons fileupload before diskfileitem file manipulation remote code execution publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact 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 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.