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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
460,559 | 13,212,748,677 | IssuesEvent | 2020-08-16 08:58:21 | SpongePowered/SpongeCommon | https://api.github.com/repos/SpongePowered/SpongeCommon | closed | Add static methods for plugins to detect whether they're running on Forge or Vanilla | priority: low type: enhancement | Together with the [addition of plugin-provided mixins in SpongeVanilla](https://github.com/SpongePowered/SpongeVanilla/pull/250), it would be useful for plugins to have some static methods to detect the environment they're running in before the game has actually started.
They can be used to apply a certain mixin only to either SpongeForge or SpongeVanilla but not both (similar to what we do currently in SpongeVanilla/SpongeForge).
| 1.0 | Add static methods for plugins to detect whether they're running on Forge or Vanilla - Together with the [addition of plugin-provided mixins in SpongeVanilla](https://github.com/SpongePowered/SpongeVanilla/pull/250), it would be useful for plugins to have some static methods to detect the environment they're running in before the game has actually started.
They can be used to apply a certain mixin only to either SpongeForge or SpongeVanilla but not both (similar to what we do currently in SpongeVanilla/SpongeForge).
| priority | add static methods for plugins to detect whether they re running on forge or vanilla together with the it would be useful for plugins to have some static methods to detect the environment they re running in before the game has actually started they can be used to apply a certain mixin only to either spongeforge or spongevanilla but not both similar to what we do currently in spongevanilla spongeforge | 1 |
428,221 | 12,404,922,079 | IssuesEvent | 2020-05-21 16:21:07 | DarshanShet777/Model-Airport | https://api.github.com/repos/DarshanShet777/Model-Airport | opened | Electrical Engineering: Checkpost IR Receiver Incorrect Readings | Medium Priority | The Checkposts cannot seem to sense the robot when it arrives. | 1.0 | Electrical Engineering: Checkpost IR Receiver Incorrect Readings - The Checkposts cannot seem to sense the robot when it arrives. | priority | electrical engineering checkpost ir receiver incorrect readings the checkposts cannot seem to sense the robot when it arrives | 1 |
112,156 | 4,511,868,870 | IssuesEvent | 2016-09-03 08:58:22 | kubernetes/kubernetes | https://api.github.com/repos/kubernetes/kubernetes | closed | BeforeSuite: Failed to setup provider config | area/cluster-lifecycle kind/flake priority/P0 | Multiple issues in the BeforeSuite failure bug (#30075). Splitting this particular failure mode out.
Aug 15 14:39:13.884: Failed to setup provider config: Error building GCE/GKE provider: Get https://www.googleapis.com/compute/v1/projects/k8s-e2e-gke-staging-parallel/global/networks?alt=json: oauth2: cannot fetch token: Post https://accounts.google.com/o/oauth2/token: net/http: TLS handshake timeout
Aug 23 21:51:14.760: Failed to setup provider config: Error building GCE/GKE provider: googleapi: Error 500: Internal Error, internalError
Aug 25 16:06:00.946: Failed to setup provider config: Error building GCE/GKE provider: Get https://www.googleapis.com/compute/v1/projects/k8s-e2e-gke-staging-parallel/global/networks?alt=json: oauth2: cannot fetch token: Post https://accounts.google.com/o/oauth2/token: dial tcp 74.125.69.84:443: i/o timeout
Comment with more details: https://github.com/kubernetes/kubernetes/issues/30075#issuecomment-242576929 | 1.0 | BeforeSuite: Failed to setup provider config - Multiple issues in the BeforeSuite failure bug (#30075). Splitting this particular failure mode out.
Aug 15 14:39:13.884: Failed to setup provider config: Error building GCE/GKE provider: Get https://www.googleapis.com/compute/v1/projects/k8s-e2e-gke-staging-parallel/global/networks?alt=json: oauth2: cannot fetch token: Post https://accounts.google.com/o/oauth2/token: net/http: TLS handshake timeout
Aug 23 21:51:14.760: Failed to setup provider config: Error building GCE/GKE provider: googleapi: Error 500: Internal Error, internalError
Aug 25 16:06:00.946: Failed to setup provider config: Error building GCE/GKE provider: Get https://www.googleapis.com/compute/v1/projects/k8s-e2e-gke-staging-parallel/global/networks?alt=json: oauth2: cannot fetch token: Post https://accounts.google.com/o/oauth2/token: dial tcp 74.125.69.84:443: i/o timeout
Comment with more details: https://github.com/kubernetes/kubernetes/issues/30075#issuecomment-242576929 | priority | beforesuite failed to setup provider config multiple issues in the beforesuite failure bug splitting this particular failure mode out aug failed to setup provider config error building gce gke provider get cannot fetch token post net http tls handshake timeout aug failed to setup provider config error building gce gke provider googleapi error internal error internalerror aug failed to setup provider config error building gce gke provider get cannot fetch token post dial tcp i o timeout comment with more details | 1 |
264,498 | 23,120,941,184 | IssuesEvent | 2022-07-27 21:24:48 | microsoft/vscode-pull-request-github | https://api.github.com/repos/microsoft/vscode-pull-request-github | closed | Test Suggested Assignees | testplan-item | Refs: #3627
- [x] anyOS @greazer
- [x] anyOS @lramos15
Complexity: 1
[Create Issue](https://github.com/microsoft/vscode-pull-request-github/issues/new?body=Testing+%233765%0A%0A&assignees=benibenj)
---
Suggests Users when assigning a user to a PR
1. Install the pre-release build of GitHub Pull Requests and Issues.
2. Open a folder in VS Code that contains a GitHub repository.
3. Open a Pull Request Overview of any PR by clicking on the description node of a PR
4. Press on add Assignee
5. A dropdown should appear with suggested users to assign at the top. The first should be the viewer himself and the rest should be participants of the PR. In the second section, all other assignable users are listed sorted alphabetically (not the ones from the suggested list). | 1.0 | Test Suggested Assignees - Refs: #3627
- [x] anyOS @greazer
- [x] anyOS @lramos15
Complexity: 1
[Create Issue](https://github.com/microsoft/vscode-pull-request-github/issues/new?body=Testing+%233765%0A%0A&assignees=benibenj)
---
Suggests Users when assigning a user to a PR
1. Install the pre-release build of GitHub Pull Requests and Issues.
2. Open a folder in VS Code that contains a GitHub repository.
3. Open a Pull Request Overview of any PR by clicking on the description node of a PR
4. Press on add Assignee
5. A dropdown should appear with suggested users to assign at the top. The first should be the viewer himself and the rest should be participants of the PR. In the second section, all other assignable users are listed sorted alphabetically (not the ones from the suggested list). | non_priority | test suggested assignees refs anyos greazer anyos complexity suggests users when assigning a user to a pr install the pre release build of github pull requests and issues open a folder in vs code that contains a github repository open a pull request overview of any pr by clicking on the description node of a pr press on add assignee a dropdown should appear with suggested users to assign at the top the first should be the viewer himself and the rest should be participants of the pr in the second section all other assignable users are listed sorted alphabetically not the ones from the suggested list | 0 |
429,610 | 12,426,427,407 | IssuesEvent | 2020-05-24 21:07:47 | roed314/seminars | https://api.github.com/repos/roed314/seminars | closed | Make "logout" more prominent | low priority user interface | It is a little bit hard to find the logout on the site.
Maybe we could make it a button, and move it to the upper right of the Account page so that it is by itself instead of attached to other text in the middle of the page, and capitalize the first letter?
(I can see why it was put where it is, since it is an operation related to the user name, but for me the need to make it easier to find is more compelling.) | 1.0 | Make "logout" more prominent - It is a little bit hard to find the logout on the site.
Maybe we could make it a button, and move it to the upper right of the Account page so that it is by itself instead of attached to other text in the middle of the page, and capitalize the first letter?
(I can see why it was put where it is, since it is an operation related to the user name, but for me the need to make it easier to find is more compelling.) | priority | make logout more prominent it is a little bit hard to find the logout on the site maybe we could make it a button and move it to the upper right of the account page so that it is by itself instead of attached to other text in the middle of the page and capitalize the first letter i can see why it was put where it is since it is an operation related to the user name but for me the need to make it easier to find is more compelling | 1 |
317,395 | 9,664,577,266 | IssuesEvent | 2019-05-21 06:05:39 | kartoza/ford3 | https://api.github.com/repos/kartoza/ford3 | closed | the webapp must be protected by a login page. | Size: 3 auth in review priority: high review |
An user must be authenticated and authorized to see the resource he's trying to see.
I started to work on this here: https://github.com/pierrealixt/ford3/tree/login-198
<img width="575" alt="Screen Shot 2019-05-16 at 08 49 52" src="https://user-images.githubusercontent.com/35932320/57832319-a9066580-77b7-11e9-8a94-9d00a6afcf97.png">
| 1.0 | the webapp must be protected by a login page. -
An user must be authenticated and authorized to see the resource he's trying to see.
I started to work on this here: https://github.com/pierrealixt/ford3/tree/login-198
<img width="575" alt="Screen Shot 2019-05-16 at 08 49 52" src="https://user-images.githubusercontent.com/35932320/57832319-a9066580-77b7-11e9-8a94-9d00a6afcf97.png">
| priority | the webapp must be protected by a login page an user must be authenticated and authorized to see the resource he s trying to see i started to work on this here img width alt screen shot at src | 1 |
435,623 | 12,536,789,012 | IssuesEvent | 2020-06-05 01:15:43 | pingcap/tidb | https://api.github.com/repos/pingcap/tidb | closed | Flag to not print arguments in slowlog | priority/release-blocker security type/feature-request | We would like a flag that disables the printing of argument values in the slowlog. Only the query should be printed. | 1.0 | Flag to not print arguments in slowlog - We would like a flag that disables the printing of argument values in the slowlog. Only the query should be printed. | priority | flag to not print arguments in slowlog we would like a flag that disables the printing of argument values in the slowlog only the query should be printed | 1 |
758,901 | 26,573,262,387 | IssuesEvent | 2023-01-21 13:07:49 | Tau-ri-Dev/JSGMod-1.12.2 | https://api.github.com/repos/Tau-ri-Dev/JSGMod-1.12.2 | closed | Bug: Server resets PoO | Bug/Issue Low priority Confirmed | **Describe the bug**
Minecraft Servers do not save the PoO when you override it in the gate config.
**To Reproduce**
Steps to reproduce the behavior:
1. Go onto a Minecraft server
2. Build a Stargate
3. Override Stargate's PoO to anything other than the default and log out
4. Stargate PoO resets
**Expected behavior**
Stargate PoO Override should remain when logging back into the server
**Screenshots**
PoO I set in the Config tab in the gate:
<img width="1280" alt="Set PoO" src="https://user-images.githubusercontent.com/50058178/213177906-e397cabd-b137-4a72-90c0-df96875c0c5d.png">
PoO when I relog into my server:
<img width="1280" alt="Serverrelog PoO" src="https://user-images.githubusercontent.com/50058178/213178180-eade2dd1-f378-4bef-ba14-92da2978c600.png">
**Mod version**
JSG 4.11.0.1
| 1.0 | Bug: Server resets PoO - **Describe the bug**
Minecraft Servers do not save the PoO when you override it in the gate config.
**To Reproduce**
Steps to reproduce the behavior:
1. Go onto a Minecraft server
2. Build a Stargate
3. Override Stargate's PoO to anything other than the default and log out
4. Stargate PoO resets
**Expected behavior**
Stargate PoO Override should remain when logging back into the server
**Screenshots**
PoO I set in the Config tab in the gate:
<img width="1280" alt="Set PoO" src="https://user-images.githubusercontent.com/50058178/213177906-e397cabd-b137-4a72-90c0-df96875c0c5d.png">
PoO when I relog into my server:
<img width="1280" alt="Serverrelog PoO" src="https://user-images.githubusercontent.com/50058178/213178180-eade2dd1-f378-4bef-ba14-92da2978c600.png">
**Mod version**
JSG 4.11.0.1
| priority | bug server resets poo describe the bug minecraft servers do not save the poo when you override it in the gate config to reproduce steps to reproduce the behavior go onto a minecraft server build a stargate override stargate s poo to anything other than the default and log out stargate poo resets expected behavior stargate poo override should remain when logging back into the server screenshots poo i set in the config tab in the gate img width alt set poo src poo when i relog into my server img width alt serverrelog poo src mod version jsg | 1 |
19,609 | 6,743,502,232 | IssuesEvent | 2017-10-20 12:23:35 | Great-Hill-Corporation/quickBlocks | https://api.github.com/repos/Great-Hill-Corporation/quickBlocks | closed | Dates missing at articles table | build-docs status-resolved type-question | What is the meaning of the Date tags at articles table?
Here
https://github.com/Great-Hill-Corporation/quickBlocks/blob/develop/src/other/articles/README.md
we have some articles with the date defined but others is missing, is it pending? | 1.0 | Dates missing at articles table - What is the meaning of the Date tags at articles table?
Here
https://github.com/Great-Hill-Corporation/quickBlocks/blob/develop/src/other/articles/README.md
we have some articles with the date defined but others is missing, is it pending? | non_priority | dates missing at articles table what is the meaning of the date tags at articles table here we have some articles with the date defined but others is missing is it pending | 0 |
289,879 | 31,999,552,704 | IssuesEvent | 2023-09-21 11:22:57 | Mend-developer-platform-load/11653742_33 | https://api.github.com/repos/Mend-developer-platform-load/11653742_33 | opened | CVE-2022-21704 (Medium) detected in log4js-0.6.38.tgz | Mend: dependency security vulnerability | ## CVE-2022-21704 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>log4js-0.6.38.tgz</b></p></summary>
<p>Port of Log4js to work with node.</p>
<p>Library home page: <a href="https://registry.npmjs.org/log4js/-/log4js-0.6.38.tgz">https://registry.npmjs.org/log4js/-/log4js-0.6.38.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/log4js/package.json</p>
<p>
Dependency Hierarchy:
- :x: **log4js-0.6.38.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/Mend-developer-platform-load/11653742_33/commit/f0c512deafe83d8bd202ee8af80aa33955251616">f0c512deafe83d8bd202ee8af80aa33955251616</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> Vulnerability Details</summary>
<p>
log4js-node is a port of log4js to node.js. In affected versions default file permissions for log files created by the file, fileSync and dateFile appenders are world-readable (in unix). This could cause problems if log files contain sensitive information. This would affect any users that have not supplied their own permissions for the files via the mode parameter in the config. Users are advised to update.
<p>Publish Date: 2022-01-19
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-21704>CVE-2022-21704</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: None
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/log4js-node/log4js-node/security/advisories/GHSA-82v2-mx6x-wq7q">https://github.com/log4js-node/log4js-node/security/advisories/GHSA-82v2-mx6x-wq7q</a></p>
<p>Release Date: 2022-01-19</p>
<p>Fix Resolution: 6.4.0</p>
</p>
</details>
<p></p>
***
:rescue_worker_helmet: Automatic Remediation will be attempted for this issue. | True | CVE-2022-21704 (Medium) detected in log4js-0.6.38.tgz - ## CVE-2022-21704 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>log4js-0.6.38.tgz</b></p></summary>
<p>Port of Log4js to work with node.</p>
<p>Library home page: <a href="https://registry.npmjs.org/log4js/-/log4js-0.6.38.tgz">https://registry.npmjs.org/log4js/-/log4js-0.6.38.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/log4js/package.json</p>
<p>
Dependency Hierarchy:
- :x: **log4js-0.6.38.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/Mend-developer-platform-load/11653742_33/commit/f0c512deafe83d8bd202ee8af80aa33955251616">f0c512deafe83d8bd202ee8af80aa33955251616</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> Vulnerability Details</summary>
<p>
log4js-node is a port of log4js to node.js. In affected versions default file permissions for log files created by the file, fileSync and dateFile appenders are world-readable (in unix). This could cause problems if log files contain sensitive information. This would affect any users that have not supplied their own permissions for the files via the mode parameter in the config. Users are advised to update.
<p>Publish Date: 2022-01-19
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-21704>CVE-2022-21704</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: None
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/log4js-node/log4js-node/security/advisories/GHSA-82v2-mx6x-wq7q">https://github.com/log4js-node/log4js-node/security/advisories/GHSA-82v2-mx6x-wq7q</a></p>
<p>Release Date: 2022-01-19</p>
<p>Fix Resolution: 6.4.0</p>
</p>
</details>
<p></p>
***
:rescue_worker_helmet: Automatic Remediation will be attempted for this issue. | non_priority | cve medium detected in tgz cve medium severity vulnerability vulnerable library tgz port of to work with node library home page a href path to dependency file package json path to vulnerable library node modules package json dependency hierarchy x tgz vulnerable library found in head commit a href found in base branch main vulnerability details node is a port of to node js in affected versions default file permissions for log files created by the file filesync and datefile appenders are world readable in unix this could cause problems if log files contain sensitive information this would affect any users that have not supplied their own permissions for the files via the mode parameter in the config users are advised to update publish date url a href cvss score details base score metrics exploitability metrics attack vector local attack complexity low privileges required low user interaction none scope unchanged impact metrics confidentiality impact high integrity impact none availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution rescue worker helmet automatic remediation will be attempted for this issue | 0 |
260,505 | 22,626,843,667 | IssuesEvent | 2022-06-30 11:27:40 | ChainSafe/ui-monorepo | https://api.github.com/repos/ChainSafe/ui-monorepo | closed | [Storage] Sort columns in Buckets view test | Testing | As described add coverage to sort columns in Buckets:
- By Name
- By File system
- By Size
| 1.0 | [Storage] Sort columns in Buckets view test - As described add coverage to sort columns in Buckets:
- By Name
- By File system
- By Size
| non_priority | sort columns in buckets view test as described add coverage to sort columns in buckets by name by file system by size | 0 |
338,571 | 10,231,777,914 | IssuesEvent | 2019-08-18 12:33:06 | Electroblob77/Wizardry | https://api.github.com/repos/Electroblob77/Wizardry | closed | earthquake kills players without a message | cosmetic low priority | Minecraft version: 1.12.2
Wizardry version: 4.1.2
Environment: Server
Issue details:
Player A stand on the ground with low health
Player B stand on the same level and user an earthquake spell
Player A dies
Expected: chat message explaining player B kill player A
Observed: no chat message
| 1.0 | earthquake kills players without a message - Minecraft version: 1.12.2
Wizardry version: 4.1.2
Environment: Server
Issue details:
Player A stand on the ground with low health
Player B stand on the same level and user an earthquake spell
Player A dies
Expected: chat message explaining player B kill player A
Observed: no chat message
| priority | earthquake kills players without a message minecraft version wizardry version environment server issue details player a stand on the ground with low health player b stand on the same level and user an earthquake spell player a dies expected chat message explaining player b kill player a observed no chat message | 1 |
141,526 | 18,989,296,698 | IssuesEvent | 2021-11-22 04:03:17 | ChoeMinji/react-16.0.0 | https://api.github.com/repos/ChoeMinji/react-16.0.0 | opened | CVE-2021-23386 (Medium) detected in dns-packet-1.2.2.tgz, dns-packet-1.1.1.tgz | security vulnerability | ## CVE-2021-23386 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>dns-packet-1.2.2.tgz</b>, <b>dns-packet-1.1.1.tgz</b></p></summary>
<p>
<details><summary><b>dns-packet-1.2.2.tgz</b></p></summary>
<p>An abstract-encoding compliant module for encoding / decoding DNS packets</p>
<p>Library home page: <a href="https://registry.npmjs.org/dns-packet/-/dns-packet-1.2.2.tgz">https://registry.npmjs.org/dns-packet/-/dns-packet-1.2.2.tgz</a></p>
<p>Path to dependency file: react-16.0.0/fixtures/attribute-behavior/package.json</p>
<p>Path to vulnerable library: react-16.0.0/fixtures/attribute-behavior/node_modules/dns-packet/package.json</p>
<p>
Dependency Hierarchy:
- react-scripts-1.0.11.tgz (Root Library)
- webpack-dev-server-2.7.1.tgz
- bonjour-3.5.0.tgz
- multicast-dns-6.1.1.tgz
- :x: **dns-packet-1.2.2.tgz** (Vulnerable Library)
</details>
<details><summary><b>dns-packet-1.1.1.tgz</b></p></summary>
<p>An abstract-encoding compliant module for encoding / decoding DNS packets</p>
<p>Library home page: <a href="https://registry.npmjs.org/dns-packet/-/dns-packet-1.1.1.tgz">https://registry.npmjs.org/dns-packet/-/dns-packet-1.1.1.tgz</a></p>
<p>Path to dependency file: react-16.0.0/fixtures/dom/package.json</p>
<p>Path to vulnerable library: react-16.0.0/fixtures/dom/node_modules/dns-packet/package.json</p>
<p>
Dependency Hierarchy:
- react-scripts-1.0.11.tgz (Root Library)
- webpack-dev-server-2.7.1.tgz
- bonjour-3.5.0.tgz
- multicast-dns-6.1.1.tgz
- :x: **dns-packet-1.1.1.tgz** (Vulnerable Library)
</details>
<p>Found in HEAD commit: <a href="https://github.com/ChoeMinji/react-16.0.0/commit/b9bd902dad80b8b5fa55a183526357266ae47bcc">b9bd902dad80b8b5fa55a183526357266ae47bcc</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 dns-packet before 5.2.2. It creates buffers with allocUnsafe and does not always fill them before forming network packets. This can expose internal application memory over unencrypted network when querying crafted invalid domain names.
<p>Publish Date: 2021-05-20
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-23386>CVE-2021-23386</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>6.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: None
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-23386">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-23386</a></p>
<p>Release Date: 2021-05-20</p>
<p>Fix Resolution: dns-packet - 5.2.2</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | CVE-2021-23386 (Medium) detected in dns-packet-1.2.2.tgz, dns-packet-1.1.1.tgz - ## CVE-2021-23386 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>dns-packet-1.2.2.tgz</b>, <b>dns-packet-1.1.1.tgz</b></p></summary>
<p>
<details><summary><b>dns-packet-1.2.2.tgz</b></p></summary>
<p>An abstract-encoding compliant module for encoding / decoding DNS packets</p>
<p>Library home page: <a href="https://registry.npmjs.org/dns-packet/-/dns-packet-1.2.2.tgz">https://registry.npmjs.org/dns-packet/-/dns-packet-1.2.2.tgz</a></p>
<p>Path to dependency file: react-16.0.0/fixtures/attribute-behavior/package.json</p>
<p>Path to vulnerable library: react-16.0.0/fixtures/attribute-behavior/node_modules/dns-packet/package.json</p>
<p>
Dependency Hierarchy:
- react-scripts-1.0.11.tgz (Root Library)
- webpack-dev-server-2.7.1.tgz
- bonjour-3.5.0.tgz
- multicast-dns-6.1.1.tgz
- :x: **dns-packet-1.2.2.tgz** (Vulnerable Library)
</details>
<details><summary><b>dns-packet-1.1.1.tgz</b></p></summary>
<p>An abstract-encoding compliant module for encoding / decoding DNS packets</p>
<p>Library home page: <a href="https://registry.npmjs.org/dns-packet/-/dns-packet-1.1.1.tgz">https://registry.npmjs.org/dns-packet/-/dns-packet-1.1.1.tgz</a></p>
<p>Path to dependency file: react-16.0.0/fixtures/dom/package.json</p>
<p>Path to vulnerable library: react-16.0.0/fixtures/dom/node_modules/dns-packet/package.json</p>
<p>
Dependency Hierarchy:
- react-scripts-1.0.11.tgz (Root Library)
- webpack-dev-server-2.7.1.tgz
- bonjour-3.5.0.tgz
- multicast-dns-6.1.1.tgz
- :x: **dns-packet-1.1.1.tgz** (Vulnerable Library)
</details>
<p>Found in HEAD commit: <a href="https://github.com/ChoeMinji/react-16.0.0/commit/b9bd902dad80b8b5fa55a183526357266ae47bcc">b9bd902dad80b8b5fa55a183526357266ae47bcc</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 dns-packet before 5.2.2. It creates buffers with allocUnsafe and does not always fill them before forming network packets. This can expose internal application memory over unencrypted network when querying crafted invalid domain names.
<p>Publish Date: 2021-05-20
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-23386>CVE-2021-23386</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>6.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: None
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-23386">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-23386</a></p>
<p>Release Date: 2021-05-20</p>
<p>Fix Resolution: dns-packet - 5.2.2</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_priority | cve medium detected in dns packet tgz dns packet tgz cve medium severity vulnerability vulnerable libraries dns packet tgz dns packet tgz dns packet tgz an abstract encoding compliant module for encoding decoding dns packets library home page a href path to dependency file react fixtures attribute behavior package json path to vulnerable library react fixtures attribute behavior node modules dns packet package json dependency hierarchy react scripts tgz root library webpack dev server tgz bonjour tgz multicast dns tgz x dns packet tgz vulnerable library dns packet tgz an abstract encoding compliant module for encoding decoding dns packets library home page a href path to dependency file react fixtures dom package json path to vulnerable library react fixtures dom node modules dns packet package json dependency hierarchy react scripts tgz root library webpack dev server tgz bonjour tgz multicast dns tgz x dns packet tgz vulnerable library found in head commit a href found in base branch master vulnerability details this affects the package dns packet before it creates buffers with allocunsafe and does not always fill them before forming network packets this can expose internal application memory over unencrypted network when querying crafted invalid domain names publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required low user interaction none scope unchanged impact metrics confidentiality impact high integrity impact none availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution dns packet step up your open source security game with whitesource | 0 |
622,185 | 19,609,763,509 | IssuesEvent | 2022-01-06 14:06:55 | decompme/decomp.me | https://api.github.com/repos/decompme/decomp.me | closed | Use custom modal dialog instead of using HTML <dialog> | bug frontend high priority | `<dialog>` is really buggy on some browsers (read: older Safari) and its getting annoying to manually fix issues; we should just use a react modal library | 1.0 | Use custom modal dialog instead of using HTML <dialog> - `<dialog>` is really buggy on some browsers (read: older Safari) and its getting annoying to manually fix issues; we should just use a react modal library | priority | use custom modal dialog instead of using html is really buggy on some browsers read older safari and its getting annoying to manually fix issues we should just use a react modal library | 1 |
117,951 | 4,729,562,141 | IssuesEvent | 2016-10-18 19:02:46 | Parabot/Parabot | https://api.github.com/repos/Parabot/Parabot | closed | New version notification | priority:medium status:accepted type:bug | When you get notified of a new version, it redirects you to the old BDN, should be v3.
This should also detect the version, nightly or not - whereas it will download a new nightly version if available, otherwise simply the latest. | 1.0 | New version notification - When you get notified of a new version, it redirects you to the old BDN, should be v3.
This should also detect the version, nightly or not - whereas it will download a new nightly version if available, otherwise simply the latest. | priority | new version notification when you get notified of a new version it redirects you to the old bdn should be this should also detect the version nightly or not whereas it will download a new nightly version if available otherwise simply the latest | 1 |
351,763 | 32,025,433,086 | IssuesEvent | 2023-09-22 08:30:19 | unifyai/ivy | https://api.github.com/repos/unifyai/ivy | closed | Fix general_functions.test_tensorflow_where_no_xy | TensorFlow Frontend Sub Task Failing Test | | | |
|---|---|
|numpy|<a href="https://github.com/unifyai/ivy/actions/runs/6271730752"><img src=https://img.shields.io/badge/-success-success></a>
|jax|<a href="https://github.com/unifyai/ivy/actions/runs/6271730752"><img src=https://img.shields.io/badge/-success-success></a>
|tensorflow|<a href="https://github.com/unifyai/ivy/actions/runs/6271730752"><img src=https://img.shields.io/badge/-success-success></a>
|torch|<a href="https://github.com/unifyai/ivy/actions/runs/6271730752"><img src=https://img.shields.io/badge/-success-success></a>
|paddle|<a href="https://github.com/unifyai/ivy/actions/runs/6271730752"><img src=https://img.shields.io/badge/-success-success></a>
| 1.0 | Fix general_functions.test_tensorflow_where_no_xy - | | |
|---|---|
|numpy|<a href="https://github.com/unifyai/ivy/actions/runs/6271730752"><img src=https://img.shields.io/badge/-success-success></a>
|jax|<a href="https://github.com/unifyai/ivy/actions/runs/6271730752"><img src=https://img.shields.io/badge/-success-success></a>
|tensorflow|<a href="https://github.com/unifyai/ivy/actions/runs/6271730752"><img src=https://img.shields.io/badge/-success-success></a>
|torch|<a href="https://github.com/unifyai/ivy/actions/runs/6271730752"><img src=https://img.shields.io/badge/-success-success></a>
|paddle|<a href="https://github.com/unifyai/ivy/actions/runs/6271730752"><img src=https://img.shields.io/badge/-success-success></a>
| non_priority | fix general functions test tensorflow where no xy numpy a href src jax a href src tensorflow a href src torch a href src paddle a href src | 0 |
37,053 | 15,161,753,958 | IssuesEvent | 2021-02-12 09:33:25 | LiskHQ/lisk-docs | https://api.github.com/repos/LiskHQ/lisk-docs | opened | Include latest README updates | component: service type: update | Include latest updates in the README files in the documentation for Lisk Service 0.2.0 | 1.0 | Include latest README updates - Include latest updates in the README files in the documentation for Lisk Service 0.2.0 | non_priority | include latest readme updates include latest updates in the readme files in the documentation for lisk service | 0 |
222,399 | 17,411,092,093 | IssuesEvent | 2021-08-03 12:26:37 | intermine/bluegenes | https://api.github.com/repos/intermine/bluegenes | closed | Tool API: Add description field to config.json | Tool API usertesting | This will be displayed when hovering/clicking the (?) in the tool headers of the new report page design.
It seems it would be useful to provide extra information on the tool. The (?) icon would only be visible if a description is defined. | 1.0 | Tool API: Add description field to config.json - This will be displayed when hovering/clicking the (?) in the tool headers of the new report page design.
It seems it would be useful to provide extra information on the tool. The (?) icon would only be visible if a description is defined. | non_priority | tool api add description field to config json this will be displayed when hovering clicking the in the tool headers of the new report page design it seems it would be useful to provide extra information on the tool the icon would only be visible if a description is defined | 0 |
110,422 | 4,426,669,405 | IssuesEvent | 2016-08-16 19:00:49 | aces/cbrain | https://api.github.com/repos/aces/cbrain | closed | Add content_storage_shared_between_users?() method to DataProvider API | Enhancement Priority: Normal Refactoring | Right now at many places in the code we try to detect if a data provider's storage mechanism shares a single space for files between users, so that two users cannot have the same filename on the same DP (which is normally permitted by the Userfile model itself). The detection is currently done by checking the return value of `allow_file_owner_change?()` ; if true, it is assumed the storage is shared, and if false, it's not shared (as in a Vault DP). However, this is misleading, because on some DPs the storage is NOT shared yet `allow_file_owner_change?()` properly returns true. The correlation is not exact.
Let's introduce a new official API call `content_storage_shared_between_users?()` to properly reflect that storage issue. All DP's code will get the new method returning `true` or `false` and then all code whose behavior was adjusted based on `allow_file_owner_change?()` will get adjusted too.
Related: #180 #451 | 1.0 | Add content_storage_shared_between_users?() method to DataProvider API - Right now at many places in the code we try to detect if a data provider's storage mechanism shares a single space for files between users, so that two users cannot have the same filename on the same DP (which is normally permitted by the Userfile model itself). The detection is currently done by checking the return value of `allow_file_owner_change?()` ; if true, it is assumed the storage is shared, and if false, it's not shared (as in a Vault DP). However, this is misleading, because on some DPs the storage is NOT shared yet `allow_file_owner_change?()` properly returns true. The correlation is not exact.
Let's introduce a new official API call `content_storage_shared_between_users?()` to properly reflect that storage issue. All DP's code will get the new method returning `true` or `false` and then all code whose behavior was adjusted based on `allow_file_owner_change?()` will get adjusted too.
Related: #180 #451 | priority | add content storage shared between users method to dataprovider api right now at many places in the code we try to detect if a data provider s storage mechanism shares a single space for files between users so that two users cannot have the same filename on the same dp which is normally permitted by the userfile model itself the detection is currently done by checking the return value of allow file owner change if true it is assumed the storage is shared and if false it s not shared as in a vault dp however this is misleading because on some dps the storage is not shared yet allow file owner change properly returns true the correlation is not exact let s introduce a new official api call content storage shared between users to properly reflect that storage issue all dp s code will get the new method returning true or false and then all code whose behavior was adjusted based on allow file owner change will get adjusted too related | 1 |
74 | 2,495,915,805 | IssuesEvent | 2015-01-06 15:44:33 | brashrebel/render | https://api.github.com/repos/brashrebel/render | opened | Special characters | shortcode idea | Nice drop-down for easily adding special characters like copyright, trademark, etc. | 1.0 | Special characters - Nice drop-down for easily adding special characters like copyright, trademark, etc. | non_priority | special characters nice drop down for easily adding special characters like copyright trademark etc | 0 |
17,336 | 10,684,222,234 | IssuesEvent | 2019-10-22 09:59:33 | Mte90/Share-Backported | https://api.github.com/repos/Mte90/Share-Backported | closed | Integration with Google Keep | help wanted service | One nifty feature of Chrome on my Android is the ability to share web links directly into Google Keep. The note title is the web page title, the note body is just the link. It's a good decent alternative to using the browser's built-in remote bookmark management (ex: Firefox Sync). Can you please consider this integration? Thank you. | 1.0 | Integration with Google Keep - One nifty feature of Chrome on my Android is the ability to share web links directly into Google Keep. The note title is the web page title, the note body is just the link. It's a good decent alternative to using the browser's built-in remote bookmark management (ex: Firefox Sync). Can you please consider this integration? Thank you. | non_priority | integration with google keep one nifty feature of chrome on my android is the ability to share web links directly into google keep the note title is the web page title the note body is just the link it s a good decent alternative to using the browser s built in remote bookmark management ex firefox sync can you please consider this integration thank you | 0 |
55,490 | 14,523,026,523 | IssuesEvent | 2020-12-14 09:35:23 | SAP/fundamental-ngx | https://api.github.com/repos/SAP/fundamental-ngx | closed | Bug: (Platform) Combobox – on the second and next opens mobile mode dialog you'll get RangeError | Defect Hunting bug platform | #### Is this a bug, enhancement, or feature request?
bug
#### Briefly describe your proposal.
When you open the [Mobile Mode](https://fundamental-ngx.netlify.app/#/platform/combobox#combobox-mobile) dialog in the second and next times, you'll get `RangeError: Maximum call stack size exceeded.`
#### Which versions of Angular and Fundamental Library for Angular are affected? (If this is a feature request, use current version.)
fundamental-ngx: v 0.25.0
#### If this is a bug, please provide steps for reproducing it.
#### Please provide relevant source code if applicable.
#### Is there anything else we should know?
Safari | 1.0 | Bug: (Platform) Combobox – on the second and next opens mobile mode dialog you'll get RangeError - #### Is this a bug, enhancement, or feature request?
bug
#### Briefly describe your proposal.
When you open the [Mobile Mode](https://fundamental-ngx.netlify.app/#/platform/combobox#combobox-mobile) dialog in the second and next times, you'll get `RangeError: Maximum call stack size exceeded.`
#### Which versions of Angular and Fundamental Library for Angular are affected? (If this is a feature request, use current version.)
fundamental-ngx: v 0.25.0
#### If this is a bug, please provide steps for reproducing it.
#### Please provide relevant source code if applicable.
#### Is there anything else we should know?
Safari | non_priority | bug platform combobox – on the second and next opens mobile mode dialog you ll get rangeerror is this a bug enhancement or feature request bug briefly describe your proposal when you open the dialog in the second and next times you ll get rangeerror maximum call stack size exceeded which versions of angular and fundamental library for angular are affected if this is a feature request use current version fundamental ngx v if this is a bug please provide steps for reproducing it please provide relevant source code if applicable is there anything else we should know safari | 0 |
693,090 | 23,762,743,558 | IssuesEvent | 2022-09-01 10:13:00 | metabase/metabase | https://api.github.com/repos/metabase/metabase | closed | Tooltip periods are not displayed nicely on SQL questions | Type:Bug Priority:P2 Querying/Native .Frontend Visualization/Charts .Reproduced .Regression | **Describe the bug**
When you group by week/month on Editor the result is a range:
<img width="1489" alt="image" src="https://user-images.githubusercontent.com/110378427/186652916-c1b7d983-f403-4537-9951-fa24b02e1fd5.png">
If you take the same question and turn it into SQL. The tooltip doesn't pick up the range granularity :
<img width="1486" alt="image" src="https://user-images.githubusercontent.com/110378427/186653000-68a5f732-9336-4ac0-bed9-01c35028c8c7.png">
**To Reproduce**
Steps to reproduce the behavior:
1. Go to New -> Question -> Sample Database -> Orders -> Summarise Count -> Group by Created At (Choose Week)
2. Notice the preview dates are in "April 24, 2016 – April 30, 2016" format
3. Go to View this SQL Icon -> Convert Question to SQL -> Re-Run
4. Notice the dates are in "April 24, 2016 " format
5. Tooltip Granularity is lost
**Expected behavior**
Same behavior is expected from both Question and Native SQL. This issue got introduced in 44 since previously to this version they where experiencing similar outcome. In version 43 the output was as following:
<img width="1487" alt="image" src="https://user-images.githubusercontent.com/110378427/186657468-4322c2f6-9607-48f9-99bc-db87fba5685a.png">
| 1.0 | Tooltip periods are not displayed nicely on SQL questions - **Describe the bug**
When you group by week/month on Editor the result is a range:
<img width="1489" alt="image" src="https://user-images.githubusercontent.com/110378427/186652916-c1b7d983-f403-4537-9951-fa24b02e1fd5.png">
If you take the same question and turn it into SQL. The tooltip doesn't pick up the range granularity :
<img width="1486" alt="image" src="https://user-images.githubusercontent.com/110378427/186653000-68a5f732-9336-4ac0-bed9-01c35028c8c7.png">
**To Reproduce**
Steps to reproduce the behavior:
1. Go to New -> Question -> Sample Database -> Orders -> Summarise Count -> Group by Created At (Choose Week)
2. Notice the preview dates are in "April 24, 2016 – April 30, 2016" format
3. Go to View this SQL Icon -> Convert Question to SQL -> Re-Run
4. Notice the dates are in "April 24, 2016 " format
5. Tooltip Granularity is lost
**Expected behavior**
Same behavior is expected from both Question and Native SQL. This issue got introduced in 44 since previously to this version they where experiencing similar outcome. In version 43 the output was as following:
<img width="1487" alt="image" src="https://user-images.githubusercontent.com/110378427/186657468-4322c2f6-9607-48f9-99bc-db87fba5685a.png">
| priority | tooltip periods are not displayed nicely on sql questions describe the bug when you group by week month on editor the result is a range img width alt image src if you take the same question and turn it into sql the tooltip doesn t pick up the range granularity img width alt image src to reproduce steps to reproduce the behavior go to new question sample database orders summarise count group by created at choose week notice the preview dates are in april – april format go to view this sql icon convert question to sql re run notice the dates are in april format tooltip granularity is lost expected behavior same behavior is expected from both question and native sql this issue got introduced in since previously to this version they where experiencing similar outcome in version the output was as following img width alt image src | 1 |
12,337 | 14,882,738,426 | IssuesEvent | 2021-01-20 12:20:36 | GoogleCloudPlatform/fda-mystudies | https://api.github.com/repos/GoogleCloudPlatform/fda-mystudies | closed | [Mobile] [Dev] Unable to rejoin into Open study once withdrawn | Blocker Bug P0 Process: Dev Process: Fixed Process: Tested dev Unknown backend | Unable to rejoin into Open study once withdrawn for Android and iOS
| 3.0 | [Mobile] [Dev] Unable to rejoin into Open study once withdrawn - Unable to rejoin into Open study once withdrawn for Android and iOS
| non_priority | unable to rejoin into open study once withdrawn unable to rejoin into open study once withdrawn for android and ios | 0 |
243,856 | 26,290,655,143 | IssuesEvent | 2023-01-08 11:20:46 | TreyM-WSS/concord | https://api.github.com/repos/TreyM-WSS/concord | reopened | CVE-2021-38153 (Medium) detected in kafka-clients-2.4.0.jar | security vulnerability | ## CVE-2021-38153 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>kafka-clients-2.4.0.jar</b></p></summary>
<p></p>
<p>Library home page: <a href="https://kafka.apache.org">https://kafka.apache.org</a></p>
<p>Path to dependency file: /server/plugins/kafka-event-sink/pom.xml</p>
<p>Path to vulnerable library: /canner/.m2/repository/org/apache/kafka/kafka-clients/2.4.0/kafka-clients-2.4.0.jar</p>
<p>
Dependency Hierarchy:
- :x: **kafka-clients-2.4.0.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/TreyM-WSS/concord/commit/a0a888b3b97fbcfb092cc1f80f98558cfea2d71f">a0a888b3b97fbcfb092cc1f80f98558cfea2d71f</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>
Some components in Apache Kafka use `Arrays.equals` to validate a password or key, which is vulnerable to timing attacks that make brute force attacks for such credentials more likely to be successful. Users should upgrade to 2.8.1 or higher, or 3.0.0 or higher where this vulnerability has been fixed. The affected versions include Apache Kafka 2.0.0, 2.0.1, 2.1.0, 2.1.1, 2.2.0, 2.2.1, 2.2.2, 2.3.0, 2.3.1, 2.4.0, 2.4.1, 2.5.0, 2.5.1, 2.6.0, 2.6.1, 2.6.2, 2.7.0, 2.7.1, and 2.8.0.
<p>Publish Date: 2021-09-22
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2021-38153>CVE-2021-38153</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.9</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: None
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-38153">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-38153</a></p>
<p>Release Date: 2021-09-22</p>
<p>Fix Resolution: 2.6.3</p>
</p>
</details>
<p></p>
***
:rescue_worker_helmet: Automatic Remediation is available for this issue | True | CVE-2021-38153 (Medium) detected in kafka-clients-2.4.0.jar - ## CVE-2021-38153 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>kafka-clients-2.4.0.jar</b></p></summary>
<p></p>
<p>Library home page: <a href="https://kafka.apache.org">https://kafka.apache.org</a></p>
<p>Path to dependency file: /server/plugins/kafka-event-sink/pom.xml</p>
<p>Path to vulnerable library: /canner/.m2/repository/org/apache/kafka/kafka-clients/2.4.0/kafka-clients-2.4.0.jar</p>
<p>
Dependency Hierarchy:
- :x: **kafka-clients-2.4.0.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/TreyM-WSS/concord/commit/a0a888b3b97fbcfb092cc1f80f98558cfea2d71f">a0a888b3b97fbcfb092cc1f80f98558cfea2d71f</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>
Some components in Apache Kafka use `Arrays.equals` to validate a password or key, which is vulnerable to timing attacks that make brute force attacks for such credentials more likely to be successful. Users should upgrade to 2.8.1 or higher, or 3.0.0 or higher where this vulnerability has been fixed. The affected versions include Apache Kafka 2.0.0, 2.0.1, 2.1.0, 2.1.1, 2.2.0, 2.2.1, 2.2.2, 2.3.0, 2.3.1, 2.4.0, 2.4.1, 2.5.0, 2.5.1, 2.6.0, 2.6.1, 2.6.2, 2.7.0, 2.7.1, and 2.8.0.
<p>Publish Date: 2021-09-22
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2021-38153>CVE-2021-38153</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.9</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: None
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-38153">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-38153</a></p>
<p>Release Date: 2021-09-22</p>
<p>Fix Resolution: 2.6.3</p>
</p>
</details>
<p></p>
***
:rescue_worker_helmet: Automatic Remediation is available for this issue | non_priority | cve medium detected in kafka clients jar cve medium severity vulnerability vulnerable library kafka clients jar library home page a href path to dependency file server plugins kafka event sink pom xml path to vulnerable library canner repository org apache kafka kafka clients kafka clients jar dependency hierarchy x kafka clients jar vulnerable library found in head commit a href found in base branch master vulnerability details some components in apache kafka use arrays equals to validate a password or key which is vulnerable to timing attacks that make brute force attacks for such credentials more likely to be successful users should upgrade to or higher or or higher where this vulnerability has been fixed the affected versions include apache kafka and publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity high privileges required none user interaction none scope unchanged impact metrics confidentiality impact high integrity impact none availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution rescue worker helmet automatic remediation is available for this issue | 0 |
391,573 | 11,575,921,405 | IssuesEvent | 2020-02-21 10:46:09 | ahmedkaludi/accelerated-mobile-pages | https://api.github.com/repos/ahmedkaludi/accelerated-mobile-pages | closed | Warning issue on AMP option panel. | NEXT UPDATE [Priority: HIGH] bug | /var/www/html/wp-content/plugins/accelerated-mobile-pages/includes/ampforwp-fields-array.php on line 122
ref) https://secure.helpscout.net/conversation/1059605973/107207?folderId=3514643 | 1.0 | Warning issue on AMP option panel. - /var/www/html/wp-content/plugins/accelerated-mobile-pages/includes/ampforwp-fields-array.php on line 122
ref) https://secure.helpscout.net/conversation/1059605973/107207?folderId=3514643 | priority | warning issue on amp option panel var www html wp content plugins accelerated mobile pages includes ampforwp fields array php on line ref | 1 |
315,086 | 9,606,491,817 | IssuesEvent | 2019-05-11 10:51:32 | yalla-coop/connect5 | https://api.github.com/repos/yalla-coop/connect5 | opened | Trainer: Update Create Session | priority-5 sprint2 trainer | Re-use existing functionality but add
- [ ] region (required)
- [ ] partner trainer field
- [ ] email of participants -> attendee list
- [ ] email survey functionality by ticking box 'send the survey to participants by email'
<img width="150" alt="Bildschirmfoto 2019-05-11 um 12 50 51" src="https://user-images.githubusercontent.com/23721486/57568707-6cb7bb80-73eb-11e9-86d7-b6454f1920b8.png">
| 1.0 | Trainer: Update Create Session - Re-use existing functionality but add
- [ ] region (required)
- [ ] partner trainer field
- [ ] email of participants -> attendee list
- [ ] email survey functionality by ticking box 'send the survey to participants by email'
<img width="150" alt="Bildschirmfoto 2019-05-11 um 12 50 51" src="https://user-images.githubusercontent.com/23721486/57568707-6cb7bb80-73eb-11e9-86d7-b6454f1920b8.png">
| priority | trainer update create session re use existing functionality but add region required partner trainer field email of participants attendee list email survey functionality by ticking box send the survey to participants by email img width alt bildschirmfoto um src | 1 |
799,284 | 28,303,690,585 | IssuesEvent | 2023-04-10 08:51:36 | webcompat/web-bugs | https://api.github.com/repos/webcompat/web-bugs | closed | m.youtube.com - see bug description | browser-firefox-mobile priority-critical engine-gecko | <!-- @browser: Firefox Mobile 88.0 -->
<!-- @ua_header: Mozilla/5.0 (Android 10; Mobile; rv:88.0) Gecko/88.0 Firefox/88.0 -->
<!-- @reported_with: unknown -->
<!-- @public_url: https://github.com/webcompat/web-bugs/issues/120636 -->
**URL**: https://m.youtube.com/results?sp=mAEA
**Browser / Version**: Firefox Mobile 88.0
**Operating System**: Android 10
**Tested Another Browser**: Yes Other
**Problem type**: Something else
**Description**: All of the YouTube shorts are not diverse enough. Repetitive and silly. There is no way to change what I can view.
**Steps to Reproduce**:
I just keep seeing the same YouTube shorts over and over again and it is only when I view them here. If I use As block browser they are different but also repetitive.
<details>
<summary>Browser Configuration</summary>
<ul>
<li>None</li>
</ul>
</details>
_From [webcompat.com](https://webcompat.com/) with ❤️_ | 1.0 | m.youtube.com - see bug description - <!-- @browser: Firefox Mobile 88.0 -->
<!-- @ua_header: Mozilla/5.0 (Android 10; Mobile; rv:88.0) Gecko/88.0 Firefox/88.0 -->
<!-- @reported_with: unknown -->
<!-- @public_url: https://github.com/webcompat/web-bugs/issues/120636 -->
**URL**: https://m.youtube.com/results?sp=mAEA
**Browser / Version**: Firefox Mobile 88.0
**Operating System**: Android 10
**Tested Another Browser**: Yes Other
**Problem type**: Something else
**Description**: All of the YouTube shorts are not diverse enough. Repetitive and silly. There is no way to change what I can view.
**Steps to Reproduce**:
I just keep seeing the same YouTube shorts over and over again and it is only when I view them here. If I use As block browser they are different but also repetitive.
<details>
<summary>Browser Configuration</summary>
<ul>
<li>None</li>
</ul>
</details>
_From [webcompat.com](https://webcompat.com/) with ❤️_ | priority | m youtube com see bug description url browser version firefox mobile operating system android tested another browser yes other problem type something else description all of the youtube shorts are not diverse enough repetitive and silly there is no way to change what i can view steps to reproduce i just keep seeing the same youtube shorts over and over again and it is only when i view them here if i use as block browser they are different but also repetitive browser configuration none from with ❤️ | 1 |
219,079 | 7,333,119,123 | IssuesEvent | 2018-03-05 18:22:52 | NCEAS/metacat | https://api.github.com/repos/NCEAS/metacat | closed | Metacat DataONE base url always gets 404 not found page | Component: Bugzilla-Id Priority: Normal Status: Closed Tracker: Bug | ---
Author Name: **Jing Tao** (Jing Tao)
Original Redmine Issue: 7166, https://projects.ecoinformatics.org/ecoinfo/issues/7166
Original Date: 2016-12-06
Original Assignee: Jing Tao
---
The base url looks like:
https://mn-dev-ucsb-1.test.dataone.org/metacat/d1/mn
It always gets 404 not found page. Even though Metacat on this node is running, users always think something is wrong. We need this url display the node information.
| 1.0 | Metacat DataONE base url always gets 404 not found page - ---
Author Name: **Jing Tao** (Jing Tao)
Original Redmine Issue: 7166, https://projects.ecoinformatics.org/ecoinfo/issues/7166
Original Date: 2016-12-06
Original Assignee: Jing Tao
---
The base url looks like:
https://mn-dev-ucsb-1.test.dataone.org/metacat/d1/mn
It always gets 404 not found page. Even though Metacat on this node is running, users always think something is wrong. We need this url display the node information.
| priority | metacat dataone base url always gets not found page author name jing tao jing tao original redmine issue original date original assignee jing tao the base url looks like it always gets not found page even though metacat on this node is running users always think something is wrong we need this url display the node information | 1 |
83,034 | 15,683,782,977 | IssuesEvent | 2021-03-25 09:13:11 | bci-oss/vulnerable-node | https://api.github.com/repos/bci-oss/vulnerable-node | opened | CVE-2017-1000048 (High) detected in qs-4.0.0.tgz | security vulnerability | ## CVE-2017-1000048 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>qs-4.0.0.tgz</b></p></summary>
<p>A querystring parser that supports nesting and arrays, with a depth limit</p>
<p>Library home page: <a href="https://registry.npmjs.org/qs/-/qs-4.0.0.tgz">https://registry.npmjs.org/qs/-/qs-4.0.0.tgz</a></p>
<p>Path to dependency file: vulnerable-node/package.json</p>
<p>Path to vulnerable library: vulnerable-node/node_modules/qs/package.json</p>
<p>
Dependency Hierarchy:
- body-parser-1.13.3.tgz (Root Library)
- :x: **qs-4.0.0.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/bci-oss/vulnerable-node/commit/70c2a0e524ee358d41b228e329ed7627fa352fcf">70c2a0e524ee358d41b228e329ed7627fa352fcf</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 web framework using ljharb's qs module older than v6.3.2, v6.2.3, v6.1.2, and v6.0.4 is vulnerable to a DoS. A malicious user can send a evil request to cause the web framework crash.
<p>Publish Date: 2017-07-17
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2017-1000048>CVE-2017-1000048</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-1000048">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-1000048</a></p>
<p>Release Date: 2017-07-17</p>
<p>Fix Resolution: qs - 6.0.4,6.1.2,6.2.3,6.3.2</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"qs","packageVersion":"4.0.0","packageFilePaths":["/package.json"],"isTransitiveDependency":true,"dependencyTree":"body-parser:1.13.3;qs:4.0.0","isMinimumFixVersionAvailable":true,"minimumFixVersion":"qs - 6.0.4,6.1.2,6.2.3,6.3.2"}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2017-1000048","vulnerabilityDetails":"the web framework using ljharb\u0027s qs module older than v6.3.2, v6.2.3, v6.1.2, and v6.0.4 is vulnerable to a DoS. A malicious user can send a evil request to cause the web framework crash.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2017-1000048","cvss3Severity":"high","cvss3Score":"7.5","cvss3Metrics":{"A":"High","AC":"Low","PR":"None","S":"Unchanged","C":"None","UI":"None","AV":"Network","I":"None"},"extraData":{}}</REMEDIATE> --> | True | CVE-2017-1000048 (High) detected in qs-4.0.0.tgz - ## CVE-2017-1000048 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>qs-4.0.0.tgz</b></p></summary>
<p>A querystring parser that supports nesting and arrays, with a depth limit</p>
<p>Library home page: <a href="https://registry.npmjs.org/qs/-/qs-4.0.0.tgz">https://registry.npmjs.org/qs/-/qs-4.0.0.tgz</a></p>
<p>Path to dependency file: vulnerable-node/package.json</p>
<p>Path to vulnerable library: vulnerable-node/node_modules/qs/package.json</p>
<p>
Dependency Hierarchy:
- body-parser-1.13.3.tgz (Root Library)
- :x: **qs-4.0.0.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/bci-oss/vulnerable-node/commit/70c2a0e524ee358d41b228e329ed7627fa352fcf">70c2a0e524ee358d41b228e329ed7627fa352fcf</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 web framework using ljharb's qs module older than v6.3.2, v6.2.3, v6.1.2, and v6.0.4 is vulnerable to a DoS. A malicious user can send a evil request to cause the web framework crash.
<p>Publish Date: 2017-07-17
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2017-1000048>CVE-2017-1000048</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-1000048">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-1000048</a></p>
<p>Release Date: 2017-07-17</p>
<p>Fix Resolution: qs - 6.0.4,6.1.2,6.2.3,6.3.2</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"qs","packageVersion":"4.0.0","packageFilePaths":["/package.json"],"isTransitiveDependency":true,"dependencyTree":"body-parser:1.13.3;qs:4.0.0","isMinimumFixVersionAvailable":true,"minimumFixVersion":"qs - 6.0.4,6.1.2,6.2.3,6.3.2"}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2017-1000048","vulnerabilityDetails":"the web framework using ljharb\u0027s qs module older than v6.3.2, v6.2.3, v6.1.2, and v6.0.4 is vulnerable to a DoS. A malicious user can send a evil request to cause the web framework crash.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2017-1000048","cvss3Severity":"high","cvss3Score":"7.5","cvss3Metrics":{"A":"High","AC":"Low","PR":"None","S":"Unchanged","C":"None","UI":"None","AV":"Network","I":"None"},"extraData":{}}</REMEDIATE> --> | non_priority | cve high detected in qs tgz cve high severity vulnerability vulnerable library qs tgz a querystring parser that supports nesting and arrays with a depth limit library home page a href path to dependency file vulnerable node package json path to vulnerable library vulnerable node node modules qs package json dependency hierarchy body parser tgz root library x qs tgz vulnerable library found in head commit a href found in base branch master vulnerability details the web framework using ljharb s qs module older than and is vulnerable to a dos a malicious user can send a evil request to cause the web framework crash publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact none integrity impact none availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution qs isopenpronvulnerability true ispackagebased true isdefaultbranch true packages istransitivedependency true dependencytree body parser qs isminimumfixversionavailable true minimumfixversion qs basebranches vulnerabilityidentifier cve vulnerabilitydetails the web framework using ljharb qs module older than and is vulnerable to a dos a malicious user can send a evil request to cause the web framework crash vulnerabilityurl | 0 |
29,825 | 11,780,066,635 | IssuesEvent | 2020-03-16 19:16:23 | kyma-project/kyma | https://api.github.com/repos/kyma-project/kyma | closed | Move out API server proxy from core chart to separate release | area/security enhancement | <!-- Thank you for your contribution. Before you submit the issue:
1. Search open and closed issues for duplicates.
2. Read the contributing guidelines.
-->
**Description**
API server proxy is part of chart `core` which is an umbrella chart for other componetns as well such as iam-kubeconfig, console, console backend etc.
Problem is, that if something will fail with apiserver proxy installation, for example,issuing certificate on Gardener will not work because domain is too long, whole release core is retried and after 5 times it fails with manual action needed. Now cluster admin needs to take manual actions in order to "fix" apiserver proxy but at the same time helm will complain that release core already exists and the fixing party begins. It's a very tedious process. API server proxy should be a standalone release. If it fails and admin should have easy steps to reinstall, even if it requires helm delete action as proxy is stateless.
- Local and cluster installation CR should be updated
- Docs updated if needed
- Tests moved if required
<!-- Provide a clear and concise description of the feature. -->
**Reasons**
Simplify core umbrella release, simplify installation and potential cluster ops for install/upgrade.
Now upgrading core if it fails on apiserver proxy may have a huge impact on other components.
<!-- Explain why we should add this feature. Provide use cases to illustrate its benefits. -->
**Attachments**
<!-- Attach any files, links, code samples, or screenshots that will convince us to your idea. -->
| True | Move out API server proxy from core chart to separate release - <!-- Thank you for your contribution. Before you submit the issue:
1. Search open and closed issues for duplicates.
2. Read the contributing guidelines.
-->
**Description**
API server proxy is part of chart `core` which is an umbrella chart for other componetns as well such as iam-kubeconfig, console, console backend etc.
Problem is, that if something will fail with apiserver proxy installation, for example,issuing certificate on Gardener will not work because domain is too long, whole release core is retried and after 5 times it fails with manual action needed. Now cluster admin needs to take manual actions in order to "fix" apiserver proxy but at the same time helm will complain that release core already exists and the fixing party begins. It's a very tedious process. API server proxy should be a standalone release. If it fails and admin should have easy steps to reinstall, even if it requires helm delete action as proxy is stateless.
- Local and cluster installation CR should be updated
- Docs updated if needed
- Tests moved if required
<!-- Provide a clear and concise description of the feature. -->
**Reasons**
Simplify core umbrella release, simplify installation and potential cluster ops for install/upgrade.
Now upgrading core if it fails on apiserver proxy may have a huge impact on other components.
<!-- Explain why we should add this feature. Provide use cases to illustrate its benefits. -->
**Attachments**
<!-- Attach any files, links, code samples, or screenshots that will convince us to your idea. -->
| non_priority | move out api server proxy from core chart to separate release thank you for your contribution before you submit the issue search open and closed issues for duplicates read the contributing guidelines description api server proxy is part of chart core which is an umbrella chart for other componetns as well such as iam kubeconfig console console backend etc problem is that if something will fail with apiserver proxy installation for example issuing certificate on gardener will not work because domain is too long whole release core is retried and after times it fails with manual action needed now cluster admin needs to take manual actions in order to fix apiserver proxy but at the same time helm will complain that release core already exists and the fixing party begins it s a very tedious process api server proxy should be a standalone release if it fails and admin should have easy steps to reinstall even if it requires helm delete action as proxy is stateless local and cluster installation cr should be updated docs updated if needed tests moved if required reasons simplify core umbrella release simplify installation and potential cluster ops for install upgrade now upgrading core if it fails on apiserver proxy may have a huge impact on other components attachments | 0 |
684,264 | 23,412,988,069 | IssuesEvent | 2022-08-12 19:48:13 | brave/brave-browser | https://api.github.com/repos/brave/brave-browser | closed | Wallet is using an obsolete password policy | security priority/P3 feature/wallet OS/Desktop | Wallet currently requires the following password policy:
which is not in line with the [latest password policy guidelines from NIST](https://en.wikipedia.org/wiki/Password_policy#2017).
In particular, the following changes should be made:
- minimum length must be 8 characters
- different character types should not be required
(Also see https://auth0.com/blog/dont-pass-on-the-new-nist-password-guidelines/ for an explanation of the changes in NIST recommendations.) | 1.0 | Wallet is using an obsolete password policy - Wallet currently requires the following password policy:
which is not in line with the [latest password policy guidelines from NIST](https://en.wikipedia.org/wiki/Password_policy#2017).
In particular, the following changes should be made:
- minimum length must be 8 characters
- different character types should not be required
(Also see https://auth0.com/blog/dont-pass-on-the-new-nist-password-guidelines/ for an explanation of the changes in NIST recommendations.) | priority | wallet is using an obsolete password policy wallet currently requires the following password policy which is not in line with the in particular the following changes should be made minimum length must be characters different character types should not be required also see for an explanation of the changes in nist recommendations | 1 |
59,585 | 7,262,100,835 | IssuesEvent | 2018-02-19 03:08:07 | pawgistics/pawgistics | https://api.github.com/repos/pawgistics/pawgistics | closed | Email standardization | design decision enhancement | Emails should be all lowercase (or some other standardized format) before writing to db | 1.0 | Email standardization - Emails should be all lowercase (or some other standardized format) before writing to db | non_priority | email standardization emails should be all lowercase or some other standardized format before writing to db | 0 |
96,816 | 3,973,764,256 | IssuesEvent | 2016-05-04 19:45:50 | Metaswitch/sprout | https://api.github.com/repos/Metaswitch/sprout | closed | stack_data's name array is not necessarily big enough | bug medium-priority | #### Symptoms
The array was originally of size 16, and we were writing more than 16 names to it which was causing us to scribble on other fields.
#### Impact
Random failures due to fields being set to gibberish.
#### Release and environment
Release 95
#### Steps to reproduce
Add loads of aliases? | 1.0 | stack_data's name array is not necessarily big enough - #### Symptoms
The array was originally of size 16, and we were writing more than 16 names to it which was causing us to scribble on other fields.
#### Impact
Random failures due to fields being set to gibberish.
#### Release and environment
Release 95
#### Steps to reproduce
Add loads of aliases? | priority | stack data s name array is not necessarily big enough symptoms the array was originally of size and we were writing more than names to it which was causing us to scribble on other fields impact random failures due to fields being set to gibberish release and environment release steps to reproduce add loads of aliases | 1 |
54,122 | 6,366,194,256 | IssuesEvent | 2017-08-01 00:29:16 | appium/appium | https://api.github.com/repos/appium/appium | closed | WDA Retrying to launch app but fails because App not showing in simulator intermittently | ThirdpartyIssue XCUITest | ## The problem
Automation scripts work fine on for some time during execution but after a couple of tests the appium checks if the app is installed in the simulator, the logs say it's installed and but looks like the app is not installed in the simulator.
## Environment
* Appium version (or git revision) that exhibits the issue: 1.6.5
* Desktop OS/version used to run Appium: OS EL Capitan 10.11.6
* Node.js version (unless using Appium.app|exe): 6.10.2
* Mobile platform/version under test: iOS SDK set to 10.3 XCode set to 8.3.3
* Real device or emulator/simulator: Simulator 10.2
* Appium CLI or Appium.app|exe: CLI launched through appium-java
## Details
Our scripts uninstall the app before every script execution and launch the app using launchApp. We also use noReset - true, fullReset - False. We have a need to reinstall the app before every script. The script works with the provided app file for 10 + scenarios but post that the automation starts breaking because the app is not available in the simulator but the logs say otherwise.
`Capabilities [{app=/Users/devops/jenkins_home/workspace/AQA_Regression_test/GROUP/checkout/PLATFORM/ios/SITE/ZZZ/label/android_smoke/qaautomation/ZZZ.app, networkConnectionEnabled=false, noReset=true, scaleFactor=0.5, recordVideo=true, databaseEnabled=false, deviceName=iPhone 7, fullReset=false, iosInstallPause=8000, platform=MAC, showXcodeLog=true, sendKeyStrategy=grouped, newCommandTimeout=900, platformVersion=10.2, webStorageEnabled=false, locationContextEnabled=false, browserName=, takesScreenshot=true, javascriptEnabled=true, recordScreenshots=true, platformName=iOS, udid=D4ECE422-0044-4BB6-A201-ECE5F7A1579E}]`
## Link to Appium logs
Includes XcodeLog
https://gist.github.com/mmurali88/340f50ea4dcf3d760f2281a265a4e46b
Simulator Log
https://gist.github.com/mmurali88/ffd23651bd4dc329f74dd901c28dcf8c
@mykola-mokhnach Added simulator log for your verification. | 1.0 | WDA Retrying to launch app but fails because App not showing in simulator intermittently - ## The problem
Automation scripts work fine on for some time during execution but after a couple of tests the appium checks if the app is installed in the simulator, the logs say it's installed and but looks like the app is not installed in the simulator.
## Environment
* Appium version (or git revision) that exhibits the issue: 1.6.5
* Desktop OS/version used to run Appium: OS EL Capitan 10.11.6
* Node.js version (unless using Appium.app|exe): 6.10.2
* Mobile platform/version under test: iOS SDK set to 10.3 XCode set to 8.3.3
* Real device or emulator/simulator: Simulator 10.2
* Appium CLI or Appium.app|exe: CLI launched through appium-java
## Details
Our scripts uninstall the app before every script execution and launch the app using launchApp. We also use noReset - true, fullReset - False. We have a need to reinstall the app before every script. The script works with the provided app file for 10 + scenarios but post that the automation starts breaking because the app is not available in the simulator but the logs say otherwise.
`Capabilities [{app=/Users/devops/jenkins_home/workspace/AQA_Regression_test/GROUP/checkout/PLATFORM/ios/SITE/ZZZ/label/android_smoke/qaautomation/ZZZ.app, networkConnectionEnabled=false, noReset=true, scaleFactor=0.5, recordVideo=true, databaseEnabled=false, deviceName=iPhone 7, fullReset=false, iosInstallPause=8000, platform=MAC, showXcodeLog=true, sendKeyStrategy=grouped, newCommandTimeout=900, platformVersion=10.2, webStorageEnabled=false, locationContextEnabled=false, browserName=, takesScreenshot=true, javascriptEnabled=true, recordScreenshots=true, platformName=iOS, udid=D4ECE422-0044-4BB6-A201-ECE5F7A1579E}]`
## Link to Appium logs
Includes XcodeLog
https://gist.github.com/mmurali88/340f50ea4dcf3d760f2281a265a4e46b
Simulator Log
https://gist.github.com/mmurali88/ffd23651bd4dc329f74dd901c28dcf8c
@mykola-mokhnach Added simulator log for your verification. | non_priority | wda retrying to launch app but fails because app not showing in simulator intermittently the problem automation scripts work fine on for some time during execution but after a couple of tests the appium checks if the app is installed in the simulator the logs say it s installed and but looks like the app is not installed in the simulator environment appium version or git revision that exhibits the issue desktop os version used to run appium os el capitan node js version unless using appium app exe mobile platform version under test ios sdk set to xcode set to real device or emulator simulator simulator appium cli or appium app exe cli launched through appium java details our scripts uninstall the app before every script execution and launch the app using launchapp we also use noreset true fullreset false we have a need to reinstall the app before every script the script works with the provided app file for scenarios but post that the automation starts breaking because the app is not available in the simulator but the logs say otherwise capabilities link to appium logs includes xcodelog simulator log mykola mokhnach added simulator log for your verification | 0 |
156,381 | 12,308,062,801 | IssuesEvent | 2020-05-12 06:23:52 | Azure/sonic-swss | https://api.github.com/repos/Azure/sonic-swss | closed | VLAN vs tests unstable | Cleanup :droplet: Testing | The following VLAN vs tests are marginal at the moment:
- test_RemoveVlanWithRouterInterface
- test_AddPortChannelToVlan
This causes the suite to fail ~40-50% of the time across the swss and utilities tests, as well as the nightly swss build.
For now we can mark the tests as xfail in pytest so that the failures are not blocking PRs, but they need to be stabilized and put back into the test suite. | 1.0 | VLAN vs tests unstable - The following VLAN vs tests are marginal at the moment:
- test_RemoveVlanWithRouterInterface
- test_AddPortChannelToVlan
This causes the suite to fail ~40-50% of the time across the swss and utilities tests, as well as the nightly swss build.
For now we can mark the tests as xfail in pytest so that the failures are not blocking PRs, but they need to be stabilized and put back into the test suite. | non_priority | vlan vs tests unstable the following vlan vs tests are marginal at the moment test removevlanwithrouterinterface test addportchanneltovlan this causes the suite to fail of the time across the swss and utilities tests as well as the nightly swss build for now we can mark the tests as xfail in pytest so that the failures are not blocking prs but they need to be stabilized and put back into the test suite | 0 |
437,453 | 30,599,952,981 | IssuesEvent | 2023-07-22 08:33:32 | snapsinazfs/snapsinazfs | https://api.github.com/repos/snapsinazfs/snapsinazfs | closed | Add more man pages and improve existing man pages | documentation | While writing updated man pages for the current beta, I saw a few places where additional documentation could be of use.
While I'm writing those man pages, I am including references to the additional documentation, which does not yet exist.
This issue is for tracking work on man pages, including updating the current man pages as well as adding new man pages.
I'm unhappy with the limitations of pandoc, with regards to its translation of markdown to the desired output format, so, currently, I am writing the snapsinazfs(8) and snapsinazfs(5) man pages from scratch, in groff format (instead of the current markdown sources).
I'm re-using a lot of the original content, but also significantly expanding upon it, while also bringing the man pages into much closer conformance with suggested standard man page format/practices as documented in groff_man(7), man(7), groff(7), and other relevant documents that describe standard man format/practices.
Currently, the additional man pages I've made reference to are:
- snapsinazfs-zfsprops(7)
- snapsinazfs-config-console(8)
- snapsinazfs-api(3) | 1.0 | Add more man pages and improve existing man pages - While writing updated man pages for the current beta, I saw a few places where additional documentation could be of use.
While I'm writing those man pages, I am including references to the additional documentation, which does not yet exist.
This issue is for tracking work on man pages, including updating the current man pages as well as adding new man pages.
I'm unhappy with the limitations of pandoc, with regards to its translation of markdown to the desired output format, so, currently, I am writing the snapsinazfs(8) and snapsinazfs(5) man pages from scratch, in groff format (instead of the current markdown sources).
I'm re-using a lot of the original content, but also significantly expanding upon it, while also bringing the man pages into much closer conformance with suggested standard man page format/practices as documented in groff_man(7), man(7), groff(7), and other relevant documents that describe standard man format/practices.
Currently, the additional man pages I've made reference to are:
- snapsinazfs-zfsprops(7)
- snapsinazfs-config-console(8)
- snapsinazfs-api(3) | non_priority | add more man pages and improve existing man pages while writing updated man pages for the current beta i saw a few places where additional documentation could be of use while i m writing those man pages i am including references to the additional documentation which does not yet exist this issue is for tracking work on man pages including updating the current man pages as well as adding new man pages i m unhappy with the limitations of pandoc with regards to its translation of markdown to the desired output format so currently i am writing the snapsinazfs and snapsinazfs man pages from scratch in groff format instead of the current markdown sources i m re using a lot of the original content but also significantly expanding upon it while also bringing the man pages into much closer conformance with suggested standard man page format practices as documented in groff man man groff and other relevant documents that describe standard man format practices currently the additional man pages i ve made reference to are snapsinazfs zfsprops snapsinazfs config console snapsinazfs api | 0 |
126,227 | 16,992,508,920 | IssuesEvent | 2021-06-30 23:04:22 | phetsims/number-line-distance | https://api.github.com/repos/phetsims/number-line-distance | closed | Elevation Scene Distance Description for Absolute Distance | design:interviews | In the elevation scene of NLD, when both point controllers are placed and the distance type is absolute value, the distance description reads `The fish and the bird are [dy] meters apart.`. This distance statement reflects their difference in y-levels, which makes sense in the context of the numberline. However, the fish and the bird aren't actually necessarily that distance apart as they could have different x-levels. In both of the screenshots below, the distance description says they are 1 meter apart when both images have different distances between the point controllers.
This issue doesn't seem major to me, as the intention seems clear regardless, but I was just wondering if this was worth addressing or if maybe there were some better language for describing the difference of their y-values.
| 1.0 | Elevation Scene Distance Description for Absolute Distance - In the elevation scene of NLD, when both point controllers are placed and the distance type is absolute value, the distance description reads `The fish and the bird are [dy] meters apart.`. This distance statement reflects their difference in y-levels, which makes sense in the context of the numberline. However, the fish and the bird aren't actually necessarily that distance apart as they could have different x-levels. In both of the screenshots below, the distance description says they are 1 meter apart when both images have different distances between the point controllers.
This issue doesn't seem major to me, as the intention seems clear regardless, but I was just wondering if this was worth addressing or if maybe there were some better language for describing the difference of their y-values.
| non_priority | elevation scene distance description for absolute distance in the elevation scene of nld when both point controllers are placed and the distance type is absolute value the distance description reads the fish and the bird are meters apart this distance statement reflects their difference in y levels which makes sense in the context of the numberline however the fish and the bird aren t actually necessarily that distance apart as they could have different x levels in both of the screenshots below the distance description says they are meter apart when both images have different distances between the point controllers this issue doesn t seem major to me as the intention seems clear regardless but i was just wondering if this was worth addressing or if maybe there were some better language for describing the difference of their y values | 0 |
64,618 | 14,671,312,929 | IssuesEvent | 2020-12-30 07:49:17 | shaimael/C-sample-project-for-VSC | https://api.github.com/repos/shaimael/C-sample-project-for-VSC | opened | CVE-2019-0548 (High) detected in multiple libraries | security vulnerability | ## CVE-2019-0548 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>microsoft.netcore.dotnethostresolver.2.1.0.nupkg</b>, <b>microsoft.netcore.dotnetapphost.2.1.0.nupkg</b>, <b>microsoft.netcore.app.2.1.0.nupkg</b>, <b>microsoft.netcore.dotnethostpolicy.2.1.0.nupkg</b></p></summary>
<p>
<details><summary><b>microsoft.netcore.dotnethostresolver.2.1.0.nupkg</b></p></summary>
<p>Provides an implementation of framework resolution strategy used by Microsoft.NETCore.DotNetHost
ca...</p>
<p>Library home page: <a href="https://api.nuget.org/packages/microsoft.netcore.dotnethostresolver.2.1.0.nupkg">https://api.nuget.org/packages/microsoft.netcore.dotnethostresolver.2.1.0.nupkg</a></p>
<p>
Dependency Hierarchy:
- microsoft.netcore.app.2.1.0.nupkg (Root Library)
- microsoft.netcore.dotnethostpolicy.2.1.0.nupkg
- :x: **microsoft.netcore.dotnethostresolver.2.1.0.nupkg** (Vulnerable Library)
</details>
<details><summary><b>microsoft.netcore.dotnetapphost.2.1.0.nupkg</b></p></summary>
<p>Provides the .NET Core app bootstrapper intended for use in the application directory
caa7b7e2bad98...</p>
<p>Library home page: <a href="https://api.nuget.org/packages/microsoft.netcore.dotnetapphost.2.1.0.nupkg">https://api.nuget.org/packages/microsoft.netcore.dotnetapphost.2.1.0.nupkg</a></p>
<p>
Dependency Hierarchy:
- microsoft.netcore.app.2.1.0.nupkg (Root Library)
- microsoft.netcore.dotnethostpolicy.2.1.0.nupkg
- microsoft.netcore.dotnethostresolver.2.1.0.nupkg
- :x: **microsoft.netcore.dotnetapphost.2.1.0.nupkg** (Vulnerable Library)
</details>
<details><summary><b>microsoft.netcore.app.2.1.0.nupkg</b></p></summary>
<p>A set of .NET API's that are included in the default .NET Core application model.
caa7b7e2bad98e56a...</p>
<p>Library home page: <a href="https://api.nuget.org/packages/microsoft.netcore.app.2.1.0.nupkg">https://api.nuget.org/packages/microsoft.netcore.app.2.1.0.nupkg</a></p>
<p>
Dependency Hierarchy:
- :x: **microsoft.netcore.app.2.1.0.nupkg** (Vulnerable Library)
</details>
<details><summary><b>microsoft.netcore.dotnethostpolicy.2.1.0.nupkg</b></p></summary>
<p>Provides a CoreCLR hosting policy implementation -- configuration settings, assembly paths and assem...</p>
<p>Library home page: <a href="https://api.nuget.org/packages/microsoft.netcore.dotnethostpolicy.2.1.0.nupkg">https://api.nuget.org/packages/microsoft.netcore.dotnethostpolicy.2.1.0.nupkg</a></p>
<p>
Dependency Hierarchy:
- microsoft.netcore.app.2.1.0.nupkg (Root Library)
- :x: **microsoft.netcore.dotnethostpolicy.2.1.0.nupkg** (Vulnerable Library)
</details>
<p>Found in HEAD commit: <a href="https://github.com/shaimael/C-sample-project-for-VSC/commit/64548f73555b19a972f2f4748c74469a037e1bd1">64548f73555b19a972f2f4748c74469a037e1bd1</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 denial of service vulnerability exists when ASP.NET Core improperly handles web requests, aka "ASP.NET Core Denial of Service Vulnerability." This affects ASP.NET Core 2.2, ASP.NET Core 2.1. This CVE ID is unique from CVE-2019-0564.
<p>Publish Date: 2019-01-08
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-0548>CVE-2019-0548</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/aspnet/Announcements/issues/335">https://github.com/aspnet/Announcements/issues/335</a></p>
<p>Release Date: 2019-01-08</p>
<p>Fix Resolution: Microsoft.AspNetCore.SignalR - 1.1.0; Microsoft.AspNetCore.Server.Kestrel.Transport.Sockets - 2.2.1; Microsoft.AspNetCore.Server.IIS - 2.2.1; Microsoft.AspNetCore.Server.IISIntegration - 2.2.1;Microsoft.AspNetCore.Server.Kestrel.Core - 2.1.7</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"Nuget","packageName":"Microsoft.NETCore.DotNetHostResolver","packageVersion":"2.1.0","isTransitiveDependency":true,"dependencyTree":"Microsoft.NETCore.App:2.1.0;Microsoft.NETCore.DotNetHostPolicy:2.1.0;Microsoft.NETCore.DotNetHostResolver:2.1.0","isMinimumFixVersionAvailable":true,"minimumFixVersion":"Microsoft.AspNetCore.SignalR - 1.1.0; Microsoft.AspNetCore.Server.Kestrel.Transport.Sockets - 2.2.1; Microsoft.AspNetCore.Server.IIS - 2.2.1; Microsoft.AspNetCore.Server.IISIntegration - 2.2.1;Microsoft.AspNetCore.Server.Kestrel.Core - 2.1.7"},{"packageType":"Nuget","packageName":"Microsoft.NETCore.DotNetAppHost","packageVersion":"2.1.0","isTransitiveDependency":true,"dependencyTree":"Microsoft.NETCore.App:2.1.0;Microsoft.NETCore.DotNetHostPolicy:2.1.0;Microsoft.NETCore.DotNetHostResolver:2.1.0;Microsoft.NETCore.DotNetAppHost:2.1.0","isMinimumFixVersionAvailable":true,"minimumFixVersion":"Microsoft.AspNetCore.SignalR - 1.1.0; Microsoft.AspNetCore.Server.Kestrel.Transport.Sockets - 2.2.1; Microsoft.AspNetCore.Server.IIS - 2.2.1; Microsoft.AspNetCore.Server.IISIntegration - 2.2.1;Microsoft.AspNetCore.Server.Kestrel.Core - 2.1.7"},{"packageType":"Nuget","packageName":"Microsoft.NETCore.App","packageVersion":"2.1.0","isTransitiveDependency":false,"dependencyTree":"Microsoft.NETCore.App:2.1.0","isMinimumFixVersionAvailable":true,"minimumFixVersion":"Microsoft.AspNetCore.SignalR - 1.1.0; Microsoft.AspNetCore.Server.Kestrel.Transport.Sockets - 2.2.1; Microsoft.AspNetCore.Server.IIS - 2.2.1; Microsoft.AspNetCore.Server.IISIntegration - 2.2.1;Microsoft.AspNetCore.Server.Kestrel.Core - 2.1.7"},{"packageType":"Nuget","packageName":"Microsoft.NETCore.DotNetHostPolicy","packageVersion":"2.1.0","isTransitiveDependency":true,"dependencyTree":"Microsoft.NETCore.App:2.1.0;Microsoft.NETCore.DotNetHostPolicy:2.1.0","isMinimumFixVersionAvailable":true,"minimumFixVersion":"Microsoft.AspNetCore.SignalR - 1.1.0; Microsoft.AspNetCore.Server.Kestrel.Transport.Sockets - 2.2.1; Microsoft.AspNetCore.Server.IIS - 2.2.1; Microsoft.AspNetCore.Server.IISIntegration - 2.2.1;Microsoft.AspNetCore.Server.Kestrel.Core - 2.1.7"}],"vulnerabilityIdentifier":"CVE-2019-0548","vulnerabilityDetails":"A denial of service vulnerability exists when ASP.NET Core improperly handles web requests, aka \"ASP.NET Core Denial of Service Vulnerability.\" This affects ASP.NET Core 2.2, ASP.NET Core 2.1. This CVE ID is unique from CVE-2019-0564.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-0548","cvss3Severity":"high","cvss3Score":"7.5","cvss3Metrics":{"A":"High","AC":"Low","PR":"None","S":"Unchanged","C":"None","UI":"None","AV":"Network","I":"None"},"extraData":{}}</REMEDIATE> --> | True | CVE-2019-0548 (High) detected in multiple libraries - ## CVE-2019-0548 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>microsoft.netcore.dotnethostresolver.2.1.0.nupkg</b>, <b>microsoft.netcore.dotnetapphost.2.1.0.nupkg</b>, <b>microsoft.netcore.app.2.1.0.nupkg</b>, <b>microsoft.netcore.dotnethostpolicy.2.1.0.nupkg</b></p></summary>
<p>
<details><summary><b>microsoft.netcore.dotnethostresolver.2.1.0.nupkg</b></p></summary>
<p>Provides an implementation of framework resolution strategy used by Microsoft.NETCore.DotNetHost
ca...</p>
<p>Library home page: <a href="https://api.nuget.org/packages/microsoft.netcore.dotnethostresolver.2.1.0.nupkg">https://api.nuget.org/packages/microsoft.netcore.dotnethostresolver.2.1.0.nupkg</a></p>
<p>
Dependency Hierarchy:
- microsoft.netcore.app.2.1.0.nupkg (Root Library)
- microsoft.netcore.dotnethostpolicy.2.1.0.nupkg
- :x: **microsoft.netcore.dotnethostresolver.2.1.0.nupkg** (Vulnerable Library)
</details>
<details><summary><b>microsoft.netcore.dotnetapphost.2.1.0.nupkg</b></p></summary>
<p>Provides the .NET Core app bootstrapper intended for use in the application directory
caa7b7e2bad98...</p>
<p>Library home page: <a href="https://api.nuget.org/packages/microsoft.netcore.dotnetapphost.2.1.0.nupkg">https://api.nuget.org/packages/microsoft.netcore.dotnetapphost.2.1.0.nupkg</a></p>
<p>
Dependency Hierarchy:
- microsoft.netcore.app.2.1.0.nupkg (Root Library)
- microsoft.netcore.dotnethostpolicy.2.1.0.nupkg
- microsoft.netcore.dotnethostresolver.2.1.0.nupkg
- :x: **microsoft.netcore.dotnetapphost.2.1.0.nupkg** (Vulnerable Library)
</details>
<details><summary><b>microsoft.netcore.app.2.1.0.nupkg</b></p></summary>
<p>A set of .NET API's that are included in the default .NET Core application model.
caa7b7e2bad98e56a...</p>
<p>Library home page: <a href="https://api.nuget.org/packages/microsoft.netcore.app.2.1.0.nupkg">https://api.nuget.org/packages/microsoft.netcore.app.2.1.0.nupkg</a></p>
<p>
Dependency Hierarchy:
- :x: **microsoft.netcore.app.2.1.0.nupkg** (Vulnerable Library)
</details>
<details><summary><b>microsoft.netcore.dotnethostpolicy.2.1.0.nupkg</b></p></summary>
<p>Provides a CoreCLR hosting policy implementation -- configuration settings, assembly paths and assem...</p>
<p>Library home page: <a href="https://api.nuget.org/packages/microsoft.netcore.dotnethostpolicy.2.1.0.nupkg">https://api.nuget.org/packages/microsoft.netcore.dotnethostpolicy.2.1.0.nupkg</a></p>
<p>
Dependency Hierarchy:
- microsoft.netcore.app.2.1.0.nupkg (Root Library)
- :x: **microsoft.netcore.dotnethostpolicy.2.1.0.nupkg** (Vulnerable Library)
</details>
<p>Found in HEAD commit: <a href="https://github.com/shaimael/C-sample-project-for-VSC/commit/64548f73555b19a972f2f4748c74469a037e1bd1">64548f73555b19a972f2f4748c74469a037e1bd1</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 denial of service vulnerability exists when ASP.NET Core improperly handles web requests, aka "ASP.NET Core Denial of Service Vulnerability." This affects ASP.NET Core 2.2, ASP.NET Core 2.1. This CVE ID is unique from CVE-2019-0564.
<p>Publish Date: 2019-01-08
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-0548>CVE-2019-0548</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/aspnet/Announcements/issues/335">https://github.com/aspnet/Announcements/issues/335</a></p>
<p>Release Date: 2019-01-08</p>
<p>Fix Resolution: Microsoft.AspNetCore.SignalR - 1.1.0; Microsoft.AspNetCore.Server.Kestrel.Transport.Sockets - 2.2.1; Microsoft.AspNetCore.Server.IIS - 2.2.1; Microsoft.AspNetCore.Server.IISIntegration - 2.2.1;Microsoft.AspNetCore.Server.Kestrel.Core - 2.1.7</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"Nuget","packageName":"Microsoft.NETCore.DotNetHostResolver","packageVersion":"2.1.0","isTransitiveDependency":true,"dependencyTree":"Microsoft.NETCore.App:2.1.0;Microsoft.NETCore.DotNetHostPolicy:2.1.0;Microsoft.NETCore.DotNetHostResolver:2.1.0","isMinimumFixVersionAvailable":true,"minimumFixVersion":"Microsoft.AspNetCore.SignalR - 1.1.0; Microsoft.AspNetCore.Server.Kestrel.Transport.Sockets - 2.2.1; Microsoft.AspNetCore.Server.IIS - 2.2.1; Microsoft.AspNetCore.Server.IISIntegration - 2.2.1;Microsoft.AspNetCore.Server.Kestrel.Core - 2.1.7"},{"packageType":"Nuget","packageName":"Microsoft.NETCore.DotNetAppHost","packageVersion":"2.1.0","isTransitiveDependency":true,"dependencyTree":"Microsoft.NETCore.App:2.1.0;Microsoft.NETCore.DotNetHostPolicy:2.1.0;Microsoft.NETCore.DotNetHostResolver:2.1.0;Microsoft.NETCore.DotNetAppHost:2.1.0","isMinimumFixVersionAvailable":true,"minimumFixVersion":"Microsoft.AspNetCore.SignalR - 1.1.0; Microsoft.AspNetCore.Server.Kestrel.Transport.Sockets - 2.2.1; Microsoft.AspNetCore.Server.IIS - 2.2.1; Microsoft.AspNetCore.Server.IISIntegration - 2.2.1;Microsoft.AspNetCore.Server.Kestrel.Core - 2.1.7"},{"packageType":"Nuget","packageName":"Microsoft.NETCore.App","packageVersion":"2.1.0","isTransitiveDependency":false,"dependencyTree":"Microsoft.NETCore.App:2.1.0","isMinimumFixVersionAvailable":true,"minimumFixVersion":"Microsoft.AspNetCore.SignalR - 1.1.0; Microsoft.AspNetCore.Server.Kestrel.Transport.Sockets - 2.2.1; Microsoft.AspNetCore.Server.IIS - 2.2.1; Microsoft.AspNetCore.Server.IISIntegration - 2.2.1;Microsoft.AspNetCore.Server.Kestrel.Core - 2.1.7"},{"packageType":"Nuget","packageName":"Microsoft.NETCore.DotNetHostPolicy","packageVersion":"2.1.0","isTransitiveDependency":true,"dependencyTree":"Microsoft.NETCore.App:2.1.0;Microsoft.NETCore.DotNetHostPolicy:2.1.0","isMinimumFixVersionAvailable":true,"minimumFixVersion":"Microsoft.AspNetCore.SignalR - 1.1.0; Microsoft.AspNetCore.Server.Kestrel.Transport.Sockets - 2.2.1; Microsoft.AspNetCore.Server.IIS - 2.2.1; Microsoft.AspNetCore.Server.IISIntegration - 2.2.1;Microsoft.AspNetCore.Server.Kestrel.Core - 2.1.7"}],"vulnerabilityIdentifier":"CVE-2019-0548","vulnerabilityDetails":"A denial of service vulnerability exists when ASP.NET Core improperly handles web requests, aka \"ASP.NET Core Denial of Service Vulnerability.\" This affects ASP.NET Core 2.2, ASP.NET Core 2.1. This CVE ID is unique from CVE-2019-0564.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-0548","cvss3Severity":"high","cvss3Score":"7.5","cvss3Metrics":{"A":"High","AC":"Low","PR":"None","S":"Unchanged","C":"None","UI":"None","AV":"Network","I":"None"},"extraData":{}}</REMEDIATE> --> | non_priority | cve high detected in multiple libraries cve high severity vulnerability vulnerable libraries microsoft netcore dotnethostresolver nupkg microsoft netcore dotnetapphost nupkg microsoft netcore app nupkg microsoft netcore dotnethostpolicy nupkg microsoft netcore dotnethostresolver nupkg provides an implementation of framework resolution strategy used by microsoft netcore dotnethost ca library home page a href dependency hierarchy microsoft netcore app nupkg root library microsoft netcore dotnethostpolicy nupkg x microsoft netcore dotnethostresolver nupkg vulnerable library microsoft netcore dotnetapphost nupkg provides the net core app bootstrapper intended for use in the application directory library home page a href dependency hierarchy microsoft netcore app nupkg root library microsoft netcore dotnethostpolicy nupkg microsoft netcore dotnethostresolver nupkg x microsoft netcore dotnetapphost nupkg vulnerable library microsoft netcore app nupkg a set of net api s that are included in the default net core application model library home page a href dependency hierarchy x microsoft netcore app nupkg vulnerable library microsoft netcore dotnethostpolicy nupkg provides a coreclr hosting policy implementation configuration settings assembly paths and assem library home page a href dependency hierarchy microsoft netcore app nupkg root library x microsoft netcore dotnethostpolicy nupkg vulnerable library found in head commit a href found in base branch master vulnerability details a denial of service vulnerability exists when asp net core improperly handles web requests aka asp net core denial of service vulnerability this affects asp net core asp net core this cve id is unique from cve publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity 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 microsoft aspnetcore signalr microsoft aspnetcore server kestrel transport sockets microsoft aspnetcore server iis microsoft aspnetcore server iisintegration microsoft aspnetcore server kestrel core isopenpronvulnerability true ispackagebased true isdefaultbranch true packages vulnerabilityidentifier cve vulnerabilitydetails a denial of service vulnerability exists when asp net core improperly handles web requests aka asp net core denial of service vulnerability this affects asp net core asp net core this cve id is unique from cve vulnerabilityurl | 0 |
275,495 | 20,923,657,109 | IssuesEvent | 2022-03-24 20:02:10 | AY2122S2-CS2103-W16-4/tp | https://api.github.com/repos/AY2122S2-CS2103-W16-4/tp | closed | Update documentation & user guide | documentation | Update documentation & user guide for the UserType & Remind feature | 1.0 | Update documentation & user guide - Update documentation & user guide for the UserType & Remind feature | non_priority | update documentation user guide update documentation user guide for the usertype remind feature | 0 |
832,362 | 32,077,536,854 | IssuesEvent | 2023-09-25 12:02:35 | googleapis/google-cloud-ruby | https://api.github.com/repos/googleapis/google-cloud-ruby | closed | [Nightly CI Failures] Failures detected for google-cloud-storage_transfer | type: bug priority: p1 nightly failure | At 2023-09-09 09:37:37 UTC, detected failures in google-cloud-storage_transfer for: test.
The CI logs can be found [here](https://github.com/googleapis/google-cloud-ruby/actions/runs/6129868852)
report_key_f464cad80f0bbdd3c569a725a9c5f86a | 1.0 | [Nightly CI Failures] Failures detected for google-cloud-storage_transfer - At 2023-09-09 09:37:37 UTC, detected failures in google-cloud-storage_transfer for: test.
The CI logs can be found [here](https://github.com/googleapis/google-cloud-ruby/actions/runs/6129868852)
report_key_f464cad80f0bbdd3c569a725a9c5f86a | priority | failures detected for google cloud storage transfer at utc detected failures in google cloud storage transfer for test the ci logs can be found report key | 1 |
54,217 | 7,878,401,091 | IssuesEvent | 2018-06-26 10:06:12 | edamontology/edamontology | https://api.github.com/repos/edamontology/edamontology | closed | Write clear release recipe | access | publication | release documentation | ### Quick notes right now, a proper recipe TODO:
#### 1. Release candidate
Iterate each point until success:
* Make sure Travis CI builds successfully and `date` is the last save date of EDAM_dev.owl in GMT.
* Update the live version at WebProtégé, check whether alright.
* Double-check all commits to master (diffs) since the previous release {requires automated EDAM reformatter if editted EDAM graphically}
* Upload EDAM_dev.owl to NCBO as a new version {one can mark release candidate by having upload one date earlier that the expected future release date if that's the case; keep status 'production'; do other things while waiting for parsing; if not parsed in 30-60 minutes, contact BioPortal but mind ~8hr diff}
* Upload EDAM_dev.owl to edamontology.org and point /EDAM to it. OLS will pick it up at some point during the afternoon (1.19 was 13:05 GMT)
* After parsed, check at BioPortal whether alright.
* After parsed, download CSV from BioPortal, beautify accordingly in Excel or similar, and check thoroughly whether alright.
* Check OLS that ok (hierarchy, relations, synonyms, defs & comments, subsets, additional attributes)
Excel:
1. Change decimal and thousands separators to nonsense chars (e.g. ¼ and ½). {Q: Can be hacked into a macro incl. this?}
2. Open CSV from BioPortal
3. Sort rows by "Class ID"
4. Save as Text (not Mac and not DOS) and CSV (not Mac and not DOS), rename .txt to .tsv
5. Extend columns to see content, review|validate (visually and semi-automatedly)
#### 2. Release online
* In the meantime, or whenever waiting, enhance changelog and list all tackled issues accordingly.
#### 3. Release (i.e. freeze and tag) on GitHub and Zenodo
#### 4. Notify Hans to update bio.tools and give green light back
#### 5. Update DOI mentions and announce
* All checks and code review
* Change version from _dev to w/o 'dev', update date, save & commit
* Upload to NCBO & edamontology.org (before release!!!)
* After 30min download CSV from NCBO; set Excel separators to nonsense; open in Excel; save as CSV & TSV (not Mac and not DOS!) to /releases
* Review again (in Excel and e.g. Notepad++ and/or XMLSpy), repeat previous in case of a major fault
* Copy new version to /releases/EDAM.owl|csv|tsv, commit
* Generate Bubastis and fill into changelog.md
* Review all issues closed or labelled done|partially|duplicate|won't|wrong|etc., fill numbers into changelog.md accordingly, amend changelog notes
* Release on GitHub: copy the corresponding part of changelog.md into the release notes, add _x.y.owl|csv|tsv files and changelog.md (must be AFTER all the previous steps!!! In particular because of Zenodo (DOIs)!)
* Change version of _dev.owl to x.y+1_dev, update date, save & commit
* Close 'Done - staged for release' issues and relabel them to 'Fixed, released'
* Update page.html in GitHub and upload to edamontology.org
* Update the generated Zenodo record with ORCIDs, licence, OWL link, grant, etc. (see previous record) Tip: Paste the release text from GitHub (while showing it, not editing), and all links will be in!
* Announce on mailing lists, ResearchGate, and Twitter, tweet particularly interesting news or views separately (N.B. that neither @EBIOLS nor @bioontology URLs provide any pictures for tweets)
* RG:
1. Textual update with formatted release notes
2. Added code (.owl, Add authors immediately!! Then edit after added (because of RG bug) desc, DOI, license, etc. Then add to the EDAM project)
3. A textual update of Bio.Tools that/after EDAM updated to the given version (with release notes again?)
* Twitter: | 1.0 | Write clear release recipe - ### Quick notes right now, a proper recipe TODO:
#### 1. Release candidate
Iterate each point until success:
* Make sure Travis CI builds successfully and `date` is the last save date of EDAM_dev.owl in GMT.
* Update the live version at WebProtégé, check whether alright.
* Double-check all commits to master (diffs) since the previous release {requires automated EDAM reformatter if editted EDAM graphically}
* Upload EDAM_dev.owl to NCBO as a new version {one can mark release candidate by having upload one date earlier that the expected future release date if that's the case; keep status 'production'; do other things while waiting for parsing; if not parsed in 30-60 minutes, contact BioPortal but mind ~8hr diff}
* Upload EDAM_dev.owl to edamontology.org and point /EDAM to it. OLS will pick it up at some point during the afternoon (1.19 was 13:05 GMT)
* After parsed, check at BioPortal whether alright.
* After parsed, download CSV from BioPortal, beautify accordingly in Excel or similar, and check thoroughly whether alright.
* Check OLS that ok (hierarchy, relations, synonyms, defs & comments, subsets, additional attributes)
Excel:
1. Change decimal and thousands separators to nonsense chars (e.g. ¼ and ½). {Q: Can be hacked into a macro incl. this?}
2. Open CSV from BioPortal
3. Sort rows by "Class ID"
4. Save as Text (not Mac and not DOS) and CSV (not Mac and not DOS), rename .txt to .tsv
5. Extend columns to see content, review|validate (visually and semi-automatedly)
#### 2. Release online
* In the meantime, or whenever waiting, enhance changelog and list all tackled issues accordingly.
#### 3. Release (i.e. freeze and tag) on GitHub and Zenodo
#### 4. Notify Hans to update bio.tools and give green light back
#### 5. Update DOI mentions and announce
* All checks and code review
* Change version from _dev to w/o 'dev', update date, save & commit
* Upload to NCBO & edamontology.org (before release!!!)
* After 30min download CSV from NCBO; set Excel separators to nonsense; open in Excel; save as CSV & TSV (not Mac and not DOS!) to /releases
* Review again (in Excel and e.g. Notepad++ and/or XMLSpy), repeat previous in case of a major fault
* Copy new version to /releases/EDAM.owl|csv|tsv, commit
* Generate Bubastis and fill into changelog.md
* Review all issues closed or labelled done|partially|duplicate|won't|wrong|etc., fill numbers into changelog.md accordingly, amend changelog notes
* Release on GitHub: copy the corresponding part of changelog.md into the release notes, add _x.y.owl|csv|tsv files and changelog.md (must be AFTER all the previous steps!!! In particular because of Zenodo (DOIs)!)
* Change version of _dev.owl to x.y+1_dev, update date, save & commit
* Close 'Done - staged for release' issues and relabel them to 'Fixed, released'
* Update page.html in GitHub and upload to edamontology.org
* Update the generated Zenodo record with ORCIDs, licence, OWL link, grant, etc. (see previous record) Tip: Paste the release text from GitHub (while showing it, not editing), and all links will be in!
* Announce on mailing lists, ResearchGate, and Twitter, tweet particularly interesting news or views separately (N.B. that neither @EBIOLS nor @bioontology URLs provide any pictures for tweets)
* RG:
1. Textual update with formatted release notes
2. Added code (.owl, Add authors immediately!! Then edit after added (because of RG bug) desc, DOI, license, etc. Then add to the EDAM project)
3. A textual update of Bio.Tools that/after EDAM updated to the given version (with release notes again?)
* Twitter: | non_priority | write clear release recipe quick notes right now a proper recipe todo release candidate iterate each point until success make sure travis ci builds successfully and date is the last save date of edam dev owl in gmt update the live version at webprotégé check whether alright double check all commits to master diffs since the previous release requires automated edam reformatter if editted edam graphically upload edam dev owl to ncbo as a new version one can mark release candidate by having upload one date earlier that the expected future release date if that s the case keep status production do other things while waiting for parsing if not parsed in minutes contact bioportal but mind diff upload edam dev owl to edamontology org and point edam to it ols will pick it up at some point during the afternoon was gmt after parsed check at bioportal whether alright after parsed download csv from bioportal beautify accordingly in excel or similar and check thoroughly whether alright check ols that ok hierarchy relations synonyms defs comments subsets additional attributes excel change decimal and thousands separators to nonsense chars e g ¼ and ½ q can be hacked into a macro incl this open csv from bioportal sort rows by class id save as text not mac and not dos and csv not mac and not dos rename txt to tsv extend columns to see content review validate visually and semi automatedly release online in the meantime or whenever waiting enhance changelog and list all tackled issues accordingly release i e freeze and tag on github and zenodo notify hans to update bio tools and give green light back update doi mentions and announce all checks and code review change version from dev to w o dev update date save commit upload to ncbo edamontology org before release after download csv from ncbo set excel separators to nonsense open in excel save as csv tsv not mac and not dos to releases review again in excel and e g notepad and or xmlspy repeat previous in case of a major fault copy new version to releases edam owl csv tsv commit generate bubastis and fill into changelog md review all issues closed or labelled done partially duplicate won t wrong etc fill numbers into changelog md accordingly amend changelog notes release on github copy the corresponding part of changelog md into the release notes add x y owl csv tsv files and changelog md must be after all the previous steps in particular because of zenodo dois change version of dev owl to x y dev update date save commit close done staged for release issues and relabel them to fixed released update page html in github and upload to edamontology org update the generated zenodo record with orcids licence owl link grant etc see previous record tip paste the release text from github while showing it not editing and all links will be in announce on mailing lists researchgate and twitter tweet particularly interesting news or views separately n b that neither ebiols nor bioontology urls provide any pictures for tweets rg textual update with formatted release notes added code owl add authors immediately then edit after added because of rg bug desc doi license etc then add to the edam project a textual update of bio tools that after edam updated to the given version with release notes again twitter | 0 |
102,437 | 21,960,955,438 | IssuesEvent | 2022-05-24 15:46:26 | Onelinerhub/onelinerhub | https://api.github.com/repos/Onelinerhub/onelinerhub | closed | Short solution needed: "How to make background transparent" (python-matplotlib) | help wanted good first issue code python-matplotlib | Please help us write most modern and shortest code solution for this issue:
**How to make background transparent** (technology: [python-matplotlib](https://onelinerhub.com/python-matplotlib))
### Fast way
Just write the code solution in the comments.
### Prefered way
1. Create [pull request](https://github.com/Onelinerhub/onelinerhub/blob/main/how-to-contribute.md) with a new code file inside [inbox folder](https://github.com/Onelinerhub/onelinerhub/tree/main/inbox).
2. Don't forget to [use comments](https://github.com/Onelinerhub/onelinerhub/blob/main/how-to-contribute.md#code-file-md-format) explain solution.
3. Link to this issue in comments of pull request. | 1.0 | Short solution needed: "How to make background transparent" (python-matplotlib) - Please help us write most modern and shortest code solution for this issue:
**How to make background transparent** (technology: [python-matplotlib](https://onelinerhub.com/python-matplotlib))
### Fast way
Just write the code solution in the comments.
### Prefered way
1. Create [pull request](https://github.com/Onelinerhub/onelinerhub/blob/main/how-to-contribute.md) with a new code file inside [inbox folder](https://github.com/Onelinerhub/onelinerhub/tree/main/inbox).
2. Don't forget to [use comments](https://github.com/Onelinerhub/onelinerhub/blob/main/how-to-contribute.md#code-file-md-format) explain solution.
3. Link to this issue in comments of pull request. | non_priority | short solution needed how to make background transparent python matplotlib please help us write most modern and shortest code solution for this issue how to make background transparent technology fast way just write the code solution in the comments prefered way create with a new code file inside don t forget to explain solution link to this issue in comments of pull request | 0 |
392,281 | 26,932,873,396 | IssuesEvent | 2023-02-07 18:07:34 | fluxninja/aperture | https://api.github.com/repos/fluxninja/aperture | closed | Deduplicate docs between Policy and Component | Documentation | Right now some information is repeated in docs of a Component and the Policy.
Decide what should go where and deduplicate docs (inserting links where appropriate)
Discovered when working on #143 | 1.0 | Deduplicate docs between Policy and Component - Right now some information is repeated in docs of a Component and the Policy.
Decide what should go where and deduplicate docs (inserting links where appropriate)
Discovered when working on #143 | non_priority | deduplicate docs between policy and component right now some information is repeated in docs of a component and the policy decide what should go where and deduplicate docs inserting links where appropriate discovered when working on | 0 |
206,452 | 16,042,463,634 | IssuesEvent | 2021-04-22 09:34:42 | TheThingsIndustries/lorawan-stack-docs | https://api.github.com/repos/TheThingsIndustries/lorawan-stack-docs | opened | Enable Packet Broker configuration via CLI | bug documentation | #### Summary
Packet Broker commands are failing, possible configuration step for TTS Clous tenants is missing
#### Why do we need this ?
Allow customers to see their PB configuration, and make changes
#### What is already there? What do you see now?
Documentation available: https://www.thethingsindustries.com/docs/reference/packet-broker/configure/
#### What is missing? What do you want to see?
Issues:
`$ ttn-lw-cli packetbroker registration info`
returns the overview of packetbroker commands:
<img width="928" alt="Screenshot 2021-04-22 at 11 25 57" src="https://user-images.githubusercontent.com/17290639/115690646-8a268b80-a35d-11eb-8567-e39cd9753088.png">
`$ ttn-lw-cli packetbroker register`
return:
```
WARN [core]grpc: addrConn.createTransport failed to connect to {localhost:8884 localhost:8884 <nil> 0 <nil>}. Err: connection error: desc = "transport: error while dialing: dial tcp [::1]:8884: connect: connection refused". Reconnecting...
connection error: desc = "transport: error while dialing: dial tcp [::1]:8884: connect: connection refused"
```
Supposing that some PB configuration is required (`ttn-lw-stack.yaml` file?), but documentation to do so for TTS Cloud is missing.
Only documentation for configuring PB for `Enterprise` & `Open Source` are available:
https://www.thethingsindustries.com/docs/reference/packet-broker/connect/
#### How do you propose to document this?
Request input from @johanstokking
Documentation can be updated by myself
| 1.0 | Enable Packet Broker configuration via CLI - #### Summary
Packet Broker commands are failing, possible configuration step for TTS Clous tenants is missing
#### Why do we need this ?
Allow customers to see their PB configuration, and make changes
#### What is already there? What do you see now?
Documentation available: https://www.thethingsindustries.com/docs/reference/packet-broker/configure/
#### What is missing? What do you want to see?
Issues:
`$ ttn-lw-cli packetbroker registration info`
returns the overview of packetbroker commands:
<img width="928" alt="Screenshot 2021-04-22 at 11 25 57" src="https://user-images.githubusercontent.com/17290639/115690646-8a268b80-a35d-11eb-8567-e39cd9753088.png">
`$ ttn-lw-cli packetbroker register`
return:
```
WARN [core]grpc: addrConn.createTransport failed to connect to {localhost:8884 localhost:8884 <nil> 0 <nil>}. Err: connection error: desc = "transport: error while dialing: dial tcp [::1]:8884: connect: connection refused". Reconnecting...
connection error: desc = "transport: error while dialing: dial tcp [::1]:8884: connect: connection refused"
```
Supposing that some PB configuration is required (`ttn-lw-stack.yaml` file?), but documentation to do so for TTS Cloud is missing.
Only documentation for configuring PB for `Enterprise` & `Open Source` are available:
https://www.thethingsindustries.com/docs/reference/packet-broker/connect/
#### How do you propose to document this?
Request input from @johanstokking
Documentation can be updated by myself
| non_priority | enable packet broker configuration via cli summary packet broker commands are failing possible configuration step for tts clous tenants is missing why do we need this allow customers to see their pb configuration and make changes what is already there what do you see now documentation available what is missing what do you want to see issues ttn lw cli packetbroker registration info returns the overview of packetbroker commands img width alt screenshot at src ttn lw cli packetbroker register return warn grpc addrconn createtransport failed to connect to localhost localhost err connection error desc transport error while dialing dial tcp connect connection refused reconnecting connection error desc transport error while dialing dial tcp connect connection refused supposing that some pb configuration is required ttn lw stack yaml file but documentation to do so for tts cloud is missing only documentation for configuring pb for enterprise open source are available how do you propose to document this request input from johanstokking documentation can be updated by myself | 0 |
166,963 | 14,087,205,002 | IssuesEvent | 2020-11-05 05:52:39 | SAP/cloud-foundry-tools | https://api.github.com/repos/SAP/cloud-foundry-tools | closed | Url doesnt work | bug documentation good first issue | The link provides seems to be an internal link
cf-cli extension called cf-service-info (from here)[http://nexus.wdf.sap.corp:8081/nexus/content/groups/build.releases/com/sap/golang/com/sap/devx/wing/cfserviceinfo/]
The run config mentioned is not included in the project
"run the launch config 'Run Extension'"
Thanks in advance | 1.0 | Url doesnt work - The link provides seems to be an internal link
cf-cli extension called cf-service-info (from here)[http://nexus.wdf.sap.corp:8081/nexus/content/groups/build.releases/com/sap/golang/com/sap/devx/wing/cfserviceinfo/]
The run config mentioned is not included in the project
"run the launch config 'Run Extension'"
Thanks in advance | non_priority | url doesnt work the link provides seems to be an internal link cf cli extension called cf service info from here the run config mentioned is not included in the project run the launch config run extension thanks in advance | 0 |
56,988 | 7,022,194,322 | IssuesEvent | 2017-12-22 09:27:30 | EnginyeriaSofwareUB/ES2017B1 | https://api.github.com/repos/EnginyeriaSofwareUB/ES2017B1 | closed | Animación destrucción del terreno | Design feature | Criterios de aceptación:
- [x] Diseñar animación de destrucción del terreno.
- [x] Implementarla en el script
Horas de trabajo:
- Previsión:
- Realidad:
| 1.0 | Animación destrucción del terreno - Criterios de aceptación:
- [x] Diseñar animación de destrucción del terreno.
- [x] Implementarla en el script
Horas de trabajo:
- Previsión:
- Realidad:
| non_priority | animación destrucción del terreno criterios de aceptación diseñar animación de destrucción del terreno implementarla en el script horas de trabajo previsión realidad | 0 |
743,151 | 25,888,937,885 | IssuesEvent | 2022-12-14 16:26:51 | Eonasdan/tempus-dominus | https://api.github.com/repos/Eonasdan/tempus-dominus | closed | useTwentyfourHour hour-range is 01 - 24, should be 00 - 23 | State: Waiting feedback Area: TypeScript Priority: Low | - Operating: Windows 10
- Browser: Chrome 103.0.5060.66, Edge 103.0.1264.44
- Version of the plugin. 6.0.0-beta9.
- Stackblitz fork: [https://stackblitz.com/edit/tempus-dominus-v6-next-ajtgmm?file=index.js](https://stackblitz.com/edit/tempus-dominus-v6-next-ajtgmm?file=index.js)
- Browser's locale: sv-SE
When using the useTwentyfourHour-setting the hour-range is between 01 - 24, should be 00 - 23.
[Maybe related to this ticket?](https://github.com/Eonasdan/tempus-dominus/issues/2548)
| 1.0 | useTwentyfourHour hour-range is 01 - 24, should be 00 - 23 - - Operating: Windows 10
- Browser: Chrome 103.0.5060.66, Edge 103.0.1264.44
- Version of the plugin. 6.0.0-beta9.
- Stackblitz fork: [https://stackblitz.com/edit/tempus-dominus-v6-next-ajtgmm?file=index.js](https://stackblitz.com/edit/tempus-dominus-v6-next-ajtgmm?file=index.js)
- Browser's locale: sv-SE
When using the useTwentyfourHour-setting the hour-range is between 01 - 24, should be 00 - 23.
[Maybe related to this ticket?](https://github.com/Eonasdan/tempus-dominus/issues/2548)
| priority | usetwentyfourhour hour range is should be operating windows browser chrome edge version of the plugin stackblitz fork browser s locale sv se when using the usetwentyfourhour setting the hour range is between should be | 1 |
116,832 | 15,020,011,997 | IssuesEvent | 2021-02-01 14:14:08 | mozilla-lockwise/lockwise-ios | https://api.github.com/repos/mozilla-lockwise/lockwise-ios | reopened | New image for placeholder view in search for iPad | archived needs-design | The current placeholder when entries haven't loaded in looks funny on the iPad because it isn't wide enough. | 1.0 | New image for placeholder view in search for iPad - The current placeholder when entries haven't loaded in looks funny on the iPad because it isn't wide enough. | non_priority | new image for placeholder view in search for ipad the current placeholder when entries haven t loaded in looks funny on the ipad because it isn t wide enough | 0 |
45,593 | 5,720,592,830 | IssuesEvent | 2017-04-20 02:29:11 | Kademi/kademi-dev | https://api.github.com/repos/Kademi/kademi-dev | closed | Options for enable/disable cash top up for Reward Store | enhancement Ready to Test - Dev | Please implement SettingsApplication for ShoppingCartApp, and add a setting to control whether cash top ups are enabled.
Update the isCashTopupsEnabled method in ShoppingCartApp to use this setting
| 1.0 | Options for enable/disable cash top up for Reward Store - Please implement SettingsApplication for ShoppingCartApp, and add a setting to control whether cash top ups are enabled.
Update the isCashTopupsEnabled method in ShoppingCartApp to use this setting
| non_priority | options for enable disable cash top up for reward store please implement settingsapplication for shoppingcartapp and add a setting to control whether cash top ups are enabled update the iscashtopupsenabled method in shoppingcartapp to use this setting | 0 |
120,536 | 10,122,121,553 | IssuesEvent | 2019-07-31 17:10:51 | opengeospatial/te-releases | https://api.github.com/repos/opengeospatial/te-releases | closed | CDB 1.0 revision 0.4 in Beta | approved-by-test-lead ready-for-installation | I do not have permissions on the [main ets-cdb10 repository](https://github.com/opengeospatial/ets-cdb10) to tag issues with milestone "0.3". I also cannot push the commit with the release notes; it is on my fork: https://github.com/GeoSensorWebLab/ets-cdb10
Would you prefer I make a pull request for the "release notes" commit, or manually use git to pick that commit? | 1.0 | CDB 1.0 revision 0.4 in Beta - I do not have permissions on the [main ets-cdb10 repository](https://github.com/opengeospatial/ets-cdb10) to tag issues with milestone "0.3". I also cannot push the commit with the release notes; it is on my fork: https://github.com/GeoSensorWebLab/ets-cdb10
Would you prefer I make a pull request for the "release notes" commit, or manually use git to pick that commit? | non_priority | cdb revision in beta i do not have permissions on the to tag issues with milestone i also cannot push the commit with the release notes it is on my fork would you prefer i make a pull request for the release notes commit or manually use git to pick that commit | 0 |
53,277 | 6,307,044,165 | IssuesEvent | 2017-07-21 23:02:59 | Microsoft/vscode | https://api.github.com/repos/Microsoft/vscode | closed | TS Build Task Multiroot Support | on-testplan tasks typescript | **Feature**
Ensure that the TS task 2.0 builders work as expected in multiroot scenarios | 1.0 | TS Build Task Multiroot Support - **Feature**
Ensure that the TS task 2.0 builders work as expected in multiroot scenarios | non_priority | ts build task multiroot support feature ensure that the ts task builders work as expected in multiroot scenarios | 0 |
46,926 | 2,966,808,061 | IssuesEvent | 2015-07-12 08:35:32 | mattjhayes/nmeta | https://api.github.com/repos/mattjhayes/nmeta | opened | Granular QoS Treatment Control | enhancement Functional Severity: Low Priority | There needs to be an ability to tailor QoS treatment to the capabilities of the device or port. Some switch ports may have egress queues configured and others won't. Queueing a packet to a queue that doesn't exist will consign it to a black hole bit bucket.
It may be desirable to move this control to the main policy to take advantage of abstractions such as port_sets.
This issue is related to:
#35 - Policy Roadmap
#69 - Port Sets
QoS Roadmap
This GitHub issue | 1.0 | Granular QoS Treatment Control - There needs to be an ability to tailor QoS treatment to the capabilities of the device or port. Some switch ports may have egress queues configured and others won't. Queueing a packet to a queue that doesn't exist will consign it to a black hole bit bucket.
It may be desirable to move this control to the main policy to take advantage of abstractions such as port_sets.
This issue is related to:
#35 - Policy Roadmap
#69 - Port Sets
QoS Roadmap
This GitHub issue | priority | granular qos treatment control there needs to be an ability to tailor qos treatment to the capabilities of the device or port some switch ports may have egress queues configured and others won t queueing a packet to a queue that doesn t exist will consign it to a black hole bit bucket it may be desirable to move this control to the main policy to take advantage of abstractions such as port sets this issue is related to policy roadmap port sets qos roadmap this github issue | 1 |
113,384 | 24,409,318,377 | IssuesEvent | 2022-10-05 10:52:16 | TFG-Beatriz-Llamas/botStarcraft | https://api.github.com/repos/TFG-Beatriz-Llamas/botStarcraft | closed | Optimizar parámetros propios | code | - Trabajadores construido por centro de mando: Entero
- Número de barracones máximos construidos por centro de mando: Entero
- Cantidad de soldados a construir por cada centro de mando: Entero
- Número de soldados a generar antes de lanzar el ataque: Entero
| 1.0 | Optimizar parámetros propios - - Trabajadores construido por centro de mando: Entero
- Número de barracones máximos construidos por centro de mando: Entero
- Cantidad de soldados a construir por cada centro de mando: Entero
- Número de soldados a generar antes de lanzar el ataque: Entero
| non_priority | optimizar parámetros propios trabajadores construido por centro de mando entero número de barracones máximos construidos por centro de mando entero cantidad de soldados a construir por cada centro de mando entero número de soldados a generar antes de lanzar el ataque entero | 0 |
113,189 | 24,376,375,548 | IssuesEvent | 2022-10-04 01:36:32 | rkd103/Group-11 | https://api.github.com/repos/rkd103/Group-11 | closed | Implement User Story A - Add Support for Account Creation, User Sign-in, Account Access, and Credential Retrieval/Reset | enhancement code | Taking the User Stories assigned in previous issues, begin brainstorming how to implement the requirements in code.
Namely, perform independent research regarding what packages, techniques, etc. are needed to satisfy the stakeholder's image.
User Story A: "create account, login, and access personal timeline"
Original Assignee: Robert (rkd103) | 1.0 | Implement User Story A - Add Support for Account Creation, User Sign-in, Account Access, and Credential Retrieval/Reset - Taking the User Stories assigned in previous issues, begin brainstorming how to implement the requirements in code.
Namely, perform independent research regarding what packages, techniques, etc. are needed to satisfy the stakeholder's image.
User Story A: "create account, login, and access personal timeline"
Original Assignee: Robert (rkd103) | non_priority | implement user story a add support for account creation user sign in account access and credential retrieval reset taking the user stories assigned in previous issues begin brainstorming how to implement the requirements in code namely perform independent research regarding what packages techniques etc are needed to satisfy the stakeholder s image user story a create account login and access personal timeline original assignee robert | 0 |
141,427 | 11,418,523,226 | IssuesEvent | 2020-02-03 04:56:41 | brave/brave-browser | https://api.github.com/repos/brave/brave-browser | opened | Folllow up of #7526 - Unable to set monthly tips hence not shown under contribution panel | OS/Windows QA/Test-Plan-Specified QA/Yes bug feature/rewards regression | <!-- Have you searched for similar issues? Before submitting this issue, please check the open issues and add a note before logging a new issue.
PLEASE USE THE TEMPLATE BELOW TO PROVIDE INFORMATION ABOUT THE ISSUE.
INSUFFICIENT INFO WILL GET THE ISSUE CLOSED. IT WILL ONLY BE REOPENED AFTER SUFFICIENT INFO IS PROVIDED-->
## Description
<!--Provide a brief description of the issue-->
Follow up of #7526 - Unable to set monthly tips hence not shown under contribution panel
## Steps to Reproduce
<!--Please add a series of steps to reproduce the issue-->
1. Clean profile 1.3.107 staging env
2. Claim the UGP grants
3. Open https://duckduckgo.com/
4. Open the BR panel and set the monthly contributions for https://duckduckgo.com/
5. The monthly Tip isn't set and https://duckduckgo.com/ isn't displayed under monthly contributions panel.
## Actual result:
<!--Please add screenshots if needed-->
Folllow up of #7526 - Unable to set monthly tips hence not shown under contribution panel
## Expected result:
Should be able to set Monthly tips.
## Reproduces how often:
<!--[Easily reproduced/Intermittent issue/No steps to reproduce]-->
80% reproducible
## Brave version (brave://version info)
<!--For installed build, please copy Brave, Revision and OS from brave://version and paste here. If building from source please mention it along with brave://version details-->
Brave | 1.3.107 Chromium: 79.0.3945.130 (Official Build) beta (64-bit)
-- | --
Revision | e22de67c28798d98833a7137c0e22876237fc40a-refs/branch-heads/3945@{#1047}
OS | Windows 10 OS Version 1803 (Build 17134.1006)
## Version/Channel Information:
<!--Does this issue happen on any other channels? Or is it specific to a certain channel?-->
- Can you reproduce this issue with the current release? NA
- Can you reproduce this issue with the beta channel? Yes
- Can you reproduce this issue with the dev channel? Not sure
- Can you reproduce this issue with the nightly channel? Not sure
## Other Additional Information:
- Does the issue resolve itself when disabling Brave Shields?
- Does the issue resolve itself when disabling Brave Rewards?
- Is the issue reproducible on the latest version of Chrome?
## Miscellaneous Information:
<!--Any additional information, related issues, extra QA steps, configuration or data that might be necessary to reproduce the issue-->
cc: @brave/legacy_qa @NejcZdovc @masparrow @rebron | 1.0 | Folllow up of #7526 - Unable to set monthly tips hence not shown under contribution panel - <!-- Have you searched for similar issues? Before submitting this issue, please check the open issues and add a note before logging a new issue.
PLEASE USE THE TEMPLATE BELOW TO PROVIDE INFORMATION ABOUT THE ISSUE.
INSUFFICIENT INFO WILL GET THE ISSUE CLOSED. IT WILL ONLY BE REOPENED AFTER SUFFICIENT INFO IS PROVIDED-->
## Description
<!--Provide a brief description of the issue-->
Follow up of #7526 - Unable to set monthly tips hence not shown under contribution panel
## Steps to Reproduce
<!--Please add a series of steps to reproduce the issue-->
1. Clean profile 1.3.107 staging env
2. Claim the UGP grants
3. Open https://duckduckgo.com/
4. Open the BR panel and set the monthly contributions for https://duckduckgo.com/
5. The monthly Tip isn't set and https://duckduckgo.com/ isn't displayed under monthly contributions panel.
## Actual result:
<!--Please add screenshots if needed-->
Folllow up of #7526 - Unable to set monthly tips hence not shown under contribution panel
## Expected result:
Should be able to set Monthly tips.
## Reproduces how often:
<!--[Easily reproduced/Intermittent issue/No steps to reproduce]-->
80% reproducible
## Brave version (brave://version info)
<!--For installed build, please copy Brave, Revision and OS from brave://version and paste here. If building from source please mention it along with brave://version details-->
Brave | 1.3.107 Chromium: 79.0.3945.130 (Official Build) beta (64-bit)
-- | --
Revision | e22de67c28798d98833a7137c0e22876237fc40a-refs/branch-heads/3945@{#1047}
OS | Windows 10 OS Version 1803 (Build 17134.1006)
## Version/Channel Information:
<!--Does this issue happen on any other channels? Or is it specific to a certain channel?-->
- Can you reproduce this issue with the current release? NA
- Can you reproduce this issue with the beta channel? Yes
- Can you reproduce this issue with the dev channel? Not sure
- Can you reproduce this issue with the nightly channel? Not sure
## Other Additional Information:
- Does the issue resolve itself when disabling Brave Shields?
- Does the issue resolve itself when disabling Brave Rewards?
- Is the issue reproducible on the latest version of Chrome?
## Miscellaneous Information:
<!--Any additional information, related issues, extra QA steps, configuration or data that might be necessary to reproduce the issue-->
cc: @brave/legacy_qa @NejcZdovc @masparrow @rebron | non_priority | folllow up of unable to set monthly tips hence not shown under contribution panel have you searched for similar issues before submitting this issue please check the open issues and add a note before logging a new issue please use the template below to provide information about the issue insufficient info will get the issue closed it will only be reopened after sufficient info is provided description follow up of unable to set monthly tips hence not shown under contribution panel steps to reproduce clean profile staging env claim the ugp grants open open the br panel and set the monthly contributions for the monthly tip isn t set and isn t displayed under monthly contributions panel actual result folllow up of unable to set monthly tips hence not shown under contribution panel expected result should be able to set monthly tips reproduces how often reproducible brave version brave version info brave chromium official build beta bit revision refs branch heads os windows os version build version channel information can you reproduce this issue with the current release na can you reproduce this issue with the beta channel yes can you reproduce this issue with the dev channel not sure can you reproduce this issue with the nightly channel not sure other additional information does the issue resolve itself when disabling brave shields does the issue resolve itself when disabling brave rewards is the issue reproducible on the latest version of chrome miscellaneous information cc brave legacy qa nejczdovc masparrow rebron | 0 |
35,184 | 16,964,343,476 | IssuesEvent | 2021-06-29 09:03:27 | AbsaOSS/spline | https://api.github.com/repos/AbsaOSS/spline | closed | Incorrect index field "execPlanDetails.executionPlanId" | bug component: Persistence scaling / performance | Should be `execPlanDetails.executionPlanKey` | True | Incorrect index field "execPlanDetails.executionPlanId" - Should be `execPlanDetails.executionPlanKey` | non_priority | incorrect index field execplandetails executionplanid should be execplandetails executionplankey | 0 |
19,106 | 10,318,622,572 | IssuesEvent | 2019-08-30 15:22:02 | microsoft/MixedRealityToolkit-Unity | https://api.github.com/repos/microsoft/MixedRealityToolkit-Unity | closed | SpherePointer to cache TryGetNearGraspPoint | Bug Input System - Pointer Performance | ## Describe the bug
SpherePointer leverages TryGetNearGraspPoint() for many commonly used properties (i.e IsNearObject and IsInteractionEnabled). These properties are called multiple times which causes the TryGetNearGraspPoint and resulting Physics.CheckSphere to be redundantly called everytime.
## To reproduce
Read SpherePointer.cs => IsNearObject & IsInteractionEnabled
## Expected behavior
For a given frame update, the results of TryGetNearGraspPoint and Physics.CheckSphere could potentially be cached. The checksphere may be problematic if objects are instantiated during an update loop. But the TryGetNearGrapsPoint should not be altering.
## Screenshots
If applicable, add screenshots to help explain your problem.
## Your Setup (please complete the following information)
- Unity Version [e.g. 2018.3.11f1]
- MRTK Version [e.g. v2.0]
## Target Platform (please complete the following information)
- HoloLens
- HoloLens 2
- WMR immersive
- OpenVR
## Additional context
Add any other context about the problem here.
| True | SpherePointer to cache TryGetNearGraspPoint - ## Describe the bug
SpherePointer leverages TryGetNearGraspPoint() for many commonly used properties (i.e IsNearObject and IsInteractionEnabled). These properties are called multiple times which causes the TryGetNearGraspPoint and resulting Physics.CheckSphere to be redundantly called everytime.
## To reproduce
Read SpherePointer.cs => IsNearObject & IsInteractionEnabled
## Expected behavior
For a given frame update, the results of TryGetNearGraspPoint and Physics.CheckSphere could potentially be cached. The checksphere may be problematic if objects are instantiated during an update loop. But the TryGetNearGrapsPoint should not be altering.
## Screenshots
If applicable, add screenshots to help explain your problem.
## Your Setup (please complete the following information)
- Unity Version [e.g. 2018.3.11f1]
- MRTK Version [e.g. v2.0]
## Target Platform (please complete the following information)
- HoloLens
- HoloLens 2
- WMR immersive
- OpenVR
## Additional context
Add any other context about the problem here.
| non_priority | spherepointer to cache trygetneargrasppoint describe the bug spherepointer leverages trygetneargrasppoint for many commonly used properties i e isnearobject and isinteractionenabled these properties are called multiple times which causes the trygetneargrasppoint and resulting physics checksphere to be redundantly called everytime to reproduce read spherepointer cs isnearobject isinteractionenabled expected behavior for a given frame update the results of trygetneargrasppoint and physics checksphere could potentially be cached the checksphere may be problematic if objects are instantiated during an update loop but the trygetneargrapspoint should not be altering screenshots if applicable add screenshots to help explain your problem your setup please complete the following information unity version mrtk version target platform please complete the following information hololens hololens wmr immersive openvr additional context add any other context about the problem here | 0 |
160,589 | 6,100,424,391 | IssuesEvent | 2017-06-20 12:35:08 | openshift/origin-web-catalog | https://api.github.com/repos/openshift/origin-web-catalog | closed | select-project component shouldn't show projects being deleted | kind/bug priority/P3 | The select-project component shows all projects, even those being deleted. We should filter out those with a deletion timestamp which means they're scheduled for deletion. | 1.0 | select-project component shouldn't show projects being deleted - The select-project component shows all projects, even those being deleted. We should filter out those with a deletion timestamp which means they're scheduled for deletion. | priority | select project component shouldn t show projects being deleted the select project component shows all projects even those being deleted we should filter out those with a deletion timestamp which means they re scheduled for deletion | 1 |
679,905 | 23,249,231,759 | IssuesEvent | 2022-08-04 00:41:47 | ProdigyPNP/ProdigyMathGameHacking | https://api.github.com/repos/ProdigyPNP/ProdigyMathGameHacking | closed | [Closed for inactivity] Don't work | Is: Bug Priority: Low Category: PHEx | ### Describe the bug
So, I am on a macbook air, but my operating system is windows 10, and I wanted to downlowd hack and compress the zip file,and after compressing the file, I tried to load is on my chrome extension with the developer mode, but it keeps sending me errors! Also btw I tried the same thing on my other completely windows computer and it worked well, but don't know why is it doing this now? :( Plz help! :( Thanks! :)
### Describe how to replicate bug
I compress the downlowd file and load it, it will show the error again
### Date of submittion
2022. 7. 13
### Your PHEx version
Not even installed yet, cause I am not able to :(
### Your operating system and the version
my operating system is wondows 10
### Before submitting a bug report
- [X] This bug wasn't already reported.
(I have checked every bug report on GitHub)
- [X] I agree to this repository's prerequisites.
(I have read and agree to the License, Code of Conduct, and Contributing Guidelines)
| 1.0 | [Closed for inactivity] Don't work - ### Describe the bug
So, I am on a macbook air, but my operating system is windows 10, and I wanted to downlowd hack and compress the zip file,and after compressing the file, I tried to load is on my chrome extension with the developer mode, but it keeps sending me errors! Also btw I tried the same thing on my other completely windows computer and it worked well, but don't know why is it doing this now? :( Plz help! :( Thanks! :)
### Describe how to replicate bug
I compress the downlowd file and load it, it will show the error again
### Date of submittion
2022. 7. 13
### Your PHEx version
Not even installed yet, cause I am not able to :(
### Your operating system and the version
my operating system is wondows 10
### Before submitting a bug report
- [X] This bug wasn't already reported.
(I have checked every bug report on GitHub)
- [X] I agree to this repository's prerequisites.
(I have read and agree to the License, Code of Conduct, and Contributing Guidelines)
| priority | don t work describe the bug so i am on a macbook air but my operating system is windows and i wanted to downlowd hack and compress the zip file and after compressing the file i tried to load is on my chrome extension with the developer mode but it keeps sending me errors also btw i tried the same thing on my other completely windows computer and it worked well but don t know why is it doing this now plz help thanks describe how to replicate bug i compress the downlowd file and load it it will show the error again date of submittion your phex version not even installed yet cause i am not able to your operating system and the version my operating system is wondows before submitting a bug report this bug wasn t already reported i have checked every bug report on github i agree to this repository s prerequisites i have read and agree to the license code of conduct and contributing guidelines | 1 |
19,293 | 4,369,556,374 | IssuesEvent | 2016-08-04 00:38:46 | backdrop-contrib/githubapi | https://api.github.com/repos/backdrop-contrib/githubapi | closed | Flip the client secret and client ID in the README.md | Better documentation | I copy/pasted the lines from the README.md into my settings.php file:
> Optionally you can store client_id and client_secret via settings.php
```
$settings['githubapi_client_secret'] = 'YOUR_APP_CLIENT_SECRET';
$settings['githubapi_client_id'] = 'YOUR_APP_CLIENT_ID';
```
But these settings are flipped from the UI in GitHub:
To avoid confusion, we should flip the settings in the README to prevent this same copy/paste mistake.
| 1.0 | Flip the client secret and client ID in the README.md - I copy/pasted the lines from the README.md into my settings.php file:
> Optionally you can store client_id and client_secret via settings.php
```
$settings['githubapi_client_secret'] = 'YOUR_APP_CLIENT_SECRET';
$settings['githubapi_client_id'] = 'YOUR_APP_CLIENT_ID';
```
But these settings are flipped from the UI in GitHub:
To avoid confusion, we should flip the settings in the README to prevent this same copy/paste mistake.
| non_priority | flip the client secret and client id in the readme md i copy pasted the lines from the readme md into my settings php file optionally you can store client id and client secret via settings php settings your app client secret settings your app client id but these settings are flipped from the ui in github to avoid confusion we should flip the settings in the readme to prevent this same copy paste mistake | 0 |
204,128 | 15,417,463,120 | IssuesEvent | 2021-03-05 07:14:08 | Fammeo/EasyCloudBooks | https://api.github.com/repos/Fammeo/EasyCloudBooks | closed | Market place seeding error | Client Request Resolved fixed testing-required | <img width="1280" alt="Screenshot 2021-03-05 at 10 54 12 AM" src="https://user-images.githubusercontent.com/46813198/110071008-3fe34e00-7da1-11eb-9703-527e8a9f3f94.png
steps
1. RESET objects
2. save - error appeared. | 1.0 | Market place seeding error - <img width="1280" alt="Screenshot 2021-03-05 at 10 54 12 AM" src="https://user-images.githubusercontent.com/46813198/110071008-3fe34e00-7da1-11eb-9703-527e8a9f3f94.png
steps
1. RESET objects
2. save - error appeared. | non_priority | market place seeding error img width alt screenshot at am src steps reset objects save error appeared | 0 |
112,342 | 4,524,899,710 | IssuesEvent | 2016-09-07 01:27:01 | coreos/coreos-kubernetes | https://api.github.com/repos/coreos/coreos-kubernetes | closed | 401 Unauthorized kube-apiserver in multiple master nodes front of ELB | kind/support priority/P2 | Hi,
We are trying to achieve high availability cluster with multiple master nodes front ELB.
Also trying to use ingress to layer 7 traffic from ELB to master nodes.
http://kubernetes.io/docs/user-guide/ingress/#tls
apiserver-key and apiserver cert configured as secrets.
We also have external hostname for apiserver which points to ELB.
**Scenario-1**: Request through external hostname and passing through ELB get HTTP/1.1 401 Unauthorized error.
**Scenario-2**: service endpoint HTTPS request is working fine over https and admin crt and key.
```
curl -v --cacert ca.pem https://kubernetes.default.svc.cluster.local/version --cert admin.pem --key admin-key.pem
Host: kubernetes.default.svc.cluster.local
> User-Agent: curl/7.47.0
> Accept: */*
>
< HTTP/1.1 200 OK
< Content-Type: application/json
< Date: Wed, 10 Aug 2016 16:34:24 GMT
< Content-Length: 260
<
{
"major": "1",
"minor": "3",
"gitVersion": "v1.3.4",
"gitCommit": "dd6b458ef8dbf24aff55795baa68f83383c9b3a9",
"gitTreeState": "clean",
"buildDate": "2016-08-01T16:38:31Z",
"goVersion": "go1.6.2",
"compiler": "gc",
"platform": "linux/amd64"
* Connection #0 to host kubernetes.default.svc.cluster.local left intact
```
**Ingress config:**
```
apiVersion: extensions/v1beta1
kind: Ingress
metadata:
name: no-rules-map
spec:
tls:
- secretName: testsecret
backend:
serviceName: kubernetes
servicePort: 443
```
```
kubectl describe ing
Name: no-rules-map
Namespace: default
Address:
Default backend: kubernetes:443 (172.18.2.4:443,172.18.2.5:443)
TLS:
testsecret terminates
Rules:
Host Path Backends
---- ---- --------
* * kubernetes:443 (172.18.2.4:443,172.18.2.5:443)
Annotations:
No events.
```
**TLS secret details:**
```
kubectl describe secrets testsecret
Name: testsecret
Namespace: default
Labels: <none>
Annotations: <none>
Type: Opaque
Data
====
tls.crt: 1675 bytes
tls.key: 1679 bytes
```
------------------------------------------------------------------------------------
Question: can you please let me know your inputs why HTTPS request for apiserver fails through external hostname passing through ELB?
Please let me know if you need any more information on this.
Thanks! | 1.0 | 401 Unauthorized kube-apiserver in multiple master nodes front of ELB - Hi,
We are trying to achieve high availability cluster with multiple master nodes front ELB.
Also trying to use ingress to layer 7 traffic from ELB to master nodes.
http://kubernetes.io/docs/user-guide/ingress/#tls
apiserver-key and apiserver cert configured as secrets.
We also have external hostname for apiserver which points to ELB.
**Scenario-1**: Request through external hostname and passing through ELB get HTTP/1.1 401 Unauthorized error.
**Scenario-2**: service endpoint HTTPS request is working fine over https and admin crt and key.
```
curl -v --cacert ca.pem https://kubernetes.default.svc.cluster.local/version --cert admin.pem --key admin-key.pem
Host: kubernetes.default.svc.cluster.local
> User-Agent: curl/7.47.0
> Accept: */*
>
< HTTP/1.1 200 OK
< Content-Type: application/json
< Date: Wed, 10 Aug 2016 16:34:24 GMT
< Content-Length: 260
<
{
"major": "1",
"minor": "3",
"gitVersion": "v1.3.4",
"gitCommit": "dd6b458ef8dbf24aff55795baa68f83383c9b3a9",
"gitTreeState": "clean",
"buildDate": "2016-08-01T16:38:31Z",
"goVersion": "go1.6.2",
"compiler": "gc",
"platform": "linux/amd64"
* Connection #0 to host kubernetes.default.svc.cluster.local left intact
```
**Ingress config:**
```
apiVersion: extensions/v1beta1
kind: Ingress
metadata:
name: no-rules-map
spec:
tls:
- secretName: testsecret
backend:
serviceName: kubernetes
servicePort: 443
```
```
kubectl describe ing
Name: no-rules-map
Namespace: default
Address:
Default backend: kubernetes:443 (172.18.2.4:443,172.18.2.5:443)
TLS:
testsecret terminates
Rules:
Host Path Backends
---- ---- --------
* * kubernetes:443 (172.18.2.4:443,172.18.2.5:443)
Annotations:
No events.
```
**TLS secret details:**
```
kubectl describe secrets testsecret
Name: testsecret
Namespace: default
Labels: <none>
Annotations: <none>
Type: Opaque
Data
====
tls.crt: 1675 bytes
tls.key: 1679 bytes
```
------------------------------------------------------------------------------------
Question: can you please let me know your inputs why HTTPS request for apiserver fails through external hostname passing through ELB?
Please let me know if you need any more information on this.
Thanks! | priority | unauthorized kube apiserver in multiple master nodes front of elb hi we are trying to achieve high availability cluster with multiple master nodes front elb also trying to use ingress to layer traffic from elb to master nodes apiserver key and apiserver cert configured as secrets we also have external hostname for apiserver which points to elb scenario request through external hostname and passing through elb get http unauthorized error scenario service endpoint https request is working fine over https and admin crt and key curl v cacert ca pem cert admin pem key admin key pem host kubernetes default svc cluster local user agent curl accept http ok content type application json date wed aug gmt content length major minor gitversion gitcommit gittreestate clean builddate goversion compiler gc platform linux connection to host kubernetes default svc cluster local left intact ingress config apiversion extensions kind ingress metadata name no rules map spec tls secretname testsecret backend servicename kubernetes serviceport kubectl describe ing name no rules map namespace default address default backend kubernetes tls testsecret terminates rules host path backends kubernetes annotations no events tls secret details kubectl describe secrets testsecret name testsecret namespace default labels annotations type opaque data tls crt bytes tls key bytes question can you please let me know your inputs why https request for apiserver fails through external hostname passing through elb please let me know if you need any more information on this thanks | 1 |
51,136 | 3,011,103,551 | IssuesEvent | 2015-07-28 16:13:59 | MinetestForFun/minetest-minetestforfun-server | https://api.github.com/repos/MinetestForFun/minetest-minetestforfun-server | closed | Crash [Throwing] | Modding@BugFix Priority@High Server crash | #### Crash logs
http://zerobin.qbuissondebon.info/?643a724274bfff1b#Yx4yITyQ80CCU6zVWE5BxC6rUNT4bP1I1WveaZlO1Ho=
```
n]: [mana] Wrote mana data into /home/quentinbd/minetest/worlds/minetestforfun//mana.mt.
01:31:34: ACTION[main]: compassgps writing settings
01:31:34: ACTION[main]: Wrote quests to file
01:31:34: ACTION[main]: [PClasses] Datas saved
01:31:34: ACTION[main]: [tsm_pyramids] Chests saved
01:31:34: ACTION[main]: [fishing] Server shuts down. saving trophies table
01:31:35: ERROR[main]: ERROR: An unhandled exception occurred: ...uentinbd/minetest/bin/../mods/throwing/functions.lua:36: attempt to index a nil value
01:31:35: ERROR[main]: stack traceback:
01:31:35: ERROR[main]: ...uentinbd/minetest/bin/../mods/throwing/functions.lua:36: in function 'throwing_shoot_arrow'
01:31:35: ERROR[main]: ...uentinbd/minetest/bin/../mods/throwing/functions.lua:109: in function <...uentinbd/minetest/bin/../mods/throwing/functions.lua:103>
In thread 7f076f4d2740:
/home/quentinbd/minetest/src/main.cpp:882: int main(int, char**): Assertion '0' failed.
Debug stacks:
DEBUG STACK FOR THREAD 7f0768b3c700:
#0 virtual void* CurlFetchThread::Thread()
DEBUG STACK FOR THREAD 7f076f4d2740:
#0 int main(int, char**)
(Leftover data: #1 Dedicated server branch)
(Leftover data: #2 virtual void ServerMap::save(ModifiedState))
(Leftover data: #3 void ItemStack::serialize(std::ostream&) const)
/home/quentinbd/script/start02.sh : ligne 26 : 20913 Abandon /home/quentinbd/minetest/bin/minetestserver --world /home/quentinbd/minetest/worlds/minetestforfun/ --config /home/quentinbd/minetest/minetest.conf --gameid minetestforfun_game --port 30001
----------------------
Server restarted at mardi 28 juillet 2015, 01:32:05 (UTC+0200)
----------------------
WARNING: system-wide share not found at "/usr/share/minetest"
WARNING: system-wide share not found at "/home/quentinbd/minetest/bin/../share/minetest"
WARNING: system-wide share found at "/home/quentinbd/minetest/bin/.."
Using game specified by --gameid on the command line
01:32:05: WARNING: Undeclared global variable "handlers" accessed at ...home/quentinbd/minetest/bin/../mods/irc/irc/main.lua:188
``` | 1.0 | Crash [Throwing] - #### Crash logs
http://zerobin.qbuissondebon.info/?643a724274bfff1b#Yx4yITyQ80CCU6zVWE5BxC6rUNT4bP1I1WveaZlO1Ho=
```
n]: [mana] Wrote mana data into /home/quentinbd/minetest/worlds/minetestforfun//mana.mt.
01:31:34: ACTION[main]: compassgps writing settings
01:31:34: ACTION[main]: Wrote quests to file
01:31:34: ACTION[main]: [PClasses] Datas saved
01:31:34: ACTION[main]: [tsm_pyramids] Chests saved
01:31:34: ACTION[main]: [fishing] Server shuts down. saving trophies table
01:31:35: ERROR[main]: ERROR: An unhandled exception occurred: ...uentinbd/minetest/bin/../mods/throwing/functions.lua:36: attempt to index a nil value
01:31:35: ERROR[main]: stack traceback:
01:31:35: ERROR[main]: ...uentinbd/minetest/bin/../mods/throwing/functions.lua:36: in function 'throwing_shoot_arrow'
01:31:35: ERROR[main]: ...uentinbd/minetest/bin/../mods/throwing/functions.lua:109: in function <...uentinbd/minetest/bin/../mods/throwing/functions.lua:103>
In thread 7f076f4d2740:
/home/quentinbd/minetest/src/main.cpp:882: int main(int, char**): Assertion '0' failed.
Debug stacks:
DEBUG STACK FOR THREAD 7f0768b3c700:
#0 virtual void* CurlFetchThread::Thread()
DEBUG STACK FOR THREAD 7f076f4d2740:
#0 int main(int, char**)
(Leftover data: #1 Dedicated server branch)
(Leftover data: #2 virtual void ServerMap::save(ModifiedState))
(Leftover data: #3 void ItemStack::serialize(std::ostream&) const)
/home/quentinbd/script/start02.sh : ligne 26 : 20913 Abandon /home/quentinbd/minetest/bin/minetestserver --world /home/quentinbd/minetest/worlds/minetestforfun/ --config /home/quentinbd/minetest/minetest.conf --gameid minetestforfun_game --port 30001
----------------------
Server restarted at mardi 28 juillet 2015, 01:32:05 (UTC+0200)
----------------------
WARNING: system-wide share not found at "/usr/share/minetest"
WARNING: system-wide share not found at "/home/quentinbd/minetest/bin/../share/minetest"
WARNING: system-wide share found at "/home/quentinbd/minetest/bin/.."
Using game specified by --gameid on the command line
01:32:05: WARNING: Undeclared global variable "handlers" accessed at ...home/quentinbd/minetest/bin/../mods/irc/irc/main.lua:188
``` | priority | crash crash logs n wrote mana data into home quentinbd minetest worlds minetestforfun mana mt action compassgps writing settings action wrote quests to file action datas saved action chests saved action server shuts down saving trophies table error error an unhandled exception occurred uentinbd minetest bin mods throwing functions lua attempt to index a nil value error stack traceback error uentinbd minetest bin mods throwing functions lua in function throwing shoot arrow error uentinbd minetest bin mods throwing functions lua in function in thread home quentinbd minetest src main cpp int main int char assertion failed debug stacks debug stack for thread virtual void curlfetchthread thread debug stack for thread int main int char leftover data dedicated server branch leftover data virtual void servermap save modifiedstate leftover data void itemstack serialize std ostream const home quentinbd script sh ligne abandon home quentinbd minetest bin minetestserver world home quentinbd minetest worlds minetestforfun config home quentinbd minetest minetest conf gameid minetestforfun game port server restarted at mardi juillet utc warning system wide share not found at usr share minetest warning system wide share not found at home quentinbd minetest bin share minetest warning system wide share found at home quentinbd minetest bin using game specified by gameid on the command line warning undeclared global variable handlers accessed at home quentinbd minetest bin mods irc irc main lua | 1 |
167,986 | 20,736,499,965 | IssuesEvent | 2022-03-14 14:10:28 | shaimael/AltoroJ | https://api.github.com/repos/shaimael/AltoroJ | opened | log4j-1.2.16.jar: 7 vulnerabilities (highest severity is: 9.8) | security vulnerability | <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>log4j-1.2.16.jar</b></p></summary>
<p>Apache Log4j 1.2</p>
<p>Path to dependency file: /AltoroJ 3.1.1/build.gradle</p>
<p>Path to vulnerable library: /gradle/caches/modules-2/files-2.1/log4j/log4j/1.2.16/7999a63bfccbc7c247a9aea10d83d4272bd492c6/log4j-1.2.16.jar</p>
<p>
</details>
## Vulnerabilities
| CVE | Severity | <img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS | Dependency | Type | Fixed in | Remediation Available |
| ------------- | ------------- | ----- | ----- | ----- | --- | --- |
| [CVE-2022-23307](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-23307) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 9.8 | log4j-1.2.16.jar | Direct | ch.qos.reload4j:reload4j:1.2.18.1 | ✅ |
| [CVE-2022-23305](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-23305) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 9.8 | log4j-1.2.16.jar | Direct | ch.qos.reload4j:reload4j:1.2.18.2 | ✅ |
| [CVE-2019-17571](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-17571) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 9.8 | log4j-1.2.16.jar | Direct | log4j-manual - 1.2.17-16;log4j-javadoc - 1.2.17-16;log4j - 1.2.17-16,1.2.17-16 | ❌ |
| [CVE-2020-9493](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-9493) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 9.8 | log4j-1.2.16.jar | Direct | ch.qos.reload4j:reload4j:1.2.18.1 | ✅ |
| [CVE-2022-23302](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-23302) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 8.8 | log4j-1.2.16.jar | Direct | ch.qos.reload4j:reload4j:1.2.18.1 | ✅ |
| [CVE-2021-4104](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-4104) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | log4j-1.2.16.jar | Direct | uom-parent - 1.0.3-3.module,1.0.3-3.module;uom-se-javadoc - 1.0.4-3.module;parfait-examples - 0.5.4-4.module;log4j-manual - 1.2.17-16;si-units-javadoc - 0.6.5-2.module;unit-api - 1.0-5.module,1.0-5.module;unit-api-javadoc - 1.0-5.module;parfait - 0.5.4-4.module,0.5.4-4.module;log4j-javadoc - 1.2.17-16;uom-systems-javadoc - 0.7-1.module;uom-lib-javadoc - 1.0.1-6.module;uom-systems - 0.7-1.module,0.7-1.module;log4j - 1.2.17-16,1.2.17-16;uom-se - 1.0.4-3.module,1.0.4-3.module;uom-lib - 1.0.1-6.module,1.0.1-6.module;parfait-javadoc - 0.5.4-4.module;pcp-parfait-agent - 0.5.4-4.module;si-units - 0.6.5-2.module,0.6.5-2.module | ❌ |
| [CVE-2020-9488](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-9488) | <img src='https://whitesource-resources.whitesourcesoftware.com/low_vul.png' width=19 height=20> Low | 3.7 | log4j-1.2.16.jar | Direct | ch.qos.reload4j:reload4j:1.2.18.3 | ✅ |
## Details
<details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2022-23307</summary>
### Vulnerable Library - <b>log4j-1.2.16.jar</b></p>
<p>Apache Log4j 1.2</p>
<p>Path to dependency file: /AltoroJ 3.1.1/build.gradle</p>
<p>Path to vulnerable library: /gradle/caches/modules-2/files-2.1/log4j/log4j/1.2.16/7999a63bfccbc7c247a9aea10d83d4272bd492c6/log4j-1.2.16.jar</p>
<p>
Dependency Hierarchy:
- :x: **log4j-1.2.16.jar** (Vulnerable Library)
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
CVE-2020-9493 identified a deserialization issue that was present in Apache Chainsaw. Prior to Chainsaw V2.0 Chainsaw was a component of Apache Log4j 1.2.x where the same issue exists.
<p>Publish Date: 2022-01-18
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-23307>CVE-2022-23307</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://reload4j.qos.ch/">https://reload4j.qos.ch/</a></p>
<p>Release Date: 2022-01-18</p>
<p>Fix Resolution: ch.qos.reload4j:reload4j:1.2.18.1</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation is available for this issue
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2022-23305</summary>
### Vulnerable Library - <b>log4j-1.2.16.jar</b></p>
<p>Apache Log4j 1.2</p>
<p>Path to dependency file: /AltoroJ 3.1.1/build.gradle</p>
<p>Path to vulnerable library: /gradle/caches/modules-2/files-2.1/log4j/log4j/1.2.16/7999a63bfccbc7c247a9aea10d83d4272bd492c6/log4j-1.2.16.jar</p>
<p>
Dependency Hierarchy:
- :x: **log4j-1.2.16.jar** (Vulnerable Library)
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
By design, the JDBCAppender in Log4j 1.2.x accepts an SQL statement as a configuration parameter where the values to be inserted are converters from PatternLayout. The message converter, %m, is likely to always be included. This allows attackers to manipulate the SQL by entering crafted strings into input fields or headers of an application that are logged allowing unintended SQL queries to be executed. Note this issue only affects Log4j 1.x when specifically configured to use the JDBCAppender, which is not the default. Beginning in version 2.0-beta8, the JDBCAppender was re-introduced with proper support for parameterized SQL queries and further customization over the columns written to in logs. Apache Log4j 1.2 reached end of life in August 2015. Users should upgrade to Log4j 2 as it addresses numerous other issues from the previous versions.
<p>Publish Date: 2022-01-18
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-23305>CVE-2022-23305</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://reload4j.qos.ch/">https://reload4j.qos.ch/</a></p>
<p>Release Date: 2022-01-18</p>
<p>Fix Resolution: ch.qos.reload4j:reload4j:1.2.18.2</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation is available for this issue
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2019-17571</summary>
### Vulnerable Library - <b>log4j-1.2.16.jar</b></p>
<p>Apache Log4j 1.2</p>
<p>Path to dependency file: /AltoroJ 3.1.1/build.gradle</p>
<p>Path to vulnerable library: /gradle/caches/modules-2/files-2.1/log4j/log4j/1.2.16/7999a63bfccbc7c247a9aea10d83d4272bd492c6/log4j-1.2.16.jar</p>
<p>
Dependency Hierarchy:
- :x: **log4j-1.2.16.jar** (Vulnerable Library)
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
Included in Log4j 1.2 is a SocketServer class that is vulnerable to deserialization of untrusted data which can be exploited to remotely execute arbitrary code when combined with a deserialization gadget when listening to untrusted network traffic for log data. This affects Log4j versions up to 1.2 up to 1.2.17.
<p>Publish Date: 2019-12-20
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-17571>CVE-2019-17571</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://nvd.nist.gov/vuln/detail/CVE-2019-17571">https://nvd.nist.gov/vuln/detail/CVE-2019-17571</a></p>
<p>Release Date: 2019-12-20</p>
<p>Fix Resolution: log4j-manual - 1.2.17-16;log4j-javadoc - 1.2.17-16;log4j - 1.2.17-16,1.2.17-16</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2020-9493</summary>
### Vulnerable Library - <b>log4j-1.2.16.jar</b></p>
<p>Apache Log4j 1.2</p>
<p>Path to dependency file: /AltoroJ 3.1.1/build.gradle</p>
<p>Path to vulnerable library: /gradle/caches/modules-2/files-2.1/log4j/log4j/1.2.16/7999a63bfccbc7c247a9aea10d83d4272bd492c6/log4j-1.2.16.jar</p>
<p>
Dependency Hierarchy:
- :x: **log4j-1.2.16.jar** (Vulnerable Library)
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
A deserialization flaw was found in Apache Chainsaw versions prior to 2.1.0 which could lead to malicious code execution.
<p>Publish Date: 2021-06-16
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-9493>CVE-2020-9493</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://reload4j.qos.ch/">https://reload4j.qos.ch/</a></p>
<p>Release Date: 2021-06-16</p>
<p>Fix Resolution: ch.qos.reload4j:reload4j:1.2.18.1</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation is available for this issue
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2022-23302</summary>
### Vulnerable Library - <b>log4j-1.2.16.jar</b></p>
<p>Apache Log4j 1.2</p>
<p>Path to dependency file: /AltoroJ 3.1.1/build.gradle</p>
<p>Path to vulnerable library: /gradle/caches/modules-2/files-2.1/log4j/log4j/1.2.16/7999a63bfccbc7c247a9aea10d83d4272bd492c6/log4j-1.2.16.jar</p>
<p>
Dependency Hierarchy:
- :x: **log4j-1.2.16.jar** (Vulnerable Library)
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
JMSSink in all versions of Log4j 1.x is vulnerable to deserialization of untrusted data when the attacker has write access to the Log4j configuration or if the configuration references an LDAP service the attacker has access to. The attacker can provide a TopicConnectionFactoryBindingName configuration causing JMSSink to perform JNDI requests that result in remote code execution in a similar fashion to CVE-2021-4104. Note this issue only affects Log4j 1.x when specifically configured to use JMSSink, which is not the default. Apache Log4j 1.2 reached end of life in August 2015. Users should upgrade to Log4j 2 as it addresses numerous other issues from the previous versions.
<p>Publish Date: 2022-01-18
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-23302>CVE-2022-23302</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>8.8</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: 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://reload4j.qos.ch/">https://reload4j.qos.ch/</a></p>
<p>Release Date: 2022-01-18</p>
<p>Fix Resolution: ch.qos.reload4j:reload4j:1.2.18.1</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation is available for this issue
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2021-4104</summary>
### Vulnerable Library - <b>log4j-1.2.16.jar</b></p>
<p>Apache Log4j 1.2</p>
<p>Path to dependency file: /AltoroJ 3.1.1/build.gradle</p>
<p>Path to vulnerable library: /gradle/caches/modules-2/files-2.1/log4j/log4j/1.2.16/7999a63bfccbc7c247a9aea10d83d4272bd492c6/log4j-1.2.16.jar</p>
<p>
Dependency Hierarchy:
- :x: **log4j-1.2.16.jar** (Vulnerable Library)
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
JMSAppender in Log4j 1.2 is vulnerable to deserialization of untrusted data when the attacker has write access to the Log4j configuration. The attacker can provide TopicBindingName and TopicConnectionFactoryBindingName configurations causing JMSAppender to perform JNDI requests that result in remote code execution in a similar fashion to CVE-2021-44228. Note this issue only affects Log4j 1.2 when specifically configured to use JMSAppender, which is not the default. Apache Log4j 1.2 reached end of life in August 2015. Users should upgrade to Log4j 2 as it addresses numerous other issues from the previous versions.
<p>Publish Date: 2021-12-14
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-4104>CVE-2021-4104</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>7.5</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: 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>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://nvd.nist.gov/vuln/detail/CVE-2021-4104">https://nvd.nist.gov/vuln/detail/CVE-2021-4104</a></p>
<p>Release Date: 2021-12-14</p>
<p>Fix Resolution: uom-parent - 1.0.3-3.module,1.0.3-3.module;uom-se-javadoc - 1.0.4-3.module;parfait-examples - 0.5.4-4.module;log4j-manual - 1.2.17-16;si-units-javadoc - 0.6.5-2.module;unit-api - 1.0-5.module,1.0-5.module;unit-api-javadoc - 1.0-5.module;parfait - 0.5.4-4.module,0.5.4-4.module;log4j-javadoc - 1.2.17-16;uom-systems-javadoc - 0.7-1.module;uom-lib-javadoc - 1.0.1-6.module;uom-systems - 0.7-1.module,0.7-1.module;log4j - 1.2.17-16,1.2.17-16;uom-se - 1.0.4-3.module,1.0.4-3.module;uom-lib - 1.0.1-6.module,1.0.1-6.module;parfait-javadoc - 0.5.4-4.module;pcp-parfait-agent - 0.5.4-4.module;si-units - 0.6.5-2.module,0.6.5-2.module</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/low_vul.png' width=19 height=20> CVE-2020-9488</summary>
### Vulnerable Library - <b>log4j-1.2.16.jar</b></p>
<p>Apache Log4j 1.2</p>
<p>Path to dependency file: /AltoroJ 3.1.1/build.gradle</p>
<p>Path to vulnerable library: /gradle/caches/modules-2/files-2.1/log4j/log4j/1.2.16/7999a63bfccbc7c247a9aea10d83d4272bd492c6/log4j-1.2.16.jar</p>
<p>
Dependency Hierarchy:
- :x: **log4j-1.2.16.jar** (Vulnerable Library)
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
Improper validation of certificate with host mismatch in Apache Log4j SMTP appender. This could allow an SMTPS connection to be intercepted by a man-in-the-middle attack which could leak any log messages sent through that appender.
<p>Publish Date: 2020-04-27
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-9488>CVE-2020-9488</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>3.7</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: None
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://reload4j.qos.ch/">https://reload4j.qos.ch/</a></p>
<p>Release Date: 2020-04-27</p>
<p>Fix Resolution: ch.qos.reload4j:reload4j:1.2.18.3</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation is available for this issue
</details>
***
<p>:rescue_worker_helmet: Automatic Remediation is available for this issue.</p>
<!-- <REMEDIATE>[{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"Java","groupId":"log4j","packageName":"log4j","packageVersion":"1.2.16","packageFilePaths":["/AltoroJ 3.1.1/build.gradle"],"isTransitiveDependency":false,"dependencyTree":"log4j:log4j:1.2.16","isMinimumFixVersionAvailable":true,"minimumFixVersion":"ch.qos.reload4j:reload4j:1.2.18.1","isBinary":false}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2022-23307","vulnerabilityDetails":"CVE-2020-9493 identified a deserialization issue that was present in Apache Chainsaw. Prior to Chainsaw V2.0 Chainsaw was a component of Apache Log4j 1.2.x where the same issue exists.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-23307","cvss3Severity":"high","cvss3Score":"9.8","cvss3Metrics":{"A":"High","AC":"Low","PR":"None","S":"Unchanged","C":"High","UI":"None","AV":"Network","I":"High"},"extraData":{}},{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"Java","groupId":"log4j","packageName":"log4j","packageVersion":"1.2.16","packageFilePaths":["/AltoroJ 3.1.1/build.gradle"],"isTransitiveDependency":false,"dependencyTree":"log4j:log4j:1.2.16","isMinimumFixVersionAvailable":true,"minimumFixVersion":"ch.qos.reload4j:reload4j:1.2.18.2","isBinary":false}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2022-23305","vulnerabilityDetails":"By design, the JDBCAppender in Log4j 1.2.x accepts an SQL statement as a configuration parameter where the values to be inserted are converters from PatternLayout. The message converter, %m, is likely to always be included. This allows attackers to manipulate the SQL by entering crafted strings into input fields or headers of an application that are logged allowing unintended SQL queries to be executed. Note this issue only affects Log4j 1.x when specifically configured to use the JDBCAppender, which is not the default. Beginning in version 2.0-beta8, the JDBCAppender was re-introduced with proper support for parameterized SQL queries and further customization over the columns written to in logs. Apache Log4j 1.2 reached end of life in August 2015. Users should upgrade to Log4j 2 as it addresses numerous other issues from the previous versions.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-23305","cvss3Severity":"high","cvss3Score":"9.8","cvss3Metrics":{"A":"High","AC":"Low","PR":"None","S":"Unchanged","C":"High","UI":"None","AV":"Network","I":"High"},"extraData":{}},{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"Java","groupId":"log4j","packageName":"log4j","packageVersion":"1.2.16","packageFilePaths":["/AltoroJ 3.1.1/build.gradle"],"isTransitiveDependency":false,"dependencyTree":"log4j:log4j:1.2.16","isMinimumFixVersionAvailable":true,"minimumFixVersion":"log4j-manual - 1.2.17-16;log4j-javadoc - 1.2.17-16;log4j - 1.2.17-16,1.2.17-16","isBinary":false}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2019-17571","vulnerabilityDetails":"Included in Log4j 1.2 is a SocketServer class that is vulnerable to deserialization of untrusted data which can be exploited to remotely execute arbitrary code when combined with a deserialization gadget when listening to untrusted network traffic for log data. This affects Log4j versions up to 1.2 up to 1.2.17.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-17571","cvss3Severity":"high","cvss3Score":"9.8","cvss3Metrics":{"A":"High","AC":"Low","PR":"None","S":"Unchanged","C":"High","UI":"None","AV":"Network","I":"High"},"extraData":{}},{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"Java","groupId":"log4j","packageName":"log4j","packageVersion":"1.2.16","packageFilePaths":["/AltoroJ 3.1.1/build.gradle"],"isTransitiveDependency":false,"dependencyTree":"log4j:log4j:1.2.16","isMinimumFixVersionAvailable":true,"minimumFixVersion":"ch.qos.reload4j:reload4j:1.2.18.1","isBinary":false}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2020-9493","vulnerabilityDetails":"A deserialization flaw was found in Apache Chainsaw versions prior to 2.1.0 which could lead to malicious code execution.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-9493","cvss3Severity":"high","cvss3Score":"9.8","cvss3Metrics":{"A":"High","AC":"Low","PR":"None","S":"Unchanged","C":"High","UI":"None","AV":"Network","I":"High"},"extraData":{}},{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"Java","groupId":"log4j","packageName":"log4j","packageVersion":"1.2.16","packageFilePaths":["/AltoroJ 3.1.1/build.gradle"],"isTransitiveDependency":false,"dependencyTree":"log4j:log4j:1.2.16","isMinimumFixVersionAvailable":true,"minimumFixVersion":"ch.qos.reload4j:reload4j:1.2.18.1","isBinary":false}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2022-23302","vulnerabilityDetails":"JMSSink in all versions of Log4j 1.x is vulnerable to deserialization of untrusted data when the attacker has write access to the Log4j configuration or if the configuration references an LDAP service the attacker has access to. The attacker can provide a TopicConnectionFactoryBindingName configuration causing JMSSink to perform JNDI requests that result in remote code execution in a similar fashion to CVE-2021-4104. Note this issue only affects Log4j 1.x when specifically configured to use JMSSink, which is not the default. Apache Log4j 1.2 reached end of life in August 2015. Users should upgrade to Log4j 2 as it addresses numerous other issues from the previous versions.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-23302","cvss3Severity":"high","cvss3Score":"8.8","cvss3Metrics":{"A":"High","AC":"Low","PR":"Low","S":"Unchanged","C":"High","UI":"None","AV":"Network","I":"High"},"extraData":{}},{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"Java","groupId":"log4j","packageName":"log4j","packageVersion":"1.2.16","packageFilePaths":["/AltoroJ 3.1.1/build.gradle"],"isTransitiveDependency":false,"dependencyTree":"log4j:log4j:1.2.16","isMinimumFixVersionAvailable":true,"minimumFixVersion":"uom-parent - 1.0.3-3.module,1.0.3-3.module;uom-se-javadoc - 1.0.4-3.module;parfait-examples - 0.5.4-4.module;log4j-manual - 1.2.17-16;si-units-javadoc - 0.6.5-2.module;unit-api - 1.0-5.module,1.0-5.module;unit-api-javadoc - 1.0-5.module;parfait - 0.5.4-4.module,0.5.4-4.module;log4j-javadoc - 1.2.17-16;uom-systems-javadoc - 0.7-1.module;uom-lib-javadoc - 1.0.1-6.module;uom-systems - 0.7-1.module,0.7-1.module;log4j - 1.2.17-16,1.2.17-16;uom-se - 1.0.4-3.module,1.0.4-3.module;uom-lib - 1.0.1-6.module,1.0.1-6.module;parfait-javadoc - 0.5.4-4.module;pcp-parfait-agent - 0.5.4-4.module;si-units - 0.6.5-2.module,0.6.5-2.module","isBinary":false}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2021-4104","vulnerabilityDetails":"JMSAppender in Log4j 1.2 is vulnerable to deserialization of untrusted data when the attacker has write access to the Log4j configuration. The attacker can provide TopicBindingName and TopicConnectionFactoryBindingName configurations causing JMSAppender to perform JNDI requests that result in remote code execution in a similar fashion to CVE-2021-44228. Note this issue only affects Log4j 1.2 when specifically configured to use JMSAppender, which is not the default. Apache Log4j 1.2 reached end of life in August 2015. Users should upgrade to Log4j 2 as it addresses numerous other issues from the previous versions.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-4104","cvss3Severity":"high","cvss3Score":"7.5","cvss3Metrics":{"A":"High","AC":"High","PR":"Low","S":"Unchanged","C":"High","UI":"None","AV":"Network","I":"High"},"extraData":{}},{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"Java","groupId":"log4j","packageName":"log4j","packageVersion":"1.2.16","packageFilePaths":["/AltoroJ 3.1.1/build.gradle"],"isTransitiveDependency":false,"dependencyTree":"log4j:log4j:1.2.16","isMinimumFixVersionAvailable":true,"minimumFixVersion":"ch.qos.reload4j:reload4j:1.2.18.3","isBinary":false}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2020-9488","vulnerabilityDetails":"Improper validation of certificate with host mismatch in Apache Log4j SMTP appender. This could allow an SMTPS connection to be intercepted by a man-in-the-middle attack which could leak any log messages sent through that appender.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-9488","cvss3Severity":"low","cvss3Score":"3.7","cvss3Metrics":{"A":"None","AC":"High","PR":"None","S":"Unchanged","C":"Low","UI":"None","AV":"Network","I":"None"},"extraData":{}}]</REMEDIATE> --> | True | log4j-1.2.16.jar: 7 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>log4j-1.2.16.jar</b></p></summary>
<p>Apache Log4j 1.2</p>
<p>Path to dependency file: /AltoroJ 3.1.1/build.gradle</p>
<p>Path to vulnerable library: /gradle/caches/modules-2/files-2.1/log4j/log4j/1.2.16/7999a63bfccbc7c247a9aea10d83d4272bd492c6/log4j-1.2.16.jar</p>
<p>
</details>
## Vulnerabilities
| CVE | Severity | <img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS | Dependency | Type | Fixed in | Remediation Available |
| ------------- | ------------- | ----- | ----- | ----- | --- | --- |
| [CVE-2022-23307](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-23307) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 9.8 | log4j-1.2.16.jar | Direct | ch.qos.reload4j:reload4j:1.2.18.1 | ✅ |
| [CVE-2022-23305](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-23305) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 9.8 | log4j-1.2.16.jar | Direct | ch.qos.reload4j:reload4j:1.2.18.2 | ✅ |
| [CVE-2019-17571](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-17571) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 9.8 | log4j-1.2.16.jar | Direct | log4j-manual - 1.2.17-16;log4j-javadoc - 1.2.17-16;log4j - 1.2.17-16,1.2.17-16 | ❌ |
| [CVE-2020-9493](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-9493) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 9.8 | log4j-1.2.16.jar | Direct | ch.qos.reload4j:reload4j:1.2.18.1 | ✅ |
| [CVE-2022-23302](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-23302) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 8.8 | log4j-1.2.16.jar | Direct | ch.qos.reload4j:reload4j:1.2.18.1 | ✅ |
| [CVE-2021-4104](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-4104) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | log4j-1.2.16.jar | Direct | uom-parent - 1.0.3-3.module,1.0.3-3.module;uom-se-javadoc - 1.0.4-3.module;parfait-examples - 0.5.4-4.module;log4j-manual - 1.2.17-16;si-units-javadoc - 0.6.5-2.module;unit-api - 1.0-5.module,1.0-5.module;unit-api-javadoc - 1.0-5.module;parfait - 0.5.4-4.module,0.5.4-4.module;log4j-javadoc - 1.2.17-16;uom-systems-javadoc - 0.7-1.module;uom-lib-javadoc - 1.0.1-6.module;uom-systems - 0.7-1.module,0.7-1.module;log4j - 1.2.17-16,1.2.17-16;uom-se - 1.0.4-3.module,1.0.4-3.module;uom-lib - 1.0.1-6.module,1.0.1-6.module;parfait-javadoc - 0.5.4-4.module;pcp-parfait-agent - 0.5.4-4.module;si-units - 0.6.5-2.module,0.6.5-2.module | ❌ |
| [CVE-2020-9488](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-9488) | <img src='https://whitesource-resources.whitesourcesoftware.com/low_vul.png' width=19 height=20> Low | 3.7 | log4j-1.2.16.jar | Direct | ch.qos.reload4j:reload4j:1.2.18.3 | ✅ |
## Details
<details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2022-23307</summary>
### Vulnerable Library - <b>log4j-1.2.16.jar</b></p>
<p>Apache Log4j 1.2</p>
<p>Path to dependency file: /AltoroJ 3.1.1/build.gradle</p>
<p>Path to vulnerable library: /gradle/caches/modules-2/files-2.1/log4j/log4j/1.2.16/7999a63bfccbc7c247a9aea10d83d4272bd492c6/log4j-1.2.16.jar</p>
<p>
Dependency Hierarchy:
- :x: **log4j-1.2.16.jar** (Vulnerable Library)
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
CVE-2020-9493 identified a deserialization issue that was present in Apache Chainsaw. Prior to Chainsaw V2.0 Chainsaw was a component of Apache Log4j 1.2.x where the same issue exists.
<p>Publish Date: 2022-01-18
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-23307>CVE-2022-23307</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://reload4j.qos.ch/">https://reload4j.qos.ch/</a></p>
<p>Release Date: 2022-01-18</p>
<p>Fix Resolution: ch.qos.reload4j:reload4j:1.2.18.1</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation is available for this issue
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2022-23305</summary>
### Vulnerable Library - <b>log4j-1.2.16.jar</b></p>
<p>Apache Log4j 1.2</p>
<p>Path to dependency file: /AltoroJ 3.1.1/build.gradle</p>
<p>Path to vulnerable library: /gradle/caches/modules-2/files-2.1/log4j/log4j/1.2.16/7999a63bfccbc7c247a9aea10d83d4272bd492c6/log4j-1.2.16.jar</p>
<p>
Dependency Hierarchy:
- :x: **log4j-1.2.16.jar** (Vulnerable Library)
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
By design, the JDBCAppender in Log4j 1.2.x accepts an SQL statement as a configuration parameter where the values to be inserted are converters from PatternLayout. The message converter, %m, is likely to always be included. This allows attackers to manipulate the SQL by entering crafted strings into input fields or headers of an application that are logged allowing unintended SQL queries to be executed. Note this issue only affects Log4j 1.x when specifically configured to use the JDBCAppender, which is not the default. Beginning in version 2.0-beta8, the JDBCAppender was re-introduced with proper support for parameterized SQL queries and further customization over the columns written to in logs. Apache Log4j 1.2 reached end of life in August 2015. Users should upgrade to Log4j 2 as it addresses numerous other issues from the previous versions.
<p>Publish Date: 2022-01-18
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-23305>CVE-2022-23305</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://reload4j.qos.ch/">https://reload4j.qos.ch/</a></p>
<p>Release Date: 2022-01-18</p>
<p>Fix Resolution: ch.qos.reload4j:reload4j:1.2.18.2</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation is available for this issue
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2019-17571</summary>
### Vulnerable Library - <b>log4j-1.2.16.jar</b></p>
<p>Apache Log4j 1.2</p>
<p>Path to dependency file: /AltoroJ 3.1.1/build.gradle</p>
<p>Path to vulnerable library: /gradle/caches/modules-2/files-2.1/log4j/log4j/1.2.16/7999a63bfccbc7c247a9aea10d83d4272bd492c6/log4j-1.2.16.jar</p>
<p>
Dependency Hierarchy:
- :x: **log4j-1.2.16.jar** (Vulnerable Library)
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
Included in Log4j 1.2 is a SocketServer class that is vulnerable to deserialization of untrusted data which can be exploited to remotely execute arbitrary code when combined with a deserialization gadget when listening to untrusted network traffic for log data. This affects Log4j versions up to 1.2 up to 1.2.17.
<p>Publish Date: 2019-12-20
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-17571>CVE-2019-17571</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://nvd.nist.gov/vuln/detail/CVE-2019-17571">https://nvd.nist.gov/vuln/detail/CVE-2019-17571</a></p>
<p>Release Date: 2019-12-20</p>
<p>Fix Resolution: log4j-manual - 1.2.17-16;log4j-javadoc - 1.2.17-16;log4j - 1.2.17-16,1.2.17-16</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2020-9493</summary>
### Vulnerable Library - <b>log4j-1.2.16.jar</b></p>
<p>Apache Log4j 1.2</p>
<p>Path to dependency file: /AltoroJ 3.1.1/build.gradle</p>
<p>Path to vulnerable library: /gradle/caches/modules-2/files-2.1/log4j/log4j/1.2.16/7999a63bfccbc7c247a9aea10d83d4272bd492c6/log4j-1.2.16.jar</p>
<p>
Dependency Hierarchy:
- :x: **log4j-1.2.16.jar** (Vulnerable Library)
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
A deserialization flaw was found in Apache Chainsaw versions prior to 2.1.0 which could lead to malicious code execution.
<p>Publish Date: 2021-06-16
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-9493>CVE-2020-9493</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://reload4j.qos.ch/">https://reload4j.qos.ch/</a></p>
<p>Release Date: 2021-06-16</p>
<p>Fix Resolution: ch.qos.reload4j:reload4j:1.2.18.1</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation is available for this issue
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2022-23302</summary>
### Vulnerable Library - <b>log4j-1.2.16.jar</b></p>
<p>Apache Log4j 1.2</p>
<p>Path to dependency file: /AltoroJ 3.1.1/build.gradle</p>
<p>Path to vulnerable library: /gradle/caches/modules-2/files-2.1/log4j/log4j/1.2.16/7999a63bfccbc7c247a9aea10d83d4272bd492c6/log4j-1.2.16.jar</p>
<p>
Dependency Hierarchy:
- :x: **log4j-1.2.16.jar** (Vulnerable Library)
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
JMSSink in all versions of Log4j 1.x is vulnerable to deserialization of untrusted data when the attacker has write access to the Log4j configuration or if the configuration references an LDAP service the attacker has access to. The attacker can provide a TopicConnectionFactoryBindingName configuration causing JMSSink to perform JNDI requests that result in remote code execution in a similar fashion to CVE-2021-4104. Note this issue only affects Log4j 1.x when specifically configured to use JMSSink, which is not the default. Apache Log4j 1.2 reached end of life in August 2015. Users should upgrade to Log4j 2 as it addresses numerous other issues from the previous versions.
<p>Publish Date: 2022-01-18
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-23302>CVE-2022-23302</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>8.8</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: 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://reload4j.qos.ch/">https://reload4j.qos.ch/</a></p>
<p>Release Date: 2022-01-18</p>
<p>Fix Resolution: ch.qos.reload4j:reload4j:1.2.18.1</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation is available for this issue
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2021-4104</summary>
### Vulnerable Library - <b>log4j-1.2.16.jar</b></p>
<p>Apache Log4j 1.2</p>
<p>Path to dependency file: /AltoroJ 3.1.1/build.gradle</p>
<p>Path to vulnerable library: /gradle/caches/modules-2/files-2.1/log4j/log4j/1.2.16/7999a63bfccbc7c247a9aea10d83d4272bd492c6/log4j-1.2.16.jar</p>
<p>
Dependency Hierarchy:
- :x: **log4j-1.2.16.jar** (Vulnerable Library)
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
JMSAppender in Log4j 1.2 is vulnerable to deserialization of untrusted data when the attacker has write access to the Log4j configuration. The attacker can provide TopicBindingName and TopicConnectionFactoryBindingName configurations causing JMSAppender to perform JNDI requests that result in remote code execution in a similar fashion to CVE-2021-44228. Note this issue only affects Log4j 1.2 when specifically configured to use JMSAppender, which is not the default. Apache Log4j 1.2 reached end of life in August 2015. Users should upgrade to Log4j 2 as it addresses numerous other issues from the previous versions.
<p>Publish Date: 2021-12-14
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-4104>CVE-2021-4104</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>7.5</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: 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>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://nvd.nist.gov/vuln/detail/CVE-2021-4104">https://nvd.nist.gov/vuln/detail/CVE-2021-4104</a></p>
<p>Release Date: 2021-12-14</p>
<p>Fix Resolution: uom-parent - 1.0.3-3.module,1.0.3-3.module;uom-se-javadoc - 1.0.4-3.module;parfait-examples - 0.5.4-4.module;log4j-manual - 1.2.17-16;si-units-javadoc - 0.6.5-2.module;unit-api - 1.0-5.module,1.0-5.module;unit-api-javadoc - 1.0-5.module;parfait - 0.5.4-4.module,0.5.4-4.module;log4j-javadoc - 1.2.17-16;uom-systems-javadoc - 0.7-1.module;uom-lib-javadoc - 1.0.1-6.module;uom-systems - 0.7-1.module,0.7-1.module;log4j - 1.2.17-16,1.2.17-16;uom-se - 1.0.4-3.module,1.0.4-3.module;uom-lib - 1.0.1-6.module,1.0.1-6.module;parfait-javadoc - 0.5.4-4.module;pcp-parfait-agent - 0.5.4-4.module;si-units - 0.6.5-2.module,0.6.5-2.module</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/low_vul.png' width=19 height=20> CVE-2020-9488</summary>
### Vulnerable Library - <b>log4j-1.2.16.jar</b></p>
<p>Apache Log4j 1.2</p>
<p>Path to dependency file: /AltoroJ 3.1.1/build.gradle</p>
<p>Path to vulnerable library: /gradle/caches/modules-2/files-2.1/log4j/log4j/1.2.16/7999a63bfccbc7c247a9aea10d83d4272bd492c6/log4j-1.2.16.jar</p>
<p>
Dependency Hierarchy:
- :x: **log4j-1.2.16.jar** (Vulnerable Library)
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
Improper validation of certificate with host mismatch in Apache Log4j SMTP appender. This could allow an SMTPS connection to be intercepted by a man-in-the-middle attack which could leak any log messages sent through that appender.
<p>Publish Date: 2020-04-27
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-9488>CVE-2020-9488</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>3.7</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: None
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://reload4j.qos.ch/">https://reload4j.qos.ch/</a></p>
<p>Release Date: 2020-04-27</p>
<p>Fix Resolution: ch.qos.reload4j:reload4j:1.2.18.3</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation is available for this issue
</details>
***
<p>:rescue_worker_helmet: Automatic Remediation is available for this issue.</p>
<!-- <REMEDIATE>[{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"Java","groupId":"log4j","packageName":"log4j","packageVersion":"1.2.16","packageFilePaths":["/AltoroJ 3.1.1/build.gradle"],"isTransitiveDependency":false,"dependencyTree":"log4j:log4j:1.2.16","isMinimumFixVersionAvailable":true,"minimumFixVersion":"ch.qos.reload4j:reload4j:1.2.18.1","isBinary":false}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2022-23307","vulnerabilityDetails":"CVE-2020-9493 identified a deserialization issue that was present in Apache Chainsaw. Prior to Chainsaw V2.0 Chainsaw was a component of Apache Log4j 1.2.x where the same issue exists.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-23307","cvss3Severity":"high","cvss3Score":"9.8","cvss3Metrics":{"A":"High","AC":"Low","PR":"None","S":"Unchanged","C":"High","UI":"None","AV":"Network","I":"High"},"extraData":{}},{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"Java","groupId":"log4j","packageName":"log4j","packageVersion":"1.2.16","packageFilePaths":["/AltoroJ 3.1.1/build.gradle"],"isTransitiveDependency":false,"dependencyTree":"log4j:log4j:1.2.16","isMinimumFixVersionAvailable":true,"minimumFixVersion":"ch.qos.reload4j:reload4j:1.2.18.2","isBinary":false}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2022-23305","vulnerabilityDetails":"By design, the JDBCAppender in Log4j 1.2.x accepts an SQL statement as a configuration parameter where the values to be inserted are converters from PatternLayout. The message converter, %m, is likely to always be included. This allows attackers to manipulate the SQL by entering crafted strings into input fields or headers of an application that are logged allowing unintended SQL queries to be executed. Note this issue only affects Log4j 1.x when specifically configured to use the JDBCAppender, which is not the default. Beginning in version 2.0-beta8, the JDBCAppender was re-introduced with proper support for parameterized SQL queries and further customization over the columns written to in logs. Apache Log4j 1.2 reached end of life in August 2015. Users should upgrade to Log4j 2 as it addresses numerous other issues from the previous versions.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-23305","cvss3Severity":"high","cvss3Score":"9.8","cvss3Metrics":{"A":"High","AC":"Low","PR":"None","S":"Unchanged","C":"High","UI":"None","AV":"Network","I":"High"},"extraData":{}},{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"Java","groupId":"log4j","packageName":"log4j","packageVersion":"1.2.16","packageFilePaths":["/AltoroJ 3.1.1/build.gradle"],"isTransitiveDependency":false,"dependencyTree":"log4j:log4j:1.2.16","isMinimumFixVersionAvailable":true,"minimumFixVersion":"log4j-manual - 1.2.17-16;log4j-javadoc - 1.2.17-16;log4j - 1.2.17-16,1.2.17-16","isBinary":false}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2019-17571","vulnerabilityDetails":"Included in Log4j 1.2 is a SocketServer class that is vulnerable to deserialization of untrusted data which can be exploited to remotely execute arbitrary code when combined with a deserialization gadget when listening to untrusted network traffic for log data. This affects Log4j versions up to 1.2 up to 1.2.17.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2019-17571","cvss3Severity":"high","cvss3Score":"9.8","cvss3Metrics":{"A":"High","AC":"Low","PR":"None","S":"Unchanged","C":"High","UI":"None","AV":"Network","I":"High"},"extraData":{}},{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"Java","groupId":"log4j","packageName":"log4j","packageVersion":"1.2.16","packageFilePaths":["/AltoroJ 3.1.1/build.gradle"],"isTransitiveDependency":false,"dependencyTree":"log4j:log4j:1.2.16","isMinimumFixVersionAvailable":true,"minimumFixVersion":"ch.qos.reload4j:reload4j:1.2.18.1","isBinary":false}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2020-9493","vulnerabilityDetails":"A deserialization flaw was found in Apache Chainsaw versions prior to 2.1.0 which could lead to malicious code execution.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-9493","cvss3Severity":"high","cvss3Score":"9.8","cvss3Metrics":{"A":"High","AC":"Low","PR":"None","S":"Unchanged","C":"High","UI":"None","AV":"Network","I":"High"},"extraData":{}},{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"Java","groupId":"log4j","packageName":"log4j","packageVersion":"1.2.16","packageFilePaths":["/AltoroJ 3.1.1/build.gradle"],"isTransitiveDependency":false,"dependencyTree":"log4j:log4j:1.2.16","isMinimumFixVersionAvailable":true,"minimumFixVersion":"ch.qos.reload4j:reload4j:1.2.18.1","isBinary":false}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2022-23302","vulnerabilityDetails":"JMSSink in all versions of Log4j 1.x is vulnerable to deserialization of untrusted data when the attacker has write access to the Log4j configuration or if the configuration references an LDAP service the attacker has access to. The attacker can provide a TopicConnectionFactoryBindingName configuration causing JMSSink to perform JNDI requests that result in remote code execution in a similar fashion to CVE-2021-4104. Note this issue only affects Log4j 1.x when specifically configured to use JMSSink, which is not the default. Apache Log4j 1.2 reached end of life in August 2015. Users should upgrade to Log4j 2 as it addresses numerous other issues from the previous versions.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-23302","cvss3Severity":"high","cvss3Score":"8.8","cvss3Metrics":{"A":"High","AC":"Low","PR":"Low","S":"Unchanged","C":"High","UI":"None","AV":"Network","I":"High"},"extraData":{}},{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"Java","groupId":"log4j","packageName":"log4j","packageVersion":"1.2.16","packageFilePaths":["/AltoroJ 3.1.1/build.gradle"],"isTransitiveDependency":false,"dependencyTree":"log4j:log4j:1.2.16","isMinimumFixVersionAvailable":true,"minimumFixVersion":"uom-parent - 1.0.3-3.module,1.0.3-3.module;uom-se-javadoc - 1.0.4-3.module;parfait-examples - 0.5.4-4.module;log4j-manual - 1.2.17-16;si-units-javadoc - 0.6.5-2.module;unit-api - 1.0-5.module,1.0-5.module;unit-api-javadoc - 1.0-5.module;parfait - 0.5.4-4.module,0.5.4-4.module;log4j-javadoc - 1.2.17-16;uom-systems-javadoc - 0.7-1.module;uom-lib-javadoc - 1.0.1-6.module;uom-systems - 0.7-1.module,0.7-1.module;log4j - 1.2.17-16,1.2.17-16;uom-se - 1.0.4-3.module,1.0.4-3.module;uom-lib - 1.0.1-6.module,1.0.1-6.module;parfait-javadoc - 0.5.4-4.module;pcp-parfait-agent - 0.5.4-4.module;si-units - 0.6.5-2.module,0.6.5-2.module","isBinary":false}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2021-4104","vulnerabilityDetails":"JMSAppender in Log4j 1.2 is vulnerable to deserialization of untrusted data when the attacker has write access to the Log4j configuration. The attacker can provide TopicBindingName and TopicConnectionFactoryBindingName configurations causing JMSAppender to perform JNDI requests that result in remote code execution in a similar fashion to CVE-2021-44228. Note this issue only affects Log4j 1.2 when specifically configured to use JMSAppender, which is not the default. Apache Log4j 1.2 reached end of life in August 2015. Users should upgrade to Log4j 2 as it addresses numerous other issues from the previous versions.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-4104","cvss3Severity":"high","cvss3Score":"7.5","cvss3Metrics":{"A":"High","AC":"High","PR":"Low","S":"Unchanged","C":"High","UI":"None","AV":"Network","I":"High"},"extraData":{}},{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"Java","groupId":"log4j","packageName":"log4j","packageVersion":"1.2.16","packageFilePaths":["/AltoroJ 3.1.1/build.gradle"],"isTransitiveDependency":false,"dependencyTree":"log4j:log4j:1.2.16","isMinimumFixVersionAvailable":true,"minimumFixVersion":"ch.qos.reload4j:reload4j:1.2.18.3","isBinary":false}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2020-9488","vulnerabilityDetails":"Improper validation of certificate with host mismatch in Apache Log4j SMTP appender. This could allow an SMTPS connection to be intercepted by a man-in-the-middle attack which could leak any log messages sent through that appender.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-9488","cvss3Severity":"low","cvss3Score":"3.7","cvss3Metrics":{"A":"None","AC":"High","PR":"None","S":"Unchanged","C":"Low","UI":"None","AV":"Network","I":"None"},"extraData":{}}]</REMEDIATE> --> | non_priority | jar vulnerabilities highest severity is vulnerable library jar apache path to dependency file altoroj build gradle path to vulnerable library gradle caches modules files jar vulnerabilities cve severity cvss dependency type fixed in remediation available high jar direct ch qos high jar direct ch qos high jar direct manual javadoc high jar direct ch qos high jar direct ch qos high jar direct uom parent module module uom se javadoc module parfait examples module manual si units javadoc module unit api module module unit api javadoc module parfait module module javadoc uom systems javadoc module uom lib javadoc module uom systems module module uom se module module uom lib module module parfait javadoc module pcp parfait agent module si units module module low jar direct ch qos details cve vulnerable library jar apache path to dependency file altoroj build gradle path to vulnerable library gradle caches modules files jar dependency hierarchy x jar vulnerable library found in base branch master vulnerability details cve identified a deserialization issue that was present in apache chainsaw prior to chainsaw chainsaw was a component of apache x where the same issue exists 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 ch qos rescue worker helmet automatic remediation is available for this issue cve vulnerable library jar apache path to dependency file altoroj build gradle path to vulnerable library gradle caches modules files jar dependency hierarchy x jar vulnerable library found in base branch master vulnerability details by design the jdbcappender in x accepts an sql statement as a configuration parameter where the values to be inserted are converters from patternlayout the message converter m is likely to always be included this allows attackers to manipulate the sql by entering crafted strings into input fields or headers of an application that are logged allowing unintended sql queries to be executed note this issue only affects x when specifically configured to use the jdbcappender which is not the default beginning in version the jdbcappender was re introduced with proper support for parameterized sql queries and further customization over the columns written to in logs apache reached end of life in august users should upgrade to as it addresses numerous other issues from the previous versions publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required 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 ch qos rescue worker helmet automatic remediation is available for this issue cve vulnerable library jar apache path to dependency file altoroj build gradle path to vulnerable library gradle caches modules files jar dependency hierarchy x jar vulnerable library found in base branch master vulnerability details included in is a socketserver class that is vulnerable to deserialization of untrusted data which can be exploited to remotely execute arbitrary code when combined with a deserialization gadget when listening to untrusted network traffic for log data this affects versions up to up to publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction 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 manual javadoc cve vulnerable library jar apache path to dependency file altoroj build gradle path to vulnerable library gradle caches modules files jar dependency hierarchy x jar vulnerable library found in base branch master vulnerability details a deserialization flaw was found in apache chainsaw versions prior to which could lead to malicious 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 ch qos rescue worker helmet automatic remediation is available for this issue cve vulnerable library jar apache path to dependency file altoroj build gradle path to vulnerable library gradle caches modules files jar dependency hierarchy x jar vulnerable library found in base branch master vulnerability details jmssink in all versions of x is vulnerable to deserialization of untrusted data when the attacker has write access to the configuration or if the configuration references an ldap service the attacker has access to the attacker can provide a topicconnectionfactorybindingname configuration causing jmssink to perform jndi requests that result in remote code execution in a similar fashion to cve note this issue only affects x when specifically configured to use jmssink which is not the default apache reached end of life in august users should upgrade to as it addresses numerous other issues from the previous versions publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required low user interaction none scope unchanged impact metrics confidentiality impact high integrity impact high availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution ch qos rescue worker helmet automatic remediation is available for this issue cve vulnerable library jar apache path to dependency file altoroj build gradle path to vulnerable library gradle caches modules files jar dependency hierarchy x jar vulnerable library found in base branch master vulnerability details jmsappender in is vulnerable to deserialization of untrusted data when the attacker has write access to the configuration the attacker can provide topicbindingname and topicconnectionfactorybindingname configurations causing jmsappender to perform jndi requests that result in remote code execution in a similar fashion to cve note this issue only affects when specifically configured to use jmsappender which is not the default apache reached end of life in august users should upgrade to as it addresses numerous other issues from the previous versions publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity 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 uom parent module module uom se javadoc module parfait examples module manual si units javadoc module unit api module module unit api javadoc module parfait module module javadoc uom systems javadoc module uom lib javadoc module uom systems module module uom se module module uom lib module module parfait javadoc module pcp parfait agent module si units module module cve vulnerable library jar apache path to dependency file altoroj build gradle path to vulnerable library gradle caches modules files jar dependency hierarchy x jar vulnerable library found in base branch master vulnerability details improper validation of certificate with host mismatch in apache smtp appender this could allow an smtps connection to be intercepted by a man in the middle attack which could leak any log messages sent through that appender 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 none availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution ch qos rescue worker helmet automatic remediation is available for this issue rescue worker helmet automatic remediation is available for this issue istransitivedependency false dependencytree isminimumfixversionavailable true minimumfixversion ch qos isbinary false basebranches vulnerabilityidentifier cve vulnerabilitydetails cve identified a deserialization issue that was present in apache chainsaw prior to chainsaw chainsaw was a component of apache x where the same issue exists vulnerabilityurl istransitivedependency false dependencytree isminimumfixversionavailable true minimumfixversion ch qos isbinary false basebranches vulnerabilityidentifier cve vulnerabilitydetails by design the jdbcappender in x accepts an sql statement as a configuration parameter where the values to be inserted are converters from patternlayout the message converter m is likely to always be included this allows attackers to manipulate the sql by entering crafted strings into input fields or headers of an application that are logged allowing unintended sql queries to be executed note this issue only affects x when specifically configured to use the jdbcappender which is not the default beginning in version the jdbcappender was re introduced with proper support for parameterized sql queries and further customization over the columns written to in logs apache reached end of life in august users should upgrade to as it addresses numerous other issues from the previous versions vulnerabilityurl istransitivedependency false dependencytree isminimumfixversionavailable true minimumfixversion manual javadoc isbinary false basebranches vulnerabilityidentifier cve vulnerabilitydetails included in is a socketserver class that is vulnerable to deserialization of untrusted data which can be exploited to remotely execute arbitrary code when combined with a deserialization gadget when listening to untrusted network traffic for log data this affects versions up to up to vulnerabilityurl istransitivedependency false dependencytree isminimumfixversionavailable true minimumfixversion ch qos isbinary false basebranches vulnerabilityidentifier cve vulnerabilitydetails a deserialization flaw was found in apache chainsaw versions prior to which could lead to malicious code execution vulnerabilityurl istransitivedependency false dependencytree isminimumfixversionavailable true minimumfixversion ch qos isbinary false basebranches vulnerabilityidentifier cve vulnerabilitydetails jmssink in all versions of x is vulnerable to deserialization of untrusted data when the attacker has write access to the configuration or if the configuration references an ldap service the attacker has access to the attacker can provide a topicconnectionfactorybindingname configuration causing jmssink to perform jndi requests that result in remote code execution in a similar fashion to cve note this issue only affects x when specifically configured to use jmssink which is not the default apache reached end of life in august users should upgrade to as it addresses numerous other issues from the previous versions vulnerabilityurl istransitivedependency false dependencytree isminimumfixversionavailable true minimumfixversion uom parent module module uom se javadoc module parfait examples module manual si units javadoc module unit api module module unit api javadoc module parfait module module javadoc uom systems javadoc module uom lib javadoc module uom systems module module uom se module module uom lib module module parfait javadoc module pcp parfait agent module si units module module isbinary false basebranches vulnerabilityidentifier cve vulnerabilitydetails jmsappender in is vulnerable to deserialization of untrusted data when the attacker has write access to the configuration the attacker can provide topicbindingname and topicconnectionfactorybindingname configurations causing jmsappender to perform jndi requests that result in remote code execution in a similar fashion to cve note this issue only affects when specifically configured to use jmsappender which is not the default apache reached end of life in august users should upgrade to as it addresses numerous other issues from the previous versions vulnerabilityurl istransitivedependency false dependencytree isminimumfixversionavailable true minimumfixversion ch qos isbinary false basebranches vulnerabilityidentifier cve vulnerabilitydetails improper validation of certificate with host mismatch in apache smtp appender this could allow an smtps connection to be intercepted by a man in the middle attack which could leak any log messages sent through that appender vulnerabilityurl | 0 |
305,914 | 23,137,223,395 | IssuesEvent | 2022-07-28 15:10:39 | ERNI-Academy/asset-iac-terraform-azure | https://api.github.com/repos/ERNI-Academy/asset-iac-terraform-azure | closed | Documentation: Contributors list is empty | documentation | ### Explain in 1-2 sentences. Say what this is about.
Please add contributors to this repository
### Motivation Goals
-
### In scope
-
### Out of scope
-
### Risks / unknowns
-
### Examples
_No response_ | 1.0 | Documentation: Contributors list is empty - ### Explain in 1-2 sentences. Say what this is about.
Please add contributors to this repository
### Motivation Goals
-
### In scope
-
### Out of scope
-
### Risks / unknowns
-
### Examples
_No response_ | non_priority | documentation contributors list is empty explain in sentences say what this is about please add contributors to this repository motivation goals in scope out of scope risks unknowns examples no response | 0 |
359,219 | 10,666,969,701 | IssuesEvent | 2019-10-19 08:36:17 | kobotoolbox/kpi | https://api.github.com/repos/kobotoolbox/kpi | closed | Allow users to add custom wrapper code for REST submissions | enhancement high priority | ERROR: type should be string, got "https://www.flowdock.com/app/kobotoolbox/kobo/threads/mRpcBQgbF0_UeIgyXybyDxueOW3\r\n\r\n- [x] FE UI work as shown below\r\n- [x] FE interchange with \"Add custom wrapper\" using `hook` attribute called `payload_template`\r\n- [x] BE uses template when `POST`ing to external server (@noliveleger)\r\n\r\n## Description\r\n\r\nAs a user I'd like to be able to submit data to AirTable and similar services. AirTable requires a wrapper around the actual JSON submission, which I would like to specify in the UI when creating a new REST service. \r\n\r\n## Suggested UI design\r\n\r\n\r\n\r\n## Example wrapper code \r\n\r\n```\r\n{\r\n \"fields\": %SUBMISSION%\r\n}\r\n```\r\n" | 1.0 | Allow users to add custom wrapper code for REST submissions - https://www.flowdock.com/app/kobotoolbox/kobo/threads/mRpcBQgbF0_UeIgyXybyDxueOW3
- [x] FE UI work as shown below
- [x] FE interchange with "Add custom wrapper" using `hook` attribute called `payload_template`
- [x] BE uses template when `POST`ing to external server (@noliveleger)
## Description
As a user I'd like to be able to submit data to AirTable and similar services. AirTable requires a wrapper around the actual JSON submission, which I would like to specify in the UI when creating a new REST service.
## Suggested UI design
## Example wrapper code
```
{
"fields": %SUBMISSION%
}
```
| priority | allow users to add custom wrapper code for rest submissions fe ui work as shown below fe interchange with add custom wrapper using hook attribute called payload template be uses template when post ing to external server noliveleger description as a user i d like to be able to submit data to airtable and similar services airtable requires a wrapper around the actual json submission which i would like to specify in the ui when creating a new rest service suggested ui design example wrapper code fields submission | 1 |
362,796 | 10,732,119,268 | IssuesEvent | 2019-10-28 21:05:20 | yugabyte/yugabyte-db | https://api.github.com/repos/yugabyte/yugabyte-db | closed | [Platform] Fix the master placement logic when doing a full move | area/platform kind/bug priority/high | There seem to be some issue with the master placement logic when doing a large cluster full move. | 1.0 | [Platform] Fix the master placement logic when doing a full move - There seem to be some issue with the master placement logic when doing a large cluster full move. | priority | fix the master placement logic when doing a full move there seem to be some issue with the master placement logic when doing a large cluster full move | 1 |
316,867 | 9,658,080,909 | IssuesEvent | 2019-05-20 10:05:18 | bbaumgartl/test | https://api.github.com/repos/bbaumgartl/test | closed | Support for Showing only a defined List auf countries which is from static_info_tables | Priority: Should have Status: Closed Tracker: Feature | ---
Author Name: **Josef F. Glatz (Old User)** (Josef F. Glatz (Old User))
Original Redmine Issue: 31665, https://forge.typo3.org/issues/31665
Original Date: 2011-11-08
Original Assignee: Bernhard Baumgartl, datamints GmbH
---
Hello,
I'm searching for a register and edit extension for fe_users which supports md5 and saltedpasswords. Your extension looks good to me, because your extension meets all requirements.
Is it also possible to implement a feature to show a selectbox in frontend, where the fe_user can select one of the available countries?
thx in advance
| 1.0 | Support for Showing only a defined List auf countries which is from static_info_tables - ---
Author Name: **Josef F. Glatz (Old User)** (Josef F. Glatz (Old User))
Original Redmine Issue: 31665, https://forge.typo3.org/issues/31665
Original Date: 2011-11-08
Original Assignee: Bernhard Baumgartl, datamints GmbH
---
Hello,
I'm searching for a register and edit extension for fe_users which supports md5 and saltedpasswords. Your extension looks good to me, because your extension meets all requirements.
Is it also possible to implement a feature to show a selectbox in frontend, where the fe_user can select one of the available countries?
thx in advance
| priority | support for showing only a defined list auf countries which is from static info tables author name josef f glatz old user josef f glatz old user original redmine issue original date original assignee bernhard baumgartl datamints gmbh hello i m searching for a register and edit extension for fe users which supports and saltedpasswords your extension looks good to me because your extension meets all requirements is it also possible to implement a feature to show a selectbox in frontend where the fe user can select one of the available countries thx in advance | 1 |
165,219 | 20,574,349,266 | IssuesEvent | 2022-03-04 01:47:27 | rvvergara/haiku-rails-api | https://api.github.com/repos/rvvergara/haiku-rails-api | opened | CVE-2020-26247 (Medium) detected in nokogiri-1.10.10.gem | security vulnerability | ## CVE-2020-26247 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>nokogiri-1.10.10.gem</b></p></summary>
<p>Nokogiri (鋸) is an HTML, XML, SAX, and Reader parser. Among
Nokogiri's many features is the ability to search documents via XPath
or CSS3 selectors.</p>
<p>Library home page: <a href="https://rubygems.org/gems/nokogiri-1.10.10.gem">https://rubygems.org/gems/nokogiri-1.10.10.gem</a></p>
<p>
Dependency Hierarchy:
- devise-4.7.1.gem (Root Library)
- railties-5.2.4.3.gem
- actionpack-5.2.4.3.gem
- rails-dom-testing-2.0.3.gem
- :x: **nokogiri-1.10.10.gem** (Vulnerable Library)
<p>Found in base branch: <b>development</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>
Nokogiri is a Rubygem providing HTML, XML, SAX, and Reader parsers with XPath and CSS selector support. In Nokogiri before version 1.11.0.rc4 there is an XXE vulnerability. XML Schemas parsed by Nokogiri::XML::Schema are trusted by default, allowing external resources to be accessed over the network, potentially enabling XXE or SSRF attacks. This behavior is counter to the security policy followed by Nokogiri maintainers, which is to treat all input as untrusted by default whenever possible. This is fixed in Nokogiri version 1.11.0.rc4.
<p>Publish Date: 2020-12-30
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-26247>CVE-2020-26247</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>4.3</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: None
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/sparklemotion/nokogiri/releases/tag/v1.11.0.rc4">https://github.com/sparklemotion/nokogiri/releases/tag/v1.11.0.rc4</a></p>
<p>Release Date: 2020-12-30</p>
<p>Fix Resolution: 1.11.0.rc4</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-26247 (Medium) detected in nokogiri-1.10.10.gem - ## CVE-2020-26247 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>nokogiri-1.10.10.gem</b></p></summary>
<p>Nokogiri (鋸) is an HTML, XML, SAX, and Reader parser. Among
Nokogiri's many features is the ability to search documents via XPath
or CSS3 selectors.</p>
<p>Library home page: <a href="https://rubygems.org/gems/nokogiri-1.10.10.gem">https://rubygems.org/gems/nokogiri-1.10.10.gem</a></p>
<p>
Dependency Hierarchy:
- devise-4.7.1.gem (Root Library)
- railties-5.2.4.3.gem
- actionpack-5.2.4.3.gem
- rails-dom-testing-2.0.3.gem
- :x: **nokogiri-1.10.10.gem** (Vulnerable Library)
<p>Found in base branch: <b>development</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>
Nokogiri is a Rubygem providing HTML, XML, SAX, and Reader parsers with XPath and CSS selector support. In Nokogiri before version 1.11.0.rc4 there is an XXE vulnerability. XML Schemas parsed by Nokogiri::XML::Schema are trusted by default, allowing external resources to be accessed over the network, potentially enabling XXE or SSRF attacks. This behavior is counter to the security policy followed by Nokogiri maintainers, which is to treat all input as untrusted by default whenever possible. This is fixed in Nokogiri version 1.11.0.rc4.
<p>Publish Date: 2020-12-30
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-26247>CVE-2020-26247</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>4.3</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: None
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/sparklemotion/nokogiri/releases/tag/v1.11.0.rc4">https://github.com/sparklemotion/nokogiri/releases/tag/v1.11.0.rc4</a></p>
<p>Release Date: 2020-12-30</p>
<p>Fix Resolution: 1.11.0.rc4</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 nokogiri gem cve medium severity vulnerability vulnerable library nokogiri gem nokogiri 鋸 is an html xml sax and reader parser among nokogiri s many features is the ability to search documents via xpath or selectors library home page a href dependency hierarchy devise gem root library railties gem actionpack gem rails dom testing gem x nokogiri gem vulnerable library found in base branch development vulnerability details nokogiri is a rubygem providing html xml sax and reader parsers with xpath and css selector support in nokogiri before version there is an xxe vulnerability xml schemas parsed by nokogiri xml schema are trusted by default allowing external resources to be accessed over the network potentially enabling xxe or ssrf attacks this behavior is counter to the security policy followed by nokogiri maintainers which is to treat all input as untrusted by default whenever possible this is fixed in nokogiri version publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required low user interaction none scope unchanged impact metrics confidentiality impact low integrity impact none availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution step up your open source security game with whitesource | 0 |
57,223 | 3,081,249,717 | IssuesEvent | 2015-08-22 14:40:52 | pavel-pimenov/flylinkdc-r5xx | https://api.github.com/repos/pavel-pimenov/flylinkdc-r5xx | closed | Меню по правой кнопке на папке - копировать - имя ПАПКИ | bug imported Priority-Medium | _From [bobrikov](https://code.google.com/u/bobrikov/) on January 16, 2013 12:06:16_
Имхо нужно сделать
**Attachment:** [Имя-папки.png](http://code.google.com/p/flylinkdc/issues/detail?id=887)
_Original issue: http://code.google.com/p/flylinkdc/issues/detail?id=887_ | 1.0 | Меню по правой кнопке на папке - копировать - имя ПАПКИ - _From [bobrikov](https://code.google.com/u/bobrikov/) on January 16, 2013 12:06:16_
Имхо нужно сделать
**Attachment:** [Имя-папки.png](http://code.google.com/p/flylinkdc/issues/detail?id=887)
_Original issue: http://code.google.com/p/flylinkdc/issues/detail?id=887_ | priority | меню по правой кнопке на папке копировать имя папки from on january имхо нужно сделать attachment original issue | 1 |
48,629 | 10,266,803,064 | IssuesEvent | 2019-08-22 22:40:07 | volta-cli/volta | https://api.github.com/repos/volta-cli/volta | opened | Investigate build bloat | code quality | A friend told me about this [recent article on Rust build sizes](https://raphlinus.github.io/rust/2019/08/21/rust-bloat.html), and specifically the article links to a useful tool: [cargo-bloat](https://github.com/RazrFalcon/cargo-bloat).
We should use that tool to see if there are places we can reduce the binary size of Volta builds (and possibly the build times as a consequence).
One particular hint I got was that [reqwest](https://github.com/seanmonstar/reqwest) is an especially large library, and there are competitors like [isahc](https://docs.rs/isahc/0.7.0/isahc/) that are considerably smaller. We'd have to investigate to see if it looks like a good tradeoff, though (in terms of feature set, quality, level of maintenance).
And generally let's keep our wits about us—smaller binary size is good, but not if it comes at too high of a cost. It's not the only goal. | 1.0 | Investigate build bloat - A friend told me about this [recent article on Rust build sizes](https://raphlinus.github.io/rust/2019/08/21/rust-bloat.html), and specifically the article links to a useful tool: [cargo-bloat](https://github.com/RazrFalcon/cargo-bloat).
We should use that tool to see if there are places we can reduce the binary size of Volta builds (and possibly the build times as a consequence).
One particular hint I got was that [reqwest](https://github.com/seanmonstar/reqwest) is an especially large library, and there are competitors like [isahc](https://docs.rs/isahc/0.7.0/isahc/) that are considerably smaller. We'd have to investigate to see if it looks like a good tradeoff, though (in terms of feature set, quality, level of maintenance).
And generally let's keep our wits about us—smaller binary size is good, but not if it comes at too high of a cost. It's not the only goal. | non_priority | investigate build bloat a friend told me about this and specifically the article links to a useful tool we should use that tool to see if there are places we can reduce the binary size of volta builds and possibly the build times as a consequence one particular hint i got was that is an especially large library and there are competitors like that are considerably smaller we d have to investigate to see if it looks like a good tradeoff though in terms of feature set quality level of maintenance and generally let s keep our wits about us—smaller binary size is good but not if it comes at too high of a cost it s not the only goal | 0 |
30,542 | 7,227,772,893 | IssuesEvent | 2018-02-11 00:34:35 | raywo/MMM-PublicTransportHafas | https://api.github.com/repos/raywo/MMM-PublicTransportHafas | closed | Fix "method_lines" issue in convenience/query_stations.js | codeclimate | Function `refineProducts` has 30 lines of code (exceeds 25 allowed). Consider refactoring.
https://codeclimate.com/github/raywo/MMM-PublicTransportHafas/convenience/query_stations.js#issue_5a7f455b6b463a000100001a | 1.0 | Fix "method_lines" issue in convenience/query_stations.js - Function `refineProducts` has 30 lines of code (exceeds 25 allowed). Consider refactoring.
https://codeclimate.com/github/raywo/MMM-PublicTransportHafas/convenience/query_stations.js#issue_5a7f455b6b463a000100001a | non_priority | fix method lines issue in convenience query stations js function refineproducts has lines of code exceeds allowed consider refactoring | 0 |
20,691 | 3,620,466,897 | IssuesEvent | 2016-02-08 20:03:45 | SOZOGlobal/Scrumban | https://api.github.com/repos/SOZOGlobal/Scrumban | opened | Create Renew Social Platforms | content design | Pintrest
Twitter
Medium
Instagram
Facebook
Snapchat
Periscope
LinkedIn
YouTube
plus, consistent copy and logo/backgrounds on all | 1.0 | Create Renew Social Platforms - Pintrest
Twitter
Medium
Instagram
Facebook
Snapchat
Periscope
LinkedIn
YouTube
plus, consistent copy and logo/backgrounds on all | non_priority | create renew social platforms pintrest twitter medium instagram facebook snapchat periscope linkedin youtube plus consistent copy and logo backgrounds on all | 0 |
381,175 | 11,274,507,923 | IssuesEvent | 2020-01-14 18:43:22 | sdinteractive/Magento2_SomethingDigital_UpgradeHelper | https://api.github.com/repos/sdinteractive/Magento2_SomethingDigital_UpgradeHelper | closed | Check for changes to $_template | Priority - Low | [9:44 AM] Subbu Swamynathan: PSA: with 2.1.15, magento changed a line in the block to view orders Magento\Sales\Block\Order\View
[9:44 AM] Subbu Swamynathan: from
[9:44 AM] Subbu Swamynathan:
protected $_template = 'order/view.phtml';
[9:44 AM] Subbu Swamynathan: to
[9:45 AM] Subbu Swamynathan:
protected $_template = 'Magento_Sales::order/view.phtml';
[9:45 AM] Subbu Swamynathan: this means, the override in app/code like ...
[9:45 AM] Subbu Swamynathan: does not work | 1.0 | Check for changes to $_template - [9:44 AM] Subbu Swamynathan: PSA: with 2.1.15, magento changed a line in the block to view orders Magento\Sales\Block\Order\View
[9:44 AM] Subbu Swamynathan: from
[9:44 AM] Subbu Swamynathan:
protected $_template = 'order/view.phtml';
[9:44 AM] Subbu Swamynathan: to
[9:45 AM] Subbu Swamynathan:
protected $_template = 'Magento_Sales::order/view.phtml';
[9:45 AM] Subbu Swamynathan: this means, the override in app/code like ...
[9:45 AM] Subbu Swamynathan: does not work | priority | check for changes to template subbu swamynathan psa with magento changed a line in the block to view orders magento sales block order view subbu swamynathan from subbu swamynathan protected template order view phtml subbu swamynathan to subbu swamynathan protected template magento sales order view phtml subbu swamynathan this means the override in app code like subbu swamynathan does not work | 1 |
181,047 | 14,850,203,642 | IssuesEvent | 2021-01-18 03:44:53 | minio/direct-csi | https://api.github.com/repos/minio/direct-csi | closed | Multiple Storage Classes | documentation | Currently I use openebs local pvs for databases. I will be using this for minio but I am wondering is it possible to create multiple strorage classes and if so how would I do that? I would rather just use this than openebs and this so that I make things simpler. | 1.0 | Multiple Storage Classes - Currently I use openebs local pvs for databases. I will be using this for minio but I am wondering is it possible to create multiple strorage classes and if so how would I do that? I would rather just use this than openebs and this so that I make things simpler. | non_priority | multiple storage classes currently i use openebs local pvs for databases i will be using this for minio but i am wondering is it possible to create multiple strorage classes and if so how would i do that i would rather just use this than openebs and this so that i make things simpler | 0 |
9,301 | 3,032,826,317 | IssuesEvent | 2015-08-05 11:25:03 | WebTales/rubedo | https://api.github.com/repos/WebTales/rubedo | closed | Add SEO on contents | enhancement high priority To test | Ajouter les metas(Titre+ description) aux contenus ou utiliser méta existants (titre+résumé) pour le référencement des contenus proposés sous forme de requêtes. | 1.0 | Add SEO on contents - Ajouter les metas(Titre+ description) aux contenus ou utiliser méta existants (titre+résumé) pour le référencement des contenus proposés sous forme de requêtes. | non_priority | add seo on contents ajouter les metas titre description aux contenus ou utiliser méta existants titre résumé pour le référencement des contenus proposés sous forme de requêtes | 0 |
373,442 | 26,054,785,660 | IssuesEvent | 2022-12-22 23:22:33 | OliverOverend/gym-simplifiedtetris | https://api.github.com/repos/OliverOverend/gym-simplifiedtetris | opened | DOC: Contributing docs are outdated | Documentation Enhancement | ### Please a URL to the documentation:
https://github.com/OliverOverend/gym-simplifiedtetris/blob/master/CONTRIBUTING.md
### Please provide a description of the issue:
The contributing docs are outdated and clunky.
### Please explain the suggested fix:
Streamline the contributing docs by rejuvenating them with up-to-date information. | 1.0 | DOC: Contributing docs are outdated - ### Please a URL to the documentation:
https://github.com/OliverOverend/gym-simplifiedtetris/blob/master/CONTRIBUTING.md
### Please provide a description of the issue:
The contributing docs are outdated and clunky.
### Please explain the suggested fix:
Streamline the contributing docs by rejuvenating them with up-to-date information. | non_priority | doc contributing docs are outdated please a url to the documentation please provide a description of the issue the contributing docs are outdated and clunky please explain the suggested fix streamline the contributing docs by rejuvenating them with up to date information | 0 |
71,001 | 15,168,124,129 | IssuesEvent | 2021-02-12 18:53:25 | jgeraigery/seaside-gradle-plugins | https://api.github.com/repos/jgeraigery/seaside-gradle-plugins | opened | CVE-2018-1199 (Medium) detected in spring-core-3.1.3.RELEASE.jar | security vulnerability | ## CVE-2018-1199 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>spring-core-3.1.3.RELEASE.jar</b></p></summary>
<p>Spring Framework Parent</p>
<p>Path to dependency file: seaside-gradle-plugins/com.ngc.seaside.gradle.plugins.distribution/build.gradle</p>
<p>Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.springframework/spring-core/3.1.3.RELEASE/abaf69158b1f9639adfbb24b94bba190a1892f2f/spring-core-3.1.3.RELEASE.jar</p>
<p>
Dependency Hierarchy:
- license-gradle-plugin-0.14.0.jar (Root Library)
- license-maven-plugin-3.0.jar
- :x: **spring-core-3.1.3.RELEASE.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/jgeraigery/seaside-gradle-plugins/commit/9eb1a570ebceb5372e7b739fefd25c83d3760edc">9eb1a570ebceb5372e7b739fefd25c83d3760edc</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>
Spring Security (Spring Security 4.1.x before 4.1.5, 4.2.x before 4.2.4, and 5.0.x before 5.0.1; and Spring Framework 4.3.x before 4.3.14 and 5.0.x before 5.0.3) does not consider URL path parameters when processing security constraints. By adding a URL path parameter with special encodings, an attacker may be able to bypass a security constraint. The root cause of this issue is a lack of clarity regarding the handling of path parameters in the Servlet Specification. Some Servlet containers include path parameters in the value returned for getPathInfo() and some do not. Spring Security uses the value returned by getPathInfo() as part of the process of mapping requests to security constraints. In this particular attack, different character encodings used in path parameters allows secured Spring MVC static resource URLs to be bypassed.
<p>Publish Date: 2018-03-16
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-1199>CVE-2018-1199</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: Low
- Integrity Impact: None
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://nvd.nist.gov/vuln/detail/CVE-2018-1199">https://nvd.nist.gov/vuln/detail/CVE-2018-1199</a></p>
<p>Release Date: 2018-03-16</p>
<p>Fix Resolution: org.springframework.security:spring-security-web:4.1.5.RELEASE,4.2.4.RELEASE,5.0.1.RELEASE,5.0.3.RELEASE,org.springframework.security:spring-security-config:4.1.5.RELEASE,4.2.4.RELEASE,5.0.1.RELEASE,5.0.3.RELEASE,org.springframework:spring-core:4.1.5.RELEASE,4.2.4.RELEASE,5.0.1.RELEASE,5.0.3.RELEASE,4.3.14.RELEASE</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"Java","groupId":"org.springframework","packageName":"spring-core","packageVersion":"3.1.3.RELEASE","packageFilePaths":["/com.ngc.seaside.gradle.plugins.distribution/build.gradle"],"isTransitiveDependency":true,"dependencyTree":"gradle.plugin.nl.javadude.gradle.plugins:license-gradle-plugin:0.14.0;com.mycila:license-maven-plugin:3.0;org.springframework:spring-core:3.1.3.RELEASE","isMinimumFixVersionAvailable":true,"minimumFixVersion":"org.springframework.security:spring-security-web:4.1.5.RELEASE,4.2.4.RELEASE,5.0.1.RELEASE,5.0.3.RELEASE,org.springframework.security:spring-security-config:4.1.5.RELEASE,4.2.4.RELEASE,5.0.1.RELEASE,5.0.3.RELEASE,org.springframework:spring-core:4.1.5.RELEASE,4.2.4.RELEASE,5.0.1.RELEASE,5.0.3.RELEASE,4.3.14.RELEASE"}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2018-1199","vulnerabilityDetails":"Spring Security (Spring Security 4.1.x before 4.1.5, 4.2.x before 4.2.4, and 5.0.x before 5.0.1; and Spring Framework 4.3.x before 4.3.14 and 5.0.x before 5.0.3) does not consider URL path parameters when processing security constraints. By adding a URL path parameter with special encodings, an attacker may be able to bypass a security constraint. The root cause of this issue is a lack of clarity regarding the handling of path parameters in the Servlet Specification. Some Servlet containers include path parameters in the value returned for getPathInfo() and some do not. Spring Security uses the value returned by getPathInfo() as part of the process of mapping requests to security constraints. In this particular attack, different character encodings used in path parameters allows secured Spring MVC static resource URLs to be bypassed.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-1199","cvss3Severity":"medium","cvss3Score":"5.3","cvss3Metrics":{"A":"None","AC":"Low","PR":"None","S":"Unchanged","C":"Low","UI":"None","AV":"Network","I":"None"},"extraData":{}}</REMEDIATE> --> | True | CVE-2018-1199 (Medium) detected in spring-core-3.1.3.RELEASE.jar - ## CVE-2018-1199 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>spring-core-3.1.3.RELEASE.jar</b></p></summary>
<p>Spring Framework Parent</p>
<p>Path to dependency file: seaside-gradle-plugins/com.ngc.seaside.gradle.plugins.distribution/build.gradle</p>
<p>Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/org.springframework/spring-core/3.1.3.RELEASE/abaf69158b1f9639adfbb24b94bba190a1892f2f/spring-core-3.1.3.RELEASE.jar</p>
<p>
Dependency Hierarchy:
- license-gradle-plugin-0.14.0.jar (Root Library)
- license-maven-plugin-3.0.jar
- :x: **spring-core-3.1.3.RELEASE.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/jgeraigery/seaside-gradle-plugins/commit/9eb1a570ebceb5372e7b739fefd25c83d3760edc">9eb1a570ebceb5372e7b739fefd25c83d3760edc</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>
Spring Security (Spring Security 4.1.x before 4.1.5, 4.2.x before 4.2.4, and 5.0.x before 5.0.1; and Spring Framework 4.3.x before 4.3.14 and 5.0.x before 5.0.3) does not consider URL path parameters when processing security constraints. By adding a URL path parameter with special encodings, an attacker may be able to bypass a security constraint. The root cause of this issue is a lack of clarity regarding the handling of path parameters in the Servlet Specification. Some Servlet containers include path parameters in the value returned for getPathInfo() and some do not. Spring Security uses the value returned by getPathInfo() as part of the process of mapping requests to security constraints. In this particular attack, different character encodings used in path parameters allows secured Spring MVC static resource URLs to be bypassed.
<p>Publish Date: 2018-03-16
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-1199>CVE-2018-1199</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: Low
- Integrity Impact: None
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://nvd.nist.gov/vuln/detail/CVE-2018-1199">https://nvd.nist.gov/vuln/detail/CVE-2018-1199</a></p>
<p>Release Date: 2018-03-16</p>
<p>Fix Resolution: org.springframework.security:spring-security-web:4.1.5.RELEASE,4.2.4.RELEASE,5.0.1.RELEASE,5.0.3.RELEASE,org.springframework.security:spring-security-config:4.1.5.RELEASE,4.2.4.RELEASE,5.0.1.RELEASE,5.0.3.RELEASE,org.springframework:spring-core:4.1.5.RELEASE,4.2.4.RELEASE,5.0.1.RELEASE,5.0.3.RELEASE,4.3.14.RELEASE</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"Java","groupId":"org.springframework","packageName":"spring-core","packageVersion":"3.1.3.RELEASE","packageFilePaths":["/com.ngc.seaside.gradle.plugins.distribution/build.gradle"],"isTransitiveDependency":true,"dependencyTree":"gradle.plugin.nl.javadude.gradle.plugins:license-gradle-plugin:0.14.0;com.mycila:license-maven-plugin:3.0;org.springframework:spring-core:3.1.3.RELEASE","isMinimumFixVersionAvailable":true,"minimumFixVersion":"org.springframework.security:spring-security-web:4.1.5.RELEASE,4.2.4.RELEASE,5.0.1.RELEASE,5.0.3.RELEASE,org.springframework.security:spring-security-config:4.1.5.RELEASE,4.2.4.RELEASE,5.0.1.RELEASE,5.0.3.RELEASE,org.springframework:spring-core:4.1.5.RELEASE,4.2.4.RELEASE,5.0.1.RELEASE,5.0.3.RELEASE,4.3.14.RELEASE"}],"baseBranches":["master"],"vulnerabilityIdentifier":"CVE-2018-1199","vulnerabilityDetails":"Spring Security (Spring Security 4.1.x before 4.1.5, 4.2.x before 4.2.4, and 5.0.x before 5.0.1; and Spring Framework 4.3.x before 4.3.14 and 5.0.x before 5.0.3) does not consider URL path parameters when processing security constraints. By adding a URL path parameter with special encodings, an attacker may be able to bypass a security constraint. The root cause of this issue is a lack of clarity regarding the handling of path parameters in the Servlet Specification. Some Servlet containers include path parameters in the value returned for getPathInfo() and some do not. Spring Security uses the value returned by getPathInfo() as part of the process of mapping requests to security constraints. In this particular attack, different character encodings used in path parameters allows secured Spring MVC static resource URLs to be bypassed.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2018-1199","cvss3Severity":"medium","cvss3Score":"5.3","cvss3Metrics":{"A":"None","AC":"Low","PR":"None","S":"Unchanged","C":"Low","UI":"None","AV":"Network","I":"None"},"extraData":{}}</REMEDIATE> --> | non_priority | cve medium detected in spring core release jar cve medium severity vulnerability vulnerable library spring core release jar spring framework parent path to dependency file seaside gradle plugins com ngc seaside gradle plugins distribution build gradle path to vulnerable library home wss scanner gradle caches modules files org springframework spring core release spring core release jar dependency hierarchy license gradle plugin jar root library license maven plugin jar x spring core release jar vulnerable library found in head commit a href found in base branch master vulnerability details spring security spring security x before x before and x before and spring framework x before and x before does not consider url path parameters when processing security constraints by adding a url path parameter with special encodings an attacker may be able to bypass a security constraint the root cause of this issue is a lack of clarity regarding the handling of path parameters in the servlet specification some servlet containers include path parameters in the value returned for getpathinfo and some do not spring security uses the value returned by getpathinfo as part of the process of mapping requests to security constraints in this particular attack different character encodings used in path parameters allows secured spring mvc static resource urls to be bypassed publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact low integrity impact none availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution org springframework security spring security web release release release release org springframework security spring security config release release release release org springframework spring core release release release release release isopenpronvulnerability true ispackagebased true isdefaultbranch true packages istransitivedependency true dependencytree gradle plugin nl javadude gradle plugins license gradle plugin com mycila license maven plugin org springframework spring core release isminimumfixversionavailable true minimumfixversion org springframework security spring security web release release release release org springframework security spring security config release release release release org springframework spring core release release release release release basebranches vulnerabilityidentifier cve vulnerabilitydetails spring security spring security x before x before and x before and spring framework x before and x before does not consider url path parameters when processing security constraints by adding a url path parameter with special encodings an attacker may be able to bypass a security constraint the root cause of this issue is a lack of clarity regarding the handling of path parameters in the servlet specification some servlet containers include path parameters in the value returned for getpathinfo and some do not spring security uses the value returned by getpathinfo as part of the process of mapping requests to security constraints in this particular attack different character encodings used in path parameters allows secured spring mvc static resource urls to be bypassed vulnerabilityurl | 0 |
129,918 | 5,106,362,713 | IssuesEvent | 2017-01-05 11:09:06 | odalic/sti | https://api.github.com/repos/odalic/sti | closed | Implement property (aka relation) proposal | bug core extension feature java knowledge bases priority: Urgent sparql | Hi, I have entirely overlooked this, but this feature is still not implemented (the API is ready) for the properties. | 1.0 | Implement property (aka relation) proposal - Hi, I have entirely overlooked this, but this feature is still not implemented (the API is ready) for the properties. | priority | implement property aka relation proposal hi i have entirely overlooked this but this feature is still not implemented the api is ready for the properties | 1 |
187,969 | 15,112,693,574 | IssuesEvent | 2021-02-08 22:16:35 | josecls/agripluvi-api | https://api.github.com/repos/josecls/agripluvi-api | closed | Feature: Adiciona documentação de como rodar o projeto | Feature Low Priority documentation good first issue | ### Descrição
No projeto atual não temos um readme especificando o passo a passo para rodar o projeto localmente, isso iria auxiliar as pessoas que nunca trabalharam com Java.
### Ação
Criar um arquivo readme.md com informações úteis sobre o projeto.
### Observações
- [**Guia de como criar um readme.md bonitão**](https://medium.com/@raullesteves/github-como-fazer-um-readme-md-bonit%C3%A3o-c85c8f154f8) | 1.0 | Feature: Adiciona documentação de como rodar o projeto - ### Descrição
No projeto atual não temos um readme especificando o passo a passo para rodar o projeto localmente, isso iria auxiliar as pessoas que nunca trabalharam com Java.
### Ação
Criar um arquivo readme.md com informações úteis sobre o projeto.
### Observações
- [**Guia de como criar um readme.md bonitão**](https://medium.com/@raullesteves/github-como-fazer-um-readme-md-bonit%C3%A3o-c85c8f154f8) | non_priority | feature adiciona documentação de como rodar o projeto descrição no projeto atual não temos um readme especificando o passo a passo para rodar o projeto localmente isso iria auxiliar as pessoas que nunca trabalharam com java ação criar um arquivo readme md com informações úteis sobre o projeto observações | 0 |
154,056 | 19,710,772,518 | IssuesEvent | 2022-01-13 04:53:55 | ChoeMinji/react-17.0.2 | https://api.github.com/repos/ChoeMinji/react-17.0.2 | opened | WS-2018-0628 (Medium) detected in marked-0.3.6.tgz | security vulnerability | ## WS-2018-0628 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>marked-0.3.6.tgz</b></p></summary>
<p>A markdown parser built for speed</p>
<p>Library home page: <a href="https://registry.npmjs.org/marked/-/marked-0.3.6.tgz">https://registry.npmjs.org/marked/-/marked-0.3.6.tgz</a></p>
<p>Path to dependency file: /fixtures/fiber-debugger/package.json</p>
<p>Path to vulnerable library: /fixtures/fiber-debugger/node_modules/marked/package.json</p>
<p>
Dependency Hierarchy:
- react-scripts-0.9.5.tgz (Root Library)
- jest-18.1.0.tgz
- jest-cli-18.1.0.tgz
- node-notifier-4.6.1.tgz
- cli-usage-0.1.4.tgz
- :x: **marked-0.3.6.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/ChoeMinji/react-17.0.2/commit/4669645897ed4ebcd4ee037f4dabb509ed4754c7">4669645897ed4ebcd4ee037f4dabb509ed4754c7</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>
marked before 0.4.0 is vulnerable to Regular Expression Denial of Service (REDoS) through heading in marked.js.
<p>Publish Date: 2018-04-16
<p>URL: <a href=https://github.com/markedjs/marked/commit/09afabf69c6d0c919c03443f47bdfe476566105d>WS-2018-0628</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://github.com/markedjs/marked/releases/tag/0.4.0">https://github.com/markedjs/marked/releases/tag/0.4.0</a></p>
<p>Release Date: 2018-04-16</p>
<p>Fix Resolution: marked - 0.4.0</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | WS-2018-0628 (Medium) detected in marked-0.3.6.tgz - ## WS-2018-0628 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>marked-0.3.6.tgz</b></p></summary>
<p>A markdown parser built for speed</p>
<p>Library home page: <a href="https://registry.npmjs.org/marked/-/marked-0.3.6.tgz">https://registry.npmjs.org/marked/-/marked-0.3.6.tgz</a></p>
<p>Path to dependency file: /fixtures/fiber-debugger/package.json</p>
<p>Path to vulnerable library: /fixtures/fiber-debugger/node_modules/marked/package.json</p>
<p>
Dependency Hierarchy:
- react-scripts-0.9.5.tgz (Root Library)
- jest-18.1.0.tgz
- jest-cli-18.1.0.tgz
- node-notifier-4.6.1.tgz
- cli-usage-0.1.4.tgz
- :x: **marked-0.3.6.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/ChoeMinji/react-17.0.2/commit/4669645897ed4ebcd4ee037f4dabb509ed4754c7">4669645897ed4ebcd4ee037f4dabb509ed4754c7</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>
marked before 0.4.0 is vulnerable to Regular Expression Denial of Service (REDoS) through heading in marked.js.
<p>Publish Date: 2018-04-16
<p>URL: <a href=https://github.com/markedjs/marked/commit/09afabf69c6d0c919c03443f47bdfe476566105d>WS-2018-0628</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://github.com/markedjs/marked/releases/tag/0.4.0">https://github.com/markedjs/marked/releases/tag/0.4.0</a></p>
<p>Release Date: 2018-04-16</p>
<p>Fix Resolution: marked - 0.4.0</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_priority | ws medium detected in marked tgz ws medium severity vulnerability vulnerable library marked tgz a markdown parser built for speed library home page a href path to dependency file fixtures fiber debugger package json path to vulnerable library fixtures fiber debugger node modules marked package json dependency hierarchy react scripts tgz root library jest tgz jest cli tgz node notifier tgz cli usage tgz x marked tgz vulnerable library found in head commit a href found in base branch master vulnerability details marked before is vulnerable to regular expression denial of service redos through heading in marked js publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact none integrity impact none availability impact low for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution marked step up your open source security game with whitesource | 0 |
6,107 | 8,966,962,329 | IssuesEvent | 2019-01-29 01:09:38 | knative/serving | https://api.github.com/repos/knative/serving | closed | Simplify the traffic.go | area/API kind/cleanup kind/process | <!--
Pro-tip: You can leave this block commented, and it still works!
Select the appropriate areas for your issue:
/area API
Classify what kind of issue this is:
/kind cleanup
/kind process
-->
## Proposal
Currently the route/traffic/traffic.go is quite complex, but it doesn't have to be so, since we only permit a single revision for a target, so the whole flattening process can be rewritten with fewer lines.
- simplify the data structures
- simplify the algorithms
- remove the unnecessary code
- fix the linter errors with stutter named structures
| 1.0 | Simplify the traffic.go - <!--
Pro-tip: You can leave this block commented, and it still works!
Select the appropriate areas for your issue:
/area API
Classify what kind of issue this is:
/kind cleanup
/kind process
-->
## Proposal
Currently the route/traffic/traffic.go is quite complex, but it doesn't have to be so, since we only permit a single revision for a target, so the whole flattening process can be rewritten with fewer lines.
- simplify the data structures
- simplify the algorithms
- remove the unnecessary code
- fix the linter errors with stutter named structures
| non_priority | simplify the traffic go pro tip you can leave this block commented and it still works select the appropriate areas for your issue area api classify what kind of issue this is kind cleanup kind process proposal currently the route traffic traffic go is quite complex but it doesn t have to be so since we only permit a single revision for a target so the whole flattening process can be rewritten with fewer lines simplify the data structures simplify the algorithms remove the unnecessary code fix the linter errors with stutter named structures | 0 |
275,917 | 8,582,167,678 | IssuesEvent | 2018-11-13 16:20:53 | CuBoulder/express | https://api.github.com/repos/CuBoulder/express | closed | User Invite email check should not be case sensitive | priority:Critical type:Bug | the CU LDAP returns email addresses with various different cases, such as name@colorado.EDU - if a user is invited at name@colorado.edu, the email check fails.
https://github.com/CuBoulder/express/blob/dev/modules/contrib/user_external_invite/user_external_invite.module#L581 | 1.0 | User Invite email check should not be case sensitive - the CU LDAP returns email addresses with various different cases, such as name@colorado.EDU - if a user is invited at name@colorado.edu, the email check fails.
https://github.com/CuBoulder/express/blob/dev/modules/contrib/user_external_invite/user_external_invite.module#L581 | priority | user invite email check should not be case sensitive the cu ldap returns email addresses with various different cases such as name colorado edu if a user is invited at name colorado edu the email check fails | 1 |
510,540 | 14,792,557,414 | IssuesEvent | 2021-01-12 14:53:31 | myConsciousness/java-generator-commons | https://api.github.com/repos/myConsciousness/java-generator-commons | closed | AnnotationParameterの引数生成処理を改善 | Priority: high Type: improvement | # Improvement
## 1. Improvement details
`AnnotationParameter` クラスにおける引数生成処理を改善する。
## 2. Why it is necessary
より柔軟な値設定を可能にするため。
## 3. How to improve
現状 `createParameter` メソッドが呼び出された場合に文字列であればダブルクオーテーションを付けて返却しているが、
ダブルクオーテーションを付与するかどうかを実装に委ねるようにする。
## 4. References
| 1.0 | AnnotationParameterの引数生成処理を改善 - # Improvement
## 1. Improvement details
`AnnotationParameter` クラスにおける引数生成処理を改善する。
## 2. Why it is necessary
より柔軟な値設定を可能にするため。
## 3. How to improve
現状 `createParameter` メソッドが呼び出された場合に文字列であればダブルクオーテーションを付けて返却しているが、
ダブルクオーテーションを付与するかどうかを実装に委ねるようにする。
## 4. References
| priority | annotationparameterの引数生成処理を改善 improvement improvement details annotationparameter クラスにおける引数生成処理を改善する。 why it is necessary より柔軟な値設定を可能にするため。 how to improve 現状 createparameter メソッドが呼び出された場合に文字列であればダブルクオーテーションを付けて返却しているが、 ダブルクオーテーションを付与するかどうかを実装に委ねるようにする。 references | 1 |
213,500 | 16,523,743,014 | IssuesEvent | 2021-05-26 17:17:59 | openservicemesh/osm | https://api.github.com/repos/openservicemesh/osm | opened | test: pkg/certificate/providers/vault/certificate_manager.go - RotateCertificate() | area/tests size/XS | In `pkg/certificate/providers/vault/certificate_manager.go`, the unit test coverage can be improved for the RotateCertificate() func. See highlighted lines below.
Scenarios not covered:
* Entire function
ref #1489 | 1.0 | test: pkg/certificate/providers/vault/certificate_manager.go - RotateCertificate() - In `pkg/certificate/providers/vault/certificate_manager.go`, the unit test coverage can be improved for the RotateCertificate() func. See highlighted lines below.
Scenarios not covered:
* Entire function
ref #1489 | non_priority | test pkg certificate providers vault certificate manager go rotatecertificate in pkg certificate providers vault certificate manager go the unit test coverage can be improved for the rotatecertificate func see highlighted lines below scenarios not covered entire function ref | 0 |
703,337 | 24,154,377,493 | IssuesEvent | 2022-09-22 06:09:18 | themotte/rDrama | https://api.github.com/repos/themotte/rDrama | closed | Contact Admins (modmail) prompts for email for no good reason. | P2 priority | The /contact form has a field for email, which is solely used for display in the generated modmail notification. I _believe_ this is a holdover from when /contact was not `@auth_required` (perhaps all the way back on Ruqqus) and was usable for logged out users. However, it would take substantial refactoring to make this functionality useful—for one, the generated notification uses `author_id=v.id` and would instead need to generate a notification from a system account and then provide some mechanism to shunt replies over email, and also to receive replies therefrom. For another, logged out users bothering the admins might not be desirable.
In the upstream, we removed this field entirely for UX reasons, since users who wanted to modmail didn't understand why they had to put an email in. Relevant code sections:
https://github.com/themotte/rDrama/blob/4cfd1d5a5b8bc212c96625b5d3681ad3a79009b3/files/routes/static.py#L288-L295
https://github.com/themotte/rDrama/blob/4cfd1d5a5b8bc212c96625b5d3681ad3a79009b3/files/templates/contact.html#L26-L31 | 1.0 | Contact Admins (modmail) prompts for email for no good reason. - The /contact form has a field for email, which is solely used for display in the generated modmail notification. I _believe_ this is a holdover from when /contact was not `@auth_required` (perhaps all the way back on Ruqqus) and was usable for logged out users. However, it would take substantial refactoring to make this functionality useful—for one, the generated notification uses `author_id=v.id` and would instead need to generate a notification from a system account and then provide some mechanism to shunt replies over email, and also to receive replies therefrom. For another, logged out users bothering the admins might not be desirable.
In the upstream, we removed this field entirely for UX reasons, since users who wanted to modmail didn't understand why they had to put an email in. Relevant code sections:
https://github.com/themotte/rDrama/blob/4cfd1d5a5b8bc212c96625b5d3681ad3a79009b3/files/routes/static.py#L288-L295
https://github.com/themotte/rDrama/blob/4cfd1d5a5b8bc212c96625b5d3681ad3a79009b3/files/templates/contact.html#L26-L31 | priority | contact admins modmail prompts for email for no good reason the contact form has a field for email which is solely used for display in the generated modmail notification i believe this is a holdover from when contact was not auth required perhaps all the way back on ruqqus and was usable for logged out users however it would take substantial refactoring to make this functionality useful—for one the generated notification uses author id v id and would instead need to generate a notification from a system account and then provide some mechanism to shunt replies over email and also to receive replies therefrom for another logged out users bothering the admins might not be desirable in the upstream we removed this field entirely for ux reasons since users who wanted to modmail didn t understand why they had to put an email in relevant code sections | 1 |
550,147 | 16,105,703,830 | IssuesEvent | 2021-04-27 14:42:43 | sopra-fs21-group-08/sopra-fs21-group08-server | https://api.github.com/repos/sopra-fs21-group-08/sopra-fs21-group08-server | reopened | Create the Ticket interface and the individual tickets | medium priority task | time estimate: 5h
This task is part of User stories: #17 #9 #8 | 1.0 | Create the Ticket interface and the individual tickets - time estimate: 5h
This task is part of User stories: #17 #9 #8 | priority | create the ticket interface and the individual tickets time estimate this task is part of user stories | 1 |
592,368 | 17,876,838,284 | IssuesEvent | 2021-09-07 05:48:16 | annagabriel-hash/stock-transfer-app | https://api.github.com/repos/annagabriel-hash/stock-transfer-app | closed | Given that I'm a broker, when I go to the stocks page, and enter the amount of shares to be sold, the shares can be bought by the buyers. | App: Backend Priority: Medium State: In Progress Type: Feature | ### Tasks
- [x] Specify offer model
- [x] Offer table accepts stock id, user id, price, shares, status (open, closed, cancelled), order type (limit order and market order), action (buy or sell)
- [x] Specify trade model
- [x] Trade table accepts stock id, buyer_id, seller_id, price, shares, offer_ids
- [x] Given that I'm a broker, when I go to the stocks page, select market order, enter the amount of shares to be bought. The shares are sold at the current market price and my balance decreases based on the amount sold. | 1.0 | Given that I'm a broker, when I go to the stocks page, and enter the amount of shares to be sold, the shares can be bought by the buyers. - ### Tasks
- [x] Specify offer model
- [x] Offer table accepts stock id, user id, price, shares, status (open, closed, cancelled), order type (limit order and market order), action (buy or sell)
- [x] Specify trade model
- [x] Trade table accepts stock id, buyer_id, seller_id, price, shares, offer_ids
- [x] Given that I'm a broker, when I go to the stocks page, select market order, enter the amount of shares to be bought. The shares are sold at the current market price and my balance decreases based on the amount sold. | priority | given that i m a broker when i go to the stocks page and enter the amount of shares to be sold the shares can be bought by the buyers tasks specify offer model offer table accepts stock id user id price shares status open closed cancelled order type limit order and market order action buy or sell specify trade model trade table accepts stock id buyer id seller id price shares offer ids given that i m a broker when i go to the stocks page select market order enter the amount of shares to be bought the shares are sold at the current market price and my balance decreases based on the amount sold | 1 |
96,866 | 3,974,246,196 | IssuesEvent | 2016-05-04 21:27:27 | blackwatchint/modpack | https://api.github.com/repos/blackwatchint/modpack | closed | Consistently name all factions within the Armory | Low Priority Template | As many new factions may be added to the Armory in future, all existing factions need to be named using a consistent format that conveys the camo and era of the loadout. Furthermore, the factions should be better grouped and sorted. | 1.0 | Consistently name all factions within the Armory - As many new factions may be added to the Armory in future, all existing factions need to be named using a consistent format that conveys the camo and era of the loadout. Furthermore, the factions should be better grouped and sorted. | priority | consistently name all factions within the armory as many new factions may be added to the armory in future all existing factions need to be named using a consistent format that conveys the camo and era of the loadout furthermore the factions should be better grouped and sorted | 1 |
398,778 | 11,742,333,455 | IssuesEvent | 2020-03-12 00:24:18 | thaliawww/concrexit | https://api.github.com/repos/thaliawww/concrexit | closed | Improve documentation | priority: maybe someday technical change | In GitLab by @thomwiggers on Feb 13, 2018, 10:08
### One-sentence description and why
Improve documentation so that we:
* Have something to show on [docs pages](https://thalia.nu/docs/).
* Have (tested) examples for relevant functions (doctests)
* Provide better reference to our newbies and "future generations". | 1.0 | Improve documentation - In GitLab by @thomwiggers on Feb 13, 2018, 10:08
### One-sentence description and why
Improve documentation so that we:
* Have something to show on [docs pages](https://thalia.nu/docs/).
* Have (tested) examples for relevant functions (doctests)
* Provide better reference to our newbies and "future generations". | priority | improve documentation in gitlab by thomwiggers on feb one sentence description and why improve documentation so that we have something to show on have tested examples for relevant functions doctests provide better reference to our newbies and future generations | 1 |
2,964 | 5,144,855,718 | IssuesEvent | 2017-01-12 19:51:59 | TechnionYP5777/SmartCity-Accessibility | https://api.github.com/repos/TechnionYP5777/SmartCity-Accessibility | closed | wierd default behaviour of jxmaps | GUI Map services | when not being able to decipher the building type given to it, JxMaps (consistently!) returns the same building with nothing recognizable alike. wheter the type is hotel, asdasdasasd or floopyfloopydu
the same buildings are returned, find out what is the default behaviour | 1.0 | wierd default behaviour of jxmaps - when not being able to decipher the building type given to it, JxMaps (consistently!) returns the same building with nothing recognizable alike. wheter the type is hotel, asdasdasasd or floopyfloopydu
the same buildings are returned, find out what is the default behaviour | non_priority | wierd default behaviour of jxmaps when not being able to decipher the building type given to it jxmaps consistently returns the same building with nothing recognizable alike wheter the type is hotel asdasdasasd or floopyfloopydu the same buildings are returned find out what is the default behaviour | 0 |
408,650 | 11,950,305,705 | IssuesEvent | 2020-04-03 14:59:57 | JensenJ/SpaceSurvival | https://api.github.com/repos/JensenJ/SpaceSurvival | closed | [BUG] Ship Spawn Syncing Transform | bug medium-priority sync-issue | **Describe the bug**
If a player joins after a ship or another object has been spawned, they do not have the ship in the correct position in their world when they join the host player. This is because the parent of the ship object has not been set as the ship spawning object. This bug does not occur if the player is in the world when the ship is spawned however.
**To Reproduce**
Steps to reproduce the behaviour:
1. Host a game
2. Get host to spawn ship
3. Join host's game as client
4. Observe the host's ship rotated strangely and in a different position to the host's version.
**Expected behaviour**
When the player joins the game, the ship position, rotation and parentage in the hierarchy should be synced to prevent this issue from occurring. As a result of this, the behaviour should be corrected.
**Screenshots**
Host Ship:
<img width="572" alt="host" src="https://user-images.githubusercontent.com/13812018/78306143-8f3e5000-753a-11ea-9e47-e69bc1ab1d8c.png">
Client Ship:
<img width="725" alt="client" src="https://user-images.githubusercontent.com/13812018/78306165-9d8c6c00-753a-11ea-916b-b6fe5f71d8f0.png">
| 1.0 | [BUG] Ship Spawn Syncing Transform - **Describe the bug**
If a player joins after a ship or another object has been spawned, they do not have the ship in the correct position in their world when they join the host player. This is because the parent of the ship object has not been set as the ship spawning object. This bug does not occur if the player is in the world when the ship is spawned however.
**To Reproduce**
Steps to reproduce the behaviour:
1. Host a game
2. Get host to spawn ship
3. Join host's game as client
4. Observe the host's ship rotated strangely and in a different position to the host's version.
**Expected behaviour**
When the player joins the game, the ship position, rotation and parentage in the hierarchy should be synced to prevent this issue from occurring. As a result of this, the behaviour should be corrected.
**Screenshots**
Host Ship:
<img width="572" alt="host" src="https://user-images.githubusercontent.com/13812018/78306143-8f3e5000-753a-11ea-9e47-e69bc1ab1d8c.png">
Client Ship:
<img width="725" alt="client" src="https://user-images.githubusercontent.com/13812018/78306165-9d8c6c00-753a-11ea-916b-b6fe5f71d8f0.png">
| priority | ship spawn syncing transform describe the bug if a player joins after a ship or another object has been spawned they do not have the ship in the correct position in their world when they join the host player this is because the parent of the ship object has not been set as the ship spawning object this bug does not occur if the player is in the world when the ship is spawned however to reproduce steps to reproduce the behaviour host a game get host to spawn ship join host s game as client observe the host s ship rotated strangely and in a different position to the host s version expected behaviour when the player joins the game the ship position rotation and parentage in the hierarchy should be synced to prevent this issue from occurring as a result of this the behaviour should be corrected screenshots host ship img width alt host src client ship img width alt client src | 1 |
670,631 | 22,696,800,044 | IssuesEvent | 2022-07-05 07:00:15 | wso2/api-manager | https://api.github.com/repos/wso2/api-manager | opened | Redis throttling synchronization doesn't work | Type/Bug Priority/Normal | ### Description
At attempt to use redis for throttling sync will fail and spam logs with error. (Unable to sync throttle counter)
There are 2 reasons for this:
1. RedisDistributedCountManager is initialized before the redis pool
See https://github.com/wso2/carbon-apimgt/blob/master/components/apimgt/org.wso2.carbon.apimgt.gateway/src/main/java/org/wso2/carbon/apimgt/gateway/internal/APIHandlerServiceComponent.java#L130 and https://github.com/wso2/carbon-apimgt/blob/master/components/apimgt/org.wso2.carbon.apimgt.gateway/src/main/java/org/wso2/carbon/apimgt/gateway/internal/APIHandlerServiceComponent.java#L134. This results in null JedisPool instance, and NPEs along the way.
2. The RedisBaseDistributedCountManager implementation itself is incorrect
The redis response itself will always be not null, the value returned by calling get() will.
This causes errors in asyncGetAndAddCounter and asyncGetAndAlterCounter methods
See https://github.com/wso2/carbon-apimgt/blob/master/components/apimgt/org.wso2.carbon.apimgt.gateway/src/main/java/org/wso2/carbon/apimgt/gateway/RedisBaseDistributedCountManager.java#L148 and https://github.com/wso2/carbon-apimgt/blob/master/components/apimgt/org.wso2.carbon.apimgt.gateway/src/main/java/org/wso2/carbon/apimgt/gateway/RedisBaseDistributedCountManager.java#L180
Either the value itself should be checked for null, or you should just get rid of using multi and just use the result of redis incrBy subtracted by the value for add, and result of getset for alter.
### Steps to Reproduce
Run redis 7.0
Run APIM 4.1.0
Publish api, subscribe to it using limited quota subscription, use it,
### Affected Component
APIM
### Version
4.1.0
### Environment Details (with versions)
_No response_
### Relevant Log Output
_No response_
### Related Issues
_No response_
### Suggested Labels
_No response_ | 1.0 | Redis throttling synchronization doesn't work - ### Description
At attempt to use redis for throttling sync will fail and spam logs with error. (Unable to sync throttle counter)
There are 2 reasons for this:
1. RedisDistributedCountManager is initialized before the redis pool
See https://github.com/wso2/carbon-apimgt/blob/master/components/apimgt/org.wso2.carbon.apimgt.gateway/src/main/java/org/wso2/carbon/apimgt/gateway/internal/APIHandlerServiceComponent.java#L130 and https://github.com/wso2/carbon-apimgt/blob/master/components/apimgt/org.wso2.carbon.apimgt.gateway/src/main/java/org/wso2/carbon/apimgt/gateway/internal/APIHandlerServiceComponent.java#L134. This results in null JedisPool instance, and NPEs along the way.
2. The RedisBaseDistributedCountManager implementation itself is incorrect
The redis response itself will always be not null, the value returned by calling get() will.
This causes errors in asyncGetAndAddCounter and asyncGetAndAlterCounter methods
See https://github.com/wso2/carbon-apimgt/blob/master/components/apimgt/org.wso2.carbon.apimgt.gateway/src/main/java/org/wso2/carbon/apimgt/gateway/RedisBaseDistributedCountManager.java#L148 and https://github.com/wso2/carbon-apimgt/blob/master/components/apimgt/org.wso2.carbon.apimgt.gateway/src/main/java/org/wso2/carbon/apimgt/gateway/RedisBaseDistributedCountManager.java#L180
Either the value itself should be checked for null, or you should just get rid of using multi and just use the result of redis incrBy subtracted by the value for add, and result of getset for alter.
### Steps to Reproduce
Run redis 7.0
Run APIM 4.1.0
Publish api, subscribe to it using limited quota subscription, use it,
### Affected Component
APIM
### Version
4.1.0
### Environment Details (with versions)
_No response_
### Relevant Log Output
_No response_
### Related Issues
_No response_
### Suggested Labels
_No response_ | priority | redis throttling synchronization doesn t work description at attempt to use redis for throttling sync will fail and spam logs with error unable to sync throttle counter there are reasons for this redisdistributedcountmanager is initialized before the redis pool see and this results in null jedispool instance and npes along the way the redisbasedistributedcountmanager implementation itself is incorrect the redis response itself will always be not null the value returned by calling get will this causes errors in asyncgetandaddcounter and asyncgetandaltercounter methods see and either the value itself should be checked for null or you should just get rid of using multi and just use the result of redis incrby subtracted by the value for add and result of getset for alter steps to reproduce run redis run apim publish api subscribe to it using limited quota subscription use it affected component apim version environment details with versions no response relevant log output no response related issues no response suggested labels no response | 1 |
764,445 | 26,800,718,178 | IssuesEvent | 2023-02-01 14:57:10 | SecureApiGateway/SecureApiGateway | https://api.github.com/repos/SecureApiGateway/SecureApiGateway | closed | Fix RCS to sign consent decision JWTs sent to AM | bug priority | RCS is currently using a route hosted by IG to sign the RCS consent decision JWTs. This route in IG needs to be removed for security reasons, any component that needs to sign a message should do so itself.
Design work:
- [x] Review which key RCS should be using for this purpose
- [x] Review whether AM Remote Consent should use a jwks_uri or an embedded jwks containing the RCS key info (current impl is the latter)
Implementation tasks:
- [ ] Implement JWT signing logic in RCS
- [ ] Create RSA key for signing and store in google secrets
- [ ] Mount signing private key into RCS docker image and add configuration to use this key
- [ ] Write unit and integration tests for signing
- [ ] Configure AM to use the new RCS signing key; continue to configure an embedded JWKS
- [ ] Remove IG route: 70-ob-jwkms-rcs-signresponse.json | 1.0 | Fix RCS to sign consent decision JWTs sent to AM - RCS is currently using a route hosted by IG to sign the RCS consent decision JWTs. This route in IG needs to be removed for security reasons, any component that needs to sign a message should do so itself.
Design work:
- [x] Review which key RCS should be using for this purpose
- [x] Review whether AM Remote Consent should use a jwks_uri or an embedded jwks containing the RCS key info (current impl is the latter)
Implementation tasks:
- [ ] Implement JWT signing logic in RCS
- [ ] Create RSA key for signing and store in google secrets
- [ ] Mount signing private key into RCS docker image and add configuration to use this key
- [ ] Write unit and integration tests for signing
- [ ] Configure AM to use the new RCS signing key; continue to configure an embedded JWKS
- [ ] Remove IG route: 70-ob-jwkms-rcs-signresponse.json | priority | fix rcs to sign consent decision jwts sent to am rcs is currently using a route hosted by ig to sign the rcs consent decision jwts this route in ig needs to be removed for security reasons any component that needs to sign a message should do so itself design work review which key rcs should be using for this purpose review whether am remote consent should use a jwks uri or an embedded jwks containing the rcs key info current impl is the latter implementation tasks implement jwt signing logic in rcs create rsa key for signing and store in google secrets mount signing private key into rcs docker image and add configuration to use this key write unit and integration tests for signing configure am to use the new rcs signing key continue to configure an embedded jwks remove ig route ob jwkms rcs signresponse json | 1 |
281,170 | 8,692,018,542 | IssuesEvent | 2018-12-04 04:10:07 | AugurProject/augur | https://api.github.com/repos/AugurProject/augur | opened | Trade cost calculated incorrectly | 500013923 Bug Bugs Priority: Very High | A user reported that they are getting an incorrect estimated cost when filling out an order form. I was able to reproduce this on mainnet fairly easily as well.
The behavior seems to have something to do with ASK orders on the book which when taken by making the price appropriate to take the first order causes the price to suddenly jump to a point which makes no sense.
...
tried to repro on mainnet and couldn't. Seems it was an issue with the order. Need to use tools to grab mainnet blockchain while that weird order exists in order to debug it.
-bthaile
...
Screenshot of the values of the order that was causing the issues.
-bthaile
...
not able to repro the issue by taking partial order in trade and using a different user to take the rest of the buy order.
-bthaile | 1.0 | Trade cost calculated incorrectly - A user reported that they are getting an incorrect estimated cost when filling out an order form. I was able to reproduce this on mainnet fairly easily as well.
The behavior seems to have something to do with ASK orders on the book which when taken by making the price appropriate to take the first order causes the price to suddenly jump to a point which makes no sense.
...
tried to repro on mainnet and couldn't. Seems it was an issue with the order. Need to use tools to grab mainnet blockchain while that weird order exists in order to debug it.
-bthaile
...
Screenshot of the values of the order that was causing the issues.
-bthaile
...
not able to repro the issue by taking partial order in trade and using a different user to take the rest of the buy order.
-bthaile | priority | trade cost calculated incorrectly a user reported that they are getting an incorrect estimated cost when filling out an order form i was able to reproduce this on mainnet fairly easily as well the behavior seems to have something to do with ask orders on the book which when taken by making the price appropriate to take the first order causes the price to suddenly jump to a point which makes no sense tried to repro on mainnet and couldn t seems it was an issue with the order need to use tools to grab mainnet blockchain while that weird order exists in order to debug it bthaile screenshot of the values of the order that was causing the issues bthaile not able to repro the issue by taking partial order in trade and using a different user to take the rest of the buy order bthaile | 1 |
432,989 | 30,304,353,225 | IssuesEvent | 2023-07-10 08:29:04 | celestiaorg/knuu | https://api.github.com/repos/celestiaorg/knuu | opened | Use `knuu.Initialize` instead of `knuu.InitializeWithIdentifier` in README to simplify example | documentation good first issue | This simplifies the example in the README to get started quicker. | 1.0 | Use `knuu.Initialize` instead of `knuu.InitializeWithIdentifier` in README to simplify example - This simplifies the example in the README to get started quicker. | non_priority | use knuu initialize instead of knuu initializewithidentifier in readme to simplify example this simplifies the example in the readme to get started quicker | 0 |
139,491 | 31,562,844,609 | IssuesEvent | 2023-09-03 13:08:44 | h4sh5/pypi-auto-scanner | https://api.github.com/repos/h4sh5/pypi-auto-scanner | opened | python-telegram-bot 20.5 has 1 GuardDog issues | guarddog code-execution | https://pypi.org/project/python-telegram-bot
https://inspector.pypi.io/project/python-telegram-bot
```{
"dependency": "python-telegram-bot",
"version": "20.5",
"result": {
"issues": 1,
"errors": {},
"results": {
"code-execution": [
{
"location": "python-telegram-bot-20.5/setup.py:125",
"code": " subprocess.run(args, check=True, capture_output=True)",
"message": "This package is executing OS commands in the setup.py file"
}
]
},
"path": "/tmp/tmpyksyoo1t/python-telegram-bot"
}
}``` | 1.0 | python-telegram-bot 20.5 has 1 GuardDog issues - https://pypi.org/project/python-telegram-bot
https://inspector.pypi.io/project/python-telegram-bot
```{
"dependency": "python-telegram-bot",
"version": "20.5",
"result": {
"issues": 1,
"errors": {},
"results": {
"code-execution": [
{
"location": "python-telegram-bot-20.5/setup.py:125",
"code": " subprocess.run(args, check=True, capture_output=True)",
"message": "This package is executing OS commands in the setup.py file"
}
]
},
"path": "/tmp/tmpyksyoo1t/python-telegram-bot"
}
}``` | non_priority | python telegram bot has guarddog issues dependency python telegram bot version result issues errors results code execution location python telegram bot setup py code subprocess run args check true capture output true message this package is executing os commands in the setup py file path tmp python telegram bot | 0 |
416,120 | 28,067,952,474 | IssuesEvent | 2023-03-29 16:49:14 | chakra-ui/chakra-ui-docs | https://api.github.com/repos/chakra-ui/chakra-ui-docs | closed | Add documentation for `hideFrom` and `hideBelow` helper props | needs triage Topic: Documentation 📚 | ### Subject
Styled System
### Description
I can see those props are implemented https://github.com/chakra-ui/chakra-ui/blob/main/packages/core/styled-system/src/config/layout.ts#L26 but they are missing documentation. | 1.0 | Add documentation for `hideFrom` and `hideBelow` helper props - ### Subject
Styled System
### Description
I can see those props are implemented https://github.com/chakra-ui/chakra-ui/blob/main/packages/core/styled-system/src/config/layout.ts#L26 but they are missing documentation. | non_priority | add documentation for hidefrom and hidebelow helper props subject styled system description i can see those props are implemented but they are missing documentation | 0 |
205,167 | 7,094,339,518 | IssuesEvent | 2018-01-13 01:51:50 | NuGet/Home | https://api.github.com/repos/NuGet/Home | closed | Signing: add test for basic signed CMS signature | Area:PackageSigning Priority:0 | We need a test verifying a package signed with neither an author or repository signature. | 1.0 | Signing: add test for basic signed CMS signature - We need a test verifying a package signed with neither an author or repository signature. | priority | signing add test for basic signed cms signature we need a test verifying a package signed with neither an author or repository signature | 1 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.