Unnamed: 0
int64
0
832k
id
float64
2.49B
32.1B
type
stringclasses
1 value
created_at
stringlengths
19
19
repo
stringlengths
5
112
repo_url
stringlengths
34
141
action
stringclasses
3 values
title
stringlengths
1
844
labels
stringlengths
4
721
body
stringlengths
1
261k
index
stringclasses
12 values
text_combine
stringlengths
96
261k
label
stringclasses
2 values
text
stringlengths
96
248k
binary_label
int64
0
1
337,354
30,247,556,288
IssuesEvent
2023-07-06 17:42:43
unifyai/ivy
https://api.github.com/repos/unifyai/ivy
reopened
Fix array_contents.test_numpy_isclose
NumPy Frontend Sub Task Failing Test
| | | |---|---| |torch|<a href="https://github.com/unifyai/ivy/actions/runs/5478319447"><img src=https://img.shields.io/badge/-success-success></a> |jax|<a href="https://github.com/unifyai/ivy/actions/runs/5446240655/jobs/9906681891"><img src=https://img.shields.io/badge/-success-success></a> |numpy|<a href="https://github.com/unifyai/ivy/actions/runs/5446240655/jobs/9906681891"><img src=https://img.shields.io/badge/-success-success></a> |tensorflow|<a href="https://github.com/unifyai/ivy/actions/runs/5478319447"><img src=https://img.shields.io/badge/-failure-red></a> |paddle|<a href="https://github.com/unifyai/ivy/actions/runs/5478319447"><img src=https://img.shields.io/badge/-success-success></a>
1.0
Fix array_contents.test_numpy_isclose - | | | |---|---| |torch|<a href="https://github.com/unifyai/ivy/actions/runs/5478319447"><img src=https://img.shields.io/badge/-success-success></a> |jax|<a href="https://github.com/unifyai/ivy/actions/runs/5446240655/jobs/9906681891"><img src=https://img.shields.io/badge/-success-success></a> |numpy|<a href="https://github.com/unifyai/ivy/actions/runs/5446240655/jobs/9906681891"><img src=https://img.shields.io/badge/-success-success></a> |tensorflow|<a href="https://github.com/unifyai/ivy/actions/runs/5478319447"><img src=https://img.shields.io/badge/-failure-red></a> |paddle|<a href="https://github.com/unifyai/ivy/actions/runs/5478319447"><img src=https://img.shields.io/badge/-success-success></a>
non_priority
fix array contents test numpy isclose torch a href src jax a href src numpy a href src tensorflow a href src paddle a href src
0
346
2,590,524,350
IssuesEvent
2015-02-18 19:25:30
irods/irods
https://api.github.com/repos/irods/irods
opened
use of TCP_NODELAY in socket setup
for-discussion performance
I'm curious about this as I'm looking at this in Jargon https://github.com/irods/irods/blob/master/iRODS/lib/core/src/sockComm.cpp#L744-L745 And wondering what the impact is of doing this? This appears to have the potential to decrease latency but decrease bandwidth? It might be need to play with this when we have some benchmarks. e.g. Oracle & tcp.nodelay parameter Oracle Tips by Burleson Consulting The tcp.nodelay parameter By default, Oracle*Net waits until the buffer is full before transmitting data; therefore, requests are not always sent immediately to their destinations. This is most commonly found when large amounts of data are streamed from one location to another, and Oracle*Net does not transmit the packet until the buffer is full. Adding a protocol.ora file and specifying a tcp.nodelay to stop buffer flushing delays can sometimes remedy this problem. The parameter can be used both on the client and server. The protocol.ora statement is: tcp.nodelay = YES When this parameter is specified, TCP buffering is skipped so that every request is sent immediately. Slowdowns in the network may be caused by an increase in network traffic due to smaller and more frequent packet transmission. Oracle-l notes this on tcp.nodelay and it's relationship to the SDU and TDU parameters: "Setting tcp.nodelay disables the Nagle algorithm in the tcp stack that tries to efficiently balance the data load of a packet with the delay in dispatching it. Effectively, you're saying "to xxx with optimizing the data payload ... send those babies now!". The complete antithesis of what the SDU/TDU settings are trying to do for you. You'll end up with a larger number of smaller packets on your WAN, and if it's latency that's your problem, this will make matters worse, not better." worth testing at some point!
True
use of TCP_NODELAY in socket setup - I'm curious about this as I'm looking at this in Jargon https://github.com/irods/irods/blob/master/iRODS/lib/core/src/sockComm.cpp#L744-L745 And wondering what the impact is of doing this? This appears to have the potential to decrease latency but decrease bandwidth? It might be need to play with this when we have some benchmarks. e.g. Oracle & tcp.nodelay parameter Oracle Tips by Burleson Consulting The tcp.nodelay parameter By default, Oracle*Net waits until the buffer is full before transmitting data; therefore, requests are not always sent immediately to their destinations. This is most commonly found when large amounts of data are streamed from one location to another, and Oracle*Net does not transmit the packet until the buffer is full. Adding a protocol.ora file and specifying a tcp.nodelay to stop buffer flushing delays can sometimes remedy this problem. The parameter can be used both on the client and server. The protocol.ora statement is: tcp.nodelay = YES When this parameter is specified, TCP buffering is skipped so that every request is sent immediately. Slowdowns in the network may be caused by an increase in network traffic due to smaller and more frequent packet transmission. Oracle-l notes this on tcp.nodelay and it's relationship to the SDU and TDU parameters: "Setting tcp.nodelay disables the Nagle algorithm in the tcp stack that tries to efficiently balance the data load of a packet with the delay in dispatching it. Effectively, you're saying "to xxx with optimizing the data payload ... send those babies now!". The complete antithesis of what the SDU/TDU settings are trying to do for you. You'll end up with a larger number of smaller packets on your WAN, and if it's latency that's your problem, this will make matters worse, not better." worth testing at some point!
non_priority
use of tcp nodelay in socket setup i m curious about this as i m looking at this in jargon and wondering what the impact is of doing this this appears to have the potential to decrease latency but decrease bandwidth it might be need to play with this when we have some benchmarks e g oracle tcp nodelay parameter oracle tips by burleson consulting the tcp nodelay parameter by default oracle net waits until the buffer is full before transmitting data therefore requests are not always sent immediately to their destinations this is most commonly found when large amounts of data are streamed from one location to another and oracle net does not transmit the packet until the buffer is full adding a protocol ora file and specifying a tcp nodelay to stop buffer flushing delays can sometimes remedy this problem the parameter can be used both on the client and server the protocol ora statement is tcp nodelay yes when this parameter is specified tcp buffering is skipped so that every request is sent immediately slowdowns in the network may be caused by an increase in network traffic due to smaller and more frequent packet transmission oracle l notes this on tcp nodelay and it s relationship to the sdu and tdu parameters setting tcp nodelay disables the nagle algorithm in the tcp stack that tries to efficiently balance the data load of a packet with the delay in dispatching it effectively you re saying to xxx with optimizing the data payload send those babies now the complete antithesis of what the sdu tdu settings are trying to do for you you ll end up with a larger number of smaller packets on your wan and if it s latency that s your problem this will make matters worse not better worth testing at some point
0
13,408
3,710,402,378
IssuesEvent
2016-03-02 03:59:06
KSP-KOS/KOS
https://api.github.com/repos/KSP-KOS/KOS
closed
Prepare and publish 0.19 credits
documentation
@Dunbaratu suggested that we should prepare a list of people who contributed to 0.19. We need to prepare the list and decide where to put it. I've already asked all 9 people who have contributed commits to git since Nov 27th whether they want to be mentioned in credits.
1.0
Prepare and publish 0.19 credits - @Dunbaratu suggested that we should prepare a list of people who contributed to 0.19. We need to prepare the list and decide where to put it. I've already asked all 9 people who have contributed commits to git since Nov 27th whether they want to be mentioned in credits.
non_priority
prepare and publish credits dunbaratu suggested that we should prepare a list of people who contributed to we need to prepare the list and decide where to put it i ve already asked all people who have contributed commits to git since nov whether they want to be mentioned in credits
0
46,908
13,056,000,594
IssuesEvent
2020-07-30 03:21:13
icecube-trac/tix2
https://api.github.com/repos/icecube-trac/tix2
opened
[spline-reco] Bug leads to segmentation violation in case of an 'anomalously large charge' (Trac #2119)
Incomplete Migration Migrated from Trac analysis defect
Migrated from https://code.icecube.wisc.edu/ticket/2119 ```json { "status": "closed", "changetime": "2019-02-13T14:14:55", "description": "In `I3SplineRecoLikelihood::KS0Limit(int npulses, int level)` an array is accessed with `ks_test[npulses - 1]` but does not check if `npulses < 1`.\n\nI saw a couple of events that call this function with `npulses = 0` but apparently it didn't break the execution. However, I found a case with\n\n{{{\nI3HitOm.h:111 WARNING: got anomalously large charge=1.64923e+10 PE in OM at (x,y,z)=(429.8,351.0,-344.9)\n}}}\n\nthat leads to an overflow of `totalcharge` in `I3SplineRecoLikelihood::GetApprovedCharge`. Finally, `npulses` is small enough (e.g. `npulses = -2147483648`) to cause a segmentation violation.\n\nhttp://code.icecube.wisc.edu/projects/icecube/browser/IceCube/projects/spline-reco/trunk/private/spline-reco/I3SplineRecoLikelihood.cxx?rev=157082#L867\n\nThis bug blocks processing of a pass2 file.", "reporter": "joertlin", "cc": "", "resolution": "fixed", "_ts": "1550067295757382", "component": "analysis", "summary": "[spline-reco] Bug leads to segmentation violation in case of an 'anomalously large charge'", "priority": "critical", "keywords": "", "time": "2017-12-01T21:22:27", "milestone": "", "owner": "kjmeagher", "type": "defect" } ```
1.0
[spline-reco] Bug leads to segmentation violation in case of an 'anomalously large charge' (Trac #2119) - Migrated from https://code.icecube.wisc.edu/ticket/2119 ```json { "status": "closed", "changetime": "2019-02-13T14:14:55", "description": "In `I3SplineRecoLikelihood::KS0Limit(int npulses, int level)` an array is accessed with `ks_test[npulses - 1]` but does not check if `npulses < 1`.\n\nI saw a couple of events that call this function with `npulses = 0` but apparently it didn't break the execution. However, I found a case with\n\n{{{\nI3HitOm.h:111 WARNING: got anomalously large charge=1.64923e+10 PE in OM at (x,y,z)=(429.8,351.0,-344.9)\n}}}\n\nthat leads to an overflow of `totalcharge` in `I3SplineRecoLikelihood::GetApprovedCharge`. Finally, `npulses` is small enough (e.g. `npulses = -2147483648`) to cause a segmentation violation.\n\nhttp://code.icecube.wisc.edu/projects/icecube/browser/IceCube/projects/spline-reco/trunk/private/spline-reco/I3SplineRecoLikelihood.cxx?rev=157082#L867\n\nThis bug blocks processing of a pass2 file.", "reporter": "joertlin", "cc": "", "resolution": "fixed", "_ts": "1550067295757382", "component": "analysis", "summary": "[spline-reco] Bug leads to segmentation violation in case of an 'anomalously large charge'", "priority": "critical", "keywords": "", "time": "2017-12-01T21:22:27", "milestone": "", "owner": "kjmeagher", "type": "defect" } ```
non_priority
bug leads to segmentation violation in case of an anomalously large charge trac migrated from json status closed changetime description in int npulses int level an array is accessed with ks test but does not check if npulses n ni saw a couple of events that call this function with npulses but apparently it didn t break the execution however i found a case with n n h warning got anomalously large charge pe in om at x y z n n nthat leads to an overflow of totalcharge in getapprovedcharge finally npulses is small enough e g npulses to cause a segmentation violation n n bug blocks processing of a file reporter joertlin cc resolution fixed ts component analysis summary bug leads to segmentation violation in case of an anomalously large charge priority critical keywords time milestone owner kjmeagher type defect
0
129,937
17,936,527,771
IssuesEvent
2021-09-10 16:00:41
microsoft/vscode
https://api.github.com/repos/microsoft/vscode
closed
Inlay hints does not take effect when the parameter variable passed in is the same as the parameter name
*as-designed
<!-- ⚠️⚠️ Do Not Delete This! bug_report_template ⚠️⚠️ --> <!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ --> <!-- 🕮 Read our guide about submitting issues: https://github.com/microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions --> <!-- 🔎 Search existing issues to avoid creating duplicates. --> <!-- 🧪 Test using the latest Insiders build to see if your issue has already been fixed: https://code.visualstudio.com/insiders/ --> <!-- 💡 Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. --> <!-- 🔧 Launch with `code --disable-extensions` to check. --> Does this issue occur when all extensions are disabled?: Yes <!-- 🪓 If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. --> <!-- 📣 Issues caused by an extension need to be reported directly to the extension publisher. The 'Help > Report Issue' dialog can assist with this. --> - VS Code Version: 1.60.0 - OS Version: Darwin arm64 20.6.0 1. In setting.json, `"typescript.inlayHints.parameterNames.enabled": "all"` 2. Pass in the function a variable name that is the same as the parameter name The effect is shown in the following figure. ![inlay-hints-issues](https://user-images.githubusercontent.com/63690944/132800196-7b92480b-04ad-4d24-90dd-6608cbb7208c.gif) ![image](https://user-images.githubusercontent.com/63690944/132800638-8f5f90ae-8469-44e8-b7ac-092d438c88e9.png)
1.0
Inlay hints does not take effect when the parameter variable passed in is the same as the parameter name - <!-- ⚠️⚠️ Do Not Delete This! bug_report_template ⚠️⚠️ --> <!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ --> <!-- 🕮 Read our guide about submitting issues: https://github.com/microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions --> <!-- 🔎 Search existing issues to avoid creating duplicates. --> <!-- 🧪 Test using the latest Insiders build to see if your issue has already been fixed: https://code.visualstudio.com/insiders/ --> <!-- 💡 Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. --> <!-- 🔧 Launch with `code --disable-extensions` to check. --> Does this issue occur when all extensions are disabled?: Yes <!-- 🪓 If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. --> <!-- 📣 Issues caused by an extension need to be reported directly to the extension publisher. The 'Help > Report Issue' dialog can assist with this. --> - VS Code Version: 1.60.0 - OS Version: Darwin arm64 20.6.0 1. In setting.json, `"typescript.inlayHints.parameterNames.enabled": "all"` 2. Pass in the function a variable name that is the same as the parameter name The effect is shown in the following figure. ![inlay-hints-issues](https://user-images.githubusercontent.com/63690944/132800196-7b92480b-04ad-4d24-90dd-6608cbb7208c.gif) ![image](https://user-images.githubusercontent.com/63690944/132800638-8f5f90ae-8469-44e8-b7ac-092d438c88e9.png)
non_priority
inlay hints does not take effect when the parameter variable passed in is the same as the parameter name does this issue occur when all extensions are disabled yes report issue dialog can assist with this vs code version os version darwin in setting json typescript inlayhints parameternames enabled all pass in the function a variable name that is the same as the parameter name the effect is shown in the following figure
0
250,991
27,131,423,167
IssuesEvent
2023-02-16 10:03:27
uriel-naor/UrielTest
https://api.github.com/repos/uriel-naor/UrielTest
reopened
express-3.0.0.tgz: 10 vulnerabilities (highest severity is: 7.5)
security vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>express-3.0.0.tgz</b></p></summary> <p>Sinatra inspired web development framework</p> <p>Library home page: <a href="https://registry.npmjs.org/express/-/express-3.0.0.tgz">https://registry.npmjs.org/express/-/express-3.0.0.tgz</a></p> <p>Path to dependency file: /package.json</p> <p>Path to vulnerable library: /node_modules/express/package.json</p> <p> <p>Found in HEAD commit: <a href="https://github.com/uriel-naor/UrielTest/commit/894f510f12658f81a9e1c64222c0c83e96f37e91">894f510f12658f81a9e1c64222c0c83e96f37e91</a></p></details> ## Vulnerabilities | CVE | Severity | <img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS | Dependency | Type | Fixed in (express version) | Fix PR available | | ------------- | ------------- | ----- | ----- | ----- | ------------- | --- | | [CVE-2017-16138](https://www.mend.io/vulnerability-database/CVE-2017-16138) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | mime-1.2.6.tgz | Transitive | N/A* | &#10060; | | [CVE-2017-16119](https://www.mend.io/vulnerability-database/CVE-2017-16119) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | fresh-0.1.0.tgz | Transitive | N/A* | &#10060; | | [CVE-2014-6394](https://www.mend.io/vulnerability-database/CVE-2014-6394) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.3 | detected in multiple dependencies | Transitive | 3.21.0 | &#9989; | | [CVE-2013-7370](https://www.mend.io/vulnerability-database/CVE-2013-7370) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 6.1 | connect-2.6.0.tgz | Transitive | 3.21.0 | &#9989; | | [CVE-2014-6393](https://www.mend.io/vulnerability-database/CVE-2014-6393) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 6.1 | express-3.0.0.tgz | Direct | 3.21.0 | &#9989; | | [WS-2013-0004](https://github.com/senchalabs/connect/commit/126187c4e12162e231b87350740045e5bb06e93a) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 6.1 | connect-2.6.0.tgz | Transitive | 3.21.0 | &#9989; | | [CVE-2013-7371](https://www.mend.io/vulnerability-database/CVE-2013-7371) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 6.1 | connect-2.6.0.tgz | Transitive | 3.21.0 | &#9989; | | [CVE-2018-3717](https://www.mend.io/vulnerability-database/CVE-2018-3717) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 5.4 | connect-2.6.0.tgz | Transitive | 3.21.0 | &#9989; | | [CVE-2015-8859](https://www.mend.io/vulnerability-database/CVE-2015-8859) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 5.3 | detected in multiple dependencies | Transitive | 3.21.0 | &#9989; | | [CVE-2014-7191](https://www.mend.io/vulnerability-database/CVE-2014-7191) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 5.3 | qs-0.5.1.tgz | Transitive | 3.21.0 | &#9989; | <p>*For some transitive vulnerabilities, there is no version of direct dependency with a fix. Check the section "Details" below to see if there is a version of transitive dependency where vulnerability is fixed.</p> ## Details <details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2017-16138</summary> ### Vulnerable Library - <b>mime-1.2.6.tgz</b></p> <p>A comprehensive library for mime-type mapping</p> <p>Library home page: <a href="https://registry.npmjs.org/mime/-/mime-1.2.6.tgz">https://registry.npmjs.org/mime/-/mime-1.2.6.tgz</a></p> <p>Path to dependency file: /package.json</p> <p>Path to vulnerable library: /node_modules/mime/package.json</p> <p> Dependency Hierarchy: - express-3.0.0.tgz (Root Library) - send-0.1.0.tgz - :x: **mime-1.2.6.tgz** (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/uriel-naor/UrielTest/commit/894f510f12658f81a9e1c64222c0c83e96f37e91">894f510f12658f81a9e1c64222c0c83e96f37e91</a></p> <p>Found in base branch: <b>main</b></p> </p> <p></p> ### Vulnerability Details <p> The mime module < 1.4.1, 2.0.1, 2.0.2 is vulnerable to regular expression denial of service when a mime lookup is performed on untrusted user input. <p>Publish Date: 2018-06-07 <p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2017-16138>CVE-2017-16138</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>7.5</b>) <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: None - Integrity Impact: None - Availability Impact: High </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> <p></p> ### Suggested Fix <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-16138">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-16138</a></p> <p>Release Date: 2018-06-07</p> <p>Fix Resolution: 1.4.1,2.0.3</p> </p> <p></p> </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2017-16119</summary> ### Vulnerable Library - <b>fresh-0.1.0.tgz</b></p> <p>HTTP response freshness testing</p> <p>Library home page: <a href="https://registry.npmjs.org/fresh/-/fresh-0.1.0.tgz">https://registry.npmjs.org/fresh/-/fresh-0.1.0.tgz</a></p> <p>Path to dependency file: /package.json</p> <p>Path to vulnerable library: /node_modules/fresh/package.json</p> <p> Dependency Hierarchy: - express-3.0.0.tgz (Root Library) - :x: **fresh-0.1.0.tgz** (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/uriel-naor/UrielTest/commit/894f510f12658f81a9e1c64222c0c83e96f37e91">894f510f12658f81a9e1c64222c0c83e96f37e91</a></p> <p>Found in base branch: <b>main</b></p> </p> <p></p> ### Vulnerability Details <p> Fresh is a module used by the Express.js framework for HTTP response freshness testing. It is vulnerable to a regular expression denial of service when it is passed specially crafted input to parse. This causes the event loop to be blocked causing a denial of service condition. <p>Publish Date: 2018-06-07 <p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2017-16119>CVE-2017-16119</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://www.npmjs.com/advisories/526">https://www.npmjs.com/advisories/526</a></p> <p>Release Date: 2018-06-07</p> <p>Fix Resolution: fresh - 0.5.2</p> </p> <p></p> </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2014-6394</summary> ### Vulnerable Libraries - <b>send-0.1.0.tgz</b>, <b>send-0.0.4.tgz</b></p> <p> ### <b>send-0.1.0.tgz</b></p> <p>Better streaming static file server with Range and conditional-GET support</p> <p>Library home page: <a href="https://registry.npmjs.org/send/-/send-0.1.0.tgz">https://registry.npmjs.org/send/-/send-0.1.0.tgz</a></p> <p>Path to dependency file: /package.json</p> <p>Path to vulnerable library: /node_modules/send/package.json</p> <p> Dependency Hierarchy: - express-3.0.0.tgz (Root Library) - :x: **send-0.1.0.tgz** (Vulnerable Library) ### <b>send-0.0.4.tgz</b></p> <p>Better streaming static file server with Range and conditional-GET support</p> <p>Library home page: <a href="https://registry.npmjs.org/send/-/send-0.0.4.tgz">https://registry.npmjs.org/send/-/send-0.0.4.tgz</a></p> <p>Path to dependency file: /package.json</p> <p>Path to vulnerable library: /node_modules/connect/node_modules/send/package.json</p> <p> Dependency Hierarchy: - express-3.0.0.tgz (Root Library) - connect-2.6.0.tgz - :x: **send-0.0.4.tgz** (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/uriel-naor/UrielTest/commit/894f510f12658f81a9e1c64222c0c83e96f37e91">894f510f12658f81a9e1c64222c0c83e96f37e91</a></p> <p>Found in base branch: <b>main</b></p> </p> <p></p> ### Vulnerability Details <p> visionmedia send before 0.8.4 for Node.js uses a partial comparison for verifying whether a directory is within the document root, which allows remote attackers to access restricted directories, as demonstrated using "public-restricted" under a "public" directory. <p>Publish Date: 2014-10-08 <p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2014-6394>CVE-2014-6394</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>7.3</b>) <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: Low - Integrity Impact: Low - Availability Impact: Low </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> <p></p> ### Suggested Fix <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://nvd.nist.gov/vuln/detail/CVE-2014-6394">https://nvd.nist.gov/vuln/detail/CVE-2014-6394</a></p> <p>Release Date: 2014-10-08</p> <p>Fix Resolution (send): 0.8.4</p> <p>Direct dependency fix Resolution (express): 3.21.0</p><p>Fix Resolution (send): 0.8.4</p> <p>Direct dependency fix Resolution (express): 3.21.0</p> </p> <p></p> :rescue_worker_helmet: Automatic Remediation is available for this issue </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2013-7370</summary> ### Vulnerable Library - <b>connect-2.6.0.tgz</b></p> <p>High performance middleware framework</p> <p>Library home page: <a href="https://registry.npmjs.org/connect/-/connect-2.6.0.tgz">https://registry.npmjs.org/connect/-/connect-2.6.0.tgz</a></p> <p>Path to dependency file: /package.json</p> <p>Path to vulnerable library: /node_modules/connect/package.json</p> <p> Dependency Hierarchy: - express-3.0.0.tgz (Root Library) - :x: **connect-2.6.0.tgz** (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/uriel-naor/UrielTest/commit/894f510f12658f81a9e1c64222c0c83e96f37e91">894f510f12658f81a9e1c64222c0c83e96f37e91</a></p> <p>Found in base branch: <b>main</b></p> </p> <p></p> ### Vulnerability Details <p> node-connect before 2.8.1 has XSS in the Sencha Labs Connect middleware <p>Publish Date: 2019-12-11 <p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2013-7370>CVE-2013-7370</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="http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2013-7370">http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2013-7370</a></p> <p>Release Date: 2019-12-11</p> <p>Fix Resolution (connect): 2.8.2</p> <p>Direct dependency fix Resolution (express): 3.21.0</p> </p> <p></p> :rescue_worker_helmet: Automatic Remediation is available for this issue </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2014-6393</summary> ### Vulnerable Library - <b>express-3.0.0.tgz</b></p> <p>Sinatra inspired web development framework</p> <p>Library home page: <a href="https://registry.npmjs.org/express/-/express-3.0.0.tgz">https://registry.npmjs.org/express/-/express-3.0.0.tgz</a></p> <p>Path to dependency file: /package.json</p> <p>Path to vulnerable library: /node_modules/express/package.json</p> <p> Dependency Hierarchy: - :x: **express-3.0.0.tgz** (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/uriel-naor/UrielTest/commit/894f510f12658f81a9e1c64222c0c83e96f37e91">894f510f12658f81a9e1c64222c0c83e96f37e91</a></p> <p>Found in base branch: <b>main</b></p> </p> <p></p> ### Vulnerability Details <p> The Express web framework before 3.11 and 4.x before 4.5 for Node.js does not provide a charset field in HTTP Content-Type headers in 400 level responses, which might allow remote attackers to conduct cross-site scripting (XSS) attacks via characters in a non-standard encoding. <p>Publish Date: 2017-08-09 <p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2014-6393>CVE-2014-6393</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>6.1</b>) <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: Required - Scope: Changed - Impact Metrics: - Confidentiality Impact: Low - Integrity Impact: Low - Availability Impact: None </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> <p></p> ### Suggested Fix <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-6393">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-6393</a></p> <p>Release Date: 2017-08-09</p> <p>Fix Resolution (express): express - 3.11.0, 4.5.0</p> <p>Direct dependency fix Resolution (express): 3.21.0</p> </p> <p></p> :rescue_worker_helmet: Automatic Remediation is available for this issue </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> WS-2013-0004</summary> ### Vulnerable Library - <b>connect-2.6.0.tgz</b></p> <p>High performance middleware framework</p> <p>Library home page: <a href="https://registry.npmjs.org/connect/-/connect-2.6.0.tgz">https://registry.npmjs.org/connect/-/connect-2.6.0.tgz</a></p> <p>Path to dependency file: /package.json</p> <p>Path to vulnerable library: /node_modules/connect/package.json</p> <p> Dependency Hierarchy: - express-3.0.0.tgz (Root Library) - :x: **connect-2.6.0.tgz** (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/uriel-naor/UrielTest/commit/894f510f12658f81a9e1c64222c0c83e96f37e91">894f510f12658f81a9e1c64222c0c83e96f37e91</a></p> <p>Found in base branch: <b>main</b></p> </p> <p></p> ### Vulnerability Details <p> The "methodOverride" let the http post to override the method of the request with the value of the post key or with the header, which allows XSS attack. <p>Publish Date: 2013-06-27 <p>URL: <a href=https://github.com/senchalabs/connect/commit/126187c4e12162e231b87350740045e5bb06e93a>WS-2013-0004</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>Release Date: 2013-06-27</p> <p>Fix Resolution (connect): 2.8.2</p> <p>Direct dependency fix Resolution (express): 3.21.0</p> </p> <p></p> :rescue_worker_helmet: Automatic Remediation is available for this issue </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2013-7371</summary> ### Vulnerable Library - <b>connect-2.6.0.tgz</b></p> <p>High performance middleware framework</p> <p>Library home page: <a href="https://registry.npmjs.org/connect/-/connect-2.6.0.tgz">https://registry.npmjs.org/connect/-/connect-2.6.0.tgz</a></p> <p>Path to dependency file: /package.json</p> <p>Path to vulnerable library: /node_modules/connect/package.json</p> <p> Dependency Hierarchy: - express-3.0.0.tgz (Root Library) - :x: **connect-2.6.0.tgz** (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/uriel-naor/UrielTest/commit/894f510f12658f81a9e1c64222c0c83e96f37e91">894f510f12658f81a9e1c64222c0c83e96f37e91</a></p> <p>Found in base branch: <b>main</b></p> </p> <p></p> ### Vulnerability Details <p> node-connects before 2.8.2 has cross site scripting in Sencha Labs Connect middleware (vulnerability due to incomplete fix for CVE-2013-7370) <p>Publish Date: 2019-12-11 <p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2013-7371>CVE-2013-7371</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="http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2013-7371">http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2013-7371</a></p> <p>Release Date: 2019-12-11</p> <p>Fix Resolution (connect): 2.8.2</p> <p>Direct dependency fix Resolution (express): 3.21.0</p> </p> <p></p> :rescue_worker_helmet: Automatic Remediation is available for this issue </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2018-3717</summary> ### Vulnerable Library - <b>connect-2.6.0.tgz</b></p> <p>High performance middleware framework</p> <p>Library home page: <a href="https://registry.npmjs.org/connect/-/connect-2.6.0.tgz">https://registry.npmjs.org/connect/-/connect-2.6.0.tgz</a></p> <p>Path to dependency file: /package.json</p> <p>Path to vulnerable library: /node_modules/connect/package.json</p> <p> Dependency Hierarchy: - express-3.0.0.tgz (Root Library) - :x: **connect-2.6.0.tgz** (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/uriel-naor/UrielTest/commit/894f510f12658f81a9e1c64222c0c83e96f37e91">894f510f12658f81a9e1c64222c0c83e96f37e91</a></p> <p>Found in base branch: <b>main</b></p> </p> <p></p> ### Vulnerability Details <p> connect node module before 2.14.0 suffers from a Cross-Site Scripting (XSS) vulnerability due to a lack of validation of file in directory.js middleware. <p>Publish Date: 2018-06-07 <p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2018-3717>CVE-2018-3717</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>5.4</b>) <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: Low - 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://nvd.nist.gov/vuln/detail/CVE-2018-3717">https://nvd.nist.gov/vuln/detail/CVE-2018-3717</a></p> <p>Release Date: 2018-06-07</p> <p>Fix Resolution (connect): 2.14.0</p> <p>Direct dependency fix Resolution (express): 3.21.0</p> </p> <p></p> :rescue_worker_helmet: Automatic Remediation is available for this issue </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2015-8859</summary> ### Vulnerable Libraries - <b>send-0.1.0.tgz</b>, <b>send-0.0.4.tgz</b></p> <p> ### <b>send-0.1.0.tgz</b></p> <p>Better streaming static file server with Range and conditional-GET support</p> <p>Library home page: <a href="https://registry.npmjs.org/send/-/send-0.1.0.tgz">https://registry.npmjs.org/send/-/send-0.1.0.tgz</a></p> <p>Path to dependency file: /package.json</p> <p>Path to vulnerable library: /node_modules/send/package.json</p> <p> Dependency Hierarchy: - express-3.0.0.tgz (Root Library) - :x: **send-0.1.0.tgz** (Vulnerable Library) ### <b>send-0.0.4.tgz</b></p> <p>Better streaming static file server with Range and conditional-GET support</p> <p>Library home page: <a href="https://registry.npmjs.org/send/-/send-0.0.4.tgz">https://registry.npmjs.org/send/-/send-0.0.4.tgz</a></p> <p>Path to dependency file: /package.json</p> <p>Path to vulnerable library: /node_modules/connect/node_modules/send/package.json</p> <p> Dependency Hierarchy: - express-3.0.0.tgz (Root Library) - connect-2.6.0.tgz - :x: **send-0.0.4.tgz** (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/uriel-naor/UrielTest/commit/894f510f12658f81a9e1c64222c0c83e96f37e91">894f510f12658f81a9e1c64222c0c83e96f37e91</a></p> <p>Found in base branch: <b>main</b></p> </p> <p></p> ### Vulnerability Details <p> The send package before 0.11.1 for Node.js allows attackers to obtain the root path via unspecified vectors. <p>Publish Date: 2017-01-23 <p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2015-8859>CVE-2015-8859</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>5.3</b>) <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: Low - Integrity Impact: None - Availability Impact: None </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> <p></p> ### Suggested Fix <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://nvd.nist.gov/vuln/detail/CVE-2015-8859">https://nvd.nist.gov/vuln/detail/CVE-2015-8859</a></p> <p>Release Date: 2017-01-23</p> <p>Fix Resolution (send): 0.11.1</p> <p>Direct dependency fix Resolution (express): 3.21.0</p><p>Fix Resolution (send): 0.11.1</p> <p>Direct dependency fix Resolution (express): 3.21.0</p> </p> <p></p> :rescue_worker_helmet: Automatic Remediation is available for this issue </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2014-7191</summary> ### Vulnerable Library - <b>qs-0.5.1.tgz</b></p> <p>querystring parser</p> <p>Library home page: <a href="https://registry.npmjs.org/qs/-/qs-0.5.1.tgz">https://registry.npmjs.org/qs/-/qs-0.5.1.tgz</a></p> <p>Path to dependency file: /package.json</p> <p>Path to vulnerable library: /node_modules/qs/package.json</p> <p> Dependency Hierarchy: - express-3.0.0.tgz (Root Library) - connect-2.6.0.tgz - :x: **qs-0.5.1.tgz** (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/uriel-naor/UrielTest/commit/894f510f12658f81a9e1c64222c0c83e96f37e91">894f510f12658f81a9e1c64222c0c83e96f37e91</a></p> <p>Found in base branch: <b>main</b></p> </p> <p></p> ### Vulnerability Details <p> The qs module before 1.0.0 in Node.js does not call the compact function for array data, which allows remote attackers to cause a denial of service (memory consumption) by using a large index value to create a sparse array. <p>Publish Date: 2014-10-19 <p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2014-7191>CVE-2014-7191</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>5.3</b>) <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: None - Integrity Impact: 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://nvd.nist.gov/vuln/detail/CVE-2014-7191">https://nvd.nist.gov/vuln/detail/CVE-2014-7191</a></p> <p>Release Date: 2014-10-19</p> <p>Fix Resolution (qs): 1.0.0</p> <p>Direct dependency fix Resolution (express): 3.21.0</p> </p> <p></p> :rescue_worker_helmet: Automatic Remediation is available for this issue </details> *** <p>:rescue_worker_helmet: Automatic Remediation is available for this issue.</p>
True
express-3.0.0.tgz: 10 vulnerabilities (highest severity is: 7.5) - <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>express-3.0.0.tgz</b></p></summary> <p>Sinatra inspired web development framework</p> <p>Library home page: <a href="https://registry.npmjs.org/express/-/express-3.0.0.tgz">https://registry.npmjs.org/express/-/express-3.0.0.tgz</a></p> <p>Path to dependency file: /package.json</p> <p>Path to vulnerable library: /node_modules/express/package.json</p> <p> <p>Found in HEAD commit: <a href="https://github.com/uriel-naor/UrielTest/commit/894f510f12658f81a9e1c64222c0c83e96f37e91">894f510f12658f81a9e1c64222c0c83e96f37e91</a></p></details> ## Vulnerabilities | CVE | Severity | <img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS | Dependency | Type | Fixed in (express version) | Fix PR available | | ------------- | ------------- | ----- | ----- | ----- | ------------- | --- | | [CVE-2017-16138](https://www.mend.io/vulnerability-database/CVE-2017-16138) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | mime-1.2.6.tgz | Transitive | N/A* | &#10060; | | [CVE-2017-16119](https://www.mend.io/vulnerability-database/CVE-2017-16119) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | fresh-0.1.0.tgz | Transitive | N/A* | &#10060; | | [CVE-2014-6394](https://www.mend.io/vulnerability-database/CVE-2014-6394) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.3 | detected in multiple dependencies | Transitive | 3.21.0 | &#9989; | | [CVE-2013-7370](https://www.mend.io/vulnerability-database/CVE-2013-7370) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 6.1 | connect-2.6.0.tgz | Transitive | 3.21.0 | &#9989; | | [CVE-2014-6393](https://www.mend.io/vulnerability-database/CVE-2014-6393) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 6.1 | express-3.0.0.tgz | Direct | 3.21.0 | &#9989; | | [WS-2013-0004](https://github.com/senchalabs/connect/commit/126187c4e12162e231b87350740045e5bb06e93a) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 6.1 | connect-2.6.0.tgz | Transitive | 3.21.0 | &#9989; | | [CVE-2013-7371](https://www.mend.io/vulnerability-database/CVE-2013-7371) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 6.1 | connect-2.6.0.tgz | Transitive | 3.21.0 | &#9989; | | [CVE-2018-3717](https://www.mend.io/vulnerability-database/CVE-2018-3717) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 5.4 | connect-2.6.0.tgz | Transitive | 3.21.0 | &#9989; | | [CVE-2015-8859](https://www.mend.io/vulnerability-database/CVE-2015-8859) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 5.3 | detected in multiple dependencies | Transitive | 3.21.0 | &#9989; | | [CVE-2014-7191](https://www.mend.io/vulnerability-database/CVE-2014-7191) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 5.3 | qs-0.5.1.tgz | Transitive | 3.21.0 | &#9989; | <p>*For some transitive vulnerabilities, there is no version of direct dependency with a fix. Check the section "Details" below to see if there is a version of transitive dependency where vulnerability is fixed.</p> ## Details <details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2017-16138</summary> ### Vulnerable Library - <b>mime-1.2.6.tgz</b></p> <p>A comprehensive library for mime-type mapping</p> <p>Library home page: <a href="https://registry.npmjs.org/mime/-/mime-1.2.6.tgz">https://registry.npmjs.org/mime/-/mime-1.2.6.tgz</a></p> <p>Path to dependency file: /package.json</p> <p>Path to vulnerable library: /node_modules/mime/package.json</p> <p> Dependency Hierarchy: - express-3.0.0.tgz (Root Library) - send-0.1.0.tgz - :x: **mime-1.2.6.tgz** (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/uriel-naor/UrielTest/commit/894f510f12658f81a9e1c64222c0c83e96f37e91">894f510f12658f81a9e1c64222c0c83e96f37e91</a></p> <p>Found in base branch: <b>main</b></p> </p> <p></p> ### Vulnerability Details <p> The mime module < 1.4.1, 2.0.1, 2.0.2 is vulnerable to regular expression denial of service when a mime lookup is performed on untrusted user input. <p>Publish Date: 2018-06-07 <p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2017-16138>CVE-2017-16138</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>7.5</b>) <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: None - Integrity Impact: None - Availability Impact: High </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> <p></p> ### Suggested Fix <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-16138">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-16138</a></p> <p>Release Date: 2018-06-07</p> <p>Fix Resolution: 1.4.1,2.0.3</p> </p> <p></p> </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2017-16119</summary> ### Vulnerable Library - <b>fresh-0.1.0.tgz</b></p> <p>HTTP response freshness testing</p> <p>Library home page: <a href="https://registry.npmjs.org/fresh/-/fresh-0.1.0.tgz">https://registry.npmjs.org/fresh/-/fresh-0.1.0.tgz</a></p> <p>Path to dependency file: /package.json</p> <p>Path to vulnerable library: /node_modules/fresh/package.json</p> <p> Dependency Hierarchy: - express-3.0.0.tgz (Root Library) - :x: **fresh-0.1.0.tgz** (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/uriel-naor/UrielTest/commit/894f510f12658f81a9e1c64222c0c83e96f37e91">894f510f12658f81a9e1c64222c0c83e96f37e91</a></p> <p>Found in base branch: <b>main</b></p> </p> <p></p> ### Vulnerability Details <p> Fresh is a module used by the Express.js framework for HTTP response freshness testing. It is vulnerable to a regular expression denial of service when it is passed specially crafted input to parse. This causes the event loop to be blocked causing a denial of service condition. <p>Publish Date: 2018-06-07 <p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2017-16119>CVE-2017-16119</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://www.npmjs.com/advisories/526">https://www.npmjs.com/advisories/526</a></p> <p>Release Date: 2018-06-07</p> <p>Fix Resolution: fresh - 0.5.2</p> </p> <p></p> </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2014-6394</summary> ### Vulnerable Libraries - <b>send-0.1.0.tgz</b>, <b>send-0.0.4.tgz</b></p> <p> ### <b>send-0.1.0.tgz</b></p> <p>Better streaming static file server with Range and conditional-GET support</p> <p>Library home page: <a href="https://registry.npmjs.org/send/-/send-0.1.0.tgz">https://registry.npmjs.org/send/-/send-0.1.0.tgz</a></p> <p>Path to dependency file: /package.json</p> <p>Path to vulnerable library: /node_modules/send/package.json</p> <p> Dependency Hierarchy: - express-3.0.0.tgz (Root Library) - :x: **send-0.1.0.tgz** (Vulnerable Library) ### <b>send-0.0.4.tgz</b></p> <p>Better streaming static file server with Range and conditional-GET support</p> <p>Library home page: <a href="https://registry.npmjs.org/send/-/send-0.0.4.tgz">https://registry.npmjs.org/send/-/send-0.0.4.tgz</a></p> <p>Path to dependency file: /package.json</p> <p>Path to vulnerable library: /node_modules/connect/node_modules/send/package.json</p> <p> Dependency Hierarchy: - express-3.0.0.tgz (Root Library) - connect-2.6.0.tgz - :x: **send-0.0.4.tgz** (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/uriel-naor/UrielTest/commit/894f510f12658f81a9e1c64222c0c83e96f37e91">894f510f12658f81a9e1c64222c0c83e96f37e91</a></p> <p>Found in base branch: <b>main</b></p> </p> <p></p> ### Vulnerability Details <p> visionmedia send before 0.8.4 for Node.js uses a partial comparison for verifying whether a directory is within the document root, which allows remote attackers to access restricted directories, as demonstrated using "public-restricted" under a "public" directory. <p>Publish Date: 2014-10-08 <p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2014-6394>CVE-2014-6394</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>7.3</b>) <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: Low - Integrity Impact: Low - Availability Impact: Low </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> <p></p> ### Suggested Fix <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://nvd.nist.gov/vuln/detail/CVE-2014-6394">https://nvd.nist.gov/vuln/detail/CVE-2014-6394</a></p> <p>Release Date: 2014-10-08</p> <p>Fix Resolution (send): 0.8.4</p> <p>Direct dependency fix Resolution (express): 3.21.0</p><p>Fix Resolution (send): 0.8.4</p> <p>Direct dependency fix Resolution (express): 3.21.0</p> </p> <p></p> :rescue_worker_helmet: Automatic Remediation is available for this issue </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2013-7370</summary> ### Vulnerable Library - <b>connect-2.6.0.tgz</b></p> <p>High performance middleware framework</p> <p>Library home page: <a href="https://registry.npmjs.org/connect/-/connect-2.6.0.tgz">https://registry.npmjs.org/connect/-/connect-2.6.0.tgz</a></p> <p>Path to dependency file: /package.json</p> <p>Path to vulnerable library: /node_modules/connect/package.json</p> <p> Dependency Hierarchy: - express-3.0.0.tgz (Root Library) - :x: **connect-2.6.0.tgz** (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/uriel-naor/UrielTest/commit/894f510f12658f81a9e1c64222c0c83e96f37e91">894f510f12658f81a9e1c64222c0c83e96f37e91</a></p> <p>Found in base branch: <b>main</b></p> </p> <p></p> ### Vulnerability Details <p> node-connect before 2.8.1 has XSS in the Sencha Labs Connect middleware <p>Publish Date: 2019-12-11 <p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2013-7370>CVE-2013-7370</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="http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2013-7370">http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2013-7370</a></p> <p>Release Date: 2019-12-11</p> <p>Fix Resolution (connect): 2.8.2</p> <p>Direct dependency fix Resolution (express): 3.21.0</p> </p> <p></p> :rescue_worker_helmet: Automatic Remediation is available for this issue </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2014-6393</summary> ### Vulnerable Library - <b>express-3.0.0.tgz</b></p> <p>Sinatra inspired web development framework</p> <p>Library home page: <a href="https://registry.npmjs.org/express/-/express-3.0.0.tgz">https://registry.npmjs.org/express/-/express-3.0.0.tgz</a></p> <p>Path to dependency file: /package.json</p> <p>Path to vulnerable library: /node_modules/express/package.json</p> <p> Dependency Hierarchy: - :x: **express-3.0.0.tgz** (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/uriel-naor/UrielTest/commit/894f510f12658f81a9e1c64222c0c83e96f37e91">894f510f12658f81a9e1c64222c0c83e96f37e91</a></p> <p>Found in base branch: <b>main</b></p> </p> <p></p> ### Vulnerability Details <p> The Express web framework before 3.11 and 4.x before 4.5 for Node.js does not provide a charset field in HTTP Content-Type headers in 400 level responses, which might allow remote attackers to conduct cross-site scripting (XSS) attacks via characters in a non-standard encoding. <p>Publish Date: 2017-08-09 <p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2014-6393>CVE-2014-6393</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>6.1</b>) <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: Required - Scope: Changed - Impact Metrics: - Confidentiality Impact: Low - Integrity Impact: Low - Availability Impact: None </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> <p></p> ### Suggested Fix <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-6393">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-6393</a></p> <p>Release Date: 2017-08-09</p> <p>Fix Resolution (express): express - 3.11.0, 4.5.0</p> <p>Direct dependency fix Resolution (express): 3.21.0</p> </p> <p></p> :rescue_worker_helmet: Automatic Remediation is available for this issue </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> WS-2013-0004</summary> ### Vulnerable Library - <b>connect-2.6.0.tgz</b></p> <p>High performance middleware framework</p> <p>Library home page: <a href="https://registry.npmjs.org/connect/-/connect-2.6.0.tgz">https://registry.npmjs.org/connect/-/connect-2.6.0.tgz</a></p> <p>Path to dependency file: /package.json</p> <p>Path to vulnerable library: /node_modules/connect/package.json</p> <p> Dependency Hierarchy: - express-3.0.0.tgz (Root Library) - :x: **connect-2.6.0.tgz** (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/uriel-naor/UrielTest/commit/894f510f12658f81a9e1c64222c0c83e96f37e91">894f510f12658f81a9e1c64222c0c83e96f37e91</a></p> <p>Found in base branch: <b>main</b></p> </p> <p></p> ### Vulnerability Details <p> The "methodOverride" let the http post to override the method of the request with the value of the post key or with the header, which allows XSS attack. <p>Publish Date: 2013-06-27 <p>URL: <a href=https://github.com/senchalabs/connect/commit/126187c4e12162e231b87350740045e5bb06e93a>WS-2013-0004</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>Release Date: 2013-06-27</p> <p>Fix Resolution (connect): 2.8.2</p> <p>Direct dependency fix Resolution (express): 3.21.0</p> </p> <p></p> :rescue_worker_helmet: Automatic Remediation is available for this issue </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2013-7371</summary> ### Vulnerable Library - <b>connect-2.6.0.tgz</b></p> <p>High performance middleware framework</p> <p>Library home page: <a href="https://registry.npmjs.org/connect/-/connect-2.6.0.tgz">https://registry.npmjs.org/connect/-/connect-2.6.0.tgz</a></p> <p>Path to dependency file: /package.json</p> <p>Path to vulnerable library: /node_modules/connect/package.json</p> <p> Dependency Hierarchy: - express-3.0.0.tgz (Root Library) - :x: **connect-2.6.0.tgz** (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/uriel-naor/UrielTest/commit/894f510f12658f81a9e1c64222c0c83e96f37e91">894f510f12658f81a9e1c64222c0c83e96f37e91</a></p> <p>Found in base branch: <b>main</b></p> </p> <p></p> ### Vulnerability Details <p> node-connects before 2.8.2 has cross site scripting in Sencha Labs Connect middleware (vulnerability due to incomplete fix for CVE-2013-7370) <p>Publish Date: 2019-12-11 <p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2013-7371>CVE-2013-7371</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="http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2013-7371">http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2013-7371</a></p> <p>Release Date: 2019-12-11</p> <p>Fix Resolution (connect): 2.8.2</p> <p>Direct dependency fix Resolution (express): 3.21.0</p> </p> <p></p> :rescue_worker_helmet: Automatic Remediation is available for this issue </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2018-3717</summary> ### Vulnerable Library - <b>connect-2.6.0.tgz</b></p> <p>High performance middleware framework</p> <p>Library home page: <a href="https://registry.npmjs.org/connect/-/connect-2.6.0.tgz">https://registry.npmjs.org/connect/-/connect-2.6.0.tgz</a></p> <p>Path to dependency file: /package.json</p> <p>Path to vulnerable library: /node_modules/connect/package.json</p> <p> Dependency Hierarchy: - express-3.0.0.tgz (Root Library) - :x: **connect-2.6.0.tgz** (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/uriel-naor/UrielTest/commit/894f510f12658f81a9e1c64222c0c83e96f37e91">894f510f12658f81a9e1c64222c0c83e96f37e91</a></p> <p>Found in base branch: <b>main</b></p> </p> <p></p> ### Vulnerability Details <p> connect node module before 2.14.0 suffers from a Cross-Site Scripting (XSS) vulnerability due to a lack of validation of file in directory.js middleware. <p>Publish Date: 2018-06-07 <p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2018-3717>CVE-2018-3717</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>5.4</b>) <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: Low - 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://nvd.nist.gov/vuln/detail/CVE-2018-3717">https://nvd.nist.gov/vuln/detail/CVE-2018-3717</a></p> <p>Release Date: 2018-06-07</p> <p>Fix Resolution (connect): 2.14.0</p> <p>Direct dependency fix Resolution (express): 3.21.0</p> </p> <p></p> :rescue_worker_helmet: Automatic Remediation is available for this issue </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2015-8859</summary> ### Vulnerable Libraries - <b>send-0.1.0.tgz</b>, <b>send-0.0.4.tgz</b></p> <p> ### <b>send-0.1.0.tgz</b></p> <p>Better streaming static file server with Range and conditional-GET support</p> <p>Library home page: <a href="https://registry.npmjs.org/send/-/send-0.1.0.tgz">https://registry.npmjs.org/send/-/send-0.1.0.tgz</a></p> <p>Path to dependency file: /package.json</p> <p>Path to vulnerable library: /node_modules/send/package.json</p> <p> Dependency Hierarchy: - express-3.0.0.tgz (Root Library) - :x: **send-0.1.0.tgz** (Vulnerable Library) ### <b>send-0.0.4.tgz</b></p> <p>Better streaming static file server with Range and conditional-GET support</p> <p>Library home page: <a href="https://registry.npmjs.org/send/-/send-0.0.4.tgz">https://registry.npmjs.org/send/-/send-0.0.4.tgz</a></p> <p>Path to dependency file: /package.json</p> <p>Path to vulnerable library: /node_modules/connect/node_modules/send/package.json</p> <p> Dependency Hierarchy: - express-3.0.0.tgz (Root Library) - connect-2.6.0.tgz - :x: **send-0.0.4.tgz** (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/uriel-naor/UrielTest/commit/894f510f12658f81a9e1c64222c0c83e96f37e91">894f510f12658f81a9e1c64222c0c83e96f37e91</a></p> <p>Found in base branch: <b>main</b></p> </p> <p></p> ### Vulnerability Details <p> The send package before 0.11.1 for Node.js allows attackers to obtain the root path via unspecified vectors. <p>Publish Date: 2017-01-23 <p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2015-8859>CVE-2015-8859</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>5.3</b>) <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: Low - Integrity Impact: None - Availability Impact: None </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> <p></p> ### Suggested Fix <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://nvd.nist.gov/vuln/detail/CVE-2015-8859">https://nvd.nist.gov/vuln/detail/CVE-2015-8859</a></p> <p>Release Date: 2017-01-23</p> <p>Fix Resolution (send): 0.11.1</p> <p>Direct dependency fix Resolution (express): 3.21.0</p><p>Fix Resolution (send): 0.11.1</p> <p>Direct dependency fix Resolution (express): 3.21.0</p> </p> <p></p> :rescue_worker_helmet: Automatic Remediation is available for this issue </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2014-7191</summary> ### Vulnerable Library - <b>qs-0.5.1.tgz</b></p> <p>querystring parser</p> <p>Library home page: <a href="https://registry.npmjs.org/qs/-/qs-0.5.1.tgz">https://registry.npmjs.org/qs/-/qs-0.5.1.tgz</a></p> <p>Path to dependency file: /package.json</p> <p>Path to vulnerable library: /node_modules/qs/package.json</p> <p> Dependency Hierarchy: - express-3.0.0.tgz (Root Library) - connect-2.6.0.tgz - :x: **qs-0.5.1.tgz** (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/uriel-naor/UrielTest/commit/894f510f12658f81a9e1c64222c0c83e96f37e91">894f510f12658f81a9e1c64222c0c83e96f37e91</a></p> <p>Found in base branch: <b>main</b></p> </p> <p></p> ### Vulnerability Details <p> The qs module before 1.0.0 in Node.js does not call the compact function for array data, which allows remote attackers to cause a denial of service (memory consumption) by using a large index value to create a sparse array. <p>Publish Date: 2014-10-19 <p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2014-7191>CVE-2014-7191</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>5.3</b>) <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: None - Integrity Impact: 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://nvd.nist.gov/vuln/detail/CVE-2014-7191">https://nvd.nist.gov/vuln/detail/CVE-2014-7191</a></p> <p>Release Date: 2014-10-19</p> <p>Fix Resolution (qs): 1.0.0</p> <p>Direct dependency fix Resolution (express): 3.21.0</p> </p> <p></p> :rescue_worker_helmet: Automatic Remediation is available for this issue </details> *** <p>:rescue_worker_helmet: Automatic Remediation is available for this issue.</p>
non_priority
express tgz vulnerabilities highest severity is vulnerable library express tgz sinatra inspired web development framework library home page a href path to dependency file package json path to vulnerable library node modules express package json found in head commit a href vulnerabilities cve severity cvss dependency type fixed in express version fix pr available high mime tgz transitive n a high fresh tgz transitive n a high detected in multiple dependencies transitive medium connect tgz transitive medium express tgz direct medium connect tgz transitive medium connect tgz transitive medium connect tgz transitive medium detected in multiple dependencies transitive medium qs tgz transitive for some transitive vulnerabilities there is no version of direct dependency with a fix check the section details below to see if there is a version of transitive dependency where vulnerability is fixed details cve vulnerable library mime tgz a comprehensive library for mime type mapping library home page a href path to dependency file package json path to vulnerable library node modules mime package json dependency hierarchy express tgz root library send tgz x mime tgz vulnerable library found in head commit a href found in base branch main vulnerability details the mime module is vulnerable to regular expression denial of service when a mime lookup is performed on untrusted user input 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 cve vulnerable library fresh tgz http response freshness testing library home page a href path to dependency file package json path to vulnerable library node modules fresh package json dependency hierarchy express tgz root library x fresh tgz vulnerable library found in head commit a href found in base branch main vulnerability details fresh is a module used by the express js framework for http response freshness testing it is vulnerable to a regular expression denial of service when it is passed specially crafted input to parse this causes the event loop to be blocked causing a denial of service condition 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 fresh cve vulnerable libraries send tgz send tgz send tgz better streaming static file server with range and conditional get support library home page a href path to dependency file package json path to vulnerable library node modules send package json dependency hierarchy express tgz root library x send tgz vulnerable library send tgz better streaming static file server with range and conditional get support library home page a href path to dependency file package json path to vulnerable library node modules connect node modules send package json dependency hierarchy express tgz root library connect tgz x send tgz vulnerable library found in head commit a href found in base branch main vulnerability details visionmedia send before for node js uses a partial comparison for verifying whether a directory is within the document root which allows remote attackers to access restricted directories as demonstrated using public restricted under a public directory publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact low integrity impact low availability impact low for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution send direct dependency fix resolution express fix resolution send direct dependency fix resolution express rescue worker helmet automatic remediation is available for this issue cve vulnerable library connect tgz high performance middleware framework library home page a href path to dependency file package json path to vulnerable library node modules connect package json dependency hierarchy express tgz root library x connect tgz vulnerable library found in head commit a href found in base branch main vulnerability details node connect before has xss in the sencha labs connect middleware 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 connect direct dependency fix resolution express rescue worker helmet automatic remediation is available for this issue cve vulnerable library express tgz sinatra inspired web development framework library home page a href path to dependency file package json path to vulnerable library node modules express package json dependency hierarchy x express tgz vulnerable library found in head commit a href found in base branch main vulnerability details the express web framework before and x before for node js does not provide a charset field in http content type headers in level responses which might allow remote attackers to conduct cross site scripting xss attacks via characters in a non standard encoding 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 express express direct dependency fix resolution express rescue worker helmet automatic remediation is available for this issue ws vulnerable library connect tgz high performance middleware framework library home page a href path to dependency file package json path to vulnerable library node modules connect package json dependency hierarchy express tgz root library x connect tgz vulnerable library found in head commit a href found in base branch main vulnerability details the methodoverride let the http post to override the method of the request with the value of the post key or with the header which allows xss attack 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 release date fix resolution connect direct dependency fix resolution express rescue worker helmet automatic remediation is available for this issue cve vulnerable library connect tgz high performance middleware framework library home page a href path to dependency file package json path to vulnerable library node modules connect package json dependency hierarchy express tgz root library x connect tgz vulnerable library found in head commit a href found in base branch main vulnerability details node connects before has cross site scripting in sencha labs connect middleware vulnerability due to incomplete fix for cve publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction required scope 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 connect direct dependency fix resolution express rescue worker helmet automatic remediation is available for this issue cve vulnerable library connect tgz high performance middleware framework library home page a href path to dependency file package json path to vulnerable library node modules connect package json dependency hierarchy express tgz root library x connect tgz vulnerable library found in head commit a href found in base branch main vulnerability details connect node module before suffers from a cross site scripting xss vulnerability due to a lack of validation of file in directory js middleware publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required low 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 connect direct dependency fix resolution express rescue worker helmet automatic remediation is available for this issue cve vulnerable libraries send tgz send tgz send tgz better streaming static file server with range and conditional get support library home page a href path to dependency file package json path to vulnerable library node modules send package json dependency hierarchy express tgz root library x send tgz vulnerable library send tgz better streaming static file server with range and conditional get support library home page a href path to dependency file package json path to vulnerable library node modules connect node modules send package json dependency hierarchy express tgz root library connect tgz x send tgz vulnerable library found in head commit a href found in base branch main vulnerability details the send package before for node js allows attackers to obtain the root path via unspecified vectors publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact low integrity impact none availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution send direct dependency fix resolution express fix resolution send direct dependency fix resolution express rescue worker helmet automatic remediation is available for this issue cve vulnerable library qs tgz querystring parser library home page a href path to dependency file package json path to vulnerable library node modules qs package json dependency hierarchy express tgz root library connect tgz x qs tgz vulnerable library found in head commit a href found in base branch main vulnerability details the qs module before in node js does not call the compact function for array data which allows remote attackers to cause a denial of service memory consumption by using a large index value to create a sparse array publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact none integrity impact none availability impact low for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution qs direct dependency fix resolution express rescue worker helmet automatic remediation is available for this issue rescue worker helmet automatic remediation is available for this issue
0
85,495
10,618,356,492
IssuesEvent
2019-10-13 03:40:40
carbon-design-system/ibm-dotcom-library
https://api.github.com/repos/carbon-design-system/ibm-dotcom-library
opened
Locale Selector Animation: Open & Close
design design: ux dev dev: research migrate
_james-dow created the following on Sep 10:_ ### Detailed description We need to do an animation exploration around the Locale Selector for when it opens. ### Additional information - [Lara identified some moments to explore](https://ibm.ent.box.com/file/504039567025) - [Original Design Exploration](https://github.ibm.com/webstandards/digital-design/issues/787) - [To be developed in Sprint 19](https://github.ibm.com/webstandards/digital-design/issues/1078) - [Invision Prototype of Design Changes](https://ibm.invisionapp.com/share/26NZ77UF57S) - [IBM Design Language: Motion](https://www.ibm.com/design/language/elements/motion/basics) - [Locale Selector API](https://1.www.s81c.com/common/js/dynamicnav/www/countrylist/usen-utf8.js) - [User Locale API](https://api.www.s81c.com/webmaster/dbip/) ### Before / After <img src="https://media.github.ibm.com/user/19/files/c219c000-d32c-11e9-97b4-38e41040b0f2" width="300" /> <img src="https://media.github.ibm.com/user/19/files/e2e21580-d32c-11e9-9025-62056b296c52" width="300" /> ### Acceptance criteria - [ ] Quick prototypes to demonstrate explorations - [ ] At least 3 alternatives _Original issue: https://github.ibm.com/webstandards/digital-design/issues/1646_
2.0
Locale Selector Animation: Open & Close - _james-dow created the following on Sep 10:_ ### Detailed description We need to do an animation exploration around the Locale Selector for when it opens. ### Additional information - [Lara identified some moments to explore](https://ibm.ent.box.com/file/504039567025) - [Original Design Exploration](https://github.ibm.com/webstandards/digital-design/issues/787) - [To be developed in Sprint 19](https://github.ibm.com/webstandards/digital-design/issues/1078) - [Invision Prototype of Design Changes](https://ibm.invisionapp.com/share/26NZ77UF57S) - [IBM Design Language: Motion](https://www.ibm.com/design/language/elements/motion/basics) - [Locale Selector API](https://1.www.s81c.com/common/js/dynamicnav/www/countrylist/usen-utf8.js) - [User Locale API](https://api.www.s81c.com/webmaster/dbip/) ### Before / After <img src="https://media.github.ibm.com/user/19/files/c219c000-d32c-11e9-97b4-38e41040b0f2" width="300" /> <img src="https://media.github.ibm.com/user/19/files/e2e21580-d32c-11e9-9025-62056b296c52" width="300" /> ### Acceptance criteria - [ ] Quick prototypes to demonstrate explorations - [ ] At least 3 alternatives _Original issue: https://github.ibm.com/webstandards/digital-design/issues/1646_
non_priority
locale selector animation open close james dow created the following on sep detailed description we need to do an animation exploration around the locale selector for when it opens additional information before after acceptance criteria quick prototypes to demonstrate explorations at least alternatives original issue
0
280,261
24,288,019,038
IssuesEvent
2022-09-29 01:23:12
yirugi/sptest
https://api.github.com/repos/yirugi/sptest
opened
Results tab design improvement
enhancement retest usability
<a href="https://github.itap.purdue.edu/brewer36"><img src="https://avatars.github.itap.purdue.edu/u/3637?" align="left" width="96" height="96" hspace="10"></img></a> **Issue by [brewer36](https://github.itap.purdue.edu/brewer36)** _Monday Mar 01, 2021 at 21:07 GMT_ _Originally opened as https://github.itap.purdue.edu/ScientificSolutions/superpower_gui/issues/16_ ---- - [x] Can't find the results directly, one additional click is required. Results should automatically show up at the top of the tab - [x] Old results will stay until the most update entry is clicked. This can cause errors and confusion if the user checks quickly. Results should automatically refresh - [x] Results display should scroll after reaching a max height
1.0
Results tab design improvement - <a href="https://github.itap.purdue.edu/brewer36"><img src="https://avatars.github.itap.purdue.edu/u/3637?" align="left" width="96" height="96" hspace="10"></img></a> **Issue by [brewer36](https://github.itap.purdue.edu/brewer36)** _Monday Mar 01, 2021 at 21:07 GMT_ _Originally opened as https://github.itap.purdue.edu/ScientificSolutions/superpower_gui/issues/16_ ---- - [x] Can't find the results directly, one additional click is required. Results should automatically show up at the top of the tab - [x] Old results will stay until the most update entry is clicked. This can cause errors and confusion if the user checks quickly. Results should automatically refresh - [x] Results display should scroll after reaching a max height
non_priority
results tab design improvement issue by monday mar at gmt originally opened as can t find the results directly one additional click is required results should automatically show up at the top of the tab old results will stay until the most update entry is clicked this can cause errors and confusion if the user checks quickly results should automatically refresh results display should scroll after reaching a max height
0
5,680
5,114,716,745
IssuesEvent
2017-01-06 19:24:47
mysociety/alaveteli
https://api.github.com/repos/mysociety/alaveteli
closed
explore running Alavateli on JRuby
framework improvement performance
Many people report good performance results, particularly with regard to memory consumption, when running Rails sites on JRuby instead of MRI. (The author of JRuby, Charles Nutter, even [suggested this for Alaveteli](http://www.mysociety.org/2009/09/17/whatdotheyknow-growing-pains-and-ruby-memory-leaks/#comment-1840).) I guess the likely issue here would be any dependent gems that include native code. @crowbot suggested that it would be worth allocating a day at some point to explore this.
True
explore running Alavateli on JRuby - Many people report good performance results, particularly with regard to memory consumption, when running Rails sites on JRuby instead of MRI. (The author of JRuby, Charles Nutter, even [suggested this for Alaveteli](http://www.mysociety.org/2009/09/17/whatdotheyknow-growing-pains-and-ruby-memory-leaks/#comment-1840).) I guess the likely issue here would be any dependent gems that include native code. @crowbot suggested that it would be worth allocating a day at some point to explore this.
non_priority
explore running alavateli on jruby many people report good performance results particularly with regard to memory consumption when running rails sites on jruby instead of mri the author of jruby charles nutter even i guess the likely issue here would be any dependent gems that include native code crowbot suggested that it would be worth allocating a day at some point to explore this
0
9,459
3,916,323,319
IssuesEvent
2016-04-21 00:52:44
elastic/logstash
https://api.github.com/repos/elastic/logstash
closed
Add /robots.txt to logstash.net website host
code-cleanup docs
Currently google (and I guess the rest web search engines too) finds the NOT latest version when searching for some documentation. and I think it's not the way it should be. The solution for this is adding the file robots.txt in the root of the host. currently [http://logstash.net/robots.txt](http://logstash.net/robots.txt) returns 404. thanks :)
1.0
Add /robots.txt to logstash.net website host - Currently google (and I guess the rest web search engines too) finds the NOT latest version when searching for some documentation. and I think it's not the way it should be. The solution for this is adding the file robots.txt in the root of the host. currently [http://logstash.net/robots.txt](http://logstash.net/robots.txt) returns 404. thanks :)
non_priority
add robots txt to logstash net website host currently google and i guess the rest web search engines too finds the not latest version when searching for some documentation and i think it s not the way it should be the solution for this is adding the file robots txt in the root of the host currently returns thanks
0
7,812
4,074,543,833
IssuesEvent
2016-05-28 14:37:18
jeff1evesque/drupal-demonstration
https://api.github.com/repos/jeff1evesque/drupal-demonstration
opened
Create systemd script to automate redis-server
build new feature
We will create a systemd script that will automate starting the redis-server process. This script will be called within `redis/manifests/start.pp`.
1.0
Create systemd script to automate redis-server - We will create a systemd script that will automate starting the redis-server process. This script will be called within `redis/manifests/start.pp`.
non_priority
create systemd script to automate redis server we will create a systemd script that will automate starting the redis server process this script will be called within redis manifests start pp
0
316,976
23,658,570,466
IssuesEvent
2022-08-26 13:34:47
GoogleCloudPlatform/pbmm-on-gcp-onboarding
https://api.github.com/repos/GoogleCloudPlatform/pbmm-on-gcp-onboarding
opened
As a developer i need to install/modify/update/delete the landing zone - modify/update readme and formal doc
documentation
20220826: draft in progress - Gather a GCP billing ID for association later - Involve the (BAA) Billing Account Administrator for the to-be-shared billing ID so that the SA account below can be added as a BAA - Gather a subdomain for use by organization onboarding - Involve the IT owner of the domain zone - to be able to add a TXT record to the zone just for organization onboarding - Create new Cloud Identity account - as super admin (SA) - reference https://github.com/GoogleCloudPlatform/pbmm-on-gcp-onboarding/blob/main/docs/google-cloud-onboarding.md#onboarding-category-3b1-3rd-party-email-account---3rd-party-aws-route53-domain-validation---reuse-existing-billing-account - Onboard the organization as step 2 of creating the super admin account - Add the following roles to the SA account before cloning/running the repo - Clone repo (several options) - Configure variables - Check in only bootstrap and common - Run script - invoking 1 of 4 runs (bootstrap, common, nonprod, prod) - all 4 will run we expect bootstrap only to pass - Fix any issues with config blocking common builds - Commit common - If common passes, commit nonprod config - If nonprod passes, commit prod config - Modifications: - Do a small FW change on prod - commit, observe changes in VPC Networks view and Asset Inventory change summary - Upstream updates: pending - Full LZ retrofit: pending - Full LZ delete: pending
1.0
As a developer i need to install/modify/update/delete the landing zone - modify/update readme and formal doc - 20220826: draft in progress - Gather a GCP billing ID for association later - Involve the (BAA) Billing Account Administrator for the to-be-shared billing ID so that the SA account below can be added as a BAA - Gather a subdomain for use by organization onboarding - Involve the IT owner of the domain zone - to be able to add a TXT record to the zone just for organization onboarding - Create new Cloud Identity account - as super admin (SA) - reference https://github.com/GoogleCloudPlatform/pbmm-on-gcp-onboarding/blob/main/docs/google-cloud-onboarding.md#onboarding-category-3b1-3rd-party-email-account---3rd-party-aws-route53-domain-validation---reuse-existing-billing-account - Onboard the organization as step 2 of creating the super admin account - Add the following roles to the SA account before cloning/running the repo - Clone repo (several options) - Configure variables - Check in only bootstrap and common - Run script - invoking 1 of 4 runs (bootstrap, common, nonprod, prod) - all 4 will run we expect bootstrap only to pass - Fix any issues with config blocking common builds - Commit common - If common passes, commit nonprod config - If nonprod passes, commit prod config - Modifications: - Do a small FW change on prod - commit, observe changes in VPC Networks view and Asset Inventory change summary - Upstream updates: pending - Full LZ retrofit: pending - Full LZ delete: pending
non_priority
as a developer i need to install modify update delete the landing zone modify update readme and formal doc draft in progress gather a gcp billing id for association later involve the baa billing account administrator for the to be shared billing id so that the sa account below can be added as a baa gather a subdomain for use by organization onboarding involve the it owner of the domain zone to be able to add a txt record to the zone just for organization onboarding create new cloud identity account as super admin sa reference onboard the organization as step of creating the super admin account add the following roles to the sa account before cloning running the repo clone repo several options configure variables check in only bootstrap and common run script invoking of runs bootstrap common nonprod prod all will run we expect bootstrap only to pass fix any issues with config blocking common builds commit common if common passes commit nonprod config if nonprod passes commit prod config modifications do a small fw change on prod commit observe changes in vpc networks view and asset inventory change summary upstream updates pending full lz retrofit pending full lz delete pending
0
219,102
24,446,211,876
IssuesEvent
2022-10-06 18:12:22
hapifhir/hapi-fhir
https://api.github.com/repos/hapifhir/hapi-fhir
reopened
CVE-2022-25857 (High) detected in snakeyaml-1.30.jar, snakeyaml-1.29.jar
security vulnerability
## CVE-2022-25857 - High Severity Vulnerability <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>snakeyaml-1.30.jar</b>, <b>snakeyaml-1.29.jar</b></p></summary> <p> <details><summary><b>snakeyaml-1.30.jar</b></p></summary> <p>YAML 1.1 parser and emitter for Java</p> <p>Library home page: <a href="https://bitbucket.org/snakeyaml/snakeyaml">https://bitbucket.org/snakeyaml/snakeyaml</a></p> <p>Path to dependency file: /hapi-fhir-cli/hapi-fhir-cli-app/pom.xml</p> <p>Path to vulnerable library: /home/wss-scanner/.m2/repository/org/yaml/snakeyaml/1.30/snakeyaml-1.30.jar,/home/wss-scanner/.m2/repository/org/yaml/snakeyaml/1.30/snakeyaml-1.30.jar,/home/wss-scanner/.m2/repository/org/yaml/snakeyaml/1.30/snakeyaml-1.30.jar</p> <p> Dependency Hierarchy: - hapi-fhir-cli-api-6.2.0-PRE12-SNAPSHOT.jar (Root Library) - hapi-fhir-jpaserver-base-6.2.0-PRE12-SNAPSHOT.jar - springdoc-openapi-ui-1.5.13.jar - springdoc-openapi-webmvc-core-1.5.13.jar - springdoc-openapi-common-1.5.13.jar - swagger-integration-2.1.11.jar - swagger-core-2.1.12.jar - jackson-dataformat-yaml-2.13.2.jar - :x: **snakeyaml-1.30.jar** (Vulnerable Library) </details> <details><summary><b>snakeyaml-1.29.jar</b></p></summary> <p>YAML 1.1 parser and emitter for Java</p> <p>Library home page: <a href="http://www.snakeyaml.org">http://www.snakeyaml.org</a></p> <p>Path to dependency file: /hapi-fhir-spring-boot/hapi-fhir-spring-boot-samples/hapi-fhir-spring-boot-sample-client-apache/pom.xml</p> <p>Path to vulnerable library: /home/wss-scanner/.m2/repository/org/yaml/snakeyaml/1.29/snakeyaml-1.29.jar,/home/wss-scanner/.m2/repository/org/yaml/snakeyaml/1.29/snakeyaml-1.29.jar,/home/wss-scanner/.m2/repository/org/yaml/snakeyaml/1.29/snakeyaml-1.29.jar,/home/wss-scanner/.m2/repository/org/yaml/snakeyaml/1.29/snakeyaml-1.29.jar</p> <p> Dependency Hierarchy: - spring-boot-starter-web-2.6.7.jar (Root Library) - spring-boot-starter-2.6.7.jar - :x: **snakeyaml-1.29.jar** (Vulnerable Library) </details> <p>Found in HEAD commit: <a href="https://github.com/hapifhir/hapi-fhir/commit/b59f2d05a7d0fd10c7b03bb6f0ebf97757172a71">b59f2d05a7d0fd10c7b03bb6f0ebf97757172a71</a></p> <p>Found in base branch: <b>master</b></p> </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary> <p> The package org.yaml:snakeyaml from 0 and before 1.31 are vulnerable to Denial of Service (DoS) due missing to nested depth limitation for collections. <p>Publish Date: 2022-08-30 <p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-25857>CVE-2022-25857</a></p> </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary> <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: None - Integrity Impact: None - Availability Impact: High </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary> <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-25857">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-25857</a></p> <p>Release Date: 2022-08-30</p> <p>Fix Resolution (org.yaml:snakeyaml): 1.31</p> <p>Direct dependency fix Resolution (org.springframework.boot:spring-boot-starter-web): 2.6.9</p> </p> </details> <p></p> *** Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
True
CVE-2022-25857 (High) detected in snakeyaml-1.30.jar, snakeyaml-1.29.jar - ## CVE-2022-25857 - High Severity Vulnerability <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>snakeyaml-1.30.jar</b>, <b>snakeyaml-1.29.jar</b></p></summary> <p> <details><summary><b>snakeyaml-1.30.jar</b></p></summary> <p>YAML 1.1 parser and emitter for Java</p> <p>Library home page: <a href="https://bitbucket.org/snakeyaml/snakeyaml">https://bitbucket.org/snakeyaml/snakeyaml</a></p> <p>Path to dependency file: /hapi-fhir-cli/hapi-fhir-cli-app/pom.xml</p> <p>Path to vulnerable library: /home/wss-scanner/.m2/repository/org/yaml/snakeyaml/1.30/snakeyaml-1.30.jar,/home/wss-scanner/.m2/repository/org/yaml/snakeyaml/1.30/snakeyaml-1.30.jar,/home/wss-scanner/.m2/repository/org/yaml/snakeyaml/1.30/snakeyaml-1.30.jar</p> <p> Dependency Hierarchy: - hapi-fhir-cli-api-6.2.0-PRE12-SNAPSHOT.jar (Root Library) - hapi-fhir-jpaserver-base-6.2.0-PRE12-SNAPSHOT.jar - springdoc-openapi-ui-1.5.13.jar - springdoc-openapi-webmvc-core-1.5.13.jar - springdoc-openapi-common-1.5.13.jar - swagger-integration-2.1.11.jar - swagger-core-2.1.12.jar - jackson-dataformat-yaml-2.13.2.jar - :x: **snakeyaml-1.30.jar** (Vulnerable Library) </details> <details><summary><b>snakeyaml-1.29.jar</b></p></summary> <p>YAML 1.1 parser and emitter for Java</p> <p>Library home page: <a href="http://www.snakeyaml.org">http://www.snakeyaml.org</a></p> <p>Path to dependency file: /hapi-fhir-spring-boot/hapi-fhir-spring-boot-samples/hapi-fhir-spring-boot-sample-client-apache/pom.xml</p> <p>Path to vulnerable library: /home/wss-scanner/.m2/repository/org/yaml/snakeyaml/1.29/snakeyaml-1.29.jar,/home/wss-scanner/.m2/repository/org/yaml/snakeyaml/1.29/snakeyaml-1.29.jar,/home/wss-scanner/.m2/repository/org/yaml/snakeyaml/1.29/snakeyaml-1.29.jar,/home/wss-scanner/.m2/repository/org/yaml/snakeyaml/1.29/snakeyaml-1.29.jar</p> <p> Dependency Hierarchy: - spring-boot-starter-web-2.6.7.jar (Root Library) - spring-boot-starter-2.6.7.jar - :x: **snakeyaml-1.29.jar** (Vulnerable Library) </details> <p>Found in HEAD commit: <a href="https://github.com/hapifhir/hapi-fhir/commit/b59f2d05a7d0fd10c7b03bb6f0ebf97757172a71">b59f2d05a7d0fd10c7b03bb6f0ebf97757172a71</a></p> <p>Found in base branch: <b>master</b></p> </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary> <p> The package org.yaml:snakeyaml from 0 and before 1.31 are vulnerable to Denial of Service (DoS) due missing to nested depth limitation for collections. <p>Publish Date: 2022-08-30 <p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-25857>CVE-2022-25857</a></p> </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary> <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: None - Integrity Impact: None - Availability Impact: High </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary> <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-25857">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-25857</a></p> <p>Release Date: 2022-08-30</p> <p>Fix Resolution (org.yaml:snakeyaml): 1.31</p> <p>Direct dependency fix Resolution (org.springframework.boot:spring-boot-starter-web): 2.6.9</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 snakeyaml jar snakeyaml jar cve high severity vulnerability vulnerable libraries snakeyaml jar snakeyaml jar snakeyaml jar yaml parser and emitter for java library home page a href path to dependency file hapi fhir cli hapi fhir cli app pom xml path to vulnerable library home wss scanner repository org yaml snakeyaml snakeyaml jar home wss scanner repository org yaml snakeyaml snakeyaml jar home wss scanner repository org yaml snakeyaml snakeyaml jar dependency hierarchy hapi fhir cli api snapshot jar root library hapi fhir jpaserver base snapshot jar springdoc openapi ui jar springdoc openapi webmvc core jar springdoc openapi common jar swagger integration jar swagger core jar jackson dataformat yaml jar x snakeyaml jar vulnerable library snakeyaml jar yaml parser and emitter for java library home page a href path to dependency file hapi fhir spring boot hapi fhir spring boot samples hapi fhir spring boot sample client apache pom xml path to vulnerable library home wss scanner repository org yaml snakeyaml snakeyaml jar home wss scanner repository org yaml snakeyaml snakeyaml jar home wss scanner repository org yaml snakeyaml snakeyaml jar home wss scanner repository org yaml snakeyaml snakeyaml jar dependency hierarchy spring boot starter web jar root library spring boot starter jar x snakeyaml jar vulnerable library found in head commit a href found in base branch master vulnerability details the package org yaml snakeyaml from and before are vulnerable to denial of service dos due missing to nested depth limitation for collections publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact none integrity impact none availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution org yaml snakeyaml direct dependency fix resolution org springframework boot spring boot starter web step up your open source security game with mend
0
14,089
4,820,524,093
IssuesEvent
2016-11-04 23:20:35
julianguyen/ifme
https://api.github.com/repos/julianguyen/ifme
opened
Fix "Rubocop/Metrics/ClassLength" issue in app/controllers/strategies_controller.rb
codeclimate
Class has too many lines. [248/100] https://codeclimate.com/github/julianguyen/ifme/app/controllers/strategies_controller.rb#issue_581d14aa9a13990001000a2e
1.0
Fix "Rubocop/Metrics/ClassLength" issue in app/controllers/strategies_controller.rb - Class has too many lines. [248/100] https://codeclimate.com/github/julianguyen/ifme/app/controllers/strategies_controller.rb#issue_581d14aa9a13990001000a2e
non_priority
fix rubocop metrics classlength issue in app controllers strategies controller rb class has too many lines
0
316,070
27,134,136,242
IssuesEvent
2023-02-16 11:59:16
wazuh/wazuh
https://api.github.com/repos/wazuh/wazuh
closed
Release 4.4.0 - RC1 - E2E UX tests - Centralized configuration - Agent groups
module/configuration team/cicd type/test/manual release test/4.4.0
The following issue aims to run the specified test for the current release candidate, report the results, and open new issues for any encountered errors. ## Test information | | | |-------------------------|--------------------------------------------| | **Test name** | Centralized configuration - Agent groups | | **Category** | Configuration | | **Deployment option** |[Installation assistant](https://documentation.wazuh.com/current/installation-guide/wazuh-indexer/installation-assistant.html)| | **Main release issue** | https://github.com/wazuh/wazuh/issues/16132 | | **Main E2E UX test issue** | https://github.com/wazuh/wazuh/issues/16135 | | **Release candidate #** | RC1 | ## Environment | | | | |-|-|-| | **Component** | **OS** | **Installation** | | Wazuh dashboard | Amazon Linux 2 | [Installation assistant](https://documentation.wazuh.com/current/installation-guide/wazuh-indexer/installation-assistant.html)| | Wazuh indexer | Amazon Linux 2 | [Installation assistant](https://documentation.wazuh.com/current/installation-guide/wazuh-indexer/installation-assistant.html)| | Wazuh server | Amazon Linux 2 | [Installation assistant](https://documentation.wazuh.com/current/installation-guide/wazuh-indexer/installation-assistant.html)| | Wazuh agent | Windows | Wazuh WUI one-liner deploy IP GROUP (created beforehand) | ## Test description Test the functionality of agent groups for centralized configuration: - [x] Try different groups for different OS - [x] Try tags in the same group, to apply different blocks of configuration to different OS or agents. - [x] Try creating groups with different files of diferent types and sizes (try to reach the limits) - [x] Try creating multigroups and add agents to them, check configuration applies in order - [x] Check if propagation times are acceptable ## Test report procedure All test results must have one of the following statuses: | | | |---------------------------------|--------------------------------------------| | :green_circle: | All checks passed. | | :red_circle: | There is at least one failed result. | | :yellow_circle: | There is at least one expected failure or skipped test and no failures. | ## Conclusions All tests have been executed and the results can be found in the issue updates. | **Status** | **Test** | **Failure type** | **Notes** | |----------------|-------------|---------------------|----------------| | :green_circle: | Installing the Wazuh manager, dashboard, and indexer | - | - | | :green_circle: | Test 1: Deploy an agent on version 4.4.0 and set it to a group upon deployment | - | - | | :yellow_circle: | Test 2: Modifying configuration, adding agent to new groups. | Known issue | https://github.com/wazuh/wazuh-kibana-app/issues/5133 | ## Auditors validation The definition of done for this one is the validation of the conclusions and the test results from all auditors. All checks from below must be accepted in order to close this issue. - [x] @wazuh/binary-beasts - [x] @davidjiglesias
2.0
Release 4.4.0 - RC1 - E2E UX tests - Centralized configuration - Agent groups - The following issue aims to run the specified test for the current release candidate, report the results, and open new issues for any encountered errors. ## Test information | | | |-------------------------|--------------------------------------------| | **Test name** | Centralized configuration - Agent groups | | **Category** | Configuration | | **Deployment option** |[Installation assistant](https://documentation.wazuh.com/current/installation-guide/wazuh-indexer/installation-assistant.html)| | **Main release issue** | https://github.com/wazuh/wazuh/issues/16132 | | **Main E2E UX test issue** | https://github.com/wazuh/wazuh/issues/16135 | | **Release candidate #** | RC1 | ## Environment | | | | |-|-|-| | **Component** | **OS** | **Installation** | | Wazuh dashboard | Amazon Linux 2 | [Installation assistant](https://documentation.wazuh.com/current/installation-guide/wazuh-indexer/installation-assistant.html)| | Wazuh indexer | Amazon Linux 2 | [Installation assistant](https://documentation.wazuh.com/current/installation-guide/wazuh-indexer/installation-assistant.html)| | Wazuh server | Amazon Linux 2 | [Installation assistant](https://documentation.wazuh.com/current/installation-guide/wazuh-indexer/installation-assistant.html)| | Wazuh agent | Windows | Wazuh WUI one-liner deploy IP GROUP (created beforehand) | ## Test description Test the functionality of agent groups for centralized configuration: - [x] Try different groups for different OS - [x] Try tags in the same group, to apply different blocks of configuration to different OS or agents. - [x] Try creating groups with different files of diferent types and sizes (try to reach the limits) - [x] Try creating multigroups and add agents to them, check configuration applies in order - [x] Check if propagation times are acceptable ## Test report procedure All test results must have one of the following statuses: | | | |---------------------------------|--------------------------------------------| | :green_circle: | All checks passed. | | :red_circle: | There is at least one failed result. | | :yellow_circle: | There is at least one expected failure or skipped test and no failures. | ## Conclusions All tests have been executed and the results can be found in the issue updates. | **Status** | **Test** | **Failure type** | **Notes** | |----------------|-------------|---------------------|----------------| | :green_circle: | Installing the Wazuh manager, dashboard, and indexer | - | - | | :green_circle: | Test 1: Deploy an agent on version 4.4.0 and set it to a group upon deployment | - | - | | :yellow_circle: | Test 2: Modifying configuration, adding agent to new groups. | Known issue | https://github.com/wazuh/wazuh-kibana-app/issues/5133 | ## Auditors validation The definition of done for this one is the validation of the conclusions and the test results from all auditors. All checks from below must be accepted in order to close this issue. - [x] @wazuh/binary-beasts - [x] @davidjiglesias
non_priority
release ux tests centralized configuration agent groups the following issue aims to run the specified test for the current release candidate report the results and open new issues for any encountered errors test information test name centralized configuration agent groups category configuration deployment option main release issue main ux test issue release candidate environment component os installation wazuh dashboard amazon linux wazuh indexer amazon linux wazuh server amazon linux wazuh agent windows wazuh wui one liner deploy ip group created beforehand test description test the functionality of agent groups for centralized configuration try different groups for different os try tags in the same group to apply different blocks of configuration to different os or agents try creating groups with different files of diferent types and sizes try to reach the limits try creating multigroups and add agents to them check configuration applies in order check if propagation times are acceptable test report procedure all test results must have one of the following statuses green circle all checks passed red circle there is at least one failed result yellow circle there is at least one expected failure or skipped test and no failures conclusions all tests have been executed and the results can be found in the issue updates status test failure type notes green circle installing the wazuh manager dashboard and indexer green circle test deploy an agent on version and set it to a group upon deployment yellow circle test modifying configuration adding agent to new groups known issue auditors validation the definition of done for this one is the validation of the conclusions and the test results from all auditors all checks from below must be accepted in order to close this issue wazuh binary beasts davidjiglesias
0
198,687
22,669,245,760
IssuesEvent
2022-07-03 11:09:06
TIBCOSoftware/js-workshops
https://api.github.com/repos/TIBCOSoftware/js-workshops
opened
CVE-2022-25758 (Medium) detected in scss-tokenizer-0.2.3.tgz
security vulnerability
## CVE-2022-25758 - Medium Severity Vulnerability <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>scss-tokenizer-0.2.3.tgz</b></p></summary> <p>A tokenzier for Sass' SCSS syntax</p> <p>Library home page: <a href="https://registry.npmjs.org/scss-tokenizer/-/scss-tokenizer-0.2.3.tgz">https://registry.npmjs.org/scss-tokenizer/-/scss-tokenizer-0.2.3.tgz</a></p> <p>Path to dependency file: /UrbanRoast-tutorial/resources/d3-funnel-master/package.json</p> <p>Path to vulnerable library: /UrbanRoast-tutorial/resources/d3-funnel-master/node_modules/scss-tokenizer/package.json</p> <p> Dependency Hierarchy: - gulp-sass-3.2.1.tgz (Root Library) - node-sass-4.12.0.tgz - sass-graph-2.2.4.tgz - :x: **scss-tokenizer-0.2.3.tgz** (Vulnerable Library) </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary> <p> All versions of package scss-tokenizer are vulnerable to Regular Expression Denial of Service (ReDoS) via the loadAnnotation() function, due to the usage of insecure regex. <p>Publish Date: 2022-07-01 <p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-25758>CVE-2022-25758</a></p> </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.3</b>)</summary> <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: None - Integrity Impact: None - Availability Impact: Low </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> </details> <p></p>
True
CVE-2022-25758 (Medium) detected in scss-tokenizer-0.2.3.tgz - ## CVE-2022-25758 - Medium Severity Vulnerability <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>scss-tokenizer-0.2.3.tgz</b></p></summary> <p>A tokenzier for Sass' SCSS syntax</p> <p>Library home page: <a href="https://registry.npmjs.org/scss-tokenizer/-/scss-tokenizer-0.2.3.tgz">https://registry.npmjs.org/scss-tokenizer/-/scss-tokenizer-0.2.3.tgz</a></p> <p>Path to dependency file: /UrbanRoast-tutorial/resources/d3-funnel-master/package.json</p> <p>Path to vulnerable library: /UrbanRoast-tutorial/resources/d3-funnel-master/node_modules/scss-tokenizer/package.json</p> <p> Dependency Hierarchy: - gulp-sass-3.2.1.tgz (Root Library) - node-sass-4.12.0.tgz - sass-graph-2.2.4.tgz - :x: **scss-tokenizer-0.2.3.tgz** (Vulnerable Library) </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary> <p> All versions of package scss-tokenizer are vulnerable to Regular Expression Denial of Service (ReDoS) via the loadAnnotation() function, due to the usage of insecure regex. <p>Publish Date: 2022-07-01 <p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-25758>CVE-2022-25758</a></p> </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.3</b>)</summary> <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: None - Integrity Impact: None - Availability Impact: Low </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> </details> <p></p>
non_priority
cve medium detected in scss tokenizer tgz cve medium severity vulnerability vulnerable library scss tokenizer tgz a tokenzier for sass scss syntax library home page a href path to dependency file urbanroast tutorial resources funnel master package json path to vulnerable library urbanroast tutorial resources funnel master node modules scss tokenizer package json dependency hierarchy gulp sass tgz root library node sass tgz sass graph tgz x scss tokenizer tgz vulnerable library vulnerability details all versions of package scss tokenizer are vulnerable to regular expression denial of service redos via the loadannotation function due to the usage of insecure regex publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact none integrity impact none availability impact low for more information on scores click a href
0
215,784
16,617,243,911
IssuesEvent
2021-06-02 18:22:52
xnd-project/rbc
https://api.github.com/repos/xnd-project/rbc
closed
Document the usage of ColumnList attributes.
documentation
Hi Pearu, can you write some docs as well explaining how to use and internal attributes about ColumnList? You can put those under `doc/` folder. Don't worry if the docs don't build as expected, I can fix them in another PR. _Originally posted by @guilhermeleobas in https://github.com/xnd-project/rbc/issues/306#issuecomment-799621838_
1.0
Document the usage of ColumnList attributes. - Hi Pearu, can you write some docs as well explaining how to use and internal attributes about ColumnList? You can put those under `doc/` folder. Don't worry if the docs don't build as expected, I can fix them in another PR. _Originally posted by @guilhermeleobas in https://github.com/xnd-project/rbc/issues/306#issuecomment-799621838_
non_priority
document the usage of columnlist attributes hi pearu can you write some docs as well explaining how to use and internal attributes about columnlist you can put those under doc folder don t worry if the docs don t build as expected i can fix them in another pr originally posted by guilhermeleobas in
0
220,706
24,565,385,287
IssuesEvent
2022-10-13 02:10:40
alpersonalwebsite/react-state-fetch
https://api.github.com/repos/alpersonalwebsite/react-state-fetch
closed
CVE-2021-33587 (High) detected in css-what-3.4.2.tgz - autoclosed
security vulnerability
## CVE-2021-33587 - High Severity Vulnerability <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>css-what-3.4.2.tgz</b></p></summary> <p>a CSS selector parser</p> <p>Library home page: <a href="https://registry.npmjs.org/css-what/-/css-what-3.4.2.tgz">https://registry.npmjs.org/css-what/-/css-what-3.4.2.tgz</a></p> <p>Path to dependency file: /package.json</p> <p>Path to vulnerable library: /node_modules/svgo/node_modules/css-what/package.json</p> <p> Dependency Hierarchy: - react-scripts-3.3.0.tgz (Root Library) - webpack-4.3.3.tgz - plugin-svgo-4.3.1.tgz - svgo-1.3.2.tgz - css-select-2.1.0.tgz - :x: **css-what-3.4.2.tgz** (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/alpersonalwebsite/react-state-fetch/commit/64d27f11d528412fa673f060b1b6aca55ce44a95">64d27f11d528412fa673f060b1b6aca55ce44a95</a></p> <p>Found in base branch: <b>master</b></p> </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary> <p> The css-what package 4.0.0 through 5.0.0 for Node.js does not ensure that attribute parsing has Linear Time Complexity relative to the size of the input. <p>Publish Date: 2021-05-28 <p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-33587>CVE-2021-33587</a></p> </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary> <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: None - Integrity Impact: None - Availability Impact: High </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary> <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-33587">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-33587</a></p> <p>Release Date: 2021-05-28</p> <p>Fix Resolution (css-what): 5.0.1</p> <p>Direct dependency fix Resolution (react-scripts): 5.0.1</p> </p> </details> <p></p> *** Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
True
CVE-2021-33587 (High) detected in css-what-3.4.2.tgz - autoclosed - ## CVE-2021-33587 - High Severity Vulnerability <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>css-what-3.4.2.tgz</b></p></summary> <p>a CSS selector parser</p> <p>Library home page: <a href="https://registry.npmjs.org/css-what/-/css-what-3.4.2.tgz">https://registry.npmjs.org/css-what/-/css-what-3.4.2.tgz</a></p> <p>Path to dependency file: /package.json</p> <p>Path to vulnerable library: /node_modules/svgo/node_modules/css-what/package.json</p> <p> Dependency Hierarchy: - react-scripts-3.3.0.tgz (Root Library) - webpack-4.3.3.tgz - plugin-svgo-4.3.1.tgz - svgo-1.3.2.tgz - css-select-2.1.0.tgz - :x: **css-what-3.4.2.tgz** (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/alpersonalwebsite/react-state-fetch/commit/64d27f11d528412fa673f060b1b6aca55ce44a95">64d27f11d528412fa673f060b1b6aca55ce44a95</a></p> <p>Found in base branch: <b>master</b></p> </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary> <p> The css-what package 4.0.0 through 5.0.0 for Node.js does not ensure that attribute parsing has Linear Time Complexity relative to the size of the input. <p>Publish Date: 2021-05-28 <p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-33587>CVE-2021-33587</a></p> </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary> <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: None - Integrity Impact: None - Availability Impact: High </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary> <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-33587">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-33587</a></p> <p>Release Date: 2021-05-28</p> <p>Fix Resolution (css-what): 5.0.1</p> <p>Direct dependency fix Resolution (react-scripts): 5.0.1</p> </p> </details> <p></p> *** Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
non_priority
cve high detected in css what tgz autoclosed cve high severity vulnerability vulnerable library css what tgz a css selector parser library home page a href path to dependency file package json path to vulnerable library node modules svgo node modules css what package json dependency hierarchy react scripts tgz root library webpack tgz plugin svgo tgz svgo tgz css select tgz x css what tgz vulnerable library found in head commit a href found in base branch master vulnerability details the css what package through for node js does not ensure that attribute parsing has linear time complexity relative to the size of the input 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 css what direct dependency fix resolution react scripts step up your open source security game with mend
0
92,109
11,609,798,623
IssuesEvent
2020-02-26 01:07:05
dev-launchers/platform__website
https://api.github.com/repos/dev-launchers/platform__website
opened
Learn Page: GitHub/Git resources to help students understand Git and GitHub
content-curation help wanted opinions wanted ux design
**Is your feature request related to a problem? Please describe.** Git and GitHub are complicated topics, and it would be nice to have a structured solution to helping students understand core concepts related to both. **Describe the solution you'd like** We'd like to implement a new tab or section with easily approachable activities or explanations, which will guide the students through understanding the core concepts of Git and GitHub. Right now, it seems best to create this in a separate tab on the Learn Page, and then in the future add a better way to create subcategories in our current tab system. Some possible resources we've been provided are: - https://www.youtube.com/watch?v=nhNq2kIvi9s - https://education.github.com/git-cheat-sheet-education.pdf - https://www.youtube.com/watch?v=0fKg7e37bQE - https://www.notion.so/Introduction-to-GitHub-202af6f64bbd4299b15f238dcd09d2a7 However, none of these resources are perfectly digestible/engaging for our teen students. **It would be nice to have these broken down into different sections we can place on individual cards on our page, so that the students will be able to tackle them in bite sized pieces** The last link in that list might be our best bet, if we're able to break out links to individual sections in the article. *Other suggestions to tackling this are very welcome!* The most important concepts students should be familiar with in order to begin working on their projects are: - Beginner: - Viewing their code on GitHub - General reasons to use version control - How the repo system works (local vs remote and changes to each) - Committing/Pushing - Intermediate: - Fetching/Pulling - Branches - Collaborating on GitHub - Pull Requests - Merging Branches/Conflicts To get them started, just those things in the beginner section should help them work in the environment we're using to create their projects. *We're using CodeSandbox to introduce students to Git/GitHub, which has a very limited feature set. If possible, the best solution would be structured to teach most of these concepts through CodeSandbox!* All modifications to the Learn Page can be done using the spreadsheet located at: https://docs.google.com/spreadsheets/d/1QV419fM2DHZM59mFK6eYYbYiq6bs4sBUpTwVZ_dZJNg/edit#gid=815710842 If you'd like to make changes to the sheet, please request access here!
1.0
Learn Page: GitHub/Git resources to help students understand Git and GitHub - **Is your feature request related to a problem? Please describe.** Git and GitHub are complicated topics, and it would be nice to have a structured solution to helping students understand core concepts related to both. **Describe the solution you'd like** We'd like to implement a new tab or section with easily approachable activities or explanations, which will guide the students through understanding the core concepts of Git and GitHub. Right now, it seems best to create this in a separate tab on the Learn Page, and then in the future add a better way to create subcategories in our current tab system. Some possible resources we've been provided are: - https://www.youtube.com/watch?v=nhNq2kIvi9s - https://education.github.com/git-cheat-sheet-education.pdf - https://www.youtube.com/watch?v=0fKg7e37bQE - https://www.notion.so/Introduction-to-GitHub-202af6f64bbd4299b15f238dcd09d2a7 However, none of these resources are perfectly digestible/engaging for our teen students. **It would be nice to have these broken down into different sections we can place on individual cards on our page, so that the students will be able to tackle them in bite sized pieces** The last link in that list might be our best bet, if we're able to break out links to individual sections in the article. *Other suggestions to tackling this are very welcome!* The most important concepts students should be familiar with in order to begin working on their projects are: - Beginner: - Viewing their code on GitHub - General reasons to use version control - How the repo system works (local vs remote and changes to each) - Committing/Pushing - Intermediate: - Fetching/Pulling - Branches - Collaborating on GitHub - Pull Requests - Merging Branches/Conflicts To get them started, just those things in the beginner section should help them work in the environment we're using to create their projects. *We're using CodeSandbox to introduce students to Git/GitHub, which has a very limited feature set. If possible, the best solution would be structured to teach most of these concepts through CodeSandbox!* All modifications to the Learn Page can be done using the spreadsheet located at: https://docs.google.com/spreadsheets/d/1QV419fM2DHZM59mFK6eYYbYiq6bs4sBUpTwVZ_dZJNg/edit#gid=815710842 If you'd like to make changes to the sheet, please request access here!
non_priority
learn page github git resources to help students understand git and github is your feature request related to a problem please describe git and github are complicated topics and it would be nice to have a structured solution to helping students understand core concepts related to both describe the solution you d like we d like to implement a new tab or section with easily approachable activities or explanations which will guide the students through understanding the core concepts of git and github right now it seems best to create this in a separate tab on the learn page and then in the future add a better way to create subcategories in our current tab system some possible resources we ve been provided are however none of these resources are perfectly digestible engaging for our teen students it would be nice to have these broken down into different sections we can place on individual cards on our page so that the students will be able to tackle them in bite sized pieces the last link in that list might be our best bet if we re able to break out links to individual sections in the article other suggestions to tackling this are very welcome the most important concepts students should be familiar with in order to begin working on their projects are beginner viewing their code on github general reasons to use version control how the repo system works local vs remote and changes to each committing pushing intermediate fetching pulling branches collaborating on github pull requests merging branches conflicts to get them started just those things in the beginner section should help them work in the environment we re using to create their projects we re using codesandbox to introduce students to git github which has a very limited feature set if possible the best solution would be structured to teach most of these concepts through codesandbox all modifications to the learn page can be done using the spreadsheet located at if you d like to make changes to the sheet please request access here
0
374,949
26,140,547,708
IssuesEvent
2022-12-29 17:46:23
appsmithorg/appsmith-docs
https://api.github.com/repos/appsmithorg/appsmith-docs
opened
[Docs]: Dynamic Menu Items - Table Widget
Documentation Enhancement App Viewers Pod Table Widget V2 User Education Pod
### Is there an existing issue for this? - [X] I have searched the existing issues ### Engineering Ticket Link https://github.com/appsmithorg/appsmith/issues/17955 ### Release Date Will merge to release possibly by 30 Dec, 2022 ### Release Number - ### First Draft _No response_ ### Loom video _No response_ ### Discord/slack/intercom Link if needed _No response_ ### PRD _No response_ ### Test plan/cases _No response_ ### Use cases or user requests PR here - https://github.com/appsmithorg/appsmith/pull/18945 This feature allows users to use dynamic menu items (same as menu button widget) in Menu Button Column Type inside the Table Widget.
1.0
[Docs]: Dynamic Menu Items - Table Widget - ### Is there an existing issue for this? - [X] I have searched the existing issues ### Engineering Ticket Link https://github.com/appsmithorg/appsmith/issues/17955 ### Release Date Will merge to release possibly by 30 Dec, 2022 ### Release Number - ### First Draft _No response_ ### Loom video _No response_ ### Discord/slack/intercom Link if needed _No response_ ### PRD _No response_ ### Test plan/cases _No response_ ### Use cases or user requests PR here - https://github.com/appsmithorg/appsmith/pull/18945 This feature allows users to use dynamic menu items (same as menu button widget) in Menu Button Column Type inside the Table Widget.
non_priority
dynamic menu items table widget is there an existing issue for this i have searched the existing issues engineering ticket link release date will merge to release possibly by dec release number first draft no response loom video no response discord slack intercom link if needed no response prd no response test plan cases no response use cases or user requests pr here this feature allows users to use dynamic menu items same as menu button widget in menu button column type inside the table widget
0
83,626
7,877,228,750
IssuesEvent
2018-06-26 06:04:25
reposense/RepoSense
https://api.github.com/repos/reposense/RepoSense
closed
Redirect functional test to use testrepo
a-Testing p.Medium
Functional is performing the test on repositories that are beyond our control. This means that if the repositories' owners make any changes to their repository, it will affect our test results. Let's use the state-preserved, forked repositories under our organization instead.
1.0
Redirect functional test to use testrepo - Functional is performing the test on repositories that are beyond our control. This means that if the repositories' owners make any changes to their repository, it will affect our test results. Let's use the state-preserved, forked repositories under our organization instead.
non_priority
redirect functional test to use testrepo functional is performing the test on repositories that are beyond our control this means that if the repositories owners make any changes to their repository it will affect our test results let s use the state preserved forked repositories under our organization instead
0
33,669
27,701,113,700
IssuesEvent
2023-03-14 08:05:24
lablup/backend.ai
https://api.github.com/repos/lablup/backend.ai
closed
Fix conda-pack workflow and adjust the workflow step dependencies
bug infrastructure enhance
https://github.com/lablup/backend.ai/actions/runs/4334482265/jobs/7568438532#step:8:22 Currently, the default workflow is like: <img width="682" alt="image" src="https://user-images.githubusercontent.com/555156/222956183-67c0b1a1-967c-44ec-908c-57f92016e350.png"> Let's change it like: <img width="682" alt="image" src="https://user-images.githubusercontent.com/555156/222956859-ed2fc841-5c20-48e1-8560-425539781e30.png"> so that any failures in the conda-pack step do not interrupt the original Linux wheel build and deployment. Also rename the `windows-conda-pack` step to `build-conda-pack-for-windows` to keep the consistency with the verb tense.
1.0
Fix conda-pack workflow and adjust the workflow step dependencies - https://github.com/lablup/backend.ai/actions/runs/4334482265/jobs/7568438532#step:8:22 Currently, the default workflow is like: <img width="682" alt="image" src="https://user-images.githubusercontent.com/555156/222956183-67c0b1a1-967c-44ec-908c-57f92016e350.png"> Let's change it like: <img width="682" alt="image" src="https://user-images.githubusercontent.com/555156/222956859-ed2fc841-5c20-48e1-8560-425539781e30.png"> so that any failures in the conda-pack step do not interrupt the original Linux wheel build and deployment. Also rename the `windows-conda-pack` step to `build-conda-pack-for-windows` to keep the consistency with the verb tense.
non_priority
fix conda pack workflow and adjust the workflow step dependencies currently the default workflow is like img width alt image src let s change it like img width alt image src so that any failures in the conda pack step do not interrupt the original linux wheel build and deployment also rename the windows conda pack step to build conda pack for windows to keep the consistency with the verb tense
0
131,651
27,996,094,600
IssuesEvent
2023-03-27 08:34:44
SAST-org/SAST-Test-Repo-d4e44d54-764b-4268-80e1-5f3933690b00
https://api.github.com/repos/SAST-org/SAST-Test-Repo-d4e44d54-764b-4268-80e1-5f3933690b00
opened
Code Security Report: 3 high severity findings, 10 total findings
Mend: code security findings
# Code Security Report ### Scan Metadata **Latest Scan:** 2023-03-27 08:34am **Total Findings:** 10 | **New Findings:** 0 | **Resolved Findings:** 0 **Tested Project Files:** 117 **Detected Programming Languages:** 2 (Python, JavaScript / Node.js) <!-- SAST-MANUAL-SCAN-START --> - [ ] Check this box to manually trigger a scan <!-- SAST-MANUAL-SCAN-END --> ### Finding Details <table role='table'><thead><tr><th>Severity</th><th>Vulnerability Type</th><th>CWE</th><th>File</th><th>Data Flows</th><th>Date</th></tr></thead><tbody><tr><td><a href='#'><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20></a> High</td><td>SQL Injection</td><td> [CWE-89](https://cwe.mitre.org/data/definitions/89.html) </td><td> [libuser.py:53](https://github.com/SAST-org/SAST-Test-Repo-d4e44d54-764b-4268-80e1-5f3933690b00/blob/8e3cf1fe70cf1ff48e42de7bad31cf6407ddbeb7/bad/libuser.py#L53) </td><td>2</td><td>2023-03-27 08:34am</td></tr><tr><td colspan='6'><details><summary>More info</summary> https://github.com/SAST-org/SAST-Test-Repo-d4e44d54-764b-4268-80e1-5f3933690b00/blob/8e3cf1fe70cf1ff48e42de7bad31cf6407ddbeb7/bad/libuser.py#L48-L53 <details> <summary>2 Data Flow/s detected</summary></br> <details> <summary>View Data Flow 1</summary> https://github.com/SAST-org/SAST-Test-Repo-d4e44d54-764b-4268-80e1-5f3933690b00/blob/8e3cf1fe70cf1ff48e42de7bad31cf6407ddbeb7/bad/mod_user.py#L69 https://github.com/SAST-org/SAST-Test-Repo-d4e44d54-764b-4268-80e1-5f3933690b00/blob/8e3cf1fe70cf1ff48e42de7bad31cf6407ddbeb7/bad/mod_user.py#L69 https://github.com/SAST-org/SAST-Test-Repo-d4e44d54-764b-4268-80e1-5f3933690b00/blob/8e3cf1fe70cf1ff48e42de7bad31cf6407ddbeb7/bad/libuser.py#L46 https://github.com/SAST-org/SAST-Test-Repo-d4e44d54-764b-4268-80e1-5f3933690b00/blob/8e3cf1fe70cf1ff48e42de7bad31cf6407ddbeb7/bad/libuser.py#L53 </details> <details> <summary>View Data Flow 2</summary> https://github.com/SAST-org/SAST-Test-Repo-d4e44d54-764b-4268-80e1-5f3933690b00/blob/8e3cf1fe70cf1ff48e42de7bad31cf6407ddbeb7/bad/mod_user.py#L69 https://github.com/SAST-org/SAST-Test-Repo-d4e44d54-764b-4268-80e1-5f3933690b00/blob/8e3cf1fe70cf1ff48e42de7bad31cf6407ddbeb7/bad/mod_user.py#L69 https://github.com/SAST-org/SAST-Test-Repo-d4e44d54-764b-4268-80e1-5f3933690b00/blob/8e3cf1fe70cf1ff48e42de7bad31cf6407ddbeb7/bad/libuser.py#L46 https://github.com/SAST-org/SAST-Test-Repo-d4e44d54-764b-4268-80e1-5f3933690b00/blob/8e3cf1fe70cf1ff48e42de7bad31cf6407ddbeb7/bad/libuser.py#L53 </details> </details> </td></tr></details></td></tr><tr><td><a href='#'><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20></a> High</td><td>SQL Injection</td><td> [CWE-89](https://cwe.mitre.org/data/definitions/89.html) </td><td> [libuser.py:25](https://github.com/SAST-org/SAST-Test-Repo-d4e44d54-764b-4268-80e1-5f3933690b00/blob/8e3cf1fe70cf1ff48e42de7bad31cf6407ddbeb7/bad/libuser.py#L25) </td><td>12</td><td>2023-03-27 08:34am</td></tr><tr><td colspan='6'><details><summary>More info</summary> https://github.com/SAST-org/SAST-Test-Repo-d4e44d54-764b-4268-80e1-5f3933690b00/blob/8e3cf1fe70cf1ff48e42de7bad31cf6407ddbeb7/bad/libuser.py#L20-L25 <details> <summary>12 Data Flow/s detected</summary></br> <details> <summary>View Data Flow 1</summary> https://github.com/SAST-org/SAST-Test-Repo-d4e44d54-764b-4268-80e1-5f3933690b00/blob/8e3cf1fe70cf1ff48e42de7bad31cf6407ddbeb7/bad/mod_user.py#L46 https://github.com/SAST-org/SAST-Test-Repo-d4e44d54-764b-4268-80e1-5f3933690b00/blob/8e3cf1fe70cf1ff48e42de7bad31cf6407ddbeb7/bad/mod_user.py#L46 https://github.com/SAST-org/SAST-Test-Repo-d4e44d54-764b-4268-80e1-5f3933690b00/blob/8e3cf1fe70cf1ff48e42de7bad31cf6407ddbeb7/bad/libuser.py#L20 https://github.com/SAST-org/SAST-Test-Repo-d4e44d54-764b-4268-80e1-5f3933690b00/blob/8e3cf1fe70cf1ff48e42de7bad31cf6407ddbeb7/bad/libuser.py#L25 </details> <details> <summary>View Data Flow 2</summary> https://github.com/SAST-org/SAST-Test-Repo-d4e44d54-764b-4268-80e1-5f3933690b00/blob/8e3cf1fe70cf1ff48e42de7bad31cf6407ddbeb7/bad/mod_user.py#L46 https://github.com/SAST-org/SAST-Test-Repo-d4e44d54-764b-4268-80e1-5f3933690b00/blob/8e3cf1fe70cf1ff48e42de7bad31cf6407ddbeb7/bad/mod_user.py#L46 https://github.com/SAST-org/SAST-Test-Repo-d4e44d54-764b-4268-80e1-5f3933690b00/blob/8e3cf1fe70cf1ff48e42de7bad31cf6407ddbeb7/bad/libuser.py#L20 https://github.com/SAST-org/SAST-Test-Repo-d4e44d54-764b-4268-80e1-5f3933690b00/blob/8e3cf1fe70cf1ff48e42de7bad31cf6407ddbeb7/bad/libuser.py#L25 </details> <details> <summary>View Data Flow 3</summary> https://github.com/SAST-org/SAST-Test-Repo-d4e44d54-764b-4268-80e1-5f3933690b00/blob/8e3cf1fe70cf1ff48e42de7bad31cf6407ddbeb7/bad/mod_user.py#L45 https://github.com/SAST-org/SAST-Test-Repo-d4e44d54-764b-4268-80e1-5f3933690b00/blob/8e3cf1fe70cf1ff48e42de7bad31cf6407ddbeb7/bad/mod_user.py#L45 https://github.com/SAST-org/SAST-Test-Repo-d4e44d54-764b-4268-80e1-5f3933690b00/blob/8e3cf1fe70cf1ff48e42de7bad31cf6407ddbeb7/bad/libuser.py#L20 https://github.com/SAST-org/SAST-Test-Repo-d4e44d54-764b-4268-80e1-5f3933690b00/blob/8e3cf1fe70cf1ff48e42de7bad31cf6407ddbeb7/bad/libuser.py#L25 </details> [View more Data Flows](https://dev.whitesourcesoftware.com/sast/#/scans/b7bee5de-7dbb-4b0d-87aa-f257d07de53d/details?vulnId=7491777b-898a-41fe-b4bf-d0cc2c916a2b&filtered=yes) </details> </td></tr></details></td></tr><tr><td><a href='#'><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20></a> High</td><td>SQL Injection</td><td> [CWE-89](https://cwe.mitre.org/data/definitions/89.html) </td><td> [libuser.py:12](https://github.com/SAST-org/SAST-Test-Repo-d4e44d54-764b-4268-80e1-5f3933690b00/blob/8e3cf1fe70cf1ff48e42de7bad31cf6407ddbeb7/bad/libuser.py#L12) </td><td>10</td><td>2023-03-27 08:34am</td></tr><tr><td colspan='6'><details><summary>More info</summary> https://github.com/SAST-org/SAST-Test-Repo-d4e44d54-764b-4268-80e1-5f3933690b00/blob/8e3cf1fe70cf1ff48e42de7bad31cf6407ddbeb7/bad/libuser.py#L7-L12 <details> <summary>10 Data Flow/s detected</summary></br> <details> <summary>View Data Flow 1</summary> https://github.com/SAST-org/SAST-Test-Repo-d4e44d54-764b-4268-80e1-5f3933690b00/blob/8e3cf1fe70cf1ff48e42de7bad31cf6407ddbeb7/bad/mod_user.py#L69 https://github.com/SAST-org/SAST-Test-Repo-d4e44d54-764b-4268-80e1-5f3933690b00/blob/8e3cf1fe70cf1ff48e42de7bad31cf6407ddbeb7/bad/mod_user.py#L69 https://github.com/SAST-org/SAST-Test-Repo-d4e44d54-764b-4268-80e1-5f3933690b00/blob/8e3cf1fe70cf1ff48e42de7bad31cf6407ddbeb7/bad/libuser.py#L5 https://github.com/SAST-org/SAST-Test-Repo-d4e44d54-764b-4268-80e1-5f3933690b00/blob/8e3cf1fe70cf1ff48e42de7bad31cf6407ddbeb7/bad/libuser.py#L12 </details> <details> <summary>View Data Flow 2</summary> https://github.com/SAST-org/SAST-Test-Repo-d4e44d54-764b-4268-80e1-5f3933690b00/blob/8e3cf1fe70cf1ff48e42de7bad31cf6407ddbeb7/bad/mod_user.py#L69 https://github.com/SAST-org/SAST-Test-Repo-d4e44d54-764b-4268-80e1-5f3933690b00/blob/8e3cf1fe70cf1ff48e42de7bad31cf6407ddbeb7/bad/mod_user.py#L69 https://github.com/SAST-org/SAST-Test-Repo-d4e44d54-764b-4268-80e1-5f3933690b00/blob/8e3cf1fe70cf1ff48e42de7bad31cf6407ddbeb7/bad/libuser.py#L5 https://github.com/SAST-org/SAST-Test-Repo-d4e44d54-764b-4268-80e1-5f3933690b00/blob/8e3cf1fe70cf1ff48e42de7bad31cf6407ddbeb7/bad/libuser.py#L12 </details> <details> <summary>View Data Flow 3</summary> https://github.com/SAST-org/SAST-Test-Repo-d4e44d54-764b-4268-80e1-5f3933690b00/blob/8e3cf1fe70cf1ff48e42de7bad31cf6407ddbeb7/bad/mod_user.py#L17 https://github.com/SAST-org/SAST-Test-Repo-d4e44d54-764b-4268-80e1-5f3933690b00/blob/8e3cf1fe70cf1ff48e42de7bad31cf6407ddbeb7/bad/mod_user.py#L17 https://github.com/SAST-org/SAST-Test-Repo-d4e44d54-764b-4268-80e1-5f3933690b00/blob/8e3cf1fe70cf1ff48e42de7bad31cf6407ddbeb7/bad/libuser.py#L5 https://github.com/SAST-org/SAST-Test-Repo-d4e44d54-764b-4268-80e1-5f3933690b00/blob/8e3cf1fe70cf1ff48e42de7bad31cf6407ddbeb7/bad/libuser.py#L12 </details> [View more Data Flows](https://dev.whitesourcesoftware.com/sast/#/scans/b7bee5de-7dbb-4b0d-87aa-f257d07de53d/details?vulnId=3fd361d2-a7a0-46d2-b03d-9c93b496b144&filtered=yes) </details> </td></tr></details></td></tr><tr><td><a href='#'><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20></a> Medium</td><td>Hardcoded Password/Credentials</td><td> [CWE-798](https://cwe.mitre.org/data/definitions/798.html) </td><td> [libuser.py:12](https://github.com/SAST-org/SAST-Test-Repo-d4e44d54-764b-4268-80e1-5f3933690b00/blob/8e3cf1fe70cf1ff48e42de7bad31cf6407ddbeb7/bad/libuser.py#L12) </td><td>1</td><td>2023-03-27 08:34am</td></tr><tr><td colspan='6'><details><summary>More info</summary> https://github.com/SAST-org/SAST-Test-Repo-d4e44d54-764b-4268-80e1-5f3933690b00/blob/8e3cf1fe70cf1ff48e42de7bad31cf6407ddbeb7/bad/libuser.py#L7-L12 <details> <summary>1 Data Flow/s detected</summary></br> <details> <summary>View Data Flow 1</summary> https://github.com/SAST-org/SAST-Test-Repo-d4e44d54-764b-4268-80e1-5f3933690b00/blob/8e3cf1fe70cf1ff48e42de7bad31cf6407ddbeb7/bad/libuser.py#L12 </details> </details> </td></tr></details></td></tr><tr><td><a href='#'><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20></a> Medium</td><td>Hardcoded Password/Credentials</td><td> [CWE-798](https://cwe.mitre.org/data/definitions/798.html) </td><td> [vulpy-ssl.py:13](https://github.com/SAST-org/SAST-Test-Repo-d4e44d54-764b-4268-80e1-5f3933690b00/blob/8e3cf1fe70cf1ff48e42de7bad31cf6407ddbeb7/good/vulpy-ssl.py#L13) </td><td>1</td><td>2023-03-27 08:34am</td></tr><tr><td colspan='6'><details><summary>More info</summary> https://github.com/SAST-org/SAST-Test-Repo-d4e44d54-764b-4268-80e1-5f3933690b00/blob/8e3cf1fe70cf1ff48e42de7bad31cf6407ddbeb7/good/vulpy-ssl.py#L8-L13 <details> <summary>1 Data Flow/s detected</summary></br> <details> <summary>View Data Flow 1</summary> https://github.com/SAST-org/SAST-Test-Repo-d4e44d54-764b-4268-80e1-5f3933690b00/blob/8e3cf1fe70cf1ff48e42de7bad31cf6407ddbeb7/good/vulpy-ssl.py#L13 </details> </details> </td></tr></details></td></tr><tr><td><a href='#'><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20></a> Medium</td><td>Hardcoded Password/Credentials</td><td> [CWE-798](https://cwe.mitre.org/data/definitions/798.html) </td><td> [libapi.py:10](https://github.com/SAST-org/SAST-Test-Repo-d4e44d54-764b-4268-80e1-5f3933690b00/blob/8e3cf1fe70cf1ff48e42de7bad31cf6407ddbeb7/good/libapi.py#L10) </td><td>1</td><td>2023-03-27 08:34am</td></tr><tr><td colspan='6'><details><summary>More info</summary> https://github.com/SAST-org/SAST-Test-Repo-d4e44d54-764b-4268-80e1-5f3933690b00/blob/8e3cf1fe70cf1ff48e42de7bad31cf6407ddbeb7/good/libapi.py#L5-L10 <details> <summary>1 Data Flow/s detected</summary></br> <details> <summary>View Data Flow 1</summary> https://github.com/SAST-org/SAST-Test-Repo-d4e44d54-764b-4268-80e1-5f3933690b00/blob/8e3cf1fe70cf1ff48e42de7bad31cf6407ddbeb7/good/libapi.py#L10 </details> </details> </td></tr></details></td></tr><tr><td><a href='#'><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20></a> Medium</td><td>Hardcoded Password/Credentials</td><td> [CWE-798](https://cwe.mitre.org/data/definitions/798.html) </td><td> [vulpy.py:17](https://github.com/SAST-org/SAST-Test-Repo-d4e44d54-764b-4268-80e1-5f3933690b00/blob/8e3cf1fe70cf1ff48e42de7bad31cf6407ddbeb7/good/vulpy.py#L17) </td><td>1</td><td>2023-03-27 08:34am</td></tr><tr><td colspan='6'><details><summary>More info</summary> https://github.com/SAST-org/SAST-Test-Repo-d4e44d54-764b-4268-80e1-5f3933690b00/blob/8e3cf1fe70cf1ff48e42de7bad31cf6407ddbeb7/good/vulpy.py#L12-L17 <details> <summary>1 Data Flow/s detected</summary></br> <details> <summary>View Data Flow 1</summary> https://github.com/SAST-org/SAST-Test-Repo-d4e44d54-764b-4268-80e1-5f3933690b00/blob/8e3cf1fe70cf1ff48e42de7bad31cf6407ddbeb7/good/vulpy.py#L17 </details> </details> </td></tr></details></td></tr><tr><td><a href='#'><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20></a> Medium</td><td>Hardcoded Password/Credentials</td><td> [CWE-798](https://cwe.mitre.org/data/definitions/798.html) </td><td> [vulpy.py:16](https://github.com/SAST-org/SAST-Test-Repo-d4e44d54-764b-4268-80e1-5f3933690b00/blob/8e3cf1fe70cf1ff48e42de7bad31cf6407ddbeb7/bad/vulpy.py#L16) </td><td>1</td><td>2023-03-27 08:34am</td></tr><tr><td colspan='6'><details><summary>More info</summary> https://github.com/SAST-org/SAST-Test-Repo-d4e44d54-764b-4268-80e1-5f3933690b00/blob/8e3cf1fe70cf1ff48e42de7bad31cf6407ddbeb7/bad/vulpy.py#L11-L16 <details> <summary>1 Data Flow/s detected</summary></br> <details> <summary>View Data Flow 1</summary> https://github.com/SAST-org/SAST-Test-Repo-d4e44d54-764b-4268-80e1-5f3933690b00/blob/8e3cf1fe70cf1ff48e42de7bad31cf6407ddbeb7/bad/vulpy.py#L16 </details> </details> </td></tr></details></td></tr><tr><td><a href='#'><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20></a> Medium</td><td>Hardcoded Password/Credentials</td><td> [CWE-798](https://cwe.mitre.org/data/definitions/798.html) </td><td> [vulpy-ssl.py:13](https://github.com/SAST-org/SAST-Test-Repo-d4e44d54-764b-4268-80e1-5f3933690b00/blob/8e3cf1fe70cf1ff48e42de7bad31cf6407ddbeb7/bad/vulpy-ssl.py#L13) </td><td>1</td><td>2023-03-27 08:34am</td></tr><tr><td colspan='6'><details><summary>More info</summary> https://github.com/SAST-org/SAST-Test-Repo-d4e44d54-764b-4268-80e1-5f3933690b00/blob/8e3cf1fe70cf1ff48e42de7bad31cf6407ddbeb7/bad/vulpy-ssl.py#L8-L13 <details> <summary>1 Data Flow/s detected</summary></br> <details> <summary>View Data Flow 1</summary> https://github.com/SAST-org/SAST-Test-Repo-d4e44d54-764b-4268-80e1-5f3933690b00/blob/8e3cf1fe70cf1ff48e42de7bad31cf6407ddbeb7/bad/vulpy-ssl.py#L13 </details> </details> </td></tr></details></td></tr><tr><td><a href='#'><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20></a> Medium</td><td>Hardcoded Password/Credentials</td><td> [CWE-798](https://cwe.mitre.org/data/definitions/798.html) </td><td> [libuser.py:53](https://github.com/SAST-org/SAST-Test-Repo-d4e44d54-764b-4268-80e1-5f3933690b00/blob/8e3cf1fe70cf1ff48e42de7bad31cf6407ddbeb7/bad/libuser.py#L53) </td><td>1</td><td>2023-03-27 08:34am</td></tr><tr><td colspan='6'><details><summary>More info</summary> https://github.com/SAST-org/SAST-Test-Repo-d4e44d54-764b-4268-80e1-5f3933690b00/blob/8e3cf1fe70cf1ff48e42de7bad31cf6407ddbeb7/bad/libuser.py#L48-L53 <details> <summary>1 Data Flow/s detected</summary></br> <details> <summary>View Data Flow 1</summary> https://github.com/SAST-org/SAST-Test-Repo-d4e44d54-764b-4268-80e1-5f3933690b00/blob/8e3cf1fe70cf1ff48e42de7bad31cf6407ddbeb7/bad/libuser.py#L53 </details> </details> </td></tr></details></td></tr></tbody></table>
1.0
Code Security Report: 3 high severity findings, 10 total findings - # Code Security Report ### Scan Metadata **Latest Scan:** 2023-03-27 08:34am **Total Findings:** 10 | **New Findings:** 0 | **Resolved Findings:** 0 **Tested Project Files:** 117 **Detected Programming Languages:** 2 (Python, JavaScript / Node.js) <!-- SAST-MANUAL-SCAN-START --> - [ ] Check this box to manually trigger a scan <!-- SAST-MANUAL-SCAN-END --> ### Finding Details <table role='table'><thead><tr><th>Severity</th><th>Vulnerability Type</th><th>CWE</th><th>File</th><th>Data Flows</th><th>Date</th></tr></thead><tbody><tr><td><a href='#'><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20></a> High</td><td>SQL Injection</td><td> [CWE-89](https://cwe.mitre.org/data/definitions/89.html) </td><td> [libuser.py:53](https://github.com/SAST-org/SAST-Test-Repo-d4e44d54-764b-4268-80e1-5f3933690b00/blob/8e3cf1fe70cf1ff48e42de7bad31cf6407ddbeb7/bad/libuser.py#L53) </td><td>2</td><td>2023-03-27 08:34am</td></tr><tr><td colspan='6'><details><summary>More info</summary> https://github.com/SAST-org/SAST-Test-Repo-d4e44d54-764b-4268-80e1-5f3933690b00/blob/8e3cf1fe70cf1ff48e42de7bad31cf6407ddbeb7/bad/libuser.py#L48-L53 <details> <summary>2 Data Flow/s detected</summary></br> <details> <summary>View Data Flow 1</summary> https://github.com/SAST-org/SAST-Test-Repo-d4e44d54-764b-4268-80e1-5f3933690b00/blob/8e3cf1fe70cf1ff48e42de7bad31cf6407ddbeb7/bad/mod_user.py#L69 https://github.com/SAST-org/SAST-Test-Repo-d4e44d54-764b-4268-80e1-5f3933690b00/blob/8e3cf1fe70cf1ff48e42de7bad31cf6407ddbeb7/bad/mod_user.py#L69 https://github.com/SAST-org/SAST-Test-Repo-d4e44d54-764b-4268-80e1-5f3933690b00/blob/8e3cf1fe70cf1ff48e42de7bad31cf6407ddbeb7/bad/libuser.py#L46 https://github.com/SAST-org/SAST-Test-Repo-d4e44d54-764b-4268-80e1-5f3933690b00/blob/8e3cf1fe70cf1ff48e42de7bad31cf6407ddbeb7/bad/libuser.py#L53 </details> <details> <summary>View Data Flow 2</summary> https://github.com/SAST-org/SAST-Test-Repo-d4e44d54-764b-4268-80e1-5f3933690b00/blob/8e3cf1fe70cf1ff48e42de7bad31cf6407ddbeb7/bad/mod_user.py#L69 https://github.com/SAST-org/SAST-Test-Repo-d4e44d54-764b-4268-80e1-5f3933690b00/blob/8e3cf1fe70cf1ff48e42de7bad31cf6407ddbeb7/bad/mod_user.py#L69 https://github.com/SAST-org/SAST-Test-Repo-d4e44d54-764b-4268-80e1-5f3933690b00/blob/8e3cf1fe70cf1ff48e42de7bad31cf6407ddbeb7/bad/libuser.py#L46 https://github.com/SAST-org/SAST-Test-Repo-d4e44d54-764b-4268-80e1-5f3933690b00/blob/8e3cf1fe70cf1ff48e42de7bad31cf6407ddbeb7/bad/libuser.py#L53 </details> </details> </td></tr></details></td></tr><tr><td><a href='#'><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20></a> High</td><td>SQL Injection</td><td> [CWE-89](https://cwe.mitre.org/data/definitions/89.html) </td><td> [libuser.py:25](https://github.com/SAST-org/SAST-Test-Repo-d4e44d54-764b-4268-80e1-5f3933690b00/blob/8e3cf1fe70cf1ff48e42de7bad31cf6407ddbeb7/bad/libuser.py#L25) </td><td>12</td><td>2023-03-27 08:34am</td></tr><tr><td colspan='6'><details><summary>More info</summary> https://github.com/SAST-org/SAST-Test-Repo-d4e44d54-764b-4268-80e1-5f3933690b00/blob/8e3cf1fe70cf1ff48e42de7bad31cf6407ddbeb7/bad/libuser.py#L20-L25 <details> <summary>12 Data Flow/s detected</summary></br> <details> <summary>View Data Flow 1</summary> https://github.com/SAST-org/SAST-Test-Repo-d4e44d54-764b-4268-80e1-5f3933690b00/blob/8e3cf1fe70cf1ff48e42de7bad31cf6407ddbeb7/bad/mod_user.py#L46 https://github.com/SAST-org/SAST-Test-Repo-d4e44d54-764b-4268-80e1-5f3933690b00/blob/8e3cf1fe70cf1ff48e42de7bad31cf6407ddbeb7/bad/mod_user.py#L46 https://github.com/SAST-org/SAST-Test-Repo-d4e44d54-764b-4268-80e1-5f3933690b00/blob/8e3cf1fe70cf1ff48e42de7bad31cf6407ddbeb7/bad/libuser.py#L20 https://github.com/SAST-org/SAST-Test-Repo-d4e44d54-764b-4268-80e1-5f3933690b00/blob/8e3cf1fe70cf1ff48e42de7bad31cf6407ddbeb7/bad/libuser.py#L25 </details> <details> <summary>View Data Flow 2</summary> https://github.com/SAST-org/SAST-Test-Repo-d4e44d54-764b-4268-80e1-5f3933690b00/blob/8e3cf1fe70cf1ff48e42de7bad31cf6407ddbeb7/bad/mod_user.py#L46 https://github.com/SAST-org/SAST-Test-Repo-d4e44d54-764b-4268-80e1-5f3933690b00/blob/8e3cf1fe70cf1ff48e42de7bad31cf6407ddbeb7/bad/mod_user.py#L46 https://github.com/SAST-org/SAST-Test-Repo-d4e44d54-764b-4268-80e1-5f3933690b00/blob/8e3cf1fe70cf1ff48e42de7bad31cf6407ddbeb7/bad/libuser.py#L20 https://github.com/SAST-org/SAST-Test-Repo-d4e44d54-764b-4268-80e1-5f3933690b00/blob/8e3cf1fe70cf1ff48e42de7bad31cf6407ddbeb7/bad/libuser.py#L25 </details> <details> <summary>View Data Flow 3</summary> https://github.com/SAST-org/SAST-Test-Repo-d4e44d54-764b-4268-80e1-5f3933690b00/blob/8e3cf1fe70cf1ff48e42de7bad31cf6407ddbeb7/bad/mod_user.py#L45 https://github.com/SAST-org/SAST-Test-Repo-d4e44d54-764b-4268-80e1-5f3933690b00/blob/8e3cf1fe70cf1ff48e42de7bad31cf6407ddbeb7/bad/mod_user.py#L45 https://github.com/SAST-org/SAST-Test-Repo-d4e44d54-764b-4268-80e1-5f3933690b00/blob/8e3cf1fe70cf1ff48e42de7bad31cf6407ddbeb7/bad/libuser.py#L20 https://github.com/SAST-org/SAST-Test-Repo-d4e44d54-764b-4268-80e1-5f3933690b00/blob/8e3cf1fe70cf1ff48e42de7bad31cf6407ddbeb7/bad/libuser.py#L25 </details> [View more Data Flows](https://dev.whitesourcesoftware.com/sast/#/scans/b7bee5de-7dbb-4b0d-87aa-f257d07de53d/details?vulnId=7491777b-898a-41fe-b4bf-d0cc2c916a2b&filtered=yes) </details> </td></tr></details></td></tr><tr><td><a href='#'><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20></a> High</td><td>SQL Injection</td><td> [CWE-89](https://cwe.mitre.org/data/definitions/89.html) </td><td> [libuser.py:12](https://github.com/SAST-org/SAST-Test-Repo-d4e44d54-764b-4268-80e1-5f3933690b00/blob/8e3cf1fe70cf1ff48e42de7bad31cf6407ddbeb7/bad/libuser.py#L12) </td><td>10</td><td>2023-03-27 08:34am</td></tr><tr><td colspan='6'><details><summary>More info</summary> https://github.com/SAST-org/SAST-Test-Repo-d4e44d54-764b-4268-80e1-5f3933690b00/blob/8e3cf1fe70cf1ff48e42de7bad31cf6407ddbeb7/bad/libuser.py#L7-L12 <details> <summary>10 Data Flow/s detected</summary></br> <details> <summary>View Data Flow 1</summary> https://github.com/SAST-org/SAST-Test-Repo-d4e44d54-764b-4268-80e1-5f3933690b00/blob/8e3cf1fe70cf1ff48e42de7bad31cf6407ddbeb7/bad/mod_user.py#L69 https://github.com/SAST-org/SAST-Test-Repo-d4e44d54-764b-4268-80e1-5f3933690b00/blob/8e3cf1fe70cf1ff48e42de7bad31cf6407ddbeb7/bad/mod_user.py#L69 https://github.com/SAST-org/SAST-Test-Repo-d4e44d54-764b-4268-80e1-5f3933690b00/blob/8e3cf1fe70cf1ff48e42de7bad31cf6407ddbeb7/bad/libuser.py#L5 https://github.com/SAST-org/SAST-Test-Repo-d4e44d54-764b-4268-80e1-5f3933690b00/blob/8e3cf1fe70cf1ff48e42de7bad31cf6407ddbeb7/bad/libuser.py#L12 </details> <details> <summary>View Data Flow 2</summary> https://github.com/SAST-org/SAST-Test-Repo-d4e44d54-764b-4268-80e1-5f3933690b00/blob/8e3cf1fe70cf1ff48e42de7bad31cf6407ddbeb7/bad/mod_user.py#L69 https://github.com/SAST-org/SAST-Test-Repo-d4e44d54-764b-4268-80e1-5f3933690b00/blob/8e3cf1fe70cf1ff48e42de7bad31cf6407ddbeb7/bad/mod_user.py#L69 https://github.com/SAST-org/SAST-Test-Repo-d4e44d54-764b-4268-80e1-5f3933690b00/blob/8e3cf1fe70cf1ff48e42de7bad31cf6407ddbeb7/bad/libuser.py#L5 https://github.com/SAST-org/SAST-Test-Repo-d4e44d54-764b-4268-80e1-5f3933690b00/blob/8e3cf1fe70cf1ff48e42de7bad31cf6407ddbeb7/bad/libuser.py#L12 </details> <details> <summary>View Data Flow 3</summary> https://github.com/SAST-org/SAST-Test-Repo-d4e44d54-764b-4268-80e1-5f3933690b00/blob/8e3cf1fe70cf1ff48e42de7bad31cf6407ddbeb7/bad/mod_user.py#L17 https://github.com/SAST-org/SAST-Test-Repo-d4e44d54-764b-4268-80e1-5f3933690b00/blob/8e3cf1fe70cf1ff48e42de7bad31cf6407ddbeb7/bad/mod_user.py#L17 https://github.com/SAST-org/SAST-Test-Repo-d4e44d54-764b-4268-80e1-5f3933690b00/blob/8e3cf1fe70cf1ff48e42de7bad31cf6407ddbeb7/bad/libuser.py#L5 https://github.com/SAST-org/SAST-Test-Repo-d4e44d54-764b-4268-80e1-5f3933690b00/blob/8e3cf1fe70cf1ff48e42de7bad31cf6407ddbeb7/bad/libuser.py#L12 </details> [View more Data Flows](https://dev.whitesourcesoftware.com/sast/#/scans/b7bee5de-7dbb-4b0d-87aa-f257d07de53d/details?vulnId=3fd361d2-a7a0-46d2-b03d-9c93b496b144&filtered=yes) </details> </td></tr></details></td></tr><tr><td><a href='#'><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20></a> Medium</td><td>Hardcoded Password/Credentials</td><td> [CWE-798](https://cwe.mitre.org/data/definitions/798.html) </td><td> [libuser.py:12](https://github.com/SAST-org/SAST-Test-Repo-d4e44d54-764b-4268-80e1-5f3933690b00/blob/8e3cf1fe70cf1ff48e42de7bad31cf6407ddbeb7/bad/libuser.py#L12) </td><td>1</td><td>2023-03-27 08:34am</td></tr><tr><td colspan='6'><details><summary>More info</summary> https://github.com/SAST-org/SAST-Test-Repo-d4e44d54-764b-4268-80e1-5f3933690b00/blob/8e3cf1fe70cf1ff48e42de7bad31cf6407ddbeb7/bad/libuser.py#L7-L12 <details> <summary>1 Data Flow/s detected</summary></br> <details> <summary>View Data Flow 1</summary> https://github.com/SAST-org/SAST-Test-Repo-d4e44d54-764b-4268-80e1-5f3933690b00/blob/8e3cf1fe70cf1ff48e42de7bad31cf6407ddbeb7/bad/libuser.py#L12 </details> </details> </td></tr></details></td></tr><tr><td><a href='#'><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20></a> Medium</td><td>Hardcoded Password/Credentials</td><td> [CWE-798](https://cwe.mitre.org/data/definitions/798.html) </td><td> [vulpy-ssl.py:13](https://github.com/SAST-org/SAST-Test-Repo-d4e44d54-764b-4268-80e1-5f3933690b00/blob/8e3cf1fe70cf1ff48e42de7bad31cf6407ddbeb7/good/vulpy-ssl.py#L13) </td><td>1</td><td>2023-03-27 08:34am</td></tr><tr><td colspan='6'><details><summary>More info</summary> https://github.com/SAST-org/SAST-Test-Repo-d4e44d54-764b-4268-80e1-5f3933690b00/blob/8e3cf1fe70cf1ff48e42de7bad31cf6407ddbeb7/good/vulpy-ssl.py#L8-L13 <details> <summary>1 Data Flow/s detected</summary></br> <details> <summary>View Data Flow 1</summary> https://github.com/SAST-org/SAST-Test-Repo-d4e44d54-764b-4268-80e1-5f3933690b00/blob/8e3cf1fe70cf1ff48e42de7bad31cf6407ddbeb7/good/vulpy-ssl.py#L13 </details> </details> </td></tr></details></td></tr><tr><td><a href='#'><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20></a> Medium</td><td>Hardcoded Password/Credentials</td><td> [CWE-798](https://cwe.mitre.org/data/definitions/798.html) </td><td> [libapi.py:10](https://github.com/SAST-org/SAST-Test-Repo-d4e44d54-764b-4268-80e1-5f3933690b00/blob/8e3cf1fe70cf1ff48e42de7bad31cf6407ddbeb7/good/libapi.py#L10) </td><td>1</td><td>2023-03-27 08:34am</td></tr><tr><td colspan='6'><details><summary>More info</summary> https://github.com/SAST-org/SAST-Test-Repo-d4e44d54-764b-4268-80e1-5f3933690b00/blob/8e3cf1fe70cf1ff48e42de7bad31cf6407ddbeb7/good/libapi.py#L5-L10 <details> <summary>1 Data Flow/s detected</summary></br> <details> <summary>View Data Flow 1</summary> https://github.com/SAST-org/SAST-Test-Repo-d4e44d54-764b-4268-80e1-5f3933690b00/blob/8e3cf1fe70cf1ff48e42de7bad31cf6407ddbeb7/good/libapi.py#L10 </details> </details> </td></tr></details></td></tr><tr><td><a href='#'><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20></a> Medium</td><td>Hardcoded Password/Credentials</td><td> [CWE-798](https://cwe.mitre.org/data/definitions/798.html) </td><td> [vulpy.py:17](https://github.com/SAST-org/SAST-Test-Repo-d4e44d54-764b-4268-80e1-5f3933690b00/blob/8e3cf1fe70cf1ff48e42de7bad31cf6407ddbeb7/good/vulpy.py#L17) </td><td>1</td><td>2023-03-27 08:34am</td></tr><tr><td colspan='6'><details><summary>More info</summary> https://github.com/SAST-org/SAST-Test-Repo-d4e44d54-764b-4268-80e1-5f3933690b00/blob/8e3cf1fe70cf1ff48e42de7bad31cf6407ddbeb7/good/vulpy.py#L12-L17 <details> <summary>1 Data Flow/s detected</summary></br> <details> <summary>View Data Flow 1</summary> https://github.com/SAST-org/SAST-Test-Repo-d4e44d54-764b-4268-80e1-5f3933690b00/blob/8e3cf1fe70cf1ff48e42de7bad31cf6407ddbeb7/good/vulpy.py#L17 </details> </details> </td></tr></details></td></tr><tr><td><a href='#'><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20></a> Medium</td><td>Hardcoded Password/Credentials</td><td> [CWE-798](https://cwe.mitre.org/data/definitions/798.html) </td><td> [vulpy.py:16](https://github.com/SAST-org/SAST-Test-Repo-d4e44d54-764b-4268-80e1-5f3933690b00/blob/8e3cf1fe70cf1ff48e42de7bad31cf6407ddbeb7/bad/vulpy.py#L16) </td><td>1</td><td>2023-03-27 08:34am</td></tr><tr><td colspan='6'><details><summary>More info</summary> https://github.com/SAST-org/SAST-Test-Repo-d4e44d54-764b-4268-80e1-5f3933690b00/blob/8e3cf1fe70cf1ff48e42de7bad31cf6407ddbeb7/bad/vulpy.py#L11-L16 <details> <summary>1 Data Flow/s detected</summary></br> <details> <summary>View Data Flow 1</summary> https://github.com/SAST-org/SAST-Test-Repo-d4e44d54-764b-4268-80e1-5f3933690b00/blob/8e3cf1fe70cf1ff48e42de7bad31cf6407ddbeb7/bad/vulpy.py#L16 </details> </details> </td></tr></details></td></tr><tr><td><a href='#'><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20></a> Medium</td><td>Hardcoded Password/Credentials</td><td> [CWE-798](https://cwe.mitre.org/data/definitions/798.html) </td><td> [vulpy-ssl.py:13](https://github.com/SAST-org/SAST-Test-Repo-d4e44d54-764b-4268-80e1-5f3933690b00/blob/8e3cf1fe70cf1ff48e42de7bad31cf6407ddbeb7/bad/vulpy-ssl.py#L13) </td><td>1</td><td>2023-03-27 08:34am</td></tr><tr><td colspan='6'><details><summary>More info</summary> https://github.com/SAST-org/SAST-Test-Repo-d4e44d54-764b-4268-80e1-5f3933690b00/blob/8e3cf1fe70cf1ff48e42de7bad31cf6407ddbeb7/bad/vulpy-ssl.py#L8-L13 <details> <summary>1 Data Flow/s detected</summary></br> <details> <summary>View Data Flow 1</summary> https://github.com/SAST-org/SAST-Test-Repo-d4e44d54-764b-4268-80e1-5f3933690b00/blob/8e3cf1fe70cf1ff48e42de7bad31cf6407ddbeb7/bad/vulpy-ssl.py#L13 </details> </details> </td></tr></details></td></tr><tr><td><a href='#'><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20></a> Medium</td><td>Hardcoded Password/Credentials</td><td> [CWE-798](https://cwe.mitre.org/data/definitions/798.html) </td><td> [libuser.py:53](https://github.com/SAST-org/SAST-Test-Repo-d4e44d54-764b-4268-80e1-5f3933690b00/blob/8e3cf1fe70cf1ff48e42de7bad31cf6407ddbeb7/bad/libuser.py#L53) </td><td>1</td><td>2023-03-27 08:34am</td></tr><tr><td colspan='6'><details><summary>More info</summary> https://github.com/SAST-org/SAST-Test-Repo-d4e44d54-764b-4268-80e1-5f3933690b00/blob/8e3cf1fe70cf1ff48e42de7bad31cf6407ddbeb7/bad/libuser.py#L48-L53 <details> <summary>1 Data Flow/s detected</summary></br> <details> <summary>View Data Flow 1</summary> https://github.com/SAST-org/SAST-Test-Repo-d4e44d54-764b-4268-80e1-5f3933690b00/blob/8e3cf1fe70cf1ff48e42de7bad31cf6407ddbeb7/bad/libuser.py#L53 </details> </details> </td></tr></details></td></tr></tbody></table>
non_priority
code security report high severity findings total findings code security report scan metadata latest scan total findings new findings resolved findings tested project files detected programming languages python javascript node js check this box to manually trigger a scan finding details severity vulnerability type cwe file data flows date high sql injection more info data flow s detected view data flow view data flow high sql injection more info data flow s detected view data flow view data flow view data flow high sql injection more info data flow s detected view data flow view data flow view data flow medium hardcoded password credentials more info data flow s detected view data flow medium hardcoded password credentials more info data flow s detected view data flow medium hardcoded password credentials more info data flow s detected view data flow medium hardcoded password credentials more info data flow s detected view data flow medium hardcoded password credentials more info data flow s detected view data flow medium hardcoded password credentials more info data flow s detected view data flow medium hardcoded password credentials more info data flow s detected view data flow
0
6,748
6,584,002,898
IssuesEvent
2017-09-13 08:35:08
vmware/docker-volume-vsphere
https://api.github.com/repos/vmware/docker-volume-vsphere
closed
Improve CI/CD log collection
component/ci-infrastructure kind/enhancement
- [ ] Dump relevant information for both successful and failed runs - [ ] Post logs to a location where developers can download it - [ ] Improve logging output in CI/CD
1.0
Improve CI/CD log collection - - [ ] Dump relevant information for both successful and failed runs - [ ] Post logs to a location where developers can download it - [ ] Improve logging output in CI/CD
non_priority
improve ci cd log collection dump relevant information for both successful and failed runs post logs to a location where developers can download it improve logging output in ci cd
0
33,238
15,830,234,738
IssuesEvent
2021-04-06 12:15:20
chef/chef-server
https://api.github.com/repos/chef/chef-server
closed
Update OpenResty to 1.19.3.1
Aspect: Performance Component: omnibus packaging Type: Chore
OpenResty to 1.19.3.1 is out with significant performance improvements: https://openresty.org/en/ann-1019003001.html
True
Update OpenResty to 1.19.3.1 - OpenResty to 1.19.3.1 is out with significant performance improvements: https://openresty.org/en/ann-1019003001.html
non_priority
update openresty to openresty to is out with significant performance improvements
0
19,453
6,725,331,574
IssuesEvent
2017-10-17 04:39:24
hyperrealm/libconfig
https://api.github.com/repos/hyperrealm/libconfig
closed
undefined reference to 'config_setting_lookup'
build issue
- **Environment**: Ubuntu Server 14.04, make 3.81 - **libconfig version**: 1.5 (I could not install the latest version of libconfig (I got same problem here #53 ). I am using version 1.5 which has been installed by command line `sudo apt-get install libconfig-dev`) - **Problem**: `undefined reference to 'config_setting_lookup'` - I have modified the configuration file `examples/example.cfg` and `example/example1.c` to have many authors for a book: `examples/example.cfg` ``` books = ( { title = "Treasure Island"; author = ["Robert Louis Stevenson","Nobody"]; price = 29.99; qty = 5; }, { title = "Snow Crash"; author = ["Neal Stephenson"]; price = 9.99; qty = 8; } ); ``` `example/example1.c` ``` config_setting_t *authors = config_setting_lookup(book, "author", &author); if(!(config_setting_lookup_string(book, "title", &title) && author && config_setting_lookup_float(book, "price", &price) && config_setting_lookup_int(book, "qty", &qty))) continue; ``` P/S: In the source code (version 1.5 I have grabbed here: https://launchpad.net/ubuntu/+source/libconfig/1.5-0.2 ), I could see there is `config_setting_lookup` function: `libconfig.h:270` and `libconfig.c:1189`
1.0
undefined reference to 'config_setting_lookup' - - **Environment**: Ubuntu Server 14.04, make 3.81 - **libconfig version**: 1.5 (I could not install the latest version of libconfig (I got same problem here #53 ). I am using version 1.5 which has been installed by command line `sudo apt-get install libconfig-dev`) - **Problem**: `undefined reference to 'config_setting_lookup'` - I have modified the configuration file `examples/example.cfg` and `example/example1.c` to have many authors for a book: `examples/example.cfg` ``` books = ( { title = "Treasure Island"; author = ["Robert Louis Stevenson","Nobody"]; price = 29.99; qty = 5; }, { title = "Snow Crash"; author = ["Neal Stephenson"]; price = 9.99; qty = 8; } ); ``` `example/example1.c` ``` config_setting_t *authors = config_setting_lookup(book, "author", &author); if(!(config_setting_lookup_string(book, "title", &title) && author && config_setting_lookup_float(book, "price", &price) && config_setting_lookup_int(book, "qty", &qty))) continue; ``` P/S: In the source code (version 1.5 I have grabbed here: https://launchpad.net/ubuntu/+source/libconfig/1.5-0.2 ), I could see there is `config_setting_lookup` function: `libconfig.h:270` and `libconfig.c:1189`
non_priority
undefined reference to config setting lookup environment ubuntu server make libconfig version i could not install the latest version of libconfig i got same problem here i am using version which has been installed by command line sudo apt get install libconfig dev problem undefined reference to config setting lookup i have modified the configuration file examples example cfg and example c to have many authors for a book examples example cfg books title treasure island author price qty title snow crash author price qty example c config setting t authors config setting lookup book author author if config setting lookup string book title title author config setting lookup float book price price config setting lookup int book qty qty continue p s in the source code version i have grabbed here i could see there is config setting lookup function libconfig h and libconfig c
0
88,606
11,104,998,068
IssuesEvent
2019-12-17 08:56:59
i-adopt/terminologies
https://api.github.com/repos/i-adopt/terminologies
closed
role related to data and observable property terminology
consumer questionnaire design
remove data from data and observable property terminology
1.0
role related to data and observable property terminology - remove data from data and observable property terminology
non_priority
role related to data and observable property terminology remove data from data and observable property terminology
0
37,361
6,601,423,139
IssuesEvent
2017-09-18 00:24:15
rancher/os
https://api.github.com/repos/rancher/os
closed
Password for rancher user in 0.6.0-rc5?
area/documentation
**RancherOS Version: (ros os version)** 0.6.0-rc5 **Where are you running RancherOS? (docker-machine, AWS, GCE, baremetal, etc.)** VirtualBox 4.3.28 I booted 0.6.0-rc5 iso in a VirtualBox VM and tried to login to it via ssh with rancher user. However the default password from previous releases did not work so I switched to root and changed it. I noticed that autologin to virtual console with rancher user is enabled but what is the password?
1.0
Password for rancher user in 0.6.0-rc5? - **RancherOS Version: (ros os version)** 0.6.0-rc5 **Where are you running RancherOS? (docker-machine, AWS, GCE, baremetal, etc.)** VirtualBox 4.3.28 I booted 0.6.0-rc5 iso in a VirtualBox VM and tried to login to it via ssh with rancher user. However the default password from previous releases did not work so I switched to root and changed it. I noticed that autologin to virtual console with rancher user is enabled but what is the password?
non_priority
password for rancher user in rancheros version ros os version where are you running rancheros docker machine aws gce baremetal etc virtualbox i booted iso in a virtualbox vm and tried to login to it via ssh with rancher user however the default password from previous releases did not work so i switched to root and changed it i noticed that autologin to virtual console with rancher user is enabled but what is the password
0
61,140
8,490,124,280
IssuesEvent
2018-10-26 22:41:39
vim-volt/volt
https://api.github.com/repos/vim-volt/volt
closed
Volt list template example gives hard-to-read output
bug documentation fixed-in-devel
The example for volt list is as follows: ` $ volt list -f '{{ range .Profiles }}{{ if eq $.CurrentProfileName .Name }}{{ range .ReposPath }}{{ . }}{{ end }}{{ end }}{{ end }}' ` which will print all the plugins for the current profile in a single continous line. I advise the following command replace it: ` $ volt list -f '{{ range .Profiles }}{{ if eq $.CurrentProfileName .Name }}{{ range .ReposPath }}{{ println . }}{{ end }}{{ end }}{{ end }}'` which gives one plugin per line output.
1.0
Volt list template example gives hard-to-read output - The example for volt list is as follows: ` $ volt list -f '{{ range .Profiles }}{{ if eq $.CurrentProfileName .Name }}{{ range .ReposPath }}{{ . }}{{ end }}{{ end }}{{ end }}' ` which will print all the plugins for the current profile in a single continous line. I advise the following command replace it: ` $ volt list -f '{{ range .Profiles }}{{ if eq $.CurrentProfileName .Name }}{{ range .ReposPath }}{{ println . }}{{ end }}{{ end }}{{ end }}'` which gives one plugin per line output.
non_priority
volt list template example gives hard to read output the example for volt list is as follows volt list f range profiles if eq currentprofilename name range repospath end end end which will print all the plugins for the current profile in a single continous line i advise the following command replace it volt list f range profiles if eq currentprofilename name range repospath println end end end which gives one plugin per line output
0
286,228
24,731,927,308
IssuesEvent
2022-10-20 18:22:10
dotnet/source-build
https://api.github.com/repos/dotnet/source-build
closed
Next steps on SDK comparison testing
area-ci-testing
@dagood added some next steps to improve our SDK comparison testing here: https://github.com/dotnet/source-build/pull/1611#pullrequestreview-433453313. --- 1. Add a baseline diff vs. last release. 2. Filter the results such that any output that makes it past the filter is something that we need to take action on. (E.g. scenario impacting.) 3. *(Out of scope) Eliminate differences between Microsoft and source-built SDKs.*
1.0
Next steps on SDK comparison testing - @dagood added some next steps to improve our SDK comparison testing here: https://github.com/dotnet/source-build/pull/1611#pullrequestreview-433453313. --- 1. Add a baseline diff vs. last release. 2. Filter the results such that any output that makes it past the filter is something that we need to take action on. (E.g. scenario impacting.) 3. *(Out of scope) Eliminate differences between Microsoft and source-built SDKs.*
non_priority
next steps on sdk comparison testing dagood added some next steps to improve our sdk comparison testing here add a baseline diff vs last release filter the results such that any output that makes it past the filter is something that we need to take action on e g scenario impacting out of scope eliminate differences between microsoft and source built sdks
0
167,689
26,534,461,630
IssuesEvent
2023-01-19 14:45:19
tillioss/tilli-ide
https://api.github.com/repos/tillioss/tilli-ide
opened
[Work Plan Tasks] M3 | Digital Safety (Prototyping)
Art & Design Tilli: Backlog
Create M3 | Digital Safety Screens in the IDE for User Testing that will be conducted by March
1.0
[Work Plan Tasks] M3 | Digital Safety (Prototyping) - Create M3 | Digital Safety Screens in the IDE for User Testing that will be conducted by March
non_priority
digital safety prototyping create digital safety screens in the ide for user testing that will be conducted by march
0
33,934
12,229,047,460
IssuesEvent
2020-05-03 22:10:11
YANG-DB/yang-db
https://api.github.com/repos/YANG-DB/yang-db
opened
CVE-2020-10672 (High) detected in jackson-databind-2.9.8.jar
security vulnerability
## CVE-2020-10672 - High Severity Vulnerability <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>jackson-databind-2.9.8.jar</b></p></summary> <p>General data-binding functionality for Jackson: works on core streaming API</p> <p>Library home page: <a href="http://github.com/FasterXML/jackson">http://github.com/FasterXML/jackson</a></p> <p>Path to vulnerable library: /yang-db/distrib/dragon-dragon/lib/jackson-databind-2.9.8.jar,/yang-db/distrib/knowledge-knowledge/lib/jackson-databind-2.9.8.jar</p> <p> Dependency Hierarchy: - :x: **jackson-databind-2.9.8.jar** (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/YANG-DB/yang-db/commit/fb4688fc73077d82b1716f0af8303e34cb1e6d25">fb4688fc73077d82b1716f0af8303e34cb1e6d25</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> FasterXML jackson-databind 2.x before 2.9.10.4 mishandles the interaction between serialization gadgets and typing, related to org.apache.aries.transaction.jms.internal.XaPooledConnectionFactory (aka aries.transaction.jms). <p>Publish Date: 2020-03-18 <p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-10672>CVE-2020-10672</a></p> </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>8.8</b>)</summary> <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: Required - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: High - Integrity Impact: High - Availability Impact: High </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary> <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://nvd.nist.gov/vuln/detail/CVE-2020-10672">https://nvd.nist.gov/vuln/detail/CVE-2020-10672</a></p> <p>Release Date: 2020-03-18</p> <p>Fix Resolution: jackson-databind-2.9.10.4</p> </p> </details> <p></p> *** Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
True
CVE-2020-10672 (High) detected in jackson-databind-2.9.8.jar - ## CVE-2020-10672 - High Severity Vulnerability <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>jackson-databind-2.9.8.jar</b></p></summary> <p>General data-binding functionality for Jackson: works on core streaming API</p> <p>Library home page: <a href="http://github.com/FasterXML/jackson">http://github.com/FasterXML/jackson</a></p> <p>Path to vulnerable library: /yang-db/distrib/dragon-dragon/lib/jackson-databind-2.9.8.jar,/yang-db/distrib/knowledge-knowledge/lib/jackson-databind-2.9.8.jar</p> <p> Dependency Hierarchy: - :x: **jackson-databind-2.9.8.jar** (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/YANG-DB/yang-db/commit/fb4688fc73077d82b1716f0af8303e34cb1e6d25">fb4688fc73077d82b1716f0af8303e34cb1e6d25</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> FasterXML jackson-databind 2.x before 2.9.10.4 mishandles the interaction between serialization gadgets and typing, related to org.apache.aries.transaction.jms.internal.XaPooledConnectionFactory (aka aries.transaction.jms). <p>Publish Date: 2020-03-18 <p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-10672>CVE-2020-10672</a></p> </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>8.8</b>)</summary> <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: Required - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: High - Integrity Impact: High - Availability Impact: High </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary> <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://nvd.nist.gov/vuln/detail/CVE-2020-10672">https://nvd.nist.gov/vuln/detail/CVE-2020-10672</a></p> <p>Release Date: 2020-03-18</p> <p>Fix Resolution: jackson-databind-2.9.10.4</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 vulnerable library yang db distrib dragon dragon lib jackson databind jar yang db distrib knowledge knowledge lib jackson databind jar dependency hierarchy x jackson databind jar vulnerable library found in head commit a href vulnerability details fasterxml jackson databind x before mishandles the interaction between serialization gadgets and typing related to org apache aries transaction jms internal xapooledconnectionfactory aka aries transaction jms publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction required scope unchanged impact metrics confidentiality impact high integrity impact high availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution jackson databind step up your open source security game with whitesource
0
288,180
21,689,495,083
IssuesEvent
2022-05-09 14:14:10
Cantera/cantera-website
https://api.github.com/repos/Cantera/cantera-website
closed
Add documentation for covered configuration options
documentation-update
The new GitHub CI covers a few common configuration options for a compilation of Cantera from source. It would be good to document what is routinely tested, and what is not covered by the test runners. Issue is opened in response to discussion in Cantera/cantera#1208
1.0
Add documentation for covered configuration options - The new GitHub CI covers a few common configuration options for a compilation of Cantera from source. It would be good to document what is routinely tested, and what is not covered by the test runners. Issue is opened in response to discussion in Cantera/cantera#1208
non_priority
add documentation for covered configuration options the new github ci covers a few common configuration options for a compilation of cantera from source it would be good to document what is routinely tested and what is not covered by the test runners issue is opened in response to discussion in cantera cantera
0
33,458
12,216,563,238
IssuesEvent
2020-05-01 15:24:02
bsbtd/Teste
https://api.github.com/repos/bsbtd/Teste
opened
CVE-2019-13173 (High) detected in fstream-1.0.11.tgz
security vulnerability
## CVE-2019-13173 - High Severity Vulnerability <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>fstream-1.0.11.tgz</b></p></summary> <p>Advanced file system stream things</p> <p>Library home page: <a href="https://registry.npmjs.org/fstream/-/fstream-1.0.11.tgz">https://registry.npmjs.org/fstream/-/fstream-1.0.11.tgz</a></p> <p>Path to dependency file: /tmp/ws-scm/Teste/ionic-angular-twitter-pwa/server/package.json</p> <p>Path to vulnerable library: /tmp/ws-scm/Teste/ionic-angular-twitter-pwa/node_modules/grpc/node_modules/fstream/package.json</p> <p> Dependency Hierarchy: - firebase-4.13.1.tgz (Root Library) - firestore-0.4.1.tgz - grpc-1.10.1.tgz - node-pre-gyp-0.7.0.tgz - tar-2.2.1.tgz - :x: **fstream-1.0.11.tgz** (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/bsbtd/Teste/commit/50a539d66e7a2f790cf8a8d8d1471993698c9adc">50a539d66e7a2f790cf8a8d8d1471993698c9adc</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> fstream before 1.0.12 is vulnerable to Arbitrary File Overwrite. Extracting tarballs containing a hardlink to a file that already exists in the system, and a file that matches the hardlink, will overwrite the system's file with the contents of the extracted file. The fstream.DirWriter() function is vulnerable. <p>Publish Date: 2019-07-02 <p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-13173>CVE-2019-13173</a></p> </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary> <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: None - Integrity Impact: High - Availability Impact: None </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary> <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-13173">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-13173</a></p> <p>Release Date: 2019-07-02</p> <p>Fix Resolution: 1.0.12</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-13173 (High) detected in fstream-1.0.11.tgz - ## CVE-2019-13173 - High Severity Vulnerability <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>fstream-1.0.11.tgz</b></p></summary> <p>Advanced file system stream things</p> <p>Library home page: <a href="https://registry.npmjs.org/fstream/-/fstream-1.0.11.tgz">https://registry.npmjs.org/fstream/-/fstream-1.0.11.tgz</a></p> <p>Path to dependency file: /tmp/ws-scm/Teste/ionic-angular-twitter-pwa/server/package.json</p> <p>Path to vulnerable library: /tmp/ws-scm/Teste/ionic-angular-twitter-pwa/node_modules/grpc/node_modules/fstream/package.json</p> <p> Dependency Hierarchy: - firebase-4.13.1.tgz (Root Library) - firestore-0.4.1.tgz - grpc-1.10.1.tgz - node-pre-gyp-0.7.0.tgz - tar-2.2.1.tgz - :x: **fstream-1.0.11.tgz** (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/bsbtd/Teste/commit/50a539d66e7a2f790cf8a8d8d1471993698c9adc">50a539d66e7a2f790cf8a8d8d1471993698c9adc</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> fstream before 1.0.12 is vulnerable to Arbitrary File Overwrite. Extracting tarballs containing a hardlink to a file that already exists in the system, and a file that matches the hardlink, will overwrite the system's file with the contents of the extracted file. The fstream.DirWriter() function is vulnerable. <p>Publish Date: 2019-07-02 <p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-13173>CVE-2019-13173</a></p> </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary> <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: None - Integrity Impact: High - Availability Impact: None </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary> <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-13173">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-13173</a></p> <p>Release Date: 2019-07-02</p> <p>Fix Resolution: 1.0.12</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 fstream tgz cve high severity vulnerability vulnerable library fstream tgz advanced file system stream things library home page a href path to dependency file tmp ws scm teste ionic angular twitter pwa server package json path to vulnerable library tmp ws scm teste ionic angular twitter pwa node modules grpc node modules fstream package json dependency hierarchy firebase tgz root library firestore tgz grpc tgz node pre gyp tgz tar tgz x fstream tgz vulnerable library found in head commit a href vulnerability details fstream before is vulnerable to arbitrary file overwrite extracting tarballs containing a hardlink to a file that already exists in the system and a file that matches the hardlink will overwrite the system s file with the contents of the extracted file the fstream dirwriter function is vulnerable publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact none integrity impact high availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution step up your open source security game with whitesource
0
46,254
13,152,912,874
IssuesEvent
2020-08-10 01:00:48
jgeraigery/FHIR
https://api.github.com/repos/jgeraigery/FHIR
opened
CVE-2020-15138 (High) detected in prismjs-1.17.1.tgz
security vulnerability
## CVE-2020-15138 - High Severity Vulnerability <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>prismjs-1.17.1.tgz</b></p></summary> <p>Lightweight, robust, elegant syntax highlighting. A spin-off project from Dabblet.</p> <p>Library home page: <a href="https://registry.npmjs.org/prismjs/-/prismjs-1.17.1.tgz">https://registry.npmjs.org/prismjs/-/prismjs-1.17.1.tgz</a></p> <p>Path to dependency file: /tmp/ws-scm/FHIR/docs/package.json</p> <p>Path to vulnerable library: /tmp/ws-scm/FHIR/docs/node_modules/prismjs/package.json</p> <p> Dependency Hierarchy: - gatsby-theme-carbon-1.6.1.tgz (Root Library) - addons-website-0.0.1-alpha.21.tgz - :x: **prismjs-1.17.1.tgz** (Vulnerable Library) </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary> <p> Prism is vulnerable to Cross-Site Scripting. The easing preview of the Previewers plugin has an XSS vulnerability that allows attackers to execute arbitrary code in Safari and Internet Explorer. This impacts all Safari and Internet Explorer users of Prism >=v1.1.0 that use the _Previewers_ plugin (>=v1.10.0) or the _Previewer: Easing_ plugin (v1.1.0 to v1.9.0). This problem is fixed in version 1.21.0. To workaround the issue without upgrading, disable the easing preview on all impacted code blocks. You need Prism v1.10.0 or newer to apply this workaround. <p>Publish Date: 2020-07-21 <p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-15138>CVE-2020-15138</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.1</b>)</summary> <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: High - Privileges Required: None - User Interaction: Required - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: High - Integrity Impact: High - Availability Impact: Low </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary> <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://github.com/PrismJS/prism/v1.21.0">https://github.com/PrismJS/prism/v1.21.0</a></p> <p>Release Date: 2020-07-21</p> <p>Fix Resolution: v1.21.0</p> </p> </details> <p></p> <!-- <REMEDIATE>{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"prismjs","packageVersion":"1.17.1","isTransitiveDependency":true,"dependencyTree":"gatsby-theme-carbon:1.6.1;@carbon/addons-website:0.0.1-alpha.21;prismjs:1.17.1","isMinimumFixVersionAvailable":true,"minimumFixVersion":"v1.21.0"}],"vulnerabilityIdentifier":"CVE-2020-15138","vulnerabilityDetails":"Prism is vulnerable to Cross-Site Scripting. The easing preview of the Previewers plugin has an XSS vulnerability that allows attackers to execute arbitrary code in Safari and Internet Explorer. This impacts all Safari and Internet Explorer users of Prism \u003e\u003dv1.1.0 that use the _Previewers_ plugin (\u003e\u003dv1.10.0) or the _Previewer: Easing_ plugin (v1.1.0 to v1.9.0). This problem is fixed in version 1.21.0. To workaround the issue without upgrading, disable the easing preview on all impacted code blocks. You need Prism v1.10.0 or newer to apply this workaround.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-15138","cvss3Severity":"high","cvss3Score":"7.1","cvss3Metrics":{"A":"Low","AC":"High","PR":"None","S":"Unchanged","C":"High","UI":"Required","AV":"Network","I":"High"},"extraData":{}}</REMEDIATE> -->
True
CVE-2020-15138 (High) detected in prismjs-1.17.1.tgz - ## CVE-2020-15138 - High Severity Vulnerability <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>prismjs-1.17.1.tgz</b></p></summary> <p>Lightweight, robust, elegant syntax highlighting. A spin-off project from Dabblet.</p> <p>Library home page: <a href="https://registry.npmjs.org/prismjs/-/prismjs-1.17.1.tgz">https://registry.npmjs.org/prismjs/-/prismjs-1.17.1.tgz</a></p> <p>Path to dependency file: /tmp/ws-scm/FHIR/docs/package.json</p> <p>Path to vulnerable library: /tmp/ws-scm/FHIR/docs/node_modules/prismjs/package.json</p> <p> Dependency Hierarchy: - gatsby-theme-carbon-1.6.1.tgz (Root Library) - addons-website-0.0.1-alpha.21.tgz - :x: **prismjs-1.17.1.tgz** (Vulnerable Library) </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary> <p> Prism is vulnerable to Cross-Site Scripting. The easing preview of the Previewers plugin has an XSS vulnerability that allows attackers to execute arbitrary code in Safari and Internet Explorer. This impacts all Safari and Internet Explorer users of Prism >=v1.1.0 that use the _Previewers_ plugin (>=v1.10.0) or the _Previewer: Easing_ plugin (v1.1.0 to v1.9.0). This problem is fixed in version 1.21.0. To workaround the issue without upgrading, disable the easing preview on all impacted code blocks. You need Prism v1.10.0 or newer to apply this workaround. <p>Publish Date: 2020-07-21 <p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-15138>CVE-2020-15138</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.1</b>)</summary> <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: High - Privileges Required: None - User Interaction: Required - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: High - Integrity Impact: High - Availability Impact: Low </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary> <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://github.com/PrismJS/prism/v1.21.0">https://github.com/PrismJS/prism/v1.21.0</a></p> <p>Release Date: 2020-07-21</p> <p>Fix Resolution: v1.21.0</p> </p> </details> <p></p> <!-- <REMEDIATE>{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"prismjs","packageVersion":"1.17.1","isTransitiveDependency":true,"dependencyTree":"gatsby-theme-carbon:1.6.1;@carbon/addons-website:0.0.1-alpha.21;prismjs:1.17.1","isMinimumFixVersionAvailable":true,"minimumFixVersion":"v1.21.0"}],"vulnerabilityIdentifier":"CVE-2020-15138","vulnerabilityDetails":"Prism is vulnerable to Cross-Site Scripting. The easing preview of the Previewers plugin has an XSS vulnerability that allows attackers to execute arbitrary code in Safari and Internet Explorer. This impacts all Safari and Internet Explorer users of Prism \u003e\u003dv1.1.0 that use the _Previewers_ plugin (\u003e\u003dv1.10.0) or the _Previewer: Easing_ plugin (v1.1.0 to v1.9.0). This problem is fixed in version 1.21.0. To workaround the issue without upgrading, disable the easing preview on all impacted code blocks. You need Prism v1.10.0 or newer to apply this workaround.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-15138","cvss3Severity":"high","cvss3Score":"7.1","cvss3Metrics":{"A":"Low","AC":"High","PR":"None","S":"Unchanged","C":"High","UI":"Required","AV":"Network","I":"High"},"extraData":{}}</REMEDIATE> -->
non_priority
cve high detected in prismjs tgz cve high severity vulnerability vulnerable library prismjs tgz lightweight robust elegant syntax highlighting a spin off project from dabblet library home page a href path to dependency file tmp ws scm fhir docs package json path to vulnerable library tmp ws scm fhir docs node modules prismjs package json dependency hierarchy gatsby theme carbon tgz root library addons website alpha tgz x prismjs tgz vulnerable library vulnerability details prism is vulnerable to cross site scripting the easing preview of the previewers plugin has an xss vulnerability that allows attackers to execute arbitrary code in safari and internet explorer this impacts all safari and internet explorer users of prism that use the previewers plugin or the previewer easing plugin to this problem is fixed in version to workaround the issue without upgrading disable the easing preview on all impacted code blocks you need prism or newer to apply this workaround publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity high privileges required none user interaction required scope unchanged impact metrics confidentiality impact high integrity impact high availability impact low for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution isopenpronvulnerability true ispackagebased true isdefaultbranch true packages vulnerabilityidentifier cve vulnerabilitydetails prism is vulnerable to cross site scripting the easing preview of the previewers plugin has an xss vulnerability that allows attackers to execute arbitrary code in safari and internet explorer this impacts all safari and internet explorer users of prism that use the previewers plugin or the previewer easing plugin to this problem is fixed in version to workaround the issue without upgrading disable the easing preview on all impacted code blocks you need prism or newer to apply this workaround vulnerabilityurl
0
92,891
15,872,902,288
IssuesEvent
2021-04-09 01:02:47
KaterinaOrg/keycloak
https://api.github.com/repos/KaterinaOrg/keycloak
opened
CVE-2017-15708 (High) detected in commons-collections-3.2.1.jar
security vulnerability
## CVE-2017-15708 - High Severity Vulnerability <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>commons-collections-3.2.1.jar</b></p></summary> <p>Types that extend and augment the Java Collections Framework.</p> <p>Path to dependency file: keycloak/testsuite/integration-arquillian/servers/auth-server/undertow/pom.xml</p> <p>Path to vulnerable library: /home/wss-scanner/.m2/repository/commons-collections/commons-collections/3.2.1/commons-collections-3.2.1.jar,/home/wss-scanner/.m2/repository/commons-collections/commons-collections/3.2.1/commons-collections-3.2.1.jar</p> <p> Dependency Hierarchy: - apacheds-core-annotations-2.0.0.AM26.jar (Root Library) - mavibot-1.0.0-M8.jar - :x: **commons-collections-3.2.1.jar** (Vulnerable Library) <p>Found in base branch: <b>master</b></p> </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary> <p> In Apache Synapse, by default no authentication is required for Java Remote Method Invocation (RMI). So Apache Synapse 3.0.1 or all previous releases (3.0.0, 2.1.0, 2.0.0, 1.2, 1.1.2, 1.1.1) allows remote code execution attacks that can be performed by injecting specially crafted serialized objects. And the presence of Apache Commons Collections 3.2.1 (commons-collections-3.2.1.jar) or previous versions in Synapse distribution makes this exploitable. To mitigate the issue, we need to limit RMI access to trusted users only. Further upgrading to 3.0.1 version will eliminate the risk of having said Commons Collection version. In Synapse 3.0.1, Commons Collection has been updated to 3.2.2 version. <p>Publish Date: 2017-12-11 <p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2017-15708>CVE-2017-15708</a></p> </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>9.8</b>)</summary> <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: High - Integrity Impact: High - Availability Impact: High </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary> <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-15708">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-15708</a></p> <p>Release Date: 2017-12-11</p> <p>Fix Resolution: org.apache.synapse:Apache-Synapse:3.0.1;commons-collections:commons-collections:3.2.2</p> </p> </details> <p></p> <!-- <REMEDIATE>{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"Java","groupId":"commons-collections","packageName":"commons-collections","packageVersion":"3.2.1","packageFilePaths":["/testsuite/integration-arquillian/servers/auth-server/undertow/pom.xml","/util/embedded-ldap/pom.xml"],"isTransitiveDependency":true,"dependencyTree":"org.apache.directory.server:apacheds-core-annotations:2.0.0.AM26;org.apache.directory.mavibot:mavibot:1.0.0-M8;commons-collections:commons-collections:3.2.1","isMinimumFixVersionAvailable":true,"minimumFixVersion":"org.apache.synapse:Apache-Synapse:3.0.1;commons-collections:commons-collections:3.2.2"}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2017-15708","vulnerabilityDetails":"In Apache Synapse, by default no authentication is required for Java Remote Method Invocation (RMI). So Apache Synapse 3.0.1 or all previous releases (3.0.0, 2.1.0, 2.0.0, 1.2, 1.1.2, 1.1.1) allows remote code execution attacks that can be performed by injecting specially crafted serialized objects. And the presence of Apache Commons Collections 3.2.1 (commons-collections-3.2.1.jar) or previous versions in Synapse distribution makes this exploitable. To mitigate the issue, we need to limit RMI access to trusted users only. Further upgrading to 3.0.1 version will eliminate the risk of having said Commons Collection version. In Synapse 3.0.1, Commons Collection has been updated to 3.2.2 version.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2017-15708","cvss3Severity":"high","cvss3Score":"9.8","cvss3Metrics":{"A":"High","AC":"Low","PR":"None","S":"Unchanged","C":"High","UI":"None","AV":"Network","I":"High"},"extraData":{}}</REMEDIATE> -->
True
CVE-2017-15708 (High) detected in commons-collections-3.2.1.jar - ## CVE-2017-15708 - High Severity Vulnerability <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>commons-collections-3.2.1.jar</b></p></summary> <p>Types that extend and augment the Java Collections Framework.</p> <p>Path to dependency file: keycloak/testsuite/integration-arquillian/servers/auth-server/undertow/pom.xml</p> <p>Path to vulnerable library: /home/wss-scanner/.m2/repository/commons-collections/commons-collections/3.2.1/commons-collections-3.2.1.jar,/home/wss-scanner/.m2/repository/commons-collections/commons-collections/3.2.1/commons-collections-3.2.1.jar</p> <p> Dependency Hierarchy: - apacheds-core-annotations-2.0.0.AM26.jar (Root Library) - mavibot-1.0.0-M8.jar - :x: **commons-collections-3.2.1.jar** (Vulnerable Library) <p>Found in base branch: <b>master</b></p> </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary> <p> In Apache Synapse, by default no authentication is required for Java Remote Method Invocation (RMI). So Apache Synapse 3.0.1 or all previous releases (3.0.0, 2.1.0, 2.0.0, 1.2, 1.1.2, 1.1.1) allows remote code execution attacks that can be performed by injecting specially crafted serialized objects. And the presence of Apache Commons Collections 3.2.1 (commons-collections-3.2.1.jar) or previous versions in Synapse distribution makes this exploitable. To mitigate the issue, we need to limit RMI access to trusted users only. Further upgrading to 3.0.1 version will eliminate the risk of having said Commons Collection version. In Synapse 3.0.1, Commons Collection has been updated to 3.2.2 version. <p>Publish Date: 2017-12-11 <p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2017-15708>CVE-2017-15708</a></p> </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>9.8</b>)</summary> <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: High - Integrity Impact: High - Availability Impact: High </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary> <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-15708">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-15708</a></p> <p>Release Date: 2017-12-11</p> <p>Fix Resolution: org.apache.synapse:Apache-Synapse:3.0.1;commons-collections:commons-collections:3.2.2</p> </p> </details> <p></p> <!-- <REMEDIATE>{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"Java","groupId":"commons-collections","packageName":"commons-collections","packageVersion":"3.2.1","packageFilePaths":["/testsuite/integration-arquillian/servers/auth-server/undertow/pom.xml","/util/embedded-ldap/pom.xml"],"isTransitiveDependency":true,"dependencyTree":"org.apache.directory.server:apacheds-core-annotations:2.0.0.AM26;org.apache.directory.mavibot:mavibot:1.0.0-M8;commons-collections:commons-collections:3.2.1","isMinimumFixVersionAvailable":true,"minimumFixVersion":"org.apache.synapse:Apache-Synapse:3.0.1;commons-collections:commons-collections:3.2.2"}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2017-15708","vulnerabilityDetails":"In Apache Synapse, by default no authentication is required for Java Remote Method Invocation (RMI). So Apache Synapse 3.0.1 or all previous releases (3.0.0, 2.1.0, 2.0.0, 1.2, 1.1.2, 1.1.1) allows remote code execution attacks that can be performed by injecting specially crafted serialized objects. And the presence of Apache Commons Collections 3.2.1 (commons-collections-3.2.1.jar) or previous versions in Synapse distribution makes this exploitable. To mitigate the issue, we need to limit RMI access to trusted users only. Further upgrading to 3.0.1 version will eliminate the risk of having said Commons Collection version. In Synapse 3.0.1, Commons Collection has been updated to 3.2.2 version.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2017-15708","cvss3Severity":"high","cvss3Score":"9.8","cvss3Metrics":{"A":"High","AC":"Low","PR":"None","S":"Unchanged","C":"High","UI":"None","AV":"Network","I":"High"},"extraData":{}}</REMEDIATE> -->
non_priority
cve high detected in commons collections jar cve high severity vulnerability vulnerable library commons collections jar types that extend and augment the java collections framework path to dependency file keycloak testsuite integration arquillian servers auth server undertow pom xml path to vulnerable library home wss scanner repository commons collections commons collections commons collections jar home wss scanner repository commons collections commons collections commons collections jar dependency hierarchy apacheds core annotations jar root library mavibot jar x commons collections jar vulnerable library found in base branch master vulnerability details in apache synapse by default no authentication is required for java remote method invocation rmi so apache synapse or all previous releases allows remote code execution attacks that can be performed by injecting specially crafted serialized objects and the presence of apache commons collections commons collections jar or previous versions in synapse distribution makes this exploitable to mitigate the issue we need to limit rmi access to trusted users only further upgrading to version will eliminate the risk of having said commons collection version in synapse commons collection has been updated to version publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact high integrity impact high availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution org apache synapse apache synapse commons collections commons collections isopenpronvulnerability true ispackagebased true isdefaultbranch true packages istransitivedependency true dependencytree org apache directory server apacheds core annotations org apache directory mavibot mavibot commons collections commons collections isminimumfixversionavailable true minimumfixversion org apache synapse apache synapse commons collections commons collections basebranches vulnerabilityidentifier cve vulnerabilitydetails in apache synapse by default no authentication is required for java remote method invocation rmi so apache synapse or all previous releases allows remote code execution attacks that can be performed by injecting specially crafted serialized objects and the presence of apache commons collections commons collections jar or previous versions in synapse distribution makes this exploitable to mitigate the issue we need to limit rmi access to trusted users only further upgrading to version will eliminate the risk of having said commons collection version in synapse commons collection has been updated to version vulnerabilityurl
0
34,339
6,312,243,186
IssuesEvent
2017-07-24 02:17:49
dgraph-io/dgraph
https://api.github.com/repos/dgraph-io/dgraph
closed
Improve documentation for sharding
documentation in progress
ERROR: type should be string, got "https://wiki.dgraph.io/Deploy#Data_sharding contains a fair bit of information about sharding, but some concepts are still a bit unclear.\r\n\r\n- If we want to configure the shard calculation, we use `default: fp % N + k`. It would be nice to have some information on how `N` and `k` should be chosen.\r\n\r\n- The documentation also gives an example of starting a clustered node: `dgraph --groups \"0,1,2\" --idx 4 --peer \"<ip address>:<port>\" --my \"ip-address-others-should-access-me-at\"` Will there be any adverse effects if a node is restarted with a different list of groups?\r\n- The documentation also states that each group must be served by 1,3, or 5 servers, which can be hard to manage operationally. Are there any adverse effects if we just run a cluster with the default groups on all of them `--groups 0,1`?"
1.0
Improve documentation for sharding - https://wiki.dgraph.io/Deploy#Data_sharding contains a fair bit of information about sharding, but some concepts are still a bit unclear. - If we want to configure the shard calculation, we use `default: fp % N + k`. It would be nice to have some information on how `N` and `k` should be chosen. - The documentation also gives an example of starting a clustered node: `dgraph --groups "0,1,2" --idx 4 --peer "<ip address>:<port>" --my "ip-address-others-should-access-me-at"` Will there be any adverse effects if a node is restarted with a different list of groups? - The documentation also states that each group must be served by 1,3, or 5 servers, which can be hard to manage operationally. Are there any adverse effects if we just run a cluster with the default groups on all of them `--groups 0,1`?
non_priority
improve documentation for sharding contains a fair bit of information about sharding but some concepts are still a bit unclear if we want to configure the shard calculation we use default fp n k it would be nice to have some information on how n and k should be chosen the documentation also gives an example of starting a clustered node dgraph groups idx peer my ip address others should access me at will there be any adverse effects if a node is restarted with a different list of groups the documentation also states that each group must be served by or servers which can be hard to manage operationally are there any adverse effects if we just run a cluster with the default groups on all of them groups
0
160,392
12,510,180,214
IssuesEvent
2020-06-02 18:11:13
awslabs/s2n
https://api.github.com/repos/awslabs/s2n
opened
Migrate PQ handshake test to integ V2
type/integration_test
### Problem: The PQ handshake test should be migrated to the integv2 framework. We should detect whether or not S2N was built with PQ support, and skip the test if it wasn't. ### Solution: Migrate the test. If a libOQS provider is available, test against that provider. (#1765) ### Requirements / Acceptance Criteria: ### Out of scope: If a libOQS provider has not yet been written, that part can be skipped. A new issue should be opened to test s2n against libOQS. [//]: # (NOTE: If you believe this might be a security issue, please email aws-security@amazon.com instead of creating a GitHub issue. For more details, see the AWS Vulnerability Reporting Guide: https://aws.amazon.com/security/vulnerability-reporting/ )
1.0
Migrate PQ handshake test to integ V2 - ### Problem: The PQ handshake test should be migrated to the integv2 framework. We should detect whether or not S2N was built with PQ support, and skip the test if it wasn't. ### Solution: Migrate the test. If a libOQS provider is available, test against that provider. (#1765) ### Requirements / Acceptance Criteria: ### Out of scope: If a libOQS provider has not yet been written, that part can be skipped. A new issue should be opened to test s2n against libOQS. [//]: # (NOTE: If you believe this might be a security issue, please email aws-security@amazon.com instead of creating a GitHub issue. For more details, see the AWS Vulnerability Reporting Guide: https://aws.amazon.com/security/vulnerability-reporting/ )
non_priority
migrate pq handshake test to integ problem the pq handshake test should be migrated to the framework we should detect whether or not was built with pq support and skip the test if it wasn t solution migrate the test if a liboqs provider is available test against that provider requirements acceptance criteria out of scope if a liboqs provider has not yet been written that part can be skipped a new issue should be opened to test against liboqs note if you believe this might be a security issue please email aws security amazon com instead of creating a github issue for more details see the aws vulnerability reporting guide
0
74,483
15,349,990,681
IssuesEvent
2021-03-01 01:03:14
TreyM-WSS/concord
https://api.github.com/repos/TreyM-WSS/concord
opened
CVE-2020-27223 (Medium) detected in jetty-http-9.4.26.v20200117.jar
security vulnerability
## CVE-2020-27223 - Medium Severity Vulnerability <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>jetty-http-9.4.26.v20200117.jar</b></p></summary> <p>The Eclipse Jetty Project</p> <p>Library home page: <a href="http://www.eclipse.org/jetty">http://www.eclipse.org/jetty</a></p> <p>Path to dependency file: concord/server/queue-client/pom.xml</p> <p>Path to vulnerable library: /home/wss-scanner/.m2/repository/org/eclipse/jetty/jetty-http/9.4.26.v20200117/jetty-http-9.4.26.v20200117.jar,/home/wss-scanner/.m2/repository/org/eclipse/jetty/jetty-http/9.4.26.v20200117/jetty-http-9.4.26.v20200117.jar</p> <p> Dependency Hierarchy: - jetty-client-9.4.26.v20200117.jar (Root Library) - :x: **jetty-http-9.4.26.v20200117.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> In Eclipse Jetty 9.4.6.v20170531 to 9.4.36.v20210114 (inclusive), 10.0.0, and 11.0.0 when Jetty handles a request containing multiple Accept headers with a large number of “quality� (i.e. q) parameters, the server may enter a denial of service (DoS) state due to high CPU usage processing those quality values, resulting in minutes of CPU time exhausted processing those quality values. <p>Publish Date: 2021-02-26 <p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-27223>CVE-2020-27223</a></p> </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.3</b>)</summary> <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: None - Integrity Impact: Low - Availability Impact: None </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary> <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://github.com/eclipse/jetty.project/security/advisories/GHSA-m394-8rww-3jr7">https://github.com/eclipse/jetty.project/security/advisories/GHSA-m394-8rww-3jr7</a></p> <p>Release Date: 2021-02-26</p> <p>Fix Resolution: org.eclipse.jetty:jetty-http:9.4.37.v20210219, org.eclipse.jetty:jetty-http:10.0.1, org.eclipse.jetty:jetty-http:11.0.1</p> </p> </details> <p></p> <!-- <REMEDIATE>{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"Java","groupId":"org.eclipse.jetty","packageName":"jetty-http","packageVersion":"9.4.26.v20200117","packageFilePaths":["/server/queue-client/pom.xml","/docker-images/agent/pom.xml"],"isTransitiveDependency":true,"dependencyTree":"org.eclipse.jetty:jetty-client:9.4.26.v20200117;org.eclipse.jetty:jetty-http:9.4.26.v20200117","isMinimumFixVersionAvailable":true,"minimumFixVersion":"org.eclipse.jetty:jetty-http:9.4.37.v20210219, org.eclipse.jetty:jetty-http:10.0.1, org.eclipse.jetty:jetty-http:11.0.1"}],"baseBranches":[],"vulnerabilityIdentifier":"CVE-2020-27223","vulnerabilityDetails":"In Eclipse Jetty 9.4.6.v20170531 to 9.4.36.v20210114 (inclusive), 10.0.0, and 11.0.0 when Jetty handles a request containing multiple Accept headers with a large number of “quality� (i.e. q) parameters, the server may enter a denial of service (DoS) state due to high CPU usage processing those quality values, resulting in minutes of CPU time exhausted processing those quality values.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-27223","cvss3Severity":"medium","cvss3Score":"5.3","cvss3Metrics":{"A":"None","AC":"Low","PR":"None","S":"Unchanged","C":"None","UI":"None","AV":"Network","I":"Low"},"extraData":{}}</REMEDIATE> -->
True
CVE-2020-27223 (Medium) detected in jetty-http-9.4.26.v20200117.jar - ## CVE-2020-27223 - Medium Severity Vulnerability <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>jetty-http-9.4.26.v20200117.jar</b></p></summary> <p>The Eclipse Jetty Project</p> <p>Library home page: <a href="http://www.eclipse.org/jetty">http://www.eclipse.org/jetty</a></p> <p>Path to dependency file: concord/server/queue-client/pom.xml</p> <p>Path to vulnerable library: /home/wss-scanner/.m2/repository/org/eclipse/jetty/jetty-http/9.4.26.v20200117/jetty-http-9.4.26.v20200117.jar,/home/wss-scanner/.m2/repository/org/eclipse/jetty/jetty-http/9.4.26.v20200117/jetty-http-9.4.26.v20200117.jar</p> <p> Dependency Hierarchy: - jetty-client-9.4.26.v20200117.jar (Root Library) - :x: **jetty-http-9.4.26.v20200117.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> In Eclipse Jetty 9.4.6.v20170531 to 9.4.36.v20210114 (inclusive), 10.0.0, and 11.0.0 when Jetty handles a request containing multiple Accept headers with a large number of “quality� (i.e. q) parameters, the server may enter a denial of service (DoS) state due to high CPU usage processing those quality values, resulting in minutes of CPU time exhausted processing those quality values. <p>Publish Date: 2021-02-26 <p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-27223>CVE-2020-27223</a></p> </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.3</b>)</summary> <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: None - Integrity Impact: Low - Availability Impact: None </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary> <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://github.com/eclipse/jetty.project/security/advisories/GHSA-m394-8rww-3jr7">https://github.com/eclipse/jetty.project/security/advisories/GHSA-m394-8rww-3jr7</a></p> <p>Release Date: 2021-02-26</p> <p>Fix Resolution: org.eclipse.jetty:jetty-http:9.4.37.v20210219, org.eclipse.jetty:jetty-http:10.0.1, org.eclipse.jetty:jetty-http:11.0.1</p> </p> </details> <p></p> <!-- <REMEDIATE>{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"Java","groupId":"org.eclipse.jetty","packageName":"jetty-http","packageVersion":"9.4.26.v20200117","packageFilePaths":["/server/queue-client/pom.xml","/docker-images/agent/pom.xml"],"isTransitiveDependency":true,"dependencyTree":"org.eclipse.jetty:jetty-client:9.4.26.v20200117;org.eclipse.jetty:jetty-http:9.4.26.v20200117","isMinimumFixVersionAvailable":true,"minimumFixVersion":"org.eclipse.jetty:jetty-http:9.4.37.v20210219, org.eclipse.jetty:jetty-http:10.0.1, org.eclipse.jetty:jetty-http:11.0.1"}],"baseBranches":[],"vulnerabilityIdentifier":"CVE-2020-27223","vulnerabilityDetails":"In Eclipse Jetty 9.4.6.v20170531 to 9.4.36.v20210114 (inclusive), 10.0.0, and 11.0.0 when Jetty handles a request containing multiple Accept headers with a large number of “quality� (i.e. q) parameters, the server may enter a denial of service (DoS) state due to high CPU usage processing those quality values, resulting in minutes of CPU time exhausted processing those quality values.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-27223","cvss3Severity":"medium","cvss3Score":"5.3","cvss3Metrics":{"A":"None","AC":"Low","PR":"None","S":"Unchanged","C":"None","UI":"None","AV":"Network","I":"Low"},"extraData":{}}</REMEDIATE> -->
non_priority
cve medium detected in jetty http jar cve medium severity vulnerability vulnerable library jetty http jar the eclipse jetty project library home page a href path to dependency file concord server queue client pom xml path to vulnerable library home wss scanner repository org eclipse jetty jetty http jetty http jar home wss scanner repository org eclipse jetty jetty http jetty http jar dependency hierarchy jetty client jar root library x jetty http jar vulnerable library vulnerability details in eclipse jetty to inclusive and when jetty handles a request containing multiple accept headers with a large number of “quality†i e q parameters the server may enter a denial of service dos state due to high cpu usage processing those quality values resulting in minutes of cpu time exhausted processing those quality values publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact none integrity impact low availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution org eclipse jetty jetty http org eclipse jetty jetty http org eclipse jetty jetty http isopenpronvulnerability true ispackagebased true isdefaultbranch true packages istransitivedependency true dependencytree org eclipse jetty jetty client org eclipse jetty jetty http isminimumfixversionavailable true minimumfixversion org eclipse jetty jetty http org eclipse jetty jetty http org eclipse jetty jetty http basebranches vulnerabilityidentifier cve vulnerabilitydetails in eclipse jetty to inclusive and when jetty handles a request containing multiple accept headers with a large number of “quality†i e q parameters the server may enter a denial of service dos state due to high cpu usage processing those quality values resulting in minutes of cpu time exhausted processing those quality values vulnerabilityurl
0
168,045
20,740,881,392
IssuesEvent
2022-03-14 17:33:39
jgeraigery/experian-java-2
https://api.github.com/repos/jgeraigery/experian-java-2
opened
CVE-2019-12384 (Medium) detected in jackson-databind-2.9.2.jar
security vulnerability
## CVE-2019-12384 - Medium Severity Vulnerability <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>jackson-databind-2.9.2.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: /MavenWorkspace/bis-services-lib/bis-services-base/pom.xml</p> <p>Path to vulnerable library: /itory/com/fasterxml/jackson/core/jackson-databind/2.9.2/jackson-databind-2.9.2.jar</p> <p> Dependency Hierarchy: - :x: **jackson-databind-2.9.2.jar** (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/jgeraigery/experian-java-2/commit/49c5a11e4b6306fbd0e55f77c7f6b9773ee8bc52">49c5a11e4b6306fbd0e55f77c7f6b9773ee8bc52</a></p> <p>Found in base branch: <b>master</b></p> </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary> <p> FasterXML jackson-databind 2.x before 2.9.9.1 might allow attackers to have a variety of impacts by leveraging failure to block the logback-core class from polymorphic deserialization. Depending on the classpath content, remote code execution may be possible. <p>Publish Date: 2019-06-24 <p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-12384>CVE-2019-12384</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: 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-12384">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-12384</a></p> <p>Release Date: 2020-10-20</p> <p>Fix Resolution: 2.9.9.1</p> </p> </details> <p></p> *** :rescue_worker_helmet: Automatic Remediation is available for this issue <!-- <REMEDIATE>{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"Java","groupId":"com.fasterxml.jackson.core","packageName":"jackson-databind","packageVersion":"2.9.2","packageFilePaths":["/MavenWorkspace/bis-services-lib/bis-services-base/pom.xml"],"isTransitiveDependency":false,"dependencyTree":"com.fasterxml.jackson.core:jackson-databind:2.9.2","isMinimumFixVersionAvailable":true,"minimumFixVersion":"2.9.9.1","isBinary":false}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2019-12384","vulnerabilityDetails":"FasterXML jackson-databind 2.x before 2.9.9.1 might allow attackers to have a variety of impacts by leveraging failure to block the logback-core class from polymorphic deserialization. Depending on the classpath content, remote code execution may be possible.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-12384","cvss3Severity":"medium","cvss3Score":"5.9","cvss3Metrics":{"A":"None","AC":"High","PR":"None","S":"Unchanged","C":"High","UI":"None","AV":"Network","I":"None"},"extraData":{}}</REMEDIATE> -->
True
CVE-2019-12384 (Medium) detected in jackson-databind-2.9.2.jar - ## CVE-2019-12384 - Medium Severity Vulnerability <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>jackson-databind-2.9.2.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: /MavenWorkspace/bis-services-lib/bis-services-base/pom.xml</p> <p>Path to vulnerable library: /itory/com/fasterxml/jackson/core/jackson-databind/2.9.2/jackson-databind-2.9.2.jar</p> <p> Dependency Hierarchy: - :x: **jackson-databind-2.9.2.jar** (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/jgeraigery/experian-java-2/commit/49c5a11e4b6306fbd0e55f77c7f6b9773ee8bc52">49c5a11e4b6306fbd0e55f77c7f6b9773ee8bc52</a></p> <p>Found in base branch: <b>master</b></p> </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary> <p> FasterXML jackson-databind 2.x before 2.9.9.1 might allow attackers to have a variety of impacts by leveraging failure to block the logback-core class from polymorphic deserialization. Depending on the classpath content, remote code execution may be possible. <p>Publish Date: 2019-06-24 <p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-12384>CVE-2019-12384</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: 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-12384">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-12384</a></p> <p>Release Date: 2020-10-20</p> <p>Fix Resolution: 2.9.9.1</p> </p> </details> <p></p> *** :rescue_worker_helmet: Automatic Remediation is available for this issue <!-- <REMEDIATE>{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"Java","groupId":"com.fasterxml.jackson.core","packageName":"jackson-databind","packageVersion":"2.9.2","packageFilePaths":["/MavenWorkspace/bis-services-lib/bis-services-base/pom.xml"],"isTransitiveDependency":false,"dependencyTree":"com.fasterxml.jackson.core:jackson-databind:2.9.2","isMinimumFixVersionAvailable":true,"minimumFixVersion":"2.9.9.1","isBinary":false}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2019-12384","vulnerabilityDetails":"FasterXML jackson-databind 2.x before 2.9.9.1 might allow attackers to have a variety of impacts by leveraging failure to block the logback-core class from polymorphic deserialization. Depending on the classpath content, remote code execution may be possible.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-12384","cvss3Severity":"medium","cvss3Score":"5.9","cvss3Metrics":{"A":"None","AC":"High","PR":"None","S":"Unchanged","C":"High","UI":"None","AV":"Network","I":"None"},"extraData":{}}</REMEDIATE> -->
non_priority
cve medium detected in jackson databind jar cve medium severity vulnerability vulnerable library jackson databind jar general data binding functionality for jackson works on core streaming api library home page a href path to dependency file mavenworkspace bis services lib bis services base pom xml path to vulnerable library itory com fasterxml jackson core jackson databind jackson databind jar dependency hierarchy x jackson databind jar vulnerable library found in head commit a href found in base branch master vulnerability details fasterxml jackson databind x before might allow attackers to have a variety of impacts by leveraging failure to block the logback core class from polymorphic deserialization depending on the classpath content remote code execution may be possible publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity high privileges required none user interaction none scope unchanged impact metrics confidentiality impact high integrity impact none availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution rescue worker helmet automatic remediation is available for this issue isopenpronvulnerability true ispackagebased true isdefaultbranch true packages istransitivedependency false dependencytree com fasterxml jackson core jackson databind isminimumfixversionavailable true minimumfixversion isbinary false basebranches vulnerabilityidentifier cve vulnerabilitydetails fasterxml jackson databind x before might allow attackers to have a variety of impacts by leveraging failure to block the logback core class from polymorphic deserialization depending on the classpath content remote code execution may be possible vulnerabilityurl
0
90,320
15,856,107,090
IssuesEvent
2021-04-08 01:32:12
KingdomB/liri-node-app
https://api.github.com/repos/KingdomB/liri-node-app
opened
CVE-2019-13173 (High) detected in fstream-1.0.11.tgz
security vulnerability
## CVE-2019-13173 - High Severity Vulnerability <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>fstream-1.0.11.tgz</b></p></summary> <p>Advanced file system stream things</p> <p>Library home page: <a href="https://registry.npmjs.org/fstream/-/fstream-1.0.11.tgz">https://registry.npmjs.org/fstream/-/fstream-1.0.11.tgz</a></p> <p>Path to dependency file: /liri-node-app/package.json</p> <p>Path to vulnerable library: liri-node-app/node_modules/npm/node_modules/fstream/package.json</p> <p> Dependency Hierarchy: - npm-6.9.0.tgz (Root Library) - node-gyp-3.8.0.tgz - :x: **fstream-1.0.11.tgz** (Vulnerable Library) </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary> <p> fstream before 1.0.12 is vulnerable to Arbitrary File Overwrite. Extracting tarballs containing a hardlink to a file that already exists in the system, and a file that matches the hardlink, will overwrite the system's file with the contents of the extracted file. The fstream.DirWriter() function is vulnerable. <p>Publish Date: 2019-07-02 <p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-13173>CVE-2019-13173</a></p> </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary> <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: None - Integrity Impact: High - Availability Impact: None </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary> <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-13173">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-13173</a></p> <p>Release Date: 2019-07-02</p> <p>Fix Resolution: 1.0.12</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-13173 (High) detected in fstream-1.0.11.tgz - ## CVE-2019-13173 - High Severity Vulnerability <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>fstream-1.0.11.tgz</b></p></summary> <p>Advanced file system stream things</p> <p>Library home page: <a href="https://registry.npmjs.org/fstream/-/fstream-1.0.11.tgz">https://registry.npmjs.org/fstream/-/fstream-1.0.11.tgz</a></p> <p>Path to dependency file: /liri-node-app/package.json</p> <p>Path to vulnerable library: liri-node-app/node_modules/npm/node_modules/fstream/package.json</p> <p> Dependency Hierarchy: - npm-6.9.0.tgz (Root Library) - node-gyp-3.8.0.tgz - :x: **fstream-1.0.11.tgz** (Vulnerable Library) </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary> <p> fstream before 1.0.12 is vulnerable to Arbitrary File Overwrite. Extracting tarballs containing a hardlink to a file that already exists in the system, and a file that matches the hardlink, will overwrite the system's file with the contents of the extracted file. The fstream.DirWriter() function is vulnerable. <p>Publish Date: 2019-07-02 <p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-13173>CVE-2019-13173</a></p> </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary> <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: None - Integrity Impact: High - Availability Impact: None </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary> <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-13173">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-13173</a></p> <p>Release Date: 2019-07-02</p> <p>Fix Resolution: 1.0.12</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 fstream tgz cve high severity vulnerability vulnerable library fstream tgz advanced file system stream things library home page a href path to dependency file liri node app package json path to vulnerable library liri node app node modules npm node modules fstream package json dependency hierarchy npm tgz root library node gyp tgz x fstream tgz vulnerable library vulnerability details fstream before is vulnerable to arbitrary file overwrite extracting tarballs containing a hardlink to a file that already exists in the system and a file that matches the hardlink will overwrite the system s file with the contents of the extracted file the fstream dirwriter function is vulnerable publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact none integrity impact high availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution step up your open source security game with whitesource
0
317,210
23,669,024,761
IssuesEvent
2022-08-27 03:49:48
ietf-wg-dmarc/draft-ietf-dmarc-dmarcbis
https://api.github.com/repos/ietf-wg-dmarc/draft-ietf-dmarc-dmarcbis
closed
Applicability
documentation minor component: dmarc-bis
Say something about when to use DMARC and the problems it causes when used badly.
1.0
Applicability - Say something about when to use DMARC and the problems it causes when used badly.
non_priority
applicability say something about when to use dmarc and the problems it causes when used badly
0
38,301
8,453,195,421
IssuesEvent
2018-10-20 13:19:37
joomla/joomla-cms
https://api.github.com/repos/joomla/joomla-cms
closed
[com_privacy] Once a request is confirmed, its confirm_token is not removed from the db
No Code Attached Yet
### Steps to reproduce the issue Joomla 3.9 Request an export of your data Confirm that request ### Expected result The confirm_token is removed from the database once used to confirm your request. It is no longer needed, just taking up space, and as it was used as a token, should be removed. ### Actual result The token remains in the db E.g `$2y$10$H8JDZa3vV6k0DV/g0Gr6ZeHptmW1MJ9Lfn/f1YHmP3YFqcvQP.C1y`
1.0
[com_privacy] Once a request is confirmed, its confirm_token is not removed from the db - ### Steps to reproduce the issue Joomla 3.9 Request an export of your data Confirm that request ### Expected result The confirm_token is removed from the database once used to confirm your request. It is no longer needed, just taking up space, and as it was used as a token, should be removed. ### Actual result The token remains in the db E.g `$2y$10$H8JDZa3vV6k0DV/g0Gr6ZeHptmW1MJ9Lfn/f1YHmP3YFqcvQP.C1y`
non_priority
once a request is confirmed its confirm token is not removed from the db steps to reproduce the issue joomla request an export of your data confirm that request expected result the confirm token is removed from the database once used to confirm your request it is no longer needed just taking up space and as it was used as a token should be removed actual result the token remains in the db e g
0
114,091
14,530,233,747
IssuesEvent
2020-12-14 18:57:42
Opentrons/opentrons
https://api.github.com/repos/Opentrons/opentrons
opened
feat: Ability to specify height during blow out in PD
:spider: SPDDRS feature-request protocol designer
<!-- Thanks for taking the time to file a feature request! Please make sure you've read the "Opening Issues" section of our Contributing Guide: https://github.com/Opentrons/opentrons/blob/edge/CONTRIBUTING.md#opening-issues To ensure your issue can be addressed quickly, please fill out the sections below to the best of your ability! --> # Overview Blow out occurs at the top of the labware well in PD protocols and cannot be changed. Users have asked if there is a way to specify the height of the pipette during blow out so they can lower it from the default height. Some users expect this to already be an option for blow out since the pipette height can be specified for the aspirate and dispense steps of a transfer. <!-- Use this section to describe your issue at a high level. Please include some context about why you want this feature. What would this feature allow you to accomplish? Are there any workarounds you use to partially achieve your goal? Are there any issues you could find that may be related? --> <!-- List any implementation steps, specs, or links to docs here. -->
1.0
feat: Ability to specify height during blow out in PD - <!-- Thanks for taking the time to file a feature request! Please make sure you've read the "Opening Issues" section of our Contributing Guide: https://github.com/Opentrons/opentrons/blob/edge/CONTRIBUTING.md#opening-issues To ensure your issue can be addressed quickly, please fill out the sections below to the best of your ability! --> # Overview Blow out occurs at the top of the labware well in PD protocols and cannot be changed. Users have asked if there is a way to specify the height of the pipette during blow out so they can lower it from the default height. Some users expect this to already be an option for blow out since the pipette height can be specified for the aspirate and dispense steps of a transfer. <!-- Use this section to describe your issue at a high level. Please include some context about why you want this feature. What would this feature allow you to accomplish? Are there any workarounds you use to partially achieve your goal? Are there any issues you could find that may be related? --> <!-- List any implementation steps, specs, or links to docs here. -->
non_priority
feat ability to specify height during blow out in pd thanks for taking the time to file a feature request please make sure you ve read the opening issues section of our contributing guide to ensure your issue can be addressed quickly please fill out the sections below to the best of your ability overview blow out occurs at the top of the labware well in pd protocols and cannot be changed users have asked if there is a way to specify the height of the pipette during blow out so they can lower it from the default height some users expect this to already be an option for blow out since the pipette height can be specified for the aspirate and dispense steps of a transfer use this section to describe your issue at a high level please include some context about why you want this feature what would this feature allow you to accomplish are there any workarounds you use to partially achieve your goal are there any issues you could find that may be related list any implementation steps specs or links to docs here
0
192,708
14,626,909,921
IssuesEvent
2020-12-23 11:13:51
Cookie-AutoDelete/Cookie-AutoDelete
https://api.github.com/repos/Cookie-AutoDelete/Cookie-AutoDelete
opened
[BUG] Clean's dropdown menu doesnt fit (v3.5.1)
untested bug/issue
When I click to Clean's dropdown menu, it opens up but doesnt fit to the screen. I'm using 1920x1080 but I've just tried in different resolutions, and it still occurs. ![cookieautodelete](https://user-images.githubusercontent.com/75943932/102990743-f4066400-4528-11eb-9cbf-5176fc6cb111.gif) I've uploaded the gif to imgur, as well: [https://imgur.com/a/7HQTxMC](https://imgur.com/a/7HQTxMC)
1.0
[BUG] Clean's dropdown menu doesnt fit (v3.5.1) - When I click to Clean's dropdown menu, it opens up but doesnt fit to the screen. I'm using 1920x1080 but I've just tried in different resolutions, and it still occurs. ![cookieautodelete](https://user-images.githubusercontent.com/75943932/102990743-f4066400-4528-11eb-9cbf-5176fc6cb111.gif) I've uploaded the gif to imgur, as well: [https://imgur.com/a/7HQTxMC](https://imgur.com/a/7HQTxMC)
non_priority
clean s dropdown menu doesnt fit when i click to clean s dropdown menu it opens up but doesnt fit to the screen i m using but i ve just tried in different resolutions and it still occurs i ve uploaded the gif to imgur as well
0
98,483
20,739,661,599
IssuesEvent
2022-03-14 16:31:34
paulevsGitch/BCLib
https://api.github.com/repos/paulevsGitch/BCLib
closed
[Compatibility] Incompatibility with NoFog mod
compatibility in dev code
I downloaded [NoFog](https://www.curseforge.com/minecraft/mc-mods/nofog) mod and then entered the end dimension with Better End mod, but the fog is still there like the following screenshots. Minecraft version: 1.18.1 / Fabric Loader version: 0.12.12 / Fabric API version: 0.45.2 Better End version: 1.0.0 / BCLib version: 1.2.4 / [NoFog version: 1.2.0](https://www.curseforge.com/minecraft/mc-mods/nofog/files/3599894) ![2022-01-17_00 15 43](https://user-images.githubusercontent.com/96723542/149771312-ce734839-e54a-4244-910b-3d90e67572ae.png) ![2022-01-16_23 52 50](https://user-images.githubusercontent.com/96723542/149771322-633de020-9802-45bb-ae3d-ce2dc384a0b8.png) ![2022-01-17_00 15 23](https://user-images.githubusercontent.com/96723542/149771327-4ffb03de-bada-4774-b753-2b25ffe6f1ca.png)
1.0
[Compatibility] Incompatibility with NoFog mod - I downloaded [NoFog](https://www.curseforge.com/minecraft/mc-mods/nofog) mod and then entered the end dimension with Better End mod, but the fog is still there like the following screenshots. Minecraft version: 1.18.1 / Fabric Loader version: 0.12.12 / Fabric API version: 0.45.2 Better End version: 1.0.0 / BCLib version: 1.2.4 / [NoFog version: 1.2.0](https://www.curseforge.com/minecraft/mc-mods/nofog/files/3599894) ![2022-01-17_00 15 43](https://user-images.githubusercontent.com/96723542/149771312-ce734839-e54a-4244-910b-3d90e67572ae.png) ![2022-01-16_23 52 50](https://user-images.githubusercontent.com/96723542/149771322-633de020-9802-45bb-ae3d-ce2dc384a0b8.png) ![2022-01-17_00 15 23](https://user-images.githubusercontent.com/96723542/149771327-4ffb03de-bada-4774-b753-2b25ffe6f1ca.png)
non_priority
incompatibility with nofog mod i downloaded mod and then entered the end dimension with better end mod but the fog is still there like the following screenshots minecraft version fabric loader version fabric api version better end version bclib version
0
37,442
18,393,489,958
IssuesEvent
2021-10-12 08:45:37
OpenNMT/OpenNMT-tf
https://api.github.com/repos/OpenNMT/OpenNMT-tf
closed
Lower throughput than expected in multi-GPU training with online tokenization
bug performance
There are some performance issues when training on multiple GPUs and enabling the online OpenNMT tokenization. The throughput is lower than expected and GPU usage frequently goes down to 0%. Possible workarounds: * Tokenize the data before the training * Use the `SentencePieceTokenizer` that is implemented as a TensorFlow op * Use Horovod for multi-GPU training See https://forum.opennmt.net/t/cannot-scale-well-with-multiple-gpus/4239 for a discussion and possible explanation.
True
Lower throughput than expected in multi-GPU training with online tokenization - There are some performance issues when training on multiple GPUs and enabling the online OpenNMT tokenization. The throughput is lower than expected and GPU usage frequently goes down to 0%. Possible workarounds: * Tokenize the data before the training * Use the `SentencePieceTokenizer` that is implemented as a TensorFlow op * Use Horovod for multi-GPU training See https://forum.opennmt.net/t/cannot-scale-well-with-multiple-gpus/4239 for a discussion and possible explanation.
non_priority
lower throughput than expected in multi gpu training with online tokenization there are some performance issues when training on multiple gpus and enabling the online opennmt tokenization the throughput is lower than expected and gpu usage frequently goes down to possible workarounds tokenize the data before the training use the sentencepiecetokenizer that is implemented as a tensorflow op use horovod for multi gpu training see for a discussion and possible explanation
0
453,029
32,079,668,345
IssuesEvent
2023-09-25 13:13:42
park-soo/project-board
https://api.github.com/repos/park-soo/project-board
closed
깃헙 프로젝트와 이슈 정리하기
documentation
깃헙 프로젝트를 세팅하고, 카드를 만들어 정리하자. * [x] 프로젝트 베타 만들기 * [x] 카드 목록 만들기 - 게시판 * [x] 이슈로 적절히 바꾸기
1.0
깃헙 프로젝트와 이슈 정리하기 - 깃헙 프로젝트를 세팅하고, 카드를 만들어 정리하자. * [x] 프로젝트 베타 만들기 * [x] 카드 목록 만들기 - 게시판 * [x] 이슈로 적절히 바꾸기
non_priority
깃헙 프로젝트와 이슈 정리하기 깃헙 프로젝트를 세팅하고 카드를 만들어 정리하자 프로젝트 베타 만들기 카드 목록 만들기 게시판 이슈로 적절히 바꾸기
0
44,999
9,664,071,866
IssuesEvent
2019-05-21 03:40:53
joomla/joomla-cms
https://api.github.com/repos/joomla/joomla-cms
closed
Calendar field not able to set old date
J3 Issue No Code Attached Yet
### Steps to reproduce the issue 1. Create a calendar field for an article. 2. Set the date before 1900. 3. Press enter. ### Expected result The date is set no matter how old the date is. ### Actual result The date field is cleared. ### System information (as much as possible) Clean installation of Joomla 3.7.3 ### Additional comments It might have something to do with a default value for the minyear argument. Anyway, you should be able to select older dates. Why are there even a limit to this? Also, why is the minyear only relative and no option to set fixed.
1.0
Calendar field not able to set old date - ### Steps to reproduce the issue 1. Create a calendar field for an article. 2. Set the date before 1900. 3. Press enter. ### Expected result The date is set no matter how old the date is. ### Actual result The date field is cleared. ### System information (as much as possible) Clean installation of Joomla 3.7.3 ### Additional comments It might have something to do with a default value for the minyear argument. Anyway, you should be able to select older dates. Why are there even a limit to this? Also, why is the minyear only relative and no option to set fixed.
non_priority
calendar field not able to set old date steps to reproduce the issue create a calendar field for an article set the date before press enter expected result the date is set no matter how old the date is actual result the date field is cleared system information as much as possible clean installation of joomla additional comments it might have something to do with a default value for the minyear argument anyway you should be able to select older dates why are there even a limit to this also why is the minyear only relative and no option to set fixed
0
336,120
24,487,747,160
IssuesEvent
2022-10-09 17:10:59
bycza-zagroda/track-expenses-app-frontend
https://api.github.com/repos/bycza-zagroda/track-expenses-app-frontend
closed
upgrade application version
documentation 0.2 - Version
Application version need to be updated from 0.1.0 to 0.2.0. This is in package.json
1.0
upgrade application version - Application version need to be updated from 0.1.0 to 0.2.0. This is in package.json
non_priority
upgrade application version application version need to be updated from to this is in package json
0
144,248
22,307,840,889
IssuesEvent
2022-06-13 14:26:57
department-of-veterans-affairs/va.gov-team
https://api.github.com/repos/department-of-veterans-affairs/va.gov-team
opened
[Design] Create Final Wireframes for Adding Physical Location to Pre-Check-in & Check-in Screens
design ux HCE-Checkin
## User Story We need final wireframes for adding physical location field to displays of appointment information in **PRE-CHECK-IN AND CHECK-IN** applications ## Tasks - [ ] Finalize detailed wireframes and callouts - [ ] Decide: Should a content and accessibility review be part of this ticket or separate tickets due to scope? ## Acceptance Criteria - [ ] UI review meeting with product/UX team for feature capabilities - [ ] UI review meeting with engineering for layout and callouts (can be the same meeting as above) - [ ] Wireframe available on Sketch Cloud - [ ] If the wireframes applies to an error state or text message, then update the [GitHub source of truth](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/health-care/checkin/design/text-and-error-messages.md) documentation.
1.0
[Design] Create Final Wireframes for Adding Physical Location to Pre-Check-in & Check-in Screens - ## User Story We need final wireframes for adding physical location field to displays of appointment information in **PRE-CHECK-IN AND CHECK-IN** applications ## Tasks - [ ] Finalize detailed wireframes and callouts - [ ] Decide: Should a content and accessibility review be part of this ticket or separate tickets due to scope? ## Acceptance Criteria - [ ] UI review meeting with product/UX team for feature capabilities - [ ] UI review meeting with engineering for layout and callouts (can be the same meeting as above) - [ ] Wireframe available on Sketch Cloud - [ ] If the wireframes applies to an error state or text message, then update the [GitHub source of truth](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/products/health-care/checkin/design/text-and-error-messages.md) documentation.
non_priority
create final wireframes for adding physical location to pre check in check in screens user story we need final wireframes for adding physical location field to displays of appointment information in pre check in and check in applications tasks finalize detailed wireframes and callouts decide should a content and accessibility review be part of this ticket or separate tickets due to scope acceptance criteria ui review meeting with product ux team for feature capabilities ui review meeting with engineering for layout and callouts can be the same meeting as above wireframe available on sketch cloud if the wireframes applies to an error state or text message then update the documentation
0
208,536
16,129,361,387
IssuesEvent
2021-04-29 00:26:12
PowerShell/PowerShellEditorServices
https://api.github.com/repos/PowerShell/PowerShellEditorServices
closed
Remove "All Rights Reserved" from copyright notices
Area-Documentation Issue-Bug Status: In PR
Similar to https://github.com/PowerShell/vscode-powershell/issues/2896 we should be following [Microsoft policy](https://docs.opensource.microsoft.com/content/releasing/copyright-headers.html) on our copyright notices.
1.0
Remove "All Rights Reserved" from copyright notices - Similar to https://github.com/PowerShell/vscode-powershell/issues/2896 we should be following [Microsoft policy](https://docs.opensource.microsoft.com/content/releasing/copyright-headers.html) on our copyright notices.
non_priority
remove all rights reserved from copyright notices similar to we should be following on our copyright notices
0
297,897
22,407,755,062
IssuesEvent
2022-06-18 08:16:57
yeniful/kko_okk
https://api.github.com/repos/yeniful/kko_okk
closed
README.md 파일 수정
documentation
발표 스크립트 만들면서 README.md 파일도 같이 적절히 수정할게요. 입 터는 걸로 먹고 살던 가락이 있으니 적절(?)히 수정되지 싶습니다.
1.0
README.md 파일 수정 - 발표 스크립트 만들면서 README.md 파일도 같이 적절히 수정할게요. 입 터는 걸로 먹고 살던 가락이 있으니 적절(?)히 수정되지 싶습니다.
non_priority
readme md 파일 수정 발표 스크립트 만들면서 readme md 파일도 같이 적절히 수정할게요 입 터는 걸로 먹고 살던 가락이 있으니 적절 히 수정되지 싶습니다
0
123,344
10,264,811,090
IssuesEvent
2019-08-22 17:17:46
wprig/wprig
https://api.github.com/repos/wprig/wprig
closed
assets directory structure could be improved.
css enhancement needs-testing wontfix
## Issue Overview When viewing the wprig src theme, relative src css references fail with current assets directory structure e.g. `background-image: url('../images/image.jpg');` ## Steps to Reproduce 1. Set theme to wprig source theme 2. Set a relative path in your css file. Something like this: `background-image: url('../images/image.jpg');` 3. The image can not be found because the reference in the wprig src theme would need to be: `background-image: url('../../images/src/image.jpg');` But in the dist theme it would need to be: `background-image: url('../images/src/image.jpg');` ## Possible Solution The src css references will work perfectly if we move the src assets into their own src assets directory and change the assets tree to look something like this: ``` \assets\css \assets\images \assets\js \assets-src\css \assets-src\images \assets-src\js ``` Another advantage is that it simplifies the .gitignore file a little :) ``` !/assets/ ``` vs ``` !/assets/ /assets/* !/assets/css/ /assets/css/* !/assets/css/src/ !/assets/js/ /assets/js/* !/assets/js/src/ !/assets/images/ /assets/images/* !/assets/images/src/ ```
1.0
assets directory structure could be improved. - ## Issue Overview When viewing the wprig src theme, relative src css references fail with current assets directory structure e.g. `background-image: url('../images/image.jpg');` ## Steps to Reproduce 1. Set theme to wprig source theme 2. Set a relative path in your css file. Something like this: `background-image: url('../images/image.jpg');` 3. The image can not be found because the reference in the wprig src theme would need to be: `background-image: url('../../images/src/image.jpg');` But in the dist theme it would need to be: `background-image: url('../images/src/image.jpg');` ## Possible Solution The src css references will work perfectly if we move the src assets into their own src assets directory and change the assets tree to look something like this: ``` \assets\css \assets\images \assets\js \assets-src\css \assets-src\images \assets-src\js ``` Another advantage is that it simplifies the .gitignore file a little :) ``` !/assets/ ``` vs ``` !/assets/ /assets/* !/assets/css/ /assets/css/* !/assets/css/src/ !/assets/js/ /assets/js/* !/assets/js/src/ !/assets/images/ /assets/images/* !/assets/images/src/ ```
non_priority
assets directory structure could be improved issue overview when viewing the wprig src theme relative src css references fail with current assets directory structure e g background image url images image jpg steps to reproduce set theme to wprig source theme set a relative path in your css file something like this background image url images image jpg the image can not be found because the reference in the wprig src theme would need to be background image url images src image jpg but in the dist theme it would need to be background image url images src image jpg possible solution the src css references will work perfectly if we move the src assets into their own src assets directory and change the assets tree to look something like this assets css assets images assets js assets src css assets src images assets src js another advantage is that it simplifies the gitignore file a little assets vs assets assets assets css assets css assets css src assets js assets js assets js src assets images assets images assets images src
0
23,054
4,866,401,084
IssuesEvent
2016-11-14 23:39:33
laradock/laradock
https://api.github.com/repos/laradock/laradock
closed
bash: npm: command not found (fix included)
Documentation Update
Hello! I'm having trouble using npm inside workspace container. Here's what I type in: `laradock@53b3a82a9d29:/var/www$ nvm bash: nvm: command not found` `laradock@53b3a82a9d29:/var/www$ npm bash: npm: command not found` And here's the relevant part of my `docker-compose.yml`: ``` workspace: build: context: ./workspace args: - INSTALL_XDEBUG=true - INSTALL_MONGO=true - INSTALL_NODE=true - INSTALL_YARN=false - INSTALL_DRUSH=false - INSTALL_AEROSPIKE_EXTENSION=false - COMPOSER_GLOBAL_INSTALL=false - INSTALL_WORKSPACE_SSH=true - PUID=1000 - PGID=1000 - NODE_VERSION=stable - TZ=UTC ``` I'm using windows 10 currently. **FIX** After building the workspace `docker-compose build workspace` I ran `docker-compose up -d nginx mysql redis` again to fix the issue. This should be included in the documentation, I think. Any thoughts? Regards, Nico
1.0
bash: npm: command not found (fix included) - Hello! I'm having trouble using npm inside workspace container. Here's what I type in: `laradock@53b3a82a9d29:/var/www$ nvm bash: nvm: command not found` `laradock@53b3a82a9d29:/var/www$ npm bash: npm: command not found` And here's the relevant part of my `docker-compose.yml`: ``` workspace: build: context: ./workspace args: - INSTALL_XDEBUG=true - INSTALL_MONGO=true - INSTALL_NODE=true - INSTALL_YARN=false - INSTALL_DRUSH=false - INSTALL_AEROSPIKE_EXTENSION=false - COMPOSER_GLOBAL_INSTALL=false - INSTALL_WORKSPACE_SSH=true - PUID=1000 - PGID=1000 - NODE_VERSION=stable - TZ=UTC ``` I'm using windows 10 currently. **FIX** After building the workspace `docker-compose build workspace` I ran `docker-compose up -d nginx mysql redis` again to fix the issue. This should be included in the documentation, I think. Any thoughts? Regards, Nico
non_priority
bash npm command not found fix included hello i m having trouble using npm inside workspace container here s what i type in laradock var www nvm bash nvm command not found laradock var www npm bash npm command not found and here s the relevant part of my docker compose yml workspace build context workspace args install xdebug true install mongo true install node true install yarn false install drush false install aerospike extension false composer global install false install workspace ssh true puid pgid node version stable tz utc i m using windows currently fix after building the workspace docker compose build workspace i ran docker compose up d nginx mysql redis again to fix the issue this should be included in the documentation i think any thoughts regards nico
0
63,670
26,485,468,922
IssuesEvent
2023-01-17 17:38:36
gradido/gradido
https://api.github.com/repos/gradido/gradido
closed
🐛 [Bug] falsche meta tags in public/index.html
bug service: wallet frontend
<!-- You can find the latest issue templates here https://github.com/ulfgebhardt/issue-templates --> ## 🐛 Bugreport Die Meta Tags sind doppelt drin und wie auf dem bild zu erkennen auch falsch bezeichnet. das problem liegt in der vue.config.js. das was in HtmlWebpackPlugin meta eingetragen ist .. wird fälschlicherweise in die public/index angehnagen. da wir aber in der public/index.html die <%= htmlWebpackPlugin.options.title_de %> verwenden .. ist dies in meta in den HtmlWebpackPlugin einstellungen nicht nötig dies in meta {} zu setzen. wenn also die option-tags aus dem meta {} genommen werden dann können wir dieses problem beheben das diese an die public/index.html gehangen werden. ![image](https://user-images.githubusercontent.com/1324583/176633029-b607fe1a-b5e5-458f-88c8-e85e07075161.png)
1.0
🐛 [Bug] falsche meta tags in public/index.html - <!-- You can find the latest issue templates here https://github.com/ulfgebhardt/issue-templates --> ## 🐛 Bugreport Die Meta Tags sind doppelt drin und wie auf dem bild zu erkennen auch falsch bezeichnet. das problem liegt in der vue.config.js. das was in HtmlWebpackPlugin meta eingetragen ist .. wird fälschlicherweise in die public/index angehnagen. da wir aber in der public/index.html die <%= htmlWebpackPlugin.options.title_de %> verwenden .. ist dies in meta in den HtmlWebpackPlugin einstellungen nicht nötig dies in meta {} zu setzen. wenn also die option-tags aus dem meta {} genommen werden dann können wir dieses problem beheben das diese an die public/index.html gehangen werden. ![image](https://user-images.githubusercontent.com/1324583/176633029-b607fe1a-b5e5-458f-88c8-e85e07075161.png)
non_priority
🐛 falsche meta tags in public index html 🐛 bugreport die meta tags sind doppelt drin und wie auf dem bild zu erkennen auch falsch bezeichnet das problem liegt in der vue config js das was in htmlwebpackplugin meta eingetragen ist wird fälschlicherweise in die public index angehnagen da wir aber in der public index html die verwenden ist dies in meta in den htmlwebpackplugin einstellungen nicht nötig dies in meta zu setzen wenn also die option tags aus dem meta genommen werden dann können wir dieses problem beheben das diese an die public index html gehangen werden
0
213,087
16,509,465,480
IssuesEvent
2021-05-26 00:54:50
department-of-veterans-affairs/va.gov-team
https://api.github.com/repos/department-of-veterans-affairs/va.gov-team
opened
Contact Center Resources - Improve Product Guides
Epic Resources and support VSP-contact-center documentation
## Product Outline [Link](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/teams/vsp/teams/contact-center/product-outlines/contact-center-tier-2-and-3-support.md) This epic most closely ties to our tier 2/3 support product, but is primarily to improve a component (product guides) of the collaboration cycle owned by the product support team. We own the process of ensuring product guides are comprehensive and efficiently usable by contact center support agents. ## High Level User Story/ies As a contact center support agent, I need comprehensive and intuitive product guide to reference when Veterans call so I can solve the issues they are experience while using VA.gov. ## Hypothesis or Bet **If** _we add a clickable table of contents to product guids, update our best practices doc with that requirement, and provide a comprehensive `example product guide`_ **then** _we expect to see a reduction in time to resolution for CC support agents_. ## OKR _TBD_ ## Definition of done ### For this epic to be done, we will complete the following things: - Update existing product guide best practices doc with new requirements (i.e. clickable table of contents, table of figures and appropriate references when figures are used, title page required, consistent use of headers/sub-headers, etc.) - Update CC product guide review/request guidelines - Collab Cycle PM has been notified of changes and provide documentation - Product Guide Review template is created and made available to VFS teams *Take into consideration Accessibility/QA needs as well as Product, Technical, and Design requirements.* ## How to configure this issue - [ ] **Labeled with Team** (`product support`, `analytics-insights`, `operations`, `tools-be`, `tools-fe`,`content-ia`, `service-design`, `vsa-*`) - [ ] **Labeled with Practice Area** (`backend`, `frontend`, `devops`, `design`, `research`, `product`, `ia`, `qa`, `analytics`, `contact center`, `research`, `accessibility`, `content`)
1.0
Contact Center Resources - Improve Product Guides - ## Product Outline [Link](https://github.com/department-of-veterans-affairs/va.gov-team/blob/master/teams/vsp/teams/contact-center/product-outlines/contact-center-tier-2-and-3-support.md) This epic most closely ties to our tier 2/3 support product, but is primarily to improve a component (product guides) of the collaboration cycle owned by the product support team. We own the process of ensuring product guides are comprehensive and efficiently usable by contact center support agents. ## High Level User Story/ies As a contact center support agent, I need comprehensive and intuitive product guide to reference when Veterans call so I can solve the issues they are experience while using VA.gov. ## Hypothesis or Bet **If** _we add a clickable table of contents to product guids, update our best practices doc with that requirement, and provide a comprehensive `example product guide`_ **then** _we expect to see a reduction in time to resolution for CC support agents_. ## OKR _TBD_ ## Definition of done ### For this epic to be done, we will complete the following things: - Update existing product guide best practices doc with new requirements (i.e. clickable table of contents, table of figures and appropriate references when figures are used, title page required, consistent use of headers/sub-headers, etc.) - Update CC product guide review/request guidelines - Collab Cycle PM has been notified of changes and provide documentation - Product Guide Review template is created and made available to VFS teams *Take into consideration Accessibility/QA needs as well as Product, Technical, and Design requirements.* ## How to configure this issue - [ ] **Labeled with Team** (`product support`, `analytics-insights`, `operations`, `tools-be`, `tools-fe`,`content-ia`, `service-design`, `vsa-*`) - [ ] **Labeled with Practice Area** (`backend`, `frontend`, `devops`, `design`, `research`, `product`, `ia`, `qa`, `analytics`, `contact center`, `research`, `accessibility`, `content`)
non_priority
contact center resources improve product guides product outline this epic most closely ties to our tier support product but is primarily to improve a component product guides of the collaboration cycle owned by the product support team we own the process of ensuring product guides are comprehensive and efficiently usable by contact center support agents high level user story ies as a contact center support agent i need comprehensive and intuitive product guide to reference when veterans call so i can solve the issues they are experience while using va gov hypothesis or bet if we add a clickable table of contents to product guids update our best practices doc with that requirement and provide a comprehensive example product guide then we expect to see a reduction in time to resolution for cc support agents okr tbd definition of done for this epic to be done we will complete the following things update existing product guide best practices doc with new requirements i e clickable table of contents table of figures and appropriate references when figures are used title page required consistent use of headers sub headers etc update cc product guide review request guidelines collab cycle pm has been notified of changes and provide documentation product guide review template is created and made available to vfs teams take into consideration accessibility qa needs as well as product technical and design requirements how to configure this issue labeled with team product support analytics insights operations tools be tools fe content ia service design vsa labeled with practice area backend frontend devops design research product ia qa analytics contact center research accessibility content
0
119,811
17,633,539,498
IssuesEvent
2021-08-19 11:01:10
NixOS/nixpkgs
https://api.github.com/repos/NixOS/nixpkgs
closed
Vulnerability roundup 85: libgadu-1.11.2: 1 advisory
1.severity: security
[search](https://search.nix.gsc.io/?q=libgadu&i=fosho&repos=NixOS-nixpkgs), [files](https://github.com/NixOS/nixpkgs/search?utf8=%E2%9C%93&q=libgadu+in%3Apath&type=Code) * [ ] [CVE-2014-3775](https://nvd.nist.gov/vuln/detail/CVE-2014-3775) (nixos-20.03, nixos-unstable) Scanned versions: nixos-20.03: a84b797b28e; nixos-unstable: 22c98819ccd. May contain false positives.
True
Vulnerability roundup 85: libgadu-1.11.2: 1 advisory - [search](https://search.nix.gsc.io/?q=libgadu&i=fosho&repos=NixOS-nixpkgs), [files](https://github.com/NixOS/nixpkgs/search?utf8=%E2%9C%93&q=libgadu+in%3Apath&type=Code) * [ ] [CVE-2014-3775](https://nvd.nist.gov/vuln/detail/CVE-2014-3775) (nixos-20.03, nixos-unstable) Scanned versions: nixos-20.03: a84b797b28e; nixos-unstable: 22c98819ccd. May contain false positives.
non_priority
vulnerability roundup libgadu advisory nixos nixos unstable scanned versions nixos nixos unstable may contain false positives
0
166,436
12,955,798,650
IssuesEvent
2020-07-20 07:05:11
pywbem/nocaselist
https://api.github.com/repos/pywbem/nocaselist
closed
installtest fails on pypy3 with latest package levels
area: test resolution: partly fixed type: bug
From Travis run on pypy3 with latest package levels (see https://travis-ci.org/github/pywbem/nocaselist/jobs/709856857): ``` $ make installtest Makefile: Running install tests tests/installtest/test_install.sh dist/nocaselist-1.0.0.dev1-py2.py3-none-any.whl dist/nocaselist-1.0.0.dev1.tar.gz python Preparing for the tests Creating test directory: tests/installtest/../../tmp_installtest Creating source archive unpack directory: tests/installtest/../../tmp_installtest/src_dist Removing .egg file: tests/installtest/../../dist/nocaselist*.egg Testcase test1: Pip install from repo root directory: tests/installtest/../.. Saving location of current virtualenv: /home/travis/virtualenv/pypy3.6-7.1.1 Before creating virtualenv: tests/installtest/../../tmp_installtest/virtualenvs/nocaselist_test_test1 Python version: Python 3.6.1 (784b254d6699, Apr 14 2019, 10:22:42) [PyPy 7.1.1-beta0 with GCC 6.2.0 20160901] from /home/travis/virtualenv/pypy3.6-7.1.1/bin/python Pip version: pip 20.1.1 from /home/travis/virtualenv/pypy3.6-7.1.1/site-packages/pip (python 3.6) Creating virtualenv: tests/installtest/../../tmp_installtest/virtualenvs/nocaselist_test_test1 Activating virtualenv: tests/installtest/../../tmp_installtest/virtualenvs/nocaselist_test_test1 Error: Command failed with rc=1: source tests/installtest/../../tmp_installtest/virtualenvs/nocaselist_test_test1/bin/activate, output follows: tests/installtest/test_install.sh: line 230: tests/installtest/../../tmp_installtest/virtualenvs/nocaselist_test_test1/bin/activate: No such file or directory Makefile:573: recipe for target 'installtest' failed make: *** [installtest] Error 1 The command "make installtest" exited with 2. ```
1.0
installtest fails on pypy3 with latest package levels - From Travis run on pypy3 with latest package levels (see https://travis-ci.org/github/pywbem/nocaselist/jobs/709856857): ``` $ make installtest Makefile: Running install tests tests/installtest/test_install.sh dist/nocaselist-1.0.0.dev1-py2.py3-none-any.whl dist/nocaselist-1.0.0.dev1.tar.gz python Preparing for the tests Creating test directory: tests/installtest/../../tmp_installtest Creating source archive unpack directory: tests/installtest/../../tmp_installtest/src_dist Removing .egg file: tests/installtest/../../dist/nocaselist*.egg Testcase test1: Pip install from repo root directory: tests/installtest/../.. Saving location of current virtualenv: /home/travis/virtualenv/pypy3.6-7.1.1 Before creating virtualenv: tests/installtest/../../tmp_installtest/virtualenvs/nocaselist_test_test1 Python version: Python 3.6.1 (784b254d6699, Apr 14 2019, 10:22:42) [PyPy 7.1.1-beta0 with GCC 6.2.0 20160901] from /home/travis/virtualenv/pypy3.6-7.1.1/bin/python Pip version: pip 20.1.1 from /home/travis/virtualenv/pypy3.6-7.1.1/site-packages/pip (python 3.6) Creating virtualenv: tests/installtest/../../tmp_installtest/virtualenvs/nocaselist_test_test1 Activating virtualenv: tests/installtest/../../tmp_installtest/virtualenvs/nocaselist_test_test1 Error: Command failed with rc=1: source tests/installtest/../../tmp_installtest/virtualenvs/nocaselist_test_test1/bin/activate, output follows: tests/installtest/test_install.sh: line 230: tests/installtest/../../tmp_installtest/virtualenvs/nocaselist_test_test1/bin/activate: No such file or directory Makefile:573: recipe for target 'installtest' failed make: *** [installtest] Error 1 The command "make installtest" exited with 2. ```
non_priority
installtest fails on with latest package levels from travis run on with latest package levels see make installtest makefile running install tests tests installtest test install sh dist nocaselist none any whl dist nocaselist tar gz python preparing for the tests creating test directory tests installtest tmp installtest creating source archive unpack directory tests installtest tmp installtest src dist removing egg file tests installtest dist nocaselist egg testcase pip install from repo root directory tests installtest saving location of current virtualenv home travis virtualenv before creating virtualenv tests installtest tmp installtest virtualenvs nocaselist test python version python apr from home travis virtualenv bin python pip version pip from home travis virtualenv site packages pip python creating virtualenv tests installtest tmp installtest virtualenvs nocaselist test activating virtualenv tests installtest tmp installtest virtualenvs nocaselist test error command failed with rc source tests installtest tmp installtest virtualenvs nocaselist test bin activate output follows tests installtest test install sh line tests installtest tmp installtest virtualenvs nocaselist test bin activate no such file or directory makefile recipe for target installtest failed make error the command make installtest exited with
0
320,955
27,494,358,424
IssuesEvent
2023-03-05 01:07:46
j-c-cook/ghedt
https://api.github.com/repos/j-c-cook/ghedt
closed
Increase coverage of testing
tests
The goal of this issue is to incorporate adequate testing of `ghedt` and subsequent packages (`PLAT`). Implementing tests based on examples in my thesis (Cook 2021) will suffice.
1.0
Increase coverage of testing - The goal of this issue is to incorporate adequate testing of `ghedt` and subsequent packages (`PLAT`). Implementing tests based on examples in my thesis (Cook 2021) will suffice.
non_priority
increase coverage of testing the goal of this issue is to incorporate adequate testing of ghedt and subsequent packages plat implementing tests based on examples in my thesis cook will suffice
0
88,948
17,755,902,762
IssuesEvent
2021-08-28 18:57:52
octomation/maintainer
https://api.github.com/repos/octomation/maintainer
opened
contribution chart
difficulty: hard kind: feature scope: code
Add a possibility to fetch contribution chart from GitHub and shows appropriate date correction for git commit. ```bash $ maintainer contribution chart $ git at $(maintainer contribution next) ```
1.0
contribution chart - Add a possibility to fetch contribution chart from GitHub and shows appropriate date correction for git commit. ```bash $ maintainer contribution chart $ git at $(maintainer contribution next) ```
non_priority
contribution chart add a possibility to fetch contribution chart from github and shows appropriate date correction for git commit bash maintainer contribution chart git at maintainer contribution next
0
10,336
3,103,601,329
IssuesEvent
2015-08-31 11:06:02
sohelvali/Test-Git-Issue
https://api.github.com/repos/sohelvali/Test-Git-Issue
closed
Entresto Label not in DOC Label- please upload
test Label
Available on DailyMed  http://dailymed.nlm.nih.gov/dailymed/drugInfo.cfm?setid=000dc81d-ab91-450c-8eae-8eb74e72296f Please upload as soon as possible per client request. Thank you, Katia
1.0
Entresto Label not in DOC Label- please upload - Available on DailyMed  http://dailymed.nlm.nih.gov/dailymed/drugInfo.cfm?setid=000dc81d-ab91-450c-8eae-8eb74e72296f Please upload as soon as possible per client request. Thank you, Katia
non_priority
entresto label not in doc label please upload available on dailymed  please upload as soon as possible per client request thank you katia
0
143,468
13,065,122,261
IssuesEvent
2020-07-30 19:15:41
vilihegyi/securo
https://api.github.com/repos/vilihegyi/securo
opened
Save the database for every device - documentation
documentation good first issue
Currently the database is only stored on the device running this application. To be more blockchain like we could find a solution to keep the database stored on every device so that if someone tries to alter, everyone will know the information isn't valid and not to take the vote in account. Documentation on this.
1.0
Save the database for every device - documentation - Currently the database is only stored on the device running this application. To be more blockchain like we could find a solution to keep the database stored on every device so that if someone tries to alter, everyone will know the information isn't valid and not to take the vote in account. Documentation on this.
non_priority
save the database for every device documentation currently the database is only stored on the device running this application to be more blockchain like we could find a solution to keep the database stored on every device so that if someone tries to alter everyone will know the information isn t valid and not to take the vote in account documentation on this
0
126,571
10,427,617,097
IssuesEvent
2019-09-16 20:21:35
publiclab/plots2
https://api.github.com/repos/publiclab/plots2
closed
Email auto replies are auto-posting to research notes.
Ruby help wanted testing
### This has happened before, but email auto replies are showing up as comment responses in threads on the site. This particular email posted about 70 times, and contains information about the poster's personal schedule as well as contact information for another person. ![AutoReplyPost](https://user-images.githubusercontent.com/8331717/58979199-7ab6ed00-879b-11e9-8dea-448238f51796.gif) Can we disable auto comments in comment by email?
1.0
Email auto replies are auto-posting to research notes. - ### This has happened before, but email auto replies are showing up as comment responses in threads on the site. This particular email posted about 70 times, and contains information about the poster's personal schedule as well as contact information for another person. ![AutoReplyPost](https://user-images.githubusercontent.com/8331717/58979199-7ab6ed00-879b-11e9-8dea-448238f51796.gif) Can we disable auto comments in comment by email?
non_priority
email auto replies are auto posting to research notes this has happened before but email auto replies are showing up as comment responses in threads on the site this particular email posted about times and contains information about the poster s personal schedule as well as contact information for another person can we disable auto comments in comment by email
0
242,566
20,254,062,019
IssuesEvent
2022-02-14 21:01:02
rspott/WAF-test02
https://api.github.com/repos/rspott/WAF-test02
opened
Scan container workloads for vulnerabilities
WARP-Import test1 Security Deployment & Testing Testing & Validation
<a href="https://docs.microsoft.com/azure/security-center/container-security">Scan container workloads for vulnerabilities</a> <p><b>Why Consider This?</b></p> To build secure containerized workloads, ensure the images that they're based on are free of known vulnerabilities. Shipping a known vulnerability in a container isn't significantly safer than on a VM. <p><b>Context</b></p> <p><span>Azure Security Center / Azure Defender is the Azure-native solution for securing containers. Azure Defender can protect virtual machines that are running Docker, Azure Kubernetes Service clusters, Azure Container Registry registries. Azure Defender is able to scan container images and identify security issues, or provide real-time threat detection for containerized environments.</span></p> <p><b>Suggested Actions</b></p> <p><span>Consider using Azure Defender for securing containerized workloads.</span></p> <p><b>Learn More</b></p> <p><a href="https://docs.microsoft.com/en-us/azure/security-center/container-security" target="_blank"><span>https://docs.microsoft.com/en-us/azure/security-center/container-security</span></a><span /></p>
3.0
Scan container workloads for vulnerabilities - <a href="https://docs.microsoft.com/azure/security-center/container-security">Scan container workloads for vulnerabilities</a> <p><b>Why Consider This?</b></p> To build secure containerized workloads, ensure the images that they're based on are free of known vulnerabilities. Shipping a known vulnerability in a container isn't significantly safer than on a VM. <p><b>Context</b></p> <p><span>Azure Security Center / Azure Defender is the Azure-native solution for securing containers. Azure Defender can protect virtual machines that are running Docker, Azure Kubernetes Service clusters, Azure Container Registry registries. Azure Defender is able to scan container images and identify security issues, or provide real-time threat detection for containerized environments.</span></p> <p><b>Suggested Actions</b></p> <p><span>Consider using Azure Defender for securing containerized workloads.</span></p> <p><b>Learn More</b></p> <p><a href="https://docs.microsoft.com/en-us/azure/security-center/container-security" target="_blank"><span>https://docs.microsoft.com/en-us/azure/security-center/container-security</span></a><span /></p>
non_priority
scan container workloads for vulnerabilities why consider this to build secure containerized workloads ensure the images that they re based on are free of known vulnerabilities shipping a known vulnerability in a container isn t significantly safer than on a vm context azure security center azure defender is the azure native solution for securing containers azure defender can protect virtual machines that are running docker azure kubernetes service clusters azure container registry registries azure defender is able to scan container images and identify security issues or provide real time threat detection for containerized environments suggested actions consider using azure defender for securing containerized workloads learn more
0
201,726
23,039,619,112
IssuesEvent
2022-07-23 01:02:05
marcostolosa/marcostolosa.github.io
https://api.github.com/repos/marcostolosa/marcostolosa.github.io
opened
bootstrap-3.1.1.js: 6 vulnerabilities (highest severity is: 6.1)
security vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>bootstrap-3.1.1.js</b></p></summary> <p>The most popular front-end framework for developing responsive, mobile first projects on the web.</p> <p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/3.1.1/js/bootstrap.js">https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/3.1.1/js/bootstrap.js</a></p> <p>Path to vulnerable library: /assets/bootstrap/js/bootstrap.js</p> <p> </details> ## Vulnerabilities | CVE | Severity | <img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS | Dependency | Type | Fixed in | Remediation Available | | ------------- | ------------- | ----- | ----- | ----- | --- | --- | | [CVE-2019-8331](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-8331) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 6.1 | bootstrap-3.1.1.js | Direct | bootstrap - 3.4.1,4.3.1;bootstrap-sass - 3.4.1,4.3.1 | &#10060; | | [CVE-2018-14040](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-14040) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 6.1 | bootstrap-3.1.1.js | Direct | org.webjars.npm:bootstrap:4.1.2,org.webjars:bootstrap:3.4.0 | &#10060; | | [CVE-2018-20677](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-20677) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 6.1 | bootstrap-3.1.1.js | Direct | Bootstrap - v3.4.0;NorDroN.AngularTemplate - 0.1.6;Dynamic.NET.Express.ProjectTemplates - 0.8.0;dotnetng.template - 1.0.0.4;ZNxtApp.Core.Module.Theme - 1.0.9-Beta;JMeter - 5.0.0 | &#10060; | | [CVE-2018-14042](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-14042) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 6.1 | bootstrap-3.1.1.js | Direct | org.webjars.npm:bootstrap:4.1.2.org.webjars:bootstrap:3.4.0 | &#10060; | | [CVE-2018-20676](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-20676) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 6.1 | bootstrap-3.1.1.js | Direct | bootstrap - 3.4.0 | &#10060; | | [CVE-2016-10735](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2016-10735) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 6.1 | bootstrap-3.1.1.js | Direct | bootstrap - 3.4.0, 4.0.0-beta.2 | &#10060; | ## Details <details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2019-8331</summary> ### Vulnerable Library - <b>bootstrap-3.1.1.js</b></p> <p>The most popular front-end framework for developing responsive, mobile first projects on the web.</p> <p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/3.1.1/js/bootstrap.js">https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/3.1.1/js/bootstrap.js</a></p> <p>Path to vulnerable library: /assets/bootstrap/js/bootstrap.js</p> <p> Dependency Hierarchy: - :x: **bootstrap-3.1.1.js** (Vulnerable Library) </p> <p></p> ### Vulnerability Details <p> In Bootstrap before 3.4.1 and 4.3.x before 4.3.1, XSS is possible in the tooltip or popover data-template attribute. <p>Publish Date: 2019-02-20 <p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-8331>CVE-2019-8331</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>Release Date: 2019-02-20</p> <p>Fix Resolution: bootstrap - 3.4.1,4.3.1;bootstrap-sass - 3.4.1,4.3.1</p> </p> <p></p> Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2018-14040</summary> ### Vulnerable Library - <b>bootstrap-3.1.1.js</b></p> <p>The most popular front-end framework for developing responsive, mobile first projects on the web.</p> <p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/3.1.1/js/bootstrap.js">https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/3.1.1/js/bootstrap.js</a></p> <p>Path to vulnerable library: /assets/bootstrap/js/bootstrap.js</p> <p> Dependency Hierarchy: - :x: **bootstrap-3.1.1.js** (Vulnerable Library) </p> <p></p> ### Vulnerability Details <p> In Bootstrap before 4.1.2, XSS is possible in the collapse data-parent attribute. <p>Publish Date: 2018-07-13 <p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-14040>CVE-2018-14040</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>Release Date: 2018-07-13</p> <p>Fix Resolution: org.webjars.npm:bootstrap:4.1.2,org.webjars:bootstrap:3.4.0</p> </p> <p></p> Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2018-20677</summary> ### Vulnerable Library - <b>bootstrap-3.1.1.js</b></p> <p>The most popular front-end framework for developing responsive, mobile first projects on the web.</p> <p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/3.1.1/js/bootstrap.js">https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/3.1.1/js/bootstrap.js</a></p> <p>Path to vulnerable library: /assets/bootstrap/js/bootstrap.js</p> <p> Dependency Hierarchy: - :x: **bootstrap-3.1.1.js** (Vulnerable Library) </p> <p></p> ### Vulnerability Details <p> In Bootstrap before 3.4.0, XSS is possible in the affix configuration target property. <p>Publish Date: 2019-01-09 <p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-20677>CVE-2018-20677</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>6.1</b>) <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: Required - Scope: Changed - Impact Metrics: - Confidentiality Impact: Low - Integrity Impact: Low - Availability Impact: None </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> <p></p> ### Suggested Fix <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-20677">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-20677</a></p> <p>Release Date: 2019-01-09</p> <p>Fix Resolution: Bootstrap - v3.4.0;NorDroN.AngularTemplate - 0.1.6;Dynamic.NET.Express.ProjectTemplates - 0.8.0;dotnetng.template - 1.0.0.4;ZNxtApp.Core.Module.Theme - 1.0.9-Beta;JMeter - 5.0.0</p> </p> <p></p> Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2018-14042</summary> ### Vulnerable Library - <b>bootstrap-3.1.1.js</b></p> <p>The most popular front-end framework for developing responsive, mobile first projects on the web.</p> <p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/3.1.1/js/bootstrap.js">https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/3.1.1/js/bootstrap.js</a></p> <p>Path to vulnerable library: /assets/bootstrap/js/bootstrap.js</p> <p> Dependency Hierarchy: - :x: **bootstrap-3.1.1.js** (Vulnerable Library) </p> <p></p> ### Vulnerability Details <p> In Bootstrap before 4.1.2, XSS is possible in the data-container property of tooltip. <p>Publish Date: 2018-07-13 <p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-14042>CVE-2018-14042</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>Release Date: 2018-07-13</p> <p>Fix Resolution: org.webjars.npm:bootstrap:4.1.2.org.webjars:bootstrap:3.4.0</p> </p> <p></p> Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2018-20676</summary> ### Vulnerable Library - <b>bootstrap-3.1.1.js</b></p> <p>The most popular front-end framework for developing responsive, mobile first projects on the web.</p> <p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/3.1.1/js/bootstrap.js">https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/3.1.1/js/bootstrap.js</a></p> <p>Path to vulnerable library: /assets/bootstrap/js/bootstrap.js</p> <p> Dependency Hierarchy: - :x: **bootstrap-3.1.1.js** (Vulnerable Library) </p> <p></p> ### Vulnerability Details <p> In Bootstrap before 3.4.0, XSS is possible in the tooltip data-viewport attribute. <p>Publish Date: 2019-01-09 <p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-20676>CVE-2018-20676</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>6.1</b>) <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: Required - Scope: Changed - Impact Metrics: - Confidentiality Impact: Low - Integrity Impact: Low - Availability Impact: None </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> <p></p> ### Suggested Fix <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-20676">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-20676</a></p> <p>Release Date: 2019-01-09</p> <p>Fix Resolution: bootstrap - 3.4.0</p> </p> <p></p> Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2016-10735</summary> ### Vulnerable Library - <b>bootstrap-3.1.1.js</b></p> <p>The most popular front-end framework for developing responsive, mobile first projects on the web.</p> <p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/3.1.1/js/bootstrap.js">https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/3.1.1/js/bootstrap.js</a></p> <p>Path to vulnerable library: /assets/bootstrap/js/bootstrap.js</p> <p> Dependency Hierarchy: - :x: **bootstrap-3.1.1.js** (Vulnerable Library) </p> <p></p> ### Vulnerability Details <p> In Bootstrap 3.x before 3.4.0 and 4.x-beta before 4.0.0-beta.2, XSS is possible in the data-target attribute, a different vulnerability than CVE-2018-14041. <p>Publish Date: 2019-01-09 <p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2016-10735>CVE-2016-10735</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>6.1</b>) <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: Required - Scope: Changed - Impact Metrics: - Confidentiality Impact: Low - Integrity Impact: Low - Availability Impact: None </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> <p></p> ### Suggested Fix <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-10735">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-10735</a></p> <p>Release Date: 2019-01-09</p> <p>Fix Resolution: bootstrap - 3.4.0, 4.0.0-beta.2</p> </p> <p></p> Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) </details>
True
bootstrap-3.1.1.js: 6 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>bootstrap-3.1.1.js</b></p></summary> <p>The most popular front-end framework for developing responsive, mobile first projects on the web.</p> <p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/3.1.1/js/bootstrap.js">https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/3.1.1/js/bootstrap.js</a></p> <p>Path to vulnerable library: /assets/bootstrap/js/bootstrap.js</p> <p> </details> ## Vulnerabilities | CVE | Severity | <img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS | Dependency | Type | Fixed in | Remediation Available | | ------------- | ------------- | ----- | ----- | ----- | --- | --- | | [CVE-2019-8331](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-8331) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 6.1 | bootstrap-3.1.1.js | Direct | bootstrap - 3.4.1,4.3.1;bootstrap-sass - 3.4.1,4.3.1 | &#10060; | | [CVE-2018-14040](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-14040) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 6.1 | bootstrap-3.1.1.js | Direct | org.webjars.npm:bootstrap:4.1.2,org.webjars:bootstrap:3.4.0 | &#10060; | | [CVE-2018-20677](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-20677) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 6.1 | bootstrap-3.1.1.js | Direct | Bootstrap - v3.4.0;NorDroN.AngularTemplate - 0.1.6;Dynamic.NET.Express.ProjectTemplates - 0.8.0;dotnetng.template - 1.0.0.4;ZNxtApp.Core.Module.Theme - 1.0.9-Beta;JMeter - 5.0.0 | &#10060; | | [CVE-2018-14042](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-14042) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 6.1 | bootstrap-3.1.1.js | Direct | org.webjars.npm:bootstrap:4.1.2.org.webjars:bootstrap:3.4.0 | &#10060; | | [CVE-2018-20676](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-20676) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 6.1 | bootstrap-3.1.1.js | Direct | bootstrap - 3.4.0 | &#10060; | | [CVE-2016-10735](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2016-10735) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 6.1 | bootstrap-3.1.1.js | Direct | bootstrap - 3.4.0, 4.0.0-beta.2 | &#10060; | ## Details <details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2019-8331</summary> ### Vulnerable Library - <b>bootstrap-3.1.1.js</b></p> <p>The most popular front-end framework for developing responsive, mobile first projects on the web.</p> <p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/3.1.1/js/bootstrap.js">https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/3.1.1/js/bootstrap.js</a></p> <p>Path to vulnerable library: /assets/bootstrap/js/bootstrap.js</p> <p> Dependency Hierarchy: - :x: **bootstrap-3.1.1.js** (Vulnerable Library) </p> <p></p> ### Vulnerability Details <p> In Bootstrap before 3.4.1 and 4.3.x before 4.3.1, XSS is possible in the tooltip or popover data-template attribute. <p>Publish Date: 2019-02-20 <p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-8331>CVE-2019-8331</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>Release Date: 2019-02-20</p> <p>Fix Resolution: bootstrap - 3.4.1,4.3.1;bootstrap-sass - 3.4.1,4.3.1</p> </p> <p></p> Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2018-14040</summary> ### Vulnerable Library - <b>bootstrap-3.1.1.js</b></p> <p>The most popular front-end framework for developing responsive, mobile first projects on the web.</p> <p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/3.1.1/js/bootstrap.js">https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/3.1.1/js/bootstrap.js</a></p> <p>Path to vulnerable library: /assets/bootstrap/js/bootstrap.js</p> <p> Dependency Hierarchy: - :x: **bootstrap-3.1.1.js** (Vulnerable Library) </p> <p></p> ### Vulnerability Details <p> In Bootstrap before 4.1.2, XSS is possible in the collapse data-parent attribute. <p>Publish Date: 2018-07-13 <p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-14040>CVE-2018-14040</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>Release Date: 2018-07-13</p> <p>Fix Resolution: org.webjars.npm:bootstrap:4.1.2,org.webjars:bootstrap:3.4.0</p> </p> <p></p> Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2018-20677</summary> ### Vulnerable Library - <b>bootstrap-3.1.1.js</b></p> <p>The most popular front-end framework for developing responsive, mobile first projects on the web.</p> <p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/3.1.1/js/bootstrap.js">https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/3.1.1/js/bootstrap.js</a></p> <p>Path to vulnerable library: /assets/bootstrap/js/bootstrap.js</p> <p> Dependency Hierarchy: - :x: **bootstrap-3.1.1.js** (Vulnerable Library) </p> <p></p> ### Vulnerability Details <p> In Bootstrap before 3.4.0, XSS is possible in the affix configuration target property. <p>Publish Date: 2019-01-09 <p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-20677>CVE-2018-20677</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>6.1</b>) <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: Required - Scope: Changed - Impact Metrics: - Confidentiality Impact: Low - Integrity Impact: Low - Availability Impact: None </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> <p></p> ### Suggested Fix <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-20677">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-20677</a></p> <p>Release Date: 2019-01-09</p> <p>Fix Resolution: Bootstrap - v3.4.0;NorDroN.AngularTemplate - 0.1.6;Dynamic.NET.Express.ProjectTemplates - 0.8.0;dotnetng.template - 1.0.0.4;ZNxtApp.Core.Module.Theme - 1.0.9-Beta;JMeter - 5.0.0</p> </p> <p></p> Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2018-14042</summary> ### Vulnerable Library - <b>bootstrap-3.1.1.js</b></p> <p>The most popular front-end framework for developing responsive, mobile first projects on the web.</p> <p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/3.1.1/js/bootstrap.js">https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/3.1.1/js/bootstrap.js</a></p> <p>Path to vulnerable library: /assets/bootstrap/js/bootstrap.js</p> <p> Dependency Hierarchy: - :x: **bootstrap-3.1.1.js** (Vulnerable Library) </p> <p></p> ### Vulnerability Details <p> In Bootstrap before 4.1.2, XSS is possible in the data-container property of tooltip. <p>Publish Date: 2018-07-13 <p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-14042>CVE-2018-14042</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>Release Date: 2018-07-13</p> <p>Fix Resolution: org.webjars.npm:bootstrap:4.1.2.org.webjars:bootstrap:3.4.0</p> </p> <p></p> Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2018-20676</summary> ### Vulnerable Library - <b>bootstrap-3.1.1.js</b></p> <p>The most popular front-end framework for developing responsive, mobile first projects on the web.</p> <p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/3.1.1/js/bootstrap.js">https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/3.1.1/js/bootstrap.js</a></p> <p>Path to vulnerable library: /assets/bootstrap/js/bootstrap.js</p> <p> Dependency Hierarchy: - :x: **bootstrap-3.1.1.js** (Vulnerable Library) </p> <p></p> ### Vulnerability Details <p> In Bootstrap before 3.4.0, XSS is possible in the tooltip data-viewport attribute. <p>Publish Date: 2019-01-09 <p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-20676>CVE-2018-20676</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>6.1</b>) <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: Required - Scope: Changed - Impact Metrics: - Confidentiality Impact: Low - Integrity Impact: Low - Availability Impact: None </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> <p></p> ### Suggested Fix <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-20676">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-20676</a></p> <p>Release Date: 2019-01-09</p> <p>Fix Resolution: bootstrap - 3.4.0</p> </p> <p></p> Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) </details><details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2016-10735</summary> ### Vulnerable Library - <b>bootstrap-3.1.1.js</b></p> <p>The most popular front-end framework for developing responsive, mobile first projects on the web.</p> <p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/3.1.1/js/bootstrap.js">https://cdnjs.cloudflare.com/ajax/libs/twitter-bootstrap/3.1.1/js/bootstrap.js</a></p> <p>Path to vulnerable library: /assets/bootstrap/js/bootstrap.js</p> <p> Dependency Hierarchy: - :x: **bootstrap-3.1.1.js** (Vulnerable Library) </p> <p></p> ### Vulnerability Details <p> In Bootstrap 3.x before 3.4.0 and 4.x-beta before 4.0.0-beta.2, XSS is possible in the data-target attribute, a different vulnerability than CVE-2018-14041. <p>Publish Date: 2019-01-09 <p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2016-10735>CVE-2016-10735</a></p> </p> <p></p> ### CVSS 3 Score Details (<b>6.1</b>) <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: Required - Scope: Changed - Impact Metrics: - Confidentiality Impact: Low - Integrity Impact: Low - Availability Impact: None </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> <p></p> ### Suggested Fix <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-10735">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2016-10735</a></p> <p>Release Date: 2019-01-09</p> <p>Fix Resolution: bootstrap - 3.4.0, 4.0.0-beta.2</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
bootstrap js vulnerabilities highest severity is vulnerable library bootstrap js the most popular front end framework for developing responsive mobile first projects on the web library home page a href path to vulnerable library assets bootstrap js bootstrap js vulnerabilities cve severity cvss dependency type fixed in remediation available medium bootstrap js direct bootstrap bootstrap sass medium bootstrap js direct org webjars npm bootstrap org webjars bootstrap medium bootstrap js direct bootstrap nordron angulartemplate dynamic net express projecttemplates dotnetng template znxtapp core module theme beta jmeter medium bootstrap js direct org webjars npm bootstrap org webjars bootstrap medium bootstrap js direct bootstrap medium bootstrap js direct bootstrap beta details cve vulnerable library bootstrap js the most popular front end framework for developing responsive mobile first projects on the web library home page a href path to vulnerable library assets bootstrap js bootstrap js dependency hierarchy x bootstrap js vulnerable library vulnerability details in bootstrap before and x before xss is possible in the tooltip or popover data template attribute 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 release date fix resolution bootstrap bootstrap sass step up your open source security game with mend cve vulnerable library bootstrap js the most popular front end framework for developing responsive mobile first projects on the web library home page a href path to vulnerable library assets bootstrap js bootstrap js dependency hierarchy x bootstrap js vulnerable library vulnerability details in bootstrap before xss is possible in the collapse data parent attribute 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 release date fix resolution org webjars npm bootstrap org webjars bootstrap step up your open source security game with mend cve vulnerable library bootstrap js the most popular front end framework for developing responsive mobile first projects on the web library home page a href path to vulnerable library assets bootstrap js bootstrap js dependency hierarchy x bootstrap js vulnerable library vulnerability details in bootstrap before xss is possible in the affix configuration target property 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 bootstrap nordron angulartemplate dynamic net express projecttemplates dotnetng template znxtapp core module theme beta jmeter step up your open source security game with mend cve vulnerable library bootstrap js the most popular front end framework for developing responsive mobile first projects on the web library home page a href path to vulnerable library assets bootstrap js bootstrap js dependency hierarchy x bootstrap js vulnerable library vulnerability details in bootstrap before xss is possible in the data container property of tooltip 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 release date fix resolution org webjars npm bootstrap org webjars bootstrap step up your open source security game with mend cve vulnerable library bootstrap js the most popular front end framework for developing responsive mobile first projects on the web library home page a href path to vulnerable library assets bootstrap js bootstrap js dependency hierarchy x bootstrap js vulnerable library vulnerability details in bootstrap before xss is possible in the tooltip data viewport attribute 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 bootstrap step up your open source security game with mend cve vulnerable library bootstrap js the most popular front end framework for developing responsive mobile first projects on the web library home page a href path to vulnerable library assets bootstrap js bootstrap js dependency hierarchy x bootstrap js vulnerable library vulnerability details in bootstrap x before and x beta before beta xss is possible in the data target attribute a different vulnerability than cve publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction required scope 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 bootstrap beta step up your open source security game with mend
0
405,540
27,523,517,967
IssuesEvent
2023-03-06 16:28:23
epiverse-trace/bpmodels
https://api.github.com/repos/epiverse-trace/bpmodels
closed
Add use case vignettes
documentation
Adding use case vignettes would help the user identify ways to apply this package. Some use cases include: 1. Forecasting an epidemic given data (ideally a linelist) on the first few cases. (*Will update with more later) 2. Estimating R0 from epidemic data
1.0
Add use case vignettes - Adding use case vignettes would help the user identify ways to apply this package. Some use cases include: 1. Forecasting an epidemic given data (ideally a linelist) on the first few cases. (*Will update with more later) 2. Estimating R0 from epidemic data
non_priority
add use case vignettes adding use case vignettes would help the user identify ways to apply this package some use cases include forecasting an epidemic given data ideally a linelist on the first few cases will update with more later estimating from epidemic data
0
20,692
14,099,419,737
IssuesEvent
2020-11-06 01:20:28
noahtalerman/test-issues-kolide
https://api.github.com/repos/noahtalerman/test-issues-kolide
opened
[CLOSED] Typescript
Component: Development Infrastructure
<a href="https://github.com/mikestone14"><img src="https://avatars2.githubusercontent.com/u/2905145?v=4" align="left" width="96" height="96" hspace="10"></img></a> **Issue by [mikestone14](https://github.com/mikestone14)** _Sunday Oct 30, 2016 at 16:42 GMT_ _Originally opened as https://github.com/kolide/fleet/pull/355_ ---- This is a first attempt at adding Typescript to the repo. It seems to be compiling locally and working fine but I'm having trouble getting Typescript to compile when testing. I've tried debugging it but am a bit stuck. Help appreciated! ---- _**[mikestone14](https://github.com/mikestone14)** included the following code: https://github.com/kolide/fleet/pull/355/commits_
1.0
[CLOSED] Typescript - <a href="https://github.com/mikestone14"><img src="https://avatars2.githubusercontent.com/u/2905145?v=4" align="left" width="96" height="96" hspace="10"></img></a> **Issue by [mikestone14](https://github.com/mikestone14)** _Sunday Oct 30, 2016 at 16:42 GMT_ _Originally opened as https://github.com/kolide/fleet/pull/355_ ---- This is a first attempt at adding Typescript to the repo. It seems to be compiling locally and working fine but I'm having trouble getting Typescript to compile when testing. I've tried debugging it but am a bit stuck. Help appreciated! ---- _**[mikestone14](https://github.com/mikestone14)** included the following code: https://github.com/kolide/fleet/pull/355/commits_
non_priority
typescript issue by sunday oct at gmt originally opened as this is a first attempt at adding typescript to the repo it seems to be compiling locally and working fine but i m having trouble getting typescript to compile when testing i ve tried debugging it but am a bit stuck help appreciated included the following code
0
332,530
29,482,469,228
IssuesEvent
2023-06-02 07:08:12
unifyai/ivy
https://api.github.com/repos/unifyai/ivy
closed
Fix searching.test_numpy_argwhere
NumPy Frontend Sub Task Failing Test
| | | |---|---| |tensorflow|<a href="null" rel="noopener noreferrer" target="_blank"><img src=https://img.shields.io/badge/-success-success></a> |torch|<a href="https://github.com/unifyai/ivy/actions/runs/5147945733/jobs/9268988482" rel="noopener noreferrer" target="_blank"><img src=https://img.shields.io/badge/-success-success></a> |numpy|<a href="https://github.com/unifyai/ivy/actions/runs/5147945733/jobs/9268988482" rel="noopener noreferrer" target="_blank"><img src=https://img.shields.io/badge/-success-success></a> |jax|<a href="https://github.com/unifyai/ivy/actions/runs/5147945733/jobs/9268988482" rel="noopener noreferrer" target="_blank"><img src=https://img.shields.io/badge/-success-success></a> |paddle|<a href="https://github.com/unifyai/ivy/actions/runs/5147945733/jobs/9268988482" rel="noopener noreferrer" target="_blank"><img src=https://img.shields.io/badge/-success-success></a>
1.0
Fix searching.test_numpy_argwhere - | | | |---|---| |tensorflow|<a href="null" rel="noopener noreferrer" target="_blank"><img src=https://img.shields.io/badge/-success-success></a> |torch|<a href="https://github.com/unifyai/ivy/actions/runs/5147945733/jobs/9268988482" rel="noopener noreferrer" target="_blank"><img src=https://img.shields.io/badge/-success-success></a> |numpy|<a href="https://github.com/unifyai/ivy/actions/runs/5147945733/jobs/9268988482" rel="noopener noreferrer" target="_blank"><img src=https://img.shields.io/badge/-success-success></a> |jax|<a href="https://github.com/unifyai/ivy/actions/runs/5147945733/jobs/9268988482" rel="noopener noreferrer" target="_blank"><img src=https://img.shields.io/badge/-success-success></a> |paddle|<a href="https://github.com/unifyai/ivy/actions/runs/5147945733/jobs/9268988482" rel="noopener noreferrer" target="_blank"><img src=https://img.shields.io/badge/-success-success></a>
non_priority
fix searching test numpy argwhere tensorflow img src torch img src numpy img src jax img src paddle img src
0
7,421
4,981,823,683
IssuesEvent
2016-12-07 09:22:48
tgstation/tgstation
https://api.github.com/repos/tgstation/tgstation
closed
Action buttons are very slow to update.
Not a bug UI Usability
This can cause problems for wizards, especially with charged spells like lightning bolt, where he can accidentally queue up multiple lightning bolts without being able to fire them. It also generally feels really clunky for it to update that slowly when the rest of the UI has been made so much faster. Also I'd like to point out that the progress bar can get wonky with this @Iamgoofball
True
Action buttons are very slow to update. - This can cause problems for wizards, especially with charged spells like lightning bolt, where he can accidentally queue up multiple lightning bolts without being able to fire them. It also generally feels really clunky for it to update that slowly when the rest of the UI has been made so much faster. Also I'd like to point out that the progress bar can get wonky with this @Iamgoofball
non_priority
action buttons are very slow to update this can cause problems for wizards especially with charged spells like lightning bolt where he can accidentally queue up multiple lightning bolts without being able to fire them it also generally feels really clunky for it to update that slowly when the rest of the ui has been made so much faster also i d like to point out that the progress bar can get wonky with this iamgoofball
0
125,594
16,818,462,641
IssuesEvent
2021-06-17 10:09:41
SocialGouv/1000jours
https://api.github.com/repos/SocialGouv/1000jours
closed
ETQ utilisateur, je peux consulter la liste des professionnels à contacter
design dev à revoir epic::questionnaire epds
Après le questionnaire, à l'affichage du résultat, je peux voir une liste de professionnels à contacter selon le résultat
1.0
ETQ utilisateur, je peux consulter la liste des professionnels à contacter - Après le questionnaire, à l'affichage du résultat, je peux voir une liste de professionnels à contacter selon le résultat
non_priority
etq utilisateur je peux consulter la liste des professionnels à contacter après le questionnaire à l affichage du résultat je peux voir une liste de professionnels à contacter selon le résultat
0
181,144
30,631,997,174
IssuesEvent
2023-07-24 15:05:44
sparcs-kaist/otl-app
https://api.github.com/repos/sparcs-kaist/otl-app
closed
[FEAT] ColorStyles 및 TextStyles 정리
chore design
## Description ColorStyles 정리 - pinks - grayscale TextStyles 정리 - Display Bold, Display Regular - Headline Bold, Headline Regular - Title Bold, Title Regular - Body Bold, Body Regular - Label Bold, Label Regular
1.0
[FEAT] ColorStyles 및 TextStyles 정리 - ## Description ColorStyles 정리 - pinks - grayscale TextStyles 정리 - Display Bold, Display Regular - Headline Bold, Headline Regular - Title Bold, Title Regular - Body Bold, Body Regular - Label Bold, Label Regular
non_priority
colorstyles 및 textstyles 정리 description colorstyles 정리 pinks grayscale textstyles 정리 display bold display regular headline bold headline regular title bold title regular body bold body regular label bold label regular
0
252,340
21,572,061,664
IssuesEvent
2022-05-02 09:24:54
cockroachdb/cockroach
https://api.github.com/repos/cockroachdb/cockroach
opened
roachtest: tpccbench/nodes=9/cpu=4/multi-region failed
C-test-failure O-robot O-roachtest release-blocker branch-release-21.1
roachtest.tpccbench/nodes=9/cpu=4/multi-region [failed](https://teamcity.cockroachdb.com/viewLog.html?buildId=5072925&tab=buildLog) with [artifacts](https://teamcity.cockroachdb.com/viewLog.html?buildId=5072925&tab=artifacts#/tpccbench/nodes=9/cpu=4/multi-region) on release-21.1 @ [dedf8c3934ca3a3cb58c1bdc4f3eaebf7f9ce97d](https://github.com/cockroachdb/cockroach/commits/dedf8c3934ca3a3cb58c1bdc4f3eaebf7f9ce97d): ``` | main.(*monitor).WaitE | /home/agent/work/.go/src/github.com/cockroachdb/cockroach/pkg/cmd/roachtest/cluster.go:2676 | main.(*monitor).Wait | /home/agent/work/.go/src/github.com/cockroachdb/cockroach/pkg/cmd/roachtest/cluster.go:2684 | main.runTPCCBench | /home/agent/work/.go/src/github.com/cockroachdb/cockroach/pkg/cmd/roachtest/tpcc.go:781 | main.registerTPCCBenchSpec.func1 | /home/agent/work/.go/src/github.com/cockroachdb/cockroach/pkg/cmd/roachtest/tpcc.go:613 | main.(*testRunner).runTest.func2 | /home/agent/work/.go/src/github.com/cockroachdb/cockroach/pkg/cmd/roachtest/test_runner.go:733 | runtime.goexit | /usr/local/go/src/runtime/asm_amd64.s:1581 Wraps: (2) monitor failure Wraps: (3) unexpected node event: 7: dead (exit status 137) Error types: (1) *withstack.withStack (2) *errutil.withPrefix (3) *errors.errorString cluster.go:1667,context.go:91,cluster.go:1656,test_runner.go:820: dead node detection: /home/agent/work/.go/src/github.com/cockroachdb/cockroach/bin/roachprod monitor teamcity-5072925-1651470179-43-n12cpu4-geo --oneshot --ignore-empty-nodes: exit status 1 2: 13572 4: skipped 1: 14711 3: 13811 6: 13377 8: skipped 5: 13290 9: 12588 7: dead (exit status 137) 12: skipped 11: 12565 10: 12350 Error: UNCLASSIFIED_PROBLEM: 7: dead (exit status 137) (1) UNCLASSIFIED_PROBLEM Wraps: (2) attached stack trace -- stack trace: | main.glob..func14 | /home/agent/work/.go/src/github.com/cockroachdb/cockroach/pkg/cmd/roachprod/main.go:1147 | main.wrap.func1 | /home/agent/work/.go/src/github.com/cockroachdb/cockroach/pkg/cmd/roachprod/main.go:271 | github.com/spf13/cobra.(*Command).execute | /home/agent/work/.go/src/github.com/cockroachdb/cockroach/vendor/github.com/spf13/cobra/command.go:830 | github.com/spf13/cobra.(*Command).ExecuteC | /home/agent/work/.go/src/github.com/cockroachdb/cockroach/vendor/github.com/spf13/cobra/command.go:914 | github.com/spf13/cobra.(*Command).Execute | /home/agent/work/.go/src/github.com/cockroachdb/cockroach/vendor/github.com/spf13/cobra/command.go:864 | main.main | /home/agent/work/.go/src/github.com/cockroachdb/cockroach/pkg/cmd/roachprod/main.go:1889 | runtime.main | /usr/local/go/src/runtime/proc.go:255 | runtime.goexit | /usr/local/go/src/runtime/asm_amd64.s:1581 Wraps: (3) 7: dead (exit status 137) Error types: (1) errors.Unclassified (2) *withstack.withStack (3) *errutil.leafError ``` <details><summary>Reproduce</summary> <p> <p>To reproduce, try: ```bash # From https://go.crdb.dev/p/roachstress, perhaps edited lightly. caffeinate ./roachstress.sh tpccbench/nodes=9/cpu=4/multi-region ``` </p> </p> </details> <details><summary>Same failure on other branches</summary> <p> - #72083 roachtest: tpccbench/nodes=9/cpu=4/multi-region failed [sst raft oom] [C-test-failure O-roachtest O-robot S-1 branch-master] </p> </details> /cc @cockroachdb/kv <sub> [This test on roachdash](https://roachdash.crdb.dev/?filter=status:open%20t:.*tpccbench/nodes=9/cpu=4/multi-region.*&sort=title+created&display=lastcommented+project) | [Improve this report!](https://github.com/cockroachdb/cockroach/tree/master/pkg/cmd/internal/issues) </sub>
2.0
roachtest: tpccbench/nodes=9/cpu=4/multi-region failed - roachtest.tpccbench/nodes=9/cpu=4/multi-region [failed](https://teamcity.cockroachdb.com/viewLog.html?buildId=5072925&tab=buildLog) with [artifacts](https://teamcity.cockroachdb.com/viewLog.html?buildId=5072925&tab=artifacts#/tpccbench/nodes=9/cpu=4/multi-region) on release-21.1 @ [dedf8c3934ca3a3cb58c1bdc4f3eaebf7f9ce97d](https://github.com/cockroachdb/cockroach/commits/dedf8c3934ca3a3cb58c1bdc4f3eaebf7f9ce97d): ``` | main.(*monitor).WaitE | /home/agent/work/.go/src/github.com/cockroachdb/cockroach/pkg/cmd/roachtest/cluster.go:2676 | main.(*monitor).Wait | /home/agent/work/.go/src/github.com/cockroachdb/cockroach/pkg/cmd/roachtest/cluster.go:2684 | main.runTPCCBench | /home/agent/work/.go/src/github.com/cockroachdb/cockroach/pkg/cmd/roachtest/tpcc.go:781 | main.registerTPCCBenchSpec.func1 | /home/agent/work/.go/src/github.com/cockroachdb/cockroach/pkg/cmd/roachtest/tpcc.go:613 | main.(*testRunner).runTest.func2 | /home/agent/work/.go/src/github.com/cockroachdb/cockroach/pkg/cmd/roachtest/test_runner.go:733 | runtime.goexit | /usr/local/go/src/runtime/asm_amd64.s:1581 Wraps: (2) monitor failure Wraps: (3) unexpected node event: 7: dead (exit status 137) Error types: (1) *withstack.withStack (2) *errutil.withPrefix (3) *errors.errorString cluster.go:1667,context.go:91,cluster.go:1656,test_runner.go:820: dead node detection: /home/agent/work/.go/src/github.com/cockroachdb/cockroach/bin/roachprod monitor teamcity-5072925-1651470179-43-n12cpu4-geo --oneshot --ignore-empty-nodes: exit status 1 2: 13572 4: skipped 1: 14711 3: 13811 6: 13377 8: skipped 5: 13290 9: 12588 7: dead (exit status 137) 12: skipped 11: 12565 10: 12350 Error: UNCLASSIFIED_PROBLEM: 7: dead (exit status 137) (1) UNCLASSIFIED_PROBLEM Wraps: (2) attached stack trace -- stack trace: | main.glob..func14 | /home/agent/work/.go/src/github.com/cockroachdb/cockroach/pkg/cmd/roachprod/main.go:1147 | main.wrap.func1 | /home/agent/work/.go/src/github.com/cockroachdb/cockroach/pkg/cmd/roachprod/main.go:271 | github.com/spf13/cobra.(*Command).execute | /home/agent/work/.go/src/github.com/cockroachdb/cockroach/vendor/github.com/spf13/cobra/command.go:830 | github.com/spf13/cobra.(*Command).ExecuteC | /home/agent/work/.go/src/github.com/cockroachdb/cockroach/vendor/github.com/spf13/cobra/command.go:914 | github.com/spf13/cobra.(*Command).Execute | /home/agent/work/.go/src/github.com/cockroachdb/cockroach/vendor/github.com/spf13/cobra/command.go:864 | main.main | /home/agent/work/.go/src/github.com/cockroachdb/cockroach/pkg/cmd/roachprod/main.go:1889 | runtime.main | /usr/local/go/src/runtime/proc.go:255 | runtime.goexit | /usr/local/go/src/runtime/asm_amd64.s:1581 Wraps: (3) 7: dead (exit status 137) Error types: (1) errors.Unclassified (2) *withstack.withStack (3) *errutil.leafError ``` <details><summary>Reproduce</summary> <p> <p>To reproduce, try: ```bash # From https://go.crdb.dev/p/roachstress, perhaps edited lightly. caffeinate ./roachstress.sh tpccbench/nodes=9/cpu=4/multi-region ``` </p> </p> </details> <details><summary>Same failure on other branches</summary> <p> - #72083 roachtest: tpccbench/nodes=9/cpu=4/multi-region failed [sst raft oom] [C-test-failure O-roachtest O-robot S-1 branch-master] </p> </details> /cc @cockroachdb/kv <sub> [This test on roachdash](https://roachdash.crdb.dev/?filter=status:open%20t:.*tpccbench/nodes=9/cpu=4/multi-region.*&sort=title+created&display=lastcommented+project) | [Improve this report!](https://github.com/cockroachdb/cockroach/tree/master/pkg/cmd/internal/issues) </sub>
non_priority
roachtest tpccbench nodes cpu multi region failed roachtest tpccbench nodes cpu multi region with on release main monitor waite home agent work go src github com cockroachdb cockroach pkg cmd roachtest cluster go main monitor wait home agent work go src github com cockroachdb cockroach pkg cmd roachtest cluster go main runtpccbench home agent work go src github com cockroachdb cockroach pkg cmd roachtest tpcc go main registertpccbenchspec home agent work go src github com cockroachdb cockroach pkg cmd roachtest tpcc go main testrunner runtest home agent work go src github com cockroachdb cockroach pkg cmd roachtest test runner go runtime goexit usr local go src runtime asm s wraps monitor failure wraps unexpected node event dead exit status error types withstack withstack errutil withprefix errors errorstring cluster go context go cluster go test runner go dead node detection home agent work go src github com cockroachdb cockroach bin roachprod monitor teamcity geo oneshot ignore empty nodes exit status skipped skipped dead exit status skipped error unclassified problem dead exit status unclassified problem wraps attached stack trace stack trace main glob home agent work go src github com cockroachdb cockroach pkg cmd roachprod main go main wrap home agent work go src github com cockroachdb cockroach pkg cmd roachprod main go github com cobra command execute home agent work go src github com cockroachdb cockroach vendor github com cobra command go github com cobra command executec home agent work go src github com cockroachdb cockroach vendor github com cobra command go github com cobra command execute home agent work go src github com cockroachdb cockroach vendor github com cobra command go main main home agent work go src github com cockroachdb cockroach pkg cmd roachprod main go runtime main usr local go src runtime proc go runtime goexit usr local go src runtime asm s wraps dead exit status error types errors unclassified withstack withstack errutil leaferror reproduce to reproduce try bash from perhaps edited lightly caffeinate roachstress sh tpccbench nodes cpu multi region same failure on other branches roachtest tpccbench nodes cpu multi region failed cc cockroachdb kv
0
89,748
25,894,429,633
IssuesEvent
2022-12-14 20:58:06
elastic/beats
https://api.github.com/repos/elastic/beats
closed
Build 472 for 7.17 with status FAILURE
automation ci-reported Team:Elastic-Agent-Data-Plane build-failures
## :broken_heart: Tests Failed <!-- BUILD BADGES--> > _the below badges are clickable and redirect to their specific view in the CI or DOCS_ [![Pipeline View](https://img.shields.io/badge/pipeline-pipeline%20-green)](https://beats-ci.elastic.co/blue/organizations/jenkins/Beats%2Fbeats%2F7.17/detail/7.17/472//pipeline) [![Test View](https://img.shields.io/badge/test-test-green)](https://beats-ci.elastic.co/blue/organizations/jenkins/Beats%2Fbeats%2F7.17/detail/7.17/472//tests) [![Changes](https://img.shields.io/badge/changes-changes-green)](https://beats-ci.elastic.co/blue/organizations/jenkins/Beats%2Fbeats%2F7.17/detail/7.17/472//changes) [![Artifacts](https://img.shields.io/badge/artifacts-artifacts-yellow)](https://beats-ci.elastic.co/blue/organizations/jenkins/Beats%2Fbeats%2F7.17/detail/7.17/472//artifacts) [![preview](https://img.shields.io/badge/docs-preview-yellowgreen)](http://beats_null.docs-preview.app.elstc.co/diff) [![preview](https://img.shields.io/badge/elastic-observability-blue)](https://ci-stats.elastic.co/app/apm/services/beats-ci/transactions/view?rangeFrom=2022-08-26T12:39:45.243Z&rangeTo=2022-08-26T12:59:45.243Z&transactionName=BUILD+Beats%2Fbeats%2F7.17&transactionType=job&latencyAggregationType=avg&traceId=a45aae0bb6904fafbe293fd718523855&transactionId=6d04fec736a14b86) <!-- BUILD SUMMARY--> <details><summary>Expand to view the summary</summary> <p> #### Build stats * Start Time: 2022-08-26T12:49:45.243+0000 * Duration: 116 min 55 sec #### Test stats :test_tube: | Test | Results | | ------------ | :-----------------------------: | | Failed | 2 | | Passed | 25712 | | Skipped | 1884 | | Total | 27598 | </p> </details> <!-- TEST RESULTS IF ANY--> ### Test errors [![2](https://img.shields.io/badge/2%20-red)](https://beats-ci.elastic.co/blue/organizations/jenkins/Beats%2Fbeats%2F7.17/detail/7.17/472//tests) <details><summary>Expand to view the tests failures</summary><p> ##### `Build&Test / metricbeat-goIntegTest / TestFetch – github.com/elastic/beats/v7/metricbeat/module/jolokia/jmx` <ul> <details><summary>Expand to view the error details</summary><p> ``` Failed ``` </p></details> <details><summary>Expand to view the stacktrace</summary><p> ``` === RUN TestFetch Found orphan containers (metricbeat_7_17_7_b9ff75cd3f-snapshot_http_1, metricbeat_7_17_7_b9ff75cd3f-snapshot_haproxy_1, metricbeat_7_17_7_b9ff75cd3f-snapshot_golang_1, metricbeat_7_17_7_b9ff75cd3f-snapshot_etcd_1, metricbeat_7_17_7_b9ff75cd3f-snapshot_envoyproxy_1, metricbeat_7_17_7_b9ff75cd3f-snapshot_dropwizard_1, metricbeat_7_17_7_b9ff75cd3f-snapshot_logstash_1, metricbeat_7_17_7_b9ff75cd3f-snapshot_kafka_1) for this project. If you removed or renamed this service in your compose file, you can run this command with the --remove-orphans flag to clean it up. Building jolokia Step 1/14 : FROM java:8-jdk-alpine Service "jolokia" failed to build: manifest for java:8-jdk-alpine not found: manifest unknown: manifest unknown jmx_integration_test.go:33: failed to start service "jolokia: exit status 1 Found orphan containers (metricbeat_7_17_7_b9ff75cd3f-snapshot_http_1, metricbeat_7_17_7_b9ff75cd3f-snapshot_haproxy_1, metricbeat_7_17_7_b9ff75cd3f-snapshot_golang_1, metricbeat_7_17_7_b9ff75cd3f-snapshot_etcd_1, metricbeat_7_17_7_b9ff75cd3f-snapshot_envoyproxy_1, metricbeat_7_17_7_b9ff75cd3f-snapshot_dropwizard_1, metricbeat_7_17_7_b9ff75cd3f-snapshot_logstash_1, metricbeat_7_17_7_b9ff75cd3f-snapshot_kafka_1) for this project. If you removed or renamed this service in your compose file, you can run this command with the --remove-orphans flag to clean it up. Building jolokia Step 1/14 : FROM java:8-jdk-alpine Service "jolokia" failed to build: manifest for java:8-jdk-alpine not found: manifest unknown: manifest unknown jmx_integration_test.go:33: failed to start service "jolokia: exit status 1 Found orphan containers (metricbeat_7_17_7_b9ff75cd3f-snapshot_http_1, metricbeat_7_17_7_b9ff75cd3f-snapshot_haproxy_1, metricbeat_7_17_7_b9ff75cd3f-snapshot_golang_1, metricbeat_7_17_7_b9ff75cd3f-snapshot_etcd_1, metricbeat_7_17_7_b9ff75cd3f-snapshot_envoyproxy_1, metricbeat_7_17_7_b9ff75cd3f-snapshot_dropwizard_1, metricbeat_7_17_7_b9ff75cd3f-snapshot_logstash_1, metricbeat_7_17_7_b9ff75cd3f-snapshot_kafka_1) for this project. If you removed or renamed this service in your compose file, you can run this command with the --remove-orphans flag to clean it up. Building jolokia Step 1/14 : FROM java:8-jdk-alpine Service "jolokia" failed to build: manifest for java:8-jdk-alpine not found: manifest unknown: manifest unknown jmx_integration_test.go:33: failed to start service "jolokia: exit status 1 jmx_integration_test.go:33: getting host for jolokia: no container running for service --- FAIL: TestFetch (9.07s) ``` </p></details> </ul> ##### `Build&Test / metricbeat-goIntegTest / TestData – github.com/elastic/beats/v7/metricbeat/module/jolokia/jmx` <ul> <details><summary>Expand to view the error details</summary><p> ``` Failed ``` </p></details> <details><summary>Expand to view the stacktrace</summary><p> ``` === RUN TestData Found orphan containers (metricbeat_7_17_7_b9ff75cd3f-snapshot_http_1, metricbeat_7_17_7_b9ff75cd3f-snapshot_haproxy_1, metricbeat_7_17_7_b9ff75cd3f-snapshot_golang_1, metricbeat_7_17_7_b9ff75cd3f-snapshot_etcd_1, metricbeat_7_17_7_b9ff75cd3f-snapshot_envoyproxy_1, metricbeat_7_17_7_b9ff75cd3f-snapshot_dropwizard_1, metricbeat_7_17_7_b9ff75cd3f-snapshot_logstash_1, metricbeat_7_17_7_b9ff75cd3f-snapshot_kafka_1) for this project. If you removed or renamed this service in your compose file, you can run this command with the --remove-orphans flag to clean it up. Building jolokia Step 1/14 : FROM java:8-jdk-alpine Service "jolokia" failed to build: manifest for java:8-jdk-alpine not found: manifest unknown: manifest unknown jmx_integration_test.go:45: failed to start service "jolokia: exit status 1 Found orphan containers (metricbeat_7_17_7_b9ff75cd3f-snapshot_http_1, metricbeat_7_17_7_b9ff75cd3f-snapshot_haproxy_1, metricbeat_7_17_7_b9ff75cd3f-snapshot_golang_1, metricbeat_7_17_7_b9ff75cd3f-snapshot_etcd_1, metricbeat_7_17_7_b9ff75cd3f-snapshot_envoyproxy_1, metricbeat_7_17_7_b9ff75cd3f-snapshot_dropwizard_1, metricbeat_7_17_7_b9ff75cd3f-snapshot_logstash_1, metricbeat_7_17_7_b9ff75cd3f-snapshot_kafka_1) for this project. If you removed or renamed this service in your compose file, you can run this command with the --remove-orphans flag to clean it up. Building jolokia Step 1/14 : FROM java:8-jdk-alpine Service "jolokia" failed to build: manifest for java:8-jdk-alpine not found: manifest unknown: manifest unknown jmx_integration_test.go:45: failed to start service "jolokia: exit status 1 Found orphan containers (metricbeat_7_17_7_b9ff75cd3f-snapshot_http_1, metricbeat_7_17_7_b9ff75cd3f-snapshot_haproxy_1, metricbeat_7_17_7_b9ff75cd3f-snapshot_golang_1, metricbeat_7_17_7_b9ff75cd3f-snapshot_etcd_1, metricbeat_7_17_7_b9ff75cd3f-snapshot_envoyproxy_1, metricbeat_7_17_7_b9ff75cd3f-snapshot_dropwizard_1, metricbeat_7_17_7_b9ff75cd3f-snapshot_logstash_1, metricbeat_7_17_7_b9ff75cd3f-snapshot_kafka_1) for this project. If you removed or renamed this service in your compose file, you can run this command with the --remove-orphans flag to clean it up. Building jolokia Step 1/14 : FROM java:8-jdk-alpine Service "jolokia" failed to build: manifest for java:8-jdk-alpine not found: manifest unknown: manifest unknown jmx_integration_test.go:45: failed to start service "jolokia: exit status 1 jmx_integration_test.go:45: getting host for jolokia: no container running for service --- FAIL: TestData (6.73s) ``` </p></details> </ul> </p></details> <!-- STEPS ERRORS IF ANY --> ### Steps errors [![11](https://img.shields.io/badge/11%20-red)](https://beats-ci.elastic.co/blue/organizations/jenkins/Beats%2Fbeats%2F7.17/detail/7.17/472//pipeline) <details><summary>Expand to view the steps failures</summary> <p> > Show only the first 10 steps failures ##### `filebeat-shipping-to-next-major - STACK_ENVIRONMENT=next-major TESTING_FILEBEAT_SKIP_DIFF=1 mage pyt` <ul> <li>Took 15 min 55 sec . View more details <a href="https://beats-ci.elastic.co//blue/rest/organizations/jenkins/pipelines/Beats/pipelines/beats/pipelines/7.17/runs/472/steps/21592/log/?start=0">here</a></li> <li>Description: <code>STACK_ENVIRONMENT=next-major TESTING_FILEBEAT_SKIP_DIFF=1 mage pythonIntegTest</code></l1> </ul> ##### `metricbeat-goIntegTest - mage goIntegTest` <ul> <li>Took 28 min 47 sec . View more details <a href="https://beats-ci.elastic.co//blue/rest/organizations/jenkins/pipelines/Beats/pipelines/beats/pipelines/7.17/runs/472/steps/15525/log/?start=0">here</a></li> <li>Description: <code>mage goIntegTest</code></l1> </ul> ##### `metricbeat-goIntegTest - mage goIntegTest` <ul> <li>Took 19 min 10 sec . View more details <a href="https://beats-ci.elastic.co//blue/rest/organizations/jenkins/pipelines/Beats/pipelines/beats/pipelines/7.17/runs/472/steps/21826/log/?start=0">here</a></li> <li>Description: <code>mage goIntegTest</code></l1> </ul> ##### `metricbeat-goIntegTest - mage goIntegTest` <ul> <li>Took 20 min 44 sec . View more details <a href="https://beats-ci.elastic.co//blue/rest/organizations/jenkins/pipelines/Beats/pipelines/beats/pipelines/7.17/runs/472/steps/22147/log/?start=0">here</a></li> <li>Description: <code>mage goIntegTest</code></l1> </ul> ##### `metricbeat-pythonIntegTest - mage pythonIntegTest` <ul> <li>Took 2 min 32 sec . View more details <a href="https://beats-ci.elastic.co//blue/rest/organizations/jenkins/pipelines/Beats/pipelines/beats/pipelines/7.17/runs/472/steps/14747/log/?start=0">here</a></li> <li>Description: <code>mage pythonIntegTest</code></l1> </ul> ##### `metricbeat-pythonIntegTest - mage pythonIntegTest` <ul> <li>Took 0 min 22 sec . View more details <a href="https://beats-ci.elastic.co//blue/rest/organizations/jenkins/pipelines/Beats/pipelines/beats/pipelines/7.17/runs/472/steps/15798/log/?start=0">here</a></li> <li>Description: <code>mage pythonIntegTest</code></l1> </ul> ##### `metricbeat-pythonIntegTest - mage pythonIntegTest` <ul> <li>Took 0 min 22 sec . View more details <a href="https://beats-ci.elastic.co//blue/rest/organizations/jenkins/pipelines/Beats/pipelines/beats/pipelines/7.17/runs/472/steps/16227/log/?start=0">here</a></li> <li>Description: <code>mage pythonIntegTest</code></l1> </ul> ##### `x-pack/filebeat-pythonIntegTest - mage pythonIntegTest` <ul> <li>Took 40 min 3 sec . View more details <a href="https://beats-ci.elastic.co//blue/rest/organizations/jenkins/pipelines/Beats/pipelines/beats/pipelines/7.17/runs/472/steps/14181/log/?start=0">here</a></li> <li>Description: <code>mage pythonIntegTest</code></l1> </ul> ##### `x-pack/filebeat-module-compat-prev-minor - STACK_ENVIRONMENT=prev-minor TESTING_FILEBEAT_SKIP_DIFF=1` <ul> <li>Took 40 min 4 sec . View more details <a href="https://beats-ci.elastic.co//blue/rest/organizations/jenkins/pipelines/Beats/pipelines/beats/pipelines/7.17/runs/472/steps/14753/log/?start=0">here</a></li> <li>Description: <code>STACK_ENVIRONMENT=prev-minor TESTING_FILEBEAT_SKIP_DIFF=1 PYTEST_ADDOPTS="-k test_xpack_modules" mage pythonIntegTest</code></l1> </ul> ##### `Error signal` <ul> <li>Took 0 min 0 sec . View more details <a href="https://beats-ci.elastic.co//blue/rest/organizations/jenkins/pipelines/Beats/pipelines/beats/pipelines/7.17/runs/472/steps/22262/log/?start=0">here</a></li> <li>Description: <code>Error "hudson.AbortException: script returned exit code 1"</code></l1> </ul> </p> </details>
1.0
Build 472 for 7.17 with status FAILURE - ## :broken_heart: Tests Failed <!-- BUILD BADGES--> > _the below badges are clickable and redirect to their specific view in the CI or DOCS_ [![Pipeline View](https://img.shields.io/badge/pipeline-pipeline%20-green)](https://beats-ci.elastic.co/blue/organizations/jenkins/Beats%2Fbeats%2F7.17/detail/7.17/472//pipeline) [![Test View](https://img.shields.io/badge/test-test-green)](https://beats-ci.elastic.co/blue/organizations/jenkins/Beats%2Fbeats%2F7.17/detail/7.17/472//tests) [![Changes](https://img.shields.io/badge/changes-changes-green)](https://beats-ci.elastic.co/blue/organizations/jenkins/Beats%2Fbeats%2F7.17/detail/7.17/472//changes) [![Artifacts](https://img.shields.io/badge/artifacts-artifacts-yellow)](https://beats-ci.elastic.co/blue/organizations/jenkins/Beats%2Fbeats%2F7.17/detail/7.17/472//artifacts) [![preview](https://img.shields.io/badge/docs-preview-yellowgreen)](http://beats_null.docs-preview.app.elstc.co/diff) [![preview](https://img.shields.io/badge/elastic-observability-blue)](https://ci-stats.elastic.co/app/apm/services/beats-ci/transactions/view?rangeFrom=2022-08-26T12:39:45.243Z&rangeTo=2022-08-26T12:59:45.243Z&transactionName=BUILD+Beats%2Fbeats%2F7.17&transactionType=job&latencyAggregationType=avg&traceId=a45aae0bb6904fafbe293fd718523855&transactionId=6d04fec736a14b86) <!-- BUILD SUMMARY--> <details><summary>Expand to view the summary</summary> <p> #### Build stats * Start Time: 2022-08-26T12:49:45.243+0000 * Duration: 116 min 55 sec #### Test stats :test_tube: | Test | Results | | ------------ | :-----------------------------: | | Failed | 2 | | Passed | 25712 | | Skipped | 1884 | | Total | 27598 | </p> </details> <!-- TEST RESULTS IF ANY--> ### Test errors [![2](https://img.shields.io/badge/2%20-red)](https://beats-ci.elastic.co/blue/organizations/jenkins/Beats%2Fbeats%2F7.17/detail/7.17/472//tests) <details><summary>Expand to view the tests failures</summary><p> ##### `Build&Test / metricbeat-goIntegTest / TestFetch – github.com/elastic/beats/v7/metricbeat/module/jolokia/jmx` <ul> <details><summary>Expand to view the error details</summary><p> ``` Failed ``` </p></details> <details><summary>Expand to view the stacktrace</summary><p> ``` === RUN TestFetch Found orphan containers (metricbeat_7_17_7_b9ff75cd3f-snapshot_http_1, metricbeat_7_17_7_b9ff75cd3f-snapshot_haproxy_1, metricbeat_7_17_7_b9ff75cd3f-snapshot_golang_1, metricbeat_7_17_7_b9ff75cd3f-snapshot_etcd_1, metricbeat_7_17_7_b9ff75cd3f-snapshot_envoyproxy_1, metricbeat_7_17_7_b9ff75cd3f-snapshot_dropwizard_1, metricbeat_7_17_7_b9ff75cd3f-snapshot_logstash_1, metricbeat_7_17_7_b9ff75cd3f-snapshot_kafka_1) for this project. If you removed or renamed this service in your compose file, you can run this command with the --remove-orphans flag to clean it up. Building jolokia Step 1/14 : FROM java:8-jdk-alpine Service "jolokia" failed to build: manifest for java:8-jdk-alpine not found: manifest unknown: manifest unknown jmx_integration_test.go:33: failed to start service "jolokia: exit status 1 Found orphan containers (metricbeat_7_17_7_b9ff75cd3f-snapshot_http_1, metricbeat_7_17_7_b9ff75cd3f-snapshot_haproxy_1, metricbeat_7_17_7_b9ff75cd3f-snapshot_golang_1, metricbeat_7_17_7_b9ff75cd3f-snapshot_etcd_1, metricbeat_7_17_7_b9ff75cd3f-snapshot_envoyproxy_1, metricbeat_7_17_7_b9ff75cd3f-snapshot_dropwizard_1, metricbeat_7_17_7_b9ff75cd3f-snapshot_logstash_1, metricbeat_7_17_7_b9ff75cd3f-snapshot_kafka_1) for this project. If you removed or renamed this service in your compose file, you can run this command with the --remove-orphans flag to clean it up. Building jolokia Step 1/14 : FROM java:8-jdk-alpine Service "jolokia" failed to build: manifest for java:8-jdk-alpine not found: manifest unknown: manifest unknown jmx_integration_test.go:33: failed to start service "jolokia: exit status 1 Found orphan containers (metricbeat_7_17_7_b9ff75cd3f-snapshot_http_1, metricbeat_7_17_7_b9ff75cd3f-snapshot_haproxy_1, metricbeat_7_17_7_b9ff75cd3f-snapshot_golang_1, metricbeat_7_17_7_b9ff75cd3f-snapshot_etcd_1, metricbeat_7_17_7_b9ff75cd3f-snapshot_envoyproxy_1, metricbeat_7_17_7_b9ff75cd3f-snapshot_dropwizard_1, metricbeat_7_17_7_b9ff75cd3f-snapshot_logstash_1, metricbeat_7_17_7_b9ff75cd3f-snapshot_kafka_1) for this project. If you removed or renamed this service in your compose file, you can run this command with the --remove-orphans flag to clean it up. Building jolokia Step 1/14 : FROM java:8-jdk-alpine Service "jolokia" failed to build: manifest for java:8-jdk-alpine not found: manifest unknown: manifest unknown jmx_integration_test.go:33: failed to start service "jolokia: exit status 1 jmx_integration_test.go:33: getting host for jolokia: no container running for service --- FAIL: TestFetch (9.07s) ``` </p></details> </ul> ##### `Build&Test / metricbeat-goIntegTest / TestData – github.com/elastic/beats/v7/metricbeat/module/jolokia/jmx` <ul> <details><summary>Expand to view the error details</summary><p> ``` Failed ``` </p></details> <details><summary>Expand to view the stacktrace</summary><p> ``` === RUN TestData Found orphan containers (metricbeat_7_17_7_b9ff75cd3f-snapshot_http_1, metricbeat_7_17_7_b9ff75cd3f-snapshot_haproxy_1, metricbeat_7_17_7_b9ff75cd3f-snapshot_golang_1, metricbeat_7_17_7_b9ff75cd3f-snapshot_etcd_1, metricbeat_7_17_7_b9ff75cd3f-snapshot_envoyproxy_1, metricbeat_7_17_7_b9ff75cd3f-snapshot_dropwizard_1, metricbeat_7_17_7_b9ff75cd3f-snapshot_logstash_1, metricbeat_7_17_7_b9ff75cd3f-snapshot_kafka_1) for this project. If you removed or renamed this service in your compose file, you can run this command with the --remove-orphans flag to clean it up. Building jolokia Step 1/14 : FROM java:8-jdk-alpine Service "jolokia" failed to build: manifest for java:8-jdk-alpine not found: manifest unknown: manifest unknown jmx_integration_test.go:45: failed to start service "jolokia: exit status 1 Found orphan containers (metricbeat_7_17_7_b9ff75cd3f-snapshot_http_1, metricbeat_7_17_7_b9ff75cd3f-snapshot_haproxy_1, metricbeat_7_17_7_b9ff75cd3f-snapshot_golang_1, metricbeat_7_17_7_b9ff75cd3f-snapshot_etcd_1, metricbeat_7_17_7_b9ff75cd3f-snapshot_envoyproxy_1, metricbeat_7_17_7_b9ff75cd3f-snapshot_dropwizard_1, metricbeat_7_17_7_b9ff75cd3f-snapshot_logstash_1, metricbeat_7_17_7_b9ff75cd3f-snapshot_kafka_1) for this project. If you removed or renamed this service in your compose file, you can run this command with the --remove-orphans flag to clean it up. Building jolokia Step 1/14 : FROM java:8-jdk-alpine Service "jolokia" failed to build: manifest for java:8-jdk-alpine not found: manifest unknown: manifest unknown jmx_integration_test.go:45: failed to start service "jolokia: exit status 1 Found orphan containers (metricbeat_7_17_7_b9ff75cd3f-snapshot_http_1, metricbeat_7_17_7_b9ff75cd3f-snapshot_haproxy_1, metricbeat_7_17_7_b9ff75cd3f-snapshot_golang_1, metricbeat_7_17_7_b9ff75cd3f-snapshot_etcd_1, metricbeat_7_17_7_b9ff75cd3f-snapshot_envoyproxy_1, metricbeat_7_17_7_b9ff75cd3f-snapshot_dropwizard_1, metricbeat_7_17_7_b9ff75cd3f-snapshot_logstash_1, metricbeat_7_17_7_b9ff75cd3f-snapshot_kafka_1) for this project. If you removed or renamed this service in your compose file, you can run this command with the --remove-orphans flag to clean it up. Building jolokia Step 1/14 : FROM java:8-jdk-alpine Service "jolokia" failed to build: manifest for java:8-jdk-alpine not found: manifest unknown: manifest unknown jmx_integration_test.go:45: failed to start service "jolokia: exit status 1 jmx_integration_test.go:45: getting host for jolokia: no container running for service --- FAIL: TestData (6.73s) ``` </p></details> </ul> </p></details> <!-- STEPS ERRORS IF ANY --> ### Steps errors [![11](https://img.shields.io/badge/11%20-red)](https://beats-ci.elastic.co/blue/organizations/jenkins/Beats%2Fbeats%2F7.17/detail/7.17/472//pipeline) <details><summary>Expand to view the steps failures</summary> <p> > Show only the first 10 steps failures ##### `filebeat-shipping-to-next-major - STACK_ENVIRONMENT=next-major TESTING_FILEBEAT_SKIP_DIFF=1 mage pyt` <ul> <li>Took 15 min 55 sec . View more details <a href="https://beats-ci.elastic.co//blue/rest/organizations/jenkins/pipelines/Beats/pipelines/beats/pipelines/7.17/runs/472/steps/21592/log/?start=0">here</a></li> <li>Description: <code>STACK_ENVIRONMENT=next-major TESTING_FILEBEAT_SKIP_DIFF=1 mage pythonIntegTest</code></l1> </ul> ##### `metricbeat-goIntegTest - mage goIntegTest` <ul> <li>Took 28 min 47 sec . View more details <a href="https://beats-ci.elastic.co//blue/rest/organizations/jenkins/pipelines/Beats/pipelines/beats/pipelines/7.17/runs/472/steps/15525/log/?start=0">here</a></li> <li>Description: <code>mage goIntegTest</code></l1> </ul> ##### `metricbeat-goIntegTest - mage goIntegTest` <ul> <li>Took 19 min 10 sec . View more details <a href="https://beats-ci.elastic.co//blue/rest/organizations/jenkins/pipelines/Beats/pipelines/beats/pipelines/7.17/runs/472/steps/21826/log/?start=0">here</a></li> <li>Description: <code>mage goIntegTest</code></l1> </ul> ##### `metricbeat-goIntegTest - mage goIntegTest` <ul> <li>Took 20 min 44 sec . View more details <a href="https://beats-ci.elastic.co//blue/rest/organizations/jenkins/pipelines/Beats/pipelines/beats/pipelines/7.17/runs/472/steps/22147/log/?start=0">here</a></li> <li>Description: <code>mage goIntegTest</code></l1> </ul> ##### `metricbeat-pythonIntegTest - mage pythonIntegTest` <ul> <li>Took 2 min 32 sec . View more details <a href="https://beats-ci.elastic.co//blue/rest/organizations/jenkins/pipelines/Beats/pipelines/beats/pipelines/7.17/runs/472/steps/14747/log/?start=0">here</a></li> <li>Description: <code>mage pythonIntegTest</code></l1> </ul> ##### `metricbeat-pythonIntegTest - mage pythonIntegTest` <ul> <li>Took 0 min 22 sec . View more details <a href="https://beats-ci.elastic.co//blue/rest/organizations/jenkins/pipelines/Beats/pipelines/beats/pipelines/7.17/runs/472/steps/15798/log/?start=0">here</a></li> <li>Description: <code>mage pythonIntegTest</code></l1> </ul> ##### `metricbeat-pythonIntegTest - mage pythonIntegTest` <ul> <li>Took 0 min 22 sec . View more details <a href="https://beats-ci.elastic.co//blue/rest/organizations/jenkins/pipelines/Beats/pipelines/beats/pipelines/7.17/runs/472/steps/16227/log/?start=0">here</a></li> <li>Description: <code>mage pythonIntegTest</code></l1> </ul> ##### `x-pack/filebeat-pythonIntegTest - mage pythonIntegTest` <ul> <li>Took 40 min 3 sec . View more details <a href="https://beats-ci.elastic.co//blue/rest/organizations/jenkins/pipelines/Beats/pipelines/beats/pipelines/7.17/runs/472/steps/14181/log/?start=0">here</a></li> <li>Description: <code>mage pythonIntegTest</code></l1> </ul> ##### `x-pack/filebeat-module-compat-prev-minor - STACK_ENVIRONMENT=prev-minor TESTING_FILEBEAT_SKIP_DIFF=1` <ul> <li>Took 40 min 4 sec . View more details <a href="https://beats-ci.elastic.co//blue/rest/organizations/jenkins/pipelines/Beats/pipelines/beats/pipelines/7.17/runs/472/steps/14753/log/?start=0">here</a></li> <li>Description: <code>STACK_ENVIRONMENT=prev-minor TESTING_FILEBEAT_SKIP_DIFF=1 PYTEST_ADDOPTS="-k test_xpack_modules" mage pythonIntegTest</code></l1> </ul> ##### `Error signal` <ul> <li>Took 0 min 0 sec . View more details <a href="https://beats-ci.elastic.co//blue/rest/organizations/jenkins/pipelines/Beats/pipelines/beats/pipelines/7.17/runs/472/steps/22262/log/?start=0">here</a></li> <li>Description: <code>Error "hudson.AbortException: script returned exit code 1"</code></l1> </ul> </p> </details>
non_priority
build for with status failure broken heart tests failed the below badges are clickable and redirect to their specific view in the ci or docs expand to view the summary build stats start time duration min sec test stats test tube test results failed passed skipped total test errors expand to view the tests failures build test metricbeat gointegtest testfetch – github com elastic beats metricbeat module jolokia jmx expand to view the error details failed expand to view the stacktrace run testfetch found orphan containers metricbeat snapshot http metricbeat snapshot haproxy metricbeat snapshot golang metricbeat snapshot etcd metricbeat snapshot envoyproxy metricbeat snapshot dropwizard metricbeat snapshot logstash metricbeat snapshot kafka for this project if you removed or renamed this service in your compose file you can run this command with the remove orphans flag to clean it up building jolokia step from java jdk alpine service jolokia failed to build manifest for java jdk alpine not found manifest unknown manifest unknown jmx integration test go failed to start service jolokia exit status found orphan containers metricbeat snapshot http metricbeat snapshot haproxy metricbeat snapshot golang metricbeat snapshot etcd metricbeat snapshot envoyproxy metricbeat snapshot dropwizard metricbeat snapshot logstash metricbeat snapshot kafka for this project if you removed or renamed this service in your compose file you can run this command with the remove orphans flag to clean it up building jolokia step from java jdk alpine service jolokia failed to build manifest for java jdk alpine not found manifest unknown manifest unknown jmx integration test go failed to start service jolokia exit status found orphan containers metricbeat snapshot http metricbeat snapshot haproxy metricbeat snapshot golang metricbeat snapshot etcd metricbeat snapshot envoyproxy metricbeat snapshot dropwizard metricbeat snapshot logstash metricbeat snapshot kafka for this project if you removed or renamed this service in your compose file you can run this command with the remove orphans flag to clean it up building jolokia step from java jdk alpine service jolokia failed to build manifest for java jdk alpine not found manifest unknown manifest unknown jmx integration test go failed to start service jolokia exit status jmx integration test go getting host for jolokia no container running for service fail testfetch build test metricbeat gointegtest testdata – github com elastic beats metricbeat module jolokia jmx expand to view the error details failed expand to view the stacktrace run testdata found orphan containers metricbeat snapshot http metricbeat snapshot haproxy metricbeat snapshot golang metricbeat snapshot etcd metricbeat snapshot envoyproxy metricbeat snapshot dropwizard metricbeat snapshot logstash metricbeat snapshot kafka for this project if you removed or renamed this service in your compose file you can run this command with the remove orphans flag to clean it up building jolokia step from java jdk alpine service jolokia failed to build manifest for java jdk alpine not found manifest unknown manifest unknown jmx integration test go failed to start service jolokia exit status found orphan containers metricbeat snapshot http metricbeat snapshot haproxy metricbeat snapshot golang metricbeat snapshot etcd metricbeat snapshot envoyproxy metricbeat snapshot dropwizard metricbeat snapshot logstash metricbeat snapshot kafka for this project if you removed or renamed this service in your compose file you can run this command with the remove orphans flag to clean it up building jolokia step from java jdk alpine service jolokia failed to build manifest for java jdk alpine not found manifest unknown manifest unknown jmx integration test go failed to start service jolokia exit status found orphan containers metricbeat snapshot http metricbeat snapshot haproxy metricbeat snapshot golang metricbeat snapshot etcd metricbeat snapshot envoyproxy metricbeat snapshot dropwizard metricbeat snapshot logstash metricbeat snapshot kafka for this project if you removed or renamed this service in your compose file you can run this command with the remove orphans flag to clean it up building jolokia step from java jdk alpine service jolokia failed to build manifest for java jdk alpine not found manifest unknown manifest unknown jmx integration test go failed to start service jolokia exit status jmx integration test go getting host for jolokia no container running for service fail testdata steps errors expand to view the steps failures show only the first steps failures filebeat shipping to next major stack environment next major testing filebeat skip diff mage pyt took min sec view more details a href description stack environment next major testing filebeat skip diff mage pythonintegtest metricbeat gointegtest mage gointegtest took min sec view more details a href description mage gointegtest metricbeat gointegtest mage gointegtest took min sec view more details a href description mage gointegtest metricbeat gointegtest mage gointegtest took min sec view more details a href description mage gointegtest metricbeat pythonintegtest mage pythonintegtest took min sec view more details a href description mage pythonintegtest metricbeat pythonintegtest mage pythonintegtest took min sec view more details a href description mage pythonintegtest metricbeat pythonintegtest mage pythonintegtest took min sec view more details a href description mage pythonintegtest x pack filebeat pythonintegtest mage pythonintegtest took min sec view more details a href description mage pythonintegtest x pack filebeat module compat prev minor stack environment prev minor testing filebeat skip diff took min sec view more details a href description stack environment prev minor testing filebeat skip diff pytest addopts k test xpack modules mage pythonintegtest error signal took min sec view more details a href description error hudson abortexception script returned exit code
0
21,668
3,911,983,806
IssuesEvent
2016-04-20 08:41:07
owncloud/client
https://api.github.com/repos/owncloud/client
closed
[Windows] WiFi performance fix not working for auto-updated clients
bug gold-ticket ReadyToTest sev2-high
The fix for #4294 (0ef9bd9) seems to fix newly installed clients only, auto-updated clients still activate the plugin until the user manually renames/removes the directory. Windows client version 2.1.1 (build 5837), installed and auto-updated since last December (before 0ef9bd9).
1.0
[Windows] WiFi performance fix not working for auto-updated clients - The fix for #4294 (0ef9bd9) seems to fix newly installed clients only, auto-updated clients still activate the plugin until the user manually renames/removes the directory. Windows client version 2.1.1 (build 5837), installed and auto-updated since last December (before 0ef9bd9).
non_priority
wifi performance fix not working for auto updated clients the fix for seems to fix newly installed clients only auto updated clients still activate the plugin until the user manually renames removes the directory windows client version build installed and auto updated since last december before
0
202,287
23,076,949,034
IssuesEvent
2022-07-26 01:09:15
AlexRogalskiy/sputnik
https://api.github.com/repos/AlexRogalskiy/sputnik
opened
CVE-2021-35065 (High) detected in glob-parent-5.1.2.tgz, glob-parent-3.1.0.tgz
security vulnerability
## CVE-2021-35065 - High Severity Vulnerability <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>glob-parent-5.1.2.tgz</b>, <b>glob-parent-3.1.0.tgz</b></p></summary> <p> <details><summary><b>glob-parent-5.1.2.tgz</b></p></summary> <p>Extract the non-magic parent path from a glob string.</p> <p>Library home page: <a href="https://registry.npmjs.org/glob-parent/-/glob-parent-5.1.2.tgz">https://registry.npmjs.org/glob-parent/-/glob-parent-5.1.2.tgz</a></p> <p>Path to dependency file: /package.json</p> <p>Path to vulnerable library: /node_modules/glob-parent/package.json</p> <p> Dependency Hierarchy: - eslint-7.28.0.tgz (Root Library) - :x: **glob-parent-5.1.2.tgz** (Vulnerable Library) </details> <details><summary><b>glob-parent-3.1.0.tgz</b></p></summary> <p>Strips glob magic from a string to provide the parent directory path</p> <p>Library home page: <a href="https://registry.npmjs.org/glob-parent/-/glob-parent-3.1.0.tgz">https://registry.npmjs.org/glob-parent/-/glob-parent-3.1.0.tgz</a></p> <p>Path to dependency file: /package.json</p> <p>Path to vulnerable library: /node_modules/lerna/node_modules/glob-parent/package.json</p> <p> Dependency Hierarchy: - lerna-2.11.0.tgz (Root Library) - :x: **glob-parent-3.1.0.tgz** (Vulnerable Library) </details> <p>Found in HEAD commit: <a href="https://github.com/AlexRogalskiy/sputnik/commit/4caaf310bd148f5659fc2a5ce980cb8a4f8a7658">4caaf310bd148f5659fc2a5ce980cb8a4f8a7658</a></p> <p>Found in base branch: <b>master</b></p> </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary> <p> The package glob-parent before 6.0.1 are vulnerable to Regular Expression Denial of Service (ReDoS) <p>Publish Date: 2021-06-22 <p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-35065>CVE-2021-35065</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-cj88-88mr-972w">https://github.com/advisories/GHSA-cj88-88mr-972w</a></p> <p>Release Date: 2021-06-22</p> <p>Fix Resolution (glob-parent): 6.0.1</p> <p>Direct dependency fix Resolution (eslint): 8.0.0</p><p>Fix Resolution (glob-parent): 6.0.1</p> <p>Direct dependency fix Resolution (lerna): 3.0.0</p> </p> </details> <p></p> *** Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
True
CVE-2021-35065 (High) detected in glob-parent-5.1.2.tgz, glob-parent-3.1.0.tgz - ## CVE-2021-35065 - High Severity Vulnerability <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>glob-parent-5.1.2.tgz</b>, <b>glob-parent-3.1.0.tgz</b></p></summary> <p> <details><summary><b>glob-parent-5.1.2.tgz</b></p></summary> <p>Extract the non-magic parent path from a glob string.</p> <p>Library home page: <a href="https://registry.npmjs.org/glob-parent/-/glob-parent-5.1.2.tgz">https://registry.npmjs.org/glob-parent/-/glob-parent-5.1.2.tgz</a></p> <p>Path to dependency file: /package.json</p> <p>Path to vulnerable library: /node_modules/glob-parent/package.json</p> <p> Dependency Hierarchy: - eslint-7.28.0.tgz (Root Library) - :x: **glob-parent-5.1.2.tgz** (Vulnerable Library) </details> <details><summary><b>glob-parent-3.1.0.tgz</b></p></summary> <p>Strips glob magic from a string to provide the parent directory path</p> <p>Library home page: <a href="https://registry.npmjs.org/glob-parent/-/glob-parent-3.1.0.tgz">https://registry.npmjs.org/glob-parent/-/glob-parent-3.1.0.tgz</a></p> <p>Path to dependency file: /package.json</p> <p>Path to vulnerable library: /node_modules/lerna/node_modules/glob-parent/package.json</p> <p> Dependency Hierarchy: - lerna-2.11.0.tgz (Root Library) - :x: **glob-parent-3.1.0.tgz** (Vulnerable Library) </details> <p>Found in HEAD commit: <a href="https://github.com/AlexRogalskiy/sputnik/commit/4caaf310bd148f5659fc2a5ce980cb8a4f8a7658">4caaf310bd148f5659fc2a5ce980cb8a4f8a7658</a></p> <p>Found in base branch: <b>master</b></p> </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary> <p> The package glob-parent before 6.0.1 are vulnerable to Regular Expression Denial of Service (ReDoS) <p>Publish Date: 2021-06-22 <p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-35065>CVE-2021-35065</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-cj88-88mr-972w">https://github.com/advisories/GHSA-cj88-88mr-972w</a></p> <p>Release Date: 2021-06-22</p> <p>Fix Resolution (glob-parent): 6.0.1</p> <p>Direct dependency fix Resolution (eslint): 8.0.0</p><p>Fix Resolution (glob-parent): 6.0.1</p> <p>Direct dependency fix Resolution (lerna): 3.0.0</p> </p> </details> <p></p> *** Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
non_priority
cve high detected in glob parent tgz glob parent tgz cve high severity vulnerability vulnerable libraries glob parent tgz glob parent tgz glob parent tgz extract the non magic parent path from a glob string library home page a href path to dependency file package json path to vulnerable library node modules glob parent package json dependency hierarchy eslint tgz root library x glob parent tgz vulnerable library glob parent tgz strips glob magic from a string to provide the parent directory path library home page a href path to dependency file package json path to vulnerable library node modules lerna node modules glob parent package json dependency hierarchy lerna tgz root library x glob parent tgz vulnerable library found in head commit a href found in base branch master vulnerability details the package glob parent before are vulnerable to regular expression denial of service redos publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required 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 glob parent direct dependency fix resolution eslint fix resolution glob parent direct dependency fix resolution lerna step up your open source security game with mend
0
8,719
27,172,165,187
IssuesEvent
2023-02-17 20:30:55
OneDrive/onedrive-api-docs
https://api.github.com/repos/OneDrive/onedrive-api-docs
closed
Search on group not working without Sites.Read.All permission
type:bug area:Docs automation:Closed
Searching in a Group Drive with a **Client Credentials** (Application permission) token doesn't work with the `Files.ReadWrite.All` permission. For example: `https://graph.microsoft.com/v1.0/groups/{GROUP_ID}/drive/root/search(q='newFileTest.docx')` ... results in a 403 Forbidden error: ```json { "error": { "code": "accessDenied", "message": "The caller does not have permission to perform the action.", "innerError": { "request-id": "**redacted**", "date": "2019-04-17T12:47:10" } } } ``` Only when the **Client Credentials** (Application permission) token has the `Sites.ReadWrite.All` permission (probably `Sites.Read.All` is enough already), search works. Please update the docs to clarify this behavior. --- #### Document Details ⚠ *Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.* * ID: 6a094aa0-adc5-9f08-d75e-bff6c5c42b4b * Version Independent ID: c674446f-0d55-5c4b-0d0a-bbddf184dd1b * Content: [Search for files - OneDrive API - OneDrive dev center](https://docs.microsoft.com/en-us/onedrive/developer/rest-api/api/driveitem_search?view=odsp-graph-online#feedback) * Content Source: [docs/rest-api/api/driveitem_search.md](https://github.com/OneDrive/onedrive-api-docs/blob/live/docs/rest-api/api/driveitem_search.md) * Product: **onedrive** * GitHub Login: @rgregg * Microsoft Alias: **rgregg**
1.0
Search on group not working without Sites.Read.All permission - Searching in a Group Drive with a **Client Credentials** (Application permission) token doesn't work with the `Files.ReadWrite.All` permission. For example: `https://graph.microsoft.com/v1.0/groups/{GROUP_ID}/drive/root/search(q='newFileTest.docx')` ... results in a 403 Forbidden error: ```json { "error": { "code": "accessDenied", "message": "The caller does not have permission to perform the action.", "innerError": { "request-id": "**redacted**", "date": "2019-04-17T12:47:10" } } } ``` Only when the **Client Credentials** (Application permission) token has the `Sites.ReadWrite.All` permission (probably `Sites.Read.All` is enough already), search works. Please update the docs to clarify this behavior. --- #### Document Details ⚠ *Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.* * ID: 6a094aa0-adc5-9f08-d75e-bff6c5c42b4b * Version Independent ID: c674446f-0d55-5c4b-0d0a-bbddf184dd1b * Content: [Search for files - OneDrive API - OneDrive dev center](https://docs.microsoft.com/en-us/onedrive/developer/rest-api/api/driveitem_search?view=odsp-graph-online#feedback) * Content Source: [docs/rest-api/api/driveitem_search.md](https://github.com/OneDrive/onedrive-api-docs/blob/live/docs/rest-api/api/driveitem_search.md) * Product: **onedrive** * GitHub Login: @rgregg * Microsoft Alias: **rgregg**
non_priority
search on group not working without sites read all permission searching in a group drive with a client credentials application permission token doesn t work with the files readwrite all permission for example results in a forbidden error json error code accessdenied message the caller does not have permission to perform the action innererror request id redacted date only when the client credentials application permission token has the sites readwrite all permission probably sites read all is enough already search works please update the docs to clarify this behavior 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 onedrive github login rgregg microsoft alias rgregg
0
225,510
17,863,242,133
IssuesEvent
2021-09-06 05:54:43
MetagaussInc/Blazeforms-Revamped-Frontend
https://api.github.com/repos/MetagaussInc/Blazeforms-Revamped-Frontend
closed
Add form popup-description field validation message not showing properly.[Form-view]
bug low Ready For Retest
1. Click on Add form. 2. Description validation message not showing properly. Check here- ![image](https://user-images.githubusercontent.com/77260614/131886135-67a7c799-b002-4bb7-92f1-36995e4690a1.png)
1.0
Add form popup-description field validation message not showing properly.[Form-view] - 1. Click on Add form. 2. Description validation message not showing properly. Check here- ![image](https://user-images.githubusercontent.com/77260614/131886135-67a7c799-b002-4bb7-92f1-36995e4690a1.png)
non_priority
add form popup description field validation message not showing properly click on add form description validation message not showing properly check here
0
391,725
26,905,495,573
IssuesEvent
2023-02-06 18:43:18
microsoftgraph/microsoft-graph-docs
https://api.github.com/repos/microsoftgraph/microsoft-graph-docs
closed
serviceupdatemessage: Add info about filtering
request: documentation area: service health and communications
Please add more information which properties on `serviceupdatemessage` resource type support filtering. --- #### Document Details ⚠ *Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.* * ID: 3aeeb1ca-d222-6f26-d7d2-f0961bf18dae * Version Independent ID: fc2cf4b2-d797-acaa-8d91-6a1eba77da9a * Content: [serviceUpdateMessage resource type - Microsoft Graph v1.0](https://learn.microsoft.com/en-us/graph/api/resources/serviceupdatemessage?view=graph-rest-1.0#properties) * Content Source: [api-reference/v1.0/resources/serviceupdatemessage.md](https://github.com/microsoftgraph/microsoft-graph-docs/blob/main/api-reference/v1.0/resources/serviceupdatemessage.md) * Product: **service-communications** * Technology: **microsoft-graph** * GitHub Login: @payiAzure * Microsoft Alias: **MSGraphDocsVteam**
1.0
serviceupdatemessage: Add info about filtering - Please add more information which properties on `serviceupdatemessage` resource type support filtering. --- #### Document Details ⚠ *Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.* * ID: 3aeeb1ca-d222-6f26-d7d2-f0961bf18dae * Version Independent ID: fc2cf4b2-d797-acaa-8d91-6a1eba77da9a * Content: [serviceUpdateMessage resource type - Microsoft Graph v1.0](https://learn.microsoft.com/en-us/graph/api/resources/serviceupdatemessage?view=graph-rest-1.0#properties) * Content Source: [api-reference/v1.0/resources/serviceupdatemessage.md](https://github.com/microsoftgraph/microsoft-graph-docs/blob/main/api-reference/v1.0/resources/serviceupdatemessage.md) * Product: **service-communications** * Technology: **microsoft-graph** * GitHub Login: @payiAzure * Microsoft Alias: **MSGraphDocsVteam**
non_priority
serviceupdatemessage add info about filtering please add more information which properties on serviceupdatemessage resource type support filtering document details ⚠ do not edit this section it is required for learn microsoft com ➟ github issue linking id version independent id acaa content content source product service communications technology microsoft graph github login payiazure microsoft alias msgraphdocsvteam
0
69,330
7,131,497,172
IssuesEvent
2018-01-22 11:12:41
WebliniaERP/webliniaerp-web
https://api.github.com/repos/WebliniaERP/webliniaerp-web
closed
Visualizar comprovante de Pgto via PDV
1-problema 2-prioridade alta 3-HAGE SUPLEMENTOS duplicado test
Nao esta sendo possivel visualizar o comprovante de pgto após realizar a acao via PDV, por favor, queiram disponibilizar essa função para que seja possivel visualizar o comprovante e na sequencia imprimir
1.0
Visualizar comprovante de Pgto via PDV - Nao esta sendo possivel visualizar o comprovante de pgto após realizar a acao via PDV, por favor, queiram disponibilizar essa função para que seja possivel visualizar o comprovante e na sequencia imprimir
non_priority
visualizar comprovante de pgto via pdv nao esta sendo possivel visualizar o comprovante de pgto após realizar a acao via pdv por favor queiram disponibilizar essa função para que seja possivel visualizar o comprovante e na sequencia imprimir
0
129,389
18,092,943,259
IssuesEvent
2021-09-22 05:17:12
AlexRogalskiy/typescript-tools
https://api.github.com/repos/AlexRogalskiy/typescript-tools
closed
CVE-2012-6708 (Medium) detected in jquery-1.8.1.min.js
security vulnerability Status: Invalid
## CVE-2012-6708 - Medium Severity Vulnerability <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>jquery-1.8.1.min.js</b></p></summary> <p>JavaScript library for DOM operations</p> <p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/jquery/1.8.1/jquery.min.js">https://cdnjs.cloudflare.com/ajax/libs/jquery/1.8.1/jquery.min.js</a></p> <p>Path to dependency file: typescript-tools/node_modules/redeyed/examples/browser/index.html</p> <p>Path to vulnerable library: /node_modules/redeyed/examples/browser/index.html</p> <p> Dependency Hierarchy: - :x: **jquery-1.8.1.min.js** (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/AlexRogalskiy/typescript-tools/commit/afc1c33cea76f8d57316e4485c82961b29f04d08">afc1c33cea76f8d57316e4485c82961b29f04d08</a></p> <p>Found in base branch: <b>master</b></p> </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary> <p> jQuery before 1.9.0 is vulnerable to Cross-site Scripting (XSS) attacks. The jQuery(strInput) function does not differentiate selectors from HTML in a reliable fashion. In vulnerable versions, jQuery determined whether the input was HTML by looking for the '<' character anywhere in the string, giving attackers more flexibility when attempting to construct a malicious payload. In fixed versions, jQuery only deems the input to be HTML if it explicitly starts with the '<' character, limiting exploitability only to attackers who can control the beginning of a string, which is far less common. <p>Publish Date: 2018-01-18 <p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2012-6708>CVE-2012-6708</a></p> </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>6.1</b>)</summary> <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: Required - Scope: Changed - Impact Metrics: - Confidentiality Impact: Low - Integrity Impact: Low - Availability Impact: None </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary> <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://nvd.nist.gov/vuln/detail/CVE-2012-6708">https://nvd.nist.gov/vuln/detail/CVE-2012-6708</a></p> <p>Release Date: 2018-01-18</p> <p>Fix Resolution: jQuery - v1.9.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-2012-6708 (Medium) detected in jquery-1.8.1.min.js - ## CVE-2012-6708 - Medium Severity Vulnerability <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>jquery-1.8.1.min.js</b></p></summary> <p>JavaScript library for DOM operations</p> <p>Library home page: <a href="https://cdnjs.cloudflare.com/ajax/libs/jquery/1.8.1/jquery.min.js">https://cdnjs.cloudflare.com/ajax/libs/jquery/1.8.1/jquery.min.js</a></p> <p>Path to dependency file: typescript-tools/node_modules/redeyed/examples/browser/index.html</p> <p>Path to vulnerable library: /node_modules/redeyed/examples/browser/index.html</p> <p> Dependency Hierarchy: - :x: **jquery-1.8.1.min.js** (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/AlexRogalskiy/typescript-tools/commit/afc1c33cea76f8d57316e4485c82961b29f04d08">afc1c33cea76f8d57316e4485c82961b29f04d08</a></p> <p>Found in base branch: <b>master</b></p> </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary> <p> jQuery before 1.9.0 is vulnerable to Cross-site Scripting (XSS) attacks. The jQuery(strInput) function does not differentiate selectors from HTML in a reliable fashion. In vulnerable versions, jQuery determined whether the input was HTML by looking for the '<' character anywhere in the string, giving attackers more flexibility when attempting to construct a malicious payload. In fixed versions, jQuery only deems the input to be HTML if it explicitly starts with the '<' character, limiting exploitability only to attackers who can control the beginning of a string, which is far less common. <p>Publish Date: 2018-01-18 <p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2012-6708>CVE-2012-6708</a></p> </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>6.1</b>)</summary> <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: Required - Scope: Changed - Impact Metrics: - Confidentiality Impact: Low - Integrity Impact: Low - Availability Impact: None </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary> <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://nvd.nist.gov/vuln/detail/CVE-2012-6708">https://nvd.nist.gov/vuln/detail/CVE-2012-6708</a></p> <p>Release Date: 2018-01-18</p> <p>Fix Resolution: jQuery - v1.9.0</p> </p> </details> <p></p> *** Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
non_priority
cve medium detected in jquery min js cve medium severity vulnerability vulnerable library jquery min js javascript library for dom operations library home page a href path to dependency file typescript tools node modules redeyed examples browser index html path to vulnerable library node modules redeyed examples browser index html dependency hierarchy x jquery min js vulnerable library found in head commit a href found in base branch master vulnerability details jquery before is vulnerable to cross site scripting xss attacks the jquery strinput function does not differentiate selectors from html in a reliable fashion in vulnerable versions jquery determined whether the input was html by looking for the character anywhere in the string giving attackers more flexibility when attempting to construct a malicious payload in fixed versions jquery only deems the input to be html if it explicitly starts with the character limiting exploitability only to attackers who can control the beginning of a string which is far less common 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 jquery step up your open source security game with whitesource
0
19,653
3,228,782,275
IssuesEvent
2015-10-12 06:59:40
hazelcast/hazelcast
https://api.github.com/repos/hazelcast/hazelcast
closed
[TEST-FAILURE] TransactionalMapReadQuorumTest failures
Team: Core Type: Defect
com.hazelcast.quorum.TransactionalMapReadQuorumTest.testTxGetThrowsExceptionWhenQuorumSizeNotMet[Executing: TransactionOptions{timeoutMillis=120000, durability=1, txType=TWO_PHASE}] com.hazelcast.quorum.TransactionalMapReadQuorumTest.testTxContainsKeyThrowsExceptionWhenQuorumSizeNotMet[Executing: TransactionOptions{timeoutMillis=120000, durability=1, txType=TWO_PHASE}] com.hazelcast.quorum.TransactionalMapReadQuorumTest.testTxGetThrowsExceptionWhenQuorumSizeNotMet[Executing: TransactionOptions{timeoutMillis=120000, durability=1, txType=LOCAL}] com.hazelcast.quorum.TransactionalMapReadQuorumTest.testTxContainsKeyThrowsExceptionWhenQuorumSizeNotMet[Executing: TransactionOptions{timeoutMillis=120000, durability=1, txType=LOCAL}] ``` java.lang.AssertionError: Expected exception: com.hazelcast.transaction.TransactionException at org.junit.internal.runners.statements.ExpectException.evaluate(ExpectException.java:32) at com.hazelcast.test.AbstractHazelcastClassRunner$ThreadDumpAwareRunAfters.evaluate(AbstractHazelcastClassRunner.java:134) at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78) at com.hazelcast.test.HazelcastParallelClassRunner.access$201(HazelcastParallelClassRunner.java:29) at com.hazelcast.test.HazelcastParallelClassRunner$TestRunner.run(HazelcastParallelClassRunner.java:89) at java.lang.Thread.run(Thread.java:738) ``` https://hazelcast-l337.ci.cloudbees.com/job/Hazelcast-3.x-IbmJDK1.6/626/
1.0
[TEST-FAILURE] TransactionalMapReadQuorumTest failures - com.hazelcast.quorum.TransactionalMapReadQuorumTest.testTxGetThrowsExceptionWhenQuorumSizeNotMet[Executing: TransactionOptions{timeoutMillis=120000, durability=1, txType=TWO_PHASE}] com.hazelcast.quorum.TransactionalMapReadQuorumTest.testTxContainsKeyThrowsExceptionWhenQuorumSizeNotMet[Executing: TransactionOptions{timeoutMillis=120000, durability=1, txType=TWO_PHASE}] com.hazelcast.quorum.TransactionalMapReadQuorumTest.testTxGetThrowsExceptionWhenQuorumSizeNotMet[Executing: TransactionOptions{timeoutMillis=120000, durability=1, txType=LOCAL}] com.hazelcast.quorum.TransactionalMapReadQuorumTest.testTxContainsKeyThrowsExceptionWhenQuorumSizeNotMet[Executing: TransactionOptions{timeoutMillis=120000, durability=1, txType=LOCAL}] ``` java.lang.AssertionError: Expected exception: com.hazelcast.transaction.TransactionException at org.junit.internal.runners.statements.ExpectException.evaluate(ExpectException.java:32) at com.hazelcast.test.AbstractHazelcastClassRunner$ThreadDumpAwareRunAfters.evaluate(AbstractHazelcastClassRunner.java:134) at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78) at com.hazelcast.test.HazelcastParallelClassRunner.access$201(HazelcastParallelClassRunner.java:29) at com.hazelcast.test.HazelcastParallelClassRunner$TestRunner.run(HazelcastParallelClassRunner.java:89) at java.lang.Thread.run(Thread.java:738) ``` https://hazelcast-l337.ci.cloudbees.com/job/Hazelcast-3.x-IbmJDK1.6/626/
non_priority
transactionalmapreadquorumtest failures com hazelcast quorum transactionalmapreadquorumtest testtxgetthrowsexceptionwhenquorumsizenotmet com hazelcast quorum transactionalmapreadquorumtest testtxcontainskeythrowsexceptionwhenquorumsizenotmet com hazelcast quorum transactionalmapreadquorumtest testtxgetthrowsexceptionwhenquorumsizenotmet com hazelcast quorum transactionalmapreadquorumtest testtxcontainskeythrowsexceptionwhenquorumsizenotmet java lang assertionerror expected exception com hazelcast transaction transactionexception at org junit internal runners statements expectexception evaluate expectexception java at com hazelcast test abstracthazelcastclassrunner threaddumpawarerunafters evaluate abstracthazelcastclassrunner java at org junit runners parentrunner runleaf parentrunner java at org junit runners runchild java at com hazelcast test hazelcastparallelclassrunner access hazelcastparallelclassrunner java at com hazelcast test hazelcastparallelclassrunner testrunner run hazelcastparallelclassrunner java at java lang thread run thread java
0
137,873
18,769,338,480
IssuesEvent
2021-11-06 14:44:51
AlexRogalskiy/github-action-user-contribution
https://api.github.com/repos/AlexRogalskiy/github-action-user-contribution
opened
CVE-2021-33623 (High) detected in trim-newlines-1.0.0.tgz
security vulnerability
## CVE-2021-33623 - High Severity Vulnerability <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>trim-newlines-1.0.0.tgz</b></p></summary> <p>Trim newlines from the start and/or end of a string</p> <p>Library home page: <a href="https://registry.npmjs.org/trim-newlines/-/trim-newlines-1.0.0.tgz">https://registry.npmjs.org/trim-newlines/-/trim-newlines-1.0.0.tgz</a></p> <p>Path to dependency file: github-action-user-contribution/package.json</p> <p>Path to vulnerable library: github-action-user-contribution/node_modules/get-pkg-repo/node_modules/trim-newlines/package.json</p> <p> Dependency Hierarchy: - conventional-changelog-cli-2.1.1.tgz (Root Library) - conventional-changelog-3.1.24.tgz - conventional-changelog-core-4.2.2.tgz - get-pkg-repo-1.4.0.tgz - meow-3.7.0.tgz - :x: **trim-newlines-1.0.0.tgz** (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/AlexRogalskiy/github-action-user-contribution/commit/aa744014156b1e4ed6a2c7ac856937f7729f7b36">aa744014156b1e4ed6a2c7ac856937f7729f7b36</a></p> </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary> <p> The trim-newlines package before 3.0.1 and 4.x before 4.0.1 for Node.js has an issue related to regular expression denial-of-service (ReDoS) for the .end() method. <p>Publish Date: 2021-05-28 <p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-33623>CVE-2021-33623</a></p> </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary> <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: None - Integrity Impact: None - Availability Impact: High </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary> <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-33623">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-33623</a></p> <p>Release Date: 2021-05-28</p> <p>Fix Resolution: trim-newlines - 3.0.1, 4.0.1</p> </p> </details> <p></p> *** Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
True
CVE-2021-33623 (High) detected in trim-newlines-1.0.0.tgz - ## CVE-2021-33623 - High Severity Vulnerability <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>trim-newlines-1.0.0.tgz</b></p></summary> <p>Trim newlines from the start and/or end of a string</p> <p>Library home page: <a href="https://registry.npmjs.org/trim-newlines/-/trim-newlines-1.0.0.tgz">https://registry.npmjs.org/trim-newlines/-/trim-newlines-1.0.0.tgz</a></p> <p>Path to dependency file: github-action-user-contribution/package.json</p> <p>Path to vulnerable library: github-action-user-contribution/node_modules/get-pkg-repo/node_modules/trim-newlines/package.json</p> <p> Dependency Hierarchy: - conventional-changelog-cli-2.1.1.tgz (Root Library) - conventional-changelog-3.1.24.tgz - conventional-changelog-core-4.2.2.tgz - get-pkg-repo-1.4.0.tgz - meow-3.7.0.tgz - :x: **trim-newlines-1.0.0.tgz** (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/AlexRogalskiy/github-action-user-contribution/commit/aa744014156b1e4ed6a2c7ac856937f7729f7b36">aa744014156b1e4ed6a2c7ac856937f7729f7b36</a></p> </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary> <p> The trim-newlines package before 3.0.1 and 4.x before 4.0.1 for Node.js has an issue related to regular expression denial-of-service (ReDoS) for the .end() method. <p>Publish Date: 2021-05-28 <p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-33623>CVE-2021-33623</a></p> </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary> <p> Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: None - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: None - Integrity Impact: None - Availability Impact: High </p> For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>. </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary> <p> <p>Type: Upgrade version</p> <p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-33623">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-33623</a></p> <p>Release Date: 2021-05-28</p> <p>Fix Resolution: trim-newlines - 3.0.1, 4.0.1</p> </p> </details> <p></p> *** Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)
non_priority
cve high detected in trim newlines tgz cve high severity vulnerability vulnerable library trim newlines tgz trim newlines from the start and or end of a string library home page a href path to dependency file github action user contribution package json path to vulnerable library github action user contribution node modules get pkg repo node modules trim newlines package json dependency hierarchy conventional changelog cli tgz root library conventional changelog tgz conventional changelog core tgz get pkg repo tgz meow tgz x trim newlines tgz vulnerable library found in head commit a href vulnerability details the trim newlines package before and x before for node js has an issue related to regular expression denial of service redos for the end method 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 trim newlines step up your open source security game with whitesource
0
134,490
18,471,325,847
IssuesEvent
2021-10-17 19:43:55
samq-ghdemo/Java-Demo
https://api.github.com/repos/samq-ghdemo/Java-Demo
opened
CVE-2013-4002 (Medium) detected in xercesImpl-2.8.0.jar
security vulnerability
## CVE-2013-4002 - Medium Severity Vulnerability <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>xercesImpl-2.8.0.jar</b></p></summary> <p>Xerces2 is the next generation of high performance, fully compliant XML parsers in the Apache Xerces family. This new version of Xerces introduces the Xerces Native Interface (XNI), a complete framework for building parser components and configurations that is extremely modular and easy to program.</p> <p>Library home page: <a href="http://xerces.apache.org/xerces2-j">http://xerces.apache.org/xerces2-j</a></p> <p>Path to dependency file: Java-Demo/pom.xml</p> <p>Path to vulnerable library: /home/wss-scanner/.m2/repository/xerces/xercesImpl/2.8.0/xercesImpl-2.8.0.jar</p> <p> Dependency Hierarchy: - esapi-2.1.0.1.jar (Root Library) - xom-1.2.5.jar - :x: **xercesImpl-2.8.0.jar** (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/samq-ghdemo/Java-Demo/commit/3ac002d655870dcf124820ae1a9cd2e7e9121da6">3ac002d655870dcf124820ae1a9cd2e7e9121da6</a></p> <p>Found in base branch: <b>main</b></p> </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary> <p> XMLscanner.java in Apache Xerces2 Java Parser before 2.12.0, as used in the Java Runtime Environment (JRE) in IBM Java 5.0 before 5.0 SR16-FP3, 6 before 6 SR14, 6.0.1 before 6.0.1 SR6, and 7 before 7 SR5 as well as Oracle Java SE 7u40 and earlier, Java SE 6u60 and earlier, Java SE 5.0u51 and earlier, JRockit R28.2.8 and earlier, JRockit R27.7.6 and earlier, Java SE Embedded 7u40 and earlier, and possibly other products allows remote attackers to cause a denial of service via vectors related to XML attribute names. <p>Publish Date: 2013-07-23 <p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2013-4002>CVE-2013-4002</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: N/A - Attack Complexity: N/A - Privileges Required: N/A - User Interaction: N/A - Scope: N/A - Impact Metrics: - Confidentiality Impact: N/A - Integrity Impact: N/A - Availability Impact: N/A </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-2013-4002">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2013-4002</a></p> <p>Release Date: 2013-07-23</p> <p>Fix Resolution: xerces:xercesImpl:Xerces-J_2_12_0</p> </p> </details> <p></p> <!-- <REMEDIATE>{"isOpenPROnVulnerability":false,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"Java","groupId":"xerces","packageName":"xercesImpl","packageVersion":"2.8.0","packageFilePaths":["/pom.xml"],"isTransitiveDependency":true,"dependencyTree":"org.owasp.esapi:esapi:2.1.0.1;xom:xom:1.2.5;xerces:xercesImpl:2.8.0","isMinimumFixVersionAvailable":true,"minimumFixVersion":"xerces:xercesImpl:Xerces-J_2_12_0"}],"baseBranches":["main"],"vulnerabilityIdentifier":"CVE-2013-4002","vulnerabilityDetails":"XMLscanner.java in Apache Xerces2 Java Parser before 2.12.0, as used in the Java Runtime Environment (JRE) in IBM Java 5.0 before 5.0 SR16-FP3, 6 before 6 SR14, 6.0.1 before 6.0.1 SR6, and 7 before 7 SR5 as well as Oracle Java SE 7u40 and earlier, Java SE 6u60 and earlier, Java SE 5.0u51 and earlier, JRockit R28.2.8 and earlier, JRockit R27.7.6 and earlier, Java SE Embedded 7u40 and earlier, and possibly other products allows remote attackers to cause a denial of service via vectors related to XML attribute names.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2013-4002","cvss3Severity":"medium","cvss3Score":"5.5","cvss3Metrics":{"A":"N/A","AC":"N/A","PR":"N/A","S":"N/A","C":"N/A","UI":"N/A","AV":"N/A","I":"N/A"},"extraData":{}}</REMEDIATE> -->
True
CVE-2013-4002 (Medium) detected in xercesImpl-2.8.0.jar - ## CVE-2013-4002 - Medium Severity Vulnerability <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>xercesImpl-2.8.0.jar</b></p></summary> <p>Xerces2 is the next generation of high performance, fully compliant XML parsers in the Apache Xerces family. This new version of Xerces introduces the Xerces Native Interface (XNI), a complete framework for building parser components and configurations that is extremely modular and easy to program.</p> <p>Library home page: <a href="http://xerces.apache.org/xerces2-j">http://xerces.apache.org/xerces2-j</a></p> <p>Path to dependency file: Java-Demo/pom.xml</p> <p>Path to vulnerable library: /home/wss-scanner/.m2/repository/xerces/xercesImpl/2.8.0/xercesImpl-2.8.0.jar</p> <p> Dependency Hierarchy: - esapi-2.1.0.1.jar (Root Library) - xom-1.2.5.jar - :x: **xercesImpl-2.8.0.jar** (Vulnerable Library) <p>Found in HEAD commit: <a href="https://github.com/samq-ghdemo/Java-Demo/commit/3ac002d655870dcf124820ae1a9cd2e7e9121da6">3ac002d655870dcf124820ae1a9cd2e7e9121da6</a></p> <p>Found in base branch: <b>main</b></p> </p> </details> <p></p> <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary> <p> XMLscanner.java in Apache Xerces2 Java Parser before 2.12.0, as used in the Java Runtime Environment (JRE) in IBM Java 5.0 before 5.0 SR16-FP3, 6 before 6 SR14, 6.0.1 before 6.0.1 SR6, and 7 before 7 SR5 as well as Oracle Java SE 7u40 and earlier, Java SE 6u60 and earlier, Java SE 5.0u51 and earlier, JRockit R28.2.8 and earlier, JRockit R27.7.6 and earlier, Java SE Embedded 7u40 and earlier, and possibly other products allows remote attackers to cause a denial of service via vectors related to XML attribute names. <p>Publish Date: 2013-07-23 <p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2013-4002>CVE-2013-4002</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: N/A - Attack Complexity: N/A - Privileges Required: N/A - User Interaction: N/A - Scope: N/A - Impact Metrics: - Confidentiality Impact: N/A - Integrity Impact: N/A - Availability Impact: N/A </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-2013-4002">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2013-4002</a></p> <p>Release Date: 2013-07-23</p> <p>Fix Resolution: xerces:xercesImpl:Xerces-J_2_12_0</p> </p> </details> <p></p> <!-- <REMEDIATE>{"isOpenPROnVulnerability":false,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"Java","groupId":"xerces","packageName":"xercesImpl","packageVersion":"2.8.0","packageFilePaths":["/pom.xml"],"isTransitiveDependency":true,"dependencyTree":"org.owasp.esapi:esapi:2.1.0.1;xom:xom:1.2.5;xerces:xercesImpl:2.8.0","isMinimumFixVersionAvailable":true,"minimumFixVersion":"xerces:xercesImpl:Xerces-J_2_12_0"}],"baseBranches":["main"],"vulnerabilityIdentifier":"CVE-2013-4002","vulnerabilityDetails":"XMLscanner.java in Apache Xerces2 Java Parser before 2.12.0, as used in the Java Runtime Environment (JRE) in IBM Java 5.0 before 5.0 SR16-FP3, 6 before 6 SR14, 6.0.1 before 6.0.1 SR6, and 7 before 7 SR5 as well as Oracle Java SE 7u40 and earlier, Java SE 6u60 and earlier, Java SE 5.0u51 and earlier, JRockit R28.2.8 and earlier, JRockit R27.7.6 and earlier, Java SE Embedded 7u40 and earlier, and possibly other products allows remote attackers to cause a denial of service via vectors related to XML attribute names.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2013-4002","cvss3Severity":"medium","cvss3Score":"5.5","cvss3Metrics":{"A":"N/A","AC":"N/A","PR":"N/A","S":"N/A","C":"N/A","UI":"N/A","AV":"N/A","I":"N/A"},"extraData":{}}</REMEDIATE> -->
non_priority
cve medium detected in xercesimpl jar cve medium severity vulnerability vulnerable library xercesimpl jar is the next generation of high performance fully compliant xml parsers in the apache xerces family this new version of xerces introduces the xerces native interface xni a complete framework for building parser components and configurations that is extremely modular and easy to program library home page a href path to dependency file java demo pom xml path to vulnerable library home wss scanner repository xerces xercesimpl xercesimpl jar dependency hierarchy esapi jar root library xom jar x xercesimpl jar vulnerable library found in head commit a href found in base branch main vulnerability details xmlscanner java in apache java parser before as used in the java runtime environment jre in ibm java before before before and before as well as oracle java se and earlier java se and earlier java se and earlier jrockit and earlier jrockit and earlier java se embedded and earlier and possibly other products allows remote attackers to cause a denial of service via vectors related to xml attribute names publish date url a href cvss score details base score metrics exploitability metrics attack vector n a attack complexity n a privileges required n a user interaction n a scope n a impact metrics confidentiality impact n a integrity impact n a availability impact n a for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution xerces xercesimpl xerces j isopenpronvulnerability false ispackagebased true isdefaultbranch true packages istransitivedependency true dependencytree org owasp esapi esapi xom xom xerces xercesimpl isminimumfixversionavailable true minimumfixversion xerces xercesimpl xerces j basebranches vulnerabilityidentifier cve vulnerabilitydetails xmlscanner java in apache java parser before as used in the java runtime environment jre in ibm java before before before and before as well as oracle java se and earlier java se and earlier java se and earlier jrockit and earlier jrockit and earlier java se embedded and earlier and possibly other products allows remote attackers to cause a denial of service via vectors related to xml attribute names vulnerabilityurl
0
45,358
7,179,124,438
IssuesEvent
2018-01-31 18:38:16
servo/servo
https://api.github.com/repos/servo/servo
closed
Doc builds are busted since the switch to rustup
A-documentation A-infrastructure I-bustage
Every doc build shows: ``` Error running mach: ['doc'] The error occurred in code that was called by the mach command. This is either a bug in the called code itself or in the way that mach is calling it. You should consider filing a bug for this issue. If filing a bug, please include the full output of mach, including this error message. The details of the failure are as follows: OSError: [Errno 2] No such file or directory File "/home/servo/buildbot/slave/doc/build/python/servo/post_build_commands.py", line 214, in doc rustc_path = check_output(["rustup" + BIN_SUFFIX, "which", "rustc"], env=env) File "/home/servo/buildbot/slave/doc/build/python/servo/command_base.py", line 153, in check_output return subprocess.check_output(*args, shell=sys.platform == 'win32', **kwargs) File "/usr/lib/python2.7/subprocess.py", line 566, in check_output process = Popen(stdout=PIPE, *popenargs, **kwargs) File "/usr/lib/python2.7/subprocess.py", line 710, in __init__ errread, errwrite) File "/usr/lib/python2.7/subprocess.py", line 1327, in _execute_child raise child_exception program finished with exit code 1 elapsedTime=10.037575 ```
1.0
Doc builds are busted since the switch to rustup - Every doc build shows: ``` Error running mach: ['doc'] The error occurred in code that was called by the mach command. This is either a bug in the called code itself or in the way that mach is calling it. You should consider filing a bug for this issue. If filing a bug, please include the full output of mach, including this error message. The details of the failure are as follows: OSError: [Errno 2] No such file or directory File "/home/servo/buildbot/slave/doc/build/python/servo/post_build_commands.py", line 214, in doc rustc_path = check_output(["rustup" + BIN_SUFFIX, "which", "rustc"], env=env) File "/home/servo/buildbot/slave/doc/build/python/servo/command_base.py", line 153, in check_output return subprocess.check_output(*args, shell=sys.platform == 'win32', **kwargs) File "/usr/lib/python2.7/subprocess.py", line 566, in check_output process = Popen(stdout=PIPE, *popenargs, **kwargs) File "/usr/lib/python2.7/subprocess.py", line 710, in __init__ errread, errwrite) File "/usr/lib/python2.7/subprocess.py", line 1327, in _execute_child raise child_exception program finished with exit code 1 elapsedTime=10.037575 ```
non_priority
doc builds are busted since the switch to rustup every doc build shows error running mach the error occurred in code that was called by the mach command this is either a bug in the called code itself or in the way that mach is calling it you should consider filing a bug for this issue if filing a bug please include the full output of mach including this error message the details of the failure are as follows oserror no such file or directory file home servo buildbot slave doc build python servo post build commands py line in doc rustc path check output env env file home servo buildbot slave doc build python servo command base py line in check output return subprocess check output args shell sys platform kwargs file usr lib subprocess py line in check output process popen stdout pipe popenargs kwargs file usr lib subprocess py line in init errread errwrite file usr lib subprocess py line in execute child raise child exception program finished with exit code elapsedtime
0
236,901
26,072,298,749
IssuesEvent
2022-12-24 01:15:08
nexmo-community/node-passwordless-login
https://api.github.com/repos/nexmo-community/node-passwordless-login
opened
body-parser-1.18.3.tgz: 1 vulnerabilities (highest severity is: 7.5)
security vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>body-parser-1.18.3.tgz</b></p></summary> <p></p> <p>Path to dependency file: /package.json</p> <p>Path to vulnerable library: /node_modules/qs/package.json</p> <p> </details> ## Vulnerabilities | CVE | Severity | <img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS | Dependency | Type | Fixed in (body-parser version) | Remediation Available | | ------------- | ------------- | ----- | ----- | ----- | ------------- | --- | | [CVE-2022-24999](https://www.mend.io/vulnerability-database/CVE-2022-24999) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | qs-6.5.2.tgz | Transitive | 1.19.0 | &#9989; | ## Details <details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2022-24999</summary> ### Vulnerable Library - <b>qs-6.5.2.tgz</b></p> <p>A querystring parser that supports nesting and arrays, with a depth limit</p> <p>Library home page: <a href="https://registry.npmjs.org/qs/-/qs-6.5.2.tgz">https://registry.npmjs.org/qs/-/qs-6.5.2.tgz</a></p> <p>Path to dependency file: /package.json</p> <p>Path to vulnerable library: /node_modules/qs/package.json</p> <p> Dependency Hierarchy: - body-parser-1.18.3.tgz (Root Library) - :x: **qs-6.5.2.tgz** (Vulnerable Library) <p>Found in base branch: <b>main</b></p> </p> <p></p> ### Vulnerability Details <p> qs before 6.10.3, as used in Express before 4.17.3 and other products, allows attackers to cause a Node process hang for an Express application because an __ proto__ key can be used. In many typical Express use cases, an unauthenticated remote attacker can place the attack payload in the query string of the URL that is used to visit the application, such as a[__proto__]=b&a[__proto__]&a[length]=100000000. The fix was backported to qs 6.9.7, 6.8.3, 6.7.3, 6.6.1, 6.5.3, 6.4.1, 6.3.3, and 6.2.4 (and therefore Express 4.17.3, which has "deps: qs@6.9.7" in its release description, is not vulnerable). <p>Publish Date: 2022-11-26 <p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-24999>CVE-2022-24999</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://www.cve.org/CVERecord?id=CVE-2022-24999">https://www.cve.org/CVERecord?id=CVE-2022-24999</a></p> <p>Release Date: 2022-11-26</p> <p>Fix Resolution (qs): 6.5.3</p> <p>Direct dependency fix Resolution (body-parser): 1.19.0</p> </p> <p></p> :rescue_worker_helmet: Automatic Remediation is available for this issue </details> *** <p>:rescue_worker_helmet: Automatic Remediation is available for this issue.</p>
True
body-parser-1.18.3.tgz: 1 vulnerabilities (highest severity is: 7.5) - <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>body-parser-1.18.3.tgz</b></p></summary> <p></p> <p>Path to dependency file: /package.json</p> <p>Path to vulnerable library: /node_modules/qs/package.json</p> <p> </details> ## Vulnerabilities | CVE | Severity | <img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS | Dependency | Type | Fixed in (body-parser version) | Remediation Available | | ------------- | ------------- | ----- | ----- | ----- | ------------- | --- | | [CVE-2022-24999](https://www.mend.io/vulnerability-database/CVE-2022-24999) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | qs-6.5.2.tgz | Transitive | 1.19.0 | &#9989; | ## Details <details> <summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2022-24999</summary> ### Vulnerable Library - <b>qs-6.5.2.tgz</b></p> <p>A querystring parser that supports nesting and arrays, with a depth limit</p> <p>Library home page: <a href="https://registry.npmjs.org/qs/-/qs-6.5.2.tgz">https://registry.npmjs.org/qs/-/qs-6.5.2.tgz</a></p> <p>Path to dependency file: /package.json</p> <p>Path to vulnerable library: /node_modules/qs/package.json</p> <p> Dependency Hierarchy: - body-parser-1.18.3.tgz (Root Library) - :x: **qs-6.5.2.tgz** (Vulnerable Library) <p>Found in base branch: <b>main</b></p> </p> <p></p> ### Vulnerability Details <p> qs before 6.10.3, as used in Express before 4.17.3 and other products, allows attackers to cause a Node process hang for an Express application because an __ proto__ key can be used. In many typical Express use cases, an unauthenticated remote attacker can place the attack payload in the query string of the URL that is used to visit the application, such as a[__proto__]=b&a[__proto__]&a[length]=100000000. The fix was backported to qs 6.9.7, 6.8.3, 6.7.3, 6.6.1, 6.5.3, 6.4.1, 6.3.3, and 6.2.4 (and therefore Express 4.17.3, which has "deps: qs@6.9.7" in its release description, is not vulnerable). <p>Publish Date: 2022-11-26 <p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-24999>CVE-2022-24999</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://www.cve.org/CVERecord?id=CVE-2022-24999">https://www.cve.org/CVERecord?id=CVE-2022-24999</a></p> <p>Release Date: 2022-11-26</p> <p>Fix Resolution (qs): 6.5.3</p> <p>Direct dependency fix Resolution (body-parser): 1.19.0</p> </p> <p></p> :rescue_worker_helmet: Automatic Remediation is available for this issue </details> *** <p>:rescue_worker_helmet: Automatic Remediation is available for this issue.</p>
non_priority
body parser tgz vulnerabilities highest severity is vulnerable library body parser tgz path to dependency file package json path to vulnerable library node modules qs package json vulnerabilities cve severity cvss dependency type fixed in body parser version remediation available high qs tgz transitive details cve vulnerable library qs tgz a querystring parser that supports nesting and arrays with a depth limit library home page a href path to dependency file package json path to vulnerable library node modules qs package json dependency hierarchy body parser tgz root library x qs tgz vulnerable library found in base branch main vulnerability details qs before as used in express before and other products allows attackers to cause a node process hang for an express application because an proto key can be used in many typical express use cases an unauthenticated remote attacker can place the attack payload in the query string of the url that is used to visit the application such as a b a a the fix was backported to qs and and therefore express which has deps qs in its release description is not vulnerable 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 qs direct dependency fix resolution body parser rescue worker helmet automatic remediation is available for this issue rescue worker helmet automatic remediation is available for this issue
0
9,123
24,056,041,000
IssuesEvent
2022-09-16 16:59:17
Northeastern-Electric-Racing/shepherd_bms
https://api.github.com/repos/Northeastern-Electric-Racing/shepherd_bms
closed
Create a compute board interface
Feature Architecture
The compute board interface should abstract the following on the compute board: 1) Controlling the fan speed (using NERduino PWM API) 2) Controlling mounting the charger (Not sure how this works really, maybe just toggling the AIRs) 3) Polling data from the current sensor 4) Toggling the AIR's (by sending a message to the motor controller) 5) Debugging / handling the latching fault on the board 6) Anything else that might come up that the user wants
1.0
Create a compute board interface - The compute board interface should abstract the following on the compute board: 1) Controlling the fan speed (using NERduino PWM API) 2) Controlling mounting the charger (Not sure how this works really, maybe just toggling the AIRs) 3) Polling data from the current sensor 4) Toggling the AIR's (by sending a message to the motor controller) 5) Debugging / handling the latching fault on the board 6) Anything else that might come up that the user wants
non_priority
create a compute board interface the compute board interface should abstract the following on the compute board controlling the fan speed using nerduino pwm api controlling mounting the charger not sure how this works really maybe just toggling the airs polling data from the current sensor toggling the air s by sending a message to the motor controller debugging handling the latching fault on the board anything else that might come up that the user wants
0
110,110
11,688,434,625
IssuesEvent
2020-03-05 14:32:19
JonathasSL/SmartParking
https://api.github.com/repos/JonathasSL/SmartParking
closed
Termo de Abertura de Projeto
documentation help wanted
[Termo de Abertura de Projeto](https://docs.google.com/document/d/1x1gz6puMgay8-oeZKew8PnbC0LMjeRiG/edit) ### Tópico 1 - [x] Nome do projeto - [x] Gerente do Projeto - [x] Cliente do Projeto - [x] Tipo do projeto - [x] Objetivo do projeto - [x] Benefícios que justificam o projeto - [x] Qualidade esperada do produto final (Requisitos de qualidade) ### Tópico 2 - [x] Oque será feito (Escopo) - [x] Oque não será feito - [x] Resultados/serviços/produtos a serem entregues - [x] Condições para início do projeto ### Tópico 3 - [x] Prazo previsto @JonathasSL - [x] Data prevista de início @JonathasSL - [x] Data prevista de término @JonathasSL ### Tópico 4 - [x] Recursos humanos - [x] Hardware - [x] Rede e serviços de hospedagem - [x] Software de terceiros - [x] Serviços e treinamento - [x] Total geral ### Tópico 5 - [x] Nomes - [x] Funções - [x] Assinaturas
1.0
Termo de Abertura de Projeto - [Termo de Abertura de Projeto](https://docs.google.com/document/d/1x1gz6puMgay8-oeZKew8PnbC0LMjeRiG/edit) ### Tópico 1 - [x] Nome do projeto - [x] Gerente do Projeto - [x] Cliente do Projeto - [x] Tipo do projeto - [x] Objetivo do projeto - [x] Benefícios que justificam o projeto - [x] Qualidade esperada do produto final (Requisitos de qualidade) ### Tópico 2 - [x] Oque será feito (Escopo) - [x] Oque não será feito - [x] Resultados/serviços/produtos a serem entregues - [x] Condições para início do projeto ### Tópico 3 - [x] Prazo previsto @JonathasSL - [x] Data prevista de início @JonathasSL - [x] Data prevista de término @JonathasSL ### Tópico 4 - [x] Recursos humanos - [x] Hardware - [x] Rede e serviços de hospedagem - [x] Software de terceiros - [x] Serviços e treinamento - [x] Total geral ### Tópico 5 - [x] Nomes - [x] Funções - [x] Assinaturas
non_priority
termo de abertura de projeto tópico nome do projeto gerente do projeto cliente do projeto tipo do projeto objetivo do projeto benefícios que justificam o projeto qualidade esperada do produto final requisitos de qualidade tópico oque será feito escopo oque não será feito resultados serviços produtos a serem entregues condições para início do projeto tópico prazo previsto jonathassl data prevista de início jonathassl data prevista de término jonathassl tópico recursos humanos hardware rede e serviços de hospedagem software de terceiros serviços e treinamento total geral tópico nomes funções assinaturas
0
292,787
25,238,131,228
IssuesEvent
2022-11-15 03:55:03
wtbarnes/synthesizAR
https://api.github.com/repos/wtbarnes/synthesizAR
closed
Simplify and expand tests
Testing
Currently, there are only a few integration tests (e.g. ones that span the whole pipeline). Additionally, they use the dask/distributed options which is unnecessary for testing basic functionality. These tests should be simplified and the number of tests expanded to included many other clients. One option would be to create a basic skeleton fixture that could be used by many instruments for testing their functionality. The dask tests should be kept (to insure that the parallelism continues to work), but moved to their own file.
1.0
Simplify and expand tests - Currently, there are only a few integration tests (e.g. ones that span the whole pipeline). Additionally, they use the dask/distributed options which is unnecessary for testing basic functionality. These tests should be simplified and the number of tests expanded to included many other clients. One option would be to create a basic skeleton fixture that could be used by many instruments for testing their functionality. The dask tests should be kept (to insure that the parallelism continues to work), but moved to their own file.
non_priority
simplify and expand tests currently there are only a few integration tests e g ones that span the whole pipeline additionally they use the dask distributed options which is unnecessary for testing basic functionality these tests should be simplified and the number of tests expanded to included many other clients one option would be to create a basic skeleton fixture that could be used by many instruments for testing their functionality the dask tests should be kept to insure that the parallelism continues to work but moved to their own file
0
319,730
23,787,398,945
IssuesEvent
2022-09-02 11:28:43
antstackio/hover-design
https://api.github.com/repos/antstackio/hover-design
closed
HOV-30 | NativeSelect component
documentation New Component P0
<!--- Provide a general summary of the issue in the Title above --> ## Expected Behavior Make a `<NativeSelect>` Component Features: - Should come with default `select` props - Inherit from `<select>` <!--- If you're describing a bug, tell us what should happen --> <!--- If you're suggesting a change/improvement, tell us how it should work --> ## Current Behavior No NativeSelect component - [ ] Make spec for NativeSelect component - [ ] Make the base component with API and without styles - [ ] add styling
1.0
HOV-30 | NativeSelect component - <!--- Provide a general summary of the issue in the Title above --> ## Expected Behavior Make a `<NativeSelect>` Component Features: - Should come with default `select` props - Inherit from `<select>` <!--- If you're describing a bug, tell us what should happen --> <!--- If you're suggesting a change/improvement, tell us how it should work --> ## Current Behavior No NativeSelect component - [ ] Make spec for NativeSelect component - [ ] Make the base component with API and without styles - [ ] add styling
non_priority
hov nativeselect component expected behavior make a component features should come with default select props inherit from current behavior no nativeselect component make spec for nativeselect component make the base component with api and without styles add styling
0
3,103
6,111,054,862
IssuesEvent
2017-06-21 16:11:01
nodejs/node
https://api.github.com/repos/nodejs/node
closed
"write after end" error when stdout was end()-ed
confirmed-bug process stream
<!-- Thank you for reporting an issue. This issue tracker is for bugs and issues found within Node.js core. If you require more general support please file an issue on our help repo. https://github.com/nodejs/help Please fill in as much of the template below as you're able. Version: output of `node -v` Platform: output of `uname -a` (UNIX), or version and 32 or 64-bit (Windows) Subsystem: if known, please specify affected core module name If possible, please provide code that demonstrates the problem, keeping it as simple and free of external dependencies as you are able. --> * **Version**: `master`, presumably all recent node major versions * **Platform**: OS X 10.10.5 * **Subsystem**: process/console <!-- Enter your issue details below this comment. --> `stdout`/`stderr` unexpectedly throw a `write after end` error when `end()` has been called on them, even though `end()` throws it's own error in `destroy()`/`destroySoon()` overriding the usual destroy code which is in `net.Socket`. Since it overrides the destroy code, I don't think it should ever actually destroy the stream, which the error seems to indicate, but it appears to destroy it nonetheless. Try in the REPL: ```js process.stderr.end('foo') // throws error, REPL catches it console.error('hello?') // Unexpectedly throws "write after end" ``` cc @nodejs/streams
1.0
"write after end" error when stdout was end()-ed - <!-- Thank you for reporting an issue. This issue tracker is for bugs and issues found within Node.js core. If you require more general support please file an issue on our help repo. https://github.com/nodejs/help Please fill in as much of the template below as you're able. Version: output of `node -v` Platform: output of `uname -a` (UNIX), or version and 32 or 64-bit (Windows) Subsystem: if known, please specify affected core module name If possible, please provide code that demonstrates the problem, keeping it as simple and free of external dependencies as you are able. --> * **Version**: `master`, presumably all recent node major versions * **Platform**: OS X 10.10.5 * **Subsystem**: process/console <!-- Enter your issue details below this comment. --> `stdout`/`stderr` unexpectedly throw a `write after end` error when `end()` has been called on them, even though `end()` throws it's own error in `destroy()`/`destroySoon()` overriding the usual destroy code which is in `net.Socket`. Since it overrides the destroy code, I don't think it should ever actually destroy the stream, which the error seems to indicate, but it appears to destroy it nonetheless. Try in the REPL: ```js process.stderr.end('foo') // throws error, REPL catches it console.error('hello?') // Unexpectedly throws "write after end" ``` cc @nodejs/streams
non_priority
write after end error when stdout was end ed thank you for reporting an issue this issue tracker is for bugs and issues found within node js core if you require more general support please file an issue on our help repo please fill in as much of the template below as you re able version output of node v platform output of uname a unix or version and or bit windows subsystem if known please specify affected core module name if possible please provide code that demonstrates the problem keeping it as simple and free of external dependencies as you are able version master presumably all recent node major versions platform os x subsystem process console stdout stderr unexpectedly throw a write after end error when end has been called on them even though end throws it s own error in destroy destroysoon overriding the usual destroy code which is in net socket since it overrides the destroy code i don t think it should ever actually destroy the stream which the error seems to indicate but it appears to destroy it nonetheless try in the repl js process stderr end foo throws error repl catches it console error hello unexpectedly throws write after end cc nodejs streams
0
386,179
26,671,068,306
IssuesEvent
2023-01-26 10:19:31
facebook/docusaurus
https://api.github.com/repos/facebook/docusaurus
closed
How do I use the component resolution md syntax in tsx to convert it to HTML?
documentation
### Have you read the Contributing Guidelines on issues? - [X] I have read the [Contributing Guidelines on issues](https://github.com/facebook/docusaurus/blob/main/CONTRIBUTING.md#reporting-new-issues). ### Description How do I use the component resolution md syntax in tsx to convert it to HTML? I don't want to generate documents statically, I want to use some of the features of md to make it dynamic! So I need to render the MD-parsing html in tsx ### Self-service - [X] I'd be willing to address this documentation request myself.
1.0
How do I use the component resolution md syntax in tsx to convert it to HTML? - ### Have you read the Contributing Guidelines on issues? - [X] I have read the [Contributing Guidelines on issues](https://github.com/facebook/docusaurus/blob/main/CONTRIBUTING.md#reporting-new-issues). ### Description How do I use the component resolution md syntax in tsx to convert it to HTML? I don't want to generate documents statically, I want to use some of the features of md to make it dynamic! So I need to render the MD-parsing html in tsx ### Self-service - [X] I'd be willing to address this documentation request myself.
non_priority
how do i use the component resolution md syntax in tsx to convert it to html have you read the contributing guidelines on issues i have read the description how do i use the component resolution md syntax in tsx to convert it to html i don t want to generate documents statically i want to use some of the features of md to make it dynamic so i need to render the md parsing html in tsx self service i d be willing to address this documentation request myself
0
45,281
11,624,017,544
IssuesEvent
2020-02-27 10:00:34
BOINC/boinc
https://api.github.com/repos/BOINC/boinc
opened
[mac][wx] build failure: wxWidgets 3.1.0 incompatible with macOS 10.15
C: Build System C: Client - Macintosh C: Manager C: Testing E: 1 day T: Defect
**Describe the bug** ``` wxWidgets-3.1.0/src/osx/webview_webkit.mm:35:10: fatal error: 'WebKit/HIWebView.h' file not found #include <WebKit/HIWebView.h> ^~~~~~~~~~~~~~~~~~~~ wxWidgets-3.1.0/src/osx/webview_webkit.mm:35:10: note: did not find header 'HIWebView.h' in framework 'WebKit' (loaded from '/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.15.sdk/System/Library/Frameworks') ``` **Steps To Reproduce** 1. Run `setupForBOINC.sh` (or just `buildWxMac.sh`) **System Information** - OS: macOS 10.15 (Xcode 11.3.1) - BOINC Version: master This again raises the question how this could escape integration testing. Which macOS platforms does Travis test on?
1.0
[mac][wx] build failure: wxWidgets 3.1.0 incompatible with macOS 10.15 - **Describe the bug** ``` wxWidgets-3.1.0/src/osx/webview_webkit.mm:35:10: fatal error: 'WebKit/HIWebView.h' file not found #include <WebKit/HIWebView.h> ^~~~~~~~~~~~~~~~~~~~ wxWidgets-3.1.0/src/osx/webview_webkit.mm:35:10: note: did not find header 'HIWebView.h' in framework 'WebKit' (loaded from '/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.15.sdk/System/Library/Frameworks') ``` **Steps To Reproduce** 1. Run `setupForBOINC.sh` (or just `buildWxMac.sh`) **System Information** - OS: macOS 10.15 (Xcode 11.3.1) - BOINC Version: master This again raises the question how this could escape integration testing. Which macOS platforms does Travis test on?
non_priority
build failure wxwidgets incompatible with macos describe the bug wxwidgets src osx webview webkit mm fatal error webkit hiwebview h file not found include wxwidgets src osx webview webkit mm note did not find header hiwebview h in framework webkit loaded from applications xcode app contents developer platforms macosx platform developer sdks sdk system library frameworks steps to reproduce run setupforboinc sh or just buildwxmac sh system information os macos xcode boinc version master this again raises the question how this could escape integration testing which macos platforms does travis test on
0
291,010
21,913,403,496
IssuesEvent
2022-05-21 12:26:26
StackStorm-Exchange/exchange-incubator
https://api.github.com/repos/StackStorm-Exchange/exchange-incubator
reopened
OBSOLETE - [HOWTO] Automatic transfer of packs
documentation
Once a pull request is reviewed and merged, the following needs to happen: 1. An empty repository should be bootstrapped in the StackStorm-Exchange org with [exchange-bootstrap.sh](https://github.com/StackStorm-Exchange/ci/blob/master/utils/exchange-bootstrap.sh). 2. The submitted pack should be transferred into that repository in one of the two ways: * as a new commit, if the pack has been submitted as a dir; * as a merge with `--allow-unrelated-histories` if the pack has been submitted as a submodule and has git history. 3. The submitted pack should be removed from this repository once the transfer is complete and verified (automatically). `exchange-bootstrap.sh` takes care of the CI, builds, and index updates, so the pack should automatically get to the Exchange index after the correct transfer, given it doesn't have linting errors (#6).
1.0
OBSOLETE - [HOWTO] Automatic transfer of packs - Once a pull request is reviewed and merged, the following needs to happen: 1. An empty repository should be bootstrapped in the StackStorm-Exchange org with [exchange-bootstrap.sh](https://github.com/StackStorm-Exchange/ci/blob/master/utils/exchange-bootstrap.sh). 2. The submitted pack should be transferred into that repository in one of the two ways: * as a new commit, if the pack has been submitted as a dir; * as a merge with `--allow-unrelated-histories` if the pack has been submitted as a submodule and has git history. 3. The submitted pack should be removed from this repository once the transfer is complete and verified (automatically). `exchange-bootstrap.sh` takes care of the CI, builds, and index updates, so the pack should automatically get to the Exchange index after the correct transfer, given it doesn't have linting errors (#6).
non_priority
obsolete automatic transfer of packs once a pull request is reviewed and merged the following needs to happen an empty repository should be bootstrapped in the stackstorm exchange org with the submitted pack should be transferred into that repository in one of the two ways as a new commit if the pack has been submitted as a dir as a merge with allow unrelated histories if the pack has been submitted as a submodule and has git history the submitted pack should be removed from this repository once the transfer is complete and verified automatically exchange bootstrap sh takes care of the ci builds and index updates so the pack should automatically get to the exchange index after the correct transfer given it doesn t have linting errors
0
307,029
26,512,999,288
IssuesEvent
2023-01-18 18:34:36
hashicorp/terraform-provider-google
https://api.github.com/repos/hashicorp/terraform-provider-google
opened
Failing test(s): TestAccSqlDatabaseInstance_ActiveDirectory
test failure
<!--- This is a template for reporting test failures on nightly builds. It should only be used by core contributors who have access to our CI/CD results. ---> <!-- i.e. "Consistently since X date" or "X% failure in MONTH" --> Failure rate: 100%, for the full history that we can see in TeamCity <!-- List all impacted tests for searchability. The title of the issue can instead list one or more groups of tests, or describe the overall root cause. --> Impacted tests: - TestAccSqlDatabaseInstance_ActiveDirectory <!-- Link to the nightly build(s), ideally with one impacted test opened --> Nightly builds: - [Link](https://ci-oss.hashicorp.engineering/viewLog.html?buildId=368190&tab=buildResultsDiv&buildTypeId=GoogleCloud_ProviderGoogleCloudGoogleProject#testNameId-5904787966955611785) <!-- The error message that displays in the tests tab, for reference --> Message: ``` ------- Stdout: ------- === RUN TestAccSqlDatabaseInstance_ActiveDirectory === PAUSE TestAccSqlDatabaseInstance_ActiveDirectory === CONT TestAccSqlDatabaseInstance_ActiveDirectory provider_test.go:307: Step 1/2 error: Error running apply: exit status 1 Error: Error waiting for Create Instance: with google_sql_database_instance.instance-with-ad, on terraform_plugin_test.tf line 21, in resource "google_sql_database_instance" "instance-with-ad": 21: resource "google_sql_database_instance" "instance-with-ad" { --- FAIL: TestAccSqlDatabaseInstance_ActiveDirectory (103.41s) FAIL ``` Internal error message provided by Cloud SQL team: ``` operation.status.message: "404 Not Found\n{\n \"code\": 404,\n \"errors\": [\n {\n \"domain\": \"global\",\n \"message\": \"The resource \'projects/w4c1c7f8bbbf17de3p-tp\' was not found\",\n \"reason\": \"notFound\"\n }\n ],\n \"message\": \"The resource \'projects/w4c1c7f8bbbf17de3p-tp\' was not found\",\n \"status\": \"NOT_FOUND\"\n}" operation.type: PREPARE_TENANT_PROJECT ``` Internal ticket with Cloud SQL team (contains some screenshots with slightly more info): b/264929444 Notes: I was not able to find `w4c1c7f8bbbf17de3p-tp` ever mentioned in our logs, and along with its name and the `PREPARE_TENANT_PROJECT` type, it appears to be a tenant project used internally for the SQL instance. We don't seem to see this error with the other SQL tests, and one of the main differences with this particular test is the use of `active_directory_config` config. We seem to have trouble with Active Directory in our tests, so this could be related to some of those issues (ie. Active Directory setup might not be working properly prior to the test running). Other tickets related to Active Directory tests: * https://github.com/GoogleCloudPlatform/magic-modules/pull/6368 * https://github.com/hashicorp/terraform-provider-google/issues/9238 * https://github.com/hashicorp/terraform-provider-google/issues/8660 * https://github.com/hashicorp/terraform-provider-google/issues/7159
1.0
Failing test(s): TestAccSqlDatabaseInstance_ActiveDirectory - <!--- This is a template for reporting test failures on nightly builds. It should only be used by core contributors who have access to our CI/CD results. ---> <!-- i.e. "Consistently since X date" or "X% failure in MONTH" --> Failure rate: 100%, for the full history that we can see in TeamCity <!-- List all impacted tests for searchability. The title of the issue can instead list one or more groups of tests, or describe the overall root cause. --> Impacted tests: - TestAccSqlDatabaseInstance_ActiveDirectory <!-- Link to the nightly build(s), ideally with one impacted test opened --> Nightly builds: - [Link](https://ci-oss.hashicorp.engineering/viewLog.html?buildId=368190&tab=buildResultsDiv&buildTypeId=GoogleCloud_ProviderGoogleCloudGoogleProject#testNameId-5904787966955611785) <!-- The error message that displays in the tests tab, for reference --> Message: ``` ------- Stdout: ------- === RUN TestAccSqlDatabaseInstance_ActiveDirectory === PAUSE TestAccSqlDatabaseInstance_ActiveDirectory === CONT TestAccSqlDatabaseInstance_ActiveDirectory provider_test.go:307: Step 1/2 error: Error running apply: exit status 1 Error: Error waiting for Create Instance: with google_sql_database_instance.instance-with-ad, on terraform_plugin_test.tf line 21, in resource "google_sql_database_instance" "instance-with-ad": 21: resource "google_sql_database_instance" "instance-with-ad" { --- FAIL: TestAccSqlDatabaseInstance_ActiveDirectory (103.41s) FAIL ``` Internal error message provided by Cloud SQL team: ``` operation.status.message: "404 Not Found\n{\n \"code\": 404,\n \"errors\": [\n {\n \"domain\": \"global\",\n \"message\": \"The resource \'projects/w4c1c7f8bbbf17de3p-tp\' was not found\",\n \"reason\": \"notFound\"\n }\n ],\n \"message\": \"The resource \'projects/w4c1c7f8bbbf17de3p-tp\' was not found\",\n \"status\": \"NOT_FOUND\"\n}" operation.type: PREPARE_TENANT_PROJECT ``` Internal ticket with Cloud SQL team (contains some screenshots with slightly more info): b/264929444 Notes: I was not able to find `w4c1c7f8bbbf17de3p-tp` ever mentioned in our logs, and along with its name and the `PREPARE_TENANT_PROJECT` type, it appears to be a tenant project used internally for the SQL instance. We don't seem to see this error with the other SQL tests, and one of the main differences with this particular test is the use of `active_directory_config` config. We seem to have trouble with Active Directory in our tests, so this could be related to some of those issues (ie. Active Directory setup might not be working properly prior to the test running). Other tickets related to Active Directory tests: * https://github.com/GoogleCloudPlatform/magic-modules/pull/6368 * https://github.com/hashicorp/terraform-provider-google/issues/9238 * https://github.com/hashicorp/terraform-provider-google/issues/8660 * https://github.com/hashicorp/terraform-provider-google/issues/7159
non_priority
failing test s testaccsqldatabaseinstance activedirectory failure rate for the full history that we can see in teamcity impacted tests testaccsqldatabaseinstance activedirectory nightly builds message stdout run testaccsqldatabaseinstance activedirectory pause testaccsqldatabaseinstance activedirectory cont testaccsqldatabaseinstance activedirectory provider test go step error error running apply exit status error error waiting for create instance with google sql database instance instance with ad on terraform plugin test tf line in resource google sql database instance instance with ad resource google sql database instance instance with ad fail testaccsqldatabaseinstance activedirectory fail internal error message provided by cloud sql team operation status message not found n n code n errors n message the resource projects tp was not found n status not found n operation type prepare tenant project internal ticket with cloud sql team contains some screenshots with slightly more info b notes i was not able to find tp ever mentioned in our logs and along with its name and the prepare tenant project type it appears to be a tenant project used internally for the sql instance we don t seem to see this error with the other sql tests and one of the main differences with this particular test is the use of active directory config config we seem to have trouble with active directory in our tests so this could be related to some of those issues ie active directory setup might not be working properly prior to the test running other tickets related to active directory tests
0
45,928
24,277,448,162
IssuesEvent
2022-09-28 14:47:25
Accenture/sfmc-devtools-copado
https://api.github.com/repos/Accenture/sfmc-devtools-copado
closed
[TASK] dont update package.json upon loading mcdev
chore performance node.js
Commit.js runs `npm install --save mcdev` but there is no need for the `--save` parameter here
True
[TASK] dont update package.json upon loading mcdev - Commit.js runs `npm install --save mcdev` but there is no need for the `--save` parameter here
non_priority
dont update package json upon loading mcdev commit js runs npm install save mcdev but there is no need for the save parameter here
0
326,469
27,993,866,539
IssuesEvent
2023-03-27 07:01:08
cockroachdb/cockroach
https://api.github.com/repos/cockroachdb/cockroach
opened
ccl/backupccl: TestDataDriven failed
C-test-failure O-robot branch-master
ccl/backupccl.TestDataDriven [failed](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Nightlies_StressBazel/9263157?buildTab=log) with [artifacts](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Nightlies_StressBazel/9263157?buildTab=artifacts#/) on master @ [2bd2c806ab3044569b09e0a205b5bc0452ad4e2b](https://github.com/cockroachdb/cockroach/commits/2bd2c806ab3044569b09e0a205b5bc0452ad4e2b): ``` ---- datadriven.go:242: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/4466/execroot/com_github_cockroachdb_cockroach/bazel-out/k8-fastbuild/bin/pkg/ccl/backupccl/backupccl_test_/backupccl_test.runfiles/com_github_cockroachdb_cockroach/pkg/ccl/backupccl/testdata/backup-restore/external-connections-nodelocal:206: query-sql [0 args] SELECT object_name, object_type, backup_type FROM [SHOW BACKUP LATEST IN 'external://full/nested' WITH incremental_location = 'external://inc/nested'] ORDER BY (object_name, backup_type); ---- d database full d database incremental foo table full foo table incremental public schema full public schema incremental schema schema full schema schema incremental === RUN TestDataDriven/external-connections-userfile/basic-restore-userfile datadriven.go:242: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/4466/execroot/com_github_cockroachdb_cockroach/bazel-out/k8-fastbuild/bin/pkg/ccl/backupccl/backupccl_test_/backupccl_test.runfiles/com_github_cockroachdb_cockroach/pkg/ccl/backupccl/testdata/backup-restore/external-connections-userfile:105: exec-sql [0 args] RESTORE DATABASE d FROM LATEST IN 'external://conn-foo/database' WITH new_db_name='d2' ---- datadriven.go:242: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/4466/execroot/com_github_cockroachdb_cockroach/bazel-out/k8-fastbuild/bin/pkg/ccl/backupccl/backupccl_test_/backupccl_test.runfiles/com_github_cockroachdb_cockroach/pkg/ccl/backupccl/testdata/backup-restore/external-connections-userfile:109: query-sql [0 args] SELECT * FROM d2.schema.foo ---- 1 2 3 datadriven.go:242: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/4466/execroot/com_github_cockroachdb_cockroach/bazel-out/k8-fastbuild/bin/pkg/ccl/backupccl/backupccl_test_/backupccl_test.runfiles/com_github_cockroachdb_cockroach/pkg/ccl/backupccl/testdata/backup-restore/external-connections-userfile:116: exec-sql [0 args] DROP DATABASE d2 CASCADE ---- datadriven.go:242: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/4466/execroot/com_github_cockroachdb_cockroach/bazel-out/k8-fastbuild/bin/pkg/ccl/backupccl/backupccl_test_/backupccl_test.runfiles/com_github_cockroachdb_cockroach/pkg/ccl/backupccl/testdata/backup-restore/external-connections-userfile:121: exec-sql [0 args] RESTORE TABLE d.schema.foo FROM LATEST IN 'external://conn-foo/table' WITH into_db = 'defaultdb' ---- datadriven.go:242: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/4466/execroot/com_github_cockroachdb_cockroach/bazel-out/k8-fastbuild/bin/pkg/ccl/backupccl/backupccl_test_/backupccl_test.runfiles/com_github_cockroachdb_cockroach/pkg/ccl/backupccl/testdata/backup-restore/external-connections-userfile:125: query-sql [0 args] SELECT * FROM defaultdb.schema.foo ---- 1 2 3 4 5 6 ``` <p>Parameters: <code>TAGS=bazel,gss,deadlock</code> </p> <details><summary>Help</summary> <p> See also: [How To Investigate a Go Test Failure \(internal\)](https://cockroachlabs.atlassian.net/l/c/HgfXfJgM) </p> </details> <details><summary>Same failure on other branches</summary> <p> - #99560 ccl/backupccl: TestDataDriven failed [C-test-failure O-robot T-disaster-recovery branch-release-23.1] </p> </details> /cc @cockroachdb/disaster-recovery <sub> [This test on roachdash](https://roachdash.crdb.dev/?filter=status:open%20t:.*TestDataDriven.*&sort=title+created&display=lastcommented+project) | [Improve this report!](https://github.com/cockroachdb/cockroach/tree/master/pkg/cmd/internal/issues) </sub>
1.0
ccl/backupccl: TestDataDriven failed - ccl/backupccl.TestDataDriven [failed](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Nightlies_StressBazel/9263157?buildTab=log) with [artifacts](https://teamcity.cockroachdb.com/buildConfiguration/Cockroach_Nightlies_StressBazel/9263157?buildTab=artifacts#/) on master @ [2bd2c806ab3044569b09e0a205b5bc0452ad4e2b](https://github.com/cockroachdb/cockroach/commits/2bd2c806ab3044569b09e0a205b5bc0452ad4e2b): ``` ---- datadriven.go:242: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/4466/execroot/com_github_cockroachdb_cockroach/bazel-out/k8-fastbuild/bin/pkg/ccl/backupccl/backupccl_test_/backupccl_test.runfiles/com_github_cockroachdb_cockroach/pkg/ccl/backupccl/testdata/backup-restore/external-connections-nodelocal:206: query-sql [0 args] SELECT object_name, object_type, backup_type FROM [SHOW BACKUP LATEST IN 'external://full/nested' WITH incremental_location = 'external://inc/nested'] ORDER BY (object_name, backup_type); ---- d database full d database incremental foo table full foo table incremental public schema full public schema incremental schema schema full schema schema incremental === RUN TestDataDriven/external-connections-userfile/basic-restore-userfile datadriven.go:242: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/4466/execroot/com_github_cockroachdb_cockroach/bazel-out/k8-fastbuild/bin/pkg/ccl/backupccl/backupccl_test_/backupccl_test.runfiles/com_github_cockroachdb_cockroach/pkg/ccl/backupccl/testdata/backup-restore/external-connections-userfile:105: exec-sql [0 args] RESTORE DATABASE d FROM LATEST IN 'external://conn-foo/database' WITH new_db_name='d2' ---- datadriven.go:242: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/4466/execroot/com_github_cockroachdb_cockroach/bazel-out/k8-fastbuild/bin/pkg/ccl/backupccl/backupccl_test_/backupccl_test.runfiles/com_github_cockroachdb_cockroach/pkg/ccl/backupccl/testdata/backup-restore/external-connections-userfile:109: query-sql [0 args] SELECT * FROM d2.schema.foo ---- 1 2 3 datadriven.go:242: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/4466/execroot/com_github_cockroachdb_cockroach/bazel-out/k8-fastbuild/bin/pkg/ccl/backupccl/backupccl_test_/backupccl_test.runfiles/com_github_cockroachdb_cockroach/pkg/ccl/backupccl/testdata/backup-restore/external-connections-userfile:116: exec-sql [0 args] DROP DATABASE d2 CASCADE ---- datadriven.go:242: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/4466/execroot/com_github_cockroachdb_cockroach/bazel-out/k8-fastbuild/bin/pkg/ccl/backupccl/backupccl_test_/backupccl_test.runfiles/com_github_cockroachdb_cockroach/pkg/ccl/backupccl/testdata/backup-restore/external-connections-userfile:121: exec-sql [0 args] RESTORE TABLE d.schema.foo FROM LATEST IN 'external://conn-foo/table' WITH into_db = 'defaultdb' ---- datadriven.go:242: /home/roach/.cache/bazel/_bazel_roach/c5a4e7d36696d9cd970af2045211a7df/sandbox/processwrapper-sandbox/4466/execroot/com_github_cockroachdb_cockroach/bazel-out/k8-fastbuild/bin/pkg/ccl/backupccl/backupccl_test_/backupccl_test.runfiles/com_github_cockroachdb_cockroach/pkg/ccl/backupccl/testdata/backup-restore/external-connections-userfile:125: query-sql [0 args] SELECT * FROM defaultdb.schema.foo ---- 1 2 3 4 5 6 ``` <p>Parameters: <code>TAGS=bazel,gss,deadlock</code> </p> <details><summary>Help</summary> <p> See also: [How To Investigate a Go Test Failure \(internal\)](https://cockroachlabs.atlassian.net/l/c/HgfXfJgM) </p> </details> <details><summary>Same failure on other branches</summary> <p> - #99560 ccl/backupccl: TestDataDriven failed [C-test-failure O-robot T-disaster-recovery branch-release-23.1] </p> </details> /cc @cockroachdb/disaster-recovery <sub> [This test on roachdash](https://roachdash.crdb.dev/?filter=status:open%20t:.*TestDataDriven.*&sort=title+created&display=lastcommented+project) | [Improve this report!](https://github.com/cockroachdb/cockroach/tree/master/pkg/cmd/internal/issues) </sub>
non_priority
ccl backupccl testdatadriven failed ccl backupccl testdatadriven with on master datadriven go home roach cache bazel bazel roach sandbox processwrapper sandbox execroot com github cockroachdb cockroach bazel out fastbuild bin pkg ccl backupccl backupccl test backupccl test runfiles com github cockroachdb cockroach pkg ccl backupccl testdata backup restore external connections nodelocal query sql select object name object type backup type from show backup latest in external full nested with incremental location external inc nested order by object name backup type d database full d database incremental foo table full foo table incremental public schema full public schema incremental schema schema full schema schema incremental run testdatadriven external connections userfile basic restore userfile datadriven go home roach cache bazel bazel roach sandbox processwrapper sandbox execroot com github cockroachdb cockroach bazel out fastbuild bin pkg ccl backupccl backupccl test backupccl test runfiles com github cockroachdb cockroach pkg ccl backupccl testdata backup restore external connections userfile exec sql restore database d from latest in external conn foo database with new db name datadriven go home roach cache bazel bazel roach sandbox processwrapper sandbox execroot com github cockroachdb cockroach bazel out fastbuild bin pkg ccl backupccl backupccl test backupccl test runfiles com github cockroachdb cockroach pkg ccl backupccl testdata backup restore external connections userfile query sql select from schema foo datadriven go home roach cache bazel bazel roach sandbox processwrapper sandbox execroot com github cockroachdb cockroach bazel out fastbuild bin pkg ccl backupccl backupccl test backupccl test runfiles com github cockroachdb cockroach pkg ccl backupccl testdata backup restore external connections userfile exec sql drop database cascade datadriven go home roach cache bazel bazel roach sandbox processwrapper sandbox execroot com github cockroachdb cockroach bazel out fastbuild bin pkg ccl backupccl backupccl test backupccl test runfiles com github cockroachdb cockroach pkg ccl backupccl testdata backup restore external connections userfile exec sql restore table d schema foo from latest in external conn foo table with into db defaultdb datadriven go home roach cache bazel bazel roach sandbox processwrapper sandbox execroot com github cockroachdb cockroach bazel out fastbuild bin pkg ccl backupccl backupccl test backupccl test runfiles com github cockroachdb cockroach pkg ccl backupccl testdata backup restore external connections userfile query sql select from defaultdb schema foo parameters tags bazel gss deadlock help see also same failure on other branches ccl backupccl testdatadriven failed cc cockroachdb disaster recovery
0
124,662
17,774,555,877
IssuesEvent
2021-08-30 17:27:56
elastic/kibana
https://api.github.com/repos/elastic/kibana
closed
[Docs] Manually disabling legacy URL aliases
Team:Security docs
Existing saved object types will be converted to become share-capable in the 8.0 release (#100489). As a result of this, "Legacy URL aliases" are created and consumers need to use the new `resolve` API to fetch objects from deep link URLs. When an object is resolved, if circumstances allow, it can result in a `conflict` outcome. Consumers will normally show a callout if this happens, but not always -- for example, if a secondary object on the page is resolved with a conflict, [consumers may opt to show an error instead](https://www.elastic.co/guide/en/kibana/master/sharing-saved-objects.html#sharing-saved-objects-faq-multiple-deep-link-objects). In these corner cases where we need to show an error message to a user, we should provide some actionable information with details on what this error is and how to fix it. This doesn't "fit" in the UI of Kibana itself as this is a broader platform concern and there is no UI to handle this. So we should produce an external docs page for it.
True
[Docs] Manually disabling legacy URL aliases - Existing saved object types will be converted to become share-capable in the 8.0 release (#100489). As a result of this, "Legacy URL aliases" are created and consumers need to use the new `resolve` API to fetch objects from deep link URLs. When an object is resolved, if circumstances allow, it can result in a `conflict` outcome. Consumers will normally show a callout if this happens, but not always -- for example, if a secondary object on the page is resolved with a conflict, [consumers may opt to show an error instead](https://www.elastic.co/guide/en/kibana/master/sharing-saved-objects.html#sharing-saved-objects-faq-multiple-deep-link-objects). In these corner cases where we need to show an error message to a user, we should provide some actionable information with details on what this error is and how to fix it. This doesn't "fit" in the UI of Kibana itself as this is a broader platform concern and there is no UI to handle this. So we should produce an external docs page for it.
non_priority
manually disabling legacy url aliases existing saved object types will be converted to become share capable in the release as a result of this legacy url aliases are created and consumers need to use the new resolve api to fetch objects from deep link urls when an object is resolved if circumstances allow it can result in a conflict outcome consumers will normally show a callout if this happens but not always for example if a secondary object on the page is resolved with a conflict in these corner cases where we need to show an error message to a user we should provide some actionable information with details on what this error is and how to fix it this doesn t fit in the ui of kibana itself as this is a broader platform concern and there is no ui to handle this so we should produce an external docs page for it
0
54,152
29,736,378,556
IssuesEvent
2023-06-14 01:30:10
frogatto/frogatto
https://api.github.com/repos/frogatto/frogatto
opened
weird lag / low fps before opening main menu
Anura Issue Bug Performance Issue
> If I am playing the game (Ryzen 5 3600X, 16GB DDR4 RAM, and GTX 1080) it kinda lags even though my FPS are at 60 (NVIDIA GeForce Experience is telling me this). When I press Escape to open up the menu and pause the game, it still runs for a few frames. When I close the menu, everything runs smoothly and then everything will happen again. —[@ClientQUI#5340 on Discord](https://discord.com/channels/225816341737766912/225816341737766912/1117932671063031868) https://github.com/frogatto/frogatto/assets/862627/b681a062-be22-48ae-9464-e8afca0dbfc5
True
weird lag / low fps before opening main menu - > If I am playing the game (Ryzen 5 3600X, 16GB DDR4 RAM, and GTX 1080) it kinda lags even though my FPS are at 60 (NVIDIA GeForce Experience is telling me this). When I press Escape to open up the menu and pause the game, it still runs for a few frames. When I close the menu, everything runs smoothly and then everything will happen again. —[@ClientQUI#5340 on Discord](https://discord.com/channels/225816341737766912/225816341737766912/1117932671063031868) https://github.com/frogatto/frogatto/assets/862627/b681a062-be22-48ae-9464-e8afca0dbfc5
non_priority
weird lag low fps before opening main menu if i am playing the game ryzen ram and gtx it kinda lags even though my fps are at nvidia geforce experience is telling me this when i press escape to open up the menu and pause the game it still runs for a few frames when i close the menu everything runs smoothly and then everything will happen again —
0
4,216
6,794,161,697
IssuesEvent
2017-11-01 10:54:22
singapore/renovate
https://api.github.com/repos/singapore/renovate
closed
Making MRs from a fork?
feat help wanted needs-requirements pri4-low wontfix
Hi, I'd like to use `renovate` on a project hosted on Gitlab. I went through the doc and managed to set it up on my project, but it seems it requires a `developer` permission on the project, to be able to create branches. Would it be possible to make it create MR from its own fork, to avoid granting too much permissions to the bot account? Thanks!
1.0
Making MRs from a fork? - Hi, I'd like to use `renovate` on a project hosted on Gitlab. I went through the doc and managed to set it up on my project, but it seems it requires a `developer` permission on the project, to be able to create branches. Would it be possible to make it create MR from its own fork, to avoid granting too much permissions to the bot account? Thanks!
non_priority
making mrs from a fork hi i d like to use renovate on a project hosted on gitlab i went through the doc and managed to set it up on my project but it seems it requires a developer permission on the project to be able to create branches would it be possible to make it create mr from its own fork to avoid granting too much permissions to the bot account thanks
0