Unnamed: 0 int64 0 832k | id float64 2.49B 32.1B | type stringclasses 1 value | created_at stringlengths 19 19 | repo stringlengths 5 112 | repo_url stringlengths 34 141 | action stringclasses 3 values | title stringlengths 1 844 | labels stringlengths 4 721 | body stringlengths 1 261k | index stringclasses 12 values | text_combine stringlengths 96 261k | label stringclasses 2 values | text stringlengths 96 248k | binary_label int64 0 1 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
128,227 | 12,367,611,326 | IssuesEvent | 2020-05-18 12:34:31 | lxndrblz/anatole | https://api.github.com/repos/lxndrblz/anatole | closed | Replace screenshots in documentation | documentation | The screenshots in the images folder are showing a dated version of the theme. Those should be replaced with the most current one. | 1.0 | Replace screenshots in documentation - The screenshots in the images folder are showing a dated version of the theme. Those should be replaced with the most current one. | non_priority | replace screenshots in documentation the screenshots in the images folder are showing a dated version of the theme those should be replaced with the most current one | 0 |
79,763 | 9,942,199,706 | IssuesEvent | 2019-07-03 13:24:53 | alpheios-project/alpheios_nemo_ui | https://api.github.com/repos/alpheios-project/alpheios_nemo_ui | closed | drop the navlogin on the desktop | design | @abrasax has requested that we drop the extra white banner on the texts page on the desktop and use the same banner as we have on mobile right now on the desktop as well. | 1.0 | drop the navlogin on the desktop - @abrasax has requested that we drop the extra white banner on the texts page on the desktop and use the same banner as we have on mobile right now on the desktop as well. | non_priority | drop the navlogin on the desktop abrasax has requested that we drop the extra white banner on the texts page on the desktop and use the same banner as we have on mobile right now on the desktop as well | 0 |
73,210 | 24,507,593,086 | IssuesEvent | 2022-10-10 17:53:54 | zed-industries/feedback | https://api.github.com/repos/zed-industries/feedback | opened | Ctrl + \` increases the character count | defect triage | ### Check for existing issues
- [X] Completed
### Describe the bug / provide steps to reproduce it
Typing `` Ctrl + ` `` in the editor increases the character count (or moves the internal cursor position) while visually no character appears on the screen.
In the attached screenshot I pressed the combination 30 times, and each time the count increased by 1.
This could be related to #563 , since the key combination should be the one that opens the Terminal.
### Expected behavior
Either some character should appear or the character count should not increase (or the cursor should not move).
### Environment
```
Zed 0.59.0 – /Applications/Zed.app
macOS 12.5.1
architecture arm64
```
### If applicable, add mockups / screenshots to help explain present your vision of the feature
### If applicable, attach your `~/Library/Logs/Zed/Zed.log` file to this issue
_No response_ | 1.0 | Ctrl + \` increases the character count - ### Check for existing issues
- [X] Completed
### Describe the bug / provide steps to reproduce it
Typing `` Ctrl + ` `` in the editor increases the character count (or moves the internal cursor position) while visually no character appears on the screen.
In the attached screenshot I pressed the combination 30 times, and each time the count increased by 1.
This could be related to #563 , since the key combination should be the one that opens the Terminal.
### Expected behavior
Either some character should appear or the character count should not increase (or the cursor should not move).
### Environment
```
Zed 0.59.0 – /Applications/Zed.app
macOS 12.5.1
architecture arm64
```
### If applicable, add mockups / screenshots to help explain present your vision of the feature
### If applicable, attach your `~/Library/Logs/Zed/Zed.log` file to this issue
_No response_ | non_priority | ctrl increases the character count check for existing issues completed describe the bug provide steps to reproduce it typing ctrl in the editor increases the character count or moves the internal cursor position while visually no character appears on the screen in the attached screenshot i pressed the combination times and each time the count increased by this could be related to since the key combination should be the one that opens the terminal expected behavior either some character should appear or the character count should not increase or the cursor should not move environment zed – applications zed app macos architecture if applicable add mockups screenshots to help explain present your vision of the feature if applicable attach your library logs zed zed log file to this issue no response | 0 |
237,433 | 19,634,093,035 | IssuesEvent | 2022-01-08 01:26:52 | Azure/azure-sdk-for-js | https://api.github.com/repos/Azure/azure-sdk-for-js | closed | [Metrics Advisor] [AAD] MetricsAdvisorClient Feedback creates ChangePoint feedback failing in nightly runs | Client test-reliability Cognitive - Metrics Advisor | Metrics Advisor nightly test runs are failing with:
> Error message:
>{"code":"BadRequest","message":null}
>
> Stack trace:
>RestError: {"code":"BadRequest","message":null}
at handleErrorResponse (/Users/runner/work/1/s/sdk/core/core-http/src/policies/deserializationPolicy.ts:274:17)
at /Users/runner/work/1/s/sdk/core/core-http/src/policies/deserializationPolicy.ts:179:47
at processTicksAndRejections (node:internal/process/task_queues:96:5)
at GeneratedClient.sendOperationRequest (/Users/runner/work/1/s/sdk/core/core-http/src/serviceClient.ts:521:23)
at MetricsAdvisorClient.addFeedback (/Users/runner/work/1/s/sdk/metricsadvisor/ai-metrics-advisor/dist-esm/src/metricsAdvisorClient.js:415:485)
at Context.<anonymous> (/Users/runner/work/1/s/sdk/metricsadvisor/ai-metrics-advisor/test/public/advisorclient.spec.ts:550:26)
For more details check here:
- https://dev.azure.com/azure-sdk/internal/_build/results?buildId=1263094&view=results | 1.0 | [Metrics Advisor] [AAD] MetricsAdvisorClient Feedback creates ChangePoint feedback failing in nightly runs - Metrics Advisor nightly test runs are failing with:
> Error message:
>{"code":"BadRequest","message":null}
>
> Stack trace:
>RestError: {"code":"BadRequest","message":null}
at handleErrorResponse (/Users/runner/work/1/s/sdk/core/core-http/src/policies/deserializationPolicy.ts:274:17)
at /Users/runner/work/1/s/sdk/core/core-http/src/policies/deserializationPolicy.ts:179:47
at processTicksAndRejections (node:internal/process/task_queues:96:5)
at GeneratedClient.sendOperationRequest (/Users/runner/work/1/s/sdk/core/core-http/src/serviceClient.ts:521:23)
at MetricsAdvisorClient.addFeedback (/Users/runner/work/1/s/sdk/metricsadvisor/ai-metrics-advisor/dist-esm/src/metricsAdvisorClient.js:415:485)
at Context.<anonymous> (/Users/runner/work/1/s/sdk/metricsadvisor/ai-metrics-advisor/test/public/advisorclient.spec.ts:550:26)
For more details check here:
- https://dev.azure.com/azure-sdk/internal/_build/results?buildId=1263094&view=results | non_priority | metricsadvisorclient feedback creates changepoint feedback failing in nightly runs metrics advisor nightly test runs are failing with error message code badrequest message null stack trace resterror code badrequest message null at handleerrorresponse users runner work s sdk core core http src policies deserializationpolicy ts at users runner work s sdk core core http src policies deserializationpolicy ts at processticksandrejections node internal process task queues at generatedclient sendoperationrequest users runner work s sdk core core http src serviceclient ts at metricsadvisorclient addfeedback users runner work s sdk metricsadvisor ai metrics advisor dist esm src metricsadvisorclient js at context users runner work s sdk metricsadvisor ai metrics advisor test public advisorclient spec ts for more details check here | 0 |
25,819 | 7,751,479,859 | IssuesEvent | 2018-05-30 17:11:33 | scalacenter/scalafix | https://api.github.com/repos/scalacenter/scalafix | closed | testkit cannot be resolved | bug build | The scalafix.g8 template CI failed because testkit cannot be resolved anymore due to its dependency on test-utils
```
$ coursier fetch ch.epfl.scala:scalafix-testkit_2.12.4:0.6.0-M1
Error:
ch.epfl.scala:scalafix-test-utils_2.12:0.6.0-M1
not found: /Users/ollie/.ivy2/local/ch.epfl.scala/scalafix-test-utils_2.12/0.6.0-M1/ivys/ivy.xml
not found: https://repo1.maven.org/maven2/ch/epfl/scala/scalafix-test-utils_2.12/0.6.0-M1/scalafix-test-utils_2.12-0.6.0-M1.pom
```
https://travis-ci.org/scalacenter/scalafix.g8/builds/341912036?utm_source=email&utm_medium=notification
Can we either publish test-utils or drop the dependency on test-utils in testkit? Alternatively, can we inline test-utils into testkit if we want to make it part of the public API? | 1.0 | testkit cannot be resolved - The scalafix.g8 template CI failed because testkit cannot be resolved anymore due to its dependency on test-utils
```
$ coursier fetch ch.epfl.scala:scalafix-testkit_2.12.4:0.6.0-M1
Error:
ch.epfl.scala:scalafix-test-utils_2.12:0.6.0-M1
not found: /Users/ollie/.ivy2/local/ch.epfl.scala/scalafix-test-utils_2.12/0.6.0-M1/ivys/ivy.xml
not found: https://repo1.maven.org/maven2/ch/epfl/scala/scalafix-test-utils_2.12/0.6.0-M1/scalafix-test-utils_2.12-0.6.0-M1.pom
```
https://travis-ci.org/scalacenter/scalafix.g8/builds/341912036?utm_source=email&utm_medium=notification
Can we either publish test-utils or drop the dependency on test-utils in testkit? Alternatively, can we inline test-utils into testkit if we want to make it part of the public API? | non_priority | testkit cannot be resolved the scalafix template ci failed because testkit cannot be resolved anymore due to its dependency on test utils coursier fetch ch epfl scala scalafix testkit error ch epfl scala scalafix test utils not found users ollie local ch epfl scala scalafix test utils ivys ivy xml not found can we either publish test utils or drop the dependency on test utils in testkit alternatively can we inline test utils into testkit if we want to make it part of the public api | 0 |
114,586 | 24,623,496,196 | IssuesEvent | 2022-10-16 07:53:41 | alexeygrigorev/mlbookcamp-code | https://api.github.com/repos/alexeygrigorev/mlbookcamp-code | opened | Timecodes for "ML Zoomcamp 7.2 - Building Your Prediction Service with BentoML" | timecodes | Youtube video: https://www.youtube.com/watch?v=bWdEVlUw1CA | 1.0 | Timecodes for "ML Zoomcamp 7.2 - Building Your Prediction Service with BentoML" - Youtube video: https://www.youtube.com/watch?v=bWdEVlUw1CA | non_priority | timecodes for ml zoomcamp building your prediction service with bentoml youtube video | 0 |
203,987 | 15,396,702,723 | IssuesEvent | 2021-03-03 21:01:38 | zowe/zowe-cli | https://api.github.com/repos/zowe/zowe-cli | closed | Generalize provisioning automated tests to be system-independent | testing | _From @ChrisBoehmCA on September 6, 2018 12:26_
Currently the provisioning tests only pass on a certain system that has been pre-configured with a provisioning workflow. It would be ideal to be able to run these tests on any system
Maybe we could store the workflow XML in the test resources directory and call the z/OSMF REST APIs to define the workflow, then delete it at the end of the tests so that it could be run on any system?
_Copied from original issue: gizafoundation/brightside#233_ | 1.0 | Generalize provisioning automated tests to be system-independent - _From @ChrisBoehmCA on September 6, 2018 12:26_
Currently the provisioning tests only pass on a certain system that has been pre-configured with a provisioning workflow. It would be ideal to be able to run these tests on any system
Maybe we could store the workflow XML in the test resources directory and call the z/OSMF REST APIs to define the workflow, then delete it at the end of the tests so that it could be run on any system?
_Copied from original issue: gizafoundation/brightside#233_ | non_priority | generalize provisioning automated tests to be system independent from chrisboehmca on september currently the provisioning tests only pass on a certain system that has been pre configured with a provisioning workflow it would be ideal to be able to run these tests on any system maybe we could store the workflow xml in the test resources directory and call the z osmf rest apis to define the workflow then delete it at the end of the tests so that it could be run on any system copied from original issue gizafoundation brightside | 0 |
40,796 | 10,164,850,508 | IssuesEvent | 2019-08-07 12:41:41 | primefaces/primefaces | https://api.github.com/repos/primefaces/primefaces | closed | Tree: Wrong dropIndex in AJAX behavior event | defect | ## 1) Environment
- PrimeFaces version: Trunk
- Application server + version: WF 10.1.0.Final
- Affected browsers: IE, FF, ...
## 2) Expected behavior
There are multiple possibilities, where a tree node could be dropped. Either **on** other nodes , which will make them siblings of that node. Or **between** nodes, which will insert the node at that position.
The second case (between) is working correctly. The `dropIndex` has the correct value. But the first case (on) should always either add the node at the beginning or at the end of the drop nodes child list. That means, that the `dropIndex` should either be `0` or `count of child-nodes`
## 3) Actual behavior
The `dropIndex` contains the index from inside the old parent node. This produces different results of the tree based on the child count of the drop node. If the drop node has enough children so that the `dropIndex` is in range, it will be inserted at the same index it previously had in the old parent node. Otherwise it will be appended to the end.
But the AJAX behaviour event will always report the original index, event if the node was appended instead of inserted. You have to manually adjust that value. That is not a good idea because you have to know the implementation logic of the tree renderer and that may change at any time which may cause bugs.
## 4) Steps to reproduce
- Setup a tree with multple nodes and child nodes and an AJAX behavior event for drag'n'drop.
- Move one node to an other one, the dropIndex of the event is always the index from inside the parent. Not from the drop node.
## 5) Sample XHTML
Will be provided if really needed
## 6) Sample bean
Will be povided if really needed
## 7) Possible fix
Always append the dragged node to end of the drop node children. For the correct index, change the line `dndIndex = targetDragNode.prevAll('li.ui-treenode').length;` to `dndIndex = dropNode.find('>.ui-treenode-children>li.ui-treenode').length;`
(the image contains some debug output, that could be ignored)
| 1.0 | Tree: Wrong dropIndex in AJAX behavior event - ## 1) Environment
- PrimeFaces version: Trunk
- Application server + version: WF 10.1.0.Final
- Affected browsers: IE, FF, ...
## 2) Expected behavior
There are multiple possibilities, where a tree node could be dropped. Either **on** other nodes , which will make them siblings of that node. Or **between** nodes, which will insert the node at that position.
The second case (between) is working correctly. The `dropIndex` has the correct value. But the first case (on) should always either add the node at the beginning or at the end of the drop nodes child list. That means, that the `dropIndex` should either be `0` or `count of child-nodes`
## 3) Actual behavior
The `dropIndex` contains the index from inside the old parent node. This produces different results of the tree based on the child count of the drop node. If the drop node has enough children so that the `dropIndex` is in range, it will be inserted at the same index it previously had in the old parent node. Otherwise it will be appended to the end.
But the AJAX behaviour event will always report the original index, event if the node was appended instead of inserted. You have to manually adjust that value. That is not a good idea because you have to know the implementation logic of the tree renderer and that may change at any time which may cause bugs.
## 4) Steps to reproduce
- Setup a tree with multple nodes and child nodes and an AJAX behavior event for drag'n'drop.
- Move one node to an other one, the dropIndex of the event is always the index from inside the parent. Not from the drop node.
## 5) Sample XHTML
Will be provided if really needed
## 6) Sample bean
Will be povided if really needed
## 7) Possible fix
Always append the dragged node to end of the drop node children. For the correct index, change the line `dndIndex = targetDragNode.prevAll('li.ui-treenode').length;` to `dndIndex = dropNode.find('>.ui-treenode-children>li.ui-treenode').length;`
(the image contains some debug output, that could be ignored)
| non_priority | tree wrong dropindex in ajax behavior event environment primefaces version trunk application server version wf final affected browsers ie ff expected behavior there are multiple possibilities where a tree node could be dropped either on other nodes which will make them siblings of that node or between nodes which will insert the node at that position the second case between is working correctly the dropindex has the correct value but the first case on should always either add the node at the beginning or at the end of the drop nodes child list that means that the dropindex should either be or count of child nodes actual behavior the dropindex contains the index from inside the old parent node this produces different results of the tree based on the child count of the drop node if the drop node has enough children so that the dropindex is in range it will be inserted at the same index it previously had in the old parent node otherwise it will be appended to the end but the ajax behaviour event will always report the original index event if the node was appended instead of inserted you have to manually adjust that value that is not a good idea because you have to know the implementation logic of the tree renderer and that may change at any time which may cause bugs steps to reproduce setup a tree with multple nodes and child nodes and an ajax behavior event for drag n drop move one node to an other one the dropindex of the event is always the index from inside the parent not from the drop node sample xhtml will be provided if really needed sample bean will be povided if really needed possible fix always append the dragged node to end of the drop node children for the correct index change the line dndindex targetdragnode prevall li ui treenode length to dndindex dropnode find ui treenode children li ui treenode length the image contains some debug output that could be ignored | 0 |
160,381 | 12,509,930,826 | IssuesEvent | 2020-06-02 17:43:59 | awslabs/s2n | https://api.github.com/repos/awslabs/s2n | closed | Travis builds for Integration Tests failing | type/flaky_test type/integration_test | ## **Problem:**
Travis builds that run integration tests for s2n Client with the endpoint: wikipedia.org using Corked IO is consistently failing.
Ex: [Travis build #626853394](https://travis-ci.org/awslabs/s2n/jobs/626853394?utm_medium=notification&utm_source=github_status)
## **Proposed Solution:**
Investigate the problem and fix the build.
[//]: # (NOTE: If you believe this might be a security issue, please email aws-security@amazon.com instead of creating a GitHub issue. For more details, see the AWS Vulnerability Reporting Guide: https://aws.amazon.com/security/vulnerability-reporting/ )
| 2.0 | Travis builds for Integration Tests failing - ## **Problem:**
Travis builds that run integration tests for s2n Client with the endpoint: wikipedia.org using Corked IO is consistently failing.
Ex: [Travis build #626853394](https://travis-ci.org/awslabs/s2n/jobs/626853394?utm_medium=notification&utm_source=github_status)
## **Proposed Solution:**
Investigate the problem and fix the build.
[//]: # (NOTE: If you believe this might be a security issue, please email aws-security@amazon.com instead of creating a GitHub issue. For more details, see the AWS Vulnerability Reporting Guide: https://aws.amazon.com/security/vulnerability-reporting/ )
| non_priority | travis builds for integration tests failing problem travis builds that run integration tests for client with the endpoint wikipedia org using corked io is consistently failing ex proposed solution investigate the problem and fix the build note if you believe this might be a security issue please email aws security amazon com instead of creating a github issue for more details see the aws vulnerability reporting guide | 0 |
102,639 | 16,576,352,857 | IssuesEvent | 2021-05-31 05:41:21 | AlexRogalskiy/github-action-json-fields | https://api.github.com/repos/AlexRogalskiy/github-action-json-fields | opened | CVE-2021-33502 (High) detected in normalize-url-5.3.0.tgz | security vulnerability | ## CVE-2021-33502 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>normalize-url-5.3.0.tgz</b></p></summary>
<p>Normalize a URL</p>
<p>Library home page: <a href="https://registry.npmjs.org/normalize-url/-/normalize-url-5.3.0.tgz">https://registry.npmjs.org/normalize-url/-/normalize-url-5.3.0.tgz</a></p>
<p>Path to dependency file: github-action-json-fields/package.json</p>
<p>Path to vulnerable library: github-action-json-fields/node_modules/normalize-url/package.json</p>
<p>
Dependency Hierarchy:
- npm-7.0.10.tgz (Root Library)
- :x: **normalize-url-5.3.0.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/AlexRogalskiy/github-action-json-fields/commit/b89d9afd75d508a856f18aa876c1d17a9b47a14e">b89d9afd75d508a856f18aa876c1d17a9b47a14e</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
The normalize-url package before 4.5.1, 5.x before 5.3.1, and 6.x before 6.0.1 for Node.js has a ReDoS (regular expression denial of service) issue because it has exponential performance for data: URLs.
<p>Publish Date: 2021-05-24
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-33502>CVE-2021-33502</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-33502">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-33502</a></p>
<p>Release Date: 2021-05-24</p>
<p>Fix Resolution: normalize-url - 4.5.1, 5.3.1, 6.0.1</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | CVE-2021-33502 (High) detected in normalize-url-5.3.0.tgz - ## CVE-2021-33502 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>normalize-url-5.3.0.tgz</b></p></summary>
<p>Normalize a URL</p>
<p>Library home page: <a href="https://registry.npmjs.org/normalize-url/-/normalize-url-5.3.0.tgz">https://registry.npmjs.org/normalize-url/-/normalize-url-5.3.0.tgz</a></p>
<p>Path to dependency file: github-action-json-fields/package.json</p>
<p>Path to vulnerable library: github-action-json-fields/node_modules/normalize-url/package.json</p>
<p>
Dependency Hierarchy:
- npm-7.0.10.tgz (Root Library)
- :x: **normalize-url-5.3.0.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/AlexRogalskiy/github-action-json-fields/commit/b89d9afd75d508a856f18aa876c1d17a9b47a14e">b89d9afd75d508a856f18aa876c1d17a9b47a14e</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
The normalize-url package before 4.5.1, 5.x before 5.3.1, and 6.x before 6.0.1 for Node.js has a ReDoS (regular expression denial of service) issue because it has exponential performance for data: URLs.
<p>Publish Date: 2021-05-24
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-33502>CVE-2021-33502</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-33502">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-33502</a></p>
<p>Release Date: 2021-05-24</p>
<p>Fix Resolution: normalize-url - 4.5.1, 5.3.1, 6.0.1</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_priority | cve high detected in normalize url tgz cve high severity vulnerability vulnerable library normalize url tgz normalize a url library home page a href path to dependency file github action json fields package json path to vulnerable library github action json fields node modules normalize url package json dependency hierarchy npm tgz root library x normalize url tgz vulnerable library found in head commit a href vulnerability details the normalize url package before x before and x before for node js has a redos regular expression denial of service issue because it has exponential performance for data urls 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 normalize url step up your open source security game with whitesource | 0 |
25,753 | 6,711,591,033 | IssuesEvent | 2017-10-13 05:05:46 | vayamdevindia/Vayam | https://api.github.com/repos/vayamdevindia/Vayam | opened | Create a development setup using npm, bower and grunt | Code | Create a development setup using npm, bower and grunt
- Install following
- Node
- Bower
- Grunt
- Angular 1.6
- Bootstrap 3 - saas
- Create following common tasks with grunt to carry out normal dev work
- Copy lib files from bower dir to other relevant dir
- Compile saas files to css files
- Concat all js files to generate single app.js files
- Listen on file changes and carry out Compilation or cancat work as required.
- Create a project dir structure according to https://scotch.io/tutorials/angularjs-best-practices-directory-structure
- Create initial routing using ng-route and check in some basic page layouts for following
- Home
- Contactus
- About us | 1.0 | Create a development setup using npm, bower and grunt - Create a development setup using npm, bower and grunt
- Install following
- Node
- Bower
- Grunt
- Angular 1.6
- Bootstrap 3 - saas
- Create following common tasks with grunt to carry out normal dev work
- Copy lib files from bower dir to other relevant dir
- Compile saas files to css files
- Concat all js files to generate single app.js files
- Listen on file changes and carry out Compilation or cancat work as required.
- Create a project dir structure according to https://scotch.io/tutorials/angularjs-best-practices-directory-structure
- Create initial routing using ng-route and check in some basic page layouts for following
- Home
- Contactus
- About us | non_priority | create a development setup using npm bower and grunt create a development setup using npm bower and grunt install following node bower grunt angular bootstrap saas create following common tasks with grunt to carry out normal dev work copy lib files from bower dir to other relevant dir compile saas files to css files concat all js files to generate single app js files listen on file changes and carry out compilation or cancat work as required create a project dir structure according to create initial routing using ng route and check in some basic page layouts for following home contactus about us | 0 |
132,178 | 28,112,757,117 | IssuesEvent | 2023-03-31 08:29:53 | dotnet/runtime | https://api.github.com/repos/dotnet/runtime | closed | [NativeAOT] Assertion failed 'node->IsUnusedValue() && "found an unmarked unused value"' - when compiling System.Net.Sockets.Tests | area-CodeGen-coreclr in-pr | ```C
// At this point the unusedDefs map should contain only unused values.
if (checkUnusedValues)
{
for (auto kvp : unusedDefs)
{
GenTree* node = kvp.Key();
assert(node->IsUnusedValue() && "found an unmarked unused value"); <==== here
assert(!node->isContained() && "a contained node should have a user");
}
}
```
```
KernelBase.dll!wil::details::DebugBreak(void) Unknown
> clrjit_win_x64_x64.dll!assertAbort(const char * why, const char * file, unsigned int line) Line 304 C++
clrjit_win_x64_x64.dll!LIR::Range::CheckLIR(Compiler * compiler, bool checkUnusedValues) Line 1692 C++
[Inline Frame] clrjit_win_x64_x64.dll!Lowering::CheckBlock(Compiler * compiler, BasicBlock *) Line 7351 C++
[Inline Frame] clrjit_win_x64_x64.dll!Lowering::LowerBlock(BasicBlock *) Line 7382 C++
clrjit_win_x64_x64.dll!Lowering::DoPhase() Line 7151 C++
clrjit_win_x64_x64.dll!Phase::Run() Line 62 C++
clrjit_win_x64_x64.dll!Compiler::compCompile(void * * methodCodePtr, unsigned int * methodCodeSize, JitFlags * compileFlags) Line 5088 C++
clrjit_win_x64_x64.dll!Compiler::compCompileHelper(CORINFO_MODULE_STRUCT_ * classPtr, ICorJitInfo * compHnd, CORINFO_METHOD_INFO * methodInfo, void * * methodCodePtr, unsigned int * methodCodeSize, JitFlags * compileFlags) Line 7025 C++
[Inline Frame] clrjit_win_x64_x64.dll!Compiler::compCompile::__l164::__Body::Run(Compiler::compCompile::__l2::__JITParam *) Line 6181 C++
clrjit_win_x64_x64.dll!Compiler::compCompile(CORINFO_MODULE_STRUCT_ * classPtr, void * * methodCodePtr, unsigned int * methodCodeSize, JitFlags * compileFlags) Line 6185 C++
[Inline Frame] clrjit_win_x64_x64.dll!jitNativeCode::__l8::__Body::Run::__l6::__Body::Run(jitNativeCode::__l8::__Body::Run::__l5::__JITParam *) Line 7668 C++
clrjit_win_x64_x64.dll!`jitNativeCode'::`8'::__Body::Run(jitNativeCode::__l2::__JITParam * __JITpParam) Line 7671 C++
clrjit_win_x64_x64.dll!jitNativeCode(CORINFO_METHOD_STRUCT_ * methodHnd, CORINFO_MODULE_STRUCT_ * classPtr, ICorJitInfo * compHnd, CORINFO_METHOD_INFO * methodInfo, void * * methodCodePtr, unsigned int * methodCodeSize, JitFlags * compileFlags, void * inlineInfoPtr) Line 7695 C++
clrjit_win_x64_x64.dll!CILJit::compileMethod(ICorJitInfo * compHnd, CORINFO_METHOD_INFO * methodInfo, unsigned int flags, unsigned char * * entryAddress, unsigned int * nativeSizeOfCode) Line 272 C++
jitinterface_x64.dll!JitCompileMethod(CorInfoExceptionClass * * ppException, ICorJitCompiler * pJit, void * thisHandle, void * * callbacks, CORINFO_METHOD_INFO * methodInfo, unsigned int flags, unsigned char * * entryAddress, unsigned int * nativeSizeOfCode) Line 34 C++
ilc.exe!ILCompiler_RyuJit_Internal_JitInterface_CorInfoImpl__JitCompileMethod () Unknown
ilc.exe!ILCompiler_RyuJit_Internal_JitInterface_CorInfoImpl__CompileMethodInternal() Line 358 Unknown
ilc.exe!ILCompiler_RyuJit_Internal_JitInterface_CorInfoImpl__CompileMethod() Line 62 Unknown
ilc.exe!ILCompiler_RyuJit_ILCompiler_RyuJitCompilation__CompileSingleMethod_0() Line 190 Unknown
ilc.exe!System_Threading_Tasks_Parallel_System_Threading_Tasks_Parallel___c__DisplayClass19_0_1<System___Canon>___ForWorker_b__1() Line 1060 Unknown
ilc.exe!System_Threading_Tasks_Parallel_System_Threading_Tasks_TaskReplicator_Replica__Execute() Line 79 Unknown
ilc.exe!S_P_CoreLib_System_Threading_ExecutionContext__RunFromThreadPoolDispatchLoop() Line 268 Unknown
ilc.exe!S_P_CoreLib_System_Threading_Tasks_Task__ExecuteWithThreadLocal() Line 2353 Unknown
ilc.exe!S_P_CoreLib_System_Threading_ThreadPoolWorkQueue__Dispatch() Line 919 Unknown
ilc.exe!S_P_CoreLib_System_Threading_ThreadPool__DispatchCallback() Line 376 Unknown
``` | 1.0 | [NativeAOT] Assertion failed 'node->IsUnusedValue() && "found an unmarked unused value"' - when compiling System.Net.Sockets.Tests - ```C
// At this point the unusedDefs map should contain only unused values.
if (checkUnusedValues)
{
for (auto kvp : unusedDefs)
{
GenTree* node = kvp.Key();
assert(node->IsUnusedValue() && "found an unmarked unused value"); <==== here
assert(!node->isContained() && "a contained node should have a user");
}
}
```
```
KernelBase.dll!wil::details::DebugBreak(void) Unknown
> clrjit_win_x64_x64.dll!assertAbort(const char * why, const char * file, unsigned int line) Line 304 C++
clrjit_win_x64_x64.dll!LIR::Range::CheckLIR(Compiler * compiler, bool checkUnusedValues) Line 1692 C++
[Inline Frame] clrjit_win_x64_x64.dll!Lowering::CheckBlock(Compiler * compiler, BasicBlock *) Line 7351 C++
[Inline Frame] clrjit_win_x64_x64.dll!Lowering::LowerBlock(BasicBlock *) Line 7382 C++
clrjit_win_x64_x64.dll!Lowering::DoPhase() Line 7151 C++
clrjit_win_x64_x64.dll!Phase::Run() Line 62 C++
clrjit_win_x64_x64.dll!Compiler::compCompile(void * * methodCodePtr, unsigned int * methodCodeSize, JitFlags * compileFlags) Line 5088 C++
clrjit_win_x64_x64.dll!Compiler::compCompileHelper(CORINFO_MODULE_STRUCT_ * classPtr, ICorJitInfo * compHnd, CORINFO_METHOD_INFO * methodInfo, void * * methodCodePtr, unsigned int * methodCodeSize, JitFlags * compileFlags) Line 7025 C++
[Inline Frame] clrjit_win_x64_x64.dll!Compiler::compCompile::__l164::__Body::Run(Compiler::compCompile::__l2::__JITParam *) Line 6181 C++
clrjit_win_x64_x64.dll!Compiler::compCompile(CORINFO_MODULE_STRUCT_ * classPtr, void * * methodCodePtr, unsigned int * methodCodeSize, JitFlags * compileFlags) Line 6185 C++
[Inline Frame] clrjit_win_x64_x64.dll!jitNativeCode::__l8::__Body::Run::__l6::__Body::Run(jitNativeCode::__l8::__Body::Run::__l5::__JITParam *) Line 7668 C++
clrjit_win_x64_x64.dll!`jitNativeCode'::`8'::__Body::Run(jitNativeCode::__l2::__JITParam * __JITpParam) Line 7671 C++
clrjit_win_x64_x64.dll!jitNativeCode(CORINFO_METHOD_STRUCT_ * methodHnd, CORINFO_MODULE_STRUCT_ * classPtr, ICorJitInfo * compHnd, CORINFO_METHOD_INFO * methodInfo, void * * methodCodePtr, unsigned int * methodCodeSize, JitFlags * compileFlags, void * inlineInfoPtr) Line 7695 C++
clrjit_win_x64_x64.dll!CILJit::compileMethod(ICorJitInfo * compHnd, CORINFO_METHOD_INFO * methodInfo, unsigned int flags, unsigned char * * entryAddress, unsigned int * nativeSizeOfCode) Line 272 C++
jitinterface_x64.dll!JitCompileMethod(CorInfoExceptionClass * * ppException, ICorJitCompiler * pJit, void * thisHandle, void * * callbacks, CORINFO_METHOD_INFO * methodInfo, unsigned int flags, unsigned char * * entryAddress, unsigned int * nativeSizeOfCode) Line 34 C++
ilc.exe!ILCompiler_RyuJit_Internal_JitInterface_CorInfoImpl__JitCompileMethod () Unknown
ilc.exe!ILCompiler_RyuJit_Internal_JitInterface_CorInfoImpl__CompileMethodInternal() Line 358 Unknown
ilc.exe!ILCompiler_RyuJit_Internal_JitInterface_CorInfoImpl__CompileMethod() Line 62 Unknown
ilc.exe!ILCompiler_RyuJit_ILCompiler_RyuJitCompilation__CompileSingleMethod_0() Line 190 Unknown
ilc.exe!System_Threading_Tasks_Parallel_System_Threading_Tasks_Parallel___c__DisplayClass19_0_1<System___Canon>___ForWorker_b__1() Line 1060 Unknown
ilc.exe!System_Threading_Tasks_Parallel_System_Threading_Tasks_TaskReplicator_Replica__Execute() Line 79 Unknown
ilc.exe!S_P_CoreLib_System_Threading_ExecutionContext__RunFromThreadPoolDispatchLoop() Line 268 Unknown
ilc.exe!S_P_CoreLib_System_Threading_Tasks_Task__ExecuteWithThreadLocal() Line 2353 Unknown
ilc.exe!S_P_CoreLib_System_Threading_ThreadPoolWorkQueue__Dispatch() Line 919 Unknown
ilc.exe!S_P_CoreLib_System_Threading_ThreadPool__DispatchCallback() Line 376 Unknown
``` | non_priority | assertion failed node isunusedvalue found an unmarked unused value when compiling system net sockets tests c at this point the unuseddefs map should contain only unused values if checkunusedvalues for auto kvp unuseddefs gentree node kvp key assert node isunusedvalue found an unmarked unused value here assert node iscontained a contained node should have a user kernelbase dll wil details debugbreak void unknown clrjit win dll assertabort const char why const char file unsigned int line line c clrjit win dll lir range checklir compiler compiler bool checkunusedvalues line c clrjit win dll lowering checkblock compiler compiler basicblock line c clrjit win dll lowering lowerblock basicblock line c clrjit win dll lowering dophase line c clrjit win dll phase run line c clrjit win dll compiler compcompile void methodcodeptr unsigned int methodcodesize jitflags compileflags line c clrjit win dll compiler compcompilehelper corinfo module struct classptr icorjitinfo comphnd corinfo method info methodinfo void methodcodeptr unsigned int methodcodesize jitflags compileflags line c clrjit win dll compiler compcompile body run compiler compcompile jitparam line c clrjit win dll compiler compcompile corinfo module struct classptr void methodcodeptr unsigned int methodcodesize jitflags compileflags line c clrjit win dll jitnativecode body run body run jitnativecode body run jitparam line c clrjit win dll jitnativecode body run jitnativecode jitparam jitpparam line c clrjit win dll jitnativecode corinfo method struct methodhnd corinfo module struct classptr icorjitinfo comphnd corinfo method info methodinfo void methodcodeptr unsigned int methodcodesize jitflags compileflags void inlineinfoptr line c clrjit win dll ciljit compilemethod icorjitinfo comphnd corinfo method info methodinfo unsigned int flags unsigned char entryaddress unsigned int nativesizeofcode line c jitinterface dll jitcompilemethod corinfoexceptionclass ppexception icorjitcompiler pjit void thishandle void callbacks corinfo method info methodinfo unsigned int flags unsigned char entryaddress unsigned int nativesizeofcode line c ilc exe ilcompiler ryujit internal jitinterface corinfoimpl jitcompilemethod unknown ilc exe ilcompiler ryujit internal jitinterface corinfoimpl compilemethodinternal line unknown ilc exe ilcompiler ryujit internal jitinterface corinfoimpl compilemethod line unknown ilc exe ilcompiler ryujit ilcompiler ryujitcompilation compilesinglemethod line unknown ilc exe system threading tasks parallel system threading tasks parallel c forworker b line unknown ilc exe system threading tasks parallel system threading tasks taskreplicator replica execute line unknown ilc exe s p corelib system threading executioncontext runfromthreadpooldispatchloop line unknown ilc exe s p corelib system threading tasks task executewiththreadlocal line unknown ilc exe s p corelib system threading threadpoolworkqueue dispatch line unknown ilc exe s p corelib system threading threadpool dispatchcallback line unknown | 0 |
277,585 | 21,050,188,772 | IssuesEvent | 2022-03-31 19:50:45 | seisbench/seisbench | https://api.github.com/repos/seisbench/seisbench | closed | Documentation dependancies changed (doc build failing) | documentation discussion | It seems that very recently, Sphinx deprecated Jinja2 imports which now results in an ```ImportError``` when building the docs (https://github.com/sphinx-doc/sphinx/issues/10291).
Apparent fixes are to either pin the underlying Jinja2<3.1 and set it in the ```requirements.txt```, or update Sphinx. I can confirm from a local install that updating Sphinx to a later version works (4.0.3). Version pinning is pretty common (or advised) from what I can tell when building the docs but I think in this case we should update Sphinx. The reasoning being; this was a breaking change they imposed in Sphinx v4 which affected an underlying dependency and resulted in us having to make changes anyway. Let me know what you think. | 1.0 | Documentation dependancies changed (doc build failing) - It seems that very recently, Sphinx deprecated Jinja2 imports which now results in an ```ImportError``` when building the docs (https://github.com/sphinx-doc/sphinx/issues/10291).
Apparent fixes are to either pin the underlying Jinja2<3.1 and set it in the ```requirements.txt```, or update Sphinx. I can confirm from a local install that updating Sphinx to a later version works (4.0.3). Version pinning is pretty common (or advised) from what I can tell when building the docs but I think in this case we should update Sphinx. The reasoning being; this was a breaking change they imposed in Sphinx v4 which affected an underlying dependency and resulted in us having to make changes anyway. Let me know what you think. | non_priority | documentation dependancies changed doc build failing it seems that very recently sphinx deprecated imports which now results in an importerror when building the docs apparent fixes are to either pin the underlying and set it in the requirements txt or update sphinx i can confirm from a local install that updating sphinx to a later version works version pinning is pretty common or advised from what i can tell when building the docs but i think in this case we should update sphinx the reasoning being this was a breaking change they imposed in sphinx which affected an underlying dependency and resulted in us having to make changes anyway let me know what you think | 0 |
133,828 | 18,357,068,275 | IssuesEvent | 2021-10-08 19:53:04 | Dima2021/syncthing | https://api.github.com/repos/Dima2021/syncthing | opened | CVE-2021-33502 (High) detected in normalize-url-3.3.0.tgz, normalize-url-1.9.1.tgz | security vulnerability | ## CVE-2021-33502 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>normalize-url-3.3.0.tgz</b>, <b>normalize-url-1.9.1.tgz</b></p></summary>
<p>
<details><summary><b>normalize-url-3.3.0.tgz</b></p></summary>
<p>Normalize a URL</p>
<p>Library home page: <a href="https://registry.npmjs.org/normalize-url/-/normalize-url-3.3.0.tgz">https://registry.npmjs.org/normalize-url/-/normalize-url-3.3.0.tgz</a></p>
<p>Path to dependency file: syncthing/next-gen-gui/package.json</p>
<p>Path to vulnerable library: syncthing/next-gen-gui/node_modules/normalize-url/package.json</p>
<p>
Dependency Hierarchy:
- build-angular-0.901.0.tgz (Root Library)
- cssnano-4.1.10.tgz
- cssnano-preset-default-4.0.7.tgz
- postcss-normalize-url-4.0.1.tgz
- :x: **normalize-url-3.3.0.tgz** (Vulnerable Library)
</details>
<details><summary><b>normalize-url-1.9.1.tgz</b></p></summary>
<p>Normalize a URL</p>
<p>Library home page: <a href="https://registry.npmjs.org/normalize-url/-/normalize-url-1.9.1.tgz">https://registry.npmjs.org/normalize-url/-/normalize-url-1.9.1.tgz</a></p>
<p>Path to dependency file: syncthing/next-gen-gui/package.json</p>
<p>Path to vulnerable library: syncthing/next-gen-gui/node_modules/mini-css-extract-plugin/node_modules/normalize-url/package.json</p>
<p>
Dependency Hierarchy:
- build-angular-0.901.0.tgz (Root Library)
- mini-css-extract-plugin-0.9.0.tgz
- :x: **normalize-url-1.9.1.tgz** (Vulnerable Library)
</details>
<p>Found in HEAD commit: <a href="https://github.com/Dima2021/syncthing/commit/f1f0a600f271ef119a180d9c2b72d8dddce1dc21">f1f0a600f271ef119a180d9c2b72d8dddce1dc21</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
The normalize-url package before 4.5.1, 5.x before 5.3.1, and 6.x before 6.0.1 for Node.js has a ReDoS (regular expression denial of service) issue because it has exponential performance for data: URLs.
<p>Publish Date: 2021-05-24
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-33502>CVE-2021-33502</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-33502">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-33502</a></p>
<p>Release Date: 2021-05-24</p>
<p>Fix Resolution: normalize-url - 4.5.1, 5.3.1, 6.0.1</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"normalize-url","packageVersion":"3.3.0","packageFilePaths":["/next-gen-gui/package.json"],"isTransitiveDependency":true,"dependencyTree":"@angular-devkit/build-angular:0.901.0;cssnano:4.1.10;cssnano-preset-default:4.0.7;postcss-normalize-url:4.0.1;normalize-url:3.3.0","isMinimumFixVersionAvailable":true,"minimumFixVersion":"normalize-url - 4.5.1, 5.3.1, 6.0.1"},{"packageType":"javascript/Node.js","packageName":"normalize-url","packageVersion":"1.9.1","packageFilePaths":["/next-gen-gui/package.json"],"isTransitiveDependency":true,"dependencyTree":"@angular-devkit/build-angular:0.901.0;mini-css-extract-plugin:0.9.0;normalize-url:1.9.1","isMinimumFixVersionAvailable":true,"minimumFixVersion":"normalize-url - 4.5.1, 5.3.1, 6.0.1"}],"baseBranches":["main"],"vulnerabilityIdentifier":"CVE-2021-33502","vulnerabilityDetails":"The normalize-url package before 4.5.1, 5.x before 5.3.1, and 6.x before 6.0.1 for Node.js has a ReDoS (regular expression denial of service) issue because it has exponential performance for data: URLs.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-33502","cvss3Severity":"high","cvss3Score":"7.5","cvss3Metrics":{"A":"High","AC":"Low","PR":"None","S":"Unchanged","C":"None","UI":"None","AV":"Network","I":"None"},"extraData":{}}</REMEDIATE> --> | True | CVE-2021-33502 (High) detected in normalize-url-3.3.0.tgz, normalize-url-1.9.1.tgz - ## CVE-2021-33502 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>normalize-url-3.3.0.tgz</b>, <b>normalize-url-1.9.1.tgz</b></p></summary>
<p>
<details><summary><b>normalize-url-3.3.0.tgz</b></p></summary>
<p>Normalize a URL</p>
<p>Library home page: <a href="https://registry.npmjs.org/normalize-url/-/normalize-url-3.3.0.tgz">https://registry.npmjs.org/normalize-url/-/normalize-url-3.3.0.tgz</a></p>
<p>Path to dependency file: syncthing/next-gen-gui/package.json</p>
<p>Path to vulnerable library: syncthing/next-gen-gui/node_modules/normalize-url/package.json</p>
<p>
Dependency Hierarchy:
- build-angular-0.901.0.tgz (Root Library)
- cssnano-4.1.10.tgz
- cssnano-preset-default-4.0.7.tgz
- postcss-normalize-url-4.0.1.tgz
- :x: **normalize-url-3.3.0.tgz** (Vulnerable Library)
</details>
<details><summary><b>normalize-url-1.9.1.tgz</b></p></summary>
<p>Normalize a URL</p>
<p>Library home page: <a href="https://registry.npmjs.org/normalize-url/-/normalize-url-1.9.1.tgz">https://registry.npmjs.org/normalize-url/-/normalize-url-1.9.1.tgz</a></p>
<p>Path to dependency file: syncthing/next-gen-gui/package.json</p>
<p>Path to vulnerable library: syncthing/next-gen-gui/node_modules/mini-css-extract-plugin/node_modules/normalize-url/package.json</p>
<p>
Dependency Hierarchy:
- build-angular-0.901.0.tgz (Root Library)
- mini-css-extract-plugin-0.9.0.tgz
- :x: **normalize-url-1.9.1.tgz** (Vulnerable Library)
</details>
<p>Found in HEAD commit: <a href="https://github.com/Dima2021/syncthing/commit/f1f0a600f271ef119a180d9c2b72d8dddce1dc21">f1f0a600f271ef119a180d9c2b72d8dddce1dc21</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
The normalize-url package before 4.5.1, 5.x before 5.3.1, and 6.x before 6.0.1 for Node.js has a ReDoS (regular expression denial of service) issue because it has exponential performance for data: URLs.
<p>Publish Date: 2021-05-24
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-33502>CVE-2021-33502</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-33502">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-33502</a></p>
<p>Release Date: 2021-05-24</p>
<p>Fix Resolution: normalize-url - 4.5.1, 5.3.1, 6.0.1</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"normalize-url","packageVersion":"3.3.0","packageFilePaths":["/next-gen-gui/package.json"],"isTransitiveDependency":true,"dependencyTree":"@angular-devkit/build-angular:0.901.0;cssnano:4.1.10;cssnano-preset-default:4.0.7;postcss-normalize-url:4.0.1;normalize-url:3.3.0","isMinimumFixVersionAvailable":true,"minimumFixVersion":"normalize-url - 4.5.1, 5.3.1, 6.0.1"},{"packageType":"javascript/Node.js","packageName":"normalize-url","packageVersion":"1.9.1","packageFilePaths":["/next-gen-gui/package.json"],"isTransitiveDependency":true,"dependencyTree":"@angular-devkit/build-angular:0.901.0;mini-css-extract-plugin:0.9.0;normalize-url:1.9.1","isMinimumFixVersionAvailable":true,"minimumFixVersion":"normalize-url - 4.5.1, 5.3.1, 6.0.1"}],"baseBranches":["main"],"vulnerabilityIdentifier":"CVE-2021-33502","vulnerabilityDetails":"The normalize-url package before 4.5.1, 5.x before 5.3.1, and 6.x before 6.0.1 for Node.js has a ReDoS (regular expression denial of service) issue because it has exponential performance for data: URLs.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-33502","cvss3Severity":"high","cvss3Score":"7.5","cvss3Metrics":{"A":"High","AC":"Low","PR":"None","S":"Unchanged","C":"None","UI":"None","AV":"Network","I":"None"},"extraData":{}}</REMEDIATE> --> | non_priority | cve high detected in normalize url tgz normalize url tgz cve high severity vulnerability vulnerable libraries normalize url tgz normalize url tgz normalize url tgz normalize a url library home page a href path to dependency file syncthing next gen gui package json path to vulnerable library syncthing next gen gui node modules normalize url package json dependency hierarchy build angular tgz root library cssnano tgz cssnano preset default tgz postcss normalize url tgz x normalize url tgz vulnerable library normalize url tgz normalize a url library home page a href path to dependency file syncthing next gen gui package json path to vulnerable library syncthing next gen gui node modules mini css extract plugin node modules normalize url package json dependency hierarchy build angular tgz root library mini css extract plugin tgz x normalize url tgz vulnerable library found in head commit a href found in base branch main vulnerability details the normalize url package before x before and x before for node js has a redos regular expression denial of service issue because it has exponential performance for data urls 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 normalize url isopenpronvulnerability true ispackagebased true isdefaultbranch true packages istransitivedependency true dependencytree angular devkit build angular cssnano cssnano preset default postcss normalize url normalize url isminimumfixversionavailable true minimumfixversion normalize url packagetype javascript node js packagename normalize url packageversion packagefilepaths istransitivedependency true dependencytree angular devkit build angular mini css extract plugin normalize url isminimumfixversionavailable true minimumfixversion normalize url basebranches vulnerabilityidentifier cve vulnerabilitydetails the normalize url package before x before and x before for node js has a redos regular expression denial of service issue because it has exponential performance for data urls vulnerabilityurl | 0 |
12,746 | 3,644,026,114 | IssuesEvent | 2016-02-15 07:33:22 | Esri/angular-esri-map | https://api.github.com/repos/Esri/angular-esri-map | opened | Add links to v1 docs and beta warning | documentation | Should copy code from [v1.x docs](https://arcgis.github.com/angular-esri-map-site-v1) that adds a link to the top nav to the previous version of the docs, and also a sticky footer warning to indicate that the repo is in beta (for now). | 1.0 | Add links to v1 docs and beta warning - Should copy code from [v1.x docs](https://arcgis.github.com/angular-esri-map-site-v1) that adds a link to the top nav to the previous version of the docs, and also a sticky footer warning to indicate that the repo is in beta (for now). | non_priority | add links to docs and beta warning should copy code from that adds a link to the top nav to the previous version of the docs and also a sticky footer warning to indicate that the repo is in beta for now | 0 |
152,606 | 13,461,783,785 | IssuesEvent | 2020-09-09 15:13:59 | fga-eps-mds/2020-1-Ziguen | https://api.github.com/repos/fga-eps-mds/2020-1-Ziguen | closed | Gestão da Sprint 1 | Reuniao documentation | **Definir os processos de cada sprint/ciclo, definido em uma semana.**
### Tarefas
- [x] Documentação da Sprint;
- [x] Reuniões semanais - Sprint com período definido de uma semana;
- [x] Pesquisa de novas atividades para cada Sprint;
- [x] Criação das issues;
- [x] Execução das tarefas das issues;
- [x] Movimentação da issue para as próximas fases;
- [x] Apresentar o que foi desenvolvido para equipe na reunião seguinte.
### Critério de Aceitação
- [x] Discussão do que foi feito e ajustes, se necessário;
- [x] Documentação de discussões de reunião. | 1.0 | Gestão da Sprint 1 - **Definir os processos de cada sprint/ciclo, definido em uma semana.**
### Tarefas
- [x] Documentação da Sprint;
- [x] Reuniões semanais - Sprint com período definido de uma semana;
- [x] Pesquisa de novas atividades para cada Sprint;
- [x] Criação das issues;
- [x] Execução das tarefas das issues;
- [x] Movimentação da issue para as próximas fases;
- [x] Apresentar o que foi desenvolvido para equipe na reunião seguinte.
### Critério de Aceitação
- [x] Discussão do que foi feito e ajustes, se necessário;
- [x] Documentação de discussões de reunião. | non_priority | gestão da sprint definir os processos de cada sprint ciclo definido em uma semana tarefas documentação da sprint reuniões semanais sprint com período definido de uma semana pesquisa de novas atividades para cada sprint criação das issues execução das tarefas das issues movimentação da issue para as próximas fases apresentar o que foi desenvolvido para equipe na reunião seguinte critério de aceitação discussão do que foi feito e ajustes se necessário documentação de discussões de reunião | 0 |
111,689 | 11,739,733,662 | IssuesEvent | 2020-03-11 18:14:46 | twitter/twitter-text | https://api.github.com/repos/twitter/twitter-text | closed | Update documentation - specifically for CJK and Emoji | documentation | The official documentation doesn't reflect reality. Especially around Chinese, Japanese, and Korean text.
On https://developer.twitter.com/en/docs/basics/counting-characters the documentation says
> Tweet length is measured by the number of codepoints in the NFC normalized version of the text.
This is not *quite* true :-)
The Twitter-Text page - https://developer.twitter.com/en/docs/developer-utilities/twitter-text - says:
> The Configuration defines Unicode code point ranges, with a weight associated with each of these ranges. **This enables language density to be taken into consideration when counting characters.**
But it doesn't explain which high-density languages are included. Nor does it explain Emoji.
## Reading between the lines
On [the blog post announcing 280 characters](https://blog.twitter.com/en_us/topics/product/2017/Giving-you-more-characters-to-express-yourself.html), you say:
> We want every person around the world to easily express themselves on Twitter, so we're doing something new: we're going to try out a longer limit, 280 characters, in languages impacted by cramming (**which is all except Japanese, Chinese, and Korean**).
Hidden in the [POST status/update](https://developer.twitter.com/en/docs/tweets/post-and-engage/api-reference/post-statuses-update) documentation, it says:
> To make room for more expression, we will now count all emojis as equal—including those with gender and skin tone modifiers 👍🏻👍🏽👍🏿. This is now reflected in Twitter-Text, our Open Source library.
But I don't see that in the official documentation anywhere.
## Suggestion
* Update both https://developer.twitter.com/en/docs/basics/counting-characters and https://developer.twitter.com/en/docs/developer-utilities/twitter-text
* Explain how emoji are counted
* Explain that CJK text is still restricted to 140 characters
* If possible, give a simple explanation of the weightedLength algorithm for mixed content. | 1.0 | Update documentation - specifically for CJK and Emoji - The official documentation doesn't reflect reality. Especially around Chinese, Japanese, and Korean text.
On https://developer.twitter.com/en/docs/basics/counting-characters the documentation says
> Tweet length is measured by the number of codepoints in the NFC normalized version of the text.
This is not *quite* true :-)
The Twitter-Text page - https://developer.twitter.com/en/docs/developer-utilities/twitter-text - says:
> The Configuration defines Unicode code point ranges, with a weight associated with each of these ranges. **This enables language density to be taken into consideration when counting characters.**
But it doesn't explain which high-density languages are included. Nor does it explain Emoji.
## Reading between the lines
On [the blog post announcing 280 characters](https://blog.twitter.com/en_us/topics/product/2017/Giving-you-more-characters-to-express-yourself.html), you say:
> We want every person around the world to easily express themselves on Twitter, so we're doing something new: we're going to try out a longer limit, 280 characters, in languages impacted by cramming (**which is all except Japanese, Chinese, and Korean**).
Hidden in the [POST status/update](https://developer.twitter.com/en/docs/tweets/post-and-engage/api-reference/post-statuses-update) documentation, it says:
> To make room for more expression, we will now count all emojis as equal—including those with gender and skin tone modifiers 👍🏻👍🏽👍🏿. This is now reflected in Twitter-Text, our Open Source library.
But I don't see that in the official documentation anywhere.
## Suggestion
* Update both https://developer.twitter.com/en/docs/basics/counting-characters and https://developer.twitter.com/en/docs/developer-utilities/twitter-text
* Explain how emoji are counted
* Explain that CJK text is still restricted to 140 characters
* If possible, give a simple explanation of the weightedLength algorithm for mixed content. | non_priority | update documentation specifically for cjk and emoji the official documentation doesn t reflect reality especially around chinese japanese and korean text on the documentation says tweet length is measured by the number of codepoints in the nfc normalized version of the text this is not quite true the twitter text page says the configuration defines unicode code point ranges with a weight associated with each of these ranges this enables language density to be taken into consideration when counting characters but it doesn t explain which high density languages are included nor does it explain emoji reading between the lines on you say we want every person around the world to easily express themselves on twitter so we re doing something new we re going to try out a longer limit characters in languages impacted by cramming which is all except japanese chinese and korean hidden in the documentation it says to make room for more expression we will now count all emojis as equal—including those with gender and skin tone modifiers 👍🏻👍🏽👍🏿 this is now reflected in twitter text our open source library but i don t see that in the official documentation anywhere suggestion update both and explain how emoji are counted explain that cjk text is still restricted to characters if possible give a simple explanation of the weightedlength algorithm for mixed content | 0 |
350,982 | 31,932,568,982 | IssuesEvent | 2023-09-19 08:25:34 | unifyai/ivy | https://api.github.com/repos/unifyai/ivy | reopened | Fix linalg.test_adjoint | Sub Task Ivy API Experimental Failing Test | | | |
|---|---|
|jax|<a href="https://github.com/unifyai/ivy/actions/runs/5722995918/job/15506875181"><img src=https://img.shields.io/badge/-failure-red></a>
|numpy|<a href="https://github.com/unifyai/ivy/actions/runs/5722995918/job/15506875181"><img src=https://img.shields.io/badge/-failure-red></a>
|tensorflow|<a href="https://github.com/unifyai/ivy/actions/runs/5722995918/job/15506875181"><img src=https://img.shields.io/badge/-success-success></a>
|torch|<a href="https://github.com/unifyai/ivy/actions/runs/5722995918/job/15506875181"><img src=https://img.shields.io/badge/-failure-red></a>
|paddle|<a href="https://github.com/unifyai/ivy/actions/runs/5722995918/job/15506875181"><img src=https://img.shields.io/badge/-failure-red></a>
| 1.0 | Fix linalg.test_adjoint - | | |
|---|---|
|jax|<a href="https://github.com/unifyai/ivy/actions/runs/5722995918/job/15506875181"><img src=https://img.shields.io/badge/-failure-red></a>
|numpy|<a href="https://github.com/unifyai/ivy/actions/runs/5722995918/job/15506875181"><img src=https://img.shields.io/badge/-failure-red></a>
|tensorflow|<a href="https://github.com/unifyai/ivy/actions/runs/5722995918/job/15506875181"><img src=https://img.shields.io/badge/-success-success></a>
|torch|<a href="https://github.com/unifyai/ivy/actions/runs/5722995918/job/15506875181"><img src=https://img.shields.io/badge/-failure-red></a>
|paddle|<a href="https://github.com/unifyai/ivy/actions/runs/5722995918/job/15506875181"><img src=https://img.shields.io/badge/-failure-red></a>
| non_priority | fix linalg test adjoint jax a href src numpy a href src tensorflow a href src torch a href src paddle a href src | 0 |
175,515 | 21,313,842,668 | IssuesEvent | 2022-04-16 01:07:52 | dacastro4/laravel-gmail | https://api.github.com/repos/dacastro4/laravel-gmail | opened | orchestra/testbench-v3.5.5: 2 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>orchestra/testbench-v3.5.5</b></p></summary>
<p></p>
<p>
</details>
## Vulnerabilities
| CVE | Severity | <img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS | Dependency | Type | Fixed in | Remediation Available |
| ------------- | ------------- | ----- | ----- | ----- | --- | --- |
| [WS-2020-0144](https://blog.laravel.com/laravel-cookie-security-releases) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 9.8 | laravel/framework-v5.5.45 | Transitive | N/A | ❌ |
| [CVE-2021-43503](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-43503) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 9.8 | laravel/framework-v5.5.45 | Transitive | N/A | ❌ |
## Details
<details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> WS-2020-0144</summary>
### Vulnerable Library - <b>laravel/framework-v5.5.45</b></p>
<p>The Laravel Framework.</p>
<p>Library home page: <a href="https://api.github.com/repos/laravel/framework/zipball/52c79ecf54b6168a54730ccb6c4c9f3561732a80">https://api.github.com/repos/laravel/framework/zipball/52c79ecf54b6168a54730ccb6c4c9f3561732a80</a></p>
<p>
Dependency Hierarchy:
- orchestra/testbench-v3.5.5 (Root Library)
- :x: **laravel/framework-v5.5.45** (Vulnerable Library)
</p>
<p></p>
### Vulnerability Details
<p>
Application's using the "cookie" session driver were the primary applications affected by this vulnerability. Since we have not yet released a security release for the Laravel 5.5 version of the framework, we recommend that all applications running Laravel 5.5 and earlier do not use the "cookie" session driver in their production deployments.
<p>Publish Date: 2020-07-27
<p>URL: <a href=https://blog.laravel.com/laravel-cookie-security-releases>WS-2020-0144</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://nvd.nist.gov/vuln/detail/WS-2020-0144">https://nvd.nist.gov/vuln/detail/WS-2020-0144</a></p>
<p>Release Date: 2020-07-27</p>
<p>Fix Resolution: laravel/framework - 5.6.x-dev,5.7.x-dev,v6.18.31,5.0.x-dev,5.5.x-dev,5.2.x-dev,4.2.x-dev,5.2.41,6.x-dev,5.3,5.0.30,5.4.x-dev,5.1.x-dev,5.8.x-dev</p>
</p>
<p></p>
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2021-43503</summary>
### Vulnerable Library - <b>laravel/framework-v5.5.45</b></p>
<p>The Laravel Framework.</p>
<p>Library home page: <a href="https://api.github.com/repos/laravel/framework/zipball/52c79ecf54b6168a54730ccb6c4c9f3561732a80">https://api.github.com/repos/laravel/framework/zipball/52c79ecf54b6168a54730ccb6c4c9f3561732a80</a></p>
<p>
Dependency Hierarchy:
- orchestra/testbench-v3.5.5 (Root Library)
- :x: **laravel/framework-v5.5.45** (Vulnerable Library)
</p>
<p></p>
### Vulnerability Details
<p>
A Remote Code Execution (RCE) vulnerability exists in h laravel 5.8.38 via an unserialize pop chain in (1) __destruct in \Routing\PendingResourceRegistration.php, (2) __cal in Queue\Capsule\Manager.php, and (3) __invoke in mockery\library\Mockery\ClosureWrapper.php.
<p>Publish Date: 2022-04-08
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-43503>CVE-2021-43503</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>
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
</details>
<!-- <REMEDIATE>[{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"PHP","packageName":"laravel/framework","packageVersion":"v5.5.45","packageFilePaths":[],"isTransitiveDependency":true,"dependencyTree":"orchestra/testbench:v3.5.5;laravel/framework:v5.5.45","isMinimumFixVersionAvailable":true,"minimumFixVersion":"laravel/framework - 5.6.x-dev,5.7.x-dev,v6.18.31,5.0.x-dev,5.5.x-dev,5.2.x-dev,4.2.x-dev,5.2.41,6.x-dev,5.3,5.0.30,5.4.x-dev,5.1.x-dev,5.8.x-dev","isBinary":true}],"baseBranches":[],"vulnerabilityIdentifier":"WS-2020-0144","vulnerabilityDetails":"Application\u0027s using the \"cookie\" session driver were the primary applications affected by this vulnerability. Since we have not yet released a security release for the Laravel 5.5 version of the framework, we recommend that all applications running Laravel 5.5 and earlier do not use the \"cookie\" session driver in their production deployments.","vulnerabilityUrl":"https://blog.laravel.com/laravel-cookie-security-releases","cvss3Severity":"high","cvss3Score":"9.8","cvss3Metrics":{"A":"High","AC":"Low","PR":"None","S":"Unchanged","C":"High","UI":"None","AV":"Network","I":"High"},"extraData":{}},{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"PHP","packageName":"laravel/framework","packageVersion":"v5.5.45","packageFilePaths":[],"isTransitiveDependency":true,"dependencyTree":"orchestra/testbench:v3.5.5;laravel/framework:v5.5.45","isMinimumFixVersionAvailable":false,"isBinary":true}],"baseBranches":[],"vulnerabilityIdentifier":"CVE-2021-43503","vulnerabilityDetails":"A Remote Code Execution (RCE) vulnerability exists in h laravel 5.8.38 via an unserialize pop chain in (1) __destruct in \\Routing\\PendingResourceRegistration.php, (2) __cal in Queue\\Capsule\\Manager.php, and (3) __invoke in mockery\\library\\Mockery\\ClosureWrapper.php.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-43503","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 | orchestra/testbench-v3.5.5: 2 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>orchestra/testbench-v3.5.5</b></p></summary>
<p></p>
<p>
</details>
## Vulnerabilities
| CVE | Severity | <img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS | Dependency | Type | Fixed in | Remediation Available |
| ------------- | ------------- | ----- | ----- | ----- | --- | --- |
| [WS-2020-0144](https://blog.laravel.com/laravel-cookie-security-releases) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 9.8 | laravel/framework-v5.5.45 | Transitive | N/A | ❌ |
| [CVE-2021-43503](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-43503) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 9.8 | laravel/framework-v5.5.45 | Transitive | N/A | ❌ |
## Details
<details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> WS-2020-0144</summary>
### Vulnerable Library - <b>laravel/framework-v5.5.45</b></p>
<p>The Laravel Framework.</p>
<p>Library home page: <a href="https://api.github.com/repos/laravel/framework/zipball/52c79ecf54b6168a54730ccb6c4c9f3561732a80">https://api.github.com/repos/laravel/framework/zipball/52c79ecf54b6168a54730ccb6c4c9f3561732a80</a></p>
<p>
Dependency Hierarchy:
- orchestra/testbench-v3.5.5 (Root Library)
- :x: **laravel/framework-v5.5.45** (Vulnerable Library)
</p>
<p></p>
### Vulnerability Details
<p>
Application's using the "cookie" session driver were the primary applications affected by this vulnerability. Since we have not yet released a security release for the Laravel 5.5 version of the framework, we recommend that all applications running Laravel 5.5 and earlier do not use the "cookie" session driver in their production deployments.
<p>Publish Date: 2020-07-27
<p>URL: <a href=https://blog.laravel.com/laravel-cookie-security-releases>WS-2020-0144</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://nvd.nist.gov/vuln/detail/WS-2020-0144">https://nvd.nist.gov/vuln/detail/WS-2020-0144</a></p>
<p>Release Date: 2020-07-27</p>
<p>Fix Resolution: laravel/framework - 5.6.x-dev,5.7.x-dev,v6.18.31,5.0.x-dev,5.5.x-dev,5.2.x-dev,4.2.x-dev,5.2.41,6.x-dev,5.3,5.0.30,5.4.x-dev,5.1.x-dev,5.8.x-dev</p>
</p>
<p></p>
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2021-43503</summary>
### Vulnerable Library - <b>laravel/framework-v5.5.45</b></p>
<p>The Laravel Framework.</p>
<p>Library home page: <a href="https://api.github.com/repos/laravel/framework/zipball/52c79ecf54b6168a54730ccb6c4c9f3561732a80">https://api.github.com/repos/laravel/framework/zipball/52c79ecf54b6168a54730ccb6c4c9f3561732a80</a></p>
<p>
Dependency Hierarchy:
- orchestra/testbench-v3.5.5 (Root Library)
- :x: **laravel/framework-v5.5.45** (Vulnerable Library)
</p>
<p></p>
### Vulnerability Details
<p>
A Remote Code Execution (RCE) vulnerability exists in h laravel 5.8.38 via an unserialize pop chain in (1) __destruct in \Routing\PendingResourceRegistration.php, (2) __cal in Queue\Capsule\Manager.php, and (3) __invoke in mockery\library\Mockery\ClosureWrapper.php.
<p>Publish Date: 2022-04-08
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-43503>CVE-2021-43503</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>
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
</details>
<!-- <REMEDIATE>[{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"PHP","packageName":"laravel/framework","packageVersion":"v5.5.45","packageFilePaths":[],"isTransitiveDependency":true,"dependencyTree":"orchestra/testbench:v3.5.5;laravel/framework:v5.5.45","isMinimumFixVersionAvailable":true,"minimumFixVersion":"laravel/framework - 5.6.x-dev,5.7.x-dev,v6.18.31,5.0.x-dev,5.5.x-dev,5.2.x-dev,4.2.x-dev,5.2.41,6.x-dev,5.3,5.0.30,5.4.x-dev,5.1.x-dev,5.8.x-dev","isBinary":true}],"baseBranches":[],"vulnerabilityIdentifier":"WS-2020-0144","vulnerabilityDetails":"Application\u0027s using the \"cookie\" session driver were the primary applications affected by this vulnerability. Since we have not yet released a security release for the Laravel 5.5 version of the framework, we recommend that all applications running Laravel 5.5 and earlier do not use the \"cookie\" session driver in their production deployments.","vulnerabilityUrl":"https://blog.laravel.com/laravel-cookie-security-releases","cvss3Severity":"high","cvss3Score":"9.8","cvss3Metrics":{"A":"High","AC":"Low","PR":"None","S":"Unchanged","C":"High","UI":"None","AV":"Network","I":"High"},"extraData":{}},{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"PHP","packageName":"laravel/framework","packageVersion":"v5.5.45","packageFilePaths":[],"isTransitiveDependency":true,"dependencyTree":"orchestra/testbench:v3.5.5;laravel/framework:v5.5.45","isMinimumFixVersionAvailable":false,"isBinary":true}],"baseBranches":[],"vulnerabilityIdentifier":"CVE-2021-43503","vulnerabilityDetails":"A Remote Code Execution (RCE) vulnerability exists in h laravel 5.8.38 via an unserialize pop chain in (1) __destruct in \\Routing\\PendingResourceRegistration.php, (2) __cal in Queue\\Capsule\\Manager.php, and (3) __invoke in mockery\\library\\Mockery\\ClosureWrapper.php.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-43503","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 | orchestra testbench vulnerabilities highest severity is vulnerable library orchestra testbench vulnerabilities cve severity cvss dependency type fixed in remediation available high laravel framework transitive n a high laravel framework transitive n a details ws vulnerable library laravel framework the laravel framework library home page a href dependency hierarchy orchestra testbench root library x laravel framework vulnerable library vulnerability details application s using the cookie session driver were the primary applications affected by this vulnerability since we have not yet released a security release for the laravel version of the framework we recommend that all applications running laravel and earlier do not use the cookie session driver in their production deployments 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 laravel framework x dev x dev x dev x dev x dev x dev x dev x dev x dev x dev step up your open source security game with whitesource cve vulnerable library laravel framework the laravel framework library home page a href dependency hierarchy orchestra testbench root library x laravel framework vulnerable library vulnerability details a remote code execution rce vulnerability exists in h laravel via an unserialize pop chain in destruct in routing pendingresourceregistration php cal in queue capsule manager php and invoke in mockery library mockery closurewrapper php 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 step up your open source security game with whitesource istransitivedependency true dependencytree orchestra testbench laravel framework isminimumfixversionavailable true minimumfixversion laravel framework x dev x dev x dev x dev x dev x dev x dev x dev x dev x dev isbinary true basebranches vulnerabilityidentifier ws vulnerabilitydetails application using the cookie session driver were the primary applications affected by this vulnerability since we have not yet released a security release for the laravel version of the framework we recommend that all applications running laravel and earlier do not use the cookie session driver in their production deployments vulnerabilityurl istransitivedependency true dependencytree orchestra testbench laravel framework isminimumfixversionavailable false isbinary true basebranches vulnerabilityidentifier cve vulnerabilitydetails a remote code execution rce vulnerability exists in h laravel via an unserialize pop chain in destruct in routing pendingresourceregistration php cal in queue capsule manager php and invoke in mockery library mockery closurewrapper php vulnerabilityurl | 0 |
160,261 | 25,135,213,409 | IssuesEvent | 2022-11-09 18:01:41 | microsoft/pyright | https://api.github.com/repos/microsoft/pyright | closed | Support the use of Generic with __init_subclass__ arguments | as designed | **Is your feature request related to a problem? Please describe.**
I have the following structure in my code:
```python
from typing import Generic, TypeVar
class BaseDatabaseModel:
pass
Model = TypeVar("Model", bound=BaseDatabaseModel)
class SomeDatabaseModel(BaseDatabaseModel):
pass
class BaseOperations(Generic[Model]):
model: type[Model]
def __init_subclass__(cls, model: type[Model]) -> None:
cls.model = model
class BusinessLogic(BaseOperations, model=SomeDatabaseModel):
pass
reveal_type(BusinessLogic().model)
```
Pyright is already able to see that `model` is a required parameter for any descendants of `BaseOperations` but sadly it doesn't support `Generic`. I.e. In this case `reveal_type` shows `Unknown` instead of `Type[SomeDatabaseModel]`.
**Describe the solution you'd like**
`reveal_type` should show `Type[SomeDatabaseModel]` similar to how it would do if we sent model through `__init__`. Pyright is great at guessing types and I know that you prefer for pyright to only support features that are supported by python's type system (and this one is) so it would be cool if you were able to implement it.
**Additional context**
Mypy gives `Type[Any]` for this `reveal_type` which is a bit more helpful but still not great.
| 1.0 | Support the use of Generic with __init_subclass__ arguments - **Is your feature request related to a problem? Please describe.**
I have the following structure in my code:
```python
from typing import Generic, TypeVar
class BaseDatabaseModel:
pass
Model = TypeVar("Model", bound=BaseDatabaseModel)
class SomeDatabaseModel(BaseDatabaseModel):
pass
class BaseOperations(Generic[Model]):
model: type[Model]
def __init_subclass__(cls, model: type[Model]) -> None:
cls.model = model
class BusinessLogic(BaseOperations, model=SomeDatabaseModel):
pass
reveal_type(BusinessLogic().model)
```
Pyright is already able to see that `model` is a required parameter for any descendants of `BaseOperations` but sadly it doesn't support `Generic`. I.e. In this case `reveal_type` shows `Unknown` instead of `Type[SomeDatabaseModel]`.
**Describe the solution you'd like**
`reveal_type` should show `Type[SomeDatabaseModel]` similar to how it would do if we sent model through `__init__`. Pyright is great at guessing types and I know that you prefer for pyright to only support features that are supported by python's type system (and this one is) so it would be cool if you were able to implement it.
**Additional context**
Mypy gives `Type[Any]` for this `reveal_type` which is a bit more helpful but still not great.
| non_priority | support the use of generic with init subclass arguments is your feature request related to a problem please describe i have the following structure in my code python from typing import generic typevar class basedatabasemodel pass model typevar model bound basedatabasemodel class somedatabasemodel basedatabasemodel pass class baseoperations generic model type def init subclass cls model type none cls model model class businesslogic baseoperations model somedatabasemodel pass reveal type businesslogic model pyright is already able to see that model is a required parameter for any descendants of baseoperations but sadly it doesn t support generic i e in this case reveal type shows unknown instead of type describe the solution you d like reveal type should show type similar to how it would do if we sent model through init pyright is great at guessing types and i know that you prefer for pyright to only support features that are supported by python s type system and this one is so it would be cool if you were able to implement it additional context mypy gives type for this reveal type which is a bit more helpful but still not great | 0 |
280,323 | 24,295,041,605 | IssuesEvent | 2022-09-29 09:23:07 | hoppscotch/hoppscotch | https://api.github.com/repos/hoppscotch/hoppscotch | closed | [bug]: Docker Hoppscotch v3.0.0 do not start | bug need testing | ### Is there an existing issue for this?
- [X] I have searched the existing issues
### Current behavior
## Operation
```
docker run --rm --name hoppscotch -p 3000:3000 hoppscotch/hoppscotch:latest
```
## Result ( https://labs.play-with-docker.com )
```
###############################################################
# WARNING!!!! #
# This is a sandbox environment. Using personal credentials #
# is HIGHLY! discouraged. Any consequences of doing so are #
# completely the user's responsibilites. #
# #
# The PWD team. #
###############################################################
[node1] (local) root@192.168.0.28 ~
$ docker run --rm --name hoppscotch -p 3000:3000 hoppscotch/hoppscotch:latest
Unable to find image 'hoppscotch/hoppscotch:latest' locally
latest: Pulling from hoppscotch/hoppscotch
213ec9aee27d: Pull complete
5f1f78129e95: Pull complete
dbe0afc499c9: Pull complete
db3b3dd80de9: Pull complete
8fe2b759a691: Pull complete
1bc87e0f6f72: Pull complete
acddc8052956: Pull complete
4f4fb700ef54: Pull complete
67db4ee0270d: Pull complete
affaf95f05f8: Pull complete
3fc499c3533e: Pull complete
a984c104554c: Pull complete
Digest: sha256:4576cc570e094dd63b0d456b6255d27348d3a8c342940c2c08a0b1ccb9da38b0
Status: Downloaded newer image for hoppscotch/hoppscotch:latest
> hoppscotch-app@3.0.0 start /app
> pnpm -r do-prod-start
Scope: 5 of 6 workspace projects
None of the selected packages has a "do-prod-start" script
[node1] (local) root@192.168.0.28 ~
```
### Steps to reproduce
1. https://labs.play-with-docker.com
2. docker run --rm --name hoppscotch -p 3000:3000 hoppscotch/hoppscotch:latest
3. Result
```
docker run --rm --name hoppscotch -p 3000:3000 hoppscotch/hoppscotch:latest
Unable to find image 'hoppscotch/hoppscotch:latest' locally
latest: Pulling from hoppscotch/hoppscotch
213ec9aee27d: Pull complete
5f1f78129e95: Pull complete
dbe0afc499c9: Pull complete
db3b3dd80de9: Pull complete
8fe2b759a691: Pull complete
1bc87e0f6f72: Pull complete
acddc8052956: Pull complete
4f4fb700ef54: Pull complete
67db4ee0270d: Pull complete
affaf95f05f8: Pull complete
3fc499c3533e: Pull complete
a984c104554c: Pull complete
Digest: sha256:4576cc570e094dd63b0d456b6255d27348d3a8c342940c2c08a0b1ccb9da38b0
Status: Downloaded newer image for hoppscotch/hoppscotch:latest
> hoppscotch-app@3.0.0 start /app
> pnpm -r do-prod-start
Scope: 5 of 6 workspace projects
None of the selected packages has a "do-prod-start" script
```
### Environment
Release
### Version
Local | 1.0 | [bug]: Docker Hoppscotch v3.0.0 do not start - ### Is there an existing issue for this?
- [X] I have searched the existing issues
### Current behavior
## Operation
```
docker run --rm --name hoppscotch -p 3000:3000 hoppscotch/hoppscotch:latest
```
## Result ( https://labs.play-with-docker.com )
```
###############################################################
# WARNING!!!! #
# This is a sandbox environment. Using personal credentials #
# is HIGHLY! discouraged. Any consequences of doing so are #
# completely the user's responsibilites. #
# #
# The PWD team. #
###############################################################
[node1] (local) root@192.168.0.28 ~
$ docker run --rm --name hoppscotch -p 3000:3000 hoppscotch/hoppscotch:latest
Unable to find image 'hoppscotch/hoppscotch:latest' locally
latest: Pulling from hoppscotch/hoppscotch
213ec9aee27d: Pull complete
5f1f78129e95: Pull complete
dbe0afc499c9: Pull complete
db3b3dd80de9: Pull complete
8fe2b759a691: Pull complete
1bc87e0f6f72: Pull complete
acddc8052956: Pull complete
4f4fb700ef54: Pull complete
67db4ee0270d: Pull complete
affaf95f05f8: Pull complete
3fc499c3533e: Pull complete
a984c104554c: Pull complete
Digest: sha256:4576cc570e094dd63b0d456b6255d27348d3a8c342940c2c08a0b1ccb9da38b0
Status: Downloaded newer image for hoppscotch/hoppscotch:latest
> hoppscotch-app@3.0.0 start /app
> pnpm -r do-prod-start
Scope: 5 of 6 workspace projects
None of the selected packages has a "do-prod-start" script
[node1] (local) root@192.168.0.28 ~
```
### Steps to reproduce
1. https://labs.play-with-docker.com
2. docker run --rm --name hoppscotch -p 3000:3000 hoppscotch/hoppscotch:latest
3. Result
```
docker run --rm --name hoppscotch -p 3000:3000 hoppscotch/hoppscotch:latest
Unable to find image 'hoppscotch/hoppscotch:latest' locally
latest: Pulling from hoppscotch/hoppscotch
213ec9aee27d: Pull complete
5f1f78129e95: Pull complete
dbe0afc499c9: Pull complete
db3b3dd80de9: Pull complete
8fe2b759a691: Pull complete
1bc87e0f6f72: Pull complete
acddc8052956: Pull complete
4f4fb700ef54: Pull complete
67db4ee0270d: Pull complete
affaf95f05f8: Pull complete
3fc499c3533e: Pull complete
a984c104554c: Pull complete
Digest: sha256:4576cc570e094dd63b0d456b6255d27348d3a8c342940c2c08a0b1ccb9da38b0
Status: Downloaded newer image for hoppscotch/hoppscotch:latest
> hoppscotch-app@3.0.0 start /app
> pnpm -r do-prod-start
Scope: 5 of 6 workspace projects
None of the selected packages has a "do-prod-start" script
```
### Environment
Release
### Version
Local | non_priority | docker hoppscotch do not start is there an existing issue for this i have searched the existing issues current behavior operation docker run rm name hoppscotch p hoppscotch hoppscotch latest result warning this is a sandbox environment using personal credentials is highly discouraged any consequences of doing so are completely the user s responsibilites the pwd team local root docker run rm name hoppscotch p hoppscotch hoppscotch latest unable to find image hoppscotch hoppscotch latest locally latest pulling from hoppscotch hoppscotch pull complete pull complete pull complete pull complete pull complete pull complete pull complete pull complete pull complete pull complete pull complete pull complete digest status downloaded newer image for hoppscotch hoppscotch latest hoppscotch app start app pnpm r do prod start scope of workspace projects none of the selected packages has a do prod start script local root steps to reproduce docker run rm name hoppscotch p hoppscotch hoppscotch latest result docker run rm name hoppscotch p hoppscotch hoppscotch latest unable to find image hoppscotch hoppscotch latest locally latest pulling from hoppscotch hoppscotch pull complete pull complete pull complete pull complete pull complete pull complete pull complete pull complete pull complete pull complete pull complete pull complete digest status downloaded newer image for hoppscotch hoppscotch latest hoppscotch app start app pnpm r do prod start scope of workspace projects none of the selected packages has a do prod start script environment release version local | 0 |
49,336 | 12,323,695,476 | IssuesEvent | 2020-05-13 12:36:36 | micronaut-projects/micronaut-core | https://api.github.com/repos/micronaut-projects/micronaut-core | closed | add micronaut-security-annotations to bom | relates-to: build | Security related annotations have been moved to its own dependency. However, that dependency [micronaut-security-annotations](https://mvnrepository.com/artifact/io.micronaut/micronaut-security-annotations) is not in the bom. | 1.0 | add micronaut-security-annotations to bom - Security related annotations have been moved to its own dependency. However, that dependency [micronaut-security-annotations](https://mvnrepository.com/artifact/io.micronaut/micronaut-security-annotations) is not in the bom. | non_priority | add micronaut security annotations to bom security related annotations have been moved to its own dependency however that dependency is not in the bom | 0 |
26,985 | 11,420,865,500 | IssuesEvent | 2020-02-03 10:56:37 | CasualGaming/studlan | https://api.github.com/repos/CasualGaming/studlan | opened | Logout vulnerable to CSRF | Bug Security | ### Feature or Bug?
- [ ] Feature
- [x] Bug
### Description
Logout is just a link. It doesn't matter that much for logout functionality, but might as well fix it. | True | Logout vulnerable to CSRF - ### Feature or Bug?
- [ ] Feature
- [x] Bug
### Description
Logout is just a link. It doesn't matter that much for logout functionality, but might as well fix it. | non_priority | logout vulnerable to csrf feature or bug feature bug description logout is just a link it doesn t matter that much for logout functionality but might as well fix it | 0 |
128,051 | 10,513,029,717 | IssuesEvent | 2019-09-27 19:27:43 | helm/helm | https://api.github.com/repos/helm/helm | closed | Test pod not deleted with helm.sh/hook-delete-policy | area/helm-test feature | I have a chart with tests. The test pod is annotated as follows:
```yaml
annotations:
helm.sh/hook: test-success
helm.sh/hook-delete-policy: hook-succeeded
```
I would expect the pod to be deleted once the test has run successfully. This is, however, not the case.
```
$ helm version
Client: &version.Version{SemVer:"v2.7.2", GitCommit:"8478fb4fc723885b155c924d1c8c410b7a9444e6", GitTreeState:"clean"}
Server: &version.Version{SemVer:"v2.7.2", GitCommit:"8478fb4fc723885b155c924d1c8c410b7a9444e6", GitTreeState:"clean"}
```
| 1.0 | Test pod not deleted with helm.sh/hook-delete-policy - I have a chart with tests. The test pod is annotated as follows:
```yaml
annotations:
helm.sh/hook: test-success
helm.sh/hook-delete-policy: hook-succeeded
```
I would expect the pod to be deleted once the test has run successfully. This is, however, not the case.
```
$ helm version
Client: &version.Version{SemVer:"v2.7.2", GitCommit:"8478fb4fc723885b155c924d1c8c410b7a9444e6", GitTreeState:"clean"}
Server: &version.Version{SemVer:"v2.7.2", GitCommit:"8478fb4fc723885b155c924d1c8c410b7a9444e6", GitTreeState:"clean"}
```
| non_priority | test pod not deleted with helm sh hook delete policy i have a chart with tests the test pod is annotated as follows yaml annotations helm sh hook test success helm sh hook delete policy hook succeeded i would expect the pod to be deleted once the test has run successfully this is however not the case helm version client version version semver gitcommit gittreestate clean server version version semver gitcommit gittreestate clean | 0 |
66,376 | 14,768,188,271 | IssuesEvent | 2021-01-10 10:50:48 | YauheniPo/Elements_Test_Framework | https://api.github.com/repos/YauheniPo/Elements_Test_Framework | opened | CVE-2019-10094 (High) detected in tika-core-1.20.jar | security vulnerability | ## CVE-2019-10094 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>tika-core-1.20.jar</b></p></summary>
<p>This is the core Apache Tika™ toolkit library from which all other modules inherit functionality. It also
includes the core facades for the Tika API.</p>
<p>Library home page: <a href="http://tika.apache.org/">http://tika.apache.org/</a></p>
<p>Path to dependency file: Elements_Test_Framework/pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/org/apache/tika/tika-core/1.20/tika-core-1.20.jar</p>
<p>
Dependency Hierarchy:
- allure-testng-2.10.0.jar (Root Library)
- allure-java-commons-2.10.0.jar
- :x: **tika-core-1.20.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/YauheniPo/Elements_Test_Framework/commit/b6525683a2173ae823218926b6f8d80d10c5d61f">b6525683a2173ae823218926b6f8d80d10c5d61f</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>
A carefully crafted package/compressed file that, when unzipped/uncompressed yields the same file (a quine), causes a StackOverflowError in Apache Tika's RecursiveParserWrapper in versions 1.7-1.21. Apache Tika users should upgrade to 1.22 or later.
<p>Publish Date: 2019-08-02
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-10094>CVE-2019-10094</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.8</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: 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>
</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-10093">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-10093</a></p>
<p>Release Date: 2019-08-02</p>
<p>Fix Resolution: 1.22</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-10094 (High) detected in tika-core-1.20.jar - ## CVE-2019-10094 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>tika-core-1.20.jar</b></p></summary>
<p>This is the core Apache Tika™ toolkit library from which all other modules inherit functionality. It also
includes the core facades for the Tika API.</p>
<p>Library home page: <a href="http://tika.apache.org/">http://tika.apache.org/</a></p>
<p>Path to dependency file: Elements_Test_Framework/pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/org/apache/tika/tika-core/1.20/tika-core-1.20.jar</p>
<p>
Dependency Hierarchy:
- allure-testng-2.10.0.jar (Root Library)
- allure-java-commons-2.10.0.jar
- :x: **tika-core-1.20.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/YauheniPo/Elements_Test_Framework/commit/b6525683a2173ae823218926b6f8d80d10c5d61f">b6525683a2173ae823218926b6f8d80d10c5d61f</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>
A carefully crafted package/compressed file that, when unzipped/uncompressed yields the same file (a quine), causes a StackOverflowError in Apache Tika's RecursiveParserWrapper in versions 1.7-1.21. Apache Tika users should upgrade to 1.22 or later.
<p>Publish Date: 2019-08-02
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-10094>CVE-2019-10094</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.8</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: 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>
</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-10093">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-10093</a></p>
<p>Release Date: 2019-08-02</p>
<p>Fix Resolution: 1.22</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 tika core jar cve high severity vulnerability vulnerable library tika core jar this is the core apache tika™ toolkit library from which all other modules inherit functionality it also includes the core facades for the tika api library home page a href path to dependency file elements test framework pom xml path to vulnerable library home wss scanner repository org apache tika tika core tika core jar dependency hierarchy allure testng jar root library allure java commons jar x tika core jar vulnerable library found in head commit a href found in base branch master vulnerability details a carefully crafted package compressed file that when unzipped uncompressed yields the same file a quine causes a stackoverflowerror in apache tika s recursiveparserwrapper in versions apache tika users should upgrade to or later 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 high availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution step up your open source security game with whitesource | 0 |
210,190 | 23,740,045,463 | IssuesEvent | 2022-08-31 11:37:55 | w3c/wot-profile | https://api.github.com/repos/w3c/wot-profile | opened | Remove reference to security best practices document | security | Task: Update the references to only reference the "Security guidelines" document. | True | Remove reference to security best practices document - Task: Update the references to only reference the "Security guidelines" document. | non_priority | remove reference to security best practices document task update the references to only reference the security guidelines document | 0 |
54,578 | 11,261,153,556 | IssuesEvent | 2020-01-13 12:06:13 | Regalis11/Barotrauma | https://api.github.com/repos/Regalis11/Barotrauma | closed | [Bug] [0.9.6.0] Docking port docks on the wrong side in certain applications. | Bug Code | - [X] I have searched the issue tracker to check if the issue has already been reported.
**Description**
In campaign, after the first mission, subsequent missions will have shuttle docked on the wrong side of the docking port. This seems to happen when the docking port is recessed into the main body of the submarine.
**Steps To Reproduce**
Have a docking port inside a recessed area of the submarine with shuttle attached. Start campaign, play through the first mission. Select the next mission and inspect the docking port.
**Version**
Windows 1903
Barotrauma 0.9.6.0
**Additional information**
Imgur links showing the issue, it's easier shown than explained in words.
https://i.imgur.com/BsylDpX.png
https://i.imgur.com/FvGXxZV.png
Attached is a zip of the submarines used in testing, along with the campaign save files the bug happened on for those submarines.
[Docking Port Bug.zip](https://github.com/Regalis11/Barotrauma/files/4014428/Docking.Port.Bug.zip)
| 1.0 | [Bug] [0.9.6.0] Docking port docks on the wrong side in certain applications. - - [X] I have searched the issue tracker to check if the issue has already been reported.
**Description**
In campaign, after the first mission, subsequent missions will have shuttle docked on the wrong side of the docking port. This seems to happen when the docking port is recessed into the main body of the submarine.
**Steps To Reproduce**
Have a docking port inside a recessed area of the submarine with shuttle attached. Start campaign, play through the first mission. Select the next mission and inspect the docking port.
**Version**
Windows 1903
Barotrauma 0.9.6.0
**Additional information**
Imgur links showing the issue, it's easier shown than explained in words.
https://i.imgur.com/BsylDpX.png
https://i.imgur.com/FvGXxZV.png
Attached is a zip of the submarines used in testing, along with the campaign save files the bug happened on for those submarines.
[Docking Port Bug.zip](https://github.com/Regalis11/Barotrauma/files/4014428/Docking.Port.Bug.zip)
| non_priority | docking port docks on the wrong side in certain applications i have searched the issue tracker to check if the issue has already been reported description in campaign after the first mission subsequent missions will have shuttle docked on the wrong side of the docking port this seems to happen when the docking port is recessed into the main body of the submarine steps to reproduce have a docking port inside a recessed area of the submarine with shuttle attached start campaign play through the first mission select the next mission and inspect the docking port version windows barotrauma additional information imgur links showing the issue it s easier shown than explained in words attached is a zip of the submarines used in testing along with the campaign save files the bug happened on for those submarines | 0 |
239,598 | 26,231,943,169 | IssuesEvent | 2023-01-05 01:32:34 | satishmukundan/WebGoat | https://api.github.com/repos/satishmukundan/WebGoat | opened | CVE-2022-1471 (High) detected in snakeyaml-1.28.jar | security vulnerability | ## CVE-2022-1471 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>snakeyaml-1.28.jar</b></p></summary>
<p>YAML 1.1 parser and emitter for Java</p>
<p>Library home page: <a href="http://www.snakeyaml.org">http://www.snakeyaml.org</a></p>
<p>Path to dependency file: /docker/pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/org/yaml/snakeyaml/1.28/snakeyaml-1.28.jar,/home/wss-scanner/.m2/repository/org/yaml/snakeyaml/1.28/snakeyaml-1.28.jar,/home/wss-scanner/.m2/repository/org/yaml/snakeyaml/1.28/snakeyaml-1.28.jar</p>
<p>
Dependency Hierarchy:
- spring-boot-starter-validation-2.5.4.jar (Root Library)
- spring-boot-starter-2.5.4.jar
- :x: **snakeyaml-1.28.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/satishmukundan/WebGoat/commit/c4196e8da2299c385e53198c98fccad8aa5ceee8">c4196e8da2299c385e53198c98fccad8aa5ceee8</a></p>
<p>Found in base branch: <b>develop</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>
SnakeYaml's Constructor() class does not restrict types which can be instantiated during deserialization. Deserializing yaml content provided by an attacker can lead to remote code execution. We recommend using SnakeYaml's SafeConsturctor when parsing untrusted content to restrict deserialization.
<p>Publish Date: 2022-12-01
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-1471>CVE-2022-1471</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>
***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | CVE-2022-1471 (High) detected in snakeyaml-1.28.jar - ## CVE-2022-1471 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>snakeyaml-1.28.jar</b></p></summary>
<p>YAML 1.1 parser and emitter for Java</p>
<p>Library home page: <a href="http://www.snakeyaml.org">http://www.snakeyaml.org</a></p>
<p>Path to dependency file: /docker/pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/org/yaml/snakeyaml/1.28/snakeyaml-1.28.jar,/home/wss-scanner/.m2/repository/org/yaml/snakeyaml/1.28/snakeyaml-1.28.jar,/home/wss-scanner/.m2/repository/org/yaml/snakeyaml/1.28/snakeyaml-1.28.jar</p>
<p>
Dependency Hierarchy:
- spring-boot-starter-validation-2.5.4.jar (Root Library)
- spring-boot-starter-2.5.4.jar
- :x: **snakeyaml-1.28.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/satishmukundan/WebGoat/commit/c4196e8da2299c385e53198c98fccad8aa5ceee8">c4196e8da2299c385e53198c98fccad8aa5ceee8</a></p>
<p>Found in base branch: <b>develop</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>
SnakeYaml's Constructor() class does not restrict types which can be instantiated during deserialization. Deserializing yaml content provided by an attacker can lead to remote code execution. We recommend using SnakeYaml's SafeConsturctor when parsing untrusted content to restrict deserialization.
<p>Publish Date: 2022-12-01
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-1471>CVE-2022-1471</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>
***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_priority | cve high detected in snakeyaml jar cve high severity vulnerability vulnerable library snakeyaml jar yaml parser and emitter for java library home page a href path to dependency file docker pom xml path to vulnerable library home wss scanner repository org yaml snakeyaml snakeyaml jar home wss scanner repository org yaml snakeyaml snakeyaml jar home wss scanner repository org yaml snakeyaml snakeyaml jar dependency hierarchy spring boot starter validation jar root library spring boot starter jar x snakeyaml jar vulnerable library found in head commit a href found in base branch develop vulnerability details snakeyaml s constructor class does not restrict types which can be instantiated during deserialization deserializing yaml content provided by an attacker can lead to remote code execution we recommend using snakeyaml s safeconsturctor when parsing untrusted content to restrict deserialization 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 step up your open source security game with mend | 0 |
136,281 | 11,045,277,492 | IssuesEvent | 2019-12-09 14:50:55 | raiden-network/raiden | https://api.github.com/repos/raiden-network/raiden | closed | PFS1 Fails in Assert Task | Component / Scenario Player Flag / Testing |
## Problem Definition
Scenario in a nutshell:
node0: `0x754e41dBd78F7B2B6C88d6Ec4313986e406a0F45`
node1: `0x8525528Ee6AbC8F177048515b1884c334802E02E`
node3: `0xC86383586EDa066133120c94a78b3C75DD62a572`
node4: `0xE8FF5e3433ccf7B09b91981C305EB65F8aD8847a`
```
{
"task": "<AssertTask: {'from': 1, 'to': 0, 'total_deposit': 1000000000000000000, 'balance': 1001000000000000000}>",
"event": "Task errored",
"logger": "scenario_player.tasks.base",
"level": "error",
"timestamp": "2019-12-09 03:55:38.221896",
"exception": "Traceback (most recent call last):\n File \"/usr/local/lib/python3.7/site-packages/scenario_player/tasks/channels.py\", line 192, in _run\n sleep(1)\n File \"/usr/local/lib/python3.7/site-packages/gevent/hub.py\", line 159, in sleep\n hub.wait(t)\n File \"src/gevent/_hub_primitives.py\", line 46, in gevent.__hub_primitives.WaitOperationsGreenlet.wait\n File \"src/gevent/_hub_primitives.py\", line 55, in gevent.__hub_primitives.WaitOperationsGreenlet.wait\n File \"src/gevent/_waiter.py\", line 151, in gevent.__waiter.Waiter.get\n File \"src/gevent/_greenlet_primitives.py\", line 59, in gevent.__greenlet_primitives.SwitchOutGreenletWithLoop.switch\n File \"src/gevent/_greenlet_primitives.py\", line 59, in gevent.__greenlet_primitives.SwitchOutGreenletWithLoop.switch\n File \"src/gevent/_greenlet_primitives.py\", line 63, in gevent.__greenlet_primitives.SwitchOutGreenletWithLoop.switch\n File \"src/gevent/__greenlet_primitives.pxd\", line 35, in gevent.__greenlet_primitives._greenlet_switch\ngevent.timeout.Timeout: 30 seconds\n\nDuring handling of the above exception, another exception occurred:\n\nTraceback (most recent call last):\n File \"/usr/local/lib/python3.7/site-packages/scenario_player/tasks/base.py\", line 74, in __call__\n return self._run(*args, **kwargs)\n File \"/usr/local/lib/python3.7/site-packages/scenario_player/tasks/channels.py\", line 194, in _run\n raise exception\n File \"/usr/local/lib/python3.7/site-packages/scenario_player/tasks/channels.py\", line 185, in _run\n result = super()._run(*args, **kwargs)\n File \"/usr/local/lib/python3.7/site-packages/scenario_player/tasks/api_base.py\", line 70, in _run\n return self._process_response(response_dict)\n File \"/usr/local/lib/python3.7/site-packages/scenario_player/tasks/channels.py\", line 170, in _process_response\n f'Value mismatch for \"{field}\". '\nscenario_player.exceptions.legacy.ScenarioAssertionError: Value mismatch for \"balance\". Should: \"1001000000000000000\" Is: \"1000000000000000\" Channel: {'state': 'opened', 'channel_identifier': '5282', 'balance': '1000000000000000', 'token_address': '0x62083c80353Df771426D209eF578619EE68D5C7A', 'total_deposit': '0', 'partner_address': '0x754e41dBd78F7B2B6C88d6Ec4313986e406a0F45', 'total_withdraw': '0', 'reveal_timeout': '50', 'token_network_address': '0xDa1fBc048f503635950058953f5c60FC1F564ee6', 'settle_timeout': '500'}"
}
```
What does the exception say
1. Fails at line 58
`- assert: {from: 1, to: 0, total_deposit: 1_000_000_000_000_000_000, balance: 1_001_000_000_000_000_000}`
2. `Value mismatch for \"balance\". Should: \"1001000000000000000\" Is: \"1000000000000000\"`
where:
`1_001_000_000_000_000_000`: Should
xxxx`1_000_000_000_000_000`: Is
3. Current state of the channel
```
Channel:
{
"state": "opened",
"channel_identifier": "5282",
"balance": "1000000000000000",
"token_address": "0x62083c80353Df771426D209eF578619EE68D5C7A",
"total_deposit": "0",
"partner_address": "0x754e41dBd78F7B2B6C88d6Ec4313986e406a0F45",
"total_withdraw": "0",
"reveal_timeout": "50",
"token_network_address": "0xDa1fBc048f503635950058953f5c60FC1F564ee6",
"settle_timeout": "500"
}
```
[pfs1_get_a_simple_path_2019_12_09.tar.gz](https://github.com/raiden-network/raiden/files/3938479/pfs1_get_a_simple_path_2019_12_09.tar.gz)
| 1.0 | PFS1 Fails in Assert Task -
## Problem Definition
Scenario in a nutshell:
node0: `0x754e41dBd78F7B2B6C88d6Ec4313986e406a0F45`
node1: `0x8525528Ee6AbC8F177048515b1884c334802E02E`
node3: `0xC86383586EDa066133120c94a78b3C75DD62a572`
node4: `0xE8FF5e3433ccf7B09b91981C305EB65F8aD8847a`
```
{
"task": "<AssertTask: {'from': 1, 'to': 0, 'total_deposit': 1000000000000000000, 'balance': 1001000000000000000}>",
"event": "Task errored",
"logger": "scenario_player.tasks.base",
"level": "error",
"timestamp": "2019-12-09 03:55:38.221896",
"exception": "Traceback (most recent call last):\n File \"/usr/local/lib/python3.7/site-packages/scenario_player/tasks/channels.py\", line 192, in _run\n sleep(1)\n File \"/usr/local/lib/python3.7/site-packages/gevent/hub.py\", line 159, in sleep\n hub.wait(t)\n File \"src/gevent/_hub_primitives.py\", line 46, in gevent.__hub_primitives.WaitOperationsGreenlet.wait\n File \"src/gevent/_hub_primitives.py\", line 55, in gevent.__hub_primitives.WaitOperationsGreenlet.wait\n File \"src/gevent/_waiter.py\", line 151, in gevent.__waiter.Waiter.get\n File \"src/gevent/_greenlet_primitives.py\", line 59, in gevent.__greenlet_primitives.SwitchOutGreenletWithLoop.switch\n File \"src/gevent/_greenlet_primitives.py\", line 59, in gevent.__greenlet_primitives.SwitchOutGreenletWithLoop.switch\n File \"src/gevent/_greenlet_primitives.py\", line 63, in gevent.__greenlet_primitives.SwitchOutGreenletWithLoop.switch\n File \"src/gevent/__greenlet_primitives.pxd\", line 35, in gevent.__greenlet_primitives._greenlet_switch\ngevent.timeout.Timeout: 30 seconds\n\nDuring handling of the above exception, another exception occurred:\n\nTraceback (most recent call last):\n File \"/usr/local/lib/python3.7/site-packages/scenario_player/tasks/base.py\", line 74, in __call__\n return self._run(*args, **kwargs)\n File \"/usr/local/lib/python3.7/site-packages/scenario_player/tasks/channels.py\", line 194, in _run\n raise exception\n File \"/usr/local/lib/python3.7/site-packages/scenario_player/tasks/channels.py\", line 185, in _run\n result = super()._run(*args, **kwargs)\n File \"/usr/local/lib/python3.7/site-packages/scenario_player/tasks/api_base.py\", line 70, in _run\n return self._process_response(response_dict)\n File \"/usr/local/lib/python3.7/site-packages/scenario_player/tasks/channels.py\", line 170, in _process_response\n f'Value mismatch for \"{field}\". '\nscenario_player.exceptions.legacy.ScenarioAssertionError: Value mismatch for \"balance\". Should: \"1001000000000000000\" Is: \"1000000000000000\" Channel: {'state': 'opened', 'channel_identifier': '5282', 'balance': '1000000000000000', 'token_address': '0x62083c80353Df771426D209eF578619EE68D5C7A', 'total_deposit': '0', 'partner_address': '0x754e41dBd78F7B2B6C88d6Ec4313986e406a0F45', 'total_withdraw': '0', 'reveal_timeout': '50', 'token_network_address': '0xDa1fBc048f503635950058953f5c60FC1F564ee6', 'settle_timeout': '500'}"
}
```
What does the exception say
1. Fails at line 58
`- assert: {from: 1, to: 0, total_deposit: 1_000_000_000_000_000_000, balance: 1_001_000_000_000_000_000}`
2. `Value mismatch for \"balance\". Should: \"1001000000000000000\" Is: \"1000000000000000\"`
where:
`1_001_000_000_000_000_000`: Should
xxxx`1_000_000_000_000_000`: Is
3. Current state of the channel
```
Channel:
{
"state": "opened",
"channel_identifier": "5282",
"balance": "1000000000000000",
"token_address": "0x62083c80353Df771426D209eF578619EE68D5C7A",
"total_deposit": "0",
"partner_address": "0x754e41dBd78F7B2B6C88d6Ec4313986e406a0F45",
"total_withdraw": "0",
"reveal_timeout": "50",
"token_network_address": "0xDa1fBc048f503635950058953f5c60FC1F564ee6",
"settle_timeout": "500"
}
```
[pfs1_get_a_simple_path_2019_12_09.tar.gz](https://github.com/raiden-network/raiden/files/3938479/pfs1_get_a_simple_path_2019_12_09.tar.gz)
| non_priority | fails in assert task problem definition scenario in a nutshell task event task errored logger scenario player tasks base level error timestamp exception traceback most recent call last n file usr local lib site packages scenario player tasks channels py line in run n sleep n file usr local lib site packages gevent hub py line in sleep n hub wait t n file src gevent hub primitives py line in gevent hub primitives waitoperationsgreenlet wait n file src gevent hub primitives py line in gevent hub primitives waitoperationsgreenlet wait n file src gevent waiter py line in gevent waiter waiter get n file src gevent greenlet primitives py line in gevent greenlet primitives switchoutgreenletwithloop switch n file src gevent greenlet primitives py line in gevent greenlet primitives switchoutgreenletwithloop switch n file src gevent greenlet primitives py line in gevent greenlet primitives switchoutgreenletwithloop switch n file src gevent greenlet primitives pxd line in gevent greenlet primitives greenlet switch ngevent timeout timeout seconds n nduring handling of the above exception another exception occurred n ntraceback most recent call last n file usr local lib site packages scenario player tasks base py line in call n return self run args kwargs n file usr local lib site packages scenario player tasks channels py line in run n raise exception n file usr local lib site packages scenario player tasks channels py line in run n result super run args kwargs n file usr local lib site packages scenario player tasks api base py line in run n return self process response response dict n file usr local lib site packages scenario player tasks channels py line in process response n f value mismatch for field nscenario player exceptions legacy scenarioassertionerror value mismatch for balance should is channel state opened channel identifier balance token address total deposit partner address total withdraw reveal timeout token network address settle timeout what does the exception say fails at line assert from to total deposit balance value mismatch for balance should is where should xxxx is current state of the channel channel state opened channel identifier balance token address total deposit partner address total withdraw reveal timeout token network address settle timeout | 0 |
11,236 | 7,122,531,161 | IssuesEvent | 2018-01-19 12:12:20 | coblo/gui-demo | https://api.github.com/repos/coblo/gui-demo | opened | Add support for private/public transaction comments/references. | enhancement feature usability | Currently the "comment" field of a transaction is only stored in the users local wallet. These comments are lost if the user recovers his account on a fresh installation. I propose to support at least 2 more types of transaction comments:
Public: Publicly readable comments via transaction metadata or custom stream
Private: Comment only readable by sender(s)/receiver(s) via encryption. | True | Add support for private/public transaction comments/references. - Currently the "comment" field of a transaction is only stored in the users local wallet. These comments are lost if the user recovers his account on a fresh installation. I propose to support at least 2 more types of transaction comments:
Public: Publicly readable comments via transaction metadata or custom stream
Private: Comment only readable by sender(s)/receiver(s) via encryption. | non_priority | add support for private public transaction comments references currently the comment field of a transaction is only stored in the users local wallet these comments are lost if the user recovers his account on a fresh installation i propose to support at least more types of transaction comments public publicly readable comments via transaction metadata or custom stream private comment only readable by sender s receiver s via encryption | 0 |
124,416 | 26,453,125,041 | IssuesEvent | 2023-01-16 12:43:40 | Regalis11/Barotrauma | https://api.github.com/repos/Regalis11/Barotrauma | closed | [Factions] Guardian weapon never despawns if the guardian's arm gets severed | Bug Code | ### Disclaimers
- [X] I have searched the issue tracker to check if the issue has already been reported.
- [ ] My issue happened while using mods.
### What happened?
During a ruin mission, one of the Ruin Guardians actively attempted to board the submarine (successfully) and was killed inside. The steam cannon part of its arm was severed. Over the course of 16 hours and two separate sessions, the limb never despawned as captured below.
_Figure 1. First instance of severed limb._
_Figure 2. Another player encounters the severed limb._
_Figure 3. A second instance of the severed limb, encountered five nodes after instance one._
_Figure 4. The lovely Jade Harley's highlight of the Alien Ruin arm from the previous image._
_Figure 5. The same limb being on the sub a day later after the server had been closed and reopened._
It is also important to note that the Guardian boarding the submarine might not be a bug. As of 0.19.14.0, it cannot board the submarine. This may have been changed during one of the unstable builds.
### Reproduction steps
_No response_
### Bug prevalence
Happens regularly
### Version
Faction/endgame test branch
### -
_No response_
### Which operating system did you encounter this bug on?
Windows
### Relevant error messages and crash reports
_No response_ | 1.0 | [Factions] Guardian weapon never despawns if the guardian's arm gets severed - ### Disclaimers
- [X] I have searched the issue tracker to check if the issue has already been reported.
- [ ] My issue happened while using mods.
### What happened?
During a ruin mission, one of the Ruin Guardians actively attempted to board the submarine (successfully) and was killed inside. The steam cannon part of its arm was severed. Over the course of 16 hours and two separate sessions, the limb never despawned as captured below.
_Figure 1. First instance of severed limb._
_Figure 2. Another player encounters the severed limb._
_Figure 3. A second instance of the severed limb, encountered five nodes after instance one._
_Figure 4. The lovely Jade Harley's highlight of the Alien Ruin arm from the previous image._
_Figure 5. The same limb being on the sub a day later after the server had been closed and reopened._
It is also important to note that the Guardian boarding the submarine might not be a bug. As of 0.19.14.0, it cannot board the submarine. This may have been changed during one of the unstable builds.
### Reproduction steps
_No response_
### Bug prevalence
Happens regularly
### Version
Faction/endgame test branch
### -
_No response_
### Which operating system did you encounter this bug on?
Windows
### Relevant error messages and crash reports
_No response_ | non_priority | guardian weapon never despawns if the guardian s arm gets severed disclaimers i have searched the issue tracker to check if the issue has already been reported my issue happened while using mods what happened during a ruin mission one of the ruin guardians actively attempted to board the submarine successfully and was killed inside the steam cannon part of its arm was severed over the course of hours and two separate sessions the limb never despawned as captured below figure first instance of severed limb figure another player encounters the severed limb figure a second instance of the severed limb encountered five nodes after instance one figure the lovely jade harley s highlight of the alien ruin arm from the previous image figure the same limb being on the sub a day later after the server had been closed and reopened it is also important to note that the guardian boarding the submarine might not be a bug as of it cannot board the submarine this may have been changed during one of the unstable builds reproduction steps no response bug prevalence happens regularly version faction endgame test branch no response which operating system did you encounter this bug on windows relevant error messages and crash reports no response | 0 |
35,576 | 12,360,594,556 | IssuesEvent | 2020-05-17 15:55:04 | CephalonTobran/web | https://api.github.com/repos/CephalonTobran/web | opened | CVE-2019-11358 (Medium) detected in jquery-2.1.4.min.js | security vulnerability | ## CVE-2019-11358 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>jquery-2.1.4.min.js</b></p></summary>
<p>JavaScript library for DOM operations</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/jquery/2.1.4/jquery.min.js">https://cdnjs.cloudflare.com/ajax/libs/jquery/2.1.4/jquery.min.js</a></p>
<p>Path to dependency file: /tmp/ws-scm/web/node_modules/js-base64/.attic/test-moment/index.html</p>
<p>Path to vulnerable library: /web/node_modules/js-base64/.attic/test-moment/index.html</p>
<p>
Dependency Hierarchy:
- :x: **jquery-2.1.4.min.js** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/CephalonTobran/web/commit/6481ee08faa914d71937f6c7abc92e6a96c8bca0">6481ee08faa914d71937f6c7abc92e6a96c8bca0</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>
jQuery before 3.4.0, as used in Drupal, Backdrop CMS, and other products, mishandles jQuery.extend(true, {}, ...) because of Object.prototype pollution. If an unsanitized source object contained an enumerable __proto__ property, it could extend the native Object.prototype.
<p>Publish Date: 2019-04-20
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-11358>CVE-2019-11358</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>6.1</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: Low
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-11358">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-11358</a></p>
<p>Release Date: 2019-04-20</p>
<p>Fix Resolution: 3.4.0</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | CVE-2019-11358 (Medium) detected in jquery-2.1.4.min.js - ## CVE-2019-11358 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>jquery-2.1.4.min.js</b></p></summary>
<p>JavaScript library for DOM operations</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/jquery/2.1.4/jquery.min.js">https://cdnjs.cloudflare.com/ajax/libs/jquery/2.1.4/jquery.min.js</a></p>
<p>Path to dependency file: /tmp/ws-scm/web/node_modules/js-base64/.attic/test-moment/index.html</p>
<p>Path to vulnerable library: /web/node_modules/js-base64/.attic/test-moment/index.html</p>
<p>
Dependency Hierarchy:
- :x: **jquery-2.1.4.min.js** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/CephalonTobran/web/commit/6481ee08faa914d71937f6c7abc92e6a96c8bca0">6481ee08faa914d71937f6c7abc92e6a96c8bca0</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>
jQuery before 3.4.0, as used in Drupal, Backdrop CMS, and other products, mishandles jQuery.extend(true, {}, ...) because of Object.prototype pollution. If an unsanitized source object contained an enumerable __proto__ property, it could extend the native Object.prototype.
<p>Publish Date: 2019-04-20
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-11358>CVE-2019-11358</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>6.1</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: Low
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-11358">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-11358</a></p>
<p>Release Date: 2019-04-20</p>
<p>Fix Resolution: 3.4.0</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_priority | cve medium detected in jquery min js cve medium severity vulnerability vulnerable library jquery min js javascript library for dom operations library home page a href path to dependency file tmp ws scm web node modules js attic test moment index html path to vulnerable library web node modules js attic test moment index html dependency hierarchy x jquery min js vulnerable library found in head commit a href vulnerability details jquery before as used in drupal backdrop cms and other products mishandles jquery extend true because of object prototype pollution if an unsanitized source object contained an enumerable proto property it could extend the native object prototype publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction required scope changed impact metrics confidentiality impact low integrity impact low availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution step up your open source security game with whitesource | 0 |
16,492 | 4,055,478,400 | IssuesEvent | 2016-05-24 15:35:30 | Kinto/kinto | https://api.github.com/repos/Kinto/kinto | closed | cross-link Kinto docs to Cliquet docs instead of copying | documentation enhancement | Use the Sphinx "intersphinx" plugin to link to Cliquet documentation in a disciplined way rather than just copying a random amount of documentation out of another project. Most of the Kinto documentation should be defined with reference to corresponding documentation in Cliquet -- for example, Kinto permissions should link to Cliquet permissions, and Kinto records should link to Cliquet resources.
[N.B. that of course this might depend on the outcome of https://github.com/mozilla-services/cliquet/issues/687.] | 1.0 | cross-link Kinto docs to Cliquet docs instead of copying - Use the Sphinx "intersphinx" plugin to link to Cliquet documentation in a disciplined way rather than just copying a random amount of documentation out of another project. Most of the Kinto documentation should be defined with reference to corresponding documentation in Cliquet -- for example, Kinto permissions should link to Cliquet permissions, and Kinto records should link to Cliquet resources.
[N.B. that of course this might depend on the outcome of https://github.com/mozilla-services/cliquet/issues/687.] | non_priority | cross link kinto docs to cliquet docs instead of copying use the sphinx intersphinx plugin to link to cliquet documentation in a disciplined way rather than just copying a random amount of documentation out of another project most of the kinto documentation should be defined with reference to corresponding documentation in cliquet for example kinto permissions should link to cliquet permissions and kinto records should link to cliquet resources | 0 |
2,942 | 2,651,700,728 | IssuesEvent | 2015-03-16 13:28:17 | MysingleClairesimon/2ABEVKWLYVY7CISYZTMBSQI7 | https://api.github.com/repos/MysingleClairesimon/2ABEVKWLYVY7CISYZTMBSQI7 | closed | frgl4GhKz2EJFc4+KM+j6iQzgD28U9vCCW0JoixUKin/jB5E7sg6dNegIDHW/LetDy27UB8iHriTMBi1IcE+B/FDfruAeTefNze2ox5D5eCMurZ0Imk7nYJ1xZ+QlFZ0QXnKirjceIOdwWVgIrX8o0vz+D6q4xhve0bmZzHho/c= | design | SYbLkRxjd/tog1DcK2m6VNkPZ1EXmoTjjhgy/WginyTYNChaQ2TV6GEWPx4GVzofx+j/wj8NCTOe17dj0zjdgvKAzstvNWpHTQEZTGYNHz/KmTLVn67/nnveCs3LIgo9yepgoFQxBAHd/fiRbmmH8737QeUoNbMfHHdfUEXpoD3oz7Ik4b8XOKAeuttKn2N67ETcEnD8/CCXuyQ4g1EFZeGUoCsuuN77S5W3xjsk3q/fVrYtW0dGFdZTcJmjcS532Q9nUReahOOOGDL9aCKfJNg0KFpDZNXoYRY/HgZXOh/H6P/CPw0JM57Xt2PTON2CNbOuK/nfNmWP9NeHUHbfTvRZY6rxpq551pAbd1k5teLg6OJ/S+gH8CfJxkErn73nBVOtz8zL4bskS9GZGCFgZTHixwtGPeVhGNZ3KumCf0ETIqO/aZyQO2Wwiv+gw2Hadcx35wl5uMfY6AzIUMEkxhhpqQoYArfFab74NE3WwshCbtEe1rrkz8rOifbENxWKAfWx5i3SUc+e7bFS7LTLfjzNbKzIAYbaQNpuEpNWXfcrgwYJkKpRoNXJBIA+iLBTOjubaF6sTo9uEQbAq+29mU+6Eo3qyJ7tZrR7tufMWhM9p8o5SZGU/UZeA6FFUJocVUItH+n0+QEnVSekIeDL7S+haEN9uz+Rs3JGBIFlCC2rNUDNxolz3fGWjbc/CIp+lnsRpx4n6wvu2C/Eqz2imopnxEXxQsM+hSJ64L3uU+bloMA88tYUHqk91/AP4QwQLVbFRIYYBEL6gCX25AILAbOuRtcTor92TpQbhPTDW/v3AkoxrPf9c6JRfkjielylhsd0jxfurAkbmktYbg2ZxZox7Lh4p2hcGx7rbfaiGQ0YdVsZztOJkiBz0JawGCYVESJApUK50tGrAu6qzy6xQrPh0ULoVxceDblGgP+an/61uA9uZHJAOd7C5nuzXquR | 1.0 | frgl4GhKz2EJFc4+KM+j6iQzgD28U9vCCW0JoixUKin/jB5E7sg6dNegIDHW/LetDy27UB8iHriTMBi1IcE+B/FDfruAeTefNze2ox5D5eCMurZ0Imk7nYJ1xZ+QlFZ0QXnKirjceIOdwWVgIrX8o0vz+D6q4xhve0bmZzHho/c= - SYbLkRxjd/tog1DcK2m6VNkPZ1EXmoTjjhgy/WginyTYNChaQ2TV6GEWPx4GVzofx+j/wj8NCTOe17dj0zjdgvKAzstvNWpHTQEZTGYNHz/KmTLVn67/nnveCs3LIgo9yepgoFQxBAHd/fiRbmmH8737QeUoNbMfHHdfUEXpoD3oz7Ik4b8XOKAeuttKn2N67ETcEnD8/CCXuyQ4g1EFZeGUoCsuuN77S5W3xjsk3q/fVrYtW0dGFdZTcJmjcS532Q9nUReahOOOGDL9aCKfJNg0KFpDZNXoYRY/HgZXOh/H6P/CPw0JM57Xt2PTON2CNbOuK/nfNmWP9NeHUHbfTvRZY6rxpq551pAbd1k5teLg6OJ/S+gH8CfJxkErn73nBVOtz8zL4bskS9GZGCFgZTHixwtGPeVhGNZ3KumCf0ETIqO/aZyQO2Wwiv+gw2Hadcx35wl5uMfY6AzIUMEkxhhpqQoYArfFab74NE3WwshCbtEe1rrkz8rOifbENxWKAfWx5i3SUc+e7bFS7LTLfjzNbKzIAYbaQNpuEpNWXfcrgwYJkKpRoNXJBIA+iLBTOjubaF6sTo9uEQbAq+29mU+6Eo3qyJ7tZrR7tufMWhM9p8o5SZGU/UZeA6FFUJocVUItH+n0+QEnVSekIeDL7S+haEN9uz+Rs3JGBIFlCC2rNUDNxolz3fGWjbc/CIp+lnsRpx4n6wvu2C/Eqz2imopnxEXxQsM+hSJ64L3uU+bloMA88tYUHqk91/AP4QwQLVbFRIYYBEL6gCX25AILAbOuRtcTor92TpQbhPTDW/v3AkoxrPf9c6JRfkjielylhsd0jxfurAkbmktYbg2ZxZox7Lh4p2hcGx7rbfaiGQ0YdVsZztOJkiBz0JawGCYVESJApUK50tGrAu6qzy6xQrPh0ULoVxceDblGgP+an/61uA9uZHJAOd7C5nuzXquR | non_priority | km b c syblkrxjd j hgzxoh s cip an | 0 |
116,835 | 9,885,023,740 | IssuesEvent | 2019-06-25 00:35:57 | cmangos/issues | https://api.github.com/repos/cmangos/issues | closed | Zul'Aman Nalorakk Runs Through the Ground After a Reset | Info: Needs Testing System: NPC Type: Patch Version: TBC | **Current behavior**: When a group wipes or the boss is reset he runs through the ground, towards the edges of the map.
https://youtu.be/ruhN23pr-Aw
**Expected behavior**: Should go back to original position
**Steps to reproduce**:
1. .go c Nalorakk
2. Aggro then .die on yourself
3. Watch Nalorakk leave the game
**Client version**: 2.4.3
**Commit hash**: ea58208edb97ca294961ab2a2045cfda77860ec3
**Database version**: 5d467bd4dc3bb73a4a4b4ed8629050c8cf497309
**Operating system**: Windows Server 2012
[//]: # (If this is a crash report, include the crashlog from a debug build with https://gist.github.com/)
| 1.0 | Zul'Aman Nalorakk Runs Through the Ground After a Reset - **Current behavior**: When a group wipes or the boss is reset he runs through the ground, towards the edges of the map.
https://youtu.be/ruhN23pr-Aw
**Expected behavior**: Should go back to original position
**Steps to reproduce**:
1. .go c Nalorakk
2. Aggro then .die on yourself
3. Watch Nalorakk leave the game
**Client version**: 2.4.3
**Commit hash**: ea58208edb97ca294961ab2a2045cfda77860ec3
**Database version**: 5d467bd4dc3bb73a4a4b4ed8629050c8cf497309
**Operating system**: Windows Server 2012
[//]: # (If this is a crash report, include the crashlog from a debug build with https://gist.github.com/)
| non_priority | zul aman nalorakk runs through the ground after a reset current behavior when a group wipes or the boss is reset he runs through the ground towards the edges of the map expected behavior should go back to original position steps to reproduce go c nalorakk aggro then die on yourself watch nalorakk leave the game client version commit hash database version operating system windows server if this is a crash report include the crashlog from a debug build with | 0 |
44,682 | 7,124,978,920 | IssuesEvent | 2018-01-19 21:01:36 | JohnSundell/ImagineEngine | https://api.github.com/repos/JohnSundell/ImagineEngine | closed | README section with why this engine stands out | documentation improvement | I think it would be nice to have a section on the README file showing why someone would want to use ImagineEngine over cocos2d or SpriteKit.
Like, what characteristics make this one stand out, why you designed it. 😊 | 1.0 | README section with why this engine stands out - I think it would be nice to have a section on the README file showing why someone would want to use ImagineEngine over cocos2d or SpriteKit.
Like, what characteristics make this one stand out, why you designed it. 😊 | non_priority | readme section with why this engine stands out i think it would be nice to have a section on the readme file showing why someone would want to use imagineengine over or spritekit like what characteristics make this one stand out why you designed it 😊 | 0 |
294,192 | 25,351,640,094 | IssuesEvent | 2022-11-19 21:08:06 | avallete/yt-playlists-delete-enhancer | https://api.github.com/repos/avallete/yt-playlists-delete-enhancer | closed | CVE-2021-23382 (High) detected in postcss-7.0.35.tgz | security vulnerability safe to test | ## CVE-2021-23382 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>postcss-7.0.35.tgz</b></p></summary>
<p>Tool for transforming styles with JS plugins</p>
<p>Library home page: <a href="https://registry.npmjs.org/postcss/-/postcss-7.0.35.tgz">https://registry.npmjs.org/postcss/-/postcss-7.0.35.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/postcss/package.json</p>
<p>
Dependency Hierarchy:
- userscripter-1.4.0.tgz (Root Library)
- css-loader-3.6.0.tgz
- :x: **postcss-7.0.35.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/avallete/yt-playlists-delete-enhancer/commit/63757e1a54fd9a08f07881f3abd6736dfc02cba8">63757e1a54fd9a08f07881f3abd6736dfc02cba8</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
The package postcss before 8.2.13 are vulnerable to Regular Expression Denial of Service (ReDoS) via getAnnotationURL() and loadAnnotation() in lib/previous-map.js. The vulnerable regexes are caused mainly by the sub-pattern \/\*\s* sourceMappingURL=(.*).
<p>Publish Date: 2021-04-26
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2021-23382>CVE-2021-23382</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-23382">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-23382</a></p>
<p>Release Date: 2021-04-26</p>
<p>Fix Resolution (postcss): 7.0.36</p>
<p>Direct dependency fix Resolution (userscripter): 1.5.0</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | 1.0 | CVE-2021-23382 (High) detected in postcss-7.0.35.tgz - ## CVE-2021-23382 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>postcss-7.0.35.tgz</b></p></summary>
<p>Tool for transforming styles with JS plugins</p>
<p>Library home page: <a href="https://registry.npmjs.org/postcss/-/postcss-7.0.35.tgz">https://registry.npmjs.org/postcss/-/postcss-7.0.35.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/postcss/package.json</p>
<p>
Dependency Hierarchy:
- userscripter-1.4.0.tgz (Root Library)
- css-loader-3.6.0.tgz
- :x: **postcss-7.0.35.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/avallete/yt-playlists-delete-enhancer/commit/63757e1a54fd9a08f07881f3abd6736dfc02cba8">63757e1a54fd9a08f07881f3abd6736dfc02cba8</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
The package postcss before 8.2.13 are vulnerable to Regular Expression Denial of Service (ReDoS) via getAnnotationURL() and loadAnnotation() in lib/previous-map.js. The vulnerable regexes are caused mainly by the sub-pattern \/\*\s* sourceMappingURL=(.*).
<p>Publish Date: 2021-04-26
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2021-23382>CVE-2021-23382</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-23382">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-23382</a></p>
<p>Release Date: 2021-04-26</p>
<p>Fix Resolution (postcss): 7.0.36</p>
<p>Direct dependency fix Resolution (userscripter): 1.5.0</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_priority | cve high detected in postcss tgz cve high severity vulnerability vulnerable library postcss tgz tool for transforming styles with js plugins library home page a href path to dependency file package json path to vulnerable library node modules postcss package json dependency hierarchy userscripter tgz root library css loader tgz x postcss tgz vulnerable library found in head commit a href found in base branch master vulnerability details the package postcss before are vulnerable to regular expression denial of service redos via getannotationurl and loadannotation in lib previous map js the vulnerable regexes are caused mainly by the sub pattern s sourcemappingurl publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact none integrity impact none availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution postcss direct dependency fix resolution userscripter step up your open source security game with mend | 0 |
29,944 | 11,787,491,586 | IssuesEvent | 2020-03-17 14:07:37 | adrijshikhar/spotify-player | https://api.github.com/repos/adrijshikhar/spotify-player | opened | CVE-2018-11695 (High) detected in node-sass-4.13.1.tgz, node-sass-v4.13.1 | security vulnerability | ## CVE-2018-11695 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>node-sass-4.13.1.tgz</b></p></summary>
<p>
<details><summary><b>node-sass-4.13.1.tgz</b></p></summary>
<p>Wrapper around libsass</p>
<p>Library home page: <a href="https://registry.npmjs.org/node-sass/-/node-sass-4.13.1.tgz">https://registry.npmjs.org/node-sass/-/node-sass-4.13.1.tgz</a></p>
<p>Path to dependency file: /tmp/ws-scm/spotify-player/package.json</p>
<p>Path to vulnerable library: /spotify-player/node_modules/node-sass/package.json</p>
<p>
Dependency Hierarchy:
- :x: **node-sass-4.13.1.tgz** (Vulnerable Library)
</details>
<p>Found in HEAD commit: <a href="https://github.com/adrijshikhar/spotify-player/commit/172ce42afc892e366a594479a5108477592b3bac">172ce42afc892e366a594479a5108477592b3bac</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
An issue was discovered in LibSass through 3.5.2. A NULL pointer dereference was found in the function Sass::Expand::operator which could be leveraged by an attacker to cause a denial of service (application crash) or possibly have unspecified other impact.
<p>Publish Date: 2018-06-04
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-11695>CVE-2018-11695</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>8.8</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: 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>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-11695">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-11695</a></p>
<p>Release Date: 2018-06-04</p>
<p>Fix Resolution: 3.6.0</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | CVE-2018-11695 (High) detected in node-sass-4.13.1.tgz, node-sass-v4.13.1 - ## CVE-2018-11695 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>node-sass-4.13.1.tgz</b></p></summary>
<p>
<details><summary><b>node-sass-4.13.1.tgz</b></p></summary>
<p>Wrapper around libsass</p>
<p>Library home page: <a href="https://registry.npmjs.org/node-sass/-/node-sass-4.13.1.tgz">https://registry.npmjs.org/node-sass/-/node-sass-4.13.1.tgz</a></p>
<p>Path to dependency file: /tmp/ws-scm/spotify-player/package.json</p>
<p>Path to vulnerable library: /spotify-player/node_modules/node-sass/package.json</p>
<p>
Dependency Hierarchy:
- :x: **node-sass-4.13.1.tgz** (Vulnerable Library)
</details>
<p>Found in HEAD commit: <a href="https://github.com/adrijshikhar/spotify-player/commit/172ce42afc892e366a594479a5108477592b3bac">172ce42afc892e366a594479a5108477592b3bac</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
An issue was discovered in LibSass through 3.5.2. A NULL pointer dereference was found in the function Sass::Expand::operator which could be leveraged by an attacker to cause a denial of service (application crash) or possibly have unspecified other impact.
<p>Publish Date: 2018-06-04
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-11695>CVE-2018-11695</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>8.8</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: 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>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-11695">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-11695</a></p>
<p>Release Date: 2018-06-04</p>
<p>Fix Resolution: 3.6.0</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_priority | cve high detected in node sass tgz node sass cve high severity vulnerability vulnerable libraries node sass tgz node sass tgz wrapper around libsass library home page a href path to dependency file tmp ws scm spotify player package json path to vulnerable library spotify player node modules node sass package json dependency hierarchy x node sass tgz vulnerable library found in head commit a href vulnerability details an issue was discovered in libsass through a null pointer dereference was found in the function sass expand operator which could be leveraged by an attacker to cause a denial of service application crash or possibly have unspecified other impact 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 step up your open source security game with whitesource | 0 |
89,884 | 15,855,959,882 | IssuesEvent | 2021-04-08 01:10:45 | LevyForchh/lerc | https://api.github.com/repos/LevyForchh/lerc | opened | CVE-2021-23337 (High) detected in lodash-3.10.1.tgz | security vulnerability | ## CVE-2021-23337 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable 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: lerc/OtherLanguages/js/package.json</p>
<p>Path to vulnerable library: lerc/OtherLanguages/js/node_modules/lodash/package.json</p>
<p>
Dependency Hierarchy:
- gh-release-2.2.1.tgz (Root Library)
- inquirer-0.8.5.tgz
- :x: **lodash-3.10.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/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
Lodash versions prior to 4.17.21 are vulnerable to Command Injection via the template function.
<p>Publish Date: 2021-02-15
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-23337>CVE-2021-23337</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.2</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: High
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/lodash/lodash/commit/3469357cff396a26c363f8c1b5a91dde28ba4b1c">https://github.com/lodash/lodash/commit/3469357cff396a26c363f8c1b5a91dde28ba4b1c</a></p>
<p>Release Date: 2021-02-15</p>
<p>Fix Resolution: lodash - 4.17.21</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":false,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"lodash","packageVersion":"3.10.1","packageFilePaths":["/OtherLanguages/js/package.json"],"isTransitiveDependency":true,"dependencyTree":"gh-release:2.2.1;inquirer:0.8.5;lodash:3.10.1","isMinimumFixVersionAvailable":true,"minimumFixVersion":"lodash - 4.17.21"}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2021-23337","vulnerabilityDetails":"Lodash versions prior to 4.17.21 are vulnerable to Command Injection via the template function.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-23337","cvss3Severity":"high","cvss3Score":"7.2","cvss3Metrics":{"A":"High","AC":"Low","PR":"High","S":"Unchanged","C":"High","UI":"None","AV":"Network","I":"High"},"extraData":{}}</REMEDIATE> --> | True | CVE-2021-23337 (High) detected in lodash-3.10.1.tgz - ## CVE-2021-23337 - High 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: lerc/OtherLanguages/js/package.json</p>
<p>Path to vulnerable library: lerc/OtherLanguages/js/node_modules/lodash/package.json</p>
<p>
Dependency Hierarchy:
- gh-release-2.2.1.tgz (Root Library)
- inquirer-0.8.5.tgz
- :x: **lodash-3.10.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/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
Lodash versions prior to 4.17.21 are vulnerable to Command Injection via the template function.
<p>Publish Date: 2021-02-15
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-23337>CVE-2021-23337</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.2</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: High
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/lodash/lodash/commit/3469357cff396a26c363f8c1b5a91dde28ba4b1c">https://github.com/lodash/lodash/commit/3469357cff396a26c363f8c1b5a91dde28ba4b1c</a></p>
<p>Release Date: 2021-02-15</p>
<p>Fix Resolution: lodash - 4.17.21</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":false,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"lodash","packageVersion":"3.10.1","packageFilePaths":["/OtherLanguages/js/package.json"],"isTransitiveDependency":true,"dependencyTree":"gh-release:2.2.1;inquirer:0.8.5;lodash:3.10.1","isMinimumFixVersionAvailable":true,"minimumFixVersion":"lodash - 4.17.21"}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2021-23337","vulnerabilityDetails":"Lodash versions prior to 4.17.21 are vulnerable to Command Injection via the template function.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-23337","cvss3Severity":"high","cvss3Score":"7.2","cvss3Metrics":{"A":"High","AC":"Low","PR":"High","S":"Unchanged","C":"High","UI":"None","AV":"Network","I":"High"},"extraData":{}}</REMEDIATE> --> | non_priority | cve high detected in lodash tgz cve high severity vulnerability vulnerable library lodash tgz the modern build of lodash modular utilities library home page a href path to dependency file lerc otherlanguages js package json path to vulnerable library lerc otherlanguages js node modules lodash package json dependency hierarchy gh release tgz root library inquirer tgz x lodash tgz vulnerable library found in base branch master vulnerability details lodash versions prior to are vulnerable to command injection via the template function publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required high user interaction none scope unchanged impact metrics confidentiality impact high integrity impact high availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution lodash isopenpronvulnerability false ispackagebased true isdefaultbranch true packages istransitivedependency true dependencytree gh release inquirer lodash isminimumfixversionavailable true minimumfixversion lodash basebranches vulnerabilityidentifier cve vulnerabilitydetails lodash versions prior to are vulnerable to command injection via the template function vulnerabilityurl | 0 |
87,501 | 10,920,105,139 | IssuesEvent | 2019-11-21 20:30:05 | mozilla/network-pulse | https://api.github.com/repos/mozilla/network-pulse | closed | Add image attribution and license | design | When users submit an image with their pulse entry, they may not be owner of the image. We should give them option for attribution and license. This should be optional and unobtrusive.
Step one: design for the form. | 1.0 | Add image attribution and license - When users submit an image with their pulse entry, they may not be owner of the image. We should give them option for attribution and license. This should be optional and unobtrusive.
Step one: design for the form. | non_priority | add image attribution and license when users submit an image with their pulse entry they may not be owner of the image we should give them option for attribution and license this should be optional and unobtrusive step one design for the form | 0 |
64,473 | 26,751,811,791 | IssuesEvent | 2023-01-30 20:15:22 | hashicorp/terraform-provider-azurerm | https://api.github.com/repos/hashicorp/terraform-provider-azurerm | closed | Support for Test Failover Network and Test failover Settings for ASR | enhancement service/recovery-services | ### Is there an existing issue for this?
- [X] I have searched the existing issues
### Community Note
<!--- Please keep this note for the community --->
* Please vote on this issue by adding a :thumbsup: [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue to help the community and maintainers prioritize this request
* Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
* If you are interested in working on this issue or have submitted a pull request, please leave a comment
<!--- Thank you for keeping this note for the community --->
### Description
The following providers are missing Failover Test Network/Failover Test Settings available in the portal.
azurerm_site_recovery_network_mapping
azurerm_site_recovery_replicated_vm
Here is a screenshot of what im talking about:
### New or Affected Resource(s)/Data Source(s)
azurerm_site_recovery_network_mapping,azurerm_site_recovery_replicated_vm
### Potential Terraform Configuration
_No response_
### References
Referenced to question but no request to add this has been made it seems.
https://github.com/hashicorp/terraform-provider-azurerm/issues/7039 | 2.0 | Support for Test Failover Network and Test failover Settings for ASR - ### Is there an existing issue for this?
- [X] I have searched the existing issues
### Community Note
<!--- Please keep this note for the community --->
* Please vote on this issue by adding a :thumbsup: [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue to help the community and maintainers prioritize this request
* Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
* If you are interested in working on this issue or have submitted a pull request, please leave a comment
<!--- Thank you for keeping this note for the community --->
### Description
The following providers are missing Failover Test Network/Failover Test Settings available in the portal.
azurerm_site_recovery_network_mapping
azurerm_site_recovery_replicated_vm
Here is a screenshot of what im talking about:
### New or Affected Resource(s)/Data Source(s)
azurerm_site_recovery_network_mapping,azurerm_site_recovery_replicated_vm
### Potential Terraform Configuration
_No response_
### References
Referenced to question but no request to add this has been made it seems.
https://github.com/hashicorp/terraform-provider-azurerm/issues/7039 | non_priority | support for test failover network and test failover settings for asr is there an existing issue for this i have searched the existing issues community note please vote on this issue by adding a thumbsup to the original issue to help the community and maintainers prioritize this request please do not leave or me too comments they generate extra noise for issue followers and do not help prioritize the request if you are interested in working on this issue or have submitted a pull request please leave a comment description the following providers are missing failover test network failover test settings available in the portal azurerm site recovery network mapping azurerm site recovery replicated vm here is a screenshot of what im talking about new or affected resource s data source s azurerm site recovery network mapping azurerm site recovery replicated vm potential terraform configuration no response references referenced to question but no request to add this has been made it seems | 0 |
84,270 | 24,264,508,338 | IssuesEvent | 2022-09-28 04:14:17 | lemurheavy/coveralls-public | https://api.github.com/repos/lemurheavy/coveralls-public | closed | https://docs.coveralls.io/parallel-build-webhook should document all of the webhook parameters completely | documentation marked-for-closure parallel-builds api | https://docs.coveralls.io/parallel-build-webhook only gives partial documentation for the webhook which is not sufficient to understand how to use it except in a couple narrow configurations (TravisCI, CircleCI). If it documented all of the parameters and their meanings then anyone could fairly easily use the webhook from any CI system.
The first problem with the page is this statement:
> Then set up a post build webhook like so:
> https://coveralls.io/webhook?repo_token=(your repo token)
This makes it seem as though no additional parameters are required. However, reading the rest of the page, it seems quite unlikely this is true.
The rest of the problem is that the webhook payload is not explained:
```
{
"payload": {
"build_num": 1234,
"status": "done"
}
}
```
How is the value for `build_num` assigned? What are the consequences of the value? What are the possible values of `"status"` and what are their consequences?
| 1.0 | https://docs.coveralls.io/parallel-build-webhook should document all of the webhook parameters completely - https://docs.coveralls.io/parallel-build-webhook only gives partial documentation for the webhook which is not sufficient to understand how to use it except in a couple narrow configurations (TravisCI, CircleCI). If it documented all of the parameters and their meanings then anyone could fairly easily use the webhook from any CI system.
The first problem with the page is this statement:
> Then set up a post build webhook like so:
> https://coveralls.io/webhook?repo_token=(your repo token)
This makes it seem as though no additional parameters are required. However, reading the rest of the page, it seems quite unlikely this is true.
The rest of the problem is that the webhook payload is not explained:
```
{
"payload": {
"build_num": 1234,
"status": "done"
}
}
```
How is the value for `build_num` assigned? What are the consequences of the value? What are the possible values of `"status"` and what are their consequences?
| non_priority | should document all of the webhook parameters completely only gives partial documentation for the webhook which is not sufficient to understand how to use it except in a couple narrow configurations travisci circleci if it documented all of the parameters and their meanings then anyone could fairly easily use the webhook from any ci system the first problem with the page is this statement then set up a post build webhook like so repo token this makes it seem as though no additional parameters are required however reading the rest of the page it seems quite unlikely this is true the rest of the problem is that the webhook payload is not explained payload build num status done how is the value for build num assigned what are the consequences of the value what are the possible values of status and what are their consequences | 0 |
150,021 | 23,589,048,454 | IssuesEvent | 2022-08-23 13:53:55 | MetaMask/metamask-extension | https://api.github.com/repos/MetaMask/metamask-extension | closed | Create review spending cap component | type-enhancement area-transactions design-system transaction safety team | ## Resources
[Figma Design file](https://www.figma.com/file/n0xMnZqQz4w9Sfa3ZdhWUi/Consentful-experience-for-token-allowances?node-id=2007%3A14202)
## Acceptance Criteria
1. TBD
2.
2. Clicking on `edit`, takes the user back to the first token allowance screen (a.k.a. Set spending cap screen)
| 1.0 | Create review spending cap component - ## Resources
[Figma Design file](https://www.figma.com/file/n0xMnZqQz4w9Sfa3ZdhWUi/Consentful-experience-for-token-allowances?node-id=2007%3A14202)
## Acceptance Criteria
1. TBD
2.
2. Clicking on `edit`, takes the user back to the first token allowance screen (a.k.a. Set spending cap screen)
| non_priority | create review spending cap component resources acceptance criteria tbd clicking on edit takes the user back to the first token allowance screen a k a set spending cap screen | 0 |
139,653 | 20,922,970,744 | IssuesEvent | 2022-03-24 19:17:41 | Subscribie/subscribie | https://api.github.com/repos/Subscribie/subscribie | closed | View Transactions Page not found | bug needs-design needs-qa | **Is your feature request related to a problem? Please describe.**
From the shop owner dashboard, clicking the 'view transactions' link lead to a 'Something's gone wrong' page
**Describe the solution you'd like**
Correct this page break issue so the page correctly shows a list of recent transactions
**Describe alternatives you've considered**
Recent payments would still be viewable in GoCardless
- [ ] Debug page link to source issue
- [ ] Fix to have a fully functioning link to the transactions list
| 1.0 | View Transactions Page not found - **Is your feature request related to a problem? Please describe.**
From the shop owner dashboard, clicking the 'view transactions' link lead to a 'Something's gone wrong' page
**Describe the solution you'd like**
Correct this page break issue so the page correctly shows a list of recent transactions
**Describe alternatives you've considered**
Recent payments would still be viewable in GoCardless
- [ ] Debug page link to source issue
- [ ] Fix to have a fully functioning link to the transactions list
| non_priority | view transactions page not found is your feature request related to a problem please describe from the shop owner dashboard clicking the view transactions link lead to a something s gone wrong page describe the solution you d like correct this page break issue so the page correctly shows a list of recent transactions describe alternatives you ve considered recent payments would still be viewable in gocardless debug page link to source issue fix to have a fully functioning link to the transactions list | 0 |
285,018 | 24,637,100,600 | IssuesEvent | 2022-10-17 08:48:33 | Plant-for-the-Planet-org/treemapper | https://api.github.com/repos/Plant-for-the-Planet-org/treemapper | opened | Error in main.jsbundle:28 | bug bugsnag testflight 1.0.9 | ## Error in Tree Mapper
**Error** in **main.jsbundle:28**
ENOENT: no such file or directory, open '/var/mobile/Containers/Data/Application/9F7C5431-F098-467F-842C-EF34AA92F8B9/Documents/null'
[View on Bugsnag](https://app.bugsnag.com/plant-for-the-planet/tree-mapper/errors/634d16dfa9025000086c7241?event_id=634d16df009a574fe2d30000&i=gh&m=ci)
## Stacktrace
main.jsbundle:28 -
[View full stacktrace](https://app.bugsnag.com/plant-for-the-planet/tree-mapper/errors/634d16dfa9025000086c7241?event_id=634d16df009a574fe2d30000&i=gh&m=ci)
*Created automatically via Bugsnag* | 1.0 | Error in main.jsbundle:28 - ## Error in Tree Mapper
**Error** in **main.jsbundle:28**
ENOENT: no such file or directory, open '/var/mobile/Containers/Data/Application/9F7C5431-F098-467F-842C-EF34AA92F8B9/Documents/null'
[View on Bugsnag](https://app.bugsnag.com/plant-for-the-planet/tree-mapper/errors/634d16dfa9025000086c7241?event_id=634d16df009a574fe2d30000&i=gh&m=ci)
## Stacktrace
main.jsbundle:28 -
[View full stacktrace](https://app.bugsnag.com/plant-for-the-planet/tree-mapper/errors/634d16dfa9025000086c7241?event_id=634d16df009a574fe2d30000&i=gh&m=ci)
*Created automatically via Bugsnag* | non_priority | error in main jsbundle error in tree mapper error in main jsbundle enoent no such file or directory open var mobile containers data application documents null stacktrace main jsbundle created automatically via bugsnag | 0 |
92,007 | 26,551,876,767 | IssuesEvent | 2023-01-20 08:36:30 | camunda/zeebe | https://api.github.com/repos/camunda/zeebe | closed | Remove Jenkins CI Pipeline leftovers | kind/toil area/test component/build-pipeline | We can clean up our Jenkins configuration, for example the Jenkinsfile and various scripts in the `.ci` folder.
We'll have to be a bit careful since some of the scripts might be used for other Jenkins pipelines that we haven't replaced yet, such as the release builds or QA runs.
blocked by #9137 | 1.0 | Remove Jenkins CI Pipeline leftovers - We can clean up our Jenkins configuration, for example the Jenkinsfile and various scripts in the `.ci` folder.
We'll have to be a bit careful since some of the scripts might be used for other Jenkins pipelines that we haven't replaced yet, such as the release builds or QA runs.
blocked by #9137 | non_priority | remove jenkins ci pipeline leftovers we can clean up our jenkins configuration for example the jenkinsfile and various scripts in the ci folder we ll have to be a bit careful since some of the scripts might be used for other jenkins pipelines that we haven t replaced yet such as the release builds or qa runs blocked by | 0 |
5,960 | 8,784,237,658 | IssuesEvent | 2018-12-20 09:15:51 | linnovate/root | https://api.github.com/repos/linnovate/root | closed | partners permission bugs in different entities | 2.0.6 Process bug | ### tasks : after creating a sub task for a task that has a partner other than the creator and an assignee, setting the partner in the main task to editor/commentor, the role isnt saved in the sub task and instead shows the partner as a viewer .
in the main task
in the sub task:
### **projects:** in the sub tasks after adding a partner to the main project, the partner doesnt show up in the sub task.
in the main project in a task from the tasks sub tab, the partner doesnt show up as well.
in the main project
in the tasks tab/ sub projects
### **meetings:** after adding a partner to the meeting and setting him as editor/commenter, and then clicking on manage tasks, the partner doesnt show up in the task
### **documents**: after adding a partner to the document and setting him as editor/commenter, and then clicking on manage tasks, the partner doesnt show up in the task and the role change isnt saved in the document itself. in addition a user with viewer permissions can select a signature
### **folders**: after adding a partner with commenter or editor roles to the folder and then entering the documents tab from manage documents, the partners added are shown in the document but with viewer roles
### **offices**: after adding a partner with commenter or editor roles to the office and then entering the folders tab from manage folders, the partners added are shown in the folder but with viewer roles | 1.0 | partners permission bugs in different entities - ### tasks : after creating a sub task for a task that has a partner other than the creator and an assignee, setting the partner in the main task to editor/commentor, the role isnt saved in the sub task and instead shows the partner as a viewer .
in the main task
in the sub task:
### **projects:** in the sub tasks after adding a partner to the main project, the partner doesnt show up in the sub task.
in the main project in a task from the tasks sub tab, the partner doesnt show up as well.
in the main project
in the tasks tab/ sub projects
### **meetings:** after adding a partner to the meeting and setting him as editor/commenter, and then clicking on manage tasks, the partner doesnt show up in the task
### **documents**: after adding a partner to the document and setting him as editor/commenter, and then clicking on manage tasks, the partner doesnt show up in the task and the role change isnt saved in the document itself. in addition a user with viewer permissions can select a signature
### **folders**: after adding a partner with commenter or editor roles to the folder and then entering the documents tab from manage documents, the partners added are shown in the document but with viewer roles
### **offices**: after adding a partner with commenter or editor roles to the office and then entering the folders tab from manage folders, the partners added are shown in the folder but with viewer roles | non_priority | partners permission bugs in different entities tasks after creating a sub task for a task that has a partner other than the creator and an assignee setting the partner in the main task to editor commentor the role isnt saved in the sub task and instead shows the partner as a viewer in the main task in the sub task projects in the sub tasks after adding a partner to the main project the partner doesnt show up in the sub task in the main project in a task from the tasks sub tab the partner doesnt show up as well in the main project in the tasks tab sub projects meetings after adding a partner to the meeting and setting him as editor commenter and then clicking on manage tasks the partner doesnt show up in the task documents after adding a partner to the document and setting him as editor commenter and then clicking on manage tasks the partner doesnt show up in the task and the role change isnt saved in the document itself in addition a user with viewer permissions can select a signature folders after adding a partner with commenter or editor roles to the folder and then entering the documents tab from manage documents the partners added are shown in the document but with viewer roles offices after adding a partner with commenter or editor roles to the office and then entering the folders tab from manage folders the partners added are shown in the folder but with viewer roles | 0 |
32,009 | 26,346,625,850 | IssuesEvent | 2023-01-10 22:48:15 | qoollo/bob | https://api.github.com/repos/qoollo/bob | closed | Integration tests: add tests for aliens | infrastructure | Strategy:
1. run cluster with `n` nodes
2. write small amount of data to cluster
3. turn off one node
4. repeat 2, 3 until one node remains
5. turn on all nodes
6. read all data (should be successful) | 1.0 | Integration tests: add tests for aliens - Strategy:
1. run cluster with `n` nodes
2. write small amount of data to cluster
3. turn off one node
4. repeat 2, 3 until one node remains
5. turn on all nodes
6. read all data (should be successful) | non_priority | integration tests add tests for aliens strategy run cluster with n nodes write small amount of data to cluster turn off one node repeat until one node remains turn on all nodes read all data should be successful | 0 |
162,759 | 12,689,933,183 | IssuesEvent | 2020-06-21 09:12:49 | MDAnalysis/mdanalysis | https://api.github.com/repos/MDAnalysis/mdanalysis | closed | parallel testing crashes (matplotlib?) | testing | ## Expected behavior ##
running `pytest -n4 .` in `testsuite/MDAnalysisTests` should complete successfully.
## Actual behavior ##
Several tests (all of which seem to use matplotlib) fail with "node down: Not properly terminated" issues.
test failures:
analysis/test_dihedrals.py::TestJanin:test_plot
anlysis/test_dihedrals.py::TestRamachandran::test_plot
analysis/test_persistencelength.py::TestPersistenceLength::test_current_axes
visualization/test_streamlines.py::test_streamplot_2D
analysis/test_persistencelength.py::TestPersistenceLength::test_plot_with_ax
analysis/test_psa.py::TestPSAnalysis::test_dendrogram_produced
analysis/test_persistencelength.py::TestPersistenceLength::test_plot_ax_return
## Current version of MDAnalysis ##
- Which version are you using? (run `python -c "import MDAnalysis as mda; print(mda.__version__)"`) 2.0.0-dev0
- Which version of Python (`python -V`)? 3.7.7
- Which operating system? Ubuntu 20.04 LTS (WSL2)
| 1.0 | parallel testing crashes (matplotlib?) - ## Expected behavior ##
running `pytest -n4 .` in `testsuite/MDAnalysisTests` should complete successfully.
## Actual behavior ##
Several tests (all of which seem to use matplotlib) fail with "node down: Not properly terminated" issues.
test failures:
analysis/test_dihedrals.py::TestJanin:test_plot
anlysis/test_dihedrals.py::TestRamachandran::test_plot
analysis/test_persistencelength.py::TestPersistenceLength::test_current_axes
visualization/test_streamlines.py::test_streamplot_2D
analysis/test_persistencelength.py::TestPersistenceLength::test_plot_with_ax
analysis/test_psa.py::TestPSAnalysis::test_dendrogram_produced
analysis/test_persistencelength.py::TestPersistenceLength::test_plot_ax_return
## Current version of MDAnalysis ##
- Which version are you using? (run `python -c "import MDAnalysis as mda; print(mda.__version__)"`) 2.0.0-dev0
- Which version of Python (`python -V`)? 3.7.7
- Which operating system? Ubuntu 20.04 LTS (WSL2)
| non_priority | parallel testing crashes matplotlib expected behavior running pytest in testsuite mdanalysistests should complete successfully actual behavior several tests all of which seem to use matplotlib fail with node down not properly terminated issues test failures analysis test dihedrals py testjanin test plot anlysis test dihedrals py testramachandran test plot analysis test persistencelength py testpersistencelength test current axes visualization test streamlines py test streamplot analysis test persistencelength py testpersistencelength test plot with ax analysis test psa py testpsanalysis test dendrogram produced analysis test persistencelength py testpersistencelength test plot ax return current version of mdanalysis which version are you using run python c import mdanalysis as mda print mda version which version of python python v which operating system ubuntu lts | 0 |
45,923 | 13,144,996,863 | IssuesEvent | 2020-08-08 01:02:46 | shaundmorris/ddf | https://api.github.com/repos/shaundmorris/ddf | closed | CVE-2013-4002 High Severity Vulnerability detected by WhiteSource | security vulnerability wontfix | ## CVE-2013-4002 - High Severity Vulnerability
<details><summary><img src='https://www.whitesourcesoftware.com/wp-content/uploads/2018/10/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>xercesImpl-2.11.0.jar</b></p></summary>
<p>POM was created from install:install-file</p>
<p>path: /root/.m2/repository/xerces/xercesImpl/2.11.0/xercesImpl-2.11.0.jar,2/repository/xerces/xercesImpl/2.11.0/xercesImpl-2.11.0.jar</p>
<p>
Dependency Hierarchy:
- :x: **xercesImpl-2.11.0.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/shaundmorris/ddf/commit/97965f18b08ff37443884cd51df841cee9d729ff">97965f18b08ff37443884cd51df841cee9d729ff</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://www.whitesourcesoftware.com/wp-content/uploads/2018/10/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
XMLscanner.java in Apache Xerces2 Java Parser before 2.12.0, as used in the Java Runtime Environment (JRE) in IBM Java 5.0 before 5.0 SR16-FP3, 6 before 6 SR14, 6.0.1 before 6.0.1 SR6, and 7 before 7 SR5 as well as Oracle Java SE 7u40 and earlier, Java SE 6u60 and earlier, Java SE 5.0u51 and earlier, JRockit R28.2.8 and earlier, JRockit R27.7.6 and earlier, Java SE Embedded 7u40 and earlier, and possibly other products allows remote attackers to cause a denial of service via vectors related to XML attribute names.
<p>Publish Date: 2013-07-23
<p>URL: <a href=https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2013-4002>CVE-2013-4002</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://www.whitesourcesoftware.com/wp-content/uploads/2018/10/cvss3.png' width=19 height=20> CVSS 2 Score Details (<b>7.1</b>)</summary>
<p>
Base Score Metrics not available</p>
</p>
</details>
<p></p>
<details><summary><img src='https://www.whitesourcesoftware.com/wp-content/uploads/2018/10/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://security.gentoo.org/glsa/201406-32">https://security.gentoo.org/glsa/201406-32</a></p>
<p>Release Date: 2014-06-29</p>
<p>Fix Resolution: All IcedTea JDK users should upgrade to the latest version >= icedtea-bin-6.1.13.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-2013-4002 High Severity Vulnerability detected by WhiteSource - ## CVE-2013-4002 - High Severity Vulnerability
<details><summary><img src='https://www.whitesourcesoftware.com/wp-content/uploads/2018/10/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>xercesImpl-2.11.0.jar</b></p></summary>
<p>POM was created from install:install-file</p>
<p>path: /root/.m2/repository/xerces/xercesImpl/2.11.0/xercesImpl-2.11.0.jar,2/repository/xerces/xercesImpl/2.11.0/xercesImpl-2.11.0.jar</p>
<p>
Dependency Hierarchy:
- :x: **xercesImpl-2.11.0.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/shaundmorris/ddf/commit/97965f18b08ff37443884cd51df841cee9d729ff">97965f18b08ff37443884cd51df841cee9d729ff</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://www.whitesourcesoftware.com/wp-content/uploads/2018/10/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
XMLscanner.java in Apache Xerces2 Java Parser before 2.12.0, as used in the Java Runtime Environment (JRE) in IBM Java 5.0 before 5.0 SR16-FP3, 6 before 6 SR14, 6.0.1 before 6.0.1 SR6, and 7 before 7 SR5 as well as Oracle Java SE 7u40 and earlier, Java SE 6u60 and earlier, Java SE 5.0u51 and earlier, JRockit R28.2.8 and earlier, JRockit R27.7.6 and earlier, Java SE Embedded 7u40 and earlier, and possibly other products allows remote attackers to cause a denial of service via vectors related to XML attribute names.
<p>Publish Date: 2013-07-23
<p>URL: <a href=https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2013-4002>CVE-2013-4002</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://www.whitesourcesoftware.com/wp-content/uploads/2018/10/cvss3.png' width=19 height=20> CVSS 2 Score Details (<b>7.1</b>)</summary>
<p>
Base Score Metrics not available</p>
</p>
</details>
<p></p>
<details><summary><img src='https://www.whitesourcesoftware.com/wp-content/uploads/2018/10/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://security.gentoo.org/glsa/201406-32">https://security.gentoo.org/glsa/201406-32</a></p>
<p>Release Date: 2014-06-29</p>
<p>Fix Resolution: All IcedTea JDK users should upgrade to the latest version >= icedtea-bin-6.1.13.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 severity vulnerability detected by whitesource cve high severity vulnerability vulnerable library xercesimpl jar pom was created from install install file path root repository xerces xercesimpl xercesimpl jar repository xerces xercesimpl xercesimpl jar dependency hierarchy x xercesimpl jar vulnerable library found in head commit a href vulnerability details xmlscanner java in apache java parser before as used in the java runtime environment jre in ibm java before before before and before as well as oracle java se and earlier java se and earlier java se and earlier jrockit and earlier jrockit and earlier java se embedded and earlier and possibly other products allows remote attackers to cause a denial of service via vectors related to xml attribute names 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 all icedtea jdk users should upgrade to the latest version icedtea bin step up your open source security game with whitesource | 0 |
82,005 | 10,213,198,403 | IssuesEvent | 2019-08-14 21:27:13 | carbon-design-system/carbon | https://api.github.com/repos/carbon-design-system/carbon | closed | Color Black is showing with grey outline | design kit :symbols: type: bug 🐛 | - [x] `carbon-components`
- [ ] `carbon-components-react`
## Detailed description
Color bug in the libraries:
`Grey 10`
`Grey 90`
`White`
The color `Black` swatch come with a grey outline:
## Screenshots
<img width="635" alt="image" src="https://user-images.githubusercontent.com/3612533/61748544-c0a62f80-ada0-11e9-80ec-3a2b0f411664.png">
<img width="765" alt="image" src="https://user-images.githubusercontent.com/3612533/61748612-fb0fcc80-ada0-11e9-8cf5-98657beceb46.png"> | 1.0 | Color Black is showing with grey outline - - [x] `carbon-components`
- [ ] `carbon-components-react`
## Detailed description
Color bug in the libraries:
`Grey 10`
`Grey 90`
`White`
The color `Black` swatch come with a grey outline:
## Screenshots
<img width="635" alt="image" src="https://user-images.githubusercontent.com/3612533/61748544-c0a62f80-ada0-11e9-80ec-3a2b0f411664.png">
<img width="765" alt="image" src="https://user-images.githubusercontent.com/3612533/61748612-fb0fcc80-ada0-11e9-8cf5-98657beceb46.png"> | non_priority | color black is showing with grey outline carbon components carbon components react detailed description color bug in the libraries grey grey white the color black swatch come with a grey outline screenshots img width alt image src img width alt image src | 0 |
2,923 | 5,289,363,333 | IssuesEvent | 2017-02-08 17:11:55 | Harmonus/HMS_SlicerModule | https://api.github.com/repos/Harmonus/HMS_SlicerModule | opened | Register target and confirmation scans | requirement | Software automatically registers the target scan to the confirmation scan to optimize the prostate image overlap and transforms the target model from the original target scan to the confirmation scan. | 1.0 | Register target and confirmation scans - Software automatically registers the target scan to the confirmation scan to optimize the prostate image overlap and transforms the target model from the original target scan to the confirmation scan. | non_priority | register target and confirmation scans software automatically registers the target scan to the confirmation scan to optimize the prostate image overlap and transforms the target model from the original target scan to the confirmation scan | 0 |
162,087 | 13,882,206,509 | IssuesEvent | 2020-10-18 05:32:22 | jmfayard/refreshVersions | https://api.github.com/repos/jmfayard/refreshVersions | closed | What is the buildSrc module? | documentation groovy-and-kotlin | _Context: [buildSrcVersions](https://github.com/jmfayard/buildSrcVersions) is a Gradle plugin that makes it easier to manage your dependencies inside your IDE. It extracts all your dependencies and search for available dependencies updates._
> The directory buildSrc is treated as an included build. Upon discovery of the directory, Gradle automatically compiles and tests this code and puts it in the classpath of your build script. For multi-project builds there can be only one buildSrc directory, which has to sit in the root project directory. buildSrc should be preferred over script plugins as it is easier to maintain, refactor and test the code.
> buildSrc uses the same source code conventions applicable to Java and Groovy projects. It also provides direct access to the Gradle API. Additional dependencies can be declared in a dedicated build.gradle under buildSrc.
See more at https://docs.gradle.org/current/userguide/organizing_gradle_projects.html#sec:build_sources
A practical example:
```kt
// buildSrc/..../Config.kt
object Config {
const val applicationId = "de.fayard.something"
const val compileSdkVersion = 27
const val targetSdkVersion = 27
const val versionName = "1.0.0"
const val versionCode = 1
const val minSdkVersion = 21
val runsOnCi : Boolean = System.getenv("MY_ENV_VARIABLE") != null
}
```
You can now use those constants everywhere in the your Gradle biuld *and* the IDE is giving you auto-complete, in both `build.gradle` and `build.gradle.kts` files
Example
```groovy
// app/build.gradle
android {
compileSdkVersion(Config.compileSdkVersion)
defaultConfig {
minSdkVersion(Config.minSdkVersion)
targetSdkVersion(Config.targetSdkVersion)
versionCode = Config.versionCode
versionName = Config.versionName
applicationId = Config.applicationId
}
}
```
| 1.0 | What is the buildSrc module? - _Context: [buildSrcVersions](https://github.com/jmfayard/buildSrcVersions) is a Gradle plugin that makes it easier to manage your dependencies inside your IDE. It extracts all your dependencies and search for available dependencies updates._
> The directory buildSrc is treated as an included build. Upon discovery of the directory, Gradle automatically compiles and tests this code and puts it in the classpath of your build script. For multi-project builds there can be only one buildSrc directory, which has to sit in the root project directory. buildSrc should be preferred over script plugins as it is easier to maintain, refactor and test the code.
> buildSrc uses the same source code conventions applicable to Java and Groovy projects. It also provides direct access to the Gradle API. Additional dependencies can be declared in a dedicated build.gradle under buildSrc.
See more at https://docs.gradle.org/current/userguide/organizing_gradle_projects.html#sec:build_sources
A practical example:
```kt
// buildSrc/..../Config.kt
object Config {
const val applicationId = "de.fayard.something"
const val compileSdkVersion = 27
const val targetSdkVersion = 27
const val versionName = "1.0.0"
const val versionCode = 1
const val minSdkVersion = 21
val runsOnCi : Boolean = System.getenv("MY_ENV_VARIABLE") != null
}
```
You can now use those constants everywhere in the your Gradle biuld *and* the IDE is giving you auto-complete, in both `build.gradle` and `build.gradle.kts` files
Example
```groovy
// app/build.gradle
android {
compileSdkVersion(Config.compileSdkVersion)
defaultConfig {
minSdkVersion(Config.minSdkVersion)
targetSdkVersion(Config.targetSdkVersion)
versionCode = Config.versionCode
versionName = Config.versionName
applicationId = Config.applicationId
}
}
```
| non_priority | what is the buildsrc module context is a gradle plugin that makes it easier to manage your dependencies inside your ide it extracts all your dependencies and search for available dependencies updates the directory buildsrc is treated as an included build upon discovery of the directory gradle automatically compiles and tests this code and puts it in the classpath of your build script for multi project builds there can be only one buildsrc directory which has to sit in the root project directory buildsrc should be preferred over script plugins as it is easier to maintain refactor and test the code buildsrc uses the same source code conventions applicable to java and groovy projects it also provides direct access to the gradle api additional dependencies can be declared in a dedicated build gradle under buildsrc see more at a practical example kt buildsrc config kt object config const val applicationid de fayard something const val compilesdkversion const val targetsdkversion const val versionname const val versioncode const val minsdkversion val runsonci boolean system getenv my env variable null you can now use those constants everywhere in the your gradle biuld and the ide is giving you auto complete in both build gradle and build gradle kts files example groovy app build gradle android compilesdkversion config compilesdkversion defaultconfig minsdkversion config minsdkversion targetsdkversion config targetsdkversion versioncode config versioncode versionname config versionname applicationid config applicationid | 0 |
431,954 | 30,259,836,658 | IssuesEvent | 2023-07-07 07:19:38 | precice/micro-manager | https://api.github.com/repos/precice/micro-manager | closed | Add pictorial description of macro-micro coupling to README | documentation | Currently the README has only text which describes the concept and working of the Micro Manager. In addition to the provided information, a pictorial description of the macro-micro coupling strategy would be beneficial for understanding the core concept of the Micro Manager. | 1.0 | Add pictorial description of macro-micro coupling to README - Currently the README has only text which describes the concept and working of the Micro Manager. In addition to the provided information, a pictorial description of the macro-micro coupling strategy would be beneficial for understanding the core concept of the Micro Manager. | non_priority | add pictorial description of macro micro coupling to readme currently the readme has only text which describes the concept and working of the micro manager in addition to the provided information a pictorial description of the macro micro coupling strategy would be beneficial for understanding the core concept of the micro manager | 0 |
40,837 | 10,584,868,596 | IssuesEvent | 2019-10-08 16:15:36 | JabRef/jabref | https://api.github.com/repos/JabRef/jabref | closed | Register native messaging host also when user has no admin rights | bug build-system | As of now, the installer adds an entry in the registry pointing to the JabRef executable:
https://github.com/JabRef/jabref/blob/1d8b3aad2f9ca4441c41fa6fa3dfac61e45cb5ef/jabref.install4j#L578
Usually, this key is placed under `HKEY_LOCAL_MACHINE`.
https://github.com/JabRef/jabref/blob/1d8b3aad2f9ca4441c41fa6fa3dfac61e45cb5ef/jabref.install4j#L580-L585
However, if the user does not have admin rights, it should instead be placed under `HKEY_CURRENT_USER`. | 1.0 | Register native messaging host also when user has no admin rights - As of now, the installer adds an entry in the registry pointing to the JabRef executable:
https://github.com/JabRef/jabref/blob/1d8b3aad2f9ca4441c41fa6fa3dfac61e45cb5ef/jabref.install4j#L578
Usually, this key is placed under `HKEY_LOCAL_MACHINE`.
https://github.com/JabRef/jabref/blob/1d8b3aad2f9ca4441c41fa6fa3dfac61e45cb5ef/jabref.install4j#L580-L585
However, if the user does not have admin rights, it should instead be placed under `HKEY_CURRENT_USER`. | non_priority | register native messaging host also when user has no admin rights as of now the installer adds an entry in the registry pointing to the jabref executable usually this key is placed under hkey local machine however if the user does not have admin rights it should instead be placed under hkey current user | 0 |
430,183 | 30,120,274,086 | IssuesEvent | 2023-06-30 14:38:54 | ant-media/Ant-Media-Server | https://api.github.com/repos/ant-media/Ant-Media-Server | opened | Android SDK - Documentation and Blogpost update | documentation/blog-post | The Android SDK document is outdated and needs to be rewritten according to the latest changes in the SDK and UI.
#5201 | 1.0 | Android SDK - Documentation and Blogpost update - The Android SDK document is outdated and needs to be rewritten according to the latest changes in the SDK and UI.
#5201 | non_priority | android sdk documentation and blogpost update the android sdk document is outdated and needs to be rewritten according to the latest changes in the sdk and ui | 0 |
186,525 | 14,396,245,495 | IssuesEvent | 2020-12-03 05:51:23 | canonical/ubuntu-advantage-client | https://api.github.com/repos/canonical/ubuntu-advantage-client | closed | fips: test that enabled fips is chosen after reboot | testing | Integration tests need to config the following when FIPS is enabled on a new image:
- after reboot, fips kernel is active from `uname -r`
- after reboot, the kernel represents FIPS config is active by `cat /proc/sys/crypto/fips_enabled` == 1
Not working on Xenial at the moment | 1.0 | fips: test that enabled fips is chosen after reboot - Integration tests need to config the following when FIPS is enabled on a new image:
- after reboot, fips kernel is active from `uname -r`
- after reboot, the kernel represents FIPS config is active by `cat /proc/sys/crypto/fips_enabled` == 1
Not working on Xenial at the moment | non_priority | fips test that enabled fips is chosen after reboot integration tests need to config the following when fips is enabled on a new image after reboot fips kernel is active from uname r after reboot the kernel represents fips config is active by cat proc sys crypto fips enabled not working on xenial at the moment | 0 |
8,259 | 7,227,776,786 | IssuesEvent | 2018-02-11 00:37:58 | mailpile/Mailpile | https://api.github.com/repos/mailpile/Mailpile | closed | Misleading subject line for memory hole | Bugs Privacy / Security Usability | **User story:** I am a non-Mailpile user. I have become accustomed to getting Mailpile emails with the subject line "Encrypted message", so I assume any email with this subject line is encrypted (rather than checking the normal indicators).
**Suggestion:**
Change the subject line to something like "No subject", "Subject removed", "Subject embedded" or even "Enable [memory hole](#156) to read this subject". | True | Misleading subject line for memory hole - **User story:** I am a non-Mailpile user. I have become accustomed to getting Mailpile emails with the subject line "Encrypted message", so I assume any email with this subject line is encrypted (rather than checking the normal indicators).
**Suggestion:**
Change the subject line to something like "No subject", "Subject removed", "Subject embedded" or even "Enable [memory hole](#156) to read this subject". | non_priority | misleading subject line for memory hole user story i am a non mailpile user i have become accustomed to getting mailpile emails with the subject line encrypted message so i assume any email with this subject line is encrypted rather than checking the normal indicators suggestion change the subject line to something like no subject subject removed subject embedded or even enable to read this subject | 0 |
57,762 | 24,218,701,339 | IssuesEvent | 2022-09-26 09:02:41 | microsoft/vscode-cpptools | https://api.github.com/repos/microsoft/vscode-cpptools | closed | VSCode reports many outdated warnings | bug Language Service external more info needed | ### Environment
- OS and Version: MacOS
- VS Code Version: 1.71.2
- C/C++ Extension Version: latest
### Bug Summary and Steps to Reproduce
Bug Summary:
<img width="1177" alt="image" src="https://user-images.githubusercontent.com/8640918/191915009-27604640-f859-4ff9-8343-bf0a6767b24f.png">
Steps to reproduce:
1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error
### Expected behavior
_No response_
### Code sample and Logs
```shell
快速信息操作失败: FE: 'Unknown error'
```
<img width="1409" alt="image" src="https://user-images.githubusercontent.com/8640918/191915262-1f31da49-ca55-43eb-bebd-be262dccb0ec.png">
### Screenshots
_No response_
### Additional context
_No response_ | 1.0 | VSCode reports many outdated warnings - ### Environment
- OS and Version: MacOS
- VS Code Version: 1.71.2
- C/C++ Extension Version: latest
### Bug Summary and Steps to Reproduce
Bug Summary:
<img width="1177" alt="image" src="https://user-images.githubusercontent.com/8640918/191915009-27604640-f859-4ff9-8343-bf0a6767b24f.png">
Steps to reproduce:
1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error
### Expected behavior
_No response_
### Code sample and Logs
```shell
快速信息操作失败: FE: 'Unknown error'
```
<img width="1409" alt="image" src="https://user-images.githubusercontent.com/8640918/191915262-1f31da49-ca55-43eb-bebd-be262dccb0ec.png">
### Screenshots
_No response_
### Additional context
_No response_ | non_priority | vscode reports many outdated warnings environment os and version macos vs code version c c extension version latest bug summary and steps to reproduce bug summary img width alt image src steps to reproduce go to click on scroll down to see error expected behavior no response code sample and logs shell 快速信息操作失败 fe unknown error img width alt image src screenshots no response additional context no response | 0 |
417,057 | 28,110,073,772 | IssuesEvent | 2023-03-31 06:18:31 | DerenC/ped | https://api.github.com/repos/DerenC/ped | opened | Missing Explanation under the ":information_source: Notes about the command format:" of Features section | severity.VeryLow type.DocumentationBug | 
<!--session: 1680242691429-fed40b3b-7977-429a-8a16-fc36135b82a7-->
<!--Version: Web v3.4.7--> | 1.0 | Missing Explanation under the ":information_source: Notes about the command format:" of Features section - 
<!--session: 1680242691429-fed40b3b-7977-429a-8a16-fc36135b82a7-->
<!--Version: Web v3.4.7--> | non_priority | missing explanation under the information source notes about the command format of features section | 0 |
86,384 | 15,755,620,914 | IssuesEvent | 2021-03-31 02:06:07 | senthilbalakrishnanfull/testing | https://api.github.com/repos/senthilbalakrishnanfull/testing | opened | CVE-2018-19837 (Medium) detected in node-sass-4.12.0.tgz | security vulnerability | ## CVE-2018-19837 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>node-sass-4.12.0.tgz</b></p></summary>
<p>Wrapper around libsass</p>
<p>Library home page: <a href="https://registry.npmjs.org/node-sass/-/node-sass-4.12.0.tgz">https://registry.npmjs.org/node-sass/-/node-sass-4.12.0.tgz</a></p>
<p>Path to dependency file: /testing/package.json</p>
<p>Path to vulnerable library: testing/node_modules/node-sass/package.json,testing/node_modules/node-sass/package.json</p>
<p>
Dependency Hierarchy:
- :x: **node-sass-4.12.0.tgz** (Vulnerable Library)
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
In LibSass prior to 3.5.5, Sass::Eval::operator()(Sass::Binary_Expression*) inside eval.cpp allows attackers to cause a denial-of-service resulting from stack consumption via a crafted sass file, because of certain incorrect parsing of '%' as a modulo operator in parser.cpp.
<p>Publish Date: 2018-12-04
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-19837>CVE-2018-19837</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: None
- User Interaction: Required
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-19837">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-19837</a></p>
<p>Fix Resolution: 3.5.5</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | CVE-2018-19837 (Medium) detected in node-sass-4.12.0.tgz - ## CVE-2018-19837 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>node-sass-4.12.0.tgz</b></p></summary>
<p>Wrapper around libsass</p>
<p>Library home page: <a href="https://registry.npmjs.org/node-sass/-/node-sass-4.12.0.tgz">https://registry.npmjs.org/node-sass/-/node-sass-4.12.0.tgz</a></p>
<p>Path to dependency file: /testing/package.json</p>
<p>Path to vulnerable library: testing/node_modules/node-sass/package.json,testing/node_modules/node-sass/package.json</p>
<p>
Dependency Hierarchy:
- :x: **node-sass-4.12.0.tgz** (Vulnerable Library)
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
In LibSass prior to 3.5.5, Sass::Eval::operator()(Sass::Binary_Expression*) inside eval.cpp allows attackers to cause a denial-of-service resulting from stack consumption via a crafted sass file, because of certain incorrect parsing of '%' as a modulo operator in parser.cpp.
<p>Publish Date: 2018-12-04
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-19837>CVE-2018-19837</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: None
- User Interaction: Required
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-19837">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-19837</a></p>
<p>Fix Resolution: 3.5.5</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 node sass tgz cve medium severity vulnerability vulnerable library node sass tgz wrapper around libsass library home page a href path to dependency file testing package json path to vulnerable library testing node modules node sass package json testing node modules node sass package json dependency hierarchy x node sass tgz vulnerable library vulnerability details in libsass prior to sass eval operator sass binary expression inside eval cpp allows attackers to cause a denial of service resulting from stack consumption via a crafted sass file because of certain incorrect parsing of as a modulo operator in parser cpp 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 none integrity impact none availability impact high for more information on scores click a href suggested fix type upgrade version origin a href fix resolution step up your open source security game with whitesource | 0 |
41,949 | 10,724,718,985 | IssuesEvent | 2019-10-28 03:02:06 | cakephp/cakephp | https://api.github.com/repos/cakephp/cakephp | closed | Auth Component _unauthenticated should accept return value as boolean | defect documentation | This is a (multiple allowed):
* [x] bug
* [ ] enhancement
* [ ] feature-discussion (RFC)
* CakePHP Version: 4.0.0-beta4
* Platform and Target: Windows 10 FIrefox Nightly 72.0a1 (2019-10-21) (64-bit) Wamp Apache php 7.2.14, Mysql 5.7.24
### What you did
Custom unauthenticated function in plugin to check guest permission of action.
### What happened
If guest permission is available then this function should return true (Boolean).
### What you expected to happen
Auth component following functions must accept return value as Boolean
startup()
authCheck()
_unauthenticated()
| 1.0 | Auth Component _unauthenticated should accept return value as boolean - This is a (multiple allowed):
* [x] bug
* [ ] enhancement
* [ ] feature-discussion (RFC)
* CakePHP Version: 4.0.0-beta4
* Platform and Target: Windows 10 FIrefox Nightly 72.0a1 (2019-10-21) (64-bit) Wamp Apache php 7.2.14, Mysql 5.7.24
### What you did
Custom unauthenticated function in plugin to check guest permission of action.
### What happened
If guest permission is available then this function should return true (Boolean).
### What you expected to happen
Auth component following functions must accept return value as Boolean
startup()
authCheck()
_unauthenticated()
| non_priority | auth component unauthenticated should accept return value as boolean this is a multiple allowed bug enhancement feature discussion rfc cakephp version platform and target windows firefox nightly bit wamp apache php mysql what you did custom unauthenticated function in plugin to check guest permission of action what happened if guest permission is available then this function should return true boolean what you expected to happen auth component following functions must accept return value as boolean startup authcheck unauthenticated | 0 |
306,290 | 26,454,875,464 | IssuesEvent | 2023-01-16 13:49:15 | GSilviq/Teodor.bg | https://api.github.com/repos/GSilviq/Teodor.bg | opened | Adding a default delivery address successfully | Positive test case | Pre-conditions:
1.The application www.teodor.bg is loaded.
2.Valid user exist in the system.
3.The user is logged in to the application.
Steps:
1
Click on "Account icon" on the top right corner
Expected result
Is redirected to main "Account page"
2
Navigate to left side on the page and clicks on the "Моите адреси"
Expected result
The current address is displayed
3
Press "Добави нов адрес" button
Expected result
Is redirected to "Добави нов адрес" page
4
Fill mandatory detail as expected
Expected result
1.The user press" Запиши адрес" button
2. The address has been successfully saved | 1.0 | Adding a default delivery address successfully - Pre-conditions:
1.The application www.teodor.bg is loaded.
2.Valid user exist in the system.
3.The user is logged in to the application.
Steps:
1
Click on "Account icon" on the top right corner
Expected result
Is redirected to main "Account page"
2
Navigate to left side on the page and clicks on the "Моите адреси"
Expected result
The current address is displayed
3
Press "Добави нов адрес" button
Expected result
Is redirected to "Добави нов адрес" page
4
Fill mandatory detail as expected
Expected result
1.The user press" Запиши адрес" button
2. The address has been successfully saved | non_priority | adding a default delivery address successfully pre conditions the application is loaded valid user exist in the system the user is logged in to the application steps click on account icon on the top right corner expected result is redirected to main account page navigate to left side on the page and clicks on the моите адреси expected result the current address is displayed press добави нов адрес button expected result is redirected to добави нов адрес page fill mandatory detail as expected expected result the user press запиши адрес button the address has been successfully saved | 0 |
312,840 | 26,881,257,789 | IssuesEvent | 2023-02-05 17:10:28 | PalisadoesFoundation/talawa-admin | https://api.github.com/repos/PalisadoesFoundation/talawa-admin | closed | Code Coverage: Create tests for OrganizationDashboard.tsx | good first issue test points 01 | - Please coordinate **issue assignment** and **PR reviews** with the contributors listed in this issue https://github.com/PalisadoesFoundation/talawa/issues/359
We will need unittests done for all methods, classes and functions found in this file.
Any widgets referenced in this file must also have unittests done
```
src/screens/OrganizationDashboard/OrganizationDashboard.tsx
```
- Parent Issue: https://github.com/PalisadoesFoundation/talawa-admin/issues/241
### PR Acceptance Criteria
- When complete this file must show **100%** coverage when merged into the code base.
- [The current code coverage for the file can be found here](https://app.codecov.io/gh/PalisadoesFoundation/talawa-admin?search=&displayType=list)
- The PR will show a report for the code coverage for the file you have added. You can use that as a guide
| 1.0 | Code Coverage: Create tests for OrganizationDashboard.tsx - - Please coordinate **issue assignment** and **PR reviews** with the contributors listed in this issue https://github.com/PalisadoesFoundation/talawa/issues/359
We will need unittests done for all methods, classes and functions found in this file.
Any widgets referenced in this file must also have unittests done
```
src/screens/OrganizationDashboard/OrganizationDashboard.tsx
```
- Parent Issue: https://github.com/PalisadoesFoundation/talawa-admin/issues/241
### PR Acceptance Criteria
- When complete this file must show **100%** coverage when merged into the code base.
- [The current code coverage for the file can be found here](https://app.codecov.io/gh/PalisadoesFoundation/talawa-admin?search=&displayType=list)
- The PR will show a report for the code coverage for the file you have added. You can use that as a guide
| non_priority | code coverage create tests for organizationdashboard tsx please coordinate issue assignment and pr reviews with the contributors listed in this issue we will need unittests done for all methods classes and functions found in this file any widgets referenced in this file must also have unittests done src screens organizationdashboard organizationdashboard tsx parent issue pr acceptance criteria when complete this file must show coverage when merged into the code base the pr will show a report for the code coverage for the file you have added you can use that as a guide | 0 |
132,332 | 12,504,359,495 | IssuesEvent | 2020-06-02 08:53:09 | kyma-incubator/compass | https://api.github.com/repos/kyma-incubator/compass | closed | Compass connectivity guidelines | Epic area/documentation area/management-plane enhancement wontfix | <!-- Thank you for your contribution. Before you submit the issue:
1. Search open and closed issues for duplicates.
2. Read the contributing guidelines.
-->
**Description**
We need to have a separate chapter containing information for developers implementing Compass integration. The chapter should contain guidelines describing how the software that works along Compass should be designed and integrated.
Topics to be covered:
- What data should be stored in external application's data model
- Certificate rotation: guidelines for implementing job that renews certificate (it should mention private key rotation)
- Certificate revocation
Topics should reference code examples.
**Reasons**
Information important for developers implementing Compass integration is distributed in various documents. Some information is included in the architecture description, some even in Kyma repository What we need is the single place where all important knowledge for implementing any integration is gathered. | 1.0 | Compass connectivity guidelines - <!-- Thank you for your contribution. Before you submit the issue:
1. Search open and closed issues for duplicates.
2. Read the contributing guidelines.
-->
**Description**
We need to have a separate chapter containing information for developers implementing Compass integration. The chapter should contain guidelines describing how the software that works along Compass should be designed and integrated.
Topics to be covered:
- What data should be stored in external application's data model
- Certificate rotation: guidelines for implementing job that renews certificate (it should mention private key rotation)
- Certificate revocation
Topics should reference code examples.
**Reasons**
Information important for developers implementing Compass integration is distributed in various documents. Some information is included in the architecture description, some even in Kyma repository What we need is the single place where all important knowledge for implementing any integration is gathered. | non_priority | compass connectivity guidelines thank you for your contribution before you submit the issue search open and closed issues for duplicates read the contributing guidelines description we need to have a separate chapter containing information for developers implementing compass integration the chapter should contain guidelines describing how the software that works along compass should be designed and integrated topics to be covered what data should be stored in external application s data model certificate rotation guidelines for implementing job that renews certificate it should mention private key rotation certificate revocation topics should reference code examples reasons information important for developers implementing compass integration is distributed in various documents some information is included in the architecture description some even in kyma repository what we need is the single place where all important knowledge for implementing any integration is gathered | 0 |
286,399 | 31,562,484,915 | IssuesEvent | 2023-09-03 12:27:06 | Arthurdw/firefly | https://api.github.com/repos/Arthurdw/firefly | closed | pretty_env_logger-0.4.0.crate: 1 vulnerabilities (highest severity is: 9.8) | Mend: dependency security vulnerability | <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>pretty_env_logger-0.4.0.crate</b></p></summary>
<p></p>
<p>
</details>
## Vulnerabilities
| CVE | Severity | <img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS | Dependency | Type | Fixed in (pretty_env_logger version) | Remediation Available |
| ------------- | ------------- | ----- | ----- | ----- | ------------- | --- |
| [WS-2023-0223](https://github.com/advisories/GHSA-g98v-hv3f-hcfr) | <img src='https://whitesource-resources.whitesourcesoftware.com/critical_vul.png?' width=19 height=20> Critical | 9.8 | atty-0.2.14.crate | Transitive | N/A* | ❌ |
<p>*For some transitive vulnerabilities, there is no version of direct dependency with a fix. Check the "Details" section below to see if there is a version of transitive dependency where vulnerability is fixed.</p>
## Details
<details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/critical_vul.png?' width=19 height=20> WS-2023-0223</summary>
### Vulnerable Library - <b>atty-0.2.14.crate</b></p>
<p>A simple interface for querying atty</p>
<p>Library home page: <a href="https://crates.io/api/v1/crates/atty/0.2.14/download">https://crates.io/api/v1/crates/atty/0.2.14/download</a></p>
<p>
Dependency Hierarchy:
- pretty_env_logger-0.4.0.crate (Root Library)
- env_logger-0.7.1.crate
- :x: **atty-0.2.14.crate** (Vulnerable Library)
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
atty potential unaligned read
<p>Publish Date: 2023-06-30
<p>URL: <a href=https://github.com/advisories/GHSA-g98v-hv3f-hcfr>WS-2023-0223</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>
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
</details> | True | pretty_env_logger-0.4.0.crate: 1 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>pretty_env_logger-0.4.0.crate</b></p></summary>
<p></p>
<p>
</details>
## Vulnerabilities
| CVE | Severity | <img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS | Dependency | Type | Fixed in (pretty_env_logger version) | Remediation Available |
| ------------- | ------------- | ----- | ----- | ----- | ------------- | --- |
| [WS-2023-0223](https://github.com/advisories/GHSA-g98v-hv3f-hcfr) | <img src='https://whitesource-resources.whitesourcesoftware.com/critical_vul.png?' width=19 height=20> Critical | 9.8 | atty-0.2.14.crate | Transitive | N/A* | ❌ |
<p>*For some transitive vulnerabilities, there is no version of direct dependency with a fix. Check the "Details" section below to see if there is a version of transitive dependency where vulnerability is fixed.</p>
## Details
<details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/critical_vul.png?' width=19 height=20> WS-2023-0223</summary>
### Vulnerable Library - <b>atty-0.2.14.crate</b></p>
<p>A simple interface for querying atty</p>
<p>Library home page: <a href="https://crates.io/api/v1/crates/atty/0.2.14/download">https://crates.io/api/v1/crates/atty/0.2.14/download</a></p>
<p>
Dependency Hierarchy:
- pretty_env_logger-0.4.0.crate (Root Library)
- env_logger-0.7.1.crate
- :x: **atty-0.2.14.crate** (Vulnerable Library)
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
atty potential unaligned read
<p>Publish Date: 2023-06-30
<p>URL: <a href=https://github.com/advisories/GHSA-g98v-hv3f-hcfr>WS-2023-0223</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>
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
</details> | non_priority | pretty env logger crate vulnerabilities highest severity is vulnerable library pretty env logger crate vulnerabilities cve severity cvss dependency type fixed in pretty env logger version remediation available critical atty crate transitive n a for some transitive vulnerabilities there is no version of direct dependency with a fix check the details section below to see if there is a version of transitive dependency where vulnerability is fixed details ws vulnerable library atty crate a simple interface for querying atty library home page a href dependency hierarchy pretty env logger crate root library env logger crate x atty crate vulnerable library found in base branch master vulnerability details atty potential unaligned read 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 step up your open source security game with mend | 0 |
154,036 | 13,534,325,806 | IssuesEvent | 2020-09-16 05:25:54 | reganbaucke/JuDGE.jl | https://api.github.com/repos/reganbaucke/JuDGE.jl | closed | Online documentation | documentation | Create online documentation detailing how to set up trees, expansion variables, sub_problems and overall models. | 1.0 | Online documentation - Create online documentation detailing how to set up trees, expansion variables, sub_problems and overall models. | non_priority | online documentation create online documentation detailing how to set up trees expansion variables sub problems and overall models | 0 |
228,808 | 18,263,062,515 | IssuesEvent | 2021-10-04 03:31:43 | ceoss-kmitl/ceoss-frontend | https://api.github.com/repos/ceoss-kmitl/ceoss-frontend | closed | Refine Menu v2 UI | feature frontend no-test | ## Scope
- ตอนปิดหน้าอยากให้กดตรงที่ว่างข้างนอกได้ด้วย
- field ตำแหน่งบริหารชวนสับสน ถ้าไม่ได้เป็นผู้บริหารก็ควรมีข้อความ เป็นช่องเปล่า ๆ แล้วมันงง ๆ | 1.0 | Refine Menu v2 UI - ## Scope
- ตอนปิดหน้าอยากให้กดตรงที่ว่างข้างนอกได้ด้วย
- field ตำแหน่งบริหารชวนสับสน ถ้าไม่ได้เป็นผู้บริหารก็ควรมีข้อความ เป็นช่องเปล่า ๆ แล้วมันงง ๆ | non_priority | refine menu ui scope ตอนปิดหน้าอยากให้กดตรงที่ว่างข้างนอกได้ด้วย field ตำแหน่งบริหารชวนสับสน ถ้าไม่ได้เป็นผู้บริหารก็ควรมีข้อความ เป็นช่องเปล่า ๆ แล้วมันงง ๆ | 0 |
165,101 | 20,574,160,373 | IssuesEvent | 2022-03-04 01:26:40 | panasalap/linux-4.1.15 | https://api.github.com/repos/panasalap/linux-4.1.15 | closed | CVE-2017-13215 (High) detected in linux-stable-rtv4.1.33 - autoclosed | security vulnerability | ## CVE-2017-13215 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>linux-stable-rtv4.1.33</b></p></summary>
<p>
<p>Julia Cartwright's fork of linux-stable-rt.git</p>
<p>Library home page: <a href=https://git.kernel.org/pub/scm/linux/kernel/git/julia/linux-stable-rt.git>https://git.kernel.org/pub/scm/linux/kernel/git/julia/linux-stable-rt.git</a></p>
<p>Found in HEAD commit: <a href="https://github.com/panasalap/linux-4.1.15/commit/aae4c2fa46027fd4c477372871df090c6b94f3f1">aae4c2fa46027fd4c477372871df090c6b94f3f1</a></p>
<p>Found in base branch: <b>master</b></p></p>
</details>
</p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Source Files (2)</summary>
<p></p>
<p>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/crypto/algif_skcipher.c</b>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/crypto/algif_skcipher.c</b>
</p>
</details>
<p></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
A elevation of privilege vulnerability in the Upstream kernel skcipher. Product: Android. Versions: Android kernel. Android ID: A-64386293. References: Upstream kernel.
<p>Publish Date: 2018-01-12
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2017-13215>CVE-2017-13215</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.8</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="http://www.securitytracker.com/id/1040106">http://www.securitytracker.com/id/1040106</a></p>
<p>Fix Resolution: The vendor has issued a fix (2018-01-01 security patch level; 2018-01-05 security patch level).
The vendor advisory is available at:
https://source.android.com/security/bulletin/2018-01-01</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | CVE-2017-13215 (High) detected in linux-stable-rtv4.1.33 - autoclosed - ## CVE-2017-13215 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>linux-stable-rtv4.1.33</b></p></summary>
<p>
<p>Julia Cartwright's fork of linux-stable-rt.git</p>
<p>Library home page: <a href=https://git.kernel.org/pub/scm/linux/kernel/git/julia/linux-stable-rt.git>https://git.kernel.org/pub/scm/linux/kernel/git/julia/linux-stable-rt.git</a></p>
<p>Found in HEAD commit: <a href="https://github.com/panasalap/linux-4.1.15/commit/aae4c2fa46027fd4c477372871df090c6b94f3f1">aae4c2fa46027fd4c477372871df090c6b94f3f1</a></p>
<p>Found in base branch: <b>master</b></p></p>
</details>
</p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Source Files (2)</summary>
<p></p>
<p>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/crypto/algif_skcipher.c</b>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/crypto/algif_skcipher.c</b>
</p>
</details>
<p></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
A elevation of privilege vulnerability in the Upstream kernel skcipher. Product: Android. Versions: Android kernel. Android ID: A-64386293. References: Upstream kernel.
<p>Publish Date: 2018-01-12
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2017-13215>CVE-2017-13215</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.8</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="http://www.securitytracker.com/id/1040106">http://www.securitytracker.com/id/1040106</a></p>
<p>Fix Resolution: The vendor has issued a fix (2018-01-01 security patch level; 2018-01-05 security patch level).
The vendor advisory is available at:
https://source.android.com/security/bulletin/2018-01-01</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 linux stable autoclosed cve high severity vulnerability vulnerable library linux stable julia cartwright s fork of linux stable rt git library home page a href found in head commit a href found in base branch master vulnerable source files crypto algif skcipher c crypto algif skcipher c vulnerability details a elevation of privilege vulnerability in the upstream kernel skcipher product android versions android kernel android id a references upstream kernel 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 fix resolution the vendor has issued a fix security patch level security patch level the vendor advisory is available at step up your open source security game with whitesource | 0 |
75,528 | 7,476,436,465 | IssuesEvent | 2018-04-04 03:06:56 | openbmc/openbmc-test-automation | https://api.github.com/repos/openbmc/openbmc-test-automation | closed | IPMI Test use cases for Basic IPL | Test |
IPMI Power ON,
Power OFF,
Power Cycle
Power Soft,
Power Reset,
BMC Reset
BMC Reboot
IPMI Warm/Cold MC Reset <-- This is in review | 1.0 | IPMI Test use cases for Basic IPL -
IPMI Power ON,
Power OFF,
Power Cycle
Power Soft,
Power Reset,
BMC Reset
BMC Reboot
IPMI Warm/Cold MC Reset <-- This is in review | non_priority | ipmi test use cases for basic ipl ipmi power on power off power cycle power soft power reset bmc reset bmc reboot ipmi warm cold mc reset this is in review | 0 |
127,309 | 18,010,393,397 | IssuesEvent | 2021-09-16 07:55:46 | maddyCode23/linux-4.1.15 | https://api.github.com/repos/maddyCode23/linux-4.1.15 | opened | CVE-2021-3348 (High) detected in linux-stable-rtv4.1.33 | security vulnerability | ## CVE-2021-3348 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>linux-stable-rtv4.1.33</b></p></summary>
<p>
<p>Julia Cartwright's fork of linux-stable-rt.git</p>
<p>Library home page: <a href=https://git.kernel.org/pub/scm/linux/kernel/git/julia/linux-stable-rt.git>https://git.kernel.org/pub/scm/linux/kernel/git/julia/linux-stable-rt.git</a></p>
<p>Found in HEAD commit: <a href="https://github.com/maddyCode23/linux-4.1.15/commit/f1f3d2b150be669390b32dfea28e773471bdd6e7">f1f3d2b150be669390b32dfea28e773471bdd6e7</a></p>
</p>
</details>
</p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Source Files (2)</summary>
<p></p>
<p>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/drivers/block/nbd.c</b>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/drivers/block/nbd.c</b>
</p>
</details>
<p></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
nbd_add_socket in drivers/block/nbd.c in the Linux kernel through 5.10.12 has an ndb_queue_rq use-after-free that could be triggered by local attackers (with access to the nbd device) via an I/O request at a certain point during device setup, aka CID-b98e762e3d71.
<p>Publish Date: 2021-02-01
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-3348>CVE-2021-3348</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.0</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: High
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://www.linuxkernelcves.com/cves/CVE-2021-3348">https://www.linuxkernelcves.com/cves/CVE-2021-3348</a></p>
<p>Release Date: 2021-02-01</p>
<p>Fix Resolution: v4.14.219,4.19.173,v5.4.95,v5.10.13</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-3348 (High) detected in linux-stable-rtv4.1.33 - ## CVE-2021-3348 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>linux-stable-rtv4.1.33</b></p></summary>
<p>
<p>Julia Cartwright's fork of linux-stable-rt.git</p>
<p>Library home page: <a href=https://git.kernel.org/pub/scm/linux/kernel/git/julia/linux-stable-rt.git>https://git.kernel.org/pub/scm/linux/kernel/git/julia/linux-stable-rt.git</a></p>
<p>Found in HEAD commit: <a href="https://github.com/maddyCode23/linux-4.1.15/commit/f1f3d2b150be669390b32dfea28e773471bdd6e7">f1f3d2b150be669390b32dfea28e773471bdd6e7</a></p>
</p>
</details>
</p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Source Files (2)</summary>
<p></p>
<p>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/drivers/block/nbd.c</b>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/drivers/block/nbd.c</b>
</p>
</details>
<p></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
nbd_add_socket in drivers/block/nbd.c in the Linux kernel through 5.10.12 has an ndb_queue_rq use-after-free that could be triggered by local attackers (with access to the nbd device) via an I/O request at a certain point during device setup, aka CID-b98e762e3d71.
<p>Publish Date: 2021-02-01
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-3348>CVE-2021-3348</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.0</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: High
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://www.linuxkernelcves.com/cves/CVE-2021-3348">https://www.linuxkernelcves.com/cves/CVE-2021-3348</a></p>
<p>Release Date: 2021-02-01</p>
<p>Fix Resolution: v4.14.219,4.19.173,v5.4.95,v5.10.13</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 linux stable cve high severity vulnerability vulnerable library linux stable julia cartwright s fork of linux stable rt git library home page a href found in head commit a href vulnerable source files drivers block nbd c drivers block nbd c vulnerability details nbd add socket in drivers block nbd c in the linux kernel through has an ndb queue rq use after free that could be triggered by local attackers with access to the nbd device via an i o request at a certain point during device setup aka cid publish date url a href cvss score details base score metrics exploitability metrics attack vector local attack complexity high privileges required low user interaction none scope unchanged impact metrics confidentiality impact high integrity impact high availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution step up your open source security game with whitesource | 0 |
32,725 | 4,787,666,700 | IssuesEvent | 2016-10-30 04:30:37 | SegMail/SegMail | https://api.github.com/repos/SegMail/SegMail | closed | MailMerge | Feature Ready for Int Tests | To keep things simple, MailMerge will just use simple text and be parsed into html links. We don't have the technical expertise to make fancy buttons in the frontend email editor. The alternative would be just provide a link, like "<a href='!confirm'>Confirm</a>" so that users can add in their own button images or text. When MailMerge service parses the email body, it just needs to look for the string '!confirm' and replace it with the proper landing page link. | 1.0 | MailMerge - To keep things simple, MailMerge will just use simple text and be parsed into html links. We don't have the technical expertise to make fancy buttons in the frontend email editor. The alternative would be just provide a link, like "<a href='!confirm'>Confirm</a>" so that users can add in their own button images or text. When MailMerge service parses the email body, it just needs to look for the string '!confirm' and replace it with the proper landing page link. | non_priority | mailmerge to keep things simple mailmerge will just use simple text and be parsed into html links we don t have the technical expertise to make fancy buttons in the frontend email editor the alternative would be just provide a link like confirm so that users can add in their own button images or text when mailmerge service parses the email body it just needs to look for the string confirm and replace it with the proper landing page link | 0 |
297,149 | 22,341,977,898 | IssuesEvent | 2022-06-15 02:25:29 | Studio-Ops-Org/Studio-2022-S1-Repo | https://api.github.com/repos/Studio-Ops-Org/Studio-2022-S1-Repo | closed | Snapshot Documentation | Documentation Extra Comments | Create documentation around the process of snapshotting a machine, creating a disk, and deploying a new machine. Include screenshots where applicable and use our Azure conventions for tagging.
- [x] Creating a snapshot
- [x] Creating a disk from the snapshot
- [x] Deploying a new VM from the disk
- [x] Swapping the disk on an already created VM
Upload to **General > Projects > Miscellaneous** before class on Thursday the 14th of April. | 1.0 | Snapshot Documentation - Create documentation around the process of snapshotting a machine, creating a disk, and deploying a new machine. Include screenshots where applicable and use our Azure conventions for tagging.
- [x] Creating a snapshot
- [x] Creating a disk from the snapshot
- [x] Deploying a new VM from the disk
- [x] Swapping the disk on an already created VM
Upload to **General > Projects > Miscellaneous** before class on Thursday the 14th of April. | non_priority | snapshot documentation create documentation around the process of snapshotting a machine creating a disk and deploying a new machine include screenshots where applicable and use our azure conventions for tagging creating a snapshot creating a disk from the snapshot deploying a new vm from the disk swapping the disk on an already created vm upload to general projects miscellaneous before class on thursday the of april | 0 |
125,661 | 12,265,483,578 | IssuesEvent | 2020-05-07 07:15:00 | athleea/GoodFounded | https://api.github.com/repos/athleea/GoodFounded | opened | 메인 화면 세부 기획 | documentation | 메인 화면 이란?
1. 앱이 실행되면 처음으로 보여지는 화면
2. 하단 네이게이션 탭에 홈 아이콘을 누르면 보여지는 화면
메인 화면의 보여줄 내용들을 세부적으로 기획하여야한다. | 1.0 | 메인 화면 세부 기획 - 메인 화면 이란?
1. 앱이 실행되면 처음으로 보여지는 화면
2. 하단 네이게이션 탭에 홈 아이콘을 누르면 보여지는 화면
메인 화면의 보여줄 내용들을 세부적으로 기획하여야한다. | non_priority | 메인 화면 세부 기획 메인 화면 이란 앱이 실행되면 처음으로 보여지는 화면 하단 네이게이션 탭에 홈 아이콘을 누르면 보여지는 화면 메인 화면의 보여줄 내용들을 세부적으로 기획하여야한다 | 0 |
101,942 | 21,880,126,361 | IssuesEvent | 2022-05-19 13:42:35 | FuelLabs/sway | https://api.github.com/repos/FuelLabs/sway | closed | Deprecate the concrete implementations related to `HashMethod` from `hash.sw` when generics are implemented | good first issue lib: std code quality | We first need to complete
- [x] #1511
- [x] #1552
Then we can remove the concrete implementations because the generics handle those cases. | 1.0 | Deprecate the concrete implementations related to `HashMethod` from `hash.sw` when generics are implemented - We first need to complete
- [x] #1511
- [x] #1552
Then we can remove the concrete implementations because the generics handle those cases. | non_priority | deprecate the concrete implementations related to hashmethod from hash sw when generics are implemented we first need to complete then we can remove the concrete implementations because the generics handle those cases | 0 |
262,379 | 22,837,523,672 | IssuesEvent | 2022-07-12 18:10:33 | MarinaFX/Fiero | https://api.github.com/repos/MarinaFX/Fiero | opened | [FEATURE] US 4 | TK 46 Develop Front/Back-end integration on Challenges List Screen [2] | Feature UI Back-end Tests | # Develop Front/Back-end integration on Challenges List Screen ✏️
# Description 📝
## Project Info 📈
> - US **4**
> - Task
- ID: **46**
- Title: **Develop Front/Back-end integration on Challenges List Screen**
## Expected Behaviour ✅
When going to the home screen of the App, all challenges created by the user should be fetched from the Database and inserted into a list
**Additional context** 🌎
Unit testing of the request should be provided as well
| 1.0 | [FEATURE] US 4 | TK 46 Develop Front/Back-end integration on Challenges List Screen [2] - # Develop Front/Back-end integration on Challenges List Screen ✏️
# Description 📝
## Project Info 📈
> - US **4**
> - Task
- ID: **46**
- Title: **Develop Front/Back-end integration on Challenges List Screen**
## Expected Behaviour ✅
When going to the home screen of the App, all challenges created by the user should be fetched from the Database and inserted into a list
**Additional context** 🌎
Unit testing of the request should be provided as well
| non_priority | us tk develop front back end integration on challenges list screen develop front back end integration on challenges list screen ✏️ description 📝 project info 📈 us task id title develop front back end integration on challenges list screen expected behaviour ✅ when going to the home screen of the app all challenges created by the user should be fetched from the database and inserted into a list additional context 🌎 unit testing of the request should be provided as well | 0 |
245,029 | 26,503,761,108 | IssuesEvent | 2023-01-18 12:20:22 | snowdensb/caseflow | https://api.github.com/repos/snowdensb/caseflow | opened | CVE-2022-25901 (Medium) detected in cookiejar-2.1.2.tgz | security vulnerability | ## CVE-2022-25901 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>cookiejar-2.1.2.tgz</b></p></summary>
<p>simple persistent cookiejar system</p>
<p>Library home page: <a href="https://registry.npmjs.org/cookiejar/-/cookiejar-2.1.2.tgz">https://registry.npmjs.org/cookiejar/-/cookiejar-2.1.2.tgz</a></p>
<p>Path to dependency file: /client/package.json</p>
<p>Path to vulnerable library: /client/node_modules/cookiejar/package.json</p>
<p>
Dependency Hierarchy:
- superagent-3.8.3.tgz (Root Library)
- :x: **cookiejar-2.1.2.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/snowdensb/caseflow/commit/81f8b3f5658022f994993a18a7653667705b7f6e">81f8b3f5658022f994993a18a7653667705b7f6e</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>
Versions of the package cookiejar before 2.1.4 are vulnerable to Regular Expression Denial of Service (ReDoS) via the Cookie.parse function, which uses an insecure regular expression.
<p>Publish Date: 2023-01-18
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-25901>CVE-2022-25901</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: 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>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Release Date: 2023-01-18</p>
<p>Fix Resolution: cookiejar - 2.1.4</p>
</p>
</details>
<p></p>
| True | CVE-2022-25901 (Medium) detected in cookiejar-2.1.2.tgz - ## CVE-2022-25901 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>cookiejar-2.1.2.tgz</b></p></summary>
<p>simple persistent cookiejar system</p>
<p>Library home page: <a href="https://registry.npmjs.org/cookiejar/-/cookiejar-2.1.2.tgz">https://registry.npmjs.org/cookiejar/-/cookiejar-2.1.2.tgz</a></p>
<p>Path to dependency file: /client/package.json</p>
<p>Path to vulnerable library: /client/node_modules/cookiejar/package.json</p>
<p>
Dependency Hierarchy:
- superagent-3.8.3.tgz (Root Library)
- :x: **cookiejar-2.1.2.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/snowdensb/caseflow/commit/81f8b3f5658022f994993a18a7653667705b7f6e">81f8b3f5658022f994993a18a7653667705b7f6e</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>
Versions of the package cookiejar before 2.1.4 are vulnerable to Regular Expression Denial of Service (ReDoS) via the Cookie.parse function, which uses an insecure regular expression.
<p>Publish Date: 2023-01-18
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-25901>CVE-2022-25901</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: 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>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Release Date: 2023-01-18</p>
<p>Fix Resolution: cookiejar - 2.1.4</p>
</p>
</details>
<p></p>
| non_priority | cve medium detected in cookiejar tgz cve medium severity vulnerability vulnerable library cookiejar tgz simple persistent cookiejar system library home page a href path to dependency file client package json path to vulnerable library client node modules cookiejar package json dependency hierarchy superagent tgz root library x cookiejar tgz vulnerable library found in head commit a href found in base branch master vulnerability details versions of the package cookiejar before are vulnerable to regular expression denial of service redos via the cookie parse function which uses an insecure regular expression 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 low for more information on scores click a href suggested fix type upgrade version release date fix resolution cookiejar | 0 |
105,245 | 16,628,119,568 | IssuesEvent | 2021-06-03 12:22:45 | elastic/kibana | https://api.github.com/repos/elastic/kibana | opened | [Security Solution] No back button from the Event Filters Tab to the Integration Tab | Team: SecuritySolution Team:Onboarding and Lifecycle Mgt bug impact:medium v7.14.0 | **Describe the feature**
No back button from the Event Filters Tab to the Integration
**Build Details:**
```
VERSION: 7.14.0-SNAPSHOT
BUILD: 41403
COMMIT: 4f0781737cdb5cf9b5dfa624368b4306b5d6bcb0
ARTIFACT: https://artifacts-api.elastic.co/v1/search/7.14.0-SNAPSHOT
```
**Preconditions**
1. Elastic 7.13.0 environment should be deployed.
**Steps to Reproduce**
1. Navigate to the Integrations Tab under the Fleet
2. Select the Endpoint Security Integration
3. Navigate to the Advanced tab
4. Navigate to the 'Trusted Apps' & observe there is a link to navigate back to the Endpoint Security Integration.
5. Navigate to the 'Event Filters & observe there is no link to navigate back to the Endpoint Security Integration.
**Test data**
N/A
**Impacted Test case(s)**
N/A
**Actual Result**
No back button from the Event Filters Tab to the Integration
**Expected Result**
There should be a back button from the Event Filters Tab to the Integration
**What's Working**
N/A
**What's Not Working**
N/A
**Screenshot**
- Advanced Tab:
- Trusted Applications Tab:
- Event Filter Tab:
**Logs**:
N/A | True | [Security Solution] No back button from the Event Filters Tab to the Integration Tab - **Describe the feature**
No back button from the Event Filters Tab to the Integration
**Build Details:**
```
VERSION: 7.14.0-SNAPSHOT
BUILD: 41403
COMMIT: 4f0781737cdb5cf9b5dfa624368b4306b5d6bcb0
ARTIFACT: https://artifacts-api.elastic.co/v1/search/7.14.0-SNAPSHOT
```
**Preconditions**
1. Elastic 7.13.0 environment should be deployed.
**Steps to Reproduce**
1. Navigate to the Integrations Tab under the Fleet
2. Select the Endpoint Security Integration
3. Navigate to the Advanced tab
4. Navigate to the 'Trusted Apps' & observe there is a link to navigate back to the Endpoint Security Integration.
5. Navigate to the 'Event Filters & observe there is no link to navigate back to the Endpoint Security Integration.
**Test data**
N/A
**Impacted Test case(s)**
N/A
**Actual Result**
No back button from the Event Filters Tab to the Integration
**Expected Result**
There should be a back button from the Event Filters Tab to the Integration
**What's Working**
N/A
**What's Not Working**
N/A
**Screenshot**
- Advanced Tab:
- Trusted Applications Tab:
- Event Filter Tab:
**Logs**:
N/A | non_priority | no back button from the event filters tab to the integration tab describe the feature no back button from the event filters tab to the integration build details version snapshot build commit artifact preconditions elastic environment should be deployed steps to reproduce navigate to the integrations tab under the fleet select the endpoint security integration navigate to the advanced tab navigate to the trusted apps observe there is a link to navigate back to the endpoint security integration navigate to the event filters observe there is no link to navigate back to the endpoint security integration test data n a impacted test case s n a actual result no back button from the event filters tab to the integration expected result there should be a back button from the event filters tab to the integration what s working n a what s not working n a screenshot advanced tab trusted applications tab event filter tab logs n a | 0 |
59,024 | 14,365,777,490 | IssuesEvent | 2020-12-01 02:39:44 | NixOS/nixpkgs | https://api.github.com/repos/NixOS/nixpkgs | closed | Vulnerability roundup 85: oauth2_proxy-3.2.0: 2 advisories [6.1] | 1.severity: security | [search](https://search.nix.gsc.io/?q=oauth2_proxy&i=fosho&repos=NixOS-nixpkgs), [files](https://github.com/NixOS/nixpkgs/search?utf8=%E2%9C%93&q=oauth2_proxy+in%3Apath&type=Code)
* [ ] [CVE-2020-5233](https://nvd.nist.gov/vuln/detail/CVE-2020-5233) CVSSv3=6.1 (nixos-20.03)
* [ ] [CVE-2020-11053](https://nvd.nist.gov/vuln/detail/CVE-2020-11053) CVSSv3=6.1 (nixos-20.03)
Scanned versions: nixos-20.03: a84b797b28e. May contain false positives.
Cc @ehmry
Cc @lethalman
Cc @yorickvp
| True | Vulnerability roundup 85: oauth2_proxy-3.2.0: 2 advisories [6.1] - [search](https://search.nix.gsc.io/?q=oauth2_proxy&i=fosho&repos=NixOS-nixpkgs), [files](https://github.com/NixOS/nixpkgs/search?utf8=%E2%9C%93&q=oauth2_proxy+in%3Apath&type=Code)
* [ ] [CVE-2020-5233](https://nvd.nist.gov/vuln/detail/CVE-2020-5233) CVSSv3=6.1 (nixos-20.03)
* [ ] [CVE-2020-11053](https://nvd.nist.gov/vuln/detail/CVE-2020-11053) CVSSv3=6.1 (nixos-20.03)
Scanned versions: nixos-20.03: a84b797b28e. May contain false positives.
Cc @ehmry
Cc @lethalman
Cc @yorickvp
| non_priority | vulnerability roundup proxy advisories nixos nixos scanned versions nixos may contain false positives cc ehmry cc lethalman cc yorickvp | 0 |
107,767 | 11,570,744,019 | IssuesEvent | 2020-02-20 20:06:22 | enenra/space-engineers-utilities | https://api.github.com/repos/enenra/space-engineers-utilities | closed | Print reminder to include texture files in mod into log | documentation enhancement export | Specifically if:
* it's a local material
* it's a non-standard MatLib
Possibly also mark custom matlibs in matlib panel? and change them to not display file format... | 1.0 | Print reminder to include texture files in mod into log - Specifically if:
* it's a local material
* it's a non-standard MatLib
Possibly also mark custom matlibs in matlib panel? and change them to not display file format... | non_priority | print reminder to include texture files in mod into log specifically if it s a local material it s a non standard matlib possibly also mark custom matlibs in matlib panel and change them to not display file format | 0 |
218,063 | 16,920,557,601 | IssuesEvent | 2021-06-25 04:35:01 | AtlasOfLivingAustralia/la-pipelines | https://api.github.com/repos/AtlasOfLivingAustralia/la-pipelines | closed | Record view issues | testing-findings | Compare current prod vs biocache Quoll
https://biocache-test.ala.org.au/occurrences/b2b2d325-6c4c-40f5-a479-b1d03359c764
https://biocache.ala.org.au/occurrences/b2b2d325-6c4c-40f5-a479-b1d03359c764
1. ~~Occurrence record title is missing~~
2. ~~Additional properties missing~~, ~~instead Dynamic properties is displayed with JSON content.~~ #346
3. ~~"Data quality tests" list is very short~~
4. ~~Missing "Additional political boundaries information" section~~
5. ~~Missing "Environmental sampling for this location" section~~
6. ~~Missing Catalog number and Other catalog numbers~~
7. Basis of record appears as UNKNOWN supplied basis "Genomic DNA"
8. Licence appears as UNSPECIFIED instead of CC-By-Int
9. ~~Geospatial section: No Locality, Longitude and Latitude. Is coordinate precision not expected as per the decision of not implementing gbif/pipelines#517 or it should still display the value regardless.~~ | 1.0 | Record view issues - Compare current prod vs biocache Quoll
https://biocache-test.ala.org.au/occurrences/b2b2d325-6c4c-40f5-a479-b1d03359c764
https://biocache.ala.org.au/occurrences/b2b2d325-6c4c-40f5-a479-b1d03359c764
1. ~~Occurrence record title is missing~~
2. ~~Additional properties missing~~, ~~instead Dynamic properties is displayed with JSON content.~~ #346
3. ~~"Data quality tests" list is very short~~
4. ~~Missing "Additional political boundaries information" section~~
5. ~~Missing "Environmental sampling for this location" section~~
6. ~~Missing Catalog number and Other catalog numbers~~
7. Basis of record appears as UNKNOWN supplied basis "Genomic DNA"
8. Licence appears as UNSPECIFIED instead of CC-By-Int
9. ~~Geospatial section: No Locality, Longitude and Latitude. Is coordinate precision not expected as per the decision of not implementing gbif/pipelines#517 or it should still display the value regardless.~~ | non_priority | record view issues compare current prod vs biocache quoll occurrence record title is missing additional properties missing instead dynamic properties is displayed with json content data quality tests list is very short missing additional political boundaries information section missing environmental sampling for this location section missing catalog number and other catalog numbers basis of record appears as unknown supplied basis genomic dna licence appears as unspecified instead of cc by int geospatial section no locality longitude and latitude is coordinate precision not expected as per the decision of not implementing gbif pipelines or it should still display the value regardless | 0 |
230,852 | 25,482,782,640 | IssuesEvent | 2022-11-26 01:30:44 | Satheesh575555/linux-4.1.15 | https://api.github.com/repos/Satheesh575555/linux-4.1.15 | reopened | CVE-2016-8666 (Medium) detected in multiple libraries | security vulnerability | ## CVE-2016-8666 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>linuxlinux-4.6</b>, <b>linuxlinux-4.6</b>, <b>linuxlinux-4.6</b>, <b>linuxlinux-4.6</b></p></summary>
<p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
The IP stack in the Linux kernel before 4.6 allows remote attackers to cause a denial of service (stack consumption and panic) or possibly have unspecified other impact by triggering use of the GRO path for packets with tunnel stacking, as demonstrated by interleaved IPv4 headers and GRE headers, a related issue to CVE-2016-7039.
<p>Publish Date: 2016-10-16
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2016-8666>CVE-2016-8666</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.9</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://nvd.nist.gov/vuln/detail/CVE-2016-8666">https://nvd.nist.gov/vuln/detail/CVE-2016-8666</a></p>
<p>Release Date: 2016-10-16</p>
<p>Fix Resolution: 4.6</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-2016-8666 (Medium) detected in multiple libraries - ## CVE-2016-8666 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>linuxlinux-4.6</b>, <b>linuxlinux-4.6</b>, <b>linuxlinux-4.6</b>, <b>linuxlinux-4.6</b></p></summary>
<p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
The IP stack in the Linux kernel before 4.6 allows remote attackers to cause a denial of service (stack consumption and panic) or possibly have unspecified other impact by triggering use of the GRO path for packets with tunnel stacking, as demonstrated by interleaved IPv4 headers and GRE headers, a related issue to CVE-2016-7039.
<p>Publish Date: 2016-10-16
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2016-8666>CVE-2016-8666</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.9</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://nvd.nist.gov/vuln/detail/CVE-2016-8666">https://nvd.nist.gov/vuln/detail/CVE-2016-8666</a></p>
<p>Release Date: 2016-10-16</p>
<p>Fix Resolution: 4.6</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_priority | cve medium detected in multiple libraries cve medium severity vulnerability vulnerable libraries linuxlinux linuxlinux linuxlinux linuxlinux vulnerability details the ip stack in the linux kernel before allows remote attackers to cause a denial of service stack consumption and panic or possibly have unspecified other impact by triggering use of the gro path for packets with tunnel stacking as demonstrated by interleaved headers and gre headers a related issue to cve publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity high privileges required none user interaction none scope unchanged impact metrics confidentiality impact none integrity impact none availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution step up your open source security game with mend | 0 |
19,151 | 6,676,606,181 | IssuesEvent | 2017-10-05 06:50:28 | klee/klee | https://api.github.com/repos/klee/klee | closed | CMake clean issue and runtime dependency bug | bug build system | Typing `make clean` in a build directory does not remove the `.bc` files for the KLEE runtime.
@delcypher , can you take a look at this? Thanks. | 1.0 | CMake clean issue and runtime dependency bug - Typing `make clean` in a build directory does not remove the `.bc` files for the KLEE runtime.
@delcypher , can you take a look at this? Thanks. | non_priority | cmake clean issue and runtime dependency bug typing make clean in a build directory does not remove the bc files for the klee runtime delcypher can you take a look at this thanks | 0 |
288,894 | 31,930,984,230 | IssuesEvent | 2023-09-19 07:24:28 | Trinadh465/linux-4.1.15_CVE-2023-4128 | https://api.github.com/repos/Trinadh465/linux-4.1.15_CVE-2023-4128 | opened | CVE-2017-18216 (Medium) detected in linuxlinux-4.6 | Mend: dependency security vulnerability | ## CVE-2017-18216 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>linuxlinux-4.6</b></p></summary>
<p>
<p>The Linux Kernel</p>
<p>Library home page: <a href=https://mirrors.edge.kernel.org/pub/linux/kernel/v4.x/?wsslib=linux>https://mirrors.edge.kernel.org/pub/linux/kernel/v4.x/?wsslib=linux</a></p>
<p>Found in HEAD commit: <a href="https://github.com/Trinadh465/linux-4.1.15_CVE-2023-4128/commit/0c6c8d8c809f697cd5fc581c6c08e9ad646c55a8">0c6c8d8c809f697cd5fc581c6c08e9ad646c55a8</a></p>
<p>Found in base branch: <b>main</b></p></p>
</details>
</p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Source Files (2)</summary>
<p></p>
<p>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/fs/ocfs2/cluster/nodemanager.c</b>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/fs/ocfs2/cluster/nodemanager.c</b>
</p>
</details>
<p></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> Vulnerability Details</summary>
<p>
In fs/ocfs2/cluster/nodemanager.c in the Linux kernel before 4.15, local users can cause a denial of service (NULL pointer dereference and BUG) because a required mutex is not used.
<p>Publish Date: 2018-03-05
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2017-18216>CVE-2017-18216</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://nvd.nist.gov/vuln/detail/CVE-2017-18216">https://nvd.nist.gov/vuln/detail/CVE-2017-18216</a></p>
<p>Release Date: 2018-03-05</p>
<p>Fix Resolution: 4.15</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | CVE-2017-18216 (Medium) detected in linuxlinux-4.6 - ## CVE-2017-18216 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>linuxlinux-4.6</b></p></summary>
<p>
<p>The Linux Kernel</p>
<p>Library home page: <a href=https://mirrors.edge.kernel.org/pub/linux/kernel/v4.x/?wsslib=linux>https://mirrors.edge.kernel.org/pub/linux/kernel/v4.x/?wsslib=linux</a></p>
<p>Found in HEAD commit: <a href="https://github.com/Trinadh465/linux-4.1.15_CVE-2023-4128/commit/0c6c8d8c809f697cd5fc581c6c08e9ad646c55a8">0c6c8d8c809f697cd5fc581c6c08e9ad646c55a8</a></p>
<p>Found in base branch: <b>main</b></p></p>
</details>
</p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Source Files (2)</summary>
<p></p>
<p>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/fs/ocfs2/cluster/nodemanager.c</b>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/fs/ocfs2/cluster/nodemanager.c</b>
</p>
</details>
<p></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> Vulnerability Details</summary>
<p>
In fs/ocfs2/cluster/nodemanager.c in the Linux kernel before 4.15, local users can cause a denial of service (NULL pointer dereference and BUG) because a required mutex is not used.
<p>Publish Date: 2018-03-05
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2017-18216>CVE-2017-18216</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://nvd.nist.gov/vuln/detail/CVE-2017-18216">https://nvd.nist.gov/vuln/detail/CVE-2017-18216</a></p>
<p>Release Date: 2018-03-05</p>
<p>Fix Resolution: 4.15</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 linuxlinux cve medium severity vulnerability vulnerable library linuxlinux the linux kernel library home page a href found in head commit a href found in base branch main vulnerable source files fs cluster nodemanager c fs cluster nodemanager c vulnerability details in fs cluster nodemanager c in the linux kernel before local users can cause a denial of service null pointer dereference and bug because a required mutex is not used publish date url a href cvss score details base score metrics exploitability metrics attack vector local attack complexity low privileges required low user interaction none scope unchanged impact metrics confidentiality impact none integrity impact none availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution step up your open source security game with mend | 0 |
197,274 | 15,648,634,945 | IssuesEvent | 2021-03-23 06:08:26 | seanpm2001/SPM_FoodIndex | https://api.github.com/repos/seanpm2001/SPM_FoodIndex | opened | Feature request: nutrional values for all entries + vegetarianism info | documentation enhancement |
***
### Feature request: nutrional values for all entries + vegetarianism info
As the title says, but also: why I can't go Vegan, why I chose to go Vegetarian, historical idles who were vegan/vegetarian.
This update will take a lot of time, but won't be much work.
***
| 1.0 | Feature request: nutrional values for all entries + vegetarianism info -
***
### Feature request: nutrional values for all entries + vegetarianism info
As the title says, but also: why I can't go Vegan, why I chose to go Vegetarian, historical idles who were vegan/vegetarian.
This update will take a lot of time, but won't be much work.
***
| non_priority | feature request nutrional values for all entries vegetarianism info feature request nutrional values for all entries vegetarianism info as the title says but also why i can t go vegan why i chose to go vegetarian historical idles who were vegan vegetarian this update will take a lot of time but won t be much work | 0 |
112,959 | 17,114,077,726 | IssuesEvent | 2021-07-11 00:31:43 | AlexRogalskiy/ws-documents | https://api.github.com/repos/AlexRogalskiy/ws-documents | closed | CVE-2021-21349 (High) detected in xstream-1.4.11.1.jar | no-issue-activity security vulnerability | ## CVE-2021-21349 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>xstream-1.4.11.1.jar</b></p></summary>
<p>XStream is a serialization library from Java objects to XML and back.</p>
<p>Library home page: <a href="http://x-stream.github.io">http://x-stream.github.io</a></p>
<p>Path to dependency file: ws-documents/modules/document-generator/pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/com/thoughtworks/xstream/xstream/1.4.11.1/xstream-1.4.11.1.jar,/home/wss-scanner/.m2/repository/com/thoughtworks/xstream/xstream/1.4.11.1/xstream-1.4.11.1.jar,/home/wss-scanner/.m2/repository/com/thoughtworks/xstream/xstream/1.4.11.1/xstream-1.4.11.1.jar,/home/wss-scanner/.m2/repository/com/thoughtworks/xstream/xstream/1.4.11.1/xstream-1.4.11.1.jar,/home/wss-scanner/.m2/repository/com/thoughtworks/xstream/xstream/1.4.11.1/xstream-1.4.11.1.jar</p>
<p>
Dependency Hierarchy:
- spring-cloud-starter-netflix-eureka-client-2.2.5.RELEASE.jar (Root Library)
- :x: **xstream-1.4.11.1.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/AlexRogalskiy/ws-documents/commit/f0ca974033183c586fb41762fb7d7f4730a99acc">f0ca974033183c586fb41762fb7d7f4730a99acc</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
XStream is a Java library to serialize objects to XML and back again. In XStream before version 1.4.16, there is a vulnerability which may allow a remote attacker to request data from internal resources that are not publicly available only by manipulating the processed input stream. No user is affected, who followed the recommendation to setup XStream's security framework with a whitelist limited to the minimal required types. If you rely on XStream's default blacklist of the Security Framework, you will have to use at least version 1.4.16.
<p>Publish Date: 2021-03-23
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-21349>CVE-2021-21349</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: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: None
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/x-stream/xstream/security/advisories/GHSA-f6hm-88x3-mfjv">https://github.com/x-stream/xstream/security/advisories/GHSA-f6hm-88x3-mfjv</a></p>
<p>Release Date: 2021-03-23</p>
<p>Fix Resolution: com.thoughtworks.xstream:xstream:1.4.16</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-21349 (High) detected in xstream-1.4.11.1.jar - ## CVE-2021-21349 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>xstream-1.4.11.1.jar</b></p></summary>
<p>XStream is a serialization library from Java objects to XML and back.</p>
<p>Library home page: <a href="http://x-stream.github.io">http://x-stream.github.io</a></p>
<p>Path to dependency file: ws-documents/modules/document-generator/pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/com/thoughtworks/xstream/xstream/1.4.11.1/xstream-1.4.11.1.jar,/home/wss-scanner/.m2/repository/com/thoughtworks/xstream/xstream/1.4.11.1/xstream-1.4.11.1.jar,/home/wss-scanner/.m2/repository/com/thoughtworks/xstream/xstream/1.4.11.1/xstream-1.4.11.1.jar,/home/wss-scanner/.m2/repository/com/thoughtworks/xstream/xstream/1.4.11.1/xstream-1.4.11.1.jar,/home/wss-scanner/.m2/repository/com/thoughtworks/xstream/xstream/1.4.11.1/xstream-1.4.11.1.jar</p>
<p>
Dependency Hierarchy:
- spring-cloud-starter-netflix-eureka-client-2.2.5.RELEASE.jar (Root Library)
- :x: **xstream-1.4.11.1.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/AlexRogalskiy/ws-documents/commit/f0ca974033183c586fb41762fb7d7f4730a99acc">f0ca974033183c586fb41762fb7d7f4730a99acc</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
XStream is a Java library to serialize objects to XML and back again. In XStream before version 1.4.16, there is a vulnerability which may allow a remote attacker to request data from internal resources that are not publicly available only by manipulating the processed input stream. No user is affected, who followed the recommendation to setup XStream's security framework with a whitelist limited to the minimal required types. If you rely on XStream's default blacklist of the Security Framework, you will have to use at least version 1.4.16.
<p>Publish Date: 2021-03-23
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-21349>CVE-2021-21349</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: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: None
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/x-stream/xstream/security/advisories/GHSA-f6hm-88x3-mfjv">https://github.com/x-stream/xstream/security/advisories/GHSA-f6hm-88x3-mfjv</a></p>
<p>Release Date: 2021-03-23</p>
<p>Fix Resolution: com.thoughtworks.xstream:xstream:1.4.16</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 xstream jar cve high severity vulnerability vulnerable library xstream jar xstream is a serialization library from java objects to xml and back library home page a href path to dependency file ws documents modules document generator pom xml path to vulnerable library home wss scanner repository com thoughtworks xstream xstream xstream jar home wss scanner repository com thoughtworks xstream xstream xstream jar home wss scanner repository com thoughtworks xstream xstream xstream jar home wss scanner repository com thoughtworks xstream xstream xstream jar home wss scanner repository com thoughtworks xstream xstream xstream jar dependency hierarchy spring cloud starter netflix eureka client release jar root library x xstream jar vulnerable library found in head commit a href vulnerability details xstream is a java library to serialize objects to xml and back again in xstream before version there is a vulnerability which may allow a remote attacker to request data from internal resources that are not publicly available only by manipulating the processed input stream no user is affected who followed the recommendation to setup xstream s security framework with a whitelist limited to the minimal required types if you rely on xstream s default blacklist of the security framework you will have to use at least version publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope changed impact metrics confidentiality impact high integrity impact none availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution com thoughtworks xstream xstream step up your open source security game with whitesource | 0 |
31,661 | 13,610,571,679 | IssuesEvent | 2020-09-23 07:35:06 | microsoft/botframework-solutions | https://api.github.com/repos/microsoft/botframework-solutions | closed | [MS Teams] Unable to upload attachments to bot | Bot Services Needs Triage Type: Bug customer-replied-to customer-reported | Hi,
We have 1v1 bot available to our users through MS Teams. Since roughly this week, it is no longer possible to upload attachments to the bot - it fails with error (see below).
The uploading itself is done simply by opening up chat window with bot, clicking on paperclip icon, clicking on _Upload from my computer_ and finally choosing the file to upload:
The progress bar then appears:
After uploading completes, the following error popup is displayed and attachment is not sent over:
Additional notes:
* Choosing _Onedrive_ option does not show the error popup, but no file is sent - nothing happens.
* The file type and size does not matter. But all the tests were done with png and txt file with no more than few kilobytes.
* The error happens in both the desktop and web version of Teams client.
* Same error happens for all of our Teams enabled bots, including one that was set up just last week.
* The error does not happen if inline image is pasted and sent over.
* The Teams tenant is based in Europe.
* This should be irrelevant, but the bot itself is powered by .NET SDK of MS Bot Framework v4 and hosted in Azure with MS Teams enabled as one of its channels.
For the reference, here is Teams package manifest:
```
{
"$schema": "https://developer.microsoft.com/en-us/json-schemas/teams/v1.7/MicrosoftTeams.schema.json",
"manifestVersion": "1.7",
"version": "0.0.1",
"id": "<removed>",
"packageName": "<removed>",
"developer": {
"name": "<removed>",
"websiteUrl": "<removed>",
"privacyUrl": "<removed>",
"termsOfUseUrl": "<removed>"
},
"icons": {
"color": "color.png",
"outline": "outline.png"
},
"name": {
"short": "<removed>",
"full": "<removed>"
},
"description": {
"short": "<removed>",
"full": "<removed>"
},
"accentColor": "#761092",
"bots": [
{
"botId": "<removed>",
"scopes": [
"personal"
],
"supportsFiles": true,
"isNotificationOnly": false
}
],
"permissions": [
"identity",
"messageTeamMembers"
],
"validDomains": []
}
```
Will appreciate any ideas, thanks. | 1.0 | [MS Teams] Unable to upload attachments to bot - Hi,
We have 1v1 bot available to our users through MS Teams. Since roughly this week, it is no longer possible to upload attachments to the bot - it fails with error (see below).
The uploading itself is done simply by opening up chat window with bot, clicking on paperclip icon, clicking on _Upload from my computer_ and finally choosing the file to upload:
The progress bar then appears:
After uploading completes, the following error popup is displayed and attachment is not sent over:
Additional notes:
* Choosing _Onedrive_ option does not show the error popup, but no file is sent - nothing happens.
* The file type and size does not matter. But all the tests were done with png and txt file with no more than few kilobytes.
* The error happens in both the desktop and web version of Teams client.
* Same error happens for all of our Teams enabled bots, including one that was set up just last week.
* The error does not happen if inline image is pasted and sent over.
* The Teams tenant is based in Europe.
* This should be irrelevant, but the bot itself is powered by .NET SDK of MS Bot Framework v4 and hosted in Azure with MS Teams enabled as one of its channels.
For the reference, here is Teams package manifest:
```
{
"$schema": "https://developer.microsoft.com/en-us/json-schemas/teams/v1.7/MicrosoftTeams.schema.json",
"manifestVersion": "1.7",
"version": "0.0.1",
"id": "<removed>",
"packageName": "<removed>",
"developer": {
"name": "<removed>",
"websiteUrl": "<removed>",
"privacyUrl": "<removed>",
"termsOfUseUrl": "<removed>"
},
"icons": {
"color": "color.png",
"outline": "outline.png"
},
"name": {
"short": "<removed>",
"full": "<removed>"
},
"description": {
"short": "<removed>",
"full": "<removed>"
},
"accentColor": "#761092",
"bots": [
{
"botId": "<removed>",
"scopes": [
"personal"
],
"supportsFiles": true,
"isNotificationOnly": false
}
],
"permissions": [
"identity",
"messageTeamMembers"
],
"validDomains": []
}
```
Will appreciate any ideas, thanks. | non_priority | unable to upload attachments to bot hi we have bot available to our users through ms teams since roughly this week it is no longer possible to upload attachments to the bot it fails with error see below the uploading itself is done simply by opening up chat window with bot clicking on paperclip icon clicking on upload from my computer and finally choosing the file to upload the progress bar then appears after uploading completes the following error popup is displayed and attachment is not sent over additional notes choosing onedrive option does not show the error popup but no file is sent nothing happens the file type and size does not matter but all the tests were done with png and txt file with no more than few kilobytes the error happens in both the desktop and web version of teams client same error happens for all of our teams enabled bots including one that was set up just last week the error does not happen if inline image is pasted and sent over the teams tenant is based in europe this should be irrelevant but the bot itself is powered by net sdk of ms bot framework and hosted in azure with ms teams enabled as one of its channels for the reference here is teams package manifest schema manifestversion version id packagename developer name websiteurl privacyurl termsofuseurl icons color color png outline outline png name short full description short full accentcolor bots botid scopes personal supportsfiles true isnotificationonly false permissions identity messageteammembers validdomains will appreciate any ideas thanks | 0 |
242,447 | 26,269,392,567 | IssuesEvent | 2023-01-06 15:33:55 | yaeljacobs67/npm-plugin | https://api.github.com/repos/yaeljacobs67/npm-plugin | opened | CVE-2021-23362 (Medium) detected in hosted-git-info-2.6.0.tgz | security vulnerability | ## CVE-2021-23362 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>hosted-git-info-2.6.0.tgz</b></p></summary>
<p>Provides metadata and conversions from repository urls for Github, Bitbucket and Gitlab</p>
<p>Library home page: <a href="https://registry.npmjs.org/hosted-git-info/-/hosted-git-info-2.6.0.tgz">https://registry.npmjs.org/hosted-git-info/-/hosted-git-info-2.6.0.tgz</a></p>
<p>Path to dependency file: /npm-plugin/package.json</p>
<p>Path to vulnerable library: /node_modules/hosted-git-info/package.json</p>
<p>
Dependency Hierarchy:
- grunt-1.0.3.tgz (Root Library)
- dateformat-1.0.12.tgz
- meow-3.7.0.tgz
- normalize-package-data-2.4.0.tgz
- :x: **hosted-git-info-2.6.0.tgz** (Vulnerable Library)
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
The package hosted-git-info before 3.0.8 are vulnerable to Regular Expression Denial of Service (ReDoS) via regular expression shortcutMatch in the fromUrl function in index.js. The affected regular expression exhibits polynomial worst-case time complexity.
<p>Publish Date: 2021-03-23
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2021-23362>CVE-2021-23362</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: 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>
</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-43f8-2h32-f4cj">https://github.com/advisories/GHSA-43f8-2h32-f4cj</a></p>
<p>Release Date: 2021-03-23</p>
<p>Fix Resolution (hosted-git-info): 2.8.9</p>
<p>Direct dependency fix Resolution (grunt): 1.0.4</p>
</p>
</details>
<p></p>
***
<!-- REMEDIATE-OPEN-PR-START -->
- [ ] Check this box to open an automated fix PR
<!-- REMEDIATE-OPEN-PR-END -->
| True | CVE-2021-23362 (Medium) detected in hosted-git-info-2.6.0.tgz - ## CVE-2021-23362 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>hosted-git-info-2.6.0.tgz</b></p></summary>
<p>Provides metadata and conversions from repository urls for Github, Bitbucket and Gitlab</p>
<p>Library home page: <a href="https://registry.npmjs.org/hosted-git-info/-/hosted-git-info-2.6.0.tgz">https://registry.npmjs.org/hosted-git-info/-/hosted-git-info-2.6.0.tgz</a></p>
<p>Path to dependency file: /npm-plugin/package.json</p>
<p>Path to vulnerable library: /node_modules/hosted-git-info/package.json</p>
<p>
Dependency Hierarchy:
- grunt-1.0.3.tgz (Root Library)
- dateformat-1.0.12.tgz
- meow-3.7.0.tgz
- normalize-package-data-2.4.0.tgz
- :x: **hosted-git-info-2.6.0.tgz** (Vulnerable Library)
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
The package hosted-git-info before 3.0.8 are vulnerable to Regular Expression Denial of Service (ReDoS) via regular expression shortcutMatch in the fromUrl function in index.js. The affected regular expression exhibits polynomial worst-case time complexity.
<p>Publish Date: 2021-03-23
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2021-23362>CVE-2021-23362</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: 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>
</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-43f8-2h32-f4cj">https://github.com/advisories/GHSA-43f8-2h32-f4cj</a></p>
<p>Release Date: 2021-03-23</p>
<p>Fix Resolution (hosted-git-info): 2.8.9</p>
<p>Direct dependency fix Resolution (grunt): 1.0.4</p>
</p>
</details>
<p></p>
***
<!-- REMEDIATE-OPEN-PR-START -->
- [ ] Check this box to open an automated fix PR
<!-- REMEDIATE-OPEN-PR-END -->
| non_priority | cve medium detected in hosted git info tgz cve medium severity vulnerability vulnerable library hosted git info tgz provides metadata and conversions from repository urls for github bitbucket and gitlab library home page a href path to dependency file npm plugin package json path to vulnerable library node modules hosted git info package json dependency hierarchy grunt tgz root library dateformat tgz meow tgz normalize package data tgz x hosted git info tgz vulnerable library vulnerability details the package hosted git info before are vulnerable to regular expression denial of service redos via regular expression shortcutmatch in the fromurl function in index js the affected regular expression exhibits polynomial worst case time complexity publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact none integrity impact none availability impact low for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution hosted git info direct dependency fix resolution grunt check this box to open an automated fix pr | 0 |
340,377 | 24,651,725,744 | IssuesEvent | 2022-10-17 19:15:18 | dotnet/runtime | https://api.github.com/repos/dotnet/runtime | reopened | Assembly.LoadFrom treats parameter as path rather than URI | documentation area-System.Reflection | ## Description
`Assembly.LoadFrom` is supposed to take a URI as its parameter:
> The `assemblyFile` parameter must refer to a URI without escape characters. This method supplies escape characters for all invalid characters in the URI.
([docs.microsoft.com](https://docs.microsoft.com/en-us/dotnet/api/system.reflection.assembly.loadfrom))
On .NET Framework, you can pass in a `file://` URI (constructed from the `Assembly.CodeBase` URI of another assembly, for example) to `Assembly.LoadFrom` and the assembly will be loaded.
On .NET Core, the `assemblyFile` parameter is treated as a path. The URI gets passed into `Path.GetFullPath` which mangles the URI to begin with and continues to treat it as a path from there on. This never works for loading an assembly from any URI.
https://github.com/dotnet/runtime/blob/a92f4f02dcbbd76cb9edf682424d001b9eb6d870/src/libraries/System.Private.CoreLib/src/System/Reflection/Assembly.cs#L329-L334
For `file://` URIs, the behavior of .NET Core should match the behavior of .NET Framework, which is also the documented behavior. I don't have any opinions about whether this should work for non-`file://` URIs.
## Test Case
```c#
System.Reflection.Assembly.LoadFrom(typeof(object).Assembly.CodeBase)
````
On .NET Framework, this returns `[mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]`. On .NET Core, this throws `FileNotFoundException` with a message like `Could not load file or assembly 'C:\YourProject\bin\Debug\netcoreapp2.1\file:\C:\Program Files\dotnet\shared\Microsoft.NETCore.App\2.1.19\System.Private.CoreLib.dll'. The filename, directory name, or volume label syntax is incorrect.`. | 1.0 | Assembly.LoadFrom treats parameter as path rather than URI - ## Description
`Assembly.LoadFrom` is supposed to take a URI as its parameter:
> The `assemblyFile` parameter must refer to a URI without escape characters. This method supplies escape characters for all invalid characters in the URI.
([docs.microsoft.com](https://docs.microsoft.com/en-us/dotnet/api/system.reflection.assembly.loadfrom))
On .NET Framework, you can pass in a `file://` URI (constructed from the `Assembly.CodeBase` URI of another assembly, for example) to `Assembly.LoadFrom` and the assembly will be loaded.
On .NET Core, the `assemblyFile` parameter is treated as a path. The URI gets passed into `Path.GetFullPath` which mangles the URI to begin with and continues to treat it as a path from there on. This never works for loading an assembly from any URI.
https://github.com/dotnet/runtime/blob/a92f4f02dcbbd76cb9edf682424d001b9eb6d870/src/libraries/System.Private.CoreLib/src/System/Reflection/Assembly.cs#L329-L334
For `file://` URIs, the behavior of .NET Core should match the behavior of .NET Framework, which is also the documented behavior. I don't have any opinions about whether this should work for non-`file://` URIs.
## Test Case
```c#
System.Reflection.Assembly.LoadFrom(typeof(object).Assembly.CodeBase)
````
On .NET Framework, this returns `[mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]`. On .NET Core, this throws `FileNotFoundException` with a message like `Could not load file or assembly 'C:\YourProject\bin\Debug\netcoreapp2.1\file:\C:\Program Files\dotnet\shared\Microsoft.NETCore.App\2.1.19\System.Private.CoreLib.dll'. The filename, directory name, or volume label syntax is incorrect.`. | non_priority | assembly loadfrom treats parameter as path rather than uri description assembly loadfrom is supposed to take a uri as its parameter the assemblyfile parameter must refer to a uri without escape characters this method supplies escape characters for all invalid characters in the uri on net framework you can pass in a file uri constructed from the assembly codebase uri of another assembly for example to assembly loadfrom and the assembly will be loaded on net core the assemblyfile parameter is treated as a path the uri gets passed into path getfullpath which mangles the uri to begin with and continues to treat it as a path from there on this never works for loading an assembly from any uri for file uris the behavior of net core should match the behavior of net framework which is also the documented behavior i don t have any opinions about whether this should work for non file uris test case c system reflection assembly loadfrom typeof object assembly codebase on net framework this returns on net core this throws filenotfoundexception with a message like could not load file or assembly c yourproject bin debug file c program files dotnet shared microsoft netcore app system private corelib dll the filename directory name or volume label syntax is incorrect | 0 |
195,884 | 22,362,798,790 | IssuesEvent | 2022-06-15 22:38:22 | snowflakedb/snowflake-hive-metastore-connector | https://api.github.com/repos/snowflakedb/snowflake-hive-metastore-connector | closed | CVE-2020-36179 (High) detected in jackson-databind-2.6.5.jar | security vulnerability | ## CVE-2020-36179 - 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.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: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/com/fasterxml/jackson/core/jackson-databind/2.6.5/jackson-databind-2.6.5.jar</p>
<p>
Dependency Hierarchy:
- hive-metastore-2.3.5.jar (Root Library)
- hive-serde-2.3.5.jar
- hive-common-2.3.5.jar
- :x: **jackson-databind-2.6.5.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/snowflakedb/snowflake-hive-metastore-connector/commit/37f5b0ac91898ef82cc1bf4610b729970f6eed58">37f5b0ac91898ef82cc1bf4610b729970f6eed58</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>
FasterXML jackson-databind 2.x before 2.9.10.8 mishandles the interaction between serialization gadgets and typing, related to oadd.org.apache.commons.dbcp.cpdsadapter.DriverAdapterCPDS.
<p>Publish Date: 2021-01-07
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-36179>CVE-2020-36179</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>8.1</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/FasterXML/jackson-databind/issues/3004">https://github.com/FasterXML/jackson-databind/issues/3004</a></p>
<p>Release Date: 2021-01-07</p>
<p>Fix Resolution (com.fasterxml.jackson.core:jackson-databind): 2.6.7.5</p>
<p>Direct dependency fix Resolution (org.apache.hive:hive-metastore): 2.3.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":"org.apache.hive","packageName":"hive-metastore","packageVersion":"2.3.5","packageFilePaths":["/pom.xml"],"isTransitiveDependency":false,"dependencyTree":"org.apache.hive:hive-metastore:2.3.5","isMinimumFixVersionAvailable":true,"minimumFixVersion":"2.3.6","isBinary":false}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2020-36179","vulnerabilityDetails":"FasterXML jackson-databind 2.x before 2.9.10.8 mishandles the interaction between serialization gadgets and typing, related to oadd.org.apache.commons.dbcp.cpdsadapter.DriverAdapterCPDS.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-36179","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-36179 (High) detected in jackson-databind-2.6.5.jar - ## CVE-2020-36179 - 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.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: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/com/fasterxml/jackson/core/jackson-databind/2.6.5/jackson-databind-2.6.5.jar</p>
<p>
Dependency Hierarchy:
- hive-metastore-2.3.5.jar (Root Library)
- hive-serde-2.3.5.jar
- hive-common-2.3.5.jar
- :x: **jackson-databind-2.6.5.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/snowflakedb/snowflake-hive-metastore-connector/commit/37f5b0ac91898ef82cc1bf4610b729970f6eed58">37f5b0ac91898ef82cc1bf4610b729970f6eed58</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>
FasterXML jackson-databind 2.x before 2.9.10.8 mishandles the interaction between serialization gadgets and typing, related to oadd.org.apache.commons.dbcp.cpdsadapter.DriverAdapterCPDS.
<p>Publish Date: 2021-01-07
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-36179>CVE-2020-36179</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>8.1</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/FasterXML/jackson-databind/issues/3004">https://github.com/FasterXML/jackson-databind/issues/3004</a></p>
<p>Release Date: 2021-01-07</p>
<p>Fix Resolution (com.fasterxml.jackson.core:jackson-databind): 2.6.7.5</p>
<p>Direct dependency fix Resolution (org.apache.hive:hive-metastore): 2.3.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":"org.apache.hive","packageName":"hive-metastore","packageVersion":"2.3.5","packageFilePaths":["/pom.xml"],"isTransitiveDependency":false,"dependencyTree":"org.apache.hive:hive-metastore:2.3.5","isMinimumFixVersionAvailable":true,"minimumFixVersion":"2.3.6","isBinary":false}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2020-36179","vulnerabilityDetails":"FasterXML jackson-databind 2.x before 2.9.10.8 mishandles the interaction between serialization gadgets and typing, related to oadd.org.apache.commons.dbcp.cpdsadapter.DriverAdapterCPDS.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-36179","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 pom xml path to vulnerable library home wss scanner repository com fasterxml jackson core jackson databind jackson databind jar dependency hierarchy hive metastore jar root library hive serde jar hive common jar x jackson databind jar vulnerable library found in head commit a href found in base branch master vulnerability details fasterxml jackson databind x before mishandles the interaction between serialization gadgets and typing related to oadd org apache commons dbcp cpdsadapter driveradaptercpds 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 direct dependency fix resolution org apache hive hive metastore rescue worker helmet automatic remediation is available for this issue isopenpronvulnerability true ispackagebased true isdefaultbranch true packages istransitivedependency false dependencytree org apache hive hive metastore isminimumfixversionavailable true minimumfixversion isbinary false basebranches vulnerabilityidentifier cve vulnerabilitydetails fasterxml jackson databind x before mishandles the interaction between serialization gadgets and typing related to oadd org apache commons dbcp cpdsadapter driveradaptercpds vulnerabilityurl | 0 |
39,480 | 20,015,153,037 | IssuesEvent | 2022-02-01 11:15:44 | modin-project/unidist | https://api.github.com/repos/modin-project/unidist | closed | Investigate hotspots for MPI backend on benchmarks | performance 🚀 P1 | We should investigate hotspots for MPI backend on benchmarks (plasticc, cencus, taxi) and try fixing them.
A list of fixed performance issues/PRs:
- #12 | True | Investigate hotspots for MPI backend on benchmarks - We should investigate hotspots for MPI backend on benchmarks (plasticc, cencus, taxi) and try fixing them.
A list of fixed performance issues/PRs:
- #12 | non_priority | investigate hotspots for mpi backend on benchmarks we should investigate hotspots for mpi backend on benchmarks plasticc cencus taxi and try fixing them a list of fixed performance issues prs | 0 |
155,637 | 13,630,272,857 | IssuesEvent | 2020-09-24 16:12:21 | joadeveloped/dataStreaming | https://api.github.com/repos/joadeveloped/dataStreaming | closed | Tablero 1: Kilos pendientes de cosechas | documentation | Avance de proceso según lo estipulado para ese día.
 | 1.0 | Tablero 1: Kilos pendientes de cosechas - Avance de proceso según lo estipulado para ese día.
 | non_priority | tablero kilos pendientes de cosechas avance de proceso según lo estipulado para ese día | 0 |
994 | 2,594,472,388 | IssuesEvent | 2015-02-20 03:55:29 | linkedin/hopscotch | https://api.github.com/repos/linkedin/hopscotch | closed | isTourBubble and showNumber: BUG ? (and an ugly workaround) | code-cleanup | There are two undocumented settings: `showNumber` and `isTourBubble`.
I'd expect that `no-number` class should be added when `showNumber` is `false`. However, it's not the case:
```js
opt = {
...
showNumber: true,
isTourBubble: true
};
...
//Apply classes to bubble. Add "animated" for fade css animation
el.className = 'hopscotch-bubble animated';
if (!opt.isTourBubble) {
utils.addClass(el, 'hopscotch-callout no-number');
}
``` | 1.0 | isTourBubble and showNumber: BUG ? (and an ugly workaround) - There are two undocumented settings: `showNumber` and `isTourBubble`.
I'd expect that `no-number` class should be added when `showNumber` is `false`. However, it's not the case:
```js
opt = {
...
showNumber: true,
isTourBubble: true
};
...
//Apply classes to bubble. Add "animated" for fade css animation
el.className = 'hopscotch-bubble animated';
if (!opt.isTourBubble) {
utils.addClass(el, 'hopscotch-callout no-number');
}
``` | non_priority | istourbubble and shownumber bug and an ugly workaround there are two undocumented settings shownumber and istourbubble i d expect that no number class should be added when shownumber is false however it s not the case js opt shownumber true istourbubble true apply classes to bubble add animated for fade css animation el classname hopscotch bubble animated if opt istourbubble utils addclass el hopscotch callout no number | 0 |
170,225 | 13,179,008,561 | IssuesEvent | 2020-08-12 10:07:45 | photoprism/photoprism | https://api.github.com/repos/photoprism/photoprism | closed | Sporadically: "Month" not properly shown in details view | bug help wanted important please-test | For some photos that got imported, PP does not show the proper value of the month within photo's details view.
The field remains empty, while remaining fields seem to be filled properly.
The error occurred for several photos imported in local PP instance, as well as at least for one - if not more - photos as in public PP demo.
Trigger for the problem is unknown.
Steps to reproduce:
OK:
Import Photos to PP
NOK
Check Photos' details: Navigation bar "Photos" -> select impacted photo(s) -> select "edit" -> select "Details"
Example as from local instance:
Example as in public PP demo:
System details:
- Demo version running on demo.photoprism.org (PhotoPrism™ 200729-65c57f5-Linux-x86_64)
- local instance: PhotoPrism™ 200724-2859549-Linux-x86_64 / Chrome 81.0.4044.138 / macOS 10.15.5
Example original picture:
| 1.0 | Sporadically: "Month" not properly shown in details view - For some photos that got imported, PP does not show the proper value of the month within photo's details view.
The field remains empty, while remaining fields seem to be filled properly.
The error occurred for several photos imported in local PP instance, as well as at least for one - if not more - photos as in public PP demo.
Trigger for the problem is unknown.
Steps to reproduce:
OK:
Import Photos to PP
NOK
Check Photos' details: Navigation bar "Photos" -> select impacted photo(s) -> select "edit" -> select "Details"
Example as from local instance:
Example as in public PP demo:
System details:
- Demo version running on demo.photoprism.org (PhotoPrism™ 200729-65c57f5-Linux-x86_64)
- local instance: PhotoPrism™ 200724-2859549-Linux-x86_64 / Chrome 81.0.4044.138 / macOS 10.15.5
Example original picture:
| non_priority | sporadically month not properly shown in details view for some photos that got imported pp does not show the proper value of the month within photo s details view the field remains empty while remaining fields seem to be filled properly the error occurred for several photos imported in local pp instance as well as at least for one if not more photos as in public pp demo trigger for the problem is unknown steps to reproduce ok import photos to pp nok check photos details navigation bar photos select impacted photo s select edit select details example as from local instance example as in public pp demo system details demo version running on demo photoprism org photoprism™ linux local instance photoprism™ linux chrome macos example original picture | 0 |
328,948 | 28,142,729,122 | IssuesEvent | 2023-04-02 05:29:50 | etcd-io/etcd | https://api.github.com/repos/etcd-io/etcd | closed | [3.4] ./test: line 229: kill: (7520) - No such process | area/testing help wanted stale type/flake | I saw this error multiple times in 3.4 pipeline,
```
{"level":"info","ts":1658452719.9775898,"caller":"tester/cluster.go:585","msg":"closed tester HTTP server","tester-address":"127.0.0.1:9028"}
./test: line 229: kill: (7520) - No such process
./test: line 229: kill: (7521) - No such process
./test: line 229: kill: (7522) - No such process
ETCD_TESTER_EXIT_CODE: 2
FAILED! 'tail -1000 /tmp/etcd-functional-1/etcd.log'
tail: cannot open '/tmp/etcd-functional-1/etcd.log' for reading: No such file or directory
Error: Process completed with exit code 1.
```
Refer to https://github.com/etcd-io/etcd/runs/7460637442?check_suite_focus=true | 1.0 | [3.4] ./test: line 229: kill: (7520) - No such process - I saw this error multiple times in 3.4 pipeline,
```
{"level":"info","ts":1658452719.9775898,"caller":"tester/cluster.go:585","msg":"closed tester HTTP server","tester-address":"127.0.0.1:9028"}
./test: line 229: kill: (7520) - No such process
./test: line 229: kill: (7521) - No such process
./test: line 229: kill: (7522) - No such process
ETCD_TESTER_EXIT_CODE: 2
FAILED! 'tail -1000 /tmp/etcd-functional-1/etcd.log'
tail: cannot open '/tmp/etcd-functional-1/etcd.log' for reading: No such file or directory
Error: Process completed with exit code 1.
```
Refer to https://github.com/etcd-io/etcd/runs/7460637442?check_suite_focus=true | non_priority | test line kill no such process i saw this error multiple times in pipeline level info ts caller tester cluster go msg closed tester http server tester address test line kill no such process test line kill no such process test line kill no such process etcd tester exit code failed tail tmp etcd functional etcd log tail cannot open tmp etcd functional etcd log for reading no such file or directory error process completed with exit code refer to | 0 |
18,711 | 13,067,556,843 | IssuesEvent | 2020-07-31 00:50:29 | icecube-trac/tix2 | https://api.github.com/repos/icecube-trac/tix2 | closed | move ccache caches to build directories (Trac #2032) | Migrated from Trac enhancement infrastructure | CMake's Makefile generator uses the full path of source files during compilation. Because `ccache` uses the command line as a step in building its object hashes, two projects can't use the same cache. For instance, on the SL6 (cvmfs) build bot, there are two build areas
* `~/kipple_cvmfs/docs/`
* `~/kipple_cvmfs/Scientific_Linux_6__new___cvmfs_/`
Currently they share a common cache (`~/.ccache/`), but because CMake uses full paths, the build areas will never share objects in that cache. From a metrics standpoint, this makes it pointless to have a common cache. If we split the cache à la:
* `~/kipple_cvmfs/docs/.ccache/`
* `~/kipple_cvmfs/Scientific_Linux_6__new___cvmfs_/.ccache/`
we're now able to gather more accurate per-build metrics on how well (or not) we're using `ccache` because each build area isn't polluting the other's stats. This will take some use of `ccache`'s environment variables. `CCACHE_BASEDIR` can probably stay the same (`~/kipple_cvmfs`), but `CCACHE_DIR` will have to be set. Since each build area is an individual "bot", this should be fairly clean in the master buildbot config.
Stats should be recorded before and after each build with some kind of "diff" presented to the buildbot worker for display online. This could be as simple as:
```text
cmake -s > stats.0
make
make pybindings
make test-bins
cmake -s > stats.1
diff -u stats.0 stats.1
```
in some combination of buildbot steps. Having accurate stats will allow us to tweak `ccache` to reduce cache misses, and pre-processed cache hits, and increase direct cache hits. This will decrease overall build time.
This should obviously be done after the upgrade to Buildbot 9.
Migrated from https://code.icecube.wisc.edu/ticket/2032
```json
{
"status": "closed",
"changetime": "2019-09-18T07:51:29",
"description": "CMake's Makefile generator uses the full path of source files during compilation. Because `ccache` uses the command line as a step in building its object hashes, two projects can't use the same cache. For instance, on the SL6 (cvmfs) build bot, there are two build areas\n\n * `~/kipple_cvmfs/docs/`\n * `~/kipple_cvmfs/Scientific_Linux_6__new___cvmfs_/`\n\nCurrently they share a common cache (`~/.ccache/`), but because CMake uses full paths, the build areas will never share objects in that cache. From a metrics standpoint, this makes it pointless to have a common cache. If we split the cache \u00e0 la: \n\n * `~/kipple_cvmfs/docs/.ccache/`\n * `~/kipple_cvmfs/Scientific_Linux_6__new___cvmfs_/.ccache/`\n\nwe're now able to gather more accurate per-build metrics on how well (or not) we're using `ccache` because each build area isn't polluting the other's stats. This will take some use of `ccache`'s environment variables. `CCACHE_BASEDIR` can probably stay the same (`~/kipple_cvmfs`), but `CCACHE_DIR` will have to be set. Since each build area is an individual \"bot\", this should be fairly clean in the master buildbot config.\n\nStats should be recorded before and after each build with some kind of \"diff\" presented to the buildbot worker for display online. This could be as simple as:\n{{{\ncmake -s > stats.0\nmake\nmake pybindings\nmake test-bins\ncmake -s > stats.1\ndiff -u stats.0 stats.1\n }}}\nin some combination of buildbot steps. Having accurate stats will allow us to tweak `ccache` to reduce cache misses, and pre-processed cache hits, and increase direct cache hits. This will decrease overall build time.\n\nThis should obviously be done after the upgrade to Buildbot 9.",
"reporter": "nega",
"cc": "",
"resolution": "insufficient resources",
"_ts": "1568793089537035",
"component": "infrastructure",
"summary": "move ccache caches to build directories",
"priority": "minor",
"keywords": "ccache buildbot",
"time": "2017-05-25T16:03:38",
"milestone": "Long-Term Future",
"owner": "nega",
"type": "enhancement"
}
```
| 1.0 | move ccache caches to build directories (Trac #2032) - CMake's Makefile generator uses the full path of source files during compilation. Because `ccache` uses the command line as a step in building its object hashes, two projects can't use the same cache. For instance, on the SL6 (cvmfs) build bot, there are two build areas
* `~/kipple_cvmfs/docs/`
* `~/kipple_cvmfs/Scientific_Linux_6__new___cvmfs_/`
Currently they share a common cache (`~/.ccache/`), but because CMake uses full paths, the build areas will never share objects in that cache. From a metrics standpoint, this makes it pointless to have a common cache. If we split the cache à la:
* `~/kipple_cvmfs/docs/.ccache/`
* `~/kipple_cvmfs/Scientific_Linux_6__new___cvmfs_/.ccache/`
we're now able to gather more accurate per-build metrics on how well (or not) we're using `ccache` because each build area isn't polluting the other's stats. This will take some use of `ccache`'s environment variables. `CCACHE_BASEDIR` can probably stay the same (`~/kipple_cvmfs`), but `CCACHE_DIR` will have to be set. Since each build area is an individual "bot", this should be fairly clean in the master buildbot config.
Stats should be recorded before and after each build with some kind of "diff" presented to the buildbot worker for display online. This could be as simple as:
```text
cmake -s > stats.0
make
make pybindings
make test-bins
cmake -s > stats.1
diff -u stats.0 stats.1
```
in some combination of buildbot steps. Having accurate stats will allow us to tweak `ccache` to reduce cache misses, and pre-processed cache hits, and increase direct cache hits. This will decrease overall build time.
This should obviously be done after the upgrade to Buildbot 9.
Migrated from https://code.icecube.wisc.edu/ticket/2032
```json
{
"status": "closed",
"changetime": "2019-09-18T07:51:29",
"description": "CMake's Makefile generator uses the full path of source files during compilation. Because `ccache` uses the command line as a step in building its object hashes, two projects can't use the same cache. For instance, on the SL6 (cvmfs) build bot, there are two build areas\n\n * `~/kipple_cvmfs/docs/`\n * `~/kipple_cvmfs/Scientific_Linux_6__new___cvmfs_/`\n\nCurrently they share a common cache (`~/.ccache/`), but because CMake uses full paths, the build areas will never share objects in that cache. From a metrics standpoint, this makes it pointless to have a common cache. If we split the cache \u00e0 la: \n\n * `~/kipple_cvmfs/docs/.ccache/`\n * `~/kipple_cvmfs/Scientific_Linux_6__new___cvmfs_/.ccache/`\n\nwe're now able to gather more accurate per-build metrics on how well (or not) we're using `ccache` because each build area isn't polluting the other's stats. This will take some use of `ccache`'s environment variables. `CCACHE_BASEDIR` can probably stay the same (`~/kipple_cvmfs`), but `CCACHE_DIR` will have to be set. Since each build area is an individual \"bot\", this should be fairly clean in the master buildbot config.\n\nStats should be recorded before and after each build with some kind of \"diff\" presented to the buildbot worker for display online. This could be as simple as:\n{{{\ncmake -s > stats.0\nmake\nmake pybindings\nmake test-bins\ncmake -s > stats.1\ndiff -u stats.0 stats.1\n }}}\nin some combination of buildbot steps. Having accurate stats will allow us to tweak `ccache` to reduce cache misses, and pre-processed cache hits, and increase direct cache hits. This will decrease overall build time.\n\nThis should obviously be done after the upgrade to Buildbot 9.",
"reporter": "nega",
"cc": "",
"resolution": "insufficient resources",
"_ts": "1568793089537035",
"component": "infrastructure",
"summary": "move ccache caches to build directories",
"priority": "minor",
"keywords": "ccache buildbot",
"time": "2017-05-25T16:03:38",
"milestone": "Long-Term Future",
"owner": "nega",
"type": "enhancement"
}
```
| non_priority | move ccache caches to build directories trac cmake s makefile generator uses the full path of source files during compilation because ccache uses the command line as a step in building its object hashes two projects can t use the same cache for instance on the cvmfs build bot there are two build areas kipple cvmfs docs kipple cvmfs scientific linux new cvmfs currently they share a common cache ccache but because cmake uses full paths the build areas will never share objects in that cache from a metrics standpoint this makes it pointless to have a common cache if we split the cache à la kipple cvmfs docs ccache kipple cvmfs scientific linux new cvmfs ccache we re now able to gather more accurate per build metrics on how well or not we re using ccache because each build area isn t polluting the other s stats this will take some use of ccache s environment variables ccache basedir can probably stay the same kipple cvmfs but ccache dir will have to be set since each build area is an individual bot this should be fairly clean in the master buildbot config stats should be recorded before and after each build with some kind of diff presented to the buildbot worker for display online this could be as simple as text cmake s stats make make pybindings make test bins cmake s stats diff u stats stats in some combination of buildbot steps having accurate stats will allow us to tweak ccache to reduce cache misses and pre processed cache hits and increase direct cache hits this will decrease overall build time this should obviously be done after the upgrade to buildbot migrated from json status closed changetime description cmake s makefile generator uses the full path of source files during compilation because ccache uses the command line as a step in building its object hashes two projects can t use the same cache for instance on the cvmfs build bot there are two build areas n n kipple cvmfs docs n kipple cvmfs scientific linux new cvmfs n ncurrently they share a common cache ccache but because cmake uses full paths the build areas will never share objects in that cache from a metrics standpoint this makes it pointless to have a common cache if we split the cache la n n kipple cvmfs docs ccache n kipple cvmfs scientific linux new cvmfs ccache n nwe re now able to gather more accurate per build metrics on how well or not we re using ccache because each build area isn t polluting the other s stats this will take some use of ccache s environment variables ccache basedir can probably stay the same kipple cvmfs but ccache dir will have to be set since each build area is an individual bot this should be fairly clean in the master buildbot config n nstats should be recorded before and after each build with some kind of diff presented to the buildbot worker for display online this could be as simple as n ncmake s stats nmake nmake pybindings nmake test bins ncmake s stats ndiff u stats stats n nin some combination of buildbot steps having accurate stats will allow us to tweak ccache to reduce cache misses and pre processed cache hits and increase direct cache hits this will decrease overall build time n nthis should obviously be done after the upgrade to buildbot reporter nega cc resolution insufficient resources ts component infrastructure summary move ccache caches to build directories priority minor keywords ccache buildbot time milestone long term future owner nega type enhancement | 0 |
296,879 | 25,582,694,473 | IssuesEvent | 2022-12-01 06:29:18 | brave/brave-browser | https://api.github.com/repos/brave/brave-browser | closed | VPN auto disconnects when the device goes to sleep for more than an hour | bug OS/macOS OS/Windows QA/Yes QA/Test-Plan-Specified OS/Desktop feature/vpn | <!-- Have you searched for similar issues? Before submitting this issue, please check the open issues and add a note before logging a new issue.
PLEASE USE THE TEMPLATE BELOW TO PROVIDE INFORMATION ABOUT THE ISSUE.
INSUFFICIENT INFO WILL GET THE ISSUE CLOSED. IT WILL ONLY BE REOPENED AFTER SUFFICIENT INFO IS PROVIDED-->
## Description
<!--Provide a brief description of the issue-->
VPN auto disconnects when the device goes to sleep for more than an hour
## Steps to Reproduce
<!--Please add a series of steps to reproduce the issue-->
1. Clean profile 1.46.118
2. Install VPN
3. Wait for device to go to sleep for more than an hour
4. Login back to device, VPN is disconnected
## Actual result:
<!--Please add screenshots if needed-->
VPN auto disconnects when the device goes to sleep for more than an hour
## Expected result:
VPN should not auto disconnect
## Reproduces how often:
<!--[Easily reproduced/Intermittent issue/No steps to reproduce]-->
Easy
## Brave version (brave://version info)
<!--For installed build, please copy Brave, Revision and OS from brave://version and paste here. If building from source please mention it along with brave://version details-->
Brave | 1.46.118 Chromium: 108.0.5359.48 (Official Build) beta (64-bit)
-- | --
Revision | 18ceeca0d99318e70c00d2e04d88aa55488b5c63-refs/branch-heads/5359@{#854}
OS | Windows 10 Version 21H2 (Build 19044.2251)
## Version/Channel Information:
<!--Does this issue happen on any other channels? Or is it specific to a certain channel?-->
- Can you reproduce this issue with the current release? NA
- Can you reproduce this issue with the beta channel? Yes
- Can you reproduce this issue with the nightly channel? Yes
## Other Additional Information:
- Does the issue resolve itself when disabling Brave Shields? NA
- Does the issue resolve itself when disabling Brave Rewards? NA
- Is the issue reproducible on the latest version of Chrome? NA
## Miscellaneous Information:
<!--Any additional information, related issues, extra QA steps, configuration or data that might be necessary to reproduce the issue-->
cc: @brave/qa-team @spylogsster @bsclifton @mattmcalister | 1.0 | VPN auto disconnects when the device goes to sleep for more than an hour - <!-- Have you searched for similar issues? Before submitting this issue, please check the open issues and add a note before logging a new issue.
PLEASE USE THE TEMPLATE BELOW TO PROVIDE INFORMATION ABOUT THE ISSUE.
INSUFFICIENT INFO WILL GET THE ISSUE CLOSED. IT WILL ONLY BE REOPENED AFTER SUFFICIENT INFO IS PROVIDED-->
## Description
<!--Provide a brief description of the issue-->
VPN auto disconnects when the device goes to sleep for more than an hour
## Steps to Reproduce
<!--Please add a series of steps to reproduce the issue-->
1. Clean profile 1.46.118
2. Install VPN
3. Wait for device to go to sleep for more than an hour
4. Login back to device, VPN is disconnected
## Actual result:
<!--Please add screenshots if needed-->
VPN auto disconnects when the device goes to sleep for more than an hour
## Expected result:
VPN should not auto disconnect
## Reproduces how often:
<!--[Easily reproduced/Intermittent issue/No steps to reproduce]-->
Easy
## Brave version (brave://version info)
<!--For installed build, please copy Brave, Revision and OS from brave://version and paste here. If building from source please mention it along with brave://version details-->
Brave | 1.46.118 Chromium: 108.0.5359.48 (Official Build) beta (64-bit)
-- | --
Revision | 18ceeca0d99318e70c00d2e04d88aa55488b5c63-refs/branch-heads/5359@{#854}
OS | Windows 10 Version 21H2 (Build 19044.2251)
## Version/Channel Information:
<!--Does this issue happen on any other channels? Or is it specific to a certain channel?-->
- Can you reproduce this issue with the current release? NA
- Can you reproduce this issue with the beta channel? Yes
- Can you reproduce this issue with the nightly channel? Yes
## Other Additional Information:
- Does the issue resolve itself when disabling Brave Shields? NA
- Does the issue resolve itself when disabling Brave Rewards? NA
- Is the issue reproducible on the latest version of Chrome? NA
## Miscellaneous Information:
<!--Any additional information, related issues, extra QA steps, configuration or data that might be necessary to reproduce the issue-->
cc: @brave/qa-team @spylogsster @bsclifton @mattmcalister | non_priority | vpn auto disconnects when the device goes to sleep for more than an hour have you searched for similar issues before submitting this issue please check the open issues and add a note before logging a new issue please use the template below to provide information about the issue insufficient info will get the issue closed it will only be reopened after sufficient info is provided description vpn auto disconnects when the device goes to sleep for more than an hour steps to reproduce clean profile install vpn wait for device to go to sleep for more than an hour login back to device vpn is disconnected actual result vpn auto disconnects when the device goes to sleep for more than an hour expected result vpn should not auto disconnect reproduces how often easy brave version brave version info brave chromium official build beta bit revision refs branch heads os windows version build version channel information can you reproduce this issue with the current release na can you reproduce this issue with the beta channel yes can you reproduce this issue with the nightly channel yes other additional information does the issue resolve itself when disabling brave shields na does the issue resolve itself when disabling brave rewards na is the issue reproducible on the latest version of chrome na miscellaneous information cc brave qa team spylogsster bsclifton mattmcalister | 0 |
335,412 | 30,028,854,221 | IssuesEvent | 2023-06-27 08:15:53 | unifyai/ivy | https://api.github.com/repos/unifyai/ivy | closed | Fix jax_devicearray.test_jax_special_add | JAX Frontend Sub Task Failing Test | | | |
|---|---|
|jax|<a href="https://github.com/unifyai/ivy/actions/runs/5386564860/jobs/9776762610"><img src=https://img.shields.io/badge/-success-success></a>
|numpy|<a href="https://github.com/unifyai/ivy/actions/runs/5386564860/jobs/9776762610"><img src=https://img.shields.io/badge/-success-success></a>
|tensorflow|<a href="https://github.com/unifyai/ivy/actions/runs/5386564860/jobs/9776762610"><img src=https://img.shields.io/badge/-success-success></a>
|torch|<a href="https://github.com/unifyai/ivy/actions/runs/5386564860/jobs/9776762610"><img src=https://img.shields.io/badge/-success-success></a>
|paddle|<a href="null"><img src=https://img.shields.io/badge/-success-success></a>
| 1.0 | Fix jax_devicearray.test_jax_special_add - | | |
|---|---|
|jax|<a href="https://github.com/unifyai/ivy/actions/runs/5386564860/jobs/9776762610"><img src=https://img.shields.io/badge/-success-success></a>
|numpy|<a href="https://github.com/unifyai/ivy/actions/runs/5386564860/jobs/9776762610"><img src=https://img.shields.io/badge/-success-success></a>
|tensorflow|<a href="https://github.com/unifyai/ivy/actions/runs/5386564860/jobs/9776762610"><img src=https://img.shields.io/badge/-success-success></a>
|torch|<a href="https://github.com/unifyai/ivy/actions/runs/5386564860/jobs/9776762610"><img src=https://img.shields.io/badge/-success-success></a>
|paddle|<a href="null"><img src=https://img.shields.io/badge/-success-success></a>
| non_priority | fix jax devicearray test jax special add jax a href src numpy a href src tensorflow a href src torch a href src paddle img src | 0 |
77,230 | 9,552,071,151 | IssuesEvent | 2019-05-02 15:46:48 | azavea/pwd-fishway | https://api.github.com/repos/azavea/pwd-fishway | opened | Add Fira font to project | design | # Overview
Add the Fira font, including all weights that we will be using in the project. We probably can't just use a Google link, since the client indicated that the internet connection may go down.
## Describe the solution you'd like
- [ ] Add https://mozilla.github.io/Fira/
- [ ] Confirm it works without internet | 1.0 | Add Fira font to project - # Overview
Add the Fira font, including all weights that we will be using in the project. We probably can't just use a Google link, since the client indicated that the internet connection may go down.
## Describe the solution you'd like
- [ ] Add https://mozilla.github.io/Fira/
- [ ] Confirm it works without internet | non_priority | add fira font to project overview add the fira font including all weights that we will be using in the project we probably can t just use a google link since the client indicated that the internet connection may go down describe the solution you d like add confirm it works without internet | 0 |
6,122 | 8,766,359,569 | IssuesEvent | 2018-12-17 16:37:40 | FundacionParaguaya/MentorApp | https://api.github.com/repos/FundacionParaguaya/MentorApp | opened | Remove option to exit process on the final thankyou screen. | UX Requirement | When a user has completed the Life Map and is viewing the thankyou screen they should not have the option to quit the process (nor do they in reality).
**Describe the solution you'd like**
Remove the X option from the top right corner of the screen on the thankyou page.
<img width="362" alt="screen shot 2018-12-17 at 17 32 44" src="https://user-images.githubusercontent.com/45012899/50100941-da3b3380-0221-11e9-903c-719046b4ce87.png">
| 1.0 | Remove option to exit process on the final thankyou screen. - When a user has completed the Life Map and is viewing the thankyou screen they should not have the option to quit the process (nor do they in reality).
**Describe the solution you'd like**
Remove the X option from the top right corner of the screen on the thankyou page.
<img width="362" alt="screen shot 2018-12-17 at 17 32 44" src="https://user-images.githubusercontent.com/45012899/50100941-da3b3380-0221-11e9-903c-719046b4ce87.png">
| non_priority | remove option to exit process on the final thankyou screen when a user has completed the life map and is viewing the thankyou screen they should not have the option to quit the process nor do they in reality describe the solution you d like remove the x option from the top right corner of the screen on the thankyou page img width alt screen shot at src | 0 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.