Split (1)

train · 223k rows

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
249,226	26,890,773,678	IssuesEvent	2023-02-06 08:45:08	samq-ghdemo/snyk-goof	https://api.github.com/repos/samq-ghdemo/snyk-goof	opened	snyk-1.290.2.tgz: 28 vulnerabilities (highest severity is: 9.8)	security vulnerability	<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>snyk-1.290.2.tgz</b></p></summary> <p>snyk library and cli utility</p> <p>Library home page: <a href="https://registry.npmjs.org/snyk/-/snyk-1.290.2.tgz">https://registry.npmjs.org/snyk/-/snyk-1.290.2.tgz</a></p> <p>Path to dependency file: /package.json</p> <p>Path to vulnerable library: /node_modules/snyk/package.json</p> <p> <p>Found in HEAD commit: <a href="https://github.com/samq-ghdemo/snyk-goof/commit/77eae86d878e3f5b3d008c20fb02ac8f24ee2393">77eae86d878e3f5b3d008c20fb02ac8f24ee2393</a></p></details> ## Vulnerabilities \| CVE \| Severity \| <img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS \| Dependency \| Type \| Fixed in (snyk version) \| Remediation Available \| \| ------------- \| ------------- \| ----- \| ----- \| ----- \| ------------- \| --- \| \| [CVE-2021-23406](https://www.mend.io/vulnerability-database/CVE-2021-23406) \| <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High \| 9.8 \| detected in multiple dependencies \| Transitive \| 1.518.0 \| ✅ \| \| [CVE-2022-2216](https://www.mend.io/vulnerability-database/CVE-2022-2216) \| <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High \| 9.8 \| parse-url-5.0.1.tgz \| Transitive \| 1.291.0 \| ✅ \| \| [CVE-2020-7774](https://www.mend.io/vulnerability-database/CVE-2020-7774) \| <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High \| 9.8 \| y18n-3.2.1.tgz \| Transitive \| 1.291.0 \| ✅ \| \| [CVE-2021-28918](https://www.mend.io/vulnerability-database/CVE-2021-28918) \| <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High \| 9.1 \| netmask-1.0.6.tgz \| Transitive \| 1.518.0 \| ✅ \| \| [CVE-2022-2900](https://www.mend.io/vulnerability-database/CVE-2022-2900) \| <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High \| 9.1 \| parse-url-5.0.1.tgz \| Transitive \| 1.324.0 \| ✅ \| \| [CVE-2022-24441](https://www.mend.io/vulnerability-database/CVE-2022-24441) \| <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High \| 8.8 \| snyk-1.290.2.tgz \| Direct \| 1.1064.0 \| ✅ \| \| [CVE-2022-40764](https://www.mend.io/vulnerability-database/CVE-2022-40764) \| <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High \| 7.8 \| snyk-1.290.2.tgz \| Direct \| 1.996.0 \| ✅ \| \| [CVE-2021-3807](https://www.mend.io/vulnerability-database/CVE-2021-3807) \| <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High \| 7.5 \| detected in multiple dependencies \| Transitive \| 1.685.0 \| ✅ \| \| [CVE-2022-3517](https://www.mend.io/vulnerability-database/CVE-2022-3517) \| <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High \| 7.5 \| minimatch-3.0.4.tgz \| Transitive \| N/A* \| ❌ \| \| [CVE-2022-0722](https://www.mend.io/vulnerability-database/CVE-2022-0722) \| <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High \| 7.5 \| parse-url-5.0.1.tgz \| Transitive \| 1.291.0 \| ✅ \| \| [CVE-2022-21803](https://www.mend.io/vulnerability-database/CVE-2022-21803) \| <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High \| 7.5 \| nconf-0.10.0.tgz \| Transitive \| 1.425.4 \| ✅ \| \| [WS-2022-0237](https://github.com/ionicabizau/parse-url/commit/b88c81df8f4c5168af454eaa4f92afa9349e4e13) \| <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High \| 7.5 \| parse-url-5.0.1.tgz \| Transitive \| 1.324.0 \| ✅ \| \| [WS-2022-0238](https://huntr.dev/bounties/52060edb-e426-431b-a0d0-e70407e44f18/) \| <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High \| 7.5 \| parse-url-5.0.1.tgz \| Transitive \| 1.324.0 \| ✅ \| \| [CVE-2020-8203](https://www.mend.io/vulnerability-database/CVE-2020-8203) \| <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High \| 7.4 \| lodash-4.17.15.tgz \| Transitive \| 1.291.0 \| ✅ \| \| [CVE-2022-48285](https://www.mend.io/vulnerability-database/CVE-2022-48285) \| <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High \| 7.3 \| jszip-3.2.2.tgz \| Transitive \| 1.291.0 \| ✅ \| \| [CVE-2022-0624](https://www.mend.io/vulnerability-database/CVE-2022-0624) \| <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High \| 7.3 \| parse-path-4.0.1.tgz \| Transitive \| 1.324.0 \| ✅ \| \| [CVE-2021-23337](https://www.mend.io/vulnerability-database/CVE-2021-23337) \| <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High \| 7.2 \| lodash-4.17.15.tgz \| Transitive \| 1.291.0 \| ✅ \| \| [CVE-2020-8244](https://www.mend.io/vulnerability-database/CVE-2020-8244) \| <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium \| 6.5 \| bl-3.0.0.tgz \| Transitive \| 1.291.0 \| ✅ \| \| [CVE-2022-22984](https://www.mend.io/vulnerability-database/CVE-2022-22984) \| <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium \| 6.3 \| detected in multiple dependencies \| Transitive \| 1.330.1 \| ✅ \| \| [CVE-2022-3224](https://www.mend.io/vulnerability-database/CVE-2022-3224) \| <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium \| 6.1 \| parse-url-5.0.1.tgz \| Transitive \| N/A* \| ❌ \| \| [CVE-2022-2217](https://www.mend.io/vulnerability-database/CVE-2022-2217) \| <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium \| 6.1 \| parse-url-5.0.1.tgz \| Transitive \| 1.291.0 \| ✅ \| \| [CVE-2022-2218](https://www.mend.io/vulnerability-database/CVE-2022-2218) \| <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium \| 6.1 \| parse-url-5.0.1.tgz \| Transitive \| 1.291.0 \| ✅ \| \| [WS-2022-0239](https://github.com/ionicabizau/parse-url/commit/b88c81df8f4c5168af454eaa4f92afa9349e4e13) \| <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium \| 6.1 \| parse-url-5.0.1.tgz \| Transitive \| 1.324.0 \| ✅ \| \| [CVE-2020-28500](https://www.mend.io/vulnerability-database/CVE-2020-28500) \| <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium \| 5.3 \| lodash-4.17.15.tgz \| Transitive \| 1.291.0 \| ✅ \| \| [CVE-2021-29418](https://www.mend.io/vulnerability-database/CVE-2021-29418) \| <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium \| 5.3 \| netmask-1.0.6.tgz \| Transitive \| 1.518.0 \| ✅ \| \| [CVE-2021-23413](https://www.mend.io/vulnerability-database/CVE-2021-23413) \| <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium \| 5.3 \| jszip-3.2.2.tgz \| Transitive \| 1.291.0 \| ✅ \| \| [CVE-2022-33987](https://www.mend.io/vulnerability-database/CVE-2022-33987) \| <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium \| 5.3 \| got-6.7.1.tgz \| Transitive \| 1.685.0 \| ✅ \| \| [CVE-2021-23362](https://www.mend.io/vulnerability-database/CVE-2021-23362) \| <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium \| 5.3 \| hosted-git-info-2.8.5.tgz \| Transitive \| 1.291.0 \| ✅ \| <p>For some transitive vulnerabilities, there is no version of direct dependency with a fix. Check the section "Details" below to see if there is a version of transitive dependency where vulnerability is fixed.</p> ## Details > Partial details (22 vulnerabilities) are displayed below due to a content size limitation in GitHub. To view information on the remaining vulnerabilities, navigate to the Mend Application.<br> <details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2021-23406</summary> ### Vulnerable Libraries - <b>pac-resolver-3.0.0.tgz</b>, <b>degenerator-1.0.4.tgz</b></p> <p> ### <b>pac-resolver-3.0.0.tgz</b></p> <p>Generates an asynchronous resolver function from a PAC file</p> <p>Library home page: <a href="https://registry.npmjs.org/pac-resolver/-/pac-resolver-3.0.0.tgz">https://registry.npmjs.org/pac-resolver/-/pac-resolver-3.0.0.tgz</a></p> <p>Path to dependency file: /package.json</p> <p>Path to vulnerable library: /node_modules/pac-resolver/package.json</p> <p> Dependency Hierarchy: - snyk-1.290.2.tgz (Root Library) - proxy-agent-3.1.1.tgz - pac-proxy-agent-3.0.1.tgz - :x: pac-resolver-3.0.0.tgz* (Vulnerable Library) ### <b>degenerator-1.0.4.tgz</b></p> <p>Turns sync functions into async generator functions</p> <p>Library home page: <a href="https://registry.npmjs.org/degenerator/-/degenerator-1.0.4.tgz">https://registry.npmjs.org/degenerator/-/degenerator-1.0.4.tgz</a></p> <p>Path to dependency file: /package.json</p> <p>Path to vulnerable library: /node_modules/degenerator/package.json</p> <p> Dependency Hierarchy: - snyk-1.290.2.tgz (Root Library) - proxy-agent-3.1.1.tgz - pac-proxy-agent-3.0.1.tgz - pac-resolver-3.0.0.tgz - :x: degenerator-1.0.4.tgz (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/samq-ghdemo/snyk-goof/commit/77eae86d878e3f5b3d008c20fb02ac8f24ee2393">77eae86d878e3f5b3d008c20fb02ac8f24ee2393</a></p> <p>Found in base branch: <b>master</b></p> </p> <p></p> ### Vulnerability Details <p> This affects the package pac-resolver before 5.0.0. This can occur when used with untrusted input, due to unsafe PAC file handling. NOTE: The fix for this vulnerability is applied in the node-degenerator library, a dependency written by the same maintainer. <p>Publish Date: 2021-08-24 <p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2021-23406>CVE-2021-23406</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>9.8</b>) <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: High - Integrity Impact: High - Availability Impact: High </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> <p></p> ### Suggested Fix <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://github.com/advisories/GHSA-9j49-mfvp-vmhm">https://github.com/advisories/GHSA-9j49-mfvp-vmhm</a></p> <p>Release Date: 2021-08-24</p> <p>Fix Resolution (pac-resolver): 5.0.0</p> <p>Direct dependency fix Resolution (snyk): 1.518.0</p><p>Fix Resolution (degenerator): 3.0.1</p> <p>Direct dependency fix Resolution (snyk): 1.518.0</p> </p> <p></p> :rescue_worker_helmet: Automatic Remediation is available for this issue </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2022-2216</summary> ### Vulnerable Library - <b>parse-url-5.0.1.tgz</b></p> <p>An advanced url parser supporting git urls too.</p> <p>Library home page: <a href="https://registry.npmjs.org/parse-url/-/parse-url-5.0.1.tgz">https://registry.npmjs.org/parse-url/-/parse-url-5.0.1.tgz</a></p> <p>Path to dependency file: /package.json</p> <p>Path to vulnerable library: /node_modules/parse-url/package.json</p> <p> Dependency Hierarchy: - snyk-1.290.2.tgz (Root Library) - git-url-parse-11.1.2.tgz - git-up-4.0.1.tgz - :x: parse-url-5.0.1.tgz (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/samq-ghdemo/snyk-goof/commit/77eae86d878e3f5b3d008c20fb02ac8f24ee2393">77eae86d878e3f5b3d008c20fb02ac8f24ee2393</a></p> <p>Found in base branch: <b>master</b></p> </p> <p></p> ### Vulnerability Details <p> Server-Side Request Forgery (SSRF) in GitHub repository ionicabizau/parse-url prior to 7.0.0. <p>Publish Date: 2022-06-27 <p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-2216>CVE-2022-2216</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>9.8</b>) <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: High - Integrity Impact: High - Availability Impact: High </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> <p></p> ### Suggested Fix <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://huntr.dev/bounties/505a3d39-2723-4a06-b1f7-9b2d133c92e1/">https://huntr.dev/bounties/505a3d39-2723-4a06-b1f7-9b2d133c92e1/</a></p> <p>Release Date: 2022-06-27</p> <p>Fix Resolution (parse-url): 6.0.3</p> <p>Direct dependency fix Resolution (snyk): 1.291.0</p> </p> <p></p> :rescue_worker_helmet: Automatic Remediation is available for this issue </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2020-7774</summary> ### Vulnerable Library - <b>y18n-3.2.1.tgz</b></p> <p>the bare-bones internationalization library used by yargs</p> <p>Library home page: <a href="https://registry.npmjs.org/y18n/-/y18n-3.2.1.tgz">https://registry.npmjs.org/y18n/-/y18n-3.2.1.tgz</a></p> <p>Path to dependency file: /package.json</p> <p>Path to vulnerable library: /node_modules/nyc/node_modules/yargs/node_modules/y18n/package.json,/node_modules/y18n/package.json</p> <p> Dependency Hierarchy: - snyk-1.290.2.tgz (Root Library) - snyk-config-2.2.3.tgz - nconf-0.10.0.tgz - yargs-3.32.0.tgz - :x: y18n-3.2.1.tgz (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/samq-ghdemo/snyk-goof/commit/77eae86d878e3f5b3d008c20fb02ac8f24ee2393">77eae86d878e3f5b3d008c20fb02ac8f24ee2393</a></p> <p>Found in base branch: <b>master</b></p> </p> <p></p> ### Vulnerability Details <p> The package y18n before 3.2.2, 4.0.1 and 5.0.5, is vulnerable to Prototype Pollution. <p>Publish Date: 2020-11-17 <p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2020-7774>CVE-2020-7774</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>9.8</b>) <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: High - Integrity Impact: High - Availability Impact: High </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> <p></p> ### Suggested Fix <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://www.npmjs.com/advisories/1654">https://www.npmjs.com/advisories/1654</a></p> <p>Release Date: 2020-11-17</p> <p>Fix Resolution (y18n): 3.2.2</p> <p>Direct dependency fix Resolution (snyk): 1.291.0</p> </p> <p></p> :rescue_worker_helmet: Automatic Remediation is available for this issue </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2021-28918</summary> ### Vulnerable Library - <b>netmask-1.0.6.tgz</b></p> <p>Parse and lookup IP network blocks</p> <p>Library home page: <a href="https://registry.npmjs.org/netmask/-/netmask-1.0.6.tgz">https://registry.npmjs.org/netmask/-/netmask-1.0.6.tgz</a></p> <p>Path to dependency file: /package.json</p> <p>Path to vulnerable library: /node_modules/netmask/package.json</p> <p> Dependency Hierarchy: - snyk-1.290.2.tgz (Root Library) - proxy-agent-3.1.1.tgz - pac-proxy-agent-3.0.1.tgz - pac-resolver-3.0.0.tgz - :x: netmask-1.0.6.tgz (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/samq-ghdemo/snyk-goof/commit/77eae86d878e3f5b3d008c20fb02ac8f24ee2393">77eae86d878e3f5b3d008c20fb02ac8f24ee2393</a></p> <p>Found in base branch: <b>master</b></p> </p> <p></p> ### Vulnerability Details <p> Improper input validation of octal strings in netmask npm package v1.0.6 and below allows unauthenticated remote attackers to perform indeterminate SSRF, RFI, and LFI attacks on many of the dependent packages. A remote unauthenticated attacker can bypass packages relying on netmask to filter IPs and reach critical VPN or LAN hosts. <p>Publish Date: 2021-04-01 <p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2021-28918>CVE-2021-28918</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>9.1</b>) <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: High - Integrity Impact: High - Availability Impact: 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://github.com/advisories/GHSA-pch5-whg9-qr2r">https://github.com/advisories/GHSA-pch5-whg9-qr2r</a></p> <p>Release Date: 2021-04-01</p> <p>Fix Resolution (netmask): 2.0.1</p> <p>Direct dependency fix Resolution (snyk): 1.518.0</p> </p> <p></p> :rescue_worker_helmet: Automatic Remediation is available for this issue </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2022-2900</summary> ### Vulnerable Library - <b>parse-url-5.0.1.tgz</b></p> <p>An advanced url parser supporting git urls too.</p> <p>Library home page: <a href="https://registry.npmjs.org/parse-url/-/parse-url-5.0.1.tgz">https://registry.npmjs.org/parse-url/-/parse-url-5.0.1.tgz</a></p> <p>Path to dependency file: /package.json</p> <p>Path to vulnerable library: /node_modules/parse-url/package.json</p> <p> Dependency Hierarchy: - snyk-1.290.2.tgz (Root Library) - git-url-parse-11.1.2.tgz - git-up-4.0.1.tgz - :x: parse-url-5.0.1.tgz (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/samq-ghdemo/snyk-goof/commit/77eae86d878e3f5b3d008c20fb02ac8f24ee2393">77eae86d878e3f5b3d008c20fb02ac8f24ee2393</a></p> <p>Found in base branch: <b>master</b></p> </p> <p></p> ### Vulnerability Details <p> Server-Side Request Forgery (SSRF) in GitHub repository ionicabizau/parse-url prior to 8.1.0. <p>Publish Date: 2022-09-14 <p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-2900>CVE-2022-2900</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>9.1</b>) <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: High - Integrity Impact: High - Availability Impact: 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>Release Date: 2022-09-14</p> <p>Fix Resolution (parse-url): 8.0.0</p> <p>Direct dependency fix Resolution (snyk): 1.324.0</p> </p> <p></p> :rescue_worker_helmet: Automatic Remediation is available for this issue </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2022-24441</summary> ### Vulnerable Library - <b>snyk-1.290.2.tgz</b></p> <p>snyk library and cli utility</p> <p>Library home page: <a href="https://registry.npmjs.org/snyk/-/snyk-1.290.2.tgz">https://registry.npmjs.org/snyk/-/snyk-1.290.2.tgz</a></p> <p>Path to dependency file: /package.json</p> <p>Path to vulnerable library: /node_modules/snyk/package.json</p> <p> Dependency Hierarchy: - :x: snyk-1.290.2.tgz (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/samq-ghdemo/snyk-goof/commit/77eae86d878e3f5b3d008c20fb02ac8f24ee2393">77eae86d878e3f5b3d008c20fb02ac8f24ee2393</a></p> <p>Found in base branch: <b>master</b></p> </p> <p></p> ### Vulnerability Details <p> The package snyk before 1.1064.0 are vulnerable to Code Injection when analyzing a project. An attacker who can convince a user to scan a malicious project can include commands in a build file such as build.gradle or gradle-wrapper.jar, which will be executed with the privileges of the application. This vulnerability may be triggered when running the the CLI tool directly, or when running a scan with one of the IDE plugins that invoke the Snyk CLI. Successful exploitation of this issue would likely require some level of social engineering - to coerce an untrusted project to be downloaded and analyzed via the Snyk CLI or opened in an IDE where a Snyk IDE plugin is installed and enabled. Additionally, if the IDE has a Trust feature then the target folder must be marked as ‘trusted’ in order to be vulnerable. NOTE: This issue is independent of the one reported in [CVE-2022-40764](https://security.snyk.io/vuln/SNYK-JS-SNYK-3037342), and upgrading to a fixed version for this addresses that issue as well. The affected IDE plugins and versions are: - VS Code - Affected: <=1.8.0, Fixed: 1.9.0 - IntelliJ - Affected: <=2.4.47, Fixed: 2.4.48 - Visual Studio - Affected: <=1.1.30, Fixed: 1.1.31 - Eclipse - Affected: <=v20221115.132308, Fixed: All subsequent versions - Language Server - Affected: <=v20221109.114426, Fixed: All subsequent versions <p>Publish Date: 2022-11-30 <p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-24441>CVE-2022-24441</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>8.8</b>) <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: Required - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: High - Integrity Impact: High - Availability Impact: High </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> <p></p> ### Suggested Fix <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://www.cve.org/CVERecord?id=CVE-2022-24441">https://www.cve.org/CVERecord?id=CVE-2022-24441</a></p> <p>Release Date: 2022-11-30</p> <p>Fix Resolution: 1.1064.0</p> </p> <p></p> :rescue_worker_helmet: Automatic Remediation is available for this issue </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2022-40764</summary> ### Vulnerable Library - <b>snyk-1.290.2.tgz</b></p> <p>snyk library and cli utility</p> <p>Library home page: <a href="https://registry.npmjs.org/snyk/-/snyk-1.290.2.tgz">https://registry.npmjs.org/snyk/-/snyk-1.290.2.tgz</a></p> <p>Path to dependency file: /package.json</p> <p>Path to vulnerable library: /node_modules/snyk/package.json</p> <p> Dependency Hierarchy: - :x: snyk-1.290.2.tgz (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/samq-ghdemo/snyk-goof/commit/77eae86d878e3f5b3d008c20fb02ac8f24ee2393">77eae86d878e3f5b3d008c20fb02ac8f24ee2393</a></p> <p>Found in base branch: <b>master</b></p> </p> <p></p> ### Vulnerability Details <p> Snyk CLI before 1.996.0 allows arbitrary command execution, affecting Snyk IDE plugins and the snyk npm package. Exploitation could follow from the common practice of viewing untrusted files in the Visual Studio Code editor, for example. The original demonstration was with shell metacharacters in the vendor.json ignore field, affecting snyk-go-plugin before 1.19.1. This affects, for example, the Snyk TeamCity plugin (which does not update automatically) before 20220930.142957. <p>Publish Date: 2022-10-03 <p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-40764>CVE-2022-40764</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>7.8</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: High - Integrity Impact: High - Availability Impact: High </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> <p></p> ### Suggested Fix <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://github.com/advisories/GHSA-hpqj-7cj6-hfj8">https://github.com/advisories/GHSA-hpqj-7cj6-hfj8</a></p> <p>Release Date: 2022-10-03</p> <p>Fix Resolution: 1.996.0</p> </p> <p></p> :rescue_worker_helmet: Automatic Remediation is available for this issue </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2021-3807</summary> ### Vulnerable Libraries - <b>ansi-regex-4.1.0.tgz</b>, <b>ansi-regex-3.0.0.tgz</b></p> <p> ### <b>ansi-regex-4.1.0.tgz</b></p> <p>Regular expression for matching ANSI escape codes</p> <p>Library home page: <a href="https://registry.npmjs.org/ansi-regex/-/ansi-regex-4.1.0.tgz">https://registry.npmjs.org/ansi-regex/-/ansi-regex-4.1.0.tgz</a></p> <p>Path to dependency file: /package.json</p> <p>Path to vulnerable library: /node_modules/wrap-ansi/node_modules/ansi-regex/package.json,/node_modules/snyk/node_modules/ansi-regex/package.json,/node_modules/inquirer/node_modules/ansi-regex/package.json</p> <p> Dependency Hierarchy: - snyk-1.290.2.tgz (Root Library) - strip-ansi-5.2.0.tgz - :x: ansi-regex-4.1.0.tgz (Vulnerable Library) ### <b>ansi-regex-3.0.0.tgz</b></p> <p>Regular expression for matching ANSI escape codes</p> <p>Library home page: <a href="https://registry.npmjs.org/ansi-regex/-/ansi-regex-3.0.0.tgz">https://registry.npmjs.org/ansi-regex/-/ansi-regex-3.0.0.tgz</a></p> <p>Path to dependency file: /package.json</p> <p>Path to vulnerable library: /node_modules/string-width/node_modules/ansi-regex/package.json</p> <p> Dependency Hierarchy: - snyk-1.290.2.tgz (Root Library) - inquirer-6.5.2.tgz - string-width-2.1.1.tgz - strip-ansi-4.0.0.tgz - :x: ansi-regex-3.0.0.tgz (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/samq-ghdemo/snyk-goof/commit/77eae86d878e3f5b3d008c20fb02ac8f24ee2393">77eae86d878e3f5b3d008c20fb02ac8f24ee2393</a></p> <p>Found in base branch: <b>master</b></p> </p> <p></p> ### Vulnerability Details <p> ansi-regex is vulnerable to Inefficient Regular Expression Complexity <p>Publish Date: 2021-09-17 <p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2021-3807>CVE-2021-3807</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>7.5</b>) <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: None - Integrity Impact: None - Availability Impact: High </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> <p></p> ### Suggested Fix <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://huntr.dev/bounties/5b3cf33b-ede0-4398-9974-800876dfd994/">https://huntr.dev/bounties/5b3cf33b-ede0-4398-9974-800876dfd994/</a></p> <p>Release Date: 2021-09-17</p> <p>Fix Resolution (ansi-regex): 4.1.1</p> <p>Direct dependency fix Resolution (snyk): 1.685.0</p><p>Fix Resolution (ansi-regex): 3.0.1</p> <p>Direct dependency fix Resolution (snyk): 1.291.0</p> </p> <p></p> :rescue_worker_helmet: Automatic Remediation is available for this issue </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2022-3517</summary> ### Vulnerable Library - <b>minimatch-3.0.4.tgz</b></p> <p>a glob matcher in javascript</p> <p>Library home page: <a href="https://registry.npmjs.org/minimatch/-/minimatch-3.0.4.tgz">https://registry.npmjs.org/minimatch/-/minimatch-3.0.4.tgz</a></p> <p>Path to dependency file: /package.json</p> <p>Path to vulnerable library: /node_modules/minimatch/package.json</p> <p> Dependency Hierarchy: - snyk-1.290.2.tgz (Root Library) - glob-7.1.3.tgz - :x: minimatch-3.0.4.tgz (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/samq-ghdemo/snyk-goof/commit/77eae86d878e3f5b3d008c20fb02ac8f24ee2393">77eae86d878e3f5b3d008c20fb02ac8f24ee2393</a></p> <p>Found in base branch: <b>master</b></p> </p> <p></p> ### Vulnerability Details <p> A vulnerability was found in the minimatch package. This flaw allows a Regular Expression Denial of Service (ReDoS) when calling the braceExpand function with specific arguments, resulting in a Denial of Service. <p>Publish Date: 2022-10-17 <p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-3517>CVE-2022-3517</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>7.5</b>) <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: None - Integrity Impact: None - Availability Impact: High </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> <p></p> ### Suggested Fix <p> <p>Type: Upgrade version</p> <p>Release Date: 2022-10-17</p> <p>Fix Resolution: minimatch - 3.0.5</p> </p> <p></p> </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2022-0722</summary> ### Vulnerable Library - <b>parse-url-5.0.1.tgz</b></p> <p>An advanced url parser supporting git urls too.</p> <p>Library home page: <a href="https://registry.npmjs.org/parse-url/-/parse-url-5.0.1.tgz">https://registry.npmjs.org/parse-url/-/parse-url-5.0.1.tgz</a></p> <p>Path to dependency file: /package.json</p> <p>Path to vulnerable library: /node_modules/parse-url/package.json</p> <p> Dependency Hierarchy: - snyk-1.290.2.tgz (Root Library) - git-url-parse-11.1.2.tgz - git-up-4.0.1.tgz - :x: parse-url-5.0.1.tgz (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/samq-ghdemo/snyk-goof/commit/77eae86d878e3f5b3d008c20fb02ac8f24ee2393">77eae86d878e3f5b3d008c20fb02ac8f24ee2393</a></p> <p>Found in base branch: <b>master</b></p> </p> <p></p> ### Vulnerability Details <p> Exposure of Sensitive Information to an Unauthorized Actor in GitHub repository ionicabizau/parse-url prior to 7.0.0. <p>Publish Date: 2022-06-27 <p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-0722>CVE-2022-0722</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>7.5</b>) <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: High - Integrity Impact: None - Availability Impact: None </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> <p></p> ### Suggested Fix <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://huntr.dev/bounties/2490ef6d-5577-4714-a4dd-9608251b4226">https://huntr.dev/bounties/2490ef6d-5577-4714-a4dd-9608251b4226</a></p> <p>Release Date: 2022-06-27</p> <p>Fix Resolution (parse-url): 6.0.3</p> <p>Direct dependency fix Resolution (snyk): 1.291.0</p> </p> <p></p> :rescue_worker_helmet: Automatic Remediation is available for this issue </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2022-21803</summary> ### Vulnerable Library - <b>nconf-0.10.0.tgz</b></p> <p>Hierarchical node.js configuration with files, environment variables, command-line arguments, and atomic object merging.</p> <p>Library home page: <a href="https://registry.npmjs.org/nconf/-/nconf-0.10.0.tgz">https://registry.npmjs.org/nconf/-/nconf-0.10.0.tgz</a></p> <p>Path to dependency file: /package.json</p> <p>Path to vulnerable library: /node_modules/nconf/package.json</p> <p> Dependency Hierarchy: - snyk-1.290.2.tgz (Root Library) - snyk-config-2.2.3.tgz - :x: nconf-0.10.0.tgz (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/samq-ghdemo/snyk-goof/commit/77eae86d878e3f5b3d008c20fb02ac8f24ee2393">77eae86d878e3f5b3d008c20fb02ac8f24ee2393</a></p> <p>Found in base branch: <b>master</b></p> </p> <p></p> ### Vulnerability Details <p> This affects the package nconf before 0.11.4. When using the memory engine, it is possible to store a nested JSON representation of the configuration. The .set() function, that is responsible for setting the configuration properties, is vulnerable to Prototype Pollution. By providing a crafted property, it is possible to modify the properties on the Object.prototype. <p>Publish Date: 2022-04-12 <p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-21803>CVE-2022-21803</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>7.5</b>) <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: None - Integrity Impact: High - Availability Impact: None </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> <p></p> ### Suggested Fix <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-21803">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-21803</a></p> <p>Release Date: 2022-04-12</p> <p>Fix Resolution (nconf): 0.11.4</p> <p>Direct dependency fix Resolution (snyk): 1.425.4</p> </p> <p></p> :rescue_worker_helmet: Automatic Remediation is available for this issue </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> WS-2022-0237</summary> ### Vulnerable Library - <b>parse-url-5.0.1.tgz</b></p> <p>An advanced url parser supporting git urls too.</p> <p>Library home page: <a href="https://registry.npmjs.org/parse-url/-/parse-url-5.0.1.tgz">https://registry.npmjs.org/parse-url/-/parse-url-5.0.1.tgz</a></p> <p>Path to dependency file: /package.json</p> <p>Path to vulnerable library: /node_modules/parse-url/package.json</p> <p> Dependency Hierarchy: - snyk-1.290.2.tgz (Root Library) - git-url-parse-11.1.2.tgz - git-up-4.0.1.tgz - :x: parse-url-5.0.1.tgz (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/samq-ghdemo/snyk-goof/commit/77eae86d878e3f5b3d008c20fb02ac8f24ee2393">77eae86d878e3f5b3d008c20fb02ac8f24ee2393</a></p> <p>Found in base branch: <b>master</b></p> </p> <p></p> ### Vulnerability Details <p> Regular Expression Denial of Service (ReDoS) in ionicabizau/parse-url before 8.0.0. It allows cause a denial of service when calling function parse-url <p>Publish Date: 2022-07-04 <p>URL: <a href=https://github.com/ionicabizau/parse-url/commit/b88c81df8f4c5168af454eaa4f92afa9349e4e13>WS-2022-0237</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>7.5</b>) <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: None - Integrity Impact: None - Availability Impact: High </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> <p></p> ### Suggested Fix <p> <p>Type: Upgrade version</p> <p>Release Date: 2022-07-04</p> <p>Fix Resolution (parse-url): 8.0.0</p> <p>Direct dependency fix Resolution (snyk): 1.324.0</p> </p> <p></p> :rescue_worker_helmet: Automatic Remediation is available for this issue </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> WS-2022-0238</summary> ### Vulnerable Library - <b>parse-url-5.0.1.tgz</b></p> <p>An advanced url parser supporting git urls too.</p> <p>Library home page: <a href="https://registry.npmjs.org/parse-url/-/parse-url-5.0.1.tgz">https://registry.npmjs.org/parse-url/-/parse-url-5.0.1.tgz</a></p> <p>Path to dependency file: /package.json</p> <p>Path to vulnerable library: /node_modules/parse-url/package.json</p> <p> Dependency Hierarchy: - snyk-1.290.2.tgz (Root Library) - git-url-parse-11.1.2.tgz - git-up-4.0.1.tgz - :x: parse-url-5.0.1.tgz (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/samq-ghdemo/snyk-goof/commit/77eae86d878e3f5b3d008c20fb02ac8f24ee2393">77eae86d878e3f5b3d008c20fb02ac8f24ee2393</a></p> <p>Found in base branch: <b>master</b></p> </p> <p></p> ### Vulnerability Details <p> File Protocol Spoofing in parse-url before 8.0.0 can lead to attacks, such as XSS, Arbitrary Read/Write File, and Remote Code Execution. <p>Publish Date: 2022-06-30 <p>URL: <a href=https://huntr.dev/bounties/52060edb-e426-431b-a0d0-e70407e44f18/>WS-2022-0238</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>7.5</b>) <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: High - Privileges Required: None - User Interaction: Required - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: High - Integrity Impact: High - Availability Impact: High </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> <p></p> ### Suggested Fix <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://huntr.dev/bounties/52060edb-e426-431b-a0d0-e70407e44f18/">https://huntr.dev/bounties/52060edb-e426-431b-a0d0-e70407e44f18/</a></p> <p>Release Date: 2022-06-30</p> <p>Fix Resolution (parse-url): 8.0.0</p> <p>Direct dependency fix Resolution (snyk): 1.324.0</p> </p> <p></p> :rescue_worker_helmet: Automatic Remediation is available for this issue </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2020-8203</summary> ### Vulnerable Library - <b>lodash-4.17.15.tgz</b></p> <p>Lodash modular utilities.</p> <p>Library home page: <a href="https://registry.npmjs.org/lodash/-/lodash-4.17.15.tgz">https://registry.npmjs.org/lodash/-/lodash-4.17.15.tgz</a></p> <p>Path to dependency file: /package.json</p> <p>Path to vulnerable library: /node_modules/snyk/node_modules/lodash/package.json,/node_modules/snyk-nodejs-lockfile-parser/node_modules/lodash/package.json,/node_modules/snyk-config/node_modules/lodash/package.json,/node_modules/@snyk/ruby-semver/node_modules/lodash/package.json,/node_modules/snyk-nuget-plugin/node_modules/lodash/package.json,/node_modules/inquirer/node_modules/lodash/package.json,/node_modules/graphlib/node_modules/lodash/package.json,/node_modules/snyk-mvn-plugin/node_modules/lodash/package.json,/node_modules/dotnet-deps-parser/node_modules/lodash/package.json,/node_modules/@snyk/composer-lockfile-parser/node_modules/lodash/package.json</p> <p> Dependency Hierarchy: - snyk-1.290.2.tgz (Root Library) - :x: lodash-4.17.15.tgz (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/samq-ghdemo/snyk-goof/commit/77eae86d878e3f5b3d008c20fb02ac8f24ee2393">77eae86d878e3f5b3d008c20fb02ac8f24ee2393</a></p> <p>Found in base branch: <b>master</b></p> </p> <p></p> ### Vulnerability Details <p> Prototype pollution attack when using _.zipObjectDeep in lodash before 4.17.20. <p>Publish Date: 2020-07-15 <p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2020-8203>CVE-2020-8203</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>7.4</b>) <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: High - Privileges Required: None - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: None - Integrity Impact: High - Availability Impact: High </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> <p></p> ### Suggested Fix <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://www.npmjs.com/advisories/1523">https://www.npmjs.com/advisories/1523</a></p> <p>Release Date: 2020-07-15</p> <p>Fix Resolution (lodash): 4.17.19</p> <p>Direct dependency fix Resolution (snyk): 1.291.0</p> </p> <p></p> :rescue_worker_helmet: Automatic Remediation is available for this issue </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2022-48285</summary> ### Vulnerable Library - <b>jszip-3.2.2.tgz</b></p> <p>Create, read and edit .zip files with JavaScript http://stuartk.com/jszip</p> <p>Library home page: <a href="https://registry.npmjs.org/jszip/-/jszip-3.2.2.tgz">https://registry.npmjs.org/jszip/-/jszip-3.2.2.tgz</a></p> <p>Path to dependency file: /package.json</p> <p>Path to vulnerable library: /node_modules/jszip/package.json</p> <p> Dependency Hierarchy: - snyk-1.290.2.tgz (Root Library) - snyk-nuget-plugin-1.16.0.tgz - :x: jszip-3.2.2.tgz (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/samq-ghdemo/snyk-goof/commit/77eae86d878e3f5b3d008c20fb02ac8f24ee2393">77eae86d878e3f5b3d008c20fb02ac8f24ee2393</a></p> <p>Found in base branch: <b>master</b></p> </p> <p></p> ### Vulnerability Details <p> loadAsync in JSZip before 3.8.0 allows Directory Traversal via a crafted ZIP archive. <p>Publish Date: 2023-01-29 <p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-48285>CVE-2022-48285</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>7.3</b>) <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: Low - Integrity Impact: Low - Availability Impact: Low </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> <p></p> ### Suggested Fix <p> <p>Type: Upgrade version</p> <p>Release Date: 2023-01-29</p> <p>Fix Resolution (jszip): 3.8.0</p> <p>Direct dependency fix Resolution (snyk): 1.291.0</p> </p> <p></p> :rescue_worker_helmet: Automatic Remediation is available for this issue </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2022-0624</summary> ### Vulnerable Library - <b>parse-path-4.0.1.tgz</b></p> <p>Parse paths (local paths, urls: ssh/git/etc)</p> <p>Library home page: <a href="https://registry.npmjs.org/parse-path/-/parse-path-4.0.1.tgz">https://registry.npmjs.org/parse-path/-/parse-path-4.0.1.tgz</a></p> <p>Path to dependency file: /package.json</p> <p>Path to vulnerable library: /node_modules/parse-path/package.json</p> <p> Dependency Hierarchy: - snyk-1.290.2.tgz (Root Library) - git-url-parse-11.1.2.tgz - git-up-4.0.1.tgz - parse-url-5.0.1.tgz - :x: parse-path-4.0.1.tgz (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/samq-ghdemo/snyk-goof/commit/77eae86d878e3f5b3d008c20fb02ac8f24ee2393">77eae86d878e3f5b3d008c20fb02ac8f24ee2393</a></p> <p>Found in base branch: <b>master</b></p> </p> <p></p> ### Vulnerability Details <p> Authorization Bypass Through User-Controlled Key in GitHub repository ionicabizau/parse-path prior to 5.0.0. <p>Publish Date: 2022-06-28 <p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-0624>CVE-2022-0624</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>7.3</b>) <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: Low - Integrity Impact: Low - Availability Impact: Low </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-2022-0624">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-0624</a></p> <p>Release Date: 2022-06-28</p> <p>Fix Resolution (parse-path): 6.0.0</p> <p>Direct dependency fix Resolution (snyk): 1.324.0</p> </p> <p></p> :rescue_worker_helmet: Automatic Remediation is available for this issue </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2021-23337</summary> ### Vulnerable Library - <b>lodash-4.17.15.tgz</b></p> <p>Lodash modular utilities.</p> <p>Library home page: <a href="https://registry.npmjs.org/lodash/-/lodash-4.17.15.tgz">https://registry.npmjs.org/lodash/-/lodash-4.17.15.tgz</a></p> <p>Path to dependency file: /package.json</p> <p>Path to vulnerable library: /node_modules/snyk/node_modules/lodash/package.json,/node_modules/snyk-nodejs-lockfile-parser/node_modules/lodash/package.json,/node_modules/snyk-config/node_modules/lodash/package.json,/node_modules/@snyk/ruby-semver/node_modules/lodash/package.json,/node_modules/snyk-nuget-plugin/node_modules/lodash/package.json,/node_modules/inquirer/node_modules/lodash/package.json,/node_modules/graphlib/node_modules/lodash/package.json,/node_modules/snyk-mvn-plugin/node_modules/lodash/package.json,/node_modules/dotnet-deps-parser/node_modules/lodash/package.json,/node_modules/@snyk/composer-lockfile-parser/node_modules/lodash/package.json</p> <p> Dependency Hierarchy: - snyk-1.290.2.tgz (Root Library) - :x: lodash-4.17.15.tgz (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/samq-ghdemo/snyk-goof/commit/77eae86d878e3f5b3d008c20fb02ac8f24ee2393">77eae86d878e3f5b3d008c20fb02ac8f24ee2393</a></p> <p>Found in base branch: <b>master</b></p> </p> <p></p> ### Vulnerability Details <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://www.mend.io/vulnerability-database/CVE-2021-23337>CVE-2021-23337</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>7.2</b>) <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> <p></p> ### Suggested Fix <p> <p>Type: Upgrade version</p> <p>Release Date: 2021-02-15</p> <p>Fix Resolution (lodash): 4.17.21</p> <p>Direct dependency fix Resolution (snyk): 1.291.0</p> </p> <p></p> :rescue_worker_helmet: Automatic Remediation is available for this issue </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2020-8244</summary> ### Vulnerable Library - <b>bl-3.0.0.tgz</b></p> <p>Buffer List: collect buffers and access with a standard readable Buffer interface, streamable too!</p> <p>Library home page: <a href="https://registry.npmjs.org/bl/-/bl-3.0.0.tgz">https://registry.npmjs.org/bl/-/bl-3.0.0.tgz</a></p> <p>Path to dependency file: /package.json</p> <p>Path to vulnerable library: /node_modules/tar-stream/node_modules/bl/package.json</p> <p> Dependency Hierarchy: - snyk-1.290.2.tgz (Root Library) - snyk-docker-plugin-1.38.0.tgz - tar-stream-2.1.0.tgz - :x: bl-3.0.0.tgz (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/samq-ghdemo/snyk-goof/commit/77eae86d878e3f5b3d008c20fb02ac8f24ee2393">77eae86d878e3f5b3d008c20fb02ac8f24ee2393</a></p> <p>Found in base branch: <b>master</b></p> </p> <p></p> ### Vulnerability Details <p> A buffer over-read vulnerability exists in bl <4.0.3, <3.0.1, <2.2.1, and <1.2.3 which could allow an attacker to supply user input (even typed) that if it ends up in consume() argument and can become negative, the BufferList state can be corrupted, tricking it into exposing uninitialized memory via regular .slice() calls. <p>Publish Date: 2020-08-30 <p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2020-8244>CVE-2020-8244</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>6.5</b>) <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: Low - Integrity Impact: None - Availability Impact: Low </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> <p></p> ### Suggested Fix <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://github.com/advisories/GHSA-pp7h-53gx-mx7r">https://github.com/advisories/GHSA-pp7h-53gx-mx7r</a></p> <p>Release Date: 2020-08-30</p> <p>Fix Resolution (bl): 3.0.1</p> <p>Direct dependency fix Resolution (snyk): 1.291.0</p> </p> <p></p> :rescue_worker_helmet: Automatic Remediation is available for this issue </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2022-22984</summary> ### Vulnerable Libraries - <b>snyk-cocoapods-plugin-2.0.1.tgz</b>, <b>snyk-gradle-plugin-3.2.4.tgz</b>, <b>snyk-docker-plugin-1.38.0.tgz</b>, <b>snyk-sbt-plugin-2.11.0.tgz</b>, <b>snyk-1.290.2.tgz</b>, <b>snyk-python-plugin-1.17.0.tgz</b>, <b>snyk-mvn-plugin-2.8.0.tgz</b></p> <p> ### <b>snyk-cocoapods-plugin-2.0.1.tgz</b></p> <p>Snyk CLI CocoaPods plugin</p> <p>Library home page: <a href="https://registry.npmjs.org/@snyk/snyk-cocoapods-plugin/-/snyk-cocoapods-plugin-2.0.1.tgz">https://registry.npmjs.org/@snyk/snyk-cocoapods-plugin/-/snyk-cocoapods-plugin-2.0.1.tgz</a></p> <p>Path to dependency file: /package.json</p> <p>Path to vulnerable library: /node_modules/@snyk/snyk-cocoapods-plugin/package.json</p> <p> Dependency Hierarchy: - snyk-1.290.2.tgz (Root Library) - :x: snyk-cocoapods-plugin-2.0.1.tgz (Vulnerable Library) ### <b>snyk-gradle-plugin-3.2.4.tgz</b></p> <p>Snyk CLI Gradle plugin</p> <p>Library home page: <a href="https://registry.npmjs.org/snyk-gradle-plugin/-/snyk-gradle-plugin-3.2.4.tgz">https://registry.npmjs.org/snyk-gradle-plugin/-/snyk-gradle-plugin-3.2.4.tgz</a></p> <p>Path to dependency file: /package.json</p> <p>Path to vulnerable library: /node_modules/snyk-gradle-plugin/package.json</p> <p> Dependency Hierarchy: - snyk-1.290.2.tgz (Root Library) - :x: snyk-gradle-plugin-3.2.4.tgz (Vulnerable Library) ### <b>snyk-docker-plugin-1.38.0.tgz</b></p> <p>Snyk CLI docker plugin</p> <p>Library home page: <a href="https://registry.npmjs.org/snyk-docker-plugin/-/snyk-docker-plugin-1.38.0.tgz">https://registry.npmjs.org/snyk-docker-plugin/-/snyk-docker-plugin-1.38.0.tgz</a></p> <p>Path to dependency file: /package.json</p> <p>Path to vulnerable library: /node_modules/snyk-docker-plugin/package.json</p> <p> Dependency Hierarchy: - snyk-1.290.2.tgz (Root Library) - :x: snyk-docker-plugin-1.38.0.tgz (Vulnerable Library) ### <b>snyk-sbt-plugin-2.11.0.tgz</b></p> <p>Snyk CLI SBT plugin</p> <p>Library home page: <a href="https://registry.npmjs.org/snyk-sbt-plugin/-/snyk-sbt-plugin-2.11.0.tgz">https://registry.npmjs.org/snyk-sbt-plugin/-/snyk-sbt-plugin-2.11.0.tgz</a></p> <p>Path to dependency file: /package.json</p> <p>Path to vulnerable library: /node_modules/snyk-sbt-plugin/package.json</p> <p> Dependency Hierarchy: - snyk-1.290.2.tgz (Root Library) - :x: snyk-sbt-plugin-2.11.0.tgz (Vulnerable Library) ### <b>snyk-1.290.2.tgz</b></p> <p>snyk library and cli utility</p> <p>Library home page: <a href="https://registry.npmjs.org/snyk/-/snyk-1.290.2.tgz">https://registry.npmjs.org/snyk/-/snyk-1.290.2.tgz</a></p> <p>Path to dependency file: /package.json</p> <p>Path to vulnerable library: /node_modules/snyk/package.json</p> <p> Dependency Hierarchy: - :x: snyk-1.290.2.tgz (Vulnerable Library) ### <b>snyk-python-plugin-1.17.0.tgz</b></p> <p>Snyk CLI Python plugin</p> <p>Library home page: <a href="https://registry.npmjs.org/snyk-python-plugin/-/snyk-python-plugin-1.17.0.tgz">https://registry.npmjs.org/snyk-python-plugin/-/snyk-python-plugin-1.17.0.tgz</a></p> <p>Path to dependency file: /package.json</p> <p>Path to vulnerable library: /node_modules/snyk-python-plugin/package.json</p> <p> Dependency Hierarchy: - snyk-1.290.2.tgz (Root Library) - :x: snyk-python-plugin-1.17.0.tgz (Vulnerable Library) ### <b>snyk-mvn-plugin-2.8.0.tgz</b></p> <p>Snyk CLI Maven plugin</p> <p>Library home page: <a href="https://registry.npmjs.org/snyk-mvn-plugin/-/snyk-mvn-plugin-2.8.0.tgz">https://registry.npmjs.org/snyk-mvn-plugin/-/snyk-mvn-plugin-2.8.0.tgz</a></p> <p>Path to dependency file: /package.json</p> <p>Path to vulnerable library: /node_modules/snyk-mvn-plugin/package.json</p> <p> Dependency Hierarchy: - snyk-1.290.2.tgz (Root Library) - :x: snyk-mvn-plugin-2.8.0.tgz (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/samq-ghdemo/snyk-goof/commit/77eae86d878e3f5b3d008c20fb02ac8f24ee2393">77eae86d878e3f5b3d008c20fb02ac8f24ee2393</a></p> <p>Found in base branch: <b>master</b></p> </p> <p></p> ### Vulnerability Details <p> The package snyk before 1.1064.0; the package snyk-mvn-plugin before 2.31.3; the package snyk-gradle-plugin before 3.24.5; the package @snyk/snyk-cocoapods-plugin before 2.5.3; the package snyk-sbt-plugin before 2.16.2; the package snyk-python-plugin before 1.24.2; the package snyk-docker-plugin before 5.6.5; the package @snyk/snyk-hex-plugin before 1.1.6 are vulnerable to Command Injection due to an incomplete fix for [CVE-2022-40764](https://security.snyk.io/vuln/SNYK-JS-SNYK-3037342). A successful exploit allows attackers to run arbitrary commands on the host system where the Snyk CLI is installed by passing in crafted command line flags. In order to exploit this vulnerability, a user would have to execute the snyk test command on untrusted files. In most cases, an attacker positioned to control the command line arguments to the Snyk CLI would already be positioned to execute arbitrary commands. However, this could be abused in specific scenarios, such as continuous integration pipelines, where developers can control the arguments passed to the Snyk CLI to leverage this component as part of a wider attack against an integration/build pipeline. This issue has been addressed in the latest Snyk Docker images available at https://hub.docker.com/r/snyk/snyk as of 2022-11-29. Images downloaded and built prior to that date should be updated. The issue has also been addressed in the Snyk TeamCity CI/CD plugin as of version v20221130.093605. <p>Publish Date: 2022-11-30 <p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-22984>CVE-2022-22984</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>6.3</b>) <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: Low - 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> <p></p> ### Suggested Fix <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://www.cve.org/CVERecord?id=CVE-2022-22984">https://www.cve.org/CVERecord?id=CVE-2022-22984</a></p> <p>Release Date: 2022-11-30</p> <p>Fix Resolution (snyk-gradle-plugin): 3.24.5</p> <p>Direct dependency fix Resolution (snyk): 1.330.1</p><p>Fix Resolution (snyk-docker-plugin): 5.6.5</p> <p>Direct dependency fix Resolution (snyk): 1.685.0</p><p>Fix Resolution (snyk-sbt-plugin): 2.16.2</p> <p>Direct dependency fix Resolution (snyk): 1.685.0</p><p>Fix Resolution (snyk-python-plugin): 1.24.2</p> <p>Direct dependency fix Resolution (snyk): 1.685.0</p><p>Fix Resolution (snyk-mvn-plugin): 2.31.3</p> <p>Direct dependency fix Resolution (snyk): 1.685.0</p> </p> <p></p> :rescue_worker_helmet: Automatic Remediation is available for this issue </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2022-3224</summary> ### Vulnerable Library - <b>parse-url-5.0.1.tgz</b></p> <p>An advanced url parser supporting git urls too.</p> <p>Library home page: <a href="https://registry.npmjs.org/parse-url/-/parse-url-5.0.1.tgz">https://registry.npmjs.org/parse-url/-/parse-url-5.0.1.tgz</a></p> <p>Path to dependency file: /package.json</p> <p>Path to vulnerable library: /node_modules/parse-url/package.json</p> <p> Dependency Hierarchy: - snyk-1.290.2.tgz (Root Library) - git-url-parse-11.1.2.tgz - git-up-4.0.1.tgz - :x: parse-url-5.0.1.tgz (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/samq-ghdemo/snyk-goof/commit/77eae86d878e3f5b3d008c20fb02ac8f24ee2393">77eae86d878e3f5b3d008c20fb02ac8f24ee2393</a></p> <p>Found in base branch: <b>master</b></p> </p> <p></p> ### Vulnerability Details <p> Misinterpretation of Input in GitHub repository ionicabizau/parse-url prior to 8.1.0. <p>Publish Date: 2022-09-15 <p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-3224>CVE-2022-3224</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>6.1</b>) <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: Required - Scope: Changed - Impact Metrics: - Confidentiality Impact: Low - Integrity Impact: Low - Availability Impact: None </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> <p></p> ### Suggested Fix <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-3224">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-3224</a></p> <p>Release Date: 2022-09-15</p> <p>Fix Resolution: parse-url - 8.1.0</p> </p> <p></p> </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2022-2217</summary> ### Vulnerable Library - <b>parse-url-5.0.1.tgz</b></p> <p>An advanced url parser supporting git urls too.</p> <p>Library home page: <a href="https://registry.npmjs.org/parse-url/-/parse-url-5.0.1.tgz">https://registry.npmjs.org/parse-url/-/parse-url-5.0.1.tgz</a></p> <p>Path to dependency file: /package.json</p> <p>Path to vulnerable library: /node_modules/parse-url/package.json</p> <p> Dependency Hierarchy: - snyk-1.290.2.tgz (Root Library) - git-url-parse-11.1.2.tgz - git-up-4.0.1.tgz - :x: parse-url-5.0.1.tgz (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/samq-ghdemo/snyk-goof/commit/77eae86d878e3f5b3d008c20fb02ac8f24ee2393">77eae86d878e3f5b3d008c20fb02ac8f24ee2393</a></p> <p>Found in base branch: <b>master</b></p> </p> <p></p> ### Vulnerability Details <p> Cross-site Scripting (XSS) - Generic in GitHub repository ionicabizau/parse-url prior to 7.0.0. <p>Publish Date: 2022-06-27 <p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-2217>CVE-2022-2217</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>6.1</b>) <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: Required - Scope: Changed - Impact Metrics: - Confidentiality Impact: Low - Integrity Impact: Low - Availability Impact: None </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> <p></p> ### Suggested Fix <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://huntr.dev/bounties/4e046c63-b1ca-4bcc-b418-29796918a71b/">https://huntr.dev/bounties/4e046c63-b1ca-4bcc-b418-29796918a71b/</a></p> <p>Release Date: 2022-06-27</p> <p>Fix Resolution (parse-url): 6.0.3</p> <p>Direct dependency fix Resolution (snyk): 1.291.0</p> </p> <p></p> :rescue_worker_helmet: Automatic Remediation is available for this issue </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2022-2218</summary> ### Vulnerable Library - <b>parse-url-5.0.1.tgz</b></p> <p>An advanced url parser supporting git urls too.</p> <p>Library home page: <a href="https://registry.npmjs.org/parse-url/-/parse-url-5.0.1.tgz">https://registry.npmjs.org/parse-url/-/parse-url-5.0.1.tgz</a></p> <p>Path to dependency file: /package.json</p> <p>Path to vulnerable library: /node_modules/parse-url/package.json</p> <p> Dependency Hierarchy: - snyk-1.290.2.tgz (Root Library) - git-url-parse-11.1.2.tgz - git-up-4.0.1.tgz - :x: parse-url-5.0.1.tgz (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/samq-ghdemo/snyk-goof/commit/77eae86d878e3f5b3d008c20fb02ac8f24ee2393">77eae86d878e3f5b3d008c20fb02ac8f24ee2393</a></p> <p>Found in base branch: <b>master</b></p> </p> <p></p> ### Vulnerability Details <p> Cross-site Scripting (XSS) - Stored in GitHub repository ionicabizau/parse-url prior to 7.0.0. <p>Publish Date: 2022-06-27 <p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-2218>CVE-2022-2218</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>6.1</b>) <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: Required - Scope: Changed - Impact Metrics: - Confidentiality Impact: Low - Integrity Impact: Low - Availability Impact: None </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> <p></p> ### Suggested Fix <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://huntr.dev/bounties/024912d3-f103-4daf-a1d0-567f4d9f2bf5/">https://huntr.dev/bounties/024912d3-f103-4daf-a1d0-567f4d9f2bf5/</a></p> <p>Release Date: 2022-06-27</p> <p>Fix Resolution (parse-url): 6.0.3</p> <p>Direct dependency fix Resolution (snyk): 1.291.0</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	snyk-1.290.2.tgz: 28 vulnerabilities (highest severity is: 9.8) - <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>snyk-1.290.2.tgz</b></p></summary> <p>snyk library and cli utility</p> <p>Library home page: <a href="https://registry.npmjs.org/snyk/-/snyk-1.290.2.tgz">https://registry.npmjs.org/snyk/-/snyk-1.290.2.tgz</a></p> <p>Path to dependency file: /package.json</p> <p>Path to vulnerable library: /node_modules/snyk/package.json</p> <p> <p>Found in HEAD commit: <a href="https://github.com/samq-ghdemo/snyk-goof/commit/77eae86d878e3f5b3d008c20fb02ac8f24ee2393">77eae86d878e3f5b3d008c20fb02ac8f24ee2393</a></p></details> ## Vulnerabilities \| CVE \| Severity \| <img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS \| Dependency \| Type \| Fixed in (snyk version) \| Remediation Available \| \| ------------- \| ------------- \| ----- \| ----- \| ----- \| ------------- \| --- \| \| [CVE-2021-23406](https://www.mend.io/vulnerability-database/CVE-2021-23406) \| <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High \| 9.8 \| detected in multiple dependencies \| Transitive \| 1.518.0 \| ✅ \| \| [CVE-2022-2216](https://www.mend.io/vulnerability-database/CVE-2022-2216) \| <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High \| 9.8 \| parse-url-5.0.1.tgz \| Transitive \| 1.291.0 \| ✅ \| \| [CVE-2020-7774](https://www.mend.io/vulnerability-database/CVE-2020-7774) \| <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High \| 9.8 \| y18n-3.2.1.tgz \| Transitive \| 1.291.0 \| ✅ \| \| [CVE-2021-28918](https://www.mend.io/vulnerability-database/CVE-2021-28918) \| <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High \| 9.1 \| netmask-1.0.6.tgz \| Transitive \| 1.518.0 \| ✅ \| \| [CVE-2022-2900](https://www.mend.io/vulnerability-database/CVE-2022-2900) \| <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High \| 9.1 \| parse-url-5.0.1.tgz \| Transitive \| 1.324.0 \| ✅ \| \| [CVE-2022-24441](https://www.mend.io/vulnerability-database/CVE-2022-24441) \| <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High \| 8.8 \| snyk-1.290.2.tgz \| Direct \| 1.1064.0 \| ✅ \| \| [CVE-2022-40764](https://www.mend.io/vulnerability-database/CVE-2022-40764) \| <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High \| 7.8 \| snyk-1.290.2.tgz \| Direct \| 1.996.0 \| ✅ \| \| [CVE-2021-3807](https://www.mend.io/vulnerability-database/CVE-2021-3807) \| <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High \| 7.5 \| detected in multiple dependencies \| Transitive \| 1.685.0 \| ✅ \| \| [CVE-2022-3517](https://www.mend.io/vulnerability-database/CVE-2022-3517) \| <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High \| 7.5 \| minimatch-3.0.4.tgz \| Transitive \| N/A* \| ❌ \| \| [CVE-2022-0722](https://www.mend.io/vulnerability-database/CVE-2022-0722) \| <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High \| 7.5 \| parse-url-5.0.1.tgz \| Transitive \| 1.291.0 \| ✅ \| \| [CVE-2022-21803](https://www.mend.io/vulnerability-database/CVE-2022-21803) \| <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High \| 7.5 \| nconf-0.10.0.tgz \| Transitive \| 1.425.4 \| ✅ \| \| [WS-2022-0237](https://github.com/ionicabizau/parse-url/commit/b88c81df8f4c5168af454eaa4f92afa9349e4e13) \| <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High \| 7.5 \| parse-url-5.0.1.tgz \| Transitive \| 1.324.0 \| ✅ \| \| [WS-2022-0238](https://huntr.dev/bounties/52060edb-e426-431b-a0d0-e70407e44f18/) \| <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High \| 7.5 \| parse-url-5.0.1.tgz \| Transitive \| 1.324.0 \| ✅ \| \| [CVE-2020-8203](https://www.mend.io/vulnerability-database/CVE-2020-8203) \| <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High \| 7.4 \| lodash-4.17.15.tgz \| Transitive \| 1.291.0 \| ✅ \| \| [CVE-2022-48285](https://www.mend.io/vulnerability-database/CVE-2022-48285) \| <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High \| 7.3 \| jszip-3.2.2.tgz \| Transitive \| 1.291.0 \| ✅ \| \| [CVE-2022-0624](https://www.mend.io/vulnerability-database/CVE-2022-0624) \| <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High \| 7.3 \| parse-path-4.0.1.tgz \| Transitive \| 1.324.0 \| ✅ \| \| [CVE-2021-23337](https://www.mend.io/vulnerability-database/CVE-2021-23337) \| <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High \| 7.2 \| lodash-4.17.15.tgz \| Transitive \| 1.291.0 \| ✅ \| \| [CVE-2020-8244](https://www.mend.io/vulnerability-database/CVE-2020-8244) \| <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium \| 6.5 \| bl-3.0.0.tgz \| Transitive \| 1.291.0 \| ✅ \| \| [CVE-2022-22984](https://www.mend.io/vulnerability-database/CVE-2022-22984) \| <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium \| 6.3 \| detected in multiple dependencies \| Transitive \| 1.330.1 \| ✅ \| \| [CVE-2022-3224](https://www.mend.io/vulnerability-database/CVE-2022-3224) \| <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium \| 6.1 \| parse-url-5.0.1.tgz \| Transitive \| N/A* \| ❌ \| \| [CVE-2022-2217](https://www.mend.io/vulnerability-database/CVE-2022-2217) \| <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium \| 6.1 \| parse-url-5.0.1.tgz \| Transitive \| 1.291.0 \| ✅ \| \| [CVE-2022-2218](https://www.mend.io/vulnerability-database/CVE-2022-2218) \| <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium \| 6.1 \| parse-url-5.0.1.tgz \| Transitive \| 1.291.0 \| ✅ \| \| [WS-2022-0239](https://github.com/ionicabizau/parse-url/commit/b88c81df8f4c5168af454eaa4f92afa9349e4e13) \| <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium \| 6.1 \| parse-url-5.0.1.tgz \| Transitive \| 1.324.0 \| ✅ \| \| [CVE-2020-28500](https://www.mend.io/vulnerability-database/CVE-2020-28500) \| <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium \| 5.3 \| lodash-4.17.15.tgz \| Transitive \| 1.291.0 \| ✅ \| \| [CVE-2021-29418](https://www.mend.io/vulnerability-database/CVE-2021-29418) \| <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium \| 5.3 \| netmask-1.0.6.tgz \| Transitive \| 1.518.0 \| ✅ \| \| [CVE-2021-23413](https://www.mend.io/vulnerability-database/CVE-2021-23413) \| <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium \| 5.3 \| jszip-3.2.2.tgz \| Transitive \| 1.291.0 \| ✅ \| \| [CVE-2022-33987](https://www.mend.io/vulnerability-database/CVE-2022-33987) \| <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium \| 5.3 \| got-6.7.1.tgz \| Transitive \| 1.685.0 \| ✅ \| \| [CVE-2021-23362](https://www.mend.io/vulnerability-database/CVE-2021-23362) \| <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium \| 5.3 \| hosted-git-info-2.8.5.tgz \| Transitive \| 1.291.0 \| ✅ \| <p>For some transitive vulnerabilities, there is no version of direct dependency with a fix. Check the section "Details" below to see if there is a version of transitive dependency where vulnerability is fixed.</p> ## Details > Partial details (22 vulnerabilities) are displayed below due to a content size limitation in GitHub. To view information on the remaining vulnerabilities, navigate to the Mend Application.<br> <details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2021-23406</summary> ### Vulnerable Libraries - <b>pac-resolver-3.0.0.tgz</b>, <b>degenerator-1.0.4.tgz</b></p> <p> ### <b>pac-resolver-3.0.0.tgz</b></p> <p>Generates an asynchronous resolver function from a PAC file</p> <p>Library home page: <a href="https://registry.npmjs.org/pac-resolver/-/pac-resolver-3.0.0.tgz">https://registry.npmjs.org/pac-resolver/-/pac-resolver-3.0.0.tgz</a></p> <p>Path to dependency file: /package.json</p> <p>Path to vulnerable library: /node_modules/pac-resolver/package.json</p> <p> Dependency Hierarchy: - snyk-1.290.2.tgz (Root Library) - proxy-agent-3.1.1.tgz - pac-proxy-agent-3.0.1.tgz - :x: pac-resolver-3.0.0.tgz* (Vulnerable Library) ### <b>degenerator-1.0.4.tgz</b></p> <p>Turns sync functions into async generator functions</p> <p>Library home page: <a href="https://registry.npmjs.org/degenerator/-/degenerator-1.0.4.tgz">https://registry.npmjs.org/degenerator/-/degenerator-1.0.4.tgz</a></p> <p>Path to dependency file: /package.json</p> <p>Path to vulnerable library: /node_modules/degenerator/package.json</p> <p> Dependency Hierarchy: - snyk-1.290.2.tgz (Root Library) - proxy-agent-3.1.1.tgz - pac-proxy-agent-3.0.1.tgz - pac-resolver-3.0.0.tgz - :x: degenerator-1.0.4.tgz (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/samq-ghdemo/snyk-goof/commit/77eae86d878e3f5b3d008c20fb02ac8f24ee2393">77eae86d878e3f5b3d008c20fb02ac8f24ee2393</a></p> <p>Found in base branch: <b>master</b></p> </p> <p></p> ### Vulnerability Details <p> This affects the package pac-resolver before 5.0.0. This can occur when used with untrusted input, due to unsafe PAC file handling. NOTE: The fix for this vulnerability is applied in the node-degenerator library, a dependency written by the same maintainer. <p>Publish Date: 2021-08-24 <p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2021-23406>CVE-2021-23406</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>9.8</b>) <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: High - Integrity Impact: High - Availability Impact: High </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> <p></p> ### Suggested Fix <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://github.com/advisories/GHSA-9j49-mfvp-vmhm">https://github.com/advisories/GHSA-9j49-mfvp-vmhm</a></p> <p>Release Date: 2021-08-24</p> <p>Fix Resolution (pac-resolver): 5.0.0</p> <p>Direct dependency fix Resolution (snyk): 1.518.0</p><p>Fix Resolution (degenerator): 3.0.1</p> <p>Direct dependency fix Resolution (snyk): 1.518.0</p> </p> <p></p> :rescue_worker_helmet: Automatic Remediation is available for this issue </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2022-2216</summary> ### Vulnerable Library - <b>parse-url-5.0.1.tgz</b></p> <p>An advanced url parser supporting git urls too.</p> <p>Library home page: <a href="https://registry.npmjs.org/parse-url/-/parse-url-5.0.1.tgz">https://registry.npmjs.org/parse-url/-/parse-url-5.0.1.tgz</a></p> <p>Path to dependency file: /package.json</p> <p>Path to vulnerable library: /node_modules/parse-url/package.json</p> <p> Dependency Hierarchy: - snyk-1.290.2.tgz (Root Library) - git-url-parse-11.1.2.tgz - git-up-4.0.1.tgz - :x: parse-url-5.0.1.tgz (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/samq-ghdemo/snyk-goof/commit/77eae86d878e3f5b3d008c20fb02ac8f24ee2393">77eae86d878e3f5b3d008c20fb02ac8f24ee2393</a></p> <p>Found in base branch: <b>master</b></p> </p> <p></p> ### Vulnerability Details <p> Server-Side Request Forgery (SSRF) in GitHub repository ionicabizau/parse-url prior to 7.0.0. <p>Publish Date: 2022-06-27 <p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-2216>CVE-2022-2216</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>9.8</b>) <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: High - Integrity Impact: High - Availability Impact: High </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> <p></p> ### Suggested Fix <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://huntr.dev/bounties/505a3d39-2723-4a06-b1f7-9b2d133c92e1/">https://huntr.dev/bounties/505a3d39-2723-4a06-b1f7-9b2d133c92e1/</a></p> <p>Release Date: 2022-06-27</p> <p>Fix Resolution (parse-url): 6.0.3</p> <p>Direct dependency fix Resolution (snyk): 1.291.0</p> </p> <p></p> :rescue_worker_helmet: Automatic Remediation is available for this issue </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2020-7774</summary> ### Vulnerable Library - <b>y18n-3.2.1.tgz</b></p> <p>the bare-bones internationalization library used by yargs</p> <p>Library home page: <a href="https://registry.npmjs.org/y18n/-/y18n-3.2.1.tgz">https://registry.npmjs.org/y18n/-/y18n-3.2.1.tgz</a></p> <p>Path to dependency file: /package.json</p> <p>Path to vulnerable library: /node_modules/nyc/node_modules/yargs/node_modules/y18n/package.json,/node_modules/y18n/package.json</p> <p> Dependency Hierarchy: - snyk-1.290.2.tgz (Root Library) - snyk-config-2.2.3.tgz - nconf-0.10.0.tgz - yargs-3.32.0.tgz - :x: y18n-3.2.1.tgz (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/samq-ghdemo/snyk-goof/commit/77eae86d878e3f5b3d008c20fb02ac8f24ee2393">77eae86d878e3f5b3d008c20fb02ac8f24ee2393</a></p> <p>Found in base branch: <b>master</b></p> </p> <p></p> ### Vulnerability Details <p> The package y18n before 3.2.2, 4.0.1 and 5.0.5, is vulnerable to Prototype Pollution. <p>Publish Date: 2020-11-17 <p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2020-7774>CVE-2020-7774</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>9.8</b>) <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: High - Integrity Impact: High - Availability Impact: High </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> <p></p> ### Suggested Fix <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://www.npmjs.com/advisories/1654">https://www.npmjs.com/advisories/1654</a></p> <p>Release Date: 2020-11-17</p> <p>Fix Resolution (y18n): 3.2.2</p> <p>Direct dependency fix Resolution (snyk): 1.291.0</p> </p> <p></p> :rescue_worker_helmet: Automatic Remediation is available for this issue </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2021-28918</summary> ### Vulnerable Library - <b>netmask-1.0.6.tgz</b></p> <p>Parse and lookup IP network blocks</p> <p>Library home page: <a href="https://registry.npmjs.org/netmask/-/netmask-1.0.6.tgz">https://registry.npmjs.org/netmask/-/netmask-1.0.6.tgz</a></p> <p>Path to dependency file: /package.json</p> <p>Path to vulnerable library: /node_modules/netmask/package.json</p> <p> Dependency Hierarchy: - snyk-1.290.2.tgz (Root Library) - proxy-agent-3.1.1.tgz - pac-proxy-agent-3.0.1.tgz - pac-resolver-3.0.0.tgz - :x: netmask-1.0.6.tgz (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/samq-ghdemo/snyk-goof/commit/77eae86d878e3f5b3d008c20fb02ac8f24ee2393">77eae86d878e3f5b3d008c20fb02ac8f24ee2393</a></p> <p>Found in base branch: <b>master</b></p> </p> <p></p> ### Vulnerability Details <p> Improper input validation of octal strings in netmask npm package v1.0.6 and below allows unauthenticated remote attackers to perform indeterminate SSRF, RFI, and LFI attacks on many of the dependent packages. A remote unauthenticated attacker can bypass packages relying on netmask to filter IPs and reach critical VPN or LAN hosts. <p>Publish Date: 2021-04-01 <p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2021-28918>CVE-2021-28918</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>9.1</b>) <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: High - Integrity Impact: High - Availability Impact: 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://github.com/advisories/GHSA-pch5-whg9-qr2r">https://github.com/advisories/GHSA-pch5-whg9-qr2r</a></p> <p>Release Date: 2021-04-01</p> <p>Fix Resolution (netmask): 2.0.1</p> <p>Direct dependency fix Resolution (snyk): 1.518.0</p> </p> <p></p> :rescue_worker_helmet: Automatic Remediation is available for this issue </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2022-2900</summary> ### Vulnerable Library - <b>parse-url-5.0.1.tgz</b></p> <p>An advanced url parser supporting git urls too.</p> <p>Library home page: <a href="https://registry.npmjs.org/parse-url/-/parse-url-5.0.1.tgz">https://registry.npmjs.org/parse-url/-/parse-url-5.0.1.tgz</a></p> <p>Path to dependency file: /package.json</p> <p>Path to vulnerable library: /node_modules/parse-url/package.json</p> <p> Dependency Hierarchy: - snyk-1.290.2.tgz (Root Library) - git-url-parse-11.1.2.tgz - git-up-4.0.1.tgz - :x: parse-url-5.0.1.tgz (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/samq-ghdemo/snyk-goof/commit/77eae86d878e3f5b3d008c20fb02ac8f24ee2393">77eae86d878e3f5b3d008c20fb02ac8f24ee2393</a></p> <p>Found in base branch: <b>master</b></p> </p> <p></p> ### Vulnerability Details <p> Server-Side Request Forgery (SSRF) in GitHub repository ionicabizau/parse-url prior to 8.1.0. <p>Publish Date: 2022-09-14 <p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-2900>CVE-2022-2900</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>9.1</b>) <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: High - Integrity Impact: High - Availability Impact: 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>Release Date: 2022-09-14</p> <p>Fix Resolution (parse-url): 8.0.0</p> <p>Direct dependency fix Resolution (snyk): 1.324.0</p> </p> <p></p> :rescue_worker_helmet: Automatic Remediation is available for this issue </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2022-24441</summary> ### Vulnerable Library - <b>snyk-1.290.2.tgz</b></p> <p>snyk library and cli utility</p> <p>Library home page: <a href="https://registry.npmjs.org/snyk/-/snyk-1.290.2.tgz">https://registry.npmjs.org/snyk/-/snyk-1.290.2.tgz</a></p> <p>Path to dependency file: /package.json</p> <p>Path to vulnerable library: /node_modules/snyk/package.json</p> <p> Dependency Hierarchy: - :x: snyk-1.290.2.tgz (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/samq-ghdemo/snyk-goof/commit/77eae86d878e3f5b3d008c20fb02ac8f24ee2393">77eae86d878e3f5b3d008c20fb02ac8f24ee2393</a></p> <p>Found in base branch: <b>master</b></p> </p> <p></p> ### Vulnerability Details <p> The package snyk before 1.1064.0 are vulnerable to Code Injection when analyzing a project. An attacker who can convince a user to scan a malicious project can include commands in a build file such as build.gradle or gradle-wrapper.jar, which will be executed with the privileges of the application. This vulnerability may be triggered when running the the CLI tool directly, or when running a scan with one of the IDE plugins that invoke the Snyk CLI. Successful exploitation of this issue would likely require some level of social engineering - to coerce an untrusted project to be downloaded and analyzed via the Snyk CLI or opened in an IDE where a Snyk IDE plugin is installed and enabled. Additionally, if the IDE has a Trust feature then the target folder must be marked as ‘trusted’ in order to be vulnerable. NOTE: This issue is independent of the one reported in [CVE-2022-40764](https://security.snyk.io/vuln/SNYK-JS-SNYK-3037342), and upgrading to a fixed version for this addresses that issue as well. The affected IDE plugins and versions are: - VS Code - Affected: <=1.8.0, Fixed: 1.9.0 - IntelliJ - Affected: <=2.4.47, Fixed: 2.4.48 - Visual Studio - Affected: <=1.1.30, Fixed: 1.1.31 - Eclipse - Affected: <=v20221115.132308, Fixed: All subsequent versions - Language Server - Affected: <=v20221109.114426, Fixed: All subsequent versions <p>Publish Date: 2022-11-30 <p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-24441>CVE-2022-24441</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>8.8</b>) <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: Required - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: High - Integrity Impact: High - Availability Impact: High </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> <p></p> ### Suggested Fix <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://www.cve.org/CVERecord?id=CVE-2022-24441">https://www.cve.org/CVERecord?id=CVE-2022-24441</a></p> <p>Release Date: 2022-11-30</p> <p>Fix Resolution: 1.1064.0</p> </p> <p></p> :rescue_worker_helmet: Automatic Remediation is available for this issue </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2022-40764</summary> ### Vulnerable Library - <b>snyk-1.290.2.tgz</b></p> <p>snyk library and cli utility</p> <p>Library home page: <a href="https://registry.npmjs.org/snyk/-/snyk-1.290.2.tgz">https://registry.npmjs.org/snyk/-/snyk-1.290.2.tgz</a></p> <p>Path to dependency file: /package.json</p> <p>Path to vulnerable library: /node_modules/snyk/package.json</p> <p> Dependency Hierarchy: - :x: snyk-1.290.2.tgz (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/samq-ghdemo/snyk-goof/commit/77eae86d878e3f5b3d008c20fb02ac8f24ee2393">77eae86d878e3f5b3d008c20fb02ac8f24ee2393</a></p> <p>Found in base branch: <b>master</b></p> </p> <p></p> ### Vulnerability Details <p> Snyk CLI before 1.996.0 allows arbitrary command execution, affecting Snyk IDE plugins and the snyk npm package. Exploitation could follow from the common practice of viewing untrusted files in the Visual Studio Code editor, for example. The original demonstration was with shell metacharacters in the vendor.json ignore field, affecting snyk-go-plugin before 1.19.1. This affects, for example, the Snyk TeamCity plugin (which does not update automatically) before 20220930.142957. <p>Publish Date: 2022-10-03 <p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-40764>CVE-2022-40764</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>7.8</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: High - Integrity Impact: High - Availability Impact: High </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> <p></p> ### Suggested Fix <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://github.com/advisories/GHSA-hpqj-7cj6-hfj8">https://github.com/advisories/GHSA-hpqj-7cj6-hfj8</a></p> <p>Release Date: 2022-10-03</p> <p>Fix Resolution: 1.996.0</p> </p> <p></p> :rescue_worker_helmet: Automatic Remediation is available for this issue </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2021-3807</summary> ### Vulnerable Libraries - <b>ansi-regex-4.1.0.tgz</b>, <b>ansi-regex-3.0.0.tgz</b></p> <p> ### <b>ansi-regex-4.1.0.tgz</b></p> <p>Regular expression for matching ANSI escape codes</p> <p>Library home page: <a href="https://registry.npmjs.org/ansi-regex/-/ansi-regex-4.1.0.tgz">https://registry.npmjs.org/ansi-regex/-/ansi-regex-4.1.0.tgz</a></p> <p>Path to dependency file: /package.json</p> <p>Path to vulnerable library: /node_modules/wrap-ansi/node_modules/ansi-regex/package.json,/node_modules/snyk/node_modules/ansi-regex/package.json,/node_modules/inquirer/node_modules/ansi-regex/package.json</p> <p> Dependency Hierarchy: - snyk-1.290.2.tgz (Root Library) - strip-ansi-5.2.0.tgz - :x: ansi-regex-4.1.0.tgz (Vulnerable Library) ### <b>ansi-regex-3.0.0.tgz</b></p> <p>Regular expression for matching ANSI escape codes</p> <p>Library home page: <a href="https://registry.npmjs.org/ansi-regex/-/ansi-regex-3.0.0.tgz">https://registry.npmjs.org/ansi-regex/-/ansi-regex-3.0.0.tgz</a></p> <p>Path to dependency file: /package.json</p> <p>Path to vulnerable library: /node_modules/string-width/node_modules/ansi-regex/package.json</p> <p> Dependency Hierarchy: - snyk-1.290.2.tgz (Root Library) - inquirer-6.5.2.tgz - string-width-2.1.1.tgz - strip-ansi-4.0.0.tgz - :x: ansi-regex-3.0.0.tgz (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/samq-ghdemo/snyk-goof/commit/77eae86d878e3f5b3d008c20fb02ac8f24ee2393">77eae86d878e3f5b3d008c20fb02ac8f24ee2393</a></p> <p>Found in base branch: <b>master</b></p> </p> <p></p> ### Vulnerability Details <p> ansi-regex is vulnerable to Inefficient Regular Expression Complexity <p>Publish Date: 2021-09-17 <p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2021-3807>CVE-2021-3807</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>7.5</b>) <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: None - Integrity Impact: None - Availability Impact: High </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> <p></p> ### Suggested Fix <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://huntr.dev/bounties/5b3cf33b-ede0-4398-9974-800876dfd994/">https://huntr.dev/bounties/5b3cf33b-ede0-4398-9974-800876dfd994/</a></p> <p>Release Date: 2021-09-17</p> <p>Fix Resolution (ansi-regex): 4.1.1</p> <p>Direct dependency fix Resolution (snyk): 1.685.0</p><p>Fix Resolution (ansi-regex): 3.0.1</p> <p>Direct dependency fix Resolution (snyk): 1.291.0</p> </p> <p></p> :rescue_worker_helmet: Automatic Remediation is available for this issue </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2022-3517</summary> ### Vulnerable Library - <b>minimatch-3.0.4.tgz</b></p> <p>a glob matcher in javascript</p> <p>Library home page: <a href="https://registry.npmjs.org/minimatch/-/minimatch-3.0.4.tgz">https://registry.npmjs.org/minimatch/-/minimatch-3.0.4.tgz</a></p> <p>Path to dependency file: /package.json</p> <p>Path to vulnerable library: /node_modules/minimatch/package.json</p> <p> Dependency Hierarchy: - snyk-1.290.2.tgz (Root Library) - glob-7.1.3.tgz - :x: minimatch-3.0.4.tgz (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/samq-ghdemo/snyk-goof/commit/77eae86d878e3f5b3d008c20fb02ac8f24ee2393">77eae86d878e3f5b3d008c20fb02ac8f24ee2393</a></p> <p>Found in base branch: <b>master</b></p> </p> <p></p> ### Vulnerability Details <p> A vulnerability was found in the minimatch package. This flaw allows a Regular Expression Denial of Service (ReDoS) when calling the braceExpand function with specific arguments, resulting in a Denial of Service. <p>Publish Date: 2022-10-17 <p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-3517>CVE-2022-3517</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>7.5</b>) <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: None - Integrity Impact: None - Availability Impact: High </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> <p></p> ### Suggested Fix <p> <p>Type: Upgrade version</p> <p>Release Date: 2022-10-17</p> <p>Fix Resolution: minimatch - 3.0.5</p> </p> <p></p> </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2022-0722</summary> ### Vulnerable Library - <b>parse-url-5.0.1.tgz</b></p> <p>An advanced url parser supporting git urls too.</p> <p>Library home page: <a href="https://registry.npmjs.org/parse-url/-/parse-url-5.0.1.tgz">https://registry.npmjs.org/parse-url/-/parse-url-5.0.1.tgz</a></p> <p>Path to dependency file: /package.json</p> <p>Path to vulnerable library: /node_modules/parse-url/package.json</p> <p> Dependency Hierarchy: - snyk-1.290.2.tgz (Root Library) - git-url-parse-11.1.2.tgz - git-up-4.0.1.tgz - :x: parse-url-5.0.1.tgz (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/samq-ghdemo/snyk-goof/commit/77eae86d878e3f5b3d008c20fb02ac8f24ee2393">77eae86d878e3f5b3d008c20fb02ac8f24ee2393</a></p> <p>Found in base branch: <b>master</b></p> </p> <p></p> ### Vulnerability Details <p> Exposure of Sensitive Information to an Unauthorized Actor in GitHub repository ionicabizau/parse-url prior to 7.0.0. <p>Publish Date: 2022-06-27 <p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-0722>CVE-2022-0722</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>7.5</b>) <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: High - Integrity Impact: None - Availability Impact: None </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> <p></p> ### Suggested Fix <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://huntr.dev/bounties/2490ef6d-5577-4714-a4dd-9608251b4226">https://huntr.dev/bounties/2490ef6d-5577-4714-a4dd-9608251b4226</a></p> <p>Release Date: 2022-06-27</p> <p>Fix Resolution (parse-url): 6.0.3</p> <p>Direct dependency fix Resolution (snyk): 1.291.0</p> </p> <p></p> :rescue_worker_helmet: Automatic Remediation is available for this issue </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2022-21803</summary> ### Vulnerable Library - <b>nconf-0.10.0.tgz</b></p> <p>Hierarchical node.js configuration with files, environment variables, command-line arguments, and atomic object merging.</p> <p>Library home page: <a href="https://registry.npmjs.org/nconf/-/nconf-0.10.0.tgz">https://registry.npmjs.org/nconf/-/nconf-0.10.0.tgz</a></p> <p>Path to dependency file: /package.json</p> <p>Path to vulnerable library: /node_modules/nconf/package.json</p> <p> Dependency Hierarchy: - snyk-1.290.2.tgz (Root Library) - snyk-config-2.2.3.tgz - :x: nconf-0.10.0.tgz (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/samq-ghdemo/snyk-goof/commit/77eae86d878e3f5b3d008c20fb02ac8f24ee2393">77eae86d878e3f5b3d008c20fb02ac8f24ee2393</a></p> <p>Found in base branch: <b>master</b></p> </p> <p></p> ### Vulnerability Details <p> This affects the package nconf before 0.11.4. When using the memory engine, it is possible to store a nested JSON representation of the configuration. The .set() function, that is responsible for setting the configuration properties, is vulnerable to Prototype Pollution. By providing a crafted property, it is possible to modify the properties on the Object.prototype. <p>Publish Date: 2022-04-12 <p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-21803>CVE-2022-21803</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>7.5</b>) <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: None - Integrity Impact: High - Availability Impact: None </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> <p></p> ### Suggested Fix <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-21803">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-21803</a></p> <p>Release Date: 2022-04-12</p> <p>Fix Resolution (nconf): 0.11.4</p> <p>Direct dependency fix Resolution (snyk): 1.425.4</p> </p> <p></p> :rescue_worker_helmet: Automatic Remediation is available for this issue </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> WS-2022-0237</summary> ### Vulnerable Library - <b>parse-url-5.0.1.tgz</b></p> <p>An advanced url parser supporting git urls too.</p> <p>Library home page: <a href="https://registry.npmjs.org/parse-url/-/parse-url-5.0.1.tgz">https://registry.npmjs.org/parse-url/-/parse-url-5.0.1.tgz</a></p> <p>Path to dependency file: /package.json</p> <p>Path to vulnerable library: /node_modules/parse-url/package.json</p> <p> Dependency Hierarchy: - snyk-1.290.2.tgz (Root Library) - git-url-parse-11.1.2.tgz - git-up-4.0.1.tgz - :x: parse-url-5.0.1.tgz (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/samq-ghdemo/snyk-goof/commit/77eae86d878e3f5b3d008c20fb02ac8f24ee2393">77eae86d878e3f5b3d008c20fb02ac8f24ee2393</a></p> <p>Found in base branch: <b>master</b></p> </p> <p></p> ### Vulnerability Details <p> Regular Expression Denial of Service (ReDoS) in ionicabizau/parse-url before 8.0.0. It allows cause a denial of service when calling function parse-url <p>Publish Date: 2022-07-04 <p>URL: <a href=https://github.com/ionicabizau/parse-url/commit/b88c81df8f4c5168af454eaa4f92afa9349e4e13>WS-2022-0237</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>7.5</b>) <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: None - Integrity Impact: None - Availability Impact: High </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> <p></p> ### Suggested Fix <p> <p>Type: Upgrade version</p> <p>Release Date: 2022-07-04</p> <p>Fix Resolution (parse-url): 8.0.0</p> <p>Direct dependency fix Resolution (snyk): 1.324.0</p> </p> <p></p> :rescue_worker_helmet: Automatic Remediation is available for this issue </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> WS-2022-0238</summary> ### Vulnerable Library - <b>parse-url-5.0.1.tgz</b></p> <p>An advanced url parser supporting git urls too.</p> <p>Library home page: <a href="https://registry.npmjs.org/parse-url/-/parse-url-5.0.1.tgz">https://registry.npmjs.org/parse-url/-/parse-url-5.0.1.tgz</a></p> <p>Path to dependency file: /package.json</p> <p>Path to vulnerable library: /node_modules/parse-url/package.json</p> <p> Dependency Hierarchy: - snyk-1.290.2.tgz (Root Library) - git-url-parse-11.1.2.tgz - git-up-4.0.1.tgz - :x: parse-url-5.0.1.tgz (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/samq-ghdemo/snyk-goof/commit/77eae86d878e3f5b3d008c20fb02ac8f24ee2393">77eae86d878e3f5b3d008c20fb02ac8f24ee2393</a></p> <p>Found in base branch: <b>master</b></p> </p> <p></p> ### Vulnerability Details <p> File Protocol Spoofing in parse-url before 8.0.0 can lead to attacks, such as XSS, Arbitrary Read/Write File, and Remote Code Execution. <p>Publish Date: 2022-06-30 <p>URL: <a href=https://huntr.dev/bounties/52060edb-e426-431b-a0d0-e70407e44f18/>WS-2022-0238</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>7.5</b>) <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: High - Privileges Required: None - User Interaction: Required - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: High - Integrity Impact: High - Availability Impact: High </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> <p></p> ### Suggested Fix <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://huntr.dev/bounties/52060edb-e426-431b-a0d0-e70407e44f18/">https://huntr.dev/bounties/52060edb-e426-431b-a0d0-e70407e44f18/</a></p> <p>Release Date: 2022-06-30</p> <p>Fix Resolution (parse-url): 8.0.0</p> <p>Direct dependency fix Resolution (snyk): 1.324.0</p> </p> <p></p> :rescue_worker_helmet: Automatic Remediation is available for this issue </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2020-8203</summary> ### Vulnerable Library - <b>lodash-4.17.15.tgz</b></p> <p>Lodash modular utilities.</p> <p>Library home page: <a href="https://registry.npmjs.org/lodash/-/lodash-4.17.15.tgz">https://registry.npmjs.org/lodash/-/lodash-4.17.15.tgz</a></p> <p>Path to dependency file: /package.json</p> <p>Path to vulnerable library: /node_modules/snyk/node_modules/lodash/package.json,/node_modules/snyk-nodejs-lockfile-parser/node_modules/lodash/package.json,/node_modules/snyk-config/node_modules/lodash/package.json,/node_modules/@snyk/ruby-semver/node_modules/lodash/package.json,/node_modules/snyk-nuget-plugin/node_modules/lodash/package.json,/node_modules/inquirer/node_modules/lodash/package.json,/node_modules/graphlib/node_modules/lodash/package.json,/node_modules/snyk-mvn-plugin/node_modules/lodash/package.json,/node_modules/dotnet-deps-parser/node_modules/lodash/package.json,/node_modules/@snyk/composer-lockfile-parser/node_modules/lodash/package.json</p> <p> Dependency Hierarchy: - snyk-1.290.2.tgz (Root Library) - :x: lodash-4.17.15.tgz (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/samq-ghdemo/snyk-goof/commit/77eae86d878e3f5b3d008c20fb02ac8f24ee2393">77eae86d878e3f5b3d008c20fb02ac8f24ee2393</a></p> <p>Found in base branch: <b>master</b></p> </p> <p></p> ### Vulnerability Details <p> Prototype pollution attack when using _.zipObjectDeep in lodash before 4.17.20. <p>Publish Date: 2020-07-15 <p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2020-8203>CVE-2020-8203</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>7.4</b>) <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: High - Privileges Required: None - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: None - Integrity Impact: High - Availability Impact: High </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> <p></p> ### Suggested Fix <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://www.npmjs.com/advisories/1523">https://www.npmjs.com/advisories/1523</a></p> <p>Release Date: 2020-07-15</p> <p>Fix Resolution (lodash): 4.17.19</p> <p>Direct dependency fix Resolution (snyk): 1.291.0</p> </p> <p></p> :rescue_worker_helmet: Automatic Remediation is available for this issue </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2022-48285</summary> ### Vulnerable Library - <b>jszip-3.2.2.tgz</b></p> <p>Create, read and edit .zip files with JavaScript http://stuartk.com/jszip</p> <p>Library home page: <a href="https://registry.npmjs.org/jszip/-/jszip-3.2.2.tgz">https://registry.npmjs.org/jszip/-/jszip-3.2.2.tgz</a></p> <p>Path to dependency file: /package.json</p> <p>Path to vulnerable library: /node_modules/jszip/package.json</p> <p> Dependency Hierarchy: - snyk-1.290.2.tgz (Root Library) - snyk-nuget-plugin-1.16.0.tgz - :x: jszip-3.2.2.tgz (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/samq-ghdemo/snyk-goof/commit/77eae86d878e3f5b3d008c20fb02ac8f24ee2393">77eae86d878e3f5b3d008c20fb02ac8f24ee2393</a></p> <p>Found in base branch: <b>master</b></p> </p> <p></p> ### Vulnerability Details <p> loadAsync in JSZip before 3.8.0 allows Directory Traversal via a crafted ZIP archive. <p>Publish Date: 2023-01-29 <p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-48285>CVE-2022-48285</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>7.3</b>) <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: Low - Integrity Impact: Low - Availability Impact: Low </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> <p></p> ### Suggested Fix <p> <p>Type: Upgrade version</p> <p>Release Date: 2023-01-29</p> <p>Fix Resolution (jszip): 3.8.0</p> <p>Direct dependency fix Resolution (snyk): 1.291.0</p> </p> <p></p> :rescue_worker_helmet: Automatic Remediation is available for this issue </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2022-0624</summary> ### Vulnerable Library - <b>parse-path-4.0.1.tgz</b></p> <p>Parse paths (local paths, urls: ssh/git/etc)</p> <p>Library home page: <a href="https://registry.npmjs.org/parse-path/-/parse-path-4.0.1.tgz">https://registry.npmjs.org/parse-path/-/parse-path-4.0.1.tgz</a></p> <p>Path to dependency file: /package.json</p> <p>Path to vulnerable library: /node_modules/parse-path/package.json</p> <p> Dependency Hierarchy: - snyk-1.290.2.tgz (Root Library) - git-url-parse-11.1.2.tgz - git-up-4.0.1.tgz - parse-url-5.0.1.tgz - :x: parse-path-4.0.1.tgz (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/samq-ghdemo/snyk-goof/commit/77eae86d878e3f5b3d008c20fb02ac8f24ee2393">77eae86d878e3f5b3d008c20fb02ac8f24ee2393</a></p> <p>Found in base branch: <b>master</b></p> </p> <p></p> ### Vulnerability Details <p> Authorization Bypass Through User-Controlled Key in GitHub repository ionicabizau/parse-path prior to 5.0.0. <p>Publish Date: 2022-06-28 <p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-0624>CVE-2022-0624</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>7.3</b>) <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: Low - Integrity Impact: Low - Availability Impact: Low </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-2022-0624">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-0624</a></p> <p>Release Date: 2022-06-28</p> <p>Fix Resolution (parse-path): 6.0.0</p> <p>Direct dependency fix Resolution (snyk): 1.324.0</p> </p> <p></p> :rescue_worker_helmet: Automatic Remediation is available for this issue </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2021-23337</summary> ### Vulnerable Library - <b>lodash-4.17.15.tgz</b></p> <p>Lodash modular utilities.</p> <p>Library home page: <a href="https://registry.npmjs.org/lodash/-/lodash-4.17.15.tgz">https://registry.npmjs.org/lodash/-/lodash-4.17.15.tgz</a></p> <p>Path to dependency file: /package.json</p> <p>Path to vulnerable library: /node_modules/snyk/node_modules/lodash/package.json,/node_modules/snyk-nodejs-lockfile-parser/node_modules/lodash/package.json,/node_modules/snyk-config/node_modules/lodash/package.json,/node_modules/@snyk/ruby-semver/node_modules/lodash/package.json,/node_modules/snyk-nuget-plugin/node_modules/lodash/package.json,/node_modules/inquirer/node_modules/lodash/package.json,/node_modules/graphlib/node_modules/lodash/package.json,/node_modules/snyk-mvn-plugin/node_modules/lodash/package.json,/node_modules/dotnet-deps-parser/node_modules/lodash/package.json,/node_modules/@snyk/composer-lockfile-parser/node_modules/lodash/package.json</p> <p> Dependency Hierarchy: - snyk-1.290.2.tgz (Root Library) - :x: lodash-4.17.15.tgz (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/samq-ghdemo/snyk-goof/commit/77eae86d878e3f5b3d008c20fb02ac8f24ee2393">77eae86d878e3f5b3d008c20fb02ac8f24ee2393</a></p> <p>Found in base branch: <b>master</b></p> </p> <p></p> ### Vulnerability Details <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://www.mend.io/vulnerability-database/CVE-2021-23337>CVE-2021-23337</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>7.2</b>) <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> <p></p> ### Suggested Fix <p> <p>Type: Upgrade version</p> <p>Release Date: 2021-02-15</p> <p>Fix Resolution (lodash): 4.17.21</p> <p>Direct dependency fix Resolution (snyk): 1.291.0</p> </p> <p></p> :rescue_worker_helmet: Automatic Remediation is available for this issue </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2020-8244</summary> ### Vulnerable Library - <b>bl-3.0.0.tgz</b></p> <p>Buffer List: collect buffers and access with a standard readable Buffer interface, streamable too!</p> <p>Library home page: <a href="https://registry.npmjs.org/bl/-/bl-3.0.0.tgz">https://registry.npmjs.org/bl/-/bl-3.0.0.tgz</a></p> <p>Path to dependency file: /package.json</p> <p>Path to vulnerable library: /node_modules/tar-stream/node_modules/bl/package.json</p> <p> Dependency Hierarchy: - snyk-1.290.2.tgz (Root Library) - snyk-docker-plugin-1.38.0.tgz - tar-stream-2.1.0.tgz - :x: bl-3.0.0.tgz (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/samq-ghdemo/snyk-goof/commit/77eae86d878e3f5b3d008c20fb02ac8f24ee2393">77eae86d878e3f5b3d008c20fb02ac8f24ee2393</a></p> <p>Found in base branch: <b>master</b></p> </p> <p></p> ### Vulnerability Details <p> A buffer over-read vulnerability exists in bl <4.0.3, <3.0.1, <2.2.1, and <1.2.3 which could allow an attacker to supply user input (even typed) that if it ends up in consume() argument and can become negative, the BufferList state can be corrupted, tricking it into exposing uninitialized memory via regular .slice() calls. <p>Publish Date: 2020-08-30 <p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2020-8244>CVE-2020-8244</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>6.5</b>) <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: Low - Integrity Impact: None - Availability Impact: Low </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> <p></p> ### Suggested Fix <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://github.com/advisories/GHSA-pp7h-53gx-mx7r">https://github.com/advisories/GHSA-pp7h-53gx-mx7r</a></p> <p>Release Date: 2020-08-30</p> <p>Fix Resolution (bl): 3.0.1</p> <p>Direct dependency fix Resolution (snyk): 1.291.0</p> </p> <p></p> :rescue_worker_helmet: Automatic Remediation is available for this issue </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2022-22984</summary> ### Vulnerable Libraries - <b>snyk-cocoapods-plugin-2.0.1.tgz</b>, <b>snyk-gradle-plugin-3.2.4.tgz</b>, <b>snyk-docker-plugin-1.38.0.tgz</b>, <b>snyk-sbt-plugin-2.11.0.tgz</b>, <b>snyk-1.290.2.tgz</b>, <b>snyk-python-plugin-1.17.0.tgz</b>, <b>snyk-mvn-plugin-2.8.0.tgz</b></p> <p> ### <b>snyk-cocoapods-plugin-2.0.1.tgz</b></p> <p>Snyk CLI CocoaPods plugin</p> <p>Library home page: <a href="https://registry.npmjs.org/@snyk/snyk-cocoapods-plugin/-/snyk-cocoapods-plugin-2.0.1.tgz">https://registry.npmjs.org/@snyk/snyk-cocoapods-plugin/-/snyk-cocoapods-plugin-2.0.1.tgz</a></p> <p>Path to dependency file: /package.json</p> <p>Path to vulnerable library: /node_modules/@snyk/snyk-cocoapods-plugin/package.json</p> <p> Dependency Hierarchy: - snyk-1.290.2.tgz (Root Library) - :x: snyk-cocoapods-plugin-2.0.1.tgz (Vulnerable Library) ### <b>snyk-gradle-plugin-3.2.4.tgz</b></p> <p>Snyk CLI Gradle plugin</p> <p>Library home page: <a href="https://registry.npmjs.org/snyk-gradle-plugin/-/snyk-gradle-plugin-3.2.4.tgz">https://registry.npmjs.org/snyk-gradle-plugin/-/snyk-gradle-plugin-3.2.4.tgz</a></p> <p>Path to dependency file: /package.json</p> <p>Path to vulnerable library: /node_modules/snyk-gradle-plugin/package.json</p> <p> Dependency Hierarchy: - snyk-1.290.2.tgz (Root Library) - :x: snyk-gradle-plugin-3.2.4.tgz (Vulnerable Library) ### <b>snyk-docker-plugin-1.38.0.tgz</b></p> <p>Snyk CLI docker plugin</p> <p>Library home page: <a href="https://registry.npmjs.org/snyk-docker-plugin/-/snyk-docker-plugin-1.38.0.tgz">https://registry.npmjs.org/snyk-docker-plugin/-/snyk-docker-plugin-1.38.0.tgz</a></p> <p>Path to dependency file: /package.json</p> <p>Path to vulnerable library: /node_modules/snyk-docker-plugin/package.json</p> <p> Dependency Hierarchy: - snyk-1.290.2.tgz (Root Library) - :x: snyk-docker-plugin-1.38.0.tgz (Vulnerable Library) ### <b>snyk-sbt-plugin-2.11.0.tgz</b></p> <p>Snyk CLI SBT plugin</p> <p>Library home page: <a href="https://registry.npmjs.org/snyk-sbt-plugin/-/snyk-sbt-plugin-2.11.0.tgz">https://registry.npmjs.org/snyk-sbt-plugin/-/snyk-sbt-plugin-2.11.0.tgz</a></p> <p>Path to dependency file: /package.json</p> <p>Path to vulnerable library: /node_modules/snyk-sbt-plugin/package.json</p> <p> Dependency Hierarchy: - snyk-1.290.2.tgz (Root Library) - :x: snyk-sbt-plugin-2.11.0.tgz (Vulnerable Library) ### <b>snyk-1.290.2.tgz</b></p> <p>snyk library and cli utility</p> <p>Library home page: <a href="https://registry.npmjs.org/snyk/-/snyk-1.290.2.tgz">https://registry.npmjs.org/snyk/-/snyk-1.290.2.tgz</a></p> <p>Path to dependency file: /package.json</p> <p>Path to vulnerable library: /node_modules/snyk/package.json</p> <p> Dependency Hierarchy: - :x: snyk-1.290.2.tgz (Vulnerable Library) ### <b>snyk-python-plugin-1.17.0.tgz</b></p> <p>Snyk CLI Python plugin</p> <p>Library home page: <a href="https://registry.npmjs.org/snyk-python-plugin/-/snyk-python-plugin-1.17.0.tgz">https://registry.npmjs.org/snyk-python-plugin/-/snyk-python-plugin-1.17.0.tgz</a></p> <p>Path to dependency file: /package.json</p> <p>Path to vulnerable library: /node_modules/snyk-python-plugin/package.json</p> <p> Dependency Hierarchy: - snyk-1.290.2.tgz (Root Library) - :x: snyk-python-plugin-1.17.0.tgz (Vulnerable Library) ### <b>snyk-mvn-plugin-2.8.0.tgz</b></p> <p>Snyk CLI Maven plugin</p> <p>Library home page: <a href="https://registry.npmjs.org/snyk-mvn-plugin/-/snyk-mvn-plugin-2.8.0.tgz">https://registry.npmjs.org/snyk-mvn-plugin/-/snyk-mvn-plugin-2.8.0.tgz</a></p> <p>Path to dependency file: /package.json</p> <p>Path to vulnerable library: /node_modules/snyk-mvn-plugin/package.json</p> <p> Dependency Hierarchy: - snyk-1.290.2.tgz (Root Library) - :x: snyk-mvn-plugin-2.8.0.tgz (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/samq-ghdemo/snyk-goof/commit/77eae86d878e3f5b3d008c20fb02ac8f24ee2393">77eae86d878e3f5b3d008c20fb02ac8f24ee2393</a></p> <p>Found in base branch: <b>master</b></p> </p> <p></p> ### Vulnerability Details <p> The package snyk before 1.1064.0; the package snyk-mvn-plugin before 2.31.3; the package snyk-gradle-plugin before 3.24.5; the package @snyk/snyk-cocoapods-plugin before 2.5.3; the package snyk-sbt-plugin before 2.16.2; the package snyk-python-plugin before 1.24.2; the package snyk-docker-plugin before 5.6.5; the package @snyk/snyk-hex-plugin before 1.1.6 are vulnerable to Command Injection due to an incomplete fix for [CVE-2022-40764](https://security.snyk.io/vuln/SNYK-JS-SNYK-3037342). A successful exploit allows attackers to run arbitrary commands on the host system where the Snyk CLI is installed by passing in crafted command line flags. In order to exploit this vulnerability, a user would have to execute the snyk test command on untrusted files. In most cases, an attacker positioned to control the command line arguments to the Snyk CLI would already be positioned to execute arbitrary commands. However, this could be abused in specific scenarios, such as continuous integration pipelines, where developers can control the arguments passed to the Snyk CLI to leverage this component as part of a wider attack against an integration/build pipeline. This issue has been addressed in the latest Snyk Docker images available at https://hub.docker.com/r/snyk/snyk as of 2022-11-29. Images downloaded and built prior to that date should be updated. The issue has also been addressed in the Snyk TeamCity CI/CD plugin as of version v20221130.093605. <p>Publish Date: 2022-11-30 <p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-22984>CVE-2022-22984</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>6.3</b>) <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: Low - 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> <p></p> ### Suggested Fix <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://www.cve.org/CVERecord?id=CVE-2022-22984">https://www.cve.org/CVERecord?id=CVE-2022-22984</a></p> <p>Release Date: 2022-11-30</p> <p>Fix Resolution (snyk-gradle-plugin): 3.24.5</p> <p>Direct dependency fix Resolution (snyk): 1.330.1</p><p>Fix Resolution (snyk-docker-plugin): 5.6.5</p> <p>Direct dependency fix Resolution (snyk): 1.685.0</p><p>Fix Resolution (snyk-sbt-plugin): 2.16.2</p> <p>Direct dependency fix Resolution (snyk): 1.685.0</p><p>Fix Resolution (snyk-python-plugin): 1.24.2</p> <p>Direct dependency fix Resolution (snyk): 1.685.0</p><p>Fix Resolution (snyk-mvn-plugin): 2.31.3</p> <p>Direct dependency fix Resolution (snyk): 1.685.0</p> </p> <p></p> :rescue_worker_helmet: Automatic Remediation is available for this issue </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2022-3224</summary> ### Vulnerable Library - <b>parse-url-5.0.1.tgz</b></p> <p>An advanced url parser supporting git urls too.</p> <p>Library home page: <a href="https://registry.npmjs.org/parse-url/-/parse-url-5.0.1.tgz">https://registry.npmjs.org/parse-url/-/parse-url-5.0.1.tgz</a></p> <p>Path to dependency file: /package.json</p> <p>Path to vulnerable library: /node_modules/parse-url/package.json</p> <p> Dependency Hierarchy: - snyk-1.290.2.tgz (Root Library) - git-url-parse-11.1.2.tgz - git-up-4.0.1.tgz - :x: parse-url-5.0.1.tgz (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/samq-ghdemo/snyk-goof/commit/77eae86d878e3f5b3d008c20fb02ac8f24ee2393">77eae86d878e3f5b3d008c20fb02ac8f24ee2393</a></p> <p>Found in base branch: <b>master</b></p> </p> <p></p> ### Vulnerability Details <p> Misinterpretation of Input in GitHub repository ionicabizau/parse-url prior to 8.1.0. <p>Publish Date: 2022-09-15 <p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-3224>CVE-2022-3224</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>6.1</b>) <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: Required - Scope: Changed - Impact Metrics: - Confidentiality Impact: Low - Integrity Impact: Low - Availability Impact: None </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> <p></p> ### Suggested Fix <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-3224">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-3224</a></p> <p>Release Date: 2022-09-15</p> <p>Fix Resolution: parse-url - 8.1.0</p> </p> <p></p> </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2022-2217</summary> ### Vulnerable Library - <b>parse-url-5.0.1.tgz</b></p> <p>An advanced url parser supporting git urls too.</p> <p>Library home page: <a href="https://registry.npmjs.org/parse-url/-/parse-url-5.0.1.tgz">https://registry.npmjs.org/parse-url/-/parse-url-5.0.1.tgz</a></p> <p>Path to dependency file: /package.json</p> <p>Path to vulnerable library: /node_modules/parse-url/package.json</p> <p> Dependency Hierarchy: - snyk-1.290.2.tgz (Root Library) - git-url-parse-11.1.2.tgz - git-up-4.0.1.tgz - :x: parse-url-5.0.1.tgz (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/samq-ghdemo/snyk-goof/commit/77eae86d878e3f5b3d008c20fb02ac8f24ee2393">77eae86d878e3f5b3d008c20fb02ac8f24ee2393</a></p> <p>Found in base branch: <b>master</b></p> </p> <p></p> ### Vulnerability Details <p> Cross-site Scripting (XSS) - Generic in GitHub repository ionicabizau/parse-url prior to 7.0.0. <p>Publish Date: 2022-06-27 <p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-2217>CVE-2022-2217</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>6.1</b>) <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: Required - Scope: Changed - Impact Metrics: - Confidentiality Impact: Low - Integrity Impact: Low - Availability Impact: None </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> <p></p> ### Suggested Fix <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://huntr.dev/bounties/4e046c63-b1ca-4bcc-b418-29796918a71b/">https://huntr.dev/bounties/4e046c63-b1ca-4bcc-b418-29796918a71b/</a></p> <p>Release Date: 2022-06-27</p> <p>Fix Resolution (parse-url): 6.0.3</p> <p>Direct dependency fix Resolution (snyk): 1.291.0</p> </p> <p></p> :rescue_worker_helmet: Automatic Remediation is available for this issue </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2022-2218</summary> ### Vulnerable Library - <b>parse-url-5.0.1.tgz</b></p> <p>An advanced url parser supporting git urls too.</p> <p>Library home page: <a href="https://registry.npmjs.org/parse-url/-/parse-url-5.0.1.tgz">https://registry.npmjs.org/parse-url/-/parse-url-5.0.1.tgz</a></p> <p>Path to dependency file: /package.json</p> <p>Path to vulnerable library: /node_modules/parse-url/package.json</p> <p> Dependency Hierarchy: - snyk-1.290.2.tgz (Root Library) - git-url-parse-11.1.2.tgz - git-up-4.0.1.tgz - :x: parse-url-5.0.1.tgz (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/samq-ghdemo/snyk-goof/commit/77eae86d878e3f5b3d008c20fb02ac8f24ee2393">77eae86d878e3f5b3d008c20fb02ac8f24ee2393</a></p> <p>Found in base branch: <b>master</b></p> </p> <p></p> ### Vulnerability Details <p> Cross-site Scripting (XSS) - Stored in GitHub repository ionicabizau/parse-url prior to 7.0.0. <p>Publish Date: 2022-06-27 <p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-2218>CVE-2022-2218</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>6.1</b>) <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: Required - Scope: Changed - Impact Metrics: - Confidentiality Impact: Low - Integrity Impact: Low - Availability Impact: None </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> <p></p> ### Suggested Fix <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://huntr.dev/bounties/024912d3-f103-4daf-a1d0-567f4d9f2bf5/">https://huntr.dev/bounties/024912d3-f103-4daf-a1d0-567f4d9f2bf5/</a></p> <p>Release Date: 2022-06-27</p> <p>Fix Resolution (parse-url): 6.0.3</p> <p>Direct dependency fix Resolution (snyk): 1.291.0</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	snyk tgz vulnerabilities highest severity is vulnerable library snyk tgz snyk library and cli utility library home page a href path to dependency file package json path to vulnerable library node modules snyk package json found in head commit a href vulnerabilities cve severity cvss dependency type fixed in snyk version remediation available high detected in multiple dependencies transitive high parse url tgz transitive high tgz transitive high netmask tgz transitive high parse url tgz transitive high snyk tgz direct high snyk tgz direct high detected in multiple dependencies transitive high minimatch tgz transitive n a high parse url tgz transitive high nconf tgz transitive high parse url tgz transitive high parse url tgz transitive high lodash tgz transitive high jszip tgz transitive high parse path tgz transitive high lodash tgz transitive medium bl tgz transitive medium detected in multiple dependencies transitive medium parse url tgz transitive n a medium parse url tgz transitive medium parse url tgz transitive medium parse url tgz transitive medium lodash tgz transitive medium netmask tgz transitive medium jszip tgz transitive medium got tgz transitive medium hosted git info tgz transitive for some transitive vulnerabilities there is no version of direct dependency with a fix check the section details below to see if there is a version of transitive dependency where vulnerability is fixed details partial details vulnerabilities are displayed below due to a content size limitation in github to view information on the remaining vulnerabilities navigate to the mend application cve vulnerable libraries pac resolver tgz degenerator tgz pac resolver tgz generates an asynchronous resolver function from a pac file library home page a href path to dependency file package json path to vulnerable library node modules pac resolver package json dependency hierarchy snyk tgz root library proxy agent tgz pac proxy agent tgz x pac resolver tgz vulnerable library degenerator tgz turns sync functions into async generator functions library home page a href path to dependency file package json path to vulnerable library node modules degenerator package json dependency hierarchy snyk tgz root library proxy agent tgz pac proxy agent tgz pac resolver tgz x degenerator tgz vulnerable library found in head commit a href found in base branch master vulnerability details this affects the package pac resolver before this can occur when used with untrusted input due to unsafe pac file handling note the fix for this vulnerability is applied in the node degenerator library a dependency written by the same maintainer 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 pac resolver direct dependency fix resolution snyk fix resolution degenerator direct dependency fix resolution snyk rescue worker helmet automatic remediation is available for this issue cve vulnerable library parse url tgz an advanced url parser supporting git urls too library home page a href path to dependency file package json path to vulnerable library node modules parse url package json dependency hierarchy snyk tgz root library git url parse tgz git up tgz x parse url tgz vulnerable library found in head commit a href found in base branch master vulnerability details server side request forgery ssrf in github repository ionicabizau parse url prior to 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 parse url direct dependency fix resolution snyk rescue worker helmet automatic remediation is available for this issue cve vulnerable library tgz the bare bones internationalization library used by yargs library home page a href path to dependency file package json path to vulnerable library node modules nyc node modules yargs node modules package json node modules package json dependency hierarchy snyk tgz root library snyk config tgz nconf tgz yargs tgz x tgz vulnerable library found in head commit a href found in base branch master vulnerability details the package before and is vulnerable to prototype pollution 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 direct dependency fix resolution snyk rescue worker helmet automatic remediation is available for this issue cve vulnerable library netmask tgz parse and lookup ip network blocks library home page a href path to dependency file package json path to vulnerable library node modules netmask package json dependency hierarchy snyk tgz root library proxy agent tgz pac proxy agent tgz pac resolver tgz x netmask tgz vulnerable library found in head commit a href found in base branch master vulnerability details improper input validation of octal strings in netmask npm package and below allows unauthenticated remote attackers to perform indeterminate ssrf rfi and lfi attacks on many of the dependent packages a remote unauthenticated attacker can bypass packages relying on netmask to filter ips and reach critical vpn or lan hosts 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 none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution netmask direct dependency fix resolution snyk rescue worker helmet automatic remediation is available for this issue cve vulnerable library parse url tgz an advanced url parser supporting git urls too library home page a href path to dependency file package json path to vulnerable library node modules parse url package json dependency hierarchy snyk tgz root library git url parse tgz git up tgz x parse url tgz vulnerable library found in head commit a href found in base branch master vulnerability details server side request forgery ssrf in github repository ionicabizau parse url prior to 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 none for more information on scores click a href suggested fix type upgrade version release date fix resolution parse url direct dependency fix resolution snyk rescue worker helmet automatic remediation is available for this issue cve vulnerable library snyk tgz snyk library and cli utility library home page a href path to dependency file package json path to vulnerable library node modules snyk package json dependency hierarchy x snyk tgz vulnerable library found in head commit a href found in base branch master vulnerability details the package snyk before are vulnerable to code injection when analyzing a project an attacker who can convince a user to scan a malicious project can include commands in a build file such as build gradle or gradle wrapper jar which will be executed with the privileges of the application this vulnerability may be triggered when running the the cli tool directly or when running a scan with one of the ide plugins that invoke the snyk cli successful exploitation of this issue would likely require some level of social engineering to coerce an untrusted project to be downloaded and analyzed via the snyk cli or opened in an ide where a snyk ide plugin is installed and enabled additionally if the ide has a trust feature then the target folder must be marked as ‘trusted’ in order to be vulnerable note this issue is independent of the one reported in and upgrading to a fixed version for this addresses that issue as well the affected ide plugins and versions are vs code affected fixed intellij affected fixed visual studio affected fixed eclipse affected fixed all subsequent versions language server affected fixed all subsequent versions 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 unchanged impact metrics confidentiality impact high integrity impact high availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution rescue worker helmet automatic remediation is available for this issue cve vulnerable library snyk tgz snyk library and cli utility library home page a href path to dependency file package json path to vulnerable library node modules snyk package json dependency hierarchy x snyk tgz vulnerable library found in head commit a href found in base branch master vulnerability details snyk cli before allows arbitrary command execution affecting snyk ide plugins and the snyk npm package exploitation could follow from the common practice of viewing untrusted files in the visual studio code editor for example the original demonstration was with shell metacharacters in the vendor json ignore field affecting snyk go plugin before this affects for example the snyk teamcity plugin which does not update automatically before 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 rescue worker helmet automatic remediation is available for this issue cve vulnerable libraries ansi regex tgz ansi regex tgz ansi regex tgz regular expression for matching ansi escape codes library home page a href path to dependency file package json path to vulnerable library node modules wrap ansi node modules ansi regex package json node modules snyk node modules ansi regex package json node modules inquirer node modules ansi regex package json dependency hierarchy snyk tgz root library strip ansi tgz x ansi regex tgz vulnerable library ansi regex tgz regular expression for matching ansi escape codes library home page a href path to dependency file package json path to vulnerable library node modules string width node modules ansi regex package json dependency hierarchy snyk tgz root library inquirer tgz string width tgz strip ansi tgz x ansi regex tgz vulnerable library found in head commit a href found in base branch master vulnerability details ansi regex is vulnerable to inefficient regular expression 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 suggested fix type upgrade version origin a href release date fix resolution ansi regex direct dependency fix resolution snyk fix resolution ansi regex direct dependency fix resolution snyk rescue worker helmet automatic remediation is available for this issue cve vulnerable library minimatch tgz a glob matcher in javascript library home page a href path to dependency file package json path to vulnerable library node modules minimatch package json dependency hierarchy snyk tgz root library glob tgz x minimatch tgz vulnerable library found in head commit a href found in base branch master vulnerability details a vulnerability was found in the minimatch package this flaw allows a regular expression denial of service redos when calling the braceexpand function with specific arguments resulting in a denial of service 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 minimatch cve vulnerable library parse url tgz an advanced url parser supporting git urls too library home page a href path to dependency file package json path to vulnerable library node modules parse url package json dependency hierarchy snyk tgz root library git url parse tgz git up tgz x parse url tgz vulnerable library found in head commit a href found in base branch master vulnerability details exposure of sensitive information to an unauthorized actor in github repository ionicabizau parse url prior to 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 none availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution parse url direct dependency fix resolution snyk rescue worker helmet automatic remediation is available for this issue cve vulnerable library nconf tgz hierarchical node js configuration with files environment variables command line arguments and atomic object merging library home page a href path to dependency file package json path to vulnerable library node modules nconf package json dependency hierarchy snyk tgz root library snyk config tgz x nconf tgz vulnerable library found in head commit a href found in base branch master vulnerability details this affects the package nconf before when using the memory engine it is possible to store a nested json representation of the configuration the set function that is responsible for setting the configuration properties is vulnerable to prototype pollution by providing a crafted property it is possible to modify the properties on the 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 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 nconf direct dependency fix resolution snyk rescue worker helmet automatic remediation is available for this issue ws vulnerable library parse url tgz an advanced url parser supporting git urls too library home page a href path to dependency file package json path to vulnerable library node modules parse url package json dependency hierarchy snyk tgz root library git url parse tgz git up tgz x parse url tgz vulnerable library found in head commit a href found in base branch master vulnerability details regular expression denial of service redos in ionicabizau parse url before it allows cause a denial of service when calling function parse url 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 parse url direct dependency fix resolution snyk rescue worker helmet automatic remediation is available for this issue ws vulnerable library parse url tgz an advanced url parser supporting git urls too library home page a href path to dependency file package json path to vulnerable library node modules parse url package json dependency hierarchy snyk tgz root library git url parse tgz git up tgz x parse url tgz vulnerable library found in head commit a href found in base branch master vulnerability details file protocol spoofing in parse url before can lead to attacks such as xss arbitrary read write file and remote code execution publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity high privileges required none user interaction required scope unchanged impact metrics confidentiality impact high integrity impact high availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution parse url direct dependency fix resolution snyk rescue worker helmet automatic remediation is available for this issue cve vulnerable library lodash tgz lodash modular utilities library home page a href path to dependency file package json path to vulnerable library node modules snyk node modules lodash package json node modules snyk nodejs lockfile parser node modules lodash package json node modules snyk config node modules lodash package json node modules snyk ruby semver node modules lodash package json node modules snyk nuget plugin node modules lodash package json node modules inquirer node modules lodash package json node modules graphlib node modules lodash package json node modules snyk mvn plugin node modules lodash package json node modules dotnet deps parser node modules lodash package json node modules snyk composer lockfile parser node modules lodash package json dependency hierarchy snyk tgz root library x lodash tgz vulnerable library found in head commit a href found in base branch master vulnerability details prototype pollution attack when using zipobjectdeep in lodash before publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity high privileges required none user interaction none scope unchanged impact metrics confidentiality impact none integrity impact 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 direct dependency fix resolution snyk rescue worker helmet automatic remediation is available for this issue cve vulnerable library jszip tgz create read and edit zip files with javascript library home page a href path to dependency file package json path to vulnerable library node modules jszip package json dependency hierarchy snyk tgz root library snyk nuget plugin tgz x jszip tgz vulnerable library found in head commit a href found in base branch master vulnerability details loadasync in jszip before allows directory traversal via a crafted zip archive 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 release date fix resolution jszip direct dependency fix resolution snyk rescue worker helmet automatic remediation is available for this issue cve vulnerable library parse path tgz parse paths local paths urls ssh git etc library home page a href path to dependency file package json path to vulnerable library node modules parse path package json dependency hierarchy snyk tgz root library git url parse tgz git up tgz parse url tgz x parse path tgz vulnerable library found in head commit a href found in base branch master vulnerability details authorization bypass through user controlled key in github repository ionicabizau parse path prior to 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 parse path direct dependency fix resolution snyk rescue worker helmet automatic remediation is available for this issue cve vulnerable library lodash tgz lodash modular utilities library home page a href path to dependency file package json path to vulnerable library node modules snyk node modules lodash package json node modules snyk nodejs lockfile parser node modules lodash package json node modules snyk config node modules lodash package json node modules snyk ruby semver node modules lodash package json node modules snyk nuget plugin node modules lodash package json node modules inquirer node modules lodash package json node modules graphlib node modules lodash package json node modules snyk mvn plugin node modules lodash package json node modules dotnet deps parser node modules lodash package json node modules snyk composer lockfile parser node modules lodash package json dependency hierarchy snyk tgz root library 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 release date fix resolution lodash direct dependency fix resolution snyk rescue worker helmet automatic remediation is available for this issue cve vulnerable library bl tgz buffer list collect buffers and access with a standard readable buffer interface streamable too library home page a href path to dependency file package json path to vulnerable library node modules tar stream node modules bl package json dependency hierarchy snyk tgz root library snyk docker plugin tgz tar stream tgz x bl tgz vulnerable library found in head commit a href found in base branch master vulnerability details a buffer over read vulnerability exists in bl and which could allow an attacker to supply user input even typed that if it ends up in consume argument and can become negative the bufferlist state can be corrupted tricking it into exposing uninitialized memory via regular slice calls publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact low integrity impact none availability impact low for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution bl direct dependency fix resolution snyk rescue worker helmet automatic remediation is available for this issue cve vulnerable libraries snyk cocoapods plugin tgz snyk gradle plugin tgz snyk docker plugin tgz snyk sbt plugin tgz snyk tgz snyk python plugin tgz snyk mvn plugin tgz snyk cocoapods plugin tgz snyk cli cocoapods plugin library home page a href path to dependency file package json path to vulnerable library node modules snyk snyk cocoapods plugin package json dependency hierarchy snyk tgz root library x snyk cocoapods plugin tgz vulnerable library snyk gradle plugin tgz snyk cli gradle plugin library home page a href path to dependency file package json path to vulnerable library node modules snyk gradle plugin package json dependency hierarchy snyk tgz root library x snyk gradle plugin tgz vulnerable library snyk docker plugin tgz snyk cli docker plugin library home page a href path to dependency file package json path to vulnerable library node modules snyk docker plugin package json dependency hierarchy snyk tgz root library x snyk docker plugin tgz vulnerable library snyk sbt plugin tgz snyk cli sbt plugin library home page a href path to dependency file package json path to vulnerable library node modules snyk sbt plugin package json dependency hierarchy snyk tgz root library x snyk sbt plugin tgz vulnerable library snyk tgz snyk library and cli utility library home page a href path to dependency file package json path to vulnerable library node modules snyk package json dependency hierarchy x snyk tgz vulnerable library snyk python plugin tgz snyk cli python plugin library home page a href path to dependency file package json path to vulnerable library node modules snyk python plugin package json dependency hierarchy snyk tgz root library x snyk python plugin tgz vulnerable library snyk mvn plugin tgz snyk cli maven plugin library home page a href path to dependency file package json path to vulnerable library node modules snyk mvn plugin package json dependency hierarchy snyk tgz root library x snyk mvn plugin tgz vulnerable library found in head commit a href found in base branch master vulnerability details the package snyk before the package snyk mvn plugin before the package snyk gradle plugin before the package snyk snyk cocoapods plugin before the package snyk sbt plugin before the package snyk python plugin before the package snyk docker plugin before the package snyk snyk hex plugin before are vulnerable to command injection due to an incomplete fix for a successful exploit allows attackers to run arbitrary commands on the host system where the snyk cli is installed by passing in crafted command line flags in order to exploit this vulnerability a user would have to execute the snyk test command on untrusted files in most cases an attacker positioned to control the command line arguments to the snyk cli would already be positioned to execute arbitrary commands however this could be abused in specific scenarios such as continuous integration pipelines where developers can control the arguments passed to the snyk cli to leverage this component as part of a wider attack against an integration build pipeline this issue has been addressed in the latest snyk docker images available at as of images downloaded and built prior to that date should be updated the issue has also been addressed in the snyk teamcity ci cd plugin as of version publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required low user interaction none scope unchanged impact metrics confidentiality impact 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 snyk gradle plugin direct dependency fix resolution snyk fix resolution snyk docker plugin direct dependency fix resolution snyk fix resolution snyk sbt plugin direct dependency fix resolution snyk fix resolution snyk python plugin direct dependency fix resolution snyk fix resolution snyk mvn plugin direct dependency fix resolution snyk rescue worker helmet automatic remediation is available for this issue cve vulnerable library parse url tgz an advanced url parser supporting git urls too library home page a href path to dependency file package json path to vulnerable library node modules parse url package json dependency hierarchy snyk tgz root library git url parse tgz git up tgz x parse url tgz vulnerable library found in head commit a href found in base branch master vulnerability details misinterpretation of input in github repository ionicabizau parse url prior to 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 parse url cve vulnerable library parse url tgz an advanced url parser supporting git urls too library home page a href path to dependency file package json path to vulnerable library node modules parse url package json dependency hierarchy snyk tgz root library git url parse tgz git up tgz x parse url tgz vulnerable library found in head commit a href found in base branch master vulnerability details cross site scripting xss generic in github repository ionicabizau parse url prior to 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 parse url direct dependency fix resolution snyk rescue worker helmet automatic remediation is available for this issue cve vulnerable library parse url tgz an advanced url parser supporting git urls too library home page a href path to dependency file package json path to vulnerable library node modules parse url package json dependency hierarchy snyk tgz root library git url parse tgz git up tgz x parse url tgz vulnerable library found in head commit a href found in base branch master vulnerability details cross site scripting xss stored in github repository ionicabizau parse url prior to 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 parse url direct dependency fix resolution snyk rescue worker helmet automatic remediation is available for this issue rescue worker helmet automatic remediation is available for this issue
22,942	3,980,432,091	IssuesEvent	2016-05-06 07:32:54	cockroachdb/cockroach	https://api.github.com/repos/cockroachdb/cockroach	closed	circleci: failed tests: TestNodeRestart	Robot test-failure	The following test appears to have failed: [#17206](https://circleci.com/gh/cockroachdb/cockroach/17206): ``` cockroach: [start --ca-cert=/certs/ca.crt --cert=/certs/node.crt --key=/certs/node.key --host=roach1 --alsologtostderr=INFO --store=path=/data2.0 --join=roach0:26257 --log-dir=/logs/roach1 --logtostderr=false] I160503 19:02:22.835375 acceptance/cluster/docker.go:328 unable to create container roach2: Error response from daemon: Conflict. The name "/roach2" is already in use by container f87fe142ce885d7ce87959e82b8d150f9fae7828c7cb932c9488e6c8e4351034. You have to remove (or rename) that container to be able to reuse that name. I160503 19:02:22.836763 acceptance/cluster/localcluster.go:653 stopping I160503 19:02:22.836893 acceptance/cluster/localcluster.go:551 event stream done, resetting...: net/http: request canceled I160503 19:02:22.836904 acceptance/cluster/localcluster.go:574 events monitor exits --- FAIL: TestNodeRestart (11.18s) panic: error indicated existing container roach2, but none found: error: Error response from daemon: Conflict. The name "/roach2" is already in use by container f87fe142ce885d7ce87959e82b8d150f9fae7828c7cb932c9488e6c8e4351034. You have to remove (or rename) that container to be able to reuse that name. containers: [{ID:5b22ea23d1e7f567c557b47cc4982936dbd815cca0528c6df9f7daec7e452502 Names:[/roach1] Image:cockroachdb/builder:20160305-182433 ImageID:sha256:26823585ed7ee28fa547f4a91d16d6f26765bfcc3b49e8befcd6f67189ad4617 Command:/cockroach start --ca-cert=/certs/ca.crt --cert=/certs/node.crt --key=/certs/node.key --host=roach1 --alsologtostderr=INFO --store=path=/data2.0 --join=roach0:26257 --log-dir=/logs/roach1 --logtostderr=false Created:1462302132 Ports:[{IP:0.0.0.0 PrivatePort:26257 PublicPort:32798 Type:tcp} {IP:0.0.0.0 PrivatePort:8080 PublicPort:32799 Type:tcp}] SizeRw:0 SizeRootFs:0 Labels:map[Roach: Hostname:roach1] State: Status:Up 10 seconds HostConfig:{NetworkMode:598508a6052a2b62c0edfb335e45a2d4d7c9082323df7dfa041616e765bd74f0} NetworkSettings:0xc820118350 Mounts:[]} {ID:d6774258776d5645015184d11363f22481a2f8d5d6fc22582d8ce9bee5ee2a0a Names:[/roach0] Image:cockroachdb/builder:20160305-182433 ImageID:sha256:26823585ed7ee28fa547f4a91d16d6f26765bfcc3b49e8befcd6f67189ad4617 Command:/cockroach start --ca-cert=/certs/ca.crt --cert=/certs/node.crt --key=/certs/node.key --host=roach0 --alsologtostderr=INFO --store=path=/data1.0 --log-dir=/logs/roach0 --logtostderr=false Created:1462302132 Ports:[{IP:0.0.0.0 PrivatePort:26257 PublicPort:32796 Type:tcp} {IP:0.0.0.0 PrivatePort:8080 PublicPort:32797 Type:tcp}] SizeRw:0 SizeRootFs:0 Labels:map[Hostname:roach0 Roach:] State: Status:Up 10 seconds HostConfig:{NetworkMode:598508a6052a2b62c0edfb335e45a2d4d7c9082323df7dfa041616e765bd74f0} NetworkSettings:0xc820118360 Mounts:[]} {ID:f5d9495377174b6da5d8b1e25d92836386f99321db82584f80674cdd26785a29 Names:[/volumes] Image:cockroachdb/builder:20160305-182433 ImageID:sha256:26823585ed7ee28fa547f4a91d16d6f26765bfcc3b49e8befcd6f67189ad4617 Command:/bin/true Created:1462302131 Ports:[] SizeRw:0 SizeRootFs:0 Labels:map[] State: Status:Exited (0) 10 seconds ago HostConfig:{NetworkMode:598508a6052a2b62c0edfb335e45a2d4d7c9082323df7dfa041616e765bd74f0} NetworkSettings:0xc820118370 Mounts:[]} {ID:6d0f67b685745c47827877f6ad958e0b36a1fde92d142a578d300e8f158a8e45 Names:[/dreamy_ramanujan] Image:cockroachdb/builder:20160305-182433 ImageID:sha256:26823585ed7ee28fa547f4a91d16d6f26765bfcc3b49e8befcd6f67189ad4617 Command:make test 'TESTFLAGS=-v --verbosity=1 --vmodule=monitor=2,tracer=2' Created:1462301779 Ports:[] SizeRw:0 SizeRootFs:0 Labels:map[] State: Status:Exited (0) 2 minutes ago HostConfig:{NetworkMode:default} NetworkSettings:0xc820118380 Mounts:[]} {ID:fe432ad58414777580b2acb8fdb51c4a23b4b11c83b2cd14683ab3d350cef37a Names:[/nostalgic_euler] Image:cockroachdb/builder:20160305-182433 ImageID:sha256:26823585ed7ee28fa547f4a91d16d6f26765bfcc3b49e8befcd6f67189ad4617 Command:build/circle-deps.sh docker Created:1462301661 Ports:[] SizeRw:0 SizeRootFs:0 Labels:map[] State: Status:Exited (0) 6 minutes ago HostConfig:{NetworkMode:default} NetworkSettings:0xc820118390 Mounts:[]}] [recovered] panic: runtime error: invalid memory address or nil pointer dereference [recovered] panic: runtime error: invalid memory address or nil pointer dereference [signal 0xb code=0x1 addr=0x0 pc=0x6d94a4] goroutine 648 [running]: panic(0x1319560, 0xc820014140) /usr/local/go/src/runtime/panic.go:464 +0x3e6 testing.tRunner.func1(0xc82040a090) /usr/local/go/src/testing/testing.go:467 +0x192 panic(0x1319560, 0xc820014140) /usr/local/go/src/runtime/panic.go:426 +0x4e9 github.com/cockroachdb/cockroach/acceptance/cluster.(LocalCluster).expectEvent(0xc8200c22a0, 0xc8204a0a20, 0xc82020c8e8, 0x1, 0x1) /go/src/github.com/cockroachdb/cockroach/acceptance/cluster/localcluster.go:183 +0x274 github.com/cockroachdb/cockroach/acceptance/cluster.(Container).Kill(0xc8204a0a20, 0x0, 0x0) /go/src/github.com/cockroachdb/cockroach/acceptance/cluster/docker.go:187 +0x20e github.com/cockroachdb/cockroach/acceptance/cluster.(LocalCluster).stop(0xc8200c22a0) /go/src/github.com/cockroachdb/cockroach/acceptance/cluster/localcluster.go:664 +0x1a0 github.com/cockroachdb/cockroach/acceptance/cluster.(LocalCluster).stopOnPanic(0xc8200c22a0) /go/src/github.com/cockroachdb/cockroach/acceptance/cluster/localcluster.go:236 +0x4d panic(0x12cc860, 0xc8201ea2f0) /usr/local/go/src/runtime/panic.go:426 +0x4e9 github.com/cockroachdb/cockroach/acceptance/cluster.maybePanic(0x7f7af892f028, 0xc8201ea2f0) /go/src/github.com/cockroachdb/cockroach/acceptance/cluster/docker.go:166 +0x4b github.com/cockroachdb/cockroach/acceptance/cluster.(LocalCluster).createRoach(0xc8200c22a0, 0xc8203d3020, 0xc8204a0a20, 0xc8203eb840, 0x2, 0x2, 0xc820272540, 0xa, 0xc) /go/src/github.com/cockroachdb/cockroach/acceptance/cluster/localcluster.go:420 +0x792 github.com/cockroachdb/cockroach/acceptance/cluster.(LocalCluster).startNode(0xc8200c22a0, 0xc8203d3020) /go/src/github.com/cockroachdb/cockroach/acceptance/cluster/localcluster.go:477 +0x920 github.com/cockroachdb/cockroach/acceptance/cluster.(LocalCluster).Start(0xc8200c22a0) /go/src/github.com/cockroachdb/cockroach/acceptance/cluster/localcluster.go:598 +0x7a1 github.com/cockroachdb/cockroach/acceptance.StartCluster(0xc82040a090, 0xc8205d6470, 0x9, 0xc8205c0880, 0x1, 0x1, 0x12a05f200, 0x0, 0x0) -- testing.tRunner(0xc82040a090, 0x1daa1a0) /usr/local/go/src/testing/testing.go:473 +0x98 created by testing.RunTests /usr/local/go/src/testing/testing.go:582 +0x892 goroutine 1 [chan receive]: testing.RunTests(0x173fd40, 0x1daa140, 0x17, 0x17, 0xc82025bd01) /usr/local/go/src/testing/testing.go:583 +0x8d2 testing.(M).Run(0xc82027af08, 0x173dfd0) /usr/local/go/src/testing/testing.go:515 +0x81 github.com/cockroachdb/cockroach/acceptance.TestMain(0xc82027af08) /go/src/github.com/cockroachdb/cockroach/acceptance/main_test.go:48 +0x3e main.main() github.com/cockroachdb/cockroach/acceptance/_test/_testmain.go:96 +0x114 goroutine 17 [syscall, 2 minutes, locked to thread]: runtime.goexit() /usr/local/go/src/runtime/asm_amd64.s:1998 +0x1 goroutine 20 [chan receive]: github.com/cockroachdb/cockroach/util/log.(loggingT).flushDaemon(0x2082200) /go/src/github.com/cockroachdb/cockroach/util/log/clog.go:1011 +0x64 created by github.com/cockroachdb/cockroach/util/log.init.1 /go/src/github.com/cockroachdb/cockroach/util/log/clog.go:598 +0x8a goroutine 22 [syscall, 2 minutes]: os/signal.signal_recv(0x0) /usr/local/go/src/runtime/sigqueue.go:116 +0x132 os/signal.loop() /usr/local/go/src/os/signal/signal_unix.go:22 +0x18 created by os/signal.init.1 /usr/local/go/src/os/signal/signal_unix.go:28 +0x37 goroutine 23 [chan receive, 2 minutes]: github.com/cockroachdb/cockroach/acceptance.TestMain.func1() /go/src/github.com/cockroachdb/cockroach/acceptance/main_test.go:39 +0xd8 created by github.com/cockroachdb/cockroach/acceptance.TestMain /go/src/github.com/cockroachdb/cockroach/acceptance/main_test.go:47 +0x30 goroutine 572 [chan receive, 1 minutes]: database/sql.(DB).connectionOpener(0xc820010790) /usr/local/go/src/database/sql/sql.go:727 +0x45 created by database/sql.Open /usr/local/go/src/database/sql/sql.go:493 +0x33f goroutine 29 [select, 2 minutes, locked to thread]: runtime.gopark(0x1740580, 0xc820025728, 0x1466c50, 0x6, 0x18, 0x2) /usr/local/go/src/runtime/proc.go:262 +0x163 runtime.selectgoImpl(0xc820025728, 0x0, 0x18) /usr/local/go/src/runtime/select.go:392 +0xa67 runtime.selectgo(0xc820025728) /usr/local/go/src/runtime/select.go:215 +0x12 runtime.ensureSigM.func1() /usr/local/go/src/runtime/signal1_unix.go:279 +0x358 runtime.goexit() /usr/local/go/src/runtime/asm_amd64.s:1998 +0x1 goroutine 27 [IO wait, 2 minutes]: net.runtime_pollWait(0x7f7af8900dc8, 0x72, 0xc82047c000) /usr/local/go/src/runtime/netpoll.go:160 +0x60 net.(pollDesc).Wait(0xc8203e2c30, 0x72, 0x0, 0x0) /usr/local/go/src/net/fd_poll_runtime.go:73 +0x3a net.(pollDesc).WaitRead(0xc8203e2c30, 0x0, 0x0) /usr/local/go/src/net/fd_poll_runtime.go:78 +0x36 net.(netFD).Read(0xc8203e2bd0, 0xc82047c000, 0x1000, 0x1000, 0x0, 0x7f7af892f050, 0xc820014200) /usr/local/go/src/net/fd_unix.go:250 +0x23a net.(conn).Read(0xc8201186b8, 0xc82047c000, 0x1000, 0x1000, 0x0, 0x0, 0x0) /usr/local/go/src/net/net.go:172 +0xe4 -- net/http.(persistConn).readLoop(0xc8203ff930) /usr/local/go/src/net/http/transport.go:1069 +0x177 created by net/http.(Transport).dialConn /usr/local/go/src/net/http/transport.go:853 +0x10a6 goroutine 28 [select, 2 minutes]: net/http.(persistConn).writeLoop(0xc8203ff930) /usr/local/go/src/net/http/transport.go:1273 +0x472 created by net/http.(Transport).dialConn /usr/local/go/src/net/http/transport.go:854 +0x10cb goroutine 531 [chan receive, 1 minutes]: database/sql.(DB).connectionOpener(0xc8200ea630) /usr/local/go/src/database/sql/sql.go:727 +0x45 created by database/sql.Open /usr/local/go/src/database/sql/sql.go:493 +0x33f goroutine 142 [IO wait, 1 minutes]: net.runtime_pollWait(0x7f7af8900c48, 0x72, 0xc8202df000) /usr/local/go/src/runtime/netpoll.go:160 +0x60 net.(pollDesc).Wait(0xc8203e3170, 0x72, 0x0, 0x0) /usr/local/go/src/net/fd_poll_runtime.go:73 +0x3a net.(pollDesc).WaitRead(0xc8203e3170, 0x0, 0x0) /usr/local/go/src/net/fd_poll_runtime.go:78 +0x36 net.(netFD).Read(0xc8203e3110, 0xc8202df000, 0x1000, 0x1000, 0x0, 0x7f7af892f050, 0xc820014200) /usr/local/go/src/net/fd_unix.go:250 +0x23a net.(conn).Read(0xc82002a248, 0xc8202df000, 0x1000, 0x1000, 0x0, 0x0, 0x0) /usr/local/go/src/net/net.go:172 +0xe4 -- net/http.(persistConn).readLoop(0xc820124d00) /usr/local/go/src/net/http/transport.go:1069 +0x177 created by net/http.(Transport).dialConn /usr/local/go/src/net/http/transport.go:853 +0x10a6 goroutine 270 [IO wait, 1 minutes]: net.runtime_pollWait(0x7f7af8900a08, 0x72, 0xc820205000) /usr/local/go/src/runtime/netpoll.go:160 +0x60 net.(pollDesc).Wait(0xc8203e21b0, 0x72, 0x0, 0x0) /usr/local/go/src/net/fd_poll_runtime.go:73 +0x3a net.(pollDesc).WaitRead(0xc8203e21b0, 0x0, 0x0) /usr/local/go/src/net/fd_poll_runtime.go:78 +0x36 net.(netFD).Read(0xc8203e2150, 0xc820205000, 0x1000, 0x1000, 0x0, 0x7f7af892f050, 0xc820014200) /usr/local/go/src/net/fd_unix.go:250 +0x23a net.(conn).Read(0xc820118100, 0xc820205000, 0x1000, 0x1000, 0x0, 0x0, 0x0) /usr/local/go/src/net/net.go:172 +0xe4 -- net/http.(persistConn).readLoop(0xc8203fe680) /usr/local/go/src/net/http/transport.go:1069 +0x177 created by net/http.(Transport).dialConn /usr/local/go/src/net/http/transport.go:853 +0x10a6 goroutine 432 [select]: net/http.(persistConn).writeLoop(0xc820060820) /usr/local/go/src/net/http/transport.go:1273 +0x472 created by net/http.(Transport).dialConn /usr/local/go/src/net/http/transport.go:854 +0x10cb goroutine 143 [select, 1 minutes]: net/http.(persistConn).writeLoop(0xc820124d00) /usr/local/go/src/net/http/transport.go:1273 +0x472 created by net/http.(Transport).dialConn /usr/local/go/src/net/http/transport.go:854 +0x10cb goroutine 506 [chan receive, 1 minutes]: database/sql.(DB).connectionOpener(0xc8203b7550) /usr/local/go/src/database/sql/sql.go:727 +0x45 created by database/sql.Open /usr/local/go/src/database/sql/sql.go:493 +0x33f goroutine 431 [IO wait]: net.runtime_pollWait(0x7f7af8900ac8, 0x72, 0xc82039a000) /usr/local/go/src/runtime/netpoll.go:160 +0x60 net.(pollDesc).Wait(0xc820552300, 0x72, 0x0, 0x0) /usr/local/go/src/net/fd_poll_runtime.go:73 +0x3a net.(pollDesc).WaitRead(0xc820552300, 0x0, 0x0) /usr/local/go/src/net/fd_poll_runtime.go:78 +0x36 net.(netFD).Read(0xc8205522a0, 0xc82039a000, 0x1000, 0x1000, 0x0, 0x7f7af892f050, 0xc820014200) /usr/local/go/src/net/fd_unix.go:250 +0x23a net.(conn).Read(0xc820118278, 0xc82039a000, 0x1000, 0x1000, 0x0, 0x0, 0x0) /usr/local/go/src/net/net.go:172 +0xe4 -- net/http.(persistConn).readLoop(0xc820060820) /usr/local/go/src/net/http/transport.go:1069 +0x177 created by net/http.(Transport).dialConn /usr/local/go/src/net/http/transport.go:853 +0x10a6 goroutine 271 [select, 1 minutes]: net/http.(persistConn).writeLoop(0xc8203fe680) /usr/local/go/src/net/http/transport.go:1273 +0x472 created by net/http.(Transport).dialConn /usr/local/go/src/net/http/transport.go:854 +0x10cb goroutine 698 [IO wait]: net.runtime_pollWait(0x7f7af89001c8, 0x72, 0xc820234000) /usr/local/go/src/runtime/netpoll.go:160 +0x60 net.(pollDesc).Wait(0xc8201d4140, 0x72, 0x0, 0x0) /usr/local/go/src/net/fd_poll_runtime.go:73 +0x3a net.(pollDesc).WaitRead(0xc8201d4140, 0x0, 0x0) /usr/local/go/src/net/fd_poll_runtime.go:78 +0x36 net.(netFD).Read(0xc8201d40e0, 0xc820234000, 0x1000, 0x1000, 0x0, 0x7f7af892f050, 0xc820014200) /usr/local/go/src/net/fd_unix.go:250 +0x23a net.(conn).Read(0xc820118340, 0xc820234000, 0x1000, 0x1000, 0x0, 0x0, 0x0) /usr/local/go/src/net/net.go:172 +0xe4 -- net/http.(persistConn).readLoop(0xc820060b60) /usr/local/go/src/net/http/transport.go:1069 +0x177 created by net/http.(Transport).dialConn /usr/local/go/src/net/http/transport.go:853 +0x10a6 goroutine 349 [IO wait, 1 minutes]: net.runtime_pollWait(0x7f7af8900b88, 0x72, 0xc8202c9000) /usr/local/go/src/runtime/netpoll.go:160 +0x60 net.(pollDesc).Wait(0xc8205521b0, 0x72, 0x0, 0x0) /usr/local/go/src/net/fd_poll_runtime.go:73 +0x3a net.(pollDesc).WaitRead(0xc8205521b0, 0x0, 0x0) /usr/local/go/src/net/fd_poll_runtime.go:78 +0x36 net.(netFD).Read(0xc820552150, 0xc8202c9000, 0x1000, 0x1000, 0x0, 0x7f7af892f050, 0xc820014200) /usr/local/go/src/net/fd_unix.go:250 +0x23a net.(conn).Read(0xc820118238, 0xc8202c9000, 0x1000, 0x1000, 0x0, 0x0, 0x0) /usr/local/go/src/net/net.go:172 +0xe4 -- net/http.(persistConn).readLoop(0xc820060270) /usr/local/go/src/net/http/transport.go:1069 +0x177 created by net/http.(Transport).dialConn /usr/local/go/src/net/http/transport.go:853 +0x10a6 goroutine 350 [select, 1 minutes]: net/http.(persistConn).writeLoop(0xc820060270) /usr/local/go/src/net/http/transport.go:1273 +0x472 created by net/http.(Transport).dialConn /usr/local/go/src/net/http/transport.go:854 +0x10cb goroutine 502 [chan receive, 1 minutes]: database/sql.(DB).connectionOpener(0xc8203b7340) /usr/local/go/src/database/sql/sql.go:727 +0x45 created by database/sql.Open /usr/local/go/src/database/sql/sql.go:493 +0x33f goroutine 498 [chan receive, 1 minutes]: database/sql.(DB).connectionOpener(0xc8203b6f20) /usr/local/go/src/database/sql/sql.go:727 +0x45 created by database/sql.Open /usr/local/go/src/database/sql/sql.go:493 +0x33f goroutine 699 [select]: net/http.(persistConn).writeLoop(0xc820060b60) /usr/local/go/src/net/http/transport.go:1273 +0x472 created by net/http.(Transport).dialConn /usr/local/go/src/net/http/transport.go:854 +0x10cb goroutine 494 [chan receive, 1 minutes]: database/sql.(DB).connectionOpener(0xc8203b68f0) /usr/local/go/src/database/sql/sql.go:727 +0x45 created by database/sql.Open /usr/local/go/src/database/sql/sql.go:493 +0x33f goroutine 702 [runnable]: github.com/docker/engine-api/client/transport/cancellable.Do.func3(0x7f7af8900f30, 0xc8205daab0, 0xc8205d71e0, 0xc8202dd440) /go/src/github.com/docker/engine-api/client/transport/cancellable/cancellable.go:77 created by github.com/docker/engine-api/client/transport/cancellable.Do /go/src/github.com/docker/engine-api/client/transport/cancellable/cancellable.go:84 +0x336 goroutine 529 [chan receive, 1 minutes]: database/sql.(DB).connectionOpener(0xc820011b80) /usr/local/go/src/database/sql/sql.go:727 +0x45 created by database/sql.Open /usr/local/go/src/database/sql/sql.go:493 +0x33f ok github.com/cockroachdb/cockroach/acceptance 1337s ``` Please assign, take a look and update the issue accordingly.	1.0	circleci: failed tests: TestNodeRestart - The following test appears to have failed: [#17206](https://circleci.com/gh/cockroachdb/cockroach/17206): ``` cockroach: [start --ca-cert=/certs/ca.crt --cert=/certs/node.crt --key=/certs/node.key --host=roach1 --alsologtostderr=INFO --store=path=/data2.0 --join=roach0:26257 --log-dir=/logs/roach1 --logtostderr=false] I160503 19:02:22.835375 acceptance/cluster/docker.go:328 unable to create container roach2: Error response from daemon: Conflict. The name "/roach2" is already in use by container f87fe142ce885d7ce87959e82b8d150f9fae7828c7cb932c9488e6c8e4351034. You have to remove (or rename) that container to be able to reuse that name. I160503 19:02:22.836763 acceptance/cluster/localcluster.go:653 stopping I160503 19:02:22.836893 acceptance/cluster/localcluster.go:551 event stream done, resetting...: net/http: request canceled I160503 19:02:22.836904 acceptance/cluster/localcluster.go:574 events monitor exits --- FAIL: TestNodeRestart (11.18s) panic: error indicated existing container roach2, but none found: error: Error response from daemon: Conflict. The name "/roach2" is already in use by container f87fe142ce885d7ce87959e82b8d150f9fae7828c7cb932c9488e6c8e4351034. You have to remove (or rename) that container to be able to reuse that name. containers: [{ID:5b22ea23d1e7f567c557b47cc4982936dbd815cca0528c6df9f7daec7e452502 Names:[/roach1] Image:cockroachdb/builder:20160305-182433 ImageID:sha256:26823585ed7ee28fa547f4a91d16d6f26765bfcc3b49e8befcd6f67189ad4617 Command:/cockroach start --ca-cert=/certs/ca.crt --cert=/certs/node.crt --key=/certs/node.key --host=roach1 --alsologtostderr=INFO --store=path=/data2.0 --join=roach0:26257 --log-dir=/logs/roach1 --logtostderr=false Created:1462302132 Ports:[{IP:0.0.0.0 PrivatePort:26257 PublicPort:32798 Type:tcp} {IP:0.0.0.0 PrivatePort:8080 PublicPort:32799 Type:tcp}] SizeRw:0 SizeRootFs:0 Labels:map[Roach: Hostname:roach1] State: Status:Up 10 seconds HostConfig:{NetworkMode:598508a6052a2b62c0edfb335e45a2d4d7c9082323df7dfa041616e765bd74f0} NetworkSettings:0xc820118350 Mounts:[]} {ID:d6774258776d5645015184d11363f22481a2f8d5d6fc22582d8ce9bee5ee2a0a Names:[/roach0] Image:cockroachdb/builder:20160305-182433 ImageID:sha256:26823585ed7ee28fa547f4a91d16d6f26765bfcc3b49e8befcd6f67189ad4617 Command:/cockroach start --ca-cert=/certs/ca.crt --cert=/certs/node.crt --key=/certs/node.key --host=roach0 --alsologtostderr=INFO --store=path=/data1.0 --log-dir=/logs/roach0 --logtostderr=false Created:1462302132 Ports:[{IP:0.0.0.0 PrivatePort:26257 PublicPort:32796 Type:tcp} {IP:0.0.0.0 PrivatePort:8080 PublicPort:32797 Type:tcp}] SizeRw:0 SizeRootFs:0 Labels:map[Hostname:roach0 Roach:] State: Status:Up 10 seconds HostConfig:{NetworkMode:598508a6052a2b62c0edfb335e45a2d4d7c9082323df7dfa041616e765bd74f0} NetworkSettings:0xc820118360 Mounts:[]} {ID:f5d9495377174b6da5d8b1e25d92836386f99321db82584f80674cdd26785a29 Names:[/volumes] Image:cockroachdb/builder:20160305-182433 ImageID:sha256:26823585ed7ee28fa547f4a91d16d6f26765bfcc3b49e8befcd6f67189ad4617 Command:/bin/true Created:1462302131 Ports:[] SizeRw:0 SizeRootFs:0 Labels:map[] State: Status:Exited (0) 10 seconds ago HostConfig:{NetworkMode:598508a6052a2b62c0edfb335e45a2d4d7c9082323df7dfa041616e765bd74f0} NetworkSettings:0xc820118370 Mounts:[]} {ID:6d0f67b685745c47827877f6ad958e0b36a1fde92d142a578d300e8f158a8e45 Names:[/dreamy_ramanujan] Image:cockroachdb/builder:20160305-182433 ImageID:sha256:26823585ed7ee28fa547f4a91d16d6f26765bfcc3b49e8befcd6f67189ad4617 Command:make test 'TESTFLAGS=-v --verbosity=1 --vmodule=monitor=2,tracer=2' Created:1462301779 Ports:[] SizeRw:0 SizeRootFs:0 Labels:map[] State: Status:Exited (0) 2 minutes ago HostConfig:{NetworkMode:default} NetworkSettings:0xc820118380 Mounts:[]} {ID:fe432ad58414777580b2acb8fdb51c4a23b4b11c83b2cd14683ab3d350cef37a Names:[/nostalgic_euler] Image:cockroachdb/builder:20160305-182433 ImageID:sha256:26823585ed7ee28fa547f4a91d16d6f26765bfcc3b49e8befcd6f67189ad4617 Command:build/circle-deps.sh docker Created:1462301661 Ports:[] SizeRw:0 SizeRootFs:0 Labels:map[] State: Status:Exited (0) 6 minutes ago HostConfig:{NetworkMode:default} NetworkSettings:0xc820118390 Mounts:[]}] [recovered] panic: runtime error: invalid memory address or nil pointer dereference [recovered] panic: runtime error: invalid memory address or nil pointer dereference [signal 0xb code=0x1 addr=0x0 pc=0x6d94a4] goroutine 648 [running]: panic(0x1319560, 0xc820014140) /usr/local/go/src/runtime/panic.go:464 +0x3e6 testing.tRunner.func1(0xc82040a090) /usr/local/go/src/testing/testing.go:467 +0x192 panic(0x1319560, 0xc820014140) /usr/local/go/src/runtime/panic.go:426 +0x4e9 github.com/cockroachdb/cockroach/acceptance/cluster.(LocalCluster).expectEvent(0xc8200c22a0, 0xc8204a0a20, 0xc82020c8e8, 0x1, 0x1) /go/src/github.com/cockroachdb/cockroach/acceptance/cluster/localcluster.go:183 +0x274 github.com/cockroachdb/cockroach/acceptance/cluster.(Container).Kill(0xc8204a0a20, 0x0, 0x0) /go/src/github.com/cockroachdb/cockroach/acceptance/cluster/docker.go:187 +0x20e github.com/cockroachdb/cockroach/acceptance/cluster.(LocalCluster).stop(0xc8200c22a0) /go/src/github.com/cockroachdb/cockroach/acceptance/cluster/localcluster.go:664 +0x1a0 github.com/cockroachdb/cockroach/acceptance/cluster.(LocalCluster).stopOnPanic(0xc8200c22a0) /go/src/github.com/cockroachdb/cockroach/acceptance/cluster/localcluster.go:236 +0x4d panic(0x12cc860, 0xc8201ea2f0) /usr/local/go/src/runtime/panic.go:426 +0x4e9 github.com/cockroachdb/cockroach/acceptance/cluster.maybePanic(0x7f7af892f028, 0xc8201ea2f0) /go/src/github.com/cockroachdb/cockroach/acceptance/cluster/docker.go:166 +0x4b github.com/cockroachdb/cockroach/acceptance/cluster.(LocalCluster).createRoach(0xc8200c22a0, 0xc8203d3020, 0xc8204a0a20, 0xc8203eb840, 0x2, 0x2, 0xc820272540, 0xa, 0xc) /go/src/github.com/cockroachdb/cockroach/acceptance/cluster/localcluster.go:420 +0x792 github.com/cockroachdb/cockroach/acceptance/cluster.(LocalCluster).startNode(0xc8200c22a0, 0xc8203d3020) /go/src/github.com/cockroachdb/cockroach/acceptance/cluster/localcluster.go:477 +0x920 github.com/cockroachdb/cockroach/acceptance/cluster.(LocalCluster).Start(0xc8200c22a0) /go/src/github.com/cockroachdb/cockroach/acceptance/cluster/localcluster.go:598 +0x7a1 github.com/cockroachdb/cockroach/acceptance.StartCluster(0xc82040a090, 0xc8205d6470, 0x9, 0xc8205c0880, 0x1, 0x1, 0x12a05f200, 0x0, 0x0) -- testing.tRunner(0xc82040a090, 0x1daa1a0) /usr/local/go/src/testing/testing.go:473 +0x98 created by testing.RunTests /usr/local/go/src/testing/testing.go:582 +0x892 goroutine 1 [chan receive]: testing.RunTests(0x173fd40, 0x1daa140, 0x17, 0x17, 0xc82025bd01) /usr/local/go/src/testing/testing.go:583 +0x8d2 testing.(M).Run(0xc82027af08, 0x173dfd0) /usr/local/go/src/testing/testing.go:515 +0x81 github.com/cockroachdb/cockroach/acceptance.TestMain(0xc82027af08) /go/src/github.com/cockroachdb/cockroach/acceptance/main_test.go:48 +0x3e main.main() github.com/cockroachdb/cockroach/acceptance/_test/_testmain.go:96 +0x114 goroutine 17 [syscall, 2 minutes, locked to thread]: runtime.goexit() /usr/local/go/src/runtime/asm_amd64.s:1998 +0x1 goroutine 20 [chan receive]: github.com/cockroachdb/cockroach/util/log.(loggingT).flushDaemon(0x2082200) /go/src/github.com/cockroachdb/cockroach/util/log/clog.go:1011 +0x64 created by github.com/cockroachdb/cockroach/util/log.init.1 /go/src/github.com/cockroachdb/cockroach/util/log/clog.go:598 +0x8a goroutine 22 [syscall, 2 minutes]: os/signal.signal_recv(0x0) /usr/local/go/src/runtime/sigqueue.go:116 +0x132 os/signal.loop() /usr/local/go/src/os/signal/signal_unix.go:22 +0x18 created by os/signal.init.1 /usr/local/go/src/os/signal/signal_unix.go:28 +0x37 goroutine 23 [chan receive, 2 minutes]: github.com/cockroachdb/cockroach/acceptance.TestMain.func1() /go/src/github.com/cockroachdb/cockroach/acceptance/main_test.go:39 +0xd8 created by github.com/cockroachdb/cockroach/acceptance.TestMain /go/src/github.com/cockroachdb/cockroach/acceptance/main_test.go:47 +0x30 goroutine 572 [chan receive, 1 minutes]: database/sql.(DB).connectionOpener(0xc820010790) /usr/local/go/src/database/sql/sql.go:727 +0x45 created by database/sql.Open /usr/local/go/src/database/sql/sql.go:493 +0x33f goroutine 29 [select, 2 minutes, locked to thread]: runtime.gopark(0x1740580, 0xc820025728, 0x1466c50, 0x6, 0x18, 0x2) /usr/local/go/src/runtime/proc.go:262 +0x163 runtime.selectgoImpl(0xc820025728, 0x0, 0x18) /usr/local/go/src/runtime/select.go:392 +0xa67 runtime.selectgo(0xc820025728) /usr/local/go/src/runtime/select.go:215 +0x12 runtime.ensureSigM.func1() /usr/local/go/src/runtime/signal1_unix.go:279 +0x358 runtime.goexit() /usr/local/go/src/runtime/asm_amd64.s:1998 +0x1 goroutine 27 [IO wait, 2 minutes]: net.runtime_pollWait(0x7f7af8900dc8, 0x72, 0xc82047c000) /usr/local/go/src/runtime/netpoll.go:160 +0x60 net.(pollDesc).Wait(0xc8203e2c30, 0x72, 0x0, 0x0) /usr/local/go/src/net/fd_poll_runtime.go:73 +0x3a net.(pollDesc).WaitRead(0xc8203e2c30, 0x0, 0x0) /usr/local/go/src/net/fd_poll_runtime.go:78 +0x36 net.(netFD).Read(0xc8203e2bd0, 0xc82047c000, 0x1000, 0x1000, 0x0, 0x7f7af892f050, 0xc820014200) /usr/local/go/src/net/fd_unix.go:250 +0x23a net.(conn).Read(0xc8201186b8, 0xc82047c000, 0x1000, 0x1000, 0x0, 0x0, 0x0) /usr/local/go/src/net/net.go:172 +0xe4 -- net/http.(persistConn).readLoop(0xc8203ff930) /usr/local/go/src/net/http/transport.go:1069 +0x177 created by net/http.(Transport).dialConn /usr/local/go/src/net/http/transport.go:853 +0x10a6 goroutine 28 [select, 2 minutes]: net/http.(persistConn).writeLoop(0xc8203ff930) /usr/local/go/src/net/http/transport.go:1273 +0x472 created by net/http.(Transport).dialConn /usr/local/go/src/net/http/transport.go:854 +0x10cb goroutine 531 [chan receive, 1 minutes]: database/sql.(DB).connectionOpener(0xc8200ea630) /usr/local/go/src/database/sql/sql.go:727 +0x45 created by database/sql.Open /usr/local/go/src/database/sql/sql.go:493 +0x33f goroutine 142 [IO wait, 1 minutes]: net.runtime_pollWait(0x7f7af8900c48, 0x72, 0xc8202df000) /usr/local/go/src/runtime/netpoll.go:160 +0x60 net.(pollDesc).Wait(0xc8203e3170, 0x72, 0x0, 0x0) /usr/local/go/src/net/fd_poll_runtime.go:73 +0x3a net.(pollDesc).WaitRead(0xc8203e3170, 0x0, 0x0) /usr/local/go/src/net/fd_poll_runtime.go:78 +0x36 net.(netFD).Read(0xc8203e3110, 0xc8202df000, 0x1000, 0x1000, 0x0, 0x7f7af892f050, 0xc820014200) /usr/local/go/src/net/fd_unix.go:250 +0x23a net.(conn).Read(0xc82002a248, 0xc8202df000, 0x1000, 0x1000, 0x0, 0x0, 0x0) /usr/local/go/src/net/net.go:172 +0xe4 -- net/http.(persistConn).readLoop(0xc820124d00) /usr/local/go/src/net/http/transport.go:1069 +0x177 created by net/http.(Transport).dialConn /usr/local/go/src/net/http/transport.go:853 +0x10a6 goroutine 270 [IO wait, 1 minutes]: net.runtime_pollWait(0x7f7af8900a08, 0x72, 0xc820205000) /usr/local/go/src/runtime/netpoll.go:160 +0x60 net.(pollDesc).Wait(0xc8203e21b0, 0x72, 0x0, 0x0) /usr/local/go/src/net/fd_poll_runtime.go:73 +0x3a net.(pollDesc).WaitRead(0xc8203e21b0, 0x0, 0x0) /usr/local/go/src/net/fd_poll_runtime.go:78 +0x36 net.(netFD).Read(0xc8203e2150, 0xc820205000, 0x1000, 0x1000, 0x0, 0x7f7af892f050, 0xc820014200) /usr/local/go/src/net/fd_unix.go:250 +0x23a net.(conn).Read(0xc820118100, 0xc820205000, 0x1000, 0x1000, 0x0, 0x0, 0x0) /usr/local/go/src/net/net.go:172 +0xe4 -- net/http.(persistConn).readLoop(0xc8203fe680) /usr/local/go/src/net/http/transport.go:1069 +0x177 created by net/http.(Transport).dialConn /usr/local/go/src/net/http/transport.go:853 +0x10a6 goroutine 432 [select]: net/http.(persistConn).writeLoop(0xc820060820) /usr/local/go/src/net/http/transport.go:1273 +0x472 created by net/http.(Transport).dialConn /usr/local/go/src/net/http/transport.go:854 +0x10cb goroutine 143 [select, 1 minutes]: net/http.(persistConn).writeLoop(0xc820124d00) /usr/local/go/src/net/http/transport.go:1273 +0x472 created by net/http.(Transport).dialConn /usr/local/go/src/net/http/transport.go:854 +0x10cb goroutine 506 [chan receive, 1 minutes]: database/sql.(DB).connectionOpener(0xc8203b7550) /usr/local/go/src/database/sql/sql.go:727 +0x45 created by database/sql.Open /usr/local/go/src/database/sql/sql.go:493 +0x33f goroutine 431 [IO wait]: net.runtime_pollWait(0x7f7af8900ac8, 0x72, 0xc82039a000) /usr/local/go/src/runtime/netpoll.go:160 +0x60 net.(pollDesc).Wait(0xc820552300, 0x72, 0x0, 0x0) /usr/local/go/src/net/fd_poll_runtime.go:73 +0x3a net.(pollDesc).WaitRead(0xc820552300, 0x0, 0x0) /usr/local/go/src/net/fd_poll_runtime.go:78 +0x36 net.(netFD).Read(0xc8205522a0, 0xc82039a000, 0x1000, 0x1000, 0x0, 0x7f7af892f050, 0xc820014200) /usr/local/go/src/net/fd_unix.go:250 +0x23a net.(conn).Read(0xc820118278, 0xc82039a000, 0x1000, 0x1000, 0x0, 0x0, 0x0) /usr/local/go/src/net/net.go:172 +0xe4 -- net/http.(persistConn).readLoop(0xc820060820) /usr/local/go/src/net/http/transport.go:1069 +0x177 created by net/http.(Transport).dialConn /usr/local/go/src/net/http/transport.go:853 +0x10a6 goroutine 271 [select, 1 minutes]: net/http.(persistConn).writeLoop(0xc8203fe680) /usr/local/go/src/net/http/transport.go:1273 +0x472 created by net/http.(Transport).dialConn /usr/local/go/src/net/http/transport.go:854 +0x10cb goroutine 698 [IO wait]: net.runtime_pollWait(0x7f7af89001c8, 0x72, 0xc820234000) /usr/local/go/src/runtime/netpoll.go:160 +0x60 net.(pollDesc).Wait(0xc8201d4140, 0x72, 0x0, 0x0) /usr/local/go/src/net/fd_poll_runtime.go:73 +0x3a net.(pollDesc).WaitRead(0xc8201d4140, 0x0, 0x0) /usr/local/go/src/net/fd_poll_runtime.go:78 +0x36 net.(netFD).Read(0xc8201d40e0, 0xc820234000, 0x1000, 0x1000, 0x0, 0x7f7af892f050, 0xc820014200) /usr/local/go/src/net/fd_unix.go:250 +0x23a net.(conn).Read(0xc820118340, 0xc820234000, 0x1000, 0x1000, 0x0, 0x0, 0x0) /usr/local/go/src/net/net.go:172 +0xe4 -- net/http.(persistConn).readLoop(0xc820060b60) /usr/local/go/src/net/http/transport.go:1069 +0x177 created by net/http.(Transport).dialConn /usr/local/go/src/net/http/transport.go:853 +0x10a6 goroutine 349 [IO wait, 1 minutes]: net.runtime_pollWait(0x7f7af8900b88, 0x72, 0xc8202c9000) /usr/local/go/src/runtime/netpoll.go:160 +0x60 net.(pollDesc).Wait(0xc8205521b0, 0x72, 0x0, 0x0) /usr/local/go/src/net/fd_poll_runtime.go:73 +0x3a net.(pollDesc).WaitRead(0xc8205521b0, 0x0, 0x0) /usr/local/go/src/net/fd_poll_runtime.go:78 +0x36 net.(netFD).Read(0xc820552150, 0xc8202c9000, 0x1000, 0x1000, 0x0, 0x7f7af892f050, 0xc820014200) /usr/local/go/src/net/fd_unix.go:250 +0x23a net.(conn).Read(0xc820118238, 0xc8202c9000, 0x1000, 0x1000, 0x0, 0x0, 0x0) /usr/local/go/src/net/net.go:172 +0xe4 -- net/http.(persistConn).readLoop(0xc820060270) /usr/local/go/src/net/http/transport.go:1069 +0x177 created by net/http.(Transport).dialConn /usr/local/go/src/net/http/transport.go:853 +0x10a6 goroutine 350 [select, 1 minutes]: net/http.(persistConn).writeLoop(0xc820060270) /usr/local/go/src/net/http/transport.go:1273 +0x472 created by net/http.(Transport).dialConn /usr/local/go/src/net/http/transport.go:854 +0x10cb goroutine 502 [chan receive, 1 minutes]: database/sql.(DB).connectionOpener(0xc8203b7340) /usr/local/go/src/database/sql/sql.go:727 +0x45 created by database/sql.Open /usr/local/go/src/database/sql/sql.go:493 +0x33f goroutine 498 [chan receive, 1 minutes]: database/sql.(DB).connectionOpener(0xc8203b6f20) /usr/local/go/src/database/sql/sql.go:727 +0x45 created by database/sql.Open /usr/local/go/src/database/sql/sql.go:493 +0x33f goroutine 699 [select]: net/http.(persistConn).writeLoop(0xc820060b60) /usr/local/go/src/net/http/transport.go:1273 +0x472 created by net/http.(Transport).dialConn /usr/local/go/src/net/http/transport.go:854 +0x10cb goroutine 494 [chan receive, 1 minutes]: database/sql.(DB).connectionOpener(0xc8203b68f0) /usr/local/go/src/database/sql/sql.go:727 +0x45 created by database/sql.Open /usr/local/go/src/database/sql/sql.go:493 +0x33f goroutine 702 [runnable]: github.com/docker/engine-api/client/transport/cancellable.Do.func3(0x7f7af8900f30, 0xc8205daab0, 0xc8205d71e0, 0xc8202dd440) /go/src/github.com/docker/engine-api/client/transport/cancellable/cancellable.go:77 created by github.com/docker/engine-api/client/transport/cancellable.Do /go/src/github.com/docker/engine-api/client/transport/cancellable/cancellable.go:84 +0x336 goroutine 529 [chan receive, 1 minutes]: database/sql.(DB).connectionOpener(0xc820011b80) /usr/local/go/src/database/sql/sql.go:727 +0x45 created by database/sql.Open /usr/local/go/src/database/sql/sql.go:493 +0x33f ok github.com/cockroachdb/cockroach/acceptance 1337s ``` Please assign, take a look and update the issue accordingly.	non_priority	circleci failed tests testnoderestart the following test appears to have failed cockroach acceptance cluster docker go unable to create container error response from daemon conflict the name is already in use by container you have to remove or rename that container to be able to reuse that name acceptance cluster localcluster go stopping acceptance cluster localcluster go event stream done resetting net http request canceled acceptance cluster localcluster go events monitor exits fail testnoderestart panic error indicated existing container but none found error error response from daemon conflict the name is already in use by container you have to remove or rename that container to be able to reuse that name containers image cockroachdb builder imageid command cockroach start ca cert certs ca crt cert certs node crt key certs node key host alsologtostderr info store path join log dir logs logtostderr false created ports sizerw sizerootfs labels map state status up seconds hostconfig networkmode networksettings mounts id names image cockroachdb builder imageid command cockroach start ca cert certs ca crt cert certs node crt key certs node key host alsologtostderr info store path log dir logs logtostderr false created ports sizerw sizerootfs labels map state status up seconds hostconfig networkmode networksettings mounts id names image cockroachdb builder imageid command bin true created ports sizerw sizerootfs labels map state status exited seconds ago hostconfig networkmode networksettings mounts id names image cockroachdb builder imageid command make test testflags v verbosity vmodule monitor tracer created ports sizerw sizerootfs labels map state status exited minutes ago hostconfig networkmode default networksettings mounts id names image cockroachdb builder imageid command build circle deps sh docker created ports sizerw sizerootfs labels map state status exited minutes ago hostconfig networkmode default networksettings mounts panic runtime error invalid memory address or nil pointer dereference panic runtime error invalid memory address or nil pointer dereference goroutine panic usr local go src runtime panic go testing trunner usr local go src testing testing go panic usr local go src runtime panic go github com cockroachdb cockroach acceptance cluster localcluster expectevent go src github com cockroachdb cockroach acceptance cluster localcluster go github com cockroachdb cockroach acceptance cluster container kill go src github com cockroachdb cockroach acceptance cluster docker go github com cockroachdb cockroach acceptance cluster localcluster stop go src github com cockroachdb cockroach acceptance cluster localcluster go github com cockroachdb cockroach acceptance cluster localcluster stoponpanic go src github com cockroachdb cockroach acceptance cluster localcluster go panic usr local go src runtime panic go github com cockroachdb cockroach acceptance cluster maybepanic go src github com cockroachdb cockroach acceptance cluster docker go github com cockroachdb cockroach acceptance cluster localcluster createroach go src github com cockroachdb cockroach acceptance cluster localcluster go github com cockroachdb cockroach acceptance cluster localcluster startnode go src github com cockroachdb cockroach acceptance cluster localcluster go github com cockroachdb cockroach acceptance cluster localcluster start go src github com cockroachdb cockroach acceptance cluster localcluster go github com cockroachdb cockroach acceptance startcluster testing trunner usr local go src testing testing go created by testing runtests usr local go src testing testing go goroutine testing runtests usr local go src testing testing go testing m run usr local go src testing testing go github com cockroachdb cockroach acceptance testmain go src github com cockroachdb cockroach acceptance main test go main main github com cockroachdb cockroach acceptance test testmain go goroutine runtime goexit usr local go src runtime asm s goroutine github com cockroachdb cockroach util log loggingt flushdaemon go src github com cockroachdb cockroach util log clog go created by github com cockroachdb cockroach util log init go src github com cockroachdb cockroach util log clog go goroutine os signal signal recv usr local go src runtime sigqueue go os signal loop usr local go src os signal signal unix go created by os signal init usr local go src os signal signal unix go goroutine github com cockroachdb cockroach acceptance testmain go src github com cockroachdb cockroach acceptance main test go created by github com cockroachdb cockroach acceptance testmain go src github com cockroachdb cockroach acceptance main test go goroutine database sql db connectionopener usr local go src database sql sql go created by database sql open usr local go src database sql sql go goroutine runtime gopark usr local go src runtime proc go runtime selectgoimpl usr local go src runtime select go runtime selectgo usr local go src runtime select go runtime ensuresigm usr local go src runtime unix go runtime goexit usr local go src runtime asm s goroutine net runtime pollwait usr local go src runtime netpoll go net polldesc wait usr local go src net fd poll runtime go net polldesc waitread usr local go src net fd poll runtime go net netfd read usr local go src net fd unix go net conn read usr local go src net net go net http persistconn readloop usr local go src net http transport go created by net http transport dialconn usr local go src net http transport go goroutine net http persistconn writeloop usr local go src net http transport go created by net http transport dialconn usr local go src net http transport go goroutine database sql db connectionopener usr local go src database sql sql go created by database sql open usr local go src database sql sql go goroutine net runtime pollwait usr local go src runtime netpoll go net polldesc wait usr local go src net fd poll runtime go net polldesc waitread usr local go src net fd poll runtime go net netfd read usr local go src net fd unix go net conn read usr local go src net net go net http persistconn readloop usr local go src net http transport go created by net http transport dialconn usr local go src net http transport go goroutine net runtime pollwait usr local go src runtime netpoll go net polldesc wait usr local go src net fd poll runtime go net polldesc waitread usr local go src net fd poll runtime go net netfd read usr local go src net fd unix go net conn read usr local go src net net go net http persistconn readloop usr local go src net http transport go created by net http transport dialconn usr local go src net http transport go goroutine net http persistconn writeloop usr local go src net http transport go created by net http transport dialconn usr local go src net http transport go goroutine net http persistconn writeloop usr local go src net http transport go created by net http transport dialconn usr local go src net http transport go goroutine database sql db connectionopener usr local go src database sql sql go created by database sql open usr local go src database sql sql go goroutine net runtime pollwait usr local go src runtime netpoll go net polldesc wait usr local go src net fd poll runtime go net polldesc waitread usr local go src net fd poll runtime go net netfd read usr local go src net fd unix go net conn read usr local go src net net go net http persistconn readloop usr local go src net http transport go created by net http transport dialconn usr local go src net http transport go goroutine net http persistconn writeloop usr local go src net http transport go created by net http transport dialconn usr local go src net http transport go goroutine net runtime pollwait usr local go src runtime netpoll go net polldesc wait usr local go src net fd poll runtime go net polldesc waitread usr local go src net fd poll runtime go net netfd read usr local go src net fd unix go net conn read usr local go src net net go net http persistconn readloop usr local go src net http transport go created by net http transport dialconn usr local go src net http transport go goroutine net runtime pollwait usr local go src runtime netpoll go net polldesc wait usr local go src net fd poll runtime go net polldesc waitread usr local go src net fd poll runtime go net netfd read usr local go src net fd unix go net conn read usr local go src net net go net http persistconn readloop usr local go src net http transport go created by net http transport dialconn usr local go src net http transport go goroutine net http persistconn writeloop usr local go src net http transport go created by net http transport dialconn usr local go src net http transport go goroutine database sql db connectionopener usr local go src database sql sql go created by database sql open usr local go src database sql sql go goroutine database sql db connectionopener usr local go src database sql sql go created by database sql open usr local go src database sql sql go goroutine net http persistconn writeloop usr local go src net http transport go created by net http transport dialconn usr local go src net http transport go goroutine database sql db connectionopener usr local go src database sql sql go created by database sql open usr local go src database sql sql go goroutine github com docker engine api client transport cancellable do go src github com docker engine api client transport cancellable cancellable go created by github com docker engine api client transport cancellable do go src github com docker engine api client transport cancellable cancellable go goroutine database sql db connectionopener usr local go src database sql sql go created by database sql open usr local go src database sql sql go ok github com cockroachdb cockroach acceptance please assign take a look and update the issue accordingly
18,078	4,232,028,963	IssuesEvent	2016-07-04 19:35:27	redox-os/ion	https://api.github.com/repos/redox-os/ion	closed	Create an examples folder and use it as part of the testing process	documentation low-hanging fruit testing	It would be helpful to have example ion scripts to both help out users and enhance testing. We could have an `examples/` directory with scripts in it. Each script would end with `.ion` and we could also have `.out` files to show the expected output for each script. Once we have this we could easily add an automatic test to run each of these and compare the actual output with the expected output. This type of integrations testing would add much more confidence for me than any amount of unit testing would.	1.0	Create an examples folder and use it as part of the testing process - It would be helpful to have example ion scripts to both help out users and enhance testing. We could have an `examples/` directory with scripts in it. Each script would end with `.ion` and we could also have `.out` files to show the expected output for each script. Once we have this we could easily add an automatic test to run each of these and compare the actual output with the expected output. This type of integrations testing would add much more confidence for me than any amount of unit testing would.	non_priority	create an examples folder and use it as part of the testing process it would be helpful to have example ion scripts to both help out users and enhance testing we could have an examples directory with scripts in it each script would end with ion and we could also have out files to show the expected output for each script once we have this we could easily add an automatic test to run each of these and compare the actual output with the expected output this type of integrations testing would add much more confidence for me than any amount of unit testing would
17,349	23,932,328,437	IssuesEvent	2022-09-10 18:36:11	349115261/LabviewFLL	https://api.github.com/repos/349115261/LabviewFLL	closed	Robot Code Issue N01	Not compatible on all	The current code only works for the correct robot main error is the lifting attachment that is putting too much stress on the one median motor so currently, even if you try to recreate the robot it does not work, trying to fix this by a code fix and psychical. @labviewadvocate ![WIN_20220905_14_56_40_Pro](https://user-images.githubusercontent.com/70164920/188502741-a34525c0-0d50-4d53-9433-65a9b1c4bf5f.jpg)	True	Robot Code Issue N01 - The current code only works for the correct robot main error is the lifting attachment that is putting too much stress on the one median motor so currently, even if you try to recreate the robot it does not work, trying to fix this by a code fix and psychical. @labviewadvocate ![WIN_20220905_14_56_40_Pro](https://user-images.githubusercontent.com/70164920/188502741-a34525c0-0d50-4d53-9433-65a9b1c4bf5f.jpg)	non_priority	robot code issue the current code only works for the correct robot main error is the lifting attachment that is putting too much stress on the one median motor so currently even if you try to recreate the robot it does not work trying to fix this by a code fix and psychical labviewadvocate
31,549	6,548,445,189	IssuesEvent	2017-09-04 21:59:36	Openki/Openki	https://api.github.com/repos/Openki/Openki	closed	Sending messages to users without registered email	Defect UX	On the users profile page, you can write a message and click the send-button. If the user didn't add their email-address, you will see a tiny error popup un the bottom right corner: Error: this user has no email [401] This is terrible UX. The messaging field should be hidden when the user does not have an email-address registered with us. Fixing this is not instant because users don't see other's email-address. So we have to send an "accepts messages" flag or something. Allowing direct messages between users of the platform would be even better.	1.0	Sending messages to users without registered email - On the users profile page, you can write a message and click the send-button. If the user didn't add their email-address, you will see a tiny error popup un the bottom right corner: Error: this user has no email [401] This is terrible UX. The messaging field should be hidden when the user does not have an email-address registered with us. Fixing this is not instant because users don't see other's email-address. So we have to send an "accepts messages" flag or something. Allowing direct messages between users of the platform would be even better.	non_priority	sending messages to users without registered email on the users profile page you can write a message and click the send button if the user didn t add their email address you will see a tiny error popup un the bottom right corner error this user has no email this is terrible ux the messaging field should be hidden when the user does not have an email address registered with us fixing this is not instant because users don t see other s email address so we have to send an accepts messages flag or something allowing direct messages between users of the platform would be even better
43,422	5,634,750,614	IssuesEvent	2017-04-05 22:10:00	CuBoulder/express	https://api.github.com/repos/CuBoulder/express	opened	WYSIWYG should strip non-breaking spaces and replace with a regular space	Design Editor Experience	## Context Our users are most likely to use non-breaking spaces to force layouts. I think it is incredibly unlikely that someone would use them correctly. We don't want users to create layouts in the wysiwyg. ## Possible Fix * When saving a node, replace ` ` with a space -------- Old comment from @kreynen, he may care to revise: ``` I'm fine changing the default text filter to strip these, but I think we need to give more advanced users options to either insert nbsp as a short code or give advanced users the option of adding CSS using something like https://www.drupal.org/project/css_injector or https://www.drupal.org/project/context_addassets ```	1.0	WYSIWYG should strip non-breaking spaces and replace with a regular space - ## Context Our users are most likely to use non-breaking spaces to force layouts. I think it is incredibly unlikely that someone would use them correctly. We don't want users to create layouts in the wysiwyg. ## Possible Fix * When saving a node, replace ` ` with a space -------- Old comment from @kreynen, he may care to revise: ``` I'm fine changing the default text filter to strip these, but I think we need to give more advanced users options to either insert nbsp as a short code or give advanced users the option of adding CSS using something like https://www.drupal.org/project/css_injector or https://www.drupal.org/project/context_addassets ```	non_priority	wysiwyg should strip non breaking spaces and replace with a regular space context our users are most likely to use non breaking spaces to force layouts i think it is incredibly unlikely that someone would use them correctly we don t want users to create layouts in the wysiwyg possible fix when saving a node replace nbsp with a space old comment from kreynen he may care to revise i m fine changing the default text filter to strip these but i think we need to give more advanced users options to either insert nbsp as a short code or give advanced users the option of adding css using something like or
328,113	28,101,876,147	IssuesEvent	2023-03-30 20:11:52	cockroachdb/cockroach	https://api.github.com/repos/cockroachdb/cockroach	closed	roachtest: schemachange/during/tpcc failed	C-test-failure O-robot O-roachtest branch-master release-blocker T-sql-schema	roachtest.schemachange/during/tpcc [failed](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Nightlies_RoachtestNightlyGceBazel/9329887?buildTab=log) with [artifacts](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Nightlies_RoachtestNightlyGceBazel/9329887?buildTab=artifacts#/schemachange/during/tpcc) on master @ [1f8024bf14433ca169e5a8c3768c5d223dc5018c](https://github.com/cockroachdb/cockroach/commits/1f8024bf14433ca169e5a8c3768c5d223dc5018c): ``` test artifacts and logs in: /artifacts/schemachange/during/tpcc/run_1 (monitor.go:127).Wait: monitor failure: monitor task failed: output in run_122327.339469682_n5_cockroach-workload-r: ./cockroach workload run tpcc --warehouses=1000 --histograms=perf/stats.json --wait=false --tolerate-errors --workers=1000 --ramp=5m0s --duration=3h0m0s --prometheus-port=2112 --pprofport=33333 {pgurl:1-4} returned: COMMAND_PROBLEM: ssh verbose log retained in ssh_122328.106497777_n5_cockroach-workload-r.log: exit status 1 ``` <p>Parameters: <code>ROACHTEST_cloud=gce</code> , <code>ROACHTEST_cpu=16</code> , <code>ROACHTEST_encrypted=false</code> , <code>ROACHTEST_ssd=0</code> </p> <details><summary>Help</summary> <p> See: [roachtest README](https://github.com/cockroachdb/cockroach/blob/master/pkg/cmd/roachtest/README.md) See: [How To Investigate $internal$](https://cockroachlabs.atlassian.net/l/c/SSSBr8c7) </p> </details> /cc @cockroachdb/sql-schema <sub> [This test on roachdash](https://roachdash.crdb.dev/?filter=status:open%20t:.schemachange/during/tpcc.&sort=title+created&display=lastcommented+project) \| [Improve this report!](https://github.com/cockroachdb/cockroach/tree/master/pkg/cmd/internal/issues) </sub> Jira issue: CRDB-26261	2.0	roachtest: schemachange/during/tpcc failed - roachtest.schemachange/during/tpcc [failed](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Nightlies_RoachtestNightlyGceBazel/9329887?buildTab=log) with [artifacts](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Nightlies_RoachtestNightlyGceBazel/9329887?buildTab=artifacts#/schemachange/during/tpcc) on master @ [1f8024bf14433ca169e5a8c3768c5d223dc5018c](https://github.com/cockroachdb/cockroach/commits/1f8024bf14433ca169e5a8c3768c5d223dc5018c): ``` test artifacts and logs in: /artifacts/schemachange/during/tpcc/run_1 (monitor.go:127).Wait: monitor failure: monitor task failed: output in run_122327.339469682_n5_cockroach-workload-r: ./cockroach workload run tpcc --warehouses=1000 --histograms=perf/stats.json --wait=false --tolerate-errors --workers=1000 --ramp=5m0s --duration=3h0m0s --prometheus-port=2112 --pprofport=33333 {pgurl:1-4} returned: COMMAND_PROBLEM: ssh verbose log retained in ssh_122328.106497777_n5_cockroach-workload-r.log: exit status 1 ``` <p>Parameters: <code>ROACHTEST_cloud=gce</code> , <code>ROACHTEST_cpu=16</code> , <code>ROACHTEST_encrypted=false</code> , <code>ROACHTEST_ssd=0</code> </p> <details><summary>Help</summary> <p> See: [roachtest README](https://github.com/cockroachdb/cockroach/blob/master/pkg/cmd/roachtest/README.md) See: [How To Investigate $internal$](https://cockroachlabs.atlassian.net/l/c/SSSBr8c7) </p> </details> /cc @cockroachdb/sql-schema <sub> [This test on roachdash](https://roachdash.crdb.dev/?filter=status:open%20t:.schemachange/during/tpcc.&sort=title+created&display=lastcommented+project) \| [Improve this report!](https://github.com/cockroachdb/cockroach/tree/master/pkg/cmd/internal/issues) </sub> Jira issue: CRDB-26261	non_priority	roachtest schemachange during tpcc failed roachtest schemachange during tpcc with on master test artifacts and logs in artifacts schemachange during tpcc run monitor go wait monitor failure monitor task failed output in run cockroach workload r cockroach workload run tpcc warehouses histograms perf stats json wait false tolerate errors workers ramp duration prometheus port pprofport pgurl returned command problem ssh verbose log retained in ssh cockroach workload r log exit status parameters roachtest cloud gce roachtest cpu roachtest encrypted false roachtest ssd help see see cc cockroachdb sql schema jira issue crdb
28,431	8,141,093,325	IssuesEvent	2018-08-21 00:06:32	typed-ember/ember-cli-typescript	https://api.github.com/repos/typed-ember/ember-cli-typescript	closed	New application blueprints	build enhancement	Create blueprints just like https://github.com/emberjs/ember-module-unification-blueprint for automatically creating and setting up a new ember application with TypeScript. Right now, if we follow the instructions on the README, we still end up needing to do lots of work to finish setting up our ember app for TypeScript. Initially created files are still .js, and converting them to .ts still results in many TypeScript errors.	1.0	New application blueprints - Create blueprints just like https://github.com/emberjs/ember-module-unification-blueprint for automatically creating and setting up a new ember application with TypeScript. Right now, if we follow the instructions on the README, we still end up needing to do lots of work to finish setting up our ember app for TypeScript. Initially created files are still .js, and converting them to .ts still results in many TypeScript errors.	non_priority	new application blueprints create blueprints just like for automatically creating and setting up a new ember application with typescript right now if we follow the instructions on the readme we still end up needing to do lots of work to finish setting up our ember app for typescript initially created files are still js and converting them to ts still results in many typescript errors
346,522	30,924,484,927	IssuesEvent	2023-08-06 10:12:15	python/cpython	https://api.github.com/repos/python/cpython	closed	Tcl and Tk versions can be desynchronized	tests topic-tkinter	For a long time Tcl and Tk versions were synchronized. But in future they can be desynchronized again, for example Tcl 9.0/Tk 8.7. Tests currently use Tcl and Tk versions interchangeably. They should be updated to test the correct version. <!-- gh-linked-prs --> ### Linked PRs * gh-107688 <!-- /gh-linked-prs -->	1.0	Tcl and Tk versions can be desynchronized - For a long time Tcl and Tk versions were synchronized. But in future they can be desynchronized again, for example Tcl 9.0/Tk 8.7. Tests currently use Tcl and Tk versions interchangeably. They should be updated to test the correct version. <!-- gh-linked-prs --> ### Linked PRs * gh-107688 <!-- /gh-linked-prs -->	non_priority	tcl and tk versions can be desynchronized for a long time tcl and tk versions were synchronized but in future they can be desynchronized again for example tcl tk tests currently use tcl and tk versions interchangeably they should be updated to test the correct version linked prs gh
53,429	13,261,597,960	IssuesEvent	2020-08-20 20:11:25	icecube-trac/tix4	https://api.github.com/repos/icecube-trac/tix4	closed	muongun - UNIX api violation (malloc) (Trac #1374)	Migrated from Trac combo simulation defect	http://software.icecube.wisc.edu/static_analysis/00_LATEST/report-c5454a.html#EndPath The behavior of `malloc()` when allocating zero bytes is implementation defined. This could result in this section of code always failing. This code should be refactored to "do what I want" from "do what I mean". <details> <summary><em>Migrated from <a href="https://code.icecube.wisc.edu/projects/icecube/ticket/1374">https://code.icecube.wisc.edu/projects/icecube/ticket/1374</a>, reported by negaand owned by jvansanten</em></summary> <p> ```json { "status": "closed", "changetime": "2016-03-18T21:14:07", "_ts": "1458335647931556", "description": "http://software.icecube.wisc.edu/static_analysis/00_LATEST/report-c5454a.html#EndPath\n\nThe behavior of `malloc()` when allocating zero bytes is implementation defined. This could result in this section of code always failing. This code should be refactored to \"do what I want\" from \"do what I mean\".", "reporter": "nega", "cc": "", "resolution": "fixed", "time": "2015-10-01T13:59:52", "component": "combo simulation", "summary": "muongun - UNIX api violation (malloc)", "priority": "normal", "keywords": "", "milestone": "", "owner": "jvansanten", "type": "defect" } ``` </p> </details>	1.0	muongun - UNIX api violation (malloc) (Trac #1374) - http://software.icecube.wisc.edu/static_analysis/00_LATEST/report-c5454a.html#EndPath The behavior of `malloc()` when allocating zero bytes is implementation defined. This could result in this section of code always failing. This code should be refactored to "do what I want" from "do what I mean". <details> <summary><em>Migrated from <a href="https://code.icecube.wisc.edu/projects/icecube/ticket/1374">https://code.icecube.wisc.edu/projects/icecube/ticket/1374</a>, reported by negaand owned by jvansanten</em></summary> <p> ```json { "status": "closed", "changetime": "2016-03-18T21:14:07", "_ts": "1458335647931556", "description": "http://software.icecube.wisc.edu/static_analysis/00_LATEST/report-c5454a.html#EndPath\n\nThe behavior of `malloc()` when allocating zero bytes is implementation defined. This could result in this section of code always failing. This code should be refactored to \"do what I want\" from \"do what I mean\".", "reporter": "nega", "cc": "", "resolution": "fixed", "time": "2015-10-01T13:59:52", "component": "combo simulation", "summary": "muongun - UNIX api violation (malloc)", "priority": "normal", "keywords": "", "milestone": "", "owner": "jvansanten", "type": "defect" } ``` </p> </details>	non_priority	muongun unix api violation malloc trac the behavior of malloc when allocating zero bytes is implementation defined this could result in this section of code always failing this code should be refactored to do what i want from do what i mean migrated from json status closed changetime ts description behavior of malloc when allocating zero bytes is implementation defined this could result in this section of code always failing this code should be refactored to do what i want from do what i mean reporter nega cc resolution fixed time component combo simulation summary muongun unix api violation malloc priority normal keywords milestone owner jvansanten type defect
28,123	5,194,332,669	IssuesEvent	2017-01-23 02:58:04	TNGSB/eWallet	https://api.github.com/repos/TNGSB/eWallet	closed	e-Wallet_Mobile App (Scan & Pay) 17012017 #19	Defect - High (Sev-2)	Defect Description : User to perform "Insufficient Balance" scenario for merchant payment. However, upon successful scanning and PIN input, the application keep on loading with end up no result. Tested with android build 20, UAT environment. Attached screenshot for POT. ![screenshot_20170117-152954](https://cloud.githubusercontent.com/assets/23113211/22011603/f51a158c-dcca-11e6-8d2d-514e8a99b59e.png) ![screenshot_20170117-153415](https://cloud.githubusercontent.com/assets/23113211/22011604/f51c6e2c-dcca-11e6-8e48-8a72e60f0bf5.png) ![screenshot_20170117-153427](https://cloud.githubusercontent.com/assets/23113211/22011605/f51c97c6-dcca-11e6-82ed-572a36688a10.png)	1.0	e-Wallet_Mobile App (Scan & Pay) 17012017 #19 - Defect Description : User to perform "Insufficient Balance" scenario for merchant payment. However, upon successful scanning and PIN input, the application keep on loading with end up no result. Tested with android build 20, UAT environment. Attached screenshot for POT. ![screenshot_20170117-152954](https://cloud.githubusercontent.com/assets/23113211/22011603/f51a158c-dcca-11e6-8d2d-514e8a99b59e.png) ![screenshot_20170117-153415](https://cloud.githubusercontent.com/assets/23113211/22011604/f51c6e2c-dcca-11e6-8e48-8a72e60f0bf5.png) ![screenshot_20170117-153427](https://cloud.githubusercontent.com/assets/23113211/22011605/f51c97c6-dcca-11e6-82ed-572a36688a10.png)	non_priority	e wallet mobile app scan pay defect description user to perform insufficient balance scenario for merchant payment however upon successful scanning and pin input the application keep on loading with end up no result tested with android build uat environment attached screenshot for pot
258,332	19,557,183,606	IssuesEvent	2022-01-03 11:16:43	bounswe/2021SpringGroup8	https://api.github.com/repos/bounswe/2021SpringGroup8	closed	Search Post and Search Community Endpoints should be well documented	documentation backend	I should document the newly created endpoints which are search post and search community.	1.0	Search Post and Search Community Endpoints should be well documented - I should document the newly created endpoints which are search post and search community.	non_priority	search post and search community endpoints should be well documented i should document the newly created endpoints which are search post and search community
67,279	9,015,768,561	IssuesEvent	2019-02-06 04:59:09	PeterCamilleri/mini_readline	https://api.github.com/repos/PeterCamilleri/mini_readline	opened	Document the creation of alternate key mappings.	documentation	The mini_readline keyboard mappings are not carved in stone. Provide documentation on how alternate keyboard mappings can be defined for application specific purposes.	1.0	Document the creation of alternate key mappings. - The mini_readline keyboard mappings are not carved in stone. Provide documentation on how alternate keyboard mappings can be defined for application specific purposes.	non_priority	document the creation of alternate key mappings the mini readline keyboard mappings are not carved in stone provide documentation on how alternate keyboard mappings can be defined for application specific purposes
19,797	26,178,927,810	IssuesEvent	2023-01-02 13:16:10	NixOS/nix	https://api.github.com/repos/NixOS/nix	closed	Release 2.12	process	Is your feature request related to a problem? Please describe. [I'm always frustrated when] fixes are merged but not released. Describe the solution you'd like Release Nix 2.12.0. Apply and release backports. Describe alternatives you've considered Treat Nix master as a rolling release and cut releases in Nixpkgs instead. Additional context Releases were supposed to be 6-weekly, but 13 weeks have passed since 2.11.0.	1.0	Release 2.12 - Is your feature request related to a problem? Please describe. [I'm always frustrated when] fixes are merged but not released. Describe the solution you'd like Release Nix 2.12.0. Apply and release backports. Describe alternatives you've considered Treat Nix master as a rolling release and cut releases in Nixpkgs instead. Additional context Releases were supposed to be 6-weekly, but 13 weeks have passed since 2.11.0.	non_priority	release is your feature request related to a problem please describe fixes are merged but not released describe the solution you d like release nix apply and release backports describe alternatives you ve considered treat nix master as a rolling release and cut releases in nixpkgs instead additional context releases were supposed to be weekly but weeks have passed since
87,973	15,791,202,262	IssuesEvent	2021-04-02 03:46:56	YJSoft/nedb	https://api.github.com/repos/YJSoft/nedb	opened	WS-2017-0247 (Low) detected in ms-0.3.0.tgz	security vulnerability	## WS-2017-0247 - Low Severity Vulnerability <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>ms-0.3.0.tgz</b></p></summary> <p>Tiny ms conversion utility</p> <p>Library home page: <a href="https://registry.npmjs.org/ms/-/ms-0.3.0.tgz">https://registry.npmjs.org/ms/-/ms-0.3.0.tgz</a></p> <p>Path to dependency file: nedb/package.json</p> <p>Path to vulnerable library: nedb/node_modules/ms/package.json</p> <p> Dependency Hierarchy: - mocha-1.4.3.tgz (Root Library) - :x: ms-0.3.0.tgz (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/YJSoft/nedb/commit/c3b8d81a383e4da24efcf18e552e70fb79fe742d">c3b8d81a383e4da24efcf18e552e70fb79fe742d</a></p> <p>Found in base branch: <b>master</b></p> </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/low_vul.png' width=19 height=20> Vulnerability Details</summary> <p> Affected versions of this package are vulnerable to Regular Expression Denial of Service (ReDoS). <p>Publish Date: 2017-04-12 <p>URL: <a href=https://github.com/zeit/ms/commit/305f2ddcd4eff7cc7c518aca6bb2b2d2daad8fef>WS-2017-0247</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>3.4</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://github.com/vercel/ms/pull/89">https://github.com/vercel/ms/pull/89</a></p> <p>Release Date: 2017-04-12</p> <p>Fix Resolution: 2.1.1</p> </p> </details> <p></p> *** Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)	True	WS-2017-0247 (Low) detected in ms-0.3.0.tgz - ## WS-2017-0247 - Low Severity Vulnerability <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>ms-0.3.0.tgz</b></p></summary> <p>Tiny ms conversion utility</p> <p>Library home page: <a href="https://registry.npmjs.org/ms/-/ms-0.3.0.tgz">https://registry.npmjs.org/ms/-/ms-0.3.0.tgz</a></p> <p>Path to dependency file: nedb/package.json</p> <p>Path to vulnerable library: nedb/node_modules/ms/package.json</p> <p> Dependency Hierarchy: - mocha-1.4.3.tgz (Root Library) - :x: ms-0.3.0.tgz (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/YJSoft/nedb/commit/c3b8d81a383e4da24efcf18e552e70fb79fe742d">c3b8d81a383e4da24efcf18e552e70fb79fe742d</a></p> <p>Found in base branch: <b>master</b></p> </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/low_vul.png' width=19 height=20> Vulnerability Details</summary> <p> Affected versions of this package are vulnerable to Regular Expression Denial of Service (ReDoS). <p>Publish Date: 2017-04-12 <p>URL: <a href=https://github.com/zeit/ms/commit/305f2ddcd4eff7cc7c518aca6bb2b2d2daad8fef>WS-2017-0247</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>3.4</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://github.com/vercel/ms/pull/89">https://github.com/vercel/ms/pull/89</a></p> <p>Release Date: 2017-04-12</p> <p>Fix Resolution: 2.1.1</p> </p> </details> <p></p> *** Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)	non_priority	ws low detected in ms tgz ws low severity vulnerability vulnerable library ms tgz tiny ms conversion utility library home page a href path to dependency file nedb package json path to vulnerable library nedb node modules ms package json dependency hierarchy mocha tgz root library x ms tgz vulnerable library found in head commit a href found in base branch master vulnerability details affected versions of this package are vulnerable to regular expression denial of service redos 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 step up your open source security game with whitesource
46,579	7,267,639,222	IssuesEvent	2018-02-20 06:27:03	FOSSEE/online_test	https://api.github.com/repos/FOSSEE/online_test	closed	Link to Production Deployment Guide document gives a 404	Type: Documentation	In README.md: ` This is a Quickstart guide to help users set up a trial instance. If you wish to deploy Yaksh in a production environment here is a Production Deployment Guide. ` That link is broken.	1.0	Link to Production Deployment Guide document gives a 404 - In README.md: ` This is a Quickstart guide to help users set up a trial instance. If you wish to deploy Yaksh in a production environment here is a Production Deployment Guide. ` That link is broken.	non_priority	link to production deployment guide document gives a in readme md this is a quickstart guide to help users set up a trial instance if you wish to deploy yaksh in a production environment here is a production deployment guide that link is broken
31,669	4,713,981,037	IssuesEvent	2016-10-14 22:02:59	phil-hutchinson/linguate	https://api.github.com/repos/phil-hutchinson/linguate	closed	DefaultRegexLexerGenerator: unit test for null builder passed to generate() / implementation	unit test	Add unit test to DefaultRegexLexerGenerator for null passed to generate as builder parameter. Should return NullPointerException. Implement fix for this unit test.	1.0	DefaultRegexLexerGenerator: unit test for null builder passed to generate() / implementation - Add unit test to DefaultRegexLexerGenerator for null passed to generate as builder parameter. Should return NullPointerException. Implement fix for this unit test.	non_priority	defaultregexlexergenerator unit test for null builder passed to generate implementation add unit test to defaultregexlexergenerator for null passed to generate as builder parameter should return nullpointerexception implement fix for this unit test
196,976	14,897,733,540	IssuesEvent	2021-01-21 12:10:45	openmls/openmls	https://api.github.com/repos/openmls/openmls	closed	Create testing framework for managed group API	P3 tests	It would be useful to have a testing framework for the group API similar to the existing one for the low-level API. That would make testing of more complex cases easier and it should also be relatively easy to do.	1.0	Create testing framework for managed group API - It would be useful to have a testing framework for the group API similar to the existing one for the low-level API. That would make testing of more complex cases easier and it should also be relatively easy to do.	non_priority	create testing framework for managed group api it would be useful to have a testing framework for the group api similar to the existing one for the low level api that would make testing of more complex cases easier and it should also be relatively easy to do
134,030	12,560,188,388	IssuesEvent	2020-06-07 21:18:48	civictechindex/website	https://api.github.com/repos/civictechindex/website	closed	GitHub API Walkthrough	documentation	### Overview Understand the GitHub API integration ### Action Items - [x] Get an idea of the framework using the test link - [x] Refer and get hands-on with the Brigade Project Status Index Board - [x] Read about GitHub API: developer documentation ### Resources [Testing the GitHub API](https://hackforla.github.io/github-api-test/) [Brigade Project Status Index Board ](https://github.com/civictechindex/brigade-project-index-statusboard) [GitHub API Docs](https://developer.github.com/v3/)	1.0	GitHub API Walkthrough - ### Overview Understand the GitHub API integration ### Action Items - [x] Get an idea of the framework using the test link - [x] Refer and get hands-on with the Brigade Project Status Index Board - [x] Read about GitHub API: developer documentation ### Resources [Testing the GitHub API](https://hackforla.github.io/github-api-test/) [Brigade Project Status Index Board ](https://github.com/civictechindex/brigade-project-index-statusboard) [GitHub API Docs](https://developer.github.com/v3/)	non_priority	github api walkthrough overview understand the github api integration action items get an idea of the framework using the test link refer and get hands on with the brigade project status index board read about github api developer documentation resources
28,966	11,706,039,258	IssuesEvent	2020-03-07 19:32:28	vlaship/spark-streaming	https://api.github.com/repos/vlaship/spark-streaming	opened	CVE-2020-9546 (Medium) detected in jackson-databind-2.6.5.jar	security vulnerability	## CVE-2020-9546 - Medium Severity Vulnerability <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>jackson-databind-2.6.5.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: /tmp/ws-scm/spark-streaming/build.gradle</p> <p>Path to vulnerable library: /root/.gradle/caches/modules-2/files-2.1/com.fasterxml.jackson.core/jackson-databind/2.6.5/d50be1723a09befd903887099ff2014ea9020333/jackson-databind-2.6.5.jar,/root/.gradle/caches/modules-2/files-2.1/com.fasterxml.jackson.core/jackson-databind/2.6.5/d50be1723a09befd903887099ff2014ea9020333/jackson-databind-2.6.5.jar</p> <p> Dependency Hierarchy: - spark-streaming_2.11-2.2.0.jar (Root Library) - spark-core_2.11-2.2.0.jar - :x: jackson-databind-2.6.5.jar (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/vlaship/spark-streaming/commit/8193fe8b5a8089e67347f5851a02c41ea5056fb0">8193fe8b5a8089e67347f5851a02c41ea5056fb0</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> FasterXML jackson-databind 2.x before 2.9.10.4 mishandles the interaction between serialization gadgets and typing, related to org.apache.hadoop.shaded.com.zaxxer.hikari.HikariConfig (aka shaded hikari-config). <p>Publish Date: 2020-03-02 <p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-9546>CVE-2020-9546</a></p> </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 2 Score Details (<b>5.0</b>)</summary> <p> Base Score Metrics not available</p> </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary> <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-9546">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-9546</a></p> <p>Release Date: 2020-03-02</p> <p>Fix Resolution: com.fasterxml.jackson.core:jackson-databind:2.10.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-2020-9546 (Medium) detected in jackson-databind-2.6.5.jar - ## CVE-2020-9546 - Medium Severity Vulnerability <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>jackson-databind-2.6.5.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: /tmp/ws-scm/spark-streaming/build.gradle</p> <p>Path to vulnerable library: /root/.gradle/caches/modules-2/files-2.1/com.fasterxml.jackson.core/jackson-databind/2.6.5/d50be1723a09befd903887099ff2014ea9020333/jackson-databind-2.6.5.jar,/root/.gradle/caches/modules-2/files-2.1/com.fasterxml.jackson.core/jackson-databind/2.6.5/d50be1723a09befd903887099ff2014ea9020333/jackson-databind-2.6.5.jar</p> <p> Dependency Hierarchy: - spark-streaming_2.11-2.2.0.jar (Root Library) - spark-core_2.11-2.2.0.jar - :x: jackson-databind-2.6.5.jar (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/vlaship/spark-streaming/commit/8193fe8b5a8089e67347f5851a02c41ea5056fb0">8193fe8b5a8089e67347f5851a02c41ea5056fb0</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> FasterXML jackson-databind 2.x before 2.9.10.4 mishandles the interaction between serialization gadgets and typing, related to org.apache.hadoop.shaded.com.zaxxer.hikari.HikariConfig (aka shaded hikari-config). <p>Publish Date: 2020-03-02 <p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-9546>CVE-2020-9546</a></p> </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 2 Score Details (<b>5.0</b>)</summary> <p> Base Score Metrics not available</p> </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary> <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-9546">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-9546</a></p> <p>Release Date: 2020-03-02</p> <p>Fix Resolution: com.fasterxml.jackson.core:jackson-databind:2.10.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 jackson databind jar cve medium 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 tmp ws scm spark streaming build gradle path to vulnerable library root gradle caches modules files com fasterxml jackson core jackson databind jackson databind jar root gradle caches modules files com fasterxml jackson core jackson databind jackson databind jar dependency hierarchy spark streaming jar root library spark core jar x jackson databind jar vulnerable library found in head commit a href vulnerability details fasterxml jackson databind x before mishandles the interaction between serialization gadgets and typing related to org apache hadoop shaded com zaxxer hikari hikariconfig aka shaded hikari config 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 com fasterxml jackson core jackson databind step up your open source security game with whitesource
245,090	18,772,225,224	IssuesEvent	2021-11-07 02:32:01	TrevorDBrown/LinkFreePlus	https://api.github.com/repos/TrevorDBrown/LinkFreePlus	opened	Need Documentation	documentation	JSON config files (linkfree.json, themes.json) are available as samples, but no formal documentation is written.	1.0	Need Documentation - JSON config files (linkfree.json, themes.json) are available as samples, but no formal documentation is written.	non_priority	need documentation json config files linkfree json themes json are available as samples but no formal documentation is written
198,965	15,017,331,615	IssuesEvent	2021-02-01 10:42:41	elastic/kibana	https://api.github.com/repos/elastic/kibana	opened	Investigate timelion app functional test failure on cloud	Feature:Timelion Team:KibanaApp bug test-cloud	This timelion test `test/functional/apps/timelion/_expression_typeahead,js` fails a lot on cloud. Specifically the test that creates the problem is the `should show field suggestions for split argument when index pattern set`. The problem described [here](https://github.com/elastic/kibana/pull/89538) is that when the split method is applied the suggestions list has 53 instead of 51 elements. This happens on 7.11 but it may happens on other versions too so: - We need to investigate why the suggestions list returns a different number - When the problem is solved we should change these lines `expect(suggestions.length).not.to.eql(0);` to test the correct suggestions length.	1.0	Investigate timelion app functional test failure on cloud - This timelion test `test/functional/apps/timelion/_expression_typeahead,js` fails a lot on cloud. Specifically the test that creates the problem is the `should show field suggestions for split argument when index pattern set`. The problem described [here](https://github.com/elastic/kibana/pull/89538) is that when the split method is applied the suggestions list has 53 instead of 51 elements. This happens on 7.11 but it may happens on other versions too so: - We need to investigate why the suggestions list returns a different number - When the problem is solved we should change these lines `expect(suggestions.length).not.to.eql(0);` to test the correct suggestions length.	non_priority	investigate timelion app functional test failure on cloud this timelion test test functional apps timelion expression typeahead js fails a lot on cloud specifically the test that creates the problem is the should show field suggestions for split argument when index pattern set the problem described is that when the split method is applied the suggestions list has instead of elements this happens on but it may happens on other versions too so we need to investigate why the suggestions list returns a different number when the problem is solved we should change these lines expect suggestions length not to eql to test the correct suggestions length
2,987	3,755,595,724	IssuesEvent	2016-03-12 19:29:56	Rdatatable/data.table	https://api.github.com/repos/Rdatatable/data.table	closed	unkeyed join could use existing indexes	Enhancement performance	According to the title of #1130 Implement joins using secondary keys, I assume unkeyed join using `on` already uses indexes so it don't have to resort data to join. But it seems to not use existing index. ```r library(data.table) options(datatable.verbose=TRUE) options(datatable.auto.index=TRUE) dt1 = data.table(a=letters[c(3L,1L,2L)]) dt2 = data.table(a=letters[c(2L,1L,3L)]) set2keyv(dt1, "a") # forder took 0 sec set2keyv(dt2, "a") # forder took 0 sec dt1[dt2, on = c("a" = "a")] # Starting bmerge ...done in 0 secs # a # 1: b # 2: a # 3: c ``` If it does use index please turn that FR to extend `verbose=TRUE` to mention that.	True	unkeyed join could use existing indexes - According to the title of #1130 Implement joins using secondary keys, I assume unkeyed join using `on` already uses indexes so it don't have to resort data to join. But it seems to not use existing index. ```r library(data.table) options(datatable.verbose=TRUE) options(datatable.auto.index=TRUE) dt1 = data.table(a=letters[c(3L,1L,2L)]) dt2 = data.table(a=letters[c(2L,1L,3L)]) set2keyv(dt1, "a") # forder took 0 sec set2keyv(dt2, "a") # forder took 0 sec dt1[dt2, on = c("a" = "a")] # Starting bmerge ...done in 0 secs # a # 1: b # 2: a # 3: c ``` If it does use index please turn that FR to extend `verbose=TRUE` to mention that.	non_priority	unkeyed join could use existing indexes according to the title of implement joins using secondary keys i assume unkeyed join using on already uses indexes so it don t have to resort data to join but it seems to not use existing index r library data table options datatable verbose true options datatable auto index true data table a letters data table a letters a forder took sec a forder took sec starting bmerge done in secs a b a c if it does use index please turn that fr to extend verbose true to mention that
76,946	15,496,235,964	IssuesEvent	2021-03-11 02:18:23	n-devs/Fiction	https://api.github.com/repos/n-devs/Fiction	opened	CVE-2019-20149 (High) detected in kind-of-6.0.2.tgz	security vulnerability	## CVE-2019-20149 - High Severity Vulnerability <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>kind-of-6.0.2.tgz</b></p></summary> <p>Get the native type of a value.</p> <p>Library home page: <a href="https://registry.npmjs.org/kind-of/-/kind-of-6.0.2.tgz">https://registry.npmjs.org/kind-of/-/kind-of-6.0.2.tgz</a></p> <p>Path to dependency file: /Fiction/package.json</p> <p>Path to vulnerable library: Fiction/node_modules/http-proxy-middleware/node_modules/kind-of/package.json</p> <p> Dependency Hierarchy: - react-scripts-2.1.1.tgz (Root Library) - sass-loader-7.1.0.tgz - clone-deep-2.0.2.tgz - :x: kind-of-6.0.2.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> ctorName in index.js in kind-of v6.0.2 allows external user input to overwrite certain internal attributes via a conflicting name, as demonstrated by 'constructor': {'name':'Symbol'}. Hence, a crafted payload can overwrite this builtin attribute to manipulate the type detection result. <p>Publish Date: 2019-12-30 <p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-20149>CVE-2019-20149</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="http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2019-20149">http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2019-20149</a></p> <p>Release Date: 2019-12-30</p> <p>Fix Resolution: 6.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-2019-20149 (High) detected in kind-of-6.0.2.tgz - ## CVE-2019-20149 - High Severity Vulnerability <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>kind-of-6.0.2.tgz</b></p></summary> <p>Get the native type of a value.</p> <p>Library home page: <a href="https://registry.npmjs.org/kind-of/-/kind-of-6.0.2.tgz">https://registry.npmjs.org/kind-of/-/kind-of-6.0.2.tgz</a></p> <p>Path to dependency file: /Fiction/package.json</p> <p>Path to vulnerable library: Fiction/node_modules/http-proxy-middleware/node_modules/kind-of/package.json</p> <p> Dependency Hierarchy: - react-scripts-2.1.1.tgz (Root Library) - sass-loader-7.1.0.tgz - clone-deep-2.0.2.tgz - :x: kind-of-6.0.2.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> ctorName in index.js in kind-of v6.0.2 allows external user input to overwrite certain internal attributes via a conflicting name, as demonstrated by 'constructor': {'name':'Symbol'}. Hence, a crafted payload can overwrite this builtin attribute to manipulate the type detection result. <p>Publish Date: 2019-12-30 <p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-20149>CVE-2019-20149</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="http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2019-20149">http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2019-20149</a></p> <p>Release Date: 2019-12-30</p> <p>Fix Resolution: 6.0.3</p> </p> </details> <p></p> *** Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)	non_priority	cve high detected in kind of tgz cve high severity vulnerability vulnerable library kind of tgz get the native type of a value library home page a href path to dependency file fiction package json path to vulnerable library fiction node modules http proxy middleware node modules kind of package json dependency hierarchy react scripts tgz root library sass loader tgz clone deep tgz x kind of tgz vulnerable library vulnerability details ctorname in index js in kind of allows external user input to overwrite certain internal attributes via a conflicting name as demonstrated by constructor name symbol hence a crafted payload can overwrite this builtin attribute to manipulate the type detection result 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 step up your open source security game with whitesource
19,750	6,759,760,056	IssuesEvent	2017-10-24 18:13:20	grpc/grpc	https://api.github.com/repos/grpc/grpc	opened	timeout error: json_run_localhost:cpp_protobuf_async_streaming_from_server_qps_unconstrained_secure GRPC_POLL_STRATEGY=epollsig	infra/BUILDPONY	https://sponge.corp.google.com/target?id=73e2455a-238a-4911-90e2-dcae5f88a340&target=github/grpc/c%2B%2B_linux_opt_native&searchFor=&show=ALL&sortBy=STATUS ``` Timeout 79 25255 writing.cc:142] ipv6:[::1]:56962:0x7fe2f400f100 stream 35 stalled by transport [fc:pending=5:flowed=41935:peer_initwin=4194304:t_win=0:s_win=4152374:s_delta=-41930] D1023 22:11:09.072941089 25255 writing.cc:142] ipv6:[::1]:56962:0x7fe2f400f100 stream 173 stalled by transport [fc:pending=5:flowed=41970:peer_initwin=4194304:t_win=0:s_win=4152339:s_delta=-41965] D1023 22:11:09.072945056 25255 writing.cc:142] ipv6:[::1]:56962:0x7fe2f400f100 stream 113 stalled by transport [fc:pending=5:flowed=41955:peer_initwin=4194304:t_win=0:s_win=4152354:s_delta=-41950] D1023 22:11:09.072949000 25255 writing.cc:142] ipv6:[::1]:56962:0x7fe2f400f100 stream 43 stalled by transport [fc:pending=5:flowed=41960:peer_initwin=4194304:t_win=0:s_win=4152349:s_delta=-41955] D1023 22:11:09.072952841 25255 writing.cc:142] ipv6:[::1]:56962:0x7fe2f400f100 stream 15 stalled by transport [fc:pending=5:flowed=41950:peer_initwin=4194304:t_win=0:s_win=4152359:s_delta=-41945] D1023 22:11:09.072956694 25255 writing.cc:142] ipv6:[::1]:56962:0x7fe2f400f100 stream 31 stalled by transport [fc:pending=5:flowed=41935:peer_initwin=4194304:t_win=0:s_win=4152374:s_delta=-41930] D1023 22:11:09.072960598 25255 writing.cc:142] ipv6:[::1]:56962:0x7fe2f400f100 stream 171 stalled by transport [fc:pending=5:flowed=41960:peer_initwin=4194304:t_win=0:s_win=4152349:s_delta=-41955] D1023 22:11:09.072964545 25255 writing.cc:142] ipv6:[::1]:56962:0x7fe2f400f100 stream 111 stalled by transport [fc:pending=5:flowed=41965:peer_initwin=4194304:t_win=0:s_win=4152344:s_delta=-41960] D1023 22:11:09.072968399 25255 writing.cc:142] ipv6:[::1]:56962:0x7fe2f400f100 stream 61 stalled by transport [fc:pending=5:flowed=41975:peer_initwin=4194304:t_win=0:s_win=4152334:s_delta=-41970] D1023 22:11:09.072972285 25255 writing.cc:142] ipv6:[::1]:56962:0x7fe2f400f100 stream 131 stalled by transport [fc:pending=5:flowed=41905:peer_initwin=4194304:t_win=0:s_win=4152404:s_delta=-41900] D1023 22:11:09.072976219 25255 writing.cc:142] ipv6:[::1]:56962:0x7fe2f400f100 stream 37 stalled by transport [fc:pending=5:flowed=41950:peer_initwin=4194304:t_win=0:s_win=4152359:s_delta=-41945] D1023 22:11:09.072980117 25255 writing.cc:142] ipv6:[::1]:56962:0x7fe2f400f100 stream 139 stalled by transport [fc:pending=5:flowed=41940:peer_initwin=4194304:t_win=0:s_win=4152369:s_delta=-41935] D1023 22:11:09.072983981 25255 writing.cc:142] ipv6:[::1]:56962:0x7fe2f400f100 stream 97 stalled by transport [fc:pending=5:flowed=41950:peer_initwin=4194304:t_win=0:s_win=4152359:s_delta=-41945] D1023 22:11:09.072987897 25255 writing.cc:142] ipv6:[::1]:56962:0x7fe2f400f100 stream 101 stalled by transport [fc:pending=5:flowed=41950:peer_initwin=4194304:t_win=0:s_win=4152359:s_delta=-41945] D1023 22:11:09.072993828 25255 writing.cc:142] ipv6:[::1]:56962:0x7fe2f400f100 stream 187 stalled by transport [fc:pending=5:flowed=41965:peer_initwin=4194304:t_win=0:s_win=4152344:s_delta=-41960] D1023 22:11:09.072999159 25255 writing.cc:142] ipv6:[::1]:56962:0x7fe2f400f100 stream 95 stalled by transport [fc:pending=5:flowed=41955:peer_initwin=4194304:t_win=0:s_win=4152354:s_delta=-41950] D1023 22:11:09.073003294 25255 writing.cc:142] ipv6:[::1]:56962:0x7fe2f400f100 stream 119 stalled by transport [fc:pending=5:flowed=41845:peer_initwin=4194304:t_win=0:s_win=4152464:s_delta=-41840] D1023 22:11:09.073007269 25255 writing.cc:142] ipv6:[::1]:56962:0x7fe2f400f100 stream 17 stalled by transport [fc:pending=5:flowed=41990:peer_initwin=4194304:t_win=0:s_win=4152319:s_delta=-41985] D1023 22:11:09.073011184 25255 writing.cc:142] ipv6:[::1]:56962:0x7fe2f400f100 stream 65 stalled by transport [fc:pending=5:flowed=41980:peer_initwin=4194304:t_win=0:s_win=4152329:s_delta=-41975] D1023 22:11:09.073015174 25255 writing.cc:142] ipv6:[::1]:56962:0x7fe2f400f100 stream 177 stalled by transport [fc:pending=5:flowed=41890:peer_initwin=4194304:t_win=0:s_win=4152419:s_delta=-41885] D1023 22:11:09.073021730 25255 writing.cc:142] ipv6:[::1]:56962:0x7fe2f400f100 stream 81 stalled by transport [fc:pending=5:flowed=41980:peer_initwin=4194304:t_win=0:s_win=4152329:s_delta=-41975] D1023 22:11:09.073025616 25255 writing.cc:142] ipv6:[::1]:56962:0x7fe2f400f100 stream 87 stalled by transport [fc:pending=5:flowed=41950:peer_initwin=4194304:t_win=0:s_win=4152359:s_delta=-41945] D1023 22:11:09.073029413 25255 writing.cc:142] ipv6:[::1]:56962:0x7fe2f400f100 stream 183 stalled by transport [fc:pending=5:flowed=41945:peer_initwin=4194304:t_win=0:s_win=4152364:s_delta=-41940] D1023 22:11:09.073033190 25255 writing.cc:142] ipv6:[::1]:56962:0x7fe2f400f100 stream 191 stalled by transport [fc:pending=5:flowed=41975:peer_initwin=4194304:t_win=0:s_win=4152334:s_delta=-41970] D1023 22:11:09.073036981 25255 writing.cc:142] ipv6:[::1]:56962:0x7fe2f400f100 stream 175 stalled by transport [fc:pending=5:flowed=41955:peer_initwin=4194304:t_win=0:s_win=4152354:s_delta=-41950] D1023 22:11:09.073040753 25255 writing.cc:142] ipv6:[::1]:56962:0x7fe2f400f100 stream 23 stalled by transport [fc:pending=5:flowed=41930:peer_initwin=4194304:t_win=0:s_win=4152379:s_delta=-41925] D1023 22:11:09.073044498 25255 writing.cc:142] ipv6:[::1]:56962:0x7fe2f400f100 stream 107 stalled by transport [fc:pending=5:flowed=41975:peer_initwin=4194304:t_win=0:s_win=4152334:s_delta=-41970] D1023 22:11:09.073048260 25255 writing.cc:142] ipv6:[::1]:56962:0x7fe2f400f100 stream 165 stalled by transport [fc:pending=5:flowed=41940:peer_initwin=4194304:t_win=0:s_win=4152369:s_delta=-41935] D1023 22:11:09.073051943 25255 writing.cc:142] ipv6:[::1]:56962:0x7fe2f400f100 stream 145 stalled by transport [fc:pending=5:flowed=41930:peer_initwin=4194304:t_win=0:s_win=4152379:s_delta=-41925] D1023 22:11:09.073055723 25255 writing.cc:142] ipv6:[::1]:56962:0x7fe2f400f100 stream 179 stalled by transport [fc:pending=5:flowed=41900:peer_initwin=4194304:t_win=0:s_win=4152409:s_delta=-41895] D1023 22:11:09.073059505 25255 writing.cc:142] ipv6:[::1]:56962:0x7fe2f400f100 stream 77 stalled by transport [fc:pending=5:flowed=41965:peer_initwin=4194304:t_win=0:s_win=4152344:s_delta=-41960] D1023 22:11:09.073063318 25255 writing.cc:142] ipv6:[::1]:56962:0x7fe2f400f100 stream 109 stalled by transport [fc:pending=5:flowed=41960:peer_initwin=4194304:t_win=0:s_win=4152349:s_delta=-41955] D1023 22:11:09.073067060 25255 writing.cc:142] ipv6:[::1]:56962:0x7fe2f400f100 stream 161 stalled by transport [fc:pending=5:flowed=41980:peer_initwin=4194304:t_win=0:s_win=4152329:s_delta=-41975] D1023 22:11:09.073117232 25119 writing.cc:142] ipv6:[::1]:56962:0x7fe2f400f100 stream 115 stalled by transport [fc:pending=5:flowed=41975:peer_initwin=4194304:t_win=0:s_win=4152334:s_delta=-41970] D1023 22:11:09.073177506 25214 writing.cc:142] ipv6:[::1]:56962:0x7fe2f400f100 stream 137 stalled by transport [fc:pending=5:flowed=41935:peer_initwin=4194304:t_win=0:s_win=4152374:s_delta=-41930] D1023 22:11:09.073196957 25214 writing.cc:142] ipv6:[::1]:56962:0x7fe2f400f100 stream 63 stalled by transport [fc:pending=5:flowed=41965:peer_initwin=4194304:t_win=0:s_win=4152344:s_delta=-41960] D1023 22:11:09.073203017 25214 writing.cc:142] ipv6:[::1]:56962:0x7fe2f400f100 stream 147 stalled by transport [fc:pending=5:flowed=41925:peer_initwin=4194304:t_win=0:s_win=4152384:s_delta=-41920] D1023 22:11:09.073207114 25214 writing.cc:142] ipv6:[::1]:56962:0x7fe2f400f100 stream 123 stalled by transport [fc:pending=5:flowed=41895:peer_initwin=4194304:t_win=0:s_win=4152414:s_delta=-41890] D1023 22:11:09.073210961 25214 writing.cc:142] ipv6:[::1]:56962:0x7fe2f400f100 stream 103 stalled by transport [fc:pending=5:flowed=41935:peer_initwin=4194304:t_win=0:s_win=4152374:s_delta=-41930] ```	1.0	timeout error: json_run_localhost:cpp_protobuf_async_streaming_from_server_qps_unconstrained_secure GRPC_POLL_STRATEGY=epollsig - https://sponge.corp.google.com/target?id=73e2455a-238a-4911-90e2-dcae5f88a340&target=github/grpc/c%2B%2B_linux_opt_native&searchFor=&show=ALL&sortBy=STATUS ``` Timeout 79 25255 writing.cc:142] ipv6:[::1]:56962:0x7fe2f400f100 stream 35 stalled by transport [fc:pending=5:flowed=41935:peer_initwin=4194304:t_win=0:s_win=4152374:s_delta=-41930] D1023 22:11:09.072941089 25255 writing.cc:142] ipv6:[::1]:56962:0x7fe2f400f100 stream 173 stalled by transport [fc:pending=5:flowed=41970:peer_initwin=4194304:t_win=0:s_win=4152339:s_delta=-41965] D1023 22:11:09.072945056 25255 writing.cc:142] ipv6:[::1]:56962:0x7fe2f400f100 stream 113 stalled by transport [fc:pending=5:flowed=41955:peer_initwin=4194304:t_win=0:s_win=4152354:s_delta=-41950] D1023 22:11:09.072949000 25255 writing.cc:142] ipv6:[::1]:56962:0x7fe2f400f100 stream 43 stalled by transport [fc:pending=5:flowed=41960:peer_initwin=4194304:t_win=0:s_win=4152349:s_delta=-41955] D1023 22:11:09.072952841 25255 writing.cc:142] ipv6:[::1]:56962:0x7fe2f400f100 stream 15 stalled by transport [fc:pending=5:flowed=41950:peer_initwin=4194304:t_win=0:s_win=4152359:s_delta=-41945] D1023 22:11:09.072956694 25255 writing.cc:142] ipv6:[::1]:56962:0x7fe2f400f100 stream 31 stalled by transport [fc:pending=5:flowed=41935:peer_initwin=4194304:t_win=0:s_win=4152374:s_delta=-41930] D1023 22:11:09.072960598 25255 writing.cc:142] ipv6:[::1]:56962:0x7fe2f400f100 stream 171 stalled by transport [fc:pending=5:flowed=41960:peer_initwin=4194304:t_win=0:s_win=4152349:s_delta=-41955] D1023 22:11:09.072964545 25255 writing.cc:142] ipv6:[::1]:56962:0x7fe2f400f100 stream 111 stalled by transport [fc:pending=5:flowed=41965:peer_initwin=4194304:t_win=0:s_win=4152344:s_delta=-41960] D1023 22:11:09.072968399 25255 writing.cc:142] ipv6:[::1]:56962:0x7fe2f400f100 stream 61 stalled by transport [fc:pending=5:flowed=41975:peer_initwin=4194304:t_win=0:s_win=4152334:s_delta=-41970] D1023 22:11:09.072972285 25255 writing.cc:142] ipv6:[::1]:56962:0x7fe2f400f100 stream 131 stalled by transport [fc:pending=5:flowed=41905:peer_initwin=4194304:t_win=0:s_win=4152404:s_delta=-41900] D1023 22:11:09.072976219 25255 writing.cc:142] ipv6:[::1]:56962:0x7fe2f400f100 stream 37 stalled by transport [fc:pending=5:flowed=41950:peer_initwin=4194304:t_win=0:s_win=4152359:s_delta=-41945] D1023 22:11:09.072980117 25255 writing.cc:142] ipv6:[::1]:56962:0x7fe2f400f100 stream 139 stalled by transport [fc:pending=5:flowed=41940:peer_initwin=4194304:t_win=0:s_win=4152369:s_delta=-41935] D1023 22:11:09.072983981 25255 writing.cc:142] ipv6:[::1]:56962:0x7fe2f400f100 stream 97 stalled by transport [fc:pending=5:flowed=41950:peer_initwin=4194304:t_win=0:s_win=4152359:s_delta=-41945] D1023 22:11:09.072987897 25255 writing.cc:142] ipv6:[::1]:56962:0x7fe2f400f100 stream 101 stalled by transport [fc:pending=5:flowed=41950:peer_initwin=4194304:t_win=0:s_win=4152359:s_delta=-41945] D1023 22:11:09.072993828 25255 writing.cc:142] ipv6:[::1]:56962:0x7fe2f400f100 stream 187 stalled by transport [fc:pending=5:flowed=41965:peer_initwin=4194304:t_win=0:s_win=4152344:s_delta=-41960] D1023 22:11:09.072999159 25255 writing.cc:142] ipv6:[::1]:56962:0x7fe2f400f100 stream 95 stalled by transport [fc:pending=5:flowed=41955:peer_initwin=4194304:t_win=0:s_win=4152354:s_delta=-41950] D1023 22:11:09.073003294 25255 writing.cc:142] ipv6:[::1]:56962:0x7fe2f400f100 stream 119 stalled by transport [fc:pending=5:flowed=41845:peer_initwin=4194304:t_win=0:s_win=4152464:s_delta=-41840] D1023 22:11:09.073007269 25255 writing.cc:142] ipv6:[::1]:56962:0x7fe2f400f100 stream 17 stalled by transport [fc:pending=5:flowed=41990:peer_initwin=4194304:t_win=0:s_win=4152319:s_delta=-41985] D1023 22:11:09.073011184 25255 writing.cc:142] ipv6:[::1]:56962:0x7fe2f400f100 stream 65 stalled by transport [fc:pending=5:flowed=41980:peer_initwin=4194304:t_win=0:s_win=4152329:s_delta=-41975] D1023 22:11:09.073015174 25255 writing.cc:142] ipv6:[::1]:56962:0x7fe2f400f100 stream 177 stalled by transport [fc:pending=5:flowed=41890:peer_initwin=4194304:t_win=0:s_win=4152419:s_delta=-41885] D1023 22:11:09.073021730 25255 writing.cc:142] ipv6:[::1]:56962:0x7fe2f400f100 stream 81 stalled by transport [fc:pending=5:flowed=41980:peer_initwin=4194304:t_win=0:s_win=4152329:s_delta=-41975] D1023 22:11:09.073025616 25255 writing.cc:142] ipv6:[::1]:56962:0x7fe2f400f100 stream 87 stalled by transport [fc:pending=5:flowed=41950:peer_initwin=4194304:t_win=0:s_win=4152359:s_delta=-41945] D1023 22:11:09.073029413 25255 writing.cc:142] ipv6:[::1]:56962:0x7fe2f400f100 stream 183 stalled by transport [fc:pending=5:flowed=41945:peer_initwin=4194304:t_win=0:s_win=4152364:s_delta=-41940] D1023 22:11:09.073033190 25255 writing.cc:142] ipv6:[::1]:56962:0x7fe2f400f100 stream 191 stalled by transport [fc:pending=5:flowed=41975:peer_initwin=4194304:t_win=0:s_win=4152334:s_delta=-41970] D1023 22:11:09.073036981 25255 writing.cc:142] ipv6:[::1]:56962:0x7fe2f400f100 stream 175 stalled by transport [fc:pending=5:flowed=41955:peer_initwin=4194304:t_win=0:s_win=4152354:s_delta=-41950] D1023 22:11:09.073040753 25255 writing.cc:142] ipv6:[::1]:56962:0x7fe2f400f100 stream 23 stalled by transport [fc:pending=5:flowed=41930:peer_initwin=4194304:t_win=0:s_win=4152379:s_delta=-41925] D1023 22:11:09.073044498 25255 writing.cc:142] ipv6:[::1]:56962:0x7fe2f400f100 stream 107 stalled by transport [fc:pending=5:flowed=41975:peer_initwin=4194304:t_win=0:s_win=4152334:s_delta=-41970] D1023 22:11:09.073048260 25255 writing.cc:142] ipv6:[::1]:56962:0x7fe2f400f100 stream 165 stalled by transport [fc:pending=5:flowed=41940:peer_initwin=4194304:t_win=0:s_win=4152369:s_delta=-41935] D1023 22:11:09.073051943 25255 writing.cc:142] ipv6:[::1]:56962:0x7fe2f400f100 stream 145 stalled by transport [fc:pending=5:flowed=41930:peer_initwin=4194304:t_win=0:s_win=4152379:s_delta=-41925] D1023 22:11:09.073055723 25255 writing.cc:142] ipv6:[::1]:56962:0x7fe2f400f100 stream 179 stalled by transport [fc:pending=5:flowed=41900:peer_initwin=4194304:t_win=0:s_win=4152409:s_delta=-41895] D1023 22:11:09.073059505 25255 writing.cc:142] ipv6:[::1]:56962:0x7fe2f400f100 stream 77 stalled by transport [fc:pending=5:flowed=41965:peer_initwin=4194304:t_win=0:s_win=4152344:s_delta=-41960] D1023 22:11:09.073063318 25255 writing.cc:142] ipv6:[::1]:56962:0x7fe2f400f100 stream 109 stalled by transport [fc:pending=5:flowed=41960:peer_initwin=4194304:t_win=0:s_win=4152349:s_delta=-41955] D1023 22:11:09.073067060 25255 writing.cc:142] ipv6:[::1]:56962:0x7fe2f400f100 stream 161 stalled by transport [fc:pending=5:flowed=41980:peer_initwin=4194304:t_win=0:s_win=4152329:s_delta=-41975] D1023 22:11:09.073117232 25119 writing.cc:142] ipv6:[::1]:56962:0x7fe2f400f100 stream 115 stalled by transport [fc:pending=5:flowed=41975:peer_initwin=4194304:t_win=0:s_win=4152334:s_delta=-41970] D1023 22:11:09.073177506 25214 writing.cc:142] ipv6:[::1]:56962:0x7fe2f400f100 stream 137 stalled by transport [fc:pending=5:flowed=41935:peer_initwin=4194304:t_win=0:s_win=4152374:s_delta=-41930] D1023 22:11:09.073196957 25214 writing.cc:142] ipv6:[::1]:56962:0x7fe2f400f100 stream 63 stalled by transport [fc:pending=5:flowed=41965:peer_initwin=4194304:t_win=0:s_win=4152344:s_delta=-41960] D1023 22:11:09.073203017 25214 writing.cc:142] ipv6:[::1]:56962:0x7fe2f400f100 stream 147 stalled by transport [fc:pending=5:flowed=41925:peer_initwin=4194304:t_win=0:s_win=4152384:s_delta=-41920] D1023 22:11:09.073207114 25214 writing.cc:142] ipv6:[::1]:56962:0x7fe2f400f100 stream 123 stalled by transport [fc:pending=5:flowed=41895:peer_initwin=4194304:t_win=0:s_win=4152414:s_delta=-41890] D1023 22:11:09.073210961 25214 writing.cc:142] ipv6:[::1]:56962:0x7fe2f400f100 stream 103 stalled by transport [fc:pending=5:flowed=41935:peer_initwin=4194304:t_win=0:s_win=4152374:s_delta=-41930] ```	non_priority	timeout error json run localhost cpp protobuf async streaming from server qps unconstrained secure grpc poll strategy epollsig timeout writing cc stream stalled by transport writing cc stream stalled by transport writing cc stream stalled by transport writing cc stream stalled by transport writing cc stream stalled by transport writing cc stream stalled by transport writing cc stream stalled by transport writing cc stream stalled by transport writing cc stream stalled by transport writing cc stream stalled by transport writing cc stream stalled by transport writing cc stream stalled by transport writing cc stream stalled by transport writing cc stream stalled by transport writing cc stream stalled by transport writing cc stream stalled by transport writing cc stream stalled by transport writing cc stream stalled by transport writing cc stream stalled by transport writing cc stream stalled by transport writing cc stream stalled by transport writing cc stream stalled by transport writing cc stream stalled by transport writing cc stream stalled by transport writing cc stream stalled by transport writing cc stream stalled by transport writing cc stream stalled by transport writing cc stream stalled by transport writing cc stream stalled by transport writing cc stream stalled by transport writing cc stream stalled by transport writing cc stream stalled by transport writing cc stream stalled by transport writing cc stream stalled by transport writing cc stream stalled by transport writing cc stream stalled by transport writing cc stream stalled by transport writing cc stream stalled by transport writing cc stream stalled by transport
3,339	2,848,528,116	IssuesEvent	2015-05-29 23:58:44	angular/angular	https://api.github.com/repos/angular/angular	opened	ts2dart should rename types/methods for simple facades	comp: code-generation P1: urgent type: feature	* [ ] rename `Array`, `Map`, `String` and all of their methods * [ ] throw when object has `.push()` but is of type `any`.	1.0	ts2dart should rename types/methods for simple facades - * [ ] rename `Array`, `Map`, `String` and all of their methods * [ ] throw when object has `.push()` but is of type `any`.	non_priority	should rename types methods for simple facades rename array map string and all of their methods throw when object has push but is of type any
237,453	26,085,145,552	IssuesEvent	2022-12-26 01:09:20	xlizaluizax/gridsome-forestry-starter	https://api.github.com/repos/xlizaluizax/gridsome-forestry-starter	opened	CVE-2022-37603 (High) detected in loader-utils-1.4.0.tgz	security vulnerability	## CVE-2022-37603 - High Severity Vulnerability <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>loader-utils-1.4.0.tgz</b></p></summary> <p>utils for webpack loaders</p> <p>Library home page: <a href="https://registry.npmjs.org/loader-utils/-/loader-utils-1.4.0.tgz">https://registry.npmjs.org/loader-utils/-/loader-utils-1.4.0.tgz</a></p> <p>Path to dependency file: /package.json</p> <p>Path to vulnerable library: /node_modules/loader-utils/package.json</p> <p> Dependency Hierarchy: - gridsome-0.7.13.tgz (Root Library) - :x: loader-utils-1.4.0.tgz (Vulnerable Library) <p>Found in base branch: <b>master</b></p> </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary> <p> A Regular expression denial of service (ReDoS) flaw was found in Function interpolateName in interpolateName.js in webpack loader-utils 2.0.0 via the url variable in interpolateName.js. <p>Publish Date: 2022-10-14 <p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-37603>CVE-2022-37603</a></p> </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary> <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: None - Integrity Impact: None - Availability Impact: High </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary> <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://github.com/advisories/GHSA-3rfm-jhwj-7488">https://github.com/advisories/GHSA-3rfm-jhwj-7488</a></p> <p>Release Date: 2022-10-14</p> <p>Fix Resolution (loader-utils): 2.0.4</p> <p>Direct dependency fix Resolution (gridsome): 0.7.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-37603 (High) detected in loader-utils-1.4.0.tgz - ## CVE-2022-37603 - High Severity Vulnerability <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>loader-utils-1.4.0.tgz</b></p></summary> <p>utils for webpack loaders</p> <p>Library home page: <a href="https://registry.npmjs.org/loader-utils/-/loader-utils-1.4.0.tgz">https://registry.npmjs.org/loader-utils/-/loader-utils-1.4.0.tgz</a></p> <p>Path to dependency file: /package.json</p> <p>Path to vulnerable library: /node_modules/loader-utils/package.json</p> <p> Dependency Hierarchy: - gridsome-0.7.13.tgz (Root Library) - :x: loader-utils-1.4.0.tgz (Vulnerable Library) <p>Found in base branch: <b>master</b></p> </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary> <p> A Regular expression denial of service (ReDoS) flaw was found in Function interpolateName in interpolateName.js in webpack loader-utils 2.0.0 via the url variable in interpolateName.js. <p>Publish Date: 2022-10-14 <p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-37603>CVE-2022-37603</a></p> </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary> <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: None - Integrity Impact: None - Availability Impact: High </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary> <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://github.com/advisories/GHSA-3rfm-jhwj-7488">https://github.com/advisories/GHSA-3rfm-jhwj-7488</a></p> <p>Release Date: 2022-10-14</p> <p>Fix Resolution (loader-utils): 2.0.4</p> <p>Direct dependency fix Resolution (gridsome): 0.7.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 high detected in loader utils tgz cve high severity vulnerability vulnerable library loader utils tgz utils for webpack loaders library home page a href path to dependency file package json path to vulnerable library node modules loader utils package json dependency hierarchy gridsome tgz root library x loader utils tgz vulnerable library found in base branch master vulnerability details a regular expression denial of service redos flaw was found in function interpolatename in interpolatename js in webpack loader utils via the url variable in interpolatename js publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact none integrity impact none availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution loader utils direct dependency fix resolution gridsome step up your open source security game with mend
65,239	14,708,540,815	IssuesEvent	2021-01-04 23:58:54	mauriciolauffer/NodeGoat	https://api.github.com/repos/mauriciolauffer/NodeGoat	opened	CVE-2019-1010266 (Medium) detected in lodash-2.4.2.tgz, lodash-4.13.1.tgz	security vulnerability	## CVE-2019-1010266 - Medium Severity Vulnerability <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>lodash-2.4.2.tgz</b>, <b>lodash-4.13.1.tgz</b></p></summary> <p> <details><summary><b>lodash-2.4.2.tgz</b></p></summary> <p>A utility library delivering consistency, customization, performance, & extras.</p> <p>Library home page: <a href="https://registry.npmjs.org/lodash/-/lodash-2.4.2.tgz">https://registry.npmjs.org/lodash/-/lodash-2.4.2.tgz</a></p> <p>Path to dependency file: NodeGoat/package.json</p> <p>Path to vulnerable library: NodeGoat/node_modules/zaproxy/node_modules/lodash/package.json</p> <p> Dependency Hierarchy: - zaproxy-0.2.0.tgz (Root Library) - :x: lodash-2.4.2.tgz (Vulnerable Library) </details> <details><summary><b>lodash-4.13.1.tgz</b></p></summary> <p>Lodash modular utilities.</p> <p>Library home page: <a href="https://registry.npmjs.org/lodash/-/lodash-4.13.1.tgz">https://registry.npmjs.org/lodash/-/lodash-4.13.1.tgz</a></p> <p>Path to dependency file: NodeGoat/package.json</p> <p>Path to vulnerable library: NodeGoat/node_modules/nyc/node_modules/lodash/package.json</p> <p> Dependency Hierarchy: - grunt-if-0.2.0.tgz (Root Library) - grunt-contrib-nodeunit-1.0.0.tgz - nodeunit-0.9.5.tgz - tap-7.1.2.tgz - nyc-7.1.0.tgz - istanbul-lib-instrument-1.1.0-alpha.4.tgz - babel-generator-6.11.4.tgz - :x: lodash-4.13.1.tgz (Vulnerable Library) </details> <p>Found in HEAD commit: <a href="https://github.com/mauriciolauffer/NodeGoat/commit/7e4baae75a2e9024fd12261d8d99f91cc913a308">7e4baae75a2e9024fd12261d8d99f91cc913a308</a></p> <p>Found in base branch: <b>master</b></p> </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary> <p> lodash prior to 4.17.11 is affected by: CWE-400: Uncontrolled Resource Consumption. The impact is: Denial of service. The component is: Date handler. The attack vector is: Attacker provides very long strings, which the library attempts to match using a regular expression. The fixed version is: 4.17.11. <p>Publish Date: 2019-07-17 <p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-1010266>CVE-2019-1010266</a></p> </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>6.5</b>)</summary> <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: Low - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: None - Integrity Impact: 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-2019-1010266">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-1010266</a></p> <p>Release Date: 2019-07-17</p> <p>Fix Resolution: 4.17.11</p> </p> </details> <p></p> *** Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)	True	CVE-2019-1010266 (Medium) detected in lodash-2.4.2.tgz, lodash-4.13.1.tgz - ## CVE-2019-1010266 - Medium Severity Vulnerability <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>lodash-2.4.2.tgz</b>, <b>lodash-4.13.1.tgz</b></p></summary> <p> <details><summary><b>lodash-2.4.2.tgz</b></p></summary> <p>A utility library delivering consistency, customization, performance, & extras.</p> <p>Library home page: <a href="https://registry.npmjs.org/lodash/-/lodash-2.4.2.tgz">https://registry.npmjs.org/lodash/-/lodash-2.4.2.tgz</a></p> <p>Path to dependency file: NodeGoat/package.json</p> <p>Path to vulnerable library: NodeGoat/node_modules/zaproxy/node_modules/lodash/package.json</p> <p> Dependency Hierarchy: - zaproxy-0.2.0.tgz (Root Library) - :x: lodash-2.4.2.tgz (Vulnerable Library) </details> <details><summary><b>lodash-4.13.1.tgz</b></p></summary> <p>Lodash modular utilities.</p> <p>Library home page: <a href="https://registry.npmjs.org/lodash/-/lodash-4.13.1.tgz">https://registry.npmjs.org/lodash/-/lodash-4.13.1.tgz</a></p> <p>Path to dependency file: NodeGoat/package.json</p> <p>Path to vulnerable library: NodeGoat/node_modules/nyc/node_modules/lodash/package.json</p> <p> Dependency Hierarchy: - grunt-if-0.2.0.tgz (Root Library) - grunt-contrib-nodeunit-1.0.0.tgz - nodeunit-0.9.5.tgz - tap-7.1.2.tgz - nyc-7.1.0.tgz - istanbul-lib-instrument-1.1.0-alpha.4.tgz - babel-generator-6.11.4.tgz - :x: lodash-4.13.1.tgz (Vulnerable Library) </details> <p>Found in HEAD commit: <a href="https://github.com/mauriciolauffer/NodeGoat/commit/7e4baae75a2e9024fd12261d8d99f91cc913a308">7e4baae75a2e9024fd12261d8d99f91cc913a308</a></p> <p>Found in base branch: <b>master</b></p> </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary> <p> lodash prior to 4.17.11 is affected by: CWE-400: Uncontrolled Resource Consumption. The impact is: Denial of service. The component is: Date handler. The attack vector is: Attacker provides very long strings, which the library attempts to match using a regular expression. The fixed version is: 4.17.11. <p>Publish Date: 2019-07-17 <p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-1010266>CVE-2019-1010266</a></p> </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>6.5</b>)</summary> <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: Low - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: None - Integrity Impact: 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-2019-1010266">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-1010266</a></p> <p>Release Date: 2019-07-17</p> <p>Fix Resolution: 4.17.11</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 lodash tgz lodash tgz cve medium severity vulnerability vulnerable libraries lodash tgz lodash tgz lodash tgz a utility library delivering consistency customization performance extras library home page a href path to dependency file nodegoat package json path to vulnerable library nodegoat node modules zaproxy node modules lodash package json dependency hierarchy zaproxy tgz root library x lodash tgz vulnerable library lodash tgz lodash modular utilities library home page a href path to dependency file nodegoat package json path to vulnerable library nodegoat node modules nyc node modules lodash package json dependency hierarchy grunt if tgz root library grunt contrib nodeunit tgz nodeunit tgz tap tgz nyc tgz istanbul lib instrument alpha tgz babel generator tgz x lodash tgz vulnerable library found in head commit a href found in base branch master vulnerability details lodash prior to is affected by cwe uncontrolled resource consumption the impact is denial of service the component is date handler the attack vector is attacker provides very long strings which the library attempts to match using a regular expression the fixed version is publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required low user interaction none scope unchanged impact metrics confidentiality impact none integrity impact none availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution step up your open source security game with whitesource
139,211	18,846,340,178	IssuesEvent	2021-11-11 15:20:31	finos/plexus-interop	https://api.github.com/repos/finos/plexus-interop	opened	CVE-2021-23807 (High) detected in jsonpointer-4.0.1.tgz	security vulnerability	## CVE-2021-23807 - High Severity Vulnerability <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>jsonpointer-4.0.1.tgz</b></p></summary> <p>Simple JSON Addressing.</p> <p>Library home page: <a href="https://registry.npmjs.org/jsonpointer/-/jsonpointer-4.0.1.tgz">https://registry.npmjs.org/jsonpointer/-/jsonpointer-4.0.1.tgz</a></p> <p>Path to dependency file: plexus-interop/dsl/interop-lang-vscode/package.json</p> <p>Path to vulnerable library: plexus-interop/dsl/interop-lang-vscode/node_modules/jsonpointer/package.json</p> <p> Dependency Hierarchy: - vscode-1.1.14.tgz (Root Library) - gulp-remote-src-0.4.3.tgz - request-2.79.0.tgz - har-validator-2.0.6.tgz - is-my-json-valid-2.17.2.tgz - :x: jsonpointer-4.0.1.tgz (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/finos/plexus-interop/commit/9bb34b17909843691b3584fd99303ec8b5dc6983">9bb34b17909843691b3584fd99303ec8b5dc6983</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 jsonpointer before 5.0.0. A type confusion vulnerability can lead to a bypass of a previous Prototype Pollution fix when the pointer components are arrays. <p>Publish Date: 2021-11-03 <p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-23807>CVE-2021-23807</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-2021-23807">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-23807</a></p> <p>Release Date: 2021-11-03</p> <p>Fix Resolution: jsonpointer - 5.0.0</p> </p> </details> <p></p> <!-- <REMEDIATE>{"isOpenPROnVulnerability":false,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"jsonpointer","packageVersion":"4.0.1","packageFilePaths":["/dsl/interop-lang-vscode/package.json"],"isTransitiveDependency":true,"dependencyTree":"vscode:1.1.14;gulp-remote-src:0.4.3;request:2.79.0;har-validator:2.0.6;is-my-json-valid:2.17.2;jsonpointer:4.0.1","isMinimumFixVersionAvailable":true,"minimumFixVersion":"jsonpointer - 5.0.0"}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2021-23807","vulnerabilityDetails":"This affects the package jsonpointer before 5.0.0. A type confusion vulnerability can lead to a bypass of a previous Prototype Pollution fix when the pointer components are arrays.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-23807","cvss3Severity":"high","cvss3Score":"9.8","cvss3Metrics":{"A":"High","AC":"Low","PR":"None","S":"Unchanged","C":"High","UI":"None","AV":"Network","I":"High"},"extraData":{}}</REMEDIATE> -->	True	CVE-2021-23807 (High) detected in jsonpointer-4.0.1.tgz - ## CVE-2021-23807 - High Severity Vulnerability <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>jsonpointer-4.0.1.tgz</b></p></summary> <p>Simple JSON Addressing.</p> <p>Library home page: <a href="https://registry.npmjs.org/jsonpointer/-/jsonpointer-4.0.1.tgz">https://registry.npmjs.org/jsonpointer/-/jsonpointer-4.0.1.tgz</a></p> <p>Path to dependency file: plexus-interop/dsl/interop-lang-vscode/package.json</p> <p>Path to vulnerable library: plexus-interop/dsl/interop-lang-vscode/node_modules/jsonpointer/package.json</p> <p> Dependency Hierarchy: - vscode-1.1.14.tgz (Root Library) - gulp-remote-src-0.4.3.tgz - request-2.79.0.tgz - har-validator-2.0.6.tgz - is-my-json-valid-2.17.2.tgz - :x: jsonpointer-4.0.1.tgz (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/finos/plexus-interop/commit/9bb34b17909843691b3584fd99303ec8b5dc6983">9bb34b17909843691b3584fd99303ec8b5dc6983</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 jsonpointer before 5.0.0. A type confusion vulnerability can lead to a bypass of a previous Prototype Pollution fix when the pointer components are arrays. <p>Publish Date: 2021-11-03 <p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-23807>CVE-2021-23807</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-2021-23807">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-23807</a></p> <p>Release Date: 2021-11-03</p> <p>Fix Resolution: jsonpointer - 5.0.0</p> </p> </details> <p></p> <!-- <REMEDIATE>{"isOpenPROnVulnerability":false,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"jsonpointer","packageVersion":"4.0.1","packageFilePaths":["/dsl/interop-lang-vscode/package.json"],"isTransitiveDependency":true,"dependencyTree":"vscode:1.1.14;gulp-remote-src:0.4.3;request:2.79.0;har-validator:2.0.6;is-my-json-valid:2.17.2;jsonpointer:4.0.1","isMinimumFixVersionAvailable":true,"minimumFixVersion":"jsonpointer - 5.0.0"}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2021-23807","vulnerabilityDetails":"This affects the package jsonpointer before 5.0.0. A type confusion vulnerability can lead to a bypass of a previous Prototype Pollution fix when the pointer components are arrays.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-23807","cvss3Severity":"high","cvss3Score":"9.8","cvss3Metrics":{"A":"High","AC":"Low","PR":"None","S":"Unchanged","C":"High","UI":"None","AV":"Network","I":"High"},"extraData":{}}</REMEDIATE> -->	non_priority	cve high detected in jsonpointer tgz cve high severity vulnerability vulnerable library jsonpointer tgz simple json addressing library home page a href path to dependency file plexus interop dsl interop lang vscode package json path to vulnerable library plexus interop dsl interop lang vscode node modules jsonpointer package json dependency hierarchy vscode tgz root library gulp remote src tgz request tgz har validator tgz is my json valid tgz x jsonpointer tgz vulnerable library found in head commit a href found in base branch master vulnerability details this affects the package jsonpointer before a type confusion vulnerability can lead to a bypass of a previous prototype pollution fix when the pointer components are arrays 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 jsonpointer isopenpronvulnerability false ispackagebased true isdefaultbranch true packages istransitivedependency true dependencytree vscode gulp remote src request har validator is my json valid jsonpointer isminimumfixversionavailable true minimumfixversion jsonpointer basebranches vulnerabilityidentifier cve vulnerabilitydetails this affects the package jsonpointer before a type confusion vulnerability can lead to a bypass of a previous prototype pollution fix when the pointer components are arrays vulnerabilityurl
115,087	11,865,040,752	IssuesEvent	2020-03-25 23:10:32	Arquisoft/viade_es1b	https://api.github.com/repos/Arquisoft/viade_es1b	closed	la documentacion no se muestra correctamente en master	bug documentation	La documentacion no aparece completa, solo hasta el punto 4, y el contenido parece entremezclado.	1.0	la documentacion no se muestra correctamente en master - La documentacion no aparece completa, solo hasta el punto 4, y el contenido parece entremezclado.	non_priority	la documentacion no se muestra correctamente en master la documentacion no aparece completa solo hasta el punto y el contenido parece entremezclado
22,574	3,790,833,342	IssuesEvent	2016-03-21 23:06:50	diablodale/dp.kinect2	https://api.github.com/repos/diablodale/dp.kinect2	closed	registration problem	by design not-a-bug	Win 10 Max 7 32 bits 7.2.1 registered Runtime 2.0 dp.kinect2 v1.1.20160225.0 I can't register properly the dp.kinect2 external. I followed the instructions and it worked but only with the max 64 bit version. After registering the external in Max 64 bits it works for a while also in Max 32 bit version, but after closing max the registration disappears and I have to repeate the whole process again. Thanks!	1.0	registration problem - Win 10 Max 7 32 bits 7.2.1 registered Runtime 2.0 dp.kinect2 v1.1.20160225.0 I can't register properly the dp.kinect2 external. I followed the instructions and it worked but only with the max 64 bit version. After registering the external in Max 64 bits it works for a while also in Max 32 bit version, but after closing max the registration disappears and I have to repeate the whole process again. Thanks!	non_priority	registration problem win max bits registered runtime dp i can t register properly the dp external i followed the instructions and it worked but only with the max bit version after registering the external in max bits it works for a while also in max bit version but after closing max the registration disappears and i have to repeate the whole process again thanks
8,310	21,922,610,145	IssuesEvent	2022-05-22 20:00:09	RockItTeam/website	https://api.github.com/repos/RockItTeam/website	closed	As a user, I can subscribe to the newsletter and this is handled via Milchimp	Backend API Intégration Frontend - utilisateur devOps / architecture	Objectif : Connecter le formulaire de newsletter à une inscription sur le mailchimp d'Adrien Backend : - [ ] Créer un endpoint API dédié sur le backend qui permet d'enregistrer l'adresse email comme destinataire des newsletter sur Mailchimp POST /api/v1/newsletter_registration Frontend - [ ] Connecter le formulaire de newsletter à l'endpoint API. Gérer un affichage de type succès lorsque le formulaire a été envoyée (et message d'erreur) A confirmer, mais ça devrait être cet endpoint qu'il faut taper : https://mailchimp.com/developer/marketing/api/list-members/ La gestion des désinscriptions n'est pas à faire (cf via le lien dans le bas des emails envoyés, ajouté auto par mailchimp) Faire des tests avec un compte mailchimp de dev, et indiquer quels sont les secrets nécessaires pour la prod	1.0	As a user, I can subscribe to the newsletter and this is handled via Milchimp - Objectif : Connecter le formulaire de newsletter à une inscription sur le mailchimp d'Adrien Backend : - [ ] Créer un endpoint API dédié sur le backend qui permet d'enregistrer l'adresse email comme destinataire des newsletter sur Mailchimp POST /api/v1/newsletter_registration Frontend - [ ] Connecter le formulaire de newsletter à l'endpoint API. Gérer un affichage de type succès lorsque le formulaire a été envoyée (et message d'erreur) A confirmer, mais ça devrait être cet endpoint qu'il faut taper : https://mailchimp.com/developer/marketing/api/list-members/ La gestion des désinscriptions n'est pas à faire (cf via le lien dans le bas des emails envoyés, ajouté auto par mailchimp) Faire des tests avec un compte mailchimp de dev, et indiquer quels sont les secrets nécessaires pour la prod	non_priority	as a user i can subscribe to the newsletter and this is handled via milchimp objectif connecter le formulaire de newsletter à une inscription sur le mailchimp d adrien backend créer un endpoint api dédié sur le backend qui permet d enregistrer l adresse email comme destinataire des newsletter sur mailchimp post api newsletter registration frontend connecter le formulaire de newsletter à l endpoint api gérer un affichage de type succès lorsque le formulaire a été envoyée et message d erreur a confirmer mais ça devrait être cet endpoint qu il faut taper la gestion des désinscriptions n est pas à faire cf via le lien dans le bas des emails envoyés ajouté auto par mailchimp faire des tests avec un compte mailchimp de dev et indiquer quels sont les secrets nécessaires pour la prod
359,525	25,242,769,545	IssuesEvent	2022-11-15 08:54:03	swsnu/swppfall2022-team1	https://api.github.com/repos/swsnu/swppfall2022-team1	opened	FE <-> BE 아키텍쳐 간략 설명	documentation	설명을 하자면, 1. `infra/dto` 아래 백엔드에서 보내주는 모델과 동일한 interface 생성 (snake_case으로 똑같이) 2. `domain/model` 아래 해당 dto와 일치하는 FE 모델을 camelCase로 만든다. 1. 이때 이미 비슷한 모델이 이미 존재한다면, 따로 파일을 생성하지 않고 이미 존재하는 파일 내 type을 typescript을 잘 사용해서 생성해도 된다 (예: BoardPost 타입은 따로 파일을 만들지 않고, ListItemPost 파일 내에 만들어줬다. 이는 나중에 FeedPost, EventDetailPost의 공통점들을 한꺼번에 모아볼 수 있기 위해서이다) 3. `infra/transformer`에서 새로운 파일을 생성해 dto를 model로 매핑해준다 4. `infra/api`에 해당되는 api 함수를 작성한다. 1. return type을 정확히 명시한다 - 예: `Promise<BoardPost>` 2. axios 함수의 response type을 정확히 명시한다 - 예: `axios.get<BoardPostDto>` 5. slice에서 해당되는 action내에 위의 함수를 호출해주고 reducer내에서 payload를 받아 state관리를 한다 6. selector 파일에서 state를 빼온다 7. 뷰에서 action을 dispatch하고, 원하는 데이터를 selector에서 빼온다 ## 꼭 이 형식을 지켜주세요! 다소 복잡하지만, 책임을 분산시키며 타입을 확실하게 명시해줍니다. P.S. 한가지 아쉬운점... 원래 `domain`이라는게 그 어디에도 의존하면 안 되는 존재인데 현재는 `domain <-> infra` 간의 circular dependency (쌍방향 의존성?) 존재. 이거는 `domain <- infra`는 가능하지만, `domain -> infra`는 발생하면 안 된다는 뜻. 현재 상태에서 `domain -> infra`가 발생하는 원인은 `api` 때문이다. 그래서 이를 해결하기 위해서는 API에 대한 껍대기 interface를 `domain`내에 구현하는 것이고 실제 구현체는 `infra`에서 생성하는 것이다. 그리고서는 최최최상단에서 dependency injection을 통해 실제 구현체를 domain에 주입하는 것이다. 그러면 `domain/store` 내에 있는 slice들은 더욱 testable해지고, `domain`에서의 외부 api에 의존성도 사라진다. 일단은 MVP를 만들어내는 것이 더 중요하기에 아키텍쳐 리팩토링은 추후 스프린트에 진행하면 좋을 것 같습니다~	1.0	FE <-> BE 아키텍쳐 간략 설명 - 설명을 하자면, 1. `infra/dto` 아래 백엔드에서 보내주는 모델과 동일한 interface 생성 (snake_case으로 똑같이) 2. `domain/model` 아래 해당 dto와 일치하는 FE 모델을 camelCase로 만든다. 1. 이때 이미 비슷한 모델이 이미 존재한다면, 따로 파일을 생성하지 않고 이미 존재하는 파일 내 type을 typescript을 잘 사용해서 생성해도 된다 (예: BoardPost 타입은 따로 파일을 만들지 않고, ListItemPost 파일 내에 만들어줬다. 이는 나중에 FeedPost, EventDetailPost의 공통점들을 한꺼번에 모아볼 수 있기 위해서이다) 3. `infra/transformer`에서 새로운 파일을 생성해 dto를 model로 매핑해준다 4. `infra/api`에 해당되는 api 함수를 작성한다. 1. return type을 정확히 명시한다 - 예: `Promise<BoardPost>` 2. axios 함수의 response type을 정확히 명시한다 - 예: `axios.get<BoardPostDto>` 5. slice에서 해당되는 action내에 위의 함수를 호출해주고 reducer내에서 payload를 받아 state관리를 한다 6. selector 파일에서 state를 빼온다 7. 뷰에서 action을 dispatch하고, 원하는 데이터를 selector에서 빼온다 ## 꼭 이 형식을 지켜주세요! 다소 복잡하지만, 책임을 분산시키며 타입을 확실하게 명시해줍니다. P.S. 한가지 아쉬운점... 원래 `domain`이라는게 그 어디에도 의존하면 안 되는 존재인데 현재는 `domain <-> infra` 간의 circular dependency (쌍방향 의존성?) 존재. 이거는 `domain <- infra`는 가능하지만, `domain -> infra`는 발생하면 안 된다는 뜻. 현재 상태에서 `domain -> infra`가 발생하는 원인은 `api` 때문이다. 그래서 이를 해결하기 위해서는 API에 대한 껍대기 interface를 `domain`내에 구현하는 것이고 실제 구현체는 `infra`에서 생성하는 것이다. 그리고서는 최최최상단에서 dependency injection을 통해 실제 구현체를 domain에 주입하는 것이다. 그러면 `domain/store` 내에 있는 slice들은 더욱 testable해지고, `domain`에서의 외부 api에 의존성도 사라진다. 일단은 MVP를 만들어내는 것이 더 중요하기에 아키텍쳐 리팩토링은 추후 스프린트에 진행하면 좋을 것 같습니다~	non_priority	fe be 아키텍쳐 간략 설명 설명을 하자면 infra dto 아래 백엔드에서 보내주는 모델과 동일한 interface 생성 snake case으로 똑같이 domain model 아래 해당 dto와 일치하는 fe 모델을 camelcase로 만든다 이때 이미 비슷한 모델이 이미 존재한다면 따로 파일을 생성하지 않고 이미 존재하는 파일 내 type을 typescript을 잘 사용해서 생성해도 된다 예 boardpost 타입은 따로 파일을 만들지 않고 listitempost 파일 내에 만들어줬다 이는 나중에 feedpost eventdetailpost의 공통점들을 한꺼번에 모아볼 수 있기 위해서이다 infra transformer 에서 새로운 파일을 생성해 dto를 model로 매핑해준다 infra api 에 해당되는 api 함수를 작성한다 return type을 정확히 명시한다 예 promise axios 함수의 response type을 정확히 명시한다 예 axios get slice에서 해당되는 action내에 위의 함수를 호출해주고 reducer내에서 payload를 받아 state관리를 한다 selector 파일에서 state를 빼온다 뷰에서 action을 dispatch하고 원하는 데이터를 selector에서 빼온다 꼭 이 형식을 지켜주세요 다소 복잡하지만 책임을 분산시키며 타입을 확실하게 명시해줍니다 p s 한가지 아쉬운점 원래 domain 이라는게 그 어디에도 의존하면 안 되는 존재인데 현재는 domain infra 간의 circular dependency 쌍방향 의존성 존재 이거는 domain infra 는 발생하면 안 된다는 뜻 현재 상태에서 domain infra 가 발생하는 원인은 api 때문이다 그래서 이를 해결하기 위해서는 api에 대한 껍대기 interface를 domain 내에 구현하는 것이고 실제 구현체는 infra 에서 생성하는 것이다 그리고서는 최최최상단에서 dependency injection을 통해 실제 구현체를 domain에 주입하는 것이다 그러면 domain store 내에 있는 slice들은 더욱 testable해지고 domain 에서의 외부 api에 의존성도 사라진다 일단은 mvp를 만들어내는 것이 더 중요하기에 아키텍쳐 리팩토링은 추후 스프린트에 진행하면 좋을 것 같습니다
154,121	24,250,853,303	IssuesEvent	2022-09-27 14:06:30	department-of-veterans-affairs/va.gov-team	https://api.github.com/repos/department-of-veterans-affairs/va.gov-team	closed	[Design] Update Travel pay appt confirmation wireframes and prototype to be a single appt confirmation	design ux HCE-Checkin CIE-next	Task - [x] Update Travel pay appt confirmation wireframes to be a single appt confirmation - [x] Update Travel pay appt confirmation prototype to be a single appt confirmation	1.0	[Design] Update Travel pay appt confirmation wireframes and prototype to be a single appt confirmation - Task - [x] Update Travel pay appt confirmation wireframes to be a single appt confirmation - [x] Update Travel pay appt confirmation prototype to be a single appt confirmation	non_priority	update travel pay appt confirmation wireframes and prototype to be a single appt confirmation task update travel pay appt confirmation wireframes to be a single appt confirmation update travel pay appt confirmation prototype to be a single appt confirmation
22,090	3,774,066,399	IssuesEvent	2016-03-17 07:10:28	sayurispace/B6T3WX3I4U4VCWIYBNAYQJLH	https://api.github.com/repos/sayurispace/B6T3WX3I4U4VCWIYBNAYQJLH	closed	M9t401AK7FZxTNSPprAukcMG+w2MdP4K4h77jmWatXargAXlpQEZOkloDXJAUBLNqxnkUtAUjGQdrvcO81YzHlvB+lU39xAlj7LatTVSMFG2qx9C5NuFoPqHBHeI9BBNCBp2OTz7dEM33xhYJ3irnnO+WvQfXwZej8dCiEfrjpk=	design	s0Hr6k7yev9whCilkx0LBpxFoRZ3rVDHTiezJnxdPM9jK3lZsZn3+BWvI/XBT/69KHJTP1KTLycFQcJQltM5MuifKTAd5ocWS1WPgwVmP4B4qv7tmjAXevb62sGM/yP+0u8aVVa1j494FWA/S+WYEKf7om6sjekYKG1zzcaVDAC7ToBiaP8o1PP/Z1NY9Dj32q2dTQp3lHmO7lR+e/B2bTJk52NRUnm3nVdotgaXY9JjWPP0eMHhmF19pbOaS/9DSGQ3qVPHPc8MmYCNUg6F+kOPkdRGLgBIo7K5pD4eQIQ+zuH/de+T/dntWQWyUeJ7WpwdjGWc8eBeJ3+0s3gq0sef6mDHqCYVMNk8dj4qkedjK3lZsZn3+BWvI/XBT/69aRNa8iQSHI6OYQGJU003pz7O4f9175P92e1ZBbJR4nvm8D4WT47rhcj9sZvH/WF2Ri0pBJ2P3s2/riw4jNEzumMreVmxmff4Fa8j9cFP/r18eyR1dnA3zcjr5HYikNe5Ps7h/3Xvk/3Z7VkFslHie9pFZjUPAybOkPTuFXRevtsDx4mw3fSmp2iwMCQB8ooXYyt5WbGZ9/gVryP1wU/+vaAhhSwAM27fGKrnSW7jRy4+zuH/de+T/dntWQWyUeJ7eiZfuMupwqkDl2IVQYC0eDhEn6AuoaYC82CCc97wiT910so+rwD8+opMMK48Z06T9IsG1yYoJ4/uE3WutBWfXD7O4f9175P92e1ZBbJR4ntUGCbXri31yn4nLmdQiXbyA8eJsN30pqdosDAkAfKKF2MreVmxmff4Fa8j9cFP/r2z0ahJIf/qgSJSxTFfrlmLYyt5WbGZ9/gVryP1wU/+vQicfTAh/L0drE6KDJpeIbrbKCc8flKQuGIBO4/zeK0+8mieptdTuEHITwqod3QXKfO5ITEu5ORmJ516Reaec5hjK3lZsZn3+BWvI/XBT/69sEib8Y2PvWt5TqdcqNFkAV1ypwxMD7vpq+WYxcXgFavyaJ6m11O4QchPCqh3dBcpZ0SJ5Aqgw3WN/4aC33WRuD7O4f9175P92e1ZBbJR4num/gjmZ8tYK6rgBLz/NmC6jUSsXEJB8WOssBlgwzKSGGMreVmxmff4Fa8j9cFP/r2cTOr+E6btNi4GacebEZNGPs7h/3Xvk/3Z7VkFslHie5sgv+e3wZgQzT9WZG3fQLvUNU89swfFJBz/qjeDpGFtYyt5WbGZ9/gVryP1wU/+vREc1nVO2mIzyO8N0SM+ewQ+zuH/de+T/dntWQWyUeJ7cZ8V7RZ274+YOUe3uxoewjj2pyEkvLrUc4E8VKQ29a510so+rwD8+opMMK48Z06T2qQXfcMewdKwB2T4c8TpJj7O4f9175P92e1ZBbJR4ns/7J0WY7iN1cDcrf18ZmJaqQsR0dwanpXEhEWpEIY8FGMreVmxmff4Fa8j9cFP/r0dytx7tinY6i2EoWvqMdR+Ps7h/3Xvk/3Z7VkFslHie4dzhQh1OgFjT0bX6cX2FKE49qchJLy61HOBPFSkNvWuddLKPq8A/PqKTDCuPGdOk8vaWErNti5bTLh/Bep3cIs+zuH/de+T/dntWQWyUeJ7YmFvhasIOvUDSt2CkFcFWTj2pyEkvLrUc4E8VKQ29a510so+rwD8+opMMK48Z06T265FfISV+yVexvI1x3J7gz7O4f9175P92e1ZBbJR4ntb5deQaSwvoLx3c/m2EVxBOPanISS8utRzgTxUpDb1rnXSyj6vAPz6ikwwrjxnTpMRCdOCt2blYiFQY0iqczHSPs7h/3Xvk/3Z7VkFslHieyEUg8Q40VDzcBfdZf9qBDw49qchJLy61HOBPFSkNvWuddLKPq8A/PqKTDCuPGdOkyLSoqn4pANCbYlCUJQ4k64+zuH/de+T/dntWQWyUeJ7cmma8X9ON9cQT3KMc1hapTj2pyEkvLrUc4E8VKQ29a510so+rwD8+opMMK48Z06TaZrH8+e8b4nzRw9Rg4dl9T7O4f9175P92e1ZBbJR4nvn2fydoov+kCSLAy9/5dxPRQDknYQDQtd1PooFmrdpifJonqbXU7hByE8KqHd0Fyl6XCAJCs773hUYmv8xoEPVYyt5WbGZ9/gVryP1wU/+vdXiF4xEoxnG8HzI+UC5H5WpCxHR3BqelcSERakQhjwUYyt5WbGZ9/gVryP1wU/+vbmNktjguMNHLoknjGsJf1xjK3lZsZn3+BWvI/XBT/69GIbMlMIceq6gth3XWVED7jj2pyEkvLrUc4E8VKQ29a510so+rwD8+opMMK48Z06TvXh7RC+MP97PWXuQNfAYvj7O4f9175P92e1ZBbJR4nu1QhQWlEc2phBlhLLMJ04bvkDCHjkJz0/qUj7nI1fMvnXSyj6vAPz6ikwwrjxnTpMoDahYOsw1Yc411qlPjwTaPs7h/3Xvk/3Z7VkFslHie8HtGg/4exiZsnBd6FIxp/849qchJLy61HOBPFSkNvWuddLKPq8A/PqKTDCuPGdOk843J/ur2f17dynynoFcv9A+zuH/de+T/dntWQWyUeJ7NN4NKDa6XOeLu+wIBYy3HKWooJPm6UD39zMTrNW7GmNjK3lZsZn3+BWvI/XBT/699mpueav0/ZCxg/ld6o4+3T7O4f9175P92e1ZBbJR4ntcuysRafXOVcHFAoY3ekTVH50GOdXHM7mweHRTAE8wAmMreVmxmff4Fa8j9cFP/r0jqfBWkoh4H/FGk5CUnIC7Ps7h/3Xvk/3Z7VkFslHie2tIrbGrp3eubTAB2Tt08gE49qchJLy61HOBPFSkNvWuddLKPq8A/PqKTDCuPGdOk/ptYjM0zyoLc/zYFJQFhDA+zuH/de+T/dntWQWyUeJ78QvGCKcx4psMUa7i+T0NsNt1s/UM97VdqLnz+YsVWIR10so+rwD8+opMMK48Z06THB0yBF/ogt1iA5Ipw5UkVT7O4f9175P92e1ZBbJR4nvctwwmHcyNaySqiI4JAFRVVFwBQHXLmplAd6VhxCWMJWQm7+rDHQVJRGfHyi8OvC7Vfbw7dv881InD//se32acPs7h/3Xvk/3Z7VkFslHie1NaeVXS08CnbUbbn5kWnGlRTiaqAgG9B958uSQBTXLazB+L7GIqBN3pZ1co9G3aSPxNRI6UmhqKI4osd/c/Lew+zuH/de+T/dntWQWyUeJ7uoeq6OYJF8oia77Z6mEXvMDo6K/OFfLKRweTIIcDW4BjK3lZsZn3+BWvI/XBT/69iNgdt47Wpxlp7uQH9aCRHT7O4f9175P92e1ZBbJR4ntlBs8HEafGZBNXUB2M5KR+rxVLTTPEBuH6wuiQX4kV8kaXJg6fwBYmiGLnJH6j9hKazft85GyCJCv7OB+WWDY7Ps7h/3Xvk/3Z7VkFslHiexPRXshYyl2bhGb0s8dWAxduqxU6cdVDCLKpMlCPGiur8mieptdTuEHITwqod3QXKTRfrJ9GVxkoiOUzbBiAAF5jK3lZsZn3+BWvI/XBT/69OLK08TF1S+IBJJA6XiERKPF0XlvoZxRsUBEU3CR0nG9jK3lZsZn3+BWvI/XBT/69cQDx3GnAWmhb5IdimhcLPGMreVmxmff4Fa8j9cFP/r1Xotc7g7YaJEQJAazDrW9YrPmzuQHAP5fRYaegvPrs52MreVmxmff4Fa8j9cFP/r2bhIZhVP0++VZjHk43D0aRYyt5WbGZ9/gVryP1wU/+vbRsrpaAZlF/sgdRjG1ayosWd1UDv9PPFf5n6TgkyAqx8mieptdTuEHITwqod3QXKS31YQFXr1CgUk/KNV1oBKVjK3lZsZn3+BWvI/XBT/69lQWopNP086ZZRjTi1y3DkR+dBjnVxzO5sHh0UwBPMAJjK3lZsZn3+BWvI/XBT/69RnDscgY5qPYenx2n74TC8j7O4f9175P92e1ZBbJR4nvUeLHOURsddTmXnZmkz8Q2ZaxKE+PbmUG5e0hheOzbqfJonqbXU7hByE8KqHd0FylR1qYdZcH1GWgPOaAqiKCsPs7h/3Xvk/3Z7VkFslHie8fl5GIo3yL2B2nE6HCV0NpkXSL9MchoVc5AE7ceIy58ddLKPq8A/PqKTDCuPGdOk/ie9rbVp5A89lHPjqUufAk+zuH/de+T/dntWQWyUeJ7zxfl3mtQ+9FmiXFCf+GItJIN4LAAyMLNiS4pXNXmo8JjK3lZsZn3+BWvI/XBT/69AVFL93QdciIJoaCfvxzq2z7O4f9175P92e1ZBbJR4nu8lCVNFsJUUrCZO03bOcIxG4hRa3spXNxyj5J0MO3eSXXSyj6vAPz6ikwwrjxnTpPixC7r1rBNa8Sh2cc+Vg7PPs7h/3Xvk/3Z7VkFslHie5g+vYQ/81gLzq40rAeSP+54id+nCyi8bnWBHGSO9bj7Yyt5WbGZ9/gVryP1wU/+vbJdhUwjdNHIQr+rtx3ohMljK3lZsZn3+BWvI/XBT/69CdQygpCbDkeESYMOuPw9LHiJ36cLKLxudYEcZI71uPtjK3lZsZn3+BWvI/XBT/69jmQiC9gdledL3rJxMu6gp2MreVmxmff4Fa8j9cFP/r3Jqh6Op2MPU1bYtXB5kXqleInfpwsovG51gRxkjvW4+2MreVmxmff4Fa8j9cFP/r00/2nMrhJZelSsptUhiiIhYyt5WbGZ9/gVryP1wU/+vVAyUWJhf5Wm3JKVqQgCgv6SCE+i1/itfjFr87ejNyzMYyt5WbGZ9/gVryP1wU/+vca8HNhWSP587SOPQSKu6Ag+zuH/de+T/dntWQWyUeJ7P+ZC46AvkW5yNZku0X3N5dmR7FbQBBfz8fLw+FuT6cJjK3lZsZn3+BWvI/XBT/69TJhUvm3r57na8GKC+/omumMreVmxmff4Fa8j9cFP/r2XtA29QY5P+0+FVioTkA720S4IlBLc9nhgmKE88tggcswfi+xiKgTd6WdXKPRt2kjcUwL7c+9KltVfBwlR6GfXYyt5WbGZ9/gVryP1wU/+vdgLaafgWWiJIHkOAo4sScW4i6ktZg74RLXqmAcxmE7cKqqGNsu35Hra/wnXACmjedOnhleaI9sOhPODRr11HD1jK3lZsZn3+BWvI/XBT/69luSjtS7rVE/7TTk+SWUfg9t1s/UM97VdqLnz+YsVWIR10so+rwD8+opMMK48Z06T7VP5B0oTeJyA2BdCdvEBNz7O4f9175P92e1ZBbJR4nvHug+oOP6biocLtHIe5N/2RnGYTCPXI9dHP54X0UjDffJonqbXU7hByE8KqHd0FykQxFMsDox/QN5DUKsl5z0oYyt5WbGZ9/gVryP1wU/+vR84+iqwslfFlbjxDymvtYesdr73+DYTSwQPT3WKC0uO8mieptdTuEHITwqod3QXKS3kEHiRcLiKVSSzEDYnQYtjK3lZsZn3+BWvI/XBT/69PTkko5ZROb4uvcBd9SKw8Dj2pyEkvLrUc4E8VKQ29a510so+rwD8+opMMK48Z06T42WayWwRDIkI0J0SSZ65+D7O4f9175P92e1ZBbJR4nsoGg1M/tgJc1t9aA0xeyE4OPanISS8utRzgTxUpDb1rnXSyj6vAPz6ikwwrjxnTpOdRXggr+Fkvjfam6Yi9LlXPs7h/3Xvk/3Z7VkFslHiexwB1WqVmeqsAsnczZtJepI49qchJLy61HOBPFSkNvWuddLKPq8A/PqKTDCuPGdOk62sr71nOf80YCS5rBwZ5RA+zuH/de+T/dntWQWyUeJ7iqzaKxy0Ncrce9QnJ6lMx/ivQ8b+GDsuzch4VOI0XCXyaJ6m11O4QchPCqh3dBcpJssNx9p24Mi3a1lDy3drmj7O4f9175P92e1ZBbJR4nuB0bmsw3Ams5AHAe32uR20P2spr2CrwVKeAJLz2QERlfJonqbXU7hByE8KqHd0Fym3FenHIYaw7TUAey9lFM3iPs7h/3Xvk/3Z7VkFslHie8vE3uqhhIY5bWGJakJ7FaN5evfYwhl3+mXxOxiAVjGoYyt5WbGZ9/gVryP1wU/+vU4AEXABUIyMCNItkfzsCrJjK3lZsZn3+BWvI/XBT/69b98kXQQqzt+DwIOHz/CLCrGIVLDD9hOUaINJtQG/4dJ10so+rwD8+opMMK48Z06TsiVBwP6jaTDQbhDrQDO2LD7O4f9175P92e1ZBbJR4nsiQVMsc2XOkeQSIaS614CJenGZKIkAZqIXcZ4WZFM4x6MYDjWUtwHdKu9KxBzLMPhHa8Xy0YT00x34jX8SfozNPs7h/3Xvk/3Z7VkFslHie4HBDPsZB5fF2mDK/xBJ2pQ49qchJLy61HOBPFSkNvWuddLKPq8A/PqKTDCuPGdOkwtWwAzcCuBaktkKl6pHXyY+zuH/de+T/dntWQWyUeJ7YaeTQ/dySWSk/PpFH3awBzj2pyEkvLrUc4E8VKQ29a510so+rwD8+opMMK48Z06T6Q/3RRwrXXco6Md0an4nTj7O4f9175P92e1ZBbJR4nsfsG6e5lD5aIZE3hQS0mSmA+AgWYMXqylFnCZnfWMo13XSyj6vAPz6ikwwrjxnTpP2FafOt8p6r72tzqpCTWHQYyt5WbGZ9/gVryP1wU/+vcsctBPUGBHs3c0j6jhX7g8UwByYPqOes+uCr8L7HjpuYyt5WbGZ9/gVryP1wU/+vZUgQaD9PQnsbOoSPXadTqY+zuH/de+T/dntWQWyUeJ7OICqruPRzb2fF0WOl/32gRZNqmJQB7cTRuimddmQhnpjK3lZsZn3+BWvI/XBT/69gZbFBkae0MR+oPqpEehg1D7O4f9175P92e1ZBbJR4nssOv55iRTletOrKmdx5HZs7PsIdC8mh+BXDMD/Zcd2QvJonqbXU7hByE8KqHd0FynCTJov/tePAskoHLbXniCRYyt5WbGZ9/gVryP1wU/+vVr00RnFnRc5FzlXz58WHfZ7S+sXajlppx5w2blMCLdMYyt5WbGZ9/gVryP1wU/+vW11SCq35mKKASgNpX+nSUpjK3lZsZn3+BWvI/XBT/69E7l2Iqej7O0CpSJowLdeK9t1s/UM97VdqLnz+YsVWIR10so+rwD8+opMMK48Z06TJKyFY9JNvn1Cm5nqG9DpnGMreVmxmff4Fa8j9cFP/r1OYbLIP2avYhF/vQaiue6YNkiWxWRSEpXlcIrD17R+l/JonqbXU7hByE8KqHd0FykNTFDeR/csYeQi8mD86Q67Yyt5WbGZ9/gVryP1wU/+vWKz+43LThgNZoCtMIbCqkLnOsTMzF4kt64pGJ3KBLkB8mieptdTuEHITwqod3QXKc6nVQHCJ2yUPiR8L068QRM+zuH/de+T/dntWQWyUeJ7WOq6xlonO5+Efjc8VhQPRajlfjI+BGk2UHq+kCybnLuUJ6c/2FWT/HGziLe4vDaILQciLo3WIlNftH4y/uJJeGE5qYLdzmRWlubtnA0mqbk=	1.0	M9t401AK7FZxTNSPprAukcMG+w2MdP4K4h77jmWatXargAXlpQEZOkloDXJAUBLNqxnkUtAUjGQdrvcO81YzHlvB+lU39xAlj7LatTVSMFG2qx9C5NuFoPqHBHeI9BBNCBp2OTz7dEM33xhYJ3irnnO+WvQfXwZej8dCiEfrjpk= - s0Hr6k7yev9whCilkx0LBpxFoRZ3rVDHTiezJnxdPM9jK3lZsZn3+BWvI/XBT/69KHJTP1KTLycFQcJQltM5MuifKTAd5ocWS1WPgwVmP4B4qv7tmjAXevb62sGM/yP+0u8aVVa1j494FWA/S+WYEKf7om6sjekYKG1zzcaVDAC7ToBiaP8o1PP/Z1NY9Dj32q2dTQp3lHmO7lR+e/B2bTJk52NRUnm3nVdotgaXY9JjWPP0eMHhmF19pbOaS/9DSGQ3qVPHPc8MmYCNUg6F+kOPkdRGLgBIo7K5pD4eQIQ+zuH/de+T/dntWQWyUeJ7WpwdjGWc8eBeJ3+0s3gq0sef6mDHqCYVMNk8dj4qkedjK3lZsZn3+BWvI/XBT/69aRNa8iQSHI6OYQGJU003pz7O4f9175P92e1ZBbJR4nvm8D4WT47rhcj9sZvH/WF2Ri0pBJ2P3s2/riw4jNEzumMreVmxmff4Fa8j9cFP/r18eyR1dnA3zcjr5HYikNe5Ps7h/3Xvk/3Z7VkFslHie9pFZjUPAybOkPTuFXRevtsDx4mw3fSmp2iwMCQB8ooXYyt5WbGZ9/gVryP1wU/+vaAhhSwAM27fGKrnSW7jRy4+zuH/de+T/dntWQWyUeJ7eiZfuMupwqkDl2IVQYC0eDhEn6AuoaYC82CCc97wiT910so+rwD8+opMMK48Z06T9IsG1yYoJ4/uE3WutBWfXD7O4f9175P92e1ZBbJR4ntUGCbXri31yn4nLmdQiXbyA8eJsN30pqdosDAkAfKKF2MreVmxmff4Fa8j9cFP/r2z0ahJIf/qgSJSxTFfrlmLYyt5WbGZ9/gVryP1wU/+vQicfTAh/L0drE6KDJpeIbrbKCc8flKQuGIBO4/zeK0+8mieptdTuEHITwqod3QXKfO5ITEu5ORmJ516Reaec5hjK3lZsZn3+BWvI/XBT/69sEib8Y2PvWt5TqdcqNFkAV1ypwxMD7vpq+WYxcXgFavyaJ6m11O4QchPCqh3dBcpZ0SJ5Aqgw3WN/4aC33WRuD7O4f9175P92e1ZBbJR4num/gjmZ8tYK6rgBLz/NmC6jUSsXEJB8WOssBlgwzKSGGMreVmxmff4Fa8j9cFP/r2cTOr+E6btNi4GacebEZNGPs7h/3Xvk/3Z7VkFslHie5sgv+e3wZgQzT9WZG3fQLvUNU89swfFJBz/qjeDpGFtYyt5WbGZ9/gVryP1wU/+vREc1nVO2mIzyO8N0SM+ewQ+zuH/de+T/dntWQWyUeJ7cZ8V7RZ274+YOUe3uxoewjj2pyEkvLrUc4E8VKQ29a510so+rwD8+opMMK48Z06T2qQXfcMewdKwB2T4c8TpJj7O4f9175P92e1ZBbJR4ns/7J0WY7iN1cDcrf18ZmJaqQsR0dwanpXEhEWpEIY8FGMreVmxmff4Fa8j9cFP/r0dytx7tinY6i2EoWvqMdR+Ps7h/3Xvk/3Z7VkFslHie4dzhQh1OgFjT0bX6cX2FKE49qchJLy61HOBPFSkNvWuddLKPq8A/PqKTDCuPGdOk8vaWErNti5bTLh/Bep3cIs+zuH/de+T/dntWQWyUeJ7YmFvhasIOvUDSt2CkFcFWTj2pyEkvLrUc4E8VKQ29a510so+rwD8+opMMK48Z06T265FfISV+yVexvI1x3J7gz7O4f9175P92e1ZBbJR4ntb5deQaSwvoLx3c/m2EVxBOPanISS8utRzgTxUpDb1rnXSyj6vAPz6ikwwrjxnTpMRCdOCt2blYiFQY0iqczHSPs7h/3Xvk/3Z7VkFslHieyEUg8Q40VDzcBfdZf9qBDw49qchJLy61HOBPFSkNvWuddLKPq8A/PqKTDCuPGdOkyLSoqn4pANCbYlCUJQ4k64+zuH/de+T/dntWQWyUeJ7cmma8X9ON9cQT3KMc1hapTj2pyEkvLrUc4E8VKQ29a510so+rwD8+opMMK48Z06TaZrH8+e8b4nzRw9Rg4dl9T7O4f9175P92e1ZBbJR4nvn2fydoov+kCSLAy9/5dxPRQDknYQDQtd1PooFmrdpifJonqbXU7hByE8KqHd0Fyl6XCAJCs773hUYmv8xoEPVYyt5WbGZ9/gVryP1wU/+vdXiF4xEoxnG8HzI+UC5H5WpCxHR3BqelcSERakQhjwUYyt5WbGZ9/gVryP1wU/+vbmNktjguMNHLoknjGsJf1xjK3lZsZn3+BWvI/XBT/69GIbMlMIceq6gth3XWVED7jj2pyEkvLrUc4E8VKQ29a510so+rwD8+opMMK48Z06TvXh7RC+MP97PWXuQNfAYvj7O4f9175P92e1ZBbJR4nu1QhQWlEc2phBlhLLMJ04bvkDCHjkJz0/qUj7nI1fMvnXSyj6vAPz6ikwwrjxnTpMoDahYOsw1Yc411qlPjwTaPs7h/3Xvk/3Z7VkFslHie8HtGg/4exiZsnBd6FIxp/849qchJLy61HOBPFSkNvWuddLKPq8A/PqKTDCuPGdOk843J/ur2f17dynynoFcv9A+zuH/de+T/dntWQWyUeJ7NN4NKDa6XOeLu+wIBYy3HKWooJPm6UD39zMTrNW7GmNjK3lZsZn3+BWvI/XBT/699mpueav0/ZCxg/ld6o4+3T7O4f9175P92e1ZBbJR4ntcuysRafXOVcHFAoY3ekTVH50GOdXHM7mweHRTAE8wAmMreVmxmff4Fa8j9cFP/r0jqfBWkoh4H/FGk5CUnIC7Ps7h/3Xvk/3Z7VkFslHie2tIrbGrp3eubTAB2Tt08gE49qchJLy61HOBPFSkNvWuddLKPq8A/PqKTDCuPGdOk/ptYjM0zyoLc/zYFJQFhDA+zuH/de+T/dntWQWyUeJ78QvGCKcx4psMUa7i+T0NsNt1s/UM97VdqLnz+YsVWIR10so+rwD8+opMMK48Z06THB0yBF/ogt1iA5Ipw5UkVT7O4f9175P92e1ZBbJR4nvctwwmHcyNaySqiI4JAFRVVFwBQHXLmplAd6VhxCWMJWQm7+rDHQVJRGfHyi8OvC7Vfbw7dv881InD//se32acPs7h/3Xvk/3Z7VkFslHie1NaeVXS08CnbUbbn5kWnGlRTiaqAgG9B958uSQBTXLazB+L7GIqBN3pZ1co9G3aSPxNRI6UmhqKI4osd/c/Lew+zuH/de+T/dntWQWyUeJ7uoeq6OYJF8oia77Z6mEXvMDo6K/OFfLKRweTIIcDW4BjK3lZsZn3+BWvI/XBT/69iNgdt47Wpxlp7uQH9aCRHT7O4f9175P92e1ZBbJR4ntlBs8HEafGZBNXUB2M5KR+rxVLTTPEBuH6wuiQX4kV8kaXJg6fwBYmiGLnJH6j9hKazft85GyCJCv7OB+WWDY7Ps7h/3Xvk/3Z7VkFslHiexPRXshYyl2bhGb0s8dWAxduqxU6cdVDCLKpMlCPGiur8mieptdTuEHITwqod3QXKTRfrJ9GVxkoiOUzbBiAAF5jK3lZsZn3+BWvI/XBT/69OLK08TF1S+IBJJA6XiERKPF0XlvoZxRsUBEU3CR0nG9jK3lZsZn3+BWvI/XBT/69cQDx3GnAWmhb5IdimhcLPGMreVmxmff4Fa8j9cFP/r1Xotc7g7YaJEQJAazDrW9YrPmzuQHAP5fRYaegvPrs52MreVmxmff4Fa8j9cFP/r2bhIZhVP0++VZjHk43D0aRYyt5WbGZ9/gVryP1wU/+vbRsrpaAZlF/sgdRjG1ayosWd1UDv9PPFf5n6TgkyAqx8mieptdTuEHITwqod3QXKS31YQFXr1CgUk/KNV1oBKVjK3lZsZn3+BWvI/XBT/69lQWopNP086ZZRjTi1y3DkR+dBjnVxzO5sHh0UwBPMAJjK3lZsZn3+BWvI/XBT/69RnDscgY5qPYenx2n74TC8j7O4f9175P92e1ZBbJR4nvUeLHOURsddTmXnZmkz8Q2ZaxKE+PbmUG5e0hheOzbqfJonqbXU7hByE8KqHd0FylR1qYdZcH1GWgPOaAqiKCsPs7h/3Xvk/3Z7VkFslHie8fl5GIo3yL2B2nE6HCV0NpkXSL9MchoVc5AE7ceIy58ddLKPq8A/PqKTDCuPGdOk/ie9rbVp5A89lHPjqUufAk+zuH/de+T/dntWQWyUeJ7zxfl3mtQ+9FmiXFCf+GItJIN4LAAyMLNiS4pXNXmo8JjK3lZsZn3+BWvI/XBT/69AVFL93QdciIJoaCfvxzq2z7O4f9175P92e1ZBbJR4nu8lCVNFsJUUrCZO03bOcIxG4hRa3spXNxyj5J0MO3eSXXSyj6vAPz6ikwwrjxnTpPixC7r1rBNa8Sh2cc+Vg7PPs7h/3Xvk/3Z7VkFslHie5g+vYQ/81gLzq40rAeSP+54id+nCyi8bnWBHGSO9bj7Yyt5WbGZ9/gVryP1wU/+vbJdhUwjdNHIQr+rtx3ohMljK3lZsZn3+BWvI/XBT/69CdQygpCbDkeESYMOuPw9LHiJ36cLKLxudYEcZI71uPtjK3lZsZn3+BWvI/XBT/69jmQiC9gdledL3rJxMu6gp2MreVmxmff4Fa8j9cFP/r3Jqh6Op2MPU1bYtXB5kXqleInfpwsovG51gRxkjvW4+2MreVmxmff4Fa8j9cFP/r00/2nMrhJZelSsptUhiiIhYyt5WbGZ9/gVryP1wU/+vVAyUWJhf5Wm3JKVqQgCgv6SCE+i1/itfjFr87ejNyzMYyt5WbGZ9/gVryP1wU/+vca8HNhWSP587SOPQSKu6Ag+zuH/de+T/dntWQWyUeJ7P+ZC46AvkW5yNZku0X3N5dmR7FbQBBfz8fLw+FuT6cJjK3lZsZn3+BWvI/XBT/69TJhUvm3r57na8GKC+/omumMreVmxmff4Fa8j9cFP/r2XtA29QY5P+0+FVioTkA720S4IlBLc9nhgmKE88tggcswfi+xiKgTd6WdXKPRt2kjcUwL7c+9KltVfBwlR6GfXYyt5WbGZ9/gVryP1wU/+vdgLaafgWWiJIHkOAo4sScW4i6ktZg74RLXqmAcxmE7cKqqGNsu35Hra/wnXACmjedOnhleaI9sOhPODRr11HD1jK3lZsZn3+BWvI/XBT/69luSjtS7rVE/7TTk+SWUfg9t1s/UM97VdqLnz+YsVWIR10so+rwD8+opMMK48Z06T7VP5B0oTeJyA2BdCdvEBNz7O4f9175P92e1ZBbJR4nvHug+oOP6biocLtHIe5N/2RnGYTCPXI9dHP54X0UjDffJonqbXU7hByE8KqHd0FykQxFMsDox/QN5DUKsl5z0oYyt5WbGZ9/gVryP1wU/+vR84+iqwslfFlbjxDymvtYesdr73+DYTSwQPT3WKC0uO8mieptdTuEHITwqod3QXKS3kEHiRcLiKVSSzEDYnQYtjK3lZsZn3+BWvI/XBT/69PTkko5ZROb4uvcBd9SKw8Dj2pyEkvLrUc4E8VKQ29a510so+rwD8+opMMK48Z06T42WayWwRDIkI0J0SSZ65+D7O4f9175P92e1ZBbJR4nsoGg1M/tgJc1t9aA0xeyE4OPanISS8utRzgTxUpDb1rnXSyj6vAPz6ikwwrjxnTpOdRXggr+Fkvjfam6Yi9LlXPs7h/3Xvk/3Z7VkFslHiexwB1WqVmeqsAsnczZtJepI49qchJLy61HOBPFSkNvWuddLKPq8A/PqKTDCuPGdOk62sr71nOf80YCS5rBwZ5RA+zuH/de+T/dntWQWyUeJ7iqzaKxy0Ncrce9QnJ6lMx/ivQ8b+GDsuzch4VOI0XCXyaJ6m11O4QchPCqh3dBcpJssNx9p24Mi3a1lDy3drmj7O4f9175P92e1ZBbJR4nuB0bmsw3Ams5AHAe32uR20P2spr2CrwVKeAJLz2QERlfJonqbXU7hByE8KqHd0Fym3FenHIYaw7TUAey9lFM3iPs7h/3Xvk/3Z7VkFslHie8vE3uqhhIY5bWGJakJ7FaN5evfYwhl3+mXxOxiAVjGoYyt5WbGZ9/gVryP1wU/+vU4AEXABUIyMCNItkfzsCrJjK3lZsZn3+BWvI/XBT/69b98kXQQqzt+DwIOHz/CLCrGIVLDD9hOUaINJtQG/4dJ10so+rwD8+opMMK48Z06TsiVBwP6jaTDQbhDrQDO2LD7O4f9175P92e1ZBbJR4nsiQVMsc2XOkeQSIaS614CJenGZKIkAZqIXcZ4WZFM4x6MYDjWUtwHdKu9KxBzLMPhHa8Xy0YT00x34jX8SfozNPs7h/3Xvk/3Z7VkFslHie4HBDPsZB5fF2mDK/xBJ2pQ49qchJLy61HOBPFSkNvWuddLKPq8A/PqKTDCuPGdOkwtWwAzcCuBaktkKl6pHXyY+zuH/de+T/dntWQWyUeJ7YaeTQ/dySWSk/PpFH3awBzj2pyEkvLrUc4E8VKQ29a510so+rwD8+opMMK48Z06T6Q/3RRwrXXco6Md0an4nTj7O4f9175P92e1ZBbJR4nsfsG6e5lD5aIZE3hQS0mSmA+AgWYMXqylFnCZnfWMo13XSyj6vAPz6ikwwrjxnTpP2FafOt8p6r72tzqpCTWHQYyt5WbGZ9/gVryP1wU/+vcsctBPUGBHs3c0j6jhX7g8UwByYPqOes+uCr8L7HjpuYyt5WbGZ9/gVryP1wU/+vZUgQaD9PQnsbOoSPXadTqY+zuH/de+T/dntWQWyUeJ7OICqruPRzb2fF0WOl/32gRZNqmJQB7cTRuimddmQhnpjK3lZsZn3+BWvI/XBT/69gZbFBkae0MR+oPqpEehg1D7O4f9175P92e1ZBbJR4nssOv55iRTletOrKmdx5HZs7PsIdC8mh+BXDMD/Zcd2QvJonqbXU7hByE8KqHd0FynCTJov/tePAskoHLbXniCRYyt5WbGZ9/gVryP1wU/+vVr00RnFnRc5FzlXz58WHfZ7S+sXajlppx5w2blMCLdMYyt5WbGZ9/gVryP1wU/+vW11SCq35mKKASgNpX+nSUpjK3lZsZn3+BWvI/XBT/69E7l2Iqej7O0CpSJowLdeK9t1s/UM97VdqLnz+YsVWIR10so+rwD8+opMMK48Z06TJKyFY9JNvn1Cm5nqG9DpnGMreVmxmff4Fa8j9cFP/r1OYbLIP2avYhF/vQaiue6YNkiWxWRSEpXlcIrD17R+l/JonqbXU7hByE8KqHd0FykNTFDeR/csYeQi8mD86Q67Yyt5WbGZ9/gVryP1wU/+vWKz+43LThgNZoCtMIbCqkLnOsTMzF4kt64pGJ3KBLkB8mieptdTuEHITwqod3QXKc6nVQHCJ2yUPiR8L068QRM+zuH/de+T/dntWQWyUeJ7WOq6xlonO5+Efjc8VhQPRajlfjI+BGk2UHq+kCybnLuUJ6c/2FWT/HGziLe4vDaILQciLo3WIlNftH4y/uJJeGE5qYLdzmRWlubtnA0mqbk=	non_priority	bwvi xbt yp s e zuh de t bwvi xbt zuh de t vqicftah bwvi xbt ewq zuh de t zuh de t zuh de t bwvi xbt zuh de t bwvi xbt zcxg pqktdcupgdok zyfjqfhda zuh de t c lew zuh de t bwvi xbt bwvi xbt bwvi xbt vbrsrpaazlf bwvi xbt bwvi xbt pqktdcupgdok zuh de t bwvi xbt vyq vbjdhuwjdnhiqr bwvi xbt bwvi xbt zuh de t bwvi xbt bwvi xbt bwvi xbt zuh de t bwvi xbt dwiohz zuh de t dyswsk zuh de t bwvi xbt bxdmd bwvi xbt l vwkz zuh de t
22,012	14,964,987,266	IssuesEvent	2021-01-27 12:46:40	Rothamsted/knetminer	https://api.github.com/repos/Rothamsted/knetminer	opened	Integration tests against real datasets	chore/infrastructure new feature	We should add automated tests against real datasets to the CI workflows. Several types of tests should be put in place: - Test Ondex/OXL dataset, by loading them in memory and using the Ondex API interfaces - Test at least one Knetminer instance using its current web API, possibly write extensions for it. - Test against SPARQL/Neo4j endpoint using the respective query languages In all the cases above tests would mostly consist of checking expected patterns in the dataset, eg, - the concepts/relation counts are > given constants - counts of certain concept types are > thresholds - certain graph paths exist - the graph traverser returns certain expected paths For the Ondex tests, a good way to proceed would be to realise fluent interfaces to access an Ondex graph and then to integrate them into a scripting language like Groovy, have a look [here][10] for a few details. For the Knetminer tests, probably a good way is to first ensure that the API always (or in most cases) returns JSON and then use something like [JSONPath][20] to write the tests. For the SPARQL and Cypher tests, we have already test utilities, [SPARQL tests via script][30], [Jena/SPARQL tests][40] (needs to be adapted to generic endpoint, not just Jena-based SPARQL wrappers), [Cypher/Java tests][50]. [10]: https://docs.google.com/document/d/1nDYOSwATuwrOAED9M7S2vEGHu9o6oklrgFXJpFKMQNo/edit?usp=sharing [20]: https://www.baeldung.com/guide-to-jayway-jsonpath [30]: https://github.com/marco-brandizi/rdfutils/tree/master/virtuoso-utils/sparql_unit_testing [40]: https://github.com/marco-brandizi/rdfutils/blob/master/rdfutils-jena/src/main/java/info/marcobrandizi/rdfutils/jena/SparqlBasedTester.java [50]: https://github.com/marco-brandizi/rdfutils/blob/master/rdfutils-jena/src/main/java/info/marcobrandizi/rdfutils/jena/SparqlBasedTester.java	1.0	Integration tests against real datasets - We should add automated tests against real datasets to the CI workflows. Several types of tests should be put in place: - Test Ondex/OXL dataset, by loading them in memory and using the Ondex API interfaces - Test at least one Knetminer instance using its current web API, possibly write extensions for it. - Test against SPARQL/Neo4j endpoint using the respective query languages In all the cases above tests would mostly consist of checking expected patterns in the dataset, eg, - the concepts/relation counts are > given constants - counts of certain concept types are > thresholds - certain graph paths exist - the graph traverser returns certain expected paths For the Ondex tests, a good way to proceed would be to realise fluent interfaces to access an Ondex graph and then to integrate them into a scripting language like Groovy, have a look [here][10] for a few details. For the Knetminer tests, probably a good way is to first ensure that the API always (or in most cases) returns JSON and then use something like [JSONPath][20] to write the tests. For the SPARQL and Cypher tests, we have already test utilities, [SPARQL tests via script][30], [Jena/SPARQL tests][40] (needs to be adapted to generic endpoint, not just Jena-based SPARQL wrappers), [Cypher/Java tests][50]. [10]: https://docs.google.com/document/d/1nDYOSwATuwrOAED9M7S2vEGHu9o6oklrgFXJpFKMQNo/edit?usp=sharing [20]: https://www.baeldung.com/guide-to-jayway-jsonpath [30]: https://github.com/marco-brandizi/rdfutils/tree/master/virtuoso-utils/sparql_unit_testing [40]: https://github.com/marco-brandizi/rdfutils/blob/master/rdfutils-jena/src/main/java/info/marcobrandizi/rdfutils/jena/SparqlBasedTester.java [50]: https://github.com/marco-brandizi/rdfutils/blob/master/rdfutils-jena/src/main/java/info/marcobrandizi/rdfutils/jena/SparqlBasedTester.java	non_priority	integration tests against real datasets we should add automated tests against real datasets to the ci workflows several types of tests should be put in place test ondex oxl dataset by loading them in memory and using the ondex api interfaces test at least one knetminer instance using its current web api possibly write extensions for it test against sparql endpoint using the respective query languages in all the cases above tests would mostly consist of checking expected patterns in the dataset eg the concepts relation counts are given constants counts of certain concept types are thresholds certain graph paths exist the graph traverser returns certain expected paths for the ondex tests a good way to proceed would be to realise fluent interfaces to access an ondex graph and then to integrate them into a scripting language like groovy have a look for a few details for the knetminer tests probably a good way is to first ensure that the api always or in most cases returns json and then use something like to write the tests for the sparql and cypher tests we have already test utilities needs to be adapted to generic endpoint not just jena based sparql wrappers
365,076	25,519,478,905	IssuesEvent	2022-11-28 19:09:29	tmforum-oda/oda-ca-docs	https://api.github.com/repos/tmforum-oda/oda-ca-docs	closed	Adding some new presentation links to the Playbook page	documentation	## Description Adding a general presentation and some links to the DTW presentations on the Playbook page	1.0	Adding some new presentation links to the Playbook page - ## Description Adding a general presentation and some links to the DTW presentations on the Playbook page	non_priority	adding some new presentation links to the playbook page description adding a general presentation and some links to the dtw presentations on the playbook page
212,392	16,446,917,012	IssuesEvent	2021-05-20 20:47:24	eclipse-openj9/openj9	https://api.github.com/repos/eclipse-openj9/openj9	closed	jtreg java/util/zip/DeInflate.java inflate failures, length mismatch	comp:test test failure	https://ci.eclipse.org/openj9/job/Test_openjdk11_j9_sanity.openjdk_s390x_linux_OpenJDK11/40/ java/util/zip/DeInflate.java Fails on Ubunut 20 machines ub20-390-1 and 2 (Eclipse jenkins ub16-390-1 and 2), passed on a ub18 machine. The failure is not related to the new OpenJDK level. ``` 06:20:19 m=525312, n=498076, len=524288, eq=false 06:20:19 STDERR: 06:20:19 java.lang.RuntimeException: De/inflater failed:java.util.zip.Deflater@4b610026 06:20:19 at DeInflate.check(DeInflate.java:141) 06:20:19 at DeInflate.main(DeInflate.java:290) 06:31:28 m=525312, n=498093, len=524288, eq=false 06:31:28 STDERR: 06:31:28 java.lang.RuntimeException: De/inflater failed:java.util.zip.Deflater@5c1f2389 06:31:28 at DeInflate.check(DeInflate.java:141) 06:31:28 at DeInflate.main(DeInflate.java:290) ```	2.0	jtreg java/util/zip/DeInflate.java inflate failures, length mismatch - https://ci.eclipse.org/openj9/job/Test_openjdk11_j9_sanity.openjdk_s390x_linux_OpenJDK11/40/ java/util/zip/DeInflate.java Fails on Ubunut 20 machines ub20-390-1 and 2 (Eclipse jenkins ub16-390-1 and 2), passed on a ub18 machine. The failure is not related to the new OpenJDK level. ``` 06:20:19 m=525312, n=498076, len=524288, eq=false 06:20:19 STDERR: 06:20:19 java.lang.RuntimeException: De/inflater failed:java.util.zip.Deflater@4b610026 06:20:19 at DeInflate.check(DeInflate.java:141) 06:20:19 at DeInflate.main(DeInflate.java:290) 06:31:28 m=525312, n=498093, len=524288, eq=false 06:31:28 STDERR: 06:31:28 java.lang.RuntimeException: De/inflater failed:java.util.zip.Deflater@5c1f2389 06:31:28 at DeInflate.check(DeInflate.java:141) 06:31:28 at DeInflate.main(DeInflate.java:290) ```	non_priority	jtreg java util zip deinflate java inflate failures length mismatch java util zip deinflate java fails on ubunut machines and eclipse jenkins and passed on a machine the failure is not related to the new openjdk level m n len eq false stderr java lang runtimeexception de inflater failed java util zip deflater at deinflate check deinflate java at deinflate main deinflate java m n len eq false stderr java lang runtimeexception de inflater failed java util zip deflater at deinflate check deinflate java at deinflate main deinflate java
106,881	11,501,144,625	IssuesEvent	2020-02-12 16:40:25	huggingface/transformers	https://api.github.com/repos/huggingface/transformers	closed	PreTrainedModel.generate do_sample default argument is wrong in the documentation	Core: Modeling Documentation PyTorch	# 🐛 Bug ## Information Model I am using (Bert, XLNet ...): GPT2LMHeadModel Language I am using the model on (English, Chinese ...): English The problem arises when using: * [ ] the official example scripts: (give details below) * [X] my own modified scripts: (give details below) The tasks I am working on is: * [ ] an official GLUE/SQUaD task: (give the name) * [X] my own task or dataset: (give details below) ## To reproduce Steps to reproduce the behavior: 1. Create GPT2LMHeadModel and GPT2Tokenizer objects using the from_pretrained('gpt2') method 2. Use the generate function to generate sequences without any input argument multiple times, and then repeat by setting do_sample = True 3. When do_sample is set to False (or is not supplied at all), the generate method constantly generates the following string: '!\n\nThe first thing I did was to make a list of all the things I would!' When generating with do_sample set to True, changing results are outputted. This is consistent with the behaviour described in the code, except for the default value of do_sample Code sample from a python shell: '''python >>> model = transformers.GPT2LMHeadModel.from_pretrained('gpt2') >>> g2t = transformers.GPT2Tokenizer.from_pretrained('gpt2') >>> g2t.decode(model.generate()[0]) '!\n\nThe first thing I did was to make a list of all the things I would!' >>> g2t.decode(model.generate()[0]) '!\n\nThe first thing I did was to make a list of all the things I would!' >>> g2t.decode(model.generate()[0]) '!\n\nThe first thing I did was to make a list of all the things I would!' >>> g2t.decode(model.generate(do_sample=True)[0]) "!, I can't help but wonder how she's doing. I really have no idea.!" >>> g2t.decode(model.generate(do_sample=True)[0]) '!\n\nThe other guy is trying to take something away from the guy before you even start!' >>> g2t.decode(model.generate(do_sample=True)[0]) '! are you kidding me?\n\n\nBut maybe you should wait for his own "last act!' ''' Similarly, you can do print((transformers.GPT2LMHeadModel.from_pretrained('gpt2')).config.do_sample) to verify that the 'default' argument is in fact False ## Expected behavior The documentation should say do_sample is False by default OR the config should be updated to be in line with the documentation ## Environment info <!-- You can run the command `python transformers-cli env` and copy-and-paste its output below. Don't forget to fill out the missing fields in that output! --> - `transformers` version: 2.4.1 - Platform: Ubuntu GNU/Linux 18.04 - Python version: Python 3.6.9 (default, Nov 7 2019, 10:44:02) [GCC 8.3.0] on linux - PyTorch version (GPU?): 1.4.0 GPU version with Nvidia RTX 2080Ti - Tensorflow version (GPU?): N/A - Using GPU in script?: No - Using distributed or parallel set-up in script?: No	1.0	PreTrainedModel.generate do_sample default argument is wrong in the documentation - # 🐛 Bug ## Information Model I am using (Bert, XLNet ...): GPT2LMHeadModel Language I am using the model on (English, Chinese ...): English The problem arises when using: * [ ] the official example scripts: (give details below) * [X] my own modified scripts: (give details below) The tasks I am working on is: * [ ] an official GLUE/SQUaD task: (give the name) * [X] my own task or dataset: (give details below) ## To reproduce Steps to reproduce the behavior: 1. Create GPT2LMHeadModel and GPT2Tokenizer objects using the from_pretrained('gpt2') method 2. Use the generate function to generate sequences without any input argument multiple times, and then repeat by setting do_sample = True 3. When do_sample is set to False (or is not supplied at all), the generate method constantly generates the following string: '!\n\nThe first thing I did was to make a list of all the things I would!' When generating with do_sample set to True, changing results are outputted. This is consistent with the behaviour described in the code, except for the default value of do_sample Code sample from a python shell: '''python >>> model = transformers.GPT2LMHeadModel.from_pretrained('gpt2') >>> g2t = transformers.GPT2Tokenizer.from_pretrained('gpt2') >>> g2t.decode(model.generate()[0]) '!\n\nThe first thing I did was to make a list of all the things I would!' >>> g2t.decode(model.generate()[0]) '!\n\nThe first thing I did was to make a list of all the things I would!' >>> g2t.decode(model.generate()[0]) '!\n\nThe first thing I did was to make a list of all the things I would!' >>> g2t.decode(model.generate(do_sample=True)[0]) "!, I can't help but wonder how she's doing. I really have no idea.!" >>> g2t.decode(model.generate(do_sample=True)[0]) '!\n\nThe other guy is trying to take something away from the guy before you even start!' >>> g2t.decode(model.generate(do_sample=True)[0]) '! are you kidding me?\n\n\nBut maybe you should wait for his own "last act!' ''' Similarly, you can do print((transformers.GPT2LMHeadModel.from_pretrained('gpt2')).config.do_sample) to verify that the 'default' argument is in fact False ## Expected behavior The documentation should say do_sample is False by default OR the config should be updated to be in line with the documentation ## Environment info <!-- You can run the command `python transformers-cli env` and copy-and-paste its output below. Don't forget to fill out the missing fields in that output! --> - `transformers` version: 2.4.1 - Platform: Ubuntu GNU/Linux 18.04 - Python version: Python 3.6.9 (default, Nov 7 2019, 10:44:02) [GCC 8.3.0] on linux - PyTorch version (GPU?): 1.4.0 GPU version with Nvidia RTX 2080Ti - Tensorflow version (GPU?): N/A - Using GPU in script?: No - Using distributed or parallel set-up in script?: No	non_priority	pretrainedmodel generate do sample default argument is wrong in the documentation 🐛 bug information model i am using bert xlnet language i am using the model on english chinese english the problem arises when using the official example scripts give details below my own modified scripts give details below the tasks i am working on is an official glue squad task give the name my own task or dataset give details below to reproduce steps to reproduce the behavior create and objects using the from pretrained method use the generate function to generate sequences without any input argument multiple times and then repeat by setting do sample true when do sample is set to false or is not supplied at all the generate method constantly generates the following string n nthe first thing i did was to make a list of all the things i would when generating with do sample set to true changing results are outputted this is consistent with the behaviour described in the code except for the default value of do sample code sample from a python shell python model transformers from pretrained transformers from pretrained decode model generate n nthe first thing i did was to make a list of all the things i would decode model generate n nthe first thing i did was to make a list of all the things i would decode model generate n nthe first thing i did was to make a list of all the things i would decode model generate do sample true i can t help but wonder how she s doing i really have no idea decode model generate do sample true n nthe other guy is trying to take something away from the guy before you even start decode model generate do sample true are you kidding me n n nbut maybe you should wait for his own last act similarly you can do print transformers from pretrained config do sample to verify that the default argument is in fact false expected behavior the documentation should say do sample is false by default or the config should be updated to be in line with the documentation environment info you can run the command python transformers cli env and copy and paste its output below don t forget to fill out the missing fields in that output transformers version platform ubuntu gnu linux python version python default nov on linux pytorch version gpu gpu version with nvidia rtx tensorflow version gpu n a using gpu in script no using distributed or parallel set up in script no
16,711	23,044,241,030	IssuesEvent	2022-07-23 16:40:57	ValveSoftware/Proton	https://api.github.com/repos/ValveSoftware/Proton	closed	Alice: Madness Returns (19680)	Game compatibility - Unofficial	# Compatibility Report - Name of the game with compatibility issues: - Steam AppID of the game: ## System Information - GPU: <!-- e.g. RX 580 or GTX 970 --> - Driver/LLVM version: <!-- e.g. Mesa 18.2/7.0.0 or nvidia 396.54 --> - Kernel version: <!-- e.g. 4.17 --> - Link to full system information report as [Gist](https://gist.github.com/): - Proton version: ## I confirm: - [x] that I haven't found an existing compatibility report for this game. - [x] that I have checked whether there are updates for my system available. <!-- Please add `PROTON_LOG=1 %command%` to the game's launch options and attach the generated $HOME/steam-$APPID.log to this issue report as a file. (Proton logs compress well if needed.)--> ## Symptoms <!-- What's the problem? --> ## Reproduction <!-- 1. You can find the Steam AppID in the URL of the shop page of the game. e.g. for `The Witcher 3: Wild Hunt` the AppID is `292030`. 2. You can find your driver and Linux version, as well as your graphics processor's name in the system information report of Steam. 3. You can retrieve a full system information report by clicking `Help` > `System Information` in the Steam client on your machine. 4. Please copy it to your clipboard by pressing `Ctrl+A` and then `Ctrl+C`. Then paste it in a [Gist](https://gist.github.com/) and post the link in this issue. 5. Please search for open issues and pull requests by the name of the game and find out whether they are relevant and should be referenced above. -->	True	Alice: Madness Returns (19680) - # Compatibility Report - Name of the game with compatibility issues: - Steam AppID of the game: ## System Information - GPU: <!-- e.g. RX 580 or GTX 970 --> - Driver/LLVM version: <!-- e.g. Mesa 18.2/7.0.0 or nvidia 396.54 --> - Kernel version: <!-- e.g. 4.17 --> - Link to full system information report as [Gist](https://gist.github.com/): - Proton version: ## I confirm: - [x] that I haven't found an existing compatibility report for this game. - [x] that I have checked whether there are updates for my system available. <!-- Please add `PROTON_LOG=1 %command%` to the game's launch options and attach the generated $HOME/steam-$APPID.log to this issue report as a file. (Proton logs compress well if needed.)--> ## Symptoms <!-- What's the problem? --> ## Reproduction <!-- 1. You can find the Steam AppID in the URL of the shop page of the game. e.g. for `The Witcher 3: Wild Hunt` the AppID is `292030`. 2. You can find your driver and Linux version, as well as your graphics processor's name in the system information report of Steam. 3. You can retrieve a full system information report by clicking `Help` > `System Information` in the Steam client on your machine. 4. Please copy it to your clipboard by pressing `Ctrl+A` and then `Ctrl+C`. Then paste it in a [Gist](https://gist.github.com/) and post the link in this issue. 5. Please search for open issues and pull requests by the name of the game and find out whether they are relevant and should be referenced above. -->	non_priority	alice madness returns compatibility report name of the game with compatibility issues steam appid of the game system information gpu driver llvm version kernel version link to full system information report as proton version i confirm that i haven t found an existing compatibility report for this game that i have checked whether there are updates for my system available please add proton log command to the game s launch options and attach the generated home steam appid log to this issue report as a file proton logs compress well if needed symptoms reproduction you can find the steam appid in the url of the shop page of the game e g for the witcher wild hunt the appid is you can find your driver and linux version as well as your graphics processor s name in the system information report of steam you can retrieve a full system information report by clicking help system information in the steam client on your machine please copy it to your clipboard by pressing ctrl a and then ctrl c then paste it in a and post the link in this issue please search for open issues and pull requests by the name of the game and find out whether they are relevant and should be referenced above
38,724	15,785,771,234	IssuesEvent	2021-04-01 16:47:33	MicrosoftDocs/live-share	https://api.github.com/repos/MicrosoftDocs/live-share	reopened	save error	area: language services p2 product-feedback	The problem is easy to describe: 1. Host edits file 2. Guest also edits file 3. Guest saves file For us at least, on the guest's end, it looks as though the file is saved, but on the host's end, the file does not actually get saved. If the guest saves again, then the save actually propagates to the host's computer. Same deal for the host: 1. Host edits file 2. Guest also edits file 3. Host saves file It will appear to the guest as though the host didn't in fact save the file, until the host saves twice. This bug really doesn't matter that much though, because on the host's end, the file does indeed get saved on the first try. The order of 1 and 2 do not matter. Just that both guest and host edit, but only one tries to save the changes.	1.0	save error - The problem is easy to describe: 1. Host edits file 2. Guest also edits file 3. Guest saves file For us at least, on the guest's end, it looks as though the file is saved, but on the host's end, the file does not actually get saved. If the guest saves again, then the save actually propagates to the host's computer. Same deal for the host: 1. Host edits file 2. Guest also edits file 3. Host saves file It will appear to the guest as though the host didn't in fact save the file, until the host saves twice. This bug really doesn't matter that much though, because on the host's end, the file does indeed get saved on the first try. The order of 1 and 2 do not matter. Just that both guest and host edit, but only one tries to save the changes.	non_priority	save error the problem is easy to describe host edits file guest also edits file guest saves file for us at least on the guest s end it looks as though the file is saved but on the host s end the file does not actually get saved if the guest saves again then the save actually propagates to the host s computer same deal for the host host edits file guest also edits file host saves file it will appear to the guest as though the host didn t in fact save the file until the host saves twice this bug really doesn t matter that much though because on the host s end the file does indeed get saved on the first try the order of and do not matter just that both guest and host edit but only one tries to save the changes
5,239	3,908,831,767	IssuesEvent	2016-04-19 17:09:16	cul-it/mann-wagon	https://api.github.com/repos/cul-it/mann-wagon	closed	Create a template that will render results from temporary site search index	usability	~~See #92~~ edited by @cappadona	True	Create a template that will render results from temporary site search index - ~~See #92~~ edited by @cappadona	non_priority	create a template that will render results from temporary site search index see edited by cappadona
57,735	16,020,380,376	IssuesEvent	2021-04-20 21:59:48	primefaces/primereact	https://api.github.com/repos/primefaces/primereact	closed	SlideMenu menu model template has wrong classname	defect	I'm submitting a ... (check one with "x") ``` [ x ] bug report [ ] feature request [ ] support request => Please do not submit support request here, instead see https://forum.primefaces.org/viewforum.php?f=57 ``` Current behavior When working with the menu model for the SlideMenu, the options.className is set to p-menuitem. This causes issues with the default styling of the component(p-menuitem-link styles do not get applied at all). Expected behavior When working with the menu model for the SlideMenu, the options.className should be set to p-menuitem-link. This is how the rest of the menu components work and would allow for easy passthrough when creating your own template items. Minimal reproduction of the problem with instructions Create a template for the SlideMenu model items. Grab the className from the options. The className is set to p-menuitem which causes weird styling issues and the SlideMenu will not look right. This should be p-menuitem-link like the rest of the Menu components have the className correctly set to when working with the menu model. Please tell us about your environment: Windows, VSCode, Chrome * React version: ^17.0.1, ^16.8.0 * PrimeReact version: ^6.2.1 * Browser: [all] * Language: [all]	1.0	SlideMenu menu model template has wrong classname - I'm submitting a ... (check one with "x") ``` [ x ] bug report [ ] feature request [ ] support request => Please do not submit support request here, instead see https://forum.primefaces.org/viewforum.php?f=57 ``` Current behavior When working with the menu model for the SlideMenu, the options.className is set to p-menuitem. This causes issues with the default styling of the component(p-menuitem-link styles do not get applied at all). Expected behavior When working with the menu model for the SlideMenu, the options.className should be set to p-menuitem-link. This is how the rest of the menu components work and would allow for easy passthrough when creating your own template items. Minimal reproduction of the problem with instructions Create a template for the SlideMenu model items. Grab the className from the options. The className is set to p-menuitem which causes weird styling issues and the SlideMenu will not look right. This should be p-menuitem-link like the rest of the Menu components have the className correctly set to when working with the menu model. Please tell us about your environment: Windows, VSCode, Chrome * React version: ^17.0.1, ^16.8.0 * PrimeReact version: ^6.2.1 * Browser: [all] * Language: [all]	non_priority	slidemenu menu model template has wrong classname i m submitting a check one with x bug report feature request support request please do not submit support request here instead see current behavior when working with the menu model for the slidemenu the options classname is set to p menuitem this causes issues with the default styling of the component p menuitem link styles do not get applied at all expected behavior when working with the menu model for the slidemenu the options classname should be set to p menuitem link this is how the rest of the menu components work and would allow for easy passthrough when creating your own template items minimal reproduction of the problem with instructions create a template for the slidemenu model items grab the classname from the options the classname is set to p menuitem which causes weird styling issues and the slidemenu will not look right this should be p menuitem link like the rest of the menu components have the classname correctly set to when working with the menu model please tell us about your environment windows vscode chrome react version primereact version browser language
192,777	14,629,164,215	IssuesEvent	2020-12-23 15:23:26	deathlyrage/pot-demo-bugs	https://api.github.com/repos/deathlyrage/pot-demo-bugs	closed	sound	needs testing	Location: (X=244322.234375,Y=-218446.921875,Z=-3158.881592) ![](https://mapbug.alderongames.com/uploads/(X=244322.234375,Y=-218446.921875,Z=-3158.881592).jpg) Message: when the cerato goes on some grass in any part of the map it goes dead silence no thud sound when troting or spiriting Version: 8790 (demo) Reporter: Raivmoon (283-177-658)	1.0	sound - Location: (X=244322.234375,Y=-218446.921875,Z=-3158.881592) ![](https://mapbug.alderongames.com/uploads/(X=244322.234375,Y=-218446.921875,Z=-3158.881592).jpg) Message: when the cerato goes on some grass in any part of the map it goes dead silence no thud sound when troting or spiriting Version: 8790 (demo) Reporter: Raivmoon (283-177-658)	non_priority	sound location x y z message when the cerato goes on some grass in any part of the map it goes dead silence no thud sound when troting or spiriting version demo reporter raivmoon
90,332	10,678,880,599	IssuesEvent	2019-10-21 18:09:54	PeterCamilleri/test65	https://api.github.com/repos/PeterCamilleri/test65	closed	Rename option	documentation enhancement	The debug option should be renamed to verbose like: -v or --verbose The version option should just be: --version This will be more in line with user expectations.	1.0	Rename option - The debug option should be renamed to verbose like: -v or --verbose The version option should just be: --version This will be more in line with user expectations.	non_priority	rename option the debug option should be renamed to verbose like v or verbose the version option should just be version this will be more in line with user expectations
218,570	16,763,848,828	IssuesEvent	2021-06-14 05:59:29	sarl/sarl	https://api.github.com/repos/sarl/sarl	opened	Create a tutorial for creating a executable JAR.	0 - Backlog Documentation enhancement	An executable JAR is usually used for creating a standalone SARL application. The creation of this executable JAR have several specific points that should be explained. <!--- @huboard:{"order":2.5733723742784353e-54,"milestone_order":6.750285807555175e-59} -->	1.0	Create a tutorial for creating a executable JAR. - An executable JAR is usually used for creating a standalone SARL application. The creation of this executable JAR have several specific points that should be explained. <!--- @huboard:{"order":2.5733723742784353e-54,"milestone_order":6.750285807555175e-59} -->	non_priority	create a tutorial for creating a executable jar an executable jar is usually used for creating a standalone sarl application the creation of this executable jar have several specific points that should be explained huboard order milestone order
164,790	26,024,677,097	IssuesEvent	2022-12-21 15:23:44	department-of-veterans-affairs/va.gov-team	https://api.github.com/repos/department-of-veterans-affairs/va.gov-team	opened	Landing / Map for aggregation of insights & feedback	service-design	## Issue Description What about a landing that has the feedback of various inputs portals? A pain point map. And research could also be linked to relevant areas This could provide a hub that OCTO leadership, Tech teams, and fixed teams can reference for guidance on problem areas and the research surrounding them ## Tasks - [ ] ## Acceptance Criteria - [ ]	1.0	Landing / Map for aggregation of insights & feedback - ## Issue Description What about a landing that has the feedback of various inputs portals? A pain point map. And research could also be linked to relevant areas This could provide a hub that OCTO leadership, Tech teams, and fixed teams can reference for guidance on problem areas and the research surrounding them ## Tasks - [ ] ## Acceptance Criteria - [ ]	non_priority	landing map for aggregation of insights feedback issue description what about a landing that has the feedback of various inputs portals a pain point map and research could also be linked to relevant areas this could provide a hub that octo leadership tech teams and fixed teams can reference for guidance on problem areas and the research surrounding them tasks acceptance criteria
195,992	14,789,223,724	IssuesEvent	2021-01-12 10:16:57	ReneNulschDE/mbapi2020	https://api.github.com/repos/ReneNulschDE/mbapi2020	closed	device_tracker only updates once	bug retest-needed	Hi, the device_tracker with GPS coordinates just gets updated if I restart Home Assistant. Is there any way to fix that?	1.0	device_tracker only updates once - Hi, the device_tracker with GPS coordinates just gets updated if I restart Home Assistant. Is there any way to fix that?	non_priority	device tracker only updates once hi the device tracker with gps coordinates just gets updated if i restart home assistant is there any way to fix that
5,986	4,107,695,853	IssuesEvent	2016-06-06 13:55:15	cul-it/mann-wagon	https://api.github.com/repos/cul-it/mann-wagon	closed	Usability task for hours (consultation services)	Epic usability	You've heard that CISER consultants have walk-in hours at Mann. What time does the CISER help desk at Mann open tomorrow?	True	Usability task for hours (consultation services) - You've heard that CISER consultants have walk-in hours at Mann. What time does the CISER help desk at Mann open tomorrow?	non_priority	usability task for hours consultation services you ve heard that ciser consultants have walk in hours at mann what time does the ciser help desk at mann open tomorrow
28,992	4,461,355,115	IssuesEvent	2016-08-24 05:01:25	lo-co/exscalabar_server	https://api.github.com/repos/lo-co/exscalabar_server	closed	pressure controller not initilising	READY FOR TESTING	pressure controller is not initialising from the ini file correctly. It defaults to 0mb! This may be because we are using the wrong command in the ini file? C ommand we've inserted is: > prCntl.p0 = 1100.00	1.0	pressure controller not initilising - pressure controller is not initialising from the ini file correctly. It defaults to 0mb! This may be because we are using the wrong command in the ini file? C ommand we've inserted is: > prCntl.p0 = 1100.00	non_priority	pressure controller not initilising pressure controller is not initialising from the ini file correctly it defaults to this may be because we are using the wrong command in the ini file c ommand we ve inserted is prcntl
22,349	7,160,435,104	IssuesEvent	2018-01-28 00:30:38	tobyroworth/Crown-PA-Docs-Site	https://api.github.com/repos/tobyroworth/Crown-PA-Docs-Site	closed	App fails to load in Safari	build	The app loads in Safari (v11.0.2) but none of the panels are click-able. On render, the console displays these error messages: - SyntaxError: Cannot use keyword as imported binding name. - Failed to load resource: the server responded with a status of 404 (HTTP/2.0 404) https://crownpa-docs.firebaseapp.com/node_modules/@webcomponents/webcomponentsjs/webcomponents-hi.js	1.0	App fails to load in Safari - The app loads in Safari (v11.0.2) but none of the panels are click-able. On render, the console displays these error messages: - SyntaxError: Cannot use keyword as imported binding name. - Failed to load resource: the server responded with a status of 404 (HTTP/2.0 404) https://crownpa-docs.firebaseapp.com/node_modules/@webcomponents/webcomponentsjs/webcomponents-hi.js	non_priority	app fails to load in safari the app loads in safari but none of the panels are click able on render the console displays these error messages syntaxerror cannot use keyword as imported binding name failed to load resource the server responded with a status of http
163,509	13,920,532,402	IssuesEvent	2020-10-21 10:34:36	daejo/just-tech-news	https://api.github.com/repos/daejo/just-tech-news	closed	Create a single post page	documentation	* As a user, I can view an article's details on a separate page. * As a logged-in user, I can add a comment to an article. * As a logged-in user, I can upvote an article.	1.0	Create a single post page - * As a user, I can view an article's details on a separate page. * As a logged-in user, I can add a comment to an article. * As a logged-in user, I can upvote an article.	non_priority	create a single post page as a user i can view an article s details on a separate page as a logged in user i can add a comment to an article as a logged in user i can upvote an article
184,708	14,987,941,857	IssuesEvent	2021-01-29 00:02:36	LuisFalconMX/strapi	https://api.github.com/repos/LuisFalconMX/strapi	closed	Enhance Readme.md	documentation	The readme file could be best seen with next features: - [ ] Oficial Strapi logo in header - [ ] Badges with version of each dependency - [ ] Cover of the project live To create the badges could be used: https://github.com/badges/shields and https://simpleicons.org/.	1.0	Enhance Readme.md - The readme file could be best seen with next features: - [ ] Oficial Strapi logo in header - [ ] Badges with version of each dependency - [ ] Cover of the project live To create the badges could be used: https://github.com/badges/shields and https://simpleicons.org/.	non_priority	enhance readme md the readme file could be best seen with next features oficial strapi logo in header badges with version of each dependency cover of the project live to create the badges could be used and
121,351	15,892,985,312	IssuesEvent	2021-04-11 03:11:54	pandas-dev/pandas	https://api.github.com/repos/pandas-dev/pandas	closed	Support for Merging Columns in HTML Parser	API Design Enhancement IO HTML	See the table here: http://www.sec.gov/Archives/edgar/data/47217/000104746913006802/a2215416z10-q.htm#CCSE the trailing ")" and the leading "$" are in different columns (aka td's / cells) from the number.. There should be an option to merge all column under a given heading (#4679).	1.0	Support for Merging Columns in HTML Parser - See the table here: http://www.sec.gov/Archives/edgar/data/47217/000104746913006802/a2215416z10-q.htm#CCSE the trailing ")" and the leading "$" are in different columns (aka td's / cells) from the number.. There should be an option to merge all column under a given heading (#4679).	non_priority	support for merging columns in html parser see the table here the trailing and the leading are in different columns aka td s cells from the number there should be an option to merge all column under a given heading
293,273	22,050,725,437	IssuesEvent	2022-05-30 08:25:17	Ubungsaufgabe/.github	https://api.github.com/repos/Ubungsaufgabe/.github	opened	Repository Restrictions	documentation	This repository was created by: organization-workflows[bot]. There are 2 reviews required on this repository as per organization rules. Notifying @knowncitizen Additional information: Ref?: refs/heads/main Repo?: [object Object] Original payload: [object Object]	1.0	Repository Restrictions - This repository was created by: organization-workflows[bot]. There are 2 reviews required on this repository as per organization rules. Notifying @knowncitizen Additional information: Ref?: refs/heads/main Repo?: [object Object] Original payload: [object Object]	non_priority	repository restrictions this repository was created by organization workflows there are reviews required on this repository as per organization rules notifying knowncitizen additional information ref refs heads main repo original payload
14,321	2,798,410,461	IssuesEvent	2015-05-12 18:29:12	skaut/dsw-oddil	https://api.github.com/repos/skaut/dsw-oddil	closed	Wordpress 4.2 hlásí chybu v register_sidebar	defect template	Notice: Funkce register_sidebar byla použita nesprávným způsobem. No id was set in the arguments array for the "Postranní panel 1" sidebar. Defaulting to "sidebar-1". Manually set the id to "sidebar-1" to silence this notice and keep existing sidebar content. Please see Debugging in WordPress for more information. (Tato zpráva se nově zobrazuje od verze 4.2.0.) in /var/www/virtual/dsw-oddil/web/www/wp-includes/functions.php on line 3560	1.0	Wordpress 4.2 hlásí chybu v register_sidebar - Notice: Funkce register_sidebar byla použita nesprávným způsobem. No id was set in the arguments array for the "Postranní panel 1" sidebar. Defaulting to "sidebar-1". Manually set the id to "sidebar-1" to silence this notice and keep existing sidebar content. Please see Debugging in WordPress for more information. (Tato zpráva se nově zobrazuje od verze 4.2.0.) in /var/www/virtual/dsw-oddil/web/www/wp-includes/functions.php on line 3560	non_priority	wordpress hlásí chybu v register sidebar notice funkce register sidebar byla použita nesprávným způsobem no id was set in the arguments array for the postranní panel sidebar defaulting to sidebar manually set the id to sidebar to silence this notice and keep existing sidebar content please see debugging in wordpress for more information tato zpráva se nově zobrazuje od verze in var www virtual dsw oddil web www wp includes functions php on line
224,893	24,795,408,670	IssuesEvent	2022-10-24 16:48:51	Jacksole/Learning-JavaScript	https://api.github.com/repos/Jacksole/Learning-JavaScript	closed	CVE-2021-23386 (Medium) detected in dns-packet-1.3.1.tgz - autoclosed	security vulnerability	## CVE-2021-23386 - Medium 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: /React/fullstack_app/client/package.json</p> <p>Path to vulnerable library: /React/fullstack_app/client/node_modules/dns-packet/package.json,/React/mern-todo-app/node_modules/dns-packet/package.json,/React/react-form-validation-demo/node_modules/dns-packet/package.json</p> <p> Dependency Hierarchy: - react-scripts-3.2.0.tgz (Root Library) - webpack-dev-server-3.2.1.tgz - bonjour-3.5.0.tgz - multicast-dns-6.2.3.tgz - :x: dns-packet-1.3.1.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/medium_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: May 20, 2021 5:15:00 PM <p>URL: <a href=https://www.mend.io/vulnerability-database/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>6.5</b>)</summary> <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: Low - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: High - Integrity Impact: None - Availability Impact: None </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary> <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://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: May 20, 2021 5:15:00 PM</p> <p>Fix Resolution (dns-packet): 1.3.2</p> <p>Direct dependency fix Resolution (react-scripts): 3.3.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-23386 (Medium) detected in dns-packet-1.3.1.tgz - autoclosed - ## CVE-2021-23386 - Medium 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: /React/fullstack_app/client/package.json</p> <p>Path to vulnerable library: /React/fullstack_app/client/node_modules/dns-packet/package.json,/React/mern-todo-app/node_modules/dns-packet/package.json,/React/react-form-validation-demo/node_modules/dns-packet/package.json</p> <p> Dependency Hierarchy: - react-scripts-3.2.0.tgz (Root Library) - webpack-dev-server-3.2.1.tgz - bonjour-3.5.0.tgz - multicast-dns-6.2.3.tgz - :x: dns-packet-1.3.1.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/medium_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: May 20, 2021 5:15:00 PM <p>URL: <a href=https://www.mend.io/vulnerability-database/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>6.5</b>)</summary> <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: Low - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: High - Integrity Impact: None - Availability Impact: None </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary> <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://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: May 20, 2021 5:15:00 PM</p> <p>Fix Resolution (dns-packet): 1.3.2</p> <p>Direct dependency fix Resolution (react-scripts): 3.3.0</p> </p> </details> <p></p> *** Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)	non_priority	cve medium detected in dns packet tgz autoclosed cve medium 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 react fullstack app client package json path to vulnerable library react fullstack app client node modules dns packet package json react mern todo app node modules dns packet package json react react form validation demo node modules dns packet package json dependency hierarchy react scripts tgz root library webpack dev server tgz bonjour tgz multicast dns tgz x dns packet tgz vulnerable library 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 may pm url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required low user interaction none scope unchanged impact metrics confidentiality impact high integrity impact none availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date may pm fix resolution dns packet direct dependency fix resolution react scripts step up your open source security game with mend
341,210	30,572,819,633	IssuesEvent	2023-07-21 00:51:00	warriordog/ActivityPubSharp	https://api.github.com/repos/warriordog/ActivityPubSharp	opened	Test DefaultValuesShould_BeStrippedFromOutput is failing	type:bug area:tests	It was always failing, but I made the test class `abstract` so it wasn't running. 🤦‍♀️🤦‍♀️🤦‍♀️🤦‍♀️🤦‍♀️🤦‍♀️🤦‍♀️ Need to find out if the problem is the test, or the code.	1.0	Test DefaultValuesShould_BeStrippedFromOutput is failing - It was always failing, but I made the test class `abstract` so it wasn't running. 🤦‍♀️🤦‍♀️🤦‍♀️🤦‍♀️🤦‍♀️🤦‍♀️🤦‍♀️ Need to find out if the problem is the test, or the code.	non_priority	test defaultvaluesshould bestrippedfromoutput is failing it was always failing but i made the test class abstract so it wasn t running 🤦‍♀️🤦‍♀️🤦‍♀️🤦‍♀️🤦‍♀️🤦‍♀️🤦‍♀️ need to find out if the problem is the test or the code
166,948	20,725,652,680	IssuesEvent	2022-03-14 01:18:59	akshat702/map-ionic	https://api.github.com/repos/akshat702/map-ionic	opened	CVE-2021-37701 (High) detected in tar-2.2.2.tgz, tar-2.2.1.tgz	security vulnerability	## CVE-2021-37701 - High Severity Vulnerability <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>tar-2.2.2.tgz</b>, <b>tar-2.2.1.tgz</b></p></summary> <p> <details><summary><b>tar-2.2.2.tgz</b></p></summary> <p>tar for node</p> <p>Library home page: <a href="https://registry.npmjs.org/tar/-/tar-2.2.2.tgz">https://registry.npmjs.org/tar/-/tar-2.2.2.tgz</a></p> <p>Path to dependency file: /Archive/plugins/cordova-plugin-ionic-webview/package.json</p> <p>Path to vulnerable library: /e2e/plugins/cordova-plugin-ionic-webview/node_modules/npm/node_modules/node-gyp/node_modules/tar/package.json,/e2e/plugins/cordova-plugin-ionic-webview/node_modules/npm/node_modules/node-gyp/node_modules/tar/package.json,/e2e/plugins/cordova-plugin-ionic-webview/node_modules/npm/node_modules/node-gyp/node_modules/tar/package.json,/e2e/plugins/cordova-plugin-ionic-webview/node_modules/npm/node_modules/node-gyp/node_modules/tar/package.json,/e2e/plugins/cordova-plugin-ionic-webview/node_modules/npm/node_modules/node-gyp/node_modules/tar/package.json</p> <p> Dependency Hierarchy: - npm-5.1.13.tgz (Root Library) - npm-6.10.0.tgz - node-gyp-3.8.0.tgz - :x: tar-2.2.2.tgz (Vulnerable Library) </details> <details><summary><b>tar-2.2.1.tgz</b></p></summary> <p>tar for node</p> <p>Library home page: <a href="https://registry.npmjs.org/tar/-/tar-2.2.1.tgz">https://registry.npmjs.org/tar/-/tar-2.2.1.tgz</a></p> <p>Path to dependency file: /dynamic/package.json</p> <p>Path to vulnerable library: /e2e/node_modules/tar/package.json,/e2e/node_modules/tar/package.json,/e2e/node_modules/tar/package.json,/e2e/node_modules/tar/package.json,/e2e/node_modules/tar/package.json</p> <p> Dependency Hierarchy: - build-angular-0.12.4.tgz (Root Library) - node-sass-4.10.0.tgz - node-gyp-3.8.0.tgz - :x: tar-2.2.1.tgz (Vulnerable Library) </details> </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 npm package "tar" (aka node-tar) before versions 4.4.16, 5.0.8, and 6.1.7 has an arbitrary file creation/overwrite and arbitrary code execution vulnerability. node-tar aims to guarantee that any file whose location would be modified by a symbolic link is not extracted. This is, in part, achieved by ensuring that extracted directories are not symlinks. Additionally, in order to prevent unnecessary stat calls to determine whether a given path is a directory, paths are cached when directories are created. This logic was insufficient when extracting tar files that contained both a directory and a symlink with the same name as the directory, where the symlink and directory names in the archive entry used backslashes as a path separator on posix systems. The cache checking logic used both `\` and `/` characters as path separators, however `\` is a valid filename character on posix systems. By first creating a directory, and then replacing that directory with a symlink, it was thus possible to bypass node-tar symlink checks on directories, essentially allowing an untrusted tar file to symlink into an arbitrary location and subsequently extracting arbitrary files into that location, thus allowing arbitrary file creation and overwrite. Additionally, a similar confusion could arise on case-insensitive filesystems. If a tar archive contained a directory at `FOO`, followed by a symbolic link named `foo`, then on case-insensitive file systems, the creation of the symbolic link would remove the directory from the filesystem, but _not_ from the internal directory cache, as it would not be treated as a cache hit. A subsequent file entry within the `FOO` directory would then be placed in the target of the symbolic link, thinking that the directory had already been created. These issues were addressed in releases 4.4.16, 5.0.8 and 6.1.7. The v3 branch of node-tar has been deprecated and did not receive patches for these issues. If you are still using a v3 release we recommend you update to a more recent version of node-tar. If this is not possible, a workaround is available in the referenced GHSA-9r2w-394v-53qc. <p>Publish Date: 2021-08-31 <p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-37701>CVE-2021-37701</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.6</b>)</summary> <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Local - Attack Complexity: Low - Privileges Required: None - User Interaction: Required - Scope: Changed - Impact Metrics: - Confidentiality Impact: High - Integrity Impact: High - Availability Impact: High </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary> <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://github.com/npm/node-tar/security/advisories/GHSA-9r2w-394v-53qc">https://github.com/npm/node-tar/security/advisories/GHSA-9r2w-394v-53qc</a></p> <p>Release Date: 2021-08-31</p> <p>Fix Resolution (tar): 4.4.16</p> <p>Direct dependency fix Resolution (@semantic-release/npm): 5.1.14</p><p>Fix Resolution (tar): 4.4.16</p> <p>Direct dependency fix Resolution (@angular-devkit/build-angular): 0.800.0-beta.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-2021-37701 (High) detected in tar-2.2.2.tgz, tar-2.2.1.tgz - ## CVE-2021-37701 - High Severity Vulnerability <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>tar-2.2.2.tgz</b>, <b>tar-2.2.1.tgz</b></p></summary> <p> <details><summary><b>tar-2.2.2.tgz</b></p></summary> <p>tar for node</p> <p>Library home page: <a href="https://registry.npmjs.org/tar/-/tar-2.2.2.tgz">https://registry.npmjs.org/tar/-/tar-2.2.2.tgz</a></p> <p>Path to dependency file: /Archive/plugins/cordova-plugin-ionic-webview/package.json</p> <p>Path to vulnerable library: /e2e/plugins/cordova-plugin-ionic-webview/node_modules/npm/node_modules/node-gyp/node_modules/tar/package.json,/e2e/plugins/cordova-plugin-ionic-webview/node_modules/npm/node_modules/node-gyp/node_modules/tar/package.json,/e2e/plugins/cordova-plugin-ionic-webview/node_modules/npm/node_modules/node-gyp/node_modules/tar/package.json,/e2e/plugins/cordova-plugin-ionic-webview/node_modules/npm/node_modules/node-gyp/node_modules/tar/package.json,/e2e/plugins/cordova-plugin-ionic-webview/node_modules/npm/node_modules/node-gyp/node_modules/tar/package.json</p> <p> Dependency Hierarchy: - npm-5.1.13.tgz (Root Library) - npm-6.10.0.tgz - node-gyp-3.8.0.tgz - :x: tar-2.2.2.tgz (Vulnerable Library) </details> <details><summary><b>tar-2.2.1.tgz</b></p></summary> <p>tar for node</p> <p>Library home page: <a href="https://registry.npmjs.org/tar/-/tar-2.2.1.tgz">https://registry.npmjs.org/tar/-/tar-2.2.1.tgz</a></p> <p>Path to dependency file: /dynamic/package.json</p> <p>Path to vulnerable library: /e2e/node_modules/tar/package.json,/e2e/node_modules/tar/package.json,/e2e/node_modules/tar/package.json,/e2e/node_modules/tar/package.json,/e2e/node_modules/tar/package.json</p> <p> Dependency Hierarchy: - build-angular-0.12.4.tgz (Root Library) - node-sass-4.10.0.tgz - node-gyp-3.8.0.tgz - :x: tar-2.2.1.tgz (Vulnerable Library) </details> </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 npm package "tar" (aka node-tar) before versions 4.4.16, 5.0.8, and 6.1.7 has an arbitrary file creation/overwrite and arbitrary code execution vulnerability. node-tar aims to guarantee that any file whose location would be modified by a symbolic link is not extracted. This is, in part, achieved by ensuring that extracted directories are not symlinks. Additionally, in order to prevent unnecessary stat calls to determine whether a given path is a directory, paths are cached when directories are created. This logic was insufficient when extracting tar files that contained both a directory and a symlink with the same name as the directory, where the symlink and directory names in the archive entry used backslashes as a path separator on posix systems. The cache checking logic used both `\` and `/` characters as path separators, however `\` is a valid filename character on posix systems. By first creating a directory, and then replacing that directory with a symlink, it was thus possible to bypass node-tar symlink checks on directories, essentially allowing an untrusted tar file to symlink into an arbitrary location and subsequently extracting arbitrary files into that location, thus allowing arbitrary file creation and overwrite. Additionally, a similar confusion could arise on case-insensitive filesystems. If a tar archive contained a directory at `FOO`, followed by a symbolic link named `foo`, then on case-insensitive file systems, the creation of the symbolic link would remove the directory from the filesystem, but _not_ from the internal directory cache, as it would not be treated as a cache hit. A subsequent file entry within the `FOO` directory would then be placed in the target of the symbolic link, thinking that the directory had already been created. These issues were addressed in releases 4.4.16, 5.0.8 and 6.1.7. The v3 branch of node-tar has been deprecated and did not receive patches for these issues. If you are still using a v3 release we recommend you update to a more recent version of node-tar. If this is not possible, a workaround is available in the referenced GHSA-9r2w-394v-53qc. <p>Publish Date: 2021-08-31 <p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-37701>CVE-2021-37701</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.6</b>)</summary> <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Local - Attack Complexity: Low - Privileges Required: None - User Interaction: Required - Scope: Changed - Impact Metrics: - Confidentiality Impact: High - Integrity Impact: High - Availability Impact: High </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary> <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://github.com/npm/node-tar/security/advisories/GHSA-9r2w-394v-53qc">https://github.com/npm/node-tar/security/advisories/GHSA-9r2w-394v-53qc</a></p> <p>Release Date: 2021-08-31</p> <p>Fix Resolution (tar): 4.4.16</p> <p>Direct dependency fix Resolution (@semantic-release/npm): 5.1.14</p><p>Fix Resolution (tar): 4.4.16</p> <p>Direct dependency fix Resolution (@angular-devkit/build-angular): 0.800.0-beta.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 tar tgz tar tgz cve high severity vulnerability vulnerable libraries tar tgz tar tgz tar tgz tar for node library home page a href path to dependency file archive plugins cordova plugin ionic webview package json path to vulnerable library plugins cordova plugin ionic webview node modules npm node modules node gyp node modules tar package json plugins cordova plugin ionic webview node modules npm node modules node gyp node modules tar package json plugins cordova plugin ionic webview node modules npm node modules node gyp node modules tar package json plugins cordova plugin ionic webview node modules npm node modules node gyp node modules tar package json plugins cordova plugin ionic webview node modules npm node modules node gyp node modules tar package json dependency hierarchy npm tgz root library npm tgz node gyp tgz x tar tgz vulnerable library tar tgz tar for node library home page a href path to dependency file dynamic package json path to vulnerable library node modules tar package json node modules tar package json node modules tar package json node modules tar package json node modules tar package json dependency hierarchy build angular tgz root library node sass tgz node gyp tgz x tar tgz vulnerable library vulnerability details the npm package tar aka node tar before versions and has an arbitrary file creation overwrite and arbitrary code execution vulnerability node tar aims to guarantee that any file whose location would be modified by a symbolic link is not extracted this is in part achieved by ensuring that extracted directories are not symlinks additionally in order to prevent unnecessary stat calls to determine whether a given path is a directory paths are cached when directories are created this logic was insufficient when extracting tar files that contained both a directory and a symlink with the same name as the directory where the symlink and directory names in the archive entry used backslashes as a path separator on posix systems the cache checking logic used both and characters as path separators however is a valid filename character on posix systems by first creating a directory and then replacing that directory with a symlink it was thus possible to bypass node tar symlink checks on directories essentially allowing an untrusted tar file to symlink into an arbitrary location and subsequently extracting arbitrary files into that location thus allowing arbitrary file creation and overwrite additionally a similar confusion could arise on case insensitive filesystems if a tar archive contained a directory at foo followed by a symbolic link named foo then on case insensitive file systems the creation of the symbolic link would remove the directory from the filesystem but not from the internal directory cache as it would not be treated as a cache hit a subsequent file entry within the foo directory would then be placed in the target of the symbolic link thinking that the directory had already been created these issues were addressed in releases and the branch of node tar has been deprecated and did not receive patches for these issues if you are still using a release we recommend you update to a more recent version of node tar if this is not possible a workaround is available in the referenced ghsa 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 changed impact metrics confidentiality impact high integrity impact high availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution tar direct dependency fix resolution semantic release npm fix resolution tar direct dependency fix resolution angular devkit build angular beta step up your open source security game with whitesource
125,318	12,257,152,529	IssuesEvent	2020-05-06 13:16:30	davidfrantz/force	https://api.github.com/repos/davidfrantz/force	closed	spectral indices formulars	documentation	Please provide the used formulars for the spectral indices: NDVI,EVI,NBR,ARVI,SAVI,SARVI,TC-BRIGHT,TC-GREEN,TC-WET,TC-DI,NDBI,NDWI,MNDWI,NDSI,SMA Perhaps I missed them in the docs? https://force-eo.readthedocs.io/en/latest/components/higher-level/tsa/param.html#parameterization	1.0	spectral indices formulars - Please provide the used formulars for the spectral indices: NDVI,EVI,NBR,ARVI,SAVI,SARVI,TC-BRIGHT,TC-GREEN,TC-WET,TC-DI,NDBI,NDWI,MNDWI,NDSI,SMA Perhaps I missed them in the docs? https://force-eo.readthedocs.io/en/latest/components/higher-level/tsa/param.html#parameterization	non_priority	spectral indices formulars please provide the used formulars for the spectral indices ndvi evi nbr arvi savi sarvi tc bright tc green tc wet tc di ndbi ndwi mndwi ndsi sma perhaps i missed them in the docs
332,440	24,343,124,468	IssuesEvent	2022-10-02 00:24:43	haqq-network/haqq	https://api.github.com/repos/haqq-network/haqq	closed	Evergreen DAO description doc	documentation Status: Stale	It is necessary to describe the device and mechanisms of operation of Evergreen DAO	1.0	Evergreen DAO description doc - It is necessary to describe the device and mechanisms of operation of Evergreen DAO	non_priority	evergreen dao description doc it is necessary to describe the device and mechanisms of operation of evergreen dao
194,968	14,697,955,891	IssuesEvent	2021-01-04 05:09:56	github-vet/rangeloop-pointer-findings	https://api.github.com/repos/github-vet/rangeloop-pointer-findings	closed	hello-mr-code/terraform-oci: oci/database_database_software_image_test.go; 16 LoC	fresh small test	Found a possible issue in [hello-mr-code/terraform-oci](https://www.github.com/hello-mr-code/terraform-oci) at [oci/database_database_software_image_test.go](https://github.com/hello-mr-code/terraform-oci/blob/2f6aa93ef8643328af454512a5fe78ab006697f0/oci/database_database_software_image_test.go#L335-L350) Below is the message reported by the analyzer for this snippet of code. Beware that the analyzer only reports the first issue it finds, so please do not limit your consideration to the contents of the below message. > reference to databaseSoftwareImageId is reassigned at line 339 [Click here to see the code in its original context.](https://github.com/hello-mr-code/terraform-oci/blob/2f6aa93ef8643328af454512a5fe78ab006697f0/oci/database_database_software_image_test.go#L335-L350) <details> <summary>Click here to show the 16 line(s) of Go which triggered the analyzer.</summary> ```go for _, databaseSoftwareImageId := range databaseSoftwareImageIds { if ok := SweeperDefaultResourceId[databaseSoftwareImageId]; !ok { deleteDatabaseSoftwareImageRequest := oci_database.DeleteDatabaseSoftwareImageRequest{} deleteDatabaseSoftwareImageRequest.DatabaseSoftwareImageId = &databaseSoftwareImageId deleteDatabaseSoftwareImageRequest.RequestMetadata.RetryPolicy = getRetryPolicy(true, "database") _, error := databaseClient.DeleteDatabaseSoftwareImage(context.Background(), deleteDatabaseSoftwareImageRequest) if error != nil { fmt.Printf("Error deleting DatabaseSoftwareImage %s %s, It is possible that the resource is already deleted. Please verify manually \n", databaseSoftwareImageId, error) continue } waitTillCondition(testAccProvider, &databaseSoftwareImageId, databaseSoftwareImageSweepWaitCondition, time.Duration(3time.Minute), databaseSoftwareImageSweepResponseFetchOperation, "database", true) } } ``` </details> Leave a reaction on this issue to contribute to the project by classifying this instance as a Bug* :-1:, Mitigated :+1:, or Desirable Behavior :rocket: See the descriptions of the classifications [here](https://github.com/github-vet/rangeclosure-findings#how-can-i-help) for more information. commit ID: 2f6aa93ef8643328af454512a5fe78ab006697f0	1.0	hello-mr-code/terraform-oci: oci/database_database_software_image_test.go; 16 LoC - Found a possible issue in [hello-mr-code/terraform-oci](https://www.github.com/hello-mr-code/terraform-oci) at [oci/database_database_software_image_test.go](https://github.com/hello-mr-code/terraform-oci/blob/2f6aa93ef8643328af454512a5fe78ab006697f0/oci/database_database_software_image_test.go#L335-L350) Below is the message reported by the analyzer for this snippet of code. Beware that the analyzer only reports the first issue it finds, so please do not limit your consideration to the contents of the below message. > reference to databaseSoftwareImageId is reassigned at line 339 [Click here to see the code in its original context.](https://github.com/hello-mr-code/terraform-oci/blob/2f6aa93ef8643328af454512a5fe78ab006697f0/oci/database_database_software_image_test.go#L335-L350) <details> <summary>Click here to show the 16 line(s) of Go which triggered the analyzer.</summary> ```go for _, databaseSoftwareImageId := range databaseSoftwareImageIds { if ok := SweeperDefaultResourceId[databaseSoftwareImageId]; !ok { deleteDatabaseSoftwareImageRequest := oci_database.DeleteDatabaseSoftwareImageRequest{} deleteDatabaseSoftwareImageRequest.DatabaseSoftwareImageId = &databaseSoftwareImageId deleteDatabaseSoftwareImageRequest.RequestMetadata.RetryPolicy = getRetryPolicy(true, "database") _, error := databaseClient.DeleteDatabaseSoftwareImage(context.Background(), deleteDatabaseSoftwareImageRequest) if error != nil { fmt.Printf("Error deleting DatabaseSoftwareImage %s %s, It is possible that the resource is already deleted. Please verify manually \n", databaseSoftwareImageId, error) continue } waitTillCondition(testAccProvider, &databaseSoftwareImageId, databaseSoftwareImageSweepWaitCondition, time.Duration(3time.Minute), databaseSoftwareImageSweepResponseFetchOperation, "database", true) } } ``` </details> Leave a reaction on this issue to contribute to the project by classifying this instance as a Bug* :-1:, Mitigated :+1:, or Desirable Behavior :rocket: See the descriptions of the classifications [here](https://github.com/github-vet/rangeclosure-findings#how-can-i-help) for more information. commit ID: 2f6aa93ef8643328af454512a5fe78ab006697f0	non_priority	hello mr code terraform oci oci database database software image test go loc found a possible issue in at below is the message reported by the analyzer for this snippet of code beware that the analyzer only reports the first issue it finds so please do not limit your consideration to the contents of the below message reference to databasesoftwareimageid is reassigned at line click here to show the line s of go which triggered the analyzer go for databasesoftwareimageid range databasesoftwareimageids if ok sweeperdefaultresourceid ok deletedatabasesoftwareimagerequest oci database deletedatabasesoftwareimagerequest deletedatabasesoftwareimagerequest databasesoftwareimageid databasesoftwareimageid deletedatabasesoftwareimagerequest requestmetadata retrypolicy getretrypolicy true database error databaseclient deletedatabasesoftwareimage context background deletedatabasesoftwareimagerequest if error nil fmt printf error deleting databasesoftwareimage s s it is possible that the resource is already deleted please verify manually n databasesoftwareimageid error continue waittillcondition testaccprovider databasesoftwareimageid databasesoftwareimagesweepwaitcondition time duration time minute databasesoftwareimagesweepresponsefetchoperation database true leave a reaction on this issue to contribute to the project by classifying this instance as a bug mitigated or desirable behavior rocket see the descriptions of the classifications for more information commit id
35,879	4,703,447,442	IssuesEvent	2016-10-13 08:02:25	pritsingh1701/android-stop-watch	https://api.github.com/repos/pritsingh1701/android-stop-watch	closed	As a Developer, I want to Create a Swipe Fragment Screen for app	App design	Who ? - Navdeep Singh What ? - Swipe Fragment Screen Why? - We need to swipe the screens Commnent :- any comments	1.0	As a Developer, I want to Create a Swipe Fragment Screen for app - Who ? - Navdeep Singh What ? - Swipe Fragment Screen Why? - We need to swipe the screens Commnent :- any comments	non_priority	as a developer i want to create a swipe fragment screen for app who navdeep singh what swipe fragment screen why we need to swipe the screens commnent any comments
342,965	24,762,812,934	IssuesEvent	2022-10-22 05:41:10	Chinmay-03/Hactoberfest-X-MIBCS-2022	https://api.github.com/repos/Chinmay-03/Hactoberfest-X-MIBCS-2022	closed	write what we do.md file for this repository	documentation good first issue hacktoberfest MIBCS	you should explore this repository to understand what it does and write a file name what_we_do.md to help a newbie, or first-time visitor more easily understand this repository and help it make more popular. Multiple people can be assigned and can collaborate	1.0	write what we do.md file for this repository - you should explore this repository to understand what it does and write a file name what_we_do.md to help a newbie, or first-time visitor more easily understand this repository and help it make more popular. Multiple people can be assigned and can collaborate	non_priority	write what we do md file for this repository you should explore this repository to understand what it does and write a file name what we do md to help a newbie or first time visitor more easily understand this repository and help it make more popular multiple people can be assigned and can collaborate
33,631	16,055,619,167	IssuesEvent	2021-04-23 04:14:47	cockroachdb/cockroach	https://api.github.com/repos/cockroachdb/cockroach	closed	storage: Wake ranges in background on node failure	A-kv-distribution C-performance X-stale	Throughput drops substantially after node failure, especially in low-concurrency clients. This is because each request that wakes a new range must block until it has gone through its raft election and lease acquisition. If instead of waking ranges up solely on user activity, we had a queue to wake up ranges in the background (ideally prioritized by how much traffic they've gotten recently), we could move this latency out of the user-visible path. We'd have to be careful not to overwhelm the cluster with this election traffic, though, and to ensure that waking up an idle range is done at a lower priority than user-facing traffic.	True	storage: Wake ranges in background on node failure - Throughput drops substantially after node failure, especially in low-concurrency clients. This is because each request that wakes a new range must block until it has gone through its raft election and lease acquisition. If instead of waking ranges up solely on user activity, we had a queue to wake up ranges in the background (ideally prioritized by how much traffic they've gotten recently), we could move this latency out of the user-visible path. We'd have to be careful not to overwhelm the cluster with this election traffic, though, and to ensure that waking up an idle range is done at a lower priority than user-facing traffic.	non_priority	storage wake ranges in background on node failure throughput drops substantially after node failure especially in low concurrency clients this is because each request that wakes a new range must block until it has gone through its raft election and lease acquisition if instead of waking ranges up solely on user activity we had a queue to wake up ranges in the background ideally prioritized by how much traffic they ve gotten recently we could move this latency out of the user visible path we d have to be careful not to overwhelm the cluster with this election traffic though and to ensure that waking up an idle range is done at a lower priority than user facing traffic
358,115	25,178,113,810	IssuesEvent	2022-11-11 11:06:48	microsoft/InnerEye-DeepLearning	https://api.github.com/repos/microsoft/InnerEye-DeepLearning	closed	Which paper is referenced in HeadAndNeckBase.py?	documentation	Hello In [HeadAndNeckBase.py](https://github.com/microsoft/InnerEye-DeepLearning/blob/main/InnerEye/ML/configs/segmentation/HeadAndNeckBase.py) the following is stated in a comment: "with the appropriate dataset, this would build the model whose results are reported in the InnerEye team’s paper". I assume you mean the follwing paper? [1] O. Oktay et al., “Evaluation of Deep Learning to Augment Image-Guided Radiotherapy for Head and Neck and Prostate Cancers,” JAMA Netw. Open, pp. 1–11, 2020, doi: 10.1001/jamanetworkopen.2020.27426. Thank you in advance. [AB#6005](https://innereye.visualstudio.com/60ce1777-00d6-4015-82bc-488a0c00202f/_workitems/edit/6005)	1.0	Which paper is referenced in HeadAndNeckBase.py? - Hello In [HeadAndNeckBase.py](https://github.com/microsoft/InnerEye-DeepLearning/blob/main/InnerEye/ML/configs/segmentation/HeadAndNeckBase.py) the following is stated in a comment: "with the appropriate dataset, this would build the model whose results are reported in the InnerEye team’s paper". I assume you mean the follwing paper? [1] O. Oktay et al., “Evaluation of Deep Learning to Augment Image-Guided Radiotherapy for Head and Neck and Prostate Cancers,” JAMA Netw. Open, pp. 1–11, 2020, doi: 10.1001/jamanetworkopen.2020.27426. Thank you in advance. [AB#6005](https://innereye.visualstudio.com/60ce1777-00d6-4015-82bc-488a0c00202f/_workitems/edit/6005)	non_priority	which paper is referenced in headandneckbase py hello in the following is stated in a comment with the appropriate dataset this would build the model whose results are reported in the innereye team’s paper i assume you mean the follwing paper o oktay et al “evaluation of deep learning to augment image guided radiotherapy for head and neck and prostate cancers ” jama netw open pp – doi jamanetworkopen thank you in advance
302,262	22,795,337,043	IssuesEvent	2022-07-10 16:26:48	HH9-Team11/FrontEnd	https://api.github.com/repos/HH9-Team11/FrontEnd	opened	회원가입 json data key 값 변경	documentation enhancement	기존 ``` { "username" : , “password” : , “dogName” : , “dogSize”:, “dogAge”:, “dogGender”:, “address“:, “lat” : 33.450701, “lng” : 126.570667 } ``` 변경후 ``` { "username" : , “password” : , “petName” : , “petSize” : , // 대형, 중형, 소형 “petAge” : , “petGender” : , “address“: , “lat” : 33.450701, “lng” : 126.570667 } ``` dog -> pet 으로 변경하였습니다. petSize도 대형, 중형, 소형으로 넘겨주시면 감사하겠습니다. 노션 api 명세도 수정해놓았습니다. 궁금하신 사항은 갠톡보내주세요	1.0	회원가입 json data key 값 변경 - 기존 ``` { "username" : , “password” : , “dogName” : , “dogSize”:, “dogAge”:, “dogGender”:, “address“:, “lat” : 33.450701, “lng” : 126.570667 } ``` 변경후 ``` { "username" : , “password” : , “petName” : , “petSize” : , // 대형, 중형, 소형 “petAge” : , “petGender” : , “address“: , “lat” : 33.450701, “lng” : 126.570667 } ``` dog -> pet 으로 변경하였습니다. petSize도 대형, 중형, 소형으로 넘겨주시면 감사하겠습니다. 노션 api 명세도 수정해놓았습니다. 궁금하신 사항은 갠톡보내주세요	non_priority	회원가입 json data key 값 변경 기존 username “password” “dogname” “dogsize” “dogage” “doggender” “address“ “lat” “lng” 변경후 username “password” “petname” “petsize” 대형 중형 소형 “petage” “petgender” “address“ “lat” “lng” dog pet 으로 변경하였습니다 petsize도 대형 중형 소형으로 넘겨주시면 감사하겠습니다 노션 api 명세도 수정해놓았습니다 궁금하신 사항은 갠톡보내주세요
38,071	15,495,621,059	IssuesEvent	2021-03-11 01:11:17	hashicorp/terraform-provider-aws	https://api.github.com/repos/hashicorp/terraform-provider-aws	closed	Destroy/recreate DB instance on minor version update rather than updating	enhancement service/rds	### Terraform Version Terraform v0.12.3 + provider.aws v2.16.0 + provider.template v2.1.2 ### Affected Resource(s) <!--- Please list the affected resources and data sources. ---> * aws_rds_cluster * aws_rds_cluster_instance ### Terraform Configuration Files ```hcl resource "aws_rds_cluster" "main_postgresql" { cluster_identifier = "aurora-cluster-main" deletion_protection = false availability_zones = ['us-east-1a', 'us-east-1b', 'us-east-1c'] database_name = "pcs" skip_final_snapshot = true backup_retention_period = 5 preferred_backup_window = "03:00-05:00" preferred_maintenance_window = "Mon:05:00-Mon:06:00" vpc_security_group_ids = [aws_security_group.main_postgresql.id] storage_encrypted = true # Careful, the below property need to be in sync between the cluster and the instances engine = "aurora-postgresql" engine_version = "10.7" db_subnet_group_name = aws_db_subnet_group.main.name master_username = "admin" master_password = "duMMY$123" apply_immediately = true } resource "aws_rds_cluster_instance" "main_postgresql_instances" { count = 2 identifier_prefix = "aurora-cluster-main-instance-" cluster_identifier = aws_rds_cluster.main_postgresql.id publicly_accessible = true instance_class = var.db_instance_type_per_env[terraform.workspace] auto_minor_version_upgrade = false # Careful, the below property need to be in sync between the cluster and the instances engine = local.engine engine_version = local.engine_version db_subnet_group_name = aws_db_subnet_group.main.name apply_immediately = true } ``` ### Debug Output https://gist.github.com/gbataille/9c7b6084614b1b6c022342c48dbb80f7 ### Expected Behavior DB cluster and DB instances are upgraded in place like if you did it through the AWS console. If you do it from the AWS console, the cluster and the instances are put in upgrading status, a dump is taken, pg_upgrade is run live, the instances are rebooted (~10s) and everything is back up. ### Actual Behavior Instances are destroyed and new ones with the new minor version are re-created --> it takes way longer --> the downtime is way longer. Luckily, since it's Aurora and the data layer is separate from the engine, no data was lost. ### Steps to Reproduce <!--- Please list the steps required to reproduce the issue. ---> 1. `terraform apply` with a RDS Aurora specifying postgresql 10.6 2. `terraform apply` with a RDS Aurora specifying postgresql 10.7	1.0	Destroy/recreate DB instance on minor version update rather than updating - ### Terraform Version Terraform v0.12.3 + provider.aws v2.16.0 + provider.template v2.1.2 ### Affected Resource(s) <!--- Please list the affected resources and data sources. ---> * aws_rds_cluster * aws_rds_cluster_instance ### Terraform Configuration Files ```hcl resource "aws_rds_cluster" "main_postgresql" { cluster_identifier = "aurora-cluster-main" deletion_protection = false availability_zones = ['us-east-1a', 'us-east-1b', 'us-east-1c'] database_name = "pcs" skip_final_snapshot = true backup_retention_period = 5 preferred_backup_window = "03:00-05:00" preferred_maintenance_window = "Mon:05:00-Mon:06:00" vpc_security_group_ids = [aws_security_group.main_postgresql.id] storage_encrypted = true # Careful, the below property need to be in sync between the cluster and the instances engine = "aurora-postgresql" engine_version = "10.7" db_subnet_group_name = aws_db_subnet_group.main.name master_username = "admin" master_password = "duMMY$123" apply_immediately = true } resource "aws_rds_cluster_instance" "main_postgresql_instances" { count = 2 identifier_prefix = "aurora-cluster-main-instance-" cluster_identifier = aws_rds_cluster.main_postgresql.id publicly_accessible = true instance_class = var.db_instance_type_per_env[terraform.workspace] auto_minor_version_upgrade = false # Careful, the below property need to be in sync between the cluster and the instances engine = local.engine engine_version = local.engine_version db_subnet_group_name = aws_db_subnet_group.main.name apply_immediately = true } ``` ### Debug Output https://gist.github.com/gbataille/9c7b6084614b1b6c022342c48dbb80f7 ### Expected Behavior DB cluster and DB instances are upgraded in place like if you did it through the AWS console. If you do it from the AWS console, the cluster and the instances are put in upgrading status, a dump is taken, pg_upgrade is run live, the instances are rebooted (~10s) and everything is back up. ### Actual Behavior Instances are destroyed and new ones with the new minor version are re-created --> it takes way longer --> the downtime is way longer. Luckily, since it's Aurora and the data layer is separate from the engine, no data was lost. ### Steps to Reproduce <!--- Please list the steps required to reproduce the issue. ---> 1. `terraform apply` with a RDS Aurora specifying postgresql 10.6 2. `terraform apply` with a RDS Aurora specifying postgresql 10.7	non_priority	destroy recreate db instance on minor version update rather than updating terraform version terraform provider aws provider template affected resource s aws rds cluster aws rds cluster instance terraform configuration files hcl resource aws rds cluster main postgresql cluster identifier aurora cluster main deletion protection false availability zones database name pcs skip final snapshot true backup retention period preferred backup window preferred maintenance window mon mon vpc security group ids storage encrypted true careful the below property need to be in sync between the cluster and the instances engine aurora postgresql engine version db subnet group name aws db subnet group main name master username admin master password dummy apply immediately true resource aws rds cluster instance main postgresql instances count identifier prefix aurora cluster main instance cluster identifier aws rds cluster main postgresql id publicly accessible true instance class var db instance type per env auto minor version upgrade false careful the below property need to be in sync between the cluster and the instances engine local engine engine version local engine version db subnet group name aws db subnet group main name apply immediately true debug output expected behavior db cluster and db instances are upgraded in place like if you did it through the aws console if you do it from the aws console the cluster and the instances are put in upgrading status a dump is taken pg upgrade is run live the instances are rebooted and everything is back up actual behavior instances are destroyed and new ones with the new minor version are re created it takes way longer the downtime is way longer luckily since it s aurora and the data layer is separate from the engine no data was lost steps to reproduce terraform apply with a rds aurora specifying postgresql terraform apply with a rds aurora specifying postgresql
333,050	24,360,786,240	IssuesEvent	2022-10-03 11:30:27	giovaninppc/AccessibilityHandbook	https://api.github.com/repos/giovaninppc/AccessibilityHandbook	opened	Add discussion about identifying the preferred font size	documentation enhancement	The font sizes vary from extra small to extra extra extra large, then, with the accessibility feature enabled, it varies from accessibility medium to accessibility extra extra extra large. I think it would be nice to add a discussion about this on the app, so developers can properly understand what it means and possibly handle it manually if they want.	1.0	Add discussion about identifying the preferred font size - The font sizes vary from extra small to extra extra extra large, then, with the accessibility feature enabled, it varies from accessibility medium to accessibility extra extra extra large. I think it would be nice to add a discussion about this on the app, so developers can properly understand what it means and possibly handle it manually if they want.	non_priority	add discussion about identifying the preferred font size the font sizes vary from extra small to extra extra extra large then with the accessibility feature enabled it varies from accessibility medium to accessibility extra extra extra large i think it would be nice to add a discussion about this on the app so developers can properly understand what it means and possibly handle it manually if they want
132,943	18,785,315,674	IssuesEvent	2021-11-08 11:29:04	navikt/nav-dekoratoren	https://api.github.com/repos/navikt/nav-dekoratoren	opened	Se på plassering av "Del skjerm med veileder" i footer	design	Tilbakemelding fra NKS: ![image](https://user-images.githubusercontent.com/47320658/140734240-eb55f85b-6da5-4eab-ae9a-afa8163862ba.png) Fremmedspråklige sliter med å finne navigere til "Del skjerm med veileder" i footer. Vi må se på hvordan vi kan gjøre det enklere for denne brukergruppen å finne knappen.	1.0	Se på plassering av "Del skjerm med veileder" i footer - Tilbakemelding fra NKS: ![image](https://user-images.githubusercontent.com/47320658/140734240-eb55f85b-6da5-4eab-ae9a-afa8163862ba.png) Fremmedspråklige sliter med å finne navigere til "Del skjerm med veileder" i footer. Vi må se på hvordan vi kan gjøre det enklere for denne brukergruppen å finne knappen.	non_priority	se på plassering av del skjerm med veileder i footer tilbakemelding fra nks fremmedspråklige sliter med å finne navigere til del skjerm med veileder i footer vi må se på hvordan vi kan gjøre det enklere for denne brukergruppen å finne knappen
81,231	15,606,955,833	IssuesEvent	2021-03-19 08:46:01	tyutyutyu/sample-app	https://api.github.com/repos/tyutyutyu/sample-app	closed	CVE-2020-10693 (Medium) detected in hibernate-validator-6.0.18.Final.jar - autoclosed	security vulnerability	## CVE-2020-10693 - Medium Severity Vulnerability <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>hibernate-validator-6.0.18.Final.jar</b></p></summary> <p>Hibernate's Bean Validation (JSR-380) reference implementation.</p> <p>Library home page: <a href="http://hibernate.org/validator">http://hibernate.org/validator</a></p> <p>Path to dependency file: sample-app/pom.xml</p> <p>Path to vulnerable library: /home/wss-scanner/.m2/repository/org/hibernate/validator/hibernate-validator/6.0.18.Final/hibernate-validator-6.0.18.Final.jar</p> <p> Dependency Hierarchy: - spring-boot-starter-web-2.2.2.RELEASE.jar (Root Library) - spring-boot-starter-validation-2.2.2.RELEASE.jar - :x: hibernate-validator-6.0.18.Final.jar (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/tyutyutyu/sample-app/commit/8c2a9148b6372b4bd502e52c727da38c2cb63e54">8c2a9148b6372b4bd502e52c727da38c2cb63e54</a></p> <p>Found in base branch: <b>master</b></p> </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary> <p> A flaw was found in Hibernate Validator version 6.1.2.Final. A bug in the message interpolation processor enables invalid EL expressions to be evaluated as if they were valid. This flaw allows attackers to bypass input sanitation (escaping, stripping) controls that developers may have put in place when handling user-controlled data in error messages. <p>Publish Date: 2020-05-06 <p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-10693>CVE-2020-10693</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://hibernate.atlassian.net/projects/HV/issues/HV-1774">https://hibernate.atlassian.net/projects/HV/issues/HV-1774</a></p> <p>Release Date: 2020-05-06</p> <p>Fix Resolution: org.hibernate.validator:hibernate-validator:6.0.20.Final,org.hibernate.validator:hibernate-validator:6.1.5.Final,org.hibernate.validator:hibernate-validator:7.0.0.Alpha2</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-10693 (Medium) detected in hibernate-validator-6.0.18.Final.jar - autoclosed - ## CVE-2020-10693 - Medium Severity Vulnerability <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>hibernate-validator-6.0.18.Final.jar</b></p></summary> <p>Hibernate's Bean Validation (JSR-380) reference implementation.</p> <p>Library home page: <a href="http://hibernate.org/validator">http://hibernate.org/validator</a></p> <p>Path to dependency file: sample-app/pom.xml</p> <p>Path to vulnerable library: /home/wss-scanner/.m2/repository/org/hibernate/validator/hibernate-validator/6.0.18.Final/hibernate-validator-6.0.18.Final.jar</p> <p> Dependency Hierarchy: - spring-boot-starter-web-2.2.2.RELEASE.jar (Root Library) - spring-boot-starter-validation-2.2.2.RELEASE.jar - :x: hibernate-validator-6.0.18.Final.jar (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/tyutyutyu/sample-app/commit/8c2a9148b6372b4bd502e52c727da38c2cb63e54">8c2a9148b6372b4bd502e52c727da38c2cb63e54</a></p> <p>Found in base branch: <b>master</b></p> </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary> <p> A flaw was found in Hibernate Validator version 6.1.2.Final. A bug in the message interpolation processor enables invalid EL expressions to be evaluated as if they were valid. This flaw allows attackers to bypass input sanitation (escaping, stripping) controls that developers may have put in place when handling user-controlled data in error messages. <p>Publish Date: 2020-05-06 <p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-10693>CVE-2020-10693</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://hibernate.atlassian.net/projects/HV/issues/HV-1774">https://hibernate.atlassian.net/projects/HV/issues/HV-1774</a></p> <p>Release Date: 2020-05-06</p> <p>Fix Resolution: org.hibernate.validator:hibernate-validator:6.0.20.Final,org.hibernate.validator:hibernate-validator:6.1.5.Final,org.hibernate.validator:hibernate-validator:7.0.0.Alpha2</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 hibernate validator final jar autoclosed cve medium severity vulnerability vulnerable library hibernate validator final jar hibernate s bean validation jsr reference implementation library home page a href path to dependency file sample app pom xml path to vulnerable library home wss scanner repository org hibernate validator hibernate validator final hibernate validator final jar dependency hierarchy spring boot starter web release jar root library spring boot starter validation release jar x hibernate validator final jar vulnerable library found in head commit a href found in base branch master vulnerability details a flaw was found in hibernate validator version final a bug in the message interpolation processor enables invalid el expressions to be evaluated as if they were valid this flaw allows attackers to bypass input sanitation escaping stripping controls that developers may have put in place when handling user controlled data in error messages 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 org hibernate validator hibernate validator final org hibernate validator hibernate validator final org hibernate validator hibernate validator step up your open source security game with whitesource
148,536	23,358,185,607	IssuesEvent	2022-08-10 09:17:54	LearningChain/FrontEnd	https://api.github.com/repos/LearningChain/FrontEnd	closed	feat : Avatar 컴포넌트 제작	✨ FEAT 🎨 DESIGN	### 설명 아바타 컴포넌트를 제작합니다. ### 세부 기능 요구사항 - [ ] 컴포넌트 작성 - [ ] 스토리북 작성 ### 주의사항	1.0	feat : Avatar 컴포넌트 제작 - ### 설명 아바타 컴포넌트를 제작합니다. ### 세부 기능 요구사항 - [ ] 컴포넌트 작성 - [ ] 스토리북 작성 ### 주의사항	non_priority	feat avatar 컴포넌트 제작 설명 아바타 컴포넌트를 제작합니다 세부 기능 요구사항 컴포넌트 작성 스토리북 작성 주의사항
165,483	14,003,311,332	IssuesEvent	2020-10-28 15:45:13	FLAMEGPU/FLAMEGPU2_dev	https://api.github.com/repos/FLAMEGPU/FLAMEGPU2_dev	closed	Order of exitCondition functions.	Documentation enhancement	Exit conditions are not executed in the order they are added to the model. This is unintuivite (although not sure why anyone would actually have two which are order dependent..., i'm abusing it for testing purposes) This should be well documented or changed to preserve order of adding to the model. i.e. ``` FLAMEGPU_EXIT_CONDITION(exitCondition_a) { printf("a\n"); return CONTINUE; } FLAMEGPU_EXIT_CONDITION(exitCondition_b) { printf("b\n"); return CONTINUE; } // ... model.addExitCondition(exitCondition_b); model.addExitCondition(exitCondition_a); // ... ``` will produce ``` a b ``` I.e. it appears to be order of definition, not order of adding to the model. Edit it does not appear to always be order of deinition either: ``` FLAMEGPU_EXIT_CONDITION(exitCondition_testGetStepCounter) { printf("a\n"); return CONTINUE; } FLAMEGPU_EXIT_CONDITION(exitCondition_increase_expectStepCounter) { printf("b\n"); return CONTINUE } // ... model.addExitCondition(exitCondition_testGetStepCounter); model.addExitCondition(exitCondition_increase_expectStepCounter); // ... ``` ``` b a ``` Edit: Currently, regular exit conditions are called prior to any python(maybe RTC?) exit conditions, which would also warrent documentation.	1.0	Order of exitCondition functions. - Exit conditions are not executed in the order they are added to the model. This is unintuivite (although not sure why anyone would actually have two which are order dependent..., i'm abusing it for testing purposes) This should be well documented or changed to preserve order of adding to the model. i.e. ``` FLAMEGPU_EXIT_CONDITION(exitCondition_a) { printf("a\n"); return CONTINUE; } FLAMEGPU_EXIT_CONDITION(exitCondition_b) { printf("b\n"); return CONTINUE; } // ... model.addExitCondition(exitCondition_b); model.addExitCondition(exitCondition_a); // ... ``` will produce ``` a b ``` I.e. it appears to be order of definition, not order of adding to the model. Edit it does not appear to always be order of deinition either: ``` FLAMEGPU_EXIT_CONDITION(exitCondition_testGetStepCounter) { printf("a\n"); return CONTINUE; } FLAMEGPU_EXIT_CONDITION(exitCondition_increase_expectStepCounter) { printf("b\n"); return CONTINUE } // ... model.addExitCondition(exitCondition_testGetStepCounter); model.addExitCondition(exitCondition_increase_expectStepCounter); // ... ``` ``` b a ``` Edit: Currently, regular exit conditions are called prior to any python(maybe RTC?) exit conditions, which would also warrent documentation.	non_priority	order of exitcondition functions exit conditions are not executed in the order they are added to the model this is unintuivite although not sure why anyone would actually have two which are order dependent i m abusing it for testing purposes this should be well documented or changed to preserve order of adding to the model i e flamegpu exit condition exitcondition a printf a n return continue flamegpu exit condition exitcondition b printf b n return continue model addexitcondition exitcondition b model addexitcondition exitcondition a will produce a b i e it appears to be order of definition not order of adding to the model edit it does not appear to always be order of deinition either flamegpu exit condition exitcondition testgetstepcounter printf a n return continue flamegpu exit condition exitcondition increase expectstepcounter printf b n return continue model addexitcondition exitcondition testgetstepcounter model addexitcondition exitcondition increase expectstepcounter b a edit currently regular exit conditions are called prior to any python maybe rtc exit conditions which would also warrent documentation
32,773	4,416,954,134	IssuesEvent	2016-08-15 00:39:23	chihacknight/join-a-breakout	https://api.github.com/repos/chihacknight/join-a-breakout	reopened	Chicago Nursing Home Search	Dev UX Design Working group	About the group The main goal of this project is to create a tool to help people and their families choose the best long term care option available. Another goal to is to make the residents of Chicago and surrounding areas aware of the differences in nursing home quality and to advocate for improvements. [chicagonursinghomesearch.com](url) Group leaders Joel Inwood, ziegegeist@gmail.com Who we're looking for Anyone who wants to give us design or usability feedback is welcome. We also need folks who can help out or offer advice on making a database. Where we meet Either in one of the free rooms or in the main audience area	1.0	Chicago Nursing Home Search - About the group The main goal of this project is to create a tool to help people and their families choose the best long term care option available. Another goal to is to make the residents of Chicago and surrounding areas aware of the differences in nursing home quality and to advocate for improvements. [chicagonursinghomesearch.com](url) Group leaders Joel Inwood, ziegegeist@gmail.com Who we're looking for Anyone who wants to give us design or usability feedback is welcome. We also need folks who can help out or offer advice on making a database. Where we meet Either in one of the free rooms or in the main audience area	non_priority	chicago nursing home search about the group the main goal of this project is to create a tool to help people and their families choose the best long term care option available another goal to is to make the residents of chicago and surrounding areas aware of the differences in nursing home quality and to advocate for improvements url group leaders joel inwood ziegegeist gmail com who we re looking for anyone who wants to give us design or usability feedback is welcome we also need folks who can help out or offer advice on making a database where we meet either in one of the free rooms or in the main audience area
13,781	3,357,240,784	IssuesEvent	2015-11-19 00:12:21	bokeh/bokeh	https://api.github.com/repos/bokeh/bokeh	closed	Remove logic from Bokeh server endpoints	reso: invalid tag: server tag: tests type: task	Should be factored into functions that the the endpoint delegates to to help with testing.	1.0	Remove logic from Bokeh server endpoints - Should be factored into functions that the the endpoint delegates to to help with testing.	non_priority	remove logic from bokeh server endpoints should be factored into functions that the the endpoint delegates to to help with testing
32,653	12,140,809,930	IssuesEvent	2020-04-23 21:11:19	ioet/time-tracker-backend	https://api.github.com/repos/ioet/time-tracker-backend	closed	The endpoint to get the running time entry is not getting the right one	bug security	The endpoint to get the running time entry needs to get the time entry corresponding to the authenticated user. In addition, verify that in the update/create of the time entries the restriction related to verify that the start date is before the end date is properly working.	True	The endpoint to get the running time entry is not getting the right one - The endpoint to get the running time entry needs to get the time entry corresponding to the authenticated user. In addition, verify that in the update/create of the time entries the restriction related to verify that the start date is before the end date is properly working.	non_priority	the endpoint to get the running time entry is not getting the right one the endpoint to get the running time entry needs to get the time entry corresponding to the authenticated user in addition verify that in the update create of the time entries the restriction related to verify that the start date is before the end date is properly working
69,354	8,394,998,281	IssuesEvent	2018-10-10 03:52:47	gitcoinco/web	https://api.github.com/repos/gitcoinco/web	closed	as a user, i want gitcoin.co/inbox, so i can manage my notifications (and action items)	Needs Technical Review needs design to bounty	<!-- Hello Gitcoiner! Please use the template below for issue ideas or bugs found within Gitcoin. If it is general support you need, reach out to us at gitcoin.co/slack Provide a general summary of the issue in the title above and use relevant fields below to define the problem. --> ### User Story [comment]: # (As a <user type>, I want to <task> so that <goal>.) as a user, i want gitcoin.co/inbox (or gitcoin.co/notifications), so i can manage my notifications ### Why Is this Needed its easy to lose track of your notifications [comment]: # (Describe the problem and why this task is needed. Provide description of the current state, what you would like to happen, and what actually happen) Summary: ### Description [comment]: # (Feature or Bug? i.e Type: Bug) Type: Feature ### Current Behavior [comment]: # (Describe what actually happened.) No inbox ### Expected Behavior [comment]: # (Describe what you expected to happen.) Inbox ### Definition of Done [comment]: # (Any other information that would be useful, bullets are helpful.) User can go to gitcoin.co/inbox and see a list of notifications. * notifications can be selected or unselected. there will be 'select all' or 'deselect all' buttons on the top, and there will also be 'mark selected as read', 'delete selected' and 'mark selected all as unread' buttons' * notifications will be sorted chronologically and paginated * notifications can be marked as read, marked as unread, or deleted * each notification has a 'go' button next to it which will allow the user to process the notification (whatever action is associated with it).. when a user clicks 'go' the notification will be marked as read. This page will be linked in the top right nav, under my user profile. Notifications will be generated each time a user needs to take action upon something (approve worker, disapprove worker, accept worker, receive tip, etc) Suggested model for notifications * pk * created_on * is_read (default = false) * deleted (default = false) * copy * action url	1.0	as a user, i want gitcoin.co/inbox, so i can manage my notifications (and action items) - <!-- Hello Gitcoiner! Please use the template below for issue ideas or bugs found within Gitcoin. If it is general support you need, reach out to us at gitcoin.co/slack Provide a general summary of the issue in the title above and use relevant fields below to define the problem. --> ### User Story [comment]: # (As a <user type>, I want to <task> so that <goal>.) as a user, i want gitcoin.co/inbox (or gitcoin.co/notifications), so i can manage my notifications ### Why Is this Needed its easy to lose track of your notifications [comment]: # (Describe the problem and why this task is needed. Provide description of the current state, what you would like to happen, and what actually happen) Summary: ### Description [comment]: # (Feature or Bug? i.e Type: Bug) Type: Feature ### Current Behavior [comment]: # (Describe what actually happened.) No inbox ### Expected Behavior [comment]: # (Describe what you expected to happen.) Inbox ### Definition of Done [comment]: # (Any other information that would be useful, bullets are helpful.) User can go to gitcoin.co/inbox and see a list of notifications. * notifications can be selected or unselected. there will be 'select all' or 'deselect all' buttons on the top, and there will also be 'mark selected as read', 'delete selected' and 'mark selected all as unread' buttons' * notifications will be sorted chronologically and paginated * notifications can be marked as read, marked as unread, or deleted * each notification has a 'go' button next to it which will allow the user to process the notification (whatever action is associated with it).. when a user clicks 'go' the notification will be marked as read. This page will be linked in the top right nav, under my user profile. Notifications will be generated each time a user needs to take action upon something (approve worker, disapprove worker, accept worker, receive tip, etc) Suggested model for notifications * pk * created_on * is_read (default = false) * deleted (default = false) * copy * action url	non_priority	as a user i want gitcoin co inbox so i can manage my notifications and action items hello gitcoiner please use the template below for issue ideas or bugs found within gitcoin if it is general support you need reach out to us at gitcoin co slack provide a general summary of the issue in the title above and use relevant fields below to define the problem user story as a i want to so that as a user i want gitcoin co inbox or gitcoin co notifications so i can manage my notifications why is this needed its easy to lose track of your notifications describe the problem and why this task is needed provide description of the current state what you would like to happen and what actually happen summary description feature or bug i e type bug type feature current behavior describe what actually happened no inbox expected behavior describe what you expected to happen inbox definition of done any other information that would be useful bullets are helpful user can go to gitcoin co inbox and see a list of notifications notifications can be selected or unselected there will be select all or deselect all buttons on the top and there will also be mark selected as read delete selected and mark selected all as unread buttons notifications will be sorted chronologically and paginated notifications can be marked as read marked as unread or deleted each notification has a go button next to it which will allow the user to process the notification whatever action is associated with it when a user clicks go the notification will be marked as read this page will be linked in the top right nav under my user profile notifications will be generated each time a user needs to take action upon something approve worker disapprove worker accept worker receive tip etc suggested model for notifications pk created on is read default false deleted default false copy action url
20,225	13,767,081,125	IssuesEvent	2020-10-07 15:18:24	esrlabs/northstar	https://api.github.com/repos/esrlabs/northstar	closed	Remove ext4 support	good first issue infrastructure linux	ext4 is not used anymore and code to support it should be removed both from - north - tooling	1.0	Remove ext4 support - ext4 is not used anymore and code to support it should be removed both from - north - tooling	non_priority	remove support is not used anymore and code to support it should be removed both from north tooling
51,406	27,059,589,935	IssuesEvent	2023-02-13 18:39:19	matrix-org/dendrite	https://api.github.com/repos/matrix-org/dendrite	closed	/sync performance slow since v0.10.0	C-Sync-API T-Task X-Performance	<!-- All bug reports must provide the following background information Text between <!-- and --> marks will be invisible in the report. --> ### Background information <!-- Please include versions of all software when known e.g database versions, docker versions, client versions --> - v0.10.1 - Monolith - Postgres - Running in Docker ### Description I'm running Dendrite in Docker and noticed a huge difference in performance when doing initial sync when switching from v0.9.9 to v0.10.0 or v0.10.1 Response times in my server: With docker image matrixdotorg/dendrite-monolith:v0.9.9 ``` # With existing filter $ curl -o /dev/null -s -w 'Total: %{time_total}s\n' 'https://[my-domain]/_matrix/client/r0/sync?filter=7&timeout=0&_cacheBuster=1665145519640&access_token=[redacted]' Total: 1,113253s # With inline filter $ curl -o /dev/null -s -w 'Total: %{time_total}s\n' 'https://[my-domain]/_matrix/client/r0/sync?filter=%7B%22room%22%3A%7B%22timeline%22%3A%7B%22limit%22%3A100%7D%7D%7D&timeout=0&access_token=[redacted]' Total: 6,983575s ``` With docker image matrixdotorg/dendrite-monolith:v0.10.1 ``` # With existing filter $ curl -o /dev/null -s -w 'Total: %{time_total}s\n' 'https://[my-domain]/_matrix/client/r0/sync?filter=7&timeout=0&_cacheBuster=1665145519640&access_token=[redacted]' Total: 5,740234s # With inline filter $ curl -o /dev/null -s -w 'Total: %{time_total}s\n' 'https://[my-domain]/_matrix/client/r0/sync?filter=%7B%22room%22%3A%7B%22timeline%22%3A%7B%22limit%22%3A100%7D%7D%7D&timeout=0&access_token=[redacted]' Total: 15,450809s ```	True	/sync performance slow since v0.10.0 - <!-- All bug reports must provide the following background information Text between <!-- and --> marks will be invisible in the report. --> ### Background information <!-- Please include versions of all software when known e.g database versions, docker versions, client versions --> - v0.10.1 - Monolith - Postgres - Running in Docker ### Description I'm running Dendrite in Docker and noticed a huge difference in performance when doing initial sync when switching from v0.9.9 to v0.10.0 or v0.10.1 Response times in my server: With docker image matrixdotorg/dendrite-monolith:v0.9.9 ``` # With existing filter $ curl -o /dev/null -s -w 'Total: %{time_total}s\n' 'https://[my-domain]/_matrix/client/r0/sync?filter=7&timeout=0&_cacheBuster=1665145519640&access_token=[redacted]' Total: 1,113253s # With inline filter $ curl -o /dev/null -s -w 'Total: %{time_total}s\n' 'https://[my-domain]/_matrix/client/r0/sync?filter=%7B%22room%22%3A%7B%22timeline%22%3A%7B%22limit%22%3A100%7D%7D%7D&timeout=0&access_token=[redacted]' Total: 6,983575s ``` With docker image matrixdotorg/dendrite-monolith:v0.10.1 ``` # With existing filter $ curl -o /dev/null -s -w 'Total: %{time_total}s\n' 'https://[my-domain]/_matrix/client/r0/sync?filter=7&timeout=0&_cacheBuster=1665145519640&access_token=[redacted]' Total: 5,740234s # With inline filter $ curl -o /dev/null -s -w 'Total: %{time_total}s\n' 'https://[my-domain]/_matrix/client/r0/sync?filter=%7B%22room%22%3A%7B%22timeline%22%3A%7B%22limit%22%3A100%7D%7D%7D&timeout=0&access_token=[redacted]' Total: 15,450809s ```	non_priority	sync performance slow since all bug reports must provide the following background information text between marks will be invisible in the report background information monolith postgres running in docker description i m running dendrite in docker and noticed a huge difference in performance when doing initial sync when switching from to or response times in my server with docker image matrixdotorg dendrite monolith with existing filter curl o dev null s w total time total s n https matrix client sync filter timeout cachebuster access token total with inline filter curl o dev null s w total time total s n https matrix client sync filter timeout access token total with docker image matrixdotorg dendrite monolith with existing filter curl o dev null s w total time total s n https matrix client sync filter timeout cachebuster access token total with inline filter curl o dev null s w total time total s n https matrix client sync filter timeout access token total
9,624	11,699,862,895	IssuesEvent	2020-03-06 16:23:20	ClickHouse/ClickHouse	https://api.github.com/repos/ClickHouse/ClickHouse	closed	Backward compativility issue client 20.2 ->server 20.3	backward compatibility bug st-wontfix	hit it by accident (updated server, and did type query in old client session) i think on client-side `send_logs_level` was enabled. ``` Ubuntu-1804-bionic-64-minimal :) select 1; SELECT 1 Exception on client: Code: 10. DB::Exception: Not found column thread_number in block. There are only columns: event_time, event_time_microseconds, host_name, query_id, thread_id, priority, source, text Connecting to localhost:9000 as user default. Connected to ClickHouse server version 20.3.1 revision 54433. ClickHouse client version is older than ClickHouse server. It may lack support for new features. Ubuntu-1804-bionic-64-minimal :) show processlist; -- the same ```	True	Backward compativility issue client 20.2 ->server 20.3 - hit it by accident (updated server, and did type query in old client session) i think on client-side `send_logs_level` was enabled. ``` Ubuntu-1804-bionic-64-minimal :) select 1; SELECT 1 Exception on client: Code: 10. DB::Exception: Not found column thread_number in block. There are only columns: event_time, event_time_microseconds, host_name, query_id, thread_id, priority, source, text Connecting to localhost:9000 as user default. Connected to ClickHouse server version 20.3.1 revision 54433. ClickHouse client version is older than ClickHouse server. It may lack support for new features. Ubuntu-1804-bionic-64-minimal :) show processlist; -- the same ```	non_priority	backward compativility issue client server hit it by accident updated server and did type query in old client session i think on client side send logs level was enabled ubuntu bionic minimal select select exception on client code db exception not found column thread number in block there are only columns event time event time microseconds host name query id thread id priority source text connecting to localhost as user default connected to clickhouse server version revision clickhouse client version is older than clickhouse server it may lack support for new features ubuntu bionic minimal show processlist the same
140,928	18,927,864,554	IssuesEvent	2021-11-17 11:28:14	sultanabubaker/Rem_Ren_Maven_Test	https://api.github.com/repos/sultanabubaker/Rem_Ren_Maven_Test	opened	CVE-2020-15250 (Medium) detected in junit-4.12.jar	security vulnerability	## CVE-2020-15250 - Medium Severity Vulnerability <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>junit-4.12.jar</b></p></summary> <p>JUnit is a unit testing framework for Java, created by Erich Gamma and Kent Beck.</p> <p>Library home page: <a href="http://junit.org">http://junit.org</a></p> <p>Path to dependency file: Rem_Ren_Maven_Test/pom.xml</p> <p>Path to vulnerable library: ry/junit/junit/4.12/junit-4.12.jar</p> <p> Dependency Hierarchy: - :x: junit-4.12.jar (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/sultanabubaker/Rem_Ren_Maven_Test/commit/be48940f6d2bd6a994a73f5d4fdb75cc2abdc7fc">be48940f6d2bd6a994a73f5d4fdb75cc2abdc7fc</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> In JUnit4 from version 4.7 and before 4.13.1, the test rule TemporaryFolder contains a local information disclosure vulnerability. On Unix like systems, the system's temporary directory is shared between all users on that system. Because of this, when files and directories are written into this directory they are, by default, readable by other users on that same system. This vulnerability does not allow other users to overwrite the contents of these directories or files. This is purely an information disclosure vulnerability. This vulnerability impacts you if the JUnit tests write sensitive information, like API keys or passwords, into the temporary folder, and the JUnit tests execute in an environment where the OS has other untrusted users. Because certain JDK file system APIs were only added in JDK 1.7, this this fix is dependent upon the version of the JDK you are using. For Java 1.7 and higher users: this vulnerability is fixed in 4.13.1. For Java 1.6 and lower users: no patch is available, you must use the workaround below. If you are unable to patch, or are stuck running on Java 1.6, specifying the `java.io.tmpdir` system environment variable to a directory that is exclusively owned by the executing user will fix this vulnerability. For more information, including an example of vulnerable code, see the referenced GitHub Security Advisory. <p>Publish Date: 2020-10-12 <p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-15250>CVE-2020-15250</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: High - Integrity Impact: None - Availability Impact: None </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary> <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://github.com/junit-team/junit4/security/advisories/GHSA-269g-pwp5-87pp">https://github.com/junit-team/junit4/security/advisories/GHSA-269g-pwp5-87pp</a></p> <p>Release Date: 2020-10-12</p> <p>Fix Resolution: junit:junit:4.13.1</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":"junit","packageName":"junit","packageVersion":"4.12","packageFilePaths":["/pom.xml"],"isTransitiveDependency":false,"dependencyTree":"junit:junit:4.12","isMinimumFixVersionAvailable":true,"minimumFixVersion":"junit:junit:4.13.1"}],"baseBranches":["main"],"vulnerabilityIdentifier":"CVE-2020-15250","vulnerabilityDetails":"In JUnit4 from version 4.7 and before 4.13.1, the test rule TemporaryFolder contains a local information disclosure vulnerability. On Unix like systems, the system\u0027s temporary directory is shared between all users on that system. Because of this, when files and directories are written into this directory they are, by default, readable by other users on that same system. This vulnerability does not allow other users to overwrite the contents of these directories or files. This is purely an information disclosure vulnerability. This vulnerability impacts you if the JUnit tests write sensitive information, like API keys or passwords, into the temporary folder, and the JUnit tests execute in an environment where the OS has other untrusted users. Because certain JDK file system APIs were only added in JDK 1.7, this this fix is dependent upon the version of the JDK you are using. For Java 1.7 and higher users: this vulnerability is fixed in 4.13.1. For Java 1.6 and lower users: no patch is available, you must use the workaround below. If you are unable to patch, or are stuck running on Java 1.6, specifying the `java.io.tmpdir` system environment variable to a directory that is exclusively owned by the executing user will fix this vulnerability. For more information, including an example of vulnerable code, see the referenced GitHub Security Advisory.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-15250","cvss3Severity":"medium","cvss3Score":"5.5","cvss3Metrics":{"A":"None","AC":"Low","PR":"None","S":"Unchanged","C":"High","UI":"Required","AV":"Local","I":"None"},"extraData":{}}</REMEDIATE> -->	True	CVE-2020-15250 (Medium) detected in junit-4.12.jar - ## CVE-2020-15250 - Medium Severity Vulnerability <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>junit-4.12.jar</b></p></summary> <p>JUnit is a unit testing framework for Java, created by Erich Gamma and Kent Beck.</p> <p>Library home page: <a href="http://junit.org">http://junit.org</a></p> <p>Path to dependency file: Rem_Ren_Maven_Test/pom.xml</p> <p>Path to vulnerable library: ry/junit/junit/4.12/junit-4.12.jar</p> <p> Dependency Hierarchy: - :x: junit-4.12.jar (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/sultanabubaker/Rem_Ren_Maven_Test/commit/be48940f6d2bd6a994a73f5d4fdb75cc2abdc7fc">be48940f6d2bd6a994a73f5d4fdb75cc2abdc7fc</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> In JUnit4 from version 4.7 and before 4.13.1, the test rule TemporaryFolder contains a local information disclosure vulnerability. On Unix like systems, the system's temporary directory is shared between all users on that system. Because of this, when files and directories are written into this directory they are, by default, readable by other users on that same system. This vulnerability does not allow other users to overwrite the contents of these directories or files. This is purely an information disclosure vulnerability. This vulnerability impacts you if the JUnit tests write sensitive information, like API keys or passwords, into the temporary folder, and the JUnit tests execute in an environment where the OS has other untrusted users. Because certain JDK file system APIs were only added in JDK 1.7, this this fix is dependent upon the version of the JDK you are using. For Java 1.7 and higher users: this vulnerability is fixed in 4.13.1. For Java 1.6 and lower users: no patch is available, you must use the workaround below. If you are unable to patch, or are stuck running on Java 1.6, specifying the `java.io.tmpdir` system environment variable to a directory that is exclusively owned by the executing user will fix this vulnerability. For more information, including an example of vulnerable code, see the referenced GitHub Security Advisory. <p>Publish Date: 2020-10-12 <p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-15250>CVE-2020-15250</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: High - Integrity Impact: None - Availability Impact: None </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary> <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://github.com/junit-team/junit4/security/advisories/GHSA-269g-pwp5-87pp">https://github.com/junit-team/junit4/security/advisories/GHSA-269g-pwp5-87pp</a></p> <p>Release Date: 2020-10-12</p> <p>Fix Resolution: junit:junit:4.13.1</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":"junit","packageName":"junit","packageVersion":"4.12","packageFilePaths":["/pom.xml"],"isTransitiveDependency":false,"dependencyTree":"junit:junit:4.12","isMinimumFixVersionAvailable":true,"minimumFixVersion":"junit:junit:4.13.1"}],"baseBranches":["main"],"vulnerabilityIdentifier":"CVE-2020-15250","vulnerabilityDetails":"In JUnit4 from version 4.7 and before 4.13.1, the test rule TemporaryFolder contains a local information disclosure vulnerability. On Unix like systems, the system\u0027s temporary directory is shared between all users on that system. Because of this, when files and directories are written into this directory they are, by default, readable by other users on that same system. This vulnerability does not allow other users to overwrite the contents of these directories or files. This is purely an information disclosure vulnerability. This vulnerability impacts you if the JUnit tests write sensitive information, like API keys or passwords, into the temporary folder, and the JUnit tests execute in an environment where the OS has other untrusted users. Because certain JDK file system APIs were only added in JDK 1.7, this this fix is dependent upon the version of the JDK you are using. For Java 1.7 and higher users: this vulnerability is fixed in 4.13.1. For Java 1.6 and lower users: no patch is available, you must use the workaround below. If you are unable to patch, or are stuck running on Java 1.6, specifying the `java.io.tmpdir` system environment variable to a directory that is exclusively owned by the executing user will fix this vulnerability. For more information, including an example of vulnerable code, see the referenced GitHub Security Advisory.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-15250","cvss3Severity":"medium","cvss3Score":"5.5","cvss3Metrics":{"A":"None","AC":"Low","PR":"None","S":"Unchanged","C":"High","UI":"Required","AV":"Local","I":"None"},"extraData":{}}</REMEDIATE> -->	non_priority	cve medium detected in junit jar cve medium severity vulnerability vulnerable library junit jar junit is a unit testing framework for java created by erich gamma and kent beck library home page a href path to dependency file rem ren maven test pom xml path to vulnerable library ry junit junit junit jar dependency hierarchy x junit jar vulnerable library found in head commit a href found in base branch main vulnerability details in from version and before the test rule temporaryfolder contains a local information disclosure vulnerability on unix like systems the system s temporary directory is shared between all users on that system because of this when files and directories are written into this directory they are by default readable by other users on that same system this vulnerability does not allow other users to overwrite the contents of these directories or files this is purely an information disclosure vulnerability this vulnerability impacts you if the junit tests write sensitive information like api keys or passwords into the temporary folder and the junit tests execute in an environment where the os has other untrusted users because certain jdk file system apis were only added in jdk this this fix is dependent upon the version of the jdk you are using for java and higher users this vulnerability is fixed in for java and lower users no patch is available you must use the workaround below if you are unable to patch or are stuck running on java specifying the java io tmpdir system environment variable to a directory that is exclusively owned by the executing user will fix this vulnerability for more information including an example of vulnerable code see the referenced github security advisory 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 high integrity impact none availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution junit junit check this box to open an automated fix pr isopenpronvulnerability false ispackagebased true isdefaultbranch true packages istransitivedependency false dependencytree junit junit isminimumfixversionavailable true minimumfixversion junit junit basebranches vulnerabilityidentifier cve vulnerabilitydetails in from version and before the test rule temporaryfolder contains a local information disclosure vulnerability on unix like systems the system temporary directory is shared between all users on that system because of this when files and directories are written into this directory they are by default readable by other users on that same system this vulnerability does not allow other users to overwrite the contents of these directories or files this is purely an information disclosure vulnerability this vulnerability impacts you if the junit tests write sensitive information like api keys or passwords into the temporary folder and the junit tests execute in an environment where the os has other untrusted users because certain jdk file system apis were only added in jdk this this fix is dependent upon the version of the jdk you are using for java and higher users this vulnerability is fixed in for java and lower users no patch is available you must use the workaround below if you are unable to patch or are stuck running on java specifying the java io tmpdir system environment variable to a directory that is exclusively owned by the executing user will fix this vulnerability for more information including an example of vulnerable code see the referenced github security advisory vulnerabilityurl
178,991	13,807,388,985	IssuesEvent	2020-10-11 21:54:02	389ds/389-ds-base	https://api.github.com/repos/389ds/389-ds-base	closed	Python task timeout updates.	CI test CLI good first issue lib389	Issue Description Importing a file with 1 million users generates an import task failed message. A clear and concise description of what the bug is. Package Version and Platform: - Platform: Fedora 32 - 5.6.6-300.fc32.x86_64 (Cloud Edition) - Package and version: 389-ds-base-1.4.3.12-1.fc32.x86_64 Steps to Reproduce 1. Increase the default import cache size from 16M to 100M. Importing the 1 M user file failed when using the default import cache size. ![image](https://user-images.githubusercontent.com/71395320/93881860-5c9a3680-fcd7-11ea-9e0d-dbd08fd75b95.png) ldapmodify -D "cn=dm" -w password -f update.ldif 2. Verify updates. ldapsearch -D cn=dm -b "cn=bdb,cn=config,cn=ldbm database,cn=plugins,cn=config" -w password objectclass=* nsslapd-import-cachesize ![image](https://user-images.githubusercontent.com/71395320/93882190-c3b7eb00-fcd7-11ea-8cb4-a276ffd223a7.png) 3. Generate an ldif file containing 1 million users. sudo dsctl inst01 ldifgen users --number 1000000 --suffix=dc=example,dc=com --ldif-file users.ldif 4. Import file into instance backend. sudo dsconf inst01 backend import userroot users.ldif ![image](https://user-images.githubusercontent.com/71395320/93880561-98cc9780-fcd5-11ea-89a2-e966c1eb51ad.png) 5. Request a search for everything from the server, works as expected. ldapsearch -D cn=dm -w password objectclass=* ![image](https://user-images.githubusercontent.com/71395320/93881230-899a1980-fcd6-11ea-8a21-23c71769009d.png) Expected results It was expected that a search of the server DB would fail following the import task error. This error message could prevent some user automation maybe. Additional context	1.0	Python task timeout updates. - Issue Description Importing a file with 1 million users generates an import task failed message. A clear and concise description of what the bug is. Package Version and Platform: - Platform: Fedora 32 - 5.6.6-300.fc32.x86_64 (Cloud Edition) - Package and version: 389-ds-base-1.4.3.12-1.fc32.x86_64 Steps to Reproduce 1. Increase the default import cache size from 16M to 100M. Importing the 1 M user file failed when using the default import cache size. ![image](https://user-images.githubusercontent.com/71395320/93881860-5c9a3680-fcd7-11ea-9e0d-dbd08fd75b95.png) ldapmodify -D "cn=dm" -w password -f update.ldif 2. Verify updates. ldapsearch -D cn=dm -b "cn=bdb,cn=config,cn=ldbm database,cn=plugins,cn=config" -w password objectclass=* nsslapd-import-cachesize ![image](https://user-images.githubusercontent.com/71395320/93882190-c3b7eb00-fcd7-11ea-8cb4-a276ffd223a7.png) 3. Generate an ldif file containing 1 million users. sudo dsctl inst01 ldifgen users --number 1000000 --suffix=dc=example,dc=com --ldif-file users.ldif 4. Import file into instance backend. sudo dsconf inst01 backend import userroot users.ldif ![image](https://user-images.githubusercontent.com/71395320/93880561-98cc9780-fcd5-11ea-89a2-e966c1eb51ad.png) 5. Request a search for everything from the server, works as expected. ldapsearch -D cn=dm -w password objectclass=* ![image](https://user-images.githubusercontent.com/71395320/93881230-899a1980-fcd6-11ea-8a21-23c71769009d.png) Expected results It was expected that a search of the server DB would fail following the import task error. This error message could prevent some user automation maybe. Additional context	non_priority	python task timeout updates issue description importing a file with million users generates an import task failed message a clear and concise description of what the bug is package version and platform platform fedora cloud edition package and version ds base steps to reproduce increase the default import cache size from to importing the m user file failed when using the default import cache size ldapmodify d cn dm w password f update ldif verify updates ldapsearch d cn dm b cn bdb cn config cn ldbm database cn plugins cn config w password objectclass nsslapd import cachesize generate an ldif file containing million users sudo dsctl ldifgen users number suffix dc example dc com ldif file users ldif import file into instance backend sudo dsconf backend import userroot users ldif request a search for everything from the server works as expected ldapsearch d cn dm w password objectclass expected results it was expected that a search of the server db would fail following the import task error this error message could prevent some user automation maybe additional context
56,525	6,521,399,633	IssuesEvent	2017-08-28 20:25:29	OData/odata.net	https://api.github.com/repos/OData/odata.net	closed	Need to verify the test cases in LinqTests.cs	SkippedTestClean	<!-- markdownlint-disable MD002 MD041 --> Need to verify/modify the test cases in LinqTests.cs. ### Assemblies affected Test ### Reproduce steps Uncomment to run the test cases in cs file. ### Expected result All test cases pass. ### Actual result Most of test cases failed.	1.0	Need to verify the test cases in LinqTests.cs - <!-- markdownlint-disable MD002 MD041 --> Need to verify/modify the test cases in LinqTests.cs. ### Assemblies affected Test ### Reproduce steps Uncomment to run the test cases in cs file. ### Expected result All test cases pass. ### Actual result Most of test cases failed.	non_priority	need to verify the test cases in linqtests cs need to verify modify the test cases in linqtests cs assemblies affected test reproduce steps uncomment to run the test cases in cs file expected result all test cases pass actual result most of test cases failed
15,994	20,188,204,609	IssuesEvent	2022-02-11 01:17:49	savitamittalmsft/WAS-SEC-TEST	https://api.github.com/repos/savitamittalmsft/WAS-SEC-TEST	opened	Use Azure Firewall or a 3rd party next-generation firewall to protect against data exfiltration	WARP-Import WAF FEB 2021 Security Performance and Scalability Capacity Management Processes Networking & Connectivity Connectivity	<a href="https://docs.microsoft.com/azure/architecture/framework/security/design-network-flow#data-exfiltration">Use Azure Firewall or a 3rd party next-generation firewall to protect against data exfiltration</a> <p><b>Why Consider This?</b></p> NVA solutions and Azure Firewall (for supported protocols) can be leveraged as a reverse proxy to restrict access to only authorized PaaS services for services where Private Link is not yet supported (Azure Firewall). <p><b>Context</b></p> <p><b>Suggested Actions</b></p> <p><span>Configure Azure Firewall or a 3rd party next generation firewall to protect against data exfiltration concerns.</span></p> <p><b>Learn More</b></p> <p><a href="https://docs.microsoft.com/en-us/azure/firewall/" target="_blank"><span>https://docs.microsoft.com/en-us/azure/firewall/</span></a><span /></p><p><a href="https://azuremarketplace.microsoft.com/en-us/marketplace/apps/category/networking" target="_blank"><span>https://azuremarketplace.microsoft.com/en-us/marketplace/apps/category/networking</span></a><span /></p>	1.0	Use Azure Firewall or a 3rd party next-generation firewall to protect against data exfiltration - <a href="https://docs.microsoft.com/azure/architecture/framework/security/design-network-flow#data-exfiltration">Use Azure Firewall or a 3rd party next-generation firewall to protect against data exfiltration</a> <p><b>Why Consider This?</b></p> NVA solutions and Azure Firewall (for supported protocols) can be leveraged as a reverse proxy to restrict access to only authorized PaaS services for services where Private Link is not yet supported (Azure Firewall). <p><b>Context</b></p> <p><b>Suggested Actions</b></p> <p><span>Configure Azure Firewall or a 3rd party next generation firewall to protect against data exfiltration concerns.</span></p> <p><b>Learn More</b></p> <p><a href="https://docs.microsoft.com/en-us/azure/firewall/" target="_blank"><span>https://docs.microsoft.com/en-us/azure/firewall/</span></a><span /></p><p><a href="https://azuremarketplace.microsoft.com/en-us/marketplace/apps/category/networking" target="_blank"><span>https://azuremarketplace.microsoft.com/en-us/marketplace/apps/category/networking</span></a><span /></p>	non_priority	use azure firewall or a party next generation firewall to protect against data exfiltration why consider this nva solutions and azure firewall for supported protocols can be leveraged as a reverse proxy to restrict access to only authorized paas services for services where private link is not yet supported azure firewall context suggested actions configure azure firewall or a party next generation firewall to protect against data exfiltration concerns learn more
126,136	16,981,083,822	IssuesEvent	2021-06-30 08:56:55	Kukustar/bookkeping	https://api.github.com/repos/Kukustar/bookkeping	opened	Atomic design	design fiture	Create component lib in UI using atomic design. Use material design - https://github.com/material-components/material-components-web Need to bootstrap project via webpack solution - https://glitch.com/~material-starter-kit Design system - https://material.io/design/material-studies/rally.html#motion	1.0	Atomic design - Create component lib in UI using atomic design. Use material design - https://github.com/material-components/material-components-web Need to bootstrap project via webpack solution - https://glitch.com/~material-starter-kit Design system - https://material.io/design/material-studies/rally.html#motion	non_priority	atomic design create component lib in ui using atomic design use material design need to bootstrap project via webpack solution design system
15,919	5,195,652,636	IssuesEvent	2017-01-23 10:07:49	SemsTestOrg/combinearchive-web	https://api.github.com/repos/SemsTestOrg/combinearchive-web	closed	"include own VCard" checkbox	code fixed major migrated task	## Trac Ticket #110 component: code owner: somebody reporter: martinP created: 2015-04-09 12:59:58 milestone: type: task version: keywords: ## comment 1 time: 2015-09-28 16:31:43 author: mp487 <martin.peters3@uni-rostock.de> In changeset:"e6bcbc8b06911f4675b19d8e08b8976e921a55d1"]: ```CommitTicketReference repository="" revision="e6bcbc8b06911f4675b19d8e08b8976e921a55d1" added checkbox in html [see #110] no function atm ``` ## comment 2 time: 2015-09-28 16:31:45 author: mp487 <martin.peters3@uni-rostock.de> In changeset:"a932b55712c1383b880a01b8a9a60aac7122c3df"]: ```CommitTicketReference repository="" revision="a932b55712c1383b880a01b8a9a60aac7122c3df" added check only when creating empty archives atm [see #110] ``` ## comment 3 time: 2015-09-28 16:31:46 author: mp487 <martin.peters3@uni-rostock.de> In changeset:"2be02977e4216f1ceb4bbe91d6c05b10baeb6e7a"]: ```CommitTicketReference repository="" revision="2be02977e4216f1ceb4bbe91d6c05b10baeb6e7a" fixed typo in jQuery statement [see #110] ``` ## comment 4 time: 2015-09-28 16:31:48 author: mp487 <martin.peters3@uni-rostock.de> In changeset:"acaa5883e8b24debedbee7f6cfca25ca1715f904"]: ```CommitTicketReference repository="" revision="acaa5883e8b24debedbee7f6cfca25ca1715f904" added some handy Tools methods for handling VCards and also impl support for adding own VCard to imported archives [see #110] ``` ## comment 5 time: 2015-09-28 16:31:49 author: mp487 <martin.peters3@uni-rostock.de> In changeset:"cd947cc19e859ae0f44c99b9f82076cc70ac4d2c"]: ```CommitTicketReference repository="" revision="cd947cc19e859ae0f44c99b9f82076cc70ac4d2c" forgot to add statement in RestApi [see #110] ``` ## comment 6 time: 2015-09-28 16:31:50 author: mp487 <martin.peters3@uni-rostock.de> In changeset:"b3d0e38be6f2ef49bbd3305a234a67097f16e213"]: ```CommitTicketReference repository="" revision="b3d0e38be6f2ef49bbd3305a234a67097f16e213" forgot pack() after adding meta data [see #110] ``` ## comment 7 time: 2015-10-06 10:53:46 author: martinP rename to "add me as creator" check/uncheck it recording to import option ## comment 8 time: 2015-10-06 14:43:34 author: mp487 <martin.peters3@uni-rostock.de> In changeset:"a0a3e23df8d58f996a48b5c04e121a13e582b849"]: ```CommitTicketReference repository="" revision="a0a3e23df8d58f996a48b5c04e121a13e582b849" rename "include own VCard" to "add me as Creator" [see #110] ``` ## comment 9 time: 2015-10-06 14:43:36 author: mp487 <martin.peters3@uni-rostock.de> In changeset:"4e1fc190a2677d0fa5de012b87671ce2a382245c"]: ```CommitTicketReference repository="" revision="4e1fc190a2677d0fa5de012b87671ce2a382245c" added auto pref for ownVCard checkbox [see #110] ``` ## comment 10 time: 2015-10-06 14:57:42 author: martinP ## comment 11 time: 2015-10-06 14:57:42 author: martinP Updated resolution to fixed ## comment 12 time: 2015-10-06 14:57:42 author: martinP Updated status to closed	1.0	"include own VCard" checkbox - ## Trac Ticket #110 component: code owner: somebody reporter: martinP created: 2015-04-09 12:59:58 milestone: type: task version: keywords: ## comment 1 time: 2015-09-28 16:31:43 author: mp487 <martin.peters3@uni-rostock.de> In changeset:"e6bcbc8b06911f4675b19d8e08b8976e921a55d1"]: ```CommitTicketReference repository="" revision="e6bcbc8b06911f4675b19d8e08b8976e921a55d1" added checkbox in html [see #110] no function atm ``` ## comment 2 time: 2015-09-28 16:31:45 author: mp487 <martin.peters3@uni-rostock.de> In changeset:"a932b55712c1383b880a01b8a9a60aac7122c3df"]: ```CommitTicketReference repository="" revision="a932b55712c1383b880a01b8a9a60aac7122c3df" added check only when creating empty archives atm [see #110] ``` ## comment 3 time: 2015-09-28 16:31:46 author: mp487 <martin.peters3@uni-rostock.de> In changeset:"2be02977e4216f1ceb4bbe91d6c05b10baeb6e7a"]: ```CommitTicketReference repository="" revision="2be02977e4216f1ceb4bbe91d6c05b10baeb6e7a" fixed typo in jQuery statement [see #110] ``` ## comment 4 time: 2015-09-28 16:31:48 author: mp487 <martin.peters3@uni-rostock.de> In changeset:"acaa5883e8b24debedbee7f6cfca25ca1715f904"]: ```CommitTicketReference repository="" revision="acaa5883e8b24debedbee7f6cfca25ca1715f904" added some handy Tools methods for handling VCards and also impl support for adding own VCard to imported archives [see #110] ``` ## comment 5 time: 2015-09-28 16:31:49 author: mp487 <martin.peters3@uni-rostock.de> In changeset:"cd947cc19e859ae0f44c99b9f82076cc70ac4d2c"]: ```CommitTicketReference repository="" revision="cd947cc19e859ae0f44c99b9f82076cc70ac4d2c" forgot to add statement in RestApi [see #110] ``` ## comment 6 time: 2015-09-28 16:31:50 author: mp487 <martin.peters3@uni-rostock.de> In changeset:"b3d0e38be6f2ef49bbd3305a234a67097f16e213"]: ```CommitTicketReference repository="" revision="b3d0e38be6f2ef49bbd3305a234a67097f16e213" forgot pack() after adding meta data [see #110] ``` ## comment 7 time: 2015-10-06 10:53:46 author: martinP rename to "add me as creator" check/uncheck it recording to import option ## comment 8 time: 2015-10-06 14:43:34 author: mp487 <martin.peters3@uni-rostock.de> In changeset:"a0a3e23df8d58f996a48b5c04e121a13e582b849"]: ```CommitTicketReference repository="" revision="a0a3e23df8d58f996a48b5c04e121a13e582b849" rename "include own VCard" to "add me as Creator" [see #110] ``` ## comment 9 time: 2015-10-06 14:43:36 author: mp487 <martin.peters3@uni-rostock.de> In changeset:"4e1fc190a2677d0fa5de012b87671ce2a382245c"]: ```CommitTicketReference repository="" revision="4e1fc190a2677d0fa5de012b87671ce2a382245c" added auto pref for ownVCard checkbox [see #110] ``` ## comment 10 time: 2015-10-06 14:57:42 author: martinP ## comment 11 time: 2015-10-06 14:57:42 author: martinP Updated resolution to fixed ## comment 12 time: 2015-10-06 14:57:42 author: martinP Updated status to closed	non_priority	include own vcard checkbox trac ticket component code owner somebody reporter martinp created milestone type task version keywords comment time author in changeset committicketreference repository revision added checkbox in html no function atm comment time author in changeset committicketreference repository revision added check only when creating empty archives atm comment time author in changeset committicketreference repository revision fixed typo in jquery statement comment time author in changeset committicketreference repository revision added some handy tools methods for handling vcards and also impl support for adding own vcard to imported archives comment time author in changeset committicketreference repository revision forgot to add statement in restapi comment time author in changeset committicketreference repository revision forgot pack after adding meta data comment time author martinp rename to add me as creator check uncheck it recording to import option comment time author in changeset committicketreference repository revision rename include own vcard to add me as creator comment time author in changeset committicketreference repository revision added auto pref for ownvcard checkbox comment time author martinp comment time author martinp updated resolution to fixed comment time author martinp updated status to closed
115,381	14,738,083,298	IssuesEvent	2021-01-07 03:41:55	newappwelove/perfinance	https://api.github.com/repos/newappwelove/perfinance	closed	Signin & Signup View	design web-client	https://www.figma.com/file/88a7VHeGfXRBr5FMivONJG/Perfinance?node-id=40%3A1321 Sign In Dark Mode ![X - Dark mode](https://user-images.githubusercontent.com/52730845/103848364-c991da80-50d4-11eb-83e4-54ef6e0539ca.png) Sign In Light Mode ![X - Light mode](https://user-images.githubusercontent.com/52730845/103848369-ceef2500-50d4-11eb-918b-a278a4d56b3b.png) Sign Up Dark Mode ![X - Dark mode](https://user-images.githubusercontent.com/52730845/103848380-d6163300-50d4-11eb-8e0d-4f1dc311af1d.png) Sign Up Light Mode ![X - Light mode](https://user-images.githubusercontent.com/52730845/103848388-da425080-50d4-11eb-87bc-3112aae1f913.png)	1.0	Signin & Signup View - https://www.figma.com/file/88a7VHeGfXRBr5FMivONJG/Perfinance?node-id=40%3A1321 Sign In Dark Mode ![X - Dark mode](https://user-images.githubusercontent.com/52730845/103848364-c991da80-50d4-11eb-83e4-54ef6e0539ca.png) Sign In Light Mode ![X - Light mode](https://user-images.githubusercontent.com/52730845/103848369-ceef2500-50d4-11eb-918b-a278a4d56b3b.png) Sign Up Dark Mode ![X - Dark mode](https://user-images.githubusercontent.com/52730845/103848380-d6163300-50d4-11eb-8e0d-4f1dc311af1d.png) Sign Up Light Mode ![X - Light mode](https://user-images.githubusercontent.com/52730845/103848388-da425080-50d4-11eb-87bc-3112aae1f913.png)	non_priority	signin signup view sign in dark mode sign in light mode sign up dark mode sign up light mode
171,238	27,087,586,601	IssuesEvent	2023-02-14 18:10:25	department-of-veterans-affairs/va.gov-team	https://api.github.com/repos/department-of-veterans-affairs/va.gov-team	closed	Review Change Comm. Plan for #50774	service-design	## Purpose Asked to review Change Comm. Plan for upcoming Datadog read-only launch (#50774) ## Tasks - [ ] Review Change communication Plan ## Acceptance Criteria - [ ] Reviewed and comments communicated	1.0	Review Change Comm. Plan for #50774 - ## Purpose Asked to review Change Comm. Plan for upcoming Datadog read-only launch (#50774) ## Tasks - [ ] Review Change communication Plan ## Acceptance Criteria - [ ] Reviewed and comments communicated	non_priority	review change comm plan for purpose asked to review change comm plan for upcoming datadog read only launch tasks review change communication plan acceptance criteria reviewed and comments communicated
130,369	18,155,777,445	IssuesEvent	2021-09-27 01:13:36	crossbrowsertesting/cbt-tunnel-nodejs	https://api.github.com/repos/crossbrowsertesting/cbt-tunnel-nodejs	opened	CVE-2021-23406 (High) detected in degenerator-1.0.4.tgz	security vulnerability	## CVE-2021-23406 - High Severity Vulnerability <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>degenerator-1.0.4.tgz</b></p></summary> <p>Turns sync functions into async generator functions</p> <p>Library home page: <a href="https://registry.npmjs.org/degenerator/-/degenerator-1.0.4.tgz">https://registry.npmjs.org/degenerator/-/degenerator-1.0.4.tgz</a></p> <p>Path to dependency file: cbt-tunnel-nodejs/package.json</p> <p>Path to vulnerable library: cbt-tunnel-nodejs/node_modules/degenerator/package.json</p> <p> Dependency Hierarchy: - pac-resolver-3.0.1.tgz (Root Library) - :x: degenerator-1.0.4.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> This affects the package pac-resolver before 5.0.0. This can occur when used with untrusted input, due to unsafe PAC file handling. NOTE: The fix for this vulnerability is applied in the node-degenerator library, a dependency written by the same maintainer. <p>Publish Date: 2021-08-24 <p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-23406>CVE-2021-23406</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://github.com/advisories/GHSA-9j49-mfvp-vmhm">https://github.com/advisories/GHSA-9j49-mfvp-vmhm</a></p> <p>Release Date: 2021-08-24</p> <p>Fix Resolution: pac-resolver -5.0.0, degenerator - 3.0.1</p> </p> </details> <p></p> <!-- <REMEDIATE>{"isOpenPROnVulnerability":false,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"degenerator","packageVersion":"1.0.4","packageFilePaths":["/package.json"],"isTransitiveDependency":true,"dependencyTree":"@crossbrowsertesting/pac-resolver:3.0.1;degenerator:1.0.4","isMinimumFixVersionAvailable":true,"minimumFixVersion":"pac-resolver -5.0.0, degenerator - 3.0.1"}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2021-23406","vulnerabilityDetails":"This affects the package pac-resolver before 5.0.0. This can occur when used with untrusted input, due to unsafe PAC file handling. NOTE: The fix for this vulnerability is applied in the node-degenerator library, a dependency written by the same maintainer.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-23406","cvss3Severity":"high","cvss3Score":"9.8","cvss3Metrics":{"A":"High","AC":"Low","PR":"None","S":"Unchanged","C":"High","UI":"None","AV":"Network","I":"High"},"extraData":{}}</REMEDIATE> -->	True	CVE-2021-23406 (High) detected in degenerator-1.0.4.tgz - ## CVE-2021-23406 - High Severity Vulnerability <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>degenerator-1.0.4.tgz</b></p></summary> <p>Turns sync functions into async generator functions</p> <p>Library home page: <a href="https://registry.npmjs.org/degenerator/-/degenerator-1.0.4.tgz">https://registry.npmjs.org/degenerator/-/degenerator-1.0.4.tgz</a></p> <p>Path to dependency file: cbt-tunnel-nodejs/package.json</p> <p>Path to vulnerable library: cbt-tunnel-nodejs/node_modules/degenerator/package.json</p> <p> Dependency Hierarchy: - pac-resolver-3.0.1.tgz (Root Library) - :x: degenerator-1.0.4.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> This affects the package pac-resolver before 5.0.0. This can occur when used with untrusted input, due to unsafe PAC file handling. NOTE: The fix for this vulnerability is applied in the node-degenerator library, a dependency written by the same maintainer. <p>Publish Date: 2021-08-24 <p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-23406>CVE-2021-23406</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://github.com/advisories/GHSA-9j49-mfvp-vmhm">https://github.com/advisories/GHSA-9j49-mfvp-vmhm</a></p> <p>Release Date: 2021-08-24</p> <p>Fix Resolution: pac-resolver -5.0.0, degenerator - 3.0.1</p> </p> </details> <p></p> <!-- <REMEDIATE>{"isOpenPROnVulnerability":false,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"degenerator","packageVersion":"1.0.4","packageFilePaths":["/package.json"],"isTransitiveDependency":true,"dependencyTree":"@crossbrowsertesting/pac-resolver:3.0.1;degenerator:1.0.4","isMinimumFixVersionAvailable":true,"minimumFixVersion":"pac-resolver -5.0.0, degenerator - 3.0.1"}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2021-23406","vulnerabilityDetails":"This affects the package pac-resolver before 5.0.0. This can occur when used with untrusted input, due to unsafe PAC file handling. NOTE: The fix for this vulnerability is applied in the node-degenerator library, a dependency written by the same maintainer.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-23406","cvss3Severity":"high","cvss3Score":"9.8","cvss3Metrics":{"A":"High","AC":"Low","PR":"None","S":"Unchanged","C":"High","UI":"None","AV":"Network","I":"High"},"extraData":{}}</REMEDIATE> -->	non_priority	cve high detected in degenerator tgz cve high severity vulnerability vulnerable library degenerator tgz turns sync functions into async generator functions library home page a href path to dependency file cbt tunnel nodejs package json path to vulnerable library cbt tunnel nodejs node modules degenerator package json dependency hierarchy pac resolver tgz root library x degenerator tgz vulnerable library found in base branch master vulnerability details this affects the package pac resolver before this can occur when used with untrusted input due to unsafe pac file handling note the fix for this vulnerability is applied in the node degenerator library a dependency written by the same maintainer 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 pac resolver degenerator isopenpronvulnerability false ispackagebased true isdefaultbranch true packages istransitivedependency true dependencytree crossbrowsertesting pac resolver degenerator isminimumfixversionavailable true minimumfixversion pac resolver degenerator basebranches vulnerabilityidentifier cve vulnerabilitydetails this affects the package pac resolver before this can occur when used with untrusted input due to unsafe pac file handling note the fix for this vulnerability is applied in the node degenerator library a dependency written by the same maintainer vulnerabilityurl
441,009	30,765,397,859	IssuesEvent	2023-07-30 08:24:19	sktime/sktime	https://api.github.com/repos/sktime/sktime	opened	Update sktime meet up google calender	documentation	#### Describe the issue linked to the documentation I believe the google calendar isnt updated with current rhythm of the meetups. Adding this as a issue here so that its visible. #### Suggest a potential alternative/fix It would be helpful if its either updated or replaced with tabular format of events that I believe mostly are scheduled on Fridays/Tuesday. Certainly the preference would be to have a calendar so that anyone can add it to their calendar. As per Discord Unless otherwise stated, times are Fridays, in UTC, on sktime discord (meet in dev/meet-ups channel ⁠meet-ups) 15:00-16:00pm - collaborative coding session & community meet-up 16:00pm - regular community council meeting workstreams: 11:00am - pipelines, pywatts ⁠pipelines-pywatts forecasting/deep learning/pytorch - at weekly meet-up benchmarking, tuning - at weekly meet-up skbase - async, https://github.com/sktime/skbase summer mentorship programme: 3pm UTC, Tue & Fri - mentee stand-up (Fri is together with community meet-up)	1.0	Update sktime meet up google calender - #### Describe the issue linked to the documentation I believe the google calendar isnt updated with current rhythm of the meetups. Adding this as a issue here so that its visible. #### Suggest a potential alternative/fix It would be helpful if its either updated or replaced with tabular format of events that I believe mostly are scheduled on Fridays/Tuesday. Certainly the preference would be to have a calendar so that anyone can add it to their calendar. As per Discord Unless otherwise stated, times are Fridays, in UTC, on sktime discord (meet in dev/meet-ups channel ⁠meet-ups) 15:00-16:00pm - collaborative coding session & community meet-up 16:00pm - regular community council meeting workstreams: 11:00am - pipelines, pywatts ⁠pipelines-pywatts forecasting/deep learning/pytorch - at weekly meet-up benchmarking, tuning - at weekly meet-up skbase - async, https://github.com/sktime/skbase summer mentorship programme: 3pm UTC, Tue & Fri - mentee stand-up (Fri is together with community meet-up)	non_priority	update sktime meet up google calender describe the issue linked to the documentation i believe the google calendar isnt updated with current rhythm of the meetups adding this as a issue here so that its visible suggest a potential alternative fix it would be helpful if its either updated or replaced with tabular format of events that i believe mostly are scheduled on fridays tuesday certainly the preference would be to have a calendar so that anyone can add it to their calendar as per discord unless otherwise stated times are fridays in utc on sktime discord meet in dev meet ups channel ⁠meet ups collaborative coding session community meet up regular community council meeting workstreams pipelines pywatts ⁠pipelines pywatts forecasting deep learning pytorch at weekly meet up benchmarking tuning at weekly meet up skbase async summer mentorship programme utc tue fri mentee stand up fri is together with community meet up
7,936	8,124,701,384	IssuesEvent	2018-08-16 18:25:19	MicrosoftDocs/azure-docs	https://api.github.com/repos/MicrosoftDocs/azure-docs	closed	Reporting broken link	assigned-to-author doc-bug service-fabric/svc triaged	> For encrypting the disks (OS drive and other managed disks) attached to your nodes, we leverage the Azure Disk Encryption. Azure Disk Encryption is a new capability that helps you encrypt your Windows virtual machine disks. In the above, the https://docs.microsoft.com/en-us/azure/service-fabric/service-fabric-enable-azure-disk-encryption-windows behind _encrypt your Windows virtual machine disks_ is broken, it points to https://docs.microsoft.com/en-us/azure/service-fabric/service-fabric-cluster-creation-via-portal --- #### Document Details ⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking. * ID: 6202fb05-c2b0-b87f-71c9-5683e54f5e0c * Version Independent ID: 39505638-9926-fbc6-a795-3d7699859cde * Content: [Create an Azure Service Fabric cluster from a template](https://docs.microsoft.com/en-us/azure/service-fabric/service-fabric-cluster-creation-via-arm#encrypting-the-disks-attached-to-your-windows-cluster-nodevirtual-machine-instances) * Content Source: [articles/service-fabric/service-fabric-cluster-creation-via-arm.md](https://github.com/Microsoft/azure-docs/blob/master/articles/service-fabric/service-fabric-cluster-creation-via-arm.md) * Service: service-fabric * GitHub Login: @aljo-microsoft * Microsoft Alias: aljo	1.0	Reporting broken link - > For encrypting the disks (OS drive and other managed disks) attached to your nodes, we leverage the Azure Disk Encryption. Azure Disk Encryption is a new capability that helps you encrypt your Windows virtual machine disks. In the above, the https://docs.microsoft.com/en-us/azure/service-fabric/service-fabric-enable-azure-disk-encryption-windows behind _encrypt your Windows virtual machine disks_ is broken, it points to https://docs.microsoft.com/en-us/azure/service-fabric/service-fabric-cluster-creation-via-portal --- #### Document Details ⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking. * ID: 6202fb05-c2b0-b87f-71c9-5683e54f5e0c * Version Independent ID: 39505638-9926-fbc6-a795-3d7699859cde * Content: [Create an Azure Service Fabric cluster from a template](https://docs.microsoft.com/en-us/azure/service-fabric/service-fabric-cluster-creation-via-arm#encrypting-the-disks-attached-to-your-windows-cluster-nodevirtual-machine-instances) * Content Source: [articles/service-fabric/service-fabric-cluster-creation-via-arm.md](https://github.com/Microsoft/azure-docs/blob/master/articles/service-fabric/service-fabric-cluster-creation-via-arm.md) * Service: service-fabric * GitHub Login: @aljo-microsoft * Microsoft Alias: aljo	non_priority	reporting broken link for encrypting the disks os drive and other managed disks attached to your nodes we leverage the azure disk encryption azure disk encryption is a new capability that helps you encrypt your windows virtual machine disks in the above the behind encrypt your windows virtual machine disks is broken it points to document details ⚠ do not edit this section it is required for docs microsoft com ➟ github issue linking id version independent id content content source service service fabric github login aljo microsoft microsoft alias aljo
234,254	19,122,524,152	IssuesEvent	2021-12-01 01:09:53	cockroachdb/cockroach	https://api.github.com/repos/cockroachdb/cockroach	closed	roachtest: kv/multi-store-with-overload failed	C-test-failure O-robot O-roachtest branch-master	roachtest.kv/multi-store-with-overload [failed](https://teamcity.cockroachdb.com/viewLog.html?buildId=3804493&tab=buildLog) with [artifacts](https://teamcity.cockroachdb.com/viewLog.html?buildId=3804493&tab=artifacts#/kv/multi-store-with-overload) on master @ [40f11fead0a0453969634f8ddb0502c1f78b2806](https://github.com/cockroachdb/cockroach/commits/40f11fead0a0453969634f8ddb0502c1f78b2806): ``` \| stdout: \| teamcity-3804493-1637959164-50-n2cpu8: starting nodes \| 0: ~ ./cockroach.sh: exit status 1 \| (1) attached stack trace \| -- stack trace: \| \| github.com/cockroachdb/cockroach/pkg/roachprod/install.(SyncedCluster).startNode \| \| /home/agent/work/.go/src/github.com/cockroachdb/cockroach/pkg/roachprod/install/cockroach.go:348 \| \| github.com/cockroachdb/cockroach/pkg/roachprod/install.(SyncedCluster).Start.func1 \| \| /home/agent/work/.go/src/github.com/cockroachdb/cockroach/pkg/roachprod/install/cockroach.go:130 \| \| github.com/cockroachdb/cockroach/pkg/roachprod/install.(SyncedCluster).ParallelE.func1.1 \| \| /home/agent/work/.go/src/github.com/cockroachdb/cockroach/pkg/roachprod/install/cluster_synced.go:1968 \| \| runtime.goexit \| \| /usr/local/go/src/runtime/asm_amd64.s:1581 \| Wraps: (2) ~ ./cockroach.sh \| \| [0;1;31mJob for cockroach.service failed because the control process exited with error code.[0m \| \| [0;1;31mSee "systemctl status cockroach.service" and "journalctl -xe" for details.[0m \| Wraps: (3) exit status 1 \| Error types: (1) withstack.withStack (2) errutil.withPrefix (3) exec.ExitError: \| Error: UNCLASSIFIED_PROBLEM: one or more parallel execution failure \| (1) UNCLASSIFIED_PROBLEM \| Wraps: (2) attached stack trace \| -- stack trace: \| \| github.com/cockroachdb/cockroach/pkg/roachprod/install.(SyncedCluster).ParallelE \| \| /home/agent/work/.go/src/github.com/cockroachdb/cockroach/pkg/roachprod/install/cluster_synced.go:2045 \| \| github.com/cockroachdb/cockroach/pkg/roachprod/install.(SyncedCluster).Parallel \| \| /home/agent/work/.go/src/github.com/cockroachdb/cockroach/pkg/roachprod/install/cluster_synced.go:1929 \| \| github.com/cockroachdb/cockroach/pkg/roachprod/install.(SyncedCluster).Start \| \| /home/agent/work/.go/src/github.com/cockroachdb/cockroach/pkg/roachprod/install/cockroach.go:121 \| \| github.com/cockroachdb/cockroach/pkg/roachprod.Start \| \| /home/agent/work/.go/src/github.com/cockroachdb/cockroach/pkg/roachprod/roachprod.go:573 \| \| main.glob..func9 \| \| /home/agent/work/.go/src/github.com/cockroachdb/cockroach/pkg/cmd/roachprod/main.go:397 \| \| main.wrap.func1 \| \| /home/agent/work/.go/src/github.com/cockroachdb/cockroach/pkg/cmd/roachprod/main.go:65 \| \| github.com/spf13/cobra.(Command).execute \| \| /home/agent/work/.go/src/github.com/cockroachdb/cockroach/vendor/github.com/spf13/cobra/command.go:856 \| \| github.com/spf13/cobra.(Command).ExecuteC \| \| /home/agent/work/.go/src/github.com/cockroachdb/cockroach/vendor/github.com/spf13/cobra/command.go:960 \| \| github.com/spf13/cobra.(Command).Execute \| \| /home/agent/work/.go/src/github.com/cockroachdb/cockroach/vendor/github.com/spf13/cobra/command.go:897 \| \| main.main \| \| /home/agent/work/.go/src/github.com/cockroachdb/cockroach/pkg/cmd/roachprod/main.go:905 \| \| runtime.main \| \| /usr/local/go/src/runtime/proc.go:255 \| \| runtime.goexit \| \| /usr/local/go/src/runtime/asm_amd64.s:1581 \| Wraps: (3) one or more parallel execution failure \| Error types: (1) errors.Unclassified (2) withstack.withStack (3) errutil.leafError Wraps: (2) exit status 1 Error types: (1) cluster.WithCommandDetails (2) exec.ExitError ``` <details><summary>Help</summary> <p> See: [roachtest README](https://github.com/cockroachdb/cockroach/blob/master/pkg/cmd/roachtest/README.md) See: [How To Investigate $internal$](https://cockroachlabs.atlassian.net/l/c/SSSBr8c7) </p> </details> <details><summary>Same failure on other branches</summary> <p> - #72867 roachtest: kv/multi-store-with-overload failed [perm denied] [C-test-failure O-roachtest O-robot branch-release-21.2] </p> </details> /cc @cockroachdb/kv-triage <sub> [This test on roachdash](https://roachdash.crdb.dev/?filter=status:open%20t:.kv/multi-store-with-overload.&sort=title+created&display=lastcommented+project) \| [Improve this report!](https://github.com/cockroachdb/cockroach/tree/master/pkg/cmd/internal/issues) </sub>	2.0	roachtest: kv/multi-store-with-overload failed - roachtest.kv/multi-store-with-overload [failed](https://teamcity.cockroachdb.com/viewLog.html?buildId=3804493&tab=buildLog) with [artifacts](https://teamcity.cockroachdb.com/viewLog.html?buildId=3804493&tab=artifacts#/kv/multi-store-with-overload) on master @ [40f11fead0a0453969634f8ddb0502c1f78b2806](https://github.com/cockroachdb/cockroach/commits/40f11fead0a0453969634f8ddb0502c1f78b2806): ``` \| stdout: \| teamcity-3804493-1637959164-50-n2cpu8: starting nodes \| 0: ~ ./cockroach.sh: exit status 1 \| (1) attached stack trace \| -- stack trace: \| \| github.com/cockroachdb/cockroach/pkg/roachprod/install.(SyncedCluster).startNode \| \| /home/agent/work/.go/src/github.com/cockroachdb/cockroach/pkg/roachprod/install/cockroach.go:348 \| \| github.com/cockroachdb/cockroach/pkg/roachprod/install.(SyncedCluster).Start.func1 \| \| /home/agent/work/.go/src/github.com/cockroachdb/cockroach/pkg/roachprod/install/cockroach.go:130 \| \| github.com/cockroachdb/cockroach/pkg/roachprod/install.(SyncedCluster).ParallelE.func1.1 \| \| /home/agent/work/.go/src/github.com/cockroachdb/cockroach/pkg/roachprod/install/cluster_synced.go:1968 \| \| runtime.goexit \| \| /usr/local/go/src/runtime/asm_amd64.s:1581 \| Wraps: (2) ~ ./cockroach.sh \| \| [0;1;31mJob for cockroach.service failed because the control process exited with error code.[0m \| \| [0;1;31mSee "systemctl status cockroach.service" and "journalctl -xe" for details.[0m \| Wraps: (3) exit status 1 \| Error types: (1) withstack.withStack (2) errutil.withPrefix (3) exec.ExitError: \| Error: UNCLASSIFIED_PROBLEM: one or more parallel execution failure \| (1) UNCLASSIFIED_PROBLEM \| Wraps: (2) attached stack trace \| -- stack trace: \| \| github.com/cockroachdb/cockroach/pkg/roachprod/install.(SyncedCluster).ParallelE \| \| /home/agent/work/.go/src/github.com/cockroachdb/cockroach/pkg/roachprod/install/cluster_synced.go:2045 \| \| github.com/cockroachdb/cockroach/pkg/roachprod/install.(SyncedCluster).Parallel \| \| /home/agent/work/.go/src/github.com/cockroachdb/cockroach/pkg/roachprod/install/cluster_synced.go:1929 \| \| github.com/cockroachdb/cockroach/pkg/roachprod/install.(SyncedCluster).Start \| \| /home/agent/work/.go/src/github.com/cockroachdb/cockroach/pkg/roachprod/install/cockroach.go:121 \| \| github.com/cockroachdb/cockroach/pkg/roachprod.Start \| \| /home/agent/work/.go/src/github.com/cockroachdb/cockroach/pkg/roachprod/roachprod.go:573 \| \| main.glob..func9 \| \| /home/agent/work/.go/src/github.com/cockroachdb/cockroach/pkg/cmd/roachprod/main.go:397 \| \| main.wrap.func1 \| \| /home/agent/work/.go/src/github.com/cockroachdb/cockroach/pkg/cmd/roachprod/main.go:65 \| \| github.com/spf13/cobra.(Command).execute \| \| /home/agent/work/.go/src/github.com/cockroachdb/cockroach/vendor/github.com/spf13/cobra/command.go:856 \| \| github.com/spf13/cobra.(Command).ExecuteC \| \| /home/agent/work/.go/src/github.com/cockroachdb/cockroach/vendor/github.com/spf13/cobra/command.go:960 \| \| github.com/spf13/cobra.(Command).Execute \| \| /home/agent/work/.go/src/github.com/cockroachdb/cockroach/vendor/github.com/spf13/cobra/command.go:897 \| \| main.main \| \| /home/agent/work/.go/src/github.com/cockroachdb/cockroach/pkg/cmd/roachprod/main.go:905 \| \| runtime.main \| \| /usr/local/go/src/runtime/proc.go:255 \| \| runtime.goexit \| \| /usr/local/go/src/runtime/asm_amd64.s:1581 \| Wraps: (3) one or more parallel execution failure \| Error types: (1) errors.Unclassified (2) withstack.withStack (3) errutil.leafError Wraps: (2) exit status 1 Error types: (1) cluster.WithCommandDetails (2) exec.ExitError ``` <details><summary>Help</summary> <p> See: [roachtest README](https://github.com/cockroachdb/cockroach/blob/master/pkg/cmd/roachtest/README.md) See: [How To Investigate $internal$](https://cockroachlabs.atlassian.net/l/c/SSSBr8c7) </p> </details> <details><summary>Same failure on other branches</summary> <p> - #72867 roachtest: kv/multi-store-with-overload failed [perm denied] [C-test-failure O-roachtest O-robot branch-release-21.2] </p> </details> /cc @cockroachdb/kv-triage <sub> [This test on roachdash](https://roachdash.crdb.dev/?filter=status:open%20t:.kv/multi-store-with-overload.&sort=title+created&display=lastcommented+project) \| [Improve this report!](https://github.com/cockroachdb/cockroach/tree/master/pkg/cmd/internal/issues) </sub>	non_priority	roachtest kv multi store with overload failed roachtest kv multi store with overload with on master stdout teamcity starting nodes cockroach sh exit status attached stack trace stack trace github com cockroachdb cockroach pkg roachprod install syncedcluster startnode home agent work go src github com cockroachdb cockroach pkg roachprod install cockroach go github com cockroachdb cockroach pkg roachprod install syncedcluster start home agent work go src github com cockroachdb cockroach pkg roachprod install cockroach go github com cockroachdb cockroach pkg roachprod install syncedcluster parallele home agent work go src github com cockroachdb cockroach pkg roachprod install cluster synced go runtime goexit usr local go src runtime asm s wraps cockroach sh for cockroach service failed because the control process exited with error code systemctl status cockroach service and journalctl xe for details wraps exit status error types withstack withstack errutil withprefix exec exiterror error unclassified problem one or more parallel execution failure unclassified problem wraps attached stack trace stack trace github com cockroachdb cockroach pkg roachprod install syncedcluster parallele home agent work go src github com cockroachdb cockroach pkg roachprod install cluster synced go github com cockroachdb cockroach pkg roachprod install syncedcluster parallel home agent work go src github com cockroachdb cockroach pkg roachprod install cluster synced go github com cockroachdb cockroach pkg roachprod install syncedcluster start home agent work go src github com cockroachdb cockroach pkg roachprod install cockroach go github com cockroachdb cockroach pkg roachprod start home agent work go src github com cockroachdb cockroach pkg roachprod roachprod go main glob home agent work go src github com cockroachdb cockroach pkg cmd roachprod main go main wrap home agent work go src github com cockroachdb cockroach pkg cmd roachprod main go github com cobra command execute home agent work go src github com cockroachdb cockroach vendor github com cobra command go github com cobra command executec home agent work go src github com cockroachdb cockroach vendor github com cobra command go github com cobra command execute home agent work go src github com cockroachdb cockroach vendor github com cobra command go main main home agent work go src github com cockroachdb cockroach pkg cmd roachprod main go runtime main usr local go src runtime proc go runtime goexit usr local go src runtime asm s wraps one or more parallel execution failure error types errors unclassified withstack withstack errutil leaferror wraps exit status error types cluster withcommanddetails exec exiterror help see see same failure on other branches roachtest kv multi store with overload failed cc cockroachdb kv triage
368,641	25,801,279,445	IssuesEvent	2022-12-11 02:03:27	external-secrets/external-secrets	https://api.github.com/repos/external-secrets/external-secrets	closed	Documentation does not state that CreationPolicy=Owner setting ownerReference field	good first issue area/documentation Stale	Describe the solution you'd like Update the creationPolicy=Merge (or create a new policy) that also sets the `ownerReference` on the managed secret. What is the added value? This would be useful for bootstrapping the `Secret` used by a `SecretStore`, and having external-secrets automatically syncronise changes to the secret after the initial secret creation. This is possible with the Merge strategy already, however my GitOps tooling (argocd) is attempting to self-heal (converge on declared state) and clean up the secret as without the `ownerReference` metadata it does not understand the `Secret`s relationship to the `ExternalSecret` resource. Give us examples of the outcome I think this could be achieved by extending the check in the `mutationFunc` in `pkg/controllers/externalsecret/externalsecret_controller.go` to also set apply owner fields for the merge creationPolicy. Observations (Constraints, Context, etc): The initial secret is being created directly with `kubectl create secret generic ...`.	1.0	Documentation does not state that CreationPolicy=Owner setting ownerReference field - Describe the solution you'd like Update the creationPolicy=Merge (or create a new policy) that also sets the `ownerReference` on the managed secret. What is the added value? This would be useful for bootstrapping the `Secret` used by a `SecretStore`, and having external-secrets automatically syncronise changes to the secret after the initial secret creation. This is possible with the Merge strategy already, however my GitOps tooling (argocd) is attempting to self-heal (converge on declared state) and clean up the secret as without the `ownerReference` metadata it does not understand the `Secret`s relationship to the `ExternalSecret` resource. Give us examples of the outcome I think this could be achieved by extending the check in the `mutationFunc` in `pkg/controllers/externalsecret/externalsecret_controller.go` to also set apply owner fields for the merge creationPolicy. Observations (Constraints, Context, etc): The initial secret is being created directly with `kubectl create secret generic ...`.	non_priority	documentation does not state that creationpolicy owner setting ownerreference field describe the solution you d like update the creationpolicy merge or create a new policy that also sets the ownerreference on the managed secret what is the added value this would be useful for bootstrapping the secret used by a secretstore and having external secrets automatically syncronise changes to the secret after the initial secret creation this is possible with the merge strategy already however my gitops tooling argocd is attempting to self heal converge on declared state and clean up the secret as without the ownerreference metadata it does not understand the secret s relationship to the externalsecret resource give us examples of the outcome i think this could be achieved by extending the check in the mutationfunc in pkg controllers externalsecret externalsecret controller go to also set apply owner fields for the merge creationpolicy observations constraints context etc the initial secret is being created directly with kubectl create secret generic
125,718	10,350,528,324	IssuesEvent	2019-09-05 03:10:50	bskinn/stdio-mgr	https://api.github.com/repos/bskinn/stdio-mgr	reopened	Testing against console libraries	needs tests	colorama < 0.4 is incompatible, as its `StreamWrapper` only gained context manager features in 0.4 https://github.com/tartley/colorama/commit/2f4b564a6586709db2fed20e5d1f5856b1a482d2 and it pushes instances of its `StreamWrapper` into `sys.std*` We could potentially work around this by detecting and patching its objects, but it probably isnt worth the effort. coala was forced to use < 0.4 because of `radon`, but they have bumped their min dependency, so we will too. Not many projects will be still wanting colorama < 0.4. So this is probably best addressed with documentation of knownn incompatibilities. However, it would be worth checking out other console libraries, and creating tests for each.	1.0	Testing against console libraries - colorama < 0.4 is incompatible, as its `StreamWrapper` only gained context manager features in 0.4 https://github.com/tartley/colorama/commit/2f4b564a6586709db2fed20e5d1f5856b1a482d2 and it pushes instances of its `StreamWrapper` into `sys.std*` We could potentially work around this by detecting and patching its objects, but it probably isnt worth the effort. coala was forced to use < 0.4 because of `radon`, but they have bumped their min dependency, so we will too. Not many projects will be still wanting colorama < 0.4. So this is probably best addressed with documentation of knownn incompatibilities. However, it would be worth checking out other console libraries, and creating tests for each.	non_priority	testing against console libraries colorama is incompatible as its streamwrapper only gained context manager features in and it pushes instances of its streamwrapper into sys std we could potentially work around this by detecting and patching its objects but it probably isnt worth the effort coala was forced to use because of radon but they have bumped their min dependency so we will too not many projects will be still wanting colorama so this is probably best addressed with documentation of knownn incompatibilities however it would be worth checking out other console libraries and creating tests for each
50,734	13,572,597,253	IssuesEvent	2020-09-19 01:02:02	jtimberlake/jazz	https://api.github.com/repos/jtimberlake/jazz	opened	CVE-2020-24750 (High) detected in jackson-databind-2.9.10.4.jar	security vulnerability	## CVE-2020-24750 - 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.4.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: jazz/templates/function-template-java/pom.xml</p> <p>Path to vulnerable library: canner/.m2/repository/com/fasterxml/jackson/core/jackson-databind/2.9.10.4/jackson-databind-2.9.10.4.jar,canner/.m2/repository/com/fasterxml/jackson/core/jackson-databind/2.9.10.4/jackson-databind-2.9.10.4.jar,canner/.m2/repository/com/fasterxml/jackson/core/jackson-databind/2.9.10.4/jackson-databind-2.9.10.4.jar</p> <p> Dependency Hierarchy: - :x: jackson-databind-2.9.10.4.jar (Vulnerable Library) </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary> <p> FasterXML jackson-databind 2.x before 2.9.10.6 mishandles the interaction between serialization gadgets and typing, related to com.pastdev.httpcomponents.configuration.JndiConfiguration. <p>Publish Date: 2020-08-28 <p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-24750>CVE-2020-24750</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://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-24616">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-24616</a></p> <p>Release Date: 2020-08-28</p> <p>Fix Resolution: com.fasterxml.jackson.core:jackson-databind:2.9.10.6</p> </p> </details> <p></p> *** :rescue_worker_helmet: Automatic Remediation is available for this issue <!-- <REMEDIATE>{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"Java","groupId":"com.fasterxml.jackson.core","packageName":"jackson-databind","packageVersion":"2.9.10.4","isTransitiveDependency":false,"dependencyTree":"com.fasterxml.jackson.core:jackson-databind:2.9.10.4","isMinimumFixVersionAvailable":true,"minimumFixVersion":"com.fasterxml.jackson.core:jackson-databind:2.9.10.6"}],"vulnerabilityIdentifier":"CVE-2020-24750","vulnerabilityDetails":"FasterXML jackson-databind 2.x before 2.9.10.6 mishandles the interaction between serialization gadgets and typing, related to com.pastdev.httpcomponents.configuration.JndiConfiguration.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-24750","cvss3Severity":"high","cvss3Score":"8.1","cvss3Metrics":{"A":"High","AC":"High","PR":"None","S":"Unchanged","C":"High","UI":"None","AV":"Network","I":"High"},"extraData":{}}</REMEDIATE> -->	True	CVE-2020-24750 (High) detected in jackson-databind-2.9.10.4.jar - ## CVE-2020-24750 - 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.4.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: jazz/templates/function-template-java/pom.xml</p> <p>Path to vulnerable library: canner/.m2/repository/com/fasterxml/jackson/core/jackson-databind/2.9.10.4/jackson-databind-2.9.10.4.jar,canner/.m2/repository/com/fasterxml/jackson/core/jackson-databind/2.9.10.4/jackson-databind-2.9.10.4.jar,canner/.m2/repository/com/fasterxml/jackson/core/jackson-databind/2.9.10.4/jackson-databind-2.9.10.4.jar</p> <p> Dependency Hierarchy: - :x: jackson-databind-2.9.10.4.jar (Vulnerable Library) </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary> <p> FasterXML jackson-databind 2.x before 2.9.10.6 mishandles the interaction between serialization gadgets and typing, related to com.pastdev.httpcomponents.configuration.JndiConfiguration. <p>Publish Date: 2020-08-28 <p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-24750>CVE-2020-24750</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://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-24616">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-24616</a></p> <p>Release Date: 2020-08-28</p> <p>Fix Resolution: com.fasterxml.jackson.core:jackson-databind:2.9.10.6</p> </p> </details> <p></p> *** :rescue_worker_helmet: Automatic Remediation is available for this issue <!-- <REMEDIATE>{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"Java","groupId":"com.fasterxml.jackson.core","packageName":"jackson-databind","packageVersion":"2.9.10.4","isTransitiveDependency":false,"dependencyTree":"com.fasterxml.jackson.core:jackson-databind:2.9.10.4","isMinimumFixVersionAvailable":true,"minimumFixVersion":"com.fasterxml.jackson.core:jackson-databind:2.9.10.6"}],"vulnerabilityIdentifier":"CVE-2020-24750","vulnerabilityDetails":"FasterXML jackson-databind 2.x before 2.9.10.6 mishandles the interaction between serialization gadgets and typing, related to com.pastdev.httpcomponents.configuration.JndiConfiguration.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-24750","cvss3Severity":"high","cvss3Score":"8.1","cvss3Metrics":{"A":"High","AC":"High","PR":"None","S":"Unchanged","C":"High","UI":"None","AV":"Network","I":"High"},"extraData":{}}</REMEDIATE> -->	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 jazz templates function template java pom xml path to vulnerable library canner repository com fasterxml jackson core jackson databind jackson databind jar canner repository com fasterxml jackson core jackson databind jackson databind jar canner repository com fasterxml jackson core jackson databind jackson databind jar dependency hierarchy x jackson databind jar vulnerable library vulnerability details fasterxml jackson databind x before mishandles the interaction between serialization gadgets and typing related to com pastdev httpcomponents configuration jndiconfiguration 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 rescue worker helmet automatic remediation is available for this issue isopenpronvulnerability true ispackagebased true isdefaultbranch true packages vulnerabilityidentifier cve vulnerabilitydetails fasterxml jackson databind x before mishandles the interaction between serialization gadgets and typing related to com pastdev httpcomponents configuration jndiconfiguration vulnerabilityurl
47,240	7,311,619,189	IssuesEvent	2018-02-28 18:20:42	blackbaud/stache2	https://api.github.com/repos/blackbaud/stache2	closed	Documentation on how to set the navigation	bug documentation groomed	We don't have any documentation on how to update the navigation, aside from putting `<app-nav>` on every page (which is about to change). We should document how to adjust the navigation whether you're using the old omnibar or new one.	1.0	Documentation on how to set the navigation - We don't have any documentation on how to update the navigation, aside from putting `<app-nav>` on every page (which is about to change). We should document how to adjust the navigation whether you're using the old omnibar or new one.	non_priority	documentation on how to set the navigation we don t have any documentation on how to update the navigation aside from putting on every page which is about to change we should document how to adjust the navigation whether you re using the old omnibar or new one
45,774	13,132,612,755	IssuesEvent	2020-08-06 19:15:20	RG4421/LunchLearningApp	https://api.github.com/repos/RG4421/LunchLearningApp	opened	CVE-2018-16487 (Medium) detected in lodash-3.10.1.tgz	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-3.10.1.tgz</b></p></summary> <p>The modern build of lodash modular utilities.</p> <p>Library home page: <a href="https://registry.npmjs.org/lodash/-/lodash-3.10.1.tgz">https://registry.npmjs.org/lodash/-/lodash-3.10.1.tgz</a></p> <p>Path to dependency file: /tmp/ws-scm/LunchLearningApp/LunchAndLearnWebUI/package.json</p> <p>Path to vulnerable library: /tmp/ws-scm/LunchLearningApp/LunchAndLearnWebUI/node_modules/karma/node_modules/lodash/package.json</p> <p> Dependency Hierarchy: - karma-1.7.1.tgz (Root Library) - :x: lodash-3.10.1.tgz (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/RG4421/LunchLearningApp/commit/dabd2522ce385cf3e53e00b24a0b6eb174caab1c">dabd2522ce385cf3e53e00b24a0b6eb174caab1c</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> 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":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"lodash","packageVersion":"3.10.1","isTransitiveDependency":true,"dependencyTree":"karma:1.7.1;lodash:3.10.1","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-3.10.1.tgz - ## 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-3.10.1.tgz</b></p></summary> <p>The modern build of lodash modular utilities.</p> <p>Library home page: <a href="https://registry.npmjs.org/lodash/-/lodash-3.10.1.tgz">https://registry.npmjs.org/lodash/-/lodash-3.10.1.tgz</a></p> <p>Path to dependency file: /tmp/ws-scm/LunchLearningApp/LunchAndLearnWebUI/package.json</p> <p>Path to vulnerable library: /tmp/ws-scm/LunchLearningApp/LunchAndLearnWebUI/node_modules/karma/node_modules/lodash/package.json</p> <p> Dependency Hierarchy: - karma-1.7.1.tgz (Root Library) - :x: lodash-3.10.1.tgz (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/RG4421/LunchLearningApp/commit/dabd2522ce385cf3e53e00b24a0b6eb174caab1c">dabd2522ce385cf3e53e00b24a0b6eb174caab1c</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> 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":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"lodash","packageVersion":"3.10.1","isTransitiveDependency":true,"dependencyTree":"karma:1.7.1;lodash:3.10.1","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 tgz cve medium severity vulnerability vulnerable library lodash tgz the modern build of lodash modular utilities library home page a href path to dependency file tmp ws scm lunchlearningapp lunchandlearnwebui package json path to vulnerable library tmp ws scm lunchlearningapp lunchandlearnwebui node modules karma node modules lodash package json dependency hierarchy karma tgz root library x lodash tgz vulnerable library found in head commit a href 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 true 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
174,085	13,456,029,568	IssuesEvent	2020-09-09 07:14:10	elastic/elasticsearch	https://api.github.com/repos/elastic/elasticsearch	closed	SqlClearCursorActionIT.testAutoCursorCleanup failure	:Query Languages/SQL >test-failure Team:QL	Build scan: https://gradle-enterprise.elastic.co/s/vww2nhtqvllnq Repro line: ``` ./gradlew ':x-pack:plugin:sql:internalClusterTest' --tests "org.elasticsearch.xpack.sql.action.SqlClearCursorActionIT.testAutoCursorCleanup" \ -Dtests.seed=ED48C0414093BFA8 \ -Dtests.security.manager=true \ -Dtests.locale=de \ -Dtests.timezone=America/Campo_Grande \ -Druntime.java=11 ``` Reproduces locally?: No Applicable branches: master Failure history: First ever failure I could find at least. I have not muted the test because this is the first failure and it does not reproduce Failure excerpt: ``` java.lang.AssertionError: expected:<0> but was:<1> at __randomizedtesting.SeedInfo.seed([ED48C0414093BFA8:2A4953187A7F7CBA]:0) at org.junit.Assert.fail(Assert.java:88) at org.junit.Assert.failNotEquals(Assert.java:834) at org.junit.Assert.assertEquals(Assert.java:645) at org.junit.Assert.assertEquals(Assert.java:631) at org.elasticsearch.xpack.sql.action.SqlClearCursorActionIT.testAutoCursorCleanup(SqlClearCursorActionIT.java:85) ```	1.0	SqlClearCursorActionIT.testAutoCursorCleanup failure - Build scan: https://gradle-enterprise.elastic.co/s/vww2nhtqvllnq Repro line: ``` ./gradlew ':x-pack:plugin:sql:internalClusterTest' --tests "org.elasticsearch.xpack.sql.action.SqlClearCursorActionIT.testAutoCursorCleanup" \ -Dtests.seed=ED48C0414093BFA8 \ -Dtests.security.manager=true \ -Dtests.locale=de \ -Dtests.timezone=America/Campo_Grande \ -Druntime.java=11 ``` Reproduces locally?: No Applicable branches: master Failure history: First ever failure I could find at least. I have not muted the test because this is the first failure and it does not reproduce Failure excerpt: ``` java.lang.AssertionError: expected:<0> but was:<1> at __randomizedtesting.SeedInfo.seed([ED48C0414093BFA8:2A4953187A7F7CBA]:0) at org.junit.Assert.fail(Assert.java:88) at org.junit.Assert.failNotEquals(Assert.java:834) at org.junit.Assert.assertEquals(Assert.java:645) at org.junit.Assert.assertEquals(Assert.java:631) at org.elasticsearch.xpack.sql.action.SqlClearCursorActionIT.testAutoCursorCleanup(SqlClearCursorActionIT.java:85) ```	non_priority	sqlclearcursoractionit testautocursorcleanup failure build scan repro line gradlew x pack plugin sql internalclustertest tests org elasticsearch xpack sql action sqlclearcursoractionit testautocursorcleanup dtests seed dtests security manager true dtests locale de dtests timezone america campo grande druntime java reproduces locally no applicable branches master failure history first ever failure i could find at least i have not muted the test because this is the first failure and it does not reproduce failure excerpt java lang assertionerror expected but was at randomizedtesting seedinfo seed at org junit assert fail assert java at org junit assert failnotequals assert java at org junit assert assertequals assert java at org junit assert assertequals assert java at org elasticsearch xpack sql action sqlclearcursoractionit testautocursorcleanup sqlclearcursoractionit java
134,507	12,609,219,939	IssuesEvent	2020-06-12 00:53:32	GTFB/Altrp	https://api.github.com/repos/GTFB/Altrp	closed	wysiwyg контроллер	documentation editor	вот здесь контроллеры ![изображение](https://user-images.githubusercontent.com/23271651/83797190-e8497200-a6aa-11ea-858a-ba835c49eaef.png) подключение wysiwyg редактора асинхронное брать библиотеку с минимум 1к звезд	1.0	wysiwyg контроллер - вот здесь контроллеры ![изображение](https://user-images.githubusercontent.com/23271651/83797190-e8497200-a6aa-11ea-858a-ba835c49eaef.png) подключение wysiwyg редактора асинхронное брать библиотеку с минимум 1к звезд	non_priority	wysiwyg контроллер вот здесь контроллеры подключение wysiwyg редактора асинхронное брать библиотеку с минимум звезд
15,719	10,340,359,747	IssuesEvent	2019-09-03 21:43:57	cityofaustin/atd-knack-signs-markings	https://api.github.com/repos/cityofaustin/atd-knack-signs-markings	reopened	Signs Work Orders: Hide Lat/Lon Fields	Need: 2-Should Have Service: Dev Type: Enhancement Workgroup: SMB	There's not much screen real estate when viewing signs work orders on a tablet. Hide the lat/lon fields from the embedded map on the Sign Work Order Details. ![Screen Shot 2019-08-28 at 10.29.05 PM.png](https://images.zenhubusercontent.com/5caf676becad11531cc417cb/ecad3d1c-6277-4d4a-84f8-866e6cfc5b73) - [x] Hide the `Latitude` and `Longitude` fields on the map - [x] Make the `Add Location` button larger` #208	1.0	Signs Work Orders: Hide Lat/Lon Fields - There's not much screen real estate when viewing signs work orders on a tablet. Hide the lat/lon fields from the embedded map on the Sign Work Order Details. ![Screen Shot 2019-08-28 at 10.29.05 PM.png](https://images.zenhubusercontent.com/5caf676becad11531cc417cb/ecad3d1c-6277-4d4a-84f8-866e6cfc5b73) - [x] Hide the `Latitude` and `Longitude` fields on the map - [x] Make the `Add Location` button larger` #208	non_priority	signs work orders hide lat lon fields there s not much screen real estate when viewing signs work orders on a tablet hide the lat lon fields from the embedded map on the sign work order details hide the latitude and longitude fields on the map make the add location button larger

Subsets and Splits

No community queries yet

The top public SQL queries from the community will appear here once available.