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 1k | labels stringlengths 4 1.38k | body stringlengths 1 262k | index stringclasses 16
values | text_combine stringlengths 96 262k | label stringclasses 2
values | text stringlengths 96 252k | binary_label int64 0 1 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
171,306 | 6,486,167,570 | IssuesEvent | 2017-08-19 17:11:20 | SacredDuckwhale/TotalAP | https://api.github.com/repos/SacredDuckwhale/TotalAP | opened | Support for the Underlight Angler (fishing artifact) | module:controllers module:core module:gui priority:normal status:confirmed type:feature | I haven't had time to get it done yet, but the foundation to implementing this easily has been laid with the new GUI and DB interface. It's not the highest priority task, and obtaining the artifact and testing the feature will take up more time than adding it.
See [CF#3](https://wow.curseforge.com/projects/totalap/issues/3) for details. | 1.0 | Support for the Underlight Angler (fishing artifact) - I haven't had time to get it done yet, but the foundation to implementing this easily has been laid with the new GUI and DB interface. It's not the highest priority task, and obtaining the artifact and testing the feature will take up more time than adding it.
See [CF#3](https://wow.curseforge.com/projects/totalap/issues/3) for details. | priority | support for the underlight angler fishing artifact i haven t had time to get it done yet but the foundation to implementing this easily has been laid with the new gui and db interface it s not the highest priority task and obtaining the artifact and testing the feature will take up more time than adding it see for details | 1 |
23,783 | 2,663,381,266 | IssuesEvent | 2015-03-20 04:42:18 | AtlasOfLivingAustralia/layers-service | https://api.github.com/repos/AtlasOfLivingAustralia/layers-service | reopened | Load Layer: Important Bird Areas (IBAs) - Australia | priority-high type-enhancement | The Important Bird (and Biodiversity) Areas (see http://www.birdlife.org.au/projects/important-bird-areas/iba-maps) are internationally recognised and IUCN-supported area of significane for bird species. They are in addition to CAPAD areas.
Criteria for IBAs (metadata): http://www.birdlife.org/datazone/info/ibacritglob
International data: http://www.birdlife.org/datazone/geomap.php?r=i&bbox=-150%20-50%20150%2080 but can't see how to get GIS data.
No counterparts to deprecate. | 1.0 | Load Layer: Important Bird Areas (IBAs) - Australia - The Important Bird (and Biodiversity) Areas (see http://www.birdlife.org.au/projects/important-bird-areas/iba-maps) are internationally recognised and IUCN-supported area of significane for bird species. They are in addition to CAPAD areas.
Criteria for IBAs (metadata): http://www.birdlife.org/datazone/info/ibacritglob
International data: http://www.birdlife.org/datazone/geomap.php?r=i&bbox=-150%20-50%20150%2080 but can't see how to get GIS data.
No counterparts to deprecate. | priority | load layer important bird areas ibas australia the important bird and biodiversity areas see are internationally recognised and iucn supported area of significane for bird species they are in addition to capad areas criteria for ibas metadata international data but can t see how to get gis data no counterparts to deprecate | 1 |
321,668 | 9,807,181,877 | IssuesEvent | 2019-06-12 13:11:41 | founders-programme-2/business-launchpad | https://api.github.com/repos/founders-programme-2/business-launchpad | opened | Sign up: client-side | T1d priority-2 | relates to #53
- create front end react form
- name
- email
- password
- send state to backend
| 1.0 | Sign up: client-side - relates to #53
- create front end react form
- name
- email
- password
- send state to backend
| priority | sign up client side relates to create front end react form name email password send state to backend | 1 |
43,076 | 12,965,181,214 | IssuesEvent | 2020-07-20 21:50:41 | jtimberlake/griffin | https://api.github.com/repos/jtimberlake/griffin | opened | CVE-2018-19839 (Medium) detected in node-sass-4.14.1.tgz, CSS::Sass-v3.6.0 | security vulnerability | ## CVE-2018-19839 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>node-sass-4.14.1.tgz</b></p></summary>
<p>
<details><summary><b>node-sass-4.14.1.tgz</b></p></summary>
<p>Wrapper around libsass</p>
<p>Library home page: <a href="https://registry.npmjs.org/node-sass/-/node-sass-4.14.1.tgz">https://registry.npmjs.org/node-sass/-/node-sass-4.14.1.tgz</a></p>
<p>Path to dependency file: /tmp/ws-scm/griffin/ui/angular/package.json</p>
<p>Path to vulnerable library: /tmp/ws-scm/griffin/ui/angular/node_modules/node-sass/package.json</p>
<p>
Dependency Hierarchy:
- cli-1.3.0.tgz (Root Library)
- :x: **node-sass-4.14.1.tgz** (Vulnerable Library)
</details>
<p>Found in HEAD commit: <a href="https://github.com/jtimberlake/griffin/commit/7b8d4cb53c4eab239eecb18da5b2a6048b2fce60">7b8d4cb53c4eab239eecb18da5b2a6048b2fce60</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
In LibSass prior to 3.5.5, the function handle_error in sass_context.cpp allows attackers to cause a denial-of-service resulting from a heap-based buffer over-read via a crafted sass file.
<p>Publish Date: 2018-12-04
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-19839>CVE-2018-19839</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>6.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-19839">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-19839</a></p>
<p>Release Date: 2018-12-04</p>
<p>Fix Resolution: Libsass:3.6.0</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":false,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"node-sass","packageVersion":"4.14.1","isTransitiveDependency":true,"dependencyTree":"@angular/cli:1.3.0;node-sass:4.14.1","isMinimumFixVersionAvailable":true,"minimumFixVersion":"Libsass:3.6.0"}],"vulnerabilityIdentifier":"CVE-2018-19839","vulnerabilityDetails":"In LibSass prior to 3.5.5, the function handle_error in sass_context.cpp allows attackers to cause a denial-of-service resulting from a heap-based buffer over-read via a crafted sass file.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-19839","cvss3Severity":"medium","cvss3Score":"6.5","cvss3Metrics":{"A":"High","AC":"Low","PR":"None","S":"Unchanged","C":"None","UI":"Required","AV":"Network","I":"None"},"extraData":{}}</REMEDIATE> --> | True | CVE-2018-19839 (Medium) detected in node-sass-4.14.1.tgz, CSS::Sass-v3.6.0 - ## CVE-2018-19839 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>node-sass-4.14.1.tgz</b></p></summary>
<p>
<details><summary><b>node-sass-4.14.1.tgz</b></p></summary>
<p>Wrapper around libsass</p>
<p>Library home page: <a href="https://registry.npmjs.org/node-sass/-/node-sass-4.14.1.tgz">https://registry.npmjs.org/node-sass/-/node-sass-4.14.1.tgz</a></p>
<p>Path to dependency file: /tmp/ws-scm/griffin/ui/angular/package.json</p>
<p>Path to vulnerable library: /tmp/ws-scm/griffin/ui/angular/node_modules/node-sass/package.json</p>
<p>
Dependency Hierarchy:
- cli-1.3.0.tgz (Root Library)
- :x: **node-sass-4.14.1.tgz** (Vulnerable Library)
</details>
<p>Found in HEAD commit: <a href="https://github.com/jtimberlake/griffin/commit/7b8d4cb53c4eab239eecb18da5b2a6048b2fce60">7b8d4cb53c4eab239eecb18da5b2a6048b2fce60</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
In LibSass prior to 3.5.5, the function handle_error in sass_context.cpp allows attackers to cause a denial-of-service resulting from a heap-based buffer over-read via a crafted sass file.
<p>Publish Date: 2018-12-04
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-19839>CVE-2018-19839</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>6.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-19839">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-19839</a></p>
<p>Release Date: 2018-12-04</p>
<p>Fix Resolution: Libsass:3.6.0</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":false,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"node-sass","packageVersion":"4.14.1","isTransitiveDependency":true,"dependencyTree":"@angular/cli:1.3.0;node-sass:4.14.1","isMinimumFixVersionAvailable":true,"minimumFixVersion":"Libsass:3.6.0"}],"vulnerabilityIdentifier":"CVE-2018-19839","vulnerabilityDetails":"In LibSass prior to 3.5.5, the function handle_error in sass_context.cpp allows attackers to cause a denial-of-service resulting from a heap-based buffer over-read via a crafted sass file.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-19839","cvss3Severity":"medium","cvss3Score":"6.5","cvss3Metrics":{"A":"High","AC":"Low","PR":"None","S":"Unchanged","C":"None","UI":"Required","AV":"Network","I":"None"},"extraData":{}}</REMEDIATE> --> | non_priority | cve medium detected in node sass tgz css sass cve medium severity vulnerability vulnerable libraries node sass tgz node sass tgz wrapper around libsass library home page a href path to dependency file tmp ws scm griffin ui angular package json path to vulnerable library tmp ws scm griffin ui angular node modules node sass package json dependency hierarchy cli tgz root library x node sass tgz vulnerable library found in head commit a href vulnerability details in libsass prior to the function handle error in sass context cpp allows attackers to cause a denial of service resulting from a heap based buffer over read via a crafted sass file publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction required scope unchanged impact metrics confidentiality impact none integrity impact none availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution libsass isopenpronvulnerability false ispackagebased true isdefaultbranch true packages vulnerabilityidentifier cve vulnerabilitydetails in libsass prior to the function handle error in sass context cpp allows attackers to cause a denial of service resulting from a heap based buffer over read via a crafted sass file vulnerabilityurl | 0 |
678,959 | 23,217,347,754 | IssuesEvent | 2022-08-02 15:03:52 | deckhouse/deckhouse | https://api.github.com/repos/deckhouse/deckhouse | closed | [metallb] BGP-based LoadBalancer IPs response only to legitimate IP:port requests | area/network status/rotten priority/backlog | ### Preflight Checklist
- [X] I agree to follow the [Code of Conduct](https://github.com/deckhouse/deckhouse/blob/main/CODE_OF_CONDUCT.md) that this project adheres to.
- [X] I have searched the [issue tracker](https://github.com/deckhouse/deckhouse/issues) for an issue that matches the one I want to file, without success.
### Version
v1.28
### Expected Behavior
There should be clear errors when trying to connect the wrong port of LoadBalancer or when trying to ping it:
```
$ telnet 10.40.0.168 2345
Trying 10.40.0.168...
telnet: Unable to connect to remote host: Connection refused
```
```
$ ping 10.40.0.168 -c 1
PING 10.40.0.168 (10.40.0.168) 56(84) bytes of data.
From 10.40.0.168 icmp_seq=1 Destination Port Unreachable
--- 10.40.0.168 ping statistics ---
1 packets transmitted, 0 received, +1 errors, 100% packet loss, time 0ms
```
Solution proposal:
* add speaker sidecar with a daemon which adds REJECT rules to every subnet or IP range in `metallb.addressPools`.
* if the #470 issue will be solved by adding the terminating REJECT rule, this issue will be solved automatically.
### Actual Behavior
The LB IPs don't respond at all (of the default FORWARD policy is DROP):
```
$ telnet 10.40.0.168 2345
Trying 10.40.0.168...
```
```
$ ping 10.40.0.168 -c 1 -w 1
PING 10.40.0.168 (10.40.0.168) 56(84) bytes of data.
--- 10.40.0.168 ping statistics ---
1 packets transmitted, 0 received, 100% packet loss, time 0ms
```
### Steps To Reproduce
_No response_
### Additional Information
_No response_
### Logs
_No response_ | 1.0 | [metallb] BGP-based LoadBalancer IPs response only to legitimate IP:port requests - ### Preflight Checklist
- [X] I agree to follow the [Code of Conduct](https://github.com/deckhouse/deckhouse/blob/main/CODE_OF_CONDUCT.md) that this project adheres to.
- [X] I have searched the [issue tracker](https://github.com/deckhouse/deckhouse/issues) for an issue that matches the one I want to file, without success.
### Version
v1.28
### Expected Behavior
There should be clear errors when trying to connect the wrong port of LoadBalancer or when trying to ping it:
```
$ telnet 10.40.0.168 2345
Trying 10.40.0.168...
telnet: Unable to connect to remote host: Connection refused
```
```
$ ping 10.40.0.168 -c 1
PING 10.40.0.168 (10.40.0.168) 56(84) bytes of data.
From 10.40.0.168 icmp_seq=1 Destination Port Unreachable
--- 10.40.0.168 ping statistics ---
1 packets transmitted, 0 received, +1 errors, 100% packet loss, time 0ms
```
Solution proposal:
* add speaker sidecar with a daemon which adds REJECT rules to every subnet or IP range in `metallb.addressPools`.
* if the #470 issue will be solved by adding the terminating REJECT rule, this issue will be solved automatically.
### Actual Behavior
The LB IPs don't respond at all (of the default FORWARD policy is DROP):
```
$ telnet 10.40.0.168 2345
Trying 10.40.0.168...
```
```
$ ping 10.40.0.168 -c 1 -w 1
PING 10.40.0.168 (10.40.0.168) 56(84) bytes of data.
--- 10.40.0.168 ping statistics ---
1 packets transmitted, 0 received, 100% packet loss, time 0ms
```
### Steps To Reproduce
_No response_
### Additional Information
_No response_
### Logs
_No response_ | priority | bgp based loadbalancer ips response only to legitimate ip port requests preflight checklist i agree to follow the that this project adheres to i have searched the for an issue that matches the one i want to file without success version expected behavior there should be clear errors when trying to connect the wrong port of loadbalancer or when trying to ping it telnet trying telnet unable to connect to remote host connection refused ping c ping bytes of data from icmp seq destination port unreachable ping statistics packets transmitted received errors packet loss time solution proposal add speaker sidecar with a daemon which adds reject rules to every subnet or ip range in metallb addresspools if the issue will be solved by adding the terminating reject rule this issue will be solved automatically actual behavior the lb ips don t respond at all of the default forward policy is drop telnet trying ping c w ping bytes of data ping statistics packets transmitted received packet loss time steps to reproduce no response additional information no response logs no response | 1 |
4,242 | 7,187,127,872 | IssuesEvent | 2018-02-02 03:06:28 | Great-Hill-Corporation/quickBlocks | https://api.github.com/repos/Great-Hill-Corporation/quickBlocks | closed | trace optimizations | monitors-all status-inprocess type-enhancement | If a trace has more than 50? 100? traces, then store the traces on the hard drive. 99% of the time needed to process a block with a big trace is taken by the node returning the traces and the javascript code parsing the JSON.
Add a field to the transaction structure called 'tracesOnDisk' which instructs the monitor to read the traces from disc and then only load them if we're doing --deep | 1.0 | trace optimizations - If a trace has more than 50? 100? traces, then store the traces on the hard drive. 99% of the time needed to process a block with a big trace is taken by the node returning the traces and the javascript code parsing the JSON.
Add a field to the transaction structure called 'tracesOnDisk' which instructs the monitor to read the traces from disc and then only load them if we're doing --deep | non_priority | trace optimizations if a trace has more than traces then store the traces on the hard drive of the time needed to process a block with a big trace is taken by the node returning the traces and the javascript code parsing the json add a field to the transaction structure called tracesondisk which instructs the monitor to read the traces from disc and then only load them if we re doing deep | 0 |
122,951 | 4,847,474,159 | IssuesEvent | 2016-11-10 15:03:35 | CSC-IT-Center-for-Science/iow-ui | https://api.github.com/repos/CSC-IT-Center-for-Science/iow-ui | closed | E2E tests with protractor | epic frontend High priority | # Sections
- [x] Frontpage
- [x] Add model
- [x] Edit model
- [x] Model vocabularies
- [x] Model reference data
- [x] Model links
- [x] Model namespaces
- [x] Remove model
- [x] Add class (by concept, reference, external)
- [x] Add predicate (by concept, reference, external)
- [x] Edit class
- [x] Add property (by concept, existing predicate, external)
- [x] Edit property
- [x] Property predicate view
- [x] Edit predicate
- [x] Remove class
- [x] Remove predicate
- [x] Remove property
- [ ] Concept editor ! wont fix before termeditor is in use
| 1.0 | E2E tests with protractor - # Sections
- [x] Frontpage
- [x] Add model
- [x] Edit model
- [x] Model vocabularies
- [x] Model reference data
- [x] Model links
- [x] Model namespaces
- [x] Remove model
- [x] Add class (by concept, reference, external)
- [x] Add predicate (by concept, reference, external)
- [x] Edit class
- [x] Add property (by concept, existing predicate, external)
- [x] Edit property
- [x] Property predicate view
- [x] Edit predicate
- [x] Remove class
- [x] Remove predicate
- [x] Remove property
- [ ] Concept editor ! wont fix before termeditor is in use
| priority | tests with protractor sections frontpage add model edit model model vocabularies model reference data model links model namespaces remove model add class by concept reference external add predicate by concept reference external edit class add property by concept existing predicate external edit property property predicate view edit predicate remove class remove predicate remove property concept editor wont fix before termeditor is in use | 1 |
2,394 | 2,725,873,674 | IssuesEvent | 2015-04-15 05:37:13 | adobe/brackets | https://api.github.com/repos/adobe/brackets | closed | Code folding markers broken after deleting selection across collapsed section | F Code Folding fix in progress high priority | 1. Start with this JS code:
```
define(function () {
var foo;
function one() {
foo = 1;
}
function two() {
foo = 2;
}
function three() {
foo = 3;
}
});
```
1. Collapse "two"
2. Select from the start of the `function` keyword in "two", to the start of the `function` keyword in "three"
3. Press delete
* Result: folding triangle for "one" now shows it's collapsed, even though function "one" is _not_ collapsed
4. Click the folding triangle for "one" repeatedly
* Result: nothing happens; triangle is nonresponsive
5. Undo
* Result: triangle for "one" still show's it's collapsed. Triangle for "two" shows it's _not_ collapsed even though it _is_
6. Click triangle for "two" repeatedly
* Result nothing happens on first click, but on 2nd click it starts working correctly
7. Click triangle for "one" repeatedly
* Result: it still does nothing
| 1.0 | Code folding markers broken after deleting selection across collapsed section - 1. Start with this JS code:
```
define(function () {
var foo;
function one() {
foo = 1;
}
function two() {
foo = 2;
}
function three() {
foo = 3;
}
});
```
1. Collapse "two"
2. Select from the start of the `function` keyword in "two", to the start of the `function` keyword in "three"
3. Press delete
* Result: folding triangle for "one" now shows it's collapsed, even though function "one" is _not_ collapsed
4. Click the folding triangle for "one" repeatedly
* Result: nothing happens; triangle is nonresponsive
5. Undo
* Result: triangle for "one" still show's it's collapsed. Triangle for "two" shows it's _not_ collapsed even though it _is_
6. Click triangle for "two" repeatedly
* Result nothing happens on first click, but on 2nd click it starts working correctly
7. Click triangle for "one" repeatedly
* Result: it still does nothing
| non_priority | code folding markers broken after deleting selection across collapsed section start with this js code define function var foo function one foo function two foo function three foo collapse two select from the start of the function keyword in two to the start of the function keyword in three press delete result folding triangle for one now shows it s collapsed even though function one is not collapsed click the folding triangle for one repeatedly result nothing happens triangle is nonresponsive undo result triangle for one still show s it s collapsed triangle for two shows it s not collapsed even though it is click triangle for two repeatedly result nothing happens on first click but on click it starts working correctly click triangle for one repeatedly result it still does nothing | 0 |
798,548 | 28,289,559,052 | IssuesEvent | 2023-04-09 02:44:23 | AY2223S2-CS2103T-W09-4/tp | https://api.github.com/repos/AY2223S2-CS2103T-W09-4/tp | closed | [PE-D][Tester D] [Minor] days instead of day | priority.Low type.FeatureFlaw | 
<!--session: 1680242808805-81f07706-8824-452e-a98e-ad93d1f47077--><!--Version: Web v3.4.7-->
-------------
Labels: `severity.VeryLow` `type.FunctionalityBug`
original: rockman007372/ped#9 | 1.0 | [PE-D][Tester D] [Minor] days instead of day - 
<!--session: 1680242808805-81f07706-8824-452e-a98e-ad93d1f47077--><!--Version: Web v3.4.7-->
-------------
Labels: `severity.VeryLow` `type.FunctionalityBug`
original: rockman007372/ped#9 | priority | days instead of day labels severity verylow type functionalitybug original ped | 1 |
605,730 | 18,739,636,201 | IssuesEvent | 2021-11-04 12:07:07 | tektoncd/operator | https://api.github.com/repos/tektoncd/operator | closed | tekton operator fails to deploy dashboard | kind/bug priority/critical-urgent | # Expected Behavior
The dashboard is not deployed via the operator with "all" profile
# Actual Behavior
```
panic: open /var/run/ko/tekton-dashboard/tekton-dashboard-fullaccess: no such file or directory
```
# Steps to Reproduce the Problem
Follow operator install instructions with "all" profile.
# Additional Info
- Kubernetes version:
1.22.1
```
│ {"level":"debug","logger":"tekton-operator","caller":"controller/controller.go:526","msg":"Processing from queue dashboar │
│ d (depth: 0)","knative.dev/pod":"tekton-operator-7dd98cb7fc-2l4j9","knative.dev/controller":"github.com.tektoncd.operator │
│ .pkg.reconciler.kubernetes.tektondashboard.Reconciler","knative.dev/kind":"operator.tekton.dev.TektonDashboard"} │
│ {"level":"info","logger":"tekton-operator","caller":"tektondashboard/tektondashboard.go:98","msg":"Reconciling TektonDash │
│ boards","knative.dev/pod":"tekton-operator-7dd98cb7fc-2l4j9","knative.dev/controller":"github.com.tektoncd.operator.pkg.r │
│ econciler.kubernetes.tektondashboard.Reconciler","knative.dev/kind":"operator.tekton.dev.TektonDashboard","knative.dev/tr │
│ aceid":"37da2fea-00ed-4675-a751-f986bac72a0c","knative.dev/key":"dashboard","status":{"observedGeneration":1,"conditions" │
│ :[{"type":"DependenciesInstalled","status":"Unknown","lastTransitionTime":"2021-10-26T21:47:42Z"},{"type":"DeploymentsAva │
│ ilable","status":"Unknown","lastTransitionTime":"2021-10-26T21:47:42Z"},{"type":"InstallSucceeded","status":"Unknown","la │
│ stTransitionTime":"2021-10-26T21:47:42Z"},{"type":"Ready","status":"Unknown","lastTransitionTime":"2021-10-26T21:47:42Z"} │
│ ]}} │
│ panic: open /var/run/ko/tekton-dashboard/tekton-dashboard-fullaccess: no such file or directory │
│ goroutine 856 [running]: │
│ github.com/tektoncd/operator/pkg/reconciler/common.latestRelease(...) │
│ github.com/tektoncd/operator/pkg/reconciler/common/releases.go:170 │
│ github.com/tektoncd/operator/pkg/reconciler/common.TargetVersion(0x1932b88, 0x40003bfa00, 0x400035b020, 0x3) │
│ github.com/tektoncd/operator/pkg/reconciler/common/releases.go:46 +0x90 │
│ github.com/tektoncd/operator/pkg/reconciler/common.TargetManifest(0x1932b88, 0x40003bfa00, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, │
│ 0x0, 0x146fc40, ...) │
│ github.com/tektoncd/operator/pkg/reconciler/common/releases.go:51 +0x40 │
│ github.com/tektoncd/operator/pkg/reconciler/common.AppendTarget(0x19088d8, 0x4001512720, 0x4000a5ea00, 0x1932b88, 0x40003 │
│ bfa00, 0x1604ee0, 0x4001303528) │
│ github.com/tektoncd/operator/pkg/reconciler/common/stages.go:51 +0x48 │
│ github.com/tektoncd/operator/pkg/reconciler/common.Stages.Execute(0x4001303680, 0x4, 0x4, 0x19088d8, 0x4001512720, 0x4000 │
│ a5ea00, 0x1932b88, 0x40003bfa00, 0x0, 0x0) │
│ github.com/tektoncd/operator/pkg/reconciler/common/stages.go:36 +0x74 │
│ github.com/tektoncd/operator/pkg/reconciler/kubernetes/tektondashboard.(*Reconciler).ReconcileKind(0x4000933e80, 0x19088d │
│ 8, 0x4001512720, 0x40003bfa00, 0x0, 0x0) │
│ github.com/tektoncd/operator/pkg/reconciler/kubernetes/tektondashboard/tektondashboard.go:133 +0xa80 │
│ github.com/tektoncd/operator/pkg/client/injection/reconciler/operator/v1alpha1/tektondashboard.(*reconcilerImpl).Reconcil │
│ e(0x40004bed20, 0x19088d8, 0x4001512720, 0x4000895ca4, 0x9, 0x4000356e50, 0x19088d8) │
│ github.com/tektoncd/operator/pkg/client/injection/reconciler/operator/v1alpha1/tektondashboard/reconciler.go:249 +0xe │
│ 50 │
│ knative.dev/pkg/controller.(*Impl).processNextWorkItem(0x4000978b40, 0x0) │
│ knative.dev/pkg@v0.0.0-20210827184538-2bd91f75571c/controller/controller.go:555 +0x3fc │
│ knative.dev/pkg/controller.(*Impl).RunContext.func3(0x4000b0a5a0, 0x4000978b40) │
│ knative.dev/pkg@v0.0.0-20210827184538-2bd91f75571c/controller/controller.go:491 +0x50 │
│ created by knative.dev/pkg/controller.(*Impl).RunContext │
│ knative.dev/pkg@v0.0.0-20210827184538-2bd91f75571c/controller/controller.go:489 +0x130 │
```
- Tekton Pipeline version:
**Output of `tkn version` or `kubectl get pods -n tekton-pipelines -l app=tekton-pipelines-controller -o=jsonpath='{.items[0].metadata.labels.version}'`**
v0.28.2
<!-- Any other additional information -->
| 1.0 | tekton operator fails to deploy dashboard - # Expected Behavior
The dashboard is not deployed via the operator with "all" profile
# Actual Behavior
```
panic: open /var/run/ko/tekton-dashboard/tekton-dashboard-fullaccess: no such file or directory
```
# Steps to Reproduce the Problem
Follow operator install instructions with "all" profile.
# Additional Info
- Kubernetes version:
1.22.1
```
│ {"level":"debug","logger":"tekton-operator","caller":"controller/controller.go:526","msg":"Processing from queue dashboar │
│ d (depth: 0)","knative.dev/pod":"tekton-operator-7dd98cb7fc-2l4j9","knative.dev/controller":"github.com.tektoncd.operator │
│ .pkg.reconciler.kubernetes.tektondashboard.Reconciler","knative.dev/kind":"operator.tekton.dev.TektonDashboard"} │
│ {"level":"info","logger":"tekton-operator","caller":"tektondashboard/tektondashboard.go:98","msg":"Reconciling TektonDash │
│ boards","knative.dev/pod":"tekton-operator-7dd98cb7fc-2l4j9","knative.dev/controller":"github.com.tektoncd.operator.pkg.r │
│ econciler.kubernetes.tektondashboard.Reconciler","knative.dev/kind":"operator.tekton.dev.TektonDashboard","knative.dev/tr │
│ aceid":"37da2fea-00ed-4675-a751-f986bac72a0c","knative.dev/key":"dashboard","status":{"observedGeneration":1,"conditions" │
│ :[{"type":"DependenciesInstalled","status":"Unknown","lastTransitionTime":"2021-10-26T21:47:42Z"},{"type":"DeploymentsAva │
│ ilable","status":"Unknown","lastTransitionTime":"2021-10-26T21:47:42Z"},{"type":"InstallSucceeded","status":"Unknown","la │
│ stTransitionTime":"2021-10-26T21:47:42Z"},{"type":"Ready","status":"Unknown","lastTransitionTime":"2021-10-26T21:47:42Z"} │
│ ]}} │
│ panic: open /var/run/ko/tekton-dashboard/tekton-dashboard-fullaccess: no such file or directory │
│ goroutine 856 [running]: │
│ github.com/tektoncd/operator/pkg/reconciler/common.latestRelease(...) │
│ github.com/tektoncd/operator/pkg/reconciler/common/releases.go:170 │
│ github.com/tektoncd/operator/pkg/reconciler/common.TargetVersion(0x1932b88, 0x40003bfa00, 0x400035b020, 0x3) │
│ github.com/tektoncd/operator/pkg/reconciler/common/releases.go:46 +0x90 │
│ github.com/tektoncd/operator/pkg/reconciler/common.TargetManifest(0x1932b88, 0x40003bfa00, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, │
│ 0x0, 0x146fc40, ...) │
│ github.com/tektoncd/operator/pkg/reconciler/common/releases.go:51 +0x40 │
│ github.com/tektoncd/operator/pkg/reconciler/common.AppendTarget(0x19088d8, 0x4001512720, 0x4000a5ea00, 0x1932b88, 0x40003 │
│ bfa00, 0x1604ee0, 0x4001303528) │
│ github.com/tektoncd/operator/pkg/reconciler/common/stages.go:51 +0x48 │
│ github.com/tektoncd/operator/pkg/reconciler/common.Stages.Execute(0x4001303680, 0x4, 0x4, 0x19088d8, 0x4001512720, 0x4000 │
│ a5ea00, 0x1932b88, 0x40003bfa00, 0x0, 0x0) │
│ github.com/tektoncd/operator/pkg/reconciler/common/stages.go:36 +0x74 │
│ github.com/tektoncd/operator/pkg/reconciler/kubernetes/tektondashboard.(*Reconciler).ReconcileKind(0x4000933e80, 0x19088d │
│ 8, 0x4001512720, 0x40003bfa00, 0x0, 0x0) │
│ github.com/tektoncd/operator/pkg/reconciler/kubernetes/tektondashboard/tektondashboard.go:133 +0xa80 │
│ github.com/tektoncd/operator/pkg/client/injection/reconciler/operator/v1alpha1/tektondashboard.(*reconcilerImpl).Reconcil │
│ e(0x40004bed20, 0x19088d8, 0x4001512720, 0x4000895ca4, 0x9, 0x4000356e50, 0x19088d8) │
│ github.com/tektoncd/operator/pkg/client/injection/reconciler/operator/v1alpha1/tektondashboard/reconciler.go:249 +0xe │
│ 50 │
│ knative.dev/pkg/controller.(*Impl).processNextWorkItem(0x4000978b40, 0x0) │
│ knative.dev/pkg@v0.0.0-20210827184538-2bd91f75571c/controller/controller.go:555 +0x3fc │
│ knative.dev/pkg/controller.(*Impl).RunContext.func3(0x4000b0a5a0, 0x4000978b40) │
│ knative.dev/pkg@v0.0.0-20210827184538-2bd91f75571c/controller/controller.go:491 +0x50 │
│ created by knative.dev/pkg/controller.(*Impl).RunContext │
│ knative.dev/pkg@v0.0.0-20210827184538-2bd91f75571c/controller/controller.go:489 +0x130 │
```
- Tekton Pipeline version:
**Output of `tkn version` or `kubectl get pods -n tekton-pipelines -l app=tekton-pipelines-controller -o=jsonpath='{.items[0].metadata.labels.version}'`**
v0.28.2
<!-- Any other additional information -->
| priority | tekton operator fails to deploy dashboard expected behavior the dashboard is not deployed via the operator with all profile actual behavior panic open var run ko tekton dashboard tekton dashboard fullaccess no such file or directory steps to reproduce the problem follow operator install instructions with all profile additional info kubernetes version │ level debug logger tekton operator caller controller controller go msg processing from queue dashboar │ │ d depth knative dev pod tekton operator knative dev controller github com tektoncd operator │ │ pkg reconciler kubernetes tektondashboard reconciler knative dev kind operator tekton dev tektondashboard │ │ level info logger tekton operator caller tektondashboard tektondashboard go msg reconciling tektondash │ │ boards knative dev pod tekton operator knative dev controller github com tektoncd operator pkg r │ │ econciler kubernetes tektondashboard reconciler knative dev kind operator tekton dev tektondashboard knative dev tr │ │ aceid knative dev key dashboard status observedgeneration conditions │ │ type dependenciesinstalled status unknown lasttransitiontime type deploymentsava │ │ ilable status unknown lasttransitiontime type installsucceeded status unknown la │ │ sttransitiontime type ready status unknown lasttransitiontime │ │ │ │ panic open var run ko tekton dashboard tekton dashboard fullaccess no such file or directory │ │ goroutine │ │ github com tektoncd operator pkg reconciler common latestrelease │ │ github com tektoncd operator pkg reconciler common releases go │ │ github com tektoncd operator pkg reconciler common targetversion │ │ github com tektoncd operator pkg reconciler common releases go │ │ github com tektoncd operator pkg reconciler common targetmanifest │ │ │ │ github com tektoncd operator pkg reconciler common releases go │ │ github com tektoncd operator pkg reconciler common appendtarget │ │ │ │ github com tektoncd operator pkg reconciler common stages go │ │ github com tektoncd operator pkg reconciler common stages execute │ │ │ │ github com tektoncd operator pkg reconciler common stages go │ │ github com tektoncd operator pkg reconciler kubernetes tektondashboard reconciler reconcilekind │ │ │ │ github com tektoncd operator pkg reconciler kubernetes tektondashboard tektondashboard go │ │ github com tektoncd operator pkg client injection reconciler operator tektondashboard reconcilerimpl reconcil │ │ e │ │ github com tektoncd operator pkg client injection reconciler operator tektondashboard reconciler go │ │ │ │ knative dev pkg controller impl processnextworkitem │ │ knative dev pkg controller controller go │ │ knative dev pkg controller impl runcontext │ │ knative dev pkg controller controller go │ │ created by knative dev pkg controller impl runcontext │ │ knative dev pkg controller controller go │ tekton pipeline version output of tkn version or kubectl get pods n tekton pipelines l app tekton pipelines controller o jsonpath items metadata labels version | 1 |
140,091 | 18,894,897,825 | IssuesEvent | 2021-11-15 16:48:17 | w3c/web-share | https://api.github.com/repos/w3c/web-share | opened | Split security & privacy considerations | privacy-tracker security-tracker | Please split security and privacy considerations into separate sections, as it has been claimed was done here, but appears to have not yet been done. https://github.com/w3c/security-request/issues/17#issuecomment-968988827 | True | Split security & privacy considerations - Please split security and privacy considerations into separate sections, as it has been claimed was done here, but appears to have not yet been done. https://github.com/w3c/security-request/issues/17#issuecomment-968988827 | non_priority | split security privacy considerations please split security and privacy considerations into separate sections as it has been claimed was done here but appears to have not yet been done | 0 |
373,549 | 11,045,547,946 | IssuesEvent | 2019-12-09 15:18:13 | openshift/odo | https://api.github.com/repos/openshift/odo | closed | No pre check is done for existence of same component in the cluster | kind/bug priority/High triage/unresolved | /kind bug
<!--
Welcome! - We kindly ask you to:
1. Fill out the issue template below
2. Use the Google group if you have a question rather than a bug or feature request.
The group is at: https://groups.google.com/forum/#!forum/odo-users
Thanks for understanding, and for contributing to the project!
-->
## What versions of software are you using?
**Operating System:**
supported
**Output of `odo version`:**
master
## How did you run odo exactly?
```
$ odo create nodejs backend --context
/Users/amit/go/src/github.com/openshift/odo/tests/examples/source/nodejs/
--project test123
$ odo push --context /Users/amit/go/src/github.com/openshift/odo/tests/examples/source/nodejs/
$ odo component list --context
/Users/amit/go/src/github.com/openshift/odo/tests/examples/source/nodejs/
APP NAME TYPE SOURCE STATE
app backend nodejs file://./ Pushed -------------- Looks good
$ odo create python backend --context
/Users/amit/go/src/github.com/openshift/odo/tests/examples/source/nodejs/
--project test123
$ odo push --context /Users/amit/go/src/github.com/openshift/odo/tests/examples/source/python/
$ odo component list --context /Users/amit/go/src/github.com/openshift/odo/tests/examples/source/nodejs/
APP NAME TYPE SOURCE STATE
app backend python file://./ Pushed <----- nodejs component is replaced
$ odo component list --context /Users/amit/go/src/github.com/openshift/odo/tests/examples/source/python/
APP NAME TYPE SOURCE STATE
app backend python file://./ Pushed <----- nodejs component is replaced
```
## Actual behavior
Replacing the deployed component of same name
## Expected behavior
Should throw error of something like
```There is already a component of same name exist in the same app and in same namespace.```
## Any logs, error output, etc?
| 1.0 | No pre check is done for existence of same component in the cluster - /kind bug
<!--
Welcome! - We kindly ask you to:
1. Fill out the issue template below
2. Use the Google group if you have a question rather than a bug or feature request.
The group is at: https://groups.google.com/forum/#!forum/odo-users
Thanks for understanding, and for contributing to the project!
-->
## What versions of software are you using?
**Operating System:**
supported
**Output of `odo version`:**
master
## How did you run odo exactly?
```
$ odo create nodejs backend --context
/Users/amit/go/src/github.com/openshift/odo/tests/examples/source/nodejs/
--project test123
$ odo push --context /Users/amit/go/src/github.com/openshift/odo/tests/examples/source/nodejs/
$ odo component list --context
/Users/amit/go/src/github.com/openshift/odo/tests/examples/source/nodejs/
APP NAME TYPE SOURCE STATE
app backend nodejs file://./ Pushed -------------- Looks good
$ odo create python backend --context
/Users/amit/go/src/github.com/openshift/odo/tests/examples/source/nodejs/
--project test123
$ odo push --context /Users/amit/go/src/github.com/openshift/odo/tests/examples/source/python/
$ odo component list --context /Users/amit/go/src/github.com/openshift/odo/tests/examples/source/nodejs/
APP NAME TYPE SOURCE STATE
app backend python file://./ Pushed <----- nodejs component is replaced
$ odo component list --context /Users/amit/go/src/github.com/openshift/odo/tests/examples/source/python/
APP NAME TYPE SOURCE STATE
app backend python file://./ Pushed <----- nodejs component is replaced
```
## Actual behavior
Replacing the deployed component of same name
## Expected behavior
Should throw error of something like
```There is already a component of same name exist in the same app and in same namespace.```
## Any logs, error output, etc?
| priority | no pre check is done for existence of same component in the cluster kind bug welcome we kindly ask you to fill out the issue template below use the google group if you have a question rather than a bug or feature request the group is at thanks for understanding and for contributing to the project what versions of software are you using operating system supported output of odo version master how did you run odo exactly odo create nodejs backend context users amit go src github com openshift odo tests examples source nodejs project odo push context users amit go src github com openshift odo tests examples source nodejs odo component list context users amit go src github com openshift odo tests examples source nodejs app name type source state app backend nodejs file pushed looks good odo create python backend context users amit go src github com openshift odo tests examples source nodejs project odo push context users amit go src github com openshift odo tests examples source python odo component list context users amit go src github com openshift odo tests examples source nodejs app name type source state app backend python file pushed nodejs component is replaced odo component list context users amit go src github com openshift odo tests examples source python app name type source state app backend python file pushed nodejs component is replaced actual behavior replacing the deployed component of same name expected behavior should throw error of something like there is already a component of same name exist in the same app and in same namespace any logs error output etc | 1 |
17,972 | 6,532,879,524 | IssuesEvent | 2017-08-31 02:11:35 | electron-userland/electron-packager | https://api.github.com/repos/electron-userland/electron-packager | closed | Electron win32 ia32 app is not working but x64 is | build-target:windows needs info | <!--
Thanks for filing an issue!
Please check off all of the steps as they are completed by replacing [ ] with [x].
-->
* [x] I have read the [contribution documentation](https://github.com/electron-userland/electron-packager/blob/master/CONTRIBUTING.md) for this project.
* [x] I agree to follow the [code of conduct](https://github.com/electron/electron/blob/master/CODE_OF_CONDUCT.md) that this project follows, as appropriate.
* [x] I have searched the issue tracker for an issue that matches the one I want to file, without success.
Hi,
I am using Windows 7 64bits and have used electron packager to build my project to both win32 ia32 and win32 x64
The x64 version is working perfectly on windows 64 bit machines but the ia32 version is not working on neither 32 bit or 64 bit machines. I click the 32bit executable and absolutely NOTHING happens.
This is very frusturating because I haven't found a single person who's had this issue before.
Please help!
Thank you.
**Console output when you run electron-packager with the environment variable `DEBUG=electron-packager`. Please include the stack trace if one exists.**
```
D:\GP>electron-packager . --arch=ia32
electron-packager Electron Packager 9.0.0 +0ms
electron-packager Node v6.11.2 +15ms
electron-packager Host Operating system: win32 (x64) +0ms
electron-packager Packager Options: {"":["."],"all":false,"derefSymlinks":true
,"download":{"strictSSL":true},"overwrite":false,"prune":true,"quiet":false,"arc
h":"ia32","DEBUG":"electron-packager","dir":".","protocols":[]} +0ms
electron-packager Target Platforms: win32 +0ms
electron-packager Target Architectures: ia32 +0ms
electron-packager Inferring application name from name in D:\GP\package.json +
0ms
electron-packager Inferring appVersion from version in D:\GP\package.json +0ms
electron-packager Inferring target Electron version from electron in D:\GP\pac
kage.json +16ms
electron-packager Application name: gp +32ms
electron-packager Target Electron version: 1.6.11 +0ms
electron-packager Ignored path regular expressions: [ '/node_modules/electron(
$|/)',
'/node_modules/electron-prebuilt(-compile)?($|/)',
'/node_modules/electron-packager($|/)',
'/\\.git($|/)',
'/node_modules/\\.bin($|/)',
'\\.o(bj)?$' ] +0ms
electron-packager Downloading Electron with options {"strictSSL":true,"platfor
m":"win32","arch":"ia32","version":"1.6.11"} +0ms
Skipping win32 ia32 (output dir already exists, use --overwrite to force)
D:\GP>electron-packager . --arch=ia32 --overwrite --DEBUG=electron-packager
electron-packager Electron Packager 9.0.0 +0ms
electron-packager Node v6.11.2 +0ms
electron-packager Host Operating system: win32 (x64) +0ms
electron-packager Packager Options: {"":["."],"all":false,"derefSymlinks":true
,"download":{"strictSSL":true},"overwrite":true,"prune":true,"quiet":false,"arch
":"ia32","DEBUG":"electron-packager","dir":".","protocols":[]} +0ms
electron-packager Target Platforms: win32 +0ms
electron-packager Target Architectures: ia32 +0ms
electron-packager Inferring application name from name in D:\GP\package.json +
0ms
electron-packager Inferring appVersion from version in D:\GP\package.json +16m
s
electron-packager Inferring target Electron version from electron in D:\GP\pac
kage.json +0ms
electron-packager Application name: gp +31ms
electron-packager Target Electron version: 1.6.11 +0ms
electron-packager Ignored path regular expressions: [ '/node_modules/electron(
$|/)',
'/node_modules/electron-prebuilt(-compile)?($|/)',
'/node_modules/electron-packager($|/)',
'/\\.git($|/)',
'/node_modules/\\.bin($|/)',
'\\.o(bj)?$' ] +0ms
electron-packager Downloading Electron with options {"strictSSL":true,"platfor
m":"win32","arch":"ia32","version":"1.6.11"} +0ms
Packaging app for platform win32 ia32 using electron v1.6.11
electron-packager Creating C:\Users\Taha\AppData\Local\Temp\electron-packager\
win32-ia32-template +2s
electron-packager Extracting C:\Users\Taha\AppData\Local\electron\Cache\electr
on-v1.6.11-win32-ia32.zip to C:\Users\Taha\AppData\Local\Temp\electron-packager\
win32-ia32-template +16ms
electron-packager Initializing app in C:\Users\Taha\AppData\Local\Temp\electro
n-packager\win32-ia32\gp-win32-ia32 from C:\Users\Taha\AppData\Local\Temp\electr
on-packager\win32-ia32-template template +3s
electron-packager Ignored paths based on the out param: [ 'D:\\GP\\gp-darwin-x
64',
'D:\\GP\\gp-linux-ia32',
'D:\\GP\\gp-linux-x64',
'D:\\GP\\gp-linux-armv7l',
'D:\\GP\\gp-linux-arm64',
'D:\\GP\\gp-mas-x64',
'D:\\GP\\gp-win32-ia32',
'D:\\GP\\gp-win32-x64' ] +3s
electron-packager Pruning modules via: npm prune --production +0ms
electron-packager Renaming electron.exe to gp.exe in C:\Users\Taha\AppData\Loc
al\Temp\electron-packager\win32-ia32\gp-win32-ia32 +31s
electron-packager Running rcedit with the options {"version-string":{"FileDesc
ription":"gp","InternalName":"gp","OriginalFilename":"gp.exe","ProductName":"gp"
},"file-version":"1.0.0","product-version":"1.0.0"} +0ms
electron-packager Moving C:\Users\Taha\AppData\Local\Temp\electron-packager\wi
n32-ia32\gp-win32-ia32 to D:\GP\gp-win32-ia32 +203ms
Wrote new app to D:\GP\gp-win32-ia32```
| 1.0 | Electron win32 ia32 app is not working but x64 is - <!--
Thanks for filing an issue!
Please check off all of the steps as they are completed by replacing [ ] with [x].
-->
* [x] I have read the [contribution documentation](https://github.com/electron-userland/electron-packager/blob/master/CONTRIBUTING.md) for this project.
* [x] I agree to follow the [code of conduct](https://github.com/electron/electron/blob/master/CODE_OF_CONDUCT.md) that this project follows, as appropriate.
* [x] I have searched the issue tracker for an issue that matches the one I want to file, without success.
Hi,
I am using Windows 7 64bits and have used electron packager to build my project to both win32 ia32 and win32 x64
The x64 version is working perfectly on windows 64 bit machines but the ia32 version is not working on neither 32 bit or 64 bit machines. I click the 32bit executable and absolutely NOTHING happens.
This is very frusturating because I haven't found a single person who's had this issue before.
Please help!
Thank you.
**Console output when you run electron-packager with the environment variable `DEBUG=electron-packager`. Please include the stack trace if one exists.**
```
D:\GP>electron-packager . --arch=ia32
electron-packager Electron Packager 9.0.0 +0ms
electron-packager Node v6.11.2 +15ms
electron-packager Host Operating system: win32 (x64) +0ms
electron-packager Packager Options: {"":["."],"all":false,"derefSymlinks":true
,"download":{"strictSSL":true},"overwrite":false,"prune":true,"quiet":false,"arc
h":"ia32","DEBUG":"electron-packager","dir":".","protocols":[]} +0ms
electron-packager Target Platforms: win32 +0ms
electron-packager Target Architectures: ia32 +0ms
electron-packager Inferring application name from name in D:\GP\package.json +
0ms
electron-packager Inferring appVersion from version in D:\GP\package.json +0ms
electron-packager Inferring target Electron version from electron in D:\GP\pac
kage.json +16ms
electron-packager Application name: gp +32ms
electron-packager Target Electron version: 1.6.11 +0ms
electron-packager Ignored path regular expressions: [ '/node_modules/electron(
$|/)',
'/node_modules/electron-prebuilt(-compile)?($|/)',
'/node_modules/electron-packager($|/)',
'/\\.git($|/)',
'/node_modules/\\.bin($|/)',
'\\.o(bj)?$' ] +0ms
electron-packager Downloading Electron with options {"strictSSL":true,"platfor
m":"win32","arch":"ia32","version":"1.6.11"} +0ms
Skipping win32 ia32 (output dir already exists, use --overwrite to force)
D:\GP>electron-packager . --arch=ia32 --overwrite --DEBUG=electron-packager
electron-packager Electron Packager 9.0.0 +0ms
electron-packager Node v6.11.2 +0ms
electron-packager Host Operating system: win32 (x64) +0ms
electron-packager Packager Options: {"":["."],"all":false,"derefSymlinks":true
,"download":{"strictSSL":true},"overwrite":true,"prune":true,"quiet":false,"arch
":"ia32","DEBUG":"electron-packager","dir":".","protocols":[]} +0ms
electron-packager Target Platforms: win32 +0ms
electron-packager Target Architectures: ia32 +0ms
electron-packager Inferring application name from name in D:\GP\package.json +
0ms
electron-packager Inferring appVersion from version in D:\GP\package.json +16m
s
electron-packager Inferring target Electron version from electron in D:\GP\pac
kage.json +0ms
electron-packager Application name: gp +31ms
electron-packager Target Electron version: 1.6.11 +0ms
electron-packager Ignored path regular expressions: [ '/node_modules/electron(
$|/)',
'/node_modules/electron-prebuilt(-compile)?($|/)',
'/node_modules/electron-packager($|/)',
'/\\.git($|/)',
'/node_modules/\\.bin($|/)',
'\\.o(bj)?$' ] +0ms
electron-packager Downloading Electron with options {"strictSSL":true,"platfor
m":"win32","arch":"ia32","version":"1.6.11"} +0ms
Packaging app for platform win32 ia32 using electron v1.6.11
electron-packager Creating C:\Users\Taha\AppData\Local\Temp\electron-packager\
win32-ia32-template +2s
electron-packager Extracting C:\Users\Taha\AppData\Local\electron\Cache\electr
on-v1.6.11-win32-ia32.zip to C:\Users\Taha\AppData\Local\Temp\electron-packager\
win32-ia32-template +16ms
electron-packager Initializing app in C:\Users\Taha\AppData\Local\Temp\electro
n-packager\win32-ia32\gp-win32-ia32 from C:\Users\Taha\AppData\Local\Temp\electr
on-packager\win32-ia32-template template +3s
electron-packager Ignored paths based on the out param: [ 'D:\\GP\\gp-darwin-x
64',
'D:\\GP\\gp-linux-ia32',
'D:\\GP\\gp-linux-x64',
'D:\\GP\\gp-linux-armv7l',
'D:\\GP\\gp-linux-arm64',
'D:\\GP\\gp-mas-x64',
'D:\\GP\\gp-win32-ia32',
'D:\\GP\\gp-win32-x64' ] +3s
electron-packager Pruning modules via: npm prune --production +0ms
electron-packager Renaming electron.exe to gp.exe in C:\Users\Taha\AppData\Loc
al\Temp\electron-packager\win32-ia32\gp-win32-ia32 +31s
electron-packager Running rcedit with the options {"version-string":{"FileDesc
ription":"gp","InternalName":"gp","OriginalFilename":"gp.exe","ProductName":"gp"
},"file-version":"1.0.0","product-version":"1.0.0"} +0ms
electron-packager Moving C:\Users\Taha\AppData\Local\Temp\electron-packager\wi
n32-ia32\gp-win32-ia32 to D:\GP\gp-win32-ia32 +203ms
Wrote new app to D:\GP\gp-win32-ia32```
| non_priority | electron app is not working but is thanks for filing an issue please check off all of the steps as they are completed by replacing with i have read the for this project i agree to follow the that this project follows as appropriate i have searched the issue tracker for an issue that matches the one i want to file without success hi i am using windows and have used electron packager to build my project to both and the version is working perfectly on windows bit machines but the version is not working on neither bit or bit machines i click the executable and absolutely nothing happens this is very frusturating because i haven t found a single person who s had this issue before please help thank you console output when you run electron packager with the environment variable debug electron packager please include the stack trace if one exists d gp electron packager arch electron packager electron packager electron packager node electron packager host operating system electron packager packager options all false derefsymlinks true download strictssl true overwrite false prune true quiet false arc h debug electron packager dir protocols electron packager target platforms electron packager target architectures electron packager inferring application name from name in d gp package json electron packager inferring appversion from version in d gp package json electron packager inferring target electron version from electron in d gp pac kage json electron packager application name gp electron packager target electron version electron packager ignored path regular expressions node modules electron node modules electron prebuilt compile node modules electron packager git node modules bin o bj electron packager downloading electron with options strictssl true platfor m arch version skipping output dir already exists use overwrite to force d gp electron packager arch overwrite debug electron packager electron packager electron packager electron packager node electron packager host operating system electron packager packager options all false derefsymlinks true download strictssl true overwrite true prune true quiet false arch debug electron packager dir protocols electron packager target platforms electron packager target architectures electron packager inferring application name from name in d gp package json electron packager inferring appversion from version in d gp package json s electron packager inferring target electron version from electron in d gp pac kage json electron packager application name gp electron packager target electron version electron packager ignored path regular expressions node modules electron node modules electron prebuilt compile node modules electron packager git node modules bin o bj electron packager downloading electron with options strictssl true platfor m arch version packaging app for platform using electron electron packager creating c users taha appdata local temp electron packager template electron packager extracting c users taha appdata local electron cache electr on zip to c users taha appdata local temp electron packager template electron packager initializing app in c users taha appdata local temp electro n packager gp from c users taha appdata local temp electr on packager template template electron packager ignored paths based on the out param d gp gp darwin x d gp gp linux d gp gp linux d gp gp linux d gp gp linux d gp gp mas d gp gp d gp gp electron packager pruning modules via npm prune production electron packager renaming electron exe to gp exe in c users taha appdata loc al temp electron packager gp electron packager running rcedit with the options version string filedesc ription gp internalname gp originalfilename gp exe productname gp file version product version electron packager moving c users taha appdata local temp electron packager wi gp to d gp gp wrote new app to d gp gp | 0 |
48,520 | 5,962,121,684 | IssuesEvent | 2017-05-29 20:37:35 | pubkey/rxdb | https://api.github.com/repos/pubkey/rxdb | closed | RxQuery.regex() will not produce the right toString()-representation | has test case | When `.regex()` is used in a query and toString is called, the regex-string is not in the resulting string.
This creates broken behaviour on the _queryCache, because it will return the wrong query.
Reproduce: [https://jsfiddle.net/h8n0awfc/1/](https://jsfiddle.net/h8n0awfc/1/) | 1.0 | RxQuery.regex() will not produce the right toString()-representation - When `.regex()` is used in a query and toString is called, the regex-string is not in the resulting string.
This creates broken behaviour on the _queryCache, because it will return the wrong query.
Reproduce: [https://jsfiddle.net/h8n0awfc/1/](https://jsfiddle.net/h8n0awfc/1/) | non_priority | rxquery regex will not produce the right tostring representation when regex is used in a query and tostring is called the regex string is not in the resulting string this creates broken behaviour on the querycache because it will return the wrong query reproduce | 0 |
262,756 | 27,989,244,892 | IssuesEvent | 2023-03-27 01:13:39 | DavidSpek/pipelines | https://api.github.com/repos/DavidSpek/pipelines | opened | CVE-2023-25666 (High) detected in tensorflow-1.15.0-cp27-cp27mu-manylinux2010_x86_64.whl | Mend: dependency security vulnerability | ## CVE-2023-25666 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>tensorflow-1.15.0-cp27-cp27mu-manylinux2010_x86_64.whl</b></p></summary>
<p>TensorFlow is an open source machine learning framework for everyone.</p>
<p>Library home page: <a href="https://files.pythonhosted.org/packages/ec/98/f968caf5f65759e78873b900cbf0ae20b1699fb11268ecc0f892186419a7/tensorflow-1.15.0-cp27-cp27mu-manylinux2010_x86_64.whl">https://files.pythonhosted.org/packages/ec/98/f968caf5f65759e78873b900cbf0ae20b1699fb11268ecc0f892186419a7/tensorflow-1.15.0-cp27-cp27mu-manylinux2010_x86_64.whl</a></p>
<p>Path to dependency file: /contrib/components/openvino/ovms-deployer/containers/requirements.txt</p>
<p>Path to vulnerable library: /contrib/components/openvino/ovms-deployer/containers/requirements.txt,/samples/core/ai_platform/training</p>
<p>
Dependency Hierarchy:
- :x: **tensorflow-1.15.0-cp27-cp27mu-manylinux2010_x86_64.whl** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/DavidSpek/pipelines/commit/6f7433f006e282c4f25441e7502b80d73751e38f">6f7433f006e282c4f25441e7502b80d73751e38f</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>
TensorFlow is an open source platform for machine learning. Prior to versions 2.12.0 and 2.11.1, there is a floating point exception in AudioSpectrogram. A fix is included in TensorFlow version 2.12.0 and version 2.11.1.
<p>Publish Date: 2023-03-24
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2023-25666>CVE-2023-25666</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/tensorflow/tensorflow/security/advisories/GHSA-f637-vh3r-vfh2">https://github.com/tensorflow/tensorflow/security/advisories/GHSA-f637-vh3r-vfh2</a></p>
<p>Release Date: 2023-03-24</p>
<p>Fix Resolution: tensorflow - 2.11.1,2.12.0, tensorflow-cpu - 2.11.1,2.12.0, tensorflow-gpu - 2.11.1,2.12.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-2023-25666 (High) detected in tensorflow-1.15.0-cp27-cp27mu-manylinux2010_x86_64.whl - ## CVE-2023-25666 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>tensorflow-1.15.0-cp27-cp27mu-manylinux2010_x86_64.whl</b></p></summary>
<p>TensorFlow is an open source machine learning framework for everyone.</p>
<p>Library home page: <a href="https://files.pythonhosted.org/packages/ec/98/f968caf5f65759e78873b900cbf0ae20b1699fb11268ecc0f892186419a7/tensorflow-1.15.0-cp27-cp27mu-manylinux2010_x86_64.whl">https://files.pythonhosted.org/packages/ec/98/f968caf5f65759e78873b900cbf0ae20b1699fb11268ecc0f892186419a7/tensorflow-1.15.0-cp27-cp27mu-manylinux2010_x86_64.whl</a></p>
<p>Path to dependency file: /contrib/components/openvino/ovms-deployer/containers/requirements.txt</p>
<p>Path to vulnerable library: /contrib/components/openvino/ovms-deployer/containers/requirements.txt,/samples/core/ai_platform/training</p>
<p>
Dependency Hierarchy:
- :x: **tensorflow-1.15.0-cp27-cp27mu-manylinux2010_x86_64.whl** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/DavidSpek/pipelines/commit/6f7433f006e282c4f25441e7502b80d73751e38f">6f7433f006e282c4f25441e7502b80d73751e38f</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>
TensorFlow is an open source platform for machine learning. Prior to versions 2.12.0 and 2.11.1, there is a floating point exception in AudioSpectrogram. A fix is included in TensorFlow version 2.12.0 and version 2.11.1.
<p>Publish Date: 2023-03-24
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2023-25666>CVE-2023-25666</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/tensorflow/tensorflow/security/advisories/GHSA-f637-vh3r-vfh2">https://github.com/tensorflow/tensorflow/security/advisories/GHSA-f637-vh3r-vfh2</a></p>
<p>Release Date: 2023-03-24</p>
<p>Fix Resolution: tensorflow - 2.11.1,2.12.0, tensorflow-cpu - 2.11.1,2.12.0, tensorflow-gpu - 2.11.1,2.12.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 tensorflow whl cve high severity vulnerability vulnerable library tensorflow whl tensorflow is an open source machine learning framework for everyone library home page a href path to dependency file contrib components openvino ovms deployer containers requirements txt path to vulnerable library contrib components openvino ovms deployer containers requirements txt samples core ai platform training dependency hierarchy x tensorflow whl vulnerable library found in head commit a href found in base branch master vulnerability details tensorflow is an open source platform for machine learning prior to versions and there is a floating point exception in audiospectrogram a fix is included in tensorflow version and 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 none integrity impact none availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution tensorflow tensorflow cpu tensorflow gpu step up your open source security game with mend | 0 |
357,403 | 10,606,112,493 | IssuesEvent | 2019-10-10 22:12:26 | kubernetes/website | https://api.github.com/repos/kubernetes/website | closed | Localising Stateless applications sub-section to Hindi | kind/feature language/hi lifecycle/rotten priority/backlog | **What would you like to be added**
Markdown to be translated:-
- https://github.com/kubernetes/website/edit/master/content/en/docs/tutorials/stateless-application/expose-external-ip-address.md
- https://github.com/kubernetes/website/edit/master/content/en/docs/tutorials/stateless-application/guestbook.md
| 1.0 | Localising Stateless applications sub-section to Hindi - **What would you like to be added**
Markdown to be translated:-
- https://github.com/kubernetes/website/edit/master/content/en/docs/tutorials/stateless-application/expose-external-ip-address.md
- https://github.com/kubernetes/website/edit/master/content/en/docs/tutorials/stateless-application/guestbook.md
| priority | localising stateless applications sub section to hindi what would you like to be added markdown to be translated | 1 |
655,671 | 21,704,517,168 | IssuesEvent | 2022-05-10 08:25:24 | bounswe/bounswe2022group2 | https://api.github.com/repos/bounswe/bounswe2022group2 | closed | Practice App: Implement the Signup Endpoint | priority-medium status-needreview practice-app practice-app:back-end | ### Issue Description
We determined the endpoints to be included in the practice app project in our [weekly meeting-9](https://github.com/bounswe/bounswe2022group2/wiki/Meeting-%239-(01.05.2022)).
After the determination of the complete list, we divided the tasks within the team. I took the responsibility for the signup endpoint. To be able to implement the signup endpoint, we need the user model that will be created with issue #151. After the creation of the user model, I will implement the signup endpoint.
### Step Details
Steps that will be performed:
- [x] Check whether the incoming data is valid
- [x] Check whether the user is already exists
- [x] Hash the password
- [x] Create and save the user
- [x] Return the created user with a success message
- [x] Return an error message if an error occurs in any of the previous steps
- [x] Test the endpoint with Postman
- [x] Save requests as a collection in Postman
- [x] Document the endpoint
### Final Actions
After I created the signup endpoint, I will test it by using Postman. While testing, I will save my successful and failed requests and I will create a collection in Postman. I will also give the link to the collection under this as a comment to enable anyone to test the endpoint. Finally, I will document the endpoint and will share the documentation as a comment under this issue to add it to the corresponding wiki page in the future.
### Deadline of the Issue
08.05.2022 - Sunday - 23:59
### Reviewer
Onur Kömürcü
### Deadline for the Review
09.05.2022 - Monday - 23:59 | 1.0 | Practice App: Implement the Signup Endpoint - ### Issue Description
We determined the endpoints to be included in the practice app project in our [weekly meeting-9](https://github.com/bounswe/bounswe2022group2/wiki/Meeting-%239-(01.05.2022)).
After the determination of the complete list, we divided the tasks within the team. I took the responsibility for the signup endpoint. To be able to implement the signup endpoint, we need the user model that will be created with issue #151. After the creation of the user model, I will implement the signup endpoint.
### Step Details
Steps that will be performed:
- [x] Check whether the incoming data is valid
- [x] Check whether the user is already exists
- [x] Hash the password
- [x] Create and save the user
- [x] Return the created user with a success message
- [x] Return an error message if an error occurs in any of the previous steps
- [x] Test the endpoint with Postman
- [x] Save requests as a collection in Postman
- [x] Document the endpoint
### Final Actions
After I created the signup endpoint, I will test it by using Postman. While testing, I will save my successful and failed requests and I will create a collection in Postman. I will also give the link to the collection under this as a comment to enable anyone to test the endpoint. Finally, I will document the endpoint and will share the documentation as a comment under this issue to add it to the corresponding wiki page in the future.
### Deadline of the Issue
08.05.2022 - Sunday - 23:59
### Reviewer
Onur Kömürcü
### Deadline for the Review
09.05.2022 - Monday - 23:59 | priority | practice app implement the signup endpoint issue description we determined the endpoints to be included in the practice app project in our after the determination of the complete list we divided the tasks within the team i took the responsibility for the signup endpoint to be able to implement the signup endpoint we need the user model that will be created with issue after the creation of the user model i will implement the signup endpoint step details steps that will be performed check whether the incoming data is valid check whether the user is already exists hash the password create and save the user return the created user with a success message return an error message if an error occurs in any of the previous steps test the endpoint with postman save requests as a collection in postman document the endpoint final actions after i created the signup endpoint i will test it by using postman while testing i will save my successful and failed requests and i will create a collection in postman i will also give the link to the collection under this as a comment to enable anyone to test the endpoint finally i will document the endpoint and will share the documentation as a comment under this issue to add it to the corresponding wiki page in the future deadline of the issue sunday reviewer onur kömürcü deadline for the review monday | 1 |
64,190 | 14,657,467,770 | IssuesEvent | 2020-12-28 15:39:45 | fu1771695yongxie/yarn | https://api.github.com/repos/fu1771695yongxie/yarn | opened | CVE-2020-11022 (Medium) detected in multiple libraries | security vulnerability | ## CVE-2020-11022 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>jquery-1.7.2.min.js</b>, <b>jquery-1.7.1.min.js</b>, <b>jquery-1.8.1.js</b>, <b>jquery-1.8.1.min.js</b></p></summary>
<p>
<details><summary><b>jquery-1.7.2.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.7.2/jquery.min.js">https://cdnjs.cloudflare.com/ajax/libs/jquery/1.7.2/jquery.min.js</a></p>
<p>Path to dependency file: yarn/__tests__/fixtures/install/install-bin-links-eslint/node_modules/js-base64/test/index.html</p>
<p>Path to vulnerable library: yarn/__tests__/fixtures/install/install-bin-links-eslint/node_modules/js-base64/test/index.html,yarn/__tests__/fixtures/install/prod-should-keep-subdeps/node_modules/js-base64/test/index.html</p>
<p>
Dependency Hierarchy:
- :x: **jquery-1.7.2.min.js** (Vulnerable Library)
</details>
<details><summary><b>jquery-1.7.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.7.1/jquery.min.js">https://cdnjs.cloudflare.com/ajax/libs/jquery/1.7.1/jquery.min.js</a></p>
<p>Path to dependency file: yarn/__tests__/fixtures/install/install-bin-links-eslint/node_modules/sockjs/examples/express/index.html</p>
<p>Path to vulnerable library: yarn/__tests__/fixtures/install/install-bin-links-eslint/node_modules/sockjs/examples/express/index.html,yarn/node_modules/vm-browserify/example/run/index.html,yarn/__tests__/fixtures/install/install-bin-links-eslint/node_modules/sockjs/examples/multiplex/index.html,yarn/__tests__/fixtures/install/lockfile-optimization/node_modules/vm-browserify/example/run/index.html,yarn/__tests__/fixtures/outdated/wanted-newer-than-current/node_modules/vm-browserify/example/run/index.html,yarn/__tests__/fixtures/install/install-bin-links-eslint/node_modules/sockjs/examples/hapi/html/index.html,yarn/__tests__/fixtures/install/install-bin-links-eslint/node_modules/vm-browserify/example/run/index.html,yarn/__tests__/fixtures/install/install-bin-links-eslint/node_modules/sockjs/examples/express-3.x/index.html,yarn/__tests__/fixtures/install/install-bin-links-eslint/node_modules/sockjs/examples/echo/index.html</p>
<p>
Dependency Hierarchy:
- :x: **jquery-1.7.1.min.js** (Vulnerable Library)
</details>
<details><summary><b>jquery-1.8.1.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.js">https://cdnjs.cloudflare.com/ajax/libs/jquery/1.8.1/jquery.js</a></p>
<p>Path to vulnerable library: yarn/__tests__/fixtures/install/install-bin-links-eslint/node_modules/webpack-dev-server/client/web_modules/jquery/jquery-1.8.1.js</p>
<p>
Dependency Hierarchy:
- :x: **jquery-1.8.1.js** (Vulnerable Library)
</details>
<details><summary><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: yarn/__tests__/fixtures/install/install-bin-links-eslint/node_modules/redeyed/examples/browser/index.html</p>
<p>Path to vulnerable library: yarn/__tests__/fixtures/install/install-bin-links-eslint/node_modules/redeyed/examples/browser/index.html,yarn/__tests__/fixtures/add/no-mirror-remote-when-duplicates/node_modules/redeyed/examples/browser/index.html</p>
<p>
Dependency Hierarchy:
- :x: **jquery-1.8.1.min.js** (Vulnerable Library)
</details>
<p>Found in HEAD commit: <a href="https://github.com/fu1771695yongxie/yarn/commit/b0308a6bc0041ba9a7c0fefc30be7721760dfd37">b0308a6bc0041ba9a7c0fefc30be7721760dfd37</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
In jQuery versions greater than or equal to 1.2 and before 3.5.0, passing HTML from untrusted sources - even after sanitizing it - to one of jQuery's DOM manipulation methods (i.e. .html(), .append(), and others) may execute untrusted code. This problem is patched in jQuery 3.5.0.
<p>Publish Date: 2020-04-29
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-11022>CVE-2020-11022</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://blog.jquery.com/2020/04/10/jquery-3-5-0-released/">https://blog.jquery.com/2020/04/10/jquery-3-5-0-released/</a></p>
<p>Release Date: 2020-04-29</p>
<p>Fix Resolution: jQuery - 3.5.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-2020-11022 (Medium) detected in multiple libraries - ## CVE-2020-11022 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>jquery-1.7.2.min.js</b>, <b>jquery-1.7.1.min.js</b>, <b>jquery-1.8.1.js</b>, <b>jquery-1.8.1.min.js</b></p></summary>
<p>
<details><summary><b>jquery-1.7.2.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.7.2/jquery.min.js">https://cdnjs.cloudflare.com/ajax/libs/jquery/1.7.2/jquery.min.js</a></p>
<p>Path to dependency file: yarn/__tests__/fixtures/install/install-bin-links-eslint/node_modules/js-base64/test/index.html</p>
<p>Path to vulnerable library: yarn/__tests__/fixtures/install/install-bin-links-eslint/node_modules/js-base64/test/index.html,yarn/__tests__/fixtures/install/prod-should-keep-subdeps/node_modules/js-base64/test/index.html</p>
<p>
Dependency Hierarchy:
- :x: **jquery-1.7.2.min.js** (Vulnerable Library)
</details>
<details><summary><b>jquery-1.7.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.7.1/jquery.min.js">https://cdnjs.cloudflare.com/ajax/libs/jquery/1.7.1/jquery.min.js</a></p>
<p>Path to dependency file: yarn/__tests__/fixtures/install/install-bin-links-eslint/node_modules/sockjs/examples/express/index.html</p>
<p>Path to vulnerable library: yarn/__tests__/fixtures/install/install-bin-links-eslint/node_modules/sockjs/examples/express/index.html,yarn/node_modules/vm-browserify/example/run/index.html,yarn/__tests__/fixtures/install/install-bin-links-eslint/node_modules/sockjs/examples/multiplex/index.html,yarn/__tests__/fixtures/install/lockfile-optimization/node_modules/vm-browserify/example/run/index.html,yarn/__tests__/fixtures/outdated/wanted-newer-than-current/node_modules/vm-browserify/example/run/index.html,yarn/__tests__/fixtures/install/install-bin-links-eslint/node_modules/sockjs/examples/hapi/html/index.html,yarn/__tests__/fixtures/install/install-bin-links-eslint/node_modules/vm-browserify/example/run/index.html,yarn/__tests__/fixtures/install/install-bin-links-eslint/node_modules/sockjs/examples/express-3.x/index.html,yarn/__tests__/fixtures/install/install-bin-links-eslint/node_modules/sockjs/examples/echo/index.html</p>
<p>
Dependency Hierarchy:
- :x: **jquery-1.7.1.min.js** (Vulnerable Library)
</details>
<details><summary><b>jquery-1.8.1.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.js">https://cdnjs.cloudflare.com/ajax/libs/jquery/1.8.1/jquery.js</a></p>
<p>Path to vulnerable library: yarn/__tests__/fixtures/install/install-bin-links-eslint/node_modules/webpack-dev-server/client/web_modules/jquery/jquery-1.8.1.js</p>
<p>
Dependency Hierarchy:
- :x: **jquery-1.8.1.js** (Vulnerable Library)
</details>
<details><summary><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: yarn/__tests__/fixtures/install/install-bin-links-eslint/node_modules/redeyed/examples/browser/index.html</p>
<p>Path to vulnerable library: yarn/__tests__/fixtures/install/install-bin-links-eslint/node_modules/redeyed/examples/browser/index.html,yarn/__tests__/fixtures/add/no-mirror-remote-when-duplicates/node_modules/redeyed/examples/browser/index.html</p>
<p>
Dependency Hierarchy:
- :x: **jquery-1.8.1.min.js** (Vulnerable Library)
</details>
<p>Found in HEAD commit: <a href="https://github.com/fu1771695yongxie/yarn/commit/b0308a6bc0041ba9a7c0fefc30be7721760dfd37">b0308a6bc0041ba9a7c0fefc30be7721760dfd37</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
In jQuery versions greater than or equal to 1.2 and before 3.5.0, passing HTML from untrusted sources - even after sanitizing it - to one of jQuery's DOM manipulation methods (i.e. .html(), .append(), and others) may execute untrusted code. This problem is patched in jQuery 3.5.0.
<p>Publish Date: 2020-04-29
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-11022>CVE-2020-11022</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://blog.jquery.com/2020/04/10/jquery-3-5-0-released/">https://blog.jquery.com/2020/04/10/jquery-3-5-0-released/</a></p>
<p>Release Date: 2020-04-29</p>
<p>Fix Resolution: jQuery - 3.5.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 multiple libraries cve medium severity vulnerability vulnerable libraries jquery min js jquery min js jquery js jquery min js jquery min js javascript library for dom operations library home page a href path to dependency file yarn tests fixtures install install bin links eslint node modules js test index html path to vulnerable library yarn tests fixtures install install bin links eslint node modules js test index html yarn tests fixtures install prod should keep subdeps node modules js test index html dependency hierarchy x jquery min js vulnerable library jquery min js javascript library for dom operations library home page a href path to dependency file yarn tests fixtures install install bin links eslint node modules sockjs examples express index html path to vulnerable library yarn tests fixtures install install bin links eslint node modules sockjs examples express index html yarn node modules vm browserify example run index html yarn tests fixtures install install bin links eslint node modules sockjs examples multiplex index html yarn tests fixtures install lockfile optimization node modules vm browserify example run index html yarn tests fixtures outdated wanted newer than current node modules vm browserify example run index html yarn tests fixtures install install bin links eslint node modules sockjs examples hapi html index html yarn tests fixtures install install bin links eslint node modules vm browserify example run index html yarn tests fixtures install install bin links eslint node modules sockjs examples express x index html yarn tests fixtures install install bin links eslint node modules sockjs examples echo index html dependency hierarchy x jquery min js vulnerable library jquery js javascript library for dom operations library home page a href path to vulnerable library yarn tests fixtures install install bin links eslint node modules webpack dev server client web modules jquery jquery js dependency hierarchy x jquery js vulnerable library jquery min js javascript library for dom operations library home page a href path to dependency file yarn tests fixtures install install bin links eslint node modules redeyed examples browser index html path to vulnerable library yarn tests fixtures install install bin links eslint node modules redeyed examples browser index html yarn tests fixtures add no mirror remote when duplicates 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 in jquery versions greater than or equal to and before passing html from untrusted sources even after sanitizing it to one of jquery s dom manipulation methods i e html append and others may execute untrusted code this problem is patched in jquery 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 |
210,771 | 16,115,720,407 | IssuesEvent | 2021-04-28 07:07:34 | grub-n-go/grub-n-go | https://api.github.com/repos/grub-n-go/grub-n-go | closed | EXISTING TEST PAGES | TestCafe | Please do all work for this task in a branch named issue-22
- [x] Edit existing test pages
**navbar**
**landing**
**signin/signout/signup**
**filter**
**addproject**
- [x] skip tests on
**profile**
**home**
**projects**
**interests**
- [x] System passes test | 1.0 | EXISTING TEST PAGES - Please do all work for this task in a branch named issue-22
- [x] Edit existing test pages
**navbar**
**landing**
**signin/signout/signup**
**filter**
**addproject**
- [x] skip tests on
**profile**
**home**
**projects**
**interests**
- [x] System passes test | non_priority | existing test pages please do all work for this task in a branch named issue edit existing test pages navbar landing signin signout signup filter addproject skip tests on profile home projects interests system passes test | 0 |
476,263 | 13,736,109,546 | IssuesEvent | 2020-10-05 11:13:47 | stylelint/stylelint | https://api.github.com/repos/stylelint/stylelint | closed | Fix file paths that contain the `+` character being ignored | priority: high status: ready to implement type: bug | > Clearly describe the bug
File paths that contain a `+` are either not linted or will fail with an error.
If the glob pattern itself contains a `+` itself it will throw this error even if it's quoted or escaped:
```
Error: No files matching the pattern "src/app/+route" were found.
at globby.then.filePaths (/.../node_modules/stylelint/lib/standalone.js:206:17)
at process._tickCallback (internal/process/next_tick.js:68:7)
error Command failed with exit code 1.
```
If the glob pattern does not contain a `+` but the pattern would match paths that do contain a `+` it will not error, but it also won't lint those files either. It seems to just ignore them.
> Which rule, if any, is the bug related to?
n/a
> What CSS is needed to reproduce the bug?
n/a
> What stylelint configuration is needed to reproduce the bug?
n/a
> Which version of stylelint are you using?
`10.1.0`
> How are you running stylelint: CLI, PostCSS plugin, Node.js API?
- `stylelint src/app/+route/styles.scss`
- `stylelint src/app/+route`
- `stylelint 'src/app/+route/styles.scss'`
- `stylelint src/app/\+route/styles.scss`
> Does the bug relate to non-standard syntax (e.g. SCSS, Less etc.)?
n/a
> What did you expect to happen?
It will lint file paths that contain the `+` symbol it does not throw an error and also lints files that might be in paths that contain a `+`.
> What actually happened (e.g. what warnings or errors did you get)?
Doesn't lint the files or throws an error.
<!--
Before posting, please check that the bug hasn't already been:
1. fixed in the next release (https://github.com/stylelint/stylelint/blob/master/CHANGELOG.md)
2. discussed previously (https://github.com/stylelint/stylelint/search)
-->
<!--
You can help us fix the bug more quickly by:
1. Figuring out what needs to be done and proposing it
2. Submitting a PR with failing tests.
Once the bug has been confirmed, you can help out further by:
1. Writing the code and submitting a PR.
-->
Some initial investigation seems to suggest this might be an issue in `globby`. I tried updating `globby` to the latest version and it no longer threw the errors. However, it also didn't pick up actual linting errors for any files contained with paths that contain `+`. I've tried the same with other linters `TSLint` & `ESLint` and both seem to handle these paths fine. However, they also don't use `globby` either.
| 1.0 | Fix file paths that contain the `+` character being ignored - > Clearly describe the bug
File paths that contain a `+` are either not linted or will fail with an error.
If the glob pattern itself contains a `+` itself it will throw this error even if it's quoted or escaped:
```
Error: No files matching the pattern "src/app/+route" were found.
at globby.then.filePaths (/.../node_modules/stylelint/lib/standalone.js:206:17)
at process._tickCallback (internal/process/next_tick.js:68:7)
error Command failed with exit code 1.
```
If the glob pattern does not contain a `+` but the pattern would match paths that do contain a `+` it will not error, but it also won't lint those files either. It seems to just ignore them.
> Which rule, if any, is the bug related to?
n/a
> What CSS is needed to reproduce the bug?
n/a
> What stylelint configuration is needed to reproduce the bug?
n/a
> Which version of stylelint are you using?
`10.1.0`
> How are you running stylelint: CLI, PostCSS plugin, Node.js API?
- `stylelint src/app/+route/styles.scss`
- `stylelint src/app/+route`
- `stylelint 'src/app/+route/styles.scss'`
- `stylelint src/app/\+route/styles.scss`
> Does the bug relate to non-standard syntax (e.g. SCSS, Less etc.)?
n/a
> What did you expect to happen?
It will lint file paths that contain the `+` symbol it does not throw an error and also lints files that might be in paths that contain a `+`.
> What actually happened (e.g. what warnings or errors did you get)?
Doesn't lint the files or throws an error.
<!--
Before posting, please check that the bug hasn't already been:
1. fixed in the next release (https://github.com/stylelint/stylelint/blob/master/CHANGELOG.md)
2. discussed previously (https://github.com/stylelint/stylelint/search)
-->
<!--
You can help us fix the bug more quickly by:
1. Figuring out what needs to be done and proposing it
2. Submitting a PR with failing tests.
Once the bug has been confirmed, you can help out further by:
1. Writing the code and submitting a PR.
-->
Some initial investigation seems to suggest this might be an issue in `globby`. I tried updating `globby` to the latest version and it no longer threw the errors. However, it also didn't pick up actual linting errors for any files contained with paths that contain `+`. I've tried the same with other linters `TSLint` & `ESLint` and both seem to handle these paths fine. However, they also don't use `globby` either.
| priority | fix file paths that contain the character being ignored clearly describe the bug file paths that contain a are either not linted or will fail with an error if the glob pattern itself contains a itself it will throw this error even if it s quoted or escaped error no files matching the pattern src app route were found at globby then filepaths node modules stylelint lib standalone js at process tickcallback internal process next tick js error command failed with exit code if the glob pattern does not contain a but the pattern would match paths that do contain a it will not error but it also won t lint those files either it seems to just ignore them which rule if any is the bug related to n a what css is needed to reproduce the bug n a what stylelint configuration is needed to reproduce the bug n a which version of stylelint are you using how are you running stylelint cli postcss plugin node js api stylelint src app route styles scss stylelint src app route stylelint src app route styles scss stylelint src app route styles scss does the bug relate to non standard syntax e g scss less etc n a what did you expect to happen it will lint file paths that contain the symbol it does not throw an error and also lints files that might be in paths that contain a what actually happened e g what warnings or errors did you get doesn t lint the files or throws an error before posting please check that the bug hasn t already been fixed in the next release discussed previously you can help us fix the bug more quickly by figuring out what needs to be done and proposing it submitting a pr with failing tests once the bug has been confirmed you can help out further by writing the code and submitting a pr some initial investigation seems to suggest this might be an issue in globby i tried updating globby to the latest version and it no longer threw the errors however it also didn t pick up actual linting errors for any files contained with paths that contain i ve tried the same with other linters tslint eslint and both seem to handle these paths fine however they also don t use globby either | 1 |
66,278 | 16,582,799,005 | IssuesEvent | 2021-05-31 14:05:43 | VROOM-Project/vroom | https://api.github.com/repos/VROOM-Project/vroom | closed | Update CI build image to Ubuntu 20.04 | CI builds enhancement | CI runs currently use Ubuntu bionic images, which means we are checking the build against compiler versions that are (much) older than the ones currently available out of the box in recent dev/production boxes. Switching to Ubuntu focal should enable updating:
- gcc from version 8 to 9;
- clang from version 6 to 10.
The way to do this is somehow related to the outcome of #436 but I'm still filling a dedicated ticket as we'll need it in any case at some point. | 1.0 | Update CI build image to Ubuntu 20.04 - CI runs currently use Ubuntu bionic images, which means we are checking the build against compiler versions that are (much) older than the ones currently available out of the box in recent dev/production boxes. Switching to Ubuntu focal should enable updating:
- gcc from version 8 to 9;
- clang from version 6 to 10.
The way to do this is somehow related to the outcome of #436 but I'm still filling a dedicated ticket as we'll need it in any case at some point. | non_priority | update ci build image to ubuntu ci runs currently use ubuntu bionic images which means we are checking the build against compiler versions that are much older than the ones currently available out of the box in recent dev production boxes switching to ubuntu focal should enable updating gcc from version to clang from version to the way to do this is somehow related to the outcome of but i m still filling a dedicated ticket as we ll need it in any case at some point | 0 |
147,424 | 5,639,410,123 | IssuesEvent | 2017-04-06 14:17:45 | vmware/harbor | https://api.github.com/repos/vmware/harbor | closed | Members action menu is clipped on last row in datagrid | area/clarity-ui priority/p1 UX | the members action menu for a project is clipped and a scroll bar shows up when clicking on the 3 dots.
<img width="1054" alt="screen shot 2017-03-31 at 9 31 09 am" src="https://cloud.githubusercontent.com/assets/626032/24553183/4b56da42-15f7-11e7-871b-da1d0441fe59.png">
| 1.0 | Members action menu is clipped on last row in datagrid - the members action menu for a project is clipped and a scroll bar shows up when clicking on the 3 dots.
<img width="1054" alt="screen shot 2017-03-31 at 9 31 09 am" src="https://cloud.githubusercontent.com/assets/626032/24553183/4b56da42-15f7-11e7-871b-da1d0441fe59.png">
| priority | members action menu is clipped on last row in datagrid the members action menu for a project is clipped and a scroll bar shows up when clicking on the dots img width alt screen shot at am src | 1 |
667,359 | 22,468,112,775 | IssuesEvent | 2022-06-22 05:03:36 | pipalacademy/engage | https://api.github.com/repos/pipalacademy/engage | closed | [Story] Code review for problem submissions | priority: high | As a trainer
- [x] I should be able to see review comments left by me and other trainers
- [ ] I should be able to see which comments are stale
- [ ] ~~I should be able to see the submissions on which my review was requested~~
- [x] I should be able to add comments on problem submissions
- [ ] I should be able to add a rating for correctness and clarity
As a participant
- [x] I should be able to see the comments on my submission
- [x] I should be able to submit again and ask for a re-review | 1.0 | [Story] Code review for problem submissions - As a trainer
- [x] I should be able to see review comments left by me and other trainers
- [ ] I should be able to see which comments are stale
- [ ] ~~I should be able to see the submissions on which my review was requested~~
- [x] I should be able to add comments on problem submissions
- [ ] I should be able to add a rating for correctness and clarity
As a participant
- [x] I should be able to see the comments on my submission
- [x] I should be able to submit again and ask for a re-review | priority | code review for problem submissions as a trainer i should be able to see review comments left by me and other trainers i should be able to see which comments are stale i should be able to see the submissions on which my review was requested i should be able to add comments on problem submissions i should be able to add a rating for correctness and clarity as a participant i should be able to see the comments on my submission i should be able to submit again and ask for a re review | 1 |
9,282 | 6,197,283,341 | IssuesEvent | 2017-07-05 16:27:05 | theodi/octopub | https://api.github.com/repos/theodi/octopub | closed | How to make a Private dataset Public? | f:question fn:Usability i:enhancement | I've been experimenting with Octopub and published a private dataset https://octopub.io/datasets/321/dataset_files
I can't see how to make it public. Has this been implemented? | True | How to make a Private dataset Public? - I've been experimenting with Octopub and published a private dataset https://octopub.io/datasets/321/dataset_files
I can't see how to make it public. Has this been implemented? | non_priority | how to make a private dataset public i ve been experimenting with octopub and published a private dataset i can t see how to make it public has this been implemented | 0 |
172,992 | 21,090,307,054 | IssuesEvent | 2022-04-04 03:43:58 | nautobot/nautobot | https://api.github.com/repos/nautobot/nautobot | closed | API provision tokens for user | type: feature group: security | <!--
NOTE: IF YOUR ISSUE DOES NOT FOLLOW THIS TEMPLATE, IT WILL BE CLOSED.
This form is only for proposing specific new features or enhancements.
If you have a general idea or question, please start a discussion instead:
https://github.com/nautobot/nautobot/discussions
Please describe the environment in which you are running Nautobot.
-->
### Environment
* Python version: n/a
* Nautobot version: n/a
<!--
Describe in detail the new functionality you are proposing. Include any
specific changes to work flows, data models, or the user interface.
-->
### Proposed Functionality
Netbox 3.0 added a feature where you can generate a token using the API if pass along a user/pass - https://github.com/netbox-community/netbox/commit/b038b1f613becb0298d276fa453fe844ba9e6f1e
Nautobot could enhance this feature by allowing the token generation to be more customisable (set the name and the permissions). But just having what Netbox has is a good base I think.
<!--
Convey an example use case for your proposed feature. Write from the
perspective of a Nautobot user who would benefit from the proposed
functionality and describe how.
--->
### Use Case
Would like to be able to generate tokens instead of saving people's passwords somewhere.
<!--
Note any changes to the database schema necessary to support the new
feature. For example, does the proposal require adding a new model or
field? (Not all new features require database changes.)
--->
### Database Changes
None.
<!--
List any new dependencies on external libraries or services that this new
feature would introduce. For example, does the proposal require the
installation of a new Python package? (Not all new features introduce new
dependencies.)
-->
### External Dependencies
None. | True | API provision tokens for user - <!--
NOTE: IF YOUR ISSUE DOES NOT FOLLOW THIS TEMPLATE, IT WILL BE CLOSED.
This form is only for proposing specific new features or enhancements.
If you have a general idea or question, please start a discussion instead:
https://github.com/nautobot/nautobot/discussions
Please describe the environment in which you are running Nautobot.
-->
### Environment
* Python version: n/a
* Nautobot version: n/a
<!--
Describe in detail the new functionality you are proposing. Include any
specific changes to work flows, data models, or the user interface.
-->
### Proposed Functionality
Netbox 3.0 added a feature where you can generate a token using the API if pass along a user/pass - https://github.com/netbox-community/netbox/commit/b038b1f613becb0298d276fa453fe844ba9e6f1e
Nautobot could enhance this feature by allowing the token generation to be more customisable (set the name and the permissions). But just having what Netbox has is a good base I think.
<!--
Convey an example use case for your proposed feature. Write from the
perspective of a Nautobot user who would benefit from the proposed
functionality and describe how.
--->
### Use Case
Would like to be able to generate tokens instead of saving people's passwords somewhere.
<!--
Note any changes to the database schema necessary to support the new
feature. For example, does the proposal require adding a new model or
field? (Not all new features require database changes.)
--->
### Database Changes
None.
<!--
List any new dependencies on external libraries or services that this new
feature would introduce. For example, does the proposal require the
installation of a new Python package? (Not all new features introduce new
dependencies.)
-->
### External Dependencies
None. | non_priority | api provision tokens for user note if your issue does not follow this template it will be closed this form is only for proposing specific new features or enhancements if you have a general idea or question please start a discussion instead please describe the environment in which you are running nautobot environment python version n a nautobot version n a describe in detail the new functionality you are proposing include any specific changes to work flows data models or the user interface proposed functionality netbox added a feature where you can generate a token using the api if pass along a user pass nautobot could enhance this feature by allowing the token generation to be more customisable set the name and the permissions but just having what netbox has is a good base i think convey an example use case for your proposed feature write from the perspective of a nautobot user who would benefit from the proposed functionality and describe how use case would like to be able to generate tokens instead of saving people s passwords somewhere note any changes to the database schema necessary to support the new feature for example does the proposal require adding a new model or field not all new features require database changes database changes none list any new dependencies on external libraries or services that this new feature would introduce for example does the proposal require the installation of a new python package not all new features introduce new dependencies external dependencies none | 0 |
273,394 | 23,750,016,081 | IssuesEvent | 2022-08-31 19:40:06 | Satellite-im/Core-PWA | https://api.github.com/repos/Satellite-im/Core-PWA | closed | AP-1409: Event not being triggered when using the same account on 2 different places | bug ready-to-test-in-dev | STR:
use a account with a pending request on 2 browsers
accept the request on one of the browsers
the other browser still shows the request pending
seems is missing an event to update the request being accepted
[file id="36afa724-b40f-4bbc-bdc1-eef76bdc09bf"] | 1.0 | AP-1409: Event not being triggered when using the same account on 2 different places - STR:
use a account with a pending request on 2 browsers
accept the request on one of the browsers
the other browser still shows the request pending
seems is missing an event to update the request being accepted
[file id="36afa724-b40f-4bbc-bdc1-eef76bdc09bf"] | non_priority | ap event not being triggered when using the same account on different places str use a account with a pending request on browsers accept the request on one of the browsers the other browser still shows the request pending seems is missing an event to update the request being accepted | 0 |
114,164 | 4,614,986,610 | IssuesEvent | 2016-09-25 21:39:24 | radiasoft/sirepo | https://api.github.com/repos/radiasoft/sirepo | closed | uwsgi and/or log output UserAgent | 1st Priority | The uwsgi log doesn't give enough operational information. It should output the UserAgent and possibly the client IP (proxy must forward this). | 1.0 | uwsgi and/or log output UserAgent - The uwsgi log doesn't give enough operational information. It should output the UserAgent and possibly the client IP (proxy must forward this). | priority | uwsgi and or log output useragent the uwsgi log doesn t give enough operational information it should output the useragent and possibly the client ip proxy must forward this | 1 |
131,184 | 18,245,471,265 | IssuesEvent | 2021-10-01 17:46:47 | HTTPArchive/almanac.httparchive.org | https://api.github.com/repos/HTTPArchive/almanac.httparchive.org | closed | Chart UI accessibility | bug design accessibility | Some accessibility-related things I noticed with the colors + text applied
- There are some instances where white text is used on green bars - for example [fonts chapter has a graph](https://almanac.httparchive.org/en/2020/http2#fig-19) where the % is shown as white on the green bar (failing text color contrast) vs [accessibility where it's black](https://almanac.httparchive.org/en/2020/http2#fig-19)
<img width="656" alt="fonts chapter" src="https://user-images.githubusercontent.com/22671477/120258885-dae4aa80-c260-11eb-9f58-f5e3ff1a3d4b.png">
<img width="616" alt="accessibility chapter" src="https://user-images.githubusercontent.com/22671477/120258896-e041f500-c260-11eb-938c-a1e0189c19f9.png">
- Similar issues with white text on red bars - e.g. [media chapter](https://almanac.httparchive.org/en/2020/media#fig-4) (failing text contrast)
<img width="644" alt="media" src="https://user-images.githubusercontent.com/22671477/120259261-9efe1500-c261-11eb-899c-a9e32c9eec7c.png">
- ["heatmap" on the web font page](https://almanac.httparchive.org/en/2020/fonts#fig-2) is using a red-green scale, which isn't a color blind friendly option. [Color brewer has a list of colour-blind friendly palettes](https://colorbrewer2.org/#type=diverging&scheme=RdBu&n=3) we can pick for a diverging scale, including red-blue
<img width="727" alt="font" src="https://user-images.githubusercontent.com/22671477/120259655-601c8f00-c262-11eb-929d-a3c48d5b4a61.png">
- a lot of graphs have colors placed side by side which may not have sufficient contrast between them. If we add white dividers between the slices/bars/etc it should make it easier to see. E.g. [e-commerce chart today](https://almanac.httparchive.org/en/2020/ecommerce#fig-4). [WCAG has some sample techniques](https://www.w3.org/WAI/WCAG21/Understanding/non-text-contrast.html) on their site.
<img width="713" alt="ecommerce" src="https://user-images.githubusercontent.com/22671477/120259915-da4d1380-c262-11eb-9a23-48600981a5cd.png">
- generally wondering how the categorial colors are selected, and if we want to use one of [color brewer's suggested ones](https://colorbrewer2.org/#type=qualitative&scheme=Dark2&n=3)
| 1.0 | Chart UI accessibility - Some accessibility-related things I noticed with the colors + text applied
- There are some instances where white text is used on green bars - for example [fonts chapter has a graph](https://almanac.httparchive.org/en/2020/http2#fig-19) where the % is shown as white on the green bar (failing text color contrast) vs [accessibility where it's black](https://almanac.httparchive.org/en/2020/http2#fig-19)
<img width="656" alt="fonts chapter" src="https://user-images.githubusercontent.com/22671477/120258885-dae4aa80-c260-11eb-9f58-f5e3ff1a3d4b.png">
<img width="616" alt="accessibility chapter" src="https://user-images.githubusercontent.com/22671477/120258896-e041f500-c260-11eb-938c-a1e0189c19f9.png">
- Similar issues with white text on red bars - e.g. [media chapter](https://almanac.httparchive.org/en/2020/media#fig-4) (failing text contrast)
<img width="644" alt="media" src="https://user-images.githubusercontent.com/22671477/120259261-9efe1500-c261-11eb-899c-a9e32c9eec7c.png">
- ["heatmap" on the web font page](https://almanac.httparchive.org/en/2020/fonts#fig-2) is using a red-green scale, which isn't a color blind friendly option. [Color brewer has a list of colour-blind friendly palettes](https://colorbrewer2.org/#type=diverging&scheme=RdBu&n=3) we can pick for a diverging scale, including red-blue
<img width="727" alt="font" src="https://user-images.githubusercontent.com/22671477/120259655-601c8f00-c262-11eb-929d-a3c48d5b4a61.png">
- a lot of graphs have colors placed side by side which may not have sufficient contrast between them. If we add white dividers between the slices/bars/etc it should make it easier to see. E.g. [e-commerce chart today](https://almanac.httparchive.org/en/2020/ecommerce#fig-4). [WCAG has some sample techniques](https://www.w3.org/WAI/WCAG21/Understanding/non-text-contrast.html) on their site.
<img width="713" alt="ecommerce" src="https://user-images.githubusercontent.com/22671477/120259915-da4d1380-c262-11eb-9a23-48600981a5cd.png">
- generally wondering how the categorial colors are selected, and if we want to use one of [color brewer's suggested ones](https://colorbrewer2.org/#type=qualitative&scheme=Dark2&n=3)
| non_priority | chart ui accessibility some accessibility related things i noticed with the colors text applied there are some instances where white text is used on green bars for example where the is shown as white on the green bar failing text color contrast vs img width alt fonts chapter src img width alt accessibility chapter src similar issues with white text on red bars e g failing text contrast img width alt media src is using a red green scale which isn t a color blind friendly option we can pick for a diverging scale including red blue img width alt font src a lot of graphs have colors placed side by side which may not have sufficient contrast between them if we add white dividers between the slices bars etc it should make it easier to see e g on their site img width alt ecommerce src generally wondering how the categorial colors are selected and if we want to use one of | 0 |
523,387 | 15,180,659,382 | IssuesEvent | 2021-02-15 00:46:20 | blchelle/ribbit | https://api.github.com/repos/blchelle/ribbit | closed | Delete 'forgot password' token after a successful reset | Length: Less than 5 hours Priority: Medium Status: In Progress Type: Enhancement | ## Description
When a user successfully resets their password, delete their token from Redis. This isn't really a security vulnerability. It's more related to a better UX. | 1.0 | Delete 'forgot password' token after a successful reset - ## Description
When a user successfully resets their password, delete their token from Redis. This isn't really a security vulnerability. It's more related to a better UX. | priority | delete forgot password token after a successful reset description when a user successfully resets their password delete their token from redis this isn t really a security vulnerability it s more related to a better ux | 1 |
33,355 | 2,764,254,499 | IssuesEvent | 2015-04-29 14:37:15 | dmwm/WMCore | https://api.github.com/repos/dmwm/WMCore | closed | Show the CE and Workernode in WMStats for jobs in failed and in cooloff | Medium Priority New Feature WMAgent WMStats | Hi,
During the O&C week it was requested we need the pilot jobs to pass the CE to the WMAgent job and then this one should do the following:
1. Report the correct CE to dashboard
2. For failed and cooloff jobs it should correctly show in wmstats the workernode where it ran aswell as the CE.
| 1.0 | Show the CE and Workernode in WMStats for jobs in failed and in cooloff - Hi,
During the O&C week it was requested we need the pilot jobs to pass the CE to the WMAgent job and then this one should do the following:
1. Report the correct CE to dashboard
2. For failed and cooloff jobs it should correctly show in wmstats the workernode where it ran aswell as the CE.
| priority | show the ce and workernode in wmstats for jobs in failed and in cooloff hi during the o c week it was requested we need the pilot jobs to pass the ce to the wmagent job and then this one should do the following report the correct ce to dashboard for failed and cooloff jobs it should correctly show in wmstats the workernode where it ran aswell as the ce | 1 |
280,889 | 30,862,887,973 | IssuesEvent | 2023-08-03 05:32:55 | momo-tong/struts2-core-2.5.16 | https://api.github.com/repos/momo-tong/struts2-core-2.5.16 | opened | struts2-core-2.5.16.jar: 10 vulnerabilities (highest severity is: 9.8) | Mend: dependency security vulnerability | <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>struts2-core-2.5.16.jar</b></p></summary>
<p>Apache Struts 2</p>
<p>Library home page: <a href="http://struts.apache.org/">http://struts.apache.org/</a></p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/org/apache/struts/struts2-core/2.5.16/struts2-core-2.5.16.jar</p>
<p>
<p>Found in HEAD commit: <a href="https://github.com/momo-tong/struts2-core-2.5.16/commit/bab45b0cda5bbc717574c5e8f4c5447c2a784540">bab45b0cda5bbc717574c5e8f4c5447c2a784540</a></p></details>
## Vulnerabilities
| CVE | Severity | <img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS | Dependency | Type | Fixed in (struts2-core version) | Remediation Available |
| ------------- | ------------- | ----- | ----- | ----- | ------------- | --- |
| [CVE-2021-31805](https://www.mend.io/vulnerability-database/CVE-2021-31805) | <img src='https://whitesource-resources.whitesourcesoftware.com/critical_vul.png?' width=19 height=20> Critical | 9.8 | struts2-core-2.5.16.jar | Direct | org.apache.struts:struts2-core:2.5.30 | ❌ |
| [CVE-2020-17530](https://www.mend.io/vulnerability-database/CVE-2020-17530) | <img src='https://whitesource-resources.whitesourcesoftware.com/critical_vul.png?' width=19 height=20> Critical | 9.8 | struts2-core-2.5.16.jar | Direct | 2.5.26 | ❌ |
| [CVE-2019-0230](https://www.mend.io/vulnerability-database/CVE-2019-0230) | <img src='https://whitesource-resources.whitesourcesoftware.com/critical_vul.png?' width=19 height=20> Critical | 9.8 | struts2-core-2.5.16.jar | Direct | 2.5.22 | ❌ |
| [CVE-2018-11776](https://www.mend.io/vulnerability-database/CVE-2018-11776) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 8.1 | struts2-core-2.5.16.jar | Direct | 2.5.17 | ❌ |
| [CVE-2023-34396](https://www.mend.io/vulnerability-database/CVE-2023-34396) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 7.5 | struts2-core-2.5.16.jar | Direct | 2.5.31 | ❌ |
| [WS-2014-0034](https://commons.apache.org/proper/commons-fileupload/changes-report.html) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 7.5 | commons-fileupload-1.3.3.jar | Transitive | 2.5.20 | ❌ |
| [CVE-2023-24998](https://www.mend.io/vulnerability-database/CVE-2023-24998) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 7.5 | commons-fileupload-1.3.3.jar | Transitive | 6.1.2 | ❌ |
| [CVE-2019-0233](https://www.mend.io/vulnerability-database/CVE-2019-0233) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 7.5 | struts2-core-2.5.16.jar | Direct | 2.5.22 | ❌ |
| [CVE-2023-34149](https://www.mend.io/vulnerability-database/CVE-2023-34149) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> Medium | 6.5 | struts2-core-2.5.16.jar | Direct | 2.5.31 | ❌ |
| [CVE-2021-29425](https://www.mend.io/vulnerability-database/CVE-2021-29425) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> Medium | 4.8 | commons-io-2.5.jar | Transitive | 6.1.2 | ❌ |
## Details
<details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/critical_vul.png?' width=19 height=20> CVE-2021-31805</summary>
### Vulnerable Library - <b>struts2-core-2.5.16.jar</b></p>
<p>Apache Struts 2</p>
<p>Library home page: <a href="http://struts.apache.org/">http://struts.apache.org/</a></p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/org/apache/struts/struts2-core/2.5.16/struts2-core-2.5.16.jar</p>
<p>
Dependency Hierarchy:
- :x: **struts2-core-2.5.16.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/momo-tong/struts2-core-2.5.16/commit/bab45b0cda5bbc717574c5e8f4c5447c2a784540">bab45b0cda5bbc717574c5e8f4c5447c2a784540</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
The fix issued for CVE-2020-17530 was incomplete. So from Apache Struts 2.0.0 to 2.5.29, still some of the tag’s attributes could perform a double evaluation if a developer applied forced OGNL evaluation by using the %{...} syntax. Using forced OGNL evaluation on untrusted user input can lead to a Remote Code Execution and security degradation.
<p>Publish Date: 2022-04-12
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2021-31805>CVE-2021-31805</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>9.8</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cwiki.apache.org/confluence/display/WW/S2-062">https://cwiki.apache.org/confluence/display/WW/S2-062</a></p>
<p>Release Date: 2022-04-12</p>
<p>Fix Resolution: org.apache.struts:struts2-core:2.5.30</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/critical_vul.png?' width=19 height=20> CVE-2020-17530</summary>
### Vulnerable Library - <b>struts2-core-2.5.16.jar</b></p>
<p>Apache Struts 2</p>
<p>Library home page: <a href="http://struts.apache.org/">http://struts.apache.org/</a></p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/org/apache/struts/struts2-core/2.5.16/struts2-core-2.5.16.jar</p>
<p>
Dependency Hierarchy:
- :x: **struts2-core-2.5.16.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/momo-tong/struts2-core-2.5.16/commit/bab45b0cda5bbc717574c5e8f4c5447c2a784540">bab45b0cda5bbc717574c5e8f4c5447c2a784540</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
Forced OGNL evaluation, when evaluated on raw user input in tag attributes, may lead to remote code execution. Affected software : Apache Struts 2.0.0 - Struts 2.5.25.
<p>Publish Date: 2020-12-11
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2020-17530>CVE-2020-17530</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>9.8</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cwiki.apache.org/confluence/display/WW/S2-061">https://cwiki.apache.org/confluence/display/WW/S2-061</a></p>
<p>Release Date: 2020-12-11</p>
<p>Fix Resolution: 2.5.26</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/critical_vul.png?' width=19 height=20> CVE-2019-0230</summary>
### Vulnerable Library - <b>struts2-core-2.5.16.jar</b></p>
<p>Apache Struts 2</p>
<p>Library home page: <a href="http://struts.apache.org/">http://struts.apache.org/</a></p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/org/apache/struts/struts2-core/2.5.16/struts2-core-2.5.16.jar</p>
<p>
Dependency Hierarchy:
- :x: **struts2-core-2.5.16.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/momo-tong/struts2-core-2.5.16/commit/bab45b0cda5bbc717574c5e8f4c5447c2a784540">bab45b0cda5bbc717574c5e8f4c5447c2a784540</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
Apache Struts 2.0.0 to 2.5.20 forced double OGNL evaluation, when evaluated on raw user input in tag attributes, may lead to remote code execution.
<p>Publish Date: 2020-09-14
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2019-0230>CVE-2019-0230</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>9.8</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cwiki.apache.org/confluence/display/ww/s2-059">https://cwiki.apache.org/confluence/display/ww/s2-059</a></p>
<p>Release Date: 2020-09-14</p>
<p>Fix Resolution: 2.5.22</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/high_vul.png?' width=19 height=20> CVE-2018-11776</summary>
### Vulnerable Library - <b>struts2-core-2.5.16.jar</b></p>
<p>Apache Struts 2</p>
<p>Library home page: <a href="http://struts.apache.org/">http://struts.apache.org/</a></p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/org/apache/struts/struts2-core/2.5.16/struts2-core-2.5.16.jar</p>
<p>
Dependency Hierarchy:
- :x: **struts2-core-2.5.16.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/momo-tong/struts2-core-2.5.16/commit/bab45b0cda5bbc717574c5e8f4c5447c2a784540">bab45b0cda5bbc717574c5e8f4c5447c2a784540</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
Apache Struts versions 2.3 to 2.3.34 and 2.5 to 2.5.16 suffer from possible Remote Code Execution when alwaysSelectFullNamespace is true (either by user or a plugin like Convention Plugin) and then: results are used with no namespace and in same time, its upper package have no or wildcard namespace and similar to results, same possibility when using url tag which doesn't have value and action set and in same time, its upper package have no or wildcard namespace.
<p>Publish Date: 2018-08-22
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2018-11776>CVE-2018-11776</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>8.1</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://nvd.nist.gov/vuln/detail/CVE-2018-11776">https://nvd.nist.gov/vuln/detail/CVE-2018-11776</a></p>
<p>Release Date: 2018-08-22</p>
<p>Fix Resolution: 2.5.17</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/high_vul.png?' width=19 height=20> CVE-2023-34396</summary>
### Vulnerable Library - <b>struts2-core-2.5.16.jar</b></p>
<p>Apache Struts 2</p>
<p>Library home page: <a href="http://struts.apache.org/">http://struts.apache.org/</a></p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/org/apache/struts/struts2-core/2.5.16/struts2-core-2.5.16.jar</p>
<p>
Dependency Hierarchy:
- :x: **struts2-core-2.5.16.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/momo-tong/struts2-core-2.5.16/commit/bab45b0cda5bbc717574c5e8f4c5447c2a784540">bab45b0cda5bbc717574c5e8f4c5447c2a784540</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
Allocation of Resources Without Limits or Throttling vulnerability in Apache Software Foundation Apache Struts.This issue affects Apache Struts: through 2.5.30, through 6.1.2.
Upgrade to Struts 2.5.31 or 6.1.2.1 or greater
<p>Publish Date: 2023-06-14
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2023-34396>CVE-2023-34396</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://github.com/advisories/GHSA-4g42-gqrg-4633">https://github.com/advisories/GHSA-4g42-gqrg-4633</a></p>
<p>Release Date: 2023-06-14</p>
<p>Fix Resolution: 2.5.31</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/high_vul.png?' width=19 height=20> WS-2014-0034</summary>
### Vulnerable Library - <b>commons-fileupload-1.3.3.jar</b></p>
<p>The Apache Commons FileUpload component provides a simple yet flexible means of adding support for multipart
file upload functionality to servlets and web applications.</p>
<p>Library home page: <a href="http://commons.apache.org/proper/commons-fileupload/">http://commons.apache.org/proper/commons-fileupload/</a></p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/commons-fileupload/commons-fileupload/1.3.3/commons-fileupload-1.3.3.jar</p>
<p>
Dependency Hierarchy:
- struts2-core-2.5.16.jar (Root Library)
- :x: **commons-fileupload-1.3.3.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/momo-tong/struts2-core-2.5.16/commit/bab45b0cda5bbc717574c5e8f4c5447c2a784540">bab45b0cda5bbc717574c5e8f4c5447c2a784540</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
The class FileUploadBase in Apache Commons Fileupload before 1.4 has potential resource leak - InputStream not closed on exception.
<p>Publish Date: 2014-02-17
<p>URL: <a href=https://commons.apache.org/proper/commons-fileupload/changes-report.html>WS-2014-0034</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>7.5</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: None
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Release Date: 2014-02-17</p>
<p>Fix Resolution (commons-fileupload:commons-fileupload): 1.4</p>
<p>Direct dependency fix Resolution (org.apache.struts:struts2-core): 2.5.20</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/high_vul.png?' width=19 height=20> CVE-2023-24998</summary>
### Vulnerable Library - <b>commons-fileupload-1.3.3.jar</b></p>
<p>The Apache Commons FileUpload component provides a simple yet flexible means of adding support for multipart
file upload functionality to servlets and web applications.</p>
<p>Library home page: <a href="http://commons.apache.org/proper/commons-fileupload/">http://commons.apache.org/proper/commons-fileupload/</a></p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/commons-fileupload/commons-fileupload/1.3.3/commons-fileupload-1.3.3.jar</p>
<p>
Dependency Hierarchy:
- struts2-core-2.5.16.jar (Root Library)
- :x: **commons-fileupload-1.3.3.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/momo-tong/struts2-core-2.5.16/commit/bab45b0cda5bbc717574c5e8f4c5447c2a784540">bab45b0cda5bbc717574c5e8f4c5447c2a784540</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
Apache Commons FileUpload before 1.5 does not limit the number of request parts to be processed resulting in the possibility of an attacker triggering a DoS with a malicious upload or series of uploads.
Note that, like all of the file upload limits, the
new configuration option (FileUploadBase#setFileCountMax) is not
enabled by default and must be explicitly configured.
<p>Publish Date: 2023-02-20
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2023-24998>CVE-2023-24998</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://tomcat.apache.org/security-10.html">https://tomcat.apache.org/security-10.html</a></p>
<p>Release Date: 2023-02-20</p>
<p>Fix Resolution (commons-fileupload:commons-fileupload): 1.5</p>
<p>Direct dependency fix Resolution (org.apache.struts:struts2-core): 6.1.2</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/high_vul.png?' width=19 height=20> CVE-2019-0233</summary>
### Vulnerable Library - <b>struts2-core-2.5.16.jar</b></p>
<p>Apache Struts 2</p>
<p>Library home page: <a href="http://struts.apache.org/">http://struts.apache.org/</a></p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/org/apache/struts/struts2-core/2.5.16/struts2-core-2.5.16.jar</p>
<p>
Dependency Hierarchy:
- :x: **struts2-core-2.5.16.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/momo-tong/struts2-core-2.5.16/commit/bab45b0cda5bbc717574c5e8f4c5447c2a784540">bab45b0cda5bbc717574c5e8f4c5447c2a784540</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
An access permission override in Apache Struts 2.0.0 to 2.5.20 may cause a Denial of Service when performing a file upload.
<p>Publish Date: 2020-09-14
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2019-0233>CVE-2019-0233</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://cwiki.apache.org/confluence/display/ww/s2-060">https://cwiki.apache.org/confluence/display/ww/s2-060</a></p>
<p>Release Date: 2020-09-14</p>
<p>Fix Resolution: 2.5.22</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-2023-34149</summary>
### Vulnerable Library - <b>struts2-core-2.5.16.jar</b></p>
<p>Apache Struts 2</p>
<p>Library home page: <a href="http://struts.apache.org/">http://struts.apache.org/</a></p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/org/apache/struts/struts2-core/2.5.16/struts2-core-2.5.16.jar</p>
<p>
Dependency Hierarchy:
- :x: **struts2-core-2.5.16.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/momo-tong/struts2-core-2.5.16/commit/bab45b0cda5bbc717574c5e8f4c5447c2a784540">bab45b0cda5bbc717574c5e8f4c5447c2a784540</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
Allocation of Resources Without Limits or Throttling vulnerability in Apache Software Foundation Apache Struts.This issue affects Apache Struts: through 2.5.30, through 6.1.2.
Upgrade to Struts 2.5.31 or 6.1.2.1 or greater.
<p>Publish Date: 2023-06-14
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2023-34149>CVE-2023-34149</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>6.5</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/advisories/GHSA-8f6x-v685-g2xc">https://github.com/advisories/GHSA-8f6x-v685-g2xc</a></p>
<p>Release Date: 2023-06-14</p>
<p>Fix Resolution: 2.5.31</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-2021-29425</summary>
### Vulnerable Library - <b>commons-io-2.5.jar</b></p>
<p>The Apache Commons IO library contains utility classes, stream implementations, file filters,
file comparators, endian transformation classes, and much more.</p>
<p>Library home page: <a href="http://commons.apache.org/proper/commons-io/">http://commons.apache.org/proper/commons-io/</a></p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/commons-io/commons-io/2.5/commons-io-2.5.jar</p>
<p>
Dependency Hierarchy:
- struts2-core-2.5.16.jar (Root Library)
- commons-fileupload-1.3.3.jar
- :x: **commons-io-2.5.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/momo-tong/struts2-core-2.5.16/commit/bab45b0cda5bbc717574c5e8f4c5447c2a784540">bab45b0cda5bbc717574c5e8f4c5447c2a784540</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
In Apache Commons IO before 2.7, When invoking the method FileNameUtils.normalize with an improper input string, like "//../foo", or "\\..\foo", the result would be the same value, thus possibly providing access to files in the parent directory, but not further above (thus "limited" path traversal), if the calling code would use the result to construct a path value.
<p>Publish Date: 2021-04-13
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2021-29425>CVE-2021-29425</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>4.8</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: 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-2021-29425">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-29425</a></p>
<p>Release Date: 2021-04-13</p>
<p>Fix Resolution (commons-io:commons-io): 2.7</p>
<p>Direct dependency fix Resolution (org.apache.struts:struts2-core): 6.1.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 | struts2-core-2.5.16.jar: 10 vulnerabilities (highest severity is: 9.8) - <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>struts2-core-2.5.16.jar</b></p></summary>
<p>Apache Struts 2</p>
<p>Library home page: <a href="http://struts.apache.org/">http://struts.apache.org/</a></p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/org/apache/struts/struts2-core/2.5.16/struts2-core-2.5.16.jar</p>
<p>
<p>Found in HEAD commit: <a href="https://github.com/momo-tong/struts2-core-2.5.16/commit/bab45b0cda5bbc717574c5e8f4c5447c2a784540">bab45b0cda5bbc717574c5e8f4c5447c2a784540</a></p></details>
## Vulnerabilities
| CVE | Severity | <img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS | Dependency | Type | Fixed in (struts2-core version) | Remediation Available |
| ------------- | ------------- | ----- | ----- | ----- | ------------- | --- |
| [CVE-2021-31805](https://www.mend.io/vulnerability-database/CVE-2021-31805) | <img src='https://whitesource-resources.whitesourcesoftware.com/critical_vul.png?' width=19 height=20> Critical | 9.8 | struts2-core-2.5.16.jar | Direct | org.apache.struts:struts2-core:2.5.30 | ❌ |
| [CVE-2020-17530](https://www.mend.io/vulnerability-database/CVE-2020-17530) | <img src='https://whitesource-resources.whitesourcesoftware.com/critical_vul.png?' width=19 height=20> Critical | 9.8 | struts2-core-2.5.16.jar | Direct | 2.5.26 | ❌ |
| [CVE-2019-0230](https://www.mend.io/vulnerability-database/CVE-2019-0230) | <img src='https://whitesource-resources.whitesourcesoftware.com/critical_vul.png?' width=19 height=20> Critical | 9.8 | struts2-core-2.5.16.jar | Direct | 2.5.22 | ❌ |
| [CVE-2018-11776](https://www.mend.io/vulnerability-database/CVE-2018-11776) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 8.1 | struts2-core-2.5.16.jar | Direct | 2.5.17 | ❌ |
| [CVE-2023-34396](https://www.mend.io/vulnerability-database/CVE-2023-34396) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 7.5 | struts2-core-2.5.16.jar | Direct | 2.5.31 | ❌ |
| [WS-2014-0034](https://commons.apache.org/proper/commons-fileupload/changes-report.html) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 7.5 | commons-fileupload-1.3.3.jar | Transitive | 2.5.20 | ❌ |
| [CVE-2023-24998](https://www.mend.io/vulnerability-database/CVE-2023-24998) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 7.5 | commons-fileupload-1.3.3.jar | Transitive | 6.1.2 | ❌ |
| [CVE-2019-0233](https://www.mend.io/vulnerability-database/CVE-2019-0233) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 7.5 | struts2-core-2.5.16.jar | Direct | 2.5.22 | ❌ |
| [CVE-2023-34149](https://www.mend.io/vulnerability-database/CVE-2023-34149) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> Medium | 6.5 | struts2-core-2.5.16.jar | Direct | 2.5.31 | ❌ |
| [CVE-2021-29425](https://www.mend.io/vulnerability-database/CVE-2021-29425) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> Medium | 4.8 | commons-io-2.5.jar | Transitive | 6.1.2 | ❌ |
## Details
<details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/critical_vul.png?' width=19 height=20> CVE-2021-31805</summary>
### Vulnerable Library - <b>struts2-core-2.5.16.jar</b></p>
<p>Apache Struts 2</p>
<p>Library home page: <a href="http://struts.apache.org/">http://struts.apache.org/</a></p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/org/apache/struts/struts2-core/2.5.16/struts2-core-2.5.16.jar</p>
<p>
Dependency Hierarchy:
- :x: **struts2-core-2.5.16.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/momo-tong/struts2-core-2.5.16/commit/bab45b0cda5bbc717574c5e8f4c5447c2a784540">bab45b0cda5bbc717574c5e8f4c5447c2a784540</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
The fix issued for CVE-2020-17530 was incomplete. So from Apache Struts 2.0.0 to 2.5.29, still some of the tag’s attributes could perform a double evaluation if a developer applied forced OGNL evaluation by using the %{...} syntax. Using forced OGNL evaluation on untrusted user input can lead to a Remote Code Execution and security degradation.
<p>Publish Date: 2022-04-12
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2021-31805>CVE-2021-31805</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>9.8</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cwiki.apache.org/confluence/display/WW/S2-062">https://cwiki.apache.org/confluence/display/WW/S2-062</a></p>
<p>Release Date: 2022-04-12</p>
<p>Fix Resolution: org.apache.struts:struts2-core:2.5.30</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/critical_vul.png?' width=19 height=20> CVE-2020-17530</summary>
### Vulnerable Library - <b>struts2-core-2.5.16.jar</b></p>
<p>Apache Struts 2</p>
<p>Library home page: <a href="http://struts.apache.org/">http://struts.apache.org/</a></p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/org/apache/struts/struts2-core/2.5.16/struts2-core-2.5.16.jar</p>
<p>
Dependency Hierarchy:
- :x: **struts2-core-2.5.16.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/momo-tong/struts2-core-2.5.16/commit/bab45b0cda5bbc717574c5e8f4c5447c2a784540">bab45b0cda5bbc717574c5e8f4c5447c2a784540</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
Forced OGNL evaluation, when evaluated on raw user input in tag attributes, may lead to remote code execution. Affected software : Apache Struts 2.0.0 - Struts 2.5.25.
<p>Publish Date: 2020-12-11
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2020-17530>CVE-2020-17530</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>9.8</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cwiki.apache.org/confluence/display/WW/S2-061">https://cwiki.apache.org/confluence/display/WW/S2-061</a></p>
<p>Release Date: 2020-12-11</p>
<p>Fix Resolution: 2.5.26</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/critical_vul.png?' width=19 height=20> CVE-2019-0230</summary>
### Vulnerable Library - <b>struts2-core-2.5.16.jar</b></p>
<p>Apache Struts 2</p>
<p>Library home page: <a href="http://struts.apache.org/">http://struts.apache.org/</a></p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/org/apache/struts/struts2-core/2.5.16/struts2-core-2.5.16.jar</p>
<p>
Dependency Hierarchy:
- :x: **struts2-core-2.5.16.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/momo-tong/struts2-core-2.5.16/commit/bab45b0cda5bbc717574c5e8f4c5447c2a784540">bab45b0cda5bbc717574c5e8f4c5447c2a784540</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
Apache Struts 2.0.0 to 2.5.20 forced double OGNL evaluation, when evaluated on raw user input in tag attributes, may lead to remote code execution.
<p>Publish Date: 2020-09-14
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2019-0230>CVE-2019-0230</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>9.8</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cwiki.apache.org/confluence/display/ww/s2-059">https://cwiki.apache.org/confluence/display/ww/s2-059</a></p>
<p>Release Date: 2020-09-14</p>
<p>Fix Resolution: 2.5.22</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/high_vul.png?' width=19 height=20> CVE-2018-11776</summary>
### Vulnerable Library - <b>struts2-core-2.5.16.jar</b></p>
<p>Apache Struts 2</p>
<p>Library home page: <a href="http://struts.apache.org/">http://struts.apache.org/</a></p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/org/apache/struts/struts2-core/2.5.16/struts2-core-2.5.16.jar</p>
<p>
Dependency Hierarchy:
- :x: **struts2-core-2.5.16.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/momo-tong/struts2-core-2.5.16/commit/bab45b0cda5bbc717574c5e8f4c5447c2a784540">bab45b0cda5bbc717574c5e8f4c5447c2a784540</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
Apache Struts versions 2.3 to 2.3.34 and 2.5 to 2.5.16 suffer from possible Remote Code Execution when alwaysSelectFullNamespace is true (either by user or a plugin like Convention Plugin) and then: results are used with no namespace and in same time, its upper package have no or wildcard namespace and similar to results, same possibility when using url tag which doesn't have value and action set and in same time, its upper package have no or wildcard namespace.
<p>Publish Date: 2018-08-22
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2018-11776>CVE-2018-11776</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>8.1</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://nvd.nist.gov/vuln/detail/CVE-2018-11776">https://nvd.nist.gov/vuln/detail/CVE-2018-11776</a></p>
<p>Release Date: 2018-08-22</p>
<p>Fix Resolution: 2.5.17</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/high_vul.png?' width=19 height=20> CVE-2023-34396</summary>
### Vulnerable Library - <b>struts2-core-2.5.16.jar</b></p>
<p>Apache Struts 2</p>
<p>Library home page: <a href="http://struts.apache.org/">http://struts.apache.org/</a></p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/org/apache/struts/struts2-core/2.5.16/struts2-core-2.5.16.jar</p>
<p>
Dependency Hierarchy:
- :x: **struts2-core-2.5.16.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/momo-tong/struts2-core-2.5.16/commit/bab45b0cda5bbc717574c5e8f4c5447c2a784540">bab45b0cda5bbc717574c5e8f4c5447c2a784540</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
Allocation of Resources Without Limits or Throttling vulnerability in Apache Software Foundation Apache Struts.This issue affects Apache Struts: through 2.5.30, through 6.1.2.
Upgrade to Struts 2.5.31 or 6.1.2.1 or greater
<p>Publish Date: 2023-06-14
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2023-34396>CVE-2023-34396</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://github.com/advisories/GHSA-4g42-gqrg-4633">https://github.com/advisories/GHSA-4g42-gqrg-4633</a></p>
<p>Release Date: 2023-06-14</p>
<p>Fix Resolution: 2.5.31</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/high_vul.png?' width=19 height=20> WS-2014-0034</summary>
### Vulnerable Library - <b>commons-fileupload-1.3.3.jar</b></p>
<p>The Apache Commons FileUpload component provides a simple yet flexible means of adding support for multipart
file upload functionality to servlets and web applications.</p>
<p>Library home page: <a href="http://commons.apache.org/proper/commons-fileupload/">http://commons.apache.org/proper/commons-fileupload/</a></p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/commons-fileupload/commons-fileupload/1.3.3/commons-fileupload-1.3.3.jar</p>
<p>
Dependency Hierarchy:
- struts2-core-2.5.16.jar (Root Library)
- :x: **commons-fileupload-1.3.3.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/momo-tong/struts2-core-2.5.16/commit/bab45b0cda5bbc717574c5e8f4c5447c2a784540">bab45b0cda5bbc717574c5e8f4c5447c2a784540</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
The class FileUploadBase in Apache Commons Fileupload before 1.4 has potential resource leak - InputStream not closed on exception.
<p>Publish Date: 2014-02-17
<p>URL: <a href=https://commons.apache.org/proper/commons-fileupload/changes-report.html>WS-2014-0034</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>7.5</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: None
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Release Date: 2014-02-17</p>
<p>Fix Resolution (commons-fileupload:commons-fileupload): 1.4</p>
<p>Direct dependency fix Resolution (org.apache.struts:struts2-core): 2.5.20</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/high_vul.png?' width=19 height=20> CVE-2023-24998</summary>
### Vulnerable Library - <b>commons-fileupload-1.3.3.jar</b></p>
<p>The Apache Commons FileUpload component provides a simple yet flexible means of adding support for multipart
file upload functionality to servlets and web applications.</p>
<p>Library home page: <a href="http://commons.apache.org/proper/commons-fileupload/">http://commons.apache.org/proper/commons-fileupload/</a></p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/commons-fileupload/commons-fileupload/1.3.3/commons-fileupload-1.3.3.jar</p>
<p>
Dependency Hierarchy:
- struts2-core-2.5.16.jar (Root Library)
- :x: **commons-fileupload-1.3.3.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/momo-tong/struts2-core-2.5.16/commit/bab45b0cda5bbc717574c5e8f4c5447c2a784540">bab45b0cda5bbc717574c5e8f4c5447c2a784540</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
Apache Commons FileUpload before 1.5 does not limit the number of request parts to be processed resulting in the possibility of an attacker triggering a DoS with a malicious upload or series of uploads.
Note that, like all of the file upload limits, the
new configuration option (FileUploadBase#setFileCountMax) is not
enabled by default and must be explicitly configured.
<p>Publish Date: 2023-02-20
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2023-24998>CVE-2023-24998</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://tomcat.apache.org/security-10.html">https://tomcat.apache.org/security-10.html</a></p>
<p>Release Date: 2023-02-20</p>
<p>Fix Resolution (commons-fileupload:commons-fileupload): 1.5</p>
<p>Direct dependency fix Resolution (org.apache.struts:struts2-core): 6.1.2</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/high_vul.png?' width=19 height=20> CVE-2019-0233</summary>
### Vulnerable Library - <b>struts2-core-2.5.16.jar</b></p>
<p>Apache Struts 2</p>
<p>Library home page: <a href="http://struts.apache.org/">http://struts.apache.org/</a></p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/org/apache/struts/struts2-core/2.5.16/struts2-core-2.5.16.jar</p>
<p>
Dependency Hierarchy:
- :x: **struts2-core-2.5.16.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/momo-tong/struts2-core-2.5.16/commit/bab45b0cda5bbc717574c5e8f4c5447c2a784540">bab45b0cda5bbc717574c5e8f4c5447c2a784540</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
An access permission override in Apache Struts 2.0.0 to 2.5.20 may cause a Denial of Service when performing a file upload.
<p>Publish Date: 2020-09-14
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2019-0233>CVE-2019-0233</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://cwiki.apache.org/confluence/display/ww/s2-060">https://cwiki.apache.org/confluence/display/ww/s2-060</a></p>
<p>Release Date: 2020-09-14</p>
<p>Fix Resolution: 2.5.22</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-2023-34149</summary>
### Vulnerable Library - <b>struts2-core-2.5.16.jar</b></p>
<p>Apache Struts 2</p>
<p>Library home page: <a href="http://struts.apache.org/">http://struts.apache.org/</a></p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/org/apache/struts/struts2-core/2.5.16/struts2-core-2.5.16.jar</p>
<p>
Dependency Hierarchy:
- :x: **struts2-core-2.5.16.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/momo-tong/struts2-core-2.5.16/commit/bab45b0cda5bbc717574c5e8f4c5447c2a784540">bab45b0cda5bbc717574c5e8f4c5447c2a784540</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
Allocation of Resources Without Limits or Throttling vulnerability in Apache Software Foundation Apache Struts.This issue affects Apache Struts: through 2.5.30, through 6.1.2.
Upgrade to Struts 2.5.31 or 6.1.2.1 or greater.
<p>Publish Date: 2023-06-14
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2023-34149>CVE-2023-34149</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>6.5</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/advisories/GHSA-8f6x-v685-g2xc">https://github.com/advisories/GHSA-8f6x-v685-g2xc</a></p>
<p>Release Date: 2023-06-14</p>
<p>Fix Resolution: 2.5.31</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-2021-29425</summary>
### Vulnerable Library - <b>commons-io-2.5.jar</b></p>
<p>The Apache Commons IO library contains utility classes, stream implementations, file filters,
file comparators, endian transformation classes, and much more.</p>
<p>Library home page: <a href="http://commons.apache.org/proper/commons-io/">http://commons.apache.org/proper/commons-io/</a></p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/commons-io/commons-io/2.5/commons-io-2.5.jar</p>
<p>
Dependency Hierarchy:
- struts2-core-2.5.16.jar (Root Library)
- commons-fileupload-1.3.3.jar
- :x: **commons-io-2.5.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/momo-tong/struts2-core-2.5.16/commit/bab45b0cda5bbc717574c5e8f4c5447c2a784540">bab45b0cda5bbc717574c5e8f4c5447c2a784540</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
In Apache Commons IO before 2.7, When invoking the method FileNameUtils.normalize with an improper input string, like "//../foo", or "\\..\foo", the result would be the same value, thus possibly providing access to files in the parent directory, but not further above (thus "limited" path traversal), if the calling code would use the result to construct a path value.
<p>Publish Date: 2021-04-13
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2021-29425>CVE-2021-29425</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>4.8</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: 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-2021-29425">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-29425</a></p>
<p>Release Date: 2021-04-13</p>
<p>Fix Resolution (commons-io:commons-io): 2.7</p>
<p>Direct dependency fix Resolution (org.apache.struts:struts2-core): 6.1.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 | core jar vulnerabilities highest severity is vulnerable library core jar apache struts library home page a href path to dependency file pom xml path to vulnerable library home wss scanner repository org apache struts core core jar found in head commit a href vulnerabilities cve severity cvss dependency type fixed in core version remediation available critical core jar direct org apache struts core critical core jar direct critical core jar direct high core jar direct high core jar direct high commons fileupload jar transitive high commons fileupload jar transitive high core jar direct medium core jar direct medium commons io jar transitive details cve vulnerable library core jar apache struts library home page a href path to dependency file pom xml path to vulnerable library home wss scanner repository org apache struts core core jar dependency hierarchy x core jar vulnerable library found in head commit a href found in base branch master vulnerability details the fix issued for cve was incomplete so from apache struts to still some of the tag’s attributes could perform a double evaluation if a developer applied forced ognl evaluation by using the syntax using forced ognl evaluation on untrusted user input can lead to a remote code execution and security degradation 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 struts core step up your open source security game with mend cve vulnerable library core jar apache struts library home page a href path to dependency file pom xml path to vulnerable library home wss scanner repository org apache struts core core jar dependency hierarchy x core jar vulnerable library found in head commit a href found in base branch master vulnerability details forced ognl evaluation when evaluated on raw user input in tag attributes may lead to remote code execution affected software apache struts struts publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact high integrity impact high availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution step up your open source security game with mend cve vulnerable library core jar apache struts library home page a href path to dependency file pom xml path to vulnerable library home wss scanner repository org apache struts core core jar dependency hierarchy x core jar vulnerable library found in head commit a href found in base branch master vulnerability details apache struts to forced double ognl evaluation when evaluated on raw user input in tag attributes may lead to remote code execution publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact high integrity impact high availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution step up your open source security game with mend cve vulnerable library core jar apache struts library home page a href path to dependency file pom xml path to vulnerable library home wss scanner repository org apache struts core core jar dependency hierarchy x core jar vulnerable library found in head commit a href found in base branch master vulnerability details apache struts versions to and to suffer from possible remote code execution when alwaysselectfullnamespace is true either by user or a plugin like convention plugin and then results are used with no namespace and in same time its upper package have no or wildcard namespace and similar to results same possibility when using url tag which doesn t have value and action set and in same time its upper package have no or wildcard namespace publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity high privileges required none user interaction none scope unchanged impact metrics confidentiality impact high integrity impact high availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution step up your open source security game with mend cve vulnerable library core jar apache struts library home page a href path to dependency file pom xml path to vulnerable library home wss scanner repository org apache struts core core jar dependency hierarchy x core jar vulnerable library found in head commit a href found in base branch master vulnerability details allocation of resources without limits or throttling vulnerability in apache software foundation apache struts this issue affects apache struts through through upgrade to struts or or greater 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 step up your open source security game with mend ws vulnerable library commons fileupload jar the apache commons fileupload component provides a simple yet flexible means of adding support for multipart file upload functionality to servlets and web applications library home page a href path to dependency file pom xml path to vulnerable library home wss scanner repository commons fileupload commons fileupload commons fileupload jar dependency hierarchy core jar root library x commons fileupload jar vulnerable library found in head commit a href found in base branch master vulnerability details the class fileuploadbase in apache commons fileupload before has potential resource leak inputstream not closed on exception publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact high integrity impact none availability impact none for more information on scores click a href suggested fix type upgrade version release date fix resolution commons fileupload commons fileupload direct dependency fix resolution org apache struts core step up your open source security game with mend cve vulnerable library commons fileupload jar the apache commons fileupload component provides a simple yet flexible means of adding support for multipart file upload functionality to servlets and web applications library home page a href path to dependency file pom xml path to vulnerable library home wss scanner repository commons fileupload commons fileupload commons fileupload jar dependency hierarchy core jar root library x commons fileupload jar vulnerable library found in head commit a href found in base branch master vulnerability details apache commons fileupload before does not limit the number of request parts to be processed resulting in the possibility of an attacker triggering a dos with a malicious upload or series of uploads note that like all of the file upload limits the new configuration option fileuploadbase setfilecountmax is not enabled by default and must be explicitly configured 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 commons fileupload commons fileupload direct dependency fix resolution org apache struts core step up your open source security game with mend cve vulnerable library core jar apache struts library home page a href path to dependency file pom xml path to vulnerable library home wss scanner repository org apache struts core core jar dependency hierarchy x core jar vulnerable library found in head commit a href found in base branch master vulnerability details an access permission override in apache struts to may cause a denial of service when performing a file upload 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 step up your open source security game with mend cve vulnerable library core jar apache struts library home page a href path to dependency file pom xml path to vulnerable library home wss scanner repository org apache struts core core jar dependency hierarchy x core jar vulnerable library found in head commit a href found in base branch master vulnerability details allocation of resources without limits or throttling vulnerability in apache software foundation apache struts this issue affects apache struts through through upgrade to struts or or greater publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required low user interaction none scope unchanged impact metrics confidentiality impact none integrity impact none availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution step up your open source security game with mend cve vulnerable library commons io jar the apache commons io library contains utility classes stream implementations file filters file comparators endian transformation classes and much more library home page a href path to dependency file pom xml path to vulnerable library home wss scanner repository commons io commons io commons io jar dependency hierarchy core jar root library commons fileupload jar x commons io jar vulnerable library found in head commit a href found in base branch master vulnerability details in apache commons io before when invoking the method filenameutils normalize with an improper input string like foo or foo the result would be the same value thus possibly providing access to files in the parent directory but not further above thus limited path traversal if the calling code would use the result to construct a path value publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity high privileges required none user interaction none scope unchanged impact metrics confidentiality impact low integrity impact low availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution commons io commons io direct dependency fix resolution org apache struts core step up your open source security game with mend | 0 |
139,324 | 18,850,332,442 | IssuesEvent | 2021-11-11 19:57:54 | snowdensb/sonar-xanitizer | https://api.github.com/repos/snowdensb/sonar-xanitizer | opened | CVE-2019-0227 (High) detected in axis-1.4.jar | security vulnerability | ## CVE-2019-0227 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>axis-1.4.jar</b></p></summary>
<p>An implementation of the SOAP ("Simple Object Access Protocol") submission to W3C.</p>
<p>Library home page: <a href="http://ws.apache.org/axis">http://ws.apache.org/axis</a></p>
<p>Path to vulnerable library: /src/test/resources/webgoat/WEB-INF/lib/axis-1.4.jar</p>
<p>
Dependency Hierarchy:
- :x: **axis-1.4.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/snowdensb/sonar-xanitizer/commit/e2144e84b1fdbf18c01c24e6ab9ade7b45b25283">e2144e84b1fdbf18c01c24e6ab9ade7b45b25283</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
A Server Side Request Forgery (SSRF) vulnerability affected the Apache Axis 1.4 distribution that was last released in 2006. Security and bug commits commits continue in the projects Axis 1.x Subversion repository, legacy users are encouraged to build from source. The successor to Axis 1.x is Axis2, the latest version is 1.7.9 and is not vulnerable to this issue.
<p>Publish Date: 2019-05-01
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-0227>CVE-2019-0227</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: Adjacent
- Attack Complexity: High
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://rhinosecuritylabs.com/application-security/cve-2019-0227-expired-domain-rce-apache-axis/">https://rhinosecuritylabs.com/application-security/cve-2019-0227-expired-domain-rce-apache-axis/</a></p>
<p>Release Date: 2019-05-01</p>
<p>Fix Resolution: org.apache.axis2:axis2:1.7.9</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":"axis","packageName":"axis","packageVersion":"1.4","packageFilePaths":[],"isTransitiveDependency":false,"dependencyTree":"axis:axis:1.4","isMinimumFixVersionAvailable":true,"minimumFixVersion":"org.apache.axis2:axis2:1.7.9"}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2019-0227","vulnerabilityDetails":"A Server Side Request Forgery (SSRF) vulnerability affected the Apache Axis 1.4 distribution that was last released in 2006. Security and bug commits commits continue in the projects Axis 1.x Subversion repository, legacy users are encouraged to build from source. The successor to Axis 1.x is Axis2, the latest version is 1.7.9 and is not vulnerable to this issue.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-0227","cvss3Severity":"high","cvss3Score":"7.5","cvss3Metrics":{"A":"High","AC":"High","PR":"None","S":"Unchanged","C":"High","UI":"None","AV":"Adjacent","I":"High"},"extraData":{}}</REMEDIATE> --> | True | CVE-2019-0227 (High) detected in axis-1.4.jar - ## CVE-2019-0227 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>axis-1.4.jar</b></p></summary>
<p>An implementation of the SOAP ("Simple Object Access Protocol") submission to W3C.</p>
<p>Library home page: <a href="http://ws.apache.org/axis">http://ws.apache.org/axis</a></p>
<p>Path to vulnerable library: /src/test/resources/webgoat/WEB-INF/lib/axis-1.4.jar</p>
<p>
Dependency Hierarchy:
- :x: **axis-1.4.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/snowdensb/sonar-xanitizer/commit/e2144e84b1fdbf18c01c24e6ab9ade7b45b25283">e2144e84b1fdbf18c01c24e6ab9ade7b45b25283</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
A Server Side Request Forgery (SSRF) vulnerability affected the Apache Axis 1.4 distribution that was last released in 2006. Security and bug commits commits continue in the projects Axis 1.x Subversion repository, legacy users are encouraged to build from source. The successor to Axis 1.x is Axis2, the latest version is 1.7.9 and is not vulnerable to this issue.
<p>Publish Date: 2019-05-01
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-0227>CVE-2019-0227</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: Adjacent
- Attack Complexity: High
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://rhinosecuritylabs.com/application-security/cve-2019-0227-expired-domain-rce-apache-axis/">https://rhinosecuritylabs.com/application-security/cve-2019-0227-expired-domain-rce-apache-axis/</a></p>
<p>Release Date: 2019-05-01</p>
<p>Fix Resolution: org.apache.axis2:axis2:1.7.9</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":"axis","packageName":"axis","packageVersion":"1.4","packageFilePaths":[],"isTransitiveDependency":false,"dependencyTree":"axis:axis:1.4","isMinimumFixVersionAvailable":true,"minimumFixVersion":"org.apache.axis2:axis2:1.7.9"}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2019-0227","vulnerabilityDetails":"A Server Side Request Forgery (SSRF) vulnerability affected the Apache Axis 1.4 distribution that was last released in 2006. Security and bug commits commits continue in the projects Axis 1.x Subversion repository, legacy users are encouraged to build from source. The successor to Axis 1.x is Axis2, the latest version is 1.7.9 and is not vulnerable to this issue.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-0227","cvss3Severity":"high","cvss3Score":"7.5","cvss3Metrics":{"A":"High","AC":"High","PR":"None","S":"Unchanged","C":"High","UI":"None","AV":"Adjacent","I":"High"},"extraData":{}}</REMEDIATE> --> | non_priority | cve high detected in axis jar cve high severity vulnerability vulnerable library axis jar an implementation of the soap simple object access protocol submission to library home page a href path to vulnerable library src test resources webgoat web inf lib axis jar dependency hierarchy x axis jar vulnerable library found in head commit a href found in base branch master vulnerability details a server side request forgery ssrf vulnerability affected the apache axis distribution that was last released in security and bug commits commits continue in the projects axis x subversion repository legacy users are encouraged to build from source the successor to axis x is the latest version is and is not vulnerable to this issue publish date url a href cvss score details base score metrics exploitability metrics attack vector adjacent attack complexity high privileges required none user interaction none scope unchanged impact metrics confidentiality impact high integrity impact high availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution org apache rescue worker helmet automatic remediation is available for this issue isopenpronvulnerability true ispackagebased true isdefaultbranch true packages istransitivedependency false dependencytree axis axis isminimumfixversionavailable true minimumfixversion org apache basebranches vulnerabilityidentifier cve vulnerabilitydetails a server side request forgery ssrf vulnerability affected the apache axis distribution that was last released in security and bug commits commits continue in the projects axis x subversion repository legacy users are encouraged to build from source the successor to axis x is the latest version is and is not vulnerable to this issue vulnerabilityurl | 0 |
644,285 | 20,972,829,348 | IssuesEvent | 2022-03-28 12:58:05 | mito-ds/monorepo | https://api.github.com/repos/mito-ds/monorepo | closed | Pivot table aggregation methods like `median` should be disabled for non-number columns | type: mitosheet effort: 2 priority: low | **Describe the bug**
Add a row to a pivot table, and then a value that is a string column. Set the aggregation method to `mean`, and get an error.
**Expected behavior**
The invalid options for the value aggregation should be disabled (with an error message) on non-number columns (e.g. everything but count, and count unique).
| 1.0 | Pivot table aggregation methods like `median` should be disabled for non-number columns - **Describe the bug**
Add a row to a pivot table, and then a value that is a string column. Set the aggregation method to `mean`, and get an error.
**Expected behavior**
The invalid options for the value aggregation should be disabled (with an error message) on non-number columns (e.g. everything but count, and count unique).
| priority | pivot table aggregation methods like median should be disabled for non number columns describe the bug add a row to a pivot table and then a value that is a string column set the aggregation method to mean and get an error expected behavior the invalid options for the value aggregation should be disabled with an error message on non number columns e g everything but count and count unique | 1 |
596,194 | 18,099,854,580 | IssuesEvent | 2021-09-22 13:11:53 | Timonwa/pelumi-akintokun | https://api.github.com/repos/Timonwa/pelumi-akintokun | opened | Refactor projects section | enhancement Medium priority | Add a json file for projects details and write JavaScript that uses only one project card and updates or adds more depending on the projects in the json file to reduce the HTML code. | 1.0 | Refactor projects section - Add a json file for projects details and write JavaScript that uses only one project card and updates or adds more depending on the projects in the json file to reduce the HTML code. | priority | refactor projects section add a json file for projects details and write javascript that uses only one project card and updates or adds more depending on the projects in the json file to reduce the html code | 1 |
339,563 | 10,256,197,883 | IssuesEvent | 2019-08-21 17:04:57 | ngageoint/hootenanny-ui | https://api.github.com/repos/ngageoint/hootenanny-ui | closed | UI adv opts sends mismatching matcher/merger config strings to web service | Category: UI Defined Priority: High Type: Bug | **Don't start on this until https://github.com/ngageoint/hootenanny/pull/2148 is merged.**
The hoot core settings "match.creators" and "merger.creators" are both a semicolon delimited string made of individual matchers/mergers and always must be of the same length. Currently, the UI adv opts sends strings with different numbers of inputs for each.
As part of [2145](https://github.com/ngageoint/hootenanny/issues/2145) a check was added to core to throw an exception when this happens. When running on the ? branch now, you will see an error like this if a mismatch is sent to the web services:
`22:05:43.787 DEBUG ...core/conflate/MatchFactory.cpp( 154) matchCreators: [5]{hoot::PoiPolygonMatchCreator, hoot::NetworkMatchCreator, hoot::BuildingMatchCreator, hoot::ScriptMatchCreator,PoiGeneric.js, hoot::ScriptMatchCreator,LinearWaterway.js}
22:05:43.788 DEBUG ...core/conflate/MatchFactory.cpp( 156) mergerCreators: [4]{hoot::PoiPolygonMergerCreator, hoot::NetworkMergerCreator, hoot::BuildingMergerCreator, hoot::ScriptMergerCreator}
], stderr=[Error running conflate:
The number of configured match creators (5) does not equal the number of configured merger creators (4)`
The adv opts UI needs to be corrected so that the number of matchers/creators is the same. The overall ordering of matchers/creators in both config strings is not important (e.g. match.creators="hoot::BuildingMatchCreator;hoot::NetworkMatchCreator" is equivalent to match.creators="hoot::NetworkMatchCreator;hoot::BuildingMatchCreator"), but each entry in the matchers list always needs to match in the correct order with the corresponding entry in the mergers list. (e.g. the following would be wrong: match.creators="hoot::BuildingMatchCreator;hoot::NetworkMatchCreator" and merger.creators=""hoot::NetworkMergerCreator;hoot::BuildingMergerCreator). Here is the current list of matchers and valid mergers:
- hoot::BuildingMatchCreator/hoot::BuildingMergerCreator
- hoot::HighwayMatchCreator/hoot::HighwaySnapMergerCreator
- hoot::NetworkMatchCreator/hoot::NetworkMergerCreator
- hoot::PoiPolygonMatchCreator/hoot::PoiPolygonMergerCreator
- hoot::ScriptMatchCreator,Area.js/hoot::ScriptMergerCreator
- hoot::ScriptMatchCreator,LinearWaterway.js/hoot::ScriptMergerCreator
- hoot::ScriptMatchCreator,PoiGeneric.js/hoot::ScriptMergerCreator
There must always be a separate hoot::ScriptMergerCreator entry for each hoot::ScriptMatchCreator,* entry.
For more info on matchers/mergers, see [match creators](https://github.com/ngageoint/hootenanny/blob/develop/conf/core/ConfigOptions.asciidoc#matchcreators) and [merger creators](https://github.com/ngageoint/hootenanny/blob/develop/conf/core/ConfigOptions.asciidoc#mergercreators).
When this and the following options are done, the autocorrect.options parameter can be removed from both the UI and the core:
* #969
* #970
* #971 | 1.0 | UI adv opts sends mismatching matcher/merger config strings to web service - **Don't start on this until https://github.com/ngageoint/hootenanny/pull/2148 is merged.**
The hoot core settings "match.creators" and "merger.creators" are both a semicolon delimited string made of individual matchers/mergers and always must be of the same length. Currently, the UI adv opts sends strings with different numbers of inputs for each.
As part of [2145](https://github.com/ngageoint/hootenanny/issues/2145) a check was added to core to throw an exception when this happens. When running on the ? branch now, you will see an error like this if a mismatch is sent to the web services:
`22:05:43.787 DEBUG ...core/conflate/MatchFactory.cpp( 154) matchCreators: [5]{hoot::PoiPolygonMatchCreator, hoot::NetworkMatchCreator, hoot::BuildingMatchCreator, hoot::ScriptMatchCreator,PoiGeneric.js, hoot::ScriptMatchCreator,LinearWaterway.js}
22:05:43.788 DEBUG ...core/conflate/MatchFactory.cpp( 156) mergerCreators: [4]{hoot::PoiPolygonMergerCreator, hoot::NetworkMergerCreator, hoot::BuildingMergerCreator, hoot::ScriptMergerCreator}
], stderr=[Error running conflate:
The number of configured match creators (5) does not equal the number of configured merger creators (4)`
The adv opts UI needs to be corrected so that the number of matchers/creators is the same. The overall ordering of matchers/creators in both config strings is not important (e.g. match.creators="hoot::BuildingMatchCreator;hoot::NetworkMatchCreator" is equivalent to match.creators="hoot::NetworkMatchCreator;hoot::BuildingMatchCreator"), but each entry in the matchers list always needs to match in the correct order with the corresponding entry in the mergers list. (e.g. the following would be wrong: match.creators="hoot::BuildingMatchCreator;hoot::NetworkMatchCreator" and merger.creators=""hoot::NetworkMergerCreator;hoot::BuildingMergerCreator). Here is the current list of matchers and valid mergers:
- hoot::BuildingMatchCreator/hoot::BuildingMergerCreator
- hoot::HighwayMatchCreator/hoot::HighwaySnapMergerCreator
- hoot::NetworkMatchCreator/hoot::NetworkMergerCreator
- hoot::PoiPolygonMatchCreator/hoot::PoiPolygonMergerCreator
- hoot::ScriptMatchCreator,Area.js/hoot::ScriptMergerCreator
- hoot::ScriptMatchCreator,LinearWaterway.js/hoot::ScriptMergerCreator
- hoot::ScriptMatchCreator,PoiGeneric.js/hoot::ScriptMergerCreator
There must always be a separate hoot::ScriptMergerCreator entry for each hoot::ScriptMatchCreator,* entry.
For more info on matchers/mergers, see [match creators](https://github.com/ngageoint/hootenanny/blob/develop/conf/core/ConfigOptions.asciidoc#matchcreators) and [merger creators](https://github.com/ngageoint/hootenanny/blob/develop/conf/core/ConfigOptions.asciidoc#mergercreators).
When this and the following options are done, the autocorrect.options parameter can be removed from both the UI and the core:
* #969
* #970
* #971 | priority | ui adv opts sends mismatching matcher merger config strings to web service don t start on this until is merged the hoot core settings match creators and merger creators are both a semicolon delimited string made of individual matchers mergers and always must be of the same length currently the ui adv opts sends strings with different numbers of inputs for each as part of a check was added to core to throw an exception when this happens when running on the branch now you will see an error like this if a mismatch is sent to the web services debug core conflate matchfactory cpp matchcreators hoot poipolygonmatchcreator hoot networkmatchcreator hoot buildingmatchcreator hoot scriptmatchcreator poigeneric js hoot scriptmatchcreator linearwaterway js debug core conflate matchfactory cpp mergercreators hoot poipolygonmergercreator hoot networkmergercreator hoot buildingmergercreator hoot scriptmergercreator stderr error running conflate the number of configured match creators does not equal the number of configured merger creators the adv opts ui needs to be corrected so that the number of matchers creators is the same the overall ordering of matchers creators in both config strings is not important e g match creators hoot buildingmatchcreator hoot networkmatchcreator is equivalent to match creators hoot networkmatchcreator hoot buildingmatchcreator but each entry in the matchers list always needs to match in the correct order with the corresponding entry in the mergers list e g the following would be wrong match creators hoot buildingmatchcreator hoot networkmatchcreator and merger creators hoot networkmergercreator hoot buildingmergercreator here is the current list of matchers and valid mergers hoot buildingmatchcreator hoot buildingmergercreator hoot highwaymatchcreator hoot highwaysnapmergercreator hoot networkmatchcreator hoot networkmergercreator hoot poipolygonmatchcreator hoot poipolygonmergercreator hoot scriptmatchcreator area js hoot scriptmergercreator hoot scriptmatchcreator linearwaterway js hoot scriptmergercreator hoot scriptmatchcreator poigeneric js hoot scriptmergercreator there must always be a separate hoot scriptmergercreator entry for each hoot scriptmatchcreator entry for more info on matchers mergers see and when this and the following options are done the autocorrect options parameter can be removed from both the ui and the core | 1 |
80,409 | 30,273,686,249 | IssuesEvent | 2023-07-07 17:32:44 | H-uru/Plasma | https://api.github.com/repos/H-uru/Plasma | closed | Game is pixelated when using HiDPI Scaling on Windows | Client Hacktoberfest Defect | Conversation with @cwalther on IRC 2020-02-29 indicates problems with playing the game when Windows scaling is enabled. He reports the image is improperly scaled using nearest neighbor interpolation when playing in full screen. There is a [previous report](https://forum.guildofwriters.org/viewtopic.php?f=117&t=7062) of chicanery as well.
```[17:16:20] <CWalther> Hi everyone! I’m just trying out Gehn 27, and it’s not looking as good as it should on my 4K display when I choose the full 3840x2160 resolution. Things are scaled as if it was rendering for 3840x2160 (e.g. the cursor is tiny), but the view is rendered at 1920x2160 and pixel-doubled, so it looks blocky. Is that the way it’s supposed to be? It may have been that way before, I don’t remember exactly. Do I need to
[17:16:21] <CWalther> tweak anything in my Windows display settings? It’s set to 200%, “fix scaling” off and no custom scaling.
[17:16:53] <CWalther> *rendered at 1920x1080
[17:26:27] <Doobes> Hoikas would probably have the best answer for that as he's been able to grab high res screenshots of things.
[17:27:24] <Doobes> He may currently be AFK or busy with something though.
[17:27:27] <CWalther> Yeah, I remembered that so it seems odd.
[17:28:30] <Doobes> Wish I could help, but I'm still stuck in 1080p land. :D
[17:32:30] <CWalther> Chiso is looking fantastic in 1080p! :)
[17:47:03] <Hoikas> I haven't seen any issues on my 3840x1600 display, CWalther
[17:47:42] <CWalther> I almost suspected as much, otherwise you’d have fixed them :)
[17:48:47] <CWalther> I can try playing with the Windows settings.
[17:50:03] <Hoikas> I know we had a complaint recently from someone playing with scaling enabled, but I think that was a case of the UI being offscreen
[17:51:18] <CWalther> With 100% scale it looks good (but I don't want my Windows desktop that tiny).
[17:51:33] <Hoikas> :)
[17:52:27] <Hoikas> I don't touch scaling myself. I invariantly use programs that look terrible with it on. Instead, I "just" (a year ago) bought an ultrawide monitor
[17:54:44] <CWalther> With 200% and “fix scaling for apps” enabled (whatever that is), no difference, still blocky.
[17:57:06] <CWalther> With “custom scaling” 300%, pixel-tripled blocky.
[17:57:32] <Hoikas> I'm not sure I understand "pixel-doubled" and "pixel-tripled"
[17:58:01] <CWalther> What I mean is that groups of 2x2 or 3x3 physical pixels have the same color to make one image pixel.
[17:58:17] <Hoikas> ok
[17:58:41] <CWalther> As if you scaled up a lower-res image using nearest neighbor interpolation.
[17:59:07] <Hoikas> that very well could be what is actually happening
[18:00:24] <CWalther> I guess so. MOULa by the way does not do that, so it probably has to do with resolution-awareness added in newer WIndows SDKs or somesuch.
[18:00:53] <Hoikas> or that "fullscreen" is just a borderless window for us
[18:01:25] <CWalther> Good point, I haven't tried what happens in windowed mode.
[18:02:40] <Hoikas> "Desktop applications must tell Windows if they support DPI scaling. By default, the system considers desktop applications DPI unaware and bitmap-stretches their windows."
[18:03:22] <Hoikas> I believe wingdi uses a crummy nearest-neighbor type filter by default
[18:03:43] <Hoikas> (but dwm should be DX, not gdi...)
[18:04:46] <CWalther> I read those docs once when I was working on a Windows app… it's horribly complicated. There are multiple stages of awareness.
[18:05:11] <Hoikas> I've skimmed them before and am currently filled with dread.
[18:11:50] <Hoikas> This actually does not look too hard to fix for Windows 10 1703 and later
[18:12:30] <Hoikas> As for anything earlier than that... "update to a recent OS"
[18:15:35] <CWalther> In windowed mode (with my original 200% setting) it looks like it renders either at the chosen resolution, or if that is larger than 1920x1080 squished down to that (not even preserving aspect ratio), and then pixel-doubles it.
[18:16:16] <CWalther> “update to a recent OS” – I’m fine with that as far as Windows is concerned
[18:16:56] <Hoikas> strange stuff. I'll have to look at this when my screen isn't full
[18:17:09] * Hoikas shivers at the idea of playing with the Windows scaling features
[18:17:34] <CWalther> Eh, no pressure. I was just wondering if it was a known problem.
[18:19:05] <Hoikas> it wasn't--thanks for bringing it up!
[18:19:52] <CWalther> (Of course, going further it would also be nice if it would take into account the Windows scaling factor for things like the cursor and the mouseover player name text (was that “plates” too?), so these wouldn’t be tiny for me.)
[18:21:12] <Hoikas> from what I see, windows will provide client RECT if we opt into dpi awareness v2, so hopefully if we resize to that rect, everything should be fine
[18:21:58] <Hoikas> of course, my understanding might be completely wrong as well ^_^
[18:22:43] <CWalther> I don't remember how you opt in - was it a manifest setting, or a function to call?
[18:24:27] <Hoikas> in Windows 8 it was the former, but in Windows 10 1607, we can use SetThreadDpiAwarenessContext
[18:25:02] <CWalther> Ugh, thread-specific?
[18:25:46] <Hoikas> SetProcessDpiAwarenessContext was added in 1703, it seems
[18:26:03] <Hoikas> "It is recommended that you set the process-default DPI awareness via application manifest. See Setting the default DPI awareness for a process for more information. Setting the process-default DPI awareness via API call can lead to unexpected application behavior."
[18:27:08] <Hoikas> the per-thread function seems to be more flexible. Windows are generally bound to a specific thread, so it makes sense to use that
``` | 1.0 | Game is pixelated when using HiDPI Scaling on Windows - Conversation with @cwalther on IRC 2020-02-29 indicates problems with playing the game when Windows scaling is enabled. He reports the image is improperly scaled using nearest neighbor interpolation when playing in full screen. There is a [previous report](https://forum.guildofwriters.org/viewtopic.php?f=117&t=7062) of chicanery as well.
```[17:16:20] <CWalther> Hi everyone! I’m just trying out Gehn 27, and it’s not looking as good as it should on my 4K display when I choose the full 3840x2160 resolution. Things are scaled as if it was rendering for 3840x2160 (e.g. the cursor is tiny), but the view is rendered at 1920x2160 and pixel-doubled, so it looks blocky. Is that the way it’s supposed to be? It may have been that way before, I don’t remember exactly. Do I need to
[17:16:21] <CWalther> tweak anything in my Windows display settings? It’s set to 200%, “fix scaling” off and no custom scaling.
[17:16:53] <CWalther> *rendered at 1920x1080
[17:26:27] <Doobes> Hoikas would probably have the best answer for that as he's been able to grab high res screenshots of things.
[17:27:24] <Doobes> He may currently be AFK or busy with something though.
[17:27:27] <CWalther> Yeah, I remembered that so it seems odd.
[17:28:30] <Doobes> Wish I could help, but I'm still stuck in 1080p land. :D
[17:32:30] <CWalther> Chiso is looking fantastic in 1080p! :)
[17:47:03] <Hoikas> I haven't seen any issues on my 3840x1600 display, CWalther
[17:47:42] <CWalther> I almost suspected as much, otherwise you’d have fixed them :)
[17:48:47] <CWalther> I can try playing with the Windows settings.
[17:50:03] <Hoikas> I know we had a complaint recently from someone playing with scaling enabled, but I think that was a case of the UI being offscreen
[17:51:18] <CWalther> With 100% scale it looks good (but I don't want my Windows desktop that tiny).
[17:51:33] <Hoikas> :)
[17:52:27] <Hoikas> I don't touch scaling myself. I invariantly use programs that look terrible with it on. Instead, I "just" (a year ago) bought an ultrawide monitor
[17:54:44] <CWalther> With 200% and “fix scaling for apps” enabled (whatever that is), no difference, still blocky.
[17:57:06] <CWalther> With “custom scaling” 300%, pixel-tripled blocky.
[17:57:32] <Hoikas> I'm not sure I understand "pixel-doubled" and "pixel-tripled"
[17:58:01] <CWalther> What I mean is that groups of 2x2 or 3x3 physical pixels have the same color to make one image pixel.
[17:58:17] <Hoikas> ok
[17:58:41] <CWalther> As if you scaled up a lower-res image using nearest neighbor interpolation.
[17:59:07] <Hoikas> that very well could be what is actually happening
[18:00:24] <CWalther> I guess so. MOULa by the way does not do that, so it probably has to do with resolution-awareness added in newer WIndows SDKs or somesuch.
[18:00:53] <Hoikas> or that "fullscreen" is just a borderless window for us
[18:01:25] <CWalther> Good point, I haven't tried what happens in windowed mode.
[18:02:40] <Hoikas> "Desktop applications must tell Windows if they support DPI scaling. By default, the system considers desktop applications DPI unaware and bitmap-stretches their windows."
[18:03:22] <Hoikas> I believe wingdi uses a crummy nearest-neighbor type filter by default
[18:03:43] <Hoikas> (but dwm should be DX, not gdi...)
[18:04:46] <CWalther> I read those docs once when I was working on a Windows app… it's horribly complicated. There are multiple stages of awareness.
[18:05:11] <Hoikas> I've skimmed them before and am currently filled with dread.
[18:11:50] <Hoikas> This actually does not look too hard to fix for Windows 10 1703 and later
[18:12:30] <Hoikas> As for anything earlier than that... "update to a recent OS"
[18:15:35] <CWalther> In windowed mode (with my original 200% setting) it looks like it renders either at the chosen resolution, or if that is larger than 1920x1080 squished down to that (not even preserving aspect ratio), and then pixel-doubles it.
[18:16:16] <CWalther> “update to a recent OS” – I’m fine with that as far as Windows is concerned
[18:16:56] <Hoikas> strange stuff. I'll have to look at this when my screen isn't full
[18:17:09] * Hoikas shivers at the idea of playing with the Windows scaling features
[18:17:34] <CWalther> Eh, no pressure. I was just wondering if it was a known problem.
[18:19:05] <Hoikas> it wasn't--thanks for bringing it up!
[18:19:52] <CWalther> (Of course, going further it would also be nice if it would take into account the Windows scaling factor for things like the cursor and the mouseover player name text (was that “plates” too?), so these wouldn’t be tiny for me.)
[18:21:12] <Hoikas> from what I see, windows will provide client RECT if we opt into dpi awareness v2, so hopefully if we resize to that rect, everything should be fine
[18:21:58] <Hoikas> of course, my understanding might be completely wrong as well ^_^
[18:22:43] <CWalther> I don't remember how you opt in - was it a manifest setting, or a function to call?
[18:24:27] <Hoikas> in Windows 8 it was the former, but in Windows 10 1607, we can use SetThreadDpiAwarenessContext
[18:25:02] <CWalther> Ugh, thread-specific?
[18:25:46] <Hoikas> SetProcessDpiAwarenessContext was added in 1703, it seems
[18:26:03] <Hoikas> "It is recommended that you set the process-default DPI awareness via application manifest. See Setting the default DPI awareness for a process for more information. Setting the process-default DPI awareness via API call can lead to unexpected application behavior."
[18:27:08] <Hoikas> the per-thread function seems to be more flexible. Windows are generally bound to a specific thread, so it makes sense to use that
``` | non_priority | game is pixelated when using hidpi scaling on windows conversation with cwalther on irc indicates problems with playing the game when windows scaling is enabled he reports the image is improperly scaled using nearest neighbor interpolation when playing in full screen there is a of chicanery as well hi everyone i’m just trying out gehn and it’s not looking as good as it should on my display when i choose the full resolution things are scaled as if it was rendering for e g the cursor is tiny but the view is rendered at and pixel doubled so it looks blocky is that the way it’s supposed to be it may have been that way before i don’t remember exactly do i need to tweak anything in my windows display settings it’s set to “fix scaling” off and no custom scaling rendered at hoikas would probably have the best answer for that as he s been able to grab high res screenshots of things he may currently be afk or busy with something though yeah i remembered that so it seems odd wish i could help but i m still stuck in land d chiso is looking fantastic in i haven t seen any issues on my display cwalther i almost suspected as much otherwise you’d have fixed them i can try playing with the windows settings i know we had a complaint recently from someone playing with scaling enabled but i think that was a case of the ui being offscreen with scale it looks good but i don t want my windows desktop that tiny i don t touch scaling myself i invariantly use programs that look terrible with it on instead i just a year ago bought an ultrawide monitor with and “fix scaling for apps” enabled whatever that is no difference still blocky with “custom scaling” pixel tripled blocky i m not sure i understand pixel doubled and pixel tripled what i mean is that groups of or physical pixels have the same color to make one image pixel ok as if you scaled up a lower res image using nearest neighbor interpolation that very well could be what is actually happening i guess so moula by the way does not do that so it probably has to do with resolution awareness added in newer windows sdks or somesuch or that fullscreen is just a borderless window for us good point i haven t tried what happens in windowed mode desktop applications must tell windows if they support dpi scaling by default the system considers desktop applications dpi unaware and bitmap stretches their windows i believe wingdi uses a crummy nearest neighbor type filter by default but dwm should be dx not gdi i read those docs once when i was working on a windows app… it s horribly complicated there are multiple stages of awareness i ve skimmed them before and am currently filled with dread this actually does not look too hard to fix for windows and later as for anything earlier than that update to a recent os in windowed mode with my original setting it looks like it renders either at the chosen resolution or if that is larger than squished down to that not even preserving aspect ratio and then pixel doubles it “update to a recent os” – i’m fine with that as far as windows is concerned strange stuff i ll have to look at this when my screen isn t full hoikas shivers at the idea of playing with the windows scaling features eh no pressure i was just wondering if it was a known problem it wasn t thanks for bringing it up of course going further it would also be nice if it would take into account the windows scaling factor for things like the cursor and the mouseover player name text was that “plates” too so these wouldn’t be tiny for me from what i see windows will provide client rect if we opt into dpi awareness so hopefully if we resize to that rect everything should be fine of course my understanding might be completely wrong as well i don t remember how you opt in was it a manifest setting or a function to call in windows it was the former but in windows we can use setthreaddpiawarenesscontext ugh thread specific setprocessdpiawarenesscontext was added in it seems it is recommended that you set the process default dpi awareness via application manifest see setting the default dpi awareness for a process for more information setting the process default dpi awareness via api call can lead to unexpected application behavior the per thread function seems to be more flexible windows are generally bound to a specific thread so it makes sense to use that | 0 |
56,099 | 3,078,216,071 | IssuesEvent | 2015-08-21 08:43:38 | pavel-pimenov/flylinkdc-r5xx | https://api.github.com/repos/pavel-pimenov/flylinkdc-r5xx | closed | Папки с медиафайлами в шаре имеют "качество звука" | enhancement imported Priority-Low | _From [reaor...@gmail.com](https://code.google.com/u/102418317896447533964/) on March 11, 2011 19:29:43_
Скрин ниже
**Attachment:** [Безымянный.JPG](http://code.google.com/p/flylinkdc/issues/detail?id=392)
_Original issue: http://code.google.com/p/flylinkdc/issues/detail?id=392_ | 1.0 | Папки с медиафайлами в шаре имеют "качество звука" - _From [reaor...@gmail.com](https://code.google.com/u/102418317896447533964/) on March 11, 2011 19:29:43_
Скрин ниже
**Attachment:** [Безымянный.JPG](http://code.google.com/p/flylinkdc/issues/detail?id=392)
_Original issue: http://code.google.com/p/flylinkdc/issues/detail?id=392_ | priority | папки с медиафайлами в шаре имеют качество звука from on march скрин ниже attachment original issue | 1 |
392,086 | 26,923,486,370 | IssuesEvent | 2023-02-07 12:11:53 | DanielAraldi/clean-node-api | https://api.github.com/repos/DanielAraldi/clean-node-api | closed | Add Refresh Token | documentation enhancement | ### Refresh Token
Currently, the API does not have an `endpoint` to update the user's `token`, that is, a `refresh token`. This should be added with the best user experience in mind. I emphasize that documentation must be written for this new API flow. | 1.0 | Add Refresh Token - ### Refresh Token
Currently, the API does not have an `endpoint` to update the user's `token`, that is, a `refresh token`. This should be added with the best user experience in mind. I emphasize that documentation must be written for this new API flow. | non_priority | add refresh token refresh token currently the api does not have an endpoint to update the user s token that is a refresh token this should be added with the best user experience in mind i emphasize that documentation must be written for this new api flow | 0 |
411,340 | 12,017,129,859 | IssuesEvent | 2020-04-10 17:40:35 | geomstats/geomstats | https://api.github.com/repos/geomstats/geomstats | opened | Remove warnings with nose2 | high priority | Running nose2 with np, pytorch and tf prints a lot of warnings, specifically for the examples with np.
We should fix the issue, or prevent these warnings to be printed when using nose2. | 1.0 | Remove warnings with nose2 - Running nose2 with np, pytorch and tf prints a lot of warnings, specifically for the examples with np.
We should fix the issue, or prevent these warnings to be printed when using nose2. | priority | remove warnings with running with np pytorch and tf prints a lot of warnings specifically for the examples with np we should fix the issue or prevent these warnings to be printed when using | 1 |
196,177 | 22,441,052,089 | IssuesEvent | 2022-06-21 01:20:24 | utopikkad/my-blog-vuejs | https://api.github.com/repos/utopikkad/my-blog-vuejs | closed | CVE-2020-8203 (High) detected in lodash-4.17.15.tgz - autoclosed | security vulnerability | ## CVE-2020-8203 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>lodash-4.17.15.tgz</b></p></summary>
<p>Lodash modular utilities.</p>
<p>Library home page: <a href="https://registry.npmjs.org/lodash/-/lodash-4.17.15.tgz">https://registry.npmjs.org/lodash/-/lodash-4.17.15.tgz</a></p>
<p>Path to dependency file: my-blog-vuejs/package.json</p>
<p>Path to vulnerable library: my-blog-vuejs/node_modules/lodash/package.json</p>
<p>
Dependency Hierarchy:
- nuxt-2.11.0.tgz (Root Library)
- builder-2.11.0.tgz
- :x: **lodash-4.17.15.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/utopikkad/my-blog-vuejs/commit/f3e8a4d9e82da6e74534fd6912d6644a8fdf93d6">f3e8a4d9e82da6e74534fd6912d6644a8fdf93d6</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>
Prototype pollution attack when using _.zipObjectDeep in lodash before 4.17.20.
<p>Publish Date: 2020-07-15
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-8203>CVE-2020-8203</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.4</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://www.npmjs.com/advisories/1523">https://www.npmjs.com/advisories/1523</a></p>
<p>Release Date: 2020-10-21</p>
<p>Fix Resolution: lodash - 4.17.19</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-8203 (High) detected in lodash-4.17.15.tgz - autoclosed - ## CVE-2020-8203 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>lodash-4.17.15.tgz</b></p></summary>
<p>Lodash modular utilities.</p>
<p>Library home page: <a href="https://registry.npmjs.org/lodash/-/lodash-4.17.15.tgz">https://registry.npmjs.org/lodash/-/lodash-4.17.15.tgz</a></p>
<p>Path to dependency file: my-blog-vuejs/package.json</p>
<p>Path to vulnerable library: my-blog-vuejs/node_modules/lodash/package.json</p>
<p>
Dependency Hierarchy:
- nuxt-2.11.0.tgz (Root Library)
- builder-2.11.0.tgz
- :x: **lodash-4.17.15.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/utopikkad/my-blog-vuejs/commit/f3e8a4d9e82da6e74534fd6912d6644a8fdf93d6">f3e8a4d9e82da6e74534fd6912d6644a8fdf93d6</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>
Prototype pollution attack when using _.zipObjectDeep in lodash before 4.17.20.
<p>Publish Date: 2020-07-15
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-8203>CVE-2020-8203</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.4</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://www.npmjs.com/advisories/1523">https://www.npmjs.com/advisories/1523</a></p>
<p>Release Date: 2020-10-21</p>
<p>Fix Resolution: lodash - 4.17.19</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 lodash tgz autoclosed cve high severity vulnerability vulnerable library lodash tgz lodash modular utilities library home page a href path to dependency file my blog vuejs package json path to vulnerable library my blog vuejs node modules lodash package json dependency hierarchy nuxt tgz root library builder tgz x lodash tgz vulnerable library found in head commit a href vulnerability details prototype pollution attack when using zipobjectdeep in lodash before publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity high privileges required none user interaction none scope unchanged impact metrics confidentiality impact none integrity impact high availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution lodash step up your open source security game with whitesource | 0 |
41,645 | 10,757,833,951 | IssuesEvent | 2019-10-31 13:59:52 | paritytech/parity-ethereum | https://api.github.com/repos/paritytech/parity-ethereum | closed | Docker centos build fails | M0-build 🏗 | - **Parity Ethereum version**: 2.7.0-nightly
- **Operating system**: Linux
- **Installation**: docker built from source
I'm trying to build the centos docker version of Parity, based on the template in the master branch repo: https://github.com/paritytech/parity-ethereum/tree/master/scripts/docker.
The README.md seems to be outdated after move `docker` directory to `scripts` directory. After run the `build.sh` in the right directory:
```
git clone https://github.com/paritytech/parity-ethereum.git
cd parity-ethereum/scripts
./docker/centos/build.sh
```
I got the following cmake error:
```
cmake version 3.12.0
CMake suite maintained and supported by Kitware (kitware.com/cmake).
error: could not find `Cargo.toml` in `/build/parity-ethereum` or any parent directory
The command '/bin/sh -c yum -y update && yum install -y systemd-devel git make gcc-c++ gcc file binutils && curl -L "https://cmake.org/files/v3.12/cmake-3.12.0-Linux-x86_64.tar.gz" -o cmake.tar.gz && tar -xzf cmake.tar.gz && cp -r cmake-3.12.0-Linux-x86_64/* /usr/ && curl https://sh.rustup.rs -sSf | sh -s -- -y && PATH=/root/.cargo/bin:$PATH && RUST_BACKTRACE=1 && rustc -vV && cargo -V && gcc -v && g++ -v && cmake --version && cd parity-ethereum && cargo build --verbose --release --features final && strip /build/parity-ethereum/target/release/parity && file /build/parity-ethereum/target/release/parity' returned a non-zero code: 101
```
This is because the [Dockerfile.build](https://github.com/paritytech/parity-ethereum/blob/master/scripts/docker/centos/Dockerfile.build#L5) is adding from the scripts directory instead from the previous path with the parity source code.
## How to fix
Update [build.sh](https://github.com/paritytech/parity-ethereum/blob/master/scripts/docker/centos/build.sh) shell script replacing the old path `docker/centos` to the new one `scripts/docker/centos`:
```
sed -i 's,docker/centos,scripts/docker/centos,g' build.sh
```
Run from `parity-ethereum` directory:
```
git clone https://github.com/paritytech/parity-ethereum.git
cd parity-ethereum/
./scripts/docker/centos/build.sh
``` | 1.0 | Docker centos build fails - - **Parity Ethereum version**: 2.7.0-nightly
- **Operating system**: Linux
- **Installation**: docker built from source
I'm trying to build the centos docker version of Parity, based on the template in the master branch repo: https://github.com/paritytech/parity-ethereum/tree/master/scripts/docker.
The README.md seems to be outdated after move `docker` directory to `scripts` directory. After run the `build.sh` in the right directory:
```
git clone https://github.com/paritytech/parity-ethereum.git
cd parity-ethereum/scripts
./docker/centos/build.sh
```
I got the following cmake error:
```
cmake version 3.12.0
CMake suite maintained and supported by Kitware (kitware.com/cmake).
error: could not find `Cargo.toml` in `/build/parity-ethereum` or any parent directory
The command '/bin/sh -c yum -y update && yum install -y systemd-devel git make gcc-c++ gcc file binutils && curl -L "https://cmake.org/files/v3.12/cmake-3.12.0-Linux-x86_64.tar.gz" -o cmake.tar.gz && tar -xzf cmake.tar.gz && cp -r cmake-3.12.0-Linux-x86_64/* /usr/ && curl https://sh.rustup.rs -sSf | sh -s -- -y && PATH=/root/.cargo/bin:$PATH && RUST_BACKTRACE=1 && rustc -vV && cargo -V && gcc -v && g++ -v && cmake --version && cd parity-ethereum && cargo build --verbose --release --features final && strip /build/parity-ethereum/target/release/parity && file /build/parity-ethereum/target/release/parity' returned a non-zero code: 101
```
This is because the [Dockerfile.build](https://github.com/paritytech/parity-ethereum/blob/master/scripts/docker/centos/Dockerfile.build#L5) is adding from the scripts directory instead from the previous path with the parity source code.
## How to fix
Update [build.sh](https://github.com/paritytech/parity-ethereum/blob/master/scripts/docker/centos/build.sh) shell script replacing the old path `docker/centos` to the new one `scripts/docker/centos`:
```
sed -i 's,docker/centos,scripts/docker/centos,g' build.sh
```
Run from `parity-ethereum` directory:
```
git clone https://github.com/paritytech/parity-ethereum.git
cd parity-ethereum/
./scripts/docker/centos/build.sh
``` | non_priority | docker centos build fails parity ethereum version nightly operating system linux installation docker built from source i m trying to build the centos docker version of parity based on the template in the master branch repo the readme md seems to be outdated after move docker directory to scripts directory after run the build sh in the right directory git clone cd parity ethereum scripts docker centos build sh i got the following cmake error cmake version cmake suite maintained and supported by kitware kitware com cmake error could not find cargo toml in build parity ethereum or any parent directory the command bin sh c yum y update yum install y systemd devel git make gcc c gcc file binutils curl l o cmake tar gz tar xzf cmake tar gz cp r cmake linux usr curl ssf sh s y path root cargo bin path rust backtrace rustc vv cargo v gcc v g v cmake version cd parity ethereum cargo build verbose release features final strip build parity ethereum target release parity file build parity ethereum target release parity returned a non zero code this is because the is adding from the scripts directory instead from the previous path with the parity source code how to fix update shell script replacing the old path docker centos to the new one scripts docker centos sed i s docker centos scripts docker centos g build sh run from parity ethereum directory git clone cd parity ethereum scripts docker centos build sh | 0 |
49,975 | 20,984,575,260 | IssuesEvent | 2022-03-29 00:44:21 | Azure/azure-sdk-for-go | https://api.github.com/repos/Azure/azure-sdk-for-go | closed | [azservicebus] Sessions detach can be inconsistent | bug Service Bus Client | After a link detach it seems like there's a delay between the session lock expiring and me being able to reconnect to it.
This makes it so recovery is difficult - our current error code just assumes that attempting to open a session either works because we obtain the lock, or fails because the session is already locked. It doesn't attempt to account for a potential delay until the session becomes available again.
I need to investigate this a bit more - I have a simple test that just does a detach on an entity and then attempts to recover the link.
This is related to me wanting to fix the issue with message completion retrying unnecessarily when the lock has expired. | 1.0 | [azservicebus] Sessions detach can be inconsistent - After a link detach it seems like there's a delay between the session lock expiring and me being able to reconnect to it.
This makes it so recovery is difficult - our current error code just assumes that attempting to open a session either works because we obtain the lock, or fails because the session is already locked. It doesn't attempt to account for a potential delay until the session becomes available again.
I need to investigate this a bit more - I have a simple test that just does a detach on an entity and then attempts to recover the link.
This is related to me wanting to fix the issue with message completion retrying unnecessarily when the lock has expired. | non_priority | sessions detach can be inconsistent after a link detach it seems like there s a delay between the session lock expiring and me being able to reconnect to it this makes it so recovery is difficult our current error code just assumes that attempting to open a session either works because we obtain the lock or fails because the session is already locked it doesn t attempt to account for a potential delay until the session becomes available again i need to investigate this a bit more i have a simple test that just does a detach on an entity and then attempts to recover the link this is related to me wanting to fix the issue with message completion retrying unnecessarily when the lock has expired | 0 |
148,411 | 23,348,213,472 | IssuesEvent | 2022-08-09 20:12:57 | carbon-design-system/carbon-for-ibm-dotcom | https://api.github.com/repos/carbon-design-system/carbon-for-ibm-dotcom | closed | [Cards] audit & synthesis continued | design design: visual design: study | ## User story
As a designer, I need to perform an audit of the Card components across IBM.com in order to identify inconsistencies, and synthesize findings into recommendations
Continuation of #9061
## Additional information
### Differentiating from the background
Thy explored adding a stroke around selectable tiles in Carbon to pass accessibility requirements, however we don't _need_ to add a stroke. We want to determine if there are other ways to show that a card is clickable (interactive), other than adding a stroke around the entire tile, so that I can update the tile guidance.
- Are there other ways we could separate cards from the background?
- How would this effect current card usage?
- Example: Gatsby resource cards and IBM.com use condensed cards often, would the drop shadow work in this scenario?
**Drop shadow**
- Grid usage for single vs group of cards
- [ ] default
- [ ] narrow
- [ ] condensed
- Tile color
- ui-01 / layer-01
- ui-02 / background or layer-02(possibly messes up logic)
- can marketing use white tiles on white background)
- Themes
- Does the solution work for dark themes?
**Lighter stroke**
previous explorations used gray50 to pass 3:1 contrast. Could we use a lighter stroke like `border-subtle`?
- Grid usage for single vs group of cards
- [ ] default
- [ ] narrow
- [ ] condensed
- Tile color
- `ui-01` / `layer-01`
- `ui-02` / `background` or `layer-02`(possibly messes up logic)
- can marketing use white tiles on white background)
- Themes
- Does the solution work for dark themes?
### Establish icon consistency
We would like to establish clear rules for icon consistency within Cards, this is a partial continuation from the previous sprint.
1. Be consistent with icon color treatment in a UI
a. CTA icon is blue if stand alone
b. CTA icon is gray or white If there are colorful elements on a card (images, icons, pictograms, other logos)
2. Consistent placement
a. If one icon aligned left
b. If multiple icons: arrows aligned left; other aligned right
- Identify where we are breaking this rule
- Themes
- Does the solution work for dark themes?
### Resources
Previous ticket for Selectable tiles [Carbon repo]
Previous ticket reviewing Carbon for IBM.com cards #9061
### Acceptance criteria
- [ ] explorations documented in Figma file
- [ ] Share findings with Carbon and Carbon for IBM.com team
- [ ] Synthesis of recommendations provided | 3.0 | [Cards] audit & synthesis continued - ## User story
As a designer, I need to perform an audit of the Card components across IBM.com in order to identify inconsistencies, and synthesize findings into recommendations
Continuation of #9061
## Additional information
### Differentiating from the background
Thy explored adding a stroke around selectable tiles in Carbon to pass accessibility requirements, however we don't _need_ to add a stroke. We want to determine if there are other ways to show that a card is clickable (interactive), other than adding a stroke around the entire tile, so that I can update the tile guidance.
- Are there other ways we could separate cards from the background?
- How would this effect current card usage?
- Example: Gatsby resource cards and IBM.com use condensed cards often, would the drop shadow work in this scenario?
**Drop shadow**
- Grid usage for single vs group of cards
- [ ] default
- [ ] narrow
- [ ] condensed
- Tile color
- ui-01 / layer-01
- ui-02 / background or layer-02(possibly messes up logic)
- can marketing use white tiles on white background)
- Themes
- Does the solution work for dark themes?
**Lighter stroke**
previous explorations used gray50 to pass 3:1 contrast. Could we use a lighter stroke like `border-subtle`?
- Grid usage for single vs group of cards
- [ ] default
- [ ] narrow
- [ ] condensed
- Tile color
- `ui-01` / `layer-01`
- `ui-02` / `background` or `layer-02`(possibly messes up logic)
- can marketing use white tiles on white background)
- Themes
- Does the solution work for dark themes?
### Establish icon consistency
We would like to establish clear rules for icon consistency within Cards, this is a partial continuation from the previous sprint.
1. Be consistent with icon color treatment in a UI
a. CTA icon is blue if stand alone
b. CTA icon is gray or white If there are colorful elements on a card (images, icons, pictograms, other logos)
2. Consistent placement
a. If one icon aligned left
b. If multiple icons: arrows aligned left; other aligned right
- Identify where we are breaking this rule
- Themes
- Does the solution work for dark themes?
### Resources
Previous ticket for Selectable tiles [Carbon repo]
Previous ticket reviewing Carbon for IBM.com cards #9061
### Acceptance criteria
- [ ] explorations documented in Figma file
- [ ] Share findings with Carbon and Carbon for IBM.com team
- [ ] Synthesis of recommendations provided | non_priority | audit synthesis continued user story as a designer i need to perform an audit of the card components across ibm com in order to identify inconsistencies and synthesize findings into recommendations continuation of additional information differentiating from the background thy explored adding a stroke around selectable tiles in carbon to pass accessibility requirements however we don t need to add a stroke we want to determine if there are other ways to show that a card is clickable interactive other than adding a stroke around the entire tile so that i can update the tile guidance are there other ways we could separate cards from the background how would this effect current card usage example gatsby resource cards and ibm com use condensed cards often would the drop shadow work in this scenario drop shadow grid usage for single vs group of cards default narrow condensed tile color ui layer ui background or layer possibly messes up logic can marketing use white tiles on white background themes does the solution work for dark themes lighter stroke previous explorations used to pass contrast could we use a lighter stroke like border subtle grid usage for single vs group of cards default narrow condensed tile color ui layer ui background or layer possibly messes up logic can marketing use white tiles on white background themes does the solution work for dark themes establish icon consistency we would like to establish clear rules for icon consistency within cards this is a partial continuation from the previous sprint be consistent with icon color treatment in a ui a cta icon is blue if stand alone b cta icon is gray or white if there are colorful elements on a card images icons pictograms other logos consistent placement a if one icon aligned left b if multiple icons arrows aligned left other aligned right identify where we are breaking this rule themes does the solution work for dark themes resources previous ticket for selectable tiles previous ticket reviewing carbon for ibm com cards acceptance criteria explorations documented in figma file share findings with carbon and carbon for ibm com team synthesis of recommendations provided | 0 |
137,108 | 18,752,635,541 | IssuesEvent | 2021-11-05 05:42:23 | madhans23/linux-4.15 | https://api.github.com/repos/madhans23/linux-4.15 | opened | CVE-2018-5814 (High) detected in multiple libraries | security vulnerability | ## CVE-2018-5814 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>linuxv4.15</b>, <b>linuxv4.15</b>, <b>linuxv4.15</b></p></summary>
<p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
In the Linux Kernel before version 4.16.11, 4.14.43, 4.9.102, and 4.4.133, multiple race condition errors when handling probe, disconnect, and rebind operations can be exploited to trigger a use-after-free condition or a NULL pointer dereference by sending multiple USB over IP packets.
<p>Publish Date: 2018-06-12
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-5814>CVE-2018-5814</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.0</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: High
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://nvd.nist.gov/vuln/detail/CVE-2018-5814">https://nvd.nist.gov/vuln/detail/CVE-2018-5814</a></p>
<p>Release Date: 2018-06-12</p>
<p>Fix Resolution: 4.16.11,4.14.43,4.9.102,4.4.133</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | CVE-2018-5814 (High) detected in multiple libraries - ## CVE-2018-5814 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>linuxv4.15</b>, <b>linuxv4.15</b>, <b>linuxv4.15</b></p></summary>
<p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
In the Linux Kernel before version 4.16.11, 4.14.43, 4.9.102, and 4.4.133, multiple race condition errors when handling probe, disconnect, and rebind operations can be exploited to trigger a use-after-free condition or a NULL pointer dereference by sending multiple USB over IP packets.
<p>Publish Date: 2018-06-12
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-5814>CVE-2018-5814</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.0</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: High
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://nvd.nist.gov/vuln/detail/CVE-2018-5814">https://nvd.nist.gov/vuln/detail/CVE-2018-5814</a></p>
<p>Release Date: 2018-06-12</p>
<p>Fix Resolution: 4.16.11,4.14.43,4.9.102,4.4.133</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 multiple libraries cve high severity vulnerability vulnerable libraries vulnerability details in the linux kernel before version and multiple race condition errors when handling probe disconnect and rebind operations can be exploited to trigger a use after free condition or a null pointer dereference by sending multiple usb over ip packets publish date url a href cvss score details base score metrics exploitability metrics attack vector local attack complexity high privileges required low user interaction none scope unchanged impact metrics confidentiality impact high integrity impact high availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution step up your open source security game with whitesource | 0 |
111,372 | 24,119,498,652 | IssuesEvent | 2022-09-20 17:22:41 | sourcegraph/sourcegraph | https://api.github.com/repos/sourcegraph/sourcegraph | opened | [Accessibility]: Code Insights — context menu doesn't announce items within menu | accessibility estimate/3d team/code-insights team/frontend-platform wcag/2.1/fixing wcag/2.1 | ### Audit type
Screen reader navigation
### User journey audit issue
https://github.com/sourcegraph/sourcegraph/issues/33502
### Problem description
If you open the code insight context menu (three dot menu) on the dashboard page screen reader doesn't announce focused item and therefore you can't figure out on which item you're currently focused
![Uploading Screenshot 2022-09-20 at 20.19.29.png…]()
### Expected behavior
Screen reader should announce available (not disabled) and focused item in the context menu.
### Additional details
I'm tagging frontend platform team because we use MenuButton component for this means which is part of the wildcard. It seems if it doesn't work for code insights it shouldn't work for all other places in the app and we should fix it on the wildcard level.
### Assigning labels
- [X] Please give this issue an estimate by applying a label like `estimate/Xd`, where X is the estimated number of days it will take to complete.
- [X] If this issue is specific to a specific Sourcegraph product, please assign the appropriate team label to this issue.
- [X] If this issue will require input from designers in order to complete, please assign the label `needs-design`.
- [X] If you are confident that this issue should be fixed by GitStart, please assign the label `gitstart`.
### Owner
I'm unsure who should work on this issue or if it needs more clarification. I will let the Frontend Platform team triage this. | 1.0 | [Accessibility]: Code Insights — context menu doesn't announce items within menu - ### Audit type
Screen reader navigation
### User journey audit issue
https://github.com/sourcegraph/sourcegraph/issues/33502
### Problem description
If you open the code insight context menu (three dot menu) on the dashboard page screen reader doesn't announce focused item and therefore you can't figure out on which item you're currently focused
![Uploading Screenshot 2022-09-20 at 20.19.29.png…]()
### Expected behavior
Screen reader should announce available (not disabled) and focused item in the context menu.
### Additional details
I'm tagging frontend platform team because we use MenuButton component for this means which is part of the wildcard. It seems if it doesn't work for code insights it shouldn't work for all other places in the app and we should fix it on the wildcard level.
### Assigning labels
- [X] Please give this issue an estimate by applying a label like `estimate/Xd`, where X is the estimated number of days it will take to complete.
- [X] If this issue is specific to a specific Sourcegraph product, please assign the appropriate team label to this issue.
- [X] If this issue will require input from designers in order to complete, please assign the label `needs-design`.
- [X] If you are confident that this issue should be fixed by GitStart, please assign the label `gitstart`.
### Owner
I'm unsure who should work on this issue or if it needs more clarification. I will let the Frontend Platform team triage this. | non_priority | code insights — context menu doesn t announce items within menu audit type screen reader navigation user journey audit issue problem description if you open the code insight context menu three dot menu on the dashboard page screen reader doesn t announce focused item and therefore you can t figure out on which item you re currently focused expected behavior screen reader should announce available not disabled and focused item in the context menu additional details i m tagging frontend platform team because we use menubutton component for this means which is part of the wildcard it seems if it doesn t work for code insights it shouldn t work for all other places in the app and we should fix it on the wildcard level assigning labels please give this issue an estimate by applying a label like estimate xd where x is the estimated number of days it will take to complete if this issue is specific to a specific sourcegraph product please assign the appropriate team label to this issue if this issue will require input from designers in order to complete please assign the label needs design if you are confident that this issue should be fixed by gitstart please assign the label gitstart owner i m unsure who should work on this issue or if it needs more clarification i will let the frontend platform team triage this | 0 |
219,045 | 7,333,086,593 | IssuesEvent | 2018-03-05 18:16:13 | NCEAS/metacat | https://api.github.com/repos/NCEAS/metacat | closed | Add ONEDCX stylesheet for D1 view service | Category: metacat Component: Bugzilla-Id Priority: Normal Status: Resolved Tracker: Bug | ---
Author Name: **ben leinfelder** (ben leinfelder)
Original Redmine Issue: 7032, https://projects.ecoinformatics.org/ecoinfo/issues/7032
Original Date: 2016-05-24
Original Assignee: ben leinfelder
---
see https://redmine.dataone.org/issues/7686
| 1.0 | Add ONEDCX stylesheet for D1 view service - ---
Author Name: **ben leinfelder** (ben leinfelder)
Original Redmine Issue: 7032, https://projects.ecoinformatics.org/ecoinfo/issues/7032
Original Date: 2016-05-24
Original Assignee: ben leinfelder
---
see https://redmine.dataone.org/issues/7686
| priority | add onedcx stylesheet for view service author name ben leinfelder ben leinfelder original redmine issue original date original assignee ben leinfelder see | 1 |
513,249 | 14,918,461,791 | IssuesEvent | 2021-01-22 21:44:23 | 3YOURMIND/kotti | https://api.github.com/repos/3YOURMIND/kotti | closed | Re-enable Jest for KtForm | package:kotti-ui priority:4-high scope:linting state:help wanted type:enhancement | We have unit tests for the KtForm that were disabled since moving to Lerna. We should re-enable them.
---
Split from #241 | 1.0 | Re-enable Jest for KtForm - We have unit tests for the KtForm that were disabled since moving to Lerna. We should re-enable them.
---
Split from #241 | priority | re enable jest for ktform we have unit tests for the ktform that were disabled since moving to lerna we should re enable them split from | 1 |
224,790 | 7,472,906,599 | IssuesEvent | 2018-04-03 14:00:43 | edenlabllc/ehealth.api | https://api.github.com/repos/edenlabllc/ehealth.api | closed | Problem on IL | kind/bug priority/medium status/todo | From logs:
```
** (MatchError) no match of right hand side value: %{}
(ehealth) lib/ehealth/persons/validator.ex:13: EHealth.Persons.Validator.validate/1
(ehealth) lib/ehealth/declaration_requests/declaration_requests.ex:140: EHealth.DeclarationRequests.create_offline/2
(ehealth) lib/ehealth/web/controllers/declaration_request_controller.ex:30: EHealth.Web.DeclarationRequestController.create/2
(ehealth) lib/ehealth/web/controllers/declaration_request_controller.ex:1: EHealth.Web.DeclarationRequestController.action/2
(ehealth) lib/ehealth/web/controllers/declaration_request_controller.ex:1: EHealth.Web.DeclarationRequestController.phoenix_controller_pipeline/2
(ehealth) lib/ehealth/endpoint.ex:1: EHealth.Web.Endpoint.instrument/4
(phoenix) lib/phoenix/router.ex:278: Phoenix.Router.__call__/1
(ehealth) lib/plug/error_handler.ex:64: EHealthWeb.Router.call/2
``` | 1.0 | Problem on IL - From logs:
```
** (MatchError) no match of right hand side value: %{}
(ehealth) lib/ehealth/persons/validator.ex:13: EHealth.Persons.Validator.validate/1
(ehealth) lib/ehealth/declaration_requests/declaration_requests.ex:140: EHealth.DeclarationRequests.create_offline/2
(ehealth) lib/ehealth/web/controllers/declaration_request_controller.ex:30: EHealth.Web.DeclarationRequestController.create/2
(ehealth) lib/ehealth/web/controllers/declaration_request_controller.ex:1: EHealth.Web.DeclarationRequestController.action/2
(ehealth) lib/ehealth/web/controllers/declaration_request_controller.ex:1: EHealth.Web.DeclarationRequestController.phoenix_controller_pipeline/2
(ehealth) lib/ehealth/endpoint.ex:1: EHealth.Web.Endpoint.instrument/4
(phoenix) lib/phoenix/router.ex:278: Phoenix.Router.__call__/1
(ehealth) lib/plug/error_handler.ex:64: EHealthWeb.Router.call/2
``` | priority | problem on il from logs matcherror no match of right hand side value ehealth lib ehealth persons validator ex ehealth persons validator validate ehealth lib ehealth declaration requests declaration requests ex ehealth declarationrequests create offline ehealth lib ehealth web controllers declaration request controller ex ehealth web declarationrequestcontroller create ehealth lib ehealth web controllers declaration request controller ex ehealth web declarationrequestcontroller action ehealth lib ehealth web controllers declaration request controller ex ehealth web declarationrequestcontroller phoenix controller pipeline ehealth lib ehealth endpoint ex ehealth web endpoint instrument phoenix lib phoenix router ex phoenix router call ehealth lib plug error handler ex ehealthweb router call | 1 |
491,427 | 14,163,820,106 | IssuesEvent | 2020-11-12 03:20:55 | momentum-mod/game | https://api.github.com/repos/momentum-mod/game | closed | info_particle_systems with "start_active 1" don't appear on map load | Priority: Low Size: Medium Type: Bug | **Describe the bug**
Any info_particle_system with the "start_active" keyvalue doesn't appear unless restarted via entity inputs.
**To Reproduce**
Steps to reproduce the behavior:
- Load a [map](https://github.com/momentum-mod/game/files/4366426/firetest.zip) with the aforementioned info_particle_system.
- Do `ent_fire particle stop` followed by `ent_fire particle start`, now the particle appears.
| 1.0 | info_particle_systems with "start_active 1" don't appear on map load - **Describe the bug**
Any info_particle_system with the "start_active" keyvalue doesn't appear unless restarted via entity inputs.
**To Reproduce**
Steps to reproduce the behavior:
- Load a [map](https://github.com/momentum-mod/game/files/4366426/firetest.zip) with the aforementioned info_particle_system.
- Do `ent_fire particle stop` followed by `ent_fire particle start`, now the particle appears.
| priority | info particle systems with start active don t appear on map load describe the bug any info particle system with the start active keyvalue doesn t appear unless restarted via entity inputs to reproduce steps to reproduce the behavior load a with the aforementioned info particle system do ent fire particle stop followed by ent fire particle start now the particle appears | 1 |
349,101 | 10,458,788,375 | IssuesEvent | 2019-09-20 09:22:58 | chef/chef | https://api.github.com/repos/chef/chef | closed | knife ssh looking for key with --ssh-user and --ssh-password specified | Priority: Medium Status: Needs Replication Status: Sustaining Backlog Type: Bug | Expected: Use my password and don't look for a key.
Actual:
```
[@gazoo:~/rcf-chef]↥ master+ ± knife ssh 'roles:*jenkins*' 'git --version' --no-host-key-verify --ssh-user jblaine --ssh-password
Enter your password:
WARNING: Failed to connect to jenkins-rhel6-slave.our.org -- Errno::ENOENT: No such file or directory @ rb_sysopen - /home/jblaine/.ssh/id_rsa
WARNING: Failed to connect to jenkins-rhel6-slave-w.our.org -- Errno::ENOENT: No such file or directory @ rb_sysopen - /home/jblaine/.ssh/id_rsa
[@gazoo:~/rcf-chef]↥ master+ ± knife --version
Chef: 12.3.0
[@gazoo:~/rcf-chef]↥ master+ ±
```
| 1.0 | knife ssh looking for key with --ssh-user and --ssh-password specified - Expected: Use my password and don't look for a key.
Actual:
```
[@gazoo:~/rcf-chef]↥ master+ ± knife ssh 'roles:*jenkins*' 'git --version' --no-host-key-verify --ssh-user jblaine --ssh-password
Enter your password:
WARNING: Failed to connect to jenkins-rhel6-slave.our.org -- Errno::ENOENT: No such file or directory @ rb_sysopen - /home/jblaine/.ssh/id_rsa
WARNING: Failed to connect to jenkins-rhel6-slave-w.our.org -- Errno::ENOENT: No such file or directory @ rb_sysopen - /home/jblaine/.ssh/id_rsa
[@gazoo:~/rcf-chef]↥ master+ ± knife --version
Chef: 12.3.0
[@gazoo:~/rcf-chef]↥ master+ ±
```
| priority | knife ssh looking for key with ssh user and ssh password specified expected use my password and don t look for a key actual ↥ master ± knife ssh roles jenkins git version no host key verify ssh user jblaine ssh password enter your password warning failed to connect to jenkins slave our org errno enoent no such file or directory rb sysopen home jblaine ssh id rsa warning failed to connect to jenkins slave w our org errno enoent no such file or directory rb sysopen home jblaine ssh id rsa ↥ master ± knife version chef ↥ master ± | 1 |
19,734 | 3,488,348,597 | IssuesEvent | 2016-01-02 21:44:52 | socallinuxexpo/SCALE-Design | https://api.github.com/repos/socallinuxexpo/SCALE-Design | closed | SCALE Stickers | design | We've had a sponsor sign up to provide stickers to SCALE this year. We just need to provide artwork. I'd suggest starting with the same stickermule templates as last year.
@hriday @ScislaC | 1.0 | SCALE Stickers - We've had a sponsor sign up to provide stickers to SCALE this year. We just need to provide artwork. I'd suggest starting with the same stickermule templates as last year.
@hriday @ScislaC | non_priority | scale stickers we ve had a sponsor sign up to provide stickers to scale this year we just need to provide artwork i d suggest starting with the same stickermule templates as last year hriday scislac | 0 |
152,016 | 5,831,629,238 | IssuesEvent | 2017-05-08 19:49:30 | VulcanDev/FinalProjectICS4U | https://api.github.com/repos/VulcanDev/FinalProjectICS4U | closed | Completion of planet generation code. | enhancement high priority | Need to complete the code for planet generation to allow for modular spawning of planets based on climateID.
This way we can add and removal planets at will and it won't change the core function when generating planets. | 1.0 | Completion of planet generation code. - Need to complete the code for planet generation to allow for modular spawning of planets based on climateID.
This way we can add and removal planets at will and it won't change the core function when generating planets. | priority | completion of planet generation code need to complete the code for planet generation to allow for modular spawning of planets based on climateid this way we can add and removal planets at will and it won t change the core function when generating planets | 1 |
428,238 | 29,935,098,142 | IssuesEvent | 2023-06-22 12:14:54 | Safe-DS/Stdlib | https://api.github.com/repos/Safe-DS/Stdlib | opened | Standardize Optional Type in docstrings | documentation :book: | Currently a parameter or return type of `some_type | None` is described in the docstring as either `some_type | None` or `Optional[some_type]`. We should set our standard for this case and change all other cases to this new standard.
Additionally there are cases where the parameter allows a None type but the docstring type does not show this. We should add this information to all those cases.
## Examples
`Optional[type]` in the `Imputer`
```py
def fit(self, table: Table, column_names: list[str] | None) -> Imputer:
"""
[...]
Parameters
----------
[...]
column_names : Optional[list[str]]
The list of columns from the table used to fit the transformer. If `None`, all columns are used.
[...]
"""
```
`type | None` in `Table`:
```py
def __init__(self, data: Mapping[str, Sequence[Any]] | None = None) -> None:
"""
Create a table from a mapping of column names to their values.
Parameters
----------
data : Mapping[str, Sequence[Any]] | None
The data. If None, an empty table is created.
[...]
"""
```
Example of a method without this information in `Table.py`:
```py
def slice_rows(
self,
start: int | None = None,
end: int | None = None,
step: int = 1,
) -> Table:
"""
Slice a part of the table into a new table.
This table is not modified.
Parameters
----------
start : int
The first index of the range to be copied into a new table, None by default.
end : int
The last index of the range to be copied into a new table, None by default.
[...]
"""
``` | 1.0 | Standardize Optional Type in docstrings - Currently a parameter or return type of `some_type | None` is described in the docstring as either `some_type | None` or `Optional[some_type]`. We should set our standard for this case and change all other cases to this new standard.
Additionally there are cases where the parameter allows a None type but the docstring type does not show this. We should add this information to all those cases.
## Examples
`Optional[type]` in the `Imputer`
```py
def fit(self, table: Table, column_names: list[str] | None) -> Imputer:
"""
[...]
Parameters
----------
[...]
column_names : Optional[list[str]]
The list of columns from the table used to fit the transformer. If `None`, all columns are used.
[...]
"""
```
`type | None` in `Table`:
```py
def __init__(self, data: Mapping[str, Sequence[Any]] | None = None) -> None:
"""
Create a table from a mapping of column names to their values.
Parameters
----------
data : Mapping[str, Sequence[Any]] | None
The data. If None, an empty table is created.
[...]
"""
```
Example of a method without this information in `Table.py`:
```py
def slice_rows(
self,
start: int | None = None,
end: int | None = None,
step: int = 1,
) -> Table:
"""
Slice a part of the table into a new table.
This table is not modified.
Parameters
----------
start : int
The first index of the range to be copied into a new table, None by default.
end : int
The last index of the range to be copied into a new table, None by default.
[...]
"""
``` | non_priority | standardize optional type in docstrings currently a parameter or return type of some type none is described in the docstring as either some type none or optional we should set our standard for this case and change all other cases to this new standard additionally there are cases where the parameter allows a none type but the docstring type does not show this we should add this information to all those cases examples optional in the imputer py def fit self table table column names list none imputer parameters column names optional the list of columns from the table used to fit the transformer if none all columns are used type none in table py def init self data mapping none none none create a table from a mapping of column names to their values parameters data mapping none the data if none an empty table is created example of a method without this information in table py py def slice rows self start int none none end int none none step int table slice a part of the table into a new table this table is not modified parameters start int the first index of the range to be copied into a new table none by default end int the last index of the range to be copied into a new table none by default | 0 |
66,130 | 14,767,355,985 | IssuesEvent | 2021-01-10 06:14:20 | shiriivtsan/bebo | https://api.github.com/repos/shiriivtsan/bebo | opened | CVE-2018-14721 (High) detected in jackson-databind-2.8.6.jar | security vulnerability | ## CVE-2018-14721 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>jackson-databind-2.8.6.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: bebo/jackson-databind-2.8.6.jar</p>
<p>
Dependency Hierarchy:
- :x: **jackson-databind-2.8.6.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/shiriivtsan/bebo/commit/8eb42e349cd3aded1eab4b65b59788a7e934dd99">8eb42e349cd3aded1eab4b65b59788a7e934dd99</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
FasterXML jackson-databind 2.x before 2.9.7 might allow remote attackers to conduct server-side request forgery (SSRF) attacks by leveraging failure to block the axis2-jaxws class from polymorphic deserialization.
<p>Publish Date: 2019-01-02
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-14721>CVE-2018-14721</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>10.0</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-14721">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-14721</a></p>
<p>Release Date: 2019-01-02</p>
<p>Fix Resolution: com.fasterxml.jackson.core:jackson-databind:2.9.7,2.8.11.3,2.7.9.5,2.6.7.3</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.8.6","isTransitiveDependency":false,"dependencyTree":"com.fasterxml.jackson.core:jackson-databind:2.8.6","isMinimumFixVersionAvailable":true,"minimumFixVersion":"com.fasterxml.jackson.core:jackson-databind:2.9.7,2.8.11.3,2.7.9.5,2.6.7.3"}],"vulnerabilityIdentifier":"CVE-2018-14721","vulnerabilityDetails":"FasterXML jackson-databind 2.x before 2.9.7 might allow remote attackers to conduct server-side request forgery (SSRF) attacks by leveraging failure to block the axis2-jaxws class from polymorphic deserialization.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-14721","cvss3Severity":"high","cvss3Score":"10.0","cvss3Metrics":{"A":"High","AC":"Low","PR":"None","S":"Changed","C":"High","UI":"None","AV":"Network","I":"High"},"extraData":{}}</REMEDIATE> --> | True | CVE-2018-14721 (High) detected in jackson-databind-2.8.6.jar - ## CVE-2018-14721 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>jackson-databind-2.8.6.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: bebo/jackson-databind-2.8.6.jar</p>
<p>
Dependency Hierarchy:
- :x: **jackson-databind-2.8.6.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/shiriivtsan/bebo/commit/8eb42e349cd3aded1eab4b65b59788a7e934dd99">8eb42e349cd3aded1eab4b65b59788a7e934dd99</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
FasterXML jackson-databind 2.x before 2.9.7 might allow remote attackers to conduct server-side request forgery (SSRF) attacks by leveraging failure to block the axis2-jaxws class from polymorphic deserialization.
<p>Publish Date: 2019-01-02
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-14721>CVE-2018-14721</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>10.0</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-14721">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2018-14721</a></p>
<p>Release Date: 2019-01-02</p>
<p>Fix Resolution: com.fasterxml.jackson.core:jackson-databind:2.9.7,2.8.11.3,2.7.9.5,2.6.7.3</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.8.6","isTransitiveDependency":false,"dependencyTree":"com.fasterxml.jackson.core:jackson-databind:2.8.6","isMinimumFixVersionAvailable":true,"minimumFixVersion":"com.fasterxml.jackson.core:jackson-databind:2.9.7,2.8.11.3,2.7.9.5,2.6.7.3"}],"vulnerabilityIdentifier":"CVE-2018-14721","vulnerabilityDetails":"FasterXML jackson-databind 2.x before 2.9.7 might allow remote attackers to conduct server-side request forgery (SSRF) attacks by leveraging failure to block the axis2-jaxws class from polymorphic deserialization.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-14721","cvss3Severity":"high","cvss3Score":"10.0","cvss3Metrics":{"A":"High","AC":"Low","PR":"None","S":"Changed","C":"High","UI":"None","AV":"Network","I":"High"},"extraData":{}}</REMEDIATE> --> | non_priority | cve high detected in jackson databind jar cve high severity vulnerability vulnerable library jackson databind jar general data binding functionality for jackson works on core streaming api library home page a href path to vulnerable library bebo 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 remote attackers to conduct server side request forgery ssrf attacks by leveraging failure to block the jaxws class from polymorphic deserialization publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope changed impact metrics confidentiality impact high integrity impact high availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution com fasterxml jackson core jackson databind rescue worker helmet automatic remediation is available for this issue isopenpronvulnerability true ispackagebased true isdefaultbranch true packages vulnerabilityidentifier cve vulnerabilitydetails fasterxml jackson databind x before might allow remote attackers to conduct server side request forgery ssrf attacks by leveraging failure to block the jaxws class from polymorphic deserialization vulnerabilityurl | 0 |
342,725 | 10,320,899,153 | IssuesEvent | 2019-08-30 22:14:39 | kubeflow/pipelines | https://api.github.com/repos/kubeflow/pipelines | closed | persistence agent should delete successful runs right after sync | area/back-end area/pipelines priority/p1 | **What happened:**
Argo workflow CRD pileup (100K+) caused GKE cluster API times out, causing issues for all namespaces in the cluster.
Excessive workflows (5K+) also caused significant UI slow down.
**What did you expect to happen:**
Persistence Agent deleted successful workflows right after sync.
Failed workflow can be GCed per workflow TTL since users may want to rerun the pipeline by skipping successful steps.
**What steps did you take:**
[A clear and concise description of what the bug is.]
**Anything else you would like to add:**
[Miscellaneous information that will assist in solving the issue.]
| 1.0 | persistence agent should delete successful runs right after sync - **What happened:**
Argo workflow CRD pileup (100K+) caused GKE cluster API times out, causing issues for all namespaces in the cluster.
Excessive workflows (5K+) also caused significant UI slow down.
**What did you expect to happen:**
Persistence Agent deleted successful workflows right after sync.
Failed workflow can be GCed per workflow TTL since users may want to rerun the pipeline by skipping successful steps.
**What steps did you take:**
[A clear and concise description of what the bug is.]
**Anything else you would like to add:**
[Miscellaneous information that will assist in solving the issue.]
| priority | persistence agent should delete successful runs right after sync what happened argo workflow crd pileup caused gke cluster api times out causing issues for all namespaces in the cluster excessive workflows also caused significant ui slow down what did you expect to happen persistence agent deleted successful workflows right after sync failed workflow can be gced per workflow ttl since users may want to rerun the pipeline by skipping successful steps what steps did you take anything else you would like to add | 1 |
21,997 | 10,708,664,764 | IssuesEvent | 2019-10-24 20:12:54 | nicktombeur/artificialcolors | https://api.github.com/repos/nicktombeur/artificialcolors | opened | CVE-2019-17531 (High) detected in jackson-databind-2.9.9.jar | security vulnerability | ## CVE-2019-17531 - 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.9.jar</b></p></summary>
<p>General data-binding functionality for Jackson: works on core streaming API</p>
<p>Library home page: <a href="http://github.com/FasterXML/jackson">http://github.com/FasterXML/jackson</a></p>
<p>Path to dependency file: /tmp/ws-scm/artificialcolors/back-end/pom.xml</p>
<p>Path to vulnerable library: /root/.m2/repository/com/fasterxml/jackson/core/jackson-databind/2.9.9/jackson-databind-2.9.9.jar</p>
<p>
Dependency Hierarchy:
- spring-boot-starter-web-2.1.6.RELEASE.jar (Root Library)
- spring-boot-starter-json-2.1.6.RELEASE.jar
- :x: **jackson-databind-2.9.9.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/nicktombeur/artificialcolors/commit/5fbe189d2d404af1fb2e57723fa5987ddd8376cb">5fbe189d2d404af1fb2e57723fa5987ddd8376cb</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
A Polymorphic Typing issue was discovered in FasterXML jackson-databind 2.0.0 through 2.9.10. When Default Typing is enabled (either globally or for a specific property) for an externally exposed JSON endpoint and the service has the apache-log4j-extra (version 1.2.x) jar in the classpath, and an attacker can provide a JNDI service to access, it is possible to make the service execute a malicious payload.
<p>Publish Date: 2019-10-12
<p>URL: <a href=https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-17531>CVE-2019-17531</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 2 Score Details (<b>7.5</b>)</summary>
<p>
Base Score Metrics not available</p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-17531">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-17531</a></p>
<p>Release Date: 2019-10-12</p>
<p>Fix Resolution: 2.10</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-17531 (High) detected in jackson-databind-2.9.9.jar - ## CVE-2019-17531 - 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.9.jar</b></p></summary>
<p>General data-binding functionality for Jackson: works on core streaming API</p>
<p>Library home page: <a href="http://github.com/FasterXML/jackson">http://github.com/FasterXML/jackson</a></p>
<p>Path to dependency file: /tmp/ws-scm/artificialcolors/back-end/pom.xml</p>
<p>Path to vulnerable library: /root/.m2/repository/com/fasterxml/jackson/core/jackson-databind/2.9.9/jackson-databind-2.9.9.jar</p>
<p>
Dependency Hierarchy:
- spring-boot-starter-web-2.1.6.RELEASE.jar (Root Library)
- spring-boot-starter-json-2.1.6.RELEASE.jar
- :x: **jackson-databind-2.9.9.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/nicktombeur/artificialcolors/commit/5fbe189d2d404af1fb2e57723fa5987ddd8376cb">5fbe189d2d404af1fb2e57723fa5987ddd8376cb</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
A Polymorphic Typing issue was discovered in FasterXML jackson-databind 2.0.0 through 2.9.10. When Default Typing is enabled (either globally or for a specific property) for an externally exposed JSON endpoint and the service has the apache-log4j-extra (version 1.2.x) jar in the classpath, and an attacker can provide a JNDI service to access, it is possible to make the service execute a malicious payload.
<p>Publish Date: 2019-10-12
<p>URL: <a href=https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-17531>CVE-2019-17531</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 2 Score Details (<b>7.5</b>)</summary>
<p>
Base Score Metrics not available</p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-17531">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-17531</a></p>
<p>Release Date: 2019-10-12</p>
<p>Fix Resolution: 2.10</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_priority | cve high detected in jackson databind jar cve high severity vulnerability vulnerable library jackson databind jar general data binding functionality for jackson works on core streaming api library home page a href path to dependency file tmp ws scm artificialcolors back end pom xml path to vulnerable library root repository com fasterxml jackson core jackson databind jackson databind jar dependency hierarchy spring boot starter web release jar root library spring boot starter json release jar x jackson databind jar vulnerable library found in head commit a href vulnerability details a polymorphic typing issue was discovered in fasterxml jackson databind through when default typing is enabled either globally or for a specific property for an externally exposed json endpoint and the service has the apache extra version x jar in the classpath and an attacker can provide a jndi service to access it is possible to make the service execute a malicious payload publish date url a href cvss score details base score metrics not available suggested fix type upgrade version origin a href release date fix resolution step up your open source security game with whitesource | 0 |
178,800 | 14,679,590,200 | IssuesEvent | 2020-12-31 07:25:34 | rasatmaja/links-barnacle | https://api.github.com/repos/rasatmaja/links-barnacle | closed | Add logging on repository, cors, and server | documentation | # **Add logging on repository, cors, and server**
**Issue type** :
- [x] 🤴 Code style update (formatting, renaming)
- [x] 🏇🏼 Refactoring (no functional changes, no api changes) | 1.0 | Add logging on repository, cors, and server - # **Add logging on repository, cors, and server**
**Issue type** :
- [x] 🤴 Code style update (formatting, renaming)
- [x] 🏇🏼 Refactoring (no functional changes, no api changes) | non_priority | add logging on repository cors and server add logging on repository cors and server issue type 🤴 code style update formatting renaming 🏇🏼 refactoring no functional changes no api changes | 0 |
477,684 | 13,766,373,003 | IssuesEvent | 2020-10-07 14:29:47 | ansible/awx | https://api.github.com/repos/ansible/awx | opened | Host details variables showing JSON format without indentation on load | component:ui_next priority:low state:needs_devel type:bug | <!-- Issues are for **concrete, actionable bugs and feature requests** only - if you're just asking for debugging help or technical support, please use:
- http://webchat.freenode.net/?channels=ansible-awx
- https://groups.google.com/forum/#!forum/awx-project
We have to limit this because of limited volunteer time to respond to issues! -->
##### ISSUE TYPE
- Bug Report
##### SUMMARY
Host details variables showing JSON format without indentation on load
##### ENVIRONMENT
* AWX version: 15.0.0
* AWX install method:docker for mac
* Ansible version: 2.9.13
* Operating System: Catalina
* Web Browser: Chrome
##### STEPS TO REPRODUCE
1. Navigate to Hosts
2. Select a host which has variables
##### EXPECTED RESULTS
The CodeMirror should show the JSON indented
##### ACTUAL RESULTS
The JSON is displayed without indentation
##### ADDITIONAL INFORMATION
| 1.0 | Host details variables showing JSON format without indentation on load - <!-- Issues are for **concrete, actionable bugs and feature requests** only - if you're just asking for debugging help or technical support, please use:
- http://webchat.freenode.net/?channels=ansible-awx
- https://groups.google.com/forum/#!forum/awx-project
We have to limit this because of limited volunteer time to respond to issues! -->
##### ISSUE TYPE
- Bug Report
##### SUMMARY
Host details variables showing JSON format without indentation on load
##### ENVIRONMENT
* AWX version: 15.0.0
* AWX install method:docker for mac
* Ansible version: 2.9.13
* Operating System: Catalina
* Web Browser: Chrome
##### STEPS TO REPRODUCE
1. Navigate to Hosts
2. Select a host which has variables
##### EXPECTED RESULTS
The CodeMirror should show the JSON indented
##### ACTUAL RESULTS
The JSON is displayed without indentation
##### ADDITIONAL INFORMATION
| priority | host details variables showing json format without indentation on load issues are for concrete actionable bugs and feature requests only if you re just asking for debugging help or technical support please use we have to limit this because of limited volunteer time to respond to issues issue type bug report summary host details variables showing json format without indentation on load environment awx version awx install method docker for mac ansible version operating system catalina web browser chrome steps to reproduce navigate to hosts select a host which has variables expected results the codemirror should show the json indented actual results the json is displayed without indentation additional information | 1 |
125,780 | 4,964,696,571 | IssuesEvent | 2016-12-03 22:25:43 | yairodriguez/uxmyths | https://api.github.com/repos/yairodriguez/uxmyths | opened | Myth 9 | [priority] high [status] accepted [type] feature | ### Description
Create the **Myth 9**, *Design has to be original*.
---
### Issue Checklist
- [ ] Write the needed tests.
- [ ] Create the markup for the component.
- [ ] Add the correct styles.
- [ ] Use the lint to clean `CSS` code.
- [ ] Document all things.
---
### Assignees
- [ ] Final assign @yairodriguez | 1.0 | Myth 9 - ### Description
Create the **Myth 9**, *Design has to be original*.
---
### Issue Checklist
- [ ] Write the needed tests.
- [ ] Create the markup for the component.
- [ ] Add the correct styles.
- [ ] Use the lint to clean `CSS` code.
- [ ] Document all things.
---
### Assignees
- [ ] Final assign @yairodriguez | priority | myth description create the myth design has to be original issue checklist write the needed tests create the markup for the component add the correct styles use the lint to clean css code document all things assignees final assign yairodriguez | 1 |
134,166 | 12,566,684,307 | IssuesEvent | 2020-06-08 11:40:21 | 20-1-SKKU-OSS/2020-1-OSS-8 | https://api.github.com/repos/20-1-SKKU-OSS/2020-1-OSS-8 | opened | [번역수정요청] imdb_fasttext.md | documentation | 번역 미완성:
- 첫 번째 표에서
-> Embedding : 임베딩
-> Accuracy, 5 epochs : 정확도, 5에폭
-> Speed (s/epoch) : 속도(초/에폭)
-> Hardware : 하드웨어
- 효율적인 embedding 층부터 시작 : 효율적인 임베딩 층부터 시작
- embeddings를 평균 낼 GlobalAveragePooling1D를 더하라 : 임베딩을 평균 낼
GlobalAveragePooling1D를 추가
번역 스타일:
- 단일 단위 출력 레이어에 반영하여 S자형으로 압착한다 : 단일 단위 출력 레이어에 반영하여 S자형
으로 압착
| 1.0 | [번역수정요청] imdb_fasttext.md - 번역 미완성:
- 첫 번째 표에서
-> Embedding : 임베딩
-> Accuracy, 5 epochs : 정확도, 5에폭
-> Speed (s/epoch) : 속도(초/에폭)
-> Hardware : 하드웨어
- 효율적인 embedding 층부터 시작 : 효율적인 임베딩 층부터 시작
- embeddings를 평균 낼 GlobalAveragePooling1D를 더하라 : 임베딩을 평균 낼
GlobalAveragePooling1D를 추가
번역 스타일:
- 단일 단위 출력 레이어에 반영하여 S자형으로 압착한다 : 단일 단위 출력 레이어에 반영하여 S자형
으로 압착
| non_priority | imdb fasttext md 번역 미완성 첫 번째 표에서 embedding 임베딩 accuracy epochs 정확도 speed s epoch 속도 초 에폭 hardware 하드웨어 효율적인 embedding 층부터 시작 효율적인 임베딩 층부터 시작 embeddings를 평균 낼 더하라 임베딩을 평균 낼 추가 번역 스타일 단일 단위 출력 레이어에 반영하여 s자형으로 압착한다 단일 단위 출력 레이어에 반영하여 s자형 으로 압착 | 0 |
41,989 | 5,413,677,503 | IssuesEvent | 2017-03-01 17:15:12 | openshift/origin | https://api.github.com/repos/openshift/origin | closed | flake: OVS generic should add and remove flows when nodes are added and removed | component/networking kind/test-flake priority/P1 | https://ci.openshift.redhat.com/jenkins/job/test_pr_origin_extended/1073/
/data/src/github.com/openshift/origin/test/extended/networking/ovs.go:150
Flows after deleting node should be same as before creating it
Expected
<bool>: false
to be true
/data/src/github.com/openshift/origin/test/extended/networking/ovs.go:149
| 1.0 | flake: OVS generic should add and remove flows when nodes are added and removed - https://ci.openshift.redhat.com/jenkins/job/test_pr_origin_extended/1073/
/data/src/github.com/openshift/origin/test/extended/networking/ovs.go:150
Flows after deleting node should be same as before creating it
Expected
<bool>: false
to be true
/data/src/github.com/openshift/origin/test/extended/networking/ovs.go:149
| non_priority | flake ovs generic should add and remove flows when nodes are added and removed data src github com openshift origin test extended networking ovs go flows after deleting node should be same as before creating it expected false to be true data src github com openshift origin test extended networking ovs go | 0 |
748,090 | 26,106,618,763 | IssuesEvent | 2022-12-27 14:01:29 | webcompat/web-bugs | https://api.github.com/repos/webcompat/web-bugs | closed | www.britannica.com - design is broken | browser-firefox priority-important engine-gecko | <!-- @browser: Firefox 108.0 -->
<!-- @ua_header: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:108.0) Gecko/20100101 Firefox/108.0 -->
<!-- @reported_with: unknown -->
<!-- @public_url: https://github.com/webcompat/web-bugs/issues/115895 -->
**URL**: https://www.britannica.com/topic/Flying-Spaghetti-Monster
**Browser / Version**: Firefox 108.0
**Operating System**: Windows 10
**Tested Another Browser**: Yes Edge
**Problem type**: Design is broken
**Description**: Images not loaded
**Steps to Reproduce**:
Just opened the page (problem is also on some other sites).
Some elements on the page (buttons made from images) are not shown as buttons but as alternate text.
<details>
<summary>View the screenshot</summary>
<img alt="Screenshot" src="https://webcompat.com/uploads/2022/12/da183dd7-a917-43c0-b501-ee7030c1e446.jpg">
</details>
<details>
<summary>Browser Configuration</summary>
<ul>
<li>None</li>
</ul>
</details>
_From [webcompat.com](https://webcompat.com/) with ❤️_ | 1.0 | www.britannica.com - design is broken - <!-- @browser: Firefox 108.0 -->
<!-- @ua_header: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:108.0) Gecko/20100101 Firefox/108.0 -->
<!-- @reported_with: unknown -->
<!-- @public_url: https://github.com/webcompat/web-bugs/issues/115895 -->
**URL**: https://www.britannica.com/topic/Flying-Spaghetti-Monster
**Browser / Version**: Firefox 108.0
**Operating System**: Windows 10
**Tested Another Browser**: Yes Edge
**Problem type**: Design is broken
**Description**: Images not loaded
**Steps to Reproduce**:
Just opened the page (problem is also on some other sites).
Some elements on the page (buttons made from images) are not shown as buttons but as alternate text.
<details>
<summary>View the screenshot</summary>
<img alt="Screenshot" src="https://webcompat.com/uploads/2022/12/da183dd7-a917-43c0-b501-ee7030c1e446.jpg">
</details>
<details>
<summary>Browser Configuration</summary>
<ul>
<li>None</li>
</ul>
</details>
_From [webcompat.com](https://webcompat.com/) with ❤️_ | priority | design is broken url browser version firefox operating system windows tested another browser yes edge problem type design is broken description images not loaded steps to reproduce just opened the page problem is also on some other sites some elements on the page buttons made from images are not shown as buttons but as alternate text view the screenshot img alt screenshot src browser configuration none from with ❤️ | 1 |
342,631 | 10,319,846,460 | IssuesEvent | 2019-08-30 18:41:13 | dasaderi/PIT_fellows_workgroup | https://api.github.com/repos/dasaderi/PIT_fellows_workgroup | closed | Steering committee members personal outreach | MozFest high_priority_level outreach | Everyone from the committee should reach out to their personal networks to share the survey. Please add bullet points as you plan your personal outreach.
- [x] Daniela to post on MoFo fellows' Slack
- [x] Reach out to Amel, Moz Science Fellow
- [x] Jen to send info out to Tech Exchange fellows
- [x] Becca to email the 2017-18 Mozilla fellows cohort
| 1.0 | Steering committee members personal outreach - Everyone from the committee should reach out to their personal networks to share the survey. Please add bullet points as you plan your personal outreach.
- [x] Daniela to post on MoFo fellows' Slack
- [x] Reach out to Amel, Moz Science Fellow
- [x] Jen to send info out to Tech Exchange fellows
- [x] Becca to email the 2017-18 Mozilla fellows cohort
| priority | steering committee members personal outreach everyone from the committee should reach out to their personal networks to share the survey please add bullet points as you plan your personal outreach daniela to post on mofo fellows slack reach out to amel moz science fellow jen to send info out to tech exchange fellows becca to email the mozilla fellows cohort | 1 |
42,487 | 2,870,846,344 | IssuesEvent | 2015-06-07 15:44:47 | FLEXIcontent/flexicontent-cck | https://api.github.com/repos/FLEXIcontent/flexicontent-cck | closed | Make search query parameters language independent | enhancement Priority Normal | As a suggestion, maybe the query parameter "searchword" could be something shorter and independent from any language, in order to avoid mixed languages urls. Maybe you can use the letter "q", such as used by Google: www.site.com/search?q=example
This was originally asked here:
http://www.flexicontent.org/forum/21-troubleshooting/53661-search-issues-with-languages-and-sef.html
Where you also commented:
"we would also want to possible replace our filter_NN= with e.g. q_fieldname in regards of field filters too" | 1.0 | Make search query parameters language independent - As a suggestion, maybe the query parameter "searchword" could be something shorter and independent from any language, in order to avoid mixed languages urls. Maybe you can use the letter "q", such as used by Google: www.site.com/search?q=example
This was originally asked here:
http://www.flexicontent.org/forum/21-troubleshooting/53661-search-issues-with-languages-and-sef.html
Where you also commented:
"we would also want to possible replace our filter_NN= with e.g. q_fieldname in regards of field filters too" | priority | make search query parameters language independent as a suggestion maybe the query parameter searchword could be something shorter and independent from any language in order to avoid mixed languages urls maybe you can use the letter q such as used by google this was originally asked here where you also commented we would also want to possible replace our filter nn with e g q fieldname in regards of field filters too | 1 |
443,340 | 30,885,600,838 | IssuesEvent | 2023-08-03 21:28:19 | AsmSafone/SafoneAPI | https://api.github.com/repos/AsmSafone/SafoneAPI | closed | Api call failed | bug documentation |
Traceback (most recent call last):
File "/app/Mr.Stark/Stark/__init__.py", line 83, in wrapper
return await func(client, message, *args, **kwargs)
File "/app/Mr.Stark/Stark/Plugins/translater.py", line 21, in translate_me
output = await api.translate(text, target=lang)
File "/opt/venv/lib/python3.8/site-packages/SafoneAPI/__init__.py", line 913, in translate
return await self._fetch("translate", text=text, origin=origin, target=target)
File "/opt/venv/lib/python3.8/site-packages/SafoneAPI/__init__.py", line 68, in _fetch
raise GenericApiError(
SafoneAPI.GenericApiError: Api Call Failed, Please report this: https://api.safone.me/report
| 1.0 | Api call failed -
Traceback (most recent call last):
File "/app/Mr.Stark/Stark/__init__.py", line 83, in wrapper
return await func(client, message, *args, **kwargs)
File "/app/Mr.Stark/Stark/Plugins/translater.py", line 21, in translate_me
output = await api.translate(text, target=lang)
File "/opt/venv/lib/python3.8/site-packages/SafoneAPI/__init__.py", line 913, in translate
return await self._fetch("translate", text=text, origin=origin, target=target)
File "/opt/venv/lib/python3.8/site-packages/SafoneAPI/__init__.py", line 68, in _fetch
raise GenericApiError(
SafoneAPI.GenericApiError: Api Call Failed, Please report this: https://api.safone.me/report
| non_priority | api call failed traceback most recent call last file app mr stark stark init py line in wrapper return await func client message args kwargs file app mr stark stark plugins translater py line in translate me output await api translate text target lang file opt venv lib site packages safoneapi init py line in translate return await self fetch translate text text origin origin target target file opt venv lib site packages safoneapi init py line in fetch raise genericapierror safoneapi genericapierror api call failed please report this | 0 |
12,867 | 8,026,063,006 | IssuesEvent | 2018-07-27 01:35:22 | tensorflow/tensorflow | https://api.github.com/repos/tensorflow/tensorflow | closed | TF hangs with distributed mode | stat:awaiting response type:bug/performance | ### System information
- **Have I written custom code (as opposed to using a stock example script provided in TensorFlow)**:
No
- **OS Platform and Distribution (e.g., Linux Ubuntu 16.04)**:
Linux Ubuntu 16.04
- **TensorFlow installed from (source or binary)**:
source
- **TensorFlow version (use command below)**:
1.5
- **Python version**:
2.7
- **Bazel version (if compiling from source)**:
0.5.4
- **GCC/Compiler version (if compiling from source)**:
5.4.0
- **CUDA/cuDNN version**:
9.0/7
- **GPU model and memory**:
TitanXP, 12G
- **Exact command to reproduce**:
### Describe the problem
When I run skip_thoughts model with distributed mode(2 workers in a machine, 2 GPUs per worker), tf hangs with linux condition variable error.
### Source code / logs
Below is the gdb log.
`Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
185 ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S: No such file or directory.
(gdb) bt
#0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1 0x00007fd44d2e891c in std::condition_variable::wait(std::unique_lock<std::mutex>&) () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#2 0x00007fd45b021ecb in nsync::nsync_mu_semaphore_p_with_deadline(nsync::nsync_semaphore_s_*, timespec) ()
from /home/soojeong/expdir_parallax/venv/local/lib/python2.7/site-packages/tensorflow/python/_pywrap_tensorflow_internal.so
#3 0x00007fd45b0217a1 in nsync::nsync_sem_wait_with_cancel_(nsync::waiter*, timespec, nsync::nsync_note_s_*) ()
from /home/soojeong/expdir_parallax/venv/local/lib/python2.7/site-packages/tensorflow/python/_pywrap_tensorflow_internal.so
#4 0x00007fd45b01ec12 in nsync::nsync_cv_wait_with_deadline_generic(nsync::nsync_cv_s_*, void*, void (*)(void*), void (*)(void*), timespec, nsync::nsync_note_s_*) ()
from /home/soojeong/expdir_parallax/venv/local/lib/python2.7/site-packages/tensorflow/python/_pywrap_tensorflow_internal.so
#5 0x00007fd45b01f0f3 in nsync::nsync_cv_wait_with_deadline(nsync::nsync_cv_s_*, nsync::nsync_mu_s_*, timespec, nsync::nsync_note_s_*) ()
from /home/soojeong/expdir_parallax/venv/local/lib/python2.7/site-packages/tensorflow/python/_pywrap_tensorflow_internal.so
#6 0x00007fd45879da1b in tensorflow::(anonymous namespace)::WaitForNotification(tensorflow::CallOptions*, long long, tensorflow::Notification*) ()
from /home/soojeong/expdir_parallax/venv/local/lib/python2.7/site-packages/tensorflow/python/_pywrap_tensorflow_internal.so
#7 0x00007fd45879e313 in tensorflow::LocalMaster::RunStep(tensorflow::CallOptions*, tensorflow::RunStepRequestWrapper*, tensorflow::MutableRunStepResponseWrapper*) ()
from /home/soojeong/expdir_parallax/venv/local/lib/python2.7/site-packages/tensorflow/python/_pywrap_tensorflow_internal.so`
| True | TF hangs with distributed mode - ### System information
- **Have I written custom code (as opposed to using a stock example script provided in TensorFlow)**:
No
- **OS Platform and Distribution (e.g., Linux Ubuntu 16.04)**:
Linux Ubuntu 16.04
- **TensorFlow installed from (source or binary)**:
source
- **TensorFlow version (use command below)**:
1.5
- **Python version**:
2.7
- **Bazel version (if compiling from source)**:
0.5.4
- **GCC/Compiler version (if compiling from source)**:
5.4.0
- **CUDA/cuDNN version**:
9.0/7
- **GPU model and memory**:
TitanXP, 12G
- **Exact command to reproduce**:
### Describe the problem
When I run skip_thoughts model with distributed mode(2 workers in a machine, 2 GPUs per worker), tf hangs with linux condition variable error.
### Source code / logs
Below is the gdb log.
`Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
185 ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S: No such file or directory.
(gdb) bt
#0 pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1 0x00007fd44d2e891c in std::condition_variable::wait(std::unique_lock<std::mutex>&) () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#2 0x00007fd45b021ecb in nsync::nsync_mu_semaphore_p_with_deadline(nsync::nsync_semaphore_s_*, timespec) ()
from /home/soojeong/expdir_parallax/venv/local/lib/python2.7/site-packages/tensorflow/python/_pywrap_tensorflow_internal.so
#3 0x00007fd45b0217a1 in nsync::nsync_sem_wait_with_cancel_(nsync::waiter*, timespec, nsync::nsync_note_s_*) ()
from /home/soojeong/expdir_parallax/venv/local/lib/python2.7/site-packages/tensorflow/python/_pywrap_tensorflow_internal.so
#4 0x00007fd45b01ec12 in nsync::nsync_cv_wait_with_deadline_generic(nsync::nsync_cv_s_*, void*, void (*)(void*), void (*)(void*), timespec, nsync::nsync_note_s_*) ()
from /home/soojeong/expdir_parallax/venv/local/lib/python2.7/site-packages/tensorflow/python/_pywrap_tensorflow_internal.so
#5 0x00007fd45b01f0f3 in nsync::nsync_cv_wait_with_deadline(nsync::nsync_cv_s_*, nsync::nsync_mu_s_*, timespec, nsync::nsync_note_s_*) ()
from /home/soojeong/expdir_parallax/venv/local/lib/python2.7/site-packages/tensorflow/python/_pywrap_tensorflow_internal.so
#6 0x00007fd45879da1b in tensorflow::(anonymous namespace)::WaitForNotification(tensorflow::CallOptions*, long long, tensorflow::Notification*) ()
from /home/soojeong/expdir_parallax/venv/local/lib/python2.7/site-packages/tensorflow/python/_pywrap_tensorflow_internal.so
#7 0x00007fd45879e313 in tensorflow::LocalMaster::RunStep(tensorflow::CallOptions*, tensorflow::RunStepRequestWrapper*, tensorflow::MutableRunStepResponseWrapper*) ()
from /home/soojeong/expdir_parallax/venv/local/lib/python2.7/site-packages/tensorflow/python/_pywrap_tensorflow_internal.so`
| non_priority | tf hangs with distributed mode system information have i written custom code as opposed to using a stock example script provided in tensorflow no os platform and distribution e g linux ubuntu linux ubuntu tensorflow installed from source or binary source tensorflow version use command below python version bazel version if compiling from source gcc compiler version if compiling from source cuda cudnn version gpu model and memory titanxp exact command to reproduce describe the problem when i run skip thoughts model with distributed mode workers in a machine gpus per worker tf hangs with linux condition variable error source code logs below is the gdb log using host libthread db library lib linux gnu libthread db so pthread cond wait glibc at sysdeps unix sysv linux pthread cond wait s sysdeps unix sysv linux pthread cond wait s no such file or directory gdb bt pthread cond wait glibc at sysdeps unix sysv linux pthread cond wait s in std condition variable wait std unique lock from usr lib linux gnu libstdc so in nsync nsync mu semaphore p with deadline nsync nsync semaphore s timespec from home soojeong expdir parallax venv local lib site packages tensorflow python pywrap tensorflow internal so in nsync nsync sem wait with cancel nsync waiter timespec nsync nsync note s from home soojeong expdir parallax venv local lib site packages tensorflow python pywrap tensorflow internal so in nsync nsync cv wait with deadline generic nsync nsync cv s void void void void void timespec nsync nsync note s from home soojeong expdir parallax venv local lib site packages tensorflow python pywrap tensorflow internal so in nsync nsync cv wait with deadline nsync nsync cv s nsync nsync mu s timespec nsync nsync note s from home soojeong expdir parallax venv local lib site packages tensorflow python pywrap tensorflow internal so in tensorflow anonymous namespace waitfornotification tensorflow calloptions long long tensorflow notification from home soojeong expdir parallax venv local lib site packages tensorflow python pywrap tensorflow internal so in tensorflow localmaster runstep tensorflow calloptions tensorflow runsteprequestwrapper tensorflow mutablerunstepresponsewrapper from home soojeong expdir parallax venv local lib site packages tensorflow python pywrap tensorflow internal so | 0 |
66,575 | 14,788,934,074 | IssuesEvent | 2021-01-12 09:53:42 | andygonzalez2010/store | https://api.github.com/repos/andygonzalez2010/store | opened | CVE-2020-13822 (High) detected in elliptic-6.4.1.tgz | security vulnerability | ## CVE-2020-13822 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>elliptic-6.4.1.tgz</b></p></summary>
<p>EC cryptography</p>
<p>Library home page: <a href="https://registry.npmjs.org/elliptic/-/elliptic-6.4.1.tgz">https://registry.npmjs.org/elliptic/-/elliptic-6.4.1.tgz</a></p>
<p>Path to dependency file: store/package.json</p>
<p>Path to vulnerable library: store/node_modules/elliptic/package.json</p>
<p>
Dependency Hierarchy:
- webpack-4.28.4.tgz (Root Library)
- node-libs-browser-2.2.0.tgz
- crypto-browserify-3.12.0.tgz
- browserify-sign-4.0.4.tgz
- :x: **elliptic-6.4.1.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/andygonzalez2010/store/commit/3f6d614029f4d6cfdddfcef8468949cb7822503c">3f6d614029f4d6cfdddfcef8468949cb7822503c</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
The Elliptic package 6.5.2 for Node.js allows ECDSA signature malleability via variations in encoding, leading '\0' bytes, or integer overflows. This could conceivably have a security-relevant impact if an application relied on a single canonical signature.
<p>Publish Date: 2020-06-04
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-13822>CVE-2020-13822</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.7</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: 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/indutny/elliptic/tree/v6.5.3">https://github.com/indutny/elliptic/tree/v6.5.3</a></p>
<p>Release Date: 2020-06-04</p>
<p>Fix Resolution: v6.5.3</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | CVE-2020-13822 (High) detected in elliptic-6.4.1.tgz - ## CVE-2020-13822 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>elliptic-6.4.1.tgz</b></p></summary>
<p>EC cryptography</p>
<p>Library home page: <a href="https://registry.npmjs.org/elliptic/-/elliptic-6.4.1.tgz">https://registry.npmjs.org/elliptic/-/elliptic-6.4.1.tgz</a></p>
<p>Path to dependency file: store/package.json</p>
<p>Path to vulnerable library: store/node_modules/elliptic/package.json</p>
<p>
Dependency Hierarchy:
- webpack-4.28.4.tgz (Root Library)
- node-libs-browser-2.2.0.tgz
- crypto-browserify-3.12.0.tgz
- browserify-sign-4.0.4.tgz
- :x: **elliptic-6.4.1.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/andygonzalez2010/store/commit/3f6d614029f4d6cfdddfcef8468949cb7822503c">3f6d614029f4d6cfdddfcef8468949cb7822503c</a></p>
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
The Elliptic package 6.5.2 for Node.js allows ECDSA signature malleability via variations in encoding, leading '\0' bytes, or integer overflows. This could conceivably have a security-relevant impact if an application relied on a single canonical signature.
<p>Publish Date: 2020-06-04
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-13822>CVE-2020-13822</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.7</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: 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/indutny/elliptic/tree/v6.5.3">https://github.com/indutny/elliptic/tree/v6.5.3</a></p>
<p>Release Date: 2020-06-04</p>
<p>Fix Resolution: v6.5.3</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_priority | cve high detected in elliptic tgz cve high severity vulnerability vulnerable library elliptic tgz ec cryptography library home page a href path to dependency file store package json path to vulnerable library store node modules elliptic package json dependency hierarchy webpack tgz root library node libs browser tgz crypto browserify tgz browserify sign tgz x elliptic tgz vulnerable library found in head commit a href found in base branch master vulnerability details the elliptic package for node js allows ecdsa signature malleability via variations in encoding leading bytes or integer overflows this could conceivably have a security relevant impact if an application relied on a single canonical signature publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity high privileges required none user interaction none scope unchanged impact metrics confidentiality impact high integrity impact high availability impact low 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 |
235,446 | 7,738,595,807 | IssuesEvent | 2018-05-28 12:40:11 | Ybalrid/virtual-air-hockey | https://api.github.com/repos/Ybalrid/virtual-air-hockey | closed | Fix falcon collision feedback for player 2 | 1st priority Networking Novint related Physics stuff bug | Right now the player 2 doesn't get proper collision. I suggest adding the collision information to the packets stent by the server. Since we trust server's physics.
| 1.0 | Fix falcon collision feedback for player 2 - Right now the player 2 doesn't get proper collision. I suggest adding the collision information to the packets stent by the server. Since we trust server's physics.
| priority | fix falcon collision feedback for player right now the player doesn t get proper collision i suggest adding the collision information to the packets stent by the server since we trust server s physics | 1 |
690,054 | 23,644,410,986 | IssuesEvent | 2022-08-25 20:24:31 | WarwickAI/wai-platform-v2 | https://api.github.com/repos/WarwickAI/wai-platform-v2 | closed | Add date field to events | enhancement high-priority | For Tutorials and Talks, this will be the date of the event.
For Courses and Project, this will be the starting date of the event.
Can be shown in the `extraInfo` section on the cards, and beneath the heading on the page. | 1.0 | Add date field to events - For Tutorials and Talks, this will be the date of the event.
For Courses and Project, this will be the starting date of the event.
Can be shown in the `extraInfo` section on the cards, and beneath the heading on the page. | priority | add date field to events for tutorials and talks this will be the date of the event for courses and project this will be the starting date of the event can be shown in the extrainfo section on the cards and beneath the heading on the page | 1 |
610,393 | 18,906,447,922 | IssuesEvent | 2021-11-16 09:35:44 | craftercms/craftercms | https://api.github.com/repos/craftercms/craftercms | closed | [studio-ui] Icons are being displayed larger than intended | bug priority: medium | ### Bug Report
#### Crafter CMS Version
```
Studio Version Number: 4.0.0-SNAPSHOT-7c6989
Build Number: 7c69897050e62b929364876f4f1cb0e6f9c191bc
Build Date: 29/10/2021, 1:36 pm
```
#### Describe the bug
Icons on PathNav and AddressBar components (possibly other places, please review thoroughly) are displayed larger than intended.
#### To Reproduce
Compare the sizes of the icons on the PathNav or the AddressBar with the PathNavTree. The intended size is the one on the PathNavTree (e.g. templates).
#### Screenshots
<img width="239" alt="image" src="https://user-images.githubusercontent.com/3928341/140478446-ef1ca3c6-89d1-477d-b543-bcdd03a76075.png">
| 1.0 | [studio-ui] Icons are being displayed larger than intended - ### Bug Report
#### Crafter CMS Version
```
Studio Version Number: 4.0.0-SNAPSHOT-7c6989
Build Number: 7c69897050e62b929364876f4f1cb0e6f9c191bc
Build Date: 29/10/2021, 1:36 pm
```
#### Describe the bug
Icons on PathNav and AddressBar components (possibly other places, please review thoroughly) are displayed larger than intended.
#### To Reproduce
Compare the sizes of the icons on the PathNav or the AddressBar with the PathNavTree. The intended size is the one on the PathNavTree (e.g. templates).
#### Screenshots
<img width="239" alt="image" src="https://user-images.githubusercontent.com/3928341/140478446-ef1ca3c6-89d1-477d-b543-bcdd03a76075.png">
| priority | icons are being displayed larger than intended bug report crafter cms version studio version number snapshot build number build date pm describe the bug icons on pathnav and addressbar components possibly other places please review thoroughly are displayed larger than intended to reproduce compare the sizes of the icons on the pathnav or the addressbar with the pathnavtree the intended size is the one on the pathnavtree e g templates screenshots img width alt image src | 1 |
499,218 | 14,443,176,587 | IssuesEvent | 2020-12-07 19:14:59 | cloudfoundry-incubator/kubecf | https://api.github.com/repos/cloudfoundry-incubator/kubecf | closed | Enabling the autoscaler feature restarts credhub and uaa | Priority: Medium Status: Not A Bug Type: Bug | **Describe the bug**
I installed kubecf with `make kubecf-apply` (uses Diego). Pushed and tested 12factor sample app.
Then upgraded via `FEATURE_AUTOSCALER=1 make kubecf-apply`. This first restarted both `bosh-dns` pods, which may be necessary (I don't know). But then it also stopped `credhub` and `uaa`, which should not be affected.
Eventually `credhub` and `uaa` come back, and all autoscaler pods start, and everything seems fine. The 12factor app remained accessible during the whole time.
**Expected behavior**
I expect `credhub` and `uaa` not to be restarted when the only requested change is enabling autoscaler.
| 1.0 | Enabling the autoscaler feature restarts credhub and uaa - **Describe the bug**
I installed kubecf with `make kubecf-apply` (uses Diego). Pushed and tested 12factor sample app.
Then upgraded via `FEATURE_AUTOSCALER=1 make kubecf-apply`. This first restarted both `bosh-dns` pods, which may be necessary (I don't know). But then it also stopped `credhub` and `uaa`, which should not be affected.
Eventually `credhub` and `uaa` come back, and all autoscaler pods start, and everything seems fine. The 12factor app remained accessible during the whole time.
**Expected behavior**
I expect `credhub` and `uaa` not to be restarted when the only requested change is enabling autoscaler.
| priority | enabling the autoscaler feature restarts credhub and uaa describe the bug i installed kubecf with make kubecf apply uses diego pushed and tested sample app then upgraded via feature autoscaler make kubecf apply this first restarted both bosh dns pods which may be necessary i don t know but then it also stopped credhub and uaa which should not be affected eventually credhub and uaa come back and all autoscaler pods start and everything seems fine the app remained accessible during the whole time expected behavior i expect credhub and uaa not to be restarted when the only requested change is enabling autoscaler | 1 |
196,972 | 22,572,025,280 | IssuesEvent | 2022-06-28 01:47:49 | xlizaluizax/datocms-Vue.js---DatoCMS---DatingWIKI | https://api.github.com/repos/xlizaluizax/datocms-Vue.js---DatoCMS---DatingWIKI | opened | CVE-2021-42740 (High) detected in shell-quote-1.7.2.tgz | security vulnerability | ## CVE-2021-42740 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>shell-quote-1.7.2.tgz</b></p></summary>
<p>quote and parse shell commands</p>
<p>Library home page: <a href="https://registry.npmjs.org/shell-quote/-/shell-quote-1.7.2.tgz">https://registry.npmjs.org/shell-quote/-/shell-quote-1.7.2.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/shell-quote/package.json</p>
<p>
Dependency Hierarchy:
- cli-plugin-babel-4.2.3.tgz (Root Library)
- cli-shared-utils-4.2.3.tgz
- launch-editor-2.2.1.tgz
- :x: **shell-quote-1.7.2.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/xlizaluizax/datocms-Vue.js---DatoCMS---DatingWIKI/commit/4bd03db9e49918a230ca87828b997a7380cb1b7e">4bd03db9e49918a230ca87828b997a7380cb1b7e</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 shell-quote package before 1.7.3 for Node.js allows command injection. An attacker can inject unescaped shell metacharacters through a regex designed to support Windows drive letters. If the output of this package is passed to a real shell as a quoted argument to a command with exec(), an attacker can inject arbitrary commands. This is because the Windows drive letter regex character class is {A-z] instead of the correct {A-Za-z]. Several shell metacharacters exist in the space between capital letter Z and lower case letter a, such as the backtick character.
<p>Publish Date: 2021-10-21
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-42740>CVE-2021-42740</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-2021-42740">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-42740</a></p>
<p>Release Date: 2021-10-21</p>
<p>Fix Resolution: shell-quote - 1.7.3</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-42740 (High) detected in shell-quote-1.7.2.tgz - ## CVE-2021-42740 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>shell-quote-1.7.2.tgz</b></p></summary>
<p>quote and parse shell commands</p>
<p>Library home page: <a href="https://registry.npmjs.org/shell-quote/-/shell-quote-1.7.2.tgz">https://registry.npmjs.org/shell-quote/-/shell-quote-1.7.2.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/shell-quote/package.json</p>
<p>
Dependency Hierarchy:
- cli-plugin-babel-4.2.3.tgz (Root Library)
- cli-shared-utils-4.2.3.tgz
- launch-editor-2.2.1.tgz
- :x: **shell-quote-1.7.2.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/xlizaluizax/datocms-Vue.js---DatoCMS---DatingWIKI/commit/4bd03db9e49918a230ca87828b997a7380cb1b7e">4bd03db9e49918a230ca87828b997a7380cb1b7e</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 shell-quote package before 1.7.3 for Node.js allows command injection. An attacker can inject unescaped shell metacharacters through a regex designed to support Windows drive letters. If the output of this package is passed to a real shell as a quoted argument to a command with exec(), an attacker can inject arbitrary commands. This is because the Windows drive letter regex character class is {A-z] instead of the correct {A-Za-z]. Several shell metacharacters exist in the space between capital letter Z and lower case letter a, such as the backtick character.
<p>Publish Date: 2021-10-21
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-42740>CVE-2021-42740</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-2021-42740">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-42740</a></p>
<p>Release Date: 2021-10-21</p>
<p>Fix Resolution: shell-quote - 1.7.3</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 shell quote tgz cve high severity vulnerability vulnerable library shell quote tgz quote and parse shell commands library home page a href path to dependency file package json path to vulnerable library node modules shell quote package json dependency hierarchy cli plugin babel tgz root library cli shared utils tgz launch editor tgz x shell quote tgz vulnerable library found in head commit a href vulnerability details the shell quote package before for node js allows command injection an attacker can inject unescaped shell metacharacters through a regex designed to support windows drive letters if the output of this package is passed to a real shell as a quoted argument to a command with exec an attacker can inject arbitrary commands this is because the windows drive letter regex character class is a z instead of the correct a za z several shell metacharacters exist in the space between capital letter z and lower case letter a such as the backtick character 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 shell quote step up your open source security game with mend | 0 |
343,332 | 30,658,508,809 | IssuesEvent | 2023-07-25 13:39:32 | stockOneQ/back | https://api.github.com/repos/stockOneQ/back | closed | 제품 목록 조회 API 구현 및 제품 CRUD 쿼리를 픽스한다 | 🐞 BugFix 📬 API 🔨 Refactor ✅ Test ✨ Feature | ## Description 🖊️
- 제품 목록 조회 API를 구현한다
- 모든 조회는 가나다순 및 빈도순 두 가지 경우로 나뉘며, 기본 정렬은 가나다순으로 한다
## To-do 🧑💻
- [ ] 전체 목록 조회
- [ ] 유통기한 경과 목록 조회
- [ ] 유통기한 임박 목록 조회
- [ ] 재고 부족 목록 조회
- [ ] 분류 기준별 제품 갯수 조회
| 1.0 | 제품 목록 조회 API 구현 및 제품 CRUD 쿼리를 픽스한다 - ## Description 🖊️
- 제품 목록 조회 API를 구현한다
- 모든 조회는 가나다순 및 빈도순 두 가지 경우로 나뉘며, 기본 정렬은 가나다순으로 한다
## To-do 🧑💻
- [ ] 전체 목록 조회
- [ ] 유통기한 경과 목록 조회
- [ ] 유통기한 임박 목록 조회
- [ ] 재고 부족 목록 조회
- [ ] 분류 기준별 제품 갯수 조회
| non_priority | 제품 목록 조회 api 구현 및 제품 crud 쿼리를 픽스한다 description 🖊️ 제품 목록 조회 api를 구현한다 모든 조회는 가나다순 및 빈도순 두 가지 경우로 나뉘며 기본 정렬은 가나다순으로 한다 to do 🧑💻 전체 목록 조회 유통기한 경과 목록 조회 유통기한 임박 목록 조회 재고 부족 목록 조회 분류 기준별 제품 갯수 조회 | 0 |
709,032 | 24,365,653,485 | IssuesEvent | 2022-10-03 14:58:49 | NCAR/wrfcloud | https://api.github.com/repos/NCAR/wrfcloud | opened | Add workflow manager to runtime components | priority: low alert: NEED MORE DEFINITION component: NWP components | ## Describe the New Feature ##
Consider adding a workflow manager, e.g. ecflow or rocoto, to the runtime components to help manage the monitoring and job dependencies.
### Acceptance Testing ###
*List input data types and sources.*
*Describe tests required for new functionality.*
### Time Estimate ###
*Estimate the amount of work required here.*
*Issues should represent approximately 1 to 3 days of work.*
### Sub-Issues ###
Consider breaking the new feature down into sub-issues.
- [ ] *Add a checkbox for each sub-issue here.*
### Relevant Deadlines ###
*List relevant project deadlines here or state NONE.*
## Define the Metadata ##
### Assignee ###
- [ ] Select **engineer(s)** or **no engineer** required
- [ ] Select **scientist(s)** or **no scientist** required
### Labels ###
- [ ] Select **component(s)**
- [ ] Select **priority**
### Projects and Milestone ###
- [ ] Select **Project**
- [ ] Select **Milestone** as the next official version or **Backlog of Development Ideas**
## New Feature Checklist ##
- [ ] Complete the issue definition above, including the **Time Estimate** and **Funding source**.
- [ ] Fork this repository or create a branch of **develop**.
Branch name: `feature_<Issue Number>/<Description>`
- [ ] Complete the development and test your changes.
- [ ] Add/update log messages for easier debugging.
- [ ] Add/update tests.
- [ ] Add/update documentation.
- [ ] Push local changes to GitHub.
- [ ] Submit a pull request to merge into **develop**.
Pull request: `feature <Issue Number> <Description>`
- [ ] Define the pull request metadata, as permissions allow.
Select: **Reviewer(s)**, **Project**, and **Development** issue
Select: **Milestone** as the next official version
- [ ] Iterate until the reviewer(s) accept and merge your changes.
- [ ] Delete your fork or branch.
- [ ] Close this issue.
| 1.0 | Add workflow manager to runtime components - ## Describe the New Feature ##
Consider adding a workflow manager, e.g. ecflow or rocoto, to the runtime components to help manage the monitoring and job dependencies.
### Acceptance Testing ###
*List input data types and sources.*
*Describe tests required for new functionality.*
### Time Estimate ###
*Estimate the amount of work required here.*
*Issues should represent approximately 1 to 3 days of work.*
### Sub-Issues ###
Consider breaking the new feature down into sub-issues.
- [ ] *Add a checkbox for each sub-issue here.*
### Relevant Deadlines ###
*List relevant project deadlines here or state NONE.*
## Define the Metadata ##
### Assignee ###
- [ ] Select **engineer(s)** or **no engineer** required
- [ ] Select **scientist(s)** or **no scientist** required
### Labels ###
- [ ] Select **component(s)**
- [ ] Select **priority**
### Projects and Milestone ###
- [ ] Select **Project**
- [ ] Select **Milestone** as the next official version or **Backlog of Development Ideas**
## New Feature Checklist ##
- [ ] Complete the issue definition above, including the **Time Estimate** and **Funding source**.
- [ ] Fork this repository or create a branch of **develop**.
Branch name: `feature_<Issue Number>/<Description>`
- [ ] Complete the development and test your changes.
- [ ] Add/update log messages for easier debugging.
- [ ] Add/update tests.
- [ ] Add/update documentation.
- [ ] Push local changes to GitHub.
- [ ] Submit a pull request to merge into **develop**.
Pull request: `feature <Issue Number> <Description>`
- [ ] Define the pull request metadata, as permissions allow.
Select: **Reviewer(s)**, **Project**, and **Development** issue
Select: **Milestone** as the next official version
- [ ] Iterate until the reviewer(s) accept and merge your changes.
- [ ] Delete your fork or branch.
- [ ] Close this issue.
| priority | add workflow manager to runtime components describe the new feature consider adding a workflow manager e g ecflow or rocoto to the runtime components to help manage the monitoring and job dependencies acceptance testing list input data types and sources describe tests required for new functionality time estimate estimate the amount of work required here issues should represent approximately to days of work sub issues consider breaking the new feature down into sub issues add a checkbox for each sub issue here relevant deadlines list relevant project deadlines here or state none define the metadata assignee select engineer s or no engineer required select scientist s or no scientist required labels select component s select priority projects and milestone select project select milestone as the next official version or backlog of development ideas new feature checklist complete the issue definition above including the time estimate and funding source fork this repository or create a branch of develop branch name feature complete the development and test your changes add update log messages for easier debugging add update tests add update documentation push local changes to github submit a pull request to merge into develop pull request feature define the pull request metadata as permissions allow select reviewer s project and development issue select milestone as the next official version iterate until the reviewer s accept and merge your changes delete your fork or branch close this issue | 1 |
103,903 | 22,498,693,413 | IssuesEvent | 2022-06-23 09:49:03 | Onelinerhub/onelinerhub | https://api.github.com/repos/Onelinerhub/onelinerhub | closed | Short solution needed: "How to convert yyyymmdd string to datetime" (python-pandas) | help wanted good first issue code python-pandas | Please help us write most modern and shortest code solution for this issue:
**How to convert yyyymmdd string to datetime** (technology: [python-pandas](https://onelinerhub.com/python-pandas))
### Fast way
Just write the code solution in the comments.
### Prefered way
1. Create pull request with a new code file inside [inbox folder](https://github.com/Onelinerhub/onelinerhub/tree/main/inbox).
2. Don't forget to use comments to make solution explained.
3. Link to this issue in comments of pull request. | 1.0 | Short solution needed: "How to convert yyyymmdd string to datetime" (python-pandas) - Please help us write most modern and shortest code solution for this issue:
**How to convert yyyymmdd string to datetime** (technology: [python-pandas](https://onelinerhub.com/python-pandas))
### Fast way
Just write the code solution in the comments.
### Prefered way
1. Create pull request with a new code file inside [inbox folder](https://github.com/Onelinerhub/onelinerhub/tree/main/inbox).
2. Don't forget to use comments to make solution explained.
3. Link to this issue in comments of pull request. | non_priority | short solution needed how to convert yyyymmdd string to datetime python pandas please help us write most modern and shortest code solution for this issue how to convert yyyymmdd string to datetime technology fast way just write the code solution in the comments prefered way create pull request with a new code file inside don t forget to use comments to make solution explained link to this issue in comments of pull request | 0 |
306,326 | 9,383,995,024 | IssuesEvent | 2019-04-05 06:29:07 | ntop/ntopng | https://api.github.com/repos/ntop/ntopng | opened | (Almost) Useless SSL Alerts Certificate Mismatch | bug priority ticket | 
The above alert is almost useless as it is not clear what is the problem being reported. Please list
- requested client certificate
- offered server certificates | 1.0 | (Almost) Useless SSL Alerts Certificate Mismatch - 
The above alert is almost useless as it is not clear what is the problem being reported. Please list
- requested client certificate
- offered server certificates | priority | almost useless ssl alerts certificate mismatch the above alert is almost useless as it is not clear what is the problem being reported please list requested client certificate offered server certificates | 1 |
804,733 | 29,498,670,325 | IssuesEvent | 2023-06-02 19:23:28 | googleapis/nodejs-pubsub | https://api.github.com/repos/googleapis/nodejs-pubsub | closed | Add sample for pubsub_commit_avro_schema | type: feature request api: pubsub priority: p3 samples | This is a Node sample for schema revisions.
ref: 266567049
| 1.0 | Add sample for pubsub_commit_avro_schema - This is a Node sample for schema revisions.
ref: 266567049
| priority | add sample for pubsub commit avro schema this is a node sample for schema revisions ref | 1 |
385,125 | 11,413,015,669 | IssuesEvent | 2020-02-01 16:55:51 | elninotech/uppload | https://api.github.com/repos/elninotech/uppload | closed | Uppload hangs while uploading PDFs | bug good first issue high-priority | When I upload images, everything works. But, when I upload pdfs of any size, it hangs on the "uploading" screen.
The `before-upload` event does fire. No error event fires. No error message is ever displayed. No XHR request is ever made to the backend. The `settingsFunction` never fires.
I have the following configuration
```ts
const uppload = new Uppload({
lang: en,
defaultService: "local",
uploader: xhrUploader({
responseKey: "file",
endpoint: `${process.env.API_URL}/attachments`,
settingsFunction(xmlHttp) {
console.log("do i get to settingsFunc");
xmlHttp.setRequestHeader("authorization", Auth.getToken());
},
})
});
uppload.use([
new Local({
mimeTypes: ["image/png", "image/jpeg", "image/gif", "application/pdf"]
})
]);
uppload.on("*", console.log);
```
I attached an event emitter to all events and got the following console output
| 1.0 | Uppload hangs while uploading PDFs - When I upload images, everything works. But, when I upload pdfs of any size, it hangs on the "uploading" screen.
The `before-upload` event does fire. No error event fires. No error message is ever displayed. No XHR request is ever made to the backend. The `settingsFunction` never fires.
I have the following configuration
```ts
const uppload = new Uppload({
lang: en,
defaultService: "local",
uploader: xhrUploader({
responseKey: "file",
endpoint: `${process.env.API_URL}/attachments`,
settingsFunction(xmlHttp) {
console.log("do i get to settingsFunc");
xmlHttp.setRequestHeader("authorization", Auth.getToken());
},
})
});
uppload.use([
new Local({
mimeTypes: ["image/png", "image/jpeg", "image/gif", "application/pdf"]
})
]);
uppload.on("*", console.log);
```
I attached an event emitter to all events and got the following console output
| priority | uppload hangs while uploading pdfs when i upload images everything works but when i upload pdfs of any size it hangs on the uploading screen the before upload event does fire no error event fires no error message is ever displayed no xhr request is ever made to the backend the settingsfunction never fires i have the following configuration ts const uppload new uppload lang en defaultservice local uploader xhruploader responsekey file endpoint process env api url attachments settingsfunction xmlhttp console log do i get to settingsfunc xmlhttp setrequestheader authorization auth gettoken uppload use new local mimetypes uppload on console log i attached an event emitter to all events and got the following console output | 1 |
111,110 | 17,012,566,050 | IssuesEvent | 2021-07-02 07:31:26 | longhorn/longhorn | https://api.github.com/repos/longhorn/longhorn | opened | [TASK] Regularly rebuild with the updated package/security patch to catch vulnerability issues earlier | area/package area/security kind/task | **What's the task? Please describe.**
As titled, one of the best practices to protect the images from exposure of vulnerabilities is to regularly update the install packages from the base image. Need to make sure we update the packages when building new images.
**Describe the items of the task (DoD, definition of done) you'd like.**
- [ ] update the installed packages when building images for all components
**Additional context**
N/A
| True | [TASK] Regularly rebuild with the updated package/security patch to catch vulnerability issues earlier - **What's the task? Please describe.**
As titled, one of the best practices to protect the images from exposure of vulnerabilities is to regularly update the install packages from the base image. Need to make sure we update the packages when building new images.
**Describe the items of the task (DoD, definition of done) you'd like.**
- [ ] update the installed packages when building images for all components
**Additional context**
N/A
| non_priority | regularly rebuild with the updated package security patch to catch vulnerability issues earlier what s the task please describe as titled one of the best practices to protect the images from exposure of vulnerabilities is to regularly update the install packages from the base image need to make sure we update the packages when building new images describe the items of the task dod definition of done you d like update the installed packages when building images for all components additional context n a | 0 |
157,577 | 6,008,757,547 | IssuesEvent | 2017-06-06 08:46:16 | lxde/lxqt | https://api.github.com/repos/lxde/lxqt | closed | Some widgets can not be themed | low-priority lxqt-panel qss/themes | Maybe Im missing something, but this are some little issues I have found while theming:
**LXQT Runner**
The searh results (QListView or "commandList") use the system theme, but still refuses to be styled with the lxqt-runner.qss. The last update did not change this, or I did not notice how to do it.
**Panel Plugins**
Show Desktop, Screen Saver, Volume and Mount seems to have a fixed size. If you change the size of the panel to 60px you will see that this widgets stay in a same size while all the others expand with the panel. This leads to them having non clickable areas. This happen also with the old themes.
I have been lurking the code searching for a way to change this behavior. From the stylesheets the only thing that seems to work is to put "height: 100%" but this is not necesary with other widgets (and this lead to other glitches), so I think that there must be something wrong with this plugins.
| 1.0 | Some widgets can not be themed - Maybe Im missing something, but this are some little issues I have found while theming:
**LXQT Runner**
The searh results (QListView or "commandList") use the system theme, but still refuses to be styled with the lxqt-runner.qss. The last update did not change this, or I did not notice how to do it.
**Panel Plugins**
Show Desktop, Screen Saver, Volume and Mount seems to have a fixed size. If you change the size of the panel to 60px you will see that this widgets stay in a same size while all the others expand with the panel. This leads to them having non clickable areas. This happen also with the old themes.
I have been lurking the code searching for a way to change this behavior. From the stylesheets the only thing that seems to work is to put "height: 100%" but this is not necesary with other widgets (and this lead to other glitches), so I think that there must be something wrong with this plugins.
| priority | some widgets can not be themed maybe im missing something but this are some little issues i have found while theming lxqt runner the searh results qlistview or commandlist use the system theme but still refuses to be styled with the lxqt runner qss the last update did not change this or i did not notice how to do it panel plugins show desktop screen saver volume and mount seems to have a fixed size if you change the size of the panel to you will see that this widgets stay in a same size while all the others expand with the panel this leads to them having non clickable areas this happen also with the old themes i have been lurking the code searching for a way to change this behavior from the stylesheets the only thing that seems to work is to put height but this is not necesary with other widgets and this lead to other glitches so i think that there must be something wrong with this plugins | 1 |
405,006 | 27,500,831,771 | IssuesEvent | 2023-03-05 17:23:18 | hotosm/fmtm | https://api.github.com/repos/hotosm/fmtm | opened | Add documentation for React frontend | documentation Priority: Should have | Currently the React frontend is undocumented.
We should describe:
- The Microfrontend configuration.
- How to set up the development environment.
- How to contribute to the frontend.
- How it is deployed in production.
Pages should be added to the /docs directory via PR. They will be automatically published on the Wiki via CI. | 1.0 | Add documentation for React frontend - Currently the React frontend is undocumented.
We should describe:
- The Microfrontend configuration.
- How to set up the development environment.
- How to contribute to the frontend.
- How it is deployed in production.
Pages should be added to the /docs directory via PR. They will be automatically published on the Wiki via CI. | non_priority | add documentation for react frontend currently the react frontend is undocumented we should describe the microfrontend configuration how to set up the development environment how to contribute to the frontend how it is deployed in production pages should be added to the docs directory via pr they will be automatically published on the wiki via ci | 0 |
433,376 | 12,505,736,366 | IssuesEvent | 2020-06-02 11:17:35 | gitcoinco/web | https://api.github.com/repos/gitcoinco/web | closed | UX when an issue is kicked back to open | Gitcoin Bounties To Define priority: ungroomed | (not ready to be worked on)
From Seiron on chat:
> What about the issues where someone started working but they got reopened due to lack of progress? They have usually an unrealistic rest period of time to finish them. Is there a solution to add some more time to it? There are some issues with only some days left. What happens with this issues? Gone forever? (edited)
| 1.0 | UX when an issue is kicked back to open - (not ready to be worked on)
From Seiron on chat:
> What about the issues where someone started working but they got reopened due to lack of progress? They have usually an unrealistic rest period of time to finish them. Is there a solution to add some more time to it? There are some issues with only some days left. What happens with this issues? Gone forever? (edited)
| priority | ux when an issue is kicked back to open not ready to be worked on from seiron on chat what about the issues where someone started working but they got reopened due to lack of progress they have usually an unrealistic rest period of time to finish them is there a solution to add some more time to it there are some issues with only some days left what happens with this issues gone forever edited | 1 |
108,649 | 4,348,901,515 | IssuesEvent | 2016-07-30 06:49:04 | k-bx/boilerpipe | https://api.github.com/repos/k-bx/boilerpipe | closed | Featurerequest: Run boilerpipe as a command line tool | auto-migrated Priority-Medium Type-Enhancement | ```
Is it possible to use Boilerpipe as a CLI app together with other bash
commands, e.g. extract the text of an entire website with a command like:
wget -p http://mysite.com | boilerplate -options > file#.html
```
Original issue reported on code.google.com by `haraldgr...@gmail.com` on 22 Mar 2011 at 3:26 | 1.0 | Featurerequest: Run boilerpipe as a command line tool - ```
Is it possible to use Boilerpipe as a CLI app together with other bash
commands, e.g. extract the text of an entire website with a command like:
wget -p http://mysite.com | boilerplate -options > file#.html
```
Original issue reported on code.google.com by `haraldgr...@gmail.com` on 22 Mar 2011 at 3:26 | priority | featurerequest run boilerpipe as a command line tool is it possible to use boilerpipe as a cli app together with other bash commands e g extract the text of an entire website with a command like wget p boilerplate options file html original issue reported on code google com by haraldgr gmail com on mar at | 1 |
209,098 | 7,165,224,819 | IssuesEvent | 2018-01-29 13:51:18 | dkpro/dkpro-tc | https://api.github.com/repos/dkpro/dkpro-tc | closed | Handling "empty" predictions in the evaluation module | Priority-Medium bug | Originally reported on Google Code with ID 231
```
In several places, the evaluation module currently assumes that, for each instance,
there is one or more labels (strings or integers) for both gold standard and prediction.
Due to particularities in the machine learning frameworks (see Issue 228), this might
not always be the case.
One solution might be to check for empty predictions right when the evaluation file
(id2outcome) is first read, and replace empty strings with a dedicated constant and
integer (e.g. "-1").
```
Reported by `daxenberger.j` on 2015-01-26 08:48:04
| 1.0 | Handling "empty" predictions in the evaluation module - Originally reported on Google Code with ID 231
```
In several places, the evaluation module currently assumes that, for each instance,
there is one or more labels (strings or integers) for both gold standard and prediction.
Due to particularities in the machine learning frameworks (see Issue 228), this might
not always be the case.
One solution might be to check for empty predictions right when the evaluation file
(id2outcome) is first read, and replace empty strings with a dedicated constant and
integer (e.g. "-1").
```
Reported by `daxenberger.j` on 2015-01-26 08:48:04
| priority | handling empty predictions in the evaluation module originally reported on google code with id in several places the evaluation module currently assumes that for each instance there is one or more labels strings or integers for both gold standard and prediction due to particularities in the machine learning frameworks see issue this might not always be the case one solution might be to check for empty predictions right when the evaluation file is first read and replace empty strings with a dedicated constant and integer e g reported by daxenberger j on | 1 |
566,633 | 16,825,839,923 | IssuesEvent | 2021-06-17 18:26:45 | GoogleCloudPlatform/golang-samples | https://api.github.com/repos/GoogleCloudPlatform/golang-samples | closed | asset/quickstart/export-assets-bigquery: TestMain failed | api: cloudasset flakybot: flaky flakybot: issue priority: p2 samples type: bug | This test failed!
To configure my behavior, see [the Flaky Bot documentation](https://github.com/googleapis/repo-automation-bots/tree/master/packages/flakybot).
If I'm commenting on this issue too often, add the `flakybot: quiet` label and
I will stop commenting.
---
commit: 8106ae9058e916342aa0a1e376a7729d429ec1b9
buildURL: [Build Status](https://source.cloud.google.com/results/invocations/5d07e974-6f4e-46d7-8871-db32fe18673c), [Sponge](http://sponge2/5d07e974-6f4e-46d7-8871-db32fe18673c)
status: failed | 1.0 | asset/quickstart/export-assets-bigquery: TestMain failed - This test failed!
To configure my behavior, see [the Flaky Bot documentation](https://github.com/googleapis/repo-automation-bots/tree/master/packages/flakybot).
If I'm commenting on this issue too often, add the `flakybot: quiet` label and
I will stop commenting.
---
commit: 8106ae9058e916342aa0a1e376a7729d429ec1b9
buildURL: [Build Status](https://source.cloud.google.com/results/invocations/5d07e974-6f4e-46d7-8871-db32fe18673c), [Sponge](http://sponge2/5d07e974-6f4e-46d7-8871-db32fe18673c)
status: failed | priority | asset quickstart export assets bigquery testmain failed this test failed to configure my behavior see if i m commenting on this issue too often add the flakybot quiet label and i will stop commenting commit buildurl status failed | 1 |
114,421 | 4,630,881,727 | IssuesEvent | 2016-09-28 14:06:10 | mantidproject/mantid | https://api.github.com/repos/mantidproject/mantid | closed | Fix ISIS Indirect Inelastic system tests for GSL2 | Component: Fitting Component: Indirect Inelastic Priority: High | Tests failing with GSL2: http://builds.mantidproject.org/job/master_systemtests-ubuntu-16.04/21/testReport/
Fix the Indirect Inelastic related ones (or split into more issues/tickets):
- SystemTests.ISISIndirectInelastic.IRISIqtAndIqtFit
- SystemTests.ISISIndirectInelastic.OSIRISIqtAndIqtFit
- SystemTests.ISISIndirectInelastic.IRISConvFit
- SystemTests.ISISIndirectInelastic.IRISIqtAndIqtFitMulti
- SystemTests.ISISIndirectInelastic.OSIRISConvFit
- SystemTests.ISISIndirectInelastic.OSIRISIqtAndIqtFitMulti
| 1.0 | Fix ISIS Indirect Inelastic system tests for GSL2 - Tests failing with GSL2: http://builds.mantidproject.org/job/master_systemtests-ubuntu-16.04/21/testReport/
Fix the Indirect Inelastic related ones (or split into more issues/tickets):
- SystemTests.ISISIndirectInelastic.IRISIqtAndIqtFit
- SystemTests.ISISIndirectInelastic.OSIRISIqtAndIqtFit
- SystemTests.ISISIndirectInelastic.IRISConvFit
- SystemTests.ISISIndirectInelastic.IRISIqtAndIqtFitMulti
- SystemTests.ISISIndirectInelastic.OSIRISConvFit
- SystemTests.ISISIndirectInelastic.OSIRISIqtAndIqtFitMulti
| priority | fix isis indirect inelastic system tests for tests failing with fix the indirect inelastic related ones or split into more issues tickets systemtests isisindirectinelastic irisiqtandiqtfit systemtests isisindirectinelastic osirisiqtandiqtfit systemtests isisindirectinelastic irisconvfit systemtests isisindirectinelastic irisiqtandiqtfitmulti systemtests isisindirectinelastic osirisconvfit systemtests isisindirectinelastic osirisiqtandiqtfitmulti | 1 |
206,216 | 16,022,104,330 | IssuesEvent | 2021-04-21 02:05:31 | ChessAdventure/client | https://api.github.com/repos/ChessAdventure/client | closed | Back to dashboard button on game screen | documentation | **Description:**
- Add a button that leaves the game and redirects to the dashboard
- This will probably have to clear the extension (gameId) from state because the existence of that redirects to dashboard
| 1.0 | Back to dashboard button on game screen - **Description:**
- Add a button that leaves the game and redirects to the dashboard
- This will probably have to clear the extension (gameId) from state because the existence of that redirects to dashboard
| non_priority | back to dashboard button on game screen description add a button that leaves the game and redirects to the dashboard this will probably have to clear the extension gameid from state because the existence of that redirects to dashboard | 0 |
217,802 | 16,889,449,403 | IssuesEvent | 2021-06-23 07:24:52 | WoWManiaUK/Redemption | https://api.github.com/repos/WoWManiaUK/Redemption | closed | Unkillable High Priest Hawinni | Fixed on PTR - Ready to Test | **Links:**
https://www.wow-mania.com/armory/?quest=12674
**What is Happening:**
After being subjected to the [Quetz'lun's Hexxing Stick], and having the animation of "Exploding", he stays immortal and keeps attacking the player.
After walking away from the mob, he instantly resets his position, and returns to before being affected by the quest item.
**What Should happen:**
The mob should be considered "Dead"
and have it's corpose dissapear properly
[Attachment 1. Showing hitting the mob after effect of the quest-item.]
[Attachment 2. Showing the mob hitting player, while staying alive.]
| 1.0 | Unkillable High Priest Hawinni - **Links:**
https://www.wow-mania.com/armory/?quest=12674
**What is Happening:**
After being subjected to the [Quetz'lun's Hexxing Stick], and having the animation of "Exploding", he stays immortal and keeps attacking the player.
After walking away from the mob, he instantly resets his position, and returns to before being affected by the quest item.
**What Should happen:**
The mob should be considered "Dead"
and have it's corpose dissapear properly
[Attachment 1. Showing hitting the mob after effect of the quest-item.]
[Attachment 2. Showing the mob hitting player, while staying alive.]
| non_priority | unkillable high priest hawinni links what is happening after being subjected to the and having the animation of exploding he stays immortal and keeps attacking the player after walking away from the mob he instantly resets his position and returns to before being affected by the quest item what should happen the mob should be considered dead and have it s corpose dissapear properly | 0 |
198,905 | 22,674,185,211 | IssuesEvent | 2022-07-04 01:25:30 | Techini/WebGoat | https://api.github.com/repos/Techini/WebGoat | closed | CVE-2021-21343 (High) detected in xstream-1.4.5.jar - autoclosed | security vulnerability | ## CVE-2021-21343 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>xstream-1.4.5.jar</b></p></summary>
<p>XStream is a serialization library from Java objects to XML and back.</p>
<p>Path to dependency file: /webgoat-lessons/vulnerable-components/pom.xml</p>
<p>Path to vulnerable library: /m2/repository/com/thoughtworks/xstream/xstream/1.4.5/xstream-1.4.5.jar,/home/wss-scanner/.m2/repository/com/thoughtworks/xstream/xstream/1.4.5/xstream-1.4.5.jar,/home/wss-scanner/.m2/repository/com/thoughtworks/xstream/xstream/1.4.5/xstream-1.4.5.jar</p>
<p>
Dependency Hierarchy:
- :x: **xstream-1.4.5.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/Techini/WebGoat/commit/d33cc0e32a0d1b949ff1b85af16890cd452276f8">d33cc0e32a0d1b949ff1b85af16890cd452276f8</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
XStream is a Java library to serialize objects to XML and back again. In XStream before version 1.4.16, there is a vulnerability where the processed stream at unmarshalling time contains type information to recreate the formerly written objects. XStream creates therefore new instances based on these type information. An attacker can manipulate the processed input stream and replace or inject objects, that result in the deletion of a file on the local host. No user is affected, who followed the recommendation to setup XStream's security framework with a whitelist limited to the minimal required types. If you rely on XStream's default blacklist of the Security Framework, you will have to use at least version 1.4.16.
<p>Publish Date: 2021-03-23
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-21343>CVE-2021-21343</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: High
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/x-stream/xstream/security/advisories/GHSA-74cv-f58x-f9wf">https://github.com/x-stream/xstream/security/advisories/GHSA-74cv-f58x-f9wf</a></p>
<p>Release Date: 2021-03-23</p>
<p>Fix Resolution: com.thoughtworks.xstream:xstream:1.4.16</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | CVE-2021-21343 (High) detected in xstream-1.4.5.jar - autoclosed - ## CVE-2021-21343 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>xstream-1.4.5.jar</b></p></summary>
<p>XStream is a serialization library from Java objects to XML and back.</p>
<p>Path to dependency file: /webgoat-lessons/vulnerable-components/pom.xml</p>
<p>Path to vulnerable library: /m2/repository/com/thoughtworks/xstream/xstream/1.4.5/xstream-1.4.5.jar,/home/wss-scanner/.m2/repository/com/thoughtworks/xstream/xstream/1.4.5/xstream-1.4.5.jar,/home/wss-scanner/.m2/repository/com/thoughtworks/xstream/xstream/1.4.5/xstream-1.4.5.jar</p>
<p>
Dependency Hierarchy:
- :x: **xstream-1.4.5.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/Techini/WebGoat/commit/d33cc0e32a0d1b949ff1b85af16890cd452276f8">d33cc0e32a0d1b949ff1b85af16890cd452276f8</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
XStream is a Java library to serialize objects to XML and back again. In XStream before version 1.4.16, there is a vulnerability where the processed stream at unmarshalling time contains type information to recreate the formerly written objects. XStream creates therefore new instances based on these type information. An attacker can manipulate the processed input stream and replace or inject objects, that result in the deletion of a file on the local host. No user is affected, who followed the recommendation to setup XStream's security framework with a whitelist limited to the minimal required types. If you rely on XStream's default blacklist of the Security Framework, you will have to use at least version 1.4.16.
<p>Publish Date: 2021-03-23
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-21343>CVE-2021-21343</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: High
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/x-stream/xstream/security/advisories/GHSA-74cv-f58x-f9wf">https://github.com/x-stream/xstream/security/advisories/GHSA-74cv-f58x-f9wf</a></p>
<p>Release Date: 2021-03-23</p>
<p>Fix Resolution: com.thoughtworks.xstream:xstream:1.4.16</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_priority | cve high detected in xstream jar autoclosed cve high severity vulnerability vulnerable library xstream jar xstream is a serialization library from java objects to xml and back path to dependency file webgoat lessons vulnerable components pom xml path to vulnerable library repository com thoughtworks xstream xstream xstream jar home wss scanner repository com thoughtworks xstream xstream xstream jar home wss scanner repository com thoughtworks xstream xstream xstream jar dependency hierarchy x xstream jar vulnerable library found in head commit a href vulnerability details xstream is a java library to serialize objects to xml and back again in xstream before version there is a vulnerability where the processed stream at unmarshalling time contains type information to recreate the formerly written objects xstream creates therefore new instances based on these type information an attacker can manipulate the processed input stream and replace or inject objects that result in the deletion of a file on the local host no user is affected who followed the recommendation to setup xstream s security framework with a whitelist limited to the minimal required types if you rely on xstream s default blacklist of the security framework you will have to use at least version publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact none integrity impact high availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution com thoughtworks xstream xstream step up your open source security game with whitesource | 0 |
499,574 | 14,450,422,441 | IssuesEvent | 2020-12-08 09:34:01 | myConsciousness/entity-validator | https://api.github.com/repos/myConsciousness/entity-validator | opened | コンテンツフレームワークを使用しない期待値の指定方式に関する仕様策定 | Priority: high Type: new feature | # Add New Feature
## 1. Feature details
コンテンツフレームワークを使用しないアノテーションへ期待値を指定する方式に関する仕様を策定する。
## 2. Why it is necessary
機能拡張に伴う新規機能の実装。
## 3. How to implement
期待値をアノテーションへ直接指定できる機能を実装する。
## 4. References
| 1.0 | コンテンツフレームワークを使用しない期待値の指定方式に関する仕様策定 - # Add New Feature
## 1. Feature details
コンテンツフレームワークを使用しないアノテーションへ期待値を指定する方式に関する仕様を策定する。
## 2. Why it is necessary
機能拡張に伴う新規機能の実装。
## 3. How to implement
期待値をアノテーションへ直接指定できる機能を実装する。
## 4. References
| priority | コンテンツフレームワークを使用しない期待値の指定方式に関する仕様策定 add new feature feature details コンテンツフレームワークを使用しないアノテーションへ期待値を指定する方式に関する仕様を策定する。 why it is necessary 機能拡張に伴う新規機能の実装。 how to implement 期待値をアノテーションへ直接指定できる機能を実装する。 references | 1 |
194,819 | 6,899,517,119 | IssuesEvent | 2017-11-24 14:08:07 | highcharts/highcharts | https://api.github.com/repos/highcharts/highcharts | closed | One data label not showing. | Bug Priority:Low | When I create a stack bar chart, and choose the stacked bars to be horizontally, along with the labels showing on the stacked bars, one data label is not being displayed.
As shown in the snapshot,
The data label(value) is not shown on stacked bar .
If any other legend is hidden, then the data label on the stacked bar will be displayed correctly.The snapshot is given below.
After again making all the legends enable, the data label will still be displayed.Please refer to the snapshot below.
But after saving the chart, that particular data label is again not displayed on stacked bar
If the legend values are also displayed along with the legends, then the datalabel is displayed.Please refer to the attachment below.
| 1.0 | One data label not showing. - When I create a stack bar chart, and choose the stacked bars to be horizontally, along with the labels showing on the stacked bars, one data label is not being displayed.
As shown in the snapshot,
The data label(value) is not shown on stacked bar .
If any other legend is hidden, then the data label on the stacked bar will be displayed correctly.The snapshot is given below.
After again making all the legends enable, the data label will still be displayed.Please refer to the snapshot below.
But after saving the chart, that particular data label is again not displayed on stacked bar
If the legend values are also displayed along with the legends, then the datalabel is displayed.Please refer to the attachment below.
| priority | one data label not showing when i create a stack bar chart and choose the stacked bars to be horizontally along with the labels showing on the stacked bars one data label is not being displayed as shown in the snapshot the data label value is not shown on stacked bar if any other legend is hidden then the data label on the stacked bar will be displayed correctly the snapshot is given below after again making all the legends enable the data label will still be displayed please refer to the snapshot below but after saving the chart that particular data label is again not displayed on stacked bar if the legend values are also displayed along with the legends then the datalabel is displayed please refer to the attachment below | 1 |
312,343 | 9,546,160,048 | IssuesEvent | 2019-05-01 19:06:49 | poanetwork/nifty-wallet | https://api.github.com/repos/poanetwork/nifty-wallet | opened | Change POA Network -> POA Core | enhancement medium priority | POA Network is too generic, and it refers more to the project as whole. POA Core is more accurate description of the network | 1.0 | Change POA Network -> POA Core - POA Network is too generic, and it refers more to the project as whole. POA Core is more accurate description of the network | priority | change poa network poa core poa network is too generic and it refers more to the project as whole poa core is more accurate description of the network | 1 |
452,583 | 13,056,095,143 | IssuesEvent | 2020-07-30 03:38:33 | kubeflow/pipelines | https://api.github.com/repos/kubeflow/pipelines | closed | kfp.Client: Can't specify localhost host | area/sdk/client kind/bug priority/p2 status/triaged | ### What steps did you take:
```
client = kfp.Client(host="http://localhost:8888")
...
client.upload_pipeline(filename, name, description)
```
### What happened:
```
Traceback (most recent call last):
File "../kubeflow-apply/kubeflow-apply.py", line 73, in <module>
args.func()
File "../kubeflow-apply/kubeflow-apply.py", line 33, in pipelines
self.client.upload_pipeline(filename, name, description)
File "/usr/local/lib/python3.8/site-packages/kfp/_client.py", line 723, in upload_pipeline
response = self._upload_api.upload_pipeline(pipeline_package_path, name=pipeline_name, description=description)
File "/usr/local/lib/python3.8/site-packages/kfp_server_api/api/pipeline_upload_service_api.py", line 83, in upload_pipeline
return self.upload_pipeline_with_http_info(uploadfile, **kwargs) # noqa: E501
File "/usr/local/lib/python3.8/site-packages/kfp_server_api/api/pipeline_upload_service_api.py", line 177, in upload_pipeline_with_http_info
return self.api_client.call_api(
File "/usr/local/lib/python3.8/site-packages/kfp_server_api/api_client.py", line 379, in call_api
return self.__call_api(resource_path, method,
File "/usr/local/lib/python3.8/site-packages/kfp_server_api/api_client.py", line 196, in __call_api
response_data = self.request(
File "/usr/local/lib/python3.8/site-packages/kfp_server_api/api_client.py", line 422, in request
return self.rest_client.POST(url,
File "/usr/local/lib/python3.8/site-packages/kfp_server_api/rest.py", line 279, in POST
return self.request("POST", url,
File "/usr/local/lib/python3.8/site-packages/kfp_server_api/rest.py", line 196, in request
r = self.pool_manager.request(
File "/usr/local/lib/python3.8/site-packages/urllib3/request.py", line 79, in request
return self.request_encode_body(
File "/usr/local/lib/python3.8/site-packages/urllib3/request.py", line 172, in request_encode_body
return self.urlopen(method, url, **extra_kw)
File "/usr/local/lib/python3.8/site-packages/urllib3/poolmanager.py", line 326, in urlopen
conn = self.connection_from_host(u.host, port=u.port, scheme=u.scheme)
File "/usr/local/lib/python3.8/site-packages/urllib3/poolmanager.py", line 231, in connection_from_host
raise LocationValueError("No host specified.")
urllib3.exceptions.LocationValueError: No host specified.
```
### What did you expect to happen:
Being able to specify the host
### Environment:
KFP SDK version: 1.0.0
### Anything else you would like to add:
The problem is that for unclear reasons kfp strips the schema from the url, causing urllib3's parse_url to interpret the 'localhost' part as schema. This was working with kfp==0.1.31 | 1.0 | kfp.Client: Can't specify localhost host - ### What steps did you take:
```
client = kfp.Client(host="http://localhost:8888")
...
client.upload_pipeline(filename, name, description)
```
### What happened:
```
Traceback (most recent call last):
File "../kubeflow-apply/kubeflow-apply.py", line 73, in <module>
args.func()
File "../kubeflow-apply/kubeflow-apply.py", line 33, in pipelines
self.client.upload_pipeline(filename, name, description)
File "/usr/local/lib/python3.8/site-packages/kfp/_client.py", line 723, in upload_pipeline
response = self._upload_api.upload_pipeline(pipeline_package_path, name=pipeline_name, description=description)
File "/usr/local/lib/python3.8/site-packages/kfp_server_api/api/pipeline_upload_service_api.py", line 83, in upload_pipeline
return self.upload_pipeline_with_http_info(uploadfile, **kwargs) # noqa: E501
File "/usr/local/lib/python3.8/site-packages/kfp_server_api/api/pipeline_upload_service_api.py", line 177, in upload_pipeline_with_http_info
return self.api_client.call_api(
File "/usr/local/lib/python3.8/site-packages/kfp_server_api/api_client.py", line 379, in call_api
return self.__call_api(resource_path, method,
File "/usr/local/lib/python3.8/site-packages/kfp_server_api/api_client.py", line 196, in __call_api
response_data = self.request(
File "/usr/local/lib/python3.8/site-packages/kfp_server_api/api_client.py", line 422, in request
return self.rest_client.POST(url,
File "/usr/local/lib/python3.8/site-packages/kfp_server_api/rest.py", line 279, in POST
return self.request("POST", url,
File "/usr/local/lib/python3.8/site-packages/kfp_server_api/rest.py", line 196, in request
r = self.pool_manager.request(
File "/usr/local/lib/python3.8/site-packages/urllib3/request.py", line 79, in request
return self.request_encode_body(
File "/usr/local/lib/python3.8/site-packages/urllib3/request.py", line 172, in request_encode_body
return self.urlopen(method, url, **extra_kw)
File "/usr/local/lib/python3.8/site-packages/urllib3/poolmanager.py", line 326, in urlopen
conn = self.connection_from_host(u.host, port=u.port, scheme=u.scheme)
File "/usr/local/lib/python3.8/site-packages/urllib3/poolmanager.py", line 231, in connection_from_host
raise LocationValueError("No host specified.")
urllib3.exceptions.LocationValueError: No host specified.
```
### What did you expect to happen:
Being able to specify the host
### Environment:
KFP SDK version: 1.0.0
### Anything else you would like to add:
The problem is that for unclear reasons kfp strips the schema from the url, causing urllib3's parse_url to interpret the 'localhost' part as schema. This was working with kfp==0.1.31 | priority | kfp client can t specify localhost host what steps did you take client kfp client host client upload pipeline filename name description what happened traceback most recent call last file kubeflow apply kubeflow apply py line in args func file kubeflow apply kubeflow apply py line in pipelines self client upload pipeline filename name description file usr local lib site packages kfp client py line in upload pipeline response self upload api upload pipeline pipeline package path name pipeline name description description file usr local lib site packages kfp server api api pipeline upload service api py line in upload pipeline return self upload pipeline with http info uploadfile kwargs noqa file usr local lib site packages kfp server api api pipeline upload service api py line in upload pipeline with http info return self api client call api file usr local lib site packages kfp server api api client py line in call api return self call api resource path method file usr local lib site packages kfp server api api client py line in call api response data self request file usr local lib site packages kfp server api api client py line in request return self rest client post url file usr local lib site packages kfp server api rest py line in post return self request post url file usr local lib site packages kfp server api rest py line in request r self pool manager request file usr local lib site packages request py line in request return self request encode body file usr local lib site packages request py line in request encode body return self urlopen method url extra kw file usr local lib site packages poolmanager py line in urlopen conn self connection from host u host port u port scheme u scheme file usr local lib site packages poolmanager py line in connection from host raise locationvalueerror no host specified exceptions locationvalueerror no host specified what did you expect to happen being able to specify the host environment kfp sdk version anything else you would like to add the problem is that for unclear reasons kfp strips the schema from the url causing s parse url to interpret the localhost part as schema this was working with kfp | 1 |
29,138 | 8,299,839,399 | IssuesEvent | 2018-09-21 05:31:51 | envoyproxy/envoy | https://api.github.com/repos/envoyproxy/envoy | reopened | Use lld as linker | build help wanted | As a part of tool chain revisit (#4159, #4158) and also as a part of (#3741). We should consider use [LLD](https://lld.llvm.org/) as default linker. LLD is at least twice faster than gold linker, we have more than 300 test target to link so this will improve CI performance.
Options:
1. Use lld everywhere (it works with gcc)
2. Use lld where clang is used (sanitizers)
A sample benchmark of linking `envoy-static` is here:
gold w/o threads (current):
`12.01s user 1.32s system 99% cpu 13.358 total`
gold w/ threads:
`14.24s user 6.97s system 180% cpu 11.762 total`
lld w/o threads:
`3.63s user 1.15s system 99% cpu 4.805 total`
lld w/ threads:
`8.64s user 11.24s system 709% cpu 2.802 total` | 1.0 | Use lld as linker - As a part of tool chain revisit (#4159, #4158) and also as a part of (#3741). We should consider use [LLD](https://lld.llvm.org/) as default linker. LLD is at least twice faster than gold linker, we have more than 300 test target to link so this will improve CI performance.
Options:
1. Use lld everywhere (it works with gcc)
2. Use lld where clang is used (sanitizers)
A sample benchmark of linking `envoy-static` is here:
gold w/o threads (current):
`12.01s user 1.32s system 99% cpu 13.358 total`
gold w/ threads:
`14.24s user 6.97s system 180% cpu 11.762 total`
lld w/o threads:
`3.63s user 1.15s system 99% cpu 4.805 total`
lld w/ threads:
`8.64s user 11.24s system 709% cpu 2.802 total` | non_priority | use lld as linker as a part of tool chain revisit and also as a part of we should consider use as default linker lld is at least twice faster than gold linker we have more than test target to link so this will improve ci performance options use lld everywhere it works with gcc use lld where clang is used sanitizers a sample benchmark of linking envoy static is here gold w o threads current user system cpu total gold w threads user system cpu total lld w o threads user system cpu total lld w threads user system cpu total | 0 |
342,117 | 10,312,205,361 | IssuesEvent | 2019-08-29 19:16:15 | CCAFS/MARLO | https://api.github.com/repos/CCAFS/MARLO | closed | Adjust Innovations section in the CGIAR Results Dashboard | Priority - High Type -Task | Adjust Innovations interface and graph filters to include 2018 data.
Tasks:
- [x] Interface.
- [x] Add new graphs.
- [x] Modify and add new chart filters.
**Deliverable:** Section in testing environment.
**Move to Review when:** Not applicable.
**Move to Closed when:** Section is released in testing environment. | 1.0 | Adjust Innovations section in the CGIAR Results Dashboard - Adjust Innovations interface and graph filters to include 2018 data.
Tasks:
- [x] Interface.
- [x] Add new graphs.
- [x] Modify and add new chart filters.
**Deliverable:** Section in testing environment.
**Move to Review when:** Not applicable.
**Move to Closed when:** Section is released in testing environment. | priority | adjust innovations section in the cgiar results dashboard adjust innovations interface and graph filters to include data tasks interface add new graphs modify and add new chart filters deliverable section in testing environment move to review when not applicable move to closed when section is released in testing environment | 1 |
102,195 | 16,548,284,910 | IssuesEvent | 2021-05-28 04:36:00 | samq-ghdemo/Java-Demo | https://api.github.com/repos/samq-ghdemo/Java-Demo | opened | CVE-2016-2510 (High) detected in bsh-core-2.0b4.jar | security vulnerability | ## CVE-2016-2510 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>bsh-core-2.0b4.jar</b></p></summary>
<p>BeanShell core</p>
<p>Path to dependency file: Java-Demo/pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/org/beanshell/bsh-core/2.0b4/bsh-core-2.0b4.jar,Java-Demo/target/easybuggy-1-SNAPSHOT/WEB-INF/lib/bsh-core-2.0b4.jar,Java-Demo/.extract/webapps/ROOT/WEB-INF/lib/bsh-core-2.0b4.jar</p>
<p>
Dependency Hierarchy:
- :x: **bsh-core-2.0b4.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/samq-ghdemo/Java-Demo/commit/ebe5ad9510b919e1dd226c70afc5e1115136f8cf">ebe5ad9510b919e1dd226c70afc5e1115136f8cf</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
BeanShell (bsh) before 2.0b6, when included on the classpath by an application that uses Java serialization or XStream, allows remote attackers to execute arbitrary code via crafted serialized data, related to XThis.Handler.
<p>Publish Date: 2016-04-07
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2016-2510>CVE-2016-2510</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>8.1</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://nvd.nist.gov/vuln/detail/CVE-2016-2510">https://nvd.nist.gov/vuln/detail/CVE-2016-2510</a></p>
<p>Release Date: 2016-04-07</p>
<p>Fix Resolution: 2.0b6</p>
</p>
</details>
<p></p>
***
<!-- REMEDIATE-OPEN-PR-START -->
- [ ] Check this box to open an automated fix PR
<!-- REMEDIATE-OPEN-PR-END -->
<!-- <REMEDIATE>{"isOpenPROnVulnerability":false,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"Java","groupId":"org.beanshell","packageName":"bsh-core","packageVersion":"2.0b4","packageFilePaths":["/pom.xml"],"isTransitiveDependency":false,"dependencyTree":"org.beanshell:bsh-core:2.0b4","isMinimumFixVersionAvailable":true,"minimumFixVersion":"2.0b6"}],"baseBranches":["main"],"vulnerabilityIdentifier":"CVE-2016-2510","vulnerabilityDetails":"BeanShell (bsh) before 2.0b6, when included on the classpath by an application that uses Java serialization or XStream, allows remote attackers to execute arbitrary code via crafted serialized data, related to XThis.Handler.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2016-2510","cvss3Severity":"high","cvss3Score":"8.1","cvss3Metrics":{"A":"High","AC":"High","PR":"None","S":"Unchanged","C":"High","UI":"None","AV":"Network","I":"High"},"extraData":{}}</REMEDIATE> --> | True | CVE-2016-2510 (High) detected in bsh-core-2.0b4.jar - ## CVE-2016-2510 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>bsh-core-2.0b4.jar</b></p></summary>
<p>BeanShell core</p>
<p>Path to dependency file: Java-Demo/pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/org/beanshell/bsh-core/2.0b4/bsh-core-2.0b4.jar,Java-Demo/target/easybuggy-1-SNAPSHOT/WEB-INF/lib/bsh-core-2.0b4.jar,Java-Demo/.extract/webapps/ROOT/WEB-INF/lib/bsh-core-2.0b4.jar</p>
<p>
Dependency Hierarchy:
- :x: **bsh-core-2.0b4.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/samq-ghdemo/Java-Demo/commit/ebe5ad9510b919e1dd226c70afc5e1115136f8cf">ebe5ad9510b919e1dd226c70afc5e1115136f8cf</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
BeanShell (bsh) before 2.0b6, when included on the classpath by an application that uses Java serialization or XStream, allows remote attackers to execute arbitrary code via crafted serialized data, related to XThis.Handler.
<p>Publish Date: 2016-04-07
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2016-2510>CVE-2016-2510</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>8.1</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://nvd.nist.gov/vuln/detail/CVE-2016-2510">https://nvd.nist.gov/vuln/detail/CVE-2016-2510</a></p>
<p>Release Date: 2016-04-07</p>
<p>Fix Resolution: 2.0b6</p>
</p>
</details>
<p></p>
***
<!-- REMEDIATE-OPEN-PR-START -->
- [ ] Check this box to open an automated fix PR
<!-- REMEDIATE-OPEN-PR-END -->
<!-- <REMEDIATE>{"isOpenPROnVulnerability":false,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"Java","groupId":"org.beanshell","packageName":"bsh-core","packageVersion":"2.0b4","packageFilePaths":["/pom.xml"],"isTransitiveDependency":false,"dependencyTree":"org.beanshell:bsh-core:2.0b4","isMinimumFixVersionAvailable":true,"minimumFixVersion":"2.0b6"}],"baseBranches":["main"],"vulnerabilityIdentifier":"CVE-2016-2510","vulnerabilityDetails":"BeanShell (bsh) before 2.0b6, when included on the classpath by an application that uses Java serialization or XStream, allows remote attackers to execute arbitrary code via crafted serialized data, related to XThis.Handler.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2016-2510","cvss3Severity":"high","cvss3Score":"8.1","cvss3Metrics":{"A":"High","AC":"High","PR":"None","S":"Unchanged","C":"High","UI":"None","AV":"Network","I":"High"},"extraData":{}}</REMEDIATE> --> | non_priority | cve high detected in bsh core jar cve high severity vulnerability vulnerable library bsh core jar beanshell core path to dependency file java demo pom xml path to vulnerable library home wss scanner repository org beanshell bsh core bsh core jar java demo target easybuggy snapshot web inf lib bsh core jar java demo extract webapps root web inf lib bsh core jar dependency hierarchy x bsh core jar vulnerable library found in head commit a href found in base branch main vulnerability details beanshell bsh before when included on the classpath by an application that uses java serialization or xstream allows remote attackers to execute arbitrary code via crafted serialized data related to xthis handler publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity high privileges required none user interaction none scope unchanged impact metrics confidentiality impact high integrity impact high availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution check this box to open an automated fix pr isopenpronvulnerability false ispackagebased true isdefaultbranch true packages istransitivedependency false dependencytree org beanshell bsh core isminimumfixversionavailable true minimumfixversion basebranches vulnerabilityidentifier cve vulnerabilitydetails beanshell bsh before when included on the classpath by an application that uses java serialization or xstream allows remote attackers to execute arbitrary code via crafted serialized data related to xthis handler vulnerabilityurl | 0 |
789,482 | 27,791,678,161 | IssuesEvent | 2023-03-17 09:24:13 | VeriFIT/mata | https://api.github.com/repos/VeriFIT/mata | opened | Complementation over non-existent states | For:library Module:nfa Type:discussion Priority:low | In classical complement algorithm implemented in `Mata::Nfa::complement_classical`, we call `Mata::Nfa::Nfa::size()` which returns domain size of initial/final state sets. Those might contain “deleted” states (final/initial at some point but not now, yet still allocated with `false` value in `NumberPredicate`), so when we complement such automaton, non-existent states become final.
As of now, we agreed on leaving it up to the user to call `Mata::Nfa::Nfa::trim` before complementing. We might want to reconsider this decision in the future. | 1.0 | Complementation over non-existent states - In classical complement algorithm implemented in `Mata::Nfa::complement_classical`, we call `Mata::Nfa::Nfa::size()` which returns domain size of initial/final state sets. Those might contain “deleted” states (final/initial at some point but not now, yet still allocated with `false` value in `NumberPredicate`), so when we complement such automaton, non-existent states become final.
As of now, we agreed on leaving it up to the user to call `Mata::Nfa::Nfa::trim` before complementing. We might want to reconsider this decision in the future. | priority | complementation over non existent states in classical complement algorithm implemented in mata nfa complement classical we call mata nfa nfa size which returns domain size of initial final state sets those might contain “deleted” states final initial at some point but not now yet still allocated with false value in numberpredicate so when we complement such automaton non existent states become final as of now we agreed on leaving it up to the user to call mata nfa nfa trim before complementing we might want to reconsider this decision in the future | 1 |
585,245 | 17,483,511,838 | IssuesEvent | 2021-08-09 07:53:18 | chaosblade-io/chaosblade | https://api.github.com/repos/chaosblade-io/chaosblade | closed | Does the dd command in the mac system not support the inflag attribute? There will be problems when simulating the disk fill scene | priority/low type/feature chaosblade-exec-os | 我在mac上执行下面命令会报错：
blade create disk fill -d --mount-point /home --size 1024
错误为：
{"code":604,"success":false,"error":"dd: unknown operand iflag\n exit status 1 exit status 1"}
看了一下上面的讨论，我直接执行下面的命令也会报错
命令为：
dd if=/dev/zero of=/home/chaos_filldisk.log.dat bs=1b count=1 iflag=fullblock
错误为：
dd: unknown operand iflag | 1.0 | Does the dd command in the mac system not support the inflag attribute? There will be problems when simulating the disk fill scene - 我在mac上执行下面命令会报错：
blade create disk fill -d --mount-point /home --size 1024
错误为：
{"code":604,"success":false,"error":"dd: unknown operand iflag\n exit status 1 exit status 1"}
看了一下上面的讨论，我直接执行下面的命令也会报错
命令为：
dd if=/dev/zero of=/home/chaos_filldisk.log.dat bs=1b count=1 iflag=fullblock
错误为：
dd: unknown operand iflag | priority | does the dd command in the mac system not support the inflag attribute there will be problems when simulating the disk fill scene 我在mac上执行下面命令会报错： blade create disk fill d mount point home size 错误为： code success false error dd unknown operand iflag n exit status exit status 看了一下上面的讨论，我直接执行下面的命令也会报错 命令为： dd if dev zero of home chaos filldisk log dat bs count iflag fullblock 错误为： dd unknown operand iflag | 1 |
766,672 | 26,893,787,823 | IssuesEvent | 2023-02-06 10:51:23 | webcompat/web-bugs | https://api.github.com/repos/webcompat/web-bugs | closed | yle.fi - site is not usable | priority-normal browser-fenix engine-gecko | <!-- @browser: Firefox Mobile 110.0 -->
<!-- @ua_header: Mozilla/5.0 (Android 12; Mobile; rv:109.0) Gecko/110.0 Firefox/110.0 -->
<!-- @reported_with: android-components-reporter -->
<!-- @public_url: https://github.com/webcompat/web-bugs/issues/117848 -->
<!-- @extra_labels: browser-fenix -->
**URL**: https://yle.fi/a/3-12686102
**Browser / Version**: Firefox Mobile 110.0
**Operating System**: Android 12
**Tested Another Browser**: No
**Problem type**: Site is not usable
**Description**: Page not loading correctly
**Steps to Reproduce**:
Firefox crash when scrolling down
<details>
<summary>View the screenshot</summary>
<img alt="Screenshot" src="https://webcompat.com/uploads/2023/2/fbedd9dc-247a-4857-9592-00e87e78d619.jpeg">
</details>
<details>
<summary>Browser Configuration</summary>
<ul>
<li>gfx.webrender.all: false</li><li>gfx.webrender.blob-images: true</li><li>gfx.webrender.enabled: false</li><li>image.mem.shared: true</li><li>buildID: 20230202190127</li><li>channel: beta</li><li>hasTouchScreen: true</li><li>mixed active content blocked: false</li><li>mixed passive content blocked: false</li><li>tracking content blocked: false</li>
</ul>
</details>
[View console log messages](https://webcompat.com/console_logs/2023/2/b22f578a-bed2-4df4-84cc-cdf435de8169)
_From [webcompat.com](https://webcompat.com/) with ❤️_ | 1.0 | yle.fi - site is not usable - <!-- @browser: Firefox Mobile 110.0 -->
<!-- @ua_header: Mozilla/5.0 (Android 12; Mobile; rv:109.0) Gecko/110.0 Firefox/110.0 -->
<!-- @reported_with: android-components-reporter -->
<!-- @public_url: https://github.com/webcompat/web-bugs/issues/117848 -->
<!-- @extra_labels: browser-fenix -->
**URL**: https://yle.fi/a/3-12686102
**Browser / Version**: Firefox Mobile 110.0
**Operating System**: Android 12
**Tested Another Browser**: No
**Problem type**: Site is not usable
**Description**: Page not loading correctly
**Steps to Reproduce**:
Firefox crash when scrolling down
<details>
<summary>View the screenshot</summary>
<img alt="Screenshot" src="https://webcompat.com/uploads/2023/2/fbedd9dc-247a-4857-9592-00e87e78d619.jpeg">
</details>
<details>
<summary>Browser Configuration</summary>
<ul>
<li>gfx.webrender.all: false</li><li>gfx.webrender.blob-images: true</li><li>gfx.webrender.enabled: false</li><li>image.mem.shared: true</li><li>buildID: 20230202190127</li><li>channel: beta</li><li>hasTouchScreen: true</li><li>mixed active content blocked: false</li><li>mixed passive content blocked: false</li><li>tracking content blocked: false</li>
</ul>
</details>
[View console log messages](https://webcompat.com/console_logs/2023/2/b22f578a-bed2-4df4-84cc-cdf435de8169)
_From [webcompat.com](https://webcompat.com/) with ❤️_ | priority | yle fi site is not usable url browser version firefox mobile operating system android tested another browser no problem type site is not usable description page not loading correctly steps to reproduce firefox crash when scrolling down view the screenshot img alt screenshot src browser configuration gfx webrender all false gfx webrender blob images true gfx webrender enabled false image mem shared true buildid channel beta hastouchscreen true mixed active content blocked false mixed passive content blocked false tracking content blocked false from with ❤️ | 1 |
244,315 | 26,375,102,597 | IssuesEvent | 2023-01-12 01:18:34 | VivekBuzruk/UI | https://api.github.com/repos/VivekBuzruk/UI | opened | CVE-2021-23413 (Medium) detected in jszip-3.5.0.tgz | security vulnerability | ## CVE-2021-23413 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>jszip-3.5.0.tgz</b></p></summary>
<p>Create, read and edit .zip files with JavaScript http://stuartk.com/jszip</p>
<p>Library home page: <a href="https://registry.npmjs.org/jszip/-/jszip-3.5.0.tgz">https://registry.npmjs.org/jszip/-/jszip-3.5.0.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/jszip/package.json</p>
<p>
Dependency Hierarchy:
- protractor-5.4.4.tgz (Root Library)
- selenium-webdriver-3.6.0.tgz
- :x: **jszip-3.5.0.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://api.github.com/repos/VivekBuzruk/UI/commits/edeb2a2fd15349abe4886893f9325323672726f3">edeb2a2fd15349abe4886893f9325323672726f3</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>
This affects the package jszip before 3.7.0. Crafting a new zip file with filenames set to Object prototype values (e.g __proto__, toString, etc) results in a returned object with a modified prototype instance.
<p>Publish Date: 2021-07-25
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2021-23413>CVE-2021-23413</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.3</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: Low
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-23413">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-23413</a></p>
<p>Release Date: 2021-07-25</p>
<p>Fix Resolution (jszip): 3.7.0</p>
<p>Direct dependency fix Resolution (protractor): 6.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-23413 (Medium) detected in jszip-3.5.0.tgz - ## CVE-2021-23413 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>jszip-3.5.0.tgz</b></p></summary>
<p>Create, read and edit .zip files with JavaScript http://stuartk.com/jszip</p>
<p>Library home page: <a href="https://registry.npmjs.org/jszip/-/jszip-3.5.0.tgz">https://registry.npmjs.org/jszip/-/jszip-3.5.0.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/jszip/package.json</p>
<p>
Dependency Hierarchy:
- protractor-5.4.4.tgz (Root Library)
- selenium-webdriver-3.6.0.tgz
- :x: **jszip-3.5.0.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://api.github.com/repos/VivekBuzruk/UI/commits/edeb2a2fd15349abe4886893f9325323672726f3">edeb2a2fd15349abe4886893f9325323672726f3</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>
This affects the package jszip before 3.7.0. Crafting a new zip file with filenames set to Object prototype values (e.g __proto__, toString, etc) results in a returned object with a modified prototype instance.
<p>Publish Date: 2021-07-25
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2021-23413>CVE-2021-23413</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.3</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: Low
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-23413">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-23413</a></p>
<p>Release Date: 2021-07-25</p>
<p>Fix Resolution (jszip): 3.7.0</p>
<p>Direct dependency fix Resolution (protractor): 6.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 medium detected in jszip tgz cve medium severity vulnerability vulnerable library jszip tgz create read and edit zip files with javascript library home page a href path to dependency file package json path to vulnerable library node modules jszip package json dependency hierarchy protractor tgz root library selenium webdriver tgz x jszip tgz vulnerable library found in head commit a href found in base branch master vulnerability details this affects the package jszip before crafting a new zip file with filenames set to object prototype values e g proto tostring etc results in a returned object with a modified prototype instance 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 jszip direct dependency fix resolution protractor step up your open source security game with mend | 0 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.