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 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
31,649 | 2,735,073,186 | IssuesEvent | 2015-04-18 02:07:25 | GoogleCloudPlatform/kubernetes | https://api.github.com/repos/GoogleCloudPlatform/kubernetes | closed | the container data lost when restart k8s cluster env | priority/support | hi,
I meet some questions when use kubernetes cluster, please kindly help me if you know the reason.
1.The pod container's data lost when restart k8s cluster, I find replicatorController will create a new pod other than restart the pod container when start the cluster. I set the "restartPolicy" for replicatorController, but failed.
2.how to link containers in k8s? define a service for the pods? it's likely different with docker.
thanks | 1.0 | the container data lost when restart k8s cluster env - hi,
I meet some questions when use kubernetes cluster, please kindly help me if you know the reason.
1.The pod container's data lost when restart k8s cluster, I find replicatorController will create a new pod other than restart the pod container when start the cluster. I set the "restartPolicy" for replicatorController, but failed.
2.how to link containers in k8s? define a service for the pods? it's likely different with docker.
thanks | priority | the container data lost when restart cluster env hi i meet some questions when use kubernetes cluster please kindly help me if you know the reason the pod container s data lost when restart cluster i find replicatorcontroller will create a new pod other than restart the pod container when start the cluster i set the restartpolicy for replicatorcontroller but failed how to link containers in define a service for the pods it s likely different with docker thanks | 1 |
486,334 | 14,007,624,179 | IssuesEvent | 2020-10-28 21:55:11 | salesagility/SuiteCRM | https://api.github.com/repos/salesagility/SuiteCRM | closed | Cannot fully remove Module Loader package when custom fields are defined. | Area: Module Priority:Important Status:Fix Proposed Type:Bug | A change introduced in e808d92a5de24f3f51f8272c0504959039fd9677 [changed](https://github.com/salesagility/SuiteCRM/commit/e808d92a5de24f3f51f8272c0504959039fd9677#diff-b0a5d2e2814371306c2fac0d6282c675L1303) the way `uninstall_custom_fields()` invokes the `DynamicField` class was used. This change attempts to replace direct invocation of bean-defined classes to use the cache-enabled, optimized `BeanFactory::newBean()`.
https://github.com/salesagility/SuiteCRM/blob/e808d92a5de24f3f51f8272c0504959039fd9677/ModuleInstall/ModuleInstaller.php#L1305
The problem here is that `DynamicField` is not a fully defined class.
When SugarBean attempts to find the class file it fails. The module doesn't define its class files fully. Arguably, it shouldn't, because it's not a class derived from SugarBean or any standardized object.
A user is met with a progress bar of 87% -- in this screenshot we've enabled PHP's `display_errors` settings to show where specifically it fails:
While there may be a better long-term solution, the immediate problem is resolved by simply replacing `$dyField = BeanFactory::newBean('DynamicFields');` with the former value of `$dyField = new DynamicField();`. I'll be issuing a pull request with this change momentarily. | 1.0 | Cannot fully remove Module Loader package when custom fields are defined. - A change introduced in e808d92a5de24f3f51f8272c0504959039fd9677 [changed](https://github.com/salesagility/SuiteCRM/commit/e808d92a5de24f3f51f8272c0504959039fd9677#diff-b0a5d2e2814371306c2fac0d6282c675L1303) the way `uninstall_custom_fields()` invokes the `DynamicField` class was used. This change attempts to replace direct invocation of bean-defined classes to use the cache-enabled, optimized `BeanFactory::newBean()`.
https://github.com/salesagility/SuiteCRM/blob/e808d92a5de24f3f51f8272c0504959039fd9677/ModuleInstall/ModuleInstaller.php#L1305
The problem here is that `DynamicField` is not a fully defined class.
When SugarBean attempts to find the class file it fails. The module doesn't define its class files fully. Arguably, it shouldn't, because it's not a class derived from SugarBean or any standardized object.
A user is met with a progress bar of 87% -- in this screenshot we've enabled PHP's `display_errors` settings to show where specifically it fails:
While there may be a better long-term solution, the immediate problem is resolved by simply replacing `$dyField = BeanFactory::newBean('DynamicFields');` with the former value of `$dyField = new DynamicField();`. I'll be issuing a pull request with this change momentarily. | priority | cannot fully remove module loader package when custom fields are defined a change introduced in the way uninstall custom fields invokes the dynamicfield class was used this change attempts to replace direct invocation of bean defined classes to use the cache enabled optimized beanfactory newbean the problem here is that dynamicfield is not a fully defined class when sugarbean attempts to find the class file it fails the module doesn t define its class files fully arguably it shouldn t because it s not a class derived from sugarbean or any standardized object a user is met with a progress bar of in this screenshot we ve enabled php s display errors settings to show where specifically it fails while there may be a better long term solution the immediate problem is resolved by simply replacing dyfield beanfactory newbean dynamicfields with the former value of dyfield new dynamicfield i ll be issuing a pull request with this change momentarily | 1 |
539,490 | 15,789,676,642 | IssuesEvent | 2021-04-01 23:21:41 | dtcenter/METviewer | https://api.github.com/repos/dtcenter/METviewer | closed | Using Github actions to build documentation | priority: low type: new feature | *Replace italics below with details for this issue.*
## Describe the New Feature ##
*Provide a description of the new feature request here.*
### Acceptance Testing ###
*List input data types and sources.*
*Describe tests required for new functionality.*
### Time Estimate ###
*Estimate the amount of work required here.*
*Issues should represent approximately 1 to 3 days of work.*
### Sub-Issues ###
Consider breaking the new feature down into sub-issues.
- [ ] *Add a checkbox for each sub-issue here.*
### Relevant Deadlines ###
None
### Funding Source ###
None
## Define the Metadata ##
### Assignee ###
Hank Fisher
### Labels ###
- [ ] Select **component(s)**
- [ ] Select **priority**
- [ ] Select **requestor(s)**
### Projects and Milestone ###
- [ ] Review **projects** and select relevant **Repository** and **Organization** ones or add "alert:NEED PROJECT ASSIGNMENT" label
- [ ] Select **milestone** to next major version milestone or "Future Versions"
## Define Related Issue(s) ##
Consider the impact to the other METplus components.
- [ ] [METplus](https://github.com/dtcenter/METplus/issues/new/choose), [MET](https://github.com/dtcenter/MET/issues/new/choose), [METdatadb](https://github.com/dtcenter/METdatadb/issues/new/choose), [METviewer](https://github.com/dtcenter/METviewer/issues/new/choose), [METexpress](https://github.com/dtcenter/METexpress/issues/new/choose), [METcalcpy](https://github.com/dtcenter/METcalcpy/issues/new/choose), [METplotpy](https://github.com/dtcenter/METplotpy/issues/new/choose)
## New Feature Checklist ##
See the [METplus Workflow](https://dtcenter.github.io/METplus/Contributors_Guide/github_workflow.html) for details.
- [ ] Complete the issue definition above, including the **Time Estimate** and **Funding source**.
- [ ] Fork this repository or create a branch of **develop**.
Branch name: `feature_<Issue Number>_<Description>`
- [ ] Complete the development and test your changes.
- [ ] Add/update log messages for easier debugging.
- [ ] Add/update unit tests.
- [ ] Add/update documentation.
- [ ] Push local changes to GitHub.
- [ ] Submit a pull request to merge into **develop**.
Pull request: `feature <Issue Number> <Description>`
- [ ] Define the pull request metadata, as permissions allow.
Select: **Reviewer(s)**, **Project(s)**, **Milestone**, and **Linked issues**
- [ ] Iterate until the reviewer(s) accept and merge your changes.
- [ ] Delete your fork or branch.
- [ ] Close this issue.
| 1.0 | Using Github actions to build documentation - *Replace italics below with details for this issue.*
## Describe the New Feature ##
*Provide a description of the new feature request here.*
### Acceptance Testing ###
*List input data types and sources.*
*Describe tests required for new functionality.*
### Time Estimate ###
*Estimate the amount of work required here.*
*Issues should represent approximately 1 to 3 days of work.*
### Sub-Issues ###
Consider breaking the new feature down into sub-issues.
- [ ] *Add a checkbox for each sub-issue here.*
### Relevant Deadlines ###
None
### Funding Source ###
None
## Define the Metadata ##
### Assignee ###
Hank Fisher
### Labels ###
- [ ] Select **component(s)**
- [ ] Select **priority**
- [ ] Select **requestor(s)**
### Projects and Milestone ###
- [ ] Review **projects** and select relevant **Repository** and **Organization** ones or add "alert:NEED PROJECT ASSIGNMENT" label
- [ ] Select **milestone** to next major version milestone or "Future Versions"
## Define Related Issue(s) ##
Consider the impact to the other METplus components.
- [ ] [METplus](https://github.com/dtcenter/METplus/issues/new/choose), [MET](https://github.com/dtcenter/MET/issues/new/choose), [METdatadb](https://github.com/dtcenter/METdatadb/issues/new/choose), [METviewer](https://github.com/dtcenter/METviewer/issues/new/choose), [METexpress](https://github.com/dtcenter/METexpress/issues/new/choose), [METcalcpy](https://github.com/dtcenter/METcalcpy/issues/new/choose), [METplotpy](https://github.com/dtcenter/METplotpy/issues/new/choose)
## New Feature Checklist ##
See the [METplus Workflow](https://dtcenter.github.io/METplus/Contributors_Guide/github_workflow.html) for details.
- [ ] Complete the issue definition above, including the **Time Estimate** and **Funding source**.
- [ ] Fork this repository or create a branch of **develop**.
Branch name: `feature_<Issue Number>_<Description>`
- [ ] Complete the development and test your changes.
- [ ] Add/update log messages for easier debugging.
- [ ] Add/update unit tests.
- [ ] Add/update documentation.
- [ ] Push local changes to GitHub.
- [ ] Submit a pull request to merge into **develop**.
Pull request: `feature <Issue Number> <Description>`
- [ ] Define the pull request metadata, as permissions allow.
Select: **Reviewer(s)**, **Project(s)**, **Milestone**, and **Linked issues**
- [ ] Iterate until the reviewer(s) accept and merge your changes.
- [ ] Delete your fork or branch.
- [ ] Close this issue.
| priority | using github actions to build documentation replace italics below with details for this issue describe the new feature provide a description of the new feature request here acceptance testing list input data types and sources describe tests required for new functionality time estimate estimate the amount of work required here issues should represent approximately to days of work sub issues consider breaking the new feature down into sub issues add a checkbox for each sub issue here relevant deadlines none funding source none define the metadata assignee hank fisher labels select component s select priority select requestor s projects and milestone review projects and select relevant repository and organization ones or add alert need project assignment label select milestone to next major version milestone or future versions define related issue s consider the impact to the other metplus components new feature checklist see the for details complete the issue definition above including the time estimate and funding source fork this repository or create a branch of develop branch name feature complete the development and test your changes add update log messages for easier debugging add update unit tests add update documentation push local changes to github submit a pull request to merge into develop pull request feature define the pull request metadata as permissions allow select reviewer s project s milestone and linked issues iterate until the reviewer s accept and merge your changes delete your fork or branch close this issue | 1 |
34,229 | 4,535,927,580 | IssuesEvent | 2016-09-08 18:49:45 | Tiendil/the-tale | https://api.github.com/repos/Tiendil/the-tale | closed | Мастера: добалансировать максимальное влияние на экономику | comp_game_logic cont_game_designe est_medium type_improvement | - учесть, что стабильность может снять только часть других параметров
- слишком сильно изменяется свобода и транспорт | 1.0 | Мастера: добалансировать максимальное влияние на экономику - - учесть, что стабильность может снять только часть других параметров
- слишком сильно изменяется свобода и транспорт | non_priority | мастера добалансировать максимальное влияние на экономику учесть что стабильность может снять только часть других параметров слишком сильно изменяется свобода и транспорт | 0 |
91,411 | 18,466,444,484 | IssuesEvent | 2021-10-17 00:39:46 | google/iree | https://api.github.com/repos/google/iree | opened | FlattenMemRefSubspanPass failing with rank-0 memrefs. | codegen | FoldSubspanOffsetIntoLoadStore currently expects that all loaded values are rank >1 - I'm hitting a case where this crashes with a null deref: https://github.com/google/iree/blob/e34c95d5db7a1fcb32a45fb72b31da2a9613166e/iree/compiler/Codegen/Common/FlattenMemRefSubspanPass.cpp#L514 because op.indices() is empty (on the first memref.store):
```mlir
module {
func @main_dispatch_3() {
%c1 = arith.constant 1 : index
%c0 = arith.constant 0 : index
%c5 = arith.constant 5 : index
%c1280 = arith.constant 1280 : index
%c32 = arith.constant 32 : index
%c-2147483648_i32 = arith.constant -2147483648 : i32
%c5_i32 = arith.constant 5 : i32
%0 = hal.interface.binding.subspan @io::@s0b0_ro[%c32] : memref<5xi32>
%1 = hal.interface.binding.subspan @io::@s0b1_wo[%c1280] : memref<i32>
memref.store %c-2147483648_i32, %1[] : memref<i32>
scf.for %arg0 = %c0 to %c5 step %c1 {
%4 = memref.load %0[%arg0] : memref<5xi32>
%5 = memref.load %1[] : memref<i32>
%6 = arith.cmpi sgt, %4, %5 : i32
%7 = select %6, %4, %5 : i32
memref.store %7, %1[] : memref<i32>
}
%2 = memref.load %1[] : memref<i32>
%3 = arith.subi %c5_i32, %2 : i32
memref.store %3, %1[] : memref<i32>
return
}
hal.interface private @io attributes {push_constants = 0 : index} {
hal.interface.binding public @s0b0_ro, set=0, binding=0, type="StorageBuffer", access="Read"
hal.interface.binding public @s0b1_wo, set=0, binding=1, type="StorageBuffer", access="Write"
}
}
```
I tried to work around this by checking for rank-0 and using the offset directly, but then the memref.store verifier failed because it was ensuring that there were 0 indices for a rank-0 memref (makes sense).
@antiagainst: what do you recommend for this? I thought about maybe widening the memref<i32> to memref<1xi32> so that I could index into it, but I'm not sure how whatever casts I would need would mess with the rest of the system.
I think this only works today because we have 0 offsets for everything so the code path is not hit. | 1.0 | FlattenMemRefSubspanPass failing with rank-0 memrefs. - FoldSubspanOffsetIntoLoadStore currently expects that all loaded values are rank >1 - I'm hitting a case where this crashes with a null deref: https://github.com/google/iree/blob/e34c95d5db7a1fcb32a45fb72b31da2a9613166e/iree/compiler/Codegen/Common/FlattenMemRefSubspanPass.cpp#L514 because op.indices() is empty (on the first memref.store):
```mlir
module {
func @main_dispatch_3() {
%c1 = arith.constant 1 : index
%c0 = arith.constant 0 : index
%c5 = arith.constant 5 : index
%c1280 = arith.constant 1280 : index
%c32 = arith.constant 32 : index
%c-2147483648_i32 = arith.constant -2147483648 : i32
%c5_i32 = arith.constant 5 : i32
%0 = hal.interface.binding.subspan @io::@s0b0_ro[%c32] : memref<5xi32>
%1 = hal.interface.binding.subspan @io::@s0b1_wo[%c1280] : memref<i32>
memref.store %c-2147483648_i32, %1[] : memref<i32>
scf.for %arg0 = %c0 to %c5 step %c1 {
%4 = memref.load %0[%arg0] : memref<5xi32>
%5 = memref.load %1[] : memref<i32>
%6 = arith.cmpi sgt, %4, %5 : i32
%7 = select %6, %4, %5 : i32
memref.store %7, %1[] : memref<i32>
}
%2 = memref.load %1[] : memref<i32>
%3 = arith.subi %c5_i32, %2 : i32
memref.store %3, %1[] : memref<i32>
return
}
hal.interface private @io attributes {push_constants = 0 : index} {
hal.interface.binding public @s0b0_ro, set=0, binding=0, type="StorageBuffer", access="Read"
hal.interface.binding public @s0b1_wo, set=0, binding=1, type="StorageBuffer", access="Write"
}
}
```
I tried to work around this by checking for rank-0 and using the offset directly, but then the memref.store verifier failed because it was ensuring that there were 0 indices for a rank-0 memref (makes sense).
@antiagainst: what do you recommend for this? I thought about maybe widening the memref<i32> to memref<1xi32> so that I could index into it, but I'm not sure how whatever casts I would need would mess with the rest of the system.
I think this only works today because we have 0 offsets for everything so the code path is not hit. | non_priority | flattenmemrefsubspanpass failing with rank memrefs foldsubspanoffsetintoloadstore currently expects that all loaded values are rank i m hitting a case where this crashes with a null deref because op indices is empty on the first memref store mlir module func main dispatch arith constant index arith constant index arith constant index arith constant index arith constant index c arith constant arith constant hal interface binding subspan io ro memref hal interface binding subspan io wo memref memref store c memref scf for to step memref load memref memref load memref arith cmpi sgt select memref store memref memref load memref arith subi memref store memref return hal interface private io attributes push constants index hal interface binding public ro set binding type storagebuffer access read hal interface binding public wo set binding type storagebuffer access write i tried to work around this by checking for rank and using the offset directly but then the memref store verifier failed because it was ensuring that there were indices for a rank memref makes sense antiagainst what do you recommend for this i thought about maybe widening the memref to memref so that i could index into it but i m not sure how whatever casts i would need would mess with the rest of the system i think this only works today because we have offsets for everything so the code path is not hit | 0 |
91,453 | 15,856,411,233 | IssuesEvent | 2021-04-08 02:16:47 | Sophobis76/angloAmerican | https://api.github.com/repos/Sophobis76/angloAmerican | opened | CVE-2020-8124 (Medium) detected in url-parse-1.4.4.tgz | security vulnerability | ## CVE-2020-8124 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>url-parse-1.4.4.tgz</b></p></summary>
<p>Small footprint URL parser that works seamlessly across Node.js and browser environments</p>
<p>Library home page: <a href="https://registry.npmjs.org/url-parse/-/url-parse-1.4.4.tgz">https://registry.npmjs.org/url-parse/-/url-parse-1.4.4.tgz</a></p>
<p>Path to dependency file: /angloAmerican/package.json</p>
<p>Path to vulnerable library: angloAmerican/node_modules/url-parse/package.json</p>
<p>
Dependency Hierarchy:
- build-angular-0.10.6.tgz (Root Library)
- webpack-dev-server-3.1.8.tgz
- sockjs-client-1.1.5.tgz
- :x: **url-parse-1.4.4.tgz** (Vulnerable Library)
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
Insufficient validation and sanitization of user input exists in url-parse npm package version 1.4.4 and earlier may allow attacker to bypass security checks.
<p>Publish Date: 2020-02-04
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-8124>CVE-2020-8124</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.3</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: Low
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-8124">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-8124</a></p>
<p>Release Date: 2020-02-04</p>
<p>Fix Resolution: url-parse - 1.4.5</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | CVE-2020-8124 (Medium) detected in url-parse-1.4.4.tgz - ## CVE-2020-8124 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>url-parse-1.4.4.tgz</b></p></summary>
<p>Small footprint URL parser that works seamlessly across Node.js and browser environments</p>
<p>Library home page: <a href="https://registry.npmjs.org/url-parse/-/url-parse-1.4.4.tgz">https://registry.npmjs.org/url-parse/-/url-parse-1.4.4.tgz</a></p>
<p>Path to dependency file: /angloAmerican/package.json</p>
<p>Path to vulnerable library: angloAmerican/node_modules/url-parse/package.json</p>
<p>
Dependency Hierarchy:
- build-angular-0.10.6.tgz (Root Library)
- webpack-dev-server-3.1.8.tgz
- sockjs-client-1.1.5.tgz
- :x: **url-parse-1.4.4.tgz** (Vulnerable Library)
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
Insufficient validation and sanitization of user input exists in url-parse npm package version 1.4.4 and earlier may allow attacker to bypass security checks.
<p>Publish Date: 2020-02-04
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-8124>CVE-2020-8124</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.3</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: Low
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-8124">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-8124</a></p>
<p>Release Date: 2020-02-04</p>
<p>Fix Resolution: url-parse - 1.4.5</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_priority | cve medium detected in url parse tgz cve medium severity vulnerability vulnerable library url parse tgz small footprint url parser that works seamlessly across node js and browser environments library home page a href path to dependency file angloamerican package json path to vulnerable library angloamerican node modules url parse package json dependency hierarchy build angular tgz root library webpack dev server tgz sockjs client tgz x url parse tgz vulnerable library vulnerability details insufficient validation and sanitization of user input exists in url parse npm package version and earlier may allow attacker to bypass security checks publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact none integrity impact low availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution url parse step up your open source security game with whitesource | 0 |
58,005 | 14,263,204,880 | IssuesEvent | 2020-11-20 14:07:26 | slic3r/Slic3r | https://api.github.com/repos/slic3r/Slic3r | closed | Restart required when "Send to printer" fails due to slicing | Can't Reproduce - Development Build Host/Controller | ### Version
Version 1.3.0-dev
Slic3r-master.2017.08.14.1313.a54ca92.64bit
### Operating system type + version
Windows 10 64-bit
### Behavior
* "Send to printer" and "Export G-Code" buttons do not re-activate if slicing fails when "Send to printer" is clicked. To reproduce, load a model that fails to slice. For instance, scale a bed test below the minimal layer height. In order for the buttons to become active, you must restart Slic3r. Re-loading models or fixing the slicing issue doesn't re-activate the buttons.
Test model and configuration
[4097.zip](https://github.com/alexrj/Slic3r/files/1327818/4097.zip) | 1.0 | Restart required when "Send to printer" fails due to slicing - ### Version
Version 1.3.0-dev
Slic3r-master.2017.08.14.1313.a54ca92.64bit
### Operating system type + version
Windows 10 64-bit
### Behavior
* "Send to printer" and "Export G-Code" buttons do not re-activate if slicing fails when "Send to printer" is clicked. To reproduce, load a model that fails to slice. For instance, scale a bed test below the minimal layer height. In order for the buttons to become active, you must restart Slic3r. Re-loading models or fixing the slicing issue doesn't re-activate the buttons.
Test model and configuration
[4097.zip](https://github.com/alexrj/Slic3r/files/1327818/4097.zip) | non_priority | restart required when send to printer fails due to slicing version version dev master operating system type version windows bit behavior send to printer and export g code buttons do not re activate if slicing fails when send to printer is clicked to reproduce load a model that fails to slice for instance scale a bed test below the minimal layer height in order for the buttons to become active you must restart re loading models or fixing the slicing issue doesn t re activate the buttons test model and configuration | 0 |
320,425 | 9,780,821,667 | IssuesEvent | 2019-06-07 18:00:28 | thonny/thonny | https://api.github.com/repos/thonny/thonny | closed | Pasting doesn't replace active selection in XFCE | bug low priority | **[Original report](https://bitbucket.org/bitbucket-issue-migration\thonny-issues.zip/issue/395) by me.**
----------------------------------------
| 1.0 | Pasting doesn't replace active selection in XFCE - **[Original report](https://bitbucket.org/bitbucket-issue-migration\thonny-issues.zip/issue/395) by me.**
----------------------------------------
| priority | pasting doesn t replace active selection in xfce by me | 1 |
191,155 | 14,593,420,458 | IssuesEvent | 2020-12-19 22:43:31 | github-vet/rangeloop-pointer-findings | https://api.github.com/repos/github-vet/rangeloop-pointer-findings | closed | alexcrownus/fabcar: vendor/github.com/google/certificate-transparency-go/fixchain/fixer_test.go; 27 LoC | fresh small test vendored |
Found a possible issue in [alexcrownus/fabcar](https://www.github.com/alexcrownus/fabcar) at [vendor/github.com/google/certificate-transparency-go/fixchain/fixer_test.go](https://github.com/alexcrownus/fabcar/blob/8d90c87788a72b2a497f2df6f651543827aaf69b/vendor/github.com/google/certificate-transparency-go/fixchain/fixer_test.go#L70-L96)
Below is the message reported by the analyzer for this snippet of code. Beware that the analyzer only reports the first
issue it finds, so please do not limit your consideration to the contents of the below message.
> range-loop variable i used in defer or goroutine at line 80
[Click here to see the code in its original context.](https://github.com/alexcrownus/fabcar/blob/8d90c87788a72b2a497f2df6f651543827aaf69b/vendor/github.com/google/certificate-transparency-go/fixchain/fixer_test.go#L70-L96)
<details>
<summary>Click here to show the 27 line(s) of Go which triggered the analyzer.</summary>
```go
for i, fst := range fixServerTests {
chains := make(chan []*x509.Certificate)
errors := make(chan *FixError)
f.toFix = make(chan *toFix)
f.chains = chains
f.errors = errors
wg.Add(2)
go func() {
defer wg.Done()
testChains(t, i, fst.expectedChains, chains)
}()
go func() {
defer wg.Done()
testErrors(t, i, fst.expectedErrs, errors)
}()
f.wg.Add(1)
go f.fixServer()
f.QueueChain(GetTestCertificateFromPEM(t, fst.cert),
extractTestChain(t, i, fst.chain), extractTestRoots(t, i, fst.roots))
f.Wait()
close(chains)
close(errors)
wg.Wait()
}
```
</details>
Leave a reaction on this issue to contribute to the project by classifying this instance as a **Bug** :-1:, **Mitigated** :+1:, or **Desirable Behavior** :rocket:
See the descriptions of the classifications [here](https://github.com/github-vet/rangeclosure-findings#how-can-i-help) for more information.
commit ID: 8d90c87788a72b2a497f2df6f651543827aaf69b
| 1.0 | alexcrownus/fabcar: vendor/github.com/google/certificate-transparency-go/fixchain/fixer_test.go; 27 LoC -
Found a possible issue in [alexcrownus/fabcar](https://www.github.com/alexcrownus/fabcar) at [vendor/github.com/google/certificate-transparency-go/fixchain/fixer_test.go](https://github.com/alexcrownus/fabcar/blob/8d90c87788a72b2a497f2df6f651543827aaf69b/vendor/github.com/google/certificate-transparency-go/fixchain/fixer_test.go#L70-L96)
Below is the message reported by the analyzer for this snippet of code. Beware that the analyzer only reports the first
issue it finds, so please do not limit your consideration to the contents of the below message.
> range-loop variable i used in defer or goroutine at line 80
[Click here to see the code in its original context.](https://github.com/alexcrownus/fabcar/blob/8d90c87788a72b2a497f2df6f651543827aaf69b/vendor/github.com/google/certificate-transparency-go/fixchain/fixer_test.go#L70-L96)
<details>
<summary>Click here to show the 27 line(s) of Go which triggered the analyzer.</summary>
```go
for i, fst := range fixServerTests {
chains := make(chan []*x509.Certificate)
errors := make(chan *FixError)
f.toFix = make(chan *toFix)
f.chains = chains
f.errors = errors
wg.Add(2)
go func() {
defer wg.Done()
testChains(t, i, fst.expectedChains, chains)
}()
go func() {
defer wg.Done()
testErrors(t, i, fst.expectedErrs, errors)
}()
f.wg.Add(1)
go f.fixServer()
f.QueueChain(GetTestCertificateFromPEM(t, fst.cert),
extractTestChain(t, i, fst.chain), extractTestRoots(t, i, fst.roots))
f.Wait()
close(chains)
close(errors)
wg.Wait()
}
```
</details>
Leave a reaction on this issue to contribute to the project by classifying this instance as a **Bug** :-1:, **Mitigated** :+1:, or **Desirable Behavior** :rocket:
See the descriptions of the classifications [here](https://github.com/github-vet/rangeclosure-findings#how-can-i-help) for more information.
commit ID: 8d90c87788a72b2a497f2df6f651543827aaf69b
| non_priority | alexcrownus fabcar vendor github com google certificate transparency go fixchain fixer test go loc found a possible issue in at below is the message reported by the analyzer for this snippet of code beware that the analyzer only reports the first issue it finds so please do not limit your consideration to the contents of the below message range loop variable i used in defer or goroutine at line click here to show the line s of go which triggered the analyzer go for i fst range fixservertests chains make chan certificate errors make chan fixerror f tofix make chan tofix f chains chains f errors errors wg add go func defer wg done testchains t i fst expectedchains chains go func defer wg done testerrors t i fst expectederrs errors f wg add go f fixserver f queuechain gettestcertificatefrompem t fst cert extracttestchain t i fst chain extracttestroots t i fst roots f wait close chains close errors wg wait leave a reaction on this issue to contribute to the project by classifying this instance as a bug mitigated or desirable behavior rocket see the descriptions of the classifications for more information commit id | 0 |
6,509 | 3,399,136,031 | IssuesEvent | 2015-12-02 09:23:38 | hjwylde/omnifmt | https://api.github.com/repos/hjwylde/omnifmt | closed | Make the path outputs relative to the root directory | existing: enhancement kind: code | The root directory is the one that contains the '.omnifmt.yaml' file. | 1.0 | Make the path outputs relative to the root directory - The root directory is the one that contains the '.omnifmt.yaml' file. | non_priority | make the path outputs relative to the root directory the root directory is the one that contains the omnifmt yaml file | 0 |
81,445 | 23,464,554,435 | IssuesEvent | 2022-08-16 15:37:17 | mercedes-benz/sechub | https://api.github.com/repos/mercedes-benz/sechub | closed | Improve documentation branch - divide images + version locations | documentation enhancement build | ## Situation
Currently we got only one `latest` for all at https://daimler.github.io/sechub/
## Wanted
As a developer I want to update server documentation for a dedicated server without influencing PDS or SecHub client - e.g. when code base for those releases differ.
## Solution
We must differ between
- SecHub Client
- SecHub Server
- PDS
So we need 3 different directories at
https://github.com/Daimler/sechub/tree/documentation/docs/latest
e.g.
https://github.com/Daimler/sechub/tree/documentation/docs/latest/sechub-client
https://github.com/Daimler/sechub/tree/documentation/docs/latest/sechub-server
https://github.com/Daimler/sechub/tree/documentation/docs/latest/pds
## Optional
Maybe it is possible to integrate the documentation upload directly into the release build by github actions (but be aware about the draft releases!)
| 1.0 | Improve documentation branch - divide images + version locations - ## Situation
Currently we got only one `latest` for all at https://daimler.github.io/sechub/
## Wanted
As a developer I want to update server documentation for a dedicated server without influencing PDS or SecHub client - e.g. when code base for those releases differ.
## Solution
We must differ between
- SecHub Client
- SecHub Server
- PDS
So we need 3 different directories at
https://github.com/Daimler/sechub/tree/documentation/docs/latest
e.g.
https://github.com/Daimler/sechub/tree/documentation/docs/latest/sechub-client
https://github.com/Daimler/sechub/tree/documentation/docs/latest/sechub-server
https://github.com/Daimler/sechub/tree/documentation/docs/latest/pds
## Optional
Maybe it is possible to integrate the documentation upload directly into the release build by github actions (but be aware about the draft releases!)
| non_priority | improve documentation branch divide images version locations situation currently we got only one latest for all at wanted as a developer i want to update server documentation for a dedicated server without influencing pds or sechub client e g when code base for those releases differ solution we must differ between sechub client sechub server pds so we need different directories at e g optional maybe it is possible to integrate the documentation upload directly into the release build by github actions but be aware about the draft releases | 0 |
698,246 | 23,971,246,391 | IssuesEvent | 2022-09-13 07:57:12 | nelsonic/nelsonic.github.io | https://api.github.com/repos/nelsonic/nelsonic.github.io | opened | Bike Baby Seat | enhancement help wanted question external-dependency technical T25m priority-2 | @SimonLab is this the seat you guys have?
Thule Yepp Mini: https://www.thule.com/en-us/child-bike-seats/front-mounted-child-bike-seats/thule-yepp-mini-_-12020101
https://www.sigmasports.com/item/Thule/Yepp-Mini-Child-Seat/Y38B
| 1.0 | Bike Baby Seat - @SimonLab is this the seat you guys have?
Thule Yepp Mini: https://www.thule.com/en-us/child-bike-seats/front-mounted-child-bike-seats/thule-yepp-mini-_-12020101
https://www.sigmasports.com/item/Thule/Yepp-Mini-Child-Seat/Y38B
| priority | bike baby seat simonlab is this the seat you guys have thule yepp mini | 1 |
695,989 | 23,878,659,743 | IssuesEvent | 2022-09-07 21:52:10 | o3de/o3de.org | https://api.github.com/repos/o3de/o3de.org | closed | [SITE][FEATURE] Left-hand ToC behavior change: Expand section + take user to page | feature/website priority/critical RTE WF1 kind/website kind/foundation | ## Describe the feature you'd like available on the website
Currently on the website, the left-hand ToC behavior simply expands a section without loading a new page for the user. Instead, the section should both expand _and_ the user should be taken to the selected page.
## Proposed implementation
In addition to section expansion, any 'click' actions on the left-hand ToC should always bring a user to the selected webpage.
## Available alternatives
No behavior change. This is considered to be an undesirable outcome from a UX standpoint. @o3de/sig-ui-ux has repeatedly given feedback that users expect different behavior.
| 1.0 | [SITE][FEATURE] Left-hand ToC behavior change: Expand section + take user to page - ## Describe the feature you'd like available on the website
Currently on the website, the left-hand ToC behavior simply expands a section without loading a new page for the user. Instead, the section should both expand _and_ the user should be taken to the selected page.
## Proposed implementation
In addition to section expansion, any 'click' actions on the left-hand ToC should always bring a user to the selected webpage.
## Available alternatives
No behavior change. This is considered to be an undesirable outcome from a UX standpoint. @o3de/sig-ui-ux has repeatedly given feedback that users expect different behavior.
| priority | left hand toc behavior change expand section take user to page describe the feature you d like available on the website currently on the website the left hand toc behavior simply expands a section without loading a new page for the user instead the section should both expand and the user should be taken to the selected page proposed implementation in addition to section expansion any click actions on the left hand toc should always bring a user to the selected webpage available alternatives no behavior change this is considered to be an undesirable outcome from a ux standpoint sig ui ux has repeatedly given feedback that users expect different behavior | 1 |
136,988 | 18,751,527,607 | IssuesEvent | 2021-11-05 03:02:39 | Dima2022/Resiliency-Studio | https://api.github.com/repos/Dima2022/Resiliency-Studio | closed | CVE-2020-10693 (Medium) detected in hibernate-validator-5.3.4.Final.jar - autoclosed | security vulnerability | ## CVE-2020-10693 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>hibernate-validator-5.3.4.Final.jar</b></p></summary>
<p>Hibernate's Bean Validation (JSR-303) reference implementation.</p>
<p>Library home page: <a href="http://hibernate.org/validator">http://hibernate.org/validator</a></p>
<p>Path to dependency file: Resiliency-Studio/resiliency-studio-security/pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/org/hibernate/hibernate-validator/5.3.4.Final/hibernate-validator-5.3.4.Final.jar,/home/wss-scanner/.m2/repository/org/hibernate/hibernate-validator/5.3.4.Final/hibernate-validator-5.3.4.Final.jar,/home/wss-scanner/.m2/repository/org/hibernate/hibernate-validator/5.3.4.Final/hibernate-validator-5.3.4.Final.jar</p>
<p>
Dependency Hierarchy:
- spring-boot-starter-web-1.5.1.RELEASE.jar (Root Library)
- :x: **hibernate-validator-5.3.4.Final.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/Dima2022/Resiliency-Studio/commit/9809d9b7bfdc114eafb0a14d86667f3a76a014e8">9809d9b7bfdc114eafb0a14d86667f3a76a014e8</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
A flaw was found in Hibernate Validator version 6.1.2.Final. A bug in the message interpolation processor enables invalid EL expressions to be evaluated as if they were valid. This flaw allows attackers to bypass input sanitation (escaping, stripping) controls that developers may have put in place when handling user-controlled data in error messages.
<p>Publish Date: 2020-05-06
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-10693>CVE-2020-10693</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.3</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: Low
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://hibernate.atlassian.net/projects/HV/issues/HV-1774">https://hibernate.atlassian.net/projects/HV/issues/HV-1774</a></p>
<p>Release Date: 2020-05-06</p>
<p>Fix Resolution: org.hibernate:hibernate-validator:6.0.20.Final,6.1.5.Final</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"Java","groupId":"org.hibernate","packageName":"hibernate-validator","packageVersion":"5.3.4.Final","packageFilePaths":["/resiliency-studio-security/pom.xml","/resiliency-studio-agent/pom.xml","/resiliency-studio-service/pom.xml"],"isTransitiveDependency":true,"dependencyTree":"org.springframework.boot:spring-boot-starter-web:1.5.1.RELEASE;org.hibernate:hibernate-validator:5.3.4.Final","isMinimumFixVersionAvailable":true,"minimumFixVersion":"org.hibernate:hibernate-validator:6.0.20.Final,6.1.5.Final"}],"baseBranches":[],"vulnerabilityIdentifier":"CVE-2020-10693","vulnerabilityDetails":"A flaw was found in Hibernate Validator version 6.1.2.Final. A bug in the message interpolation processor enables invalid EL expressions to be evaluated as if they were valid. This flaw allows attackers to bypass input sanitation (escaping, stripping) controls that developers may have put in place when handling user-controlled data in error messages.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-10693","cvss3Severity":"medium","cvss3Score":"5.3","cvss3Metrics":{"A":"None","AC":"Low","PR":"None","S":"Unchanged","C":"None","UI":"None","AV":"Network","I":"Low"},"extraData":{}}</REMEDIATE> --> | True | CVE-2020-10693 (Medium) detected in hibernate-validator-5.3.4.Final.jar - autoclosed - ## CVE-2020-10693 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>hibernate-validator-5.3.4.Final.jar</b></p></summary>
<p>Hibernate's Bean Validation (JSR-303) reference implementation.</p>
<p>Library home page: <a href="http://hibernate.org/validator">http://hibernate.org/validator</a></p>
<p>Path to dependency file: Resiliency-Studio/resiliency-studio-security/pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/org/hibernate/hibernate-validator/5.3.4.Final/hibernate-validator-5.3.4.Final.jar,/home/wss-scanner/.m2/repository/org/hibernate/hibernate-validator/5.3.4.Final/hibernate-validator-5.3.4.Final.jar,/home/wss-scanner/.m2/repository/org/hibernate/hibernate-validator/5.3.4.Final/hibernate-validator-5.3.4.Final.jar</p>
<p>
Dependency Hierarchy:
- spring-boot-starter-web-1.5.1.RELEASE.jar (Root Library)
- :x: **hibernate-validator-5.3.4.Final.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/Dima2022/Resiliency-Studio/commit/9809d9b7bfdc114eafb0a14d86667f3a76a014e8">9809d9b7bfdc114eafb0a14d86667f3a76a014e8</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
A flaw was found in Hibernate Validator version 6.1.2.Final. A bug in the message interpolation processor enables invalid EL expressions to be evaluated as if they were valid. This flaw allows attackers to bypass input sanitation (escaping, stripping) controls that developers may have put in place when handling user-controlled data in error messages.
<p>Publish Date: 2020-05-06
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-10693>CVE-2020-10693</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.3</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: Low
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://hibernate.atlassian.net/projects/HV/issues/HV-1774">https://hibernate.atlassian.net/projects/HV/issues/HV-1774</a></p>
<p>Release Date: 2020-05-06</p>
<p>Fix Resolution: org.hibernate:hibernate-validator:6.0.20.Final,6.1.5.Final</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"Java","groupId":"org.hibernate","packageName":"hibernate-validator","packageVersion":"5.3.4.Final","packageFilePaths":["/resiliency-studio-security/pom.xml","/resiliency-studio-agent/pom.xml","/resiliency-studio-service/pom.xml"],"isTransitiveDependency":true,"dependencyTree":"org.springframework.boot:spring-boot-starter-web:1.5.1.RELEASE;org.hibernate:hibernate-validator:5.3.4.Final","isMinimumFixVersionAvailable":true,"minimumFixVersion":"org.hibernate:hibernate-validator:6.0.20.Final,6.1.5.Final"}],"baseBranches":[],"vulnerabilityIdentifier":"CVE-2020-10693","vulnerabilityDetails":"A flaw was found in Hibernate Validator version 6.1.2.Final. A bug in the message interpolation processor enables invalid EL expressions to be evaluated as if they were valid. This flaw allows attackers to bypass input sanitation (escaping, stripping) controls that developers may have put in place when handling user-controlled data in error messages.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-10693","cvss3Severity":"medium","cvss3Score":"5.3","cvss3Metrics":{"A":"None","AC":"Low","PR":"None","S":"Unchanged","C":"None","UI":"None","AV":"Network","I":"Low"},"extraData":{}}</REMEDIATE> --> | non_priority | cve medium detected in hibernate validator final jar autoclosed cve medium severity vulnerability vulnerable library hibernate validator final jar hibernate s bean validation jsr reference implementation library home page a href path to dependency file resiliency studio resiliency studio security pom xml path to vulnerable library home wss scanner repository org hibernate hibernate validator final hibernate validator final jar home wss scanner repository org hibernate hibernate validator final hibernate validator final jar home wss scanner repository org hibernate hibernate validator final hibernate validator final jar dependency hierarchy spring boot starter web release jar root library x hibernate validator final jar vulnerable library found in head commit a href vulnerability details a flaw was found in hibernate validator version final a bug in the message interpolation processor enables invalid el expressions to be evaluated as if they were valid this flaw allows attackers to bypass input sanitation escaping stripping controls that developers may have put in place when handling user controlled data in error messages publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact none integrity impact low availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution org hibernate hibernate validator final final isopenpronvulnerability true ispackagebased true isdefaultbranch true packages istransitivedependency true dependencytree org springframework boot spring boot starter web release org hibernate hibernate validator final isminimumfixversionavailable true minimumfixversion org hibernate hibernate validator final final basebranches vulnerabilityidentifier cve vulnerabilitydetails a flaw was found in hibernate validator version final a bug in the message interpolation processor enables invalid el expressions to be evaluated as if they were valid this flaw allows attackers to bypass input sanitation escaping stripping controls that developers may have put in place when handling user controlled data in error messages vulnerabilityurl | 0 |
511,994 | 14,886,702,875 | IssuesEvent | 2021-01-20 17:17:33 | dermestid/bold-phylodiv-scripts | https://api.github.com/repos/dermestid/bold-phylodiv-scripts | opened | use pre-generated sample PD for heroku deployment | enhancement lower priority ui | Since getting executables to work on heroku is a pain, skip that step for now and include "demo" data in the app. | 1.0 | use pre-generated sample PD for heroku deployment - Since getting executables to work on heroku is a pain, skip that step for now and include "demo" data in the app. | priority | use pre generated sample pd for heroku deployment since getting executables to work on heroku is a pain skip that step for now and include demo data in the app | 1 |
124,600 | 12,235,238,605 | IssuesEvent | 2020-05-04 14:36:29 | vmware-samples/vcenter-event-broker-appliance | https://api.github.com/repos/vmware-samples/vcenter-event-broker-appliance | closed | Document VEBA deployment to existing K8s Cluster | documentation | We've had a number of requests from both customers/field on being able to deploy VEBA to an existing K8s Cluster and since VEBA itself is a K8s app, this is something that just needs to be done. | 1.0 | Document VEBA deployment to existing K8s Cluster - We've had a number of requests from both customers/field on being able to deploy VEBA to an existing K8s Cluster and since VEBA itself is a K8s app, this is something that just needs to be done. | non_priority | document veba deployment to existing cluster we ve had a number of requests from both customers field on being able to deploy veba to an existing cluster and since veba itself is a app this is something that just needs to be done | 0 |
68,319 | 28,353,801,766 | IssuesEvent | 2023-04-12 05:30:32 | Azure/azure-sdk-for-net | https://api.github.com/repos/Azure/azure-sdk-for-net | closed | [QUERY] Distributed tracing Activity scope for batched Service Bus Functions | Service Bus Client customer-reported question issue-addressed | ### Library name and version
Azure.Messaging.ServiceBus 7.13.1
Microsoft.Azure.WebJobs.Extensions.ServiceBus 5.9.0
### Query/Question
There currently exists discrepancies when processing Service Bus messages in either a batched versus singular fashion regarding Activity scoping and how the Functions consider incoming message `Diagnostic-Id` properties.
In my scenario, one (or many) message producers are sending Service Bus messages to a given queue/topic and each of these messages may contain different `Diagnostic-Id`s. The expectation here, is that this producer-provided trace ID is appropriately utilised within the Function when processing the message, and in turn is appropriately sent to any downstream components.
Now, when using a singular message Function (as below), this works perfectly.
``` csharp
public ProcessIncomingMessage([ServiceBusTrigger(...)] ServiceBusReceivedMessage message)
{
// Activity "ServiceBusProcessor.ProcessMessage"
// uses incoming `Diagnostic-Id` ✅
DoWork(message);
}
```
When using a batched message Function, however, incoming `Diagnostic-Id`s are being somewhat "squashed" at this level; the Activity uses a new ID (which is being sent downstream), and the individual message trace IDs are added to `Activity.Links`. As below:
``` csharp
public ProcessIncomingMessages([ServiceBusTrigger(...)] ServiceBusReceivedMessage[] messages)
{
// Activity "ServiceBusListener.ProcessMessages"
// uses new Id; incoming `Diagnostic-Id`s added to `Activity.Links` 🤔
foreach (var message in messages)
{
DoWork(message);
}
}
```
This seems backwards, I would expect that the incoming `Diagnostic-Id`s be used as the "primary" Activity ID and the "batch" Activity is added as a Link (or equivalent).
Whether or not the message consumer processes messages in batch or singularly could be considered an implementation detail (at least in this scenario) and the message producer shouldn't care; it would expect that the `Diagnostic-Id` it provided in a given message is the trace ID used for any downstream actions performed in its processing.
Now, by this point it may seem obvious that such scoping is just not really feasible within a method written like this (with a `ServiceBusReceivedMessage[]` argument), and the workaround/solution is to simply perform this context flip manually within the batch processor:
``` csharp
foreach (var message in messages)
{
using var activity = new Activity("ServiceBusProcessor.ProcessMessage");
// preserve reference to the batch Activity (optional)
activity.AddBaggage("BatchActivityId", Activity.Current.Id);
// use incoming `Diagnostic-Id` (if present)
if (message.ApplicationProperties.TryGetValue("Diagnostic-Id", out var value)
&& value is string diagnosticId
&& ActivityContext.TryParse(diagnosticId, null, out var parentContext))
{
activity.SetParentId(parentContext.TraceId, parentContext.SpanId, parentContext.TraceFlags);
}
activity.Start();
DoWork(message);
}
```
I guess my main question at this point is whether or not this would be the suggested approach; or whether there's another way of implementing a batch-triggered Function such that the trace IDs are registered as I would expect them to be (per-message). The documentation I could find on this subject is rather limited.
cc @JoshLove-msft #30279
### Environment
.Net SDK 6.0.407 | 1.0 | [QUERY] Distributed tracing Activity scope for batched Service Bus Functions - ### Library name and version
Azure.Messaging.ServiceBus 7.13.1
Microsoft.Azure.WebJobs.Extensions.ServiceBus 5.9.0
### Query/Question
There currently exists discrepancies when processing Service Bus messages in either a batched versus singular fashion regarding Activity scoping and how the Functions consider incoming message `Diagnostic-Id` properties.
In my scenario, one (or many) message producers are sending Service Bus messages to a given queue/topic and each of these messages may contain different `Diagnostic-Id`s. The expectation here, is that this producer-provided trace ID is appropriately utilised within the Function when processing the message, and in turn is appropriately sent to any downstream components.
Now, when using a singular message Function (as below), this works perfectly.
``` csharp
public ProcessIncomingMessage([ServiceBusTrigger(...)] ServiceBusReceivedMessage message)
{
// Activity "ServiceBusProcessor.ProcessMessage"
// uses incoming `Diagnostic-Id` ✅
DoWork(message);
}
```
When using a batched message Function, however, incoming `Diagnostic-Id`s are being somewhat "squashed" at this level; the Activity uses a new ID (which is being sent downstream), and the individual message trace IDs are added to `Activity.Links`. As below:
``` csharp
public ProcessIncomingMessages([ServiceBusTrigger(...)] ServiceBusReceivedMessage[] messages)
{
// Activity "ServiceBusListener.ProcessMessages"
// uses new Id; incoming `Diagnostic-Id`s added to `Activity.Links` 🤔
foreach (var message in messages)
{
DoWork(message);
}
}
```
This seems backwards, I would expect that the incoming `Diagnostic-Id`s be used as the "primary" Activity ID and the "batch" Activity is added as a Link (or equivalent).
Whether or not the message consumer processes messages in batch or singularly could be considered an implementation detail (at least in this scenario) and the message producer shouldn't care; it would expect that the `Diagnostic-Id` it provided in a given message is the trace ID used for any downstream actions performed in its processing.
Now, by this point it may seem obvious that such scoping is just not really feasible within a method written like this (with a `ServiceBusReceivedMessage[]` argument), and the workaround/solution is to simply perform this context flip manually within the batch processor:
``` csharp
foreach (var message in messages)
{
using var activity = new Activity("ServiceBusProcessor.ProcessMessage");
// preserve reference to the batch Activity (optional)
activity.AddBaggage("BatchActivityId", Activity.Current.Id);
// use incoming `Diagnostic-Id` (if present)
if (message.ApplicationProperties.TryGetValue("Diagnostic-Id", out var value)
&& value is string diagnosticId
&& ActivityContext.TryParse(diagnosticId, null, out var parentContext))
{
activity.SetParentId(parentContext.TraceId, parentContext.SpanId, parentContext.TraceFlags);
}
activity.Start();
DoWork(message);
}
```
I guess my main question at this point is whether or not this would be the suggested approach; or whether there's another way of implementing a batch-triggered Function such that the trace IDs are registered as I would expect them to be (per-message). The documentation I could find on this subject is rather limited.
cc @JoshLove-msft #30279
### Environment
.Net SDK 6.0.407 | non_priority | distributed tracing activity scope for batched service bus functions library name and version azure messaging servicebus microsoft azure webjobs extensions servicebus query question there currently exists discrepancies when processing service bus messages in either a batched versus singular fashion regarding activity scoping and how the functions consider incoming message diagnostic id properties in my scenario one or many message producers are sending service bus messages to a given queue topic and each of these messages may contain different diagnostic id s the expectation here is that this producer provided trace id is appropriately utilised within the function when processing the message and in turn is appropriately sent to any downstream components now when using a singular message function as below this works perfectly csharp public processincomingmessage servicebusreceivedmessage message activity servicebusprocessor processmessage uses incoming diagnostic id ✅ dowork message when using a batched message function however incoming diagnostic id s are being somewhat squashed at this level the activity uses a new id which is being sent downstream and the individual message trace ids are added to activity links as below csharp public processincomingmessages servicebusreceivedmessage messages activity servicebuslistener processmessages uses new id incoming diagnostic id s added to activity links 🤔 foreach var message in messages dowork message this seems backwards i would expect that the incoming diagnostic id s be used as the primary activity id and the batch activity is added as a link or equivalent whether or not the message consumer processes messages in batch or singularly could be considered an implementation detail at least in this scenario and the message producer shouldn t care it would expect that the diagnostic id it provided in a given message is the trace id used for any downstream actions performed in its processing now by this point it may seem obvious that such scoping is just not really feasible within a method written like this with a servicebusreceivedmessage argument and the workaround solution is to simply perform this context flip manually within the batch processor csharp foreach var message in messages using var activity new activity servicebusprocessor processmessage preserve reference to the batch activity optional activity addbaggage batchactivityid activity current id use incoming diagnostic id if present if message applicationproperties trygetvalue diagnostic id out var value value is string diagnosticid activitycontext tryparse diagnosticid null out var parentcontext activity setparentid parentcontext traceid parentcontext spanid parentcontext traceflags activity start dowork message i guess my main question at this point is whether or not this would be the suggested approach or whether there s another way of implementing a batch triggered function such that the trace ids are registered as i would expect them to be per message the documentation i could find on this subject is rather limited cc joshlove msft environment net sdk | 0 |
112,384 | 14,243,852,699 | IssuesEvent | 2020-11-19 05:35:06 | ppy/osu-web | https://api.github.com/repos/ppy/osu-web | closed | Forum reply box on mobile catch-all issue | area:forum platform:mobile type:design type:ux | This is a catch-all summary issue for all the issues with the forum reply box (originally https://github.com/ppy/osu-web/issues/2138#issuecomment-460536581):
Replying while on a mobile device seems pretty broken in general with different combinations of:
- not being able to unpin the reply box because the button doesn't fit on the screen. #4270
- on-screen keyboard can cause the page to only use the top half of the screen.
- pinned reply box can block entire view. #4271
- unpinning causes the reply box to be deselected which makes the on-screen keyboard go away (and then tapping in the reply box causes it to get pinned and the on-screen keyboard comes up and pushes everything up and we go into a loop of fail) #2138
| 1.0 | Forum reply box on mobile catch-all issue - This is a catch-all summary issue for all the issues with the forum reply box (originally https://github.com/ppy/osu-web/issues/2138#issuecomment-460536581):
Replying while on a mobile device seems pretty broken in general with different combinations of:
- not being able to unpin the reply box because the button doesn't fit on the screen. #4270
- on-screen keyboard can cause the page to only use the top half of the screen.
- pinned reply box can block entire view. #4271
- unpinning causes the reply box to be deselected which makes the on-screen keyboard go away (and then tapping in the reply box causes it to get pinned and the on-screen keyboard comes up and pushes everything up and we go into a loop of fail) #2138
| non_priority | forum reply box on mobile catch all issue this is a catch all summary issue for all the issues with the forum reply box originally replying while on a mobile device seems pretty broken in general with different combinations of not being able to unpin the reply box because the button doesn t fit on the screen on screen keyboard can cause the page to only use the top half of the screen pinned reply box can block entire view unpinning causes the reply box to be deselected which makes the on screen keyboard go away and then tapping in the reply box causes it to get pinned and the on screen keyboard comes up and pushes everything up and we go into a loop of fail | 0 |
224,434 | 17,187,674,888 | IssuesEvent | 2021-07-16 06:10:05 | captaincobbs/ESG-Mod | https://api.github.com/repos/captaincobbs/ESG-Mod | opened | Fix vanilla bug with minor civ ship spawns | bug in testing needs documentation | For certain types and stress levels of minors, the "endless" fleets were weaker than the middle-difficulty fleets; these have been reorganized into the proper order | 1.0 | Fix vanilla bug with minor civ ship spawns - For certain types and stress levels of minors, the "endless" fleets were weaker than the middle-difficulty fleets; these have been reorganized into the proper order | non_priority | fix vanilla bug with minor civ ship spawns for certain types and stress levels of minors the endless fleets were weaker than the middle difficulty fleets these have been reorganized into the proper order | 0 |
400,286 | 11,771,859,598 | IssuesEvent | 2020-03-16 01:46:45 | AY1920S2-CS2103-W14-3/main | https://api.github.com/repos/AY1920S2-CS2103-W14-3/main | closed | As a busy university student I want to be reminded of my friend's birthdays as and when they are approaching | priority.High type.Story | so that I do not need to memorise all my friend's birthdays but will still be able to celebrate it for them. | 1.0 | As a busy university student I want to be reminded of my friend's birthdays as and when they are approaching - so that I do not need to memorise all my friend's birthdays but will still be able to celebrate it for them. | priority | as a busy university student i want to be reminded of my friend s birthdays as and when they are approaching so that i do not need to memorise all my friend s birthdays but will still be able to celebrate it for them | 1 |
437,083 | 12,560,080,620 | IssuesEvent | 2020-06-07 20:58:31 | Tyresius92/le-chat | https://api.github.com/repos/Tyresius92/le-chat | closed | Set up Continuous Integration | Priority: High Status: Ready for Review Type: Enhancement/Feature Type: Maintenance | I've used both CircleCI and TravisCI. I have a slight preference for CircleCI.
I'm going to hold off on setting up the integration for a couple more days, to give folks time to object to using CircleCI if they don't want to use that thing. | 1.0 | Set up Continuous Integration - I've used both CircleCI and TravisCI. I have a slight preference for CircleCI.
I'm going to hold off on setting up the integration for a couple more days, to give folks time to object to using CircleCI if they don't want to use that thing. | priority | set up continuous integration i ve used both circleci and travisci i have a slight preference for circleci i m going to hold off on setting up the integration for a couple more days to give folks time to object to using circleci if they don t want to use that thing | 1 |
491,631 | 14,167,766,050 | IssuesEvent | 2020-11-12 10:44:56 | webcompat/web-bugs | https://api.github.com/repos/webcompat/web-bugs | closed | www.bing.com - see bug description | browser-fenix engine-gecko priority-critical | <!-- @browser: Firefox Mobile 83.0 -->
<!-- @ua_header: Mozilla/5.0 (Android 9; Mobile; rv:83.0) Gecko/83.0 Firefox/83.0 -->
<!-- @reported_with: android-components-reporter -->
<!-- @public_url: https://github.com/webcompat/web-bugs/issues/61577 -->
<!-- @extra_labels: browser-fenix -->
**URL**: https://www.bing.com/images/search?view=detailV2&ccid=9G5zLyO5&id=03FEE12728A346A3611AF21658E133FF60A41552&thid=OIP.9G5zLyO5d3Rltu4CDC_vNgHaDl&mediaurl=https%3A%2F%2Ffcw.com%2F~%2Fmedia%2FGIG%2FEDIT_SHARED%2FNetworks%2Fglobalnetwork.png&exph=368&expw=760&q=global&simid=608047350916057475&ck=8B7DEB62D566D3A461BEBAFBED9F9518&selectedindex=10&form=IRPRST&pc=MOZB&ajaxhist=0&vt=4&sim=11
**Browser / Version**: Firefox Mobile 83.0
**Operating System**: Android
**Tested Another Browser**: Yes Opera
**Problem type**: Something else
**Description**: stutter on scrolling images that open on clicking image in Bing..
**Steps to Reproduce**:
Choppy scrolling on Bing images. On the new window that opens up when selecting an image..
<details>
<summary>View the screenshot</summary>
<img alt="Screenshot" src="https://webcompat.com/uploads/2020/11/3478c54b-3d74-4c92-9ada-555e41c539fe.jpeg">
</details>
<details>
<summary>Browser Configuration</summary>
<ul>
<li>gfx.webrender.all: false</li><li>gfx.webrender.blob-images: true</li><li>gfx.webrender.enabled: false</li><li>image.mem.shared: true</li><li>buildID: 20201108174701</li><li>channel: beta</li><li>hasTouchScreen: true</li><li>mixed active content blocked: false</li><li>mixed passive content blocked: false</li><li>tracking content blocked: false</li>
</ul>
</details>
[View console log messages](https://webcompat.com/console_logs/2020/11/e39f3282-7d00-4b9d-8fb1-4fe25160f9e1)
_From [webcompat.com](https://webcompat.com/) with ❤️_ | 1.0 | www.bing.com - see bug description - <!-- @browser: Firefox Mobile 83.0 -->
<!-- @ua_header: Mozilla/5.0 (Android 9; Mobile; rv:83.0) Gecko/83.0 Firefox/83.0 -->
<!-- @reported_with: android-components-reporter -->
<!-- @public_url: https://github.com/webcompat/web-bugs/issues/61577 -->
<!-- @extra_labels: browser-fenix -->
**URL**: https://www.bing.com/images/search?view=detailV2&ccid=9G5zLyO5&id=03FEE12728A346A3611AF21658E133FF60A41552&thid=OIP.9G5zLyO5d3Rltu4CDC_vNgHaDl&mediaurl=https%3A%2F%2Ffcw.com%2F~%2Fmedia%2FGIG%2FEDIT_SHARED%2FNetworks%2Fglobalnetwork.png&exph=368&expw=760&q=global&simid=608047350916057475&ck=8B7DEB62D566D3A461BEBAFBED9F9518&selectedindex=10&form=IRPRST&pc=MOZB&ajaxhist=0&vt=4&sim=11
**Browser / Version**: Firefox Mobile 83.0
**Operating System**: Android
**Tested Another Browser**: Yes Opera
**Problem type**: Something else
**Description**: stutter on scrolling images that open on clicking image in Bing..
**Steps to Reproduce**:
Choppy scrolling on Bing images. On the new window that opens up when selecting an image..
<details>
<summary>View the screenshot</summary>
<img alt="Screenshot" src="https://webcompat.com/uploads/2020/11/3478c54b-3d74-4c92-9ada-555e41c539fe.jpeg">
</details>
<details>
<summary>Browser Configuration</summary>
<ul>
<li>gfx.webrender.all: false</li><li>gfx.webrender.blob-images: true</li><li>gfx.webrender.enabled: false</li><li>image.mem.shared: true</li><li>buildID: 20201108174701</li><li>channel: beta</li><li>hasTouchScreen: true</li><li>mixed active content blocked: false</li><li>mixed passive content blocked: false</li><li>tracking content blocked: false</li>
</ul>
</details>
[View console log messages](https://webcompat.com/console_logs/2020/11/e39f3282-7d00-4b9d-8fb1-4fe25160f9e1)
_From [webcompat.com](https://webcompat.com/) with ❤️_ | priority | see bug description url browser version firefox mobile operating system android tested another browser yes opera problem type something else description stutter on scrolling images that open on clicking image in bing steps to reproduce choppy scrolling on bing images on the new window that opens up when selecting an image view the screenshot img alt screenshot src browser configuration gfx webrender all false gfx webrender blob images true gfx webrender enabled false image mem shared true buildid channel beta hastouchscreen true mixed active content blocked false mixed passive content blocked false tracking content blocked false from with ❤️ | 1 |
522,075 | 15,148,372,668 | IssuesEvent | 2021-02-11 10:31:03 | duncanpeacock/fragalysis-backend | https://api.github.com/repos/duncanpeacock/fragalysis-backend | closed | WP1 Hypothesis Capture – Action Capture - Phase 1 delivery | High Priority enhancement | #### Description
Once POC is finalised, revise design / database schema / api calls as necessary to agree first stable production version and revise future roadmap. Implement this version of code / database migrations.
#### Deliverable
Phase 1 Code and database delivery
Parent: (https://github.com/xchem/fragalysis-backend/issues/197) | 1.0 | WP1 Hypothesis Capture – Action Capture - Phase 1 delivery - #### Description
Once POC is finalised, revise design / database schema / api calls as necessary to agree first stable production version and revise future roadmap. Implement this version of code / database migrations.
#### Deliverable
Phase 1 Code and database delivery
Parent: (https://github.com/xchem/fragalysis-backend/issues/197) | priority | hypothesis capture – action capture phase delivery description once poc is finalised revise design database schema api calls as necessary to agree first stable production version and revise future roadmap implement this version of code database migrations deliverable phase code and database delivery parent | 1 |
222,142 | 7,428,561,119 | IssuesEvent | 2018-03-24 03:03:14 | TrustWallet/trust-wallet-ios | https://api.github.com/repos/TrustWallet/trust-wallet-ios | closed | DApp bookmarks crashes on master | bug critical priority dapp | The app crashes when trying to open bookmarks. @VKoskiv can you take a look?
<sub>Sent with <a href="http://githawk.com">GitHawk</a></sub> | 1.0 | DApp bookmarks crashes on master - The app crashes when trying to open bookmarks. @VKoskiv can you take a look?
<sub>Sent with <a href="http://githawk.com">GitHawk</a></sub> | priority | dapp bookmarks crashes on master the app crashes when trying to open bookmarks vkoskiv can you take a look sent with a href | 1 |
172,967 | 13,368,910,440 | IssuesEvent | 2020-09-01 08:03:27 | tgstation/tgstation | https://api.github.com/repos/tgstation/tgstation | closed | Using the swap equipment hotkey lets you carry things in suit storage you shouldn't be able to | Bug Tested/Reproduced | ## Round ID:
reproduced on a local on the latest master, but did it in 143425
## Reproduction:
Using the swap equipment hotkey on a suit (harduits, eva suits, labcoats, aprons, etc) doesn't drop the item from suit storage, allowing you to carry things in suit storage you shouldn't be able to
here's a labcoat carrying a plant bag (which it can't normally)
here's an apron carrying a health analyzer (which it can't normally)
here I had a hardsuit on with a tank in the suit storage, quickswapped to a labcoat and the tank remained in the labcoat's suit storage slot + was usable (it also glitched out my jumpsuit sprite and made it invisible)
to reproduce:
- Wear an armor/suit with something in its suit storage
- quick swap hotkey to another armor/suit
- the item stays in the suit storage/doesn't drop | 1.0 | Using the swap equipment hotkey lets you carry things in suit storage you shouldn't be able to - ## Round ID:
reproduced on a local on the latest master, but did it in 143425
## Reproduction:
Using the swap equipment hotkey on a suit (harduits, eva suits, labcoats, aprons, etc) doesn't drop the item from suit storage, allowing you to carry things in suit storage you shouldn't be able to
here's a labcoat carrying a plant bag (which it can't normally)
here's an apron carrying a health analyzer (which it can't normally)
here I had a hardsuit on with a tank in the suit storage, quickswapped to a labcoat and the tank remained in the labcoat's suit storage slot + was usable (it also glitched out my jumpsuit sprite and made it invisible)
to reproduce:
- Wear an armor/suit with something in its suit storage
- quick swap hotkey to another armor/suit
- the item stays in the suit storage/doesn't drop | non_priority | using the swap equipment hotkey lets you carry things in suit storage you shouldn t be able to round id reproduced on a local on the latest master but did it in reproduction using the swap equipment hotkey on a suit harduits eva suits labcoats aprons etc doesn t drop the item from suit storage allowing you to carry things in suit storage you shouldn t be able to here s a labcoat carrying a plant bag which it can t normally here s an apron carrying a health analyzer which it can t normally here i had a hardsuit on with a tank in the suit storage quickswapped to a labcoat and the tank remained in the labcoat s suit storage slot was usable it also glitched out my jumpsuit sprite and made it invisible to reproduce wear an armor suit with something in its suit storage quick swap hotkey to another armor suit the item stays in the suit storage doesn t drop | 0 |
59,191 | 11,948,446,708 | IssuesEvent | 2020-04-03 11:53:04 | joomla/joomla-cms | https://api.github.com/repos/joomla/joomla-cms | closed | [4.0] restful curl result {"errors":[{"title":"Forbidden"}]} | No Code Attached Yet | ### Steps to reproduce the issue
install joomla 4
enable plugin API Authentication - Basic Auth
and try to get something with curl (https://docs.joomla.org/J4.x:Joomla_Core_APIs)
open msdos
curl -X GET https://{dnsname}/j4/api/index.php/v1/banners --user user_name:password
### Expected result
json with the list of elements (banners, articles, ...)
### Actual result
{"errors":[{"title":"Forbidden"}]}
### System information (as much as possible)
joomla 4 alpha 12
### Additional comments
| 1.0 | [4.0] restful curl result {"errors":[{"title":"Forbidden"}]} - ### Steps to reproduce the issue
install joomla 4
enable plugin API Authentication - Basic Auth
and try to get something with curl (https://docs.joomla.org/J4.x:Joomla_Core_APIs)
open msdos
curl -X GET https://{dnsname}/j4/api/index.php/v1/banners --user user_name:password
### Expected result
json with the list of elements (banners, articles, ...)
### Actual result
{"errors":[{"title":"Forbidden"}]}
### System information (as much as possible)
joomla 4 alpha 12
### Additional comments
| non_priority | restful curl result errors steps to reproduce the issue install joomla enable plugin api authentication basic auth and try to get something with curl open msdos curl x get user user name password expected result json with the list of elements banners articles actual result errors system information as much as possible joomla alpha additional comments | 0 |
257,938 | 27,563,834,811 | IssuesEvent | 2023-03-08 01:09:53 | LynRodWS/alcor | https://api.github.com/repos/LynRodWS/alcor | opened | CVE-2022-3509 (High) detected in protobuf-java-3.8.0.jar | security vulnerability | ## CVE-2022-3509 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>protobuf-java-3.8.0.jar</b></p></summary>
<p>Core Protocol Buffers library. Protocol Buffers are a way of encoding structured data in an
efficient yet extensible format.</p>
<p>Library home page: <a href="https://developers.google.com/protocol-buffers/">https://developers.google.com/protocol-buffers/</a></p>
<p>Path to dependency file: /services/network_acl_manager/pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/com/google/protobuf/protobuf-java/3.8.0/protobuf-java-3.8.0.jar,/canner/.m2/repository/com/google/protobuf/protobuf-java/3.8.0/protobuf-java-3.8.0.jar,/home/wss-scanner/.m2/repository/com/google/protobuf/protobuf-java/3.8.0/protobuf-java-3.8.0.jar,/canner/.m2/repository/com/google/protobuf/protobuf-java/3.8.0/protobuf-java-3.8.0.jar,/home/wss-scanner/.m2/repository/com/google/protobuf/protobuf-java/3.8.0/protobuf-java-3.8.0.jar,/home/wss-scanner/.m2/repository/com/google/protobuf/protobuf-java/3.8.0/protobuf-java-3.8.0.jar,/home/wss-scanner/.m2/repository/com/google/protobuf/protobuf-java/3.8.0/protobuf-java-3.8.0.jar,/home/wss-scanner/.m2/repository/com/google/protobuf/protobuf-java/3.8.0/protobuf-java-3.8.0.jar,/home/wss-scanner/.m2/repository/com/google/protobuf/protobuf-java/3.8.0/protobuf-java-3.8.0.jar,/home/wss-scanner/.m2/repository/com/google/protobuf/protobuf-java/3.8.0/protobuf-java-3.8.0.jar,/home/wss-scanner/.m2/repository/com/google/protobuf/protobuf-java/3.8.0/protobuf-java-3.8.0.jar,/home/wss-scanner/.m2/repository/com/google/protobuf/protobuf-java/3.8.0/protobuf-java-3.8.0.jar,/home/wss-scanner/.m2/repository/com/google/protobuf/protobuf-java/3.8.0/protobuf-java-3.8.0.jar,/home/wss-scanner/.m2/repository/com/google/protobuf/protobuf-java/3.8.0/protobuf-java-3.8.0.jar,/home/wss-scanner/.m2/repository/com/google/protobuf/protobuf-java/3.8.0/protobuf-java-3.8.0.jar,/home/wss-scanner/.m2/repository/com/google/protobuf/protobuf-java/3.8.0/protobuf-java-3.8.0.jar,/home/wss-scanner/.m2/repository/com/google/protobuf/protobuf-java/3.8.0/protobuf-java-3.8.0.jar,/home/wss-scanner/.m2/repository/com/google/protobuf/protobuf-java/3.8.0/protobuf-java-3.8.0.jar</p>
<p>
Dependency Hierarchy:
- :x: **protobuf-java-3.8.0.jar** (Vulnerable Library)
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
A parsing issue similar to CVE-2022-3171, but with textformat in protobuf-java core and lite versions prior to 3.21.7, 3.20.3, 3.19.6 and 3.16.3 can lead to a denial of service attack. Inputs containing multiple instances of non-repeated embedded messages with repeated or unknown fields causes objects to be converted back-n-forth between mutable and immutable forms, resulting in potentially long garbage collection pauses. We recommend updating to the versions mentioned above.
<p>Publish Date: 2022-12-12
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-3509>CVE-2022-3509</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-3509">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-3509</a></p>
<p>Release Date: 2022-12-12</p>
<p>Fix Resolution: 3.16.3</p>
</p>
</details>
<p></p>
***
:rescue_worker_helmet: Automatic Remediation is available for this issue | True | CVE-2022-3509 (High) detected in protobuf-java-3.8.0.jar - ## CVE-2022-3509 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>protobuf-java-3.8.0.jar</b></p></summary>
<p>Core Protocol Buffers library. Protocol Buffers are a way of encoding structured data in an
efficient yet extensible format.</p>
<p>Library home page: <a href="https://developers.google.com/protocol-buffers/">https://developers.google.com/protocol-buffers/</a></p>
<p>Path to dependency file: /services/network_acl_manager/pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/com/google/protobuf/protobuf-java/3.8.0/protobuf-java-3.8.0.jar,/canner/.m2/repository/com/google/protobuf/protobuf-java/3.8.0/protobuf-java-3.8.0.jar,/home/wss-scanner/.m2/repository/com/google/protobuf/protobuf-java/3.8.0/protobuf-java-3.8.0.jar,/canner/.m2/repository/com/google/protobuf/protobuf-java/3.8.0/protobuf-java-3.8.0.jar,/home/wss-scanner/.m2/repository/com/google/protobuf/protobuf-java/3.8.0/protobuf-java-3.8.0.jar,/home/wss-scanner/.m2/repository/com/google/protobuf/protobuf-java/3.8.0/protobuf-java-3.8.0.jar,/home/wss-scanner/.m2/repository/com/google/protobuf/protobuf-java/3.8.0/protobuf-java-3.8.0.jar,/home/wss-scanner/.m2/repository/com/google/protobuf/protobuf-java/3.8.0/protobuf-java-3.8.0.jar,/home/wss-scanner/.m2/repository/com/google/protobuf/protobuf-java/3.8.0/protobuf-java-3.8.0.jar,/home/wss-scanner/.m2/repository/com/google/protobuf/protobuf-java/3.8.0/protobuf-java-3.8.0.jar,/home/wss-scanner/.m2/repository/com/google/protobuf/protobuf-java/3.8.0/protobuf-java-3.8.0.jar,/home/wss-scanner/.m2/repository/com/google/protobuf/protobuf-java/3.8.0/protobuf-java-3.8.0.jar,/home/wss-scanner/.m2/repository/com/google/protobuf/protobuf-java/3.8.0/protobuf-java-3.8.0.jar,/home/wss-scanner/.m2/repository/com/google/protobuf/protobuf-java/3.8.0/protobuf-java-3.8.0.jar,/home/wss-scanner/.m2/repository/com/google/protobuf/protobuf-java/3.8.0/protobuf-java-3.8.0.jar,/home/wss-scanner/.m2/repository/com/google/protobuf/protobuf-java/3.8.0/protobuf-java-3.8.0.jar,/home/wss-scanner/.m2/repository/com/google/protobuf/protobuf-java/3.8.0/protobuf-java-3.8.0.jar,/home/wss-scanner/.m2/repository/com/google/protobuf/protobuf-java/3.8.0/protobuf-java-3.8.0.jar</p>
<p>
Dependency Hierarchy:
- :x: **protobuf-java-3.8.0.jar** (Vulnerable Library)
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
A parsing issue similar to CVE-2022-3171, but with textformat in protobuf-java core and lite versions prior to 3.21.7, 3.20.3, 3.19.6 and 3.16.3 can lead to a denial of service attack. Inputs containing multiple instances of non-repeated embedded messages with repeated or unknown fields causes objects to be converted back-n-forth between mutable and immutable forms, resulting in potentially long garbage collection pauses. We recommend updating to the versions mentioned above.
<p>Publish Date: 2022-12-12
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-3509>CVE-2022-3509</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-3509">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-3509</a></p>
<p>Release Date: 2022-12-12</p>
<p>Fix Resolution: 3.16.3</p>
</p>
</details>
<p></p>
***
:rescue_worker_helmet: Automatic Remediation is available for this issue | non_priority | cve high detected in protobuf java jar cve high severity vulnerability vulnerable library protobuf java jar core protocol buffers library protocol buffers are a way of encoding structured data in an efficient yet extensible format library home page a href path to dependency file services network acl manager pom xml path to vulnerable library home wss scanner repository com google protobuf protobuf java protobuf java jar canner repository com google protobuf protobuf java protobuf java jar home wss scanner repository com google protobuf protobuf java protobuf java jar canner repository com google protobuf protobuf java protobuf java jar home wss scanner repository com google protobuf protobuf java protobuf java jar home wss scanner repository com google protobuf protobuf java protobuf java jar home wss scanner repository com google protobuf protobuf java protobuf java jar home wss scanner repository com google protobuf protobuf java protobuf java jar home wss scanner repository com google protobuf protobuf java protobuf java jar home wss scanner repository com google protobuf protobuf java protobuf java jar home wss scanner repository com google protobuf protobuf java protobuf java jar home wss scanner repository com google protobuf protobuf java protobuf java jar home wss scanner repository com google protobuf protobuf java protobuf java jar home wss scanner repository com google protobuf protobuf java protobuf java jar home wss scanner repository com google protobuf protobuf java protobuf java jar home wss scanner repository com google protobuf protobuf java protobuf java jar home wss scanner repository com google protobuf protobuf java protobuf java jar home wss scanner repository com google protobuf protobuf java protobuf java jar dependency hierarchy x protobuf java jar vulnerable library found in base branch master vulnerability details a parsing issue similar to cve but with textformat in protobuf java core and lite versions prior to and can lead to a denial of service attack inputs containing multiple instances of non repeated embedded messages with repeated or unknown fields causes objects to be converted back n forth between mutable and immutable forms resulting in potentially long garbage collection pauses we recommend updating to the versions mentioned above 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 rescue worker helmet automatic remediation is available for this issue | 0 |
373,595 | 11,045,923,931 | IssuesEvent | 2019-12-09 15:57:16 | edvinnn/Green-Power | https://api.github.com/repos/edvinnn/Green-Power | closed | Keep the current prosumer consumption somewhat more constant | Priority medium good first issue | I think that the consumption fluctuates a bit to much right now :) | 1.0 | Keep the current prosumer consumption somewhat more constant - I think that the consumption fluctuates a bit to much right now :) | priority | keep the current prosumer consumption somewhat more constant i think that the consumption fluctuates a bit to much right now | 1 |
380,791 | 11,271,019,951 | IssuesEvent | 2020-01-14 12:09:26 | googleapis/nodejs-containeranalysis | https://api.github.com/repos/googleapis/nodejs-containeranalysis | opened | Synthesis failed for nodejs-containeranalysis | autosynth failure priority: p1 type: bug | Hello! Autosynth couldn't regenerate nodejs-containeranalysis. :broken_heart:
Here's the output from running `synth.py`:
```
Cloning into 'working_repo'...
Switched to branch 'autosynth'
Traceback (most recent call last):
File "/home/kbuilder/.pyenv/versions/3.6.1/lib/python3.6/runpy.py", line 193, in _run_module_as_main
"__main__", mod_spec)
File "/home/kbuilder/.pyenv/versions/3.6.1/lib/python3.6/runpy.py", line 85, in _run_code
exec(code, run_globals)
File "/tmpfs/src/git/autosynth/autosynth/synth.py", line 256, in <module>
main()
File "/tmpfs/src/git/autosynth/autosynth/synth.py", line 196, in main
last_synth_commit_hash = get_last_metadata_commit(args.metadata_path)
File "/tmpfs/src/git/autosynth/autosynth/synth.py", line 149, in get_last_metadata_commit
text=True,
File "/home/kbuilder/.pyenv/versions/3.6.1/lib/python3.6/subprocess.py", line 403, in run
with Popen(*popenargs, **kwargs) as process:
TypeError: __init__() got an unexpected keyword argument 'text'
```
Google internal developers can see the full log [here](https://sponge/c9a67de3-2540-4828-a553-47aa5fbae976).
| 1.0 | Synthesis failed for nodejs-containeranalysis - Hello! Autosynth couldn't regenerate nodejs-containeranalysis. :broken_heart:
Here's the output from running `synth.py`:
```
Cloning into 'working_repo'...
Switched to branch 'autosynth'
Traceback (most recent call last):
File "/home/kbuilder/.pyenv/versions/3.6.1/lib/python3.6/runpy.py", line 193, in _run_module_as_main
"__main__", mod_spec)
File "/home/kbuilder/.pyenv/versions/3.6.1/lib/python3.6/runpy.py", line 85, in _run_code
exec(code, run_globals)
File "/tmpfs/src/git/autosynth/autosynth/synth.py", line 256, in <module>
main()
File "/tmpfs/src/git/autosynth/autosynth/synth.py", line 196, in main
last_synth_commit_hash = get_last_metadata_commit(args.metadata_path)
File "/tmpfs/src/git/autosynth/autosynth/synth.py", line 149, in get_last_metadata_commit
text=True,
File "/home/kbuilder/.pyenv/versions/3.6.1/lib/python3.6/subprocess.py", line 403, in run
with Popen(*popenargs, **kwargs) as process:
TypeError: __init__() got an unexpected keyword argument 'text'
```
Google internal developers can see the full log [here](https://sponge/c9a67de3-2540-4828-a553-47aa5fbae976).
| priority | synthesis failed for nodejs containeranalysis hello autosynth couldn t regenerate nodejs containeranalysis broken heart here s the output from running synth py cloning into working repo switched to branch autosynth traceback most recent call last file home kbuilder pyenv versions lib runpy py line in run module as main main mod spec file home kbuilder pyenv versions lib runpy py line in run code exec code run globals file tmpfs src git autosynth autosynth synth py line in main file tmpfs src git autosynth autosynth synth py line in main last synth commit hash get last metadata commit args metadata path file tmpfs src git autosynth autosynth synth py line in get last metadata commit text true file home kbuilder pyenv versions lib subprocess py line in run with popen popenargs kwargs as process typeerror init got an unexpected keyword argument text google internal developers can see the full log | 1 |
107,532 | 4,310,159,351 | IssuesEvent | 2016-07-21 18:18:09 | dhowe/AdNauseam | https://api.github.com/repos/dhowe/AdNauseam | closed | Bug in CSS on homepage (gh-pages) | Bug PRIORITY: High | see commit cf90c3e0ff8cc368c96
also, see #291
<img width="632" alt="screen shot 2016-07-19 at 12 37 47 pm" src="https://cloud.githubusercontent.com/assets/737638/16959124/765ad5a4-4db1-11e6-8241-2f21c3609c66.png">
| 1.0 | Bug in CSS on homepage (gh-pages) - see commit cf90c3e0ff8cc368c96
also, see #291
<img width="632" alt="screen shot 2016-07-19 at 12 37 47 pm" src="https://cloud.githubusercontent.com/assets/737638/16959124/765ad5a4-4db1-11e6-8241-2f21c3609c66.png">
| priority | bug in css on homepage gh pages see commit also see img width alt screen shot at pm src | 1 |
45,852 | 9,819,400,210 | IssuesEvent | 2019-06-13 21:54:02 | certbot/certbot | https://api.github.com/repos/certbot/certbot | closed | Dedupe the Apache and Nginx plugins | area: code health area: refactoring needs-update | The Nginx plugin was modeled very closely after the Apache plugin. Recently our linter started complaining about duplicated code and we fixed it with a hack (see #3881). We should actually fix this.
How best to do this depends a lot on what's actually duplicated and I haven't looked into it closely. One potential option is to make a class that installers can derive from to help them with reverter usage. This may help future plugin authors as well. | 1.0 | Dedupe the Apache and Nginx plugins - The Nginx plugin was modeled very closely after the Apache plugin. Recently our linter started complaining about duplicated code and we fixed it with a hack (see #3881). We should actually fix this.
How best to do this depends a lot on what's actually duplicated and I haven't looked into it closely. One potential option is to make a class that installers can derive from to help them with reverter usage. This may help future plugin authors as well. | non_priority | dedupe the apache and nginx plugins the nginx plugin was modeled very closely after the apache plugin recently our linter started complaining about duplicated code and we fixed it with a hack see we should actually fix this how best to do this depends a lot on what s actually duplicated and i haven t looked into it closely one potential option is to make a class that installers can derive from to help them with reverter usage this may help future plugin authors as well | 0 |
44,397 | 2,904,557,884 | IssuesEvent | 2015-06-18 18:47:58 | openshift/origin | https://api.github.com/repos/openshift/origin | closed | "osc get all" doesn't prefix elements | area/usability component/cli priority/P3 | ```
[joe@ose3-master beta4]$ osc get all
NAME TYPE SOURCE
NAME TYPE STATUS POD
NAME DOCKER REPO TAGS UPDATED
NAME TRIGGERS LATEST VERSION
CONTROLLER CONTAINER(S) IMAGE(S) SELECTOR REPLICAS
NAME HOST/PORT PATH SERVICE LABELS
hello-openshift-route hello-openshift.cloudapps.example.com hello-openshift-service
NAME LABELS SELECTOR IP(S) PORT(S)
hello-openshift-service <none> name=hello-openshift 172.30.197.132 27017/TCP
POD IP CONTAINER(S) IMAGE(S) HOST LABELS STATUS CREATED MESSAGE
hello-openshift 10.1.1.2 ose3-node1.example.com/192.168.133.3 name=hello-openshift Running About a minute
hello-openshift openshift/hello-openshift:v0.4.3
```
Each set of resources should be prefixed by its type. For example:
````
Routes
NAME HOST/PORT PATH SERVICE LABELS
hello-openshift-route hello-openshift.cloudapps.example.com hello-openshift-service
```
```
[joe@ose3-master beta4]$ osc version
osc v0.5.2.2-18-gbf80a71
kubernetes v0.17.1-804-g496be63
``` | 1.0 | "osc get all" doesn't prefix elements - ```
[joe@ose3-master beta4]$ osc get all
NAME TYPE SOURCE
NAME TYPE STATUS POD
NAME DOCKER REPO TAGS UPDATED
NAME TRIGGERS LATEST VERSION
CONTROLLER CONTAINER(S) IMAGE(S) SELECTOR REPLICAS
NAME HOST/PORT PATH SERVICE LABELS
hello-openshift-route hello-openshift.cloudapps.example.com hello-openshift-service
NAME LABELS SELECTOR IP(S) PORT(S)
hello-openshift-service <none> name=hello-openshift 172.30.197.132 27017/TCP
POD IP CONTAINER(S) IMAGE(S) HOST LABELS STATUS CREATED MESSAGE
hello-openshift 10.1.1.2 ose3-node1.example.com/192.168.133.3 name=hello-openshift Running About a minute
hello-openshift openshift/hello-openshift:v0.4.3
```
Each set of resources should be prefixed by its type. For example:
````
Routes
NAME HOST/PORT PATH SERVICE LABELS
hello-openshift-route hello-openshift.cloudapps.example.com hello-openshift-service
```
```
[joe@ose3-master beta4]$ osc version
osc v0.5.2.2-18-gbf80a71
kubernetes v0.17.1-804-g496be63
``` | priority | osc get all doesn t prefix elements osc get all name type source name type status pod name docker repo tags updated name triggers latest version controller container s image s selector replicas name host port path service labels hello openshift route hello openshift cloudapps example com hello openshift service name labels selector ip s port s hello openshift service name hello openshift tcp pod ip container s image s host labels status created message hello openshift example com name hello openshift running about a minute hello openshift openshift hello openshift each set of resources should be prefixed by its type for example routes name host port path service labels hello openshift route hello openshift cloudapps example com hello openshift service osc version osc kubernetes | 1 |
776,660 | 27,264,532,694 | IssuesEvent | 2023-02-22 17:02:08 | ascheid/itsg33-pbmm-issue-gen | https://api.github.com/repos/ascheid/itsg33-pbmm-issue-gen | opened | CM-5(6): Access Restrictions For Change | Limit Library Privileges | Priority: P2 Suggested Assignment: IT Security Function ITSG-33 Class: Operational Control: CM-5 | # Control Definition
ACCESS RESTRICTIONS FOR CHANGE | LIMIT LIBRARY PRIVILEGES
The organization limits privileges to change software resident within software libraries.
Supplemental Guidance: Software libraries include privileged programs. Related control: AC-2.
# Class
Operational
# Suggested Assignment
IT Security Function
# Support Teams
IT Operations Group, IT Projects
| 1.0 | CM-5(6): Access Restrictions For Change | Limit Library Privileges - # Control Definition
ACCESS RESTRICTIONS FOR CHANGE | LIMIT LIBRARY PRIVILEGES
The organization limits privileges to change software resident within software libraries.
Supplemental Guidance: Software libraries include privileged programs. Related control: AC-2.
# Class
Operational
# Suggested Assignment
IT Security Function
# Support Teams
IT Operations Group, IT Projects
| priority | cm access restrictions for change limit library privileges control definition access restrictions for change limit library privileges the organization limits privileges to change software resident within software libraries supplemental guidance software libraries include privileged programs related control ac class operational suggested assignment it security function support teams it operations group it projects | 1 |
736,166 | 25,460,782,057 | IssuesEvent | 2022-11-24 18:42:00 | TalaoDAO/AltMe | https://api.github.com/repos/TalaoDAO/AltMe | closed | Change text screen IA | Priority NO GO | replace "ID document check" by "Real-time photo + ID document check"
position the IA on top of the list
add check box by default select teh IA
add button "Start"
| 1.0 | Change text screen IA - replace "ID document check" by "Real-time photo + ID document check"
position the IA on top of the list
add check box by default select teh IA
add button "Start"
| priority | change text screen ia replace id document check by real time photo id document check position the ia on top of the list add check box by default select teh ia add button start | 1 |
249,623 | 21,180,615,705 | IssuesEvent | 2022-04-08 07:33:04 | milvus-io/milvus | https://api.github.com/repos/milvus-io/milvus | opened | [Bug]: [benchmark][standalone] RpcError: _MultiThreadedRendezvous: StatusCode.DEADLINE_EXCEEDED, Deadline Exceeded | kind/bug needs-triage test/benchmark | ### Is there an existing issue for this?
- [X] I have searched the existing issues
### Environment
```markdown
- Milvus version: master-20220406-1e6f6bd0
- Deployment mode(standalone or cluster): standalone
- SDK version(e.g. pymilvus v2.0.0rc2): 2.1.0.dev18
- OS(Ubuntu or CentOS):
- CPU/Memory:
- GPU:
- Others:
```
### Current Behavior
argo task: benchmark-tag-8fgt5
test yaml:
client-configmap:client-random-locust-100m-ddl-r8-w2
server-configmap:server-single-32c128m
client pod: benchmark-tag-8fgt5-4039138332
client log file: locust_report_2022-04-06_665.log
**A few occasional errors in concurrent interface requests**
client log:
```
[2022-04-06 11:24:35,130] [ ERROR] - grpc RpcError: [_execute_search_requests], <_MultiThreadedRendezvous: StatusCode.DEADLINE_EXCEEDED, Deadline Exceeded>, <Time:{'RPC start': '2022-04-06 11:23:35.129520', 'gRPC error': '2022-04-06 11:24:35.130327'}> (pymilvus.decorators:81)
[2022-04-06 11:24:35,131] [ ERROR] - grpc RpcError: [search], <_MultiThreadedRendezvous: StatusCode.DEADLINE_EXCEEDED, Deadline Exceeded>, <Time:{'RPC start': '2022-04-06 11:23:35.120453', 'gRPC error': '2022-04-06 11:24:35.131520'}> (pymilvus.decorators:81)
[2022-04-06 11:28:35,132] [ ERROR] - grpc RpcError: [query], <_MultiThreadedRendezvous: StatusCode.DEADLINE_EXCEEDED, Deadline Exceeded>, <Time:{'RPC start': '2022-04-06 11:23:35.121605', 'gRPC error': '2022-04-06 11:28:35.132182'}> (pymilvus.decorators:81)
```
server:
```
NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES
benchmark-tag-8fgt5-1-etcd-0 1/1 Running 0 45h 10.97.16.207 qa-node013.zilliz.local <none> <none>
benchmark-tag-8fgt5-1-milvus-standalone-7fbf97888c-57qnp 1/1 Running 0 45h 10.97.17.44 qa-node014.zilliz.local <none> <none>
benchmark-tag-8fgt5-1-minio-6ccb6bb6dc-fbq7x 1/1 Running 0 45h 10.97.19.249 qa-node016.zilliz.local <none> <none>
```
### Expected Behavior
_No response_
### Steps To Reproduce
```markdown
1、create collection
2、create index of ivf_sq8
3、insert 100m million vectors
4、flush collection
5、build index with the same params
6、load collection
7、locust concurrent: query<-search, load, get<-query, scene_test 《- raise error
```
### Anything else?
client-random-locust-100m-ddl-r8-w2:
```
locust_random_performance:
collections:
-
collection_name: sift_100m_128_l2
ni_per: 50000
build_index: true
index_type: ivf_sq8
index_param:
nlist: 2048
task:
types:
-
type: query
weight: 8
params:
top_k: 10
nq: 10
search_param:
nprobe: 16
-
type: load
weight: 1
-
type: get
weight: 8
params:
ids_length: 10
-
type: scene_test
weight: 2
connection_num: 1
clients_num: 20
spawn_rate: 2
during_time: 302400
```
```
@time_wrapper
def scene_test(self, collection_name=None, vectors=None, ids=None):
logger.debug("[scene_test] Start scene test : %s" % collection_name)
self.create_collection(dimension=128, collection_name=collection_name)
time.sleep(1)
collection_info = self.get_info(collection_name)
entities = utils.generate_entities(collection_info, vectors, ids)
logger.debug("[scene_test] Start insert : %s" % collection_name)
self.insert(entities, collection_name=collection_name)
logger.debug("[scene_test] Start flush : %s" % collection_name)
self.flush(collection_name=collection_name)
self.count(collection_name=collection_name)
logger.debug("[scene_test] Start create index : %s" % collection_name)
self.create_index(field_name='float_vector', index_type="ivf_sq8", metric_type='l2',
collection_name=collection_name, index_param={'nlist': 2048})
time.sleep(59)
logger.debug("[scene_test] Start drop : %s" % collection_name)
self.drop(collection_name=collection_name)
logger.debug("[scene_test]Scene test close : %s" % collection_name)
``` | 1.0 | [Bug]: [benchmark][standalone] RpcError: _MultiThreadedRendezvous: StatusCode.DEADLINE_EXCEEDED, Deadline Exceeded - ### Is there an existing issue for this?
- [X] I have searched the existing issues
### Environment
```markdown
- Milvus version: master-20220406-1e6f6bd0
- Deployment mode(standalone or cluster): standalone
- SDK version(e.g. pymilvus v2.0.0rc2): 2.1.0.dev18
- OS(Ubuntu or CentOS):
- CPU/Memory:
- GPU:
- Others:
```
### Current Behavior
argo task: benchmark-tag-8fgt5
test yaml:
client-configmap:client-random-locust-100m-ddl-r8-w2
server-configmap:server-single-32c128m
client pod: benchmark-tag-8fgt5-4039138332
client log file: locust_report_2022-04-06_665.log
**A few occasional errors in concurrent interface requests**
client log:
```
[2022-04-06 11:24:35,130] [ ERROR] - grpc RpcError: [_execute_search_requests], <_MultiThreadedRendezvous: StatusCode.DEADLINE_EXCEEDED, Deadline Exceeded>, <Time:{'RPC start': '2022-04-06 11:23:35.129520', 'gRPC error': '2022-04-06 11:24:35.130327'}> (pymilvus.decorators:81)
[2022-04-06 11:24:35,131] [ ERROR] - grpc RpcError: [search], <_MultiThreadedRendezvous: StatusCode.DEADLINE_EXCEEDED, Deadline Exceeded>, <Time:{'RPC start': '2022-04-06 11:23:35.120453', 'gRPC error': '2022-04-06 11:24:35.131520'}> (pymilvus.decorators:81)
[2022-04-06 11:28:35,132] [ ERROR] - grpc RpcError: [query], <_MultiThreadedRendezvous: StatusCode.DEADLINE_EXCEEDED, Deadline Exceeded>, <Time:{'RPC start': '2022-04-06 11:23:35.121605', 'gRPC error': '2022-04-06 11:28:35.132182'}> (pymilvus.decorators:81)
```
server:
```
NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES
benchmark-tag-8fgt5-1-etcd-0 1/1 Running 0 45h 10.97.16.207 qa-node013.zilliz.local <none> <none>
benchmark-tag-8fgt5-1-milvus-standalone-7fbf97888c-57qnp 1/1 Running 0 45h 10.97.17.44 qa-node014.zilliz.local <none> <none>
benchmark-tag-8fgt5-1-minio-6ccb6bb6dc-fbq7x 1/1 Running 0 45h 10.97.19.249 qa-node016.zilliz.local <none> <none>
```
### Expected Behavior
_No response_
### Steps To Reproduce
```markdown
1、create collection
2、create index of ivf_sq8
3、insert 100m million vectors
4、flush collection
5、build index with the same params
6、load collection
7、locust concurrent: query<-search, load, get<-query, scene_test 《- raise error
```
### Anything else?
client-random-locust-100m-ddl-r8-w2:
```
locust_random_performance:
collections:
-
collection_name: sift_100m_128_l2
ni_per: 50000
build_index: true
index_type: ivf_sq8
index_param:
nlist: 2048
task:
types:
-
type: query
weight: 8
params:
top_k: 10
nq: 10
search_param:
nprobe: 16
-
type: load
weight: 1
-
type: get
weight: 8
params:
ids_length: 10
-
type: scene_test
weight: 2
connection_num: 1
clients_num: 20
spawn_rate: 2
during_time: 302400
```
```
@time_wrapper
def scene_test(self, collection_name=None, vectors=None, ids=None):
logger.debug("[scene_test] Start scene test : %s" % collection_name)
self.create_collection(dimension=128, collection_name=collection_name)
time.sleep(1)
collection_info = self.get_info(collection_name)
entities = utils.generate_entities(collection_info, vectors, ids)
logger.debug("[scene_test] Start insert : %s" % collection_name)
self.insert(entities, collection_name=collection_name)
logger.debug("[scene_test] Start flush : %s" % collection_name)
self.flush(collection_name=collection_name)
self.count(collection_name=collection_name)
logger.debug("[scene_test] Start create index : %s" % collection_name)
self.create_index(field_name='float_vector', index_type="ivf_sq8", metric_type='l2',
collection_name=collection_name, index_param={'nlist': 2048})
time.sleep(59)
logger.debug("[scene_test] Start drop : %s" % collection_name)
self.drop(collection_name=collection_name)
logger.debug("[scene_test]Scene test close : %s" % collection_name)
``` | non_priority | rpcerror multithreadedrendezvous statuscode deadline exceeded deadline exceeded is there an existing issue for this i have searched the existing issues environment markdown milvus version master deployment mode standalone or cluster standalone sdk version e g pymilvus os ubuntu or centos cpu memory gpu others current behavior argo task benchmark tag test yaml client configmap client random locust ddl server configmap server single client pod benchmark tag client log file locust report log a few occasional errors in concurrent interface requests client log grpc rpcerror pymilvus decorators grpc rpcerror pymilvus decorators grpc rpcerror pymilvus decorators server name ready status restarts age ip node nominated node readiness gates benchmark tag etcd running qa zilliz local benchmark tag milvus standalone running qa zilliz local benchmark tag minio running qa zilliz local expected behavior no response steps to reproduce markdown 、create collection 、create index of ivf 、insert million vectors 、flush collection 、build index with the same params 、load collection 、locust concurrent query search load get query scene test 《 raise error anything else client random locust ddl locust random performance collections collection name sift ni per build index true index type ivf index param nlist task types type query weight params top k nq search param nprobe type load weight type get weight params ids length type scene test weight connection num clients num spawn rate during time time wrapper def scene test self collection name none vectors none ids none logger debug start scene test s collection name self create collection dimension collection name collection name time sleep collection info self get info collection name entities utils generate entities collection info vectors ids logger debug start insert s collection name self insert entities collection name collection name logger debug start flush s collection name self flush collection name collection name self count collection name collection name logger debug start create index s collection name self create index field name float vector index type ivf metric type collection name collection name index param nlist time sleep logger debug start drop s collection name self drop collection name collection name logger debug scene test close s collection name | 0 |
85,488 | 7,973,864,182 | IssuesEvent | 2018-07-17 01:48:33 | owncloud/core | https://api.github.com/repos/owncloud/core | opened | Federation acceptance tests should test incoming and outgoing separately | app:federation dev:acceptance-tests | Federation acceptance tests should test permutations like:
- [ ] Incoming only - incoming stuff is accepted, outgoing is not allowed
- [ ] Outgoing only - outgoing stuff is accepted, incoming is not allowed
- [ ] Incoming and outgoing - it all works
- [ ] Neither - no federation shares are allowed
| 1.0 | Federation acceptance tests should test incoming and outgoing separately - Federation acceptance tests should test permutations like:
- [ ] Incoming only - incoming stuff is accepted, outgoing is not allowed
- [ ] Outgoing only - outgoing stuff is accepted, incoming is not allowed
- [ ] Incoming and outgoing - it all works
- [ ] Neither - no federation shares are allowed
| non_priority | federation acceptance tests should test incoming and outgoing separately federation acceptance tests should test permutations like incoming only incoming stuff is accepted outgoing is not allowed outgoing only outgoing stuff is accepted incoming is not allowed incoming and outgoing it all works neither no federation shares are allowed | 0 |
157,474 | 19,957,388,872 | IssuesEvent | 2022-01-28 01:58:59 | faizulho/sanity-gatsby-blog | https://api.github.com/repos/faizulho/sanity-gatsby-blog | opened | CVE-2022-0355 (High) detected in simple-get-4.0.0.tgz | security vulnerability | ## CVE-2022-0355 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>simple-get-4.0.0.tgz</b></p></summary>
<p>Simplest way to make http get requests. Supports HTTPS, redirects, gzip/deflate, streams in < 100 lines.</p>
<p>Library home page: <a href="https://registry.npmjs.org/simple-get/-/simple-get-4.0.0.tgz">https://registry.npmjs.org/simple-get/-/simple-get-4.0.0.tgz</a></p>
<p>Path to dependency file: /studio/package.json</p>
<p>Path to vulnerable library: /studio/node_modules/simple-get/package.json</p>
<p>
Dependency Hierarchy:
- core-2.19.2.tgz (Root Library)
- :x: **simple-get-4.0.0.tgz** (Vulnerable Library)
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
Exposure of Sensitive Information to an Unauthorized Actor in NPM simple-get prior to 4.0.1.
<p>Publish Date: 2022-01-26
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-0355>CVE-2022-0355</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>8.8</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-0355">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-0355</a></p>
<p>Release Date: 2022-01-26</p>
<p>Fix Resolution: simple-get - 4.0.1</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | CVE-2022-0355 (High) detected in simple-get-4.0.0.tgz - ## CVE-2022-0355 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>simple-get-4.0.0.tgz</b></p></summary>
<p>Simplest way to make http get requests. Supports HTTPS, redirects, gzip/deflate, streams in < 100 lines.</p>
<p>Library home page: <a href="https://registry.npmjs.org/simple-get/-/simple-get-4.0.0.tgz">https://registry.npmjs.org/simple-get/-/simple-get-4.0.0.tgz</a></p>
<p>Path to dependency file: /studio/package.json</p>
<p>Path to vulnerable library: /studio/node_modules/simple-get/package.json</p>
<p>
Dependency Hierarchy:
- core-2.19.2.tgz (Root Library)
- :x: **simple-get-4.0.0.tgz** (Vulnerable Library)
<p>Found in base branch: <b>master</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
Exposure of Sensitive Information to an Unauthorized Actor in NPM simple-get prior to 4.0.1.
<p>Publish Date: 2022-01-26
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-0355>CVE-2022-0355</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>8.8</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-0355">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2022-0355</a></p>
<p>Release Date: 2022-01-26</p>
<p>Fix Resolution: simple-get - 4.0.1</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_priority | cve high detected in simple get tgz cve high severity vulnerability vulnerable library simple get tgz simplest way to make http get requests supports https redirects gzip deflate streams in library home page a href path to dependency file studio package json path to vulnerable library studio node modules simple get package json dependency hierarchy core tgz root library x simple get tgz vulnerable library found in base branch master vulnerability details exposure of sensitive information to an unauthorized actor in npm simple get prior to 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 simple get step up your open source security game with whitesource | 0 |
55,843 | 23,616,516,443 | IssuesEvent | 2022-08-24 16:19:33 | BCDevOps/developer-experience | https://api.github.com/repos/BCDevOps/developer-experience | closed | Enable Argo CD for JAG_RBAC | automation ops and shared services app-development | **Describe the issue**
Devise a plan for the management of OCP RBAC in Argo CD for the entire justice ministry using the Warden Operator and the "GitOpsAlliance" resource.
**Additional context**
Because the project sets to be included have multiple ministry IDs, a new label will have to be added to each project set's tools namespace:
`alliance: JAG_RBAC`
Get a list of users that should have access to the Argo CD UI and to the GitHub repo. Incorporate these users into the GitOpsAlliance resource manifest.
The GitOpsAlliance resource will be created in each of these clusters: KLAB, Silver, Gold, and GoldDR.
The plan will be prepared by the Platform Services team and reviewed and approved by JAG. Initial implementation to be done by the Platform Services team, then turned over to JAG for completion.
**Definition of done**
- [x] A plan has been prepared, including repo migration strategy, repo structure, and scope
- [x] The plan has been reviewed and approved by JAG
- [x] Initial setup has been done and instructions provided to JAG for implementation next steps
| 1.0 | Enable Argo CD for JAG_RBAC - **Describe the issue**
Devise a plan for the management of OCP RBAC in Argo CD for the entire justice ministry using the Warden Operator and the "GitOpsAlliance" resource.
**Additional context**
Because the project sets to be included have multiple ministry IDs, a new label will have to be added to each project set's tools namespace:
`alliance: JAG_RBAC`
Get a list of users that should have access to the Argo CD UI and to the GitHub repo. Incorporate these users into the GitOpsAlliance resource manifest.
The GitOpsAlliance resource will be created in each of these clusters: KLAB, Silver, Gold, and GoldDR.
The plan will be prepared by the Platform Services team and reviewed and approved by JAG. Initial implementation to be done by the Platform Services team, then turned over to JAG for completion.
**Definition of done**
- [x] A plan has been prepared, including repo migration strategy, repo structure, and scope
- [x] The plan has been reviewed and approved by JAG
- [x] Initial setup has been done and instructions provided to JAG for implementation next steps
| non_priority | enable argo cd for jag rbac describe the issue devise a plan for the management of ocp rbac in argo cd for the entire justice ministry using the warden operator and the gitopsalliance resource additional context because the project sets to be included have multiple ministry ids a new label will have to be added to each project set s tools namespace alliance jag rbac get a list of users that should have access to the argo cd ui and to the github repo incorporate these users into the gitopsalliance resource manifest the gitopsalliance resource will be created in each of these clusters klab silver gold and golddr the plan will be prepared by the platform services team and reviewed and approved by jag initial implementation to be done by the platform services team then turned over to jag for completion definition of done a plan has been prepared including repo migration strategy repo structure and scope the plan has been reviewed and approved by jag initial setup has been done and instructions provided to jag for implementation next steps | 0 |
49,577 | 3,003,705,151 | IssuesEvent | 2015-07-25 05:47:17 | jayway/powermock | https://api.github.com/repos/jayway/powermock | opened | PowerMock+TestNG+DataProvider RuntimeException | bug imported Priority-Medium | _From [Ignas.Tr...@gmail.com](https://code.google.com/u/112024306843858881334/) on October 01, 2013 15:01:03_
What steps will reproduce the problem? ======================================
@Test
@PrepareForTest
public class StaticTest extends PowerMockTestCase {
@DataProvider
public final Object[][] getWeekday() {
return new Object[][] {
{new CustomClass()}
};
}
@Test (dataProvider = "getWeekday")
public void forAllWeekdaysAllClassroomsShouldBeAvailableInitially(CustomClass p) {
assertTrue(true);
}
}
class CustomClass {} What is the expected output? What do you see instead? =====================================================
I see:
java.lang.RuntimeException: Can't invoke method public void lt.ignas.classroombooking.ReservationPlaceTest.bookingForSeparateDayShouldRemainClassroomAvailable(lt.ignas.classroombooking.HourOfWeek,lt.ignas.classroombooking.HourOfWeek), probably due to classloader mismatch
I expect:
test to start with dataProvider provided object and to pass succesfully. What version of the product are you using? On what operating system? ====================================================================
UBUNTU 12.04
java version "1.7.0_40"
Java(TM) SE Runtime Environment (build 1.7.0_40-b43)
Java HotSpot(TM) 64-Bit Server VM (build 24.0-b56, mixed mode)
\<dependency>
\<groupId>org.testng</groupId>
\<artifactId>testng</artifactId>
\<version>6.8.7</version>
\</dependency>
\<dependency>
\<groupId>org.mockito</groupId>
\<artifactId>mockito-core</artifactId>
\<version>1.9.5</version>
\<scope>test</scope>
\</dependency>
\<dependency>
\<groupId>org.powermock</groupId>
\<artifactId>powermock-module-testng</artifactId>
\<version>1.5.1</version>
\</dependency>
\<dependency>
\<groupId>org.powermock</groupId>
\<artifactId>powermock-api-mockito</artifactId>
\<version>1.5.1</version>
\<exclusions>
\<exclusion>
\<groupId>org.mockito</groupId>
\<artifactId>mockito-all</artifactId>
\</exclusion>
\</exclusions>
\</dependency> Please provide any additional information below. ================================================
1. Without '@PrepareForTest' test PASSES.
2. Without 'extends PowerMockTestCase' test PASSES.
3. If DataProvider gives STD ( http://en.wikipedia.org/wiki/Standard_library ) class object (like StringBuilder, Object, int, String, etc.) (and test method requires the same type) test PASSES (see APPENDIX A below)
4. If DataProvider gives any custom class included in my project (like CustomClass in the example above) (and test metho requires that type) - test FAILS.
5. If DataProvider gives any custom class included in my project (like CustomClass in the example above) BUT test method requires Object - test PASSES. (see APPENDIX B below)
Last statement is pretty good workround, but Java's compile time checkings goes away. And explicit cast is needed.
===== APPENDIX A ======
@Test
@PrepareForTest
public class StaticTest extends PowerMockTestCase {
@DataProvider
public final Object[][] getWeekday() {
return new Object[][] {
{new StringBuilder()}
};
}
@Test (dataProvider = "getWeekday")
public void forAllWeekdaysAllClassroomsShouldBeAvailableInitially(StringBuilder p) {
assertTrue(true);
}
}
===== APPENDIX B ======
@Test
@PrepareForTest
public class StaticTest extends PowerMockTestCase {
@DataProvider
public final Object[][] getWeekday() {
return new Object[][] {
{new CustomClass()}
};
}
@Test (dataProvider = "getWeekday")
public void forAllWeekdaysAllClassroomsShouldBeAvailableInitially(Object p) {
assertTrue(true);
}
}
class CustomClass {}
_Original issue: http://code.google.com/p/powermock/issues/detail?id=464_ | 1.0 | PowerMock+TestNG+DataProvider RuntimeException - _From [Ignas.Tr...@gmail.com](https://code.google.com/u/112024306843858881334/) on October 01, 2013 15:01:03_
What steps will reproduce the problem? ======================================
@Test
@PrepareForTest
public class StaticTest extends PowerMockTestCase {
@DataProvider
public final Object[][] getWeekday() {
return new Object[][] {
{new CustomClass()}
};
}
@Test (dataProvider = "getWeekday")
public void forAllWeekdaysAllClassroomsShouldBeAvailableInitially(CustomClass p) {
assertTrue(true);
}
}
class CustomClass {} What is the expected output? What do you see instead? =====================================================
I see:
java.lang.RuntimeException: Can't invoke method public void lt.ignas.classroombooking.ReservationPlaceTest.bookingForSeparateDayShouldRemainClassroomAvailable(lt.ignas.classroombooking.HourOfWeek,lt.ignas.classroombooking.HourOfWeek), probably due to classloader mismatch
I expect:
test to start with dataProvider provided object and to pass succesfully. What version of the product are you using? On what operating system? ====================================================================
UBUNTU 12.04
java version "1.7.0_40"
Java(TM) SE Runtime Environment (build 1.7.0_40-b43)
Java HotSpot(TM) 64-Bit Server VM (build 24.0-b56, mixed mode)
\<dependency>
\<groupId>org.testng</groupId>
\<artifactId>testng</artifactId>
\<version>6.8.7</version>
\</dependency>
\<dependency>
\<groupId>org.mockito</groupId>
\<artifactId>mockito-core</artifactId>
\<version>1.9.5</version>
\<scope>test</scope>
\</dependency>
\<dependency>
\<groupId>org.powermock</groupId>
\<artifactId>powermock-module-testng</artifactId>
\<version>1.5.1</version>
\</dependency>
\<dependency>
\<groupId>org.powermock</groupId>
\<artifactId>powermock-api-mockito</artifactId>
\<version>1.5.1</version>
\<exclusions>
\<exclusion>
\<groupId>org.mockito</groupId>
\<artifactId>mockito-all</artifactId>
\</exclusion>
\</exclusions>
\</dependency> Please provide any additional information below. ================================================
1. Without '@PrepareForTest' test PASSES.
2. Without 'extends PowerMockTestCase' test PASSES.
3. If DataProvider gives STD ( http://en.wikipedia.org/wiki/Standard_library ) class object (like StringBuilder, Object, int, String, etc.) (and test method requires the same type) test PASSES (see APPENDIX A below)
4. If DataProvider gives any custom class included in my project (like CustomClass in the example above) (and test metho requires that type) - test FAILS.
5. If DataProvider gives any custom class included in my project (like CustomClass in the example above) BUT test method requires Object - test PASSES. (see APPENDIX B below)
Last statement is pretty good workround, but Java's compile time checkings goes away. And explicit cast is needed.
===== APPENDIX A ======
@Test
@PrepareForTest
public class StaticTest extends PowerMockTestCase {
@DataProvider
public final Object[][] getWeekday() {
return new Object[][] {
{new StringBuilder()}
};
}
@Test (dataProvider = "getWeekday")
public void forAllWeekdaysAllClassroomsShouldBeAvailableInitially(StringBuilder p) {
assertTrue(true);
}
}
===== APPENDIX B ======
@Test
@PrepareForTest
public class StaticTest extends PowerMockTestCase {
@DataProvider
public final Object[][] getWeekday() {
return new Object[][] {
{new CustomClass()}
};
}
@Test (dataProvider = "getWeekday")
public void forAllWeekdaysAllClassroomsShouldBeAvailableInitially(Object p) {
assertTrue(true);
}
}
class CustomClass {}
_Original issue: http://code.google.com/p/powermock/issues/detail?id=464_ | priority | powermock testng dataprovider runtimeexception from on october what steps will reproduce the problem test preparefortest public class statictest extends powermocktestcase dataprovider public final object getweekday return new object new customclass test dataprovider getweekday public void forallweekdaysallclassroomsshouldbeavailableinitially customclass p asserttrue true class customclass what is the expected output what do you see instead i see java lang runtimeexception can t invoke method public void lt ignas classroombooking reservationplacetest bookingforseparatedayshouldremainclassroomavailable lt ignas classroombooking hourofweek lt ignas classroombooking hourofweek probably due to classloader mismatch i expect test to start with dataprovider provided object and to pass succesfully what version of the product are you using on what operating system ubuntu java version java tm se runtime environment build java hotspot tm bit server vm build mixed mode org testng testng org mockito mockito core test org powermock powermock module testng org powermock powermock api mockito org mockito mockito all please provide any additional information below without preparefortest test passes without extends powermocktestcase test passes if dataprovider gives std class object like stringbuilder object int string etc and test method requires the same type test passes see appendix a below if dataprovider gives any custom class included in my project like customclass in the example above and test metho requires that type test fails if dataprovider gives any custom class included in my project like customclass in the example above but test method requires object test passes see appendix b below last statement is pretty good workround but java s compile time checkings goes away and explicit cast is needed appendix a test preparefortest public class statictest extends powermocktestcase dataprovider public final object getweekday return new object new stringbuilder test dataprovider getweekday public void forallweekdaysallclassroomsshouldbeavailableinitially stringbuilder p asserttrue true appendix b test preparefortest public class statictest extends powermocktestcase dataprovider public final object getweekday return new object new customclass test dataprovider getweekday public void forallweekdaysallclassroomsshouldbeavailableinitially object p asserttrue true class customclass original issue | 1 |
135,781 | 19,663,509,095 | IssuesEvent | 2022-01-10 19:37:50 | elementary/switchboard-plug-power | https://api.github.com/repos/elementary/switchboard-plug-power | opened | Expose automatic lower power mode setting | Needs Design | ### Problem
GNOME Settings Daemon includes a setting for automatic low power mode, but we don't expose it in the UI.
### Proposal
Include a switch for `org.gnome.settings-daemon.plugins.power power-saver-profile-on-low-battery`
### Prior Art (Optional)
_No response_ | 1.0 | Expose automatic lower power mode setting - ### Problem
GNOME Settings Daemon includes a setting for automatic low power mode, but we don't expose it in the UI.
### Proposal
Include a switch for `org.gnome.settings-daemon.plugins.power power-saver-profile-on-low-battery`
### Prior Art (Optional)
_No response_ | non_priority | expose automatic lower power mode setting problem gnome settings daemon includes a setting for automatic low power mode but we don t expose it in the ui proposal include a switch for org gnome settings daemon plugins power power saver profile on low battery prior art optional no response | 0 |
43,968 | 17,775,659,723 | IssuesEvent | 2021-08-30 18:52:18 | cityofaustin/atd-data-tech | https://api.github.com/repos/cityofaustin/atd-data-tech | opened | In markings_specialty_point feature layer, in Subtype Name for "D_ATD_SPEC_PNT_OTHER_SUB" add " 2 Gr... | Workgroup: SMB Service: Geo | <!-- Email -->
<!-- susanne.gov@austintexas.gov -->
> What application are you using?
ArcGIS
> Describe the problem.
In markings_specialty_point feature layer, in Subtype Name for "D_ATD_SPEC_PNT_OTHER_SUB" add " 2 Green Pads with chevron"
> How soon do you need this?
Soon — This week
> Is there anything else we should know?
To get started on QA/QC existing GIS inventory of green pads for pavement markings.
> Requested By
Susanne G.
Request ID: DTS21-102580
| 1.0 | In markings_specialty_point feature layer, in Subtype Name for "D_ATD_SPEC_PNT_OTHER_SUB" add " 2 Gr... - <!-- Email -->
<!-- susanne.gov@austintexas.gov -->
> What application are you using?
ArcGIS
> Describe the problem.
In markings_specialty_point feature layer, in Subtype Name for "D_ATD_SPEC_PNT_OTHER_SUB" add " 2 Green Pads with chevron"
> How soon do you need this?
Soon — This week
> Is there anything else we should know?
To get started on QA/QC existing GIS inventory of green pads for pavement markings.
> Requested By
Susanne G.
Request ID: DTS21-102580
| non_priority | in markings specialty point feature layer in subtype name for d atd spec pnt other sub add gr what application are you using arcgis describe the problem in markings specialty point feature layer in subtype name for d atd spec pnt other sub add green pads with chevron how soon do you need this soon — this week is there anything else we should know to get started on qa qc existing gis inventory of green pads for pavement markings requested by susanne g request id | 0 |
268,802 | 28,835,534,761 | IssuesEvent | 2023-05-04 01:02:36 | vital-dev-org/Spring-Boot-Sample-Project | https://api.github.com/repos/vital-dev-org/Spring-Boot-Sample-Project | opened | spring-boot-starter-data-rest-2.1.3.RELEASE.jar: 19 vulnerabilities (highest severity is: 9.8) | Mend: dependency security vulnerability | <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>spring-boot-starter-data-rest-2.1.3.RELEASE.jar</b></p></summary>
<p></p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/org/apache/tomcat/embed/tomcat-embed-core/9.0.16/tomcat-embed-core-9.0.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 (spring-boot-starter-data-rest version) | Remediation Available |
| ------------- | ------------- | ----- | ----- | ----- | ------------- | --- |
| [CVE-2016-1000027](https://www.mend.io/vulnerability-database/CVE-2016-1000027) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 9.8 | spring-web-5.1.5.RELEASE.jar | Transitive | 2.1.15.RELEASE | ✅ |
| [CVE-2019-0232](https://www.mend.io/vulnerability-database/CVE-2019-0232) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 8.1 | tomcat-embed-core-9.0.16.jar | Transitive | 2.1.5.RELEASE | ✅ |
| [CVE-2019-10072](https://www.mend.io/vulnerability-database/CVE-2019-10072) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 7.5 | tomcat-embed-core-9.0.16.jar | Transitive | 2.1.6.RELEASE | ✅ |
| [CVE-2019-17563](https://www.mend.io/vulnerability-database/CVE-2019-17563) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 7.5 | tomcat-embed-core-9.0.16.jar | Transitive | 2.1.12.RELEASE | ✅ |
| [CVE-2020-11996](https://www.mend.io/vulnerability-database/CVE-2020-11996) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 7.5 | tomcat-embed-core-9.0.16.jar | Transitive | 2.1.15.RELEASE | ✅ |
| [CVE-2020-13934](https://www.mend.io/vulnerability-database/CVE-2020-13934) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 7.5 | tomcat-embed-core-9.0.16.jar | Transitive | 2.1.16.RELEASE | ✅ |
| [CVE-2020-13935](https://www.mend.io/vulnerability-database/CVE-2020-13935) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 7.5 | tomcat-embed-websocket-9.0.16.jar | Transitive | 2.1.16.RELEASE | ✅ |
| [CVE-2021-25122](https://www.mend.io/vulnerability-database/CVE-2021-25122) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 7.5 | tomcat-embed-core-9.0.16.jar | Transitive | 2.3.9.RELEASE | ✅ |
| [CVE-2020-5398](https://www.mend.io/vulnerability-database/CVE-2020-5398) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 7.5 | spring-web-5.1.5.RELEASE.jar | Transitive | 2.1.12.RELEASE | ✅ |
| [CVE-2021-25329](https://www.mend.io/vulnerability-database/CVE-2021-25329) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 7.0 | tomcat-embed-core-9.0.16.jar | Transitive | 2.3.9.RELEASE | ✅ |
| [CVE-2019-12418](https://www.mend.io/vulnerability-database/CVE-2019-12418) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 7.0 | tomcat-embed-core-9.0.16.jar | Transitive | 2.1.11.RELEASE | ✅ |
| [CVE-2020-9484](https://www.mend.io/vulnerability-database/CVE-2020-9484) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 7.0 | tomcat-embed-core-9.0.16.jar | Transitive | 2.1.15.RELEASE | ✅ |
| [CVE-2020-5421](https://www.mend.io/vulnerability-database/CVE-2020-5421) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> Medium | 6.5 | spring-web-5.1.5.RELEASE.jar | Transitive | 2.1.17.RELEASE | ✅ |
| [CVE-2019-0221](https://www.mend.io/vulnerability-database/CVE-2019-0221) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> Medium | 6.1 | tomcat-embed-core-9.0.16.jar | Transitive | 2.1.5.RELEASE | ✅ |
| [CVE-2019-10219](https://www.mend.io/vulnerability-database/CVE-2019-10219) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> Medium | 6.1 | hibernate-validator-6.0.14.Final.jar | Transitive | 2.1.10.RELEASE | ✅ |
| [CVE-2021-24122](https://www.mend.io/vulnerability-database/CVE-2021-24122) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> Medium | 5.9 | tomcat-embed-core-9.0.16.jar | Transitive | 2.2.12.RELEASE | ✅ |
| [CVE-2020-10693](https://www.mend.io/vulnerability-database/CVE-2020-10693) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> Medium | 5.3 | hibernate-validator-6.0.14.Final.jar | Transitive | 2.1.15.RELEASE | ✅ |
| [CVE-2020-1935](https://www.mend.io/vulnerability-database/CVE-2020-1935) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> Medium | 4.8 | tomcat-embed-core-9.0.16.jar | Transitive | 2.1.13.RELEASE | ✅ |
| [CVE-2020-13943](https://www.mend.io/vulnerability-database/CVE-2020-13943) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> Medium | 4.3 | tomcat-embed-core-9.0.16.jar | Transitive | 2.1.17.RELEASE | ✅ |
## Details
<details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> CVE-2016-1000027</summary>
### Vulnerable Library - <b>spring-web-5.1.5.RELEASE.jar</b></p>
<p>Spring Web</p>
<p>Library home page: <a href="https://github.com/spring-projects/spring-framework">https://github.com/spring-projects/spring-framework</a></p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/org/springframework/spring-web/5.1.5.RELEASE/spring-web-5.1.5.RELEASE.jar</p>
<p>
Dependency Hierarchy:
- spring-boot-starter-data-rest-2.1.3.RELEASE.jar (Root Library)
- spring-boot-starter-web-2.1.3.RELEASE.jar
- :x: **spring-web-5.1.5.RELEASE.jar** (Vulnerable Library)
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
Pivotal Spring Framework through 5.3.16 suffers from a potential remote code execution (RCE) issue if used for Java deserialization of untrusted data. Depending on how the library is implemented within a product, this issue may or not occur, and authentication may be required. NOTE: the vendor's position is that untrusted data is not an intended use case. The product's behavior will not be changed because some users rely on deserialization of trusted data.
<p>Publish Date: 2020-01-02
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2016-1000027>CVE-2016-1000027</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>Release Date: 2020-01-02</p>
<p>Fix Resolution (org.springframework:spring-web): 5.1.16.RELEASE</p>
<p>Direct dependency fix Resolution (org.springframework.boot:spring-boot-starter-data-rest): 2.1.15.RELEASE</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-0232</summary>
### Vulnerable Library - <b>tomcat-embed-core-9.0.16.jar</b></p>
<p>Core Tomcat implementation</p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/org/apache/tomcat/embed/tomcat-embed-core/9.0.16/tomcat-embed-core-9.0.16.jar</p>
<p>
Dependency Hierarchy:
- spring-boot-starter-data-rest-2.1.3.RELEASE.jar (Root Library)
- spring-boot-starter-web-2.1.3.RELEASE.jar
- spring-boot-starter-tomcat-2.1.3.RELEASE.jar
- :x: **tomcat-embed-core-9.0.16.jar** (Vulnerable Library)
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
When running on Windows with enableCmdLineArguments enabled, the CGI Servlet in Apache Tomcat 9.0.0.M1 to 9.0.17, 8.5.0 to 8.5.39 and 7.0.0 to 7.0.93 is vulnerable to Remote Code Execution due to a bug in the way the JRE passes command line arguments to Windows. The CGI Servlet is disabled by default. The CGI option enableCmdLineArguments is disable by default in Tomcat 9.0.x (and will be disabled by default in all versions in response to this vulnerability). For a detailed explanation of the JRE behaviour, see Markus Wulftange's blog (https://codewhitesec.blogspot.com/2016/02/java-and-command-line-injections-in-windows.html) and this archived MSDN blog (https://web.archive.org/web/20161228144344/https://blogs.msdn.microsoft.com/twistylittlepassagesallalike/2011/04/23/everyone-quotes-command-line-arguments-the-wrong-way/).
<p>Publish Date: 2019-04-15
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2019-0232>CVE-2019-0232</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>8.1</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-0232">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-0232</a></p>
<p>Release Date: 2019-04-15</p>
<p>Fix Resolution (org.apache.tomcat.embed:tomcat-embed-core): 9.0.19</p>
<p>Direct dependency fix Resolution (org.springframework.boot:spring-boot-starter-data-rest): 2.1.5.RELEASE</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-10072</summary>
### Vulnerable Library - <b>tomcat-embed-core-9.0.16.jar</b></p>
<p>Core Tomcat implementation</p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/org/apache/tomcat/embed/tomcat-embed-core/9.0.16/tomcat-embed-core-9.0.16.jar</p>
<p>
Dependency Hierarchy:
- spring-boot-starter-data-rest-2.1.3.RELEASE.jar (Root Library)
- spring-boot-starter-web-2.1.3.RELEASE.jar
- spring-boot-starter-tomcat-2.1.3.RELEASE.jar
- :x: **tomcat-embed-core-9.0.16.jar** (Vulnerable Library)
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
The fix for CVE-2019-0199 was incomplete and did not address HTTP/2 connection window exhaustion on write in Apache Tomcat versions 9.0.0.M1 to 9.0.19 and 8.5.0 to 8.5.40 . By not sending WINDOW_UPDATE messages for the connection window (stream 0) clients were able to cause server-side threads to block eventually leading to thread exhaustion and a DoS.
<p>Publish Date: 2019-06-21
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2019-10072>CVE-2019-10072</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>7.5</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="http://tomcat.apache.org/security-8.html#Fixed_in_Apache_Tomcat_8.5.41">http://tomcat.apache.org/security-8.html#Fixed_in_Apache_Tomcat_8.5.41</a></p>
<p>Release Date: 2019-06-21</p>
<p>Fix Resolution (org.apache.tomcat.embed:tomcat-embed-core): 9.0.20</p>
<p>Direct dependency fix Resolution (org.springframework.boot:spring-boot-starter-data-rest): 2.1.6.RELEASE</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-17563</summary>
### Vulnerable Library - <b>tomcat-embed-core-9.0.16.jar</b></p>
<p>Core Tomcat implementation</p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/org/apache/tomcat/embed/tomcat-embed-core/9.0.16/tomcat-embed-core-9.0.16.jar</p>
<p>
Dependency Hierarchy:
- spring-boot-starter-data-rest-2.1.3.RELEASE.jar (Root Library)
- spring-boot-starter-web-2.1.3.RELEASE.jar
- spring-boot-starter-tomcat-2.1.3.RELEASE.jar
- :x: **tomcat-embed-core-9.0.16.jar** (Vulnerable Library)
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
When using FORM authentication with Apache Tomcat 9.0.0.M1 to 9.0.29, 8.5.0 to 8.5.49 and 7.0.0 to 7.0.98 there was a narrow window where an attacker could perform a session fixation attack. The window was considered too narrow for an exploit to be practical but, erring on the side of caution, this issue has been treated as a security vulnerability.
<p>Publish Date: 2019-12-23
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2019-17563>CVE-2019-17563</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: None
- User Interaction: Required
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-17563">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-17563</a></p>
<p>Release Date: 2019-12-23</p>
<p>Fix Resolution (org.apache.tomcat.embed:tomcat-embed-core): 9.0.30</p>
<p>Direct dependency fix Resolution (org.springframework.boot:spring-boot-starter-data-rest): 2.1.12.RELEASE</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-2020-11996</summary>
### Vulnerable Library - <b>tomcat-embed-core-9.0.16.jar</b></p>
<p>Core Tomcat implementation</p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/org/apache/tomcat/embed/tomcat-embed-core/9.0.16/tomcat-embed-core-9.0.16.jar</p>
<p>
Dependency Hierarchy:
- spring-boot-starter-data-rest-2.1.3.RELEASE.jar (Root Library)
- spring-boot-starter-web-2.1.3.RELEASE.jar
- spring-boot-starter-tomcat-2.1.3.RELEASE.jar
- :x: **tomcat-embed-core-9.0.16.jar** (Vulnerable Library)
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
A specially crafted sequence of HTTP/2 requests sent to Apache Tomcat 10.0.0-M1 to 10.0.0-M5, 9.0.0.M1 to 9.0.35 and 8.5.0 to 8.5.55 could trigger high CPU usage for several seconds. If a sufficient number of such requests were made on concurrent HTTP/2 connections, the server could become unresponsive.
<p>Publish Date: 2020-06-26
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2020-11996>CVE-2020-11996</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>7.5</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://lists.apache.org/thread.html/r5541ef6b6b68b49f76fc4c45695940116da2bcbe0312ef204a00a2e0%40%3Cannounce.tomcat.apache.org%3E,http://tomcat.apache.org/security-10.html">https://lists.apache.org/thread.html/r5541ef6b6b68b49f76fc4c45695940116da2bcbe0312ef204a00a2e0%40%3Cannounce.tomcat.apache.org%3E,http://tomcat.apache.org/security-10.html</a></p>
<p>Release Date: 2020-06-26</p>
<p>Fix Resolution (org.apache.tomcat.embed:tomcat-embed-core): 9.0.36</p>
<p>Direct dependency fix Resolution (org.springframework.boot:spring-boot-starter-data-rest): 2.1.15.RELEASE</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-2020-13934</summary>
### Vulnerable Library - <b>tomcat-embed-core-9.0.16.jar</b></p>
<p>Core Tomcat implementation</p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/org/apache/tomcat/embed/tomcat-embed-core/9.0.16/tomcat-embed-core-9.0.16.jar</p>
<p>
Dependency Hierarchy:
- spring-boot-starter-data-rest-2.1.3.RELEASE.jar (Root Library)
- spring-boot-starter-web-2.1.3.RELEASE.jar
- spring-boot-starter-tomcat-2.1.3.RELEASE.jar
- :x: **tomcat-embed-core-9.0.16.jar** (Vulnerable Library)
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
An h2c direct connection to Apache Tomcat 10.0.0-M1 to 10.0.0-M6, 9.0.0.M5 to 9.0.36 and 8.5.1 to 8.5.56 did not release the HTTP/1.1 processor after the upgrade to HTTP/2. If a sufficient number of such requests were made, an OutOfMemoryException could occur leading to a denial of service.
<p>Publish Date: 2020-07-14
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2020-13934>CVE-2020-13934</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>7.5</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://lists.apache.org/thread.html/r61f411cf82488d6ec213063fc15feeeb88e31b0ca9c29652ee4f962e%40%3Cannounce.tomcat.apache.org%3E">https://lists.apache.org/thread.html/r61f411cf82488d6ec213063fc15feeeb88e31b0ca9c29652ee4f962e%40%3Cannounce.tomcat.apache.org%3E</a></p>
<p>Release Date: 2020-07-14</p>
<p>Fix Resolution (org.apache.tomcat.embed:tomcat-embed-core): 9.0.37</p>
<p>Direct dependency fix Resolution (org.springframework.boot:spring-boot-starter-data-rest): 2.1.16.RELEASE</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-2020-13935</summary>
### Vulnerable Library - <b>tomcat-embed-websocket-9.0.16.jar</b></p>
<p>Core Tomcat implementation</p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/org/apache/tomcat/embed/tomcat-embed-websocket/9.0.16/tomcat-embed-websocket-9.0.16.jar</p>
<p>
Dependency Hierarchy:
- spring-boot-starter-data-rest-2.1.3.RELEASE.jar (Root Library)
- spring-boot-starter-web-2.1.3.RELEASE.jar
- spring-boot-starter-tomcat-2.1.3.RELEASE.jar
- :x: **tomcat-embed-websocket-9.0.16.jar** (Vulnerable Library)
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
The payload length in a WebSocket frame was not correctly validated in Apache Tomcat 10.0.0-M1 to 10.0.0-M6, 9.0.0.M1 to 9.0.36, 8.5.0 to 8.5.56 and 7.0.27 to 7.0.104. Invalid payload lengths could trigger an infinite loop. Multiple requests with invalid payload lengths could lead to a denial of service.
<p>Publish Date: 2020-07-14
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2020-13935>CVE-2020-13935</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>7.5</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://lists.apache.org/thread.html/rd48c72bd3255bda87564d4da3791517c074d94f8a701f93b85752651%40%3Cannounce.tomcat.apache.org%3E">https://lists.apache.org/thread.html/rd48c72bd3255bda87564d4da3791517c074d94f8a701f93b85752651%40%3Cannounce.tomcat.apache.org%3E</a></p>
<p>Release Date: 2020-07-14</p>
<p>Fix Resolution (org.apache.tomcat.embed:tomcat-embed-websocket): 9.0.37</p>
<p>Direct dependency fix Resolution (org.springframework.boot:spring-boot-starter-data-rest): 2.1.16.RELEASE</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-25122</summary>
### Vulnerable Library - <b>tomcat-embed-core-9.0.16.jar</b></p>
<p>Core Tomcat implementation</p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/org/apache/tomcat/embed/tomcat-embed-core/9.0.16/tomcat-embed-core-9.0.16.jar</p>
<p>
Dependency Hierarchy:
- spring-boot-starter-data-rest-2.1.3.RELEASE.jar (Root Library)
- spring-boot-starter-web-2.1.3.RELEASE.jar
- spring-boot-starter-tomcat-2.1.3.RELEASE.jar
- :x: **tomcat-embed-core-9.0.16.jar** (Vulnerable Library)
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
When responding to new h2c connection requests, Apache Tomcat versions 10.0.0-M1 to 10.0.0, 9.0.0.M1 to 9.0.41 and 8.5.0 to 8.5.61 could duplicate request headers and a limited amount of request body from one request to another meaning user A and user B could both see the results of user A's request.
<p>Publish Date: 2021-03-01
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2021-25122>CVE-2021-25122</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>7.5</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: None
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://lists.apache.org/thread.html/r7b95bc248603360501f18c8eb03bb6001ec0ee3296205b34b07105b7%40%3Cannounce.tomcat.apache.org%3E">https://lists.apache.org/thread.html/r7b95bc248603360501f18c8eb03bb6001ec0ee3296205b34b07105b7%40%3Cannounce.tomcat.apache.org%3E</a></p>
<p>Release Date: 2021-03-01</p>
<p>Fix Resolution (org.apache.tomcat.embed:tomcat-embed-core): 9.0.43</p>
<p>Direct dependency fix Resolution (org.springframework.boot:spring-boot-starter-data-rest): 2.3.9.RELEASE</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-2020-5398</summary>
### Vulnerable Library - <b>spring-web-5.1.5.RELEASE.jar</b></p>
<p>Spring Web</p>
<p>Library home page: <a href="https://github.com/spring-projects/spring-framework">https://github.com/spring-projects/spring-framework</a></p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/org/springframework/spring-web/5.1.5.RELEASE/spring-web-5.1.5.RELEASE.jar</p>
<p>
Dependency Hierarchy:
- spring-boot-starter-data-rest-2.1.3.RELEASE.jar (Root Library)
- spring-boot-starter-web-2.1.3.RELEASE.jar
- :x: **spring-web-5.1.5.RELEASE.jar** (Vulnerable Library)
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
In Spring Framework, versions 5.2.x prior to 5.2.3, versions 5.1.x prior to 5.1.13, and versions 5.0.x prior to 5.0.16, an application is vulnerable to a reflected file download (RFD) attack when it sets a "Content-Disposition" header in the response where the filename attribute is derived from user supplied input.
<p>Publish Date: 2020-01-17
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2020-5398>CVE-2020-5398</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: None
- User Interaction: Required
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://pivotal.io/security/cve-2020-5398">https://pivotal.io/security/cve-2020-5398</a></p>
<p>Release Date: 2020-01-17</p>
<p>Fix Resolution (org.springframework:spring-web): 5.1.13.RELEASE</p>
<p>Direct dependency fix Resolution (org.springframework.boot:spring-boot-starter-data-rest): 2.1.12.RELEASE</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-25329</summary>
### Vulnerable Library - <b>tomcat-embed-core-9.0.16.jar</b></p>
<p>Core Tomcat implementation</p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/org/apache/tomcat/embed/tomcat-embed-core/9.0.16/tomcat-embed-core-9.0.16.jar</p>
<p>
Dependency Hierarchy:
- spring-boot-starter-data-rest-2.1.3.RELEASE.jar (Root Library)
- spring-boot-starter-web-2.1.3.RELEASE.jar
- spring-boot-starter-tomcat-2.1.3.RELEASE.jar
- :x: **tomcat-embed-core-9.0.16.jar** (Vulnerable Library)
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
The fix for CVE-2020-9484 was incomplete. When using Apache Tomcat 10.0.0-M1 to 10.0.0, 9.0.0.M1 to 9.0.41, 8.5.0 to 8.5.61 or 7.0.0. to 7.0.107 with a configuration edge case that was highly unlikely to be used, the Tomcat instance was still vulnerable to CVE-2020-9494. Note that both the previously published prerequisites for CVE-2020-9484 and the previously published mitigations for CVE-2020-9484 also apply to this issue.
<p>Publish Date: 2021-03-01
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2021-25329>CVE-2021-25329</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>7.0</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: High
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://lists.apache.org/thread.html/rfe62fbf9d4c314f166fe8c668e50e5d9dd882a99447f26f0367474bf%40%3Cannounce.tomcat.apache.org%3E">https://lists.apache.org/thread.html/rfe62fbf9d4c314f166fe8c668e50e5d9dd882a99447f26f0367474bf%40%3Cannounce.tomcat.apache.org%3E</a></p>
<p>Release Date: 2021-03-01</p>
<p>Fix Resolution (org.apache.tomcat.embed:tomcat-embed-core): 9.0.43</p>
<p>Direct dependency fix Resolution (org.springframework.boot:spring-boot-starter-data-rest): 2.3.9.RELEASE</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-12418</summary>
### Vulnerable Library - <b>tomcat-embed-core-9.0.16.jar</b></p>
<p>Core Tomcat implementation</p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/org/apache/tomcat/embed/tomcat-embed-core/9.0.16/tomcat-embed-core-9.0.16.jar</p>
<p>
Dependency Hierarchy:
- spring-boot-starter-data-rest-2.1.3.RELEASE.jar (Root Library)
- spring-boot-starter-web-2.1.3.RELEASE.jar
- spring-boot-starter-tomcat-2.1.3.RELEASE.jar
- :x: **tomcat-embed-core-9.0.16.jar** (Vulnerable Library)
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
When Apache Tomcat 9.0.0.M1 to 9.0.28, 8.5.0 to 8.5.47, 7.0.0 and 7.0.97 is configured with the JMX Remote Lifecycle Listener, a local attacker without access to the Tomcat process or configuration files is able to manipulate the RMI registry to perform a man-in-the-middle attack to capture user names and passwords used to access the JMX interface. The attacker can then use these credentials to access the JMX interface and gain complete control over the Tomcat instance.
<p>Publish Date: 2019-12-23
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2019-12418>CVE-2019-12418</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>7.0</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: High
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-12418">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-12418</a></p>
<p>Release Date: 2019-12-23</p>
<p>Fix Resolution (org.apache.tomcat.embed:tomcat-embed-core): 9.0.29</p>
<p>Direct dependency fix Resolution (org.springframework.boot:spring-boot-starter-data-rest): 2.1.11.RELEASE</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-2020-9484</summary>
### Vulnerable Library - <b>tomcat-embed-core-9.0.16.jar</b></p>
<p>Core Tomcat implementation</p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/org/apache/tomcat/embed/tomcat-embed-core/9.0.16/tomcat-embed-core-9.0.16.jar</p>
<p>
Dependency Hierarchy:
- spring-boot-starter-data-rest-2.1.3.RELEASE.jar (Root Library)
- spring-boot-starter-web-2.1.3.RELEASE.jar
- spring-boot-starter-tomcat-2.1.3.RELEASE.jar
- :x: **tomcat-embed-core-9.0.16.jar** (Vulnerable Library)
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
When using Apache Tomcat versions 10.0.0-M1 to 10.0.0-M4, 9.0.0.M1 to 9.0.34, 8.5.0 to 8.5.54 and 7.0.0 to 7.0.103 if a) an attacker is able to control the contents and name of a file on the server; and b) the server is configured to use the PersistenceManager with a FileStore; and c) the PersistenceManager is configured with sessionAttributeValueClassNameFilter="null" (the default unless a SecurityManager is used) or a sufficiently lax filter to allow the attacker provided object to be deserialized; and d) the attacker knows the relative file path from the storage location used by FileStore to the file the attacker has control over; then, using a specifically crafted request, the attacker will be able to trigger remote code execution via deserialization of the file under their control. Note that all of conditions a) to d) must be true for the attack to succeed.
<p>Publish Date: 2020-05-20
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2020-9484>CVE-2020-9484</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>7.0</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: High
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-9484">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-9484</a></p>
<p>Release Date: 2020-05-20</p>
<p>Fix Resolution (org.apache.tomcat.embed:tomcat-embed-core): 9.0.35</p>
<p>Direct dependency fix Resolution (org.springframework.boot:spring-boot-starter-data-rest): 2.1.15.RELEASE</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation is available for this issue
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> CVE-2020-5421</summary>
### Vulnerable Library - <b>spring-web-5.1.5.RELEASE.jar</b></p>
<p>Spring Web</p>
<p>Library home page: <a href="https://github.com/spring-projects/spring-framework">https://github.com/spring-projects/spring-framework</a></p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/org/springframework/spring-web/5.1.5.RELEASE/spring-web-5.1.5.RELEASE.jar</p>
<p>
Dependency Hierarchy:
- spring-boot-starter-data-rest-2.1.3.RELEASE.jar (Root Library)
- spring-boot-starter-web-2.1.3.RELEASE.jar
- :x: **spring-web-5.1.5.RELEASE.jar** (Vulnerable Library)
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
In Spring Framework versions 5.2.0 - 5.2.8, 5.1.0 - 5.1.17, 5.0.0 - 5.0.18, 4.3.0 - 4.3.28, and older unsupported versions, the protections against RFD attacks from CVE-2015-5211 may be bypassed depending on the browser used through the use of a jsessionid path parameter.
<p>Publish Date: 2020-09-19
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2020-5421>CVE-2020-5421</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>6.5</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: Low
- User Interaction: Required
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: High
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://tanzu.vmware.com/security/cve-2020-5421">https://tanzu.vmware.com/security/cve-2020-5421</a></p>
<p>Release Date: 2020-09-19</p>
<p>Fix Resolution (org.springframework:spring-web): 5.1.18.RELEASE</p>
<p>Direct dependency fix Resolution (org.springframework.boot:spring-boot-starter-data-rest): 2.1.17.RELEASE</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation is available for this issue
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> CVE-2019-0221</summary>
### Vulnerable Library - <b>tomcat-embed-core-9.0.16.jar</b></p>
<p>Core Tomcat implementation</p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/org/apache/tomcat/embed/tomcat-embed-core/9.0.16/tomcat-embed-core-9.0.16.jar</p>
<p>
Dependency Hierarchy:
- spring-boot-starter-data-rest-2.1.3.RELEASE.jar (Root Library)
- spring-boot-starter-web-2.1.3.RELEASE.jar
- spring-boot-starter-tomcat-2.1.3.RELEASE.jar
- :x: **tomcat-embed-core-9.0.16.jar** (Vulnerable Library)
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
The SSI printenv command in Apache Tomcat 9.0.0.M1 to 9.0.0.17, 8.5.0 to 8.5.39 and 7.0.0 to 7.0.93 echoes user provided data without escaping and is, therefore, vulnerable to XSS. SSI is disabled by default. The printenv command is intended for debugging and is unlikely to be present in a production website.
<p>Publish Date: 2019-05-28
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2019-0221>CVE-2019-0221</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>6.1</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: Low
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-0221">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-0221</a></p>
<p>Release Date: 2019-05-28</p>
<p>Fix Resolution (org.apache.tomcat.embed:tomcat-embed-core): 9.0.19</p>
<p>Direct dependency fix Resolution (org.springframework.boot:spring-boot-starter-data-rest): 2.1.5.RELEASE</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation is available for this issue
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> CVE-2019-10219</summary>
### Vulnerable Library - <b>hibernate-validator-6.0.14.Final.jar</b></p>
<p>Hibernate's Bean Validation (JSR-380) reference implementation.</p>
<p>Library home page: <a href="http://hibernate.org/validator">http://hibernate.org/validator</a></p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/org/hibernate/validator/hibernate-validator/6.0.14.Final/hibernate-validator-6.0.14.Final.jar</p>
<p>
Dependency Hierarchy:
- spring-boot-starter-data-rest-2.1.3.RELEASE.jar (Root Library)
- spring-boot-starter-web-2.1.3.RELEASE.jar
- :x: **hibernate-validator-6.0.14.Final.jar** (Vulnerable Library)
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
A vulnerability was found in Hibernate-Validator. The SafeHtml validator annotation fails to properly sanitize payloads consisting of potentially malicious code in HTML comments and instructions. This vulnerability can result in an XSS attack.
<p>Publish Date: 2019-11-08
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2019-10219>CVE-2019-10219</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>6.1</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: Low
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-10219">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-10219</a></p>
<p>Release Date: 2019-11-08</p>
<p>Fix Resolution (org.hibernate.validator:hibernate-validator): 6.0.18.Final</p>
<p>Direct dependency fix Resolution (org.springframework.boot:spring-boot-starter-data-rest): 2.1.10.RELEASE</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation is available for this issue
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> CVE-2021-24122</summary>
### Vulnerable Library - <b>tomcat-embed-core-9.0.16.jar</b></p>
<p>Core Tomcat implementation</p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/org/apache/tomcat/embed/tomcat-embed-core/9.0.16/tomcat-embed-core-9.0.16.jar</p>
<p>
Dependency Hierarchy:
- spring-boot-starter-data-rest-2.1.3.RELEASE.jar (Root Library)
- spring-boot-starter-web-2.1.3.RELEASE.jar
- spring-boot-starter-tomcat-2.1.3.RELEASE.jar
- :x: **tomcat-embed-core-9.0.16.jar** (Vulnerable Library)
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
When serving resources from a network location using the NTFS file system, Apache Tomcat versions 10.0.0-M1 to 10.0.0-M9, 9.0.0.M1 to 9.0.39, 8.5.0 to 8.5.59 and 7.0.0 to 7.0.106 were susceptible to JSP source code disclosure in some configurations. The root cause was the unexpected behaviour of the JRE API File.getCanonicalPath() which in turn was caused by the inconsistent behaviour of the Windows API (FindFirstFileW) in some circumstances.
<p>Publish Date: 2021-01-14
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2021-24122>CVE-2021-24122</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>5.9</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: 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://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-24122">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-24122</a></p>
<p>Release Date: 2021-01-14</p>
<p>Fix Resolution (org.apache.tomcat.embed:tomcat-embed-core): 9.0.40</p>
<p>Direct dependency fix Resolution (org.springframework.boot:spring-boot-starter-data-rest): 2.2.12.RELEASE</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation is available for this issue
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> CVE-2020-10693</summary>
### Vulnerable Library - <b>hibernate-validator-6.0.14.Final.jar</b></p>
<p>Hibernate's Bean Validation (JSR-380) reference implementation.</p>
<p>Library home page: <a href="http://hibernate.org/validator">http://hibernate.org/validator</a></p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/org/hibernate/validator/hibernate-validator/6.0.14.Final/hibernate-validator-6.0.14.Final.jar</p>
<p>
Dependency Hierarchy:
- spring-boot-starter-data-rest-2.1.3.RELEASE.jar (Root Library)
- spring-boot-starter-web-2.1.3.RELEASE.jar
- :x: **hibernate-validator-6.0.14.Final.jar** (Vulnerable Library)
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
A flaw was found in Hibernate Validator version 6.1.2.Final. A bug in the message interpolation processor enables invalid EL expressions to be evaluated as if they were valid. This flaw allows attackers to bypass input sanitation (escaping, stripping) controls that developers may have put in place when handling user-controlled data in error messages.
<p>Publish Date: 2020-05-06
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2020-10693>CVE-2020-10693</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>5.3</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: Low
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://hibernate.atlassian.net/projects/HV/issues/HV-1774">https://hibernate.atlassian.net/projects/HV/issues/HV-1774</a></p>
<p>Release Date: 2020-05-06</p>
<p>Fix Resolution (org.hibernate.validator:hibernate-validator): 6.0.20.Final</p>
<p>Direct dependency fix Resolution (org.springframework.boot:spring-boot-starter-data-rest): 2.1.15.RELEASE</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation is available for this issue
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> CVE-2020-1935</summary>
### Vulnerable Library - <b>tomcat-embed-core-9.0.16.jar</b></p>
<p>Core Tomcat implementation</p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/org/apache/tomcat/embed/tomcat-embed-core/9.0.16/tomcat-embed-core-9.0.16.jar</p>
<p>
Dependency Hierarchy:
- spring-boot-starter-data-rest-2.1.3.RELEASE.jar (Root Library)
- spring-boot-starter-web-2.1.3.RELEASE.jar
- spring-boot-starter-tomcat-2.1.3.RELEASE.jar
- :x: **tomcat-embed-core-9.0.16.jar** (Vulnerable Library)
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
In Apache Tomcat 9.0.0.M1 to 9.0.30, 8.5.0 to 8.5.50 and 7.0.0 to 7.0.99 the HTTP header parsing code used an approach to end-of-line parsing that allowed some invalid HTTP headers to be parsed as valid. This led to a possibility of HTTP Request Smuggling if Tomcat was located behind a reverse proxy that incorrectly handled the invalid Transfer-Encoding header in a particular manner. Such a reverse proxy is considered unlikely.
<p>Publish Date: 2020-02-24
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2020-1935>CVE-2020-1935</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>4.8</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: Low
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/advisories/GHSA-6v7p-v754-j89v">https://github.com/advisories/GHSA-6v7p-v754-j89v</a></p>
<p>Release Date: 2020-02-24</p>
<p>Fix Resolution (org.apache.tomcat.embed:tomcat-embed-core): 9.0.31</p>
<p>Direct dependency fix Resolution (org.springframework.boot:spring-boot-starter-data-rest): 2.1.13.RELEASE</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation is available for this issue
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> CVE-2020-13943</summary>
### Vulnerable Library - <b>tomcat-embed-core-9.0.16.jar</b></p>
<p>Core Tomcat implementation</p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/org/apache/tomcat/embed/tomcat-embed-core/9.0.16/tomcat-embed-core-9.0.16.jar</p>
<p>
Dependency Hierarchy:
- spring-boot-starter-data-rest-2.1.3.RELEASE.jar (Root Library)
- spring-boot-starter-web-2.1.3.RELEASE.jar
- spring-boot-starter-tomcat-2.1.3.RELEASE.jar
- :x: **tomcat-embed-core-9.0.16.jar** (Vulnerable Library)
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
If an HTTP/2 client connecting to Apache Tomcat 10.0.0-M1 to 10.0.0-M7, 9.0.0.M1 to 9.0.37 or 8.5.0 to 8.5.57 exceeded the agreed maximum number of concurrent streams for a connection (in violation of the HTTP/2 protocol), it was possible that a subsequent request made on that connection could contain HTTP headers - including HTTP/2 pseudo headers - from a previous request rather than the intended headers. This could lead to users seeing responses for unexpected resources.
<p>Publish Date: 2020-10-12
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2020-13943>CVE-2020-13943</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>4.3</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: 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://lists.apache.org/thread.html/r4a390027eb27e4550142fac6c8317cc684b157ae314d31514747f307%40%3Cannounce.tomcat.apache.org%3E">https://lists.apache.org/thread.html/r4a390027eb27e4550142fac6c8317cc684b157ae314d31514747f307%40%3Cannounce.tomcat.apache.org%3E</a></p>
<p>Release Date: 2020-10-12</p>
<p>Fix Resolution (org.apache.tomcat.embed:tomcat-embed-core): 9.0.38</p>
<p>Direct dependency fix Resolution (org.springframework.boot:spring-boot-starter-data-rest): 2.1.17.RELEASE</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation is available for this issue
</details>
***
<p>:rescue_worker_helmet: Automatic Remediation is available for this issue.</p> | True | spring-boot-starter-data-rest-2.1.3.RELEASE.jar: 19 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>spring-boot-starter-data-rest-2.1.3.RELEASE.jar</b></p></summary>
<p></p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/org/apache/tomcat/embed/tomcat-embed-core/9.0.16/tomcat-embed-core-9.0.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 (spring-boot-starter-data-rest version) | Remediation Available |
| ------------- | ------------- | ----- | ----- | ----- | ------------- | --- |
| [CVE-2016-1000027](https://www.mend.io/vulnerability-database/CVE-2016-1000027) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 9.8 | spring-web-5.1.5.RELEASE.jar | Transitive | 2.1.15.RELEASE | ✅ |
| [CVE-2019-0232](https://www.mend.io/vulnerability-database/CVE-2019-0232) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 8.1 | tomcat-embed-core-9.0.16.jar | Transitive | 2.1.5.RELEASE | ✅ |
| [CVE-2019-10072](https://www.mend.io/vulnerability-database/CVE-2019-10072) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 7.5 | tomcat-embed-core-9.0.16.jar | Transitive | 2.1.6.RELEASE | ✅ |
| [CVE-2019-17563](https://www.mend.io/vulnerability-database/CVE-2019-17563) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 7.5 | tomcat-embed-core-9.0.16.jar | Transitive | 2.1.12.RELEASE | ✅ |
| [CVE-2020-11996](https://www.mend.io/vulnerability-database/CVE-2020-11996) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 7.5 | tomcat-embed-core-9.0.16.jar | Transitive | 2.1.15.RELEASE | ✅ |
| [CVE-2020-13934](https://www.mend.io/vulnerability-database/CVE-2020-13934) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 7.5 | tomcat-embed-core-9.0.16.jar | Transitive | 2.1.16.RELEASE | ✅ |
| [CVE-2020-13935](https://www.mend.io/vulnerability-database/CVE-2020-13935) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 7.5 | tomcat-embed-websocket-9.0.16.jar | Transitive | 2.1.16.RELEASE | ✅ |
| [CVE-2021-25122](https://www.mend.io/vulnerability-database/CVE-2021-25122) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 7.5 | tomcat-embed-core-9.0.16.jar | Transitive | 2.3.9.RELEASE | ✅ |
| [CVE-2020-5398](https://www.mend.io/vulnerability-database/CVE-2020-5398) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 7.5 | spring-web-5.1.5.RELEASE.jar | Transitive | 2.1.12.RELEASE | ✅ |
| [CVE-2021-25329](https://www.mend.io/vulnerability-database/CVE-2021-25329) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 7.0 | tomcat-embed-core-9.0.16.jar | Transitive | 2.3.9.RELEASE | ✅ |
| [CVE-2019-12418](https://www.mend.io/vulnerability-database/CVE-2019-12418) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 7.0 | tomcat-embed-core-9.0.16.jar | Transitive | 2.1.11.RELEASE | ✅ |
| [CVE-2020-9484](https://www.mend.io/vulnerability-database/CVE-2020-9484) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> High | 7.0 | tomcat-embed-core-9.0.16.jar | Transitive | 2.1.15.RELEASE | ✅ |
| [CVE-2020-5421](https://www.mend.io/vulnerability-database/CVE-2020-5421) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> Medium | 6.5 | spring-web-5.1.5.RELEASE.jar | Transitive | 2.1.17.RELEASE | ✅ |
| [CVE-2019-0221](https://www.mend.io/vulnerability-database/CVE-2019-0221) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> Medium | 6.1 | tomcat-embed-core-9.0.16.jar | Transitive | 2.1.5.RELEASE | ✅ |
| [CVE-2019-10219](https://www.mend.io/vulnerability-database/CVE-2019-10219) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> Medium | 6.1 | hibernate-validator-6.0.14.Final.jar | Transitive | 2.1.10.RELEASE | ✅ |
| [CVE-2021-24122](https://www.mend.io/vulnerability-database/CVE-2021-24122) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> Medium | 5.9 | tomcat-embed-core-9.0.16.jar | Transitive | 2.2.12.RELEASE | ✅ |
| [CVE-2020-10693](https://www.mend.io/vulnerability-database/CVE-2020-10693) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> Medium | 5.3 | hibernate-validator-6.0.14.Final.jar | Transitive | 2.1.15.RELEASE | ✅ |
| [CVE-2020-1935](https://www.mend.io/vulnerability-database/CVE-2020-1935) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> Medium | 4.8 | tomcat-embed-core-9.0.16.jar | Transitive | 2.1.13.RELEASE | ✅ |
| [CVE-2020-13943](https://www.mend.io/vulnerability-database/CVE-2020-13943) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> Medium | 4.3 | tomcat-embed-core-9.0.16.jar | Transitive | 2.1.17.RELEASE | ✅ |
## Details
<details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> CVE-2016-1000027</summary>
### Vulnerable Library - <b>spring-web-5.1.5.RELEASE.jar</b></p>
<p>Spring Web</p>
<p>Library home page: <a href="https://github.com/spring-projects/spring-framework">https://github.com/spring-projects/spring-framework</a></p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/org/springframework/spring-web/5.1.5.RELEASE/spring-web-5.1.5.RELEASE.jar</p>
<p>
Dependency Hierarchy:
- spring-boot-starter-data-rest-2.1.3.RELEASE.jar (Root Library)
- spring-boot-starter-web-2.1.3.RELEASE.jar
- :x: **spring-web-5.1.5.RELEASE.jar** (Vulnerable Library)
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
Pivotal Spring Framework through 5.3.16 suffers from a potential remote code execution (RCE) issue if used for Java deserialization of untrusted data. Depending on how the library is implemented within a product, this issue may or not occur, and authentication may be required. NOTE: the vendor's position is that untrusted data is not an intended use case. The product's behavior will not be changed because some users rely on deserialization of trusted data.
<p>Publish Date: 2020-01-02
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2016-1000027>CVE-2016-1000027</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>Release Date: 2020-01-02</p>
<p>Fix Resolution (org.springframework:spring-web): 5.1.16.RELEASE</p>
<p>Direct dependency fix Resolution (org.springframework.boot:spring-boot-starter-data-rest): 2.1.15.RELEASE</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-0232</summary>
### Vulnerable Library - <b>tomcat-embed-core-9.0.16.jar</b></p>
<p>Core Tomcat implementation</p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/org/apache/tomcat/embed/tomcat-embed-core/9.0.16/tomcat-embed-core-9.0.16.jar</p>
<p>
Dependency Hierarchy:
- spring-boot-starter-data-rest-2.1.3.RELEASE.jar (Root Library)
- spring-boot-starter-web-2.1.3.RELEASE.jar
- spring-boot-starter-tomcat-2.1.3.RELEASE.jar
- :x: **tomcat-embed-core-9.0.16.jar** (Vulnerable Library)
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
When running on Windows with enableCmdLineArguments enabled, the CGI Servlet in Apache Tomcat 9.0.0.M1 to 9.0.17, 8.5.0 to 8.5.39 and 7.0.0 to 7.0.93 is vulnerable to Remote Code Execution due to a bug in the way the JRE passes command line arguments to Windows. The CGI Servlet is disabled by default. The CGI option enableCmdLineArguments is disable by default in Tomcat 9.0.x (and will be disabled by default in all versions in response to this vulnerability). For a detailed explanation of the JRE behaviour, see Markus Wulftange's blog (https://codewhitesec.blogspot.com/2016/02/java-and-command-line-injections-in-windows.html) and this archived MSDN blog (https://web.archive.org/web/20161228144344/https://blogs.msdn.microsoft.com/twistylittlepassagesallalike/2011/04/23/everyone-quotes-command-line-arguments-the-wrong-way/).
<p>Publish Date: 2019-04-15
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2019-0232>CVE-2019-0232</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>8.1</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-0232">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-0232</a></p>
<p>Release Date: 2019-04-15</p>
<p>Fix Resolution (org.apache.tomcat.embed:tomcat-embed-core): 9.0.19</p>
<p>Direct dependency fix Resolution (org.springframework.boot:spring-boot-starter-data-rest): 2.1.5.RELEASE</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-10072</summary>
### Vulnerable Library - <b>tomcat-embed-core-9.0.16.jar</b></p>
<p>Core Tomcat implementation</p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/org/apache/tomcat/embed/tomcat-embed-core/9.0.16/tomcat-embed-core-9.0.16.jar</p>
<p>
Dependency Hierarchy:
- spring-boot-starter-data-rest-2.1.3.RELEASE.jar (Root Library)
- spring-boot-starter-web-2.1.3.RELEASE.jar
- spring-boot-starter-tomcat-2.1.3.RELEASE.jar
- :x: **tomcat-embed-core-9.0.16.jar** (Vulnerable Library)
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
The fix for CVE-2019-0199 was incomplete and did not address HTTP/2 connection window exhaustion on write in Apache Tomcat versions 9.0.0.M1 to 9.0.19 and 8.5.0 to 8.5.40 . By not sending WINDOW_UPDATE messages for the connection window (stream 0) clients were able to cause server-side threads to block eventually leading to thread exhaustion and a DoS.
<p>Publish Date: 2019-06-21
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2019-10072>CVE-2019-10072</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>7.5</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="http://tomcat.apache.org/security-8.html#Fixed_in_Apache_Tomcat_8.5.41">http://tomcat.apache.org/security-8.html#Fixed_in_Apache_Tomcat_8.5.41</a></p>
<p>Release Date: 2019-06-21</p>
<p>Fix Resolution (org.apache.tomcat.embed:tomcat-embed-core): 9.0.20</p>
<p>Direct dependency fix Resolution (org.springframework.boot:spring-boot-starter-data-rest): 2.1.6.RELEASE</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-17563</summary>
### Vulnerable Library - <b>tomcat-embed-core-9.0.16.jar</b></p>
<p>Core Tomcat implementation</p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/org/apache/tomcat/embed/tomcat-embed-core/9.0.16/tomcat-embed-core-9.0.16.jar</p>
<p>
Dependency Hierarchy:
- spring-boot-starter-data-rest-2.1.3.RELEASE.jar (Root Library)
- spring-boot-starter-web-2.1.3.RELEASE.jar
- spring-boot-starter-tomcat-2.1.3.RELEASE.jar
- :x: **tomcat-embed-core-9.0.16.jar** (Vulnerable Library)
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
When using FORM authentication with Apache Tomcat 9.0.0.M1 to 9.0.29, 8.5.0 to 8.5.49 and 7.0.0 to 7.0.98 there was a narrow window where an attacker could perform a session fixation attack. The window was considered too narrow for an exploit to be practical but, erring on the side of caution, this issue has been treated as a security vulnerability.
<p>Publish Date: 2019-12-23
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2019-17563>CVE-2019-17563</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: None
- User Interaction: Required
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-17563">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-17563</a></p>
<p>Release Date: 2019-12-23</p>
<p>Fix Resolution (org.apache.tomcat.embed:tomcat-embed-core): 9.0.30</p>
<p>Direct dependency fix Resolution (org.springframework.boot:spring-boot-starter-data-rest): 2.1.12.RELEASE</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-2020-11996</summary>
### Vulnerable Library - <b>tomcat-embed-core-9.0.16.jar</b></p>
<p>Core Tomcat implementation</p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/org/apache/tomcat/embed/tomcat-embed-core/9.0.16/tomcat-embed-core-9.0.16.jar</p>
<p>
Dependency Hierarchy:
- spring-boot-starter-data-rest-2.1.3.RELEASE.jar (Root Library)
- spring-boot-starter-web-2.1.3.RELEASE.jar
- spring-boot-starter-tomcat-2.1.3.RELEASE.jar
- :x: **tomcat-embed-core-9.0.16.jar** (Vulnerable Library)
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
A specially crafted sequence of HTTP/2 requests sent to Apache Tomcat 10.0.0-M1 to 10.0.0-M5, 9.0.0.M1 to 9.0.35 and 8.5.0 to 8.5.55 could trigger high CPU usage for several seconds. If a sufficient number of such requests were made on concurrent HTTP/2 connections, the server could become unresponsive.
<p>Publish Date: 2020-06-26
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2020-11996>CVE-2020-11996</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>7.5</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://lists.apache.org/thread.html/r5541ef6b6b68b49f76fc4c45695940116da2bcbe0312ef204a00a2e0%40%3Cannounce.tomcat.apache.org%3E,http://tomcat.apache.org/security-10.html">https://lists.apache.org/thread.html/r5541ef6b6b68b49f76fc4c45695940116da2bcbe0312ef204a00a2e0%40%3Cannounce.tomcat.apache.org%3E,http://tomcat.apache.org/security-10.html</a></p>
<p>Release Date: 2020-06-26</p>
<p>Fix Resolution (org.apache.tomcat.embed:tomcat-embed-core): 9.0.36</p>
<p>Direct dependency fix Resolution (org.springframework.boot:spring-boot-starter-data-rest): 2.1.15.RELEASE</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-2020-13934</summary>
### Vulnerable Library - <b>tomcat-embed-core-9.0.16.jar</b></p>
<p>Core Tomcat implementation</p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/org/apache/tomcat/embed/tomcat-embed-core/9.0.16/tomcat-embed-core-9.0.16.jar</p>
<p>
Dependency Hierarchy:
- spring-boot-starter-data-rest-2.1.3.RELEASE.jar (Root Library)
- spring-boot-starter-web-2.1.3.RELEASE.jar
- spring-boot-starter-tomcat-2.1.3.RELEASE.jar
- :x: **tomcat-embed-core-9.0.16.jar** (Vulnerable Library)
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
An h2c direct connection to Apache Tomcat 10.0.0-M1 to 10.0.0-M6, 9.0.0.M5 to 9.0.36 and 8.5.1 to 8.5.56 did not release the HTTP/1.1 processor after the upgrade to HTTP/2. If a sufficient number of such requests were made, an OutOfMemoryException could occur leading to a denial of service.
<p>Publish Date: 2020-07-14
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2020-13934>CVE-2020-13934</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>7.5</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://lists.apache.org/thread.html/r61f411cf82488d6ec213063fc15feeeb88e31b0ca9c29652ee4f962e%40%3Cannounce.tomcat.apache.org%3E">https://lists.apache.org/thread.html/r61f411cf82488d6ec213063fc15feeeb88e31b0ca9c29652ee4f962e%40%3Cannounce.tomcat.apache.org%3E</a></p>
<p>Release Date: 2020-07-14</p>
<p>Fix Resolution (org.apache.tomcat.embed:tomcat-embed-core): 9.0.37</p>
<p>Direct dependency fix Resolution (org.springframework.boot:spring-boot-starter-data-rest): 2.1.16.RELEASE</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-2020-13935</summary>
### Vulnerable Library - <b>tomcat-embed-websocket-9.0.16.jar</b></p>
<p>Core Tomcat implementation</p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/org/apache/tomcat/embed/tomcat-embed-websocket/9.0.16/tomcat-embed-websocket-9.0.16.jar</p>
<p>
Dependency Hierarchy:
- spring-boot-starter-data-rest-2.1.3.RELEASE.jar (Root Library)
- spring-boot-starter-web-2.1.3.RELEASE.jar
- spring-boot-starter-tomcat-2.1.3.RELEASE.jar
- :x: **tomcat-embed-websocket-9.0.16.jar** (Vulnerable Library)
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
The payload length in a WebSocket frame was not correctly validated in Apache Tomcat 10.0.0-M1 to 10.0.0-M6, 9.0.0.M1 to 9.0.36, 8.5.0 to 8.5.56 and 7.0.27 to 7.0.104. Invalid payload lengths could trigger an infinite loop. Multiple requests with invalid payload lengths could lead to a denial of service.
<p>Publish Date: 2020-07-14
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2020-13935>CVE-2020-13935</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>7.5</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://lists.apache.org/thread.html/rd48c72bd3255bda87564d4da3791517c074d94f8a701f93b85752651%40%3Cannounce.tomcat.apache.org%3E">https://lists.apache.org/thread.html/rd48c72bd3255bda87564d4da3791517c074d94f8a701f93b85752651%40%3Cannounce.tomcat.apache.org%3E</a></p>
<p>Release Date: 2020-07-14</p>
<p>Fix Resolution (org.apache.tomcat.embed:tomcat-embed-websocket): 9.0.37</p>
<p>Direct dependency fix Resolution (org.springframework.boot:spring-boot-starter-data-rest): 2.1.16.RELEASE</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-25122</summary>
### Vulnerable Library - <b>tomcat-embed-core-9.0.16.jar</b></p>
<p>Core Tomcat implementation</p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/org/apache/tomcat/embed/tomcat-embed-core/9.0.16/tomcat-embed-core-9.0.16.jar</p>
<p>
Dependency Hierarchy:
- spring-boot-starter-data-rest-2.1.3.RELEASE.jar (Root Library)
- spring-boot-starter-web-2.1.3.RELEASE.jar
- spring-boot-starter-tomcat-2.1.3.RELEASE.jar
- :x: **tomcat-embed-core-9.0.16.jar** (Vulnerable Library)
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
When responding to new h2c connection requests, Apache Tomcat versions 10.0.0-M1 to 10.0.0, 9.0.0.M1 to 9.0.41 and 8.5.0 to 8.5.61 could duplicate request headers and a limited amount of request body from one request to another meaning user A and user B could both see the results of user A's request.
<p>Publish Date: 2021-03-01
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2021-25122>CVE-2021-25122</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>7.5</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: None
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://lists.apache.org/thread.html/r7b95bc248603360501f18c8eb03bb6001ec0ee3296205b34b07105b7%40%3Cannounce.tomcat.apache.org%3E">https://lists.apache.org/thread.html/r7b95bc248603360501f18c8eb03bb6001ec0ee3296205b34b07105b7%40%3Cannounce.tomcat.apache.org%3E</a></p>
<p>Release Date: 2021-03-01</p>
<p>Fix Resolution (org.apache.tomcat.embed:tomcat-embed-core): 9.0.43</p>
<p>Direct dependency fix Resolution (org.springframework.boot:spring-boot-starter-data-rest): 2.3.9.RELEASE</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-2020-5398</summary>
### Vulnerable Library - <b>spring-web-5.1.5.RELEASE.jar</b></p>
<p>Spring Web</p>
<p>Library home page: <a href="https://github.com/spring-projects/spring-framework">https://github.com/spring-projects/spring-framework</a></p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/org/springframework/spring-web/5.1.5.RELEASE/spring-web-5.1.5.RELEASE.jar</p>
<p>
Dependency Hierarchy:
- spring-boot-starter-data-rest-2.1.3.RELEASE.jar (Root Library)
- spring-boot-starter-web-2.1.3.RELEASE.jar
- :x: **spring-web-5.1.5.RELEASE.jar** (Vulnerable Library)
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
In Spring Framework, versions 5.2.x prior to 5.2.3, versions 5.1.x prior to 5.1.13, and versions 5.0.x prior to 5.0.16, an application is vulnerable to a reflected file download (RFD) attack when it sets a "Content-Disposition" header in the response where the filename attribute is derived from user supplied input.
<p>Publish Date: 2020-01-17
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2020-5398>CVE-2020-5398</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: None
- User Interaction: Required
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://pivotal.io/security/cve-2020-5398">https://pivotal.io/security/cve-2020-5398</a></p>
<p>Release Date: 2020-01-17</p>
<p>Fix Resolution (org.springframework:spring-web): 5.1.13.RELEASE</p>
<p>Direct dependency fix Resolution (org.springframework.boot:spring-boot-starter-data-rest): 2.1.12.RELEASE</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-25329</summary>
### Vulnerable Library - <b>tomcat-embed-core-9.0.16.jar</b></p>
<p>Core Tomcat implementation</p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/org/apache/tomcat/embed/tomcat-embed-core/9.0.16/tomcat-embed-core-9.0.16.jar</p>
<p>
Dependency Hierarchy:
- spring-boot-starter-data-rest-2.1.3.RELEASE.jar (Root Library)
- spring-boot-starter-web-2.1.3.RELEASE.jar
- spring-boot-starter-tomcat-2.1.3.RELEASE.jar
- :x: **tomcat-embed-core-9.0.16.jar** (Vulnerable Library)
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
The fix for CVE-2020-9484 was incomplete. When using Apache Tomcat 10.0.0-M1 to 10.0.0, 9.0.0.M1 to 9.0.41, 8.5.0 to 8.5.61 or 7.0.0. to 7.0.107 with a configuration edge case that was highly unlikely to be used, the Tomcat instance was still vulnerable to CVE-2020-9494. Note that both the previously published prerequisites for CVE-2020-9484 and the previously published mitigations for CVE-2020-9484 also apply to this issue.
<p>Publish Date: 2021-03-01
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2021-25329>CVE-2021-25329</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>7.0</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: High
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://lists.apache.org/thread.html/rfe62fbf9d4c314f166fe8c668e50e5d9dd882a99447f26f0367474bf%40%3Cannounce.tomcat.apache.org%3E">https://lists.apache.org/thread.html/rfe62fbf9d4c314f166fe8c668e50e5d9dd882a99447f26f0367474bf%40%3Cannounce.tomcat.apache.org%3E</a></p>
<p>Release Date: 2021-03-01</p>
<p>Fix Resolution (org.apache.tomcat.embed:tomcat-embed-core): 9.0.43</p>
<p>Direct dependency fix Resolution (org.springframework.boot:spring-boot-starter-data-rest): 2.3.9.RELEASE</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-12418</summary>
### Vulnerable Library - <b>tomcat-embed-core-9.0.16.jar</b></p>
<p>Core Tomcat implementation</p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/org/apache/tomcat/embed/tomcat-embed-core/9.0.16/tomcat-embed-core-9.0.16.jar</p>
<p>
Dependency Hierarchy:
- spring-boot-starter-data-rest-2.1.3.RELEASE.jar (Root Library)
- spring-boot-starter-web-2.1.3.RELEASE.jar
- spring-boot-starter-tomcat-2.1.3.RELEASE.jar
- :x: **tomcat-embed-core-9.0.16.jar** (Vulnerable Library)
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
When Apache Tomcat 9.0.0.M1 to 9.0.28, 8.5.0 to 8.5.47, 7.0.0 and 7.0.97 is configured with the JMX Remote Lifecycle Listener, a local attacker without access to the Tomcat process or configuration files is able to manipulate the RMI registry to perform a man-in-the-middle attack to capture user names and passwords used to access the JMX interface. The attacker can then use these credentials to access the JMX interface and gain complete control over the Tomcat instance.
<p>Publish Date: 2019-12-23
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2019-12418>CVE-2019-12418</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>7.0</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: High
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-12418">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-12418</a></p>
<p>Release Date: 2019-12-23</p>
<p>Fix Resolution (org.apache.tomcat.embed:tomcat-embed-core): 9.0.29</p>
<p>Direct dependency fix Resolution (org.springframework.boot:spring-boot-starter-data-rest): 2.1.11.RELEASE</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-2020-9484</summary>
### Vulnerable Library - <b>tomcat-embed-core-9.0.16.jar</b></p>
<p>Core Tomcat implementation</p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/org/apache/tomcat/embed/tomcat-embed-core/9.0.16/tomcat-embed-core-9.0.16.jar</p>
<p>
Dependency Hierarchy:
- spring-boot-starter-data-rest-2.1.3.RELEASE.jar (Root Library)
- spring-boot-starter-web-2.1.3.RELEASE.jar
- spring-boot-starter-tomcat-2.1.3.RELEASE.jar
- :x: **tomcat-embed-core-9.0.16.jar** (Vulnerable Library)
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
When using Apache Tomcat versions 10.0.0-M1 to 10.0.0-M4, 9.0.0.M1 to 9.0.34, 8.5.0 to 8.5.54 and 7.0.0 to 7.0.103 if a) an attacker is able to control the contents and name of a file on the server; and b) the server is configured to use the PersistenceManager with a FileStore; and c) the PersistenceManager is configured with sessionAttributeValueClassNameFilter="null" (the default unless a SecurityManager is used) or a sufficiently lax filter to allow the attacker provided object to be deserialized; and d) the attacker knows the relative file path from the storage location used by FileStore to the file the attacker has control over; then, using a specifically crafted request, the attacker will be able to trigger remote code execution via deserialization of the file under their control. Note that all of conditions a) to d) must be true for the attack to succeed.
<p>Publish Date: 2020-05-20
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2020-9484>CVE-2020-9484</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>7.0</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: High
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-9484">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-9484</a></p>
<p>Release Date: 2020-05-20</p>
<p>Fix Resolution (org.apache.tomcat.embed:tomcat-embed-core): 9.0.35</p>
<p>Direct dependency fix Resolution (org.springframework.boot:spring-boot-starter-data-rest): 2.1.15.RELEASE</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation is available for this issue
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> CVE-2020-5421</summary>
### Vulnerable Library - <b>spring-web-5.1.5.RELEASE.jar</b></p>
<p>Spring Web</p>
<p>Library home page: <a href="https://github.com/spring-projects/spring-framework">https://github.com/spring-projects/spring-framework</a></p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/org/springframework/spring-web/5.1.5.RELEASE/spring-web-5.1.5.RELEASE.jar</p>
<p>
Dependency Hierarchy:
- spring-boot-starter-data-rest-2.1.3.RELEASE.jar (Root Library)
- spring-boot-starter-web-2.1.3.RELEASE.jar
- :x: **spring-web-5.1.5.RELEASE.jar** (Vulnerable Library)
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
In Spring Framework versions 5.2.0 - 5.2.8, 5.1.0 - 5.1.17, 5.0.0 - 5.0.18, 4.3.0 - 4.3.28, and older unsupported versions, the protections against RFD attacks from CVE-2015-5211 may be bypassed depending on the browser used through the use of a jsessionid path parameter.
<p>Publish Date: 2020-09-19
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2020-5421>CVE-2020-5421</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>6.5</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: Low
- User Interaction: Required
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: High
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://tanzu.vmware.com/security/cve-2020-5421">https://tanzu.vmware.com/security/cve-2020-5421</a></p>
<p>Release Date: 2020-09-19</p>
<p>Fix Resolution (org.springframework:spring-web): 5.1.18.RELEASE</p>
<p>Direct dependency fix Resolution (org.springframework.boot:spring-boot-starter-data-rest): 2.1.17.RELEASE</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation is available for this issue
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> CVE-2019-0221</summary>
### Vulnerable Library - <b>tomcat-embed-core-9.0.16.jar</b></p>
<p>Core Tomcat implementation</p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/org/apache/tomcat/embed/tomcat-embed-core/9.0.16/tomcat-embed-core-9.0.16.jar</p>
<p>
Dependency Hierarchy:
- spring-boot-starter-data-rest-2.1.3.RELEASE.jar (Root Library)
- spring-boot-starter-web-2.1.3.RELEASE.jar
- spring-boot-starter-tomcat-2.1.3.RELEASE.jar
- :x: **tomcat-embed-core-9.0.16.jar** (Vulnerable Library)
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
The SSI printenv command in Apache Tomcat 9.0.0.M1 to 9.0.0.17, 8.5.0 to 8.5.39 and 7.0.0 to 7.0.93 echoes user provided data without escaping and is, therefore, vulnerable to XSS. SSI is disabled by default. The printenv command is intended for debugging and is unlikely to be present in a production website.
<p>Publish Date: 2019-05-28
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2019-0221>CVE-2019-0221</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>6.1</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: Low
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-0221">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-0221</a></p>
<p>Release Date: 2019-05-28</p>
<p>Fix Resolution (org.apache.tomcat.embed:tomcat-embed-core): 9.0.19</p>
<p>Direct dependency fix Resolution (org.springframework.boot:spring-boot-starter-data-rest): 2.1.5.RELEASE</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation is available for this issue
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> CVE-2019-10219</summary>
### Vulnerable Library - <b>hibernate-validator-6.0.14.Final.jar</b></p>
<p>Hibernate's Bean Validation (JSR-380) reference implementation.</p>
<p>Library home page: <a href="http://hibernate.org/validator">http://hibernate.org/validator</a></p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/org/hibernate/validator/hibernate-validator/6.0.14.Final/hibernate-validator-6.0.14.Final.jar</p>
<p>
Dependency Hierarchy:
- spring-boot-starter-data-rest-2.1.3.RELEASE.jar (Root Library)
- spring-boot-starter-web-2.1.3.RELEASE.jar
- :x: **hibernate-validator-6.0.14.Final.jar** (Vulnerable Library)
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
A vulnerability was found in Hibernate-Validator. The SafeHtml validator annotation fails to properly sanitize payloads consisting of potentially malicious code in HTML comments and instructions. This vulnerability can result in an XSS attack.
<p>Publish Date: 2019-11-08
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2019-10219>CVE-2019-10219</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>6.1</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: Low
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-10219">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-10219</a></p>
<p>Release Date: 2019-11-08</p>
<p>Fix Resolution (org.hibernate.validator:hibernate-validator): 6.0.18.Final</p>
<p>Direct dependency fix Resolution (org.springframework.boot:spring-boot-starter-data-rest): 2.1.10.RELEASE</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation is available for this issue
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> CVE-2021-24122</summary>
### Vulnerable Library - <b>tomcat-embed-core-9.0.16.jar</b></p>
<p>Core Tomcat implementation</p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/org/apache/tomcat/embed/tomcat-embed-core/9.0.16/tomcat-embed-core-9.0.16.jar</p>
<p>
Dependency Hierarchy:
- spring-boot-starter-data-rest-2.1.3.RELEASE.jar (Root Library)
- spring-boot-starter-web-2.1.3.RELEASE.jar
- spring-boot-starter-tomcat-2.1.3.RELEASE.jar
- :x: **tomcat-embed-core-9.0.16.jar** (Vulnerable Library)
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
When serving resources from a network location using the NTFS file system, Apache Tomcat versions 10.0.0-M1 to 10.0.0-M9, 9.0.0.M1 to 9.0.39, 8.5.0 to 8.5.59 and 7.0.0 to 7.0.106 were susceptible to JSP source code disclosure in some configurations. The root cause was the unexpected behaviour of the JRE API File.getCanonicalPath() which in turn was caused by the inconsistent behaviour of the Windows API (FindFirstFileW) in some circumstances.
<p>Publish Date: 2021-01-14
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2021-24122>CVE-2021-24122</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>5.9</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: 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://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-24122">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-24122</a></p>
<p>Release Date: 2021-01-14</p>
<p>Fix Resolution (org.apache.tomcat.embed:tomcat-embed-core): 9.0.40</p>
<p>Direct dependency fix Resolution (org.springframework.boot:spring-boot-starter-data-rest): 2.2.12.RELEASE</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation is available for this issue
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> CVE-2020-10693</summary>
### Vulnerable Library - <b>hibernate-validator-6.0.14.Final.jar</b></p>
<p>Hibernate's Bean Validation (JSR-380) reference implementation.</p>
<p>Library home page: <a href="http://hibernate.org/validator">http://hibernate.org/validator</a></p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/org/hibernate/validator/hibernate-validator/6.0.14.Final/hibernate-validator-6.0.14.Final.jar</p>
<p>
Dependency Hierarchy:
- spring-boot-starter-data-rest-2.1.3.RELEASE.jar (Root Library)
- spring-boot-starter-web-2.1.3.RELEASE.jar
- :x: **hibernate-validator-6.0.14.Final.jar** (Vulnerable Library)
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
A flaw was found in Hibernate Validator version 6.1.2.Final. A bug in the message interpolation processor enables invalid EL expressions to be evaluated as if they were valid. This flaw allows attackers to bypass input sanitation (escaping, stripping) controls that developers may have put in place when handling user-controlled data in error messages.
<p>Publish Date: 2020-05-06
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2020-10693>CVE-2020-10693</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>5.3</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: Low
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://hibernate.atlassian.net/projects/HV/issues/HV-1774">https://hibernate.atlassian.net/projects/HV/issues/HV-1774</a></p>
<p>Release Date: 2020-05-06</p>
<p>Fix Resolution (org.hibernate.validator:hibernate-validator): 6.0.20.Final</p>
<p>Direct dependency fix Resolution (org.springframework.boot:spring-boot-starter-data-rest): 2.1.15.RELEASE</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation is available for this issue
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> CVE-2020-1935</summary>
### Vulnerable Library - <b>tomcat-embed-core-9.0.16.jar</b></p>
<p>Core Tomcat implementation</p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/org/apache/tomcat/embed/tomcat-embed-core/9.0.16/tomcat-embed-core-9.0.16.jar</p>
<p>
Dependency Hierarchy:
- spring-boot-starter-data-rest-2.1.3.RELEASE.jar (Root Library)
- spring-boot-starter-web-2.1.3.RELEASE.jar
- spring-boot-starter-tomcat-2.1.3.RELEASE.jar
- :x: **tomcat-embed-core-9.0.16.jar** (Vulnerable Library)
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
In Apache Tomcat 9.0.0.M1 to 9.0.30, 8.5.0 to 8.5.50 and 7.0.0 to 7.0.99 the HTTP header parsing code used an approach to end-of-line parsing that allowed some invalid HTTP headers to be parsed as valid. This led to a possibility of HTTP Request Smuggling if Tomcat was located behind a reverse proxy that incorrectly handled the invalid Transfer-Encoding header in a particular manner. Such a reverse proxy is considered unlikely.
<p>Publish Date: 2020-02-24
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2020-1935>CVE-2020-1935</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>4.8</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: Low
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/advisories/GHSA-6v7p-v754-j89v">https://github.com/advisories/GHSA-6v7p-v754-j89v</a></p>
<p>Release Date: 2020-02-24</p>
<p>Fix Resolution (org.apache.tomcat.embed:tomcat-embed-core): 9.0.31</p>
<p>Direct dependency fix Resolution (org.springframework.boot:spring-boot-starter-data-rest): 2.1.13.RELEASE</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation is available for this issue
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png?' width=19 height=20> CVE-2020-13943</summary>
### Vulnerable Library - <b>tomcat-embed-core-9.0.16.jar</b></p>
<p>Core Tomcat implementation</p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/org/apache/tomcat/embed/tomcat-embed-core/9.0.16/tomcat-embed-core-9.0.16.jar</p>
<p>
Dependency Hierarchy:
- spring-boot-starter-data-rest-2.1.3.RELEASE.jar (Root Library)
- spring-boot-starter-web-2.1.3.RELEASE.jar
- spring-boot-starter-tomcat-2.1.3.RELEASE.jar
- :x: **tomcat-embed-core-9.0.16.jar** (Vulnerable Library)
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
If an HTTP/2 client connecting to Apache Tomcat 10.0.0-M1 to 10.0.0-M7, 9.0.0.M1 to 9.0.37 or 8.5.0 to 8.5.57 exceeded the agreed maximum number of concurrent streams for a connection (in violation of the HTTP/2 protocol), it was possible that a subsequent request made on that connection could contain HTTP headers - including HTTP/2 pseudo headers - from a previous request rather than the intended headers. This could lead to users seeing responses for unexpected resources.
<p>Publish Date: 2020-10-12
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2020-13943>CVE-2020-13943</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>4.3</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: 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://lists.apache.org/thread.html/r4a390027eb27e4550142fac6c8317cc684b157ae314d31514747f307%40%3Cannounce.tomcat.apache.org%3E">https://lists.apache.org/thread.html/r4a390027eb27e4550142fac6c8317cc684b157ae314d31514747f307%40%3Cannounce.tomcat.apache.org%3E</a></p>
<p>Release Date: 2020-10-12</p>
<p>Fix Resolution (org.apache.tomcat.embed:tomcat-embed-core): 9.0.38</p>
<p>Direct dependency fix Resolution (org.springframework.boot:spring-boot-starter-data-rest): 2.1.17.RELEASE</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation is available for this issue
</details>
***
<p>:rescue_worker_helmet: Automatic Remediation is available for this issue.</p> | non_priority | spring boot starter data rest release jar vulnerabilities highest severity is vulnerable library spring boot starter data rest release jar path to dependency file pom xml path to vulnerable library home wss scanner repository org apache tomcat embed tomcat embed core tomcat embed core jar vulnerabilities cve severity cvss dependency type fixed in spring boot starter data rest version remediation available high spring web release jar transitive release high tomcat embed core jar transitive release high tomcat embed core jar transitive release high tomcat embed core jar transitive release high tomcat embed core jar transitive release high tomcat embed core jar transitive release high tomcat embed websocket jar transitive release high tomcat embed core jar transitive release high spring web release jar transitive release high tomcat embed core jar transitive release high tomcat embed core jar transitive release high tomcat embed core jar transitive release medium spring web release jar transitive release medium tomcat embed core jar transitive release medium hibernate validator final jar transitive release medium tomcat embed core jar transitive release medium hibernate validator final jar transitive release medium tomcat embed core jar transitive release medium tomcat embed core jar transitive release details cve vulnerable library spring web release jar spring web library home page a href path to dependency file pom xml path to vulnerable library home wss scanner repository org springframework spring web release spring web release jar dependency hierarchy spring boot starter data rest release jar root library spring boot starter web release jar x spring web release jar vulnerable library found in base branch master vulnerability details pivotal spring framework through suffers from a potential remote code execution rce issue if used for java deserialization of untrusted data depending on how the library is implemented within a product this issue may or not occur and authentication may be required note the vendor s position is that untrusted data is not an intended use case the product s behavior will not be changed because some users rely on deserialization of trusted data 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 release date fix resolution org springframework spring web release direct dependency fix resolution org springframework boot spring boot starter data rest release rescue worker helmet automatic remediation is available for this issue cve vulnerable library tomcat embed core jar core tomcat implementation path to dependency file pom xml path to vulnerable library home wss scanner repository org apache tomcat embed tomcat embed core tomcat embed core jar dependency hierarchy spring boot starter data rest release jar root library spring boot starter web release jar spring boot starter tomcat release jar x tomcat embed core jar vulnerable library found in base branch master vulnerability details when running on windows with enablecmdlinearguments enabled the cgi servlet in apache tomcat to to and to is vulnerable to remote code execution due to a bug in the way the jre passes command line arguments to windows the cgi servlet is disabled by default the cgi option enablecmdlinearguments is disable by default in tomcat x and will be disabled by default in all versions in response to this vulnerability for a detailed explanation of the jre behaviour see markus wulftange s blog and this archived msdn blog publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity high privileges required none user interaction none scope unchanged impact metrics confidentiality impact high integrity impact high availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution org apache tomcat embed tomcat embed core direct dependency fix resolution org springframework boot spring boot starter data rest release rescue worker helmet automatic remediation is available for this issue cve vulnerable library tomcat embed core jar core tomcat implementation path to dependency file pom xml path to vulnerable library home wss scanner repository org apache tomcat embed tomcat embed core tomcat embed core jar dependency hierarchy spring boot starter data rest release jar root library spring boot starter web release jar spring boot starter tomcat release jar x tomcat embed core jar vulnerable library found in base branch master vulnerability details the fix for cve was incomplete and did not address http connection window exhaustion on write in apache tomcat versions to and to by not sending window update messages for the connection window stream clients were able to cause server side threads to block eventually leading to thread exhaustion and a dos publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact none integrity impact none availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution org apache tomcat embed tomcat embed core direct dependency fix resolution org springframework boot spring boot starter data rest release rescue worker helmet automatic remediation is available for this issue cve vulnerable library tomcat embed core jar core tomcat implementation path to dependency file pom xml path to vulnerable library home wss scanner repository org apache tomcat embed tomcat embed core tomcat embed core jar dependency hierarchy spring boot starter data rest release jar root library spring boot starter web release jar spring boot starter tomcat release jar x tomcat embed core jar vulnerable library found in base branch master vulnerability details when using form authentication with apache tomcat to to and to there was a narrow window where an attacker could perform a session fixation attack the window was considered too narrow for an exploit to be practical but erring on the side of caution this issue has been treated as a security vulnerability publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity high privileges required none user interaction required scope unchanged impact metrics confidentiality impact high integrity impact high availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution org apache tomcat embed tomcat embed core direct dependency fix resolution org springframework boot spring boot starter data rest release rescue worker helmet automatic remediation is available for this issue cve vulnerable library tomcat embed core jar core tomcat implementation path to dependency file pom xml path to vulnerable library home wss scanner repository org apache tomcat embed tomcat embed core tomcat embed core jar dependency hierarchy spring boot starter data rest release jar root library spring boot starter web release jar spring boot starter tomcat release jar x tomcat embed core jar vulnerable library found in base branch master vulnerability details a specially crafted sequence of http requests sent to apache tomcat to to and to could trigger high cpu usage for several seconds if a sufficient number of such requests were made on concurrent http connections the server could become unresponsive publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact none integrity impact none availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution org apache tomcat embed tomcat embed core direct dependency fix resolution org springframework boot spring boot starter data rest release rescue worker helmet automatic remediation is available for this issue cve vulnerable library tomcat embed core jar core tomcat implementation path to dependency file pom xml path to vulnerable library home wss scanner repository org apache tomcat embed tomcat embed core tomcat embed core jar dependency hierarchy spring boot starter data rest release jar root library spring boot starter web release jar spring boot starter tomcat release jar x tomcat embed core jar vulnerable library found in base branch master vulnerability details an direct connection to apache tomcat to to and to did not release the http processor after the upgrade to http if a sufficient number of such requests were made an outofmemoryexception could occur leading to a denial of service publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact none integrity impact none availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution org apache tomcat embed tomcat embed core direct dependency fix resolution org springframework boot spring boot starter data rest release rescue worker helmet automatic remediation is available for this issue cve vulnerable library tomcat embed websocket jar core tomcat implementation path to dependency file pom xml path to vulnerable library home wss scanner repository org apache tomcat embed tomcat embed websocket tomcat embed websocket jar dependency hierarchy spring boot starter data rest release jar root library spring boot starter web release jar spring boot starter tomcat release jar x tomcat embed websocket jar vulnerable library found in base branch master vulnerability details the payload length in a websocket frame was not correctly validated in apache tomcat to to to and to invalid payload lengths could trigger an infinite loop multiple requests with invalid payload lengths could lead to a denial of service publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact none integrity impact none availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution org apache tomcat embed tomcat embed websocket direct dependency fix resolution org springframework boot spring boot starter data rest release rescue worker helmet automatic remediation is available for this issue cve vulnerable library tomcat embed core jar core tomcat implementation path to dependency file pom xml path to vulnerable library home wss scanner repository org apache tomcat embed tomcat embed core tomcat embed core jar dependency hierarchy spring boot starter data rest release jar root library spring boot starter web release jar spring boot starter tomcat release jar x tomcat embed core jar vulnerable library found in base branch master vulnerability details when responding to new connection requests apache tomcat versions to to and to could duplicate request headers and a limited amount of request body from one request to another meaning user a and user b could both see the results of user a s request publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact high integrity impact none availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution org apache tomcat embed tomcat embed core direct dependency fix resolution org springframework boot spring boot starter data rest release rescue worker helmet automatic remediation is available for this issue cve vulnerable library spring web release jar spring web library home page a href path to dependency file pom xml path to vulnerable library home wss scanner repository org springframework spring web release spring web release jar dependency hierarchy spring boot starter data rest release jar root library spring boot starter web release jar x spring web release jar vulnerable library found in base branch master vulnerability details in spring framework versions x prior to versions x prior to and versions x prior to an application is vulnerable to a reflected file download rfd attack when it sets a content disposition header in the response where the filename attribute is derived from user supplied input publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity high privileges required none user interaction required scope unchanged impact metrics confidentiality impact high integrity impact high availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution org springframework spring web release direct dependency fix resolution org springframework boot spring boot starter data rest release rescue worker helmet automatic remediation is available for this issue cve vulnerable library tomcat embed core jar core tomcat implementation path to dependency file pom xml path to vulnerable library home wss scanner repository org apache tomcat embed tomcat embed core tomcat embed core jar dependency hierarchy spring boot starter data rest release jar root library spring boot starter web release jar spring boot starter tomcat release jar x tomcat embed core jar vulnerable library found in base branch master vulnerability details the fix for cve was incomplete when using apache tomcat to to to or to with a configuration edge case that was highly unlikely to be used the tomcat instance was still vulnerable to cve note that both the previously published prerequisites for cve and the previously published mitigations for cve also apply to this issue publish date url a href cvss score details base score metrics exploitability metrics attack vector local attack complexity high privileges required low user interaction none scope unchanged impact metrics confidentiality impact high integrity impact high availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution org apache tomcat embed tomcat embed core direct dependency fix resolution org springframework boot spring boot starter data rest release rescue worker helmet automatic remediation is available for this issue cve vulnerable library tomcat embed core jar core tomcat implementation path to dependency file pom xml path to vulnerable library home wss scanner repository org apache tomcat embed tomcat embed core tomcat embed core jar dependency hierarchy spring boot starter data rest release jar root library spring boot starter web release jar spring boot starter tomcat release jar x tomcat embed core jar vulnerable library found in base branch master vulnerability details when apache tomcat to to and is configured with the jmx remote lifecycle listener a local attacker without access to the tomcat process or configuration files is able to manipulate the rmi registry to perform a man in the middle attack to capture user names and passwords used to access the jmx interface the attacker can then use these credentials to access the jmx interface and gain complete control over the tomcat instance publish date url a href cvss score details base score metrics exploitability metrics attack vector local attack complexity high privileges required low user interaction none scope unchanged impact metrics confidentiality impact high integrity impact high availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution org apache tomcat embed tomcat embed core direct dependency fix resolution org springframework boot spring boot starter data rest release rescue worker helmet automatic remediation is available for this issue cve vulnerable library tomcat embed core jar core tomcat implementation path to dependency file pom xml path to vulnerable library home wss scanner repository org apache tomcat embed tomcat embed core tomcat embed core jar dependency hierarchy spring boot starter data rest release jar root library spring boot starter web release jar spring boot starter tomcat release jar x tomcat embed core jar vulnerable library found in base branch master vulnerability details when using apache tomcat versions to to to and to if a an attacker is able to control the contents and name of a file on the server and b the server is configured to use the persistencemanager with a filestore and c the persistencemanager is configured with sessionattributevalueclassnamefilter null the default unless a securitymanager is used or a sufficiently lax filter to allow the attacker provided object to be deserialized and d the attacker knows the relative file path from the storage location used by filestore to the file the attacker has control over then using a specifically crafted request the attacker will be able to trigger remote code execution via deserialization of the file under their control note that all of conditions a to d must be true for the attack to succeed publish date url a href cvss score details base score metrics exploitability metrics attack vector local attack complexity high privileges required low user interaction none scope unchanged impact metrics confidentiality impact high integrity impact high availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution org apache tomcat embed tomcat embed core direct dependency fix resolution org springframework boot spring boot starter data rest release rescue worker helmet automatic remediation is available for this issue cve vulnerable library spring web release jar spring web library home page a href path to dependency file pom xml path to vulnerable library home wss scanner repository org springframework spring web release spring web release jar dependency hierarchy spring boot starter data rest release jar root library spring boot starter web release jar x spring web release jar vulnerable library found in base branch master vulnerability details in spring framework versions and older unsupported versions the protections against rfd attacks from cve may be bypassed depending on the browser used through the use of a jsessionid path parameter publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity high privileges required low user interaction required scope changed impact metrics confidentiality impact low integrity impact high availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution org springframework spring web release direct dependency fix resolution org springframework boot spring boot starter data rest release rescue worker helmet automatic remediation is available for this issue cve vulnerable library tomcat embed core jar core tomcat implementation path to dependency file pom xml path to vulnerable library home wss scanner repository org apache tomcat embed tomcat embed core tomcat embed core jar dependency hierarchy spring boot starter data rest release jar root library spring boot starter web release jar spring boot starter tomcat release jar x tomcat embed core jar vulnerable library found in base branch master vulnerability details the ssi printenv command in apache tomcat to to and to echoes user provided data without escaping and is therefore vulnerable to xss ssi is disabled by default the printenv command is intended for debugging and is unlikely to be present in a production website publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction required scope changed impact metrics confidentiality impact low integrity impact low availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution org apache tomcat embed tomcat embed core direct dependency fix resolution org springframework boot spring boot starter data rest release rescue worker helmet automatic remediation is available for this issue cve vulnerable library hibernate validator final jar hibernate s bean validation jsr reference implementation library home page a href path to dependency file pom xml path to vulnerable library home wss scanner repository org hibernate validator hibernate validator final hibernate validator final jar dependency hierarchy spring boot starter data rest release jar root library spring boot starter web release jar x hibernate validator final jar vulnerable library found in base branch master vulnerability details a vulnerability was found in hibernate validator the safehtml validator annotation fails to properly sanitize payloads consisting of potentially malicious code in html comments and instructions this vulnerability can result in an xss attack publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction required scope changed impact metrics confidentiality impact low integrity impact low availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution org hibernate validator hibernate validator final direct dependency fix resolution org springframework boot spring boot starter data rest release rescue worker helmet automatic remediation is available for this issue cve vulnerable library tomcat embed core jar core tomcat implementation path to dependency file pom xml path to vulnerable library home wss scanner repository org apache tomcat embed tomcat embed core tomcat embed core jar dependency hierarchy spring boot starter data rest release jar root library spring boot starter web release jar spring boot starter tomcat release jar x tomcat embed core jar vulnerable library found in base branch master vulnerability details when serving resources from a network location using the ntfs file system apache tomcat versions to to to and to were susceptible to jsp source code disclosure in some configurations the root cause was the unexpected behaviour of the jre api file getcanonicalpath which in turn was caused by the inconsistent behaviour of the windows api findfirstfilew in some circumstances 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 org apache tomcat embed tomcat embed core direct dependency fix resolution org springframework boot spring boot starter data rest release rescue worker helmet automatic remediation is available for this issue cve vulnerable library hibernate validator final jar hibernate s bean validation jsr reference implementation library home page a href path to dependency file pom xml path to vulnerable library home wss scanner repository org hibernate validator hibernate validator final hibernate validator final jar dependency hierarchy spring boot starter data rest release jar root library spring boot starter web release jar x hibernate validator final jar vulnerable library found in base branch master vulnerability details a flaw was found in hibernate validator version final a bug in the message interpolation processor enables invalid el expressions to be evaluated as if they were valid this flaw allows attackers to bypass input sanitation escaping stripping controls that developers may have put in place when handling user controlled data in error messages publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope unchanged impact metrics confidentiality impact none integrity impact low availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution org hibernate validator hibernate validator final direct dependency fix resolution org springframework boot spring boot starter data rest release rescue worker helmet automatic remediation is available for this issue cve vulnerable library tomcat embed core jar core tomcat implementation path to dependency file pom xml path to vulnerable library home wss scanner repository org apache tomcat embed tomcat embed core tomcat embed core jar dependency hierarchy spring boot starter data rest release jar root library spring boot starter web release jar spring boot starter tomcat release jar x tomcat embed core jar vulnerable library found in base branch master vulnerability details in apache tomcat to to and to the http header parsing code used an approach to end of line parsing that allowed some invalid http headers to be parsed as valid this led to a possibility of http request smuggling if tomcat was located behind a reverse proxy that incorrectly handled the invalid transfer encoding header in a particular manner such a reverse proxy is considered unlikely publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity high privileges required none user interaction none scope unchanged impact metrics confidentiality impact low integrity impact low availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution org apache tomcat embed tomcat embed core direct dependency fix resolution org springframework boot spring boot starter data rest release rescue worker helmet automatic remediation is available for this issue cve vulnerable library tomcat embed core jar core tomcat implementation path to dependency file pom xml path to vulnerable library home wss scanner repository org apache tomcat embed tomcat embed core tomcat embed core jar dependency hierarchy spring boot starter data rest release jar root library spring boot starter web release jar spring boot starter tomcat release jar x tomcat embed core jar vulnerable library found in base branch master vulnerability details if an http client connecting to apache tomcat to to or to exceeded the agreed maximum number of concurrent streams for a connection in violation of the http protocol it was possible that a subsequent request made on that connection could contain http headers including http pseudo headers from a previous request rather than the intended headers this could lead to users seeing responses for unexpected resources 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 org apache tomcat embed tomcat embed core direct dependency fix resolution org springframework boot spring boot starter data rest release rescue worker helmet automatic remediation is available for this issue rescue worker helmet automatic remediation is available for this issue | 0 |
225,956 | 17,293,787,981 | IssuesEvent | 2021-07-25 10:03:03 | RandomCoderOrg/ubuntu-on-android | https://api.github.com/repos/RandomCoderOrg/ubuntu-on-android | opened | Discribution url is not defined for gpu architecture armv8l | documentation question | Hello please help me !!
When I type this command :
# download installer
curl -L -o install.sh https://git.io/hippo-installer
# run the installer
bash install.sh
# Install ubuntu with this command
hippo --install
/ / /
I get error :
I have a 64-bit armv8-a (32 bit mode) in my android phone
| 1.0 | Discribution url is not defined for gpu architecture armv8l - Hello please help me !!
When I type this command :
# download installer
curl -L -o install.sh https://git.io/hippo-installer
# run the installer
bash install.sh
# Install ubuntu with this command
hippo --install
/ / /
I get error :
I have a 64-bit armv8-a (32 bit mode) in my android phone
| non_priority | discribution url is not defined for gpu architecture hello please help me when i type this command download installer curl l o install sh run the installer bash install sh install ubuntu with this command hippo install i get error i have a bit a bit mode in my android phone | 0 |
775,407 | 27,233,338,444 | IssuesEvent | 2023-02-21 14:43:22 | zowe/zowe-cli | https://api.github.com/repos/zowe/zowe-cli | closed | Zowe CLI - Known Passing CII Badge Requirements | priority-high stale research | - [x] (5) LFX Security Training (16 - 20 hours / person)
- [x] (5) Issue acknowledgement (specific timeframe: 2 - 12 months)
- [ ] (2) Address Sonar hotspots (only for protected branches) | 1.0 | Zowe CLI - Known Passing CII Badge Requirements - - [x] (5) LFX Security Training (16 - 20 hours / person)
- [x] (5) Issue acknowledgement (specific timeframe: 2 - 12 months)
- [ ] (2) Address Sonar hotspots (only for protected branches) | priority | zowe cli known passing cii badge requirements lfx security training hours person issue acknowledgement specific timeframe months address sonar hotspots only for protected branches | 1 |
199,414 | 22,693,327,601 | IssuesEvent | 2022-07-05 01:13:39 | ondrejrozsypal/test | https://api.github.com/repos/ondrejrozsypal/test | closed | CVE-2020-13596 (Medium) detected in Django-1.8.15-py2.py3-none-any.whl - autoclosed | security vulnerability | ## CVE-2020-13596 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>Django-1.8.15-py2.py3-none-any.whl</b></p></summary>
<p>A high-level Python Web framework that encourages rapid development and clean, pragmatic design.</p>
<p>Library home page: <a href="https://files.pythonhosted.org/packages/f3/bb/865626b78c2e87acd4dc1bd8f8cb0a49582ec65e40968f3d24f594bba600/Django-1.8.15-py2.py3-none-any.whl">https://files.pythonhosted.org/packages/f3/bb/865626b78c2e87acd4dc1bd8f8cb0a49582ec65e40968f3d24f594bba600/Django-1.8.15-py2.py3-none-any.whl</a></p>
<p>Path to dependency file: test/pip-requirements.txt</p>
<p>Path to vulnerable library: test/pip-requirements.txt</p>
<p>
Dependency Hierarchy:
- :x: **Django-1.8.15-py2.py3-none-any.whl** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/ondrejrozsypal/test/commit/51d606f8cf183f8bded6ae4a5b676ffd56692f0e">51d606f8cf183f8bded6ae4a5b676ffd56692f0e</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
An issue was discovered in Django 2.2 before 2.2.13 and 3.0 before 3.0.7. Query parameters generated by the Django admin ForeignKeyRawIdWidget were not properly URL encoded, leading to a possibility of an XSS attack.
<p>Publish Date: 2020-06-03
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-13596>CVE-2020-13596</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>6.1</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: Low
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://www.djangoproject.com/weblog/2020/jun/03/security-releases/">https://www.djangoproject.com/weblog/2020/jun/03/security-releases/</a></p>
<p>Release Date: 2020-06-03</p>
<p>Fix Resolution: 3.0.7,2.2.13</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-13596 (Medium) detected in Django-1.8.15-py2.py3-none-any.whl - autoclosed - ## CVE-2020-13596 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>Django-1.8.15-py2.py3-none-any.whl</b></p></summary>
<p>A high-level Python Web framework that encourages rapid development and clean, pragmatic design.</p>
<p>Library home page: <a href="https://files.pythonhosted.org/packages/f3/bb/865626b78c2e87acd4dc1bd8f8cb0a49582ec65e40968f3d24f594bba600/Django-1.8.15-py2.py3-none-any.whl">https://files.pythonhosted.org/packages/f3/bb/865626b78c2e87acd4dc1bd8f8cb0a49582ec65e40968f3d24f594bba600/Django-1.8.15-py2.py3-none-any.whl</a></p>
<p>Path to dependency file: test/pip-requirements.txt</p>
<p>Path to vulnerable library: test/pip-requirements.txt</p>
<p>
Dependency Hierarchy:
- :x: **Django-1.8.15-py2.py3-none-any.whl** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/ondrejrozsypal/test/commit/51d606f8cf183f8bded6ae4a5b676ffd56692f0e">51d606f8cf183f8bded6ae4a5b676ffd56692f0e</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
An issue was discovered in Django 2.2 before 2.2.13 and 3.0 before 3.0.7. Query parameters generated by the Django admin ForeignKeyRawIdWidget were not properly URL encoded, leading to a possibility of an XSS attack.
<p>Publish Date: 2020-06-03
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-13596>CVE-2020-13596</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>6.1</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: Low
- Integrity Impact: Low
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://www.djangoproject.com/weblog/2020/jun/03/security-releases/">https://www.djangoproject.com/weblog/2020/jun/03/security-releases/</a></p>
<p>Release Date: 2020-06-03</p>
<p>Fix Resolution: 3.0.7,2.2.13</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 django none any whl autoclosed cve medium severity vulnerability vulnerable library django none any whl a high level python web framework that encourages rapid development and clean pragmatic design library home page a href path to dependency file test pip requirements txt path to vulnerable library test pip requirements txt dependency hierarchy x django none any whl vulnerable library found in head commit a href vulnerability details an issue was discovered in django before and before query parameters generated by the django admin foreignkeyrawidwidget were not properly url encoded leading to a possibility of an xss attack publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction required scope changed impact metrics confidentiality impact low integrity impact low availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution step up your open source security game with whitesource | 0 |
600,135 | 18,290,151,972 | IssuesEvent | 2021-10-05 14:29:06 | CDH-Studio/I-Talent | https://api.github.com/repos/CDH-Studio/I-Talent | closed | The Email and Job Title not read to screen reader | :lady_beetle: bug :warning: high priority :wheelchair: accessibility | **Describe the bug**
The job title and email should be read even though they are disabled in the contact form
| 1.0 | The Email and Job Title not read to screen reader - **Describe the bug**
The job title and email should be read even though they are disabled in the contact form
| priority | the email and job title not read to screen reader describe the bug the job title and email should be read even though they are disabled in the contact form | 1 |
272,405 | 23,671,191,776 | IssuesEvent | 2022-08-27 11:31:46 | marco-at-bit/test-quality-sdk | https://api.github.com/repos/marco-at-bit/test-quality-sdk | closed | Req with highest prio | bug TestQuality Highest |
## Steps to Reproduce:
### Step 1 <span style="color:#ff9000"> **[Pending]** </span>
Step nr one
### Step 2 <span style="color:#ff9000"> **[Pending]** </span>
Second step
| 1.0 | Req with highest prio -
## Steps to Reproduce:
### Step 1 <span style="color:#ff9000"> **[Pending]** </span>
Step nr one
### Step 2 <span style="color:#ff9000"> **[Pending]** </span>
Second step
| non_priority | req with highest prio steps to reproduce step step nr one step second step | 0 |
191,317 | 15,284,819,322 | IssuesEvent | 2021-02-23 12:45:39 | allenai/ir_datasets | https://api.github.com/repos/allenai/ir_datasets | opened | arriving at documentation page from search engine is disorienting | documentation | The flow from the main result index page seems fine, but when you reach a documentation page from a search engine, it's rather disorienting. Some description at the top would probably help. | 1.0 | arriving at documentation page from search engine is disorienting - The flow from the main result index page seems fine, but when you reach a documentation page from a search engine, it's rather disorienting. Some description at the top would probably help. | non_priority | arriving at documentation page from search engine is disorienting the flow from the main result index page seems fine but when you reach a documentation page from a search engine it s rather disorienting some description at the top would probably help | 0 |
258,728 | 27,579,395,182 | IssuesEvent | 2023-03-08 15:13:44 | Dima2021/railsgoat | https://api.github.com/repos/Dima2021/railsgoat | opened | better_errors-2.5.1.gem: 7 vulnerabilities (highest severity is: 10.0) | Mend: dependency security vulnerability | <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>better_errors-2.5.1.gem</b></p></summary>
<p>Provides a better error page for Rails and other Rack apps. Includes source code inspection, a live REPL and local/instance variable inspection for all stack frames.</p>
<p>Library home page: <a href="https://rubygems.org/gems/better_errors-2.5.1.gem">https://rubygems.org/gems/better_errors-2.5.1.gem</a></p>
<p>
</details>
## Vulnerabilities
| CVE | Severity | <img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS | Dependency | Type | Fixed in (better_errors version) | Remediation Available |
| ------------- | ------------- | ----- | ----- | ----- | ------------- | --- |
| [CVE-2022-30123](https://www.mend.io/vulnerability-database/CVE-2022-30123) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 10.0 | rack-2.2.3.gem | Transitive | N/A* | ❌ |
| [CVE-2021-39197](https://www.mend.io/vulnerability-database/CVE-2021-39197) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 8.8 | better_errors-2.5.1.gem | Direct | better_errors - 2.8.0 | ❌ |
| [CVE-2022-30122](https://www.mend.io/vulnerability-database/CVE-2022-30122) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | rack-2.2.3.gem | Transitive | N/A* | ❌ |
| [CVE-2022-44571](https://www.mend.io/vulnerability-database/CVE-2022-44571) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | rack-2.2.3.gem | Transitive | N/A* | ❌ |
| [CVE-2022-44570](https://www.mend.io/vulnerability-database/CVE-2022-44570) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | rack-2.2.3.gem | Transitive | N/A* | ❌ |
| [CVE-2022-44572](https://www.mend.io/vulnerability-database/CVE-2022-44572) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | rack-2.2.3.gem | Transitive | N/A* | ❌ |
| [CVE-2023-27530](https://www.mend.io/vulnerability-database/CVE-2023-27530) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 5.5 | rack-2.2.3.gem | Transitive | N/A* | ❌ |
<p>*For some transitive vulnerabilities, there is no version of direct dependency with a fix. Check the section "Details" below to see if there is a version of transitive dependency where vulnerability is fixed.</p>
## Details
<details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2022-30123</summary>
### Vulnerable Library - <b>rack-2.2.3.gem</b></p>
<p>Rack provides a minimal, modular and adaptable interface for developing
web applications in Ruby. By wrapping HTTP requests and responses in
the simplest way possible, it unifies and distills the API for web
servers, web frameworks, and software in between (the so-called
middleware) into a single method call.
</p>
<p>Library home page: <a href="https://rubygems.org/gems/rack-2.2.3.gem">https://rubygems.org/gems/rack-2.2.3.gem</a></p>
<p>
Dependency Hierarchy:
- better_errors-2.5.1.gem (Root Library)
- :x: **rack-2.2.3.gem** (Vulnerable Library)
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
A sequence injection vulnerability exists in Rack <2.0.9.1, <2.1.4.1 and <2.2.3.1 which could allow is a possible shell escape in the Lint and CommonLogger components of Rack.
<p>Publish Date: 2022-12-05
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-30123>CVE-2022-30123</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>10.0</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/advisories/GHSA-wq4h-7r42-5hrr">https://github.com/advisories/GHSA-wq4h-7r42-5hrr</a></p>
<p>Release Date: 2022-12-05</p>
<p>Fix Resolution: rack - 2.0.9.1,2.1.4.1,2.2.3.1</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2021-39197</summary>
### Vulnerable Library - <b>better_errors-2.5.1.gem</b></p>
<p>Provides a better error page for Rails and other Rack apps. Includes source code inspection, a live REPL and local/instance variable inspection for all stack frames.</p>
<p>Library home page: <a href="https://rubygems.org/gems/better_errors-2.5.1.gem">https://rubygems.org/gems/better_errors-2.5.1.gem</a></p>
<p>
Dependency Hierarchy:
- :x: **better_errors-2.5.1.gem** (Vulnerable Library)
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
better_errors is an open source replacement for the standard Rails error page with more information rich error pages. It is also usable outside of Rails in any Rack app as Rack middleware. better_errors prior to 2.8.0 did not implement CSRF protection for its internal requests. It also did not enforce the correct "Content-Type" header for these requests, which allowed a cross-origin "simple request" to be made without CORS protection. These together left an application with better_errors enabled open to cross-origin attacks. As a developer tool, better_errors documentation strongly recommends addition only to the `development` bundle group, so this vulnerability should only affect development environments. Please ensure that your project limits better_errors to the `development` group (or the non-Rails equivalent). Starting with release 2.8.x, CSRF protection is enforced. It is recommended that you upgrade to the latest release, or minimally to "~> 2.8.3". There are no known workarounds to mitigate the risk of using older releases of better_errors.
<p>Publish Date: 2021-09-07
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2021-39197>CVE-2021-39197</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: None
- User Interaction: Required
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/BetterErrors/better_errors/security/advisories/GHSA-w3j4-76qw-wwjm">https://github.com/BetterErrors/better_errors/security/advisories/GHSA-w3j4-76qw-wwjm</a></p>
<p>Release Date: 2021-09-07</p>
<p>Fix Resolution: better_errors - 2.8.0</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2022-30122</summary>
### Vulnerable Library - <b>rack-2.2.3.gem</b></p>
<p>Rack provides a minimal, modular and adaptable interface for developing
web applications in Ruby. By wrapping HTTP requests and responses in
the simplest way possible, it unifies and distills the API for web
servers, web frameworks, and software in between (the so-called
middleware) into a single method call.
</p>
<p>Library home page: <a href="https://rubygems.org/gems/rack-2.2.3.gem">https://rubygems.org/gems/rack-2.2.3.gem</a></p>
<p>
Dependency Hierarchy:
- better_errors-2.5.1.gem (Root Library)
- :x: **rack-2.2.3.gem** (Vulnerable Library)
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
A possible denial of service vulnerability exists in Rack <2.0.9.1, <2.1.4.1 and <2.2.3.1 in the multipart parsing component of Rack.
<p>Publish Date: 2022-12-05
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-30122>CVE-2022-30122</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>7.5</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/advisories/GHSA-hxqx-xwvh-44m2">https://github.com/advisories/GHSA-hxqx-xwvh-44m2</a></p>
<p>Release Date: 2022-12-05</p>
<p>Fix Resolution: rack - 2.0.9.1,2.1.4.1,2.2.3.1</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2022-44571</summary>
### Vulnerable Library - <b>rack-2.2.3.gem</b></p>
<p>Rack provides a minimal, modular and adaptable interface for developing
web applications in Ruby. By wrapping HTTP requests and responses in
the simplest way possible, it unifies and distills the API for web
servers, web frameworks, and software in between (the so-called
middleware) into a single method call.
</p>
<p>Library home page: <a href="https://rubygems.org/gems/rack-2.2.3.gem">https://rubygems.org/gems/rack-2.2.3.gem</a></p>
<p>
Dependency Hierarchy:
- better_errors-2.5.1.gem (Root Library)
- :x: **rack-2.2.3.gem** (Vulnerable Library)
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
There is a denial of service vulnerability in the Content-Disposition parsingcomponent of Rack fixed in 2.0.9.2, 2.1.4.2, 2.2.4.1, 3.0.0.1. This could allow an attacker to craft an input that can cause Content-Disposition header parsing in Rackto take an unexpected amount of time, possibly resulting in a denial ofservice attack vector. This header is used typically used in multipartparsing. Any applications that parse multipart posts using Rack (virtuallyall Rails applications) are impacted.
<p>Publish Date: 2023-02-09
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-44571>CVE-2022-44571</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>7.5</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/advisories/GHSA-93pm-5p5f-3ghx">https://github.com/advisories/GHSA-93pm-5p5f-3ghx</a></p>
<p>Release Date: 2023-02-09</p>
<p>Fix Resolution: rack - 2.0.9.2,2.1.4.2,2.2.6.2,3.0.4.1</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2022-44570</summary>
### Vulnerable Library - <b>rack-2.2.3.gem</b></p>
<p>Rack provides a minimal, modular and adaptable interface for developing
web applications in Ruby. By wrapping HTTP requests and responses in
the simplest way possible, it unifies and distills the API for web
servers, web frameworks, and software in between (the so-called
middleware) into a single method call.
</p>
<p>Library home page: <a href="https://rubygems.org/gems/rack-2.2.3.gem">https://rubygems.org/gems/rack-2.2.3.gem</a></p>
<p>
Dependency Hierarchy:
- better_errors-2.5.1.gem (Root Library)
- :x: **rack-2.2.3.gem** (Vulnerable Library)
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
A denial of service vulnerability in the Range header parsing component of Rack >= 1.5.0. A Carefully crafted input can cause the Range header parsing component in Rack to take an unexpected amount of time, possibly resulting in a denial of service attack vector. Any applications that deal with Range requests (such as streaming applications, or applications that serve files) may be impacted.
<p>Publish Date: 2023-02-09
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-44570>CVE-2022-44570</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>7.5</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/advisories/GHSA-65f5-mfpf-vfhj">https://github.com/advisories/GHSA-65f5-mfpf-vfhj</a></p>
<p>Release Date: 2023-02-09</p>
<p>Fix Resolution: rack - 2.0.9.2,2.1.4.2,2.2.6.2,3.0.4.1</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2022-44572</summary>
### Vulnerable Library - <b>rack-2.2.3.gem</b></p>
<p>Rack provides a minimal, modular and adaptable interface for developing
web applications in Ruby. By wrapping HTTP requests and responses in
the simplest way possible, it unifies and distills the API for web
servers, web frameworks, and software in between (the so-called
middleware) into a single method call.
</p>
<p>Library home page: <a href="https://rubygems.org/gems/rack-2.2.3.gem">https://rubygems.org/gems/rack-2.2.3.gem</a></p>
<p>
Dependency Hierarchy:
- better_errors-2.5.1.gem (Root Library)
- :x: **rack-2.2.3.gem** (Vulnerable Library)
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
A denial of service vulnerability in the multipart parsing component of Rack fixed in 2.0.9.2, 2.1.4.2, 2.2.4.1 and 3.0.0.1 could allow an attacker tocraft input that can cause RFC2183 multipart boundary parsing in Rack to take an unexpected amount of time, possibly resulting in a denial of service attack vector. Any applications that parse multipart posts using Rack (virtually all Rails applications) are impacted.
<p>Publish Date: 2023-02-09
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-44572>CVE-2022-44572</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>7.5</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/advisories/GHSA-rqv2-275x-2jq5">https://github.com/advisories/GHSA-rqv2-275x-2jq5</a></p>
<p>Release Date: 2023-02-09</p>
<p>Fix Resolution: rack - 2.0.9.2,2.1.4.2,2.2.6.2,3.0.4.1</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2023-27530</summary>
### Vulnerable Library - <b>rack-2.2.3.gem</b></p>
<p>Rack provides a minimal, modular and adaptable interface for developing
web applications in Ruby. By wrapping HTTP requests and responses in
the simplest way possible, it unifies and distills the API for web
servers, web frameworks, and software in between (the so-called
middleware) into a single method call.
</p>
<p>Library home page: <a href="https://rubygems.org/gems/rack-2.2.3.gem">https://rubygems.org/gems/rack-2.2.3.gem</a></p>
<p>
Dependency Hierarchy:
- better_errors-2.5.1.gem (Root Library)
- :x: **rack-2.2.3.gem** (Vulnerable Library)
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
A possible DoS vulnerability in the Multipart MIME parsing code in Rack. This vulnerability has been assigned the CVE identifier CVE-2023-27530.
Versions Affected: All. Not affected: None Fixed Versions: 3.0.4.2, 2.2.6.3, 2.1.4.3, 2.0.9.3 The Multipart MIME parsing code in Rack limits the number of file parts, but does not limit the total number of parts that can be uploaded. Carefully crafted requests can abuse this and cause multipart parsing to take longer than expected. All users running an affected release should either upgrade or use one of the workarounds immediately.
<p>Publish Date: 2023-03-03
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2023-27530>CVE-2023-27530</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>5.5</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Release Date: 2023-03-03</p>
<p>Fix Resolution: rack - 2.0.9.3,2.1.4.3,2.2.6.3,3.0.4.2</p>
</p>
<p></p>
</details> | True | better_errors-2.5.1.gem: 7 vulnerabilities (highest severity is: 10.0) - <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>better_errors-2.5.1.gem</b></p></summary>
<p>Provides a better error page for Rails and other Rack apps. Includes source code inspection, a live REPL and local/instance variable inspection for all stack frames.</p>
<p>Library home page: <a href="https://rubygems.org/gems/better_errors-2.5.1.gem">https://rubygems.org/gems/better_errors-2.5.1.gem</a></p>
<p>
</details>
## Vulnerabilities
| CVE | Severity | <img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS | Dependency | Type | Fixed in (better_errors version) | Remediation Available |
| ------------- | ------------- | ----- | ----- | ----- | ------------- | --- |
| [CVE-2022-30123](https://www.mend.io/vulnerability-database/CVE-2022-30123) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 10.0 | rack-2.2.3.gem | Transitive | N/A* | ❌ |
| [CVE-2021-39197](https://www.mend.io/vulnerability-database/CVE-2021-39197) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 8.8 | better_errors-2.5.1.gem | Direct | better_errors - 2.8.0 | ❌ |
| [CVE-2022-30122](https://www.mend.io/vulnerability-database/CVE-2022-30122) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | rack-2.2.3.gem | Transitive | N/A* | ❌ |
| [CVE-2022-44571](https://www.mend.io/vulnerability-database/CVE-2022-44571) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | rack-2.2.3.gem | Transitive | N/A* | ❌ |
| [CVE-2022-44570](https://www.mend.io/vulnerability-database/CVE-2022-44570) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | rack-2.2.3.gem | Transitive | N/A* | ❌ |
| [CVE-2022-44572](https://www.mend.io/vulnerability-database/CVE-2022-44572) | <img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> High | 7.5 | rack-2.2.3.gem | Transitive | N/A* | ❌ |
| [CVE-2023-27530](https://www.mend.io/vulnerability-database/CVE-2023-27530) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 5.5 | rack-2.2.3.gem | Transitive | N/A* | ❌ |
<p>*For some transitive vulnerabilities, there is no version of direct dependency with a fix. Check the section "Details" below to see if there is a version of transitive dependency where vulnerability is fixed.</p>
## Details
<details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2022-30123</summary>
### Vulnerable Library - <b>rack-2.2.3.gem</b></p>
<p>Rack provides a minimal, modular and adaptable interface for developing
web applications in Ruby. By wrapping HTTP requests and responses in
the simplest way possible, it unifies and distills the API for web
servers, web frameworks, and software in between (the so-called
middleware) into a single method call.
</p>
<p>Library home page: <a href="https://rubygems.org/gems/rack-2.2.3.gem">https://rubygems.org/gems/rack-2.2.3.gem</a></p>
<p>
Dependency Hierarchy:
- better_errors-2.5.1.gem (Root Library)
- :x: **rack-2.2.3.gem** (Vulnerable Library)
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
A sequence injection vulnerability exists in Rack <2.0.9.1, <2.1.4.1 and <2.2.3.1 which could allow is a possible shell escape in the Lint and CommonLogger components of Rack.
<p>Publish Date: 2022-12-05
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-30123>CVE-2022-30123</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>10.0</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Changed
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/advisories/GHSA-wq4h-7r42-5hrr">https://github.com/advisories/GHSA-wq4h-7r42-5hrr</a></p>
<p>Release Date: 2022-12-05</p>
<p>Fix Resolution: rack - 2.0.9.1,2.1.4.1,2.2.3.1</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2021-39197</summary>
### Vulnerable Library - <b>better_errors-2.5.1.gem</b></p>
<p>Provides a better error page for Rails and other Rack apps. Includes source code inspection, a live REPL and local/instance variable inspection for all stack frames.</p>
<p>Library home page: <a href="https://rubygems.org/gems/better_errors-2.5.1.gem">https://rubygems.org/gems/better_errors-2.5.1.gem</a></p>
<p>
Dependency Hierarchy:
- :x: **better_errors-2.5.1.gem** (Vulnerable Library)
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
better_errors is an open source replacement for the standard Rails error page with more information rich error pages. It is also usable outside of Rails in any Rack app as Rack middleware. better_errors prior to 2.8.0 did not implement CSRF protection for its internal requests. It also did not enforce the correct "Content-Type" header for these requests, which allowed a cross-origin "simple request" to be made without CORS protection. These together left an application with better_errors enabled open to cross-origin attacks. As a developer tool, better_errors documentation strongly recommends addition only to the `development` bundle group, so this vulnerability should only affect development environments. Please ensure that your project limits better_errors to the `development` group (or the non-Rails equivalent). Starting with release 2.8.x, CSRF protection is enforced. It is recommended that you upgrade to the latest release, or minimally to "~> 2.8.3". There are no known workarounds to mitigate the risk of using older releases of better_errors.
<p>Publish Date: 2021-09-07
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2021-39197>CVE-2021-39197</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: None
- User Interaction: Required
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/BetterErrors/better_errors/security/advisories/GHSA-w3j4-76qw-wwjm">https://github.com/BetterErrors/better_errors/security/advisories/GHSA-w3j4-76qw-wwjm</a></p>
<p>Release Date: 2021-09-07</p>
<p>Fix Resolution: better_errors - 2.8.0</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2022-30122</summary>
### Vulnerable Library - <b>rack-2.2.3.gem</b></p>
<p>Rack provides a minimal, modular and adaptable interface for developing
web applications in Ruby. By wrapping HTTP requests and responses in
the simplest way possible, it unifies and distills the API for web
servers, web frameworks, and software in between (the so-called
middleware) into a single method call.
</p>
<p>Library home page: <a href="https://rubygems.org/gems/rack-2.2.3.gem">https://rubygems.org/gems/rack-2.2.3.gem</a></p>
<p>
Dependency Hierarchy:
- better_errors-2.5.1.gem (Root Library)
- :x: **rack-2.2.3.gem** (Vulnerable Library)
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
A possible denial of service vulnerability exists in Rack <2.0.9.1, <2.1.4.1 and <2.2.3.1 in the multipart parsing component of Rack.
<p>Publish Date: 2022-12-05
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-30122>CVE-2022-30122</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>7.5</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/advisories/GHSA-hxqx-xwvh-44m2">https://github.com/advisories/GHSA-hxqx-xwvh-44m2</a></p>
<p>Release Date: 2022-12-05</p>
<p>Fix Resolution: rack - 2.0.9.1,2.1.4.1,2.2.3.1</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2022-44571</summary>
### Vulnerable Library - <b>rack-2.2.3.gem</b></p>
<p>Rack provides a minimal, modular and adaptable interface for developing
web applications in Ruby. By wrapping HTTP requests and responses in
the simplest way possible, it unifies and distills the API for web
servers, web frameworks, and software in between (the so-called
middleware) into a single method call.
</p>
<p>Library home page: <a href="https://rubygems.org/gems/rack-2.2.3.gem">https://rubygems.org/gems/rack-2.2.3.gem</a></p>
<p>
Dependency Hierarchy:
- better_errors-2.5.1.gem (Root Library)
- :x: **rack-2.2.3.gem** (Vulnerable Library)
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
There is a denial of service vulnerability in the Content-Disposition parsingcomponent of Rack fixed in 2.0.9.2, 2.1.4.2, 2.2.4.1, 3.0.0.1. This could allow an attacker to craft an input that can cause Content-Disposition header parsing in Rackto take an unexpected amount of time, possibly resulting in a denial ofservice attack vector. This header is used typically used in multipartparsing. Any applications that parse multipart posts using Rack (virtuallyall Rails applications) are impacted.
<p>Publish Date: 2023-02-09
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-44571>CVE-2022-44571</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>7.5</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/advisories/GHSA-93pm-5p5f-3ghx">https://github.com/advisories/GHSA-93pm-5p5f-3ghx</a></p>
<p>Release Date: 2023-02-09</p>
<p>Fix Resolution: rack - 2.0.9.2,2.1.4.2,2.2.6.2,3.0.4.1</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2022-44570</summary>
### Vulnerable Library - <b>rack-2.2.3.gem</b></p>
<p>Rack provides a minimal, modular and adaptable interface for developing
web applications in Ruby. By wrapping HTTP requests and responses in
the simplest way possible, it unifies and distills the API for web
servers, web frameworks, and software in between (the so-called
middleware) into a single method call.
</p>
<p>Library home page: <a href="https://rubygems.org/gems/rack-2.2.3.gem">https://rubygems.org/gems/rack-2.2.3.gem</a></p>
<p>
Dependency Hierarchy:
- better_errors-2.5.1.gem (Root Library)
- :x: **rack-2.2.3.gem** (Vulnerable Library)
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
A denial of service vulnerability in the Range header parsing component of Rack >= 1.5.0. A Carefully crafted input can cause the Range header parsing component in Rack to take an unexpected amount of time, possibly resulting in a denial of service attack vector. Any applications that deal with Range requests (such as streaming applications, or applications that serve files) may be impacted.
<p>Publish Date: 2023-02-09
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-44570>CVE-2022-44570</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>7.5</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/advisories/GHSA-65f5-mfpf-vfhj">https://github.com/advisories/GHSA-65f5-mfpf-vfhj</a></p>
<p>Release Date: 2023-02-09</p>
<p>Fix Resolution: rack - 2.0.9.2,2.1.4.2,2.2.6.2,3.0.4.1</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> CVE-2022-44572</summary>
### Vulnerable Library - <b>rack-2.2.3.gem</b></p>
<p>Rack provides a minimal, modular and adaptable interface for developing
web applications in Ruby. By wrapping HTTP requests and responses in
the simplest way possible, it unifies and distills the API for web
servers, web frameworks, and software in between (the so-called
middleware) into a single method call.
</p>
<p>Library home page: <a href="https://rubygems.org/gems/rack-2.2.3.gem">https://rubygems.org/gems/rack-2.2.3.gem</a></p>
<p>
Dependency Hierarchy:
- better_errors-2.5.1.gem (Root Library)
- :x: **rack-2.2.3.gem** (Vulnerable Library)
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
A denial of service vulnerability in the multipart parsing component of Rack fixed in 2.0.9.2, 2.1.4.2, 2.2.4.1 and 3.0.0.1 could allow an attacker tocraft input that can cause RFC2183 multipart boundary parsing in Rack to take an unexpected amount of time, possibly resulting in a denial of service attack vector. Any applications that parse multipart posts using Rack (virtually all Rails applications) are impacted.
<p>Publish Date: 2023-02-09
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-44572>CVE-2022-44572</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>7.5</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/advisories/GHSA-rqv2-275x-2jq5">https://github.com/advisories/GHSA-rqv2-275x-2jq5</a></p>
<p>Release Date: 2023-02-09</p>
<p>Fix Resolution: rack - 2.0.9.2,2.1.4.2,2.2.6.2,3.0.4.1</p>
</p>
<p></p>
</details><details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2023-27530</summary>
### Vulnerable Library - <b>rack-2.2.3.gem</b></p>
<p>Rack provides a minimal, modular and adaptable interface for developing
web applications in Ruby. By wrapping HTTP requests and responses in
the simplest way possible, it unifies and distills the API for web
servers, web frameworks, and software in between (the so-called
middleware) into a single method call.
</p>
<p>Library home page: <a href="https://rubygems.org/gems/rack-2.2.3.gem">https://rubygems.org/gems/rack-2.2.3.gem</a></p>
<p>
Dependency Hierarchy:
- better_errors-2.5.1.gem (Root Library)
- :x: **rack-2.2.3.gem** (Vulnerable Library)
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
A possible DoS vulnerability in the Multipart MIME parsing code in Rack. This vulnerability has been assigned the CVE identifier CVE-2023-27530.
Versions Affected: All. Not affected: None Fixed Versions: 3.0.4.2, 2.2.6.3, 2.1.4.3, 2.0.9.3 The Multipart MIME parsing code in Rack limits the number of file parts, but does not limit the total number of parts that can be uploaded. Carefully crafted requests can abuse this and cause multipart parsing to take longer than expected. All users running an affected release should either upgrade or use one of the workarounds immediately.
<p>Publish Date: 2023-03-03
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2023-27530>CVE-2023-27530</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>5.5</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Release Date: 2023-03-03</p>
<p>Fix Resolution: rack - 2.0.9.3,2.1.4.3,2.2.6.3,3.0.4.2</p>
</p>
<p></p>
</details> | non_priority | better errors gem vulnerabilities highest severity is vulnerable library better errors gem provides a better error page for rails and other rack apps includes source code inspection a live repl and local instance variable inspection for all stack frames library home page a href vulnerabilities cve severity cvss dependency type fixed in better errors version remediation available high rack gem transitive n a high better errors gem direct better errors high rack gem transitive n a high rack gem transitive n a high rack gem transitive n a high rack gem transitive n a medium rack gem transitive n a for some transitive vulnerabilities there is no version of direct dependency with a fix check the section details below to see if there is a version of transitive dependency where vulnerability is fixed details cve vulnerable library rack gem rack provides a minimal modular and adaptable interface for developing web applications in ruby by wrapping http requests and responses in the simplest way possible it unifies and distills the api for web servers web frameworks and software in between the so called middleware into a single method call library home page a href dependency hierarchy better errors gem root library x rack gem vulnerable library found in base branch master vulnerability details a sequence injection vulnerability exists in rack and which could allow is a possible shell escape in the lint and commonlogger components of rack publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction none scope changed impact metrics confidentiality impact high integrity impact high availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution rack cve vulnerable library better errors gem provides a better error page for rails and other rack apps includes source code inspection a live repl and local instance variable inspection for all stack frames library home page a href dependency hierarchy x better errors gem vulnerable library found in base branch master vulnerability details better errors is an open source replacement for the standard rails error page with more information rich error pages it is also usable outside of rails in any rack app as rack middleware better errors prior to did not implement csrf protection for its internal requests it also did not enforce the correct content type header for these requests which allowed a cross origin simple request to be made without cors protection these together left an application with better errors enabled open to cross origin attacks as a developer tool better errors documentation strongly recommends addition only to the development bundle group so this vulnerability should only affect development environments please ensure that your project limits better errors to the development group or the non rails equivalent starting with release x csrf protection is enforced it is recommended that you upgrade to the latest release or minimally to there are no known workarounds to mitigate the risk of using older releases of better errors publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity low privileges required none user interaction required scope unchanged impact metrics confidentiality impact high integrity impact high availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution better errors cve vulnerable library rack gem rack provides a minimal modular and adaptable interface for developing web applications in ruby by wrapping http requests and responses in the simplest way possible it unifies and distills the api for web servers web frameworks and software in between the so called middleware into a single method call library home page a href dependency hierarchy better errors gem root library x rack gem vulnerable library found in base branch master vulnerability details a possible denial of service vulnerability exists in rack and in the multipart parsing component of rack 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 rack cve vulnerable library rack gem rack provides a minimal modular and adaptable interface for developing web applications in ruby by wrapping http requests and responses in the simplest way possible it unifies and distills the api for web servers web frameworks and software in between the so called middleware into a single method call library home page a href dependency hierarchy better errors gem root library x rack gem vulnerable library found in base branch master vulnerability details there is a denial of service vulnerability in the content disposition parsingcomponent of rack fixed in this could allow an attacker to craft an input that can cause content disposition header parsing in rackto take an unexpected amount of time possibly resulting in a denial ofservice attack vector this header is used typically used in multipartparsing any applications that parse multipart posts using rack virtuallyall rails applications are impacted 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 rack cve vulnerable library rack gem rack provides a minimal modular and adaptable interface for developing web applications in ruby by wrapping http requests and responses in the simplest way possible it unifies and distills the api for web servers web frameworks and software in between the so called middleware into a single method call library home page a href dependency hierarchy better errors gem root library x rack gem vulnerable library found in base branch master vulnerability details a denial of service vulnerability in the range header parsing component of rack a carefully crafted input can cause the range header parsing component in rack to take an unexpected amount of time possibly resulting in a denial of service attack vector any applications that deal with range requests such as streaming applications or applications that serve files may be impacted 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 rack cve vulnerable library rack gem rack provides a minimal modular and adaptable interface for developing web applications in ruby by wrapping http requests and responses in the simplest way possible it unifies and distills the api for web servers web frameworks and software in between the so called middleware into a single method call library home page a href dependency hierarchy better errors gem root library x rack gem vulnerable library found in base branch master vulnerability details a denial of service vulnerability in the multipart parsing component of rack fixed in and could allow an attacker tocraft input that can cause multipart boundary parsing in rack to take an unexpected amount of time possibly resulting in a denial of service attack vector any applications that parse multipart posts using rack virtually all rails applications are impacted 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 rack cve vulnerable library rack gem rack provides a minimal modular and adaptable interface for developing web applications in ruby by wrapping http requests and responses in the simplest way possible it unifies and distills the api for web servers web frameworks and software in between the so called middleware into a single method call library home page a href dependency hierarchy better errors gem root library x rack gem vulnerable library found in base branch master vulnerability details a possible dos vulnerability in the multipart mime parsing code in rack this vulnerability has been assigned the cve identifier cve versions affected all not affected none fixed versions the multipart mime parsing code in rack limits the number of file parts but does not limit the total number of parts that can be uploaded carefully crafted requests can abuse this and cause multipart parsing to take longer than expected all users running an affected release should either upgrade or use one of the workarounds immediately publish date url a href cvss score details base score metrics exploitability metrics attack vector local attack complexity low privileges required none user interaction required scope unchanged impact metrics confidentiality impact none integrity impact none availability impact high for more information on scores click a href suggested fix type upgrade version release date fix resolution rack | 0 |
728,466 | 25,080,330,277 | IssuesEvent | 2022-11-07 18:43:46 | serokell/tezos-packaging | https://api.github.com/repos/serokell/tezos-packaging | closed | [BUG] services using non-default node data directory enter infinite crash/restart loop after upgrade | in progress high priority | # Description
<!--
A clear and concise description of what the bug is.
-->
# To Reproduce
Steps to reproduce the behavior:
- set up baking with tezos-setup-wizard on using octez 13 packages
- apt update, apt upgrade
- observe baker and node services now constantly restart with "Pack_error: "Migration_needed" error seen in the logs for the baker
```
ug 04 10:28:23 raspberrypi tezos-node-start[8215]: Aug 4 10:28:23.829 - validator.chain: Request pushed on 2022-08-04T14:28:23.654-00:00, treated in 299us, completed in 174ms
Aug 04 10:28:23 raspberrypi tezos-node-start[8215]: Aug 4 10:28:23.830 - validator.chain: Sync_status: sync
Aug 04 10:28:23 raspberrypi tezos-baker-013-ptjakart-start[8218]: Current head: BLZWVyZCPvp6 (timestamp: 2022-08-04T14:28:14.000-00:00, validation: 2022-08-04T14:28:23.830-00:00)
Aug 04 10:28:23 raspberrypi tezos-baker-012-psithaca-start[8216]: Current head: BLZWVyZCPvp6 (timestamp: 2022-08-04T14:28:14.000-00:00, validation: 2022-08-04T14:28:23.830-00:00)
Aug 04 10:28:23 raspberrypi tezos-node-start[8215]: Aug 4 10:28:23.943 - validator.chain: Chain is bootstrapped
Aug 04 10:28:23 raspberrypi tezos-baker-013-ptjakart-start[8218]: Node is bootstrapped.
Aug 04 10:28:23 raspberrypi tezos-baker-013-ptjakart-start[8218]: Waiting for protocol 013-PtJakart to start...
Aug 04 10:28:23 raspberrypi tezos-baker-013-ptjakart-start[8218]: Baker v14.0 (4ca33194) for PtJakart2xVj started.
Aug 04 10:28:24 raspberrypi tezos-baker-013-ptjakart-start[8218]: Error:
Aug 04 10:28:24 raspberrypi tezos-baker-013-ptjakart-start[8218]: Pack_error: "Migration_needed"
Aug 04 10:28:25 raspberrypi tezos-baker-012-psithaca-start[8216]: (/usr/bin/tezos-baker-012-Psithaca) TERM: triggering shutdown.
Aug 04 10:28:25 raspberrypi tezos-baker-012-psithaca-start[8216]: Fatal error:
Aug 04 10:28:25 raspberrypi tezos-baker-012-psithaca-start[8216]: Lwt.Resolution_loop.Canceled
Aug 04 10:28:25 raspberrypi tezos-node-start[8215]: (/usr/bin/tezos-node) TERM: triggering shutdown.
Aug 04 10:28:25 raspberrypi tezos-node-start[8215]: (/usr/bin/tezos-node) TERM: triggering shutdown.
Aug 04 10:28:25 raspberrypi tezos-node-start[8215]: Aug 4 10:28:25.126 - node.main: shutting down the Tezos node
Aug 04 10:28:25 raspberrypi tezos-node-start[8215]: Aug 4 10:28:25.133 - node.validator: shutting down the chain validator NetXdQprcVkpaWU
Aug 04 10:28:25 raspberrypi tezos-node-start[8215]: Aug 4 10:28:25.137 - node.distributed_db.requester: shutting down requester
Aug 04 10:28:25 raspberrypi tezos-node-start[8215]: Aug 4 10:28:25.137 - node.distributed_db.requester: shutting down requester
Aug 04 10:28:25 raspberrypi tezos-node-start[8215]: Aug 4 10:28:25.157 - node.validator: shutting down the block validator
Aug 04 10:28:25 raspberrypi tezos-node-start[8215]: Aug 4 10:28:25.157 - external_block_validator: shutting down
Aug 04 10:28:25 raspberrypi tezos-node-start[8215]: Aug 4 10:28:25.252 - external_block_validator: process terminated abnormally with exit code 127
Aug 04 10:28:25 raspberrypi tezos-node-start[8215]: Aug 4 10:28:25.255 - p2p: shutting down the p2p's welcome worker...
Aug 04 10:28:25 raspberrypi tezos-node-start[8215]: Aug 4 10:28:25.256 - p2p: shutting down the p2p's network maintenance worker...
Aug 04 10:28:25 raspberrypi tezos-node-start[8215]: Aug 4 10:28:25.287 - p2p: shutting down the p2p connection pool...
Aug 04 10:28:28 raspberrypi tezos-node-start[8215]: (/usr/bin/tezos-node) TERM: send signal again to force-quit.
Aug 04 10:28:28 raspberrypi tezos-node-start[8215]: Aug 4 10:28:28.169 - p2p: shutting down the p2p connection handler...
Aug 04 10:28:28 raspberrypi tezos-node-start[8215]: Aug 4 10:28:28.169 - p2p: shutting down the p2p scheduler...
Aug 04 10:28:28 raspberrypi tezos-node-start[8215]: Aug 4 10:28:28.170 - node.main: shutting down the RPC server
Aug 04 10:28:28 raspberrypi tezos-node-start[8215]: (/usr/bin/tezos-node) Exit: uncaught exception during clean-up (File "src/bin_node/node_run_command.ml", line 588, characters 11-18): in bind: Address already in use
Aug 04 10:28:28 raspberrypi tezos-node-start[8215]: (/usr/bin/tezos-node) Exit: uncaught exception during clean-up (File "src/bin_node/node_run_command.ml", line 579, characters 11-18): in bind: Address already in use
Aug 04 10:28:28 raspberrypi tezos-node-start[8215]: (/usr/bin/tezos-node) Exit: clean-up callback failed (File "src/bin_node/node_run_command.ml", line 579, characters 11-18): in bind: Address already in use
Aug 04 10:28:28 raspberrypi tezos-node-start[8215]: (/usr/bin/tezos-node) Exit: clean-up callback failed (File "src/bin_node/node_run_command.ml", line 588, characters 11-18): in bind: Address already in use
Aug 04 10:28:30 raspberrypi tezos-baking-prestart[9644]: Warning:
Aug 04 10:28:30 raspberrypi tezos-baking-prestart[9644]: Failed to acquire the protocol version from the node
Aug 04 10:28:30 raspberrypi tezos-baking-prestart[9644]: Rpc request failed:
Aug 04 10:28:30 raspberrypi tezos-baking-prestart[9644]: - meth: GET
Aug 04 10:28:30 raspberrypi tezos-baking-prestart[9644]: - uri: http://localhost:8732/chains/main/blocks/head/protocols
Aug 04 10:28:30 raspberrypi tezos-baking-prestart[9644]: - error: Unable to connect to the node: "Unix.Unix_error(Unix.ECONNREFUSED, "connect", "")"
Aug 04 10:28:31 raspberrypi tezos-baking-start[9656]: Warning:
Aug 04 10:28:31 raspberrypi tezos-baking-start[9656]: Failed to acquire the protocol version from the node
Aug 04 10:28:31 raspberrypi tezos-baking-start[9656]: Rpc request failed:
Aug 04 10:28:31 raspberrypi tezos-baking-start[9656]: - meth: GET
Aug 04 10:28:31 raspberrypi tezos-baking-start[9656]: - uri: http://localhost:8732/chains/main/blocks/head/protocols
Aug 04 10:28:31 raspberrypi tezos-baking-start[9656]: - error: Unable to connect to the node: "Unix.Unix_error(Unix.ECONNREFUSED, "connect", "")"
Aug 04 10:28:32 raspberrypi tezos-node-prestart[9874]: Aug 4 10:28:32.701 - node_data_version: node data dir is up-to-date
Aug 04 10:28:32 raspberrypi tezos-node-start[9879]: Updating the node configuration...
Aug 04 10:28:34 raspberrypi tezos-node-start[9879]: Aug 4 10:28:34.136 - node.main: FULL access to RPC enabled; this is very risky. (addresses = 0.0.0.0)
Aug 04 10:28:34 raspberrypi tezos-node-start[9879]: Aug 4 10:28:34.147 - node.config.validation: the node configuration has been successfully validated.
Aug 04 10:28:35 raspberrypi tezos-node-start[9879]: Aug 4 10:28:35.554 - node.config.validation: the node configuration has been successfully validated.
Aug 04 10:28:35 raspberrypi tezos-node-start[9879]: Aug 4 10:28:35.555 - node.main: read identity file (peer_id = idsbhivPq5xxtiom2Ny18XXRr9CFNi)
Aug 04 10:28:35 raspberrypi tezos-node-start[9879]: Aug 4 10:28:35.556 - node.main: starting the Tezos node v14.0 (4ca33194) (chain = TEZOS_MAINNET)
Aug 04 10:28:36 raspberrypi tezos-node-start[9879]: Aug 4 10:28:36.604 - node.main: disabled local peer discovery
Aug 04 10:28:36 raspberrypi tezos-node-start[9879]: Aug 4 10:28:36.614 - node: shell-node initialization: bootstrapping
Aug 04 10:28:38 raspberrypi tezos-node-start[9879]: Aug 4 10:28:38.284 - node: shell-node initialization: p2p_maintain_started
Aug 04 10:28:38 raspberrypi tezos-node-start[9879]: Aug 4 10:28:38.284 - external_block_validator: initialized
Aug 04 10:28:39 raspberrypi tezos-node-start[9879]: Aug 4 10:28:39.565 - external_block_validator: block validator process started with pid 9913
Aug 04 10:28:55 raspberrypi tezos-node-start[9879]: Aug 4 10:28:55.456 - node.validator: activate chain NetXdQprcVkpaWU
Aug 04 10:28:55 raspberrypi tezos-node-start[9879]: Aug 4 10:28:55.457 - p2p.maintenance: too few connections (0)
Aug 04 10:28:55 raspberrypi tezos-node-start[9879]: Aug 4 10:28:55.462 - validator.chain: Sync_status: unsync
Aug 04 10:28:55 raspberrypi tezos-node-start[9879]: Aug 4 10:28:55.469 - node.main: starting RPC server on ::ffff:127.0.0.1:8732 (acl = AllowAll) (tls = false)
Aug 04 10:28:55 raspberrypi tezos-node-start[9879]: Aug 4 10:28:55.470 - node.main: starting RPC server on ::ffff:0.0.0.0:8732 (acl = AllowAll) (tls = false)
Aug 04 10:28:55 raspberrypi tezos-node-start[9879]: Aug 4 10:28:55.471 - node.main: the Tezos node is now running
Aug 04 10:28:56 raspberrypi tezos-node-start[9879]: Aug 4 10:28:56.045 - node.validator.bootstrap_pipeline: fetching branch of about 2 blocks from peer idt9hT87Qnfu9QVPsWGigCAdPCar5k in
Aug 04 10:28:56 raspberrypi tezos-node-start[9879]: Aug 4 10:28:56.045 - node.validator.bootstrap_pipeline: 1 steps
Aug 04 10:28:56 raspberrypi tezos-node-start[9879]: Aug 4 10:28:56.056 - node.validator.bootstrap_pipeline: fetching branch of about 2 blocks from peer idtKX8X3RMGtubZyZZgg6NaS4H6Ay9 in
Aug 04 10:28:56 raspberrypi tezos-node-start[9879]: Aug 4 10:28:56.056 - node.validator.bootstrap_pipeline: 1 steps
Aug 04 10:28:59 raspberrypi tezos-baker-012-psithaca-start[9880]: Disclaimer:
Aug 04 10:28:59 raspberrypi tezos-baker-012-psithaca-start[9880]: The Tezos network is a new blockchain technology.
Aug 04 10:28:59 raspberrypi tezos-baker-012-psithaca-start[9880]: Users are solely responsible for any risks associated
Aug 04 10:28:59 raspberrypi tezos-baker-012-psithaca-start[9880]: with usage of the Tezos network. Users should do their
Aug 04 10:28:59 raspberrypi tezos-baker-012-psithaca-start[9880]: own research to determine if Tezos is the appropriate
Aug 04 10:28:59 raspberrypi tezos-baker-012-psithaca-start[9880]: platform for their needs and should apply judgement and
Aug 04 10:28:59 raspberrypi tezos-baker-012-psithaca-start[9880]: care in their network interactions.
Aug 04 10:29:00 raspberrypi tezos-baker-013-ptjakart-start[9882]: Disclaimer:
Aug 04 10:29:00 raspberrypi tezos-baker-013-ptjakart-start[9882]: The Tezos network is a new blockchain technology.
Aug 04 10:29:00 raspberrypi tezos-baker-013-ptjakart-start[9882]: Users are solely responsible for any risks associated
Aug 04 10:29:00 raspberrypi tezos-baker-013-ptjakart-start[9882]: with usage of the Tezos network. Users should do their
Aug 04 10:29:00 raspberrypi tezos-baker-013-ptjakart-start[9882]: own research to determine if Tezos is the appropriate
Aug 04 10:29:00 raspberrypi tezos-baker-013-ptjakart-start[9882]: platform for their needs and should apply judgement and
Aug 04 10:29:00 raspberrypi tezos-baker-013-ptjakart-start[9882]: care in their network interactions.
Aug 04 10:29:00 raspberrypi tezos-baker-012-psithaca-start[9880]: Waiting for the node to be bootstrapped...
Aug 04 10:29:02 raspberrypi tezos-baker-013-ptjakart-start[9882]: Aug 4 10:29:02.790 - 013-PtJakart.baker: reading per block vote file path: per_block_votes.json
Aug 04 10:29:03 raspberrypi tezos-baker-013-ptjakart-start[9882]: Waiting for the node to be bootstrapped...
Aug 04 10:29:07 raspberrypi tezos-node-start[9879]: Aug 4 10:29:07.162 - node.validator.bootstrap_pipeline: fetching branch of about 2 blocks from peer idt2DHVx3auSRS1Nv5AoKPm6bJw28Q in
Aug 04 10:29:07 raspberrypi tezos-node-start[9879]: Aug 4 10:29:07.162 - node.validator.bootstrap_pipeline: 1 steps
Aug 04 10:29:10 raspberrypi tezos-node-start[9879]: Aug 4 10:29:10.109 - validator.block: block BM5rZQrmnvj2mDYZG9x5ncedG2QMHqgXJypD73756d1KQpvKc5T successfully validated
Aug 04 10:29:10 raspberrypi tezos-node-start[9879]: Aug 4 10:29:10.109 - validator.block: Request pushed on 2022-08-04T14:28:56.274-00:00, treated in 4.159ms, completed in 13.830s
Aug 04 10:29:10 raspberrypi tezos-node-start[9879]: Aug 4 10:29:10.629 - validator.chain: Update current head to BM5rZQrmnvj2mDYZG9x5ncedG2QMHqgXJypD73756d1KQpvKc5T (level 2592876, timestamp 2022-08-04T14:28:44-00:00, fitness 02::0027906c::::ffffffff::00000000), same branch
Aug 04 10:29:10 raspberrypi tezos-node-start[9879]: Aug 4 10:29:10.629 - validator.chain: Request pushed on 2022-08-04T14:29:10.108-00:00, treated in 1.800ms, completed in 519ms
Aug 04 10:29:10 raspberrypi tezos-baker-013-ptjakart-start[9882]: Current head: BM5rZQrmnvj2 (timestamp: 2022-08-04T14:28:44.000-00:00, validation: 2022-08-04T14:29:10.629-00:00)
Aug 04 10:29:10 raspberrypi tezos-baker-012-psithaca-start[9880]: Current head: BM5rZQrmnvj2 (timestamp: 2022-08-04T14:28:44.000-00:00, validation: 2022-08-04T14:29:10.630-00:00)
Aug 04 10:29:19 raspberrypi tezos-node-start[9879]: Aug 4 10:29:19.211 - validator.block: block BMPYMQQY4HM3K3By8ECuqVUS2hF2QhiD531YY3rCdkMoFe1jquk successfully validated
Aug 04 10:29:19 raspberrypi tezos-node-start[9879]: Aug 4 10:29:19.211 - validator.block: Request pushed on 2022-08-04T14:29:16.276-00:00, treated in 4.29ms, completed in 2.930s
Aug 04 10:29:19 raspberrypi tezos-node-start[9879]: Aug 4 10:29:19.393 - validator.chain: Update current head to BMPYMQQY4HM3K3By8ECuqVUS2hF2QhiD531YY3rCdkMoFe1jquk (level 2592877, timestamp 2022-08-04T14:29:14-00:00, fitness 02::0027906d::::ffffffff::00000000), same branch
Aug 04 10:29:19 raspberrypi tezos-node-start[9879]: Aug 4 10:29:19.393 - validator.chain: Request pushed on 2022-08-04T14:29:19.210-00:00, treated in 287us, completed in 182ms
Aug 04 10:29:19 raspberrypi tezos-baker-013-ptjakart-start[9882]: Current head: BMPYMQQY4HM3 (timestamp: 2022-08-04T14:29:14.000-00:00, validation: 2022-08-04T14:29:19.394-00:00)
Aug 04 10:29:19 raspberrypi tezos-baker-012-psithaca-start[9880]: Current head: BMPYMQQY4HM3 (timestamp: 2022-08-04T14:29:14.000-00:00, validation: 2022-08-04T14:29:19.394-00:00)
Aug 04 10:29:28 raspberrypi tezos-node-start[9879]: Aug 4 10:29:28.046 - validator.chain: Sync_status: sync
Aug 04 10:29:28 raspberrypi tezos-node-start[9879]: Aug 4 10:29:28.224 - validator.chain: Chain is bootstrapped
Aug 04 10:29:28 raspberrypi tezos-baker-013-ptjakart-start[9882]: Node is bootstrapped.
Aug 04 10:29:28 raspberrypi tezos-baker-013-ptjakart-start[9882]: Waiting for protocol 013-PtJakart to start...
Aug 04 10:29:28 raspberrypi tezos-baker-013-ptjakart-start[9882]: Baker v14.0 (4ca33194) for PtJakart2xVj started.
Aug 04 10:29:29 raspberrypi tezos-baker-013-ptjakart-start[9882]: Error:
Aug 04 10:29:29 raspberrypi tezos-baker-013-ptjakart-start[9882]: Pack_error: "Migration_needed"
Aug 04 10:29:29 raspberrypi tezos-baker-012-psithaca-start[9880]: (/usr/bin/tezos-baker-012-Psithaca) TERM: triggering shutdown.
Aug 04 10:29:29 raspberrypi tezos-baker-012-psithaca-start[9880]: Fatal error:
Aug 04 10:29:29 raspberrypi tezos-baker-012-psithaca-start[9880]: Lwt.Resolution_loop.Canceled
Aug 04 10:29:29 raspberrypi tezos-node-start[9879]: (/usr/bin/tezos-node) TERM: triggering shutdown.
Aug 04 10:29:29 raspberrypi tezos-node-start[9879]: (/usr/bin/tezos-node) TERM: triggering shutdown.
Aug 04 10:29:29 raspberrypi tezos-node-start[9879]: Aug 4 10:29:29.390 - node.main: shutting down the Tezos node
Aug 04 10:29:29 raspberrypi tezos-node-start[9879]: Aug 4 10:29:29.395 - node.validator: shutting down the chain validator NetXdQprcVkpaWU
Aug 04 10:29:29 raspberrypi tezos-node-start[9879]: Aug 4 10:29:29.395 - node.distributed_db.requester: shutting down requester
Aug 04 10:29:29 raspberrypi tezos-node-start[9879]: Aug 4 10:29:29.396 - node.distributed_db.requester: shutting down requester
Aug 04 10:29:29 raspberrypi tezos-node-start[9879]: Aug 4 10:29:29.402 - node.validator: shutting down the block validator
Aug 04 10:29:29 raspberrypi tezos-node-start[9879]: Aug 4 10:29:29.403 - external_block_validator: shutting down
Aug 04 10:29:29 raspberrypi tezos-node-start[9879]: Aug 4 10:29:29.492 - external_block_validator: process terminated abnormally with exit code 127
Aug 04 10:29:29 raspberrypi tezos-node-start[9879]: Aug 4 10:29:29.504 - p2p: shutting down the p2p's welcome worker...
Aug 04 10:29:29 raspberrypi tezos-node-start[9879]: Aug 4 10:29:29.505 - p2p: shutting down the p2p's network maintenance worker...
Aug 04 10:29:29 raspberrypi tezos-node-start[9879]: Aug 4 10:29:29.515 - p2p: shutting down the p2p connection pool...
Aug 04 10:29:32 raspberrypi tezos-node-start[9879]: (/usr/bin/tezos-node) TERM: send signal again to force-quit.
Aug 04 10:29:32 raspberrypi tezos-node-start[9879]: Aug 4 10:29:32.546 - p2p: shutting down the p2p connection handler...
Aug 04 10:29:32 raspberrypi tezos-node-start[9879]: Aug 4 10:29:32.546 - p2p: shutting down the p2p scheduler...
Aug 04 10:29:32 raspberrypi tezos-node-start[9879]: Aug 4 10:29:32.546 - node.main: shutting down the RPC server
Aug 04 10:29:32 raspberrypi tezos-node-start[9879]: (/usr/bin/tezos-node) Exit: uncaught exception during clean-up (File "src/bin_node/node_run_command.ml", line 588, characters 11-18): in bind: Address already in use
Aug 04 10:29:32 raspberrypi tezos-node-start[9879]: (/usr/bin/tezos-node) Exit: uncaught exception during clean-up (File "src/bin_node/node_run_command.ml", line 579, characters 11-18): in bind: Address already in use
Aug 04 10:29:32 raspberrypi tezos-node-start[9879]: (/usr/bin/tezos-node) Exit: clean-up callback failed (File "src/bin_node/node_run_command.ml", line 579, characters 11-18): in bind: Address already in use
Aug 04 10:29:32 raspberrypi tezos-node-start[9879]: (/usr/bin/tezos-node) Exit: clean-up callback failed (File "src/bin_node/node_run_command.ml", line 588, characters 11-18): in bind: Address already in use
Aug 04 10:29:34 raspberrypi tezos-baking-prestart[11529]: Warning:
Aug 04 10:29:34 raspberrypi tezos-baking-prestart[11529]: Failed to acquire the protocol version from the node
Aug 04 10:29:34 raspberrypi tezos-baking-prestart[11529]: Rpc request failed:
Aug 04 10:29:34 raspberrypi tezos-baking-prestart[11529]: - meth: GET
Aug 04 10:29:34 raspberrypi tezos-baking-prestart[11529]: - uri: http://localhost:8732/chains/main/blocks/head/protocols
Aug 04 10:29:34 raspberrypi tezos-baking-prestart[11529]: - error: Unable to connect to the node: "Unix.Unix_error(Unix.ECONNREFUSED, "connect", "")"
Aug 04 10:29:35 raspberrypi tezos-baking-start[11535]: Warning:
Aug 04 10:29:35 raspberrypi tezos-baking-start[11535]: Failed to acquire the protocol version from the node
Aug 04 10:29:35 raspberrypi tezos-baking-start[11535]: Rpc request failed:
Aug 04 10:29:35 raspberrypi tezos-baking-start[11535]: - meth: GET
Aug 04 10:29:35 raspberrypi tezos-baking-start[11535]: - uri: http://localhost:8732/chains/main/blocks/head/protocols
Aug 04 10:29:35 raspberrypi tezos-baking-start[11535]: - error: Unable to connect to the node: "Unix.Unix_error(Unix.ECONNREFUSED, "connect", "")"
Aug 04 10:29:36 raspberrypi tezos-node-prestart[11544]: Aug 4 10:29:36.929 - node_data_version: node data dir is up-to-date
Aug 04 10:29:36 raspberrypi tezos-node-start[11549]: Updating the node configuration...
Aug 04 10:29:38 raspberrypi tezos-node-start[11549]: Aug 4 10:29:38.429 - node.main: FULL access to RPC enabled; this is very risky. (addresses = 0.0.0.0)
Aug 04 10:29:38 raspberrypi tezos-node-start[11549]: Aug 4 10:29:38.479 - node.config.validation: the node configuration has been successfully validated.
Aug 04 10:29:39 raspberrypi tezos-node-start[11549]: Aug 4 10:29:39.993 - node.config.validation: the node configuration has been successfully validated.
Aug 04 10:29:39 raspberrypi tezos-node-start[11549]: Aug 4 10:29:39.997 - node.main: read identity file (peer_id = idsbhivPq5xxtiom2Ny18XXRr9CFNi)
Aug 04 10:29:39 raspberrypi tezos-node-start[11549]: Aug 4 10:29:39.997 - node.main: starting the Tezos node v14.0 (4ca33194) (chain = TEZOS_MAINNET)
Aug 04 10:29:41 raspberrypi tezos-node-start[11549]: Aug 4 10:29:41.055 - node.main: disabled local peer discovery
Aug 04 10:29:41 raspberrypi tezos-node-start[11549]: Aug 4 10:29:41.067 - node: shell-node initialization: bootstrapping
Aug 04 10:29:42 raspberrypi tezos-node-start[11549]: Aug 4 10:29:42.704 - node: shell-node initialization: p2p_maintain_started
Aug 04 10:29:42 raspberrypi tezos-node-start[11549]: Aug 4 10:29:42.704 - external_block_validator: initialized
Aug 04 10:29:44 raspberrypi tezos-node-start[11549]: Aug 4 10:29:44.031 - external_block_validator: block validator process started with pid 11805
Aug 04 10:29:59 raspberrypi tezos-node-start[11549]: Aug 4 10:29:59.820 - node.validator: activate chain NetXdQprcVkpaWU
Aug 04 10:29:59 raspberrypi tezos-node-start[11549]: Aug 4 10:29:59.822 - p2p.maintenance: too few connections (0)
Aug 04 10:29:59 raspberrypi tezos-node-start[11549]: Aug 4 10:29:59.825 - validator.chain: Sync_status: unsync
Aug 04 10:29:59 raspberrypi tezos-node-start[11549]: Aug 4 10:29:59.826 - node.main: starting RPC server on ::ffff:127.0.0.1:8732 (acl = AllowAll) (tls = false)
Aug 04 10:29:59 raspberrypi tezos-node-start[11549]: Aug 4 10:29:59.827 - node.main: starting RPC server on ::ffff:0.0.0.0:8732 (acl = AllowAll) (tls = false)
Aug 04 10:29:59 raspberrypi tezos-node-start[11549]: Aug 4 10:29:59.828 - node.main: the Tezos node is now running
Aug 04 10:30:01 raspberrypi tezos-node-start[11549]: Aug 4 10:30:01.003 - node.validator.bootstrap_pipeline: fetching branch of about 2 blocks from peer idt1y2MVaWNkzgX5jitBoChS1M9vzF in
Aug 04 10:30:01 raspberrypi tezos-node-start[11549]: Aug 4 10:30:01.003 - node.validator.bootstrap_pipeline: 1 steps
Aug 04 10:30:01 raspberrypi tezos-node-start[11549]: Aug 4 10:30:01.340 - node.validator.bootstrap_pipeline: fetching branch of about 2 blocks from peer idrJMsqX35ziYZWTzwgMMmWtz7UQWG in
Aug 04 10:30:01 raspberrypi tezos-node-start[11549]: Aug 4 10:30:01.340 - node.validator.bootstrap_pipeline: 1 steps
Aug 04 10:30:02 raspberrypi tezos-node-start[11549]: Aug 4 10:30:02.040 - node.validator.bootstrap_pipeline: fetching branch of about 2 blocks from peer idsBHgHBHjJ4iskr6sXhkhBKX1b3T2 in
Aug 04 10:30:02 raspberrypi tezos-node-start[11549]: Aug 4 10:30:02.041 - node.validator.bootstrap_pipeline: 1 steps
Aug 04 10:30:03 raspberrypi tezos-node-start[11549]: Aug 4 10:30:03.995 - node.validator.bootstrap_pipeline: fetching branch of about 2 blocks from peer idtdudfwXzH46QVhxmvxaJLxAu3UvK in
Aug 04 10:30:03 raspberrypi tezos-node-start[11549]: Aug 4 10:30:03.996 - node.validator.bootstrap_pipeline: 1 steps
Aug 04 10:30:04 raspberrypi tezos-baker-012-psithaca-start[11550]: Disclaimer:
Aug 04 10:30:04 raspberrypi tezos-baker-012-psithaca-start[11550]: The Tezos network is a new blockchain technology.
Aug 04 10:30:04 raspberrypi tezos-baker-012-psithaca-start[11550]: Users are solely responsible for any risks associated
Aug 04 10:30:04 raspberrypi tezos-baker-012-psithaca-start[11550]: with usage of the Tezos network. Users should do their
Aug 04 10:30:04 raspberrypi tezos-baker-012-psithaca-start[11550]: own research to determine if Tezos is the appropriate
Aug 04 10:30:04 raspberrypi tezos-baker-012-psithaca-start[11550]: platform for their needs and should apply judgement and
Aug 04 10:30:04 raspberrypi tezos-baker-012-psithaca-start[11550]: care in their network interactions.
Aug 04 10:30:04 raspberrypi tezos-node-start[11549]: Aug 4 10:30:04.394 - node.validator.bootstrap_pipeline: fetching branch of about 2 blocks from peer idsrQBDC7v8DQqmnLdHVWbrTEU93Zq in
Aug 04 10:30:04 raspberrypi tezos-node-start[11549]: Aug 4 10:30:04.394 - node.validator.bootstrap_pipeline: 1 steps
Aug 04 10:30:05 raspberrypi tezos-baker-013-ptjakart-start[11552]: Disclaimer:
Aug 04 10:30:05 raspberrypi tezos-baker-013-ptjakart-start[11552]: The Tezos network is a new blockchain technology.
Aug 04 10:30:05 raspberrypi tezos-baker-013-ptjakart-start[11552]: Users are solely responsible for any risks associated
Aug 04 10:30:05 raspberrypi tezos-baker-013-ptjakart-start[11552]: with usage of the Tezos network. Users should do their
Aug 04 10:30:05 raspberrypi tezos-baker-013-ptjakart-start[11552]: own research to determine if Tezos is the appropriate
Aug 04 10:30:05 raspberrypi tezos-baker-013-ptjakart-start[11552]: platform for their needs and should apply judgement and
Aug 04 10:30:05 raspberrypi tezos-baker-013-ptjakart-start[11552]: care in their network interactions.
Aug 04 10:30:05 raspberrypi tezos-baker-012-psithaca-start[11550]: Waiting for the node to be bootstrapped...
Aug 04 10:30:07 raspberrypi tezos-baker-013-ptjakart-start[11552]: Aug 4 10:30:07.256 - 013-PtJakart.baker: reading per block vote file path: per_block_votes.json
Aug 04 10:30:07 raspberrypi tezos-baker-013-ptjakart-start[11552]: Waiting for the node to be bootstrapped...
Aug 04 10:30:14 raspberrypi tezos-node-start[11549]: Aug 4 10:30:14.710 - validator.block: block BM1MZE5zaDUmQ8id9ZifXt2PXv3imUocADyWNuj1JugE85RYNpH successfully validated
Aug 04 10:30:14 raspberrypi tezos-node-start[11549]: Aug 4 10:30:14.710 - validator.block: Request pushed on 2022-08-04T14:30:01.269-00:00, treated in 40.129us, completed in 13.440s
Aug 04 10:30:15 raspberrypi tezos-node-start[11549]: Aug 4 10:30:15.210 - validator.chain: Update current head to BM1MZE5zaDUmQ8id9ZifXt2PXv3imUocADyWNuj1JugE85RYNpH (level 2592878, timestamp 2022-08-04T14:29:44-00:00, fitness 02::0027906e::::ffffffff::00000000), same branch
Aug 04 10:30:15 raspberrypi tezos-node-start[11549]: Aug 4 10:30:15.210 - validator.chain: Request pushed on 2022-08-04T14:30:14.710-00:00, treated in 427us, completed in 499ms
Aug 04 10:30:15 raspberrypi tezos-baker-013-ptjakart-start[11552]: Current head: BM1MZE5zaDUm (timestamp: 2022-08-04T14:29:44.000-00:00, validation: 2022-08-04T14:30:15.212-00:00)
Aug 04 10:30:15 raspberrypi tezos-baker-012-psithaca-start[11550]: Current head: BM1MZE5zaDUm (timestamp: 2022-08-04T14:29:44.000-00:00, validation: 2022-08-04T14:30:15.212-00:00)
Aug 04 10:30:15 raspberrypi tezos-node-start[11549]: Aug 4 10:30:15.215 - validator.chain: Sync_status: sync
Aug 04 10:30:15 raspberrypi tezos-node-start[11549]: Aug 4 10:30:15.335 - validator.chain: Chain is bootstrapped
Aug 04 10:30:15 raspberrypi tezos-baker-013-ptjakart-start[11552]: Node is bootstrapped.
Aug 04 10:30:15 raspberrypi tezos-baker-013-ptjakart-start[11552]: Waiting for protocol 013-PtJakart to start...
Aug 04 10:30:15 raspberrypi tezos-baker-013-ptjakart-start[11552]: Baker v14.0 (4ca33194) for PtJakart2xVj started.
Aug 04 10:30:16 raspberrypi tezos-baker-013-ptjakart-start[11552]: Error:
Aug 04 10:30:16 raspberrypi tezos-baker-013-ptjakart-start[11552]: Pack_error: "Migration_needed"
Aug 04 10:30:16 raspberrypi tezos-baker-012-psithaca-start[11550]: (/usr/bin/tezos-baker-012-Psithaca) TERM: triggering shutdown.
Aug 04 10:30:16 raspberrypi tezos-baker-012-psithaca-start[11550]: Fatal error:
Aug 04 10:30:16 raspberrypi tezos-baker-012-psithaca-start[11550]: Lwt.Resolution_loop.Canceled
Aug 04 10:30:16 raspberrypi tezos-node-start[11549]: (/usr/bin/tezos-node) TERM: triggering shutdown.
Aug 04 10:30:16 raspberrypi tezos-node-start[11549]: (/usr/bin/tezos-node) TERM: triggering shutdown.
Aug 04 10:30:16 raspberrypi tezos-node-start[11549]: Aug 4 10:30:16.878 - node.main: shutting down the Tezos node
Aug 04 10:30:16 raspberrypi tezos-node-start[11549]: Aug 4 10:30:16.881 - node.validator: shutting down the chain validator NetXdQprcVkpaWU
Aug 04 10:30:16 raspberrypi tezos-node-start[11549]: Aug 4 10:30:16.882 - node.distributed_db.requester: shutting down requester
Aug 04 10:30:16 raspberrypi tezos-node-start[11549]: Aug 4 10:30:16.885 - node.distributed_db.requester: shutting down requester
Aug 04 10:30:16 raspberrypi tezos-node-start[11549]: Aug 4 10:30:16.893 - node.validator: shutting down the block validator
Aug 04 10:30:16 raspberrypi tezos-node-start[11549]: Aug 4 10:30:16.894 - external_block_validator: shutting down
Aug 04 10:30:16 raspberrypi tezos-node-start[11549]: Aug 4 10:30:16.992 - external_block_validator: process terminated abnormally with exit code 127
Aug 04 10:30:16 raspberrypi tezos-node-start[11549]: Aug 4 10:30:16.994 - p2p: shutting down the p2p's welcome worker...
Aug 04 10:30:16 raspberrypi tezos-node-start[11549]: Aug 4 10:30:16.994 - p2p: shutting down the p2p's network maintenance worker...
Aug 04 10:30:17 raspberrypi tezos-node-start[11549]: Aug 4 10:30:17.014 - p2p: shutting down the p2p connection pool...
Aug 04 10:30:19 raspberrypi tezos-node-start[11549]: (/usr/bin/tezos-node) TERM: send signal again to force-quit.
Aug 04 10:30:19 raspberrypi tezos-node-start[11549]: Aug 4 10:30:19.720 - p2p: shutting down the p2p connection handler...
Aug 04 10:30:19 raspberrypi tezos-node-start[11549]: Aug 4 10:30:19.720 - p2p: shutting down the p2p scheduler...
Aug 04 10:30:19 raspberrypi tezos-node-start[11549]: Aug 4 10:30:19.720 - node.main: shutting down the RPC server
Aug 04 10:30:19 raspberrypi tezos-node-start[11549]: (/usr/bin/tezos-node) Exit: uncaught exception during clean-up (File "src/bin_node/node_run_command.ml", line 588, characters 11-18): in bind: Address already in use
Aug 04 10:30:19 raspberrypi tezos-node-start[11549]: (/usr/bin/tezos-node) Exit: uncaught exception during clean-up (File "src/bin_node/node_run_command.ml", line 579, characters 11-18): in bind: Address already in use
Aug 04 10:30:19 raspberrypi tezos-node-start[11549]: (/usr/bin/tezos-node) Exit: clean-up callback failed (File "src/bin_node/node_run_command.ml", line 579, characters 11-18): in bind: Address already in use
Aug 04 10:30:19 raspberrypi tezos-node-start[11549]: (/usr/bin/tezos-node) Exit: clean-up callback failed (File "src/bin_node/node_run_command.ml", line 588, characters 11-18): in bind: Address already in use
Aug 04 10:30:21 raspberrypi tezos-baking-prestart[12830]: Warning:
Aug 04 10:30:21 raspberrypi tezos-baking-prestart[12830]: Failed to acquire the protocol version from the node
Aug 04 10:30:21 raspberrypi tezos-baking-prestart[12830]: Rpc request failed:
Aug 04 10:30:21 raspberrypi tezos-baking-prestart[12830]: - meth: GET
Aug 04 10:30:21 raspberrypi tezos-baking-prestart[12830]: - uri: http://localhost:8732/chains/main/blocks/head/protocols
Aug 04 10:30:21 raspberrypi tezos-baking-prestart[12830]: - error: Unable to connect to the node: "Unix.Unix_error(Unix.ECONNREFUSED, "connect", "")"
Aug 04 10:30:23 raspberrypi tezos-baking-start[12990]: Warning:
Aug 04 10:30:23 raspberrypi tezos-baking-start[12990]: Failed to acquire the protocol version from the node
Aug 04 10:30:23 raspberrypi tezos-baking-start[12990]: Rpc request failed:
Aug 04 10:30:23 raspberrypi tezos-baking-start[12990]: - meth: GET
Aug 04 10:30:23 raspberrypi tezos-baking-start[12990]: - uri: http://localhost:8732/chains/main/blocks/head/protocols
Aug 04 10:30:23 raspberrypi tezos-baking-start[12990]: - error: Unable to connect to the node: "Unix.Unix_error(Unix.ECONNREFUSED, "connect", "")"
Aug 04 10:30:24 raspberrypi tezos-node-prestart[12999]: Aug 4 10:30:24.383 - node_data_version: node data dir is up-to-date
Aug 04 10:30:24 raspberrypi tezos-node-start[13004]: Updating the node configuration...
Aug 04 10:30:25 raspberrypi tezos-node-start[13004]: Aug 4 10:30:25.814 - node.main: FULL access to RPC enabled; this is very risky. (addresses = 0.0.0.0)
Aug 04 10:30:25 raspberrypi tezos-node-start[13004]: Aug 4 10:30:25.825 - node.config.validation: the node configuration has been successfully validated.
Aug 04 10:30:27 raspberrypi tezos-node-start[13004]: Aug 4 10:30:27.303 - node.config.validation: the node configuration has been successfully validated.
```
# Expected behavior
Services restart after upgrade without errors, stay up
# Environment
- OS: RaspberryPi OS 64-bit
- branch/revision: upgrade octez 13 -> 14
# Additional context
<!--
Add any other context about the problem here.
-->
| 1.0 | [BUG] services using non-default node data directory enter infinite crash/restart loop after upgrade - # Description
<!--
A clear and concise description of what the bug is.
-->
# To Reproduce
Steps to reproduce the behavior:
- set up baking with tezos-setup-wizard on using octez 13 packages
- apt update, apt upgrade
- observe baker and node services now constantly restart with "Pack_error: "Migration_needed" error seen in the logs for the baker
```
ug 04 10:28:23 raspberrypi tezos-node-start[8215]: Aug 4 10:28:23.829 - validator.chain: Request pushed on 2022-08-04T14:28:23.654-00:00, treated in 299us, completed in 174ms
Aug 04 10:28:23 raspberrypi tezos-node-start[8215]: Aug 4 10:28:23.830 - validator.chain: Sync_status: sync
Aug 04 10:28:23 raspberrypi tezos-baker-013-ptjakart-start[8218]: Current head: BLZWVyZCPvp6 (timestamp: 2022-08-04T14:28:14.000-00:00, validation: 2022-08-04T14:28:23.830-00:00)
Aug 04 10:28:23 raspberrypi tezos-baker-012-psithaca-start[8216]: Current head: BLZWVyZCPvp6 (timestamp: 2022-08-04T14:28:14.000-00:00, validation: 2022-08-04T14:28:23.830-00:00)
Aug 04 10:28:23 raspberrypi tezos-node-start[8215]: Aug 4 10:28:23.943 - validator.chain: Chain is bootstrapped
Aug 04 10:28:23 raspberrypi tezos-baker-013-ptjakart-start[8218]: Node is bootstrapped.
Aug 04 10:28:23 raspberrypi tezos-baker-013-ptjakart-start[8218]: Waiting for protocol 013-PtJakart to start...
Aug 04 10:28:23 raspberrypi tezos-baker-013-ptjakart-start[8218]: Baker v14.0 (4ca33194) for PtJakart2xVj started.
Aug 04 10:28:24 raspberrypi tezos-baker-013-ptjakart-start[8218]: Error:
Aug 04 10:28:24 raspberrypi tezos-baker-013-ptjakart-start[8218]: Pack_error: "Migration_needed"
Aug 04 10:28:25 raspberrypi tezos-baker-012-psithaca-start[8216]: (/usr/bin/tezos-baker-012-Psithaca) TERM: triggering shutdown.
Aug 04 10:28:25 raspberrypi tezos-baker-012-psithaca-start[8216]: Fatal error:
Aug 04 10:28:25 raspberrypi tezos-baker-012-psithaca-start[8216]: Lwt.Resolution_loop.Canceled
Aug 04 10:28:25 raspberrypi tezos-node-start[8215]: (/usr/bin/tezos-node) TERM: triggering shutdown.
Aug 04 10:28:25 raspberrypi tezos-node-start[8215]: (/usr/bin/tezos-node) TERM: triggering shutdown.
Aug 04 10:28:25 raspberrypi tezos-node-start[8215]: Aug 4 10:28:25.126 - node.main: shutting down the Tezos node
Aug 04 10:28:25 raspberrypi tezos-node-start[8215]: Aug 4 10:28:25.133 - node.validator: shutting down the chain validator NetXdQprcVkpaWU
Aug 04 10:28:25 raspberrypi tezos-node-start[8215]: Aug 4 10:28:25.137 - node.distributed_db.requester: shutting down requester
Aug 04 10:28:25 raspberrypi tezos-node-start[8215]: Aug 4 10:28:25.137 - node.distributed_db.requester: shutting down requester
Aug 04 10:28:25 raspberrypi tezos-node-start[8215]: Aug 4 10:28:25.157 - node.validator: shutting down the block validator
Aug 04 10:28:25 raspberrypi tezos-node-start[8215]: Aug 4 10:28:25.157 - external_block_validator: shutting down
Aug 04 10:28:25 raspberrypi tezos-node-start[8215]: Aug 4 10:28:25.252 - external_block_validator: process terminated abnormally with exit code 127
Aug 04 10:28:25 raspberrypi tezos-node-start[8215]: Aug 4 10:28:25.255 - p2p: shutting down the p2p's welcome worker...
Aug 04 10:28:25 raspberrypi tezos-node-start[8215]: Aug 4 10:28:25.256 - p2p: shutting down the p2p's network maintenance worker...
Aug 04 10:28:25 raspberrypi tezos-node-start[8215]: Aug 4 10:28:25.287 - p2p: shutting down the p2p connection pool...
Aug 04 10:28:28 raspberrypi tezos-node-start[8215]: (/usr/bin/tezos-node) TERM: send signal again to force-quit.
Aug 04 10:28:28 raspberrypi tezos-node-start[8215]: Aug 4 10:28:28.169 - p2p: shutting down the p2p connection handler...
Aug 04 10:28:28 raspberrypi tezos-node-start[8215]: Aug 4 10:28:28.169 - p2p: shutting down the p2p scheduler...
Aug 04 10:28:28 raspberrypi tezos-node-start[8215]: Aug 4 10:28:28.170 - node.main: shutting down the RPC server
Aug 04 10:28:28 raspberrypi tezos-node-start[8215]: (/usr/bin/tezos-node) Exit: uncaught exception during clean-up (File "src/bin_node/node_run_command.ml", line 588, characters 11-18): in bind: Address already in use
Aug 04 10:28:28 raspberrypi tezos-node-start[8215]: (/usr/bin/tezos-node) Exit: uncaught exception during clean-up (File "src/bin_node/node_run_command.ml", line 579, characters 11-18): in bind: Address already in use
Aug 04 10:28:28 raspberrypi tezos-node-start[8215]: (/usr/bin/tezos-node) Exit: clean-up callback failed (File "src/bin_node/node_run_command.ml", line 579, characters 11-18): in bind: Address already in use
Aug 04 10:28:28 raspberrypi tezos-node-start[8215]: (/usr/bin/tezos-node) Exit: clean-up callback failed (File "src/bin_node/node_run_command.ml", line 588, characters 11-18): in bind: Address already in use
Aug 04 10:28:30 raspberrypi tezos-baking-prestart[9644]: Warning:
Aug 04 10:28:30 raspberrypi tezos-baking-prestart[9644]: Failed to acquire the protocol version from the node
Aug 04 10:28:30 raspberrypi tezos-baking-prestart[9644]: Rpc request failed:
Aug 04 10:28:30 raspberrypi tezos-baking-prestart[9644]: - meth: GET
Aug 04 10:28:30 raspberrypi tezos-baking-prestart[9644]: - uri: http://localhost:8732/chains/main/blocks/head/protocols
Aug 04 10:28:30 raspberrypi tezos-baking-prestart[9644]: - error: Unable to connect to the node: "Unix.Unix_error(Unix.ECONNREFUSED, "connect", "")"
Aug 04 10:28:31 raspberrypi tezos-baking-start[9656]: Warning:
Aug 04 10:28:31 raspberrypi tezos-baking-start[9656]: Failed to acquire the protocol version from the node
Aug 04 10:28:31 raspberrypi tezos-baking-start[9656]: Rpc request failed:
Aug 04 10:28:31 raspberrypi tezos-baking-start[9656]: - meth: GET
Aug 04 10:28:31 raspberrypi tezos-baking-start[9656]: - uri: http://localhost:8732/chains/main/blocks/head/protocols
Aug 04 10:28:31 raspberrypi tezos-baking-start[9656]: - error: Unable to connect to the node: "Unix.Unix_error(Unix.ECONNREFUSED, "connect", "")"
Aug 04 10:28:32 raspberrypi tezos-node-prestart[9874]: Aug 4 10:28:32.701 - node_data_version: node data dir is up-to-date
Aug 04 10:28:32 raspberrypi tezos-node-start[9879]: Updating the node configuration...
Aug 04 10:28:34 raspberrypi tezos-node-start[9879]: Aug 4 10:28:34.136 - node.main: FULL access to RPC enabled; this is very risky. (addresses = 0.0.0.0)
Aug 04 10:28:34 raspberrypi tezos-node-start[9879]: Aug 4 10:28:34.147 - node.config.validation: the node configuration has been successfully validated.
Aug 04 10:28:35 raspberrypi tezos-node-start[9879]: Aug 4 10:28:35.554 - node.config.validation: the node configuration has been successfully validated.
Aug 04 10:28:35 raspberrypi tezos-node-start[9879]: Aug 4 10:28:35.555 - node.main: read identity file (peer_id = idsbhivPq5xxtiom2Ny18XXRr9CFNi)
Aug 04 10:28:35 raspberrypi tezos-node-start[9879]: Aug 4 10:28:35.556 - node.main: starting the Tezos node v14.0 (4ca33194) (chain = TEZOS_MAINNET)
Aug 04 10:28:36 raspberrypi tezos-node-start[9879]: Aug 4 10:28:36.604 - node.main: disabled local peer discovery
Aug 04 10:28:36 raspberrypi tezos-node-start[9879]: Aug 4 10:28:36.614 - node: shell-node initialization: bootstrapping
Aug 04 10:28:38 raspberrypi tezos-node-start[9879]: Aug 4 10:28:38.284 - node: shell-node initialization: p2p_maintain_started
Aug 04 10:28:38 raspberrypi tezos-node-start[9879]: Aug 4 10:28:38.284 - external_block_validator: initialized
Aug 04 10:28:39 raspberrypi tezos-node-start[9879]: Aug 4 10:28:39.565 - external_block_validator: block validator process started with pid 9913
Aug 04 10:28:55 raspberrypi tezos-node-start[9879]: Aug 4 10:28:55.456 - node.validator: activate chain NetXdQprcVkpaWU
Aug 04 10:28:55 raspberrypi tezos-node-start[9879]: Aug 4 10:28:55.457 - p2p.maintenance: too few connections (0)
Aug 04 10:28:55 raspberrypi tezos-node-start[9879]: Aug 4 10:28:55.462 - validator.chain: Sync_status: unsync
Aug 04 10:28:55 raspberrypi tezos-node-start[9879]: Aug 4 10:28:55.469 - node.main: starting RPC server on ::ffff:127.0.0.1:8732 (acl = AllowAll) (tls = false)
Aug 04 10:28:55 raspberrypi tezos-node-start[9879]: Aug 4 10:28:55.470 - node.main: starting RPC server on ::ffff:0.0.0.0:8732 (acl = AllowAll) (tls = false)
Aug 04 10:28:55 raspberrypi tezos-node-start[9879]: Aug 4 10:28:55.471 - node.main: the Tezos node is now running
Aug 04 10:28:56 raspberrypi tezos-node-start[9879]: Aug 4 10:28:56.045 - node.validator.bootstrap_pipeline: fetching branch of about 2 blocks from peer idt9hT87Qnfu9QVPsWGigCAdPCar5k in
Aug 04 10:28:56 raspberrypi tezos-node-start[9879]: Aug 4 10:28:56.045 - node.validator.bootstrap_pipeline: 1 steps
Aug 04 10:28:56 raspberrypi tezos-node-start[9879]: Aug 4 10:28:56.056 - node.validator.bootstrap_pipeline: fetching branch of about 2 blocks from peer idtKX8X3RMGtubZyZZgg6NaS4H6Ay9 in
Aug 04 10:28:56 raspberrypi tezos-node-start[9879]: Aug 4 10:28:56.056 - node.validator.bootstrap_pipeline: 1 steps
Aug 04 10:28:59 raspberrypi tezos-baker-012-psithaca-start[9880]: Disclaimer:
Aug 04 10:28:59 raspberrypi tezos-baker-012-psithaca-start[9880]: The Tezos network is a new blockchain technology.
Aug 04 10:28:59 raspberrypi tezos-baker-012-psithaca-start[9880]: Users are solely responsible for any risks associated
Aug 04 10:28:59 raspberrypi tezos-baker-012-psithaca-start[9880]: with usage of the Tezos network. Users should do their
Aug 04 10:28:59 raspberrypi tezos-baker-012-psithaca-start[9880]: own research to determine if Tezos is the appropriate
Aug 04 10:28:59 raspberrypi tezos-baker-012-psithaca-start[9880]: platform for their needs and should apply judgement and
Aug 04 10:28:59 raspberrypi tezos-baker-012-psithaca-start[9880]: care in their network interactions.
Aug 04 10:29:00 raspberrypi tezos-baker-013-ptjakart-start[9882]: Disclaimer:
Aug 04 10:29:00 raspberrypi tezos-baker-013-ptjakart-start[9882]: The Tezos network is a new blockchain technology.
Aug 04 10:29:00 raspberrypi tezos-baker-013-ptjakart-start[9882]: Users are solely responsible for any risks associated
Aug 04 10:29:00 raspberrypi tezos-baker-013-ptjakart-start[9882]: with usage of the Tezos network. Users should do their
Aug 04 10:29:00 raspberrypi tezos-baker-013-ptjakart-start[9882]: own research to determine if Tezos is the appropriate
Aug 04 10:29:00 raspberrypi tezos-baker-013-ptjakart-start[9882]: platform for their needs and should apply judgement and
Aug 04 10:29:00 raspberrypi tezos-baker-013-ptjakart-start[9882]: care in their network interactions.
Aug 04 10:29:00 raspberrypi tezos-baker-012-psithaca-start[9880]: Waiting for the node to be bootstrapped...
Aug 04 10:29:02 raspberrypi tezos-baker-013-ptjakart-start[9882]: Aug 4 10:29:02.790 - 013-PtJakart.baker: reading per block vote file path: per_block_votes.json
Aug 04 10:29:03 raspberrypi tezos-baker-013-ptjakart-start[9882]: Waiting for the node to be bootstrapped...
Aug 04 10:29:07 raspberrypi tezos-node-start[9879]: Aug 4 10:29:07.162 - node.validator.bootstrap_pipeline: fetching branch of about 2 blocks from peer idt2DHVx3auSRS1Nv5AoKPm6bJw28Q in
Aug 04 10:29:07 raspberrypi tezos-node-start[9879]: Aug 4 10:29:07.162 - node.validator.bootstrap_pipeline: 1 steps
Aug 04 10:29:10 raspberrypi tezos-node-start[9879]: Aug 4 10:29:10.109 - validator.block: block BM5rZQrmnvj2mDYZG9x5ncedG2QMHqgXJypD73756d1KQpvKc5T successfully validated
Aug 04 10:29:10 raspberrypi tezos-node-start[9879]: Aug 4 10:29:10.109 - validator.block: Request pushed on 2022-08-04T14:28:56.274-00:00, treated in 4.159ms, completed in 13.830s
Aug 04 10:29:10 raspberrypi tezos-node-start[9879]: Aug 4 10:29:10.629 - validator.chain: Update current head to BM5rZQrmnvj2mDYZG9x5ncedG2QMHqgXJypD73756d1KQpvKc5T (level 2592876, timestamp 2022-08-04T14:28:44-00:00, fitness 02::0027906c::::ffffffff::00000000), same branch
Aug 04 10:29:10 raspberrypi tezos-node-start[9879]: Aug 4 10:29:10.629 - validator.chain: Request pushed on 2022-08-04T14:29:10.108-00:00, treated in 1.800ms, completed in 519ms
Aug 04 10:29:10 raspberrypi tezos-baker-013-ptjakart-start[9882]: Current head: BM5rZQrmnvj2 (timestamp: 2022-08-04T14:28:44.000-00:00, validation: 2022-08-04T14:29:10.629-00:00)
Aug 04 10:29:10 raspberrypi tezos-baker-012-psithaca-start[9880]: Current head: BM5rZQrmnvj2 (timestamp: 2022-08-04T14:28:44.000-00:00, validation: 2022-08-04T14:29:10.630-00:00)
Aug 04 10:29:19 raspberrypi tezos-node-start[9879]: Aug 4 10:29:19.211 - validator.block: block BMPYMQQY4HM3K3By8ECuqVUS2hF2QhiD531YY3rCdkMoFe1jquk successfully validated
Aug 04 10:29:19 raspberrypi tezos-node-start[9879]: Aug 4 10:29:19.211 - validator.block: Request pushed on 2022-08-04T14:29:16.276-00:00, treated in 4.29ms, completed in 2.930s
Aug 04 10:29:19 raspberrypi tezos-node-start[9879]: Aug 4 10:29:19.393 - validator.chain: Update current head to BMPYMQQY4HM3K3By8ECuqVUS2hF2QhiD531YY3rCdkMoFe1jquk (level 2592877, timestamp 2022-08-04T14:29:14-00:00, fitness 02::0027906d::::ffffffff::00000000), same branch
Aug 04 10:29:19 raspberrypi tezos-node-start[9879]: Aug 4 10:29:19.393 - validator.chain: Request pushed on 2022-08-04T14:29:19.210-00:00, treated in 287us, completed in 182ms
Aug 04 10:29:19 raspberrypi tezos-baker-013-ptjakart-start[9882]: Current head: BMPYMQQY4HM3 (timestamp: 2022-08-04T14:29:14.000-00:00, validation: 2022-08-04T14:29:19.394-00:00)
Aug 04 10:29:19 raspberrypi tezos-baker-012-psithaca-start[9880]: Current head: BMPYMQQY4HM3 (timestamp: 2022-08-04T14:29:14.000-00:00, validation: 2022-08-04T14:29:19.394-00:00)
Aug 04 10:29:28 raspberrypi tezos-node-start[9879]: Aug 4 10:29:28.046 - validator.chain: Sync_status: sync
Aug 04 10:29:28 raspberrypi tezos-node-start[9879]: Aug 4 10:29:28.224 - validator.chain: Chain is bootstrapped
Aug 04 10:29:28 raspberrypi tezos-baker-013-ptjakart-start[9882]: Node is bootstrapped.
Aug 04 10:29:28 raspberrypi tezos-baker-013-ptjakart-start[9882]: Waiting for protocol 013-PtJakart to start...
Aug 04 10:29:28 raspberrypi tezos-baker-013-ptjakart-start[9882]: Baker v14.0 (4ca33194) for PtJakart2xVj started.
Aug 04 10:29:29 raspberrypi tezos-baker-013-ptjakart-start[9882]: Error:
Aug 04 10:29:29 raspberrypi tezos-baker-013-ptjakart-start[9882]: Pack_error: "Migration_needed"
Aug 04 10:29:29 raspberrypi tezos-baker-012-psithaca-start[9880]: (/usr/bin/tezos-baker-012-Psithaca) TERM: triggering shutdown.
Aug 04 10:29:29 raspberrypi tezos-baker-012-psithaca-start[9880]: Fatal error:
Aug 04 10:29:29 raspberrypi tezos-baker-012-psithaca-start[9880]: Lwt.Resolution_loop.Canceled
Aug 04 10:29:29 raspberrypi tezos-node-start[9879]: (/usr/bin/tezos-node) TERM: triggering shutdown.
Aug 04 10:29:29 raspberrypi tezos-node-start[9879]: (/usr/bin/tezos-node) TERM: triggering shutdown.
Aug 04 10:29:29 raspberrypi tezos-node-start[9879]: Aug 4 10:29:29.390 - node.main: shutting down the Tezos node
Aug 04 10:29:29 raspberrypi tezos-node-start[9879]: Aug 4 10:29:29.395 - node.validator: shutting down the chain validator NetXdQprcVkpaWU
Aug 04 10:29:29 raspberrypi tezos-node-start[9879]: Aug 4 10:29:29.395 - node.distributed_db.requester: shutting down requester
Aug 04 10:29:29 raspberrypi tezos-node-start[9879]: Aug 4 10:29:29.396 - node.distributed_db.requester: shutting down requester
Aug 04 10:29:29 raspberrypi tezos-node-start[9879]: Aug 4 10:29:29.402 - node.validator: shutting down the block validator
Aug 04 10:29:29 raspberrypi tezos-node-start[9879]: Aug 4 10:29:29.403 - external_block_validator: shutting down
Aug 04 10:29:29 raspberrypi tezos-node-start[9879]: Aug 4 10:29:29.492 - external_block_validator: process terminated abnormally with exit code 127
Aug 04 10:29:29 raspberrypi tezos-node-start[9879]: Aug 4 10:29:29.504 - p2p: shutting down the p2p's welcome worker...
Aug 04 10:29:29 raspberrypi tezos-node-start[9879]: Aug 4 10:29:29.505 - p2p: shutting down the p2p's network maintenance worker...
Aug 04 10:29:29 raspberrypi tezos-node-start[9879]: Aug 4 10:29:29.515 - p2p: shutting down the p2p connection pool...
Aug 04 10:29:32 raspberrypi tezos-node-start[9879]: (/usr/bin/tezos-node) TERM: send signal again to force-quit.
Aug 04 10:29:32 raspberrypi tezos-node-start[9879]: Aug 4 10:29:32.546 - p2p: shutting down the p2p connection handler...
Aug 04 10:29:32 raspberrypi tezos-node-start[9879]: Aug 4 10:29:32.546 - p2p: shutting down the p2p scheduler...
Aug 04 10:29:32 raspberrypi tezos-node-start[9879]: Aug 4 10:29:32.546 - node.main: shutting down the RPC server
Aug 04 10:29:32 raspberrypi tezos-node-start[9879]: (/usr/bin/tezos-node) Exit: uncaught exception during clean-up (File "src/bin_node/node_run_command.ml", line 588, characters 11-18): in bind: Address already in use
Aug 04 10:29:32 raspberrypi tezos-node-start[9879]: (/usr/bin/tezos-node) Exit: uncaught exception during clean-up (File "src/bin_node/node_run_command.ml", line 579, characters 11-18): in bind: Address already in use
Aug 04 10:29:32 raspberrypi tezos-node-start[9879]: (/usr/bin/tezos-node) Exit: clean-up callback failed (File "src/bin_node/node_run_command.ml", line 579, characters 11-18): in bind: Address already in use
Aug 04 10:29:32 raspberrypi tezos-node-start[9879]: (/usr/bin/tezos-node) Exit: clean-up callback failed (File "src/bin_node/node_run_command.ml", line 588, characters 11-18): in bind: Address already in use
Aug 04 10:29:34 raspberrypi tezos-baking-prestart[11529]: Warning:
Aug 04 10:29:34 raspberrypi tezos-baking-prestart[11529]: Failed to acquire the protocol version from the node
Aug 04 10:29:34 raspberrypi tezos-baking-prestart[11529]: Rpc request failed:
Aug 04 10:29:34 raspberrypi tezos-baking-prestart[11529]: - meth: GET
Aug 04 10:29:34 raspberrypi tezos-baking-prestart[11529]: - uri: http://localhost:8732/chains/main/blocks/head/protocols
Aug 04 10:29:34 raspberrypi tezos-baking-prestart[11529]: - error: Unable to connect to the node: "Unix.Unix_error(Unix.ECONNREFUSED, "connect", "")"
Aug 04 10:29:35 raspberrypi tezos-baking-start[11535]: Warning:
Aug 04 10:29:35 raspberrypi tezos-baking-start[11535]: Failed to acquire the protocol version from the node
Aug 04 10:29:35 raspberrypi tezos-baking-start[11535]: Rpc request failed:
Aug 04 10:29:35 raspberrypi tezos-baking-start[11535]: - meth: GET
Aug 04 10:29:35 raspberrypi tezos-baking-start[11535]: - uri: http://localhost:8732/chains/main/blocks/head/protocols
Aug 04 10:29:35 raspberrypi tezos-baking-start[11535]: - error: Unable to connect to the node: "Unix.Unix_error(Unix.ECONNREFUSED, "connect", "")"
Aug 04 10:29:36 raspberrypi tezos-node-prestart[11544]: Aug 4 10:29:36.929 - node_data_version: node data dir is up-to-date
Aug 04 10:29:36 raspberrypi tezos-node-start[11549]: Updating the node configuration...
Aug 04 10:29:38 raspberrypi tezos-node-start[11549]: Aug 4 10:29:38.429 - node.main: FULL access to RPC enabled; this is very risky. (addresses = 0.0.0.0)
Aug 04 10:29:38 raspberrypi tezos-node-start[11549]: Aug 4 10:29:38.479 - node.config.validation: the node configuration has been successfully validated.
Aug 04 10:29:39 raspberrypi tezos-node-start[11549]: Aug 4 10:29:39.993 - node.config.validation: the node configuration has been successfully validated.
Aug 04 10:29:39 raspberrypi tezos-node-start[11549]: Aug 4 10:29:39.997 - node.main: read identity file (peer_id = idsbhivPq5xxtiom2Ny18XXRr9CFNi)
Aug 04 10:29:39 raspberrypi tezos-node-start[11549]: Aug 4 10:29:39.997 - node.main: starting the Tezos node v14.0 (4ca33194) (chain = TEZOS_MAINNET)
Aug 04 10:29:41 raspberrypi tezos-node-start[11549]: Aug 4 10:29:41.055 - node.main: disabled local peer discovery
Aug 04 10:29:41 raspberrypi tezos-node-start[11549]: Aug 4 10:29:41.067 - node: shell-node initialization: bootstrapping
Aug 04 10:29:42 raspberrypi tezos-node-start[11549]: Aug 4 10:29:42.704 - node: shell-node initialization: p2p_maintain_started
Aug 04 10:29:42 raspberrypi tezos-node-start[11549]: Aug 4 10:29:42.704 - external_block_validator: initialized
Aug 04 10:29:44 raspberrypi tezos-node-start[11549]: Aug 4 10:29:44.031 - external_block_validator: block validator process started with pid 11805
Aug 04 10:29:59 raspberrypi tezos-node-start[11549]: Aug 4 10:29:59.820 - node.validator: activate chain NetXdQprcVkpaWU
Aug 04 10:29:59 raspberrypi tezos-node-start[11549]: Aug 4 10:29:59.822 - p2p.maintenance: too few connections (0)
Aug 04 10:29:59 raspberrypi tezos-node-start[11549]: Aug 4 10:29:59.825 - validator.chain: Sync_status: unsync
Aug 04 10:29:59 raspberrypi tezos-node-start[11549]: Aug 4 10:29:59.826 - node.main: starting RPC server on ::ffff:127.0.0.1:8732 (acl = AllowAll) (tls = false)
Aug 04 10:29:59 raspberrypi tezos-node-start[11549]: Aug 4 10:29:59.827 - node.main: starting RPC server on ::ffff:0.0.0.0:8732 (acl = AllowAll) (tls = false)
Aug 04 10:29:59 raspberrypi tezos-node-start[11549]: Aug 4 10:29:59.828 - node.main: the Tezos node is now running
Aug 04 10:30:01 raspberrypi tezos-node-start[11549]: Aug 4 10:30:01.003 - node.validator.bootstrap_pipeline: fetching branch of about 2 blocks from peer idt1y2MVaWNkzgX5jitBoChS1M9vzF in
Aug 04 10:30:01 raspberrypi tezos-node-start[11549]: Aug 4 10:30:01.003 - node.validator.bootstrap_pipeline: 1 steps
Aug 04 10:30:01 raspberrypi tezos-node-start[11549]: Aug 4 10:30:01.340 - node.validator.bootstrap_pipeline: fetching branch of about 2 blocks from peer idrJMsqX35ziYZWTzwgMMmWtz7UQWG in
Aug 04 10:30:01 raspberrypi tezos-node-start[11549]: Aug 4 10:30:01.340 - node.validator.bootstrap_pipeline: 1 steps
Aug 04 10:30:02 raspberrypi tezos-node-start[11549]: Aug 4 10:30:02.040 - node.validator.bootstrap_pipeline: fetching branch of about 2 blocks from peer idsBHgHBHjJ4iskr6sXhkhBKX1b3T2 in
Aug 04 10:30:02 raspberrypi tezos-node-start[11549]: Aug 4 10:30:02.041 - node.validator.bootstrap_pipeline: 1 steps
Aug 04 10:30:03 raspberrypi tezos-node-start[11549]: Aug 4 10:30:03.995 - node.validator.bootstrap_pipeline: fetching branch of about 2 blocks from peer idtdudfwXzH46QVhxmvxaJLxAu3UvK in
Aug 04 10:30:03 raspberrypi tezos-node-start[11549]: Aug 4 10:30:03.996 - node.validator.bootstrap_pipeline: 1 steps
Aug 04 10:30:04 raspberrypi tezos-baker-012-psithaca-start[11550]: Disclaimer:
Aug 04 10:30:04 raspberrypi tezos-baker-012-psithaca-start[11550]: The Tezos network is a new blockchain technology.
Aug 04 10:30:04 raspberrypi tezos-baker-012-psithaca-start[11550]: Users are solely responsible for any risks associated
Aug 04 10:30:04 raspberrypi tezos-baker-012-psithaca-start[11550]: with usage of the Tezos network. Users should do their
Aug 04 10:30:04 raspberrypi tezos-baker-012-psithaca-start[11550]: own research to determine if Tezos is the appropriate
Aug 04 10:30:04 raspberrypi tezos-baker-012-psithaca-start[11550]: platform for their needs and should apply judgement and
Aug 04 10:30:04 raspberrypi tezos-baker-012-psithaca-start[11550]: care in their network interactions.
Aug 04 10:30:04 raspberrypi tezos-node-start[11549]: Aug 4 10:30:04.394 - node.validator.bootstrap_pipeline: fetching branch of about 2 blocks from peer idsrQBDC7v8DQqmnLdHVWbrTEU93Zq in
Aug 04 10:30:04 raspberrypi tezos-node-start[11549]: Aug 4 10:30:04.394 - node.validator.bootstrap_pipeline: 1 steps
Aug 04 10:30:05 raspberrypi tezos-baker-013-ptjakart-start[11552]: Disclaimer:
Aug 04 10:30:05 raspberrypi tezos-baker-013-ptjakart-start[11552]: The Tezos network is a new blockchain technology.
Aug 04 10:30:05 raspberrypi tezos-baker-013-ptjakart-start[11552]: Users are solely responsible for any risks associated
Aug 04 10:30:05 raspberrypi tezos-baker-013-ptjakart-start[11552]: with usage of the Tezos network. Users should do their
Aug 04 10:30:05 raspberrypi tezos-baker-013-ptjakart-start[11552]: own research to determine if Tezos is the appropriate
Aug 04 10:30:05 raspberrypi tezos-baker-013-ptjakart-start[11552]: platform for their needs and should apply judgement and
Aug 04 10:30:05 raspberrypi tezos-baker-013-ptjakart-start[11552]: care in their network interactions.
Aug 04 10:30:05 raspberrypi tezos-baker-012-psithaca-start[11550]: Waiting for the node to be bootstrapped...
Aug 04 10:30:07 raspberrypi tezos-baker-013-ptjakart-start[11552]: Aug 4 10:30:07.256 - 013-PtJakart.baker: reading per block vote file path: per_block_votes.json
Aug 04 10:30:07 raspberrypi tezos-baker-013-ptjakart-start[11552]: Waiting for the node to be bootstrapped...
Aug 04 10:30:14 raspberrypi tezos-node-start[11549]: Aug 4 10:30:14.710 - validator.block: block BM1MZE5zaDUmQ8id9ZifXt2PXv3imUocADyWNuj1JugE85RYNpH successfully validated
Aug 04 10:30:14 raspberrypi tezos-node-start[11549]: Aug 4 10:30:14.710 - validator.block: Request pushed on 2022-08-04T14:30:01.269-00:00, treated in 40.129us, completed in 13.440s
Aug 04 10:30:15 raspberrypi tezos-node-start[11549]: Aug 4 10:30:15.210 - validator.chain: Update current head to BM1MZE5zaDUmQ8id9ZifXt2PXv3imUocADyWNuj1JugE85RYNpH (level 2592878, timestamp 2022-08-04T14:29:44-00:00, fitness 02::0027906e::::ffffffff::00000000), same branch
Aug 04 10:30:15 raspberrypi tezos-node-start[11549]: Aug 4 10:30:15.210 - validator.chain: Request pushed on 2022-08-04T14:30:14.710-00:00, treated in 427us, completed in 499ms
Aug 04 10:30:15 raspberrypi tezos-baker-013-ptjakart-start[11552]: Current head: BM1MZE5zaDUm (timestamp: 2022-08-04T14:29:44.000-00:00, validation: 2022-08-04T14:30:15.212-00:00)
Aug 04 10:30:15 raspberrypi tezos-baker-012-psithaca-start[11550]: Current head: BM1MZE5zaDUm (timestamp: 2022-08-04T14:29:44.000-00:00, validation: 2022-08-04T14:30:15.212-00:00)
Aug 04 10:30:15 raspberrypi tezos-node-start[11549]: Aug 4 10:30:15.215 - validator.chain: Sync_status: sync
Aug 04 10:30:15 raspberrypi tezos-node-start[11549]: Aug 4 10:30:15.335 - validator.chain: Chain is bootstrapped
Aug 04 10:30:15 raspberrypi tezos-baker-013-ptjakart-start[11552]: Node is bootstrapped.
Aug 04 10:30:15 raspberrypi tezos-baker-013-ptjakart-start[11552]: Waiting for protocol 013-PtJakart to start...
Aug 04 10:30:15 raspberrypi tezos-baker-013-ptjakart-start[11552]: Baker v14.0 (4ca33194) for PtJakart2xVj started.
Aug 04 10:30:16 raspberrypi tezos-baker-013-ptjakart-start[11552]: Error:
Aug 04 10:30:16 raspberrypi tezos-baker-013-ptjakart-start[11552]: Pack_error: "Migration_needed"
Aug 04 10:30:16 raspberrypi tezos-baker-012-psithaca-start[11550]: (/usr/bin/tezos-baker-012-Psithaca) TERM: triggering shutdown.
Aug 04 10:30:16 raspberrypi tezos-baker-012-psithaca-start[11550]: Fatal error:
Aug 04 10:30:16 raspberrypi tezos-baker-012-psithaca-start[11550]: Lwt.Resolution_loop.Canceled
Aug 04 10:30:16 raspberrypi tezos-node-start[11549]: (/usr/bin/tezos-node) TERM: triggering shutdown.
Aug 04 10:30:16 raspberrypi tezos-node-start[11549]: (/usr/bin/tezos-node) TERM: triggering shutdown.
Aug 04 10:30:16 raspberrypi tezos-node-start[11549]: Aug 4 10:30:16.878 - node.main: shutting down the Tezos node
Aug 04 10:30:16 raspberrypi tezos-node-start[11549]: Aug 4 10:30:16.881 - node.validator: shutting down the chain validator NetXdQprcVkpaWU
Aug 04 10:30:16 raspberrypi tezos-node-start[11549]: Aug 4 10:30:16.882 - node.distributed_db.requester: shutting down requester
Aug 04 10:30:16 raspberrypi tezos-node-start[11549]: Aug 4 10:30:16.885 - node.distributed_db.requester: shutting down requester
Aug 04 10:30:16 raspberrypi tezos-node-start[11549]: Aug 4 10:30:16.893 - node.validator: shutting down the block validator
Aug 04 10:30:16 raspberrypi tezos-node-start[11549]: Aug 4 10:30:16.894 - external_block_validator: shutting down
Aug 04 10:30:16 raspberrypi tezos-node-start[11549]: Aug 4 10:30:16.992 - external_block_validator: process terminated abnormally with exit code 127
Aug 04 10:30:16 raspberrypi tezos-node-start[11549]: Aug 4 10:30:16.994 - p2p: shutting down the p2p's welcome worker...
Aug 04 10:30:16 raspberrypi tezos-node-start[11549]: Aug 4 10:30:16.994 - p2p: shutting down the p2p's network maintenance worker...
Aug 04 10:30:17 raspberrypi tezos-node-start[11549]: Aug 4 10:30:17.014 - p2p: shutting down the p2p connection pool...
Aug 04 10:30:19 raspberrypi tezos-node-start[11549]: (/usr/bin/tezos-node) TERM: send signal again to force-quit.
Aug 04 10:30:19 raspberrypi tezos-node-start[11549]: Aug 4 10:30:19.720 - p2p: shutting down the p2p connection handler...
Aug 04 10:30:19 raspberrypi tezos-node-start[11549]: Aug 4 10:30:19.720 - p2p: shutting down the p2p scheduler...
Aug 04 10:30:19 raspberrypi tezos-node-start[11549]: Aug 4 10:30:19.720 - node.main: shutting down the RPC server
Aug 04 10:30:19 raspberrypi tezos-node-start[11549]: (/usr/bin/tezos-node) Exit: uncaught exception during clean-up (File "src/bin_node/node_run_command.ml", line 588, characters 11-18): in bind: Address already in use
Aug 04 10:30:19 raspberrypi tezos-node-start[11549]: (/usr/bin/tezos-node) Exit: uncaught exception during clean-up (File "src/bin_node/node_run_command.ml", line 579, characters 11-18): in bind: Address already in use
Aug 04 10:30:19 raspberrypi tezos-node-start[11549]: (/usr/bin/tezos-node) Exit: clean-up callback failed (File "src/bin_node/node_run_command.ml", line 579, characters 11-18): in bind: Address already in use
Aug 04 10:30:19 raspberrypi tezos-node-start[11549]: (/usr/bin/tezos-node) Exit: clean-up callback failed (File "src/bin_node/node_run_command.ml", line 588, characters 11-18): in bind: Address already in use
Aug 04 10:30:21 raspberrypi tezos-baking-prestart[12830]: Warning:
Aug 04 10:30:21 raspberrypi tezos-baking-prestart[12830]: Failed to acquire the protocol version from the node
Aug 04 10:30:21 raspberrypi tezos-baking-prestart[12830]: Rpc request failed:
Aug 04 10:30:21 raspberrypi tezos-baking-prestart[12830]: - meth: GET
Aug 04 10:30:21 raspberrypi tezos-baking-prestart[12830]: - uri: http://localhost:8732/chains/main/blocks/head/protocols
Aug 04 10:30:21 raspberrypi tezos-baking-prestart[12830]: - error: Unable to connect to the node: "Unix.Unix_error(Unix.ECONNREFUSED, "connect", "")"
Aug 04 10:30:23 raspberrypi tezos-baking-start[12990]: Warning:
Aug 04 10:30:23 raspberrypi tezos-baking-start[12990]: Failed to acquire the protocol version from the node
Aug 04 10:30:23 raspberrypi tezos-baking-start[12990]: Rpc request failed:
Aug 04 10:30:23 raspberrypi tezos-baking-start[12990]: - meth: GET
Aug 04 10:30:23 raspberrypi tezos-baking-start[12990]: - uri: http://localhost:8732/chains/main/blocks/head/protocols
Aug 04 10:30:23 raspberrypi tezos-baking-start[12990]: - error: Unable to connect to the node: "Unix.Unix_error(Unix.ECONNREFUSED, "connect", "")"
Aug 04 10:30:24 raspberrypi tezos-node-prestart[12999]: Aug 4 10:30:24.383 - node_data_version: node data dir is up-to-date
Aug 04 10:30:24 raspberrypi tezos-node-start[13004]: Updating the node configuration...
Aug 04 10:30:25 raspberrypi tezos-node-start[13004]: Aug 4 10:30:25.814 - node.main: FULL access to RPC enabled; this is very risky. (addresses = 0.0.0.0)
Aug 04 10:30:25 raspberrypi tezos-node-start[13004]: Aug 4 10:30:25.825 - node.config.validation: the node configuration has been successfully validated.
Aug 04 10:30:27 raspberrypi tezos-node-start[13004]: Aug 4 10:30:27.303 - node.config.validation: the node configuration has been successfully validated.
```
# Expected behavior
Services restart after upgrade without errors, stay up
# Environment
- OS: RaspberryPi OS 64-bit
- branch/revision: upgrade octez 13 -> 14
# Additional context
<!--
Add any other context about the problem here.
-->
| priority | services using non default node data directory enter infinite crash restart loop after upgrade description a clear and concise description of what the bug is to reproduce steps to reproduce the behavior set up baking with tezos setup wizard on using octez packages apt update apt upgrade observe baker and node services now constantly restart with pack error migration needed error seen in the logs for the baker ug raspberrypi tezos node start aug validator chain request pushed on treated in completed in aug raspberrypi tezos node start aug validator chain sync status sync aug raspberrypi tezos baker ptjakart start current head timestamp validation aug raspberrypi tezos baker psithaca start current head timestamp validation aug raspberrypi tezos node start aug validator chain chain is bootstrapped aug raspberrypi tezos baker ptjakart start node is bootstrapped aug raspberrypi tezos baker ptjakart start waiting for protocol ptjakart to start aug raspberrypi tezos baker ptjakart start baker for started aug raspberrypi tezos baker ptjakart start error aug raspberrypi tezos baker ptjakart start pack error migration needed aug raspberrypi tezos baker psithaca start usr bin tezos baker psithaca term triggering shutdown aug raspberrypi tezos baker psithaca start fatal error aug raspberrypi tezos baker psithaca start lwt resolution loop canceled aug raspberrypi tezos node start usr bin tezos node term triggering shutdown aug raspberrypi tezos node start usr bin tezos node term triggering shutdown aug raspberrypi tezos node start aug node main shutting down the tezos node aug raspberrypi tezos node start aug node validator shutting down the chain validator netxdqprcvkpawu aug raspberrypi tezos node start aug node distributed db requester shutting down requester aug raspberrypi tezos node start aug node distributed db requester shutting down requester aug raspberrypi tezos node start aug node validator shutting down the block validator aug raspberrypi tezos node start aug external block validator shutting down aug raspberrypi tezos node start aug external block validator process terminated abnormally with exit code aug raspberrypi tezos node start aug shutting down the s welcome worker aug raspberrypi tezos node start aug shutting down the s network maintenance worker aug raspberrypi tezos node start aug shutting down the connection pool aug raspberrypi tezos node start usr bin tezos node term send signal again to force quit aug raspberrypi tezos node start aug shutting down the connection handler aug raspberrypi tezos node start aug shutting down the scheduler aug raspberrypi tezos node start aug node main shutting down the rpc server aug raspberrypi tezos node start usr bin tezos node exit uncaught exception during clean up file src bin node node run command ml line characters in bind address already in use aug raspberrypi tezos node start usr bin tezos node exit uncaught exception during clean up file src bin node node run command ml line characters in bind address already in use aug raspberrypi tezos node start usr bin tezos node exit clean up callback failed file src bin node node run command ml line characters in bind address already in use aug raspberrypi tezos node start usr bin tezos node exit clean up callback failed file src bin node node run command ml line characters in bind address already in use aug raspberrypi tezos baking prestart warning aug raspberrypi tezos baking prestart failed to acquire the protocol version from the node aug raspberrypi tezos baking prestart rpc request failed aug raspberrypi tezos baking prestart meth get aug raspberrypi tezos baking prestart uri aug raspberrypi tezos baking prestart error unable to connect to the node unix unix error unix econnrefused connect aug raspberrypi tezos baking start warning aug raspberrypi tezos baking start failed to acquire the protocol version from the node aug raspberrypi tezos baking start rpc request failed aug raspberrypi tezos baking start meth get aug raspberrypi tezos baking start uri aug raspberrypi tezos baking start error unable to connect to the node unix unix error unix econnrefused connect aug raspberrypi tezos node prestart aug node data version node data dir is up to date aug raspberrypi tezos node start updating the node configuration aug raspberrypi tezos node start aug node main full access to rpc enabled this is very risky addresses aug raspberrypi tezos node start aug node config validation the node configuration has been successfully validated aug raspberrypi tezos node start aug node config validation the node configuration has been successfully validated aug raspberrypi tezos node start aug node main read identity file peer id aug raspberrypi tezos node start aug node main starting the tezos node chain tezos mainnet aug raspberrypi tezos node start aug node main disabled local peer discovery aug raspberrypi tezos node start aug node shell node initialization bootstrapping aug raspberrypi tezos node start aug node shell node initialization maintain started aug raspberrypi tezos node start aug external block validator initialized aug raspberrypi tezos node start aug external block validator block validator process started with pid aug raspberrypi tezos node start aug node validator activate chain netxdqprcvkpawu aug raspberrypi tezos node start aug maintenance too few connections aug raspberrypi tezos node start aug validator chain sync status unsync aug raspberrypi tezos node start aug node main starting rpc server on ffff acl allowall tls false aug raspberrypi tezos node start aug node main starting rpc server on ffff acl allowall tls false aug raspberrypi tezos node start aug node main the tezos node is now running aug raspberrypi tezos node start aug node validator bootstrap pipeline fetching branch of about blocks from peer in aug raspberrypi tezos node start aug node validator bootstrap pipeline steps aug raspberrypi tezos node start aug node validator bootstrap pipeline fetching branch of about blocks from peer in aug raspberrypi tezos node start aug node validator bootstrap pipeline steps aug raspberrypi tezos baker psithaca start disclaimer aug raspberrypi tezos baker psithaca start the tezos network is a new blockchain technology aug raspberrypi tezos baker psithaca start users are solely responsible for any risks associated aug raspberrypi tezos baker psithaca start with usage of the tezos network users should do their aug raspberrypi tezos baker psithaca start own research to determine if tezos is the appropriate aug raspberrypi tezos baker psithaca start platform for their needs and should apply judgement and aug raspberrypi tezos baker psithaca start care in their network interactions aug raspberrypi tezos baker ptjakart start disclaimer aug raspberrypi tezos baker ptjakart start the tezos network is a new blockchain technology aug raspberrypi tezos baker ptjakart start users are solely responsible for any risks associated aug raspberrypi tezos baker ptjakart start with usage of the tezos network users should do their aug raspberrypi tezos baker ptjakart start own research to determine if tezos is the appropriate aug raspberrypi tezos baker ptjakart start platform for their needs and should apply judgement and aug raspberrypi tezos baker ptjakart start care in their network interactions aug raspberrypi tezos baker psithaca start waiting for the node to be bootstrapped aug raspberrypi tezos baker ptjakart start aug ptjakart baker reading per block vote file path per block votes json aug raspberrypi tezos baker ptjakart start waiting for the node to be bootstrapped aug raspberrypi tezos node start aug node validator bootstrap pipeline fetching branch of about blocks from peer in aug raspberrypi tezos node start aug node validator bootstrap pipeline steps aug raspberrypi tezos node start aug validator block block successfully validated aug raspberrypi tezos node start aug validator block request pushed on treated in completed in aug raspberrypi tezos node start aug validator chain update current head to level timestamp fitness ffffffff same branch aug raspberrypi tezos node start aug validator chain request pushed on treated in completed in aug raspberrypi tezos baker ptjakart start current head timestamp validation aug raspberrypi tezos baker psithaca start current head timestamp validation aug raspberrypi tezos node start aug validator block block successfully validated aug raspberrypi tezos node start aug validator block request pushed on treated in completed in aug raspberrypi tezos node start aug validator chain update current head to level timestamp fitness ffffffff same branch aug raspberrypi tezos node start aug validator chain request pushed on treated in completed in aug raspberrypi tezos baker ptjakart start current head timestamp validation aug raspberrypi tezos baker psithaca start current head timestamp validation aug raspberrypi tezos node start aug validator chain sync status sync aug raspberrypi tezos node start aug validator chain chain is bootstrapped aug raspberrypi tezos baker ptjakart start node is bootstrapped aug raspberrypi tezos baker ptjakart start waiting for protocol ptjakart to start aug raspberrypi tezos baker ptjakart start baker for started aug raspberrypi tezos baker ptjakart start error aug raspberrypi tezos baker ptjakart start pack error migration needed aug raspberrypi tezos baker psithaca start usr bin tezos baker psithaca term triggering shutdown aug raspberrypi tezos baker psithaca start fatal error aug raspberrypi tezos baker psithaca start lwt resolution loop canceled aug raspberrypi tezos node start usr bin tezos node term triggering shutdown aug raspberrypi tezos node start usr bin tezos node term triggering shutdown aug raspberrypi tezos node start aug node main shutting down the tezos node aug raspberrypi tezos node start aug node validator shutting down the chain validator netxdqprcvkpawu aug raspberrypi tezos node start aug node distributed db requester shutting down requester aug raspberrypi tezos node start aug node distributed db requester shutting down requester aug raspberrypi tezos node start aug node validator shutting down the block validator aug raspberrypi tezos node start aug external block validator shutting down aug raspberrypi tezos node start aug external block validator process terminated abnormally with exit code aug raspberrypi tezos node start aug shutting down the s welcome worker aug raspberrypi tezos node start aug shutting down the s network maintenance worker aug raspberrypi tezos node start aug shutting down the connection pool aug raspberrypi tezos node start usr bin tezos node term send signal again to force quit aug raspberrypi tezos node start aug shutting down the connection handler aug raspberrypi tezos node start aug shutting down the scheduler aug raspberrypi tezos node start aug node main shutting down the rpc server aug raspberrypi tezos node start usr bin tezos node exit uncaught exception during clean up file src bin node node run command ml line characters in bind address already in use aug raspberrypi tezos node start usr bin tezos node exit uncaught exception during clean up file src bin node node run command ml line characters in bind address already in use aug raspberrypi tezos node start usr bin tezos node exit clean up callback failed file src bin node node run command ml line characters in bind address already in use aug raspberrypi tezos node start usr bin tezos node exit clean up callback failed file src bin node node run command ml line characters in bind address already in use aug raspberrypi tezos baking prestart warning aug raspberrypi tezos baking prestart failed to acquire the protocol version from the node aug raspberrypi tezos baking prestart rpc request failed aug raspberrypi tezos baking prestart meth get aug raspberrypi tezos baking prestart uri aug raspberrypi tezos baking prestart error unable to connect to the node unix unix error unix econnrefused connect aug raspberrypi tezos baking start warning aug raspberrypi tezos baking start failed to acquire the protocol version from the node aug raspberrypi tezos baking start rpc request failed aug raspberrypi tezos baking start meth get aug raspberrypi tezos baking start uri aug raspberrypi tezos baking start error unable to connect to the node unix unix error unix econnrefused connect aug raspberrypi tezos node prestart aug node data version node data dir is up to date aug raspberrypi tezos node start updating the node configuration aug raspberrypi tezos node start aug node main full access to rpc enabled this is very risky addresses aug raspberrypi tezos node start aug node config validation the node configuration has been successfully validated aug raspberrypi tezos node start aug node config validation the node configuration has been successfully validated aug raspberrypi tezos node start aug node main read identity file peer id aug raspberrypi tezos node start aug node main starting the tezos node chain tezos mainnet aug raspberrypi tezos node start aug node main disabled local peer discovery aug raspberrypi tezos node start aug node shell node initialization bootstrapping aug raspberrypi tezos node start aug node shell node initialization maintain started aug raspberrypi tezos node start aug external block validator initialized aug raspberrypi tezos node start aug external block validator block validator process started with pid aug raspberrypi tezos node start aug node validator activate chain netxdqprcvkpawu aug raspberrypi tezos node start aug maintenance too few connections aug raspberrypi tezos node start aug validator chain sync status unsync aug raspberrypi tezos node start aug node main starting rpc server on ffff acl allowall tls false aug raspberrypi tezos node start aug node main starting rpc server on ffff acl allowall tls false aug raspberrypi tezos node start aug node main the tezos node is now running aug raspberrypi tezos node start aug node validator bootstrap pipeline fetching branch of about blocks from peer in aug raspberrypi tezos node start aug node validator bootstrap pipeline steps aug raspberrypi tezos node start aug node validator bootstrap pipeline fetching branch of about blocks from peer in aug raspberrypi tezos node start aug node validator bootstrap pipeline steps aug raspberrypi tezos node start aug node validator bootstrap pipeline fetching branch of about blocks from peer in aug raspberrypi tezos node start aug node validator bootstrap pipeline steps aug raspberrypi tezos node start aug node validator bootstrap pipeline fetching branch of about blocks from peer in aug raspberrypi tezos node start aug node validator bootstrap pipeline steps aug raspberrypi tezos baker psithaca start disclaimer aug raspberrypi tezos baker psithaca start the tezos network is a new blockchain technology aug raspberrypi tezos baker psithaca start users are solely responsible for any risks associated aug raspberrypi tezos baker psithaca start with usage of the tezos network users should do their aug raspberrypi tezos baker psithaca start own research to determine if tezos is the appropriate aug raspberrypi tezos baker psithaca start platform for their needs and should apply judgement and aug raspberrypi tezos baker psithaca start care in their network interactions aug raspberrypi tezos node start aug node validator bootstrap pipeline fetching branch of about blocks from peer in aug raspberrypi tezos node start aug node validator bootstrap pipeline steps aug raspberrypi tezos baker ptjakart start disclaimer aug raspberrypi tezos baker ptjakart start the tezos network is a new blockchain technology aug raspberrypi tezos baker ptjakart start users are solely responsible for any risks associated aug raspberrypi tezos baker ptjakart start with usage of the tezos network users should do their aug raspberrypi tezos baker ptjakart start own research to determine if tezos is the appropriate aug raspberrypi tezos baker ptjakart start platform for their needs and should apply judgement and aug raspberrypi tezos baker ptjakart start care in their network interactions aug raspberrypi tezos baker psithaca start waiting for the node to be bootstrapped aug raspberrypi tezos baker ptjakart start aug ptjakart baker reading per block vote file path per block votes json aug raspberrypi tezos baker ptjakart start waiting for the node to be bootstrapped aug raspberrypi tezos node start aug validator block block successfully validated aug raspberrypi tezos node start aug validator block request pushed on treated in completed in aug raspberrypi tezos node start aug validator chain update current head to level timestamp fitness ffffffff same branch aug raspberrypi tezos node start aug validator chain request pushed on treated in completed in aug raspberrypi tezos baker ptjakart start current head timestamp validation aug raspberrypi tezos baker psithaca start current head timestamp validation aug raspberrypi tezos node start aug validator chain sync status sync aug raspberrypi tezos node start aug validator chain chain is bootstrapped aug raspberrypi tezos baker ptjakart start node is bootstrapped aug raspberrypi tezos baker ptjakart start waiting for protocol ptjakart to start aug raspberrypi tezos baker ptjakart start baker for started aug raspberrypi tezos baker ptjakart start error aug raspberrypi tezos baker ptjakart start pack error migration needed aug raspberrypi tezos baker psithaca start usr bin tezos baker psithaca term triggering shutdown aug raspberrypi tezos baker psithaca start fatal error aug raspberrypi tezos baker psithaca start lwt resolution loop canceled aug raspberrypi tezos node start usr bin tezos node term triggering shutdown aug raspberrypi tezos node start usr bin tezos node term triggering shutdown aug raspberrypi tezos node start aug node main shutting down the tezos node aug raspberrypi tezos node start aug node validator shutting down the chain validator netxdqprcvkpawu aug raspberrypi tezos node start aug node distributed db requester shutting down requester aug raspberrypi tezos node start aug node distributed db requester shutting down requester aug raspberrypi tezos node start aug node validator shutting down the block validator aug raspberrypi tezos node start aug external block validator shutting down aug raspberrypi tezos node start aug external block validator process terminated abnormally with exit code aug raspberrypi tezos node start aug shutting down the s welcome worker aug raspberrypi tezos node start aug shutting down the s network maintenance worker aug raspberrypi tezos node start aug shutting down the connection pool aug raspberrypi tezos node start usr bin tezos node term send signal again to force quit aug raspberrypi tezos node start aug shutting down the connection handler aug raspberrypi tezos node start aug shutting down the scheduler aug raspberrypi tezos node start aug node main shutting down the rpc server aug raspberrypi tezos node start usr bin tezos node exit uncaught exception during clean up file src bin node node run command ml line characters in bind address already in use aug raspberrypi tezos node start usr bin tezos node exit uncaught exception during clean up file src bin node node run command ml line characters in bind address already in use aug raspberrypi tezos node start usr bin tezos node exit clean up callback failed file src bin node node run command ml line characters in bind address already in use aug raspberrypi tezos node start usr bin tezos node exit clean up callback failed file src bin node node run command ml line characters in bind address already in use aug raspberrypi tezos baking prestart warning aug raspberrypi tezos baking prestart failed to acquire the protocol version from the node aug raspberrypi tezos baking prestart rpc request failed aug raspberrypi tezos baking prestart meth get aug raspberrypi tezos baking prestart uri aug raspberrypi tezos baking prestart error unable to connect to the node unix unix error unix econnrefused connect aug raspberrypi tezos baking start warning aug raspberrypi tezos baking start failed to acquire the protocol version from the node aug raspberrypi tezos baking start rpc request failed aug raspberrypi tezos baking start meth get aug raspberrypi tezos baking start uri aug raspberrypi tezos baking start error unable to connect to the node unix unix error unix econnrefused connect aug raspberrypi tezos node prestart aug node data version node data dir is up to date aug raspberrypi tezos node start updating the node configuration aug raspberrypi tezos node start aug node main full access to rpc enabled this is very risky addresses aug raspberrypi tezos node start aug node config validation the node configuration has been successfully validated aug raspberrypi tezos node start aug node config validation the node configuration has been successfully validated expected behavior services restart after upgrade without errors stay up environment os raspberrypi os bit branch revision upgrade octez additional context add any other context about the problem here | 1 |
134,250 | 10,887,809,717 | IssuesEvent | 2019-11-18 15:11:35 | golang/go | https://api.github.com/repos/golang/go | closed | cmd/fix: incorrect loop variable aliasing in TestRewrite | NeedsFix Testing | ### What version of Go are you using (`go version`)?
<pre>
$ go version
go version devel +c20b71eb37 Sat Nov 16 02:06:39 2019 +0000 linux/amd6
</pre>
### Does this issue reproduce with the latest release?
Yes.
### What operating system and processor architecture are you using (`go env`)?
<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
GO111MODULE=""
GOARCH="amd64"
GOBIN=""
GOCACHE="/home/u/.cache/go-build"
GOENV="/home/u/.config/go/env"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOINSECURE=""
GONOPROXY=""
GONOSUMDB=""
GOOS="linux"
GOPATH="/home/u/goget:/home/u/Desktop/go"
GOPRIVATE=""
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/home/u/go"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/home/u/go/pkg/tool/linux_amd64"
GCCGO="gccgo"
AR="ar"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
GOMOD="/home/u/go/src/cmd/go.mod"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build745246669=/tmp/go-build -gno-record-gcc-switches"
</pre></details>
### What did you do?
<!--
If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on play.golang.org is best.
-->
1. clone the go repository: `git clone https://go.googlesource.com/go.git`
2. build go as usual: `cd src; ./all.bash`
3. edit `cmd/fix/context_test.go` to ensure that the test case should FAIL.
```diff
diff --git a/src/cmd/fix/context_test.go b/src/cmd/fix/context_test.go
index 935d0d7235..f666be2fb1 100644
--- a/src/cmd/fix/context_test.go
+++ b/src/cmd/fix/context_test.go
@@ -19,7 +19,7 @@ var _ = "golang.org/x/net/context"
`,
Out: `package main
-import "context"
+import "context"x
var _ = "golang.org/x/net/context"
`,
```
4. run `go test` from the `src/cmd/fix` directory.
```
$ go test
PASS
ok cmd/fix 0.032s
```
5. notice that the test case passes, even though it *should* fail, given that we edited the expected output of the context rewrite rule.
6. remove call to `t.Parallel` in `cmd/fix/main_test.go`
```diff
diff --git a/src/cmd/fix/main_test.go b/src/cmd/fix/main_test.go
index ee74f24c6e..5214d67af1 100644
--- a/src/cmd/fix/main_test.go
+++ b/src/cmd/fix/main_test.go
@@ -77,7 +77,7 @@ func parseFixPrint(t *testing.T, fn func(*ast.File) bool, desc, in string, mustB
func TestRewrite(t *testing.T) {
for _, tt := range testCases {
t.Run(tt.Name, func(t *testing.T) {
- t.Parallel()
+ //t.Parallel()
// Apply fix: should get tt.Out.
out, fixed, ok := parseFixPrint(t, tt.Fn, tt.Name, tt.In, true)
if !ok {
```
7. re-run test case using `go test` from the `src/cmd/fix` directory.
```
--- FAIL: TestRewrite (2.86s)
--- FAIL: TestRewrite/context.0 (0.00s)
main_test.go:94: incorrect output.
main_test.go:96: --- have
package main
import "context"
var _ = "golang.org/x/net/context"
--- want
package main
import "context"x
var _ = "golang.org/x/net/context"
main_test.go:133: --- /tmp/go-fix-test929058818 2019-11-15 21:39:47.643666701 -0600
+++ /tmp/go-fix-test221839737 2019-11-15 21:39:47.643666701 -0600
@@ -1,5 +1,5 @@
package main
-import "context"
+import "context"x
var _ = "golang.org/x/net/context"
FAIL
exit status 1
FAIL cmd/fix 2.866s
```
8. notice that the test case now fails, as it should do, given that we edited the expected output of the context rewrite rule.
### What did you expect to see?
A failed test case (after having modified the expected output of the `context_test.go` test case).
### What did you see instead?
Test cases passing without error. | 1.0 | cmd/fix: incorrect loop variable aliasing in TestRewrite - ### What version of Go are you using (`go version`)?
<pre>
$ go version
go version devel +c20b71eb37 Sat Nov 16 02:06:39 2019 +0000 linux/amd6
</pre>
### Does this issue reproduce with the latest release?
Yes.
### What operating system and processor architecture are you using (`go env`)?
<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
GO111MODULE=""
GOARCH="amd64"
GOBIN=""
GOCACHE="/home/u/.cache/go-build"
GOENV="/home/u/.config/go/env"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOINSECURE=""
GONOPROXY=""
GONOSUMDB=""
GOOS="linux"
GOPATH="/home/u/goget:/home/u/Desktop/go"
GOPRIVATE=""
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/home/u/go"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/home/u/go/pkg/tool/linux_amd64"
GCCGO="gccgo"
AR="ar"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
GOMOD="/home/u/go/src/cmd/go.mod"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build745246669=/tmp/go-build -gno-record-gcc-switches"
</pre></details>
### What did you do?
<!--
If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on play.golang.org is best.
-->
1. clone the go repository: `git clone https://go.googlesource.com/go.git`
2. build go as usual: `cd src; ./all.bash`
3. edit `cmd/fix/context_test.go` to ensure that the test case should FAIL.
```diff
diff --git a/src/cmd/fix/context_test.go b/src/cmd/fix/context_test.go
index 935d0d7235..f666be2fb1 100644
--- a/src/cmd/fix/context_test.go
+++ b/src/cmd/fix/context_test.go
@@ -19,7 +19,7 @@ var _ = "golang.org/x/net/context"
`,
Out: `package main
-import "context"
+import "context"x
var _ = "golang.org/x/net/context"
`,
```
4. run `go test` from the `src/cmd/fix` directory.
```
$ go test
PASS
ok cmd/fix 0.032s
```
5. notice that the test case passes, even though it *should* fail, given that we edited the expected output of the context rewrite rule.
6. remove call to `t.Parallel` in `cmd/fix/main_test.go`
```diff
diff --git a/src/cmd/fix/main_test.go b/src/cmd/fix/main_test.go
index ee74f24c6e..5214d67af1 100644
--- a/src/cmd/fix/main_test.go
+++ b/src/cmd/fix/main_test.go
@@ -77,7 +77,7 @@ func parseFixPrint(t *testing.T, fn func(*ast.File) bool, desc, in string, mustB
func TestRewrite(t *testing.T) {
for _, tt := range testCases {
t.Run(tt.Name, func(t *testing.T) {
- t.Parallel()
+ //t.Parallel()
// Apply fix: should get tt.Out.
out, fixed, ok := parseFixPrint(t, tt.Fn, tt.Name, tt.In, true)
if !ok {
```
7. re-run test case using `go test` from the `src/cmd/fix` directory.
```
--- FAIL: TestRewrite (2.86s)
--- FAIL: TestRewrite/context.0 (0.00s)
main_test.go:94: incorrect output.
main_test.go:96: --- have
package main
import "context"
var _ = "golang.org/x/net/context"
--- want
package main
import "context"x
var _ = "golang.org/x/net/context"
main_test.go:133: --- /tmp/go-fix-test929058818 2019-11-15 21:39:47.643666701 -0600
+++ /tmp/go-fix-test221839737 2019-11-15 21:39:47.643666701 -0600
@@ -1,5 +1,5 @@
package main
-import "context"
+import "context"x
var _ = "golang.org/x/net/context"
FAIL
exit status 1
FAIL cmd/fix 2.866s
```
8. notice that the test case now fails, as it should do, given that we edited the expected output of the context rewrite rule.
### What did you expect to see?
A failed test case (after having modified the expected output of the `context_test.go` test case).
### What did you see instead?
Test cases passing without error. | non_priority | cmd fix incorrect loop variable aliasing in testrewrite what version of go are you using go version go version go version devel sat nov linux does this issue reproduce with the latest release yes what operating system and processor architecture are you using go env go env output go env goarch gobin gocache home u cache go build goenv home u config go env goexe goflags gohostarch gohostos linux goinsecure gonoproxy gonosumdb goos linux gopath home u goget home u desktop go goprivate goproxy goroot home u go gosumdb sum golang org gotmpdir gotooldir home u go pkg tool linux gccgo gccgo ar ar cc gcc cxx g cgo enabled gomod home u go src cmd go mod cgo cflags g cgo cppflags cgo cxxflags g cgo fflags g cgo ldflags g pkg config pkg config gogccflags fpic pthread fmessage length fdebug prefix map tmp go tmp go build gno record gcc switches what did you do if possible provide a recipe for reproducing the error a complete runnable program is good a link on play golang org is best clone the go repository git clone build go as usual cd src all bash edit cmd fix context test go to ensure that the test case should fail diff diff git a src cmd fix context test go b src cmd fix context test go index a src cmd fix context test go b src cmd fix context test go var golang org x net context out package main import context import context x var golang org x net context run go test from the src cmd fix directory go test pass ok cmd fix notice that the test case passes even though it should fail given that we edited the expected output of the context rewrite rule remove call to t parallel in cmd fix main test go diff diff git a src cmd fix main test go b src cmd fix main test go index a src cmd fix main test go b src cmd fix main test go func parsefixprint t testing t fn func ast file bool desc in string mustb func testrewrite t testing t for tt range testcases t run tt name func t testing t t parallel t parallel apply fix should get tt out out fixed ok parsefixprint t tt fn tt name tt in true if ok re run test case using go test from the src cmd fix directory fail testrewrite fail testrewrite context main test go incorrect output main test go have package main import context var golang org x net context want package main import context x var golang org x net context main test go tmp go fix tmp go fix package main import context import context x var golang org x net context fail exit status fail cmd fix notice that the test case now fails as it should do given that we edited the expected output of the context rewrite rule what did you expect to see a failed test case after having modified the expected output of the context test go test case what did you see instead test cases passing without error | 0 |
99,348 | 20,958,419,038 | IssuesEvent | 2022-03-27 12:41:13 | Onelinerhub/onelinerhub | https://api.github.com/repos/Onelinerhub/onelinerhub | opened | Short solution needed: "How to load data frame from CSV" (python-pandas) | help wanted good first issue code python-pandas | Please help us write most modern and shortest code solution for this issue:
**How to load data frame from CSV** (technology: [python-pandas](https://onelinerhub.com/python-pandas))
### Fast way
Just write the code solution in the comments.
### Prefered way
1. Create pull request with a new code file inside [inbox folder](https://github.com/Onelinerhub/onelinerhub/tree/main/inbox).
2. Don't forget to use comments to make solution explained.
3. Link to this issue in comments of pull request. | 1.0 | Short solution needed: "How to load data frame from CSV" (python-pandas) - Please help us write most modern and shortest code solution for this issue:
**How to load data frame from CSV** (technology: [python-pandas](https://onelinerhub.com/python-pandas))
### Fast way
Just write the code solution in the comments.
### Prefered way
1. Create pull request with a new code file inside [inbox folder](https://github.com/Onelinerhub/onelinerhub/tree/main/inbox).
2. Don't forget to use comments to make solution explained.
3. Link to this issue in comments of pull request. | non_priority | short solution needed how to load data frame from csv python pandas please help us write most modern and shortest code solution for this issue how to load data frame from csv technology fast way just write the code solution in the comments prefered way create pull request with a new code file inside don t forget to use comments to make solution explained link to this issue in comments of pull request | 0 |
256,519 | 27,561,683,769 | IssuesEvent | 2023-03-07 22:39:54 | samqws-marketing/amzn-ion-hive-serde | https://api.github.com/repos/samqws-marketing/amzn-ion-hive-serde | closed | CVE-2020-36183 (High) detected in jackson-databind-2.6.5.jar - autoclosed | Mend: dependency security vulnerability | ## CVE-2020-36183 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>jackson-databind-2.6.5.jar</b></p></summary>
<p>General data-binding functionality for Jackson: works on core streaming API</p>
<p>Library home page: <a href="http://github.com/FasterXML/jackson">http://github.com/FasterXML/jackson</a></p>
<p>Path to dependency file: /integration-test/build.gradle</p>
<p>Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/com.fasterxml.jackson.core/jackson-databind/2.6.5/d50be1723a09befd903887099ff2014ea9020333/jackson-databind-2.6.5.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/com.fasterxml.jackson.core/jackson-databind/2.6.5/d50be1723a09befd903887099ff2014ea9020333/jackson-databind-2.6.5.jar</p>
<p>
Dependency Hierarchy:
- hive-serde-2.3.9.jar (Root Library)
- hive-common-2.3.9.jar
- :x: **jackson-databind-2.6.5.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/samqws-marketing/amzn-ion-hive-serde/commit/ffb6641ebb10aac58bb7eec412635e91e79fac24">ffb6641ebb10aac58bb7eec412635e91e79fac24</a></p>
<p>Found in base branch: <b>0.3.0</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
FasterXML jackson-databind 2.x before 2.9.10.8 mishandles the interaction between serialization gadgets and typing, related to org.docx4j.org.apache.xalan.lib.sql.JNDIConnectionPool.
<p>Publish Date: 2021-01-07
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2020-36183>CVE-2020-36183</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>8.1</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Release Date: 2021-01-07</p>
<p>Fix Resolution (com.fasterxml.jackson.core:jackson-databind): 2.6.7.5</p>
<p>Direct dependency fix Resolution (org.apache.hive:hive-serde): 3.0.0</p>
</p>
</details>
<p></p>
***
<!-- REMEDIATE-OPEN-PR-START -->
- [ ] Check this box to open an automated fix PR
<!-- REMEDIATE-OPEN-PR-END -->
| True | CVE-2020-36183 (High) detected in jackson-databind-2.6.5.jar - autoclosed - ## CVE-2020-36183 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>jackson-databind-2.6.5.jar</b></p></summary>
<p>General data-binding functionality for Jackson: works on core streaming API</p>
<p>Library home page: <a href="http://github.com/FasterXML/jackson">http://github.com/FasterXML/jackson</a></p>
<p>Path to dependency file: /integration-test/build.gradle</p>
<p>Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/com.fasterxml.jackson.core/jackson-databind/2.6.5/d50be1723a09befd903887099ff2014ea9020333/jackson-databind-2.6.5.jar,/home/wss-scanner/.gradle/caches/modules-2/files-2.1/com.fasterxml.jackson.core/jackson-databind/2.6.5/d50be1723a09befd903887099ff2014ea9020333/jackson-databind-2.6.5.jar</p>
<p>
Dependency Hierarchy:
- hive-serde-2.3.9.jar (Root Library)
- hive-common-2.3.9.jar
- :x: **jackson-databind-2.6.5.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/samqws-marketing/amzn-ion-hive-serde/commit/ffb6641ebb10aac58bb7eec412635e91e79fac24">ffb6641ebb10aac58bb7eec412635e91e79fac24</a></p>
<p>Found in base branch: <b>0.3.0</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
FasterXML jackson-databind 2.x before 2.9.10.8 mishandles the interaction between serialization gadgets and typing, related to org.docx4j.org.apache.xalan.lib.sql.JNDIConnectionPool.
<p>Publish Date: 2021-01-07
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2020-36183>CVE-2020-36183</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>8.1</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Release Date: 2021-01-07</p>
<p>Fix Resolution (com.fasterxml.jackson.core:jackson-databind): 2.6.7.5</p>
<p>Direct dependency fix Resolution (org.apache.hive:hive-serde): 3.0.0</p>
</p>
</details>
<p></p>
***
<!-- REMEDIATE-OPEN-PR-START -->
- [ ] Check this box to open an automated fix PR
<!-- REMEDIATE-OPEN-PR-END -->
| non_priority | cve high detected in jackson databind jar autoclosed cve high severity vulnerability vulnerable library jackson databind jar general data binding functionality for jackson works on core streaming api library home page a href path to dependency file integration test build gradle path to vulnerable library home wss scanner gradle caches modules files com fasterxml jackson core jackson databind jackson databind jar home wss scanner gradle caches modules files com fasterxml jackson core jackson databind jackson databind jar dependency hierarchy hive serde jar root library hive common jar x jackson databind jar vulnerable library found in head commit a href found in base branch vulnerability details fasterxml jackson databind x before mishandles the interaction between serialization gadgets and typing related to org org apache xalan lib sql jndiconnectionpool publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity high privileges required none user interaction none scope unchanged impact metrics confidentiality impact high integrity impact high availability impact high for more information on scores click a href suggested fix type upgrade version release date fix resolution com fasterxml jackson core jackson databind direct dependency fix resolution org apache hive hive serde check this box to open an automated fix pr | 0 |
681,156 | 23,299,058,299 | IssuesEvent | 2022-08-07 03:01:33 | wso2/product-is | https://api.github.com/repos/wso2/product-is | closed | UI loading continuously when view the assigned users in 'Roles' section in the sub-organization | Priority/Highest Severity/Critical bug Affected-6.0.0 QA-Reported Organization Management | **Describe the issue:**
If the sub-organization doesn't have users initially and then if we view 'Users' in the 'Roles' section, it doesn't show the expected result. Please refer to this screencast.
https://user-images.githubusercontent.com/13362482/182848081-90b5aa68-b40c-450b-b428-dd58f5d91399.mov
It shows the expected output if at least one user available in the organization
https://user-images.githubusercontent.com/13362482/182849182-0519f4af-5dbe-40f9-9ae4-10f8c2a7331a.mov
**How to reproduce:**
<!-- Steps to reproduce the behavior. -->
**Expected behavior:**
<!-- A clear and concise description of what you expected to happen. -->
**Environment information** (_Please complete the following information; remove any unnecessary fields_) **:**
- Product Version: [e.g., IS 5.10.0, IS 5.9.0]
- OS: [e.g., Windows, Linux, Mac]
- Database: [e.g., MySQL, H2]
- Userstore: [e.g., LDAP, JDBC]
---
### Optional Fields
**Related issues:**
<!-- Any related issues from this/other repositories-->
**Suggested labels:**
<!-- Only to be used by non-members -->
| 1.0 | UI loading continuously when view the assigned users in 'Roles' section in the sub-organization - **Describe the issue:**
If the sub-organization doesn't have users initially and then if we view 'Users' in the 'Roles' section, it doesn't show the expected result. Please refer to this screencast.
https://user-images.githubusercontent.com/13362482/182848081-90b5aa68-b40c-450b-b428-dd58f5d91399.mov
It shows the expected output if at least one user available in the organization
https://user-images.githubusercontent.com/13362482/182849182-0519f4af-5dbe-40f9-9ae4-10f8c2a7331a.mov
**How to reproduce:**
<!-- Steps to reproduce the behavior. -->
**Expected behavior:**
<!-- A clear and concise description of what you expected to happen. -->
**Environment information** (_Please complete the following information; remove any unnecessary fields_) **:**
- Product Version: [e.g., IS 5.10.0, IS 5.9.0]
- OS: [e.g., Windows, Linux, Mac]
- Database: [e.g., MySQL, H2]
- Userstore: [e.g., LDAP, JDBC]
---
### Optional Fields
**Related issues:**
<!-- Any related issues from this/other repositories-->
**Suggested labels:**
<!-- Only to be used by non-members -->
| priority | ui loading continuously when view the assigned users in roles section in the sub organization describe the issue if the sub organization doesn t have users initially and then if we view users in the roles section it doesn t show the expected result please refer to this screencast it shows the expected output if at least one user available in the organization how to reproduce expected behavior environment information please complete the following information remove any unnecessary fields product version os database userstore optional fields related issues suggested labels | 1 |
279,014 | 21,105,196,020 | IssuesEvent | 2022-04-04 18:02:38 | spacetimedotnet/spacetime | https://api.github.com/repos/spacetimedotnet/spacetime | opened | Create MSIX installer for alpha builds | documentation enhancement help wanted | Create an MSIX installer for Alpha builds - using a self signed certificate.
- [ ] MSIX Installer
- [ ] Certificate generated
- [ ] Documentation added | 1.0 | Create MSIX installer for alpha builds - Create an MSIX installer for Alpha builds - using a self signed certificate.
- [ ] MSIX Installer
- [ ] Certificate generated
- [ ] Documentation added | non_priority | create msix installer for alpha builds create an msix installer for alpha builds using a self signed certificate msix installer certificate generated documentation added | 0 |
817,191 | 30,630,150,575 | IssuesEvent | 2023-07-24 14:04:43 | wp-media/wp-rocket | https://api.github.com/repos/wp-media/wp-rocket | closed | Cache clearing not working on a per-post basis in conjunction with WPML (non-encoded URL / special chars?) | type: bug 3rd party compatibility module: cache priority: medium severity: major | **Before submitting an issue please check that you’ve completed the following steps:**
- [x] Made sure you’re on the latest version
- [x] Used the search feature to ensure that the bug hasn’t been reported before
**Describe the bug**
We're using WP Rocket in conjunction with WPML and I have noticed a faulty behaviour when it comes to saving a (translated) post – WP Rocket doesn't automatically clear the cache for the corresponding post and the cached file also persists when actively using the `purge_cache`-action from the top bar menu.
Clearing the whole language cache via `purge_cache&type=all&lang=fr` works fine though so there must be
What I've gathered from looking at the scheduled actions logs is, that the URL passed via arg differ and I suspect the handling of the special chars / the non-encoded URL to be the culprit...
The single calls pass
`/fr/équipes/dr-eberhard-koch`
while the full cache rebuild uses
`/fr/%C3%A9quipes/dr-eberhard-koch`
Thus it could be related to the missing URL encoding...?
Would appreciate if you could take a look here – thanks!
**Additional context**
- WordPress Core @ 6.1
- WPML @ 4.5.13
- WP Rocket @ 3.12.2.1
**Backlog Grooming (for WP Media dev team use only)**
- [ ] Reproduce the problem
- [ ] Identify the root cause
- [ ] Scope a solution
- [ ] Estimate the effort
| 1.0 | Cache clearing not working on a per-post basis in conjunction with WPML (non-encoded URL / special chars?) - **Before submitting an issue please check that you’ve completed the following steps:**
- [x] Made sure you’re on the latest version
- [x] Used the search feature to ensure that the bug hasn’t been reported before
**Describe the bug**
We're using WP Rocket in conjunction with WPML and I have noticed a faulty behaviour when it comes to saving a (translated) post – WP Rocket doesn't automatically clear the cache for the corresponding post and the cached file also persists when actively using the `purge_cache`-action from the top bar menu.
Clearing the whole language cache via `purge_cache&type=all&lang=fr` works fine though so there must be
What I've gathered from looking at the scheduled actions logs is, that the URL passed via arg differ and I suspect the handling of the special chars / the non-encoded URL to be the culprit...
The single calls pass
`/fr/équipes/dr-eberhard-koch`
while the full cache rebuild uses
`/fr/%C3%A9quipes/dr-eberhard-koch`
Thus it could be related to the missing URL encoding...?
Would appreciate if you could take a look here – thanks!
**Additional context**
- WordPress Core @ 6.1
- WPML @ 4.5.13
- WP Rocket @ 3.12.2.1
**Backlog Grooming (for WP Media dev team use only)**
- [ ] Reproduce the problem
- [ ] Identify the root cause
- [ ] Scope a solution
- [ ] Estimate the effort
| priority | cache clearing not working on a per post basis in conjunction with wpml non encoded url special chars before submitting an issue please check that you’ve completed the following steps made sure you’re on the latest version used the search feature to ensure that the bug hasn’t been reported before describe the bug we re using wp rocket in conjunction with wpml and i have noticed a faulty behaviour when it comes to saving a translated post – wp rocket doesn t automatically clear the cache for the corresponding post and the cached file also persists when actively using the purge cache action from the top bar menu clearing the whole language cache via purge cache type all lang fr works fine though so there must be what i ve gathered from looking at the scheduled actions logs is that the url passed via arg differ and i suspect the handling of the special chars the non encoded url to be the culprit the single calls pass fr équipes dr eberhard koch while the full cache rebuild uses fr dr eberhard koch thus it could be related to the missing url encoding would appreciate if you could take a look here – thanks additional context wordpress core wpml wp rocket backlog grooming for wp media dev team use only reproduce the problem identify the root cause scope a solution estimate the effort | 1 |
357,309 | 10,604,970,852 | IssuesEvent | 2019-10-10 19:22:56 | SkriptLang/Skript | https://api.github.com/repos/SkriptLang/Skript | closed | Can't set player list name of a variable containing a player | bug priority: medium | ### Description
Skript doesn't allow you to set the player list name of a variable that contains a player.
(the player list name of {variable} can't be set to anything)
### Steps to Reproduce
1. Set a variable to any player object
2. Try to set the tablist name of that variable
### Expected Behavior
The tablist name should change and no error should be given.
### Errors / Screenshots
### Server Information
* **Server version/platform:** git-Paper-199 (1.14.4)
* **Skript version:** 2.4-beta7
### Additional Context
The issue can be worked around by parsing the string representation of the variable as a player.
| 1.0 | Can't set player list name of a variable containing a player - ### Description
Skript doesn't allow you to set the player list name of a variable that contains a player.
(the player list name of {variable} can't be set to anything)
### Steps to Reproduce
1. Set a variable to any player object
2. Try to set the tablist name of that variable
### Expected Behavior
The tablist name should change and no error should be given.
### Errors / Screenshots
### Server Information
* **Server version/platform:** git-Paper-199 (1.14.4)
* **Skript version:** 2.4-beta7
### Additional Context
The issue can be worked around by parsing the string representation of the variable as a player.
| priority | can t set player list name of a variable containing a player description skript doesn t allow you to set the player list name of a variable that contains a player the player list name of variable can t be set to anything steps to reproduce set a variable to any player object try to set the tablist name of that variable expected behavior the tablist name should change and no error should be given errors screenshots server information server version platform git paper skript version additional context the issue can be worked around by parsing the string representation of the variable as a player | 1 |
228,497 | 18,238,586,841 | IssuesEvent | 2021-10-01 10:03:11 | Sifchain/sifnode | https://api.github.com/repos/Sifchain/sifnode | opened | Exploration of automated IBC status monitoring and debugging | ChainOps Testing Sifnode | Explore options for detailed automated status page for IBC channels and transactions to provide constant monitoring and sustainable and scalable debugging of what is happening with chains, channels, accounts and transfers. | 1.0 | Exploration of automated IBC status monitoring and debugging - Explore options for detailed automated status page for IBC channels and transactions to provide constant monitoring and sustainable and scalable debugging of what is happening with chains, channels, accounts and transfers. | non_priority | exploration of automated ibc status monitoring and debugging explore options for detailed automated status page for ibc channels and transactions to provide constant monitoring and sustainable and scalable debugging of what is happening with chains channels accounts and transfers | 0 |
438,958 | 12,664,193,444 | IssuesEvent | 2020-06-18 03:50:25 | AuDigitalHealth/ci-fhir-r4 | https://api.github.com/repos/AuDigitalHealth/ci-fhir-r4 | closed | Pathology Report with atomic content | feature/new-profile size/medium status/in-progress tag/priority | # Prerequisites
- [x] I have searched [open](https://github.com/ci-fhir-r4/Issues/issues) and [closed](https://github.com/ci-fhir-r4/Issues/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aclosed) issues to make sure it isn't already requested or reported
- [x] I have written a descriptive issue title
# The feature
## Change description
The purpose of this profile is to define an atomic representation of a pathology report issued by the diagnostic service provider to support the electronic exchange of pathology reports between healthcare providers, and between healthcare providers and the My Health Record system infrastructure in Australia.
## What it actually enables people to do
Ensure the desired behavior is applied to subject reference.
## Mockups
If applicable, add screenshots or mockups to help explain the issue / feature.
## How awesome would it be?
<!-- A description of the value of this request to help us understand its value in comparison to the other awesome things we are doing. -->
## Workarounds
<!-- Are there any viable workarounds in case this cannot be addressed quickly?-->
## Additional context
Add any other context or links about the issue or feature here, e.g. replicate this page over here in this context. | 1.0 | Pathology Report with atomic content - # Prerequisites
- [x] I have searched [open](https://github.com/ci-fhir-r4/Issues/issues) and [closed](https://github.com/ci-fhir-r4/Issues/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aclosed) issues to make sure it isn't already requested or reported
- [x] I have written a descriptive issue title
# The feature
## Change description
The purpose of this profile is to define an atomic representation of a pathology report issued by the diagnostic service provider to support the electronic exchange of pathology reports between healthcare providers, and between healthcare providers and the My Health Record system infrastructure in Australia.
## What it actually enables people to do
Ensure the desired behavior is applied to subject reference.
## Mockups
If applicable, add screenshots or mockups to help explain the issue / feature.
## How awesome would it be?
<!-- A description of the value of this request to help us understand its value in comparison to the other awesome things we are doing. -->
## Workarounds
<!-- Are there any viable workarounds in case this cannot be addressed quickly?-->
## Additional context
Add any other context or links about the issue or feature here, e.g. replicate this page over here in this context. | priority | pathology report with atomic content prerequisites i have searched and issues to make sure it isn t already requested or reported i have written a descriptive issue title the feature change description the purpose of this profile is to define an atomic representation of a pathology report issued by the diagnostic service provider to support the electronic exchange of pathology reports between healthcare providers and between healthcare providers and the my health record system infrastructure in australia what it actually enables people to do ensure the desired behavior is applied to subject reference mockups if applicable add screenshots or mockups to help explain the issue feature how awesome would it be workarounds additional context add any other context or links about the issue or feature here e g replicate this page over here in this context | 1 |
68,777 | 8,345,767,834 | IssuesEvent | 2018-10-01 05:17:02 | caicloud/ciao | https://api.github.com/repos/caicloud/ciao | closed | [discussion] Use PVC or Configmap to avoid Docker building/pushing | kind/design | /kind discussion
I am not sure if it works. If we build and push a Docker image every time we run the code, overhead is definitely high. | 1.0 | [discussion] Use PVC or Configmap to avoid Docker building/pushing - /kind discussion
I am not sure if it works. If we build and push a Docker image every time we run the code, overhead is definitely high. | non_priority | use pvc or configmap to avoid docker building pushing kind discussion i am not sure if it works if we build and push a docker image every time we run the code overhead is definitely high | 0 |
584,356 | 17,422,089,812 | IssuesEvent | 2021-08-04 03:31:47 | brave/qa-resources | https://api.github.com/repos/brave/qa-resources | closed | 1.27.x - Release #2 | ARM OS/Android priority/P1 x86 | ### <img src="https://www.rebron.org/wordpress/wp-content/uploads/2019/06/Android.png"> `1.27.x - Release #2`
#### Release Date/Target:
#### Release Date/Target:
* Release Date: **`July 27, 2021`**
#### Summary:
Includes the following features/fixes:
* ability to change “Block trackers & ads” to either “Standard”, “Aggressive” or “Allow all” via the shields panel
* new tab tutorial page on startup for Japan region
* Updated SE in certain regions for new installs
* "Disconnected" Brave Rewards wallet state
* ads per hour under brave://settings reverting to 0
* Chromium 92.0.4515.115
**Milestone:**
* https://github.com/brave/brave-browser/milestone/222
* https://github.com/brave/brave-core/milestone/156
**Current Progress:**
* ARM --> **`Completed`**
* Tablet --> **`Completed`**
**Manual Passes:**
* ARM --> https://github.com/brave/brave-browser/issues/17191
* Tablet --> https://github.com/brave/brave-browser/issues/17192
* x86 --> https://github.com/brave/brave-browser/issues/17193 | 1.0 | 1.27.x - Release #2 - ### <img src="https://www.rebron.org/wordpress/wp-content/uploads/2019/06/Android.png"> `1.27.x - Release #2`
#### Release Date/Target:
#### Release Date/Target:
* Release Date: **`July 27, 2021`**
#### Summary:
Includes the following features/fixes:
* ability to change “Block trackers & ads” to either “Standard”, “Aggressive” or “Allow all” via the shields panel
* new tab tutorial page on startup for Japan region
* Updated SE in certain regions for new installs
* "Disconnected" Brave Rewards wallet state
* ads per hour under brave://settings reverting to 0
* Chromium 92.0.4515.115
**Milestone:**
* https://github.com/brave/brave-browser/milestone/222
* https://github.com/brave/brave-core/milestone/156
**Current Progress:**
* ARM --> **`Completed`**
* Tablet --> **`Completed`**
**Manual Passes:**
* ARM --> https://github.com/brave/brave-browser/issues/17191
* Tablet --> https://github.com/brave/brave-browser/issues/17192
* x86 --> https://github.com/brave/brave-browser/issues/17193 | priority | x release img src x release release date target release date target release date july summary includes the following features fixes ability to change “block trackers ads” to either “standard” “aggressive” or “allow all” via the shields panel new tab tutorial page on startup for japan region updated se in certain regions for new installs disconnected brave rewards wallet state ads per hour under brave settings reverting to chromium milestone current progress arm completed tablet completed manual passes arm tablet | 1 |
49,478 | 13,453,470,105 | IssuesEvent | 2020-09-09 01:03:07 | nasifimtiazohi/openmrs-module-coreapps-1.28.0 | https://api.github.com/repos/nasifimtiazohi/openmrs-module-coreapps-1.28.0 | opened | WS-2018-0590 (High) detected in diff-1.4.0.tgz | security vulnerability | ## WS-2018-0590 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>diff-1.4.0.tgz</b></p></summary>
<p>A javascript text diff implementation.</p>
<p>Library home page: <a href="https://registry.npmjs.org/diff/-/diff-1.4.0.tgz">https://registry.npmjs.org/diff/-/diff-1.4.0.tgz</a></p>
<p>Path to dependency file: /tmp/ws-scm/openmrs-module-coreapps-1.28.0/package.json</p>
<p>Path to vulnerable library: /tmp/ws-scm/openmrs-module-coreapps-1.28.0/node_modules/diff/package.json</p>
<p>
Dependency Hierarchy:
- compass-loader-0.0.4.tgz (Root Library)
- node-sass-2.1.1.tgz
- mocha-2.5.3.tgz
- :x: **diff-1.4.0.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/nasifimtiazohi/openmrs-module-coreapps-1.28.0/commit/a473f1097dd760370898008cacd6434f0620476f">a473f1097dd760370898008cacd6434f0620476f</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
A vulnerability was found in diff before v3.5.0, the affected versions of this package are vulnerable to Regular Expression Denial of Service (ReDoS) attacks.
<p>Publish Date: 2018-03-05
<p>URL: <a href=https://bugzilla.redhat.com/show_bug.cgi?id=1552148>WS-2018-0590</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 2 Score Details (<b>7.0</b>)</summary>
<p>
Base Score Metrics not available</p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/kpdecker/jsdiff/commit/2aec4298639bf30fb88a00b356bf404d3551b8c0">https://github.com/kpdecker/jsdiff/commit/2aec4298639bf30fb88a00b356bf404d3551b8c0</a></p>
<p>Release Date: 2019-06-11</p>
<p>Fix Resolution: 3.5.0</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | WS-2018-0590 (High) detected in diff-1.4.0.tgz - ## WS-2018-0590 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>diff-1.4.0.tgz</b></p></summary>
<p>A javascript text diff implementation.</p>
<p>Library home page: <a href="https://registry.npmjs.org/diff/-/diff-1.4.0.tgz">https://registry.npmjs.org/diff/-/diff-1.4.0.tgz</a></p>
<p>Path to dependency file: /tmp/ws-scm/openmrs-module-coreapps-1.28.0/package.json</p>
<p>Path to vulnerable library: /tmp/ws-scm/openmrs-module-coreapps-1.28.0/node_modules/diff/package.json</p>
<p>
Dependency Hierarchy:
- compass-loader-0.0.4.tgz (Root Library)
- node-sass-2.1.1.tgz
- mocha-2.5.3.tgz
- :x: **diff-1.4.0.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/nasifimtiazohi/openmrs-module-coreapps-1.28.0/commit/a473f1097dd760370898008cacd6434f0620476f">a473f1097dd760370898008cacd6434f0620476f</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
A vulnerability was found in diff before v3.5.0, the affected versions of this package are vulnerable to Regular Expression Denial of Service (ReDoS) attacks.
<p>Publish Date: 2018-03-05
<p>URL: <a href=https://bugzilla.redhat.com/show_bug.cgi?id=1552148>WS-2018-0590</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 2 Score Details (<b>7.0</b>)</summary>
<p>
Base Score Metrics not available</p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/kpdecker/jsdiff/commit/2aec4298639bf30fb88a00b356bf404d3551b8c0">https://github.com/kpdecker/jsdiff/commit/2aec4298639bf30fb88a00b356bf404d3551b8c0</a></p>
<p>Release Date: 2019-06-11</p>
<p>Fix Resolution: 3.5.0</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_priority | ws high detected in diff tgz ws high severity vulnerability vulnerable library diff tgz a javascript text diff implementation library home page a href path to dependency file tmp ws scm openmrs module coreapps package json path to vulnerable library tmp ws scm openmrs module coreapps node modules diff package json dependency hierarchy compass loader tgz root library node sass tgz mocha tgz x diff tgz vulnerable library found in head commit a href vulnerability details a vulnerability was found in diff before the affected versions of this package are vulnerable to regular expression denial of service redos attacks publish date url a href cvss score details base score metrics not available suggested fix type upgrade version origin a href release date fix resolution step up your open source security game with whitesource | 0 |
301,310 | 9,218,972,227 | IssuesEvent | 2019-03-11 14:31:57 | blackbaud/skyux-sdk-builder | https://api.github.com/repos/blackbaud/skyux-sdk-builder | closed | Command `skyux watch` disconnects if linting takes too long | Priority: Critical Type: Bug | During `skyux watch`, if the linting process takes longer than 20 (or so) seconds, I'll get the following messages:
```
Disconnected (0 times)Client disconnected from CONNECTED state (ping timeout) Chrome 72.0.3626 (Mac OS X 10.14.3) ERROR DisconnectedClient disconnected from CONNECTED state (ping timeout)
```
Or...
```
Chrome 72.0.3626 (Windows 10.0.0) ERROR
DisconnectedClient disconnected from CONNECTED state (ping timeout)
26 02 2019 13:14:16.380:INFO [middleware:stopper]: Stopping server
``` | 1.0 | Command `skyux watch` disconnects if linting takes too long - During `skyux watch`, if the linting process takes longer than 20 (or so) seconds, I'll get the following messages:
```
Disconnected (0 times)Client disconnected from CONNECTED state (ping timeout) Chrome 72.0.3626 (Mac OS X 10.14.3) ERROR DisconnectedClient disconnected from CONNECTED state (ping timeout)
```
Or...
```
Chrome 72.0.3626 (Windows 10.0.0) ERROR
DisconnectedClient disconnected from CONNECTED state (ping timeout)
26 02 2019 13:14:16.380:INFO [middleware:stopper]: Stopping server
``` | priority | command skyux watch disconnects if linting takes too long during skyux watch if the linting process takes longer than or so seconds i ll get the following messages disconnected times client disconnected from connected state ping timeout chrome mac os x error disconnectedclient disconnected from connected state ping timeout or chrome windows error disconnectedclient disconnected from connected state ping timeout info stopping server | 1 |
177,348 | 21,473,445,309 | IssuesEvent | 2022-04-26 11:39:45 | nanopathi/framework_base_AOSP10_r33_CVE-2021-39704 | https://api.github.com/repos/nanopathi/framework_base_AOSP10_r33_CVE-2021-39704 | opened | CVE-2021-0315 (High) detected in baseandroid-10.0.0_r34 | security vulnerability | ## CVE-2021-0315 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>baseandroid-10.0.0_r34</b></p></summary>
<p>
<p>Android framework classes and services</p>
<p>Library home page: <a href=https://android.googlesource.com/platform/frameworks/base>https://android.googlesource.com/platform/frameworks/base</a></p>
<p>Found in HEAD commit: <a href="https://github.com/nanopathi/framework_base_AOSP10_r33_CVE-2021-39704/commit/5c98afa356ae703eb7d27b712d674edd7ad5b0d8">5c98afa356ae703eb7d27b712d674edd7ad5b0d8</a></p>
<p>Found in base branch: <b>master</b></p></p>
</details>
</p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Source Files (2)</summary>
<p></p>
<p>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/core/java/android/accounts/GrantCredentialsPermissionActivity.java</b>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/core/java/android/accounts/GrantCredentialsPermissionActivity.java</b>
</p>
</details>
<p></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
In onCreate of GrantCredentialsPermissionActivity.java, there is a possible way to convince the user to grant an app access to an account due to a tapjacking/overlay attack. This could lead to local escalation of privilege with User execution privileges needed. User interaction is needed for exploitation. Product: Android; Versions: Android-8.1, Android-9, Android-10, Android-11, Android-8.0; Android ID: A-169763814.
<p>Publish Date: 2021-01-11
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-0315>CVE-2021-0315</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.3</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: Required
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/aosp-mirror/platform_frameworks_base/releases/tag/android-11.0.0_r26">https://github.com/aosp-mirror/platform_frameworks_base/releases/tag/android-11.0.0_r26</a></p>
<p>Release Date: 2020-11-07</p>
<p>Fix Resolution: android-11.0.0_r26</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-0315 (High) detected in baseandroid-10.0.0_r34 - ## CVE-2021-0315 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>baseandroid-10.0.0_r34</b></p></summary>
<p>
<p>Android framework classes and services</p>
<p>Library home page: <a href=https://android.googlesource.com/platform/frameworks/base>https://android.googlesource.com/platform/frameworks/base</a></p>
<p>Found in HEAD commit: <a href="https://github.com/nanopathi/framework_base_AOSP10_r33_CVE-2021-39704/commit/5c98afa356ae703eb7d27b712d674edd7ad5b0d8">5c98afa356ae703eb7d27b712d674edd7ad5b0d8</a></p>
<p>Found in base branch: <b>master</b></p></p>
</details>
</p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Source Files (2)</summary>
<p></p>
<p>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/core/java/android/accounts/GrantCredentialsPermissionActivity.java</b>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/core/java/android/accounts/GrantCredentialsPermissionActivity.java</b>
</p>
</details>
<p></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
In onCreate of GrantCredentialsPermissionActivity.java, there is a possible way to convince the user to grant an app access to an account due to a tapjacking/overlay attack. This could lead to local escalation of privilege with User execution privileges needed. User interaction is needed for exploitation. Product: Android; Versions: Android-8.1, Android-9, Android-10, Android-11, Android-8.0; Android ID: A-169763814.
<p>Publish Date: 2021-01-11
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-0315>CVE-2021-0315</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.3</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: Required
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/aosp-mirror/platform_frameworks_base/releases/tag/android-11.0.0_r26">https://github.com/aosp-mirror/platform_frameworks_base/releases/tag/android-11.0.0_r26</a></p>
<p>Release Date: 2020-11-07</p>
<p>Fix Resolution: android-11.0.0_r26</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_priority | cve high detected in baseandroid cve high severity vulnerability vulnerable library baseandroid android framework classes and services library home page a href found in head commit a href found in base branch master vulnerable source files core java android accounts grantcredentialspermissionactivity java core java android accounts grantcredentialspermissionactivity java vulnerability details in oncreate of grantcredentialspermissionactivity java there is a possible way to convince the user to grant an app access to an account due to a tapjacking overlay attack this could lead to local escalation of privilege with user execution privileges needed user interaction is needed for exploitation product android versions android android android android android android id a publish date url a href cvss score details base score metrics exploitability metrics attack vector local attack complexity low privileges required low user interaction required scope unchanged impact metrics confidentiality impact high integrity impact high availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution android step up your open source security game with whitesource | 0 |
87,458 | 17,270,649,860 | IssuesEvent | 2021-07-22 19:20:34 | WarEmu/WarBugs | https://api.github.com/repos/WarEmu/WarBugs | closed | Death From Below quest: Brauk kill not counted | Dungeon: Sigmar's Crypt Dungeon: Warpblade Tunnels Fix Pending NPC Quests Scripting Sourcecode | Brauk boss (who is an ad to Skrot boss) gets despawned after the main boss is killed, and is not counted as kill in the Death From Below quest.
I don't have evidence from the site, but I can provide quest logs from two different chars that were doing full run of C&T, you can see that the Brauk kill is missed by 1 for both.
| 1.0 | Death From Below quest: Brauk kill not counted - Brauk boss (who is an ad to Skrot boss) gets despawned after the main boss is killed, and is not counted as kill in the Death From Below quest.
I don't have evidence from the site, but I can provide quest logs from two different chars that were doing full run of C&T, you can see that the Brauk kill is missed by 1 for both.
| non_priority | death from below quest brauk kill not counted brauk boss who is an ad to skrot boss gets despawned after the main boss is killed and is not counted as kill in the death from below quest i don t have evidence from the site but i can provide quest logs from two different chars that were doing full run of c t you can see that the brauk kill is missed by for both | 0 |
555,647 | 16,460,022,337 | IssuesEvent | 2021-05-21 17:29:07 | ucfopen/Obojobo | https://api.github.com/repos/ucfopen/Obojobo | closed | Question Bank options not being updated | bug high priority | Tried this on dev/21 - Seems that changing the option on a Question Bank from "All questions" to "Pick 1" isn't saving correctly. | 1.0 | Question Bank options not being updated - Tried this on dev/21 - Seems that changing the option on a Question Bank from "All questions" to "Pick 1" isn't saving correctly. | priority | question bank options not being updated tried this on dev seems that changing the option on a question bank from all questions to pick isn t saving correctly | 1 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.