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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
19,524 | 6,733,510,341 | IssuesEvent | 2017-10-18 15:01:56 | eclipse/omr | https://api.github.com/repos/eclipse/omr | opened | PROPOSAL: Add semantic versioning to JitBuilder API | enhancement jitbuilder | In preparation to record JitBuilder IL (JBIL) under Issue #1818, I would like to start versioning the JitBuilder API so that the version can be written out as part of a JBIL record. With an embedded semantic version (see [http://semver.org/](http://semver.org/)) , any particular JitBuilder library should be able to self certify whether it is qualified to replay the JBIL created from any other (valid :) ) source. Why now, given the JitBuilder API is still missing major features? Because I believe we should be building the versioning notion into our infrastructure now to avoid having to retrofit later. I also think that our existing JitBuilder consumers would benefit from a better notion of how refreshing their JitBuilder library is expected to affect their implementation.
Note that this versioning specifically concerns the API, not the implementation (though, of course, some implementation changes will also implact the API). I have purposefully excluded the implementation because clients should program against the API not the implementation.
Semantic versioning will require a higher standard of code review associated with changes to the JitBuilder API, in that it will only work if committers consistently respect that changes in the API must be properly reflected in updates to the semantic versioning. _**Pull requests should not be merged if they include commits that impact the JitBuilder API without including the appropriate update to the semantic version.**_ Commits will need to be updated to include the version update.
Specifically, the proposal is to:
1) create a base class for all the *Builder classes and for TypeDictionary called something like *BuilderAPI (name subject to feedback)
2) in one particular class, a set of const integers will be introduced that describe the MAJOR, MINOR, and PATCH levels for the JitBuilder API. For hopefully adequate future proofing, I propose MAJOR as a 32-bit unsigned integer value, and MINOR/PATCH as 16-bit unsigned integer values.
3) in general, as the JitBuilder API evolves:
PATCH is increased when bug fixes change the API but in backwards compatible ways
MINOR is increased when new function changes the API but in backwards compatible ways
MAJOR is increased when the API changes but not in a backwards compatible way
4) any JitBuilder API change that affects the MAJOR number may need to be deferred depending on project plans and release schedule (you know, once we have those)
I propose to start the versioning at 1.0.0 since the JitBuilder API is actually quite functional at this point. I expect MAJOR version bumps won't be all that unusual for the next little while since the JitBuilder API is still "coming together".
An alternative, easier to implement and maintain, mechanism would be to simply call the SHA of the JitBuilder source code repository the "version" used to produce the JBIL. While this approach is certainly a lot easier to maintain and precisely correct, I believe it is unnecessarily fine grained since the JitBuilder API may remain completely unchanged across a wide range of SHAs. It will be very hard to use JBIL for anything but a completely matched pair of JitBuilder libraries which I believe will substantially reduce the number of scenarios where JBIL recording would be useful. For these reasons, I think the more painful maintenance story for semantic versioning is warranted.
Any naysayers? All feedback welcome.
@charliegracie @jduimovich @Leonardo2718 @mgaudet @0xdaryl @vijaysun-omr | 1.0 | PROPOSAL: Add semantic versioning to JitBuilder API - In preparation to record JitBuilder IL (JBIL) under Issue #1818, I would like to start versioning the JitBuilder API so that the version can be written out as part of a JBIL record. With an embedded semantic version (see [http://semver.org/](http://semver.org/)) , any particular JitBuilder library should be able to self certify whether it is qualified to replay the JBIL created from any other (valid :) ) source. Why now, given the JitBuilder API is still missing major features? Because I believe we should be building the versioning notion into our infrastructure now to avoid having to retrofit later. I also think that our existing JitBuilder consumers would benefit from a better notion of how refreshing their JitBuilder library is expected to affect their implementation.
Note that this versioning specifically concerns the API, not the implementation (though, of course, some implementation changes will also implact the API). I have purposefully excluded the implementation because clients should program against the API not the implementation.
Semantic versioning will require a higher standard of code review associated with changes to the JitBuilder API, in that it will only work if committers consistently respect that changes in the API must be properly reflected in updates to the semantic versioning. _**Pull requests should not be merged if they include commits that impact the JitBuilder API without including the appropriate update to the semantic version.**_ Commits will need to be updated to include the version update.
Specifically, the proposal is to:
1) create a base class for all the *Builder classes and for TypeDictionary called something like *BuilderAPI (name subject to feedback)
2) in one particular class, a set of const integers will be introduced that describe the MAJOR, MINOR, and PATCH levels for the JitBuilder API. For hopefully adequate future proofing, I propose MAJOR as a 32-bit unsigned integer value, and MINOR/PATCH as 16-bit unsigned integer values.
3) in general, as the JitBuilder API evolves:
PATCH is increased when bug fixes change the API but in backwards compatible ways
MINOR is increased when new function changes the API but in backwards compatible ways
MAJOR is increased when the API changes but not in a backwards compatible way
4) any JitBuilder API change that affects the MAJOR number may need to be deferred depending on project plans and release schedule (you know, once we have those)
I propose to start the versioning at 1.0.0 since the JitBuilder API is actually quite functional at this point. I expect MAJOR version bumps won't be all that unusual for the next little while since the JitBuilder API is still "coming together".
An alternative, easier to implement and maintain, mechanism would be to simply call the SHA of the JitBuilder source code repository the "version" used to produce the JBIL. While this approach is certainly a lot easier to maintain and precisely correct, I believe it is unnecessarily fine grained since the JitBuilder API may remain completely unchanged across a wide range of SHAs. It will be very hard to use JBIL for anything but a completely matched pair of JitBuilder libraries which I believe will substantially reduce the number of scenarios where JBIL recording would be useful. For these reasons, I think the more painful maintenance story for semantic versioning is warranted.
Any naysayers? All feedback welcome.
@charliegracie @jduimovich @Leonardo2718 @mgaudet @0xdaryl @vijaysun-omr | non_priority | proposal add semantic versioning to jitbuilder api in preparation to record jitbuilder il jbil under issue i would like to start versioning the jitbuilder api so that the version can be written out as part of a jbil record with an embedded semantic version see any particular jitbuilder library should be able to self certify whether it is qualified to replay the jbil created from any other valid source why now given the jitbuilder api is still missing major features because i believe we should be building the versioning notion into our infrastructure now to avoid having to retrofit later i also think that our existing jitbuilder consumers would benefit from a better notion of how refreshing their jitbuilder library is expected to affect their implementation note that this versioning specifically concerns the api not the implementation though of course some implementation changes will also implact the api i have purposefully excluded the implementation because clients should program against the api not the implementation semantic versioning will require a higher standard of code review associated with changes to the jitbuilder api in that it will only work if committers consistently respect that changes in the api must be properly reflected in updates to the semantic versioning pull requests should not be merged if they include commits that impact the jitbuilder api without including the appropriate update to the semantic version commits will need to be updated to include the version update specifically the proposal is to create a base class for all the builder classes and for typedictionary called something like builderapi name subject to feedback in one particular class a set of const integers will be introduced that describe the major minor and patch levels for the jitbuilder api for hopefully adequate future proofing i propose major as a bit unsigned integer value and minor patch as bit unsigned integer values in general as the jitbuilder api evolves patch is increased when bug fixes change the api but in backwards compatible ways minor is increased when new function changes the api but in backwards compatible ways major is increased when the api changes but not in a backwards compatible way any jitbuilder api change that affects the major number may need to be deferred depending on project plans and release schedule you know once we have those i propose to start the versioning at since the jitbuilder api is actually quite functional at this point i expect major version bumps won t be all that unusual for the next little while since the jitbuilder api is still coming together an alternative easier to implement and maintain mechanism would be to simply call the sha of the jitbuilder source code repository the version used to produce the jbil while this approach is certainly a lot easier to maintain and precisely correct i believe it is unnecessarily fine grained since the jitbuilder api may remain completely unchanged across a wide range of shas it will be very hard to use jbil for anything but a completely matched pair of jitbuilder libraries which i believe will substantially reduce the number of scenarios where jbil recording would be useful for these reasons i think the more painful maintenance story for semantic versioning is warranted any naysayers all feedback welcome charliegracie jduimovich mgaudet vijaysun omr | 0 |
166,131 | 14,020,365,616 | IssuesEvent | 2020-10-29 19:34:27 | shreyanshchordia/Graph_Algorithms | https://api.github.com/repos/shreyanshchordia/Graph_Algorithms | closed | HACKTOBER FEST | DSA | Graphs 🔥🔥 | bug digital ocean documentation enhancement good first issue hacktoberfest hacktoberfest-accepted hacktoberfest2020 | 1. **Star** the Repository
2. **Fork** it
3. **Contribute** your code
4. Issue a **PULL REQUEST**
Contribution of new code to this repository needs to be done in a specific manner otherwise your Pull Requests will be invalid. Kindly check README.md file to understand how exactly contribution can be done to the repository. | 1.0 | HACKTOBER FEST | DSA | Graphs 🔥🔥 - 1. **Star** the Repository
2. **Fork** it
3. **Contribute** your code
4. Issue a **PULL REQUEST**
Contribution of new code to this repository needs to be done in a specific manner otherwise your Pull Requests will be invalid. Kindly check README.md file to understand how exactly contribution can be done to the repository. | non_priority | hacktober fest dsa graphs 🔥🔥 star the repository fork it contribute your code issue a pull request contribution of new code to this repository needs to be done in a specific manner otherwise your pull requests will be invalid kindly check readme md file to understand how exactly contribution can be done to the repository | 0 |
75,394 | 15,397,649,338 | IssuesEvent | 2021-03-03 22:30:25 | OpenLiberty/open-liberty | https://api.github.com/repos/OpenLiberty/open-liberty | opened | authFilter element is missing from generated feature docs and has incorrect descriptions | bug in:Security | **Describe the bug**
The Open LIberty autogenerated docs for the `authFilter` element, which is generated from [this metatype.properties file](https://github.com/OpenLiberty/open-liberty/blob/integration/dev/com.ibm.ws.security.authentication.filter/resources/OSGI-INF/l10n/metatype.properties) (and other files in the [com.ibm.ws.security.authentication.filter directory](https://github.com/OpenLiberty/open-liberty/tree/integration/dev/com.ibm.ws.security.authentication.filter)), has two issues:
1. The autogen is not pulling in the attribute descriptions from [com.ibm.ws.security.authentication.filter/resources/OSGI-INF/l10n/metatype.properties](https://github.com/OpenLiberty/open-liberty/blob/integration/dev/com.ibm.ws.security.authentication.filter/resources/OSGI-INF/l10n/metatype.properties). Instead, it pulls in a single description for all the attributes, "A unique configuration ID.". See [the authFilter autogen page](https://www.openliberty.io/docs/21.0.0.2/reference/config/authFilter.html) for example.
2. The `authFilter` configuration element has disappeared from all generated feature doc pages which previously included the element in the "Feature configuration elements". This bug occurred sometime between the 20.0.0.11 and 20.0.0.12 Ga releases. For example, see the [20.0.0.11 version of the MpJWT feature page](https://www.openliberty.io/docs/20.0.0.11/reference/feature/mpJwt-1.1.html), which displays the element, and any later version of the feature page, [for example 21.0.0.2](https://www.openliberty.io/docs/21.0.0.2/reference/feature/mpJwt-1.1.html), which do not. This is the case for all liberty features that use `authFilter` .
This information is not maintained by the docs team and is pulled in automatically from properties files in the Open Liberty repo.
**Steps to Reproduce**
See doc links above
**Expected behavior**
1. The authFilter autogen page should pull in the appropriate attribute descriptions that are specified in [com.ibm.ws.security.authentication.filter/resources/OSGI-INF/l10n/metatype.properties](https://github.com/OpenLiberty/open-liberty/blob/integration/dev/com.ibm.ws.security.authentication.filter/resources/OSGI-INF/l10n/metatype.properties).
2. all version of feature pages for feaures that use authFilter should display the authFilter element in the "Feature configuration elements" list.
**Diagnostic information:**
- OpenLiberty DOCS VersionS 20.0.0.12 and later (currently through 21.0.0.2)
**Additional context**
https://github.com/OpenLiberty/open-liberty/pull/14099 may be relevant @jvanhill @utle
| True | authFilter element is missing from generated feature docs and has incorrect descriptions - **Describe the bug**
The Open LIberty autogenerated docs for the `authFilter` element, which is generated from [this metatype.properties file](https://github.com/OpenLiberty/open-liberty/blob/integration/dev/com.ibm.ws.security.authentication.filter/resources/OSGI-INF/l10n/metatype.properties) (and other files in the [com.ibm.ws.security.authentication.filter directory](https://github.com/OpenLiberty/open-liberty/tree/integration/dev/com.ibm.ws.security.authentication.filter)), has two issues:
1. The autogen is not pulling in the attribute descriptions from [com.ibm.ws.security.authentication.filter/resources/OSGI-INF/l10n/metatype.properties](https://github.com/OpenLiberty/open-liberty/blob/integration/dev/com.ibm.ws.security.authentication.filter/resources/OSGI-INF/l10n/metatype.properties). Instead, it pulls in a single description for all the attributes, "A unique configuration ID.". See [the authFilter autogen page](https://www.openliberty.io/docs/21.0.0.2/reference/config/authFilter.html) for example.
2. The `authFilter` configuration element has disappeared from all generated feature doc pages which previously included the element in the "Feature configuration elements". This bug occurred sometime between the 20.0.0.11 and 20.0.0.12 Ga releases. For example, see the [20.0.0.11 version of the MpJWT feature page](https://www.openliberty.io/docs/20.0.0.11/reference/feature/mpJwt-1.1.html), which displays the element, and any later version of the feature page, [for example 21.0.0.2](https://www.openliberty.io/docs/21.0.0.2/reference/feature/mpJwt-1.1.html), which do not. This is the case for all liberty features that use `authFilter` .
This information is not maintained by the docs team and is pulled in automatically from properties files in the Open Liberty repo.
**Steps to Reproduce**
See doc links above
**Expected behavior**
1. The authFilter autogen page should pull in the appropriate attribute descriptions that are specified in [com.ibm.ws.security.authentication.filter/resources/OSGI-INF/l10n/metatype.properties](https://github.com/OpenLiberty/open-liberty/blob/integration/dev/com.ibm.ws.security.authentication.filter/resources/OSGI-INF/l10n/metatype.properties).
2. all version of feature pages for feaures that use authFilter should display the authFilter element in the "Feature configuration elements" list.
**Diagnostic information:**
- OpenLiberty DOCS VersionS 20.0.0.12 and later (currently through 21.0.0.2)
**Additional context**
https://github.com/OpenLiberty/open-liberty/pull/14099 may be relevant @jvanhill @utle
| non_priority | authfilter element is missing from generated feature docs and has incorrect descriptions describe the bug the open liberty autogenerated docs for the authfilter element which is generated from and other files in the has two issues the autogen is not pulling in the attribute descriptions from instead it pulls in a single description for all the attributes a unique configuration id see for example the authfilter configuration element has disappeared from all generated feature doc pages which previously included the element in the feature configuration elements this bug occurred sometime between the and ga releases for example see the which displays the element and any later version of the feature page which do not this is the case for all liberty features that use authfilter this information is not maintained by the docs team and is pulled in automatically from properties files in the open liberty repo steps to reproduce see doc links above expected behavior the authfilter autogen page should pull in the appropriate attribute descriptions that are specified in all version of feature pages for feaures that use authfilter should display the authfilter element in the feature configuration elements list diagnostic information openliberty docs versions and later currently through additional context may be relevant jvanhill utle | 0 |
98,005 | 12,281,069,629 | IssuesEvent | 2020-05-08 15:12:06 | f8upd8/Product503 | https://api.github.com/repos/f8upd8/Product503 | closed | Иконки | design | Нужны все иконки с дизайна сайта в формате .svg или в формате проекта иллюстратора. На крайняк - в .png не меньше чем 2048x2048 с прозрачностью. Пока делаю без них. | 1.0 | Иконки - Нужны все иконки с дизайна сайта в формате .svg или в формате проекта иллюстратора. На крайняк - в .png не меньше чем 2048x2048 с прозрачностью. Пока делаю без них. | non_priority | иконки нужны все иконки с дизайна сайта в формате svg или в формате проекта иллюстратора на крайняк в png не меньше чем с прозрачностью пока делаю без них | 0 |
1,891 | 6,577,533,420 | IssuesEvent | 2017-09-12 01:34:41 | ansible/ansible-modules-core | https://api.github.com/repos/ansible/ansible-modules-core | closed | Docker pull: always and state: reloaded no longer ignores unnamed containers | affects_1.9 bug_report cloud docker waiting_on_maintainer | ##### Issue Type:
- Bug Report
##### Plugin Name:
Docker
##### Ansible Version:
**Worked:**
```
ansible 1.9.4
configured module search path = None
```
**Broken:**
```
ansible 2.0.0.1
config file = /Users/mmorris/Work/ansible/ansible.cfg
configured module search path = Default w/o overrides
```
##### Ansible Configuration:
```
[defaults]
host_key_checking=False
display_skipped_hosts=False
force_handlers = True
hostfile = inventory/ec2.py
retry_files_enabled = False
[ssh_connection]
pipelining=True
```
##### Environment:
Ubuntu 14.04 from OSX 10.10
##### Summary:
Something has changed in the docker module so that if you have `pull: always` and `state: reloaded` with a unnamed container, it will keep on creating new containers instead of realizing it's the same container, just differently named.
##### Steps To Reproduce:
``` yaml
- name: create redis container
docker:
image: "redis:3.0.3"
pull: always
state: reloaded
```
##### Expected Results:
When a container already exists and it has all the same settings except the dynamically assigned name is different, nothing should happen:
**First run:**
```
GATHERING FACTS ***************************************************************
ok: [x.x.x.x]
TASK: [docker | create redis container] *********************
changed: [x.x.x.x]
```
**Second run:**
```
GATHERING FACTS ***************************************************************
ok: [x.x.x.x]
TASK: [docker | create redis container] *********************
ok: [x.x.x.x]
```
```
$docker ps | grep redis | awk '{print $2 "," $12}'
redis:3.0.3,sad_tesla
```
##### Actual Results:
It will create a new, separate container every time:
**First run:**
```
GATHERING FACTS ***************************************************************
ok: [x.x.x.x]
TASK: [docker | create redis container] *********************
changed: [x.x.x.x]
```
**Second run:**
```
GATHERING FACTS ***************************************************************
ok: [x.x.x.x]
TASK: [docker | create redis container] *********************
changed: [x.x.x.x]
```
```
$ docker ps | grep redis | awk '{print $2 "," $12}'
redis:3.0.3,sad_tesla
redis:3.0.3,mad_kirch
```
Not sure why this change was made, but it is very much NOT what should be happening and will result in problems for what I know are many people who use the module like this.
| True | Docker pull: always and state: reloaded no longer ignores unnamed containers - ##### Issue Type:
- Bug Report
##### Plugin Name:
Docker
##### Ansible Version:
**Worked:**
```
ansible 1.9.4
configured module search path = None
```
**Broken:**
```
ansible 2.0.0.1
config file = /Users/mmorris/Work/ansible/ansible.cfg
configured module search path = Default w/o overrides
```
##### Ansible Configuration:
```
[defaults]
host_key_checking=False
display_skipped_hosts=False
force_handlers = True
hostfile = inventory/ec2.py
retry_files_enabled = False
[ssh_connection]
pipelining=True
```
##### Environment:
Ubuntu 14.04 from OSX 10.10
##### Summary:
Something has changed in the docker module so that if you have `pull: always` and `state: reloaded` with a unnamed container, it will keep on creating new containers instead of realizing it's the same container, just differently named.
##### Steps To Reproduce:
``` yaml
- name: create redis container
docker:
image: "redis:3.0.3"
pull: always
state: reloaded
```
##### Expected Results:
When a container already exists and it has all the same settings except the dynamically assigned name is different, nothing should happen:
**First run:**
```
GATHERING FACTS ***************************************************************
ok: [x.x.x.x]
TASK: [docker | create redis container] *********************
changed: [x.x.x.x]
```
**Second run:**
```
GATHERING FACTS ***************************************************************
ok: [x.x.x.x]
TASK: [docker | create redis container] *********************
ok: [x.x.x.x]
```
```
$docker ps | grep redis | awk '{print $2 "," $12}'
redis:3.0.3,sad_tesla
```
##### Actual Results:
It will create a new, separate container every time:
**First run:**
```
GATHERING FACTS ***************************************************************
ok: [x.x.x.x]
TASK: [docker | create redis container] *********************
changed: [x.x.x.x]
```
**Second run:**
```
GATHERING FACTS ***************************************************************
ok: [x.x.x.x]
TASK: [docker | create redis container] *********************
changed: [x.x.x.x]
```
```
$ docker ps | grep redis | awk '{print $2 "," $12}'
redis:3.0.3,sad_tesla
redis:3.0.3,mad_kirch
```
Not sure why this change was made, but it is very much NOT what should be happening and will result in problems for what I know are many people who use the module like this.
| non_priority | docker pull always and state reloaded no longer ignores unnamed containers issue type bug report plugin name docker ansible version worked ansible configured module search path none broken ansible config file users mmorris work ansible ansible cfg configured module search path default w o overrides ansible configuration host key checking false display skipped hosts false force handlers true hostfile inventory py retry files enabled false pipelining true environment ubuntu from osx summary something has changed in the docker module so that if you have pull always and state reloaded with a unnamed container it will keep on creating new containers instead of realizing it s the same container just differently named steps to reproduce yaml name create redis container docker image redis pull always state reloaded expected results when a container already exists and it has all the same settings except the dynamically assigned name is different nothing should happen first run gathering facts ok task changed second run gathering facts ok task ok docker ps grep redis awk print redis sad tesla actual results it will create a new separate container every time first run gathering facts ok task changed second run gathering facts ok task changed docker ps grep redis awk print redis sad tesla redis mad kirch not sure why this change was made but it is very much not what should be happening and will result in problems for what i know are many people who use the module like this | 0 |
67,479 | 12,964,623,687 | IssuesEvent | 2020-07-20 20:48:59 | vshaxe/vshaxe | https://api.github.com/repos/vshaxe/vshaxe | closed | Code Action to create non-existant methods | blocked-haxe code-actions code-generation enhancement | I'd like to have a code action like this in vshaxe as well:
https://twitter.com/mayakwd/status/1001825619557191680
This requires some info from the compiler, such as what the inferred argument types are and what our current context is (static vs instance). Probably has to wait until diagnostics have been transitioned over to JSON-RPC, but we should keep this use case in mind when designing the structure we use there. | 2.0 | Code Action to create non-existant methods - I'd like to have a code action like this in vshaxe as well:
https://twitter.com/mayakwd/status/1001825619557191680
This requires some info from the compiler, such as what the inferred argument types are and what our current context is (static vs instance). Probably has to wait until diagnostics have been transitioned over to JSON-RPC, but we should keep this use case in mind when designing the structure we use there. | non_priority | code action to create non existant methods i d like to have a code action like this in vshaxe as well this requires some info from the compiler such as what the inferred argument types are and what our current context is static vs instance probably has to wait until diagnostics have been transitioned over to json rpc but we should keep this use case in mind when designing the structure we use there | 0 |
257,781 | 19,531,566,972 | IssuesEvent | 2021-12-30 17:53:53 | woodpecker-ci/woodpecker | https://api.github.com/repos/woodpecker-ci/woodpecker | closed | create a matrix room for chat/support | documentation | currently when clicking on questions and support it redirects you to discord.
i created a temp account, but it required my phone number, for just creating an empty account.
i suggest creating a matrix room like codeberg with a bridge to discord.
so we users don't have to deal with discord bad privacy. | 1.0 | create a matrix room for chat/support - currently when clicking on questions and support it redirects you to discord.
i created a temp account, but it required my phone number, for just creating an empty account.
i suggest creating a matrix room like codeberg with a bridge to discord.
so we users don't have to deal with discord bad privacy. | non_priority | create a matrix room for chat support currently when clicking on questions and support it redirects you to discord i created a temp account but it required my phone number for just creating an empty account i suggest creating a matrix room like codeberg with a bridge to discord so we users don t have to deal with discord bad privacy | 0 |
7,055 | 10,348,139,414 | IssuesEvent | 2019-09-04 19:03:53 | openopps/openopps-platform | https://api.github.com/repos/openopps/openopps-platform | opened | Sitewide User: Add agency to manage users | Admin Requirements Ready | Who: Sitewide admin
What: Add Agency to manage users
Why: In order to facilitate user support
Acceptance Criteria:
Admin --> Sitewide --> Users --> Manage
- Add "Agency" after the Name field in manager users | 1.0 | Sitewide User: Add agency to manage users - Who: Sitewide admin
What: Add Agency to manage users
Why: In order to facilitate user support
Acceptance Criteria:
Admin --> Sitewide --> Users --> Manage
- Add "Agency" after the Name field in manager users | non_priority | sitewide user add agency to manage users who sitewide admin what add agency to manage users why in order to facilitate user support acceptance criteria admin sitewide users manage add agency after the name field in manager users | 0 |
130,743 | 18,170,276,599 | IssuesEvent | 2021-09-27 19:08:14 | snowdensb/job-dsl-plugin | https://api.github.com/repos/snowdensb/job-dsl-plugin | opened | CVE-2015-4852 (High) detected in commons-collections-3.2.jar | security vulnerability | ## CVE-2015-4852 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>commons-collections-3.2.jar</b></p></summary>
<p>Types that extend and augment the Java Collections Framework.</p>
<p>Library home page: <a href="http://jakarta.apache.org/commons/collections/">http://jakarta.apache.org/commons/collections/</a></p>
<p>Path to dependency file: job-dsl-plugin/job-dsl-plugin/build.gradle</p>
<p>Path to vulnerable library: /tmp/ws-ua_20210927190226_TRFFHW/downloadResource_SQXZWB/20210927190452/commons-collections-3.2.jar</p>
<p>
Dependency Hierarchy:
- vsphere-cloud-1.1.11.jar (Root Library)
- json-lib-2.1-rev7.jar
- :x: **commons-collections-3.2.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/snowdensb/job-dsl-plugin/commit/2e8946fc25b6060b5637631b8813fe86b6da687a">2e8946fc25b6060b5637631b8813fe86b6da687a</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 WLS Security component in Oracle WebLogic Server 10.3.6.0, 12.1.2.0, 12.1.3.0, and 12.2.1.0 allows remote attackers to execute arbitrary commands via a crafted serialized Java object in T3 protocol traffic to TCP port 7001, related to oracle_common/modules/com.bea.core.apache.commons.collections.jar. NOTE: the scope of this CVE is limited to the WebLogic Server product.
<p>Publish Date: 2015-11-18
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2015-4852>CVE-2015-4852</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 2 Score Details (<b>7.5</b>)</summary>
<p>
Base Score Metrics not available</p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://www.openwall.com/lists/oss-security/2015/11/17/19">https://www.openwall.com/lists/oss-security/2015/11/17/19</a></p>
<p>Release Date: 2015-11-18</p>
<p>Fix Resolution: commons-collections:commons-collections:3.2.2</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"Java","groupId":"commons-collections","packageName":"commons-collections","packageVersion":"3.2","packageFilePaths":["/job-dsl-plugin/build.gradle"],"isTransitiveDependency":true,"dependencyTree":"org.jenkins-ci.plugins:vsphere-cloud:1.1.11;org.kohsuke.stapler:json-lib:2.1-rev7;commons-collections:commons-collections:3.2","isMinimumFixVersionAvailable":true,"minimumFixVersion":"commons-collections:commons-collections:3.2.2"}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2015-4852","vulnerabilityDetails":"The WLS Security component in Oracle WebLogic Server 10.3.6.0, 12.1.2.0, 12.1.3.0, and 12.2.1.0 allows remote attackers to execute arbitrary commands via a crafted serialized Java object in T3 protocol traffic to TCP port 7001, related to oracle_common/modules/com.bea.core.apache.commons.collections.jar. NOTE: the scope of this CVE is limited to the WebLogic Server product.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2015-4852","cvss2Severity":"high","cvss2Score":"7.5","extraData":{}}</REMEDIATE> --> | True | CVE-2015-4852 (High) detected in commons-collections-3.2.jar - ## CVE-2015-4852 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>commons-collections-3.2.jar</b></p></summary>
<p>Types that extend and augment the Java Collections Framework.</p>
<p>Library home page: <a href="http://jakarta.apache.org/commons/collections/">http://jakarta.apache.org/commons/collections/</a></p>
<p>Path to dependency file: job-dsl-plugin/job-dsl-plugin/build.gradle</p>
<p>Path to vulnerable library: /tmp/ws-ua_20210927190226_TRFFHW/downloadResource_SQXZWB/20210927190452/commons-collections-3.2.jar</p>
<p>
Dependency Hierarchy:
- vsphere-cloud-1.1.11.jar (Root Library)
- json-lib-2.1-rev7.jar
- :x: **commons-collections-3.2.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/snowdensb/job-dsl-plugin/commit/2e8946fc25b6060b5637631b8813fe86b6da687a">2e8946fc25b6060b5637631b8813fe86b6da687a</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 WLS Security component in Oracle WebLogic Server 10.3.6.0, 12.1.2.0, 12.1.3.0, and 12.2.1.0 allows remote attackers to execute arbitrary commands via a crafted serialized Java object in T3 protocol traffic to TCP port 7001, related to oracle_common/modules/com.bea.core.apache.commons.collections.jar. NOTE: the scope of this CVE is limited to the WebLogic Server product.
<p>Publish Date: 2015-11-18
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2015-4852>CVE-2015-4852</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 2 Score Details (<b>7.5</b>)</summary>
<p>
Base Score Metrics not available</p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://www.openwall.com/lists/oss-security/2015/11/17/19">https://www.openwall.com/lists/oss-security/2015/11/17/19</a></p>
<p>Release Date: 2015-11-18</p>
<p>Fix Resolution: commons-collections:commons-collections:3.2.2</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"Java","groupId":"commons-collections","packageName":"commons-collections","packageVersion":"3.2","packageFilePaths":["/job-dsl-plugin/build.gradle"],"isTransitiveDependency":true,"dependencyTree":"org.jenkins-ci.plugins:vsphere-cloud:1.1.11;org.kohsuke.stapler:json-lib:2.1-rev7;commons-collections:commons-collections:3.2","isMinimumFixVersionAvailable":true,"minimumFixVersion":"commons-collections:commons-collections:3.2.2"}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2015-4852","vulnerabilityDetails":"The WLS Security component in Oracle WebLogic Server 10.3.6.0, 12.1.2.0, 12.1.3.0, and 12.2.1.0 allows remote attackers to execute arbitrary commands via a crafted serialized Java object in T3 protocol traffic to TCP port 7001, related to oracle_common/modules/com.bea.core.apache.commons.collections.jar. NOTE: the scope of this CVE is limited to the WebLogic Server product.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2015-4852","cvss2Severity":"high","cvss2Score":"7.5","extraData":{}}</REMEDIATE> --> | non_priority | cve high detected in commons collections jar cve high severity vulnerability vulnerable library commons collections jar types that extend and augment the java collections framework library home page a href path to dependency file job dsl plugin job dsl plugin build gradle path to vulnerable library tmp ws ua trffhw downloadresource sqxzwb commons collections jar dependency hierarchy vsphere cloud jar root library json lib jar x commons collections jar vulnerable library found in head commit a href found in base branch master vulnerability details the wls security component in oracle weblogic server and allows remote attackers to execute arbitrary commands via a crafted serialized java object in protocol traffic to tcp port related to oracle common modules com bea core apache commons collections jar note the scope of this cve is limited to the weblogic server product 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 commons collections commons collections isopenpronvulnerability true ispackagebased true isdefaultbranch true packages istransitivedependency true dependencytree org jenkins ci plugins vsphere cloud org kohsuke stapler json lib commons collections commons collections isminimumfixversionavailable true minimumfixversion commons collections commons collections basebranches vulnerabilityidentifier cve vulnerabilitydetails the wls security component in oracle weblogic server and allows remote attackers to execute arbitrary commands via a crafted serialized java object in protocol traffic to tcp port related to oracle common modules com bea core apache commons collections jar note the scope of this cve is limited to the weblogic server product vulnerabilityurl | 0 |
140,749 | 32,055,732,365 | IssuesEvent | 2023-09-24 03:46:21 | pulumi/pulumi | https://api.github.com/repos/pulumi/pulumi | opened | Improve user experience when running `pulumi policy publish` | kind/enhancement impact/usability area/policy-as-code needs-triage | ## Hello!
<!-- Please leave this section as-is, it's designed to help others in the community know how to interact with our GitHub issues. -->
- Vote on this issue by adding a 👍 reaction
- If you want to implement this feature, comment to let us know (we'll work with you on design, scheduling, etc.)
## Issue details
When running `pulumi policy publish` without an org name, the CLI defaults to the user's own account. This results in a failure since user accounts don't support policies.
It would be much better user experience to guide the user when possible. For example, if the user belongs to one or more pulumi orgs, then list all organization and highlight policies that have Policy-as-Code as a feature. With a selector (like in `pulumi stack select`) let the user pick the org of their choice.
Related to #14032
### Affected area/feature
* CLI
* Policy-as-Code | 1.0 | Improve user experience when running `pulumi policy publish` - ## Hello!
<!-- Please leave this section as-is, it's designed to help others in the community know how to interact with our GitHub issues. -->
- Vote on this issue by adding a 👍 reaction
- If you want to implement this feature, comment to let us know (we'll work with you on design, scheduling, etc.)
## Issue details
When running `pulumi policy publish` without an org name, the CLI defaults to the user's own account. This results in a failure since user accounts don't support policies.
It would be much better user experience to guide the user when possible. For example, if the user belongs to one or more pulumi orgs, then list all organization and highlight policies that have Policy-as-Code as a feature. With a selector (like in `pulumi stack select`) let the user pick the org of their choice.
Related to #14032
### Affected area/feature
* CLI
* Policy-as-Code | non_priority | improve user experience when running pulumi policy publish hello vote on this issue by adding a 👍 reaction if you want to implement this feature comment to let us know we ll work with you on design scheduling etc issue details when running pulumi policy publish without an org name the cli defaults to the user s own account this results in a failure since user accounts don t support policies it would be much better user experience to guide the user when possible for example if the user belongs to one or more pulumi orgs then list all organization and highlight policies that have policy as code as a feature with a selector like in pulumi stack select let the user pick the org of their choice related to affected area feature cli policy as code | 0 |
155,359 | 24,452,361,572 | IssuesEvent | 2022-10-07 01:10:54 | ubyssey/ubyssey.ca | https://api.github.com/repos/ubyssey/ubyssey.ca | closed | Design for /contribute | design feature | Design /contribute page to be more than just a block of text.
| 1.0 | Design for /contribute - Design /contribute page to be more than just a block of text.
| non_priority | design for contribute design contribute page to be more than just a block of text | 0 |
212,991 | 16,492,272,019 | IssuesEvent | 2021-05-25 06:15:57 | amazeeio/lagoon | https://api.github.com/repos/amazeeio/lagoon | closed | MariaDB image ship with functions not available in AWS RDS Aurora | 6-images-testing | **Describe the bug**
At the moment, Alpine Linux 3.11 ships with [MariaDB 10.4.13-r0](https://pkgs.alpinelinux.org/package/v3.11/main/x86/mariadb).
MariaDB introduced a new function `REGEXP_SUBSTR` in [10.0.5](https://mariadb.com/kb/en/regexp_substr/) (around 2013).
This function is available in MySQL 8.0. However is your Lagoon cluster is backed with AWS Aurora RDS, then you are currently capped to MySQL 5.7 and this function is not available.
If you use Azure Managed MySQL, then [MySQL 8.0 is available](https://docs.microsoft.com/en-us/azure/mysql/concepts-supported-versions).
**To Reproduce**
Steps to reproduce the behavior:
1. Write an SQL query that uses `REGEXP_SUBSTR`
2. Query will run locally using docker container
3. Query will fail on production using RDS Aurora
**Expected behavior**
There is consistency between local and production in terms of the version of MySQL available.
**Logs**
Seen in the application when running the query
```
REGEXP_SUBSTR does not exist
```
| 1.0 | MariaDB image ship with functions not available in AWS RDS Aurora - **Describe the bug**
At the moment, Alpine Linux 3.11 ships with [MariaDB 10.4.13-r0](https://pkgs.alpinelinux.org/package/v3.11/main/x86/mariadb).
MariaDB introduced a new function `REGEXP_SUBSTR` in [10.0.5](https://mariadb.com/kb/en/regexp_substr/) (around 2013).
This function is available in MySQL 8.0. However is your Lagoon cluster is backed with AWS Aurora RDS, then you are currently capped to MySQL 5.7 and this function is not available.
If you use Azure Managed MySQL, then [MySQL 8.0 is available](https://docs.microsoft.com/en-us/azure/mysql/concepts-supported-versions).
**To Reproduce**
Steps to reproduce the behavior:
1. Write an SQL query that uses `REGEXP_SUBSTR`
2. Query will run locally using docker container
3. Query will fail on production using RDS Aurora
**Expected behavior**
There is consistency between local and production in terms of the version of MySQL available.
**Logs**
Seen in the application when running the query
```
REGEXP_SUBSTR does not exist
```
| non_priority | mariadb image ship with functions not available in aws rds aurora describe the bug at the moment alpine linux ships with mariadb introduced a new function regexp substr in around this function is available in mysql however is your lagoon cluster is backed with aws aurora rds then you are currently capped to mysql and this function is not available if you use azure managed mysql then to reproduce steps to reproduce the behavior write an sql query that uses regexp substr query will run locally using docker container query will fail on production using rds aurora expected behavior there is consistency between local and production in terms of the version of mysql available logs seen in the application when running the query regexp substr does not exist | 0 |
225,586 | 24,873,823,663 | IssuesEvent | 2022-10-27 17:17:50 | hashicorp/nomad | https://api.github.com/repos/hashicorp/nomad | closed | Nomad Event Stream Subscriber Using ACL Token with TTL Receive Updates Until Garbage Collected | type/bug theme/security | Bulletin ID: HCSEC-2022-26
Bulletin Title: Nomad Event Stream Subscriber Using ACL Token with TTL Receive Updates Until Garbage Collected
Publication Date: October 27, 2022
Affected Products / Versions: Nomad and Nomad Enterprise 1.4.0 up to 1.4.1; fixed in 1.4.2.
Summary:
A vulnerability was identified in Nomad and Nomad Enterprise (“Nomad”) such that an event stream subscriber using an ACL token with an expiry TTL set would continue to receive events until the token was garbage collected. This vulnerability, with CVE assignment pending, was fixed in Nomad 1.4.2.
Background:
Nomad’s event stream provides a way to subscribe to Job, Allocation, Evaluation, Deployment, and Node changes in near real time. Whenever a state change occurs in Nomad's Finite State Machine (FSM) a set of events for each updated object are created.
Details:
During internal testing it was observed that an ACL token with an expiry TTL set would continue to receive events until the token was garbage collected. This behavior may be used by a malicious operator or third party with authenticated access to continue to receive events beyond the time limit their token should be allowed to.
Nomad’s ACL token TTL verification logic has been modified to authorize the subscriber’s ACL token before sending each event down the stream.
Remediation:
Customers should evaluate the risk associated with this issue and consider upgrading to Nomad 1.4.2, or newer.
See Nomad’s [Upgrading](https://www.nomadproject.io/docs/upgrade) for general guidance on this process.
Acknowledgement:
This issue was identified internally by the Nomad engineering team.
Additional content required for disclosure:
CVE Description:
HashiCorp Nomad and Nomad Enterprise 1.4.0 up to 1.4.1 event stream subscribers using a token with TTL receive updates until token garbage is collected. Fixed in 1.4.2.
CHANGELOG Entry:
n/a | True | Nomad Event Stream Subscriber Using ACL Token with TTL Receive Updates Until Garbage Collected - Bulletin ID: HCSEC-2022-26
Bulletin Title: Nomad Event Stream Subscriber Using ACL Token with TTL Receive Updates Until Garbage Collected
Publication Date: October 27, 2022
Affected Products / Versions: Nomad and Nomad Enterprise 1.4.0 up to 1.4.1; fixed in 1.4.2.
Summary:
A vulnerability was identified in Nomad and Nomad Enterprise (“Nomad”) such that an event stream subscriber using an ACL token with an expiry TTL set would continue to receive events until the token was garbage collected. This vulnerability, with CVE assignment pending, was fixed in Nomad 1.4.2.
Background:
Nomad’s event stream provides a way to subscribe to Job, Allocation, Evaluation, Deployment, and Node changes in near real time. Whenever a state change occurs in Nomad's Finite State Machine (FSM) a set of events for each updated object are created.
Details:
During internal testing it was observed that an ACL token with an expiry TTL set would continue to receive events until the token was garbage collected. This behavior may be used by a malicious operator or third party with authenticated access to continue to receive events beyond the time limit their token should be allowed to.
Nomad’s ACL token TTL verification logic has been modified to authorize the subscriber’s ACL token before sending each event down the stream.
Remediation:
Customers should evaluate the risk associated with this issue and consider upgrading to Nomad 1.4.2, or newer.
See Nomad’s [Upgrading](https://www.nomadproject.io/docs/upgrade) for general guidance on this process.
Acknowledgement:
This issue was identified internally by the Nomad engineering team.
Additional content required for disclosure:
CVE Description:
HashiCorp Nomad and Nomad Enterprise 1.4.0 up to 1.4.1 event stream subscribers using a token with TTL receive updates until token garbage is collected. Fixed in 1.4.2.
CHANGELOG Entry:
n/a | non_priority | nomad event stream subscriber using acl token with ttl receive updates until garbage collected bulletin id hcsec bulletin title nomad event stream subscriber using acl token with ttl receive updates until garbage collected publication date october affected products versions nomad and nomad enterprise up to fixed in summary a vulnerability was identified in nomad and nomad enterprise “nomad” such that an event stream subscriber using an acl token with an expiry ttl set would continue to receive events until the token was garbage collected this vulnerability with cve assignment pending was fixed in nomad background nomad’s event stream provides a way to subscribe to job allocation evaluation deployment and node changes in near real time whenever a state change occurs in nomad s finite state machine fsm a set of events for each updated object are created details during internal testing it was observed that an acl token with an expiry ttl set would continue to receive events until the token was garbage collected this behavior may be used by a malicious operator or third party with authenticated access to continue to receive events beyond the time limit their token should be allowed to nomad’s acl token ttl verification logic has been modified to authorize the subscriber’s acl token before sending each event down the stream remediation customers should evaluate the risk associated with this issue and consider upgrading to nomad or newer see nomad’s for general guidance on this process acknowledgement this issue was identified internally by the nomad engineering team additional content required for disclosure cve description hashicorp nomad and nomad enterprise up to event stream subscribers using a token with ttl receive updates until token garbage is collected fixed in changelog entry n a | 0 |
128,364 | 12,370,919,948 | IssuesEvent | 2020-05-18 17:38:21 | National-COVID-Cohort-Collaborative/Phenotype_Data_Acquisition | https://api.github.com/repos/National-COVID-Cohort-Collaborative/Phenotype_Data_Acquisition | closed | Add assumptions to OMOP documentation | documentation | Kristin noted a couple of assumptions for OMOP on the Colorado call: Updating vocab regularly and using ERA tables. Can you add these and any others to the OMOP documentation please? | 1.0 | Add assumptions to OMOP documentation - Kristin noted a couple of assumptions for OMOP on the Colorado call: Updating vocab regularly and using ERA tables. Can you add these and any others to the OMOP documentation please? | non_priority | add assumptions to omop documentation kristin noted a couple of assumptions for omop on the colorado call updating vocab regularly and using era tables can you add these and any others to the omop documentation please | 0 |
438,944 | 30,670,689,455 | IssuesEvent | 2023-07-25 22:10:43 | apache/openwhisk | https://api.github.com/repos/apache/openwhisk | closed | add documentation for typescript function runtime and update runtimes | help wanted documentation good first issue | The typescript runtime was recently added to openwhisk but we do not yet have docs for the runtime and it is missing from runtimes.json.
We need a doc like https://github.com/apache/incubator-openwhisk/blob/master/docs/actions-nodejs.md for typescript functions.
Adding the runtime to the runtime manifest can be done per https://github.com/apache/openwhisk/blob/master/docs/actions-new.md#the-runtimes-manifest. | 1.0 | add documentation for typescript function runtime and update runtimes - The typescript runtime was recently added to openwhisk but we do not yet have docs for the runtime and it is missing from runtimes.json.
We need a doc like https://github.com/apache/incubator-openwhisk/blob/master/docs/actions-nodejs.md for typescript functions.
Adding the runtime to the runtime manifest can be done per https://github.com/apache/openwhisk/blob/master/docs/actions-new.md#the-runtimes-manifest. | non_priority | add documentation for typescript function runtime and update runtimes the typescript runtime was recently added to openwhisk but we do not yet have docs for the runtime and it is missing from runtimes json we need a doc like for typescript functions adding the runtime to the runtime manifest can be done per | 0 |
7,002 | 3,073,062,927 | IssuesEvent | 2015-08-19 20:02:26 | NETponents/octoduino | https://api.github.com/repos/NETponents/octoduino | opened | Expose SPI library API over PB | c++ documentation enhancement hard help wanted octoduino_core parser | Could port over SD and LCD libraries over to PB since they both depend on SPI. | 1.0 | Expose SPI library API over PB - Could port over SD and LCD libraries over to PB since they both depend on SPI. | non_priority | expose spi library api over pb could port over sd and lcd libraries over to pb since they both depend on spi | 0 |
48,900 | 7,463,455,190 | IssuesEvent | 2018-04-01 05:34:55 | ThomGeG/Tom-Talk | https://api.github.com/repos/ThomGeG/Tom-Talk | opened | No README.md | documentation enhancement | The project lacks even a basic README. The sooner one is produced the better.
### Fundamental Sections:
- Title & Description
- Installation/Deployment guide
- Relevant additional resources | 1.0 | No README.md - The project lacks even a basic README. The sooner one is produced the better.
### Fundamental Sections:
- Title & Description
- Installation/Deployment guide
- Relevant additional resources | non_priority | no readme md the project lacks even a basic readme the sooner one is produced the better fundamental sections title description installation deployment guide relevant additional resources | 0 |
129,454 | 27,496,579,454 | IssuesEvent | 2023-03-05 07:44:36 | joomla/joomla-cms | https://api.github.com/repos/joomla/joomla-cms | closed | Non-SEF urls still remains in Article's Link A parameter | No Code Attached Yet bug | Go to edit article mode > Images and Links
Add non-SEF url in Link A parameter:
<img width="1637" alt="Снимок экрана 2023-02-21 в 22 41 46" src="https://user-images.githubusercontent.com/3432048/220442849-5e19573d-585d-41ab-afea-22be02458221.png">
`/index.php?option=com_content&view=article&id=1&catid=2`
And this non-SEF url still remains on the front-end.
I expect to get SEF URL since SEF mode is enabled.
And I use non-SEF URL to avoid 404 error if article's alias will be changed.
Joomla 4.2.8 | 1.0 | Non-SEF urls still remains in Article's Link A parameter - Go to edit article mode > Images and Links
Add non-SEF url in Link A parameter:
<img width="1637" alt="Снимок экрана 2023-02-21 в 22 41 46" src="https://user-images.githubusercontent.com/3432048/220442849-5e19573d-585d-41ab-afea-22be02458221.png">
`/index.php?option=com_content&view=article&id=1&catid=2`
And this non-SEF url still remains on the front-end.
I expect to get SEF URL since SEF mode is enabled.
And I use non-SEF URL to avoid 404 error if article's alias will be changed.
Joomla 4.2.8 | non_priority | non sef urls still remains in article s link a parameter go to edit article mode images and links add non sef url in link a parameter img width alt снимок экрана в src index php option com content amp view article amp id amp catid and this non sef url still remains on the front end i expect to get sef url since sef mode is enabled and i use non sef url to avoid error if article s alias will be changed joomla | 0 |
339,230 | 30,352,941,792 | IssuesEvent | 2023-07-11 20:31:27 | kopia/kopia | https://api.github.com/repos/kopia/kopia | closed | Test Log File Max Total Size failure: corner case for log size | help wanted good first issue test-failure keep-open | ```
logfile_test.go:193:
Error Trace: D:/a/kopia/kopia/internal/logfile/logfile_test.go:193
Error: "19600" is not less than "19600"
Test: TestLogFileMaxTotalSize/content-logs
=== FAIL: internal/logfile TestLogFileMaxTotalSize (31.97s)
``` | 1.0 | Test Log File Max Total Size failure: corner case for log size - ```
logfile_test.go:193:
Error Trace: D:/a/kopia/kopia/internal/logfile/logfile_test.go:193
Error: "19600" is not less than "19600"
Test: TestLogFileMaxTotalSize/content-logs
=== FAIL: internal/logfile TestLogFileMaxTotalSize (31.97s)
``` | non_priority | test log file max total size failure corner case for log size logfile test go error trace d a kopia kopia internal logfile logfile test go error is not less than test testlogfilemaxtotalsize content logs fail internal logfile testlogfilemaxtotalsize | 0 |
165,399 | 14,000,901,286 | IssuesEvent | 2020-10-28 12:58:58 | futurewei-cloud/zeta | https://api.github.com/repos/futurewei-cloud/zeta | opened | Zeta Target Deployment | documentation enhancement | **User Story**
As a developer, I want a consistent deployment mechanism so that I can easily test/deploy Zeta services on AWS cloud, Lab Servers and localhost
**Is your feature request related to a problem? Please describe.**
I'm always frustrated when test or integrate Zeta on different environments, the setting up, orchestration requires a lot of care and repeated work.
**Describe the solution you'd like**
I want to use Ansible playbook to manage target inventories and credentials, switch context automatically based on deployment environment and fully automate the deployment and orchestration procedure for me
**Describe alternatives you've considered**
Manual and script based procedure are hard to maintain and less flexible
**Additional context**
None | 1.0 | Zeta Target Deployment - **User Story**
As a developer, I want a consistent deployment mechanism so that I can easily test/deploy Zeta services on AWS cloud, Lab Servers and localhost
**Is your feature request related to a problem? Please describe.**
I'm always frustrated when test or integrate Zeta on different environments, the setting up, orchestration requires a lot of care and repeated work.
**Describe the solution you'd like**
I want to use Ansible playbook to manage target inventories and credentials, switch context automatically based on deployment environment and fully automate the deployment and orchestration procedure for me
**Describe alternatives you've considered**
Manual and script based procedure are hard to maintain and less flexible
**Additional context**
None | non_priority | zeta target deployment user story as a developer i want a consistent deployment mechanism so that i can easily test deploy zeta services on aws cloud lab servers and localhost is your feature request related to a problem please describe i m always frustrated when test or integrate zeta on different environments the setting up orchestration requires a lot of care and repeated work describe the solution you d like i want to use ansible playbook to manage target inventories and credentials switch context automatically based on deployment environment and fully automate the deployment and orchestration procedure for me describe alternatives you ve considered manual and script based procedure are hard to maintain and less flexible additional context none | 0 |
266,795 | 20,164,808,362 | IssuesEvent | 2022-02-10 02:25:41 | opengeospatial/ogc-geosparql | https://api.github.com/repos/opengeospatial/ogc-geosparql | closed | GeoSPARQL and Common Query language CQL | documentation | The common query language (CQL) (http://docs.opengeospatial.org/DRAFTS/19-079.html#simple-cql_filter-expression) is used in many geospatial web services (WFS) and in the currently in OGC API features to filter geospatial featurecollections.
In one of our research projects we developed a "semanticwfs" (https://github.com/i3mainz/semanticwfs), i.e. a WFS/OGC API Features compatible webservice with triple store backends which has to convert CQL filter expressions to (Geo)SPARQL internally.
Test Instance here: https://www.i3mainz.de/projekte/bkg/semanticwfs/
For this usecase (using a GeoSPARQL compliant triple store as a backend of an OGC API Features compatible web service) mappings from CQL to GeoSPARQL have to be defined.
If this is a usecase which is interesting to follow up we could define the new GeoSPARQL version keeping CQL compatibility in mind, as OGC API Features and WFS are still the main form of accessing geospatial data for the GIS community.
I am just putting this out there for discussion as I am not sure if it is something we should consider or if this is the right place. | 1.0 | GeoSPARQL and Common Query language CQL - The common query language (CQL) (http://docs.opengeospatial.org/DRAFTS/19-079.html#simple-cql_filter-expression) is used in many geospatial web services (WFS) and in the currently in OGC API features to filter geospatial featurecollections.
In one of our research projects we developed a "semanticwfs" (https://github.com/i3mainz/semanticwfs), i.e. a WFS/OGC API Features compatible webservice with triple store backends which has to convert CQL filter expressions to (Geo)SPARQL internally.
Test Instance here: https://www.i3mainz.de/projekte/bkg/semanticwfs/
For this usecase (using a GeoSPARQL compliant triple store as a backend of an OGC API Features compatible web service) mappings from CQL to GeoSPARQL have to be defined.
If this is a usecase which is interesting to follow up we could define the new GeoSPARQL version keeping CQL compatibility in mind, as OGC API Features and WFS are still the main form of accessing geospatial data for the GIS community.
I am just putting this out there for discussion as I am not sure if it is something we should consider or if this is the right place. | non_priority | geosparql and common query language cql the common query language cql is used in many geospatial web services wfs and in the currently in ogc api features to filter geospatial featurecollections in one of our research projects we developed a semanticwfs i e a wfs ogc api features compatible webservice with triple store backends which has to convert cql filter expressions to geo sparql internally test instance here for this usecase using a geosparql compliant triple store as a backend of an ogc api features compatible web service mappings from cql to geosparql have to be defined if this is a usecase which is interesting to follow up we could define the new geosparql version keeping cql compatibility in mind as ogc api features and wfs are still the main form of accessing geospatial data for the gis community i am just putting this out there for discussion as i am not sure if it is something we should consider or if this is the right place | 0 |
37,771 | 15,370,716,098 | IssuesEvent | 2021-03-02 09:09:08 | GovernIB/portafib | https://api.github.com/repos/GovernIB/portafib | closed | Evitar ús de thread locals amb classes pròpies de l'aplicació o netejar-los | Estimació: S Lloc:WebServices | Quan es crea un `ThreadLocal` amb una classe pròpia de l'aplicació, i per tant que s'ha carregat amb el classloader quan aquesta s'ha iniciat, i no es neteja aquesta referència, el thread manté una referència a una classe carregada amb el classloader de l'aplicació. Quan es fa `undeploy` de l'aplicació, aquesta referència no permet fer el GC del classloader.
En aquest cas sembla que passi amb els ThreadLocal de UsuariAplicacioJPA. | 1.0 | Evitar ús de thread locals amb classes pròpies de l'aplicació o netejar-los - Quan es crea un `ThreadLocal` amb una classe pròpia de l'aplicació, i per tant que s'ha carregat amb el classloader quan aquesta s'ha iniciat, i no es neteja aquesta referència, el thread manté una referència a una classe carregada amb el classloader de l'aplicació. Quan es fa `undeploy` de l'aplicació, aquesta referència no permet fer el GC del classloader.
En aquest cas sembla que passi amb els ThreadLocal de UsuariAplicacioJPA. | non_priority | evitar ús de thread locals amb classes pròpies de l aplicació o netejar los quan es crea un threadlocal amb una classe pròpia de l aplicació i per tant que s ha carregat amb el classloader quan aquesta s ha iniciat i no es neteja aquesta referència el thread manté una referència a una classe carregada amb el classloader de l aplicació quan es fa undeploy de l aplicació aquesta referència no permet fer el gc del classloader en aquest cas sembla que passi amb els threadlocal de usuariaplicaciojpa | 0 |
261,618 | 22,758,058,231 | IssuesEvent | 2022-07-07 18:23:02 | dotnet/runtime | https://api.github.com/repos/dotnet/runtime | opened | System.Net.Requests.Tests failure in checked coreclr Linux x64 Release | area-System.Net test-failure | Hit in this unrelated infra change: https://github.com/dotnet/runtime/pull/71770/checks?check_run_id=7238923095
The [log](https://helixre107v0xdeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-pull-71770-merge-8e7d0a4ddc254d5489/System.Net.Requests.Tests/1/console.dd07ba3f.log?helixlogtype=result) says:
```
exit code 139 means SIGSEGV Illegal memory access. Deref invalid pointer, overrunning buffer, stack overflow etc. Core dumped.
...
[ 9106.854023] .NET ThreadPool[29402]: segfault at 7 ip 00007fc0f0112c5d sp 00007f7f97ffc210 error 4 in libcoreclr.so[7fc0effea000+6ea000]
[ 9106.854032] Code: ff 48 8d 15 da 6e db ff be 79 0f 00 00 e8 ab 68 35 00 41 8b 87 d8 0c 00 00 83 c0 01 41 89 87 d8 0c 00 00 48 8b 85 68 ff ff ff <48> 8b 38 48 83 e7 f8 74 09 e8 35 a1 ff ff 85 c0 75 34 48 8d 3d 96
``` | 1.0 | System.Net.Requests.Tests failure in checked coreclr Linux x64 Release - Hit in this unrelated infra change: https://github.com/dotnet/runtime/pull/71770/checks?check_run_id=7238923095
The [log](https://helixre107v0xdeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-pull-71770-merge-8e7d0a4ddc254d5489/System.Net.Requests.Tests/1/console.dd07ba3f.log?helixlogtype=result) says:
```
exit code 139 means SIGSEGV Illegal memory access. Deref invalid pointer, overrunning buffer, stack overflow etc. Core dumped.
...
[ 9106.854023] .NET ThreadPool[29402]: segfault at 7 ip 00007fc0f0112c5d sp 00007f7f97ffc210 error 4 in libcoreclr.so[7fc0effea000+6ea000]
[ 9106.854032] Code: ff 48 8d 15 da 6e db ff be 79 0f 00 00 e8 ab 68 35 00 41 8b 87 d8 0c 00 00 83 c0 01 41 89 87 d8 0c 00 00 48 8b 85 68 ff ff ff <48> 8b 38 48 83 e7 f8 74 09 e8 35 a1 ff ff 85 c0 75 34 48 8d 3d 96
``` | non_priority | system net requests tests failure in checked coreclr linux release hit in this unrelated infra change the says exit code means sigsegv illegal memory access deref invalid pointer overrunning buffer stack overflow etc core dumped net threadpool segfault at ip sp error in libcoreclr so code ff da db ff be ab ff ff ff ff ff | 0 |
30,036 | 4,545,645,794 | IssuesEvent | 2016-09-11 11:03:01 | cockroachdb/cockroach | https://api.github.com/repos/cockroachdb/cockroach | closed | stress: failed test in cockroach/storage/storage.test: TestAcceptsUnsplitRanges | Robot test-failure | Binary: cockroach/static-tests.tar.gz sha: https://github.com/cockroachdb/cockroach/commits/860d5044234abcda41ca45990e3f0f2cebabf454
Stress build found a failed test:
```
=== RUN TestAcceptsUnsplitRanges
I160911 04:32:11.934913 1090 gossip/gossip.go:230 initial resolvers: []
W160911 04:32:11.934938 1090 gossip/gossip.go:1041 no resolvers found; use --join to specify a connected node
I160911 04:32:11.934984 1090 gossip/gossip.go:264 NodeID set to 1
I160911 04:32:11.935052 1090 storage/engine/rocksdb.go:356 opening in memory rocksdb instance
I160911 04:32:11.936300 1090 gossip/gossip.go:264 NodeID set to 1
I160911 04:32:11.936421 1090 gossip/gossip.go:264 NodeID set to 1
I160911 04:32:11.938711 1097 storage/replica_trigger.go:308 new range lease replica {1 1 1} 1970-01-01 00:00:00 +0000 UTC 900ms following replica {0 0 0} 1970-01-01 00:00:00 +0000 UTC 0s [physicalTime=1970-01-01 00:00:00 +0000 UTC]
panic: runtime error: invalid memory address or nil pointer dereference [recovered]
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0xaa713c]
goroutine 404 [running]:
panic(0x16512e0, 0xc4200100e0)
/usr/local/go/src/runtime/panic.go:500 +0x1a1
github.com/cockroachdb/cockroach/util/stop.(*Stopper).Recover(0xc4201ce000)
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:176 +0x6e
panic(0x16512e0, 0xc4200100e0)
/usr/local/go/src/runtime/panic.go:458 +0x243
github.com/coreos/etcd/raft.(*raft).appendEntry(0xc42057c0f0, 0xc42056e320, 0x1, 0x1)
/go/src/github.com/coreos/etcd/raft/raft.go:465 +0xdc
github.com/coreos/etcd/raft.(*raft).becomeLeader(0xc42057c0f0)
/go/src/github.com/coreos/etcd/raft/raft.go:551 +0x1d1
github.com/coreos/etcd/raft.(*raft).campaign(0xc42057c0f0, 0x17a1faf, 0x10)
/go/src/github.com/coreos/etcd/raft/raft.go:558 +0x709
github.com/coreos/etcd/raft.(*raft).Step(0xc42057c0f0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, ...)
/go/src/github.com/coreos/etcd/raft/raft.go:606 +0x243
github.com/coreos/etcd/raft.(*RawNode).Campaign(0xc420562580, 0x0, 0x0)
/go/src/github.com/coreos/etcd/raft/rawnode.go:127 +0x71
github.com/cockroachdb/cockroach/storage.(*Replica).withRaftGroupLocked(0xc420158fc0, 0xc420571ae0, 0x0, 0x0)
/go/src/github.com/cockroachdb/cockroach/storage/replica.go:416 +0x2a2
github.com/cockroachdb/cockroach/storage.defaultProposeRaftCommandLocked(0xc420158fc0, 0xc420526480, 0x0, 0x0)
/go/src/github.com/cockroachdb/cockroach/storage/replica.go:1637 +0x223
github.com/cockroachdb/cockroach/storage.(*Replica).proposePendingCmdLocked(0xc420158fc0, 0xc420526480, 0xc420010540, 0xc42056c220)
/go/src/github.com/cockroachdb/cockroach/storage/replica.go:1586 +0x77
github.com/cockroachdb/cockroach/storage.(*Replica).proposeRaftCommand(0xc420158fc0, 0x7f6af88d7208, 0xc420010540, 0x0, 0x16, 0x0, 0x0, 0x3, 0x0, 0x0, ...)
/go/src/github.com/cockroachdb/cockroach/storage/replica.go:1565 +0x1f3
github.com/cockroachdb/cockroach/storage.(*pendingLeaseRequest).InitOrJoinRequest.func1()
/go/src/github.com/cockroachdb/cockroach/storage/replica_range_lease.go:133 +0x1a9
github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunAsyncTask.func1(0xc4201ce000, 0x1e52381, 0x1e, 0xa8, 0xc420154270)
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:231 +0x95
created by github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunAsyncTask
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:232 +0xbc
goroutine 1 [chan receive]:
testing.(*T).Run(0xc42009e240, 0x17aac7e, 0x18, 0x1915e00, 0xc420239a01)
/usr/local/go/src/testing/testing.go:647 +0x316
testing.RunTests.func1(0xc42009e240)
/usr/local/go/src/testing/testing.go:793 +0x6d
testing.tRunner(0xc42009e240, 0xc4200fbbc0)
/usr/local/go/src/testing/testing.go:610 +0x81
testing.RunTests(0x1917cc0, 0x2162f60, 0x143, 0x143, 0xc4202421d0)
/usr/local/go/src/testing/testing.go:799 +0x2f5
testing.(*M).Run(0xc4200fbee8, 0xc420239d30)
/usr/local/go/src/testing/testing.go:743 +0x85
github.com/cockroachdb/cockroach/storage_test.TestMain(0xc4200fbee8)
/go/src/github.com/cockroachdb/cockroach/storage/main_test.go:57 +0x1ff
main.main()
github.com/cockroachdb/cockroach/storage/_test/_testmain.go:708 +0xc6
goroutine 17 [syscall, locked to thread]:
runtime.goexit()
/usr/local/go/src/runtime/asm_amd64.s:2086 +0x1
goroutine 8 [chan receive]:
github.com/cockroachdb/cockroach/util/log.(*loggingT).flushDaemon(0x24aab20)
/go/src/github.com/cockroachdb/cockroach/util/log/clog.go:1032 +0x77
created by github.com/cockroachdb/cockroach/util/log.init.1
/go/src/github.com/cockroachdb/cockroach/util/log/clog.go:613 +0x95
goroutine 1090 [runnable]:
sync.runtime_Semacquire(0xc4200984fc)
/usr/local/go/src/runtime/sema.go:47 +0x30
sync.(*Mutex).Lock(0xc4200984f8)
/usr/local/go/src/sync/mutex.go:85 +0xd0
sync.(*Pool).getSlow(0x214f2c0, 0xc420098370, 0x0)
/usr/local/go/src/sync/pool.go:133 +0xcc
sync.(*Pool).Get(0x214f2c0, 0x0, 0xc420202110)
/usr/local/go/src/sync/pool.go:121 +0xf1
fmt.newPrinter(0x601d45)
/usr/local/go/src/fmt/print.go:133 +0x31
fmt.Fprintf(0x2167280, 0xc420148310, 0x1795554, 0x4, 0xc420508af8, 0x2, 0x2, 0x2, 0x0, 0x0)
/usr/local/go/src/fmt/print.go:180 +0x26
github.com/cockroachdb/cockroach/util/encoding.PrettyPrintValue(0xc4202dc1f8, 0x1, 0x8, 0x1794d06, 0x1, 0x0, 0x1)
/go/src/github.com/cockroachdb/cockroach/util/encoding/encoding.go:962 +0x3cf
github.com/cockroachdb/cockroach/keys.decodeKeyPrint(0xc4202dc1f8, 0x1, 0x8, 0x0, 0x0)
/go/src/github.com/cockroachdb/cockroach/keys/printer.go:417 +0x54
github.com/cockroachdb/cockroach/keys.prettyPrintInternal(0xc4202dc1f8, 0x1, 0x8, 0x2165403, 0x1, 0x1)
/go/src/github.com/cockroachdb/cockroach/keys/printer.go:442 +0x6f2
github.com/cockroachdb/cockroach/keys.PrettyPrint(0xc4202dc1f8, 0x1, 0x8, 0x5fd39f, 0x24b44c0)
/go/src/github.com/cockroachdb/cockroach/keys/printer.go:507 +0x26c
github.com/cockroachdb/cockroach/roachpb.Key.String(0xc4202dc1f8, 0x1, 0x8, 0xc420508fd8, 0x8a1ffe)
/go/src/github.com/cockroachdb/cockroach/roachpb/data.go:179 +0x52
github.com/cockroachdb/cockroach/roachpb.RKey.String(0xc4202dc1f8, 0x1, 0x8, 0x8a1ffe, 0xc420509018)
/go/src/github.com/cockroachdb/cockroach/roachpb/data.go:103 +0x3f
github.com/cockroachdb/cockroach/roachpb.(*RKey).String(0xc420598900, 0x1914958, 0xc42009e600)
<autogenerated>:95 +0x64
fmt.(*pp).handleMethods(0xc42009e600, 0x73, 0xc420202101)
/usr/local/go/src/fmt/print.go:590 +0x2f6
fmt.(*pp).printArg(0xc42009e600, 0x16ca2a0, 0xc420598900, 0xc400000073)
/usr/local/go/src/fmt/print.go:665 +0x17b
fmt.(*pp).doPrintf(0xc42009e600, 0x179b214, 0x9, 0xc420509350, 0x3, 0x3)
/usr/local/go/src/fmt/print.go:985 +0x123d
fmt.Sprintf(0x179b214, 0x9, 0xc420509350, 0x3, 0x3, 0x7f6af8843b78, 0x0)
/usr/local/go/src/fmt/print.go:196 +0x6a
github.com/cockroachdb/cockroach/storage.(*atomicRangeDesc).String(0xc420159020, 0x1914958, 0xc42009e180)
/go/src/github.com/cockroachdb/cockroach/storage/replica.go:197 +0x181
fmt.(*pp).handleMethods(0xc42009e180, 0x73, 0xc420202101)
/usr/local/go/src/fmt/print.go:590 +0x2f6
fmt.(*pp).printArg(0xc42009e180, 0x1670d60, 0xc420159020, 0xc400000073)
/usr/local/go/src/fmt/print.go:665 +0x17b
fmt.(*pp).doPrintf(0xc42009e180, 0x179f98f, 0xd, 0xc420509708, 0x3, 0x3)
/usr/local/go/src/fmt/print.go:985 +0x123d
fmt.Sprintf(0x179f98f, 0xd, 0xc420509708, 0x3, 0x3, 0xc420509748, 0xc420509758)
/usr/local/go/src/fmt/print.go:196 +0x6a
github.com/cockroachdb/cockroach/storage.(*Replica).String(0xc420158fc0, 0x1914958, 0xc4200a8000)
/go/src/github.com/cockroachdb/cockroach/storage/replica.go:546 +0x113
fmt.(*pp).handleMethods(0xc4200a8000, 0x73, 0x1721401)
/usr/local/go/src/fmt/print.go:590 +0x2f6
fmt.(*pp).printArg(0xc4200a8000, 0x17943c0, 0xc420158fc0, 0x73)
/usr/local/go/src/fmt/print.go:665 +0x17b
fmt.(*pp).doPrintf(0xc4200a8000, 0x17afc8a, 0x1c, 0xc420509bd0, 0x1, 0x1)
/usr/local/go/src/fmt/print.go:985 +0x123d
fmt.Fprintf(0x2167280, 0xc420148230, 0x17afc8a, 0x1c, 0xc420509bd0, 0x1, 0x1, 0xc420509ad0, 0x8941e9, 0xc4201936c0)
/usr/local/go/src/fmt/print.go:181 +0x76
github.com/cockroachdb/cockroach/util/log.eventInternal(0x7f6af88dea68, 0xc4201b2f60, 0xc4202d0100, 0x17afc8a, 0x1c, 0xc420509bd0, 0x1, 0x1)
/go/src/github.com/cockroachdb/cockroach/util/log/trace.go:112 +0x401
github.com/cockroachdb/cockroach/util/log.VEventf(0xc400000001, 0x7f6af88dea68, 0xc4201b2f60, 0x17afc8a, 0x1c, 0xc420509bd0, 0x1, 0x1)
/go/src/github.com/cockroachdb/cockroach/util/log/trace.go:189 +0x107
github.com/cockroachdb/cockroach/storage.(*baseQueue).MaybeAdd(0xc4200c11e0, 0xc420158fc0, 0x0, 0xc400000000)
/go/src/github.com/cockroachdb/cockroach/storage/queue.go:298 +0x1cb
github.com/cockroachdb/cockroach/storage.TestAcceptsUnsplitRanges(0xc4204ec180)
/go/src/github.com/cockroachdb/cockroach/storage/queue_test.go:455 +0x909
testing.tRunner(0xc4204ec180, 0x1915e00)
/usr/local/go/src/testing/testing.go:610 +0x81
created by testing.(*T).Run
/usr/local/go/src/testing/testing.go:646 +0x2ec
goroutine 1096 [select]:
github.com/cockroachdb/cockroach/storage.(*raftScheduler).worker(0xc4201daf50, 0xc4201ce000)
/go/src/github.com/cockroachdb/cockroach/storage/scheduler.go:168 +0x3e7
github.com/cockroachdb/cockroach/storage.(*raftScheduler).Start.func1()
/go/src/github.com/cockroachdb/cockroach/storage/scheduler.go:160 +0x33
github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker.func1(0xc4201ce000, 0xc4202c37e0)
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:187 +0x7d
created by github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:188 +0x66
goroutine 1095 [select]:
github.com/cockroachdb/cockroach/storage.(*bookie).start.func1()
/go/src/github.com/cockroachdb/cockroach/storage/reservation.go:274 +0x217
github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker.func1(0xc4201ce000, 0xc4202c3320)
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:187 +0x7d
created by github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:188 +0x66
goroutine 1091 [chan receive]:
github.com/cockroachdb/cockroach/rpc.NewContext.func1()
/go/src/github.com/cockroachdb/cockroach/rpc/context.go:134 +0x76
github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker.func1(0xc4201ce000, 0xc4202c21c0)
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:187 +0x7d
created by github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:188 +0x66
goroutine 1093 [chan receive]:
github.com/cockroachdb/cockroach/storage/engine.(*RocksDB).Open.func1(0xc420014de0)
/go/src/github.com/cockroachdb/cockroach/storage/engine/rocksdb.go:390 +0x44
created by github.com/cockroachdb/cockroach/storage/engine.(*RocksDB).Open
/go/src/github.com/cockroachdb/cockroach/storage/engine/rocksdb.go:391 +0x6eb
goroutine 1092 [select]:
github.com/cockroachdb/cockroach/storage.(*StorePool).start.func1()
/go/src/github.com/cockroachdb/cockroach/storage/store_pool.go:340 +0x3da
github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker.func1(0xc4201ce000, 0xc4202c2b20)
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:187 +0x7d
created by github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:188 +0x66
goroutine 1097 [select]:
github.com/cockroachdb/cockroach/storage.(*raftScheduler).worker(0xc4201daf50, 0xc4201ce000)
/go/src/github.com/cockroachdb/cockroach/storage/scheduler.go:168 +0x3e7
github.com/cockroachdb/cockroach/storage.(*raftScheduler).Start.func1()
/go/src/github.com/cockroachdb/cockroach/storage/scheduler.go:160 +0x33
github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker.func1(0xc4201ce000, 0xc4202c3800)
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:187 +0x7d
created by github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:188 +0x66
goroutine 1099 [select]:
github.com/cockroachdb/cockroach/storage.(*raftScheduler).worker(0xc4201daf50, 0xc4201ce000)
/go/src/github.com/cockroachdb/cockroach/storage/scheduler.go:168 +0x3e7
github.com/cockroachdb/cockroach/storage.(*raftScheduler).Start.func1()
/go/src/github.com/cockroachdb/cockroach/storage/scheduler.go:160 +0x33
github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker.func1(0xc4201ce000, 0xc4202c3840)
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:187 +0x7d
created by github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:188 +0x66
goroutine 1119 [select]:
github.com/cockroachdb/cockroach/storage.(*raftScheduler).worker(0xc4201daf50, 0xc4201ce000)
/go/src/github.com/cockroachdb/cockroach/storage/scheduler.go:168 +0x3e7
github.com/cockroachdb/cockroach/storage.(*raftScheduler).Start.func1()
/go/src/github.com/cockroachdb/cockroach/storage/scheduler.go:160 +0x33
github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker.func1(0xc4201ce000, 0xc4202c3ac0)
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:187 +0x7d
created by github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:188 +0x66
goroutine 1116 [select]:
github.com/cockroachdb/cockroach/storage.(*raftScheduler).worker(0xc4201daf50, 0xc4201ce000)
/go/src/github.com/cockroachdb/cockroach/storage/scheduler.go:168 +0x3e7
github.com/cockroachdb/cockroach/storage.(*raftScheduler).Start.func1()
/go/src/github.com/cockroachdb/cockroach/storage/scheduler.go:160 +0x33
github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker.func1(0xc4201ce000, 0xc4202c3a60)
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:187 +0x7d
created by github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:188 +0x66
goroutine 1117 [select]:
github.com/cockroachdb/cockroach/storage.(*raftScheduler).worker(0xc4201daf50, 0xc4201ce000)
/go/src/github.com/cockroachdb/cockroach/storage/scheduler.go:168 +0x3e7
github.com/cockroachdb/cockroach/storage.(*raftScheduler).Start.func1()
/go/src/github.com/cockroachdb/cockroach/storage/scheduler.go:160 +0x33
github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker.func1(0xc4201ce000, 0xc4202c3a80)
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:187 +0x7d
created by github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:188 +0x66
goroutine 1118 [select]:
github.com/cockroachdb/cockroach/storage.(*raftScheduler).worker(0xc4201daf50, 0xc4201ce000)
/go/src/github.com/cockroachdb/cockroach/storage/scheduler.go:168 +0x3e7
github.com/cockroachdb/cockroach/storage.(*raftScheduler).Start.func1()
/go/src/github.com/cockroachdb/cockroach/storage/scheduler.go:160 +0x33
github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker.func1(0xc4201ce000, 0xc4202c3aa0)
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:187 +0x7d
created by github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:188 +0x66
goroutine 1106 [select]:
github.com/cockroachdb/cockroach/storage.(*raftScheduler).worker(0xc4201daf50, 0xc4201ce000)
/go/src/github.com/cockroachdb/cockroach/storage/scheduler.go:168 +0x3e7
github.com/cockroachdb/cockroach/storage.(*raftScheduler).Start.func1()
/go/src/github.com/cockroachdb/cockroach/storage/scheduler.go:160 +0x33
github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker.func1(0xc4201ce000, 0xc4202c3920)
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:187 +0x7d
created by github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:188 +0x66
goroutine 1001 [semacquire]:
sync.runtime_Semacquire(0xc4202dc3fc)
/usr/local/go/src/runtime/sema.go:47 +0x30
sync.(*Mutex).Lock(0xc4202dc3f8)
/usr/local/go/src/sync/mutex.go:85 +0xd0
github.com/cockroachdb/cockroach/storage.(*baseQueue).pop(0xc4200c11e0, 0xc42051aae0)
/go/src/github.com/cockroachdb/cockroach/storage/queue.go:603 +0x3b
github.com/cockroachdb/cockroach/storage.(*baseQueue).processLoop.func1()
/go/src/github.com/cockroachdb/cockroach/storage/queue.go:436 +0x1fc
github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker.func1(0xc4201ce000, 0xc42067d320)
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:187 +0x7d
created by github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:188 +0x66
goroutine 1098 [select]:
github.com/cockroachdb/cockroach/storage.(*raftScheduler).worker(0xc4201daf50, 0xc4201ce000)
/go/src/github.com/cockroachdb/cockroach/storage/scheduler.go:168 +0x3e7
github.com/cockroachdb/cockroach/storage.(*raftScheduler).Start.func1()
/go/src/github.com/cockroachdb/cockroach/storage/scheduler.go:160 +0x33
github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker.func1(0xc4201ce000, 0xc4202c3820)
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:187 +0x7d
created by github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:188 +0x66
goroutine 1102 [select]:
github.com/cockroachdb/cockroach/storage.(*raftScheduler).worker(0xc4201daf50, 0xc4201ce000)
/go/src/github.com/cockroachdb/cockroach/storage/scheduler.go:168 +0x3e7
github.com/cockroachdb/cockroach/storage.(*raftScheduler).Start.func1()
/go/src/github.com/cockroachdb/cockroach/storage/scheduler.go:160 +0x33
github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker.func1(0xc4201ce000, 0xc4202c38a0)
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:187 +0x7d
created by github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:188 +0x66
goroutine 1120 [select]:
github.com/cockroachdb/cockroach/storage.(*raftScheduler).worker(0xc4201daf50, 0xc4201ce000)
/go/src/github.com/cockroachdb/cockroach/storage/scheduler.go:168 +0x3e7
github.com/cockroachdb/cockroach/storage.(*raftScheduler).Start.func1()
/go/src/github.com/cockroachdb/cockroach/storage/scheduler.go:160 +0x33
github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker.func1(0xc4201ce000, 0xc4202c3ae0)
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:187 +0x7d
created by github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:188 +0x66
goroutine 1107 [select]:
github.com/cockroachdb/cockroach/storage.(*raftScheduler).worker(0xc4201daf50, 0xc4201ce000)
/go/src/github.com/cockroachdb/cockroach/storage/scheduler.go:168 +0x3e7
github.com/cockroachdb/cockroach/storage.(*raftScheduler).Start.func1()
/go/src/github.com/cockroachdb/cockroach/storage/scheduler.go:160 +0x33
github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker.func1(0xc4201ce000, 0xc4202c3940)
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:187 +0x7d
created by github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:188 +0x66
goroutine 1108 [select]:
github.com/cockroachdb/cockroach/storage.(*raftScheduler).worker(0xc4201daf50, 0xc4201ce000)
/go/src/github.com/cockroachdb/cockroach/storage/scheduler.go:168 +0x3e7
github.com/cockroachdb/cockroach/storage.(*raftScheduler).Start.func1()
/go/src/github.com/cockroachdb/cockroach/storage/scheduler.go:160 +0x33
github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker.func1(0xc4201ce000, 0xc4202c3960)
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:187 +0x7d
created by github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:188 +0x66
goroutine 1109 [select]:
github.com/cockroachdb/cockroach/storage.(*raftScheduler).worker(0xc4201daf50, 0xc4201ce000)
/go/src/github.com/cockroachdb/cockroach/storage/scheduler.go:168 +0x3e7
github.com/cockroachdb/cockroach/storage.(*raftScheduler).Start.func1()
/go/src/github.com/cockroachdb/cockroach/storage/scheduler.go:160 +0x33
github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker.func1(0xc4201ce000, 0xc4202c3980)
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:187 +0x7d
created by github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:188 +0x66
goroutine 1110 [select]:
github.com/cockroachdb/cockroach/storage.(*raftScheduler).worker(0xc4201daf50, 0xc4201ce000)
/go/src/github.com/cockroachdb/cockroach/storage/scheduler.go:168 +0x3e7
github.com/cockroachdb/cockroach/storage.(*raftScheduler).Start.func1()
/go/src/github.com/cockroachdb/cockroach/storage/scheduler.go:160 +0x33
github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker.func1(0xc4201ce000, 0xc4202c39a0)
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:187 +0x7d
created by github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:188 +0x66
goroutine 1111 [runnable]:
github.com/cockroachdb/cockroach/storage.(*raftScheduler).worker(0xc4201daf50, 0xc4201ce000)
/go/src/github.com/cockroachdb/cockroach/storage/scheduler.go:168 +0x3e7
github.com/cockroachdb/cockroach/storage.(*raftScheduler).Start.func1()
/go/src/github.com/cockroachdb/cockroach/storage/scheduler.go:160 +0x33
github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker.func1(0xc4201ce000, 0xc4202c39c0)
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:187 +0x7d
created by github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:188 +0x66
goroutine 1112 [select]:
github.com/cockroachdb/cockroach/storage.(*raftScheduler).worker(0xc4201daf50, 0xc4201ce000)
/go/src/github.com/cockroachdb/cockroach/storage/scheduler.go:168 +0x3e7
github.com/cockroachdb/cockroach/storage.(*raftScheduler).Start.func1()
/go/src/github.com/cockroachdb/cockroach/storage/scheduler.go:160 +0x33
github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker.func1(0xc4201ce000, 0xc4202c39e0)
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:187 +0x7d
created by github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:188 +0x66
goroutine 1113 [select]:
github.com/cockroachdb/cockroach/storage.(*raftScheduler).worker(0xc4201daf50, 0xc4201ce000)
/go/src/github.com/cockroachdb/cockroach/storage/scheduler.go:168 +0x3e7
github.com/cockroachdb/cockroach/storage.(*raftScheduler).Start.func1()
/go/src/github.com/cockroachdb/cockroach/storage/scheduler.go:160 +0x33
github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker.func1(0xc4201ce000, 0xc4202c3a00)
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:187 +0x7d
created by github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:188 +0x66
goroutine 1114 [select]:
github.com/cockroachdb/cockroach/storage.(*raftScheduler).worker(0xc4201daf50, 0xc4201ce000)
/go/src/github.com/cockroachdb/cockroach/storage/scheduler.go:168 +0x3e7
github.com/cockroachdb/cockroach/storage.(*raftScheduler).Start.func1()
/go/src/github.com/cockroachdb/cockroach/storage/scheduler.go:160 +0x33
github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker.func1(0xc4201ce000, 0xc4202c3a20)
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:187 +0x7d
created by github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:188 +0x66
goroutine 1115 [select]:
github.com/cockroachdb/cockroach/storage.(*raftScheduler).worker(0xc4201daf50, 0xc4201ce000)
/go/src/github.com/cockroachdb/cockroach/storage/scheduler.go:168 +0x3e7
github.com/cockroachdb/cockroach/storage.(*raftScheduler).Start.func1()
/go/src/github.com/cockroachdb/cockroach/storage/scheduler.go:160 +0x33
github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker.func1(0xc4201ce000, 0xc4202c3a40)
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:187 +0x7d
created by github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:188 +0x66
goroutine 1100 [select]:
github.com/cockroachdb/cockroach/storage.(*raftScheduler).worker(0xc4201daf50, 0xc4201ce000)
/go/src/github.com/cockroachdb/cockroach/storage/scheduler.go:168 +0x3e7
github.com/cockroachdb/cockroach/storage.(*raftScheduler).Start.func1()
/go/src/github.com/cockroachdb/cockroach/storage/scheduler.go:160 +0x33
github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker.func1(0xc4201ce000, 0xc4202c3860)
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:187 +0x7d
created by github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:188 +0x66
goroutine 1101 [select]:
github.com/cockroachdb/cockroach/storage.(*raftScheduler).worker(0xc4201daf50, 0xc4201ce000)
/go/src/github.com/cockroachdb/cockroach/storage/scheduler.go:168 +0x3e7
github.com/cockroachdb/cockroach/storage.(*raftScheduler).Start.func1()
/go/src/github.com/cockroachdb/cockroach/storage/scheduler.go:160 +0x33
github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker.func1(0xc4201ce000, 0xc4202c3880)
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:187 +0x7d
created by github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:188 +0x66
goroutine 1105 [select]:
github.com/cockroachdb/cockroach/storage.(*raftScheduler).worker(0xc4201daf50, 0xc4201ce000)
/go/src/github.com/cockroachdb/cockroach/storage/scheduler.go:168 +0x3e7
github.com/cockroachdb/cockroach/storage.(*raftScheduler).Start.func1()
/go/src/github.com/cockroachdb/cockroach/storage/scheduler.go:160 +0x33
github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker.func1(0xc4201ce000, 0xc4202c3900)
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:187 +0x7d
created by github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:188 +0x66
goroutine 1103 [select]:
github.com/cockroachdb/cockroach/storage.(*raftScheduler).worker(0xc4201daf50, 0xc4201ce000)
/go/src/github.com/cockroachdb/cockroach/storage/scheduler.go:168 +0x3e7
github.com/cockroachdb/cockroach/storage.(*raftScheduler).Start.func1()
/go/src/github.com/cockroachdb/cockroach/storage/scheduler.go:160 +0x33
github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker.func1(0xc4201ce000, 0xc4202c38c0)
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:187 +0x7d
created by github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:188 +0x66
goroutine 1104 [select]:
github.com/cockroachdb/cockroach/storage.(*raftScheduler).worker(0xc4201daf50, 0xc4201ce000)
/go/src/github.com/cockroachdb/cockroach/storage/scheduler.go:168 +0x3e7
github.com/cockroachdb/cockroach/storage.(*raftScheduler).Start.func1()
/go/src/github.com/cockroachdb/cockroach/storage/scheduler.go:160 +0x33
github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker.func1(0xc4201ce000, 0xc4202c38e0)
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:187 +0x7d
created by github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:188 +0x66
goroutine 1121 [select]:
github.com/cockroachdb/cockroach/storage.(*raftScheduler).worker(0xc4201daf50, 0xc4201ce000)
/go/src/github.com/cockroachdb/cockroach/storage/scheduler.go:168 +0x3e7
github.com/cockroachdb/cockroach/storage.(*raftScheduler).Start.func1()
/go/src/github.com/cockroachdb/cockroach/storage/scheduler.go:160 +0x33
github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker.func1(0xc4201ce000, 0xc4202c3b00)
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:187 +0x7d
created by github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:188 +0x66
goroutine 1122 [select]:
github.com/cockroachdb/cockroach/storage.(*raftScheduler).worker(0xc4201daf50, 0xc4201ce000)
/go/src/github.com/cockroachdb/cockroach/storage/scheduler.go:168 +0x3e7
github.com/cockroachdb/cockroach/storage.(*raftScheduler).Start.func1()
/go/src/github.com/cockroachdb/cockroach/storage/scheduler.go:160 +0x33
github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker.func1(0xc4201ce000, 0xc4202c3b20)
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:187 +0x7d
created by github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:188 +0x66
goroutine 1123 [select]:
github.com/cockroachdb/cockroach/storage.(*raftScheduler).worker(0xc4201daf50, 0xc4201ce000)
/go/src/github.com/cockroachdb/cockroach/storage/scheduler.go:168 +0x3e7
github.com/cockroachdb/cockroach/storage.(*raftScheduler).Start.func1()
/go/src/github.com/cockroachdb/cockroach/storage/scheduler.go:160 +0x33
github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker.func1(0xc4201ce000, 0xc4202c3b40)
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:187 +0x7d
created by github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:188 +0x66
goroutine 1124 [select]:
github.com/cockroachdb/cockroach/storage.(*raftScheduler).worker(0xc4201daf50, 0xc4201ce000)
/go/src/github.com/cockroachdb/cockroach/storage/scheduler.go:168 +0x3e7
github.com/cockroachdb/cockroach/storage.(*raftScheduler).Start.func1()
/go/src/github.com/cockroachdb/cockroach/storage/scheduler.go:160 +0x33
github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker.func1(0xc4201ce000, 0xc4202c3b60)
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:187 +0x7d
created by github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:188 +0x66
goroutine 1125 [select]:
github.com/cockroachdb/cockroach/storage.(*raftScheduler).worker(0xc4201daf50, 0xc4201ce000)
/go/src/github.com/cockroachdb/cockroach/storage/scheduler.go:168 +0x3e7
github.com/cockroachdb/cockroach/storage.(*raftScheduler).Start.func1()
/go/src/github.com/cockroachdb/cockroach/storage/scheduler.go:160 +0x33
github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker.func1(0xc4201ce000, 0xc4202c3b80)
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:187 +0x7d
created by github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:188 +0x66
goroutine 1126 [select]:
github.com/cockroachdb/cockroach/storage.(*raftScheduler).worker(0xc4201daf50, 0xc4201ce000)
/go/src/github.com/cockroachdb/cockroach/storage/scheduler.go:168 +0x3e7
github.com/cockroachdb/cockroach/storage.(*raftScheduler).Start.func1()
/go/src/github.com/cockroachdb/cockroach/storage/scheduler.go:160 +0x33
github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker.func1(0xc4201ce000, 0xc4202c3ba0)
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:187 +0x7d
created by github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:188 +0x66
goroutine 1127 [select]:
github.com/cockroachdb/cockroach/storage.(*raftScheduler).worker(0xc4201daf50, 0xc4201ce000)
/go/src/github.com/cockroachdb/cockroach/storage/scheduler.go:168 +0x3e7
github.com/cockroachdb/cockroach/storage.(*raftScheduler).Start.func1()
/go/src/github.com/cockroachdb/cockroach/storage/scheduler.go:160 +0x33
github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker.func1(0xc4201ce000, 0xc4202c3bc0)
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:187 +0x7d
created by github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:188 +0x66
goroutine 1128 [select]:
github.com/cockroachdb/cockroach/storage.(*Store).raftTickLoop.func1()
/go/src/github.com/cockroachdb/cockroach/storage/store.go:2629 +0x334
github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker.func1(0xc4201ce000, 0xc42065a8b0)
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:187 +0x7d
created by github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:188 +0x66
goroutine 1129 [select]:
github.com/cockroachdb/cockroach/storage.(*Store).raftSnapshotStatusLoop.func1()
/go/src/github.com/cockroachdb/cockroach/storage/store.go:2659 +0x211
github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker.func1(0xc4201ce000, 0xc42065a8c0)
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:187 +0x7d
created by github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:188 +0x66
goroutine 1131 [select]:
github.com/cockroachdb/cockroach/storage.(*Store).Start.func3()
/go/src/github.com/cockroachdb/cockroach/storage/store.go:964 +0x165
github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker.func1(0xc4201ce000, 0xc4202c3c40)
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:187 +0x7d
created by github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:188 +0x66
goroutine 1132 [select]:
github.com/cockroachdb/cockroach/storage.(*Store).startGossip.func1()
/go/src/github.com/cockroachdb/cockroach/storage/store.go:1039 +0x314
github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker.func1(0xc4201ce000, 0xc42065a900)
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:187 +0x7d
created by github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:188 +0x66
goroutine 1133 [select]:
github.com/cockroachdb/cockroach/storage.(*Store).startGossip.func2()
/go/src/github.com/cockroachdb/cockroach/storage/store.go:1058 +0x314
github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker.func1(0xc4201ce000, 0xc42065a910)
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:187 +0x7d
created by github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:188 +0x66
goroutine 1154 [select]:
github.com/cockroachdb/cockroach/storage.(*baseQueue).processLoop.func1()
/go/src/github.com/cockroachdb/cockroach/storage/queue.go:418 +0x2cc
github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker.func1(0xc4201ce000, 0xc42053a000)
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:187 +0x7d
created by github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:188 +0x66
goroutine 1155 [select]:
github.com/cockroachdb/cockroach/storage.(*Replica).redirectOnOrAcquireLease(0xc420158fc0, 0x7f6af88dea68, 0xc420154120, 0x12)
/go/src/github.com/cockroachdb/cockroach/storage/replica.go:750 +0x4ec
github.com/cockroachdb/cockroach/storage.(*baseQueue).processReplica(0xc42022e790, 0xc420158fc0, 0xc42067e440, 0x0, 0x0)
/go/src/github.com/cockroachdb/cockroach/storage/queue.go:489 +0x563
github.com/cockroachdb/cockroach/storage.(*baseQueue).processLoop.func1.2()
/go/src/github.com/cockroachdb/cockroach/storage/queue.go:439 +0x58
github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunTask(0xc4201ce000, 0xc420577e78, 0x0, 0x0)
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:215 +0x100
github.com/cockroachdb/cockroach/storage.(*baseQueue).processLoop.func1()
/go/src/github.com/cockroachdb/cockroach/storage/queue.go:443 +0x296
github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker.func1(0xc4201ce000, 0xc42053a020)
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:187 +0x7d
created by github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:188 +0x66
goroutine 1156 [select]:
github.com/cockroachdb/cockroach/storage.(*baseQueue).processLoop.func1()
/go/src/github.com/cockroachdb/cockroach/storage/queue.go:418 +0x2cc
github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker.func1(0xc4201ce000, 0xc42053a040)
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:187 +0x7d
created by github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:188 +0x66
goroutine 1157 [select]:
github.com/cockroachdb/cockroach/storage.(*baseQueue).processLoop.func1()
/go/src/github.com/cockroachdb/cockroach/storage/queue.go:418 +0x2cc
github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker.func1(0xc4201ce000, 0xc42053a060)
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:187 +0x7d
created by github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:188 +0x66
goroutine 1158 [select]:
github.com/cockroachdb/cockroach/storage.(*baseQueue).processLoop.func1()
/go/src/github.com/cockroachdb/cockroach/storage/queue.go:418 +0x2cc
github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker.func1(0xc4201ce000, 0xc42053a080)
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:187 +0x7d
created by github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:188 +0x66
goroutine 1159 [select]:
github.com/cockroachdb/cockroach/storage.(*baseQueue).processLoop.func1()
/go/src/github.com/cockroachdb/cockroach/storage/queue.go:418 +0x2cc
github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker.func1(0xc4201ce000, 0xc42053a0a0)
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:187 +0x7d
created by github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:188 +0x66
goroutine 1160 [select]:
github.com/cockroachdb/cockroach/storage.(*replicaScanner).waitAndProcess(0xc42023eb00, 0xecf66d54b, 0xc437ee100e, 0x24a99c0, 0xc42067e440, 0xc4201ce000, 0xc4200b2240, 0xc4205126c8)
/go/src/github.com/cockroachdb/cockroach/storage/scanner.go:201 +0x237
github.com/cockroachdb/cockroach/storage.(*replicaScanner).scanLoop.func1.1(0xc4200b2240, 0xc4202c4db0)
/go/src/github.com/cockroachdb/cockroach/storage/scanner.go:259 +0x7c
github.com/cockroachdb/cockroach/storage.(*storeRangeSet).Visit(0xc4202c4e70, 0xc4200167c0)
/go/src/github.com/cockroachdb/cockroach/storage/store.go:246 +0x21b
github.com/cockroachdb/cockroach/storage.(*replicaScanner).scanLoop.func1()
/go/src/github.com/cockroachdb/cockroach/storage/scanner.go:261 +0x233
github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker.func1(0xc4201ce000, 0xc42053a0c0)
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:187 +0x7d
created by github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:188 +0x66
goroutine 1136 [select]:
github.com/cockroachdb/cockroach/storage.(*baseQueue).processLoop.func1()
/go/src/github.com/cockroachdb/cockroach/storage/queue.go:418 +0x2cc
github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker.func1(0xc4201ce000, 0xc4202c3c60)
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:187 +0x7d
created by github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:188 +0x66
goroutine 1137 [select]:
github.com/cockroachdb/cockroach/storage.(*replicaScanner).waitAndProcess(0xc42023eb80, 0xecf66d54b, 0xc43806555d, 0x24a99c0, 0xc42067e440, 0xc4201ce000, 0xc420158b40, 0xc420483ec8)
/go/src/github.com/cockroachdb/cockroach/storage/scanner.go:201 +0x237
github.com/cockroachdb/cockroach/storage.(*replicaScanner).scanLoop.func1.1(0xc420158b40, 0xc4202c4db0)
/go/src/github.com/cockroachdb/cockroach/storage/scanner.go:259 +0x7c
github.com/cockroachdb/cockroach/storage.(*storeRangeSet).Visit(0xc4202c5260, 0xc42067e800)
/go/src/github.com/cockroachdb/cockroach/storage/store.go:246 +0x21b
github.com/cockroachdb/cockroach/storage.(*replicaScanner).scanLoop.func1()
/go/src/github.com/cockroachdb/cockroach/storage/scanner.go:261 +0x233
github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker.func1(0xc4201ce000, 0xc4202c3c80)
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:187 +0x7d
created by github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:188 +0x66
ERROR: exit status 2
```
Run Details:
```
1 runs completed, 1 failures, over 1s
FAIL
```
Please assign, take a look and update the issue accordingly. | 1.0 | stress: failed test in cockroach/storage/storage.test: TestAcceptsUnsplitRanges - Binary: cockroach/static-tests.tar.gz sha: https://github.com/cockroachdb/cockroach/commits/860d5044234abcda41ca45990e3f0f2cebabf454
Stress build found a failed test:
```
=== RUN TestAcceptsUnsplitRanges
I160911 04:32:11.934913 1090 gossip/gossip.go:230 initial resolvers: []
W160911 04:32:11.934938 1090 gossip/gossip.go:1041 no resolvers found; use --join to specify a connected node
I160911 04:32:11.934984 1090 gossip/gossip.go:264 NodeID set to 1
I160911 04:32:11.935052 1090 storage/engine/rocksdb.go:356 opening in memory rocksdb instance
I160911 04:32:11.936300 1090 gossip/gossip.go:264 NodeID set to 1
I160911 04:32:11.936421 1090 gossip/gossip.go:264 NodeID set to 1
I160911 04:32:11.938711 1097 storage/replica_trigger.go:308 new range lease replica {1 1 1} 1970-01-01 00:00:00 +0000 UTC 900ms following replica {0 0 0} 1970-01-01 00:00:00 +0000 UTC 0s [physicalTime=1970-01-01 00:00:00 +0000 UTC]
panic: runtime error: invalid memory address or nil pointer dereference [recovered]
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0xaa713c]
goroutine 404 [running]:
panic(0x16512e0, 0xc4200100e0)
/usr/local/go/src/runtime/panic.go:500 +0x1a1
github.com/cockroachdb/cockroach/util/stop.(*Stopper).Recover(0xc4201ce000)
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:176 +0x6e
panic(0x16512e0, 0xc4200100e0)
/usr/local/go/src/runtime/panic.go:458 +0x243
github.com/coreos/etcd/raft.(*raft).appendEntry(0xc42057c0f0, 0xc42056e320, 0x1, 0x1)
/go/src/github.com/coreos/etcd/raft/raft.go:465 +0xdc
github.com/coreos/etcd/raft.(*raft).becomeLeader(0xc42057c0f0)
/go/src/github.com/coreos/etcd/raft/raft.go:551 +0x1d1
github.com/coreos/etcd/raft.(*raft).campaign(0xc42057c0f0, 0x17a1faf, 0x10)
/go/src/github.com/coreos/etcd/raft/raft.go:558 +0x709
github.com/coreos/etcd/raft.(*raft).Step(0xc42057c0f0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, ...)
/go/src/github.com/coreos/etcd/raft/raft.go:606 +0x243
github.com/coreos/etcd/raft.(*RawNode).Campaign(0xc420562580, 0x0, 0x0)
/go/src/github.com/coreos/etcd/raft/rawnode.go:127 +0x71
github.com/cockroachdb/cockroach/storage.(*Replica).withRaftGroupLocked(0xc420158fc0, 0xc420571ae0, 0x0, 0x0)
/go/src/github.com/cockroachdb/cockroach/storage/replica.go:416 +0x2a2
github.com/cockroachdb/cockroach/storage.defaultProposeRaftCommandLocked(0xc420158fc0, 0xc420526480, 0x0, 0x0)
/go/src/github.com/cockroachdb/cockroach/storage/replica.go:1637 +0x223
github.com/cockroachdb/cockroach/storage.(*Replica).proposePendingCmdLocked(0xc420158fc0, 0xc420526480, 0xc420010540, 0xc42056c220)
/go/src/github.com/cockroachdb/cockroach/storage/replica.go:1586 +0x77
github.com/cockroachdb/cockroach/storage.(*Replica).proposeRaftCommand(0xc420158fc0, 0x7f6af88d7208, 0xc420010540, 0x0, 0x16, 0x0, 0x0, 0x3, 0x0, 0x0, ...)
/go/src/github.com/cockroachdb/cockroach/storage/replica.go:1565 +0x1f3
github.com/cockroachdb/cockroach/storage.(*pendingLeaseRequest).InitOrJoinRequest.func1()
/go/src/github.com/cockroachdb/cockroach/storage/replica_range_lease.go:133 +0x1a9
github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunAsyncTask.func1(0xc4201ce000, 0x1e52381, 0x1e, 0xa8, 0xc420154270)
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:231 +0x95
created by github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunAsyncTask
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:232 +0xbc
goroutine 1 [chan receive]:
testing.(*T).Run(0xc42009e240, 0x17aac7e, 0x18, 0x1915e00, 0xc420239a01)
/usr/local/go/src/testing/testing.go:647 +0x316
testing.RunTests.func1(0xc42009e240)
/usr/local/go/src/testing/testing.go:793 +0x6d
testing.tRunner(0xc42009e240, 0xc4200fbbc0)
/usr/local/go/src/testing/testing.go:610 +0x81
testing.RunTests(0x1917cc0, 0x2162f60, 0x143, 0x143, 0xc4202421d0)
/usr/local/go/src/testing/testing.go:799 +0x2f5
testing.(*M).Run(0xc4200fbee8, 0xc420239d30)
/usr/local/go/src/testing/testing.go:743 +0x85
github.com/cockroachdb/cockroach/storage_test.TestMain(0xc4200fbee8)
/go/src/github.com/cockroachdb/cockroach/storage/main_test.go:57 +0x1ff
main.main()
github.com/cockroachdb/cockroach/storage/_test/_testmain.go:708 +0xc6
goroutine 17 [syscall, locked to thread]:
runtime.goexit()
/usr/local/go/src/runtime/asm_amd64.s:2086 +0x1
goroutine 8 [chan receive]:
github.com/cockroachdb/cockroach/util/log.(*loggingT).flushDaemon(0x24aab20)
/go/src/github.com/cockroachdb/cockroach/util/log/clog.go:1032 +0x77
created by github.com/cockroachdb/cockroach/util/log.init.1
/go/src/github.com/cockroachdb/cockroach/util/log/clog.go:613 +0x95
goroutine 1090 [runnable]:
sync.runtime_Semacquire(0xc4200984fc)
/usr/local/go/src/runtime/sema.go:47 +0x30
sync.(*Mutex).Lock(0xc4200984f8)
/usr/local/go/src/sync/mutex.go:85 +0xd0
sync.(*Pool).getSlow(0x214f2c0, 0xc420098370, 0x0)
/usr/local/go/src/sync/pool.go:133 +0xcc
sync.(*Pool).Get(0x214f2c0, 0x0, 0xc420202110)
/usr/local/go/src/sync/pool.go:121 +0xf1
fmt.newPrinter(0x601d45)
/usr/local/go/src/fmt/print.go:133 +0x31
fmt.Fprintf(0x2167280, 0xc420148310, 0x1795554, 0x4, 0xc420508af8, 0x2, 0x2, 0x2, 0x0, 0x0)
/usr/local/go/src/fmt/print.go:180 +0x26
github.com/cockroachdb/cockroach/util/encoding.PrettyPrintValue(0xc4202dc1f8, 0x1, 0x8, 0x1794d06, 0x1, 0x0, 0x1)
/go/src/github.com/cockroachdb/cockroach/util/encoding/encoding.go:962 +0x3cf
github.com/cockroachdb/cockroach/keys.decodeKeyPrint(0xc4202dc1f8, 0x1, 0x8, 0x0, 0x0)
/go/src/github.com/cockroachdb/cockroach/keys/printer.go:417 +0x54
github.com/cockroachdb/cockroach/keys.prettyPrintInternal(0xc4202dc1f8, 0x1, 0x8, 0x2165403, 0x1, 0x1)
/go/src/github.com/cockroachdb/cockroach/keys/printer.go:442 +0x6f2
github.com/cockroachdb/cockroach/keys.PrettyPrint(0xc4202dc1f8, 0x1, 0x8, 0x5fd39f, 0x24b44c0)
/go/src/github.com/cockroachdb/cockroach/keys/printer.go:507 +0x26c
github.com/cockroachdb/cockroach/roachpb.Key.String(0xc4202dc1f8, 0x1, 0x8, 0xc420508fd8, 0x8a1ffe)
/go/src/github.com/cockroachdb/cockroach/roachpb/data.go:179 +0x52
github.com/cockroachdb/cockroach/roachpb.RKey.String(0xc4202dc1f8, 0x1, 0x8, 0x8a1ffe, 0xc420509018)
/go/src/github.com/cockroachdb/cockroach/roachpb/data.go:103 +0x3f
github.com/cockroachdb/cockroach/roachpb.(*RKey).String(0xc420598900, 0x1914958, 0xc42009e600)
<autogenerated>:95 +0x64
fmt.(*pp).handleMethods(0xc42009e600, 0x73, 0xc420202101)
/usr/local/go/src/fmt/print.go:590 +0x2f6
fmt.(*pp).printArg(0xc42009e600, 0x16ca2a0, 0xc420598900, 0xc400000073)
/usr/local/go/src/fmt/print.go:665 +0x17b
fmt.(*pp).doPrintf(0xc42009e600, 0x179b214, 0x9, 0xc420509350, 0x3, 0x3)
/usr/local/go/src/fmt/print.go:985 +0x123d
fmt.Sprintf(0x179b214, 0x9, 0xc420509350, 0x3, 0x3, 0x7f6af8843b78, 0x0)
/usr/local/go/src/fmt/print.go:196 +0x6a
github.com/cockroachdb/cockroach/storage.(*atomicRangeDesc).String(0xc420159020, 0x1914958, 0xc42009e180)
/go/src/github.com/cockroachdb/cockroach/storage/replica.go:197 +0x181
fmt.(*pp).handleMethods(0xc42009e180, 0x73, 0xc420202101)
/usr/local/go/src/fmt/print.go:590 +0x2f6
fmt.(*pp).printArg(0xc42009e180, 0x1670d60, 0xc420159020, 0xc400000073)
/usr/local/go/src/fmt/print.go:665 +0x17b
fmt.(*pp).doPrintf(0xc42009e180, 0x179f98f, 0xd, 0xc420509708, 0x3, 0x3)
/usr/local/go/src/fmt/print.go:985 +0x123d
fmt.Sprintf(0x179f98f, 0xd, 0xc420509708, 0x3, 0x3, 0xc420509748, 0xc420509758)
/usr/local/go/src/fmt/print.go:196 +0x6a
github.com/cockroachdb/cockroach/storage.(*Replica).String(0xc420158fc0, 0x1914958, 0xc4200a8000)
/go/src/github.com/cockroachdb/cockroach/storage/replica.go:546 +0x113
fmt.(*pp).handleMethods(0xc4200a8000, 0x73, 0x1721401)
/usr/local/go/src/fmt/print.go:590 +0x2f6
fmt.(*pp).printArg(0xc4200a8000, 0x17943c0, 0xc420158fc0, 0x73)
/usr/local/go/src/fmt/print.go:665 +0x17b
fmt.(*pp).doPrintf(0xc4200a8000, 0x17afc8a, 0x1c, 0xc420509bd0, 0x1, 0x1)
/usr/local/go/src/fmt/print.go:985 +0x123d
fmt.Fprintf(0x2167280, 0xc420148230, 0x17afc8a, 0x1c, 0xc420509bd0, 0x1, 0x1, 0xc420509ad0, 0x8941e9, 0xc4201936c0)
/usr/local/go/src/fmt/print.go:181 +0x76
github.com/cockroachdb/cockroach/util/log.eventInternal(0x7f6af88dea68, 0xc4201b2f60, 0xc4202d0100, 0x17afc8a, 0x1c, 0xc420509bd0, 0x1, 0x1)
/go/src/github.com/cockroachdb/cockroach/util/log/trace.go:112 +0x401
github.com/cockroachdb/cockroach/util/log.VEventf(0xc400000001, 0x7f6af88dea68, 0xc4201b2f60, 0x17afc8a, 0x1c, 0xc420509bd0, 0x1, 0x1)
/go/src/github.com/cockroachdb/cockroach/util/log/trace.go:189 +0x107
github.com/cockroachdb/cockroach/storage.(*baseQueue).MaybeAdd(0xc4200c11e0, 0xc420158fc0, 0x0, 0xc400000000)
/go/src/github.com/cockroachdb/cockroach/storage/queue.go:298 +0x1cb
github.com/cockroachdb/cockroach/storage.TestAcceptsUnsplitRanges(0xc4204ec180)
/go/src/github.com/cockroachdb/cockroach/storage/queue_test.go:455 +0x909
testing.tRunner(0xc4204ec180, 0x1915e00)
/usr/local/go/src/testing/testing.go:610 +0x81
created by testing.(*T).Run
/usr/local/go/src/testing/testing.go:646 +0x2ec
goroutine 1096 [select]:
github.com/cockroachdb/cockroach/storage.(*raftScheduler).worker(0xc4201daf50, 0xc4201ce000)
/go/src/github.com/cockroachdb/cockroach/storage/scheduler.go:168 +0x3e7
github.com/cockroachdb/cockroach/storage.(*raftScheduler).Start.func1()
/go/src/github.com/cockroachdb/cockroach/storage/scheduler.go:160 +0x33
github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker.func1(0xc4201ce000, 0xc4202c37e0)
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:187 +0x7d
created by github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:188 +0x66
goroutine 1095 [select]:
github.com/cockroachdb/cockroach/storage.(*bookie).start.func1()
/go/src/github.com/cockroachdb/cockroach/storage/reservation.go:274 +0x217
github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker.func1(0xc4201ce000, 0xc4202c3320)
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:187 +0x7d
created by github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:188 +0x66
goroutine 1091 [chan receive]:
github.com/cockroachdb/cockroach/rpc.NewContext.func1()
/go/src/github.com/cockroachdb/cockroach/rpc/context.go:134 +0x76
github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker.func1(0xc4201ce000, 0xc4202c21c0)
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:187 +0x7d
created by github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:188 +0x66
goroutine 1093 [chan receive]:
github.com/cockroachdb/cockroach/storage/engine.(*RocksDB).Open.func1(0xc420014de0)
/go/src/github.com/cockroachdb/cockroach/storage/engine/rocksdb.go:390 +0x44
created by github.com/cockroachdb/cockroach/storage/engine.(*RocksDB).Open
/go/src/github.com/cockroachdb/cockroach/storage/engine/rocksdb.go:391 +0x6eb
goroutine 1092 [select]:
github.com/cockroachdb/cockroach/storage.(*StorePool).start.func1()
/go/src/github.com/cockroachdb/cockroach/storage/store_pool.go:340 +0x3da
github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker.func1(0xc4201ce000, 0xc4202c2b20)
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:187 +0x7d
created by github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:188 +0x66
goroutine 1097 [select]:
github.com/cockroachdb/cockroach/storage.(*raftScheduler).worker(0xc4201daf50, 0xc4201ce000)
/go/src/github.com/cockroachdb/cockroach/storage/scheduler.go:168 +0x3e7
github.com/cockroachdb/cockroach/storage.(*raftScheduler).Start.func1()
/go/src/github.com/cockroachdb/cockroach/storage/scheduler.go:160 +0x33
github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker.func1(0xc4201ce000, 0xc4202c3800)
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:187 +0x7d
created by github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:188 +0x66
goroutine 1099 [select]:
github.com/cockroachdb/cockroach/storage.(*raftScheduler).worker(0xc4201daf50, 0xc4201ce000)
/go/src/github.com/cockroachdb/cockroach/storage/scheduler.go:168 +0x3e7
github.com/cockroachdb/cockroach/storage.(*raftScheduler).Start.func1()
/go/src/github.com/cockroachdb/cockroach/storage/scheduler.go:160 +0x33
github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker.func1(0xc4201ce000, 0xc4202c3840)
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:187 +0x7d
created by github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:188 +0x66
goroutine 1119 [select]:
github.com/cockroachdb/cockroach/storage.(*raftScheduler).worker(0xc4201daf50, 0xc4201ce000)
/go/src/github.com/cockroachdb/cockroach/storage/scheduler.go:168 +0x3e7
github.com/cockroachdb/cockroach/storage.(*raftScheduler).Start.func1()
/go/src/github.com/cockroachdb/cockroach/storage/scheduler.go:160 +0x33
github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker.func1(0xc4201ce000, 0xc4202c3ac0)
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:187 +0x7d
created by github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:188 +0x66
goroutine 1116 [select]:
github.com/cockroachdb/cockroach/storage.(*raftScheduler).worker(0xc4201daf50, 0xc4201ce000)
/go/src/github.com/cockroachdb/cockroach/storage/scheduler.go:168 +0x3e7
github.com/cockroachdb/cockroach/storage.(*raftScheduler).Start.func1()
/go/src/github.com/cockroachdb/cockroach/storage/scheduler.go:160 +0x33
github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker.func1(0xc4201ce000, 0xc4202c3a60)
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:187 +0x7d
created by github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:188 +0x66
goroutine 1117 [select]:
github.com/cockroachdb/cockroach/storage.(*raftScheduler).worker(0xc4201daf50, 0xc4201ce000)
/go/src/github.com/cockroachdb/cockroach/storage/scheduler.go:168 +0x3e7
github.com/cockroachdb/cockroach/storage.(*raftScheduler).Start.func1()
/go/src/github.com/cockroachdb/cockroach/storage/scheduler.go:160 +0x33
github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker.func1(0xc4201ce000, 0xc4202c3a80)
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:187 +0x7d
created by github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:188 +0x66
goroutine 1118 [select]:
github.com/cockroachdb/cockroach/storage.(*raftScheduler).worker(0xc4201daf50, 0xc4201ce000)
/go/src/github.com/cockroachdb/cockroach/storage/scheduler.go:168 +0x3e7
github.com/cockroachdb/cockroach/storage.(*raftScheduler).Start.func1()
/go/src/github.com/cockroachdb/cockroach/storage/scheduler.go:160 +0x33
github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker.func1(0xc4201ce000, 0xc4202c3aa0)
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:187 +0x7d
created by github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:188 +0x66
goroutine 1106 [select]:
github.com/cockroachdb/cockroach/storage.(*raftScheduler).worker(0xc4201daf50, 0xc4201ce000)
/go/src/github.com/cockroachdb/cockroach/storage/scheduler.go:168 +0x3e7
github.com/cockroachdb/cockroach/storage.(*raftScheduler).Start.func1()
/go/src/github.com/cockroachdb/cockroach/storage/scheduler.go:160 +0x33
github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker.func1(0xc4201ce000, 0xc4202c3920)
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:187 +0x7d
created by github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:188 +0x66
goroutine 1001 [semacquire]:
sync.runtime_Semacquire(0xc4202dc3fc)
/usr/local/go/src/runtime/sema.go:47 +0x30
sync.(*Mutex).Lock(0xc4202dc3f8)
/usr/local/go/src/sync/mutex.go:85 +0xd0
github.com/cockroachdb/cockroach/storage.(*baseQueue).pop(0xc4200c11e0, 0xc42051aae0)
/go/src/github.com/cockroachdb/cockroach/storage/queue.go:603 +0x3b
github.com/cockroachdb/cockroach/storage.(*baseQueue).processLoop.func1()
/go/src/github.com/cockroachdb/cockroach/storage/queue.go:436 +0x1fc
github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker.func1(0xc4201ce000, 0xc42067d320)
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:187 +0x7d
created by github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:188 +0x66
goroutine 1098 [select]:
github.com/cockroachdb/cockroach/storage.(*raftScheduler).worker(0xc4201daf50, 0xc4201ce000)
/go/src/github.com/cockroachdb/cockroach/storage/scheduler.go:168 +0x3e7
github.com/cockroachdb/cockroach/storage.(*raftScheduler).Start.func1()
/go/src/github.com/cockroachdb/cockroach/storage/scheduler.go:160 +0x33
github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker.func1(0xc4201ce000, 0xc4202c3820)
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:187 +0x7d
created by github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:188 +0x66
goroutine 1102 [select]:
github.com/cockroachdb/cockroach/storage.(*raftScheduler).worker(0xc4201daf50, 0xc4201ce000)
/go/src/github.com/cockroachdb/cockroach/storage/scheduler.go:168 +0x3e7
github.com/cockroachdb/cockroach/storage.(*raftScheduler).Start.func1()
/go/src/github.com/cockroachdb/cockroach/storage/scheduler.go:160 +0x33
github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker.func1(0xc4201ce000, 0xc4202c38a0)
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:187 +0x7d
created by github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:188 +0x66
goroutine 1120 [select]:
github.com/cockroachdb/cockroach/storage.(*raftScheduler).worker(0xc4201daf50, 0xc4201ce000)
/go/src/github.com/cockroachdb/cockroach/storage/scheduler.go:168 +0x3e7
github.com/cockroachdb/cockroach/storage.(*raftScheduler).Start.func1()
/go/src/github.com/cockroachdb/cockroach/storage/scheduler.go:160 +0x33
github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker.func1(0xc4201ce000, 0xc4202c3ae0)
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:187 +0x7d
created by github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:188 +0x66
goroutine 1107 [select]:
github.com/cockroachdb/cockroach/storage.(*raftScheduler).worker(0xc4201daf50, 0xc4201ce000)
/go/src/github.com/cockroachdb/cockroach/storage/scheduler.go:168 +0x3e7
github.com/cockroachdb/cockroach/storage.(*raftScheduler).Start.func1()
/go/src/github.com/cockroachdb/cockroach/storage/scheduler.go:160 +0x33
github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker.func1(0xc4201ce000, 0xc4202c3940)
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:187 +0x7d
created by github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:188 +0x66
goroutine 1108 [select]:
github.com/cockroachdb/cockroach/storage.(*raftScheduler).worker(0xc4201daf50, 0xc4201ce000)
/go/src/github.com/cockroachdb/cockroach/storage/scheduler.go:168 +0x3e7
github.com/cockroachdb/cockroach/storage.(*raftScheduler).Start.func1()
/go/src/github.com/cockroachdb/cockroach/storage/scheduler.go:160 +0x33
github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker.func1(0xc4201ce000, 0xc4202c3960)
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:187 +0x7d
created by github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:188 +0x66
goroutine 1109 [select]:
github.com/cockroachdb/cockroach/storage.(*raftScheduler).worker(0xc4201daf50, 0xc4201ce000)
/go/src/github.com/cockroachdb/cockroach/storage/scheduler.go:168 +0x3e7
github.com/cockroachdb/cockroach/storage.(*raftScheduler).Start.func1()
/go/src/github.com/cockroachdb/cockroach/storage/scheduler.go:160 +0x33
github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker.func1(0xc4201ce000, 0xc4202c3980)
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:187 +0x7d
created by github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:188 +0x66
goroutine 1110 [select]:
github.com/cockroachdb/cockroach/storage.(*raftScheduler).worker(0xc4201daf50, 0xc4201ce000)
/go/src/github.com/cockroachdb/cockroach/storage/scheduler.go:168 +0x3e7
github.com/cockroachdb/cockroach/storage.(*raftScheduler).Start.func1()
/go/src/github.com/cockroachdb/cockroach/storage/scheduler.go:160 +0x33
github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker.func1(0xc4201ce000, 0xc4202c39a0)
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:187 +0x7d
created by github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:188 +0x66
goroutine 1111 [runnable]:
github.com/cockroachdb/cockroach/storage.(*raftScheduler).worker(0xc4201daf50, 0xc4201ce000)
/go/src/github.com/cockroachdb/cockroach/storage/scheduler.go:168 +0x3e7
github.com/cockroachdb/cockroach/storage.(*raftScheduler).Start.func1()
/go/src/github.com/cockroachdb/cockroach/storage/scheduler.go:160 +0x33
github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker.func1(0xc4201ce000, 0xc4202c39c0)
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:187 +0x7d
created by github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:188 +0x66
goroutine 1112 [select]:
github.com/cockroachdb/cockroach/storage.(*raftScheduler).worker(0xc4201daf50, 0xc4201ce000)
/go/src/github.com/cockroachdb/cockroach/storage/scheduler.go:168 +0x3e7
github.com/cockroachdb/cockroach/storage.(*raftScheduler).Start.func1()
/go/src/github.com/cockroachdb/cockroach/storage/scheduler.go:160 +0x33
github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker.func1(0xc4201ce000, 0xc4202c39e0)
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:187 +0x7d
created by github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:188 +0x66
goroutine 1113 [select]:
github.com/cockroachdb/cockroach/storage.(*raftScheduler).worker(0xc4201daf50, 0xc4201ce000)
/go/src/github.com/cockroachdb/cockroach/storage/scheduler.go:168 +0x3e7
github.com/cockroachdb/cockroach/storage.(*raftScheduler).Start.func1()
/go/src/github.com/cockroachdb/cockroach/storage/scheduler.go:160 +0x33
github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker.func1(0xc4201ce000, 0xc4202c3a00)
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:187 +0x7d
created by github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:188 +0x66
goroutine 1114 [select]:
github.com/cockroachdb/cockroach/storage.(*raftScheduler).worker(0xc4201daf50, 0xc4201ce000)
/go/src/github.com/cockroachdb/cockroach/storage/scheduler.go:168 +0x3e7
github.com/cockroachdb/cockroach/storage.(*raftScheduler).Start.func1()
/go/src/github.com/cockroachdb/cockroach/storage/scheduler.go:160 +0x33
github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker.func1(0xc4201ce000, 0xc4202c3a20)
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:187 +0x7d
created by github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:188 +0x66
goroutine 1115 [select]:
github.com/cockroachdb/cockroach/storage.(*raftScheduler).worker(0xc4201daf50, 0xc4201ce000)
/go/src/github.com/cockroachdb/cockroach/storage/scheduler.go:168 +0x3e7
github.com/cockroachdb/cockroach/storage.(*raftScheduler).Start.func1()
/go/src/github.com/cockroachdb/cockroach/storage/scheduler.go:160 +0x33
github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker.func1(0xc4201ce000, 0xc4202c3a40)
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:187 +0x7d
created by github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:188 +0x66
goroutine 1100 [select]:
github.com/cockroachdb/cockroach/storage.(*raftScheduler).worker(0xc4201daf50, 0xc4201ce000)
/go/src/github.com/cockroachdb/cockroach/storage/scheduler.go:168 +0x3e7
github.com/cockroachdb/cockroach/storage.(*raftScheduler).Start.func1()
/go/src/github.com/cockroachdb/cockroach/storage/scheduler.go:160 +0x33
github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker.func1(0xc4201ce000, 0xc4202c3860)
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:187 +0x7d
created by github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:188 +0x66
goroutine 1101 [select]:
github.com/cockroachdb/cockroach/storage.(*raftScheduler).worker(0xc4201daf50, 0xc4201ce000)
/go/src/github.com/cockroachdb/cockroach/storage/scheduler.go:168 +0x3e7
github.com/cockroachdb/cockroach/storage.(*raftScheduler).Start.func1()
/go/src/github.com/cockroachdb/cockroach/storage/scheduler.go:160 +0x33
github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker.func1(0xc4201ce000, 0xc4202c3880)
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:187 +0x7d
created by github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:188 +0x66
goroutine 1105 [select]:
github.com/cockroachdb/cockroach/storage.(*raftScheduler).worker(0xc4201daf50, 0xc4201ce000)
/go/src/github.com/cockroachdb/cockroach/storage/scheduler.go:168 +0x3e7
github.com/cockroachdb/cockroach/storage.(*raftScheduler).Start.func1()
/go/src/github.com/cockroachdb/cockroach/storage/scheduler.go:160 +0x33
github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker.func1(0xc4201ce000, 0xc4202c3900)
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:187 +0x7d
created by github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:188 +0x66
goroutine 1103 [select]:
github.com/cockroachdb/cockroach/storage.(*raftScheduler).worker(0xc4201daf50, 0xc4201ce000)
/go/src/github.com/cockroachdb/cockroach/storage/scheduler.go:168 +0x3e7
github.com/cockroachdb/cockroach/storage.(*raftScheduler).Start.func1()
/go/src/github.com/cockroachdb/cockroach/storage/scheduler.go:160 +0x33
github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker.func1(0xc4201ce000, 0xc4202c38c0)
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:187 +0x7d
created by github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:188 +0x66
goroutine 1104 [select]:
github.com/cockroachdb/cockroach/storage.(*raftScheduler).worker(0xc4201daf50, 0xc4201ce000)
/go/src/github.com/cockroachdb/cockroach/storage/scheduler.go:168 +0x3e7
github.com/cockroachdb/cockroach/storage.(*raftScheduler).Start.func1()
/go/src/github.com/cockroachdb/cockroach/storage/scheduler.go:160 +0x33
github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker.func1(0xc4201ce000, 0xc4202c38e0)
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:187 +0x7d
created by github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:188 +0x66
goroutine 1121 [select]:
github.com/cockroachdb/cockroach/storage.(*raftScheduler).worker(0xc4201daf50, 0xc4201ce000)
/go/src/github.com/cockroachdb/cockroach/storage/scheduler.go:168 +0x3e7
github.com/cockroachdb/cockroach/storage.(*raftScheduler).Start.func1()
/go/src/github.com/cockroachdb/cockroach/storage/scheduler.go:160 +0x33
github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker.func1(0xc4201ce000, 0xc4202c3b00)
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:187 +0x7d
created by github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:188 +0x66
goroutine 1122 [select]:
github.com/cockroachdb/cockroach/storage.(*raftScheduler).worker(0xc4201daf50, 0xc4201ce000)
/go/src/github.com/cockroachdb/cockroach/storage/scheduler.go:168 +0x3e7
github.com/cockroachdb/cockroach/storage.(*raftScheduler).Start.func1()
/go/src/github.com/cockroachdb/cockroach/storage/scheduler.go:160 +0x33
github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker.func1(0xc4201ce000, 0xc4202c3b20)
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:187 +0x7d
created by github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:188 +0x66
goroutine 1123 [select]:
github.com/cockroachdb/cockroach/storage.(*raftScheduler).worker(0xc4201daf50, 0xc4201ce000)
/go/src/github.com/cockroachdb/cockroach/storage/scheduler.go:168 +0x3e7
github.com/cockroachdb/cockroach/storage.(*raftScheduler).Start.func1()
/go/src/github.com/cockroachdb/cockroach/storage/scheduler.go:160 +0x33
github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker.func1(0xc4201ce000, 0xc4202c3b40)
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:187 +0x7d
created by github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:188 +0x66
goroutine 1124 [select]:
github.com/cockroachdb/cockroach/storage.(*raftScheduler).worker(0xc4201daf50, 0xc4201ce000)
/go/src/github.com/cockroachdb/cockroach/storage/scheduler.go:168 +0x3e7
github.com/cockroachdb/cockroach/storage.(*raftScheduler).Start.func1()
/go/src/github.com/cockroachdb/cockroach/storage/scheduler.go:160 +0x33
github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker.func1(0xc4201ce000, 0xc4202c3b60)
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:187 +0x7d
created by github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:188 +0x66
goroutine 1125 [select]:
github.com/cockroachdb/cockroach/storage.(*raftScheduler).worker(0xc4201daf50, 0xc4201ce000)
/go/src/github.com/cockroachdb/cockroach/storage/scheduler.go:168 +0x3e7
github.com/cockroachdb/cockroach/storage.(*raftScheduler).Start.func1()
/go/src/github.com/cockroachdb/cockroach/storage/scheduler.go:160 +0x33
github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker.func1(0xc4201ce000, 0xc4202c3b80)
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:187 +0x7d
created by github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:188 +0x66
goroutine 1126 [select]:
github.com/cockroachdb/cockroach/storage.(*raftScheduler).worker(0xc4201daf50, 0xc4201ce000)
/go/src/github.com/cockroachdb/cockroach/storage/scheduler.go:168 +0x3e7
github.com/cockroachdb/cockroach/storage.(*raftScheduler).Start.func1()
/go/src/github.com/cockroachdb/cockroach/storage/scheduler.go:160 +0x33
github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker.func1(0xc4201ce000, 0xc4202c3ba0)
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:187 +0x7d
created by github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:188 +0x66
goroutine 1127 [select]:
github.com/cockroachdb/cockroach/storage.(*raftScheduler).worker(0xc4201daf50, 0xc4201ce000)
/go/src/github.com/cockroachdb/cockroach/storage/scheduler.go:168 +0x3e7
github.com/cockroachdb/cockroach/storage.(*raftScheduler).Start.func1()
/go/src/github.com/cockroachdb/cockroach/storage/scheduler.go:160 +0x33
github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker.func1(0xc4201ce000, 0xc4202c3bc0)
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:187 +0x7d
created by github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:188 +0x66
goroutine 1128 [select]:
github.com/cockroachdb/cockroach/storage.(*Store).raftTickLoop.func1()
/go/src/github.com/cockroachdb/cockroach/storage/store.go:2629 +0x334
github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker.func1(0xc4201ce000, 0xc42065a8b0)
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:187 +0x7d
created by github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:188 +0x66
goroutine 1129 [select]:
github.com/cockroachdb/cockroach/storage.(*Store).raftSnapshotStatusLoop.func1()
/go/src/github.com/cockroachdb/cockroach/storage/store.go:2659 +0x211
github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker.func1(0xc4201ce000, 0xc42065a8c0)
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:187 +0x7d
created by github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:188 +0x66
goroutine 1131 [select]:
github.com/cockroachdb/cockroach/storage.(*Store).Start.func3()
/go/src/github.com/cockroachdb/cockroach/storage/store.go:964 +0x165
github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker.func1(0xc4201ce000, 0xc4202c3c40)
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:187 +0x7d
created by github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:188 +0x66
goroutine 1132 [select]:
github.com/cockroachdb/cockroach/storage.(*Store).startGossip.func1()
/go/src/github.com/cockroachdb/cockroach/storage/store.go:1039 +0x314
github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker.func1(0xc4201ce000, 0xc42065a900)
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:187 +0x7d
created by github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:188 +0x66
goroutine 1133 [select]:
github.com/cockroachdb/cockroach/storage.(*Store).startGossip.func2()
/go/src/github.com/cockroachdb/cockroach/storage/store.go:1058 +0x314
github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker.func1(0xc4201ce000, 0xc42065a910)
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:187 +0x7d
created by github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:188 +0x66
goroutine 1154 [select]:
github.com/cockroachdb/cockroach/storage.(*baseQueue).processLoop.func1()
/go/src/github.com/cockroachdb/cockroach/storage/queue.go:418 +0x2cc
github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker.func1(0xc4201ce000, 0xc42053a000)
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:187 +0x7d
created by github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:188 +0x66
goroutine 1155 [select]:
github.com/cockroachdb/cockroach/storage.(*Replica).redirectOnOrAcquireLease(0xc420158fc0, 0x7f6af88dea68, 0xc420154120, 0x12)
/go/src/github.com/cockroachdb/cockroach/storage/replica.go:750 +0x4ec
github.com/cockroachdb/cockroach/storage.(*baseQueue).processReplica(0xc42022e790, 0xc420158fc0, 0xc42067e440, 0x0, 0x0)
/go/src/github.com/cockroachdb/cockroach/storage/queue.go:489 +0x563
github.com/cockroachdb/cockroach/storage.(*baseQueue).processLoop.func1.2()
/go/src/github.com/cockroachdb/cockroach/storage/queue.go:439 +0x58
github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunTask(0xc4201ce000, 0xc420577e78, 0x0, 0x0)
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:215 +0x100
github.com/cockroachdb/cockroach/storage.(*baseQueue).processLoop.func1()
/go/src/github.com/cockroachdb/cockroach/storage/queue.go:443 +0x296
github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker.func1(0xc4201ce000, 0xc42053a020)
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:187 +0x7d
created by github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:188 +0x66
goroutine 1156 [select]:
github.com/cockroachdb/cockroach/storage.(*baseQueue).processLoop.func1()
/go/src/github.com/cockroachdb/cockroach/storage/queue.go:418 +0x2cc
github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker.func1(0xc4201ce000, 0xc42053a040)
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:187 +0x7d
created by github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:188 +0x66
goroutine 1157 [select]:
github.com/cockroachdb/cockroach/storage.(*baseQueue).processLoop.func1()
/go/src/github.com/cockroachdb/cockroach/storage/queue.go:418 +0x2cc
github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker.func1(0xc4201ce000, 0xc42053a060)
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:187 +0x7d
created by github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:188 +0x66
goroutine 1158 [select]:
github.com/cockroachdb/cockroach/storage.(*baseQueue).processLoop.func1()
/go/src/github.com/cockroachdb/cockroach/storage/queue.go:418 +0x2cc
github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker.func1(0xc4201ce000, 0xc42053a080)
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:187 +0x7d
created by github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:188 +0x66
goroutine 1159 [select]:
github.com/cockroachdb/cockroach/storage.(*baseQueue).processLoop.func1()
/go/src/github.com/cockroachdb/cockroach/storage/queue.go:418 +0x2cc
github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker.func1(0xc4201ce000, 0xc42053a0a0)
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:187 +0x7d
created by github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:188 +0x66
goroutine 1160 [select]:
github.com/cockroachdb/cockroach/storage.(*replicaScanner).waitAndProcess(0xc42023eb00, 0xecf66d54b, 0xc437ee100e, 0x24a99c0, 0xc42067e440, 0xc4201ce000, 0xc4200b2240, 0xc4205126c8)
/go/src/github.com/cockroachdb/cockroach/storage/scanner.go:201 +0x237
github.com/cockroachdb/cockroach/storage.(*replicaScanner).scanLoop.func1.1(0xc4200b2240, 0xc4202c4db0)
/go/src/github.com/cockroachdb/cockroach/storage/scanner.go:259 +0x7c
github.com/cockroachdb/cockroach/storage.(*storeRangeSet).Visit(0xc4202c4e70, 0xc4200167c0)
/go/src/github.com/cockroachdb/cockroach/storage/store.go:246 +0x21b
github.com/cockroachdb/cockroach/storage.(*replicaScanner).scanLoop.func1()
/go/src/github.com/cockroachdb/cockroach/storage/scanner.go:261 +0x233
github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker.func1(0xc4201ce000, 0xc42053a0c0)
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:187 +0x7d
created by github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:188 +0x66
goroutine 1136 [select]:
github.com/cockroachdb/cockroach/storage.(*baseQueue).processLoop.func1()
/go/src/github.com/cockroachdb/cockroach/storage/queue.go:418 +0x2cc
github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker.func1(0xc4201ce000, 0xc4202c3c60)
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:187 +0x7d
created by github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:188 +0x66
goroutine 1137 [select]:
github.com/cockroachdb/cockroach/storage.(*replicaScanner).waitAndProcess(0xc42023eb80, 0xecf66d54b, 0xc43806555d, 0x24a99c0, 0xc42067e440, 0xc4201ce000, 0xc420158b40, 0xc420483ec8)
/go/src/github.com/cockroachdb/cockroach/storage/scanner.go:201 +0x237
github.com/cockroachdb/cockroach/storage.(*replicaScanner).scanLoop.func1.1(0xc420158b40, 0xc4202c4db0)
/go/src/github.com/cockroachdb/cockroach/storage/scanner.go:259 +0x7c
github.com/cockroachdb/cockroach/storage.(*storeRangeSet).Visit(0xc4202c5260, 0xc42067e800)
/go/src/github.com/cockroachdb/cockroach/storage/store.go:246 +0x21b
github.com/cockroachdb/cockroach/storage.(*replicaScanner).scanLoop.func1()
/go/src/github.com/cockroachdb/cockroach/storage/scanner.go:261 +0x233
github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker.func1(0xc4201ce000, 0xc4202c3c80)
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:187 +0x7d
created by github.com/cockroachdb/cockroach/util/stop.(*Stopper).RunWorker
/go/src/github.com/cockroachdb/cockroach/util/stop/stopper.go:188 +0x66
ERROR: exit status 2
```
Run Details:
```
1 runs completed, 1 failures, over 1s
FAIL
```
Please assign, take a look and update the issue accordingly. | non_priority | stress failed test in cockroach storage storage test testacceptsunsplitranges binary cockroach static tests tar gz sha stress build found a failed test run testacceptsunsplitranges gossip gossip go initial resolvers gossip gossip go no resolvers found use join to specify a connected node gossip gossip go nodeid set to storage engine rocksdb go opening in memory rocksdb instance gossip gossip go nodeid set to gossip gossip go nodeid set to storage replica trigger go new range lease replica utc following replica utc panic runtime error invalid memory address or nil pointer dereference panic runtime error invalid memory address or nil pointer dereference goroutine panic usr local go src runtime panic go github com cockroachdb cockroach util stop stopper recover go src github com cockroachdb cockroach util stop stopper go panic usr local go src runtime panic go github com coreos etcd raft raft appendentry go src github com coreos etcd raft raft go github com coreos etcd raft raft becomeleader go src github com coreos etcd raft raft go github com coreos etcd raft raft campaign go src github com coreos etcd raft raft go github com coreos etcd raft raft step go src github com coreos etcd raft raft go github com coreos etcd raft rawnode campaign go src github com coreos etcd raft rawnode go github com cockroachdb cockroach storage replica withraftgrouplocked go src github com cockroachdb cockroach storage replica go github com cockroachdb cockroach storage defaultproposeraftcommandlocked go src github com cockroachdb cockroach storage replica go github com cockroachdb cockroach storage replica proposependingcmdlocked go src github com cockroachdb cockroach storage replica go github com cockroachdb cockroach storage replica proposeraftcommand go src github com cockroachdb cockroach storage replica go github com cockroachdb cockroach storage pendingleaserequest initorjoinrequest go src github com cockroachdb cockroach storage replica range lease go github com cockroachdb cockroach util stop stopper runasynctask go src github com cockroachdb cockroach util stop stopper go created by github com cockroachdb cockroach util stop stopper runasynctask go src github com cockroachdb cockroach util stop stopper go goroutine testing t run usr local go src testing testing go testing runtests usr local go src testing testing go testing trunner usr local go src testing testing go testing runtests usr local go src testing testing go testing m run usr local go src testing testing go github com cockroachdb cockroach storage test testmain go src github com cockroachdb cockroach storage main test go main main github com cockroachdb cockroach storage test testmain go goroutine runtime goexit usr local go src runtime asm s goroutine github com cockroachdb cockroach util log loggingt flushdaemon go src github com cockroachdb cockroach util log clog go created by github com cockroachdb cockroach util log init go src github com cockroachdb cockroach util log clog go goroutine sync runtime semacquire usr local go src runtime sema go sync mutex lock usr local go src sync mutex go sync pool getslow usr local go src sync pool go sync pool get usr local go src sync pool go fmt newprinter usr local go src fmt print go fmt fprintf usr local go src fmt print go github com cockroachdb cockroach util encoding prettyprintvalue go src github com cockroachdb cockroach util encoding encoding go github com cockroachdb cockroach keys decodekeyprint go src github com cockroachdb cockroach keys printer go github com cockroachdb cockroach keys prettyprintinternal go src github com cockroachdb cockroach keys printer go github com cockroachdb cockroach keys prettyprint go src github com cockroachdb cockroach keys printer go github com cockroachdb cockroach roachpb key string go src github com cockroachdb cockroach roachpb data go github com cockroachdb cockroach roachpb rkey string go src github com cockroachdb cockroach roachpb data go github com cockroachdb cockroach roachpb rkey string fmt pp handlemethods usr local go src fmt print go fmt pp printarg usr local go src fmt print go fmt pp doprintf usr local go src fmt print go fmt sprintf usr local go src fmt print go github com cockroachdb cockroach storage atomicrangedesc string go src github com cockroachdb cockroach storage replica go fmt pp handlemethods usr local go src fmt print go fmt pp printarg usr local go src fmt print go fmt pp doprintf usr local go src fmt print go fmt sprintf usr local go src fmt print go github com cockroachdb cockroach storage replica string go src github com cockroachdb cockroach storage replica go fmt pp handlemethods usr local go src fmt print go fmt pp printarg usr local go src fmt print go fmt pp doprintf usr local go src fmt print go fmt fprintf usr local go src fmt print go github com cockroachdb cockroach util log eventinternal go src github com cockroachdb cockroach util log trace go github com cockroachdb cockroach util log veventf go src github com cockroachdb cockroach util log trace go github com cockroachdb cockroach storage basequeue maybeadd go src github com cockroachdb cockroach storage queue go github com cockroachdb cockroach storage testacceptsunsplitranges go src github com cockroachdb cockroach storage queue test go testing trunner usr local go src testing testing go created by testing t run usr local go src testing testing go goroutine github com cockroachdb cockroach storage raftscheduler worker go src github com cockroachdb cockroach storage scheduler go github com cockroachdb cockroach storage raftscheduler start go src github com cockroachdb cockroach storage scheduler go github com cockroachdb cockroach util stop stopper runworker go src github com cockroachdb cockroach util stop stopper go created by github com cockroachdb cockroach util stop stopper runworker go src github com cockroachdb cockroach util stop stopper go goroutine github com cockroachdb cockroach storage bookie start go src github com cockroachdb cockroach storage reservation go github com cockroachdb cockroach util stop stopper runworker go src github com cockroachdb cockroach util stop stopper go created by github com cockroachdb cockroach util stop stopper runworker go src github com cockroachdb cockroach util stop stopper go goroutine github com cockroachdb cockroach rpc newcontext go src github com cockroachdb cockroach rpc context go github com cockroachdb cockroach util stop stopper runworker go src github com cockroachdb cockroach util stop stopper go created by github com cockroachdb cockroach util stop stopper runworker go src github com cockroachdb cockroach util stop stopper go goroutine github com cockroachdb cockroach storage engine rocksdb open go src github com cockroachdb cockroach storage engine rocksdb go created by github com cockroachdb cockroach storage engine rocksdb open go src github com cockroachdb cockroach storage engine rocksdb go goroutine github com cockroachdb cockroach storage storepool start go src github com cockroachdb cockroach storage store pool go github com cockroachdb cockroach util stop stopper runworker go src github com cockroachdb cockroach util stop stopper go created by github com cockroachdb cockroach util stop stopper runworker go src github com cockroachdb cockroach util stop stopper go goroutine github com cockroachdb cockroach storage raftscheduler worker go src github com cockroachdb cockroach storage scheduler go github com cockroachdb cockroach storage raftscheduler start go src github com cockroachdb cockroach storage scheduler go github com cockroachdb cockroach util stop stopper runworker go src github com cockroachdb cockroach util stop stopper go created by github com cockroachdb cockroach util stop stopper runworker go src github com cockroachdb cockroach util stop stopper go goroutine github com cockroachdb cockroach storage raftscheduler worker go src github com cockroachdb cockroach storage scheduler go github com cockroachdb cockroach storage raftscheduler start go src github com cockroachdb cockroach storage scheduler go github com cockroachdb cockroach util stop stopper runworker go src github com cockroachdb cockroach util stop stopper go created by github com cockroachdb cockroach util stop stopper runworker go src github com cockroachdb cockroach util stop stopper go goroutine github com cockroachdb cockroach storage raftscheduler worker go src github com cockroachdb cockroach storage scheduler go github com cockroachdb cockroach storage raftscheduler start go src github com cockroachdb cockroach storage scheduler go github com cockroachdb cockroach util stop stopper runworker go src github com cockroachdb cockroach util stop stopper go created by github com cockroachdb cockroach util stop stopper runworker go src github com cockroachdb cockroach util stop stopper go goroutine github com cockroachdb cockroach storage raftscheduler worker go src github com cockroachdb cockroach storage scheduler go github com cockroachdb cockroach storage raftscheduler start go src github com cockroachdb cockroach storage scheduler go github com cockroachdb cockroach util stop stopper runworker go src github com cockroachdb cockroach util stop stopper go created by github com cockroachdb cockroach util stop stopper runworker go src github com cockroachdb cockroach util stop stopper go goroutine github com cockroachdb cockroach storage raftscheduler worker go src github com cockroachdb cockroach storage scheduler go github com cockroachdb cockroach storage raftscheduler start go src github com cockroachdb cockroach storage scheduler go github com cockroachdb cockroach util stop stopper runworker go src github com cockroachdb cockroach util stop stopper go created by github com cockroachdb cockroach util stop stopper runworker go src github com cockroachdb cockroach util stop stopper go goroutine github com cockroachdb cockroach storage raftscheduler worker go src github com cockroachdb cockroach storage scheduler go github com cockroachdb cockroach storage raftscheduler start go src github com cockroachdb cockroach storage scheduler go github com cockroachdb cockroach util stop stopper runworker go src github com cockroachdb cockroach util stop stopper go created by github com cockroachdb cockroach util stop stopper runworker go src github com cockroachdb cockroach util stop stopper go goroutine github com cockroachdb cockroach storage raftscheduler worker go src github com cockroachdb cockroach storage scheduler go github com cockroachdb cockroach storage raftscheduler start go src github com cockroachdb cockroach storage scheduler go github com cockroachdb cockroach util stop stopper runworker go src github com cockroachdb cockroach util stop stopper go created by github com cockroachdb cockroach util stop stopper runworker go src github com cockroachdb cockroach util stop stopper go goroutine sync runtime semacquire usr local go src runtime sema go sync mutex lock usr local go src sync mutex go github com cockroachdb cockroach storage basequeue pop go src github com cockroachdb cockroach storage queue go github com cockroachdb cockroach storage basequeue processloop go src github com cockroachdb cockroach storage queue go github com cockroachdb cockroach util stop stopper runworker go src github com cockroachdb cockroach util stop stopper go created by github com cockroachdb cockroach util stop stopper runworker go src github com cockroachdb cockroach util stop stopper go goroutine github com cockroachdb cockroach storage raftscheduler worker go src github com cockroachdb cockroach storage scheduler go github com cockroachdb cockroach storage raftscheduler start go src github com cockroachdb cockroach storage scheduler go github com cockroachdb cockroach util stop stopper runworker go src github com cockroachdb cockroach util stop stopper go created by github com cockroachdb cockroach util stop stopper runworker go src github com cockroachdb cockroach util stop stopper go goroutine github com cockroachdb cockroach storage raftscheduler worker go src github com cockroachdb cockroach storage scheduler go github com cockroachdb cockroach storage raftscheduler start go src github com cockroachdb cockroach storage scheduler go github com cockroachdb cockroach util stop stopper runworker go src github com cockroachdb cockroach util stop stopper go created by github com cockroachdb cockroach util stop stopper runworker go src github com cockroachdb cockroach util stop stopper go goroutine github com cockroachdb cockroach storage raftscheduler worker go src github com cockroachdb cockroach storage scheduler go github com cockroachdb cockroach storage raftscheduler start go src github com cockroachdb cockroach storage scheduler go github com cockroachdb cockroach util stop stopper runworker go src github com cockroachdb cockroach util stop stopper go created by github com cockroachdb cockroach util stop stopper runworker go src github com cockroachdb cockroach util stop stopper go goroutine github com cockroachdb cockroach storage raftscheduler worker go src github com cockroachdb cockroach storage scheduler go github com cockroachdb cockroach storage raftscheduler start go src github com cockroachdb cockroach storage scheduler go github com cockroachdb cockroach util stop stopper runworker go src github com cockroachdb cockroach util stop stopper go created by github com cockroachdb cockroach util stop stopper runworker go src github com cockroachdb cockroach util stop stopper go goroutine github com cockroachdb cockroach storage raftscheduler worker go src github com cockroachdb cockroach storage scheduler go github com cockroachdb cockroach storage raftscheduler start go src github com cockroachdb cockroach storage scheduler go github com cockroachdb cockroach util stop stopper runworker go src github com cockroachdb cockroach util stop stopper go created by github com cockroachdb cockroach util stop stopper runworker go src github com cockroachdb cockroach util stop stopper go goroutine github com cockroachdb cockroach storage raftscheduler worker go src github com cockroachdb cockroach storage scheduler go github com cockroachdb cockroach storage raftscheduler start go src github com cockroachdb cockroach storage scheduler go github com cockroachdb cockroach util stop stopper runworker go src github com cockroachdb cockroach util stop stopper go created by github com cockroachdb cockroach util stop stopper runworker go src github com cockroachdb cockroach util stop stopper go goroutine github com cockroachdb cockroach storage raftscheduler worker go src github com cockroachdb cockroach storage scheduler go github com cockroachdb cockroach storage raftscheduler start go src github com cockroachdb cockroach storage scheduler go github com cockroachdb cockroach util stop stopper runworker go src github com cockroachdb cockroach util stop stopper go created by github com cockroachdb cockroach util stop stopper runworker go src github com cockroachdb cockroach util stop stopper go goroutine github com cockroachdb cockroach storage raftscheduler worker go src github com cockroachdb cockroach storage scheduler go github com cockroachdb cockroach storage raftscheduler start go src github com cockroachdb cockroach storage scheduler go github com cockroachdb cockroach util stop stopper runworker go src github com cockroachdb cockroach util stop stopper go created by github com cockroachdb cockroach util stop stopper runworker go src github com cockroachdb cockroach util stop stopper go goroutine github com cockroachdb cockroach storage raftscheduler worker go src github com cockroachdb cockroach storage scheduler go github com cockroachdb cockroach storage raftscheduler start go src github com cockroachdb cockroach storage scheduler go github com cockroachdb cockroach util stop stopper runworker go src github com cockroachdb cockroach util stop stopper go created by github com cockroachdb cockroach util stop stopper runworker go src github com cockroachdb cockroach util stop stopper go goroutine github com cockroachdb cockroach storage raftscheduler worker go src github com cockroachdb cockroach storage scheduler go github com cockroachdb cockroach storage raftscheduler start go src github com cockroachdb cockroach storage scheduler go github com cockroachdb cockroach util stop stopper runworker go src github com cockroachdb cockroach util stop stopper go created by github com cockroachdb cockroach util stop stopper runworker go src github com cockroachdb cockroach util stop stopper go goroutine github com cockroachdb cockroach storage raftscheduler worker go src github com cockroachdb cockroach storage scheduler go github com cockroachdb cockroach storage raftscheduler start go src github com cockroachdb cockroach storage scheduler go github com cockroachdb cockroach util stop stopper runworker go src github com cockroachdb cockroach util stop stopper go created by github com cockroachdb cockroach util stop stopper runworker go src github com cockroachdb cockroach util stop stopper go goroutine github com cockroachdb cockroach storage raftscheduler worker go src github com cockroachdb cockroach storage scheduler go github com cockroachdb cockroach storage raftscheduler start go src github com cockroachdb cockroach storage scheduler go github com cockroachdb cockroach util stop stopper runworker go src github com cockroachdb cockroach util stop stopper go created by github com cockroachdb cockroach util stop stopper runworker go src github com cockroachdb cockroach util stop stopper go goroutine github com cockroachdb cockroach storage raftscheduler worker go src github com cockroachdb cockroach storage scheduler go github com cockroachdb cockroach storage raftscheduler start go src github com cockroachdb cockroach storage scheduler go github com cockroachdb cockroach util stop stopper runworker go src github com cockroachdb cockroach util stop stopper go created by github com cockroachdb cockroach util stop stopper runworker go src github com cockroachdb cockroach util stop stopper go goroutine github com cockroachdb cockroach storage raftscheduler worker go src github com cockroachdb cockroach storage scheduler go github com cockroachdb cockroach storage raftscheduler start go src github com cockroachdb cockroach storage scheduler go github com cockroachdb cockroach util stop stopper runworker go src github com cockroachdb cockroach util stop stopper go created by github com cockroachdb cockroach util stop stopper runworker go src github com cockroachdb cockroach util stop stopper go goroutine github com cockroachdb cockroach storage raftscheduler worker go src github com cockroachdb cockroach storage scheduler go github com cockroachdb cockroach storage raftscheduler start go src github com cockroachdb cockroach storage scheduler go github com cockroachdb cockroach util stop stopper runworker go src github com cockroachdb cockroach util stop stopper go created by github com cockroachdb cockroach util stop stopper runworker go src github com cockroachdb cockroach util stop stopper go goroutine github com cockroachdb cockroach storage raftscheduler worker go src github com cockroachdb cockroach storage scheduler go github com cockroachdb cockroach storage raftscheduler start go src github com cockroachdb cockroach storage scheduler go github com cockroachdb cockroach util stop stopper runworker go src github com cockroachdb cockroach util stop stopper go created by github com cockroachdb cockroach util stop stopper runworker go src github com cockroachdb cockroach util stop stopper go goroutine github com cockroachdb cockroach storage raftscheduler worker go src github com cockroachdb cockroach storage scheduler go github com cockroachdb cockroach storage raftscheduler start go src github com cockroachdb cockroach storage scheduler go github com cockroachdb cockroach util stop stopper runworker go src github com cockroachdb cockroach util stop stopper go created by github com cockroachdb cockroach util stop stopper runworker go src github com cockroachdb cockroach util stop stopper go goroutine github com cockroachdb cockroach storage raftscheduler worker go src github com cockroachdb cockroach storage scheduler go github com cockroachdb cockroach storage raftscheduler start go src github com cockroachdb cockroach storage scheduler go github com cockroachdb cockroach util stop stopper runworker go src github com cockroachdb cockroach util stop stopper go created by github com cockroachdb cockroach util stop stopper runworker go src github com cockroachdb cockroach util stop stopper go goroutine github com cockroachdb cockroach storage raftscheduler worker go src github com cockroachdb cockroach storage scheduler go github com cockroachdb cockroach storage raftscheduler start go src github com cockroachdb cockroach storage scheduler go github com cockroachdb cockroach util stop stopper runworker go src github com cockroachdb cockroach util stop stopper go created by github com cockroachdb cockroach util stop stopper runworker go src github com cockroachdb cockroach util stop stopper go goroutine github com cockroachdb cockroach storage raftscheduler worker go src github com cockroachdb cockroach storage scheduler go github com cockroachdb cockroach storage raftscheduler start go src github com cockroachdb cockroach storage scheduler go github com cockroachdb cockroach util stop stopper runworker go src github com cockroachdb cockroach util stop stopper go created by github com cockroachdb cockroach util stop stopper runworker go src github com cockroachdb cockroach util stop stopper go goroutine github com cockroachdb cockroach storage raftscheduler worker go src github com cockroachdb cockroach storage scheduler go github com cockroachdb cockroach storage raftscheduler start go src github com cockroachdb cockroach storage scheduler go github com cockroachdb cockroach util stop stopper runworker go src github com cockroachdb cockroach util stop stopper go created by github com cockroachdb cockroach util stop stopper runworker go src github com cockroachdb cockroach util stop stopper go goroutine github com cockroachdb cockroach storage raftscheduler worker go src github com cockroachdb cockroach storage scheduler go github com cockroachdb cockroach storage raftscheduler start go src github com cockroachdb cockroach storage scheduler go github com cockroachdb cockroach util stop stopper runworker go src github com cockroachdb cockroach util stop stopper go created by github com cockroachdb cockroach util stop stopper runworker go src github com cockroachdb cockroach util stop stopper go goroutine github com cockroachdb cockroach storage raftscheduler worker go src github com cockroachdb cockroach storage scheduler go github com cockroachdb cockroach storage raftscheduler start go src github com cockroachdb cockroach storage scheduler go github com cockroachdb cockroach util stop stopper runworker go src github com cockroachdb cockroach util stop stopper go created by github com cockroachdb cockroach util stop stopper runworker go src github com cockroachdb cockroach util stop stopper go goroutine github com cockroachdb cockroach storage raftscheduler worker go src github com cockroachdb cockroach storage scheduler go github com cockroachdb cockroach storage raftscheduler start go src github com cockroachdb cockroach storage scheduler go github com cockroachdb cockroach util stop stopper runworker go src github com cockroachdb cockroach util stop stopper go created by github com cockroachdb cockroach util stop stopper runworker go src github com cockroachdb cockroach util stop stopper go goroutine github com cockroachdb cockroach storage store rafttickloop go src github com cockroachdb cockroach storage store go github com cockroachdb cockroach util stop stopper runworker go src github com cockroachdb cockroach util stop stopper go created by github com cockroachdb cockroach util stop stopper runworker go src github com cockroachdb cockroach util stop stopper go goroutine github com cockroachdb cockroach storage store raftsnapshotstatusloop go src github com cockroachdb cockroach storage store go github com cockroachdb cockroach util stop stopper runworker go src github com cockroachdb cockroach util stop stopper go created by github com cockroachdb cockroach util stop stopper runworker go src github com cockroachdb cockroach util stop stopper go goroutine github com cockroachdb cockroach storage store start go src github com cockroachdb cockroach storage store go github com cockroachdb cockroach util stop stopper runworker go src github com cockroachdb cockroach util stop stopper go created by github com cockroachdb cockroach util stop stopper runworker go src github com cockroachdb cockroach util stop stopper go goroutine github com cockroachdb cockroach storage store startgossip go src github com cockroachdb cockroach storage store go github com cockroachdb cockroach util stop stopper runworker go src github com cockroachdb cockroach util stop stopper go created by github com cockroachdb cockroach util stop stopper runworker go src github com cockroachdb cockroach util stop stopper go goroutine github com cockroachdb cockroach storage store startgossip go src github com cockroachdb cockroach storage store go github com cockroachdb cockroach util stop stopper runworker go src github com cockroachdb cockroach util stop stopper go created by github com cockroachdb cockroach util stop stopper runworker go src github com cockroachdb cockroach util stop stopper go goroutine github com cockroachdb cockroach storage basequeue processloop go src github com cockroachdb cockroach storage queue go github com cockroachdb cockroach util stop stopper runworker go src github com cockroachdb cockroach util stop stopper go created by github com cockroachdb cockroach util stop stopper runworker go src github com cockroachdb cockroach util stop stopper go goroutine github com cockroachdb cockroach storage replica redirectonoracquirelease go src github com cockroachdb cockroach storage replica go github com cockroachdb cockroach storage basequeue processreplica go src github com cockroachdb cockroach storage queue go github com cockroachdb cockroach storage basequeue processloop go src github com cockroachdb cockroach storage queue go github com cockroachdb cockroach util stop stopper runtask go src github com cockroachdb cockroach util stop stopper go github com cockroachdb cockroach storage basequeue processloop go src github com cockroachdb cockroach storage queue go github com cockroachdb cockroach util stop stopper runworker go src github com cockroachdb cockroach util stop stopper go created by github com cockroachdb cockroach util stop stopper runworker go src github com cockroachdb cockroach util stop stopper go goroutine github com cockroachdb cockroach storage basequeue processloop go src github com cockroachdb cockroach storage queue go github com cockroachdb cockroach util stop stopper runworker go src github com cockroachdb cockroach util stop stopper go created by github com cockroachdb cockroach util stop stopper runworker go src github com cockroachdb cockroach util stop stopper go goroutine github com cockroachdb cockroach storage basequeue processloop go src github com cockroachdb cockroach storage queue go github com cockroachdb cockroach util stop stopper runworker go src github com cockroachdb cockroach util stop stopper go created by github com cockroachdb cockroach util stop stopper runworker go src github com cockroachdb cockroach util stop stopper go goroutine github com cockroachdb cockroach storage basequeue processloop go src github com cockroachdb cockroach storage queue go github com cockroachdb cockroach util stop stopper runworker go src github com cockroachdb cockroach util stop stopper go created by github com cockroachdb cockroach util stop stopper runworker go src github com cockroachdb cockroach util stop stopper go goroutine github com cockroachdb cockroach storage basequeue processloop go src github com cockroachdb cockroach storage queue go github com cockroachdb cockroach util stop stopper runworker go src github com cockroachdb cockroach util stop stopper go created by github com cockroachdb cockroach util stop stopper runworker go src github com cockroachdb cockroach util stop stopper go goroutine github com cockroachdb cockroach storage replicascanner waitandprocess go src github com cockroachdb cockroach storage scanner go github com cockroachdb cockroach storage replicascanner scanloop go src github com cockroachdb cockroach storage scanner go github com cockroachdb cockroach storage storerangeset visit go src github com cockroachdb cockroach storage store go github com cockroachdb cockroach storage replicascanner scanloop go src github com cockroachdb cockroach storage scanner go github com cockroachdb cockroach util stop stopper runworker go src github com cockroachdb cockroach util stop stopper go created by github com cockroachdb cockroach util stop stopper runworker go src github com cockroachdb cockroach util stop stopper go goroutine github com cockroachdb cockroach storage basequeue processloop go src github com cockroachdb cockroach storage queue go github com cockroachdb cockroach util stop stopper runworker go src github com cockroachdb cockroach util stop stopper go created by github com cockroachdb cockroach util stop stopper runworker go src github com cockroachdb cockroach util stop stopper go goroutine github com cockroachdb cockroach storage replicascanner waitandprocess go src github com cockroachdb cockroach storage scanner go github com cockroachdb cockroach storage replicascanner scanloop go src github com cockroachdb cockroach storage scanner go github com cockroachdb cockroach storage storerangeset visit go src github com cockroachdb cockroach storage store go github com cockroachdb cockroach storage replicascanner scanloop go src github com cockroachdb cockroach storage scanner go github com cockroachdb cockroach util stop stopper runworker go src github com cockroachdb cockroach util stop stopper go created by github com cockroachdb cockroach util stop stopper runworker go src github com cockroachdb cockroach util stop stopper go error exit status run details runs completed failures over fail please assign take a look and update the issue accordingly | 0 |
345,585 | 24,866,306,316 | IssuesEvent | 2022-10-27 12:14:26 | keptn/lifecycle-controller | https://api.github.com/repos/keptn/lifecycle-controller | opened | Implementi the documentation structure | documentation | ### Discussed in https://github.com/keptn/lifecycle-controller/discussions/141
<div type='discussions-op-text'>
<sup>Originally posted by **oleg-nenashev** October 11, 2022</sup>
Hello,
I propose to rework the documentation structure in the following way
* README files - top level overviews and quick-start bits. The rest will go to special pages under “/doc” (see below)
* Top-level README
* “KLC in a nutshell” - short overview
* Getting started - Installing and trying out
* Function Runtime README
* KLC Operator README
* ROADMAP.md - Overview of the project’s direction and state. Most of the content should be on the linked GitHub project dashboard
* CONTRIBUTING.md - Top-level contributing overview. How to get started, how to find issues, process and governance. The rest will be linked to developer guidelines
* “/doc” - Main holder for the documentation. The documentation will be written in Markdown and grouped by the persona
* “spec/” - formal specifications associated with the project, including CRDs
* “admin-guide/” - content for administrators who install and maintainKeptn Lifecycle Controller: Installation guide, Upgrading Keptn, Architecture, Troubleshooting, etc.
* “user-guide/” - content specific for teams working on projects operated by Keptn, including using Keptn and integrations. Defining Keptn projects, Integrating with KLC, Writing Keptn pre- and post-deployment tasks., eveloping Keptn functions
* “developer-guide/” - Set of wiki-ish documentation specific to development of the Keptn Lifecycle Controller itself. Acts as CONTRIBUTING.md extension
See this google doc for the detailed content of each section: https://docs.google.com/document/d/1eVMwZ6EqIKlmui3c7suz_pt9hSDfq_5eiwR8KT9Acw4/edit?usp=sharing
</div> | 1.0 | Implementi the documentation structure - ### Discussed in https://github.com/keptn/lifecycle-controller/discussions/141
<div type='discussions-op-text'>
<sup>Originally posted by **oleg-nenashev** October 11, 2022</sup>
Hello,
I propose to rework the documentation structure in the following way
* README files - top level overviews and quick-start bits. The rest will go to special pages under “/doc” (see below)
* Top-level README
* “KLC in a nutshell” - short overview
* Getting started - Installing and trying out
* Function Runtime README
* KLC Operator README
* ROADMAP.md - Overview of the project’s direction and state. Most of the content should be on the linked GitHub project dashboard
* CONTRIBUTING.md - Top-level contributing overview. How to get started, how to find issues, process and governance. The rest will be linked to developer guidelines
* “/doc” - Main holder for the documentation. The documentation will be written in Markdown and grouped by the persona
* “spec/” - formal specifications associated with the project, including CRDs
* “admin-guide/” - content for administrators who install and maintainKeptn Lifecycle Controller: Installation guide, Upgrading Keptn, Architecture, Troubleshooting, etc.
* “user-guide/” - content specific for teams working on projects operated by Keptn, including using Keptn and integrations. Defining Keptn projects, Integrating with KLC, Writing Keptn pre- and post-deployment tasks., eveloping Keptn functions
* “developer-guide/” - Set of wiki-ish documentation specific to development of the Keptn Lifecycle Controller itself. Acts as CONTRIBUTING.md extension
See this google doc for the detailed content of each section: https://docs.google.com/document/d/1eVMwZ6EqIKlmui3c7suz_pt9hSDfq_5eiwR8KT9Acw4/edit?usp=sharing
</div> | non_priority | implementi the documentation structure discussed in originally posted by oleg nenashev october hello i propose to rework the documentation structure in the following way readme files top level overviews and quick start bits the rest will go to special pages under “ doc” see below top level readme “klc in a nutshell” short overview getting started installing and trying out function runtime readme klc operator readme roadmap md overview of the project’s direction and state most of the content should be on the linked github project dashboard contributing md top level contributing overview how to get started how to find issues process and governance the rest will be linked to developer guidelines “ doc” main holder for the documentation the documentation will be written in markdown and grouped by the persona “spec ” formal specifications associated with the project including crds “admin guide ” content for administrators who install and maintainkeptn lifecycle controller installation guide upgrading keptn architecture troubleshooting etc “user guide ” content specific for teams working on projects operated by keptn including using keptn and integrations defining keptn projects integrating with klc writing keptn pre and post deployment tasks eveloping keptn functions “developer guide ” set of wiki ish documentation specific to development of the keptn lifecycle controller itself acts as contributing md extension see this google doc for the detailed content of each section | 0 |
394,116 | 27,021,207,744 | IssuesEvent | 2023-02-11 02:41:46 | JustBrandonLim/ICT2106_P2_Project | https://api.github.com/repos/JustBrandonLim/ICT2106_P2_Project | closed | 1.2 Team Class Diagram Start: 10/01/23 | End: 27/01/23 | documentation | Start: 10/01/23 | End: 27/01/23
- Creation of Team Class Diagram
- Linking of Class Diagram with other Teams | 1.0 | 1.2 Team Class Diagram Start: 10/01/23 | End: 27/01/23 - Start: 10/01/23 | End: 27/01/23
- Creation of Team Class Diagram
- Linking of Class Diagram with other Teams | non_priority | team class diagram start end start end creation of team class diagram linking of class diagram with other teams | 0 |
87,541 | 25,142,314,074 | IssuesEvent | 2022-11-10 00:37:42 | microsoft/onnxruntime | https://api.github.com/repos/microsoft/onnxruntime | closed | [Build] cmake error: list sub-command REMOVE_ITEM requires two or more arguments | build | ### Describe the issue
building on windows with cmake 3.19 fails with `list sub-command REMOVE_ITEM requires two or more arguments`
This is due to a cmake "bug" in 3.19 and lower with the `list(REMOVE_ITEM...)` command.
Seen in other projects like https://github.com/microsoft/vcpkg/pull/23410
Easy fix in forthcoming PR
### Urgency
_No response_
### Target platform
Windows (might be others)
### Build script
```
.\build.bat --update --build --skip_tests --cmake_generator "Visual Studio 16 2019" --config RelWithDebInfo --build_shared_lib --parallel --use_dml --use_cuda --cuda_home "C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v11.4" --cuda_version 11.4 --cudnn_home "C:\repos-nobackup\cudnn-windows-x86_64-8.4.1.50_cuda11.6-archive" --use_tensorrt --tensorrt_home "C:\repos-nobackup\TensorRT-8.4.1.5"
```
### Error / output
```
...
-- Protobuf compiler :
-- Protobuf includes :
-- Protobuf libraries :
-- BUILD_ONNX_PYTHON : OFF
Use flatbuffers from submodule
-- CMAKE_CUDA_COMPILER_VERSION: 11.4.152
CMake Error at onnxruntime_graph.cmake:63 (list):
list sub-command REMOVE_ITEM requires two or more arguments.
Call Stack (most recent call first):
CMakeLists.txt:2007 (include)
-- Found CUDA headers at C:/Program Files/NVIDIA GPU Computing Toolkit/CUDA/v11.4/include
-- Found TensorRT headers at C:/repos-nobackup/TensorRT-8.4.1.5/include
-- Find TensorRT libs at C:/repos-nobackup/TensorRT-8.4.1.5/lib/nvinfer.lib;C:/repos-nobackup/TensorRT-8.4.1.5/lib/nvinfer_plugin.lib
-- Configuring incomplete, errors occurred!
See also "C:/repos-nobackup/onnxruntime/build/Windows/RelWithDebInfo/CMakeFiles/CMakeOutput.log".
See also "C:/repos-nobackup/onnxruntime/build/Windows/RelWithDebInfo/CMakeFiles/CMakeError.log".
Traceback (most recent call last):
File "C:\repos-nobackup\onnxruntime\tools\ci_build\build.py", line 2744, in <module>
sys.exit(main())
File "C:\repos-nobackup\onnxruntime\tools\ci_build\build.py", line 2630, in main
generate_build_tree(
File "C:\repos-nobackup\onnxruntime\tools\ci_build\build.py", line 1240, in generate_build_tree
run_subprocess(
File "C:\repos-nobackup\onnxruntime\tools\ci_build\build.py", line 714, in run_subprocess
return run(*args, cwd=cwd, capture_stdout=capture_stdout, shell=shell, env=my_env)
File "C:\repos-nobackup\onnxruntime\tools\python\util\run.py", line 49, in run
completed_process = subprocess.run(
File "C:\python39\lib\subprocess.py", line 528, in run
raise CalledProcessError(retcode, process.args,
subprocess.CalledProcessError: Command '['C:\\Program Files\\CMake\\bin\\cmake.EXE', 'C:\\repos-nobackup\\onnxruntime\\cmake', '-Donnxruntime_RUN_ONNX_TESTS=OFF', '-Donnxruntime_GENERATE_TEST_REPORTS=ON', '-DPython_EXECUTABLE=C:\\python39\\python.exe', '-DPYTHON_EXECUTABLE=C:\\python39\\python.exe', '-Donnxruntime_USE_MIMALLOC=OFF', '-Donnxruntime_ENABLE_PYTHON=OFF', '-Donnxruntime_BUILD_CSHARP=OFF', '-Donnxruntime_BUILD_JAVA=OFF', '-Donnxruntime_BUILD_NODEJS=OFF', '-Donnxruntime_BUILD_OBJC=OFF', '-Donnxruntime_BUILD_SHARED_LIB=ON', '-Donnxruntime_BUILD_APPLE_FRAMEWORK=OFF', '-Donnxruntime_USE_DNNL=OFF', '-Donnxruntime_USE_NNAPI_BUILTIN=OFF', '-Donnxruntime_USE_RKNPU=OFF', '-Donnxruntime_USE_NUPHAR_TVM=OFF', '-Donnxruntime_USE_LLVM=OFF', '-Donnxruntime_ENABLE_MICROSOFT_INTERNAL=OFF', '-Donnxruntime_USE_VITISAI=OFF', '-Donnxruntime_USE_NUPHAR=OFF', '-Donnxruntime_USE_TENSORRT=ON', '-Donnxruntime_TENSORRT_PLACEHOLDER_BUILDER=OFF', '-Donnxruntime_USE_TVM=OFF', '-Donnxruntime_TVM_CUDA_RUNTIME=OFF', '-Donnxruntime_USE_MIGRAPHX=OFF', '-Donnxruntime_CROSS_COMPILING=OFF', '-Donnxruntime_DISABLE_CONTRIB_OPS=OFF', '-Donnxruntime_DISABLE_ML_OPS=OFF', '-Donnxruntime_DISABLE_RTTI=OFF', '-Donnxruntime_DISABLE_EXCEPTIONS=OFF', '-Donnxruntime_MINIMAL_BUILD=OFF', '-Donnxruntime_EXTENDED_MINIMAL_BUILD=OFF', '-Donnxruntime_MINIMAL_BUILD_CUSTOM_OPS=OFF', '-Donnxruntime_REDUCED_OPS_BUILD=OFF', '-Donnxruntime_ENABLE_LANGUAGE_INTEROP_OPS=OFF', '-Donnxruntime_USE_DML=ON', '-Donnxruntime_USE_WINML=OFF', '-Donnxruntime_BUILD_MS_EXPERIMENTAL_OPS=OFF', '-Donnxruntime_USE_TELEMETRY=OFF', '-Donnxruntime_ENABLE_LTO=OFF', '-Donnxruntime_USE_ACL=OFF', '-Donnxruntime_USE_ACL_1902=OFF', '-Donnxruntime_USE_ACL_1905=OFF', '-Donnxruntime_USE_ACL_1908=OFF', '-Donnxruntime_USE_ACL_2002=OFF', '-Donnxruntime_USE_ARMNN=OFF', '-Donnxruntime_ARMNN_RELU_USE_CPU=ON', '-Donnxruntime_ARMNN_BN_USE_CPU=ON', '-Donnxruntime_ENABLE_NVTX_PROFILE=OFF', '-Donnxruntime_ENABLE_TRAINING=OFF', '-Donnxruntime_ENABLE_TRAINING_OPS=OFF', '-Donnxruntime_ENABLE_TRAINING_TORCH_INTEROP=OFF', '-Donnxruntime_ENABLE_CPU_FP16_OPS=OFF', '-Donnxruntime_USE_NCCL=OFF', '-Donnxruntime_BUILD_BENCHMARKS=OFF', '-Donnxruntime_USE_ROCM=OFF', '-DOnnxruntime_GCOV_COVERAGE=OFF', '-Donnxruntime_USE_MPI=ON', '-Donnxruntime_ENABLE_MEMORY_PROFILE=OFF', '-Donnxruntime_ENABLE_CUDA_LINE_NUMBER_INFO=OFF', '-Donnxruntime_BUILD_WEBASSEMBLY=OFF', '-Donnxruntime_BUILD_WEBASSEMBLY_STATIC_LIB=OFF', '-Donnxruntime_ENABLE_WEBASSEMBLY_EXCEPTION_CATCHING=ON', '-Donnxruntime_ENABLE_WEBASSEMBLY_EXCEPTION_THROWING=OFF', '-Donnxruntime_ENABLE_WEBASSEMBLY_THREADS=OFF', '-Donnxruntime_ENABLE_WEBASSEMBLY_DEBUG_INFO=OFF', '-Donnxruntime_ENABLE_WEBASSEMBLY_PROFILING=OFF', '-Donnxruntime_ENABLE_EAGER_MODE=OFF', '-Donnxruntime_ENABLE_EXTERNAL_CUSTOM_OP_SCHEMAS=OFF', '-Donnxruntime_ENABLE_CUDA_PROFILING=OFF', '-Donnxruntime_USE_XNNPACK=OFF', '-Donnxruntime_NVCC_THREADS=0', '-Donnxruntime_TENSORRT_HOME=C:\\repos-nobackup\\TensorRT-8.4.1.5', '-Donnxruntime_USE_FULL_PROTOBUF=ON', '-DProtobuf_USE_STATIC_LIBS=ON', '-Donnxruntime_DEV_MODE=ON', '-Donnxruntime_USE_CUDA=ON', '-Donnxruntime_CUDA_VERSION=11.4', '-Donnxruntime_CUDA_HOME=C:\\Program Files\\NVIDIA GPU Computing Toolkit\\CUDA\\v11.4', '-Donnxruntime_CUDNN_HOME=C:\\repos-nobackup\\cudnn-windows-x86_64-8.4.1.50_cuda11.6-archive', '-DONNX_USE_MSVC_STATIC_RUNTIME=OFF', '-Dprotobuf_MSVC_STATIC_RUNTIME=OFF', '-Dgtest_force_shared_crt=ON', '-Donnxruntime_PYBIND_EXPORT_OPSCHEMA=OFF', '-A', 'x64', '-T', 'host=x64,cuda=11.4', '-G', 'Visual Studio 16 2019', '-Donnxruntime_ENABLE_MEMLEAK_CHECKER=OFF', '-DCMAKE_BUILD_TYPE=RelWithDebInfo']' returned non-zero exit status 1
```
### Visual Studio Version
16.11.18
### GCC / Compiler Version
_No response_ | 1.0 | [Build] cmake error: list sub-command REMOVE_ITEM requires two or more arguments - ### Describe the issue
building on windows with cmake 3.19 fails with `list sub-command REMOVE_ITEM requires two or more arguments`
This is due to a cmake "bug" in 3.19 and lower with the `list(REMOVE_ITEM...)` command.
Seen in other projects like https://github.com/microsoft/vcpkg/pull/23410
Easy fix in forthcoming PR
### Urgency
_No response_
### Target platform
Windows (might be others)
### Build script
```
.\build.bat --update --build --skip_tests --cmake_generator "Visual Studio 16 2019" --config RelWithDebInfo --build_shared_lib --parallel --use_dml --use_cuda --cuda_home "C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v11.4" --cuda_version 11.4 --cudnn_home "C:\repos-nobackup\cudnn-windows-x86_64-8.4.1.50_cuda11.6-archive" --use_tensorrt --tensorrt_home "C:\repos-nobackup\TensorRT-8.4.1.5"
```
### Error / output
```
...
-- Protobuf compiler :
-- Protobuf includes :
-- Protobuf libraries :
-- BUILD_ONNX_PYTHON : OFF
Use flatbuffers from submodule
-- CMAKE_CUDA_COMPILER_VERSION: 11.4.152
CMake Error at onnxruntime_graph.cmake:63 (list):
list sub-command REMOVE_ITEM requires two or more arguments.
Call Stack (most recent call first):
CMakeLists.txt:2007 (include)
-- Found CUDA headers at C:/Program Files/NVIDIA GPU Computing Toolkit/CUDA/v11.4/include
-- Found TensorRT headers at C:/repos-nobackup/TensorRT-8.4.1.5/include
-- Find TensorRT libs at C:/repos-nobackup/TensorRT-8.4.1.5/lib/nvinfer.lib;C:/repos-nobackup/TensorRT-8.4.1.5/lib/nvinfer_plugin.lib
-- Configuring incomplete, errors occurred!
See also "C:/repos-nobackup/onnxruntime/build/Windows/RelWithDebInfo/CMakeFiles/CMakeOutput.log".
See also "C:/repos-nobackup/onnxruntime/build/Windows/RelWithDebInfo/CMakeFiles/CMakeError.log".
Traceback (most recent call last):
File "C:\repos-nobackup\onnxruntime\tools\ci_build\build.py", line 2744, in <module>
sys.exit(main())
File "C:\repos-nobackup\onnxruntime\tools\ci_build\build.py", line 2630, in main
generate_build_tree(
File "C:\repos-nobackup\onnxruntime\tools\ci_build\build.py", line 1240, in generate_build_tree
run_subprocess(
File "C:\repos-nobackup\onnxruntime\tools\ci_build\build.py", line 714, in run_subprocess
return run(*args, cwd=cwd, capture_stdout=capture_stdout, shell=shell, env=my_env)
File "C:\repos-nobackup\onnxruntime\tools\python\util\run.py", line 49, in run
completed_process = subprocess.run(
File "C:\python39\lib\subprocess.py", line 528, in run
raise CalledProcessError(retcode, process.args,
subprocess.CalledProcessError: Command '['C:\\Program Files\\CMake\\bin\\cmake.EXE', 'C:\\repos-nobackup\\onnxruntime\\cmake', '-Donnxruntime_RUN_ONNX_TESTS=OFF', '-Donnxruntime_GENERATE_TEST_REPORTS=ON', '-DPython_EXECUTABLE=C:\\python39\\python.exe', '-DPYTHON_EXECUTABLE=C:\\python39\\python.exe', '-Donnxruntime_USE_MIMALLOC=OFF', '-Donnxruntime_ENABLE_PYTHON=OFF', '-Donnxruntime_BUILD_CSHARP=OFF', '-Donnxruntime_BUILD_JAVA=OFF', '-Donnxruntime_BUILD_NODEJS=OFF', '-Donnxruntime_BUILD_OBJC=OFF', '-Donnxruntime_BUILD_SHARED_LIB=ON', '-Donnxruntime_BUILD_APPLE_FRAMEWORK=OFF', '-Donnxruntime_USE_DNNL=OFF', '-Donnxruntime_USE_NNAPI_BUILTIN=OFF', '-Donnxruntime_USE_RKNPU=OFF', '-Donnxruntime_USE_NUPHAR_TVM=OFF', '-Donnxruntime_USE_LLVM=OFF', '-Donnxruntime_ENABLE_MICROSOFT_INTERNAL=OFF', '-Donnxruntime_USE_VITISAI=OFF', '-Donnxruntime_USE_NUPHAR=OFF', '-Donnxruntime_USE_TENSORRT=ON', '-Donnxruntime_TENSORRT_PLACEHOLDER_BUILDER=OFF', '-Donnxruntime_USE_TVM=OFF', '-Donnxruntime_TVM_CUDA_RUNTIME=OFF', '-Donnxruntime_USE_MIGRAPHX=OFF', '-Donnxruntime_CROSS_COMPILING=OFF', '-Donnxruntime_DISABLE_CONTRIB_OPS=OFF', '-Donnxruntime_DISABLE_ML_OPS=OFF', '-Donnxruntime_DISABLE_RTTI=OFF', '-Donnxruntime_DISABLE_EXCEPTIONS=OFF', '-Donnxruntime_MINIMAL_BUILD=OFF', '-Donnxruntime_EXTENDED_MINIMAL_BUILD=OFF', '-Donnxruntime_MINIMAL_BUILD_CUSTOM_OPS=OFF', '-Donnxruntime_REDUCED_OPS_BUILD=OFF', '-Donnxruntime_ENABLE_LANGUAGE_INTEROP_OPS=OFF', '-Donnxruntime_USE_DML=ON', '-Donnxruntime_USE_WINML=OFF', '-Donnxruntime_BUILD_MS_EXPERIMENTAL_OPS=OFF', '-Donnxruntime_USE_TELEMETRY=OFF', '-Donnxruntime_ENABLE_LTO=OFF', '-Donnxruntime_USE_ACL=OFF', '-Donnxruntime_USE_ACL_1902=OFF', '-Donnxruntime_USE_ACL_1905=OFF', '-Donnxruntime_USE_ACL_1908=OFF', '-Donnxruntime_USE_ACL_2002=OFF', '-Donnxruntime_USE_ARMNN=OFF', '-Donnxruntime_ARMNN_RELU_USE_CPU=ON', '-Donnxruntime_ARMNN_BN_USE_CPU=ON', '-Donnxruntime_ENABLE_NVTX_PROFILE=OFF', '-Donnxruntime_ENABLE_TRAINING=OFF', '-Donnxruntime_ENABLE_TRAINING_OPS=OFF', '-Donnxruntime_ENABLE_TRAINING_TORCH_INTEROP=OFF', '-Donnxruntime_ENABLE_CPU_FP16_OPS=OFF', '-Donnxruntime_USE_NCCL=OFF', '-Donnxruntime_BUILD_BENCHMARKS=OFF', '-Donnxruntime_USE_ROCM=OFF', '-DOnnxruntime_GCOV_COVERAGE=OFF', '-Donnxruntime_USE_MPI=ON', '-Donnxruntime_ENABLE_MEMORY_PROFILE=OFF', '-Donnxruntime_ENABLE_CUDA_LINE_NUMBER_INFO=OFF', '-Donnxruntime_BUILD_WEBASSEMBLY=OFF', '-Donnxruntime_BUILD_WEBASSEMBLY_STATIC_LIB=OFF', '-Donnxruntime_ENABLE_WEBASSEMBLY_EXCEPTION_CATCHING=ON', '-Donnxruntime_ENABLE_WEBASSEMBLY_EXCEPTION_THROWING=OFF', '-Donnxruntime_ENABLE_WEBASSEMBLY_THREADS=OFF', '-Donnxruntime_ENABLE_WEBASSEMBLY_DEBUG_INFO=OFF', '-Donnxruntime_ENABLE_WEBASSEMBLY_PROFILING=OFF', '-Donnxruntime_ENABLE_EAGER_MODE=OFF', '-Donnxruntime_ENABLE_EXTERNAL_CUSTOM_OP_SCHEMAS=OFF', '-Donnxruntime_ENABLE_CUDA_PROFILING=OFF', '-Donnxruntime_USE_XNNPACK=OFF', '-Donnxruntime_NVCC_THREADS=0', '-Donnxruntime_TENSORRT_HOME=C:\\repos-nobackup\\TensorRT-8.4.1.5', '-Donnxruntime_USE_FULL_PROTOBUF=ON', '-DProtobuf_USE_STATIC_LIBS=ON', '-Donnxruntime_DEV_MODE=ON', '-Donnxruntime_USE_CUDA=ON', '-Donnxruntime_CUDA_VERSION=11.4', '-Donnxruntime_CUDA_HOME=C:\\Program Files\\NVIDIA GPU Computing Toolkit\\CUDA\\v11.4', '-Donnxruntime_CUDNN_HOME=C:\\repos-nobackup\\cudnn-windows-x86_64-8.4.1.50_cuda11.6-archive', '-DONNX_USE_MSVC_STATIC_RUNTIME=OFF', '-Dprotobuf_MSVC_STATIC_RUNTIME=OFF', '-Dgtest_force_shared_crt=ON', '-Donnxruntime_PYBIND_EXPORT_OPSCHEMA=OFF', '-A', 'x64', '-T', 'host=x64,cuda=11.4', '-G', 'Visual Studio 16 2019', '-Donnxruntime_ENABLE_MEMLEAK_CHECKER=OFF', '-DCMAKE_BUILD_TYPE=RelWithDebInfo']' returned non-zero exit status 1
```
### Visual Studio Version
16.11.18
### GCC / Compiler Version
_No response_ | non_priority | cmake error list sub command remove item requires two or more arguments describe the issue building on windows with cmake fails with list sub command remove item requires two or more arguments this is due to a cmake bug in and lower with the list remove item command seen in other projects like easy fix in forthcoming pr urgency no response target platform windows might be others build script build bat update build skip tests cmake generator visual studio config relwithdebinfo build shared lib parallel use dml use cuda cuda home c program files nvidia gpu computing toolkit cuda cuda version cudnn home c repos nobackup cudnn windows archive use tensorrt tensorrt home c repos nobackup tensorrt error output protobuf compiler protobuf includes protobuf libraries build onnx python off use flatbuffers from submodule cmake cuda compiler version cmake error at onnxruntime graph cmake list list sub command remove item requires two or more arguments call stack most recent call first cmakelists txt include found cuda headers at c program files nvidia gpu computing toolkit cuda include found tensorrt headers at c repos nobackup tensorrt include find tensorrt libs at c repos nobackup tensorrt lib nvinfer lib c repos nobackup tensorrt lib nvinfer plugin lib configuring incomplete errors occurred see also c repos nobackup onnxruntime build windows relwithdebinfo cmakefiles cmakeoutput log see also c repos nobackup onnxruntime build windows relwithdebinfo cmakefiles cmakeerror log traceback most recent call last file c repos nobackup onnxruntime tools ci build build py line in sys exit main file c repos nobackup onnxruntime tools ci build build py line in main generate build tree file c repos nobackup onnxruntime tools ci build build py line in generate build tree run subprocess file c repos nobackup onnxruntime tools ci build build py line in run subprocess return run args cwd cwd capture stdout capture stdout shell shell env my env file c repos nobackup onnxruntime tools python util run py line in run completed process subprocess run file c lib subprocess py line in run raise calledprocesserror retcode process args subprocess calledprocesserror command returned non zero exit status visual studio version gcc compiler version no response | 0 |
158,647 | 13,744,594,583 | IssuesEvent | 2020-10-06 00:24:45 | TesseractCoding/NeoAlgo | https://api.github.com/repos/TesseractCoding/NeoAlgo | closed | [TAKEN] Add Selection Sort Algorithm | documentation enhancement good first issue no-issue-activity | **Algorithm: Selection Sort **
**DS:**
**Languages Supported: C, C++, Java, JavaScript, etc.**
| 1.0 | [TAKEN] Add Selection Sort Algorithm - **Algorithm: Selection Sort **
**DS:**
**Languages Supported: C, C++, Java, JavaScript, etc.**
| non_priority | add selection sort algorithm algorithm selection sort ds languages supported c c java javascript etc | 0 |
204,582 | 23,257,001,110 | IssuesEvent | 2022-08-04 10:08:16 | GoldenSoftwareLtd/gedemin | https://api.github.com/repos/GoldenSoftwareLtd/gedemin | closed | Общие. В свойства объекта добавить отображение IP-адреса (Q) | Security | _**Запись по документу → Контекстное меню → Свойства... → Общие.**_
@ShlTanya , пожалуйста, для реквизитов **Кто создал**, **Кто изменил** добавь отображение IP-адреса:
| True | Общие. В свойства объекта добавить отображение IP-адреса (Q) - _**Запись по документу → Контекстное меню → Свойства... → Общие.**_
@ShlTanya , пожалуйста, для реквизитов **Кто создал**, **Кто изменил** добавь отображение IP-адреса:
| non_priority | общие в свойства объекта добавить отображение ip адреса q запись по документу → контекстное меню → свойства → общие shltanya пожалуйста для реквизитов кто создал кто изменил добавь отображение ip адреса | 0 |
139,150 | 20,782,863,924 | IssuesEvent | 2022-03-16 16:11:32 | cli/cli | https://api.github.com/repos/cli/cli | closed | Add `gh repo remote add [forkname] <org|user> [-- [flags]]` | needs-design enhancement | ### Describe the feature or problem you’d like to solve
I have a clone (this can come from anything, e.g. `homebrew`, or `gh repo clone`, or `git clone`, or some random script from some other thing that gives me a clone).
I'd like to add my personal fork (which already exists) to the local clone without having to write `git remote add [flags] forkname long-complicated-path-that-i-have-to-go-to-the-web-ui-to-get`
### Proposed solution
`gh repo remote add [forkname] <org|user> [-- [flags]]`
Which would functionally calculate the primary github repository (looking for `upstream`, `origin`, or the first remote that's a github remote), then use the github fork network to identify the connected fork owned by `<org|user>` and perform the appropriate `git remote add [flags] forkname github-remote-path`
### Additional context
```
git remote -v
origin https://github.com/Homebrew/brew (fetch)
origin https://github.com/Homebrew/brew (push)
```
As it happens, in this case, my fork is https://github.com/jsoref/brew, and my gh preference is for `ssh`:
So, my actually ideal command is:
`gh repo remote add jsoref --no-tags`
(The extra `--` between `jsoref` and `--no-tags` is really not ideal, but it's understandable, so I'll take whichever)
which should be equivalent to:
`git remote add --no-tags jsoref git@github.com:jsoref/brew.git`
Note: often my remote names do not match (typically I'll rename a short repository to include the org name and a `-`). | 1.0 | Add `gh repo remote add [forkname] <org|user> [-- [flags]]` - ### Describe the feature or problem you’d like to solve
I have a clone (this can come from anything, e.g. `homebrew`, or `gh repo clone`, or `git clone`, or some random script from some other thing that gives me a clone).
I'd like to add my personal fork (which already exists) to the local clone without having to write `git remote add [flags] forkname long-complicated-path-that-i-have-to-go-to-the-web-ui-to-get`
### Proposed solution
`gh repo remote add [forkname] <org|user> [-- [flags]]`
Which would functionally calculate the primary github repository (looking for `upstream`, `origin`, or the first remote that's a github remote), then use the github fork network to identify the connected fork owned by `<org|user>` and perform the appropriate `git remote add [flags] forkname github-remote-path`
### Additional context
```
git remote -v
origin https://github.com/Homebrew/brew (fetch)
origin https://github.com/Homebrew/brew (push)
```
As it happens, in this case, my fork is https://github.com/jsoref/brew, and my gh preference is for `ssh`:
So, my actually ideal command is:
`gh repo remote add jsoref --no-tags`
(The extra `--` between `jsoref` and `--no-tags` is really not ideal, but it's understandable, so I'll take whichever)
which should be equivalent to:
`git remote add --no-tags jsoref git@github.com:jsoref/brew.git`
Note: often my remote names do not match (typically I'll rename a short repository to include the org name and a `-`). | non_priority | add gh repo remote add describe the feature or problem you’d like to solve i have a clone this can come from anything e g homebrew or gh repo clone or git clone or some random script from some other thing that gives me a clone i d like to add my personal fork which already exists to the local clone without having to write git remote add forkname long complicated path that i have to go to the web ui to get proposed solution gh repo remote add which would functionally calculate the primary github repository looking for upstream origin or the first remote that s a github remote then use the github fork network to identify the connected fork owned by and perform the appropriate git remote add forkname github remote path additional context git remote v origin fetch origin push as it happens in this case my fork is and my gh preference is for ssh so my actually ideal command is gh repo remote add jsoref no tags the extra between jsoref and no tags is really not ideal but it s understandable so i ll take whichever which should be equivalent to git remote add no tags jsoref git github com jsoref brew git note often my remote names do not match typically i ll rename a short repository to include the org name and a | 0 |
69,761 | 13,337,951,971 | IssuesEvent | 2020-08-28 10:07:50 | fac20/Week7-DEKN | https://api.github.com/repos/fac20/Week7-DEKN | closed | Deployed | Code review Complement | You've successfully deployed on Heroku. We did lots of testing there and got GET /, POST /signup and POST /posts working | 1.0 | Deployed - You've successfully deployed on Heroku. We did lots of testing there and got GET /, POST /signup and POST /posts working | non_priority | deployed you ve successfully deployed on heroku we did lots of testing there and got get post signup and post posts working | 0 |
143,679 | 13,079,590,275 | IssuesEvent | 2020-08-01 03:58:44 | emerson-matos/financasapi | https://api.github.com/repos/emerson-matos/financasapi | closed | [docs] Make api documentation | documentation enhancement | **Is your feature request related to a problem? Please describe.**
We should teach our client how we are organized, information about our endpoints and our requests contracts should be public to make easier to consume of potentials clients
**Describe the solution you'd like**
We should implement some auto documentation of our API
**Describe alternatives you've considered**
A possible framework to use to solve this problem is Swagger
| 1.0 | [docs] Make api documentation - **Is your feature request related to a problem? Please describe.**
We should teach our client how we are organized, information about our endpoints and our requests contracts should be public to make easier to consume of potentials clients
**Describe the solution you'd like**
We should implement some auto documentation of our API
**Describe alternatives you've considered**
A possible framework to use to solve this problem is Swagger
| non_priority | make api documentation is your feature request related to a problem please describe we should teach our client how we are organized information about our endpoints and our requests contracts should be public to make easier to consume of potentials clients describe the solution you d like we should implement some auto documentation of our api describe alternatives you ve considered a possible framework to use to solve this problem is swagger | 0 |
202,156 | 23,059,260,439 | IssuesEvent | 2022-07-25 08:26:48 | elastic/beats | https://api.github.com/repos/elastic/beats | closed | Auditbeat: Propagate output backpressure in socket dataset | enhancement Auditbeat Team:Security-External Integrations | **Describe the enhancement:**
The socket dataset tracks network flows to/from processes on a Linux system using kprobe tracepoints on the kernel's TCP/IP stack.
Currently, an unbounded linked list is used to store flows ready to be reported to the output. A system with a lot of network I/O can generate events faster than they can be delivered to the output, meaning this linked list grows without limits causing more and more memory to be used by the Auditbeat process.
The dataset needs to receive backpressure from the output to avoid using too much memory. | True | Auditbeat: Propagate output backpressure in socket dataset - **Describe the enhancement:**
The socket dataset tracks network flows to/from processes on a Linux system using kprobe tracepoints on the kernel's TCP/IP stack.
Currently, an unbounded linked list is used to store flows ready to be reported to the output. A system with a lot of network I/O can generate events faster than they can be delivered to the output, meaning this linked list grows without limits causing more and more memory to be used by the Auditbeat process.
The dataset needs to receive backpressure from the output to avoid using too much memory. | non_priority | auditbeat propagate output backpressure in socket dataset describe the enhancement the socket dataset tracks network flows to from processes on a linux system using kprobe tracepoints on the kernel s tcp ip stack currently an unbounded linked list is used to store flows ready to be reported to the output a system with a lot of network i o can generate events faster than they can be delivered to the output meaning this linked list grows without limits causing more and more memory to be used by the auditbeat process the dataset needs to receive backpressure from the output to avoid using too much memory | 0 |
218,222 | 16,977,702,096 | IssuesEvent | 2021-06-30 03:10:17 | elastic/kibana | https://api.github.com/repos/elastic/kibana | closed | Failing test: Creates and activates a new custom rule with override option - Detection rules, override Creates and activates a new custom rule with override option | Team: SecuritySolution Team:Detections and Resp Team:SIEM blocker failed-test skipped-test v7.11.0 v8.0.0 | A test failed on a tracked branch
```
SyntaxError: The following error originated from your application code, not from Cypress.
> Unexpected end of JSON input
When Cypress detects uncaught errors originating from your application it will automatically fail the current test.
This behavior is configurable, and you can choose to turn this off by listening to the `uncaught:exception` event.
https://on.cypress.io/uncaught-exception-from-application
at JSON.parse (<anonymous>)
at Object.next (http://localhost:6111/38291/bundles/plugin/bfetch/bfetch.plugin.js:1:16568)
at t.__tryOrUnsub (http://localhost:6111/38291/bundles/kbn-ui-shared-deps/kbn-ui-shared-deps.js:21:42332)
at t.next (http://localhost:6111/38291/bundles/kbn-ui-shared-deps/kbn-ui-shared-deps.js:21:41477)
at t._next (http://localhost:6111/38291/bundles/kbn-ui-shared-deps/kbn-ui-shared-deps.js:21:40553)
at t.next (http://localhost:6111/38291/bundles/kbn-ui-shared-deps/kbn-ui-shared-deps.js:21:40224)
at t._next (http://localhost:6111/38291/bundles/kbn-ui-shared-deps/kbn-ui-shared-deps.js:283:402758)
at t.next (http://localhost:6111/38291/bundles/kbn-ui-shared-deps/kbn-ui-shared-deps.js:21:40224)
at t.next (http://localhost:6111/38291/bundles/kbn-ui-shared-deps/kbn-ui-shared-deps.js:283:87988)
at t._complete (http://localhost:6111/38291/bundles/plugin/bfetch/bfetch.plugin.js:1:10357)
```
First failure: [Jenkins Build](https://kibana-ci.elastic.co/job/elastic+kibana+master/9850/)
<!-- kibanaCiData = {"failed-test":{"test.class":"Creates and activates a new custom rule with override option","test.name":"Detection rules, override Creates and activates a new custom rule with override option","test.failCount":18}} --> | 2.0 | Failing test: Creates and activates a new custom rule with override option - Detection rules, override Creates and activates a new custom rule with override option - A test failed on a tracked branch
```
SyntaxError: The following error originated from your application code, not from Cypress.
> Unexpected end of JSON input
When Cypress detects uncaught errors originating from your application it will automatically fail the current test.
This behavior is configurable, and you can choose to turn this off by listening to the `uncaught:exception` event.
https://on.cypress.io/uncaught-exception-from-application
at JSON.parse (<anonymous>)
at Object.next (http://localhost:6111/38291/bundles/plugin/bfetch/bfetch.plugin.js:1:16568)
at t.__tryOrUnsub (http://localhost:6111/38291/bundles/kbn-ui-shared-deps/kbn-ui-shared-deps.js:21:42332)
at t.next (http://localhost:6111/38291/bundles/kbn-ui-shared-deps/kbn-ui-shared-deps.js:21:41477)
at t._next (http://localhost:6111/38291/bundles/kbn-ui-shared-deps/kbn-ui-shared-deps.js:21:40553)
at t.next (http://localhost:6111/38291/bundles/kbn-ui-shared-deps/kbn-ui-shared-deps.js:21:40224)
at t._next (http://localhost:6111/38291/bundles/kbn-ui-shared-deps/kbn-ui-shared-deps.js:283:402758)
at t.next (http://localhost:6111/38291/bundles/kbn-ui-shared-deps/kbn-ui-shared-deps.js:21:40224)
at t.next (http://localhost:6111/38291/bundles/kbn-ui-shared-deps/kbn-ui-shared-deps.js:283:87988)
at t._complete (http://localhost:6111/38291/bundles/plugin/bfetch/bfetch.plugin.js:1:10357)
```
First failure: [Jenkins Build](https://kibana-ci.elastic.co/job/elastic+kibana+master/9850/)
<!-- kibanaCiData = {"failed-test":{"test.class":"Creates and activates a new custom rule with override option","test.name":"Detection rules, override Creates and activates a new custom rule with override option","test.failCount":18}} --> | non_priority | failing test creates and activates a new custom rule with override option detection rules override creates and activates a new custom rule with override option a test failed on a tracked branch syntaxerror the following error originated from your application code not from cypress unexpected end of json input when cypress detects uncaught errors originating from your application it will automatically fail the current test this behavior is configurable and you can choose to turn this off by listening to the uncaught exception event at json parse at object next at t tryorunsub at t next at t next at t next at t next at t next at t next at t complete first failure | 0 |
65,498 | 27,120,499,790 | IssuesEvent | 2023-02-15 22:23:47 | microsoft/BotFramework-Composer | https://api.github.com/repos/microsoft/BotFramework-Composer | closed | does not match memory scopes error in bot composer with multiturn implementation | customer-reported Bot Services customer-replied-to | Getting an error message does not match memory scopes error in bot composer with multiturn implementation. Multiturn is working but getting this error each time the dialog executes. Please let me know how to handle this error in bot composer.
| 1.0 | does not match memory scopes error in bot composer with multiturn implementation - Getting an error message does not match memory scopes error in bot composer with multiturn implementation. Multiturn is working but getting this error each time the dialog executes. Please let me know how to handle this error in bot composer.
| non_priority | does not match memory scopes error in bot composer with multiturn implementation getting an error message does not match memory scopes error in bot composer with multiturn implementation multiturn is working but getting this error each time the dialog executes please let me know how to handle this error in bot composer | 0 |
66,304 | 20,146,365,263 | IssuesEvent | 2022-02-09 07:59:30 | primefaces/primeng | https://api.github.com/repos/primefaces/primeng | closed | PrimeNG Calendar (p-calendar) Loses alignment when positioned at the top of the input and the user clicks in the year/month | defect | **I'm submitting a ...** (check one with "x")
```
[x] bug report => Search github for a similar issue or PR before submitting
[ ] feature request => Please check if request is not on the roadmap already https://github.com/primefaces/primeng/wiki/Roadmap
[ ] support request => Please do not submit support request here, instead see http://forum.primefaces.org/viewforum.php?f=35
```
**Plunkr Case (Bug Reports)**
The original examples from PrimeNG:
https://stackblitz.com/edit/primeng-calendar-demo
**Current behavior**
When the calendar is aligned on top of the input field and we click on the year/month, to display the list of years/months, the calendar loses its bottom alignment
**Expected behavior**
When the calendar is aligned on top of the input field and we click on the year/month, to display the list of years/months the calendar should not loses its alignment
**Minimal reproduction of the problem with instructions**
1. Go to https://stackblitz.com/edit/primeng-calendar-demo
2. Click in the input field(calendar) in the bottom of the page. In my example I am using the calendar Multiple.
<img width="285" alt="multiple-calendar-start" src="https://user-images.githubusercontent.com/11298993/148526374-c7e51c07-73b2-4bfc-b650-dd1469d6e19f.PNG">
3. Click in the year. Result: **The calendar loses it's bottom alignment**
<img width="276" alt="multiple-calendar-year-selection" src="https://user-images.githubusercontent.com/11298993/148526387-d13c7ca2-9800-4191-bf07-2fabb4c682bd.PNG">
4. Select the month. Result: **The calendar loses it's bottom alignment**
<img width="283" alt="multiple-calendar-month-selection" src="https://user-images.githubusercontent.com/11298993/148526494-ef6c0282-da29-4ab2-a7df-499769107c52.PNG">
5. After select month the calendar goes back to starting point. Result: **The calendar is not aligned to the bottom of the input anymore**
<img width="277" alt="multiple-calendar-final-result" src="https://user-images.githubusercontent.com/11298993/148526534-3b27cbbd-c8b2-412d-a1f8-27ba17c30625.PNG">
**What is the motivation / use case for changing the behavior?**
This is misleading behaviour for users.
**Please tell us about your environment:**
* **Angular version:** 13.0.2
* **PrimeNG version:** 13.0.4
* **Browser:** [Chrome 96.0.4664.110(64 bits) | Chrome (Android 11) 96.0.4664.104 | Firefox 95.0.2(64 bits) | Edge 96.0.1054.62 (64 bits) ]
This are the browsers I have available for testing
| 1.0 | PrimeNG Calendar (p-calendar) Loses alignment when positioned at the top of the input and the user clicks in the year/month - **I'm submitting a ...** (check one with "x")
```
[x] bug report => Search github for a similar issue or PR before submitting
[ ] feature request => Please check if request is not on the roadmap already https://github.com/primefaces/primeng/wiki/Roadmap
[ ] support request => Please do not submit support request here, instead see http://forum.primefaces.org/viewforum.php?f=35
```
**Plunkr Case (Bug Reports)**
The original examples from PrimeNG:
https://stackblitz.com/edit/primeng-calendar-demo
**Current behavior**
When the calendar is aligned on top of the input field and we click on the year/month, to display the list of years/months, the calendar loses its bottom alignment
**Expected behavior**
When the calendar is aligned on top of the input field and we click on the year/month, to display the list of years/months the calendar should not loses its alignment
**Minimal reproduction of the problem with instructions**
1. Go to https://stackblitz.com/edit/primeng-calendar-demo
2. Click in the input field(calendar) in the bottom of the page. In my example I am using the calendar Multiple.
<img width="285" alt="multiple-calendar-start" src="https://user-images.githubusercontent.com/11298993/148526374-c7e51c07-73b2-4bfc-b650-dd1469d6e19f.PNG">
3. Click in the year. Result: **The calendar loses it's bottom alignment**
<img width="276" alt="multiple-calendar-year-selection" src="https://user-images.githubusercontent.com/11298993/148526387-d13c7ca2-9800-4191-bf07-2fabb4c682bd.PNG">
4. Select the month. Result: **The calendar loses it's bottom alignment**
<img width="283" alt="multiple-calendar-month-selection" src="https://user-images.githubusercontent.com/11298993/148526494-ef6c0282-da29-4ab2-a7df-499769107c52.PNG">
5. After select month the calendar goes back to starting point. Result: **The calendar is not aligned to the bottom of the input anymore**
<img width="277" alt="multiple-calendar-final-result" src="https://user-images.githubusercontent.com/11298993/148526534-3b27cbbd-c8b2-412d-a1f8-27ba17c30625.PNG">
**What is the motivation / use case for changing the behavior?**
This is misleading behaviour for users.
**Please tell us about your environment:**
* **Angular version:** 13.0.2
* **PrimeNG version:** 13.0.4
* **Browser:** [Chrome 96.0.4664.110(64 bits) | Chrome (Android 11) 96.0.4664.104 | Firefox 95.0.2(64 bits) | Edge 96.0.1054.62 (64 bits) ]
This are the browsers I have available for testing
| non_priority | primeng calendar p calendar loses alignment when positioned at the top of the input and the user clicks in the year month i m submitting a check one with x bug report search github for a similar issue or pr before submitting feature request please check if request is not on the roadmap already support request please do not submit support request here instead see plunkr case bug reports the original examples from primeng current behavior when the calendar is aligned on top of the input field and we click on the year month to display the list of years months the calendar loses its bottom alignment expected behavior when the calendar is aligned on top of the input field and we click on the year month to display the list of years months the calendar should not loses its alignment minimal reproduction of the problem with instructions go to click in the input field calendar in the bottom of the page in my example i am using the calendar multiple img width alt multiple calendar start src click in the year result the calendar loses it s bottom alignment img width alt multiple calendar year selection src select the month result the calendar loses it s bottom alignment img width alt multiple calendar month selection src after select month the calendar goes back to starting point result the calendar is not aligned to the bottom of the input anymore img width alt multiple calendar final result src what is the motivation use case for changing the behavior this is misleading behaviour for users please tell us about your environment angular version primeng version browser this are the browsers i have available for testing | 0 |
224,481 | 17,190,074,056 | IssuesEvent | 2021-07-16 09:39:22 | ita-social-projects/dokazovi-requirements | https://api.github.com/repos/ita-social-projects/dokazovi-requirements | opened | [Test for Change request #241] | documentation test case | **Story link**
[#241 Story]
### Status:
Not executed
### Title:
Verify if all writings on the Authors Page are remain readable after disabling the images.
### Description:
### Pre-conditions:
You are launched https://dokazovi-fe.herokuapp.com
Click the 'Authors' tab
Step № | Test Steps | Test data | Expected result | Status (Pass/Fail/Not executed) | Notes
------------ | ------------ | ------------ | ------------ | ------------ | ------------
1 |Open the browser setting: 'Privacy and security'-'Site setting' -'Block images for tested web application' | text | text | Not Executed | text
2 | Update the web application | text | text | Not Executed | text
3 | Verify that the text is readable on the main page | text | text | Not executed | text
### Dependencies:
link
### [Gantt Chart](https://docs.google.com/spreadsheets/d/1bgaEJDOf3OhfNRfP-WWPKmmZFW5C3blOUxamE3wSCbM/edit#gid=775577959)
| 1.0 | [Test for Change request #241] - **Story link**
[#241 Story]
### Status:
Not executed
### Title:
Verify if all writings on the Authors Page are remain readable after disabling the images.
### Description:
### Pre-conditions:
You are launched https://dokazovi-fe.herokuapp.com
Click the 'Authors' tab
Step № | Test Steps | Test data | Expected result | Status (Pass/Fail/Not executed) | Notes
------------ | ------------ | ------------ | ------------ | ------------ | ------------
1 |Open the browser setting: 'Privacy and security'-'Site setting' -'Block images for tested web application' | text | text | Not Executed | text
2 | Update the web application | text | text | Not Executed | text
3 | Verify that the text is readable on the main page | text | text | Not executed | text
### Dependencies:
link
### [Gantt Chart](https://docs.google.com/spreadsheets/d/1bgaEJDOf3OhfNRfP-WWPKmmZFW5C3blOUxamE3wSCbM/edit#gid=775577959)
| non_priority | story link status not executed title verify if all writings on the authors page are remain readable after disabling the images description pre conditions you are launched click the authors tab step № test steps test data expected result status pass fail not executed notes open the browser setting privacy and security site setting block images for tested web application text text not executed text update the web application text text not executed text verify that the text is readable on the main page text text not executed text dependencies link | 0 |
233,265 | 25,758,332,519 | IssuesEvent | 2022-12-08 18:12:08 | whitesource-ps/ws-bulk-report-generator | https://api.github.com/repos/whitesource-ps/ws-bulk-report-generator | opened | certifi-2022.6.15-py3-none-any.whl: 1 vulnerabilities (highest severity is: 6.8) | security vulnerability | <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>certifi-2022.6.15-py3-none-any.whl</b></p></summary>
<p>Python package for providing Mozilla's CA Bundle.</p>
<p>Library home page: <a href="https://files.pythonhosted.org/packages/e9/06/d3d367b7af6305b16f0d28ae2aaeb86154fa91f144f036c2d5002a5a202b/certifi-2022.6.15-py3-none-any.whl">https://files.pythonhosted.org/packages/e9/06/d3d367b7af6305b16f0d28ae2aaeb86154fa91f144f036c2d5002a5a202b/certifi-2022.6.15-py3-none-any.whl</a></p>
<p>Path to dependency file: /tmp/ws-scm/ws-bulk-report-generator</p>
<p>Path to vulnerable library: /tmp/ws-scm/ws-bulk-report-generator,/requirements.txt</p>
<p>
</details>
## Vulnerabilities
| CVE | Severity | <img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS | Dependency | Type | Fixed in (certifi version) | Remediation Available |
| ------------- | ------------- | ----- | ----- | ----- | ------------- | --- |
| [CVE-2022-23491](https://www.mend.io/vulnerability-database/CVE-2022-23491) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 6.8 | certifi-2022.6.15-py3-none-any.whl | Direct | certifi - 2022.12.07 | ✅ |
## Details
<details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2022-23491</summary>
### Vulnerable Library - <b>certifi-2022.6.15-py3-none-any.whl</b></p>
<p>Python package for providing Mozilla's CA Bundle.</p>
<p>Library home page: <a href="https://files.pythonhosted.org/packages/e9/06/d3d367b7af6305b16f0d28ae2aaeb86154fa91f144f036c2d5002a5a202b/certifi-2022.6.15-py3-none-any.whl">https://files.pythonhosted.org/packages/e9/06/d3d367b7af6305b16f0d28ae2aaeb86154fa91f144f036c2d5002a5a202b/certifi-2022.6.15-py3-none-any.whl</a></p>
<p>Path to dependency file: /tmp/ws-scm/ws-bulk-report-generator</p>
<p>Path to vulnerable library: /tmp/ws-scm/ws-bulk-report-generator,/requirements.txt</p>
<p>
Dependency Hierarchy:
- :x: **certifi-2022.6.15-py3-none-any.whl** (Vulnerable Library)
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
Certifi is a curated collection of Root Certificates for validating the trustworthiness of SSL certificates while verifying the identity of TLS hosts. Certifi 2022.12.07 removes root certificates from "TrustCor" from the root store. These are in the process of being removed from Mozilla's trust store. TrustCor's root certificates are being removed pursuant to an investigation prompted by media reporting that TrustCor's ownership also operated a business that produced spyware. Conclusions of Mozilla's investigation can be found in the linked google group discussion.
<p>Publish Date: 2022-12-07
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-23491>CVE-2022-23491</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>6.8</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: High
- User Interaction: None
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: High
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://www.cve.org/CVERecord?id=CVE-2022-23491">https://www.cve.org/CVERecord?id=CVE-2022-23491</a></p>
<p>Release Date: 2022-12-07</p>
<p>Fix Resolution: certifi - 2022.12.07</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation is available for this issue
</details>
***
<p>:rescue_worker_helmet: Automatic Remediation is available for this issue.</p> | True | certifi-2022.6.15-py3-none-any.whl: 1 vulnerabilities (highest severity is: 6.8) - <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>certifi-2022.6.15-py3-none-any.whl</b></p></summary>
<p>Python package for providing Mozilla's CA Bundle.</p>
<p>Library home page: <a href="https://files.pythonhosted.org/packages/e9/06/d3d367b7af6305b16f0d28ae2aaeb86154fa91f144f036c2d5002a5a202b/certifi-2022.6.15-py3-none-any.whl">https://files.pythonhosted.org/packages/e9/06/d3d367b7af6305b16f0d28ae2aaeb86154fa91f144f036c2d5002a5a202b/certifi-2022.6.15-py3-none-any.whl</a></p>
<p>Path to dependency file: /tmp/ws-scm/ws-bulk-report-generator</p>
<p>Path to vulnerable library: /tmp/ws-scm/ws-bulk-report-generator,/requirements.txt</p>
<p>
</details>
## Vulnerabilities
| CVE | Severity | <img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS | Dependency | Type | Fixed in (certifi version) | Remediation Available |
| ------------- | ------------- | ----- | ----- | ----- | ------------- | --- |
| [CVE-2022-23491](https://www.mend.io/vulnerability-database/CVE-2022-23491) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 6.8 | certifi-2022.6.15-py3-none-any.whl | Direct | certifi - 2022.12.07 | ✅ |
## Details
<details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2022-23491</summary>
### Vulnerable Library - <b>certifi-2022.6.15-py3-none-any.whl</b></p>
<p>Python package for providing Mozilla's CA Bundle.</p>
<p>Library home page: <a href="https://files.pythonhosted.org/packages/e9/06/d3d367b7af6305b16f0d28ae2aaeb86154fa91f144f036c2d5002a5a202b/certifi-2022.6.15-py3-none-any.whl">https://files.pythonhosted.org/packages/e9/06/d3d367b7af6305b16f0d28ae2aaeb86154fa91f144f036c2d5002a5a202b/certifi-2022.6.15-py3-none-any.whl</a></p>
<p>Path to dependency file: /tmp/ws-scm/ws-bulk-report-generator</p>
<p>Path to vulnerable library: /tmp/ws-scm/ws-bulk-report-generator,/requirements.txt</p>
<p>
Dependency Hierarchy:
- :x: **certifi-2022.6.15-py3-none-any.whl** (Vulnerable Library)
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
Certifi is a curated collection of Root Certificates for validating the trustworthiness of SSL certificates while verifying the identity of TLS hosts. Certifi 2022.12.07 removes root certificates from "TrustCor" from the root store. These are in the process of being removed from Mozilla's trust store. TrustCor's root certificates are being removed pursuant to an investigation prompted by media reporting that TrustCor's ownership also operated a business that produced spyware. Conclusions of Mozilla's investigation can be found in the linked google group discussion.
<p>Publish Date: 2022-12-07
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-23491>CVE-2022-23491</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>6.8</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: High
- User Interaction: None
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: High
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://www.cve.org/CVERecord?id=CVE-2022-23491">https://www.cve.org/CVERecord?id=CVE-2022-23491</a></p>
<p>Release Date: 2022-12-07</p>
<p>Fix Resolution: certifi - 2022.12.07</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation is available for this issue
</details>
***
<p>:rescue_worker_helmet: Automatic Remediation is available for this issue.</p> | non_priority | certifi none any whl vulnerabilities highest severity is vulnerable library certifi none any whl python package for providing mozilla s ca bundle library home page a href path to dependency file tmp ws scm ws bulk report generator path to vulnerable library tmp ws scm ws bulk report generator requirements txt vulnerabilities cve severity cvss dependency type fixed in certifi version remediation available medium certifi none any whl direct certifi details cve vulnerable library certifi none any whl python package for providing mozilla s ca bundle library home page a href path to dependency file tmp ws scm ws bulk report generator path to vulnerable library tmp ws scm ws bulk report generator requirements txt dependency hierarchy x certifi none any whl vulnerable library found in base branch master vulnerability details certifi is a curated collection of root certificates for validating the trustworthiness of ssl certificates while verifying the identity of tls hosts certifi removes root certificates from trustcor from the root store these are in the process of being removed from mozilla s trust store trustcor s root certificates are being removed pursuant to an investigation prompted by media reporting that trustcor s ownership also operated a business that produced spyware conclusions of mozilla s investigation can be found in the linked google group discussion 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 changed impact metrics confidentiality impact none integrity impact high availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution certifi rescue worker helmet automatic remediation is available for this issue rescue worker helmet automatic remediation is available for this issue | 0 |
100,415 | 11,194,840,587 | IssuesEvent | 2020-01-03 03:13:26 | gatsbyjs/gatsby-pt-BR | https://api.github.com/repos/gatsbyjs/gatsby-pt-BR | closed | Translation Progress (Batch #1) - Finished | documentation | ## --------------------- ! UPDATE IMPORTANTE ! ------------------
Todos os arquivos já foram designados, futuramente abriremos novos para tradução!
## Maintainers: NUNCA mergem uma PR com somente uma aprovação!
### Revisores Oficiais
- @jessescn
- @rafaeelaudibert
- @Dennissiq
- @jay-jlm
- @iaurg
- @mjr
- @abnersajr
## -----------------------------------------------------------------
## Para os novos tradutores
Siga os passos descritos no nosso [CONTRIBUTING.md](https://github.com/gatsbyjs/gatsby-pt-BR/blob/master/CONTRIBUTING.md). **Daremos um limite de 2 SEMANAS para que cada tradução seja finalizada, no intuito de manter a tradução sempre dinâmica.**
## Labels
* [] :running_man: - Em Progresso
* [] :eyes: - Sob Revisão
* [] :heavy_check_mark: - Feita!
## Páginas
Aqui estão listadas as páginas que foram traduzidas, estão em processo de tradução ou estão disponíveis para serem traduzidas. Você pode conferir os estados delas verificando as suas `labels`.
### Community
* [x] community/code-of-conduct (@jessescn) :heavy_check_mark: #5
### Tutorial
* [x] tutorial/index (@iaurg) :heavy_check_mark: #11
* [x] tutorial/part-zero (@Dennissiq) :heavy_check_mark: #4
* [x] tutorial/part-one (@jpedroschmitz) ✔️ #89
* [x] tutorial/part-two (@crisgon) ✔️ #121
* [x] tutorial/part-three (@gutofoletto) :heavy_check_mark: #27
* [x] tutorial/part-four (@renanmav) ✔️ #14
* [x] tutorial/part-five (@luizcieslak) :heavy_check_mark: #34
* [x] tutorial/part-six (@gabrielferreiraa) :heavy_check_mark: #56
* [x] tutorial/part-seven (@ArthurFerrao) ✔️ #55
* [x] tutorial/part-eight (@gabrielreisn) :heavy_check_mark: #35
### Docs
* [x] docs/index (@iaurg) :heavy_check_mark: #11
* [x] docs/quick-start (@gvarandas) :heavy_check_mark: #38
* [x] docs/recipes (@LucasRuy) :heavy_check_mark: #40
* [x] docs/glossary (@mjr) :heavy_check_mark: #17
* [x] docs/gatsby-cli (@jay-jlm) :heavy_check_mark: #7
| 1.0 | Translation Progress (Batch #1) - Finished - ## --------------------- ! UPDATE IMPORTANTE ! ------------------
Todos os arquivos já foram designados, futuramente abriremos novos para tradução!
## Maintainers: NUNCA mergem uma PR com somente uma aprovação!
### Revisores Oficiais
- @jessescn
- @rafaeelaudibert
- @Dennissiq
- @jay-jlm
- @iaurg
- @mjr
- @abnersajr
## -----------------------------------------------------------------
## Para os novos tradutores
Siga os passos descritos no nosso [CONTRIBUTING.md](https://github.com/gatsbyjs/gatsby-pt-BR/blob/master/CONTRIBUTING.md). **Daremos um limite de 2 SEMANAS para que cada tradução seja finalizada, no intuito de manter a tradução sempre dinâmica.**
## Labels
* [] :running_man: - Em Progresso
* [] :eyes: - Sob Revisão
* [] :heavy_check_mark: - Feita!
## Páginas
Aqui estão listadas as páginas que foram traduzidas, estão em processo de tradução ou estão disponíveis para serem traduzidas. Você pode conferir os estados delas verificando as suas `labels`.
### Community
* [x] community/code-of-conduct (@jessescn) :heavy_check_mark: #5
### Tutorial
* [x] tutorial/index (@iaurg) :heavy_check_mark: #11
* [x] tutorial/part-zero (@Dennissiq) :heavy_check_mark: #4
* [x] tutorial/part-one (@jpedroschmitz) ✔️ #89
* [x] tutorial/part-two (@crisgon) ✔️ #121
* [x] tutorial/part-three (@gutofoletto) :heavy_check_mark: #27
* [x] tutorial/part-four (@renanmav) ✔️ #14
* [x] tutorial/part-five (@luizcieslak) :heavy_check_mark: #34
* [x] tutorial/part-six (@gabrielferreiraa) :heavy_check_mark: #56
* [x] tutorial/part-seven (@ArthurFerrao) ✔️ #55
* [x] tutorial/part-eight (@gabrielreisn) :heavy_check_mark: #35
### Docs
* [x] docs/index (@iaurg) :heavy_check_mark: #11
* [x] docs/quick-start (@gvarandas) :heavy_check_mark: #38
* [x] docs/recipes (@LucasRuy) :heavy_check_mark: #40
* [x] docs/glossary (@mjr) :heavy_check_mark: #17
* [x] docs/gatsby-cli (@jay-jlm) :heavy_check_mark: #7
| non_priority | translation progress batch finished update importante todos os arquivos já foram designados futuramente abriremos novos para tradução maintainers nunca mergem uma pr com somente uma aprovação revisores oficiais jessescn rafaeelaudibert dennissiq jay jlm iaurg mjr abnersajr para os novos tradutores siga os passos descritos no nosso daremos um limite de semanas para que cada tradução seja finalizada no intuito de manter a tradução sempre dinâmica labels running man em progresso eyes sob revisão heavy check mark feita páginas aqui estão listadas as páginas que foram traduzidas estão em processo de tradução ou estão disponíveis para serem traduzidas você pode conferir os estados delas verificando as suas labels community community code of conduct jessescn heavy check mark tutorial tutorial index iaurg heavy check mark tutorial part zero dennissiq heavy check mark tutorial part one jpedroschmitz ✔️ tutorial part two crisgon ✔️ tutorial part three gutofoletto heavy check mark tutorial part four renanmav ✔️ tutorial part five luizcieslak heavy check mark tutorial part six gabrielferreiraa heavy check mark tutorial part seven arthurferrao ✔️ tutorial part eight gabrielreisn heavy check mark docs docs index iaurg heavy check mark docs quick start gvarandas heavy check mark docs recipes lucasruy heavy check mark docs glossary mjr heavy check mark docs gatsby cli jay jlm heavy check mark | 0 |
44,635 | 12,303,170,548 | IssuesEvent | 2020-05-11 18:13:27 | cakephp/cakephp | https://api.github.com/repos/cakephp/cakephp | closed | Serialize issue on ResultSet | defect | This is a (multiple allowed):
* [x] bug
* [ ] enhancement
* [ ] feature-discussion (RFC)
* CakePHP Version: master / 4.x
### What you did
Upgraded from 3.x:
```php
$this->loadModel('Data.States');
$states = $this->States->find('all');
$this->set(compact('states'));
$this->set('_serialize', ['states']);
```
### What happened
Some of my controllers error with
> [Cake\View\Exception\SerializationFailureException] Serialization of View data failed. in /.../vendor/cakephp/cakephp/src/View/SerializedView.php on line 127
caused by
> Caused by: [TypeError] array_keys() expects parameter 1 to be array, object given in /.../vendor/cakephp/cakephp/src/View/XmlView.php on line 142
### What you expected to happen
That it works even without having to force-call toArray() on it, as it did before.
Do we want to fix this? Or should we expect people to always do
$states = $this->States->find('all')
->toArray();
?
| 1.0 | Serialize issue on ResultSet - This is a (multiple allowed):
* [x] bug
* [ ] enhancement
* [ ] feature-discussion (RFC)
* CakePHP Version: master / 4.x
### What you did
Upgraded from 3.x:
```php
$this->loadModel('Data.States');
$states = $this->States->find('all');
$this->set(compact('states'));
$this->set('_serialize', ['states']);
```
### What happened
Some of my controllers error with
> [Cake\View\Exception\SerializationFailureException] Serialization of View data failed. in /.../vendor/cakephp/cakephp/src/View/SerializedView.php on line 127
caused by
> Caused by: [TypeError] array_keys() expects parameter 1 to be array, object given in /.../vendor/cakephp/cakephp/src/View/XmlView.php on line 142
### What you expected to happen
That it works even without having to force-call toArray() on it, as it did before.
Do we want to fix this? Or should we expect people to always do
$states = $this->States->find('all')
->toArray();
?
| non_priority | serialize issue on resultset this is a multiple allowed bug enhancement feature discussion rfc cakephp version master x what you did upgraded from x php this loadmodel data states states this states find all this set compact states this set serialize what happened some of my controllers error with serialization of view data failed in vendor cakephp cakephp src view serializedview php on line caused by caused by array keys expects parameter to be array object given in vendor cakephp cakephp src view xmlview php on line what you expected to happen that it works even without having to force call toarray on it as it did before do we want to fix this or should we expect people to always do states this states find all toarray | 0 |
98,019 | 16,342,884,048 | IssuesEvent | 2021-05-13 01:21:48 | joaonetoo/saaddeploy | https://api.github.com/repos/joaonetoo/saaddeploy | opened | CVE-2021-29509 (High) detected in puma-3.6.0.gem | security vulnerability | ## CVE-2021-29509 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>puma-3.6.0.gem</b></p></summary>
<p>Puma is a simple, fast, threaded, and highly concurrent HTTP 1.1 server for Ruby/Rack applications. Puma is intended for use in both development and production environments. In order to get the best throughput, it is highly recommended that you use a Ruby implementation with real threads like Rubinius or JRuby.</p>
<p>Library home page: <a href="https://rubygems.org/gems/puma-3.6.0.gem">https://rubygems.org/gems/puma-3.6.0.gem</a></p>
<p>
Dependency Hierarchy:
- capistrano3-puma-1.2.1.gem (Root Library)
- :x: **puma-3.6.0.gem** (Vulnerable Library)
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
Puma is a concurrent HTTP 1.1 server for Ruby/Rack applications. The fix for CVE-2019-16770 was incomplete. The original fix only protected existing connections that had already been accepted from having their requests starved by greedy persistent-connections saturating all threads in the same process. However, new connections may still be starved by greedy persistent-connections saturating all threads in all processes in the cluster. A `puma` server which received more concurrent `keep-alive` connections than the server had threads in its threadpool would service only a subset of connections, denying service to the unserved connections. This problem has been fixed in `puma` 4.3.8 and 5.3.1. Setting `queue_requests false` also fixes the issue. This is not advised when using `puma` without a reverse proxy, such as `nginx` or `apache`, because you will open yourself to slow client attacks (e.g. slowloris). The fix is very small and a git patch is available for those using unsupported versions of Puma.
<p>Publish Date: 2021-05-11
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-29509>CVE-2021-29509</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/puma/puma/security/advisories/GHSA-q28m-8xjw-8vr5">https://github.com/puma/puma/security/advisories/GHSA-q28m-8xjw-8vr5</a></p>
<p>Release Date: 2021-05-11</p>
<p>Fix Resolution: puma - 4.3.8,5.3.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-29509 (High) detected in puma-3.6.0.gem - ## CVE-2021-29509 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>puma-3.6.0.gem</b></p></summary>
<p>Puma is a simple, fast, threaded, and highly concurrent HTTP 1.1 server for Ruby/Rack applications. Puma is intended for use in both development and production environments. In order to get the best throughput, it is highly recommended that you use a Ruby implementation with real threads like Rubinius or JRuby.</p>
<p>Library home page: <a href="https://rubygems.org/gems/puma-3.6.0.gem">https://rubygems.org/gems/puma-3.6.0.gem</a></p>
<p>
Dependency Hierarchy:
- capistrano3-puma-1.2.1.gem (Root Library)
- :x: **puma-3.6.0.gem** (Vulnerable Library)
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
Puma is a concurrent HTTP 1.1 server for Ruby/Rack applications. The fix for CVE-2019-16770 was incomplete. The original fix only protected existing connections that had already been accepted from having their requests starved by greedy persistent-connections saturating all threads in the same process. However, new connections may still be starved by greedy persistent-connections saturating all threads in all processes in the cluster. A `puma` server which received more concurrent `keep-alive` connections than the server had threads in its threadpool would service only a subset of connections, denying service to the unserved connections. This problem has been fixed in `puma` 4.3.8 and 5.3.1. Setting `queue_requests false` also fixes the issue. This is not advised when using `puma` without a reverse proxy, such as `nginx` or `apache`, because you will open yourself to slow client attacks (e.g. slowloris). The fix is very small and a git patch is available for those using unsupported versions of Puma.
<p>Publish Date: 2021-05-11
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-29509>CVE-2021-29509</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/puma/puma/security/advisories/GHSA-q28m-8xjw-8vr5">https://github.com/puma/puma/security/advisories/GHSA-q28m-8xjw-8vr5</a></p>
<p>Release Date: 2021-05-11</p>
<p>Fix Resolution: puma - 4.3.8,5.3.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 puma gem cve high severity vulnerability vulnerable library puma gem puma is a simple fast threaded and highly concurrent http server for ruby rack applications puma is intended for use in both development and production environments in order to get the best throughput it is highly recommended that you use a ruby implementation with real threads like rubinius or jruby library home page a href dependency hierarchy puma gem root library x puma gem vulnerable library vulnerability details puma is a concurrent http server for ruby rack applications the fix for cve was incomplete the original fix only protected existing connections that had already been accepted from having their requests starved by greedy persistent connections saturating all threads in the same process however new connections may still be starved by greedy persistent connections saturating all threads in all processes in the cluster a puma server which received more concurrent keep alive connections than the server had threads in its threadpool would service only a subset of connections denying service to the unserved connections this problem has been fixed in puma and setting queue requests false also fixes the issue this is not advised when using puma without a reverse proxy such as nginx or apache because you will open yourself to slow client attacks e g slowloris the fix is very small and a git patch is available for those using unsupported versions of puma 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 puma step up your open source security game with whitesource | 0 |
10,725 | 9,081,589,725 | IssuesEvent | 2019-02-17 03:02:30 | AlwaysBeCrafting/Mysticell | https://api.github.com/repos/AlwaysBeCrafting/Mysticell | opened | Migrate to React v16.8 / React Hooks | enhancement service-web | ## Summary
React has released Hooks as a way to write stateful components as plain functions, and describes them as a new path forward for the framework. The intent of Hooks aligns well with our code style. We should migrate the existing class components now while it's still a small task.
[API reference](https://reactjs.org/docs/hooks-reference.html)
## Objectives
- [ ] Update the React dependency to version 16.8 and resolve any build issues
- [ ] Convert all class components to functions, re-implementing any stateful behavior with React Hooks | 1.0 | Migrate to React v16.8 / React Hooks - ## Summary
React has released Hooks as a way to write stateful components as plain functions, and describes them as a new path forward for the framework. The intent of Hooks aligns well with our code style. We should migrate the existing class components now while it's still a small task.
[API reference](https://reactjs.org/docs/hooks-reference.html)
## Objectives
- [ ] Update the React dependency to version 16.8 and resolve any build issues
- [ ] Convert all class components to functions, re-implementing any stateful behavior with React Hooks | non_priority | migrate to react react hooks summary react has released hooks as a way to write stateful components as plain functions and describes them as a new path forward for the framework the intent of hooks aligns well with our code style we should migrate the existing class components now while it s still a small task objectives update the react dependency to version and resolve any build issues convert all class components to functions re implementing any stateful behavior with react hooks | 0 |
284,978 | 31,019,477,310 | IssuesEvent | 2023-08-10 03:16:13 | Grunet/cloud-native-honeypot | https://api.github.com/repos/Grunet/cloud-native-honeypot | closed | Don't Leave pipx Usage in CI Unpinned | security | Check the version that comes pre-installed on the runner and fail CI otherwise to make sure the update is legitimate | True | Don't Leave pipx Usage in CI Unpinned - Check the version that comes pre-installed on the runner and fail CI otherwise to make sure the update is legitimate | non_priority | don t leave pipx usage in ci unpinned check the version that comes pre installed on the runner and fail ci otherwise to make sure the update is legitimate | 0 |
42,964 | 23,057,881,784 | IssuesEvent | 2022-07-25 07:10:49 | qbittorrent/qBittorrent | https://api.github.com/repos/qbittorrent/qBittorrent | closed | High ram usage and disabling the OS cache cripple my download speed | Performance Libtorrent | **Please provide the following information**
### qBittorrent version and Operating System
4.0.4 on Windows 10
### What is the problem
i have a very high ram usage after a while, up to a point, where my system just freezes, and i have to force shutdown. no error message but i can see that my memory is at 99% (it takes minutes to get to the task manager)
FYI i have a 6700K, 16gb of ram
### What is the expected behavior
not crippling my system by using so much ram...
### Steps to reproduce
in my case, i just launch Qbittorent, start downloading and seeding and after a while my pc become unresponsive because it gets to 99% ram usage
### Extra info(if any)
it also happen on 3.3.X, disabling the OS cache as suggested in other topics works, but my download speed drop drastically, i go from 9Mio/s to 2Mio/s
Just the time it took me to write this post (4 minutes give or take) i got 15% more ram taken...
i got the client installed on a 4TO HDD
UPDATE: pausing the downloads, decrease my ram usage, but it doesn't go back to where it was at the start, and everytime i do it, this minimum increase.. for example, i m at 40% before i start the client, i got to 80%, i pause donwload, i get to 50%, i start the DL again, get to 80%, pause again, thise time i will get to 55% and so on...
UPDATE 2: if i use 999Mo Disk cache, my donwload speed is normal with os caching off
UPDATE 3: OS cache Off, disk cache 999Mio ==> high ram usage , download speed normal
<bountysource-plugin>
---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/56324739-high-ram-usage-and-disabling-the-os-cache-cripple-my-download-speed?utm_campaign=plugin&utm_content=tracker%2F298524&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F298524&utm_medium=issues&utm_source=github).
</bountysource-plugin> | True | High ram usage and disabling the OS cache cripple my download speed - **Please provide the following information**
### qBittorrent version and Operating System
4.0.4 on Windows 10
### What is the problem
i have a very high ram usage after a while, up to a point, where my system just freezes, and i have to force shutdown. no error message but i can see that my memory is at 99% (it takes minutes to get to the task manager)
FYI i have a 6700K, 16gb of ram
### What is the expected behavior
not crippling my system by using so much ram...
### Steps to reproduce
in my case, i just launch Qbittorent, start downloading and seeding and after a while my pc become unresponsive because it gets to 99% ram usage
### Extra info(if any)
it also happen on 3.3.X, disabling the OS cache as suggested in other topics works, but my download speed drop drastically, i go from 9Mio/s to 2Mio/s
Just the time it took me to write this post (4 minutes give or take) i got 15% more ram taken...
i got the client installed on a 4TO HDD
UPDATE: pausing the downloads, decrease my ram usage, but it doesn't go back to where it was at the start, and everytime i do it, this minimum increase.. for example, i m at 40% before i start the client, i got to 80%, i pause donwload, i get to 50%, i start the DL again, get to 80%, pause again, thise time i will get to 55% and so on...
UPDATE 2: if i use 999Mo Disk cache, my donwload speed is normal with os caching off
UPDATE 3: OS cache Off, disk cache 999Mio ==> high ram usage , download speed normal
<bountysource-plugin>
---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/56324739-high-ram-usage-and-disabling-the-os-cache-cripple-my-download-speed?utm_campaign=plugin&utm_content=tracker%2F298524&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F298524&utm_medium=issues&utm_source=github).
</bountysource-plugin> | non_priority | high ram usage and disabling the os cache cripple my download speed please provide the following information qbittorrent version and operating system on windows what is the problem i have a very high ram usage after a while up to a point where my system just freezes and i have to force shutdown no error message but i can see that my memory is at it takes minutes to get to the task manager fyi i have a of ram what is the expected behavior not crippling my system by using so much ram steps to reproduce in my case i just launch qbittorent start downloading and seeding and after a while my pc become unresponsive because it gets to ram usage extra info if any it also happen on x disabling the os cache as suggested in other topics works but my download speed drop drastically i go from s to s just the time it took me to write this post minutes give or take i got more ram taken i got the client installed on a hdd update pausing the downloads decrease my ram usage but it doesn t go back to where it was at the start and everytime i do it this minimum increase for example i m at before i start the client i got to i pause donwload i get to i start the dl again get to pause again thise time i will get to and so on update if i use disk cache my donwload speed is normal with os caching off update os cache off disk cache high ram usage download speed normal want to back this issue we accept bounties via | 0 |
255,644 | 21,941,721,732 | IssuesEvent | 2022-05-23 18:51:38 | gonmarfer2/Acme-Toolkits | https://api.github.com/repos/gonmarfer2/Acme-Toolkits | closed | Task-097/T: Operations by patrons on patronages (8) | testing D04 | Create both positive and negative tests for the following operations:
- [ ] Create patronages.
- [ ] Update patronages, as long as they're not published.
- [ ] Delete patronages, as long as they're not published.
- [ ] Publish patronages | 1.0 | Task-097/T: Operations by patrons on patronages (8) - Create both positive and negative tests for the following operations:
- [ ] Create patronages.
- [ ] Update patronages, as long as they're not published.
- [ ] Delete patronages, as long as they're not published.
- [ ] Publish patronages | non_priority | task t operations by patrons on patronages create both positive and negative tests for the following operations create patronages update patronages as long as they re not published delete patronages as long as they re not published publish patronages | 0 |
231,261 | 17,671,623,288 | IssuesEvent | 2021-08-23 07:05:46 | apache/skywalking | https://api.github.com/repos/apache/skywalking | opened | Cut the current java-agent/readme into different documents | documentation | We should cut the document into several small documents and update the menu. | 1.0 | Cut the current java-agent/readme into different documents - We should cut the document into several small documents and update the menu. | non_priority | cut the current java agent readme into different documents we should cut the document into several small documents and update the menu | 0 |
220,731 | 24,566,022,258 | IssuesEvent | 2022-10-13 03:08:56 | nexmo-community/client-sdk-tutorials | https://api.github.com/repos/nexmo-community/client-sdk-tutorials | opened | lint-gradle-27.2.1.jar: 18 vulnerabilities (highest severity is: 7.5) | security vulnerability | <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>lint-gradle-27.2.1.jar</b></p></summary>
<p></p>
<p>Path to dependency file: /app-to-app-java/app-to-app/app/build.gradle</p>
<p>Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/com.google.guava/guava/28.1-jre/b0e91dcb6a44ffb6221b5027e12a5cb34b841145/guava-28.1-jre.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/com.google.guava/guava/28.1-jre/b0e91dcb6a44ffb6221b5027e12a5cb34b841145/guava-28.1-jre.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/com.google.guava/guava/28.1-jre/b0e91dcb6a44ffb6221b5027e12a5cb34b841145/guava-28.1-jre.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/com.google.guava/guava/28.1-jre/b0e91dcb6a44ffb6221b5027e12a5cb34b841145/guava-28.1-jre.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/com.google.guava/guava/28.1-jre/b0e91dcb6a44ffb6221b5027e12a5cb34b841145/guava-28.1-jre.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/com.google.guava/guava/28.1-jre/b0e91dcb6a44ffb6221b5027e12a5cb34b841145/guava-28.1-jre.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/com.google.guava/guava/28.1-jre/b0e91dcb6a44ffb6221b5027e12a5cb34b841145/guava-28.1-jre.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/com.google.guava/guava/28.1-jre/b0e91dcb6a44ffb6221b5027e12a5cb34b841145/guava-28.1-jre.jar</p>
<p>
<p>Found in HEAD commit: <a href="https://github.com/nexmo-community/client-sdk-tutorials/commit/691e25809d42cce5a487504aa376638500c5b492">691e25809d42cce5a487504aa376638500c5b492</a></p></details>
## Vulnerabilities
| CVE | Severity | <img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS | Dependency | Type | Fixed in | Remediation Available |
| ------------- | ------------- | ----- | ----- | ----- | --- | --- |
| [CVE-2021-36090](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-36090) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | commons-compress-1.12.jar | Transitive | N/A | ❌ |
| [CVE-2019-17359](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-17359) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | bcprov-jdk15on-1.56.jar | Transitive | N/A | ❌ |
| [CVE-2021-35517](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-35517) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | commons-compress-1.12.jar | Transitive | N/A | ❌ |
| [CVE-2021-35516](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-35516) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | commons-compress-1.12.jar | Transitive | N/A | ❌ |
| [CVE-2021-35515](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-35515) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | commons-compress-1.12.jar | Transitive | N/A | ❌ |
| [CVE-2022-23437](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-23437) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 6.5 | xercesImpl-2.12.0.jar | Transitive | N/A | ❌ |
| [WS-2019-0379](https://github.com/apache/commons-codec/commit/48b615756d1d770091ea3322eefc08011ee8b113) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 6.5 | commons-codec-1.10.jar | Transitive | N/A | ❌ |
| [CVE-2020-15522](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-15522) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 5.9 | bcprov-jdk15on-1.56.jar | Transitive | N/A | ❌ |
| [CVE-2022-3171](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-3171) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 5.7 | protobuf-java-3.10.0.jar | Transitive | N/A | ❌ |
| [CVE-2021-22569](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-22569) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 5.5 | protobuf-java-3.10.0.jar | Transitive | N/A | ❌ |
| [CVE-2020-17521](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-17521) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 5.5 | groovy-all-2.4.15.jar | Transitive | N/A | ❌ |
| [CVE-2018-11771](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-11771) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 5.5 | commons-compress-1.12.jar | Transitive | N/A | ❌ |
| [CVE-2018-1324](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-1324) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 5.5 | commons-compress-1.12.jar | Transitive | N/A | ❌ |
| [CVE-2022-24329](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-24329) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 5.3 | kotlin-stdlib-1.4.31.jar | Transitive | N/A | ❌ |
| [CVE-2018-1000180](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-1000180) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 5.3 | bcprov-jdk15on-1.56.jar | Transitive | N/A | ❌ |
| [CVE-2020-13956](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-13956) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 5.3 | httpclient-4.5.6.jar | Transitive | N/A | ❌ |
| [CVE-2020-26939](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-26939) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 5.3 | bcprov-jdk15on-1.56.jar | Transitive | N/A | ❌ |
| [CVE-2020-8908](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-8908) | <img src='https://whitesource-resources.whitesourcesoftware.com/low_vul.png' width=19 height=20> Low | 3.3 | guava-28.1-jre.jar | Transitive | N/A | ❌ |
## Details
> Partial details (15 vulnerabilities) are displayed below due to a content size limitation in GitHub. To view information on the remaining vulnerabilities, navigate to the Mend Application.<br>
<details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2021-36090</summary>
### Vulnerable Library - <b>commons-compress-1.12.jar</b></p>
<p>Apache Commons Compress software defines an API for working with
compression and archive formats. These include: bzip2, gzip, pack200,
lzma, xz, Snappy, traditional Unix Compress, DEFLATE and ar, cpio,
jar, tar, zip, dump, 7z, arj.</p>
<p>Path to dependency file: /app-to-phone-java/app-to-phone/app/build.gradle</p>
<p>Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.apache.commons/commons-compress/1.12/84caa68576e345eb5e7ae61a0e5a9229eb100d7b/commons-compress-1.12.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.apache.commons/commons-compress/1.12/84caa68576e345eb5e7ae61a0e5a9229eb100d7b/commons-compress-1.12.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.apache.commons/commons-compress/1.12/84caa68576e345eb5e7ae61a0e5a9229eb100d7b/commons-compress-1.12.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.apache.commons/commons-compress/1.12/84caa68576e345eb5e7ae61a0e5a9229eb100d7b/commons-compress-1.12.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.apache.commons/commons-compress/1.12/84caa68576e345eb5e7ae61a0e5a9229eb100d7b/commons-compress-1.12.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.apache.commons/commons-compress/1.12/84caa68576e345eb5e7ae61a0e5a9229eb100d7b/commons-compress-1.12.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.apache.commons/commons-compress/1.12/84caa68576e345eb5e7ae61a0e5a9229eb100d7b/commons-compress-1.12.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.apache.commons/commons-compress/1.12/84caa68576e345eb5e7ae61a0e5a9229eb100d7b/commons-compress-1.12.jar</p>
<p>
Dependency Hierarchy:
- lint-gradle-27.2.1.jar (Root Library)
- builder-4.2.1.jar
- sdklib-27.2.1.jar
- :x: **commons-compress-1.12.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/nexmo-community/client-sdk-tutorials/commit/691e25809d42cce5a487504aa376638500c5b492">691e25809d42cce5a487504aa376638500c5b492</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
When reading a specially crafted ZIP archive, Compress can be made to allocate large amounts of memory that finally leads to an out of memory error even for very small inputs. This could be used to mount a denial of service attack against services that use Compress' zip package.
<p>Publish Date: 2021-07-13
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-36090>CVE-2021-36090</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>7.5</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://commons.apache.org/proper/commons-compress/security-reports.html">https://commons.apache.org/proper/commons-compress/security-reports.html</a></p>
<p>Release Date: 2021-07-13</p>
<p>Fix Resolution: org.apache.commons:commons-compress:1.21</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2019-17359</summary>
### Vulnerable Library - <b>bcprov-jdk15on-1.56.jar</b></p>
<p>The Bouncy Castle Crypto package is a Java implementation of cryptographic algorithms. This jar contains JCE provider and lightweight API for the Bouncy Castle Cryptography APIs for JDK 1.5 to JDK 1.8.</p>
<p>Library home page: <a href="http://www.bouncycastle.org/java.html">http://www.bouncycastle.org/java.html</a></p>
<p>Path to dependency file: /app-to-phone-java/app-to-phone/app/build.gradle</p>
<p>Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.bouncycastle/bcprov-jdk15on/1.56/a153c6f9744a3e9dd6feab5e210e1c9861362ec7/bcprov-jdk15on-1.56.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.bouncycastle/bcprov-jdk15on/1.56/a153c6f9744a3e9dd6feab5e210e1c9861362ec7/bcprov-jdk15on-1.56.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.bouncycastle/bcprov-jdk15on/1.56/a153c6f9744a3e9dd6feab5e210e1c9861362ec7/bcprov-jdk15on-1.56.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.bouncycastle/bcprov-jdk15on/1.56/a153c6f9744a3e9dd6feab5e210e1c9861362ec7/bcprov-jdk15on-1.56.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.bouncycastle/bcprov-jdk15on/1.56/a153c6f9744a3e9dd6feab5e210e1c9861362ec7/bcprov-jdk15on-1.56.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.bouncycastle/bcprov-jdk15on/1.56/a153c6f9744a3e9dd6feab5e210e1c9861362ec7/bcprov-jdk15on-1.56.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.bouncycastle/bcprov-jdk15on/1.56/a153c6f9744a3e9dd6feab5e210e1c9861362ec7/bcprov-jdk15on-1.56.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.bouncycastle/bcprov-jdk15on/1.56/a153c6f9744a3e9dd6feab5e210e1c9861362ec7/bcprov-jdk15on-1.56.jar</p>
<p>
Dependency Hierarchy:
- lint-gradle-27.2.1.jar (Root Library)
- builder-4.2.1.jar
- :x: **bcprov-jdk15on-1.56.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/nexmo-community/client-sdk-tutorials/commit/691e25809d42cce5a487504aa376638500c5b492">691e25809d42cce5a487504aa376638500c5b492</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
The ASN.1 parser in Bouncy Castle Crypto (aka BC Java) 1.63 can trigger a large attempted memory allocation, and resultant OutOfMemoryError error, via crafted ASN.1 data. This is fixed in 1.64.
<p>Publish Date: 2019-10-08
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-17359>CVE-2019-17359</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>7.5</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-17359">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-17359</a></p>
<p>Release Date: 2019-10-08</p>
<p>Fix Resolution: org.bouncycastle:bcprov-jdk15on:1.64</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2021-35517</summary>
### Vulnerable Library - <b>commons-compress-1.12.jar</b></p>
<p>Apache Commons Compress software defines an API for working with
compression and archive formats. These include: bzip2, gzip, pack200,
lzma, xz, Snappy, traditional Unix Compress, DEFLATE and ar, cpio,
jar, tar, zip, dump, 7z, arj.</p>
<p>Path to dependency file: /app-to-phone-java/app-to-phone/app/build.gradle</p>
<p>Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.apache.commons/commons-compress/1.12/84caa68576e345eb5e7ae61a0e5a9229eb100d7b/commons-compress-1.12.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.apache.commons/commons-compress/1.12/84caa68576e345eb5e7ae61a0e5a9229eb100d7b/commons-compress-1.12.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.apache.commons/commons-compress/1.12/84caa68576e345eb5e7ae61a0e5a9229eb100d7b/commons-compress-1.12.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.apache.commons/commons-compress/1.12/84caa68576e345eb5e7ae61a0e5a9229eb100d7b/commons-compress-1.12.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.apache.commons/commons-compress/1.12/84caa68576e345eb5e7ae61a0e5a9229eb100d7b/commons-compress-1.12.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.apache.commons/commons-compress/1.12/84caa68576e345eb5e7ae61a0e5a9229eb100d7b/commons-compress-1.12.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.apache.commons/commons-compress/1.12/84caa68576e345eb5e7ae61a0e5a9229eb100d7b/commons-compress-1.12.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.apache.commons/commons-compress/1.12/84caa68576e345eb5e7ae61a0e5a9229eb100d7b/commons-compress-1.12.jar</p>
<p>
Dependency Hierarchy:
- lint-gradle-27.2.1.jar (Root Library)
- builder-4.2.1.jar
- sdklib-27.2.1.jar
- :x: **commons-compress-1.12.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/nexmo-community/client-sdk-tutorials/commit/691e25809d42cce5a487504aa376638500c5b492">691e25809d42cce5a487504aa376638500c5b492</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
When reading a specially crafted TAR archive, Compress can be made to allocate large amounts of memory that finally leads to an out of memory error even for very small inputs. This could be used to mount a denial of service attack against services that use Compress' tar package.
<p>Publish Date: 2021-07-13
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-35517>CVE-2021-35517</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>7.5</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://commons.apache.org/proper/commons-compress/security-reports.html">https://commons.apache.org/proper/commons-compress/security-reports.html</a></p>
<p>Release Date: 2021-07-13</p>
<p>Fix Resolution: org.apache.commons:commons-compress:1.21</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2021-35516</summary>
### Vulnerable Library - <b>commons-compress-1.12.jar</b></p>
<p>Apache Commons Compress software defines an API for working with
compression and archive formats. These include: bzip2, gzip, pack200,
lzma, xz, Snappy, traditional Unix Compress, DEFLATE and ar, cpio,
jar, tar, zip, dump, 7z, arj.</p>
<p>Path to dependency file: /app-to-phone-java/app-to-phone/app/build.gradle</p>
<p>Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.apache.commons/commons-compress/1.12/84caa68576e345eb5e7ae61a0e5a9229eb100d7b/commons-compress-1.12.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.apache.commons/commons-compress/1.12/84caa68576e345eb5e7ae61a0e5a9229eb100d7b/commons-compress-1.12.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.apache.commons/commons-compress/1.12/84caa68576e345eb5e7ae61a0e5a9229eb100d7b/commons-compress-1.12.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.apache.commons/commons-compress/1.12/84caa68576e345eb5e7ae61a0e5a9229eb100d7b/commons-compress-1.12.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.apache.commons/commons-compress/1.12/84caa68576e345eb5e7ae61a0e5a9229eb100d7b/commons-compress-1.12.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.apache.commons/commons-compress/1.12/84caa68576e345eb5e7ae61a0e5a9229eb100d7b/commons-compress-1.12.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.apache.commons/commons-compress/1.12/84caa68576e345eb5e7ae61a0e5a9229eb100d7b/commons-compress-1.12.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.apache.commons/commons-compress/1.12/84caa68576e345eb5e7ae61a0e5a9229eb100d7b/commons-compress-1.12.jar</p>
<p>
Dependency Hierarchy:
- lint-gradle-27.2.1.jar (Root Library)
- builder-4.2.1.jar
- sdklib-27.2.1.jar
- :x: **commons-compress-1.12.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/nexmo-community/client-sdk-tutorials/commit/691e25809d42cce5a487504aa376638500c5b492">691e25809d42cce5a487504aa376638500c5b492</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
When reading a specially crafted 7Z archive, Compress can be made to allocate large amounts of memory that finally leads to an out of memory error even for very small inputs. This could be used to mount a denial of service attack against services that use Compress' sevenz package.
<p>Publish Date: 2021-07-13
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-35516>CVE-2021-35516</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>7.5</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://commons.apache.org/proper/commons-compress/security-reports.html">https://commons.apache.org/proper/commons-compress/security-reports.html</a></p>
<p>Release Date: 2021-07-13</p>
<p>Fix Resolution: org.apache.commons:commons-compress:1.21</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2021-35515</summary>
### Vulnerable Library - <b>commons-compress-1.12.jar</b></p>
<p>Apache Commons Compress software defines an API for working with
compression and archive formats. These include: bzip2, gzip, pack200,
lzma, xz, Snappy, traditional Unix Compress, DEFLATE and ar, cpio,
jar, tar, zip, dump, 7z, arj.</p>
<p>Path to dependency file: /app-to-phone-java/app-to-phone/app/build.gradle</p>
<p>Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.apache.commons/commons-compress/1.12/84caa68576e345eb5e7ae61a0e5a9229eb100d7b/commons-compress-1.12.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.apache.commons/commons-compress/1.12/84caa68576e345eb5e7ae61a0e5a9229eb100d7b/commons-compress-1.12.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.apache.commons/commons-compress/1.12/84caa68576e345eb5e7ae61a0e5a9229eb100d7b/commons-compress-1.12.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.apache.commons/commons-compress/1.12/84caa68576e345eb5e7ae61a0e5a9229eb100d7b/commons-compress-1.12.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.apache.commons/commons-compress/1.12/84caa68576e345eb5e7ae61a0e5a9229eb100d7b/commons-compress-1.12.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.apache.commons/commons-compress/1.12/84caa68576e345eb5e7ae61a0e5a9229eb100d7b/commons-compress-1.12.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.apache.commons/commons-compress/1.12/84caa68576e345eb5e7ae61a0e5a9229eb100d7b/commons-compress-1.12.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.apache.commons/commons-compress/1.12/84caa68576e345eb5e7ae61a0e5a9229eb100d7b/commons-compress-1.12.jar</p>
<p>
Dependency Hierarchy:
- lint-gradle-27.2.1.jar (Root Library)
- builder-4.2.1.jar
- sdklib-27.2.1.jar
- :x: **commons-compress-1.12.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/nexmo-community/client-sdk-tutorials/commit/691e25809d42cce5a487504aa376638500c5b492">691e25809d42cce5a487504aa376638500c5b492</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
When reading a specially crafted 7Z archive, the construction of the list of codecs that decompress an entry can result in an infinite loop. This could be used to mount a denial of service attack against services that use Compress' sevenz package.
<p>Publish Date: 2021-07-13
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-35515>CVE-2021-35515</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>7.5</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://commons.apache.org/proper/commons-compress/security-reports.html">https://commons.apache.org/proper/commons-compress/security-reports.html</a></p>
<p>Release Date: 2021-07-13</p>
<p>Fix Resolution: org.apache.commons:commons-compress:1.21</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2022-23437</summary>
### Vulnerable Library - <b>xercesImpl-2.12.0.jar</b></p>
<p>Xerces2 is the next generation of high performance, fully compliant XML parsers in the Apache Xerces family. This new version of Xerces introduces the Xerces Native Interface (XNI), a complete framework for building parser components and configurations that is extremely modular and easy to program.
The Apache Xerces2 parser is the reference implementation of XNI but other parser components, configurations, and parsers can be written using the Xerces Native Interface. For complete design and implementation documents, refer to the XNI Manual.
Xerces2 is a fully conforming XML Schema 1.0 processor. A partial experimental implementation of the XML Schema 1.1 Structures and Datatypes Working Drafts (December 2009) and an experimental implementation of the XML Schema Definition Language (XSD): Component Designators (SCD) Candidate Recommendation (January 2010) are provided for evaluation. For more information, refer to the XML Schema page.
Xerces2 also provides a complete implementation of the Document Object Model Level 3 Core and Load/Save W3C Recommendations and provides a complete implementation of the XML Inclusions (XInclude) W3C Recommendation. It also provides support for OASIS XML Catalogs v1.1.
Xerces2 is able to parse documents written according to the XML 1.1 Recommendation, except that it does not yet provide an option to enable normalization checking as described in section 2.13 of this specification. It also handles namespaces according to the XML Namespaces 1.1 Recommendation, and will correctly serialize XML 1.1 documents if the DOM level 3 load/save APIs are in use.</p>
<p>Library home page: <a href="https://xerces.apache.org/xerces2-j/">https://xerces.apache.org/xerces2-j/</a></p>
<p>Path to dependency file: /app-to-phone-java/app-to-phone/app/build.gradle</p>
<p>Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/xerces/xercesImpl/2.12.0/f02c844149fd306601f20e0b34853a670bef7fa2/xercesImpl-2.12.0.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/xerces/xercesImpl/2.12.0/f02c844149fd306601f20e0b34853a670bef7fa2/xercesImpl-2.12.0.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/xerces/xercesImpl/2.12.0/f02c844149fd306601f20e0b34853a670bef7fa2/xercesImpl-2.12.0.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/xerces/xercesImpl/2.12.0/f02c844149fd306601f20e0b34853a670bef7fa2/xercesImpl-2.12.0.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/xerces/xercesImpl/2.12.0/f02c844149fd306601f20e0b34853a670bef7fa2/xercesImpl-2.12.0.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/xerces/xercesImpl/2.12.0/f02c844149fd306601f20e0b34853a670bef7fa2/xercesImpl-2.12.0.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/xerces/xercesImpl/2.12.0/f02c844149fd306601f20e0b34853a670bef7fa2/xercesImpl-2.12.0.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/xerces/xercesImpl/2.12.0/f02c844149fd306601f20e0b34853a670bef7fa2/xercesImpl-2.12.0.jar</p>
<p>
Dependency Hierarchy:
- lint-gradle-27.2.1.jar (Root Library)
- sdk-common-27.2.1.jar
- :x: **xercesImpl-2.12.0.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/nexmo-community/client-sdk-tutorials/commit/691e25809d42cce5a487504aa376638500c5b492">691e25809d42cce5a487504aa376638500c5b492</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
There's a vulnerability within the Apache Xerces Java (XercesJ) XML parser when handling specially crafted XML document payloads. This causes, the XercesJ XML parser to wait in an infinite loop, which may sometimes consume system resources for prolonged duration. This vulnerability is present within XercesJ version 2.12.1 and the previous versions.
<p>Publish Date: 2022-01-24
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-23437>CVE-2022-23437</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>6.5</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: 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>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/advisories/GHSA-h65f-jvqw-m9fj">https://github.com/advisories/GHSA-h65f-jvqw-m9fj</a></p>
<p>Release Date: 2022-01-24</p>
<p>Fix Resolution: xerces:xercesImpl:2.12.2</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> WS-2019-0379</summary>
### Vulnerable Library - <b>commons-codec-1.10.jar</b></p>
<p>The Apache Commons Codec package contains simple encoder and decoders for
various formats such as Base64 and Hexadecimal. In addition to these
widely used encoders and decoders, the codec package also maintains a
collection of phonetic encoding utilities.</p>
<p>Path to dependency file: /app-to-app-java/app-to-app/app/build.gradle</p>
<p>Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/commons-codec/commons-codec/1.10/4b95f4897fa13f2cd904aee711aeafc0c5295cd8/commons-codec-1.10.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/commons-codec/commons-codec/1.10/4b95f4897fa13f2cd904aee711aeafc0c5295cd8/commons-codec-1.10.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/commons-codec/commons-codec/1.10/4b95f4897fa13f2cd904aee711aeafc0c5295cd8/commons-codec-1.10.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/commons-codec/commons-codec/1.10/4b95f4897fa13f2cd904aee711aeafc0c5295cd8/commons-codec-1.10.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/commons-codec/commons-codec/1.10/4b95f4897fa13f2cd904aee711aeafc0c5295cd8/commons-codec-1.10.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/commons-codec/commons-codec/1.10/4b95f4897fa13f2cd904aee711aeafc0c5295cd8/commons-codec-1.10.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/commons-codec/commons-codec/1.10/4b95f4897fa13f2cd904aee711aeafc0c5295cd8/commons-codec-1.10.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/commons-codec/commons-codec/1.10/4b95f4897fa13f2cd904aee711aeafc0c5295cd8/commons-codec-1.10.jar</p>
<p>
Dependency Hierarchy:
- lint-gradle-27.2.1.jar (Root Library)
- builder-4.2.1.jar
- sdklib-27.2.1.jar
- httpmime-4.5.6.jar
- httpclient-4.5.6.jar
- :x: **commons-codec-1.10.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/nexmo-community/client-sdk-tutorials/commit/691e25809d42cce5a487504aa376638500c5b492">691e25809d42cce5a487504aa376638500c5b492</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
Apache commons-codec before version “commons-codec-1.13-RC1” is vulnerable to information disclosure due to Improper Input validation.
<p>Publish Date: 2019-05-20
<p>URL: <a href=https://github.com/apache/commons-codec/commit/48b615756d1d770091ea3322eefc08011ee8b113>WS-2019-0379</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>6.5</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: Low
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Release Date: 2019-05-20</p>
<p>Fix Resolution: commons-codec:commons-codec:1.13</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2020-15522</summary>
### Vulnerable Library - <b>bcprov-jdk15on-1.56.jar</b></p>
<p>The Bouncy Castle Crypto package is a Java implementation of cryptographic algorithms. This jar contains JCE provider and lightweight API for the Bouncy Castle Cryptography APIs for JDK 1.5 to JDK 1.8.</p>
<p>Library home page: <a href="http://www.bouncycastle.org/java.html">http://www.bouncycastle.org/java.html</a></p>
<p>Path to dependency file: /app-to-phone-java/app-to-phone/app/build.gradle</p>
<p>Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.bouncycastle/bcprov-jdk15on/1.56/a153c6f9744a3e9dd6feab5e210e1c9861362ec7/bcprov-jdk15on-1.56.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.bouncycastle/bcprov-jdk15on/1.56/a153c6f9744a3e9dd6feab5e210e1c9861362ec7/bcprov-jdk15on-1.56.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.bouncycastle/bcprov-jdk15on/1.56/a153c6f9744a3e9dd6feab5e210e1c9861362ec7/bcprov-jdk15on-1.56.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.bouncycastle/bcprov-jdk15on/1.56/a153c6f9744a3e9dd6feab5e210e1c9861362ec7/bcprov-jdk15on-1.56.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.bouncycastle/bcprov-jdk15on/1.56/a153c6f9744a3e9dd6feab5e210e1c9861362ec7/bcprov-jdk15on-1.56.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.bouncycastle/bcprov-jdk15on/1.56/a153c6f9744a3e9dd6feab5e210e1c9861362ec7/bcprov-jdk15on-1.56.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.bouncycastle/bcprov-jdk15on/1.56/a153c6f9744a3e9dd6feab5e210e1c9861362ec7/bcprov-jdk15on-1.56.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.bouncycastle/bcprov-jdk15on/1.56/a153c6f9744a3e9dd6feab5e210e1c9861362ec7/bcprov-jdk15on-1.56.jar</p>
<p>
Dependency Hierarchy:
- lint-gradle-27.2.1.jar (Root Library)
- builder-4.2.1.jar
- :x: **bcprov-jdk15on-1.56.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/nexmo-community/client-sdk-tutorials/commit/691e25809d42cce5a487504aa376638500c5b492">691e25809d42cce5a487504aa376638500c5b492</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
Bouncy Castle BC Java before 1.66, BC C# .NET before 1.8.7, BC-FJA before 1.0.1.2, 1.0.2.1, and BC-FNA before 1.0.1.1 have a timing issue within the EC math library that can expose information about the private key when an attacker is able to observe timing information for the generation of multiple deterministic ECDSA signatures.
<p>Publish Date: 2021-05-20
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-15522>CVE-2020-15522</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>5.9</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: None
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-15522">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-15522</a></p>
<p>Release Date: 2021-05-20</p>
<p>Fix Resolution: C#- release-1.8.7, Java- 1.66</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2022-3171</summary>
### Vulnerable Library - <b>protobuf-java-3.10.0.jar</b></p>
<p>Core Protocol Buffers library. Protocol Buffers are a way of encoding structured data in an
efficient yet extensible format.</p>
<p>Library home page: <a href="https://developers.google.com/protocol-buffers/">https://developers.google.com/protocol-buffers/</a></p>
<p>Path to dependency file: /in-app-messaging-java/app/build.gradle</p>
<p>Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/com.google.protobuf/protobuf-java/3.10.0/410b61dd0088aab4caa05739558d43df248958c9/protobuf-java-3.10.0.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/com.google.protobuf/protobuf-java/3.10.0/410b61dd0088aab4caa05739558d43df248958c9/protobuf-java-3.10.0.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/com.google.protobuf/protobuf-java/3.10.0/410b61dd0088aab4caa05739558d43df248958c9/protobuf-java-3.10.0.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/com.google.protobuf/protobuf-java/3.10.0/410b61dd0088aab4caa05739558d43df248958c9/protobuf-java-3.10.0.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/com.google.protobuf/protobuf-java/3.10.0/410b61dd0088aab4caa05739558d43df248958c9/protobuf-java-3.10.0.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/com.google.protobuf/protobuf-java/3.10.0/410b61dd0088aab4caa05739558d43df248958c9/protobuf-java-3.10.0.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/com.google.protobuf/protobuf-java/3.10.0/410b61dd0088aab4caa05739558d43df248958c9/protobuf-java-3.10.0.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/com.google.protobuf/protobuf-java/3.10.0/410b61dd0088aab4caa05739558d43df248958c9/protobuf-java-3.10.0.jar</p>
<p>
Dependency Hierarchy:
- lint-gradle-27.2.1.jar (Root Library)
- builder-4.2.1.jar
- protos-27.2.1.jar
- :x: **protobuf-java-3.10.0.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/nexmo-community/client-sdk-tutorials/commit/691e25809d42cce5a487504aa376638500c5b492">691e25809d42cce5a487504aa376638500c5b492</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
A potential Denial of Service issue in protobuf-java core and lite was discovered in the parsing procedure for binary and text format data. Input streams containing multiple instances of non-repeated embedded messages with repeated or unknown fields cause objects to be converted back-n-forth between mutable and immutable forms, resulting in potentially long garbage collection pauses.
This issue was fixed In the following version:
protobuf-java (3.21.7, 3.20.3, 3.19.6, 3.16.3)
protobuf-javalite (3.21.7, 3.20.3, 3.19.6, 3.16.3)
protobuf-kotlin (3.21.7, 3.20.3, 3.19.6)
protobuf-kotlin-lite (3.21.7, 3.20.3, 3.19.6)
google-protobuf [JRuby gem only] (3.21.7, 3.20.3, 3.19.6)
<p>Publish Date: 2022-09-10
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-3171>CVE-2022-3171</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>5.7</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Adjacent
- 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>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/advisories/GHSA-h4h5-3hr4-j3g2">https://github.com/advisories/GHSA-h4h5-3hr4-j3g2</a></p>
<p>Release Date: 2022-09-10</p>
<p>Fix Resolution: com.google.protobuf:protobuf-java:3.16.3,3.19.6,3.20.3,3.21.7;com.google.protobuf:protobuf-javalite:3.16.3,3.19.6,3.20.3,3.21.7;com.google.protobuf:protobuf-kotlin:3.19.6,3.20.3,3.21.7;com.google.protobuf:protobuf-kotlin-lite:3.19.6,3.20.3,3.21.7;google-protobuf - 3.19.6,3.20.3,3.21.7</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2021-22569</summary>
### Vulnerable Library - <b>protobuf-java-3.10.0.jar</b></p>
<p>Core Protocol Buffers library. Protocol Buffers are a way of encoding structured data in an
efficient yet extensible format.</p>
<p>Library home page: <a href="https://developers.google.com/protocol-buffers/">https://developers.google.com/protocol-buffers/</a></p>
<p>Path to dependency file: /in-app-messaging-java/app/build.gradle</p>
<p>Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/com.google.protobuf/protobuf-java/3.10.0/410b61dd0088aab4caa05739558d43df248958c9/protobuf-java-3.10.0.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/com.google.protobuf/protobuf-java/3.10.0/410b61dd0088aab4caa05739558d43df248958c9/protobuf-java-3.10.0.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/com.google.protobuf/protobuf-java/3.10.0/410b61dd0088aab4caa05739558d43df248958c9/protobuf-java-3.10.0.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/com.google.protobuf/protobuf-java/3.10.0/410b61dd0088aab4caa05739558d43df248958c9/protobuf-java-3.10.0.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/com.google.protobuf/protobuf-java/3.10.0/410b61dd0088aab4caa05739558d43df248958c9/protobuf-java-3.10.0.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/com.google.protobuf/protobuf-java/3.10.0/410b61dd0088aab4caa05739558d43df248958c9/protobuf-java-3.10.0.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/com.google.protobuf/protobuf-java/3.10.0/410b61dd0088aab4caa05739558d43df248958c9/protobuf-java-3.10.0.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/com.google.protobuf/protobuf-java/3.10.0/410b61dd0088aab4caa05739558d43df248958c9/protobuf-java-3.10.0.jar</p>
<p>
Dependency Hierarchy:
- lint-gradle-27.2.1.jar (Root Library)
- builder-4.2.1.jar
- protos-27.2.1.jar
- :x: **protobuf-java-3.10.0.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/nexmo-community/client-sdk-tutorials/commit/691e25809d42cce5a487504aa376638500c5b492">691e25809d42cce5a487504aa376638500c5b492</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
An issue in protobuf-java allowed the interleaving of com.google.protobuf.UnknownFieldSet fields in such a way that would be processed out of order. A small malicious payload can occupy the parser for several minutes by creating large numbers of short-lived objects that cause frequent, repeated pauses. We recommend upgrading libraries beyond the vulnerable versions.
<p>Publish Date: 2022-01-10
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-22569>CVE-2021-22569</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>5.5</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/advisories/GHSA-wrvw-hg22-4m67">https://github.com/advisories/GHSA-wrvw-hg22-4m67</a></p>
<p>Release Date: 2022-01-10</p>
<p>Fix Resolution: com.google.protobuf:protobuf-java:3.16.1,3.18.2,3.19.2; com.google.protobuf:protobuf-kotlin:3.18.2,3.19.2; google-protobuf - 3.19.2</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2020-17521</summary>
### Vulnerable Library - <b>groovy-all-2.4.15.jar</b></p>
<p>Groovy: A powerful, dynamic language for the JVM</p>
<p>Library home page: <a href="http://groovy-lang.org">http://groovy-lang.org</a></p>
<p>Path to dependency file: /in-app-messaging-java/app/build.gradle</p>
<p>Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.codehaus.groovy/groovy-all/2.4.15/423a17aeb2f64bc6f76e8e44265a548bec80fd42/groovy-all-2.4.15.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.codehaus.groovy/groovy-all/2.4.15/423a17aeb2f64bc6f76e8e44265a548bec80fd42/groovy-all-2.4.15.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.codehaus.groovy/groovy-all/2.4.15/423a17aeb2f64bc6f76e8e44265a548bec80fd42/groovy-all-2.4.15.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.codehaus.groovy/groovy-all/2.4.15/423a17aeb2f64bc6f76e8e44265a548bec80fd42/groovy-all-2.4.15.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.codehaus.groovy/groovy-all/2.4.15/423a17aeb2f64bc6f76e8e44265a548bec80fd42/groovy-all-2.4.15.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.codehaus.groovy/groovy-all/2.4.15/423a17aeb2f64bc6f76e8e44265a548bec80fd42/groovy-all-2.4.15.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.codehaus.groovy/groovy-all/2.4.15/423a17aeb2f64bc6f76e8e44265a548bec80fd42/groovy-all-2.4.15.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.codehaus.groovy/groovy-all/2.4.15/423a17aeb2f64bc6f76e8e44265a548bec80fd42/groovy-all-2.4.15.jar</p>
<p>
Dependency Hierarchy:
- lint-gradle-27.2.1.jar (Root Library)
- :x: **groovy-all-2.4.15.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/nexmo-community/client-sdk-tutorials/commit/691e25809d42cce5a487504aa376638500c5b492">691e25809d42cce5a487504aa376638500c5b492</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
Apache Groovy provides extension methods to aid with creating temporary directories. Prior to this fix, Groovy's implementation of those extension methods was using a now superseded Java JDK method call that is potentially not secure on some operating systems in some contexts. Users not using the extension methods mentioned in the advisory are not affected, but may wish to read the advisory for further details. Versions Affected: 2.0 to 2.4.20, 2.5.0 to 2.5.13, 3.0.0 to 3.0.6, and 4.0.0-alpha-1. Fixed in versions 2.4.21, 2.5.14, 3.0.7, 4.0.0-alpha-2.
<p>Publish Date: 2020-12-07
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-17521>CVE-2020-17521</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>5.5</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: None
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://issues.apache.org/jira/browse/GROOVY-9824">https://issues.apache.org/jira/browse/GROOVY-9824</a></p>
<p>Release Date: 2020-12-07</p>
<p>Fix Resolution: org.codehaus.groovy:groovy-all:2.4.21,2.5.14,3.0.7</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2018-11771</summary>
### Vulnerable Library - <b>commons-compress-1.12.jar</b></p>
<p>Apache Commons Compress software defines an API for working with
compression and archive formats. These include: bzip2, gzip, pack200,
lzma, xz, Snappy, traditional Unix Compress, DEFLATE and ar, cpio,
jar, tar, zip, dump, 7z, arj.</p>
<p>Path to dependency file: /app-to-phone-java/app-to-phone/app/build.gradle</p>
<p>Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.apache.commons/commons-compress/1.12/84caa68576e345eb5e7ae61a0e5a9229eb100d7b/commons-compress-1.12.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.apache.commons/commons-compress/1.12/84caa68576e345eb5e7ae61a0e5a9229eb100d7b/commons-compress-1.12.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.apache.commons/commons-compress/1.12/84caa68576e345eb5e7ae61a0e5a9229eb100d7b/commons-compress-1.12.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.apache.commons/commons-compress/1.12/84caa68576e345eb5e7ae61a0e5a9229eb100d7b/commons-compress-1.12.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.apache.commons/commons-compress/1.12/84caa68576e345eb5e7ae61a0e5a9229eb100d7b/commons-compress-1.12.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.apache.commons/commons-compress/1.12/84caa68576e345eb5e7ae61a0e5a9229eb100d7b/commons-compress-1.12.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.apache.commons/commons-compress/1.12/84caa68576e345eb5e7ae61a0e5a9229eb100d7b/commons-compress-1.12.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.apache.commons/commons-compress/1.12/84caa68576e345eb5e7ae61a0e5a9229eb100d7b/commons-compress-1.12.jar</p>
<p>
Dependency Hierarchy:
- lint-gradle-27.2.1.jar (Root Library)
- builder-4.2.1.jar
- sdklib-27.2.1.jar
- :x: **commons-compress-1.12.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/nexmo-community/client-sdk-tutorials/commit/691e25809d42cce5a487504aa376638500c5b492">691e25809d42cce5a487504aa376638500c5b492</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
When reading a specially crafted ZIP archive, the read method of Apache Commons Compress 1.7 to 1.17's ZipArchiveInputStream can fail to return the correct EOF indication after the end of the stream has been reached. When combined with a java.io.InputStreamReader this can lead to an infinite stream, which can be used to mount a denial of service attack against services that use Compress' zip package.
<p>Publish Date: 2018-08-16
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-11771>CVE-2018-11771</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>5.5</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-11771">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-11771</a></p>
<p>Release Date: 2018-08-16</p>
<p>Fix Resolution: 1.18</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2018-1324</summary>
### Vulnerable Library - <b>commons-compress-1.12.jar</b></p>
<p>Apache Commons Compress software defines an API for working with
compression and archive formats. These include: bzip2, gzip, pack200,
lzma, xz, Snappy, traditional Unix Compress, DEFLATE and ar, cpio,
jar, tar, zip, dump, 7z, arj.</p>
<p>Path to dependency file: /app-to-phone-java/app-to-phone/app/build.gradle</p>
<p>Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.apache.commons/commons-compress/1.12/84caa68576e345eb5e7ae61a0e5a9229eb100d7b/commons-compress-1.12.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.apache.commons/commons-compress/1.12/84caa68576e345eb5e7ae61a0e5a9229eb100d7b/commons-compress-1.12.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.apache.commons/commons-compress/1.12/84caa68576e345eb5e7ae61a0e5a9229eb100d7b/commons-compress-1.12.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.apache.commons/commons-compress/1.12/84caa68576e345eb5e7ae61a0e5a9229eb100d7b/commons-compress-1.12.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.apache.commons/commons-compress/1.12/84caa68576e345eb5e7ae61a0e5a9229eb100d7b/commons-compress-1.12.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.apache.commons/commons-compress/1.12/84caa68576e345eb5e7ae61a0e5a9229eb100d7b/commons-compress-1.12.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.apache.commons/commons-compress/1.12/84caa68576e345eb5e7ae61a0e5a9229eb100d7b/commons-compress-1.12.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.apache.commons/commons-compress/1.12/84caa68576e345eb5e7ae61a0e5a9229eb100d7b/commons-compress-1.12.jar</p>
<p>
Dependency Hierarchy:
- lint-gradle-27.2.1.jar (Root Library)
- builder-4.2.1.jar
- sdklib-27.2.1.jar
- :x: **commons-compress-1.12.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/nexmo-community/client-sdk-tutorials/commit/691e25809d42cce5a487504aa376638500c5b492">691e25809d42cce5a487504aa376638500c5b492</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
A specially crafted ZIP archive can be used to cause an infinite loop inside of Apache Commons Compress' extra field parser used by the ZipFile and ZipArchiveInputStream classes in versions 1.11 to 1.15. This can be used to mount a denial of service attack against services that use Compress' zip package.
<p>Publish Date: 2018-03-16
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-1324>CVE-2018-1324</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>5.5</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-1324">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-1324</a></p>
<p>Release Date: 2018-03-16</p>
<p>Fix Resolution: 1.16</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2022-24329</summary>
### Vulnerable Library - <b>kotlin-stdlib-1.4.31.jar</b></p>
<p>Kotlin Standard Library for JVM</p>
<p>Library home page: <a href="https://kotlinlang.org/">https://kotlinlang.org/</a></p>
<p>Path to dependency file: /in-app-messaging-java/app/build.gradle</p>
<p>Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.jetbrains.kotlin/kotlin-stdlib/1.4.31/a58e0fb9812a6a93ca24b5da75e4b5a0cb89c957/kotlin-stdlib-1.4.31.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.jetbrains.kotlin/kotlin-stdlib/1.4.31/a58e0fb9812a6a93ca24b5da75e4b5a0cb89c957/kotlin-stdlib-1.4.31.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.jetbrains.kotlin/kotlin-stdlib/1.4.31/a58e0fb9812a6a93ca24b5da75e4b5a0cb89c957/kotlin-stdlib-1.4.31.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.jetbrains.kotlin/kotlin-stdlib/1.4.31/a58e0fb9812a6a93ca24b5da75e4b5a0cb89c957/kotlin-stdlib-1.4.31.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.jetbrains.kotlin/kotlin-stdlib/1.4.31/a58e0fb9812a6a93ca24b5da75e4b5a0cb89c957/kotlin-stdlib-1.4.31.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.jetbrains.kotlin/kotlin-stdlib/1.4.31/a58e0fb9812a6a93ca24b5da75e4b5a0cb89c957/kotlin-stdlib-1.4.31.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.jetbrains.kotlin/kotlin-stdlib/1.4.31/a58e0fb9812a6a93ca24b5da75e4b5a0cb89c957/kotlin-stdlib-1.4.31.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.jetbrains.kotlin/kotlin-stdlib/1.4.31/a58e0fb9812a6a93ca24b5da75e4b5a0cb89c957/kotlin-stdlib-1.4.31.jar</p>
<p>
Dependency Hierarchy:
- lint-gradle-27.2.1.jar (Root Library)
- kotlin-stdlib-jdk8-1.4.31.jar
- :x: **kotlin-stdlib-1.4.31.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/nexmo-community/client-sdk-tutorials/commit/691e25809d42cce5a487504aa376638500c5b492">691e25809d42cce5a487504aa376638500c5b492</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
In JetBrains Kotlin before 1.6.0, it was not possible to lock dependencies for Multiplatform Gradle Projects.
<p>Publish Date: 2022-02-25
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-24329>CVE-2022-24329</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>5.3</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: Low
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/advisories/GHSA-2qp4-g3q3-f92w">https://github.com/advisories/GHSA-2qp4-g3q3-f92w</a></p>
<p>Release Date: 2022-02-25</p>
<p>Fix Resolution: org.jetbrains.kotlin:kotlin-stdlib:1.6.0</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2018-1000180</summary>
### Vulnerable Library - <b>bcprov-jdk15on-1.56.jar</b></p>
<p>The Bouncy Castle Crypto package is a Java implementation of cryptographic algorithms. This jar contains JCE provider and lightweight API for the Bouncy Castle Cryptography APIs for JDK 1.5 to JDK 1.8.</p>
<p>Library home page: <a href="http://www.bouncycastle.org/java.html">http://www.bouncycastle.org/java.html</a></p>
<p>Path to dependency file: /app-to-phone-java/app-to-phone/app/build.gradle</p>
<p>Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.bouncycastle/bcprov-jdk15on/1.56/a153c6f9744a3e9dd6feab5e210e1c9861362ec7/bcprov-jdk15on-1.56.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.bouncycastle/bcprov-jdk15on/1.56/a153c6f9744a3e9dd6feab5e210e1c9861362ec7/bcprov-jdk15on-1.56.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.bouncycastle/bcprov-jdk15on/1.56/a153c6f9744a3e9dd6feab5e210e1c9861362ec7/bcprov-jdk15on-1.56.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.bouncycastle/bcprov-jdk15on/1.56/a153c6f9744a3e9dd6feab5e210e1c9861362ec7/bcprov-jdk15on-1.56.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.bouncycastle/bcprov-jdk15on/1.56/a153c6f9744a3e9dd6feab5e210e1c9861362ec7/bcprov-jdk15on-1.56.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.bouncycastle/bcprov-jdk15on/1.56/a153c6f9744a3e9dd6feab5e210e1c9861362ec7/bcprov-jdk15on-1.56.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.bouncycastle/bcprov-jdk15on/1.56/a153c6f9744a3e9dd6feab5e210e1c9861362ec7/bcprov-jdk15on-1.56.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.bouncycastle/bcprov-jdk15on/1.56/a153c6f9744a3e9dd6feab5e210e1c9861362ec7/bcprov-jdk15on-1.56.jar</p>
<p>
Dependency Hierarchy:
- lint-gradle-27.2.1.jar (Root Library)
- builder-4.2.1.jar
- :x: **bcprov-jdk15on-1.56.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/nexmo-community/client-sdk-tutorials/commit/691e25809d42cce5a487504aa376638500c5b492">691e25809d42cce5a487504aa376638500c5b492</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
Bouncy Castle BC 1.54 - 1.59, BC-FJA 1.0.0, BC-FJA 1.0.1 and earlier have a flaw in the Low-level interface to RSA key pair generator, specifically RSA Key Pairs generated in low-level API with added certainty may have less M-R tests than expected. This appears to be fixed in versions BC 1.60 beta 4 and later, BC-FJA 1.0.2 and later.
<p>Publish Date: 2018-06-05
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-1000180>CVE-2018-1000180</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>5.3</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: None
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-1000180">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-1000180</a></p>
<p>Release Date: 2018-06-05</p>
<p>Fix Resolution: org.bouncycastle:bc-fips:1.0.2;org.bouncycastle:bcprov-jdk15on:1.60;org.bouncycastle:bcprov-jdk14:1.60;org.bouncycastle:bcprov-ext-jdk14:1.60;org.bouncycastle:bcprov-ext-jdk15on:1.60;org.bouncycastle:bcprov-debug-jdk14:1.60;org.bouncycastle:bcprov-debug-jdk15on:1.60</p>
</p>
<p></p>
</details> | True | lint-gradle-27.2.1.jar: 18 vulnerabilities (highest severity is: 7.5) - <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>lint-gradle-27.2.1.jar</b></p></summary>
<p></p>
<p>Path to dependency file: /app-to-app-java/app-to-app/app/build.gradle</p>
<p>Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/com.google.guava/guava/28.1-jre/b0e91dcb6a44ffb6221b5027e12a5cb34b841145/guava-28.1-jre.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/com.google.guava/guava/28.1-jre/b0e91dcb6a44ffb6221b5027e12a5cb34b841145/guava-28.1-jre.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/com.google.guava/guava/28.1-jre/b0e91dcb6a44ffb6221b5027e12a5cb34b841145/guava-28.1-jre.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/com.google.guava/guava/28.1-jre/b0e91dcb6a44ffb6221b5027e12a5cb34b841145/guava-28.1-jre.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/com.google.guava/guava/28.1-jre/b0e91dcb6a44ffb6221b5027e12a5cb34b841145/guava-28.1-jre.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/com.google.guava/guava/28.1-jre/b0e91dcb6a44ffb6221b5027e12a5cb34b841145/guava-28.1-jre.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/com.google.guava/guava/28.1-jre/b0e91dcb6a44ffb6221b5027e12a5cb34b841145/guava-28.1-jre.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/com.google.guava/guava/28.1-jre/b0e91dcb6a44ffb6221b5027e12a5cb34b841145/guava-28.1-jre.jar</p>
<p>
<p>Found in HEAD commit: <a href="https://github.com/nexmo-community/client-sdk-tutorials/commit/691e25809d42cce5a487504aa376638500c5b492">691e25809d42cce5a487504aa376638500c5b492</a></p></details>
## Vulnerabilities
| CVE | Severity | <img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS | Dependency | Type | Fixed in | Remediation Available |
| ------------- | ------------- | ----- | ----- | ----- | --- | --- |
| [CVE-2021-36090](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-36090) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | commons-compress-1.12.jar | Transitive | N/A | ❌ |
| [CVE-2019-17359](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-17359) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | bcprov-jdk15on-1.56.jar | Transitive | N/A | ❌ |
| [CVE-2021-35517](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-35517) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | commons-compress-1.12.jar | Transitive | N/A | ❌ |
| [CVE-2021-35516](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-35516) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | commons-compress-1.12.jar | Transitive | N/A | ❌ |
| [CVE-2021-35515](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-35515) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | commons-compress-1.12.jar | Transitive | N/A | ❌ |
| [CVE-2022-23437](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-23437) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 6.5 | xercesImpl-2.12.0.jar | Transitive | N/A | ❌ |
| [WS-2019-0379](https://github.com/apache/commons-codec/commit/48b615756d1d770091ea3322eefc08011ee8b113) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 6.5 | commons-codec-1.10.jar | Transitive | N/A | ❌ |
| [CVE-2020-15522](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-15522) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 5.9 | bcprov-jdk15on-1.56.jar | Transitive | N/A | ❌ |
| [CVE-2022-3171](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-3171) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 5.7 | protobuf-java-3.10.0.jar | Transitive | N/A | ❌ |
| [CVE-2021-22569](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-22569) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 5.5 | protobuf-java-3.10.0.jar | Transitive | N/A | ❌ |
| [CVE-2020-17521](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-17521) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 5.5 | groovy-all-2.4.15.jar | Transitive | N/A | ❌ |
| [CVE-2018-11771](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-11771) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 5.5 | commons-compress-1.12.jar | Transitive | N/A | ❌ |
| [CVE-2018-1324](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-1324) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 5.5 | commons-compress-1.12.jar | Transitive | N/A | ❌ |
| [CVE-2022-24329](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-24329) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 5.3 | kotlin-stdlib-1.4.31.jar | Transitive | N/A | ❌ |
| [CVE-2018-1000180](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-1000180) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 5.3 | bcprov-jdk15on-1.56.jar | Transitive | N/A | ❌ |
| [CVE-2020-13956](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-13956) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 5.3 | httpclient-4.5.6.jar | Transitive | N/A | ❌ |
| [CVE-2020-26939](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-26939) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 5.3 | bcprov-jdk15on-1.56.jar | Transitive | N/A | ❌ |
| [CVE-2020-8908](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-8908) | <img src='https://whitesource-resources.whitesourcesoftware.com/low_vul.png' width=19 height=20> Low | 3.3 | guava-28.1-jre.jar | Transitive | N/A | ❌ |
## Details
> Partial details (15 vulnerabilities) are displayed below due to a content size limitation in GitHub. To view information on the remaining vulnerabilities, navigate to the Mend Application.<br>
<details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2021-36090</summary>
### Vulnerable Library - <b>commons-compress-1.12.jar</b></p>
<p>Apache Commons Compress software defines an API for working with
compression and archive formats. These include: bzip2, gzip, pack200,
lzma, xz, Snappy, traditional Unix Compress, DEFLATE and ar, cpio,
jar, tar, zip, dump, 7z, arj.</p>
<p>Path to dependency file: /app-to-phone-java/app-to-phone/app/build.gradle</p>
<p>Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.apache.commons/commons-compress/1.12/84caa68576e345eb5e7ae61a0e5a9229eb100d7b/commons-compress-1.12.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.apache.commons/commons-compress/1.12/84caa68576e345eb5e7ae61a0e5a9229eb100d7b/commons-compress-1.12.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.apache.commons/commons-compress/1.12/84caa68576e345eb5e7ae61a0e5a9229eb100d7b/commons-compress-1.12.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.apache.commons/commons-compress/1.12/84caa68576e345eb5e7ae61a0e5a9229eb100d7b/commons-compress-1.12.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.apache.commons/commons-compress/1.12/84caa68576e345eb5e7ae61a0e5a9229eb100d7b/commons-compress-1.12.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.apache.commons/commons-compress/1.12/84caa68576e345eb5e7ae61a0e5a9229eb100d7b/commons-compress-1.12.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.apache.commons/commons-compress/1.12/84caa68576e345eb5e7ae61a0e5a9229eb100d7b/commons-compress-1.12.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.apache.commons/commons-compress/1.12/84caa68576e345eb5e7ae61a0e5a9229eb100d7b/commons-compress-1.12.jar</p>
<p>
Dependency Hierarchy:
- lint-gradle-27.2.1.jar (Root Library)
- builder-4.2.1.jar
- sdklib-27.2.1.jar
- :x: **commons-compress-1.12.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/nexmo-community/client-sdk-tutorials/commit/691e25809d42cce5a487504aa376638500c5b492">691e25809d42cce5a487504aa376638500c5b492</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
When reading a specially crafted ZIP archive, Compress can be made to allocate large amounts of memory that finally leads to an out of memory error even for very small inputs. This could be used to mount a denial of service attack against services that use Compress' zip package.
<p>Publish Date: 2021-07-13
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-36090>CVE-2021-36090</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>7.5</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://commons.apache.org/proper/commons-compress/security-reports.html">https://commons.apache.org/proper/commons-compress/security-reports.html</a></p>
<p>Release Date: 2021-07-13</p>
<p>Fix Resolution: org.apache.commons:commons-compress:1.21</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2019-17359</summary>
### Vulnerable Library - <b>bcprov-jdk15on-1.56.jar</b></p>
<p>The Bouncy Castle Crypto package is a Java implementation of cryptographic algorithms. This jar contains JCE provider and lightweight API for the Bouncy Castle Cryptography APIs for JDK 1.5 to JDK 1.8.</p>
<p>Library home page: <a href="http://www.bouncycastle.org/java.html">http://www.bouncycastle.org/java.html</a></p>
<p>Path to dependency file: /app-to-phone-java/app-to-phone/app/build.gradle</p>
<p>Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.bouncycastle/bcprov-jdk15on/1.56/a153c6f9744a3e9dd6feab5e210e1c9861362ec7/bcprov-jdk15on-1.56.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.bouncycastle/bcprov-jdk15on/1.56/a153c6f9744a3e9dd6feab5e210e1c9861362ec7/bcprov-jdk15on-1.56.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.bouncycastle/bcprov-jdk15on/1.56/a153c6f9744a3e9dd6feab5e210e1c9861362ec7/bcprov-jdk15on-1.56.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.bouncycastle/bcprov-jdk15on/1.56/a153c6f9744a3e9dd6feab5e210e1c9861362ec7/bcprov-jdk15on-1.56.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.bouncycastle/bcprov-jdk15on/1.56/a153c6f9744a3e9dd6feab5e210e1c9861362ec7/bcprov-jdk15on-1.56.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.bouncycastle/bcprov-jdk15on/1.56/a153c6f9744a3e9dd6feab5e210e1c9861362ec7/bcprov-jdk15on-1.56.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.bouncycastle/bcprov-jdk15on/1.56/a153c6f9744a3e9dd6feab5e210e1c9861362ec7/bcprov-jdk15on-1.56.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.bouncycastle/bcprov-jdk15on/1.56/a153c6f9744a3e9dd6feab5e210e1c9861362ec7/bcprov-jdk15on-1.56.jar</p>
<p>
Dependency Hierarchy:
- lint-gradle-27.2.1.jar (Root Library)
- builder-4.2.1.jar
- :x: **bcprov-jdk15on-1.56.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/nexmo-community/client-sdk-tutorials/commit/691e25809d42cce5a487504aa376638500c5b492">691e25809d42cce5a487504aa376638500c5b492</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
The ASN.1 parser in Bouncy Castle Crypto (aka BC Java) 1.63 can trigger a large attempted memory allocation, and resultant OutOfMemoryError error, via crafted ASN.1 data. This is fixed in 1.64.
<p>Publish Date: 2019-10-08
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-17359>CVE-2019-17359</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>7.5</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-17359">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-17359</a></p>
<p>Release Date: 2019-10-08</p>
<p>Fix Resolution: org.bouncycastle:bcprov-jdk15on:1.64</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2021-35517</summary>
### Vulnerable Library - <b>commons-compress-1.12.jar</b></p>
<p>Apache Commons Compress software defines an API for working with
compression and archive formats. These include: bzip2, gzip, pack200,
lzma, xz, Snappy, traditional Unix Compress, DEFLATE and ar, cpio,
jar, tar, zip, dump, 7z, arj.</p>
<p>Path to dependency file: /app-to-phone-java/app-to-phone/app/build.gradle</p>
<p>Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.apache.commons/commons-compress/1.12/84caa68576e345eb5e7ae61a0e5a9229eb100d7b/commons-compress-1.12.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.apache.commons/commons-compress/1.12/84caa68576e345eb5e7ae61a0e5a9229eb100d7b/commons-compress-1.12.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.apache.commons/commons-compress/1.12/84caa68576e345eb5e7ae61a0e5a9229eb100d7b/commons-compress-1.12.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.apache.commons/commons-compress/1.12/84caa68576e345eb5e7ae61a0e5a9229eb100d7b/commons-compress-1.12.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.apache.commons/commons-compress/1.12/84caa68576e345eb5e7ae61a0e5a9229eb100d7b/commons-compress-1.12.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.apache.commons/commons-compress/1.12/84caa68576e345eb5e7ae61a0e5a9229eb100d7b/commons-compress-1.12.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.apache.commons/commons-compress/1.12/84caa68576e345eb5e7ae61a0e5a9229eb100d7b/commons-compress-1.12.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.apache.commons/commons-compress/1.12/84caa68576e345eb5e7ae61a0e5a9229eb100d7b/commons-compress-1.12.jar</p>
<p>
Dependency Hierarchy:
- lint-gradle-27.2.1.jar (Root Library)
- builder-4.2.1.jar
- sdklib-27.2.1.jar
- :x: **commons-compress-1.12.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/nexmo-community/client-sdk-tutorials/commit/691e25809d42cce5a487504aa376638500c5b492">691e25809d42cce5a487504aa376638500c5b492</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
When reading a specially crafted TAR archive, Compress can be made to allocate large amounts of memory that finally leads to an out of memory error even for very small inputs. This could be used to mount a denial of service attack against services that use Compress' tar package.
<p>Publish Date: 2021-07-13
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-35517>CVE-2021-35517</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>7.5</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://commons.apache.org/proper/commons-compress/security-reports.html">https://commons.apache.org/proper/commons-compress/security-reports.html</a></p>
<p>Release Date: 2021-07-13</p>
<p>Fix Resolution: org.apache.commons:commons-compress:1.21</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2021-35516</summary>
### Vulnerable Library - <b>commons-compress-1.12.jar</b></p>
<p>Apache Commons Compress software defines an API for working with
compression and archive formats. These include: bzip2, gzip, pack200,
lzma, xz, Snappy, traditional Unix Compress, DEFLATE and ar, cpio,
jar, tar, zip, dump, 7z, arj.</p>
<p>Path to dependency file: /app-to-phone-java/app-to-phone/app/build.gradle</p>
<p>Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.apache.commons/commons-compress/1.12/84caa68576e345eb5e7ae61a0e5a9229eb100d7b/commons-compress-1.12.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.apache.commons/commons-compress/1.12/84caa68576e345eb5e7ae61a0e5a9229eb100d7b/commons-compress-1.12.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.apache.commons/commons-compress/1.12/84caa68576e345eb5e7ae61a0e5a9229eb100d7b/commons-compress-1.12.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.apache.commons/commons-compress/1.12/84caa68576e345eb5e7ae61a0e5a9229eb100d7b/commons-compress-1.12.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.apache.commons/commons-compress/1.12/84caa68576e345eb5e7ae61a0e5a9229eb100d7b/commons-compress-1.12.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.apache.commons/commons-compress/1.12/84caa68576e345eb5e7ae61a0e5a9229eb100d7b/commons-compress-1.12.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.apache.commons/commons-compress/1.12/84caa68576e345eb5e7ae61a0e5a9229eb100d7b/commons-compress-1.12.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.apache.commons/commons-compress/1.12/84caa68576e345eb5e7ae61a0e5a9229eb100d7b/commons-compress-1.12.jar</p>
<p>
Dependency Hierarchy:
- lint-gradle-27.2.1.jar (Root Library)
- builder-4.2.1.jar
- sdklib-27.2.1.jar
- :x: **commons-compress-1.12.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/nexmo-community/client-sdk-tutorials/commit/691e25809d42cce5a487504aa376638500c5b492">691e25809d42cce5a487504aa376638500c5b492</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
When reading a specially crafted 7Z archive, Compress can be made to allocate large amounts of memory that finally leads to an out of memory error even for very small inputs. This could be used to mount a denial of service attack against services that use Compress' sevenz package.
<p>Publish Date: 2021-07-13
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-35516>CVE-2021-35516</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>7.5</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://commons.apache.org/proper/commons-compress/security-reports.html">https://commons.apache.org/proper/commons-compress/security-reports.html</a></p>
<p>Release Date: 2021-07-13</p>
<p>Fix Resolution: org.apache.commons:commons-compress:1.21</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2021-35515</summary>
### Vulnerable Library - <b>commons-compress-1.12.jar</b></p>
<p>Apache Commons Compress software defines an API for working with
compression and archive formats. These include: bzip2, gzip, pack200,
lzma, xz, Snappy, traditional Unix Compress, DEFLATE and ar, cpio,
jar, tar, zip, dump, 7z, arj.</p>
<p>Path to dependency file: /app-to-phone-java/app-to-phone/app/build.gradle</p>
<p>Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.apache.commons/commons-compress/1.12/84caa68576e345eb5e7ae61a0e5a9229eb100d7b/commons-compress-1.12.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.apache.commons/commons-compress/1.12/84caa68576e345eb5e7ae61a0e5a9229eb100d7b/commons-compress-1.12.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.apache.commons/commons-compress/1.12/84caa68576e345eb5e7ae61a0e5a9229eb100d7b/commons-compress-1.12.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.apache.commons/commons-compress/1.12/84caa68576e345eb5e7ae61a0e5a9229eb100d7b/commons-compress-1.12.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.apache.commons/commons-compress/1.12/84caa68576e345eb5e7ae61a0e5a9229eb100d7b/commons-compress-1.12.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.apache.commons/commons-compress/1.12/84caa68576e345eb5e7ae61a0e5a9229eb100d7b/commons-compress-1.12.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.apache.commons/commons-compress/1.12/84caa68576e345eb5e7ae61a0e5a9229eb100d7b/commons-compress-1.12.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.apache.commons/commons-compress/1.12/84caa68576e345eb5e7ae61a0e5a9229eb100d7b/commons-compress-1.12.jar</p>
<p>
Dependency Hierarchy:
- lint-gradle-27.2.1.jar (Root Library)
- builder-4.2.1.jar
- sdklib-27.2.1.jar
- :x: **commons-compress-1.12.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/nexmo-community/client-sdk-tutorials/commit/691e25809d42cce5a487504aa376638500c5b492">691e25809d42cce5a487504aa376638500c5b492</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
When reading a specially crafted 7Z archive, the construction of the list of codecs that decompress an entry can result in an infinite loop. This could be used to mount a denial of service attack against services that use Compress' sevenz package.
<p>Publish Date: 2021-07-13
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-35515>CVE-2021-35515</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>7.5</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://commons.apache.org/proper/commons-compress/security-reports.html">https://commons.apache.org/proper/commons-compress/security-reports.html</a></p>
<p>Release Date: 2021-07-13</p>
<p>Fix Resolution: org.apache.commons:commons-compress:1.21</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2022-23437</summary>
### Vulnerable Library - <b>xercesImpl-2.12.0.jar</b></p>
<p>Xerces2 is the next generation of high performance, fully compliant XML parsers in the Apache Xerces family. This new version of Xerces introduces the Xerces Native Interface (XNI), a complete framework for building parser components and configurations that is extremely modular and easy to program.
The Apache Xerces2 parser is the reference implementation of XNI but other parser components, configurations, and parsers can be written using the Xerces Native Interface. For complete design and implementation documents, refer to the XNI Manual.
Xerces2 is a fully conforming XML Schema 1.0 processor. A partial experimental implementation of the XML Schema 1.1 Structures and Datatypes Working Drafts (December 2009) and an experimental implementation of the XML Schema Definition Language (XSD): Component Designators (SCD) Candidate Recommendation (January 2010) are provided for evaluation. For more information, refer to the XML Schema page.
Xerces2 also provides a complete implementation of the Document Object Model Level 3 Core and Load/Save W3C Recommendations and provides a complete implementation of the XML Inclusions (XInclude) W3C Recommendation. It also provides support for OASIS XML Catalogs v1.1.
Xerces2 is able to parse documents written according to the XML 1.1 Recommendation, except that it does not yet provide an option to enable normalization checking as described in section 2.13 of this specification. It also handles namespaces according to the XML Namespaces 1.1 Recommendation, and will correctly serialize XML 1.1 documents if the DOM level 3 load/save APIs are in use.</p>
<p>Library home page: <a href="https://xerces.apache.org/xerces2-j/">https://xerces.apache.org/xerces2-j/</a></p>
<p>Path to dependency file: /app-to-phone-java/app-to-phone/app/build.gradle</p>
<p>Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/xerces/xercesImpl/2.12.0/f02c844149fd306601f20e0b34853a670bef7fa2/xercesImpl-2.12.0.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/xerces/xercesImpl/2.12.0/f02c844149fd306601f20e0b34853a670bef7fa2/xercesImpl-2.12.0.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/xerces/xercesImpl/2.12.0/f02c844149fd306601f20e0b34853a670bef7fa2/xercesImpl-2.12.0.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/xerces/xercesImpl/2.12.0/f02c844149fd306601f20e0b34853a670bef7fa2/xercesImpl-2.12.0.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/xerces/xercesImpl/2.12.0/f02c844149fd306601f20e0b34853a670bef7fa2/xercesImpl-2.12.0.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/xerces/xercesImpl/2.12.0/f02c844149fd306601f20e0b34853a670bef7fa2/xercesImpl-2.12.0.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/xerces/xercesImpl/2.12.0/f02c844149fd306601f20e0b34853a670bef7fa2/xercesImpl-2.12.0.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/xerces/xercesImpl/2.12.0/f02c844149fd306601f20e0b34853a670bef7fa2/xercesImpl-2.12.0.jar</p>
<p>
Dependency Hierarchy:
- lint-gradle-27.2.1.jar (Root Library)
- sdk-common-27.2.1.jar
- :x: **xercesImpl-2.12.0.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/nexmo-community/client-sdk-tutorials/commit/691e25809d42cce5a487504aa376638500c5b492">691e25809d42cce5a487504aa376638500c5b492</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
There's a vulnerability within the Apache Xerces Java (XercesJ) XML parser when handling specially crafted XML document payloads. This causes, the XercesJ XML parser to wait in an infinite loop, which may sometimes consume system resources for prolonged duration. This vulnerability is present within XercesJ version 2.12.1 and the previous versions.
<p>Publish Date: 2022-01-24
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-23437>CVE-2022-23437</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>6.5</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: 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>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/advisories/GHSA-h65f-jvqw-m9fj">https://github.com/advisories/GHSA-h65f-jvqw-m9fj</a></p>
<p>Release Date: 2022-01-24</p>
<p>Fix Resolution: xerces:xercesImpl:2.12.2</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> WS-2019-0379</summary>
### Vulnerable Library - <b>commons-codec-1.10.jar</b></p>
<p>The Apache Commons Codec package contains simple encoder and decoders for
various formats such as Base64 and Hexadecimal. In addition to these
widely used encoders and decoders, the codec package also maintains a
collection of phonetic encoding utilities.</p>
<p>Path to dependency file: /app-to-app-java/app-to-app/app/build.gradle</p>
<p>Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/commons-codec/commons-codec/1.10/4b95f4897fa13f2cd904aee711aeafc0c5295cd8/commons-codec-1.10.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/commons-codec/commons-codec/1.10/4b95f4897fa13f2cd904aee711aeafc0c5295cd8/commons-codec-1.10.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/commons-codec/commons-codec/1.10/4b95f4897fa13f2cd904aee711aeafc0c5295cd8/commons-codec-1.10.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/commons-codec/commons-codec/1.10/4b95f4897fa13f2cd904aee711aeafc0c5295cd8/commons-codec-1.10.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/commons-codec/commons-codec/1.10/4b95f4897fa13f2cd904aee711aeafc0c5295cd8/commons-codec-1.10.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/commons-codec/commons-codec/1.10/4b95f4897fa13f2cd904aee711aeafc0c5295cd8/commons-codec-1.10.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/commons-codec/commons-codec/1.10/4b95f4897fa13f2cd904aee711aeafc0c5295cd8/commons-codec-1.10.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/commons-codec/commons-codec/1.10/4b95f4897fa13f2cd904aee711aeafc0c5295cd8/commons-codec-1.10.jar</p>
<p>
Dependency Hierarchy:
- lint-gradle-27.2.1.jar (Root Library)
- builder-4.2.1.jar
- sdklib-27.2.1.jar
- httpmime-4.5.6.jar
- httpclient-4.5.6.jar
- :x: **commons-codec-1.10.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/nexmo-community/client-sdk-tutorials/commit/691e25809d42cce5a487504aa376638500c5b492">691e25809d42cce5a487504aa376638500c5b492</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
Apache commons-codec before version “commons-codec-1.13-RC1” is vulnerable to information disclosure due to Improper Input validation.
<p>Publish Date: 2019-05-20
<p>URL: <a href=https://github.com/apache/commons-codec/commit/48b615756d1d770091ea3322eefc08011ee8b113>WS-2019-0379</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>6.5</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: Low
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Release Date: 2019-05-20</p>
<p>Fix Resolution: commons-codec:commons-codec:1.13</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2020-15522</summary>
### Vulnerable Library - <b>bcprov-jdk15on-1.56.jar</b></p>
<p>The Bouncy Castle Crypto package is a Java implementation of cryptographic algorithms. This jar contains JCE provider and lightweight API for the Bouncy Castle Cryptography APIs for JDK 1.5 to JDK 1.8.</p>
<p>Library home page: <a href="http://www.bouncycastle.org/java.html">http://www.bouncycastle.org/java.html</a></p>
<p>Path to dependency file: /app-to-phone-java/app-to-phone/app/build.gradle</p>
<p>Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.bouncycastle/bcprov-jdk15on/1.56/a153c6f9744a3e9dd6feab5e210e1c9861362ec7/bcprov-jdk15on-1.56.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.bouncycastle/bcprov-jdk15on/1.56/a153c6f9744a3e9dd6feab5e210e1c9861362ec7/bcprov-jdk15on-1.56.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.bouncycastle/bcprov-jdk15on/1.56/a153c6f9744a3e9dd6feab5e210e1c9861362ec7/bcprov-jdk15on-1.56.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.bouncycastle/bcprov-jdk15on/1.56/a153c6f9744a3e9dd6feab5e210e1c9861362ec7/bcprov-jdk15on-1.56.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.bouncycastle/bcprov-jdk15on/1.56/a153c6f9744a3e9dd6feab5e210e1c9861362ec7/bcprov-jdk15on-1.56.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.bouncycastle/bcprov-jdk15on/1.56/a153c6f9744a3e9dd6feab5e210e1c9861362ec7/bcprov-jdk15on-1.56.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.bouncycastle/bcprov-jdk15on/1.56/a153c6f9744a3e9dd6feab5e210e1c9861362ec7/bcprov-jdk15on-1.56.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.bouncycastle/bcprov-jdk15on/1.56/a153c6f9744a3e9dd6feab5e210e1c9861362ec7/bcprov-jdk15on-1.56.jar</p>
<p>
Dependency Hierarchy:
- lint-gradle-27.2.1.jar (Root Library)
- builder-4.2.1.jar
- :x: **bcprov-jdk15on-1.56.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/nexmo-community/client-sdk-tutorials/commit/691e25809d42cce5a487504aa376638500c5b492">691e25809d42cce5a487504aa376638500c5b492</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
Bouncy Castle BC Java before 1.66, BC C# .NET before 1.8.7, BC-FJA before 1.0.1.2, 1.0.2.1, and BC-FNA before 1.0.1.1 have a timing issue within the EC math library that can expose information about the private key when an attacker is able to observe timing information for the generation of multiple deterministic ECDSA signatures.
<p>Publish Date: 2021-05-20
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-15522>CVE-2020-15522</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>5.9</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: None
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-15522">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-15522</a></p>
<p>Release Date: 2021-05-20</p>
<p>Fix Resolution: C#- release-1.8.7, Java- 1.66</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2022-3171</summary>
### Vulnerable Library - <b>protobuf-java-3.10.0.jar</b></p>
<p>Core Protocol Buffers library. Protocol Buffers are a way of encoding structured data in an
efficient yet extensible format.</p>
<p>Library home page: <a href="https://developers.google.com/protocol-buffers/">https://developers.google.com/protocol-buffers/</a></p>
<p>Path to dependency file: /in-app-messaging-java/app/build.gradle</p>
<p>Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/com.google.protobuf/protobuf-java/3.10.0/410b61dd0088aab4caa05739558d43df248958c9/protobuf-java-3.10.0.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/com.google.protobuf/protobuf-java/3.10.0/410b61dd0088aab4caa05739558d43df248958c9/protobuf-java-3.10.0.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/com.google.protobuf/protobuf-java/3.10.0/410b61dd0088aab4caa05739558d43df248958c9/protobuf-java-3.10.0.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/com.google.protobuf/protobuf-java/3.10.0/410b61dd0088aab4caa05739558d43df248958c9/protobuf-java-3.10.0.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/com.google.protobuf/protobuf-java/3.10.0/410b61dd0088aab4caa05739558d43df248958c9/protobuf-java-3.10.0.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/com.google.protobuf/protobuf-java/3.10.0/410b61dd0088aab4caa05739558d43df248958c9/protobuf-java-3.10.0.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/com.google.protobuf/protobuf-java/3.10.0/410b61dd0088aab4caa05739558d43df248958c9/protobuf-java-3.10.0.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/com.google.protobuf/protobuf-java/3.10.0/410b61dd0088aab4caa05739558d43df248958c9/protobuf-java-3.10.0.jar</p>
<p>
Dependency Hierarchy:
- lint-gradle-27.2.1.jar (Root Library)
- builder-4.2.1.jar
- protos-27.2.1.jar
- :x: **protobuf-java-3.10.0.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/nexmo-community/client-sdk-tutorials/commit/691e25809d42cce5a487504aa376638500c5b492">691e25809d42cce5a487504aa376638500c5b492</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
A potential Denial of Service issue in protobuf-java core and lite was discovered in the parsing procedure for binary and text format data. Input streams containing multiple instances of non-repeated embedded messages with repeated or unknown fields cause objects to be converted back-n-forth between mutable and immutable forms, resulting in potentially long garbage collection pauses.
This issue was fixed In the following version:
protobuf-java (3.21.7, 3.20.3, 3.19.6, 3.16.3)
protobuf-javalite (3.21.7, 3.20.3, 3.19.6, 3.16.3)
protobuf-kotlin (3.21.7, 3.20.3, 3.19.6)
protobuf-kotlin-lite (3.21.7, 3.20.3, 3.19.6)
google-protobuf [JRuby gem only] (3.21.7, 3.20.3, 3.19.6)
<p>Publish Date: 2022-09-10
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-3171>CVE-2022-3171</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>5.7</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Adjacent
- 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>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/advisories/GHSA-h4h5-3hr4-j3g2">https://github.com/advisories/GHSA-h4h5-3hr4-j3g2</a></p>
<p>Release Date: 2022-09-10</p>
<p>Fix Resolution: com.google.protobuf:protobuf-java:3.16.3,3.19.6,3.20.3,3.21.7;com.google.protobuf:protobuf-javalite:3.16.3,3.19.6,3.20.3,3.21.7;com.google.protobuf:protobuf-kotlin:3.19.6,3.20.3,3.21.7;com.google.protobuf:protobuf-kotlin-lite:3.19.6,3.20.3,3.21.7;google-protobuf - 3.19.6,3.20.3,3.21.7</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2021-22569</summary>
### Vulnerable Library - <b>protobuf-java-3.10.0.jar</b></p>
<p>Core Protocol Buffers library. Protocol Buffers are a way of encoding structured data in an
efficient yet extensible format.</p>
<p>Library home page: <a href="https://developers.google.com/protocol-buffers/">https://developers.google.com/protocol-buffers/</a></p>
<p>Path to dependency file: /in-app-messaging-java/app/build.gradle</p>
<p>Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/com.google.protobuf/protobuf-java/3.10.0/410b61dd0088aab4caa05739558d43df248958c9/protobuf-java-3.10.0.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/com.google.protobuf/protobuf-java/3.10.0/410b61dd0088aab4caa05739558d43df248958c9/protobuf-java-3.10.0.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/com.google.protobuf/protobuf-java/3.10.0/410b61dd0088aab4caa05739558d43df248958c9/protobuf-java-3.10.0.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/com.google.protobuf/protobuf-java/3.10.0/410b61dd0088aab4caa05739558d43df248958c9/protobuf-java-3.10.0.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/com.google.protobuf/protobuf-java/3.10.0/410b61dd0088aab4caa05739558d43df248958c9/protobuf-java-3.10.0.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/com.google.protobuf/protobuf-java/3.10.0/410b61dd0088aab4caa05739558d43df248958c9/protobuf-java-3.10.0.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/com.google.protobuf/protobuf-java/3.10.0/410b61dd0088aab4caa05739558d43df248958c9/protobuf-java-3.10.0.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/com.google.protobuf/protobuf-java/3.10.0/410b61dd0088aab4caa05739558d43df248958c9/protobuf-java-3.10.0.jar</p>
<p>
Dependency Hierarchy:
- lint-gradle-27.2.1.jar (Root Library)
- builder-4.2.1.jar
- protos-27.2.1.jar
- :x: **protobuf-java-3.10.0.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/nexmo-community/client-sdk-tutorials/commit/691e25809d42cce5a487504aa376638500c5b492">691e25809d42cce5a487504aa376638500c5b492</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
An issue in protobuf-java allowed the interleaving of com.google.protobuf.UnknownFieldSet fields in such a way that would be processed out of order. A small malicious payload can occupy the parser for several minutes by creating large numbers of short-lived objects that cause frequent, repeated pauses. We recommend upgrading libraries beyond the vulnerable versions.
<p>Publish Date: 2022-01-10
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-22569>CVE-2021-22569</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>5.5</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/advisories/GHSA-wrvw-hg22-4m67">https://github.com/advisories/GHSA-wrvw-hg22-4m67</a></p>
<p>Release Date: 2022-01-10</p>
<p>Fix Resolution: com.google.protobuf:protobuf-java:3.16.1,3.18.2,3.19.2; com.google.protobuf:protobuf-kotlin:3.18.2,3.19.2; google-protobuf - 3.19.2</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2020-17521</summary>
### Vulnerable Library - <b>groovy-all-2.4.15.jar</b></p>
<p>Groovy: A powerful, dynamic language for the JVM</p>
<p>Library home page: <a href="http://groovy-lang.org">http://groovy-lang.org</a></p>
<p>Path to dependency file: /in-app-messaging-java/app/build.gradle</p>
<p>Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.codehaus.groovy/groovy-all/2.4.15/423a17aeb2f64bc6f76e8e44265a548bec80fd42/groovy-all-2.4.15.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.codehaus.groovy/groovy-all/2.4.15/423a17aeb2f64bc6f76e8e44265a548bec80fd42/groovy-all-2.4.15.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.codehaus.groovy/groovy-all/2.4.15/423a17aeb2f64bc6f76e8e44265a548bec80fd42/groovy-all-2.4.15.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.codehaus.groovy/groovy-all/2.4.15/423a17aeb2f64bc6f76e8e44265a548bec80fd42/groovy-all-2.4.15.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.codehaus.groovy/groovy-all/2.4.15/423a17aeb2f64bc6f76e8e44265a548bec80fd42/groovy-all-2.4.15.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.codehaus.groovy/groovy-all/2.4.15/423a17aeb2f64bc6f76e8e44265a548bec80fd42/groovy-all-2.4.15.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.codehaus.groovy/groovy-all/2.4.15/423a17aeb2f64bc6f76e8e44265a548bec80fd42/groovy-all-2.4.15.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.codehaus.groovy/groovy-all/2.4.15/423a17aeb2f64bc6f76e8e44265a548bec80fd42/groovy-all-2.4.15.jar</p>
<p>
Dependency Hierarchy:
- lint-gradle-27.2.1.jar (Root Library)
- :x: **groovy-all-2.4.15.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/nexmo-community/client-sdk-tutorials/commit/691e25809d42cce5a487504aa376638500c5b492">691e25809d42cce5a487504aa376638500c5b492</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
Apache Groovy provides extension methods to aid with creating temporary directories. Prior to this fix, Groovy's implementation of those extension methods was using a now superseded Java JDK method call that is potentially not secure on some operating systems in some contexts. Users not using the extension methods mentioned in the advisory are not affected, but may wish to read the advisory for further details. Versions Affected: 2.0 to 2.4.20, 2.5.0 to 2.5.13, 3.0.0 to 3.0.6, and 4.0.0-alpha-1. Fixed in versions 2.4.21, 2.5.14, 3.0.7, 4.0.0-alpha-2.
<p>Publish Date: 2020-12-07
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-17521>CVE-2020-17521</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>5.5</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: None
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://issues.apache.org/jira/browse/GROOVY-9824">https://issues.apache.org/jira/browse/GROOVY-9824</a></p>
<p>Release Date: 2020-12-07</p>
<p>Fix Resolution: org.codehaus.groovy:groovy-all:2.4.21,2.5.14,3.0.7</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2018-11771</summary>
### Vulnerable Library - <b>commons-compress-1.12.jar</b></p>
<p>Apache Commons Compress software defines an API for working with
compression and archive formats. These include: bzip2, gzip, pack200,
lzma, xz, Snappy, traditional Unix Compress, DEFLATE and ar, cpio,
jar, tar, zip, dump, 7z, arj.</p>
<p>Path to dependency file: /app-to-phone-java/app-to-phone/app/build.gradle</p>
<p>Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.apache.commons/commons-compress/1.12/84caa68576e345eb5e7ae61a0e5a9229eb100d7b/commons-compress-1.12.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.apache.commons/commons-compress/1.12/84caa68576e345eb5e7ae61a0e5a9229eb100d7b/commons-compress-1.12.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.apache.commons/commons-compress/1.12/84caa68576e345eb5e7ae61a0e5a9229eb100d7b/commons-compress-1.12.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.apache.commons/commons-compress/1.12/84caa68576e345eb5e7ae61a0e5a9229eb100d7b/commons-compress-1.12.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.apache.commons/commons-compress/1.12/84caa68576e345eb5e7ae61a0e5a9229eb100d7b/commons-compress-1.12.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.apache.commons/commons-compress/1.12/84caa68576e345eb5e7ae61a0e5a9229eb100d7b/commons-compress-1.12.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.apache.commons/commons-compress/1.12/84caa68576e345eb5e7ae61a0e5a9229eb100d7b/commons-compress-1.12.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.apache.commons/commons-compress/1.12/84caa68576e345eb5e7ae61a0e5a9229eb100d7b/commons-compress-1.12.jar</p>
<p>
Dependency Hierarchy:
- lint-gradle-27.2.1.jar (Root Library)
- builder-4.2.1.jar
- sdklib-27.2.1.jar
- :x: **commons-compress-1.12.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/nexmo-community/client-sdk-tutorials/commit/691e25809d42cce5a487504aa376638500c5b492">691e25809d42cce5a487504aa376638500c5b492</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
When reading a specially crafted ZIP archive, the read method of Apache Commons Compress 1.7 to 1.17's ZipArchiveInputStream can fail to return the correct EOF indication after the end of the stream has been reached. When combined with a java.io.InputStreamReader this can lead to an infinite stream, which can be used to mount a denial of service attack against services that use Compress' zip package.
<p>Publish Date: 2018-08-16
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-11771>CVE-2018-11771</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>5.5</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-11771">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-11771</a></p>
<p>Release Date: 2018-08-16</p>
<p>Fix Resolution: 1.18</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2018-1324</summary>
### Vulnerable Library - <b>commons-compress-1.12.jar</b></p>
<p>Apache Commons Compress software defines an API for working with
compression and archive formats. These include: bzip2, gzip, pack200,
lzma, xz, Snappy, traditional Unix Compress, DEFLATE and ar, cpio,
jar, tar, zip, dump, 7z, arj.</p>
<p>Path to dependency file: /app-to-phone-java/app-to-phone/app/build.gradle</p>
<p>Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.apache.commons/commons-compress/1.12/84caa68576e345eb5e7ae61a0e5a9229eb100d7b/commons-compress-1.12.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.apache.commons/commons-compress/1.12/84caa68576e345eb5e7ae61a0e5a9229eb100d7b/commons-compress-1.12.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.apache.commons/commons-compress/1.12/84caa68576e345eb5e7ae61a0e5a9229eb100d7b/commons-compress-1.12.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.apache.commons/commons-compress/1.12/84caa68576e345eb5e7ae61a0e5a9229eb100d7b/commons-compress-1.12.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.apache.commons/commons-compress/1.12/84caa68576e345eb5e7ae61a0e5a9229eb100d7b/commons-compress-1.12.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.apache.commons/commons-compress/1.12/84caa68576e345eb5e7ae61a0e5a9229eb100d7b/commons-compress-1.12.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.apache.commons/commons-compress/1.12/84caa68576e345eb5e7ae61a0e5a9229eb100d7b/commons-compress-1.12.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.apache.commons/commons-compress/1.12/84caa68576e345eb5e7ae61a0e5a9229eb100d7b/commons-compress-1.12.jar</p>
<p>
Dependency Hierarchy:
- lint-gradle-27.2.1.jar (Root Library)
- builder-4.2.1.jar
- sdklib-27.2.1.jar
- :x: **commons-compress-1.12.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/nexmo-community/client-sdk-tutorials/commit/691e25809d42cce5a487504aa376638500c5b492">691e25809d42cce5a487504aa376638500c5b492</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
A specially crafted ZIP archive can be used to cause an infinite loop inside of Apache Commons Compress' extra field parser used by the ZipFile and ZipArchiveInputStream classes in versions 1.11 to 1.15. This can be used to mount a denial of service attack against services that use Compress' zip package.
<p>Publish Date: 2018-03-16
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-1324>CVE-2018-1324</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>5.5</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-1324">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-1324</a></p>
<p>Release Date: 2018-03-16</p>
<p>Fix Resolution: 1.16</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2022-24329</summary>
### Vulnerable Library - <b>kotlin-stdlib-1.4.31.jar</b></p>
<p>Kotlin Standard Library for JVM</p>
<p>Library home page: <a href="https://kotlinlang.org/">https://kotlinlang.org/</a></p>
<p>Path to dependency file: /in-app-messaging-java/app/build.gradle</p>
<p>Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.jetbrains.kotlin/kotlin-stdlib/1.4.31/a58e0fb9812a6a93ca24b5da75e4b5a0cb89c957/kotlin-stdlib-1.4.31.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.jetbrains.kotlin/kotlin-stdlib/1.4.31/a58e0fb9812a6a93ca24b5da75e4b5a0cb89c957/kotlin-stdlib-1.4.31.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.jetbrains.kotlin/kotlin-stdlib/1.4.31/a58e0fb9812a6a93ca24b5da75e4b5a0cb89c957/kotlin-stdlib-1.4.31.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.jetbrains.kotlin/kotlin-stdlib/1.4.31/a58e0fb9812a6a93ca24b5da75e4b5a0cb89c957/kotlin-stdlib-1.4.31.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.jetbrains.kotlin/kotlin-stdlib/1.4.31/a58e0fb9812a6a93ca24b5da75e4b5a0cb89c957/kotlin-stdlib-1.4.31.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.jetbrains.kotlin/kotlin-stdlib/1.4.31/a58e0fb9812a6a93ca24b5da75e4b5a0cb89c957/kotlin-stdlib-1.4.31.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.jetbrains.kotlin/kotlin-stdlib/1.4.31/a58e0fb9812a6a93ca24b5da75e4b5a0cb89c957/kotlin-stdlib-1.4.31.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.jetbrains.kotlin/kotlin-stdlib/1.4.31/a58e0fb9812a6a93ca24b5da75e4b5a0cb89c957/kotlin-stdlib-1.4.31.jar</p>
<p>
Dependency Hierarchy:
- lint-gradle-27.2.1.jar (Root Library)
- kotlin-stdlib-jdk8-1.4.31.jar
- :x: **kotlin-stdlib-1.4.31.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/nexmo-community/client-sdk-tutorials/commit/691e25809d42cce5a487504aa376638500c5b492">691e25809d42cce5a487504aa376638500c5b492</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
In JetBrains Kotlin before 1.6.0, it was not possible to lock dependencies for Multiplatform Gradle Projects.
<p>Publish Date: 2022-02-25
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-24329>CVE-2022-24329</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>5.3</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: Low
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/advisories/GHSA-2qp4-g3q3-f92w">https://github.com/advisories/GHSA-2qp4-g3q3-f92w</a></p>
<p>Release Date: 2022-02-25</p>
<p>Fix Resolution: org.jetbrains.kotlin:kotlin-stdlib:1.6.0</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2018-1000180</summary>
### Vulnerable Library - <b>bcprov-jdk15on-1.56.jar</b></p>
<p>The Bouncy Castle Crypto package is a Java implementation of cryptographic algorithms. This jar contains JCE provider and lightweight API for the Bouncy Castle Cryptography APIs for JDK 1.5 to JDK 1.8.</p>
<p>Library home page: <a href="http://www.bouncycastle.org/java.html">http://www.bouncycastle.org/java.html</a></p>
<p>Path to dependency file: /app-to-phone-java/app-to-phone/app/build.gradle</p>
<p>Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.bouncycastle/bcprov-jdk15on/1.56/a153c6f9744a3e9dd6feab5e210e1c9861362ec7/bcprov-jdk15on-1.56.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.bouncycastle/bcprov-jdk15on/1.56/a153c6f9744a3e9dd6feab5e210e1c9861362ec7/bcprov-jdk15on-1.56.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.bouncycastle/bcprov-jdk15on/1.56/a153c6f9744a3e9dd6feab5e210e1c9861362ec7/bcprov-jdk15on-1.56.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.bouncycastle/bcprov-jdk15on/1.56/a153c6f9744a3e9dd6feab5e210e1c9861362ec7/bcprov-jdk15on-1.56.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.bouncycastle/bcprov-jdk15on/1.56/a153c6f9744a3e9dd6feab5e210e1c9861362ec7/bcprov-jdk15on-1.56.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.bouncycastle/bcprov-jdk15on/1.56/a153c6f9744a3e9dd6feab5e210e1c9861362ec7/bcprov-jdk15on-1.56.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.bouncycastle/bcprov-jdk15on/1.56/a153c6f9744a3e9dd6feab5e210e1c9861362ec7/bcprov-jdk15on-1.56.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.bouncycastle/bcprov-jdk15on/1.56/a153c6f9744a3e9dd6feab5e210e1c9861362ec7/bcprov-jdk15on-1.56.jar</p>
<p>
Dependency Hierarchy:
- lint-gradle-27.2.1.jar (Root Library)
- builder-4.2.1.jar
- :x: **bcprov-jdk15on-1.56.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/nexmo-community/client-sdk-tutorials/commit/691e25809d42cce5a487504aa376638500c5b492">691e25809d42cce5a487504aa376638500c5b492</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
Bouncy Castle BC 1.54 - 1.59, BC-FJA 1.0.0, BC-FJA 1.0.1 and earlier have a flaw in the Low-level interface to RSA key pair generator, specifically RSA Key Pairs generated in low-level API with added certainty may have less M-R tests than expected. This appears to be fixed in versions BC 1.60 beta 4 and later, BC-FJA 1.0.2 and later.
<p>Publish Date: 2018-06-05
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-1000180>CVE-2018-1000180</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>5.3</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: None
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-1000180">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-1000180</a></p>
<p>Release Date: 2018-06-05</p>
<p>Fix Resolution: org.bouncycastle:bc-fips:1.0.2;org.bouncycastle:bcprov-jdk15on:1.60;org.bouncycastle:bcprov-jdk14:1.60;org.bouncycastle:bcprov-ext-jdk14:1.60;org.bouncycastle:bcprov-ext-jdk15on:1.60;org.bouncycastle:bcprov-debug-jdk14:1.60;org.bouncycastle:bcprov-debug-jdk15on:1.60</p>
</p>
<p></p>
</details> | non_priority | lint gradle jar vulnerabilities highest severity is vulnerable library lint gradle jar path to dependency file app to app java app to app app build gradle path to vulnerable library home wss scanner gradle caches modules files com google guava guava jre guava jre jar home wss scanner gradle caches modules files com google guava guava jre guava jre jar home wss scanner gradle caches modules files com google guava guava jre guava jre jar home wss scanner gradle caches modules files com google guava guava jre guava jre jar home wss scanner gradle caches modules files com google guava guava jre guava jre jar home wss scanner gradle caches modules files com google guava guava jre guava jre jar home wss scanner gradle caches modules files com google guava guava jre guava jre jar home wss scanner gradle caches modules files com google guava guava jre guava jre jar found in head commit a href vulnerabilities cve severity cvss dependency type fixed in remediation available high commons compress jar transitive n a high bcprov jar transitive n a high commons compress jar transitive n a high commons compress jar transitive n a high commons compress jar transitive n a medium xercesimpl jar transitive n a medium commons codec jar transitive n a medium bcprov jar transitive n a medium protobuf java jar transitive n a medium protobuf java jar transitive n a medium groovy all jar transitive n a medium commons compress jar transitive n a medium commons compress jar transitive n a medium kotlin stdlib jar transitive n a medium bcprov jar transitive n a medium httpclient jar transitive n a medium bcprov jar transitive n a low guava jre jar transitive n a details partial details vulnerabilities are displayed below due to a content size limitation in github to view information on the remaining vulnerabilities navigate to the mend application cve vulnerable library commons compress jar apache commons compress software defines an api for working with compression and archive formats these include gzip lzma xz snappy traditional unix compress deflate and ar cpio jar tar zip dump arj path to dependency file app to phone java app to phone app build gradle path to vulnerable library home wss scanner gradle caches modules files org apache commons commons compress commons compress jar home wss scanner gradle caches modules files org apache commons commons compress commons compress jar home wss scanner gradle caches modules files org apache commons commons compress commons compress jar home wss scanner gradle caches modules files org apache commons commons compress commons compress jar home wss scanner gradle caches modules files org apache commons commons compress commons compress jar home wss scanner gradle caches modules files org apache commons commons compress commons compress jar home wss scanner gradle caches modules files org apache commons commons compress commons compress jar home wss scanner gradle caches modules files org apache commons commons compress commons compress jar dependency hierarchy lint gradle jar root library builder jar sdklib jar x commons compress jar vulnerable library found in head commit a href found in base branch main vulnerability details when reading a specially crafted zip archive compress can be made to allocate large amounts of memory that finally leads to an out of memory error even for very small inputs this could be used to mount a denial of service attack against services that use compress zip package 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 org apache commons commons compress cve vulnerable library bcprov jar the bouncy castle crypto package is a java implementation of cryptographic algorithms this jar contains jce provider and lightweight api for the bouncy castle cryptography apis for jdk to jdk library home page a href path to dependency file app to phone java app to phone app build gradle path to vulnerable library home wss scanner gradle caches modules files org bouncycastle bcprov bcprov jar home wss scanner gradle caches modules files org bouncycastle bcprov bcprov jar home wss scanner gradle caches modules files org bouncycastle bcprov bcprov jar home wss scanner gradle caches modules files org bouncycastle bcprov bcprov jar home wss scanner gradle caches modules files org bouncycastle bcprov bcprov jar home wss scanner gradle caches modules files org bouncycastle bcprov bcprov jar home wss scanner gradle caches modules files org bouncycastle bcprov bcprov jar home wss scanner gradle caches modules files org bouncycastle bcprov bcprov jar dependency hierarchy lint gradle jar root library builder jar x bcprov jar vulnerable library found in head commit a href found in base branch main vulnerability details the asn parser in bouncy castle crypto aka bc java can trigger a large attempted memory allocation and resultant outofmemoryerror error via crafted asn data this is fixed in publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction 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 org bouncycastle bcprov cve vulnerable library commons compress jar apache commons compress software defines an api for working with compression and archive formats these include gzip lzma xz snappy traditional unix compress deflate and ar cpio jar tar zip dump arj path to dependency file app to phone java app to phone app build gradle path to vulnerable library home wss scanner gradle caches modules files org apache commons commons compress commons compress jar home wss scanner gradle caches modules files org apache commons commons compress commons compress jar home wss scanner gradle caches modules files org apache commons commons compress commons compress jar home wss scanner gradle caches modules files org apache commons commons compress commons compress jar home wss scanner gradle caches modules files org apache commons commons compress commons compress jar home wss scanner gradle caches modules files org apache commons commons compress commons compress jar home wss scanner gradle caches modules files org apache commons commons compress commons compress jar home wss scanner gradle caches modules files org apache commons commons compress commons compress jar dependency hierarchy lint gradle jar root library builder jar sdklib jar x commons compress jar vulnerable library found in head commit a href found in base branch main vulnerability details when reading a specially crafted tar archive compress can be made to allocate large amounts of memory that finally leads to an out of memory error even for very small inputs this could be used to mount a denial of service attack against services that use compress tar package 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 org apache commons commons compress cve vulnerable library commons compress jar apache commons compress software defines an api for working with compression and archive formats these include gzip lzma xz snappy traditional unix compress deflate and ar cpio jar tar zip dump arj path to dependency file app to phone java app to phone app build gradle path to vulnerable library home wss scanner gradle caches modules files org apache commons commons compress commons compress jar home wss scanner gradle caches modules files org apache commons commons compress commons compress jar home wss scanner gradle caches modules files org apache commons commons compress commons compress jar home wss scanner gradle caches modules files org apache commons commons compress commons compress jar home wss scanner gradle caches modules files org apache commons commons compress commons compress jar home wss scanner gradle caches modules files org apache commons commons compress commons compress jar home wss scanner gradle caches modules files org apache commons commons compress commons compress jar home wss scanner gradle caches modules files org apache commons commons compress commons compress jar dependency hierarchy lint gradle jar root library builder jar sdklib jar x commons compress jar vulnerable library found in head commit a href found in base branch main vulnerability details when reading a specially crafted archive compress can be made to allocate large amounts of memory that finally leads to an out of memory error even for very small inputs this could be used to mount a denial of service attack against services that use compress sevenz package 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 org apache commons commons compress cve vulnerable library commons compress jar apache commons compress software defines an api for working with compression and archive formats these include gzip lzma xz snappy traditional unix compress deflate and ar cpio jar tar zip dump arj path to dependency file app to phone java app to phone app build gradle path to vulnerable library home wss scanner gradle caches modules files org apache commons commons compress commons compress jar home wss scanner gradle caches modules files org apache commons commons compress commons compress jar home wss scanner gradle caches modules files org apache commons commons compress commons compress jar home wss scanner gradle caches modules files org apache commons commons compress commons compress jar home wss scanner gradle caches modules files org apache commons commons compress commons compress jar home wss scanner gradle caches modules files org apache commons commons compress commons compress jar home wss scanner gradle caches modules files org apache commons commons compress commons compress jar home wss scanner gradle caches modules files org apache commons commons compress commons compress jar dependency hierarchy lint gradle jar root library builder jar sdklib jar x commons compress jar vulnerable library found in head commit a href found in base branch main vulnerability details when reading a specially crafted archive the construction of the list of codecs that decompress an entry can result in an infinite loop this could be used to mount a denial of service attack against services that use compress sevenz package 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 org apache commons commons compress cve vulnerable library xercesimpl jar is the next generation of high performance fully compliant xml parsers in the apache xerces family this new version of xerces introduces the xerces native interface xni a complete framework for building parser components and configurations that is extremely modular and easy to program the apache parser is the reference implementation of xni but other parser components configurations and parsers can be written using the xerces native interface for complete design and implementation documents refer to the xni manual is a fully conforming xml schema processor a partial experimental implementation of the xml schema structures and datatypes working drafts december and an experimental implementation of the xml schema definition language xsd component designators scd candidate recommendation january are provided for evaluation for more information refer to the xml schema page also provides a complete implementation of the document object model level core and load save recommendations and provides a complete implementation of the xml inclusions xinclude recommendation it also provides support for oasis xml catalogs is able to parse documents written according to the xml recommendation except that it does not yet provide an option to enable normalization checking as described in section of this specification it also handles namespaces according to the xml namespaces recommendation and will correctly serialize xml documents if the dom level load save apis are in use library home page a href path to dependency file app to phone java app to phone app build gradle path to vulnerable library home wss scanner gradle caches modules files xerces xercesimpl xercesimpl jar home wss scanner gradle caches modules files xerces xercesimpl xercesimpl jar home wss scanner gradle caches modules files xerces xercesimpl xercesimpl jar home wss scanner gradle caches modules files xerces xercesimpl xercesimpl jar home wss scanner gradle caches modules files xerces xercesimpl xercesimpl jar home wss scanner gradle caches modules files xerces xercesimpl xercesimpl jar home wss scanner gradle caches modules files xerces xercesimpl xercesimpl jar home wss scanner gradle caches modules files xerces xercesimpl xercesimpl jar dependency hierarchy lint gradle jar root library sdk common jar x xercesimpl jar vulnerable library found in head commit a href found in base branch main vulnerability details there s a vulnerability within the apache xerces java xercesj xml parser when handling specially crafted xml document payloads this causes the xercesj xml parser to wait in an infinite loop which may sometimes consume system resources for prolonged duration this vulnerability is present within xercesj version and the previous versions publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction required scope unchanged impact metrics confidentiality impact 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 xerces xercesimpl ws vulnerable library commons codec jar the apache commons codec package contains simple encoder and decoders for various formats such as and hexadecimal in addition to these widely used encoders and decoders the codec package also maintains a collection of phonetic encoding utilities path to dependency file app to app java app to app app build gradle path to vulnerable library home wss scanner gradle caches modules files commons codec commons codec commons codec jar home wss scanner gradle caches modules files commons codec commons codec commons codec jar home wss scanner gradle caches modules files commons codec commons codec commons codec jar home wss scanner gradle caches modules files commons codec commons codec commons codec jar home wss scanner gradle caches modules files commons codec commons codec commons codec jar home wss scanner gradle caches modules files commons codec commons codec commons codec jar home wss scanner gradle caches modules files commons codec commons codec commons codec jar home wss scanner gradle caches modules files commons codec commons codec commons codec jar dependency hierarchy lint gradle jar root library builder jar sdklib jar httpmime jar httpclient jar x commons codec jar vulnerable library found in head commit a href found in base branch main vulnerability details apache commons codec before version “commons codec ” is vulnerable to information disclosure due to improper input validation publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact low integrity impact low availability impact none for more information on scores click a href suggested fix type upgrade version release date fix resolution commons codec commons codec cve vulnerable library bcprov jar the bouncy castle crypto package is a java implementation of cryptographic algorithms this jar contains jce provider and lightweight api for the bouncy castle cryptography apis for jdk to jdk library home page a href path to dependency file app to phone java app to phone app build gradle path to vulnerable library home wss scanner gradle caches modules files org bouncycastle bcprov bcprov jar home wss scanner gradle caches modules files org bouncycastle bcprov bcprov jar home wss scanner gradle caches modules files org bouncycastle bcprov bcprov jar home wss scanner gradle caches modules files org bouncycastle bcprov bcprov jar home wss scanner gradle caches modules files org bouncycastle bcprov bcprov jar home wss scanner gradle caches modules files org bouncycastle bcprov bcprov jar home wss scanner gradle caches modules files org bouncycastle bcprov bcprov jar home wss scanner gradle caches modules files org bouncycastle bcprov bcprov jar dependency hierarchy lint gradle jar root library builder jar x bcprov jar vulnerable library found in head commit a href found in base branch main vulnerability details bouncy castle bc java before bc c net before bc fja before and bc fna before have a timing issue within the ec math library that can expose information about the private key when an attacker is able to observe timing information for the generation of multiple deterministic ecdsa signatures 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 none availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution c release java cve vulnerable library protobuf java jar core protocol buffers library protocol buffers are a way of encoding structured data in an efficient yet extensible format library home page a href path to dependency file in app messaging java app build gradle path to vulnerable library home wss scanner gradle caches modules files com google protobuf protobuf java protobuf java jar home wss scanner gradle caches modules files com google protobuf protobuf java protobuf java jar home wss scanner gradle caches modules files com google protobuf protobuf java protobuf java jar home wss scanner gradle caches modules files com google protobuf protobuf java protobuf java jar home wss scanner gradle caches modules files com google protobuf protobuf java protobuf java jar home wss scanner gradle caches modules files com google protobuf protobuf java protobuf java jar home wss scanner gradle caches modules files com google protobuf protobuf java protobuf java jar home wss scanner gradle caches modules files com google protobuf protobuf java protobuf java jar dependency hierarchy lint gradle jar root library builder jar protos jar x protobuf java jar vulnerable library found in head commit a href found in base branch main vulnerability details a potential denial of service issue in protobuf java core and lite was discovered in the parsing procedure for binary and text format data input streams containing multiple instances of non repeated embedded messages with repeated or unknown fields cause objects to be converted back n forth between mutable and immutable forms resulting in potentially long garbage collection pauses this issue was fixed in the following version protobuf java protobuf javalite protobuf kotlin protobuf kotlin lite google protobuf publish date url a href cvss score details base score metrics exploitability metrics attack vector adjacent 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 com google protobuf protobuf java com google protobuf protobuf javalite com google protobuf protobuf kotlin com google protobuf protobuf kotlin lite google protobuf cve vulnerable library protobuf java jar core protocol buffers library protocol buffers are a way of encoding structured data in an efficient yet extensible format library home page a href path to dependency file in app messaging java app build gradle path to vulnerable library home wss scanner gradle caches modules files com google protobuf protobuf java protobuf java jar home wss scanner gradle caches modules files com google protobuf protobuf java protobuf java jar home wss scanner gradle caches modules files com google protobuf protobuf java protobuf java jar home wss scanner gradle caches modules files com google protobuf protobuf java protobuf java jar home wss scanner gradle caches modules files com google protobuf protobuf java protobuf java jar home wss scanner gradle caches modules files com google protobuf protobuf java protobuf java jar home wss scanner gradle caches modules files com google protobuf protobuf java protobuf java jar home wss scanner gradle caches modules files com google protobuf protobuf java protobuf java jar dependency hierarchy lint gradle jar root library builder jar protos jar x protobuf java jar vulnerable library found in head commit a href found in base branch main vulnerability details an issue in protobuf java allowed the interleaving of com google protobuf unknownfieldset fields in such a way that would be processed out of order a small malicious payload can occupy the parser for several minutes by creating large numbers of short lived objects that cause frequent repeated pauses we recommend upgrading libraries beyond the vulnerable versions publish date url a href cvss score details base score metrics exploitability metrics attack vector local attack complexity low privileges required none user interaction required scope unchanged impact metrics confidentiality impact none integrity impact none availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution com google protobuf protobuf java com google protobuf protobuf kotlin google protobuf cve vulnerable library groovy all jar groovy a powerful dynamic language for the jvm library home page a href path to dependency file in app messaging java app build gradle path to vulnerable library home wss scanner gradle caches modules files org codehaus groovy groovy all groovy all jar home wss scanner gradle caches modules files org codehaus groovy groovy all groovy all jar home wss scanner gradle caches modules files org codehaus groovy groovy all groovy all jar home wss scanner gradle caches modules files org codehaus groovy groovy all groovy all jar home wss scanner gradle caches modules files org codehaus groovy groovy all groovy all jar home wss scanner gradle caches modules files org codehaus groovy groovy all groovy all jar home wss scanner gradle caches modules files org codehaus groovy groovy all groovy all jar home wss scanner gradle caches modules files org codehaus groovy groovy all groovy all jar dependency hierarchy lint gradle jar root library x groovy all jar vulnerable library found in head commit a href found in base branch main vulnerability details apache groovy provides extension methods to aid with creating temporary directories prior to this fix groovy s implementation of those extension methods was using a now superseded java jdk method call that is potentially not secure on some operating systems in some contexts users not using the extension methods mentioned in the advisory are not affected but may wish to read the advisory for further details versions affected to to to and alpha fixed in versions alpha 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 none availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution org codehaus groovy groovy all cve vulnerable library commons compress jar apache commons compress software defines an api for working with compression and archive formats these include gzip lzma xz snappy traditional unix compress deflate and ar cpio jar tar zip dump arj path to dependency file app to phone java app to phone app build gradle path to vulnerable library home wss scanner gradle caches modules files org apache commons commons compress commons compress jar home wss scanner gradle caches modules files org apache commons commons compress commons compress jar home wss scanner gradle caches modules files org apache commons commons compress commons compress jar home wss scanner gradle caches modules files org apache commons commons compress commons compress jar home wss scanner gradle caches modules files org apache commons commons compress commons compress jar home wss scanner gradle caches modules files org apache commons commons compress commons compress jar home wss scanner gradle caches modules files org apache commons commons compress commons compress jar home wss scanner gradle caches modules files org apache commons commons compress commons compress jar dependency hierarchy lint gradle jar root library builder jar sdklib jar x commons compress jar vulnerable library found in head commit a href found in base branch main vulnerability details when reading a specially crafted zip archive the read method of apache commons compress to s ziparchiveinputstream can fail to return the correct eof indication after the end of the stream has been reached when combined with a java io inputstreamreader this can lead to an infinite stream which can be used to mount a denial of service attack against services that use compress zip package publish date url a href cvss score details base score metrics exploitability metrics attack vector local attack complexity low privileges required none user interaction required scope unchanged impact metrics confidentiality impact none integrity impact none availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution cve vulnerable library commons compress jar apache commons compress software defines an api for working with compression and archive formats these include gzip lzma xz snappy traditional unix compress deflate and ar cpio jar tar zip dump arj path to dependency file app to phone java app to phone app build gradle path to vulnerable library home wss scanner gradle caches modules files org apache commons commons compress commons compress jar home wss scanner gradle caches modules files org apache commons commons compress commons compress jar home wss scanner gradle caches modules files org apache commons commons compress commons compress jar home wss scanner gradle caches modules files org apache commons commons compress commons compress jar home wss scanner gradle caches modules files org apache commons commons compress commons compress jar home wss scanner gradle caches modules files org apache commons commons compress commons compress jar home wss scanner gradle caches modules files org apache commons commons compress commons compress jar home wss scanner gradle caches modules files org apache commons commons compress commons compress jar dependency hierarchy lint gradle jar root library builder jar sdklib jar x commons compress jar vulnerable library found in head commit a href found in base branch main vulnerability details a specially crafted zip archive can be used to cause an infinite loop inside of apache commons compress extra field parser used by the zipfile and ziparchiveinputstream classes in versions to this can be used to mount a denial of service attack against services that use compress zip package publish date url a href cvss score details base score metrics exploitability metrics attack vector local attack complexity low privileges required none user interaction required scope unchanged impact metrics confidentiality impact none integrity impact none availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution cve vulnerable library kotlin stdlib jar kotlin standard library for jvm library home page a href path to dependency file in app messaging java app build gradle path to vulnerable library home wss scanner gradle caches modules files org jetbrains kotlin kotlin stdlib kotlin stdlib jar home wss scanner gradle caches modules files org jetbrains kotlin kotlin stdlib kotlin stdlib jar home wss scanner gradle caches modules files org jetbrains kotlin kotlin stdlib kotlin stdlib jar home wss scanner gradle caches modules files org jetbrains kotlin kotlin stdlib kotlin stdlib jar home wss scanner gradle caches modules files org jetbrains kotlin kotlin stdlib kotlin stdlib jar home wss scanner gradle caches modules files org jetbrains kotlin kotlin stdlib kotlin stdlib jar home wss scanner gradle caches modules files org jetbrains kotlin kotlin stdlib kotlin stdlib jar home wss scanner gradle caches modules files org jetbrains kotlin kotlin stdlib kotlin stdlib jar dependency hierarchy lint gradle jar root library kotlin stdlib jar x kotlin stdlib jar vulnerable library found in head commit a href found in base branch main vulnerability details in jetbrains kotlin before it was not possible to lock dependencies for multiplatform gradle projects publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact none integrity impact low availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution org jetbrains kotlin kotlin stdlib cve vulnerable library bcprov jar the bouncy castle crypto package is a java implementation of cryptographic algorithms this jar contains jce provider and lightweight api for the bouncy castle cryptography apis for jdk to jdk library home page a href path to dependency file app to phone java app to phone app build gradle path to vulnerable library home wss scanner gradle caches modules files org bouncycastle bcprov bcprov jar home wss scanner gradle caches modules files org bouncycastle bcprov bcprov jar home wss scanner gradle caches modules files org bouncycastle bcprov bcprov jar home wss scanner gradle caches modules files org bouncycastle bcprov bcprov jar home wss scanner gradle caches modules files org bouncycastle bcprov bcprov jar home wss scanner gradle caches modules files org bouncycastle bcprov bcprov jar home wss scanner gradle caches modules files org bouncycastle bcprov bcprov jar home wss scanner gradle caches modules files org bouncycastle bcprov bcprov jar dependency hierarchy lint gradle jar root library builder jar x bcprov jar vulnerable library found in head commit a href found in base branch main vulnerability details bouncy castle bc bc fja bc fja and earlier have a flaw in the low level interface to rsa key pair generator specifically rsa key pairs generated in low level api with added certainty may have less m r tests than expected this appears to be fixed in versions bc beta and later bc fja and later publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact low integrity impact none availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution org bouncycastle bc fips org bouncycastle bcprov org bouncycastle bcprov org bouncycastle bcprov ext org bouncycastle bcprov ext org bouncycastle bcprov debug org bouncycastle bcprov debug | 0 |
112,443 | 24,271,433,591 | IssuesEvent | 2022-09-28 10:35:29 | Regalis11/Barotrauma | https://api.github.com/repos/Regalis11/Barotrauma | closed | If you host via the in game buttons and the server takes too long to load, you will get disconnected from it | Bug Code Networking | - [X] I have searched the issue tracker to check if the issue has already been reported.
**Description**
Looks like for a few selected people, they get disconnected from the in game server before the server can fully load, making it impossible to host using the in game buttons.
**Steps To Reproduce**
1) Host a server using the in game buttons and somehow make it take a while for it to load for the first time
2) Watch you get disconnected before the server can fully load
**Version**
v0.17.12.0
**Additional information**
| 1.0 | If you host via the in game buttons and the server takes too long to load, you will get disconnected from it - - [X] I have searched the issue tracker to check if the issue has already been reported.
**Description**
Looks like for a few selected people, they get disconnected from the in game server before the server can fully load, making it impossible to host using the in game buttons.
**Steps To Reproduce**
1) Host a server using the in game buttons and somehow make it take a while for it to load for the first time
2) Watch you get disconnected before the server can fully load
**Version**
v0.17.12.0
**Additional information**
| non_priority | if you host via the in game buttons and the server takes too long to load you will get disconnected from it i have searched the issue tracker to check if the issue has already been reported description looks like for a few selected people they get disconnected from the in game server before the server can fully load making it impossible to host using the in game buttons steps to reproduce host a server using the in game buttons and somehow make it take a while for it to load for the first time watch you get disconnected before the server can fully load version additional information | 0 |
137,130 | 30,630,979,792 | IssuesEvent | 2023-07-24 14:31:33 | Son1kXDev/5opkagame2d | https://api.github.com/repos/Son1kXDev/5opkagame2d | opened | Параллакс эффект | Code World | Сделай его более гибким (чтобы не было фиксированного количество фонов - просто создать лист для них. Скорость движения фона, относительно игрока, будет зависеть от положения в листе) | 1.0 | Параллакс эффект - Сделай его более гибким (чтобы не было фиксированного количество фонов - просто создать лист для них. Скорость движения фона, относительно игрока, будет зависеть от положения в листе) | non_priority | параллакс эффект сделай его более гибким чтобы не было фиксированного количество фонов просто создать лист для них скорость движения фона относительно игрока будет зависеть от положения в листе | 0 |
17,618 | 10,098,143,100 | IssuesEvent | 2019-07-28 12:46:46 | Shuunen/bergerac-roads | https://api.github.com/repos/Shuunen/bergerac-roads | closed | CVE-2018-19797 Low Severity Vulnerability detected by WhiteSource | security vulnerability | ## CVE-2018-19797 - Low 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>node-sassv4.9.4</b></p></summary>
<p>
<p>:rainbow: Node.js bindings to libsass</p>
<p>Library home page: <a href=https://github.com/sass/node-sass.git>https://github.com/sass/node-sass.git</a></p>
</p>
</details>
</p></p>
<details><summary><img src='https://www.whitesourcesoftware.com/wp-content/uploads/2018/10/vulnerability_details.png' width=19 height=20> Library Source Files (125)</summary>
<p></p>
<p> * The source files were matched to this source library based on a best effort match. Source libraries are selected from a list of probable public libraries.</p>
<p>
- /bergerac-roads/node_modules/node-sass/src/libsass/src/expand.hpp
- /bergerac-roads/node_modules/node-sass/src/binding.cpp
- /bergerac-roads/node_modules/node-sass/src/libsass/src/color_maps.cpp
- /bergerac-roads/node_modules/node-sass/src/libsass/src/sass_util.hpp
- /bergerac-roads/node_modules/node-sass/src/libsass/src/parser.cpp
- /bergerac-roads/node_modules/node-sass/src/libsass/src/utf8/unchecked.h
- /bergerac-roads/node_modules/node-sass/src/libsass/src/output.hpp
- /bergerac-roads/node_modules/node-sass/src/libsass/src/sass_values.hpp
- /bergerac-roads/node_modules/node-sass/src/libsass/src/util.hpp
- /bergerac-roads/node_modules/node-sass/src/libsass/src/emitter.hpp
- /bergerac-roads/node_modules/node-sass/src/libsass/src/lexer.cpp
- /bergerac-roads/node_modules/node-sass/src/libsass/test/test_node.cpp
- /bergerac-roads/node_modules/node-sass/src/libsass/include/sass/context.h
- /bergerac-roads/node_modules/node-sass/src/libsass/src/plugins.cpp
- /bergerac-roads/node_modules/node-sass/src/libsass/include/sass/base.h
- /bergerac-roads/node_modules/node-sass/src/libsass/src/position.hpp
- /bergerac-roads/node_modules/node-sass/src/libsass/src/subset_map.hpp
- /bergerac-roads/node_modules/node-sass/src/libsass/src/operation.hpp
- /bergerac-roads/node_modules/node-sass/src/libsass/src/remove_placeholders.cpp
- /bergerac-roads/node_modules/node-sass/src/libsass/src/operators.cpp
- /bergerac-roads/node_modules/node-sass/src/libsass/src/error_handling.hpp
- /bergerac-roads/node_modules/node-sass/src/custom_importer_bridge.cpp
- /bergerac-roads/node_modules/node-sass/src/libsass/contrib/plugin.cpp
- /bergerac-roads/node_modules/node-sass/src/libsass/src/functions.hpp
- /bergerac-roads/node_modules/node-sass/src/libsass/src/sass_context.hpp
- /bergerac-roads/node_modules/node-sass/src/libsass/test/test_superselector.cpp
- /bergerac-roads/node_modules/node-sass/src/libsass/src/eval.hpp
- /bergerac-roads/node_modules/node-sass/src/libsass/src/utf8_string.hpp
- /bergerac-roads/node_modules/node-sass/src/sass_context_wrapper.h
- /bergerac-roads/node_modules/node-sass/src/libsass/src/error_handling.cpp
- /bergerac-roads/node_modules/node-sass/src/libsass/src/node.cpp
- /bergerac-roads/node_modules/node-sass/src/libsass/src/subset_map.cpp
- /bergerac-roads/node_modules/node-sass/src/libsass/src/emitter.cpp
- /bergerac-roads/node_modules/node-sass/src/libsass/src/listize.cpp
- /bergerac-roads/node_modules/node-sass/src/libsass/src/ast.hpp
- /bergerac-roads/node_modules/node-sass/src/libsass/src/sass_functions.hpp
- /bergerac-roads/node_modules/node-sass/src/libsass/src/memory/SharedPtr.cpp
- /bergerac-roads/node_modules/node-sass/src/libsass/src/output.cpp
- /bergerac-roads/node_modules/node-sass/src/libsass/src/check_nesting.cpp
- /bergerac-roads/node_modules/node-sass/src/libsass/src/ast_def_macros.hpp
- /bergerac-roads/node_modules/node-sass/src/libsass/src/functions.cpp
- /bergerac-roads/node_modules/node-sass/src/libsass/src/cssize.hpp
- /bergerac-roads/node_modules/node-sass/src/libsass/src/prelexer.cpp
- /bergerac-roads/node_modules/node-sass/src/libsass/src/paths.hpp
- /bergerac-roads/node_modules/node-sass/src/libsass/src/ast_fwd_decl.hpp
- /bergerac-roads/node_modules/node-sass/src/libsass/src/inspect.hpp
- /bergerac-roads/node_modules/node-sass/src/sass_types/color.cpp
- /bergerac-roads/node_modules/node-sass/src/libsass/test/test_unification.cpp
- /bergerac-roads/node_modules/node-sass/src/libsass/src/values.cpp
- /bergerac-roads/node_modules/node-sass/src/libsass/src/sass_util.cpp
- /bergerac-roads/node_modules/node-sass/src/libsass/src/source_map.hpp
- /bergerac-roads/node_modules/node-sass/src/sass_types/list.h
- /bergerac-roads/node_modules/node-sass/src/libsass/src/check_nesting.hpp
- /bergerac-roads/node_modules/node-sass/src/libsass/src/json.cpp
- /bergerac-roads/node_modules/node-sass/src/libsass/src/units.cpp
- /bergerac-roads/node_modules/node-sass/src/libsass/src/units.hpp
- /bergerac-roads/node_modules/node-sass/src/libsass/src/utf8/checked.h
- /bergerac-roads/node_modules/node-sass/src/libsass/src/listize.hpp
- /bergerac-roads/node_modules/node-sass/src/sass_types/string.cpp
- /bergerac-roads/node_modules/node-sass/src/libsass/src/prelexer.hpp
- /bergerac-roads/node_modules/node-sass/src/sass_types/boolean.h
- /bergerac-roads/node_modules/node-sass/src/libsass/include/sass2scss.h
- /bergerac-roads/node_modules/node-sass/src/libsass/src/eval.cpp
- /bergerac-roads/node_modules/node-sass/src/libsass/src/expand.cpp
- /bergerac-roads/node_modules/node-sass/src/sass_types/factory.cpp
- /bergerac-roads/node_modules/node-sass/src/sass_types/boolean.cpp
- /bergerac-roads/node_modules/node-sass/src/libsass/src/source_map.cpp
- /bergerac-roads/node_modules/node-sass/src/sass_types/value.h
- /bergerac-roads/node_modules/node-sass/src/libsass/src/utf8_string.cpp
- /bergerac-roads/node_modules/node-sass/src/libsass/src/file.hpp
- /bergerac-roads/node_modules/node-sass/src/callback_bridge.h
- /bergerac-roads/node_modules/node-sass/src/libsass/src/sass.cpp
- /bergerac-roads/node_modules/node-sass/src/libsass/src/node.hpp
- /bergerac-roads/node_modules/node-sass/src/libsass/src/environment.cpp
- /bergerac-roads/node_modules/node-sass/src/libsass/src/extend.hpp
- /bergerac-roads/node_modules/node-sass/src/libsass/src/operators.hpp
- /bergerac-roads/node_modules/node-sass/src/libsass/src/constants.hpp
- /bergerac-roads/node_modules/node-sass/src/libsass/src/sass.hpp
- /bergerac-roads/node_modules/node-sass/src/libsass/src/ast_fwd_decl.cpp
- /bergerac-roads/node_modules/node-sass/src/libsass/src/inspect.cpp
- /bergerac-roads/node_modules/node-sass/src/libsass/src/parser.hpp
- /bergerac-roads/node_modules/node-sass/src/libsass/src/constants.cpp
- /bergerac-roads/node_modules/node-sass/src/sass_types/list.cpp
- /bergerac-roads/node_modules/node-sass/src/libsass/src/cssize.cpp
- /bergerac-roads/node_modules/node-sass/src/libsass/include/sass/functions.h
- /bergerac-roads/node_modules/node-sass/src/libsass/src/util.cpp
- /bergerac-roads/node_modules/node-sass/src/custom_function_bridge.cpp
- /bergerac-roads/node_modules/node-sass/src/libsass/src/context.hpp
- /bergerac-roads/node_modules/node-sass/src/custom_importer_bridge.h
- /bergerac-roads/node_modules/node-sass/src/libsass/src/bind.cpp
- /bergerac-roads/node_modules/node-sass/src/libsass/src/sass_functions.cpp
- /bergerac-roads/node_modules/node-sass/src/libsass/src/backtrace.cpp
- /bergerac-roads/node_modules/node-sass/src/libsass/src/cencode.c
- /bergerac-roads/node_modules/node-sass/src/libsass/src/extend.cpp
- /bergerac-roads/node_modules/node-sass/src/sass_types/sass_value_wrapper.h
- /bergerac-roads/node_modules/node-sass/src/libsass/src/file.cpp
- /bergerac-roads/node_modules/node-sass/src/libsass/src/debugger.hpp
- /bergerac-roads/node_modules/node-sass/src/libsass/src/context.cpp
- /bergerac-roads/node_modules/node-sass/src/libsass/src/base64vlq.cpp
- /bergerac-roads/node_modules/node-sass/src/sass_types/number.cpp
- /bergerac-roads/node_modules/node-sass/src/sass_types/color.h
- /bergerac-roads/node_modules/node-sass/src/libsass/src/c99func.c
- /bergerac-roads/node_modules/node-sass/src/libsass/src/position.cpp
- /bergerac-roads/node_modules/node-sass/src/libsass/src/remove_placeholders.hpp
- /bergerac-roads/node_modules/node-sass/src/libsass/src/sass_values.cpp
- /bergerac-roads/node_modules/node-sass/src/libsass/include/sass/values.h
- /bergerac-roads/node_modules/node-sass/src/libsass/test/test_subset_map.cpp
- /bergerac-roads/node_modules/node-sass/src/libsass/src/sass2scss.cpp
- /bergerac-roads/node_modules/node-sass/src/sass_types/null.cpp
- /bergerac-roads/node_modules/node-sass/src/libsass/src/ast.cpp
- /bergerac-roads/node_modules/node-sass/src/libsass/src/to_c.cpp
- /bergerac-roads/node_modules/node-sass/src/libsass/src/to_value.hpp
- /bergerac-roads/node_modules/node-sass/src/libsass/src/color_maps.hpp
- /bergerac-roads/node_modules/node-sass/src/sass_context_wrapper.cpp
- /bergerac-roads/node_modules/node-sass/src/libsass/src/sass_context.cpp
- /bergerac-roads/node_modules/node-sass/src/libsass/script/test-leaks.pl
- /bergerac-roads/node_modules/node-sass/src/libsass/src/lexer.hpp
- /bergerac-roads/node_modules/node-sass/src/libsass/src/memory/SharedPtr.hpp
- /bergerac-roads/node_modules/node-sass/src/libsass/src/to_c.hpp
- /bergerac-roads/node_modules/node-sass/src/sass_types/map.cpp
- /bergerac-roads/node_modules/node-sass/src/libsass/src/to_value.cpp
- /bergerac-roads/node_modules/node-sass/src/libsass/src/b64/encode.h
- /bergerac-roads/node_modules/node-sass/src/libsass/src/environment.hpp
- /bergerac-roads/node_modules/node-sass/src/libsass/src/plugins.hpp
- /bergerac-roads/node_modules/node-sass/src/libsass/src/debug.hpp
</p>
</details>
<p></p>
</p>
</details>
<p></p>
<details><summary><img src='https://www.whitesourcesoftware.com/wp-content/uploads/2018/10/low_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
In LibSass 3.5.5, a NULL Pointer Dereference in the function Sass::Selector_List::populate_extends in SharedPtr.hpp (used by ast.cpp and ast_selectors.cpp) may cause a Denial of Service (application crash) via a crafted sass input file.
<p>Publish Date: 2018-12-03
<p>URL: <a href=https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-19797>CVE-2018-19797</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>3.5</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://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-19827">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-19827</a></p>
<p>Fix Resolution: No fix version</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-19797 Low Severity Vulnerability detected by WhiteSource - ## CVE-2018-19797 - Low 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>node-sassv4.9.4</b></p></summary>
<p>
<p>:rainbow: Node.js bindings to libsass</p>
<p>Library home page: <a href=https://github.com/sass/node-sass.git>https://github.com/sass/node-sass.git</a></p>
</p>
</details>
</p></p>
<details><summary><img src='https://www.whitesourcesoftware.com/wp-content/uploads/2018/10/vulnerability_details.png' width=19 height=20> Library Source Files (125)</summary>
<p></p>
<p> * The source files were matched to this source library based on a best effort match. Source libraries are selected from a list of probable public libraries.</p>
<p>
- /bergerac-roads/node_modules/node-sass/src/libsass/src/expand.hpp
- /bergerac-roads/node_modules/node-sass/src/binding.cpp
- /bergerac-roads/node_modules/node-sass/src/libsass/src/color_maps.cpp
- /bergerac-roads/node_modules/node-sass/src/libsass/src/sass_util.hpp
- /bergerac-roads/node_modules/node-sass/src/libsass/src/parser.cpp
- /bergerac-roads/node_modules/node-sass/src/libsass/src/utf8/unchecked.h
- /bergerac-roads/node_modules/node-sass/src/libsass/src/output.hpp
- /bergerac-roads/node_modules/node-sass/src/libsass/src/sass_values.hpp
- /bergerac-roads/node_modules/node-sass/src/libsass/src/util.hpp
- /bergerac-roads/node_modules/node-sass/src/libsass/src/emitter.hpp
- /bergerac-roads/node_modules/node-sass/src/libsass/src/lexer.cpp
- /bergerac-roads/node_modules/node-sass/src/libsass/test/test_node.cpp
- /bergerac-roads/node_modules/node-sass/src/libsass/include/sass/context.h
- /bergerac-roads/node_modules/node-sass/src/libsass/src/plugins.cpp
- /bergerac-roads/node_modules/node-sass/src/libsass/include/sass/base.h
- /bergerac-roads/node_modules/node-sass/src/libsass/src/position.hpp
- /bergerac-roads/node_modules/node-sass/src/libsass/src/subset_map.hpp
- /bergerac-roads/node_modules/node-sass/src/libsass/src/operation.hpp
- /bergerac-roads/node_modules/node-sass/src/libsass/src/remove_placeholders.cpp
- /bergerac-roads/node_modules/node-sass/src/libsass/src/operators.cpp
- /bergerac-roads/node_modules/node-sass/src/libsass/src/error_handling.hpp
- /bergerac-roads/node_modules/node-sass/src/custom_importer_bridge.cpp
- /bergerac-roads/node_modules/node-sass/src/libsass/contrib/plugin.cpp
- /bergerac-roads/node_modules/node-sass/src/libsass/src/functions.hpp
- /bergerac-roads/node_modules/node-sass/src/libsass/src/sass_context.hpp
- /bergerac-roads/node_modules/node-sass/src/libsass/test/test_superselector.cpp
- /bergerac-roads/node_modules/node-sass/src/libsass/src/eval.hpp
- /bergerac-roads/node_modules/node-sass/src/libsass/src/utf8_string.hpp
- /bergerac-roads/node_modules/node-sass/src/sass_context_wrapper.h
- /bergerac-roads/node_modules/node-sass/src/libsass/src/error_handling.cpp
- /bergerac-roads/node_modules/node-sass/src/libsass/src/node.cpp
- /bergerac-roads/node_modules/node-sass/src/libsass/src/subset_map.cpp
- /bergerac-roads/node_modules/node-sass/src/libsass/src/emitter.cpp
- /bergerac-roads/node_modules/node-sass/src/libsass/src/listize.cpp
- /bergerac-roads/node_modules/node-sass/src/libsass/src/ast.hpp
- /bergerac-roads/node_modules/node-sass/src/libsass/src/sass_functions.hpp
- /bergerac-roads/node_modules/node-sass/src/libsass/src/memory/SharedPtr.cpp
- /bergerac-roads/node_modules/node-sass/src/libsass/src/output.cpp
- /bergerac-roads/node_modules/node-sass/src/libsass/src/check_nesting.cpp
- /bergerac-roads/node_modules/node-sass/src/libsass/src/ast_def_macros.hpp
- /bergerac-roads/node_modules/node-sass/src/libsass/src/functions.cpp
- /bergerac-roads/node_modules/node-sass/src/libsass/src/cssize.hpp
- /bergerac-roads/node_modules/node-sass/src/libsass/src/prelexer.cpp
- /bergerac-roads/node_modules/node-sass/src/libsass/src/paths.hpp
- /bergerac-roads/node_modules/node-sass/src/libsass/src/ast_fwd_decl.hpp
- /bergerac-roads/node_modules/node-sass/src/libsass/src/inspect.hpp
- /bergerac-roads/node_modules/node-sass/src/sass_types/color.cpp
- /bergerac-roads/node_modules/node-sass/src/libsass/test/test_unification.cpp
- /bergerac-roads/node_modules/node-sass/src/libsass/src/values.cpp
- /bergerac-roads/node_modules/node-sass/src/libsass/src/sass_util.cpp
- /bergerac-roads/node_modules/node-sass/src/libsass/src/source_map.hpp
- /bergerac-roads/node_modules/node-sass/src/sass_types/list.h
- /bergerac-roads/node_modules/node-sass/src/libsass/src/check_nesting.hpp
- /bergerac-roads/node_modules/node-sass/src/libsass/src/json.cpp
- /bergerac-roads/node_modules/node-sass/src/libsass/src/units.cpp
- /bergerac-roads/node_modules/node-sass/src/libsass/src/units.hpp
- /bergerac-roads/node_modules/node-sass/src/libsass/src/utf8/checked.h
- /bergerac-roads/node_modules/node-sass/src/libsass/src/listize.hpp
- /bergerac-roads/node_modules/node-sass/src/sass_types/string.cpp
- /bergerac-roads/node_modules/node-sass/src/libsass/src/prelexer.hpp
- /bergerac-roads/node_modules/node-sass/src/sass_types/boolean.h
- /bergerac-roads/node_modules/node-sass/src/libsass/include/sass2scss.h
- /bergerac-roads/node_modules/node-sass/src/libsass/src/eval.cpp
- /bergerac-roads/node_modules/node-sass/src/libsass/src/expand.cpp
- /bergerac-roads/node_modules/node-sass/src/sass_types/factory.cpp
- /bergerac-roads/node_modules/node-sass/src/sass_types/boolean.cpp
- /bergerac-roads/node_modules/node-sass/src/libsass/src/source_map.cpp
- /bergerac-roads/node_modules/node-sass/src/sass_types/value.h
- /bergerac-roads/node_modules/node-sass/src/libsass/src/utf8_string.cpp
- /bergerac-roads/node_modules/node-sass/src/libsass/src/file.hpp
- /bergerac-roads/node_modules/node-sass/src/callback_bridge.h
- /bergerac-roads/node_modules/node-sass/src/libsass/src/sass.cpp
- /bergerac-roads/node_modules/node-sass/src/libsass/src/node.hpp
- /bergerac-roads/node_modules/node-sass/src/libsass/src/environment.cpp
- /bergerac-roads/node_modules/node-sass/src/libsass/src/extend.hpp
- /bergerac-roads/node_modules/node-sass/src/libsass/src/operators.hpp
- /bergerac-roads/node_modules/node-sass/src/libsass/src/constants.hpp
- /bergerac-roads/node_modules/node-sass/src/libsass/src/sass.hpp
- /bergerac-roads/node_modules/node-sass/src/libsass/src/ast_fwd_decl.cpp
- /bergerac-roads/node_modules/node-sass/src/libsass/src/inspect.cpp
- /bergerac-roads/node_modules/node-sass/src/libsass/src/parser.hpp
- /bergerac-roads/node_modules/node-sass/src/libsass/src/constants.cpp
- /bergerac-roads/node_modules/node-sass/src/sass_types/list.cpp
- /bergerac-roads/node_modules/node-sass/src/libsass/src/cssize.cpp
- /bergerac-roads/node_modules/node-sass/src/libsass/include/sass/functions.h
- /bergerac-roads/node_modules/node-sass/src/libsass/src/util.cpp
- /bergerac-roads/node_modules/node-sass/src/custom_function_bridge.cpp
- /bergerac-roads/node_modules/node-sass/src/libsass/src/context.hpp
- /bergerac-roads/node_modules/node-sass/src/custom_importer_bridge.h
- /bergerac-roads/node_modules/node-sass/src/libsass/src/bind.cpp
- /bergerac-roads/node_modules/node-sass/src/libsass/src/sass_functions.cpp
- /bergerac-roads/node_modules/node-sass/src/libsass/src/backtrace.cpp
- /bergerac-roads/node_modules/node-sass/src/libsass/src/cencode.c
- /bergerac-roads/node_modules/node-sass/src/libsass/src/extend.cpp
- /bergerac-roads/node_modules/node-sass/src/sass_types/sass_value_wrapper.h
- /bergerac-roads/node_modules/node-sass/src/libsass/src/file.cpp
- /bergerac-roads/node_modules/node-sass/src/libsass/src/debugger.hpp
- /bergerac-roads/node_modules/node-sass/src/libsass/src/context.cpp
- /bergerac-roads/node_modules/node-sass/src/libsass/src/base64vlq.cpp
- /bergerac-roads/node_modules/node-sass/src/sass_types/number.cpp
- /bergerac-roads/node_modules/node-sass/src/sass_types/color.h
- /bergerac-roads/node_modules/node-sass/src/libsass/src/c99func.c
- /bergerac-roads/node_modules/node-sass/src/libsass/src/position.cpp
- /bergerac-roads/node_modules/node-sass/src/libsass/src/remove_placeholders.hpp
- /bergerac-roads/node_modules/node-sass/src/libsass/src/sass_values.cpp
- /bergerac-roads/node_modules/node-sass/src/libsass/include/sass/values.h
- /bergerac-roads/node_modules/node-sass/src/libsass/test/test_subset_map.cpp
- /bergerac-roads/node_modules/node-sass/src/libsass/src/sass2scss.cpp
- /bergerac-roads/node_modules/node-sass/src/sass_types/null.cpp
- /bergerac-roads/node_modules/node-sass/src/libsass/src/ast.cpp
- /bergerac-roads/node_modules/node-sass/src/libsass/src/to_c.cpp
- /bergerac-roads/node_modules/node-sass/src/libsass/src/to_value.hpp
- /bergerac-roads/node_modules/node-sass/src/libsass/src/color_maps.hpp
- /bergerac-roads/node_modules/node-sass/src/sass_context_wrapper.cpp
- /bergerac-roads/node_modules/node-sass/src/libsass/src/sass_context.cpp
- /bergerac-roads/node_modules/node-sass/src/libsass/script/test-leaks.pl
- /bergerac-roads/node_modules/node-sass/src/libsass/src/lexer.hpp
- /bergerac-roads/node_modules/node-sass/src/libsass/src/memory/SharedPtr.hpp
- /bergerac-roads/node_modules/node-sass/src/libsass/src/to_c.hpp
- /bergerac-roads/node_modules/node-sass/src/sass_types/map.cpp
- /bergerac-roads/node_modules/node-sass/src/libsass/src/to_value.cpp
- /bergerac-roads/node_modules/node-sass/src/libsass/src/b64/encode.h
- /bergerac-roads/node_modules/node-sass/src/libsass/src/environment.hpp
- /bergerac-roads/node_modules/node-sass/src/libsass/src/plugins.hpp
- /bergerac-roads/node_modules/node-sass/src/libsass/src/debug.hpp
</p>
</details>
<p></p>
</p>
</details>
<p></p>
<details><summary><img src='https://www.whitesourcesoftware.com/wp-content/uploads/2018/10/low_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
In LibSass 3.5.5, a NULL Pointer Dereference in the function Sass::Selector_List::populate_extends in SharedPtr.hpp (used by ast.cpp and ast_selectors.cpp) may cause a Denial of Service (application crash) via a crafted sass input file.
<p>Publish Date: 2018-12-03
<p>URL: <a href=https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-19797>CVE-2018-19797</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>3.5</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://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-19827">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-19827</a></p>
<p>Fix Resolution: No fix version</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 low severity vulnerability detected by whitesource cve low severity vulnerability vulnerable library node rainbow node js bindings to libsass library home page a href library source files the source files were matched to this source library based on a best effort match source libraries are selected from a list of probable public libraries bergerac roads node modules node sass src libsass src expand hpp bergerac roads node modules node sass src binding cpp bergerac roads node modules node sass src libsass src color maps cpp bergerac roads node modules node sass src libsass src sass util hpp bergerac roads node modules node sass src libsass src parser cpp bergerac roads node modules node sass src libsass src unchecked h bergerac roads node modules node sass src libsass src output hpp bergerac roads node modules node sass src libsass src sass values hpp bergerac roads node modules node sass src libsass src util hpp bergerac roads node modules node sass src libsass src emitter hpp bergerac roads node modules node sass src libsass src lexer cpp bergerac roads node modules node sass src libsass test test node cpp bergerac roads node modules node sass src libsass include sass context h bergerac roads node modules node sass src libsass src plugins cpp bergerac roads node modules node sass src libsass include sass base h bergerac roads node modules node sass src libsass src position hpp bergerac roads node modules node sass src libsass src subset map hpp bergerac roads node modules node sass src libsass src operation hpp bergerac roads node modules node sass src libsass src remove placeholders cpp bergerac roads node modules node sass src libsass src operators cpp bergerac roads node modules node sass src libsass src error handling hpp bergerac roads node modules node sass src custom importer bridge cpp bergerac roads node modules node sass src libsass contrib plugin cpp bergerac roads node modules node sass src libsass src functions hpp bergerac roads node modules node sass src libsass src sass context hpp bergerac roads node modules node sass src libsass test test superselector cpp bergerac roads node modules node sass src libsass src eval hpp bergerac roads node modules node sass src libsass src string hpp bergerac roads node modules node sass src sass context wrapper h bergerac roads node modules node sass src libsass src error handling cpp bergerac roads node modules node sass src libsass src node cpp bergerac roads node modules node sass src libsass src subset map cpp bergerac roads node modules node sass src libsass src emitter cpp bergerac roads node modules node sass src libsass src listize cpp bergerac roads node modules node sass src libsass src ast hpp bergerac roads node modules node sass src libsass src sass functions hpp bergerac roads node modules node sass src libsass src memory sharedptr cpp bergerac roads node modules node sass src libsass src output cpp bergerac roads node modules node sass src libsass src check nesting cpp bergerac roads node modules node sass src libsass src ast def macros hpp bergerac roads node modules node sass src libsass src functions cpp bergerac roads node modules node sass src libsass src cssize hpp bergerac roads node modules node sass src libsass src prelexer cpp bergerac roads node modules node sass src libsass src paths hpp bergerac roads node modules node sass src libsass src ast fwd decl hpp bergerac roads node modules node sass src libsass src inspect hpp bergerac roads node modules node sass src sass types color cpp bergerac roads node modules node sass src libsass test test unification cpp bergerac roads node modules node sass src libsass src values cpp bergerac roads node modules node sass src libsass src sass util cpp bergerac roads node modules node sass src libsass src source map hpp bergerac roads node modules node sass src sass types list h bergerac roads node modules node sass src libsass src check nesting hpp bergerac roads node modules node sass src libsass src json cpp bergerac roads node modules node sass src libsass src units cpp bergerac roads node modules node sass src libsass src units hpp bergerac roads node modules node sass src libsass src checked h bergerac roads node modules node sass src libsass src listize hpp bergerac roads node modules node sass src sass types string cpp bergerac roads node modules node sass src libsass src prelexer hpp bergerac roads node modules node sass src sass types boolean h bergerac roads node modules node sass src libsass include h bergerac roads node modules node sass src libsass src eval cpp bergerac roads node modules node sass src libsass src expand cpp bergerac roads node modules node sass src sass types factory cpp bergerac roads node modules node sass src sass types boolean cpp bergerac roads node modules node sass src libsass src source map cpp bergerac roads node modules node sass src sass types value h bergerac roads node modules node sass src libsass src string cpp bergerac roads node modules node sass src libsass src file hpp bergerac roads node modules node sass src callback bridge h bergerac roads node modules node sass src libsass src sass cpp bergerac roads node modules node sass src libsass src node hpp bergerac roads node modules node sass src libsass src environment cpp bergerac roads node modules node sass src libsass src extend hpp bergerac roads node modules node sass src libsass src operators hpp bergerac roads node modules node sass src libsass src constants hpp bergerac roads node modules node sass src libsass src sass hpp bergerac roads node modules node sass src libsass src ast fwd decl cpp bergerac roads node modules node sass src libsass src inspect cpp bergerac roads node modules node sass src libsass src parser hpp bergerac roads node modules node sass src libsass src constants cpp bergerac roads node modules node sass src sass types list cpp bergerac roads node modules node sass src libsass src cssize cpp bergerac roads node modules node sass src libsass include sass functions h bergerac roads node modules node sass src libsass src util cpp bergerac roads node modules node sass src custom function bridge cpp bergerac roads node modules node sass src libsass src context hpp bergerac roads node modules node sass src custom importer bridge h bergerac roads node modules node sass src libsass src bind cpp bergerac roads node modules node sass src libsass src sass functions cpp bergerac roads node modules node sass src libsass src backtrace cpp bergerac roads node modules node sass src libsass src cencode c bergerac roads node modules node sass src libsass src extend cpp bergerac roads node modules node sass src sass types sass value wrapper h bergerac roads node modules node sass src libsass src file cpp bergerac roads node modules node sass src libsass src debugger hpp bergerac roads node modules node sass src libsass src context cpp bergerac roads node modules node sass src libsass src cpp bergerac roads node modules node sass src sass types number cpp bergerac roads node modules node sass src sass types color h bergerac roads node modules node sass src libsass src c bergerac roads node modules node sass src libsass src position cpp bergerac roads node modules node sass src libsass src remove placeholders hpp bergerac roads node modules node sass src libsass src sass values cpp bergerac roads node modules node sass src libsass include sass values h bergerac roads node modules node sass src libsass test test subset map cpp bergerac roads node modules node sass src libsass src cpp bergerac roads node modules node sass src sass types null cpp bergerac roads node modules node sass src libsass src ast cpp bergerac roads node modules node sass src libsass src to c cpp bergerac roads node modules node sass src libsass src to value hpp bergerac roads node modules node sass src libsass src color maps hpp bergerac roads node modules node sass src sass context wrapper cpp bergerac roads node modules node sass src libsass src sass context cpp bergerac roads node modules node sass src libsass script test leaks pl bergerac roads node modules node sass src libsass src lexer hpp bergerac roads node modules node sass src libsass src memory sharedptr hpp bergerac roads node modules node sass src libsass src to c hpp bergerac roads node modules node sass src sass types map cpp bergerac roads node modules node sass src libsass src to value cpp bergerac roads node modules node sass src libsass src encode h bergerac roads node modules node sass src libsass src environment hpp bergerac roads node modules node sass src libsass src plugins hpp bergerac roads node modules node sass src libsass src debug hpp vulnerability details in libsass a null pointer dereference in the function sass selector list populate extends in sharedptr hpp used by ast cpp and ast selectors cpp may cause a denial of service application crash via a crafted sass input file publish date url a href cvss score details base score metrics not available suggested fix type upgrade version origin a href fix resolution no fix version step up your open source security game with whitesource | 0 |
268,420 | 28,565,968,629 | IssuesEvent | 2023-04-21 02:08:57 | andygonzalez2010/store | https://api.github.com/repos/andygonzalez2010/store | closed | CVE-2021-3805 (High) detected in object-path-0.9.2.tgz - autoclosed | Mend: dependency security vulnerability | ## CVE-2021-3805 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>object-path-0.9.2.tgz</b></p></summary>
<p>Access deep properties using a path</p>
<p>Library home page: <a href="https://registry.npmjs.org/object-path/-/object-path-0.9.2.tgz">https://registry.npmjs.org/object-path/-/object-path-0.9.2.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/object-path/package.json</p>
<p>
Dependency Hierarchy:
- browser-sync-2.26.5.tgz (Root Library)
- eazy-logger-3.0.2.tgz
- tfunk-3.1.0.tgz
- :x: **object-path-0.9.2.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/andygonzalez2010/store/commit/3f6d614029f4d6cfdddfcef8468949cb7822503c">3f6d614029f4d6cfdddfcef8468949cb7822503c</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>
object-path is vulnerable to Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution')
<p>Publish Date: 2021-09-17
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2021-3805>CVE-2021-3805</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://huntr.dev/bounties/571e3baf-7c46-46e3-9003-ba7e4e623053/">https://huntr.dev/bounties/571e3baf-7c46-46e3-9003-ba7e4e623053/</a></p>
<p>Release Date: 2021-09-17</p>
<p>Fix Resolution (object-path): 0.11.8</p>
<p>Direct dependency fix Resolution (browser-sync): 2.26.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-2021-3805 (High) detected in object-path-0.9.2.tgz - autoclosed - ## CVE-2021-3805 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>object-path-0.9.2.tgz</b></p></summary>
<p>Access deep properties using a path</p>
<p>Library home page: <a href="https://registry.npmjs.org/object-path/-/object-path-0.9.2.tgz">https://registry.npmjs.org/object-path/-/object-path-0.9.2.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/object-path/package.json</p>
<p>
Dependency Hierarchy:
- browser-sync-2.26.5.tgz (Root Library)
- eazy-logger-3.0.2.tgz
- tfunk-3.1.0.tgz
- :x: **object-path-0.9.2.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/andygonzalez2010/store/commit/3f6d614029f4d6cfdddfcef8468949cb7822503c">3f6d614029f4d6cfdddfcef8468949cb7822503c</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>
object-path is vulnerable to Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution')
<p>Publish Date: 2021-09-17
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2021-3805>CVE-2021-3805</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://huntr.dev/bounties/571e3baf-7c46-46e3-9003-ba7e4e623053/">https://huntr.dev/bounties/571e3baf-7c46-46e3-9003-ba7e4e623053/</a></p>
<p>Release Date: 2021-09-17</p>
<p>Fix Resolution (object-path): 0.11.8</p>
<p>Direct dependency fix Resolution (browser-sync): 2.26.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 high detected in object path tgz autoclosed cve high severity vulnerability vulnerable library object path tgz access deep properties using a path library home page a href path to dependency file package json path to vulnerable library node modules object path package json dependency hierarchy browser sync tgz root library eazy logger tgz tfunk tgz x object path tgz vulnerable library found in head commit a href found in base branch master vulnerability details object path is vulnerable to improperly controlled modification of object prototype attributes prototype pollution publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact 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 object path direct dependency fix resolution browser sync step up your open source security game with mend | 0 |
26,988 | 6,812,976,446 | IssuesEvent | 2017-11-06 07:02:09 | BTDF/DeploymentFramework | https://api.github.com/repos/BTDF/DeploymentFramework | closed | Fix issue where test for existing service instances was skipped | bug CodePlexMigrationInitiated General Impact: High Release 5.0 | Fix issue where test for existing service instances was skipped
#### This work item was migrated from CodePlex
CodePlex work item ID: '6500'
Assigned to: 'tfabraham'
Vote count: '0'
| 1.0 | Fix issue where test for existing service instances was skipped - Fix issue where test for existing service instances was skipped
#### This work item was migrated from CodePlex
CodePlex work item ID: '6500'
Assigned to: 'tfabraham'
Vote count: '0'
| non_priority | fix issue where test for existing service instances was skipped fix issue where test for existing service instances was skipped this work item was migrated from codeplex codeplex work item id assigned to tfabraham vote count | 0 |
49,022 | 10,315,171,163 | IssuesEvent | 2019-08-30 06:43:33 | intellij-rust/intellij-rust | https://api.github.com/repos/intellij-rust/intellij-rust | closed | "Implement members" ignores arbitrary self types. | bug code insight | ## Environment
* **IntelliJ Rust plugin version:** 0.2.102.2682-192-nightly
## Problem description
`self` is inserted as `Self` instead of one of a few new self types stabilized recently on the way to arbitrary self types.
## Steps to reproduce
Code:
```rust
trait X {
fn x(self: Pin<&mut Self>);
fn y(self: *const Self);
}
struct A{}
impl X for A {
}
```
Use the "implement members" quick fix.
| 1.0 | "Implement members" ignores arbitrary self types. - ## Environment
* **IntelliJ Rust plugin version:** 0.2.102.2682-192-nightly
## Problem description
`self` is inserted as `Self` instead of one of a few new self types stabilized recently on the way to arbitrary self types.
## Steps to reproduce
Code:
```rust
trait X {
fn x(self: Pin<&mut Self>);
fn y(self: *const Self);
}
struct A{}
impl X for A {
}
```
Use the "implement members" quick fix.
| non_priority | implement members ignores arbitrary self types environment intellij rust plugin version nightly problem description self is inserted as self instead of one of a few new self types stabilized recently on the way to arbitrary self types steps to reproduce code rust trait x fn x self pin fn y self const self struct a impl x for a use the implement members quick fix | 0 |
103,706 | 16,604,665,088 | IssuesEvent | 2021-06-02 01:16:28 | greenetx/jenkins2-course-spring-boot | https://api.github.com/repos/greenetx/jenkins2-course-spring-boot | opened | CVE-2019-14888 (High) detected in undertow-core-1.3.23.Final.jar | security vulnerability | ## CVE-2019-14888 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>undertow-core-1.3.23.Final.jar</b></p></summary>
<p>Undertow</p>
<p>Library home page: <a href="http://www.jboss.org/">http://www.jboss.org/</a></p>
<p>Path to dependency file: /jenkins2-course-spring-boot/spring-boot-autoconfigure/pom.xml</p>
<p>Path to vulnerable library: /root/.m2/repository/io/undertow/undertow-core/1.3.23.Final/undertow-core-1.3.23.Final.jar,2/repository/io/undertow/undertow-core/1.3.23.Final/undertow-core-1.3.23.Final.jar,/root/.m2/repository/io/undertow/undertow-core/1.3.23.Final/undertow-core-1.3.23.Final.jar,/root/.m2/repository/io/undertow/undertow-core/1.3.23.Final/undertow-core-1.3.23.Final.jar,/root/.m2/repository/io/undertow/undertow-core/1.3.23.Final/undertow-core-1.3.23.Final.jar</p>
<p>
Dependency Hierarchy:
- :x: **undertow-core-1.3.23.Final.jar** (Vulnerable Library)
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
A vulnerability was found in the Undertow HTTP server in versions before 2.0.28.SP1 when listening on HTTPS. An attacker can target the HTTPS port to carry out a Denial Of Service (DOS) to make the service unavailable on SSL.
<p>Publish Date: 2020-01-23
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-14888>CVE-2019-14888</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://issues.redhat.com/browse/UNDERTOW-1623">https://issues.redhat.com/browse/UNDERTOW-1623</a></p>
<p>Release Date: 2020-03-11</p>
<p>Fix Resolution: 2.0.30.Final</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-14888 (High) detected in undertow-core-1.3.23.Final.jar - ## CVE-2019-14888 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>undertow-core-1.3.23.Final.jar</b></p></summary>
<p>Undertow</p>
<p>Library home page: <a href="http://www.jboss.org/">http://www.jboss.org/</a></p>
<p>Path to dependency file: /jenkins2-course-spring-boot/spring-boot-autoconfigure/pom.xml</p>
<p>Path to vulnerable library: /root/.m2/repository/io/undertow/undertow-core/1.3.23.Final/undertow-core-1.3.23.Final.jar,2/repository/io/undertow/undertow-core/1.3.23.Final/undertow-core-1.3.23.Final.jar,/root/.m2/repository/io/undertow/undertow-core/1.3.23.Final/undertow-core-1.3.23.Final.jar,/root/.m2/repository/io/undertow/undertow-core/1.3.23.Final/undertow-core-1.3.23.Final.jar,/root/.m2/repository/io/undertow/undertow-core/1.3.23.Final/undertow-core-1.3.23.Final.jar</p>
<p>
Dependency Hierarchy:
- :x: **undertow-core-1.3.23.Final.jar** (Vulnerable Library)
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
A vulnerability was found in the Undertow HTTP server in versions before 2.0.28.SP1 when listening on HTTPS. An attacker can target the HTTPS port to carry out a Denial Of Service (DOS) to make the service unavailable on SSL.
<p>Publish Date: 2020-01-23
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-14888>CVE-2019-14888</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://issues.redhat.com/browse/UNDERTOW-1623">https://issues.redhat.com/browse/UNDERTOW-1623</a></p>
<p>Release Date: 2020-03-11</p>
<p>Fix Resolution: 2.0.30.Final</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 undertow core final jar cve high severity vulnerability vulnerable library undertow core final jar undertow library home page a href path to dependency file course spring boot spring boot autoconfigure pom xml path to vulnerable library root repository io undertow undertow core final undertow core final jar repository io undertow undertow core final undertow core final jar root repository io undertow undertow core final undertow core final jar root repository io undertow undertow core final undertow core final jar root repository io undertow undertow core final undertow core final jar dependency hierarchy x undertow core final jar vulnerable library vulnerability details a vulnerability was found in the undertow http server in versions before when listening on https an attacker can target the https port to carry out a denial of service dos to make the service unavailable on ssl 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 final step up your open source security game with whitesource | 0 |
158,314 | 12,412,289,353 | IssuesEvent | 2020-05-22 10:15:20 | aliasrobotics/RVD | https://api.github.com/repos/aliasrobotics/RVD | opened | 938] | bug cppcheck static analysis testing triage | ```yaml
{
"id": 1,
"title": "938]",
"type": "bug",
"description": "[src/opencv3/3rdparty/libjpeg/jmemmgr.c:983] -> [src/opencv3/3rdparty/libjpeg/jmemmgr.c:938]: (warning) Either the condition 'pool_id>=2' is redundant or the array 'mem->small_list[2]' is accessed at index 2, which is out of bounds.",
"cwe": "None",
"cve": "None",
"keywords": [
"cppcheck",
"static analysis",
"testing",
"triage",
"bug"
],
"system": "src/opencv3/3rdparty/libjpeg/jmemmgr.c",
"vendor": null,
"severity": {
"rvss-score": 0,
"rvss-vector": "",
"severity-description": "",
"cvss-score": 0,
"cvss-vector": ""
},
"links": "",
"flaw": {
"phase": "testing",
"specificity": "N/A",
"architectural-location": "N/A",
"application": "N/A",
"subsystem": "N/A",
"package": "N/A",
"languages": "None",
"date-detected": "2020-05-22 (10:15)",
"detected-by": "Alias Robotics",
"detected-by-method": "testing static",
"date-reported": "2020-05-22 (10:15)",
"reported-by": "Alias Robotics",
"reported-by-relationship": "automatic",
"issue": "",
"reproducibility": "always",
"trace": "",
"reproduction": "See artifacts below (if available)",
"reproduction-image": "gitlab.com/aliasrobotics/offensive/alurity/pipelines/active/pipeline_ros_kinetic/-/jobs/563367426/artifacts/download"
},
"exploitation": {
"description": "",
"exploitation-image": "",
"exploitation-vector": ""
},
"mitigation": {
"description": "",
"pull-request": "",
"date-mitigation": ""
}
}
``` | 1.0 | 938] - ```yaml
{
"id": 1,
"title": "938]",
"type": "bug",
"description": "[src/opencv3/3rdparty/libjpeg/jmemmgr.c:983] -> [src/opencv3/3rdparty/libjpeg/jmemmgr.c:938]: (warning) Either the condition 'pool_id>=2' is redundant or the array 'mem->small_list[2]' is accessed at index 2, which is out of bounds.",
"cwe": "None",
"cve": "None",
"keywords": [
"cppcheck",
"static analysis",
"testing",
"triage",
"bug"
],
"system": "src/opencv3/3rdparty/libjpeg/jmemmgr.c",
"vendor": null,
"severity": {
"rvss-score": 0,
"rvss-vector": "",
"severity-description": "",
"cvss-score": 0,
"cvss-vector": ""
},
"links": "",
"flaw": {
"phase": "testing",
"specificity": "N/A",
"architectural-location": "N/A",
"application": "N/A",
"subsystem": "N/A",
"package": "N/A",
"languages": "None",
"date-detected": "2020-05-22 (10:15)",
"detected-by": "Alias Robotics",
"detected-by-method": "testing static",
"date-reported": "2020-05-22 (10:15)",
"reported-by": "Alias Robotics",
"reported-by-relationship": "automatic",
"issue": "",
"reproducibility": "always",
"trace": "",
"reproduction": "See artifacts below (if available)",
"reproduction-image": "gitlab.com/aliasrobotics/offensive/alurity/pipelines/active/pipeline_ros_kinetic/-/jobs/563367426/artifacts/download"
},
"exploitation": {
"description": "",
"exploitation-image": "",
"exploitation-vector": ""
},
"mitigation": {
"description": "",
"pull-request": "",
"date-mitigation": ""
}
}
``` | non_priority | yaml id title type bug description warning either the condition pool id is redundant or the array mem small list is accessed at index which is out of bounds cwe none cve none keywords cppcheck static analysis testing triage bug system src libjpeg jmemmgr c vendor null severity rvss score rvss vector severity description cvss score cvss vector links flaw phase testing specificity n a architectural location n a application n a subsystem n a package n a languages none date detected detected by alias robotics detected by method testing static date reported reported by alias robotics reported by relationship automatic issue reproducibility always trace reproduction see artifacts below if available reproduction image gitlab com aliasrobotics offensive alurity pipelines active pipeline ros kinetic jobs artifacts download exploitation description exploitation image exploitation vector mitigation description pull request date mitigation | 0 |
275,227 | 20,913,462,959 | IssuesEvent | 2022-03-24 11:21:25 | firebase/flutterfire | https://api.github.com/repos/firebase/flutterfire | closed | [📚] google_sign_in docs ref is heading to 404 page | type: bug type: documentation good first issue | When I'm going through the [usage part of CLI](https://firebase.flutter.dev/docs/cli/#usage), There I saw `google_sign_in` manual installation references. When I click on that it goes [here](https://firebase.flutter.dev/docs/cli/auth/social#google)(404 page) | 1.0 | [📚] google_sign_in docs ref is heading to 404 page - When I'm going through the [usage part of CLI](https://firebase.flutter.dev/docs/cli/#usage), There I saw `google_sign_in` manual installation references. When I click on that it goes [here](https://firebase.flutter.dev/docs/cli/auth/social#google)(404 page) | non_priority | google sign in docs ref is heading to page when i m going through the there i saw google sign in manual installation references when i click on that it goes page | 0 |
98,639 | 11,091,798,432 | IssuesEvent | 2019-12-15 14:49:27 | TDAmeritrade/stumpy | https://api.github.com/repos/TDAmeritrade/stumpy | opened | Check for "dimensioanl" typos | documentation enhancement | There are some typos in the docstrings where "dimensional" is mis-spelled as "dimensioanl". We need to check if any other ones exist. | 1.0 | Check for "dimensioanl" typos - There are some typos in the docstrings where "dimensional" is mis-spelled as "dimensioanl". We need to check if any other ones exist. | non_priority | check for dimensioanl typos there are some typos in the docstrings where dimensional is mis spelled as dimensioanl we need to check if any other ones exist | 0 |
138,697 | 12,826,982,987 | IssuesEvent | 2020-07-06 17:34:56 | rstudio/rstudio | https://api.github.com/repos/rstudio/rstudio | opened | Update Terminal support article for 1.3 | documentation terminal | The Terminal pane in RStudio 1.3 now supports custom shells for Windows (previously only available on Mac/Linux).
Should update support article to mention that, and show an example for hooking up RTools4 as a terminal per #6810.
Also a quick skim for other helpful updates since this article was written for RStudio 1.1 and terminal has had several other enhancements.
https://support.rstudio.com/hc/en-us/articles/115010737148-Using-the-RStudio-Terminal | 1.0 | Update Terminal support article for 1.3 - The Terminal pane in RStudio 1.3 now supports custom shells for Windows (previously only available on Mac/Linux).
Should update support article to mention that, and show an example for hooking up RTools4 as a terminal per #6810.
Also a quick skim for other helpful updates since this article was written for RStudio 1.1 and terminal has had several other enhancements.
https://support.rstudio.com/hc/en-us/articles/115010737148-Using-the-RStudio-Terminal | non_priority | update terminal support article for the terminal pane in rstudio now supports custom shells for windows previously only available on mac linux should update support article to mention that and show an example for hooking up as a terminal per also a quick skim for other helpful updates since this article was written for rstudio and terminal has had several other enhancements | 0 |
10,216 | 4,021,481,812 | IssuesEvent | 2016-05-16 22:08:08 | buckte/buckte | https://api.github.com/repos/buckte/buckte | closed | Fix "Insecure Dependency" issue in Gemfile.lock | codeclimate | Nested attributes rejection proc bypass in Active Record
https://codeclimate.com/github/buckte/buckte/Gemfile.lock#issue_573a287e737f7500019ec40e | 1.0 | Fix "Insecure Dependency" issue in Gemfile.lock - Nested attributes rejection proc bypass in Active Record
https://codeclimate.com/github/buckte/buckte/Gemfile.lock#issue_573a287e737f7500019ec40e | non_priority | fix insecure dependency issue in gemfile lock nested attributes rejection proc bypass in active record | 0 |
312,011 | 23,413,287,134 | IssuesEvent | 2022-08-12 20:10:34 | mikyurkev/Most_to_Coast_v2 | https://api.github.com/repos/mikyurkev/Most_to_Coast_v2 | opened | Front-end: Accessibility: Better Dark/Light background contrast. | documentation enhancement | - Improve accessibility by better-contrasted background for people with disability. | 1.0 | Front-end: Accessibility: Better Dark/Light background contrast. - - Improve accessibility by better-contrasted background for people with disability. | non_priority | front end accessibility better dark light background contrast improve accessibility by better contrasted background for people with disability | 0 |
110,871 | 24,023,818,630 | IssuesEvent | 2022-09-15 09:47:59 | gitpod-io/gitpod | https://api.github.com/repos/gitpod-io/gitpod | closed | embed service status of Gitpod into Gitpod | type: feature request user experience component: dashboard editor: code (browser) meta: never-stale operations: observability | Here are the configuration options:
<img width="488" alt="2021-05-06_19-30-03" src="https://user-images.githubusercontent.com/127353/117275565-80df0800-aea1-11eb-83b2-e75bf6a9cd03.png">
Here is the JavaScript embed
```javascript
<script src="https://2wkvzfyrpv0h.statuspage.io/embed/script.js"></script>
```
Alternatively we could build our own:
<img width="547" alt="2021-05-06_19-31-39" src="https://user-images.githubusercontent.com/127353/117275761-b71c8780-aea1-11eb-9e57-83475fecef33.png">
- https://www.npmjs.com/package/@statuspage/status-widget
- https://status.gitpod.io/api | 1.0 | embed service status of Gitpod into Gitpod - Here are the configuration options:
<img width="488" alt="2021-05-06_19-30-03" src="https://user-images.githubusercontent.com/127353/117275565-80df0800-aea1-11eb-83b2-e75bf6a9cd03.png">
Here is the JavaScript embed
```javascript
<script src="https://2wkvzfyrpv0h.statuspage.io/embed/script.js"></script>
```
Alternatively we could build our own:
<img width="547" alt="2021-05-06_19-31-39" src="https://user-images.githubusercontent.com/127353/117275761-b71c8780-aea1-11eb-9e57-83475fecef33.png">
- https://www.npmjs.com/package/@statuspage/status-widget
- https://status.gitpod.io/api | non_priority | embed service status of gitpod into gitpod here are the configuration options img width alt src here is the javascript embed javascript script src alternatively we could build our own img width alt src | 0 |
114,561 | 14,597,443,871 | IssuesEvent | 2020-12-20 20:09:28 | coding-circle/charades | https://api.github.com/repos/coding-circle/charades | opened | Add edit score feature to host settings panel. | client design restAPI server | Occasionally the score can get messed up by someone clicking the wrong buttons following a turn. The goal of this is to add fields to adjust the score for each team.
Should coordinate with @anderspollack on designs, but open to creating your own designs and taking feedback.
**Requirements**
- Edit restAPI documentation with new endpoint for editing score
- Add to client
- Add testing
- Add route, controller | 1.0 | Add edit score feature to host settings panel. - Occasionally the score can get messed up by someone clicking the wrong buttons following a turn. The goal of this is to add fields to adjust the score for each team.
Should coordinate with @anderspollack on designs, but open to creating your own designs and taking feedback.
**Requirements**
- Edit restAPI documentation with new endpoint for editing score
- Add to client
- Add testing
- Add route, controller | non_priority | add edit score feature to host settings panel occasionally the score can get messed up by someone clicking the wrong buttons following a turn the goal of this is to add fields to adjust the score for each team should coordinate with anderspollack on designs but open to creating your own designs and taking feedback requirements edit restapi documentation with new endpoint for editing score add to client add testing add route controller | 0 |
110,909 | 17,009,627,099 | IssuesEvent | 2021-07-02 00:57:39 | Chiencc/angular | https://api.github.com/repos/Chiencc/angular | opened | CVE-2017-16024 (Medium) detected in sync-exec-0.6.2.tgz | security vulnerability | ## CVE-2017-16024 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>sync-exec-0.6.2.tgz</b></p></summary>
<p>Synchronous exec with status code support. Requires no external dependencies, no need for node-gyp compilations etc.</p>
<p>Library home page: <a href="https://registry.npmjs.org/sync-exec/-/sync-exec-0.6.2.tgz">https://registry.npmjs.org/sync-exec/-/sync-exec-0.6.2.tgz</a></p>
<p>Path to dependency file: angular/package.json</p>
<p>Path to vulnerable library: angular/node_modules/sync-exec</p>
<p>
Dependency Hierarchy:
- npm-run-4.1.0.tgz (Root Library)
- :x: **sync-exec-0.6.2.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/Chiencc/angular/commit/72f7fdba608ab5ba7ff145a21673661d5316ebaa">72f7fdba608ab5ba7ff145a21673661d5316ebaa</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
The sync-exec module is used to simulate child_process.execSync in node versions <0.11.9. Sync-exec uses tmp directories as a buffer before returning values. Other users on the server have read access to the tmp directory, possibly allowing an attacker on the server to obtain confidential information from the buffer/tmp file, while it exists.
<p>Publish Date: 2018-06-04
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2017-16024>CVE-2017-16024</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>6.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: None
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://nodesecurity.io/advisories/310">https://nodesecurity.io/advisories/310</a></p>
<p>Release Date: 2017-04-14</p>
<p>Fix Resolution: There is currently no direct patch for `sync-exec`, as the `child_process.execSync` function provided in Node.js v0.12.0 and later provides the same functionality natively.
The best mitigation currently is to update to Node.js v0.12.0 or later, and migrate all uses of `sync-exec` to `child_process.execSync()`.</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-16024 (Medium) detected in sync-exec-0.6.2.tgz - ## CVE-2017-16024 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>sync-exec-0.6.2.tgz</b></p></summary>
<p>Synchronous exec with status code support. Requires no external dependencies, no need for node-gyp compilations etc.</p>
<p>Library home page: <a href="https://registry.npmjs.org/sync-exec/-/sync-exec-0.6.2.tgz">https://registry.npmjs.org/sync-exec/-/sync-exec-0.6.2.tgz</a></p>
<p>Path to dependency file: angular/package.json</p>
<p>Path to vulnerable library: angular/node_modules/sync-exec</p>
<p>
Dependency Hierarchy:
- npm-run-4.1.0.tgz (Root Library)
- :x: **sync-exec-0.6.2.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/Chiencc/angular/commit/72f7fdba608ab5ba7ff145a21673661d5316ebaa">72f7fdba608ab5ba7ff145a21673661d5316ebaa</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
The sync-exec module is used to simulate child_process.execSync in node versions <0.11.9. Sync-exec uses tmp directories as a buffer before returning values. Other users on the server have read access to the tmp directory, possibly allowing an attacker on the server to obtain confidential information from the buffer/tmp file, while it exists.
<p>Publish Date: 2018-06-04
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2017-16024>CVE-2017-16024</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>6.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: None
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://nodesecurity.io/advisories/310">https://nodesecurity.io/advisories/310</a></p>
<p>Release Date: 2017-04-14</p>
<p>Fix Resolution: There is currently no direct patch for `sync-exec`, as the `child_process.execSync` function provided in Node.js v0.12.0 and later provides the same functionality natively.
The best mitigation currently is to update to Node.js v0.12.0 or later, and migrate all uses of `sync-exec` to `child_process.execSync()`.</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 sync exec tgz cve medium severity vulnerability vulnerable library sync exec tgz synchronous exec with status code support requires no external dependencies no need for node gyp compilations etc library home page a href path to dependency file angular package json path to vulnerable library angular node modules sync exec dependency hierarchy npm run tgz root library x sync exec tgz vulnerable library found in head commit a href found in base branch master vulnerability details the sync exec module is used to simulate child process execsync in node versions sync exec uses tmp directories as a buffer before returning values other users on the server have read access to the tmp directory possibly allowing an attacker on the server to obtain confidential information from the buffer tmp file while it exists publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required low user interaction none scope unchanged impact metrics confidentiality impact high integrity impact none availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution there is currently no direct patch for sync exec as the child process execsync function provided in node js and later provides the same functionality natively the best mitigation currently is to update to node js or later and migrate all uses of sync exec to child process execsync step up your open source security game with whitesource | 0 |
8,108 | 20,968,779,721 | IssuesEvent | 2022-03-28 09:23:00 | MicrosoftDocs/architecture-center | https://api.github.com/repos/MicrosoftDocs/architecture-center | closed | Error regarding blob name | cxp triaged product-question architecture-center/svc Pri2 azure-guide/subsvc |
[I want to read a csv file located in the blob storage. However, I am getting error that specified blob does not exist. I am confused what should be the blob name. I gave LOCALFILENAME as my csv file name seen in the blob container]
---
#### Document Details
⚠ *Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.*
* ID: 647ed505-3e6e-3db7-63ee-025edf6e63f4
* Version Independent ID: d910ba75-6c86-6172-64be-e45ba2bf5a3d
* Content: [Explore data in Azure Blob storage with pandas - Azure Architecture Center](https://docs.microsoft.com/en-us/azure/architecture/data-science-process/explore-data-blob)
* Content Source: [docs/data-science-process/explore-data-blob.md](https://github.com/microsoftdocs/architecture-center/blob/main/docs/data-science-process/explore-data-blob.md)
* Service: **architecture-center**
* Sub-service: **azure-guide**
* GitHub Login: @marktab
* Microsoft Alias: **tdsp** | 1.0 | Error regarding blob name -
[I want to read a csv file located in the blob storage. However, I am getting error that specified blob does not exist. I am confused what should be the blob name. I gave LOCALFILENAME as my csv file name seen in the blob container]
---
#### Document Details
⚠ *Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.*
* ID: 647ed505-3e6e-3db7-63ee-025edf6e63f4
* Version Independent ID: d910ba75-6c86-6172-64be-e45ba2bf5a3d
* Content: [Explore data in Azure Blob storage with pandas - Azure Architecture Center](https://docs.microsoft.com/en-us/azure/architecture/data-science-process/explore-data-blob)
* Content Source: [docs/data-science-process/explore-data-blob.md](https://github.com/microsoftdocs/architecture-center/blob/main/docs/data-science-process/explore-data-blob.md)
* Service: **architecture-center**
* Sub-service: **azure-guide**
* GitHub Login: @marktab
* Microsoft Alias: **tdsp** | non_priority | error regarding blob name document details ⚠ do not edit this section it is required for docs microsoft com ➟ github issue linking id version independent id content content source service architecture center sub service azure guide github login marktab microsoft alias tdsp | 0 |
331,960 | 29,174,921,041 | IssuesEvent | 2023-05-19 07:03:52 | unifyai/ivy | https://api.github.com/repos/unifyai/ivy | opened | Fix dtype.test_as_native_dtype | Sub Task Failing Test | | | |
|---|---|
|tensorflow|<a href="https://github.com/unifyai/ivy/actions/runs/5020544812/jobs/9002105988" rel="noopener noreferrer" target="_blank"><img src=https://img.shields.io/badge/-success-success></a>
|torch|<a href="https://github.com/unifyai/ivy/actions/runs/5020544812/jobs/9002105988" rel="noopener noreferrer" target="_blank"><img src=https://img.shields.io/badge/-success-success></a>
|numpy|<a href="https://github.com/unifyai/ivy/actions/runs/5020544812/jobs/9002105988" rel="noopener noreferrer" target="_blank"><img src=https://img.shields.io/badge/-failure-red></a>
|jax|<a href="https://github.com/unifyai/ivy/actions/runs/5020544812/jobs/9002105988" rel="noopener noreferrer" target="_blank"><img src=https://img.shields.io/badge/-success-success></a>
|paddle|<a href="null" rel="noopener noreferrer" target="_blank"><img src=https://img.shields.io/badge/-success-success></a>
<details>
<summary>FAILED ivy_tests/test_ivy/test_functional/test_core/test_dtype.py::test_as_native_dtype[cpu-ivy.functional.backends.numpy-False-False]</summary>
2023-05-19T04:48:06.1826647Z E KeyError: 'cpu'2023-05-19T04:48:06.1834358Z E 2023-05-19T04:48:06.1841876Z E You can reproduce this example by temporarily adding @reproduce_failure('6.75.3', b'AA==') as a decorator on your test case
</details>
| 1.0 | Fix dtype.test_as_native_dtype - | | |
|---|---|
|tensorflow|<a href="https://github.com/unifyai/ivy/actions/runs/5020544812/jobs/9002105988" rel="noopener noreferrer" target="_blank"><img src=https://img.shields.io/badge/-success-success></a>
|torch|<a href="https://github.com/unifyai/ivy/actions/runs/5020544812/jobs/9002105988" rel="noopener noreferrer" target="_blank"><img src=https://img.shields.io/badge/-success-success></a>
|numpy|<a href="https://github.com/unifyai/ivy/actions/runs/5020544812/jobs/9002105988" rel="noopener noreferrer" target="_blank"><img src=https://img.shields.io/badge/-failure-red></a>
|jax|<a href="https://github.com/unifyai/ivy/actions/runs/5020544812/jobs/9002105988" rel="noopener noreferrer" target="_blank"><img src=https://img.shields.io/badge/-success-success></a>
|paddle|<a href="null" rel="noopener noreferrer" target="_blank"><img src=https://img.shields.io/badge/-success-success></a>
<details>
<summary>FAILED ivy_tests/test_ivy/test_functional/test_core/test_dtype.py::test_as_native_dtype[cpu-ivy.functional.backends.numpy-False-False]</summary>
2023-05-19T04:48:06.1826647Z E KeyError: 'cpu'2023-05-19T04:48:06.1834358Z E 2023-05-19T04:48:06.1841876Z E You can reproduce this example by temporarily adding @reproduce_failure('6.75.3', b'AA==') as a decorator on your test case
</details>
| non_priority | fix dtype test as native dtype tensorflow img src torch img src numpy img src jax img src paddle img src failed ivy tests test ivy test functional test core test dtype py test as native dtype e keyerror cpu e e you can reproduce this example by temporarily adding reproduce failure b aa as a decorator on your test case | 0 |
205,295 | 23,322,381,748 | IssuesEvent | 2022-08-08 17:38:32 | jgeraigery/sol003-lifecycle-driver | https://api.github.com/repos/jgeraigery/sol003-lifecycle-driver | opened | logstash-logback-encoder-5.1.jar: 1 vulnerabilities (highest severity is: 6.6) | security vulnerability | <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>logstash-logback-encoder-5.1.jar</b></p></summary>
<p></p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/ch/qos/logback/logback-core/1.2.3/logback-core-1.2.3.jar</p>
<p>
<p>Found in HEAD commit: <a href="https://github.com/jgeraigery/sol003-lifecycle-driver/commit/cf30bd2a5fe3d7593d3325f0f496761e6da5cf1c">cf30bd2a5fe3d7593d3325f0f496761e6da5cf1c</a></p></details>
## Vulnerabilities
| CVE | Severity | <img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS | Dependency | Type | Fixed in | Remediation Available |
| ------------- | ------------- | ----- | ----- | ----- | --- | --- |
| [CVE-2021-42550](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-42550) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 6.6 | logback-core-1.2.3.jar | Transitive | 5.2 | ✅ |
## Details
<details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2021-42550</summary>
### Vulnerable Library - <b>logback-core-1.2.3.jar</b></p>
<p>logback-core module</p>
<p>Library home page: <a href="http://logback.qos.ch">http://logback.qos.ch</a></p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/ch/qos/logback/logback-core/1.2.3/logback-core-1.2.3.jar</p>
<p>
Dependency Hierarchy:
- logstash-logback-encoder-5.1.jar (Root Library)
- :x: **logback-core-1.2.3.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/jgeraigery/sol003-lifecycle-driver/commit/cf30bd2a5fe3d7593d3325f0f496761e6da5cf1c">cf30bd2a5fe3d7593d3325f0f496761e6da5cf1c</a></p>
<p>Found in base branch: <b>develop</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
In logback version 1.2.7 and prior versions, an attacker with the required privileges to edit configurations files could craft a malicious configuration allowing to execute arbitrary code loaded from LDAP servers.
<p>Publish Date: 2021-12-16
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-42550>CVE-2021-42550</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>6.6</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: High
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=VE-2021-42550">https://cve.mitre.org/cgi-bin/cvename.cgi?name=VE-2021-42550</a></p>
<p>Release Date: 2021-12-16</p>
<p>Fix Resolution (ch.qos.logback:logback-core): 1.2.8</p>
<p>Direct dependency fix Resolution (net.logstash.logback:logstash-logback-encoder): 5.2</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation is available for this issue
</details>
***
<p>:rescue_worker_helmet: Automatic Remediation is available for this issue.</p> | True | logstash-logback-encoder-5.1.jar: 1 vulnerabilities (highest severity is: 6.6) - <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>logstash-logback-encoder-5.1.jar</b></p></summary>
<p></p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/ch/qos/logback/logback-core/1.2.3/logback-core-1.2.3.jar</p>
<p>
<p>Found in HEAD commit: <a href="https://github.com/jgeraigery/sol003-lifecycle-driver/commit/cf30bd2a5fe3d7593d3325f0f496761e6da5cf1c">cf30bd2a5fe3d7593d3325f0f496761e6da5cf1c</a></p></details>
## Vulnerabilities
| CVE | Severity | <img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS | Dependency | Type | Fixed in | Remediation Available |
| ------------- | ------------- | ----- | ----- | ----- | --- | --- |
| [CVE-2021-42550](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-42550) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 6.6 | logback-core-1.2.3.jar | Transitive | 5.2 | ✅ |
## Details
<details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2021-42550</summary>
### Vulnerable Library - <b>logback-core-1.2.3.jar</b></p>
<p>logback-core module</p>
<p>Library home page: <a href="http://logback.qos.ch">http://logback.qos.ch</a></p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/ch/qos/logback/logback-core/1.2.3/logback-core-1.2.3.jar</p>
<p>
Dependency Hierarchy:
- logstash-logback-encoder-5.1.jar (Root Library)
- :x: **logback-core-1.2.3.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/jgeraigery/sol003-lifecycle-driver/commit/cf30bd2a5fe3d7593d3325f0f496761e6da5cf1c">cf30bd2a5fe3d7593d3325f0f496761e6da5cf1c</a></p>
<p>Found in base branch: <b>develop</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
In logback version 1.2.7 and prior versions, an attacker with the required privileges to edit configurations files could craft a malicious configuration allowing to execute arbitrary code loaded from LDAP servers.
<p>Publish Date: 2021-12-16
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-42550>CVE-2021-42550</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>6.6</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: High
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=VE-2021-42550">https://cve.mitre.org/cgi-bin/cvename.cgi?name=VE-2021-42550</a></p>
<p>Release Date: 2021-12-16</p>
<p>Fix Resolution (ch.qos.logback:logback-core): 1.2.8</p>
<p>Direct dependency fix Resolution (net.logstash.logback:logstash-logback-encoder): 5.2</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation is available for this issue
</details>
***
<p>:rescue_worker_helmet: Automatic Remediation is available for this issue.</p> | non_priority | logstash logback encoder jar vulnerabilities highest severity is vulnerable library logstash logback encoder jar path to dependency file pom xml path to vulnerable library home wss scanner repository ch qos logback logback core logback core jar found in head commit a href vulnerabilities cve severity cvss dependency type fixed in remediation available medium logback core jar transitive details cve vulnerable library logback core jar logback core module library home page a href path to dependency file pom xml path to vulnerable library home wss scanner repository ch qos logback logback core logback core jar dependency hierarchy logstash logback encoder jar root library x logback core jar vulnerable library found in head commit a href found in base branch develop vulnerability details in logback version and prior versions an attacker with the required privileges to edit configurations files could craft a malicious configuration allowing to execute arbitrary code loaded from ldap servers publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity high 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 ch qos logback logback core direct dependency fix resolution net logstash logback logstash logback encoder rescue worker helmet automatic remediation is available for this issue rescue worker helmet automatic remediation is available for this issue | 0 |
271,314 | 23,595,401,038 | IssuesEvent | 2022-08-23 18:44:37 | sandialabs/Albany | https://api.github.com/repos/sandialabs/Albany | closed | Broken tests on Weaver | Testing | A bunch of the nightly tests on Weaver started failing:
https://sems-cdash-son.sandia.gov/cdash/test/2685897
```
[weaver3:23006:0:23006] Caught signal 11 (Segmentation fault: address not mapped to object at address 0x2000bf9cfa80)
[weaver3:23004:0:23004] Caught signal 11 (Segmentation fault: address not mapped to object at address 0x200093dcfc80)
[weaver3:23005:0:23005] Caught signal 11 (Segmentation fault: address not mapped to object at address 0x2000bfbcfc80)
==== backtrace (tid: 23006) ====
0 0x0000000000049bb4 uct_ep_am_short() /ascldap/users/sdhammo/git/ucx-github-repo/src/uct/api/uct.h:2009
1 0x0000000000049bb4 ucp_tag_send_inline() /ascldap/users/sdhammo/git/ucx-github-repo/src/ucp/tag/tag_send.c:155
2 0x0000000000049bb4 ucp_tag_send_nbr() /ascldap/users/sdhammo/git/ucx-github-repo/src/ucp/tag/tag_send.c:229
3 0x0000000000006808 mca_pml_ucx_send() ???:0
4 0x00000000000c81a8 MPI_Send() ???:0
5 0x00000000162f4978 Teuchos::(anonymous namespace)::sendImpl<double>() ???:0
6 0x00000000162d4218 Teuchos::send<int, double>() ???:0
7 0x0000000015b4799c Tpetra::Details::DistributorActor::doPosts<Kokkos::View<double const*, Kokkos::LayoutLeft, Kokkos::Device<Kokkos::Cuda, Kokkos::CudaSpace>, Kokkos::MemoryTraits<0u> >, Kokkos::View<double*, Kokkos::Device<Kokkos::Cuda, Kokkos::CudaSpace>, void, void> >() ???:0
8 0x0000000015b49a24 Tpetra::DistObject<double, int, long long, Kokkos::Compat::KokkosDeviceWrapperNode<Kokkos::Cuda, Kokkos::CudaUVMSpace> >::doPosts() ???:0
9 0x0000000015b4c0a4 Tpetra::DistObject<double, int, long long, Kokkos::Compat::KokkosDeviceWrapperNode<Kokkos::Cuda, Kokkos::CudaUVMSpace> >::beginTransfer() ???:0
10 0x0000000015b4f470 Tpetra::DistObject<double, int, long long, Kokkos::Compat::KokkosDeviceWrapperNode<Kokkos::Cuda, Kokkos::CudaUVMSpace> >::beginExport() ???:0
11 0x0000000015b4f6dc Tpetra::DistObject<double, int, long long, Kokkos::Compat::KokkosDeviceWrapperNode<Kokkos::Cuda, Kokkos::CudaUVMSpace> >::doExport() ???:0
12 0x0000000015820910 Tpetra::FEMultiVector<double, int, long long, Kokkos::Compat::KokkosDeviceWrapperNode<Kokkos::Cuda, Kokkos::CudaUVMSpace> >::doOwnedPlusSharedToOwned() ???:0
13 0x0000000015820d7c Tpetra::FEMultiVector<double, int, long long, Kokkos::Compat::KokkosDeviceWrapperNode<Kokkos::Cuda, Kokkos::CudaUVMSpace> >::endFill() ???:0
14 0x000000001582109c Tpetra::FEMultiVector<double, int, long long, Kokkos::Compat::KokkosDeviceWrapperNode<Kokkos::Cuda, Kokkos::CudaUVMSpace> >::endAssembly() ???:0
15 0x0000000010f2a4b8 Albany::ThyraCrsMatrixFactory::fillComplete() ???:0
16 0x0000000010e76214 Albany::STKDiscretization::computeGraphs() ???:0
17 0x0000000010e89994 Albany::STKDiscretization::updateMesh() ???:0
18 0x0000000010b04ef4 Albany::DiscretizationFactory::completeDiscSetup() ???:0
19 0x0000000010b05218 Albany::DiscretizationFactory::createDiscretization() ???:0
==== backtrace (tid: 23004) ====
0 0x0000000000049bb4 uct_ep_am_short() /ascldap/users/sdhammo/git/ucx-github-repo/src/uct/api/uct.h:2009
1 0x0000000000049bb4 ucp_tag_send_inline() /ascldap/users/sdhammo/git/ucx-github-repo/src/ucp/tag/tag_send.c:155
2 0x0000000000049bb4 ucp_tag_send_nbr() /ascldap/users/sdhammo/git/ucx-github-repo/src/ucp/tag/tag_send.c:229
3 0x0000000000006808 mca_pml_ucx_send() ???:0
4 0x00000000000c81a8 MPI_Send() ???:0
5 0x00000000162f4978 Teuchos::(anonymous namespace)::sendImpl<double>() ???:0
6 0x00000000162d4218 Teuchos::send<int, double>() ???:0
7 0x0000000015b4799c Tpetra::Details::DistributorActor::doPosts<Kokkos::View<double const*, Kokkos::LayoutLeft, Kokkos::Device<Kokkos::Cuda, Kokkos::CudaSpace>, Kokkos::MemoryTraits<0u> >, Kokkos::View<double*, Kokkos::Device<Kokkos::Cuda, Kokkos::CudaSpace>, void, void> >() ???:0
8 0x0000000015b49a24 Tpetra::DistObject<double, int, long long, Kokkos::Compat::KokkosDeviceWrapperNode<Kokkos::Cuda, Kokkos::CudaUVMSpace> >::doPosts() ???:0
9 0x0000000015b4c0a4 Tpetra::DistObject<double, int, long long, Kokkos::Compat::KokkosDeviceWrapperNode<Kokkos::Cuda, Kokkos::CudaUVMSpace> >::beginTransfer() ???:0
10 0x0000000015b4f470 Tpetra::DistObject<double, int, long long, Kokkos::Compat::KokkosDeviceWrapperNode<Kokkos::Cuda, Kokkos::CudaUVMSpace> >::beginExport() ???:0
11 0x0000000015b4f6dc Tpetra::DistObject<double, int, long long, Kokkos::Compat::KokkosDeviceWrapperNode<Kokkos::Cuda, Kokkos::CudaUVMSpace> >::doExport() ???:0
12 0x0000000015820910 Tpetra::FEMultiVector<double, int, long long, Kokkos::Compat::KokkosDeviceWrapperNode<Kokkos::Cuda, Kokkos::CudaUVMSpace> >::doOwnedPlusSharedToOwned() ???:0
13 0x0000000015820d7c Tpetra::FEMultiVector<double, int, long long, Kokkos::Compat::KokkosDeviceWrapperNode<Kokkos::Cuda, Kokkos::CudaUVMSpace> >::endFill() ???:0
14 0x000000001582109c Tpetra::FEMultiVector<double, int, long long, Kokkos::Compat::KokkosDeviceWrapperNode<Kokkos::Cuda, Kokkos::CudaUVMSpace> >::endAssembly() ???:0
15 0x0000000010f2a4b8 Albany::ThyraCrsMatrixFactory::fillComplete() ???:0
16 0x0000000010e76214 Albany::STKDiscretization::computeGraphs() ???:0
17 0x0000000010e89994 Albany::STKDiscretization::updateMesh() ???:0
18 0x0000000010b04ef4 Albany::DiscretizationFactory::completeDiscSetup() ???:0
19 0x0000000010b05218 Albany::DiscretizationFactory::createDiscretization() ???:0
20 0x00000000106db73c Albany::Application::createDiscretization() ???:0
21 0x00000000106eb7d0 Albany::Application::Application() ???:0
22 0x000000001032f534 Albany::SolverFactory::createApplication() ???:0
23 0x000000001014f2c0 main() ???:0
24 0x0000000000025100 generic_start_main.isra.0() libc-start.c:0
25 0x00000000000252f4 __libc_start_main() ???:0
20 0x00000000106db73c Albany::Application::createDiscretization() ???:0
21 0x00000000106eb7d0 Albany::Application::Application() ???:0
22 0x000000001032f534 Albany::SolverFactory::createApplication() ???:0
23 0x000000001014f2c0 main() ???:0
24 0x0000000000025100 generic_start_main.isra.0() libc-start.c:0
25 0x00000000000252f4 __libc_start_main() ???:0
=================================
=================================
```
@jewatkins , @mcarlson801 : could one of you please have a look? | 1.0 | Broken tests on Weaver - A bunch of the nightly tests on Weaver started failing:
https://sems-cdash-son.sandia.gov/cdash/test/2685897
```
[weaver3:23006:0:23006] Caught signal 11 (Segmentation fault: address not mapped to object at address 0x2000bf9cfa80)
[weaver3:23004:0:23004] Caught signal 11 (Segmentation fault: address not mapped to object at address 0x200093dcfc80)
[weaver3:23005:0:23005] Caught signal 11 (Segmentation fault: address not mapped to object at address 0x2000bfbcfc80)
==== backtrace (tid: 23006) ====
0 0x0000000000049bb4 uct_ep_am_short() /ascldap/users/sdhammo/git/ucx-github-repo/src/uct/api/uct.h:2009
1 0x0000000000049bb4 ucp_tag_send_inline() /ascldap/users/sdhammo/git/ucx-github-repo/src/ucp/tag/tag_send.c:155
2 0x0000000000049bb4 ucp_tag_send_nbr() /ascldap/users/sdhammo/git/ucx-github-repo/src/ucp/tag/tag_send.c:229
3 0x0000000000006808 mca_pml_ucx_send() ???:0
4 0x00000000000c81a8 MPI_Send() ???:0
5 0x00000000162f4978 Teuchos::(anonymous namespace)::sendImpl<double>() ???:0
6 0x00000000162d4218 Teuchos::send<int, double>() ???:0
7 0x0000000015b4799c Tpetra::Details::DistributorActor::doPosts<Kokkos::View<double const*, Kokkos::LayoutLeft, Kokkos::Device<Kokkos::Cuda, Kokkos::CudaSpace>, Kokkos::MemoryTraits<0u> >, Kokkos::View<double*, Kokkos::Device<Kokkos::Cuda, Kokkos::CudaSpace>, void, void> >() ???:0
8 0x0000000015b49a24 Tpetra::DistObject<double, int, long long, Kokkos::Compat::KokkosDeviceWrapperNode<Kokkos::Cuda, Kokkos::CudaUVMSpace> >::doPosts() ???:0
9 0x0000000015b4c0a4 Tpetra::DistObject<double, int, long long, Kokkos::Compat::KokkosDeviceWrapperNode<Kokkos::Cuda, Kokkos::CudaUVMSpace> >::beginTransfer() ???:0
10 0x0000000015b4f470 Tpetra::DistObject<double, int, long long, Kokkos::Compat::KokkosDeviceWrapperNode<Kokkos::Cuda, Kokkos::CudaUVMSpace> >::beginExport() ???:0
11 0x0000000015b4f6dc Tpetra::DistObject<double, int, long long, Kokkos::Compat::KokkosDeviceWrapperNode<Kokkos::Cuda, Kokkos::CudaUVMSpace> >::doExport() ???:0
12 0x0000000015820910 Tpetra::FEMultiVector<double, int, long long, Kokkos::Compat::KokkosDeviceWrapperNode<Kokkos::Cuda, Kokkos::CudaUVMSpace> >::doOwnedPlusSharedToOwned() ???:0
13 0x0000000015820d7c Tpetra::FEMultiVector<double, int, long long, Kokkos::Compat::KokkosDeviceWrapperNode<Kokkos::Cuda, Kokkos::CudaUVMSpace> >::endFill() ???:0
14 0x000000001582109c Tpetra::FEMultiVector<double, int, long long, Kokkos::Compat::KokkosDeviceWrapperNode<Kokkos::Cuda, Kokkos::CudaUVMSpace> >::endAssembly() ???:0
15 0x0000000010f2a4b8 Albany::ThyraCrsMatrixFactory::fillComplete() ???:0
16 0x0000000010e76214 Albany::STKDiscretization::computeGraphs() ???:0
17 0x0000000010e89994 Albany::STKDiscretization::updateMesh() ???:0
18 0x0000000010b04ef4 Albany::DiscretizationFactory::completeDiscSetup() ???:0
19 0x0000000010b05218 Albany::DiscretizationFactory::createDiscretization() ???:0
==== backtrace (tid: 23004) ====
0 0x0000000000049bb4 uct_ep_am_short() /ascldap/users/sdhammo/git/ucx-github-repo/src/uct/api/uct.h:2009
1 0x0000000000049bb4 ucp_tag_send_inline() /ascldap/users/sdhammo/git/ucx-github-repo/src/ucp/tag/tag_send.c:155
2 0x0000000000049bb4 ucp_tag_send_nbr() /ascldap/users/sdhammo/git/ucx-github-repo/src/ucp/tag/tag_send.c:229
3 0x0000000000006808 mca_pml_ucx_send() ???:0
4 0x00000000000c81a8 MPI_Send() ???:0
5 0x00000000162f4978 Teuchos::(anonymous namespace)::sendImpl<double>() ???:0
6 0x00000000162d4218 Teuchos::send<int, double>() ???:0
7 0x0000000015b4799c Tpetra::Details::DistributorActor::doPosts<Kokkos::View<double const*, Kokkos::LayoutLeft, Kokkos::Device<Kokkos::Cuda, Kokkos::CudaSpace>, Kokkos::MemoryTraits<0u> >, Kokkos::View<double*, Kokkos::Device<Kokkos::Cuda, Kokkos::CudaSpace>, void, void> >() ???:0
8 0x0000000015b49a24 Tpetra::DistObject<double, int, long long, Kokkos::Compat::KokkosDeviceWrapperNode<Kokkos::Cuda, Kokkos::CudaUVMSpace> >::doPosts() ???:0
9 0x0000000015b4c0a4 Tpetra::DistObject<double, int, long long, Kokkos::Compat::KokkosDeviceWrapperNode<Kokkos::Cuda, Kokkos::CudaUVMSpace> >::beginTransfer() ???:0
10 0x0000000015b4f470 Tpetra::DistObject<double, int, long long, Kokkos::Compat::KokkosDeviceWrapperNode<Kokkos::Cuda, Kokkos::CudaUVMSpace> >::beginExport() ???:0
11 0x0000000015b4f6dc Tpetra::DistObject<double, int, long long, Kokkos::Compat::KokkosDeviceWrapperNode<Kokkos::Cuda, Kokkos::CudaUVMSpace> >::doExport() ???:0
12 0x0000000015820910 Tpetra::FEMultiVector<double, int, long long, Kokkos::Compat::KokkosDeviceWrapperNode<Kokkos::Cuda, Kokkos::CudaUVMSpace> >::doOwnedPlusSharedToOwned() ???:0
13 0x0000000015820d7c Tpetra::FEMultiVector<double, int, long long, Kokkos::Compat::KokkosDeviceWrapperNode<Kokkos::Cuda, Kokkos::CudaUVMSpace> >::endFill() ???:0
14 0x000000001582109c Tpetra::FEMultiVector<double, int, long long, Kokkos::Compat::KokkosDeviceWrapperNode<Kokkos::Cuda, Kokkos::CudaUVMSpace> >::endAssembly() ???:0
15 0x0000000010f2a4b8 Albany::ThyraCrsMatrixFactory::fillComplete() ???:0
16 0x0000000010e76214 Albany::STKDiscretization::computeGraphs() ???:0
17 0x0000000010e89994 Albany::STKDiscretization::updateMesh() ???:0
18 0x0000000010b04ef4 Albany::DiscretizationFactory::completeDiscSetup() ???:0
19 0x0000000010b05218 Albany::DiscretizationFactory::createDiscretization() ???:0
20 0x00000000106db73c Albany::Application::createDiscretization() ???:0
21 0x00000000106eb7d0 Albany::Application::Application() ???:0
22 0x000000001032f534 Albany::SolverFactory::createApplication() ???:0
23 0x000000001014f2c0 main() ???:0
24 0x0000000000025100 generic_start_main.isra.0() libc-start.c:0
25 0x00000000000252f4 __libc_start_main() ???:0
20 0x00000000106db73c Albany::Application::createDiscretization() ???:0
21 0x00000000106eb7d0 Albany::Application::Application() ???:0
22 0x000000001032f534 Albany::SolverFactory::createApplication() ???:0
23 0x000000001014f2c0 main() ???:0
24 0x0000000000025100 generic_start_main.isra.0() libc-start.c:0
25 0x00000000000252f4 __libc_start_main() ???:0
=================================
=================================
```
@jewatkins , @mcarlson801 : could one of you please have a look? | non_priority | broken tests on weaver a bunch of the nightly tests on weaver started failing caught signal segmentation fault address not mapped to object at address caught signal segmentation fault address not mapped to object at address caught signal segmentation fault address not mapped to object at address backtrace tid uct ep am short ascldap users sdhammo git ucx github repo src uct api uct h ucp tag send inline ascldap users sdhammo git ucx github repo src ucp tag tag send c ucp tag send nbr ascldap users sdhammo git ucx github repo src ucp tag tag send c mca pml ucx send mpi send teuchos anonymous namespace sendimpl teuchos send tpetra details distributoractor doposts kokkos memorytraits kokkos view void void tpetra distobject doposts tpetra distobject begintransfer tpetra distobject beginexport tpetra distobject doexport tpetra femultivector doownedplussharedtoowned tpetra femultivector endfill tpetra femultivector endassembly albany thyracrsmatrixfactory fillcomplete albany stkdiscretization computegraphs albany stkdiscretization updatemesh albany discretizationfactory completediscsetup albany discretizationfactory creatediscretization backtrace tid uct ep am short ascldap users sdhammo git ucx github repo src uct api uct h ucp tag send inline ascldap users sdhammo git ucx github repo src ucp tag tag send c ucp tag send nbr ascldap users sdhammo git ucx github repo src ucp tag tag send c mca pml ucx send mpi send teuchos anonymous namespace sendimpl teuchos send tpetra details distributoractor doposts kokkos memorytraits kokkos view void void tpetra distobject doposts tpetra distobject begintransfer tpetra distobject beginexport tpetra distobject doexport tpetra femultivector doownedplussharedtoowned tpetra femultivector endfill tpetra femultivector endassembly albany thyracrsmatrixfactory fillcomplete albany stkdiscretization computegraphs albany stkdiscretization updatemesh albany discretizationfactory completediscsetup albany discretizationfactory creatediscretization albany application creatediscretization albany application application albany solverfactory createapplication main generic start main isra libc start c libc start main albany application creatediscretization albany application application albany solverfactory createapplication main generic start main isra libc start c libc start main jewatkins could one of you please have a look | 0 |
111,757 | 11,741,492,049 | IssuesEvent | 2020-03-11 21:52:57 | flutter/flutter | https://api.github.com/repos/flutter/flutter | closed | flutter create template creates configureFlutter engine in MainActivity - leading to plugins registered twice | d: wiki documentation engine framework p: framework plugin ▣ platform-android | Creating a new project with flutter create the main activity has code to configure the flutter engine.
e.g.
```java
public class MainActivity extends FlutterActivity {
@Override
public void configureFlutterEngine(@NonNull FlutterEngine flutterEngine) {
GeneratedPluginRegistrant.registerWith(flutterEngine);
}
}
```
This shouldn't be there. And was suggested as fix here: https://github.com/flutter/flutter/issues/47801#issuecomment-568975233
Further in the plugin migration documentation the main entry explains it to remove this code.
On the other hand there is a link on https://flutter.dev/docs/development/packages-and-plugins/plugin-api-migration to https://flutter.dev/go/android-project-migration (https://github.com/flutter/flutter/wiki/Upgrading-pre-1.12-Android-projects#full-flutter-app-migration) which shows it described in the opposite way (keeping the code above).
Flutter Version used: 1.12.13+hotfix.7
| 1.0 | flutter create template creates configureFlutter engine in MainActivity - leading to plugins registered twice - Creating a new project with flutter create the main activity has code to configure the flutter engine.
e.g.
```java
public class MainActivity extends FlutterActivity {
@Override
public void configureFlutterEngine(@NonNull FlutterEngine flutterEngine) {
GeneratedPluginRegistrant.registerWith(flutterEngine);
}
}
```
This shouldn't be there. And was suggested as fix here: https://github.com/flutter/flutter/issues/47801#issuecomment-568975233
Further in the plugin migration documentation the main entry explains it to remove this code.
On the other hand there is a link on https://flutter.dev/docs/development/packages-and-plugins/plugin-api-migration to https://flutter.dev/go/android-project-migration (https://github.com/flutter/flutter/wiki/Upgrading-pre-1.12-Android-projects#full-flutter-app-migration) which shows it described in the opposite way (keeping the code above).
Flutter Version used: 1.12.13+hotfix.7
| non_priority | flutter create template creates configureflutter engine in mainactivity leading to plugins registered twice creating a new project with flutter create the main activity has code to configure the flutter engine e g java public class mainactivity extends flutteractivity override public void configureflutterengine nonnull flutterengine flutterengine generatedpluginregistrant registerwith flutterengine this shouldn t be there and was suggested as fix here further in the plugin migration documentation the main entry explains it to remove this code on the other hand there is a link on to which shows it described in the opposite way keeping the code above flutter version used hotfix | 0 |
357,545 | 25,176,402,852 | IssuesEvent | 2022-11-11 09:38:57 | zacchaeuschok/pe | https://api.github.com/repos/zacchaeuschok/pe | opened | Formatting error | type.DocumentationBug severity.Low | Two colons in a single bullet point.
Usually best to break them up.
<!--session: 1668153124908-ed46472a-a5a9-4d62-acf6-e12362aef54f-->
<!--Version: Web v3.4.4--> | 1.0 | Formatting error - Two colons in a single bullet point.
Usually best to break them up.
<!--session: 1668153124908-ed46472a-a5a9-4d62-acf6-e12362aef54f-->
<!--Version: Web v3.4.4--> | non_priority | formatting error two colons in a single bullet point usually best to break them up | 0 |
160,710 | 20,117,438,121 | IssuesEvent | 2022-02-07 21:09:16 | Toposware/hash | https://api.github.com/repos/Toposware/hash | opened | Rescue-Prime impl is not constant-time | security | While the underlying arithmetic in Cheetah is made constant-time, the current implementation of Rescue-Prime for the two different sets of parameters is not constant-time. This can be an issue for applications hashing sensitive data, which is *currently* not the case. | True | Rescue-Prime impl is not constant-time - While the underlying arithmetic in Cheetah is made constant-time, the current implementation of Rescue-Prime for the two different sets of parameters is not constant-time. This can be an issue for applications hashing sensitive data, which is *currently* not the case. | non_priority | rescue prime impl is not constant time while the underlying arithmetic in cheetah is made constant time the current implementation of rescue prime for the two different sets of parameters is not constant time this can be an issue for applications hashing sensitive data which is currently not the case | 0 |
49,388 | 10,344,553,857 | IssuesEvent | 2019-09-04 11:31:11 | Genymobile/scrcpy | https://api.github.com/repos/Genymobile/scrcpy | closed | Special (Accent) characters missing | input events unicode | Hy rom1v!
First of all, you are a special man! I love your program :D
I followed the progression of the application for a long time, and I seen that you have started to add support for special characters too.
But there are still some missing.
Űű : WARN: Could not inject char u+170, u+171
Őő : WARN: Could not inject char u+150, u+151
Is it possible to add these too?
Thanks! | 1.0 | Special (Accent) characters missing - Hy rom1v!
First of all, you are a special man! I love your program :D
I followed the progression of the application for a long time, and I seen that you have started to add support for special characters too.
But there are still some missing.
Űű : WARN: Could not inject char u+170, u+171
Őő : WARN: Could not inject char u+150, u+151
Is it possible to add these too?
Thanks! | non_priority | special accent characters missing hy first of all you are a special man i love your program d i followed the progression of the application for a long time and i seen that you have started to add support for special characters too but there are still some missing űű warn could not inject char u u őő warn could not inject char u u is it possible to add these too thanks | 0 |
51,620 | 6,537,621,893 | IssuesEvent | 2017-08-31 23:40:14 | unfoldcollective/Apprentice-of-Okolicne | https://api.github.com/repos/unfoldcollective/Apprentice-of-Okolicne | closed | save & gallery & composition view: implement redesigned composition titles | design development p-must-have | we figured out that the current way of titling the compositions ({initial} from {town}) leads to problems in Slovak, because {town} should be inflected (e.g. Amsterdam -> Amsterdamu)
We are not going to solve that thorny i18n grammar issue automatically in the app, so here's a new idea:
- the user just signs with their name (no hometown), e.g. "Philo"
- the artwork is simply titled by the user's initial, e.g. "P"
this way we still stay close to the exhibition and catalogue design:
this will affect the following screens:
1. [ ] save: only ask for Name and Email Address (not hometown)
2. [ ] gallery: We need a redesign for the gallery thumbnails that incorporates the user's initial and it should signify that the thumbnail is clickable to open it in full screen (like the current zoom icon)
3. [ ] composition view: the title in top right simply becomes the initial, e.g. "P"
@matopysny can you please work on a redesign for '2. gallery' and link to the designs here on this Github issue?
| 1.0 | save & gallery & composition view: implement redesigned composition titles - we figured out that the current way of titling the compositions ({initial} from {town}) leads to problems in Slovak, because {town} should be inflected (e.g. Amsterdam -> Amsterdamu)
We are not going to solve that thorny i18n grammar issue automatically in the app, so here's a new idea:
- the user just signs with their name (no hometown), e.g. "Philo"
- the artwork is simply titled by the user's initial, e.g. "P"
this way we still stay close to the exhibition and catalogue design:
this will affect the following screens:
1. [ ] save: only ask for Name and Email Address (not hometown)
2. [ ] gallery: We need a redesign for the gallery thumbnails that incorporates the user's initial and it should signify that the thumbnail is clickable to open it in full screen (like the current zoom icon)
3. [ ] composition view: the title in top right simply becomes the initial, e.g. "P"
@matopysny can you please work on a redesign for '2. gallery' and link to the designs here on this Github issue?
| non_priority | save gallery composition view implement redesigned composition titles we figured out that the current way of titling the compositions initial from town leads to problems in slovak because town should be inflected e g amsterdam amsterdamu we are not going to solve that thorny grammar issue automatically in the app so here s a new idea the user just signs with their name no hometown e g philo the artwork is simply titled by the user s initial e g p this way we still stay close to the exhibition and catalogue design this will affect the following screens save only ask for name and email address not hometown gallery we need a redesign for the gallery thumbnails that incorporates the user s initial and it should signify that the thumbnail is clickable to open it in full screen like the current zoom icon composition view the title in top right simply becomes the initial e g p matopysny can you please work on a redesign for gallery and link to the designs here on this github issue | 0 |
183,300 | 31,276,614,946 | IssuesEvent | 2023-08-22 06:48:45 | flowforge/flowforge | https://api.github.com/repos/flowforge/flowforge | opened | Image Rebranding | task design artwork | ### Related Issue
CtrlX Project
### Description
Rebranding "FlowForge" -> "FlowFuse":
| 1.0 | Image Rebranding - ### Related Issue
CtrlX Project
### Description
Rebranding "FlowForge" -> "FlowFuse":
| non_priority | image rebranding related issue ctrlx project description rebranding flowforge flowfuse | 0 |
114,784 | 24,663,234,644 | IssuesEvent | 2022-10-18 08:23:34 | Regalis11/Barotrauma | https://api.github.com/repos/Regalis11/Barotrauma | closed | new ugcId logic in master 0.19 matches when both are none | Bug Code Modding Unstable | ### Disclaimers
- [X] I have searched the issue tracker to check if the issue has already been reported.
- [X] My issue happened while using mods.
### What happened?
Originally the content path logic matches `%ModDir:xxx%` first with workshop id (ignores if not present, `workshopid==0`), then package name then alt-names.
Now that `steamworkshopid` logic is changed to use the new generic `ugcid`, but `Option<T>` of `none` will equal `Option<T>` of `none`. This means all local mod packages will match each other (and also match vanilla).
The code affected (`Barotrauma/Barotrauma/BarotraumaShared/SharedSource/ContentManagement/ContentPath.cs`, lines`56-65`):
```
foreach (Identifier otherModName in otherMods)
{
Option<ContentPackageId> ugcId = ContentPackageId.Parse(otherModName.Value);
ContentPackage? otherMod =
allPackages.FirstOrDefault(p => ugcId == p.UgcId)
?? allPackages.FirstOrDefault(p => p.Name == otherModName)
?? allPackages.FirstOrDefault(p => p.NameMatches(otherModName))
?? throw new MissingContentPackageException(ContentPackage, otherModName.Value);
cachedValue = cachedValue.Replace(string.Format(OtherModDirFmt, otherModName.Value), Path.GetDirectoryName(otherMod.Path));
}
```
Suggested change:
```
allPackages.FirstOrDefault(p => ugcId.IsSome() && ugcId == p.UgcId)
```
### Reproduction steps
Have one local mod that references its contents with "%ModDir%" or "%ModDir:xxx%", and the resource will not load.
### Bug prevalence
Happens every time I play
### Version
0.19.10.0
### -
_No response_
### Which operating system did you encounter this bug on?
Windows
### Relevant error messages and crash reports
```shell
I think things are clear enough.
```
| 1.0 | new ugcId logic in master 0.19 matches when both are none - ### Disclaimers
- [X] I have searched the issue tracker to check if the issue has already been reported.
- [X] My issue happened while using mods.
### What happened?
Originally the content path logic matches `%ModDir:xxx%` first with workshop id (ignores if not present, `workshopid==0`), then package name then alt-names.
Now that `steamworkshopid` logic is changed to use the new generic `ugcid`, but `Option<T>` of `none` will equal `Option<T>` of `none`. This means all local mod packages will match each other (and also match vanilla).
The code affected (`Barotrauma/Barotrauma/BarotraumaShared/SharedSource/ContentManagement/ContentPath.cs`, lines`56-65`):
```
foreach (Identifier otherModName in otherMods)
{
Option<ContentPackageId> ugcId = ContentPackageId.Parse(otherModName.Value);
ContentPackage? otherMod =
allPackages.FirstOrDefault(p => ugcId == p.UgcId)
?? allPackages.FirstOrDefault(p => p.Name == otherModName)
?? allPackages.FirstOrDefault(p => p.NameMatches(otherModName))
?? throw new MissingContentPackageException(ContentPackage, otherModName.Value);
cachedValue = cachedValue.Replace(string.Format(OtherModDirFmt, otherModName.Value), Path.GetDirectoryName(otherMod.Path));
}
```
Suggested change:
```
allPackages.FirstOrDefault(p => ugcId.IsSome() && ugcId == p.UgcId)
```
### Reproduction steps
Have one local mod that references its contents with "%ModDir%" or "%ModDir:xxx%", and the resource will not load.
### Bug prevalence
Happens every time I play
### Version
0.19.10.0
### -
_No response_
### Which operating system did you encounter this bug on?
Windows
### Relevant error messages and crash reports
```shell
I think things are clear enough.
```
| non_priority | new ugcid logic in master matches when both are none disclaimers i have searched the issue tracker to check if the issue has already been reported my issue happened while using mods what happened originally the content path logic matches moddir xxx first with workshop id ignores if not present workshopid then package name then alt names now that steamworkshopid logic is changed to use the new generic ugcid but option of none will equal option of none this means all local mod packages will match each other and also match vanilla the code affected barotrauma barotrauma barotraumashared sharedsource contentmanagement contentpath cs lines foreach identifier othermodname in othermods option ugcid contentpackageid parse othermodname value contentpackage othermod allpackages firstordefault p ugcid p ugcid allpackages firstordefault p p name othermodname allpackages firstordefault p p namematches othermodname throw new missingcontentpackageexception contentpackage othermodname value cachedvalue cachedvalue replace string format othermoddirfmt othermodname value path getdirectoryname othermod path suggested change allpackages firstordefault p ugcid issome ugcid p ugcid reproduction steps have one local mod that references its contents with moddir or moddir xxx and the resource will not load bug prevalence happens every time i play version no response which operating system did you encounter this bug on windows relevant error messages and crash reports shell i think things are clear enough | 0 |
200,140 | 15,790,701,118 | IssuesEvent | 2021-04-02 02:16:08 | open-contracting/standard | https://api.github.com/repos/open-contracting/standard | opened | Check whether some csv-table-no-translate should be csv-table | Focus - Documentation | Only codelists are translated by Transifex. The rest should likely be csv-table. Right now, only two tables use `csv-table`. To find the other tables, regex-search for `:file: (?!\.\./\.\./build/current_lang/.*csv)`. | 1.0 | Check whether some csv-table-no-translate should be csv-table - Only codelists are translated by Transifex. The rest should likely be csv-table. Right now, only two tables use `csv-table`. To find the other tables, regex-search for `:file: (?!\.\./\.\./build/current_lang/.*csv)`. | non_priority | check whether some csv table no translate should be csv table only codelists are translated by transifex the rest should likely be csv table right now only two tables use csv table to find the other tables regex search for file build current lang csv | 0 |
18,323 | 10,927,663,856 | IssuesEvent | 2019-11-22 17:11:08 | mozilla/fxa | https://api.github.com/repos/mozilla/fxa | closed | Load test / tune | fxa-email-service | We haven't done anything to analyse (or optimise) performance in this repo. If train 125 looks stable there should be some time to spend on this. | 1.0 | Load test / tune - We haven't done anything to analyse (or optimise) performance in this repo. If train 125 looks stable there should be some time to spend on this. | non_priority | load test tune we haven t done anything to analyse or optimise performance in this repo if train looks stable there should be some time to spend on this | 0 |
13,887 | 16,654,864,392 | IssuesEvent | 2021-06-05 10:36:08 | GoogleCloudPlatform/fda-mystudies | https://api.github.com/repos/GoogleCloudPlatform/fda-mystudies | closed | [PM] Responsive issue > UI is broken for toaster messages | Bug P2 Participant manager Process: Fixed Process: Tested QA Process: Tested dev | UI is broken for all the toaster messages
[Note: Issue should be fixed for all the toaster messages]
| 3.0 | [PM] Responsive issue > UI is broken for toaster messages - UI is broken for all the toaster messages
[Note: Issue should be fixed for all the toaster messages]
| non_priority | responsive issue ui is broken for toaster messages ui is broken for all the toaster messages | 0 |
239,709 | 18,281,469,469 | IssuesEvent | 2021-10-05 04:21:53 | GowthamGoush/Amazing_Sites | https://api.github.com/repos/GowthamGoush/Amazing_Sites | closed | Submarine Cable System | documentation hacktoberfest | This site gives us an interactive and regularly updated map of world's major submarine cable systems and landing stations. | 1.0 | Submarine Cable System - This site gives us an interactive and regularly updated map of world's major submarine cable systems and landing stations. | non_priority | submarine cable system this site gives us an interactive and regularly updated map of world s major submarine cable systems and landing stations | 0 |
222,688 | 17,468,225,664 | IssuesEvent | 2021-08-06 20:25:14 | sylabs/singularity | https://api.github.com/repos/sylabs/singularity | closed | e2e remote test failing after #217 | bug ci:e2e testing | **Version of Singularity**
master
**Describe the bug**
#217 changed usage strings on the remote sub-commands, without me realizing they were checked in the e2e tests. Since no e2e test code or go.mod modifications were made, the e2e tests were not triggered in CI. They are now failing in PRs in which they are triggered.
| 1.0 | e2e remote test failing after #217 - **Version of Singularity**
master
**Describe the bug**
#217 changed usage strings on the remote sub-commands, without me realizing they were checked in the e2e tests. Since no e2e test code or go.mod modifications were made, the e2e tests were not triggered in CI. They are now failing in PRs in which they are triggered.
| non_priority | remote test failing after version of singularity master describe the bug changed usage strings on the remote sub commands without me realizing they were checked in the tests since no test code or go mod modifications were made the tests were not triggered in ci they are now failing in prs in which they are triggered | 0 |
67,953 | 14,894,262,300 | IssuesEvent | 2021-01-21 07:12:57 | murthy1979/hackazon | https://api.github.com/repos/murthy1979/hackazon | opened | CVE-2016-4055 (Medium) detected in moment-2.8.3.min.js | security vulnerability | ## CVE-2016-4055 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>moment-2.8.3.min.js</b></p></summary>
<p>Parse, validate, manipulate, and display dates</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/moment.js/2.8.3/moment.min.js">https://cdnjs.cloudflare.com/ajax/libs/moment.js/2.8.3/moment.min.js</a></p>
<p>Path to vulnerable library: hackazon/web/js/moment.min.js</p>
<p>
Dependency Hierarchy:
- :x: **moment-2.8.3.min.js** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/murthy1979/hackazon/commit/7a5c1fb6205b5dacb816770c95cda9299805eb02">7a5c1fb6205b5dacb816770c95cda9299805eb02</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
The duration function in the moment package before 2.11.2 for Node.js allows remote attackers to cause a denial of service (CPU consumption) via a long string, aka a "regular expression Denial of Service (ReDoS)."
<p>Publish Date: 2017-01-23
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2016-4055>CVE-2016-4055</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>6.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-4055">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-4055</a></p>
<p>Release Date: 2017-01-23</p>
<p>Fix Resolution: 2.11.2</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | CVE-2016-4055 (Medium) detected in moment-2.8.3.min.js - ## CVE-2016-4055 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>moment-2.8.3.min.js</b></p></summary>
<p>Parse, validate, manipulate, and display dates</p>
<p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/moment.js/2.8.3/moment.min.js">https://cdnjs.cloudflare.com/ajax/libs/moment.js/2.8.3/moment.min.js</a></p>
<p>Path to vulnerable library: hackazon/web/js/moment.min.js</p>
<p>
Dependency Hierarchy:
- :x: **moment-2.8.3.min.js** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/murthy1979/hackazon/commit/7a5c1fb6205b5dacb816770c95cda9299805eb02">7a5c1fb6205b5dacb816770c95cda9299805eb02</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
The duration function in the moment package before 2.11.2 for Node.js allows remote attackers to cause a denial of service (CPU consumption) via a long string, aka a "regular expression Denial of Service (ReDoS)."
<p>Publish Date: 2017-01-23
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2016-4055>CVE-2016-4055</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>6.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-4055">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-4055</a></p>
<p>Release Date: 2017-01-23</p>
<p>Fix Resolution: 2.11.2</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_priority | cve medium detected in moment min js cve medium severity vulnerability vulnerable library moment min js parse validate manipulate and display dates library home page a href path to vulnerable library hackazon web js moment min js dependency hierarchy x moment min js vulnerable library found in head commit a href found in base branch master vulnerability details the duration function in the moment package before for node js allows remote attackers to cause a denial of service cpu consumption via a long string aka a regular expression denial of service redos publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required low user interaction none scope unchanged impact metrics confidentiality impact none integrity impact none availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution step up your open source security game with whitesource | 0 |
52,757 | 10,925,130,032 | IssuesEvent | 2019-11-22 11:45:25 | eclipse-theia/theia | https://api.github.com/repos/eclipse-theia/theia | closed | [vscode] webview does not have proper styles | bug plug-in system vscode webviews | ### Description
Theia
VSCode
### Reproduction Steps
Download vscode plugin REST Client(humao.rest-client)
create a new http file
Send Request
look response
The response is there, but text is not highlighted properly, i.e black text on black background is not visible.
**OS and Theia version:**
**Diagnostics:**
cc @olexii4 @evidolob
| 1.0 | [vscode] webview does not have proper styles - ### Description
Theia
VSCode
### Reproduction Steps
Download vscode plugin REST Client(humao.rest-client)
create a new http file
Send Request
look response
The response is there, but text is not highlighted properly, i.e black text on black background is not visible.
**OS and Theia version:**
**Diagnostics:**
cc @olexii4 @evidolob
| non_priority | webview does not have proper styles description theia vscode reproduction steps download vscode plugin rest client humao rest client create a new http file send request look response the response is there but text is not highlighted properly i e black text on black background is not visible os and theia version diagnostics cc evidolob | 0 |
87,631 | 10,934,131,801 | IssuesEvent | 2019-11-24 09:07:14 | GospelAid/badiup | https://api.github.com/repos/GospelAid/badiup | opened | Selected indication needed in gallery page | bug P0 design | Need the design for showing selected images in the gallery page. The current design shows all images unselected. Please update the design with some of the images selected.
| 1.0 | Selected indication needed in gallery page - Need the design for showing selected images in the gallery page. The current design shows all images unselected. Please update the design with some of the images selected.
| non_priority | selected indication needed in gallery page need the design for showing selected images in the gallery page the current design shows all images unselected please update the design with some of the images selected | 0 |
48,996 | 20,381,982,323 | IssuesEvent | 2022-02-21 23:32:57 | hashicorp/terraform-provider-aws | https://api.github.com/repos/hashicorp/terraform-provider-aws | closed | MalformedXML: The XML you provided was not well-formed or did not validate against our published schema (aws_s3_bucket_lifecycle_configuration) | service/s3 needs-triage | I get this error when running TF 1.1.6 and these versions
Installing hashicorp/random v3.1.0...
Installing hashicorp/external v2.2.0...
Installing hashicorp/aws v4.2.0...
Error: error creating S3 Lifecycle Configuration for bucket (test-master-deadletters): MalformedXML: The XML you provided was not well-formed or did not validate against our published schema
12:26:30 status code: 400, request id: ZHJK7AH24EXY85MC, host id: tj2hcv/f4GIhLmgx415nVsG0SDbbgCsCQJdAg4HqcU7wP8hDaDyzUAC2V0h/SWTNqlQjfZLeMqM=
12:26:30
12:26:30 with module.s3.aws_s3_bucket_lifecycle_configuration.test_deadletters,
12:26:30 on ../../modules/s3/bucket_deadletters.tf line 6, in resource "aws_s3_bucket_lifecycle_configuration" "test_deadletters":
12:26:30 6: resource "aws_s3_bucket_lifecycle_configuration" "test_deadletters" {
This is my code
`resource "aws_s3_bucket" "test_deadletters" {
bucket = "test-${var.env}-deadletters"
tags = var.tags
}
resource "aws_s3_bucket_lifecycle_configuration" "test_deadletters" {
bucket = aws_s3_bucket.test_deadletters.bucket
rule {
id = "exp"
expiration {
days = 90
}
filter {
and {
prefix = "queue="
}
}
status = "Enabled"
}
}
resource "aws_s3_bucket_public_access_block" "test_deadletters" {
bucket = aws_s3_bucket.test_deadletters.bucket
restrict_public_buckets = true
ignore_public_acls = true
block_public_acls = true
block_public_policy = true
}
resource "aws_s3_bucket_policy" "test_deadletters" {
count = var.aws_account != var.master_account_id ? 1 : 0
bucket = aws_s3_bucket.test_deadletters.bucket
policy = jsonencode({
"Version" : "2012-10-17",
"Statement" : [
{
"Effect" : "Allow",
"Principal" : {
"AWS" : "arn:aws:iam::${var.master_account_id}:root"
},
"Action" : [
"s3:GetObject",
"s3:ListBucket"
],
"Resource" : [
"arn:aws:s3:::${aws_s3_bucket.test_deadletters.bucket}",
"arn:aws:s3:::${aws_s3_bucket.test_deadletters.bucket}/*"
]
}
]
})
}
resource "aws_s3_bucket_inventory" "test_deadletters" {
bucket = aws_s3_bucket.test_deadletters.bucket
name = "athena"
included_object_versions = "Current"
schedule {
frequency = "Daily"
}
destination {
bucket {
format = "Parquet"
bucket_arn = aws_s3_bucket.test_events.arn
prefix = "inventory"
}
}
optional_fields = [
"Size",
"LastModifiedDate",
"StorageClass",
"ETag",
"IsMultipartUploaded",
"ReplicationStatus",
"EncryptionStatus",
"ObjectLockRetainUntilDate",
"ObjectLockMode",
"ObjectLockLegalHoldStatus",
"IntelligentTieringAccessTier"
]
}
resource "aws_s3_object" "test_deadletters_cloudwatch_alarm_marker" {
bucket = aws_s3_bucket.test_deadletters.bucket
key = "cloudwatch-alarm-marker"
content = ""
}` | 1.0 | MalformedXML: The XML you provided was not well-formed or did not validate against our published schema (aws_s3_bucket_lifecycle_configuration) - I get this error when running TF 1.1.6 and these versions
Installing hashicorp/random v3.1.0...
Installing hashicorp/external v2.2.0...
Installing hashicorp/aws v4.2.0...
Error: error creating S3 Lifecycle Configuration for bucket (test-master-deadletters): MalformedXML: The XML you provided was not well-formed or did not validate against our published schema
12:26:30 status code: 400, request id: ZHJK7AH24EXY85MC, host id: tj2hcv/f4GIhLmgx415nVsG0SDbbgCsCQJdAg4HqcU7wP8hDaDyzUAC2V0h/SWTNqlQjfZLeMqM=
12:26:30
12:26:30 with module.s3.aws_s3_bucket_lifecycle_configuration.test_deadletters,
12:26:30 on ../../modules/s3/bucket_deadletters.tf line 6, in resource "aws_s3_bucket_lifecycle_configuration" "test_deadletters":
12:26:30 6: resource "aws_s3_bucket_lifecycle_configuration" "test_deadletters" {
This is my code
`resource "aws_s3_bucket" "test_deadletters" {
bucket = "test-${var.env}-deadletters"
tags = var.tags
}
resource "aws_s3_bucket_lifecycle_configuration" "test_deadletters" {
bucket = aws_s3_bucket.test_deadletters.bucket
rule {
id = "exp"
expiration {
days = 90
}
filter {
and {
prefix = "queue="
}
}
status = "Enabled"
}
}
resource "aws_s3_bucket_public_access_block" "test_deadletters" {
bucket = aws_s3_bucket.test_deadletters.bucket
restrict_public_buckets = true
ignore_public_acls = true
block_public_acls = true
block_public_policy = true
}
resource "aws_s3_bucket_policy" "test_deadletters" {
count = var.aws_account != var.master_account_id ? 1 : 0
bucket = aws_s3_bucket.test_deadletters.bucket
policy = jsonencode({
"Version" : "2012-10-17",
"Statement" : [
{
"Effect" : "Allow",
"Principal" : {
"AWS" : "arn:aws:iam::${var.master_account_id}:root"
},
"Action" : [
"s3:GetObject",
"s3:ListBucket"
],
"Resource" : [
"arn:aws:s3:::${aws_s3_bucket.test_deadletters.bucket}",
"arn:aws:s3:::${aws_s3_bucket.test_deadletters.bucket}/*"
]
}
]
})
}
resource "aws_s3_bucket_inventory" "test_deadletters" {
bucket = aws_s3_bucket.test_deadletters.bucket
name = "athena"
included_object_versions = "Current"
schedule {
frequency = "Daily"
}
destination {
bucket {
format = "Parquet"
bucket_arn = aws_s3_bucket.test_events.arn
prefix = "inventory"
}
}
optional_fields = [
"Size",
"LastModifiedDate",
"StorageClass",
"ETag",
"IsMultipartUploaded",
"ReplicationStatus",
"EncryptionStatus",
"ObjectLockRetainUntilDate",
"ObjectLockMode",
"ObjectLockLegalHoldStatus",
"IntelligentTieringAccessTier"
]
}
resource "aws_s3_object" "test_deadletters_cloudwatch_alarm_marker" {
bucket = aws_s3_bucket.test_deadletters.bucket
key = "cloudwatch-alarm-marker"
content = ""
}` | non_priority | malformedxml the xml you provided was not well formed or did not validate against our published schema aws bucket lifecycle configuration i get this error when running tf and these versions installing hashicorp random installing hashicorp external installing hashicorp aws error error creating lifecycle configuration for bucket test master deadletters malformedxml the xml you provided was not well formed or did not validate against our published schema status code request id host id swtnqlqjfzlemqm with module aws bucket lifecycle configuration test deadletters on modules bucket deadletters tf line in resource aws bucket lifecycle configuration test deadletters resource aws bucket lifecycle configuration test deadletters this is my code resource aws bucket test deadletters bucket test var env deadletters tags var tags resource aws bucket lifecycle configuration test deadletters bucket aws bucket test deadletters bucket rule id exp expiration days filter and prefix queue status enabled resource aws bucket public access block test deadletters bucket aws bucket test deadletters bucket restrict public buckets true ignore public acls true block public acls true block public policy true resource aws bucket policy test deadletters count var aws account var master account id bucket aws bucket test deadletters bucket policy jsonencode version statement effect allow principal aws arn aws iam var master account id root action getobject listbucket resource arn aws aws bucket test deadletters bucket arn aws aws bucket test deadletters bucket resource aws bucket inventory test deadletters bucket aws bucket test deadletters bucket name athena included object versions current schedule frequency daily destination bucket format parquet bucket arn aws bucket test events arn prefix inventory optional fields size lastmodifieddate storageclass etag ismultipartuploaded replicationstatus encryptionstatus objectlockretainuntildate objectlockmode objectlocklegalholdstatus intelligenttieringaccesstier resource aws object test deadletters cloudwatch alarm marker bucket aws bucket test deadletters bucket key cloudwatch alarm marker content | 0 |
418,374 | 28,114,578,408 | IssuesEvent | 2023-03-31 09:45:45 | Kalipo-BV/kalipo-core | https://api.github.com/repos/Kalipo-BV/kalipo-core | opened | As a developer I would like to have STAR documentations of every review, retrospective and planning so that we can find ways to improve as a team. | Documentation User Story | ## User story specification
As a developer I would like to have STAR documentations of every review, retrospective and planning so that we can find ways to improve as a team.
## Acceptance criteria
### Functionals
- [ ] STAR review sprint 3
- [ ] STAR retro sprint 3
- [ ] STAR planning sprint 3
- [ ] STAR review sprint 4
- [ ] STAR retro sprint 4
- [ ] STAR planning sprint 4
**Pre conditions**
- ...
**Process**
- De gebruiker opent ...
- Het systeem geeft ...
- De gebruiker vult ...
**Result**
- ...
**Wireframe:**
...
### Non-functionals
- Veiligheid
- Snelheid
- Beschikbaarheid
- Betrouwbaarheid
**ISO 25010**
[https://docs.google.com/spreadsheets/d/1ge06Lyd5Bhn-QTgtjGqhO41yXi2Z6NaX/edit#gid=1777548652](url)
## Constraints
- C: Commerce, communicatie, cultuur
- O: Organisatie
- P: Members
- A: Organisatie
- F: Financiën
- **_I: Informatie/ Software_**
Blockchain
SDK
- J: Juridische
- **_T: Technologie_**
LiskSDK
Vue
- H: Huisvesting
## DoD
Een user story voldoet aan de DoD wanneer deze voldoet aan:
- De stijl van Kalipo
- Gereviewd door de product owner en voldoet aan acceptatiecriteria
- Er is een spellingscontrole gedaan
- Er zijn peer-reviews geweest
- Getest
- Gedocumenteerd
## Deliverables
- [ ]
| 1.0 | As a developer I would like to have STAR documentations of every review, retrospective and planning so that we can find ways to improve as a team. - ## User story specification
As a developer I would like to have STAR documentations of every review, retrospective and planning so that we can find ways to improve as a team.
## Acceptance criteria
### Functionals
- [ ] STAR review sprint 3
- [ ] STAR retro sprint 3
- [ ] STAR planning sprint 3
- [ ] STAR review sprint 4
- [ ] STAR retro sprint 4
- [ ] STAR planning sprint 4
**Pre conditions**
- ...
**Process**
- De gebruiker opent ...
- Het systeem geeft ...
- De gebruiker vult ...
**Result**
- ...
**Wireframe:**
...
### Non-functionals
- Veiligheid
- Snelheid
- Beschikbaarheid
- Betrouwbaarheid
**ISO 25010**
[https://docs.google.com/spreadsheets/d/1ge06Lyd5Bhn-QTgtjGqhO41yXi2Z6NaX/edit#gid=1777548652](url)
## Constraints
- C: Commerce, communicatie, cultuur
- O: Organisatie
- P: Members
- A: Organisatie
- F: Financiën
- **_I: Informatie/ Software_**
Blockchain
SDK
- J: Juridische
- **_T: Technologie_**
LiskSDK
Vue
- H: Huisvesting
## DoD
Een user story voldoet aan de DoD wanneer deze voldoet aan:
- De stijl van Kalipo
- Gereviewd door de product owner en voldoet aan acceptatiecriteria
- Er is een spellingscontrole gedaan
- Er zijn peer-reviews geweest
- Getest
- Gedocumenteerd
## Deliverables
- [ ]
| non_priority | as a developer i would like to have star documentations of every review retrospective and planning so that we can find ways to improve as a team user story specification as a developer i would like to have star documentations of every review retrospective and planning so that we can find ways to improve as a team acceptance criteria functionals star review sprint star retro sprint star planning sprint star review sprint star retro sprint star planning sprint pre conditions process de gebruiker opent het systeem geeft de gebruiker vult result wireframe non functionals veiligheid snelheid beschikbaarheid betrouwbaarheid iso url constraints c commerce communicatie cultuur o organisatie p members a organisatie f financiën i informatie software blockchain sdk j juridische t technologie lisksdk vue h huisvesting dod een user story voldoet aan de dod wanneer deze voldoet aan de stijl van kalipo gereviewd door de product owner en voldoet aan acceptatiecriteria er is een spellingscontrole gedaan er zijn peer reviews geweest getest gedocumenteerd deliverables | 0 |
171,107 | 20,920,870,737 | IssuesEvent | 2022-03-24 17:16:05 | webmachinelearning/webnn | https://api.github.com/repos/webmachinelearning/webnn | closed | op metadata that helps avoid implementation mistakes | security-tracker | Some way to help implementors validate that data is being passed correctly between nodes in the computation graph, has the expected sizes, etc.
Perhaps a little language which describes the required sizes/shapes and can be used to create checks that can be enforced as a graph is constructed, and as a graph is executed.
e.g. fields for ops which indicate:
Does it change input/output tensor contents?
Does it change input/output tensor sizes?
Can the input tensor be the output tensor?
Shape of the input, shape of the output?
Constraints on other input parameters that can be turned into automatic checks.
| True | op metadata that helps avoid implementation mistakes - Some way to help implementors validate that data is being passed correctly between nodes in the computation graph, has the expected sizes, etc.
Perhaps a little language which describes the required sizes/shapes and can be used to create checks that can be enforced as a graph is constructed, and as a graph is executed.
e.g. fields for ops which indicate:
Does it change input/output tensor contents?
Does it change input/output tensor sizes?
Can the input tensor be the output tensor?
Shape of the input, shape of the output?
Constraints on other input parameters that can be turned into automatic checks.
| non_priority | op metadata that helps avoid implementation mistakes some way to help implementors validate that data is being passed correctly between nodes in the computation graph has the expected sizes etc perhaps a little language which describes the required sizes shapes and can be used to create checks that can be enforced as a graph is constructed and as a graph is executed e g fields for ops which indicate does it change input output tensor contents does it change input output tensor sizes can the input tensor be the output tensor shape of the input shape of the output constraints on other input parameters that can be turned into automatic checks | 0 |
323,771 | 27,750,892,989 | IssuesEvent | 2023-03-15 20:38:42 | golang/go | https://api.github.com/repos/golang/go | opened | cmd/go: `go clean --fuzzcache` failure in TestScript/test_fuzz_limit_dup_entry | Testing NeedsFix GoCommand | ```
#!watchflakes
post <- pkg == "cmd/go" && `go clean --fuzzcache: exit status`
```
Pulled out from https://github.com/golang/go/issues/55311#issuecomment-1469087280.
I think the fix is to set `env GOCACHE=$WORK/cache` or similar explicitly in script tests that need a clean fuzzcache. | 1.0 | cmd/go: `go clean --fuzzcache` failure in TestScript/test_fuzz_limit_dup_entry - ```
#!watchflakes
post <- pkg == "cmd/go" && `go clean --fuzzcache: exit status`
```
Pulled out from https://github.com/golang/go/issues/55311#issuecomment-1469087280.
I think the fix is to set `env GOCACHE=$WORK/cache` or similar explicitly in script tests that need a clean fuzzcache. | non_priority | cmd go go clean fuzzcache failure in testscript test fuzz limit dup entry watchflakes post pkg cmd go go clean fuzzcache exit status pulled out from i think the fix is to set env gocache work cache or similar explicitly in script tests that need a clean fuzzcache | 0 |
112,496 | 11,770,415,015 | IssuesEvent | 2020-03-15 19:08:09 | contributing-to-kubernetes/cool-kubernetes | https://api.github.com/repos/contributing-to-kubernetes/cool-kubernetes | closed | Document PR #85968 (Fix bug in apiserver service cidr split) | documentation | **PR:**
https://github.com/kubernetes/kubernetes/pull/85968
**ISSUE:**
bug
**SIG LABELS:**
sig/api-machinery
sig/network | 1.0 | Document PR #85968 (Fix bug in apiserver service cidr split) - **PR:**
https://github.com/kubernetes/kubernetes/pull/85968
**ISSUE:**
bug
**SIG LABELS:**
sig/api-machinery
sig/network | non_priority | document pr fix bug in apiserver service cidr split pr issue bug sig labels sig api machinery sig network | 0 |
204,342 | 15,897,254,386 | IssuesEvent | 2021-04-11 20:21:30 | Retro-Cartoons/Tom | https://api.github.com/repos/Retro-Cartoons/Tom | closed | documents-for-functions-and-properties | documentation enhancement | - Add document with 'option + command + slash' to essential and complex properties and functions
- No need for insignificant function and properties | 1.0 | documents-for-functions-and-properties - - Add document with 'option + command + slash' to essential and complex properties and functions
- No need for insignificant function and properties | non_priority | documents for functions and properties add document with option command slash to essential and complex properties and functions no need for insignificant function and properties | 0 |
237,587 | 19,660,122,566 | IssuesEvent | 2022-01-10 16:13:11 | aaronangxz/Carouhell | https://api.github.com/repos/aaronangxz/Carouhell | reopened | [FEATURE#82] DeleteListings - Move deleted listings to archive table | enhancement merged to test | Instead of just deleting listings, move it to archive_tab to preserve data
- [x] Create listings_archive_tab in `test`
- [x] Create listings_archive_tab in `live`
- [x] Add INSERT query in `DeleteListing` | 1.0 | [FEATURE#82] DeleteListings - Move deleted listings to archive table - Instead of just deleting listings, move it to archive_tab to preserve data
- [x] Create listings_archive_tab in `test`
- [x] Create listings_archive_tab in `live`
- [x] Add INSERT query in `DeleteListing` | non_priority | deletelistings move deleted listings to archive table instead of just deleting listings move it to archive tab to preserve data create listings archive tab in test create listings archive tab in live add insert query in deletelisting | 0 |
14,160 | 8,491,761,790 | IssuesEvent | 2018-10-27 16:14:19 | chreden/trview | https://api.github.com/repos/chreden/trview | opened | Minimap is always being re-rendered | bug performance | Turns out it was always redrawing - wasn't resetting the force redraw flag.
| True | Minimap is always being re-rendered - Turns out it was always redrawing - wasn't resetting the force redraw flag.
| non_priority | minimap is always being re rendered turns out it was always redrawing wasn t resetting the force redraw flag | 0 |
251,758 | 27,208,395,258 | IssuesEvent | 2023-02-20 14:45:02 | scm-automation-project/vsix-nuget-simple-project | https://api.github.com/repos/scm-automation-project/vsix-nuget-simple-project | opened | microsoft.chakracore.1.8.0.nupkg: 162 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>microsoft.chakracore.1.8.0.nupkg</b></p></summary>
<p>ChakraCore is the core part of the Chakra Javascript engine that powers Microsoft Edge.</p>
<p>Library home page: <a href="https://api.nuget.org/packages/microsoft.chakracore.1.8.0.nupkg">https://api.nuget.org/packages/microsoft.chakracore.1.8.0.nupkg</a></p>
<p>Path to dependency file: /Nuget_VSIX_Project/Nuget_VSIX_Project.csproj</p>
<p>Path to vulnerable library: /home/wss-scanner/.nuget/packages/microsoft.chakracore/1.8.0/microsoft.chakracore.1.8.0.nupkg</p>
<p>
<p>Found in HEAD commit: <a href="https://github.com/scm-automation-project/vsix-nuget-simple-project/commit/026ce0ebdfc0d6ab0f3595e83fecf4f2458b0d83">026ce0ebdfc0d6ab0f3595e83fecf4f2458b0d83</a></p></details>
## Vulnerabilities
| CVE | Severity | <img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS | Dependency | Type | Fixed in (microsoft.chakracore.1.8.0.nupkg version) | Remediation Available |
| ------------- | ------------- | ----- | ----- | ----- | ------------- | --- |
| [CVE-2018-8500](https://www.mend.io/vulnerability-database/CVE-2018-8500) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 9.8 | microsoft.chakracore.1.8.0.nupkg | Direct | v1.11.2 | ✅ |
| [CVE-2020-1073](https://www.mend.io/vulnerability-database/CVE-2020-1073) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 8.1 | microsoft.chakracore.1.8.0.nupkg | Direct | v1.11.20 | ✅ |
| [CVE-2020-17048](https://www.mend.io/vulnerability-database/CVE-2020-17048) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 8.1 | microsoft.chakracore.1.8.0.nupkg | Direct | v1.11.23 | ✅ |
| [CVE-2019-0649](https://www.mend.io/vulnerability-database/CVE-2019-0649) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 8.1 | microsoft.chakracore.1.8.0.nupkg | Direct | v1.11.6 | ✅ |
| [CVE-2019-1003](https://www.mend.io/vulnerability-database/CVE-2019-1003) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | Microsoft.ChakraCore - 1.11.10 | ✅ |
| [CVE-2019-1366](https://www.mend.io/vulnerability-database/CVE-2019-1366) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | Microsoft.ChakraCore - 1.11.14 | ✅ |
| [CVE-2020-0813](https://www.mend.io/vulnerability-database/CVE-2020-0813) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | Microsoft.ChakraCore - 1.11.17 | ✅ |
| [CVE-2018-8390](https://www.mend.io/vulnerability-database/CVE-2018-8390) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | v1.10.2 | ✅ |
| [CVE-2018-8380](https://www.mend.io/vulnerability-database/CVE-2018-8380) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | v1.10.2 | ✅ |
| [CVE-2018-8381](https://www.mend.io/vulnerability-database/CVE-2018-8381) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | v1.10.2 | ✅ |
| [CVE-2020-0823](https://www.mend.io/vulnerability-database/CVE-2020-0823) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | Microsoft.ChakraCore - 1.11.17 | ✅ |
| [CVE-2018-8384](https://www.mend.io/vulnerability-database/CVE-2018-8384) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | v1.10.2 | ✅ |
| [CVE-2018-8385](https://www.mend.io/vulnerability-database/CVE-2018-8385) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | v1.10.2 | ✅ |
| [CVE-2018-8266](https://www.mend.io/vulnerability-database/CVE-2018-8266) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | v1.10.2 | ✅ |
| [CVE-2018-8541](https://www.mend.io/vulnerability-database/CVE-2018-8541) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | v1.11.3 | ✅ |
| [CVE-2018-8542](https://www.mend.io/vulnerability-database/CVE-2018-8542) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | v1.11.3 | ✅ |
| [CVE-2018-8543](https://www.mend.io/vulnerability-database/CVE-2018-8543) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | v1.11.3 | ✅ |
| [CVE-2019-1092](https://www.mend.io/vulnerability-database/CVE-2019-1092) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | Microsoft.ChakraCore - 1.11.11 | ✅ |
| [CVE-2019-1131](https://www.mend.io/vulnerability-database/CVE-2019-1131) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | Microsoft.ChakraCore - 1.11.12 | ✅ |
| [CVE-2020-0828](https://www.mend.io/vulnerability-database/CVE-2020-0828) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | Microsoft.ChakraCore - 1.11.17 | ✅ |
| [CVE-2020-0829](https://www.mend.io/vulnerability-database/CVE-2020-0829) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | Microsoft.ChakraCore - 1.11.17 | ✅ |
| [CVE-2020-0825](https://www.mend.io/vulnerability-database/CVE-2020-0825) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | Microsoft.ChakraCore - 1.11.17 | ✅ |
| [CVE-2020-0826](https://www.mend.io/vulnerability-database/CVE-2020-0826) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | Microsoft.ChakraCore - 1.11.17 | ✅ |
| [CVE-2018-8280](https://www.mend.io/vulnerability-database/CVE-2018-8280) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | v1.10.1 | ✅ |
| [CVE-2018-8391](https://www.mend.io/vulnerability-database/CVE-2018-8391) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | v1.11.1 | ✅ |
| [CVE-2020-0831](https://www.mend.io/vulnerability-database/CVE-2020-0831) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | Microsoft.ChakraCore - 1.11.17 | ✅ |
| [CVE-2020-0711](https://www.mend.io/vulnerability-database/CVE-2020-0711) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | Microsoft.ChakraCore - 1.11.16 | ✅ |
| [CVE-2019-0568](https://www.mend.io/vulnerability-database/CVE-2019-0568) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | v1.11.5 | ✅ |
| [CVE-2020-0712](https://www.mend.io/vulnerability-database/CVE-2020-0712) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | Microsoft.ChakraCore - 1.11.16 | ✅ |
| [CVE-2019-0567](https://www.mend.io/vulnerability-database/CVE-2019-0567) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | v1.11.5 | ✅ |
| [CVE-2019-1138](https://www.mend.io/vulnerability-database/CVE-2019-1138) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | Microsoft.ChakraCore - 1.11.13 | ✅ |
| [CVE-2020-0713](https://www.mend.io/vulnerability-database/CVE-2020-0713) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | Microsoft.ChakraCore - 1.11.16 | ✅ |
| [CVE-2018-0837](https://www.mend.io/vulnerability-database/CVE-2018-0837) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | Microsoft.TypeScript.Compiler - 2.8.4,2.7.2,2.2.0;Microsoft.TypeScript.MSBuild - 2.8.4;Microsoft.Azure.StreamAnalytics.CICD - 1.2.0;BaristaLabs.BaristaCore.ChakraCore.win-arm - 1.8.1;BaristaLabs.BaristaCore.ChakraCore.win-x64 - 1.8.1;BaristaLabs.BaristaCore.ChakraCore.win-x86 - 1.8.1;Microsoft.ChakraCore.vc140 - 1.8.1;Microsoft.ChakraCore - 1.8.1 | ✅ |
| [CVE-2018-8275](https://www.mend.io/vulnerability-database/CVE-2018-8275) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | v1.10.1 | ✅ |
| [CVE-2018-0838](https://www.mend.io/vulnerability-database/CVE-2018-0838) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | Microsoft.TypeScript.Compiler - 2.8.4,2.7.2,2.2.0;Microsoft.TypeScript.MSBuild - 2.8.4;Microsoft.Azure.StreamAnalytics.CICD - 1.2.0;BaristaLabs.BaristaCore.ChakraCore.win-arm - 1.8.1;BaristaLabs.BaristaCore.ChakraCore.win-x64 - 1.8.1;BaristaLabs.BaristaCore.ChakraCore.win-x86 - 1.8.1;Microsoft.ChakraCore.vc140 - 1.8.1,1.5.3;Microsoft.ChakraCore - 1.8.1 | ✅ |
| [CVE-2018-8551](https://www.mend.io/vulnerability-database/CVE-2018-8551) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | v1.11.3 | ✅ |
| [CVE-2019-0605](https://www.mend.io/vulnerability-database/CVE-2019-0605) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | v1.11.6 | ✅ |
| [CVE-2019-0607](https://www.mend.io/vulnerability-database/CVE-2019-0607) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | v1.11.6 | ✅ |
| [CVE-2018-8279](https://www.mend.io/vulnerability-database/CVE-2018-8279) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | v1.10.1 | ✅ |
| [CVE-2018-8555](https://www.mend.io/vulnerability-database/CVE-2018-8555) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | v1.11.3 | ✅ |
| [CVE-2019-0609](https://www.mend.io/vulnerability-database/CVE-2019-0609) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | v1.11.7 | ✅ |
| [CVE-2018-0835](https://www.mend.io/vulnerability-database/CVE-2018-0835) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | Microsoft.ChakraCore - 1.8.1;Microsoft.TypeScript.Compiler - 2.7.2,2.8.4,2.2.0;Microsoft.TypeScript.MSBuild - 2.8.4;Microsoft.Azure.StreamAnalytics.CICD - 1.2.0;BaristaLabs.BaristaCore.ChakraCore.win-arm - 1.8.1;BaristaLabs.BaristaCore.ChakraCore.win-x64 - 1.8.1;BaristaLabs.BaristaCore.ChakraCore.win-x86 - 1.8.1;Microsoft.ChakraCore.vc140 - 1.8.1,1.5.0 | ✅ |
| [CVE-2018-8556](https://www.mend.io/vulnerability-database/CVE-2018-8556) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | v1.11.3 | ✅ |
| [CVE-2018-8557](https://www.mend.io/vulnerability-database/CVE-2018-8557) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | v1.11.3 | ✅ |
| [CVE-2019-1140](https://www.mend.io/vulnerability-database/CVE-2019-1140) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | 1.11.12 | ✅ |
| [CVE-2019-1141](https://www.mend.io/vulnerability-database/CVE-2019-1141) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | 1.11.12 | ✅ |
| [CVE-2019-1300](https://www.mend.io/vulnerability-database/CVE-2019-1300) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | Microsoft.ChakraCore - 1.11.13 | ✅ |
| [CVE-2019-1024](https://www.mend.io/vulnerability-database/CVE-2019-1024) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | Microsoft.ChakraCore - 1.11.10 | ✅ |
| [CVE-2019-0610](https://www.mend.io/vulnerability-database/CVE-2019-0610) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | v1.11.6 | ✅ |
| [CVE-2019-0611](https://www.mend.io/vulnerability-database/CVE-2019-0611) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | v1.11.7 | ✅ |
| [CVE-2019-1308](https://www.mend.io/vulnerability-database/CVE-2019-1308) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | Microsoft.ChakraCore - 1.11.14 | ✅ |
| [CVE-2018-8243](https://www.mend.io/vulnerability-database/CVE-2018-8243) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | v1.8.5 | ✅ |
| [CVE-2019-1427](https://www.mend.io/vulnerability-database/CVE-2019-1427) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | Microsoft.ChakraCore - 1.11.15 | ✅ |
| [CVE-2019-1307](https://www.mend.io/vulnerability-database/CVE-2019-1307) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | Microsoft.ChakraCore - 1.11.14 | ✅ |
| [CVE-2019-1428](https://www.mend.io/vulnerability-database/CVE-2019-1428) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | Microsoft.ChakraCore - 1.11.15 | ✅ |
| [CVE-2019-0739](https://www.mend.io/vulnerability-database/CVE-2019-0739) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | Microsoft.ChakraCore - 1.11.8 | ✅ |
| [CVE-2018-8367](https://www.mend.io/vulnerability-database/CVE-2018-8367) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | v1.11.1 | ✅ |
| [CVE-2020-17054](https://www.mend.io/vulnerability-database/CVE-2020-17054) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | v1.11.23 | ✅ |
| [CVE-2019-0861](https://www.mend.io/vulnerability-database/CVE-2019-0861) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | Microsoft.ChakraCore - 1.11.8 | ✅ |
| [CVE-2020-0848](https://www.mend.io/vulnerability-database/CVE-2020-0848) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | Microsoft.ChakraCore - 1.11.17 | ✅ |
| [CVE-2019-0860](https://www.mend.io/vulnerability-database/CVE-2019-0860) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | Microsoft.ChakraCore - 1.11.8 | ✅ |
| [CVE-2018-8372](https://www.mend.io/vulnerability-database/CVE-2018-8372) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | v1.10.2 | ✅ |
| [CVE-2018-0937](https://www.mend.io/vulnerability-database/CVE-2018-0937) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | Microsoft.TypeScript.Compiler - 2.8.4,2.7.2,2.2.0;Microsoft.TypeScript.MSBuild - 2.8.4;Microsoft.Azure.StreamAnalytics.CICD - 1.2.0;BaristaLabs.BaristaCore.ChakraCore.win-arm - 1.8.5;BaristaLabs.BaristaCore.ChakraCore.win-x64 - 1.8.5;BaristaLabs.BaristaCore.ChakraCore.win-x86 - 1.8.5;Microsoft.ChakraCore.vc140 - 1.8.2;Microsoft.ChakraCore - 1.8.2 | ✅ |
| [CVE-2019-0989](https://www.mend.io/vulnerability-database/CVE-2019-0989) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | Microsoft.ChakraCore - 1.11.10 | ✅ |
| [CVE-2018-0933](https://www.mend.io/vulnerability-database/CVE-2018-0933) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | Microsoft.Azure.StreamAnalytics.CICD - 1.2.0;BaristaLabs.BaristaCore.ChakraCore.win-arm - 1.8.1;BaristaLabs.BaristaCore.ChakraCore.win-x64 - 1.8.1;BaristaLabs.BaristaCore.ChakraCore.win-x86 - 1.8.1;Microsoft.ChakraCore.vc140 - 1.8.0;Microsoft.ChakraCore - 1.8.2 | ✅ |
| [CVE-2018-8629](https://www.mend.io/vulnerability-database/CVE-2018-8629) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | v1.11.4 | ✅ |
| [CVE-2019-0591](https://www.mend.io/vulnerability-database/CVE-2019-0591) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | v1.11.6 | ✅ |
| [CVE-2019-0590](https://www.mend.io/vulnerability-database/CVE-2019-0590) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | v1.11.6 | ✅ |
| [CVE-2019-0593](https://www.mend.io/vulnerability-database/CVE-2019-0593) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | v1.11.6 | ✅ |
| [CVE-2019-0592](https://www.mend.io/vulnerability-database/CVE-2019-0592) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | v1.11.7 | ✅ |
| [CVE-2019-0991](https://www.mend.io/vulnerability-database/CVE-2019-0991) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | Microsoft.ChakraCore - 1.11.10 | ✅ |
| [CVE-2019-0993](https://www.mend.io/vulnerability-database/CVE-2019-0993) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | Microsoft.ChakraCore - 1.11.10 | ✅ |
| [CVE-2019-0992](https://www.mend.io/vulnerability-database/CVE-2019-0992) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | Microsoft.ChakraCore - 1.11.10 | ✅ |
| [CVE-2019-0911](https://www.mend.io/vulnerability-database/CVE-2019-0911) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | Microsoft.ChakraCore - 1.11.9 | ✅ |
| [CVE-2018-8583](https://www.mend.io/vulnerability-database/CVE-2018-8583) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | v1.11.4 | ✅ |
| [CVE-2020-1037](https://www.mend.io/vulnerability-database/CVE-2020-1037) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | Microsoft.ChakraCore - 1.11.19 | ✅ |
| [CVE-2019-0913](https://www.mend.io/vulnerability-database/CVE-2019-0913) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | Microsoft.ChakraCore - 1.11.9 | ✅ |
| [CVE-2019-0912](https://www.mend.io/vulnerability-database/CVE-2019-0912) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | Microsoft.ChakraCore - 1.11.9 | ✅ |
| [CVE-2018-8465](https://www.mend.io/vulnerability-database/CVE-2018-8465) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | v1.11.1 | ✅ |
| [CVE-2019-0915](https://www.mend.io/vulnerability-database/CVE-2019-0915) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | Microsoft.ChakraCore - 1.11.9 | ✅ |
| [CVE-2018-0866](https://www.mend.io/vulnerability-database/CVE-2018-0866) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | Microsoft.ChakraCore - 1.8.1;Microsoft.TypeScript.Compiler - 2.7.2,2.8.4,2.2.0;Microsoft.TypeScript.MSBuild - 2.8.4;Microsoft.Azure.StreamAnalytics.CICD - 1.2.0;BaristaLabs.BaristaCore.ChakraCore.win-arm - 1.8.1;BaristaLabs.BaristaCore.ChakraCore.win-x64 - 1.8.1;BaristaLabs.BaristaCore.ChakraCore.win-x86 - 1.8.1;Microsoft.ChakraCore.vc140 - 1.8.1 | ✅ |
| [CVE-2018-8466](https://www.mend.io/vulnerability-database/CVE-2018-8466) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | v1.11.1 | ✅ |
| [CVE-2019-0639](https://www.mend.io/vulnerability-database/CVE-2019-0639) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | v1.11.7 | ✅ |
| [CVE-2019-0914](https://www.mend.io/vulnerability-database/CVE-2019-0914) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | Microsoft.ChakraCore - 1.11.9 | ✅ |
| [CVE-2018-8467](https://www.mend.io/vulnerability-database/CVE-2018-8467) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | v1.11.1 | ✅ |
| [CVE-2018-8588](https://www.mend.io/vulnerability-database/CVE-2018-8588) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | v1.11.3 | ✅ |
| [CVE-2019-0917](https://www.mend.io/vulnerability-database/CVE-2019-0917) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | Microsoft.ChakraCore - 1.11.9 | ✅ |
| [CVE-2019-0916](https://www.mend.io/vulnerability-database/CVE-2019-0916) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | Microsoft.ChakraCore - 1.11.9 | ✅ |
| [CVE-2018-8227](https://www.mend.io/vulnerability-database/CVE-2018-8227) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | v1.8.5 | ✅ |
| [CVE-2018-8503](https://www.mend.io/vulnerability-database/CVE-2018-8503) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | v1.11.2 | ✅ |
| [CVE-2018-8624](https://www.mend.io/vulnerability-database/CVE-2018-8624) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | v1.11.4 | ✅ |
| [CVE-2018-8229](https://www.mend.io/vulnerability-database/CVE-2018-8229) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | v1.8.5 | ✅ |
| [CVE-2018-8505](https://www.mend.io/vulnerability-database/CVE-2018-8505) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | v1.11.2 | ✅ |
| [CVE-2019-1051](https://www.mend.io/vulnerability-database/CVE-2019-1051) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | Microsoft.ChakraCore - 1.11.10 | ✅ |
| [CVE-2019-1052](https://www.mend.io/vulnerability-database/CVE-2019-1052) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | Microsoft.ChakraCore - 1.11.10 | ✅ |
| [CVE-2019-1298](https://www.mend.io/vulnerability-database/CVE-2019-1298) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | Microsoft.ChakraCore - 1.11.13 | ✅ |
| [CVE-2019-0640](https://www.mend.io/vulnerability-database/CVE-2019-0640) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | v1.11.6 | ✅ |
| [CVE-2019-0642](https://www.mend.io/vulnerability-database/CVE-2019-0642) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | Microsoft.ChakraCore - 1.11.6 | ✅ |
| [CVE-2019-1217](https://www.mend.io/vulnerability-database/CVE-2019-1217) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | 1.11.13 | ✅ |
| [CVE-2019-1335](https://www.mend.io/vulnerability-database/CVE-2019-1335) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | Microsoft.ChakraCore - 1.11.14 | ✅ |
| [CVE-2019-0644](https://www.mend.io/vulnerability-database/CVE-2019-0644) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | v1.11.6 | ✅ |
| [CVE-2019-0922](https://www.mend.io/vulnerability-database/CVE-2019-0922) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | Microsoft.ChakraCore - 1.11.9 | ✅ |
| [CVE-2018-8473](https://www.mend.io/vulnerability-database/CVE-2018-8473) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | v1.11.2 | ✅ |
| [CVE-2019-0924](https://www.mend.io/vulnerability-database/CVE-2019-0924) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | Microsoft.ChakraCore - 1.11.9 | ✅ |
| [CVE-2018-8354](https://www.mend.io/vulnerability-database/CVE-2018-8354) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | v1.11.1 | ✅ |
| [CVE-2019-0769](https://www.mend.io/vulnerability-database/CVE-2019-0769) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | Microsoft.ChakraCore - 1.11.7 | ✅ |
| [CVE-2019-0923](https://www.mend.io/vulnerability-database/CVE-2019-0923) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | Microsoft.ChakraCore - 1.11.9 | ✅ |
| [CVE-2018-8355](https://www.mend.io/vulnerability-database/CVE-2018-8355) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | v1.10.2 | ✅ |
| [CVE-2018-8510](https://www.mend.io/vulnerability-database/CVE-2018-8510) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | v1.11.2 | ✅ |
| [CVE-2019-0925](https://www.mend.io/vulnerability-database/CVE-2019-0925) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | Microsoft.ChakraCore - 1.11.9 | ✅ |
| [CVE-2018-8236](https://www.mend.io/vulnerability-database/CVE-2018-8236) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | v1.8.5 | ✅ |
| [CVE-2018-8511](https://www.mend.io/vulnerability-database/CVE-2018-8511) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | v1.11.2 | ✅ |
| [CVE-2019-0806](https://www.mend.io/vulnerability-database/CVE-2019-0806) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | Microsoft.ChakraCore - 1.11.8 | ✅ |
| [CVE-2019-0927](https://www.mend.io/vulnerability-database/CVE-2019-0927) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | Microsoft.ChakraCore - 1.11.9 | ✅ |
| [CVE-2018-8359](https://www.mend.io/vulnerability-database/CVE-2018-8359) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | v1.10.2 | ✅ |
| [CVE-2018-8513](https://www.mend.io/vulnerability-database/CVE-2018-8513) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | v1.11.2 | ✅ |
| [CVE-2018-0874](https://www.mend.io/vulnerability-database/CVE-2018-0874) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | Microsoft.TypeScript.MSBuild - 2.2.1;BaristaLabs.BaristaCore.ChakraCore.win-arm - 1.8.1;BaristaLabs.BaristaCore.ChakraCore.win-x64 - 1.8.5;BaristaLabs.BaristaCore.ChakraCore.win-x86 - 1.8.5;Microsoft.ChakraCore.vc140 - 1.8.2;Microsoft.ChakraCore - 1.8.2 | ✅ |
| [CVE-2019-1062](https://www.mend.io/vulnerability-database/CVE-2019-1062) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | Microsoft.ChakraCore - 1.11.11 | ✅ |
| [CVE-2019-0771](https://www.mend.io/vulnerability-database/CVE-2019-0771) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | 1.11.7 | ✅ |
| [CVE-2019-1103](https://www.mend.io/vulnerability-database/CVE-2019-1103) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | Microsoft.ChakraCore - 1.11.11 | ✅ |
| [CVE-2018-8290](https://www.mend.io/vulnerability-database/CVE-2018-8290) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | v1.10.1 | ✅ |
| [CVE-2019-0652](https://www.mend.io/vulnerability-database/CVE-2019-0652) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | Microsoft.ChakraCore - 1.11.6 | ✅ |
| [CVE-2019-0773](https://www.mend.io/vulnerability-database/CVE-2019-0773) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | 1.11.7 | ✅ |
| [CVE-2018-8291](https://www.mend.io/vulnerability-database/CVE-2018-8291) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | v1.10.1 | ✅ |
| [CVE-2019-0651](https://www.mend.io/vulnerability-database/CVE-2019-0651) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | v1.11.6 | ✅ |
| [CVE-2019-1106](https://www.mend.io/vulnerability-database/CVE-2019-1106) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | v1.11.11 | ✅ |
| [CVE-2019-1107](https://www.mend.io/vulnerability-database/CVE-2019-1107) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | v1.11.11 | ✅ |
| [CVE-2018-8283](https://www.mend.io/vulnerability-database/CVE-2018-8283) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | v1.10.1 | ✅ |
| [CVE-2020-0767](https://www.mend.io/vulnerability-database/CVE-2020-0767) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | Microsoft.ChakraCore - 1.11.16 | ✅ |
| [CVE-2019-0655](https://www.mend.io/vulnerability-database/CVE-2019-0655) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | Microsoft.ChakraCore - 1.11.6 | ✅ |
| [CVE-2020-0768](https://www.mend.io/vulnerability-database/CVE-2020-0768) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | Microsoft.ChakraCore - 1.11.17 | ✅ |
| [CVE-2020-1219](https://www.mend.io/vulnerability-database/CVE-2020-1219) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | v1.11.20 | ✅ |
| [CVE-2019-0812](https://www.mend.io/vulnerability-database/CVE-2019-0812) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | Microsoft.ChakraCore - 1.11.8 | ✅ |
| [CVE-2019-0933](https://www.mend.io/vulnerability-database/CVE-2019-0933) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | Microsoft.ChakraCore - 1.11.9 | ✅ |
| [CVE-2018-8286](https://www.mend.io/vulnerability-database/CVE-2018-8286) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | v1.10.1 | ✅ |
| [CVE-2018-8287](https://www.mend.io/vulnerability-database/CVE-2018-8287) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | v1.10.1 | ✅ |
| [CVE-2019-0539](https://www.mend.io/vulnerability-database/CVE-2019-0539) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | v1.11.5 | ✅ |
| [CVE-2018-8288](https://www.mend.io/vulnerability-database/CVE-2018-8288) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | v1.10.1 | ✅ |
| [CVE-2019-0937](https://www.mend.io/vulnerability-database/CVE-2019-0937) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | Microsoft.ChakraCore - 1.11.9 | ✅ |
| [CVE-2018-0840](https://www.mend.io/vulnerability-database/CVE-2018-0840) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | Microsoft.ChakraCore - 1.8.1;Microsoft.TypeScript.Compiler - 2.7.2,2.8.4,2.2.0;Microsoft.TypeScript.MSBuild - 2.8.4;BaristaLabs.BaristaCore.ChakraCore.win-arm - 1.8.1;BaristaLabs.BaristaCore.ChakraCore.win-x86 - 1.8.1;Microsoft.ChakraCore.vc140 - 1.8.1 | ✅ |
| [CVE-2020-17131](https://www.mend.io/vulnerability-database/CVE-2020-17131) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | Microsoft.ChakraCore - 1.11.24 | ✅ |
| [CVE-2018-8617](https://www.mend.io/vulnerability-database/CVE-2018-8617) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | v1.11.4 | ✅ |
| [CVE-2018-8618](https://www.mend.io/vulnerability-database/CVE-2018-8618) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | v1.11.4 | ✅ |
| [CVE-2019-1197](https://www.mend.io/vulnerability-database/CVE-2019-1197) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | Microsoft.ChakraCore - 1.11.12 | ✅ |
| [CVE-2019-1195](https://www.mend.io/vulnerability-database/CVE-2019-1195) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | Microsoft.ChakraCore - 1.11.12 | ✅ |
| [CVE-2019-1196](https://www.mend.io/vulnerability-database/CVE-2019-1196) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | Microsoft.ChakraCore - 1.11.12 | ✅ |
| [CVE-2018-8294](https://www.mend.io/vulnerability-database/CVE-2018-8294) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | v1.10.1 | ✅ |
| [CVE-2020-0811](https://www.mend.io/vulnerability-database/CVE-2020-0811) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | Microsoft.ChakraCore - 1.11.17 | ✅ |
| [CVE-2019-1237](https://www.mend.io/vulnerability-database/CVE-2019-1237) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | Microsoft.ChakraCore - 1.11.13 | ✅ |
| [CVE-2020-0812](https://www.mend.io/vulnerability-database/CVE-2020-0812) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | Microsoft.ChakraCore - 1.11.17 | ✅ |
| [CVE-2018-8298](https://www.mend.io/vulnerability-database/CVE-2018-8298) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | v1.10.1 | ✅ |
| [CVE-2020-1065](https://www.mend.io/vulnerability-database/CVE-2020-1065) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | Microsoft.ChakraCore - 1.11.19 | ✅ |
| [CVE-2018-8456](https://www.mend.io/vulnerability-database/CVE-2018-8456) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | v1.11.1 | ✅ |
| [CVE-2019-0829](https://www.mend.io/vulnerability-database/CVE-2019-0829) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | Microsoft.ChakraCore - 1.11.8 | ✅ |
| [CVE-2018-8459](https://www.mend.io/vulnerability-database/CVE-2018-8459) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | v1.11.1 | ✅ |
| [CVE-2018-8276](https://www.mend.io/vulnerability-database/CVE-2018-8276) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 6.5 | microsoft.chakracore.1.8.0.nupkg | Direct | v1.10.1 | ✅ |
| [CVE-2019-1023](https://www.mend.io/vulnerability-database/CVE-2019-1023) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 6.5 | microsoft.chakracore.1.8.0.nupkg | Direct | Microsoft.ChakraCore - 1.11.10 | ✅ |
| [CVE-2019-0746](https://www.mend.io/vulnerability-database/CVE-2019-0746) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 6.5 | microsoft.chakracore.1.8.0.nupkg | Direct | Microsoft.ChakraCore - 1.11.7 | ✅ |
| [CVE-2019-0990](https://www.mend.io/vulnerability-database/CVE-2019-0990) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 6.5 | microsoft.chakracore.1.8.0.nupkg | Direct | Microsoft.ChakraCore - 1.11.10 | ✅ |
| [CVE-2019-0648](https://www.mend.io/vulnerability-database/CVE-2019-0648) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 4.3 | microsoft.chakracore.1.8.0.nupkg | Direct | v1.11.6 | ✅ |
| [CVE-2018-8452](https://www.mend.io/vulnerability-database/CVE-2018-8452) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 4.3 | microsoft.chakracore.1.8.0.nupkg | Direct | v1.11.1 | ✅ |
| [CVE-2018-8315](https://www.mend.io/vulnerability-database/CVE-2018-8315) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 4.2 | microsoft.chakracore.1.8.0.nupkg | Direct | v1.11.2 | ✅ |
## Details
> Partial details (8 vulnerabilities) are displayed below due to a content size limitation in GitHub. To view information on the remaining vulnerabilities, navigate to the Mend Application.<br>
<details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2018-8500</summary>
### Vulnerable Library - <b>microsoft.chakracore.1.8.0.nupkg</b></p>
<p>ChakraCore is the core part of the Chakra Javascript engine that powers Microsoft Edge.</p>
<p>Library home page: <a href="https://api.nuget.org/packages/microsoft.chakracore.1.8.0.nupkg">https://api.nuget.org/packages/microsoft.chakracore.1.8.0.nupkg</a></p>
<p>Path to dependency file: /Nuget_VSIX_Project/Nuget_VSIX_Project.csproj</p>
<p>Path to vulnerable library: /home/wss-scanner/.nuget/packages/microsoft.chakracore/1.8.0/microsoft.chakracore.1.8.0.nupkg</p>
<p>
Dependency Hierarchy:
- :x: **microsoft.chakracore.1.8.0.nupkg** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/scm-automation-project/vsix-nuget-simple-project/commit/026ce0ebdfc0d6ab0f3595e83fecf4f2458b0d83">026ce0ebdfc0d6ab0f3595e83fecf4f2458b0d83</a></p>
</p>
<p></p>
### Vulnerability Details
<p>
A remote code execution vulnerability exists in the way that the ChakraCore scripting engine handles objects in memory, aka "Scripting Engine Memory Corruption Vulnerability." This affects ChakraCore.
<p>Publish Date: 2018-10-10
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2018-8500>CVE-2018-8500</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>Release Date: 2018-10-10</p>
<p>Fix Resolution: v1.11.2</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation is available for this issue
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2020-1073</summary>
### Vulnerable Library - <b>microsoft.chakracore.1.8.0.nupkg</b></p>
<p>ChakraCore is the core part of the Chakra Javascript engine that powers Microsoft Edge.</p>
<p>Library home page: <a href="https://api.nuget.org/packages/microsoft.chakracore.1.8.0.nupkg">https://api.nuget.org/packages/microsoft.chakracore.1.8.0.nupkg</a></p>
<p>Path to dependency file: /Nuget_VSIX_Project/Nuget_VSIX_Project.csproj</p>
<p>Path to vulnerable library: /home/wss-scanner/.nuget/packages/microsoft.chakracore/1.8.0/microsoft.chakracore.1.8.0.nupkg</p>
<p>
Dependency Hierarchy:
- :x: **microsoft.chakracore.1.8.0.nupkg** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/scm-automation-project/vsix-nuget-simple-project/commit/026ce0ebdfc0d6ab0f3595e83fecf4f2458b0d83">026ce0ebdfc0d6ab0f3595e83fecf4f2458b0d83</a></p>
</p>
<p></p>
### Vulnerability Details
<p>
A remote code execution vulnerability exists in the way that the ChakraCore scripting engine handles objects in memory, aka 'Scripting Engine Memory Corruption Vulnerability'.
<p>Publish Date: 2020-06-09
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2020-1073>CVE-2020-1073</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>8.1</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Release Date: 2020-06-09</p>
<p>Fix Resolution: v1.11.20</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation is available for this issue
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2020-17048</summary>
### Vulnerable Library - <b>microsoft.chakracore.1.8.0.nupkg</b></p>
<p>ChakraCore is the core part of the Chakra Javascript engine that powers Microsoft Edge.</p>
<p>Library home page: <a href="https://api.nuget.org/packages/microsoft.chakracore.1.8.0.nupkg">https://api.nuget.org/packages/microsoft.chakracore.1.8.0.nupkg</a></p>
<p>Path to dependency file: /Nuget_VSIX_Project/Nuget_VSIX_Project.csproj</p>
<p>Path to vulnerable library: /home/wss-scanner/.nuget/packages/microsoft.chakracore/1.8.0/microsoft.chakracore.1.8.0.nupkg</p>
<p>
Dependency Hierarchy:
- :x: **microsoft.chakracore.1.8.0.nupkg** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/scm-automation-project/vsix-nuget-simple-project/commit/026ce0ebdfc0d6ab0f3595e83fecf4f2458b0d83">026ce0ebdfc0d6ab0f3595e83fecf4f2458b0d83</a></p>
</p>
<p></p>
### Vulnerability Details
<p>
Chakra Scripting Engine Memory Corruption Vulnerability This CVE ID is unique from CVE-2020-17054.
<p>Publish Date: 2020-11-11
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2020-17048>CVE-2020-17048</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>8.1</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Release Date: 2020-11-11</p>
<p>Fix Resolution: v1.11.23</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation is available for this issue
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2019-0649</summary>
### Vulnerable Library - <b>microsoft.chakracore.1.8.0.nupkg</b></p>
<p>ChakraCore is the core part of the Chakra Javascript engine that powers Microsoft Edge.</p>
<p>Library home page: <a href="https://api.nuget.org/packages/microsoft.chakracore.1.8.0.nupkg">https://api.nuget.org/packages/microsoft.chakracore.1.8.0.nupkg</a></p>
<p>Path to dependency file: /Nuget_VSIX_Project/Nuget_VSIX_Project.csproj</p>
<p>Path to vulnerable library: /home/wss-scanner/.nuget/packages/microsoft.chakracore/1.8.0/microsoft.chakracore.1.8.0.nupkg</p>
<p>
Dependency Hierarchy:
- :x: **microsoft.chakracore.1.8.0.nupkg** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/scm-automation-project/vsix-nuget-simple-project/commit/026ce0ebdfc0d6ab0f3595e83fecf4f2458b0d83">026ce0ebdfc0d6ab0f3595e83fecf4f2458b0d83</a></p>
</p>
<p></p>
### Vulnerability Details
<p>
A vulnerability exists in Microsoft Chakra JIT server, aka 'Scripting Engine Elevation of Privileged Vulnerability'.
<p>Publish Date: 2019-03-05
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2019-0649>CVE-2019-0649</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>8.1</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Release Date: 2019-03-05</p>
<p>Fix Resolution: v1.11.6</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation is available for this issue
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2019-1003</summary>
### Vulnerable Library - <b>microsoft.chakracore.1.8.0.nupkg</b></p>
<p>ChakraCore is the core part of the Chakra Javascript engine that powers Microsoft Edge.</p>
<p>Library home page: <a href="https://api.nuget.org/packages/microsoft.chakracore.1.8.0.nupkg">https://api.nuget.org/packages/microsoft.chakracore.1.8.0.nupkg</a></p>
<p>Path to dependency file: /Nuget_VSIX_Project/Nuget_VSIX_Project.csproj</p>
<p>Path to vulnerable library: /home/wss-scanner/.nuget/packages/microsoft.chakracore/1.8.0/microsoft.chakracore.1.8.0.nupkg</p>
<p>
Dependency Hierarchy:
- :x: **microsoft.chakracore.1.8.0.nupkg** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/scm-automation-project/vsix-nuget-simple-project/commit/026ce0ebdfc0d6ab0f3595e83fecf4f2458b0d83">026ce0ebdfc0d6ab0f3595e83fecf4f2458b0d83</a></p>
</p>
<p></p>
### Vulnerability Details
<p>
A remote code execution vulnerability exists in the way that the Chakra scripting engine handles objects in memory in Microsoft Edge, aka 'Chakra Scripting Engine Memory Corruption Vulnerability'. This CVE ID is unique from CVE-2019-0989, CVE-2019-0991, CVE-2019-0992, CVE-2019-0993, CVE-2019-1002, CVE-2019-1024, CVE-2019-1051, CVE-2019-1052.
<p>Publish Date: 2019-06-12
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2019-1003>CVE-2019-1003</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>7.5</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: None
- User Interaction: Required
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Release Date: 2019-06-12</p>
<p>Fix Resolution: Microsoft.ChakraCore - 1.11.10</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation is available for this issue
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2019-1366</summary>
### Vulnerable Library - <b>microsoft.chakracore.1.8.0.nupkg</b></p>
<p>ChakraCore is the core part of the Chakra Javascript engine that powers Microsoft Edge.</p>
<p>Library home page: <a href="https://api.nuget.org/packages/microsoft.chakracore.1.8.0.nupkg">https://api.nuget.org/packages/microsoft.chakracore.1.8.0.nupkg</a></p>
<p>Path to dependency file: /Nuget_VSIX_Project/Nuget_VSIX_Project.csproj</p>
<p>Path to vulnerable library: /home/wss-scanner/.nuget/packages/microsoft.chakracore/1.8.0/microsoft.chakracore.1.8.0.nupkg</p>
<p>
Dependency Hierarchy:
- :x: **microsoft.chakracore.1.8.0.nupkg** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/scm-automation-project/vsix-nuget-simple-project/commit/026ce0ebdfc0d6ab0f3595e83fecf4f2458b0d83">026ce0ebdfc0d6ab0f3595e83fecf4f2458b0d83</a></p>
</p>
<p></p>
### Vulnerability Details
<p>
A remote code execution vulnerability exists in the way that the Chakra scripting engine handles objects in memory in Microsoft Edge, aka 'Chakra Scripting Engine Memory Corruption Vulnerability'. This CVE ID is unique from CVE-2019-1307, CVE-2019-1308, CVE-2019-1335.
<p>Publish Date: 2019-10-10
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2019-1366>CVE-2019-1366</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>7.5</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: None
- User Interaction: Required
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Release Date: 2019-10-10</p>
<p>Fix Resolution: Microsoft.ChakraCore - 1.11.14</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation is available for this issue
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2020-0813</summary>
### Vulnerable Library - <b>microsoft.chakracore.1.8.0.nupkg</b></p>
<p>ChakraCore is the core part of the Chakra Javascript engine that powers Microsoft Edge.</p>
<p>Library home page: <a href="https://api.nuget.org/packages/microsoft.chakracore.1.8.0.nupkg">https://api.nuget.org/packages/microsoft.chakracore.1.8.0.nupkg</a></p>
<p>Path to dependency file: /Nuget_VSIX_Project/Nuget_VSIX_Project.csproj</p>
<p>Path to vulnerable library: /home/wss-scanner/.nuget/packages/microsoft.chakracore/1.8.0/microsoft.chakracore.1.8.0.nupkg</p>
<p>
Dependency Hierarchy:
- :x: **microsoft.chakracore.1.8.0.nupkg** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/scm-automation-project/vsix-nuget-simple-project/commit/026ce0ebdfc0d6ab0f3595e83fecf4f2458b0d83">026ce0ebdfc0d6ab0f3595e83fecf4f2458b0d83</a></p>
</p>
<p></p>
### Vulnerability Details
<p>
An information disclosure vulnerability exists when Chakra improperly discloses the contents of its memory, which could provide an attacker with information to further compromise the user’s computer or data.To exploit the vulnerability, an attacker must know the memory address of where the object was created.The update addresses the vulnerability by changing the way certain functions handle objects in memory., aka 'Scripting Engine Information Disclosure Vulnerability'.
<p>Publish Date: 2020-03-12
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2020-0813>CVE-2020-0813</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>7.5</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: None
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Release Date: 2020-03-12</p>
<p>Fix Resolution: Microsoft.ChakraCore - 1.11.17</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation is available for this issue
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2018-8390</summary>
### Vulnerable Library - <b>microsoft.chakracore.1.8.0.nupkg</b></p>
<p>ChakraCore is the core part of the Chakra Javascript engine that powers Microsoft Edge.</p>
<p>Library home page: <a href="https://api.nuget.org/packages/microsoft.chakracore.1.8.0.nupkg">https://api.nuget.org/packages/microsoft.chakracore.1.8.0.nupkg</a></p>
<p>Path to dependency file: /Nuget_VSIX_Project/Nuget_VSIX_Project.csproj</p>
<p>Path to vulnerable library: /home/wss-scanner/.nuget/packages/microsoft.chakracore/1.8.0/microsoft.chakracore.1.8.0.nupkg</p>
<p>
Dependency Hierarchy:
- :x: **microsoft.chakracore.1.8.0.nupkg** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/scm-automation-project/vsix-nuget-simple-project/commit/026ce0ebdfc0d6ab0f3595e83fecf4f2458b0d83">026ce0ebdfc0d6ab0f3595e83fecf4f2458b0d83</a></p>
</p>
<p></p>
### Vulnerability Details
<p>
A remote code execution vulnerability exists in the way that the ChakraCore scripting engine handles objects in memory, aka "Scripting Engine Memory Corruption Vulnerability." This affects Microsoft Edge, ChakraCore. This CVE ID is unique from CVE-2018-8353, CVE-2018-8355, CVE-2018-8359, CVE-2018-8371, CVE-2018-8372, CVE-2018-8373, CVE-2018-8385, CVE-2018-8389.
<p>Publish Date: 2018-08-15
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2018-8390>CVE-2018-8390</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>7.5</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: None
- User Interaction: Required
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Release Date: 2018-08-15</p>
<p>Fix Resolution: v1.10.2</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation is available for this issue
</details>
***
<p>:rescue_worker_helmet: Automatic Remediation is available for this issue.</p> | True | microsoft.chakracore.1.8.0.nupkg: 162 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>microsoft.chakracore.1.8.0.nupkg</b></p></summary>
<p>ChakraCore is the core part of the Chakra Javascript engine that powers Microsoft Edge.</p>
<p>Library home page: <a href="https://api.nuget.org/packages/microsoft.chakracore.1.8.0.nupkg">https://api.nuget.org/packages/microsoft.chakracore.1.8.0.nupkg</a></p>
<p>Path to dependency file: /Nuget_VSIX_Project/Nuget_VSIX_Project.csproj</p>
<p>Path to vulnerable library: /home/wss-scanner/.nuget/packages/microsoft.chakracore/1.8.0/microsoft.chakracore.1.8.0.nupkg</p>
<p>
<p>Found in HEAD commit: <a href="https://github.com/scm-automation-project/vsix-nuget-simple-project/commit/026ce0ebdfc0d6ab0f3595e83fecf4f2458b0d83">026ce0ebdfc0d6ab0f3595e83fecf4f2458b0d83</a></p></details>
## Vulnerabilities
| CVE | Severity | <img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS | Dependency | Type | Fixed in (microsoft.chakracore.1.8.0.nupkg version) | Remediation Available |
| ------------- | ------------- | ----- | ----- | ----- | ------------- | --- |
| [CVE-2018-8500](https://www.mend.io/vulnerability-database/CVE-2018-8500) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 9.8 | microsoft.chakracore.1.8.0.nupkg | Direct | v1.11.2 | ✅ |
| [CVE-2020-1073](https://www.mend.io/vulnerability-database/CVE-2020-1073) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 8.1 | microsoft.chakracore.1.8.0.nupkg | Direct | v1.11.20 | ✅ |
| [CVE-2020-17048](https://www.mend.io/vulnerability-database/CVE-2020-17048) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 8.1 | microsoft.chakracore.1.8.0.nupkg | Direct | v1.11.23 | ✅ |
| [CVE-2019-0649](https://www.mend.io/vulnerability-database/CVE-2019-0649) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 8.1 | microsoft.chakracore.1.8.0.nupkg | Direct | v1.11.6 | ✅ |
| [CVE-2019-1003](https://www.mend.io/vulnerability-database/CVE-2019-1003) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | Microsoft.ChakraCore - 1.11.10 | ✅ |
| [CVE-2019-1366](https://www.mend.io/vulnerability-database/CVE-2019-1366) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | Microsoft.ChakraCore - 1.11.14 | ✅ |
| [CVE-2020-0813](https://www.mend.io/vulnerability-database/CVE-2020-0813) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | Microsoft.ChakraCore - 1.11.17 | ✅ |
| [CVE-2018-8390](https://www.mend.io/vulnerability-database/CVE-2018-8390) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | v1.10.2 | ✅ |
| [CVE-2018-8380](https://www.mend.io/vulnerability-database/CVE-2018-8380) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | v1.10.2 | ✅ |
| [CVE-2018-8381](https://www.mend.io/vulnerability-database/CVE-2018-8381) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | v1.10.2 | ✅ |
| [CVE-2020-0823](https://www.mend.io/vulnerability-database/CVE-2020-0823) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | Microsoft.ChakraCore - 1.11.17 | ✅ |
| [CVE-2018-8384](https://www.mend.io/vulnerability-database/CVE-2018-8384) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | v1.10.2 | ✅ |
| [CVE-2018-8385](https://www.mend.io/vulnerability-database/CVE-2018-8385) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | v1.10.2 | ✅ |
| [CVE-2018-8266](https://www.mend.io/vulnerability-database/CVE-2018-8266) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | v1.10.2 | ✅ |
| [CVE-2018-8541](https://www.mend.io/vulnerability-database/CVE-2018-8541) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | v1.11.3 | ✅ |
| [CVE-2018-8542](https://www.mend.io/vulnerability-database/CVE-2018-8542) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | v1.11.3 | ✅ |
| [CVE-2018-8543](https://www.mend.io/vulnerability-database/CVE-2018-8543) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | v1.11.3 | ✅ |
| [CVE-2019-1092](https://www.mend.io/vulnerability-database/CVE-2019-1092) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | Microsoft.ChakraCore - 1.11.11 | ✅ |
| [CVE-2019-1131](https://www.mend.io/vulnerability-database/CVE-2019-1131) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | Microsoft.ChakraCore - 1.11.12 | ✅ |
| [CVE-2020-0828](https://www.mend.io/vulnerability-database/CVE-2020-0828) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | Microsoft.ChakraCore - 1.11.17 | ✅ |
| [CVE-2020-0829](https://www.mend.io/vulnerability-database/CVE-2020-0829) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | Microsoft.ChakraCore - 1.11.17 | ✅ |
| [CVE-2020-0825](https://www.mend.io/vulnerability-database/CVE-2020-0825) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | Microsoft.ChakraCore - 1.11.17 | ✅ |
| [CVE-2020-0826](https://www.mend.io/vulnerability-database/CVE-2020-0826) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | Microsoft.ChakraCore - 1.11.17 | ✅ |
| [CVE-2018-8280](https://www.mend.io/vulnerability-database/CVE-2018-8280) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | v1.10.1 | ✅ |
| [CVE-2018-8391](https://www.mend.io/vulnerability-database/CVE-2018-8391) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | v1.11.1 | ✅ |
| [CVE-2020-0831](https://www.mend.io/vulnerability-database/CVE-2020-0831) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | Microsoft.ChakraCore - 1.11.17 | ✅ |
| [CVE-2020-0711](https://www.mend.io/vulnerability-database/CVE-2020-0711) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | Microsoft.ChakraCore - 1.11.16 | ✅ |
| [CVE-2019-0568](https://www.mend.io/vulnerability-database/CVE-2019-0568) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | v1.11.5 | ✅ |
| [CVE-2020-0712](https://www.mend.io/vulnerability-database/CVE-2020-0712) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | Microsoft.ChakraCore - 1.11.16 | ✅ |
| [CVE-2019-0567](https://www.mend.io/vulnerability-database/CVE-2019-0567) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | v1.11.5 | ✅ |
| [CVE-2019-1138](https://www.mend.io/vulnerability-database/CVE-2019-1138) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | Microsoft.ChakraCore - 1.11.13 | ✅ |
| [CVE-2020-0713](https://www.mend.io/vulnerability-database/CVE-2020-0713) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | Microsoft.ChakraCore - 1.11.16 | ✅ |
| [CVE-2018-0837](https://www.mend.io/vulnerability-database/CVE-2018-0837) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | Microsoft.TypeScript.Compiler - 2.8.4,2.7.2,2.2.0;Microsoft.TypeScript.MSBuild - 2.8.4;Microsoft.Azure.StreamAnalytics.CICD - 1.2.0;BaristaLabs.BaristaCore.ChakraCore.win-arm - 1.8.1;BaristaLabs.BaristaCore.ChakraCore.win-x64 - 1.8.1;BaristaLabs.BaristaCore.ChakraCore.win-x86 - 1.8.1;Microsoft.ChakraCore.vc140 - 1.8.1;Microsoft.ChakraCore - 1.8.1 | ✅ |
| [CVE-2018-8275](https://www.mend.io/vulnerability-database/CVE-2018-8275) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | v1.10.1 | ✅ |
| [CVE-2018-0838](https://www.mend.io/vulnerability-database/CVE-2018-0838) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | Microsoft.TypeScript.Compiler - 2.8.4,2.7.2,2.2.0;Microsoft.TypeScript.MSBuild - 2.8.4;Microsoft.Azure.StreamAnalytics.CICD - 1.2.0;BaristaLabs.BaristaCore.ChakraCore.win-arm - 1.8.1;BaristaLabs.BaristaCore.ChakraCore.win-x64 - 1.8.1;BaristaLabs.BaristaCore.ChakraCore.win-x86 - 1.8.1;Microsoft.ChakraCore.vc140 - 1.8.1,1.5.3;Microsoft.ChakraCore - 1.8.1 | ✅ |
| [CVE-2018-8551](https://www.mend.io/vulnerability-database/CVE-2018-8551) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | v1.11.3 | ✅ |
| [CVE-2019-0605](https://www.mend.io/vulnerability-database/CVE-2019-0605) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | v1.11.6 | ✅ |
| [CVE-2019-0607](https://www.mend.io/vulnerability-database/CVE-2019-0607) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | v1.11.6 | ✅ |
| [CVE-2018-8279](https://www.mend.io/vulnerability-database/CVE-2018-8279) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | v1.10.1 | ✅ |
| [CVE-2018-8555](https://www.mend.io/vulnerability-database/CVE-2018-8555) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | v1.11.3 | ✅ |
| [CVE-2019-0609](https://www.mend.io/vulnerability-database/CVE-2019-0609) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | v1.11.7 | ✅ |
| [CVE-2018-0835](https://www.mend.io/vulnerability-database/CVE-2018-0835) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | Microsoft.ChakraCore - 1.8.1;Microsoft.TypeScript.Compiler - 2.7.2,2.8.4,2.2.0;Microsoft.TypeScript.MSBuild - 2.8.4;Microsoft.Azure.StreamAnalytics.CICD - 1.2.0;BaristaLabs.BaristaCore.ChakraCore.win-arm - 1.8.1;BaristaLabs.BaristaCore.ChakraCore.win-x64 - 1.8.1;BaristaLabs.BaristaCore.ChakraCore.win-x86 - 1.8.1;Microsoft.ChakraCore.vc140 - 1.8.1,1.5.0 | ✅ |
| [CVE-2018-8556](https://www.mend.io/vulnerability-database/CVE-2018-8556) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | v1.11.3 | ✅ |
| [CVE-2018-8557](https://www.mend.io/vulnerability-database/CVE-2018-8557) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | v1.11.3 | ✅ |
| [CVE-2019-1140](https://www.mend.io/vulnerability-database/CVE-2019-1140) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | 1.11.12 | ✅ |
| [CVE-2019-1141](https://www.mend.io/vulnerability-database/CVE-2019-1141) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | 1.11.12 | ✅ |
| [CVE-2019-1300](https://www.mend.io/vulnerability-database/CVE-2019-1300) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | Microsoft.ChakraCore - 1.11.13 | ✅ |
| [CVE-2019-1024](https://www.mend.io/vulnerability-database/CVE-2019-1024) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | Microsoft.ChakraCore - 1.11.10 | ✅ |
| [CVE-2019-0610](https://www.mend.io/vulnerability-database/CVE-2019-0610) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | v1.11.6 | ✅ |
| [CVE-2019-0611](https://www.mend.io/vulnerability-database/CVE-2019-0611) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | v1.11.7 | ✅ |
| [CVE-2019-1308](https://www.mend.io/vulnerability-database/CVE-2019-1308) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | Microsoft.ChakraCore - 1.11.14 | ✅ |
| [CVE-2018-8243](https://www.mend.io/vulnerability-database/CVE-2018-8243) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | v1.8.5 | ✅ |
| [CVE-2019-1427](https://www.mend.io/vulnerability-database/CVE-2019-1427) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | Microsoft.ChakraCore - 1.11.15 | ✅ |
| [CVE-2019-1307](https://www.mend.io/vulnerability-database/CVE-2019-1307) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | Microsoft.ChakraCore - 1.11.14 | ✅ |
| [CVE-2019-1428](https://www.mend.io/vulnerability-database/CVE-2019-1428) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | Microsoft.ChakraCore - 1.11.15 | ✅ |
| [CVE-2019-0739](https://www.mend.io/vulnerability-database/CVE-2019-0739) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | Microsoft.ChakraCore - 1.11.8 | ✅ |
| [CVE-2018-8367](https://www.mend.io/vulnerability-database/CVE-2018-8367) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | v1.11.1 | ✅ |
| [CVE-2020-17054](https://www.mend.io/vulnerability-database/CVE-2020-17054) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | v1.11.23 | ✅ |
| [CVE-2019-0861](https://www.mend.io/vulnerability-database/CVE-2019-0861) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | Microsoft.ChakraCore - 1.11.8 | ✅ |
| [CVE-2020-0848](https://www.mend.io/vulnerability-database/CVE-2020-0848) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | Microsoft.ChakraCore - 1.11.17 | ✅ |
| [CVE-2019-0860](https://www.mend.io/vulnerability-database/CVE-2019-0860) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | Microsoft.ChakraCore - 1.11.8 | ✅ |
| [CVE-2018-8372](https://www.mend.io/vulnerability-database/CVE-2018-8372) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | v1.10.2 | ✅ |
| [CVE-2018-0937](https://www.mend.io/vulnerability-database/CVE-2018-0937) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | Microsoft.TypeScript.Compiler - 2.8.4,2.7.2,2.2.0;Microsoft.TypeScript.MSBuild - 2.8.4;Microsoft.Azure.StreamAnalytics.CICD - 1.2.0;BaristaLabs.BaristaCore.ChakraCore.win-arm - 1.8.5;BaristaLabs.BaristaCore.ChakraCore.win-x64 - 1.8.5;BaristaLabs.BaristaCore.ChakraCore.win-x86 - 1.8.5;Microsoft.ChakraCore.vc140 - 1.8.2;Microsoft.ChakraCore - 1.8.2 | ✅ |
| [CVE-2019-0989](https://www.mend.io/vulnerability-database/CVE-2019-0989) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | Microsoft.ChakraCore - 1.11.10 | ✅ |
| [CVE-2018-0933](https://www.mend.io/vulnerability-database/CVE-2018-0933) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | Microsoft.Azure.StreamAnalytics.CICD - 1.2.0;BaristaLabs.BaristaCore.ChakraCore.win-arm - 1.8.1;BaristaLabs.BaristaCore.ChakraCore.win-x64 - 1.8.1;BaristaLabs.BaristaCore.ChakraCore.win-x86 - 1.8.1;Microsoft.ChakraCore.vc140 - 1.8.0;Microsoft.ChakraCore - 1.8.2 | ✅ |
| [CVE-2018-8629](https://www.mend.io/vulnerability-database/CVE-2018-8629) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | v1.11.4 | ✅ |
| [CVE-2019-0591](https://www.mend.io/vulnerability-database/CVE-2019-0591) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | v1.11.6 | ✅ |
| [CVE-2019-0590](https://www.mend.io/vulnerability-database/CVE-2019-0590) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | v1.11.6 | ✅ |
| [CVE-2019-0593](https://www.mend.io/vulnerability-database/CVE-2019-0593) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | v1.11.6 | ✅ |
| [CVE-2019-0592](https://www.mend.io/vulnerability-database/CVE-2019-0592) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | v1.11.7 | ✅ |
| [CVE-2019-0991](https://www.mend.io/vulnerability-database/CVE-2019-0991) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | Microsoft.ChakraCore - 1.11.10 | ✅ |
| [CVE-2019-0993](https://www.mend.io/vulnerability-database/CVE-2019-0993) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | Microsoft.ChakraCore - 1.11.10 | ✅ |
| [CVE-2019-0992](https://www.mend.io/vulnerability-database/CVE-2019-0992) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | Microsoft.ChakraCore - 1.11.10 | ✅ |
| [CVE-2019-0911](https://www.mend.io/vulnerability-database/CVE-2019-0911) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | Microsoft.ChakraCore - 1.11.9 | ✅ |
| [CVE-2018-8583](https://www.mend.io/vulnerability-database/CVE-2018-8583) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | v1.11.4 | ✅ |
| [CVE-2020-1037](https://www.mend.io/vulnerability-database/CVE-2020-1037) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | Microsoft.ChakraCore - 1.11.19 | ✅ |
| [CVE-2019-0913](https://www.mend.io/vulnerability-database/CVE-2019-0913) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | Microsoft.ChakraCore - 1.11.9 | ✅ |
| [CVE-2019-0912](https://www.mend.io/vulnerability-database/CVE-2019-0912) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | Microsoft.ChakraCore - 1.11.9 | ✅ |
| [CVE-2018-8465](https://www.mend.io/vulnerability-database/CVE-2018-8465) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | v1.11.1 | ✅ |
| [CVE-2019-0915](https://www.mend.io/vulnerability-database/CVE-2019-0915) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | Microsoft.ChakraCore - 1.11.9 | ✅ |
| [CVE-2018-0866](https://www.mend.io/vulnerability-database/CVE-2018-0866) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | Microsoft.ChakraCore - 1.8.1;Microsoft.TypeScript.Compiler - 2.7.2,2.8.4,2.2.0;Microsoft.TypeScript.MSBuild - 2.8.4;Microsoft.Azure.StreamAnalytics.CICD - 1.2.0;BaristaLabs.BaristaCore.ChakraCore.win-arm - 1.8.1;BaristaLabs.BaristaCore.ChakraCore.win-x64 - 1.8.1;BaristaLabs.BaristaCore.ChakraCore.win-x86 - 1.8.1;Microsoft.ChakraCore.vc140 - 1.8.1 | ✅ |
| [CVE-2018-8466](https://www.mend.io/vulnerability-database/CVE-2018-8466) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | v1.11.1 | ✅ |
| [CVE-2019-0639](https://www.mend.io/vulnerability-database/CVE-2019-0639) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | v1.11.7 | ✅ |
| [CVE-2019-0914](https://www.mend.io/vulnerability-database/CVE-2019-0914) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | Microsoft.ChakraCore - 1.11.9 | ✅ |
| [CVE-2018-8467](https://www.mend.io/vulnerability-database/CVE-2018-8467) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | v1.11.1 | ✅ |
| [CVE-2018-8588](https://www.mend.io/vulnerability-database/CVE-2018-8588) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | v1.11.3 | ✅ |
| [CVE-2019-0917](https://www.mend.io/vulnerability-database/CVE-2019-0917) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | Microsoft.ChakraCore - 1.11.9 | ✅ |
| [CVE-2019-0916](https://www.mend.io/vulnerability-database/CVE-2019-0916) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | Microsoft.ChakraCore - 1.11.9 | ✅ |
| [CVE-2018-8227](https://www.mend.io/vulnerability-database/CVE-2018-8227) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | v1.8.5 | ✅ |
| [CVE-2018-8503](https://www.mend.io/vulnerability-database/CVE-2018-8503) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | v1.11.2 | ✅ |
| [CVE-2018-8624](https://www.mend.io/vulnerability-database/CVE-2018-8624) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | v1.11.4 | ✅ |
| [CVE-2018-8229](https://www.mend.io/vulnerability-database/CVE-2018-8229) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | v1.8.5 | ✅ |
| [CVE-2018-8505](https://www.mend.io/vulnerability-database/CVE-2018-8505) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | v1.11.2 | ✅ |
| [CVE-2019-1051](https://www.mend.io/vulnerability-database/CVE-2019-1051) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | Microsoft.ChakraCore - 1.11.10 | ✅ |
| [CVE-2019-1052](https://www.mend.io/vulnerability-database/CVE-2019-1052) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | Microsoft.ChakraCore - 1.11.10 | ✅ |
| [CVE-2019-1298](https://www.mend.io/vulnerability-database/CVE-2019-1298) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | Microsoft.ChakraCore - 1.11.13 | ✅ |
| [CVE-2019-0640](https://www.mend.io/vulnerability-database/CVE-2019-0640) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | v1.11.6 | ✅ |
| [CVE-2019-0642](https://www.mend.io/vulnerability-database/CVE-2019-0642) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | Microsoft.ChakraCore - 1.11.6 | ✅ |
| [CVE-2019-1217](https://www.mend.io/vulnerability-database/CVE-2019-1217) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | 1.11.13 | ✅ |
| [CVE-2019-1335](https://www.mend.io/vulnerability-database/CVE-2019-1335) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | Microsoft.ChakraCore - 1.11.14 | ✅ |
| [CVE-2019-0644](https://www.mend.io/vulnerability-database/CVE-2019-0644) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | v1.11.6 | ✅ |
| [CVE-2019-0922](https://www.mend.io/vulnerability-database/CVE-2019-0922) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | Microsoft.ChakraCore - 1.11.9 | ✅ |
| [CVE-2018-8473](https://www.mend.io/vulnerability-database/CVE-2018-8473) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | v1.11.2 | ✅ |
| [CVE-2019-0924](https://www.mend.io/vulnerability-database/CVE-2019-0924) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | Microsoft.ChakraCore - 1.11.9 | ✅ |
| [CVE-2018-8354](https://www.mend.io/vulnerability-database/CVE-2018-8354) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | v1.11.1 | ✅ |
| [CVE-2019-0769](https://www.mend.io/vulnerability-database/CVE-2019-0769) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | Microsoft.ChakraCore - 1.11.7 | ✅ |
| [CVE-2019-0923](https://www.mend.io/vulnerability-database/CVE-2019-0923) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | Microsoft.ChakraCore - 1.11.9 | ✅ |
| [CVE-2018-8355](https://www.mend.io/vulnerability-database/CVE-2018-8355) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | v1.10.2 | ✅ |
| [CVE-2018-8510](https://www.mend.io/vulnerability-database/CVE-2018-8510) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | v1.11.2 | ✅ |
| [CVE-2019-0925](https://www.mend.io/vulnerability-database/CVE-2019-0925) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | Microsoft.ChakraCore - 1.11.9 | ✅ |
| [CVE-2018-8236](https://www.mend.io/vulnerability-database/CVE-2018-8236) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | v1.8.5 | ✅ |
| [CVE-2018-8511](https://www.mend.io/vulnerability-database/CVE-2018-8511) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | v1.11.2 | ✅ |
| [CVE-2019-0806](https://www.mend.io/vulnerability-database/CVE-2019-0806) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | Microsoft.ChakraCore - 1.11.8 | ✅ |
| [CVE-2019-0927](https://www.mend.io/vulnerability-database/CVE-2019-0927) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | Microsoft.ChakraCore - 1.11.9 | ✅ |
| [CVE-2018-8359](https://www.mend.io/vulnerability-database/CVE-2018-8359) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | v1.10.2 | ✅ |
| [CVE-2018-8513](https://www.mend.io/vulnerability-database/CVE-2018-8513) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | v1.11.2 | ✅ |
| [CVE-2018-0874](https://www.mend.io/vulnerability-database/CVE-2018-0874) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | Microsoft.TypeScript.MSBuild - 2.2.1;BaristaLabs.BaristaCore.ChakraCore.win-arm - 1.8.1;BaristaLabs.BaristaCore.ChakraCore.win-x64 - 1.8.5;BaristaLabs.BaristaCore.ChakraCore.win-x86 - 1.8.5;Microsoft.ChakraCore.vc140 - 1.8.2;Microsoft.ChakraCore - 1.8.2 | ✅ |
| [CVE-2019-1062](https://www.mend.io/vulnerability-database/CVE-2019-1062) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | Microsoft.ChakraCore - 1.11.11 | ✅ |
| [CVE-2019-0771](https://www.mend.io/vulnerability-database/CVE-2019-0771) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | 1.11.7 | ✅ |
| [CVE-2019-1103](https://www.mend.io/vulnerability-database/CVE-2019-1103) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | Microsoft.ChakraCore - 1.11.11 | ✅ |
| [CVE-2018-8290](https://www.mend.io/vulnerability-database/CVE-2018-8290) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | v1.10.1 | ✅ |
| [CVE-2019-0652](https://www.mend.io/vulnerability-database/CVE-2019-0652) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | Microsoft.ChakraCore - 1.11.6 | ✅ |
| [CVE-2019-0773](https://www.mend.io/vulnerability-database/CVE-2019-0773) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | 1.11.7 | ✅ |
| [CVE-2018-8291](https://www.mend.io/vulnerability-database/CVE-2018-8291) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | v1.10.1 | ✅ |
| [CVE-2019-0651](https://www.mend.io/vulnerability-database/CVE-2019-0651) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | v1.11.6 | ✅ |
| [CVE-2019-1106](https://www.mend.io/vulnerability-database/CVE-2019-1106) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | v1.11.11 | ✅ |
| [CVE-2019-1107](https://www.mend.io/vulnerability-database/CVE-2019-1107) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | v1.11.11 | ✅ |
| [CVE-2018-8283](https://www.mend.io/vulnerability-database/CVE-2018-8283) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | v1.10.1 | ✅ |
| [CVE-2020-0767](https://www.mend.io/vulnerability-database/CVE-2020-0767) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | Microsoft.ChakraCore - 1.11.16 | ✅ |
| [CVE-2019-0655](https://www.mend.io/vulnerability-database/CVE-2019-0655) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | Microsoft.ChakraCore - 1.11.6 | ✅ |
| [CVE-2020-0768](https://www.mend.io/vulnerability-database/CVE-2020-0768) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | Microsoft.ChakraCore - 1.11.17 | ✅ |
| [CVE-2020-1219](https://www.mend.io/vulnerability-database/CVE-2020-1219) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | v1.11.20 | ✅ |
| [CVE-2019-0812](https://www.mend.io/vulnerability-database/CVE-2019-0812) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | Microsoft.ChakraCore - 1.11.8 | ✅ |
| [CVE-2019-0933](https://www.mend.io/vulnerability-database/CVE-2019-0933) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | Microsoft.ChakraCore - 1.11.9 | ✅ |
| [CVE-2018-8286](https://www.mend.io/vulnerability-database/CVE-2018-8286) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | v1.10.1 | ✅ |
| [CVE-2018-8287](https://www.mend.io/vulnerability-database/CVE-2018-8287) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | v1.10.1 | ✅ |
| [CVE-2019-0539](https://www.mend.io/vulnerability-database/CVE-2019-0539) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | v1.11.5 | ✅ |
| [CVE-2018-8288](https://www.mend.io/vulnerability-database/CVE-2018-8288) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | v1.10.1 | ✅ |
| [CVE-2019-0937](https://www.mend.io/vulnerability-database/CVE-2019-0937) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | Microsoft.ChakraCore - 1.11.9 | ✅ |
| [CVE-2018-0840](https://www.mend.io/vulnerability-database/CVE-2018-0840) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | Microsoft.ChakraCore - 1.8.1;Microsoft.TypeScript.Compiler - 2.7.2,2.8.4,2.2.0;Microsoft.TypeScript.MSBuild - 2.8.4;BaristaLabs.BaristaCore.ChakraCore.win-arm - 1.8.1;BaristaLabs.BaristaCore.ChakraCore.win-x86 - 1.8.1;Microsoft.ChakraCore.vc140 - 1.8.1 | ✅ |
| [CVE-2020-17131](https://www.mend.io/vulnerability-database/CVE-2020-17131) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | Microsoft.ChakraCore - 1.11.24 | ✅ |
| [CVE-2018-8617](https://www.mend.io/vulnerability-database/CVE-2018-8617) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | v1.11.4 | ✅ |
| [CVE-2018-8618](https://www.mend.io/vulnerability-database/CVE-2018-8618) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | v1.11.4 | ✅ |
| [CVE-2019-1197](https://www.mend.io/vulnerability-database/CVE-2019-1197) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | Microsoft.ChakraCore - 1.11.12 | ✅ |
| [CVE-2019-1195](https://www.mend.io/vulnerability-database/CVE-2019-1195) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | Microsoft.ChakraCore - 1.11.12 | ✅ |
| [CVE-2019-1196](https://www.mend.io/vulnerability-database/CVE-2019-1196) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | Microsoft.ChakraCore - 1.11.12 | ✅ |
| [CVE-2018-8294](https://www.mend.io/vulnerability-database/CVE-2018-8294) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | v1.10.1 | ✅ |
| [CVE-2020-0811](https://www.mend.io/vulnerability-database/CVE-2020-0811) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | Microsoft.ChakraCore - 1.11.17 | ✅ |
| [CVE-2019-1237](https://www.mend.io/vulnerability-database/CVE-2019-1237) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | Microsoft.ChakraCore - 1.11.13 | ✅ |
| [CVE-2020-0812](https://www.mend.io/vulnerability-database/CVE-2020-0812) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | Microsoft.ChakraCore - 1.11.17 | ✅ |
| [CVE-2018-8298](https://www.mend.io/vulnerability-database/CVE-2018-8298) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | v1.10.1 | ✅ |
| [CVE-2020-1065](https://www.mend.io/vulnerability-database/CVE-2020-1065) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | Microsoft.ChakraCore - 1.11.19 | ✅ |
| [CVE-2018-8456](https://www.mend.io/vulnerability-database/CVE-2018-8456) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | v1.11.1 | ✅ |
| [CVE-2019-0829](https://www.mend.io/vulnerability-database/CVE-2019-0829) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | Microsoft.ChakraCore - 1.11.8 | ✅ |
| [CVE-2018-8459](https://www.mend.io/vulnerability-database/CVE-2018-8459) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | microsoft.chakracore.1.8.0.nupkg | Direct | v1.11.1 | ✅ |
| [CVE-2018-8276](https://www.mend.io/vulnerability-database/CVE-2018-8276) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 6.5 | microsoft.chakracore.1.8.0.nupkg | Direct | v1.10.1 | ✅ |
| [CVE-2019-1023](https://www.mend.io/vulnerability-database/CVE-2019-1023) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 6.5 | microsoft.chakracore.1.8.0.nupkg | Direct | Microsoft.ChakraCore - 1.11.10 | ✅ |
| [CVE-2019-0746](https://www.mend.io/vulnerability-database/CVE-2019-0746) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 6.5 | microsoft.chakracore.1.8.0.nupkg | Direct | Microsoft.ChakraCore - 1.11.7 | ✅ |
| [CVE-2019-0990](https://www.mend.io/vulnerability-database/CVE-2019-0990) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 6.5 | microsoft.chakracore.1.8.0.nupkg | Direct | Microsoft.ChakraCore - 1.11.10 | ✅ |
| [CVE-2019-0648](https://www.mend.io/vulnerability-database/CVE-2019-0648) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 4.3 | microsoft.chakracore.1.8.0.nupkg | Direct | v1.11.6 | ✅ |
| [CVE-2018-8452](https://www.mend.io/vulnerability-database/CVE-2018-8452) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 4.3 | microsoft.chakracore.1.8.0.nupkg | Direct | v1.11.1 | ✅ |
| [CVE-2018-8315](https://www.mend.io/vulnerability-database/CVE-2018-8315) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 4.2 | microsoft.chakracore.1.8.0.nupkg | Direct | v1.11.2 | ✅ |
## Details
> Partial details (8 vulnerabilities) are displayed below due to a content size limitation in GitHub. To view information on the remaining vulnerabilities, navigate to the Mend Application.<br>
<details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2018-8500</summary>
### Vulnerable Library - <b>microsoft.chakracore.1.8.0.nupkg</b></p>
<p>ChakraCore is the core part of the Chakra Javascript engine that powers Microsoft Edge.</p>
<p>Library home page: <a href="https://api.nuget.org/packages/microsoft.chakracore.1.8.0.nupkg">https://api.nuget.org/packages/microsoft.chakracore.1.8.0.nupkg</a></p>
<p>Path to dependency file: /Nuget_VSIX_Project/Nuget_VSIX_Project.csproj</p>
<p>Path to vulnerable library: /home/wss-scanner/.nuget/packages/microsoft.chakracore/1.8.0/microsoft.chakracore.1.8.0.nupkg</p>
<p>
Dependency Hierarchy:
- :x: **microsoft.chakracore.1.8.0.nupkg** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/scm-automation-project/vsix-nuget-simple-project/commit/026ce0ebdfc0d6ab0f3595e83fecf4f2458b0d83">026ce0ebdfc0d6ab0f3595e83fecf4f2458b0d83</a></p>
</p>
<p></p>
### Vulnerability Details
<p>
A remote code execution vulnerability exists in the way that the ChakraCore scripting engine handles objects in memory, aka "Scripting Engine Memory Corruption Vulnerability." This affects ChakraCore.
<p>Publish Date: 2018-10-10
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2018-8500>CVE-2018-8500</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>Release Date: 2018-10-10</p>
<p>Fix Resolution: v1.11.2</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation is available for this issue
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2020-1073</summary>
### Vulnerable Library - <b>microsoft.chakracore.1.8.0.nupkg</b></p>
<p>ChakraCore is the core part of the Chakra Javascript engine that powers Microsoft Edge.</p>
<p>Library home page: <a href="https://api.nuget.org/packages/microsoft.chakracore.1.8.0.nupkg">https://api.nuget.org/packages/microsoft.chakracore.1.8.0.nupkg</a></p>
<p>Path to dependency file: /Nuget_VSIX_Project/Nuget_VSIX_Project.csproj</p>
<p>Path to vulnerable library: /home/wss-scanner/.nuget/packages/microsoft.chakracore/1.8.0/microsoft.chakracore.1.8.0.nupkg</p>
<p>
Dependency Hierarchy:
- :x: **microsoft.chakracore.1.8.0.nupkg** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/scm-automation-project/vsix-nuget-simple-project/commit/026ce0ebdfc0d6ab0f3595e83fecf4f2458b0d83">026ce0ebdfc0d6ab0f3595e83fecf4f2458b0d83</a></p>
</p>
<p></p>
### Vulnerability Details
<p>
A remote code execution vulnerability exists in the way that the ChakraCore scripting engine handles objects in memory, aka 'Scripting Engine Memory Corruption Vulnerability'.
<p>Publish Date: 2020-06-09
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2020-1073>CVE-2020-1073</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>8.1</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Release Date: 2020-06-09</p>
<p>Fix Resolution: v1.11.20</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation is available for this issue
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2020-17048</summary>
### Vulnerable Library - <b>microsoft.chakracore.1.8.0.nupkg</b></p>
<p>ChakraCore is the core part of the Chakra Javascript engine that powers Microsoft Edge.</p>
<p>Library home page: <a href="https://api.nuget.org/packages/microsoft.chakracore.1.8.0.nupkg">https://api.nuget.org/packages/microsoft.chakracore.1.8.0.nupkg</a></p>
<p>Path to dependency file: /Nuget_VSIX_Project/Nuget_VSIX_Project.csproj</p>
<p>Path to vulnerable library: /home/wss-scanner/.nuget/packages/microsoft.chakracore/1.8.0/microsoft.chakracore.1.8.0.nupkg</p>
<p>
Dependency Hierarchy:
- :x: **microsoft.chakracore.1.8.0.nupkg** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/scm-automation-project/vsix-nuget-simple-project/commit/026ce0ebdfc0d6ab0f3595e83fecf4f2458b0d83">026ce0ebdfc0d6ab0f3595e83fecf4f2458b0d83</a></p>
</p>
<p></p>
### Vulnerability Details
<p>
Chakra Scripting Engine Memory Corruption Vulnerability This CVE ID is unique from CVE-2020-17054.
<p>Publish Date: 2020-11-11
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2020-17048>CVE-2020-17048</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>8.1</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Release Date: 2020-11-11</p>
<p>Fix Resolution: v1.11.23</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation is available for this issue
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2019-0649</summary>
### Vulnerable Library - <b>microsoft.chakracore.1.8.0.nupkg</b></p>
<p>ChakraCore is the core part of the Chakra Javascript engine that powers Microsoft Edge.</p>
<p>Library home page: <a href="https://api.nuget.org/packages/microsoft.chakracore.1.8.0.nupkg">https://api.nuget.org/packages/microsoft.chakracore.1.8.0.nupkg</a></p>
<p>Path to dependency file: /Nuget_VSIX_Project/Nuget_VSIX_Project.csproj</p>
<p>Path to vulnerable library: /home/wss-scanner/.nuget/packages/microsoft.chakracore/1.8.0/microsoft.chakracore.1.8.0.nupkg</p>
<p>
Dependency Hierarchy:
- :x: **microsoft.chakracore.1.8.0.nupkg** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/scm-automation-project/vsix-nuget-simple-project/commit/026ce0ebdfc0d6ab0f3595e83fecf4f2458b0d83">026ce0ebdfc0d6ab0f3595e83fecf4f2458b0d83</a></p>
</p>
<p></p>
### Vulnerability Details
<p>
A vulnerability exists in Microsoft Chakra JIT server, aka 'Scripting Engine Elevation of Privileged Vulnerability'.
<p>Publish Date: 2019-03-05
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2019-0649>CVE-2019-0649</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>8.1</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Release Date: 2019-03-05</p>
<p>Fix Resolution: v1.11.6</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation is available for this issue
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2019-1003</summary>
### Vulnerable Library - <b>microsoft.chakracore.1.8.0.nupkg</b></p>
<p>ChakraCore is the core part of the Chakra Javascript engine that powers Microsoft Edge.</p>
<p>Library home page: <a href="https://api.nuget.org/packages/microsoft.chakracore.1.8.0.nupkg">https://api.nuget.org/packages/microsoft.chakracore.1.8.0.nupkg</a></p>
<p>Path to dependency file: /Nuget_VSIX_Project/Nuget_VSIX_Project.csproj</p>
<p>Path to vulnerable library: /home/wss-scanner/.nuget/packages/microsoft.chakracore/1.8.0/microsoft.chakracore.1.8.0.nupkg</p>
<p>
Dependency Hierarchy:
- :x: **microsoft.chakracore.1.8.0.nupkg** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/scm-automation-project/vsix-nuget-simple-project/commit/026ce0ebdfc0d6ab0f3595e83fecf4f2458b0d83">026ce0ebdfc0d6ab0f3595e83fecf4f2458b0d83</a></p>
</p>
<p></p>
### Vulnerability Details
<p>
A remote code execution vulnerability exists in the way that the Chakra scripting engine handles objects in memory in Microsoft Edge, aka 'Chakra Scripting Engine Memory Corruption Vulnerability'. This CVE ID is unique from CVE-2019-0989, CVE-2019-0991, CVE-2019-0992, CVE-2019-0993, CVE-2019-1002, CVE-2019-1024, CVE-2019-1051, CVE-2019-1052.
<p>Publish Date: 2019-06-12
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2019-1003>CVE-2019-1003</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>7.5</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: None
- User Interaction: Required
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Release Date: 2019-06-12</p>
<p>Fix Resolution: Microsoft.ChakraCore - 1.11.10</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation is available for this issue
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2019-1366</summary>
### Vulnerable Library - <b>microsoft.chakracore.1.8.0.nupkg</b></p>
<p>ChakraCore is the core part of the Chakra Javascript engine that powers Microsoft Edge.</p>
<p>Library home page: <a href="https://api.nuget.org/packages/microsoft.chakracore.1.8.0.nupkg">https://api.nuget.org/packages/microsoft.chakracore.1.8.0.nupkg</a></p>
<p>Path to dependency file: /Nuget_VSIX_Project/Nuget_VSIX_Project.csproj</p>
<p>Path to vulnerable library: /home/wss-scanner/.nuget/packages/microsoft.chakracore/1.8.0/microsoft.chakracore.1.8.0.nupkg</p>
<p>
Dependency Hierarchy:
- :x: **microsoft.chakracore.1.8.0.nupkg** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/scm-automation-project/vsix-nuget-simple-project/commit/026ce0ebdfc0d6ab0f3595e83fecf4f2458b0d83">026ce0ebdfc0d6ab0f3595e83fecf4f2458b0d83</a></p>
</p>
<p></p>
### Vulnerability Details
<p>
A remote code execution vulnerability exists in the way that the Chakra scripting engine handles objects in memory in Microsoft Edge, aka 'Chakra Scripting Engine Memory Corruption Vulnerability'. This CVE ID is unique from CVE-2019-1307, CVE-2019-1308, CVE-2019-1335.
<p>Publish Date: 2019-10-10
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2019-1366>CVE-2019-1366</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>7.5</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: None
- User Interaction: Required
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Release Date: 2019-10-10</p>
<p>Fix Resolution: Microsoft.ChakraCore - 1.11.14</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation is available for this issue
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2020-0813</summary>
### Vulnerable Library - <b>microsoft.chakracore.1.8.0.nupkg</b></p>
<p>ChakraCore is the core part of the Chakra Javascript engine that powers Microsoft Edge.</p>
<p>Library home page: <a href="https://api.nuget.org/packages/microsoft.chakracore.1.8.0.nupkg">https://api.nuget.org/packages/microsoft.chakracore.1.8.0.nupkg</a></p>
<p>Path to dependency file: /Nuget_VSIX_Project/Nuget_VSIX_Project.csproj</p>
<p>Path to vulnerable library: /home/wss-scanner/.nuget/packages/microsoft.chakracore/1.8.0/microsoft.chakracore.1.8.0.nupkg</p>
<p>
Dependency Hierarchy:
- :x: **microsoft.chakracore.1.8.0.nupkg** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/scm-automation-project/vsix-nuget-simple-project/commit/026ce0ebdfc0d6ab0f3595e83fecf4f2458b0d83">026ce0ebdfc0d6ab0f3595e83fecf4f2458b0d83</a></p>
</p>
<p></p>
### Vulnerability Details
<p>
An information disclosure vulnerability exists when Chakra improperly discloses the contents of its memory, which could provide an attacker with information to further compromise the user’s computer or data.To exploit the vulnerability, an attacker must know the memory address of where the object was created.The update addresses the vulnerability by changing the way certain functions handle objects in memory., aka 'Scripting Engine Information Disclosure Vulnerability'.
<p>Publish Date: 2020-03-12
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2020-0813>CVE-2020-0813</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>7.5</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: None
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Release Date: 2020-03-12</p>
<p>Fix Resolution: Microsoft.ChakraCore - 1.11.17</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation is available for this issue
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2018-8390</summary>
### Vulnerable Library - <b>microsoft.chakracore.1.8.0.nupkg</b></p>
<p>ChakraCore is the core part of the Chakra Javascript engine that powers Microsoft Edge.</p>
<p>Library home page: <a href="https://api.nuget.org/packages/microsoft.chakracore.1.8.0.nupkg">https://api.nuget.org/packages/microsoft.chakracore.1.8.0.nupkg</a></p>
<p>Path to dependency file: /Nuget_VSIX_Project/Nuget_VSIX_Project.csproj</p>
<p>Path to vulnerable library: /home/wss-scanner/.nuget/packages/microsoft.chakracore/1.8.0/microsoft.chakracore.1.8.0.nupkg</p>
<p>
Dependency Hierarchy:
- :x: **microsoft.chakracore.1.8.0.nupkg** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/scm-automation-project/vsix-nuget-simple-project/commit/026ce0ebdfc0d6ab0f3595e83fecf4f2458b0d83">026ce0ebdfc0d6ab0f3595e83fecf4f2458b0d83</a></p>
</p>
<p></p>
### Vulnerability Details
<p>
A remote code execution vulnerability exists in the way that the ChakraCore scripting engine handles objects in memory, aka "Scripting Engine Memory Corruption Vulnerability." This affects Microsoft Edge, ChakraCore. This CVE ID is unique from CVE-2018-8353, CVE-2018-8355, CVE-2018-8359, CVE-2018-8371, CVE-2018-8372, CVE-2018-8373, CVE-2018-8385, CVE-2018-8389.
<p>Publish Date: 2018-08-15
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2018-8390>CVE-2018-8390</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>7.5</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: None
- User Interaction: Required
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Release Date: 2018-08-15</p>
<p>Fix Resolution: v1.10.2</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation is available for this issue
</details>
***
<p>:rescue_worker_helmet: Automatic Remediation is available for this issue.</p> | non_priority | microsoft chakracore nupkg vulnerabilities highest severity is vulnerable library microsoft chakracore nupkg chakracore is the core part of the chakra javascript engine that powers microsoft edge library home page a href path to dependency file nuget vsix project nuget vsix project csproj path to vulnerable library home wss scanner nuget packages microsoft chakracore microsoft chakracore nupkg found in head commit a href vulnerabilities cve severity cvss dependency type fixed in microsoft chakracore nupkg version remediation available high microsoft chakracore nupkg direct high microsoft chakracore nupkg direct high microsoft chakracore nupkg direct high microsoft chakracore nupkg direct high microsoft chakracore nupkg direct microsoft chakracore high microsoft chakracore nupkg direct microsoft chakracore high microsoft chakracore nupkg direct microsoft chakracore high microsoft chakracore nupkg direct high microsoft chakracore nupkg direct high microsoft chakracore nupkg direct high microsoft chakracore nupkg direct microsoft chakracore high microsoft chakracore nupkg direct high microsoft chakracore nupkg direct high microsoft chakracore nupkg direct high microsoft chakracore nupkg direct high microsoft chakracore nupkg direct high microsoft chakracore nupkg direct high microsoft chakracore nupkg direct microsoft chakracore high microsoft chakracore nupkg direct microsoft chakracore high microsoft chakracore nupkg direct microsoft chakracore high microsoft chakracore nupkg direct microsoft chakracore high microsoft chakracore nupkg direct microsoft chakracore high microsoft chakracore nupkg direct microsoft chakracore high microsoft chakracore nupkg direct high microsoft chakracore nupkg direct high microsoft chakracore nupkg direct microsoft chakracore high microsoft chakracore nupkg direct microsoft chakracore high microsoft chakracore nupkg direct high microsoft chakracore nupkg direct microsoft chakracore high microsoft chakracore nupkg direct high microsoft chakracore nupkg direct microsoft chakracore high microsoft chakracore nupkg direct microsoft chakracore high microsoft chakracore nupkg direct microsoft typescript compiler microsoft typescript msbuild microsoft azure streamanalytics cicd baristalabs baristacore chakracore win arm baristalabs baristacore chakracore win baristalabs baristacore chakracore win microsoft chakracore microsoft chakracore high microsoft chakracore nupkg direct high microsoft chakracore nupkg direct microsoft typescript compiler microsoft typescript msbuild microsoft azure streamanalytics cicd baristalabs baristacore chakracore win arm baristalabs baristacore chakracore win baristalabs baristacore chakracore win microsoft chakracore microsoft chakracore high microsoft chakracore nupkg direct high microsoft chakracore nupkg direct high microsoft chakracore nupkg direct high microsoft chakracore nupkg direct high microsoft chakracore nupkg direct high microsoft chakracore nupkg direct high microsoft chakracore nupkg direct microsoft chakracore microsoft typescript compiler microsoft typescript msbuild microsoft azure streamanalytics cicd baristalabs baristacore chakracore win arm baristalabs baristacore chakracore win baristalabs baristacore chakracore win microsoft chakracore high microsoft chakracore nupkg direct high microsoft chakracore nupkg direct high microsoft chakracore nupkg direct high microsoft chakracore nupkg direct high microsoft chakracore nupkg direct microsoft chakracore high microsoft chakracore nupkg direct microsoft chakracore high microsoft chakracore nupkg direct high microsoft chakracore nupkg direct high microsoft chakracore nupkg direct microsoft chakracore high microsoft chakracore nupkg direct high microsoft chakracore nupkg direct microsoft chakracore high microsoft chakracore nupkg direct microsoft chakracore high microsoft chakracore nupkg direct microsoft chakracore high microsoft chakracore nupkg direct microsoft chakracore high microsoft chakracore nupkg direct high microsoft chakracore nupkg direct high microsoft chakracore nupkg direct microsoft chakracore high microsoft chakracore nupkg direct microsoft chakracore high microsoft chakracore nupkg direct microsoft chakracore high microsoft chakracore nupkg direct high microsoft chakracore nupkg direct microsoft typescript compiler microsoft typescript msbuild microsoft azure streamanalytics cicd baristalabs baristacore chakracore win arm baristalabs baristacore chakracore win baristalabs baristacore chakracore win microsoft chakracore microsoft chakracore high microsoft chakracore nupkg direct microsoft chakracore high microsoft chakracore nupkg direct microsoft azure streamanalytics cicd baristalabs baristacore chakracore win arm baristalabs baristacore chakracore win baristalabs baristacore chakracore win microsoft chakracore microsoft chakracore high microsoft chakracore nupkg direct high microsoft chakracore nupkg direct high microsoft chakracore nupkg direct high microsoft chakracore nupkg direct high microsoft chakracore nupkg direct high microsoft chakracore nupkg direct microsoft chakracore high microsoft chakracore nupkg direct microsoft chakracore high microsoft chakracore nupkg direct microsoft chakracore high microsoft chakracore nupkg direct microsoft chakracore high microsoft chakracore nupkg direct high microsoft chakracore nupkg direct microsoft chakracore high microsoft chakracore nupkg direct microsoft chakracore high microsoft chakracore nupkg direct microsoft chakracore high microsoft chakracore nupkg direct high microsoft chakracore nupkg direct microsoft chakracore high microsoft chakracore nupkg direct microsoft chakracore microsoft typescript compiler microsoft typescript msbuild microsoft azure streamanalytics cicd baristalabs baristacore chakracore win arm baristalabs baristacore chakracore win baristalabs baristacore chakracore win microsoft chakracore high microsoft chakracore nupkg direct high microsoft chakracore nupkg direct high microsoft chakracore nupkg direct microsoft chakracore high microsoft chakracore nupkg direct high microsoft chakracore nupkg direct high microsoft chakracore nupkg direct microsoft chakracore high microsoft chakracore nupkg direct microsoft chakracore high microsoft chakracore nupkg direct high microsoft chakracore nupkg direct high microsoft chakracore nupkg direct high microsoft chakracore nupkg direct high microsoft chakracore nupkg direct high microsoft chakracore nupkg direct microsoft chakracore high microsoft chakracore nupkg direct microsoft chakracore high microsoft chakracore nupkg direct microsoft chakracore high microsoft chakracore nupkg direct high microsoft chakracore nupkg direct microsoft chakracore high microsoft chakracore nupkg direct high microsoft chakracore nupkg direct microsoft chakracore high microsoft chakracore nupkg direct high microsoft chakracore nupkg direct microsoft chakracore high microsoft chakracore nupkg direct high microsoft chakracore nupkg direct microsoft chakracore high microsoft chakracore nupkg direct high microsoft chakracore nupkg direct microsoft chakracore high microsoft chakracore nupkg direct microsoft chakracore high microsoft chakracore nupkg direct high microsoft chakracore nupkg direct high microsoft chakracore nupkg direct microsoft chakracore high microsoft chakracore nupkg direct high microsoft chakracore nupkg direct high microsoft chakracore nupkg direct microsoft chakracore high microsoft chakracore nupkg direct microsoft chakracore high microsoft chakracore nupkg direct high microsoft chakracore nupkg direct high microsoft chakracore nupkg direct microsoft typescript msbuild baristalabs baristacore chakracore win arm baristalabs baristacore chakracore win baristalabs baristacore chakracore win microsoft chakracore microsoft chakracore high microsoft chakracore nupkg direct microsoft chakracore high microsoft chakracore nupkg direct high microsoft chakracore nupkg direct microsoft chakracore high microsoft chakracore nupkg direct high microsoft chakracore nupkg direct microsoft chakracore high microsoft chakracore nupkg direct high microsoft chakracore nupkg direct high microsoft chakracore nupkg direct high microsoft chakracore nupkg direct high microsoft chakracore nupkg direct high microsoft chakracore nupkg direct high microsoft chakracore nupkg direct microsoft chakracore high microsoft chakracore nupkg direct microsoft chakracore high microsoft chakracore nupkg direct microsoft chakracore high microsoft chakracore nupkg direct high microsoft chakracore nupkg direct microsoft chakracore high microsoft chakracore nupkg direct microsoft chakracore high microsoft chakracore nupkg direct high microsoft chakracore nupkg direct high microsoft chakracore nupkg direct high microsoft chakracore nupkg direct high microsoft chakracore nupkg direct microsoft chakracore high microsoft chakracore nupkg direct microsoft chakracore microsoft typescript compiler microsoft typescript msbuild baristalabs baristacore chakracore win arm baristalabs baristacore chakracore win microsoft chakracore high microsoft chakracore nupkg direct microsoft chakracore high microsoft chakracore nupkg direct high microsoft chakracore nupkg direct high microsoft chakracore nupkg direct microsoft chakracore high microsoft chakracore nupkg direct microsoft chakracore high microsoft chakracore nupkg direct microsoft chakracore high microsoft chakracore nupkg direct high microsoft chakracore nupkg direct microsoft chakracore high microsoft chakracore nupkg direct microsoft chakracore high microsoft chakracore nupkg direct microsoft chakracore high microsoft chakracore nupkg direct high microsoft chakracore nupkg direct microsoft chakracore high microsoft chakracore nupkg direct high microsoft chakracore nupkg direct microsoft chakracore high microsoft chakracore nupkg direct medium microsoft chakracore nupkg direct medium microsoft chakracore nupkg direct microsoft chakracore medium microsoft chakracore nupkg direct microsoft chakracore medium microsoft chakracore nupkg direct microsoft chakracore medium microsoft chakracore nupkg direct medium microsoft chakracore nupkg direct medium microsoft chakracore nupkg direct details partial details vulnerabilities are displayed below due to a content size limitation in github to view information on the remaining vulnerabilities navigate to the mend application cve vulnerable library microsoft chakracore nupkg chakracore is the core part of the chakra javascript engine that powers microsoft edge library home page a href path to dependency file nuget vsix project nuget vsix project csproj path to vulnerable library home wss scanner nuget packages microsoft chakracore microsoft chakracore nupkg dependency hierarchy x microsoft chakracore nupkg vulnerable library found in head commit a href vulnerability details a remote code execution vulnerability exists in the way that the chakracore scripting engine handles objects in memory aka scripting engine memory corruption vulnerability this affects chakracore 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 release date fix resolution rescue worker helmet automatic remediation is available for this issue cve vulnerable library microsoft chakracore nupkg chakracore is the core part of the chakra javascript engine that powers microsoft edge library home page a href path to dependency file nuget vsix project nuget vsix project csproj path to vulnerable library home wss scanner nuget packages microsoft chakracore microsoft chakracore nupkg dependency hierarchy x microsoft chakracore nupkg vulnerable library found in head commit a href vulnerability details a remote code execution vulnerability exists in the way that the chakracore scripting engine handles objects in memory aka scripting engine memory corruption vulnerability 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 release date fix resolution rescue worker helmet automatic remediation is available for this issue cve vulnerable library microsoft chakracore nupkg chakracore is the core part of the chakra javascript engine that powers microsoft edge library home page a href path to dependency file nuget vsix project nuget vsix project csproj path to vulnerable library home wss scanner nuget packages microsoft chakracore microsoft chakracore nupkg dependency hierarchy x microsoft chakracore nupkg vulnerable library found in head commit a href vulnerability details chakra scripting engine memory corruption vulnerability this cve id is unique from cve publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity 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 release date fix resolution rescue worker helmet automatic remediation is available for this issue cve vulnerable library microsoft chakracore nupkg chakracore is the core part of the chakra javascript engine that powers microsoft edge library home page a href path to dependency file nuget vsix project nuget vsix project csproj path to vulnerable library home wss scanner nuget packages microsoft chakracore microsoft chakracore nupkg dependency hierarchy x microsoft chakracore nupkg vulnerable library found in head commit a href vulnerability details a vulnerability exists in microsoft chakra jit server aka scripting engine elevation of privileged vulnerability 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 release date fix resolution rescue worker helmet automatic remediation is available for this issue cve vulnerable library microsoft chakracore nupkg chakracore is the core part of the chakra javascript engine that powers microsoft edge library home page a href path to dependency file nuget vsix project nuget vsix project csproj path to vulnerable library home wss scanner nuget packages microsoft chakracore microsoft chakracore nupkg dependency hierarchy x microsoft chakracore nupkg vulnerable library found in head commit a href vulnerability details a remote code execution vulnerability exists in the way that the chakra scripting engine handles objects in memory in microsoft edge aka chakra scripting engine memory corruption vulnerability this cve id is unique from cve cve cve cve cve cve cve 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 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 release date fix resolution microsoft chakracore rescue worker helmet automatic remediation is available for this issue cve vulnerable library microsoft chakracore nupkg chakracore is the core part of the chakra javascript engine that powers microsoft edge library home page a href path to dependency file nuget vsix project nuget vsix project csproj path to vulnerable library home wss scanner nuget packages microsoft chakracore microsoft chakracore nupkg dependency hierarchy x microsoft chakracore nupkg vulnerable library found in head commit a href vulnerability details a remote code execution vulnerability exists in the way that the chakra scripting engine handles objects in memory in microsoft edge aka chakra scripting engine memory corruption vulnerability this cve id is unique from cve cve 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 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 release date fix resolution microsoft chakracore rescue worker helmet automatic remediation is available for this issue cve vulnerable library microsoft chakracore nupkg chakracore is the core part of the chakra javascript engine that powers microsoft edge library home page a href path to dependency file nuget vsix project nuget vsix project csproj path to vulnerable library home wss scanner nuget packages microsoft chakracore microsoft chakracore nupkg dependency hierarchy x microsoft chakracore nupkg vulnerable library found in head commit a href vulnerability details an information disclosure vulnerability exists when chakra improperly discloses the contents of its memory which could provide an attacker with information to further compromise the user’s computer or data to exploit the vulnerability an attacker must know the memory address of where the object was created the update addresses the vulnerability by changing the way certain functions handle objects in memory aka scripting engine information disclosure vulnerability publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact high integrity impact none availability impact none for more information on scores click a href suggested fix type upgrade version release date fix resolution microsoft chakracore rescue worker helmet automatic remediation is available for this issue cve vulnerable library microsoft chakracore nupkg chakracore is the core part of the chakra javascript engine that powers microsoft edge library home page a href path to dependency file nuget vsix project nuget vsix project csproj path to vulnerable library home wss scanner nuget packages microsoft chakracore microsoft chakracore nupkg dependency hierarchy x microsoft chakracore nupkg vulnerable library found in head commit a href vulnerability details a remote code execution vulnerability exists in the way that the chakracore scripting engine handles objects in memory aka scripting engine memory corruption vulnerability this affects microsoft edge chakracore this cve id is unique from cve cve cve cve cve cve cve 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 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 release date fix resolution rescue worker helmet automatic remediation is available for this issue rescue worker helmet automatic remediation is available for this issue | 0 |
1,174 | 3,414,436,837 | IssuesEvent | 2015-12-07 06:37:44 | daemonraco/toobasic | https://api.github.com/repos/daemonraco/toobasic | closed | Routes for Services | Core Logic enhancement Services | ## What to do
Add a mechanism to allow and analyze routes (clean urls) for servicies. | 1.0 | Routes for Services - ## What to do
Add a mechanism to allow and analyze routes (clean urls) for servicies. | non_priority | routes for services what to do add a mechanism to allow and analyze routes clean urls for servicies | 0 |
258,676 | 22,338,821,471 | IssuesEvent | 2022-06-14 21:28:53 | GoogleForCreators/web-stories-wp | https://api.github.com/repos/GoogleForCreators/web-stories-wp | opened | Page Attachment clashing with Shopping Attachment | Type: Bug P1 Needs Tests Pod: WP Group: Page Attachment Group: Shopping | <!--
NOTE: For help requests, support questions, or general feedback,
please use the WordPress.org forums instead: https://wordpress.org/support/plugin/web-stories/
-->
## Bug Description
<!-- A clear and concise description of what the bug is. -->
There's a couple of conflicts between the page attachment (aka outlink) and the shopping attachment, most notably because right now they use some of the same components.
1. When you add a page attachment to a page and then add shopping products, when previewing the story on the frontend you get both CTAs. This is invalid AMP. Only the shopping attachment should be shown.
2. When you add a page attachment to a page and then add shopping products, the existing page attachment CTA text is used for the shopping CTA, which is a weird combo. These should be two separate texts.
## Expected Behaviour
<!-- Please describe clearly and concisely what the expected behaviour should be. -->
* No duplicate CTAs on the frontend
* No AMP validation errors
* No shared CTA text
## Steps to Reproduce
<!-- Please provide detailed steps on how to reproduce the bug. -->
See description above
## Screenshots
<!--
If applicable, please add screenshots to help explain your problem.
Bonus points for videos!
-->
## Additional Context
<!-- Please complete the following information. -->
- Plugin Version: 1.22.0-alpha
- WordPress Version: 6.0
- Operating System: macOS
- Browser: Chrome v102
| 1.0 | Page Attachment clashing with Shopping Attachment - <!--
NOTE: For help requests, support questions, or general feedback,
please use the WordPress.org forums instead: https://wordpress.org/support/plugin/web-stories/
-->
## Bug Description
<!-- A clear and concise description of what the bug is. -->
There's a couple of conflicts between the page attachment (aka outlink) and the shopping attachment, most notably because right now they use some of the same components.
1. When you add a page attachment to a page and then add shopping products, when previewing the story on the frontend you get both CTAs. This is invalid AMP. Only the shopping attachment should be shown.
2. When you add a page attachment to a page and then add shopping products, the existing page attachment CTA text is used for the shopping CTA, which is a weird combo. These should be two separate texts.
## Expected Behaviour
<!-- Please describe clearly and concisely what the expected behaviour should be. -->
* No duplicate CTAs on the frontend
* No AMP validation errors
* No shared CTA text
## Steps to Reproduce
<!-- Please provide detailed steps on how to reproduce the bug. -->
See description above
## Screenshots
<!--
If applicable, please add screenshots to help explain your problem.
Bonus points for videos!
-->
## Additional Context
<!-- Please complete the following information. -->
- Plugin Version: 1.22.0-alpha
- WordPress Version: 6.0
- Operating System: macOS
- Browser: Chrome v102
| non_priority | page attachment clashing with shopping attachment note for help requests support questions or general feedback please use the wordpress org forums instead bug description there s a couple of conflicts between the page attachment aka outlink and the shopping attachment most notably because right now they use some of the same components when you add a page attachment to a page and then add shopping products when previewing the story on the frontend you get both ctas this is invalid amp only the shopping attachment should be shown when you add a page attachment to a page and then add shopping products the existing page attachment cta text is used for the shopping cta which is a weird combo these should be two separate texts expected behaviour no duplicate ctas on the frontend no amp validation errors no shared cta text steps to reproduce see description above screenshots if applicable please add screenshots to help explain your problem bonus points for videos additional context plugin version alpha wordpress version operating system macos browser chrome | 0 |
23,623 | 10,926,954,709 | IssuesEvent | 2019-11-22 15:43:17 | finnessyj/mage-android-sdk | https://api.github.com/repos/finnessyj/mage-android-sdk | opened | CVE-2018-12023 (High) detected in jackson-databind-2.9.5.jar | security vulnerability | ## CVE-2018-12023 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>jackson-databind-2.9.5.jar</b></p></summary>
<p>General data-binding functionality for Jackson: works on core streaming API</p>
<p>Library home page: <a href="http://github.com/FasterXML/jackson">http://github.com/FasterXML/jackson</a></p>
<p>Path to dependency file: /tmp/ws-scm/mage-android-sdk/sdk/build.gradle</p>
<p>Path to vulnerable library: /mage-android-sdk/sdk/build.gradle</p>
<p>
Dependency Hierarchy:
- :x: **jackson-databind-2.9.5.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/finnessyj/mage-android-sdk/commit/3a47c9ef0bf1956fdf0f16c83fcc74755121cd8d">3a47c9ef0bf1956fdf0f16c83fcc74755121cd8d</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 FasterXML jackson-databind prior to 2.7.9.4, 2.8.11.2, and 2.9.6. When Default Typing is enabled (either globally or for a specific property), the service has the Oracle JDBC jar in the classpath, and an attacker can provide an LDAP service to access, it is possible to make the service execute a malicious payload.
<p>Publish Date: 2019-03-21
<p>URL: <a href=https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-12023>CVE-2018-12023</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: None
- User Interaction: 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-12022">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-12022</a></p>
<p>Release Date: 2019-03-21</p>
<p>Fix Resolution: 2.7.9.4, 2.8.11.2, 2.9.6</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":false,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"Java","groupId":"com.fasterxml.jackson.core","packageName":"jackson-databind","packageVersion":"2.9.5","isTransitiveDependency":false,"dependencyTree":"com.fasterxml.jackson.core:jackson-databind:2.9.5","isMinimumFixVersionAvailable":true,"minimumFixVersion":"2.7.9.4, 2.8.11.2, 2.9.6"}],"vulnerabilityIdentifier":"CVE-2018-12023","vulnerabilityDetails":"An issue was discovered in FasterXML jackson-databind prior to 2.7.9.4, 2.8.11.2, and 2.9.6. When Default Typing is enabled (either globally or for a specific property), the service has the Oracle JDBC jar in the classpath, and an attacker can provide an LDAP service to access, it is possible to make the service execute a malicious payload.","vulnerabilityUrl":"https://cve.mitre.org/cgi-bin/cvename.cgi?name\u003dCVE-2018-12023","cvss3Severity":"high","cvss3Score":"7.5","cvss3Metrics":{"A":"High","AC":"High","PR":"None","S":"Unchanged","C":"High","UI":"Required","AV":"Network","I":"High"},"extraData":{}}</REMEDIATE> --> | True | CVE-2018-12023 (High) detected in jackson-databind-2.9.5.jar - ## CVE-2018-12023 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>jackson-databind-2.9.5.jar</b></p></summary>
<p>General data-binding functionality for Jackson: works on core streaming API</p>
<p>Library home page: <a href="http://github.com/FasterXML/jackson">http://github.com/FasterXML/jackson</a></p>
<p>Path to dependency file: /tmp/ws-scm/mage-android-sdk/sdk/build.gradle</p>
<p>Path to vulnerable library: /mage-android-sdk/sdk/build.gradle</p>
<p>
Dependency Hierarchy:
- :x: **jackson-databind-2.9.5.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/finnessyj/mage-android-sdk/commit/3a47c9ef0bf1956fdf0f16c83fcc74755121cd8d">3a47c9ef0bf1956fdf0f16c83fcc74755121cd8d</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 FasterXML jackson-databind prior to 2.7.9.4, 2.8.11.2, and 2.9.6. When Default Typing is enabled (either globally or for a specific property), the service has the Oracle JDBC jar in the classpath, and an attacker can provide an LDAP service to access, it is possible to make the service execute a malicious payload.
<p>Publish Date: 2019-03-21
<p>URL: <a href=https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-12023>CVE-2018-12023</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: None
- User Interaction: 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-12022">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-12022</a></p>
<p>Release Date: 2019-03-21</p>
<p>Fix Resolution: 2.7.9.4, 2.8.11.2, 2.9.6</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":false,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"Java","groupId":"com.fasterxml.jackson.core","packageName":"jackson-databind","packageVersion":"2.9.5","isTransitiveDependency":false,"dependencyTree":"com.fasterxml.jackson.core:jackson-databind:2.9.5","isMinimumFixVersionAvailable":true,"minimumFixVersion":"2.7.9.4, 2.8.11.2, 2.9.6"}],"vulnerabilityIdentifier":"CVE-2018-12023","vulnerabilityDetails":"An issue was discovered in FasterXML jackson-databind prior to 2.7.9.4, 2.8.11.2, and 2.9.6. When Default Typing is enabled (either globally or for a specific property), the service has the Oracle JDBC jar in the classpath, and an attacker can provide an LDAP service to access, it is possible to make the service execute a malicious payload.","vulnerabilityUrl":"https://cve.mitre.org/cgi-bin/cvename.cgi?name\u003dCVE-2018-12023","cvss3Severity":"high","cvss3Score":"7.5","cvss3Metrics":{"A":"High","AC":"High","PR":"None","S":"Unchanged","C":"High","UI":"Required","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 tmp ws scm mage android sdk sdk build gradle path to vulnerable library mage android sdk sdk build gradle dependency hierarchy x jackson databind jar vulnerable library found in head commit a href vulnerability details an issue was discovered in fasterxml jackson databind prior to and when default typing is enabled either globally or for a specific property the service has the oracle jdbc jar in the classpath and an attacker can provide an ldap service to access it is possible to make the service execute a malicious payload publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity high privileges required none user interaction required scope unchanged impact metrics confidentiality impact high integrity impact high availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution isopenpronvulnerability false ispackagebased true isdefaultbranch true packages vulnerabilityidentifier cve vulnerabilitydetails an issue was discovered in fasterxml jackson databind prior to and when default typing is enabled either globally or for a specific property the service has the oracle jdbc jar in the classpath and an attacker can provide an ldap service to access it is possible to make the service execute a malicious payload vulnerabilityurl | 0 |
85,239 | 24,545,628,121 | IssuesEvent | 2022-10-12 08:34:40 | GoogleCloudPlatform/fda-mystudies | https://api.github.com/repos/GoogleCloudPlatform/fda-mystudies | closed | [VAPT] [SB] Studies > UI Issue in the 'Filter by apps' dropdown | Bug P2 Study builder Process: Fixed Process: Tested QA Process: Tested dev | Studies > UI Issue in the 'Filter by apps' dropdown i.e., There is no outline border getting displayed in the dropdown and also no separtaion of all apps and app values
| 1.0 | [VAPT] [SB] Studies > UI Issue in the 'Filter by apps' dropdown - Studies > UI Issue in the 'Filter by apps' dropdown i.e., There is no outline border getting displayed in the dropdown and also no separtaion of all apps and app values
| non_priority | studies ui issue in the filter by apps dropdown studies ui issue in the filter by apps dropdown i e there is no outline border getting displayed in the dropdown and also no separtaion of all apps and app values | 0 |
122,294 | 10,218,574,865 | IssuesEvent | 2019-08-15 16:16:30 | mozilla/iris_firefox | https://api.github.com/repos/mozilla/iris_firefox | closed | Fix checks for Yandex and Baidu search code tests | regression test case | Both of these test are failing in the check for search on a selected text. The test is trying to right click the focus_text.png after it has been highlighted. The tests both need to have patterns created for all of the locales each supports. Create patterns for 'focus_text_selected.png.' and adjust the code to right click that pattern instead. Please see default_search_code_google.py for example. The existing image the Google test uses doesn't seem to work with the locales needed in the Baidu and Yandex tests.
Note: the Yandex test is currently blocked by a problem with setting the region. | 1.0 | Fix checks for Yandex and Baidu search code tests - Both of these test are failing in the check for search on a selected text. The test is trying to right click the focus_text.png after it has been highlighted. The tests both need to have patterns created for all of the locales each supports. Create patterns for 'focus_text_selected.png.' and adjust the code to right click that pattern instead. Please see default_search_code_google.py for example. The existing image the Google test uses doesn't seem to work with the locales needed in the Baidu and Yandex tests.
Note: the Yandex test is currently blocked by a problem with setting the region. | non_priority | fix checks for yandex and baidu search code tests both of these test are failing in the check for search on a selected text the test is trying to right click the focus text png after it has been highlighted the tests both need to have patterns created for all of the locales each supports create patterns for focus text selected png and adjust the code to right click that pattern instead please see default search code google py for example the existing image the google test uses doesn t seem to work with the locales needed in the baidu and yandex tests note the yandex test is currently blocked by a problem with setting the region | 0 |
19,012 | 26,432,539,790 | IssuesEvent | 2023-01-15 01:00:44 | hensm/fx_cast-compat | https://api.github.com/repos/hensm/fx_cast-compat | reopened | [compat] Sportsnet Now | compat-compatible compat | **App name:** Sportsnet Now
**App URL:** https://now.sportsnet.ca/
**Issues:**
No cast button on the player when all sites added to whitelist. Uses NeuLion/Endeavor streaming. Same streaming service as NBA/UFC | True | [compat] Sportsnet Now - **App name:** Sportsnet Now
**App URL:** https://now.sportsnet.ca/
**Issues:**
No cast button on the player when all sites added to whitelist. Uses NeuLion/Endeavor streaming. Same streaming service as NBA/UFC | non_priority | sportsnet now app name sportsnet now app url issues no cast button on the player when all sites added to whitelist uses neulion endeavor streaming same streaming service as nba ufc | 0 |
228,165 | 17,421,381,798 | IssuesEvent | 2021-08-04 02:03:00 | flameshot-org/flameshot | https://api.github.com/repos/flameshot-org/flameshot | closed | OSX -> macOS | Documentation Enhancement MacOS | OSX was renamed to macOS. (Or you can say: OSXI)
It would be great if the labels could be renamed.
Thanks | 1.0 | OSX -> macOS - OSX was renamed to macOS. (Or you can say: OSXI)
It would be great if the labels could be renamed.
Thanks | non_priority | osx macos osx was renamed to macos or you can say osxi it would be great if the labels could be renamed thanks | 0 |
61,354 | 8,514,980,736 | IssuesEvent | 2018-10-31 20:10:39 | aws-amplify/amplify-js | https://api.github.com/repos/aws-amplify/amplify-js | closed | Small issue in your documentation with the Jekyll Page Generator. | documentation | BUG
Small issue in your documentation with the Jekyll Page Generator.
AWS Amplify Authentication module exposes set of APIs to be used in any JavaScript framework. Please check [AWS Amplify API Reference]({%if jekyll.environment == 'production'%}{{site.amplify.baseurl}}{%endif%}/api/classes/authclass.html) for full API list. | 1.0 | Small issue in your documentation with the Jekyll Page Generator. - BUG
Small issue in your documentation with the Jekyll Page Generator.
AWS Amplify Authentication module exposes set of APIs to be used in any JavaScript framework. Please check [AWS Amplify API Reference]({%if jekyll.environment == 'production'%}{{site.amplify.baseurl}}{%endif%}/api/classes/authclass.html) for full API list. | non_priority | small issue in your documentation with the jekyll page generator bug small issue in your documentation with the jekyll page generator aws amplify authentication module exposes set of apis to be used in any javascript framework please check if jekyll environment production site amplify baseurl endif api classes authclass html for full api list | 0 |
163,061 | 25,746,490,486 | IssuesEvent | 2022-12-08 10:11:07 | microsoft/vscode | https://api.github.com/repos/microsoft/vscode | closed | Modified files not showing in source control tab | git *as-designed new release | Type: <b>Bug</b>
_Actual_:
Modified files are no longer listed in the 'Source Control Repositories' tab. Git extension is active and all other aspects working as expected (e.g. markers M/D/U in the 'Explorer' tab). The header in the 'SCR' tab is also showing the number of modified files in the current branch. Hitting refresh doesn't effect the issue. This issue persists when running VSCode without extensions. It doesn't depend on the repository - it occurs for new and existing repositories. It occurs when running VS Code under Windows 11 native and in WSL2 remote mode.
_Expected_:
Modified files showing in 'SCR' tab.
_Steps_:
* Open any existing local git repo or create new one
* Create/modify files
* Open 'Source Control Repositories' tab
* -> Modified files not showing.
VS Code version: Code 1.74.0 (5235c6bb189b60b01b1f49062f4ffa42384f8c91, 2022-12-05T16:38:16.075Z)
OS version: Windows_NT x64 10.0.22621
Modes:
Sandboxed: No
Remote OS version: Linux x64 5.10.102.1-microsoft-standard-WSL2
<details>
<summary>System Info</summary>
|Item|Value|
|---|---|
|CPUs|Intel(R) Core(TM) i7-10750H CPU @ 2.60GHz (12 x 2592)|
|GPU Status|2d_canvas: enabled<br>canvas_oop_rasterization: disabled_off<br>direct_rendering_display_compositor: disabled_off_ok<br>gpu_compositing: enabled<br>multiple_raster_threads: enabled_on<br>opengl: enabled_on<br>rasterization: enabled<br>raw_draw: disabled_off_ok<br>skia_renderer: enabled_on<br>video_decode: enabled<br>video_encode: enabled<br>vulkan: disabled_off<br>webgl: enabled<br>webgl2: enabled<br>webgpu: disabled_off|
|Load (avg)|undefined|
|Memory (System)|31.76GB (17.71GB free)|
|Process Argv|--file-uri vscode-remote://wsl%2Bubuntu-20.04/home/xxxx/xxxx/xxx.code-workspace --crash-reporter-id f2b2401f-3d62-452e-9799-3b88b4412d88|
|Screen Reader|no|
|VM|0%|
|Item|Value|
|---|---|
|Remote|WSL: Ubuntu-20.04|
|OS|Linux x64 5.10.102.1-microsoft-standard-WSL2|
|CPUs|Intel(R) Core(TM) i7-10750H CPU @ 2.60GHz (12 x 2592)|
|Memory (System)|15.50GB (13.87GB free)|
|VM|0%|
</details>
<!-- generated by issue reporter -->
| 1.0 | Modified files not showing in source control tab - Type: <b>Bug</b>
_Actual_:
Modified files are no longer listed in the 'Source Control Repositories' tab. Git extension is active and all other aspects working as expected (e.g. markers M/D/U in the 'Explorer' tab). The header in the 'SCR' tab is also showing the number of modified files in the current branch. Hitting refresh doesn't effect the issue. This issue persists when running VSCode without extensions. It doesn't depend on the repository - it occurs for new and existing repositories. It occurs when running VS Code under Windows 11 native and in WSL2 remote mode.
_Expected_:
Modified files showing in 'SCR' tab.
_Steps_:
* Open any existing local git repo or create new one
* Create/modify files
* Open 'Source Control Repositories' tab
* -> Modified files not showing.
VS Code version: Code 1.74.0 (5235c6bb189b60b01b1f49062f4ffa42384f8c91, 2022-12-05T16:38:16.075Z)
OS version: Windows_NT x64 10.0.22621
Modes:
Sandboxed: No
Remote OS version: Linux x64 5.10.102.1-microsoft-standard-WSL2
<details>
<summary>System Info</summary>
|Item|Value|
|---|---|
|CPUs|Intel(R) Core(TM) i7-10750H CPU @ 2.60GHz (12 x 2592)|
|GPU Status|2d_canvas: enabled<br>canvas_oop_rasterization: disabled_off<br>direct_rendering_display_compositor: disabled_off_ok<br>gpu_compositing: enabled<br>multiple_raster_threads: enabled_on<br>opengl: enabled_on<br>rasterization: enabled<br>raw_draw: disabled_off_ok<br>skia_renderer: enabled_on<br>video_decode: enabled<br>video_encode: enabled<br>vulkan: disabled_off<br>webgl: enabled<br>webgl2: enabled<br>webgpu: disabled_off|
|Load (avg)|undefined|
|Memory (System)|31.76GB (17.71GB free)|
|Process Argv|--file-uri vscode-remote://wsl%2Bubuntu-20.04/home/xxxx/xxxx/xxx.code-workspace --crash-reporter-id f2b2401f-3d62-452e-9799-3b88b4412d88|
|Screen Reader|no|
|VM|0%|
|Item|Value|
|---|---|
|Remote|WSL: Ubuntu-20.04|
|OS|Linux x64 5.10.102.1-microsoft-standard-WSL2|
|CPUs|Intel(R) Core(TM) i7-10750H CPU @ 2.60GHz (12 x 2592)|
|Memory (System)|15.50GB (13.87GB free)|
|VM|0%|
</details>
<!-- generated by issue reporter -->
| non_priority | modified files not showing in source control tab type bug actual modified files are no longer listed in the source control repositories tab git extension is active and all other aspects working as expected e g markers m d u in the explorer tab the header in the scr tab is also showing the number of modified files in the current branch hitting refresh doesn t effect the issue this issue persists when running vscode without extensions it doesn t depend on the repository it occurs for new and existing repositories it occurs when running vs code under windows native and in remote mode expected modified files showing in scr tab steps open any existing local git repo or create new one create modify files open source control repositories tab modified files not showing vs code version code os version windows nt modes sandboxed no remote os version linux microsoft standard system info item value cpus intel r core tm cpu x gpu status canvas enabled canvas oop rasterization disabled off direct rendering display compositor disabled off ok gpu compositing enabled multiple raster threads enabled on opengl enabled on rasterization enabled raw draw disabled off ok skia renderer enabled on video decode enabled video encode enabled vulkan disabled off webgl enabled enabled webgpu disabled off load avg undefined memory system free process argv file uri vscode remote wsl home xxxx xxxx xxx code workspace crash reporter id screen reader no vm item value remote wsl ubuntu os linux microsoft standard cpus intel r core tm cpu x memory system free vm | 0 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.