Datasets:

karths

/

binary-10IQR-medium-priority

like 0

IssuesEvent

2023-03-17 03:18:08

Nadira3/alx-low_level_programming

https://api.github.com/repos/Nadira3/alx-low_level_programming

opened

0x0Bmalloc tasks

bug documentation

The tasks assigned mostly are incomplete, implementation of the malloc function cannot be carried out until the concept is properly understood

1.0

0x0Bmalloc tasks - The tasks assigned mostly are incomplete, implementation of the malloc function cannot be carried out until the concept is properly understood

non_priority

tasks the tasks assigned mostly are incomplete implementation of the malloc function cannot be carried out until the concept is properly understood

IssuesEvent

2023-04-18 22:06:15

IntellectualSites/PlotSquared

https://api.github.com/repos/IntellectualSites/PlotSquared

opened

DEV BUILD 7.0 error creating world

Requires Testing

### Server Implementation Paper ### Server Version 1.19.3 ### Describe the bug [00:02:03 ERROR]: [Multiverse-Core] The world 'CityBuild' could NOT be loaded because it contains errors and is probably corrupt! [00:02:03 ERROR]: [Multiverse-Core] Try using Minecraft Region Fixer to repair your world! 'CityBuild' [00:02:03 ERROR]: [Multiverse-Core] https://github.com/Fenixin/Minecraft-Region-Fixer [00:02:03 ERROR]: [Multiverse-Core] Failed to Create/Load the world 'CityBuild' [00:02:03 INFO]: CONSOLE: FAILED. ### To Reproduce plot setup (finish all and set name then error) ### Expected behaviour [00:02:03 ERROR]: [Multiverse-Core] The world 'CityBuild' could NOT be loaded because it contains errors and is probably corrupt! [00:02:03 ERROR]: [Multiverse-Core] Try using Minecraft Region Fixer to repair your world! 'CityBuild' [00:02:03 ERROR]: [Multiverse-Core] https://github.com/Fenixin/Minecraft-Region-Fixer [00:02:03 ERROR]: [Multiverse-Core] Failed to Create/Load the world 'CityBuild' [00:02:03 INFO]: CONSOLE: FAILED. ### Screenshots / Videos _No response_ ### Error log (if applicable) _No response_ ### Plot Debugpaste https://athion.net/ISPaster/paste/view/48fdb008bd06469e95f1421bc7ca585c ### PlotSquared Version 7.0 DEV BUILD (git repo download and build) ### Checklist - [X] I have included a Plot debugpaste. - [X] I am using the newest build from https://www.spigotmc.org/resources/77506/ and the issue still persists. ### Anything else? _No response_

1.0

DEV BUILD 7.0 error creating world - ### Server Implementation Paper ### Server Version 1.19.3 ### Describe the bug [00:02:03 ERROR]: [Multiverse-Core] The world 'CityBuild' could NOT be loaded because it contains errors and is probably corrupt! [00:02:03 ERROR]: [Multiverse-Core] Try using Minecraft Region Fixer to repair your world! 'CityBuild' [00:02:03 ERROR]: [Multiverse-Core] https://github.com/Fenixin/Minecraft-Region-Fixer [00:02:03 ERROR]: [Multiverse-Core] Failed to Create/Load the world 'CityBuild' [00:02:03 INFO]: CONSOLE: FAILED. ### To Reproduce plot setup (finish all and set name then error) ### Expected behaviour [00:02:03 ERROR]: [Multiverse-Core] The world 'CityBuild' could NOT be loaded because it contains errors and is probably corrupt! [00:02:03 ERROR]: [Multiverse-Core] Try using Minecraft Region Fixer to repair your world! 'CityBuild' [00:02:03 ERROR]: [Multiverse-Core] https://github.com/Fenixin/Minecraft-Region-Fixer [00:02:03 ERROR]: [Multiverse-Core] Failed to Create/Load the world 'CityBuild' [00:02:03 INFO]: CONSOLE: FAILED. ### Screenshots / Videos _No response_ ### Error log (if applicable) _No response_ ### Plot Debugpaste https://athion.net/ISPaster/paste/view/48fdb008bd06469e95f1421bc7ca585c ### PlotSquared Version 7.0 DEV BUILD (git repo download and build) ### Checklist - [X] I have included a Plot debugpaste. - [X] I am using the newest build from https://www.spigotmc.org/resources/77506/ and the issue still persists. ### Anything else? _No response_

non_priority

dev build error creating world server implementation paper server version describe the bug the world citybuild could not be loaded because it contains errors and is probably corrupt try using minecraft region fixer to repair your world citybuild failed to create load the world citybuild console failed to reproduce plot setup finish all and set name then error expected behaviour the world citybuild could not be loaded because it contains errors and is probably corrupt try using minecraft region fixer to repair your world citybuild failed to create load the world citybuild console failed screenshots videos no response error log if applicable no response plot debugpaste plotsquared version dev build git repo download and build checklist i have included a plot debugpaste i am using the newest build from and the issue still persists anything else no response

IssuesEvent

2022-01-13 20:48:08

vmware-samples/vcenter-event-broker-appliance

https://api.github.com/repos/vmware-samples/vcenter-event-broker-appliance

opened

[DOC] - Windows instructions for website contributions via Jekyll

documentation

1) There are no Windows instructions for Jekyll at https://vmweventbroker.io/kb/contribute-site , though there are Windows instructions in /docs/README.md. The README instructions need to be included on the webpage 2) Windows can throw warnings saying `Auto-regeneration may not work on some Windows versions`, which forces you to restart the container on every change. This makes website contributions time consuming. Workaround is the --force-polling argument to jekyll serve. Update the webpage and README accordingly.

1.0

[DOC] - Windows instructions for website contributions via Jekyll - 1) There are no Windows instructions for Jekyll at https://vmweventbroker.io/kb/contribute-site , though there are Windows instructions in /docs/README.md. The README instructions need to be included on the webpage 2) Windows can throw warnings saying `Auto-regeneration may not work on some Windows versions`, which forces you to restart the container on every change. This makes website contributions time consuming. Workaround is the --force-polling argument to jekyll serve. Update the webpage and README accordingly.

non_priority

windows instructions for website contributions via jekyll there are no windows instructions for jekyll at though there are windows instructions in docs readme md the readme instructions need to be included on the webpage windows can throw warnings saying auto regeneration may not work on some windows versions which forces you to restart the container on every change this makes website contributions time consuming workaround is the force polling argument to jekyll serve update the webpage and readme accordingly

IssuesEvent

2018-05-29 21:45:52

dotnet/coreclr

https://api.github.com/repos/dotnet/coreclr

closed

[JitStress] Crossgen JIT/Regression/JitBlue/GitHub_18056/Bool_And_Op_cs_do Jit Assert

arch-arm32 area-CodeGen bug os-linux

Hit this during crossgen in [ Ubuntu arm Cross Checked r2r_jitstress1 Build and Test](https://ci.dot.net/job/dotnet_coreclr/job/master/job/jitstress/job/arm_cross_checked_ubuntu_r2r_jitstress1_tst_prtest/6/consoleText) when testing #18053 ``` FAILED - JIT/Regression/JitBlue/GitHub_18056/Bool_And_Op_cs_do/Bool_And_Op_cs_do.sh BEGIN EXECUTION in takeLock /ssd/j/workspace/dotnet_coreclr/master/jitstress/arm_cross_checked_ubuntu_r2r_jitstress1_tst_prtest/bin/tests/Linux.arm.Checked/Tests/Core_Root/crossgen /Platform_Assemblies_Paths /ssd/j/workspace/dotnet_coreclr/master/jitstress/arm_cross_checked_ubuntu_r2r_jitstress1_tst_prtest/bin/tests/Linux.arm.Checked/Tests/Core_Root:/ssd/j/workspace/dotnet_coreclr/master/jitstress/arm_cross_checked_ubuntu_r2r_jitstress1_tst_prtest/bin/tests/Linux.arm.Checked/JIT/Regression/JitBlue/GitHub_18056/Bool_And_Op_cs_do/IL:/ssd/j/workspace/dotnet_coreclr/master/jitstress/arm_cross_checked_ubuntu_r2r_jitstress1_tst_prtest/bin/tests/Linux.arm.Checked/JIT/Regression/JitBlue/GitHub_18056/Bool_And_Op_cs_do /in Bool_And_Op_cs_do.org /out Bool_And_Op_cs_do.exe Assert failure(PID 28502 [0x00006f56], Thread: 28502 [0x6f56]): Assertion failed 'blockPred->bbTraversalStamp == curTraversalStamp' in 'testout1:Sub_Funclet_411():int' (IL size 826) File: /mnt/j/workspace/dotnet_coreclr/master/arm_cross_checked_ubuntu_prtest/src/jit/flowgraph.cpp Line: 20738 Image: /ssd/j/workspace/dotnet_coreclr/master/jitstress/arm_cross_checked_ubuntu_r2r_jitstress1_tst_prtest/bin/tests/Linux.arm.Checked/Tests/Core_Root/crossgen Microsoft (R) CoreCLR Native Image Generator - Version 4.5.30319.0 Copyright (c) Microsoft Corporation. All rights reserved. ./Bool_And_Op_cs_do.sh: line 156: 28502 Aborted $_DebuggerFullPath "$CORE_ROOT/crossgen" /Platform_Assemblies_Paths $CORE_ROOT:$PWD/IL:$PWD /in Bool_And_Op_cs_do.org /out Bool_And_Op_cs_do.exe Crossgen failed with exitcode: 134 in ReleaseLock ```

1.0

[JitStress] Crossgen JIT/Regression/JitBlue/GitHub_18056/Bool_And_Op_cs_do Jit Assert - Hit this during crossgen in [ Ubuntu arm Cross Checked r2r_jitstress1 Build and Test](https://ci.dot.net/job/dotnet_coreclr/job/master/job/jitstress/job/arm_cross_checked_ubuntu_r2r_jitstress1_tst_prtest/6/consoleText) when testing #18053 ``` FAILED - JIT/Regression/JitBlue/GitHub_18056/Bool_And_Op_cs_do/Bool_And_Op_cs_do.sh BEGIN EXECUTION in takeLock /ssd/j/workspace/dotnet_coreclr/master/jitstress/arm_cross_checked_ubuntu_r2r_jitstress1_tst_prtest/bin/tests/Linux.arm.Checked/Tests/Core_Root/crossgen /Platform_Assemblies_Paths /ssd/j/workspace/dotnet_coreclr/master/jitstress/arm_cross_checked_ubuntu_r2r_jitstress1_tst_prtest/bin/tests/Linux.arm.Checked/Tests/Core_Root:/ssd/j/workspace/dotnet_coreclr/master/jitstress/arm_cross_checked_ubuntu_r2r_jitstress1_tst_prtest/bin/tests/Linux.arm.Checked/JIT/Regression/JitBlue/GitHub_18056/Bool_And_Op_cs_do/IL:/ssd/j/workspace/dotnet_coreclr/master/jitstress/arm_cross_checked_ubuntu_r2r_jitstress1_tst_prtest/bin/tests/Linux.arm.Checked/JIT/Regression/JitBlue/GitHub_18056/Bool_And_Op_cs_do /in Bool_And_Op_cs_do.org /out Bool_And_Op_cs_do.exe Assert failure(PID 28502 [0x00006f56], Thread: 28502 [0x6f56]): Assertion failed 'blockPred->bbTraversalStamp == curTraversalStamp' in 'testout1:Sub_Funclet_411():int' (IL size 826) File: /mnt/j/workspace/dotnet_coreclr/master/arm_cross_checked_ubuntu_prtest/src/jit/flowgraph.cpp Line: 20738 Image: /ssd/j/workspace/dotnet_coreclr/master/jitstress/arm_cross_checked_ubuntu_r2r_jitstress1_tst_prtest/bin/tests/Linux.arm.Checked/Tests/Core_Root/crossgen Microsoft (R) CoreCLR Native Image Generator - Version 4.5.30319.0 Copyright (c) Microsoft Corporation. All rights reserved. ./Bool_And_Op_cs_do.sh: line 156: 28502 Aborted $_DebuggerFullPath "$CORE_ROOT/crossgen" /Platform_Assemblies_Paths $CORE_ROOT:$PWD/IL:$PWD /in Bool_And_Op_cs_do.org /out Bool_And_Op_cs_do.exe Crossgen failed with exitcode: 134 in ReleaseLock ```

non_priority

crossgen jit regression jitblue github bool and op cs do jit assert hit this during crossgen in ubuntu arm cross checked build and test when testing failed jit regression jitblue github bool and op cs do bool and op cs do sh begin execution in takelock ssd j workspace dotnet coreclr master jitstress arm cross checked ubuntu tst prtest bin tests linux arm checked tests core root crossgen platform assemblies paths ssd j workspace dotnet coreclr master jitstress arm cross checked ubuntu tst prtest bin tests linux arm checked tests core root ssd j workspace dotnet coreclr master jitstress arm cross checked ubuntu tst prtest bin tests linux arm checked jit regression jitblue github bool and op cs do il ssd j workspace dotnet coreclr master jitstress arm cross checked ubuntu tst prtest bin tests linux arm checked jit regression jitblue github bool and op cs do in bool and op cs do org out bool and op cs do exe assert failure pid thread assertion failed blockpred bbtraversalstamp curtraversalstamp in sub funclet int il size file mnt j workspace dotnet coreclr master arm cross checked ubuntu prtest src jit flowgraph cpp line image ssd j workspace dotnet coreclr master jitstress arm cross checked ubuntu tst prtest bin tests linux arm checked tests core root crossgen microsoft r coreclr native image generator version copyright c microsoft corporation all rights reserved bool and op cs do sh line aborted debuggerfullpath core root crossgen platform assemblies paths core root pwd il pwd in bool and op cs do org out bool and op cs do exe crossgen failed with exitcode in releaselock

IssuesEvent

2023-03-28 06:46:07

Sultan-QA/pipenv-with-vul

https://api.github.com/repos/Sultan-QA/pipenv-with-vul

opened

djangorestframework-3.11.1-py3-none-any.whl: 1 vulnerabilities (highest severity is: 6.1)

Mend: dependency security vulnerability

<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>djangorestframework-3.11.1-py3-none-any.whl</b></p></summary> <p>Web APIs for Django, made easy.</p> <p>Library home page: <a href="https://files.pythonhosted.org/packages/a2/cc/a8738854bda156f8145b9185488c1dae79ce17df5b563c42ee7dd0c6245a/djangorestframework-3.11.1-py3-none-any.whl">https://files.pythonhosted.org/packages/a2/cc/a8738854bda156f8145b9185488c1dae79ce17df5b563c42ee7dd0c6245a/djangorestframework-3.11.1-py3-none-any.whl</a></p> <p>Path to dependency file: /Pipfile</p> <p>Path to vulnerable library: /Pipfile</p> <p> <p>Found in HEAD commit: <a href="https://github.com/Sultan-QA/pipenv-with-vul/commit/9dfc1e0149edd66370c87f3b46ecdc0958d39cc4">9dfc1e0149edd66370c87f3b46ecdc0958d39cc4</a></p></details> ## Vulnerabilities | CVE | Severity | <img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS | Dependency | Type | Fixed in (djangorestframework version) | Remediation Available | | ------------- | ------------- | ----- | ----- | ----- | ------------- | --- | | [CVE-2020-25626](https://www.mend.io/vulnerability-database/CVE-2020-25626) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 6.1 | djangorestframework-3.11.1-py3-none-any.whl | Direct | 3.11.2 | &#9989; | ## Details <details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2020-25626</summary> ### Vulnerable Library - <b>djangorestframework-3.11.1-py3-none-any.whl</b></p> <p>Web APIs for Django, made easy.</p> <p>Library home page: <a href="https://files.pythonhosted.org/packages/a2/cc/a8738854bda156f8145b9185488c1dae79ce17df5b563c42ee7dd0c6245a/djangorestframework-3.11.1-py3-none-any.whl">https://files.pythonhosted.org/packages/a2/cc/a8738854bda156f8145b9185488c1dae79ce17df5b563c42ee7dd0c6245a/djangorestframework-3.11.1-py3-none-any.whl</a></p> <p>Path to dependency file: /Pipfile</p> <p>Path to vulnerable library: /Pipfile</p> <p> Dependency Hierarchy: - :x: **djangorestframework-3.11.1-py3-none-any.whl** (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/Sultan-QA/pipenv-with-vul/commit/9dfc1e0149edd66370c87f3b46ecdc0958d39cc4">9dfc1e0149edd66370c87f3b46ecdc0958d39cc4</a></p> <p>Found in base branch: <b>main</b></p> </p> <p></p> ### Vulnerability Details <p> A flaw was found in Django REST Framework versions before 3.12.0 and before 3.11.2. When using the browseable API viewer, Django REST Framework fails to properly escape certain strings that can come from user input. This allows a user who can control those strings to inject malicious <script> tags, leading to a cross-site-scripting (XSS) vulnerability. <p>Publish Date: 2020-09-30 <p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2020-25626>CVE-2020-25626</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>6.1</b>) <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: Required - Scope: Changed - Impact Metrics: - Confidentiality Impact: Low - Integrity Impact: Low - Availability Impact: None </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> <p></p> ### Suggested Fix <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://pypi.org/project/djangorestframework/3.12.1/">https://pypi.org/project/djangorestframework/3.12.1/</a></p> <p>Release Date: 2020-09-30</p> <p>Fix Resolution: 3.11.2</p> </p> <p></p> :rescue_worker_helmet: Automatic Remediation is available for this issue </details> *** <p>:rescue_worker_helmet: Automatic Remediation is available for this issue.</p>

True

djangorestframework-3.11.1-py3-none-any.whl: 1 vulnerabilities (highest severity is: 6.1) - <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>djangorestframework-3.11.1-py3-none-any.whl</b></p></summary> <p>Web APIs for Django, made easy.</p> <p>Library home page: <a href="https://files.pythonhosted.org/packages/a2/cc/a8738854bda156f8145b9185488c1dae79ce17df5b563c42ee7dd0c6245a/djangorestframework-3.11.1-py3-none-any.whl">https://files.pythonhosted.org/packages/a2/cc/a8738854bda156f8145b9185488c1dae79ce17df5b563c42ee7dd0c6245a/djangorestframework-3.11.1-py3-none-any.whl</a></p> <p>Path to dependency file: /Pipfile</p> <p>Path to vulnerable library: /Pipfile</p> <p> <p>Found in HEAD commit: <a href="https://github.com/Sultan-QA/pipenv-with-vul/commit/9dfc1e0149edd66370c87f3b46ecdc0958d39cc4">9dfc1e0149edd66370c87f3b46ecdc0958d39cc4</a></p></details> ## Vulnerabilities | CVE | Severity | <img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS | Dependency | Type | Fixed in (djangorestframework version) | Remediation Available | | ------------- | ------------- | ----- | ----- | ----- | ------------- | --- | | [CVE-2020-25626](https://www.mend.io/vulnerability-database/CVE-2020-25626) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 6.1 | djangorestframework-3.11.1-py3-none-any.whl | Direct | 3.11.2 | &#9989; | ## Details <details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2020-25626</summary> ### Vulnerable Library - <b>djangorestframework-3.11.1-py3-none-any.whl</b></p> <p>Web APIs for Django, made easy.</p> <p>Library home page: <a href="https://files.pythonhosted.org/packages/a2/cc/a8738854bda156f8145b9185488c1dae79ce17df5b563c42ee7dd0c6245a/djangorestframework-3.11.1-py3-none-any.whl">https://files.pythonhosted.org/packages/a2/cc/a8738854bda156f8145b9185488c1dae79ce17df5b563c42ee7dd0c6245a/djangorestframework-3.11.1-py3-none-any.whl</a></p> <p>Path to dependency file: /Pipfile</p> <p>Path to vulnerable library: /Pipfile</p> <p> Dependency Hierarchy: - :x: **djangorestframework-3.11.1-py3-none-any.whl** (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/Sultan-QA/pipenv-with-vul/commit/9dfc1e0149edd66370c87f3b46ecdc0958d39cc4">9dfc1e0149edd66370c87f3b46ecdc0958d39cc4</a></p> <p>Found in base branch: <b>main</b></p> </p> <p></p> ### Vulnerability Details <p> A flaw was found in Django REST Framework versions before 3.12.0 and before 3.11.2. When using the browseable API viewer, Django REST Framework fails to properly escape certain strings that can come from user input. This allows a user who can control those strings to inject malicious <script> tags, leading to a cross-site-scripting (XSS) vulnerability. <p>Publish Date: 2020-09-30 <p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2020-25626>CVE-2020-25626</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>6.1</b>) <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: Required - Scope: Changed - Impact Metrics: - Confidentiality Impact: Low - Integrity Impact: Low - Availability Impact: None </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> <p></p> ### Suggested Fix <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://pypi.org/project/djangorestframework/3.12.1/">https://pypi.org/project/djangorestframework/3.12.1/</a></p> <p>Release Date: 2020-09-30</p> <p>Fix Resolution: 3.11.2</p> </p> <p></p> :rescue_worker_helmet: Automatic Remediation is available for this issue </details> *** <p>:rescue_worker_helmet: Automatic Remediation is available for this issue.</p>

non_priority

djangorestframework none any whl vulnerabilities highest severity is vulnerable library djangorestframework none any whl web apis for django made easy library home page a href path to dependency file pipfile path to vulnerable library pipfile found in head commit a href vulnerabilities cve severity cvss dependency type fixed in djangorestframework version remediation available medium djangorestframework none any whl direct details cve vulnerable library djangorestframework none any whl web apis for django made easy library home page a href path to dependency file pipfile path to vulnerable library pipfile dependency hierarchy x djangorestframework none any whl vulnerable library found in head commit a href found in base branch main vulnerability details a flaw was found in django rest framework versions before and before when using the browseable api viewer django rest framework fails to properly escape certain strings that can come from user input this allows a user who can control those strings to inject malicious tags leading to a cross site scripting xss vulnerability publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction required scope changed impact metrics confidentiality impact low integrity impact low availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution rescue worker helmet automatic remediation is available for this issue rescue worker helmet automatic remediation is available for this issue

IssuesEvent

2021-10-04 11:31:23

artsking/linux-3.0.35

https://api.github.com/repos/artsking/linux-3.0.35

opened

CVE-2014-0155 (Medium) detected in linux-stable-rtv3.8.6

security vulnerability

## CVE-2014-0155 - Medium Severity Vulnerability <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>linux-stable-rtv3.8.6</b></p></summary> <p> <p>Julia Cartwright's fork of linux-stable-rt.git</p> <p>Library home page: <a href=https://git.kernel.org/pub/scm/linux/kernel/git/julia/linux-stable-rt.git>https://git.kernel.org/pub/scm/linux/kernel/git/julia/linux-stable-rt.git</a></p> <p>Found in HEAD commit: <a href="https://github.com/artsking/linux-3.0.35/commit/5992fa81c6ac1b4e9db13f5408d914525c5b7875">5992fa81c6ac1b4e9db13f5408d914525c5b7875</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/medium_vul.png' width=19 height=20> Vulnerability Details</summary> <p> The ioapic_deliver function in virt/kvm/ioapic.c in the Linux kernel through 3.14.1 does not properly validate the kvm_irq_delivery_to_apic return value, which allows guest OS users to cause a denial of service (host OS crash) via a crafted entry in the redirection table of an I/O APIC. NOTE: the affected code was moved to the ioapic_service function before the vulnerability was announced. <p>Publish Date: 2014-04-14 <p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2014-0155>CVE-2014-0155</a></p> </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 2 Score Details (<b>5.5</b>)</summary> <p> Base Score Metrics not available</p> </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary> <p> <p>Type: Upgrade version</p> <p>Origin: <a href="http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2014-0155">http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2014-0155</a></p> <p>Release Date: 2014-04-14</p> <p>Fix Resolution: v3.15-rc2</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-2014-0155 (Medium) detected in linux-stable-rtv3.8.6 - ## CVE-2014-0155 - Medium Severity Vulnerability <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>linux-stable-rtv3.8.6</b></p></summary> <p> <p>Julia Cartwright's fork of linux-stable-rt.git</p> <p>Library home page: <a href=https://git.kernel.org/pub/scm/linux/kernel/git/julia/linux-stable-rt.git>https://git.kernel.org/pub/scm/linux/kernel/git/julia/linux-stable-rt.git</a></p> <p>Found in HEAD commit: <a href="https://github.com/artsking/linux-3.0.35/commit/5992fa81c6ac1b4e9db13f5408d914525c5b7875">5992fa81c6ac1b4e9db13f5408d914525c5b7875</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/medium_vul.png' width=19 height=20> Vulnerability Details</summary> <p> The ioapic_deliver function in virt/kvm/ioapic.c in the Linux kernel through 3.14.1 does not properly validate the kvm_irq_delivery_to_apic return value, which allows guest OS users to cause a denial of service (host OS crash) via a crafted entry in the redirection table of an I/O APIC. NOTE: the affected code was moved to the ioapic_service function before the vulnerability was announced. <p>Publish Date: 2014-04-14 <p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2014-0155>CVE-2014-0155</a></p> </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 2 Score Details (<b>5.5</b>)</summary> <p> Base Score Metrics not available</p> </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary> <p> <p>Type: Upgrade version</p> <p>Origin: <a href="http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2014-0155">http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2014-0155</a></p> <p>Release Date: 2014-04-14</p> <p>Fix Resolution: v3.15-rc2</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 linux stable cve medium severity vulnerability vulnerable library linux stable julia cartwright s fork of linux stable rt git library home page a href found in head commit a href found in base branch master vulnerable source files vulnerability details the ioapic deliver function in virt kvm ioapic c in the linux kernel through does not properly validate the kvm irq delivery to apic return value which allows guest os users to cause a denial of service host os crash via a crafted entry in the redirection table of an i o apic note the affected code was moved to the ioapic service function before the vulnerability was announced publish date url a href cvss score details base score metrics not available suggested fix type upgrade version origin a href release date fix resolution step up your open source security game with whitesource

IssuesEvent

2020-03-01 03:38:43

mohanadarafe/GuideMe

https://api.github.com/repos/mohanadarafe/GuideMe

opened

Fix recurring warning when running tests.

bug enhancement testing

Jest issues the following warning when tests are done running: 😡 **Cannot log after tests are done. Did you forget to wait for something async in your test?** ### To reproduce bug 1. Run command: npm test 2. The mentioned warning should be thrown by Jest

1.0

Fix recurring warning when running tests. - Jest issues the following warning when tests are done running: 😡 **Cannot log after tests are done. Did you forget to wait for something async in your test?** ### To reproduce bug 1. Run command: npm test 2. The mentioned warning should be thrown by Jest

non_priority

fix recurring warning when running tests jest issues the following warning when tests are done running 😡 cannot log after tests are done did you forget to wait for something async in your test to reproduce bug run command npm test the mentioned warning should be thrown by jest

IssuesEvent

2020-07-13 17:21:11

dpaulson45/HealthChecker

https://api.github.com/repos/dpaulson45/HealthChecker

closed

Create an object for the HTML report

Next Major Build Required Next Major Release enhancement

Currently, when we are building the HTML report, we do it based off the XML file. However, that isn't ideal as we need to change two completely different areas of code to keep up with the changes. Need to come up with a way so when we are building the HealthChecker object and doing a review on it, we do the same for an HTML object so we can just loop through the data to build the HTML report rather quickly.

1.0

Create an object for the HTML report - Currently, when we are building the HTML report, we do it based off the XML file. However, that isn't ideal as we need to change two completely different areas of code to keep up with the changes. Need to come up with a way so when we are building the HealthChecker object and doing a review on it, we do the same for an HTML object so we can just loop through the data to build the HTML report rather quickly.

non_priority

create an object for the html report currently when we are building the html report we do it based off the xml file however that isn t ideal as we need to change two completely different areas of code to keep up with the changes need to come up with a way so when we are building the healthchecker object and doing a review on it we do the same for an html object so we can just loop through the data to build the html report rather quickly

IssuesEvent

2019-10-07 13:17:38

elikkatzgit/thrift

https://api.github.com/repos/elikkatzgit/thrift

closed

WS-2019-0027 (Medium) detected in marked-0.3.19.js

security vulnerability

## WS-2019-0027 - Medium Severity Vulnerability <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>marked-0.3.19.js</b></p></summary> <p>A markdown parser built for speed</p> <p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/marked/0.3.19/marked.js">https://cdnjs.cloudflare.com/ajax/libs/marked/0.3.19/marked.js</a></p> <p>Path to dependency file: /tmp/ws-scm/thrift/lib/js/node_modules/marked/www/demo.html</p> <p>Path to vulnerable library: /thrift/lib/js/node_modules/marked/www/../lib/marked.js,/thrift/node_modules/marked/www/../lib/marked.js,/thrift/lib/ts/node_modules/marked/www/../lib/marked.js</p> <p> Dependency Hierarchy: - :x: **marked-0.3.19.js** (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/elikkatzgit/thrift/commit/cccd89abca5d407c8ba41e0a4405406c0215e589">cccd89abca5d407c8ba41e0a4405406c0215e589</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> Versions 0.3.17 and earlier of marked has Four regexes were vulnerable to catastrophic backtracking. This leaves markdown servers open to a potential REDOS attack. <p>Publish Date: 2019-03-17 <p>URL: <a href=https://github.com/markedjs/marked/commit/b15e42b67cec9ded8505e9d68bb8741ad7a9590d>WS-2019-0027</a></p> </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 2 Score Details (<b>5.0</b>)</summary> <p> Base Score Metrics not available</p> </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary> <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://github.com/markedjs/marked/commit/b15e42b67cec9ded8505e9d68bb8741ad7a9590d">https://github.com/markedjs/marked/commit/b15e42b67cec9ded8505e9d68bb8741ad7a9590d</a></p> <p>Release Date: 2019-03-17</p> <p>Fix Resolution: 0.3.18</p> </p> </details> <p></p>

True

WS-2019-0027 (Medium) detected in marked-0.3.19.js - ## WS-2019-0027 - Medium Severity Vulnerability <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>marked-0.3.19.js</b></p></summary> <p>A markdown parser built for speed</p> <p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/marked/0.3.19/marked.js">https://cdnjs.cloudflare.com/ajax/libs/marked/0.3.19/marked.js</a></p> <p>Path to dependency file: /tmp/ws-scm/thrift/lib/js/node_modules/marked/www/demo.html</p> <p>Path to vulnerable library: /thrift/lib/js/node_modules/marked/www/../lib/marked.js,/thrift/node_modules/marked/www/../lib/marked.js,/thrift/lib/ts/node_modules/marked/www/../lib/marked.js</p> <p> Dependency Hierarchy: - :x: **marked-0.3.19.js** (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/elikkatzgit/thrift/commit/cccd89abca5d407c8ba41e0a4405406c0215e589">cccd89abca5d407c8ba41e0a4405406c0215e589</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> Versions 0.3.17 and earlier of marked has Four regexes were vulnerable to catastrophic backtracking. This leaves markdown servers open to a potential REDOS attack. <p>Publish Date: 2019-03-17 <p>URL: <a href=https://github.com/markedjs/marked/commit/b15e42b67cec9ded8505e9d68bb8741ad7a9590d>WS-2019-0027</a></p> </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 2 Score Details (<b>5.0</b>)</summary> <p> Base Score Metrics not available</p> </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary> <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://github.com/markedjs/marked/commit/b15e42b67cec9ded8505e9d68bb8741ad7a9590d">https://github.com/markedjs/marked/commit/b15e42b67cec9ded8505e9d68bb8741ad7a9590d</a></p> <p>Release Date: 2019-03-17</p> <p>Fix Resolution: 0.3.18</p> </p> </details> <p></p>

non_priority

ws medium detected in marked js ws medium severity vulnerability vulnerable library marked js a markdown parser built for speed library home page a href path to dependency file tmp ws scm thrift lib js node modules marked www demo html path to vulnerable library thrift lib js node modules marked www lib marked js thrift node modules marked www lib marked js thrift lib ts node modules marked www lib marked js dependency hierarchy x marked js vulnerable library found in head commit a href vulnerability details versions and earlier of marked has four regexes were vulnerable to catastrophic backtracking this leaves markdown servers open to a potential redos attack publish date url a href cvss score details base score metrics not available suggested fix type upgrade version origin a href release date fix resolution

IssuesEvent

2020-12-08 08:03:23

freqtrade/freqtrade

https://api.github.com/repos/freqtrade/freqtrade

closed

Hyperopt and Backtesting results differ despite exact parameters

Backtest Hyperopt Question

## Describe your environment * Operating system: Ubuntu 20.04.1 LTS * Python Version: Python 3.8.5 * CCXT version: 1.36.85 * Freqtrade Version: 2020.10 ## Your question Although I have carefully read through issue #2008 and #3557 concerning different Hyperopt and Backtesting results and understand the crucial concept of identical parameters as described in https://github.com/freqtrade/freqtrade/issues/3557#issuecomment-653687560, I have not once been able to reproduce at least comparable results. I am desperate because I do not see the mistake. I know that you do not have the time to solve individual strategy related issues, but helping me to find the reason for these massive incongruent results would maybe help future users stuck with the same problem. ### Strategy I work with a renamed version of the ReinforcedSmoothScalping Strategy on a 15m timeframe. ``` python # pragma pylint: disable=missing-docstring, invalid-name, pointless-string-statement from functools import reduce from typing import Any, Callable, Dict, List import talib.abstract as ta from pandas import DataFrame from skopt.space import Categorical, Dimension, Integer import freqtrade.vendor.qtpylib.indicators as qtpylib from freqtrade.optimize.hyperopt_interface import IHyperOpt class Rise(IHyperOpt): """ Default hyperopt provided by the Freqtrade bot. You can override it with your own Hyperopt """ @staticmethod def buy_strategy_generator(params: Dict[str, Any]) -> Callable: """ Define the buy strategy parameters to be used by Hyperopt. """ def populate_buy_trend(dataframe: DataFrame, metadata: dict) -> DataFrame: """ Buy strategy Hyperopt will build and use. """ conditions = [] # GUARDS AND TRENDS if 'mfi-enabled' in params and params['mfi-enabled']: conditions.append(dataframe['mfi'] < params['mfi-value']) if 'fastd-enabled' in params and params['fastd-enabled']: conditions.append(dataframe['fastd'] < params['fastd-value']) if 'adx-enabled' in params and params['adx-enabled']: conditions.append(dataframe['adx'] > params['adx-value']) # if 'rsi-enabled' in params and params['rsi-enabled']: # conditions.append(dataframe['rsi'] < params['rsi-value']) if 'fastk-enabled' in params and params['fastk-enabled']: conditions.append(dataframe['fastk'] < params['fastk-value']) # TRIGGERS # if 'trigger' in params: # if params['trigger'] == 'bb_lower': # conditions.append(dataframe['close'] < dataframe['bb_lowerband']) # if params['trigger'] == 'macd_cross_signal': # conditions.append(qtpylib.crossed_above( # dataframe['macd'], dataframe['macdsignal'] # )) # if params['trigger'] == 'sar_reversal': # conditions.append(qtpylib.crossed_above( # dataframe['close'], dataframe['sar'] # )) # Check that volume is not 0 conditions.append(dataframe['volume'] > 0) if conditions: dataframe.loc[ reduce(lambda x, y: x & y, conditions), 'buy'] = 1 return dataframe return populate_buy_trend @staticmethod def indicator_space() -> List[Dimension]: """ Define your Hyperopt space for searching buy strategy parameters. """ return [ Integer(10, 25, name='mfi-value'), Integer(15, 45, name='fastd-value'), Integer(15, 45, name='fastk-value'), Integer(20, 50, name='adx-value'), # Integer(20, 40, name='rsi-value'), Categorical([True, False], name='mfi-enabled'), Categorical([True, False], name='fastd-enabled'), Categorical([True, False], name='adx-enabled'), Categorical([True, False], name='fastk-enabled'), # Categorical([True, False], name='rsi-enabled'), # Categorical(['bb_lower', 'macd_cross_signal', 'sar_reversal'], name='trigger') ] @staticmethod def sell_strategy_generator(params: Dict[str, Any]) -> Callable: """ Define the sell strategy parameters to be used by Hyperopt. """ def populate_sell_trend(dataframe: DataFrame, metadata: dict) -> DataFrame: """ Sell strategy Hyperopt will build and use. """ conditions = [] # GUARDS AND TRENDS #if 'sell-mfi-enabled' in params and params['sell-mfi-enabled']: #conditions.append(dataframe['mfi'] > params['sell-mfi-value']) if 'sell-fastd-enabled' in params and params['sell-fastd-enabled']: conditions.append(dataframe['fastd'] > params['sell-fastd-value']) #if 'sell-adx-enabled' in params and params['sell-adx-enabled']: #conditions.append(dataframe['adx'] < params['sell-adx-value']) if 'sell-fastk-enabled' in params and params['sell-fastk-enabled']: conditions.append(dataframe['fastk'] > params['sell-fastk-value']) if 'sell-cci-enabled' in params and params['sell-cci-enabled']: conditions.append(dataframe['cci'] > params['sell-cci-value']) # TRIGGERS # if 'sell-trigger' in params: # if params['sell-trigger'] == 'sell-bb_upper': # conditions.append(dataframe['close'] > dataframe['bb_upperband']) # if params['sell-trigger'] == 'sell-macd_cross_signal': # conditions.append(qtpylib.crossed_above( # dataframe['macdsignal'], dataframe['macd'] # )) # if params['sell-trigger'] == 'sell-sar_reversal': # conditions.append(qtpylib.crossed_above( # dataframe['sar'], dataframe['close'] # )) # Check that volume is not 0 conditions.append(dataframe['volume'] > 0) if conditions: dataframe.loc[ reduce(lambda x, y: x & y, conditions), 'sell'] = 1 return dataframe return populate_sell_trend @staticmethod def sell_indicator_space() -> List[Dimension]: """ Define your Hyperopt space for searching sell strategy parameters. """ return [ #Integer(75, 100, name='sell-mfi-value'), Integer(50, 100, name='sell-fastd-value'), Integer(50, 100, name='sell-fastk-value'), #Integer(50, 100, name='sell-adx-value'), Integer(100, 200, name='sell-cci-value'), #Categorical([True, False], name='sell-mfi-enabled'), Categorical([True, False], name='sell-fastd-enabled'), #Categorical([True, False], name='sell-adx-enabled'), Categorical([True, False], name='sell-cci-enabled'), Categorical([True, False], name='sell-fastk-enabled'), # Categorical(['sell-bb_upper', # 'sell-macd_cross_signal', # 'sell-sar_reversal'], name='sell-trigger') ] def populate_buy_trend(self, dataframe: DataFrame, metadata: dict) -> DataFrame: dataframe.loc[ ( ( (dataframe['open'] < dataframe['ema_low']) & (dataframe['adx'] > 30) & (dataframe['mfi'] < 30) & ( (dataframe['fastk'] < 30) & (dataframe['fastd'] < 30) & (qtpylib.crossed_above(dataframe['fastk'], dataframe['fastd'])) ) & (dataframe['resample_sma'] < dataframe['close']) ) # | # # try to get some sure things independent of resample # ((dataframe['rsi'] - dataframe['mfi']) < 10) & # (dataframe['mfi'] < 30) & # (dataframe['cci'] < -200) ), 'buy'] = 1 return dataframe def populate_sell_trend(self, dataframe: DataFrame, metadata: dict) -> DataFrame: dataframe.loc[ ( ( ( (dataframe['open'] >= dataframe['ema_high']) ) | ( (qtpylib.crossed_above(dataframe['fastk'], 70)) | (qtpylib.crossed_above(dataframe['fastd'], 70)) ) ) & (dataframe['cci'] > 100) ) , 'sell'] = 1 return dataframe ``` ### Hyperopt file and command: shallax@shallax-VirtualBox:~/freqtrade$ freqtrade hyperopt --hyperopt Rise --hyperopt-loss OnlyProfitHyperOptLoss --strategy=Ris --timerange=20180101-20180201 --timeframe=15m -e 300 ``` 2020-11-26 12:53:53,220 - freqtrade.configuration.configuration - INFO - Using config: user_data/config.json ... 2020-11-26 12:53:53,220 - freqtrade.loggers - INFO - Verbosity set to 0 2020-11-26 12:53:53,220 - freqtrade.configuration.configuration - INFO - Parameter -i/--timeframe detected ... Using timeframe: 15m ... 2020-11-26 12:53:53,220 - freqtrade.configuration.configuration - INFO - Using max_open_trades: 100 ... 2020-11-26 12:53:53,220 - freqtrade.configuration.configuration - INFO - Parameter --timerange detected: 20180101-20180201 ... 2020-11-26 12:53:53,221 - freqtrade.configuration.configuration - INFO - Using user-data directory: /home/shallax/freqtrade/user_data ... 2020-11-26 12:53:53,221 - freqtrade.configuration.configuration - INFO - Using data directory: /home/shallax/freqtrade/user_data/data/binance ... 2020-11-26 12:53:53,221 - freqtrade.configuration.configuration - INFO - Overriding timeframe with Command line argument 2020-11-26 12:53:53,221 - freqtrade.configuration.configuration - INFO - Using Hyperopt class name: Rise 2020-11-26 12:53:53,221 - freqtrade.configuration.configuration - INFO - Parameter --epochs detected ... Will run Hyperopt with for 300 epochs ... 2020-11-26 12:53:53,221 - freqtrade.configuration.configuration - INFO - Parameter -s/--spaces detected: default 2020-11-26 12:53:53,221 - freqtrade.configuration.configuration - INFO - Parameter -j/--job-workers detected: -1 2020-11-26 12:53:53,221 - freqtrade.configuration.configuration - INFO - Parameter --min-trades detected: 1 2020-11-26 12:53:53,221 - freqtrade.configuration.configuration - INFO - Using Hyperopt loss class name: OnlyProfitHyperOptLoss 2020-11-26 12:53:53,221 - freqtrade.configuration.configuration - INFO - Using "json" to store OHLCV data. 2020-11-26 12:53:53,221 - freqtrade.configuration.check_exchange - INFO - Checking exchange... 2020-11-26 12:53:53,221 - freqtrade.configuration.check_exchange - INFO - Exchange "binance" is officially supported by the Freqtrade development team. 2020-11-26 12:53:53,221 - freqtrade.configuration.configuration - INFO - Using pairlist from configuration. 2020-11-26 12:53:53,221 - freqtrade.configuration.config_validation - INFO - Validating configuration ... 2020-11-26 12:53:53,222 - freqtrade.commands.optimize_commands - INFO - Starting freqtrade in Hyperopt mode 2020-11-26 12:53:53,222 - filelock - INFO - Lock 140524426116688 acquired on /home/shallax/freqtrade/user_data/hyperopt.lock 2020-11-26 12:53:53,222 - freqtrade.exchange.exchange - INFO - Instance is running with dry_run enabled 2020-11-26 12:53:53,222 - freqtrade.exchange.exchange - INFO - Using CCXT 1.36.85 2020-11-26 12:53:53,222 - freqtrade.exchange.exchange - INFO - Applying additional ccxt config: {'enableRateLimit': True} 2020-11-26 12:53:53,226 - freqtrade.exchange.exchange - INFO - Applying additional ccxt config: {'enableRateLimit': True, 'rateLimit': 200} 2020-11-26 12:53:53,229 - freqtrade.exchange.exchange - INFO - Using Exchange "Binance" 2020-11-26 12:53:54,522 - freqtrade.resolvers.exchange_resolver - INFO - Using resolved exchange 'Binance'... 2020-11-26 12:53:54,533 - freqtrade.resolvers.iresolver - INFO - Using resolved strategy Ris from '/home/shallax/freqtrade/user_data/strategies/Ris.py'... 2020-11-26 12:53:54,534 - freqtrade.resolvers.strategy_resolver - INFO - Override strategy 'timeframe' with value in config file: 15m. 2020-11-26 12:53:54,534 - freqtrade.resolvers.strategy_resolver - INFO - Override strategy 'stake_currency' with value in config file: BTC. 2020-11-26 12:53:54,534 - freqtrade.resolvers.strategy_resolver - INFO - Override strategy 'stake_amount' with value in config file: 0.1. 2020-11-26 12:53:54,534 - freqtrade.resolvers.strategy_resolver - INFO - Override strategy 'unfilledtimeout' with value in config file: {'buy': 10, 'sell': 30}. 2020-11-26 12:53:54,534 - freqtrade.resolvers.strategy_resolver - INFO - Override strategy 'use_sell_signal' with value in config file: True. 2020-11-26 12:53:54,534 - freqtrade.resolvers.strategy_resolver - INFO - Override strategy 'sell_profit_only' with value in config file: False. 2020-11-26 12:53:54,534 - freqtrade.resolvers.strategy_resolver - INFO - Override strategy 'ignore_roi_if_buy_signal' with value in config file: False. 2020-11-26 12:53:54,534 - freqtrade.resolvers.strategy_resolver - INFO - Strategy using minimal_roi: {'0': 0.20223, '24': 0.09537, '55': 0.02539, '161': 0} 2020-11-26 12:53:54,534 - freqtrade.resolvers.strategy_resolver - INFO - Strategy using timeframe: 15m 2020-11-26 12:53:54,534 - freqtrade.resolvers.strategy_resolver - INFO - Strategy using stoploss: -0.1721 2020-11-26 12:53:54,534 - freqtrade.resolvers.strategy_resolver - INFO - Strategy using trailing_stop: False 2020-11-26 12:53:54,534 - freqtrade.resolvers.strategy_resolver - INFO - Strategy using trailing_stop_positive_offset: 0.0 2020-11-26 12:53:54,534 - freqtrade.resolvers.strategy_resolver - INFO - Strategy using trailing_only_offset_is_reached: False 2020-11-26 12:53:54,534 - freqtrade.resolvers.strategy_resolver - INFO - Strategy using process_only_new_candles: False 2020-11-26 12:53:54,534 - freqtrade.resolvers.strategy_resolver - INFO - Strategy using order_types: {'buy': 'limit', 'sell': 'limit', 'stoploss': 'limit', 'stoploss_on_exchange': False, 'stoploss_on_exchange_interval': 60} 2020-11-26 12:53:54,534 - freqtrade.resolvers.strategy_resolver - INFO - Strategy using order_time_in_force: {'buy': 'gtc', 'sell': 'gtc'} 2020-11-26 12:53:54,534 - freqtrade.resolvers.strategy_resolver - INFO - Strategy using stake_currency: BTC 2020-11-26 12:53:54,534 - freqtrade.resolvers.strategy_resolver - INFO - Strategy using stake_amount: 0.1 2020-11-26 12:53:54,534 - freqtrade.resolvers.strategy_resolver - INFO - Strategy using startup_candle_count: 0 2020-11-26 12:53:54,534 - freqtrade.resolvers.strategy_resolver - INFO - Strategy using unfilledtimeout: {'buy': 10, 'sell': 30} 2020-11-26 12:53:54,535 - freqtrade.resolvers.strategy_resolver - INFO - Strategy using use_sell_signal: True 2020-11-26 12:53:54,535 - freqtrade.resolvers.strategy_resolver - INFO - Strategy using sell_profit_only: False 2020-11-26 12:53:54,535 - freqtrade.resolvers.strategy_resolver - INFO - Strategy using ignore_roi_if_buy_signal: False 2020-11-26 12:53:54,535 - freqtrade.resolvers.strategy_resolver - INFO - Strategy using disable_dataframe_checks: False 2020-11-26 12:53:54,535 - freqtrade.configuration.config_validation - INFO - Validating configuration ... 2020-11-26 12:53:54,536 - freqtrade.resolvers.iresolver - INFO - Using resolved pairlist StaticPairList from '/home/shallax/freqtrade/freqtrade/pairlist/StaticPairList.py'... 2020-11-26 12:53:54,548 - freqtrade.resolvers.iresolver - INFO - Using resolved hyperopt Rise from '/home/shallax/freqtrade/user_data/hyperopts/Ris_hyperopt.py'... 2020-11-26 12:53:54,548 - freqtrade.resolvers.hyperopt_resolver - INFO - Hyperopt class does not provide populate_indicators() method. Using populate_indicators from the strategy. 2020-11-26 12:53:54,551 - freqtrade.resolvers.iresolver - INFO - Using resolved hyperoptloss OnlyProfitHyperOptLoss from '/home/shallax/freqtrade/freqtrade/optimize/hyperopt_loss_onlyprofit.py'... 2020-11-26 12:53:54,551 - freqtrade.optimize.hyperopt - INFO - Removing `/home/shallax/freqtrade/user_data/hyperopt_results/hyperopt_tickerdata.pkl`. 2020-11-26 12:53:54,552 - freqtrade.optimize.hyperopt - INFO - Using optimizer random state: 1505 2020-11-26 12:53:54,743 - numexpr.utils - INFO - NumExpr defaulting to 4 threads. 2020-11-26 12:53:54,771 - freqtrade.data.converter - INFO - Missing data fillup for LTC/BTC: before: 2970 - after: 2977 2020-11-26 12:53:54,773 - freqtrade.optimize.backtesting - INFO - Loading data from 2018-01-01 00:00:00 up to 2018-02-01 00:00:00 (31 days).. 2020-11-26 12:53:54,799 - freqtrade.optimize.hyperopt - INFO - Hyperopting with data from 2018-01-01 00:00:00 up to 2018-02-01 00:00:00 (31 days).. 2020-11-26 12:53:54,801 - freqtrade.optimize.hyperopt - INFO - Found 4 CPU cores. Let's make them scream! 2020-11-26 12:53:54,801 - freqtrade.optimize.hyperopt - INFO - Number of parallel jobs set as: -1 2020-11-26 12:53:54,810 - freqtrade.optimize.hyperopt_interface - INFO - Min roi table: {0: 0.04642, 30: 0.03095, 60: 0.01547, 90: 0} 2020-11-26 12:53:54,810 - freqtrade.optimize.hyperopt_interface - INFO - Max roi table: {0: 0.4797, 120: 0.17022, 300: 0.0619, 660: 0} 2020-11-26 12:53:54,821 - freqtrade.optimize.hyperopt - INFO - Effective number of parallel workers used: 4 +--------+---------+----------+------------------+--------------+------------------------------+----------------+-------------+ | Best | Epoch | Trades | Win Draw Loss | Avg profit | Profit | Avg duration | Objective | |--------+---------+----------+------------------+--------------+------------------------------+----------------+-------------| | * Best | 1/300 | 5 | 1 4 0 | 1.15% | 0.00573198 BTC (5.73%) | 1,776.0 m | 0.98091 | | * Best | 14/300 | 23 | 14 2 7 | 0.37% | 0.00847960 BTC (8.47%) | 408.3 m | 0.97176 | | * Best | 21/300 | 11 | 8 1 2 | 1.02% | 0.01123768 BTC (11.23%) | 141.8 m | 0.96258 | | * Best | 27/300 | 10 | 5 4 1 | 1.25% | 0.01253295 BTC (12.52%) | 225.0 m | 0.95827 | | Best | 45/300 | 11 | 6 4 1 | 1.20% | 0.01320340 BTC (13.19%) | 496.4 m | 0.95603 | | Best | 50/300 | 10 | 5 4 1 | 1.90% | 0.01901218 BTC (18.99%) | 513.0 m | 0.93669 | | Best | 59/300 | 12 | 9 3 0 | 2.36% | 0.02837098 BTC (28.34%) | 388.8 m | 0.90552 | [Epoch 300 of 300 (100%)] || | [Time: 0:05:36, Elapsed Time: 0:05:36] 2020-11-26 12:59:32,959 - freqtrade.optimize.hyperopt - INFO - 300 epochs saved to '/home/shallax/freqtrade/user_data/hyperopt_results/hyperopt_results_2020-11-26_12-53-54.pickle'. Best result: 59/300: 12 trades. 9/3/0 Wins/Draws/Losses. Avg profit 2.36%. Median profit 0.96%. Total profit 0.02837098 BTC ( 28.34Σ%). Avg duration 388.8 min. Objective: 0.90552 # Buy hyperspace params: buy_params = { 'adx-enabled': True, 'adx-value': 26, 'fastd-enabled': False, 'fastd-value': 22, 'fastk-enabled': False, 'fastk-value': 26, 'mfi-enabled': True, 'mfi-value': 21 } # Sell hyperspace params: sell_params = { 'sell-cci-enabled': True, 'sell-cci-value': 162, 'sell-fastd-enabled': False, 'sell-fastd-value': 53, 'sell-fastk-enabled': True, 'sell-fastk-value': 88 } # ROI table: minimal_roi = { "0": 0.28613, "76": 0.13764, "256": 0.03917, "381": 0 } # Stoploss: stoploss = -0.34571 ``` ### Then I adapt the strategy according to the above hyperopt output: ``` python # --- Do not remove these libs --- from freqtrade.strategy.interface import IStrategy from freqtrade.strategy import timeframe_to_minutes from technical.util import resample_to_interval, resampled_merge from pandas import DataFrame, DatetimeIndex, merge import numpy # noqa # -------------------------------- import talib.abstract as ta import freqtrade.vendor.qtpylib.indicators as qtpylib class Ris(IStrategy): """ this strategy is based around the idea of generating a lot of potentatils buys and make tiny profits on each trade we recommend to have at least 60 parallel trades at any time to cover non avoidable losses """ # Minimal ROI designed for the strategy. # This attribute will be overridden if the config file contains "minimal_roi" minimal_roi = { "0": 0.28613, "76": 0.13764, "256": 0.03917, "381": 0 } # Optimal stoploss designed for the strategy # This attribute will be overridden if the config file contains "stoploss" # should not be below 3% loss stoploss = -0.34571 # Optimal ticker interval for the strategy # the shorter the better ticker_interval = '15m' # resample factor to establish our general trend. Basically don't buy if a trend is not given resample_factor = 5 def populate_indicators(self, dataframe: DataFrame, metadata: dict) -> DataFrame: tf_res = timeframe_to_minutes(self.timeframe) * 5 df_res = resample_to_interval(dataframe, tf_res) df_res['sma'] = ta.SMA(df_res, 50, price='close') dataframe = resampled_merge(dataframe, df_res, fill_na=True) dataframe['resample_sma'] = dataframe[f'resample_{tf_res}_sma'] dataframe['ema_high'] = ta.EMA(dataframe, timeperiod=5, price='high') dataframe['ema_close'] = ta.EMA(dataframe, timeperiod=5, price='close') dataframe['ema_low'] = ta.EMA(dataframe, timeperiod=5, price='low') stoch_fast = ta.STOCHF(dataframe, 5, 3, 0, 3, 0) dataframe['fastd'] = stoch_fast['fastd'] dataframe['fastk'] = stoch_fast['fastk'] dataframe['adx'] = ta.ADX(dataframe) dataframe['cci'] = ta.CCI(dataframe, timeperiod=20) dataframe['rsi'] = ta.RSI(dataframe, timeperiod=14) dataframe['mfi'] = ta.MFI(dataframe) # required for graphing bollinger = qtpylib.bollinger_bands(dataframe['close'], window=20, stds=2) dataframe['bb_lowerband'] = bollinger['lower'] dataframe['bb_upperband'] = bollinger['upper'] dataframe['bb_middleband'] = bollinger['mid'] return dataframe def populate_buy_trend(self, dataframe: DataFrame, metadata: dict) -> DataFrame: dataframe.loc[ ( ( (dataframe['open'] < dataframe['ema_low']) & (dataframe['adx'] > 26) & (dataframe['mfi'] < 21) & ( #(dataframe['fastk'] < 30) & #(dataframe['fastd'] < 30) & (qtpylib.crossed_above(dataframe['fastk'], dataframe['fastd'])) ) & (dataframe['resample_sma'] < dataframe['close']) ) # | # # try to get some sure things independent of resample # ((dataframe['rsi'] - dataframe['mfi']) < 10) & # (dataframe['mfi'] < 30) & # (dataframe['cci'] < -200) ), 'buy'] = 1 return dataframe def populate_sell_trend(self, dataframe: DataFrame, metadata: dict) -> DataFrame: dataframe.loc[ ( ( ( (dataframe['open'] >= dataframe['ema_high']) ) | ( (qtpylib.crossed_above(dataframe['fastk'], 88)) # | (qtpylib.crossed_above(dataframe['fastd'], 70)) ) ) & (dataframe['cci'] > 162) ) , 'sell'] = 1 return dataframe ``` ### Backtest initiation and results: freqtrade backtesting -s Ris --export trades --timerange=20180101-20180201 --timeframe=15m Output: ``` 2020-11-26 13:06:16,209 - freqtrade.configuration.configuration - INFO - Using config: user_data/config.json ... 2020-11-26 13:06:16,209 - freqtrade.loggers - INFO - Verbosity set to 0 2020-11-26 13:06:16,209 - freqtrade.configuration.configuration - INFO - Parameter -i/--timeframe detected ... Using timeframe: 15m ... 2020-11-26 13:06:16,209 - freqtrade.configuration.configuration - INFO - Using max_open_trades: 100 ... 2020-11-26 13:06:16,210 - freqtrade.configuration.configuration - INFO - Parameter --timerange detected: 20180101-20180201 ... 2020-11-26 13:06:16,210 - freqtrade.configuration.configuration - INFO - Using user-data directory: /home/shallax/freqtrade/user_data ... 2020-11-26 13:06:16,210 - freqtrade.configuration.configuration - INFO - Using data directory: /home/shallax/freqtrade/user_data/data/binance ... 2020-11-26 13:06:16,210 - freqtrade.configuration.configuration - INFO - Overriding timeframe with Command line argument 2020-11-26 13:06:16,210 - freqtrade.configuration.configuration - INFO - Parameter --export detected: trades ... 2020-11-26 13:06:16,210 - freqtrade.configuration.configuration - INFO - Using "json" to store OHLCV data. 2020-11-26 13:06:16,210 - freqtrade.configuration.check_exchange - INFO - Checking exchange... 2020-11-26 13:06:16,210 - freqtrade.configuration.check_exchange - INFO - Exchange "binance" is officially supported by the Freqtrade development team. 2020-11-26 13:06:16,210 - freqtrade.configuration.configuration - INFO - Using pairlist from configuration. 2020-11-26 13:06:16,210 - freqtrade.configuration.config_validation - INFO - Validating configuration ... 2020-11-26 13:06:16,211 - freqtrade.commands.optimize_commands - INFO - Starting freqtrade in Backtesting mode 2020-11-26 13:06:16,211 - freqtrade.exchange.exchange - INFO - Instance is running with dry_run enabled 2020-11-26 13:06:16,211 - freqtrade.exchange.exchange - INFO - Using CCXT 1.36.85 2020-11-26 13:06:16,211 - freqtrade.exchange.exchange - INFO - Applying additional ccxt config: {'enableRateLimit': True} 2020-11-26 13:06:16,215 - freqtrade.exchange.exchange - INFO - Applying additional ccxt config: {'enableRateLimit': True, 'rateLimit': 200} 2020-11-26 13:06:16,218 - freqtrade.exchange.exchange - INFO - Using Exchange "Binance" 2020-11-26 13:06:16,965 - freqtrade.resolvers.exchange_resolver - INFO - Using resolved exchange 'Binance'... 2020-11-26 13:06:16,975 - freqtrade.resolvers.iresolver - INFO - Using resolved strategy Ris from '/home/shallax/freqtrade/user_data/strategies/Ris.py'... 2020-11-26 13:06:16,975 - freqtrade.resolvers.strategy_resolver - INFO - Override strategy 'timeframe' with value in config file: 15m. 2020-11-26 13:06:16,975 - freqtrade.resolvers.strategy_resolver - INFO - Override strategy 'stake_currency' with value in config file: BTC. 2020-11-26 13:06:16,975 - freqtrade.resolvers.strategy_resolver - INFO - Override strategy 'stake_amount' with value in config file: 0.1. 2020-11-26 13:06:16,975 - freqtrade.resolvers.strategy_resolver - INFO - Override strategy 'unfilledtimeout' with value in config file: {'buy': 10, 'sell': 30}. 2020-11-26 13:06:16,975 - freqtrade.resolvers.strategy_resolver - INFO - Override strategy 'use_sell_signal' with value in config file: True. 2020-11-26 13:06:16,975 - freqtrade.resolvers.strategy_resolver - INFO - Override strategy 'sell_profit_only' with value in config file: False. 2020-11-26 13:06:16,975 - freqtrade.resolvers.strategy_resolver - INFO - Override strategy 'ignore_roi_if_buy_signal' with value in config file: False. 2020-11-26 13:06:16,976 - freqtrade.resolvers.strategy_resolver - INFO - Strategy using minimal_roi: {'0': 0.28613, '76': 0.13764, '256': 0.03917, '381': 0} 2020-11-26 13:06:16,976 - freqtrade.resolvers.strategy_resolver - INFO - Strategy using timeframe: 15m 2020-11-26 13:06:16,976 - freqtrade.resolvers.strategy_resolver - INFO - Strategy using stoploss: -0.34571 2020-11-26 13:06:16,976 - freqtrade.resolvers.strategy_resolver - INFO - Strategy using trailing_stop: False 2020-11-26 13:06:16,976 - freqtrade.resolvers.strategy_resolver - INFO - Strategy using trailing_stop_positive_offset: 0.0 2020-11-26 13:06:16,976 - freqtrade.resolvers.strategy_resolver - INFO - Strategy using trailing_only_offset_is_reached: False 2020-11-26 13:06:16,976 - freqtrade.resolvers.strategy_resolver - INFO - Strategy using process_only_new_candles: False 2020-11-26 13:06:16,976 - freqtrade.resolvers.strategy_resolver - INFO - Strategy using order_types: {'buy': 'limit', 'sell': 'limit', 'stoploss': 'limit', 'stoploss_on_exchange': False, 'stoploss_on_exchange_interval': 60} 2020-11-26 13:06:16,976 - freqtrade.resolvers.strategy_resolver - INFO - Strategy using order_time_in_force: {'buy': 'gtc', 'sell': 'gtc'} 2020-11-26 13:06:16,976 - freqtrade.resolvers.strategy_resolver - INFO - Strategy using stake_currency: BTC 2020-11-26 13:06:16,976 - freqtrade.resolvers.strategy_resolver - INFO - Strategy using stake_amount: 0.1 2020-11-26 13:06:16,976 - freqtrade.resolvers.strategy_resolver - INFO - Strategy using startup_candle_count: 0 2020-11-26 13:06:16,976 - freqtrade.resolvers.strategy_resolver - INFO - Strategy using unfilledtimeout: {'buy': 10, 'sell': 30} 2020-11-26 13:06:16,976 - freqtrade.resolvers.strategy_resolver - INFO - Strategy using use_sell_signal: True 2020-11-26 13:06:16,976 - freqtrade.resolvers.strategy_resolver - INFO - Strategy using sell_profit_only: False 2020-11-26 13:06:16,976 - freqtrade.resolvers.strategy_resolver - INFO - Strategy using ignore_roi_if_buy_signal: False 2020-11-26 13:06:16,976 - freqtrade.resolvers.strategy_resolver - INFO - Strategy using disable_dataframe_checks: False 2020-11-26 13:06:16,976 - freqtrade.configuration.config_validation - INFO - Validating configuration ... 2020-11-26 13:06:16,979 - freqtrade.resolvers.iresolver - INFO - Using resolved pairlist StaticPairList from '/home/shallax/freqtrade/freqtrade/pairlist/StaticPairList.py'... 2020-11-26 13:06:16,980 - freqtrade.optimize.backtesting - INFO - Using stake_currency: BTC ... 2020-11-26 13:06:16,980 - freqtrade.optimize.backtesting - INFO - Using stake_amount: 0.1 ... 2020-11-26 13:06:17,153 - numexpr.utils - INFO - NumExpr defaulting to 4 threads. 2020-11-26 13:06:17,181 - freqtrade.data.converter - INFO - Missing data fillup for LTC/BTC: before: 2970 - after: 2977 2020-11-26 13:06:17,182 - freqtrade.optimize.backtesting - INFO - Loading data from 2018-01-01 00:00:00 up to 2018-02-01 00:00:00 (31 days).. 2020-11-26 13:06:17,182 - freqtrade.optimize.backtesting - INFO - Running backtesting for Strategy Ris 2020-11-26 13:06:17,205 - freqtrade.optimize.backtesting - INFO - Backtesting with data from 2018-01-01 00:00:00 up to 2018-02-01 00:00:00 (31 days).. 2020-11-26 13:06:17,232 - freqtrade.misc - INFO - dumping json to "/home/shallax/freqtrade/user_data/backtest_results/backtest-result-2020-11-26_13-06-17.json" 2020-11-26 13:06:17,233 - freqtrade.misc - INFO - dumping json to "/home/shallax/freqtrade/user_data/backtest_results/.last_result.json" Result for strategy Ris =========================================================== BACKTESTING REPORT ========================================================== | Pair | Buys | Avg Profit % | Cum Profit % | Tot Profit BTC | Tot Profit % | Avg Duration | Wins | Draws | Losses | |---------+--------+----------------+----------------+------------------+----------------+----------------+--------+---------+----------| | LTC/BTC | 0 | 0.00 | 0.00 | 0 | 0.00 | 0:00 | 0 | 0 | 0 | | TOTAL | 0 | 0.00 | 0.00 | 0 | 0.00 | 0:00 | 0 | 0 | 0 | ====================================================== SELL REASON STATS ====================================================== | Sell Reason | Sells | Wins | Draws | Losses | Avg Profit % | Cum Profit % | Tot Profit BTC | Tot Profit % | |---------------+---------+--------+---------+----------+----------------+----------------+------------------+----------------| ======================================================= LEFT OPEN TRADES REPORT ======================================================== | Pair | Buys | Avg Profit % | Cum Profit % | Tot Profit BTC | Tot Profit % | Avg Duration | Wins | Draws | Losses | |--------+--------+----------------+----------------+------------------+----------------+----------------+--------+---------+----------| | TOTAL | 0 | 0.00 | 0.00 | 0 | 0.00 | 0:00 | 0 | 0 | 0 | ``` ###Where is the mistake for this incongruence? I use the same timeframe and timerange and do not use --eps or --dmmp. Config file: ``` json { "max_open_trades": 100, "stake_currency": "BTC", "stake_amount": 0.1, "tradable_balance_ratio": 0.99, "fiat_display_currency": "USD", "timeframe": "5m", "dry_run": true, "cancel_open_orders_on_exit": false, "unfilledtimeout": { "buy": 10, "sell": 30 }, "bid_strategy": { "price_side": "bid", "ask_last_balance": 0.0, "use_order_book": false, "order_book_top": 1, "check_depth_of_market": { "enabled": false, "bids_to_ask_delta": 1 } }, "ask_strategy": { "price_side": "ask", "use_order_book": false, "order_book_min": 1, "order_book_max": 1, "use_sell_signal": true, "sell_profit_only": false, "ignore_roi_if_buy_signal": false }, "exchange": { "name": "binance", "key": "", "secret": "", "ccxt_config": {"enableRateLimit": true}, "ccxt_async_config": { "enableRateLimit": true, "rateLimit": 200 }, "pair_whitelist": [ "LTC/BTC", ], "pair_blacklist": [ "BNB/BTC", "BNB/BUSD", "BNB/ETH", "BNB/EUR", "BNB/NGN", "BNB/PAX", "BNB/RUB", "BNB/TRY", "BNB/TUSD", "BNB/USDC", "BNB/USDS", "BNB/USDT", ] }, "pairlists": [ {"method": "StaticPairList"} ], "edge": { "enabled": false, "process_throttle_secs": 3600, "calculate_since_number_of_days": 7, "allowed_risk": 0.01, "stoploss_range_min": -0.01, "stoploss_range_max": -0.1, "stoploss_range_step": -0.01, "minimum_winrate": 0.60, "minimum_expectancy": 0.20, "min_trade_number": 10, "max_trade_duration_minute": 1440, "remove_pumps": false }, "telegram": { "enabled": false, "token": "", "chat_id": "" }, "api_server": { "enabled": false, "listen_ip_address": "127.0.0.1", "listen_port": 8080, "verbosity": "info", "jwt_secret_key": "somethingrandom", "CORS_origins": [], "username": "", "password": "" }, "initial_state": "running", "forcebuy_enable": false, "internals": { "process_throttle_secs": 5 } } ``` ### I really appreciate your great work invested in this awesome open source project. I would be very thankful if someone could highlight/advice me what I did wrong in order to comprehend the mechanism better and to be finally able to reproduce identical results. Greetings

1.0

Hyperopt and Backtesting results differ despite exact parameters - ## Describe your environment * Operating system: Ubuntu 20.04.1 LTS * Python Version: Python 3.8.5 * CCXT version: 1.36.85 * Freqtrade Version: 2020.10 ## Your question Although I have carefully read through issue #2008 and #3557 concerning different Hyperopt and Backtesting results and understand the crucial concept of identical parameters as described in https://github.com/freqtrade/freqtrade/issues/3557#issuecomment-653687560, I have not once been able to reproduce at least comparable results. I am desperate because I do not see the mistake. I know that you do not have the time to solve individual strategy related issues, but helping me to find the reason for these massive incongruent results would maybe help future users stuck with the same problem. ### Strategy I work with a renamed version of the ReinforcedSmoothScalping Strategy on a 15m timeframe. ``` python # pragma pylint: disable=missing-docstring, invalid-name, pointless-string-statement from functools import reduce from typing import Any, Callable, Dict, List import talib.abstract as ta from pandas import DataFrame from skopt.space import Categorical, Dimension, Integer import freqtrade.vendor.qtpylib.indicators as qtpylib from freqtrade.optimize.hyperopt_interface import IHyperOpt class Rise(IHyperOpt): """ Default hyperopt provided by the Freqtrade bot. You can override it with your own Hyperopt """ @staticmethod def buy_strategy_generator(params: Dict[str, Any]) -> Callable: """ Define the buy strategy parameters to be used by Hyperopt. """ def populate_buy_trend(dataframe: DataFrame, metadata: dict) -> DataFrame: """ Buy strategy Hyperopt will build and use. """ conditions = [] # GUARDS AND TRENDS if 'mfi-enabled' in params and params['mfi-enabled']: conditions.append(dataframe['mfi'] < params['mfi-value']) if 'fastd-enabled' in params and params['fastd-enabled']: conditions.append(dataframe['fastd'] < params['fastd-value']) if 'adx-enabled' in params and params['adx-enabled']: conditions.append(dataframe['adx'] > params['adx-value']) # if 'rsi-enabled' in params and params['rsi-enabled']: # conditions.append(dataframe['rsi'] < params['rsi-value']) if 'fastk-enabled' in params and params['fastk-enabled']: conditions.append(dataframe['fastk'] < params['fastk-value']) # TRIGGERS # if 'trigger' in params: # if params['trigger'] == 'bb_lower': # conditions.append(dataframe['close'] < dataframe['bb_lowerband']) # if params['trigger'] == 'macd_cross_signal': # conditions.append(qtpylib.crossed_above( # dataframe['macd'], dataframe['macdsignal'] # )) # if params['trigger'] == 'sar_reversal': # conditions.append(qtpylib.crossed_above( # dataframe['close'], dataframe['sar'] # )) # Check that volume is not 0 conditions.append(dataframe['volume'] > 0) if conditions: dataframe.loc[ reduce(lambda x, y: x & y, conditions), 'buy'] = 1 return dataframe return populate_buy_trend @staticmethod def indicator_space() -> List[Dimension]: """ Define your Hyperopt space for searching buy strategy parameters. """ return [ Integer(10, 25, name='mfi-value'), Integer(15, 45, name='fastd-value'), Integer(15, 45, name='fastk-value'), Integer(20, 50, name='adx-value'), # Integer(20, 40, name='rsi-value'), Categorical([True, False], name='mfi-enabled'), Categorical([True, False], name='fastd-enabled'), Categorical([True, False], name='adx-enabled'), Categorical([True, False], name='fastk-enabled'), # Categorical([True, False], name='rsi-enabled'), # Categorical(['bb_lower', 'macd_cross_signal', 'sar_reversal'], name='trigger') ] @staticmethod def sell_strategy_generator(params: Dict[str, Any]) -> Callable: """ Define the sell strategy parameters to be used by Hyperopt. """ def populate_sell_trend(dataframe: DataFrame, metadata: dict) -> DataFrame: """ Sell strategy Hyperopt will build and use. """ conditions = [] # GUARDS AND TRENDS #if 'sell-mfi-enabled' in params and params['sell-mfi-enabled']: #conditions.append(dataframe['mfi'] > params['sell-mfi-value']) if 'sell-fastd-enabled' in params and params['sell-fastd-enabled']: conditions.append(dataframe['fastd'] > params['sell-fastd-value']) #if 'sell-adx-enabled' in params and params['sell-adx-enabled']: #conditions.append(dataframe['adx'] < params['sell-adx-value']) if 'sell-fastk-enabled' in params and params['sell-fastk-enabled']: conditions.append(dataframe['fastk'] > params['sell-fastk-value']) if 'sell-cci-enabled' in params and params['sell-cci-enabled']: conditions.append(dataframe['cci'] > params['sell-cci-value']) # TRIGGERS # if 'sell-trigger' in params: # if params['sell-trigger'] == 'sell-bb_upper': # conditions.append(dataframe['close'] > dataframe['bb_upperband']) # if params['sell-trigger'] == 'sell-macd_cross_signal': # conditions.append(qtpylib.crossed_above( # dataframe['macdsignal'], dataframe['macd'] # )) # if params['sell-trigger'] == 'sell-sar_reversal': # conditions.append(qtpylib.crossed_above( # dataframe['sar'], dataframe['close'] # )) # Check that volume is not 0 conditions.append(dataframe['volume'] > 0) if conditions: dataframe.loc[ reduce(lambda x, y: x & y, conditions), 'sell'] = 1 return dataframe return populate_sell_trend @staticmethod def sell_indicator_space() -> List[Dimension]: """ Define your Hyperopt space for searching sell strategy parameters. """ return [ #Integer(75, 100, name='sell-mfi-value'), Integer(50, 100, name='sell-fastd-value'), Integer(50, 100, name='sell-fastk-value'), #Integer(50, 100, name='sell-adx-value'), Integer(100, 200, name='sell-cci-value'), #Categorical([True, False], name='sell-mfi-enabled'), Categorical([True, False], name='sell-fastd-enabled'), #Categorical([True, False], name='sell-adx-enabled'), Categorical([True, False], name='sell-cci-enabled'), Categorical([True, False], name='sell-fastk-enabled'), # Categorical(['sell-bb_upper', # 'sell-macd_cross_signal', # 'sell-sar_reversal'], name='sell-trigger') ] def populate_buy_trend(self, dataframe: DataFrame, metadata: dict) -> DataFrame: dataframe.loc[ ( ( (dataframe['open'] < dataframe['ema_low']) & (dataframe['adx'] > 30) & (dataframe['mfi'] < 30) & ( (dataframe['fastk'] < 30) & (dataframe['fastd'] < 30) & (qtpylib.crossed_above(dataframe['fastk'], dataframe['fastd'])) ) & (dataframe['resample_sma'] < dataframe['close']) ) # | # # try to get some sure things independent of resample # ((dataframe['rsi'] - dataframe['mfi']) < 10) & # (dataframe['mfi'] < 30) & # (dataframe['cci'] < -200) ), 'buy'] = 1 return dataframe def populate_sell_trend(self, dataframe: DataFrame, metadata: dict) -> DataFrame: dataframe.loc[ ( ( ( (dataframe['open'] >= dataframe['ema_high']) ) | ( (qtpylib.crossed_above(dataframe['fastk'], 70)) | (qtpylib.crossed_above(dataframe['fastd'], 70)) ) ) & (dataframe['cci'] > 100) ) , 'sell'] = 1 return dataframe ``` ### Hyperopt file and command: shallax@shallax-VirtualBox:~/freqtrade$ freqtrade hyperopt --hyperopt Rise --hyperopt-loss OnlyProfitHyperOptLoss --strategy=Ris --timerange=20180101-20180201 --timeframe=15m -e 300 ``` 2020-11-26 12:53:53,220 - freqtrade.configuration.configuration - INFO - Using config: user_data/config.json ... 2020-11-26 12:53:53,220 - freqtrade.loggers - INFO - Verbosity set to 0 2020-11-26 12:53:53,220 - freqtrade.configuration.configuration - INFO - Parameter -i/--timeframe detected ... Using timeframe: 15m ... 2020-11-26 12:53:53,220 - freqtrade.configuration.configuration - INFO - Using max_open_trades: 100 ... 2020-11-26 12:53:53,220 - freqtrade.configuration.configuration - INFO - Parameter --timerange detected: 20180101-20180201 ... 2020-11-26 12:53:53,221 - freqtrade.configuration.configuration - INFO - Using user-data directory: /home/shallax/freqtrade/user_data ... 2020-11-26 12:53:53,221 - freqtrade.configuration.configuration - INFO - Using data directory: /home/shallax/freqtrade/user_data/data/binance ... 2020-11-26 12:53:53,221 - freqtrade.configuration.configuration - INFO - Overriding timeframe with Command line argument 2020-11-26 12:53:53,221 - freqtrade.configuration.configuration - INFO - Using Hyperopt class name: Rise 2020-11-26 12:53:53,221 - freqtrade.configuration.configuration - INFO - Parameter --epochs detected ... Will run Hyperopt with for 300 epochs ... 2020-11-26 12:53:53,221 - freqtrade.configuration.configuration - INFO - Parameter -s/--spaces detected: default 2020-11-26 12:53:53,221 - freqtrade.configuration.configuration - INFO - Parameter -j/--job-workers detected: -1 2020-11-26 12:53:53,221 - freqtrade.configuration.configuration - INFO - Parameter --min-trades detected: 1 2020-11-26 12:53:53,221 - freqtrade.configuration.configuration - INFO - Using Hyperopt loss class name: OnlyProfitHyperOptLoss 2020-11-26 12:53:53,221 - freqtrade.configuration.configuration - INFO - Using "json" to store OHLCV data. 2020-11-26 12:53:53,221 - freqtrade.configuration.check_exchange - INFO - Checking exchange... 2020-11-26 12:53:53,221 - freqtrade.configuration.check_exchange - INFO - Exchange "binance" is officially supported by the Freqtrade development team. 2020-11-26 12:53:53,221 - freqtrade.configuration.configuration - INFO - Using pairlist from configuration. 2020-11-26 12:53:53,221 - freqtrade.configuration.config_validation - INFO - Validating configuration ... 2020-11-26 12:53:53,222 - freqtrade.commands.optimize_commands - INFO - Starting freqtrade in Hyperopt mode 2020-11-26 12:53:53,222 - filelock - INFO - Lock 140524426116688 acquired on /home/shallax/freqtrade/user_data/hyperopt.lock 2020-11-26 12:53:53,222 - freqtrade.exchange.exchange - INFO - Instance is running with dry_run enabled 2020-11-26 12:53:53,222 - freqtrade.exchange.exchange - INFO - Using CCXT 1.36.85 2020-11-26 12:53:53,222 - freqtrade.exchange.exchange - INFO - Applying additional ccxt config: {'enableRateLimit': True} 2020-11-26 12:53:53,226 - freqtrade.exchange.exchange - INFO - Applying additional ccxt config: {'enableRateLimit': True, 'rateLimit': 200} 2020-11-26 12:53:53,229 - freqtrade.exchange.exchange - INFO - Using Exchange "Binance" 2020-11-26 12:53:54,522 - freqtrade.resolvers.exchange_resolver - INFO - Using resolved exchange 'Binance'... 2020-11-26 12:53:54,533 - freqtrade.resolvers.iresolver - INFO - Using resolved strategy Ris from '/home/shallax/freqtrade/user_data/strategies/Ris.py'... 2020-11-26 12:53:54,534 - freqtrade.resolvers.strategy_resolver - INFO - Override strategy 'timeframe' with value in config file: 15m. 2020-11-26 12:53:54,534 - freqtrade.resolvers.strategy_resolver - INFO - Override strategy 'stake_currency' with value in config file: BTC. 2020-11-26 12:53:54,534 - freqtrade.resolvers.strategy_resolver - INFO - Override strategy 'stake_amount' with value in config file: 0.1. 2020-11-26 12:53:54,534 - freqtrade.resolvers.strategy_resolver - INFO - Override strategy 'unfilledtimeout' with value in config file: {'buy': 10, 'sell': 30}. 2020-11-26 12:53:54,534 - freqtrade.resolvers.strategy_resolver - INFO - Override strategy 'use_sell_signal' with value in config file: True. 2020-11-26 12:53:54,534 - freqtrade.resolvers.strategy_resolver - INFO - Override strategy 'sell_profit_only' with value in config file: False. 2020-11-26 12:53:54,534 - freqtrade.resolvers.strategy_resolver - INFO - Override strategy 'ignore_roi_if_buy_signal' with value in config file: False. 2020-11-26 12:53:54,534 - freqtrade.resolvers.strategy_resolver - INFO - Strategy using minimal_roi: {'0': 0.20223, '24': 0.09537, '55': 0.02539, '161': 0} 2020-11-26 12:53:54,534 - freqtrade.resolvers.strategy_resolver - INFO - Strategy using timeframe: 15m 2020-11-26 12:53:54,534 - freqtrade.resolvers.strategy_resolver - INFO - Strategy using stoploss: -0.1721 2020-11-26 12:53:54,534 - freqtrade.resolvers.strategy_resolver - INFO - Strategy using trailing_stop: False 2020-11-26 12:53:54,534 - freqtrade.resolvers.strategy_resolver - INFO - Strategy using trailing_stop_positive_offset: 0.0 2020-11-26 12:53:54,534 - freqtrade.resolvers.strategy_resolver - INFO - Strategy using trailing_only_offset_is_reached: False 2020-11-26 12:53:54,534 - freqtrade.resolvers.strategy_resolver - INFO - Strategy using process_only_new_candles: False 2020-11-26 12:53:54,534 - freqtrade.resolvers.strategy_resolver - INFO - Strategy using order_types: {'buy': 'limit', 'sell': 'limit', 'stoploss': 'limit', 'stoploss_on_exchange': False, 'stoploss_on_exchange_interval': 60} 2020-11-26 12:53:54,534 - freqtrade.resolvers.strategy_resolver - INFO - Strategy using order_time_in_force: {'buy': 'gtc', 'sell': 'gtc'} 2020-11-26 12:53:54,534 - freqtrade.resolvers.strategy_resolver - INFO - Strategy using stake_currency: BTC 2020-11-26 12:53:54,534 - freqtrade.resolvers.strategy_resolver - INFO - Strategy using stake_amount: 0.1 2020-11-26 12:53:54,534 - freqtrade.resolvers.strategy_resolver - INFO - Strategy using startup_candle_count: 0 2020-11-26 12:53:54,534 - freqtrade.resolvers.strategy_resolver - INFO - Strategy using unfilledtimeout: {'buy': 10, 'sell': 30} 2020-11-26 12:53:54,535 - freqtrade.resolvers.strategy_resolver - INFO - Strategy using use_sell_signal: True 2020-11-26 12:53:54,535 - freqtrade.resolvers.strategy_resolver - INFO - Strategy using sell_profit_only: False 2020-11-26 12:53:54,535 - freqtrade.resolvers.strategy_resolver - INFO - Strategy using ignore_roi_if_buy_signal: False 2020-11-26 12:53:54,535 - freqtrade.resolvers.strategy_resolver - INFO - Strategy using disable_dataframe_checks: False 2020-11-26 12:53:54,535 - freqtrade.configuration.config_validation - INFO - Validating configuration ... 2020-11-26 12:53:54,536 - freqtrade.resolvers.iresolver - INFO - Using resolved pairlist StaticPairList from '/home/shallax/freqtrade/freqtrade/pairlist/StaticPairList.py'... 2020-11-26 12:53:54,548 - freqtrade.resolvers.iresolver - INFO - Using resolved hyperopt Rise from '/home/shallax/freqtrade/user_data/hyperopts/Ris_hyperopt.py'... 2020-11-26 12:53:54,548 - freqtrade.resolvers.hyperopt_resolver - INFO - Hyperopt class does not provide populate_indicators() method. Using populate_indicators from the strategy. 2020-11-26 12:53:54,551 - freqtrade.resolvers.iresolver - INFO - Using resolved hyperoptloss OnlyProfitHyperOptLoss from '/home/shallax/freqtrade/freqtrade/optimize/hyperopt_loss_onlyprofit.py'... 2020-11-26 12:53:54,551 - freqtrade.optimize.hyperopt - INFO - Removing `/home/shallax/freqtrade/user_data/hyperopt_results/hyperopt_tickerdata.pkl`. 2020-11-26 12:53:54,552 - freqtrade.optimize.hyperopt - INFO - Using optimizer random state: 1505 2020-11-26 12:53:54,743 - numexpr.utils - INFO - NumExpr defaulting to 4 threads. 2020-11-26 12:53:54,771 - freqtrade.data.converter - INFO - Missing data fillup for LTC/BTC: before: 2970 - after: 2977 2020-11-26 12:53:54,773 - freqtrade.optimize.backtesting - INFO - Loading data from 2018-01-01 00:00:00 up to 2018-02-01 00:00:00 (31 days).. 2020-11-26 12:53:54,799 - freqtrade.optimize.hyperopt - INFO - Hyperopting with data from 2018-01-01 00:00:00 up to 2018-02-01 00:00:00 (31 days).. 2020-11-26 12:53:54,801 - freqtrade.optimize.hyperopt - INFO - Found 4 CPU cores. Let's make them scream! 2020-11-26 12:53:54,801 - freqtrade.optimize.hyperopt - INFO - Number of parallel jobs set as: -1 2020-11-26 12:53:54,810 - freqtrade.optimize.hyperopt_interface - INFO - Min roi table: {0: 0.04642, 30: 0.03095, 60: 0.01547, 90: 0} 2020-11-26 12:53:54,810 - freqtrade.optimize.hyperopt_interface - INFO - Max roi table: {0: 0.4797, 120: 0.17022, 300: 0.0619, 660: 0} 2020-11-26 12:53:54,821 - freqtrade.optimize.hyperopt - INFO - Effective number of parallel workers used: 4 +--------+---------+----------+------------------+--------------+------------------------------+----------------+-------------+ | Best | Epoch | Trades | Win Draw Loss | Avg profit | Profit | Avg duration | Objective | |--------+---------+----------+------------------+--------------+------------------------------+----------------+-------------| | * Best | 1/300 | 5 | 1 4 0 | 1.15% | 0.00573198 BTC (5.73%) | 1,776.0 m | 0.98091 | | * Best | 14/300 | 23 | 14 2 7 | 0.37% | 0.00847960 BTC (8.47%) | 408.3 m | 0.97176 | | * Best | 21/300 | 11 | 8 1 2 | 1.02% | 0.01123768 BTC (11.23%) | 141.8 m | 0.96258 | | * Best | 27/300 | 10 | 5 4 1 | 1.25% | 0.01253295 BTC (12.52%) | 225.0 m | 0.95827 | | Best | 45/300 | 11 | 6 4 1 | 1.20% | 0.01320340 BTC (13.19%) | 496.4 m | 0.95603 | | Best | 50/300 | 10 | 5 4 1 | 1.90% | 0.01901218 BTC (18.99%) | 513.0 m | 0.93669 | | Best | 59/300 | 12 | 9 3 0 | 2.36% | 0.02837098 BTC (28.34%) | 388.8 m | 0.90552 | [Epoch 300 of 300 (100%)] || | [Time: 0:05:36, Elapsed Time: 0:05:36] 2020-11-26 12:59:32,959 - freqtrade.optimize.hyperopt - INFO - 300 epochs saved to '/home/shallax/freqtrade/user_data/hyperopt_results/hyperopt_results_2020-11-26_12-53-54.pickle'. Best result: 59/300: 12 trades. 9/3/0 Wins/Draws/Losses. Avg profit 2.36%. Median profit 0.96%. Total profit 0.02837098 BTC ( 28.34Σ%). Avg duration 388.8 min. Objective: 0.90552 # Buy hyperspace params: buy_params = { 'adx-enabled': True, 'adx-value': 26, 'fastd-enabled': False, 'fastd-value': 22, 'fastk-enabled': False, 'fastk-value': 26, 'mfi-enabled': True, 'mfi-value': 21 } # Sell hyperspace params: sell_params = { 'sell-cci-enabled': True, 'sell-cci-value': 162, 'sell-fastd-enabled': False, 'sell-fastd-value': 53, 'sell-fastk-enabled': True, 'sell-fastk-value': 88 } # ROI table: minimal_roi = { "0": 0.28613, "76": 0.13764, "256": 0.03917, "381": 0 } # Stoploss: stoploss = -0.34571 ``` ### Then I adapt the strategy according to the above hyperopt output: ``` python # --- Do not remove these libs --- from freqtrade.strategy.interface import IStrategy from freqtrade.strategy import timeframe_to_minutes from technical.util import resample_to_interval, resampled_merge from pandas import DataFrame, DatetimeIndex, merge import numpy # noqa # -------------------------------- import talib.abstract as ta import freqtrade.vendor.qtpylib.indicators as qtpylib class Ris(IStrategy): """ this strategy is based around the idea of generating a lot of potentatils buys and make tiny profits on each trade we recommend to have at least 60 parallel trades at any time to cover non avoidable losses """ # Minimal ROI designed for the strategy. # This attribute will be overridden if the config file contains "minimal_roi" minimal_roi = { "0": 0.28613, "76": 0.13764, "256": 0.03917, "381": 0 } # Optimal stoploss designed for the strategy # This attribute will be overridden if the config file contains "stoploss" # should not be below 3% loss stoploss = -0.34571 # Optimal ticker interval for the strategy # the shorter the better ticker_interval = '15m' # resample factor to establish our general trend. Basically don't buy if a trend is not given resample_factor = 5 def populate_indicators(self, dataframe: DataFrame, metadata: dict) -> DataFrame: tf_res = timeframe_to_minutes(self.timeframe) * 5 df_res = resample_to_interval(dataframe, tf_res) df_res['sma'] = ta.SMA(df_res, 50, price='close') dataframe = resampled_merge(dataframe, df_res, fill_na=True) dataframe['resample_sma'] = dataframe[f'resample_{tf_res}_sma'] dataframe['ema_high'] = ta.EMA(dataframe, timeperiod=5, price='high') dataframe['ema_close'] = ta.EMA(dataframe, timeperiod=5, price='close') dataframe['ema_low'] = ta.EMA(dataframe, timeperiod=5, price='low') stoch_fast = ta.STOCHF(dataframe, 5, 3, 0, 3, 0) dataframe['fastd'] = stoch_fast['fastd'] dataframe['fastk'] = stoch_fast['fastk'] dataframe['adx'] = ta.ADX(dataframe) dataframe['cci'] = ta.CCI(dataframe, timeperiod=20) dataframe['rsi'] = ta.RSI(dataframe, timeperiod=14) dataframe['mfi'] = ta.MFI(dataframe) # required for graphing bollinger = qtpylib.bollinger_bands(dataframe['close'], window=20, stds=2) dataframe['bb_lowerband'] = bollinger['lower'] dataframe['bb_upperband'] = bollinger['upper'] dataframe['bb_middleband'] = bollinger['mid'] return dataframe def populate_buy_trend(self, dataframe: DataFrame, metadata: dict) -> DataFrame: dataframe.loc[ ( ( (dataframe['open'] < dataframe['ema_low']) & (dataframe['adx'] > 26) & (dataframe['mfi'] < 21) & ( #(dataframe['fastk'] < 30) & #(dataframe['fastd'] < 30) & (qtpylib.crossed_above(dataframe['fastk'], dataframe['fastd'])) ) & (dataframe['resample_sma'] < dataframe['close']) ) # | # # try to get some sure things independent of resample # ((dataframe['rsi'] - dataframe['mfi']) < 10) & # (dataframe['mfi'] < 30) & # (dataframe['cci'] < -200) ), 'buy'] = 1 return dataframe def populate_sell_trend(self, dataframe: DataFrame, metadata: dict) -> DataFrame: dataframe.loc[ ( ( ( (dataframe['open'] >= dataframe['ema_high']) ) | ( (qtpylib.crossed_above(dataframe['fastk'], 88)) # | (qtpylib.crossed_above(dataframe['fastd'], 70)) ) ) & (dataframe['cci'] > 162) ) , 'sell'] = 1 return dataframe ``` ### Backtest initiation and results: freqtrade backtesting -s Ris --export trades --timerange=20180101-20180201 --timeframe=15m Output: ``` 2020-11-26 13:06:16,209 - freqtrade.configuration.configuration - INFO - Using config: user_data/config.json ... 2020-11-26 13:06:16,209 - freqtrade.loggers - INFO - Verbosity set to 0 2020-11-26 13:06:16,209 - freqtrade.configuration.configuration - INFO - Parameter -i/--timeframe detected ... Using timeframe: 15m ... 2020-11-26 13:06:16,209 - freqtrade.configuration.configuration - INFO - Using max_open_trades: 100 ... 2020-11-26 13:06:16,210 - freqtrade.configuration.configuration - INFO - Parameter --timerange detected: 20180101-20180201 ... 2020-11-26 13:06:16,210 - freqtrade.configuration.configuration - INFO - Using user-data directory: /home/shallax/freqtrade/user_data ... 2020-11-26 13:06:16,210 - freqtrade.configuration.configuration - INFO - Using data directory: /home/shallax/freqtrade/user_data/data/binance ... 2020-11-26 13:06:16,210 - freqtrade.configuration.configuration - INFO - Overriding timeframe with Command line argument 2020-11-26 13:06:16,210 - freqtrade.configuration.configuration - INFO - Parameter --export detected: trades ... 2020-11-26 13:06:16,210 - freqtrade.configuration.configuration - INFO - Using "json" to store OHLCV data. 2020-11-26 13:06:16,210 - freqtrade.configuration.check_exchange - INFO - Checking exchange... 2020-11-26 13:06:16,210 - freqtrade.configuration.check_exchange - INFO - Exchange "binance" is officially supported by the Freqtrade development team. 2020-11-26 13:06:16,210 - freqtrade.configuration.configuration - INFO - Using pairlist from configuration. 2020-11-26 13:06:16,210 - freqtrade.configuration.config_validation - INFO - Validating configuration ... 2020-11-26 13:06:16,211 - freqtrade.commands.optimize_commands - INFO - Starting freqtrade in Backtesting mode 2020-11-26 13:06:16,211 - freqtrade.exchange.exchange - INFO - Instance is running with dry_run enabled 2020-11-26 13:06:16,211 - freqtrade.exchange.exchange - INFO - Using CCXT 1.36.85 2020-11-26 13:06:16,211 - freqtrade.exchange.exchange - INFO - Applying additional ccxt config: {'enableRateLimit': True} 2020-11-26 13:06:16,215 - freqtrade.exchange.exchange - INFO - Applying additional ccxt config: {'enableRateLimit': True, 'rateLimit': 200} 2020-11-26 13:06:16,218 - freqtrade.exchange.exchange - INFO - Using Exchange "Binance" 2020-11-26 13:06:16,965 - freqtrade.resolvers.exchange_resolver - INFO - Using resolved exchange 'Binance'... 2020-11-26 13:06:16,975 - freqtrade.resolvers.iresolver - INFO - Using resolved strategy Ris from '/home/shallax/freqtrade/user_data/strategies/Ris.py'... 2020-11-26 13:06:16,975 - freqtrade.resolvers.strategy_resolver - INFO - Override strategy 'timeframe' with value in config file: 15m. 2020-11-26 13:06:16,975 - freqtrade.resolvers.strategy_resolver - INFO - Override strategy 'stake_currency' with value in config file: BTC. 2020-11-26 13:06:16,975 - freqtrade.resolvers.strategy_resolver - INFO - Override strategy 'stake_amount' with value in config file: 0.1. 2020-11-26 13:06:16,975 - freqtrade.resolvers.strategy_resolver - INFO - Override strategy 'unfilledtimeout' with value in config file: {'buy': 10, 'sell': 30}. 2020-11-26 13:06:16,975 - freqtrade.resolvers.strategy_resolver - INFO - Override strategy 'use_sell_signal' with value in config file: True. 2020-11-26 13:06:16,975 - freqtrade.resolvers.strategy_resolver - INFO - Override strategy 'sell_profit_only' with value in config file: False. 2020-11-26 13:06:16,975 - freqtrade.resolvers.strategy_resolver - INFO - Override strategy 'ignore_roi_if_buy_signal' with value in config file: False. 2020-11-26 13:06:16,976 - freqtrade.resolvers.strategy_resolver - INFO - Strategy using minimal_roi: {'0': 0.28613, '76': 0.13764, '256': 0.03917, '381': 0} 2020-11-26 13:06:16,976 - freqtrade.resolvers.strategy_resolver - INFO - Strategy using timeframe: 15m 2020-11-26 13:06:16,976 - freqtrade.resolvers.strategy_resolver - INFO - Strategy using stoploss: -0.34571 2020-11-26 13:06:16,976 - freqtrade.resolvers.strategy_resolver - INFO - Strategy using trailing_stop: False 2020-11-26 13:06:16,976 - freqtrade.resolvers.strategy_resolver - INFO - Strategy using trailing_stop_positive_offset: 0.0 2020-11-26 13:06:16,976 - freqtrade.resolvers.strategy_resolver - INFO - Strategy using trailing_only_offset_is_reached: False 2020-11-26 13:06:16,976 - freqtrade.resolvers.strategy_resolver - INFO - Strategy using process_only_new_candles: False 2020-11-26 13:06:16,976 - freqtrade.resolvers.strategy_resolver - INFO - Strategy using order_types: {'buy': 'limit', 'sell': 'limit', 'stoploss': 'limit', 'stoploss_on_exchange': False, 'stoploss_on_exchange_interval': 60} 2020-11-26 13:06:16,976 - freqtrade.resolvers.strategy_resolver - INFO - Strategy using order_time_in_force: {'buy': 'gtc', 'sell': 'gtc'} 2020-11-26 13:06:16,976 - freqtrade.resolvers.strategy_resolver - INFO - Strategy using stake_currency: BTC 2020-11-26 13:06:16,976 - freqtrade.resolvers.strategy_resolver - INFO - Strategy using stake_amount: 0.1 2020-11-26 13:06:16,976 - freqtrade.resolvers.strategy_resolver - INFO - Strategy using startup_candle_count: 0 2020-11-26 13:06:16,976 - freqtrade.resolvers.strategy_resolver - INFO - Strategy using unfilledtimeout: {'buy': 10, 'sell': 30} 2020-11-26 13:06:16,976 - freqtrade.resolvers.strategy_resolver - INFO - Strategy using use_sell_signal: True 2020-11-26 13:06:16,976 - freqtrade.resolvers.strategy_resolver - INFO - Strategy using sell_profit_only: False 2020-11-26 13:06:16,976 - freqtrade.resolvers.strategy_resolver - INFO - Strategy using ignore_roi_if_buy_signal: False 2020-11-26 13:06:16,976 - freqtrade.resolvers.strategy_resolver - INFO - Strategy using disable_dataframe_checks: False 2020-11-26 13:06:16,976 - freqtrade.configuration.config_validation - INFO - Validating configuration ... 2020-11-26 13:06:16,979 - freqtrade.resolvers.iresolver - INFO - Using resolved pairlist StaticPairList from '/home/shallax/freqtrade/freqtrade/pairlist/StaticPairList.py'... 2020-11-26 13:06:16,980 - freqtrade.optimize.backtesting - INFO - Using stake_currency: BTC ... 2020-11-26 13:06:16,980 - freqtrade.optimize.backtesting - INFO - Using stake_amount: 0.1 ... 2020-11-26 13:06:17,153 - numexpr.utils - INFO - NumExpr defaulting to 4 threads. 2020-11-26 13:06:17,181 - freqtrade.data.converter - INFO - Missing data fillup for LTC/BTC: before: 2970 - after: 2977 2020-11-26 13:06:17,182 - freqtrade.optimize.backtesting - INFO - Loading data from 2018-01-01 00:00:00 up to 2018-02-01 00:00:00 (31 days).. 2020-11-26 13:06:17,182 - freqtrade.optimize.backtesting - INFO - Running backtesting for Strategy Ris 2020-11-26 13:06:17,205 - freqtrade.optimize.backtesting - INFO - Backtesting with data from 2018-01-01 00:00:00 up to 2018-02-01 00:00:00 (31 days).. 2020-11-26 13:06:17,232 - freqtrade.misc - INFO - dumping json to "/home/shallax/freqtrade/user_data/backtest_results/backtest-result-2020-11-26_13-06-17.json" 2020-11-26 13:06:17,233 - freqtrade.misc - INFO - dumping json to "/home/shallax/freqtrade/user_data/backtest_results/.last_result.json" Result for strategy Ris =========================================================== BACKTESTING REPORT ========================================================== | Pair | Buys | Avg Profit % | Cum Profit % | Tot Profit BTC | Tot Profit % | Avg Duration | Wins | Draws | Losses | |---------+--------+----------------+----------------+------------------+----------------+----------------+--------+---------+----------| | LTC/BTC | 0 | 0.00 | 0.00 | 0 | 0.00 | 0:00 | 0 | 0 | 0 | | TOTAL | 0 | 0.00 | 0.00 | 0 | 0.00 | 0:00 | 0 | 0 | 0 | ====================================================== SELL REASON STATS ====================================================== | Sell Reason | Sells | Wins | Draws | Losses | Avg Profit % | Cum Profit % | Tot Profit BTC | Tot Profit % | |---------------+---------+--------+---------+----------+----------------+----------------+------------------+----------------| ======================================================= LEFT OPEN TRADES REPORT ======================================================== | Pair | Buys | Avg Profit % | Cum Profit % | Tot Profit BTC | Tot Profit % | Avg Duration | Wins | Draws | Losses | |--------+--------+----------------+----------------+------------------+----------------+----------------+--------+---------+----------| | TOTAL | 0 | 0.00 | 0.00 | 0 | 0.00 | 0:00 | 0 | 0 | 0 | ``` ###Where is the mistake for this incongruence? I use the same timeframe and timerange and do not use --eps or --dmmp. Config file: ``` json { "max_open_trades": 100, "stake_currency": "BTC", "stake_amount": 0.1, "tradable_balance_ratio": 0.99, "fiat_display_currency": "USD", "timeframe": "5m", "dry_run": true, "cancel_open_orders_on_exit": false, "unfilledtimeout": { "buy": 10, "sell": 30 }, "bid_strategy": { "price_side": "bid", "ask_last_balance": 0.0, "use_order_book": false, "order_book_top": 1, "check_depth_of_market": { "enabled": false, "bids_to_ask_delta": 1 } }, "ask_strategy": { "price_side": "ask", "use_order_book": false, "order_book_min": 1, "order_book_max": 1, "use_sell_signal": true, "sell_profit_only": false, "ignore_roi_if_buy_signal": false }, "exchange": { "name": "binance", "key": "", "secret": "", "ccxt_config": {"enableRateLimit": true}, "ccxt_async_config": { "enableRateLimit": true, "rateLimit": 200 }, "pair_whitelist": [ "LTC/BTC", ], "pair_blacklist": [ "BNB/BTC", "BNB/BUSD", "BNB/ETH", "BNB/EUR", "BNB/NGN", "BNB/PAX", "BNB/RUB", "BNB/TRY", "BNB/TUSD", "BNB/USDC", "BNB/USDS", "BNB/USDT", ] }, "pairlists": [ {"method": "StaticPairList"} ], "edge": { "enabled": false, "process_throttle_secs": 3600, "calculate_since_number_of_days": 7, "allowed_risk": 0.01, "stoploss_range_min": -0.01, "stoploss_range_max": -0.1, "stoploss_range_step": -0.01, "minimum_winrate": 0.60, "minimum_expectancy": 0.20, "min_trade_number": 10, "max_trade_duration_minute": 1440, "remove_pumps": false }, "telegram": { "enabled": false, "token": "", "chat_id": "" }, "api_server": { "enabled": false, "listen_ip_address": "127.0.0.1", "listen_port": 8080, "verbosity": "info", "jwt_secret_key": "somethingrandom", "CORS_origins": [], "username": "", "password": "" }, "initial_state": "running", "forcebuy_enable": false, "internals": { "process_throttle_secs": 5 } } ``` ### I really appreciate your great work invested in this awesome open source project. I would be very thankful if someone could highlight/advice me what I did wrong in order to comprehend the mechanism better and to be finally able to reproduce identical results. Greetings

non_priority

hyperopt and backtesting results differ despite exact parameters describe your environment operating system ubuntu lts python version python ccxt version freqtrade version your question although i have carefully read through issue and concerning different hyperopt and backtesting results and understand the crucial concept of identical parameters as described in i have not once been able to reproduce at least comparable results i am desperate because i do not see the mistake i know that you do not have the time to solve individual strategy related issues but helping me to find the reason for these massive incongruent results would maybe help future users stuck with the same problem strategy i work with a renamed version of the reinforcedsmoothscalping strategy on a timeframe python pragma pylint disable missing docstring invalid name pointless string statement from functools import reduce from typing import any callable dict list import talib abstract as ta from pandas import dataframe from skopt space import categorical dimension integer import freqtrade vendor qtpylib indicators as qtpylib from freqtrade optimize hyperopt interface import ihyperopt class rise ihyperopt default hyperopt provided by the freqtrade bot you can override it with your own hyperopt staticmethod def buy strategy generator params dict callable define the buy strategy parameters to be used by hyperopt def populate buy trend dataframe dataframe metadata dict dataframe buy strategy hyperopt will build and use conditions guards and trends if mfi enabled in params and params conditions append dataframe params if fastd enabled in params and params conditions append dataframe params if adx enabled in params and params conditions append dataframe params if rsi enabled in params and params conditions append dataframe params if fastk enabled in params and params conditions append dataframe params triggers if trigger in params if params bb lower conditions append dataframe dataframe if params macd cross signal conditions append qtpylib crossed above dataframe dataframe if params sar reversal conditions append qtpylib crossed above dataframe dataframe check that volume is not conditions append dataframe if conditions dataframe loc reduce lambda x y x y conditions buy return dataframe return populate buy trend staticmethod def indicator space list define your hyperopt space for searching buy strategy parameters return integer name mfi value integer name fastd value integer name fastk value integer name adx value integer name rsi value categorical name mfi enabled categorical name fastd enabled categorical name adx enabled categorical name fastk enabled categorical name rsi enabled categorical name trigger staticmethod def sell strategy generator params dict callable define the sell strategy parameters to be used by hyperopt def populate sell trend dataframe dataframe metadata dict dataframe sell strategy hyperopt will build and use conditions guards and trends if sell mfi enabled in params and params conditions append dataframe params if sell fastd enabled in params and params conditions append dataframe params if sell adx enabled in params and params conditions append dataframe params if sell fastk enabled in params and params conditions append dataframe params if sell cci enabled in params and params conditions append dataframe params triggers if sell trigger in params if params sell bb upper conditions append dataframe dataframe if params sell macd cross signal conditions append qtpylib crossed above dataframe dataframe if params sell sar reversal conditions append qtpylib crossed above dataframe dataframe check that volume is not conditions append dataframe if conditions dataframe loc reduce lambda x y x y conditions sell return dataframe return populate sell trend staticmethod def sell indicator space list define your hyperopt space for searching sell strategy parameters return integer name sell mfi value integer name sell fastd value integer name sell fastk value integer name sell adx value integer name sell cci value categorical name sell mfi enabled categorical name sell fastd enabled categorical name sell adx enabled categorical name sell cci enabled categorical name sell fastk enabled categorical sell bb upper sell macd cross signal sell sar reversal name sell trigger def populate buy trend self dataframe dataframe metadata dict dataframe dataframe loc dataframe dataframe dataframe dataframe dataframe dataframe qtpylib crossed above dataframe dataframe dataframe dataframe try to get some sure things independent of resample dataframe dataframe dataframe dataframe buy return dataframe def populate sell trend self dataframe dataframe metadata dict dataframe dataframe loc dataframe dataframe qtpylib crossed above dataframe qtpylib crossed above dataframe dataframe sell return dataframe hyperopt file and command shallax shallax virtualbox freqtrade freqtrade hyperopt hyperopt rise hyperopt loss onlyprofithyperoptloss strategy ris timerange timeframe e freqtrade configuration configuration info using config user data config json freqtrade loggers info verbosity set to freqtrade configuration configuration info parameter i timeframe detected using timeframe freqtrade configuration configuration info using max open trades freqtrade configuration configuration info parameter timerange detected freqtrade configuration configuration info using user data directory home shallax freqtrade user data freqtrade configuration configuration info using data directory home shallax freqtrade user data data binance freqtrade configuration configuration info overriding timeframe with command line argument freqtrade configuration configuration info using hyperopt class name rise freqtrade configuration configuration info parameter epochs detected will run hyperopt with for epochs freqtrade configuration configuration info parameter s spaces detected default freqtrade configuration configuration info parameter j job workers detected freqtrade configuration configuration info parameter min trades detected freqtrade configuration configuration info using hyperopt loss class name onlyprofithyperoptloss freqtrade configuration configuration info using json to store ohlcv data freqtrade configuration check exchange info checking exchange freqtrade configuration check exchange info exchange binance is officially supported by the freqtrade development team freqtrade configuration configuration info using pairlist from configuration freqtrade configuration config validation info validating configuration freqtrade commands optimize commands info starting freqtrade in hyperopt mode filelock info lock acquired on home shallax freqtrade user data hyperopt lock freqtrade exchange exchange info instance is running with dry run enabled freqtrade exchange exchange info using ccxt freqtrade exchange exchange info applying additional ccxt config enableratelimit true freqtrade exchange exchange info applying additional ccxt config enableratelimit true ratelimit freqtrade exchange exchange info using exchange binance freqtrade resolvers exchange resolver info using resolved exchange binance freqtrade resolvers iresolver info using resolved strategy ris from home shallax freqtrade user data strategies ris py freqtrade resolvers strategy resolver info override strategy timeframe with value in config file freqtrade resolvers strategy resolver info override strategy stake currency with value in config file btc freqtrade resolvers strategy resolver info override strategy stake amount with value in config file freqtrade resolvers strategy resolver info override strategy unfilledtimeout with value in config file buy sell freqtrade resolvers strategy resolver info override strategy use sell signal with value in config file true freqtrade resolvers strategy resolver info override strategy sell profit only with value in config file false freqtrade resolvers strategy resolver info override strategy ignore roi if buy signal with value in config file false freqtrade resolvers strategy resolver info strategy using minimal roi freqtrade resolvers strategy resolver info strategy using timeframe freqtrade resolvers strategy resolver info strategy using stoploss freqtrade resolvers strategy resolver info strategy using trailing stop false freqtrade resolvers strategy resolver info strategy using trailing stop positive offset freqtrade resolvers strategy resolver info strategy using trailing only offset is reached false freqtrade resolvers strategy resolver info strategy using process only new candles false freqtrade resolvers strategy resolver info strategy using order types buy limit sell limit stoploss limit stoploss on exchange false stoploss on exchange interval freqtrade resolvers strategy resolver info strategy using order time in force buy gtc sell gtc freqtrade resolvers strategy resolver info strategy using stake currency btc freqtrade resolvers strategy resolver info strategy using stake amount freqtrade resolvers strategy resolver info strategy using startup candle count freqtrade resolvers strategy resolver info strategy using unfilledtimeout buy sell freqtrade resolvers strategy resolver info strategy using use sell signal true freqtrade resolvers strategy resolver info strategy using sell profit only false freqtrade resolvers strategy resolver info strategy using ignore roi if buy signal false freqtrade resolvers strategy resolver info strategy using disable dataframe checks false freqtrade configuration config validation info validating configuration freqtrade resolvers iresolver info using resolved pairlist staticpairlist from home shallax freqtrade freqtrade pairlist staticpairlist py freqtrade resolvers iresolver info using resolved hyperopt rise from home shallax freqtrade user data hyperopts ris hyperopt py freqtrade resolvers hyperopt resolver info hyperopt class does not provide populate indicators method using populate indicators from the strategy freqtrade resolvers iresolver info using resolved hyperoptloss onlyprofithyperoptloss from home shallax freqtrade freqtrade optimize hyperopt loss onlyprofit py freqtrade optimize hyperopt info removing home shallax freqtrade user data hyperopt results hyperopt tickerdata pkl freqtrade optimize hyperopt info using optimizer random state numexpr utils info numexpr defaulting to threads freqtrade data converter info missing data fillup for ltc btc before after freqtrade optimize backtesting info loading data from up to days freqtrade optimize hyperopt info hyperopting with data from up to days freqtrade optimize hyperopt info found cpu cores let s make them scream freqtrade optimize hyperopt info number of parallel jobs set as freqtrade optimize hyperopt interface info min roi table freqtrade optimize hyperopt interface info max roi table freqtrade optimize hyperopt info effective number of parallel workers used best epoch trades win draw loss avg profit profit avg duration objective best btc m best btc m best btc m best btc m best btc m best btc m best btc m freqtrade optimize hyperopt info epochs saved to home shallax freqtrade user data hyperopt results hyperopt results pickle best result trades wins draws losses avg profit median profit total profit btc avg duration min objective buy hyperspace params buy params adx enabled true adx value fastd enabled false fastd value fastk enabled false fastk value mfi enabled true mfi value sell hyperspace params sell params sell cci enabled true sell cci value sell fastd enabled false sell fastd value sell fastk enabled true sell fastk value roi table minimal roi stoploss stoploss then i adapt the strategy according to the above hyperopt output python do not remove these libs from freqtrade strategy interface import istrategy from freqtrade strategy import timeframe to minutes from technical util import resample to interval resampled merge from pandas import dataframe datetimeindex merge import numpy noqa import talib abstract as ta import freqtrade vendor qtpylib indicators as qtpylib class ris istrategy this strategy is based around the idea of generating a lot of potentatils buys and make tiny profits on each trade we recommend to have at least parallel trades at any time to cover non avoidable losses minimal roi designed for the strategy this attribute will be overridden if the config file contains minimal roi minimal roi optimal stoploss designed for the strategy this attribute will be overridden if the config file contains stoploss should not be below loss stoploss optimal ticker interval for the strategy the shorter the better ticker interval resample factor to establish our general trend basically don t buy if a trend is not given resample factor def populate indicators self dataframe dataframe metadata dict dataframe tf res timeframe to minutes self timeframe df res resample to interval dataframe tf res df res ta sma df res price close dataframe resampled merge dataframe df res fill na true dataframe dataframe dataframe ta ema dataframe timeperiod price high dataframe ta ema dataframe timeperiod price close dataframe ta ema dataframe timeperiod price low stoch fast ta stochf dataframe dataframe stoch fast dataframe stoch fast dataframe ta adx dataframe dataframe ta cci dataframe timeperiod dataframe ta rsi dataframe timeperiod dataframe ta mfi dataframe required for graphing bollinger qtpylib bollinger bands dataframe window stds dataframe bollinger dataframe bollinger dataframe bollinger return dataframe def populate buy trend self dataframe dataframe metadata dict dataframe dataframe loc dataframe dataframe dataframe dataframe dataframe dataframe qtpylib crossed above dataframe dataframe dataframe dataframe try to get some sure things independent of resample dataframe dataframe dataframe dataframe buy return dataframe def populate sell trend self dataframe dataframe metadata dict dataframe dataframe loc dataframe dataframe qtpylib crossed above dataframe qtpylib crossed above dataframe dataframe sell return dataframe backtest initiation and results freqtrade backtesting s ris export trades timerange timeframe output freqtrade configuration configuration info using config user data config json freqtrade loggers info verbosity set to freqtrade configuration configuration info parameter i timeframe detected using timeframe freqtrade configuration configuration info using max open trades freqtrade configuration configuration info parameter timerange detected freqtrade configuration configuration info using user data directory home shallax freqtrade user data freqtrade configuration configuration info using data directory home shallax freqtrade user data data binance freqtrade configuration configuration info overriding timeframe with command line argument freqtrade configuration configuration info parameter export detected trades freqtrade configuration configuration info using json to store ohlcv data freqtrade configuration check exchange info checking exchange freqtrade configuration check exchange info exchange binance is officially supported by the freqtrade development team freqtrade configuration configuration info using pairlist from configuration freqtrade configuration config validation info validating configuration freqtrade commands optimize commands info starting freqtrade in backtesting mode freqtrade exchange exchange info instance is running with dry run enabled freqtrade exchange exchange info using ccxt freqtrade exchange exchange info applying additional ccxt config enableratelimit true freqtrade exchange exchange info applying additional ccxt config enableratelimit true ratelimit freqtrade exchange exchange info using exchange binance freqtrade resolvers exchange resolver info using resolved exchange binance freqtrade resolvers iresolver info using resolved strategy ris from home shallax freqtrade user data strategies ris py freqtrade resolvers strategy resolver info override strategy timeframe with value in config file freqtrade resolvers strategy resolver info override strategy stake currency with value in config file btc freqtrade resolvers strategy resolver info override strategy stake amount with value in config file freqtrade resolvers strategy resolver info override strategy unfilledtimeout with value in config file buy sell freqtrade resolvers strategy resolver info override strategy use sell signal with value in config file true freqtrade resolvers strategy resolver info override strategy sell profit only with value in config file false freqtrade resolvers strategy resolver info override strategy ignore roi if buy signal with value in config file false freqtrade resolvers strategy resolver info strategy using minimal roi freqtrade resolvers strategy resolver info strategy using timeframe freqtrade resolvers strategy resolver info strategy using stoploss freqtrade resolvers strategy resolver info strategy using trailing stop false freqtrade resolvers strategy resolver info strategy using trailing stop positive offset freqtrade resolvers strategy resolver info strategy using trailing only offset is reached false freqtrade resolvers strategy resolver info strategy using process only new candles false freqtrade resolvers strategy resolver info strategy using order types buy limit sell limit stoploss limit stoploss on exchange false stoploss on exchange interval freqtrade resolvers strategy resolver info strategy using order time in force buy gtc sell gtc freqtrade resolvers strategy resolver info strategy using stake currency btc freqtrade resolvers strategy resolver info strategy using stake amount freqtrade resolvers strategy resolver info strategy using startup candle count freqtrade resolvers strategy resolver info strategy using unfilledtimeout buy sell freqtrade resolvers strategy resolver info strategy using use sell signal true freqtrade resolvers strategy resolver info strategy using sell profit only false freqtrade resolvers strategy resolver info strategy using ignore roi if buy signal false freqtrade resolvers strategy resolver info strategy using disable dataframe checks false freqtrade configuration config validation info validating configuration freqtrade resolvers iresolver info using resolved pairlist staticpairlist from home shallax freqtrade freqtrade pairlist staticpairlist py freqtrade optimize backtesting info using stake currency btc freqtrade optimize backtesting info using stake amount numexpr utils info numexpr defaulting to threads freqtrade data converter info missing data fillup for ltc btc before after freqtrade optimize backtesting info loading data from up to days freqtrade optimize backtesting info running backtesting for strategy ris freqtrade optimize backtesting info backtesting with data from up to days freqtrade misc info dumping json to home shallax freqtrade user data backtest results backtest result json freqtrade misc info dumping json to home shallax freqtrade user data backtest results last result json result for strategy ris backtesting report pair buys avg profit cum profit tot profit btc tot profit avg duration wins draws losses ltc btc total sell reason stats sell reason sells wins draws losses avg profit cum profit tot profit btc tot profit left open trades report pair buys avg profit cum profit tot profit btc tot profit avg duration wins draws losses total where is the mistake for this incongruence i use the same timeframe and timerange and do not use eps or dmmp config file json max open trades stake currency btc stake amount tradable balance ratio fiat display currency usd timeframe dry run true cancel open orders on exit false unfilledtimeout buy sell bid strategy price side bid ask last balance use order book false order book top check depth of market enabled false bids to ask delta ask strategy price side ask use order book false order book min order book max use sell signal true sell profit only false ignore roi if buy signal false exchange name binance key secret ccxt config enableratelimit true ccxt async config enableratelimit true ratelimit pair whitelist ltc btc pair blacklist bnb btc bnb busd bnb eth bnb eur bnb ngn bnb pax bnb rub bnb try bnb tusd bnb usdc bnb usds bnb usdt pairlists method staticpairlist edge enabled false process throttle secs calculate since number of days allowed risk stoploss range min stoploss range max stoploss range step minimum winrate minimum expectancy min trade number max trade duration minute remove pumps false telegram enabled false token chat id api server enabled false listen ip address listen port verbosity info jwt secret key somethingrandom cors origins username password initial state running forcebuy enable false internals process throttle secs i really appreciate your great work invested in this awesome open source project i would be very thankful if someone could highlight advice me what i did wrong in order to comprehend the mechanism better and to be finally able to reproduce identical results greetings

IssuesEvent

2017-11-08 20:54:23

Microsoft/vscode

https://api.github.com/repos/Microsoft/vscode

closed

npm install failed when build from vscode source v1.17.2

smoke-test

<!-- Do you have a question? Please ask it on http://stackoverflow.com/questions/tagged/vscode. --> <!-- Use Help > Report Issues to prefill these. --> - VSCode Version: 1.17.2 - OS Version: win 7 - node version: v7.4.0 - npm version: v4.0.5 Steps to Reproduce: 1. scripts\npm.bat install install to get error as follows: ``` > [email protected] postinstall C:\workspace\vscode-1.17.2\vscode-1.17.2\test\smoke > tsc src/spectron/client.ts(28,26): error TS2345: Argument of type 'Client<RawResult< null>> & RawResult<null> & Client<void>' is not assignable to parameter of type 'void | PromiseLike<void>'. Type 'Client<RawResult<null>> & RawResult<null> & Client<void>' is not assigna ble to type 'PromiseLike<void>'. Types of property 'then' are incompatible. Type '(<P>(onFulfilled?: ((value: RawResult<null>) => P | Client<P>) | und efined, onRejected?: ((error:...' is not assignable to type '<TResult1 = void, T Result2 = never>(onfulfilled?: ((value: void) => TResult1 | PromiseLike<TResul.. .'. Types of parameters 'onFulfilled' and 'onfulfilled' are incompatible. Type '((value: void) => any) | null | undefined' is not assignable to type '((value: RawResult<null>) => any) | undefined'. Type 'null' is not assignable to type '((value: RawResult<null>) => any) | undefined'. npm WARN [email protected] No repository field. npm WARN [email protected] No license field. npm ERR! Windows_NT 6.1.7601 npm ERR! argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\ node_modules\\npm\\bin\\npm-cli.js" "install" npm ERR! node v7.4.0 npm ERR! npm v4.0.5 npm ERR! code ELIFECYCLE npm ERR! [email protected] postinstall: `tsc` npm ERR! Exit status 2 ``` * other info: building from the v1.16.0 source is successful in the same env

1.0

npm install failed when build from vscode source v1.17.2 - <!-- Do you have a question? Please ask it on http://stackoverflow.com/questions/tagged/vscode. --> <!-- Use Help > Report Issues to prefill these. --> - VSCode Version: 1.17.2 - OS Version: win 7 - node version: v7.4.0 - npm version: v4.0.5 Steps to Reproduce: 1. scripts\npm.bat install install to get error as follows: ``` > [email protected] postinstall C:\workspace\vscode-1.17.2\vscode-1.17.2\test\smoke > tsc src/spectron/client.ts(28,26): error TS2345: Argument of type 'Client<RawResult< null>> & RawResult<null> & Client<void>' is not assignable to parameter of type 'void | PromiseLike<void>'. Type 'Client<RawResult<null>> & RawResult<null> & Client<void>' is not assigna ble to type 'PromiseLike<void>'. Types of property 'then' are incompatible. Type '(<P>(onFulfilled?: ((value: RawResult<null>) => P | Client<P>) | und efined, onRejected?: ((error:...' is not assignable to type '<TResult1 = void, T Result2 = never>(onfulfilled?: ((value: void) => TResult1 | PromiseLike<TResul.. .'. Types of parameters 'onFulfilled' and 'onfulfilled' are incompatible. Type '((value: void) => any) | null | undefined' is not assignable to type '((value: RawResult<null>) => any) | undefined'. Type 'null' is not assignable to type '((value: RawResult<null>) => any) | undefined'. npm WARN [email protected] No repository field. npm WARN [email protected] No license field. npm ERR! Windows_NT 6.1.7601 npm ERR! argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\ node_modules\\npm\\bin\\npm-cli.js" "install" npm ERR! node v7.4.0 npm ERR! npm v4.0.5 npm ERR! code ELIFECYCLE npm ERR! [email protected] postinstall: `tsc` npm ERR! Exit status 2 ``` * other info: building from the v1.16.0 source is successful in the same env

non_priority

npm install failed when build from vscode source report issues to prefill these vscode version os version win node version npm version steps to reproduce scripts npm bat install install to get error as follows code oss dev smoke test postinstall c workspace vscode vscode test smoke tsc src spectron client ts error argument of type client rawresult null rawresult client is not assignable to parameter of type void promiselike type client rawresult client is not assigna ble to type promiselike types of property then are incompatible type onfulfilled value rawresult p client und efined onrejected error is not assignable to type void t never onfulfilled value void promiselike tresul types of parameters onfulfilled and onfulfilled are incompatible type value void any null undefined is not assignable to type value rawresult any undefined type null is not assignable to type value rawresult any undefined npm warn code oss dev smoke test no repository field npm warn code oss dev smoke test no license field npm err windows nt npm err argv c program files nodejs node exe c program files nodejs node modules npm bin npm cli js install npm err node npm err npm npm err code elifecycle npm err code oss dev smoke test postinstall tsc npm err exit status other info building from the source is successful in the same env

IssuesEvent

2020-10-28 10:13:00

microsoft/AzureStorageExplorer

https://api.github.com/repos/microsoft/AzureStorageExplorer

opened

Keep a consistent case for the property 'Etag' in the properties dialog between one blob and one file

:gear: blobs :gear: files 🧪 testing

**Storage Explorer Version:** 1.16.0-dev **Build**: 20201028.3 **Branch**: main **Platform/OS:** Windows 10/ Linux Ubuntu 16.04/ MacOS Catalina **Architecture**: ia32/x64 **Regression From**: Not a regression **Steps to reproduce:** 1. Expand one storage account -> File Shares. 2. Create one file share -> Upload one file -> Check its properties. 3. Expand one storage account -> Blob Containers. 4. Create one blob container -> Upload one blob -> Check its properties. **Expect Experience:** Keep a consistent case for the property 'Etag'. **Actual Experience:** 1. Show 'Etag' in the file's properties dialog. 2. Show 'ETag' in the blob's properties dialog.  **More Info:** 1. Show 'Uri' in one file's properties dialog while show 'URL' in one blob's properties dialog.

1.0

Keep a consistent case for the property 'Etag' in the properties dialog between one blob and one file - **Storage Explorer Version:** 1.16.0-dev **Build**: 20201028.3 **Branch**: main **Platform/OS:** Windows 10/ Linux Ubuntu 16.04/ MacOS Catalina **Architecture**: ia32/x64 **Regression From**: Not a regression **Steps to reproduce:** 1. Expand one storage account -> File Shares. 2. Create one file share -> Upload one file -> Check its properties. 3. Expand one storage account -> Blob Containers. 4. Create one blob container -> Upload one blob -> Check its properties. **Expect Experience:** Keep a consistent case for the property 'Etag'. **Actual Experience:** 1. Show 'Etag' in the file's properties dialog. 2. Show 'ETag' in the blob's properties dialog.  **More Info:** 1. Show 'Uri' in one file's properties dialog while show 'URL' in one blob's properties dialog.

non_priority

keep a consistent case for the property etag in the properties dialog between one blob and one file storage explorer version dev build branch main platform os windows linux ubuntu macos catalina architecture regression from not a regression steps to reproduce expand one storage account file shares create one file share upload one file check its properties expand one storage account blob containers create one blob container upload one blob check its properties expect experience keep a consistent case for the property etag actual experience show etag in the file s properties dialog show etag in the blob s properties dialog more info show uri in one file s properties dialog while show url in one blob s properties dialog

IssuesEvent

2020-05-22 21:25:57

wrbejar/Nova8HML

https://api.github.com/repos/wrbejar/Nova8HML

opened

CVE-2017-3523 (High) detected in mysql-connector-java-5.1.26.jar

security vulnerability

## CVE-2017-3523 - High Severity Vulnerability <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>mysql-connector-java-5.1.26.jar</b></p></summary> <p>MySQL JDBC Type 4 driver</p> <p>Library home page: <a href="http://dev.mysql.com/doc/connector-j/en/">http://dev.mysql.com/doc/connector-j/en/</a></p> <p>Path to dependency file: /tmp/ws-ua_20200522212458_OUIMQA/archiveExtraction_TASGJV/20200522212458/ws-scm_depth_0/Nova8HML/target/JavaVulnerableLab/META-INF/maven/org.cysecurity/JavaVulnerableLab/pom.xml</p> <p>Path to vulnerable library: epository/mysql/mysql-connector-java/5.1.26/mysql-connector-java-5.1.26.jar,_depth_0/Nova8HML/target/JavaVulnerableLab/META-INF/maven/org.cysecurity/JavaVulnerableLab/target/JavaVulnerableLab/WEB-INF/lib/mysql-connector-java-5.1.26.jar,/Nova8HML/target/JavaVulnerableLab/WEB-INF/lib/mysql-connector-java-5.1.26.jar,epository/mysql/mysql-connector-java/5.1.26/mysql-connector-java-5.1.26.jar,_depth_0/Nova8HML/target/JavaVulnerableLab/WEB-INF/lib/mysql-connector-java-5.1.26.jar</p> <p> Dependency Hierarchy: - :x: **mysql-connector-java-5.1.26.jar** (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/wrbejar/Nova8HML/commit/59d70a6939762caf159f40fd62a37577fd9e1ced">59d70a6939762caf159f40fd62a37577fd9e1ced</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> Vulnerability in the MySQL Connectors component of Oracle MySQL (subcomponent: Connector/J). Supported versions that are affected are 5.1.40 and earlier. Difficult to exploit vulnerability allows low privileged attacker with network access via multiple protocols to compromise MySQL Connectors. While the vulnerability is in MySQL Connectors, attacks may significantly impact additional products. Successful attacks of this vulnerability can result in takeover of MySQL Connectors. CVSS 3.0 Base Score 8.5 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H). <p>Publish Date: 2017-04-24 <p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2017-3523>CVE-2017-3523</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.5</b>)</summary> <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: High - Privileges Required: Low - User Interaction: None - Scope: Changed - Impact Metrics: - Confidentiality Impact: High - Integrity Impact: High - Availability Impact: High </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary> <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://www.oracle.com/technetwork/security-advisory/cpuapr2017-3236618.html">https://www.oracle.com/technetwork/security-advisory/cpuapr2017-3236618.html</a></p> <p>Release Date: 2017-04-24</p> <p>Fix Resolution: 5.1.41</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":"mysql","packageName":"mysql-connector-java","packageVersion":"5.1.26","isTransitiveDependency":false,"dependencyTree":"mysql:mysql-connector-java:5.1.26","isMinimumFixVersionAvailable":true,"minimumFixVersion":"5.1.41"}],"vulnerabilityIdentifier":"CVE-2017-3523","vulnerabilityDetails":"Vulnerability in the MySQL Connectors component of Oracle MySQL (subcomponent: Connector/J). Supported versions that are affected are 5.1.40 and earlier. Difficult to exploit vulnerability allows low privileged attacker with network access via multiple protocols to compromise MySQL Connectors. While the vulnerability is in MySQL Connectors, attacks may significantly impact additional products. Successful attacks of this vulnerability can result in takeover of MySQL Connectors. CVSS 3.0 Base Score 8.5 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H).","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2017-3523","cvss3Severity":"high","cvss3Score":"8.5","cvss3Metrics":{"A":"High","AC":"High","PR":"Low","S":"Changed","C":"High","UI":"None","AV":"Network","I":"High"},"extraData":{}}</REMEDIATE> -->

True

CVE-2017-3523 (High) detected in mysql-connector-java-5.1.26.jar - ## CVE-2017-3523 - High Severity Vulnerability <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>mysql-connector-java-5.1.26.jar</b></p></summary> <p>MySQL JDBC Type 4 driver</p> <p>Library home page: <a href="http://dev.mysql.com/doc/connector-j/en/">http://dev.mysql.com/doc/connector-j/en/</a></p> <p>Path to dependency file: /tmp/ws-ua_20200522212458_OUIMQA/archiveExtraction_TASGJV/20200522212458/ws-scm_depth_0/Nova8HML/target/JavaVulnerableLab/META-INF/maven/org.cysecurity/JavaVulnerableLab/pom.xml</p> <p>Path to vulnerable library: epository/mysql/mysql-connector-java/5.1.26/mysql-connector-java-5.1.26.jar,_depth_0/Nova8HML/target/JavaVulnerableLab/META-INF/maven/org.cysecurity/JavaVulnerableLab/target/JavaVulnerableLab/WEB-INF/lib/mysql-connector-java-5.1.26.jar,/Nova8HML/target/JavaVulnerableLab/WEB-INF/lib/mysql-connector-java-5.1.26.jar,epository/mysql/mysql-connector-java/5.1.26/mysql-connector-java-5.1.26.jar,_depth_0/Nova8HML/target/JavaVulnerableLab/WEB-INF/lib/mysql-connector-java-5.1.26.jar</p> <p> Dependency Hierarchy: - :x: **mysql-connector-java-5.1.26.jar** (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/wrbejar/Nova8HML/commit/59d70a6939762caf159f40fd62a37577fd9e1ced">59d70a6939762caf159f40fd62a37577fd9e1ced</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> Vulnerability in the MySQL Connectors component of Oracle MySQL (subcomponent: Connector/J). Supported versions that are affected are 5.1.40 and earlier. Difficult to exploit vulnerability allows low privileged attacker with network access via multiple protocols to compromise MySQL Connectors. While the vulnerability is in MySQL Connectors, attacks may significantly impact additional products. Successful attacks of this vulnerability can result in takeover of MySQL Connectors. CVSS 3.0 Base Score 8.5 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H). <p>Publish Date: 2017-04-24 <p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2017-3523>CVE-2017-3523</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.5</b>)</summary> <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: High - Privileges Required: Low - User Interaction: None - Scope: Changed - Impact Metrics: - Confidentiality Impact: High - Integrity Impact: High - Availability Impact: High </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary> <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://www.oracle.com/technetwork/security-advisory/cpuapr2017-3236618.html">https://www.oracle.com/technetwork/security-advisory/cpuapr2017-3236618.html</a></p> <p>Release Date: 2017-04-24</p> <p>Fix Resolution: 5.1.41</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":"mysql","packageName":"mysql-connector-java","packageVersion":"5.1.26","isTransitiveDependency":false,"dependencyTree":"mysql:mysql-connector-java:5.1.26","isMinimumFixVersionAvailable":true,"minimumFixVersion":"5.1.41"}],"vulnerabilityIdentifier":"CVE-2017-3523","vulnerabilityDetails":"Vulnerability in the MySQL Connectors component of Oracle MySQL (subcomponent: Connector/J). Supported versions that are affected are 5.1.40 and earlier. Difficult to exploit vulnerability allows low privileged attacker with network access via multiple protocols to compromise MySQL Connectors. While the vulnerability is in MySQL Connectors, attacks may significantly impact additional products. Successful attacks of this vulnerability can result in takeover of MySQL Connectors. CVSS 3.0 Base Score 8.5 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H).","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2017-3523","cvss3Severity":"high","cvss3Score":"8.5","cvss3Metrics":{"A":"High","AC":"High","PR":"Low","S":"Changed","C":"High","UI":"None","AV":"Network","I":"High"},"extraData":{}}</REMEDIATE> -->

non_priority

cve high detected in mysql connector java jar cve high severity vulnerability vulnerable library mysql connector java jar mysql jdbc type driver library home page a href path to dependency file tmp ws ua ouimqa archiveextraction tasgjv ws scm depth target javavulnerablelab meta inf maven org cysecurity javavulnerablelab pom xml path to vulnerable library epository mysql mysql connector java mysql connector java jar depth target javavulnerablelab meta inf maven org cysecurity javavulnerablelab target javavulnerablelab web inf lib mysql connector java jar target javavulnerablelab web inf lib mysql connector java jar epository mysql mysql connector java mysql connector java jar depth target javavulnerablelab web inf lib mysql connector java jar dependency hierarchy x mysql connector java jar vulnerable library found in head commit a href vulnerability details vulnerability in the mysql connectors component of oracle mysql subcomponent connector j supported versions that are affected are and earlier difficult to exploit vulnerability allows low privileged attacker with network access via multiple protocols to compromise mysql connectors while the vulnerability is in mysql connectors attacks may significantly impact additional products successful attacks of this vulnerability can result in takeover of mysql connectors cvss base score confidentiality integrity and availability impacts cvss vector cvss av n ac h pr l ui n s c c h i h a h publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity high privileges required low user interaction none scope changed impact metrics confidentiality impact high integrity impact high availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution rescue worker helmet automatic remediation is available for this issue isopenpronvulnerability true ispackagebased true isdefaultbranch true packages vulnerabilityidentifier cve vulnerabilitydetails vulnerability in the mysql connectors component of oracle mysql subcomponent connector j supported versions that are affected are and earlier difficult to exploit vulnerability allows low privileged attacker with network access via multiple protocols to compromise mysql connectors while the vulnerability is in mysql connectors attacks may significantly impact additional products successful attacks of this vulnerability can result in takeover of mysql connectors cvss base score confidentiality integrity and availability impacts cvss vector cvss av n ac h pr l ui n s c c h i h a h vulnerabilityurl

IssuesEvent

2021-08-19 01:06:37

jtimberlake/rl-bakery

https://api.github.com/repos/jtimberlake/rl-bakery

opened

CVE-2021-37686 (Medium) detected in tensorflow-2.0.0-cp37-cp37m-manylinux2010_x86_64.whl

security vulnerability

## CVE-2021-37686 - Medium Severity Vulnerability <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>tensorflow-2.0.0-cp37-cp37m-manylinux2010_x86_64.whl</b></p></summary> <p>TensorFlow is an open source machine learning framework for everyone.</p> <p>Library home page: <a href="https://files.pythonhosted.org/packages/2a/5c/f1d66de5dde6f3ff528f6ea1fd0757a0e594d17debb3ec7f82daa967ea9a/tensorflow-2.0.0-cp37-cp37m-manylinux2010_x86_64.whl">https://files.pythonhosted.org/packages/2a/5c/f1d66de5dde6f3ff528f6ea1fd0757a0e594d17debb3ec7f82daa967ea9a/tensorflow-2.0.0-cp37-cp37m-manylinux2010_x86_64.whl</a></p> <p>Path to dependency file: rl-bakery/requirements.txt</p> <p>Path to vulnerable library: rl-bakery/requirements.txt,rl-bakery</p> <p> Dependency Hierarchy: - :x: **tensorflow-2.0.0-cp37-cp37m-manylinux2010_x86_64.whl** (Vulnerable Library) <p>Found in base branch: <b>master</b></p> </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary> <p> TensorFlow is an end-to-end open source platform for machine learning. In affected versions the strided slice implementation in TFLite has a logic bug which can allow an attacker to trigger an infinite loop. This arises from newly introduced support for [ellipsis in axis definition](https://github.com/tensorflow/tensorflow/blob/149562d49faa709ea80df1d99fc41d005b81082a/tensorflow/lite/kernels/strided_slice.cc#L103-L122). An attacker can craft a model such that `ellipsis_end_idx` is smaller than `i` (e.g., always negative). In this case, the inner loop does not increase `i` and the `continue` statement causes execution to skip over the preincrement at the end of the outer loop. We have patched the issue in GitHub commit dfa22b348b70bb89d6d6ec0ff53973bacb4f4695. TensorFlow 2.6.0 is the only affected version. <p>Publish Date: 2021-08-12 <p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-37686>CVE-2021-37686</a></p> </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.5</b>)</summary> <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Local - Attack Complexity: Low - Privileges Required: Low - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: None - Integrity Impact: None - Availability Impact: High </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary> <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://github.com/tensorflow/tensorflow/security/advisories/GHSA-mhhc-q96p-mfm9">https://github.com/tensorflow/tensorflow/security/advisories/GHSA-mhhc-q96p-mfm9</a></p> <p>Release Date: 2021-08-12</p> <p>Fix Resolution: tensorflow - 2.6.0, tensorflow-cpu - 2.6.0, tensorflow-gpu - 2.6.0</p> </p> </details> <p></p> *** <!-- REMEDIATE-OPEN-PR-START --> - [ ] Check this box to open an automated fix PR <!-- REMEDIATE-OPEN-PR-END --> <!-- <REMEDIATE>{"isOpenPROnVulnerability":false,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"Python","packageName":"tensorflow","packageVersion":"2.0.0","packageFilePaths":["/requirements.txt","rl-bakery"],"isTransitiveDependency":false,"dependencyTree":"tensorflow:2.0.0","isMinimumFixVersionAvailable":true,"minimumFixVersion":"tensorflow - 2.6.0, tensorflow-cpu - 2.6.0, tensorflow-gpu - 2.6.0"}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2021-37686","vulnerabilityDetails":"TensorFlow is an end-to-end open source platform for machine learning. In affected versions the strided slice implementation in TFLite has a logic bug which can allow an attacker to trigger an infinite loop. This arises from newly introduced support for [ellipsis in axis definition](https://github.com/tensorflow/tensorflow/blob/149562d49faa709ea80df1d99fc41d005b81082a/tensorflow/lite/kernels/strided_slice.cc#L103-L122). An attacker can craft a model such that `ellipsis_end_idx` is smaller than `i` (e.g., always negative). In this case, the inner loop does not increase `i` and the `continue` statement causes execution to skip over the preincrement at the end of the outer loop. We have patched the issue in GitHub commit dfa22b348b70bb89d6d6ec0ff53973bacb4f4695. TensorFlow 2.6.0 is the only affected version.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-37686","cvss3Severity":"medium","cvss3Score":"5.5","cvss3Metrics":{"A":"High","AC":"Low","PR":"Low","S":"Unchanged","C":"None","UI":"None","AV":"Local","I":"None"},"extraData":{}}</REMEDIATE> -->

True

CVE-2021-37686 (Medium) detected in tensorflow-2.0.0-cp37-cp37m-manylinux2010_x86_64.whl - ## CVE-2021-37686 - Medium Severity Vulnerability <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>tensorflow-2.0.0-cp37-cp37m-manylinux2010_x86_64.whl</b></p></summary> <p>TensorFlow is an open source machine learning framework for everyone.</p> <p>Library home page: <a href="https://files.pythonhosted.org/packages/2a/5c/f1d66de5dde6f3ff528f6ea1fd0757a0e594d17debb3ec7f82daa967ea9a/tensorflow-2.0.0-cp37-cp37m-manylinux2010_x86_64.whl">https://files.pythonhosted.org/packages/2a/5c/f1d66de5dde6f3ff528f6ea1fd0757a0e594d17debb3ec7f82daa967ea9a/tensorflow-2.0.0-cp37-cp37m-manylinux2010_x86_64.whl</a></p> <p>Path to dependency file: rl-bakery/requirements.txt</p> <p>Path to vulnerable library: rl-bakery/requirements.txt,rl-bakery</p> <p> Dependency Hierarchy: - :x: **tensorflow-2.0.0-cp37-cp37m-manylinux2010_x86_64.whl** (Vulnerable Library) <p>Found in base branch: <b>master</b></p> </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary> <p> TensorFlow is an end-to-end open source platform for machine learning. In affected versions the strided slice implementation in TFLite has a logic bug which can allow an attacker to trigger an infinite loop. This arises from newly introduced support for [ellipsis in axis definition](https://github.com/tensorflow/tensorflow/blob/149562d49faa709ea80df1d99fc41d005b81082a/tensorflow/lite/kernels/strided_slice.cc#L103-L122). An attacker can craft a model such that `ellipsis_end_idx` is smaller than `i` (e.g., always negative). In this case, the inner loop does not increase `i` and the `continue` statement causes execution to skip over the preincrement at the end of the outer loop. We have patched the issue in GitHub commit dfa22b348b70bb89d6d6ec0ff53973bacb4f4695. TensorFlow 2.6.0 is the only affected version. <p>Publish Date: 2021-08-12 <p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-37686>CVE-2021-37686</a></p> </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.5</b>)</summary> <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Local - Attack Complexity: Low - Privileges Required: Low - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: None - Integrity Impact: None - Availability Impact: High </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary> <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://github.com/tensorflow/tensorflow/security/advisories/GHSA-mhhc-q96p-mfm9">https://github.com/tensorflow/tensorflow/security/advisories/GHSA-mhhc-q96p-mfm9</a></p> <p>Release Date: 2021-08-12</p> <p>Fix Resolution: tensorflow - 2.6.0, tensorflow-cpu - 2.6.0, tensorflow-gpu - 2.6.0</p> </p> </details> <p></p> *** <!-- REMEDIATE-OPEN-PR-START --> - [ ] Check this box to open an automated fix PR <!-- REMEDIATE-OPEN-PR-END --> <!-- <REMEDIATE>{"isOpenPROnVulnerability":false,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"Python","packageName":"tensorflow","packageVersion":"2.0.0","packageFilePaths":["/requirements.txt","rl-bakery"],"isTransitiveDependency":false,"dependencyTree":"tensorflow:2.0.0","isMinimumFixVersionAvailable":true,"minimumFixVersion":"tensorflow - 2.6.0, tensorflow-cpu - 2.6.0, tensorflow-gpu - 2.6.0"}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2021-37686","vulnerabilityDetails":"TensorFlow is an end-to-end open source platform for machine learning. In affected versions the strided slice implementation in TFLite has a logic bug which can allow an attacker to trigger an infinite loop. This arises from newly introduced support for [ellipsis in axis definition](https://github.com/tensorflow/tensorflow/blob/149562d49faa709ea80df1d99fc41d005b81082a/tensorflow/lite/kernels/strided_slice.cc#L103-L122). An attacker can craft a model such that `ellipsis_end_idx` is smaller than `i` (e.g., always negative). In this case, the inner loop does not increase `i` and the `continue` statement causes execution to skip over the preincrement at the end of the outer loop. We have patched the issue in GitHub commit dfa22b348b70bb89d6d6ec0ff53973bacb4f4695. TensorFlow 2.6.0 is the only affected version.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-37686","cvss3Severity":"medium","cvss3Score":"5.5","cvss3Metrics":{"A":"High","AC":"Low","PR":"Low","S":"Unchanged","C":"None","UI":"None","AV":"Local","I":"None"},"extraData":{}}</REMEDIATE> -->

non_priority

cve medium detected in tensorflow whl cve medium severity vulnerability vulnerable library tensorflow whl tensorflow is an open source machine learning framework for everyone library home page a href path to dependency file rl bakery requirements txt path to vulnerable library rl bakery requirements txt rl bakery dependency hierarchy x tensorflow whl vulnerable library found in base branch master vulnerability details tensorflow is an end to end open source platform for machine learning in affected versions the strided slice implementation in tflite has a logic bug which can allow an attacker to trigger an infinite loop this arises from newly introduced support for an attacker can craft a model such that ellipsis end idx is smaller than i e g always negative in this case the inner loop does not increase i and the continue statement causes execution to skip over the preincrement at the end of the outer loop we have patched the issue in github commit tensorflow is the only affected version publish date url a href cvss score details base score metrics exploitability metrics attack vector local attack complexity low privileges required low user interaction none scope unchanged impact metrics confidentiality impact none integrity impact none availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution tensorflow tensorflow cpu tensorflow gpu check this box to open an automated fix pr isopenpronvulnerability false ispackagebased true isdefaultbranch true packages istransitivedependency false dependencytree tensorflow isminimumfixversionavailable true minimumfixversion tensorflow tensorflow cpu tensorflow gpu basebranches vulnerabilityidentifier cve vulnerabilitydetails tensorflow is an end to end open source platform for machine learning in affected versions the strided slice implementation in tflite has a logic bug which can allow an attacker to trigger an infinite loop this arises from newly introduced support for an attacker can craft a model such that ellipsis end idx is smaller than i e g always negative in this case the inner loop does not increase i and the continue statement causes execution to skip over the preincrement at the end of the outer loop we have patched the issue in github commit tensorflow is the only affected version vulnerabilityurl

IssuesEvent

2022-08-19 14:02:58

microsoft/vscode

https://api.github.com/repos/microsoft/vscode

opened

Can open an ipynb notebook

integration-test-failure

``` 1) ipynb NotebookSerializer Can open an ipynb notebook: Error: Timeout of 60000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves. (/Users/runner/work/1/s/extensions/vscode-api-tests/out/singlefolder-tests/ipynb.test.js) at listOnTimeout (node:internal/timers:559:17) at processTimers (node:internal/timers:502:7) ``` https://dev.azure.com/monacotools/Monaco/_build/results?buildId=182486&view=logs&j=9833cdaa-2e92-5f8d-56a8-239fd18fd628&t=9bc48eac-eb66-52c8-7250-d6490c5f3a15&l=608

1.0

Can open an ipynb notebook - ``` 1) ipynb NotebookSerializer Can open an ipynb notebook: Error: Timeout of 60000ms exceeded. For async tests and hooks, ensure "done()" is called; if returning a Promise, ensure it resolves. (/Users/runner/work/1/s/extensions/vscode-api-tests/out/singlefolder-tests/ipynb.test.js) at listOnTimeout (node:internal/timers:559:17) at processTimers (node:internal/timers:502:7) ``` https://dev.azure.com/monacotools/Monaco/_build/results?buildId=182486&view=logs&j=9833cdaa-2e92-5f8d-56a8-239fd18fd628&t=9bc48eac-eb66-52c8-7250-d6490c5f3a15&l=608

non_priority

can open an ipynb notebook ipynb notebookserializer can open an ipynb notebook error timeout of exceeded for async tests and hooks ensure done is called if returning a promise ensure it resolves users runner work s extensions vscode api tests out singlefolder tests ipynb test js at listontimeout node internal timers at processtimers node internal timers

IssuesEvent

2022-12-22 17:39:38

aws/aws-sam-cli

https://api.github.com/repos/aws/aws-sam-cli

closed

Building functions that require native libraries to be present

type/feature area/build

### Describe your idea/feature/enhancement A number of the lambda languages have facilities for linking to C libraries for runtime performance. Ruby makes very heavy use of this, but it's not uncommon to see in Python or NodeJS as well. Even java is capable of it, though it's not all that common. For example, in Ruby if you want to talk to a mysql database, you use a gem called mysql2 that expects to link against libmysqlclient.so. A layer is the natural place to store this .so file (rather than package it with your function code), but this doesn't solve the issue of having the development headers available at function build time. ### Proposal Provide a mechanism for injecting build-time dependencies into a build container as part of the sam build process so that native libraries can be compiled. Ideally this would also spit out a lambda layer with the runtime support libraries necessary for the function to actually run. Things to consider: 1. This would likely require either an addition to the SAM spec or some type of buildspec file to specify what extra libraries are needed. 2. If we are generating a layer automatically, the transform (or possibly the CLI) would need to replace a ref to the lambda layer with the actual ARN of the dynamically created layer. ### Additional Details I've recorded my work on this and posted a Dockerfile and a couple scripts that I'm using to do this manually outside of the sam build process now. I don't consider this to be a final solution or even necessarily a valid approach. It does demonstrate part of the problem I'm facing though. https://github.com/jasonmk/lambda-gem-compiler

1.0

Building functions that require native libraries to be present - ### Describe your idea/feature/enhancement A number of the lambda languages have facilities for linking to C libraries for runtime performance. Ruby makes very heavy use of this, but it's not uncommon to see in Python or NodeJS as well. Even java is capable of it, though it's not all that common. For example, in Ruby if you want to talk to a mysql database, you use a gem called mysql2 that expects to link against libmysqlclient.so. A layer is the natural place to store this .so file (rather than package it with your function code), but this doesn't solve the issue of having the development headers available at function build time. ### Proposal Provide a mechanism for injecting build-time dependencies into a build container as part of the sam build process so that native libraries can be compiled. Ideally this would also spit out a lambda layer with the runtime support libraries necessary for the function to actually run. Things to consider: 1. This would likely require either an addition to the SAM spec or some type of buildspec file to specify what extra libraries are needed. 2. If we are generating a layer automatically, the transform (or possibly the CLI) would need to replace a ref to the lambda layer with the actual ARN of the dynamically created layer. ### Additional Details I've recorded my work on this and posted a Dockerfile and a couple scripts that I'm using to do this manually outside of the sam build process now. I don't consider this to be a final solution or even necessarily a valid approach. It does demonstrate part of the problem I'm facing though. https://github.com/jasonmk/lambda-gem-compiler

non_priority

building functions that require native libraries to be present describe your idea feature enhancement a number of the lambda languages have facilities for linking to c libraries for runtime performance ruby makes very heavy use of this but it s not uncommon to see in python or nodejs as well even java is capable of it though it s not all that common for example in ruby if you want to talk to a mysql database you use a gem called that expects to link against libmysqlclient so a layer is the natural place to store this so file rather than package it with your function code but this doesn t solve the issue of having the development headers available at function build time proposal provide a mechanism for injecting build time dependencies into a build container as part of the sam build process so that native libraries can be compiled ideally this would also spit out a lambda layer with the runtime support libraries necessary for the function to actually run things to consider this would likely require either an addition to the sam spec or some type of buildspec file to specify what extra libraries are needed if we are generating a layer automatically the transform or possibly the cli would need to replace a ref to the lambda layer with the actual arn of the dynamically created layer additional details i ve recorded my work on this and posted a dockerfile and a couple scripts that i m using to do this manually outside of the sam build process now i don t consider this to be a final solution or even necessarily a valid approach it does demonstrate part of the problem i m facing though

IssuesEvent

2021-03-25 01:02:34

Mohib-hub/jwala

https://api.github.com/repos/Mohib-hub/jwala

opened

CVE-2021-21344 (Medium) detected in xstream-1.4.7.jar

security vulnerability

## CVE-2021-21344 - Medium Severity Vulnerability <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>xstream-1.4.7.jar</b></p></summary> <p>XStream is a serialization library from Java objects to XML and back.</p> <p>Path to vulnerable library: jwala/jwala-services/src/test/resources/get-resource-mime-type-test-files/war/WEB-INF/lib/xstream-1.4.7.jar</p> <p> Dependency Hierarchy: - :x: **xstream-1.4.7.jar** (Vulnerable Library) </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary> <p> XStream is a Java library to serialize objects to XML and back again. In XStream before version 1.4.16, there is a vulnerability which may allow a remote attacker to load and execute arbitrary code from a remote host only by manipulating the processed input stream. No user is affected, who followed the recommendation to setup XStream's security framework with a whitelist limited to the minimal required types. If you rely on XStream's default blacklist of the Security Framework, you will have to use at least version 1.4.16. <p>Publish Date: 2021-03-23 <p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-21344>CVE-2021-21344</a></p> </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.3</b>)</summary> <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: High - Privileges Required: None - User Interaction: Required - 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/x-stream/xstream/security/advisories/GHSA-59jw-jqf4-3wq3">https://github.com/x-stream/xstream/security/advisories/GHSA-59jw-jqf4-3wq3</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.7","packageFilePaths":[],"isTransitiveDependency":false,"dependencyTree":"com.thoughtworks.xstream:xstream:1.4.7","isMinimumFixVersionAvailable":true,"minimumFixVersion":"com.thoughtworks.xstream:xstream:1.4.16"}],"baseBranches":[],"vulnerabilityIdentifier":"CVE-2021-21344","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 which may allow a remote attacker to load and execute arbitrary code from a remote host only by manipulating the processed input stream. 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-21344","cvss3Severity":"medium","cvss3Score":"5.3","cvss3Metrics":{"A":"None","AC":"High","PR":"None","S":"Unchanged","C":"None","UI":"Required","AV":"Network","I":"High"},"extraData":{}}</REMEDIATE> -->

True

CVE-2021-21344 (Medium) detected in xstream-1.4.7.jar - ## CVE-2021-21344 - Medium Severity Vulnerability <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>xstream-1.4.7.jar</b></p></summary> <p>XStream is a serialization library from Java objects to XML and back.</p> <p>Path to vulnerable library: jwala/jwala-services/src/test/resources/get-resource-mime-type-test-files/war/WEB-INF/lib/xstream-1.4.7.jar</p> <p> Dependency Hierarchy: - :x: **xstream-1.4.7.jar** (Vulnerable Library) </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary> <p> XStream is a Java library to serialize objects to XML and back again. In XStream before version 1.4.16, there is a vulnerability which may allow a remote attacker to load and execute arbitrary code from a remote host only by manipulating the processed input stream. No user is affected, who followed the recommendation to setup XStream's security framework with a whitelist limited to the minimal required types. If you rely on XStream's default blacklist of the Security Framework, you will have to use at least version 1.4.16. <p>Publish Date: 2021-03-23 <p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-21344>CVE-2021-21344</a></p> </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.3</b>)</summary> <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: High - Privileges Required: None - User Interaction: Required - 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/x-stream/xstream/security/advisories/GHSA-59jw-jqf4-3wq3">https://github.com/x-stream/xstream/security/advisories/GHSA-59jw-jqf4-3wq3</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.7","packageFilePaths":[],"isTransitiveDependency":false,"dependencyTree":"com.thoughtworks.xstream:xstream:1.4.7","isMinimumFixVersionAvailable":true,"minimumFixVersion":"com.thoughtworks.xstream:xstream:1.4.16"}],"baseBranches":[],"vulnerabilityIdentifier":"CVE-2021-21344","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 which may allow a remote attacker to load and execute arbitrary code from a remote host only by manipulating the processed input stream. 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-21344","cvss3Severity":"medium","cvss3Score":"5.3","cvss3Metrics":{"A":"None","AC":"High","PR":"None","S":"Unchanged","C":"None","UI":"Required","AV":"Network","I":"High"},"extraData":{}}</REMEDIATE> -->

non_priority

cve medium detected in xstream jar cve medium severity vulnerability vulnerable library xstream jar xstream is a serialization library from java objects to xml and back path to vulnerable library jwala jwala services src test resources get resource mime type test files war web inf lib xstream jar dependency hierarchy x xstream jar vulnerable library vulnerability details xstream is a java library to serialize objects to xml and back again in xstream before version there is a vulnerability which may allow a remote attacker to load and execute arbitrary code from a remote host only by manipulating the processed input stream no user is affected who followed the recommendation to setup xstream s security framework with a whitelist limited to the minimal required types if you rely on xstream s default blacklist of the security framework you will have to use at least version publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity high privileges required none user interaction required 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 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 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 which may allow a remote attacker to load and execute arbitrary code from a remote host only by manipulating the processed input stream 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

IssuesEvent

2022-03-07 16:59:35

Baneeishaque/Gym_Class_Accounter

https://api.github.com/repos/Baneeishaque/Gym_Class_Accounter

opened

CVE-2018-10237 (Medium) detected in guava-24.0-jre.jar

security vulnerability

## CVE-2018-10237 - Medium Severity Vulnerability <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>guava-24.0-jre.jar</b></p></summary> <p>Guava is a suite of core and expanded libraries that include utility classes, google's collections, io classes, and much much more.</p> <p>Library home page: <a href="https://github.com/google/guava">https://github.com/google/guava</a></p> <p>Path to dependency file: /app/build.gradle</p> <p>Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/com.google.guava/guava/24.0-jre/41ac1e74d6b4e1ea1f027139cffeb536c732a81/guava-24.0-jre.jar</p> <p> Dependency Hierarchy: - butterknife-compiler-9.0.0.jar (Root Library) - :x: **guava-24.0-jre.jar** (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/Baneeishaque/Gym_Class_Accounter/commit/d0b484ab35339c58b68f75b5f03b3958d80ce307">d0b484ab35339c58b68f75b5f03b3958d80ce307</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> Unbounded memory allocation in Google Guava 11.0 through 24.x before 24.1.1 allows remote attackers to conduct denial of service attacks against servers that depend on this library and deserialize attacker-provided data, because the AtomicDoubleArray class (when serialized with Java serialization) and the CompoundOrdering class (when serialized with GWT serialization) perform eager allocation without appropriate checks on what a client has sent and whether the data size is reasonable. <p>Publish Date: 2018-04-26 <p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-10237>CVE-2018-10237</a></p> </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.9</b>)</summary> <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: High - Privileges Required: None - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: None - Integrity Impact: None - Availability Impact: High </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary> <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://nvd.nist.gov/vuln/detail/CVE-2018-10237">https://nvd.nist.gov/vuln/detail/CVE-2018-10237</a></p> <p>Release Date: 2018-04-26</p> <p>Fix Resolution: 24.1.1-jre, 24.1.1-android</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-10237 (Medium) detected in guava-24.0-jre.jar - ## CVE-2018-10237 - Medium Severity Vulnerability <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>guava-24.0-jre.jar</b></p></summary> <p>Guava is a suite of core and expanded libraries that include utility classes, google's collections, io classes, and much much more.</p> <p>Library home page: <a href="https://github.com/google/guava">https://github.com/google/guava</a></p> <p>Path to dependency file: /app/build.gradle</p> <p>Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/com.google.guava/guava/24.0-jre/41ac1e74d6b4e1ea1f027139cffeb536c732a81/guava-24.0-jre.jar</p> <p> Dependency Hierarchy: - butterknife-compiler-9.0.0.jar (Root Library) - :x: **guava-24.0-jre.jar** (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/Baneeishaque/Gym_Class_Accounter/commit/d0b484ab35339c58b68f75b5f03b3958d80ce307">d0b484ab35339c58b68f75b5f03b3958d80ce307</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> Unbounded memory allocation in Google Guava 11.0 through 24.x before 24.1.1 allows remote attackers to conduct denial of service attacks against servers that depend on this library and deserialize attacker-provided data, because the AtomicDoubleArray class (when serialized with Java serialization) and the CompoundOrdering class (when serialized with GWT serialization) perform eager allocation without appropriate checks on what a client has sent and whether the data size is reasonable. <p>Publish Date: 2018-04-26 <p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-10237>CVE-2018-10237</a></p> </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.9</b>)</summary> <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: High - Privileges Required: None - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: None - Integrity Impact: None - Availability Impact: High </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary> <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://nvd.nist.gov/vuln/detail/CVE-2018-10237">https://nvd.nist.gov/vuln/detail/CVE-2018-10237</a></p> <p>Release Date: 2018-04-26</p> <p>Fix Resolution: 24.1.1-jre, 24.1.1-android</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 guava jre jar cve medium severity vulnerability vulnerable library guava jre jar guava is a suite of core and expanded libraries that include utility classes google s collections io classes and much much more library home page a href path to dependency file app build gradle path to vulnerable library home wss scanner gradle caches modules files com google guava guava jre guava jre jar dependency hierarchy butterknife compiler jar root library x guava jre jar vulnerable library found in head commit a href vulnerability details unbounded memory allocation in google guava through x before allows remote attackers to conduct denial of service attacks against servers that depend on this library and deserialize attacker provided data because the atomicdoublearray class when serialized with java serialization and the compoundordering class when serialized with gwt serialization perform eager allocation without appropriate checks on what a client has sent and whether the data size is reasonable publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity high privileges required none user interaction none scope unchanged impact metrics confidentiality impact none integrity impact none availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution jre android step up your open source security game with whitesource

IssuesEvent

2022-10-18 21:37:39

envoyproxy/gateway

https://api.github.com/repos/envoyproxy/gateway

closed

User-facing quickstart doc

documentation help wanted

In the RST docs, there should be a user-facing quickstart about how to install Envoy Gateway and route traffic to a sample service. This may be as "simple" as turning `docs/user/QUICKSTART.md` into RST.

1.0

User-facing quickstart doc - In the RST docs, there should be a user-facing quickstart about how to install Envoy Gateway and route traffic to a sample service. This may be as "simple" as turning `docs/user/QUICKSTART.md` into RST.

non_priority

user facing quickstart doc in the rst docs there should be a user facing quickstart about how to install envoy gateway and route traffic to a sample service this may be as simple as turning docs user quickstart md into rst

IssuesEvent

2020-09-24 10:57:16

DS-13-Dev-Team/DS13

https://api.github.com/repos/DS-13-Dev-Team/DS13

closed

Psychosis runtime

Bug Code

runtime error: Cannot execute 16.add pain(). proc name: custom pain (/mob/living/carbon/proc/custom_pain) source file: pain.dm,21 usr: null src: Bluespace Technician (/mob/living/carbon/human/bst) src.loc: the plating (200,65,3) (/turf/simulated/floor/plating) call stack: Bluespace Technician (/mob/living/carbon/human/bst): custom pain("You burst out laughing!", 1, null, 16, null) Psychotic trauma (/datum/extension/psychosis): apply psychosis effects() Psychotic trauma (/datum/extension/psychosis): start psychosis() Bluespace Technician (/mob/living/carbon/human/bst): apply psychosis(6, 5500) Traumatic sight (/datum/extension/traumatic_sight): apply psychosis effects() Traumatic sight (/datum/extension/traumatic_sight): tick() /datum/callback (/datum/callback): InvokeAsync() Timer (/datum/controller/subsystem/timer): fire(0) Timer (/datum/controller/subsystem/timer): ignite(0) Master (/datum/controller/master): RunQueue() Master (/datum/controller/master): Loop() Master (/datum/controller/master): StartProcessing(0) Happened while hanging around a clientless leaper.

1.0

Psychosis runtime - runtime error: Cannot execute 16.add pain(). proc name: custom pain (/mob/living/carbon/proc/custom_pain) source file: pain.dm,21 usr: null src: Bluespace Technician (/mob/living/carbon/human/bst) src.loc: the plating (200,65,3) (/turf/simulated/floor/plating) call stack: Bluespace Technician (/mob/living/carbon/human/bst): custom pain("You burst out laughing!", 1, null, 16, null) Psychotic trauma (/datum/extension/psychosis): apply psychosis effects() Psychotic trauma (/datum/extension/psychosis): start psychosis() Bluespace Technician (/mob/living/carbon/human/bst): apply psychosis(6, 5500) Traumatic sight (/datum/extension/traumatic_sight): apply psychosis effects() Traumatic sight (/datum/extension/traumatic_sight): tick() /datum/callback (/datum/callback): InvokeAsync() Timer (/datum/controller/subsystem/timer): fire(0) Timer (/datum/controller/subsystem/timer): ignite(0) Master (/datum/controller/master): RunQueue() Master (/datum/controller/master): Loop() Master (/datum/controller/master): StartProcessing(0) Happened while hanging around a clientless leaper.

non_priority

psychosis runtime runtime error cannot execute add pain proc name custom pain mob living carbon proc custom pain source file pain dm usr null src bluespace technician mob living carbon human bst src loc the plating turf simulated floor plating call stack bluespace technician mob living carbon human bst custom pain you burst out laughing null null psychotic trauma datum extension psychosis apply psychosis effects psychotic trauma datum extension psychosis start psychosis bluespace technician mob living carbon human bst apply psychosis traumatic sight datum extension traumatic sight apply psychosis effects traumatic sight datum extension traumatic sight tick datum callback datum callback invokeasync timer datum controller subsystem timer fire timer datum controller subsystem timer ignite master datum controller master runqueue master datum controller master loop master datum controller master startprocessing happened while hanging around a clientless leaper

IssuesEvent

2023-06-29 01:10:24

amaybaum-prod/EasyBuggy2

https://api.github.com/repos/amaybaum-prod/EasyBuggy2

opened

mysql-connector-java-5.1.25.jar: 9 vulnerabilities (highest severity is: 8.5) non-reachable

Mend: dependency security vulnerability

<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>mysql-connector-java-5.1.25.jar</b></p></summary> <p>MySQL JDBC Type 4 driver</p> <p>Library home page: <a href="http://dev.mysql.com/doc/connector-j/en/">http://dev.mysql.com/doc/connector-j/en/</a></p> <p>Path to dependency file: /pom.xml</p> <p>Path to vulnerable library: /target/easybuggy-1-SNAPSHOT/WEB-INF/lib/mysql-connector-java-5.1.25.jar,/home/wss-scanner/.m2/repository/mysql/mysql-connector-java/5.1.25/mysql-connector-java-5.1.25.jar</p> <p> </details> ## Vulnerabilities | CVE | Severity | <img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS | Dependency | Type | Fixed in (mysql-connector-java version) | Remediation Available | Reachability | | ------------- | ------------- | ----- | ----- | ----- | ------------- | --- | --- | | [CVE-2017-3523](https://www.mend.io/vulnerability-database/CVE-2017-3523) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 8.5 | mysql-connector-java-5.1.25.jar | Direct | 5.1.41 | &#9989;|<p align="center"><a href="#">[<img src='https://whitesource-resources.whitesourcesoftware.com/viaGreen.png' width=19 height=20>](## 'The vulnerability is non-reachable.')</a></p> | | [CVE-2022-21363](https://www.mend.io/vulnerability-database/CVE-2022-21363) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> Medium | 6.6 | mysql-connector-java-5.1.25.jar | Direct | mysql:mysql-connector-java:8.0.28 | &#9989;|<p align="center"><a href="#">[<img src='https://whitesource-resources.whitesourcesoftware.com/viaGreen.png' width=19 height=20>](## 'The vulnerability is non-reachable.')</a></p> | | [CVE-2017-3586](https://www.mend.io/vulnerability-database/CVE-2017-3586) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> Medium | 6.4 | mysql-connector-java-5.1.25.jar | Direct | 5.1.42 | &#9989;|<p align="center"><a href="#">[<img src='https://whitesource-resources.whitesourcesoftware.com/viaGreen.png' width=19 height=20>](## 'The vulnerability is non-reachable.')</a></p> | | [CVE-2019-2692](https://www.mend.io/vulnerability-database/CVE-2019-2692) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> Medium | 6.3 | mysql-connector-java-5.1.25.jar | Direct | 5.1.48 | &#9989;|<p align="center"><a href="#">[<img src='https://whitesource-resources.whitesourcesoftware.com/viaGreen.png' width=19 height=20>](## 'The vulnerability is non-reachable.')</a></p> | | [CVE-2020-2934](https://www.mend.io/vulnerability-database/CVE-2020-2934) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> Medium | 5.0 | mysql-connector-java-5.1.25.jar | Direct | 5.1.49 | &#9989;|<p align="center"><a href="#">[<img src='https://whitesource-resources.whitesourcesoftware.com/viaGreen.png' width=19 height=20>](## 'The vulnerability is non-reachable.')</a></p> | | [CVE-2020-2875](https://www.mend.io/vulnerability-database/CVE-2020-2875) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> Medium | 4.7 | mysql-connector-java-5.1.25.jar | Direct | 5.1.49 | &#9989;|<p align="center"><a href="#">[<img src='https://whitesource-resources.whitesourcesoftware.com/viaGreen.png' width=19 height=20>](## 'The vulnerability is non-reachable.')</a></p> | | [CVE-2015-2575](https://www.mend.io/vulnerability-database/CVE-2015-2575) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> Medium | 4.2 | mysql-connector-java-5.1.25.jar | Direct | 5.1.35 | &#9989;|<p align="center"><a href="#">[<img src='https://whitesource-resources.whitesourcesoftware.com/viaGreen.png' width=19 height=20>](## 'The vulnerability is non-reachable.')</a></p> | | [CVE-2017-3589](https://www.mend.io/vulnerability-database/CVE-2017-3589) | <img src='https://whitesource-resources.whitesourcesoftware.com/low_vul.png?' width=19 height=20> Low | 3.3 | mysql-connector-java-5.1.25.jar | Direct | 5.1.42 | &#9989;|<p align="center"><a href="#">[<img src='https://whitesource-resources.whitesourcesoftware.com/viaGreen.png' width=19 height=20>](## 'The vulnerability is non-reachable.')</a></p> | | [CVE-2020-2933](https://www.mend.io/vulnerability-database/CVE-2020-2933) | <img src='https://whitesource-resources.whitesourcesoftware.com/low_vul.png?' width=19 height=20> Low | 2.2 | mysql-connector-java-5.1.25.jar | Direct | 5.1.49 | &#9989;|<p align="center"><a href="#">[<img src='https://whitesource-resources.whitesourcesoftware.com/viaGreen.png' width=19 height=20>](## 'The vulnerability is non-reachable.')</a></p> | ## Details <details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> <img src='https://whitesource-resources.whitesourcesoftware.com/viaGreen.png' width=19 height=20> CVE-2017-3523</summary> ### Vulnerable Library - <b>mysql-connector-java-5.1.25.jar</b></p> <p>MySQL JDBC Type 4 driver</p> <p>Library home page: <a href="http://dev.mysql.com/doc/connector-j/en/">http://dev.mysql.com/doc/connector-j/en/</a></p> <p>Path to dependency file: /pom.xml</p> <p>Path to vulnerable library: /target/easybuggy-1-SNAPSHOT/WEB-INF/lib/mysql-connector-java-5.1.25.jar,/home/wss-scanner/.m2/repository/mysql/mysql-connector-java/5.1.25/mysql-connector-java-5.1.25.jar</p> <p> Dependency Hierarchy: - :x: **mysql-connector-java-5.1.25.jar** (Vulnerable Library) <p>Found in base branch: <b>master</b></p> </p> <p></p> ### Reachability Analysis <p> <p>The vulnerable code is not reachable.</p> </p> <p></p> ### Vulnerability Details <p> Vulnerability in the MySQL Connectors component of Oracle MySQL (subcomponent: Connector/J). Supported versions that are affected are 5.1.40 and earlier. Difficult to exploit vulnerability allows low privileged attacker with network access via multiple protocols to compromise MySQL Connectors. While the vulnerability is in MySQL Connectors, attacks may significantly impact additional products. Successful attacks of this vulnerability can result in takeover of MySQL Connectors. CVSS 3.0 Base Score 8.5 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H). <p>Publish Date: 2017-04-24 <p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2017-3523>CVE-2017-3523</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>8.5</b>) <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: High - Privileges Required: Low - User Interaction: None - Scope: Changed - Impact Metrics: - Confidentiality Impact: High - Integrity Impact: High - Availability Impact: High </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> <p></p> ### Suggested Fix <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://github.com/advisories/GHSA-2xxh-f8r3-hvvr">https://github.com/advisories/GHSA-2xxh-f8r3-hvvr</a></p> <p>Release Date: 2017-04-24</p> <p>Fix Resolution: 5.1.41</p> </p> <p></p> :rescue_worker_helmet: Automatic Remediation is available for this issue </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> <img src='https://whitesource-resources.whitesourcesoftware.com/viaGreen.png' width=19 height=20> CVE-2022-21363</summary> ### Vulnerable Library - <b>mysql-connector-java-5.1.25.jar</b></p> <p>MySQL JDBC Type 4 driver</p> <p>Library home page: <a href="http://dev.mysql.com/doc/connector-j/en/">http://dev.mysql.com/doc/connector-j/en/</a></p> <p>Path to dependency file: /pom.xml</p> <p>Path to vulnerable library: /target/easybuggy-1-SNAPSHOT/WEB-INF/lib/mysql-connector-java-5.1.25.jar,/home/wss-scanner/.m2/repository/mysql/mysql-connector-java/5.1.25/mysql-connector-java-5.1.25.jar</p> <p> Dependency Hierarchy: - :x: **mysql-connector-java-5.1.25.jar** (Vulnerable Library) <p>Found in base branch: <b>master</b></p> </p> <p></p> ### Reachability Analysis <p> <p>The vulnerable code is not reachable.</p> </p> <p></p> ### Vulnerability Details <p> Vulnerability in the MySQL Connectors product of Oracle MySQL (component: Connector/J). Supported versions that are affected are 8.0.27 and prior. Difficult to exploit vulnerability allows high privileged attacker with network access via multiple protocols to compromise MySQL Connectors. Successful attacks of this vulnerability can result in takeover of MySQL Connectors. CVSS 3.1 Base Score 6.6 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H). <p>Publish Date: 2022-01-19 <p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-21363>CVE-2022-21363</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>6.6</b>) <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: High - Privileges Required: High - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: High - Integrity Impact: High - Availability Impact: High </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> <p></p> ### Suggested Fix <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://github.com/advisories/GHSA-g76j-4cxx-23h9">https://github.com/advisories/GHSA-g76j-4cxx-23h9</a></p> <p>Release Date: 2022-01-19</p> <p>Fix Resolution: mysql:mysql-connector-java:8.0.28</p> </p> <p></p> :rescue_worker_helmet: Automatic Remediation is available for this issue </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> <img src='https://whitesource-resources.whitesourcesoftware.com/viaGreen.png' width=19 height=20> CVE-2017-3586</summary> ### Vulnerable Library - <b>mysql-connector-java-5.1.25.jar</b></p> <p>MySQL JDBC Type 4 driver</p> <p>Library home page: <a href="http://dev.mysql.com/doc/connector-j/en/">http://dev.mysql.com/doc/connector-j/en/</a></p> <p>Path to dependency file: /pom.xml</p> <p>Path to vulnerable library: /target/easybuggy-1-SNAPSHOT/WEB-INF/lib/mysql-connector-java-5.1.25.jar,/home/wss-scanner/.m2/repository/mysql/mysql-connector-java/5.1.25/mysql-connector-java-5.1.25.jar</p> <p> Dependency Hierarchy: - :x: **mysql-connector-java-5.1.25.jar** (Vulnerable Library) <p>Found in base branch: <b>master</b></p> </p> <p></p> ### Reachability Analysis <p> <p>The vulnerable code is not reachable.</p> </p> <p></p> ### Vulnerability Details <p> Vulnerability in the MySQL Connectors component of Oracle MySQL (subcomponent: Connector/J). Supported versions that are affected are 5.1.41 and earlier. Easily "exploitable" vulnerability allows low privileged attacker with network access via multiple protocols to compromise MySQL Connectors. While the vulnerability is in MySQL Connectors, attacks may significantly impact additional products. Successful attacks of this vulnerability can result in unauthorized update, insert or delete access to some of MySQL Connectors accessible data as well as unauthorized read access to a subset of MySQL Connectors accessible data. CVSS 3.0 Base Score 6.4 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N). <p>Publish Date: 2017-04-24 <p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2017-3586>CVE-2017-3586</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>6.4</b>) <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: Low - User Interaction: None - Scope: Changed - Impact Metrics: - Confidentiality Impact: Low - Integrity Impact: Low - Availability Impact: None </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> <p></p> ### Suggested Fix <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://bugzilla.redhat.com/show_bug.cgi?id=1444406">https://bugzilla.redhat.com/show_bug.cgi?id=1444406</a></p> <p>Release Date: 2017-04-24</p> <p>Fix Resolution: 5.1.42</p> </p> <p></p> :rescue_worker_helmet: Automatic Remediation is available for this issue </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> <img src='https://whitesource-resources.whitesourcesoftware.com/viaGreen.png' width=19 height=20> CVE-2019-2692</summary> ### Vulnerable Library - <b>mysql-connector-java-5.1.25.jar</b></p> <p>MySQL JDBC Type 4 driver</p> <p>Library home page: <a href="http://dev.mysql.com/doc/connector-j/en/">http://dev.mysql.com/doc/connector-j/en/</a></p> <p>Path to dependency file: /pom.xml</p> <p>Path to vulnerable library: /target/easybuggy-1-SNAPSHOT/WEB-INF/lib/mysql-connector-java-5.1.25.jar,/home/wss-scanner/.m2/repository/mysql/mysql-connector-java/5.1.25/mysql-connector-java-5.1.25.jar</p> <p> Dependency Hierarchy: - :x: **mysql-connector-java-5.1.25.jar** (Vulnerable Library) <p>Found in base branch: <b>master</b></p> </p> <p></p> ### Reachability Analysis <p> <p>The vulnerable code is not reachable.</p> </p> <p></p> ### Vulnerability Details <p> Vulnerability in the MySQL Connectors component of Oracle MySQL (subcomponent: Connector/J). Supported versions that are affected are 8.0.15 and prior. Difficult to exploit vulnerability allows high privileged attacker with logon to the infrastructure where MySQL Connectors executes to compromise MySQL Connectors. Successful attacks require human interaction from a person other than the attacker. Successful attacks of this vulnerability can result in takeover of MySQL Connectors. CVSS 3.0 Base Score 6.3 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.0/AV:L/AC:H/PR:H/UI:R/S:U/C:H/I:H/A:H). <p>Publish Date: 2019-04-23 <p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2019-2692>CVE-2019-2692</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>6.3</b>) <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Local - Attack Complexity: High - Privileges Required: High - User Interaction: Required - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: High - Integrity Impact: High - Availability Impact: High </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> <p></p> ### Suggested Fix <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://github.com/advisories/GHSA-jcq3-cprp-m333">https://github.com/advisories/GHSA-jcq3-cprp-m333</a></p> <p>Release Date: 2019-04-23</p> <p>Fix Resolution: 5.1.48</p> </p> <p></p> :rescue_worker_helmet: Automatic Remediation is available for this issue </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> <img src='https://whitesource-resources.whitesourcesoftware.com/viaGreen.png' width=19 height=20> CVE-2020-2934</summary> ### Vulnerable Library - <b>mysql-connector-java-5.1.25.jar</b></p> <p>MySQL JDBC Type 4 driver</p> <p>Library home page: <a href="http://dev.mysql.com/doc/connector-j/en/">http://dev.mysql.com/doc/connector-j/en/</a></p> <p>Path to dependency file: /pom.xml</p> <p>Path to vulnerable library: /target/easybuggy-1-SNAPSHOT/WEB-INF/lib/mysql-connector-java-5.1.25.jar,/home/wss-scanner/.m2/repository/mysql/mysql-connector-java/5.1.25/mysql-connector-java-5.1.25.jar</p> <p> Dependency Hierarchy: - :x: **mysql-connector-java-5.1.25.jar** (Vulnerable Library) <p>Found in base branch: <b>master</b></p> </p> <p></p> ### Reachability Analysis <p> <p>The vulnerable code is not reachable.</p> </p> <p></p> ### Vulnerability Details <p> Vulnerability in the MySQL Connectors product of Oracle MySQL (component: Connector/J). Supported versions that are affected are 8.0.19 and prior and 5.1.48 and prior. Difficult to exploit vulnerability allows unauthenticated attacker with network access via multiple protocols to compromise MySQL Connectors. Successful attacks require human interaction from a person other than the attacker. Successful attacks of this vulnerability can result in unauthorized update, insert or delete access to some of MySQL Connectors accessible data as well as unauthorized read access to a subset of MySQL Connectors accessible data and unauthorized ability to cause a partial denial of service (partial DOS) of MySQL Connectors. CVSS 3.0 Base Score 5.0 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:L). <p>Publish Date: 2020-04-15 <p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2020-2934>CVE-2020-2934</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>5.0</b>) <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: High - Privileges Required: None - User Interaction: Required - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: Low - Integrity Impact: Low - Availability Impact: Low </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> <p></p> ### Suggested Fix <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://www.oracle.com/security-alerts/cpuapr2020.html">https://www.oracle.com/security-alerts/cpuapr2020.html</a></p> <p>Release Date: 2020-04-15</p> <p>Fix Resolution: 5.1.49</p> </p> <p></p> :rescue_worker_helmet: Automatic Remediation is available for this issue </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> <img src='https://whitesource-resources.whitesourcesoftware.com/viaGreen.png' width=19 height=20> CVE-2020-2875</summary> ### Vulnerable Library - <b>mysql-connector-java-5.1.25.jar</b></p> <p>MySQL JDBC Type 4 driver</p> <p>Library home page: <a href="http://dev.mysql.com/doc/connector-j/en/">http://dev.mysql.com/doc/connector-j/en/</a></p> <p>Path to dependency file: /pom.xml</p> <p>Path to vulnerable library: /target/easybuggy-1-SNAPSHOT/WEB-INF/lib/mysql-connector-java-5.1.25.jar,/home/wss-scanner/.m2/repository/mysql/mysql-connector-java/5.1.25/mysql-connector-java-5.1.25.jar</p> <p> Dependency Hierarchy: - :x: **mysql-connector-java-5.1.25.jar** (Vulnerable Library) <p>Found in base branch: <b>master</b></p> </p> <p></p> ### Reachability Analysis <p> <p>The vulnerable code is not reachable.</p> </p> <p></p> ### Vulnerability Details <p> Vulnerability in the MySQL Connectors product of Oracle MySQL (component: Connector/J). Supported versions that are affected are 8.0.14 and prior and 5.1.48 and prior. Difficult to exploit vulnerability allows unauthenticated attacker with network access via multiple protocols to compromise MySQL Connectors. Successful attacks require human interaction from a person other than the attacker and while the vulnerability is in MySQL Connectors, attacks may significantly impact additional products. Successful attacks of this vulnerability can result in unauthorized update, insert or delete access to some of MySQL Connectors accessible data as well as unauthorized read access to a subset of MySQL Connectors accessible data. CVSS 3.0 Base Score 4.7 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:C/C:L/I:L/A:N). <p>Publish Date: 2020-04-15 <p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2020-2875>CVE-2020-2875</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>4.7</b>) <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: High - Privileges Required: None - User Interaction: Required - Scope: Changed - Impact Metrics: - Confidentiality Impact: Low - Integrity Impact: Low - Availability Impact: None </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> <p></p> ### Suggested Fix <p> <p>Type: Upgrade version</p> <p>Release Date: 2020-04-15</p> <p>Fix Resolution: 5.1.49</p> </p> <p></p> :rescue_worker_helmet: Automatic Remediation is available for this issue </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> <img src='https://whitesource-resources.whitesourcesoftware.com/viaGreen.png' width=19 height=20> CVE-2015-2575</summary> ### Vulnerable Library - <b>mysql-connector-java-5.1.25.jar</b></p> <p>MySQL JDBC Type 4 driver</p> <p>Library home page: <a href="http://dev.mysql.com/doc/connector-j/en/">http://dev.mysql.com/doc/connector-j/en/</a></p> <p>Path to dependency file: /pom.xml</p> <p>Path to vulnerable library: /target/easybuggy-1-SNAPSHOT/WEB-INF/lib/mysql-connector-java-5.1.25.jar,/home/wss-scanner/.m2/repository/mysql/mysql-connector-java/5.1.25/mysql-connector-java-5.1.25.jar</p> <p> Dependency Hierarchy: - :x: **mysql-connector-java-5.1.25.jar** (Vulnerable Library) <p>Found in base branch: <b>master</b></p> </p> <p></p> ### Reachability Analysis <p> <p>The vulnerable code is not reachable.</p> </p> <p></p> ### Vulnerability Details <p> Unspecified vulnerability in the MySQL Connectors component in Oracle MySQL 5.1.34 and earlier allows remote authenticated users to affect confidentiality and integrity via unknown vectors related to Connector/J. <p>Publish Date: 2015-04-16 <p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2015-2575>CVE-2015-2575</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>4.2</b>) <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: High - Privileges Required: Low - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: Low - Integrity Impact: Low - Availability Impact: None </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> <p></p> ### Suggested Fix <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://github.com/advisories/GHSA-gc43-g62c-99g2">https://github.com/advisories/GHSA-gc43-g62c-99g2</a></p> <p>Release Date: 2015-04-16</p> <p>Fix Resolution: 5.1.35</p> </p> <p></p> :rescue_worker_helmet: Automatic Remediation is available for this issue </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/low_vul.png?' width=19 height=20> <img src='https://whitesource-resources.whitesourcesoftware.com/viaGreen.png' width=19 height=20> CVE-2017-3589</summary> ### Vulnerable Library - <b>mysql-connector-java-5.1.25.jar</b></p> <p>MySQL JDBC Type 4 driver</p> <p>Library home page: <a href="http://dev.mysql.com/doc/connector-j/en/">http://dev.mysql.com/doc/connector-j/en/</a></p> <p>Path to dependency file: /pom.xml</p> <p>Path to vulnerable library: /target/easybuggy-1-SNAPSHOT/WEB-INF/lib/mysql-connector-java-5.1.25.jar,/home/wss-scanner/.m2/repository/mysql/mysql-connector-java/5.1.25/mysql-connector-java-5.1.25.jar</p> <p> Dependency Hierarchy: - :x: **mysql-connector-java-5.1.25.jar** (Vulnerable Library) <p>Found in base branch: <b>master</b></p> </p> <p></p> ### Reachability Analysis <p> <p>The vulnerable code is not reachable.</p> </p> <p></p> ### Vulnerability Details <p> Vulnerability in the MySQL Connectors component of Oracle MySQL (subcomponent: Connector/J). Supported versions that are affected are 5.1.41 and earlier. Easily "exploitable" vulnerability allows low privileged attacker with logon to the infrastructure where MySQL Connectors executes to compromise MySQL Connectors. Successful attacks of this vulnerability can result in unauthorized update, insert or delete access to some of MySQL Connectors accessible data. CVSS 3.0 Base Score 3.3 (Integrity impacts). CVSS Vector: (CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N). <p>Publish Date: 2017-04-24 <p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2017-3589>CVE-2017-3589</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>3.3</b>) <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Local - Attack Complexity: Low - Privileges Required: Low - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: None - Integrity Impact: Low - Availability Impact: None </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> <p></p> ### Suggested Fix <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-3589">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-3589</a></p> <p>Release Date: 2017-04-24</p> <p>Fix Resolution: 5.1.42</p> </p> <p></p> :rescue_worker_helmet: Automatic Remediation is available for this issue </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/low_vul.png?' width=19 height=20> <img src='https://whitesource-resources.whitesourcesoftware.com/viaGreen.png' width=19 height=20> CVE-2020-2933</summary> ### Vulnerable Library - <b>mysql-connector-java-5.1.25.jar</b></p> <p>MySQL JDBC Type 4 driver</p> <p>Library home page: <a href="http://dev.mysql.com/doc/connector-j/en/">http://dev.mysql.com/doc/connector-j/en/</a></p> <p>Path to dependency file: /pom.xml</p> <p>Path to vulnerable library: /target/easybuggy-1-SNAPSHOT/WEB-INF/lib/mysql-connector-java-5.1.25.jar,/home/wss-scanner/.m2/repository/mysql/mysql-connector-java/5.1.25/mysql-connector-java-5.1.25.jar</p> <p> Dependency Hierarchy: - :x: **mysql-connector-java-5.1.25.jar** (Vulnerable Library) <p>Found in base branch: <b>master</b></p> </p> <p></p> ### Reachability Analysis <p> <p>The vulnerable code is not reachable.</p> </p> <p></p> ### Vulnerability Details <p> Vulnerability in the MySQL Connectors product of Oracle MySQL (component: Connector/J). Supported versions that are affected are 5.1.48 and prior. Difficult to exploit vulnerability allows high privileged attacker with network access via multiple protocols to compromise MySQL Connectors. Successful attacks of this vulnerability can result in unauthorized ability to cause a partial denial of service (partial DOS) of MySQL Connectors. CVSS 3.0 Base Score 2.2 (Availability impacts). CVSS Vector: (CVSS:3.0/AV:N/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:L). <p>Publish Date: 2020-04-15 <p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2020-2933>CVE-2020-2933</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>2.2</b>) <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: High - Privileges Required: High - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: None - Integrity Impact: None - Availability Impact: Low </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> <p></p> ### Suggested Fix <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://docs.oracle.com/javase/7/docs/api/javax/xml/XMLConstants.html#FEATURE_SECURE_PROCESSING">https://docs.oracle.com/javase/7/docs/api/javax/xml/XMLConstants.html#FEATURE_SECURE_PROCESSING</a></p> <p>Release Date: 2020-04-15</p> <p>Fix Resolution: 5.1.49</p> </p> <p></p> :rescue_worker_helmet: Automatic Remediation is available for this issue </details> *** <p>:rescue_worker_helmet: Automatic Remediation is available for this issue.</p>

True

mysql-connector-java-5.1.25.jar: 9 vulnerabilities (highest severity is: 8.5) non-reachable - <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>mysql-connector-java-5.1.25.jar</b></p></summary> <p>MySQL JDBC Type 4 driver</p> <p>Library home page: <a href="http://dev.mysql.com/doc/connector-j/en/">http://dev.mysql.com/doc/connector-j/en/</a></p> <p>Path to dependency file: /pom.xml</p> <p>Path to vulnerable library: /target/easybuggy-1-SNAPSHOT/WEB-INF/lib/mysql-connector-java-5.1.25.jar,/home/wss-scanner/.m2/repository/mysql/mysql-connector-java/5.1.25/mysql-connector-java-5.1.25.jar</p> <p> </details> ## Vulnerabilities | CVE | Severity | <img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS | Dependency | Type | Fixed in (mysql-connector-java version) | Remediation Available | Reachability | | ------------- | ------------- | ----- | ----- | ----- | ------------- | --- | --- | | [CVE-2017-3523](https://www.mend.io/vulnerability-database/CVE-2017-3523) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 8.5 | mysql-connector-java-5.1.25.jar | Direct | 5.1.41 | &#9989;|<p align="center"><a href="#">[<img src='https://whitesource-resources.whitesourcesoftware.com/viaGreen.png' width=19 height=20>](## 'The vulnerability is non-reachable.')</a></p> | | [CVE-2022-21363](https://www.mend.io/vulnerability-database/CVE-2022-21363) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> Medium | 6.6 | mysql-connector-java-5.1.25.jar | Direct | mysql:mysql-connector-java:8.0.28 | &#9989;|<p align="center"><a href="#">[<img src='https://whitesource-resources.whitesourcesoftware.com/viaGreen.png' width=19 height=20>](## 'The vulnerability is non-reachable.')</a></p> | | [CVE-2017-3586](https://www.mend.io/vulnerability-database/CVE-2017-3586) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> Medium | 6.4 | mysql-connector-java-5.1.25.jar | Direct | 5.1.42 | &#9989;|<p align="center"><a href="#">[<img src='https://whitesource-resources.whitesourcesoftware.com/viaGreen.png' width=19 height=20>](## 'The vulnerability is non-reachable.')</a></p> | | [CVE-2019-2692](https://www.mend.io/vulnerability-database/CVE-2019-2692) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> Medium | 6.3 | mysql-connector-java-5.1.25.jar | Direct | 5.1.48 | &#9989;|<p align="center"><a href="#">[<img src='https://whitesource-resources.whitesourcesoftware.com/viaGreen.png' width=19 height=20>](## 'The vulnerability is non-reachable.')</a></p> | | [CVE-2020-2934](https://www.mend.io/vulnerability-database/CVE-2020-2934) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> Medium | 5.0 | mysql-connector-java-5.1.25.jar | Direct | 5.1.49 | &#9989;|<p align="center"><a href="#">[<img src='https://whitesource-resources.whitesourcesoftware.com/viaGreen.png' width=19 height=20>](## 'The vulnerability is non-reachable.')</a></p> | | [CVE-2020-2875](https://www.mend.io/vulnerability-database/CVE-2020-2875) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> Medium | 4.7 | mysql-connector-java-5.1.25.jar | Direct | 5.1.49 | &#9989;|<p align="center"><a href="#">[<img src='https://whitesource-resources.whitesourcesoftware.com/viaGreen.png' width=19 height=20>](## 'The vulnerability is non-reachable.')</a></p> | | [CVE-2015-2575](https://www.mend.io/vulnerability-database/CVE-2015-2575) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> Medium | 4.2 | mysql-connector-java-5.1.25.jar | Direct | 5.1.35 | &#9989;|<p align="center"><a href="#">[<img src='https://whitesource-resources.whitesourcesoftware.com/viaGreen.png' width=19 height=20>](## 'The vulnerability is non-reachable.')</a></p> | | [CVE-2017-3589](https://www.mend.io/vulnerability-database/CVE-2017-3589) | <img src='https://whitesource-resources.whitesourcesoftware.com/low_vul.png?' width=19 height=20> Low | 3.3 | mysql-connector-java-5.1.25.jar | Direct | 5.1.42 | &#9989;|<p align="center"><a href="#">[<img src='https://whitesource-resources.whitesourcesoftware.com/viaGreen.png' width=19 height=20>](## 'The vulnerability is non-reachable.')</a></p> | | [CVE-2020-2933](https://www.mend.io/vulnerability-database/CVE-2020-2933) | <img src='https://whitesource-resources.whitesourcesoftware.com/low_vul.png?' width=19 height=20> Low | 2.2 | mysql-connector-java-5.1.25.jar | Direct | 5.1.49 | &#9989;|<p align="center"><a href="#">[<img src='https://whitesource-resources.whitesourcesoftware.com/viaGreen.png' width=19 height=20>](## 'The vulnerability is non-reachable.')</a></p> | ## Details <details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> <img src='https://whitesource-resources.whitesourcesoftware.com/viaGreen.png' width=19 height=20> CVE-2017-3523</summary> ### Vulnerable Library - <b>mysql-connector-java-5.1.25.jar</b></p> <p>MySQL JDBC Type 4 driver</p> <p>Library home page: <a href="http://dev.mysql.com/doc/connector-j/en/">http://dev.mysql.com/doc/connector-j/en/</a></p> <p>Path to dependency file: /pom.xml</p> <p>Path to vulnerable library: /target/easybuggy-1-SNAPSHOT/WEB-INF/lib/mysql-connector-java-5.1.25.jar,/home/wss-scanner/.m2/repository/mysql/mysql-connector-java/5.1.25/mysql-connector-java-5.1.25.jar</p> <p> Dependency Hierarchy: - :x: **mysql-connector-java-5.1.25.jar** (Vulnerable Library) <p>Found in base branch: <b>master</b></p> </p> <p></p> ### Reachability Analysis <p> <p>The vulnerable code is not reachable.</p> </p> <p></p> ### Vulnerability Details <p> Vulnerability in the MySQL Connectors component of Oracle MySQL (subcomponent: Connector/J). Supported versions that are affected are 5.1.40 and earlier. Difficult to exploit vulnerability allows low privileged attacker with network access via multiple protocols to compromise MySQL Connectors. While the vulnerability is in MySQL Connectors, attacks may significantly impact additional products. Successful attacks of this vulnerability can result in takeover of MySQL Connectors. CVSS 3.0 Base Score 8.5 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H). <p>Publish Date: 2017-04-24 <p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2017-3523>CVE-2017-3523</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>8.5</b>) <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: High - Privileges Required: Low - User Interaction: None - Scope: Changed - Impact Metrics: - Confidentiality Impact: High - Integrity Impact: High - Availability Impact: High </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> <p></p> ### Suggested Fix <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://github.com/advisories/GHSA-2xxh-f8r3-hvvr">https://github.com/advisories/GHSA-2xxh-f8r3-hvvr</a></p> <p>Release Date: 2017-04-24</p> <p>Fix Resolution: 5.1.41</p> </p> <p></p> :rescue_worker_helmet: Automatic Remediation is available for this issue </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> <img src='https://whitesource-resources.whitesourcesoftware.com/viaGreen.png' width=19 height=20> CVE-2022-21363</summary> ### Vulnerable Library - <b>mysql-connector-java-5.1.25.jar</b></p> <p>MySQL JDBC Type 4 driver</p> <p>Library home page: <a href="http://dev.mysql.com/doc/connector-j/en/">http://dev.mysql.com/doc/connector-j/en/</a></p> <p>Path to dependency file: /pom.xml</p> <p>Path to vulnerable library: /target/easybuggy-1-SNAPSHOT/WEB-INF/lib/mysql-connector-java-5.1.25.jar,/home/wss-scanner/.m2/repository/mysql/mysql-connector-java/5.1.25/mysql-connector-java-5.1.25.jar</p> <p> Dependency Hierarchy: - :x: **mysql-connector-java-5.1.25.jar** (Vulnerable Library) <p>Found in base branch: <b>master</b></p> </p> <p></p> ### Reachability Analysis <p> <p>The vulnerable code is not reachable.</p> </p> <p></p> ### Vulnerability Details <p> Vulnerability in the MySQL Connectors product of Oracle MySQL (component: Connector/J). Supported versions that are affected are 8.0.27 and prior. Difficult to exploit vulnerability allows high privileged attacker with network access via multiple protocols to compromise MySQL Connectors. Successful attacks of this vulnerability can result in takeover of MySQL Connectors. CVSS 3.1 Base Score 6.6 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H). <p>Publish Date: 2022-01-19 <p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-21363>CVE-2022-21363</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>6.6</b>) <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: High - Privileges Required: High - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: High - Integrity Impact: High - Availability Impact: High </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> <p></p> ### Suggested Fix <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://github.com/advisories/GHSA-g76j-4cxx-23h9">https://github.com/advisories/GHSA-g76j-4cxx-23h9</a></p> <p>Release Date: 2022-01-19</p> <p>Fix Resolution: mysql:mysql-connector-java:8.0.28</p> </p> <p></p> :rescue_worker_helmet: Automatic Remediation is available for this issue </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> <img src='https://whitesource-resources.whitesourcesoftware.com/viaGreen.png' width=19 height=20> CVE-2017-3586</summary> ### Vulnerable Library - <b>mysql-connector-java-5.1.25.jar</b></p> <p>MySQL JDBC Type 4 driver</p> <p>Library home page: <a href="http://dev.mysql.com/doc/connector-j/en/">http://dev.mysql.com/doc/connector-j/en/</a></p> <p>Path to dependency file: /pom.xml</p> <p>Path to vulnerable library: /target/easybuggy-1-SNAPSHOT/WEB-INF/lib/mysql-connector-java-5.1.25.jar,/home/wss-scanner/.m2/repository/mysql/mysql-connector-java/5.1.25/mysql-connector-java-5.1.25.jar</p> <p> Dependency Hierarchy: - :x: **mysql-connector-java-5.1.25.jar** (Vulnerable Library) <p>Found in base branch: <b>master</b></p> </p> <p></p> ### Reachability Analysis <p> <p>The vulnerable code is not reachable.</p> </p> <p></p> ### Vulnerability Details <p> Vulnerability in the MySQL Connectors component of Oracle MySQL (subcomponent: Connector/J). Supported versions that are affected are 5.1.41 and earlier. Easily "exploitable" vulnerability allows low privileged attacker with network access via multiple protocols to compromise MySQL Connectors. While the vulnerability is in MySQL Connectors, attacks may significantly impact additional products. Successful attacks of this vulnerability can result in unauthorized update, insert or delete access to some of MySQL Connectors accessible data as well as unauthorized read access to a subset of MySQL Connectors accessible data. CVSS 3.0 Base Score 6.4 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N). <p>Publish Date: 2017-04-24 <p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2017-3586>CVE-2017-3586</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>6.4</b>) <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: Low - User Interaction: None - Scope: Changed - Impact Metrics: - Confidentiality Impact: Low - Integrity Impact: Low - Availability Impact: None </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> <p></p> ### Suggested Fix <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://bugzilla.redhat.com/show_bug.cgi?id=1444406">https://bugzilla.redhat.com/show_bug.cgi?id=1444406</a></p> <p>Release Date: 2017-04-24</p> <p>Fix Resolution: 5.1.42</p> </p> <p></p> :rescue_worker_helmet: Automatic Remediation is available for this issue </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> <img src='https://whitesource-resources.whitesourcesoftware.com/viaGreen.png' width=19 height=20> CVE-2019-2692</summary> ### Vulnerable Library - <b>mysql-connector-java-5.1.25.jar</b></p> <p>MySQL JDBC Type 4 driver</p> <p>Library home page: <a href="http://dev.mysql.com/doc/connector-j/en/">http://dev.mysql.com/doc/connector-j/en/</a></p> <p>Path to dependency file: /pom.xml</p> <p>Path to vulnerable library: /target/easybuggy-1-SNAPSHOT/WEB-INF/lib/mysql-connector-java-5.1.25.jar,/home/wss-scanner/.m2/repository/mysql/mysql-connector-java/5.1.25/mysql-connector-java-5.1.25.jar</p> <p> Dependency Hierarchy: - :x: **mysql-connector-java-5.1.25.jar** (Vulnerable Library) <p>Found in base branch: <b>master</b></p> </p> <p></p> ### Reachability Analysis <p> <p>The vulnerable code is not reachable.</p> </p> <p></p> ### Vulnerability Details <p> Vulnerability in the MySQL Connectors component of Oracle MySQL (subcomponent: Connector/J). Supported versions that are affected are 8.0.15 and prior. Difficult to exploit vulnerability allows high privileged attacker with logon to the infrastructure where MySQL Connectors executes to compromise MySQL Connectors. Successful attacks require human interaction from a person other than the attacker. Successful attacks of this vulnerability can result in takeover of MySQL Connectors. CVSS 3.0 Base Score 6.3 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.0/AV:L/AC:H/PR:H/UI:R/S:U/C:H/I:H/A:H). <p>Publish Date: 2019-04-23 <p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2019-2692>CVE-2019-2692</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>6.3</b>) <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Local - Attack Complexity: High - Privileges Required: High - User Interaction: Required - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: High - Integrity Impact: High - Availability Impact: High </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> <p></p> ### Suggested Fix <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://github.com/advisories/GHSA-jcq3-cprp-m333">https://github.com/advisories/GHSA-jcq3-cprp-m333</a></p> <p>Release Date: 2019-04-23</p> <p>Fix Resolution: 5.1.48</p> </p> <p></p> :rescue_worker_helmet: Automatic Remediation is available for this issue </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> <img src='https://whitesource-resources.whitesourcesoftware.com/viaGreen.png' width=19 height=20> CVE-2020-2934</summary> ### Vulnerable Library - <b>mysql-connector-java-5.1.25.jar</b></p> <p>MySQL JDBC Type 4 driver</p> <p>Library home page: <a href="http://dev.mysql.com/doc/connector-j/en/">http://dev.mysql.com/doc/connector-j/en/</a></p> <p>Path to dependency file: /pom.xml</p> <p>Path to vulnerable library: /target/easybuggy-1-SNAPSHOT/WEB-INF/lib/mysql-connector-java-5.1.25.jar,/home/wss-scanner/.m2/repository/mysql/mysql-connector-java/5.1.25/mysql-connector-java-5.1.25.jar</p> <p> Dependency Hierarchy: - :x: **mysql-connector-java-5.1.25.jar** (Vulnerable Library) <p>Found in base branch: <b>master</b></p> </p> <p></p> ### Reachability Analysis <p> <p>The vulnerable code is not reachable.</p> </p> <p></p> ### Vulnerability Details <p> Vulnerability in the MySQL Connectors product of Oracle MySQL (component: Connector/J). Supported versions that are affected are 8.0.19 and prior and 5.1.48 and prior. Difficult to exploit vulnerability allows unauthenticated attacker with network access via multiple protocols to compromise MySQL Connectors. Successful attacks require human interaction from a person other than the attacker. Successful attacks of this vulnerability can result in unauthorized update, insert or delete access to some of MySQL Connectors accessible data as well as unauthorized read access to a subset of MySQL Connectors accessible data and unauthorized ability to cause a partial denial of service (partial DOS) of MySQL Connectors. CVSS 3.0 Base Score 5.0 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:L). <p>Publish Date: 2020-04-15 <p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2020-2934>CVE-2020-2934</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>5.0</b>) <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: High - Privileges Required: None - User Interaction: Required - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: Low - Integrity Impact: Low - Availability Impact: Low </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> <p></p> ### Suggested Fix <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://www.oracle.com/security-alerts/cpuapr2020.html">https://www.oracle.com/security-alerts/cpuapr2020.html</a></p> <p>Release Date: 2020-04-15</p> <p>Fix Resolution: 5.1.49</p> </p> <p></p> :rescue_worker_helmet: Automatic Remediation is available for this issue </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> <img src='https://whitesource-resources.whitesourcesoftware.com/viaGreen.png' width=19 height=20> CVE-2020-2875</summary> ### Vulnerable Library - <b>mysql-connector-java-5.1.25.jar</b></p> <p>MySQL JDBC Type 4 driver</p> <p>Library home page: <a href="http://dev.mysql.com/doc/connector-j/en/">http://dev.mysql.com/doc/connector-j/en/</a></p> <p>Path to dependency file: /pom.xml</p> <p>Path to vulnerable library: /target/easybuggy-1-SNAPSHOT/WEB-INF/lib/mysql-connector-java-5.1.25.jar,/home/wss-scanner/.m2/repository/mysql/mysql-connector-java/5.1.25/mysql-connector-java-5.1.25.jar</p> <p> Dependency Hierarchy: - :x: **mysql-connector-java-5.1.25.jar** (Vulnerable Library) <p>Found in base branch: <b>master</b></p> </p> <p></p> ### Reachability Analysis <p> <p>The vulnerable code is not reachable.</p> </p> <p></p> ### Vulnerability Details <p> Vulnerability in the MySQL Connectors product of Oracle MySQL (component: Connector/J). Supported versions that are affected are 8.0.14 and prior and 5.1.48 and prior. Difficult to exploit vulnerability allows unauthenticated attacker with network access via multiple protocols to compromise MySQL Connectors. Successful attacks require human interaction from a person other than the attacker and while the vulnerability is in MySQL Connectors, attacks may significantly impact additional products. Successful attacks of this vulnerability can result in unauthorized update, insert or delete access to some of MySQL Connectors accessible data as well as unauthorized read access to a subset of MySQL Connectors accessible data. CVSS 3.0 Base Score 4.7 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:C/C:L/I:L/A:N). <p>Publish Date: 2020-04-15 <p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2020-2875>CVE-2020-2875</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>4.7</b>) <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: High - Privileges Required: None - User Interaction: Required - Scope: Changed - Impact Metrics: - Confidentiality Impact: Low - Integrity Impact: Low - Availability Impact: None </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> <p></p> ### Suggested Fix <p> <p>Type: Upgrade version</p> <p>Release Date: 2020-04-15</p> <p>Fix Resolution: 5.1.49</p> </p> <p></p> :rescue_worker_helmet: Automatic Remediation is available for this issue </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> <img src='https://whitesource-resources.whitesourcesoftware.com/viaGreen.png' width=19 height=20> CVE-2015-2575</summary> ### Vulnerable Library - <b>mysql-connector-java-5.1.25.jar</b></p> <p>MySQL JDBC Type 4 driver</p> <p>Library home page: <a href="http://dev.mysql.com/doc/connector-j/en/">http://dev.mysql.com/doc/connector-j/en/</a></p> <p>Path to dependency file: /pom.xml</p> <p>Path to vulnerable library: /target/easybuggy-1-SNAPSHOT/WEB-INF/lib/mysql-connector-java-5.1.25.jar,/home/wss-scanner/.m2/repository/mysql/mysql-connector-java/5.1.25/mysql-connector-java-5.1.25.jar</p> <p> Dependency Hierarchy: - :x: **mysql-connector-java-5.1.25.jar** (Vulnerable Library) <p>Found in base branch: <b>master</b></p> </p> <p></p> ### Reachability Analysis <p> <p>The vulnerable code is not reachable.</p> </p> <p></p> ### Vulnerability Details <p> Unspecified vulnerability in the MySQL Connectors component in Oracle MySQL 5.1.34 and earlier allows remote authenticated users to affect confidentiality and integrity via unknown vectors related to Connector/J. <p>Publish Date: 2015-04-16 <p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2015-2575>CVE-2015-2575</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>4.2</b>) <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: High - Privileges Required: Low - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: Low - Integrity Impact: Low - Availability Impact: None </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> <p></p> ### Suggested Fix <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://github.com/advisories/GHSA-gc43-g62c-99g2">https://github.com/advisories/GHSA-gc43-g62c-99g2</a></p> <p>Release Date: 2015-04-16</p> <p>Fix Resolution: 5.1.35</p> </p> <p></p> :rescue_worker_helmet: Automatic Remediation is available for this issue </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/low_vul.png?' width=19 height=20> <img src='https://whitesource-resources.whitesourcesoftware.com/viaGreen.png' width=19 height=20> CVE-2017-3589</summary> ### Vulnerable Library - <b>mysql-connector-java-5.1.25.jar</b></p> <p>MySQL JDBC Type 4 driver</p> <p>Library home page: <a href="http://dev.mysql.com/doc/connector-j/en/">http://dev.mysql.com/doc/connector-j/en/</a></p> <p>Path to dependency file: /pom.xml</p> <p>Path to vulnerable library: /target/easybuggy-1-SNAPSHOT/WEB-INF/lib/mysql-connector-java-5.1.25.jar,/home/wss-scanner/.m2/repository/mysql/mysql-connector-java/5.1.25/mysql-connector-java-5.1.25.jar</p> <p> Dependency Hierarchy: - :x: **mysql-connector-java-5.1.25.jar** (Vulnerable Library) <p>Found in base branch: <b>master</b></p> </p> <p></p> ### Reachability Analysis <p> <p>The vulnerable code is not reachable.</p> </p> <p></p> ### Vulnerability Details <p> Vulnerability in the MySQL Connectors component of Oracle MySQL (subcomponent: Connector/J). Supported versions that are affected are 5.1.41 and earlier. Easily "exploitable" vulnerability allows low privileged attacker with logon to the infrastructure where MySQL Connectors executes to compromise MySQL Connectors. Successful attacks of this vulnerability can result in unauthorized update, insert or delete access to some of MySQL Connectors accessible data. CVSS 3.0 Base Score 3.3 (Integrity impacts). CVSS Vector: (CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N). <p>Publish Date: 2017-04-24 <p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2017-3589>CVE-2017-3589</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>3.3</b>) <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Local - Attack Complexity: Low - Privileges Required: Low - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: None - Integrity Impact: Low - Availability Impact: None </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> <p></p> ### Suggested Fix <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-3589">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-3589</a></p> <p>Release Date: 2017-04-24</p> <p>Fix Resolution: 5.1.42</p> </p> <p></p> :rescue_worker_helmet: Automatic Remediation is available for this issue </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/low_vul.png?' width=19 height=20> <img src='https://whitesource-resources.whitesourcesoftware.com/viaGreen.png' width=19 height=20> CVE-2020-2933</summary> ### Vulnerable Library - <b>mysql-connector-java-5.1.25.jar</b></p> <p>MySQL JDBC Type 4 driver</p> <p>Library home page: <a href="http://dev.mysql.com/doc/connector-j/en/">http://dev.mysql.com/doc/connector-j/en/</a></p> <p>Path to dependency file: /pom.xml</p> <p>Path to vulnerable library: /target/easybuggy-1-SNAPSHOT/WEB-INF/lib/mysql-connector-java-5.1.25.jar,/home/wss-scanner/.m2/repository/mysql/mysql-connector-java/5.1.25/mysql-connector-java-5.1.25.jar</p> <p> Dependency Hierarchy: - :x: **mysql-connector-java-5.1.25.jar** (Vulnerable Library) <p>Found in base branch: <b>master</b></p> </p> <p></p> ### Reachability Analysis <p> <p>The vulnerable code is not reachable.</p> </p> <p></p> ### Vulnerability Details <p> Vulnerability in the MySQL Connectors product of Oracle MySQL (component: Connector/J). Supported versions that are affected are 5.1.48 and prior. Difficult to exploit vulnerability allows high privileged attacker with network access via multiple protocols to compromise MySQL Connectors. Successful attacks of this vulnerability can result in unauthorized ability to cause a partial denial of service (partial DOS) of MySQL Connectors. CVSS 3.0 Base Score 2.2 (Availability impacts). CVSS Vector: (CVSS:3.0/AV:N/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:L). <p>Publish Date: 2020-04-15 <p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2020-2933>CVE-2020-2933</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>2.2</b>) <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: High - Privileges Required: High - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: None - Integrity Impact: None - Availability Impact: Low </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> <p></p> ### Suggested Fix <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://docs.oracle.com/javase/7/docs/api/javax/xml/XMLConstants.html#FEATURE_SECURE_PROCESSING">https://docs.oracle.com/javase/7/docs/api/javax/xml/XMLConstants.html#FEATURE_SECURE_PROCESSING</a></p> <p>Release Date: 2020-04-15</p> <p>Fix Resolution: 5.1.49</p> </p> <p></p> :rescue_worker_helmet: Automatic Remediation is available for this issue </details> *** <p>:rescue_worker_helmet: Automatic Remediation is available for this issue.</p>

non_priority

mysql connector java jar vulnerabilities highest severity is non reachable vulnerable library mysql connector java jar mysql jdbc type driver library home page a href path to dependency file pom xml path to vulnerable library target easybuggy snapshot web inf lib mysql connector java jar home wss scanner repository mysql mysql connector java mysql connector java jar vulnerabilities cve severity cvss dependency type fixed in mysql connector java version remediation available reachability high mysql connector java jar direct the vulnerability is non reachable medium mysql connector java jar direct mysql mysql connector java the vulnerability is non reachable medium mysql connector java jar direct the vulnerability is non reachable medium mysql connector java jar direct the vulnerability is non reachable medium mysql connector java jar direct the vulnerability is non reachable medium mysql connector java jar direct the vulnerability is non reachable medium mysql connector java jar direct the vulnerability is non reachable low mysql connector java jar direct the vulnerability is non reachable low mysql connector java jar direct the vulnerability is non reachable details cve vulnerable library mysql connector java jar mysql jdbc type driver library home page a href path to dependency file pom xml path to vulnerable library target easybuggy snapshot web inf lib mysql connector java jar home wss scanner repository mysql mysql connector java mysql connector java jar dependency hierarchy x mysql connector java jar vulnerable library found in base branch master reachability analysis the vulnerable code is not reachable vulnerability details vulnerability in the mysql connectors component of oracle mysql subcomponent connector j supported versions that are affected are and earlier difficult to exploit vulnerability allows low privileged attacker with network access via multiple protocols to compromise mysql connectors while the vulnerability is in mysql connectors attacks may significantly impact additional products successful attacks of this vulnerability can result in takeover of mysql connectors cvss base score confidentiality integrity and availability impacts cvss vector cvss av n ac h pr l ui n s c c h i h a h publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity high privileges required low user interaction none scope changed impact metrics confidentiality impact high integrity impact high availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution rescue worker helmet automatic remediation is available for this issue cve vulnerable library mysql connector java jar mysql jdbc type driver library home page a href path to dependency file pom xml path to vulnerable library target easybuggy snapshot web inf lib mysql connector java jar home wss scanner repository mysql mysql connector java mysql connector java jar dependency hierarchy x mysql connector java jar vulnerable library found in base branch master reachability analysis the vulnerable code is not reachable vulnerability details vulnerability in the mysql connectors product of oracle mysql component connector j supported versions that are affected are and prior difficult to exploit vulnerability allows high privileged attacker with network access via multiple protocols to compromise mysql connectors successful attacks of this vulnerability can result in takeover of mysql connectors cvss base score confidentiality integrity and availability impacts cvss vector cvss av n ac h pr h ui n s u c h i h a h publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity high privileges required high user interaction none scope unchanged impact metrics confidentiality impact high integrity impact high availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution mysql mysql connector java rescue worker helmet automatic remediation is available for this issue cve vulnerable library mysql connector java jar mysql jdbc type driver library home page a href path to dependency file pom xml path to vulnerable library target easybuggy snapshot web inf lib mysql connector java jar home wss scanner repository mysql mysql connector java mysql connector java jar dependency hierarchy x mysql connector java jar vulnerable library found in base branch master reachability analysis the vulnerable code is not reachable vulnerability details vulnerability in the mysql connectors component of oracle mysql subcomponent connector j supported versions that are affected are and earlier easily exploitable vulnerability allows low privileged attacker with network access via multiple protocols to compromise mysql connectors while the vulnerability is in mysql connectors attacks may significantly impact additional products successful attacks of this vulnerability can result in unauthorized update insert or delete access to some of mysql connectors accessible data as well as unauthorized read access to a subset of mysql connectors accessible data cvss base score confidentiality and integrity impacts cvss vector cvss av n ac l pr l ui n s c c l i l a n 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 changed impact metrics confidentiality impact low integrity impact low availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution rescue worker helmet automatic remediation is available for this issue cve vulnerable library mysql connector java jar mysql jdbc type driver library home page a href path to dependency file pom xml path to vulnerable library target easybuggy snapshot web inf lib mysql connector java jar home wss scanner repository mysql mysql connector java mysql connector java jar dependency hierarchy x mysql connector java jar vulnerable library found in base branch master reachability analysis the vulnerable code is not reachable vulnerability details vulnerability in the mysql connectors component of oracle mysql subcomponent connector j supported versions that are affected are and prior difficult to exploit vulnerability allows high privileged attacker with logon to the infrastructure where mysql connectors executes to compromise mysql connectors successful attacks require human interaction from a person other than the attacker successful attacks of this vulnerability can result in takeover of mysql connectors cvss base score confidentiality integrity and availability impacts cvss vector cvss av l ac h pr h ui r s u c h i h a h publish date url a href cvss score details base score metrics exploitability metrics attack vector local attack complexity high privileges required high user interaction required scope unchanged impact metrics confidentiality impact high integrity impact high availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution rescue worker helmet automatic remediation is available for this issue cve vulnerable library mysql connector java jar mysql jdbc type driver library home page a href path to dependency file pom xml path to vulnerable library target easybuggy snapshot web inf lib mysql connector java jar home wss scanner repository mysql mysql connector java mysql connector java jar dependency hierarchy x mysql connector java jar vulnerable library found in base branch master reachability analysis the vulnerable code is not reachable vulnerability details vulnerability in the mysql connectors product of oracle mysql component connector j supported versions that are affected are and prior and and prior difficult to exploit vulnerability allows unauthenticated attacker with network access via multiple protocols to compromise mysql connectors successful attacks require human interaction from a person other than the attacker successful attacks of this vulnerability can result in unauthorized update insert or delete access to some of mysql connectors accessible data as well as unauthorized read access to a subset of mysql connectors accessible data and unauthorized ability to cause a partial denial of service partial dos of mysql connectors cvss base score confidentiality integrity and availability impacts cvss vector cvss av n ac h pr n ui r s u c l i l a l publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity high privileges required none user interaction required scope unchanged impact metrics confidentiality impact low integrity impact low availability impact low for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution rescue worker helmet automatic remediation is available for this issue cve vulnerable library mysql connector java jar mysql jdbc type driver library home page a href path to dependency file pom xml path to vulnerable library target easybuggy snapshot web inf lib mysql connector java jar home wss scanner repository mysql mysql connector java mysql connector java jar dependency hierarchy x mysql connector java jar vulnerable library found in base branch master reachability analysis the vulnerable code is not reachable vulnerability details vulnerability in the mysql connectors product of oracle mysql component connector j supported versions that are affected are and prior and and prior difficult to exploit vulnerability allows unauthenticated attacker with network access via multiple protocols to compromise mysql connectors successful attacks require human interaction from a person other than the attacker and while the vulnerability is in mysql connectors attacks may significantly impact additional products successful attacks of this vulnerability can result in unauthorized update insert or delete access to some of mysql connectors accessible data as well as unauthorized read access to a subset of mysql connectors accessible data cvss base score confidentiality and integrity impacts cvss vector cvss av n ac h pr n ui r s c c l i l a n publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity high privileges required none user interaction required scope changed impact metrics confidentiality impact low integrity impact low availability impact none for more information on scores click a href suggested fix type upgrade version release date fix resolution rescue worker helmet automatic remediation is available for this issue cve vulnerable library mysql connector java jar mysql jdbc type driver library home page a href path to dependency file pom xml path to vulnerable library target easybuggy snapshot web inf lib mysql connector java jar home wss scanner repository mysql mysql connector java mysql connector java jar dependency hierarchy x mysql connector java jar vulnerable library found in base branch master reachability analysis the vulnerable code is not reachable vulnerability details unspecified vulnerability in the mysql connectors component in oracle mysql and earlier allows remote authenticated users to affect confidentiality and integrity via unknown vectors related to connector j publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity high privileges required low user interaction none scope unchanged impact metrics confidentiality impact low integrity impact low availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution rescue worker helmet automatic remediation is available for this issue cve vulnerable library mysql connector java jar mysql jdbc type driver library home page a href path to dependency file pom xml path to vulnerable library target easybuggy snapshot web inf lib mysql connector java jar home wss scanner repository mysql mysql connector java mysql connector java jar dependency hierarchy x mysql connector java jar vulnerable library found in base branch master reachability analysis the vulnerable code is not reachable vulnerability details vulnerability in the mysql connectors component of oracle mysql subcomponent connector j supported versions that are affected are and earlier easily exploitable vulnerability allows low privileged attacker with logon to the infrastructure where mysql connectors executes to compromise mysql connectors successful attacks of this vulnerability can result in unauthorized update insert or delete access to some of mysql connectors accessible data cvss base score integrity impacts cvss vector cvss av l ac l pr l ui n s u c n i l a n publish date url a href cvss score details base score metrics exploitability metrics attack vector local attack complexity low privileges required low user interaction none scope unchanged impact metrics confidentiality impact none integrity impact low availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution rescue worker helmet automatic remediation is available for this issue cve vulnerable library mysql connector java jar mysql jdbc type driver library home page a href path to dependency file pom xml path to vulnerable library target easybuggy snapshot web inf lib mysql connector java jar home wss scanner repository mysql mysql connector java mysql connector java jar dependency hierarchy x mysql connector java jar vulnerable library found in base branch master reachability analysis the vulnerable code is not reachable vulnerability details vulnerability in the mysql connectors product of oracle mysql component connector j supported versions that are affected are and prior difficult to exploit vulnerability allows high privileged attacker with network access via multiple protocols to compromise mysql connectors successful attacks of this vulnerability can result in unauthorized ability to cause a partial denial of service partial dos of mysql connectors cvss base score availability impacts cvss vector cvss av n ac h pr h ui n s u c n i n a l publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity high privileges required high user interaction none scope unchanged impact metrics confidentiality impact none integrity impact none availability impact low for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution rescue worker helmet automatic remediation is available for this issue rescue worker helmet automatic remediation is available for this issue

IssuesEvent

2023-03-16 21:25:56

billmcchesney1/react-bootstrap

https://api.github.com/repos/billmcchesney1/react-bootstrap

opened

CVE-2023-28155 (Medium) detected in request-2.88.2.tgz

Mend: dependency security vulnerability

## CVE-2023-28155 - Medium Severity Vulnerability <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>request-2.88.2.tgz</b></p></summary> <p>Simplified HTTP request client.</p> <p>Library home page: <a href="https://registry.npmjs.org/request/-/request-2.88.2.tgz">https://registry.npmjs.org/request/-/request-2.88.2.tgz</a></p> <p>Path to dependency file: /package.json</p> <p>Path to vulnerable library: /node_modules/request/package.json,/www/node_modules/request/package.json</p> <p> Dependency Hierarchy: - docsearch.js-2.6.3.tgz (Root Library) - :x: **request-2.88.2.tgz** (Vulnerable Library) <p>Found in base branch: <b>master</b></p> </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary> <p> ** UNSUPPORTED WHEN ASSIGNED ** The Request package through 2.88.1 for Node.js allows a bypass of SSRF mitigations via an attacker-controller server that does a cross-protocol redirect (HTTP to HTTPS, or HTTPS to HTTP). NOTE: This vulnerability only affects products that are no longer supported by the maintainer. <p>Publish Date: 2023-03-16 <p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2023-28155>CVE-2023-28155</a></p> </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.5</b>)</summary> <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Local - Attack Complexity: Low - Privileges Required: None - User Interaction: Required - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: None - Integrity Impact: None - Availability Impact: High </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> </details> <p></p>

True

CVE-2023-28155 (Medium) detected in request-2.88.2.tgz - ## CVE-2023-28155 - Medium Severity Vulnerability <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>request-2.88.2.tgz</b></p></summary> <p>Simplified HTTP request client.</p> <p>Library home page: <a href="https://registry.npmjs.org/request/-/request-2.88.2.tgz">https://registry.npmjs.org/request/-/request-2.88.2.tgz</a></p> <p>Path to dependency file: /package.json</p> <p>Path to vulnerable library: /node_modules/request/package.json,/www/node_modules/request/package.json</p> <p> Dependency Hierarchy: - docsearch.js-2.6.3.tgz (Root Library) - :x: **request-2.88.2.tgz** (Vulnerable Library) <p>Found in base branch: <b>master</b></p> </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary> <p> ** UNSUPPORTED WHEN ASSIGNED ** The Request package through 2.88.1 for Node.js allows a bypass of SSRF mitigations via an attacker-controller server that does a cross-protocol redirect (HTTP to HTTPS, or HTTPS to HTTP). NOTE: This vulnerability only affects products that are no longer supported by the maintainer. <p>Publish Date: 2023-03-16 <p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2023-28155>CVE-2023-28155</a></p> </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.5</b>)</summary> <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Local - Attack Complexity: Low - Privileges Required: None - User Interaction: Required - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: None - Integrity Impact: None - Availability Impact: High </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> </details> <p></p>

non_priority

cve medium detected in request tgz cve medium severity vulnerability vulnerable library request tgz simplified http request client library home page a href path to dependency file package json path to vulnerable library node modules request package json www node modules request package json dependency hierarchy docsearch js tgz root library x request tgz vulnerable library found in base branch master vulnerability details unsupported when assigned the request package through for node js allows a bypass of ssrf mitigations via an attacker controller server that does a cross protocol redirect http to https or https to http note this vulnerability only affects products that are no longer supported by the maintainer publish date url a href cvss score details base score metrics exploitability metrics attack vector local attack complexity low privileges required none user interaction required scope unchanged impact metrics confidentiality impact none integrity impact none availability impact high for more information on scores click a href

IssuesEvent

2023-09-14 15:00:12

CodeSystem2022/ERROR-404-Trabajo-Final

https://api.github.com/repos/CodeSystem2022/ERROR-404-Trabajo-Final

closed

Hacer el Brief

documentation

- Completar el Brief para entregarlo hasta el Domingo 10 de Septiembre inclusive

1.0

Hacer el Brief - - Completar el Brief para entregarlo hasta el Domingo 10 de Septiembre inclusive

non_priority

hacer el brief completar el brief para entregarlo hasta el domingo de septiembre inclusive

IssuesEvent

2015-02-27 00:27:14

alistairreilly/andors-trail

https://api.github.com/repos/alistairreilly/andors-trail

closed

Forest northwest to Alynndir's house cannot be entered

auto-migrated Type-Defect

``` What steps will reproduce the problem? 1.according to what Alynndir says,go to the forest to the northwest 2.after defeat some enemies on the road, meet a map change point 3.reach the point leads to map change,but the only direction you can go leads you back to the former map,then a endless circle What is the expected output? What do you see instead? I assume some changes should be done to this map change point. What version of the product are you using? On what device? 0.6.8b1, Android 2.2 Please provide any additional information below. ``` Original issue reported on code.google.com by `[email protected]` on 23 Feb 2011 at 6:08

1.0

Forest northwest to Alynndir's house cannot be entered - ``` What steps will reproduce the problem? 1.according to what Alynndir says,go to the forest to the northwest 2.after defeat some enemies on the road, meet a map change point 3.reach the point leads to map change,but the only direction you can go leads you back to the former map,then a endless circle What is the expected output? What do you see instead? I assume some changes should be done to this map change point. What version of the product are you using? On what device? 0.6.8b1, Android 2.2 Please provide any additional information below. ``` Original issue reported on code.google.com by `[email protected]` on 23 Feb 2011 at 6:08

non_priority

forest northwest to alynndir s house cannot be entered what steps will reproduce the problem according to what alynndir says go to the forest to the northwest after defeat some enemies on the road meet a map change point reach the point leads to map change but the only direction you can go leads you back to the former map then a endless circle what is the expected output what do you see instead i assume some changes should be done to this map change point what version of the product are you using on what device android please provide any additional information below original issue reported on code google com by littlep gmail com on feb at

IssuesEvent

2018-09-04 03:08:01

SleepyTrousers/EnderIO

https://api.github.com/repos/SleepyTrousers/EnderIO

closed

Server crash ticking block entity

1.12 Code Complete bug

#### Issue Description: Server Crash #### What happens: When server is started it goes into SERVER_STOPPING and forced into state SERVER_STOPPED. Crash log says Ticking block entity #### What you expected to happen: Server running normally as usual #### Steps to reproduce: 1.Start server 2.Wait for block entity 3.and crash ... ____ #### Affected Versions (Do *not* use "latest"): - EnderIO: 5.0.29 - EnderCore: 0.5.35 - Minecraft: 1.12.2 - Forge: 14.23.4.2729 #### Your most recent log file where the issue was present: https://pastebin.com/eVD9evme

1.0

Server crash ticking block entity - #### Issue Description: Server Crash #### What happens: When server is started it goes into SERVER_STOPPING and forced into state SERVER_STOPPED. Crash log says Ticking block entity #### What you expected to happen: Server running normally as usual #### Steps to reproduce: 1.Start server 2.Wait for block entity 3.and crash ... ____ #### Affected Versions (Do *not* use "latest"): - EnderIO: 5.0.29 - EnderCore: 0.5.35 - Minecraft: 1.12.2 - Forge: 14.23.4.2729 #### Your most recent log file where the issue was present: https://pastebin.com/eVD9evme

non_priority

server crash ticking block entity issue description server crash what happens when server is started it goes into server stopping and forced into state server stopped crash log says ticking block entity what you expected to happen server running normally as usual steps to reproduce start server wait for block entity and crash affected versions do not use latest enderio endercore minecraft forge your most recent log file where the issue was present

IssuesEvent

2021-03-27 12:15:27

emilykaldwin1827/goof

https://api.github.com/repos/emilykaldwin1827/goof

closed

WS-2019-0064 (High) detected in handlebars-4.0.11.tgz

security vulnerability

## WS-2019-0064 - High Severity Vulnerability <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>handlebars-4.0.11.tgz</b></p></summary> <p>Handlebars provides the power necessary to let you build semantic templates effectively with no frustration</p> <p>Library home page: <a href="https://registry.npmjs.org/handlebars/-/handlebars-4.0.11.tgz">https://registry.npmjs.org/handlebars/-/handlebars-4.0.11.tgz</a></p> <p>Path to dependency file: goof/package.json</p> <p>Path to vulnerable library: goof/node_modules/nyc/node_modules/handlebars/package.json</p> <p> Dependency Hierarchy: - tap-11.1.5.tgz (Root Library) - nyc-11.9.0.tgz - istanbul-reports-1.4.0.tgz - :x: **handlebars-4.0.11.tgz** (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/emilykaldwin1827/goof/commit/27563f2447d85b487d3c44ea67f0f561f0c44b91">27563f2447d85b487d3c44ea67f0f561f0c44b91</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> Versions of handlebars prior to 4.0.14 are vulnerable to Prototype Pollution. Templates may alter an Objects' prototype, thus allowing an attacker to execute arbitrary code on the server. <p>Publish Date: 2019-01-30 <p>URL: <a href=https://github.com/wycats/handlebars.js/compare/v4.1.1...v4.1.2>WS-2019-0064</a></p> </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 2 Score Details (<b>8.0</b>)</summary> <p> Base Score Metrics not available</p> </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary> <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://www.npmjs.com/advisories/755/versions">https://www.npmjs.com/advisories/755/versions</a></p> <p>Release Date: 2019-04-30</p> <p>Fix Resolution: 1.0.6-2,4.0.14,4.1.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

WS-2019-0064 (High) detected in handlebars-4.0.11.tgz - ## WS-2019-0064 - High Severity Vulnerability <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>handlebars-4.0.11.tgz</b></p></summary> <p>Handlebars provides the power necessary to let you build semantic templates effectively with no frustration</p> <p>Library home page: <a href="https://registry.npmjs.org/handlebars/-/handlebars-4.0.11.tgz">https://registry.npmjs.org/handlebars/-/handlebars-4.0.11.tgz</a></p> <p>Path to dependency file: goof/package.json</p> <p>Path to vulnerable library: goof/node_modules/nyc/node_modules/handlebars/package.json</p> <p> Dependency Hierarchy: - tap-11.1.5.tgz (Root Library) - nyc-11.9.0.tgz - istanbul-reports-1.4.0.tgz - :x: **handlebars-4.0.11.tgz** (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/emilykaldwin1827/goof/commit/27563f2447d85b487d3c44ea67f0f561f0c44b91">27563f2447d85b487d3c44ea67f0f561f0c44b91</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> Versions of handlebars prior to 4.0.14 are vulnerable to Prototype Pollution. Templates may alter an Objects' prototype, thus allowing an attacker to execute arbitrary code on the server. <p>Publish Date: 2019-01-30 <p>URL: <a href=https://github.com/wycats/handlebars.js/compare/v4.1.1...v4.1.2>WS-2019-0064</a></p> </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 2 Score Details (<b>8.0</b>)</summary> <p> Base Score Metrics not available</p> </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary> <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://www.npmjs.com/advisories/755/versions">https://www.npmjs.com/advisories/755/versions</a></p> <p>Release Date: 2019-04-30</p> <p>Fix Resolution: 1.0.6-2,4.0.14,4.1.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

ws high detected in handlebars tgz ws high severity vulnerability vulnerable library handlebars tgz handlebars provides the power necessary to let you build semantic templates effectively with no frustration library home page a href path to dependency file goof package json path to vulnerable library goof node modules nyc node modules handlebars package json dependency hierarchy tap tgz root library nyc tgz istanbul reports tgz x handlebars tgz vulnerable library found in head commit a href found in base branch master vulnerability details versions of handlebars prior to are vulnerable to prototype pollution templates may alter an objects prototype thus allowing an attacker to execute arbitrary code on the server publish date url a href cvss score details base score metrics not available suggested fix type upgrade version origin a href release date fix resolution step up your open source security game with whitesource

IssuesEvent

2023-03-16 20:27:36

gravitational/teleport

https://api.github.com/repos/gravitational/teleport

closed

[v.12.x] /docs/pages/choose-an-edition/teleport-enterprise/introduction.mdx

documentation

## Applies To <!-- List the URL(s) for existing docs this issue relates to. If this is a proposal for a new doc, you can suggest a path and title here. --> ## Details Describe the documentation improvements you wish to see. ## Related Issues <!-- If an existing issue relates to this one, please include it here for reference. -->

1.0

[v.12.x] /docs/pages/choose-an-edition/teleport-enterprise/introduction.mdx - ## Applies To <!-- List the URL(s) for existing docs this issue relates to. If this is a proposal for a new doc, you can suggest a path and title here. --> ## Details Describe the documentation improvements you wish to see. ## Related Issues <!-- If an existing issue relates to this one, please include it here for reference. -->

non_priority

docs pages choose an edition teleport enterprise introduction mdx applies to details describe the documentation improvements you wish to see related issues

IssuesEvent

2022-09-21 16:09:39

vector-im/element-web

https://api.github.com/repos/vector-im/element-web

opened

EC video room PIP should hide nametags (or position them more intelligently)

T-Defect

### Steps to reproduce <img width="387" alt="Screenshot 2022-09-21 at 17 06 35" src="https://user-images.githubusercontent.com/1294269/191555568-2b0ef6be-df99-43cb-8948-b722fe15ae29.png"> ### Outcome #### What did you expect? Nametags which are not massively intrusive #### What happened instead? I can't see folks! ### Operating system macOS ### Browser information Chrome ### URL for webapp develop ### Application version _No response_ ### Homeserver matrix.org ### Will you send logs? No

1.0

EC video room PIP should hide nametags (or position them more intelligently) - ### Steps to reproduce <img width="387" alt="Screenshot 2022-09-21 at 17 06 35" src="https://user-images.githubusercontent.com/1294269/191555568-2b0ef6be-df99-43cb-8948-b722fe15ae29.png"> ### Outcome #### What did you expect? Nametags which are not massively intrusive #### What happened instead? I can't see folks! ### Operating system macOS ### Browser information Chrome ### URL for webapp develop ### Application version _No response_ ### Homeserver matrix.org ### Will you send logs? No

non_priority

ec video room pip should hide nametags or position them more intelligently steps to reproduce img width alt screenshot at src outcome what did you expect nametags which are not massively intrusive what happened instead i can t see folks operating system macos browser information chrome url for webapp develop application version no response homeserver matrix org will you send logs no

IssuesEvent

2020-07-06 09:15:10

greatnewcls/KNLWKKGOTE62XGFSVAZIMVUH

https://api.github.com/repos/greatnewcls/KNLWKKGOTE62XGFSVAZIMVUH

closed

S2hk/Hz17fnJemQZaXQ6WXLs3t2upJW5DEQpYk0Sx+hL53CT/PZVWpiF9Z99OfJVtviH7QVicEXp4otLLbWhFofnlKC8K2ZlzsmW57XQas9MJIU8J0Fmw6xmMXaqEJ46V+MMwzL22r6hkwzEBqf9d3k9+0w1s+3w6Xsun/j9gn4=

design

mpZVGlPA/UoBcG1CAl40A4yX1fK+O37hLwrBcWqUiwxjHukgSQYdIp5nr+s4mjNev6e/3vmTSDWO1Oxd+ASvQfAC+tsIgcvgq/iaO1kuyz0ImLSjxCs0fvz8vzhyyNyQnVAaGBXIAA9XbXPXRTcX9wQgaqp8jGqoRRuHZPtzsfL+lBIIHE0ANQ2uJkoMhj4rr80a/JPoFUKJmh+wDIJ+YLcLDvUVsPkaehWtvhYgentTmfl/R2PFSIXaXpebgsqWINwiHnmCbxY1P0ocn5WzIT+5boSOd2AcsPVH5vfeFlMmbpE9Z+Zp6nVcwvVjdZv2ckk3KOb7oScR0Iq8EctURwWHg/JeZFPaLTcIuRstPaOVX9QXJEyA0fQyqyOk8dW0uOun7Q7lqsJpihhLGG/gPJuImi6ca7D9+SQGDWGcRf5DGSJ3w0vB1wKU+MLIT5GDXiU3+k3Jfdz+HAbZlKiIEoA59NLwVUoonw9ZWXbya2Y+wbmj1OA/AppC+/TxRDXpz/5N1cxcQEnfV5Yd64hAoghEnsHgevky4Bb9cMqHyMFmvBwGQsjT8ZjRIChn02AObCQQtGaaty39RQG++is7QC5fOReZ/2dPovOFPfsu3TYDb4h2kOXRaElplJshMgonzGbiNnF7jdO1tSEohGw3J6su1GFCPKRW0ceixdQ7gYkj86zJorXNpXA/8KOFvtkR1Iv1Pui22U2oZa7+srOI3Cf8OINUjp4o3VP1biQtoJkhL7Ng29wRScGP/ygZ6piYRSmo2D0278ou3RZfY54Un0s6Rg3E+1RqOFxKn2YILHYnndeH4czt13ZoXeeyBn90

1.0

S2hk/Hz17fnJemQZaXQ6WXLs3t2upJW5DEQpYk0Sx+hL53CT/PZVWpiF9Z99OfJVtviH7QVicEXp4otLLbWhFofnlKC8K2ZlzsmW57XQas9MJIU8J0Fmw6xmMXaqEJ46V+MMwzL22r6hkwzEBqf9d3k9+0w1s+3w6Xsun/j9gn4= - mpZVGlPA/UoBcG1CAl40A4yX1fK+O37hLwrBcWqUiwxjHukgSQYdIp5nr+s4mjNev6e/3vmTSDWO1Oxd+ASvQfAC+tsIgcvgq/iaO1kuyz0ImLSjxCs0fvz8vzhyyNyQnVAaGBXIAA9XbXPXRTcX9wQgaqp8jGqoRRuHZPtzsfL+lBIIHE0ANQ2uJkoMhj4rr80a/JPoFUKJmh+wDIJ+YLcLDvUVsPkaehWtvhYgentTmfl/R2PFSIXaXpebgsqWINwiHnmCbxY1P0ocn5WzIT+5boSOd2AcsPVH5vfeFlMmbpE9Z+Zp6nVcwvVjdZv2ckk3KOb7oScR0Iq8EctURwWHg/JeZFPaLTcIuRstPaOVX9QXJEyA0fQyqyOk8dW0uOun7Q7lqsJpihhLGG/gPJuImi6ca7D9+SQGDWGcRf5DGSJ3w0vB1wKU+MLIT5GDXiU3+k3Jfdz+HAbZlKiIEoA59NLwVUoonw9ZWXbya2Y+wbmj1OA/AppC+/TxRDXpz/5N1cxcQEnfV5Yd64hAoghEnsHgevky4Bb9cMqHyMFmvBwGQsjT8ZjRIChn02AObCQQtGaaty39RQG++is7QC5fOReZ/2dPovOFPfsu3TYDb4h2kOXRaElplJshMgonzGbiNnF7jdO1tSEohGw3J6su1GFCPKRW0ceixdQ7gYkj86zJorXNpXA/8KOFvtkR1Iv1Pui22U2oZa7+srOI3Cf8OINUjp4o3VP1biQtoJkhL7Ng29wRScGP/ygZ6piYRSmo2D0278ou3RZfY54Un0s6Rg3E+1RqOFxKn2YILHYnndeH4czt13ZoXeeyBn90

non_priority

mpzvglpa asvqfac tsigcvgq jpofukjmh wdij ylcldvuvspkaehwtvhygenttmfl appc txrdxpz

IssuesEvent

2020-04-13 21:59:48

Azure-Samples/Cognitive-Services-Voice-Assistant

https://api.github.com/repos/Azure-Samples/Cognitive-Services-Voice-Assistant

opened

For RPI add instructions to make a service

Devices Console Client (C++) documentation enhancement

<!-- IF SUFFICIENT INFORMATION IS NOT PROVIDED VIA THE FOLLOWING TEMPLATE THE ISSUE MIGHT BE CLOSED WITHOUT FURTHER CONSIDERATION OR INVESTIGATION --> > Please provide us with the following information: > --------------------------------------------------------------- It should be possible to have the RPi client run from boot. ### This issue is for a: (mark with an `x`) ``` - [ ] bug report -> please search issues before submitting - [X] feature request - [X] documentation issue or request - [ ] regression (a behavior that used to work and stopped in a new release) ``` ### Minimal steps to reproduce > ### Any log messages given by the failure > ### Expected/desired behavior > ### OS and Version? > Windows 7, 8 or 10. Linux (which distribution). macOS (Yosemite? El Capitan? Sierra?) ### Versions > ### Mention any other details that might be useful > --------------------------------------------------------------- > Thanks! We'll be in touch soon.

1.0

For RPI add instructions to make a service - <!-- IF SUFFICIENT INFORMATION IS NOT PROVIDED VIA THE FOLLOWING TEMPLATE THE ISSUE MIGHT BE CLOSED WITHOUT FURTHER CONSIDERATION OR INVESTIGATION --> > Please provide us with the following information: > --------------------------------------------------------------- It should be possible to have the RPi client run from boot. ### This issue is for a: (mark with an `x`) ``` - [ ] bug report -> please search issues before submitting - [X] feature request - [X] documentation issue or request - [ ] regression (a behavior that used to work and stopped in a new release) ``` ### Minimal steps to reproduce > ### Any log messages given by the failure > ### Expected/desired behavior > ### OS and Version? > Windows 7, 8 or 10. Linux (which distribution). macOS (Yosemite? El Capitan? Sierra?) ### Versions > ### Mention any other details that might be useful > --------------------------------------------------------------- > Thanks! We'll be in touch soon.

non_priority

for rpi add instructions to make a service if sufficient information is not provided via the following template the issue might be closed without further consideration or investigation please provide us with the following information it should be possible to have the rpi client run from boot this issue is for a mark with an x bug report please search issues before submitting feature request documentation issue or request regression a behavior that used to work and stopped in a new release minimal steps to reproduce any log messages given by the failure expected desired behavior os and version windows or linux which distribution macos yosemite el capitan sierra versions mention any other details that might be useful thanks we ll be in touch soon

IssuesEvent

2016-08-15 09:37:34

venusdrogon/feilong-core

https://api.github.com/repos/venusdrogon/feilong-core

closed

com.feilong.core.text.NumberFormatUtilTest 在 jdk8 下面测试不通过

bug test

`com.feilong.core.text.NumberFormatUtilTest `在`jdk7` 下可以测试通过, 但是 `jdk8 `下测试不通过 **代码如下:** ```JAVA /** * Test format 32. */ @Test public void testFormat32(){ assertEquals("1.2", NumberFormatUtil.format(1.15, "#####.#", RoundingMode.HALF_EVEN)); assertEquals("1.2", NumberFormatUtil.format(1.25, "#####.#", RoundingMode.HALF_EVEN)); assertEquals("1.3", NumberFormatUtil.format(1.251, "#####.#", RoundingMode.HALF_EVEN)); assertEquals("-1.2", NumberFormatUtil.format(-1.15, "#####.#", RoundingMode.HALF_EVEN)); assertEquals("-1.2", NumberFormatUtil.format(-1.25, "#####.#", RoundingMode.HALF_EVEN)); assertEquals("-1.3", NumberFormatUtil.format(-1.251, "#####.#", RoundingMode.HALF_EVEN)); } /** * Test format 321. */ @Test public void testFormat321(){ assertEquals("1.2", NumberFormatUtil.format(1.15, "#####.#", null)); assertEquals("1.3", NumberFormatUtil.format(1.25, "#####.#", null)); assertEquals("1.3", NumberFormatUtil.format(1.251, "#####.#", null)); assertEquals("-1.2", NumberFormatUtil.format(-1.15, "#####.#", null)); assertEquals("-1.3", NumberFormatUtil.format(-1.25, "#####.#", null)); assertEquals("-1.3", NumberFormatUtil.format(-1.251, "#####.#", null)); } /** * Test format 111. */ @Test public void testFormat111(){ assertEquals("1.2", NumberFormatUtil.format(1.15, "#####.#")); assertEquals("1.3", NumberFormatUtil.format(1.25, "#####.#")); assertEquals("1.3", NumberFormatUtil.format(1.251, "#####.#")); assertEquals("-1.2", NumberFormatUtil.format(-1.15, "#####.#")); assertEquals("-1.3", NumberFormatUtil.format(-1.25, "#####.#")); assertEquals("-1.3", NumberFormatUtil.format(-1.251, "#####.#")); } ``` `jdk8` 测试运行结果:  jdk8 版本信息  java version "1.8.0_45"

1.0

com.feilong.core.text.NumberFormatUtilTest 在 jdk8 下面测试不通过 - `com.feilong.core.text.NumberFormatUtilTest `在`jdk7` 下可以测试通过, 但是 `jdk8 `下测试不通过 **代码如下:** ```JAVA /** * Test format 32. */ @Test public void testFormat32(){ assertEquals("1.2", NumberFormatUtil.format(1.15, "#####.#", RoundingMode.HALF_EVEN)); assertEquals("1.2", NumberFormatUtil.format(1.25, "#####.#", RoundingMode.HALF_EVEN)); assertEquals("1.3", NumberFormatUtil.format(1.251, "#####.#", RoundingMode.HALF_EVEN)); assertEquals("-1.2", NumberFormatUtil.format(-1.15, "#####.#", RoundingMode.HALF_EVEN)); assertEquals("-1.2", NumberFormatUtil.format(-1.25, "#####.#", RoundingMode.HALF_EVEN)); assertEquals("-1.3", NumberFormatUtil.format(-1.251, "#####.#", RoundingMode.HALF_EVEN)); } /** * Test format 321. */ @Test public void testFormat321(){ assertEquals("1.2", NumberFormatUtil.format(1.15, "#####.#", null)); assertEquals("1.3", NumberFormatUtil.format(1.25, "#####.#", null)); assertEquals("1.3", NumberFormatUtil.format(1.251, "#####.#", null)); assertEquals("-1.2", NumberFormatUtil.format(-1.15, "#####.#", null)); assertEquals("-1.3", NumberFormatUtil.format(-1.25, "#####.#", null)); assertEquals("-1.3", NumberFormatUtil.format(-1.251, "#####.#", null)); } /** * Test format 111. */ @Test public void testFormat111(){ assertEquals("1.2", NumberFormatUtil.format(1.15, "#####.#")); assertEquals("1.3", NumberFormatUtil.format(1.25, "#####.#")); assertEquals("1.3", NumberFormatUtil.format(1.251, "#####.#")); assertEquals("-1.2", NumberFormatUtil.format(-1.15, "#####.#")); assertEquals("-1.3", NumberFormatUtil.format(-1.25, "#####.#")); assertEquals("-1.3", NumberFormatUtil.format(-1.251, "#####.#")); } ``` `jdk8` 测试运行结果:  jdk8 版本信息  java version "1.8.0_45"

non_priority

com feilong core text numberformatutiltest 在 下面测试不通过 com feilong core text numberformatutiltest 在 下可以测试通过 但是 下测试不通过 代码如下 java test format test public void assertequals numberformatutil format roundingmode half even assertequals numberformatutil format roundingmode half even assertequals numberformatutil format roundingmode half even assertequals numberformatutil format roundingmode half even assertequals numberformatutil format roundingmode half even assertequals numberformatutil format roundingmode half even test format test public void assertequals numberformatutil format null assertequals numberformatutil format null assertequals numberformatutil format null assertequals numberformatutil format null assertequals numberformatutil format null assertequals numberformatutil format null test format test public void assertequals numberformatutil format assertequals numberformatutil format assertequals numberformatutil format assertequals numberformatutil format assertequals numberformatutil format assertequals numberformatutil format 测试运行结果 版本信息 java version

IssuesEvent

2023-01-30 06:41:41

fluttercandies/extended_image

https://api.github.com/repos/fluttercandies/extended_image

closed

[Build Error Android] Error: Too few positional arguments: 4 required, 3 given.

flutter sdk build error

Hi, I migrated the flutter to the master channel: **3.6.0-4.0.pre.32** and the Android build failing :( with error: ``` ../../../AppData/Local/Pub/Cache/hosted/pub.dev/extended_image-7.0.0-dev.1/lib/src/gesture/page_view/widgets/scroll_activity.dart:56:12: Error: Too few positional arguments: 4 required, 3 given. ) : super( ^ Target kernel_snapshot failed: Exception FAILURE: Build failed with an exception. * Where: Script 'C:\tools\flutter\packages\flutter_tools\gradle\flutter.gradle' line: 1151 * What went wrong: Execution failed for task ':app:compileFlutterBuildDebug'. > Process 'command 'C:\tools\flutter\bin\flutter.bat'' finished with non-zero exit value 1 * Try: > Run with --stacktrace option to get the stack trace. > Run with --info or --debug option to get more log output. > Run with --scan to get full insights. * Get more help at https://help.gradle.org BUILD FAILED in 14s Running Gradle task 'assembleDebug'... 15.2s Exception: Gradle task assembleDebug failed with exit code 1 ```  Please help me to fix this issue, thanks in advance!

1.0

[Build Error Android] Error: Too few positional arguments: 4 required, 3 given. - Hi, I migrated the flutter to the master channel: **3.6.0-4.0.pre.32** and the Android build failing :( with error: ``` ../../../AppData/Local/Pub/Cache/hosted/pub.dev/extended_image-7.0.0-dev.1/lib/src/gesture/page_view/widgets/scroll_activity.dart:56:12: Error: Too few positional arguments: 4 required, 3 given. ) : super( ^ Target kernel_snapshot failed: Exception FAILURE: Build failed with an exception. * Where: Script 'C:\tools\flutter\packages\flutter_tools\gradle\flutter.gradle' line: 1151 * What went wrong: Execution failed for task ':app:compileFlutterBuildDebug'. > Process 'command 'C:\tools\flutter\bin\flutter.bat'' finished with non-zero exit value 1 * Try: > Run with --stacktrace option to get the stack trace. > Run with --info or --debug option to get more log output. > Run with --scan to get full insights. * Get more help at https://help.gradle.org BUILD FAILED in 14s Running Gradle task 'assembleDebug'... 15.2s Exception: Gradle task assembleDebug failed with exit code 1 ```  Please help me to fix this issue, thanks in advance!

non_priority

error too few positional arguments required given hi i migrated the flutter to the master channel pre and the android build failing with error appdata local pub cache hosted pub dev extended image dev lib src gesture page view widgets scroll activity dart error too few positional arguments required given super target kernel snapshot failed exception failure build failed with an exception where script c tools flutter packages flutter tools gradle flutter gradle line what went wrong execution failed for task app compileflutterbuilddebug process command c tools flutter bin flutter bat finished with non zero exit value try run with stacktrace option to get the stack trace run with info or debug option to get more log output run with scan to get full insights get more help at build failed in running gradle task assembledebug exception gradle task assembledebug failed with exit code please help me to fix this issue thanks in advance

IssuesEvent

2021-02-15 01:31:05

tajmone/pmotion-assets

https://api.github.com/repos/tajmone/pmotion-assets

closed

Must define unused DLL functions

:books: documentation :electric_plug: file I/O plugins :electric_plug: plugins :warning: important

_Missing info on DLL functions._ I need to understand if DLL functions specifically targeting import or export functionality can be left out entirely in those plug-ins that won't use them — i.e. if these functions still require defining `DLLProcedure`s that do nothing, or if they can simply be omitted since PM wouldn't try to call them after having acknowledged the plug-in supported features via the registration functions. For example, an import plug-in shouldn’t expect any calls to `beginWrite()` or `writeNextImage()`, and an export plug-in shouldn’t expect any calls to `getTransparentColor()` or `isAlphaEnabled()`. For more info, see also: - [Cosmigo Forum » _HELP: More File I/O Interface Clarifications_] - tajmone/pmotion-purebasic#2 [Cosmigo Forum » _HELP: More File I/O Interface Clarifications_]: https://community.cosmigo.com/t/help-more-file-i-o-interface-clarifications/739 <!-- EOF -->

1.0

Must define unused DLL functions - _Missing info on DLL functions._ I need to understand if DLL functions specifically targeting import or export functionality can be left out entirely in those plug-ins that won't use them — i.e. if these functions still require defining `DLLProcedure`s that do nothing, or if they can simply be omitted since PM wouldn't try to call them after having acknowledged the plug-in supported features via the registration functions. For example, an import plug-in shouldn’t expect any calls to `beginWrite()` or `writeNextImage()`, and an export plug-in shouldn’t expect any calls to `getTransparentColor()` or `isAlphaEnabled()`. For more info, see also: - [Cosmigo Forum » _HELP: More File I/O Interface Clarifications_] - tajmone/pmotion-purebasic#2 [Cosmigo Forum » _HELP: More File I/O Interface Clarifications_]: https://community.cosmigo.com/t/help-more-file-i-o-interface-clarifications/739 <!-- EOF -->

non_priority

must define unused dll functions missing info on dll functions i need to understand if dll functions specifically targeting import or export functionality can be left out entirely in those plug ins that won t use them — i e if these functions still require defining dllprocedure s that do nothing or if they can simply be omitted since pm wouldn t try to call them after having acknowledged the plug in supported features via the registration functions for example an import plug in shouldn’t expect any calls to beginwrite or writenextimage and an export plug in shouldn’t expect any calls to gettransparentcolor or isalphaenabled for more info see also tajmone pmotion purebasic

IssuesEvent

2022-11-22 13:23:58

lowRISC/opentitan

https://api.github.com/repos/lowRISC/opentitan

opened

[test-triage,spi_host] spi_host_sw_reset only asserts sw_reset after transaction has ended

Component:TestTriage

### Hierarchy of regression failure Block level ### Failure Description `spi_host_sw_reset` test does not actually assert the sw_reset during the transaction, but only after a transaction has ended. I checked a bunch of seeds and they were all the same. [- Test description](https://github.com/lowRISC/opentitan/blob/4d991c505ad6f0bd9b03967652d722a9909fe6c6/hw/ip/spi_host/data/spi_host_testplan.hjson#L108-L123) The testplan does not explicitly say 'within a transaction' but that is implied here. ### Steps to Reproduce - GitHub Revision: 0986f40632 - dvsim invocation command to reproduce the failure, inclusive of build and run seeds: `util/dvsim/dvsim.py hw/ip/spi_host/dv/spi_host_sim_cfg.hjson -i spi_host_sw_reset --fixed-seed 1088210569` ### Tests with similar or related failures _No response_

1.0

[test-triage,spi_host] spi_host_sw_reset only asserts sw_reset after transaction has ended - ### Hierarchy of regression failure Block level ### Failure Description `spi_host_sw_reset` test does not actually assert the sw_reset during the transaction, but only after a transaction has ended. I checked a bunch of seeds and they were all the same. [- Test description](https://github.com/lowRISC/opentitan/blob/4d991c505ad6f0bd9b03967652d722a9909fe6c6/hw/ip/spi_host/data/spi_host_testplan.hjson#L108-L123) The testplan does not explicitly say 'within a transaction' but that is implied here. ### Steps to Reproduce - GitHub Revision: 0986f40632 - dvsim invocation command to reproduce the failure, inclusive of build and run seeds: `util/dvsim/dvsim.py hw/ip/spi_host/dv/spi_host_sim_cfg.hjson -i spi_host_sw_reset --fixed-seed 1088210569` ### Tests with similar or related failures _No response_

non_priority

spi host sw reset only asserts sw reset after transaction has ended hierarchy of regression failure block level failure description spi host sw reset test does not actually assert the sw reset during the transaction but only after a transaction has ended i checked a bunch of seeds and they were all the same the testplan does not explicitly say within a transaction but that is implied here steps to reproduce github revision dvsim invocation command to reproduce the failure inclusive of build and run seeds util dvsim dvsim py hw ip spi host dv spi host sim cfg hjson i spi host sw reset fixed seed tests with similar or related failures no response

IssuesEvent

2022-05-01 11:36:46

joomla/joomla-cms

https://api.github.com/repos/joomla/joomla-cms

closed

[4.1.x] Cassiopea Registration page Privacy/Terms alignment

New Feature No Code Attached Yet J4 Frontend Template

Hi guys, about the [Cassiopea Registration page Privacy/Terms alignment](https://photos.app.goo.gl/6VZuH7Ja7RQ8yfKt5 "Registration Privacy/Terms"), Should not be better to add by default: .required.radio { display: inline-flex; gap: 1rem; } to align them horizontally and don't waste precious space ?

1.0

[4.1.x] Cassiopea Registration page Privacy/Terms alignment - Hi guys, about the [Cassiopea Registration page Privacy/Terms alignment](https://photos.app.goo.gl/6VZuH7Ja7RQ8yfKt5 "Registration Privacy/Terms"), Should not be better to add by default: .required.radio { display: inline-flex; gap: 1rem; } to align them horizontally and don't waste precious space ?

non_priority

cassiopea registration page privacy terms alignment hi guys about the registration privacy terms should not be better to add by default required radio display inline flex gap to align them horizontally and don t waste precious space

IssuesEvent

2022-11-10 18:07:36

CozyPlantlady/yarn-guardian

https://api.github.com/repos/CozyPlantlady/yarn-guardian

closed

DESIGN: Use trashcan icon instead of "DELETE" text

task design

This would take less space in yarn and product cards

1.0

DESIGN: Use trashcan icon instead of "DELETE" text - This would take less space in yarn and product cards

non_priority

design use trashcan icon instead of delete text this would take less space in yarn and product cards

IssuesEvent

2019-12-23 15:47:40

cityofaustin/atd-vz-data

https://api.github.com/repos/cityofaustin/atd-vz-data

opened

VZV | Make motorcycle a separate mode category

Impact: 2-Major Need: 1-Must Have Project: Vision Zero Viewer Service: Dev Workgroup: VZ

Break out motorcycle as a separate mode category in all places in VZV where fatalities and serious injuries are broken down by mode. Currently there are two places in VZV where fatalities and serious injuries are broken down by mode; the mode visualizations in the Summary page and in the Map view.

1.0

VZV | Make motorcycle a separate mode category - Break out motorcycle as a separate mode category in all places in VZV where fatalities and serious injuries are broken down by mode. Currently there are two places in VZV where fatalities and serious injuries are broken down by mode; the mode visualizations in the Summary page and in the Map view.

non_priority

vzv make motorcycle a separate mode category break out motorcycle as a separate mode category in all places in vzv where fatalities and serious injuries are broken down by mode currently there are two places in vzv where fatalities and serious injuries are broken down by mode the mode visualizations in the summary page and in the map view

IssuesEvent

2021-06-21 09:50:40

astropy/astropy

https://api.github.com/repos/astropy/astropy

closed

[4.2rc1] Test failures on armel: no FPEs

Close? modeling testing wont-fix ¯\_(ツ)_/¯

### Description On the Debian "ARM 32 bit little Endian Soft Float" ("armel") platform, I get test failures since the platform seems to handle floating point errors differently. This is a regression, but it could probably be ignored? ### Expected behavior The tests should succeed ### Actual behavior I get the following two failures: ``` ______________________ test_linear_fit_model_set_weights _______________________ def test_linear_fit_model_set_weights(): […] with pytest.warns(RuntimeWarning, match=r'invalid value encountered in true_divide'): > fitted_model = fitter(init_model, x, np.ma.array(y, mask=np.isclose(weights, 0)), weights=weights) E Failed: DID NOT WARN. No warnings of type (<class 'RuntimeWarning'>,) was emitted. The list of emitted warnings is: []. astropy/modeling/tests/test_model_sets.py:392: Failed ``` and ``` ____________________ test_blackbody_exceptions_and_warnings ____________________ def test_blackbody_exceptions_and_warnings(): […] with pytest.warns(AstropyUserWarning, match='invalid') as w: bb(0 * u.AA) > assert len(w) == 3 # 2 of these are RuntimeWarning from zero divide E assert 1 == 3 E + where 1 = len(WarningsChecker(record=True)) astropy/modeling/tests/test_physical_models.py:119: AssertionError ``` ### Steps to Reproduce Build and test the package on armel ### System Details * Python 3.8.6, 3.9.0 * Numpy 1.19.4 * Astropy 4.2rc1 * Scipy 1.5.3 * Matplotlib 3.3.2

1.0

[4.2rc1] Test failures on armel: no FPEs - ### Description On the Debian "ARM 32 bit little Endian Soft Float" ("armel") platform, I get test failures since the platform seems to handle floating point errors differently. This is a regression, but it could probably be ignored? ### Expected behavior The tests should succeed ### Actual behavior I get the following two failures: ``` ______________________ test_linear_fit_model_set_weights _______________________ def test_linear_fit_model_set_weights(): […] with pytest.warns(RuntimeWarning, match=r'invalid value encountered in true_divide'): > fitted_model = fitter(init_model, x, np.ma.array(y, mask=np.isclose(weights, 0)), weights=weights) E Failed: DID NOT WARN. No warnings of type (<class 'RuntimeWarning'>,) was emitted. The list of emitted warnings is: []. astropy/modeling/tests/test_model_sets.py:392: Failed ``` and ``` ____________________ test_blackbody_exceptions_and_warnings ____________________ def test_blackbody_exceptions_and_warnings(): […] with pytest.warns(AstropyUserWarning, match='invalid') as w: bb(0 * u.AA) > assert len(w) == 3 # 2 of these are RuntimeWarning from zero divide E assert 1 == 3 E + where 1 = len(WarningsChecker(record=True)) astropy/modeling/tests/test_physical_models.py:119: AssertionError ``` ### Steps to Reproduce Build and test the package on armel ### System Details * Python 3.8.6, 3.9.0 * Numpy 1.19.4 * Astropy 4.2rc1 * Scipy 1.5.3 * Matplotlib 3.3.2

non_priority

test failures on armel no fpes description on the debian arm bit little endian soft float armel platform i get test failures since the platform seems to handle floating point errors differently this is a regression but it could probably be ignored expected behavior the tests should succeed actual behavior i get the following two failures test linear fit model set weights def test linear fit model set weights with pytest warns runtimewarning match r invalid value encountered in true divide fitted model fitter init model x np ma array y mask np isclose weights weights weights e failed did not warn no warnings of type was emitted the list of emitted warnings is astropy modeling tests test model sets py failed and test blackbody exceptions and warnings def test blackbody exceptions and warnings with pytest warns astropyuserwarning match invalid as w bb u aa assert len w of these are runtimewarning from zero divide e assert e where len warningschecker record true astropy modeling tests test physical models py assertionerror steps to reproduce build and test the package on armel system details python numpy astropy scipy matplotlib

IssuesEvent

2022-04-18 05:59:16

taosdata/TDengine

https://api.github.com/repos/taosdata/TDengine

closed

when using jdbcTemplate.batchUpdate to insert，it is single-row insert,Shall we have batch-rows insert?

performance

 jdbcTemplate.batchUpdate插入数据时，不支持批量插入,速度很慢。

True

when using jdbcTemplate.batchUpdate to insert，it is single-row insert,Shall we have batch-rows insert? -  jdbcTemplate.batchUpdate插入数据时，不支持批量插入,速度很慢。

non_priority

when using jdbctemplate batchupdate to insert，it is single row insert shall we have batch rows insert jdbctemplate batchupdate插入数据时，不支持批量插入 速度很慢。

IssuesEvent

2022-11-24 16:07:25

SAP/fundamental-ngx

https://api.github.com/repos/SAP/fundamental-ngx

closed

bug: approval-flow(platform) - checkbox present when all actions disabled/hidden

bug platform ariba Low E2E automation

#### Is this a bug, enhancement, or feature request? bug #### Briefly describe your proposal. when all node options are disabled, the checkbox is present even though it has no functionality #### Which versions of Angular and Fundamental Library for Angular are affected? (If this is a feature request, use current version.) v0.33.0-rc.57 #### If this is a bug, please provide steps for reproducing it. 1. go to https://fundamental-ngx.netlify.app/#/platform/approval-flow 2. click the option to disable all node actions 3. click the edit button 4. look at nodes (cards) **Actual results:** check box present with no functionality (options disabled and hidden) **Expected results:** will match functionality of overflow menu and be hidden when no actions available 

1.0

bug: approval-flow(platform) - checkbox present when all actions disabled/hidden - #### Is this a bug, enhancement, or feature request? bug #### Briefly describe your proposal. when all node options are disabled, the checkbox is present even though it has no functionality #### Which versions of Angular and Fundamental Library for Angular are affected? (If this is a feature request, use current version.) v0.33.0-rc.57 #### If this is a bug, please provide steps for reproducing it. 1. go to https://fundamental-ngx.netlify.app/#/platform/approval-flow 2. click the option to disable all node actions 3. click the edit button 4. look at nodes (cards) **Actual results:** check box present with no functionality (options disabled and hidden) **Expected results:** will match functionality of overflow menu and be hidden when no actions available 

non_priority

bug approval flow platform checkbox present when all actions disabled hidden is this a bug enhancement or feature request bug briefly describe your proposal when all node options are disabled the checkbox is present even though it has no functionality which versions of angular and fundamental library for angular are affected if this is a feature request use current version rc if this is a bug please provide steps for reproducing it go to click the option to disable all node actions click the edit button look at nodes cards actual results check box present with no functionality options disabled and hidden expected results will match functionality of overflow menu and be hidden when no actions available

IssuesEvent

2015-11-06 20:12:34

couchbase/sync_gateway

https://api.github.com/repos/couchbase/sync_gateway

closed

Compress WebSocket _changes messages

enhancement performance review

The WebSocket-based `_changes` feed (only used by the iOS client so far) doesn't have any compression. We can compress the individual WebSocket messages, using a single gzip context so each message takes advantage of the previous ones. Client side was already filed as https://github.com/couchbase/couchbase-lite-ios/issues/927. Details of the protocol changes are therein.

True

Compress WebSocket _changes messages - The WebSocket-based `_changes` feed (only used by the iOS client so far) doesn't have any compression. We can compress the individual WebSocket messages, using a single gzip context so each message takes advantage of the previous ones. Client side was already filed as https://github.com/couchbase/couchbase-lite-ios/issues/927. Details of the protocol changes are therein.

non_priority

compress websocket changes messages the websocket based changes feed only used by the ios client so far doesn t have any compression we can compress the individual websocket messages using a single gzip context so each message takes advantage of the previous ones client side was already filed as details of the protocol changes are therein

IssuesEvent

2020-03-09 12:30:31

bonitasoft-labs/bpmn-visu-js

https://api.github.com/repos/bonitasoft-labs/bpmn-visu-js

closed

[infra] 'npm run lint-check' missing plugin error on MacOS

bug infra:build

**Describe the bug** `lint-check` npm scripts fails because of missing pluing on MacOS Catalina (v10.15) **To Reproduce** See https://github.com/bonitasoft-labs/bpmn-visu-js/runs/479745740 from #19 Run `npm run lint-check` **Additional context** Error logs ``` Oops! Something went wrong! :( ESLint: 6.8.0. ESLint couldn't find the plugin "eslint-plugin-node". (The package "eslint-plugin-node" was not found when loaded as a Node module from the directory "/Users/runner/runners/2.165.2/work/bpmn-visu-js/bpmn-visu-js".) It's likely that the plugin isn't installed correctly. Try reinstalling by running the following: npm install eslint-plugin-node@latest --save-dev The plugin "eslint-plugin-node" was referenced from the config file in "node_modules/prettier-linter-helpers/.eslintrc.js". If you still can't figure out the problem, please stop by https://gitter.im/eslint/eslint to chat with the team. ```

1.0

[infra] 'npm run lint-check' missing plugin error on MacOS - **Describe the bug** `lint-check` npm scripts fails because of missing pluing on MacOS Catalina (v10.15) **To Reproduce** See https://github.com/bonitasoft-labs/bpmn-visu-js/runs/479745740 from #19 Run `npm run lint-check` **Additional context** Error logs ``` Oops! Something went wrong! :( ESLint: 6.8.0. ESLint couldn't find the plugin "eslint-plugin-node". (The package "eslint-plugin-node" was not found when loaded as a Node module from the directory "/Users/runner/runners/2.165.2/work/bpmn-visu-js/bpmn-visu-js".) It's likely that the plugin isn't installed correctly. Try reinstalling by running the following: npm install eslint-plugin-node@latest --save-dev The plugin "eslint-plugin-node" was referenced from the config file in "node_modules/prettier-linter-helpers/.eslintrc.js". If you still can't figure out the problem, please stop by https://gitter.im/eslint/eslint to chat with the team. ```

non_priority

npm run lint check missing plugin error on macos describe the bug lint check npm scripts fails because of missing pluing on macos catalina to reproduce see from run npm run lint check additional context error logs oops something went wrong eslint eslint couldn t find the plugin eslint plugin node the package eslint plugin node was not found when loaded as a node module from the directory users runner runners work bpmn visu js bpmn visu js it s likely that the plugin isn t installed correctly try reinstalling by running the following npm install eslint plugin node latest save dev the plugin eslint plugin node was referenced from the config file in node modules prettier linter helpers eslintrc js if you still can t figure out the problem please stop by to chat with the team

IssuesEvent

2017-05-24 07:59:04

geetsisbac/HYUDMDQI7KH46FHYFHPJLMSI

https://api.github.com/repos/geetsisbac/HYUDMDQI7KH46FHYFHPJLMSI

reopened

ikt9HYd0d7PNss4L7q/JPjeyN5h1HcmHlq9zQpDYtBlryIMbpWYvaWRdIKItBeZ/tEKHAePGqbd6Sju5f56OM05uet65FKg94kUSadTjIcWqkj9s+v72BBRAjBF8IQCazdF8l8Vt7Bfgs2VPmt9j1ql1vJtHsGKvx+AII0zzn2g=

design

uS+neMhfCVf6fzRew08RQztbV5gKijTA8S0J/MKPuFD56XyGlOU42tMem9DIdlP6dHYokI8obPjDmqQRhoiqLymCn6I8VzyNCIVKxq+wQBcfvzL47thjouAXIG6cUG/KXdw3MPVG4MdBJiWyOxOHqgJhL5XpT025ZqMeNwyLChFYgbnI4tqzy9+Hy/Me/ZrIAmEvlelPTblmox43DIsKESMFejoiRd0SKuQ/z27qFFXQa1ERjzyoKfhM+YCHmhYP+yjXN8lUHd78tuv4bmWb4w+UrKia41abbzjU44H13PvA/6kVqj1Fy1yeD6+z94dut/AMjx3F1jp8n0Y64cJdETye9r88Dzq8BAn1Z3z/GIFvmIGtjyKZSt45pAv7bNdfYK5dfO+Ap+EnpLiGxQc4CQJhL5XpT025ZqMeNwyLChF8hw+Ba4PeFnltVOIxz/ZDAmEvlelPTblmox43DIsKEQJhL5XpT025ZqMeNwyLChEPVkE70fNjAaYoidJFo/wLAmEvlelPTblmox43DIsKEYCsr1tTFPKoowmr00rX7S4CYS+V6U9NuWajHjcMiwoRnRHbMLCXU4No+K/2y4ZR49nwr7xxwXj7LiQF8DP2fYlVdx4pJoxC4UJoFGLSAjCc8XV6jccGBfWhSyQBOzrmjvA/IKZE1NgwFrJivqDTHrRZs4yS0UFXq9nHTvi2ru67LLDSmBGREpeYZTCi5gCsg/k9u+JA/lSCea5gYaykaEkEnPWoR2MlrDVAcnFkWp50AmEvlelPTblmox43DIsKEYVj9CigqAzOPu26yUdakg4CYS+V6U9NuWajHjcMiwoRAmEvlelPTblmox43DIsKEcEooKnhtf+M7YPfuS/cYYQCYS+V6U9NuWajHjcMiwoRfVgVUw3AUN+Xjd9Qax+ZDwJhL5XpT025ZqMeNwyLChECYS+V6U9NuWajHjcMiwoRGHX6atmoZdMV1LOzP6cM/zQvknCUzSGVcKR8pEiCaSHtPEWqNr0a1AbDa2QkSeFm2XQOkhr/63Al+0G1DHyeAoCWIHWnI3KrA5Wcj9e5CXgEYB1Un/JP+2yNiVOwPz34/3Fkaa7LbpBKbgeMy0qYSAl2/pXmyyRHcRR5NpQ0S/iOcbbqWxi7oXtQ99AGRQI3AmEvlelPTblmox43DIsKEVqb0ti2DktF50H14jqCZtECYS+V6U9NuWajHjcMiwoRWvDmiBoJDdq1esSw0nJKWQJhL5XpT025ZqMeNwyLChHy5SnjWY7E8iQXuPNKEBL+AmEvlelPTblmox43DIsKEQJhL5XpT025ZqMeNwyLChHylnrEo2f6VYXHytIYX5zLwHhM8jIr6GARAUOdAPYzeSeHjpdL0cZws89iztFZhWcBtbQztvi/u9Pm+BC2V68nDU7njew5EADnH3u4RfRcRmkQzeFaPF9ag61F9o9NXzj4LXRfgg5kbiJdTkljY2TmNtnex1M5VyhONUU0Bt8VcKxnGJFURPws1eBjuk/Rji02SEDleq7XdmhIUj4O6bBpdN5fb+m4J2xxprWAU3dNVgJhL5XpT025ZqMeNwyLChEOmZgiisG2FOuFqDOJopvdAmEvlelPTblmox43DIsKEQJhL5XpT025ZqMeNwyLChG2KYTG7Ua1NKYurtiPRBKIAmEvlelPTblmox43DIsKEa2lVtz0tXro+FBOs5Lm2N4CYS+V6U9NuWajHjcMiwoR38FyP4aOuSD7NILjAJEcwDtjW336XJ14/BCuLjPt3ZVhH0TmT6VCsBx8rY+ZRz2QqbQhx1XPEaJxTmWfmTsfhEebThm7GZBG/muZXGBLlGi2a1dOGHM7lxRApxqBO62KzZM4fuAX9cnZv0BYUCIcIxebWSwizbYvO80DKp0FT0eYPzEQeq34T+DPr3h1n2tfz07tBBBj9JR1yafQQQrVlI6UCmUOsKG8JO2kcWQa4u0EXMFl2AhP1tuaIFSrjyZ6AmEvlelPTblmox43DIsKEfD9nyoTYAPHVPiI+mAf5X8CYS+V6U9NuWajHjcMiwoR8K05YmiZ5rFf8GC1dPWZEAJhL5XpT025ZqMeNwyLChFD11qh0omeDdTTMfR0JMAzAmEvlelPTblmox43DIsKEQJhL5XpT025ZqMeNwyLChHn353qEeKyfHOzpsGkuvq1D5V1JEnfK7XI76UQgEQY7LaVGlQNXJKK1tG8r3UkPIu4FSfH387izYOwuKARumd4oFy9NCFNgTfKhWfCmUrsdG5kv6sPksaQNR9iM9GjWeY+8POnfF0LS4BO5URJpevGZN+0POjJrd3Q9ukWdCY1voMn06uN/YRjm8edVvbujmwCYS+V6U9NuWajHjcMiwoR6XSQpV4PBqSF669f6FU6iAJhL5XpT025ZqMeNwyLChEClqG1VTtwVZEX76UqbplJBFzBZdgIT9bbmiBUq48megJhL5XpT025ZqMeNwyLChHOx7GJe77hpVESBhpKAG9wAmEvlelPTblmox43DIsKEbqzMYzTiG+eydrpSM0jny9VYQEejWeonVcrR0Z3q57WgJYDG9VzIx5uSr5pvC6BJEu8gq1KTgTkSeHGIQsI0EOgXL00IU2BN8qFZ8KZSux0bmS/qw+SxpA1H2Iz0aNZ5uuD2odW1iOSXBgm7+CYMc05J0TNd6amN8ODQKJjhxxmi/hxCtkMoeoCi6Dlw+TSOQJhL5XpT025ZqMeNwyLChErtH+EYRqCF9XSe3aqhoNsAmEvlelPTblmox43DIsKEQJhL5XpT025ZqMeNwyLChGcOtyD7HH/OaHISqwAwlgEAmEvlelPTblmox43DIsKEVGaoJ/HKhQSfxjp3xaNrNICYS+V6U9NuWajHjcMiwoRApahtVU7cFWRF++lKm6ZSfp8q5tn0Lr88pF8QR0w5wOuGzIkykJTIeS5uLXyVMni5qLPgtAmGJTz/hoYStdqTQ1O543sORAA5x97uEX0XEZpWbyc5SDVtgF1ZbiKgaUVaVm8nOUg1bYBdWW4ioGlFWlZvJzlINW2AXVluIqBpRVpWbyc5SDVtgF1ZbiKgaUVaVm8nOUg1bYBdWW4ioGlFWlZvJzlINW2AXVluIqBpRVpWbyc5SDVtgF1ZbiKgaUVMnM0UC5WnWdIY2JUG4A6iXe3h+bBr2q5K4JBuUVGTwyvobdXNcfmuEx+2URtSaH7jpQKZQ6wobwk7aRxZBri7QRcwWXYCE/W25ogVKuPJnoCYS+V6U9NuWajHjcMiwoRdSG9/FfmJBhoMHLlf6CgyQJhL5XpT025ZqMeNwyLChHwrTliaJnmsV/wYLV09ZkQAmEvlelPTblmox43DIsKEey+LdQ4oaSmYUsIyxD3hYMCYS+V6U9NuWajHjcMiwoRAmEvlelPTblmox43DIsKEeffneoR4rJ8c7OmwaS6+rUDCb0zFx6CuVswHjPFclqpuPQWOmsdweHHphCFoTOS+KBcvTQhTYE3yoVnwplK7HRuZL+rD5LGkDUfYjPRo1nmPvDzp3xdC0uATuVESaXrxq6HX7xwBKG6kyD1LSnQX+oCYS+V6U9NuWajHjcMiwoRHxWfKrJm/HsS2Rurx1L9bgJhL5XpT025ZqMeNwyLChECYS+V6U9NuWajHjcMiwoRnDrcg+xx/zmhyEqsAMJYBAJhL5XpT025ZqMeNwyLChEf5TD+QpGPKUsGY3QE01dhAmEvlelPTblmox43DIsKEZ0R2zCwl1ODaPiv9suGUeOOAFwYVp876SIxGCcmbFt1gPiahp9gNwOrWEG1W39Bur1874buciT4fkv4Cy7PgkIP92zWWBtEodEa/TtnUdy9iT28uvPEPbFCM+qPVy+Mk2lZvJzlINW2AXVluIqBpRVpWbyc5SDVtgF1ZbiKgaUVaVm8nOUg1bYBdWW4ioGlFWlZvJzlINW2AXVluIqBpRVpWbyc5SDVtgF1ZbiKgaUVaVm8nOUg1bYBdWW4ioGlFbvu38g3eauGq34Mz6bCovNgZmV1F5HvWL/0134MsmYN+V42sMx8iUq4A3GNQAGPIg88y1yb959ti6bcTGtWbqvRhHIgHsseQko4elD05PJSAmEvlelPTblmox43DIsKEbTqI/tfMxyaaqVRPZi7c/gCYS+V6U9NuWajHjcMiwoRCeKjhga3MYa8G9AQmzTAEvkmG8VgaYaE6yooNJHbctlHooJVneBFf41WxlRDAQXhJQN8Wk/68/qsLGOC0lJrTGjzZXedfe37aEFPv9JhRlk=

1.0

ikt9HYd0d7PNss4L7q/JPjeyN5h1HcmHlq9zQpDYtBlryIMbpWYvaWRdIKItBeZ/tEKHAePGqbd6Sju5f56OM05uet65FKg94kUSadTjIcWqkj9s+v72BBRAjBF8IQCazdF8l8Vt7Bfgs2VPmt9j1ql1vJtHsGKvx+AII0zzn2g= - uS+neMhfCVf6fzRew08RQztbV5gKijTA8S0J/MKPuFD56XyGlOU42tMem9DIdlP6dHYokI8obPjDmqQRhoiqLymCn6I8VzyNCIVKxq+wQBcfvzL47thjouAXIG6cUG/KXdw3MPVG4MdBJiWyOxOHqgJhL5XpT025ZqMeNwyLChFYgbnI4tqzy9+Hy/Me/ZrIAmEvlelPTblmox43DIsKESMFejoiRd0SKuQ/z27qFFXQa1ERjzyoKfhM+YCHmhYP+yjXN8lUHd78tuv4bmWb4w+UrKia41abbzjU44H13PvA/6kVqj1Fy1yeD6+z94dut/AMjx3F1jp8n0Y64cJdETye9r88Dzq8BAn1Z3z/GIFvmIGtjyKZSt45pAv7bNdfYK5dfO+Ap+EnpLiGxQc4CQJhL5XpT025ZqMeNwyLChF8hw+Ba4PeFnltVOIxz/ZDAmEvlelPTblmox43DIsKEQJhL5XpT025ZqMeNwyLChEPVkE70fNjAaYoidJFo/wLAmEvlelPTblmox43DIsKEYCsr1tTFPKoowmr00rX7S4CYS+V6U9NuWajHjcMiwoRnRHbMLCXU4No+K/2y4ZR49nwr7xxwXj7LiQF8DP2fYlVdx4pJoxC4UJoFGLSAjCc8XV6jccGBfWhSyQBOzrmjvA/IKZE1NgwFrJivqDTHrRZs4yS0UFXq9nHTvi2ru67LLDSmBGREpeYZTCi5gCsg/k9u+JA/lSCea5gYaykaEkEnPWoR2MlrDVAcnFkWp50AmEvlelPTblmox43DIsKEYVj9CigqAzOPu26yUdakg4CYS+V6U9NuWajHjcMiwoRAmEvlelPTblmox43DIsKEcEooKnhtf+M7YPfuS/cYYQCYS+V6U9NuWajHjcMiwoRfVgVUw3AUN+Xjd9Qax+ZDwJhL5XpT025ZqMeNwyLChECYS+V6U9NuWajHjcMiwoRGHX6atmoZdMV1LOzP6cM/zQvknCUzSGVcKR8pEiCaSHtPEWqNr0a1AbDa2QkSeFm2XQOkhr/63Al+0G1DHyeAoCWIHWnI3KrA5Wcj9e5CXgEYB1Un/JP+2yNiVOwPz34/3Fkaa7LbpBKbgeMy0qYSAl2/pXmyyRHcRR5NpQ0S/iOcbbqWxi7oXtQ99AGRQI3AmEvlelPTblmox43DIsKEVqb0ti2DktF50H14jqCZtECYS+V6U9NuWajHjcMiwoRWvDmiBoJDdq1esSw0nJKWQJhL5XpT025ZqMeNwyLChHy5SnjWY7E8iQXuPNKEBL+AmEvlelPTblmox43DIsKEQJhL5XpT025ZqMeNwyLChHylnrEo2f6VYXHytIYX5zLwHhM8jIr6GARAUOdAPYzeSeHjpdL0cZws89iztFZhWcBtbQztvi/u9Pm+BC2V68nDU7njew5EADnH3u4RfRcRmkQzeFaPF9ag61F9o9NXzj4LXRfgg5kbiJdTkljY2TmNtnex1M5VyhONUU0Bt8VcKxnGJFURPws1eBjuk/Rji02SEDleq7XdmhIUj4O6bBpdN5fb+m4J2xxprWAU3dNVgJhL5XpT025ZqMeNwyLChEOmZgiisG2FOuFqDOJopvdAmEvlelPTblmox43DIsKEQJhL5XpT025ZqMeNwyLChG2KYTG7Ua1NKYurtiPRBKIAmEvlelPTblmox43DIsKEa2lVtz0tXro+FBOs5Lm2N4CYS+V6U9NuWajHjcMiwoR38FyP4aOuSD7NILjAJEcwDtjW336XJ14/BCuLjPt3ZVhH0TmT6VCsBx8rY+ZRz2QqbQhx1XPEaJxTmWfmTsfhEebThm7GZBG/muZXGBLlGi2a1dOGHM7lxRApxqBO62KzZM4fuAX9cnZv0BYUCIcIxebWSwizbYvO80DKp0FT0eYPzEQeq34T+DPr3h1n2tfz07tBBBj9JR1yafQQQrVlI6UCmUOsKG8JO2kcWQa4u0EXMFl2AhP1tuaIFSrjyZ6AmEvlelPTblmox43DIsKEfD9nyoTYAPHVPiI+mAf5X8CYS+V6U9NuWajHjcMiwoR8K05YmiZ5rFf8GC1dPWZEAJhL5XpT025ZqMeNwyLChFD11qh0omeDdTTMfR0JMAzAmEvlelPTblmox43DIsKEQJhL5XpT025ZqMeNwyLChHn353qEeKyfHOzpsGkuvq1D5V1JEnfK7XI76UQgEQY7LaVGlQNXJKK1tG8r3UkPIu4FSfH387izYOwuKARumd4oFy9NCFNgTfKhWfCmUrsdG5kv6sPksaQNR9iM9GjWeY+8POnfF0LS4BO5URJpevGZN+0POjJrd3Q9ukWdCY1voMn06uN/YRjm8edVvbujmwCYS+V6U9NuWajHjcMiwoR6XSQpV4PBqSF669f6FU6iAJhL5XpT025ZqMeNwyLChEClqG1VTtwVZEX76UqbplJBFzBZdgIT9bbmiBUq48megJhL5XpT025ZqMeNwyLChHOx7GJe77hpVESBhpKAG9wAmEvlelPTblmox43DIsKEbqzMYzTiG+eydrpSM0jny9VYQEejWeonVcrR0Z3q57WgJYDG9VzIx5uSr5pvC6BJEu8gq1KTgTkSeHGIQsI0EOgXL00IU2BN8qFZ8KZSux0bmS/qw+SxpA1H2Iz0aNZ5uuD2odW1iOSXBgm7+CYMc05J0TNd6amN8ODQKJjhxxmi/hxCtkMoeoCi6Dlw+TSOQJhL5XpT025ZqMeNwyLChErtH+EYRqCF9XSe3aqhoNsAmEvlelPTblmox43DIsKEQJhL5XpT025ZqMeNwyLChGcOtyD7HH/OaHISqwAwlgEAmEvlelPTblmox43DIsKEVGaoJ/HKhQSfxjp3xaNrNICYS+V6U9NuWajHjcMiwoRApahtVU7cFWRF++lKm6ZSfp8q5tn0Lr88pF8QR0w5wOuGzIkykJTIeS5uLXyVMni5qLPgtAmGJTz/hoYStdqTQ1O543sORAA5x97uEX0XEZpWbyc5SDVtgF1ZbiKgaUVaVm8nOUg1bYBdWW4ioGlFWlZvJzlINW2AXVluIqBpRVpWbyc5SDVtgF1ZbiKgaUVaVm8nOUg1bYBdWW4ioGlFWlZvJzlINW2AXVluIqBpRVpWbyc5SDVtgF1ZbiKgaUVMnM0UC5WnWdIY2JUG4A6iXe3h+bBr2q5K4JBuUVGTwyvobdXNcfmuEx+2URtSaH7jpQKZQ6wobwk7aRxZBri7QRcwWXYCE/W25ogVKuPJnoCYS+V6U9NuWajHjcMiwoRdSG9/FfmJBhoMHLlf6CgyQJhL5XpT025ZqMeNwyLChHwrTliaJnmsV/wYLV09ZkQAmEvlelPTblmox43DIsKEey+LdQ4oaSmYUsIyxD3hYMCYS+V6U9NuWajHjcMiwoRAmEvlelPTblmox43DIsKEeffneoR4rJ8c7OmwaS6+rUDCb0zFx6CuVswHjPFclqpuPQWOmsdweHHphCFoTOS+KBcvTQhTYE3yoVnwplK7HRuZL+rD5LGkDUfYjPRo1nmPvDzp3xdC0uATuVESaXrxq6HX7xwBKG6kyD1LSnQX+oCYS+V6U9NuWajHjcMiwoRHxWfKrJm/HsS2Rurx1L9bgJhL5XpT025ZqMeNwyLChECYS+V6U9NuWajHjcMiwoRnDrcg+xx/zmhyEqsAMJYBAJhL5XpT025ZqMeNwyLChEf5TD+QpGPKUsGY3QE01dhAmEvlelPTblmox43DIsKEZ0R2zCwl1ODaPiv9suGUeOOAFwYVp876SIxGCcmbFt1gPiahp9gNwOrWEG1W39Bur1874buciT4fkv4Cy7PgkIP92zWWBtEodEa/TtnUdy9iT28uvPEPbFCM+qPVy+Mk2lZvJzlINW2AXVluIqBpRVpWbyc5SDVtgF1ZbiKgaUVaVm8nOUg1bYBdWW4ioGlFWlZvJzlINW2AXVluIqBpRVpWbyc5SDVtgF1ZbiKgaUVaVm8nOUg1bYBdWW4ioGlFbvu38g3eauGq34Mz6bCovNgZmV1F5HvWL/0134MsmYN+V42sMx8iUq4A3GNQAGPIg88y1yb959ti6bcTGtWbqvRhHIgHsseQko4elD05PJSAmEvlelPTblmox43DIsKEbTqI/tfMxyaaqVRPZi7c/gCYS+V6U9NuWajHjcMiwoRCeKjhga3MYa8G9AQmzTAEvkmG8VgaYaE6yooNJHbctlHooJVneBFf41WxlRDAQXhJQN8Wk/68/qsLGOC0lJrTGjzZXedfe37aEFPv9JhRlk=

non_priority

us hy me ychmhyp ap k ja cyyqcys jp qw ocys xx qpvy gcys

IssuesEvent

2016-01-16 11:01:57

OpenRIAServices/OpenRiaServices

https://api.github.com/repos/OpenRIAServices/OpenRiaServices

opened

tooling not working with signed assemblies

CodePlex

**This issue was imported from [CodePlex](http://openriaservices.codeplex.com/workitem/61)** **[groovejumper](http://www.codeplex.com/site/users/view/groovejumper)** wrote 2014-12-28 at 18:08 In migrating an existing solution to OpenRiaServices, I found that the Domain Service Wizard wasn't working with the Signed assemblies (would not show any Entity Data Models in the drop-down). Switching to the unsigned assemblies corrected it, and I was able to switch back to signed assemblies afterwards. I downloaded the most up to date version of the tooling and tools support that I could find at the VS Gallery. Hopefully I won't have to switch back & forth between signed & unsigned? **[ColinBlair](http://www.codeplex.com/site/users/view/ColinBlair)** wrote 2014-12-29 at 16:17 The current tooling should be working, I spent quite a lot of time testing it which is why it took so long to get it released. When you add the new domain service make sure you are adding a new Domain Service (signed) as the unsigned one will try to add the unsigned package to the project. The signed EntityFramework package does need to be added to the project first and a build of the project is usually needed. **[groovejumper](http://www.codeplex.com/site/users/view/groovejumper)** wrote 2014-12-29 at 16:40 I'm sure I had this working with the pre-release, so not sure what the deal is. I'm definitely choosing Domain Service (signed). I'm also positive I'm referencing the signed versions of OpenRiaServices.DomainServices.Server, .Hosting, and .EntityFramework. Made sure a full build happened as well. I'm wondering if somehow my tooling install is messy - but I'm not sure how to check the specific versions of the Tooling & Tools Support I have installed are the correct ones. Should I check somewhere specific for that part? **[ColinBlair](http://www.codeplex.com/site/users/view/ColinBlair)** wrote 2014-12-29 at 19:06 OK, I have had enough of Codeplex not posting comments. I just checked to see if you had replied to my previous comment and that comment seems to be missing. I am going to start the process of moving to GitHub. When you look in the Extensions and Updates screen in Visual Studio, Open RIA Services should be version 1.3.2.1 and the support install has never been updated since the original release. Did you try restarting Visual Studio? Is you solution stored on a local drive or on the network? **[groovejumper](http://www.codeplex.com/site/users/view/groovejumper)** wrote 2014-12-29 at 20:05 Yes, in Extensions & Updates, Open RIA Services displays under Installed, at version 1.3.2.1. Yes, I've restarted VS a number of times. Solution is on a local drive. Not having worked with VSIX's before, I don't know how to verify where it's pulling the assembly from. Is it like an assembly reference where it searches through various locations (which can sometimes result in the wrong one being used)? Or maybe there's something else that's preventing the signed domain service wizard from getting at the entities. It's not the OpenRiaServices assemblies though - I just double-checked again, the path it's pulling from is the Nuget packages path, which is correctly showing the Signed versions. PS: Yes Codeplex does seem finicky sometimes, as does TFS, we're looking at migrating from TFS to Git internally...

1.0

tooling not working with signed assemblies - **This issue was imported from [CodePlex](http://openriaservices.codeplex.com/workitem/61)** **[groovejumper](http://www.codeplex.com/site/users/view/groovejumper)** wrote 2014-12-28 at 18:08 In migrating an existing solution to OpenRiaServices, I found that the Domain Service Wizard wasn't working with the Signed assemblies (would not show any Entity Data Models in the drop-down). Switching to the unsigned assemblies corrected it, and I was able to switch back to signed assemblies afterwards. I downloaded the most up to date version of the tooling and tools support that I could find at the VS Gallery. Hopefully I won't have to switch back & forth between signed & unsigned? **[ColinBlair](http://www.codeplex.com/site/users/view/ColinBlair)** wrote 2014-12-29 at 16:17 The current tooling should be working, I spent quite a lot of time testing it which is why it took so long to get it released. When you add the new domain service make sure you are adding a new Domain Service (signed) as the unsigned one will try to add the unsigned package to the project. The signed EntityFramework package does need to be added to the project first and a build of the project is usually needed. **[groovejumper](http://www.codeplex.com/site/users/view/groovejumper)** wrote 2014-12-29 at 16:40 I'm sure I had this working with the pre-release, so not sure what the deal is. I'm definitely choosing Domain Service (signed). I'm also positive I'm referencing the signed versions of OpenRiaServices.DomainServices.Server, .Hosting, and .EntityFramework. Made sure a full build happened as well. I'm wondering if somehow my tooling install is messy - but I'm not sure how to check the specific versions of the Tooling & Tools Support I have installed are the correct ones. Should I check somewhere specific for that part? **[ColinBlair](http://www.codeplex.com/site/users/view/ColinBlair)** wrote 2014-12-29 at 19:06 OK, I have had enough of Codeplex not posting comments. I just checked to see if you had replied to my previous comment and that comment seems to be missing. I am going to start the process of moving to GitHub. When you look in the Extensions and Updates screen in Visual Studio, Open RIA Services should be version 1.3.2.1 and the support install has never been updated since the original release. Did you try restarting Visual Studio? Is you solution stored on a local drive or on the network? **[groovejumper](http://www.codeplex.com/site/users/view/groovejumper)** wrote 2014-12-29 at 20:05 Yes, in Extensions & Updates, Open RIA Services displays under Installed, at version 1.3.2.1. Yes, I've restarted VS a number of times. Solution is on a local drive. Not having worked with VSIX's before, I don't know how to verify where it's pulling the assembly from. Is it like an assembly reference where it searches through various locations (which can sometimes result in the wrong one being used)? Or maybe there's something else that's preventing the signed domain service wizard from getting at the entities. It's not the OpenRiaServices assemblies though - I just double-checked again, the path it's pulling from is the Nuget packages path, which is correctly showing the Signed versions. PS: Yes Codeplex does seem finicky sometimes, as does TFS, we're looking at migrating from TFS to Git internally...

non_priority

tooling not working with signed assemblies this issue was imported from wrote at in migrating an existing solution to openriaservices i found that the domain service wizard wasn t working with the signed assemblies would not show any entity data models in the drop down switching to the unsigned assemblies corrected it and i was able to switch back to signed assemblies afterwards i downloaded the most up to date version of the tooling and tools support that i could find at the vs gallery hopefully i won t have to switch back forth between signed unsigned wrote at the current tooling should be working i spent quite a lot of time testing it which is why it took so long to get it released when you add the new domain service make sure you are adding a new domain service signed as the unsigned one will try to add the unsigned package to the project the signed entityframework package does need to be added to the project first and a build of the project is usually needed wrote at i m sure i had this working with the pre release so not sure what the deal is i m definitely choosing domain service signed i m also positive i m referencing the signed versions of openriaservices domainservices server hosting and entityframework made sure a full build happened as well i m wondering if somehow my tooling install is messy but i m not sure how to check the specific versions of the tooling tools support i have installed are the correct ones should i check somewhere specific for that part wrote at ok i have had enough of codeplex not posting comments i just checked to see if you had replied to my previous comment and that comment seems to be missing i am going to start the process of moving to github when you look in the extensions and updates screen in visual studio open ria services should be version and the support install has never been updated since the original release did you try restarting visual studio is you solution stored on a local drive or on the network wrote at yes in extensions updates open ria services displays under installed at version yes i ve restarted vs a number of times solution is on a local drive not having worked with vsix s before i don t know how to verify where it s pulling the assembly from is it like an assembly reference where it searches through various locations which can sometimes result in the wrong one being used or maybe there s something else that s preventing the signed domain service wizard from getting at the entities it s not the openriaservices assemblies though i just double checked again the path it s pulling from is the nuget packages path which is correctly showing the signed versions ps yes codeplex does seem finicky sometimes as does tfs we re looking at migrating from tfs to git internally

IssuesEvent

2022-11-29 11:30:54

Requisitos-de-Software/2022.2-MEI

https://api.github.com/repos/Requisitos-de-Software/2022.2-MEI

closed

Planejamento Geral do Projeto

documentation

# Descrição Planejamento do projeto apresentando as atividades a serem realizadas em cada etapa do projeto # Tarefas - [x] Criação do documento de Planejamento # Critérios de aceitação - [ ] Revisão por membros do grupo que não participaram da elaboração do artefato

1.0

Planejamento Geral do Projeto - # Descrição Planejamento do projeto apresentando as atividades a serem realizadas em cada etapa do projeto # Tarefas - [x] Criação do documento de Planejamento # Critérios de aceitação - [ ] Revisão por membros do grupo que não participaram da elaboração do artefato

non_priority

planejamento geral do projeto descrição planejamento do projeto apresentando as atividades a serem realizadas em cada etapa do projeto tarefas criação do documento de planejamento critérios de aceitação revisão por membros do grupo que não participaram da elaboração do artefato

IssuesEvent

2019-03-01 07:37:23

olifolkerd/tabulator

https://api.github.com/repos/olifolkerd/tabulator

closed

$.widget is not a function - jquery_wrapper

Documentation

**Describe the bug** When I included the jquery wrapper as shown here, http://tabulator.info/docs/4.2/jquery, I get an error Uncaught TypeError: $.widget is not a function **Tabulator Info** - 4.2 **To Reproduce** Steps to reproduce the behavior: 1. Create html file with only these in the head <script src="https://code.jquery.com/jquery-3.3.1.slim.min.js" integrity="sha256-3edrmyuQ0w65f8gfBsqowzjJe2iM6n0nKciPUp8y+7E=" crossorigin="anonymous"></script> <link href="dist/css/tabulator_site.min.css" rel="stylesheet" /> <script type="text/javascript" src="dist/js/tabulator.min.js"></script> <script type="text/javascript" src="dist/js/jquery_wrapper.js"></script> 2. Observe the error in console

1.0

$.widget is not a function - jquery_wrapper - **Describe the bug** When I included the jquery wrapper as shown here, http://tabulator.info/docs/4.2/jquery, I get an error Uncaught TypeError: $.widget is not a function **Tabulator Info** - 4.2 **To Reproduce** Steps to reproduce the behavior: 1. Create html file with only these in the head <script src="https://code.jquery.com/jquery-3.3.1.slim.min.js" integrity="sha256-3edrmyuQ0w65f8gfBsqowzjJe2iM6n0nKciPUp8y+7E=" crossorigin="anonymous"></script> <link href="dist/css/tabulator_site.min.css" rel="stylesheet" /> <script type="text/javascript" src="dist/js/tabulator.min.js"></script> <script type="text/javascript" src="dist/js/jquery_wrapper.js"></script> 2. Observe the error in console

non_priority

widget is not a function jquery wrapper describe the bug when i included the jquery wrapper as shown here i get an error uncaught typeerror widget is not a function tabulator info to reproduce steps to reproduce the behavior create html file with only these in the head observe the error in console

IssuesEvent

2021-01-29 18:40:00

RafaelMarangoni/sistema_bancario

https://api.github.com/repos/RafaelMarangoni/sistema_bancario

closed

Criar o LoginService

Security enhancement

Criar o LoginServie com a regra de autenticação do usuário usando DTO do usuario (LoginDTO) pra converter em um usuário e comparar a senha recebida com a criptografia da senha

True

Criar o LoginService - Criar o LoginServie com a regra de autenticação do usuário usando DTO do usuario (LoginDTO) pra converter em um usuário e comparar a senha recebida com a criptografia da senha

non_priority

criar o loginservice criar o loginservie com a regra de autenticação do usuário usando dto do usuario logindto pra converter em um usuário e comparar a senha recebida com a criptografia da senha

IssuesEvent

2020-04-13 19:26:19

ElektraInitiative/libelektra

https://api.github.com/repos/ElektraInitiative/libelektra

closed

crypto_botan: botan 2.13 header deprecation warnings

build dependencies

As of botan 2.13.x (maybe earlier?) we started getting the following header deprecation warnings: ``` In file included from ../src/plugins/crypto/botan_operations.cpp:12: /usr/local/Cellar/botan/2.13.0/include/botan-2/botan/hmac.h:14:1: warning: this header will be made internal in the future [-W#pragma-messages] BOTAN_FUTURE_INTERNAL_HEADER(hmac.h) ^ /usr/local/Cellar/botan/2.13.0/include/botan-2/botan/compiler.h:107:49: note: expanded from macro 'BOTAN_FUTURE_INTERNAL_HEADER' #define BOTAN_FUTURE_INTERNAL_HEADER(hdr) _Pragma("message \"this header will be made internal in the future\"") ^ <scratch space>:100:2: note: expanded from here message "this header will be made internal in the future" ^ In file included from ../src/plugins/crypto/botan_operations.cpp:13: /usr/local/Cellar/botan/2.13.0/include/botan-2/botan/init.h:16:1: warning: this header is deprecated [-W#pragma-messages] BOTAN_DEPRECATED_HEADER(init.h) ^ /usr/local/Cellar/botan/2.13.0/include/botan-2/botan/compiler.h:104:42: note: expanded from macro 'BOTAN_DEPRECATED_HEADER' #define BOTAN_DEPRECATED_HEADER(hdr) _Pragma("message \"this header is deprecated\"") ^ <scratch space>:102:2: note: expanded from here message "this header is deprecated" ^ In file included from ../src/plugins/crypto/botan_operations.cpp:14: /usr/local/Cellar/botan/2.13.0/include/botan-2/botan/lookup.h:35:1: warning: this header is deprecated [-W#pragma-messages] BOTAN_DEPRECATED_HEADER(lookup.h) ^ /usr/local/Cellar/botan/2.13.0/include/botan-2/botan/compiler.h:104:42: note: expanded from macro 'BOTAN_DEPRECATED_HEADER' #define BOTAN_DEPRECATED_HEADER(hdr) _Pragma("message \"this header is deprecated\"") ^ <scratch space>:104:2: note: expanded from here message "this header is deprecated" ^ In file included from ../src/plugins/crypto/botan_operations.cpp:15: /usr/local/Cellar/botan/2.13.0/include/botan-2/botan/pbkdf2.h:16:1: warning: this header will be made internal in the future [-W#pragma-messages] BOTAN_FUTURE_INTERNAL_HEADER(pbkdf2.h) ^ /usr/local/Cellar/botan/2.13.0/include/botan-2/botan/compiler.h:107:49: note: expanded from macro 'BOTAN_FUTURE_INTERNAL_HEADER' #define BOTAN_FUTURE_INTERNAL_HEADER(hdr) _Pragma("message \"this header will be made internal in the future\"") ^ <scratch space>:106:2: note: expanded from here message "this header will be made internal in the future" ^ In file included from ../src/plugins/crypto/botan_operations.cpp:17: In file included from /usr/local/Cellar/botan/2.13.0/include/botan-2/botan/sha2_32.h:12: /usr/local/Cellar/botan/2.13.0/include/botan-2/botan/mdx_hash.h:13:1: warning: this header will be made internal in the future [-W#pragma-messages] BOTAN_FUTURE_INTERNAL_HEADER(mdx_hash.h) ^ /usr/local/Cellar/botan/2.13.0/include/botan-2/botan/compiler.h:107:49: note: expanded from macro 'BOTAN_FUTURE_INTERNAL_HEADER' #define BOTAN_FUTURE_INTERNAL_HEADER(hdr) _Pragma("message \"this header will be made internal in the future\"") ^ <scratch space>:108:2: note: expanded from here message "this header will be made internal in the future" ^ In file included from ../src/plugins/crypto/botan_operations.cpp:17: /usr/local/Cellar/botan/2.13.0/include/botan-2/botan/sha2_32.h:14:1: warning: this header will be made internal in the future [-W#pragma-messages] BOTAN_FUTURE_INTERNAL_HEADER(sha2_32.h) ^ /usr/local/Cellar/botan/2.13.0/include/botan-2/botan/compiler.h:107:49: note: expanded from macro 'BOTAN_FUTURE_INTERNAL_HEADER' #define BOTAN_FUTURE_INTERNAL_HEADER(hdr) _Pragma("message \"this header will be made internal in the future\"") ^ <scratch space>:110:2: note: expanded from here message "this header will be made internal in the future" ^ 6 warnings generated. ``` Botan maintains a docu of [deprecated headers](https://github.com/randombit/botan/blob/master/doc/deprecated.rst).

1.0

crypto_botan: botan 2.13 header deprecation warnings - As of botan 2.13.x (maybe earlier?) we started getting the following header deprecation warnings: ``` In file included from ../src/plugins/crypto/botan_operations.cpp:12: /usr/local/Cellar/botan/2.13.0/include/botan-2/botan/hmac.h:14:1: warning: this header will be made internal in the future [-W#pragma-messages] BOTAN_FUTURE_INTERNAL_HEADER(hmac.h) ^ /usr/local/Cellar/botan/2.13.0/include/botan-2/botan/compiler.h:107:49: note: expanded from macro 'BOTAN_FUTURE_INTERNAL_HEADER' #define BOTAN_FUTURE_INTERNAL_HEADER(hdr) _Pragma("message \"this header will be made internal in the future\"") ^ <scratch space>:100:2: note: expanded from here message "this header will be made internal in the future" ^ In file included from ../src/plugins/crypto/botan_operations.cpp:13: /usr/local/Cellar/botan/2.13.0/include/botan-2/botan/init.h:16:1: warning: this header is deprecated [-W#pragma-messages] BOTAN_DEPRECATED_HEADER(init.h) ^ /usr/local/Cellar/botan/2.13.0/include/botan-2/botan/compiler.h:104:42: note: expanded from macro 'BOTAN_DEPRECATED_HEADER' #define BOTAN_DEPRECATED_HEADER(hdr) _Pragma("message \"this header is deprecated\"") ^ <scratch space>:102:2: note: expanded from here message "this header is deprecated" ^ In file included from ../src/plugins/crypto/botan_operations.cpp:14: /usr/local/Cellar/botan/2.13.0/include/botan-2/botan/lookup.h:35:1: warning: this header is deprecated [-W#pragma-messages] BOTAN_DEPRECATED_HEADER(lookup.h) ^ /usr/local/Cellar/botan/2.13.0/include/botan-2/botan/compiler.h:104:42: note: expanded from macro 'BOTAN_DEPRECATED_HEADER' #define BOTAN_DEPRECATED_HEADER(hdr) _Pragma("message \"this header is deprecated\"") ^ <scratch space>:104:2: note: expanded from here message "this header is deprecated" ^ In file included from ../src/plugins/crypto/botan_operations.cpp:15: /usr/local/Cellar/botan/2.13.0/include/botan-2/botan/pbkdf2.h:16:1: warning: this header will be made internal in the future [-W#pragma-messages] BOTAN_FUTURE_INTERNAL_HEADER(pbkdf2.h) ^ /usr/local/Cellar/botan/2.13.0/include/botan-2/botan/compiler.h:107:49: note: expanded from macro 'BOTAN_FUTURE_INTERNAL_HEADER' #define BOTAN_FUTURE_INTERNAL_HEADER(hdr) _Pragma("message \"this header will be made internal in the future\"") ^ <scratch space>:106:2: note: expanded from here message "this header will be made internal in the future" ^ In file included from ../src/plugins/crypto/botan_operations.cpp:17: In file included from /usr/local/Cellar/botan/2.13.0/include/botan-2/botan/sha2_32.h:12: /usr/local/Cellar/botan/2.13.0/include/botan-2/botan/mdx_hash.h:13:1: warning: this header will be made internal in the future [-W#pragma-messages] BOTAN_FUTURE_INTERNAL_HEADER(mdx_hash.h) ^ /usr/local/Cellar/botan/2.13.0/include/botan-2/botan/compiler.h:107:49: note: expanded from macro 'BOTAN_FUTURE_INTERNAL_HEADER' #define BOTAN_FUTURE_INTERNAL_HEADER(hdr) _Pragma("message \"this header will be made internal in the future\"") ^ <scratch space>:108:2: note: expanded from here message "this header will be made internal in the future" ^ In file included from ../src/plugins/crypto/botan_operations.cpp:17: /usr/local/Cellar/botan/2.13.0/include/botan-2/botan/sha2_32.h:14:1: warning: this header will be made internal in the future [-W#pragma-messages] BOTAN_FUTURE_INTERNAL_HEADER(sha2_32.h) ^ /usr/local/Cellar/botan/2.13.0/include/botan-2/botan/compiler.h:107:49: note: expanded from macro 'BOTAN_FUTURE_INTERNAL_HEADER' #define BOTAN_FUTURE_INTERNAL_HEADER(hdr) _Pragma("message \"this header will be made internal in the future\"") ^ <scratch space>:110:2: note: expanded from here message "this header will be made internal in the future" ^ 6 warnings generated. ``` Botan maintains a docu of [deprecated headers](https://github.com/randombit/botan/blob/master/doc/deprecated.rst).

non_priority

crypto botan botan header deprecation warnings as of botan x maybe earlier we started getting the following header deprecation warnings in file included from src plugins crypto botan operations cpp usr local cellar botan include botan botan hmac h warning this header will be made internal in the future botan future internal header hmac h usr local cellar botan include botan botan compiler h note expanded from macro botan future internal header define botan future internal header hdr pragma message this header will be made internal in the future note expanded from here message this header will be made internal in the future in file included from src plugins crypto botan operations cpp usr local cellar botan include botan botan init h warning this header is deprecated botan deprecated header init h usr local cellar botan include botan botan compiler h note expanded from macro botan deprecated header define botan deprecated header hdr pragma message this header is deprecated note expanded from here message this header is deprecated in file included from src plugins crypto botan operations cpp usr local cellar botan include botan botan lookup h warning this header is deprecated botan deprecated header lookup h usr local cellar botan include botan botan compiler h note expanded from macro botan deprecated header define botan deprecated header hdr pragma message this header is deprecated note expanded from here message this header is deprecated in file included from src plugins crypto botan operations cpp usr local cellar botan include botan botan h warning this header will be made internal in the future botan future internal header h usr local cellar botan include botan botan compiler h note expanded from macro botan future internal header define botan future internal header hdr pragma message this header will be made internal in the future note expanded from here message this header will be made internal in the future in file included from src plugins crypto botan operations cpp in file included from usr local cellar botan include botan botan h usr local cellar botan include botan botan mdx hash h warning this header will be made internal in the future botan future internal header mdx hash h usr local cellar botan include botan botan compiler h note expanded from macro botan future internal header define botan future internal header hdr pragma message this header will be made internal in the future note expanded from here message this header will be made internal in the future in file included from src plugins crypto botan operations cpp usr local cellar botan include botan botan h warning this header will be made internal in the future botan future internal header h usr local cellar botan include botan botan compiler h note expanded from macro botan future internal header define botan future internal header hdr pragma message this header will be made internal in the future note expanded from here message this header will be made internal in the future warnings generated botan maintains a docu of

IssuesEvent

2022-02-15 17:21:49

ArctosDB/arctos

https://api.github.com/repos/ArctosDB/arctos

closed

WIDE media column in search results

Display/Interface Infrastructure-limited

All of a sudden this afternoon my search results column with Media is resizing to be very wide:  Did I do something to make this happen? Can you help me figure out how to resize? Grabbing the column header and dragging does not seem to do it. Prior to today I'd get a scroll bar and the images would stack vertically, which I greatly prefer!

1.0

WIDE media column in search results - All of a sudden this afternoon my search results column with Media is resizing to be very wide:  Did I do something to make this happen? Can you help me figure out how to resize? Grabbing the column header and dragging does not seem to do it. Prior to today I'd get a scroll bar and the images would stack vertically, which I greatly prefer!

non_priority

wide media column in search results all of a sudden this afternoon my search results column with media is resizing to be very wide did i do something to make this happen can you help me figure out how to resize grabbing the column header and dragging does not seem to do it prior to today i d get a scroll bar and the images would stack vertically which i greatly prefer

IssuesEvent

2020-06-04 16:44:14

tensorflow/tensorflow

https://api.github.com/repos/tensorflow/tensorflow

opened

Unable to call "image_dataset_from_directory"

type:build/install

<em>Please make sure that this is a build/installation issue. As per our [GitHub Policy](https://github.com/tensorflow/tensorflow/blob/master/ISSUES.md), we only address code/doc bugs, performance issues, feature requests and build/installation issues on GitHub. tag:build_template</em> **System information** - OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Windows 10 - TensorFlow installed from (source or binary): conda install tensorflow - TensorFlow version:- version 2.1.0 - Python version: 3.7 - Installed using virtualenv? pip? conda?:conda - Bazel version (if compiling from source): - GCC/Compiler version (if compiling from source): - CUDA/cuDNN version: - GPU model and memory: **Describe the problem** Am following the commands on the tensir.io site ( https://keras.io/api/preprocessing/image/#image_dataset_from_directory-function ) and when i try to do the imports of the required functions at the start of my program i get an error. I have reviewed the directories and the image_dataset_from_directory is not in the folder so it didn't download as part of the package. how can i get it or has it been discontinued? Initial commands: import tensorflow as tf from tensorflow import keras from tensorflow.keras import preprocessing from tensorflow.keras.preprocessing.image import image_dataset_from_directory Error: from tensorflow.keras.preprocessing.image import image_dataset_from_directory Traceback (most recent call last): File "<ipython-input-11-7fae7ea40691>", line 1, in <module> from tensorflow.keras.preprocessing.image import image_dataset_from_directory ImportError: cannot import name 'image_dataset_from_directory' from 'tensorflow.keras.preprocessing.image' (d:\anaconda3\envs\masters\lib\site-packages\tensorflow_core\python\keras\api\_v2\keras\preprocessing\image\__init__.py)

1.0

Unable to call "image_dataset_from_directory" - <em>Please make sure that this is a build/installation issue. As per our [GitHub Policy](https://github.com/tensorflow/tensorflow/blob/master/ISSUES.md), we only address code/doc bugs, performance issues, feature requests and build/installation issues on GitHub. tag:build_template</em> **System information** - OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Windows 10 - TensorFlow installed from (source or binary): conda install tensorflow - TensorFlow version:- version 2.1.0 - Python version: 3.7 - Installed using virtualenv? pip? conda?:conda - Bazel version (if compiling from source): - GCC/Compiler version (if compiling from source): - CUDA/cuDNN version: - GPU model and memory: **Describe the problem** Am following the commands on the tensir.io site ( https://keras.io/api/preprocessing/image/#image_dataset_from_directory-function ) and when i try to do the imports of the required functions at the start of my program i get an error. I have reviewed the directories and the image_dataset_from_directory is not in the folder so it didn't download as part of the package. how can i get it or has it been discontinued? Initial commands: import tensorflow as tf from tensorflow import keras from tensorflow.keras import preprocessing from tensorflow.keras.preprocessing.image import image_dataset_from_directory Error: from tensorflow.keras.preprocessing.image import image_dataset_from_directory Traceback (most recent call last): File "<ipython-input-11-7fae7ea40691>", line 1, in <module> from tensorflow.keras.preprocessing.image import image_dataset_from_directory ImportError: cannot import name 'image_dataset_from_directory' from 'tensorflow.keras.preprocessing.image' (d:\anaconda3\envs\masters\lib\site-packages\tensorflow_core\python\keras\api\_v2\keras\preprocessing\image\__init__.py)

non_priority

unable to call image dataset from directory please make sure that this is a build installation issue as per our we only address code doc bugs performance issues feature requests and build installation issues on github tag build template system information os platform and distribution e g linux ubuntu windows tensorflow installed from source or binary conda install tensorflow tensorflow version version python version installed using virtualenv pip conda conda bazel version if compiling from source gcc compiler version if compiling from source cuda cudnn version gpu model and memory describe the problem am following the commands on the tensir io site and when i try to do the imports of the required functions at the start of my program i get an error i have reviewed the directories and the image dataset from directory is not in the folder so it didn t download as part of the package how can i get it or has it been discontinued initial commands import tensorflow as tf from tensorflow import keras from tensorflow keras import preprocessing from tensorflow keras preprocessing image import image dataset from directory error from tensorflow keras preprocessing image import image dataset from directory traceback most recent call last file line in from tensorflow keras preprocessing image import image dataset from directory importerror cannot import name image dataset from directory from tensorflow keras preprocessing image d envs masters lib site packages tensorflow core python keras api keras preprocessing image init py

IssuesEvent

2018-12-12 20:56:56

amclin/amc-drupal-theme

https://api.github.com/repos/amclin/amc-drupal-theme

closed

Remove social share buttons

performance

Add This statistics show that visitors are not significantly using social sharing buttons provided by Add This. Remove to improve performance.

True

Remove social share buttons - Add This statistics show that visitors are not significantly using social sharing buttons provided by Add This. Remove to improve performance.

non_priority

remove social share buttons add this statistics show that visitors are not significantly using social sharing buttons provided by add this remove to improve performance

IssuesEvent

2020-11-16 06:36:24

TECommons/coordination

https://api.github.com/repos/TECommons/coordination

opened

Establish requirements for becoming a TEC Hatcher

Communications High documentation onboarding

## 📋 Anything to add? Develop framework and template for TEC Hatch readiness, intention, and onboarding procedure by building off current documentation and refining as necessary. ## ⏰ Urgency/Due Date/Blockers? **URGENCY**: High **DUE DATE**: Dec 3 or ASAP **BLOCKERS**: Finalized reqs : Legal? ## ❓ Why is it important? Establishing consistent and meaningful TEC Hatcher onboarding requirements ## 🎉 Subtasks - [ ] Sync with other WG stewards to incorporate inputs - [ ] Develop standardized TEC Builder requirements template ## 🤼‍ Reviewer @ ## 🔗 Work doc - inspirational links [TEC Onboarding and Resources Guide](https://docs.google.com/document/d/1UDnf26QQqqc77mnhn80MLCVzJU6IdvouT-OXPrIVXCg/edit?usp=sharing)

1.0

Establish requirements for becoming a TEC Hatcher - ## 📋 Anything to add? Develop framework and template for TEC Hatch readiness, intention, and onboarding procedure by building off current documentation and refining as necessary. ## ⏰ Urgency/Due Date/Blockers? **URGENCY**: High **DUE DATE**: Dec 3 or ASAP **BLOCKERS**: Finalized reqs : Legal? ## ❓ Why is it important? Establishing consistent and meaningful TEC Hatcher onboarding requirements ## 🎉 Subtasks - [ ] Sync with other WG stewards to incorporate inputs - [ ] Develop standardized TEC Builder requirements template ## 🤼‍ Reviewer @ ## 🔗 Work doc - inspirational links [TEC Onboarding and Resources Guide](https://docs.google.com/document/d/1UDnf26QQqqc77mnhn80MLCVzJU6IdvouT-OXPrIVXCg/edit?usp=sharing)

non_priority

establish requirements for becoming a tec hatcher 📋 anything to add develop framework and template for tec hatch readiness intention and onboarding procedure by building off current documentation and refining as necessary ⏰ urgency due date blockers urgency high due date dec or asap blockers finalized reqs legal ❓ why is it important establishing consistent and meaningful tec hatcher onboarding requirements 🎉 subtasks sync with other wg stewards to incorporate inputs develop standardized tec builder requirements template 🤼‍ reviewer 🔗 work doc inspirational links

IssuesEvent

2021-10-15 18:55:14

KrishnaTO/agro

https://api.github.com/repos/KrishnaTO/agro

opened

Choosing method to adding terms

documentation

Several method for adding terms exist: - Protege - ROBOT - DOSDP-tools - ODK (?)

1.0

Choosing method to adding terms - Several method for adding terms exist: - Protege - ROBOT - DOSDP-tools - ODK (?)

non_priority

choosing method to adding terms several method for adding terms exist protege robot dosdp tools odk

IssuesEvent

2023-01-25 10:27:14

tensorchord/envd

https://api.github.com/repos/tensorchord/envd

closed

feat: --shm-size 8G to the docker run

type/documentation 📄 type/enhancement 💭 type/feature 💡 area/docker 🐳

## Description Torch dataloader gives errors. Need to be able to add more memory. Love this enhancement proposal? Give it a 👍. We prioritise the proposals with the most 👍.

1.0

feat: --shm-size 8G to the docker run - ## Description Torch dataloader gives errors. Need to be able to add more memory. Love this enhancement proposal? Give it a 👍. We prioritise the proposals with the most 👍.

non_priority

feat shm size to the docker run description torch dataloader gives errors need to be able to add more memory love this enhancement proposal give it a 👍 we prioritise the proposals with the most 👍

IssuesEvent

2017-08-10 00:34:50

chartjs/Chart.js

https://api.github.com/repos/chartjs/Chart.js

closed

Doesn't show the graph, only shows the labels

Category: Support Needs test case

Hi, Thank you for such a great tool, it came very handy for my web projects. Although I am facing issue when I am developing in cordova + framework7. What happens is, I can see all the title labels of the graph, but the graph doesn't show up. Any idea what the bug might be about?

1.0

Doesn't show the graph, only shows the labels - Hi, Thank you for such a great tool, it came very handy for my web projects. Although I am facing issue when I am developing in cordova + framework7. What happens is, I can see all the title labels of the graph, but the graph doesn't show up. Any idea what the bug might be about?

non_priority

doesn t show the graph only shows the labels hi thank you for such a great tool it came very handy for my web projects although i am facing issue when i am developing in cordova what happens is i can see all the title labels of the graph but the graph doesn t show up any idea what the bug might be about

IssuesEvent

2023-06-29 08:07:59

Nalini1998/Project_Public

https://api.github.com/repos/Nalini1998/Project_Public

closed

6. Now, let’s hide the contact info

documentation enhancement help wanted good first issue question

After our `login` variable, declare another variable named `contactInfo`. Set it equal to empty parentheses: ``` const contactInfo = ( ); ``` Make sure it is still inside the function component and before the return statement. Next, move the `<ul></ul>` element in the return statement in between the parentheses we just created for `contactInfo`!

1.0

6. Now, let’s hide the contact info - After our `login` variable, declare another variable named `contactInfo`. Set it equal to empty parentheses: ``` const contactInfo = ( ); ``` Make sure it is still inside the function component and before the return statement. Next, move the `<ul></ul>` element in the return statement in between the parentheses we just created for `contactInfo`!

non_priority

now let’s hide the contact info after our login variable declare another variable named contactinfo set it equal to empty parentheses const contactinfo make sure it is still inside the function component and before the return statement next move the element in the return statement in between the parentheses we just created for contactinfo

IssuesEvent

2023-02-03 21:11:22

Azure/azure-sdk-for-java

https://api.github.com/repos/Azure/azure-sdk-for-java

closed

Investigate Registering Strongly-Typed Header Constructors to azure-core

Client Azure.Core pillar-reliability

Investigate adding a concept of registering constructors for strongly-typed header classes into an `azure-core` maintained constructor cache. The strongly-typed header class would register its constructor to `azure-core` when the class is loaded, in the static initializer. Having the strongly-typed header class register its constructor will remove the need for `azure-core` to use reflection to find the constructor and create the class, therefore removing a location where restrictive reflection access could result in an exception being thrown (for example when a SecurityManager is being used). Only strongly-typed headers that have picked up the changes for using `HttpHeaders` directly instead of using jackson-databind should be registered (this issue outlines that https://github.com/Azure/azure-sdk-for-java/issues/27961). The following is a potential example of how this would look: ```java public final class StronglyTypedHeadersHandler { private static final Map<Class<?>, Function<HttpHeaders, ?>> CACHE = new ConcurrentHashMap<>(); public static void register(Class<?> type, Function<HttpHeaders, ?> constructor) { CACHE.put(type, constructor); } @SuppressWarnings("unchecked") public static <T> T construct(Class<T> type, HttpHeaders headers) { var constructor = CACHE.get(type); if (constructor == null) { throw new IllegalStateException("No constructor found for class '" + type + "'."); } return (T) constructor.apply(headers); } } public final class TestClass { static { StronglyTypedHeadersHandler.register(TestClass.class, TestClass::new); } TestClass(HttpHeaders rawHeaders) { // Do stuff. } } ``` This concept could be extended to other locations where reflection usage could be reduced by registering common constructors or methods.

True

Investigate Registering Strongly-Typed Header Constructors to azure-core - Investigate adding a concept of registering constructors for strongly-typed header classes into an `azure-core` maintained constructor cache. The strongly-typed header class would register its constructor to `azure-core` when the class is loaded, in the static initializer. Having the strongly-typed header class register its constructor will remove the need for `azure-core` to use reflection to find the constructor and create the class, therefore removing a location where restrictive reflection access could result in an exception being thrown (for example when a SecurityManager is being used). Only strongly-typed headers that have picked up the changes for using `HttpHeaders` directly instead of using jackson-databind should be registered (this issue outlines that https://github.com/Azure/azure-sdk-for-java/issues/27961). The following is a potential example of how this would look: ```java public final class StronglyTypedHeadersHandler { private static final Map<Class<?>, Function<HttpHeaders, ?>> CACHE = new ConcurrentHashMap<>(); public static void register(Class<?> type, Function<HttpHeaders, ?> constructor) { CACHE.put(type, constructor); } @SuppressWarnings("unchecked") public static <T> T construct(Class<T> type, HttpHeaders headers) { var constructor = CACHE.get(type); if (constructor == null) { throw new IllegalStateException("No constructor found for class '" + type + "'."); } return (T) constructor.apply(headers); } } public final class TestClass { static { StronglyTypedHeadersHandler.register(TestClass.class, TestClass::new); } TestClass(HttpHeaders rawHeaders) { // Do stuff. } } ``` This concept could be extended to other locations where reflection usage could be reduced by registering common constructors or methods.

non_priority

investigate registering strongly typed header constructors to azure core investigate adding a concept of registering constructors for strongly typed header classes into an azure core maintained constructor cache the strongly typed header class would register its constructor to azure core when the class is loaded in the static initializer having the strongly typed header class register its constructor will remove the need for azure core to use reflection to find the constructor and create the class therefore removing a location where restrictive reflection access could result in an exception being thrown for example when a securitymanager is being used only strongly typed headers that have picked up the changes for using httpheaders directly instead of using jackson databind should be registered this issue outlines that the following is a potential example of how this would look java public final class stronglytypedheadershandler private static final map function cache new concurrenthashmap public static void register class type function constructor cache put type constructor suppresswarnings unchecked public static t construct class type httpheaders headers var constructor cache get type if constructor null throw new illegalstateexception no constructor found for class type return t constructor apply headers public final class testclass static stronglytypedheadershandler register testclass class testclass new testclass httpheaders rawheaders do stuff this concept could be extended to other locations where reflection usage could be reduced by registering common constructors or methods

IssuesEvent

2023-01-24 15:20:55

leanprover-community/lean4game

https://api.github.com/repos/leanprover-community/lean4game

opened

Lemma Library

client design

We would need to sections of the Lemma library: 1. Selected lemmas relevant for this level. 2. Overview of all lemmas ever learned.

1.0

Lemma Library - We would need to sections of the Lemma library: 1. Selected lemmas relevant for this level. 2. Overview of all lemmas ever learned.

non_priority

lemma library we would need to sections of the lemma library selected lemmas relevant for this level overview of all lemmas ever learned

IssuesEvent

2023-03-02 18:29:07

axioned/codex

https://api.github.com/repos/axioned/codex

closed

Explore Astro

documentation

- [ ] Get a general understanding of what [Astro](https://astro.build/) is (their [Docs](https://docs.astro.build/) is a great place to start - [ ] Use Tailwind CSS where necessary - [ ] Complete their [tutorial](https://docs.astro.build/en/tutorial/0-introduction/) in your own repo - [ ] Deploy that tutorial to something like Vercel or Netlify - [ ] Review [Astro Islands](https://docs.astro.build/en/concepts/islands/)

1.0

Explore Astro - - [ ] Get a general understanding of what [Astro](https://astro.build/) is (their [Docs](https://docs.astro.build/) is a great place to start - [ ] Use Tailwind CSS where necessary - [ ] Complete their [tutorial](https://docs.astro.build/en/tutorial/0-introduction/) in your own repo - [ ] Deploy that tutorial to something like Vercel or Netlify - [ ] Review [Astro Islands](https://docs.astro.build/en/concepts/islands/)

non_priority

explore astro get a general understanding of what is their is a great place to start use tailwind css where necessary complete their in your own repo deploy that tutorial to something like vercel or netlify review

IssuesEvent

2021-07-03 17:29:30

bdashore3/MangaUpdates

https://api.github.com/repos/bdashore3/MangaUpdates

opened

Document the setup wizard/server

documentation

Now that this is easily accessible to consumers, document usage of these binaries.

1.0

Document the setup wizard/server - Now that this is easily accessible to consumers, document usage of these binaries.

non_priority

document the setup wizard server now that this is easily accessible to consumers document usage of these binaries

IssuesEvent

2022-08-23 13:45:04

joomla/joomla-cms

https://api.github.com/repos/joomla/joomla-cms

closed

Saving a new menu item - alias already exists - chosen article still remains?

No Code Attached Yet J3 Issue

### Steps to reproduce the issue Is it possible to prospectively change the following: accordingly to the actual state the chosen article is automatically removed in case of saving a new menu item after having chosen an article while the system notices that the alias already exists. Is it possible to solve it the way that only the alias has to be changed while the chosen article still remains? ### Expected result ### Actual result ### System information (as much as possible) ### Additional comments

1.0

Saving a new menu item - alias already exists - chosen article still remains? - ### Steps to reproduce the issue Is it possible to prospectively change the following: accordingly to the actual state the chosen article is automatically removed in case of saving a new menu item after having chosen an article while the system notices that the alias already exists. Is it possible to solve it the way that only the alias has to be changed while the chosen article still remains? ### Expected result ### Actual result ### System information (as much as possible) ### Additional comments

non_priority

saving a new menu item alias already exists chosen article still remains steps to reproduce the issue is it possible to prospectively change the following accordingly to the actual state the chosen article is automatically removed in case of saving a new menu item after having chosen an article while the system notices that the alias already exists is it possible to solve it the way that only the alias has to be changed while the chosen article still remains expected result actual result system information as much as possible additional comments

IssuesEvent

2022-10-15 13:08:49

primefaces/primefaces

https://api.github.com/repos/primefaces/primefaces

closed

DataTable: sticky header does not stick when table inside a TabView

:lady_beetle: defect Stale

**Describe the defect** If you insert a dataTable with sticky header inside e tabView, the header is not sticky. Same table outside tabView works as expected. **Reproducer** Just clone https://github.com/dmainardi/primefaces-test repository and follow instructions. **Environment:** - PF Version: 8.0. **It works (sort of) in 6.1, 6.2 and 7.0** - JSF + version: Mojarra 2.2.20, (Mojarra) Jakarta Faces 2.3.14, MyFaces 2.2.12, MyFaces 2.3.6 - Affected browsers: ALL **To Reproduce** 1. clone https://github.com/dmainardi/primefaces-test.git 2. run it with `mvn jetty:run` 3. scroll web page and see the error (last table without sticky header) **Expected behavior** Sticky header in all the tables. **Example XHTML** https://github.com/dmainardi/primefaces-test/blob/master/src/main/webapp/test.xhtml and https://github.com/dmainardi/primefaces-test/blob/master/src/main/webapp/stickyHeaderTable.xhtml **Example Bean** https://github.com/dmainardi/primefaces-test/blob/master/src/main/java/org/primefaces/test/CarView.java

1.0

DataTable: sticky header does not stick when table inside a TabView - **Describe the defect** If you insert a dataTable with sticky header inside e tabView, the header is not sticky. Same table outside tabView works as expected. **Reproducer** Just clone https://github.com/dmainardi/primefaces-test repository and follow instructions. **Environment:** - PF Version: 8.0. **It works (sort of) in 6.1, 6.2 and 7.0** - JSF + version: Mojarra 2.2.20, (Mojarra) Jakarta Faces 2.3.14, MyFaces 2.2.12, MyFaces 2.3.6 - Affected browsers: ALL **To Reproduce** 1. clone https://github.com/dmainardi/primefaces-test.git 2. run it with `mvn jetty:run` 3. scroll web page and see the error (last table without sticky header) **Expected behavior** Sticky header in all the tables. **Example XHTML** https://github.com/dmainardi/primefaces-test/blob/master/src/main/webapp/test.xhtml and https://github.com/dmainardi/primefaces-test/blob/master/src/main/webapp/stickyHeaderTable.xhtml **Example Bean** https://github.com/dmainardi/primefaces-test/blob/master/src/main/java/org/primefaces/test/CarView.java

non_priority

datatable sticky header does not stick when table inside a tabview describe the defect if you insert a datatable with sticky header inside e tabview the header is not sticky same table outside tabview works as expected reproducer just clone repository and follow instructions environment pf version it works sort of in and jsf version mojarra mojarra jakarta faces myfaces myfaces affected browsers all to reproduce clone run it with mvn jetty run scroll web page and see the error last table without sticky header expected behavior sticky header in all the tables example xhtml and example bean

IssuesEvent

2023-07-18 15:50:12

Loweredgames/Skyblock-Classic-Edition

https://api.github.com/repos/Loweredgames/Skyblock-Classic-Edition

closed

Aggiunta conversione per la 1.20 (PID_1)

enhancement confirmed test fix critical non-renewable-resource next version performance

- [x] #153 - [x] #72 - [x] #141 (aggiungere delle casse nelle strutture) - [x] aggiungere baule nel Nether - [x] aggiungere baule per End nella fortezza - [x] aggiungere baule per il nuovo loots nella nuova struttura: aggiungere l'armatura di cavallo, il nuovo sensore, testa di piglin - [x] aggiunto il bloccco flething table sopra alla chiesa nel villagio - [x] #190 - [x] #186 - [x] Testare

1.0

Aggiunta conversione per la 1.20 (PID_1) - - [x] #153 - [x] #72 - [x] #141 (aggiungere delle casse nelle strutture) - [x] aggiungere baule nel Nether - [x] aggiungere baule per End nella fortezza - [x] aggiungere baule per il nuovo loots nella nuova struttura: aggiungere l'armatura di cavallo, il nuovo sensore, testa di piglin - [x] aggiunto il bloccco flething table sopra alla chiesa nel villagio - [x] #190 - [x] #186 - [x] Testare

non_priority

aggiunta conversione per la pid aggiungere delle casse nelle strutture aggiungere baule nel nether aggiungere baule per end nella fortezza aggiungere baule per il nuovo loots nella nuova struttura aggiungere l armatura di cavallo il nuovo sensore testa di piglin aggiunto il bloccco flething table sopra alla chiesa nel villagio testare

IssuesEvent

2015-12-14 13:01:58

subrata1106/TestRel17.2UAT

https://api.github.com/repos/subrata1106/TestRel17.2UAT

closed

Coding Standards: Some of the variables name are not according to variable naming conventions.

Internal Review Defect

Coding Standards: Some of the variables name are not according to variable naming conventions.

1.0

Coding Standards: Some of the variables name are not according to variable naming conventions. - Coding Standards: Some of the variables name are not according to variable naming conventions.

non_priority

coding standards some of the variables name are not according to variable naming conventions coding standards some of the variables name are not according to variable naming conventions

IssuesEvent

2019-05-01 11:26:22

ESMValGroup/ESMValTool

https://api.github.com/repos/ESMValGroup/ESMValTool

closed

Publish NCL diagnostic script documentation on readthedocs

Workshop / Paper documentation

The configuration is outdated, so at the moment the NCL diagnostic script documentation is not built and therefore not available on readthedocs.

1.0

Publish NCL diagnostic script documentation on readthedocs - The configuration is outdated, so at the moment the NCL diagnostic script documentation is not built and therefore not available on readthedocs.

non_priority

publish ncl diagnostic script documentation on readthedocs the configuration is outdated so at the moment the ncl diagnostic script documentation is not built and therefore not available on readthedocs

IssuesEvent

2022-11-26 01:44:58

maddyCode23/linux-4.1.15

https://api.github.com/repos/maddyCode23/linux-4.1.15

reopened

CVE-2017-1000370 (High) detected in linux-stable-rtv4.1.33, linux-stable-rtv4.1.33

security vulnerability

## CVE-2017-1000370 - High Severity Vulnerability <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>linux-stable-rtv4.1.33</b>, <b>linux-stable-rtv4.1.33</b></p></summary> <p> </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary> <p> The offset2lib patch as used in the Linux Kernel contains a vulnerability that allows a PIE binary to be execve()'ed with 1GB of arguments or environmental strings then the stack occupies the address 0x80000000 and the PIE binary is mapped above 0x40000000 nullifying the protection of the offset2lib patch. This affects Linux Kernel version 4.11.5 and earlier. This is a different issue than CVE-2017-1000371. This issue appears to be limited to i386 based systems. <p>Publish Date: 2017-06-19 <p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2017-1000370>CVE-2017-1000370</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.4</b>)</summary> <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Local - Attack Complexity: Low - Privileges Required: None - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: 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-2017-1000370">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-1000370</a></p> <p>Release Date: 2017-06-19</p> <p>Fix Resolution: v4.13-rc1</p> </p> </details> <p></p> *** Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)

True

CVE-2017-1000370 (High) detected in linux-stable-rtv4.1.33, linux-stable-rtv4.1.33 - ## CVE-2017-1000370 - High Severity Vulnerability <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>linux-stable-rtv4.1.33</b>, <b>linux-stable-rtv4.1.33</b></p></summary> <p> </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary> <p> The offset2lib patch as used in the Linux Kernel contains a vulnerability that allows a PIE binary to be execve()'ed with 1GB of arguments or environmental strings then the stack occupies the address 0x80000000 and the PIE binary is mapped above 0x40000000 nullifying the protection of the offset2lib patch. This affects Linux Kernel version 4.11.5 and earlier. This is a different issue than CVE-2017-1000371. This issue appears to be limited to i386 based systems. <p>Publish Date: 2017-06-19 <p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2017-1000370>CVE-2017-1000370</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.4</b>)</summary> <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Local - Attack Complexity: Low - Privileges Required: None - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: 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-2017-1000370">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-1000370</a></p> <p>Release Date: 2017-06-19</p> <p>Fix Resolution: v4.13-rc1</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 linux stable linux stable cve high severity vulnerability vulnerable libraries linux stable linux stable vulnerability details the patch as used in the linux kernel contains a vulnerability that allows a pie binary to be execve ed with of arguments or environmental strings then the stack occupies the address and the pie binary is mapped above nullifying the protection of the patch this affects linux kernel version and earlier this is a different issue than cve this issue appears to be limited to based systems publish date url a href cvss score details base score metrics exploitability metrics attack vector local attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact 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

IssuesEvent

2015-11-17 11:28:20

joomla/joomla-cms

https://api.github.com/repos/joomla/joomla-cms

closed

Post Install Messages sort order

No Code Attached Yet

The Messages are displayed in ascending ID which means that the oldest ones are at the top. I know there are only 3 right now but it makes more sense to me that the newest message is always at the top (ORDER BY postinstall_message_id DESC ) I did try to fix this myself but only managed to ADD it to the ORDER by not change it

1.0

Post Install Messages sort order - The Messages are displayed in ascending ID which means that the oldest ones are at the top. I know there are only 3 right now but it makes more sense to me that the newest message is always at the top (ORDER BY postinstall_message_id DESC ) I did try to fix this myself but only managed to ADD it to the ORDER by not change it

non_priority

post install messages sort order the messages are displayed in ascending id which means that the oldest ones are at the top i know there are only right now but it makes more sense to me that the newest message is always at the top order by postinstall message id desc i did try to fix this myself but only managed to add it to the order by not change it

IssuesEvent

2019-09-05 00:16:55

kevins01/Java3

https://api.github.com/repos/kevins01/Java3

opened

CVE-2019-14439 (High) detected in jackson-databind-2.8.8.jar

security vulnerability

## CVE-2019-14439 - 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.8.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: /Java3/pom.xml</p> <p>Path to vulnerable library: 2/repository/com/fasterxml/jackson/core/jackson-databind/2.8.8/jackson-databind-2.8.8.jar</p> <p> Dependency Hierarchy: - :x: **jackson-databind-2.8.8.jar** (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/kevins01/Java3/commit/9b17ab3055c232217cd39d0dacede2798cd9fafa">9b17ab3055c232217cd39d0dacede2798cd9fafa</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 Polymorphic Typing issue was discovered in FasterXML jackson-databind 2.x before 2.9.9.2. This occurs when Default Typing is enabled (either globally or for a specific property) for an externally exposed JSON endpoint and the service has the logback jar in the classpath. <p>Publish Date: 2019-07-30 <p>URL: <a href=https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-14439>CVE-2019-14439</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: High - Integrity Impact: None - Availability Impact: None </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary> <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-14439">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-14439</a></p> <p>Release Date: 2019-07-30</p> <p>Fix Resolution: 2.9.9.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-2019-14439 (High) detected in jackson-databind-2.8.8.jar - ## CVE-2019-14439 - 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.8.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: /Java3/pom.xml</p> <p>Path to vulnerable library: 2/repository/com/fasterxml/jackson/core/jackson-databind/2.8.8/jackson-databind-2.8.8.jar</p> <p> Dependency Hierarchy: - :x: **jackson-databind-2.8.8.jar** (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/kevins01/Java3/commit/9b17ab3055c232217cd39d0dacede2798cd9fafa">9b17ab3055c232217cd39d0dacede2798cd9fafa</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 Polymorphic Typing issue was discovered in FasterXML jackson-databind 2.x before 2.9.9.2. This occurs when Default Typing is enabled (either globally or for a specific property) for an externally exposed JSON endpoint and the service has the logback jar in the classpath. <p>Publish Date: 2019-07-30 <p>URL: <a href=https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-14439>CVE-2019-14439</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: High - Integrity Impact: None - Availability Impact: None </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary> <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-14439">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-14439</a></p> <p>Release Date: 2019-07-30</p> <p>Fix Resolution: 2.9.9.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 jackson databind jar cve high severity vulnerability vulnerable library jackson databind jar general data binding functionality for jackson works on core streaming api library home page a href path to dependency file pom xml path to vulnerable library repository com fasterxml jackson core jackson databind jackson databind jar dependency hierarchy x jackson databind jar vulnerable library found in head commit a href vulnerability details a polymorphic typing issue was discovered in fasterxml jackson databind x before this occurs when default typing is enabled either globally or for a specific property for an externally exposed json endpoint and the service has the logback jar in the classpath publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact high integrity impact none availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution step up your open source security game with whitesource

IssuesEvent

2023-08-04 02:36:26

madhans23/linux-4.1.15

https://api.github.com/repos/madhans23/linux-4.1.15

reopened

CVE-2019-19768 (High) detected in linux-stable-rtv4.1.33

Mend: dependency security vulnerability

## CVE-2019-19768 - High Severity Vulnerability <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>linux-stable-rtv4.1.33</b></p></summary> <p> <p>Julia Cartwright's fork of linux-stable-rt.git</p> <p>Library home page: <a href=https://git.kernel.org/pub/scm/linux/kernel/git/julia/linux-stable-rt.git>https://git.kernel.org/pub/scm/linux/kernel/git/julia/linux-stable-rt.git</a></p> <p>Found in base branch: <b>master</b></p></p> </details> </p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Source Files (2)</summary> <p></p> <p> <img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/kernel/trace/blktrace.c</b> <img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/kernel/trace/blktrace.c</b> </p> </details> <p></p> </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> Vulnerability Details</summary> <p> In the Linux kernel 5.4.0-rc2, there is a use-after-free (read) in the __blk_add_trace function in kernel/trace/blktrace.c (which is used to fill out a blk_io_trace structure and place it in a per-cpu sub-buffer). <p>Publish Date: 2019-12-12 <p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2019-19768>CVE-2019-19768</a></p> </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary> <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: None - Integrity Impact: None - Availability Impact: High </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary> <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://nvd.nist.gov/vuln/detail/CVE-2019-19768">https://nvd.nist.gov/vuln/detail/CVE-2019-19768</a></p> <p>Release Date: 2020-06-10</p> <p>Fix Resolution: kernel-doc - 3.10.0-514.76.1,3.10.0-957.54.1,4.18.0-147.13.2,3.10.0-1127.8.2,3.10.0-327.88.1,4.18.0-80.18.1,4.18.0-193,3.10.0-1062.26.1,3.10.0-693.67.1;kernel-rt-core - 4.18.0-193.rt13.51;kernel-rt-debug-debuginfo - 4.18.0-193.rt13.51;kernel-abi-whitelists - 3.10.0-327.88.1,3.10.0-1062.26.1,4.18.0-147.13.2,4.18.0-80.18.1,3.10.0-514.76.1,3.10.0-1127.8.2,3.10.0-957.54.1,4.18.0-193,3.10.0-693.67.1;kernel-zfcpdump-modules - 4.18.0-193,4.18.0-147.13.2;kernel-rt-trace-devel - 3.10.0-1127.8.2.rt56.1103;kernel-debug-modules-extra - 4.18.0-147.13.2,4.18.0-193,4.18.0-147.13.2,4.18.0-193,4.18.0-80.18.1,4.18.0-80.18.1,4.18.0-147.13.2,4.18.0-193,4.18.0-193,4.18.0-147.13.2;kernel-rt-debug-kvm - 4.18.0-193.rt13.51,3.10.0-1127.8.2.rt56.1103;kernel-bootwrapper - 3.10.0-1062.26.1,3.10.0-1127.8.2,3.10.0-693.67.1,3.10.0-1062.26.1,3.10.0-957.54.1,3.10.0-1127.8.2,3.10.0-514.76.1,3.10.0-957.54.1;kernel-rt-debuginfo - 4.18.0-193.rt13.51;kernel-rt-debug-modules - 4.18.0-193.rt13.51;kernel-zfcpdump-devel - 4.18.0-193,4.18.0-147.13.2;perf - 3.10.0-514.76.1,3.10.0-957.54.1,3.10.0-1062.26.1,4.18.0-147.13.2,3.10.0-957.54.1,4.18.0-80.18.1,4.18.0-193,4.18.0-193,3.10.0-327.88.1,4.18.0-147.13.2,3.10.0-1062.26.1,3.10.0-1127.8.2,4.18.0-193,4.18.0-80.18.1,4.18.0-193,3.10.0-1127.8.2,4.18.0-147.13.2,3.10.0-1062.26.1,3.10.0-693.67.1,3.10.0-1127.8.2,3.10.0-514.76.1,3.10.0-693.67.1,4.18.0-147.13.2,3.10.0-957.54.1;kernel-zfcpdump-modules-extra - 4.18.0-193,4.18.0-147.13.2;kernel-debuginfo - 3.10.0-514.76.1,4.18.0-80.18.1,3.10.0-1062.26.1,3.10.0-957.54.1,3.10.0-1127.8.2,3.10.0-1127.8.2,3.10.0-693.67.1,4.18.0-193,3.10.0-957.54.1,4.18.0-147.13.2,3.10.0-327.88.1,3.10.0-1062.26.1;kernel-debug-devel - 3.10.0-514.76.1,4.18.0-147.13.2,3.10.0-1062.26.1,3.10.0-957.54.1,3.10.0-957.54.1,4.18.0-193,3.10.0-693.67.1,4.18.0-147.13.2,3.10.0-1127.8.2,4.18.0-147.13.2,3.10.0-327.88.1,4.18.0-193,4.18.0-80.18.1,3.10.0-693.67.1,3.10.0-1127.8.2,3.10.0-1062.26.1,4.18.0-193,3.10.0-957.54.1,3.10.0-1127.8.2,3.10.0-514.76.1,4.18.0-147.13.2,4.18.0-193,3.10.0-1062.26.1,4.18.0-80.18.1;bpftool - 3.10.0-1127.8.2,3.10.0-1062.26.1,4.18.0-147.13.2,4.18.0-193,3.10.0-1062.26.1,4.18.0-147.13.2,3.10.0-1062.26.1,3.10.0-1127.8.2,4.18.0-193,4.18.0-147.13.2,4.18.0-80.18.1,4.18.0-147.13.2,4.18.0-193,3.10.0-957.54.1,4.18.0-80.18.1,4.18.0-193,3.10.0-1127.8.2;kernel-rt-debug-core - 4.18.0-193.rt13.51;kernel-tools-libs - 3.10.0-1062.26.1,3.10.0-1062.26.1,3.10.0-327.88.1,3.10.0-1127.8.2,4.18.0-193,3.10.0-693.67.1,3.10.0-693.67.1,4.18.0-147.13.2,3.10.0-1127.8.2,3.10.0-957.54.1,4.18.0-193,4.18.0-80.18.1,4.18.0-147.13.2,3.10.0-957.54.1,3.10.0-1062.26.1,4.18.0-193,3.10.0-514.76.1,3.10.0-957.54.1,3.10.0-514.76.1,4.18.0-147.13.2,4.18.0-80.18.1,3.10.0-1127.8.2;perf-debuginfo - 3.10.0-957.54.1,3.10.0-957.54.1,3.10.0-1127.8.2,3.10.0-514.76.1,3.10.0-1062.26.1,3.10.0-1062.26.1,4.18.0-193,4.18.0-147.13.2,4.18.0-80.18.1,3.10.0-693.67.1,3.10.0-1127.8.2,3.10.0-327.88.1;kernel-cross-headers - 4.18.0-80.18.1,4.18.0-147.13.2,4.18.0-147.13.2,4.18.0-193,4.18.0-80.18.1,4.18.0-147.13.2,4.18.0-193,4.18.0-193,4.18.0-193,4.18.0-147.13.2;kernel-debug-debuginfo - 3.10.0-1127.8.2,3.10.0-1062.26.1,3.10.0-693.67.1,4.18.0-193,3.10.0-514.76.1,3.10.0-327.88.1,3.10.0-957.54.1,3.10.0-1062.26.1,3.10.0-957.54.1,4.18.0-147.13.2,4.18.0-80.18.1,3.10.0-1127.8.2;kernel-debug - 3.10.0-514.76.1,3.10.0-327.88.1,4.18.0-193,3.10.0-1127.8.2,3.10.0-693.67.1,3.10.0-957.54.1,4.18.0-193,4.18.0-193,3.10.0-1062.26.1,3.10.0-1062.26.1,4.18.0-80.18.1,3.10.0-957.54.1,4.18.0-147.13.2,4.18.0-147.13.2,4.18.0-80.18.1,3.10.0-1127.8.2,3.10.0-693.67.1,4.18.0-147.13.2,3.10.0-1127.8.2,3.10.0-514.76.1,3.10.0-1062.26.1,4.18.0-193,3.10.0-957.54.1,4.18.0-147.13.2;kernel-devel - 4.18.0-193,3.10.0-957.54.1,4.18.0-147.13.2,3.10.0-1127.8.2,3.10.0-514.76.1,3.10.0-1127.8.2,3.10.0-957.54.1,4.18.0-147.13.2,3.10.0-514.76.1,4.18.0-193,4.18.0-80.18.1,3.10.0-1062.26.1,4.18.0-193,3.10.0-957.54.1,4.18.0-80.18.1,3.10.0-1062.26.1,4.18.0-147.13.2,3.10.0-327.88.1,3.10.0-1062.26.1,4.18.0-193,3.10.0-693.67.1,3.10.0-693.67.1,4.18.0-147.13.2,3.10.0-1127.8.2;kernel - 3.10.0-1062.26.1,3.10.0-1062.26.1,3.10.0-693.67.1,3.10.0-327.88.1,3.10.0-327.88.1,4.18.0-147.13.2,4.18.0-147.13.2,3.10.0-957.54.1,4.18.0-80.18.1,4.18.0-147.13.2,4.18.0-80.18.1,3.10.0-514.76.1,3.10.0-1127.8.2,3.10.0-693.67.1,4.18.0-193,4.18.0-193,3.10.0-1127.8.2,4.18.0-147.13.2,3.10.0-1062.26.1,4.18.0-80.18.1,3.10.0-957.54.1,3.10.0-957.54.1,3.10.0-514.76.1,4.18.0-147.13.2,4.18.0-193,3.10.0-1062.26.1,3.10.0-957.54.1,3.10.0-1127.8.2,4.18.0-193,3.10.0-514.76.1,3.10.0-693.67.1,4.18.0-193,3.10.0-1127.8.2;bpftool-debuginfo - 4.18.0-193,4.18.0-147.13.2,3.10.0-1127.8.2,3.10.0-1062.26.1,4.18.0-80.18.1;kpatch-patch-3_10_0-1062_12_1 - 1-2,1-2;kernel-zfcpdump-core - 4.18.0-147.13.2,4.18.0-193;kernel-debug-core - 4.18.0-80.18.1,4.18.0-193,4.18.0-147.13.2,4.18.0-147.13.2,4.18.0-193,4.18.0-147.13.2,4.18.0-193,4.18.0-80.18.1,4.18.0-147.13.2,4.18.0-193;kernel-modules-extra - 4.18.0-147.13.2,4.18.0-193,4.18.0-193,4.18.0-80.18.1,4.18.0-147.13.2,4.18.0-147.13.2,4.18.0-193,4.18.0-80.18.1,4.18.0-193,4.18.0-147.13.2;kernel-rt-debug-devel - 3.10.0-1127.8.2.rt56.1103,4.18.0-193.rt13.51;python-perf - 3.10.0-514.76.1,3.10.0-1127.8.2,3.10.0-693.67.1,3.10.0-1127.8.2,3.10.0-1062.26.1,3.10.0-957.54.1,3.10.0-957.54.1,3.10.0-327.88.1,3.10.0-1062.26.1,3.10.0-693.67.1,3.10.0-514.76.1,3.10.0-1127.8.2,3.10.0-1062.26.1,3.10.0-957.54.1;kernel-core - 4.18.0-147.13.2,4.18.0-193,4.18.0-147.13.2,4.18.0-193,4.18.0-193,4.18.0-147.13.2,4.18.0-80.18.1,4.18.0-193,4.18.0-80.18.1,4.18.0-147.13.2;kernel-rt-debug - 3.10.0-1127.8.2.rt56.1103,4.18.0-193.rt13.51;kernel-rt-devel - 3.10.0-1127.8.2.rt56.1103,4.18.0-193.rt13.51;kernel-debuginfo-common-ppc64 - 3.10.0-957.54.1,3.10.0-1127.8.2,3.10.0-1062.26.1;python3-perf - 4.18.0-193,4.18.0-80.18.1,4.18.0-147.13.2,4.18.0-193,4.18.0-147.13.2,4.18.0-193,4.18.0-80.18.1,4.18.0-193,4.18.0-147.13.2,4.18.0-147.13.2;kernel-tools - 3.10.0-514.76.1,3.10.0-957.54.1,3.10.0-957.54.1,4.18.0-193,4.18.0-147.13.2,4.18.0-80.18.1,3.10.0-1127.8.2,3.10.0-514.76.1,4.18.0-147.13.2,4.18.0-193,4.18.0-80.18.1,3.10.0-1062.26.1,3.10.0-693.67.1,3.10.0-1127.8.2,3.10.0-1062.26.1,3.10.0-327.88.1,3.10.0-1062.26.1,4.18.0-193,3.10.0-957.54.1,3.10.0-693.67.1,4.18.0-147.13.2,3.10.0-1127.8.2;kernel-debug-modules - 4.18.0-147.13.2,4.18.0-147.13.2,4.18.0-193,4.18.0-80.18.1,4.18.0-193,4.18.0-193,4.18.0-147.13.2,4.18.0-193,4.18.0-80.18.1,4.18.0-147.13.2;kernel-rt-trace-kvm - 3.10.0-1127.8.2.rt56.1103;kernel-rt-debuginfo-common-x86_64 - 4.18.0-193.rt13.51;kernel-tools-libs-devel - 3.10.0-514.76.1,3.10.0-327.88.1,3.10.0-693.67.1,3.10.0-1062.26.1,3.10.0-1062.26.1,3.10.0-1127.8.2,3.10.0-957.54.1,3.10.0-693.67.1,3.10.0-1127.8.2,3.10.0-1127.8.2,3.10.0-514.76.1,3.10.0-957.54.1,3.10.0-1062.26.1,3.10.0-957.54.1;kernel-modules - 4.18.0-147.13.2,4.18.0-80.18.1,4.18.0-193,4.18.0-147.13.2,4.18.0-193,4.18.0-80.18.1,4.18.0-193,4.18.0-147.13.2,4.18.0-147.13.2,4.18.0-193;kernel-tools-debuginfo - 3.10.0-1062.26.1,4.18.0-193,3.10.0-1127.8.2,4.18.0-80.18.1,3.10.0-327.88.1,4.18.0-147.13.2,3.10.0-1127.8.2,3.10.0-1062.26.1,3.10.0-957.54.1,3.10.0-957.54.1,3.10.0-514.76.1,3.10.0-693.67.1;kernel-rt-modules - 4.18.0-193.rt13.51;kernel-rt-doc - 3.10.0-1127.8.2.rt56.1103;kernel-rt-kvm - 4.18.0-193.rt13.51,3.10.0-1127.8.2.rt56.1103;python-perf-debuginfo - 3.10.0-693.67.1,3.10.0-1127.8.2,3.10.0-957.54.1,3.10.0-1127.8.2,3.10.0-327.88.1,3.10.0-1062.26.1,3.10.0-957.54.1,3.10.0-514.76.1,3.10.0-1062.26.1;kernel-headers - 3.10.0-1062.26.1,4.18.0-147.13.2,3.10.0-957.54.1,3.10.0-514.76.1,4.18.0-193,4.18.0-80.18.1,4.18.0-147.13.2,3.10.0-327.88.1,3.10.0-1127.8.2,4.18.0-147.13.2,4.18.0-193,3.10.0-1062.26.1,3.10.0-693.67.1,4.18.0-193,3.10.0-1127.8.2,3.10.0-693.67.1,4.18.0-147.13.2,3.10.0-957.54.1,3.10.0-514.76.1,3.10.0-1062.26.1,4.18.0-80.18.1,3.10.0-957.54.1,4.18.0-193,3.10.0-1127.8.2;kernel-rt-trace - 3.10.0-1127.8.2.rt56.1103;kernel-debuginfo-common-x86_64 - 3.10.0-1127.8.2,3.10.0-693.67.1,3.10.0-327.88.1,4.18.0-147.13.2,4.18.0-80.18.1,3.10.0-1062.26.1,3.10.0-514.76.1,4.18.0-193,3.10.0-957.54.1;kernel-rt - 3.10.0-1127.8.2.rt56.1103,4.18.0-193.rt13.51,3.10.0-1127.8.2.rt56.1103,4.18.0-193.rt13.51;kernel-zfcpdump - 4.18.0-147.13.2,4.18.0-193;kernel-rt-debug-modules-extra - 4.18.0-193.rt13.51;python3-perf-debuginfo - 4.18.0-147.13.2,4.18.0-80.18.1,4.18.0-193;kernel-rt-modules-extra - 4.18.0-193.rt13.51</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-2019-19768 (High) detected in linux-stable-rtv4.1.33 - ## CVE-2019-19768 - High Severity Vulnerability <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>linux-stable-rtv4.1.33</b></p></summary> <p> <p>Julia Cartwright's fork of linux-stable-rt.git</p> <p>Library home page: <a href=https://git.kernel.org/pub/scm/linux/kernel/git/julia/linux-stable-rt.git>https://git.kernel.org/pub/scm/linux/kernel/git/julia/linux-stable-rt.git</a></p> <p>Found in base branch: <b>master</b></p></p> </details> </p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Source Files (2)</summary> <p></p> <p> <img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/kernel/trace/blktrace.c</b> <img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/kernel/trace/blktrace.c</b> </p> </details> <p></p> </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> Vulnerability Details</summary> <p> In the Linux kernel 5.4.0-rc2, there is a use-after-free (read) in the __blk_add_trace function in kernel/trace/blktrace.c (which is used to fill out a blk_io_trace structure and place it in a per-cpu sub-buffer). <p>Publish Date: 2019-12-12 <p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2019-19768>CVE-2019-19768</a></p> </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary> <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: None - Integrity Impact: None - Availability Impact: High </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary> <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://nvd.nist.gov/vuln/detail/CVE-2019-19768">https://nvd.nist.gov/vuln/detail/CVE-2019-19768</a></p> <p>Release Date: 2020-06-10</p> <p>Fix Resolution: kernel-doc - 3.10.0-514.76.1,3.10.0-957.54.1,4.18.0-147.13.2,3.10.0-1127.8.2,3.10.0-327.88.1,4.18.0-80.18.1,4.18.0-193,3.10.0-1062.26.1,3.10.0-693.67.1;kernel-rt-core - 4.18.0-193.rt13.51;kernel-rt-debug-debuginfo - 4.18.0-193.rt13.51;kernel-abi-whitelists - 3.10.0-327.88.1,3.10.0-1062.26.1,4.18.0-147.13.2,4.18.0-80.18.1,3.10.0-514.76.1,3.10.0-1127.8.2,3.10.0-957.54.1,4.18.0-193,3.10.0-693.67.1;kernel-zfcpdump-modules - 4.18.0-193,4.18.0-147.13.2;kernel-rt-trace-devel - 3.10.0-1127.8.2.rt56.1103;kernel-debug-modules-extra - 4.18.0-147.13.2,4.18.0-193,4.18.0-147.13.2,4.18.0-193,4.18.0-80.18.1,4.18.0-80.18.1,4.18.0-147.13.2,4.18.0-193,4.18.0-193,4.18.0-147.13.2;kernel-rt-debug-kvm - 4.18.0-193.rt13.51,3.10.0-1127.8.2.rt56.1103;kernel-bootwrapper - 3.10.0-1062.26.1,3.10.0-1127.8.2,3.10.0-693.67.1,3.10.0-1062.26.1,3.10.0-957.54.1,3.10.0-1127.8.2,3.10.0-514.76.1,3.10.0-957.54.1;kernel-rt-debuginfo - 4.18.0-193.rt13.51;kernel-rt-debug-modules - 4.18.0-193.rt13.51;kernel-zfcpdump-devel - 4.18.0-193,4.18.0-147.13.2;perf - 3.10.0-514.76.1,3.10.0-957.54.1,3.10.0-1062.26.1,4.18.0-147.13.2,3.10.0-957.54.1,4.18.0-80.18.1,4.18.0-193,4.18.0-193,3.10.0-327.88.1,4.18.0-147.13.2,3.10.0-1062.26.1,3.10.0-1127.8.2,4.18.0-193,4.18.0-80.18.1,4.18.0-193,3.10.0-1127.8.2,4.18.0-147.13.2,3.10.0-1062.26.1,3.10.0-693.67.1,3.10.0-1127.8.2,3.10.0-514.76.1,3.10.0-693.67.1,4.18.0-147.13.2,3.10.0-957.54.1;kernel-zfcpdump-modules-extra - 4.18.0-193,4.18.0-147.13.2;kernel-debuginfo - 3.10.0-514.76.1,4.18.0-80.18.1,3.10.0-1062.26.1,3.10.0-957.54.1,3.10.0-1127.8.2,3.10.0-1127.8.2,3.10.0-693.67.1,4.18.0-193,3.10.0-957.54.1,4.18.0-147.13.2,3.10.0-327.88.1,3.10.0-1062.26.1;kernel-debug-devel - 3.10.0-514.76.1,4.18.0-147.13.2,3.10.0-1062.26.1,3.10.0-957.54.1,3.10.0-957.54.1,4.18.0-193,3.10.0-693.67.1,4.18.0-147.13.2,3.10.0-1127.8.2,4.18.0-147.13.2,3.10.0-327.88.1,4.18.0-193,4.18.0-80.18.1,3.10.0-693.67.1,3.10.0-1127.8.2,3.10.0-1062.26.1,4.18.0-193,3.10.0-957.54.1,3.10.0-1127.8.2,3.10.0-514.76.1,4.18.0-147.13.2,4.18.0-193,3.10.0-1062.26.1,4.18.0-80.18.1;bpftool - 3.10.0-1127.8.2,3.10.0-1062.26.1,4.18.0-147.13.2,4.18.0-193,3.10.0-1062.26.1,4.18.0-147.13.2,3.10.0-1062.26.1,3.10.0-1127.8.2,4.18.0-193,4.18.0-147.13.2,4.18.0-80.18.1,4.18.0-147.13.2,4.18.0-193,3.10.0-957.54.1,4.18.0-80.18.1,4.18.0-193,3.10.0-1127.8.2;kernel-rt-debug-core - 4.18.0-193.rt13.51;kernel-tools-libs - 3.10.0-1062.26.1,3.10.0-1062.26.1,3.10.0-327.88.1,3.10.0-1127.8.2,4.18.0-193,3.10.0-693.67.1,3.10.0-693.67.1,4.18.0-147.13.2,3.10.0-1127.8.2,3.10.0-957.54.1,4.18.0-193,4.18.0-80.18.1,4.18.0-147.13.2,3.10.0-957.54.1,3.10.0-1062.26.1,4.18.0-193,3.10.0-514.76.1,3.10.0-957.54.1,3.10.0-514.76.1,4.18.0-147.13.2,4.18.0-80.18.1,3.10.0-1127.8.2;perf-debuginfo - 3.10.0-957.54.1,3.10.0-957.54.1,3.10.0-1127.8.2,3.10.0-514.76.1,3.10.0-1062.26.1,3.10.0-1062.26.1,4.18.0-193,4.18.0-147.13.2,4.18.0-80.18.1,3.10.0-693.67.1,3.10.0-1127.8.2,3.10.0-327.88.1;kernel-cross-headers - 4.18.0-80.18.1,4.18.0-147.13.2,4.18.0-147.13.2,4.18.0-193,4.18.0-80.18.1,4.18.0-147.13.2,4.18.0-193,4.18.0-193,4.18.0-193,4.18.0-147.13.2;kernel-debug-debuginfo - 3.10.0-1127.8.2,3.10.0-1062.26.1,3.10.0-693.67.1,4.18.0-193,3.10.0-514.76.1,3.10.0-327.88.1,3.10.0-957.54.1,3.10.0-1062.26.1,3.10.0-957.54.1,4.18.0-147.13.2,4.18.0-80.18.1,3.10.0-1127.8.2;kernel-debug - 3.10.0-514.76.1,3.10.0-327.88.1,4.18.0-193,3.10.0-1127.8.2,3.10.0-693.67.1,3.10.0-957.54.1,4.18.0-193,4.18.0-193,3.10.0-1062.26.1,3.10.0-1062.26.1,4.18.0-80.18.1,3.10.0-957.54.1,4.18.0-147.13.2,4.18.0-147.13.2,4.18.0-80.18.1,3.10.0-1127.8.2,3.10.0-693.67.1,4.18.0-147.13.2,3.10.0-1127.8.2,3.10.0-514.76.1,3.10.0-1062.26.1,4.18.0-193,3.10.0-957.54.1,4.18.0-147.13.2;kernel-devel - 4.18.0-193,3.10.0-957.54.1,4.18.0-147.13.2,3.10.0-1127.8.2,3.10.0-514.76.1,3.10.0-1127.8.2,3.10.0-957.54.1,4.18.0-147.13.2,3.10.0-514.76.1,4.18.0-193,4.18.0-80.18.1,3.10.0-1062.26.1,4.18.0-193,3.10.0-957.54.1,4.18.0-80.18.1,3.10.0-1062.26.1,4.18.0-147.13.2,3.10.0-327.88.1,3.10.0-1062.26.1,4.18.0-193,3.10.0-693.67.1,3.10.0-693.67.1,4.18.0-147.13.2,3.10.0-1127.8.2;kernel - 3.10.0-1062.26.1,3.10.0-1062.26.1,3.10.0-693.67.1,3.10.0-327.88.1,3.10.0-327.88.1,4.18.0-147.13.2,4.18.0-147.13.2,3.10.0-957.54.1,4.18.0-80.18.1,4.18.0-147.13.2,4.18.0-80.18.1,3.10.0-514.76.1,3.10.0-1127.8.2,3.10.0-693.67.1,4.18.0-193,4.18.0-193,3.10.0-1127.8.2,4.18.0-147.13.2,3.10.0-1062.26.1,4.18.0-80.18.1,3.10.0-957.54.1,3.10.0-957.54.1,3.10.0-514.76.1,4.18.0-147.13.2,4.18.0-193,3.10.0-1062.26.1,3.10.0-957.54.1,3.10.0-1127.8.2,4.18.0-193,3.10.0-514.76.1,3.10.0-693.67.1,4.18.0-193,3.10.0-1127.8.2;bpftool-debuginfo - 4.18.0-193,4.18.0-147.13.2,3.10.0-1127.8.2,3.10.0-1062.26.1,4.18.0-80.18.1;kpatch-patch-3_10_0-1062_12_1 - 1-2,1-2;kernel-zfcpdump-core - 4.18.0-147.13.2,4.18.0-193;kernel-debug-core - 4.18.0-80.18.1,4.18.0-193,4.18.0-147.13.2,4.18.0-147.13.2,4.18.0-193,4.18.0-147.13.2,4.18.0-193,4.18.0-80.18.1,4.18.0-147.13.2,4.18.0-193;kernel-modules-extra - 4.18.0-147.13.2,4.18.0-193,4.18.0-193,4.18.0-80.18.1,4.18.0-147.13.2,4.18.0-147.13.2,4.18.0-193,4.18.0-80.18.1,4.18.0-193,4.18.0-147.13.2;kernel-rt-debug-devel - 3.10.0-1127.8.2.rt56.1103,4.18.0-193.rt13.51;python-perf - 3.10.0-514.76.1,3.10.0-1127.8.2,3.10.0-693.67.1,3.10.0-1127.8.2,3.10.0-1062.26.1,3.10.0-957.54.1,3.10.0-957.54.1,3.10.0-327.88.1,3.10.0-1062.26.1,3.10.0-693.67.1,3.10.0-514.76.1,3.10.0-1127.8.2,3.10.0-1062.26.1,3.10.0-957.54.1;kernel-core - 4.18.0-147.13.2,4.18.0-193,4.18.0-147.13.2,4.18.0-193,4.18.0-193,4.18.0-147.13.2,4.18.0-80.18.1,4.18.0-193,4.18.0-80.18.1,4.18.0-147.13.2;kernel-rt-debug - 3.10.0-1127.8.2.rt56.1103,4.18.0-193.rt13.51;kernel-rt-devel - 3.10.0-1127.8.2.rt56.1103,4.18.0-193.rt13.51;kernel-debuginfo-common-ppc64 - 3.10.0-957.54.1,3.10.0-1127.8.2,3.10.0-1062.26.1;python3-perf - 4.18.0-193,4.18.0-80.18.1,4.18.0-147.13.2,4.18.0-193,4.18.0-147.13.2,4.18.0-193,4.18.0-80.18.1,4.18.0-193,4.18.0-147.13.2,4.18.0-147.13.2;kernel-tools - 3.10.0-514.76.1,3.10.0-957.54.1,3.10.0-957.54.1,4.18.0-193,4.18.0-147.13.2,4.18.0-80.18.1,3.10.0-1127.8.2,3.10.0-514.76.1,4.18.0-147.13.2,4.18.0-193,4.18.0-80.18.1,3.10.0-1062.26.1,3.10.0-693.67.1,3.10.0-1127.8.2,3.10.0-1062.26.1,3.10.0-327.88.1,3.10.0-1062.26.1,4.18.0-193,3.10.0-957.54.1,3.10.0-693.67.1,4.18.0-147.13.2,3.10.0-1127.8.2;kernel-debug-modules - 4.18.0-147.13.2,4.18.0-147.13.2,4.18.0-193,4.18.0-80.18.1,4.18.0-193,4.18.0-193,4.18.0-147.13.2,4.18.0-193,4.18.0-80.18.1,4.18.0-147.13.2;kernel-rt-trace-kvm - 3.10.0-1127.8.2.rt56.1103;kernel-rt-debuginfo-common-x86_64 - 4.18.0-193.rt13.51;kernel-tools-libs-devel - 3.10.0-514.76.1,3.10.0-327.88.1,3.10.0-693.67.1,3.10.0-1062.26.1,3.10.0-1062.26.1,3.10.0-1127.8.2,3.10.0-957.54.1,3.10.0-693.67.1,3.10.0-1127.8.2,3.10.0-1127.8.2,3.10.0-514.76.1,3.10.0-957.54.1,3.10.0-1062.26.1,3.10.0-957.54.1;kernel-modules - 4.18.0-147.13.2,4.18.0-80.18.1,4.18.0-193,4.18.0-147.13.2,4.18.0-193,4.18.0-80.18.1,4.18.0-193,4.18.0-147.13.2,4.18.0-147.13.2,4.18.0-193;kernel-tools-debuginfo - 3.10.0-1062.26.1,4.18.0-193,3.10.0-1127.8.2,4.18.0-80.18.1,3.10.0-327.88.1,4.18.0-147.13.2,3.10.0-1127.8.2,3.10.0-1062.26.1,3.10.0-957.54.1,3.10.0-957.54.1,3.10.0-514.76.1,3.10.0-693.67.1;kernel-rt-modules - 4.18.0-193.rt13.51;kernel-rt-doc - 3.10.0-1127.8.2.rt56.1103;kernel-rt-kvm - 4.18.0-193.rt13.51,3.10.0-1127.8.2.rt56.1103;python-perf-debuginfo - 3.10.0-693.67.1,3.10.0-1127.8.2,3.10.0-957.54.1,3.10.0-1127.8.2,3.10.0-327.88.1,3.10.0-1062.26.1,3.10.0-957.54.1,3.10.0-514.76.1,3.10.0-1062.26.1;kernel-headers - 3.10.0-1062.26.1,4.18.0-147.13.2,3.10.0-957.54.1,3.10.0-514.76.1,4.18.0-193,4.18.0-80.18.1,4.18.0-147.13.2,3.10.0-327.88.1,3.10.0-1127.8.2,4.18.0-147.13.2,4.18.0-193,3.10.0-1062.26.1,3.10.0-693.67.1,4.18.0-193,3.10.0-1127.8.2,3.10.0-693.67.1,4.18.0-147.13.2,3.10.0-957.54.1,3.10.0-514.76.1,3.10.0-1062.26.1,4.18.0-80.18.1,3.10.0-957.54.1,4.18.0-193,3.10.0-1127.8.2;kernel-rt-trace - 3.10.0-1127.8.2.rt56.1103;kernel-debuginfo-common-x86_64 - 3.10.0-1127.8.2,3.10.0-693.67.1,3.10.0-327.88.1,4.18.0-147.13.2,4.18.0-80.18.1,3.10.0-1062.26.1,3.10.0-514.76.1,4.18.0-193,3.10.0-957.54.1;kernel-rt - 3.10.0-1127.8.2.rt56.1103,4.18.0-193.rt13.51,3.10.0-1127.8.2.rt56.1103,4.18.0-193.rt13.51;kernel-zfcpdump - 4.18.0-147.13.2,4.18.0-193;kernel-rt-debug-modules-extra - 4.18.0-193.rt13.51;python3-perf-debuginfo - 4.18.0-147.13.2,4.18.0-80.18.1,4.18.0-193;kernel-rt-modules-extra - 4.18.0-193.rt13.51</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 linux stable cve high severity vulnerability vulnerable library linux stable julia cartwright s fork of linux stable rt git library home page a href found in base branch master vulnerable source files kernel trace blktrace c kernel trace blktrace c vulnerability details in the linux kernel there is a use after free read in the blk add trace function in kernel trace blktrace c which is used to fill out a blk io trace structure and place it in a per cpu sub buffer 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 kernel doc kernel rt core kernel rt debug debuginfo kernel abi whitelists kernel zfcpdump modules kernel rt trace devel kernel debug modules extra kernel rt debug kvm kernel bootwrapper kernel rt debuginfo kernel rt debug modules kernel zfcpdump devel perf kernel zfcpdump modules extra kernel debuginfo kernel debug devel bpftool kernel rt debug core kernel tools libs perf debuginfo kernel cross headers kernel debug debuginfo kernel debug kernel devel kernel bpftool debuginfo kpatch patch kernel zfcpdump core kernel debug core kernel modules extra kernel rt debug devel python perf kernel core kernel rt debug kernel rt devel kernel debuginfo common perf kernel tools kernel debug modules kernel rt trace kvm kernel rt debuginfo common kernel tools libs devel kernel modules kernel tools debuginfo kernel rt modules kernel rt doc kernel rt kvm python perf debuginfo kernel headers kernel rt trace kernel debuginfo common kernel rt kernel zfcpdump kernel rt debug modules extra perf debuginfo kernel rt modules extra step up your open source security game with mend

IssuesEvent

2022-11-08 11:45:52

Galileo-Galilei/kedro-mlflow

https://api.github.com/repos/Galileo-Galilei/kedro-mlflow

closed

Logging artifact after pipeline ends

documentation question

## Description Case is simple. We want to dump all logs to some log file during pipeline run, and always upload it at the very end as mlflow artifact. ## Context You can see run's logs from mlflow UI. ## Possible Implementation We couldn't find any kedro-mlflow-native way to do it, instead came up with multiple weird workarounds. The cleanest idea we had was to create a custom hook that would manually log the logging file to mlflow via `after_pipeline_run` hook. The problem was, that installed kedro plugins have priority over kedro plugins manually defined in hooks.py, which meant kedro-mlflow's `after_pipeline_run` hook executed before ours and we ended up with duplicated mlflow entries. Our final solution (one that worked) was to use `@hookimpl(tryfirst=True)` for our hook, which would prioritize execution of our's hook over kedro-mlflow's. I guess an alternative solution here would be to use `@hookimpl(trylast=True)` for kedro-mlflow's hook, lowering its priority. ## Possible Alternatives Other than that, do you think there is any better way to do it? Our initial thoughts were to add this file to `catalog.yml` and use `after_context_created` or `after_catalog_created` or `before_pipeline_run` to somehow inject this entry to pipeline's datasets.

1.0

Logging artifact after pipeline ends - ## Description Case is simple. We want to dump all logs to some log file during pipeline run, and always upload it at the very end as mlflow artifact. ## Context You can see run's logs from mlflow UI. ## Possible Implementation We couldn't find any kedro-mlflow-native way to do it, instead came up with multiple weird workarounds. The cleanest idea we had was to create a custom hook that would manually log the logging file to mlflow via `after_pipeline_run` hook. The problem was, that installed kedro plugins have priority over kedro plugins manually defined in hooks.py, which meant kedro-mlflow's `after_pipeline_run` hook executed before ours and we ended up with duplicated mlflow entries. Our final solution (one that worked) was to use `@hookimpl(tryfirst=True)` for our hook, which would prioritize execution of our's hook over kedro-mlflow's. I guess an alternative solution here would be to use `@hookimpl(trylast=True)` for kedro-mlflow's hook, lowering its priority. ## Possible Alternatives Other than that, do you think there is any better way to do it? Our initial thoughts were to add this file to `catalog.yml` and use `after_context_created` or `after_catalog_created` or `before_pipeline_run` to somehow inject this entry to pipeline's datasets.

non_priority

logging artifact after pipeline ends description case is simple we want to dump all logs to some log file during pipeline run and always upload it at the very end as mlflow artifact context you can see run s logs from mlflow ui possible implementation we couldn t find any kedro mlflow native way to do it instead came up with multiple weird workarounds the cleanest idea we had was to create a custom hook that would manually log the logging file to mlflow via after pipeline run hook the problem was that installed kedro plugins have priority over kedro plugins manually defined in hooks py which meant kedro mlflow s after pipeline run hook executed before ours and we ended up with duplicated mlflow entries our final solution one that worked was to use hookimpl tryfirst true for our hook which would prioritize execution of our s hook over kedro mlflow s i guess an alternative solution here would be to use hookimpl trylast true for kedro mlflow s hook lowering its priority possible alternatives other than that do you think there is any better way to do it our initial thoughts were to add this file to catalog yml and use after context created or after catalog created or before pipeline run to somehow inject this entry to pipeline s datasets

IssuesEvent

2017-03-14 04:53:14

VOREStation/VOREStation

https://api.github.com/repos/VOREStation/VOREStation

closed

Slimes don't eat.

Pri: 3-Severe Task: Needs Testing Type: Bug

#### Brief description of the issue More or less the title. #### What you expected to happen They don't eat. #### What actually happened They should. Xenobiology is broken right now. #### Steps to reproduce - (Step 1) Create a slime. - (Step 2) Attempt to feed it. - (Step 3) **Despair.** #### Code Revision - (Found using the "Show Server Revision" verb under the OOC tab.) Server revision: release - 2017-02-25 a199ef8613d6076c103bd3f3b92ea36d7c34a9d3 #### Anything else you may wish to add: - (Location if it's a mapping issue, screenshots, sprites, etc.)

1.0

Slimes don't eat. - #### Brief description of the issue More or less the title. #### What you expected to happen They don't eat. #### What actually happened They should. Xenobiology is broken right now. #### Steps to reproduce - (Step 1) Create a slime. - (Step 2) Attempt to feed it. - (Step 3) **Despair.** #### Code Revision - (Found using the "Show Server Revision" verb under the OOC tab.) Server revision: release - 2017-02-25 a199ef8613d6076c103bd3f3b92ea36d7c34a9d3 #### Anything else you may wish to add: - (Location if it's a mapping issue, screenshots, sprites, etc.)

non_priority

slimes don t eat brief description of the issue more or less the title what you expected to happen they don t eat what actually happened they should xenobiology is broken right now steps to reproduce step create a slime step attempt to feed it step despair code revision found using the show server revision verb under the ooc tab server revision release anything else you may wish to add location if it s a mapping issue screenshots sprites etc

IssuesEvent

2019-08-19 18:51:50

Azure/azure-cli

https://api.github.com/repos/Azure/azure-cli

closed

az cosmosdb collection create not same as in portal

Bug Cosmos Service Attention

When using az cosmos collection create and --partition-key "<val>", the key created is not the same as when creating it through the portal, and results in errors when inserting records. **To Reproduce** az cosmosdb collection create --collection-name <name> --partition-key-path "/_id'" --db-name <DBName> --resource-group <RG_Name> --key <Key> --url <URL> az cosmosdb collection create --collection-name <name> --db-name <DBName> --resource-group <RG_Name> --key <Key> --url <URL> The shard key returned looks like: "partitionKey": { "kind": "Hash", "paths": [ "/_id" ] } When inserting, using the mongoimport.exe using upsert mode, you will get "error inserting documents: query in command must target a single shard key" for each insert (example json below) or with insert you'll get "error inserting documents: document does not contain shard key" Example json: [ { "_id" : "8cd01693-b6be-4bc6-afce-a9f2015523d5", "SomeThing" : "Test", "SomeOtherThing" : "This is what it does", "Severity" : "high" } ] When using the portal to create the partition key, using "_id" and doing a az cosmosdb collection show, as above, you'll see it as: "partitionKey": { "kind": "Hash", "paths": [ "/'$v'/_id/'$v'" ] } And insert or upsert works fine. You'll see in the portal, for both methods, it shows "_/id" as the shard key. There are some posts about this same problem, with workarounds inserting the path with the $v in it, however in azure cli 2.0.55 (and higher) at least it doesn't accept it or pass it as maybe it once did. https://stackoverflow.com/questions/47399720/azure-cli-cosmosdb-partition-key-path-doesnt-work-without-v-before-and-af https://stackoverflow.com/questions/45587691/comosdb-mongoapi-document-does-not-contain-shard-key As it stands, I can't use it to create a new collection, I have to manually create it through the portal. Not sure if there is some known way that the shard key should be passed to get it , but following the examples from the two posts above gives me: Invalid Arg {"Errors":["The partition key component definition path '\/'\\'_id\/'\\'' could not be accepted, failed near position '9'. Partition key paths must contain only valid characters and not contain a trailing slash or wildcard character."]} Maybe this worked previously? Sounded like the posters got passed it, but that was in late 2017. Thanks.

1.0

az cosmosdb collection create not same as in portal - When using az cosmos collection create and --partition-key "<val>", the key created is not the same as when creating it through the portal, and results in errors when inserting records. **To Reproduce** az cosmosdb collection create --collection-name <name> --partition-key-path "/_id'" --db-name <DBName> --resource-group <RG_Name> --key <Key> --url <URL> az cosmosdb collection create --collection-name <name> --db-name <DBName> --resource-group <RG_Name> --key <Key> --url <URL> The shard key returned looks like: "partitionKey": { "kind": "Hash", "paths": [ "/_id" ] } When inserting, using the mongoimport.exe using upsert mode, you will get "error inserting documents: query in command must target a single shard key" for each insert (example json below) or with insert you'll get "error inserting documents: document does not contain shard key" Example json: [ { "_id" : "8cd01693-b6be-4bc6-afce-a9f2015523d5", "SomeThing" : "Test", "SomeOtherThing" : "This is what it does", "Severity" : "high" } ] When using the portal to create the partition key, using "_id" and doing a az cosmosdb collection show, as above, you'll see it as: "partitionKey": { "kind": "Hash", "paths": [ "/'$v'/_id/'$v'" ] } And insert or upsert works fine. You'll see in the portal, for both methods, it shows "_/id" as the shard key. There are some posts about this same problem, with workarounds inserting the path with the $v in it, however in azure cli 2.0.55 (and higher) at least it doesn't accept it or pass it as maybe it once did. https://stackoverflow.com/questions/47399720/azure-cli-cosmosdb-partition-key-path-doesnt-work-without-v-before-and-af https://stackoverflow.com/questions/45587691/comosdb-mongoapi-document-does-not-contain-shard-key As it stands, I can't use it to create a new collection, I have to manually create it through the portal. Not sure if there is some known way that the shard key should be passed to get it , but following the examples from the two posts above gives me: Invalid Arg {"Errors":["The partition key component definition path '\/'\\'_id\/'\\'' could not be accepted, failed near position '9'. Partition key paths must contain only valid characters and not contain a trailing slash or wildcard character."]} Maybe this worked previously? Sounded like the posters got passed it, but that was in late 2017. Thanks.

non_priority

az cosmosdb collection create not same as in portal when using az cosmos collection create and partition key the key created is not the same as when creating it through the portal and results in errors when inserting records to reproduce az cosmosdb collection create collection name partition key path id db name resource group key url az cosmosdb collection create collection name db name resource group key url the shard key returned looks like partitionkey kind hash paths id when inserting using the mongoimport exe using upsert mode you will get error inserting documents query in command must target a single shard key for each insert example json below or with insert you ll get error inserting documents document does not contain shard key example json id afce something test someotherthing this is what it does severity high when using the portal to create the partition key using id and doing a az cosmosdb collection show as above you ll see it as partitionkey kind hash paths v id v and insert or upsert works fine you ll see in the portal for both methods it shows id as the shard key there are some posts about this same problem with workarounds inserting the path with the v in it however in azure cli and higher at least it doesn t accept it or pass it as maybe it once did as it stands i can t use it to create a new collection i have to manually create it through the portal not sure if there is some known way that the shard key should be passed to get it but following the examples from the two posts above gives me invalid arg errors the partition key component definition path id could not be accepted failed near position partition key paths must contain only valid characters and not contain a trailing slash or wildcard character maybe this worked previously sounded like the posters got passed it but that was in late thanks

IssuesEvent

2021-10-04 08:37:22

artsking/linux-3.0.35_CVE-2020-15436_withPatch

https://api.github.com/repos/artsking/linux-3.0.35_CVE-2020-15436_withPatch

closed

CVE-2016-4580 (High) detected in linux-stable-rtv3.8.6 - autoclosed

security vulnerability

## CVE-2016-4580 - High Severity Vulnerability <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>linux-stable-rtv3.8.6</b></p></summary> <p> <p>Julia Cartwright's fork of linux-stable-rt.git</p> <p>Library home page: <a href=https://git.kernel.org/pub/scm/linux/kernel/git/julia/linux-stable-rt.git>https://git.kernel.org/pub/scm/linux/kernel/git/julia/linux-stable-rt.git</a></p> <p>Found in HEAD commit: <a href="https://github.com/artsking/linux-3.0.35_CVE-2020-15436_withPatch/commit/594a70cb9871ddd73cf61197bb1a2a1b1777a7ae">594a70cb9871ddd73cf61197bb1a2a1b1777a7ae</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> <img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/net/x25/x25_facilities.c</b> </p> </details> <p></p> </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary> <p> The x25_negotiate_facilities function in net/x25/x25_facilities.c in the Linux kernel before 4.5.5 does not properly initialize a certain data structure, which allows attackers to obtain sensitive information from kernel stack memory via an X.25 Call Request. <p>Publish Date: 2016-05-23 <p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2016-4580>CVE-2016-4580</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: 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://nvd.nist.gov/vuln/detail/CVE-2016-4580">https://nvd.nist.gov/vuln/detail/CVE-2016-4580</a></p> <p>Release Date: 2016-05-23</p> <p>Fix Resolution: 4.5.5</p> </p> </details> <p></p> *** Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)

True

CVE-2016-4580 (High) detected in linux-stable-rtv3.8.6 - autoclosed - ## CVE-2016-4580 - High Severity Vulnerability <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>linux-stable-rtv3.8.6</b></p></summary> <p> <p>Julia Cartwright's fork of linux-stable-rt.git</p> <p>Library home page: <a href=https://git.kernel.org/pub/scm/linux/kernel/git/julia/linux-stable-rt.git>https://git.kernel.org/pub/scm/linux/kernel/git/julia/linux-stable-rt.git</a></p> <p>Found in HEAD commit: <a href="https://github.com/artsking/linux-3.0.35_CVE-2020-15436_withPatch/commit/594a70cb9871ddd73cf61197bb1a2a1b1777a7ae">594a70cb9871ddd73cf61197bb1a2a1b1777a7ae</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> <img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/net/x25/x25_facilities.c</b> </p> </details> <p></p> </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary> <p> The x25_negotiate_facilities function in net/x25/x25_facilities.c in the Linux kernel before 4.5.5 does not properly initialize a certain data structure, which allows attackers to obtain sensitive information from kernel stack memory via an X.25 Call Request. <p>Publish Date: 2016-05-23 <p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2016-4580>CVE-2016-4580</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: 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://nvd.nist.gov/vuln/detail/CVE-2016-4580">https://nvd.nist.gov/vuln/detail/CVE-2016-4580</a></p> <p>Release Date: 2016-05-23</p> <p>Fix Resolution: 4.5.5</p> </p> </details> <p></p> *** Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)

non_priority

cve high detected in linux stable autoclosed cve high severity vulnerability vulnerable library linux stable julia cartwright s fork of linux stable rt git library home page a href found in head commit a href found in base branch master vulnerable source files net facilities c vulnerability details the negotiate facilities function in net facilities c in the linux kernel before does not properly initialize a certain data structure which allows attackers to obtain sensitive information from kernel stack memory via an x call request publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact high integrity impact none availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution step up your open source security game with whitesource

IssuesEvent

2018-02-01 13:44:31

yogstation13/yogstation-old

https://api.github.com/repos/yogstation13/yogstation-old

closed

warden gear portable security alarm

Balance Feature Request Map Requires Testing Sprite Request Sprites

### Expected Behaviour To function like the armoury alarm sending an alert to sec personal. Similar design as the porta flash but with proximity sensor instead. Replaces one of the portable flashes in armory ### Actual Behaviour It doesn't exist letting the Greytide makes secret tunnels into perma and armory via the labor shuttle dock almost every round blocking doors and theres not much to prevent them as there is no alarm except for using all the portable barriers or waiting to ambush them basically wasting time. ### Steps to reproduce the problem 1. Play warden 2. Check labor shuttle dock 3. False walls everywhere

1.0

warden gear portable security alarm - ### Expected Behaviour To function like the armoury alarm sending an alert to sec personal. Similar design as the porta flash but with proximity sensor instead. Replaces one of the portable flashes in armory ### Actual Behaviour It doesn't exist letting the Greytide makes secret tunnels into perma and armory via the labor shuttle dock almost every round blocking doors and theres not much to prevent them as there is no alarm except for using all the portable barriers or waiting to ambush them basically wasting time. ### Steps to reproduce the problem 1. Play warden 2. Check labor shuttle dock 3. False walls everywhere

non_priority

warden gear portable security alarm expected behaviour to function like the armoury alarm sending an alert to sec personal similar design as the porta flash but with proximity sensor instead replaces one of the portable flashes in armory actual behaviour it doesn t exist letting the greytide makes secret tunnels into perma and armory via the labor shuttle dock almost every round blocking doors and theres not much to prevent them as there is no alarm except for using all the portable barriers or waiting to ambush them basically wasting time steps to reproduce the problem play warden check labor shuttle dock false walls everywhere

IssuesEvent

2021-03-02 04:21:20

stdevPavelmc/FAASGS

https://api.github.com/repos/stdevPavelmc/FAASGS

closed

[BUG] Explain how to install predict and set the conf files.

bug documentation enhancement good first issue help wanted

See references: - https://github.com/stdevPavelmc/FAASGS/issues/14#issuecomment-778827903 - https://github.com/stdevPavelmc/FAASGS/issues/11#issuecomment-774460482 Explain better the installation of predict on the README.

1.0

[BUG] Explain how to install predict and set the conf files. - See references: - https://github.com/stdevPavelmc/FAASGS/issues/14#issuecomment-778827903 - https://github.com/stdevPavelmc/FAASGS/issues/11#issuecomment-774460482 Explain better the installation of predict on the README.

non_priority

explain how to install predict and set the conf files see references explain better the installation of predict on the readme

IssuesEvent

2023-02-14 01:03:00

pkurremula/APIGatewaySolution

https://api.github.com/repos/pkurremula/APIGatewaySolution

closed

Google.Protobuf-3.19.4.0.dll: 1 vulnerabilities (highest severity is: 7.5) - autoclosed

security vulnerability

<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>Google.Protobuf-3.19.4.0.dll</b></p></summary> <p>Google Protocol Buffers</p> <p>Library home page: <a href="https://api.nuget.org/packages/google.protobuf.3.19.4.nupkg">https://api.nuget.org/packages/google.protobuf.3.19.4.nupkg</a></p> <p>Path to vulnerable library: /ProductWebAPI/bin/Debug/net6.0/Google.Protobuf.dll,/bin/Debug/Google.Protobuf.dll</p> <p> <p>Found in HEAD commit: <a href="https://github.com/pkurremula/APIGatewaySolution/commit/0d7da7e7674ec6ef98004de517c5b0109b2cb2a0">0d7da7e7674ec6ef98004de517c5b0109b2cb2a0</a></p></details> ## Vulnerabilities | CVE | Severity | <img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS | Dependency | Type | Fixed in (Google.Protobuf version) | Remediation Available | | ------------- | ------------- | ----- | ----- | ----- | ------------- | --- | | [CVE-2022-1941](https://www.mend.io/vulnerability-database/CVE-2022-1941) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | Google.Protobuf-3.19.4.0.dll | Direct | Google.Protobuf - 3.18.3,3.19.5,3.20.2,3.21.6;protobuf-python - 3.18.3,3.19.5,3.20.2,4.21.6 | &#10060; | ## Details <details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2022-1941</summary> ### Vulnerable Library - <b>Google.Protobuf-3.19.4.0.dll</b></p> <p>Google Protocol Buffers</p> <p>Library home page: <a href="https://api.nuget.org/packages/google.protobuf.3.19.4.nupkg">https://api.nuget.org/packages/google.protobuf.3.19.4.nupkg</a></p> <p>Path to vulnerable library: /ProductWebAPI/bin/Debug/net6.0/Google.Protobuf.dll,/bin/Debug/Google.Protobuf.dll</p> <p> Dependency Hierarchy: - :x: **Google.Protobuf-3.19.4.0.dll** (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/pkurremula/APIGatewaySolution/commit/0d7da7e7674ec6ef98004de517c5b0109b2cb2a0">0d7da7e7674ec6ef98004de517c5b0109b2cb2a0</a></p> <p>Found in base branch: <b>master</b></p> </p> <p></p> ### Vulnerability Details <p> A parsing vulnerability for the MessageSet type in the ProtocolBuffers versions prior to and including 3.16.1, 3.17.3, 3.18.2, 3.19.4, 3.20.1 and 3.21.5 for protobuf-cpp, and versions prior to and including 3.16.1, 3.17.3, 3.18.2, 3.19.4, 3.20.1 and 4.21.5 for protobuf-python can lead to out of memory failures. A specially crafted message with multiple key-value per elements creates parsing issues, and can lead to a Denial of Service against services receiving unsanitized input. We recommend upgrading to versions 3.18.3, 3.19.5, 3.20.2, 3.21.6 for protobuf-cpp and 3.18.3, 3.19.5, 3.20.2, 4.21.6 for protobuf-python. Versions for 3.16 and 3.17 are no longer updated. <p>Publish Date: 2022-09-22 <p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-1941>CVE-2022-1941</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>7.5</b>) <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: None - Integrity Impact: None - Availability Impact: High </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> <p></p> ### Suggested Fix <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://cloud.google.com/support/bulletins#GCP-2022-019">https://cloud.google.com/support/bulletins#GCP-2022-019</a></p> <p>Release Date: 2022-09-22</p> <p>Fix Resolution: Google.Protobuf - 3.18.3,3.19.5,3.20.2,3.21.6;protobuf-python - 3.18.3,3.19.5,3.20.2,4.21.6</p> </p> <p></p> Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) </details>

True

Google.Protobuf-3.19.4.0.dll: 1 vulnerabilities (highest severity is: 7.5) - autoclosed - <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>Google.Protobuf-3.19.4.0.dll</b></p></summary> <p>Google Protocol Buffers</p> <p>Library home page: <a href="https://api.nuget.org/packages/google.protobuf.3.19.4.nupkg">https://api.nuget.org/packages/google.protobuf.3.19.4.nupkg</a></p> <p>Path to vulnerable library: /ProductWebAPI/bin/Debug/net6.0/Google.Protobuf.dll,/bin/Debug/Google.Protobuf.dll</p> <p> <p>Found in HEAD commit: <a href="https://github.com/pkurremula/APIGatewaySolution/commit/0d7da7e7674ec6ef98004de517c5b0109b2cb2a0">0d7da7e7674ec6ef98004de517c5b0109b2cb2a0</a></p></details> ## Vulnerabilities | CVE | Severity | <img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS | Dependency | Type | Fixed in (Google.Protobuf version) | Remediation Available | | ------------- | ------------- | ----- | ----- | ----- | ------------- | --- | | [CVE-2022-1941](https://www.mend.io/vulnerability-database/CVE-2022-1941) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | Google.Protobuf-3.19.4.0.dll | Direct | Google.Protobuf - 3.18.3,3.19.5,3.20.2,3.21.6;protobuf-python - 3.18.3,3.19.5,3.20.2,4.21.6 | &#10060; | ## Details <details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2022-1941</summary> ### Vulnerable Library - <b>Google.Protobuf-3.19.4.0.dll</b></p> <p>Google Protocol Buffers</p> <p>Library home page: <a href="https://api.nuget.org/packages/google.protobuf.3.19.4.nupkg">https://api.nuget.org/packages/google.protobuf.3.19.4.nupkg</a></p> <p>Path to vulnerable library: /ProductWebAPI/bin/Debug/net6.0/Google.Protobuf.dll,/bin/Debug/Google.Protobuf.dll</p> <p> Dependency Hierarchy: - :x: **Google.Protobuf-3.19.4.0.dll** (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/pkurremula/APIGatewaySolution/commit/0d7da7e7674ec6ef98004de517c5b0109b2cb2a0">0d7da7e7674ec6ef98004de517c5b0109b2cb2a0</a></p> <p>Found in base branch: <b>master</b></p> </p> <p></p> ### Vulnerability Details <p> A parsing vulnerability for the MessageSet type in the ProtocolBuffers versions prior to and including 3.16.1, 3.17.3, 3.18.2, 3.19.4, 3.20.1 and 3.21.5 for protobuf-cpp, and versions prior to and including 3.16.1, 3.17.3, 3.18.2, 3.19.4, 3.20.1 and 4.21.5 for protobuf-python can lead to out of memory failures. A specially crafted message with multiple key-value per elements creates parsing issues, and can lead to a Denial of Service against services receiving unsanitized input. We recommend upgrading to versions 3.18.3, 3.19.5, 3.20.2, 3.21.6 for protobuf-cpp and 3.18.3, 3.19.5, 3.20.2, 4.21.6 for protobuf-python. Versions for 3.16 and 3.17 are no longer updated. <p>Publish Date: 2022-09-22 <p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-1941>CVE-2022-1941</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>7.5</b>) <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: None - Integrity Impact: None - Availability Impact: High </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> <p></p> ### Suggested Fix <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://cloud.google.com/support/bulletins#GCP-2022-019">https://cloud.google.com/support/bulletins#GCP-2022-019</a></p> <p>Release Date: 2022-09-22</p> <p>Fix Resolution: Google.Protobuf - 3.18.3,3.19.5,3.20.2,3.21.6;protobuf-python - 3.18.3,3.19.5,3.20.2,4.21.6</p> </p> <p></p> Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) </details>

non_priority

google protobuf dll vulnerabilities highest severity is autoclosed vulnerable library google protobuf dll google protocol buffers library home page a href path to vulnerable library productwebapi bin debug google protobuf dll bin debug google protobuf dll found in head commit a href vulnerabilities cve severity cvss dependency type fixed in google protobuf version remediation available high google protobuf dll direct google protobuf protobuf python details cve vulnerable library google protobuf dll google protocol buffers library home page a href path to vulnerable library productwebapi bin debug google protobuf dll bin debug google protobuf dll dependency hierarchy x google protobuf dll vulnerable library found in head commit a href found in base branch master vulnerability details a parsing vulnerability for the messageset type in the protocolbuffers versions prior to and including and for protobuf cpp and versions prior to and including and for protobuf python can lead to out of memory failures a specially crafted message with multiple key value per elements creates parsing issues and can lead to a denial of service against services receiving unsanitized input we recommend upgrading to versions for protobuf cpp and for protobuf python versions for and are no longer updated 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 google protobuf protobuf python step up your open source security game with mend

IssuesEvent

2022-06-18 11:45:38

tamasfe/taplo

https://api.github.com/repos/tamasfe/taplo

opened

Repo and crate documentation

Help needed documentation

The documentation on the website is mostly up-to-date, however the docs in the repository and the code itself are lagging behind by a lot.

1.0

Repo and crate documentation - The documentation on the website is mostly up-to-date, however the docs in the repository and the code itself are lagging behind by a lot.

non_priority

repo and crate documentation the documentation on the website is mostly up to date however the docs in the repository and the code itself are lagging behind by a lot

IssuesEvent

2022-07-04 21:11:53

Dima2021/cargo-audit

https://api.github.com/repos/Dima2021/cargo-audit

opened

CVE-2021-4044 (High) detected in openssl-src-111.14.0+1.1.1j.crate

security vulnerability

## CVE-2021-4044 - High Severity Vulnerability <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>openssl-src-111.14.0+1.1.1j.crate</b></p></summary> <p>Source of OpenSSL and logic to build it. </p> <p>Library home page: <a href="https://crates.io/api/v1/crates/openssl-src/111.14.0+1.1.1j/download">https://crates.io/api/v1/crates/openssl-src/111.14.0+1.1.1j/download</a></p> <p> Dependency Hierarchy: - rustsec-0.23.3.crate (Root Library) - cargo-edit-0.7.0.crate - reqwest-0.10.10.crate - tokio-tls-0.3.1.crate - native-tls-0.2.7.crate - openssl-0.10.32.crate - openssl-sys-0.9.60.crate - :x: **openssl-src-111.14.0+1.1.1j.crate** (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/Dima2021/cargo-audit/commit/91b6c7a5fffc4969d7d1185aecc6179ebcf18f48">91b6c7a5fffc4969d7d1185aecc6179ebcf18f48</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> Internally libssl in OpenSSL calls X509_verify_cert() on the client side to verify a certificate supplied by a server. That function may return a negative return value to indicate an internal error (for example out of memory). Such a negative return value is mishandled by OpenSSL and will cause an IO function (such as SSL_connect() or SSL_do_handshake()) to not indicate success and a subsequent call to SSL_get_error() to return the value SSL_ERROR_WANT_RETRY_VERIFY. This return value is only supposed to be returned by OpenSSL if the application has previously called SSL_CTX_set_cert_verify_callback(). Since most applications do not do this the SSL_ERROR_WANT_RETRY_VERIFY return value from SSL_get_error() will be totally unexpected and applications may not behave correctly as a result. The exact behaviour will depend on the application but it could result in crashes, infinite loops or other similar incorrect responses. This issue is made more serious in combination with a separate bug in OpenSSL 3.0 that will cause X509_verify_cert() to indicate an internal error when processing a certificate chain. This will occur where a certificate does not include the Subject Alternative Name extension but where a Certificate Authority has enforced name constraints. This issue can occur even with valid chains. By combining the two issues an attacker could induce incorrect, application dependent behaviour. Fixed in OpenSSL 3.0.1 (Affected 3.0.0). <p>Publish Date: 2021-12-14 <p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-4044>CVE-2021-4044</a></p> </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary> <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: None - Integrity Impact: None - Availability Impact: High </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary> <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://github.com/advisories/GHSA-mmjf-f5jw-w72q">https://github.com/advisories/GHSA-mmjf-f5jw-w72q</a></p> <p>Release Date: 2021-12-14</p> <p>Fix Resolution: openssl-src - 300.0.4+3.0.1</p> </p> </details> <p></p>

True

CVE-2021-4044 (High) detected in openssl-src-111.14.0+1.1.1j.crate - ## CVE-2021-4044 - High Severity Vulnerability <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>openssl-src-111.14.0+1.1.1j.crate</b></p></summary> <p>Source of OpenSSL and logic to build it. </p> <p>Library home page: <a href="https://crates.io/api/v1/crates/openssl-src/111.14.0+1.1.1j/download">https://crates.io/api/v1/crates/openssl-src/111.14.0+1.1.1j/download</a></p> <p> Dependency Hierarchy: - rustsec-0.23.3.crate (Root Library) - cargo-edit-0.7.0.crate - reqwest-0.10.10.crate - tokio-tls-0.3.1.crate - native-tls-0.2.7.crate - openssl-0.10.32.crate - openssl-sys-0.9.60.crate - :x: **openssl-src-111.14.0+1.1.1j.crate** (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/Dima2021/cargo-audit/commit/91b6c7a5fffc4969d7d1185aecc6179ebcf18f48">91b6c7a5fffc4969d7d1185aecc6179ebcf18f48</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> Internally libssl in OpenSSL calls X509_verify_cert() on the client side to verify a certificate supplied by a server. That function may return a negative return value to indicate an internal error (for example out of memory). Such a negative return value is mishandled by OpenSSL and will cause an IO function (such as SSL_connect() or SSL_do_handshake()) to not indicate success and a subsequent call to SSL_get_error() to return the value SSL_ERROR_WANT_RETRY_VERIFY. This return value is only supposed to be returned by OpenSSL if the application has previously called SSL_CTX_set_cert_verify_callback(). Since most applications do not do this the SSL_ERROR_WANT_RETRY_VERIFY return value from SSL_get_error() will be totally unexpected and applications may not behave correctly as a result. The exact behaviour will depend on the application but it could result in crashes, infinite loops or other similar incorrect responses. This issue is made more serious in combination with a separate bug in OpenSSL 3.0 that will cause X509_verify_cert() to indicate an internal error when processing a certificate chain. This will occur where a certificate does not include the Subject Alternative Name extension but where a Certificate Authority has enforced name constraints. This issue can occur even with valid chains. By combining the two issues an attacker could induce incorrect, application dependent behaviour. Fixed in OpenSSL 3.0.1 (Affected 3.0.0). <p>Publish Date: 2021-12-14 <p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-4044>CVE-2021-4044</a></p> </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary> <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: None - Integrity Impact: None - Availability Impact: High </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary> <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://github.com/advisories/GHSA-mmjf-f5jw-w72q">https://github.com/advisories/GHSA-mmjf-f5jw-w72q</a></p> <p>Release Date: 2021-12-14</p> <p>Fix Resolution: openssl-src - 300.0.4+3.0.1</p> </p> </details> <p></p>

non_priority

cve high detected in openssl src crate cve high severity vulnerability vulnerable library openssl src crate source of openssl and logic to build it library home page a href dependency hierarchy rustsec crate root library cargo edit crate reqwest crate tokio tls crate native tls crate openssl crate openssl sys crate x openssl src crate vulnerable library found in head commit a href found in base branch main vulnerability details internally libssl in openssl calls verify cert on the client side to verify a certificate supplied by a server that function may return a negative return value to indicate an internal error for example out of memory such a negative return value is mishandled by openssl and will cause an io function such as ssl connect or ssl do handshake to not indicate success and a subsequent call to ssl get error to return the value ssl error want retry verify this return value is only supposed to be returned by openssl if the application has previously called ssl ctx set cert verify callback since most applications do not do this the ssl error want retry verify return value from ssl get error will be totally unexpected and applications may not behave correctly as a result the exact behaviour will depend on the application but it could result in crashes infinite loops or other similar incorrect responses this issue is made more serious in combination with a separate bug in openssl that will cause verify cert to indicate an internal error when processing a certificate chain this will occur where a certificate does not include the subject alternative name extension but where a certificate authority has enforced name constraints this issue can occur even with valid chains by combining the two issues an attacker could induce incorrect application dependent behaviour fixed in openssl affected 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 openssl src

IssuesEvent

2021-03-17 01:16:50

Killy85/python-bot

https://api.github.com/repos/Killy85/python-bot

opened

CVE-2021-27922 (High) detected in Pillow-5.4.1-cp27-cp27mu-manylinux1_x86_64.whl, Pillow-6.0.0-cp27-cp27mu-manylinux1_x86_64.whl

security vulnerability

## CVE-2021-27922 - High Severity Vulnerability <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>Pillow-5.4.1-cp27-cp27mu-manylinux1_x86_64.whl</b>, <b>Pillow-6.0.0-cp27-cp27mu-manylinux1_x86_64.whl</b></p></summary> <p> <details><summary><b>Pillow-5.4.1-cp27-cp27mu-manylinux1_x86_64.whl</b></p></summary> <p>Python Imaging Library (Fork)</p> <p>Library home page: <a href="https://files.pythonhosted.org/packages/0d/f3/421598450cb9503f4565d936860763b5af413a61009d87a5ab1e34139672/Pillow-5.4.1-cp27-cp27mu-manylinux1_x86_64.whl">https://files.pythonhosted.org/packages/0d/f3/421598450cb9503f4565d936860763b5af413a61009d87a5ab1e34139672/Pillow-5.4.1-cp27-cp27mu-manylinux1_x86_64.whl</a></p> <p>Path to vulnerable library: python-bot/requirements.txt</p> <p> Dependency Hierarchy: - :x: **Pillow-5.4.1-cp27-cp27mu-manylinux1_x86_64.whl** (Vulnerable Library) </details> <details><summary><b>Pillow-6.0.0-cp27-cp27mu-manylinux1_x86_64.whl</b></p></summary> <p>Python Imaging Library (Fork)</p> <p>Library home page: <a href="https://files.pythonhosted.org/packages/b6/4b/5adc1109908266554fb978154c797c7d71aba43dd15508d8c1565648f6bc/Pillow-6.0.0-cp27-cp27mu-manylinux1_x86_64.whl">https://files.pythonhosted.org/packages/b6/4b/5adc1109908266554fb978154c797c7d71aba43dd15508d8c1565648f6bc/Pillow-6.0.0-cp27-cp27mu-manylinux1_x86_64.whl</a></p> <p>Path to vulnerable library: python-bot/requirements.txt</p> <p> Dependency Hierarchy: - :x: **Pillow-6.0.0-cp27-cp27mu-manylinux1_x86_64.whl** (Vulnerable Library) </details> </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary> <p> Pillow before 8.1.1 allows attackers to cause a denial of service (memory consumption) because the reported size of a contained image is not properly checked for an ICNS container, and thus an attempted memory allocation can be very large. <p>Publish Date: 2021-03-03 <p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-27922>CVE-2021-27922</a></p> </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary> <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: None - Integrity Impact: None - Availability Impact: High </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> </details> <p></p> *** Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)

True

CVE-2021-27922 (High) detected in Pillow-5.4.1-cp27-cp27mu-manylinux1_x86_64.whl, Pillow-6.0.0-cp27-cp27mu-manylinux1_x86_64.whl - ## CVE-2021-27922 - High Severity Vulnerability <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>Pillow-5.4.1-cp27-cp27mu-manylinux1_x86_64.whl</b>, <b>Pillow-6.0.0-cp27-cp27mu-manylinux1_x86_64.whl</b></p></summary> <p> <details><summary><b>Pillow-5.4.1-cp27-cp27mu-manylinux1_x86_64.whl</b></p></summary> <p>Python Imaging Library (Fork)</p> <p>Library home page: <a href="https://files.pythonhosted.org/packages/0d/f3/421598450cb9503f4565d936860763b5af413a61009d87a5ab1e34139672/Pillow-5.4.1-cp27-cp27mu-manylinux1_x86_64.whl">https://files.pythonhosted.org/packages/0d/f3/421598450cb9503f4565d936860763b5af413a61009d87a5ab1e34139672/Pillow-5.4.1-cp27-cp27mu-manylinux1_x86_64.whl</a></p> <p>Path to vulnerable library: python-bot/requirements.txt</p> <p> Dependency Hierarchy: - :x: **Pillow-5.4.1-cp27-cp27mu-manylinux1_x86_64.whl** (Vulnerable Library) </details> <details><summary><b>Pillow-6.0.0-cp27-cp27mu-manylinux1_x86_64.whl</b></p></summary> <p>Python Imaging Library (Fork)</p> <p>Library home page: <a href="https://files.pythonhosted.org/packages/b6/4b/5adc1109908266554fb978154c797c7d71aba43dd15508d8c1565648f6bc/Pillow-6.0.0-cp27-cp27mu-manylinux1_x86_64.whl">https://files.pythonhosted.org/packages/b6/4b/5adc1109908266554fb978154c797c7d71aba43dd15508d8c1565648f6bc/Pillow-6.0.0-cp27-cp27mu-manylinux1_x86_64.whl</a></p> <p>Path to vulnerable library: python-bot/requirements.txt</p> <p> Dependency Hierarchy: - :x: **Pillow-6.0.0-cp27-cp27mu-manylinux1_x86_64.whl** (Vulnerable Library) </details> </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary> <p> Pillow before 8.1.1 allows attackers to cause a denial of service (memory consumption) because the reported size of a contained image is not properly checked for an ICNS container, and thus an attempted memory allocation can be very large. <p>Publish Date: 2021-03-03 <p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-27922>CVE-2021-27922</a></p> </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary> <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: None - Integrity Impact: None - Availability Impact: High </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> </details> <p></p> *** Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)

non_priority

cve high detected in pillow whl pillow whl cve high severity vulnerability vulnerable libraries pillow whl pillow whl pillow whl python imaging library fork library home page a href path to vulnerable library python bot requirements txt dependency hierarchy x pillow whl vulnerable library pillow whl python imaging library fork library home page a href path to vulnerable library python bot requirements txt dependency hierarchy x pillow whl vulnerable library vulnerability details pillow before allows attackers to cause a denial of service memory consumption because the reported size of a contained image is not properly checked for an icns container and thus an attempted memory allocation can be very large publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact none integrity impact none availability impact high for more information on scores click a href step up your open source security game with whitesource

IssuesEvent

2023-01-31 18:39:15

aj-stein-nist/OSCAL

https://api.github.com/repos/aj-stein-nist/OSCAL

closed

Scheduled Check of Markdown Documents Found Bad Hyperlinks

bug Scope: Documentation

FILE: .github/ABOUT.md [✓] ISSUE_TEMPLATE/ [✓] workflows [✓] CODEOWNERS [✓] issue_template.md 4 links checked. FILE: .github/ISSUE_TEMPLATE/README.md [✓] bug_report.yaml [✓] question.yaml [✓] feature_request.yaml 3 links checked. FILE: .github/PULL_REQUEST_TEMPLATE.md [✓] https://github.com/usnistgov/OSCAL/blob/main/CONTRIBUTING.md [/] https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks/allowing-changes-to-a-pull-request-branch-created-from-a-fork [✓] https://github.com/usnistgov/OSCAL/pulls [✓] https://git-scm.com/book/en/v2/Git-Tools-Rewriting-History [✓] https://creativecommons.org/publicdomain/zero/1.0/ [✓] https://pages.nist.gov/OSCAL 6 links checked. FILE: .github/issue_template.md No hyperlinks found! 0 links checked. FILE: CODE_OF_CONDUCT.md [✓] mailto:[email protected] [✓] http://contributor-covenant.org [✓] http://contributor-covenant.org/version/1/4/ 3 links checked. FILE: CONTRIBUTING.md [✓] #overview [✓] #project-approach [✓] #contribution-options [✓] #issue-reporting-triage-and-handling [✓] #communications-mechanisms [✓] #contributing-to-the-repository [✓] #repository-structure [✓] #contributing-to-a-development-sprint [✓] #user-stories [✓] #issue-status [✓] #reporting-issue-progress [✓] #git-repo-checkout [✓] #initializing-git-submodules [✓] #configuring-submodules-to-use-ssh [✓] #updating-submodules [✓] #licenses-and-attribution [✓] #this-project-is-in-the-public-domain [✓] #contributions-will-be-released-into-the-public-domain [✓] https://github.com/usnistgov/OSCAL/projects [✓] https://opensource.guide/how-to-contribute/ [✓] https://github.com/usnistgov/OSCAL/issues [/] https://help.github.com/articles/creating-an-issue/ [✓] https://github.com/usnistgov/OSCAL/issues/new?template=feature_request.md&labels=enhancement%2C+User+Story [✓] https://github.com/usnistgov/OSCAL/issues/new?template=bug_report.md&labels=bug [✓] https://github.com/usnistgov/OSCAL/issues/new?labels=question&template=question.md [✓] https://github.com/usnistgov/OSCAL/projects/52 [✓] mailto:[email protected] [✓] mailto:[email protected] [✓] mailto:[email protected] [✓] mailto:[email protected] [✓] mailto:[email protected] [✓] mailto:[email protected] [✓] https://github.com/usnistgov/OSCAL/releases [✓] versioning-and-branching.md [/] https://guides.github.com/introduction/flow/ [/] https://help.github.com/articles/fork-a-repo/ [/] https://help.github.com/articles/creating-and-deleting-branches-within-your-repository/ [/] https://help.github.com/articles/creating-a-pull-request-from-a-fork/ [/] https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks/allowing-changes-to-a-pull-request-branch-created-from-a-fork [✓] ./versioning-and-branching.md [/] https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-base-branch-of-a-pull-request [✓] .github [✓] json [✓] xml [✓] docs [✓] https://pages.nist.gov/OSCAL [✓] content [✓] https://github.com/usnistgov/oscal-content/tree/main [✓] build [✓] src [✓] https://github.com/usnistgov/oscal-content/tree/main/src [✓] CODE_OF_CONDUCT.md [✓] CONTRIBUTING.md [✓] LICENSE.md [✓] USERS.md [✓] https://github.com/usnistgov/OSCAL/issues?q=is%3Aopen+is%3Aissue+label%3A%22User+Story%22 [✓] https://github.com/usnistgov/OSCAL/issues/new?labels=User+Story%2C+enhancement&template=feature_request.md [✓] https://creativecommons.org/publicdomain/zero/1.0/ 58 links checked. FILE: LICENSE.md [✓] #this-project-is-in-the-worldwide-public-domain [✓] #fair-use-of-nist-dataworks [✓] #nist-software [✓] #contributions-to-this-project [✓] https://creativecommons.org/publicdomain/zero/1.0/ [✓] https://www.nist.gov/open/license [✓] CONTRIBUTING.md 7 links checked. FILE: README.md [✓] https://gitter.im/usnistgov-OSCAL/Lobby [✓] https://github.com/usnistgov/OSCAL/actions/workflows/status-ci-cd.yml [✓] https://github.com/usnistgov/OSCAL/releases [✓] https://csrc.nist.gov/Projects/Open-Security-Controls-Assessment-Language [✓] https://github.com/usnistgov/OSCAL/blob/main/CONTRIBUTING.md [✓] https://www.nist.gov/oscal [✓] https://pages.nist.gov/OSCAL/reference/ [✓] https://pages.nist.gov/OSCAL/concepts/examples/ [✓] https://github.com/usnistgov/OSCAL/releases [✓] mailto:[email protected] [✓] https://github.com/usnistgov/OSCAL/issues [✓] https://pages.nist.gov/OSCAL/contribute/ [✓] https://www.nist.gov/blogs/cybersecurity-insights/foundation-interoperable-and-portable-security-automation-revealed [✓] https://pages.nist.gov/OSCAL/ [✓] https://github.com/usnistgov/oscal-content/ [✓] https://github.com/usnistgov/oscal-content/tree/main/nist.gov/SP800-53/rev5 [✓] https://github.com/usnistgov/oscal-content/tree/main/nist.gov/SP800-53/rev4 [✖] https://github.com/GSA/fedramp-automation/tree/master/dist/content/baselines/rev4 [✓] mailto:[email protected] [✓] https://pages.nist.gov/OSCAL/contact/ [✓] https://img.shields.io/gitter/room/usnistgov-OSCAL/Lobby [✓] https://github.com/usnistgov/OSCAL/actions/workflows/status-ci-cd.yml/badge.svg [✓] https://img.shields.io/github/v/release/usnistgov/OSCAL?color=green 23 links checked. [✖] https://github.com/GSA/fedramp-automation/tree/master/dist/content/baselines/rev4 → Status: 404 FILE: README_validations.md [✓] https://pages.nist.gov/OSCAL/concepts/layer/validation/ [✓] https://github.com/usnistgov/OSCAL/tree/main/xml/schema [✓] https://github.com/usnistgov/OSCAL/tree/main/json/schema [✓] https://pages.nist.gov/OSCAL/concepts/layer/#status-of-the-oscal-layers [✓] https://www.w3.org/TR/xmlschema-1/ [✓] https://json-schema.org/ [✓] http://xmlsoft.org/xmllint.html [✓] https://github.com/ajv-validator/ajv-cli [✓] https://github.com/usnistgov/OSCAL/blob/main/docs/content/downloads/_index.md#oscal-releases [✓] https://github.com/usnistgov/metaschema/ 10 links checked. FILE: USERS.md No hyperlinks found! 0 links checked. FILE: build/README.md [✓] https://docs.docker.com/install/ [✓] https://docs.docker.com/compose/install/ [✓] https://github.com/rprichard/winpty [✓] https://ubuntu.com/ [✓] https://releases.ubuntu.com/releases/focal/ [✓] https://releases.ubuntu.com/releases/jammy/ [✓] ./ci-cd/config/metaschema [✓] ../docs 8 links checked. FILE: build/ci-cd/README.md [✓] https://pages.nist.gov/OSCAL [✓] https://github.com/usnistgov/OSCAL/blob/master/CONTRIBUTING.md [✓] https://github.com/usnistgov/OSCAL [✓] run-all.sh [✓] validate-metaschema.sh [✓] https://github.com/usnistgov/OSCAL/tree/master/src/metaschema [✓] https://github.com/usnistgov/metaschema/blob/master/toolchains/xslt-M4/validate/metaschema.xsd [✓] generate-schema.sh [✓] https://github.com/usnistgov/OSCAL/tree/master/xml/schema [✓] https://github.com/usnistgov/OSCAL/tree/master/json/schema [✓] validate-content.sh [✓] https://github.com/usnistgov/OSCAL/tree/master/src [✓] generate-content-converters.sh [✓] https://github.com/usnistgov/OSCAL/tree/master/xml/convert [✓] https://github.com/usnistgov/OSCAL/tree/master/json/convert [✓] copy-and-convert-content.sh [✓] https://github.com/usnistgov/OSCAL/tree/master/src/content [✓] validate-content-conversion-round-trips.sh [✓] generate-model-documentation.sh [✓] http://xmlsoft.org/xmllint.html [✓] https://maven.apache.org/ [✓] https://nodejs.org/en/ [✓] https://github.com/jessedc/ajv-cli [✓] https://www.python.org/ [✓] https://search.maven.org/artifact/net.sf.saxon/Saxon-HE [✓] https://www.saxonica.com/download/java.xml 26 links checked. FILE: build/ci-cd/python/readme.md [✓] https://www.python.org/ [✓] http://xmlsoft.org/xmllint.html [✓] http://saxon.sourceforge.net/ 3 links checked. FILE: content/README.md [✓] https://github.com/usnistgov/oscal-content 1 links checked. FILE: content/fedramp.gov/README.md [✖] https://github.com/GSA/fedramp-automation/tree/master/dist/content/baselines 1 links checked. [✖] https://github.com/GSA/fedramp-automation/tree/master/dist/content/baselines → Status: 404 FILE: content/nist.gov/SP800-53/README.md [✓] https://github.com/usnistgov/oscal-content/tree/main/nist.gov/SP800-53 1 links checked. FILE: content/nist.gov/SP800-53/rev4/README.md [✓] https://github.com/usnistgov/oscal-content/tree/main/nist.gov/SP800-53/rev4 1 links checked. FILE: content/nist.gov/SP800-53/rev5/README.md [✓] https://github.com/usnistgov/oscal-content/tree/main/nist.gov/SP800-53/rev5 1 links checked. FILE: git-cheat-sheet.md No hyperlinks found! 0 links checked. FILE: json/README.md [✓] #oscal-json-resources [✓] #table-of-contents [✓] #available-json-resources [✓] #json-schema-for-oscal-models [✓] #validating-oscal-json-content [✓] #oscal-xml-to-json-converters [✓] #converting-oscal-xml-content-to-json [✓] #alternate-invocations [✓] schema [✓] convert [✓] https://json-schema.org/specification-links.html#draft-7 [✓] https://pages.nist.gov/OSCAL/documentation/schema/ [✓] schema/oscal_catalog_schema.json [✓] schema/oscal_profile_schema.json [✓] schema/oscal_ssp_schema.json [✓] schema/oscal_component_schema.json [✓] schema/oscal_assessment-plan_schema.json [✓] schema/oscal_assessment-results_schema.json [✓] schema/oscal_poam_schema.json [✓] https://ajv.js.org/ [✓] https://github.com/jessedc/ajv-cli [✓] ../content [✓] https://github.com/jessedc/ajv-cli#installation [✓] https://nodejs.org/en/download/current/ [✓] https://www.w3.org/TR/xslt-30/ [✓] https://www.w3.org/TR/xpath-31/ [✓] convert/oscal_catalog_xml-to-json-converter.xsl [✓] convert/oscal_profile_xml-to-json-converter.xsl [✓] convert/oscal_ssp_xml-to-json-converter.xsl [✓] convert/oscal_component_xml-to-json-converter.xsl [✓] convert/oscal_assessment-plan_xml-to-json-converter.xsl [✓] convert/oscal_assessment-results_xml-to-json-converter.xsl [✓] convert/oscal_poam_xml-to-json-converter.xsl [✓] http://saxon.sourceforge.net/ [✓] http://saxon.sourceforge.net/#F9.9HE [✓] https://search.maven.org/artifact/net.sf.saxon/Saxon-HE [✓] http://www.saxonica.com [✓] https://www.w3.org/TR/xpath-functions-31/#func-json-to-xml 38 links checked. FILE: src/content/README.md [✓] https://github.com/usnistgov/oscal-content/tree/master/src 1 links checked. FILE: src/file-naming-conventions.md [✓] #oscal-file-naming-conventions [✓] #table-of-contents [✓] #naming-oscal-catalog-and-profile-files [✓] #catalog-example [✓] #profile-examples [✓] #naming-oscal-schema-files [✓] #schema-examples [✓] #naming-oscal-conversion-xsl-templates [✓] #conversion-xslt-example [✓] https://semver.org/ 10 links checked. FILE: src/metaschema/doc-identity-notes.md No hyperlinks found! 0 links checked. FILE: src/metaschema/readme.md [✓] https://pages.nist.gov/OSCAL/docs/schemas/ [✓] https://pages.nist.gov/OSCAL [✓] https://github.com/usnistgov/metaschema/blob/main/toolchains/xslt-M4/validate/metaschema.xsd [✓] https://github.com/usnistgov/metaschema/blob/main/toolchains/xslt-M4/validate/metaschema-composition-check.sch 4 links checked. FILE: src/release/content-upgrade/README.md [✓] https://github.com/usnistgov/OSCAL/releases/tag/v1.0.0-milestone1 [✓] https://github.com/usnistgov/OSCAL/releases/tag/v1.0.0-milestone2 [✓] https://github.com/usnistgov/OSCAL/releases/tag/v1.0.0-milestone3 [✓] https://github.com/usnistgov/OSCAL/releases/tag/v1.0.0-rc1 [✓] https://github.com/usnistgov/OSCAL/releases/tag/v1.0.0-rc2 [✓] https://github.com/usnistgov/OSCAL/releases/tag/v1.0.0 [✓] https://www.oracle.com/java/technologies/downloads/ [✓] http://saxon.sourceforge.net/ [✓] https://www.w3.org/TR/xslt-30/ [✓] https://www.oxygenxml.com/ [✓] https://www.oxygenxml.com/doc/ug-oxygen/topics/xslt-tab.html [✓] https://pages.nist.gov/OSCAL/contact/ [✓] https://www.oxygenxml.com/doc/ug-editor/topics/xslt-stylesheet-parameters.html [✓] https://github.com/usnistgov/OSCAL/tree/main/xml [✓] https://github.com/usnistgov/OSCAL/tree/main/json 15 links checked. FILE: src/release/release-notes.md [✓] https://github.com/usnistgov/OSCAL/releases 1 links checked. FILE: src/specifications/profile-resolution/readme.md [✓] https://pages.nist.gov/OSCAL/concepts/processing/profile-resolution/ [✓] https://gitter.im/usnistgov-OSCAL/Lobby [✓] https://pages.nist.gov/OSCAL/contact/ 3 links checked. FILE: src/utils/schematron/readme.md [✓] oscal-profile.sch 1 links checked. FILE: src/utils/util/readme.md [✓] https://pages.nist.gov/OSCAL/tools/ [✓] https://github.com/usnistgov/oscal-tools 2 links checked. FILE: src/utils/util/resolver-pipeline/readme.md [✓] https://pages.nist.gov/OSCAL/concepts/processing/profile-resolution/ [✓] ../../../specifications/profile-resolution 2 links checked. FILE: src/utils/util/resolver-pipeline/resolver-2018/resolution-notes.md No hyperlinks found! 0 links checked. FILE: versioning-and-branching.md [✓] #versioning [✓] #branching [✓] #versioning-and-branching [✓] #git-setup [✓] #branching-for-contributors [✓] #personal-working-branches [✓] #branching-for-repository-maintainers [✓] #release-branches [✓] #creating-a-release-branch [✓] #releasing-a-release-branch [✓] #releasing-a-patch-revision [✓] #feature-branches [✓] #creating-a-feature-branch [✓] #syncing-a-feature-branch-with-develop [✓] #merging-a-feature-branch [✓] https://semver.org/spec/v2.0.0.html [✓] https://github.com/usnistgov/OSCAL/releases [✓] https://github.com/usnistgov/OSCAL/tree/main [✓] https://github.com/usnistgov/OSCAL/tree/develop [✓] ./CONTRIBUTING.md#contributing-to-the-repository [✓] https://github.com/usnistgov/OSCAL/tree/nist-pages 21 links checked. FILE: xml/README.md [✓] #oscal-xml-resources [✓] #table-of-contents [✓] #available-xml-resources [✓] #xml-schema-for-oscal-models [✓] #validating-oscal-xml-content [✓] #oscal-json-to-xml-converters [✓] #converting-oscal-json-content-to-xml [✓] #alternate-invocations [✓] schema [✓] convert [✓] https://www.w3.org/TR/xmlschema11-1/ [✓] https://pages.nist.gov/OSCAL/documentation/schema/ [✓] schema/oscal_catalog_schema.xsd [✓] schema/oscal_profile_schema.xsd [✓] schema/oscal_ssp_schema.xsd [✓] schema/oscal_component_schema.xsd [✓] schema/oscal_assessment-plan_schema.xsd [✓] schema/oscal_assessment-results_schema.xsd [✓] schema/oscal_poam_schema.xsd [✓] http://xmlsoft.org/xmllint.html [✓] ../content [✓] http://xmlsoft.org/downloads.html [✓] https://www.w3.org/TR/xslt-30/ [✓] https://www.w3.org/TR/xpath-31/ [✓] convert/oscal_catalog_json-to-xml-converter.xsl [✓] convert/oscal_profile_json-to-xml-converter.xsl [✓] convert/oscal_ssp_json-to-xml-converter.xsl [✓] convert/oscal_component_json-to-xml-converter.xsl [✓] convert/oscal_assessment-plan_json-to-xml-converter.xsl [✓] convert/oscal_assessment-results_json-to-xml-converter.xsl [✓] convert/oscal_poam_json-to-xml-converter.xsl [✓] http://saxon.sourceforge.net/ [✓] http://saxon.sourceforge.net/#F9.9HE [✓] https://search.maven.org/artifact/net.sf.saxon/Saxon-HE [✓] http://www.saxonica.com 35 links checked.

1.0

Scheduled Check of Markdown Documents Found Bad Hyperlinks - FILE: .github/ABOUT.md [✓] ISSUE_TEMPLATE/ [✓] workflows [✓] CODEOWNERS [✓] issue_template.md 4 links checked. FILE: .github/ISSUE_TEMPLATE/README.md [✓] bug_report.yaml [✓] question.yaml [✓] feature_request.yaml 3 links checked. FILE: .github/PULL_REQUEST_TEMPLATE.md [✓] https://github.com/usnistgov/OSCAL/blob/main/CONTRIBUTING.md [/] https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks/allowing-changes-to-a-pull-request-branch-created-from-a-fork [✓] https://github.com/usnistgov/OSCAL/pulls [✓] https://git-scm.com/book/en/v2/Git-Tools-Rewriting-History [✓] https://creativecommons.org/publicdomain/zero/1.0/ [✓] https://pages.nist.gov/OSCAL 6 links checked. FILE: .github/issue_template.md No hyperlinks found! 0 links checked. FILE: CODE_OF_CONDUCT.md [✓] mailto:[email protected] [✓] http://contributor-covenant.org [✓] http://contributor-covenant.org/version/1/4/ 3 links checked. FILE: CONTRIBUTING.md [✓] #overview [✓] #project-approach [✓] #contribution-options [✓] #issue-reporting-triage-and-handling [✓] #communications-mechanisms [✓] #contributing-to-the-repository [✓] #repository-structure [✓] #contributing-to-a-development-sprint [✓] #user-stories [✓] #issue-status [✓] #reporting-issue-progress [✓] #git-repo-checkout [✓] #initializing-git-submodules [✓] #configuring-submodules-to-use-ssh [✓] #updating-submodules [✓] #licenses-and-attribution [✓] #this-project-is-in-the-public-domain [✓] #contributions-will-be-released-into-the-public-domain [✓] https://github.com/usnistgov/OSCAL/projects [✓] https://opensource.guide/how-to-contribute/ [✓] https://github.com/usnistgov/OSCAL/issues [/] https://help.github.com/articles/creating-an-issue/ [✓] https://github.com/usnistgov/OSCAL/issues/new?template=feature_request.md&labels=enhancement%2C+User+Story [✓] https://github.com/usnistgov/OSCAL/issues/new?template=bug_report.md&labels=bug [✓] https://github.com/usnistgov/OSCAL/issues/new?labels=question&template=question.md [✓] https://github.com/usnistgov/OSCAL/projects/52 [✓] mailto:[email protected] [✓] mailto:[email protected] [✓] mailto:[email protected] [✓] mailto:[email protected] [✓] mailto:[email protected] [✓] mailto:[email protected] [✓] https://github.com/usnistgov/OSCAL/releases [✓] versioning-and-branching.md [/] https://guides.github.com/introduction/flow/ [/] https://help.github.com/articles/fork-a-repo/ [/] https://help.github.com/articles/creating-and-deleting-branches-within-your-repository/ [/] https://help.github.com/articles/creating-a-pull-request-from-a-fork/ [/] https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks/allowing-changes-to-a-pull-request-branch-created-from-a-fork [✓] ./versioning-and-branching.md [/] https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-base-branch-of-a-pull-request [✓] .github [✓] json [✓] xml [✓] docs [✓] https://pages.nist.gov/OSCAL [✓] content [✓] https://github.com/usnistgov/oscal-content/tree/main [✓] build [✓] src [✓] https://github.com/usnistgov/oscal-content/tree/main/src [✓] CODE_OF_CONDUCT.md [✓] CONTRIBUTING.md [✓] LICENSE.md [✓] USERS.md [✓] https://github.com/usnistgov/OSCAL/issues?q=is%3Aopen+is%3Aissue+label%3A%22User+Story%22 [✓] https://github.com/usnistgov/OSCAL/issues/new?labels=User+Story%2C+enhancement&template=feature_request.md [✓] https://creativecommons.org/publicdomain/zero/1.0/ 58 links checked. FILE: LICENSE.md [✓] #this-project-is-in-the-worldwide-public-domain [✓] #fair-use-of-nist-dataworks [✓] #nist-software [✓] #contributions-to-this-project [✓] https://creativecommons.org/publicdomain/zero/1.0/ [✓] https://www.nist.gov/open/license [✓] CONTRIBUTING.md 7 links checked. FILE: README.md [✓] https://gitter.im/usnistgov-OSCAL/Lobby [✓] https://github.com/usnistgov/OSCAL/actions/workflows/status-ci-cd.yml [✓] https://github.com/usnistgov/OSCAL/releases [✓] https://csrc.nist.gov/Projects/Open-Security-Controls-Assessment-Language [✓] https://github.com/usnistgov/OSCAL/blob/main/CONTRIBUTING.md [✓] https://www.nist.gov/oscal [✓] https://pages.nist.gov/OSCAL/reference/ [✓] https://pages.nist.gov/OSCAL/concepts/examples/ [✓] https://github.com/usnistgov/OSCAL/releases [✓] mailto:[email protected] [✓] https://github.com/usnistgov/OSCAL/issues [✓] https://pages.nist.gov/OSCAL/contribute/ [✓] https://www.nist.gov/blogs/cybersecurity-insights/foundation-interoperable-and-portable-security-automation-revealed [✓] https://pages.nist.gov/OSCAL/ [✓] https://github.com/usnistgov/oscal-content/ [✓] https://github.com/usnistgov/oscal-content/tree/main/nist.gov/SP800-53/rev5 [✓] https://github.com/usnistgov/oscal-content/tree/main/nist.gov/SP800-53/rev4 [✖] https://github.com/GSA/fedramp-automation/tree/master/dist/content/baselines/rev4 [✓] mailto:[email protected] [✓] https://pages.nist.gov/OSCAL/contact/ [✓] https://img.shields.io/gitter/room/usnistgov-OSCAL/Lobby [✓] https://github.com/usnistgov/OSCAL/actions/workflows/status-ci-cd.yml/badge.svg [✓] https://img.shields.io/github/v/release/usnistgov/OSCAL?color=green 23 links checked. [✖] https://github.com/GSA/fedramp-automation/tree/master/dist/content/baselines/rev4 → Status: 404 FILE: README_validations.md [✓] https://pages.nist.gov/OSCAL/concepts/layer/validation/ [✓] https://github.com/usnistgov/OSCAL/tree/main/xml/schema [✓] https://github.com/usnistgov/OSCAL/tree/main/json/schema [✓] https://pages.nist.gov/OSCAL/concepts/layer/#status-of-the-oscal-layers [✓] https://www.w3.org/TR/xmlschema-1/ [✓] https://json-schema.org/ [✓] http://xmlsoft.org/xmllint.html [✓] https://github.com/ajv-validator/ajv-cli [✓] https://github.com/usnistgov/OSCAL/blob/main/docs/content/downloads/_index.md#oscal-releases [✓] https://github.com/usnistgov/metaschema/ 10 links checked. FILE: USERS.md No hyperlinks found! 0 links checked. FILE: build/README.md [✓] https://docs.docker.com/install/ [✓] https://docs.docker.com/compose/install/ [✓] https://github.com/rprichard/winpty [✓] https://ubuntu.com/ [✓] https://releases.ubuntu.com/releases/focal/ [✓] https://releases.ubuntu.com/releases/jammy/ [✓] ./ci-cd/config/metaschema [✓] ../docs 8 links checked. FILE: build/ci-cd/README.md [✓] https://pages.nist.gov/OSCAL [✓] https://github.com/usnistgov/OSCAL/blob/master/CONTRIBUTING.md [✓] https://github.com/usnistgov/OSCAL [✓] run-all.sh [✓] validate-metaschema.sh [✓] https://github.com/usnistgov/OSCAL/tree/master/src/metaschema [✓] https://github.com/usnistgov/metaschema/blob/master/toolchains/xslt-M4/validate/metaschema.xsd [✓] generate-schema.sh [✓] https://github.com/usnistgov/OSCAL/tree/master/xml/schema [✓] https://github.com/usnistgov/OSCAL/tree/master/json/schema [✓] validate-content.sh [✓] https://github.com/usnistgov/OSCAL/tree/master/src [✓] generate-content-converters.sh [✓] https://github.com/usnistgov/OSCAL/tree/master/xml/convert [✓] https://github.com/usnistgov/OSCAL/tree/master/json/convert [✓] copy-and-convert-content.sh [✓] https://github.com/usnistgov/OSCAL/tree/master/src/content [✓] validate-content-conversion-round-trips.sh [✓] generate-model-documentation.sh [✓] http://xmlsoft.org/xmllint.html [✓] https://maven.apache.org/ [✓] https://nodejs.org/en/ [✓] https://github.com/jessedc/ajv-cli [✓] https://www.python.org/ [✓] https://search.maven.org/artifact/net.sf.saxon/Saxon-HE [✓] https://www.saxonica.com/download/java.xml 26 links checked. FILE: build/ci-cd/python/readme.md [✓] https://www.python.org/ [✓] http://xmlsoft.org/xmllint.html [✓] http://saxon.sourceforge.net/ 3 links checked. FILE: content/README.md [✓] https://github.com/usnistgov/oscal-content 1 links checked. FILE: content/fedramp.gov/README.md [✖] https://github.com/GSA/fedramp-automation/tree/master/dist/content/baselines 1 links checked. [✖] https://github.com/GSA/fedramp-automation/tree/master/dist/content/baselines → Status: 404 FILE: content/nist.gov/SP800-53/README.md [✓] https://github.com/usnistgov/oscal-content/tree/main/nist.gov/SP800-53 1 links checked. FILE: content/nist.gov/SP800-53/rev4/README.md [✓] https://github.com/usnistgov/oscal-content/tree/main/nist.gov/SP800-53/rev4 1 links checked. FILE: content/nist.gov/SP800-53/rev5/README.md [✓] https://github.com/usnistgov/oscal-content/tree/main/nist.gov/SP800-53/rev5 1 links checked. FILE: git-cheat-sheet.md No hyperlinks found! 0 links checked. FILE: json/README.md [✓] #oscal-json-resources [✓] #table-of-contents [✓] #available-json-resources [✓] #json-schema-for-oscal-models [✓] #validating-oscal-json-content [✓] #oscal-xml-to-json-converters [✓] #converting-oscal-xml-content-to-json [✓] #alternate-invocations [✓] schema [✓] convert [✓] https://json-schema.org/specification-links.html#draft-7 [✓] https://pages.nist.gov/OSCAL/documentation/schema/ [✓] schema/oscal_catalog_schema.json [✓] schema/oscal_profile_schema.json [✓] schema/oscal_ssp_schema.json [✓] schema/oscal_component_schema.json [✓] schema/oscal_assessment-plan_schema.json [✓] schema/oscal_assessment-results_schema.json [✓] schema/oscal_poam_schema.json [✓] https://ajv.js.org/ [✓] https://github.com/jessedc/ajv-cli [✓] ../content [✓] https://github.com/jessedc/ajv-cli#installation [✓] https://nodejs.org/en/download/current/ [✓] https://www.w3.org/TR/xslt-30/ [✓] https://www.w3.org/TR/xpath-31/ [✓] convert/oscal_catalog_xml-to-json-converter.xsl [✓] convert/oscal_profile_xml-to-json-converter.xsl [✓] convert/oscal_ssp_xml-to-json-converter.xsl [✓] convert/oscal_component_xml-to-json-converter.xsl [✓] convert/oscal_assessment-plan_xml-to-json-converter.xsl [✓] convert/oscal_assessment-results_xml-to-json-converter.xsl [✓] convert/oscal_poam_xml-to-json-converter.xsl [✓] http://saxon.sourceforge.net/ [✓] http://saxon.sourceforge.net/#F9.9HE [✓] https://search.maven.org/artifact/net.sf.saxon/Saxon-HE [✓] http://www.saxonica.com [✓] https://www.w3.org/TR/xpath-functions-31/#func-json-to-xml 38 links checked. FILE: src/content/README.md [✓] https://github.com/usnistgov/oscal-content/tree/master/src 1 links checked. FILE: src/file-naming-conventions.md [✓] #oscal-file-naming-conventions [✓] #table-of-contents [✓] #naming-oscal-catalog-and-profile-files [✓] #catalog-example [✓] #profile-examples [✓] #naming-oscal-schema-files [✓] #schema-examples [✓] #naming-oscal-conversion-xsl-templates [✓] #conversion-xslt-example [✓] https://semver.org/ 10 links checked. FILE: src/metaschema/doc-identity-notes.md No hyperlinks found! 0 links checked. FILE: src/metaschema/readme.md [✓] https://pages.nist.gov/OSCAL/docs/schemas/ [✓] https://pages.nist.gov/OSCAL [✓] https://github.com/usnistgov/metaschema/blob/main/toolchains/xslt-M4/validate/metaschema.xsd [✓] https://github.com/usnistgov/metaschema/blob/main/toolchains/xslt-M4/validate/metaschema-composition-check.sch 4 links checked. FILE: src/release/content-upgrade/README.md [✓] https://github.com/usnistgov/OSCAL/releases/tag/v1.0.0-milestone1 [✓] https://github.com/usnistgov/OSCAL/releases/tag/v1.0.0-milestone2 [✓] https://github.com/usnistgov/OSCAL/releases/tag/v1.0.0-milestone3 [✓] https://github.com/usnistgov/OSCAL/releases/tag/v1.0.0-rc1 [✓] https://github.com/usnistgov/OSCAL/releases/tag/v1.0.0-rc2 [✓] https://github.com/usnistgov/OSCAL/releases/tag/v1.0.0 [✓] https://www.oracle.com/java/technologies/downloads/ [✓] http://saxon.sourceforge.net/ [✓] https://www.w3.org/TR/xslt-30/ [✓] https://www.oxygenxml.com/ [✓] https://www.oxygenxml.com/doc/ug-oxygen/topics/xslt-tab.html [✓] https://pages.nist.gov/OSCAL/contact/ [✓] https://www.oxygenxml.com/doc/ug-editor/topics/xslt-stylesheet-parameters.html [✓] https://github.com/usnistgov/OSCAL/tree/main/xml [✓] https://github.com/usnistgov/OSCAL/tree/main/json 15 links checked. FILE: src/release/release-notes.md [✓] https://github.com/usnistgov/OSCAL/releases 1 links checked. FILE: src/specifications/profile-resolution/readme.md [✓] https://pages.nist.gov/OSCAL/concepts/processing/profile-resolution/ [✓] https://gitter.im/usnistgov-OSCAL/Lobby [✓] https://pages.nist.gov/OSCAL/contact/ 3 links checked. FILE: src/utils/schematron/readme.md [✓] oscal-profile.sch 1 links checked. FILE: src/utils/util/readme.md [✓] https://pages.nist.gov/OSCAL/tools/ [✓] https://github.com/usnistgov/oscal-tools 2 links checked. FILE: src/utils/util/resolver-pipeline/readme.md [✓] https://pages.nist.gov/OSCAL/concepts/processing/profile-resolution/ [✓] ../../../specifications/profile-resolution 2 links checked. FILE: src/utils/util/resolver-pipeline/resolver-2018/resolution-notes.md No hyperlinks found! 0 links checked. FILE: versioning-and-branching.md [✓] #versioning [✓] #branching [✓] #versioning-and-branching [✓] #git-setup [✓] #branching-for-contributors [✓] #personal-working-branches [✓] #branching-for-repository-maintainers [✓] #release-branches [✓] #creating-a-release-branch [✓] #releasing-a-release-branch [✓] #releasing-a-patch-revision [✓] #feature-branches [✓] #creating-a-feature-branch [✓] #syncing-a-feature-branch-with-develop [✓] #merging-a-feature-branch [✓] https://semver.org/spec/v2.0.0.html [✓] https://github.com/usnistgov/OSCAL/releases [✓] https://github.com/usnistgov/OSCAL/tree/main [✓] https://github.com/usnistgov/OSCAL/tree/develop [✓] ./CONTRIBUTING.md#contributing-to-the-repository [✓] https://github.com/usnistgov/OSCAL/tree/nist-pages 21 links checked. FILE: xml/README.md [✓] #oscal-xml-resources [✓] #table-of-contents [✓] #available-xml-resources [✓] #xml-schema-for-oscal-models [✓] #validating-oscal-xml-content [✓] #oscal-json-to-xml-converters [✓] #converting-oscal-json-content-to-xml [✓] #alternate-invocations [✓] schema [✓] convert [✓] https://www.w3.org/TR/xmlschema11-1/ [✓] https://pages.nist.gov/OSCAL/documentation/schema/ [✓] schema/oscal_catalog_schema.xsd [✓] schema/oscal_profile_schema.xsd [✓] schema/oscal_ssp_schema.xsd [✓] schema/oscal_component_schema.xsd [✓] schema/oscal_assessment-plan_schema.xsd [✓] schema/oscal_assessment-results_schema.xsd [✓] schema/oscal_poam_schema.xsd [✓] http://xmlsoft.org/xmllint.html [✓] ../content [✓] http://xmlsoft.org/downloads.html [✓] https://www.w3.org/TR/xslt-30/ [✓] https://www.w3.org/TR/xpath-31/ [✓] convert/oscal_catalog_json-to-xml-converter.xsl [✓] convert/oscal_profile_json-to-xml-converter.xsl [✓] convert/oscal_ssp_json-to-xml-converter.xsl [✓] convert/oscal_component_json-to-xml-converter.xsl [✓] convert/oscal_assessment-plan_json-to-xml-converter.xsl [✓] convert/oscal_assessment-results_json-to-xml-converter.xsl [✓] convert/oscal_poam_json-to-xml-converter.xsl [✓] http://saxon.sourceforge.net/ [✓] http://saxon.sourceforge.net/#F9.9HE [✓] https://search.maven.org/artifact/net.sf.saxon/Saxon-HE [✓] http://www.saxonica.com 35 links checked.

non_priority

scheduled check of markdown documents found bad hyperlinks file github about md issue template workflows codeowners issue template md links checked file github issue template readme md bug report yaml question yaml feature request yaml links checked file github pull request template md links checked file github issue template md no hyperlinks found links checked file code of conduct md mailto oscal nist gov links checked file contributing md overview project approach contribution options issue reporting triage and handling communications mechanisms contributing to the repository repository structure contributing to a development sprint user stories issue status reporting issue progress git repo checkout initializing git submodules configuring submodules to use ssh updating submodules licenses and attribution this project is in the public domain contributions will be released into the public domain mailto oscal dev nist gov mailto oscal dev subscribe list nist gov mailto oscal dev unsubscribe list nist gov mailto oscal updates list nist gov mailto oscal updates subscribe list nist gov mailto oscal updates unsubscribe list nist gov versioning and branching md versioning and branching md github json xml docs content build src code of conduct md contributing md license md users md links checked file license md this project is in the worldwide public domain fair use of nist dataworks nist software contributions to this project contributing md links checked file readme md mailto oscal nist gov mailto oscal dev list nist gov links checked → status file readme validations md links checked file users md no hyperlinks found links checked file build readme md ci cd config metaschema docs links checked file build ci cd readme md run all sh validate metaschema sh generate schema sh validate content sh generate content converters sh copy and convert content sh validate content conversion round trips sh generate model documentation sh links checked file build ci cd python readme md links checked file content readme md links checked file content fedramp gov readme md links checked → status file content nist gov readme md links checked file content nist gov readme md links checked file content nist gov readme md links checked file git cheat sheet md no hyperlinks found links checked file json readme md oscal json resources table of contents available json resources json schema for oscal models validating oscal json content oscal xml to json converters converting oscal xml content to json alternate invocations schema convert schema oscal catalog schema json schema oscal profile schema json schema oscal ssp schema json schema oscal component schema json schema oscal assessment plan schema json schema oscal assessment results schema json schema oscal poam schema json content convert oscal catalog xml to json converter xsl convert oscal profile xml to json converter xsl convert oscal ssp xml to json converter xsl convert oscal component xml to json converter xsl convert oscal assessment plan xml to json converter xsl convert oscal assessment results xml to json converter xsl convert oscal poam xml to json converter xsl links checked file src content readme md links checked file src file naming conventions md oscal file naming conventions table of contents naming oscal catalog and profile files catalog example profile examples naming oscal schema files schema examples naming oscal conversion xsl templates conversion xslt example links checked file src metaschema doc identity notes md no hyperlinks found links checked file src metaschema readme md links checked file src release content upgrade readme md links checked file src release release notes md links checked file src specifications profile resolution readme md links checked file src utils schematron readme md oscal profile sch links checked file src utils util readme md links checked file src utils util resolver pipeline readme md specifications profile resolution links checked file src utils util resolver pipeline resolver resolution notes md no hyperlinks found links checked file versioning and branching md versioning branching versioning and branching git setup branching for contributors personal working branches branching for repository maintainers release branches creating a release branch releasing a release branch releasing a patch revision feature branches creating a feature branch syncing a feature branch with develop merging a feature branch contributing md contributing to the repository links checked file xml readme md oscal xml resources table of contents available xml resources xml schema for oscal models validating oscal xml content oscal json to xml converters converting oscal json content to xml alternate invocations schema convert schema oscal catalog schema xsd schema oscal profile schema xsd schema oscal ssp schema xsd schema oscal component schema xsd schema oscal assessment plan schema xsd schema oscal assessment results schema xsd schema oscal poam schema xsd content convert oscal catalog json to xml converter xsl convert oscal profile json to xml converter xsl convert oscal ssp json to xml converter xsl convert oscal component json to xml converter xsl convert oscal assessment plan json to xml converter xsl convert oscal assessment results json to xml converter xsl convert oscal poam json to xml converter xsl links checked

IssuesEvent

2023-02-06 08:09:54

valtech-ch/microservice-kubernetes-cluster

https://api.github.com/repos/valtech-ch/microservice-kubernetes-cluster

closed

CVE-2021-29425 (Medium) detected in commons-io-2.4.jar - autoclosed

security vulnerability

## CVE-2021-29425 - Medium Severity Vulnerability <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>commons-io-2.4.jar</b></p></summary> <p>The Commons IO library contains utility classes, stream implementations, file filters, file comparators, endian transformation classes, and much more.</p> <p>Library home page: <a href="http://commons.apache.org/io/">http://commons.apache.org/io/</a></p> <p>Path to dependency file: /persistence/build.gradle</p> <p>Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/commons-io/commons-io/2.4/b1b6ea3b7e4aa4f492509a4952029cd8e48019ad/commons-io-2.4.jar</p> <p> Dependency Hierarchy: - springfox-staticdocs-2.6.1.jar (Root Library) - swagger2markup-0.9.2.jar - :x: **commons-io-2.4.jar** (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/valtech-ch/microservice-kubernetes-cluster/commit/335a4047c89f52dfe860e93daefb32dc86a521a2">335a4047c89f52dfe860e93daefb32dc86a521a2</a></p> <p>Found in base branch: <b>develop</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 Apache Commons IO before 2.7, When invoking the method FileNameUtils.normalize with an improper input string, like "//../foo", or "\\..\foo", the result would be the same value, thus possibly providing access to files in the parent directory, but not further above (thus "limited" path traversal), if the calling code would use the result to construct a path value. <p>Publish Date: 2021-04-13 <p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2021-29425>CVE-2021-29425</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>4.8</b>)</summary> <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: High - Privileges Required: None - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: Low - Integrity Impact: Low - Availability Impact: None </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary> <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-29425">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-29425</a></p> <p>Release Date: 2021-04-13</p> <p>Fix Resolution: commons-io:commons-io:2.7</p> </p> </details> <p></p> *** Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)

True

CVE-2021-29425 (Medium) detected in commons-io-2.4.jar - autoclosed - ## CVE-2021-29425 - Medium Severity Vulnerability <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>commons-io-2.4.jar</b></p></summary> <p>The Commons IO library contains utility classes, stream implementations, file filters, file comparators, endian transformation classes, and much more.</p> <p>Library home page: <a href="http://commons.apache.org/io/">http://commons.apache.org/io/</a></p> <p>Path to dependency file: /persistence/build.gradle</p> <p>Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/commons-io/commons-io/2.4/b1b6ea3b7e4aa4f492509a4952029cd8e48019ad/commons-io-2.4.jar</p> <p> Dependency Hierarchy: - springfox-staticdocs-2.6.1.jar (Root Library) - swagger2markup-0.9.2.jar - :x: **commons-io-2.4.jar** (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/valtech-ch/microservice-kubernetes-cluster/commit/335a4047c89f52dfe860e93daefb32dc86a521a2">335a4047c89f52dfe860e93daefb32dc86a521a2</a></p> <p>Found in base branch: <b>develop</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 Apache Commons IO before 2.7, When invoking the method FileNameUtils.normalize with an improper input string, like "//../foo", or "\\..\foo", the result would be the same value, thus possibly providing access to files in the parent directory, but not further above (thus "limited" path traversal), if the calling code would use the result to construct a path value. <p>Publish Date: 2021-04-13 <p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2021-29425>CVE-2021-29425</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>4.8</b>)</summary> <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: High - Privileges Required: None - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: Low - Integrity Impact: Low - Availability Impact: None </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary> <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-29425">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-29425</a></p> <p>Release Date: 2021-04-13</p> <p>Fix Resolution: commons-io:commons-io:2.7</p> </p> </details> <p></p> *** Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)

non_priority

cve medium detected in commons io jar autoclosed cve medium severity vulnerability vulnerable library commons io jar the commons io library contains utility classes stream implementations file filters file comparators endian transformation classes and much more library home page a href path to dependency file persistence build gradle path to vulnerable library home wss scanner gradle caches modules files commons io commons io commons io jar dependency hierarchy springfox staticdocs jar root library jar x commons io jar vulnerable library found in head commit a href found in base branch develop vulnerability details in apache commons io before when invoking the method filenameutils normalize with an improper input string like foo or foo the result would be the same value thus possibly providing access to files in the parent directory but not further above thus limited path traversal if the calling code would use the result to construct a path value publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity high privileges required none user interaction none scope unchanged impact metrics confidentiality impact low integrity impact low availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution commons io commons io step up your open source security game with mend

IssuesEvent

2021-03-07 00:26:55

Submitty/Submitty

https://api.github.com/repos/Submitty/Submitty

closed

Add checks on code coverage of new commits

Testing / Continuous Integration (CI) refactor / coding style

Seeing Matt writing new unit tests these days, I feel we can force new PRs to have at least the same coverage as what we have in the master branch. This would slowly improve the code quality of Submitty over time without too much pain and forces developers to look more closely at their code to avoid some easy bugs (like possibly undefined variables, which happened many times as I can remember). I am not sure if coveralls can do this. If it can't, codecov is good. I see in other projects codecov bot automatically replies in the PR saying if the coverage is increased/decreased.

1.0

Add checks on code coverage of new commits - Seeing Matt writing new unit tests these days, I feel we can force new PRs to have at least the same coverage as what we have in the master branch. This would slowly improve the code quality of Submitty over time without too much pain and forces developers to look more closely at their code to avoid some easy bugs (like possibly undefined variables, which happened many times as I can remember). I am not sure if coveralls can do this. If it can't, codecov is good. I see in other projects codecov bot automatically replies in the PR saying if the coverage is increased/decreased.

non_priority

add checks on code coverage of new commits seeing matt writing new unit tests these days i feel we can force new prs to have at least the same coverage as what we have in the master branch this would slowly improve the code quality of submitty over time without too much pain and forces developers to look more closely at their code to avoid some easy bugs like possibly undefined variables which happened many times as i can remember i am not sure if coveralls can do this if it can t codecov is good i see in other projects codecov bot automatically replies in the pr saying if the coverage is increased decreased

IssuesEvent

2020-04-20 20:47:32

MicrosoftDocs/visualstudio-docs

https://api.github.com/repos/MicrosoftDocs/visualstudio-docs

closed

A Github link to the example described would have been more useful

Pri2 msbuild/tech visual-studio-windows/prod

ReadLinesFromFile task Working Example Missing --- #### Document Details ⚠ *Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.* * ID: 265fb437-d5ed-1c0e-1c34-bd885e7a41cb * Version Independent ID: 4846dbd1-b059-2f96-c94b-610f801a4abc * Content: [ReadLinesFromFile Task - Visual Studio](https://docs.microsoft.com/en-us/visualstudio/msbuild/readlinesfromfile-task?view=vs-2019) * Content Source: [docs/msbuild/readlinesfromfile-task.md](https://github.com/MicrosoftDocs/visualstudio-docs/blob/master/docs/msbuild/readlinesfromfile-task.md) * Product: **visual-studio-windows** * Technology: **msbuild** * GitHub Login: @ghogen * Microsoft Alias: **ghogen**

1.0

A Github link to the example described would have been more useful - ReadLinesFromFile task Working Example Missing --- #### Document Details ⚠ *Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.* * ID: 265fb437-d5ed-1c0e-1c34-bd885e7a41cb * Version Independent ID: 4846dbd1-b059-2f96-c94b-610f801a4abc * Content: [ReadLinesFromFile Task - Visual Studio](https://docs.microsoft.com/en-us/visualstudio/msbuild/readlinesfromfile-task?view=vs-2019) * Content Source: [docs/msbuild/readlinesfromfile-task.md](https://github.com/MicrosoftDocs/visualstudio-docs/blob/master/docs/msbuild/readlinesfromfile-task.md) * Product: **visual-studio-windows** * Technology: **msbuild** * GitHub Login: @ghogen * Microsoft Alias: **ghogen**

non_priority

a github link to the example described would have been more useful readlinesfromfile task working example missing document details ⚠ do not edit this section it is required for docs microsoft com ➟ github issue linking id version independent id content content source product visual studio windows technology msbuild github login ghogen microsoft alias ghogen

IssuesEvent

2017-01-09 07:11:16

minishift/minishift

https://api.github.com/repos/minishift/minishift

opened

Document how to run single test/test case/package in development section

documentation

Currently, in the [development section#running-tests](https://github.com/minishift/minishift/blob/master/docs/developing.md#running-tests), there is no instruction how one can run single test/ test case or package. It is needed for faster development as running entire tests with `make test` may take time. Document the possible ways to test single test/test case or package.

1.0

Document how to run single test/test case/package in development section - Currently, in the [development section#running-tests](https://github.com/minishift/minishift/blob/master/docs/developing.md#running-tests), there is no instruction how one can run single test/ test case or package. It is needed for faster development as running entire tests with `make test` may take time. Document the possible ways to test single test/test case or package.

non_priority

document how to run single test test case package in development section currently in the there is no instruction how one can run single test test case or package it is needed for faster development as running entire tests with make test may take time document the possible ways to test single test test case or package

IssuesEvent

2015-10-30 21:01:57

orientechnologies/orientdb

https://api.github.com/repos/orientechnologies/orientdb

opened

Very bad performance - need help troubleshooting

performance

We are using the Graph API to maintain a Graph of phone handsets calling each other and their voice quality metrics as the calls traverse the network. Our data model is about 16 vertex classes and 32 edge types.

True

Very bad performance - need help troubleshooting - We are using the Graph API to maintain a Graph of phone handsets calling each other and their voice quality metrics as the calls traverse the network. Our data model is about 16 vertex classes and 32 edge types.

non_priority

very bad performance need help troubleshooting we are using the graph api to maintain a graph of phone handsets calling each other and their voice quality metrics as the calls traverse the network our data model is about vertex classes and edge types

IssuesEvent

2019-02-20 20:44:54

material-components/material-components-ios

https://api.github.com/repos/material-components/material-components-ios

closed

[Buttons] Update all documentation references to MDCRaisedButton with MDCContainedButton references instead

[Buttons] type:Documentation

As an iOS Developer using MDC-iOS, I want to see documentation using the most recent recommended APIs. ----- Definition of done: * All documentation referring to `MDCRaisedButton` are updated to use `MDCContainedButton` instead. <!-- Auto-generated content below, do not modify --> --- #### Internal data - Associated internal bug: [b/117179199](http://b/117179199)

1.0

[Buttons] Update all documentation references to MDCRaisedButton with MDCContainedButton references instead - As an iOS Developer using MDC-iOS, I want to see documentation using the most recent recommended APIs. ----- Definition of done: * All documentation referring to `MDCRaisedButton` are updated to use `MDCContainedButton` instead. <!-- Auto-generated content below, do not modify --> --- #### Internal data - Associated internal bug: [b/117179199](http://b/117179199)

non_priority

update all documentation references to mdcraisedbutton with mdccontainedbutton references instead as an ios developer using mdc ios i want to see documentation using the most recent recommended apis definition of done all documentation referring to mdcraisedbutton are updated to use mdccontainedbutton instead internal data associated internal bug

IssuesEvent

2022-12-15 18:59:52

cockroachdb/cockroach

https://api.github.com/repos/cockroachdb/cockroach

closed

logictestccl: the test target often times out at 30 minutes, while the median run time is well below 30 minutes

C-test-failure C-investigation A-testing T-sql-sessions

Many CI runs currently fail with a 30 minutes timeout in `logictestccl`. [Example here](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_UnitTests/3181984?). Possibly (but not certainly) in TestTenantLogic. I am not sure this is expected, given we have many runs which are well below 30 minutes. It may be a deadlock that is difficult to encounter. My suggestion would be to stress-test that package, and detect when a stress run does not make progress any more (which is a different exercise than waiting it to fail).  Jira issue: CRDB-8624

2.0

logictestccl: the test target often times out at 30 minutes, while the median run time is well below 30 minutes - Many CI runs currently fail with a 30 minutes timeout in `logictestccl`. [Example here](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_UnitTests/3181984?). Possibly (but not certainly) in TestTenantLogic. I am not sure this is expected, given we have many runs which are well below 30 minutes. It may be a deadlock that is difficult to encounter. My suggestion would be to stress-test that package, and detect when a stress run does not make progress any more (which is a different exercise than waiting it to fail).  Jira issue: CRDB-8624

non_priority

logictestccl the test target often times out at minutes while the median run time is well below minutes many ci runs currently fail with a minutes timeout in logictestccl possibly but not certainly in testtenantlogic i am not sure this is expected given we have many runs which are well below minutes it may be a deadlock that is difficult to encounter my suggestion would be to stress test that package and detect when a stress run does not make progress any more which is a different exercise than waiting it to fail jira issue crdb

IssuesEvent

2019-11-10 08:54:02

stefanfreitag/IntroToVulnerabilityScanning

https://api.github.com/repos/stefanfreitag/IntroToVulnerabilityScanning

opened

CVE-2018-11698 (High) detected in opennms-opennms-source-25.0.0-1

security vulnerability

## CVE-2018-11698 - High Severity Vulnerability <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>opennmsopennms-source-25.0.0-1</b></p></summary> <p> <p>A Java based fault and performance management system</p> <p>Library home page: <a href=https://sourceforge.net/projects/opennms/>https://sourceforge.net/projects/opennms/</a></p> <p>Found in HEAD commit: <a href="https://github.com/stefanfreitag/IntroToVulnerabilityScanning/commit/367868603e5bd16cc4c63e01d060742fb68e97da">367868603e5bd16cc4c63e01d060742fb68e97da</a></p> </p> </details> </p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Library Source Files (87)</summary> <p></p> <p> * The source files were matched to this source library based on a best effort match. Source libraries are selected from a list of probable public libraries.</p> <p> - /IntroToVulnerabilityScanning/node_modules/console-browserify/test/static/test-adapter.js - /IntroToVulnerabilityScanning/node_modules/nan/nan_callbacks_pre_12_inl.h - /IntroToVulnerabilityScanning/node_modules/node-sass/src/libsass/src/expand.hpp - /IntroToVulnerabilityScanning/node_modules/node-sass/src/libsass/src/expand.cpp - /IntroToVulnerabilityScanning/node_modules/node-sass/src/sass_types/factory.cpp - /IntroToVulnerabilityScanning/node_modules/node-sass/src/libsass/src/operators.cpp - /IntroToVulnerabilityScanning/node_modules/nan/nan_implementation_12_inl.h - /IntroToVulnerabilityScanning/node_modules/node-sass/src/sass_types/boolean.cpp - /IntroToVulnerabilityScanning/node_modules/node-sass/src/libsass/src/util.hpp - /IntroToVulnerabilityScanning/node_modules/node-sass/src/sass_types/value.h - /IntroToVulnerabilityScanning/node_modules/node-sass/src/libsass/src/emitter.hpp - /IntroToVulnerabilityScanning/node_modules/nan/nan_converters_pre_43_inl.h - /IntroToVulnerabilityScanning/node_modules/node-sass/src/callback_bridge.h - /IntroToVulnerabilityScanning/node_modules/node-sass/src/libsass/src/file.cpp - /IntroToVulnerabilityScanning/node_modules/node-sass/src/libsass/src/sass.cpp - /IntroToVulnerabilityScanning/node_modules/nan/nan_persistent_12_inl.h - /IntroToVulnerabilityScanning/node_modules/node-sass/src/libsass/src/operation.hpp - /IntroToVulnerabilityScanning/node_modules/nan/nan_persistent_pre_12_inl.h - /IntroToVulnerabilityScanning/node_modules/node-sass/src/libsass/src/operators.hpp - /IntroToVulnerabilityScanning/node_modules/node-sass/src/libsass/src/constants.hpp - /IntroToVulnerabilityScanning/node_modules/node-sass/src/libsass/src/error_handling.hpp - /IntroToVulnerabilityScanning/node_modules/nan/nan_weak.h - /IntroToVulnerabilityScanning/node_modules/nan/nan_implementation_pre_12_inl.h - /IntroToVulnerabilityScanning/node_modules/node-sass/src/custom_importer_bridge.cpp - /IntroToVulnerabilityScanning/node_modules/node-sass/src/libsass/src/parser.hpp - /IntroToVulnerabilityScanning/node_modules/node-sass/src/libsass/src/constants.cpp - /IntroToVulnerabilityScanning/node_modules/node-sass/src/sass_types/list.cpp - /IntroToVulnerabilityScanning/node_modules/node-sass/src/libsass/src/cssize.cpp - /IntroToVulnerabilityScanning/node_modules/node-sass/src/libsass/src/functions.hpp - /IntroToVulnerabilityScanning/node_modules/node-sass/src/libsass/src/util.cpp - /IntroToVulnerabilityScanning/node_modules/node-sass/src/custom_function_bridge.cpp - /IntroToVulnerabilityScanning/node_modules/nan/nan_typedarray_contents.h - /IntroToVulnerabilityScanning/node_modules/node-sass/src/custom_importer_bridge.h - /IntroToVulnerabilityScanning/node_modules/node-sass/src/libsass/src/bind.cpp - /IntroToVulnerabilityScanning/node_modules/nan/nan_json.h - /IntroToVulnerabilityScanning/node_modules/node-sass/src/libsass/src/eval.hpp - /IntroToVulnerabilityScanning/node_modules/node-sass/src/libsass/src/inspect.cpp - /IntroToVulnerabilityScanning/node_modules/nan/nan_converters.h - /IntroToVulnerabilityScanning/node_modules/node-sass/src/libsass/src/backtrace.cpp - /IntroToVulnerabilityScanning/node_modules/node-sass/src/libsass/src/extend.cpp - /IntroToVulnerabilityScanning/node_modules/nan/nan.h - /IntroToVulnerabilityScanning/node_modules/node-sass/src/sass_context_wrapper.h - /IntroToVulnerabilityScanning/node_modules/node-sass/src/sass_types/sass_value_wrapper.h - /IntroToVulnerabilityScanning/node_modules/node-sass/src/libsass/src/error_handling.cpp - /IntroToVulnerabilityScanning/node_modules/node-sass/src/libsass/src/parser.cpp - /IntroToVulnerabilityScanning/node_modules/node-sass/src/libsass/src/debugger.hpp - /IntroToVulnerabilityScanning/node_modules/node-sass/src/libsass/src/emitter.cpp - /IntroToVulnerabilityScanning/node_modules/node-sass/src/sass_types/number.cpp - /IntroToVulnerabilityScanning/node_modules/node-sass/src/sass_types/color.h - /IntroToVulnerabilityScanning/node_modules/nan/nan_new.h - /IntroToVulnerabilityScanning/node_modules/nan/nan_maybe_pre_43_inl.h - /IntroToVulnerabilityScanning/node_modules/node-sass/src/libsass/src/sass_values.cpp - /IntroToVulnerabilityScanning/node_modules/node-sass/src/libsass/src/ast.hpp - /IntroToVulnerabilityScanning/node_modules/nan/nan_callbacks_12_inl.h - /IntroToVulnerabilityScanning/node_modules/nan/nan_maybe_43_inl.h - /IntroToVulnerabilityScanning/node_modules/nan/nan_object_wrap.h - /IntroToVulnerabilityScanning/node_modules/node-sass/src/libsass/src/output.cpp - /IntroToVulnerabilityScanning/node_modules/node-sass/src/libsass/src/check_nesting.cpp - /IntroToVulnerabilityScanning/node_modules/node-sass/src/sass_types/null.cpp - /IntroToVulnerabilityScanning/node_modules/node-sass/src/libsass/src/ast_def_macros.hpp - /IntroToVulnerabilityScanning/node_modules/node-sass/src/libsass/src/functions.cpp - /IntroToVulnerabilityScanning/node_modules/node-sass/src/libsass/src/cssize.hpp - /IntroToVulnerabilityScanning/node_modules/node-sass/src/libsass/src/prelexer.cpp - /IntroToVulnerabilityScanning/node_modules/node-sass/src/libsass/src/ast.cpp - /IntroToVulnerabilityScanning/node_modules/node-sass/src/libsass/src/to_c.cpp - /IntroToVulnerabilityScanning/node_modules/node-sass/src/libsass/src/to_value.hpp - /IntroToVulnerabilityScanning/node_modules/node-sass/src/libsass/src/ast_fwd_decl.hpp - /IntroToVulnerabilityScanning/node_modules/nan/nan_callbacks.h - /IntroToVulnerabilityScanning/node_modules/node-sass/src/libsass/src/inspect.hpp - /IntroToVulnerabilityScanning/node_modules/node-sass/src/sass_types/color.cpp - /IntroToVulnerabilityScanning/node_modules/node-sass/src/libsass/src/values.cpp - /IntroToVulnerabilityScanning/node_modules/node-sass/src/sass_context_wrapper.cpp - /IntroToVulnerabilityScanning/node_modules/node-sass/src/sass_types/list.h - /IntroToVulnerabilityScanning/node_modules/node-sass/src/libsass/src/check_nesting.hpp - /IntroToVulnerabilityScanning/node_modules/nan/nan_define_own_property_helper.h - /IntroToVulnerabilityScanning/node_modules/node-sass/src/sass_types/map.cpp - /IntroToVulnerabilityScanning/node_modules/node-sass/src/libsass/src/to_value.cpp - /IntroToVulnerabilityScanning/node_modules/node-sass/src/libsass/src/context.cpp - /IntroToVulnerabilityScanning/node_modules/node-sass/src/binding.cpp - /IntroToVulnerabilityScanning/node_modules/node-sass/src/sass_types/string.cpp - /IntroToVulnerabilityScanning/node_modules/node-sass/src/libsass/src/sass_context.cpp - /IntroToVulnerabilityScanning/node_modules/nan/nan_converters_43_inl.h - /IntroToVulnerabilityScanning/node_modules/node-sass/src/libsass/src/prelexer.hpp - /IntroToVulnerabilityScanning/node_modules/node-sass/src/libsass/src/context.hpp - /IntroToVulnerabilityScanning/node_modules/node-sass/src/sass_types/boolean.h - /IntroToVulnerabilityScanning/node_modules/nan/nan_private.h - /IntroToVulnerabilityScanning/node_modules/node-sass/src/libsass/src/eval.cpp </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> An issue was discovered in LibSass through 3.5.4. An out-of-bounds read of a memory region was found in the function Sass::handle_error which could be leveraged by an attacker to disclose information or manipulated to read from unmapped memory causing a denial of service. <p>Publish Date: 2018-06-04 <p>URL: <a href=https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-11698>CVE-2018-11698</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: 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-11698">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-11698</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-11698 (High) detected in opennms-opennms-source-25.0.0-1 - ## CVE-2018-11698 - High Severity Vulnerability <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>opennmsopennms-source-25.0.0-1</b></p></summary> <p> <p>A Java based fault and performance management system</p> <p>Library home page: <a href=https://sourceforge.net/projects/opennms/>https://sourceforge.net/projects/opennms/</a></p> <p>Found in HEAD commit: <a href="https://github.com/stefanfreitag/IntroToVulnerabilityScanning/commit/367868603e5bd16cc4c63e01d060742fb68e97da">367868603e5bd16cc4c63e01d060742fb68e97da</a></p> </p> </details> </p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Library Source Files (87)</summary> <p></p> <p> * The source files were matched to this source library based on a best effort match. Source libraries are selected from a list of probable public libraries.</p> <p> - /IntroToVulnerabilityScanning/node_modules/console-browserify/test/static/test-adapter.js - /IntroToVulnerabilityScanning/node_modules/nan/nan_callbacks_pre_12_inl.h - /IntroToVulnerabilityScanning/node_modules/node-sass/src/libsass/src/expand.hpp - /IntroToVulnerabilityScanning/node_modules/node-sass/src/libsass/src/expand.cpp - /IntroToVulnerabilityScanning/node_modules/node-sass/src/sass_types/factory.cpp - /IntroToVulnerabilityScanning/node_modules/node-sass/src/libsass/src/operators.cpp - /IntroToVulnerabilityScanning/node_modules/nan/nan_implementation_12_inl.h - /IntroToVulnerabilityScanning/node_modules/node-sass/src/sass_types/boolean.cpp - /IntroToVulnerabilityScanning/node_modules/node-sass/src/libsass/src/util.hpp - /IntroToVulnerabilityScanning/node_modules/node-sass/src/sass_types/value.h - /IntroToVulnerabilityScanning/node_modules/node-sass/src/libsass/src/emitter.hpp - /IntroToVulnerabilityScanning/node_modules/nan/nan_converters_pre_43_inl.h - /IntroToVulnerabilityScanning/node_modules/node-sass/src/callback_bridge.h - /IntroToVulnerabilityScanning/node_modules/node-sass/src/libsass/src/file.cpp - /IntroToVulnerabilityScanning/node_modules/node-sass/src/libsass/src/sass.cpp - /IntroToVulnerabilityScanning/node_modules/nan/nan_persistent_12_inl.h - /IntroToVulnerabilityScanning/node_modules/node-sass/src/libsass/src/operation.hpp - /IntroToVulnerabilityScanning/node_modules/nan/nan_persistent_pre_12_inl.h - /IntroToVulnerabilityScanning/node_modules/node-sass/src/libsass/src/operators.hpp - /IntroToVulnerabilityScanning/node_modules/node-sass/src/libsass/src/constants.hpp - /IntroToVulnerabilityScanning/node_modules/node-sass/src/libsass/src/error_handling.hpp - /IntroToVulnerabilityScanning/node_modules/nan/nan_weak.h - /IntroToVulnerabilityScanning/node_modules/nan/nan_implementation_pre_12_inl.h - /IntroToVulnerabilityScanning/node_modules/node-sass/src/custom_importer_bridge.cpp - /IntroToVulnerabilityScanning/node_modules/node-sass/src/libsass/src/parser.hpp - /IntroToVulnerabilityScanning/node_modules/node-sass/src/libsass/src/constants.cpp - /IntroToVulnerabilityScanning/node_modules/node-sass/src/sass_types/list.cpp - /IntroToVulnerabilityScanning/node_modules/node-sass/src/libsass/src/cssize.cpp - /IntroToVulnerabilityScanning/node_modules/node-sass/src/libsass/src/functions.hpp - /IntroToVulnerabilityScanning/node_modules/node-sass/src/libsass/src/util.cpp - /IntroToVulnerabilityScanning/node_modules/node-sass/src/custom_function_bridge.cpp - /IntroToVulnerabilityScanning/node_modules/nan/nan_typedarray_contents.h - /IntroToVulnerabilityScanning/node_modules/node-sass/src/custom_importer_bridge.h - /IntroToVulnerabilityScanning/node_modules/node-sass/src/libsass/src/bind.cpp - /IntroToVulnerabilityScanning/node_modules/nan/nan_json.h - /IntroToVulnerabilityScanning/node_modules/node-sass/src/libsass/src/eval.hpp - /IntroToVulnerabilityScanning/node_modules/node-sass/src/libsass/src/inspect.cpp - /IntroToVulnerabilityScanning/node_modules/nan/nan_converters.h - /IntroToVulnerabilityScanning/node_modules/node-sass/src/libsass/src/backtrace.cpp - /IntroToVulnerabilityScanning/node_modules/node-sass/src/libsass/src/extend.cpp - /IntroToVulnerabilityScanning/node_modules/nan/nan.h - /IntroToVulnerabilityScanning/node_modules/node-sass/src/sass_context_wrapper.h - /IntroToVulnerabilityScanning/node_modules/node-sass/src/sass_types/sass_value_wrapper.h - /IntroToVulnerabilityScanning/node_modules/node-sass/src/libsass/src/error_handling.cpp - /IntroToVulnerabilityScanning/node_modules/node-sass/src/libsass/src/parser.cpp - /IntroToVulnerabilityScanning/node_modules/node-sass/src/libsass/src/debugger.hpp - /IntroToVulnerabilityScanning/node_modules/node-sass/src/libsass/src/emitter.cpp - /IntroToVulnerabilityScanning/node_modules/node-sass/src/sass_types/number.cpp - /IntroToVulnerabilityScanning/node_modules/node-sass/src/sass_types/color.h - /IntroToVulnerabilityScanning/node_modules/nan/nan_new.h - /IntroToVulnerabilityScanning/node_modules/nan/nan_maybe_pre_43_inl.h - /IntroToVulnerabilityScanning/node_modules/node-sass/src/libsass/src/sass_values.cpp - /IntroToVulnerabilityScanning/node_modules/node-sass/src/libsass/src/ast.hpp - /IntroToVulnerabilityScanning/node_modules/nan/nan_callbacks_12_inl.h - /IntroToVulnerabilityScanning/node_modules/nan/nan_maybe_43_inl.h - /IntroToVulnerabilityScanning/node_modules/nan/nan_object_wrap.h - /IntroToVulnerabilityScanning/node_modules/node-sass/src/libsass/src/output.cpp - /IntroToVulnerabilityScanning/node_modules/node-sass/src/libsass/src/check_nesting.cpp - /IntroToVulnerabilityScanning/node_modules/node-sass/src/sass_types/null.cpp - /IntroToVulnerabilityScanning/node_modules/node-sass/src/libsass/src/ast_def_macros.hpp - /IntroToVulnerabilityScanning/node_modules/node-sass/src/libsass/src/functions.cpp - /IntroToVulnerabilityScanning/node_modules/node-sass/src/libsass/src/cssize.hpp - /IntroToVulnerabilityScanning/node_modules/node-sass/src/libsass/src/prelexer.cpp - /IntroToVulnerabilityScanning/node_modules/node-sass/src/libsass/src/ast.cpp - /IntroToVulnerabilityScanning/node_modules/node-sass/src/libsass/src/to_c.cpp - /IntroToVulnerabilityScanning/node_modules/node-sass/src/libsass/src/to_value.hpp - /IntroToVulnerabilityScanning/node_modules/node-sass/src/libsass/src/ast_fwd_decl.hpp - /IntroToVulnerabilityScanning/node_modules/nan/nan_callbacks.h - /IntroToVulnerabilityScanning/node_modules/node-sass/src/libsass/src/inspect.hpp - /IntroToVulnerabilityScanning/node_modules/node-sass/src/sass_types/color.cpp - /IntroToVulnerabilityScanning/node_modules/node-sass/src/libsass/src/values.cpp - /IntroToVulnerabilityScanning/node_modules/node-sass/src/sass_context_wrapper.cpp - /IntroToVulnerabilityScanning/node_modules/node-sass/src/sass_types/list.h - /IntroToVulnerabilityScanning/node_modules/node-sass/src/libsass/src/check_nesting.hpp - /IntroToVulnerabilityScanning/node_modules/nan/nan_define_own_property_helper.h - /IntroToVulnerabilityScanning/node_modules/node-sass/src/sass_types/map.cpp - /IntroToVulnerabilityScanning/node_modules/node-sass/src/libsass/src/to_value.cpp - /IntroToVulnerabilityScanning/node_modules/node-sass/src/libsass/src/context.cpp - /IntroToVulnerabilityScanning/node_modules/node-sass/src/binding.cpp - /IntroToVulnerabilityScanning/node_modules/node-sass/src/sass_types/string.cpp - /IntroToVulnerabilityScanning/node_modules/node-sass/src/libsass/src/sass_context.cpp - /IntroToVulnerabilityScanning/node_modules/nan/nan_converters_43_inl.h - /IntroToVulnerabilityScanning/node_modules/node-sass/src/libsass/src/prelexer.hpp - /IntroToVulnerabilityScanning/node_modules/node-sass/src/libsass/src/context.hpp - /IntroToVulnerabilityScanning/node_modules/node-sass/src/sass_types/boolean.h - /IntroToVulnerabilityScanning/node_modules/nan/nan_private.h - /IntroToVulnerabilityScanning/node_modules/node-sass/src/libsass/src/eval.cpp </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> An issue was discovered in LibSass through 3.5.4. An out-of-bounds read of a memory region was found in the function Sass::handle_error which could be leveraged by an attacker to disclose information or manipulated to read from unmapped memory causing a denial of service. <p>Publish Date: 2018-06-04 <p>URL: <a href=https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-11698>CVE-2018-11698</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: 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-11698">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-11698</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 high detected in opennms opennms source cve high severity vulnerability vulnerable library opennmsopennms source a java based fault and performance management system library home page a href found in head commit a href library source files the source files were matched to this source library based on a best effort match source libraries are selected from a list of probable public libraries introtovulnerabilityscanning node modules console browserify test static test adapter js introtovulnerabilityscanning node modules nan nan callbacks pre inl h introtovulnerabilityscanning node modules node sass src libsass src expand hpp introtovulnerabilityscanning node modules node sass src libsass src expand cpp introtovulnerabilityscanning node modules node sass src sass types factory cpp introtovulnerabilityscanning node modules node sass src libsass src operators cpp introtovulnerabilityscanning node modules nan nan implementation inl h introtovulnerabilityscanning node modules node sass src sass types boolean cpp introtovulnerabilityscanning node modules node sass src libsass src util hpp introtovulnerabilityscanning node modules node sass src sass types value h introtovulnerabilityscanning node modules node sass src libsass src emitter hpp introtovulnerabilityscanning node modules nan nan converters pre inl h introtovulnerabilityscanning node modules node sass src callback bridge h introtovulnerabilityscanning node modules node sass src libsass src file cpp introtovulnerabilityscanning node modules node sass src libsass src sass cpp introtovulnerabilityscanning node modules nan nan persistent inl h introtovulnerabilityscanning node modules node sass src libsass src operation hpp introtovulnerabilityscanning node modules nan nan persistent pre inl h introtovulnerabilityscanning node modules node sass src libsass src operators hpp introtovulnerabilityscanning node modules node sass src libsass src constants hpp introtovulnerabilityscanning node modules node sass src libsass src error handling hpp introtovulnerabilityscanning node modules nan nan weak h introtovulnerabilityscanning node modules nan nan implementation pre inl h introtovulnerabilityscanning node modules node sass src custom importer bridge cpp introtovulnerabilityscanning node modules node sass src libsass src parser hpp introtovulnerabilityscanning node modules node sass src libsass src constants cpp introtovulnerabilityscanning node modules node sass src sass types list cpp introtovulnerabilityscanning node modules node sass src libsass src cssize cpp introtovulnerabilityscanning node modules node sass src libsass src functions hpp introtovulnerabilityscanning node modules node sass src libsass src util cpp introtovulnerabilityscanning node modules node sass src custom function bridge cpp introtovulnerabilityscanning node modules nan nan typedarray contents h introtovulnerabilityscanning node modules node sass src custom importer bridge h introtovulnerabilityscanning node modules node sass src libsass src bind cpp introtovulnerabilityscanning node modules nan nan json h introtovulnerabilityscanning node modules node sass src libsass src eval hpp introtovulnerabilityscanning node modules node sass src libsass src inspect cpp introtovulnerabilityscanning node modules nan nan converters h introtovulnerabilityscanning node modules node sass src libsass src backtrace cpp introtovulnerabilityscanning node modules node sass src libsass src extend cpp introtovulnerabilityscanning node modules nan nan h introtovulnerabilityscanning node modules node sass src sass context wrapper h introtovulnerabilityscanning node modules node sass src sass types sass value wrapper h introtovulnerabilityscanning node modules node sass src libsass src error handling cpp introtovulnerabilityscanning node modules node sass src libsass src parser cpp introtovulnerabilityscanning node modules node sass src libsass src debugger hpp introtovulnerabilityscanning node modules node sass src libsass src emitter cpp introtovulnerabilityscanning node modules node sass src sass types number cpp introtovulnerabilityscanning node modules node sass src sass types color h introtovulnerabilityscanning node modules nan nan new h introtovulnerabilityscanning node modules nan nan maybe pre inl h introtovulnerabilityscanning node modules node sass src libsass src sass values cpp introtovulnerabilityscanning node modules node sass src libsass src ast hpp introtovulnerabilityscanning node modules nan nan callbacks inl h introtovulnerabilityscanning node modules nan nan maybe inl h introtovulnerabilityscanning node modules nan nan object wrap h introtovulnerabilityscanning node modules node sass src libsass src output cpp introtovulnerabilityscanning node modules node sass src libsass src check nesting cpp introtovulnerabilityscanning node modules node sass src sass types null cpp introtovulnerabilityscanning node modules node sass src libsass src ast def macros hpp introtovulnerabilityscanning node modules node sass src libsass src functions cpp introtovulnerabilityscanning node modules node sass src libsass src cssize hpp introtovulnerabilityscanning node modules node sass src libsass src prelexer cpp introtovulnerabilityscanning node modules node sass src libsass src ast cpp introtovulnerabilityscanning node modules node sass src libsass src to c cpp introtovulnerabilityscanning node modules node sass src libsass src to value hpp introtovulnerabilityscanning node modules node sass src libsass src ast fwd decl hpp introtovulnerabilityscanning node modules nan nan callbacks h introtovulnerabilityscanning node modules node sass src libsass src inspect hpp introtovulnerabilityscanning node modules node sass src sass types color cpp introtovulnerabilityscanning node modules node sass src libsass src values cpp introtovulnerabilityscanning node modules node sass src sass context wrapper cpp introtovulnerabilityscanning node modules node sass src sass types list h introtovulnerabilityscanning node modules node sass src libsass src check nesting hpp introtovulnerabilityscanning node modules nan nan define own property helper h introtovulnerabilityscanning node modules node sass src sass types map cpp introtovulnerabilityscanning node modules node sass src libsass src to value cpp introtovulnerabilityscanning node modules node sass src libsass src context cpp introtovulnerabilityscanning node modules node sass src binding cpp introtovulnerabilityscanning node modules node sass src sass types string cpp introtovulnerabilityscanning node modules node sass src libsass src sass context cpp introtovulnerabilityscanning node modules nan nan converters inl h introtovulnerabilityscanning node modules node sass src libsass src prelexer hpp introtovulnerabilityscanning node modules node sass src libsass src context hpp introtovulnerabilityscanning node modules node sass src sass types boolean h introtovulnerabilityscanning node modules nan nan private h introtovulnerabilityscanning node modules node sass src libsass src eval cpp vulnerability details an issue was discovered in libsass through an out of bounds read of a memory region was found in the function sass handle error which could be leveraged by an attacker to disclose information or manipulated to read from unmapped memory causing a denial of service publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction required scope unchanged impact metrics confidentiality impact high 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

IssuesEvent

2021-02-05 06:10:52

codeblooded/grpc

https://api.github.com/repos/codeblooded/grpc

closed

Create nodes on demand using the autoscaler

P2 design orch someday

This idea was provided by @gnossen, and it may solve some issues. There are several considerations, though: - Resource and cost limits (what would be our max/min nodes/pool? How do we handle cases where we need to scale >max?) - Handling the case when the autoscaler can't scale in a zone or does not fully descale (pod budget options) - Ensuring the autoscaler can work with our complicated pooling business logic This issue serves as a reminder and tracker for discussions and progress.

1.0

Create nodes on demand using the autoscaler - This idea was provided by @gnossen, and it may solve some issues. There are several considerations, though: - Resource and cost limits (what would be our max/min nodes/pool? How do we handle cases where we need to scale >max?) - Handling the case when the autoscaler can't scale in a zone or does not fully descale (pod budget options) - Ensuring the autoscaler can work with our complicated pooling business logic This issue serves as a reminder and tracker for discussions and progress.

non_priority

create nodes on demand using the autoscaler this idea was provided by gnossen and it may solve some issues there are several considerations though resource and cost limits what would be our max min nodes pool how do we handle cases where we need to scale max handling the case when the autoscaler can t scale in a zone or does not fully descale pod budget options ensuring the autoscaler can work with our complicated pooling business logic this issue serves as a reminder and tracker for discussions and progress

IssuesEvent

2021-05-08 01:05:09

Princeton-CDH/geniza

https://api.github.com/repos/Princeton-CDH/geniza

closed

Revise the document title so that it can appear on search and browse results, + the document detail view, scholarship records, external links as the page title

💬 awaiting review 🗺️ design

I have revised the document title, [here](https://www.figma.com/file/HpGBOZi9lO8B3nCAx3d4Fj/Princeton-Geniza-Project-team?node-id=851%3A6486) You can find the revised document title in following pages in the link above - document detail view - scholarship records - external links - search results - browse results There is more: - PGP ID is at the bottom of the document detail view, scholarship records, and external links. - There are design proposals for what the UI looks like when a document has 1 shelfmark, vs when it has more than one shelfmark (along with the states, default and selected) – there is also a proposal with a note (blue sticky note) for documents with more than one shelfmark type/group, please look and let me know if it makes sense, I am proposing it for easier readability. – used real data for these designs. Note: - Since we have decided on the document type + shelfmark# to be the document title I have eliminated them as separate fields in all the pages. - I strongly prefer that we do not make the entire page title bold but make it partially bold. - The designs assume that a document has only one document type – I hope that's always true. - @thatbudakguy I have applied auto layout for all the data that comes before the description on the document detail view, and the all the search and browse results, you may notice specific changes with spacing or the placement of the fragment visual, or spacing and alignment on the search and browse results it's because of the auto layout – it's supposed to make things more practical.

1.0

Revise the document title so that it can appear on search and browse results, + the document detail view, scholarship records, external links as the page title - I have revised the document title, [here](https://www.figma.com/file/HpGBOZi9lO8B3nCAx3d4Fj/Princeton-Geniza-Project-team?node-id=851%3A6486) You can find the revised document title in following pages in the link above - document detail view - scholarship records - external links - search results - browse results There is more: - PGP ID is at the bottom of the document detail view, scholarship records, and external links. - There are design proposals for what the UI looks like when a document has 1 shelfmark, vs when it has more than one shelfmark (along with the states, default and selected) – there is also a proposal with a note (blue sticky note) for documents with more than one shelfmark type/group, please look and let me know if it makes sense, I am proposing it for easier readability. – used real data for these designs. Note: - Since we have decided on the document type + shelfmark# to be the document title I have eliminated them as separate fields in all the pages. - I strongly prefer that we do not make the entire page title bold but make it partially bold. - The designs assume that a document has only one document type – I hope that's always true. - @thatbudakguy I have applied auto layout for all the data that comes before the description on the document detail view, and the all the search and browse results, you may notice specific changes with spacing or the placement of the fragment visual, or spacing and alignment on the search and browse results it's because of the auto layout – it's supposed to make things more practical.

non_priority

revise the document title so that it can appear on search and browse results the document detail view scholarship records external links as the page title i have revised the document title you can find the revised document title in following pages in the link above document detail view scholarship records external links search results browse results there is more pgp id is at the bottom of the document detail view scholarship records and external links there are design proposals for what the ui looks like when a document has shelfmark vs when it has more than one shelfmark along with the states default and selected – there is also a proposal with a note blue sticky note for documents with more than one shelfmark type group please look and let me know if it makes sense i am proposing it for easier readability – used real data for these designs note since we have decided on the document type shelfmark to be the document title i have eliminated them as separate fields in all the pages i strongly prefer that we do not make the entire page title bold but make it partially bold the designs assume that a document has only one document type – i hope that s always true thatbudakguy i have applied auto layout for all the data that comes before the description on the document detail view and the all the search and browse results you may notice specific changes with spacing or the placement of the fragment visual or spacing and alignment on the search and browse results it s because of the auto layout – it s supposed to make things more practical

IssuesEvent

2019-05-14 12:01:45

edoddridge/aronnax

https://api.github.com/repos/edoddridge/aronnax

closed

Describe periodic boundary conditions in chapter 1 of documentation

documentation easy pick

#202 suggests that the current docs do not accurately communicate Aronnax's capabilities for periodic domains. It may be helpful to add a brief discussion to chapter 1 of the docs.

1.0

Describe periodic boundary conditions in chapter 1 of documentation - #202 suggests that the current docs do not accurately communicate Aronnax's capabilities for periodic domains. It may be helpful to add a brief discussion to chapter 1 of the docs.

non_priority

describe periodic boundary conditions in chapter of documentation suggests that the current docs do not accurately communicate aronnax s capabilities for periodic domains it may be helpful to add a brief discussion to chapter of the docs

IssuesEvent

2018-11-27 09:53:54

humera987/FXLabs-Test-Automation

https://api.github.com/repos/humera987/FXLabs-Test-Automation

reopened

new tested 27 : ApiV1IssuesProjectIdIdGetPathParamIdNullValue

new tested 27

Project : new tested 27 Job : UAT Env : UAT Region : US_WEST Result : fail Status Code : 404 Headers : {X-Content-Type-Options=[nosniff], X-XSS-Protection=[1; mode=block], Cache-Control=[no-cache, no-store, max-age=0, must-revalidate], Pragma=[no-cache], Expires=[0], X-Frame-Options=[DENY], Set-Cookie=[SESSION=YjJjMDM1YmItYWE3Yi00MzU2LWIwMDYtN2ZkYmJiNWJmYTc5; Path=/; HttpOnly], Content-Type=[application/json;charset=UTF-8], Transfer-Encoding=[chunked], Date=[Tue, 27 Nov 2018 09:50:57 GMT]} Endpoint : http://13.56.210.25/api/v1/api/v1/issues/project-id/null?status=MMOdomMV Request : Response : { "timestamp" : "2018-11-27T09:50:57.671+0000", "status" : 404, "error" : "Not Found", "message" : "No message available", "path" : "/api/v1/api/v1/issues/project-id/null" } Logs : Assertion [@StatusCode != 401] resolved-to [404 != 401] result [Passed]Assertion [@StatusCode != 500] resolved-to [404 != 500] result [Passed]Assertion [@StatusCode != 404] resolved-to [404 != 404] result [Failed]Assertion [@StatusCode != 200] resolved-to [404 != 200] result [Passed] --- FX Bot ---

1.0

new tested 27 : ApiV1IssuesProjectIdIdGetPathParamIdNullValue - Project : new tested 27 Job : UAT Env : UAT Region : US_WEST Result : fail Status Code : 404 Headers : {X-Content-Type-Options=[nosniff], X-XSS-Protection=[1; mode=block], Cache-Control=[no-cache, no-store, max-age=0, must-revalidate], Pragma=[no-cache], Expires=[0], X-Frame-Options=[DENY], Set-Cookie=[SESSION=YjJjMDM1YmItYWE3Yi00MzU2LWIwMDYtN2ZkYmJiNWJmYTc5; Path=/; HttpOnly], Content-Type=[application/json;charset=UTF-8], Transfer-Encoding=[chunked], Date=[Tue, 27 Nov 2018 09:50:57 GMT]} Endpoint : http://13.56.210.25/api/v1/api/v1/issues/project-id/null?status=MMOdomMV Request : Response : { "timestamp" : "2018-11-27T09:50:57.671+0000", "status" : 404, "error" : "Not Found", "message" : "No message available", "path" : "/api/v1/api/v1/issues/project-id/null" } Logs : Assertion [@StatusCode != 401] resolved-to [404 != 401] result [Passed]Assertion [@StatusCode != 500] resolved-to [404 != 500] result [Passed]Assertion [@StatusCode != 404] resolved-to [404 != 404] result [Failed]Assertion [@StatusCode != 200] resolved-to [404 != 200] result [Passed] --- FX Bot ---

non_priority

new tested project new tested job uat env uat region us west result fail status code headers x content type options x xss protection cache control pragma expires x frame options set cookie content type transfer encoding date endpoint request response timestamp status error not found message no message available path api api issues project id null logs assertion resolved to result assertion resolved to result assertion resolved to result assertion resolved to result fx bot

IssuesEvent

2022-02-14 13:31:23

gradle/gradle

https://api.github.com/repos/gradle/gradle

closed

improve documentation of feature variants

in:dependency-declarations a:documentation

[plantuml](https://plantuml.com/pdf) allows to generate pdf, and for it needs additional libraries. they try to keep the basic jar slim. the maven build has a profile which allows to create a jar with dependencies. i tried to convert this to gradle, using feature variants, from a producer perspective. it just behaved like one would add normal dependencies, and produces the fat jar. there is a question here: https://discuss.gradle.org/t/build-variant-command-line/42193 . which left me a little unsure - if this is a bug, or a missing sentence in the documentation of [feature, producer part](https://docs.gradle.org/current/userguide/feature_variants.html), or just my stupidity. in any case a sentence how to deal with such a use case including how to call it would be appreciated.

1.0

improve documentation of feature variants - [plantuml](https://plantuml.com/pdf) allows to generate pdf, and for it needs additional libraries. they try to keep the basic jar slim. the maven build has a profile which allows to create a jar with dependencies. i tried to convert this to gradle, using feature variants, from a producer perspective. it just behaved like one would add normal dependencies, and produces the fat jar. there is a question here: https://discuss.gradle.org/t/build-variant-command-line/42193 . which left me a little unsure - if this is a bug, or a missing sentence in the documentation of [feature, producer part](https://docs.gradle.org/current/userguide/feature_variants.html), or just my stupidity. in any case a sentence how to deal with such a use case including how to call it would be appreciated.

non_priority

improve documentation of feature variants allows to generate pdf and for it needs additional libraries they try to keep the basic jar slim the maven build has a profile which allows to create a jar with dependencies i tried to convert this to gradle using feature variants from a producer perspective it just behaved like one would add normal dependencies and produces the fat jar there is a question here which left me a little unsure if this is a bug or a missing sentence in the documentation of or just my stupidity in any case a sentence how to deal with such a use case including how to call it would be appreciated

IssuesEvent

2015-05-10 03:17:11

UCSC-MedBook/MedBook-Telescope3

https://api.github.com/repos/UCSC-MedBook/MedBook-Telescope3

reopened

MultiActor Collaboration

testing use case

A. Dr House makes a collaboration called “Foo". B. Dr House sees no posts in collaboration. C. Dr House makes a post “Bar” in the collaboration D. Thirteen can’t see Dr. House’s post. E. Thirteen asks to be included in the collaboration. F. Dr. House grants Thirteen’s membership to collaboration “Foo”. G. Thirteen can see Dr. House’s post “Bar”. H. Dr House kicks Thirteen out of collaboration “Foo”. I. Thirteen can no longer see post “Bar”.

1.0

MultiActor Collaboration - A. Dr House makes a collaboration called “Foo". B. Dr House sees no posts in collaboration. C. Dr House makes a post “Bar” in the collaboration D. Thirteen can’t see Dr. House’s post. E. Thirteen asks to be included in the collaboration. F. Dr. House grants Thirteen’s membership to collaboration “Foo”. G. Thirteen can see Dr. House’s post “Bar”. H. Dr House kicks Thirteen out of collaboration “Foo”. I. Thirteen can no longer see post “Bar”.

non_priority

multiactor collaboration a dr house makes a collaboration called “foo b dr house sees no posts in collaboration c dr house makes a post “bar” in the collaboration d thirteen can’t see dr house’s post e thirteen asks to be included in the collaboration f dr house grants thirteen’s membership to collaboration “foo” g thirteen can see dr house’s post “bar” h dr house kicks thirteen out of collaboration “foo” i thirteen can no longer see post “bar”

IssuesEvent

2023-05-09 03:18:38

Jesus180Reyes/kariken_rider_app

https://api.github.com/repos/Jesus180Reyes/kariken_rider_app

closed

TODO Add Markers from Pickup Location to Destination Location

documentation enhancement

### TODO Add Markers Location from: * Pickup Location * Destination Location

1.0

TODO Add Markers from Pickup Location to Destination Location - ### TODO Add Markers Location from: * Pickup Location * Destination Location

non_priority

todo add markers from pickup location to destination location todo add markers location from pickup location destination location

IssuesEvent

2020-12-02 08:02:09

Azure/AKS

https://api.github.com/repos/Azure/AKS

closed

Azure CLI requires Owner on subscription when creating cluster with advanced networking, while Azure Portal does not.

bug resolution/fix-released security

**What happened**: When I create cluster with Azure CLI with `--network-plugin azure` I get: ``` Could not create a role assignment for subnet. Are you an Owner on this subscription? ``` This is basically the same issue as in closed #614. Like noted in comments in that issue, it should not be required to be an Owner on subscription to create AKS cluster. 1. It is not technically mandatory to be Owner on subscription: - it is enough to be Owner on the Virtual Network to be able to add Network Contributor rights on the default subnet to the service principal - also I believe that "Application administrator" in AAD is enough to create service principals - not to mention that in reality not even that full role is needed, only some particular permission 2. When creating cluster from Azure Portal being an Owner on subscription is not required. This means that this is Azure CLI limitation 3. On the other hand this is unrealistic to require Owner on whole subscription just to be able to create AKS cluster. **What you expected to happen**: Azure CLI should be able to create AKS cluster with "advanced networking" without requiring Owner on subscription. Basically this should work when run under account with is not Owner on subscription: **How to reproduce it (as minimally and precisely as possible)**: Run this: ```powershell az aks create ` --name $aksName ` --resource-group $resourceGroupName ` --network-plugin azure ` --vnet-subnet-id $defaultSubnetId ``` **Workaround** Here is our lengthy workaround: ```powershell $servicePrincipal = az ad sp create-for-rbac --skip-assignment --name "$aksName-sp" # Hopefully below is enough to wait for AAD to propagate new service principal, but do not know... do { az ad sp show --id $servicePrincipal.appId | Out-Null } while ($LASTEXITCODE -ne 0) az role assignment create --role "Network Contributor" --assignee $servicePrincipal.appId --scope $defaultSubnetId az aks create ` --name $aksName ` --resource-group $resourceGroupName ` --network-plugin azure ` --vnet-subnet-id $defaultSubnetId ` --service-principal $servicePrincipal.appId ` --client-secret $servicePrincipal.password ```

True

Azure CLI requires Owner on subscription when creating cluster with advanced networking, while Azure Portal does not. - **What happened**: When I create cluster with Azure CLI with `--network-plugin azure` I get: ``` Could not create a role assignment for subnet. Are you an Owner on this subscription? ``` This is basically the same issue as in closed #614. Like noted in comments in that issue, it should not be required to be an Owner on subscription to create AKS cluster. 1. It is not technically mandatory to be Owner on subscription: - it is enough to be Owner on the Virtual Network to be able to add Network Contributor rights on the default subnet to the service principal - also I believe that "Application administrator" in AAD is enough to create service principals - not to mention that in reality not even that full role is needed, only some particular permission 2. When creating cluster from Azure Portal being an Owner on subscription is not required. This means that this is Azure CLI limitation 3. On the other hand this is unrealistic to require Owner on whole subscription just to be able to create AKS cluster. **What you expected to happen**: Azure CLI should be able to create AKS cluster with "advanced networking" without requiring Owner on subscription. Basically this should work when run under account with is not Owner on subscription: **How to reproduce it (as minimally and precisely as possible)**: Run this: ```powershell az aks create ` --name $aksName ` --resource-group $resourceGroupName ` --network-plugin azure ` --vnet-subnet-id $defaultSubnetId ``` **Workaround** Here is our lengthy workaround: ```powershell $servicePrincipal = az ad sp create-for-rbac --skip-assignment --name "$aksName-sp" # Hopefully below is enough to wait for AAD to propagate new service principal, but do not know... do { az ad sp show --id $servicePrincipal.appId | Out-Null } while ($LASTEXITCODE -ne 0) az role assignment create --role "Network Contributor" --assignee $servicePrincipal.appId --scope $defaultSubnetId az aks create ` --name $aksName ` --resource-group $resourceGroupName ` --network-plugin azure ` --vnet-subnet-id $defaultSubnetId ` --service-principal $servicePrincipal.appId ` --client-secret $servicePrincipal.password ```

non_priority

azure cli requires owner on subscription when creating cluster with advanced networking while azure portal does not what happened when i create cluster with azure cli with network plugin azure i get could not create a role assignment for subnet are you an owner on this subscription this is basically the same issue as in closed like noted in comments in that issue it should not be required to be an owner on subscription to create aks cluster it is not technically mandatory to be owner on subscription it is enough to be owner on the virtual network to be able to add network contributor rights on the default subnet to the service principal also i believe that application administrator in aad is enough to create service principals not to mention that in reality not even that full role is needed only some particular permission when creating cluster from azure portal being an owner on subscription is not required this means that this is azure cli limitation on the other hand this is unrealistic to require owner on whole subscription just to be able to create aks cluster what you expected to happen azure cli should be able to create aks cluster with advanced networking without requiring owner on subscription basically this should work when run under account with is not owner on subscription how to reproduce it as minimally and precisely as possible run this powershell az aks create name aksname resource group resourcegroupname network plugin azure vnet subnet id defaultsubnetid workaround here is our lengthy workaround powershell serviceprincipal az ad sp create for rbac skip assignment name aksname sp hopefully below is enough to wait for aad to propagate new service principal but do not know do az ad sp show id serviceprincipal appid out null while lastexitcode ne az role assignment create role network contributor assignee serviceprincipal appid scope defaultsubnetid az aks create name aksname resource group resourcegroupname network plugin azure vnet subnet id defaultsubnetid service principal serviceprincipal appid client secret serviceprincipal password

IssuesEvent

2020-04-22 12:33:59

ansible/ansible

https://api.github.com/repos/ansible/ansible

closed

VMWare VM Inventory Plugin Host Filters

affects_2.10 cloud feature has_pr inventory support:core test vmware

<!--- Verify first that your feature was not already discussed on GitHub --> <!--- Complete *all* sections as described, this form is processed automatically --> ##### SUMMARY <!--- Describe the new feature/improvement briefly below --> Add ability to filter down results when using the vmware_vm_inventory plugin ##### ISSUE TYPE - Feature Idea ##### COMPONENT NAME <!--- Write the short name of the module, plugin, task or feature below, use your best guess if unsure --> vmware_vm_inventory ##### ADDITIONAL INFORMATION <!--- Describe how the feature would be used, why it is needed and what it would solve --> The older vmware_inventory.py script had the ability to filter down hosts based on "host_filters". Please implement a similar feature into the vmware_vm_inventory plugin.

1.0

VMWare VM Inventory Plugin Host Filters - <!--- Verify first that your feature was not already discussed on GitHub --> <!--- Complete *all* sections as described, this form is processed automatically --> ##### SUMMARY <!--- Describe the new feature/improvement briefly below --> Add ability to filter down results when using the vmware_vm_inventory plugin ##### ISSUE TYPE - Feature Idea ##### COMPONENT NAME <!--- Write the short name of the module, plugin, task or feature below, use your best guess if unsure --> vmware_vm_inventory ##### ADDITIONAL INFORMATION <!--- Describe how the feature would be used, why it is needed and what it would solve --> The older vmware_inventory.py script had the ability to filter down hosts based on "host_filters". Please implement a similar feature into the vmware_vm_inventory plugin.

non_priority

vmware vm inventory plugin host filters summary add ability to filter down results when using the vmware vm inventory plugin issue type feature idea component name vmware vm inventory additional information the older vmware inventory py script had the ability to filter down hosts based on host filters please implement a similar feature into the vmware vm inventory plugin

IssuesEvent

2022-04-04 01:30:30

ICEI-PUC-Minas-PMV-ADS/pmv-ads-2022-1-e3-proj-mov-t1-recruta-ti

https://api.github.com/repos/ICEI-PUC-Minas-PMV-ADS/pmv-ads-2022-1-e3-proj-mov-t1-recruta-ti

closed

NBR 13596 ISO/IEC 9126-1, 2001.

documentation

H15e-ADS-CST - Projetar sistemas ou serviços de software para plataformas móveis: estruturar o projeto com base na norma técnica de qualidade de software NBR 13596 ISO/IEC 9126-1, 2001.

1.0

NBR 13596 ISO/IEC 9126-1, 2001. - H15e-ADS-CST - Projetar sistemas ou serviços de software para plataformas móveis: estruturar o projeto com base na norma técnica de qualidade de software NBR 13596 ISO/IEC 9126-1, 2001.

non_priority

nbr iso iec ads cst projetar sistemas ou serviços de software para plataformas móveis estruturar o projeto com base na norma técnica de qualidade de software nbr iso iec

IssuesEvent

2019-09-23 13:04:01

Verizon-Geeks/cncf-clients

https://api.github.com/repos/Verizon-Geeks/cncf-clients

opened

Deploy Java app on Kubernetes

documentation kubernetes

Document deployment procedures. Create ``projects/kubernetes/java`` folder. Add all your changes under this folder.

1.0

Deploy Java app on Kubernetes - Document deployment procedures. Create ``projects/kubernetes/java`` folder. Add all your changes under this folder.

non_priority

deploy java app on kubernetes document deployment procedures create projects kubernetes java folder add all your changes under this folder

IssuesEvent

2016-06-28 05:26:01

Microsoft/vsts-tasks

https://api.github.com/repos/Microsoft/vsts-tasks

closed

Ordered test support in Run Functional Tests task

Area: Test

I'm on an onpromise TFS 2015 with update 2. I have a release definition which contains several environments and one of them looks like this: - Windows Machine File Copy (deploys the assemblies from a build) - Visual Studio Test Agent Deployment - Run Functional Tests Test Selection: Test Assembly Test Assembly: **\*XYZ.orderedtest (XYZ is the proper name of the ordered test file but it does not matter at this point). Deploying to this environment results in the following error: ##[warning]DistributedTests: Test run is aborted. Logging details of the run logs. ##[warning]DistributedTests: New test run created. ##[warning]Test Run queued for Project Collection Build Service (TEAM FOUNDATION). ##[warning]DistributedTests: Test discovery started. ##[warning]DistributedTests: Test Run Discovery Aborted . Test run id : 278798 ##[warning]DistributedTests: UnExpected error occured during test execution. Try again. ##[warning]DistributedTests: **Error : No tests were discovered from the specified test sources** ##[warning]DistributedTests: Test run aborted. Test run id: 278798 I'm wondering whether the ordered test is supported in this task or i have setup something wrong. Any thoughts?

1.0

Ordered test support in Run Functional Tests task - I'm on an onpromise TFS 2015 with update 2. I have a release definition which contains several environments and one of them looks like this: - Windows Machine File Copy (deploys the assemblies from a build) - Visual Studio Test Agent Deployment - Run Functional Tests Test Selection: Test Assembly Test Assembly: **\*XYZ.orderedtest (XYZ is the proper name of the ordered test file but it does not matter at this point). Deploying to this environment results in the following error: ##[warning]DistributedTests: Test run is aborted. Logging details of the run logs. ##[warning]DistributedTests: New test run created. ##[warning]Test Run queued for Project Collection Build Service (TEAM FOUNDATION). ##[warning]DistributedTests: Test discovery started. ##[warning]DistributedTests: Test Run Discovery Aborted . Test run id : 278798 ##[warning]DistributedTests: UnExpected error occured during test execution. Try again. ##[warning]DistributedTests: **Error : No tests were discovered from the specified test sources** ##[warning]DistributedTests: Test run aborted. Test run id: 278798 I'm wondering whether the ordered test is supported in this task or i have setup something wrong. Any thoughts?

non_priority

ordered test support in run functional tests task i m on an onpromise tfs with update i have a release definition which contains several environments and one of them looks like this windows machine file copy deploys the assemblies from a build visual studio test agent deployment run functional tests test selection test assembly test assembly xyz orderedtest xyz is the proper name of the ordered test file but it does not matter at this point deploying to this environment results in the following error distributedtests test run is aborted logging details of the run logs distributedtests new test run created test run queued for project collection build service team foundation distributedtests test discovery started distributedtests test run discovery aborted test run id distributedtests unexpected error occured during test execution try again distributedtests error no tests were discovered from the specified test sources distributedtests test run aborted test run id i m wondering whether the ordered test is supported in this task or i have setup something wrong any thoughts