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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
115,174 | 9,782,457,194 | IssuesEvent | 2019-06-07 23:47:58 | jruby/jruby | https://api.github.com/repos/jruby/jruby | opened | Inadequate testing of JMX features | beginner help wanted java integration tests | We don't have any tests that confirm the JMX endpoints we expose are working. As an example, the remote backtrace generation broke in JRuby 9.2.7.0 when we fixed how exception backtraces are created. I have fixed that in d2875a427a, but without tests obviously this and the rest of our mbeans are at risk of regressing again.
This would be a good one for external contributors. You can use Ruby to access JMX directly, or use @enebo's jmx gem for a nicer interface. | 1.0 | Inadequate testing of JMX features - We don't have any tests that confirm the JMX endpoints we expose are working. As an example, the remote backtrace generation broke in JRuby 9.2.7.0 when we fixed how exception backtraces are created. I have fixed that in d2875a427a, but without tests obviously this and the rest of our mbeans are at risk of regressing again.
This would be a good one for external contributors. You can use Ruby to access JMX directly, or use @enebo's jmx gem for a nicer interface. | non_priority | inadequate testing of jmx features we don t have any tests that confirm the jmx endpoints we expose are working as an example the remote backtrace generation broke in jruby when we fixed how exception backtraces are created i have fixed that in but without tests obviously this and the rest of our mbeans are at risk of regressing again this would be a good one for external contributors you can use ruby to access jmx directly or use enebo s jmx gem for a nicer interface | 0 |
377,730 | 26,267,792,027 | IssuesEvent | 2023-01-06 14:12:55 | ynikitenko/yarsync | https://api.github.com/repos/ynikitenko/yarsync | closed | improve github-pages | documentation help wanted | - center the top button "View On GitHub" vertically,
- create navigation between pages?
- use hacker theme instead of midnight? Decide on its readability first. At the moment [fonts are unreadable](https://github.com/pages-themes/hacker/issues/112). Green sections look awesome, but maybe white is less distracting and better for reading a manual?
- can't link to document sections (including manual and inter-manual links),
- can't copy code with a click (as it is done on GitHub); not essential, but nice to have,
- add an arrow "to the top of the page" at the bottom?
- manual still looks a bit better in the terminal. | 1.0 | improve github-pages - - center the top button "View On GitHub" vertically,
- create navigation between pages?
- use hacker theme instead of midnight? Decide on its readability first. At the moment [fonts are unreadable](https://github.com/pages-themes/hacker/issues/112). Green sections look awesome, but maybe white is less distracting and better for reading a manual?
- can't link to document sections (including manual and inter-manual links),
- can't copy code with a click (as it is done on GitHub); not essential, but nice to have,
- add an arrow "to the top of the page" at the bottom?
- manual still looks a bit better in the terminal. | non_priority | improve github pages center the top button view on github vertically create navigation between pages use hacker theme instead of midnight decide on its readability first at the moment green sections look awesome but maybe white is less distracting and better for reading a manual can t link to document sections including manual and inter manual links can t copy code with a click as it is done on github not essential but nice to have add an arrow to the top of the page at the bottom manual still looks a bit better in the terminal | 0 |
150,719 | 23,702,275,602 | IssuesEvent | 2022-08-29 20:13:56 | practice-uffs/programa | https://api.github.com/repos/practice-uffs/programa | opened | Postar novo membro nas redes sociais | ajuda:con-design ajuda:ger-aux | Criar imagem base como a feita para os demais bolsistas.
Revisar texto de apresentação [(linha 59)](https://docs.google.com/spreadsheets/d/15kGGrER8UTGQhPIvGm2jHhs3pEO6f7gqISZgRyqpMKE/edit#gid=745178717) | 1.0 | Postar novo membro nas redes sociais - Criar imagem base como a feita para os demais bolsistas.
Revisar texto de apresentação [(linha 59)](https://docs.google.com/spreadsheets/d/15kGGrER8UTGQhPIvGm2jHhs3pEO6f7gqISZgRyqpMKE/edit#gid=745178717) | non_priority | postar novo membro nas redes sociais criar imagem base como a feita para os demais bolsistas revisar texto de apresentação | 0 |
317,619 | 23,680,847,472 | IssuesEvent | 2022-08-28 19:28:27 | orbita-center/react-dadata-box | https://api.github.com/repos/orbita-center/react-dadata-box | closed | SpecificQueryModeResponse generic into docs | documentation | SpecificQueryModeResponse generic into docs for **customActions** & **type** sync | 1.0 | SpecificQueryModeResponse generic into docs - SpecificQueryModeResponse generic into docs for **customActions** & **type** sync | non_priority | specificquerymoderesponse generic into docs specificquerymoderesponse generic into docs for customactions type sync | 0 |
26,004 | 19,560,311,598 | IssuesEvent | 2022-01-03 15:23:02 | hzi-braunschweig/SORMAS-Project | https://api.github.com/repos/hzi-braunschweig/SORMAS-Project | closed | CentralInfraSyncFacade::syncAll should run in its own DB transaction | infrastructure change s2s | ### Feature Description
The `syncAll` function of `CentralInfraSyncFacade` which pulls all infra data types we currently have.
### Problem Description
The function is currently not executed in a dedicated transactio. This means that if `loadAndStoreContinents` and `loadAndStoreSubcontinents` succeed, but `loadAndStoreCountries` does not as e.g., a country references a non existent subcontinent, nothing should end up in the DB as the provided data from central is clearly wrong.
### Proposed Change
Open a transaction and rollback on any Exception. Commit the whole infra only if everything is correct. | 1.0 | CentralInfraSyncFacade::syncAll should run in its own DB transaction - ### Feature Description
The `syncAll` function of `CentralInfraSyncFacade` which pulls all infra data types we currently have.
### Problem Description
The function is currently not executed in a dedicated transactio. This means that if `loadAndStoreContinents` and `loadAndStoreSubcontinents` succeed, but `loadAndStoreCountries` does not as e.g., a country references a non existent subcontinent, nothing should end up in the DB as the provided data from central is clearly wrong.
### Proposed Change
Open a transaction and rollback on any Exception. Commit the whole infra only if everything is correct. | non_priority | centralinfrasyncfacade syncall should run in its own db transaction feature description the syncall function of centralinfrasyncfacade which pulls all infra data types we currently have problem description the function is currently not executed in a dedicated transactio this means that if loadandstorecontinents and loadandstoresubcontinents succeed but loadandstorecountries does not as e g a country references a non existent subcontinent nothing should end up in the db as the provided data from central is clearly wrong proposed change open a transaction and rollback on any exception commit the whole infra only if everything is correct | 0 |
61,628 | 14,632,130,183 | IssuesEvent | 2020-12-23 21:33:50 | Cacti/cacti | https://api.github.com/repos/Cacti/cacti | closed | In a recent audit of core Cacti code, there were a few stored XSS issues that can be exposed. | SECURITY resolved | # Describe the bug
There are a few places in the current code where an attacker, once having gained access to the Cacti database through a SQL injection, could modify data in tables to possibly expose an stored XSS bug in Cacti.
## Expected behavior
Cacti should never allow things like this to happen.
| True | In a recent audit of core Cacti code, there were a few stored XSS issues that can be exposed. - # Describe the bug
There are a few places in the current code where an attacker, once having gained access to the Cacti database through a SQL injection, could modify data in tables to possibly expose an stored XSS bug in Cacti.
## Expected behavior
Cacti should never allow things like this to happen.
| non_priority | in a recent audit of core cacti code there were a few stored xss issues that can be exposed describe the bug there are a few places in the current code where an attacker once having gained access to the cacti database through a sql injection could modify data in tables to possibly expose an stored xss bug in cacti expected behavior cacti should never allow things like this to happen | 0 |
38,454 | 15,701,836,875 | IssuesEvent | 2021-03-26 11:46:37 | MicrosoftDocs/azure-docs | https://api.github.com/repos/MicrosoftDocs/azure-docs | closed | Need to know the ETA of one bug | command terminated with exit status=52 | DNS record propagated | Pri2 container-service/svc cxp product-bug triaged | When stopping and then starting the AKS cluster, we encounter the issue as below.
++++++++++++++
Agents are unable to resolve Kubernetes API server name. It's likely custom DNS server is not correctly configured, please see https://aka.ms/aks/private-cluster#hub-and-spoke-with-custom-dns for more information. Details: VMSSAgentPoolReconciler retry failed: {
"Category": "InternalError",
"SubCode": "LookupNoSuchHost",
"Dependency": "Microsoft.Compute/VirtualMachineScaleSet",
"OriginError": {
"code": "VMExtensionProvisioningError",
"message": "VM has reported a failure when processing extension 'vmssCSE'. Error message: \"Enable failed: failed to execute command: command terminated with exit status=52 .....
++++++++++++++
After raising the MS support ticket, this is one known issue. It’s because when we stop AKS cluster, the cluster FQDN will be removed from Azure DNS record. Next time, when we start the cluster, it needs some time to add the FQDN record. So we need to know the ETA of this bug. We are going to take this upto production , so please fix this ASAP.
Thank you for your help!
---
#### Document Details
⚠ *Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.*
* ID: f07b13b8-6b8b-57f9-7fb3-361329af08be
* Version Independent ID: d3c6ae95-654f-be23-5dcd-3c3146d5cf63
* Content: [Start and Stop an Azure Kubernetes Service (AKS) - Azure Kubernetes Service](https://docs.microsoft.com/en-us/azure/aks/start-stop-cluster)
* Content Source: [articles/aks/start-stop-cluster.md](https://github.com/MicrosoftDocs/azure-docs/blob/master/articles/aks/start-stop-cluster.md)
* Service: **container-service**
* GitHub Login: @palma21
* Microsoft Alias: **mlearned** | 1.0 | Need to know the ETA of one bug | command terminated with exit status=52 | DNS record propagated - When stopping and then starting the AKS cluster, we encounter the issue as below.
++++++++++++++
Agents are unable to resolve Kubernetes API server name. It's likely custom DNS server is not correctly configured, please see https://aka.ms/aks/private-cluster#hub-and-spoke-with-custom-dns for more information. Details: VMSSAgentPoolReconciler retry failed: {
"Category": "InternalError",
"SubCode": "LookupNoSuchHost",
"Dependency": "Microsoft.Compute/VirtualMachineScaleSet",
"OriginError": {
"code": "VMExtensionProvisioningError",
"message": "VM has reported a failure when processing extension 'vmssCSE'. Error message: \"Enable failed: failed to execute command: command terminated with exit status=52 .....
++++++++++++++
After raising the MS support ticket, this is one known issue. It’s because when we stop AKS cluster, the cluster FQDN will be removed from Azure DNS record. Next time, when we start the cluster, it needs some time to add the FQDN record. So we need to know the ETA of this bug. We are going to take this upto production , so please fix this ASAP.
Thank you for your help!
---
#### Document Details
⚠ *Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.*
* ID: f07b13b8-6b8b-57f9-7fb3-361329af08be
* Version Independent ID: d3c6ae95-654f-be23-5dcd-3c3146d5cf63
* Content: [Start and Stop an Azure Kubernetes Service (AKS) - Azure Kubernetes Service](https://docs.microsoft.com/en-us/azure/aks/start-stop-cluster)
* Content Source: [articles/aks/start-stop-cluster.md](https://github.com/MicrosoftDocs/azure-docs/blob/master/articles/aks/start-stop-cluster.md)
* Service: **container-service**
* GitHub Login: @palma21
* Microsoft Alias: **mlearned** | non_priority | need to know the eta of one bug command terminated with exit status dns record propagated when stopping and then starting the aks cluster we encounter the issue as below agents are unable to resolve kubernetes api server name it s likely custom dns server is not correctly configured please see for more information details vmssagentpoolreconciler retry failed category internalerror subcode lookupnosuchhost dependency microsoft compute virtualmachinescaleset originerror code vmextensionprovisioningerror message vm has reported a failure when processing extension vmsscse error message enable failed failed to execute command command terminated with exit status after raising the ms support ticket this is one known issue it’s because when we stop aks cluster the cluster fqdn will be removed from azure dns record next time when we start the cluster it needs some time to add the fqdn record so we need to know the eta of this bug we are going to take this upto production so please fix this asap thank you for your help 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 container service github login microsoft alias mlearned | 0 |
79,470 | 9,906,349,018 | IssuesEvent | 2019-06-27 13:41:30 | unitsofmeasurement/indriya | https://api.github.com/repos/unitsofmeasurement/indriya | closed | Move AbstractConverter to function | design task | I know this is a slightly bigger step, but as a new redefined `MultiplyConverter` interface also got defined (in place of the earlier class) in the function package, and `AbstractUnitFormat` etc. are in the format package, it is consequent here. | 1.0 | Move AbstractConverter to function - I know this is a slightly bigger step, but as a new redefined `MultiplyConverter` interface also got defined (in place of the earlier class) in the function package, and `AbstractUnitFormat` etc. are in the format package, it is consequent here. | non_priority | move abstractconverter to function i know this is a slightly bigger step but as a new redefined multiplyconverter interface also got defined in place of the earlier class in the function package and abstractunitformat etc are in the format package it is consequent here | 0 |
1,064 | 3,023,679,036 | IssuesEvent | 2015-08-01 19:15:28 | Py64/Wolves | https://api.github.com/repos/Py64/Wolves | opened | Improve registration process | doing major security-high | - Sending activation mails
- If user exists, cancel
- Check is email fine | True | Improve registration process - - Sending activation mails
- If user exists, cancel
- Check is email fine | non_priority | improve registration process sending activation mails if user exists cancel check is email fine | 0 |
38,713 | 6,690,058,897 | IssuesEvent | 2017-10-09 07:23:29 | Sylius/Sylius | https://api.github.com/repos/Sylius/Sylius | closed | Custom shipping calculators - Outdated documentation | Documentation | In custom shipping calculators (http://docs.sylius.org/en/latest/bundles/SyliusShippingBundle/custom_calculators.html#configurable-calculators), code samples are outdated :
- `DHLCalculator` class should implements `Sylius\Component\Shipping\Calculator\CalculatorInterface` instead of extending old `Sylius\Bundle\ShippingBundle\Calculator\Calculator` class
- `DHLCalculator` class should implements `getType()` method
- use declaration of `ShippingSubjectInterface` should be : `use Sylius\Component\Shipping\Model\ShipmentInterface` | 1.0 | Custom shipping calculators - Outdated documentation - In custom shipping calculators (http://docs.sylius.org/en/latest/bundles/SyliusShippingBundle/custom_calculators.html#configurable-calculators), code samples are outdated :
- `DHLCalculator` class should implements `Sylius\Component\Shipping\Calculator\CalculatorInterface` instead of extending old `Sylius\Bundle\ShippingBundle\Calculator\Calculator` class
- `DHLCalculator` class should implements `getType()` method
- use declaration of `ShippingSubjectInterface` should be : `use Sylius\Component\Shipping\Model\ShipmentInterface` | non_priority | custom shipping calculators outdated documentation in custom shipping calculators code samples are outdated dhlcalculator class should implements sylius component shipping calculator calculatorinterface instead of extending old sylius bundle shippingbundle calculator calculator class dhlcalculator class should implements gettype method use declaration of shippingsubjectinterface should be use sylius component shipping model shipmentinterface | 0 |
97,021 | 8,640,320,522 | IssuesEvent | 2018-11-24 04:03:54 | Fourdee/DietPi | https://api.github.com/repos/Fourdee/DietPi | closed | DietPi-Software | Pi-hole: Add support for blocking page | Feature Request :factory: Testing/testers required :arrow_down_small: | - At webserver conf level?
- Also outstanding issue with service not starting during boot, workaround has been applied to v6.13. | 2.0 | DietPi-Software | Pi-hole: Add support for blocking page - - At webserver conf level?
- Also outstanding issue with service not starting during boot, workaround has been applied to v6.13. | non_priority | dietpi software pi hole add support for blocking page at webserver conf level also outstanding issue with service not starting during boot workaround has been applied to | 0 |
30,524 | 24,894,587,879 | IssuesEvent | 2022-10-28 14:45:24 | DMPRoadmap/roadmap | https://api.github.com/repos/DMPRoadmap/roadmap | opened | Upgrade Rails to 7.x | infrastructure effort-large need-to-slice | We will eventually need to upgrade to 7.x.
Was pointed to this helpful guide (wish I had known about it earlier) https://www.fastruby.io/blog/rails/upgrades/upgrade-rails-6-1-to-7-0.html | 1.0 | Upgrade Rails to 7.x - We will eventually need to upgrade to 7.x.
Was pointed to this helpful guide (wish I had known about it earlier) https://www.fastruby.io/blog/rails/upgrades/upgrade-rails-6-1-to-7-0.html | non_priority | upgrade rails to x we will eventually need to upgrade to x was pointed to this helpful guide wish i had known about it earlier | 0 |
40,419 | 5,290,607,925 | IssuesEvent | 2017-02-08 20:19:54 | ansible/ansible | https://api.github.com/repos/ansible/ansible | closed | Wrong Shippable test on type(x).__name__ print | affects_2.3 bug_report test | <!---
Verify first that your issue/request is not already reported on GitHub.
Also test if the latest release, and master branch are affected too.
-->
##### ISSUE TYPE
- Bug Report
##### COMPONENT NAME
<!--- Name of the module/plugin/task/feature -->
shippable
##### ANSIBLE VERSION
<!--- Paste verbatim output from “ansible --version” between quotes below -->
```
devel
```
##### CONFIGURATION
<!---
Mention any settings you have changed/added/removed in ansible.cfg
(or using the ANSIBLE_* environment variables).
-->
##### OS / ENVIRONMENT
<!---
Mention the OS you are running Ansible from, and the OS you are
managing, or say “N/A” for anything that is not platform-specific.
-->
##### SUMMARY
<!--- Explain the problem briefly -->
Shippable failed to detect type(x) usage correctly. When using type(x).__name__ to retrieve a type, it thinks we are trying to test which type is this.
here is the incorrect build
https://app.shippable.com/runs/589add9b6ee43c0f00b55fe3/1/console
##### STEPS TO REPRODUCE
<!---
For bugs, show exactly how to reproduce the problem, using a minimal test-case.
For new features, show how the feature would be used.
-->
<!--- Paste example playbooks or commands between quotes below -->
```
self.module.fail_json(msg='TSIG update error (%s): %s' % (type(e).__name__, str(e)))
```
<!--- You can also paste gist.github.com links for larger files -->
##### EXPECTED RESULTS
<!--- What did you expect to happen when running the steps above? -->
working test
##### ACTUAL RESULTS
<!--- What actually happened? If possible run with extra verbosity (-vvvv) -->
<!--- Paste verbatim command output between quotes below -->
```
ERROR: Type comparison using type() found on line 197. Use isinstance() instead
```
| 1.0 | Wrong Shippable test on type(x).__name__ print - <!---
Verify first that your issue/request is not already reported on GitHub.
Also test if the latest release, and master branch are affected too.
-->
##### ISSUE TYPE
- Bug Report
##### COMPONENT NAME
<!--- Name of the module/plugin/task/feature -->
shippable
##### ANSIBLE VERSION
<!--- Paste verbatim output from “ansible --version” between quotes below -->
```
devel
```
##### CONFIGURATION
<!---
Mention any settings you have changed/added/removed in ansible.cfg
(or using the ANSIBLE_* environment variables).
-->
##### OS / ENVIRONMENT
<!---
Mention the OS you are running Ansible from, and the OS you are
managing, or say “N/A” for anything that is not platform-specific.
-->
##### SUMMARY
<!--- Explain the problem briefly -->
Shippable failed to detect type(x) usage correctly. When using type(x).__name__ to retrieve a type, it thinks we are trying to test which type is this.
here is the incorrect build
https://app.shippable.com/runs/589add9b6ee43c0f00b55fe3/1/console
##### STEPS TO REPRODUCE
<!---
For bugs, show exactly how to reproduce the problem, using a minimal test-case.
For new features, show how the feature would be used.
-->
<!--- Paste example playbooks or commands between quotes below -->
```
self.module.fail_json(msg='TSIG update error (%s): %s' % (type(e).__name__, str(e)))
```
<!--- You can also paste gist.github.com links for larger files -->
##### EXPECTED RESULTS
<!--- What did you expect to happen when running the steps above? -->
working test
##### ACTUAL RESULTS
<!--- What actually happened? If possible run with extra verbosity (-vvvv) -->
<!--- Paste verbatim command output between quotes below -->
```
ERROR: Type comparison using type() found on line 197. Use isinstance() instead
```
| non_priority | wrong shippable test on type x name print verify first that your issue request is not already reported on github also test if the latest release and master branch are affected too issue type bug report component name shippable ansible version devel configuration mention any settings you have changed added removed in ansible cfg or using the ansible environment variables os environment mention the os you are running ansible from and the os you are managing or say “n a” for anything that is not platform specific summary shippable failed to detect type x usage correctly when using type x name to retrieve a type it thinks we are trying to test which type is this here is the incorrect build steps to reproduce for bugs show exactly how to reproduce the problem using a minimal test case for new features show how the feature would be used self module fail json msg tsig update error s s type e name str e expected results working test actual results error type comparison using type found on line use isinstance instead | 0 |
33,129 | 12,190,112,921 | IssuesEvent | 2020-04-29 08:45:03 | lgmorand/aks-checklist | https://api.github.com/repos/lgmorand/aks-checklist | closed | CVE-2018-20822 (Medium) detected in node-sass-v4.13.1, node-sass-4.13.1.tgz | security vulnerability | ## CVE-2018-20822 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>node-sass-4.13.1.tgz</b></p></summary>
<p>
<details><summary><b>node-sass-4.13.1.tgz</b></p></summary>
<p>Wrapper around libsass</p>
<p>Library home page: <a href="https://registry.npmjs.org/node-sass/-/node-sass-4.13.1.tgz">https://registry.npmjs.org/node-sass/-/node-sass-4.13.1.tgz</a></p>
<p>Path to dependency file: /tmp/ws-scm/aks-checklist/package.json</p>
<p>Path to vulnerable library: /tmp/ws-scm/aks-checklist/node_modules/node-sass/package.json</p>
<p>
Dependency Hierarchy:
- gulp-sass-4.0.2.tgz (Root Library)
- :x: **node-sass-4.13.1.tgz** (Vulnerable Library)
</details>
<p>Found in HEAD commit: <a href="https://github.com/lgmorand/aks-checklist/commit/76621f749e31b0ae992056310004183337207c77">76621f749e31b0ae992056310004183337207c77</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
LibSass 3.5.4 allows attackers to cause a denial-of-service (uncontrolled recursion in Sass::Complex_Selector::perform in ast.hpp and Sass::Inspect::operator in inspect.cpp).
<p>Publish Date: 2019-04-23
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-20822>CVE-2018-20822</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>6.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-20822">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-20822</a></p>
<p>Release Date: 2019-08-06</p>
<p>Fix Resolution: LibSass - 3.6.0</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | CVE-2018-20822 (Medium) detected in node-sass-v4.13.1, node-sass-4.13.1.tgz - ## CVE-2018-20822 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>node-sass-4.13.1.tgz</b></p></summary>
<p>
<details><summary><b>node-sass-4.13.1.tgz</b></p></summary>
<p>Wrapper around libsass</p>
<p>Library home page: <a href="https://registry.npmjs.org/node-sass/-/node-sass-4.13.1.tgz">https://registry.npmjs.org/node-sass/-/node-sass-4.13.1.tgz</a></p>
<p>Path to dependency file: /tmp/ws-scm/aks-checklist/package.json</p>
<p>Path to vulnerable library: /tmp/ws-scm/aks-checklist/node_modules/node-sass/package.json</p>
<p>
Dependency Hierarchy:
- gulp-sass-4.0.2.tgz (Root Library)
- :x: **node-sass-4.13.1.tgz** (Vulnerable Library)
</details>
<p>Found in HEAD commit: <a href="https://github.com/lgmorand/aks-checklist/commit/76621f749e31b0ae992056310004183337207c77">76621f749e31b0ae992056310004183337207c77</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
LibSass 3.5.4 allows attackers to cause a denial-of-service (uncontrolled recursion in Sass::Complex_Selector::perform in ast.hpp and Sass::Inspect::operator in inspect.cpp).
<p>Publish Date: 2019-04-23
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-20822>CVE-2018-20822</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>6.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-20822">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-20822</a></p>
<p>Release Date: 2019-08-06</p>
<p>Fix Resolution: LibSass - 3.6.0</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_priority | cve medium detected in node sass node sass tgz cve medium severity vulnerability vulnerable libraries node sass tgz node sass tgz wrapper around libsass library home page a href path to dependency file tmp ws scm aks checklist package json path to vulnerable library tmp ws scm aks checklist node modules node sass package json dependency hierarchy gulp sass tgz root library x node sass tgz vulnerable library found in head commit a href vulnerability details libsass allows attackers to cause a denial of service uncontrolled recursion in sass complex selector perform in ast hpp and sass inspect operator in inspect cpp publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction required scope unchanged impact metrics confidentiality impact none integrity impact none availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution libsass step up your open source security game with whitesource | 0 |
149,446 | 23,477,142,204 | IssuesEvent | 2022-08-17 07:18:18 | jupyterlab/jupyterlab | https://api.github.com/repos/jupyterlab/jupyterlab | closed | Future of ui-components package: drop Blueprint; should we use Material-UI? | status:Needs Discussion tag:Design System CSS | Refs:
#6828
#6890
There's currently an ongoing discussion about the future of the `ui-components` package in Jupyterlab core:
- There's no particular reason to keep the Blueprint dependency around. We should refactor out the sparse use of it in `ui-components` and drop the dep
- This should be easy, and it will be an API breaking change, so it should maybe go in for 2.0
- Should we replace Blueprint with Material-UI?
- Pro:
- Does a lot of nice stuff that would be too much work to do on our own
- Really nice dialog boxes
- Con:
- Does a lot of complex stuff that we don't need
- May be counterproductive for accessibility stuff | 1.0 | Future of ui-components package: drop Blueprint; should we use Material-UI? - Refs:
#6828
#6890
There's currently an ongoing discussion about the future of the `ui-components` package in Jupyterlab core:
- There's no particular reason to keep the Blueprint dependency around. We should refactor out the sparse use of it in `ui-components` and drop the dep
- This should be easy, and it will be an API breaking change, so it should maybe go in for 2.0
- Should we replace Blueprint with Material-UI?
- Pro:
- Does a lot of nice stuff that would be too much work to do on our own
- Really nice dialog boxes
- Con:
- Does a lot of complex stuff that we don't need
- May be counterproductive for accessibility stuff | non_priority | future of ui components package drop blueprint should we use material ui refs there s currently an ongoing discussion about the future of the ui components package in jupyterlab core there s no particular reason to keep the blueprint dependency around we should refactor out the sparse use of it in ui components and drop the dep this should be easy and it will be an api breaking change so it should maybe go in for should we replace blueprint with material ui pro does a lot of nice stuff that would be too much work to do on our own really nice dialog boxes con does a lot of complex stuff that we don t need may be counterproductive for accessibility stuff | 0 |
317,448 | 27,238,103,567 | IssuesEvent | 2023-02-21 17:52:37 | Azure/azure-sdk-tools | https://api.github.com/repos/Azure/azure-sdk-tools | closed | [test-proxy] Consider using microsoft/reverse-proxy | Test-Proxy | https://github.com/microsoft/reverse-proxy is "a toolkit for developing high-performance HTTP reverse proxy applications".
It might be worth investigating this project, to see if it could makes sense to implement test-proxy on top of reverse-proxy. | 1.0 | [test-proxy] Consider using microsoft/reverse-proxy - https://github.com/microsoft/reverse-proxy is "a toolkit for developing high-performance HTTP reverse proxy applications".
It might be worth investigating this project, to see if it could makes sense to implement test-proxy on top of reverse-proxy. | non_priority | consider using microsoft reverse proxy is a toolkit for developing high performance http reverse proxy applications it might be worth investigating this project to see if it could makes sense to implement test proxy on top of reverse proxy | 0 |
54,981 | 6,886,021,385 | IssuesEvent | 2017-11-21 17:57:02 | cs340tabyu/cs340Fall2017 | https://api.github.com/repos/cs340tabyu/cs340Fall2017 | opened | Large click space for certain routes | P4: Aesthetic or Design Flaw The Fun Team | Not a huge problem, but I noticed if you click on the edges of the map it acts are though you're trying to claim one of the nearby routes. Maybe you designed it that way, but it felt a little weird | 1.0 | Large click space for certain routes - Not a huge problem, but I noticed if you click on the edges of the map it acts are though you're trying to claim one of the nearby routes. Maybe you designed it that way, but it felt a little weird | non_priority | large click space for certain routes not a huge problem but i noticed if you click on the edges of the map it acts are though you re trying to claim one of the nearby routes maybe you designed it that way but it felt a little weird | 0 |
196,808 | 15,610,590,071 | IssuesEvent | 2021-03-19 13:22:42 | thelastinuit/toad | https://api.github.com/repos/thelastinuit/toad | closed | Update Readme | documentation | ## Expected Behavior
It should be helpful to developers who want to use it or modify it.
## Current Behavior
README says nothing of value about this demo project.
## Possible Solution
Update Readme with:
- Steps on how to install it
- Steps on how to run it | 1.0 | Update Readme - ## Expected Behavior
It should be helpful to developers who want to use it or modify it.
## Current Behavior
README says nothing of value about this demo project.
## Possible Solution
Update Readme with:
- Steps on how to install it
- Steps on how to run it | non_priority | update readme expected behavior it should be helpful to developers who want to use it or modify it current behavior readme says nothing of value about this demo project possible solution update readme with steps on how to install it steps on how to run it | 0 |
329,950 | 24,239,553,708 | IssuesEvent | 2022-09-27 04:51:10 | easystats/easystats | https://api.github.com/repos/easystats/easystats | opened | Include reference to publication in `DESCRIPTION` | Core Packages :package: Documentation :books: | Of course, only if there is a publication corresponding to the package you are maintaining:
[Like so](https://cran.r-project.org/web/packages/brms/index.html):
<img width="679" alt="Screenshot 2022-09-27 at 06 48 15" src="https://user-images.githubusercontent.com/11330453/192434636-d97ae01c-f848-4f19-a1b8-3cb74e57efa8.png">
# Progress tracker
- [ ] insight
- [ ] bayestestR
- [ ] effectsize
- [ ] parameters
- [ ] performance
- [ ] correlation
- [ ] see
- [ ] datawizard
| 1.0 | Include reference to publication in `DESCRIPTION` - Of course, only if there is a publication corresponding to the package you are maintaining:
[Like so](https://cran.r-project.org/web/packages/brms/index.html):
<img width="679" alt="Screenshot 2022-09-27 at 06 48 15" src="https://user-images.githubusercontent.com/11330453/192434636-d97ae01c-f848-4f19-a1b8-3cb74e57efa8.png">
# Progress tracker
- [ ] insight
- [ ] bayestestR
- [ ] effectsize
- [ ] parameters
- [ ] performance
- [ ] correlation
- [ ] see
- [ ] datawizard
| non_priority | include reference to publication in description of course only if there is a publication corresponding to the package you are maintaining img width alt screenshot at src progress tracker insight bayestestr effectsize parameters performance correlation see datawizard | 0 |
223,158 | 17,105,412,474 | IssuesEvent | 2021-07-09 16:55:27 | thcheetah777/alien | https://api.github.com/repos/thcheetah777/alien | closed | Organize main files into folders | documentation help wanted no coding simple | ## Steps:
- [x] Organize world.js by scenes
- [ ] Organize script.js by main scene class and config in another file | 1.0 | Organize main files into folders - ## Steps:
- [x] Organize world.js by scenes
- [ ] Organize script.js by main scene class and config in another file | non_priority | organize main files into folders steps organize world js by scenes organize script js by main scene class and config in another file | 0 |
323,589 | 23,955,827,313 | IssuesEvent | 2022-09-12 14:53:19 | tardis-sn/tardis | https://api.github.com/repos/tardis-sn/tardis | opened | Produce more in-depth documentation of the gamma-ray transport | documentation nebular | Gamma-ray transport needs more documentation to describe how it works and why it works as it does, ideally with paper references.
| 1.0 | Produce more in-depth documentation of the gamma-ray transport - Gamma-ray transport needs more documentation to describe how it works and why it works as it does, ideally with paper references.
| non_priority | produce more in depth documentation of the gamma ray transport gamma ray transport needs more documentation to describe how it works and why it works as it does ideally with paper references | 0 |
81,016 | 7,763,367,051 | IssuesEvent | 2018-06-01 16:18:42 | TheDMSGroup/mautic-extended-field | https://api.github.com/repos/TheDMSGroup/mautic-extended-field | closed | Installation prefix not implemented | bug needs testing | Hi guys,
There is an option to create table prefix during Mautic installation . It seems your plugin does not support this and sql queries do not work properly (tables are missing) . I'm putting the error message we got:
[2018-05-17 17:10:23] mautic.CRITICAL: Uncaught PHP Exception Doctrine\DBAL\Exception\TableNotFoundException:
"An exception occurred while executing '
SELECT COUNT(l.id) as count FROM mtc_leads l LEFT JOIN mtc_users u ON u.id = l.owner_id LEFT JOIN lead_fields_leads_string_xref string129
ON (l.id = string129.lead_id) AND (string129.lead_field_id = 129)'
: SQLSTATE[42S02]: Base table or view not found: 1146 Table 'mautic.lead_fields_leads_string_xref' doesn't exist"
at /home/webhosts/XLCD.com/html/mautic/vendor/doctrine/dbal/lib/Doctrine/DBAL/Driver/AbstractMySQLDriver.php line 53
{"exception":"[object] (Doctrine\\DBAL\\Exception\\TableNotFoundException(code: 0): An exception occurred while executing 'SELECT COUNT(l.id) as count
FROM mtc_leads l LEFT JOIN mtc_users u ON u.id = l.owner_id LEFT JOIN lead_fields_leads_string_xref string129 ON (l.id = string129.lead_id) AND
(string129.lead_field_id = 129)':\n\nSQLSTATE[42S02]: Base table or view not found: 1146 Table 'mautic.lead_fields_leads_string_xref' doesn't exist at
/home/webhosts/XLCD.com/html/mautic/vendor/doctrine/dbal/lib/Doctrine/DBAL/Driver/AbstractMySQLDriver.php:53,
Doctrine\\DBAL\\Driver\\PDOException(code: 42S02): SQLSTATE[42S02]: Base table or view not found: 1146 Table 'mautic.lead_fields_leads_string_xref'
doesn't exist at /home/webhosts/XLCD.com/html/mautic/vendor/doctrine/dbal/lib/Doctrine/DBAL/Driver/PDOConnection.php:106,
PDOException(code: 42S02): SQLSTATE[42S02]: Base table or view not found: 1146 Table 'mautic.lead_fields_leads_string_xref' doesn't exist at
/home/webhosts/XLCD.com/html/mautic/vendor/doctrine/dbal/lib/Doctrine/DBAL/Driver/PDOConnection.php:104)"} []
Br - PS | 1.0 | Installation prefix not implemented - Hi guys,
There is an option to create table prefix during Mautic installation . It seems your plugin does not support this and sql queries do not work properly (tables are missing) . I'm putting the error message we got:
[2018-05-17 17:10:23] mautic.CRITICAL: Uncaught PHP Exception Doctrine\DBAL\Exception\TableNotFoundException:
"An exception occurred while executing '
SELECT COUNT(l.id) as count FROM mtc_leads l LEFT JOIN mtc_users u ON u.id = l.owner_id LEFT JOIN lead_fields_leads_string_xref string129
ON (l.id = string129.lead_id) AND (string129.lead_field_id = 129)'
: SQLSTATE[42S02]: Base table or view not found: 1146 Table 'mautic.lead_fields_leads_string_xref' doesn't exist"
at /home/webhosts/XLCD.com/html/mautic/vendor/doctrine/dbal/lib/Doctrine/DBAL/Driver/AbstractMySQLDriver.php line 53
{"exception":"[object] (Doctrine\\DBAL\\Exception\\TableNotFoundException(code: 0): An exception occurred while executing 'SELECT COUNT(l.id) as count
FROM mtc_leads l LEFT JOIN mtc_users u ON u.id = l.owner_id LEFT JOIN lead_fields_leads_string_xref string129 ON (l.id = string129.lead_id) AND
(string129.lead_field_id = 129)':\n\nSQLSTATE[42S02]: Base table or view not found: 1146 Table 'mautic.lead_fields_leads_string_xref' doesn't exist at
/home/webhosts/XLCD.com/html/mautic/vendor/doctrine/dbal/lib/Doctrine/DBAL/Driver/AbstractMySQLDriver.php:53,
Doctrine\\DBAL\\Driver\\PDOException(code: 42S02): SQLSTATE[42S02]: Base table or view not found: 1146 Table 'mautic.lead_fields_leads_string_xref'
doesn't exist at /home/webhosts/XLCD.com/html/mautic/vendor/doctrine/dbal/lib/Doctrine/DBAL/Driver/PDOConnection.php:106,
PDOException(code: 42S02): SQLSTATE[42S02]: Base table or view not found: 1146 Table 'mautic.lead_fields_leads_string_xref' doesn't exist at
/home/webhosts/XLCD.com/html/mautic/vendor/doctrine/dbal/lib/Doctrine/DBAL/Driver/PDOConnection.php:104)"} []
Br - PS | non_priority | installation prefix not implemented hi guys there is an option to create table prefix during mautic installation it seems your plugin does not support this and sql queries do not work properly tables are missing i m putting the error message we got mautic critical uncaught php exception doctrine dbal exception tablenotfoundexception an exception occurred while executing select count l id as count from mtc leads l left join mtc users u on u id l owner id left join lead fields leads string xref on l id lead id and lead field id sqlstate base table or view not found table mautic lead fields leads string xref doesn t exist at home webhosts xlcd com html mautic vendor doctrine dbal lib doctrine dbal driver abstractmysqldriver php line exception doctrine dbal exception tablenotfoundexception code an exception occurred while executing select count l id as count from mtc leads l left join mtc users u on u id l owner id left join lead fields leads string xref on l id lead id and lead field id n nsqlstate base table or view not found table mautic lead fields leads string xref doesn t exist at home webhosts xlcd com html mautic vendor doctrine dbal lib doctrine dbal driver abstractmysqldriver php doctrine dbal driver pdoexception code sqlstate base table or view not found table mautic lead fields leads string xref doesn t exist at home webhosts xlcd com html mautic vendor doctrine dbal lib doctrine dbal driver pdoconnection php pdoexception code sqlstate base table or view not found table mautic lead fields leads string xref doesn t exist at home webhosts xlcd com html mautic vendor doctrine dbal lib doctrine dbal driver pdoconnection php br ps | 0 |
44,640 | 23,719,805,948 | IssuesEvent | 2022-08-30 14:31:45 | simdjson/simdjson | https://api.github.com/repos/simdjson/simdjson | opened | Optimize to_bitmask() for ARM | performance | The current to_bitmask() implementation in ARM is expensive.
In simdutf, we reengineered the code to use a faster function...
https://github.com/simdutf/simdutf/blob/c0cb6dddb12256a261bb249255660b79c1fe67a2/src/simdutf/arm64/simd.h#L210-L212
Reference:
https://community.arm.com/arm-community-blogs/b/infrastructure-solutions-blog/posts/porting-x86-vector-bitmask-optimizations-to-arm-neon
We should investigate this optimization.
Credit to Nathan Kurz for the pointer.
| True | Optimize to_bitmask() for ARM - The current to_bitmask() implementation in ARM is expensive.
In simdutf, we reengineered the code to use a faster function...
https://github.com/simdutf/simdutf/blob/c0cb6dddb12256a261bb249255660b79c1fe67a2/src/simdutf/arm64/simd.h#L210-L212
Reference:
https://community.arm.com/arm-community-blogs/b/infrastructure-solutions-blog/posts/porting-x86-vector-bitmask-optimizations-to-arm-neon
We should investigate this optimization.
Credit to Nathan Kurz for the pointer.
| non_priority | optimize to bitmask for arm the current to bitmask implementation in arm is expensive in simdutf we reengineered the code to use a faster function reference we should investigate this optimization credit to nathan kurz for the pointer | 0 |
162,321 | 12,643,453,279 | IssuesEvent | 2020-06-16 09:50:01 | jpmorganchase/nbcelltests | https://api.github.com/repos/jpmorganchase/nbcelltests | opened | Certain cell failures are not detected | bug cell tests | Inherited from nbval. E.g. test for bad magics is currently marked "known fail":
https://github.com/jpmorganchase/nbcelltests/blob/f6d206118ee336efd74049ff8c72fd827be1c739/nbcelltests/tests/test_test.py#L475-L481
(note: typo in above method name - "does _not_")
There might be other cases too, haven't investigated. | 1.0 | Certain cell failures are not detected - Inherited from nbval. E.g. test for bad magics is currently marked "known fail":
https://github.com/jpmorganchase/nbcelltests/blob/f6d206118ee336efd74049ff8c72fd827be1c739/nbcelltests/tests/test_test.py#L475-L481
(note: typo in above method name - "does _not_")
There might be other cases too, haven't investigated. | non_priority | certain cell failures are not detected inherited from nbval e g test for bad magics is currently marked known fail note typo in above method name does not there might be other cases too haven t investigated | 0 |
90,297 | 18,106,355,277 | IssuesEvent | 2021-09-22 19:33:47 | UBC-Thunderbots/Software | https://api.github.com/repos/UBC-Thunderbots/Software | closed | DynamicParameters: Separate const parameters from dynamic parameters | Difficulty - 7 Code Quality | ### Description of the task
Currently we have `c_params` which get generated from `constant` parameters in a config definition yaml file, and we have `cpp_params` that are generated from both `const` and `non-const` parameters in the yaml file.
Marking a dynamic parameter as `const` is something that we realized will never happen, and it saves us a great deal of complexity if they were entirely separate concepts. This ticket involves separating all the `constant parameters` from the ` dynamic parameters` and having separate files for both.
RFC of new parameter system for context: https://docs.google.com/document/d/1-QD8_7TZiq6CNRSMeSmyg0ChrSVfvxwt_e6eLqiqRDA/edit
<!--
What does this work depend on?
What interface will this work use or create?
What are the main components of the task?
Where does this work fit in the larger project?
It is important to define this task sufficiently so that an untrained
team member can take it on and know where to start. Feel free to
link to resources or other team member which could guide the assignee to
complete the task
-->
### Acceptance criteria
The goal of this ticket is to:
<!--
Checkbox list that outlines what needs to be done in order for this task
to be considered "complete".
Specify any implementation requirements such as data structures,
functionalities, testing requirements, documentation, etc.
-->
- [ ] Pull out all `const` parameters into their own seperate files, so each config yaml only exclusively has dynamic parameters, or const parameters, never both.
- [ ] Figure out folder/file structure for const vs dynamic parameters (i.e how do we know a config file contains const parameters or dynamic parameters)
- [ ] Update the schema to reject `const` keyword (should be implicit from point above, which file is const and which file dynamic)
- [ ] Rename `c_params` to `constant_parameters` and `cpp_parameters` to `dynamic_parameters`
### Blocked By
#1298
<!--
List all other issues that need to be completed before this one, ex:
- #123
- #374
-->
| 1.0 | DynamicParameters: Separate const parameters from dynamic parameters - ### Description of the task
Currently we have `c_params` which get generated from `constant` parameters in a config definition yaml file, and we have `cpp_params` that are generated from both `const` and `non-const` parameters in the yaml file.
Marking a dynamic parameter as `const` is something that we realized will never happen, and it saves us a great deal of complexity if they were entirely separate concepts. This ticket involves separating all the `constant parameters` from the ` dynamic parameters` and having separate files for both.
RFC of new parameter system for context: https://docs.google.com/document/d/1-QD8_7TZiq6CNRSMeSmyg0ChrSVfvxwt_e6eLqiqRDA/edit
<!--
What does this work depend on?
What interface will this work use or create?
What are the main components of the task?
Where does this work fit in the larger project?
It is important to define this task sufficiently so that an untrained
team member can take it on and know where to start. Feel free to
link to resources or other team member which could guide the assignee to
complete the task
-->
### Acceptance criteria
The goal of this ticket is to:
<!--
Checkbox list that outlines what needs to be done in order for this task
to be considered "complete".
Specify any implementation requirements such as data structures,
functionalities, testing requirements, documentation, etc.
-->
- [ ] Pull out all `const` parameters into their own seperate files, so each config yaml only exclusively has dynamic parameters, or const parameters, never both.
- [ ] Figure out folder/file structure for const vs dynamic parameters (i.e how do we know a config file contains const parameters or dynamic parameters)
- [ ] Update the schema to reject `const` keyword (should be implicit from point above, which file is const and which file dynamic)
- [ ] Rename `c_params` to `constant_parameters` and `cpp_parameters` to `dynamic_parameters`
### Blocked By
#1298
<!--
List all other issues that need to be completed before this one, ex:
- #123
- #374
-->
| non_priority | dynamicparameters separate const parameters from dynamic parameters description of the task currently we have c params which get generated from constant parameters in a config definition yaml file and we have cpp params that are generated from both const and non const parameters in the yaml file marking a dynamic parameter as const is something that we realized will never happen and it saves us a great deal of complexity if they were entirely separate concepts this ticket involves separating all the constant parameters from the dynamic parameters and having separate files for both rfc of new parameter system for context what does this work depend on what interface will this work use or create what are the main components of the task where does this work fit in the larger project it is important to define this task sufficiently so that an untrained team member can take it on and know where to start feel free to link to resources or other team member which could guide the assignee to complete the task acceptance criteria the goal of this ticket is to checkbox list that outlines what needs to be done in order for this task to be considered complete specify any implementation requirements such as data structures functionalities testing requirements documentation etc pull out all const parameters into their own seperate files so each config yaml only exclusively has dynamic parameters or const parameters never both figure out folder file structure for const vs dynamic parameters i e how do we know a config file contains const parameters or dynamic parameters update the schema to reject const keyword should be implicit from point above which file is const and which file dynamic rename c params to constant parameters and cpp parameters to dynamic parameters blocked by list all other issues that need to be completed before this one ex | 0 |
63,032 | 12,278,520,118 | IssuesEvent | 2020-05-08 10:08:16 | fac19/snake | https://api.github.com/repos/fac19/snake | opened | Good place for an explanatory comment? | code review documentation | The onKeyDown function is really interesting - I notice you plan to mention it in the presentation, which I'm looking forward to because tbh I don't get it. It might also be good to include an explanatory comment for yourself six months down the line. | 1.0 | Good place for an explanatory comment? - The onKeyDown function is really interesting - I notice you plan to mention it in the presentation, which I'm looking forward to because tbh I don't get it. It might also be good to include an explanatory comment for yourself six months down the line. | non_priority | good place for an explanatory comment the onkeydown function is really interesting i notice you plan to mention it in the presentation which i m looking forward to because tbh i don t get it it might also be good to include an explanatory comment for yourself six months down the line | 0 |
209,305 | 16,190,527,729 | IssuesEvent | 2021-05-04 07:49:06 | pmndrs/react-spring.io | https://api.github.com/repos/pmndrs/react-spring.io | closed | Add some guides | documentation enhancement help wanted | Everyone is encouraged to help out with these tasks:
- [ ] Add a "guide directory" page
- [ ] Write a short guide for getting started with each target platform (eg: web, zdog, three)
- [ ] Convert solved questions from https://github.com/react-spring/react-spring/issues into guided implementations
- [ ] Write a short guide about how you fixed a broken animation while learning `react-spring`
It would be great if the guides used [`react-live`](https://github.com/FormidableLabs/react-live)! | 1.0 | Add some guides - Everyone is encouraged to help out with these tasks:
- [ ] Add a "guide directory" page
- [ ] Write a short guide for getting started with each target platform (eg: web, zdog, three)
- [ ] Convert solved questions from https://github.com/react-spring/react-spring/issues into guided implementations
- [ ] Write a short guide about how you fixed a broken animation while learning `react-spring`
It would be great if the guides used [`react-live`](https://github.com/FormidableLabs/react-live)! | non_priority | add some guides everyone is encouraged to help out with these tasks add a guide directory page write a short guide for getting started with each target platform eg web zdog three convert solved questions from into guided implementations write a short guide about how you fixed a broken animation while learning react spring it would be great if the guides used | 0 |
100,193 | 12,508,382,180 | IssuesEvent | 2020-06-02 15:28:33 | revelry-foundation/nightingale | https://api.github.com/repos/revelry-foundation/nightingale | opened | Landing Page - Hero Image - Stock Purchase | @done approve @done write @skipped estimate design | ## Background
We're using an image from Getty for the hero of the landing page, that seems to meet with everyone's approval. (see attachment below) We need to purchase this prior to launch. Pricing is below. Recommended resolution is the MEDIUM size.
<img width="350" alt="Screen Shot 2020-06-02 at 10 27 44" src="https://user-images.githubusercontent.com/45366606/83538707-c63dcd00-a4bb-11ea-99af-0f2c0961f21f.png">
## Scenario: Homepage Hero Stock Photo
Given I am someone with the financial authority to make the decision,
- [ ] When I pick up this ticket,
- [ ] Then I purchase the image at the recommended resolution,
- [ ] And I upload the original file to [the project GDrive folder](https://drive.google.com/open?id=1g5I0ZstVfwZM4dBLOR-dfJsU9TwXpHyO),
- [ ] And I let @westonmcwhorter and @vegasgeek know that I have done so. | 1.0 | Landing Page - Hero Image - Stock Purchase - ## Background
We're using an image from Getty for the hero of the landing page, that seems to meet with everyone's approval. (see attachment below) We need to purchase this prior to launch. Pricing is below. Recommended resolution is the MEDIUM size.
<img width="350" alt="Screen Shot 2020-06-02 at 10 27 44" src="https://user-images.githubusercontent.com/45366606/83538707-c63dcd00-a4bb-11ea-99af-0f2c0961f21f.png">
## Scenario: Homepage Hero Stock Photo
Given I am someone with the financial authority to make the decision,
- [ ] When I pick up this ticket,
- [ ] Then I purchase the image at the recommended resolution,
- [ ] And I upload the original file to [the project GDrive folder](https://drive.google.com/open?id=1g5I0ZstVfwZM4dBLOR-dfJsU9TwXpHyO),
- [ ] And I let @westonmcwhorter and @vegasgeek know that I have done so. | non_priority | landing page hero image stock purchase background we re using an image from getty for the hero of the landing page that seems to meet with everyone s approval see attachment below we need to purchase this prior to launch pricing is below recommended resolution is the medium size img width alt screen shot at src scenario homepage hero stock photo given i am someone with the financial authority to make the decision when i pick up this ticket then i purchase the image at the recommended resolution and i upload the original file to and i let westonmcwhorter and vegasgeek know that i have done so | 0 |
81,776 | 10,179,859,877 | IssuesEvent | 2019-08-09 08:52:11 | LiskHQ/lisk-hub | https://api.github.com/repos/LiskHQ/lisk-hub | closed | Align app loader animation to design | Unplanned severity: medium stretch goals type: design | ## Current behaviour
App loading screen (the one before splash screen) was not updated to the latest design
## Expected behaviour
App loading screen should be updated to the latest design provided by design team. The animation should be something like https://codepen.io/kenchen/pen/tgBiE | 1.0 | Align app loader animation to design - ## Current behaviour
App loading screen (the one before splash screen) was not updated to the latest design
## Expected behaviour
App loading screen should be updated to the latest design provided by design team. The animation should be something like https://codepen.io/kenchen/pen/tgBiE | non_priority | align app loader animation to design current behaviour app loading screen the one before splash screen was not updated to the latest design expected behaviour app loading screen should be updated to the latest design provided by design team the animation should be something like | 0 |
249,321 | 26,911,338,134 | IssuesEvent | 2023-02-07 00:12:20 | Enterprise-CMCS/macpro-appian-connector | https://api.github.com/repos/Enterprise-CMCS/macpro-appian-connector | closed | SecurityHub Finding - SNS.1 SNS topics should be encrypted at-rest using AWS KMS | security-hub us-east-1 MEDIUM master | **************************************************************
__This issue was generated from Security Hub data and is managed through automation.__
Please do not edit the title or body of this issue, or remove the security-hub tag. All other edits/comments are welcome.
Finding Title: SNS.1 SNS topics should be encrypted at-rest using AWS KMS
**************************************************************
## Type of Issue:
- [x] Security Hub Finding
## Title:
SNS.1 SNS topics should be encrypted at-rest using AWS KMS
## Description
This control checks whether an Amazon SNS topic is encrypted at rest using AWS KMS.
## Remediation
https://docs.aws.amazon.com/console/securityhub/SNS.1/remediation
For directions on how to fix this issue, consult the AWS Security Hub Foundational Security Best Practices documentation.
## AC:
- All findings of this type are resolved or suppressed, indicated by a Workflow Status of Resolved or Suppressed. (Note: this ticket will automatically close when the AC is met.)
| True | SecurityHub Finding - SNS.1 SNS topics should be encrypted at-rest using AWS KMS - **************************************************************
__This issue was generated from Security Hub data and is managed through automation.__
Please do not edit the title or body of this issue, or remove the security-hub tag. All other edits/comments are welcome.
Finding Title: SNS.1 SNS topics should be encrypted at-rest using AWS KMS
**************************************************************
## Type of Issue:
- [x] Security Hub Finding
## Title:
SNS.1 SNS topics should be encrypted at-rest using AWS KMS
## Description
This control checks whether an Amazon SNS topic is encrypted at rest using AWS KMS.
## Remediation
https://docs.aws.amazon.com/console/securityhub/SNS.1/remediation
For directions on how to fix this issue, consult the AWS Security Hub Foundational Security Best Practices documentation.
## AC:
- All findings of this type are resolved or suppressed, indicated by a Workflow Status of Resolved or Suppressed. (Note: this ticket will automatically close when the AC is met.)
| non_priority | securityhub finding sns sns topics should be encrypted at rest using aws kms this issue was generated from security hub data and is managed through automation please do not edit the title or body of this issue or remove the security hub tag all other edits comments are welcome finding title sns sns topics should be encrypted at rest using aws kms type of issue security hub finding title sns sns topics should be encrypted at rest using aws kms description this control checks whether an amazon sns topic is encrypted at rest using aws kms remediation for directions on how to fix this issue consult the aws security hub foundational security best practices documentation ac all findings of this type are resolved or suppressed indicated by a workflow status of resolved or suppressed note this ticket will automatically close when the ac is met | 0 |
111,436 | 14,079,628,442 | IssuesEvent | 2020-11-04 15:06:50 | laurent22/joplin | https://api.github.com/repos/laurent22/joplin | closed | Markdown export, exports also name of Note - Makes it non MD compliant | as designed | ## Environment
Joplin version:
Joplin for Desktop
Copyright © 2016-2020 Laurent Cozic
Joplin 1.2.6 (prod, win32)
Client ID: 92e2017594e141ffb762ac52e679bb96
Sync Version: 2
Profile Version: 34
Keychain Supported: Yes
Revision: f5f117cb (master)
Platform: Windows 10 - 10.0.18363.0
OS specifics:
## Steps to reproduce
1. Create a new note and save it
2. press File -> Export all -> MD Markdown
3. The output includes the note name as the first list of the file.
<!--
Issues without reproduction steps are likely to stall.
-->
## Describe what you expected to happen
I would expect that the note name in the markdown file either is:
a. Not in the export at all
b. Always exported as H1 in top of the file
## Logfile
<!--
Please attach a debug log. Issues without a debug log are likely to stall.
For information on how to collect a log file: https://joplinapp.org/debugging/
-->
| 1.0 | Markdown export, exports also name of Note - Makes it non MD compliant - ## Environment
Joplin version:
Joplin for Desktop
Copyright © 2016-2020 Laurent Cozic
Joplin 1.2.6 (prod, win32)
Client ID: 92e2017594e141ffb762ac52e679bb96
Sync Version: 2
Profile Version: 34
Keychain Supported: Yes
Revision: f5f117cb (master)
Platform: Windows 10 - 10.0.18363.0
OS specifics:
## Steps to reproduce
1. Create a new note and save it
2. press File -> Export all -> MD Markdown
3. The output includes the note name as the first list of the file.
<!--
Issues without reproduction steps are likely to stall.
-->
## Describe what you expected to happen
I would expect that the note name in the markdown file either is:
a. Not in the export at all
b. Always exported as H1 in top of the file
## Logfile
<!--
Please attach a debug log. Issues without a debug log are likely to stall.
For information on how to collect a log file: https://joplinapp.org/debugging/
-->
| non_priority | markdown export exports also name of note makes it non md compliant environment joplin version joplin for desktop copyright © laurent cozic joplin prod client id sync version profile version keychain supported yes revision master platform windows os specifics steps to reproduce create a new note and save it press file export all md markdown the output includes the note name as the first list of the file issues without reproduction steps are likely to stall describe what you expected to happen i would expect that the note name in the markdown file either is a not in the export at all b always exported as in top of the file logfile please attach a debug log issues without a debug log are likely to stall for information on how to collect a log file | 0 |
357,999 | 25,176,598,749 | IssuesEvent | 2022-11-11 09:49:03 | jeyvia/pe | https://api.github.com/repos/jeyvia/pe | opened | DG Design & Implementation missing documentations | severity.High type.DocumentationBug | Design & Implementation only includes:
1. Save/Withdraw/Deposite feature
2. Add/Remove personal currency feature
It is missing:
1. Account feature
2. List feature
3. Transfer feature
4. Info about currencies feature
5. Currency conversion feature
6. balance feature
7. help feature
and many more features that lack both the documentation and diagrams to aid developers' understanding.
<!--session: 1668153587820-285a8579-6045-4dce-b5bb-f6e6da1d6dfd-->
<!--Version: Web v3.4.4--> | 1.0 | DG Design & Implementation missing documentations - Design & Implementation only includes:
1. Save/Withdraw/Deposite feature
2. Add/Remove personal currency feature
It is missing:
1. Account feature
2. List feature
3. Transfer feature
4. Info about currencies feature
5. Currency conversion feature
6. balance feature
7. help feature
and many more features that lack both the documentation and diagrams to aid developers' understanding.
<!--session: 1668153587820-285a8579-6045-4dce-b5bb-f6e6da1d6dfd-->
<!--Version: Web v3.4.4--> | non_priority | dg design implementation missing documentations design implementation only includes save withdraw deposite feature add remove personal currency feature it is missing account feature list feature transfer feature info about currencies feature currency conversion feature balance feature help feature and many more features that lack both the documentation and diagrams to aid developers understanding | 0 |
184,260 | 21,784,841,544 | IssuesEvent | 2022-05-14 01:30:56 | Thezone1975/tabliss | https://api.github.com/repos/Thezone1975/tabliss | closed | WS-2020-0218 (High) detected in merge-1.2.0.tgz - autoclosed | security vulnerability | ## WS-2020-0218 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>merge-1.2.0.tgz</b></p></summary>
<p>Merge multiple objects into one, optionally creating a new cloned object. Similar to the jQuery.extend but more flexible. Works in Node.js and the browser.</p>
<p>Library home page: <a href="https://registry.npmjs.org/merge/-/merge-1.2.0.tgz">https://registry.npmjs.org/merge/-/merge-1.2.0.tgz</a></p>
<p>Path to dependency file: /tabliss/package.json</p>
<p>Path to vulnerable library: tabliss/node_modules/merge/package.json</p>
<p>
Dependency Hierarchy:
- jest-23.1.0.tgz (Root Library)
- jest-cli-23.6.0.tgz
- jest-haste-map-23.6.0.tgz
- sane-2.5.2.tgz
- exec-sh-0.2.1.tgz
- :x: **merge-1.2.0.tgz** (Vulnerable Library)
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
A Prototype Pollution vulnerability was found in merge before 2.1.0 via the merge.recursive function. It can be tricked into adding or modifying properties of the Object prototype. These properties will be present on all objects.
<p>Publish Date: 2020-10-09
<p>URL: <a href=https://github.com/yeikos/js.merge/pull/38>WS-2020-0218</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/yeikos/js.merge/pull/38">https://github.com/yeikos/js.merge/pull/38</a></p>
<p>Release Date: 2020-10-09</p>
<p>Fix Resolution: merge - 2.1.0</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | WS-2020-0218 (High) detected in merge-1.2.0.tgz - autoclosed - ## WS-2020-0218 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>merge-1.2.0.tgz</b></p></summary>
<p>Merge multiple objects into one, optionally creating a new cloned object. Similar to the jQuery.extend but more flexible. Works in Node.js and the browser.</p>
<p>Library home page: <a href="https://registry.npmjs.org/merge/-/merge-1.2.0.tgz">https://registry.npmjs.org/merge/-/merge-1.2.0.tgz</a></p>
<p>Path to dependency file: /tabliss/package.json</p>
<p>Path to vulnerable library: tabliss/node_modules/merge/package.json</p>
<p>
Dependency Hierarchy:
- jest-23.1.0.tgz (Root Library)
- jest-cli-23.6.0.tgz
- jest-haste-map-23.6.0.tgz
- sane-2.5.2.tgz
- exec-sh-0.2.1.tgz
- :x: **merge-1.2.0.tgz** (Vulnerable Library)
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
A Prototype Pollution vulnerability was found in merge before 2.1.0 via the merge.recursive function. It can be tricked into adding or modifying properties of the Object prototype. These properties will be present on all objects.
<p>Publish Date: 2020-10-09
<p>URL: <a href=https://github.com/yeikos/js.merge/pull/38>WS-2020-0218</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/yeikos/js.merge/pull/38">https://github.com/yeikos/js.merge/pull/38</a></p>
<p>Release Date: 2020-10-09</p>
<p>Fix Resolution: merge - 2.1.0</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_priority | ws high detected in merge tgz autoclosed ws high severity vulnerability vulnerable library merge tgz merge multiple objects into one optionally creating a new cloned object similar to the jquery extend but more flexible works in node js and the browser library home page a href path to dependency file tabliss package json path to vulnerable library tabliss node modules merge package json dependency hierarchy jest tgz root library jest cli tgz jest haste map tgz sane tgz exec sh tgz x merge tgz vulnerable library vulnerability details a prototype pollution vulnerability was found in merge before via the merge recursive function it can be tricked into adding or modifying properties of the object prototype these properties will be present on all objects publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact 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 merge step up your open source security game with whitesource | 0 |
256,849 | 19,473,291,678 | IssuesEvent | 2021-12-24 07:09:55 | appsmithorg/appsmith | https://api.github.com/repos/appsmithorg/appsmith | opened | Missing Document Viewer widget documentation | Documentation | @Pranay105 added the documentation for the document viewer widget here. https://www.notion.so/appsmith/Document-Viewer-1a36c9ff38b3440eb3d47ac41341bd90
Please review this and let me know | 1.0 | Missing Document Viewer widget documentation - @Pranay105 added the documentation for the document viewer widget here. https://www.notion.so/appsmith/Document-Viewer-1a36c9ff38b3440eb3d47ac41341bd90
Please review this and let me know | non_priority | missing document viewer widget documentation added the documentation for the document viewer widget here please review this and let me know | 0 |
104,756 | 9,008,205,469 | IssuesEvent | 2019-02-05 02:36:03 | cockroachdb/cockroach | https://api.github.com/repos/cockroachdb/cockroach | closed | roachtest: synctest failed | C-test-failure O-robot | SHA: https://github.com/cockroachdb/cockroach/commits/407932a95f3ad53d61481e5a7493fc4ed468faa9
Parameters:
To repro, try:
```
# Don't forget to check out a clean suitable branch and experiment with the
# stress invocation until the desired results present themselves. For example,
# using stress instead of stressrace and passing the '-p' stressflag which
# controls concurrency.
./scripts/gceworker.sh start && ./scripts/gceworker.sh mosh
cd ~/go/src/github.com/cockroachdb/cockroach && \
stdbuf -oL -eL \
make stressrace TESTS=synctest PKG=roachtest TESTTIMEOUT=5m STRESSFLAGS='-maxtime 20m -timeout 10m' 2>&1 | tee /tmp/stress.log
```
Failed test: https://teamcity.cockroachdb.com/viewLog.html?buildId=1117776&tab=buildLog
```
The test failed on master:
test.go:743,cluster.go:1226,synctest.go:64: /home/agent/work/.go/src/github.com/cockroachdb/cockroach/bin/roachprod run teamcity-1117776-synctest:1 -- sudo charybdefs {store-dir}/faulty -oallow_other,modules=subdir,subdir={store-dir}/real && chmod 777 {store-dir}/{real,faulty} returned:
stderr:
stdout:
sudo: charybdefs: command not found
Error: exit status 1
: exit status 1
``` | 1.0 | roachtest: synctest failed - SHA: https://github.com/cockroachdb/cockroach/commits/407932a95f3ad53d61481e5a7493fc4ed468faa9
Parameters:
To repro, try:
```
# Don't forget to check out a clean suitable branch and experiment with the
# stress invocation until the desired results present themselves. For example,
# using stress instead of stressrace and passing the '-p' stressflag which
# controls concurrency.
./scripts/gceworker.sh start && ./scripts/gceworker.sh mosh
cd ~/go/src/github.com/cockroachdb/cockroach && \
stdbuf -oL -eL \
make stressrace TESTS=synctest PKG=roachtest TESTTIMEOUT=5m STRESSFLAGS='-maxtime 20m -timeout 10m' 2>&1 | tee /tmp/stress.log
```
Failed test: https://teamcity.cockroachdb.com/viewLog.html?buildId=1117776&tab=buildLog
```
The test failed on master:
test.go:743,cluster.go:1226,synctest.go:64: /home/agent/work/.go/src/github.com/cockroachdb/cockroach/bin/roachprod run teamcity-1117776-synctest:1 -- sudo charybdefs {store-dir}/faulty -oallow_other,modules=subdir,subdir={store-dir}/real && chmod 777 {store-dir}/{real,faulty} returned:
stderr:
stdout:
sudo: charybdefs: command not found
Error: exit status 1
: exit status 1
``` | non_priority | roachtest synctest failed sha parameters to repro try don t forget to check out a clean suitable branch and experiment with the stress invocation until the desired results present themselves for example using stress instead of stressrace and passing the p stressflag which controls concurrency scripts gceworker sh start scripts gceworker sh mosh cd go src github com cockroachdb cockroach stdbuf ol el make stressrace tests synctest pkg roachtest testtimeout stressflags maxtime timeout tee tmp stress log failed test the test failed on master test go cluster go synctest go home agent work go src github com cockroachdb cockroach bin roachprod run teamcity synctest sudo charybdefs store dir faulty oallow other modules subdir subdir store dir real chmod store dir real faulty returned stderr stdout sudo charybdefs command not found error exit status exit status | 0 |
55,219 | 13,994,746,644 | IssuesEvent | 2020-10-28 01:30:43 | GooseWSS/apollo | https://api.github.com/repos/GooseWSS/apollo | opened | CVE-2019-6286 (Medium) detected in node-sass-4.14.1.tgz, node-sassv4.13.1 | security vulnerability | ## CVE-2019-6286 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>node-sass-4.14.1.tgz</b>, <b>node-sassv4.13.1</b></p></summary>
<p>
<details><summary><b>node-sass-4.14.1.tgz</b></p></summary>
<p>Wrapper around libsass</p>
<p>Library home page: <a href="https://registry.npmjs.org/node-sass/-/node-sass-4.14.1.tgz">https://registry.npmjs.org/node-sass/-/node-sass-4.14.1.tgz</a></p>
<p>Path to dependency file: apollo/modules/dreamview/frontend/package.json</p>
<p>Path to vulnerable library: apollo/modules/dreamview/frontend/node_modules/node-sass/package.json</p>
<p>
Dependency Hierarchy:
- :x: **node-sass-4.14.1.tgz** (Vulnerable Library)
</details>
<p>Found in HEAD commit: <a href="https://github.com/GooseWSS/apollo/commit/3daafad25ab3c7a29a0227f78bfc97114f368242">3daafad25ab3c7a29a0227f78bfc97114f368242</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
In LibSass 3.5.5, a heap-based buffer over-read exists in Sass::Prelexer::skip_over_scopes in prelexer.hpp when called from Sass::Parser::parse_import(), a similar issue to CVE-2018-11693.
<p>Publish Date: 2019-01-14
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-6286>CVE-2019-6286</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>6.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-6286">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-6286</a></p>
<p>Release Date: 2019-08-06</p>
<p>Fix Resolution: LibSass - 3.6.0</p>
</p>
</details>
<p></p>
***
:rescue_worker_helmet: Automatic Remediation is available for this issue
<!-- <REMEDIATE>{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"node-sass","packageVersion":"4.14.1","isTransitiveDependency":false,"dependencyTree":"node-sass:4.14.1","isMinimumFixVersionAvailable":true,"minimumFixVersion":"LibSass - 3.6.0"}],"vulnerabilityIdentifier":"CVE-2019-6286","vulnerabilityDetails":"In LibSass 3.5.5, a heap-based buffer over-read exists in Sass::Prelexer::skip_over_scopes in prelexer.hpp when called from Sass::Parser::parse_import(), a similar issue to CVE-2018-11693.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-6286","cvss3Severity":"medium","cvss3Score":"6.5","cvss3Metrics":{"A":"High","AC":"Low","PR":"None","S":"Unchanged","C":"None","UI":"Required","AV":"Network","I":"None"},"extraData":{}}</REMEDIATE> --> | True | CVE-2019-6286 (Medium) detected in node-sass-4.14.1.tgz, node-sassv4.13.1 - ## CVE-2019-6286 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>node-sass-4.14.1.tgz</b>, <b>node-sassv4.13.1</b></p></summary>
<p>
<details><summary><b>node-sass-4.14.1.tgz</b></p></summary>
<p>Wrapper around libsass</p>
<p>Library home page: <a href="https://registry.npmjs.org/node-sass/-/node-sass-4.14.1.tgz">https://registry.npmjs.org/node-sass/-/node-sass-4.14.1.tgz</a></p>
<p>Path to dependency file: apollo/modules/dreamview/frontend/package.json</p>
<p>Path to vulnerable library: apollo/modules/dreamview/frontend/node_modules/node-sass/package.json</p>
<p>
Dependency Hierarchy:
- :x: **node-sass-4.14.1.tgz** (Vulnerable Library)
</details>
<p>Found in HEAD commit: <a href="https://github.com/GooseWSS/apollo/commit/3daafad25ab3c7a29a0227f78bfc97114f368242">3daafad25ab3c7a29a0227f78bfc97114f368242</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
In LibSass 3.5.5, a heap-based buffer over-read exists in Sass::Prelexer::skip_over_scopes in prelexer.hpp when called from Sass::Parser::parse_import(), a similar issue to CVE-2018-11693.
<p>Publish Date: 2019-01-14
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-6286>CVE-2019-6286</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>6.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-6286">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-6286</a></p>
<p>Release Date: 2019-08-06</p>
<p>Fix Resolution: LibSass - 3.6.0</p>
</p>
</details>
<p></p>
***
:rescue_worker_helmet: Automatic Remediation is available for this issue
<!-- <REMEDIATE>{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"node-sass","packageVersion":"4.14.1","isTransitiveDependency":false,"dependencyTree":"node-sass:4.14.1","isMinimumFixVersionAvailable":true,"minimumFixVersion":"LibSass - 3.6.0"}],"vulnerabilityIdentifier":"CVE-2019-6286","vulnerabilityDetails":"In LibSass 3.5.5, a heap-based buffer over-read exists in Sass::Prelexer::skip_over_scopes in prelexer.hpp when called from Sass::Parser::parse_import(), a similar issue to CVE-2018-11693.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-6286","cvss3Severity":"medium","cvss3Score":"6.5","cvss3Metrics":{"A":"High","AC":"Low","PR":"None","S":"Unchanged","C":"None","UI":"Required","AV":"Network","I":"None"},"extraData":{}}</REMEDIATE> --> | non_priority | cve medium detected in node sass tgz node cve medium severity vulnerability vulnerable libraries node sass tgz node node sass tgz wrapper around libsass library home page a href path to dependency file apollo modules dreamview frontend package json path to vulnerable library apollo modules dreamview frontend node modules node sass package json dependency hierarchy x node sass tgz vulnerable library found in head commit a href found in base branch master vulnerability details in libsass a heap based buffer over read exists in sass prelexer skip over scopes in prelexer hpp when called from sass parser parse import a similar issue to cve publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction 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 libsass rescue worker helmet automatic remediation is available for this issue isopenpronvulnerability true ispackagebased true isdefaultbranch true packages vulnerabilityidentifier cve vulnerabilitydetails in libsass a heap based buffer over read exists in sass prelexer skip over scopes in prelexer hpp when called from sass parser parse import a similar issue to cve vulnerabilityurl | 0 |
367,812 | 25,763,443,472 | IssuesEvent | 2022-12-08 22:49:50 | mlte-team/mlte | https://api.github.com/repos/mlte-team/mlte | opened | Develop a Roadmap for Integrations | documentation question | We want to expand MLTE to integrate with various third-party libraries for ML. We should develop a roadmap for integration that prioritizes specific functionality in specific libraries. | 1.0 | Develop a Roadmap for Integrations - We want to expand MLTE to integrate with various third-party libraries for ML. We should develop a roadmap for integration that prioritizes specific functionality in specific libraries. | non_priority | develop a roadmap for integrations we want to expand mlte to integrate with various third party libraries for ml we should develop a roadmap for integration that prioritizes specific functionality in specific libraries | 0 |
42,612 | 11,171,239,272 | IssuesEvent | 2019-12-28 18:01:38 | markstory/asset_compress | https://api.github.com/repos/markstory/asset_compress | closed | build command throws error with CakePHP 4.0.0 | defect | see https://travis-ci.org/foodcoopshop/foodcoopshop/jobs/629496999
`$ bin/cake asset_compress build`
Exception: Too few arguments to function Cake\Console\Shell::out(), 0 passed in /home/travis/build/foodcoopshop/foodcoopshop/vendor/markstory/asset_compress/src/Shell/AssetCompressShell.php on line 51 and at least 1 expected
In [/home/travis/build/foodcoopshop/foodcoopshop/vendor/cakephp/cakephp/src/Console/Shell.php, line 709]
2019-12-26 00:16:17 Error: [ArgumentCountError] Too few arguments to function Cake\Console\Shell::out(), 0 passed in /home/travis/build/foodcoopshop/foodcoopshop/vendor/markstory/asset_compress/src/Shell/AssetCompressShell.php on line 51 and at least 1 expected in /home/travis/build/foodcoopshop/foodcoopshop/vendor/cakephp/cakephp/src/Console/Shell.php on line 709
Stack Trace:
- /home/travis/build/foodcoopshop/foodcoopshop/vendor/markstory/asset_compress/src/Shell/AssetCompressShell.php:51
- /home/travis/build/foodcoopshop/foodcoopshop/vendor/cakephp/cakephp/src/Console/Shell.php:500
- /home/travis/build/foodcoopshop/foodcoopshop/vendor/cakephp/cakephp/src/Console/CommandRunner.php:354
- /home/travis/build/foodcoopshop/foodcoopshop/vendor/cakephp/cakephp/src/Console/CommandRunner.php:168
- /home/travis/build/foodcoopshop/foodcoopshop/bin/cake.php:12 | 1.0 | build command throws error with CakePHP 4.0.0 - see https://travis-ci.org/foodcoopshop/foodcoopshop/jobs/629496999
`$ bin/cake asset_compress build`
Exception: Too few arguments to function Cake\Console\Shell::out(), 0 passed in /home/travis/build/foodcoopshop/foodcoopshop/vendor/markstory/asset_compress/src/Shell/AssetCompressShell.php on line 51 and at least 1 expected
In [/home/travis/build/foodcoopshop/foodcoopshop/vendor/cakephp/cakephp/src/Console/Shell.php, line 709]
2019-12-26 00:16:17 Error: [ArgumentCountError] Too few arguments to function Cake\Console\Shell::out(), 0 passed in /home/travis/build/foodcoopshop/foodcoopshop/vendor/markstory/asset_compress/src/Shell/AssetCompressShell.php on line 51 and at least 1 expected in /home/travis/build/foodcoopshop/foodcoopshop/vendor/cakephp/cakephp/src/Console/Shell.php on line 709
Stack Trace:
- /home/travis/build/foodcoopshop/foodcoopshop/vendor/markstory/asset_compress/src/Shell/AssetCompressShell.php:51
- /home/travis/build/foodcoopshop/foodcoopshop/vendor/cakephp/cakephp/src/Console/Shell.php:500
- /home/travis/build/foodcoopshop/foodcoopshop/vendor/cakephp/cakephp/src/Console/CommandRunner.php:354
- /home/travis/build/foodcoopshop/foodcoopshop/vendor/cakephp/cakephp/src/Console/CommandRunner.php:168
- /home/travis/build/foodcoopshop/foodcoopshop/bin/cake.php:12 | non_priority | build command throws error with cakephp see bin cake asset compress build exception too few arguments to function cake console shell out passed in home travis build foodcoopshop foodcoopshop vendor markstory asset compress src shell assetcompressshell php on line and at least expected in error too few arguments to function cake console shell out passed in home travis build foodcoopshop foodcoopshop vendor markstory asset compress src shell assetcompressshell php on line and at least expected in home travis build foodcoopshop foodcoopshop vendor cakephp cakephp src console shell php on line stack trace home travis build foodcoopshop foodcoopshop vendor markstory asset compress src shell assetcompressshell php home travis build foodcoopshop foodcoopshop vendor cakephp cakephp src console shell php home travis build foodcoopshop foodcoopshop vendor cakephp cakephp src console commandrunner php home travis build foodcoopshop foodcoopshop vendor cakephp cakephp src console commandrunner php home travis build foodcoopshop foodcoopshop bin cake php | 0 |
192,680 | 14,625,874,810 | IssuesEvent | 2020-12-23 09:20:54 | eclipse/che | https://api.github.com/repos/eclipse/che | closed | Git SSH flow E2E UI tests failed on 'Generate a SSH key' step | area/qe e2e-test/failure kind/bug severity/P1 | ### Describe the bug
Git SSH flow E2E UI tests failed on 'Generate a SSH key' step because workspace wasn't ready at the time:
https://codeready-workspaces-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/basic-MultiUser-Che-check-e2e-tests-against-k8s/2343/
```
▼ TopMenu.selectOption "View"
▼ TopMenu.clickOnTopMenuButton "View"
▼ Ide.closeAllNotifications
▼ NotificationCenter.open
▼ NotificationCenter.clickIconOnStatusBar
▼ NotificationCenter.waitOpening
▼ NotificationCenter.closeAll
▼ NotificationCenter.clickCloseAllNotificationsButton
▼ NotificationCenter.waitClearNotificationsList
▼ TopMenu.clickOnSubmenuItem "Find Command..."
▼ QuickOpenContainer.typeAndSelectSuggestion
▼ QuickOpenContainer.clickOnContainerItem "SSH: generate key pair..."
▼ QuickOpenContainer.waitContainer
1) Generate a SSH key
1 passing (1m)
1 failing
1) Git with ssh workflow
Generate a SSH key:
TimeoutError: Exceeded maximum clicking attempts, the 'By(css selector, div[aria-label="SSH: generate key pair..., picker"])' element is not clickable
at DriverHelper.waitAndClick (/tmp/e2e/utils/DriverHelper.ts:291:15)
at <anonymous>
at process._tickCallback (internal/process/next_tick.js:188:7)
```
### Che version
<!-- (if workspace is running, version can be obtained with help/about menu) -->
- [ ] latest
- [x] nightly
- [ ] other: please specify
### Steps to reproduce
Tests scenario https://github.com/eclipse/che/blob/master/tests/e2e/tests/e2e/GitSsh.spec.ts
### Expected behavior
<!-- A clear and concise description of what you expected to happen. -->
### Runtime
- [ ] kubernetes (include output of `kubectl version`)
- [ ] Openshift (include output of `oc version`)
- [x] minikube (include output of `minikube version` and `kubectl version`)
- [ ] minishift (include output of `minishift version` and `oc version`)
- [ ] docker-desktop + K8S (include output of `docker version` and `kubectl version`)
- [ ] other: (please specify)
### Screenshots
### Screencast
https://youtu.be/hsII-Al_-Ys
### Installation method
- [x] chectl
* provide a full command that was used to deploy Eclipse Che (including the output)
* provide an output of `chectl version` command
- [ ] OperatorHub
- [ ] I don't know
### Environment
- [ ] my computer
- [ ] Windows
- [ ] Linux
- [ ] macOS
- [ ] Cloud
- [ ] Amazon
- [ ] Azure
- [ ] GCE
- [ ] other (please specify)
- [ ] other: please specify
### Eclipse Che Logs
<!-- https://www.eclipse.org/che/docs/che-7/collecting-logs-using-chectl -->
### Additional context
<!-- Add any other context about the problem here. -->
| 1.0 | Git SSH flow E2E UI tests failed on 'Generate a SSH key' step - ### Describe the bug
Git SSH flow E2E UI tests failed on 'Generate a SSH key' step because workspace wasn't ready at the time:
https://codeready-workspaces-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/basic-MultiUser-Che-check-e2e-tests-against-k8s/2343/
```
▼ TopMenu.selectOption "View"
▼ TopMenu.clickOnTopMenuButton "View"
▼ Ide.closeAllNotifications
▼ NotificationCenter.open
▼ NotificationCenter.clickIconOnStatusBar
▼ NotificationCenter.waitOpening
▼ NotificationCenter.closeAll
▼ NotificationCenter.clickCloseAllNotificationsButton
▼ NotificationCenter.waitClearNotificationsList
▼ TopMenu.clickOnSubmenuItem "Find Command..."
▼ QuickOpenContainer.typeAndSelectSuggestion
▼ QuickOpenContainer.clickOnContainerItem "SSH: generate key pair..."
▼ QuickOpenContainer.waitContainer
1) Generate a SSH key
1 passing (1m)
1 failing
1) Git with ssh workflow
Generate a SSH key:
TimeoutError: Exceeded maximum clicking attempts, the 'By(css selector, div[aria-label="SSH: generate key pair..., picker"])' element is not clickable
at DriverHelper.waitAndClick (/tmp/e2e/utils/DriverHelper.ts:291:15)
at <anonymous>
at process._tickCallback (internal/process/next_tick.js:188:7)
```
### Che version
<!-- (if workspace is running, version can be obtained with help/about menu) -->
- [ ] latest
- [x] nightly
- [ ] other: please specify
### Steps to reproduce
Tests scenario https://github.com/eclipse/che/blob/master/tests/e2e/tests/e2e/GitSsh.spec.ts
### Expected behavior
<!-- A clear and concise description of what you expected to happen. -->
### Runtime
- [ ] kubernetes (include output of `kubectl version`)
- [ ] Openshift (include output of `oc version`)
- [x] minikube (include output of `minikube version` and `kubectl version`)
- [ ] minishift (include output of `minishift version` and `oc version`)
- [ ] docker-desktop + K8S (include output of `docker version` and `kubectl version`)
- [ ] other: (please specify)
### Screenshots
### Screencast
https://youtu.be/hsII-Al_-Ys
### Installation method
- [x] chectl
* provide a full command that was used to deploy Eclipse Che (including the output)
* provide an output of `chectl version` command
- [ ] OperatorHub
- [ ] I don't know
### Environment
- [ ] my computer
- [ ] Windows
- [ ] Linux
- [ ] macOS
- [ ] Cloud
- [ ] Amazon
- [ ] Azure
- [ ] GCE
- [ ] other (please specify)
- [ ] other: please specify
### Eclipse Che Logs
<!-- https://www.eclipse.org/che/docs/che-7/collecting-logs-using-chectl -->
### Additional context
<!-- Add any other context about the problem here. -->
| non_priority | git ssh flow ui tests failed on generate a ssh key step describe the bug git ssh flow ui tests failed on generate a ssh key step because workspace wasn t ready at the time ▼ topmenu selectoption view ▼ topmenu clickontopmenubutton view ▼ ide closeallnotifications ▼ notificationcenter open ▼ notificationcenter clickicononstatusbar ▼ notificationcenter waitopening ▼ notificationcenter closeall ▼ notificationcenter clickcloseallnotificationsbutton ▼ notificationcenter waitclearnotificationslist ▼ topmenu clickonsubmenuitem find command ▼ quickopencontainer typeandselectsuggestion ▼ quickopencontainer clickoncontaineritem ssh generate key pair ▼ quickopencontainer waitcontainer generate a ssh key passing failing git with ssh workflow generate a ssh key timeouterror exceeded maximum clicking attempts the by css selector div element is not clickable at driverhelper waitandclick tmp utils driverhelper ts at at process tickcallback internal process next tick js che version latest nightly other please specify steps to reproduce tests scenario expected behavior runtime kubernetes include output of kubectl version openshift include output of oc version minikube include output of minikube version and kubectl version minishift include output of minishift version and oc version docker desktop include output of docker version and kubectl version other please specify screenshots screencast installation method chectl provide a full command that was used to deploy eclipse che including the output provide an output of chectl version command operatorhub i don t know environment my computer windows linux macos cloud amazon azure gce other please specify other please specify eclipse che logs additional context | 0 |
166,022 | 20,711,379,498 | IssuesEvent | 2022-03-12 01:14:25 | snowflakedb/snowflake-jdbc | https://api.github.com/repos/snowflakedb/snowflake-jdbc | closed | SNOW-558862: CVE-2019-10202 (High) detected in jackson-databind-2.9.8.jar - autoclosed | security vulnerability | ## CVE-2019-10202 - 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.8.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-ua_20220312003410_KQQKCS/archiveExtraction_BELGGC/FUIDAN/20220312003410/snowflake-jdbc_depth_0/dependencies/arrow-vector-0.15.1/META-INF/maven/org.apache.arrow/arrow-vector/pom.xml</p>
<p>Path to vulnerable library: /sitory/com/fasterxml/jackson/core/jackson-databind/2.9.8/jackson-databind-2.9.8.jar</p>
<p>
Dependency Hierarchy:
- :x: **jackson-databind-2.9.8.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/snowflakedb/snowflake-jdbc/commit/8560bcca9d395d1ee02123536c2e958f7d386fe0">8560bcca9d395d1ee02123536c2e958f7d386fe0</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
A series of deserialization vulnerabilities have been discovered in Codehaus 1.9.x implemented in EAP 7. This CVE fixes CVE-2017-17485, CVE-2017-7525, CVE-2017-15095, CVE-2018-5968, CVE-2018-7489, CVE-2018-1000873, CVE-2019-12086 reported for FasterXML jackson-databind by implementing a whitelist approach that will mitigate these vulnerabilities and future ones alike.
<p>Publish Date: 2019-10-01
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-10202>CVE-2019-10202</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>9.8</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://access.redhat.com/errata/RHSA-2019:2938">https://access.redhat.com/errata/RHSA-2019:2938</a></p>
<p>Release Date: 2019-10-01</p>
<p>Fix Resolution: JBoss Enterprise Application Platform - 7.2.4;com.fasterxml.jackson.core:jackson-databind:2.9.9</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"Java","groupId":"com.fasterxml.jackson.core","packageName":"jackson-databind","packageVersion":"2.9.8","packageFilePaths":["/tmp/ws-ua_20220312003410_KQQKCS/archiveExtraction_BELGGC/FUIDAN/20220312003410/snowflake-jdbc_depth_0/dependencies/arrow-vector-0.15.1/META-INF/maven/org.apache.arrow/arrow-vector/pom.xml"],"isTransitiveDependency":false,"dependencyTree":"com.fasterxml.jackson.core:jackson-databind:2.9.8","isMinimumFixVersionAvailable":true,"minimumFixVersion":"JBoss Enterprise Application Platform - 7.2.4;com.fasterxml.jackson.core:jackson-databind:2.9.9","isBinary":false}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2019-10202","vulnerabilityDetails":"A series of deserialization vulnerabilities have been discovered in Codehaus 1.9.x implemented in EAP 7. This CVE fixes CVE-2017-17485, CVE-2017-7525, CVE-2017-15095, CVE-2018-5968, CVE-2018-7489, CVE-2018-1000873, CVE-2019-12086 reported for FasterXML jackson-databind by implementing a whitelist approach that will mitigate these vulnerabilities and future ones alike.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-10202","cvss3Severity":"high","cvss3Score":"9.8","cvss3Metrics":{"A":"High","AC":"Low","PR":"None","S":"Unchanged","C":"High","UI":"None","AV":"Network","I":"High"},"extraData":{}}</REMEDIATE> --> | True | SNOW-558862: CVE-2019-10202 (High) detected in jackson-databind-2.9.8.jar - autoclosed - ## CVE-2019-10202 - 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.8.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-ua_20220312003410_KQQKCS/archiveExtraction_BELGGC/FUIDAN/20220312003410/snowflake-jdbc_depth_0/dependencies/arrow-vector-0.15.1/META-INF/maven/org.apache.arrow/arrow-vector/pom.xml</p>
<p>Path to vulnerable library: /sitory/com/fasterxml/jackson/core/jackson-databind/2.9.8/jackson-databind-2.9.8.jar</p>
<p>
Dependency Hierarchy:
- :x: **jackson-databind-2.9.8.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/snowflakedb/snowflake-jdbc/commit/8560bcca9d395d1ee02123536c2e958f7d386fe0">8560bcca9d395d1ee02123536c2e958f7d386fe0</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
A series of deserialization vulnerabilities have been discovered in Codehaus 1.9.x implemented in EAP 7. This CVE fixes CVE-2017-17485, CVE-2017-7525, CVE-2017-15095, CVE-2018-5968, CVE-2018-7489, CVE-2018-1000873, CVE-2019-12086 reported for FasterXML jackson-databind by implementing a whitelist approach that will mitigate these vulnerabilities and future ones alike.
<p>Publish Date: 2019-10-01
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-10202>CVE-2019-10202</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>9.8</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://access.redhat.com/errata/RHSA-2019:2938">https://access.redhat.com/errata/RHSA-2019:2938</a></p>
<p>Release Date: 2019-10-01</p>
<p>Fix Resolution: JBoss Enterprise Application Platform - 7.2.4;com.fasterxml.jackson.core:jackson-databind:2.9.9</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"Java","groupId":"com.fasterxml.jackson.core","packageName":"jackson-databind","packageVersion":"2.9.8","packageFilePaths":["/tmp/ws-ua_20220312003410_KQQKCS/archiveExtraction_BELGGC/FUIDAN/20220312003410/snowflake-jdbc_depth_0/dependencies/arrow-vector-0.15.1/META-INF/maven/org.apache.arrow/arrow-vector/pom.xml"],"isTransitiveDependency":false,"dependencyTree":"com.fasterxml.jackson.core:jackson-databind:2.9.8","isMinimumFixVersionAvailable":true,"minimumFixVersion":"JBoss Enterprise Application Platform - 7.2.4;com.fasterxml.jackson.core:jackson-databind:2.9.9","isBinary":false}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2019-10202","vulnerabilityDetails":"A series of deserialization vulnerabilities have been discovered in Codehaus 1.9.x implemented in EAP 7. This CVE fixes CVE-2017-17485, CVE-2017-7525, CVE-2017-15095, CVE-2018-5968, CVE-2018-7489, CVE-2018-1000873, CVE-2019-12086 reported for FasterXML jackson-databind by implementing a whitelist approach that will mitigate these vulnerabilities and future ones alike.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-10202","cvss3Severity":"high","cvss3Score":"9.8","cvss3Metrics":{"A":"High","AC":"Low","PR":"None","S":"Unchanged","C":"High","UI":"None","AV":"Network","I":"High"},"extraData":{}}</REMEDIATE> --> | non_priority | snow cve high detected in jackson databind jar autoclosed 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 ua kqqkcs archiveextraction belggc fuidan snowflake jdbc depth dependencies arrow vector meta inf maven org apache arrow arrow vector pom xml path to vulnerable library sitory com fasterxml jackson core jackson databind jackson databind jar dependency hierarchy x jackson databind jar vulnerable library found in head commit a href found in base branch master vulnerability details a series of deserialization vulnerabilities have been discovered in codehaus x implemented in eap this cve fixes cve cve cve cve cve cve cve reported for fasterxml jackson databind by implementing a whitelist approach that will mitigate these vulnerabilities and future ones alike publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact high integrity impact high availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution jboss enterprise application platform com fasterxml jackson core jackson databind isopenpronvulnerability true ispackagebased true isdefaultbranch true packages istransitivedependency false dependencytree com fasterxml jackson core jackson databind isminimumfixversionavailable true minimumfixversion jboss enterprise application platform com fasterxml jackson core jackson databind isbinary false basebranches vulnerabilityidentifier cve vulnerabilitydetails a series of deserialization vulnerabilities have been discovered in codehaus x implemented in eap this cve fixes cve cve cve cve cve cve cve reported for fasterxml jackson databind by implementing a whitelist approach that will mitigate these vulnerabilities and future ones alike vulnerabilityurl | 0 |
61,893 | 12,196,459,197 | IssuesEvent | 2020-04-29 19:07:07 | kwk/test-llvm-bz-import-5 | https://api.github.com/repos/kwk/test-llvm-bz-import-5 | closed | Assertion `FieldNo < FieldCount && "Invalid Field No"' | BZ-BUG-STATUS: RESOLVED BZ-RESOLUTION: FIXED clang/LLVM Codegen dummy import from bugzilla | This issue was imported from Bugzilla https://bugs.llvm.org/show_bug.cgi?id=10912. | 1.0 | Assertion `FieldNo < FieldCount && "Invalid Field No"' - This issue was imported from Bugzilla https://bugs.llvm.org/show_bug.cgi?id=10912. | non_priority | assertion fieldno fieldcount invalid field no this issue was imported from bugzilla | 0 |
79,154 | 28,019,051,856 | IssuesEvent | 2023-03-28 02:48:38 | salsadigitalauorg/civictheme_source | https://api.github.com/repos/salsadigitalauorg/civictheme_source | opened | [DEFECT] Test Jira GH integration | Type: Defect | ### Summary
Summary
### Steps to reproduce
Steps
### Observed outcome
Observed
### Expected outcome
Expected | 1.0 | [DEFECT] Test Jira GH integration - ### Summary
Summary
### Steps to reproduce
Steps
### Observed outcome
Observed
### Expected outcome
Expected | non_priority | test jira gh integration summary summary steps to reproduce steps observed outcome observed expected outcome expected | 0 |
15,587 | 5,147,069,109 | IssuesEvent | 2017-01-13 04:57:19 | rubberduck-vba/Rubberduck | https://api.github.com/repos/rubberduck-vba/Rubberduck | closed | Code inspection allows refresh of project with missing references | bug code-explorer code-inspections | I managed to get a project with a missing reference (VBE warned on open). The status bar stuck on "Resolving references", which (I guess) was to be expected. However, the refresh button on the Code Inspection window was still active. So... being the button pusher that I am, I clicked on it and ended up with a perpetually spinning busy indicator with all of the parser states stuck in "Pending".
| 2.0 | Code inspection allows refresh of project with missing references - I managed to get a project with a missing reference (VBE warned on open). The status bar stuck on "Resolving references", which (I guess) was to be expected. However, the refresh button on the Code Inspection window was still active. So... being the button pusher that I am, I clicked on it and ended up with a perpetually spinning busy indicator with all of the parser states stuck in "Pending".
| non_priority | code inspection allows refresh of project with missing references i managed to get a project with a missing reference vbe warned on open the status bar stuck on resolving references which i guess was to be expected however the refresh button on the code inspection window was still active so being the button pusher that i am i clicked on it and ended up with a perpetually spinning busy indicator with all of the parser states stuck in pending | 0 |
357,549 | 25,176,403,391 | IssuesEvent | 2022-11-11 09:38:58 | jwdavis0200/pe | https://api.github.com/repos/jwdavis0200/pe | opened | Commons class is used by multiple classes but yet is not so in the architecture diagram. | type.DocumentationBug severity.VeryLow | 
The commons components is shown to be isolated here, which may confuse developers and give them the impression that it is either a deprecated component or an isolated component in the architecture.
However, later in the DG,
It is specified that the commons class is used by multiple components. Hence not accurate diagram.
<!--session: 1668154592408-aa02e40a-16e9-443e-95e5-0d6565bc2029-->
<!--Version: Web v3.4.4--> | 1.0 | Commons class is used by multiple classes but yet is not so in the architecture diagram. - 
The commons components is shown to be isolated here, which may confuse developers and give them the impression that it is either a deprecated component or an isolated component in the architecture.
However, later in the DG,
It is specified that the commons class is used by multiple components. Hence not accurate diagram.
<!--session: 1668154592408-aa02e40a-16e9-443e-95e5-0d6565bc2029-->
<!--Version: Web v3.4.4--> | non_priority | commons class is used by multiple classes but yet is not so in the architecture diagram the commons components is shown to be isolated here which may confuse developers and give them the impression that it is either a deprecated component or an isolated component in the architecture however later in the dg it is specified that the commons class is used by multiple components hence not accurate diagram | 0 |
96,965 | 8,638,743,436 | IssuesEvent | 2018-11-23 15:47:09 | EyeSeeTea/dhis2-newsletter | https://api.github.com/repos/EyeSeeTea/dhis2-newsletter | closed | Add unsubscribe link to newsletters | testing | Add Unsubscribe link to emails:
- [x] @mention Notifications
- [x] Newsletters | 1.0 | Add unsubscribe link to newsletters - Add Unsubscribe link to emails:
- [x] @mention Notifications
- [x] Newsletters | non_priority | add unsubscribe link to newsletters add unsubscribe link to emails mention notifications newsletters | 0 |
69,736 | 9,330,441,009 | IssuesEvent | 2019-03-28 06:56:13 | GluuFederation/oxTrust | https://api.github.com/repos/GluuFederation/oxTrust | closed | Add form for passport configuration management | Needs Documentation Needs screenshot new development | Related #1531
The `conf` section of `gluuPassportConfiguration` json looks like:
```
{
"serverURI": "...",
"serverWebPort": 8090,
"postProfileEndpoint": "...",
"spTLSCert": "...",
"spTLSKey": "...",
"logging": {
"level": "...",
"consoleLogOnly" : true/false,
"activeMQConf": {
"enabled": true/false,
"host": "...",
"username": "...",
"password": "...",
"port": "..."
}
}
```
We have to create a form to manage this data. There is already a POJO created for [this here](https://github.com/GluuFederation/oxCore/blob/master/oxService/src/main/java/org/xdi/model/passport/config/Configuration.java)
All fields are required except the `activeMQConf` section.
The possible values that `level` can take are the npm logging levels: error, warn, info, verbose, and debug
Hopefully, upon form submission we should validate `serverURI` and `postProfileEndpoint` are URLs (not arbitrary strings)
| 1.0 | Add form for passport configuration management - Related #1531
The `conf` section of `gluuPassportConfiguration` json looks like:
```
{
"serverURI": "...",
"serverWebPort": 8090,
"postProfileEndpoint": "...",
"spTLSCert": "...",
"spTLSKey": "...",
"logging": {
"level": "...",
"consoleLogOnly" : true/false,
"activeMQConf": {
"enabled": true/false,
"host": "...",
"username": "...",
"password": "...",
"port": "..."
}
}
```
We have to create a form to manage this data. There is already a POJO created for [this here](https://github.com/GluuFederation/oxCore/blob/master/oxService/src/main/java/org/xdi/model/passport/config/Configuration.java)
All fields are required except the `activeMQConf` section.
The possible values that `level` can take are the npm logging levels: error, warn, info, verbose, and debug
Hopefully, upon form submission we should validate `serverURI` and `postProfileEndpoint` are URLs (not arbitrary strings)
| non_priority | add form for passport configuration management related the conf section of gluupassportconfiguration json looks like serveruri serverwebport postprofileendpoint sptlscert sptlskey logging level consolelogonly true false activemqconf enabled true false host username password port we have to create a form to manage this data there is already a pojo created for all fields are required except the activemqconf section the possible values that level can take are the npm logging levels error warn info verbose and debug hopefully upon form submission we should validate serveruri and postprofileendpoint are urls not arbitrary strings | 0 |
21,009 | 11,046,548,123 | IssuesEvent | 2019-12-09 17:03:57 | statsmodels/statsmodels | https://api.github.com/repos/statsmodels/statsmodels | opened | REF/Review computational shortcuts for OLS outlier influence regression diagnostics | Performance comp-graphics comp-regression comp-stats comp-tools | outlier influence and similar regression diagnostics might still have some inefficient computations.
(I improved those as I semi-randomly found computational shortcuts)
article that summarizes several computational shortcuts
Velleman, Paul F., and Roy E. Welsch. 1981. “Efficient Computing of Regression Diagnostics.” The American Statistician 35 (4): 234–42. https://doi.org/10.2307/2683296.
one that I haven't seen before: section 3.1 catcher matrix which is just transposed `pinv(x)`
can be used to construct partial residual plot without explicit regression to partial out other variables.
e.g. statsmodels.graphics.regressionplots plot_partregress uses OLS to partial out other exog
i.e. we should be able to get partial regression residuals directly from pinv(x), but I haven't tried yet.
related
PRs #6265, #6268 and #2380 work with moment (`cov(xy)`) or product matrices (`x'x`) and not with `pinv(x)` and are focused on effects/influence of variables and not with effects of observations.
| True | REF/Review computational shortcuts for OLS outlier influence regression diagnostics - outlier influence and similar regression diagnostics might still have some inefficient computations.
(I improved those as I semi-randomly found computational shortcuts)
article that summarizes several computational shortcuts
Velleman, Paul F., and Roy E. Welsch. 1981. “Efficient Computing of Regression Diagnostics.” The American Statistician 35 (4): 234–42. https://doi.org/10.2307/2683296.
one that I haven't seen before: section 3.1 catcher matrix which is just transposed `pinv(x)`
can be used to construct partial residual plot without explicit regression to partial out other variables.
e.g. statsmodels.graphics.regressionplots plot_partregress uses OLS to partial out other exog
i.e. we should be able to get partial regression residuals directly from pinv(x), but I haven't tried yet.
related
PRs #6265, #6268 and #2380 work with moment (`cov(xy)`) or product matrices (`x'x`) and not with `pinv(x)` and are focused on effects/influence of variables and not with effects of observations.
| non_priority | ref review computational shortcuts for ols outlier influence regression diagnostics outlier influence and similar regression diagnostics might still have some inefficient computations i improved those as i semi randomly found computational shortcuts article that summarizes several computational shortcuts velleman paul f and roy e welsch “efficient computing of regression diagnostics ” the american statistician – one that i haven t seen before section catcher matrix which is just transposed pinv x can be used to construct partial residual plot without explicit regression to partial out other variables e g statsmodels graphics regressionplots plot partregress uses ols to partial out other exog i e we should be able to get partial regression residuals directly from pinv x but i haven t tried yet related prs and work with moment cov xy or product matrices x x and not with pinv x and are focused on effects influence of variables and not with effects of observations | 0 |
211,332 | 16,196,711,065 | IssuesEvent | 2021-05-04 15:22:38 | hashgraph/hedera-services | https://api.github.com/repos/hashgraph/hedera-services | closed | Reconnect test scenarios for Files | Test Development enhancement | **Summary**
Add reconnect test scenario in which the following file operations are done during and after reconnect
1. Files are created
2. Files are Updated
3. Files are Appended
Validate if the reconnect is successful with the file operations. | 1.0 | Reconnect test scenarios for Files - **Summary**
Add reconnect test scenario in which the following file operations are done during and after reconnect
1. Files are created
2. Files are Updated
3. Files are Appended
Validate if the reconnect is successful with the file operations. | non_priority | reconnect test scenarios for files summary add reconnect test scenario in which the following file operations are done during and after reconnect files are created files are updated files are appended validate if the reconnect is successful with the file operations | 0 |
206,747 | 23,396,871,822 | IssuesEvent | 2022-08-12 01:18:41 | Baneeishaque/comingsoon_03-colorlib | https://api.github.com/repos/Baneeishaque/comingsoon_03-colorlib | opened | CVE-2022-24785 (High) detected in moment-2.20.1.min.js | security vulnerability | ## CVE-2022-24785 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>moment-2.20.1.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.20.1/moment.min.js">https://cdnjs.cloudflare.com/ajax/libs/moment.js/2.20.1/moment.min.js</a></p>
<p>Path to dependency file: /index.html</p>
<p>Path to vulnerable library: /vendor/countdowntime/moment.min.js,/vendor/countdowntime/moment.min.js</p>
<p>
Dependency Hierarchy:
- :x: **moment-2.20.1.min.js** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/Baneeishaque/comingsoon_03-colorlib/commit/6437a6c55e104e9f959ac26e963b5a4843a5b8d7">6437a6c55e104e9f959ac26e963b5a4843a5b8d7</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>
Moment.js is a JavaScript date library for parsing, validating, manipulating, and formatting dates. A path traversal vulnerability impacts npm (server) users of Moment.js between versions 1.0.1 and 2.29.1, especially if a user-provided locale string is directly used to switch moment locale. This problem is patched in 2.29.2, and the patch can be applied to all affected versions. As a workaround, sanitize the user-provided locale name before passing it to Moment.js.
<p>Publish Date: 2022-04-04
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-24785>CVE-2022-24785</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: High
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/moment/moment/security/advisories/GHSA-8hfj-j24r-96c4">https://github.com/moment/moment/security/advisories/GHSA-8hfj-j24r-96c4</a></p>
<p>Release Date: 2022-04-04</p>
<p>Fix Resolution: moment - 2.29.2</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | CVE-2022-24785 (High) detected in moment-2.20.1.min.js - ## CVE-2022-24785 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>moment-2.20.1.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.20.1/moment.min.js">https://cdnjs.cloudflare.com/ajax/libs/moment.js/2.20.1/moment.min.js</a></p>
<p>Path to dependency file: /index.html</p>
<p>Path to vulnerable library: /vendor/countdowntime/moment.min.js,/vendor/countdowntime/moment.min.js</p>
<p>
Dependency Hierarchy:
- :x: **moment-2.20.1.min.js** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/Baneeishaque/comingsoon_03-colorlib/commit/6437a6c55e104e9f959ac26e963b5a4843a5b8d7">6437a6c55e104e9f959ac26e963b5a4843a5b8d7</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>
Moment.js is a JavaScript date library for parsing, validating, manipulating, and formatting dates. A path traversal vulnerability impacts npm (server) users of Moment.js between versions 1.0.1 and 2.29.1, especially if a user-provided locale string is directly used to switch moment locale. This problem is patched in 2.29.2, and the patch can be applied to all affected versions. As a workaround, sanitize the user-provided locale name before passing it to Moment.js.
<p>Publish Date: 2022-04-04
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-24785>CVE-2022-24785</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: High
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/moment/moment/security/advisories/GHSA-8hfj-j24r-96c4">https://github.com/moment/moment/security/advisories/GHSA-8hfj-j24r-96c4</a></p>
<p>Release Date: 2022-04-04</p>
<p>Fix Resolution: moment - 2.29.2</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 moment min js cve high severity vulnerability vulnerable library moment min js parse validate manipulate and display dates library home page a href path to dependency file index html path to vulnerable library vendor countdowntime moment min js vendor countdowntime moment min js dependency hierarchy x moment min js vulnerable library found in head commit a href vulnerability details moment js is a javascript date library for parsing validating manipulating and formatting dates a path traversal vulnerability impacts npm server users of moment js between versions and especially if a user provided locale string is directly used to switch moment locale this problem is patched in and the patch can be applied to all affected versions as a workaround sanitize the user provided locale name before passing it to moment js publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact none integrity impact high availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution moment step up your open source security game with mend | 0 |
4,267 | 3,342,867,400 | IssuesEvent | 2015-11-15 00:46:52 | SecUpwN/Android-IMSI-Catcher-Detector | https://api.github.com/repos/SecUpwN/Android-IMSI-Catcher-Detector | reopened | Build: Automatic version and app name update with Gradle | BUILD ENHANCEMENT | Implement automatic build and version updates when using Travis-CI and Gradle, to build our App.
The `build.gradle` script to do this, is described [HERE](http://bryankrosenbaum.com/2013/11/27/getting-to-know-gradle-auto-increment-version-and-signing-releases/), and lastest version can be found [HERE](https://github.com/bryanro/later-android/blob/master/Later/build.gradle). This would obviously require a few modifications in the *RegEx* as our build string is different, including changing the correct min/max of the supported API. (min=API-**17**, max=?)
```xml
<manifest xmlns:android="http://schemas.android.com/apk/res/android"
package="com.SecUpwN.AIMSICD"
android:versionCode="24"
android:versionName="0.1.24-alpha-build-12">
```
The link above also provide a way to implement automatic APK signing, using a [signing.properties](https://github.com/bryanro/later-android/blob/master/signing.properties) file.
And [HERE](http://toastdroid.com/2014/03/28/customizing-your-build-with-gradle/) is a way to automatically name the built APK. | 1.0 | Build: Automatic version and app name update with Gradle - Implement automatic build and version updates when using Travis-CI and Gradle, to build our App.
The `build.gradle` script to do this, is described [HERE](http://bryankrosenbaum.com/2013/11/27/getting-to-know-gradle-auto-increment-version-and-signing-releases/), and lastest version can be found [HERE](https://github.com/bryanro/later-android/blob/master/Later/build.gradle). This would obviously require a few modifications in the *RegEx* as our build string is different, including changing the correct min/max of the supported API. (min=API-**17**, max=?)
```xml
<manifest xmlns:android="http://schemas.android.com/apk/res/android"
package="com.SecUpwN.AIMSICD"
android:versionCode="24"
android:versionName="0.1.24-alpha-build-12">
```
The link above also provide a way to implement automatic APK signing, using a [signing.properties](https://github.com/bryanro/later-android/blob/master/signing.properties) file.
And [HERE](http://toastdroid.com/2014/03/28/customizing-your-build-with-gradle/) is a way to automatically name the built APK. | non_priority | build automatic version and app name update with gradle implement automatic build and version updates when using travis ci and gradle to build our app the build gradle script to do this is described and lastest version can be found this would obviously require a few modifications in the regex as our build string is different including changing the correct min max of the supported api min api max xml manifest xmlns android package com secupwn aimsicd android versioncode android versionname alpha build the link above also provide a way to implement automatic apk signing using a file and is a way to automatically name the built apk | 0 |
86,816 | 15,755,875,730 | IssuesEvent | 2021-03-31 02:32:25 | turkdevops/node | https://api.github.com/repos/turkdevops/node | opened | WS-2017-0266 (Low) detected in http-signature-0.10.0.tgz | security vulnerability | ## WS-2017-0266 - Low Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>http-signature-0.10.0.tgz</b></p></summary>
<p>Reference implementation of Joyent's HTTP Signature Scheme</p>
<p>Library home page: <a href="https://registry.npmjs.org/http-signature/-/http-signature-0.10.0.tgz">https://registry.npmjs.org/http-signature/-/http-signature-0.10.0.tgz</a></p>
<p>Path to dependency file: node/deps/npm/package.json</p>
<p>Path to vulnerable library: node/deps/npm/node_modules/request/node_modules/http-signature/package.json</p>
<p>
Dependency Hierarchy:
- request-2.42.0.tgz (Root Library)
- :x: **http-signature-0.10.0.tgz** (Vulnerable Library)
<p>Found in base branch: <b>archived-io.js-v0.10</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/low_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
Affected versions (before 1.0.0) of the http-signature package are vulnerable to Timing Attacks.
<p>Publish Date: 2015-01-22
<p>URL: <a href=https://github.com/joyent/node-http-signature/commit/78ab1da232f31f695f5c362d863593a143aa8b56>WS-2017-0266</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>3.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Adjacent
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: None
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/joyent/node-http-signature/pull/36">https://github.com/joyent/node-http-signature/pull/36</a></p>
<p>Release Date: 2017-01-31</p>
<p>Fix Resolution: 1.0.0</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | WS-2017-0266 (Low) detected in http-signature-0.10.0.tgz - ## WS-2017-0266 - Low Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>http-signature-0.10.0.tgz</b></p></summary>
<p>Reference implementation of Joyent's HTTP Signature Scheme</p>
<p>Library home page: <a href="https://registry.npmjs.org/http-signature/-/http-signature-0.10.0.tgz">https://registry.npmjs.org/http-signature/-/http-signature-0.10.0.tgz</a></p>
<p>Path to dependency file: node/deps/npm/package.json</p>
<p>Path to vulnerable library: node/deps/npm/node_modules/request/node_modules/http-signature/package.json</p>
<p>
Dependency Hierarchy:
- request-2.42.0.tgz (Root Library)
- :x: **http-signature-0.10.0.tgz** (Vulnerable Library)
<p>Found in base branch: <b>archived-io.js-v0.10</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/low_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
Affected versions (before 1.0.0) of the http-signature package are vulnerable to Timing Attacks.
<p>Publish Date: 2015-01-22
<p>URL: <a href=https://github.com/joyent/node-http-signature/commit/78ab1da232f31f695f5c362d863593a143aa8b56>WS-2017-0266</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>3.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Adjacent
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: None
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/joyent/node-http-signature/pull/36">https://github.com/joyent/node-http-signature/pull/36</a></p>
<p>Release Date: 2017-01-31</p>
<p>Fix Resolution: 1.0.0</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_priority | ws low detected in http signature tgz ws low severity vulnerability vulnerable library http signature tgz reference implementation of joyent s http signature scheme library home page a href path to dependency file node deps npm package json path to vulnerable library node deps npm node modules request node modules http signature package json dependency hierarchy request tgz root library x http signature tgz vulnerable library found in base branch archived io js vulnerability details affected versions before of the http signature package are vulnerable to timing attacks publish date url a href cvss score details base score metrics exploitability metrics attack vector adjacent attack complexity low privileges required none user interaction required 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 step up your open source security game with whitesource | 0 |
27,350 | 6,841,269,583 | IssuesEvent | 2017-11-11 11:22:06 | justDoji/TrackMeUp | https://api.github.com/repos/justDoji/TrackMeUp | opened | QualityAssurance: increase test coverage of Java component | code-quality | Increase the test coverage indicated by the Sonar Cloud analysis.
Target coverage is 70%, only non-trivial functions should be tested.
(no private constructor or getter tests). | 1.0 | QualityAssurance: increase test coverage of Java component - Increase the test coverage indicated by the Sonar Cloud analysis.
Target coverage is 70%, only non-trivial functions should be tested.
(no private constructor or getter tests). | non_priority | qualityassurance increase test coverage of java component increase the test coverage indicated by the sonar cloud analysis target coverage is only non trivial functions should be tested no private constructor or getter tests | 0 |
132,485 | 12,509,501,577 | IssuesEvent | 2020-06-02 17:08:48 | nipype/pydra | https://api.github.com/repos/nipype/pydra | opened | Expand docstrings in specs.py and core.py to numpy docstring style | documentation | Docstrings are not complete, so it's not clear how the classes are related to each other and what some of the functions and class methods do etc. | 1.0 | Expand docstrings in specs.py and core.py to numpy docstring style - Docstrings are not complete, so it's not clear how the classes are related to each other and what some of the functions and class methods do etc. | non_priority | expand docstrings in specs py and core py to numpy docstring style docstrings are not complete so it s not clear how the classes are related to each other and what some of the functions and class methods do etc | 0 |
109,714 | 9,411,676,933 | IssuesEvent | 2019-04-10 00:31:07 | filecoin-project/go-filecoin | https://api.github.com/repos/filecoin-project/go-filecoin | opened | Resolve long low-CPU delays during tests | A-tests C-dev-productivity | ### Description
When running tests, I observe periods of intense CPU work and periods where my CPU is near idle (maybe 1 core working). This suggests that the total duration required to run tests is longer than necessary, not constrained by resources. My guess is that there are some lengthy tests that are not but should be marked as parallel.
### Acceptance criteria
- Tests consume all resources available on a typical developer machine in the name of finishing as quickly as possible.
### Risks + pitfalls
If the tests to be parallelised are very memory intensive they may put more pressure on CI builds, see #2516.
### Where to begin
Evaluate which test functions are not marked parallel. | 1.0 | Resolve long low-CPU delays during tests - ### Description
When running tests, I observe periods of intense CPU work and periods where my CPU is near idle (maybe 1 core working). This suggests that the total duration required to run tests is longer than necessary, not constrained by resources. My guess is that there are some lengthy tests that are not but should be marked as parallel.
### Acceptance criteria
- Tests consume all resources available on a typical developer machine in the name of finishing as quickly as possible.
### Risks + pitfalls
If the tests to be parallelised are very memory intensive they may put more pressure on CI builds, see #2516.
### Where to begin
Evaluate which test functions are not marked parallel. | non_priority | resolve long low cpu delays during tests description when running tests i observe periods of intense cpu work and periods where my cpu is near idle maybe core working this suggests that the total duration required to run tests is longer than necessary not constrained by resources my guess is that there are some lengthy tests that are not but should be marked as parallel acceptance criteria tests consume all resources available on a typical developer machine in the name of finishing as quickly as possible risks pitfalls if the tests to be parallelised are very memory intensive they may put more pressure on ci builds see where to begin evaluate which test functions are not marked parallel | 0 |
160,881 | 20,120,316,292 | IssuesEvent | 2022-02-08 01:07:02 | AkshayMukkavilli/Tensorflow | https://api.github.com/repos/AkshayMukkavilli/Tensorflow | opened | CVE-2022-23573 (High) detected in tensorflow-1.13.1-cp27-cp27mu-manylinux1_x86_64.whl | security vulnerability | ## CVE-2022-23573 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>tensorflow-1.13.1-cp27-cp27mu-manylinux1_x86_64.whl</b></p></summary>
<p>TensorFlow is an open source machine learning framework for everyone.</p>
<p>Library home page: <a href="https://files.pythonhosted.org/packages/d2/ea/ab2c8c0e81bd051cc1180b104c75a865ab0fc66c89be992c4b20bbf6d624/tensorflow-1.13.1-cp27-cp27mu-manylinux1_x86_64.whl">https://files.pythonhosted.org/packages/d2/ea/ab2c8c0e81bd051cc1180b104c75a865ab0fc66c89be992c4b20bbf6d624/tensorflow-1.13.1-cp27-cp27mu-manylinux1_x86_64.whl</a></p>
<p>Path to dependency file: /Tensorflow/src/requirements.txt</p>
<p>Path to vulnerable library: /teSource-ArchiveExtractor_5ea86033-7612-4210-97f3-8edb65806ddf/20190525011619_2843/20190525011537_depth_0/2/tensorflow-1.13.1-cp27-cp27mu-manylinux1_x86_64/tensorflow-1.13.1.data/purelib/tensorflow</p>
<p>
Dependency Hierarchy:
- :x: **tensorflow-1.13.1-cp27-cp27mu-manylinux1_x86_64.whl** (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>
Tensorflow is an Open Source Machine Learning Framework. The implementation of `AssignOp` can result in copying uninitialized data to a new tensor. This later results in undefined behavior. The implementation has a check that the left hand side of the assignment is initialized (to minimize number of allocations), but does not check that the right hand side is also initialized. The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.3, as these are also affected and still in supported range.
<p>Publish Date: 2022-02-04
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-23573>CVE-2022-23573</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.6</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: Low
- Integrity Impact: Low
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/tensorflow/tensorflow/security/advisories/GHSA-q85f-69q7-55h2">https://github.com/tensorflow/tensorflow/security/advisories/GHSA-q85f-69q7-55h2</a></p>
<p>Release Date: 2022-02-04</p>
<p>Fix Resolution: tensorflow - 2.5.3,2.6.3,2.7.1,2.8.0;tensorflow-cpu - 2.5.3,2.6.3,2.7.1,2.8.0;tensorflow-gpu - 2.5.3,2.6.3,2.7.1,2.8.0</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | CVE-2022-23573 (High) detected in tensorflow-1.13.1-cp27-cp27mu-manylinux1_x86_64.whl - ## CVE-2022-23573 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>tensorflow-1.13.1-cp27-cp27mu-manylinux1_x86_64.whl</b></p></summary>
<p>TensorFlow is an open source machine learning framework for everyone.</p>
<p>Library home page: <a href="https://files.pythonhosted.org/packages/d2/ea/ab2c8c0e81bd051cc1180b104c75a865ab0fc66c89be992c4b20bbf6d624/tensorflow-1.13.1-cp27-cp27mu-manylinux1_x86_64.whl">https://files.pythonhosted.org/packages/d2/ea/ab2c8c0e81bd051cc1180b104c75a865ab0fc66c89be992c4b20bbf6d624/tensorflow-1.13.1-cp27-cp27mu-manylinux1_x86_64.whl</a></p>
<p>Path to dependency file: /Tensorflow/src/requirements.txt</p>
<p>Path to vulnerable library: /teSource-ArchiveExtractor_5ea86033-7612-4210-97f3-8edb65806ddf/20190525011619_2843/20190525011537_depth_0/2/tensorflow-1.13.1-cp27-cp27mu-manylinux1_x86_64/tensorflow-1.13.1.data/purelib/tensorflow</p>
<p>
Dependency Hierarchy:
- :x: **tensorflow-1.13.1-cp27-cp27mu-manylinux1_x86_64.whl** (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>
Tensorflow is an Open Source Machine Learning Framework. The implementation of `AssignOp` can result in copying uninitialized data to a new tensor. This later results in undefined behavior. The implementation has a check that the left hand side of the assignment is initialized (to minimize number of allocations), but does not check that the right hand side is also initialized. The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.3, as these are also affected and still in supported range.
<p>Publish Date: 2022-02-04
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-23573>CVE-2022-23573</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.6</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: Low
- Integrity Impact: Low
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/tensorflow/tensorflow/security/advisories/GHSA-q85f-69q7-55h2">https://github.com/tensorflow/tensorflow/security/advisories/GHSA-q85f-69q7-55h2</a></p>
<p>Release Date: 2022-02-04</p>
<p>Fix Resolution: tensorflow - 2.5.3,2.6.3,2.7.1,2.8.0;tensorflow-cpu - 2.5.3,2.6.3,2.7.1,2.8.0;tensorflow-gpu - 2.5.3,2.6.3,2.7.1,2.8.0</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_priority | cve high detected in tensorflow whl cve high severity vulnerability vulnerable library tensorflow whl tensorflow is an open source machine learning framework for everyone library home page a href path to dependency file tensorflow src requirements txt path to vulnerable library tesource archiveextractor depth tensorflow tensorflow data purelib tensorflow dependency hierarchy x tensorflow whl vulnerable library vulnerability details tensorflow is an open source machine learning framework the implementation of assignop can result in copying uninitialized data to a new tensor this later results in undefined behavior the implementation has a check that the left hand side of the assignment is initialized to minimize number of allocations but does not check that the right hand side is also initialized the fix will be included in tensorflow we will also cherrypick this commit on tensorflow tensorflow and tensorflow as these are also affected and still in supported range publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required low user interaction none scope unchanged impact metrics confidentiality impact low integrity impact low availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution tensorflow tensorflow cpu tensorflow gpu step up your open source security game with whitesource | 0 |
3,304 | 12,749,105,772 | IssuesEvent | 2020-06-26 21:46:43 | tgstation/tgstation-server | https://api.github.com/repos/tgstation/tgstation-server | closed | Create a checklist for the release process | CI Maintainability Issue Work In Progress | Things to include
- Release note touchup on PRs
- Major/Minor/Patch selection
- API/Client/Server versioning
- Proper use of TGSDeploy and NugetDeploy
- Announcement channels | True | Create a checklist for the release process - Things to include
- Release note touchup on PRs
- Major/Minor/Patch selection
- API/Client/Server versioning
- Proper use of TGSDeploy and NugetDeploy
- Announcement channels | non_priority | create a checklist for the release process things to include release note touchup on prs major minor patch selection api client server versioning proper use of tgsdeploy and nugetdeploy announcement channels | 0 |
245,549 | 18,787,332,601 | IssuesEvent | 2021-11-08 13:32:05 | philippabele/irrigation-springler | https://api.github.com/repos/philippabele/irrigation-springler | closed | Update readme / literature review | documentation | - Inform the reader about, what work has been done before. What ideas and models have already been developed.
- List the relevant literature, blogs, educational platforms and sites to highlight sources for background information of this project.
| 1.0 | Update readme / literature review - - Inform the reader about, what work has been done before. What ideas and models have already been developed.
- List the relevant literature, blogs, educational platforms and sites to highlight sources for background information of this project.
| non_priority | update readme literature review inform the reader about what work has been done before what ideas and models have already been developed list the relevant literature blogs educational platforms and sites to highlight sources for background information of this project | 0 |
356,181 | 25,176,131,301 | IssuesEvent | 2022-11-11 09:25:16 | autumn-sonata/pe | https://api.github.com/repos/autumn-sonata/pe | opened | [User guide] Some commands lacking any visuals to aid the user in following along with the examples | severity.VeryLow type.DocumentationBug |
In this case, to better distinguish between the `find` and `filter` command, there should be an example with visuals.
<!--session: 1668154499182-004918ce-c7c4-4d19-a42b-a278b5192249-->
<!--Version: Web v3.4.4--> | 1.0 | [User guide] Some commands lacking any visuals to aid the user in following along with the examples -
In this case, to better distinguish between the `find` and `filter` command, there should be an example with visuals.
<!--session: 1668154499182-004918ce-c7c4-4d19-a42b-a278b5192249-->
<!--Version: Web v3.4.4--> | non_priority | some commands lacking any visuals to aid the user in following along with the examples in this case to better distinguish between the find and filter command there should be an example with visuals | 0 |
291,207 | 21,917,624,928 | IssuesEvent | 2022-05-22 04:01:19 | cynkra/dm | https://api.github.com/repos/cynkra/dm | closed | Remove all calls of soft deprecated functionalities | documentation | an example:
https://github.com/cynkra/dm/blob/0cd852445b5e41fcc93fc2f428bf02c22d2cc165/vignettes/tech-dm-join.Rmd#L98-L100
results the following:
Looking into the code - there are more soft-deprecated functions. Would be worth to clean this up.
| 1.0 | Remove all calls of soft deprecated functionalities - an example:
https://github.com/cynkra/dm/blob/0cd852445b5e41fcc93fc2f428bf02c22d2cc165/vignettes/tech-dm-join.Rmd#L98-L100
results the following:
Looking into the code - there are more soft-deprecated functions. Would be worth to clean this up.
| non_priority | remove all calls of soft deprecated functionalities an example results the following looking into the code there are more soft deprecated functions would be worth to clean this up | 0 |
178,936 | 13,804,666,674 | IssuesEvent | 2020-10-11 10:06:42 | add-ons/plugin.video.vtm.go | https://api.github.com/repos/add-ons/plugin.video.vtm.go | closed | Run some CI tests every few hours to check authentication flow | testing | Given the recent breakages in the login flow, it would make sense to run some CI tests related to authentication every few hours. Maybe like every 6 hours, that's 4 times a day.
@dagwieers can you help with that? I think you've set that up for VRT NU. Do we get an e-mail when something breaks? | 1.0 | Run some CI tests every few hours to check authentication flow - Given the recent breakages in the login flow, it would make sense to run some CI tests related to authentication every few hours. Maybe like every 6 hours, that's 4 times a day.
@dagwieers can you help with that? I think you've set that up for VRT NU. Do we get an e-mail when something breaks? | non_priority | run some ci tests every few hours to check authentication flow given the recent breakages in the login flow it would make sense to run some ci tests related to authentication every few hours maybe like every hours that s times a day dagwieers can you help with that i think you ve set that up for vrt nu do we get an e mail when something breaks | 0 |
1,637 | 2,613,015,160 | IssuesEvent | 2015-02-27 18:08:07 | scento/lingua | https://api.github.com/repos/scento/lingua | opened | CLDR Language | documentation feature implementation testcase | **Implementation:**
The class `\Lingua\Setup\Processor\CldrLanguage` should process the data generated by `Lingua\Setup\Downloader\Iana`, `Lingua\Setup\Downloader\Icu` and `Lingua\Setup\Downloader\Sil` to generate the following files:
* `iso639-1.json`
* `iso639-1_to_iso639-3.json`
* `iso639-1_to_bcp47.json`
* `iso639-3.json`
* `iso639-3_to_iso639-1.json`
* `iso639-3_to_bcp47.json`
* `bcp47_to_iso639-1.json`
* `bcp47_to_iso639-3.json`
There is no `bcp47.json`, since the BCP47 codes are aggregated and do not only contain the language part, which is represented by this class. The method `getSubsystem()` must always return `Language`.
**Testcase:**
The testcase should cover the entire implementation. Please ensure, that all functions verify, that the parameters match the expected type. In case the base data is not available, an Exception must be thrown. Also throw an Exception, in case the Downloaders are not available, no `Setup` is available or no destination is available. Since new files must be created, the `process()` function must throw an Exception, when the destination directory is not writable or any other error occur.
**Documentation:**
The documentation to this class should cover the input and output files, a list of the dependencies regarding Downloaders and an short overview about the basic functionality. As always, UML diagrams should be added to illustrate the subsystem integration.
**Integration:**
The caching feature of `composer install` must be removed, since the user needs to accept the SIL license and the data must be downloaded from their page. This processor combines the SIL and data from other sources, which might be unavailable in that context.
---
 | 1.0 | CLDR Language - **Implementation:**
The class `\Lingua\Setup\Processor\CldrLanguage` should process the data generated by `Lingua\Setup\Downloader\Iana`, `Lingua\Setup\Downloader\Icu` and `Lingua\Setup\Downloader\Sil` to generate the following files:
* `iso639-1.json`
* `iso639-1_to_iso639-3.json`
* `iso639-1_to_bcp47.json`
* `iso639-3.json`
* `iso639-3_to_iso639-1.json`
* `iso639-3_to_bcp47.json`
* `bcp47_to_iso639-1.json`
* `bcp47_to_iso639-3.json`
There is no `bcp47.json`, since the BCP47 codes are aggregated and do not only contain the language part, which is represented by this class. The method `getSubsystem()` must always return `Language`.
**Testcase:**
The testcase should cover the entire implementation. Please ensure, that all functions verify, that the parameters match the expected type. In case the base data is not available, an Exception must be thrown. Also throw an Exception, in case the Downloaders are not available, no `Setup` is available or no destination is available. Since new files must be created, the `process()` function must throw an Exception, when the destination directory is not writable or any other error occur.
**Documentation:**
The documentation to this class should cover the input and output files, a list of the dependencies regarding Downloaders and an short overview about the basic functionality. As always, UML diagrams should be added to illustrate the subsystem integration.
**Integration:**
The caching feature of `composer install` must be removed, since the user needs to accept the SIL license and the data must be downloaded from their page. This processor combines the SIL and data from other sources, which might be unavailable in that context.
---
 | non_priority | cldr language implementation the class lingua setup processor cldrlanguage should process the data generated by lingua setup downloader iana lingua setup downloader icu and lingua setup downloader sil to generate the following files json to json to json json to json to json to json to json there is no json since the codes are aggregated and do not only contain the language part which is represented by this class the method getsubsystem must always return language testcase the testcase should cover the entire implementation please ensure that all functions verify that the parameters match the expected type in case the base data is not available an exception must be thrown also throw an exception in case the downloaders are not available no setup is available or no destination is available since new files must be created the process function must throw an exception when the destination directory is not writable or any other error occur documentation the documentation to this class should cover the input and output files a list of the dependencies regarding downloaders and an short overview about the basic functionality as always uml diagrams should be added to illustrate the subsystem integration integration the caching feature of composer install must be removed since the user needs to accept the sil license and the data must be downloaded from their page this processor combines the sil and data from other sources which might be unavailable in that context | 0 |
303,945 | 26,240,851,904 | IssuesEvent | 2023-01-05 11:21:25 | woocommerce/woocommerce-blocks | https://api.github.com/repos/woocommerce/woocommerce-blocks | closed | Product Query: [Tests] Add E2E tests for Popular Filters | category: tests 🔹 block-type: product-query | The test should cover:
- Newest
- Best Selling
- Top rated
We should test against a reference to avoid false positive tests. A possible reference is the WooCommerce products shortcode. | 1.0 | Product Query: [Tests] Add E2E tests for Popular Filters - The test should cover:
- Newest
- Best Selling
- Top rated
We should test against a reference to avoid false positive tests. A possible reference is the WooCommerce products shortcode. | non_priority | product query add tests for popular filters the test should cover newest best selling top rated we should test against a reference to avoid false positive tests a possible reference is the woocommerce products shortcode | 0 |
284,166 | 30,913,598,962 | IssuesEvent | 2023-08-05 02:21:24 | Satheesh575555/linux-4.1.15_CVE-2022-45934 | https://api.github.com/repos/Satheesh575555/linux-4.1.15_CVE-2022-45934 | reopened | CVE-2022-24958 (High) detected in linuxlinux-4.6 | Mend: dependency security vulnerability | ## CVE-2022-24958 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>linuxlinux-4.6</b></p></summary>
<p>
<p>The Linux Kernel</p>
<p>Library home page: <a href=https://mirrors.edge.kernel.org/pub/linux/kernel/v4.x/?wsslib=linux>https://mirrors.edge.kernel.org/pub/linux/kernel/v4.x/?wsslib=linux</a></p>
<p>Found in HEAD commit: <a href="https://github.com/Satheesh575555/linux-4.1.15_CVE-2022-45934/commit/7c0b143b43394df131d83e9aecb3c5518edc127a">7c0b143b43394df131d83e9aecb3c5518edc127a</a></p>
<p>Found in base branch: <b>master</b></p></p>
</details>
</p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Source Files (1)</summary>
<p></p>
<p>
</p>
</details>
<p></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> Vulnerability Details</summary>
<p>
drivers/usb/gadget/legacy/inode.c in the Linux kernel through 5.16.8 mishandles dev->buf release.
<p>Publish Date: 2022-02-11
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-24958>CVE-2022-24958</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.8</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-24958">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-24958</a></p>
<p>Release Date: 2022-02-11</p>
<p>Fix Resolution: v5.16</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | CVE-2022-24958 (High) detected in linuxlinux-4.6 - ## CVE-2022-24958 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>linuxlinux-4.6</b></p></summary>
<p>
<p>The Linux Kernel</p>
<p>Library home page: <a href=https://mirrors.edge.kernel.org/pub/linux/kernel/v4.x/?wsslib=linux>https://mirrors.edge.kernel.org/pub/linux/kernel/v4.x/?wsslib=linux</a></p>
<p>Found in HEAD commit: <a href="https://github.com/Satheesh575555/linux-4.1.15_CVE-2022-45934/commit/7c0b143b43394df131d83e9aecb3c5518edc127a">7c0b143b43394df131d83e9aecb3c5518edc127a</a></p>
<p>Found in base branch: <b>master</b></p></p>
</details>
</p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Source Files (1)</summary>
<p></p>
<p>
</p>
</details>
<p></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> Vulnerability Details</summary>
<p>
drivers/usb/gadget/legacy/inode.c in the Linux kernel through 5.16.8 mishandles dev->buf release.
<p>Publish Date: 2022-02-11
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-24958>CVE-2022-24958</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.8</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-24958">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-24958</a></p>
<p>Release Date: 2022-02-11</p>
<p>Fix Resolution: v5.16</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_priority | cve high detected in linuxlinux cve high severity vulnerability vulnerable library linuxlinux the linux kernel library home page a href found in head commit a href found in base branch master vulnerable source files vulnerability details drivers usb gadget legacy inode c in the linux kernel through mishandles dev buf release publish date url a href cvss score details base score metrics exploitability metrics attack vector local attack complexity low privileges required low user interaction none scope unchanged impact metrics confidentiality impact high integrity impact high availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution step up your open source security game with mend | 0 |
115,765 | 24,808,303,072 | IssuesEvent | 2022-10-25 07:22:45 | sast-automation-dev/railsgoat-45 | https://api.github.com/repos/sast-automation-dev/railsgoat-45 | opened | Code Security Report: 20 high severity findings, 30 total findings | code security findings | # Code Security Report
**Latest Scan:** 2022-10-25 07:20am
**Total Findings:** 30
**Tested Project Files:** 134
**Detected Programming Languages:** 2
<!-- SAST-MANUAL-SCAN-START -->
- [ ] Check this box to manually trigger a scan
<!-- SAST-MANUAL-SCAN-END -->
## Language: JavaScript / Node.js
| Severity | CWE | Vulnerability Type | Count |
|-|-|-|-|
|<img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium|[CWE-338](https://cwe.mitre.org/data/definitions/338.html)|Weak Pseudo-Random|2|
### Details
> No high vulnerability findings detected. To view information on the remaining findings, navigate to the [Mend SAST Application](https://dev.whitesourcesoftware.com/sast/#/scans/714406f6-bc99-47d7-b72f-612cc14ee022/details).
## Language: Ruby
| Severity | CWE | Vulnerability Type | Count |
|-|-|-|-|
|<img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High|[CWE-78](https://cwe.mitre.org/data/definitions/78.html)|Command Injection|4|
|<img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High|[CWE-89](https://cwe.mitre.org/data/definitions/89.html)|SQL Injection|1|
|<img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High|[CWE-22](https://cwe.mitre.org/data/definitions/22.html)|Path/Directory Traversal|3|
|<img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High|[CWE-915](https://cwe.mitre.org/data/definitions/915.html)|Mass Assignment|1|
|<img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High|[CWE-79](https://cwe.mitre.org/data/definitions/79.html)|Dangerous HTML Embedded|10|
|<img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High|[CWE-79](https://cwe.mitre.org/data/definitions/79.html)|Cross-Site Scripting|1|
|<img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium|[CWE-321](https://cwe.mitre.org/data/definitions/321.html)|Secret Key In Source|1|
|<img src='https://whitesource-resources.whitesourcesoftware.com/low_vul.png' width=19 height=20> Low|[CWE-916](https://cwe.mitre.org/data/definitions/916.html)|Weak Hash Strength|5|
|<img src='https://whitesource-resources.whitesourcesoftware.com/low_vul.png' width=19 height=20> Low|[CWE-113](https://cwe.mitre.org/data/definitions/113.html)|HTTP Response Splitting|1|
|<img src='https://whitesource-resources.whitesourcesoftware.com/low_vul.png' width=19 height=20> Low|[CWE-1004](https://cwe.mitre.org/data/definitions/1004.html)|Cookie Without 'HttpOnly' Flag|1|
### Details
> The below list presents the 20 high vulnerability findings that need your attention. To view information on these findings, navigate to the [Mend SAST Application](https://dev.whitesourcesoftware.com/sast/#/scans/714406f6-bc99-47d7-b72f-612cc14ee022/details).
<details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20>Command Injection (CWE-78) : 4</summary>
#### Findings
<details>
<summary>models/benefits.rb:15</summary>
https://github.com/sast-automation-dev/railsgoat-45/blob/4af0b15b213fca0ddfbdcf696e5803947b8bc1a2/railsgoat-45/app/models/benefits.rb#L10-L15
<details>
<summary> Trace </summary>
https://github.com/sast-automation-dev/railsgoat-45/blob/4af0b15b213fca0ddfbdcf696e5803947b8bc1a2/railsgoat-45/app/controllers/benefit_forms_controller.rb#L19
https://github.com/sast-automation-dev/railsgoat-45/blob/4af0b15b213fca0ddfbdcf696e5803947b8bc1a2/railsgoat-45/app/models/benefits.rb#L4
https://github.com/sast-automation-dev/railsgoat-45/blob/4af0b15b213fca0ddfbdcf696e5803947b8bc1a2/railsgoat-45/app/models/benefits.rb#L15
</details>
</details>
<details>
<summary>models/benefits.rb:15</summary>
https://github.com/sast-automation-dev/railsgoat-45/blob/4af0b15b213fca0ddfbdcf696e5803947b8bc1a2/railsgoat-45/app/models/benefits.rb#L10-L15
<details>
<summary> Trace </summary>
https://github.com/sast-automation-dev/railsgoat-45/blob/4af0b15b213fca0ddfbdcf696e5803947b8bc1a2/railsgoat-45/app/controllers/benefit_forms_controller.rb#L19
https://github.com/sast-automation-dev/railsgoat-45/blob/4af0b15b213fca0ddfbdcf696e5803947b8bc1a2/railsgoat-45/app/models/benefits.rb#L4
https://github.com/sast-automation-dev/railsgoat-45/blob/4af0b15b213fca0ddfbdcf696e5803947b8bc1a2/railsgoat-45/app/models/benefits.rb#L6
https://github.com/sast-automation-dev/railsgoat-45/blob/4af0b15b213fca0ddfbdcf696e5803947b8bc1a2/railsgoat-45/app/models/benefits.rb#L13
https://github.com/sast-automation-dev/railsgoat-45/blob/4af0b15b213fca0ddfbdcf696e5803947b8bc1a2/railsgoat-45/app/models/benefits.rb#L15
</details>
</details>
<details>
<summary>models/benefits.rb:15</summary>
https://github.com/sast-automation-dev/railsgoat-45/blob/4af0b15b213fca0ddfbdcf696e5803947b8bc1a2/railsgoat-45/app/models/benefits.rb#L10-L15
<details>
<summary> Trace </summary>
https://github.com/sast-automation-dev/railsgoat-45/blob/4af0b15b213fca0ddfbdcf696e5803947b8bc1a2/railsgoat-45/app/controllers/benefit_forms_controller.rb#L19
https://github.com/sast-automation-dev/railsgoat-45/blob/4af0b15b213fca0ddfbdcf696e5803947b8bc1a2/railsgoat-45/app/models/benefits.rb#L4
https://github.com/sast-automation-dev/railsgoat-45/blob/4af0b15b213fca0ddfbdcf696e5803947b8bc1a2/railsgoat-45/app/models/benefits.rb#L13
https://github.com/sast-automation-dev/railsgoat-45/blob/4af0b15b213fca0ddfbdcf696e5803947b8bc1a2/railsgoat-45/app/models/benefits.rb#L15
</details>
</details>
<details>
<summary>models/benefits.rb:15</summary>
https://github.com/sast-automation-dev/railsgoat-45/blob/4af0b15b213fca0ddfbdcf696e5803947b8bc1a2/railsgoat-45/app/models/benefits.rb#L10-L15
<details>
<summary> Trace </summary>
https://github.com/sast-automation-dev/railsgoat-45/blob/4af0b15b213fca0ddfbdcf696e5803947b8bc1a2/railsgoat-45/app/controllers/benefit_forms_controller.rb#L19
https://github.com/sast-automation-dev/railsgoat-45/blob/4af0b15b213fca0ddfbdcf696e5803947b8bc1a2/railsgoat-45/app/models/benefits.rb#L4
https://github.com/sast-automation-dev/railsgoat-45/blob/4af0b15b213fca0ddfbdcf696e5803947b8bc1a2/railsgoat-45/app/models/benefits.rb#L6
https://github.com/sast-automation-dev/railsgoat-45/blob/4af0b15b213fca0ddfbdcf696e5803947b8bc1a2/railsgoat-45/app/models/benefits.rb#L15
</details>
</details>
</details>
<details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20>SQL Injection (CWE-89) : 1</summary>
#### Findings
<details>
<summary>controllers/users_controller.rb:29</summary>
https://github.com/sast-automation-dev/railsgoat-45/blob/4af0b15b213fca0ddfbdcf696e5803947b8bc1a2/railsgoat-45/app/controllers/users_controller.rb#L24-L29
</details>
</details>
<details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20>Path/Directory Traversal (CWE-22) : 3</summary>
#### Findings
<details>
<summary>models/benefits.rb:7</summary>
https://github.com/sast-automation-dev/railsgoat-45/blob/4af0b15b213fca0ddfbdcf696e5803947b8bc1a2/railsgoat-45/app/models/benefits.rb#L2-L7
<details>
<summary> Trace </summary>
https://github.com/sast-automation-dev/railsgoat-45/blob/4af0b15b213fca0ddfbdcf696e5803947b8bc1a2/railsgoat-45/app/controllers/benefit_forms_controller.rb#L19
https://github.com/sast-automation-dev/railsgoat-45/blob/4af0b15b213fca0ddfbdcf696e5803947b8bc1a2/railsgoat-45/app/models/benefits.rb#L4
https://github.com/sast-automation-dev/railsgoat-45/blob/4af0b15b213fca0ddfbdcf696e5803947b8bc1a2/railsgoat-45/app/models/benefits.rb#L6
https://github.com/sast-automation-dev/railsgoat-45/blob/4af0b15b213fca0ddfbdcf696e5803947b8bc1a2/railsgoat-45/app/models/benefits.rb#L7
</details>
</details>
<details>
<summary>controllers/benefit_forms_controller.rb:12</summary>
https://github.com/sast-automation-dev/railsgoat-45/blob/4af0b15b213fca0ddfbdcf696e5803947b8bc1a2/railsgoat-45/app/controllers/benefit_forms_controller.rb#L7-L12
<details>
<summary> Trace </summary>
https://github.com/sast-automation-dev/railsgoat-45/blob/4af0b15b213fca0ddfbdcf696e5803947b8bc1a2/railsgoat-45/app/controllers/benefit_forms_controller.rb#L11
https://github.com/sast-automation-dev/railsgoat-45/blob/4af0b15b213fca0ddfbdcf696e5803947b8bc1a2/railsgoat-45/app/controllers/benefit_forms_controller.rb#L12
</details>
</details>
<details>
<summary>controllers/benefit_forms_controller.rb:12</summary>
https://github.com/sast-automation-dev/railsgoat-45/blob/4af0b15b213fca0ddfbdcf696e5803947b8bc1a2/railsgoat-45/app/controllers/benefit_forms_controller.rb#L7-L12
<details>
<summary> Trace </summary>
https://github.com/sast-automation-dev/railsgoat-45/blob/4af0b15b213fca0ddfbdcf696e5803947b8bc1a2/railsgoat-45/app/controllers/benefit_forms_controller.rb#L10
https://github.com/sast-automation-dev/railsgoat-45/blob/4af0b15b213fca0ddfbdcf696e5803947b8bc1a2/railsgoat-45/app/controllers/benefit_forms_controller.rb#L11
https://github.com/sast-automation-dev/railsgoat-45/blob/4af0b15b213fca0ddfbdcf696e5803947b8bc1a2/railsgoat-45/app/controllers/benefit_forms_controller.rb#L12
</details>
</details>
</details>
<details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20>Mass Assignment (CWE-915) : 1</summary>
#### Findings
<details>
<summary>controllers/users_controller.rb:55</summary>
https://github.com/sast-automation-dev/railsgoat-45/blob/4af0b15b213fca0ddfbdcf696e5803947b8bc1a2/railsgoat-45/app/controllers/users_controller.rb#L50-L55
</details>
</details>
<details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20>Dangerous HTML Embedded (CWE-79) : 10</summary>
#### Findings
<details>
<summary>performance/index.html.erb:63</summary>
https://github.com/sast-automation-dev/railsgoat-45/blob/4af0b15b213fca0ddfbdcf696e5803947b8bc1a2/railsgoat-45/app/views/performance/index.html.erb#L58-L63
</details>
<details>
<summary>admin/get_all_users.html.erb:29</summary>
https://github.com/sast-automation-dev/railsgoat-45/blob/4af0b15b213fca0ddfbdcf696e5803947b8bc1a2/railsgoat-45/app/views/admin/get_all_users.html.erb#L24-L29
</details>
<details>
<summary>messages/index.html.erb:114</summary>
https://github.com/sast-automation-dev/railsgoat-45/blob/4af0b15b213fca0ddfbdcf696e5803947b8bc1a2/railsgoat-45/app/views/messages/index.html.erb#L109-L114
</details>
<details>
<summary>shared/_header.html.erb:31</summary>
https://github.com/sast-automation-dev/railsgoat-45/blob/4af0b15b213fca0ddfbdcf696e5803947b8bc1a2/railsgoat-45/app/views/layouts/shared/_header.html.erb#L26-L31
</details>
<details>
<summary>controllers/password_resets_controller.rb:36</summary>
https://github.com/sast-automation-dev/railsgoat-45/blob/4af0b15b213fca0ddfbdcf696e5803947b8bc1a2/railsgoat-45/app/controllers/password_resets_controller.rb#L31-L36
</details>
<details>
<summary>shared/_header.html.erb:82</summary>
https://github.com/sast-automation-dev/railsgoat-45/blob/4af0b15b213fca0ddfbdcf696e5803947b8bc1a2/railsgoat-45/app/views/layouts/shared/_header.html.erb#L77-L82
</details>
<details>
<summary>paid_time_off/index.html.erb:192</summary>
https://github.com/sast-automation-dev/railsgoat-45/blob/4af0b15b213fca0ddfbdcf696e5803947b8bc1a2/railsgoat-45/app/views/paid_time_off/index.html.erb#L187-L192
</details>
<details>
<summary>paid_time_off/index.html.erb:158</summary>
https://github.com/sast-automation-dev/railsgoat-45/blob/4af0b15b213fca0ddfbdcf696e5803947b8bc1a2/railsgoat-45/app/views/paid_time_off/index.html.erb#L153-L158
</details>
<details>
<summary>paid_time_off/index.html.erb:135</summary>
https://github.com/sast-automation-dev/railsgoat-45/blob/4af0b15b213fca0ddfbdcf696e5803947b8bc1a2/railsgoat-45/app/views/paid_time_off/index.html.erb#L130-L135
</details>
<details>
<summary>users/account_settings.html.erb:81</summary>
https://github.com/sast-automation-dev/railsgoat-45/blob/4af0b15b213fca0ddfbdcf696e5803947b8bc1a2/railsgoat-45/app/views/users/account_settings.html.erb#L76-L81
</details>
</details>
<details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20>Cross-Site Scripting (CWE-79) : 1</summary>
#### Findings
<details>
<summary>layouts/application.html.erb:12</summary>
https://github.com/sast-automation-dev/railsgoat-45/blob/4af0b15b213fca0ddfbdcf696e5803947b8bc1a2/railsgoat-45/app/views/layouts/application.html.erb#L7-L12
</details>
</details>
| 1.0 | Code Security Report: 20 high severity findings, 30 total findings - # Code Security Report
**Latest Scan:** 2022-10-25 07:20am
**Total Findings:** 30
**Tested Project Files:** 134
**Detected Programming Languages:** 2
<!-- SAST-MANUAL-SCAN-START -->
- [ ] Check this box to manually trigger a scan
<!-- SAST-MANUAL-SCAN-END -->
## Language: JavaScript / Node.js
| Severity | CWE | Vulnerability Type | Count |
|-|-|-|-|
|<img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium|[CWE-338](https://cwe.mitre.org/data/definitions/338.html)|Weak Pseudo-Random|2|
### Details
> No high vulnerability findings detected. To view information on the remaining findings, navigate to the [Mend SAST Application](https://dev.whitesourcesoftware.com/sast/#/scans/714406f6-bc99-47d7-b72f-612cc14ee022/details).
## Language: Ruby
| Severity | CWE | Vulnerability Type | Count |
|-|-|-|-|
|<img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High|[CWE-78](https://cwe.mitre.org/data/definitions/78.html)|Command Injection|4|
|<img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High|[CWE-89](https://cwe.mitre.org/data/definitions/89.html)|SQL Injection|1|
|<img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High|[CWE-22](https://cwe.mitre.org/data/definitions/22.html)|Path/Directory Traversal|3|
|<img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High|[CWE-915](https://cwe.mitre.org/data/definitions/915.html)|Mass Assignment|1|
|<img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High|[CWE-79](https://cwe.mitre.org/data/definitions/79.html)|Dangerous HTML Embedded|10|
|<img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High|[CWE-79](https://cwe.mitre.org/data/definitions/79.html)|Cross-Site Scripting|1|
|<img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium|[CWE-321](https://cwe.mitre.org/data/definitions/321.html)|Secret Key In Source|1|
|<img src='https://whitesource-resources.whitesourcesoftware.com/low_vul.png' width=19 height=20> Low|[CWE-916](https://cwe.mitre.org/data/definitions/916.html)|Weak Hash Strength|5|
|<img src='https://whitesource-resources.whitesourcesoftware.com/low_vul.png' width=19 height=20> Low|[CWE-113](https://cwe.mitre.org/data/definitions/113.html)|HTTP Response Splitting|1|
|<img src='https://whitesource-resources.whitesourcesoftware.com/low_vul.png' width=19 height=20> Low|[CWE-1004](https://cwe.mitre.org/data/definitions/1004.html)|Cookie Without 'HttpOnly' Flag|1|
### Details
> The below list presents the 20 high vulnerability findings that need your attention. To view information on these findings, navigate to the [Mend SAST Application](https://dev.whitesourcesoftware.com/sast/#/scans/714406f6-bc99-47d7-b72f-612cc14ee022/details).
<details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20>Command Injection (CWE-78) : 4</summary>
#### Findings
<details>
<summary>models/benefits.rb:15</summary>
https://github.com/sast-automation-dev/railsgoat-45/blob/4af0b15b213fca0ddfbdcf696e5803947b8bc1a2/railsgoat-45/app/models/benefits.rb#L10-L15
<details>
<summary> Trace </summary>
https://github.com/sast-automation-dev/railsgoat-45/blob/4af0b15b213fca0ddfbdcf696e5803947b8bc1a2/railsgoat-45/app/controllers/benefit_forms_controller.rb#L19
https://github.com/sast-automation-dev/railsgoat-45/blob/4af0b15b213fca0ddfbdcf696e5803947b8bc1a2/railsgoat-45/app/models/benefits.rb#L4
https://github.com/sast-automation-dev/railsgoat-45/blob/4af0b15b213fca0ddfbdcf696e5803947b8bc1a2/railsgoat-45/app/models/benefits.rb#L15
</details>
</details>
<details>
<summary>models/benefits.rb:15</summary>
https://github.com/sast-automation-dev/railsgoat-45/blob/4af0b15b213fca0ddfbdcf696e5803947b8bc1a2/railsgoat-45/app/models/benefits.rb#L10-L15
<details>
<summary> Trace </summary>
https://github.com/sast-automation-dev/railsgoat-45/blob/4af0b15b213fca0ddfbdcf696e5803947b8bc1a2/railsgoat-45/app/controllers/benefit_forms_controller.rb#L19
https://github.com/sast-automation-dev/railsgoat-45/blob/4af0b15b213fca0ddfbdcf696e5803947b8bc1a2/railsgoat-45/app/models/benefits.rb#L4
https://github.com/sast-automation-dev/railsgoat-45/blob/4af0b15b213fca0ddfbdcf696e5803947b8bc1a2/railsgoat-45/app/models/benefits.rb#L6
https://github.com/sast-automation-dev/railsgoat-45/blob/4af0b15b213fca0ddfbdcf696e5803947b8bc1a2/railsgoat-45/app/models/benefits.rb#L13
https://github.com/sast-automation-dev/railsgoat-45/blob/4af0b15b213fca0ddfbdcf696e5803947b8bc1a2/railsgoat-45/app/models/benefits.rb#L15
</details>
</details>
<details>
<summary>models/benefits.rb:15</summary>
https://github.com/sast-automation-dev/railsgoat-45/blob/4af0b15b213fca0ddfbdcf696e5803947b8bc1a2/railsgoat-45/app/models/benefits.rb#L10-L15
<details>
<summary> Trace </summary>
https://github.com/sast-automation-dev/railsgoat-45/blob/4af0b15b213fca0ddfbdcf696e5803947b8bc1a2/railsgoat-45/app/controllers/benefit_forms_controller.rb#L19
https://github.com/sast-automation-dev/railsgoat-45/blob/4af0b15b213fca0ddfbdcf696e5803947b8bc1a2/railsgoat-45/app/models/benefits.rb#L4
https://github.com/sast-automation-dev/railsgoat-45/blob/4af0b15b213fca0ddfbdcf696e5803947b8bc1a2/railsgoat-45/app/models/benefits.rb#L13
https://github.com/sast-automation-dev/railsgoat-45/blob/4af0b15b213fca0ddfbdcf696e5803947b8bc1a2/railsgoat-45/app/models/benefits.rb#L15
</details>
</details>
<details>
<summary>models/benefits.rb:15</summary>
https://github.com/sast-automation-dev/railsgoat-45/blob/4af0b15b213fca0ddfbdcf696e5803947b8bc1a2/railsgoat-45/app/models/benefits.rb#L10-L15
<details>
<summary> Trace </summary>
https://github.com/sast-automation-dev/railsgoat-45/blob/4af0b15b213fca0ddfbdcf696e5803947b8bc1a2/railsgoat-45/app/controllers/benefit_forms_controller.rb#L19
https://github.com/sast-automation-dev/railsgoat-45/blob/4af0b15b213fca0ddfbdcf696e5803947b8bc1a2/railsgoat-45/app/models/benefits.rb#L4
https://github.com/sast-automation-dev/railsgoat-45/blob/4af0b15b213fca0ddfbdcf696e5803947b8bc1a2/railsgoat-45/app/models/benefits.rb#L6
https://github.com/sast-automation-dev/railsgoat-45/blob/4af0b15b213fca0ddfbdcf696e5803947b8bc1a2/railsgoat-45/app/models/benefits.rb#L15
</details>
</details>
</details>
<details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20>SQL Injection (CWE-89) : 1</summary>
#### Findings
<details>
<summary>controllers/users_controller.rb:29</summary>
https://github.com/sast-automation-dev/railsgoat-45/blob/4af0b15b213fca0ddfbdcf696e5803947b8bc1a2/railsgoat-45/app/controllers/users_controller.rb#L24-L29
</details>
</details>
<details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20>Path/Directory Traversal (CWE-22) : 3</summary>
#### Findings
<details>
<summary>models/benefits.rb:7</summary>
https://github.com/sast-automation-dev/railsgoat-45/blob/4af0b15b213fca0ddfbdcf696e5803947b8bc1a2/railsgoat-45/app/models/benefits.rb#L2-L7
<details>
<summary> Trace </summary>
https://github.com/sast-automation-dev/railsgoat-45/blob/4af0b15b213fca0ddfbdcf696e5803947b8bc1a2/railsgoat-45/app/controllers/benefit_forms_controller.rb#L19
https://github.com/sast-automation-dev/railsgoat-45/blob/4af0b15b213fca0ddfbdcf696e5803947b8bc1a2/railsgoat-45/app/models/benefits.rb#L4
https://github.com/sast-automation-dev/railsgoat-45/blob/4af0b15b213fca0ddfbdcf696e5803947b8bc1a2/railsgoat-45/app/models/benefits.rb#L6
https://github.com/sast-automation-dev/railsgoat-45/blob/4af0b15b213fca0ddfbdcf696e5803947b8bc1a2/railsgoat-45/app/models/benefits.rb#L7
</details>
</details>
<details>
<summary>controllers/benefit_forms_controller.rb:12</summary>
https://github.com/sast-automation-dev/railsgoat-45/blob/4af0b15b213fca0ddfbdcf696e5803947b8bc1a2/railsgoat-45/app/controllers/benefit_forms_controller.rb#L7-L12
<details>
<summary> Trace </summary>
https://github.com/sast-automation-dev/railsgoat-45/blob/4af0b15b213fca0ddfbdcf696e5803947b8bc1a2/railsgoat-45/app/controllers/benefit_forms_controller.rb#L11
https://github.com/sast-automation-dev/railsgoat-45/blob/4af0b15b213fca0ddfbdcf696e5803947b8bc1a2/railsgoat-45/app/controllers/benefit_forms_controller.rb#L12
</details>
</details>
<details>
<summary>controllers/benefit_forms_controller.rb:12</summary>
https://github.com/sast-automation-dev/railsgoat-45/blob/4af0b15b213fca0ddfbdcf696e5803947b8bc1a2/railsgoat-45/app/controllers/benefit_forms_controller.rb#L7-L12
<details>
<summary> Trace </summary>
https://github.com/sast-automation-dev/railsgoat-45/blob/4af0b15b213fca0ddfbdcf696e5803947b8bc1a2/railsgoat-45/app/controllers/benefit_forms_controller.rb#L10
https://github.com/sast-automation-dev/railsgoat-45/blob/4af0b15b213fca0ddfbdcf696e5803947b8bc1a2/railsgoat-45/app/controllers/benefit_forms_controller.rb#L11
https://github.com/sast-automation-dev/railsgoat-45/blob/4af0b15b213fca0ddfbdcf696e5803947b8bc1a2/railsgoat-45/app/controllers/benefit_forms_controller.rb#L12
</details>
</details>
</details>
<details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20>Mass Assignment (CWE-915) : 1</summary>
#### Findings
<details>
<summary>controllers/users_controller.rb:55</summary>
https://github.com/sast-automation-dev/railsgoat-45/blob/4af0b15b213fca0ddfbdcf696e5803947b8bc1a2/railsgoat-45/app/controllers/users_controller.rb#L50-L55
</details>
</details>
<details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20>Dangerous HTML Embedded (CWE-79) : 10</summary>
#### Findings
<details>
<summary>performance/index.html.erb:63</summary>
https://github.com/sast-automation-dev/railsgoat-45/blob/4af0b15b213fca0ddfbdcf696e5803947b8bc1a2/railsgoat-45/app/views/performance/index.html.erb#L58-L63
</details>
<details>
<summary>admin/get_all_users.html.erb:29</summary>
https://github.com/sast-automation-dev/railsgoat-45/blob/4af0b15b213fca0ddfbdcf696e5803947b8bc1a2/railsgoat-45/app/views/admin/get_all_users.html.erb#L24-L29
</details>
<details>
<summary>messages/index.html.erb:114</summary>
https://github.com/sast-automation-dev/railsgoat-45/blob/4af0b15b213fca0ddfbdcf696e5803947b8bc1a2/railsgoat-45/app/views/messages/index.html.erb#L109-L114
</details>
<details>
<summary>shared/_header.html.erb:31</summary>
https://github.com/sast-automation-dev/railsgoat-45/blob/4af0b15b213fca0ddfbdcf696e5803947b8bc1a2/railsgoat-45/app/views/layouts/shared/_header.html.erb#L26-L31
</details>
<details>
<summary>controllers/password_resets_controller.rb:36</summary>
https://github.com/sast-automation-dev/railsgoat-45/blob/4af0b15b213fca0ddfbdcf696e5803947b8bc1a2/railsgoat-45/app/controllers/password_resets_controller.rb#L31-L36
</details>
<details>
<summary>shared/_header.html.erb:82</summary>
https://github.com/sast-automation-dev/railsgoat-45/blob/4af0b15b213fca0ddfbdcf696e5803947b8bc1a2/railsgoat-45/app/views/layouts/shared/_header.html.erb#L77-L82
</details>
<details>
<summary>paid_time_off/index.html.erb:192</summary>
https://github.com/sast-automation-dev/railsgoat-45/blob/4af0b15b213fca0ddfbdcf696e5803947b8bc1a2/railsgoat-45/app/views/paid_time_off/index.html.erb#L187-L192
</details>
<details>
<summary>paid_time_off/index.html.erb:158</summary>
https://github.com/sast-automation-dev/railsgoat-45/blob/4af0b15b213fca0ddfbdcf696e5803947b8bc1a2/railsgoat-45/app/views/paid_time_off/index.html.erb#L153-L158
</details>
<details>
<summary>paid_time_off/index.html.erb:135</summary>
https://github.com/sast-automation-dev/railsgoat-45/blob/4af0b15b213fca0ddfbdcf696e5803947b8bc1a2/railsgoat-45/app/views/paid_time_off/index.html.erb#L130-L135
</details>
<details>
<summary>users/account_settings.html.erb:81</summary>
https://github.com/sast-automation-dev/railsgoat-45/blob/4af0b15b213fca0ddfbdcf696e5803947b8bc1a2/railsgoat-45/app/views/users/account_settings.html.erb#L76-L81
</details>
</details>
<details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20>Cross-Site Scripting (CWE-79) : 1</summary>
#### Findings
<details>
<summary>layouts/application.html.erb:12</summary>
https://github.com/sast-automation-dev/railsgoat-45/blob/4af0b15b213fca0ddfbdcf696e5803947b8bc1a2/railsgoat-45/app/views/layouts/application.html.erb#L7-L12
</details>
</details>
| non_priority | code security report high severity findings total findings code security report latest scan total findings tested project files detected programming languages check this box to manually trigger a scan language javascript node js severity cwe vulnerability type count medium pseudo random details no high vulnerability findings detected to view information on the remaining findings navigate to the language ruby severity cwe vulnerability type count high injection high injection high traversal high assignment high html embedded high scripting medium key in source low hash strength low response splitting low without httponly flag details the below list presents the high vulnerability findings that need your attention to view information on these findings navigate to the command injection cwe findings models benefits rb trace models benefits rb trace models benefits rb trace models benefits rb trace sql injection cwe findings controllers users controller rb path directory traversal cwe findings models benefits rb trace controllers benefit forms controller rb trace controllers benefit forms controller rb trace mass assignment cwe findings controllers users controller rb dangerous html embedded cwe findings performance index html erb admin get all users html erb messages index html erb shared header html erb controllers password resets controller rb shared header html erb paid time off index html erb paid time off index html erb paid time off index html erb users account settings html erb cross site scripting cwe findings layouts application html erb | 0 |
7,823 | 10,996,990,856 | IssuesEvent | 2019-12-03 08:10:22 | Altinn/altinn-studio | https://api.github.com/repos/Altinn/altinn-studio | closed | isArchived is not set to True when an instance is sent in | area/message-box area/process kind/bug solution/sbl team/nusse | ## Describe the bug
isArchived is not set to True when an instance is sent in by an user from SBL
## To Reproduce
Steps to reproduce the behavior:
1. Login to AT21 and start a instance of a deployed app
2. Fill in data and send inn the instance
3. The receipt page is presented to the user
4. Navigate back to inbox and see that the instance is still available in the Inbox
5. Open the instance and click on 'Gå til skjema' and user is presented with a receipt
## Expected behavior
When an instance is submitted/sent in, isArchived on the instance should be set to true and the instance should be moved to the archived.
## Additional info
App: ttd/pdp-test
Env: AT21
Browser: Chrome 78 | 1.0 | isArchived is not set to True when an instance is sent in - ## Describe the bug
isArchived is not set to True when an instance is sent in by an user from SBL
## To Reproduce
Steps to reproduce the behavior:
1. Login to AT21 and start a instance of a deployed app
2. Fill in data and send inn the instance
3. The receipt page is presented to the user
4. Navigate back to inbox and see that the instance is still available in the Inbox
5. Open the instance and click on 'Gå til skjema' and user is presented with a receipt
## Expected behavior
When an instance is submitted/sent in, isArchived on the instance should be set to true and the instance should be moved to the archived.
## Additional info
App: ttd/pdp-test
Env: AT21
Browser: Chrome 78 | non_priority | isarchived is not set to true when an instance is sent in describe the bug isarchived is not set to true when an instance is sent in by an user from sbl to reproduce steps to reproduce the behavior login to and start a instance of a deployed app fill in data and send inn the instance the receipt page is presented to the user navigate back to inbox and see that the instance is still available in the inbox open the instance and click on gå til skjema and user is presented with a receipt expected behavior when an instance is submitted sent in isarchived on the instance should be set to true and the instance should be moved to the archived additional info app ttd pdp test env browser chrome | 0 |
44,903 | 9,658,568,826 | IssuesEvent | 2019-05-20 11:21:12 | OpenXRay/xray-16 | https://api.github.com/repos/OpenXRay/xray-16 | closed | Split xrCore/ModuleLookup.cpp to Windows and Linux versions | Code Quality Core Developer Experience Infrastructure | Split the file to something like `ModuleLookupWindows.cpp` and `ModuleLookupLinux.cpp` | 1.0 | Split xrCore/ModuleLookup.cpp to Windows and Linux versions - Split the file to something like `ModuleLookupWindows.cpp` and `ModuleLookupLinux.cpp` | non_priority | split xrcore modulelookup cpp to windows and linux versions split the file to something like modulelookupwindows cpp and modulelookuplinux cpp | 0 |
15,574 | 8,961,578,414 | IssuesEvent | 2019-01-28 10:02:18 | bazelbuild/bazel | https://api.github.com/repos/bazelbuild/bazel | closed | [aquery] Add a label to TreeArtifact in text output | P2 team-Performance | ### Description of the problem / feature request:
It is useful for the users to know if an output artifact of an action is a TreeArtifact. We already have this information in the proto output. It should be added to the text output as well. | True | [aquery] Add a label to TreeArtifact in text output - ### Description of the problem / feature request:
It is useful for the users to know if an output artifact of an action is a TreeArtifact. We already have this information in the proto output. It should be added to the text output as well. | non_priority | add a label to treeartifact in text output description of the problem feature request it is useful for the users to know if an output artifact of an action is a treeartifact we already have this information in the proto output it should be added to the text output as well | 0 |
167,377 | 14,111,412,303 | IssuesEvent | 2020-11-07 00:09:47 | JulianaMurillo1509/git_web_practice_branch | https://api.github.com/repos/JulianaMurillo1509/git_web_practice_branch | closed | Un commit que no sigue la convención de código o arreglo a realizar | documentation | La convención de código a seguir: `<Identificador comentario>: <Comentario>`
Igualmente, solo hay 1 arreglo a realizar. Al realizar cada paso y completarlo se creará un issue con las instrucciones a realizar para continuar.
Para realizar la corrección del mensaje de commit usar `git commit --amend` y `git commit push -f`
El último commit tiene el siguiente mensaje:
`fix_1`
Este issue es solo un recordatorio de la convención de comentarios en los commits y puede ser cerrado. | 1.0 | Un commit que no sigue la convención de código o arreglo a realizar - La convención de código a seguir: `<Identificador comentario>: <Comentario>`
Igualmente, solo hay 1 arreglo a realizar. Al realizar cada paso y completarlo se creará un issue con las instrucciones a realizar para continuar.
Para realizar la corrección del mensaje de commit usar `git commit --amend` y `git commit push -f`
El último commit tiene el siguiente mensaje:
`fix_1`
Este issue es solo un recordatorio de la convención de comentarios en los commits y puede ser cerrado. | non_priority | un commit que no sigue la convención de código o arreglo a realizar la convención de código a seguir igualmente solo hay arreglo a realizar al realizar cada paso y completarlo se creará un issue con las instrucciones a realizar para continuar para realizar la corrección del mensaje de commit usar git commit amend y git commit push f el último commit tiene el siguiente mensaje fix este issue es solo un recordatorio de la convención de comentarios en los commits y puede ser cerrado | 0 |
133,540 | 12,543,844,814 | IssuesEvent | 2020-06-05 16:13:34 | SE2-Busfahrer-SS20/SE2-Busfahrer-SS20 | https://api.github.com/repos/SE2-Busfahrer-SS20/SE2-Busfahrer-SS20 | closed | [E07 Story 04] - Schummelfunktion Refactoring/Testen/Dokumentation | Effort: 5 Test documentation | Schummelfunktion Refactoring/Testen/Dokumentation | 1.0 | [E07 Story 04] - Schummelfunktion Refactoring/Testen/Dokumentation - Schummelfunktion Refactoring/Testen/Dokumentation | non_priority | schummelfunktion refactoring testen dokumentation schummelfunktion refactoring testen dokumentation | 0 |
22,135 | 6,229,488,462 | IssuesEvent | 2017-07-11 04:10:12 | XceedBoucherS/TestImport5 | https://api.github.com/repos/XceedBoucherS/TestImport5 | closed | Do not handle PreviewMouseDown on PropertyItem | CodePlex | <b>emartin[CodePlex]</b> <br />Need expressed from patch 13449 (
http://wpftoolkit.codeplex.com/SourceControl/list/patches )
This handling is actually done to affect the quotIsSelectedquot property. Handling this event may interfere with the underlying editor that need to handle the MouseDown event too.
| 1.0 | Do not handle PreviewMouseDown on PropertyItem - <b>emartin[CodePlex]</b> <br />Need expressed from patch 13449 (
http://wpftoolkit.codeplex.com/SourceControl/list/patches )
This handling is actually done to affect the quotIsSelectedquot property. Handling this event may interfere with the underlying editor that need to handle the MouseDown event too.
| non_priority | do not handle previewmousedown on propertyitem emartin need expressed from patch this handling is actually done to affect the quotisselectedquot property handling this event may interfere with the underlying editor that need to handle the mousedown event too | 0 |
136,792 | 11,083,736,704 | IssuesEvent | 2019-12-13 15:05:08 | ipfs/go-ipfs | https://api.github.com/repos/ipfs/go-ipfs | opened | go-ipfs-api test timeout | test failure | The go-ipfs-api tests are timing out randomly when run against go-ipfs master (using CircleCI, at least).
Example failure (no output): https://circleci.com/gh/ipfs/go-ipfs/22908 | 1.0 | go-ipfs-api test timeout - The go-ipfs-api tests are timing out randomly when run against go-ipfs master (using CircleCI, at least).
Example failure (no output): https://circleci.com/gh/ipfs/go-ipfs/22908 | non_priority | go ipfs api test timeout the go ipfs api tests are timing out randomly when run against go ipfs master using circleci at least example failure no output | 0 |
174,248 | 21,259,432,979 | IssuesEvent | 2022-04-13 01:21:44 | GuyBarGil/WebGoat | https://api.github.com/repos/GuyBarGil/WebGoat | opened | WS-2019-0490 (High) detected in jcommander-1.72.jar | security vulnerability | ## WS-2019-0490 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>jcommander-1.72.jar</b></p></summary>
<p>Command line parsing</p>
<p>Library home page: <a href="http://jcommander.org">http://jcommander.org</a></p>
<p>Path to dependency file: /webgoat-integration-tests/pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/com/beust/jcommander/1.72/jcommander-1.72.jar</p>
<p>
Dependency Hierarchy:
- webgoat-server-8.2.1-SNAPSHOT.jar (Root Library)
- webgoat-container-8.2.1-SNAPSHOT.jar
- asciidoctorj-2.4.3.jar
- :x: **jcommander-1.72.jar** (Vulnerable Library)
<p>Found in base branch: <b>develop</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
Inclusion of Functionality from Untrusted Control Sphere vulnerability found in jcommander before 1.75. jcommander resolving dependencies over HTTP instead of HTTPS.
<p>Publish Date: 2019-02-19
<p>URL: <a href=https://github.com/cbeust/jcommander/commit/3ae95595febbed9c13f367b6bda5c0be1c572c53>WS-2019-0490</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>8.1</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/cbeust/jcommander/issues/465">https://github.com/cbeust/jcommander/issues/465</a></p>
<p>Release Date: 2019-02-19</p>
<p>Fix Resolution: com.beust:jcommander:1.75</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | WS-2019-0490 (High) detected in jcommander-1.72.jar - ## WS-2019-0490 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>jcommander-1.72.jar</b></p></summary>
<p>Command line parsing</p>
<p>Library home page: <a href="http://jcommander.org">http://jcommander.org</a></p>
<p>Path to dependency file: /webgoat-integration-tests/pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/com/beust/jcommander/1.72/jcommander-1.72.jar</p>
<p>
Dependency Hierarchy:
- webgoat-server-8.2.1-SNAPSHOT.jar (Root Library)
- webgoat-container-8.2.1-SNAPSHOT.jar
- asciidoctorj-2.4.3.jar
- :x: **jcommander-1.72.jar** (Vulnerable Library)
<p>Found in base branch: <b>develop</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
Inclusion of Functionality from Untrusted Control Sphere vulnerability found in jcommander before 1.75. jcommander resolving dependencies over HTTP instead of HTTPS.
<p>Publish Date: 2019-02-19
<p>URL: <a href=https://github.com/cbeust/jcommander/commit/3ae95595febbed9c13f367b6bda5c0be1c572c53>WS-2019-0490</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>8.1</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/cbeust/jcommander/issues/465">https://github.com/cbeust/jcommander/issues/465</a></p>
<p>Release Date: 2019-02-19</p>
<p>Fix Resolution: com.beust:jcommander:1.75</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_priority | ws high detected in jcommander jar ws high severity vulnerability vulnerable library jcommander jar command line parsing library home page a href path to dependency file webgoat integration tests pom xml path to vulnerable library home wss scanner repository com beust jcommander jcommander jar dependency hierarchy webgoat server snapshot jar root library webgoat container snapshot jar asciidoctorj jar x jcommander jar vulnerable library found in base branch develop vulnerability details inclusion of functionality from untrusted control sphere vulnerability found in jcommander before jcommander resolving dependencies over http instead of https publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity high privileges required none user interaction none scope unchanged impact metrics confidentiality impact high integrity impact high availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution com beust jcommander step up your open source security game with whitesource | 0 |
278,530 | 30,702,347,396 | IssuesEvent | 2023-07-27 01:22:27 | hshivhare67/kernel_v4.1.15_CVE-2019-10220 | https://api.github.com/repos/hshivhare67/kernel_v4.1.15_CVE-2019-10220 | closed | CVE-2016-7117 (Critical) detected in linuxlinux-4.4.302 - autoclosed | Mend: dependency security vulnerability | ## CVE-2016-7117 - Critical Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>linuxlinux-4.4.302</b></p></summary>
<p>
<p>The Linux Kernel</p>
<p>Library home page: <a href=https://mirrors.edge.kernel.org/pub/linux/kernel/v4.x/?wsslib=linux>https://mirrors.edge.kernel.org/pub/linux/kernel/v4.x/?wsslib=linux</a></p>
<p>Found in base branch: <b>master</b></p></p>
</details>
</p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Source Files (1)</summary>
<p></p>
<p>
</p>
</details>
<p></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/critical_vul.png?' width=19 height=20> Vulnerability Details</summary>
<p>
Use-after-free vulnerability in the __sys_recvmmsg function in net/socket.c in the Linux kernel before 4.5.2 allows remote attackers to execute arbitrary code via vectors involving a recvmmsg system call that is mishandled during error processing.
<p>Publish Date: 2016-10-10
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2016-7117>CVE-2016-7117</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>9.8</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://nvd.nist.gov/vuln/detail/CVE-2016-7117">https://nvd.nist.gov/vuln/detail/CVE-2016-7117</a></p>
<p>Release Date: 2016-10-10</p>
<p>Fix Resolution: 4.5.2</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | CVE-2016-7117 (Critical) detected in linuxlinux-4.4.302 - autoclosed - ## CVE-2016-7117 - Critical Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>linuxlinux-4.4.302</b></p></summary>
<p>
<p>The Linux Kernel</p>
<p>Library home page: <a href=https://mirrors.edge.kernel.org/pub/linux/kernel/v4.x/?wsslib=linux>https://mirrors.edge.kernel.org/pub/linux/kernel/v4.x/?wsslib=linux</a></p>
<p>Found in base branch: <b>master</b></p></p>
</details>
</p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Source Files (1)</summary>
<p></p>
<p>
</p>
</details>
<p></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/critical_vul.png?' width=19 height=20> Vulnerability Details</summary>
<p>
Use-after-free vulnerability in the __sys_recvmmsg function in net/socket.c in the Linux kernel before 4.5.2 allows remote attackers to execute arbitrary code via vectors involving a recvmmsg system call that is mishandled during error processing.
<p>Publish Date: 2016-10-10
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2016-7117>CVE-2016-7117</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>9.8</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://nvd.nist.gov/vuln/detail/CVE-2016-7117">https://nvd.nist.gov/vuln/detail/CVE-2016-7117</a></p>
<p>Release Date: 2016-10-10</p>
<p>Fix Resolution: 4.5.2</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 critical detected in linuxlinux autoclosed cve critical severity vulnerability vulnerable library linuxlinux the linux kernel library home page a href found in base branch master vulnerable source files vulnerability details use after free vulnerability in the sys recvmmsg function in net socket c in the linux kernel before allows remote attackers to execute arbitrary code via vectors involving a recvmmsg system call that is mishandled during error processing publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact high integrity impact high availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution step up your open source security game with mend | 0 |
126,132 | 16,980,083,288 | IssuesEvent | 2021-06-30 07:43:07 | nextcloud/spreed | https://api.github.com/repos/nextcloud/spreed | closed | Add icons for Mark as read and unread | 3. to review design | **Is your feature request related to a problem? Please describe.**
There are no icons for both the "Mark as read" and "Mark as unread" context menu options which looks odd next to the other options which do have icons.
**Describe the solution you'd like**
Icons should be added for the "Mark as read" and "Mark as unread" options.
**Additional context**
| 1.0 | Add icons for Mark as read and unread - **Is your feature request related to a problem? Please describe.**
There are no icons for both the "Mark as read" and "Mark as unread" context menu options which looks odd next to the other options which do have icons.
**Describe the solution you'd like**
Icons should be added for the "Mark as read" and "Mark as unread" options.
**Additional context**
| non_priority | add icons for mark as read and unread is your feature request related to a problem please describe there are no icons for both the mark as read and mark as unread context menu options which looks odd next to the other options which do have icons describe the solution you d like icons should be added for the mark as read and mark as unread options additional context | 0 |
185,137 | 21,785,083,775 | IssuesEvent | 2022-05-14 02:25:35 | turkdevops/angular | https://api.github.com/repos/turkdevops/angular | opened | CVE-2022-1650 (High) detected in eventsource-1.0.7.tgz | security vulnerability | ## CVE-2022-1650 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>eventsource-1.0.7.tgz</b></p></summary>
<p>W3C compliant EventSource client for Node.js and browser (polyfill)</p>
<p>Library home page: <a href="https://registry.npmjs.org/eventsource/-/eventsource-1.0.7.tgz">https://registry.npmjs.org/eventsource/-/eventsource-1.0.7.tgz</a></p>
<p>Path to dependency file: /integration/cli-hello-world-lazy-rollup/package.json</p>
<p>Path to vulnerable library: /integration/cli-hello-world-lazy-rollup/node_modules/eventsource/package.json,/integration/cli-hello-world-ivy-minimal/node_modules/eventsource/package.json,/integration/cli-hello-world-lazy/node_modules/eventsource/package.json,/integration/ng_update_migrations/node_modules/eventsource/package.json,/integration/trusted-types/node_modules/eventsource/package.json,/aio/node_modules/eventsource/package.json,/integration/cli-hello-world-ivy-compat/node_modules/eventsource/package.json,/integration/cli-hello-world/node_modules/eventsource/package.json,/integration/cli-hello-world-ivy-i18n/node_modules/eventsource/package.json,/node_modules/eventsource/package.json</p>
<p>
Dependency Hierarchy:
- build-angular-0.1100.1.tgz (Root Library)
- webpack-dev-server-3.11.0.tgz
- sockjs-client-1.4.0.tgz
- :x: **eventsource-1.0.7.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/turkdevops/angular/commit/c6aca37f442da8c55a02d7c53ccc58100ab004f3">c6aca37f442da8c55a02d7c53ccc58100ab004f3</a></p>
<p>Found in base branch: <b>labs/router</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>
Exposure of Sensitive Information to an Unauthorized Actor in GitHub repository eventsource/eventsource prior to v2.0.2.
<p>Publish Date: 2022-05-12
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-1650>CVE-2022-1650</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>8.1</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</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/dc9e467f-be5d-4945-867d-1044d27e9b8e/">https://huntr.dev/bounties/dc9e467f-be5d-4945-867d-1044d27e9b8e/</a></p>
<p>Release Date: 2022-05-12</p>
<p>Fix Resolution: eventsource - 2.0.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-2022-1650 (High) detected in eventsource-1.0.7.tgz - ## CVE-2022-1650 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>eventsource-1.0.7.tgz</b></p></summary>
<p>W3C compliant EventSource client for Node.js and browser (polyfill)</p>
<p>Library home page: <a href="https://registry.npmjs.org/eventsource/-/eventsource-1.0.7.tgz">https://registry.npmjs.org/eventsource/-/eventsource-1.0.7.tgz</a></p>
<p>Path to dependency file: /integration/cli-hello-world-lazy-rollup/package.json</p>
<p>Path to vulnerable library: /integration/cli-hello-world-lazy-rollup/node_modules/eventsource/package.json,/integration/cli-hello-world-ivy-minimal/node_modules/eventsource/package.json,/integration/cli-hello-world-lazy/node_modules/eventsource/package.json,/integration/ng_update_migrations/node_modules/eventsource/package.json,/integration/trusted-types/node_modules/eventsource/package.json,/aio/node_modules/eventsource/package.json,/integration/cli-hello-world-ivy-compat/node_modules/eventsource/package.json,/integration/cli-hello-world/node_modules/eventsource/package.json,/integration/cli-hello-world-ivy-i18n/node_modules/eventsource/package.json,/node_modules/eventsource/package.json</p>
<p>
Dependency Hierarchy:
- build-angular-0.1100.1.tgz (Root Library)
- webpack-dev-server-3.11.0.tgz
- sockjs-client-1.4.0.tgz
- :x: **eventsource-1.0.7.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/turkdevops/angular/commit/c6aca37f442da8c55a02d7c53ccc58100ab004f3">c6aca37f442da8c55a02d7c53ccc58100ab004f3</a></p>
<p>Found in base branch: <b>labs/router</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>
Exposure of Sensitive Information to an Unauthorized Actor in GitHub repository eventsource/eventsource prior to v2.0.2.
<p>Publish Date: 2022-05-12
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-1650>CVE-2022-1650</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>8.1</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</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/dc9e467f-be5d-4945-867d-1044d27e9b8e/">https://huntr.dev/bounties/dc9e467f-be5d-4945-867d-1044d27e9b8e/</a></p>
<p>Release Date: 2022-05-12</p>
<p>Fix Resolution: eventsource - 2.0.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 high detected in eventsource tgz cve high severity vulnerability vulnerable library eventsource tgz compliant eventsource client for node js and browser polyfill library home page a href path to dependency file integration cli hello world lazy rollup package json path to vulnerable library integration cli hello world lazy rollup node modules eventsource package json integration cli hello world ivy minimal node modules eventsource package json integration cli hello world lazy node modules eventsource package json integration ng update migrations node modules eventsource package json integration trusted types node modules eventsource package json aio node modules eventsource package json integration cli hello world ivy compat node modules eventsource package json integration cli hello world node modules eventsource package json integration cli hello world ivy node modules eventsource package json node modules eventsource package json dependency hierarchy build angular tgz root library webpack dev server tgz sockjs client tgz x eventsource tgz vulnerable library found in head commit a href found in base branch labs router vulnerability details exposure of sensitive information to an unauthorized actor in github repository eventsource eventsource prior to publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction required scope unchanged impact metrics confidentiality impact high integrity impact high availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution eventsource step up your open source security game with whitesource | 0 |
152,494 | 19,685,361,295 | IssuesEvent | 2022-01-11 21:26:57 | eclipse/rdf4j | https://api.github.com/repos/eclipse/rdf4j | closed | Upgrade to Spring 5.3.14 | 🐞 bug security dependencies | ### Current Behavior
Current 5.3 version may have a log injection vulnerability
### Expected Behavior
Upgrade to latest patch version to fix the issue
### Steps To Reproduce
_No response_
### Version
3.7.4
### Are you interested in contributing a solution yourself?
Yes
### Anything else?
https://spring.io/blog/2021/12/16/spring-framework-5-3-14-and-5-2-19-available-now
https://tanzu.vmware.com/security/cve-2021-22096 | True | Upgrade to Spring 5.3.14 - ### Current Behavior
Current 5.3 version may have a log injection vulnerability
### Expected Behavior
Upgrade to latest patch version to fix the issue
### Steps To Reproduce
_No response_
### Version
3.7.4
### Are you interested in contributing a solution yourself?
Yes
### Anything else?
https://spring.io/blog/2021/12/16/spring-framework-5-3-14-and-5-2-19-available-now
https://tanzu.vmware.com/security/cve-2021-22096 | non_priority | upgrade to spring current behavior current version may have a log injection vulnerability expected behavior upgrade to latest patch version to fix the issue steps to reproduce no response version are you interested in contributing a solution yourself yes anything else | 0 |
45,557 | 7,190,224,600 | IssuesEvent | 2018-02-02 16:32:40 | CCI-MOC/hil | https://api.github.com/repos/CCI-MOC/hil | closed | More consistent terminology | cleanup documentation naming | There are a number of concepts in the HaaS that we have redundant names for throughout the code, which makes variable names less consistent and thus less predictable. Here are some examples:
- [ ] name/label
...okay just the one example for now. We can edit this if/when we find more, I feel like they're there.
| 1.0 | More consistent terminology - There are a number of concepts in the HaaS that we have redundant names for throughout the code, which makes variable names less consistent and thus less predictable. Here are some examples:
- [ ] name/label
...okay just the one example for now. We can edit this if/when we find more, I feel like they're there.
| non_priority | more consistent terminology there are a number of concepts in the haas that we have redundant names for throughout the code which makes variable names less consistent and thus less predictable here are some examples name label okay just the one example for now we can edit this if when we find more i feel like they re there | 0 |
201,813 | 15,814,086,953 | IssuesEvent | 2021-04-05 08:51:47 | asiisii/Fitness-Tracker | https://api.github.com/repos/asiisii/Fitness-Tracker | closed | Charts are not updating | bug documentation | When the date or week or the user name is changed, charts need to remove the orignal data, and update it with new data. | 1.0 | Charts are not updating - When the date or week or the user name is changed, charts need to remove the orignal data, and update it with new data. | non_priority | charts are not updating when the date or week or the user name is changed charts need to remove the orignal data and update it with new data | 0 |
132,367 | 18,716,895,383 | IssuesEvent | 2021-11-03 06:48:21 | woocommerce/woocommerce-gutenberg-products-block | https://api.github.com/repos/woocommerce/woocommerce-gutenberg-products-block | closed | Decide on and design template block placeholders for the editor | needs design category: fse 🔹 block-type: templates | ## Context
For the [WooCommerce Store Editing Templates v1](https://github.com/woocommerce/woocommerce-gutenberg-products-block/issues/4926), we're converting a set of WooCommerce PHP templates to a block each. Initially, the goal is not to create fully-featured blocks but instead create one basic block per PHP template that renders a placeholder in the editor and the template on the Frontend.
## Goal
The goal of this particular issue is to decide on the placeholder design and copy for the editor.
## Ideas
We created some basic prototypes to demonstrate the design challenge and offer some initial ideas on potential solutions.
### Option 1: simple text-based placeholder
The first option would be to display a simple text-based placeholder that provides the merchant with an explanation that a) they are seeing a placeholder they can move and add blocks around and b) that the placeholder will be replaced by the related WooCommerce template on the Frontend.
This simple option has a couple of key advantages:
- Its compact size makes it easy for a merchant to move around and edit the page with other blocks. For example, if they'd like to move the template block into a column layout, it's easier to move a compact block than a prominent wireframe placeholder like below.
- It's very straightforward to implement. Given that these placeholders are a temporary stopgap solution, it is at least up for debate on how much work should go into creating them.
Note: we just used the `Notice` component inside the `Placeholder` component for the prototype here. As per [Block Editor Handbook](https://developer.wordpress.org/block-editor/reference-guides/components/notice/) it sounds like the `Notice` should only be used for top-level notices. We'd have to use something else here.
<img width="500" alt="Screenshot 2021-10-14 at 16 34 16" src="https://user-images.githubusercontent.com/1562646/137440146-d24c2807-c2cc-49b5-99b4-ea4ded1ce4e1.png">
### Option 2: text-based replica placeholder
The second option is inspired by the recent effort of [unifying Site Editing block placeholders](https://github.com/WordPress/gutenberg/issues/35501). In situations in which the blocks have no data to reference, the blocks are now showing basic descriptions in place of where the relevant elements would be e.g. "Product title" where the title of the product would show.
The main downsides of this option are:
- Given that the placeholder mimics the actual template that will be rendered on the Frontend, the placeholder can get very large which makes it difficult for a merchant to move it around in the editor. The user experience arguably isn't great.
- Implementing this option means we'll have to basically replicate each entire template in the editor. Given that these placeholders are a temporary stopgap solution, it is up for debate if this is worth the time commitment required.
<img width="500" alt="Screenshot 2021-10-14 at 17 20 00" src="https://user-images.githubusercontent.com/1562646/137441560-f43d1b24-4fe0-4afd-894f-7495fd0470ad.png">
### Option 3.1: wireframe replica placeholder
The third option is inspired by the navigation block empty state placeholder. In situations in which the block has no data, it's showing a basic wireframe representation of the content.
The main downsides of this option are:
- Given that the placeholder mimics the actual template that will be rendered on the Frontend, the placeholder can get very large which makes it difficult for a merchant to move it around in the editor. The user experience arguably isn't great.
- While this option is a little less involved than option 2, implementing this option still means we'll have to basically replicate each entire template in the editor. Given that these placeholders are a temporary stopgap solution, it is up for debate if this is worth the time commitment required.
<img width="500" alt="Screenshot 2021-10-14 at 17 52 47" src="https://user-images.githubusercontent.com/1562646/137442283-975c8a26-fa4e-4204-a7e2-9c0e78173a25.png">
### Option 3.2: image-based wireframe replica placeholder
A potential solution to reducing the time investment for this option could be to just include an image wireframe representing the template. The assumption here is that designing these wireframes in Figma would probably be quicker than building out each wireframe with actual markup/styles?
<img width="500" alt="Screenshot 2021-10-15 at 08 49 01" src="https://user-images.githubusercontent.com/1562646/137444374-13318db4-3967-4581-8e29-7331c28ab062.png">
| 1.0 | Decide on and design template block placeholders for the editor - ## Context
For the [WooCommerce Store Editing Templates v1](https://github.com/woocommerce/woocommerce-gutenberg-products-block/issues/4926), we're converting a set of WooCommerce PHP templates to a block each. Initially, the goal is not to create fully-featured blocks but instead create one basic block per PHP template that renders a placeholder in the editor and the template on the Frontend.
## Goal
The goal of this particular issue is to decide on the placeholder design and copy for the editor.
## Ideas
We created some basic prototypes to demonstrate the design challenge and offer some initial ideas on potential solutions.
### Option 1: simple text-based placeholder
The first option would be to display a simple text-based placeholder that provides the merchant with an explanation that a) they are seeing a placeholder they can move and add blocks around and b) that the placeholder will be replaced by the related WooCommerce template on the Frontend.
This simple option has a couple of key advantages:
- Its compact size makes it easy for a merchant to move around and edit the page with other blocks. For example, if they'd like to move the template block into a column layout, it's easier to move a compact block than a prominent wireframe placeholder like below.
- It's very straightforward to implement. Given that these placeholders are a temporary stopgap solution, it is at least up for debate on how much work should go into creating them.
Note: we just used the `Notice` component inside the `Placeholder` component for the prototype here. As per [Block Editor Handbook](https://developer.wordpress.org/block-editor/reference-guides/components/notice/) it sounds like the `Notice` should only be used for top-level notices. We'd have to use something else here.
<img width="500" alt="Screenshot 2021-10-14 at 16 34 16" src="https://user-images.githubusercontent.com/1562646/137440146-d24c2807-c2cc-49b5-99b4-ea4ded1ce4e1.png">
### Option 2: text-based replica placeholder
The second option is inspired by the recent effort of [unifying Site Editing block placeholders](https://github.com/WordPress/gutenberg/issues/35501). In situations in which the blocks have no data to reference, the blocks are now showing basic descriptions in place of where the relevant elements would be e.g. "Product title" where the title of the product would show.
The main downsides of this option are:
- Given that the placeholder mimics the actual template that will be rendered on the Frontend, the placeholder can get very large which makes it difficult for a merchant to move it around in the editor. The user experience arguably isn't great.
- Implementing this option means we'll have to basically replicate each entire template in the editor. Given that these placeholders are a temporary stopgap solution, it is up for debate if this is worth the time commitment required.
<img width="500" alt="Screenshot 2021-10-14 at 17 20 00" src="https://user-images.githubusercontent.com/1562646/137441560-f43d1b24-4fe0-4afd-894f-7495fd0470ad.png">
### Option 3.1: wireframe replica placeholder
The third option is inspired by the navigation block empty state placeholder. In situations in which the block has no data, it's showing a basic wireframe representation of the content.
The main downsides of this option are:
- Given that the placeholder mimics the actual template that will be rendered on the Frontend, the placeholder can get very large which makes it difficult for a merchant to move it around in the editor. The user experience arguably isn't great.
- While this option is a little less involved than option 2, implementing this option still means we'll have to basically replicate each entire template in the editor. Given that these placeholders are a temporary stopgap solution, it is up for debate if this is worth the time commitment required.
<img width="500" alt="Screenshot 2021-10-14 at 17 52 47" src="https://user-images.githubusercontent.com/1562646/137442283-975c8a26-fa4e-4204-a7e2-9c0e78173a25.png">
### Option 3.2: image-based wireframe replica placeholder
A potential solution to reducing the time investment for this option could be to just include an image wireframe representing the template. The assumption here is that designing these wireframes in Figma would probably be quicker than building out each wireframe with actual markup/styles?
<img width="500" alt="Screenshot 2021-10-15 at 08 49 01" src="https://user-images.githubusercontent.com/1562646/137444374-13318db4-3967-4581-8e29-7331c28ab062.png">
| non_priority | decide on and design template block placeholders for the editor context for the we re converting a set of woocommerce php templates to a block each initially the goal is not to create fully featured blocks but instead create one basic block per php template that renders a placeholder in the editor and the template on the frontend goal the goal of this particular issue is to decide on the placeholder design and copy for the editor ideas we created some basic prototypes to demonstrate the design challenge and offer some initial ideas on potential solutions option simple text based placeholder the first option would be to display a simple text based placeholder that provides the merchant with an explanation that a they are seeing a placeholder they can move and add blocks around and b that the placeholder will be replaced by the related woocommerce template on the frontend this simple option has a couple of key advantages its compact size makes it easy for a merchant to move around and edit the page with other blocks for example if they d like to move the template block into a column layout it s easier to move a compact block than a prominent wireframe placeholder like below it s very straightforward to implement given that these placeholders are a temporary stopgap solution it is at least up for debate on how much work should go into creating them note we just used the notice component inside the placeholder component for the prototype here as per it sounds like the notice should only be used for top level notices we d have to use something else here img width alt screenshot at src option text based replica placeholder the second option is inspired by the recent effort of in situations in which the blocks have no data to reference the blocks are now showing basic descriptions in place of where the relevant elements would be e g product title where the title of the product would show the main downsides of this option are given that the placeholder mimics the actual template that will be rendered on the frontend the placeholder can get very large which makes it difficult for a merchant to move it around in the editor the user experience arguably isn t great implementing this option means we ll have to basically replicate each entire template in the editor given that these placeholders are a temporary stopgap solution it is up for debate if this is worth the time commitment required img width alt screenshot at src option wireframe replica placeholder the third option is inspired by the navigation block empty state placeholder in situations in which the block has no data it s showing a basic wireframe representation of the content the main downsides of this option are given that the placeholder mimics the actual template that will be rendered on the frontend the placeholder can get very large which makes it difficult for a merchant to move it around in the editor the user experience arguably isn t great while this option is a little less involved than option implementing this option still means we ll have to basically replicate each entire template in the editor given that these placeholders are a temporary stopgap solution it is up for debate if this is worth the time commitment required img width alt screenshot at src option image based wireframe replica placeholder a potential solution to reducing the time investment for this option could be to just include an image wireframe representing the template the assumption here is that designing these wireframes in figma would probably be quicker than building out each wireframe with actual markup styles img width alt screenshot at src | 0 |
121,973 | 12,138,355,449 | IssuesEvent | 2020-04-23 17:06:43 | CTeX-org/ctex-kit | https://api.github.com/repos/CTeX-org/ctex-kit | closed | ctex: \CTEXifname 的名称和用法问题 | ctex documentation | 目前 `ctex` 文档中对 `\CTEXifname` 的说明如下：
> `\CTEXifname` 用于根据当前章节的名字的有无设置不同的格式。……例如，设置章的标题有名字时左对齐，无名字时居中对齐，并且在标题后画一条横线。
但在代码部分的注释却是「用于判断当前标题是否有编号」，且从后续代码来看确实是用来判断是否有编号而非名字的。
所以，是否应当重新命名这一命令，或是仅仅修改文档？以及这一名称的由来有什么解释吗？
有关信息：`\CTEXifname` 是在 fbfc484f81c1a9568c02642c541d249562b74e26 引入的，之后基本没有做过修改。 | 1.0 | ctex: \CTEXifname 的名称和用法问题 - 目前 `ctex` 文档中对 `\CTEXifname` 的说明如下：
> `\CTEXifname` 用于根据当前章节的名字的有无设置不同的格式。……例如，设置章的标题有名字时左对齐，无名字时居中对齐，并且在标题后画一条横线。
但在代码部分的注释却是「用于判断当前标题是否有编号」，且从后续代码来看确实是用来判断是否有编号而非名字的。
所以，是否应当重新命名这一命令，或是仅仅修改文档？以及这一名称的由来有什么解释吗？
有关信息：`\CTEXifname` 是在 fbfc484f81c1a9568c02642c541d249562b74e26 引入的，之后基本没有做过修改。 | non_priority | ctex ctexifname 的名称和用法问题 目前 ctex 文档中对 ctexifname 的说明如下： ctexifname 用于根据当前章节的名字的有无设置不同的格式。……例如，设置章的标题有名字时左对齐，无名字时居中对齐，并且在标题后画一条横线。 但在代码部分的注释却是「用于判断当前标题是否有编号」，且从后续代码来看确实是用来判断是否有编号而非名字的。 所以，是否应当重新命名这一命令，或是仅仅修改文档？以及这一名称的由来有什么解释吗？ 有关信息： ctexifname 是在 引入的，之后基本没有做过修改。 | 0 |
112,679 | 14,273,563,399 | IssuesEvent | 2020-11-21 22:20:28 | flutter/flutter | https://api.github.com/repos/flutter/flutter | closed | Implement material icon toggles | P4 f: material design framework severe: new feature | Icon and IconButton doesn't use colors from the current theme, it should probably read them from the primaryIconTheme property of the ThemeData. Also, by default the theme uses black and white colors while the material design spec says they should be gray.
| 1.0 | Implement material icon toggles - Icon and IconButton doesn't use colors from the current theme, it should probably read them from the primaryIconTheme property of the ThemeData. Also, by default the theme uses black and white colors while the material design spec says they should be gray.
| non_priority | implement material icon toggles icon and iconbutton doesn t use colors from the current theme it should probably read them from the primaryicontheme property of the themedata also by default the theme uses black and white colors while the material design spec says they should be gray | 0 |
64,371 | 6,901,100,074 | IssuesEvent | 2017-11-25 01:40:53 | alleyinteractive/wordpress-fieldmanager | https://api.github.com/repos/alleyinteractive/wordpress-fieldmanager | closed | Increase selector specificity for initializing display-if fields | needs-tests scope:display-if scope:field | As @danielbachhuber [noted](https://github.com/alleyinteractive/wordpress-fieldmanager/pull/399#discussion_r46553341), targeting any element with the `display-if` class has a high potential for false positives. We could reduce that potential by using a selector with some more FM-specific information.
| 1.0 | Increase selector specificity for initializing display-if fields - As @danielbachhuber [noted](https://github.com/alleyinteractive/wordpress-fieldmanager/pull/399#discussion_r46553341), targeting any element with the `display-if` class has a high potential for false positives. We could reduce that potential by using a selector with some more FM-specific information.
| non_priority | increase selector specificity for initializing display if fields as danielbachhuber targeting any element with the display if class has a high potential for false positives we could reduce that potential by using a selector with some more fm specific information | 0 |
5,053 | 2,902,499,769 | IssuesEvent | 2015-06-18 07:27:15 | excilys/androidannotations | https://api.github.com/repos/excilys/androidannotations | closed | REST POST | Documentation | There are no more arguments and file uploading example?
I pass parameters through the following form, not accepted by the server.
@Post("/user/register")
@Accept(MediaType.APPLICATION_JSON)
ResponseEntity<User> register(MultiValueMap multiValueMap);
There is, if the multi-parameter and multi-file upload together, how do
Sorry I could not find an example | 1.0 | REST POST - There are no more arguments and file uploading example?
I pass parameters through the following form, not accepted by the server.
@Post("/user/register")
@Accept(MediaType.APPLICATION_JSON)
ResponseEntity<User> register(MultiValueMap multiValueMap);
There is, if the multi-parameter and multi-file upload together, how do
Sorry I could not find an example | non_priority | rest post there are no more arguments and file uploading example i pass parameters through the following form not accepted by the server post user register accept mediatype application json responseentity register multivaluemap multivaluemap there is if the multi parameter and multi file upload together how do sorry i could not find an example | 0 |
47,885 | 13,259,114,867 | IssuesEvent | 2020-08-20 16:16:11 | tech256/jobs | https://api.github.com/repos/tech256/jobs | closed | Cyber Analyst (#1405711) | Active Clearance Required Cyber Security Hiring stale | PeopleTec is currently seeking a Cyber Analyst to support our Huntsville, AL location.
PeopleTec is currently searching for a Cyber Analyst to support an Aviation customer in our Huntsville, AL location. The ideal candidate will be responsible for development of the Assess and Authorize package for various Aviation customer tactical systems. Candidate will also be responsible for the continuous monitoring and IV&V of these systems. The Cyber Analyst will be responsible for the development or updating of Risk Management Framework (RMF) documentation, standard operating procedures, policies and security instructions. Candidate will also be responsible for assisting in entering A&A data and documentation into eMASS and some system administration functions of aviation tactical systems.
Required Skills/Experience:
Strong communication and customer skills
Knowledge of cyber security
Background in IT or System administration
Minimum of 6+ years of related work experience
Knowledge of the Department of Defense Risk Management Framework (RMF) policies and procedures
Excellent technical domain knowledge
Great communication skills with peers and customers
Ability to adapt to a dynamic customer-oriented environment
Travel: Up to 20%
Must be a U.S. Citizen
An active DoD Secret clearance is required to perform this work. Candidates are required to have an active Secret clearance upon hire, and the ability to maintain this level of clearance during their employment.
Education Requirements:
BS degree in Computer Engineering, Cyber, or other technical domain
6+ years in system administration (10 years without degree)
1+ year in RMF and eMASS
Physical Job Requirements:
Must be able to lift and move up to 25lbs during hardware installations
Desired Skills:
Security+, CISSP, CEH, MCSE
People First. Technology Always.
PeopleTec, Inc. is an employee-owned small business founded in Huntsville, AL that provides exceptional customer support by employing and retaining a highly skilled workforce.
Culture: The name "PeopleTec" was deliberately chosen to remind us of our core value system - our people. Our company's foundation was built on placing our employees and customers first. With an award-winning atmosphere, we have matured into a company that boasts the best and brightest across multiple technical fields.
Career: At PeopleTec, we value your long-term goals. Whether it's through our continuing-education opportunities, our robust training programs, or our "People First" benefits package, PeopleTec truly believes that our best investments are our people.
Come Experience It.
EOE/Minorities/Females/Veterans/Disabled
PeopleTec, Inc. is an Equal Employment Opportunity employer and provides reasonable accommodation for qualified individuals with disabilities and disabled veterans in its job application procedures. If you have any difficulty using our online system and you need an accommodation due to a disability, you may use the following email address, HR@peopletec.com and/or phone number (256.319.3800) to contact us about your interest in employment with PeopleTec, Inc.
All qualified applicants will receive consideration for employment without regard to race, color, religion, sex, sexual orientation, gender identity, national origin, age, genetic information, citizenship, ancestry, marital status, protected veteran status, disability status or any other status protected by federal, state, or local law. PeopleTec, Inc. participates in E-Verify.
For more information, or to apply now, you must go to the website below. Please DO NOT email your resume to us as we only accept applications through our website.
https://www.applicantpro.com/openings/peopletec/jobs/1405711-424912 | True | Cyber Analyst (#1405711) - PeopleTec is currently seeking a Cyber Analyst to support our Huntsville, AL location.
PeopleTec is currently searching for a Cyber Analyst to support an Aviation customer in our Huntsville, AL location. The ideal candidate will be responsible for development of the Assess and Authorize package for various Aviation customer tactical systems. Candidate will also be responsible for the continuous monitoring and IV&V of these systems. The Cyber Analyst will be responsible for the development or updating of Risk Management Framework (RMF) documentation, standard operating procedures, policies and security instructions. Candidate will also be responsible for assisting in entering A&A data and documentation into eMASS and some system administration functions of aviation tactical systems.
Required Skills/Experience:
Strong communication and customer skills
Knowledge of cyber security
Background in IT or System administration
Minimum of 6+ years of related work experience
Knowledge of the Department of Defense Risk Management Framework (RMF) policies and procedures
Excellent technical domain knowledge
Great communication skills with peers and customers
Ability to adapt to a dynamic customer-oriented environment
Travel: Up to 20%
Must be a U.S. Citizen
An active DoD Secret clearance is required to perform this work. Candidates are required to have an active Secret clearance upon hire, and the ability to maintain this level of clearance during their employment.
Education Requirements:
BS degree in Computer Engineering, Cyber, or other technical domain
6+ years in system administration (10 years without degree)
1+ year in RMF and eMASS
Physical Job Requirements:
Must be able to lift and move up to 25lbs during hardware installations
Desired Skills:
Security+, CISSP, CEH, MCSE
People First. Technology Always.
PeopleTec, Inc. is an employee-owned small business founded in Huntsville, AL that provides exceptional customer support by employing and retaining a highly skilled workforce.
Culture: The name "PeopleTec" was deliberately chosen to remind us of our core value system - our people. Our company's foundation was built on placing our employees and customers first. With an award-winning atmosphere, we have matured into a company that boasts the best and brightest across multiple technical fields.
Career: At PeopleTec, we value your long-term goals. Whether it's through our continuing-education opportunities, our robust training programs, or our "People First" benefits package, PeopleTec truly believes that our best investments are our people.
Come Experience It.
EOE/Minorities/Females/Veterans/Disabled
PeopleTec, Inc. is an Equal Employment Opportunity employer and provides reasonable accommodation for qualified individuals with disabilities and disabled veterans in its job application procedures. If you have any difficulty using our online system and you need an accommodation due to a disability, you may use the following email address, HR@peopletec.com and/or phone number (256.319.3800) to contact us about your interest in employment with PeopleTec, Inc.
All qualified applicants will receive consideration for employment without regard to race, color, religion, sex, sexual orientation, gender identity, national origin, age, genetic information, citizenship, ancestry, marital status, protected veteran status, disability status or any other status protected by federal, state, or local law. PeopleTec, Inc. participates in E-Verify.
For more information, or to apply now, you must go to the website below. Please DO NOT email your resume to us as we only accept applications through our website.
https://www.applicantpro.com/openings/peopletec/jobs/1405711-424912 | non_priority | cyber analyst peopletec is currently seeking a cyber analyst to support our huntsville al location peopletec is currently searching for a cyber analyst to support an aviation customer in our huntsville al location the ideal candidate will be responsible for development of the assess and authorize package for various aviation customer tactical systems candidate will also be responsible for the continuous monitoring and iv v of these systems the cyber analyst will be responsible for the development or updating of risk management framework rmf documentation standard operating procedures policies and security instructions candidate will also be responsible for assisting in entering a a data and documentation into emass and some system administration functions of aviation tactical systems required skills experience strong communication and customer skills knowledge of cyber security background in it or system administration minimum of years of related work experience knowledge of the department of defense risk management framework rmf policies and procedures excellent technical domain knowledge great communication skills with peers and customers ability to adapt to a dynamic customer oriented environment travel up to must be a u s citizen an active dod secret clearance is required to perform this work candidates are required to have an active secret clearance upon hire and the ability to maintain this level of clearance during their employment education requirements bs degree in computer engineering cyber or other technical domain years in system administration years without degree year in rmf and emass physical job requirements must be able to lift and move up to during hardware installations desired skills security cissp ceh mcse people first technology always peopletec inc is an employee owned small business founded in huntsville al that provides exceptional customer support by employing and retaining a highly skilled workforce culture the name peopletec was deliberately chosen to remind us of our core value system our people our company s foundation was built on placing our employees and customers first with an award winning atmosphere we have matured into a company that boasts the best and brightest across multiple technical fields career at peopletec we value your long term goals whether it s through our continuing education opportunities our robust training programs or our people first benefits package peopletec truly believes that our best investments are our people come experience it eoe minorities females veterans disabled peopletec inc is an equal employment opportunity employer and provides reasonable accommodation for qualified individuals with disabilities and disabled veterans in its job application procedures if you have any difficulty using our online system and you need an accommodation due to a disability you may use the following email address hr peopletec com and or phone number to contact us about your interest in employment with peopletec inc all qualified applicants will receive consideration for employment without regard to race color religion sex sexual orientation gender identity national origin age genetic information citizenship ancestry marital status protected veteran status disability status or any other status protected by federal state or local law peopletec inc participates in e verify for more information or to apply now you must go to the website below please do not email your resume to us as we only accept applications through our website | 0 |
20,701 | 27,385,849,614 | IssuesEvent | 2023-02-28 13:16:10 | microsoftgraph/msgraph-metadata | https://api.github.com/repos/microsoftgraph/msgraph-metadata | closed | beta generation failing because of delta function | Generator: Metadata Preprocessor metadata-issue blocking | [beta weekly generation is currently failing](https://microsoftgraph.visualstudio.com/Graph%20Developer%20Experiences/_build/results?buildId=106293&view=logs&j=4c81e8e4-6eb9-5def-7261-b44ad0fc1b7d&t=163839c6-f69e-5b5d-39e2-5b38e97d3fe3) because [a delta function on directory objects was added](https://dev.azure.com/msazure/One/_git/AD-AggregatorService-Workloads/pullRequest/7582888#1676991425) which conflicts with the derived types delta functions.
I believe we should introduce an xsl fix that removes the functions on the derived types, only for beta, only for kiota based SDK for the time being until the service fixes their definition to unblock our generation pipeline, but I'm open to feedback here first.
CC @andrueastman @peombwa @irvinesunday | 1.0 | beta generation failing because of delta function - [beta weekly generation is currently failing](https://microsoftgraph.visualstudio.com/Graph%20Developer%20Experiences/_build/results?buildId=106293&view=logs&j=4c81e8e4-6eb9-5def-7261-b44ad0fc1b7d&t=163839c6-f69e-5b5d-39e2-5b38e97d3fe3) because [a delta function on directory objects was added](https://dev.azure.com/msazure/One/_git/AD-AggregatorService-Workloads/pullRequest/7582888#1676991425) which conflicts with the derived types delta functions.
I believe we should introduce an xsl fix that removes the functions on the derived types, only for beta, only for kiota based SDK for the time being until the service fixes their definition to unblock our generation pipeline, but I'm open to feedback here first.
CC @andrueastman @peombwa @irvinesunday | non_priority | beta generation failing because of delta function because which conflicts with the derived types delta functions i believe we should introduce an xsl fix that removes the functions on the derived types only for beta only for kiota based sdk for the time being until the service fixes their definition to unblock our generation pipeline but i m open to feedback here first cc andrueastman peombwa irvinesunday | 0 |
38,209 | 5,168,753,999 | IssuesEvent | 2017-01-17 22:28:02 | mozilla/activity-stream | https://api.github.com/repos/mozilla/activity-stream | closed | Add tests to make sure we add listeners for each event from content | Chore P3 Tests | Right now we don't actually have tests to make sure we've added listeners for every event content will send.
We should make sure all actions defined in `common/action-manager`, such as `NOTIFY_USER_EVENT`, actually triggers a handler in the addon.
| 1.0 | Add tests to make sure we add listeners for each event from content - Right now we don't actually have tests to make sure we've added listeners for every event content will send.
We should make sure all actions defined in `common/action-manager`, such as `NOTIFY_USER_EVENT`, actually triggers a handler in the addon.
| non_priority | add tests to make sure we add listeners for each event from content right now we don t actually have tests to make sure we ve added listeners for every event content will send we should make sure all actions defined in common action manager such as notify user event actually triggers a handler in the addon | 0 |
262,984 | 19,850,257,377 | IssuesEvent | 2022-01-21 11:27:49 | RaphaelNeubert/I5_GPS_Tracks | https://api.github.com/repos/RaphaelNeubert/I5_GPS_Tracks | opened | UC Tracks auflisten (Optionale Fortsetzung) Loeschen | documentation | Track loeschen als optionale Fortsetzung von UC Tracks auflisten hinzufuegen | 1.0 | UC Tracks auflisten (Optionale Fortsetzung) Loeschen - Track loeschen als optionale Fortsetzung von UC Tracks auflisten hinzufuegen | non_priority | uc tracks auflisten optionale fortsetzung loeschen track loeschen als optionale fortsetzung von uc tracks auflisten hinzufuegen | 0 |
244,199 | 26,373,668,870 | IssuesEvent | 2023-01-11 23:16:44 | snowdensb/job-dsl-plugin | https://api.github.com/repos/snowdensb/job-dsl-plugin | opened | CVE-2021-37533 (Medium) detected in commons-net-3.6.jar | security vulnerability | ## CVE-2021-37533 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>commons-net-3.6.jar</b></p></summary>
<p>Apache Commons Net library contains a collection of network utilities and protocol implementations.
Supported protocols include: Echo, Finger, FTP, NNTP, NTP, POP3(S), SMTP(S), Telnet, Whois</p>
<p>Path to dependency file: /build.gradle</p>
<p>Path to vulnerable library: /tmp/ws-ua_20210927190226_TRFFHW/downloadResource_SQXZWB/20210927190451/commons-net-3.6.jar</p>
<p>
Dependency Hierarchy:
- jenkins-test-harness-2.60.jar (Root Library)
- jenkins-test-harness-htmlunit-2.36.0-1.jar
- :x: **commons-net-3.6.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/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
Prior to Apache Commons Net 3.9.0, Net's FTP client trusts the host from PASV response by default. A malicious server can redirect the Commons Net code to use a different host, but the user has to connect to the malicious server in the first place. This may lead to leakage of information about services running on the private network of the client. The default in version 3.9.0 is now false to ignore such hosts, as cURL does. See https://issues.apache.org/jira/browse/NET-711.
<p>Publish Date: 2022-12-03
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2021-37533>CVE-2021-37533</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>6.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: 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://www.cve.org/CVERecord?id=CVE-2021-37533">https://www.cve.org/CVERecord?id=CVE-2021-37533</a></p>
<p>Release Date: 2022-12-03</p>
<p>Fix Resolution: commons-net:commons-net:3.9.0</p>
</p>
</details>
<p></p>
| True | CVE-2021-37533 (Medium) detected in commons-net-3.6.jar - ## CVE-2021-37533 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>commons-net-3.6.jar</b></p></summary>
<p>Apache Commons Net library contains a collection of network utilities and protocol implementations.
Supported protocols include: Echo, Finger, FTP, NNTP, NTP, POP3(S), SMTP(S), Telnet, Whois</p>
<p>Path to dependency file: /build.gradle</p>
<p>Path to vulnerable library: /tmp/ws-ua_20210927190226_TRFFHW/downloadResource_SQXZWB/20210927190451/commons-net-3.6.jar</p>
<p>
Dependency Hierarchy:
- jenkins-test-harness-2.60.jar (Root Library)
- jenkins-test-harness-htmlunit-2.36.0-1.jar
- :x: **commons-net-3.6.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/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
Prior to Apache Commons Net 3.9.0, Net's FTP client trusts the host from PASV response by default. A malicious server can redirect the Commons Net code to use a different host, but the user has to connect to the malicious server in the first place. This may lead to leakage of information about services running on the private network of the client. The default in version 3.9.0 is now false to ignore such hosts, as cURL does. See https://issues.apache.org/jira/browse/NET-711.
<p>Publish Date: 2022-12-03
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2021-37533>CVE-2021-37533</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>6.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: 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://www.cve.org/CVERecord?id=CVE-2021-37533">https://www.cve.org/CVERecord?id=CVE-2021-37533</a></p>
<p>Release Date: 2022-12-03</p>
<p>Fix Resolution: commons-net:commons-net:3.9.0</p>
</p>
</details>
<p></p>
| non_priority | cve medium detected in commons net jar cve medium severity vulnerability vulnerable library commons net jar apache commons net library contains a collection of network utilities and protocol implementations supported protocols include echo finger ftp nntp ntp s smtp s telnet whois path to dependency file build gradle path to vulnerable library tmp ws ua trffhw downloadresource sqxzwb commons net jar dependency hierarchy jenkins test harness jar root library jenkins test harness htmlunit jar x commons net jar vulnerable library found in head commit a href found in base branch master vulnerability details prior to apache commons net net s ftp client trusts the host from pasv response by default a malicious server can redirect the commons net code to use a different host but the user has to connect to the malicious server in the first place this may lead to leakage of information about services running on the private network of the client the default in version is now false to ignore such hosts as curl does see publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction required scope unchanged impact metrics confidentiality impact high integrity impact none availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution commons net commons net | 0 |
1,219 | 5,290,444,148 | IssuesEvent | 2017-02-08 19:54:35 | reactphp/react | https://api.github.com/repos/reactphp/react | closed | Move Buffer to EventLoop component, add libevent implementation | architecture event-loop | The write buffer is currently in the Socket component. But it really is more general purpose. For libevent we can provide an implementation that uses [event_buffer_write](http://php.net/event_buffer_write), which may give us some speed improvements.
| 1.0 | Move Buffer to EventLoop component, add libevent implementation - The write buffer is currently in the Socket component. But it really is more general purpose. For libevent we can provide an implementation that uses [event_buffer_write](http://php.net/event_buffer_write), which may give us some speed improvements.
| non_priority | move buffer to eventloop component add libevent implementation the write buffer is currently in the socket component but it really is more general purpose for libevent we can provide an implementation that uses which may give us some speed improvements | 0 |
401,685 | 27,335,962,739 | IssuesEvent | 2023-02-26 07:46:28 | MLNLP-World/AI-Paper-Collector | https://api.github.com/repos/MLNLP-World/AI-Paper-Collector | closed | [Question]搜索的时候会出错怎么办 | documentation | **Question**
本地和colab上执行都会出错，请问下这怎么解决呢
**Screenshots**
Traceback (most recent call last):
File "main.py", line 60, in <module>
main()
File "main.py", line 43, in main
results = exec_search(indexes, candidates, query, mode, threshold, confs, limit)
File "/content/AI-Paper-Collector/searcher.py", line 179, in exec_search
results = exact_search(indexes, query, confs)
File "/content/AI-Paper-Collector/searcher.py", line 86, in exact_search
results = [item for item in indexes if query in item[1].lower()]
File "/content/AI-Paper-Collector/searcher.py", line 86, in <listcomp>
results = [item for item in indexes if query in item[1].lower()]
AttributeError: 'dict' object has no attribute 'lower'
| 1.0 | [Question]搜索的时候会出错怎么办 - **Question**
本地和colab上执行都会出错，请问下这怎么解决呢
**Screenshots**
Traceback (most recent call last):
File "main.py", line 60, in <module>
main()
File "main.py", line 43, in main
results = exec_search(indexes, candidates, query, mode, threshold, confs, limit)
File "/content/AI-Paper-Collector/searcher.py", line 179, in exec_search
results = exact_search(indexes, query, confs)
File "/content/AI-Paper-Collector/searcher.py", line 86, in exact_search
results = [item for item in indexes if query in item[1].lower()]
File "/content/AI-Paper-Collector/searcher.py", line 86, in <listcomp>
results = [item for item in indexes if query in item[1].lower()]
AttributeError: 'dict' object has no attribute 'lower'
| non_priority | 搜索的时候会出错怎么办 question 本地和colab上执行都会出错，请问下这怎么解决呢 screenshots traceback most recent call last file main py line in main file main py line in main results exec search indexes candidates query mode threshold confs limit file content ai paper collector searcher py line in exec search results exact search indexes query confs file content ai paper collector searcher py line in exact search results lower file content ai paper collector searcher py line in results lower attributeerror dict object has no attribute lower | 0 |
92,256 | 11,616,199,230 | IssuesEvent | 2020-02-26 15:21:22 | nextcloud/mail | https://api.github.com/repos/nextcloud/mail | closed | Dark theme in mail app | 1. to develop design help wanted papercut | *Note: I don't know if I should post here or on mail tracker. I can repost if needed.*
### Actual behaviour
With Dark theme enabled, I see the following inconsistencies:
* Folder icons are still black
* Text in message panel containing "From XX to YY" is still black.
* Multipart messages with HTML are displayed with black font. Default font color should be light grey.
* Lack of contrast on HTML mails (see below screenshots of the same mail)
### Server configuration
Nextcloud 14.0.4
Mail app 0.11.0
<bountysource-plugin>
---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/67268610-dark-theme-in-mail-app?utm_campaign=plugin&utm_content=tracker%2F44154351&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F44154351&utm_medium=issues&utm_source=github).
</bountysource-plugin> | 1.0 | Dark theme in mail app - *Note: I don't know if I should post here or on mail tracker. I can repost if needed.*
### Actual behaviour
With Dark theme enabled, I see the following inconsistencies:
* Folder icons are still black
* Text in message panel containing "From XX to YY" is still black.
* Multipart messages with HTML are displayed with black font. Default font color should be light grey.
* Lack of contrast on HTML mails (see below screenshots of the same mail)
### Server configuration
Nextcloud 14.0.4
Mail app 0.11.0
<bountysource-plugin>
---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/67268610-dark-theme-in-mail-app?utm_campaign=plugin&utm_content=tracker%2F44154351&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F44154351&utm_medium=issues&utm_source=github).
</bountysource-plugin> | non_priority | dark theme in mail app note i don t know if i should post here or on mail tracker i can repost if needed actual behaviour with dark theme enabled i see the following inconsistencies folder icons are still black text in message panel containing from xx to yy is still black multipart messages with html are displayed with black font default font color should be light grey lack of contrast on html mails see below screenshots of the same mail server configuration nextcloud mail app want to back this issue we accept bounties via | 0 |
148,918 | 19,560,731,417 | IssuesEvent | 2022-01-03 15:52:56 | shaimael/Webgoat | https://api.github.com/repos/shaimael/Webgoat | opened | CVE-2021-21342 (High) detected in xstream-1.4.5.jar | security vulnerability | ## CVE-2021-21342 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>xstream-1.4.5.jar</b></p></summary>
<p>XStream is a serialization library from Java objects to XML and back.</p>
<p>Path to dependency file: /webgoat-lessons/vulnerable-components/pom.xml</p>
<p>Path to vulnerable library: /m2/repository/com/thoughtworks/xstream/xstream/1.4.5/xstream-1.4.5.jar,/home/wss-scanner/.m2/repository/com/thoughtworks/xstream/xstream/1.4.5/xstream-1.4.5.jar,/home/wss-scanner/.m2/repository/com/thoughtworks/xstream/xstream/1.4.5/xstream-1.4.5.jar</p>
<p>
Dependency Hierarchy:
- :x: **xstream-1.4.5.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/shaimael/Webgoat/commit/06d8d0b5bb8a459ba3d47f61a64fe00c62662d81">06d8d0b5bb8a459ba3d47f61a64fe00c62662d81</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
XStream is a Java library to serialize objects to XML and back again. In XStream before version 1.4.16, there is a vulnerability where the processed stream at unmarshalling time contains type information to recreate the formerly written objects. XStream creates therefore new instances based on these type information. An attacker can manipulate the processed input stream and replace or inject objects, that result in a server-side forgery request. No user is affected, who followed the recommendation to setup XStream's security framework with a whitelist limited to the minimal required types. If you rely on XStream's default blacklist of the Security Framework, you will have to use at least version 1.4.16.
<p>Publish Date: 2021-03-23
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-21342>CVE-2021-21342</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>9.1</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/x-stream/xstream/security/advisories/GHSA-hvv8-336g-rx3m">https://github.com/x-stream/xstream/security/advisories/GHSA-hvv8-336g-rx3m</a></p>
<p>Release Date: 2021-03-23</p>
<p>Fix Resolution: com.thoughtworks.xstream:xstream:1.4.16</p>
</p>
</details>
<p></p>
***
:rescue_worker_helmet: Automatic Remediation is available for this issue
<!-- <REMEDIATE>{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"Java","groupId":"com.thoughtworks.xstream","packageName":"xstream","packageVersion":"1.4.5","packageFilePaths":["/webgoat-lessons/vulnerable-components/pom.xml"],"isTransitiveDependency":false,"dependencyTree":"com.thoughtworks.xstream:xstream:1.4.5","isMinimumFixVersionAvailable":true,"minimumFixVersion":"com.thoughtworks.xstream:xstream:1.4.16","isBinary":false}],"baseBranches":["main"],"vulnerabilityIdentifier":"CVE-2021-21342","vulnerabilityDetails":"XStream is a Java library to serialize objects to XML and back again. In XStream before version 1.4.16, there is a vulnerability where the processed stream at unmarshalling time contains type information to recreate the formerly written objects. XStream creates therefore new instances based on these type information. An attacker can manipulate the processed input stream and replace or inject objects, that result in a server-side forgery request. No user is affected, who followed the recommendation to setup XStream\u0027s security framework with a whitelist limited to the minimal required types. If you rely on XStream\u0027s default blacklist of the Security Framework, you will have to use at least version 1.4.16.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-21342","cvss3Severity":"high","cvss3Score":"9.1","cvss3Metrics":{"A":"None","AC":"Low","PR":"None","S":"Unchanged","C":"High","UI":"None","AV":"Network","I":"High"},"extraData":{}}</REMEDIATE> --> | True | CVE-2021-21342 (High) detected in xstream-1.4.5.jar - ## CVE-2021-21342 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>xstream-1.4.5.jar</b></p></summary>
<p>XStream is a serialization library from Java objects to XML and back.</p>
<p>Path to dependency file: /webgoat-lessons/vulnerable-components/pom.xml</p>
<p>Path to vulnerable library: /m2/repository/com/thoughtworks/xstream/xstream/1.4.5/xstream-1.4.5.jar,/home/wss-scanner/.m2/repository/com/thoughtworks/xstream/xstream/1.4.5/xstream-1.4.5.jar,/home/wss-scanner/.m2/repository/com/thoughtworks/xstream/xstream/1.4.5/xstream-1.4.5.jar</p>
<p>
Dependency Hierarchy:
- :x: **xstream-1.4.5.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/shaimael/Webgoat/commit/06d8d0b5bb8a459ba3d47f61a64fe00c62662d81">06d8d0b5bb8a459ba3d47f61a64fe00c62662d81</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
XStream is a Java library to serialize objects to XML and back again. In XStream before version 1.4.16, there is a vulnerability where the processed stream at unmarshalling time contains type information to recreate the formerly written objects. XStream creates therefore new instances based on these type information. An attacker can manipulate the processed input stream and replace or inject objects, that result in a server-side forgery request. No user is affected, who followed the recommendation to setup XStream's security framework with a whitelist limited to the minimal required types. If you rely on XStream's default blacklist of the Security Framework, you will have to use at least version 1.4.16.
<p>Publish Date: 2021-03-23
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-21342>CVE-2021-21342</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>9.1</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/x-stream/xstream/security/advisories/GHSA-hvv8-336g-rx3m">https://github.com/x-stream/xstream/security/advisories/GHSA-hvv8-336g-rx3m</a></p>
<p>Release Date: 2021-03-23</p>
<p>Fix Resolution: com.thoughtworks.xstream:xstream:1.4.16</p>
</p>
</details>
<p></p>
***
:rescue_worker_helmet: Automatic Remediation is available for this issue
<!-- <REMEDIATE>{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"Java","groupId":"com.thoughtworks.xstream","packageName":"xstream","packageVersion":"1.4.5","packageFilePaths":["/webgoat-lessons/vulnerable-components/pom.xml"],"isTransitiveDependency":false,"dependencyTree":"com.thoughtworks.xstream:xstream:1.4.5","isMinimumFixVersionAvailable":true,"minimumFixVersion":"com.thoughtworks.xstream:xstream:1.4.16","isBinary":false}],"baseBranches":["main"],"vulnerabilityIdentifier":"CVE-2021-21342","vulnerabilityDetails":"XStream is a Java library to serialize objects to XML and back again. In XStream before version 1.4.16, there is a vulnerability where the processed stream at unmarshalling time contains type information to recreate the formerly written objects. XStream creates therefore new instances based on these type information. An attacker can manipulate the processed input stream and replace or inject objects, that result in a server-side forgery request. No user is affected, who followed the recommendation to setup XStream\u0027s security framework with a whitelist limited to the minimal required types. If you rely on XStream\u0027s default blacklist of the Security Framework, you will have to use at least version 1.4.16.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-21342","cvss3Severity":"high","cvss3Score":"9.1","cvss3Metrics":{"A":"None","AC":"Low","PR":"None","S":"Unchanged","C":"High","UI":"None","AV":"Network","I":"High"},"extraData":{}}</REMEDIATE> --> | non_priority | cve high detected in xstream jar cve high severity vulnerability vulnerable library xstream jar xstream is a serialization library from java objects to xml and back path to dependency file webgoat lessons vulnerable components pom xml path to vulnerable library repository com thoughtworks xstream xstream xstream jar home wss scanner repository com thoughtworks xstream xstream xstream jar home wss scanner repository com thoughtworks xstream xstream xstream jar dependency hierarchy x xstream jar vulnerable library found in head commit a href found in base branch main vulnerability details xstream is a java library to serialize objects to xml and back again in xstream before version there is a vulnerability where the processed stream at unmarshalling time contains type information to recreate the formerly written objects xstream creates therefore new instances based on these type information an attacker can manipulate the processed input stream and replace or inject objects that result in a server side forgery request no user is affected who followed the recommendation to setup xstream s security framework with a whitelist limited to the minimal required types if you rely on xstream s default blacklist of the security framework you will have to use at least version publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact high integrity impact high availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution com thoughtworks xstream xstream rescue worker helmet automatic remediation is available for this issue isopenpronvulnerability true ispackagebased true isdefaultbranch true packages istransitivedependency false dependencytree com thoughtworks xstream xstream isminimumfixversionavailable true minimumfixversion com thoughtworks xstream xstream isbinary false basebranches vulnerabilityidentifier cve vulnerabilitydetails xstream is a java library to serialize objects to xml and back again in xstream before version there is a vulnerability where the processed stream at unmarshalling time contains type information to recreate the formerly written objects xstream creates therefore new instances based on these type information an attacker can manipulate the processed input stream and replace or inject objects that result in a server side forgery request no user is affected who followed the recommendation to setup xstream security framework with a whitelist limited to the minimal required types if you rely on xstream default blacklist of the security framework you will have to use at least version vulnerabilityurl | 0 |
342,973 | 24,762,961,532 | IssuesEvent | 2022-10-22 06:08:32 | ryan-way/newgameplus | https://api.github.com/repos/ryan-way/newgameplus | closed | Game Architecture Requirements | documentation | - Persistence
- Logging
- Monitoring (data gathering)
- Allow for long running jobs | 1.0 | Game Architecture Requirements - - Persistence
- Logging
- Monitoring (data gathering)
- Allow for long running jobs | non_priority | game architecture requirements persistence logging monitoring data gathering allow for long running jobs | 0 |
23,200 | 7,297,651,164 | IssuesEvent | 2018-02-26 14:51:14 | debrief/debrief | https://api.github.com/repos/debrief/debrief | opened | Improved Twitter posting | build help wanted | We send automated Tweets on new releases.
But, they're very boring Tweets:
We should follow an improved process. I think it's currently done by IFTTT. We should try to extend/modify the function to:
* include an image, if there is on in the Release notes
* include more descriptive text. I could make the first para an overview, and we us the first para for the body of the tweet. | 1.0 | Improved Twitter posting - We send automated Tweets on new releases.
But, they're very boring Tweets:
We should follow an improved process. I think it's currently done by IFTTT. We should try to extend/modify the function to:
* include an image, if there is on in the Release notes
* include more descriptive text. I could make the first para an overview, and we us the first para for the body of the tweet. | non_priority | improved twitter posting we send automated tweets on new releases but they re very boring tweets we should follow an improved process i think it s currently done by ifttt we should try to extend modify the function to include an image if there is on in the release notes include more descriptive text i could make the first para an overview and we us the first para for the body of the tweet | 0 |
161,222 | 12,534,179,299 | IssuesEvent | 2020-06-04 18:57:05 | astropy/astropy | https://api.github.com/repos/astropy/astropy | closed | tox -e codestyle fails on astropy/_erfa/core.py | Bug Docs testing | <!-- This comments are hidden when you submit the issue,
so you do not need to remove them! -->
<!-- Please be sure to check out our contributing guidelines,
https://github.com/astropy/astropy/blob/master/CONTRIBUTING.md .
Please be sure to check out our code of conduct,
https://github.com/astropy/astropy/blob/master/CODE_OF_CONDUCT.md . -->
<!-- Please have a search on our GitHub repository to see if a similar
issue has already been posted.
If a similar issue is closed, have a quick look to see if you are satisfied
by the resolution.
If not please go ahead and open an issue! -->
<!-- Please check that the development version still produces the same bug.
You can install development version with
pip install git+https://github.com/astropy/astropy
command. -->
### Description
<!-- Provide a general description of the bug. -->
`tox -e codestyle` always fails with a huge stream of code style violations in `astropy/_erfa/core.py`. This renders it largely useless for checking my own code for style violations.
I assume the file is auto-generated, so simply telling the job to ignore code style violations in that file might solve the problem. If not, a once-over with `black` or `autopep8` would probably resolve the issue.
### Expected behavior
<!-- What did you expect to happen. -->
`tox -e codestyle` succeeds on a clean master.
### Actual behavior
<!-- What actually happened. -->
<!-- Was the output confusing or poorly described? -->
```
...
astropy/_erfa/core.py:20058:37: W291 trailing whitespace
astropy/_erfa/core.py:20101:37: W291 trailing whitespace
astropy/_erfa/core.py:20146:37: W291 trailing whitespace
astropy/_erfa/core.py:20187:37: W291 trailing whitespace
astropy/_erfa/core.py:20231:37: W291 trailing whitespace
astropy/_erfa/core.py:20272:37: W291 trailing whitespace
astropy/_erfa/core.py:20342:22: W292 no newline at end of file
244
ERROR: InvocationError for command /home/archibald/projects/astropy/astropy/.tox/codestyle/bin/flake8 astropy --count --select=E101,W191,W291,W292,W293,W391,E111,E112,E113,E30,E502,E722,E901,E902,E999,F822,F823 (exited with code 1)
_______________________________________________________ summary _______________________________________________________
ERROR: codestyle: commands failed
```
### Steps to Reproduce
<!-- Ideally a code example could be provided so we can run it ourselves. -->
<!-- If you are pasting code, use triple backticks (```) around
your code snippet. -->
<!-- If necessary, sanitize your screen output to be pasted so you do not
reveal secrets like tokens and passwords. -->
```sh
tox -e codestyle
```
### System Details
<!-- Even if you do not think this is necessary, it is useful information for the maintainers.
Please run the following snippet and paste the output below:
import platform; print(platform.platform())
import sys; print("Python", sys.version)
import numpy; print("Numpy", numpy.__version__)
import astropy; print("astropy", astropy.__version__)
import scipy; print("Scipy", scipy.__version__)
import matplotlib; print("Matplotlib", matplotlib.__version__)
-->
```
>>> import platform; print(platform.platform())
Linux-5.4.0-33-generic-x86_64-with-glibc2.29
>>> import sys; print("Python", sys.version)
Python 3.8.2 (default, Apr 27 2020, 15:53:34)
[GCC 9.3.0]
>>> import numpy; print("Numpy", numpy.__version__)
Numpy 1.18.4
>>> import astropy; print("astropy", astropy.__version__)
astropy 4.2.dev162+gd0a1e469f
>>> import scipy; print("Scipy", scipy.__version__)
Scipy 1.4.1
>>> import matplotlib; print("Matplotlib", matplotlib.__version__)
Matplotlib 3.2.1
``` | 1.0 | tox -e codestyle fails on astropy/_erfa/core.py - <!-- This comments are hidden when you submit the issue,
so you do not need to remove them! -->
<!-- Please be sure to check out our contributing guidelines,
https://github.com/astropy/astropy/blob/master/CONTRIBUTING.md .
Please be sure to check out our code of conduct,
https://github.com/astropy/astropy/blob/master/CODE_OF_CONDUCT.md . -->
<!-- Please have a search on our GitHub repository to see if a similar
issue has already been posted.
If a similar issue is closed, have a quick look to see if you are satisfied
by the resolution.
If not please go ahead and open an issue! -->
<!-- Please check that the development version still produces the same bug.
You can install development version with
pip install git+https://github.com/astropy/astropy
command. -->
### Description
<!-- Provide a general description of the bug. -->
`tox -e codestyle` always fails with a huge stream of code style violations in `astropy/_erfa/core.py`. This renders it largely useless for checking my own code for style violations.
I assume the file is auto-generated, so simply telling the job to ignore code style violations in that file might solve the problem. If not, a once-over with `black` or `autopep8` would probably resolve the issue.
### Expected behavior
<!-- What did you expect to happen. -->
`tox -e codestyle` succeeds on a clean master.
### Actual behavior
<!-- What actually happened. -->
<!-- Was the output confusing or poorly described? -->
```
...
astropy/_erfa/core.py:20058:37: W291 trailing whitespace
astropy/_erfa/core.py:20101:37: W291 trailing whitespace
astropy/_erfa/core.py:20146:37: W291 trailing whitespace
astropy/_erfa/core.py:20187:37: W291 trailing whitespace
astropy/_erfa/core.py:20231:37: W291 trailing whitespace
astropy/_erfa/core.py:20272:37: W291 trailing whitespace
astropy/_erfa/core.py:20342:22: W292 no newline at end of file
244
ERROR: InvocationError for command /home/archibald/projects/astropy/astropy/.tox/codestyle/bin/flake8 astropy --count --select=E101,W191,W291,W292,W293,W391,E111,E112,E113,E30,E502,E722,E901,E902,E999,F822,F823 (exited with code 1)
_______________________________________________________ summary _______________________________________________________
ERROR: codestyle: commands failed
```
### Steps to Reproduce
<!-- Ideally a code example could be provided so we can run it ourselves. -->
<!-- If you are pasting code, use triple backticks (```) around
your code snippet. -->
<!-- If necessary, sanitize your screen output to be pasted so you do not
reveal secrets like tokens and passwords. -->
```sh
tox -e codestyle
```
### System Details
<!-- Even if you do not think this is necessary, it is useful information for the maintainers.
Please run the following snippet and paste the output below:
import platform; print(platform.platform())
import sys; print("Python", sys.version)
import numpy; print("Numpy", numpy.__version__)
import astropy; print("astropy", astropy.__version__)
import scipy; print("Scipy", scipy.__version__)
import matplotlib; print("Matplotlib", matplotlib.__version__)
-->
```
>>> import platform; print(platform.platform())
Linux-5.4.0-33-generic-x86_64-with-glibc2.29
>>> import sys; print("Python", sys.version)
Python 3.8.2 (default, Apr 27 2020, 15:53:34)
[GCC 9.3.0]
>>> import numpy; print("Numpy", numpy.__version__)
Numpy 1.18.4
>>> import astropy; print("astropy", astropy.__version__)
astropy 4.2.dev162+gd0a1e469f
>>> import scipy; print("Scipy", scipy.__version__)
Scipy 1.4.1
>>> import matplotlib; print("Matplotlib", matplotlib.__version__)
Matplotlib 3.2.1
``` | non_priority | tox e codestyle fails on astropy erfa core py this comments are hidden when you submit the issue so you do not need to remove them please be sure to check out our contributing guidelines please be sure to check out our code of conduct please have a search on our github repository to see if a similar issue has already been posted if a similar issue is closed have a quick look to see if you are satisfied by the resolution if not please go ahead and open an issue please check that the development version still produces the same bug you can install development version with pip install git command description tox e codestyle always fails with a huge stream of code style violations in astropy erfa core py this renders it largely useless for checking my own code for style violations i assume the file is auto generated so simply telling the job to ignore code style violations in that file might solve the problem if not a once over with black or would probably resolve the issue expected behavior tox e codestyle succeeds on a clean master actual behavior astropy erfa core py trailing whitespace astropy erfa core py trailing whitespace astropy erfa core py trailing whitespace astropy erfa core py trailing whitespace astropy erfa core py trailing whitespace astropy erfa core py trailing whitespace astropy erfa core py no newline at end of file error invocationerror for command home archibald projects astropy astropy tox codestyle bin astropy count select exited with code summary error codestyle commands failed steps to reproduce if you are pasting code use triple backticks around your code snippet if necessary sanitize your screen output to be pasted so you do not reveal secrets like tokens and passwords sh tox e codestyle system details even if you do not think this is necessary it is useful information for the maintainers please run the following snippet and paste the output below import platform print platform platform import sys print python sys version import numpy print numpy numpy version import astropy print astropy astropy version import scipy print scipy scipy version import matplotlib print matplotlib matplotlib version import platform print platform platform linux generic with import sys print python sys version python default apr import numpy print numpy numpy version numpy import astropy print astropy astropy version astropy import scipy print scipy scipy version scipy import matplotlib print matplotlib matplotlib version matplotlib | 0 |
156,089 | 19,809,459,601 | IssuesEvent | 2022-01-19 10:35:00 | benchmarkdebricked/angular | https://api.github.com/repos/benchmarkdebricked/angular | opened | CVE-2018-20834 (High) detected in tar-2.2.1.tgz | security vulnerability | ## CVE-2018-20834 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>tar-2.2.1.tgz</b></p></summary>
<p>tar for node</p>
<p>Library home page: <a href="https://registry.npmjs.org/tar/-/tar-2.2.1.tgz">https://registry.npmjs.org/tar/-/tar-2.2.1.tgz</a></p>
<p>
Dependency Hierarchy:
- compiler-cli-6.1.0.tgz (Root Library)
- chokidar-1.7.0.tgz
- fsevents-1.1.3.tgz
- node-pre-gyp-0.6.39.tgz
- :x: **tar-2.2.1.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/benchmarkdebricked/angular/commit/d5d066ec5f183ee78b6a36dc6eaa6714647bc518">d5d066ec5f183ee78b6a36dc6eaa6714647bc518</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>
A vulnerability was found in node-tar before version 4.4.2 (excluding version 2.2.2). An Arbitrary File Overwrite issue exists when extracting a tarball containing a hardlink to a file that already exists on the system, in conjunction with a later plain file with the same name as the hardlink. This plain file content replaces the existing file content. A patch has been applied to node-tar v2.2.2).
<p>Publish Date: 2019-04-30
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-20834>CVE-2018-20834</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: High
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-16082">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-16082</a></p>
<p>Release Date: 2019-04-30</p>
<p>Fix Resolution: 2.2.2,4.4.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-2018-20834 (High) detected in tar-2.2.1.tgz - ## CVE-2018-20834 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>tar-2.2.1.tgz</b></p></summary>
<p>tar for node</p>
<p>Library home page: <a href="https://registry.npmjs.org/tar/-/tar-2.2.1.tgz">https://registry.npmjs.org/tar/-/tar-2.2.1.tgz</a></p>
<p>
Dependency Hierarchy:
- compiler-cli-6.1.0.tgz (Root Library)
- chokidar-1.7.0.tgz
- fsevents-1.1.3.tgz
- node-pre-gyp-0.6.39.tgz
- :x: **tar-2.2.1.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/benchmarkdebricked/angular/commit/d5d066ec5f183ee78b6a36dc6eaa6714647bc518">d5d066ec5f183ee78b6a36dc6eaa6714647bc518</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>
A vulnerability was found in node-tar before version 4.4.2 (excluding version 2.2.2). An Arbitrary File Overwrite issue exists when extracting a tarball containing a hardlink to a file that already exists on the system, in conjunction with a later plain file with the same name as the hardlink. This plain file content replaces the existing file content. A patch has been applied to node-tar v2.2.2).
<p>Publish Date: 2019-04-30
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-20834>CVE-2018-20834</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: High
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-16082">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-16082</a></p>
<p>Release Date: 2019-04-30</p>
<p>Fix Resolution: 2.2.2,4.4.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 high detected in tar tgz cve high severity vulnerability vulnerable library tar tgz tar for node library home page a href dependency hierarchy compiler cli tgz root library chokidar tgz fsevents tgz node pre gyp tgz x tar tgz vulnerable library found in head commit a href vulnerability details a vulnerability was found in node tar before version excluding version an arbitrary file overwrite issue exists when extracting a tarball containing a hardlink to a file that already exists on the system in conjunction with a later plain file with the same name as the hardlink this plain file content replaces the existing file content a patch has been applied to node tar publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact none integrity impact high availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution step up your open source security game with whitesource | 0 |
65,927 | 12,697,398,558 | IssuesEvent | 2020-06-22 11:45:37 | Abbassihraf/P-curiosity-LAB | https://api.github.com/repos/Abbassihraf/P-curiosity-LAB | opened | Learning center | Code | - All versions
- [ ] include nav
- [ ] latest projects webinars and posts
- [ ] new Blog posts
- [ ] popular blog posts
- [ ] events
- [ ] get started
- [ ] include footer | 1.0 | Learning center - - All versions
- [ ] include nav
- [ ] latest projects webinars and posts
- [ ] new Blog posts
- [ ] popular blog posts
- [ ] events
- [ ] get started
- [ ] include footer | non_priority | learning center all versions include nav latest projects webinars and posts new blog posts popular blog posts events get started include footer | 0 |
127,367 | 17,263,574,501 | IssuesEvent | 2021-07-22 10:58:27 | gitpod-io/gitpod | https://api.github.com/repos/gitpod-io/gitpod | closed | [Dashboard] Project Configuration | component: dashboard needs visual design 💄 roadmap item: teams & projects 🧑🚀 crew: teams and projects | Part of the [onboarding flow](https://www.notion.so/gitpod/Onboarding-Flow-bc21ce30f91c42b88bbce42ab58d17c2) (internal) after importing a git repository as a project is to guide users through the configuration steps in order to get them into a prebuilt ready-to-code dev environment.
This includes a) configuring `.gitpod.yml` and `.gitpod.Dockerfile` for the project, b) triggering a prebuild, and c) allowing users to open a workspace afterwards. | 1.0 | [Dashboard] Project Configuration - Part of the [onboarding flow](https://www.notion.so/gitpod/Onboarding-Flow-bc21ce30f91c42b88bbce42ab58d17c2) (internal) after importing a git repository as a project is to guide users through the configuration steps in order to get them into a prebuilt ready-to-code dev environment.
This includes a) configuring `.gitpod.yml` and `.gitpod.Dockerfile` for the project, b) triggering a prebuild, and c) allowing users to open a workspace afterwards. | non_priority | project configuration part of the internal after importing a git repository as a project is to guide users through the configuration steps in order to get them into a prebuilt ready to code dev environment this includes a configuring gitpod yml and gitpod dockerfile for the project b triggering a prebuild and c allowing users to open a workspace afterwards | 0 |
490 | 7,022,469,429 | IssuesEvent | 2017-12-22 10:42:58 | zcash/zcash | https://api.github.com/repos/zcash/zcash | opened | Improve serialization of MerklePath | portability protocol fragility | `MerklePath` contains vectors of `bool`. Currently, these are [directly serialized](https://github.com/zcash/zcash/blob/master/src/zcash/IncrementalMerkleTree.hpp#L15), which causes the `bool`s to be converted to `char`s [](https://github.com/zcash/zcash/blob/master/src/serialize.h#L230). This is an ambiguous serialization ([which prevents the MacOS CI builder from building](https://ci.z.cash/#/builders/16/builds/91/steps/3/logs/stdio)), but is also very inefficient. A more efficient format would be to use bit arrays ([see e.g. `CPartialMerkleTree` uses](https://github.com/zcash/zcash/blob/master/src/merkleblock.h#L91-L104)).
One question I haven't yet determined the answer to is, where is `MerklePath` actually serialized? If it is being used, then migration will be trickier. If it isn't being used, then do we even need any code here? I don't currently recall whether #2120 (which *does* serialize related structures) might start using it. | True | Improve serialization of MerklePath - `MerklePath` contains vectors of `bool`. Currently, these are [directly serialized](https://github.com/zcash/zcash/blob/master/src/zcash/IncrementalMerkleTree.hpp#L15), which causes the `bool`s to be converted to `char`s [](https://github.com/zcash/zcash/blob/master/src/serialize.h#L230). This is an ambiguous serialization ([which prevents the MacOS CI builder from building](https://ci.z.cash/#/builders/16/builds/91/steps/3/logs/stdio)), but is also very inefficient. A more efficient format would be to use bit arrays ([see e.g. `CPartialMerkleTree` uses](https://github.com/zcash/zcash/blob/master/src/merkleblock.h#L91-L104)).
One question I haven't yet determined the answer to is, where is `MerklePath` actually serialized? If it is being used, then migration will be trickier. If it isn't being used, then do we even need any code here? I don't currently recall whether #2120 (which *does* serialize related structures) might start using it. | non_priority | improve serialization of merklepath merklepath contains vectors of bool currently these are which causes the bool s to be converted to char s this is an ambiguous serialization but is also very inefficient a more efficient format would be to use bit arrays one question i haven t yet determined the answer to is where is merklepath actually serialized if it is being used then migration will be trickier if it isn t being used then do we even need any code here i don t currently recall whether which does serialize related structures might start using it | 0 |
199,415 | 22,693,327,655 | IssuesEvent | 2022-07-05 01:13:40 | Kijacode/dotfiles | https://api.github.com/repos/Kijacode/dotfiles | opened | CVE-2022-23302 (High) detected in org.apache.log4j_1.2.15.v201012070815.jar | security vulnerability | ## CVE-2022-23302 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>org.apache.log4j_1.2.15.v201012070815.jar</b></p></summary>
<p></p>
<p>Library home page: <a href="http://eclipse.mirror.garr.it/mirrors/eclipse/webtools/downloads/drops/R3.16.0/S-3.16.0.M3-20191121172023/wtp-repo-S-3.16.0.M3-20191121172023.zip">http://eclipse.mirror.garr.it/mirrors/eclipse/webtools/downloads/drops/R3.16.0/S-3.16.0.M3-20191121172023/wtp-repo-S-3.16.0.M3-20191121172023.zip</a></p>
<p>Path to vulnerable library: /.vscode/extensions/redhat.java-0.80.0/server/plugins/org.apache.log4j_1.2.15.v201012070815.jar</p>
<p>
Dependency Hierarchy:
- :x: **org.apache.log4j_1.2.15.v201012070815.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/Kijacode/dotfiles/commit/a1134e0d69c95f5b6b6bbfb161bbf263699292f0">a1134e0d69c95f5b6b6bbfb161bbf263699292f0</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
JMSSink in all versions of Log4j 1.x is vulnerable to deserialization of untrusted data when the attacker has write access to the Log4j configuration or if the configuration references an LDAP service the attacker has access to. The attacker can provide a TopicConnectionFactoryBindingName configuration causing JMSSink to perform JNDI requests that result in remote code execution in a similar fashion to CVE-2021-4104. Note this issue only affects Log4j 1.x when specifically configured to use JMSSink, which is not the default. Apache Log4j 1.2 reached end of life in August 2015. Users should upgrade to Log4j 2 as it addresses numerous other issues from the previous versions.
<p>Publish Date: 2022-01-18
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-23302>CVE-2022-23302</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>8.8</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://reload4j.qos.ch/">https://reload4j.qos.ch/</a></p>
<p>Release Date: 2022-01-18</p>
<p>Fix Resolution: ch.qos.reload4j:reload4j:1.2.18.1</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | CVE-2022-23302 (High) detected in org.apache.log4j_1.2.15.v201012070815.jar - ## CVE-2022-23302 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>org.apache.log4j_1.2.15.v201012070815.jar</b></p></summary>
<p></p>
<p>Library home page: <a href="http://eclipse.mirror.garr.it/mirrors/eclipse/webtools/downloads/drops/R3.16.0/S-3.16.0.M3-20191121172023/wtp-repo-S-3.16.0.M3-20191121172023.zip">http://eclipse.mirror.garr.it/mirrors/eclipse/webtools/downloads/drops/R3.16.0/S-3.16.0.M3-20191121172023/wtp-repo-S-3.16.0.M3-20191121172023.zip</a></p>
<p>Path to vulnerable library: /.vscode/extensions/redhat.java-0.80.0/server/plugins/org.apache.log4j_1.2.15.v201012070815.jar</p>
<p>
Dependency Hierarchy:
- :x: **org.apache.log4j_1.2.15.v201012070815.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/Kijacode/dotfiles/commit/a1134e0d69c95f5b6b6bbfb161bbf263699292f0">a1134e0d69c95f5b6b6bbfb161bbf263699292f0</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
JMSSink in all versions of Log4j 1.x is vulnerable to deserialization of untrusted data when the attacker has write access to the Log4j configuration or if the configuration references an LDAP service the attacker has access to. The attacker can provide a TopicConnectionFactoryBindingName configuration causing JMSSink to perform JNDI requests that result in remote code execution in a similar fashion to CVE-2021-4104. Note this issue only affects Log4j 1.x when specifically configured to use JMSSink, which is not the default. Apache Log4j 1.2 reached end of life in August 2015. Users should upgrade to Log4j 2 as it addresses numerous other issues from the previous versions.
<p>Publish Date: 2022-01-18
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-23302>CVE-2022-23302</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>8.8</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://reload4j.qos.ch/">https://reload4j.qos.ch/</a></p>
<p>Release Date: 2022-01-18</p>
<p>Fix Resolution: ch.qos.reload4j:reload4j:1.2.18.1</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_priority | cve high detected in org apache jar cve high severity vulnerability vulnerable library org apache jar library home page a href path to vulnerable library vscode extensions redhat java server plugins org apache jar dependency hierarchy x org apache jar vulnerable library found in head commit a href found in base branch main vulnerability details jmssink in all versions of x is vulnerable to deserialization of untrusted data when the attacker has write access to the configuration or if the configuration references an ldap service the attacker has access to the attacker can provide a topicconnectionfactorybindingname configuration causing jmssink to perform jndi requests that result in remote code execution in a similar fashion to cve note this issue only affects x when specifically configured to use jmssink which is not the default apache reached end of life in august users should upgrade to as it addresses numerous other issues from the previous versions publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required low user interaction none scope unchanged impact metrics confidentiality impact high integrity impact high availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution ch qos step up your open source security game with mend | 0 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.